Database Users

Phone won't boot and stuck with exclaimation point!

Okay, I tried to root a friend's phone with the new fresh kitchen and when the phone rebooted, I'm stuck on a screen with a phone and an exclaimation point in a triangle.
Any help here would be appreciated.
I've tried to mount the phone through sdk, but nothing..... HELP!

Turn off the phone, pull the battery if it won't turn off.
Hold the volume down key when you power it on. This should bring you into the factory bootloader.
Push menu to factory reset, this will erase all the phone's data. Then try to reboot.

While in fastboot...volume down and power button... You can try and flash the custom recovery via fastboot and adb from here

danknee said:
Turn off the phone, pull the battery if it won't turn off.
Hold the volume down key when you power it on. This should bring you into the factory bootloader.
Push menu to factory reset, this will erase all the phone's data. Then try to reboot.
Click to expand...
Click to collapse
Okay, holding the volume key down during boot brought me to the menu and I selected fastboot mode and it loaded back like nothing happened. But it appears that either the phone's not rooted or I can't get into recovery.
When I press home from that menu I just get the exclaimation point error again?
Any ideas?

jmoch2 said:
Okay, holding the volume key down during boot brought me to the menu and I selected fastboot mode and it loaded back like nothing happened. But it appears that either the phone's not rooted or I can't get into recovery.
When I press home from that menu I just get the exclaimation point error again?
Any ideas?
Click to expand...
Click to collapse
&RoidRage said:
While in fastboot...volume down and power button... You can try and flash the custom recovery via fastboot and adb from here
Click to expand...
Click to collapse
+1
Follow the instructions in RoidRage's link.

Or root your phone and install recovery .....http://forum.xda-developers.com/showthread.php?t=583291.

Are you able to send it adb commands from fastboot?
Try
Code:
adb devices

&RoidRage said:
While in fastboot...volume down and power button... You can try and flash the custom recovery via fastboot and adb from here
Click to expand...
Click to collapse
The recovery image is on the SD card but when I type the commands, I keep getting kicked back to android-skd-windows\tools command prompt.

danknee said:
Are you able to send it adb commands from fastboot?
Try
Code:
adb devices
Click to expand...
Click to collapse
yes, and I get the device name.
Image is on the SD card, can seem to get the recovery image to flash.
Edit: I'm thinking the rooting didn't go through.... I get permission denied

jmoch2 said:
yes, and I get the device name.
Image is on the SD card, can seem to get the recovery image to flash.
Click to expand...
Click to collapse
Phone may not be rooted? Follow the guide RR posted to the T. This will root the phone and flash the recovery image.
http://forum.xda-developers.com/showthread.php?t=583291

danknee said:
Phone may not be rooted? Follow the guide RR posted to the T. This will root the phone and flash the recovery image.
http://forum.xda-developers.com/showthread.php?t=583291
Click to expand...
Click to collapse
Okay, got it done with the above instructions, however now when in recovery if I try to do a nan backup I get the following error:
Error : Run 'nadriod-mobile.sh' via adb!

Also, if i'm at the command prompt, I can use adb devices to see the device, however when I type adb remount... I get "remount failed: Operation not permitted"
My phone is rooted and an adb shell command gives me #
But my friends phone which I've tried to root using fresh kitchen and manual gives me a $
What am I doing wrong?

jmoch2 said:
Okay, got it done with the above instructions, however now when in recovery if I try to do a nan backup I get the following error:
Error : Run 'nadriod-mobile.sh' via adb!
Click to expand...
Click to collapse
I remember seeing this error before and it has something to do with the SD card. The fix was something like backing up the card then formatting it. How much free space do u have on the card?
Edit: Run nandroid-mobile.sh via adb! error > http://forum.xda-developers.com/showthread.php?t=621940
jmoch2 said:
Also, if i'm at the command prompt, I can use adb devices to see the device, however when I type adb remount... I get "remount failed: Operation not permitted"
Click to expand...
Click to collapse
Are you in recovery when you try the "adb remount" command? And u went thru the rooting process w/out any errors running the "adb push" and "adb shell" commands?
Edit: you can get su(#) by typing "su" after in shell ($)

kyouko said:
I remember seeing this error before and it has something to do with the SD card. The fix was something like backing up the card then formatting it. How much free space do u have on the card?
Edit: Run nandroid-mobile.sh via adb! error > http://forum.xda-developers.com/showthread.php?t=621940
Are you in recovery when you try the "adb remount" command? And u went thru the rooting process w/out any errors running the "adb push" and "adb shell" commands?
Edit: you can get su(#) by typing "su" after in shell ($)
Click to expand...
Click to collapse
That did it! Thank you Kyouko and Danknee!

clockwork recovery not working after root

i rooted my htc my4g today using gfree and it says s-off and will let me flash it in rom manager. but it will not let me make a back up or reboot into recovery. what is wrong??

What happens when you select the 'reboot into recovery' option in ROM Manager?

it just goes to the white my touch screen and sticks...nothing at all

Are you getting any errors in ROM Manager when flashing the recovery image? You're also absolutely sure the phone is rooted, correct? ROM Manager has to ask for root access to flash the recovery, and your bootloader should show S-OFF. Those are both ways to tell if you're perm-rooted.

Try downloading the Terminal Emulator from the market [https://market.android.com/details?id=jackpal.androidterm&hl=en] and type "su" the dollar sign should change to a pound sign.
then type "reboot recovery" then the enter button.
should looks like this
Code:
$ su
# reboot recovery
and see what happens.

it just says not permited

did you reroot with VISIONary after you did the s-off process?
you have to do that to make the root stick.

[Q] Boot Mode Status Unknown?

When ever I try to run KFU, it says my boot status is unknown... I have rooted with BR3 and selected the option to install fff. My ADB Status and Rooted are fine, just not bootmode. Any suggestions?

kf is normally booted ?
is kfu working as expected ?
what do you see in device manager ? -> under "android phone"
maybe use option 1 - bootmode normal and start over

Are you able to select a number option or are you getting an error? I had the same problem but it said "indstr is not recognized as an internal or external command, operable program or batch file"
ADB Status: Online
ADB Rooted: Yes
Boot Status: Unknown

I am having the same problem I cannot get fff to install or twrp recovery but it reboots in the bootloader i even tried in the command prompt a few things can somone help me

thiskindleiskicknmyass said:
I am having the same problem I cannot get fff to install or twrp recovery but it reboots in the bootloader i even tried in the command prompt a few things can somone help me
Click to expand...
Click to collapse
I am in root though i got it with a tool for samsung phone

thiskindleiskicknmyass said:
I am in root though i got it with a tool for samsung phone
Click to expand...
Click to collapse
Same. I can't find a solution

[Q] DEAD N4? Not Really but failed to root and install recovery

I tried to root my phone today by using the Nexus 4 toolkit. In the process of rooting the phone, the use connection is physically disconnect by myself well it was an accident. After that, I only got unlocked bootloader, but I am not be able to get the recovery and the SU in the phone. When I try to repeat the steps, it is stucking at " cannot connect device" or sometimes "failed ... unknown error" or even "protocol error"(if I remember correctly. It seems that the connection is gone between the phone and the desktop under the fastboot mode. But under the normal Android OS, I am able to connect my phone to desktop to do the data transfer things.
I am seeking for help here. I hope I explain my problem properly that you guys can understand. Here is error I got sometime when I connect my phone to PC.
The button is OK in the pic.

hilts425 said:
I tried to root my phone today by using the Nexus 4 toolkit. In the process of rooting the phone, the use connection is physically disconnect by myself well it was an accident. After that, I only got unlocked bootloader, but I am not be able to get the recovery and the SU in the phone. When I try to repeat the steps, it is stucking at " cannot connect device" or sometimes "failed ... unknown error" or even "protocol error"(if I remember correctly. It seems that the connection is gone between the phone and the desktop under the fastboot mode. But under the normal Android OS, I am able to connect my phone to desktop to do the data transfer things.
I am seeking for help here. I hope I explain my problem properly that you guys can understand. Here is error I got sometime when I connect my phone to PC.
The button is OK in the pic.
Click to expand...
Click to collapse
Accidently hit the thanks button
The phone`s bootloader is allready unlocked.
- Is the phone recognized in adb and fastboot mode? If not install the 0.72 usb naked drivers.
- Flash CWM recovery in fastboot mode from here http://clockworkmod.com/rommanager, choose touche or non touch.
- flash superSU 1.20 from here http://forum.xda-developers.com/showthread.php?t=1538053 in CWM recovery.
- Install BusyBox from Google Play.
- Done.

gee2012 said:
Accidently hit the thanks button
The phone`s bootloader is allready unlocked.
- Is the phone recognized in adb and fastboot mode? If not install the 0.72 usb naked drivers.
- Flash CWM recovery in fastboot mode from here http://clockworkmod.com/rommanager, choose touche or non touch.
- flash superSU 1.20 from here http://forum.xda-developers.com/showthread.php?t=1538053 in CWM recovery.
- Install BusyBox from Google Play.
- Done.
Click to expand...
Click to collapse
how do I flash cwm in fastboot?

hilts425 said:
how do I flash cwm in fastboot?
Click to expand...
Click to collapse
Install the android sdk platform-tools and once installed:
- open cmd terminal and type: adb reboot bootloader
- type: fastboot devices and you should see a serial number if the usb drivers are nstalled correctly
- then type: fastboot flash recovery recovery-(name of the recovery).img
Read some threads to get familiar with your phone and to learn how to flash, root, use adb and it`s commands etc etc.

gee2012 said:
Accidently hit the thanks button
The phone`s bootloader is allready unlocked.
- Is the phone recognized in adb and fastboot mode? If not install the 0.72 usb naked drivers.
- Flash CWM recovery in fastboot mode from here http://clockworkmod.com/rommanager, choose touche or non touch.
- flash superSU 1.20 from here http://forum.xda-developers.com/showthread.php?t=1538053 in CWM recovery.
- Install BusyBox from Google Play.
- Done.
Click to expand...
Click to collapse
the official recovery does not work now! Any ideas?

hilts425 said:
the official recovery does not work now! Any ideas?
Click to expand...
Click to collapse
Yes it works, but it will not flash the SU zip. You need a custom recovery for that.

gee2012 said:
Yes it works, but it will not flash the SU zip. You need a custom recovery for that.
Click to expand...
Click to collapse
OK when I choose the recovery I only appears the android robot with a "!" and I can not do nothing there. Is this a bad sign?

hilts425 said:
OK when I choose the recovery I only appears the android robot with a "!" and I can not do nothing there. Is this a bad sign?
Click to expand...
Click to collapse
ok when i flash the recovery in the cmd
it says
failed (command write failed unknown error.)

[Q] stuck on recovery screen.

Hello,
I've rooted my device and installed the hellfire Kitkat rom. Since I was not fully satisfied I wanted to go back to stock rom and then install the latest update from LG.
But now the device only boots into recovery (CWM V6.0.4.7)
I can install a backup ROM but when I reboot it enters recovery again.
I tried entering download mode by pressing "volume UP key" and then plugin usb but it enters recovery again.
Can someone help me please?!

sander-w said:
Hello,
I've rooted my device and installed the hellfire Kitkat rom. Since I was not fully satisfied I wanted to go back to stock rom and then install the latest update from LG.
But now the device only boots into recovery (CWM V6.0.4.7)
I can install a backup ROM but when I reboot it enters recovery again.
I tried entering download mode by pressing "volume UP key" and then plugin usb but it enters recovery again.
Can someone help me please?!
Click to expand...
Click to collapse
I'm going to be cautious replying here because I'm a noob, but did you try using ADB to issue commands through adb sideload in cwm? If you go to "load zip" (or something along those lines) then "load using adb" (or something similar) in CWM, you can use adb to issue these commands with your computer and it should fix it (at least, it fixed a boot loop for me when I was stuck with TWRP). Here's the link:
http://forum.xda-developers.com/showthread.php?t=2451696

First of all. DON'T PANIC!
And even before that - make a nandroid backup! Go in CWM and make a full backup.
You have recovery working so you should be able to load System on it ok.
I am not an expert but let me try to guide you step by step.
1. Make a backup!
2. Download a rom on your computer. MAKE SURE ITS FOR YOUR MODEL # of LG G2
List of roms here:
3. Make sure you have over 70% battery
4. Go into recovery CWM
5. Use Wipe > Swipe to Factory Wipe
(go back on bottom right corner)
6. Go Advanced from HOME screen of CWM
7. Click ADB sideload
7b. (I assume you have the drivers loaded. If not make sure ADB is loaded in windows and device manager shows it. Download basic ADB package so you have "adb.exe" file in it)
8. put your rom in the same folder where you have "Adb.exe"
9. Open command prompt on windows. Goto the folder where ADB.exe is. Then Type "adb push (filename) /sdcard/(filename)". Example, "adb push rom.zip /sdcard/rom.zip"
10. Wait until it finishes its transfer(a message will appear saying the filename, file size and the speed of the transfer per sec when it finishes)
11. Wait for a while or reboot your cwm so that the filename will appear
12. just reflash the file in CWM (Install > choose file). Wipe after again.
13. Voila!

By any chance did you successfully go back to stock 4.2.2 and then took the OTA and then got the recovery loop? If so this will help http://forum.xda-developers.com/showthread.php?t=2451696

Drachenminister said:
By any chance did you successfully go back to stock 4.2.2 and then took the OTA and then got the recovery loop? If so this will help http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
I did manage to restore the backup rom of 4.2.2 Then I downloaded the 4.4 OTA update and installed it. Then it hangs in recovery.
Do I need to have TWRP installed or does this work with CWM too?!

sander-w said:
I did manage to restore the backup rom of 4.2.2 Then I downloaded the 4.4 OTA update and installed it. Then it hangs in recovery.
Do I need to have TWRP installed or does this work with CWM too?!
Click to expand...
Click to collapse
Basically what you need is a root shell whether it's via adb or built into recovery (cwm or twrp)
Searching the forum for "cwm bootloop ota" might give you detailed instructions for your case

Drachenminister said:
By any chance did you successfully go back to stock 4.2.2 and then took the OTA and then got the recovery loop? If so this will help http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
When I try to run "adb shell" I get a message "error: closed" what does it mean?
When I run adb devices it returns a serial number. so it looks like it is able to communicate with my g2.

sander-w said:
When I try to run "adb shell" I get a message "error: closed" what does it mean?
When I run adb devices it returns a serial number. so it looks like it is able to communicate with my g2.
Click to expand...
Click to collapse
Weird, you can try and add the commands directly enclosed in parentheses like adb shell "dd if=...."

Drachenminister said:
Weird, you can try and add the commands directly enclosed in parentheses like adb shell "dd if=...."
Click to expand...
Click to collapse
It seems that my device was in sideload mode. when I disabled sideload mode I followed the instructions on this pag
http://forum.xda-developers.com/showthread.php?t=2451696
And it worked!!!
Thanks for your help all!!!!