Hi Everyone, I'm new to the Nexus 4, and I unlocked the bootloader and installed the CWM Recovery using this guide. http://au.ibtimes.com/articles/53036...at-install.htm
Everything went correctly and after I installed CWM and wanted to reboot my device, it asked to remove the stock recovery, I said Yes (there was no mention of this in the article, but i remembered how annoying this was with a previous device, so i agreed to that), as I needed to install Superuser from a ZIP, i selected No when i was prompted to root the device (from CWM). after those two questions, the phone rebooted, and now it's in a bootloop (on the bubbles boot screen, (4.4.2). Is there any way to fix this?.
Try going into recovery and doing a factory reset or wipe cache.
It's a bug with Nexus devices and bootloader unlocking. After unlocking the bootloader, you need to do a full reboot before going back in and flashing a custom recovery. See the article below about the bug. You need to re-flash the stock recovery to get out of the bootloop.
http://www.androidpolice.com/2013/1...locking-your-nexus-or-gpe-devices-bootloader/
Related
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!
Before the problem, I had a 4.1.1 rooted unlocked N7 with original ROM. I decided to apply the OTA update (03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip) from TWRP recovery using the option to manually install zip updates.
The tablet rebooted, and I used Voodoo OTA RootKeeper to regain root access. Everything worked fine, I had no error messages at any moment during the procedure and the 4.1.2 update was applied successfully, as I could verify in the info section and by testing the landscape mode.
But, when I try to reboot in recovery using the option in ROM Manager, all I get is the little robot on his back image without any message. The only way to get out of this screen is to press the power button for a few seconds until it reboots into Android. Everything is fine except the recovery mode.
I tried to reflash the recovery image using Wug's Toolkit to no avail. I tried CWM, TWRP and stock recoveries but none worked. I always get the same screen with the robot on his back when I try to boot into recovery. Booting normally is always fine, only recovery seems to be affected. If I use Wug's toolkit to boot a temporary TWRP recovery image, it works but I want to be able to boot as before, with ROM Manager.
Any ideas? Is there a solution other the wipe it all and restart from scratch?
[edit] I can start into Fastboot but if I try to go to recovery from there, the same thing happens...
I fixed it by flashing the older 3.34 bootloader. So something is wrong with the new 3.41 bootloader.
There is nothing wrong with the process.
Its the users interpretation of how it works.
After updating, the file that flashes the stock recovery on boot is put back.
So he flashed in custom recovery.
Booted at which point the custom recovery is replaced with stock
Then wonders why he can't access custom recovery anymore.
Just reflash custom recovery
Sent from my HTC One X using xda app-developers app
bagofcrap24 said:
There is nothing wrong with the process.
Its the users interpretation of how it works.
After updating, the file that flashes the stock recovery on boot is put back.
So he flashed in custom recovery.
Booted at which point the custom recovery is replaced with stock
Then wonders why he can't access custom recovery anymore.
Just reflash custom recovery
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Not true. I flashed the update through cwm and everything went fine. When you reboot the system, cwm asks if you want to flash recovery and keep root. I denied to flash the stock recovery and I kept the root. After that you can't get into recovery at all (stock or cwm or whatever). but if I downgrade my bootloader to 3.34 everything is ok. I also installed new bootloader through cwm manually again and after that I can't boot into recovery.
Btw... How to flash bootloader.raw with fast boot???
Sent from my Nexus 7 using Tapatalk 2
sikagoon7 said:
I think you are a bit misinformed. When you flash the OTA the recovery-from-boot.p is installed by default. It resets the recovery to stock every time you reboot. CWM does nothing to remedy this. The only way to fix it is to remove or rename the file to disable its function. After and ONLY after this will you be able to flash recoveries by choice and boot into them.
And while it is your choice to use whatever recovery you desire I personnaly think using stock recovery and adb sideload is the safest when it comes to signed stock OTA.zips. After that you can root and flash your recovery of choice as if you have a brand new device.
When it comes to the bootloader. Stock system, boot, and recovery verify which bootloader you are using. JRO03D looks for 3.34 and JZO54K looks for 3.41. I don't know the implications of switching them but I don't think I will test that. I've already had a bad experience with dismantling a bootloader. The bootloader is an IMG file. Download the JRO03D factory image from Google's website and extract it. Inside will be a file named bootloader-grouper-3.34.img. THAT is the stock JRO03D bootloader and that is what you need to flash using: fastboot flash bootloader bootloader-grouper-3.34.img.
Click to expand...
Click to collapse
Yes I know that and did that from the beginning (renamed the file) but the point is that you can't boot into recovery (stock or whatever). It tries to boot into recovery I think but it reboots again and loads the OS. I'm using 3.34 booatloader with 4.12 and haven't got any probs yet.
Finally Got it Working
I tried one last thing yesterday. I got into ROM Manager and used the option to flash CWM Recovery. Then I rebooted in CWM (using the ROM Manager option). All was fine and when I chose the option to reboot, CWM asked me if I would like to make the custom recovery permanent because it would otherwise be rewritten at boot (this is what caused my problems, I believe). I choose to do so and it worked normally after that.
I then downloaded the TWRP recovery (http://www.teamw.in/project/twrp2/103) and installed it with Wug's Toolkit using the option to flash a permanent Recovery from a file. I didn't modify the "recovery-from-boot.p" file because I thought that CWM already did that. Tested booting into recovery again and all is finally OK with TWRP.
One of the benefits of the 4.1.2 update is that I can now boot into recovery from the Fastboot menu.
I'm in the same boat, ended up flashing the factory image for jz054k (which included the new bootloader) to try and fix.. now I'm without root and without a recovery..
I'm unlocked, but flashing alternative recoveries just doesn't work right now.. can't boot them up.
Did the original author ever get this resolved?
-m
diomark said:
I'm in the same boat, ended up flashing the factory image for jz054k (which included the new bootloader) to try and fix.. now I'm without root and without a recovery..
I'm unlocked, but flashing alternative recoveries just doesn't work right now.. can't boot them up.
Did the original author ever get this resolved?
-m
Click to expand...
Click to collapse
There are mixed reports on bootloader 3.41 and booting recovery. I have not been able to properly boot recovery from 3.41 under any circumstances. If you have this issue as well, flash the 3.34 bootloader from JRO03D. Doing this has allowed me to use recovery again.
I was running 4.1.2 with old bootloader 3.34 and had a SOD while my Nexus was charging last night.
In Faux123's kernel thread, he told me:
You should use the new boot loader and stick with CWM for now until TWRP get their stuff compatible with 4.1.2. Boot loader initialize the power regulators to some know state for the machine to boot until the kernel takes over.. and the new kernel is expecting it to be initialize certain ways... This was the biggest difference between 4.1.1 and 4.1.2... so I HIGHLY recommend using the matching bootloader...
Click to expand...
Click to collapse
Steps I had to take to get 4.1.2 (rooted, stock rom, custom kernel):
flash stock 4.1.1 boot.img and recovery.img
flash 4.1.1 bootloader 3.34
flash recovery TRWP recovery
flash SuperSU (regain root)
flash CWM lastest recovery 6.0.1.5 (beta) based on Faux123 advice above
flash 4.1.2 bootloader 3.41
No problems so far. This whole process has taken days...
I'm finally where I want to be.
Oops, wrong thread...
Hello all, I just had a quick questions for those of you who have unlocked / rooted your Nexus 10 and installed the factory image:
1. Did you all use the toolkit in the Android Dev Forum for Nexus 10 to achieve the root?
2. Once you flashed a custom recovery was installing the factory image as simple as downloading the zip from google (https://developers.google.com/android/nexus/images#mantaray) and then flashing it via recovery and rebooting AFTER you unlock the bootloader etc?
I was under the impression that once you Unlock / Root, you have no OS on your device, is this correct? Or can I root and Android 4.2.1 will still be there, albeit completely wiped of my user data from before.
Thanks for the help, don't wanna get started on this until I know what I'm doing! Don't want a $400 makeshift frisbee disk
You can achieve root in a number of ways including flashing the SuperSU zip found in the How-to Root thread(s) or flashing a ROM with root already built in through the custom recovery.
Unlocking the device does not usually (is not supposed to) remove the OS but it does wipe data back to factory default. There has been, however, an issue with 4.2 on the N10 that causes it not to boot until you go back into Recovery and either factory reset there again or flash the stock image from Google.
Fromako said:
You can achieve root in a number of ways including flashing the SuperSU zip found in the How-to Root thread(s) or flashing a ROM with root already built in through the custom recovery.
Unlocking the device does not usually (is not supposed to) remove the OS but it does wipe data back to factory default. There has been, however, an issue with 4.2 on the N10 that causes it not to boot until you go back into Recovery and either factory reset there again or flash the stock image from Google.
Click to expand...
Click to collapse
Thanks! I think I will go through with using the toolkit tonight and see if I can get it to boot into the factory image. Glad that it sticks around (hopefully) if not I can just flash 4.2 from google via TWRP...thats what I needed to know
So really all I need to root is this:
1. fastboot oem unlock
2. fastboot flash recovery [recovery.img]
3. Boot into recovery
4. Flash SuperSU.zip? --- Where can I download SuperSU.zip ?
5. Wipe Cache / Factory Reset via TWRP wipe data
6. Reboot
7. Profit?
I won't use the toolkit if I don't have to since I am familiar with some fastboot stuff
TheEmpyre said:
I won't use the toolkit if I don't have to since I am familiar with some fastboot stuff
Click to expand...
Click to collapse
Sounds like you know enough to do it without resorting to a toolkit, yeah. This zip file from http://forum.xda-developers.com/showthread.php?t=1997227 is one place to get fastboot drivers and the SuperSU.
http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip
I'd recommend (although it may not be necessary) making sure your devices fully boots after unlocking and wiping before going back to recovery to flash SU. Again, this is just because of the unlock boot loop issue that didn't happen on pre-4.2 nexus devices like the Galaxy Nexus.
Fromako said:
Sounds like you know enough to do it without resorting to a toolkit, yeah. This zip file from http://forum.xda-developers.com/showthread.php?t=1997227 is one place to get fastboot drivers and the SuperSU.
http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip
I'd recommend (although it may not be necessary) making sure your devices fully boots after unlocking and wiping before going back to recovery to flash SU. Again, this is just because of the unlock boot loop issue that didn't happen on pre-4.2 nexus devices like the Galaxy Nexus.
Click to expand...
Click to collapse
I just finished successfully rooting...got hung up after I unlocked the bootloader and flashing TWRP but all I had to do was Format the Data and wipe cache after to successfully boot into the OS. After that I was able to load SuperSU to my SDcard and then flashed it, reboot, did root-checker and I'm all good! Thought I was screwed there for a sec cuz I didn't pre-load SuperSU or the factory image in-case it hit the fan and I wasn't able to mount my SDcard storage via TWRP...Figured it all out though thanks for the help! Glad I was able to do it without the tool-kit!
Yesterday I tried to root my nexus 4 and I followed a tutorial. I unlocked the bootloader and was able to flash twrp 2.6.3.0 custom recovery. However, I forgot to factory reset my device before flashing the recovery. When I got to the twrp screen it asked me for my password. I entered the one for my device but I couldn't get in. I entered it in a couple more times, but still it wasn't unlocking. I pressed the back button and I randomly got into the recovery. From there I continued the rooting process but when I tried to wipe cache or dalviks cahce it always said that It failed (never got to the point of flashing SuperSU). I then tried to wipe the system but I stilled got the failed message.I had no choice but to exit out of twrp and turn off my device and when I did, I got stuck at the nexus logo. I was able to get my device back to stock and I want to root my device but I'm not sure what went wrong. Should I try using twrp 2.6.0.0 because a lot of guides I followed used that custom recovery. Also, if I use and old recovery will I be able to update it later? I also followed this guide : http://forum.xda-developers.com/showpost.php?p=41291371&postcount=28 so I wouldn't lose my data. I tried including as much info as possible so sorry if I wrote too much.
neogamma said:
Yesterday I tried to root my nexus 4 and I followed a tutorial. I unlocked the bootloader and was able to flash twrp 2.6.3.0 custom recovery. However, I forgot to factory reset my device before flashing the recovery. When I got to the twrp screen it asked me for my password. I entered the one for my device but I couldn't get in. I entered it in a couple more times, but still it wasn't unlocking. I pressed the back button and I randomly got into the recovery. From there I continued the rooting process but when I tried to wipe cache or dalviks cahce it always said that It failed (never got to the point of flashing SuperSU). I then tried to wipe the system but I stilled got the failed message.I had no choice but to exit out of twrp and turn off my device and when I did, I got stuck at the nexus logo. I was able to get my device back to stock and I want to root my device but I'm not sure what went wrong. Should I try using twrp 2.6.0.0 because a lot of guides I followed used that custom recovery. Also, if I use and old recovery will I be able to update it later? I also followed this guide : http://forum.xda-developers.com/showpost.php?p=41291371&postcount=28 so I wouldn't lose my data. I tried including as much info as possible so sorry if I wrote too much.
Click to expand...
Click to collapse
Hey man,
I followed this guide. I flashed CWM instead of TWRP.
http://forum.xda-developers.com/showthread.php?t=2018179
Here is the version of Recovery I flashed:
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.6-mako.img
Here is the version of SU I flashed:
http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
Then I just followed the instructions on that post and everything seemed to work well for me
So I just flashed DP5 and I have been out of the loop on DP stuff since I haven't used the others since the original. Anyways, I wanted root for a few reasons but I was unaware how hard it would be to install TWRP so I could flash SuperSU. I am sure there are easier ways than how I did it, but after wiping userdata 3 times tonight I'd like to avoid that again.
So I flashed DP5, I flashed TWRP, Stuck on TWRP splash screen
So then I flashed Marshmellow Vendor, still stuck on splash screen
So then I flashed the modified boot image, twrp and viola I got into TWRP, I installed SuperSU, re-loading my data as I type this.
My question, can I flash the stock boot.img to re-encrypt my device? Is there a way to do it? I don't think i'll need TWRP necessarily so I am ok if it doesn't work so long as I keep root.
Just go into Settings>Security and select "Encrypt phone", and follow the prompts. There's no need to flash another boot image. The one you have now just doesn't force encryption, it doesn't mean you can't encrypt if you want to encrypt.
Sent from my Nexus 6P using Tapatalk