Database Users

Unlockr didn't totally work. Did nandroid restore. Not sure where I am now.

I tried yesterday to one-click root my MT3G following unlockr.
Got the Amon-Ra recovery on there, but it hung on the green MT3G splash screen when I tried flashing cyanogen 4.1.11 .
Waited like over 20 minutes. So I took out battery, and tried to boot again. Same thing. So I rebooted into recovery and tried flashing ROM again.
No matter what ROM I tried, I got a "E:Can't open /sdcard/update.zip (bad)" message. (I redownloaded ROMs from different sources given the message thinking maybe they were bad or incomlplete, but nothing worked).
I finally did a nandroid restore.
Now I'm not sure where I am. Given that I restored my stock nandroid backup, my understanding is I'm no longer rooted. Though, I am still able to boot into the Amon-Ra recovery. which I thought would have not still been possible. I downloaded better terminal and tried typing "su" but it wouldn't let me continue, so that confirms not rooted, right?
Do I run the recovery flasher app again (which is still on the phone), and reflash a recovery image? Or should I delete the app and redownload the recovery flasher apk.
Just not sure how to safely retry.

You need to provide more details about your process. I actually unrooted mine previously done with Cyanogen Recovery and rerooted with same instructions on that site only this time with Amon Ra recovery image without problems. In my case I wanted the option of formatting partitions. Maybe you should try Cyanogen stable Rom first, like 3.68.1 version. I had an issue with 4.1.11.1 after I partitioned the card so I did 3.68.1>4.0.4>4.1.11.1.

[Q] TWRP nor CWM will successfully wipe/format data

First, I searched and read all relevant threads concerning this issue. The five threads that showed up in the search did not help me solve my issue.
So on to my problem. I can no longer flash any rom onto my device. I attempted to flash the first official CM10 nightly (which I recently found out was not flashing properly for others) and had no success. I simply got a black screen and nothing more. I eventually got back into TWRP (v2.2.1.4) to try and Nandroid restore, but I noticed that /data was not formatting and the restore failed. Every time I would slide the bar across to confirm the restore TWRP would reboot itself. I then flashed CWM (v6.0.1.0) and the same problems were there. After that I flashed an earlier version of TWRP and successfully restored the backup. I'm not 100% sure how it was successful. So I decided to try flashing another ROM and no go. Same problems. Anyone have any ideas? When I was using CWM I got the error message below.
Code:
E: unable to locate volume information
E: unable to open ums lunfile '/sys/devices/platform/usb_mass_storage/lun0/file'
E: unable to format data
I'm running Bugless Beast with Motley #219

I'm having similar, if not identical problems. After flashing TWRP 2.2.1.4, I tried flashing a rom and gapps; the tablet would boot endlessly into recovery. Nothing I did would do anything, so I flashed the stock image to start over. This time, I used CWM 6.0.1.0 touch to make sure that it wasn't the recovery that was causing the problem. However, now after flashing the rom and gapps, instead of booting into recovery, I got stuck at a black screen and had to hold the power button in order to get back to the bootloader.
Now, like you, it seems I can't flash any roms anymore. It's frustrating to say the least.
Sent from my Galaxy Nexus using xda app-developers app

aznxk3vi17 said:
I'm having similar, if not identical problems. After flashing TWRP 2.2.1.4, I tried flashing a rom and gapps; the tablet would boot endlessly into recovery. Nothing I did would do anything, so I flashed the stock image to start over. This time, I used CWM 6.0.1.0 touch to make sure that it wasn't the recovery that was causing the problem. However, now after flashing the rom and gapps, instead of booting into recovery, I got stuck at a black screen and had to hold the power button in order to get back to the bootloader.
Now, like you, it seems I can't flash any roms anymore. It's frustrating to say the least.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
What rom did you attempt to flash?

elementur said:
What rom did you attempt to flash?
Click to expand...
Click to collapse
So do I.I attempted to flash the first official CM10 8.18 nightly and had no success. I just got a black screen.Even more I boot into bootloader and choose to boot into recover but just stay at google logo.I try to flash recover once more,but just can't boot into recover!!

I have the same problem, i flashed the cm10 nightly which I learned would not boot. No I have no backup to boot to, and cannot even push a new rom to the storage to try to install.

Shano56 said:
I have the same problem, i flashed the cm10 nightly which I learned would not boot. No I have no backup to boot to, and cannot even push a new rom to the storage to try to install.
Click to expand...
Click to collapse
Can't boot into recover,does anyone know what is wrong?When it is in android I can use APM boot into recover or via ADB,but unusually when it is in the bootloader I choose to boot into recover,it just stay at google logo!!What it is going wrong?

phiracle said:
Can't boot into recover,does anyone know what is wrong?When it is in android I can use APM boot into recover or via ADB,but unusually when it is in the bootloader I choose to boot into recover,it just stay at google logo!!What it is going wrong?
Click to expand...
Click to collapse
There is a bug with the Nexus 7 where you cannot access the recovery through the bootloader. To fix this, boot up into the bootloader on your nexus 7 and, without doing anything, plug it into the computer you used for rooting it and then select the option Restart bootloader and press the power button. Once it gets you back into the bootloader again select Recovery mode and press the power button. It will now get you into the recovery and once you're in recovery you can unplug your tablet from the computer. Note that this fix is not permanent and you will have to do this every time you wish to access your recovery via the bootloader (and this problem is not relevant to the OP's problem).

android1234567 said:
There is a bug with the Nexus 7 where you cannot access the recovery through the bootloader. To fix this, boot up into the bootloader on your nexus 7 and, without doing anything, plug it into the computer you used for rooting it and then select the option Restart bootloader and press the power button. Once it gets you back into the bootloader again select Recovery mode and press the power button. It will now get you into the recovery and once you're in recovery you can unplug your tablet from the computer. Note that this fix is not permanent and you will have to do this every time you wish to access your recovery via the bootloader (and this problem is not relevant to the OP's problem).
Click to expand...
Click to collapse
Thank You Very Much!!!

I am having much the same problem as the OP. I finally rooted my Nexus 7 using WugFresh's Nexus Root Toolkit. It seemed all went well. I chose to use TWRP in a first attempt to install a ROM (I was on rooted stock), and following the instructions for installing my chosen ROM I went into it to wipe cache, Dalvic Cache and data. Both cache and dalvic cache wiped without issue, but when I attempted to wipe /data TWRP simply reported that it failed. With that failing, I did not attempt to install a rom. I was still able to boot out of recovery, but even with repeated attempts wiping data always failed. Is any one aware of any solution or have any suggestions. Thank you!

[Q] Boot hangs at Android sign.

Simply put, this is what happens when a rooting newbie discovers custom bootloaders and ROMs.
Current State:
A full stock ROM installed (no root) with the Skrillax V8 bootloader plopped on top of it. (which of course means the recovery-from-boot.p file still exists and that I don't have CWM.) The tablet will show the Acer logo then the Android logo and will give the appearance of booting. Then the icon flashes. It does this intermittently and forever.
What I want:
CM 10+ running with Skrillax and TWRP stably. I'd go with Flexreaper for next choice. Maybe I'll try to compile a KitKat version for it someday. Who knows.
How I managed to get my tablet in this crappy state:
Rooted tab a long while ago with a probably far outdated method.
Looked all over the internet later on how to unlock the bootloader and settled on the manual method in this excellent thread.
I flashed V8 and TWRP without a hitch using nvflash.
I wiped and installed Flexreaper.
I liked it but wanted a higher prize. I make a nandroid backup of it onto the external_sd and wiped and installed CM 10.1 from this thread.
This is where everything started going sour. It told me the install was invalid halfway. Disappointed, I wiped again and tried to restore my nandroid backup. It seemed to restore properly, but then Skrillax hung forever loading the kernel.
I wiped again and installed Flexreaper fresh. This time it booted. I downloaded the newest unofficial version of CM they mention on their wiki.
Booted to recovery and installed CM 10. It ran fine and I was impressed with the new OS. Then I noticed the apparent lack of Gapps.
I flashed the Gapps Jellybean package and rebooted. Skrillax hung.
Wiped everything I could fine in the TWRP menu and installed Flexreaper. Got past the primary kernel loading but the android icon would work for a bit then flash, starting all over again.
At this point I flashed several other recoveries, hoping it was my recovery. No such luck. I tried all of them included in V8.
Then finally, I downloaded full stock ICS and flashed it. I rebooted and noticed the same Android flashing thing.
Finally, I flashed V8 again, being the newbie I was, and then suddenly remembered while trying to boot to recovery that the Full install probably rewrote the recovery-from-boot.p.
And here I am.
Tl;dr version:
Went click-happy with ROMs, wiping, and recovery flashing until I was left with a stock OS that wouldn't boot with a Skrillax bootloader but no recovery.
The good news is, I still have cpuid+sbk, it still boots to APX (no idea how I didn't screw that up too.), and I have a nandroid backup on my external_sd which is probably untouched, since I was careful to not wipe it in TWRP.
Please help me fix this. I don't want an excuse to waste money on a flashy new Nexus or Asus Transformer tablet, I already have too many for my wallet's comfort.

I quess you renamed stock rom to update.zip and than flashed it? If you havent do it, put it on sd card and pres power+vol down (if nuttin happens than vol up). That shld trigger flashing proces
poslato sa elmag radija

uglyjohny said:
I quess you renamed stock rom to update.zip and than flashed it? If you havent do it, put it on sd card and pres power+vol down (if nuttin happens than vol up). That shld trigger flashing proces
poslato sa elmag radija
Click to expand...
Click to collapse
I don't have access to a micro sd card reader if the file must be placed on the micro SD card. I already have flashed the stock rom supposedly via TWRP, so I shouldn't have to flash it again, I wouldn't think. If I do, I guess I'll have to get a reader.

Yes. Micro sd. Rename it. You have guodes gere on xda. Im hoping it will help you.
poslato sa elmag radija

It didn't work. Still in same state as before.

I also have access to fastboot if that would help.

m27frogy said:
Simply put, this is what happens when a rooting newbie discovers custom bootloaders and ROMs.
Current State:
A full stock ROM installed (no root) with the Skrillax V8 bootloader plopped on top of it. (which of course means the recovery-from-boot.p file still exists and that I don't have CWM.) The tablet will show the Acer logo then the Android logo and will give the appearance of booting. Then the icon flashes. It does this intermittently and forever.
What I want:
CM 10+ running with Skrillax and TWRP stably. I'd go with Flexreaper for next choice. Maybe I'll try to compile a KitKat version for it someday. Who knows.
How I managed to get my tablet in this crappy state:
Rooted tab a long while ago with a probably far outdated method.
Looked all over the internet later on how to unlock the bootloader and settled on the manual method in this excellent thread.
I flashed V8 and TWRP without a hitch using nvflash.
I wiped and installed Flexreaper.
I liked it but wanted a higher prize. I make a nandroid backup of it onto the external_sd and wiped and installed CM 10.1 from this thread.
This is where everything started going sour. It told me the install was invalid halfway. Disappointed, I wiped again and tried to restore my nandroid backup. It seemed to restore properly, but then Skrillax hung forever loading the kernel.
I wiped again and installed Flexreaper fresh. This time it booted. I downloaded the newest unofficial version of CM they mention on their wiki.
Booted to recovery and installed CM 10. It ran fine and I was impressed with the new OS. Then I noticed the apparent lack of Gapps.
I flashed the Gapps Jellybean package and rebooted. Skrillax hung.
Wiped everything I could fine in the TWRP menu and installed Flexreaper. Got past the primary kernel loading but the android icon would work for a bit then flash, starting all over again.
At this point I flashed several other recoveries, hoping it was my recovery. No such luck. I tried all of them included in V8.
Then finally, I downloaded full stock ICS and flashed it. I rebooted and noticed the same Android flashing thing.
Finally, I flashed V8 again, being the newbie I was, and then suddenly remembered while trying to boot to recovery that the Full install probably rewrote the recovery-from-boot.p.
And here I am.
Tl;dr version:
Went click-happy with ROMs, wiping, and recovery flashing until I was left with a stock OS that wouldn't boot with a Skrillax bootloader but no recovery.
The good news is, I still have cpuid+sbk, it still boots to APX (no idea how I didn't screw that up too.), and I have a nandroid backup on my external_sd which is probably untouched, since I was careful to not wipe it in TWRP.
Please help me fix this. I don't want an excuse to waste money on a flashy new Nexus or Asus Transformer tablet, I already have too many for my wallet's comfort.
Click to expand...
Click to collapse
Babsector should still work - you would need t do a search for it

It seems to have worked properly, sort of. Flashing FLEXReaper results in an "Encryption failed." prompt at boot, which the button, of course, does not work. Wiping everything works except that the prompt notes "E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p4" Trying to reflash V8 with TWRP with the V8.bat file fails at format. More help?

My tablet is still displaying "Encryption failed", the button still doesn't work, and I still love my a500. Help?
Anyone?

I guess I'm screwed, then.

In the end, I think my data partition failed. Formatting or wiping data fails and when installing FlexReaper, it reports /data size as -1. Unless anyone knows how to fix flash memory, I think I'm stuck.

[Q] A501 Semi Bricked plz Help

Hello People! so here is my case.. i followed this specific Guide to the letter http://forum.xda-developers.com/showthread.php?t=2792022 from a stock Hc Rom/recovery to kit kat used blackthund3rs Flash tool to flash Skrilax_CZ's bootloader and everything went smooth i managed to flash Cwm 6.0.4.5 on secboot without problems too but after i installed the Omnirom i forgot to do a factory reset i just cleared cache and dalvik cache after that the tablet wont boot to the rom it just shows the android logo and then resets by it self problem is that i cant even do a wipe/factory reset through cwm in secboot it just freezes and restarts again tried to install the omnirom again from the zip is gone from sdcard!!! oO along with everything else i guess i can see only 3 folders 0 the clockworkmod one and obb thing is i got the cpuid and sbk number also stock recovery is there. so what happens next? any help will be really appreciated!
ps. Sorry for my long and painfull to the eye post!

Devilhanzo said:
Hello People! so here is my case.. i followed this specific Guide to the letter http://forum.xda-developers.com/showthread.php?t=2792022 from a stock Hc Rom/recovery to kit kat used blackthund3rs Flash tool to flash Skrilax_CZ's bootloader and everything went smooth i managed to flash Cwm 6.0.4.5 on secboot without problems too but after i installed the Omnirom i forgot to do a factory reset i just cleared cache and dalvik cache after that the tablet wont boot to the rom it just shows the android logo and then resets by it self problem is that i cant even do a wipe/factory reset through cwm in secboot it just freezes and restarts again tried to install the omnirom again from the zip is gone from sdcard!!! oO along with everything else i guess i can see only 3 folders 0 the clockworkmod one and obb thing is i got the cpuid and sbk number also stock recovery is there. so what happens next? any help will be really appreciated!
ps. Sorry for my long and painfull to the eye post!
Click to expand...
Click to collapse
We have similar problems man!
http://forum.xda-developers.com/iconia-a500/help/help-a500-brickedi-t3080673

Nexus 6p with Android 7.0 in bootloop cannot access recovery

Hi Guys,
I'm Kinda new about making a new thread, so if anything's wrong let me know.
Just last evening my nexus 6p (on Android 7.0 official) got into a boot loop from a normal state. It just boots & right after when the white google logo transforms into 4 round object, it just reboots (it takes about 3-5 secs). I can access the boot loader but was unable to access to recovery from there as that takes it to bootloop again. I've tried flashing it, but since i had already updated to Nougat official version & the official image for 6p is yet to come, i tried with some earlier version of Marshmallow. but that failed as well. can it be that i need to select the right version of factory image as i really do not remember my old marshmallow versions anymore.
It seems i'm out of options right now. :crying:
Any advice guys??
TIA

Found this on Nexus 6p help forum. Haven't tried it though so I'm unable to confirm if it works or not.
https://productforums.google.com/forum/#!topic/nexus/hdrNONCCoNE

@sirluigi, this EXACT thing just happened to me ..
stock nougat, only bootloader unlocked ((( and since I've got no access to recovery and no Nougat image, I don't know what to do next
minicoop7, unfortunately, for that guide I need to go into recovery mode

ciocu said:
@sirluigi, this EXACT thing just happened to me ..
stock nougat, only bootloader unlocked ((( and since I've got no access to recovery and no Nougat image, I don't know what to do next
minicoop7, unfortunately, for that guide I need to go into recovery mode
Click to expand...
Click to collapse
Have you tried using fastboot to temp boot to recovery?

fastboot boot twrp-3.0.2-1-angler.img
downloading 'boot.img'...
OKAY [ 0.409s]
booting...
OKAY [ 0.680s]
finished. total time: 1.097s
Click to expand...
Click to collapse
same behavior, nothing but a bootloop
I'm dowloading an official MM image, just to get the stock recovery and see if I can temp boot in it
edit: not possible, I even tried to flash twrp, I tried flashing stock recovery from MTC20F.. tried to temp boot in both, all with no luck and with phone constantly alternating between the "Your device cannot be checked for corruption" screen and the white Google screen with the open lock.

sirluigi said:
Hi Guys,
I'm Kinda new about making a new thread, so if anything's wrong let me know.
Just last evening my nexus 6p (on Android 7.0 official) got into a boot loop from a normal state. It just boots & right after when the white google logo transforms into 4 round object, it just reboots (it takes about 3-5 secs). I can access the boot loader but was unable to access to recovery from there as that takes it to bootloop again. I've tried flashing it, but since i had already updated to Nougat official version & the official image for 6p is yet to come, i tried with some earlier version of Marshmallow. but that failed as well. can it be that i need to select the right version of factory image as i really do not remember my old marshmallow versions anymore.
It seems i'm out of options right now. :crying:
Any advice guys??
TIA
Click to expand...
Click to collapse
Guys its very simple, flash the stock mtc20f image first. After that boot it, it wont work but don't worry. Onece it bootloops go into bootloader and fastboot flash twrp 3.0.2-0. once thats done boot into twrp recovery. Onece in twrp make a backup of the image you just flashed that don't work. Once thats done mount system in recovery. Once mounted plug phone into computer and open the twrp folder you will see on your internal wich will have the backup that you just made. Transfer an old working backup into that folder that way twrp will recognize that backup. Once the backup is in the folder you shoukd see 2 backups in there, your new one that doesn't boot and your old one that does work wich you just put into the twrp folder. Once done go to restore and restore the backup of the working rom you just put in there, make sure to check off all on restore. Once done reboot system and it should boot. This will only work if you have a backup of an old working rom.
---------- Post added at 01:13 AM ---------- Previous post was at 01:00 AM ----------
sirluigi said:
Hi Guys,
I'm Kinda new about making a new thread, so if anything's wrong let me know.
Just last evening my nexus 6p (on Android 7.0 official) got into a boot loop from a normal state. It just boots & right after when the white google logo transforms into 4 round object, it just reboots (it takes about 3-5 secs). I can access the boot loader but was unable to access to recovery from there as that takes it to bootloop again. I've tried flashing it, but since i had already updated to Nougat official version & the official image for 6p is yet to come, i tried with some earlier version of Marshmallow. but that failed as well. can it be that i need to select the right version of factory image as i really do not remember my old marshmallow versions anymore.
It seems i'm out of options right now. :crying:
Any advice guys??
TIA
Click to expand...
Click to collapse
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help

disbeyad999989 said:
Guys its very simple, flash the stock mtc20f image first. After that boot it, it wont work but don't worry. Onece it bootloops go into bootloader and fastboot flash twrp 3.0.2-0. once thats done boot into twrp recovery. Onece in twrp make a backup of the image you just flashed that don't work. Once thats done mount system in recovery. Once mounted plug phone into computer and open the twrp folder you will see on your internal wich will have the backup that you just made. Transfer an old working backup into that folder that way twrp will recognize that backup. Once the backup is in the folder you shoukd see 2 backups in there, your new one that doesn't boot and your old one that does work wich you just put into the twrp folder. Once done go to restore and restore the backup of the working rom you just put in there, make sure to check off all on restore. Once done reboot system and it should boot. This will only work if you have a backup of an old working rom.
---------- Post added at 01:13 AM ---------- Previous post was at 01:00 AM ----------
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
Click to expand...
Click to collapse
Unfortunately, this didn't work for me.

I believe you should be fine with just trying to flash an earlier recovery version using fastboot... if you're trying to save your data and then factory flash MM and then restore your data to the phone, you should be able to use fastboot pull and then copy them back once you've got a working device by simple copy from windows.

disbeyad999989 said:
Guys its very simple, flash the stock mtc20f image first. After that boot it, it wont work but don't worry. Onece it bootloops go into bootloader and fastboot flash twrp 3.0.2-0. once thats done boot into twrp recovery. Onece in twrp make a backup of the image you just flashed that don't work. Once thats done mount system in recovery. Once mounted plug phone into computer and open the twrp folder you will see on your internal wich will have the backup that you just made. Transfer an old working backup into that folder that way twrp will recognize that backup. Once the backup is in the folder you shoukd see 2 backups in there, your new one that doesn't boot and your old one that does work wich you just put into the twrp folder. Once done go to restore and restore the backup of the working rom you just put in there, make sure to check off all on restore. Once done reboot system and it should boot. This will only work if you have a backup of an old working rom.
---------- Post added at 01:13 AM ---------- Previous post was at 01:00 AM ----------
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
Click to expand...
Click to collapse
Can you elaborate the steps pls? also have you had an earlier back up of your phone which i don't have?

Has anyone been able to get this to work without being able to get into TWRP? I can't get into recovery whether it is a temp boot to it, or fastboot flash either version..

I have compiled a list of the 20+ methods from various users in THIS thread. It's the second post.

Stuck in a bootloop still @tr4nqui1i7y but will try your methods as well... Fingers crossed..

So I do not if this may help anyone who as run into this issue but still may want to retrieve their data before formating their data or factory resetting. While running TWRP 3.0.3 and flashing the latest 7.1.1 files for angler. I would sometimes be able to boot into the recovery like 3/10 tries ( from the bootloader menu). My data was encrypted and it woul freeze constantly when trying to decrypt soo i decided once I finally got it to boot again in the recovery menu(TWRP after hours mind you) I let the phone stay idle for a few mins should the cpu would cool down that my battery percentage would drop around 41% and the tried to decrypt data which went tru successfully. I retrieve what I Could and it froze during a process of a nandroid backup and started bootlooping again. I believe the battery percentage may be linked to the early shutdown issues that many user were reported having and the bootloop of death we are experiencing. Hopefully this info may help someone else.