Related
Hi Guys!
I am trying to root my nexus, unlocked it, installed the right usb drivers, I can see the phone and everything looks right.
Downloaded Superboot for ERE27 with himem enabled and ran this. no problem.
I put the img file on the SD card and when I boot the phone in Fastboot / Recovery it does not find and img files on the SD card.
I tried 2 different cards and also different img files.
When I do this I get first the message no images found than I see the droid with a triangle and a ! in it. - Have to pull the battery.
Ideas anyone?
Thanks
What are you trying to do?
1) you had to unlock the bootloader which enables you to install a new recovery image (which is needed to allow you to install new roms)
2) you had to apply the recovery image Amon RA via a command prompt and a batch file if you use Windows. The phone's USB connection needs to be in development mode and once the batch file executes and successfully finishes you need to reboot the phone.
3) you restart the phone into bootloader mode, use the volume rocker to select the recovery console. If you end up with an andriod and exclamation symbol the Amon RA recovery file was not installed.
4) the new recovery console allows you to clean the SD card. Install roms from the SD card and some other commands. The Roms for the Andriod are in ZIP format and do not need to be unziped. In other words all you need to copy to the SD card is the full ZIP file (approx 75MB) and install that directly from the recovery console.
If your android stays in the booting sequence which is shown as the X with flying little pixels, it's most likely because you did not wipe the device clean first. That item is in the recovery console as well.
Hope this helps. I am just as new to this as you are.
You didn't unzip them did you?
You're trying to root with superboot. Great, but the recovery is not capable of flashing .img files, only .zip updates and roms and such. .img files have to be flashed using fastboot, not recovery, and are flashed from the connected computer.
If you read the superboot instructions from wherever you got the file, you'll see that you have to put the .img in the same directory ON YOUR COMPUTER as fastboot, connect via USB, boot the phone into fastboot, then enter the appropriate command line on the computer to flash the file.
If you've done that, then you are officially DONE with the rooting process.
Also, make damn sure that the superboot version matches the software version on your phone. They're both ERE27, right?
I'm not sure what anosis's post is talking about, but that looks more like the process for installing a custom rom (ie cyanogenmod), than rooting.
To root your phone, you DO NOT need Amon-RA's recovery. You only need that if you want to install custom roms, etc. It wont hurt to have it, as it includes many more functions than the stock recovery, but just to root, you don't need it.
Summary:
If you flashed the superboot.img from your computer via fastboot, your phone is rooted. Done.
You don't need to do anything in the recovery at all for rooting. Only for installing update.zips and custom rom.zips.
Hey, So I have been scouring the forums trying to find some answers about this and you seem to be the closet to my situation. Here is what I did:
So I was running a CM9 Aplha, reverted back to stock 2.3.6 [1ada25375426.signed-soju-ota-189904.1ada2537]) so that I could then apply ICS update [VQ8PQk_V]) which I sucessfully did. This was about a month ago and it was all going well.
Then yesterday I wanted to upgrade to 4.0.4 [hR7QFEtn] so I did and superuser wasn't working properly but then I reinstalled it and got it to work. However I got to the point where everything was working fine EXCEPT for the Google Play store kept on force closing. I spent hours trying last night and could not find a solution.
I tried restoring the previous ICS update that I had and it worked, and then I tried updating again. Also side: My clockwork was on the fritz lately so I was using Zedowmaxs force into clockwork recovery image [fastboot boot recovery3101.img] to force it in sometimes.
Anyway bottom line here is where my REAL ISSUE begins. I decided just to wipe everything and start anew. I factory reset/ wiped properly [cache partition and davliche cache] and then locked my bootloader again. Then tried rebooting. Got stuck on Google screen. Then I unlocked my bootloader again. Tried again, same issue.
So, here is where I am at. Cannot get into recovery from fastboot, takes me back to fastboot. AND, everything is wiped because I locked/unlocked my bootloader. All I can do is adb commands.
I don't know what to do from here and there is a lot of things going on. If you could help that would be great!? What I am going to try next is to flash some recovery on, but I don't know which one/ try to mount a file to my sd card from adb commands.
Daboxk said:
Hey, So I have been scouring the forums trying to find some answers about this and you seem to be the closet to my situation. Here is what I did:
So I was running a CM9 Aplha, reverted back to stock 2.3.6 [1ada25375426.signed-soju-ota-189904.1ada2537]) so that I could then apply ICS update [VQ8PQk_V]) which I sucessfully did. This was about a month ago and it was all going well.
Then yesterday I wanted to upgrade to 4.0.4 [hR7QFEtn] so I did and superuser wasn't working properly but then I reinstalled it and got it to work. However I got to the point where everything was working fine EXCEPT for the Google Play store kept on force closing. I spent hours trying last night and could not find a solution.
I tried restoring the previous ICS update that I had and it worked, and then I tried updating again. Also side: My clockwork was on the fritz lately so I was using Zedowmaxs force into clockwork recovery image [fastboot boot recovery3101.img] to force it in sometimes.
Anyway bottom line here is where my REAL ISSUE begins. I decided just to wipe everything and start anew. I factory reset/ wiped properly [cache partition and davliche cache] and then locked my bootloader again. Then tried rebooting. Got stuck on Google screen. Then I unlocked my bootloader again. Tried again, same issue.
So, here is where I am at. Cannot get into recovery from fastboot, takes me back to fastboot. AND, everything is wiped because I locked/unlocked my bootloader. All I can do is adb commands.
I don't know what to do from here and there is a lot of things going on. If you could help that would be great!? What I am going to try next is to flash some recovery on, but I don't know which one/ try to mount a file to my sd card from adb commands.
Click to expand...
Click to collapse
It looks like the time when you were locking-unlocking the bootloader, you messed up the recovery. Since your phone can get into bootloader menu, I think you can get out of this issue.
Here is what I would do.
1. Unlock the bootloader.
2. flash clockworkmod recovery using fastboot USB.
3. Download recovery-RA-passion-v2.2.1.img, put it in C:\fastboot\
4. Shut down your phone. Then start your Nexus One in Fastboot mode by holding down the Trackball and press the Power button.
5. Connect your phone to your computer. Open a Command Prompt (Start -> All Programs -> Accessories -> Command Prompt), and run the following commands:
cd C:\fastboot
fastboot devices
fastboot flash recovery recovery-RA-passion-v2.2.1.img
now see if you can get into recovery. If you can, just flash a custom rom using install zip from sd card option in the recovery
I didn't read all the replies but fastboot reads from your PC's disk not the sdcard, unless you are running it through shell or something?
Hey guys... Just rooted my Nexus 7 and for that matter any android device for the first time. I followed ToolKit 2.0 and did the one step for unlocking boot, rooting, flashing CWM and all option and successfully rooted. But however i am having trouble going into CWM mode.. Can someone please help me. I tried going into the power button and volume down button mode and with the volume keys went to 'Recovery Mode' but then the device just goes blank and then Google comes up written and nothing else happens. I then installed this app called ROM Manager via which i am able to boot into CWM. So how do i do it without the app. Please help me out guys.. Thanks a lot
In Google Nexus 7 ToolKit 2.0, try option 10.....
jshashwat93 said:
Hey guys... Just rooted my Nexus 7 and for that matter any android device for the first time. I followed ToolKit 2.0 and did the one step for unlocking boot, rooting, flashing CWM and all option and successfully rooted. But however i am having trouble going into CWM mode.. Can someone please help me. I tried going into the power button and volume down button mode and with the volume keys went to 'Recovery Mode' but then the device just goes blank and then Google comes up written and nothing else happens. I then installed this app called ROM Manager via which i am able to boot into CWM. So how do i do it without the app. Please help me out guys.. Thanks a lot
Click to expand...
Click to collapse
You need to plug the device into a powered USB port on the computer and manually entering recovery will work. It's a glitch in the nexus bootloader for the time being.
Also, the Trinity kernel toolbox app and maybe goo manager work for going to recovery, and the roms advanced power menus with the reboot to recovery option will work. The app quick boot may work too. But for using the volume rockers you need to be connected to USB
You could also use adb "adb reboot recovery"
If you don't have a pc near you, download the Android Terminal Emulator and type
su (hit enter and grand the superuser permission)
reboot recovery (enter)
Me too sometimes my device wouldn't want to go into recovery from the bootloader. I would have to pass from an app such as Rom Manager to reboot in recovery or it would get stock on Google logo.
What I did to solve is to :
./fastboot erase boot
./fastboot format system
./fastboot format cache
./fastboot format userdata
then from there I could boot into recovery and flash any rom I wanted to.
I'm pretty pissed because clockwork has been nothing but trouble on the Vision the Ville and now the Grouper and I keep forking pocket change to koush for his little touch recovery and it is still buggy. I can't believe this problem of not getting f to recovery from fastboot without needing anything else.
so I'm doing a fastboot erase recovery to wipe off that clockwork and then fastboot flash recovery teamWINifitaintbrokedontfixit.img
Sent from the Groupah
SO long story short I followed the rooting guide below:
http://forum.xda-developers.com/showthread.php?t=2266654
What I did:
I Unlocked Bootloader & Installed Custom Recovery, but after
I clicked Reboot, TWRP prompted me to "Fix Root Permission"
and install Root, which I made the grave mistake of swiping to
accept..
Now everytime the phone boots I see a "Google" Logo with a padlock
underneath, for a good few minutes, then a never-ending bootloop!!!
I can get into Recovery, but I can't see the Phone connected to any of my
computers, So I am unable to add in a file to flash and possibly fix my Nexus...
(I also can't mount, nor can I wipe anything except cache)
Please please please, is there anything I can do to save this phone???
:crying::crying::crying:
When you're in recovery mode you need to use adb to transfer files to your Nexus. Look for a howto that tells you how to use it.
Go into recovery and factory reset. If it still bootloops go back to recovery then on your PC go to device manager. Plug your phone up and see if it starts trying to update the drivers if it does stop it and manually direct it to the driver folder and let it install. Download super SU and use adb to push it to the phone
adb push su.zip /sdcard/
Flash it in recovery then reboot
Sent via BLACKED OUT LTE N4
There is a sweet yummy feature in recovery called "adb sideload". Boot into TWRP recovery -> Advanced -> ADB Sideload.
Typing "adb sideload path-to-your-flashable-zip" in the command line will send the zip to your phone and flash.
Nothing seemed to work however I got it working using one of the tool kits that was able to pull me out of the boot loop in the bootloader thanks guys
Sent from my Nexus 4 using Tapatalk 4
Adizzzle said:
Nothing seemed to work however I got it working using one of the tool kits that was able to pull me out of the boot loop in the bootloader thanks guys
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Please, how did you do it, I am in the same situation.
saidddo said:
Please, how did you do it, I am in the same situation.
Click to expand...
Click to collapse
Hold your power button for 15-ish seconds (even hold it for a while when the screen is black)
After that, hold the volume up+down+power button this will boot you into the bootloader.
After this you can just simply push a rom through adb on your phone, or try the factory reset in the recovery mentioned above.
so finaly how you decide your problem? cause i have the same problem
Hello,
my Nexus 4 dropped on the floor and now the touchscreen in the bottom right corner is not working anymore. This is a very unfortunate position since I am not able to press the "OK" button to unlock the lockscreen. I now want to at least save my data. USB Debugging is not enabled, so adb commands are not working :/
I googled a bit and found this thread witch the pretty much same situation:
http://forum.xda-developers.com/nexus-4/help/nexus-4-to-copy-data-broken-touch-input-t2415195
The steps to take are described as the following:
Read this guide http://forum.xda-developers.com/show....php?t=2266654 . only follow the parts to unlock the boot loader and flash clockworkmod custom recovery. Make sure that you flash the recovery right after unlocking (without rebooting in between) otherwise data will get wiped. )
After that boot into your newly flashed recovery and use "adb pull /data/media/" . this should copy everything on the internal sdcard of the phone.
Click to expand...
Click to collapse
So i did unlock the bootloader and flashed a clockwork custom recovery (6.0.4.7). I also managed to not reboot the phone between these two steps.
I was not sure what to do now as i did not know what was meant by boot into your newly flashed recovery . So i found another thread and followed these instructions
http://forum.xda-developers.com/showpost.php?p=41291371&postcount=28
After wiping the cache in step 4 i was in a boot loop (at least it took time like an eternity) and shut down the phone manually (by pressing the Power On button a few seconds). The new bootet phone is now in a state where I have to set the language for the new clockwork custom recovery. I tried to do some adb commands (because USB Debugging should not be the problem anymore) but it did not work. I am also scared that because of my manually shutting down caused a full wipe as i read the following sentence in the latest thread:
This no longer seems to be working if your phone is on official 4.3 (meaning you have the 4.3 bootloader). It will only give you a bootloop and then you will end up having to do a full wipe, resulting in losing your data. Only do this is you are on 4.2.
Click to expand...
Click to collapse
My question is now: Is all my data lost now? And if not, how can I save it / where did I go wrong?
Thank you for your help, I appreciate it!
frucade
Unlocking the bootloader wipes your device. So, yea, your data is gone. Without a custom recovery and a locked bootloader you were doomed from the beginning.
Sent from my Nexus 9 using XDA Free mobile app
Rooted LG V20 owner here, but still running stock rom. Nowadays, my most important apps won't run because my phone is rooted. The apps check for that, and complain that my phone is rooted and won't let me use them. I've tried using apps like "Hide my root" so I can keep my phone rooted, but those apps just give me errors about being unable to find the su binary and what not. And I can't seem to fix them, or rather, don't even want to try. I'm just so tired of constantly having to deal with technical issues like this... So I decided today I would bend over and accept the latest OTA update, which would most likely make me lose root and also permanently make me unable to root my phone again.
Only problem is, now my phone is stuck in a boot loop, where it always boots into TWRP. I can't decrypt the data partition, which is the first thing TWRP asks me to do. Entering the long numeric PIN I used to encrypt it (using the stock ROM encryption feature) doesn't work, so I have no clue how else to decrypt it. Thing is, I'm not sure if I even need to decrypt it. I just want my phone to boot back up normally.
I tried to reflash the "debloated" H9180s image I had saved from last time I updated my phone, wiped the cache/dalvik, and rebooted, but the boot loop remains. Presumably this is because I couldn't decrypt "data" partition first(?). Then I tried some advice from some other threads, such as this one, and this one), but nothing has worked so far. I can't reinstall twrp because when I boot in fastboot mode, adb can't see my device even though fastboot can (apparently that's due to a patch from the manufacturer to prevent users from rooting their phones). Deleting any of the fota or misc folders didn't help either (most of them weren't there, but the one I did find and deleted had no effect).
Can anyone help me get my phone to boot again? I am open to any solution, whether it keeps root or not, as long as I still have my data and apps. Hoping to eventually get rid of root or figure out how to hide it so I can use certain important apps again. But that's a later step in the process.
EDIT: I forgot to mention that holding the volume down button and the power key when booting my phone has NEVER once worked ever since I have owned this phone. The only way I've ever been able to boot into TWRP (prior to my boot loop) was to plug it into my Macbook and run "adb boot recovery." So any solution with the "volume down and power button" combo isn't going to help. Curious why this has been an issue, too.
fronzee88 said:
Rooted LG V20 owner here, but still running stock rom. Nowadays, my most important apps won't run because my phone is rooted. The apps check for that, and complain that my phone is rooted and won't let me use them. I've tried using apps like "Hide my root" so I can keep my phone rooted, but those apps just give me errors about being unable to find the su binary and what not. And I can't seem to fix them, or rather, don't even want to try. I'm just so tired of constantly having to deal with technical issues like this... So I decided today I would bend over and accept the latest OTA update, which would most likely make me lose root and also permanently make me unable to root my phone again.
Only problem is, now my phone is stuck in a boot loop, where it always boots into TWRP. I can't decrypt the data partition, which is the first thing TWRP asks me to do. Entering the long numeric PIN I used to encrypt it (using the stock ROM encryption feature) doesn't work, so I have no clue how else to decrypt it. Thing is, I'm not sure if I even need to decrypt it. I just want my phone to boot back up normally.
I tried to reflash the "debloated" H9180s image I had saved from last time I updated my phone, wiped the cache/dalvik, and rebooted, but the boot loop remains. Presumably this is because I couldn't decrypt "data" partition first(?). Then I tried some advice from some other threads, such as this one, and this one), but nothing has worked so far. I can't reinstall twrp because when I boot in fastboot mode, adb can't see my device even though fastboot can (apparently that's due to a patch from the manufacturer to prevent users from rooting their phones). Deleting any of the fota or misc folders didn't help either (most of them weren't there, but the one I did find and deleted had no effect).
Can anyone help me get my phone to boot again? I am open to any solution, whether it keeps root or not, as long as I still have my data and apps. Hoping to eventually get rid of root or figure out how to hide it so I can use certain important apps again. But that's a later step in the process.
EDIT: I forgot to mention that holding the volume down button and the power key when booting my phone has NEVER once worked ever since I have owned this phone. The only way I've ever been able to boot into TWRP (prior to my boot loop) was to plug it into my Macbook and run "adb boot recovery." So any solution with the "volume down and power button" combo isn't going to help. Curious why this has been an issue, too.
Click to expand...
Click to collapse
In twrp go to mount and make sure system is mounted, then try rebooting
Sent from my LG-H910 using XDA Labs
cnjax said:
In twrp go to mount and make sure system is mounted, then try rebooting
Click to expand...
Click to collapse
It still boots into TWRP.
fronzee88 said:
It still boots into TWRP.
Click to expand...
Click to collapse
Did you try restoring a back up
Sent from my LG-H910 using XDA Labs
cnjax said:
Did you try restoring a back up
Click to expand...
Click to collapse
I made a backup with TWRP before attempting the original update that caused this issue, but I am doubting the integrity of that backup, because I was not able to decrypt the "data" partition before making the backup. So I backed up the data partition in the encrypted state, but I am not sure if that is restorable or not. Instead, I just tried reflashing the ROM.
When I navigated to the TWRP backups folder where the backup was supposed to have been saved, I couldn't find the (most recent) backup, so I am not sure if I can actually restore anything, should the need arise.
While in TWRP:
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1
That will wipe the flags that are forcing a reboot into recovery that is trying to apply the OTA.
Once that is done, if you want to return your phone to stock, flash any 10p or higher KDZ. If you don't have download mode, there is a zip in the lafsploit thread that you can flash to get download mode back.
-- Brian
runningnak3d said:
While in TWRP:
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1
That will wipe the flags that are forcing a reboot into recovery that is trying to apply the OTA.
Click to expand...
Click to collapse
I wasn't able to get connect with my laptop from adb (unauthorized message) but I did enter the dd command in a terminal directly in twrp itself (Advanced > Terminal). It worked!!! Thank you, thank you, thank you! Whew.
If you weren't able to connect with adb, then you are running a bad copy of TWRP (3.1). That build has issues. You need to upgrade to TWRP 3.2 -- but glad you are back up and running.
-- Brian
runningnak3d said:
If you weren't able to connect with adb, then you are running a bad copy of TWRP (3.1). That build has issues. You need to upgrade to TWRP 3.2 -- but glad you are back up and running.
Click to expand...
Click to collapse
Good to know. Thanks!
runningnak3d said:
If you weren't able to connect with adb, then you are running a bad copy of TWRP (3.1). That build has issues. You need to upgrade to TWRP 3.2 -- but glad you are back up and running.
Click to expand...
Click to collapse
I'm having trouble finding the latest official TWRP download for LG V20 T-Mobile (H918). The device isn't listed on their official site. Any suggestions on how to upgrade?
TWRP 3.2: https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
-- Brian
runningnak3d said:
if you want to return your phone to stock, flash any 10p or higher KDZ. If you don't have download mode, there is a zip in the lafsploit thread that you can flash to get download mode back.
Click to expand...
Click to collapse
I'm not sure what you mean by "download" mode, but my other question is: Will flashing a KDZ cause me to lose all my data? If so, how can I make a backup of all my data if the "data" partition is encrypted? I can't get TWRP to decrypt it even when entering the correct PIN that I normally use to unlock my encrypted phone upon regular bootup.
Note that Titanium Backup is not an option if I'm planning to unroot my phone.
Yes, flashing a KDZ wipes your phone.
If your data partition is encrypted, the only way to backup your data is from within the OS (copy to SD card) or use LG backup.
Btw the reason you arnt able to get into recovery via the buttons is because you were doing it wrong, its not hold power and volume down, its actually hold volume down, press power until the screen turns on, then (still holding vol down) tap the power button (either once at exactly the right time, or repeatedly which works more consistantly) until a screen appears asking if you want to factory reset. saying yes (via the volume and power buttons) twice boots twrp if installed, else it boots the stock recovery and wipes the phone.
runningnak3d said:
While in TWRP:
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1
That will wipe the flags that are forcing a reboot into recovery that is trying to apply the OTA.
Once that is done, if you want to return your phone to stock, flash any 10p or higher KDZ. If you don't have download mode, there is a zip in the lafsploit thread that you can flash to get download mode back.
-- Brian
Click to expand...
Click to collapse
The same thing happened to me but on my V10. Would this command work on that phone?