I used ginger break to root my g2x. flashed a theme onto cm7/36 now I'm stuck in a bootloop and cannot for the life of me figure out this nvflash to get back to recovery. when I open the one click flash app and try to flash to the internal or external i get a unhandled exception error has occured in the app message somebody please help.
Do you have the APX drivers installed?
yes I have the apx drivers installed. running windows 7 but when i click flash on the app it give me an error and say cant find file(update) got it flashed with the nv thanks to all
Related
Totally n00bed my Nexus S.
Was running the latest Miui and installed ROM Manager. Decided to download stock Android and install.
Now the phone is boot-looped (stuck on the Nexus boot image) and Recovery seems to be gone.
I tried pushing the recovery image file but adb won't detect the device.
Any advice?
I had that once when I installed stock. I fixed it by going into recovery and clearing cache and dalvik
Sent from my Nexus S using XDA App
I can't boot into recovery though - It's missing.
theadb said:
Totally n00bed my Nexus S.
Was running the latest Miui and installed ROM Manager. Decided to download stock Android and install.
Now the phone is boot-looped (stuck on the Nexus boot image) and Recovery seems to be gone.
I tried pushing the recovery image file but adb won't detect the device.
Any advice?
Click to expand...
Click to collapse
you need to install the proper nexus s drivers.easiest way is to go to the pdanet website http://junefabrics.com/android/ , download their free product, and let it install the drivers for you. did you flash the recovery through rom manager originally? anyways, then wipe(data. factory reset) and reflash the stock rom. you always have to wipe before flashing a DIFFERENT rom, or youll get stuck in a bootloop.
I installed the 64-bit drivers from PDA already but I'm running XP 64-bit (could that be the issue?)
theadb said:
I installed the 64-bit drivers from PDA already but I'm running XP 64-bit (could that be the issue?)
Click to expand...
Click to collapse
maybe?????
Will adb still work even though I can't boot my phone and turn usb debugging on?
Unfortunately I have 64-bit windows at work, but I'll try on my Win7 or Mac at home.
Still can't get adb to or fastboot to recognize the device...maybe I'm missing something...
I have no recovery and can't boot - what can I do?
Bump. In the exact same mess.
I was on MIUI ICS and tried to go to a stock GB rom, ended up stuck at the boot animation in the fresh rom (which kept looping). Recovery was a no-go too. I tried using adb to push another stock rom which again, installed but got stuck at the boot animation. After that even adb stopped detecting the phone.
What do I do now? theadb how did you fix it?
ADB is working as I plugged in my HD2, which was detected immediately.
Er bump?
Use fastboot to flash a new recovery, then boot into recovery and do what is needed. Recovery will probably be replaced by stock each time you attempt to boot into android while the stock ROM is installed.
I'm in the exact same situation and I don't really think there's anything we can do. We can't enter fastboot. We can't go into download mode. We can't boot into recovery there is literally zilch that we can do to fix the phone.
hey guys,
I tried rooting and flashing a new rom on my friend's Nexus S and things kind of went south. The phone doesn't boot up completely. it shows the google logo but nothing more. i can get into bootloader and from there into the CMW recovery. The phone's from Fido and I believe it's an i9020a. Right now once i get into the bootloader it say's "carrier info: ATT". I'm too used to working with odin. I found the right version of the stock rom to flash but it says "error status 7. installation aborted". Can anyone help me fix the phone?
shaahinjjj said:
hey guys,
I tried rooting and flashing a new rom on my friend's Nexus S and things kind of went south. The phone doesn't boot up completely. it shows the google logo but nothing more. i can get into bootloader and from there into the CMW recovery. The phone's from Fido and I believe it's an i9020a. Right now once i get into the bootloader it say's "carrier info: ATT". I'm too used to working with odin. I found the right version of the stock rom to flash but it says "error status 7. installation aborted". Can anyone help me fix the phone?
Click to expand...
Click to collapse
What rom did you flash?
Wipe data/factory reset in CWM. Fixes most booting problems unless you flashed a wrong rom.
yes i'm pretty sure i did flash the wrong rom. I flashed a miui rom here's the link to the thread: http://forum.xda-developers.com/showthread.php?t=1869369
I just need to flash the right rom but i can't find which is the right one. I already tried what you said but no luck.
I'm trying to get the fastboot to work. before i flashed anything it was working and my drivers on my mac would recognize the phone and commands would work in the terminal. now it just doesn't recognize the phone.
After trying to install CM10 Via TWRP my phone hung on the CM10 splash page.
I have tried to reinstall CM10 and I keep having the same problem.
I'm able to access TWRP but for some odd reason I can't mount my sd card properly. I'm not able to click "Mount sd card" on the "mount" page in TWRP. That being said I can't backup my phone from a previous backup.. Any help would be greatly appreciated.
Now my phone won't even turn on.. HELP
undergrad said:
Now my phone won't even turn on.. HELP
Click to expand...
Click to collapse
Have you tried holding down the power and volume down button for longer then 10 seconds or longer? this should force restart your phone, get into TWRP and try an other Rom for now, also did you try an international rom? international roms will not work.
UPDATE: I'm guessing your also can't recover your last back up because your on HBOOT 1.14 S-ON? 1.14 will not recover boot.img's
If you manage to get it to mount to your computer (Check your drivers are installed also, EG htc sync usb drivers) then look for a "one click boot img flash" unless you know how to flash them using fastboot commands, whenever you are to flash a room, extract the boot.img from the zip file, flash that in fastboot, THEN go to recovery and flash a rom. same goes for backups. S-off is a hassle.
My computer recognizes that the phone is being plugged into the computer but it can't install the proper drivers.
Sadly I can't get my phone to go into recovery either.
undergrad said:
My computer recognizes that the phone is being plugged into the computer but it can't install the proper drivers.
Sadly I can't get my phone to go into recovery either.
Click to expand...
Click to collapse
when in twrp recovery.
1. delete cache, dav. cache, and system restore.
2. reinstall the gapp files and the CM10 zip file.
3. reboot
The issue is that I can't get into TWRP
what did you do to it? phones don't just die and cm10 didn't kill it. are you sure you flashed cm10 for the evita?
also try flashing this version of twrp openrecovery-twrp-2.3.3.1-evita.img
also run "fastboot erase cache" after flashing then try going into recovery and wiping cache,dalvik, and external
I'm trying to fix it by using the HTC Android Phone ROM Update utility, but I keep getting the follow error.. "ERROR [140]: BOOTLOADER VERSION ERROR...
I'm not currently able to boot into TWRP to install a new ROM.
undergrad said:
I'm trying to fix it by using the HTC Android Phone ROM Update utility, but I keep getting the follow error.. "ERROR [140]: BOOTLOADER VERSION ERROR...
I'm not currently able to boot into TWRP to install a new ROM.
Click to expand...
Click to collapse
well if you've unlocked your bootloader you cant upgrade with anything to do with htc and that's sure to mess with it. you're on your own sources of updates, no OTA nothing. You need to install htc sync and adb drivers for your phone if that still doesnt detect then its a usb brick and I'm of no hope but others may be
Lemagex said:
well if you've unlocked your bootloader you cant upgrade with anything to do with htc and that's sure to mess with it. you're on your own sources of updates, no OTA nothing. You need to install htc sync and adb drivers for your phone if that still doesnt detect then its a usb brick and I'm of no hope but others may be
Click to expand...
Click to collapse
I managed to relock my bootloader, but installing the stock RUU is still another story..
I can only get my computer to recognize that the phone is connected to my computer if I'm in Fastboot mode.
If you can't mount from recovery the sd got corrupted happened to me they have a fix if you do a few searchs. If you locked the bootoader and the computer only recognizes in fastboot that is good now run a RUU like 1.85
Sent from my HTC One X using xda premium
Hi
I am having a problem maybe someone can help. I had a custom rom and everything was working fine until it went into a bootloop for some reason and now I cannot seem to be able to do anything. Here is what I can and cannot do. I have TWRP 2.6.3.9 installed but I got an error message when I try to install a rom (several different ones including stock). I can put it into apx and adb mode but cant get easyrecoveryV0.42 to work only error messages athough the device is listed. I tried odin but it doesnt seem to recognize the device. I have reinstalled the drivers and tried on other computers but no luck. Could there be a problem with the partition not mounting? At this point I am willing to try anything.
Try flashing TWRP again using Easyflasher
http://forum.xda-developers.com/showthread.php?t=1688012
*Detection* said:
Try flashing TWRP again using Easyflasher
http://forum.xda-developers.com/showthread.php?t=1688012
Click to expand...
Click to collapse
I tried all three of the recoveries there and nothing. They act as though they are installing but nothing changes. I have tried some different roms from but I get an error message and they won't install.
jonnygee said:
I tried all three of the recoveries there and nothing. They act as though they are installing but nothing changes. I have tried some different roms from but I get an error message and they won't install.
Click to expand...
Click to collapse
Try this one http://forum.xda-developers.com/showthread.php?t=1995157
Just go to the "Flash" tab and select "ANDROID ONLY".
This will flash the android prime together with the recovery. After flashing, you can proceed to flash any rom using the recovery.
Dear XDA community,
I installed Clockwork recovery and the USB drivers. The device is unlocked and when in fastboot mode it is correctly identified by my PC as falcon XT1302 with an USB connection. When in recovery mode, the device appears as "Android" in the devices menu in Windows 7 and there is a yellow "!" next to it. Unfortunately after formatting system and deleting the cache as per instructions the device won't boot up. I'm stuck at the bootloader unlock warning screen. I can access fastboot mode and recovery mode but that's it.
I want to place the cyanogenmod zip inside the internal SD card of the Moto G but adb doesn't work. I get the device not found error when inputting a command. adb devices returns a blank. I don't know which drivers to install or what to do. I've tried various fixes on forums but none work. Maybe USB debugging is the problem although I distinctly remember switching it on. In any case, I can't boot so I can't change the settings.
All I want is a way to place the cyano .zip in the phone /sdcard so that I can install it. I'm all out of ideas. USB mounting doesn't seem to work. Neither does sideloader (or maybe I messed it up?) I am at wit's end.
I didn't have anything important on my phone so I did not make a backup. In hindsight, this was a stupid mistake. I've certainly learned a lot during the install attempt.
If possible please give step by step instructions. I am not a very technical person. Any help would be greatly appreciated. pls halp
kind regards
Dont worry too much if you can acces Fast Boot just download STOCK Firmware for your version I can't post links cuz im beginer searc under help "Restore STOCK Firmware" and flash it. :fingers-crossed:
Reply here i will tell you how if you not fixed it alredy
Thanks but that's not really what I want to do. I want to flash cyanogenmod on it.
regards
hechadnebiphyh said:
Thanks but that's not really what I want to do. I want to flash cyanogenmod on it.
regards
Click to expand...
Click to collapse
As above said flash stock boot up copy cm11 and gapps reboot boot loader flash cwm or twrp reboot recovery wipe data,cache,dalvik flash ROM gapps reboot all done
Sent from my Nexus 7 using Tapatalk
Thanks to the users who replied. I've managed to solve the problem. :laugh:
Would have been faster though to get your device recognized while in recovery. You can install the driver manually and it should work. Just search for seperate driver files and ignore the Windows message that it is probably 'not compatible etc.'.
Then your device is connected properly and you can get ADB sideload to work from your recovery.