Related
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
My rooted Axon 7 (A2017U) does not show the boot partition in TWRP when backing up or restoring a backup that previously showed the boot partition. Here is what I did prior to the problem:
1. Manually updated stock rom to B32 using DrakenFX procedures, which includes flashing bootstack. (I made a backup after the upgrade of boot, data, and system - as usual.)
2. When I restored AICP nandroid, boot was shown along with data and system. Phone operated normally, but would not flash OTA upgrade - error 7. (Attempted to flash a previous version that I had flashed before with the same error 7.)
3. Rather than unzipping the rom and deleting the asserts line, I flashed the universal boot image from LineageOS and was able to OTA without issue, but when I ran the TWRP backup, boot did not show and only system and data backed up.
4. Restored the stock nandroid, boot did not show.
My phone is operating normally, but I find it disconcerting to have made an unintended change and would appreciate any help in correcting my error.
Thanks in advance.
Hi have you fixed your problem or not?
William Guo said:
Hi have you fixed your problem or not?
Click to expand...
Click to collapse
No, still waiting for assistance.
Reflash TWRP. I had partitions missing and there was a weird version of TWRP installed for unknown reasons. Reflashing the latest TWRP fixed my problem.
JKSurf said:
Reflash TWRP. I had partitions missing and there was a weird version of TWRP installed for unknown reasons. Reflashing the latest TWRP fixed my problem.
Click to expand...
Click to collapse
That worked. Thank you very much. Weird how that happened.
Just as a matter of interest, I just did a clean install of AICP, which required installation of universal bootstack, and found that TWRP version had been replaced with an old version that did not show boot partition when doing nandroid. Reflashed current build image and boot file was visible.
Keep the latest .img on TWRP, and when you flash the universal bootstack, flash the TWRP .img after. I've asked over at the LOS thread if they could update the TWRP version on the bootstack and nobody answered lol
Should we use the one from twrps official website? I'm having the same issue but I can't remember changing my recovery.
jojofreddy said:
Should we use the one from twrps official website? I'm having the same issue but I can't remember changing my recovery.
Click to expand...
Click to collapse
You don't change your recovery, the universal bootstack zip does
It's the same whether you use the zip from TWRP's official website or raystef66's download center really
Guys this is help less.
After rooting my device I followed some instructions to get the Lineage 14. I flashed a BootLoader and a Modem as instructed and went forth to mount USB in order to transfer the custom rom into the device. But this is where the problem is.
It says E: Cant find partition to mount storage. I've tried to reboot, wide, data, storage, system and cache and repair the partition I don't know what else to do.
Anyone else can help? Btw I am fairly new to this stuff so please dumb it down for me.
Another thing, when I go to reboot my recovery it says my device isn't rooted and asks to install superSu, however it was rooted before I entered download mode and started installing bootloader and modem.
Now I have no operating system in the device so i can literally only use Recovery or download mode.
Is my device bricked? I don't know. :crying: :crying:
Pobi123 said:
Guys this is help less.
After rooting my device I followed some instructions to get the Lineage 14. I flashed a BootLoader and a Modem as instructed and went forth to mount USB in order to transfer the custom rom into the device. But this is where the problem is.
It says E: Cant find partition to mount storage. I've tried to reboot, wide, data, storage, system and cache and repair the partition I don't know what else to do.
Anyone else can help? Btw I am fairly new to this stuff so please dumb it down for me.
Another thing, when I go to reboot my recovery it says my device isn't rooted and asks to install superSu, however it was rooted before I entered download mode and started installing bootloader and modem.
Now I have no operating system in the device so i can literally only use Recovery or download mode.
Is my device bricked? I don't know. :crying: :crying:
Click to expand...
Click to collapse
If you can boot recovery, all is not lost.
First, are you sure that you flashed the correct bootloader/modem for your s5 model (G900 T, P, V, F, etc? Odin should not let you flash the wrong one, but anything is possible.
If Bl/modem is correct, them the next thing is to get the custom rom onto the phone.
-make sure you have downloaded everything you need (rom, root method(pref Magisk), gapps if wanted)
- boot into recovery, I'm recommending and assuming that you are using the latest Twrp, if not, d/l official Twrp for your model, and flash that with Odin
-In twrp select wipe, format data, just in case.
-now you should be able to mount usb storage, using the option in twrp
- now you should be able to mount your phone to your PC and transfer the rom, put it somewhere easy to find on the phone. also copy gapps and Magisk zips
-now, still in twrp, select install, select rom zip, select add more, select Magisk zip, also flash gapps at this time if you want to use them.
-click the button to flash
-click wipe cache/dalvik
-click reboot
-pray ?
BlueCyclone said:
If you can boot recovery, all is not lost.
First, are you sure that you flashed the correct bootloader/modem for your s5 model (G900 T, P, V, F, etc? Odin should not let you flash the wrong one, but anything is possible.
If Bl/modem is correct, them the next thing is to get the custom rom onto the phone.
-make sure you have downloaded everything you need (rom, root method(pref Magisk), gapps if wanted)
- boot into recovery, I'm recommending and assuming that you are using the latest Twrp, if not, d/l official Twrp for your model, and flash that with Odin
-In twrp select wipe, format data, just in case.
-now you should be able to mount usb storage, using the option in twrp
- now you should be able to mount your phone to your PC and transfer the rom, put it somewhere easy to find on the phone. also copy gapps and Magisk zips
-now, still in twrp, select install, select rom zip, select add more, select Magisk zip, also flash gapps at this time if you want to use them.
-click the button to flash
-click wipe cache/dalvik
-click reboot
-pray ?
Click to expand...
Click to collapse
Hey man! Thank you so much for your reply. I installed CPE1 bootloader and modem driver, honestly I don't even know what they do. Was this a wrong thing to do?
I rooted my device using cf auto root, then flashed the bootloader and modem using Odin. After that I (stupidly) tried to boot my stock OS and it was stuck in a bootloop.
Unfortunately I won't be able to try your instructions this till tomorrow evening but I'll keep you posted!! do you mind if I pm?
Edit: I was using twrp 2.8.7 I believe, could this have been the problem? Also I updated twrp to latest and tried micro sd as storage and flashed a Rom but the phone is still bootlooping
Pobi123 said:
Hey man! Thank you so much for your reply. I installed CPE1 bootloader and modem driver, honestly I don't even know what they do. Was this a wrong thing to do?
I rooted my device using cf auto root, then flashed the bootloader and modem using Odin. After that I (stupidly) tried to boot my stock OS and it was stuck in a bootloop.
Unfortunately I won't be able to try your instructions this till tomorrow evening but I'll keep you posted!! do you mind if I pm?
Edit: I was using twrp 2.8.7 I believe, could this have been the problem? Also I updated twrp to latest and tried micro sd as storage and flashed a Rom but the phone is still bootlooping
Click to expand...
Click to collapse
Ok I see you have S5 plus. I'm not familiar with that device to know which baseband it should be.
One thing you might try is to boot recovery and clear cache/dalvik and then try booting the custom rom.
If all else fails, you might try Samfirm
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
That should give you a stock firmware file to flash with odin.
You can pm if you need to, I don't own an S5+, nor am I a veteran flasher but I will try to help if I can.
BlueCyclone said:
Ok I see you have S5 plus. I'm not familiar with that device to know which baseband it should be.
One thing you might try is to boot recovery and clear cache/dalvik and then try booting the custom rom.
If all else fails, you might try Samfirm
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
That should give you a stock firmware file to flash with odin.
You can pm if you need to, I don't own an S5+, nor am I a veteran flasher but I will try to help if I can.
Click to expand...
Click to collapse
Ive tried the suggestion you gave me, no success. However I honestly dont know if it could be my fault. I'm gonna flash the stock firmware and restart the whole root process.
Thanks for your help man!
Pobi123 said:
Ive tried the suggestion you gave me, no success. However I honestly dont know if it could be my fault. I'm gonna flash the stock firmware and restart the whole root process.
Thanks for your help man!
Click to expand...
Click to collapse
Ok sorry I couldn't be more help
Oh, you don't need to use of cfautoroot anymore, you can just flash Magisk after the rom, and then use Magisk manager to manage all your root permissions.
So if you are going back to stock, I would:
-Flash stock in Odin
-probably boot stock once to verify (first boot takes long)
-odin flash latest twrp(uncheck auto-reboot, just battery pull after it says pass)
-power on phone with key combo to boot recovery
- format data
-flash rom/gapps?/Magisk
-wipe cache/dalvik
-reboot system (first boot will take long)
Hope you get your phone working again
BlueCyclone said:
Ok sorry I couldn't be more help
Oh, you don't need to use of cfautoroot anymore, you can just flash Magisk after the rom, and then use Magisk manager to manage all your root permissions.
So if you are going back to stock, I would:
-Flash stock in Odin
-probably boot stock once to verify (first boot takes long)
-odin flash latest twrp(uncheck auto-reboot, just battery pull after it says pass)
-power on phone with key combo to boot recovery
- format data
-flash rom/gapps?/Magisk
-wipe cache/dalvik
-reboot system (first boot will take long)
Hope you get your phone working again
Click to expand...
Click to collapse
Good News! Phone is back in full working order after flashing stock firmware. It was kinda scary though, I had to fix an error in Odin and then the phone wouldn't even boot up! Left it over night, booted it again and it worked fine Thanks a lot for your help, I'll try not to soft brick my device again
I am stuck at encryption failed when I flash stock oreo rom. I tried formatting data using twrp and flashed no encryption file as well but nothing works.:crying::crying::crying:
I just want to use the stock oreo rom again with root.
Pls help:crying:
Which ROM did you try and flash / install?
Try upgrading your TWRP to the latest version too.
jl10101 said:
Which ROM did you try and flash / install?
Try upgrading your TWRP to the latest version too.
Click to expand...
Click to collapse
I used partition dl mode to flash the stock oreo rom over 7.0 to keep the root. Then i flashed custom kernal for stock 8.0 but it didnt work. I have done the same procedure before and it has worked like a charm. But it keeps on giving the encrytion error when i try it now
Deadmeat03 said:
I used partition dl mode to flash the stock oreo rom over 7.0 to keep the root. Then i flashed custom kernal for stock 8.0 but it didnt work. I have done the same procedure before and it has worked like a charm. But it keeps on giving the encrytion error when i try it now
Click to expand...
Click to collapse
Odd. If I had to guess anything, it would be that not all the partitions were flashed when going from Nougat to Oreo.
I once flash a Nougat ROM from an Oreo ROM and I had the same encryption issue and lost everything.
That was the last time I would trust myself again and not do a backup.
Flash stock recovery from KDZ through patched LGUP & do a factory reset .
After stock recovery completes the wipe do a battery pull, flash TWRP via fastboot, format data, flash Kernel & Magisk & you should be back on track...
Prowler_gr said:
Flash stock recovery from KDZ through patched LGUP & do a factory reset .
After stock recovery completes the wipe do a battery pull, flash TWRP via fastboot, format data, flash Kernel & Magisk & you should be back on track...
Click to expand...
Click to collapse
I tried that as well. With stock recovery is says data is corrupted and doesn't do anything. I think it might be a problem with patched lg up because when i use normal lg up to flash oreo it works. But I cant root then.
I would try changing to 3.2.3-4 TWRP and then trying the procedure again. It seems that the 3.3.0 TWRP does not decrypt properly sometimes.
In the same boat as OP
scottyrick said:
I would try changing to 3.2.3-4 TWRP and then trying the procedure again. It seems that the 3.3.0 TWRP does not decrypt properly sometimes.
Click to expand...
Click to collapse
Hi
Looking for a way to keep TWRP and root ... any help appreciated
I've got a US996 with the same issue as the op. I have the latest TWRP 3.3.1-0. The phone was working fine until I upgraded twrp but I might have done a mistake resetting phone outside of twrp.
I can still get back into twrp but I haven't been able to install zip files without getting that decryption unsuccessful message when booting to system.
When getting back into TWRP using hardware buttons sometimes there is a prompt asking "keep system read only?" which I never chose and swipe to allow modification. I think this happens after
I pull the battery after getting the decryption unsuccessful message. There is a reset system that I could chose under the decryption unsuccessful message but I'm assuming that will make me lose twrp
...but if my phone is a us996 and is still
unlocked, would it matter if I did select it? Wouldn't I be able to reinstall twrp using adb again on a computer after Oreo is reinstalled?
To do Prowler_gr's suggestion which guide do I follow (sounds like I should do the second option)
"Flash stock recovery from KDZ through patched LGUP & do a factory reset .
After stock recovery completes the wipe do a battery pull, flash TWRP via fastboot, format data, flash Kernel & Magisk & you should be back on track... "
1-[GUIDE][UNBRICK] Patch LGUP to unlock features & unbrick V20 (Variant mismatch fix) to use lgup
or this guide
2-Ultimate guide to unbrick LG V20(Only Variants with .KDZ)[No OS Firmware Update Loop]
Thank you for any guidance on this...
There is a reset system that I could chose under the decryption unsuccessful message but I'm assuming that will make me lose twrp
Click to expand...
Click to collapse
Don't blame me if this goes wrong but I'm pretty much 100% certain that you mush press the rest button. This has happened to me a few times I'm sure. You won't loose twrp. Whatever resetting goes on in the background I don't think it's an actual Factory Reset.
Edit: Just to be clear you taking about a white screen with I think in dark blue or black text ENCRYPTION UNSUCCESSFUL and something like "reset phone" option directly under it, on the upper half of the screen?
Hi ezzony
Yes you are thinking of the right decryption unsuccessful page. I get it when booting to system
after installing Oreo and magisk 19 and having wiped everything (format data too). I will get the exact wording of it tonight
Thanks!
downgrade twrp i has same prob twrp 3.3.1 gives issues
ghet2rockuu said:
downgrade twrp i has same prob twrp 3.3.1 gives issues
Click to expand...
Click to collapse
Hi ghet2rockuu
I downgraded twrp and that got it working Thank You! see also Phoenix591 thread [Recovery][Unofficial for the moment]TWRP 3.3.1-0 : 2019-05-17 #625
Thank You !
For the past 24+ hours I've been trying to flash a few custom roms on my UNLOCKED BOOTLOADER OP6T, but the phone TURNS OFF a few seconds after the boot sequence/animation.
I've read about the A/B slots and tried the Roms' flashing instructions, along with a few suggestions from others, but I cannot get any Custom Rom on my phone...
Here are the steps I've taken to flash (a few times I tried different things that I'll put in parenthesis). Is there anything ya'll see that I'm doing wrong?:
Starting from OOS 10.3.2 Fastboot Recovery and all required files on an OTG USB Drive
fastboot to TWRP....img
Confirmed I'm on Slot A
Wipe Data/Dalvik
Install OOS...zip (10.3.2)
Install TWRP...zip (3.3.1.32)
Reboot Recovery
(Format Data)
Confirmed I'm on Slot B
Install OOS...zip (10.3.2)
Install TWRP...zip (3.3.1.32)
Reboot Recovery
Confirmed I'm on Slot A
Install Xtended (v8 4/13)
(Wipe Data/Cache)
Install TWRP...zip (3.3.1.32)
Reboot Recovery
Confirmed I'm on Slot B
Install Xtended (v8 4/13)
(Wipe Data/Cache)
Install TWRP...zip (3.3.1.32)
Reboot Recovery
Confirmed I'm on Slot A
Install GAPPS (Arm64 10.0 Nano)
(Format Data)
Reboot System
My Guide for Lineage, however it will work for most AOSP based ROMs.
I assume you arent manually switching slots. Don't, there is no need, in fact dont worry about it. Slots will switch automatically after flashing a ROM when you reboot recovery. There is no cache partition, stop wiping this, its not doing anything. There are two slots, but only one data partition that is shared, there isnt a reason to keep wiping it.
On most instructions adding or removing steps will make things not work. Unfortunately for this device there is a lot of out dated information and information that just doesnt work. My guide has been tested with 10.3.3, and the latest version of LOS, however if you have a T-Mobile 6T you are on your own. (I have a regular 6T)
OhioYJ said:
My Guide for Lineage, however it will work for most AOSP based ROMs.
I assume you arent manually switching slots. Don't, there is no need, in fact dont worry about it. Slots will switch automatically after flashing a ROM when you reboot recovery. There is no cache partition, stop wiping this, its not doing anything. There are two slots, but only one data partition that is shared, there isnt a reason to keep wiping it.
On most instructions adding or removing steps will make things not work. Unfortunately for this device there is a lot of out dated information and information that just doesnt work. My guide has been tested with 10.3.3, and the latest version of LOS, however if you have a T-Mobile 6T you are on your own. (I have a regular 6T)
Click to expand...
Click to collapse
Thanks for the comment! I just followed your guide, but still seeing the boot animation for a few seconds, then the phone vibrates and turns off.
For kicks, I decided to Format Data and I see the boot animation longer, all the way to the end when it's about to start Android, but then it vibrates and shuts off. Strange.
I'm thinking there is something different about my phone... It's a global, unlocked version and I've rooted/flashed hundreds of roms over the years on various devices, so all of this should be a piece of cake................. Thanks!
oooscasianooo said:
Thanks for the comment! I just followed your guide, but still seeing the boot animation for a few seconds, then the phone vibrates and turns off.
For kicks, I decided to Format Data and I see the boot animation longer, all the way to the end when it's about to start Android, but then it vibrates and shuts off. Strange.
I'm thinking there is something different about my phone... It's a global, unlocked version and I've rooted/flashed hundreds of roms over the years on various devices, so all of this should be a piece of cake................. Thanks!
Click to expand...
Click to collapse
Have you tried without Gapps?
After the shutdown go back to twrp and extract the content of /sys/fs/pstore/* and upload the files here.
onliner said:
After the shutdown go back to twrp and extract the content of /sys/fs/pstore/* and upload the files here.
Click to expand...
Click to collapse
Thanks. I actually gave up and setup stock OOS again, so it took a while to get a TWRP backup, etc. etc.
So after the backup, I installed Xtended + TWRP, reboot to recovery, installed Xtended + TWRP, wiped dalvik, and reboot to system.
Boot animation shut down issue as usual.
Afterwards, I copied the pstore folder (attached zip).
Thanks!
onliner said:
After the shutdown go back to twrp and extract the content of /sys/fs/pstore/* and upload the files here.
Click to expand...
Click to collapse
Anything in the logs I can look for?
This is driving me crazy. I flashed MIUI just fine (because it had the .bat file that does everything for you). Essentially it's doing the same thing as flashing OOS & Rom on A/B, right?
Just tried flashing the newest Xtended Rom (May 11th), same issue. Phone vibrates and completely turns off while the boot animation is running.
OhioYJ said:
My Guide for Lineage, however it will work for most AOSP based ROMs.
I assume you arent manually switching slots. Don't, there is no need, in fact dont worry about it. Slots will switch automatically after flashing a ROM when you reboot recovery. There is no cache partition, stop wiping this, its not doing anything. There are two slots, but only one data partition that is shared, there isnt a reason to keep wiping it.
On most instructions adding or removing steps will make things not work. Unfortunately for this device there is a lot of out dated information and information that just doesnt work. My guide has been tested with 10.3.3, and the latest version of LOS, however if you have a T-Mobile 6T you are on your own. (I have a regular 6T)
Click to expand...
Click to collapse
If you have a TMobile 6t I can confirm I have had to manually change the slots during the flashing process to get custom ROMs installed.
mrmcshagbag said:
If you have a TMobile 6t I can confirm I have had to manually change the slots during the flashing process to get custom ROMs installed.
Click to expand...
Click to collapse
I found out that I do have the T-Mobile version that the seller flashed to International Software haha
When I reboot to recovery, I do see that the slots are being changed though.
Would you mind post the exact steps you took to successfully flash a ROM/GAPPS?
oooscasianooo said:
I found out that I do have the T-Mobile version that the seller flashed to International Software haha
When I reboot to recovery, I do see that the slots are being changed though.
Would you mind post the exact steps you took to successfully flash a ROM/GAPPS?
Click to expand...
Click to collapse
Fastboot boot TWRP Marion version
Flash oos
Flash Marion TWRP zip
Check my slot
Reboot recovery
Changed slot since it didn't change
Reboot recovery
Flash oos
Flash Marion TWRP zip
Changed slot
Reboot recovery
Flash custom rom
Flash Marion TWRP zip
Change slot
Reboot recovery
Flash gapps
Flash magisk 20.4
Reboot to system
Those are the steps I had to take before I finally got a custom rom to work. I tried doing the methods posted which would have probably worked if the slots were changing on there own but they weren't for me.
mrmcshagbag said:
Fastboot boot TWRP Marion version
Flash oos
Flash Marion TWRP zip
Check my slot
Reboot recovery
Changed slot since it didn't change
Reboot recovery
Flash oos
Flash Marion TWRP zip
Changed slot
Reboot recovery
Flash custom rom
Flash Marion TWRP zip
Change slot
Reboot recovery
Flash gapps
Flash magisk 20.4
Reboot to system
Those are the steps I had to take before I finally got a custom rom to work. I tried doing the methods posted which would have probably worked if the slots were changing on there own but they weren't for me.
Click to expand...
Click to collapse
Thanks! Do you mean the "mauronofrio" version?
oooscasianooo said:
Thanks! Do you mean the "mauronofrio" version?
Click to expand...
Click to collapse
Yes couldn't remember the exact name but I knew you would be able to find it haha
mrmcshagbag said:
Yes couldn't remember the exact name but I knew you would be able to find it haha
Click to expand...
Click to collapse
hahaha thanks! I was thinking, "is there a T-Mobile version of TWRP?!" haha!