After attempting root on my replacement phone, I could NOT boot to system. Each time I rebooted to "System", it would boot straight to TWRP over and over. I tried reflashing stock files. No verity patching.. etc.
The Fix:
Download the latest version of TWRP specific to your device here https://build.nethunter.com/test-builds/twrp/lge/
Flash the file and the device should now be able to boot to system. If that doesn't work try another version.
I spoke to @jcadduono about my problems and he believes there may have been something weird going on in the misc partition. Reflashing TWRP will/should fix the problem.
Thanks @jcadduono for all the support.
I had this happen to me after installing TWRP for the first time. It would keep rebooting to TWRP. This was after making sure I flashed SuperSU as well. Eventually in a moment of "might as well see what will happen" I rebooted then held down the power button and volume down. Got to the option if I wanted to factory reset my phone which I did which booted into TWRP. Rebooted to system from there which got me out of the TWRP Bootloop.
I'm still in the bootloop. It now says "No OS installed." Any help would be appreciated.
Also, I'm getting this:
"Failed to mount '/system' (Unknown error 150)"
Help, please!
---------- Post added at 12:59 PM ---------- Previous post was at 12:05 PM ----------
I tried all *three* versions. Still on a TWRP bootloop.
Mrsana said:
I'm still in the bootloop. It now says "No OS installed." Any help would be appreciated.
Also, I'm getting this:
"Failed to mount '/system' (Unknown error 150)"
Help, please!
---------- Post added at 12:59 PM ---------- Previous post was at 12:05 PM ----------
I tried all *three* versions. Still on a TWRP bootloop.
Click to expand...
Click to collapse
Download the deodex rom flash it, then flash no_verity , then format data.
Mastajeff said:
Download the deodex rom flash it, then flash no_verity , then format data.
Click to expand...
Click to collapse
So, I've done those steps and I'm still stuck in a recovery bootloop. I have twrp, just can't seem to get out of it
frenize said:
So, I've done those steps and I'm still stuck in a recovery bootloop. I have twrp, just can't seem to get out of it
Click to expand...
Click to collapse
Turn off your phone. Go into TWRP *manually*. That is, press the power off and volume down buttons. Once you see the LG logo, quickly release the power button and press it again. It will ask if you want to do a factory reset. Say "Yes" to both.
Once inside TWRP (*manually*), do a factory reset. You will be rebooted and it will go back to TWRP. Once inside TWRP after the reboot, go to reboot and choose "System". You should know be out of the TWRP bootloop!
It worked for me.
frenize said:
So, I've done those steps and I'm still stuck in a recovery bootloop. I have twrp, just can't seem to get out of it
Click to expand...
Click to collapse
Decrypt data.
As a general statement : Almost all TWRP bootloops are due to users not backing up their data, and then formatting data.
Hardware encryption is not supported.
Decrypt your data, flash a ROM, and if that ROM doesn't have SuperSU, flash SuperSU.
Go flash my v5 MOD ROM.
Decrypt your data! 95% of TWRP loop cases are due to data not being decrypted, or some other step the user failed to follow.
Good luck.
---------- Post added at 04:28 PM ---------- Previous post was at 04:28 PM ----------
Mrsana said:
I'm still in the bootloop. It now says "No OS installed." Any help would be appreciated.
Also, I'm getting this:
"Failed to mount '/system' (Unknown error 150)"
Help, please!
---------- Post added at 12:59 PM ---------- Previous post was at 12:05 PM ----------
I tried all *three* versions. Still on a TWRP bootloop.
Click to expand...
Click to collapse
This is because you went to Advanced Wipe, and formatted /system.
Make sure you are on the latest TWRP, make sure you're data is decrypted, and then go flash my v5 MOD ROM.
For those that are still having troubles. My guide works: forum.xda-developers.com/v20/how-to/how-fixed-bricked-lg-v20-t3501310
Mastajeff said:
After attempting root on my replacement phone, I could NOT boot to system. Each time I rebooted to "System", it would boot straight to TWRP over and over. I tried reflashing stock files. No verity patching.. etc.
The Fix:
Download the latest version of TWRP specific to your device here https://build.nethunter.com/test-builds/twrp/lge/
Flash the file and the device should now be able to boot to system. If that doesn't work try another version.
I spoke to @jcadduono about my problems and he believes there may have been something weird going on in the misc partition. Reflashing TWRP will/should fix the problem.
Thanks @jcadduono for all the support.
Click to expand...
Click to collapse
is it possible that the phone bootloops without doing anything like root and custom roms?
asking cz i'm looking to get the LG V20 but don't know about the risk of it bootlooping itself, without rooting or anything like that, like it used
to happen on lg g4 and g3.
Thank you
It's been determined that it does this when it finds an update in the fota and or misc folders. The phone downloads updates even when you tell it not to. It just doesn't install them without your permission.
Easy to get out of with the volume down and power button reset procedure which then deletes the files automatically or you can delete the files in twrp to fix it.
Poda_jj said:
is it possible that the phone bootloops without doing anything like root and custom roms?
asking cz i'm looking to get the LG V20 but don't know about the risk of it bootlooping itself, without rooting or anything like that, like it used
to happen on lg g4 and g3.
Thank you
Click to expand...
Click to collapse
All the bootloops for the V20 so far are all due to modifications and rooting. There are some roms that work for everyone but just refuses to work on my phone and will just bootloop. I doubt that the cause of the software bootloop is fully known. I've followed directions 100% on working romss and it would bootloop but installed a different version of the same rom and it worked. None of the bootloop "fixes" did anything for me. Fortunately, the rom that I installed is still awesome and works great.
LS997 BTW
I fought with this for many hours yesterday. I tried everything I could find and got nowhere. Finally ended out holding Volume Up while inserting the cable to computer to put the phone in download mode and was able to use the kdz file to stock restore.
bond32 said:
I fought with this for many hours yesterday. I tried everything I could find and got nowhere. Finally ended out holding Volume Up while inserting the cable to computer to put the phone in download mode and was able to use the kdz file to stock restore.
Click to expand...
Click to collapse
my phone is in twrp bootloop as well, mind going into a bit of details as in how you did the kdz restore?
dangercl0se said:
my phone is in twrp bootloop as well, mind going into a bit of details as in how you did the kdz restore?
Click to expand...
Click to collapse
There's a few guides here on how to do a full restore. Make sure you download the things you need according to your model V20 and make sure you have ADB working and current drivers installed.
http://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903/page7
I've used the kdz file before without any problems but it began the process from my home screen. I had no idea how to get it to start if you're in a TWRP loop which is where the "download mode" came in.
With the phone completely off, hold volume up a d plug it in the computer.
That will put it in download mode which is what mine needed.
The other mistake I made, make sure you use a USB 2.0 port, not 3.0. I've always had issues with USB 3.0 drivers not working correctly but 2.0 seems to be good.
My one is fully back to stock on Verizon 13a now and works well, except I think something is taking up space on my internal storage. It shows a max of around 50 gb with used some and 44 gb available. That seems quite low like something isn't right...
twrp boot loops most deffinately happen due to the update package sitting in your misc folder
use twrp to delete the misc directory as well as the fota directory and reboot.
This hasn't happened to me once since i moved to the latest version for my variant, but happens a ton when using the original build that kept dl the update regardless of me telling it to.
This is a common issue with the LG series and boot-loops. They all do this if there is a expected upate in the misc directory. And has been covered many times over the variants and that deleting misc is the only option. Some of us dont have a kdz, or if youve changed your build.prop the kdz wont restore anything since it will see it as a incompatible device.
before rebooting into twrp on a older build make sure you delete the update package if not this will keep happening. once deleted make sure the updater gets frozen so it wont re-download later.
Team DevDigitel said:
twrp boot loops most deffinately happen due to the update package sitting in your misc folder
use twrp to delete the misc directory as well as the fota directory and reboot.
This hasn't happened to me once since i moved to the latest version for my variant, but happens a ton when using the original build that kept dl the update regardless of me telling it to.
This is a common issue with the LG series and boot-loops. They all do this if there is a expected upate in the misc directory. And has been covered many times over the variants and that deleting misc is the only option. Some of us dont have a kdz, or if youve changed your build.prop the kdz wont restore anything since it will see it as a incompatible device.
before rebooting into twrp on a older build make sure you delete the update package if not this will keep happening. once deleted make sure the updater gets frozen so it wont re-download later.
Click to expand...
Click to collapse
Thanks. I suppose deleting those folders isn't possible without root access?
bond32 said:
Thanks. I suppose deleting those folders isn't possible without root access?
Click to expand...
Click to collapse
yeah MISC and FOTA are protected as read only for the user without root.
Mrsana said:
Turn off your phone. Go into TWRP *manually*. That is, press the power off and volume down buttons. Once you see the LG logo, quickly release the power button and press it again. It will ask if you want to do a factory reset. Say "Yes" to both.
Once inside TWRP (*manually*), do a factory reset. You will be rebooted and it will go back to TWRP. Once inside TWRP after the reboot, go to reboot and choose "System". You should know be out of the TWRP bootloop!
It worked for me.
Click to expand...
Click to collapse
Thank you, This Worked for me.
bond32 said:
There's a few guides here on how to do a full restore. Make sure you download the things you need according to your model V20 and make sure you have ADB working and current drivers installed.
http://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903/page7
I've used the kdz file before without any problems but it began the process from my home screen. I had no idea how to get it to start if you're in a TWRP loop which is where the "download mode" came in.
With the phone completely off, hold volume up a d plug it in the computer.
That will put it in download mode which is what mine needed.
The other mistake I made, make sure you use a USB 2.0 port, not 3.0. I've always had issues with USB 3.0 drivers not working correctly but 2.0 seems to be good.
My one is fully back to stock on Verizon 13a now and works well, except I think something is taking up space on my internal storage. It shows a max of around 50 gb with used some and 44 gb available. That seems quite low like something isn't right...
Click to expand...
Click to collapse
did that, phone works, no more root.... i rooted the phone again, flashed SU and encryption zip. STILL GET INTO TWRP LOOP.
dangercl0se said:
did that, phone works, no more root.... i rooted the phone again, flashed SU and encryption zip. STILL GET INTO TWRP LOOP.
Click to expand...
Click to collapse
Did you try the above where you delete the misc and fota folders?
Related
Hey guys, flashed this camera mod http://forum.xda-developers.com/showthread.php?t=2516061
and am now stuck in a boot loop. my huge mistake was i didn't make a backup on CWN when i installed it, since i'm a massive noob.
I'd post this in the thread for the mod, but new accts can't post in developer forum (to prevent threads like these, probably).
anyone know a quick solution to this? i've dalvik wiped, factory resetted, wiped cache partition.
edit: i also don't know how to get the stock camera ROM back on the device since it doesn't show up in my windows explorer. if i knew that, it'd be easy to go back to stock.
stealth0wnz said:
Hey guys, flashed this camera mod http://forum.xda-developers.com/showthread.php?t=2516061
and am now stuck in a boot loop. my huge mistake was i didn't make a backup on CWN when i installed it, since i'm a massive noob.
I'd post this in the thread for the mod, but new accts can't post in developer forum (to prevent threads like these, probably).
anyone know a quick solution to this? i've dalvik wiped, factory resetted, wiped cache partition.
edit: i also don't know how to get the stock camera ROM back on the device since it doesn't show up in my windows explorer. if i knew that, it'd be easy to go back to stock.
Click to expand...
Click to collapse
If you can get back to the boot loader (hold down power button and volume down) and recovery (choice in bootloader menu), you are fine. I did the same thing. you can adb push the stock file (in his developer thread) and then flash it with custom recovery.
Here is a link showing how to adb push - http://forum.xda-developers.com/showthread.php?t=1667929
If that doesn't work, you can always flash back stock...... Unfortunately have had to do this more than once and have learned my lesson on backups.
Speedbal
Hope that helps.
speedbal said:
If you can get back to the boot loader (hold down power button and volume down) and recovery (choice in bootloader menu), you are fine. I did the same thing. you can adb push the stock file (in his developer thread) and then flash it with custom recovery.
If that doesn't work, you can always flash back stock...... Unfortunately have had to do this more than once and have learned my lesson on backups.
Speedbal
Hope that helps.
Click to expand...
Click to collapse
I guess you gotta learn this stuff at some point, thanks for your help! i forgot that you could push files!
now a brand new issue is that anytime i flash ANYTHING to the phone, adb doesn't see the device anymore.
anyone know what's up with that?
URGENT
I did the camera mod too and happened to kill my phone trying to get a camera back on it. It boot loops bc now there is no os. Tried installing Cm-12.1 on my N910P and its now getting a "Error updating binary zip" on TWRP. I have no idea what to do. I have wiped the phone several times. Tried using odin and it failed when the phone was up and running, now it still fails any rom. Please help. I have pushed thru adb, odin, im out of options on my end. no backup either. Looking for a stock twrp recovery file for any note4 dont care anymore
SteveRogers1776 said:
I did the camera mod too and happened to kill my phone trying to get a camera back on it. It boot loops bc now there is no os. Tried installing Cm-12.1 on my N910P and its now getting a "Error updating binary zip" on TWRP. I have no idea what to do. I have wiped the phone several times. Tried using odin and it failed when the phone was up and running, now it still fails any rom. Please help. I have pushed thru adb, odin, im out of options on my end. no backup either. Looking for a stock twrp recovery file for any note4 dont care anymore
Click to expand...
Click to collapse
New nightlies of CM12.1 needs the bootloader to be updated to newer version (HHZ12H).
Following the link to flashable zip of new bootloader: https://www.androidfilehost.com/?fid=23991606952613145 (Credit to @mo976)
Flash it in recovery
Wipe the cache
Reboot into bootloader and select recovery.
Flash CM12.1 rom.
I just tried what you recommended . Maybe I'm doing it wrong but I'm still getting "error updating binary zip" when trying to load anything on twrp
Hello guys, having a bit of a dilemna here as only took the plunge to root today and is my first time in doing so. What I have done is updated to 4.4.2 KitKat OTA and then rooted my moto g. I used the superboot method and got the horrible pink screen and had to manually install supersu, however the device is rooted and obviously the bootloader is unlocked. I then proceeded to put everything back on my phone and then encrypted my phone.
However, I tried to get into recovery (stock) and was fronted with the on its back android with its belly open and red "!" in a triangle. I got this before I even unlocked to bootloader. Anyhow, I wanted to use a custom recovery so I could manage different ROMs in ROM manager etc, so I flashed CWM6046-MotoG44.img (CMW ver. 6.0.4.6) and all was swell.... until i wanted to make a backup.
I did a little searching around and was stumped until I found a post suggesting that CMW couldnt mount storage because the device was encrypted.
What I would like to know if at all possible; what would be the best course of action to take, as im unsure what will/could brick/break my device and as its encrypted I dont think adb commands are pushed as when flashing the recovery image, my device was listed in fastboot devices but not adb devices.
Should I flash a stock image and go from there, put everything back on yada yada yada and NOT encrypt the device, or....
Should I do a factory reset? will this brick my device/lose root access? or will I be able to re root?
I really appreciate any input you guys can give me, and for the meantime im just going to leave my device as it is and not flash anything else,
Many thanks and best regards,
voosh
Anybody have any ideas?
Can anybody help me here. Need to get this sorted so I can flash a custom ROM. Thanks
Bump...................
voosh710 said:
Hello guys, having a bit of a dilemna here as only took the plunge to root today and is my first time in doing so. What I have done is updated to 4.4.2 KitKat OTA and then rooted my moto g. I used the superboot method and got the horrible pink screen and had to manually install supersu, however the device is rooted and obviously the bootloader is unlocked. I then proceeded to put everything back on my phone and then encrypted my phone.
However, I tried to get into recovery (stock) and was fronted with the on its back android with its belly open and red "!" in a triangle. I got this before I even unlocked to bootloader. Anyhow, I wanted to use a custom recovery so I could manage different ROMs in ROM manager etc, so I flashed CWM6046-MotoG44.img (CMW ver. 6.0.4.6) and all was swell.... until i wanted to make a backup.
I did a little searching around and was stumped until I found a post suggesting that CMW couldnt mount storage because the device was encrypted.
What I would like to know if at all possible; what would be the best course of action to take, as im unsure what will/could brick/break my device and as its encrypted I dont think adb commands are pushed as when flashing the recovery image, my device was listed in fastboot devices but not adb devices.
Should I flash a stock image and go from there, put everything back on yada yada yada and NOT encrypt the device, or....
Should I do a factory reset? will this brick my device/lose root access? or will I be able to re root?
I really appreciate any input you guys can give me, and for the meantime im just going to leave my device as it is and not flash anything else,
Many thanks and best regards,
voosh
Click to expand...
Click to collapse
When you get the dead android hold power button for ten seconds then tap the power button,that should get you into stock recovery ,then navigate to wipe data factory reset ,you shouldn't lose root but you will lose da ta and apps
Thanks for the reply but I have already installed the cwm custom recovery. Should I add that I'm still able to access device, my problem mainly is getting rid of encryption as I can't use cwm while device is encrypted and can only do so by factory reset or flashing a stock ROM, but unsure of which option to take. Many thanks and best regards
kieranc88 said:
When you get the dead android hold power button for ten seconds then tap the power button,that should get you into stock recovery ,then navigate to wipe data factory reset ,you shouldn't lose root but you will lose da ta and apps
Click to expand...
Click to collapse
https://docs.google.com/file/d/0B2LP8tI1Xwu4MGtPTlpVcVQxN0k/preview try this cwm it worked for me,I'm not too clued up on encryption but I'm guessing you can't read/write to phones system to easily with it on so I'd guess it conflicts with root
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
kieranc88 said:
When you get the dead android hold power button for ten seconds then tap the power button,that should get you into stock recovery ,then navigate to wipe data factory reset ,you shouldn't lose root but you will lose da ta and apps
Click to expand...
Click to collapse
voosh710 said:
Thanks for the reply but I have already installed the cwm custom recovery. Should I add that I'm still able to access device, my problem mainly is getting rid of encryption as I can't use cwm while device is encrypted and can only do so by factory reset or flashing a stock ROM, but unsure of which option to take. Many thanks and best regards
Click to expand...
Click to collapse
So when you boot to recovery can you access recovery options or do you get dead robot
kieranc88 said:
https://docs.google.com/file/d/0B2LP8tI1Xwu4MGtPTlpVcVQxN0k/preview try this cwm it worked for me,I'm not too clued up on encryption but I'm guessing you can't read/write to phones system to easily with it on so I'd guess it conflicts with root
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
So when you boot to recovery can you access recovery options or do you get dead robot
Click to expand...
Click to collapse
I did get a dead robot. So I flashed CWM custom recovery. I now get the cwm recovery and options, but I can't make a backup becausey filesystem is encrypted, so would like to know the best way to decrypt by means of flashing a new or ROM or simply doing a factory reset within tho phones menus.
Many thanks
voosh710 said:
I did get a dead robot. So I flashed CWM custom recovery. I now get the cwm recovery and options, but I can't make a backup becausey filesystem is encrypted, so would like to know the best way to decrypt by means of flashing a new or ROM or simply doing a factory reset within tho phones menus.
Many thanks
Click to expand...
Click to collapse
OK,you need to boot into cwm and choose the wipe data factory reset option from cwm, I tried to wipe my phone before from the phones menu and because it had a custom recovery it didn't work,but if you boot cwm-wipe data/factory reset it will remove encryption.
Any luck???
kieranc88 said:
Any luck???
Click to expand...
Click to collapse
Sorry, I fell asleep lol was a long day.
Going to try it now and will keep you posted, Cheers.
EDIT - Didnt work - failed to mount storage because "android secure"
Factory reset within the phone also didnt work - The phone reset and the android with the blue thing in its stomach was stuck in a loop, probably because of custom recovery.
Is there a stock recovery I can flash to factory restore the phone?
EDIT 2 - Flashed this recovery - http://forum.xda-developers.com/showthread.php?t=2578243
Now when I boot into recovery it just boots into the phone regularly. When performing a factory reset now the android doesnt even appear and the phone boots regularly again, still encrypted
voosh710 said:
Sorry, I fell asleep lol was a long day.
Going to try it now and will keep you posted, Cheers.
EDIT - Didnt work - failed to mount storage because "android secure"
Factory reset within the phone also didnt work - The phone reset and the android with the blue thing in its stomach was stuck in a loop, probably because of custom recovery.
Is there a stock recovery I can flash to factory restore the phone?
EDIT 2 - Flashed this recovery - http://forum.xda-developers.com/showthread.php?t=2578243
Now when I boot into recovery it just boots into the phone regularly. When performing a factory reset now the android doesnt even appear and the phone boots regularly again, still encrypted
Click to expand...
Click to collapse
I kinda guessed that would happen because its not stock recovery,have u got a us version or international(is it xt1032 or xt1034?
kieranc88 said:
I kinda guessed that would happen because its not stock recovery,have u got a us version or international(is it xt1032 or xt1034?
Click to expand...
Click to collapse
Its a unlocked retail UK version, not sure if its xt1032 or xt1034 because I renamed it to Moto G.
voosh710 said:
Its a unlocked retail UK version, not sure if its xt1032 or xt1034 because I renamed it to Moto G.
Click to expand...
Click to collapse
You've got the same as mine,OK if that didn't work it might be because its jellybean, this is a recovery for the us version but its a KitKat recovery but worst that can happen is it won't boot to recovery, flash it and if doesn't work I'll see can I extract the recovery image from my phone, try it and get back to me asap fastboot flash recovery recovery.IMG
https://www.dropbox.com/s/66br4aiyzipu6x9/recovery.img
kieranc88 said:
You've got the same as mine,OK if that didn't work it might be because its jellybean, this is a recovery for the us version but its a KitKat recovery but worst that can happen is it won't boot to recovery, flash it and if doesn't work I'll see can I extract the recovery image from my phone, try it and get back to me asap fastboot flash recovery recovery.IMG
https://www.dropbox.com/s/66br4aiyzipu6x9/recovery.img
Click to expand...
Click to collapse
Flashed and still boots regularly .
voosh710 said:
Flashed and still boots regularly .
Click to expand...
Click to collapse
In the command line is it saying recovery sent
kieranc88 said:
In the command line is it saying recovery sent
Click to expand...
Click to collapse
Sent and finished ok
voosh710 said:
Sent and finished ok
Click to expand...
Click to collapse
How many times have you flashed it,try flashing two three timees
kieranc88 said:
How many times have you flashed it,try flashing two three timees
Click to expand...
Click to collapse
Actually, looking at the device it says "hab check failed for recovery"
However the other one (jellybean one i think that I linked to) never.
tried flashing 5 or 6 times no luck
Try this link to restore to 4.3 then ota to 4.4 again http://www.modaco.com/topic/366786-how-to-flash-to-the-standard-uk-rom/
My buddy is having a hard time flashing a new ROM on his tablet. Currently he's running Cyanogen with TWRP.
Apparently TWRP formatted his tablet randomly and he hasn't been able to install a new ROM because his tablet won't mount the system or cache. It keeps failing. Neither system or cache are selectable to mount and it says "E: unable to mount '/system' "
And ADB isn't pushing anything.
Any thoughts why?
Sunset Rider said:
My buddy is having a hard time flashing a new ROM on his tablet. Currently he's running Cyanogen with TWRP.
Apparently TWRP formatted his tablet randomly and he hasn't been able to install a new ROM because his tablet won't mount the system or cache. It keeps failing. Neither system or cache are selectable to mount and it says "E: unable to mount '/system' "
And ADB isn't pushing anything.
Any thoughts why?
Click to expand...
Click to collapse
TWRP formatted his tablet randomly??? Never heard of such a thing!
And we need more information:
What versions of bootloader, CM, TWRP and you are trying to push what in ADB?
Do you have access to fastboot? What rom are you trying to flash?
What did he do - as best as he can remember?
berndblb said:
TWRP formatted his tablet randomly??? Never heard of such a thing!
And we need more information:
What versions of bootloader, CM, TWRP and you are trying to push what in ADB?
Do you have access to fastboot? What rom are you trying to flash?
What did he do - as best as he can remember?
Click to expand...
Click to collapse
It wiped his data when he went to decrypt data and it asked for a password. He hit cancel and it said system memory 0gb
He has the newest twrp, he was on 10.2 trying to go to 11, and he was trying to push the mounting through adb and was getting errors. Because he is unable to select them In twrp
He has fastboot but it doesn't respond to commands at all.
Thank you for any help
fastboot
Sunset Rider said:
It wiped his data when he went to decrypt data and it asked for a password. He hit cancel and it said system memory 0gb
He has the newest twrp, he was on 10.2 trying to go to 11, and he was trying to push the mounting through adb and was getting errors. Because he is unable to select them In twrp
He has fastboot but it doesn't respond to commands at all.
Thank you for any help
Click to expand...
Click to collapse
Sounds like a soft brick.. Due to a wrong recovery flash or he flashed the newest version of twrp, and did a full data wipe.. It has known issues!!!!!
Becareful from here.. Like berndblb said we need verify we still have fastboot access!!:fingers-crossed:
What is the OS of the PC your using to fastboot from??
Well I tried installing cromi for him and it stalls at 87%
Sunset Rider said:
Well I tried installing cromi for him and it stalls at 87%
Click to expand...
Click to collapse
UPDATE: We restarted the tablet, mid installation because it froze, and it booted up to his old 10.2 just fine. I recommended he do a clean format now but he doesn't want to do anything lol.
So right now I'm just thanking God he didn't brick it hard
Sunset Rider said:
It wiped his data when he went to decrypt data and it asked for a password. He hit cancel and it said system memory 0gb
Click to expand...
Click to collapse
Did he have the tablet encrypted or did the request for a decryption password just show up unexpectedly? If it's the latter - I have read about this a number of times - unfortunately still cannot make rhyme or reason out of it, but I suspect it's a corrupted recovery....
He has the newest twrp, he was on 10.2 trying to go to 11, and he was trying to push the mounting through adb and was getting errors. Because he is unable to select them In twrp
Click to expand...
Click to collapse
The newest meaning 2.6.3.2?
He has fastboot but it doesn't respond to commands at all.
Thank you for any help
Click to expand...
Click to collapse
Which probably means he doesn't have the correct fastboot drivers installed. That would No. 1: Get fastboot working. Download the Google Universal Naked drivers, install them and try
Code:
fastboot devices
If that returns the tablet's serial number, you're in business. You could then flash CWM 6.0.4.6 in fastboot. I would probably wipe data (hope he has everything backed up) and flash the rom.
---------- Post added at 10:18 PM ---------- Previous post was at 10:10 PM ----------
lj50036 said:
Sounds like a soft brick.. Due to a wrong recovery flash or he flashed the newest version of twrp, and did a full data wipe.. It has known issues!!!!!
Becareful from here.. Like berndblb said we need verify we still have fastboot access!!:fingers-crossed:
What is the OS of the PC your using to fastboot from??
Click to expand...
Click to collapse
@lj50036 could you elaborate on the issues of TWRP 2.6.3.2.? sbdags included it it in his bootloader/TWRP flash package for CROMi-X and one guy just softbricked flashing CROMi_X after flashing that package, he seems to have done everything else correctly and I suspect the recovery is buggy???
TWRP
could you elaborate on the issues of TWRP 2.6.3.2.? sbdags included it it in his bootloader/TWRP flash package for CROMi-X and one guy just softbricked flashing CROMi_X after flashing that package, he seems to have done everything else correctly and I suspect the recovery is buggy???
Click to expand...
Click to collapse
My issues are first hand.. It flashes just fine, everything seems to function correctly.. It's only the wiping of data that has a issue.... It just hangs says its doing it thing but nothing ever happens..After a hard reboot TWRP now asking for password will not mount any storage of any kind... The fastest way to a soft brick.... I posted on the TWRP forum, about the issue... Maybe we need a new forum letting people know about the issue, so we dont end up with a riot!!!
lj50036 said:
My issues are first hand.. It flashes just fine, everything seems to function correctly.. It's only the wiping of data that has a issue.... It just hangs says its doing it thing but nothing ever happens..After a hard reboot TWRP now asking for password will not mount any storage of any kind... The fastest way to a soft brick.... I posted on the TWRP forum, about the issue... Maybe we need a new forum letting people know about the issue, so we dont end up with a riot!!!
Click to expand...
Click to collapse
Thanks! Though I would love to see what a riot on XDA looks like LOL
berndblb said:
Did he have the tablet encrypted or did the request for a decryption password just show up unexpectedly? If it's the latter - I have read about this a number of times - unfortunately still cannot make rhyme or reason out of it, but I suspect it's a corrupted recovery....
The newest meaning 2.6.3.2?
Which probably means he doesn't have the correct fastboot drivers installed. That would No. 1: Get fastboot working. Download the Google Universal Naked drivers, install them and try
Code:
fastboot devices
If that returns the tablet's serial number, you're in business. You could then flash CWM 6.0.4.6 in fastboot. I would probably wipe data (hope he has everything backed up) and flash the rom.
---------- Post added at 10:18 PM ---------- Previous post was at 10:10 PM ----------
@lj50036 could you elaborate on the issues of TWRP 2.6.3.2.? sbdags included it it in his bootloader/TWRP flash package for CROMi-X and one guy just softbricked flashing CROMi_X after flashing that package, he seems to have done everything else correctly and I suspect the recovery is buggy???
Click to expand...
Click to collapse
It was version 2.6.3.0.
He had no decrypted files he was just seeing what it did when he hit decrypt data. I asked for a password which he obviously never set and hit cancel. And it said he had nothing in internal storage.
However, after the install froze on an older Cromi version I put on his sd card (from my 700t), we held down the power button and rebooted. It booted up fine to his previous Cyanogen 10.2. WITH all of his internal storage still there, EVEN THOUGH, he did a format from TWRP already.
So it's definitely a problem with TWRP. His tablet is back to the way it was before the fiasco and he is afraid to do anything else.
Sunset Rider said:
It was version 2.6.3.0.
He had no decrypted files he was just seeing what it did when he hit decrypt data. I asked for a password which he obviously never set and hit cancel. And it said he had nothing in internal storage.
However, after the install froze on an older Cromi version I put on his sd card (from my 700t), we held down the power button and rebooted. It booted up fine to his previous Cyanogen 10.2. WITH all of his internal storage still there, EVEN THOUGH, he did a format from TWRP already.
So it's definitely a problem with TWRP. His tablet is back to the way it was before the fiasco and he is afraid to do anything else.
Click to expand...
Click to collapse
Are you sure about this???
Because TWRP 2.6.3.0 was too big for the recovery partition of the TF700 and never properly installed????
For any reliable advice you need to provide the bootloader version (which you still haven't given us) and if you have a working system, you should be able to boot into recovery and give us it's version number.
For installing CM 11 on the TF700 you need to be on the 10.6.1.14.10 bootloader and have the CWM 6.0.4.6 recovery.
TWRP 2.6.3.2 supposedly works with CM 11, but I would not trust it - read about too many problems with it....
And anyway - in terms of performance, neither CM 10.2 or CM 11 beats CROMi-X on this tablet - period.
Here I am
berndblb said:
Are you sure about this???
Because TWRP 2.6.3.0 was too big for the recovery partition of the TF700 and never properly installed????
For any reliable advice you need to provide the bootloader version (which you still haven't given us) and if you have a working system, you should be able to boot into recovery and give us it's version number.
For installing CM 11 on the TF700 you need to be on the 10.6.1.14.10 bootloader and have the CWM 6.0.4.6 recovery.
TWRP 2.6.3.2 supposedly works with CM 11, but I would not trust it - read about too many problems with it....
And anyway - in terms of performance, neither CM 10.2 or CM 11 beats CROMi-X on this tablet - period.
Click to expand...
Click to collapse
Hey guys, this is Wade, the cause of the whole fiasco.
It was the newest TWRP 2.3.6.2, but I imagine it might've been a problem with the bootloader? I had no idea that the bootloader needed updating; I thought that once you could boot what you wanted, that was it, but obviously I'm mistaken. Where do I find the bootloader version? It was the latest posting to the Asus download site, or the V8, 2013 bootloader edition for JB. 4.2
Basically, I had tried several times that day installing CM11 and the gapps with CWM 6.0.3.1 (which ROM manager says is the up to date version? WTF?) to no avail. It kept giving me md5sum errors, and I couldn't find anything to easily fix that. CWM would also not respond to commands from ROM manager other than backups... If i told it to bootload and flash, it would just reboot normally... ADB also would fail, despite saying that i COULD connect to fastboot.
So i read on the actual CM forum that the newest TWRP 2.6.3.2 would do the trick as well, and tried that. But ya, once i booted into twrp, it threw a password query at me. I never set a password, so I pressed cancel, and that's when the partition showed up as blank.
I went to reboot, but it warned that I had no OS installed. That's about when I freaked out. It would see my microSD fine, but wasn't able to talk to /system to actually flash anything, and ADB would just give "error:closed" if I tried any mount commands there.
So ya, I invited my buddy over, and he recommended we try flashing an old CROMI-X, and it WORKED! sort of. It started to flash, even though a previous CM 10.2 and it's gapps (which I was already running and knew worked) wouldn't!
Then it froze installing Youtube, and after ten mins we held down the power.
And it booted back into CM 10.2 like nothing had happened.
Even though TWRP said I had succesfully factory reset AND wiped AND formatted the internal by that point. Lies!
So ya, I imagine it's a combination of pilot error, and TWRP being a little fluky. My question - where did that 87% CROMI-X flash go, and how can I get rid of it? And i reflashed CWM 6.0.3.1, but I'm still wary of going into the bootloader, just in case bastard TWRP is still lurkin
UPDATE
Wadesauce said:
I had no idea that the bootloader needed updating; I thought that once you could boot what you wanted, that was it, but obviously I'm mistaken. Where do I find the bootloader version? It was the latest posting to the Asus download site, or the V8, 2013 bootloader edition for JB. 4.2
Click to expand...
Click to collapse
So it was definitely the old ASUS 4.2 bootloader I was using. I had no idea that dasunsrule32 wanted us to use his April 2013 bootloader for 10.2 as well, the site that told me how to put CM 10.2 on my tab said to use the old ASUS one.
Finally manned up and tried my first soft reboot, and it brought up the ASUS menu with the blue loading bar - it seemed like it wanted to go into bootloader. Then it went blank and the regular ASUS logo showed, and then the CM logo and booted. So i didn't walk away from this unscathed; something low-down got messed with...
Can I update the bootloader to his, despite the problems ive been having? How do I do that?
And why does ROM manager only offer 6.0.3.1??
And since CM11 is based on 4.4, wont it eventually be better than CROMi-X?
Wadesauce said:
So it was definitely the old ASUS 4.2 bootloader I was using. I had no idea that dasunsrule32 wanted us to use his April 2013 bootloader for 10.2 as well, the site that told me how to put CM 10.2 on my tab said to use the old ASUS one.
So can I update the bootloader to his, despite the problems ive been having? How do I do that?
And why does ROM manager only offer 6.0.3.1??
And since CM11 is based on 4.4, wont it eventually be better than CROMi-X?
Click to expand...
Click to collapse
Can you still boot into fastboot mode on your tablet and can your PC see the tablet in fastboot mode?? What is the OS on your PC??
i dunno
lj50036 said:
Can you still boot into fastboot mode on your tablet and can your PC see the tablet in fastboot mode?? What is the OS on your PC??
Click to expand...
Click to collapse
I haven't tried booting into bootloader, or even a full power down/power up yet. This is the device I use for school and right now would be a pretty sh**y time for anything serious to happen to it.
I am mainly afraid that TWRP hasn't left yet, or that I won't be able to access the CWM that ROM manager says I just successfully reflashed.
I don't really want to plug it back into the computer until I know more about what happened to it. Is it likely that the CROMI that we tried flashing or the old TWRP will cause me problems? Remember that CROMI said it was 87% successful (had loaded kernel and system and all that jazz)
And I have 64 bit Win7, it should have appropriate drivers
Feedback
Wadesauce said:
I haven't tried booting into bootloader, or even a full power down/power up yet. This is the device I use for school and right now would be a pretty sh**y time for anything serious to happen to it.
I am mainly afraid that TWRP hasn't left yet, or that I won't be able to access the CWM that ROM manager says I just successfully reflashed.
I don't really want to plug it back into the computer until I know more about what happened to it. Is it likely that the CROMI that we tried flashing or the old TWRP will cause me problems? Remember that CROMI said it was 87% successful (had loaded kernel and system and all that jazz)
And I have 64 bit Win7, it should have appropriate drivers
Click to expand...
Click to collapse
Well you just let me know.. I will be here to help out if you would like it ....As always thx lj
Wadesauce said:
Hey guys, this is Wade, the cause of the whole fiasco.
It was the newest TWRP 2.3.6.2, but I imagine it might've been a problem with the bootloader? I had no idea that the bootloader needed updating; I thought that once you could boot what you wanted, that was it, but obviously I'm mistaken. Where do I find the bootloader version? It was the latest posting to the Asus download site, or the V8, 2013 bootloader edition for JB. 4.2
Basically, I had tried several times that day installing CM11 and the gapps with CWM 6.0.3.1 (which ROM manager says is the up to date version? WTF?) to no avail. It kept giving me md5sum errors, and I couldn't find anything to easily fix that. CWM would also not respond to commands from ROM manager other than backups... If i told it to bootload and flash, it would just reboot normally... ADB also would fail, despite saying that i COULD connect to fastboot.
So i read on the actual CM forum that the newest TWRP 2.6.3.2 would do the trick as well, and tried that. But ya, once i booted into twrp, it threw a password query at me. I never set a password, so I pressed cancel, and that's when the partition showed up as blank.
I went to reboot, but it warned that I had no OS installed. That's about when I freaked out. It would see my microSD fine, but wasn't able to talk to /system to actually flash anything, and ADB would just give "error:closed" if I tried any mount commands there.
So ya, I invited my buddy over, and he recommended we try flashing an old CROMI-X, and it WORKED! sort of. It started to flash, even though a previous CM 10.2 and it's gapps (which I was already running and knew worked) wouldn't!
Then it froze installing Youtube, and after ten mins we held down the power.
And it booted back into CM 10.2 like nothing had happened.
Even though TWRP said I had succesfully factory reset AND wiped AND formatted the internal by that point. Lies!
So ya, I imagine it's a combination of pilot error, and TWRP being a little fluky. My question - where did that 87% CROMI-X flash go, and how can I get rid of it? And i reflashed CWM 6.0.3.1, but I'm still wary of going into the bootloader, just in case bastard TWRP is still lurkin
Click to expand...
Click to collapse
Jeez - where to start?
First of all: Do yourself a favor and ditch ROM Manager. It does not work well with the TF700 and several people have hard bricked using it. You have been very lucky so far!
Second: Do not flash anything until you are 150% sure you know what you are doing, you understand the requirements for your situation and have everything you need at hand.
Do not flash anything EVER if you do not know what bootloader version you have. That's like getting into your car blind folded and trusting that your GPS will drive you safely to your destination.
Every ROM has it's requirements in terms of bootloader version and recovery and they are usually clearly stated in the first couple of paragraphs in the OP of the rom thread. If not: Stay away from that rom unless you know exactly what you are doing!
TWRP 2.6.3.2 has major issues when formatting data from it. Stay away from it for now.
To find out what you can do to get a stable system back, you need to know where you are and what you have.
Boot into the bootloader (and do not use ROM Manager to do it!) and read the tiny script. It'll probably be 10.6.1.14.10 or .8
Post the result.
Boot into the recovery to check what you have installed. Versions matter!
The proper way of installing a custom recovery is in fastboot mode. Which is different from ADB, btw - you've been mixing those up I think.
Google "adb fastboot tutorial" and do some reading. Once you understand, get it set up on your PC, boot the tablet into the bootloader, connect both via original USB cable and test the connection with
Code:
fastboot devices
If it returns the serial number of your tablet, you are in business and we can continue from there.
Happy studying!
Getting there...
berndblb said:
Google "adb fastboot tutorial" and do some reading. Once you understand, get it set up on your PC, boot the tablet into the bootloader, connect both via original USB cable and test the connection with
Code:
fastboot devices
If it returns the serial number of your tablet, you are in business and we can continue from there.
Happy studying!
Click to expand...
Click to collapse
Alright, I have done some reading as far as all of this goes. I understand a lot of it better now.
So I'm positive now that it was because I hadn't updated my bootloader before trying through CWM. And TWRP obviously was no more useful.
I haven't quite checked what the bootloader version is - I think there may be something wrong with it still (given my weird boot-up) and I don't want to go there until I'm totally sure what I'm doing. I'd hate to hit bootloader and then realize something was seriously wrong, and my time was ticking.
However, I have never changed the bootloader since I used ASUS's one from their website originally - since it says v8, I imagine thats the .8 one?
Before I uninstalled ROM manager, I checked what it said my recovery was - and it said I had CWM 6.0.3.1 still, even though the TWRP fiasco has just gone down. I used ROM to reflash the same 6.0.3.1 from the device, and it said it was successful.
So before I begin, could i possibly ask a few questions?
1) Could I have corrupted the bootloader?
2) Can more than one recovery exist? Is it maybe true that CWM 6.0.3.1 would be the one I will boot into if I went into recovery? I REALLY don't want it to be TWRP again as it might not survive the experience (I had put TWRP on via fastboot). Should I just get to bootloader, flash a new recovery right away and go from there?
3) When I go to finally solve it, what are the hypothetical steps I should take? Right now, as far as I can tell, it will be:
a) Make sure all drivers are working, and files (including backup) are on my PC.
b) reboot into bootloader, check version.
c) flash the 10.6.1.14.4 bootloader
d) reboot
e) reboot into bootloader
f) flash CWM. 6.0.4.6
g) reboot
i) reboot into bootloader, into recovery, then flash CM 11 and gapps
j) reboot
Ya? No? Any help would be appreciated
Wadesauce said:
Alright, I have done some reading as far as all of this goes. I understand a lot of it better now.
So I'm positive now that it was because I hadn't updated my bootloader before trying through CWM. And TWRP obviously was no more useful.
I haven't quite checked what the bootloader version is - I think there may be something wrong with it still (given my weird boot-up) and I don't want to go there until I'm totally sure what I'm doing. I'd hate to hit bootloader and then realize something was seriously wrong, and my time was ticking.
However, I have never changed the bootloader since I used ASUS's one from their website originally - since it says v8, I imagine thats the .8 one?
Before I uninstalled ROM manager, I checked what it said my recovery was - and it said I had CWM 6.0.3.1 still, even though the TWRP fiasco has just gone down. I used ROM to reflash the same 6.0.3.1 from the device, and it said it was successful.
So before I begin, could i possibly ask a few questions?
1) Could I have corrupted the bootloader?
2) Can more than one recovery exist? Is it maybe true that CWM 6.0.3.1 would be the one I will boot into if I went into recovery? I REALLY don't want it to be TWRP again as it might not survive the experience (I had put TWRP on via fastboot). Should I just get to bootloader, flash a new recovery right away and go from there?
3) When I go to finally solve it, what are the hypothetical steps I should take? Right now, as far as I can tell, it will be:
a) Make sure all drivers are working, and files (including backup) are on my PC.
b) reboot into bootloader, check version.
c) flash the 10.6.1.14.4 bootloader
d) reboot
e) reboot into bootloader
f) flash CWM. 6.0.4.6
g) reboot
i) reboot into bootloader, into recovery, then flash CM 11 and gapps
j) reboot
Ya? No? Any help would be appreciated
Click to expand...
Click to collapse
1. No, your bootloader is still good because you still can boot into your system. You need your bootloader to initiate your hardware before your OS is booting.. I am very sure that is the case but it would be nice for someone to confirm it...
2. Your recovery partition is too small for two custom recoveries to exist. So it is almost impossible for you to have two recoveries..
Before you want to go further, it is easier to find out your bootloader and recovery versions so you know what is the next step that you need to do. Otherwise, it is just a guess or a shot in the dark... I think that you are fine but you need to wait for some experts to confirm it... Good luck...:fingers-crossed:
Please bear with me
LetMeKnow said:
Before you want to go further, it is easier to find out your bootloader and recovery versions so you know what is the next step that you need to do. Otherwise, it is just a guess or a shot in the dark... I think that you are fine but you need to wait for some experts to confirm it... Good luck...:fingers-crossed:
Click to expand...
Click to collapse
Sorry hahah, I know I must seem really frustrating...
I have held off for 2 reasons:
1. The first time I did a soft reboot after my fiasco, upon boot it went through the first series of steps trying to load into the bootloader, but then booted fine. Another time a few days after, it rebooted while i was using it, and just went blank after the asus logo. Holding the power down caused it to boot fine. Still, neither of those had ever happened before, and I am pretty sure that some point along the line of bootloader-->OS something is broken. Hopefully on the OS side.
2. I am not going to attempt to boot into recovery until I know that it isn't the same TWRP 2.6.3.2 that got me into this whole fiasco. I know it sounds like a catch 22, not wanting to reboot into recovery to check what it is, but I have NO IDEA how to get out of this TWRP as it stands. I had to flash a CROMI (which failed at 87%) and hard reboot. Not willing to go out on a limb and assume that hard-reboot will work during any step of that process.
So, why do I have to check it? Can't I boot into bootloader, flash a new bootloader, flash a new recovery, and then reboot normally? Assuming I'll be able to establish fastboot (drivers still work, so fingers crossed on that one).
Ive tried to install TWRP via adb about 3 times now and it just will not work. The install goes perfectly but when i try to enter recovery mode from the phone being turned off, it just infinitely says my phone is booting. Does not go into twrp at all. My Nougat installation is extremely buggy. I have no model number, i went through complete hell to even enter my google account info. Everything seems to work fine on nougat though but i just cannot stand the bugged installation. Could really use some help.....
EDIT: Flashed TWRP through adb sideload and the phone just sits there still even when i enabled usb debugging and all. Bluetooth doesnt work and NFC doesnt work. But everything else works perfectly fine. It would just be nice to get the full functionality of my phone back. Phone isnt rooted. Just need some quick assistance.... Thanks for whomever answers.
United States user
Huawei NXT-L29
Android 7.0
have you tried to flash through fastboot the twrp in this thread? http://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617 (do not worry if is for mate 9. it works anyway)
also please check if your bootloader is unlocked before doing it.
download srk huawei tool, is pretty easy to use: http://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
First you need to roll back to ur previous firmware.
You can try dload method using ur previous firmware or use rollback package.http://forum.xda-developers.com/mate-8/general/best-easiest-to-rollback-to-emui-4-0-t3507399/page1
When ur back with a working firmware,you have to unlock bootloader if its locked again,and flash twrp.
Once done u have to download nougat firmware with the data zip ment for ur region.
Go to twrp install the 2 zips( firmware and data) than reboot.
If the phone didn't boot after 10 minutes ,reboot into recovery( twrp will be replaced with stock recovery after installing the zips) and do factory reset.
Omg i forgot that the bootloader might be locked.. Ill try to find the comand to put my unlock code in and get back to this thread.. Thanks so much for suggestions.. Though ive had tkbdeal with it nougat is FANTASTIC
UPDATE: So far nothing is working. Tried the rollback packages and im still on nougat. I have an actual firmware version now. But its Russian firmware? Trying the dload method with L29185 firmwares like 200 and 320 and nothing works. Tried many things and now i cannot even install twrp. The install process would work it just wouldnt do anything when i tried to boot to twrp but now when i try to flash twrp over the recovery it just completely fails. no error code it just says it cannot find a file by that name or it cannot read it. adb says the bootloader is unlocked. Am i just completely stuck here on a buggy nougat installation? Is there any way to force a twrp backup to load outside of twrp?
gm007 said:
First you need to roll back to ur previous firmware.
You can try dload method using ur previous firmware or use rollback package.http://forum.xda-developers.com/mate-8/general/best-easiest-to-rollback-to-emui-4-0-t3507399/page1
When ur back with a working firmware,you have to unlock bootloader if its locked again,and flash twrp.
Once done u have to download nougat firmware with the data zip ment for ur region.
Go to twrp install the 2 zips( firmware and data) than reboot.
If the phone didn't boot after 10 minutes ,reboot into recovery( twrp will be replaced with stock recovery after installing the zips) and do factory reset.
Click to expand...
Click to collapse
ok so now most of this is done. Excuse me for pulling you aside I do hope you reply. Im having an issue getting twrp to work. Im on an official stock firmware. Bootloader unlocked, flashed twrp and im stuck at the screen that says my device cannot be trusted. Its on its way to booting to twrp but it completely wont. Its just stuck at that screen for about 5 minutes now. Ive let it ride and i think its just frozen there. Any ideas? im using the twrp posted by the commenter above you. The 3.0.2-1 and this is where im at.
Well now i cannot get my phone to stop wanting to factory reset itself. It keeps trying to boot into recovery and twrp is flashed over stock recovery and twrp still wont boot even though bootloader is unlocked. it freezes at the unsafe device booting screen every time it starts. I think this phone is bricked beyond repair now. Nougat update completely ruined my phone.
OcazPrime said:
ok so now most of this is done. Excuse me for pulling you aside I do hope you reply. Im having an issue getting twrp to work. Im on an official stock firmware. Bootloader unlocked, flashed twrp and im stuck at the screen that says my device cannot be trusted. Its on its way to booting to twrp but it completely wont. Its just stuck at that screen for about 5 minutes now. Ive let it ride and i think its just frozen there. Any ideas? im using the twrp posted by the commenter above you. The 3.0.2-1 and this is where im at.
Click to expand...
Click to collapse
That twrp is for mate 9 and will not work for mate 8 you need to fastboot another twrp. You need to flash another twrp you can try the twrp for the honor 8 which will work on mate 8
http://forum.xda-developers.com/honor-8/how-to/twrp-nougat-edition-t3504140
You will be to get into this twrp but not all functions are working.
---------- Post added at 02:03 AM ---------- Previous post was at 01:59 AM ----------
OcazPrime said:
Well now i cannot get my phone to stop wanting to factory reset itself. It keeps trying to boot into recovery and twrp is flashed over stock recovery and twrp still wont boot even though bootloader is unlocked. it freezes at the unsafe device booting screen every time it starts. I think this phone is bricked beyond repair now. Nougat update completely ruined my phone.
Click to expand...
Click to collapse
As long as you can get into fastboot mode, you can recover. Try to flash the nougat stock recovery then use the rollback package (try all three to see which one work) then you can dload back to your previous rom.
---------- Post added at 02:06 AM ---------- Previous post was at 02:03 AM ----------
Icchan said:
have you tried to flash through fastboot the twrp in this thread? http://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617 (do not worry if is for mate 9. it works anyway)
also please check if your bootloader is unlocked before doing it.
download srk huawei tool, is pretty easy to use: http://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
Click to expand...
Click to collapse
Did you try it and it works for you? I flashed this twrp and my phone just get stuck at the screen "your phone is booting" and I have to flash another twrp.
In total what ive done up to my current state:
Flashed nougat in. Installed wrong tried reverting and noticed twrp wouldnt boot. Downloaded rollback packages. Only the russian one worked and ended up on C636B180 firmware. Checked my other recovery thread for twrp and got twrp working finally. TWRP wont flash any roms for some reason. When it flashes roms it doesnt actually install anything. When i boot it just sits there on the screen you get with an unlocked bootloader i havent let it sit there for long because when i get back into twrp and check the file manager, there are no files in sdcard. So my rom straight up didnt install. When i check it on my pc the storage size hasnt decreased at all. Its just completely screwed right now and im so frustrated im probably getting a new phone.
OcazPrime said:
In total what ive done up to my current state:
Flashed nougat in. Installed wrong tried reverting and noticed twrp wouldnt boot. Downloaded rollback packages. Only the russian one worked and ended up on C636B180 firmware. Checked my other recovery thread for twrp and got twrp working finally. TWRP wont flash any roms for some reason. When it flashes roms it doesnt actually install anything. When i boot it just sits there on the screen you get with an unlocked bootloader i havent let it sit there for long because when i get back into twrp and check the file manager, there are no files in sdcard. So my rom straight up didnt install. When i check it on my pc the storage size hasnt decreased at all. Its just completely screwed right now and im so frustrated im probably getting a new phone.
Click to expand...
Click to collapse
If you are back to C636B180 firmware, you need to unlock the phone, flash twrp, which is fully working in emui 4, root the phone then use SRK to change to the software region you want:
http://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
Can i just download a superuser zip and flash it with twrp to root? Havemt rooted this phone in forever cuz i never did much with it since my first and only rooting
The reason why recovery doesn't work is due to kernel isn't supported on new bootloader
LastStandingDroid said:
The reason why recovery doesn't work is due to kernel isn't supported on new bootloader
Click to expand...
Click to collapse
What?
The previous twrp version doesn't work on nougat due to kernel.
I guess it's selected by bootloader or the new teecd
You can download twrp as mentioned here
http://forum.xda-developers.com/showthread.php?p=70126187
Also @tknguyencsu what works in that version for your mate 8?
Does MTP work and adb?
Data won't work unless you use encrypted version.
Sent from my FRD-L09 using Tapatalk
OcazPrime said:
Ive tried to install TWRP via adb about 3 times now and it just will not work. The install goes perfectly but when i try to enter recovery mode from the phone being turned off, it just infinitely says my phone is booting. Does not go into twrp at all. My Nougat installation is extremely buggy. I have no model number, i went through complete hell to even enter my google account info. Everything seems to work fine on nougat though but i just cannot stand the bugged installation. Could really use some help.....
EDIT: Flashed TWRP through adb sideload and the phone just sits there still even when i enabled usb debugging and all. Bluetooth doesnt work and NFC doesnt work. But everything else works perfectly fine. It would just be nice to get the full functionality of my phone back. Phone isnt rooted. Just need some quick assistance.... Thanks for whomever answers.
United States user
Huawei NXT-L29
Android 7.0
Click to expand...
Click to collapse
Budy I have same problem Pls note me when u find somethıng :=)) ıf I then ı will let u know.
TWRP Recovery 3.0.3
Download TWRP Recovery 3.0.3
http://sillanwali.com/downloads/twp-3.0.3.img
I was on 5.1.8 and updated to 5.1.9 but for some reason the phone boots, goes to the OS but immediately shows the shutting down dialog box and reboots the phone to recovery.
I tried reinstalling 5.1.9 with and without root but have the same result. I have tried with and without permanent twrp. The only thing I haven't tried is a factory reset as I am abroad and cannot afford to lose all my info (especially whatsapp as I won't be able to set it back up until 2 weeks when I return home).
Has anyone encountered anything like this or know how to fix it?
toyanucci said:
I was on 5.1.8 and updated to 5.1.9 but for some reason the phone boots, goes to the OS but immediately shows the shutting down dialog box and reboots the phone to recovery.
I tried reinstalling 5.1.9 with and without root but have the same result. I have tried with and without permanent twrp. The only thing I haven't tried is a factory reset as I am abroad and cannot afford to lose all my info (especially whatsapp as I won't be able to set it back up until 2 weeks when I return home).
Has anyone encountered anything like this or know how to fix it?
Click to expand...
Click to collapse
Share this with OnePlus team on Twitter too until someone help you here too.
If MTP supported by your TWRP then copy the data? If TWRP is still there.
mjp93 said:
Share this with OnePlus team on Twitter too until someone help you here too.
If MTP supported by your TWRP then copy the data? If TWRP is still there.
Click to expand...
Click to collapse
MTP doesn't work but adb works. I have reinstalled 5.1.9 after doing a full wipe and still the phone reboots to recovery after trying to boot normally.
Can anyone help me please :crying::crying::crying::crying:
toyanucci said:
I was on 5.1.8 and updated to 5.1.9 but for some reason the phone boots, goes to the OS but immediately shows the shutting down dialog box and reboots the phone to recovery.
I tried reinstalling 5.1.9 with and without root but have the same result. I have tried with and without permanent twrp. The only thing I haven't tried is a factory reset as I am abroad and cannot afford to lose all my info (especially whatsapp as I won't be able to set it back up until 2 weeks when I return home).
Has anyone encountered anything like this or know how to fix it?
Click to expand...
Click to collapse
Just dirty flash 5.1.8 system update in TWRP, reflash TWRP, reboot recovery, flash magisk. You shouldn't have to wipe data if there were no problems in previous OS and forcing a shutdown shouldn't be due to data anyway. You could also try to dirty flash 5.1.9 again with those steps. Has to be the full ROM.
mikex8593 said:
Just dirty flash 5.1.8 system update in TWRP, reflash TWRP, reboot recovery, flash magisk. You shouldn't have to wipe data if there were no problems in previous OS and forcing a shutdown shouldn't be due to data anyway. You could also try to dirty flash 5.1.9 again with those steps. Has to be the full ROM.
Click to expand...
Click to collapse
I'm travelling and the hotel wifi is super slow. I have the full 5.1.9 and I've tried dirty flashing and clean flashing (I did a nandroid backup first). With a dirty flash the phone boots to the lockscreen but immediately says shutting down and reboots, after the reboot it goes to recovery (stock or twrp whichever is installed). After a clean flash it seems to try to boot then just shuts off and reboots to whichever recovery is installed.
I've set 5.1.8 to download which will take HOURS so I'll report back with any update. I pray this fixes it...
toyanucci said:
MTP doesn't work but adb works. I have reinstalled 5.1.9 after doing a full wipe and still the phone reboots to recovery after trying to boot normally.
Can anyone help me please :crying::crying::crying::crying:
Click to expand...
Click to collapse
In thw worst case, since ADB works, you can backup your entire internal storage to your computer and factory reset. Use adb-sync for this.
Pat123 said:
In thw worst case, since ADB works, you can backup your entire internal storage to your computer and factory reset. Use adb-sync for this.
Click to expand...
Click to collapse
I did a factory reset (didn't wipe internal storage) after doing the nandroid backup and it had the same issue where it tried to boot then screen went black and it rebooted to recovery
mikex8593 said:
Just dirty flash 5.1.8 system update in TWRP, reflash TWRP, reboot recovery, flash magisk. You shouldn't have to wipe data if there were no problems in previous OS and forcing a shutdown shouldn't be due to data anyway. You could also try to dirty flash 5.1.9 again with those steps. Has to be the full ROM.
Click to expand...
Click to collapse
5.1.8 should be flashed again over current 5.1.8?
Why not just tell twrp to switch back to other slot with working oos. I am missing something that this was not tried yet?
MrSteelX said:
Why not just tell twrp to switch back to other slot with working oos. I am missing something that this was not tried yet?
Click to expand...
Click to collapse
I tried changing slots in twrp. Slot A boots to lockscreen then powers off and boots to recovery. Slot B doesn't boot at all and just shows a light blue notification LED.
toyanucci said:
I did a factory reset (didn't wipe internal storage) after doing the nandroid backup and it had the same issue where it tried to boot then screen went black and it rebooted to recovery
Click to expand...
Click to collapse
I meant take backup through ADB, format everything including data, internal storage, then fastboot flash full ROM zip.
I am having the same exact issue.
Can't restore a nandroid backup. All I get is light blue notification LED. I tried 5.1.8 and 5.1.9. With TWRP right after and without it. Without even magisk. It just bootloops forever. If I install 5.1.9/5.1.8 full zips, twrp, reboot recovery, magisk. It just reboots into twrp. I can't even install any of the full ota zips. It wont get past the android boot animation when I just want to flash the ota zip only. Can't get out of twrp. Luckily I was able to backup everything, but don't know how to proceed further allowing me to regain usage of my phone.
To me, this is sounding like something did not flash right with vendor partition.
if a full wipe of System, data, internal storage, the whole 9 yards doesn't work. The only option I see that should work is the mega unbrick thread. https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
MrSteelX said:
To me, this is sounding like something did not flash right with vendor partition.
Click to expand...
Click to collapse
Any suggestions how to fix this. I am hoping I dont have to use the MSM tool and start all the way from scratch.
garz said:
Any suggestions how to fix this. I am hoping I dont have to use the MSM tool and start all the way from scratch.
Click to expand...
Click to collapse
Did you make sure the download was not corrupt before flashing? OnePlus6Oxygen_22_OTA_013_all_1807130145_92ea1c670c0fae.zip MD5 61EAE0DA48C6B3914F48F3E6EA99A74B
Yes, everything matched up. I guess I need to start from scratch.
---------- Post added at 10:25 AM ---------- Previous post was at 10:08 AM ----------
This guy's tool worked like a champ for me. Didn't have to delete everything in storage.
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665/
garz said:
Yes, everything matched up. I guess I need to start from scratch.
---------- Post added at 10:25 AM ---------- Previous post was at 10:08 AM ----------
This guy's tool worked like a champ for me. Didn't have to delete everything in storage.
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665/
Click to expand...
Click to collapse
Funny, I was about post that link but i see you found it first. It is also good that it fixed it for you.
As far as TWRP backups, you only need to backup data. You can just install the full ROM zip file and restore data to get everything back if you have issues with nandroid restore. Just don't forget to flash TWRP before rebooting or you will need to fastboot it again.
Maybe an issue with battery calibration. Try checking the battery when the phone just boots. If it says low battery and because of that its shutting down then its just a software error and just try to turn in the phone with charger connected to check if tgats the problem. If that dosent work try the oneplus 6 mega unbrick guide and return to stock oos 5.1.5 using snapdragon msm recovery tool. For detailed info see tge OP6 unbrick guide on xda. Tell me if it works
toyanucci said:
I tried changing slots in twrp. Slot A boots to lockscreen then powers off and boots to recovery. Slot B doesn't boot at all and just shows a light blue notification LED.
Click to expand...
Click to collapse
One question, when you manually change to slot B, you're in a black screen with blue notification LED right? If that doesn't even go fastboot, how do you get out of that slot into the other one again to the boot-recovery loop?