Two weeks ago I had an ICS rom installed and was tired of the poor battery life, so I tried to unroot my phone and bring it back to stock to start over later. I got the stock 2.3.3 installed and decided not to unroot and just use the rom.
I followed this guide: http://forum.xda-developers.com/showthread.php?p=14159600#post14159600
But I didn't actually use SOC to unroot, because I wasn't sending my phone back to TMobile.
Today I was looking to see if there were any ICS roms that I might like to try out and found HFS. I downloaded it and tried to boot into CWM (Power + Vol down), and instead of going into CWM, it did the little android install splash screen, and just wiped my phone. So I installed RomManager and tried to install the rom through that. It rebooted, and did the same thing. So I "fake flashed" CWM through RomManager, and it booted into CWM finally. I thought I was in the clear, so I factory reset, wiped everything, and installed the HFS rom. It ran all the way trhough and installed successfully, until I rebooted. Now it's stuck on the white LG logo. I can't boot into CWM! It just goes to the android update splash and restarts.
To make things so much worse, I can't even boot into S/W update! I remove the battery and hold both volume buttons and plug in the USB. It does nothing. No lights, no driver installation prompt on my computer. Nothing...
What can I do at this point?
You need to re-install CWM, when you went back to stock it probably reverted your recovery to stock as well
Alright, I can get into s/w update by holding only the down arrow... But now I can't get NVFlash to acknowledge that my phone is plugged in. I've installed the LG drivers, ADB drivers and the LG Modem drivers. It doesn't ask for the APX drivers, although I've installed them in the past...
What do?
Just making sure, you are removing the battery, holding down the VOL up/down while you are plugging it in W/O the battery?
Yes I am. But it doesn't work if I push both, then plug it in. I only push the bottom and it boots into S/W
FYI, never, and I mean, NEVER use ROM Manager to flash CWM Recovery. That's like asking for a brick.
Sent from someone's Galaxy Nexus running AOKP + Franco
idbl_fanatic said:
Just making sure, you are removing the battery, holding down the VOL up/down while you are plugging it in W/O the battery?
Click to expand...
Click to collapse
DaBigums said:
Yes I am. But it doesn't work if I push both, then plug it in. I only push the bottom and it boots into S/W
Click to expand...
Click to collapse
Re-read his question. In order to get into apx mode you must remove the battery, keep it out, and, while holding the volume up AND down buttons, plug in the phone. If you already have the drivers installed itbwill not prompt for them. Just. Flash cwm with nvflash.
Sent from my LG-P999 using xda premium
Волк said:
Re-read his question. In order to get into apx mode you must remove the battery, keep it out, and, while holding the volume up AND down buttons, plug in the phone. If you already have the drivers installed itbwill not prompt for them. Just. Flash cwm with nvflash.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
My apologies for any misunderstanding as my answer was really short. But what I meant to say was, when I remove the battery and push both volume buttons down, then plug it in, I wait for 3 minutes and it still does nothing. But if I remove the battery, hold only the volume down button, it will boot into S/W. But when I use this method, it doesn't show up in the device manager as anything. I only get the sound of connecting a USB device, other than that, it's just not recognized by my PC. I've tried to run NVFlash anyway, and it says USB not connected. I'm at a complete loss...
Well I actually had a problem like this ( the not found usb part ) ehen I "bricked" my phone and what I did was I kept trying this for about 5 minutes and it worked. So my advice ie to check if you have the USB driver installed then keep trying to NVFlash.
If I helped you, push the thanks button for goodness sakes!
Related
I had a defective G2X and got a new one today. I tried to root this one the same way I did my other, but now the problems in the subject line are showing up.
*I rooted using one-click
*I couldn't get NVFlash to work using the vol up/down and pluggin in USB so I just flashed it using ROM manager
*Wiped
Now, I still cannot get NVFlash on because the phone doesn't show up while using vol up/down + plug in usb.
ROM manager doesn't have root privileges (even though one-click says phone is rooted)
Can't access recovery. It just shows the Android sitting next to the box with the orange arrow.
I do have the SDK... Is there a way to flash the 2.2.2 recovery using that? I haven't had to use ADB in ages and have forgotten most of the commands.
In addition...
Tried mounting and it is coming up as Mount: No such tool
You'll have to NVFlash properly.
I think you are forgetting to remove the battery when attempting to NVFlash.
Remove battery
Hold Vol+/- and plug in the USB
The computer should ding and load the APX drivers. Then just use the NVFlash One-Click app to load the latest ClockWorkMod.
Focus on fixing the known issues before trying to attempt another project. Besides I don't think ADB will work if the phone is dead.
Once you successfully NVFlash, from No Power, hold Vol Down and Power until it powers on and dumps you into ClockWorkMod Recovery.
There you can flash a custom rom, or restore a downloaded Stock Nandroid.
player911 said:
You'll have to NVFlash properly.
I think you are forgetting to remove the battery when attempting to NVFlash.
Remove battery
Hold Vol+/- and plug in the USB
The computer should ding and load the APX drivers. Then just use the NVFlash One-Click app to load the latest ClockWorkMod.
Focus on fixing the known issues before trying to attempt another project. Besides I don't think ADB will work if the phone is dead.
Once you successfully NVFlash, from No Power, hold Vol Down and Power until it powers on and dumps you into ClockWorkMod Recovery.
There you can flash a custom rom, or restore a downloaded Stock Nandroid.
Click to expand...
Click to collapse
After repeated attempts, I got NVflash to work properly. However, when trying to get into recovery through ROM manager, it does nothing. If I try to use the volume down key while powering up, I get the "please wait while upgrading".
EDIT: Did the same steps no less than 20 times... the 21st made it work. :shrug:
It shouldn't have been that difficult ....it's an easy 1,2,3 process ....as long as you got it to work thats fine...theres a step by step vid on YouTube on how to root our phone with NVflash...mind you its 15 min long, as long as you follow it exactly how he does it...it works!!! Good luck!
Sent from my LG-P999 using XDA App
Hi,
As the title says, I can't get into recovery. I rooted and installed CWM a few weeks ago (still on 3.1), and now when I press vol- and power buttons the tablet just boots up normally. It does another weird thing, too. If I press only on either of the volume keys, it also boots up.
I'm suspecting a FUBAR'd CWM install, but I'm not sure since I'm no expert.
Also, adb no longer sees the tablet. Typing adb devices shows nothing, and it used to work (otherwise how did I root, right?)
Any ideas on what I have to do? Nvflash a stock blob or whatever it's called?
Did you either intentionally or not run the OTA update? If you OTA'd after cwm - then you will need to unbrick/nvflash. You're behavior sounds a lot like mine, after I tried to OTA a cwm enabled transformer.
ferparedes said:
Hi,
As the title says, I can't get into recovery. I rooted and installed CWM a few weeks ago (still on 3.1), and now when I press vol- and power buttons the tablet just boots up normally. It does another weird thing, too. If I press only on either of the volume keys, it also boots up.
I'm suspecting a FUBAR'd CWM install, but I'm not sure since I'm no expert.
Also, adb no longer sees the tablet. Typing adb devices shows nothing, and it used to work (otherwise how did I root, right?)
Any ideas on what I have to do? Nvflash a stock blob or whatever it's called?
Click to expand...
Click to collapse
For the cwm thing: first of all, with your tablet turned on, try if the VOL UP and VOL DOWN keys are working. Then turn it off.
Press VOL DOWN + POWER until you see a little write on the upper left corner, then release all and press VOL UP.
For adb: turn on your tablet and connect it to your pc. On the screen of the tablet click on the icon of asus sync in the lower right corner then click on the popup. It will search for asus sync on your computer (have you installed it, right?). From that moment on, adb should work normally.
Hope this has helped.
Thanks! adb worked. Still can't get into recovery. I think it's borked, because I used "adb reboot recovery" and the tablet just rebooted normally.
Any more ideas??
akameswaran said:
Did you either intentionally or not run the OTA update? If you OTA'd after cwm - then you will need to unbrick/nvflash. You're behavior sounds a lot like mine, after I tried to OTA a cwm enabled transformer.
Click to expand...
Click to collapse
Maybe that's it. I'll try it...didn't want to, because I don't want to wipe anything. This nice device of ours is so much more complicated than my SGS
Try this app, if CWM is installed correctly it should work. Cheers.
http://forum.xda-developers.com/showthread.php?t=1173434&highlight=reboot+recovery
Thanks! CWM was definitely broken, probably because I attempted OTA update.
So I went and used the guide in the nvflash unbricking thread, and since that guide installs Prime 1.4, I went ahead and updated to 1.7. Now I'm rooted, cwm'ed and prime'd!!!!
Sent from my Transformer TF101 using Tapatalk
I just rooted my One S using this thread: http://forum.xda-developers.com/showthread.php?t=2008440. I flashed Clockworkmod touch recovery and installed the latest CM10 Nightly. I ended up installing the standard Clockworkmod recovery (non touch) through ROM manager once my phone was up and running. Everything on my phone was working great until I let my battery run all the way down to the point my phone shut off. I plugged my phone in and it automatically booted to recovery. I waited a little bit for the phone to charge and selected "reboot system now" from recovery. My phone did not boot and only goes to recovery. When it reboots, it briefly flashes a green stripe twice in the upper third of the screen prior to booting all the way but never shows the HTC screen or anything other than recovery. I tried reflashing the ROM in recovery, formatting every partition in recovery, entering fasboot using ADB, rebooting using ADB, and nothing seems to get my phone to do anything other than boot to recovery. I tried running the latest RUU and it fails (presumably because it can't enter fasboot). I tried pressing and holding volume+, -, and the power button at the same time, I tried holding just the volume down button while holding the power button, but no luck so far.
Is there a way to reflash the recovery from ADB while the phone is in recovery? Is there any other way I can force my phone into fastboot? Can I safely use the method in this thread http://forum.xda-developers.com/showthread.php?t=1990043 to "unbrick" my phone by entering commands via ADB shell while in recovery rather than in terminal emulator? Thanks in advance for all the collective XDA wisdom that I'm sure will help get my phone back up and running.
Hey I had the same problem about a week ago. Are you sure you used the latest the RUU file?
chilaca91 said:
Hey I had the same problem about a week ago. Are you sure you used the latest the RUU file?
Click to expand...
Click to collapse
I'm using RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04L_release_279577_signed.exe. I don't think it would matter which one I used though because it gives me an error that says it can't connect to the phone.
Try holding down the power button for 10 sec and then let go of the power and hold down the volume button. I had to do this a couple of times until I finally got into the bootloader
Sent from my One S using xda app-developers app
chilaca91 said:
Try holding down the power button for 10 sec and then let go of the power and hold down the volume button. I had to do this a couple of times until I finally got into the bootloader
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Amazing! That did the trick. Thanks a ton for that info. I knew it would be something simple.
I also had a similar problem. Seemed to occur only when I had the USB cable plugged into the phone. Once I removed it, I could then get into fastboot. Once I was in fastboot, I simply plugged the USB cable back in, and everything worked flawlessly.
All that crap you got wouldn't have happened if you use TWRP instead of CWM.
The CWM file in my Infuse 4g is corrupt. When holding down volume up + volume down and pressing power button; CWM restore comes up but is garbled. I can not use it. Is there anyway to solve this? The phone is bricked.
That is due to missing GB bootloaders. Search around and you will find how to flash them on download mode.
Use qkster's uclb3 heimdall one-click twice, the second time with the bootloaders checkbox ticked on.
I've been at it all day with no luck.
Went to the page suggested and could not get it to work.
Went to several more with the same luck.
Heimdall can't detect it. Odin can't detect it.
However, adb devices finds it.
adb reboot works but gets the same garbled up screen again and again.
Downloaded 3e_recovery_no_sig_check.zip
Installed it by adb push ... adb reboot recovery gives me the same garbled up cwm recovery window.
Reinstalled it several times... same thing.
I really need some help.
I have no phone... landline or other wise.
What happened was;
Rooted the phone.
Use modmanager to install cwm and install a rom.
All seemed to go well. The instructions said the new rom would boot up twice then to add the gapps zip.
It just kept booting up over and over for over an hour. (looping)
When I did the 'vol up + vol down and press power button to go into recovery mode, I got the garbled up recovery screen.
That where the phone is right now. Nothing but a brick.
Any help greatly appreciated.
dlw2
dlw1146 said:
I've been at it all day with no luck.
Went to the page suggested and could not get it to work.
Went to several more with the same luck.
Heimdall can't detect it. Odin can't detect it.
However, adb devices finds it.
adb reboot works but gets the same garbled up screen again and again.
Downloaded 3e_recovery_no_sig_check.zip
Installed it by adb push ... adb reboot recovery gives me the same garbled up cwm recovery window.
Reinstalled it several times... same thing.
I really need some help.
I have no phone... landline or other wise.
What happened was;
Rooted the phone.
Use modmanager to install cwm and install a rom.
All seemed to go well. The instructions said the new rom would boot up twice then to add the gapps zip.
It just kept booting up over and over for over an hour. (looping)
When I did the 'vol up + vol down and press power button to go into recovery mode, I got the garbled up recovery screen.
That where the phone is right now. Nothing but a brick.
Any help greatly appreciated.
dlw2
Click to expand...
Click to collapse
Do what andros11 said above
Sent from my SGH-I997 using xda premium
dlw1146 said:
I've been at it all day with no luck.
Went to the page suggested and could not get it to work.
Went to several more with the same luck.
Heimdall can't detect it. Odin can't detect it.
However, adb devices finds it.
adb reboot works but gets the same garbled up screen again and again.
Downloaded 3e_recovery_no_sig_check.zip
Installed it by adb push ... adb reboot recovery gives me the same garbled up cwm recovery window.
Reinstalled it several times... same thing.
I really need some help.
I have no phone... landline or other wise.
What happened was;
Rooted the phone.
Use modmanager to install cwm and install a rom.
All seemed to go well. The instructions said the new rom would boot up twice then to add the gapps zip.
It just kept booting up over and over for over an hour. (looping)
When I did the 'vol up + vol down and press power button to go into recovery mode, I got the garbled up recovery screen.
That where the phone is right now. Nothing but a brick.
Any help greatly appreciated.
dlw2
Click to expand...
Click to collapse
You said you used "modmanager"... did you mean ROM manager? ROM manager doesn't play well with most of these ROMs. Could be part of the problem. Get rid if it and do what andros11 said.
Sent from my SGH-I997 using xda premium
she Mbrumbe
It's working! Thank you all.
dlw
What did you do to fix it?
Sent from my SGH-I997 using xda premium
Did as andros11 suggested.
Use qkster's uclb3 heimdall one-click twice, the second time with the bootloaders checkbox ticked on.
All went well.
Also, can I root with this update?
dlw
Follow instructions in the 2nd post in the following:
http://forum.xda-developers.com/showthread.php?p=23118144
Sent from my SGH-I997 using xda premium
Having trouble getting into 'download mode' after flashing.
With data cable connected to PC and phone.
vol down + vol up + power = e3 recovery
vol down + power = normal boot
vol up + power = normal boot
Without data cable connected to phone same as above.
How do I get back into 'downoad mode'?
dlw
dlw1146 said:
Having trouble getting into 'download mode' after flashing.
With data cable connected to PC and phone.
vol down + vol up + power = e3 recovery
vol down + power = normal boot
vol up + power = normal boot
Without data cable connected to phone same as above.
How do I get back into 'downoad mode'?
dlw
Click to expand...
Click to collapse
Pull battery
Put battery back in
Hold volume +/- at the same time
Connect phone to pc while holding volume
Sent from my HTC PH39100 using Tapatalk 2
Thanks a million.
dlw
Deleted.
Sent from my SGH-I997 using xda premium
If you know how to solder make a jig, They'll save you lots of time if you have trouble getting in to Download mode.
http://galaxys2root.com/galaxy-s2-hacks/how-to-make-a-usb-jig-for-your-galaxy-s2/
Or you can buy them cheaply on flee-bay
Hi, this situation is kind of strange and I hope it's just the battery and not the whole goddamn phone.
What I'm dealing with at the moment is:
The phone doesn't boot
When plugged onto charger or USB cable it boots but stuck at Google logo after a blink and stays there. Also, Home, Back and other buttons are lighten.
When "forcefully" put into fastboot mode, e.g. after plugging it onto USB and instantly pressing Vol Up + Power it stuck there as well, volume rocker no more response neither does the power button. Also, I notice there are no commands at the end like "USB int" etc we see normally.
Fastboot or ADB returns no device found
Please help. I personally believe it could be due to battery, what do you guys think?
Thank you.
As long as you can see the google logo, your device is not bricked. GIve more useful information; like your computer operating system, the last thing you did before this happened, etc.
ej8989 said:
As long as you can see the google logo, your device is not bricked. GIve more useful information; like your computer operating system, the last thing you did before this happened, etc.
Click to expand...
Click to collapse
Thanks. My OS is Windows 8.1 Update 1. The last thing was to install UPDATE-SuperSU to root so that I can install ROM Manager to update Recovery but the installation was aborted so I attempt to flash it via Fastboot with success. Then, wanted to install SlimKat but it couldn't let me mount USB storage so that I can put the .zip file. I, then stupidly click on install via ADB but didn't know how to go back so I pulled the battery and powered up; used ADP push command to transfer said the file, but again for some reason I had to pull the battery and since then I am in above position.
Sent from my XT1032 using Tapatalk
Put the device in bootloader and plug it into the computer, be patient, my phone is rather slow to get detected sometimes.. (Up to 30 min.) Check your drivers on the computer, try rebooting the boot loader from just pressing the power button (while in boot loader mode)..
If all else fails, read up on Wugs NRTK page and about ODIN...
Sent from my Nexus S using XDA Premium 4 mobile app
Setting.Out said:
Put the device in bootloader and plug it into the computer, be patient, my phone is rather slow to get detected sometimes.. (Up to 30 min.) Check your drivers on the computer, try rebooting the boot loader from just pressing the power button (while in boot loader mode)..
If all else fails, read up on Wugs NRTK page and about ODIN...
Sent from my Nexus S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi, device doesn't go into bootloader without plugging it to computer (I've to press required buttons BEFORE plugging OTG cable). And when it boots in fastboot mode it doesn't let me press any button either. I kept it plugged in for sometime as well when it when it was at Google logo; will try to do the same while in fastboot mode too and let you know. As for drivers, same computer was used before when it was working and it detected just fine immediately (gave me a pain to find the right drivers though - PDANet was a life saver).
EDIT:
I should mention that I broke the OS before this happened by formatting /system folder and wiping other data from CWM recovery - I think, I also rebooted it without flashing the ROM as well.
BaghiXDA said:
Hi, device doesn't go into bootloader without plugging it to computer (I've to press required buttons BEFORE plugging OTG cable). And when it boots in fastboot mode it doesn't let me press any button either. I kept it plugged in for sometime as well when it when it was at Google logo; will try to do the same while in fastboot mode too and let you know. As for drivers, same computer was used before when it was working and it detected just fine immediately (gave me a pain to find the right drivers though - PDANet was a life saver).
EDIT:
I should mention that I broke the OS before this happened by formatting /system folder and wiping other data from CWM recovery - I think, I also rebooted it without flashing the ROM as well.
Click to expand...
Click to collapse
I recently had to update my drivers on my computer.. after it did an update, my phone wasn't recognized..
Try Wugs Nexus Root Toolkit,.. use the options for "bricked".. do this from the bootloader screen (power/volume +)...
I don't have experience with ODIN, so you'll need to read that forum/threads...
Setting.Out said:
I recently had to update my drivers on my computer.. after it did an update, my phone wasn't recognized..
Try Wugs Nexus Root Toolkit,.. use the options for "bricked".. do this from the bootloader screen (power/volume +)...
I don't have experience with ODIN, so you'll need to read that forum/threads...
Click to expand...
Click to collapse
The problem is, even the Toolkit doesn't recognize the device no matter what. Even the keys for ODIN don't work, aren't they Home+VOL+ and Power?
EDIT1:
Kept plugged in for little longer as suggested but it heats up (it's too hot here) so I plugged out. Going to be running it off of Linux and lets see how it goes. :fingers-crossed:
EDIT2:
Tried Adam's UnBrickable method on Linux and even that couldn't find device. But that was to be expected since Adam clearly mentioned in his post that this tool isn't for those who see anything on their screen.
Whelp! Currently I can only see I:\ drive in device manager and that's all under portable devices and that's all. I see the same even in BIOS boot options, it's listed as "Google".
Guess need to close this thread now.