I am a noob to android but I was able to root my Evo via unrevoked 3 and install cm 6.1.2. Everything was perfect. Then I decided to flash a battery tweak and this is where things started going downhill.
Opened battery tweak with Rom Manager. It downloaded and installed ClockworkMod Recovery v.2.5.0.1, even though I already had v3.0.0.2 installed via unrevoked. It said I needed to flash in recovery so after booting into recovery I flashed it and rebooted.
After reboot, the screen was stuck at the white HTC Evo screen. I booted into recovery and tried a nandroid restore (that I had created with ClockworkMod v3.0.0.2) but it failed. Tried to flash cyanogenmod 6.1.2 and got the status 7 error. Tried to flash a stock rooted HTC Rom, but it also failed.
Basically I cannot boot into anything except hboot and recovery. Is there anyway to fix this or am I done for?
At this point I would run the latest RUU (ROM Update Utility) which will restore your device. It's pretty much a last resort that works in just about all situations. Are you familiar with the process?
Been at this for a couple of hours and I was able to solve it by finding the correct RUU file (based on radio version), renaming it to PC36IMG.zip and placing it into the root of the SD card. Rebooted into hboot and followed prompts and it worked out. Thanks MBeattie!
Glad you got it working. Welcome to XDA & Android.
I had this same problem and followed your advice, running RUU worked great, thank you. This happened to me after I installed one of the normal phone updates. I tried pushing an update using adb, but it just kept saying device offline. Anyways, thanks again, happy to have my phone back
I'm experiencing some issues. I flashed a bad rom and now I'm stuck at boot screen (google logo). I can enter fastboot, but I can't get into CWM. I've tried the nexus toolkit, but the ADB drivers won't function.
What do I do next?
Hope I haven't bricked my phone...
If you can enter fast boot then your phone is not bricked. Read up on how the flash the stock Google image using fast boot. You will loose all you data but you will have a working phone again.
Sent from my Galaxy Nexus using xda premium
Ok, the problem is that suddenly my computer won't see the phone as an ADB device. I've tried every usb driver I can find. I've tried the PDAnet, but I won't install properly when I can't enter the rom and tick the usb debugging mode.
killbox said:
Ok, the problem is that suddenly my computer won't see the phone as an ADB device. I've tried every usb driver I can find. I've tried the PDAnet, but I won't install properly when I can't enter the rom and tick the usb debugging mode.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1626895
I managed to get into CWM
What I'm actually trying to do is to restore a cwm backup I made before I sent my device to repair the usb port.
So far I've figured out that you must be using a ICS rom to be able to restore a ICS backup right?
killbox said:
I managed to get into CWM
What I'm actually trying to do is to restore a cwm backup I made before I sent my device to repair the usb port.
So far I've figured out that you must be using a ICS rom to be able to restore a ICS backup right?
Click to expand...
Click to collapse
Not necessarily but you will need to format/wipe data if restoring a different OS version.
Sent from my Galaxy Nexus using xda premium
Ok, will I loose everything on SD card then? included cwm backups?
killbox said:
Ok, will I loose everything on SD card then? included cwm backups?
Click to expand...
Click to collapse
Nah only app+data. Your "SD Card" will be fine.
Ok, tried that.
I get:
Error while restoring /system!
I'm not quite sure, but I think the rom I'm trying to restore is ARHD 4.1.0, while the one I have now is ARHD 6.1.0
killbox said:
Ok, tried that.
I get:
Error while restoring /system!
I'm not quite sure, but I think the rom I'm trying to restore is ARHD 4.1.0, while the one I have now is ARHD 6.1.0
Click to expand...
Click to collapse
Did you ever figure out how to fix this??
I just ran into a similar dilemma and have yet to fix it.
On my Verizon Galaxy Nexus, I had Vicious Jellybean V.5
Starting acting up.
Made a backup using CW.
Went to recovery.
Wiped the device for a clean install.
Then went to use the toolkit and the drivers wont install properly..
FML.
I can boot into FASTBOOT, CWM recovery, and ODIN. But Google logo is as far as it gets when I try to get into android..
I'm using the latest version of Galaxy Nexus Toolkit V.7.8
Any way to flash using Odin?? Way back when, there was something like odin that I used for my Droid X.. Does that exist?
PLEASE HELP :\
mikeright25 said:
Did you ever figure out how to fix this??
I just ran into a similar dilemma and have yet to fix it.
On my Verizon Galaxy Nexus, I had Vicious Jellybean V.5
Starting acting up.
Made a backup using CW.
Went to recovery.
Wiped the device for a clean install.
Then went to use the toolkit and the drivers wont install properly..
FML.
I can boot into FASTBOOT, CWM recovery, and ODIN. But Google logo is as far as it gets when I try to get into android..
I'm using the latest version of Galaxy Nexus Toolkit V.7.8
Any way to flash using Odin?? Way back when, there was something like odin that I used for my Droid X.. Does that exist?
PLEASE HELP :\
Click to expand...
Click to collapse
If you can boot into recovery you can just flash a ROM onto your phone. If for some reason you don't have one then just boot to recovery, go to mounts and storage, mount the SD card, then you should be able to put a ROM on there and flash it.
For future reference I would personally stay away from the toolkit. It's convenient but there isn't really a substitute for knowing how to do everything yourself =]
If you need more help feel free to PM me!
foxehkins said:
If you can boot into recovery you can just flash a ROM onto your phone. If for some reason you don't have one then just boot to recovery, go to mounts and storage, mount the SD card, then you should be able to put a ROM on there and flash it.
For future reference I would personally stay away from the toolkit. It's convenient but there isn't really a substitute for knowing how to do everything yourself =]
If you need more help feel free to PM me!
Click to expand...
Click to collapse
Hey,
Thanks so much for the quick response! Unfortunately, the biggest problem lies in the fact that I am unable to push anything to CWM recovery because my computer wont install the driver properly and I've been trying to figure out a way to do that or push a file to the phone for 6 hrs now
When I did a factory reset and wiped cache it actually deleted the backup that I made and everything else..
So I need to find a way to get a zip file on to the phone to flash or figure out how to get this driver working. Maybe a different computer.. Ugh.
I've been looking into ODIN and such, But this is so frustrating. Can't believe I made such a rookie mistake.
-Mike
mikeright25 said:
Did you ever figure out how to fix this??
I just ran into a similar dilemma and have yet to fix it.
On my Verizon Galaxy Nexus, I had Vicious Jellybean V.5
Starting acting up.
Made a backup using CW.
Went to recovery.
Wiped the device for a clean install.
Then went to use the toolkit and the drivers wont install properly..
FML.
I can boot into FASTBOOT, CWM recovery, and ODIN. But Google logo is as far as it gets when I try to get into android..
I'm using the latest version of Galaxy Nexus Toolkit V.7.8
Any way to flash using Odin?? Way back when, there was something like odin that I used for my Droid X.. Does that exist?
PLEASE HELP :\
Click to expand...
Click to collapse
If you can go to CWM, AND you have fastboot and adb files, you can always push one of the ROM to sdcard via "adb push ROM_NAME.zip /sdcard/"
If you don't have adb and fastboot files, just google them. It wouldn't be hard to find
mikeright25 said:
Hey,
Thanks so much for the quick response! Unfortunately, the biggest problem lies in the fact that I am unable to push anything to CWM recovery because my computer wont install the driver properly and I've been trying to figure out a way to do that or push a file to the phone for 6 hrs now
When I did a factory reset and wiped cache it actually deleted the backup that I made and everything else..
So I need to find a way to get a zip file on to the phone to flash or figure out how to get this driver working. Maybe a different computer.. Ugh.
I've been looking into ODIN and such, But this is so frustrating. Can't believe I made such a rookie mistake.
-Mike
Click to expand...
Click to collapse
Did your computer recognize the device before? If so then you shouldn't need to reinstall the drivers. PM me and I can try to wlk you through it over gtalk or something.
---------- Post added at 04:05 PM ---------- Previous post was at 03:58 PM ----------
The drivers can also be found here. http://dl.dropbox.com/u/15110285/FYA Files/GNexus-root-package-FYA.zip
Have you tried downloading the drivers again?
Sent from my Galaxy Nexus using xda app-developers app
Change operating systems..
Just uninstall all drivers, reboot, feed it the same driver again.
bk201doesntexist said:
Change operating systems..
Just uninstall all drivers, reboot, feed it the same driver again.
Click to expand...
Click to collapse
Thanks guys for the ideas
But, yes my computer used to recognize the Nexus just fine.
Now, tried all usb ports didn't work, and trying it in my old computer (with the 32bit version of win7 instead of x64) gave a pnpui.dll error (which I'm going to assume means plug n play user interface error).
The first kind of fresh idea is using ADB commands [good thought], but I haven't used those since I first got it, when the nexus was released.
And I believe, in that case the drivers will still need to be recognized..Right?
I'm going to try going through the precise steps in the WugToolkit for installing the drivers, but I have a feeling that something that affects the drivers may have been wiped when I did the whole factory reset/cache wipe (to an already corrupt version of jellybean)
Any other ideas guys?
mikeright25 said:
Thanks guys for the ideas
But, yes my computer used to recognize the Nexus just fine.
Now, tried all usb ports didn't work, and trying it in my old computer (with the 32bit version of win7 instead of x64) gave a pnpui.dll error (which I'm going to assume means plug n play user interface error).
The first kind of fresh idea is using ADB commands [good thought], but I haven't used those since I first got it, when the nexus was released.
And I believe, in that case the drivers will still need to be recognized..Right?
I'm going to try going through the precise steps in the WugToolkit for installing the drivers, but I have a feeling that something that affects the drivers may have been wiped when I did the whole factory reset/cache wipe (to an already corrupt version of jellybean)
Any other ideas guys?
Click to expand...
Click to collapse
I recommend using this package by 1wayjonny. It works perfectly and, unlike most other packages, 1wayjonny’s repack does not install any crapware along with it. That said, it doesn’t include an .exe file, so it needs to be installed manually from the .inf file. If you do not now how to do that, see here for instructions.
killbox said:
Ok, the problem is that suddenly my computer won't see the phone as an ADB device. I've tried every usb driver I can find. I've tried the PDAnet, but I won't install properly when I can't enter the rom and tick the usb debugging mode.
Click to expand...
Click to collapse
Just a quick FYI "adb" is only accessible once booted up to the rom.
I got the notification last night for the update to 4.4 and proceeded with the install, it rebooted in TWRP recovery started installing and then after 5 minutes or so it dropped back to the TWRP menu.
I tried a reboot but whatever I try and do it always boots into recovery which I take to mean the upgrade failed and something is wrong with the boot loader.
I've tried to sideload the full firmware but it just sits there saying waiting for ADB mode and does nothing.
How can I go about rescuing my N7?
Thanks for any help.
Jon
jonchill said:
I got the notification last night for the update to 4.4 and proceeded with the install, it rebooted in TWRP recovery started installing and then after 5 minutes or so it dropped back to the TWRP menu.
I tried a reboot but whatever I try and do it always boots into recovery which I take to mean the upgrade failed and something is wrong with the boot loader.
I've tried to sideload the full firmware but it just sits there saying waiting for ADB mode and does nothing.
How can I go about rescuing my N7?
Thanks for any help.
Jon
Click to expand...
Click to collapse
I dont know the fix actually. but its not safe to do an OTA update when you're not in stock(recovery)!
I had the same problem. Apparently TWRP isn't working with 4.4.
It seems to be a rule never to OTA if you're not on full stock.
Anyway, here's a solution to get you back to a working 4.3 without loosing data. I just followed the steps and they work fine:
Flashing stock factory image
Afterwards use one of the guides to manually upgrade to 4.4
bur2000 said:
I had the same problem. Apparently TWRP isn't working with 4.4.
It seems to be a rule never to OTA if you're not on full stock.
Anyway, here's a solution to get you back to a working 4.3 without loosing data. I just followed the steps and they work fine:
Flashing stock factory image
Afterwards use one of the guides to manually upgrade to 4.4
Click to expand...
Click to collapse
Thanks for this worked a treat, never to be repeated.
Hi everyone,
Just wanted to give you a few details before I get into where I'm at now.
I decided for the first time to root and flash CM11 on my Samsung Galaxy S4 and everything went flawlessly so I wanted to try it on my S3 T999. I had a lot of trouble this time around every step of the way. I tried using CM's installer that they have but every time I would switch the USB mode from MTP to PTP using the CM OneClick app, my phone would no longer get recognized AT ALL through my computer, so I factory reset it through Samsung's settings and decided to just do it using ODIN and a guide here help me along.
So I started over and followed http://forum.xda-developers.com/showthread.php?t=2563955 this guide. Downloaded ODIN, I downloaded TWRP v2.5.0.0 because it states the dt2mo users might have problems with 2.6+. Followed the rest of the guide, everything went well. Then I downloaded cm-11-20140210-SNAPSHOT-M3-d2tmo.zip and Gapps for CM 11.
Currently:
Booted into recovery, backed up to my SD card, did a factory reset, then went to install the above snapshot. It failed saying error executing updater binary in zip. I tried to restore my backup I just made and rebooted and it just sits at the Samsung logo. Not sure where to go from here. Someone in another thread mentioned to flash the latest twrp using ODIN but I tried to connect to ODIN when in download mode and the S3 doesn't get recognized.
EDIT: Two more things. I did an Advanced Wipe once. Dalvik Cache, System, Data, and Cache. And After failing to flash, when I try to reboot, TWRP states I lost root and asking if I wanted it back...
follow the instructions in this thread and flash the root 66(pre-rooted firmware) firmware for your T999:
http://forum.xda-developers.com/showthread.php?t=1949687
T999_UVUEMJC
Official JB Firmware - Latest JB 4.3 Firmware
Cobra281 said:
follow the instructions in this thread and flash the root 66(pre-rooted firmware) firmware for your T999:
http://forum.xda-developers.com/showthread.php?t=1949687
T999_UVUEMJC
Official JB Firmware - Latest JB 4.3 Firmware
Click to expand...
Click to collapse
I'm currently downloading root 66 for T999 but I have tried to connect through ODIN before and it is no longer recognizing my phone. Nothing happens. I had this problem all day yesterday after messing with the usb connections that I mentioned in my first post.
EDIT!:
It seems as though already having connected the phone to the computer and THEN booting into download mode recognized the phone and started downloading the drivers.
3itmn said:
I'm currently downloading root 66 for T999 but I have tried to connect through ODIN before and it is no longer recognizing my phone. Nothing happens. I had this problem all day yesterday after messing with the usb connections that I mentioned in my first post.
EDIT!:
It seems as though already having connected the phone to the computer and THEN booting into download mode recognized the phone and started downloading the drivers.
Click to expand...
Click to collapse
also i presume that you're using the stock\original Samsung USB cable that came with the S3?
Cobra281 said:
also i presume that you're using the stock\original Samsung USB cable that came with the S3?
Click to expand...
Click to collapse
Thank you for linking me to that firmware! That worked, I'm back up and running 4.3. I would still like to be able to flash CM11 but I don't know what I did wrong. Should I have went with the latest TWRP or used something else?
3itmn said:
Thank you for linking me to that firmware! That worked, I'm back up and running 4.3. I would still like to be able to flash CM11 but I don't know what I did wrong. Should I have went with the latest TWRP or used something else?
Click to expand...
Click to collapse
not a problem. personally, i like TWRP, especially since it installs automatically when you download the GooManager app
Okay so here's the thing. I been following XDA for a while and I never had a problem with rooting and installing roms. Yesterday we received a Samsung Galaxy Tab 3 from Sprint. I believed it's the T217S version but anyways I looked up info and found out how to root it and put a custom recovery. Everything went fine until I decided to install the Remedy Rom. Now I wasn't sure if I had to wipe anything but just to be safe I did except the SD card. After that I Installed the Remedy Rom but before I could install the Knox Remover 1.2 it had already rebooted when it rebooted it bricked on the Samsung Logo. Now I began to panic but I researched and found out running the Stock Rom from Odin would fix this little issue. After running it back to stock. I again tried to get into Recovery but this time I got a different Recovery it said no command in the background and in the top Android system recovery. I remember I installed TWRP. I'm not sure what went wrong but now I can't restore it back to how it was. I can't even get into download mode to re root it.
Can anyone help me with this dilemma?
Can no one help me with this issue?
There was a recent sprint update to this device as of a few days ago. It's possible that the older rooting and recovery may not be compatible.
You might be able to Odin back to the prior version, then try root/recovery.
cougarcougar said:
There was a recent sprint update to this device as of a few days ago. It's possible that the older rooting and recovery may not be compatible.
You might be able to Odin back to the prior version, then try root/recovery.
Click to expand...
Click to collapse
Thank you for the reply. As I said I cant access download mode anymore so how can I run Odin through it? I can still boot into the Device itself I just can't enter recovery or download mode.