Database Info

[Q] Help! I'm stuck in android system recovery!

hey guys! so i'm stuck in android system recovery and i can't really do anything.
i tried applying the update.zip but it said "signature verification failed".
problems im having.
-im NOT rooted
-everytime i reboot the phone it always goes back to system recovery
-i cant flash an update
-my computer wont even recognize the phone
-i cant go into download mode
please help. ive searched everywhere and there doesnt seem to be a clean answer.
anything helps. thanks.

You are getting that because you didn't properly push the recovery file to system/bin....BECAUSE YOU ARE NOT ROOTED. try to wipe cache and factory reset the phone from recovery to get back your android stock. Try to get into download mode using one if the methods in the download guide in the bible. Odin to kc1 with the final cwm from krylon that fbis posted. You will have root.
Please read the bible, especially the opening threads. Also, do not apply update.zip.
Sent from my SGH-T959V using XDA Premium App

Try outing in recovery using adb
Sent from my SGH-T959V using XDA App

jager555 said:
You are getting that because you didn't properly push the recovery file to system/bin....BECAUSE YOU ARE NOT ROOTED. try to wipe cache and factory reset the phone from recovery to get back your android stock. Try to get into download mode using one if the methods in the download guide in the bible. Odin to kc1 with the final cwm from krylon that fbis posted. You will have root.
Please read the bible, especially the opening threads. Also, do not apply update.zip.
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
so i dont know how i can connect to odin if my pc cant read the phone.

reinstall the drivers using the files in the bible useful files section. (http://forum.xda-developers.com/showthread.php?t=1117554)
restart the computer.
plug one end of the usb to a different port than what you had it before.
take out your sd card and your sim card and put the battery back in.
press the up+down volume keys and connect the usb cable to the phone

xXpatisXx said:
so i dont know how i can connect to odin if my pc cant read the phone.
Click to expand...
Click to collapse
oh i also have tried to get into download mode.
i tried:
- the 3 button method
- adb
none of those dont work.
please help =/

what exactly did you do to get into this?

jager555 said:
what exactly did you do to get into this?
Click to expand...
Click to collapse
a friend of mine gave me his phone and it was fully functional. but then some certain apps werent working so i tried to reset all the data through the privacy settings. and i had no luck. so i tried going into download mode but instead it took me to the recovery menu. i wiped all cache and user data and i tried to reinstall packages. its been stuck ever since.

ill show you a video of what im going through in just a sec...

also since im in recovery mode. does that mean my phone isnt bricked?
http://www.youtube.com/watch?v=eBo3630sNu0

jager555 said:
what exactly did you do to get into this?
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=eBo3630sNu0

download the usb drivers from the bible for your windows machine.. Once installed reboot the pc
once rebooted download odin 1.85 from xda or u can snag it out of my kc1 downlaod i packed it in there
oppen up odin you may have to run as admin...
with your phone powered off
press and hold
vol up and down
then insert usb
once you see the screen with a android yellow box says download your fine if you dont see that screen but odin has a light com port dont fret your ok
download dr honks kb 5 odin off the bible and flash that
it wont have the hacked signature verificaton we will get to that
once you flash the rom via odin and its up and running
go here
http://forum.xda-developers.com/showthread.php?t=1099374
download cwm final and recovery record
then download root explorer or equilvent off the market
push the reocery record to the system bin folder
you will prob have to set the system bin folder to read write then change it back to read only after
once u do that reboot phone boot cwm hit reinstall packages enjoy

RaverX3X said:
download the usb drivers from the bible for your windows machine.. Once installed reboot the pc
once rebooted download odin 1.85 from xda or u can snag it out of my kc1 downlaod i packed it in there
oppen up odin you may have to run as admin...
with your phone powered off
press and hold
vol up and down
then insert usb
once you see the screen with a android yellow box says download your fine if you dont see that screen but odin has a light com port dont fret your ok
download dr honks kb 5 odin off the bible and flash that
it wont have the hacked signature verificaton we will get to that
once you flash the rom via odin and its up and running
go here
http://forum.xda-developers.com/showthread.php?t=1099374
download cwm final and recovery record
then download root explorer or equilvent off the market
push the reocery record to the system bin folder
you will prob have to set the system bin folder to read write then change it back to read only after
once u do that reboot phone boot cwm hit reinstall packages enjoy
Click to expand...
Click to collapse
thanks but i downloaded the drivers and the phone still isnt recognized by the pc or odin. please help!

Can someone please help =[

xXpatisXx said:
Can someone please help =[
Click to expand...
Click to collapse
Did you try a different usb port?
Sent from my SGH-T959V using XDA Premium App

cnote74 said:
Did you try a different usb port?
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
yes i tried all 3 on my laptop. i just resorted to buying a usb jig. that works right?

Can't use ADB in CWM

Apparently my problem with CWM v5 is a known issue and there is a fix for it, but I can't access ADB while in CWM because Windows can't find the drivers for it even though I have the sync drivers and the windows driver package from the "how to setup adb" thread. ADB works fine when my TF is booted into Android.

brando56894 said:
I can't seem to figure out what it actually causing this since I had changed a few things when I noticed it. Whenever I boot up my TF it will boot to CWM and it doesn't matter if it's a cold boot or a reboot. I first thought it was due to AOKP since one of the things listed in the changelog of v1.4 was a fix for booting to recovery, right before this I had CM9 installed and went into rom manager and flashed the newest CWM build. The first reboot was fine and the same went for the first flash of AOKP. I forgot to flash GAPPS so I rebooted and it immediately went to recovery. I went back to my CM9 backup and it was still doing this. I flashed roach's build of CWM5 and it didn't fix anything (actually it didn't seem to stick), I flashed CWM3 to test this out and sure enough on reboot CWM5 was still there, I even tried to flash CWM3 via rom manager and it didn't do anything.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Holy crap... There's a search function. Use it.
See here: http://forum.xda-developers.com/showthread.php?t=1530337

I don't how I missed that thread, thanks for pointing it out.
Sent from my Transformer TF101 using Tapatalk

brando56894 said:
I don't how I missed that thread, thanks for pointing it out.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
No problem. I really didn't mean to be so harsh. Just kind of came out that way.

I understand I do it too One odd problem that I'm having is that Windows detects my TF when it's in Android and the drivers install successfully, yet when I reboot into CWM it tries to install the drivers but says that it can't find the necessary drivers. I have both Asus Sync and the ASUS Windows USB Drivers from here installed, do I need a third set to use it in the recovery?

brando56894 said:
I understand I do it too One odd problem that I'm having is that Windows detects my TF when it's in Android and the drivers install successfully, yet when I reboot into CWM it tries to install the drivers but says that it can't find the necessary drivers. I have both Asus Sync and the ASUS Windows USB Drivers from here installed, do I need a third set to use it in the recovery?
Click to expand...
Click to collapse
If you're able to boot into Android, move the necessary file you need to internal before booting into cwm recovery.
ADB in recovery are for those stuck in cwm recovery and can't boot into Android at all.

What operating system do you have? Win 7 64bit? I had a same problem.
I used this tutorial:
http://www.addictivetips.com/mobile/enable-adb-usb-drivers-for-nvidia-tegra-based-android-tablets/
You must change VID and PID, those you find in Computer > Properties > Device manager and select Android ADB (some device with ADB, I don't know exactly) > Properties > bookmark Details > select ID hardware and there it is.

Yea it was W7 64 I just ended up doing it in Linux because I didn't need any drivers. I dislike Windows anyway.
Sent from my Transformer TF101 using Tapatalk

ADB connection problem

Hi guys, I have a Probelm with Clockwerk Moon Recovery V5.8.1.8m
I wanted my Transformer (S / N 80) root again because I had him at Asus in repair, I'm so proceed:
- "1-Click Root Transformer" for root
- "1-Click Root Transformer" for CWM
- "Super Wipe" started for "Android_Revolution_HD-EeePad_3.4.3_3G"
- CWM update to "Clockwerk Moon Recovery V5.8.1.8m"
Since nothing works, CWM only recognizes the internal memory and I get no connection with ADB.
adb does not work, I already tried everything
I hope you can help me.
sorry for my english

r3a said:
Hi guys, I have a Probelm with Clockwerk Moon Recovery V5.8.1.8m
I wanted my Transformer (S / N 80) root again because I had him at Asus in repair, I'm so proceed:
- "1-Click Root Transformer" for root
- "1-Click Root Transformer" for CWM
- "Super Wipe" started for "Android_Revolution_HD-EeePad_3.4.3_3G"
- CWM update to "Clockwerk Moon Recovery V5.8.1.8m"
Since nothing works, CWM only recognizes the internal memory and I get no connection with ADB.
adb does not work, I already tried everything
I hope you can help me.
sorry for my english
Click to expand...
Click to collapse
Cwm 5.x.x.x doest recognise external memory use different recovery... use nvflash/easy flash to install rouge recovery you should be OK after that.... that doest work then easy flash can unroot and install latest firmware.. once you are back on stock root again using easy flash and install rouge recovery or TWRP....
Sent from my Transformer TF101 using xda app-developers app

udupa82 said:
Cwm 5.x.x.x doest recognise external memory use different recovery... use nvflash/easy flash to install rouge recovery you should be OK after that.... that doest work then easy flash can unroot and install latest firmware.. once you are back on stock root again using easy flash and install rouge recovery or TWRP....
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
I get no connection with NVFLASH, my transformer is not responding

r3a said:
I get no connection with NVFLASH, my transformer is not responding
Click to expand...
Click to collapse
When you r in nvflash/apx mode ( press power n volume up buttons together) screen is blank... so you won't see anything until you start rooting/installing cwm then you will see some lines on top left corner of your tablet in very small font... only way you know your tablet is in nvflash/apx mode is by noticing it on your laptops notification area( you will see apx device found).. use universal naked driver package to install apx drivers if windows fails to install required drivers...
Sent from my Transformer TF101 using xda app-developers app

udupa82 said:
When you r in nvflash/apx mode ( press power n volume up buttons together) screen is blank... so you won't see anything until you start rooting/installing cwm then you will see some lines on top left corner of your tablet in very small font... only way you know your tablet is in nvflash/apx mode is by noticing it on your laptops notification area( you will see apx device found).. use universal naked driver package to install apx drivers if windows fails to install required drivers...
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
I know how to get into the NVFLASH / apx mode and the screen is black, drivers will also be recognized, as I know
but I can not copy data to my Transformer
NVFLASH crash the drivers and adb server is out of date
always the same no matter what I test, other PCs, drivers or programs

[Q] asus transformer sort semi brick need help asap please...

ok so ive had my tf101 rooted since i got the thing over a year and a half ago, i was running the megatron rom which was cm9 based and everything was good. today i tried to flash Eos4 and i got F%$ked out the a$$. so i did my standard procedure which was put the rom and gapps package on my device and then i wiped everything (after making a nandroid) and flash the rom along with its gapps. then i went to reboot it then i got shot back into recovery...so i was like wtf. i then found a way where if i hold the power and volume down for about 10 seconds i could cold boot android and once booted fix this problem with my recovery. unfortunately when i go to boot into android my device just bootloops on the boot animation ( ive left for about ten mins just to make sure) then i was like oh well ill just restore my nandroid, but for some reason clockwork mod touch wont let me use my microsd card, and its also not letting me restore from the backup i made earlier, it says files not found. i tried to connect it to my pc so i could just factory reflash it but unfortunately it will not be picked up by my pc through adb or apx.
so here is my main issue,
i just need to boot into android one time successfully so i can change the location of some ROM files and fix this stupid recovery bull****.
or if i could some how factory reset the tablet completely then that would be fine too
or or i could flash a different recovery that actually worked (currently on CWM 5.8.3.4 installed from rom manager which i realize now to be a huge mistake)
and i've tried ever tool on this forum as well and nothing works because it cannot pick up my device.
*** one other side note i am running windows 8 pro 32bit through Vmware (if this can be problematic)
thanks for any help in advance

To fix this, you will need to get your tablet recognized by your computer via ADB (in recovery) or APX mode.
You could have a bad cable, or it could be the VM causing the detection issues.
Is there a way you can connect it to a computer running Windows natively?
Does your computer make the new hardware sound when connecting?
Once you get it detected via one method or the other, here are my suggestions:
APX - Use the Naked Driver 0.72 and replace whatever driver is being used. Then use EasyFlasher to install TWRP 2.2.1.4 (it blows CWM away, and can read internal AND external memory)
ADB - use the Naked Driver 0.72 and replace whatever driver is being used. Then download the TWRP 2.3.2.3 blob from the TWRP project: http://techerrata.com/browse/twrp2/tf101
Call the downloaded file TWRP.blob.
Then run the following from your computer via ADB:
Code:
adb push TWRP.blob /sdcard/
adb shell
su
dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
reboot
Make sure it is a normal reboot to complete the recovery. Then reboot to recovery and you should be able to see the external card (so long as it is formatted for FAT32).

Thanks for the quick response and it probably is because I am using vmware... Unfortunately I don't have access to a windows machine right now. But I will definitely try to find one
Sent from my SAMSUNG-SGH-I747 using xda premium

Ok so now it looks like this... All i did was flash some random ass jb rom I found in my cwm folder... It has been like this for about 15 mins
Sent from my SAMSUNG-SGH-I747 using xda premium
** edit I'm assuming it got stuck boot the apps because now a my directories seem F&#cked up too... It now goes sdcard/0/0/0/(everthing else)

That's because your recovery is not compatible with 4.2.1. TWRP recovery 2.3.2.3 or 2.3.3.x should be fine as federuco said, to fix the sdcard/0/0/... issue.
For the stuck at apps thing, usually it's because you didn't wipe everything when changing rom. Make sure to do a full reset, wipe cache dalvik and system.

Lethe6 said:
That's because your recovery is not compatible with 4.2.1. TWRP recovery 2.3.2.3 or 2.3.3.x should be fine as federuco said, to fix the sdcard/0/0/... issue.
For the stuck at apps thing, usually it's because you didn't wipe everything when changing rom. Make sure to do a full reset, wipe cache dalvik and system.
Click to expand...
Click to collapse
But my problem is I can't flash another recovery... I can't access the memory on my micro sd card... So like idk what to do
Sent from my SAMSUNG-SGH-I747 using xda premium

What happens if you reboot it after it is at the starting apps screen?
If you can get into the OS, install GooManager and install TWRP.

frederuco said:
What happens if you reboot it after it is at the starting apps screen?
If you can get into the OS, install GooManager and install TWRP.
Click to expand...
Click to collapse
I can't get into the os that's the problem... I just clean installed Windows via boot camp on my mac... Gunna try a few tools now... Hopefully I can get it back to stock... I'll update in a little bit
Sent from my SAMSUNG-SGH-I747 using xda premium

Ok so my computer can sort of detect it... I installed the drivers via brks root kit but when I plug it in in apx mode it says unknown device... Tried all my programs and they all failed...
Sent from my SAMSUNG-SGH-I747 using xda premium

Ok so I've tried to to reinstall the drivers... Tried to flash everything in apx and adb but it's not being properly detected By the PC... So I have no idea what to do at this point... If I could somehow either boot into android or flash TWRP
Sent from my SAMSUNG-SGH-I747 using xda premium

Use the Naked Drivers.
Let me find the link to the thread....
Here you go: http://forum.xda-developers.com/showthread.php?t=1514942
Grab the driver pack in the first thread, update the device using the APX driver when in APX mode.
Then you should be good to go. I have used EasyFlasher via APX with great success.

frederuco said:
Use the Naked Drivers.
Let me find the link to the thread....
Here you go: http://forum.xda-developers.com/showthread.php?t=1514942
Grab the driver pack in the first thread, update the device using the APX driver when in APX mode.
Then you should be good to go. I have used EasyFlasher via APX with great success.
Click to expand...
Click to collapse
Not to sound like a complete noob at this point but idk how to install these naked drivers
Sent from my SAMSUNG-SGH-I747 using xda premium

I think I installed the drivers right but idk can someone please like teamviwer or Google + hangout with me
Sent from my SAMSUNG-SGH-I747 using xda premium

Put your device in APX mode. To do so, make sure it's completely powered off (hold the power button 10 seconds), then hold down volume up + power for about 5 seconds. Do that while it's connected through USB. The screen will remain black so you won't see anything on the device, but you will hear a new device found in windows. Go in your device manager and look for either "unkown device" or "NVIDIA boot-recovery driver for mobile devices". If you see the nvidia one, right click and delete it; it should be come unknown. Right click the unknown device, install driver... navigate to where you extracted the naked drivers, and install.
Then use easyflasher.

Lethe6 said:
Put your device in APX mode. To do so, make sure it's completely powered off (hold the power button 10 seconds), then hold down volume up + power for about 5 seconds. Do that while it's connected through USB. The screen will remain black so you won't see anything on the device, but you will hear a new device found in windows. Go in your device manager and look for either "unkown device" or "NVIDIA boot-recovery driver for mobile devices". If you see the nvidia one, right click and delete it; it should be come unknown. Right click the unknown device, install driver... navigate to where you extracted the naked drivers, and install.
Then use easyflasher.
Click to expand...
Click to collapse
Not working... :/ I swear it's not me
Sent from my SAMSUNG-SGH-I747 using xda premium

stuck on lg logo

Wondering if anyone could point me in the right direction. I was trying to go back to stock to flash new twrp but when i wiped through advanced it wiped my phone completely. I wasnt able to get back on the Rom and now I can only get back to twrp by doing the hard factory reset. what is the best way to get my phone back? it was twrp 2.3.2 if it helps

This is what I see when I try to get into download mode
Sent from my Transformer TF101 using XDA Premium 4 mobile app

Dude that is download mode
Sent from my LG-LS980 using xda app-developers app
---------- Post added at 08:43 PM ---------- Previous post was at 08:36 PM ----------
Since your phone can not boot you must use that mode to go back to your original firmware, that I can not help you with because I have a sprint variant
Sent from my LG-LS980 using xda app-developers app

if you have custom recovery then use adb sideload and push rom of choice and that's it but if u want to go back to stock then search for threads in xda which clearly describe them.
Sent from my LG-D800 using xda app-developers app

clago87 said:
This is what I see when I try to get into download mode
Sent from my Transformer TF101 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Use this tutorial http://forum.xda-developers.com/showthread.php?t=2663369 is very easy. Or you can push the rom by RECOVERY
adb push D800_Stock_KK.zip/data/
adb push UPDATE-SuperSU-v1.93.zip/data/
Good Luck

thank you my pc is not recognizing my g2 so I am going to backtrack reinstall the drivers to see if it makes a difference

clago87 said:
thank you my pc is not recognizing my g2 so I am going to backtrack reinstall the drivers to see if it makes a difference
Click to expand...
Click to collapse
I think the easiest way is to restore from pc, just to be able to recognize your phone to your computer

my phone stuck in cwm loop
Mattx94 said:
I think the easiest way is to restore from pc, just to be able to recognize your phone to your computer
Click to expand...
Click to collapse
Hey guys, today my phone downloaded the update from at&t and to get rid of notification to install I selected install later. Well it did just that. Now I am in a bootlop of cwm and no matter what I do can I download to "download mode" or boot up. Also, I have tried a ton of new drivers and added adb to my windows 8.1 however when under command prompt i type ...adb devices...it doesnt list any device. I cannot sideload anything without the phone being recognized.
Please help!!!

Custom recovery
shades333 said:
Hey guys, today my phone downloaded the update from at&t and to get rid of notification to install I selected install later. Well it did just that. Now I am in a bootlop of cwm and no matter what I do can I download to "download mode" or boot up. Also, I have tried a ton of new drivers and added adb to my windows 8.1 however when under command prompt i type ...adb devices...it doesnt list any device. I cannot sideload anything without the phone being recognized.
Please help!!!
Click to expand...
Click to collapse
Dude, it looks like you have soft-bricked your phone. Do you have any custom recoveries installed? Are you running CM or any stock ROMS (non-AT&T)?
I ran into a boot loop earlier. Luckily I had custom recovery installed. Try these steps to get into custom recovery:
Code:
Turn your phone off.
Press volume down and power button until the LG logo comes on screen
Let go of both buttons
Hold the volume down and power buttons again until you see the "hard reset screen"
Press power once and then power again to confirm. The screen says it will reset your device but it will not as long as you have a custom recovery installed.
Your custom recovery should appear on screen.

I was able to fix it thankfully. Just had to reinstall adb from a previous file. I followed this thread
http://forum.xda-developers.com/showthread.php?t=2451696
Sent from my LG-D800 using XDA Premium 4 mobile app