Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Samsung Galaxy S Duos 3-VE / Galaxy Ace 4 SM-G316HU (vivalto5mve3g) #87

Open
dbp007 opened this issue Jul 22, 2018 · 3 comments
Open

Samsung Galaxy S Duos 3-VE / Galaxy Ace 4 SM-G316HU (vivalto5mve3g) #87

dbp007 opened this issue Jul 22, 2018 · 3 comments

Comments

@dbp007
Copy link

dbp007 commented Jul 22, 2018

Device: Galaxy ACE 4 (SM-G316HU)
Codename : vivalto5mve3g
Unofficial TWRP 3.0.2 : https://mega.nz/#!OtkiHKzL!LTF4TQukiUcKbl7nSv2pAbeJvEq4G_lfx0bdjQX42xk
Rom Unofficial CM 13 & its kernel : https://mega.nz/#!S4FDCb4C!W8RNFa40U0mJxPSL2fxn9N4b-J1SkZdZxTT0wDj874Q
Device running stock partition layout.
The Dump file:
repit-dump.log

@Lanchon
Copy link
Owner

Lanchon commented Nov 7, 2019

hi,

some newer devices have a signed GPT (partition table). on such devices, altering the GPT hard-bricks the device. this is the reason i mostly stopped development of REPIT.

make sure you read this. you can try running the strings command on images of your bootloaders (or post the images here) to get hints on the situation of your device. strings can usually rule out signatures, but it can also result in false positives.

to recover from a hard brick you would need an image of your eMMC and the ability to program the eMMC with a JTAG probe. if you do not know what JTAG is, then assume you have no way to recover your device.

please decide whether you want to risk testing a REPIT port on your device.

thanks!

@Lanchon
Copy link
Owner

Lanchon commented Nov 14, 2019

hi,

sorry for the long delay. are you still interested in this?

thanks!

@Lanchon Lanchon changed the title Add galaxy ace 4 (sm-g316hu) Samsung Galaxy S Duos 3-VE / Galaxy Ace 4 SM-G316HU (vivalto5mve3g) Nov 14, 2019
@dbp007
Copy link
Author

dbp007 commented Mar 4, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants