Related
So I my A2017G had RR-20170314 with TWRP 3.1.0-0 and AX7 R6 installed. Everything was working fine until today my phone rebooted while it was in my pocket. I didn't change anything before and haven't used it for some time and only noticed this through 2 short vibrations. Since then the phone refused to boot into system, TWRP was still accessible though. Three short blinks by the led directly after the bootloader screen and then the phone shut itself down.
Back in recovery I made a full backup and tried booting with deleting cache etc and installing the latest RR. Nothing worked.
When I went back to stock I was finally able to boot. Flashed TWRP 3.1.0-0 through axon7tool and installed RR again. And again only those 3 led blinks
Used "disemmcwp" to make sure write protection is disabled and noticed that when I rebootet the recovery got replaced by the stock one. Only if I enable write protection through "emmcwpenab" the recovery isn't replaced
Just checked the status of the bootloader and it still says unlocked.
I found two threads with a similiar issue but unfortunately nothing helped:
https://forum.xda-developers.com/axon-7/help/boot-recovery-boot-t3569364
https://forum.xda-developers.com/axon-7/help/3-flashes-reboot-phone-shuts-off-t3574324
Never experienced such a thing before. Any help is really appreciated ?
I'm really out of ideas what to do. And stock isn't really a permament solution
Are you using latest G bootstack? Is the device in dfu, or edl mode (check device manager on pc)?
Be very careful with that G version.
Yes since I was on RR before. Using the stock bootstack nor the one provided in the Los thread makes a difference.
Fortunately I'm not stuck in DFU mode. Booting to stock works, so does edl and twrp. But twrp only without using disemmcwp
I would try using older twrp. I've encountered this before but usually a reboot fixes it. I have not gone to twrp 3.1 yet, i think 3.0.4 was the one before.
lafester said:
I would try using older twrp. I've encountered this before but usually a reboot fixes it. I have not gone to twrp 3.1 yet, i think 3.0.4 was the one before.
Click to expand...
Click to collapse
Tried it with TWRP 3.04-1 and it's the same result.
Reboot diseemcwp -> recovery gets replaced by stock recovery after reboot
Reboot emmcwpenab -> recovery gets not replaced
In both cases I am unable to boot with a modified system or kernel.
Seems like the write protection is screwed up
Cyb3rzombi3 said:
Tried it with TWRP 3.04-1 and it's the same result.
Reboot diseemcwp -> recovery gets replaced by stock recovery after reboot
Reboot emmcwpenab -> recovery gets not replaced
In both cases I am unable to boot with a modified system or kernel.
Seems like the write protection is screwed up
Click to expand...
Click to collapse
If you disable write protection you inadvertently end up tripping dm-verity, which causes the device not to boot (security feature).
The reason you feel that disabling system write protection through TWRP causes TWRP to get overwritten by the stock recovery, could be because of the reboot rather than anything else.
I.e. When you install the stock system and reboot, the system overwrites the recovery partition, installing the stock recovery.
My suggestion:
- Make a backup.
- Wipe dalvik cache, cache, system, and data through recovery (under Wipe-> Advanced Wipe).
- Check that the filesystem of the partitions are ext4 (through the "file system" button under Wipe->Advanced Wipe menu), and change them if necessary.
- Reboot recovery.
- Don't swipe to allow system modifications.
- Install the stock bootstack, stock system (I'm assuming that you are using DrakenFX's image zips), and reboot.
- If it fails to install, just reboot recovery, and try to install once again.
Let me know if this works for you.
Erahgon said:
If you disable write protection you inadvertently end up tripping dm-verity, which causes the device not to boot (security feature).
The reason you feel that disabling system write protection through TWRP causes TWRP to get overwritten by the stock recovery, could be because of the reboot rather than anything else.
I.e. When you install the stock system and reboot, the system overwrites the recovery partition, installing the stock recovery.
My suggestion:
- Make a backup.
- Wipe dalvik cache, cache, system, and data through recovery (under Wipe-> Advanced Wipe).
- Check that the filesystem of the partitions are ext4 (through the "file system" button under Wipe->Advanced Wipe menu), and change them if necessary.
- Reboot recovery.
- Don't swipe to allow system modifications.
- Install the stock bootstack, stock system (I'm assuming that you are using DrakenFX's image zips), and reboot.
- If it fails to install, just reboot recovery, and try to install once again.
Let me know if this works for you.
Click to expand...
Click to collapse
Already did those steps but instead of using DrakenFX's files I used the official stock zip.
Shouldn't make a difference right?
Gonna try it once more...
Edit:
I'm stock now, TWRP installed without allowing system modifications.
Edit2:
Just rebootet and the recovery is gone again. This happened after I dlashed the recovery again after reverting to stock.
Edit3:
So what I tried so far after reverting to stock after each fail:
- flash SuperSU 2.65 -> unable to boot
- flash SuperSU 2.97 -> unable to boot
- flash Magisk 11.6 -> boot successful, Magiks installed and showing root but unable to request root permissions
- flash latest Los -> unable to boot
- flash latest RR -> unable to boot
- flash latest tool to disable dm-verity (from TWRP thread: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/) -> unable to boot
- flash AX7 R1 -> unable to reboot
Did the above steps with allowing system modifications and without.
Same for rebooting with disemmcwp and reformatiing partitions.
Tried using the universal bootloader from Los thread and still wasn't able to boot except using the stock rom.
I'm really out of ideads what I could try next.
Recovery seems to stick for now.
Could it be that the problem is not dm-verity but something else?
When I rooted the device I encountered no problem with that security mechanism. Custom roms and kernels worked as well without ever having to worry abou that.
Finally managed to boot into RR!
Here is what I did:
1. Went back to B10
2. Relocked bootloader
3. Booted into system -> developer settings -> Oem Unlock
4. Unlocked bootloader
5. Flashed recovery through fastboot
6. Booted directly into TWRP (when I did a restart it was overwritten immediately that's why I booted directly into it one the second try)
7. Allowed system modifications inside TWRP and flashed SuperSU 2.65
8. Successfully booted into system and had root
9. Flashed Universal Bootloader and Modem from Los thread
10. Flashed RR + Gapps
I really don't know which step the crucial one was but I hope if someone else manages to get into the same situation as I did those steps will help.
Thank you guys for helping me out
Hi!
I have a A2107G and unlocked it, coming from B04.
Everything worked so far, but I have messed around with bootstack/modem and now I am struggling.
I flashed a new ROM with TWRP (different versions) and the ROM (doesn't matter which one) is stuck in booting animation.
What can I do to bring it back to life?
Also another question: After switching on, directly after the ZTE logo coming up, a black sceen with some infos coming up and stay there for 5 secs.
Is there a way to get rid of this
Sui77 said:
Hi!
I have a A2107G and unlocked it, coming from B04.
Everything worked so far, but I have messed around with bootstack/modem and now I am struggling.
I flashed a new ROM with TWRP (different versions) and the ROM (doesn't matter which one) is stuck in booting animation.
What can I do to bring it back to life?
Also another question: After switching on, directly after the ZTE logo coming up, a black sceen with some infos coming up and stay there for 5 secs.
Is there a way to get rid of this
Click to expand...
Click to collapse
Do you have twrp? If yes, flash stock rom.
WesTD said:
Do you have twrp? If yes, flash stock rom.
Click to expand...
Click to collapse
Yes, I have TWRP.
So i should flash a stock image and start over from scratch (with rooting, ...)
Is the posted screen normal?
Sui77 said:
Yes, I have TWRP.
So i should flash a stock image and start over from scratch (with rooting, ...)
Is the posted screen normal?
Click to expand...
Click to collapse
Yes it is normal. It means you've unlocked bootloader.
Flash stock rom zip. There are some guides.
WesTD said:
Yes it is normal. It means you've unlocked bootloader.
Flash stock rom zip. There are some guides.
Click to expand...
Click to collapse
THX.
Will do so.
Which ROM do you prefer? CarbonRom? LOS?
How do i get the system partition r/w?
I think I screwed up the phone when i tried to make it writable?
Sui77 said:
THX.
Will do so.
Which ROM do you prefer? CarbonRom? LOS?
How do i get the system partition r/w?
I think I screwed up the phone when i tried to make it writable?
Click to expand...
Click to collapse
I use aosp bases.
Sui77 said:
THX.
Will do so.
Which ROM do you prefer? CarbonRom? LOS?
How do i get the system partition r/w?
I think I screwed up the phone when i tried to make it writable?
Click to expand...
Click to collapse
Heh. I don't know if there are flashable stock zips for the A2017G, the way I know of is flashing the stock recovery and using an official zip. But you shouldn't go back to stock if you want to use custom ROMs. Try this:
-Get an SD card, put
~ a custom ROM (RR, LOS,NucleaROM (i prefer NucleaROM, just sayin)),
~a Magisk 13.3 zip or SuperSU 2.82 zip,
~an OpenGApps zip (I use pico), arm64,
~a TWRP 3.1.1-0.img and
~A2017X Universal Bootloader and A2017G modem.
-Wipe system, data, cache and dalvik
-Install the Universal Bootloader, then the Modem, then the ROM and last the GApps and magisk/SuperSU
-If you had something important on the internal storage put it on the SD with the File manager under Advanced
-Go to Wipe -> Format data -> type Yes. This will get rid of the possible encryption from the stock ROM, but it will wipe your internal storage too.
-Reboot to system
You can use the 5 seconds screen to get to TWRP with the Volume buttons. Pretty handy I guess. There's a zip out there that gets rid of that screen, but you risk black-screening your phone with what seems to be no immediate fix (you'd be looking at an RMA)
So, after you use the phone and open TWRP again, you'll have an old version of it (3.0.1N-0 or sth). So go to Install, choose Install image, and select the TWRP 3.1.1-0.img on your SDcard. Then Reboot -> reboot to recovery and you can do whatever you want.
Choose an username... said:
Heh. I don't know if there are flashable stock zips for the A2017G, the way I know of is flashing the stock recovery and using an official zip. But you shouldn't go back to stock if you want to use custom ROMs. Try this:
-Get an SD card, put
~ a custom ROM (RR, LOS,NucleaROM (i prefer NucleaROM, just sayin)),
~a Magisk 13.3 zip or SuperSU 2.82 zip,
~an OpenGApps zip (I use pico), arm64,
~a TWRP 3.1.1-0.img and
~A2017X Universal Bootloader and A2017G modem.
-Wipe system, data, cache and dalvik
-Install the Universal Bootloader, then the Modem, then the ROM and last the GApps and magisk/SuperSU
-If you had something important on the internal storage put it on the SD with the File manager under Advanced
-Go to Wipe -> Format data -> type Yes. This will get rid of the possible encryption from the stock ROM, but it will wipe your internal storage too.
-Reboot to system
You can use the 5 seconds screen to get to TWRP with the Volume buttons. Pretty handy I guess. There's a zip out there that gets rid of that screen, but you risk black-screening your phone with what seems to be no immediate fix (you'd be looking at an RMA)
So, after you use the phone and open TWRP again, you'll have an old version of it (3.0.1N-0 or sth). So go to Install, choose Install image, and select the TWRP 3.1.1-0.img on your SDcard. Then Reboot -> reboot to recovery and you can do whatever you want.
Click to expand...
Click to collapse
Hi!
Thanks for your help and the time you spent on my problem.
I have tried all that stuff already, but maybe not in exact that order. Will try it this evening.
In case i will be able to bring it back to life, I have 2 questions, pls:
1: You mentioned the 5sec-screen and a zip to get rid of it.
Where could I find it (not seen yet) and how do i get into fastboot, when I skip this screen?
2: When I setted up my Axon with a Custom Rom and SU and everything was working as it should do, I was not able to write to /system (or deleting something in system/apps)
How do I get rid of this restriction? I think I have found an instruction once, but I failed and afterwards my device was stuck in animation.
orry for bothering, but the Axon really drive me nuts. Never had such a hassle with my Nexus
Sui77 said:
Hi!
Thanks for your help and the time you spent on my problem.
I have tried all that stuff already, but maybe not in exact that order. Will try it this evening.
In case i will be able to bring it back to life, I have 2 questions, pls:
1: You mentioned the 5sec-screen and a zip to get rid of it.
Where could I find it (not seen yet) and how do i get into fastboot, when I skip this screen?
2: When I setted up my Axon with a Custom Rom and SU and everything was working as it should do, I was not able to write to /system (or deleting something in system/apps)
How do I get rid of this restriction? I think I have found an instruction once, but I failed and afterwards my device was stuck in animation.
orry for bothering, but the Axon really drive me nuts. Never had such a hassle with my Nexus
Click to expand...
Click to collapse
Which file manager you are using?
I'm using Root Explorer and no problem. Be sure you allow to root permission
WesTD said:
Which file manager you are using?
I'm using Root Explorer and no problem. Be sure you allow to root permission
Click to expand...
Click to collapse
Also Root Explorer, root granted.
Sui77 said:
Also Root Explorer, root granted.
Click to expand...
Click to collapse
Can you just leave the 5 sec screen alone? You can kill your phone, and there doesn't seem to be anything you can do really.
If you're insistent, you can find it under Themes Apps and Mods, called "We remove the inscription that the bootloader is unlocked" made by NFound1.
And about the restriction to modify the system, connect your phone to a PC with ADB, fire up ADB and configure it (USB debugging, ADB over network if you have the option, permit the connection) and issue 'adb reboot disemmcwp' (disable emmc write protection, that is. Write it just like that or your phone will reboot and you will still have the protection active).
The phone has its difficulties and all but it's easy to work with once you get the hang of it. And, you know, your big cores don't just die all of a sudden, which is a good thing!
Choose an username... said:
Heh. I don't know if there are flashable stock zips for the A2017G, the way I know of is flashing the stock recovery and using an official zip. But you shouldn't go back to stock if you want to use custom ROMs. Try this:
-Get an SD card, put
~ a custom ROM (RR, LOS,NucleaROM (i prefer NucleaROM, just sayin)),
~a Magisk 13.3 zip or SuperSU 2.82 zip,
~an OpenGApps zip (I use pico), arm64,
~a TWRP 3.1.1-0.img and
~A2017X Universal Bootloader and A2017G modem.
-Wipe system, data, cache and dalvik
-Install the Universal Bootloader, then the Modem, then the ROM and last the GApps and magisk/SuperSU
-If you had something important on the internal storage put it on the SD with the File manager under Advanced
-Go to Wipe -> Format data -> type Yes. This will get rid of the possible encryption from the stock ROM, but it will wipe your internal storage too.
-Reboot to system
You can use the 5 seconds screen to get to TWRP with the Volume buttons. Pretty handy I guess. There's a zip out there that gets rid of that screen, but you risk black-screening your phone with what seems to be no immediate fix (you'd be looking at an RMA)
So, after you use the phone and open TWRP again, you'll have an old version of it (3.0.1N-0 or sth). So go to Install, choose Install image, and select the TWRP 3.1.1-0.img on your SDcard. Then Reboot -> reboot to recovery and you can do whatever you want.
Click to expand...
Click to collapse
Tried exactly the steps you descriped, but no luck ---- still stuck in animation
Will try it tomorrow with Magist.
How can I go back to total stock.
Tried anything I found on xda, but no luck.
When I flash the ZTE B05 zip, I don't even get the boot animation.
Sui77 said:
Tried exactly the steps you descriped, but no luck ---- still stuck in animation
Will try it tomorrow with Magist.
How can I go back to total stock.
Tried anything I found on xda, but no luck.
When I flash the ZTE B05 zip, I don't even get the boot animation.
Click to expand...
Click to collapse
How do you flash the B05 zip? Did you try to flash the official zip?? lol
Follow my guide on the Guides section ("back to stock safely" or sth), it works...
Choose an username... said:
How do you flash the B05 zip? Did you try to flash the official zip?? lol
Follow my guide on the Guides section ("back to stock safely" or sth), it works...
Click to expand...
Click to collapse
I tired to flash a B5 an B5 bootstack with TWRP 3.1.1 -> not able to boot
Then i flashed, according to your guide, the stock recovery and now the device seems to be really bricked.
After the ZTE logo a lying robot appears for half a second and after that, the device is dead.
Can't boot into TWRP, can't use adb, EDL, ...
Ok, managed to get back TWRP.
But I really don't know how so solve my issue of how to come back to stock :crying:
Flashed a B05 stock (zip) and B05 bootstack and Magist....stuck in boot animation (AXON picture collage).
Fu....
Update:
Managed to flash this files:
ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip
ZTE_A2017GV1.0.0B09_StockSystem_by_tron1.zip
TWRP 3.1.1.0
Phone is up and running with A2017GV1.0.0B09
How can I upgrade to the B05 bootstack and the B05 ROM
Sui77 said:
Update:
Managed to flash this files:
ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip
ZTE_A2017GV1.0.0B09_StockSystem_by_tron1.zip
TWRP 3.1.1.0
Phone is up and running with A2017GV1.0.0B09
How can I upgrade to the B05 bootstack and the B05 ROM
Click to expand...
Click to collapse
to go back to stock, download the full zip of any version you want, and download stock recvovery from b08, you have flashed it.
from twrp, format data, and try to boot, if you cannot, reflash b09 recovery from twrp, select image and the recovery you download, then go to stock recovery and update from sdcard. it allways work for me, if you stuck in boot animation again, reboot recovery and wipe data.
after you succesfully boot, reboot edl, and reflash twrp, the version you were using before witn axon7tool, thats all
Sui77 said:
Update:
Managed to flash this files:
ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip
ZTE_A2017GV1.0.0B09_StockSystem_by_tron1.zip
TWRP 3.1.1.0
Phone is up and running with A2017GV1.0.0B09
How can I upgrade to the B05 bootstack and the B05 ROM
Click to expand...
Click to collapse
Just follow my guide for that. If you flash the B04 recovery (the one i provided) you shouldn't have any trouble
Managed to flash the B05 and phone is up and running.
Made a backup by using TWRP 3.1.1.0 and flashed CarbonRom, which also worked nicely.
However, I'm not able to flash LOS by using the B05 bootstack.
I'm too dumb for this phone
Sui77 said:
Managed to flash the B05 and phone is up and running.
Made a backup by using TWRP 3.1.1.0 and flashed CarbonRom, which also worked nicely.
However, I'm not able to flash LOS by using the B05 bootstack.
I'm too dumb for this phone
Click to expand...
Click to collapse
What B05 bootstack? You have to use the universal bootstack and the A2017G modem file...
Both are on the LOS thread. It seems weird that carbonROM would even boot without the universal bootstack though
Hello Guys it´s me again. (i know im annoying )
Well, i did a Factory Reset in dotOS and it Rebooted into TWRP.
However, Normally a Phone would then Perform the Action in the Recovery but in this Case it did not do it. So i Reflashed the Rom.
After that it Rebooted into TWRP again. I Tried to Access the Bootloader with Vol Down + Power. That also Booted into TWRP. After that i Selected Bootloader in the TWRP Reboot Options. That Booted the Phone into the Mode where i Flashed the Recovery but it did not Give me the Options like META MODE, FACTORY MODE etc, when i tapped the Volume Buttons. Only a Black Background with White text Saying :
> FASTBOOT mode...
> device unlocked
I Tried to Restore my Stock TWRP Backup but that did not Solve the Issue. I also tried to Reflash dotOS but same issue.
What else Can i do to get this fixed ? I never had a Problem Like this on any Sony or Samsung Device i tinkered with. Thats why im asking that much.
@Marc_Xperia Do not forget to install no-verity-opt-encrypt zip file or simple disable *system verifier* in kernel ramdisk.
TheHitMan said:
@Marc_Xperia Do not forget to install no-verity-opt-encrypt zip file or simple disable *system verifier* in kernel ramdisk.
Click to expand...
Click to collapse
I Tried that but still no luck. Might Revert to stock and try it that why. If i can find the VCOM Driver...
Marc_Xperia said:
Hello Guys it´s me again. (i know im annoying )
Well, i did a Factory Reset in dotOS and it Rebooted into TWRP.
However, Normally a Phone would then Perform the Action in the Recovery but in this Case it did not do it. So i Reflashed the Rom.
After that it Rebooted into TWRP again. I Tried to Access the Bootloader with Vol Down + Power. That also Booted into TWRP. After that i Selected Bootloader in the TWRP Reboot Options. That Booted the Phone into the Mode where i Flashed the Recovery but it did not Give me the Options like META MODE, FACTORY MODE etc, when i tapped the Volume Buttons. Only a Black Background with White text Saying :
> FASTBOOT mode...
> device unlocked
I Tried to Restore my Stock TWRP Backup but that did not Solve the Issue. I also tried to Reflash dotOS but same issue.
What else Can i do to get this fixed ? I never had a Problem Like this on any Sony or Samsung Device i tinkered with. Thats why im asking that much.
Click to expand...
Click to collapse
It's very simple
-boot into recovery
-wipe
-advanced wipe
-clear / format cache & dalvik
-reboot _choose reboot recovery
-select mtp file transfer mode in twrp
-push LATEST* magisk zip
-push clean copy of dotOs
-then do FULL WIPE (all) but not your sd or internal sd/data
-install first dotOs zip
-install magisk zip
-wipe cache
-reboot
* If you fail check what is selected under the mount section & report back
If problem persists flash an older version of recovery using SPflashtools and then older version of dotOs with magisk
_do full wipe first
#some new recoveries had errors so make sure you are running ABSOLUTE latest or OLDEST version of twrp
# I haven't tried the last or latest version of dotOs yes ( older versions worked 100%)
KevMetal said:
It's very simple
-boot into recovery
-wipe
-advanced wipe
-clear / format cache & dalvik
-reboot _choose reboot recovery
-select mtp file transfer mode in twrp
-push LATEST* magisk zip
-push clean copy of dotOs
-then do FULL WIPE (all) but not your sd or internal sd/data
-install first dotOs zip
-install magisk zip
-wipe cache
-reboot
* If you fail check what is selected under the mount section & report back
If problem persists flash an older version of recovery using SPflashtools and then older version of dotOs with magisk
_do full wipe first
#some new recoveries had errors so make sure you are running ABSOLUTE latest or OLDEST version of twrp
# I haven't tried the last or latest version of dotOs yes ( older versions worked 100%)
Click to expand...
Click to collapse
Do you have Some Links on the ABSOULTE latest or OLDEST Version of TWRP ? I dont trust the one i Have anymore.
I Used this one : https://androidfilehost.com/?fid=890129502657592740
Marc_Xperia said:
Do you have Some Links on the ABSOULTE latest or OLDEST Version of TWRP ? I dont trust the one i Have anymore.
I Used this one : https://androidfilehost.com/?fid=890129502657592740
Click to expand...
Click to collapse
Download this tool .
https://www.androidfilehost.com/?fid=817550096634801704
Extract the .rar
Inside the folder there is recovery by XNlogos with zero errors
This tool can also inject recovery using fastboot or unlock bootloader in automated manner & flash custom boot( with verity encrypt DISABLED)
I've got a SM-G950F, and succesfully flashed TWRP on it.
Wiped /data, after that i flashed dm-verity and force encryption disabler, everything was ok until the first boot into the system.
It booted up, and immediately after that i turned off the phone and booted into TWRP, and for some reason it couldnt mount /data again.
The tutorial i have followed:
Thanks for the tutorial to: jesec
Part 1 - HOW-TO FLASH TWRP:
1. In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
2. Go to Settings -> Developer options and enable OEM Unlock option.
3. Download and Install Samsung Mobile Phones Drivers.
- Option 1: Download and Install Smart Switch for PC.
- Option 2: Download and Install standalone driver package.
4. Download and extract Odin (Samsung's Flash Tool) to your computer.
5. Download a .tar image of TWRP.
6. Reboot your device to download mode.
- Hold [VOLUME DOWN] + [BIXBY] + [POWER] for approx. 15 seconds.
- Read the warning carefully.
- If you agree, press [VOLUME UP] to get into Download mode. If you don't agree, STOP.
7. Open Odin and place that TWRP tar file in the [AP] slot.
8. Connect your phone.
9. Hold [VOLUME UP] + [BIXBY] + [POWER] on your phone and then press start on Odin.
10. Wait for the phone to reboot. DO NOT release [VOLUME UP] + [BIXBY] + [POWER] or you may not reboot into TWRP.
Part 2 - HOW-TO INITIALIZE TWRP: (for new phones)
1. If you completed Part 1 successfully, you should be in TWRP now. At this point, you will reach the screen asking you if you want to allow system modifications.
2. Select "Keep /system RO". (Don't swipe right or you may not be able to boot into system if you failed to complete next steps. However, you can swipe right to allow modifications if you are confident that you can complete next steps.)
3. Go to "Wipe" menu of TWRP and you will find "Format Data". Press "Format Data" and type "yes" to continue.
4. Go to "Reboot" menu and Press "Recovery" to reboot TWRP.
5. Download the latest dm-verity and force encryption disabler zip on your computer.
6. Transfer the zip to your phone.
- Option 1: MTP: Connect your phone with computer and just copy the zip to internal storage. (similar to how you transfer files when in system.)
- Option 2: ADB: Connect your phone with computer and run command "adb push /path/to/zip /sdcard/".
- Option 3: External SD: Copy the zip to an external SD and then insert the card to your phone.
7. Go to "Install" menu of TWRP and flash the zip.
TWRP is initialized and fully functional at this stage. Now you can either reboot into system or root, flash custom ROMs via TWRP.
Part 3 - HOW-TO ROOT:
1. Download the flashable zip.
- Option 1: Magisk
- Option 2: SuperSU (untested)
2. Transfer the zip to your phone.
3. Go to "Install" menu of TWRP and flash the zip.
Part 3a - HOW-TO FLASH CUSTOM ROMS:
1. Download the flashable zip.
2. Transfer the zip to your phone.
3. Go to "Install" menu of TWRP and flash the zip.
Simple.
Click to expand...
Click to collapse
Before the 1st boot i even rooted the device, that remained after the first boot, but no /data mount.
After the 5th try, i gave up.
What could be the problem, or is this normal on this phone?
Are you using latest twrp version 3.2.3.2
I'm using 3.2.1.0
kristof889 said:
I'm using 3.2.1.0
Click to expand...
Click to collapse
Use latest twrp 3.2.3.2 should have data mount and quota issues fixed.
You can flash the .Img file through twrp or flash the .img.tar file with Odin.
After flashing reboot straight into twrp and repeat part 2 of the guide you quoted.
I would be interested to know also if in download mode if you have a line in there saying rmm state?
Twrp for s8 exynos
https://dl.twrp.me/dreamlte/
Installed the 3.2.3.2 version, but nothing has changed. after the first boot into system, TWRP says cant mount /data..
I dont have anything like rmm state in download mode.
kristof889 said:
Installed the 3.2.3.2 version, but nothing has changed. after the first boot into system, TWRP says cant mount /data..
I dont have anything like rmm state in download mode.
Click to expand...
Click to collapse
I am assuming you followed the instructions that you quoted in your first post.(mainly part 2) after flashing twrp
Did you format data in twrp - not wipe - this is needed to decrypt your phone.
Rebooted back into twrp.
Did you flash the no verity opt zip (version 6) - this will disable re encryption of your phone when booting back into system.
This should all be done before booting back into system otherwise your phone will re encrypt itself.
I am assuming you followed the instructions that you quoted in your first post.(mainly part 2) after flashing twrp
Did you format data in twrp - not wipe - this is needed to decrypt your phone.
Rebooted back into twrp.
Did you flash the no verity opt zip (version 6) - this will disable re encryption of your phone when booting back into system.
This should all be done before booting back into system otherwise your phone will re encrypt itself.
Click to expand...
Click to collapse
I formatted data, not just wiped it.
I have installed the no verity opt, the latest version.
Even after these, my phone reencrypted itself.
kristof889 said:
I formatted data, not just wiped it.
I have installed the no verity opt, the latest version.
Even after these, my phone reencrypted itself.
Click to expand...
Click to collapse
When do the errors occur ie: during backup,restore,flashing something.
When first starting twrp did you swipe to allow modifications or did you leave it as read only.
You mean, the data mount error?
If yes, immediately after the 2nd boot into TWRP, after the first boot into system. Before i do anything in twrp, i check the log (with the button on the lower right) and it creates a bunch of errors, all in contact with the data partition.
So i can even do a proper backup.
If i flash any zip, upon the next boot into system it says something like verify failed, cannot reboot your phone and it gives a button wich used to restore the phone from recovery, but now i cant even do that bcoz it cant mount /data and thus can restore the phone.
kristof889 said:
You mean, the data mount error?
If yes, immediately after the 2nd boot into TWRP, after the first boot into system. Before i do anything in twrp, i check the log (with the button on the lower right) and it creates a bunch of errors, all in contact with the data partition.
So i can even do a proper backup.
If i flash any zip, upon the next boot into system it says something like verify failed, cannot reboot your phone and it gives a button wich used to restore the phone from recovery, but now i cant even do that bcoz it cant mount /data and thus can restore the phone.
Click to expand...
Click to collapse
Still sounds like you device is still encrypted.
Doing a factory reset with twrp should work to restore your phone or at worst you can re-flash your firmware.
If you can in twrp FORMAT data again and flash the no verity zip use version 6 zip file
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
I would be curious to know in twrp in the mount menu what options are ticked as well.
After the fresh flash, it was not encrypted because i could access the internal storage, and data was mounted.
Now in TWRP system(read only), cache and dalvik is mounted, and internal storage says 0MB
kristof889 said:
After the fresh flash, it was not encrypted because i could access the internal storage, and data was mounted.
Now in TWRP system(read only), cache and dalvik is mounted, and internal storage says 0MB
Click to expand...
Click to collapse
What Android version are you on?
When you flashed twrp it should have asked you whether or not to ' swipe to allow modifications ' did you swipe to allow or not.
In the mount menu of twrp I have ticked/checked data,cache,SD card the option at the bottom to allow read only I have ticked - this does not stop me from doing backups but does stop me from restoring (data mount error ) so you can leave it unticked.
I would.like to know your steps for twrp installation (not the one you quoted in first post) as I screwed up when I first tried.
I attached the software information bellow.
I have not swiped to allow for system modifications
First steps were the followimg:
Install .tra with odin
Immediately reboot to twrp
No swipe for system modifications
Format data
Flash no dm verity v6
(Flash magisk)
Reboot to system
kristof889 said:
First steps were the followimg:
Install .tra with odin
Immediately reboot to twrp
No swipe for system modifications
Format data
Flash no dm verity v6
(Flash magisk)
Reboot to system
Click to expand...
Click to collapse
Ok basically you have missed a step as far as I can see
(When I did mine I did swipe to allow modifications )
After you have formated data you will need to reboot back into twrp ( use reboot menu in twrp )
Then flash the no verity zip and magisk
If using magisk I would try the latest version 18 it's working ok for me.
Then boot into system to see if everything ok
Then reboot into twrp and see if the data mount issue is fixed.
spawnlives said:
Ok basically you have missed a step as far as I can see
(When I did mine I did swipe to allow modifications )
After you have formated data you will need to reboot back into twrp ( use reboot menu in twrp )
Then flash the no verity zip and magisk
If using magisk I would try the latest version 18 it's working ok for me.
Then boot into system to see if everything ok
Then reboot into twrp and see if the data mount issue is fixed.
Click to expand...
Click to collapse
Thank you for your advice. I will try it in the following days and will post the result.
I fixed this by flashing Renovate ICE's ROM and selecting the TWRP included in the AROMA installer.
Can access storage on TWRP now with no issues.
CoreyOS said:
I fixed this by flashing Renovate ICE's ROM and selecting the TWRP included in the AROMA installer.
Can access storage on TWRP now with no issues.
Click to expand...
Click to collapse
But i want to use the stock rom.
Maybe if i flash Renovate rom and after that again the stock?
kristof889 said:
But i want to use the stock rom.
Maybe if i flash Renovate rom and after that again the stock?
Click to expand...
Click to collapse
Why stock???
It pretty much is stock, just you have full control over the apps preinstalled and you can change colours of various UI elements.
It's just easier to flash a zip than it is to flash via ODIN, then flash TWRP and keep trying over and over to get this result when I know this rom works fine with CTSprofile.
You will only need to flash TWRP once and copy the rom to your phone.
The rest is magic (AROMA)
I haven't really had to mess with anything and have just installed and used the HSBC banking app as if it were an official phone. (ROOTED and custom ROM and Recovery)
One extra step you could take is to use Magisk hide and point it to the app you want to hide root from.
CoreyOS said:
Why stock???
It pretty much is stock, just you have full control over the apps preinstalled and you can change colours of various UI elements.
It's just easier to flash a zip than it is to flash via ODIN, then flash TWRP and keep trying over and over to get this result when I know this rom works fine with CTSprofile.
You will only need to flash TWRP once and copy the rom to your phone.
The rest is magic (AROMA)
I haven't really had to mess with anything and have just installed and used the HSBC banking app as if it were an official phone. (ROOTED and custom ROM and Recovery)
One extra step you could take is to use Magisk hide and point it to the app you want to hide root from.
Click to expand...
Click to collapse
So on that rom i can use s health and all knox based apps like normal?
If yes, i will try it, it looks very nice
I have a J7 Pro (J730G/DS) and I was wondering if its possible to install ANY rom that is 64bit as my CPU does indeed support 64bit but my OS is only 32.
I want to use this smartphone as an emulation device but most modern emulators such as Citra and Dolphin require 64bit Android
if its possible, can anyone link a guide on how to change my rom to a 64bit one?
I recommend installing a custom Treble rom, as they are all arm64.
For that I recommend first to create a Vendor partition(with recovery) using the file Exynos7870_CreateVendor_2.0.zip(download from here https://forum.xda-developers.com/galaxy-j7-2017/development/treble-project-treblue-j710x-t4098875)
Then recommend you to install this ROM: https://forum.xda-developers.com/galaxy-j7-2017/development/unofficial-crdroid-6-7-t4119505
And you will have a 64 bit OS.
death.by.confusion said:
I recommend installing a custom Treble rom, as they are all arm64.
For that I recommend first to create a Vendor partition(with recovery) using the file Exynos7870_CreateVendor_2.0.zip(download from here https://forum.xda-developers.com/galaxy-j7-2017/development/treble-project-treblue-j710x-t4098875)
Then recommend you to install this ROM: https://forum.xda-developers.com/galaxy-j7-2017/development/unofficial-crdroid-6-7-t4119505
And you will have a 64 bit OS.
Click to expand...
Click to collapse
Thank you for the help, do you maybe have a guide for me? never installed a custom ROM before
[GUIDE][J730X] A beginer's guide to installing custom ROM on Samsung Galaxy J7 2017
In order to install a custom ROM, the general steps are to: Unlock bootloader, Install custom recovery, make a backup of your current stock ROM, and then go to install a custom ROM.
NOTE: It is good idea to note your software version and your baseband version right now(enter *#1234# on dial pad)
This is so you can find your stock ROM on https://www.sammobile.com/ and flash with Odin tool.
Unlock bootloader
In our samsung phone it is very easy to unlock the bootloader. All you have to do is go to Developer options and enable OEM Unlock(something similar to the image below)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To enable Developer options, you go in About phone, and press on the field Build Number multiple times(something similar to the image below)
Install custom recovery
There are multiple choices for custom recovery for our samsung phone. I recommend to install TWRP 3.3.0(link here https://github.com/ananjaser1211/android_device_samsung_jxy17lte/releases)
You need samsung USB drivers(link here https://developer.samsung.com/mobile/android-usb-driver.html and the
the Odin tool(for flashing the recovery)(link here https://odinflashtool.com/download/odin3-v3-13-1/
1. Turn your phone in to Download mode. For that, first power off your phone, and then hold POWER button together with volume DOWN and HOME button, then connect the phone with USB cable on the computer.
2. Open Odin tool
3. In the options tab, uncheck auto reboot
4. Select the custom recovery image in to AP field(the exact file name of recovery from link is TWRP-3.3.0-j7y17lte-20190417.tar
5. Start flashing.
6. Now, hold POWER, volume DOWN, volume UP and HOME button together until your screen on the phone goes back, then instantly hold POWER, Volume UP and HOME button together, so you boot in to the installed recovery.
7. You should see the installed recovery working.
Set up internal storage so the recovery works properly
Warning: This operation WILL DELETE EVERYTHING ON YOUR INTERNAL STORAGE. COPY YOUR FILES ELSEWHERE.
Use your installed recovery to wipe the internal storage, so it becomes available for usage.
Select the option Wipe, then Format data, and then confirm the operation.
No you should be able to use your recovery for other operations.
Make a backup of your current stock ROM
Use your installed recovery to make a backup of your current stock ROM.
Select the option Backup, and then select all partitions, then confirm the backup operation.
After this, don't forget to copy the backup in your computer. For that, you can plug your phone to PC while you are in recovery, and then you can just copy the backup. The backup is stored in the folder named TWRP.
Install a custom ROM
You can use your recovery to install a custom ROM.
The general steps for installing a custom ROM are:
1. Wipe the partitions Data, Dalvik/Cache, System
2. Download the ROM that is a zip file and store the zip file in phone(either internal memory or SD CARD)
3. Use the install option in recovery to install the ROM
4. Reboot the phone.
Install a custom TREBLE ROM
Treble ROMS are different than regular custom ROMS, because they need the phone to have an additional Vendor partition.
To create a Vendor partition, use your recovery to install the zip Exynos7870_CreateVendor_2.0.zip(download from here https://forum.xda-developers.com/galaxy-j7-2017/development/treble-project-treblue-j710x-t4098875) and reboot your phone in to recovery so the recovery detects the new vendor partition.
Then you need to flash a particular vendor(Either Project Treblue, or H-VENDOR).
After that, you can wipe the partitions(Data, Dalvik/Cache, System) and flash the custom TREBLE ROM.
I recommend to flash this custom TREBLE ROM: crDROID https://forum.xda-developers.com/galaxy-j7-2017/development/unofficial-crdroid-6-7-t4119505
To flash crDROID, first install the zip Exynos7870_CreateVendor_2.0.zip, reboot your phone in to recovery, and then flash crDROID(note that the vendor is included in crDROID).
Revert to stock ROM
You can use Odin tool to flash the stock rom. First find your stock rom on https://www.sammobile.com/, unpack the downloaded ROM, and then use Odin tool to flash all the files(BL,AP,CP, CSC)
To revert to stock ROM using your recovery, first install the zip Exynos7870_RevertVendor_2.0.zip(link here https://forum.xda-developers.com/galaxy-j7-2017/development/treble-project-treblue-j710x-t4098875), reboot your phone in to recovery so the recovery detects that the vendor partition is gone, and then restore your previously created backup.
death.by.confusion said:
In order to install a custom ROM, the general steps are to: Unlock bootloader, Install custom recovery, make a backup of your current stock ROM, and then go to install a custom ROM.
NOTE: It is good idea to note your software version and your baseband version right now(enter *#1234# on dial pad)
This is so you can find your stock ROM on https://www.sammobile.com/ and flash with Odin tool.
Unlock bootloader
In our samsung phone it is very easy to unlock the bootloader. All you have to do is go to Developer options and enable OEM Unlock(something similar to the image below)
To enable Developer options, you go in About phone, and press on the field Build Number multiple times(something similar to the image below)
Install custom recovery
There are multiple choices for custom recovery for our samsung phone. I recommend to install TWRP 3.3.0(link here https://github.com/ananjaser1211/android_device_samsung_jxy17lte/releases)
You need samsung USB drivers(link here https://developer.samsung.com/mobile/android-usb-driver.html and the
the Odin tool(for flashing the recovery)(link here https://odinflashtool.com/download/odin3-v3-13-1/
1. Turn your phone in to Download mode. For that, first power off your phone, and then hold POWER button together with volume DOWN and HOME button, then connect the phone with USB cable on the computer.
2. Open Odin tool
3. In the options tab, uncheck auto reboot
4. Select the custom recovery image in to AP field(the exact file name of recovery from link is TWRP-3.3.0-j7y17lte-20190417.tar
5. Start flashing.
6. Now, hold POWER, volume DOWN, volume UP and HOME button together until your screen on the phone goes back, then instantly hold POWER, Volume UP and HOME button together, so you boot in to the installed recovery.
7. You should see the installed recovery working.
Set up internal storage so the recovery works properly
Warning: This operation WILL DELETE EVERYTHING ON YOUR INTERNAL STORAGE. COPY YOUR FILES ELSEWHERE.
Use your installed recovery to wipe the internal storage, so it becomes available for usage.
Select the option Wipe, then Format data, and then confirm the operation.
No you should be able to use your recovery for other operations.
Make a backup of your current stock ROM
Use your installed recovery to make a backup of your current stock ROM.
Select the option Backup, and then select all partitions, then confirm the backup operation.
After this, don't forget to copy the backup in your computer. For that, you can plug your phone to PC while you are in recovery, and then you can just copy the backup. The backup is stored in the folder named TWRP.
Install a custom ROM
You can use your recovery to install a custom ROM.
The general steps for installing a custom ROM are:
1. Wipe the partitions Data, Dalvik/Cache, System
2. Download the ROM that is a zip file and store the zip file in phone(either internal memory or SD CARD)
3. Use the install option in recovery to install the ROM
4. Reboot the phone.
Install a custom TREBLE ROM
Treble ROMS are different than regular custom ROMS, because they need the phone to have an additional Vendor partition.
To create a Vendor partition, use your recovery to install the zip Exynos7870_CreateVendor_2.0.zip(download from here https://forum.xda-developers.com/galaxy-j7-2017/development/treble-project-treblue-j710x-t4098875) and reboot your phone in to recovery so the recovery detects the new vendor partition.
Then you need to flash a particular vendor(Either Project Treblue, or H-VENDOR).
After that, you can wipe the partitions(Data, Dalvik/Cache, System) and flash the custom TREBLE ROM.
I recommend to flash this custom TREBLE ROM: crDROID https://forum.xda-developers.com/galaxy-j7-2017/development/unofficial-crdroid-6-7-t4119505
To flash crDROID, first install the zip Exynos7870_CreateVendor_2.0.zip, reboot your phone in to recovery, and then flash crDROID(note that the vendor is included in crDROID).
Revert to stock ROM
You can use Odin tool to flash the stock rom. First find your stock rom on https://www.sammobile.com/, unpack the downloaded ROM, and then use Odin tool to flash all the files(BL,AP,CP, CSC)
To revert to stock ROM using your recovery, first install the zip Exynos7870_RevertVendor_2.0.zip(link here https://forum.xda-developers.com/galaxy-j7-2017/development/treble-project-treblue-j710x-t4098875), reboot your phone in to recovery so the recovery detects that the vendor partition is gone, and then restore your previously created backup.
Click to expand...
Click to collapse
Thank you very much but I have a problem, when I try to install CreateVendor or crDroid I get an error in TWRP "failed to mount /preload (invalid argument)
any fix for that?
LidorTzruya said:
Thank you very much but I have a problem, when I try to install CreateVendor or crDroid I get an error in TWRP "failed to mount /preload (invalid argument)
any fix for that?
Click to expand...
Click to collapse
This is not an error that will break your phone. TWRP will install the ROM successfuly, so don't worry about the error. Since there is a Vendor partition, it is natural that the phone won't have a preload partition, so TWRP won't be able to mount it.
Now how is the ROM working?
death.by.confusion said:
This is not an error that will break your phone. TWRP will install the ROM successfuly, so don't worry about the error. Since there is a Vendor partition, it is natural that the phone won't have a preload partition, so TWRP won't be able to mount it.
Now how is the ROM working?
Click to expand...
Click to collapse
it works well! thank you! I tried installing GApps (ARM64, android 10, stock) and that just puts the phone into a bootloop, so I re-installed the rom. maybe you know what it happens?
LidorTzruya said:
it works well! thank you! I tried installing GApps (ARM64, android 10, stock) and that just puts the phone into a bootloop, so I re-installed the rom. maybe you know what it happens?
Click to expand...
Click to collapse
I don't use GAPPS, so i don't know what would be the problem.
I suggest you install pico package instead of the stock package.
If still not working, then I suggest you install bitgapps.
death.by.confusion said:
In order to install a custom ROM, the general steps are to: Unlock bootloader, Install custom recovery, make a backup of your current stock ROM, and then go to install a custom ROM.
NOTE: It is good idea to note your software version and your baseband version right now(enter *#1234# on dial pad)
This is so you can find your stock ROM on https://www.sammobile.com/ and flash with Odin tool.
Unlock bootloader
In our samsung phone it is very easy to unlock the bootloader. All you have to do is go to Developer options and enable OEM Unlock(something similar to the image below)
To enable Developer options, you go in About phone, and press on the field Build Number multiple times(something similar to the image below)
Install custom recovery
There are multiple choices for custom recovery for our samsung phone. I recommend to install TWRP 3.3.0(link here https://github.com/ananjaser1211/android_device_samsung_jxy17lte/releases)
You need samsung USB drivers(link here https://developer.samsung.com/mobile/android-usb-driver.html and the
the Odin tool(for flashing the recovery)(link here https://odinflashtool.com/download/odin3-v3-13-1/
1. Turn your phone in to Download mode. For that, first power off your phone, and then hold POWER button together with volume DOWN and HOME button, then connect the phone with USB cable on the computer.
2. Open Odin tool
3. In the options tab, uncheck auto reboot
4. Select the custom recovery image in to AP field(the exact file name of recovery from link is TWRP-3.3.0-j7y17lte-20190417.tar
5. Start flashing.
6. Now, hold POWER, volume DOWN, volume UP and HOME button together until your screen on the phone goes back, then instantly hold POWER, Volume UP and HOME button together, so you boot in to the installed recovery.
7. You should see the installed recovery working.
Set up internal storage so the recovery works properly
Warning: This operation WILL DELETE EVERYTHING ON YOUR INTERNAL STORAGE. COPY YOUR FILES ELSEWHERE.
Use your installed recovery to wipe the internal storage, so it becomes available for usage.
Select the option Wipe, then Format data, and then confirm the operation.
No you should be able to use your recovery for other operations.
Make a backup of your current stock ROM
Use your installed recovery to make a backup of your current stock ROM.
Select the option Backup, and then select all partitions, then confirm the backup operation.
After this, don't forget to copy the backup in your computer. For that, you can plug your phone to PC while you are in recovery, and then you can just copy the backup. The backup is stored in the folder named TWRP.
Install a custom ROM
You can use your recovery to install a custom ROM.
The general steps for installing a custom ROM are:
1. Wipe the partitions Data, Dalvik/Cache, System
2. Download the ROM that is a zip file and store the zip file in phone(either internal memory or SD CARD)
3. Use the install option in recovery to install the ROM
4. Reboot the phone.
Install a custom TREBLE ROM
Treble ROMS are different than regular custom ROMS, because they need the phone to have an additional Vendor partition.
To create a Vendor partition, use your recovery to install the zip Exynos7870_CreateVendor_2.0.zip(download from here https://forum.xda-developers.com/galaxy-j7-2017/development/treble-project-treblue-j710x-t4098875) and reboot your phone in to recovery so the recovery detects the new vendor partition.
Then you need to flash a particular vendor(Either Project Treblue, or H-VENDOR).
After that, you can wipe the partitions(Data, Dalvik/Cache, System) and flash the custom TREBLE ROM.
I recommend to flash this custom TREBLE ROM: crDROID https://forum.xda-developers.com/galaxy-j7-2017/development/unofficial-crdroid-6-7-t4119505
To flash crDROID, first install the zip Exynos7870_CreateVendor_2.0.zip, reboot your phone in to recovery, and then flash crDROID(note that the vendor is included in crDROID).
Revert to stock ROM
You can use Odin tool to flash the stock rom. First find your stock rom on https://www.sammobile.com/, unpack the downloaded ROM, and then use Odin tool to flash all the files(BL,AP,CP, CSC)
To revert to stock ROM using your recovery, first install the zip Exynos7870_RevertVendor_2.0.zip(link here https://forum.xda-developers.com/galaxy-j7-2017/development/treble-project-treblue-j710x-t4098875), reboot your phone in to recovery so the recovery detects that the vendor partition is gone, and then restore your previously created backup.
Click to expand...
Click to collapse
Hello sir, im just newbie about updating phone like this so i just follow your step above and now my phone going to CRDROID after SAMSUNG screen, is this ok or wrong ?? i still be able to use my phone but the problem is my sim card is not detected, and also i miss the part of revert stock rom, and when i try to revert stock rom my phone say there is no OS inside. Maybe you know what should i do sir ? at least my simcard detected and i have signal to do whatsapp and other else, thank you sir
death.by.confusion said:
In order to install a custom ROM, the general steps are to: Unlock bootloader, Install custom recovery, make a backup of your current stock ROM, and then go to install a custom ROM.
NOTE: It is good idea to note your software version and your baseband version right now(enter *#1234# on dial pad)
This is so you can find your stock ROM on https://www.sammobile.com/ and flash with Odin tool.
Unlock bootloader
In our samsung phone it is very easy to unlock the bootloader. All you have to do is go to Developer options and enable OEM Unlock(something similar to the image below)
To enable Developer options, you go in About phone, and press on the field Build Number multiple times(something similar to the image below)
Install custom recovery
There are multiple choices for custom recovery for our samsung phone. I recommend to install TWRP 3.3.0(link here https://github.com/ananjaser1211/android_device_samsung_jxy17lte/releases)
You need samsung USB drivers(link here https://developer.samsung.com/mobile/android-usb-driver.html and the
the Odin tool(for flashing the recovery)(link here https://odinflashtool.com/download/odin3-v3-13-1/
1. Turn your phone in to Download mode. For that, first power off your phone, and then hold POWER button together with volume DOWN and HOME button, then connect the phone with USB cable on the computer.
2. Open Odin tool
3. In the options tab, uncheck auto reboot
4. Select the custom recovery image in to AP field(the exact file name of recovery from link is TWRP-3.3.0-j7y17lte-20190417.tar
5. Start flashing.
6. Now, hold POWER, volume DOWN, volume UP and HOME button together until your screen on the phone goes back, then instantly hold POWER, Volume UP and HOME button together, so you boot in to the installed recovery.
7. You should see the installed recovery working.
Set up internal storage so the recovery works properly
Warning: This operation WILL DELETE EVERYTHING ON YOUR INTERNAL STORAGE. COPY YOUR FILES ELSEWHERE.
Use your installed recovery to wipe the internal storage, so it becomes available for usage.
Select the option Wipe, then Format data, and then confirm the operation.
No you should be able to use your recovery for other operations.
Make a backup of your current stock ROM
Use your installed recovery to make a backup of your current stock ROM.
Select the option Backup, and then select all partitions, then confirm the backup operation.
After this, don't forget to copy the backup in your computer. For that, you can plug your phone to PC while you are in recovery, and then you can just copy the backup. The backup is stored in the folder named TWRP.
Install a custom ROM
You can use your recovery to install a custom ROM.
The general steps for installing a custom ROM are:
1. Wipe the partitions Data, Dalvik/Cache, System
2. Download the ROM that is a zip file and store the zip file in phone(either internal memory or SD CARD)
3. Use the install option in recovery to install the ROM
4. Reboot the phone.
Install a custom TREBLE ROM
Treble ROMS are different than regular custom ROMS, because they need the phone to have an additional Vendor partition.
To create a Vendor partition, use your recovery to install the zip Exynos7870_CreateVendor_2.0.zip(download from here https://forum.xda-developers.com/galaxy-j7-2017/development/treble-project-treblue-j710x-t4098875) and reboot your phone in to recovery so the recovery detects the new vendor partition.
Then you need to flash a particular vendor(Either Project Treblue, or H-VENDOR).
After that, you can wipe the partitions(Data, Dalvik/Cache, System) and flash the custom TREBLE ROM.
I recommend to flash this custom TREBLE ROM: crDROID https://forum.xda-developers.com/galaxy-j7-2017/development/unofficial-crdroid-6-7-t4119505
To flash crDROID, first install the zip Exynos7870_CreateVendor_2.0.zip, reboot your phone in to recovery, and then flash crDROID(note that the vendor is included in crDROID).
Revert to stock ROM
You can use Odin tool to flash the stock rom. First find your stock rom on https://www.sammobile.com/, unpack the downloaded ROM, and then use Odin tool to flash all the files(BL,AP,CP, CSC)
To revert to stock ROM using your recovery, first install the zip Exynos7870_RevertVendor_2.0.zip(link here https://forum.xda-developers.com/galaxy-j7-2017/development/treble-project-treblue-j710x-t4098875), reboot your phone in to recovery so the recovery detects that the vendor partition is gone, and then restore your previously created backup.
Click to expand...
Click to collapse
Hi, I tried it on my J7 Pro (j730g/ds), but it stuck on cdroid logo. What I do
1. Install TWRP and format /data
2. Install Exynos7870_CreateVendor_2.0.zip and reboot to recovery
3. And Install crDroid 6.9 (without gapps)
4. Reboot
But phone it bootloop on cdroid logo.
Any help is Appreciate
Sorry for my bad english before.
suciprimawati said:
Hi, I tried it on my J7 Pro (j730g/ds), but it stuck on cdroid logo. What I do
1. Install TWRP and format /data
2. Install Exynos7870_CreateVendor_2.0.zip and reboot to recovery
3. And Install crDroid 6.9 (without gapps)
4. Reboot
But phone it bootloop on cdroid logo.
Any help is Appreciate
Sorry for my bad english before.
Click to expand...
Click to collapse
Do not flash cdroid, flash a treble rom instead. It should have a extension of .img instead of .zip
After flashing Exynos7870_CreateVendor_2.0.zip，flash skyhawk recovery project.
https://forum.xda-developers.com/ga.../unofficial-skyhawk-recovery-project-t4107145, rebooting into skywawk recovery,you should flash H-Vendor.
https://forum.xda-developers.com/galaxy-j7-2017/development/treble-h-vendor-v1-0-t4116277
Without rebooting immediately flash gsi image.
after flashing reboot device.
death.by.confusion said:
[GUIDE][J730X] A beginer's guide to installing custom ROM on Samsung Galaxy J7 2017
In order to install a custom ROM, the general steps are to: Unlock bootloader, Install custom recovery, make a backup of your current stock ROM, and then go to install a custom ROM.
NOTE: It is good idea to note your software version and your baseband version right now(enter *#1234# on dial pad)
This is so you can find your stock ROM on https://www.sammobile.com/ and flash with Odin tool.
Unlock bootloader
In our samsung phone it is very easy to unlock the bootloader. All you have to do is go to Developer options and enable OEM Unlock(something similar to the image below)
To enable Developer options, you go in About phone, and press on the field Build Number multiple times(something similar to the image below)
Install custom recovery
There are multiple choices for custom recovery for our samsung phone. I recommend to install TWRP 3.3.0(link here https://github.com/ananjaser1211/android_device_samsung_jxy17lte/releases)
You need samsung USB drivers(link here https://developer.samsung.com/mobile/android-usb-driver.html and the
the Odin tool(for flashing the recovery)(link here https://odinflashtool.com/download/odin3-v3-13-1/
1. Turn your phone in to Download mode. For that, first power off your phone, and then hold POWER button together with volume DOWN and HOME button, then connect the phone with USB cable on the computer.
2. Open Odin tool
3. In the options tab, uncheck auto reboot
4. Select the custom recovery image in to AP field(the exact file name of recovery from link is TWRP-3.3.0-j7y17lte-20190417.tar
5. Start flashing.
6. Now, hold POWER, volume DOWN, volume UP and HOME button together until your screen on the phone goes back, then instantly hold POWER, Volume UP and HOME button together, so you boot in to the installed recovery.
7. You should see the installed recovery working.
Set up internal storage so the recovery works properly
Warning: This operation WILL DELETE EVERYTHING ON YOUR INTERNAL STORAGE. COPY YOUR FILES ELSEWHERE.
Use your installed recovery to wipe the internal storage, so it becomes available for usage.
Select the option Wipe, then Format data, and then confirm the operation.
No you should be able to use your recovery for other operations.
Make a backup of your current stock ROM
Use your installed recovery to make a backup of your current stock ROM.
Select the option Backup, and then select all partitions, then confirm the backup operation.
After this, don't forget to copy the backup in your computer. For that, you can plug your phone to PC while you are in recovery, and then you can just copy the backup. The backup is stored in the folder named TWRP.
Install a custom ROM
You can use your recovery to install a custom ROM.
The general steps for installing a custom ROM are:
1. Wipe the partitions Data, Dalvik/Cache, System
2. Download the ROM that is a zip file and store the zip file in phone(either internal memory or SD CARD)
3. Use the install option in recovery to install the ROM
4. Reboot the phone.
Install a custom TREBLE ROM
Treble ROMS are different than regular custom ROMS, because they need the phone to have an additional Vendor partition.
To create a Vendor partition, use your recovery to install the zip Exynos7870_CreateVendor_2.0.zip(download from here https://forum.xda-developers.com/galaxy-j7-2017/development/treble-project-treblue-j710x-t4098875) and reboot your phone in to recovery so the recovery detects the new vendor partition.
Then you need to flash a particular vendor(Either Project Treblue, or H-VENDOR).
After that, you can wipe the partitions(Data, Dalvik/Cache, System) and flash the custom TREBLE ROM.
I recommend to flash this custom TREBLE ROM: crDROID https://forum.xda-developers.com/galaxy-j7-2017/development/unofficial-crdroid-6-7-t4119505
To flash crDROID, first install the zip Exynos7870_CreateVendor_2.0.zip, reboot your phone in to recovery, and then flash crDROID(note that the vendor is included in crDROID).
Revert to stock ROM
You can use Odin tool to flash the stock rom. First find your stock rom on https://www.sammobile.com/, unpack the downloaded ROM, and then use Odin tool to flash all the files(BL,AP,CP, CSC)
To revert to stock ROM using your recovery, first install the zip Exynos7870_RevertVendor_2.0.zip(link here https://forum.xda-developers.com/galaxy-j7-2017/development/treble-project-treblue-j710x-t4098875), reboot your phone in to recovery so the recovery detects that the vendor partition is gone, and then restore your previously created backup.
Click to expand...
Click to collapse
Hello. Sorry for the long reply ahead. I have the same problem of wanting to use 64 bit apps in my J7 pro (SM-J30G/DS). It's my first time doing a custom rom as well and I followed all the instructions detailed here, but things did not go well for me.
The only step I missed is copying the backup to my laptop because for some reason my device is not letting it be copied. Nevertheless, I proceeded to install the custom rom since I was hoping to use the stock rom in sammobile.com instead as backup.
However, I keep getting both the error 7 and "failed to mount /preload (invalid argument)" when installing crdroid. I tried numerous ways to fix it but nothing happens. The following are what I have already tried:
- Install older versions of crdroid (all versions causes error 7)
- Remove assert in "updater-script" (tried it in 6.9 and 6.7 versions but still get error 7)
- Install latest versions of twrp (I cannot find the latest version of twrp for j7y17lte aside from what's here, so I went to other sites that offer twrp for J7 pro (2017). I found j7xelte and herolte but they don't work, so I used given twrp here again)
I can't fix the error and the install was always unsuccessful, so I decided to use another custom rom which is HavocOS. I followed the instructions but I still get the error 7 when installing project treblue. I tried removing assert again but the error is still there. I researched more but I can't find any more solutions to this problem or what's causing it.
One thing to note is that the create vendor zip was installed successfully (but with failed to mount/preload) and only the custom roms receive error 7. My research about error 7 said that it happens when the device is incompatible with the roms to be installed, but I'm pretty sure that my device is J730G/DS which should work fine since it worked with others here that have the same device. If my device was incompatible, then why does the twrp and create vendor work fine? Is it because my phone was not rooted? I saw that a lot of custom roms require root before installing, but it was not mentioned in the instructions so I did not root my phone.
Another problem is that I can't revert to my stock rom anymore. I found my stock rom in sammobile and proceeded to flash it using odin, but then my phone is stuck in samsung logo after rebooting. I tried leaving it for 8 hours to see if it will load but nothing happened. I can still access the recovery so I reinstalled twrp and would try to reinstall my stock rom.
Any help would be appreciated. Thank you!
EDIT: After reinstalling twrp, I tried flashing the create vendor and crdroid again and for some reason, the installation was now successful. But after rebooting to system, it was stuck in the crdroid logo. I then went to twrp again, formatted the data, then installed HavocOS and to my surprise, it was successful! There are no problems with boot and I am currently able to use the rom smoothly.
Problem is fixed since I am able to use 64 bit apps, but if you guys know what happened and what steps I did wrong, please tell me! I am still confused with what the problem is and I don't want to experience the same problem when I update my rom. Any help would be appreciated. Thank you very much!
I want to run 64 bit in J7 max G615F
does it work on nokia 2.3 which is binder64?