I created a Nandroid of my X Compact running Marshmallow using TWRP (TWRP-3.0.2-3-F5321) last week. TWRP told me the recovery had completed successfully.
When I tried to restore from that recovery today, I received the error message: "Your device has been unlocked and the boot image is not working"
Any ideas as to what I've done wrong?
Seems like something wrong with kernel... Try to reflash your kernel in recovery, fastboot or Flashtool, depending what kernel are you using..
Thanks so much. I formatted my handset and started again from scratch so I'm a bit reluctant to try and restore now, but in the future if I need to I'll try and reflash the kernel. (I'm using Androplus Kernel)
Related
Tried to root my thinkpad tablet, i rooted it with this; http://vulnfactory.org/public/Thinkpad_Root_Windows.zip
Then i installed cwm, i used cwr_ventana_2.img
And when i tried to install the CM10 rom i was stuck in boot loops...
I then restored the rooted 0089/OTA 2.5 ROW stock image nandroid backup and it worked again.
And heres what bricked it, i tried to install the ThinkPadTablet_A310_03_0064_0126_WE, and now im stuck with bootloops and no recovery....
What to do?
So you have a ROW tablet and tried to apply a WE update?
I have e WE tablet, and used a ROW CWM backup restore... since i got MD5 error on the backup i took....
did you try to see if your bootloader is locked or not.
if it is not then it is no big deal, but if it is locked then i have no ideea what you can do.
The bootloader is locked, got only a 0x4 error or something, im going to call Lenovo today :silly:
i had this boot loop issue also, and i used the wipe zip to manually wipe all the partitions. the normal factory reset didnt worked for me...
how did you apply the zip? does it open the zip automaticly on boot or?
I"m having issue with flashing roms, kernels and restoring on my device and i'm not sure if its cause a process was done incorrect and/or a TWRP.
I have a 2017U. Bootloader is unlocked, TWRP 3.1.0, and currently on stock B19 (no root, via TWRP with Draken's Stock system).
Here are the issues I"m facing:
1. Unable to Restore backup. I've made a backup and selected Boot, System and data. Also selected "compression". Restore shows complete, but device freeze on boot screen (the one says hit vol for more options).
2. Issue flashing kernel. I tried flashing Beastmode (a couple of previous versions up to the most currect R45). I keeps booting back into Recovery. I then tried flashing the stock kernel from Freeza and it still boots into recovery.
3. Flashing Roms. This one is possibly a rom issue, but just wanted to throw it out there any ways in case it's not. Flashed Bad Boys rom. Works fine when installing with SU or Magik, but doesn't boot if it select "no root"...
Any help/advice is appreciated.
You either need to flash supersu, or no-dmverity to patch the kernel to bypass this security feature.
3.1 is also not ready according to twrp thread.
Sent from my ZTE A2017U using Tapatalk
Thanks guys.
Just having a difficult time with TWRP recently. I wasn't able to restore properly on 3.0.4.
Every time i tried to restore, it says i need to uncheck mount system partition read only. Do need to flash the no-dmverity after i restore?
After reading up and being waived off the Official TWRP I originally used the open source (which I cant find on my phone or desktop) TWRP for my recovery.
I've been playing around with different ROMS on my Oneplus5 and ran into a TWRP loop after restoring from one ROM to another. It was suggested, and I followed the advice, to flash the Official TWRP and no more TWRP loop.
A week or so later, trying to restore from the Resurrection ROM to xXx ROM and I'm back in a TWRP boot loop.
I've tried different wipes before restoring and still looped.
Tried flashing this version of TWRP to recovery https://forum.xda-developers.com/oneplus-5/development/twrp-oneplus-5-wip-t3626134 and it was no help.
Any suggestions?
Try flashing no verity op5.zip
I don't think official TWRP can restore backups that include system data on the OP5 without going into a bootloop. Blu Spark TWRP works much better. I've never gotten a boot loop restoring any backup I made with that version of TWRP.
jhs39 said:
I don't think official TWRP can restore backups that include system data on the OP5 without going into a bootloop. Blu Spark TWRP works much better. I've never gotten a boot loop restoring any backup I made with that version of TWRP.
Click to expand...
Click to collapse
Thanks, it was getting a bit frustrating and before your solutions posted, in the interim I used Method 2 from here:https://forum.xda-developers.com/oneplus-5/how-to/guide-fix-twrp-recovery-script-loop-t3649727 loading the stock bootloader wiped my device clean (all pics, my files, my TB folder gone) but I was able to load a ROM and boot (I hate Goggle, they can f up just about anything, but that god for their backup/restore, it got me up and running from scratch quickly ). I will give the blu spark a shot and @ se7ensde take a look at your suggestion.
It is a shame that TWRP restore is such a problem, and a random one at that. I have restored from ROM to ROM to compare them without an incident until....
I've had this happen before on other phones, usually fixed by just installing a different rom or restoring a backup. Not here.
I finally unlocked my bootloader on the XT1607 (the Motorola site just randomly worked one day), installed TWRP & the 7.1.1 Soak Test (from here). I forgot to backup 6.0.1, so I backed up the soak test which was booting and working flawlessly. I was using it for a while, but I did a factory reset inside TWRP and it randomly said "cannot mount storage" and when I rebooted, it was into TWRP. It wasn't working at all, so I got LineageOS 15.1 and flashed that. Same error, "cannot mount storage" and back to TWRP. I went into Wipe>Format Data and then reinstalled Lineage. The "cannot mount storage" error was gone, but still booting into TWRP. I tried AOSP Extended, CyanogenMod, Paranoid Android. roms with gapps, roms without, with & without supersu or magisk. Nothing worked. So then I thought that restoring my backup (of all partitions) would fix the issue. It didn't, still booting back into TWRP. I'd also like to mention that plugging the phone in still worked, I can view the files in file manager, sd card works, etc.
So, no clue what to do here. What's wrong? It all started with that simple factory reset from twrp.
edit: I found that if I boot into bootloader and press start it will go into android, but hardly a permanent solution.
Same thing happened to me but my issue resolved after restoring back to stock rom with stock recovery and after that u can again flash twrp it will work fine
sumit1327 said:
Same thing happened to me but my issue resolved after restoring back to stock rom with stock recovery and after that u can again flash twrp it will work fine
Click to expand...
Click to collapse
Heyyy, thanks man. Worked like a charm.
I am currently using a OnePlus 5 which used to run on a stock based rom, xxxNoLimits v3.1
Since the dev ended the support I wanted to revert back to pure OOS, so I downlaoded the newest 5.1.5 zip and followed the instructions using the newest blu_spark twrp recovery but right after pressing the "flash" button I kept getting error 7, so I download the zip from a mirror link and I have also tried the newest version of codeworkx twrp, still error 7. Then I tried flashing the original stock recovery in order to flash the zip but it instantly threw me back to the zip selection menu, flashing the zip via adb sideload kept quitting at exactly 47%. At this point I was pretty frustrated, I flashed twrp codeworkx again and wiped EVERYTHING, which includes the system, data, cache, dalvik partitions and then I also did a format on the data partition, the point was that now I would have a clean phone only running twrp and I thought I could easily flash the newest zip now without any problems, NOPE, still error 7!!! Now I am stuck here, the stock recovery doesnt let me flash anything and I've tried 4 different versions of twrp recoverys and every single one gives me the same error, I even dug up an older version of OOS, I think it which I had running for a few weeks without any probles so I knew that the zip was not corrupted but same error
Now I had given up and wanted to restore the backup I did just in case anything goes wrong, well, restoring the backup fails when it tries to restore the data partition, so I unchecked everything except system, system image and recovery but it didnt work, now I am sitting here with my phone telling me that there's no OS installed. any advice?
Use Unbrick Tool and Restore
Hey,
You can Flash your Mobile using the Unbrick tool at - https://androidfilehost.com/?w=files&flid=204903
Use the Latest file which I guess comes with OOS 5.1.3 - https://androidfilehost.com/?fid=962339331458999196
If you try to Go to Open Beta ROM First Flash Open Beta 12--> Open Beta 13 --> Open Beta 17
freaky2xd said:
I am currently using a OnePlus 5 which used to run on a stock based rom, xxxNoLimits v3.1
Since the dev ended the support I wanted to revert back to pure OOS, so I downlaoded the newest 5.1.5 zip and followed the instructions using the newest blu_spark twrp recovery but right after pressing the "flash" button I kept getting error 7, so I download the zip from a mirror link and I have also tried the newest version of codeworkx twrp, still error 7. Then I tried flashing the original stock recovery in order to flash the zip but it instantly threw me back to the zip selection menu, flashing the zip via adb sideload kept quitting at exactly 47%. At this point I was pretty frustrated, I flashed twrp codeworkx again and wiped EVERYTHING, which includes the system, data, cache, dalvik partitions and then I also did a format on the data partition, the point was that now I would have a clean phone only running twrp and I thought I could easily flash the newest zip now without any problems, NOPE, still error 7!!! Now I am stuck here, the stock recovery doesnt let me flash anything and I've tried 4 different versions of twrp recoverys and every single one gives me the same error, I even dug up an older version of OOS, I think it which I had running for a few weeks without any probles so I knew that the zip was not corrupted but same error
Now I had given up and wanted to restore the backup I did just in case anything goes wrong, well, restoring the backup fails when it tries to restore the data partition, so I unchecked everything except system, system image and recovery but it didnt work, now I am sitting here with my phone telling me that there's no OS installed. any advice?
Click to expand...
Click to collapse
Flashing newest oos doesn't always work l have had this sometime l have had to go back 3 oos versions then flash them in order to flash the latest release.
freaky2xd said:
I am currently using a OnePlus 5 which used to run on a stock based rom, xxxNoLimits v3.1
Since the dev ended the support I wanted to revert back to pure OOS, so I downlaoded the newest 5.1.5 zip and followed the instructions using the newest blu_spark twrp recovery but right after pressing the "flash" button I kept getting error 7, so I download the zip from a mirror link and I have also tried the newest version of codeworkx twrp, still error 7. Then I tried flashing the original stock recovery in order to flash the zip but it instantly threw me back to the zip selection menu, flashing the zip via adb sideload kept quitting at exactly 47%. At this point I was pretty frustrated, I flashed twrp codeworkx again and wiped EVERYTHING, which includes the system, data, cache, dalvik partitions and then I also did a format on the data partition, the point was that now I would have a clean phone only running twrp and I thought I could easily flash the newest zip now without any problems, NOPE, still error 7!!! Now I am stuck here, the stock recovery doesnt let me flash anything and I've tried 4 different versions of twrp recoverys and every single one gives me the same error, I even dug up an older version of OOS, I think it which I had running for a few weeks without any probles so I knew that the zip was not corrupted but same error
Now I had given up and wanted to restore the backup I did just in case anything goes wrong, well, restoring the backup fails when it tries to restore the data partition, so I unchecked everything except system, system image and recovery but it didnt work, now I am sitting here with my phone telling me that there's no OS installed. any advice?
Click to expand...
Click to collapse
Hi ! Do you have some news about it ? I have the same issue since Monday...
I've tried like anything i've found and even more, but nothing did the job ...
The only way to have my OP5 working is downgrade to an old version running Android 7.1.1