Database Info

[Q] I can't boot into recovery mode after rooting

Hey all,
I used the "root your phone with Ubuntu" guide from the Nexus S Development forum, and then did a "fastboot oem lock" but when I try to reboot into recovery mode, the phone just sticks at the Google logo. I never see the /!\ icon to proceed further to install the 2.3.2 update manually.
I tried an "adb reboot recovery" to see if that would get me into recovery, but no luck there either, it just sits at the Google logo.
I have to remove the battery in order to boot the phone properly.
I'm curious how to proceed.

cormyn said:
Hey all,
I used the "root your phone with Ubuntu" guide from the Nexus S Development forum, and then did a "fastboot oem lock" but when I try to reboot into recovery mode, the phone just sticks at the Google logo. I never see the /!\ icon to proceed further to install the 2.3.2 update manually.
I tried an "adb reboot recovery" to see if that would get me into recovery, but no luck there either, it just sits at the Google logo.
I have to remove the battery in order to boot the phone properly.
I'm curious how to proceed.
Click to expand...
Click to collapse
you need to flash a recovery via fastboot.
Download the clockwork recovery recovery-clockwork-3.0.0.0-crespo.img image, and save it to the ..\android-sdk-windows\tools directory
renamed it to recovery.img
then type...
fastboot flash recovery recovery.img
and hit enter
Click to expand...
Click to collapse

simms22 said:
you need to flash a recovery via fastboot.
Click to expand...
Click to collapse
There's a new version of CWM to flash...that one you're linking is causing issues to people trying to apply updates. CWM is now 3.0.0.5
http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img

distortedloop said:
There's a new version of CWM to flash...that one you're linking is causing issues to people trying to apply updates. CWM is now 3.0.0.5
http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img
Click to expand...
Click to collapse
fixed it, thanks!

simms22 said:
you need to flash a recovery via fastboot.
Click to expand...
Click to collapse
Huh, I thought the recovery reset itself... Thanks for the info.

Ah, drag, I had already locked my nexus back up, and unlocking it is going to wipe the phone all over again.
I think if I'm going to wipe my phone anyway, I'll just wipe it back to factory and leave the phone unrooted... Too much hassle with the internal SD getting wiped every time.

cormyn said:
Huh, I thought the recovery reset itself... Thanks for the info.
Click to expand...
Click to collapse
Only after a successful reboot to the normal system, and only if you're on 2.3.1 or greater, and only if you've not renamed the /etc/install-recovery.sh file.
cormyn said:
Ah, drag, I had already locked my nexus back up, and unlocking it is going to wipe the phone all over again.
I think I'm just going to unroot my phone. Too much hassle with the internal SD getting wiped every time.
Click to expand...
Click to collapse
Yeah, that sucks. I don't relock my bootloader.

Incidentally, I had flashed a recovery, it was called recovery-clockwork-herring.img as suggested in the original "root your nexus s with ubuntu" guide. Maybe someone should tell that author to suggest a newer/better recovery.

cormyn said:
Incidentally, I had flashed a recovery, it was called recovery-clockwork-herring.img as suggested in the original "root your nexus s with ubuntu" guide. Maybe someone should tell that author to suggest a newer/better recovery.
Click to expand...
Click to collapse
Use this one: http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img

Thanks for the info, distortedloop. I think I'm just going to factory wipe and leave my phone unrooted for a while.
... assuming of course that a factory reset will get me back to a place where I can install OTA updates, or a recovery mode where I can manually install update.zip files?

distortedloop said:
Use this one: http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img
Click to expand...
Click to collapse
i was using the older CW recovery 3.0.0.0 also, so i just decided to flash version 3.0.0.5. since im at work, i cant fastboot it to my phone. i did it via the terminal emulator on my phone. 1st time i got a bunch of out of space errors so i booted into recovery just to check, and it was gone. nothing there. so i rebooted and tried it again via terminal. 2nd time was a success. to flash the recovery in the terminal emulator, download the recovery and put it on the root of your sd card and rename it recovery.img . now open the terminal and type...
su(press enter)
flash_image recovery /sdcard/recovery.img(press enter)
reboot recovery(press enter)

well, apparently a factory wipe was a bad move, 'cause now the phone rebooted and is stuck at the Google logo, like it's trying to get back into the recovery.

cormyn said:
Thanks for the info, distortedloop. I think I'm just going to factory wipe and leave my phone unrooted for a while.
... assuming of course that a factory reset will get me back to a place where I can install OTA updates, or a recovery mode where I can manually install update.zip files?
Click to expand...
Click to collapse
Factory reset won't remover the su binary and symlinks it makes. Factory reset only wipes the /data partition, not the /system one.
An oem lock, then oem unlock might, but I'm not sure...that definitely wipes the sdcard, though, unlike a factory reset does, so back that up first!
There's some thread on here someplace about how to completely remove root.

Pulled the battery, went back into bootloader mode, did a 'fastboot oem unlock', then flashed the crespo 3.0.5 img, and then 'fastboot oem lock' and the phone reboots properly.
Thanks again!

[Q] Stuck at twrp

Ok so I am stuck, I recently rooted my device and accepted the ota, big error on my part. I then proceeded to install twrp via adb commands, in Ubuntu... problem not is I am now stuck in twrp 2.6.3.2, and the touch in this version is very jenky, the bottom half doesn't accurately register touch commands. Can anyone help me to restore this device?
-note twrp bypasses download mode
-and factory restore doesn't work
-I was able to flash cloudy g3 but I can't get past twrp
-also I did an advance wipe but still couldn't get anywhere.
Please help!

nicklefloss said:
Ok so I am stuck, I recently rooted my device and accepted the ota, big error on my part. I then proceeded to install twrp via adb commands, in Ubuntu... problem not is I am now stuck in twrp 2.6.3.2, and the touch in this version is very jenky, the bottom half doesn't accurately register touch commands. Can anyone help me to restore this device?
-note twrp bypasses download mode
-and factory restore doesn't work
-I was able to flash cloudy g3 but I can't get past twrp
-also I did an advance wipe but still couldn't get anywhere.
Please help!
Click to expand...
Click to collapse
From the TWRP terminal command type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.

jsho31 said:
From the TWRP terminal command type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
Click to expand...
Click to collapse
Thanks but that doesnt work because my phone doesnt register on ubuntu

nicklefloss said:
Thanks but that doesnt work because my phone doesnt register on ubuntu
Click to expand...
Click to collapse
you use the terminal command via TWRP, not your lcomputer

[Q] Running TWRP on top of CWM with Aroma Installer??

Some of you may be wondering by the title of my thread, "Why in the world would you want to do that? Just install TWRP completely!"
The simple answer to that; I simply can't. I am unable to overwrite my recovery using goo manager/recovery flashes/terminal emulator, etc. And now you must be thinking. "Well just reset your tablet using NVFlash or the ADB Toolkit!" But alas, I just cannot for the one reason that has killed me for the past two years:
No computer will detect my Transformer.
That's right, plugging up my tablet to a computer via USB cable does nothing at all. And no, it is not my USB cable, because I have tried multiple. All I have ever wanted to do was upgrade from Android 4.1, but I cannot, because my current CWM image doesn't fully support it. So this brings us to my first question: Is it possible to run another recovery on top of my current one, just so I can flash a kitkat ROM? Is this even possible? Will it prove ineffective because it's running on top of the incompatible CWM anyway? Any and all answers will be appreaciated. I really wish I could simply use an easy Flash tool, but I just happen to be hated by all devices. Any fix to my recovery issue or my NVFlash/USB cable issue will be GREATLY appreciated! Thank you for your time

What recovery do you currently have installed?
Is there any output if you try to install a different recovery.zip?
After trying to install a new recovery, do you get a progressbar in the initial Asus bootscreen.
Does your device currently boot into android?
If so, what happens if you open a terminal in android and type
su
Does your prompt change to [email protected]?

doppelhelix said:
What recovery do you currently have installed?
Is there any output if you try to install a different recovery.zip?
After trying to install a new recovery, do you get a progressbar in the initial Asus bootscreen.
Does your device currently boot into android?
If so, what happens if you open a terminal in android and type
su
Does your prompt change to [email protected]?
Click to expand...
Click to collapse
I'm running clockworkmod touch (version 5.something) I don't get any progress bar after flashing a new recovery.zip
if I flash a new recovery.zip, it goes through successfully, but it never actually flashes. I can reboot into android via the "cold-boot" method (booting normally takes me to recovery). I don't know about the su command. I'll get back to you on that.
Edit: u0 [email protected]:/ # is what I get, so no root user. Just u0 with the root pound sign after. That's the only change

creed10 said:
That's the only change
Click to expand...
Click to collapse
Ok. That's a start.
Please download the latest TWRP 2.8.1.1 recovery. We need it because cwm is outdated for our devices.
You will also need UPDATE-SuperSU-v2.16.zip.
Boot to recovery and install the supersu.zip.
Boot to android and open the new Supersu application. If there are no errors we can continue.
Boot into recovery and flash the twrp.zip
Go back to android. Open the terminal and type
su
Now the supersu app should ask you to grant root for the terminal. Do it.
Now enter the following:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
reboot
Let the device reboot
You will notice the progressbar at the initial Asus screen.
Wait until android is fully rebooted.
Reboot to recovery. Voila, TWRP.

doppelhelix said:
Ok. That's a start.
Please download the latest TWRP 2.8.1.1 recovery. We need it because cwm is outdated for our devices.
You will also need UPDATE-SuperSU-v2.16.zip.
Boot to recovery and install the supersu.zip.
Boot to android and open the new Supersu application. If there are no errors we can continue.
Boot into recovery and flash the twrp.zip
Go back to android. Open the terminal and type
su
Now the supersu app should ask you to grant root for the terminal. Do it.
Now enter the following:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
reboot
Let the device reboot
You will notice the progressbar at the initial Asus screen.
Wait until android is fully rebooted.
Reboot to recovery. Voila, TWRP.
Click to expand...
Click to collapse
I followed everything step by step, and it all went just how you described! After nearly two years of having a screwed up tablet, you sir, have helped me resurrect it! I see a donation coming around!

Yeah, just saw that while looking at your other posts. But the thanks-button will suffice .
And you will be pleased how far this device has come. KatKiss Lollipop was just released by timduru

doppelhelix said:
Yeah, just saw that while looking at your other posts. But the thanks-button will suffice .
And you will be pleased how far this device has come. KatKiss Lollipop was just released by timduru
Click to expand...
Click to collapse
Sounds great! I will be forever in your debt, kind sir

[Q] TWRP bootloop .?.

Well, AT&T got me this time, somehow the OTA apparently auto ran a batch file, Forced a reboot to what the phone thought was stock recovery to do the OTA, WHOOPS " TEAM WIN IS NOT STOCK RECOVERY "
And now, yes you know it, every time I choose to reboot to System in twrp. It boots right back into twrp, YaY . Now I really Like team win and all, but I would also like to be able to boot back into the system style, but i don't think it is possible .?.
This is my Question, Can I ADB the Boot to recovery Flag out , remove the command .?. or something like so .?.
....A little insight, I already took the OTA before, when it actually asked me if I wanted too .?. I don't know where that option was this time ? Anyway when I took the OTA before I was only rooted. No custom recovery, And did not know it was going to be Lollipop :silly: , and also that I was going to lose some of the G2 features. YaY again So......with help from some of my friends, listed in my signature :highfive: , I returned my G2 back to Kit-Kat D80020y , but this time the OTA was Forced and I have twrp v. 2.7.0.0 installed, so yeap, this is probably known as Soft Brick. YaY
If I should just go Cloudy , let me know. I almost did it last month.
*JUST FYI IF THIS HAPPENS TO YOU, POWER YOUR DEVICE OFF INSIDE TWRP , IT IS IN THE REBOOT MENU * DON'T LET THE BATTERY DRAIN IN RECOVERY *

FOUND IT ! , MOST SIMPLE STEPS EVER TO FIX THIS PROBLEM
On your TWRP terminal command type this code ( select root / )
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
( backspace to delete fota then type misc )
type
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Then hit enter and back out of terminal to reboot system
Worked 110% for me :good:

Stuck in boot loop. Please help!

I was running on rooted H83020a with TWRP and SuperSU installed. I wanted to upgrade to 20N, and I downloaded Zip file from https://forum.xda-developers.com/tm...t/stock-h830-20n-zips-kdz-2017-12-01-t3732851
Below is the steps I followed:
1. Take a complete backup using LG Backup
2. Boot into TWRP using Quick Reboot Pro App
3. Flashed Complete Zip (H83020N) from TWRP
4. Flash SuperSU Zip (v2.82 downloaded from www.supersu.com)
5. Reboot System
I am now stuck in a boot loop. Phone shows LG logo and reboots again and again. I tried the Power button + Vol Down method, but, it doesn't work too. It gets to Factory reset screen, and after Yes and Yes, it goes to back to boot loop again. I am able to get into Download Mode and Fastboot Mode. Can I do something from here?
Can someone help please? Anyway to get into TWRP or recovery?

Thanks to @waylo. I flashed back to 20A using LGUP and KDZ file. Need to dirtycow back TWRP now. I'm still wondering what went wrong in my process.
1. Take a complete backup using LG Backup
2. Boot into TWRP
3. Flash Complete Zip (H83020N) from TWRP
4. Flash SuperSU Zip
5. Reboot System
Click to expand...
Click to collapse
Do I need to reboot to TWRP once after flashing instead of Reboot System directly after flash? Any idea?

Please help me
I have LG G5 H860 with the same case like you sir, please give me trick to repair my phone sir...

Boot into twrp and run this from an adb shell:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
This should fix the boot loop. Don't forget the bs, count and conv parts. They avoid overwriting your imei and other useful information.

drmarble said:
Boot into twrp and run this from an adb shell:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
This should fix the boot loop. Don't forget the bs, count and conv parts. They avoid overwriting your imei and other useful information.
Click to expand...
Click to collapse
Thanks! it solve my problem
my device stuck in twrp after perform a factory reset on android settings menu.
with this command I didn't have to re-flash!