[Q]InvalidState on bootloader for Nexus 7 (2012) Wifi Lollipop flash - Nexus 7 Q&A, Help & Troubleshooting

When I obtained the Lollipop image for the 2012 Wifi Nexus 7 (nakasi-lrx21p-factory-93daa4d3.tgz), I didn't want to lose my user data nor all the files on my media partition (TiBu backups, etc), so I unzipped all the images and flashed them manually so that it wouldn't erase the userdata partition.
First, I attempt to flash the bootloader, but using stupid auto-complete in the command window, I accidentally flashed boot.img instead of bootloader-grouper-4.23.img to the bootloader partition. I immediately saw what I did and panicked. I didn't reboot and then I tried to flash bootloader-grouper-4.23.img. Everytime that happens, this is what I get:
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.433s
rebooting into bootloader...
I decided to just go ahead and continue flashing everything else and it all seemed to be fine. I booted into Lollipop without any issues.
However, I was having some performance issues, so I decided to backup my media partition and go ahead and reflash it, having it wipe everything. This time, I used the enclosed flash-all.bat script and I noticed I still get the "InvalidState" when attempting to write to the bootloader.
When I flashed the boot.img to the bootloader partition, did I screw something up? Or, is there something wrong with the image Google provided and it's nothing to worry about?
I was able to install TWRP and root it, so obviously, there isn't that much of an issue, but I'm just wondering if everyone else is getting this message?
I am using the correct factory image from Google: nakasi-lrx21p-factory-93daa4d3.tgz
Thanks for any help with this. I guess I don't have anything to worry about since it flashes everything else fine and boots up, but I would like to make sure.

iBolski said:
When I obtained the Lollipop image for the 2012 Wifi Nexus 7 (nakasi-lrx21p-factory-93daa4d3.tgz), I didn't want to lose my user data nor all the files on my media partition (TiBu backups, etc), so I unzipped all the images and flashed them manually so that it wouldn't erase the userdata partition.
First, I attempt to flash the bootloader, but using stupid auto-complete in the command window, I accidentally flashed boot.img instead of bootloader-grouper-4.23.img to the bootloader partition. I immediately saw what I did and panicked. I didn't reboot and then I tried to flash bootloader-grouper-4.23.img. Everytime that happens, this is what I get:
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.433s
rebooting into bootloader...
I decided to just go ahead and continue flashing everything else and it all seemed to be fine. I booted into Lollipop without any issues.
However, I was having some performance issues, so I decided to backup my media partition and go ahead and reflash it, having it wipe everything. This time, I used the enclosed flash-all.bat script and I noticed I still get the "InvalidState" when attempting to write to the bootloader.
When I flashed the boot.img to the bootloader partition, did I screw something up? Or, is there something wrong with the image Google provided and it's nothing to worry about?
I was able to install TWRP and root it, so obviously, there isn't that much of an issue, but I'm just wondering if everyone else is getting this message?
I am using the correct factory image from Google: nakasi-lrx21p-factory-93daa4d3.tgz
Thanks for any help with this. I guess I don't have anything to worry about since it flashes everything else fine and boots up, but I would like to make sure.
Click to expand...
Click to collapse
I got the same 'Invalid State' error that you did although I didn't accidentally flash anything else.. I just ran through the ./flash-all.sh script and it just straightup failed while trying to flash the bootloader.. and then it just barreled ahead and deleted my recovery partition + everything else haha. So now I'm in a state where I can't boot at all, not even into recovery @[email protected]
Sorry, that was no help haha, just wanted to let you know that I've seen the Invalid State error as well.

I had that when I did a fastboot install of lollipop. Just ignored it and moved on as version was identical anyway

I had this same problem. What I ended up doing was downloading the Nexus Root Kit and then using that to flash the individual files and it worked fine for me. Though, now I got to figure out how to get the system to know there are actually 16GB of storage and not 6GB.
Edit: I found out what needed to be done. I just needed to do a factory reset.

This has been a known problem on Grouper for nearly a year now.
http://forum.xda-developers.com/showthread.php?t=2573015

SteveRiley said:
This has been a known problem on Grouper for nearly a year now.
http://forum.xda-developers.com/showthread.php?t=2573015
Click to expand...
Click to collapse
Thanks. I knew about that one on previous releases. I just wasn't sure if it was the same issue.
Nice to know it's nothing to worry about, but I just about had a heart attack when I realized that I flashed boot.img to the bootloader (or at least tried) and I wasn't sure if I had just perma-bricked my Nexus.
Thank goodness it didn't. I'm sure there are some safeguards from allowing that from happening and it's probably more it I were to flash something else to the boot partition that would cause an issue.
Anyways, thanks for the reminder.

iBolski said:
Nice to know it's nothing to worry about, but I just about had a heart attack when I realized that I flashed boot.img to the bootloader (or at least tried) and I wasn't sure if I had just perma-bricked my Nexus.
Thank goodness it didn't. I'm sure there are some safeguards from allowing that from happening and it's probably more it I were to flash something else to the boot partition that would cause an issue.
Click to expand...
Click to collapse
Well, when I first saw the error about the failed flash to the bootloader partition, I actually did flash the bootloader image to the boot partition. That appeared to work just fine -- no error, and the process finished with a success message. This would have most certainly rendered the OS unbootable, but it wouldn't have bricked the device. That's when I reminded myself that "boot" is not equivalent to "bootloader"! So I reflashed the correct bits to the boot partition.

Related

[HELP]My nexus 4 can not boot even after flash stock image correctly several times!

Hello everyone, I thought I've got a big problem here...
My nexus 4 originally crashed and stuck into a boot loop several days ago, and I flashed stock factory image(4.4.2), then it works again. After that, I imported my backup files into internal storage and using titanium backup restored my apps and data, unfortunately, crashed and boot loop again...So I flashed stock factory image again to find out what reason of this. After several restore from stock factory image, I found that my sms message and many mp3 files could lead to crash, after flash factory image, works fine, use it, reboot it ,fine, but after copy many mp3 files and restore my sms backup(about 2,000+ messages), reboot, stuck into boot loop... Now I try to flash stock image again, however, with no luck to boot my phone...
During my privious several times of flash stock image, it's always hard to boot the machine normally at the first time, I always try to wipe cache, factory reset in recovery even several times to manage to boot the machine normally.
This time when I flash stock image again, I just can't boot my nexus 4 anymore, even wipe cache, factory reset from recovery, whatever other tries...:crying:
Now I even tried several ways to flash stock image(4.4.2, which I used to managed boot up before):
1 Using the newest Nexus Root Toolkit: Boot into bootloader mode and click "Flash Stock+Unroot(soft bricked/boot loop)", everything says OK, however, it just can't boot and stuck in Google logo screen, even after I waited for 2 hours...
2 Using the flash-all.bat: Extract the .tgz image file into a folder which contains adb.exe and fastboot.exe, then execute flash-all.bat, everything reports OK, but just can't boot up, still stuck on Google screen.
3 Manually flash: Extract the .tgz and the .zip, put all files(including boot.zip, system.zip, recovery.zip etc) in one folder, flash bootloader and radio first, then "fastboot flash [partition] *.img", and everything says OK, just can't boot up and stuck on Google screen.
4 Manually flash using 3rd party recovery: Have tried to flash newest CWRP recovery and CMOD recovery separately first, then do manually flash as above.
I even do:
fastboot oem lock
fastboot oem unlock
fastboot reboot-bootloader
fastboot erase system(or fastboot format system)
fastboot erase userdata(or fastboot format userdata)
fastboot erase boot
fastboot erase recovery
fastboot erase cache(or fastboot format cache)
these commands before I try to do the four ways to restore factory image above, but nothing changed.
Now stuck on Google screen, what ever I wipe cache/factory reset how many times, it's just stucked... I even doubt if my flash memory was broken???
PELEASE HELP!
diligentpig said:
Hello everyone, I thought I've got a big problem here...
My nexus 4 originally crashed and stuck into a boot loop several days ago, and I flashed stock factory image(4.4.2), then it works again. After
[Snip]
PELEASE HELP!
Click to expand...
Click to collapse
Flash CWM, wipe the partitions there (But not /boot or /persist, those will hardbrick if you reboot after wiping although I don't think it will let you wipe them), flash the latest radio (.98), and then flash a 4.4 ROM.
If that doesn't work, wait for more responses from others, then try this as a last resort. I suggest that you wait a few days, this can be dangerous
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Follow carefully, and read multiple times before starting. Take it slow and don't panic if the process doesn't go as expected at 85% (Mine wouldn't reboot on its own for some reason, it kept erroring but it was fine and worked itself out)
It should put the phone on a complete clean slate for flashing
Thanks for your reply
lopezk38 said:
Flash CWM, wipe the partitions there (But not /boot or /persist, those will hardbrick if you reboot after wiping although I don't think it will let you wipe them), flash the latest radio (.98), and then flash a 4.4 ROM.
If that doesn't work, wait for more responses from others, then try this as a last resort. I suggest that you wait a few days, this can be dangerous
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Follow carefully, and read multiple times before starting. Take it slow and don't panic if the process doesn't go as expected at 85% (Mine wouldn't reboot on its own for some reason, it kept erroring but it was fine and worked itself out)
It should put the phone on a complete clean slate for flashing
Click to expand...
Click to collapse
Hi lopezk38,
Thanks for your reply! And I do as your instruction:flash newest CWM recovery, then factory rest, wipe cache, and under mouts menu format system/cache/data and firmware(but error), then flash a latest CyanogenMod image for nexus 4, with no luck, everything remains the same
However, I saw the link you provided to unbrick nexus 4, I'll read it carefully several times. At the same time, I'll wait for any other kind help that anyone can provide. If finally there is no other way to repair it, I'll go through with your link.
Thanks again for the tip!
diligentpig said:
Hi lopezk38,
Thanks for your reply! And I do as your instruction:flash newest CWM recovery, then factory rest, wipe cache, and under mouts menu format system/cache/data and firmware(but error), then flash a latest CyanogenMod image for nexus 4, with no luck, everything remains the same
However, I saw the link you provided to unbrick nexus 4, I'll read it carefully several times. At the same time, I'll wait for any other kind help that anyone can provide. If finally there is no other way to repair it, I'll go through with your link.
Thanks again for the tip!
Click to expand...
Click to collapse
Yeah /firmware was another that won't wipe, I just forgot to mention it. Best of luck
It sounds like you have faulty nand block (s). Before no critical parts of the firmware got written to it, so it developed problems when you wrote data to it. Looks like this time you didn't get so lucky, or more failed. If it's under warranty I would RMA it; if it's not, I'm honestly not sure what your best option is. Maybe get one that has broken screen etc, then do a logic board transplant. Good luck.
Sent from my Nexus 4 using Tapatalk
lopezk38 said:
Yeah /firmware was another that won't wipe, I just forgot to mention it. Best of luck
Click to expand...
Click to collapse
I'm going to do the work in the thread you provided now...and will tell you what I've got finally.
consolation said:
It sounds like you have faulty nand block (s). Before no critical parts of the firmware got written to it, so it developed problems when you wrote data to it. Looks like this time you didn't get so lucky, or more failed. If it's under warranty I would RMA it; if it's not, I'm honestly not sure what your best option is. Maybe get one that has broken screen etc, then do a logic board transplant. Good luck.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply. Nexus 4 was not intend to sell to my country, so...Wish me luck
lopezk38 said:
Flash CWM, wipe the partitions there (But not /boot or /persist, those will hardbrick if you reboot after wiping although I don't think it will let you wipe them), flash the latest radio (.98), and then flash a 4.4 ROM.
If that doesn't work, wait for more responses from others, then try this as a last resort. I suggest that you wait a few days, this can be dangerous
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Follow carefully, and read multiple times before starting. Take it slow and don't panic if the process doesn't go as expected at 85% (Mine wouldn't reboot on its own for some reason, it kept erroring but it was fine and worked itself out)
It should put the phone on a complete clean slate for flashing
Click to expand...
Click to collapse
diligentpig said:
Hi lopezk38,
Thanks for your reply! And I do as your instruction:flash newest CWM recovery, then factory rest, wipe cache, and under mouts menu format system/cache/data and firmware(but error), then flash a latest CyanogenMod image for nexus 4, with no luck, everything remains the same
However, I saw the link you provided to unbrick nexus 4, I'll read it carefully several times. At the same time, I'll wait for any other kind help that anyone can provide. If finally there is no other way to repair it, I'll go through with your link.
Thanks again for the tip!
Click to expand...
Click to collapse
Hi, I've carefully read the link several times, and finally go through with it without any problems, and I could flash 4.2.2 stock images and do the 8gb to 16gb part to restore my phone to 16gb storage...However I found that I only can flash 4.2.2 image to make the phone boot up normally, with 4.3 or 4.4.2 image, it fails at boot up. Most important and sad part is, when the phone complete initial setup and install some software, it crash and can not boot again:crying: I've given several tries but the same result.
Finally, I made decision to sold it to buyer who needs only a good glass screen for replacement purpose... Farewell, my nexus4...

[Q] Can't seem to flash or update from fastboot or recovery. HELP

I've never had problems like this and I've been flashing custom roms and recovery since HTC G1 days. Maybe you chaps can enlighten me a bit.
I can boot into all partitions of my device just fine, regular system, recovery, bootloader all okay. My daily rom (Vanir), however, has been getting a little bogged down lately so I'm trying to do an update.
I transferred my rom and gapps files to the sdcard and boot into twrp 2.6.3.1 to update, but lo and behold, the files are now missing. All my other files are there, just not the rom or the gapps. Not too worried yet, I'll just use the sideload method instead.
Start up sideload and watch it transfer over the new rom (MIUI at this point, and I factory reset before hand). From the cmd line I can see it going over just fine and the device seems to be accepting it as well. It gets to 100% and starts a quick error free install on the device, but when I reboot, nothing has been changed and I'm back in Vanir. Okay...I'll update the recovery and see if a new one works.
So I boot into the fastboot to update the recovery.
Code:
fastboot flash recovery openrecovery-twrp-2.7.0.0-grouper.img
Looks good, no error messages, cmd line shows it has been written, so I reboot into my new recovery, only its not new, its still twrp 2.6.3.1 and everything still doesn't work.
Long story long, I also tried installing CWM instead of TWRP -- didn't work, using adb push to move the files and that didn't work, and every time I seem to just lose the zip files after a reboot or update attempt. In fact, when I boot back into Vanir, all my regular files are there, but even though I haven't removed them none of the rom or gapps zips are anywhere. I am sure they have successfully transferred multiple times, but they never seem to make it through a boot sequence.
At this point I'm stuck, and wondering about my boot partitions being messed up. Any help you can provide is much appreciated.
Update, with new information.
I tried to do a complete wipe a la the guide that's stickied in this forum, and it's led me to a bit of new information. It seems that my bootloader is repeatedly failing to update from version 3.23 every time giving either the "InvalidState" error, or when I use older bootloaders that are supposed to work like the JWR66V bootloader mention in this post, it doesn't say "InvalidState" but still fails just the same with a blank where it would say "InvalidState".
I've also realized that none of my changes to my tablet are persisting through a boot sequence. If I download a new app, it is gone upon restarting. In fact, every time I power it up, it downloads the same 3 app updates to the device. Perhaps that can help narrow the problem down a little bit? Sounds like a data wipe is happening every time, but only for changes since I began to try to update the tablet a few days ago, all my files from before the update attempt are never removed or altered at all.
Lastly, according to Rom Manager, I have both TWRP and ClockworkMod as recovery. Actually, that makes me think it might be a boot.img issue. If anyone has any ideas at all, I am open to try any of them at this point. Thanks for reading and for your suggestions in advance!

[Q] Can't finish write to userdata

Nexus 4 with stock (originally 4.4.2), which wouldn't update to 4.4.3, due to TWRP being installed, so when 4.4.4 came around, thought I would download and flash myself. Not a huge expert, but have certainly flashed several phones successfully previously.
Initially using the Nexus Root Toolkit, unrooted etc, downloaded the correct file from https://developers.google.com/android/nexus/images, tried to update, and would not write the radio file (waited for ages), tried to do using adb etc, no go.
Finally downloaded the 4.4.2 image, and using fastboot, this successfully did everything up to userdata, erased userdata successfully, and sent file, but never completes writing. (writing 'userdata'...) If I reboot, just gets stuck on the 4 circles.
Have installed CWM and tried doing a factory reset, but can not mount data....
Anyone able to assist?
Thanks
hornetster said:
Have installed CWM and tried doing a factory reset, but can not mount data....
Anyone able to assist?
Thanks
Click to expand...
Click to collapse
Panic over...
Perseverence seemed to pay off. Just did more of the same, and tried installing the userdata by itself. Seems to have worked.
But now am stock, and still doesn't seem to want to install the updates....
Well, thought it was stock, but the latest OTA didn't install. Don't really know why, as I wasn't watching, but it did the download, then kicked off the install, but when I came back to it, was just sitting at the home screen, no messages and the update hadn't happened - still sitting on 4.4.2.
I had flashed 4.4.2, and I thought the only bit that hadn't worked was the userdata, which I flashed separately, recovery has been flashed to stock recovery...
Why hasn't it updated?
And how can I tell if 'everything' is stock?
Thanks.

Cannot get my Moto X Pure 2015 to do much of anything!

Hello everyone.
Today I decided to wipe my phone and install NucleaRom on it. Everything ran well for a few hours but eventually the device froze, so I rebooted into the bootloader and then into recovery to wipe and restore my backup. The problem is, when the phone tries to wipe the data partition it reboots back into the bootloader.
At this point, I cannot wipe the phone, restore a backup, or reinstall NucleaRom. I just want to get back to stock rooted 7.0, which is how it was yesterday.
Can anyone help me figure this out? I do not have a backup phone and am pretty desperate at this point!
I tried to reflash the stock NPH25.200-22 image using fastboot but I start getting errors and the phone freezes on the bootloader screen. Just completely puzzled! I've been tinkering with Android phones since 2010 and have never run into something this bad before.
I think your problem might be caused by how f2fs is implemented in unofficial TWRP and NucleaROM. It does something to the data partition that doesn't always play nice.
Warning, what I suggest here is going to format your whole data partition. If there's anything on it you'd like to keep, I'd suggest backing it up with TWRPs built-in file manager or over USB to a computer before attempting this.
If I were in your situation, here's what I'd try:
1) Download the latest official TWRP
2) Flash it with fastboot:
Code:
fastboot flash recovery twrp.img
3) Don't reboot normally. Use the volume rocker to select recovery and boot into it.
4) In TWRP select Wipe -> Advanced Wipe
5) Tick the Data box and then hit Repair or Change Filesystem
6) Select Change Filesystem
7) Select F2FS and let it format data
8) Reboot to bootloader and fastboot flash the full firmware package you were trying to. If you were already on that firmware or higher it is normal for bootloader and gpt.bin to fail, you can ignore those errors. Make sure every other step exits successfully, if not then repeat the step.
9) Reboot to system and cross your fingers
I'm not certain this will fix your problem, but if your phone is already non-booting, it isn't going to make it worse.
jason2678 said:
I think your problem might be caused by how f2fs is implemented in unofficial TWRP and NucleaROM. It does something to the data partition that doesn't always play nice.
Warning, what I suggest here is going to format your whole data partition. If there's anything on it you'd like to keep, I'd suggest backing it up with TWRPs built-in file manager or over USB to a computer before attempting this.
If I were in your situation, here's what I'd try:
1) Download the latest official TWRP
2) Flash it with fastboot:
Code:
fastboot flash recovery twrp.img
3) Don't reboot normally. Use the volume rocker to select recovery and boot into it.
4) In TWRP select Wipe -> Advanced Wipe
5) Tick the Data box and then hit Repair or Change Filesystem
6) Select Change Filesystem
7) Select F2FS and let it format data
8) Reboot to bootloader and fastboot flash the full firmware package you were trying to. If you were already on that firmware or higher it is normal for bootloader and gpt.bin to fail, you can ignore those errors. Make sure every other step exits successfully, if not then repeat the step.
9) Reboot to system and cross your fingers
I'm not certain this will fix your problem, but if your phone is already non-booting, it isn't going to make it worse.
Click to expand...
Click to collapse
Thank you for the suggestion! I made the attempt but once my phone tries to format the data partition, it vibrates for about 5 seconds and then reboots back to the bootloader. It has been doing this yesterday every time I would try it. Do you have any suggestions as to why this is, and how to correct it?
I've pretty much given up hope at this point and was going to order a new phone. But it would be nice to get this back in working order so I can resell it or trade it in for a discounted price. The phone has been really good to me over the years and, besides a slightly worn down battery, still works fairly well. Hate to see it turn into a paper-weight when the hardware is still working!
EDIT: Tried the same thing, but this time using ext4 and it worked! Going to try and manually flash the firmware and see what happens!
LyleFerguson said:
Thank you for the suggestion! I made the attempt but once my phone tries to format the data partition, it vibrates for about 5 seconds and then reboots back to the bootloader. It has been doing this yesterday every time I would try it. Do you have any suggestions as to why this is, and how to correct it?
I've pretty much given up hope at this point and was going to order a new phone. But it would be nice to get this back in working order so I can resell it or trade it in for a discounted price. The phone has been really good to me over the years and, besides a slightly worn down battery, still works fairly well. Hate to see it turn into a paper-weight when the hardware is still working!
Click to expand...
Click to collapse
Did you format with the latest official TWRP or the unofficial version of TWRP linked to the NucleaROM OP? There are differences. If one isn't working, try the other. I think it is just a matter of finding the right TWRP version to work with your data partition and reformatting it to fix it. I've also seen formatting it to ext4, then formatting it back to f2fs as a suggested fix for this.
If you just want to try different TWRP versions without constantly flashing new recoveries you can just boot into an image without actually flashing it with fastboot:
Code:
fastboot boot twrp.img
Others have had this problem of not being able to wipe before and solved it. Don't give up. I think you'll find the answer you're after in the official LOS thread or possibly the TWRP thread, but unfortunately with forums there's a lot of noise and the information is quite disjointed.
I've steered clear of the nougat firmware and rebased custom roms myself because it still seems to be in somewhat of a state of flux, so I don't have any firsthand experience with this.
jason2678 said:
Did you format with the latest official TWRP or the unofficial version of TWRP linked to the NucleaROM OP? There are differences. If one isn't working, try the other. I think it is just a matter of finding the right TWRP version to work with your data partition and reformatting it to fix it. I've also seen formatting it to ext4, then formatting it back to f2fs as a suggested fix for this.
If you just want to try different TWRP versions without constantly flashing new recoveries you can just boot into an image without actually flashing it with fastboot:
Code:
fastboot boot twrp.img
Others have had this problem of not being able to wipe before and solved it. Don't give up. I think you'll find the answer you're after in the official LOS thread or possibly the TWRP thread, but unfortunately with forums there's a lot of noise and the information is quite disjointed.
I've steered clear of the nougat firmware and rebased custom roms myself because it still seems to be in somewhat of a state of flux, so I don't have any firsthand experience with this.
Click to expand...
Click to collapse
I used the TWRP that you had linked me. Formatted using ext4 and then tried flashing the files manually with fastboot. My phone is now back to normal!

Any advice on how to boot into os?

So the OS disappeared overnight a couple nights ago and I'm trying everything I can but nothing. I tried the unbricking tool but none work, all get stuck at different times or while trying to perform a task. I've gotten stuck while downloading cache, param, memory size:59.601.....G, recording download time. I also tried to sideload even with the compatibility zip deleted and I still get error 7. I was on 9.0.3 or .4, I forgot, my twrp is 3.2.3-x blu_spark 9.91. Cache, system, vendor, data, firmware all are unable to mount. I tried to repair and change the file system on anything and nothing. I've been trying for almost a week and nothing. I'm starting to lose hope and hope I don't have to buy a new phone. If anyone can help me I would really appreciate it.
delgadoj15 said:
So the OS disappeared overnight a couple nights ago and I'm trying everything I can but nothing. I tried the unbricking tool but none work, all get stuck at different times or while trying to perform a task. I've gotten stuck while downloading cache, param, memory size:59.601.....G, recording download time. I also tried to sideload even with the compatibility zip deleted and I still get error 7. I was on 9.0.3 or .4, I forgot, my twrp is 3.2.3-x blu_spark 9.91. Cache, system, vendor, data, firmware all are unable to mount. I tried to repair and change the file system on anything and nothing. I've been trying for almost a week and nothing. I'm starting to lose hope and hope I don't have to buy a new phone. If anyone can help me I would really appreciate it.
Click to expand...
Click to collapse
Try flashing the Oreo build and update to Pie via OTA.
NGowtham said:
Try flashing the Oreo build and update to Pie via OTA.
Click to expand...
Click to collapse
Ok, I'll try and I'll update.
Update: I tried to sideload 5.1.2 because of no internal storage, and it gave me error 7
delgadoj15 said:
Ok, I'll try and I'll update.
Update: I tried to sideload 5.1.2 because of no internal storage, and it gave me error 7
Click to expand...
Click to collapse
I followed this thread and successfully booted Oreo (5.1.7)
https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
Maybe it will help to upgrade your TWRP? When returning to stock, I used the 3.3.0 Blu_spark.
.vermilion said:
Maybe it will help to upgrade your TWRP? When returning to stock, I used the 3.3.0 Blu_spark.
Click to expand...
Click to collapse
I have tried to flash different versions of TWRP but they all get stuck on writing recovery. I also tried to repair and change each to ex4 or any other type and change back, but I get errors on all.
NGowtham said:
I followed this thread and successfully booted Oreo (5.1.7)
https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
Click to expand...
Click to collapse
I've been trying to use that tool for a week already and it doesn't work I get different messages every time when it gets stuck. I am doing the steps correctly and still nothing. I'm trying different versions and still nothing.
delgadoj15 said:
I have tried to flash different versions of TWRP but they all get stuck on writing recovery. I also tried to repair and change each to ex4 or any other type and change back, but I get errors on all.
Click to expand...
Click to collapse
It even fails when booting to TWRP, install - select image - selecting the new TWRP and install it in the recovery section?
.vermilion said:
It even fails when booting to TWRP, install - select image - selecting the new TWRP and install it in the recovery section?
Click to expand...
Click to collapse
Yes I tried that last night by pushing twrp because of no internal and I selected recovery but it said no recovery partition I believe.
Update: tried again but now no partitions came up to select it to flash to
2nd update: flashed this https://forum.xda-developers.com/oneplus-5/how-to/firmware-modem-collection-flashable-zips-t3627049 ,tried flashing TWRP again through fastboot and got this:
Sending 'recovery' (28672 KB) OKAY [ 0.706s]
Writing 'recovery' FAILED (remote: 'Error flashing partition : Device Error')
fastboot: error: Command failed
Sending 'boot.img' (28672 KB) OKAY [ 0.645s]
Booting OKAY [346.025s]
Finished. Total time: 346.888
3rd update: Flashed twrp 3.3.0 and tried to format data and it booted into the os. Now no more stressing :good:

Categories

Resources