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?
After installing twrp using the one click root method, it restarted my V20 and I ended up in recovery mode (TWRP) and unable to boot into the OS. It seems I only have access to fastboot, download mode, and TWRP at this moment. I tried flashing the partitions with twrp, but twrp isn't realing my SD card for some odd reason, and I don't believe theres another way to move the file directly to the phone. I've been trying to work with "LG FlashTool" for hours, and keep getting the same error. Is there a reliable way to flash the OS through download mode? Thanks!
There is currently no way to flash those .tot images. What happens when you try to boot, where does it get stuck?
In TWRP you can connect to a PC and access the storage. Did you try moving the files that way?
slayerh4x said:
There is currently no way to flash those .tot images. What happens when you try to boot, where does it get stuck?
In TWRP you can connect to a PC and access the storage. Did you try moving the files that way?
Click to expand...
Click to collapse
I apologize for not checking my XDA notifications frequently enough.
I was able to copy over the .img system, boot, and recovery files to my internal storage when I was booted into TWRP then flashed them in TWRP.
Thanks for the help!
KingofPineCones said:
I apologize for not checking my XDA notifications frequently enough.
I was able to copy over the .img system, boot, and recovery files to my internal storage when I was booted into TWRP then flashed them in TWRP.
Thanks for the help!
Click to expand...
Click to collapse
I tried doing this and my system rebooted back into TWRP. Where did you get the files? Also did you ever get the encryption unsuccessful error? Whenever I install a system image or nandroid backup my phone reboots into TWRP.
crazyc78 said:
I tried doing this and my system rebooted back into TWRP. Where did you get the files? Also did you ever get the encryption unsuccessful error? Whenever I install a system image or nandroid backup my phone reboots into TWRP.
Click to expand...
Click to collapse
The encryption unsuccessful error was mentioned in the original TWRP form, you're just supposed to tap cancel and ignore it. It seems to happen every time you boot into TWRP. As for the .IMG files, I forgot where I got these but as soon as I find the post I'll be sure to give the creator credit. These worked perfectly for my H918.
Link to .zip file with the .img file-
https://drive.google.com/file/d/0B53iMlcsyyiKenAtT2k5STl0Umc/view?usp=drivesdk
(On mobile app or else I would've embedded it)
Boot into TWRP and push them through ADB into your device, then flash with TWRP. Make sure to flash system and recovery together, THEN REBOOT. If you flash system or recovery apart then reboot it might not work. I pushed them to /data/ and it worked for me. system.img is about 4GB if I remember correctly, so that one took a long time to push through ADB, about an hour and a half, just be prepared to wait a bit. Good luck!
KingofPineCones said:
The encryption unsuccessful error was mentioned in the original TWRP form, you're just supposed to tap cancel and ignore it. It seems to happen every time you boot into TWRP. As for the .IMG files, I forgot where I got these but as soon as I find the post I'll be sure to give the creator credit. These worked perfectly for my H918.
Link to .zip file with the .img file-
https://drive.google.com/file/d/0B53iMlcsyyiKenAtT2k5STl0Umc/view?usp=drivesdk
(On mobile app or else I would've embedded it)
Boot into TWRP and push them through ADB into your device, then flash with TWRP. Make sure to flash system and recovery together, THEN REBOOT. If you flash system or recovery apart then reboot it might not work. I pushed them to /data/ and it worked for me. system.img is about 4GB if I remember correctly, so that one took a long time to push through ADB, about an hour and a half, just be prepared to wait a bit. Good luck!
Click to expand...
Click to collapse
Thanks I appreciate the response, I was able to get my phone up and running by flashing a deodexed rom.
What are the commands to flash the stock system, boot image and recovery through fastboot? Is that what you used?
KingofPineCones said:
The encryption unsuccessful error was mentioned in the original TWRP form, you're just supposed to tap cancel and ignore it. It seems to happen every time you boot into TWRP. As for the .IMG files, I forgot where I got these but as soon as I find the post I'll be sure to give the creator credit. These worked perfectly for my H918.
Link to .zip file with the .img file-
https://drive.google.com/file/d/0B53iMlcsyyiKenAtT2k5STl0Umc/view?usp=drivesdk
(On mobile app or else I would've embedded it)
Boot into TWRP and push them through ADB into your device, then flash with TWRP. Make sure to flash system and recovery together, THEN REBOOT. If you flash system or recovery apart then reboot it might not work. I pushed them to /data/ and it worked for me. system.img is about 4GB if I remember correctly, so that one took a long time to push through ADB, about an hour and a half, just be prepared to wait a bit. Good luck!
Click to expand...
Click to collapse
So I downloaded this file you have in the reply... How can I flash the files in the zip through Fastboot? This currently is the only thing I can boot into to modify the system. The phone boots fine, but I cannot use ADB because it won't authorize the device. I have repeatedly tried killing the ADB server and restarting it, changed the USB ports to no avail... At this point, I cannot boot into TWRP even though it should be operational still.
andrewjt19 said:
So I downloaded this file you have in the reply... How can I flash the files in the zip through Fastboot? This currently is the only thing I can boot into to modify the system. The phone boots fine, but I cannot use ADB because it won't authorize the device. I have repeatedly tried killing the ADB server and restarting it, changed the USB ports to no avail... At this point, I cannot boot into TWRP even though it should be operational still.
Click to expand...
Click to collapse
Which TWRP version do you have? Is it RC8 or above? If its not then you are stuck until the TOT files can be used in LG UP or if we get a KDZ (Havent checked recently if a KDZ is available).
If you do there is a fail safe in TWRP (RC8 and above) that you boot to the LG factory reset and go through with it, TWRP does not execute the command and just boots to TWRP.
DarkestSpawn said:
Which TWRP version do you have? Is it RC8 or above? If its not then you are stuck until the TOT files can be used in LG UP or if we get a KDZ (Havent checked recently if a KDZ is available).
If you do there is a fail safe in TWRP (RC8 and above) that you boot to the LG factory reset and go through with it, TWRP does not execute the command and just boots to TWRP.
Click to expand...
Click to collapse
I'm running the latest version of TWRP not the RC8.
andrewjt19 said:
I'm running the latest version of TWRP not the RC8.
Click to expand...
Click to collapse
ONLY USE THIS METHOD IF YOU HAVE TWRP RC8 OR ABOVE INSTALLED!!!!! OTHERWISE YOU WILL ACTUALLY FACTORY RESET YOUR DEVICE!!!!!
While the device is powered off, press and hold Vol - and Power button. When you see the LG logo quickly release only the power button and re-press and hold the power button (Never let go of the Vol - button) This will boot you into the LG Factory reset screen. ONLY USE THIS METHOD IF YOU HAVE TWRP RC8 OR ABOVE INSTALLED!!!!! OTHERWISE YOU WILL ACTUALLY FACTORY RESET YOUR DEVICE!!!!! Choose yes to both options and you will be rebooted into TWRP. TWRP intercepts this command and ignores the factory reset part.
Will definitely give a shot. Thanks. I'll report back when I get to do it...
what are commands to flash the sys files
Hello,
I was attempting to root and install a custom ROM yesterday. I first unlocked my bootloader via ADB. Then flashed TWRP in fastboot mode using ADB. I then booted to TWRP and my internal memory said "0 GB." I wasn't able to do a backup or flash a ROM.
When I went to reboot my system it became stuck in the booting screen with the moving dots. What did I do wrong??! PLEASE HELP!
Rossco_Pee said:
Hello,
I was attempting to root and install a custom ROM yesterday. I first unlocked my bootloader via ADB. Then flashed TWRP in fastboot mode using ADB. I then booted to TWRP and my internal memory said "0 GB." I wasn't able to do a backup or flash a ROM.
When I went to reboot my system it became stuck in the booting screen with the moving dots. What did I do wrong??! PLEASE HELP!
Click to expand...
Click to collapse
Did you solve your problem ?
Once you unlock bootloader you loose all your data.
Have a try to "format" your data partition inside TWRP.
Afterwards install the custom ROM ..
Cheers
Hello everyone
as an object the twrp does not install me any rom.
I tried everything.
I can only enter bootloader and recovery and fastboot commands work.
the installation process seems to be successful, but when I reboot, recovery always comes back to me.
1.) I deleted and then reinstalled twrp via adb, nothing.
2.) I used the adb sideload command to install the rom nothing, I always restart the twrp
tips?
Hello, i am in dire need of help. I bought the new g7, flashed TWRP to recovery, installed Magisk Manager, and was happy for a bit. Long story short, a security update for my phone was released, pop ups saying "Update Failed" were getting annoying, so I naively decided it was a good idea to uninstall magisk, install the update, and reinstall magisk. Easy right? NOPE. I think Magisk messed up my partitions somehow. My phone is soft bricked, bootloops, endlessly. I can get into bootloader settings, (power + volume down), but nothing works. I can't boot into factory mode, i can't boot into TWRP. The phone shows up in fastboot, but I can't flash TWRP to recovery, it says "recovery partition not found". I am very lost, and my pictures of my Europe vacation are stuck on there. Are there any options for restoring my phone, or at least salvaging my files? Thanks in advance..
Hi There.
Maybe you can try this in order to boot into TWRP:
Code:
fastboot boot twrp-xxx.img
FoxShadow said:
Hi There.
Maybe you can try this in order to boot into TWRP:
Code:
fastboot boot twrp-xxx.img
Click to expand...
Click to collapse
Thank you for your time. I pushed TWRP to my phone, it booted fine, but I can't find my backups. My sdcard directory is filled with random folders with gibberish names, I don't know if it's encrypted or what. I had a TWRP backup in my internal storage, but as i said i can't find it. I thought maybe if i reinstalled Magisk, the bootloop would stop and i wouldn't lose information. I downloaded the .zip file to my PC, but ADB won't push to internal storage.
Terminal input (while phone is in TWRP): >adb push C:\Users\[me]\Downloads\Magisk-v19.3.zip
Output: --adb: usage: push requires an argument.
Any ideas on how to get my system back without losing my files?
gunnergilson said:
Thank you for your time. I pushed TWRP to my phone, it booted fine, but I can't find my backups. My sdcard directory is filled with random folders with gibberish names, I don't know if it's encrypted or what. I had a TWRP backup in my internal storage, but as i said i can't find it. I thought maybe if i reinstalled Magisk, the bootloop would stop and i wouldn't lose information. I downloaded the .zip file to my PC, but ADB won't push to internal storage.
Terminal input (while phone is in TWRP): >adb push C:\Users\[me]\Downloads\Magisk-v19.3.zip
Output: --adb: usage: push requires an argument.
Any ideas on how to get my system back without losing my files?
Click to expand...
Click to collapse
Dont worry. We can fix this.
No. The adb command is wrong.
Code:
adb push C:\Users\[me]\Downloads\Magisk-v19.3.zip /data/
/data is the folder in the phone where you would like to copy the Magisk file
I will make it easy for you.
Step 1. Download MagiskUninstaller from
https://github.com/topjohnwu/Magisk/releases/download/v19.3/Magisk-uninstaller-20190604.zip and save it in PC and Open a terminal/cmd in the download folder
Step 2. Boot into TWRP using
Code:
fastboot boot twrp-xxx.img
Step 3. Go to Advanced
Step 4. Press AdbSideload
Step 5. in the terminal/cmd opened in the step 1 enter
Code:
adb sideload MagiskUninstallerxxx.zip
Step 6. It will began to flash the uninstaller and Hopefully your phone will be saved.:good:
Thank you for the input, however this didn't work.
I tried sideloading the uninstaller. Here's the log:
-current boot slot: _b
-Mounting system
-Mounting vendor
-Device is system-as-root
-Device platform: arm64
!Cannot access /data, please uninstall with magisk manager
-Unmounting partitions
Updater process ended with ERROR: 1
Any other ideas? I can put files on my micro sd card, and TWRP can see that. I did that to flash the uninstaller the second time, when sideload didn't work. No luck still. I also tried installing Magisk.zip again, but still there is a bootloop. I had a full system backup made by TWRP, in my internal storage. If I could flash that, maybe it would fix the problem, but I can't seem to even find internal storage. Thanks for all the help, and I hope we can figure this out.
gunnergilson said:
Thank you for the input, however this didn't work.
I tried sideloading the uninstaller. Here's the log:
-current boot slot: _b
-Mounting system
-Mounting vendor
-Device is system-as-root
-Device platform: arm64
!Cannot access /data, please uninstall with magisk manager
-Unmounting partitions
Updater process ended with ERROR: 1
Any other ideas? I can put files on my micro sd card, and TWRP can see that. I did that to flash the uninstaller the second time, when sideload didn't work. No luck still. I also tried installing Magisk.zip again, but still there is a bootloop. I had a full system backup made by TWRP, in my internal storage. If I could flash that, maybe it would fix the problem, but I can't seem to even find internal storage. Thanks for all the help, and I hope we can figure this out.
Click to expand...
Click to collapse
You cannot find your data or you can only find gibberish filenames is because you are booting from the TWRP image. try to flash TWRP and then reboot to recovery. Then you could see the files that weren't accessible earlier.
Reference Link : https://forum.xda-developers.com/moto-g7/how-to/moto-g7-twrp-root-t3914112