Database Users

Help needed to fix rooting gone wrong

First off im sorry im adding another rooting post to these boards.
So i decided to root my 32B magic today copyed the recovery.img over and update file from the rooting wiki, loaded recovery mode then updated, but now my phone when turned on loads to the vodafone screen and freezes id left it for afew hrs but still no luck.
Here is what i know so far:
I am able to get to fastboot and fastboot usb
I cant however get to recovery mode by pressing menu+power
I can get to the recovery mode using the sdk\tools
my problem is that im sure the fix is relativly simple i.e. load some files onto sd and start again, but the problem is that i have no other way to load the files onto the sd card than through the phone and my knowledge of adb isnt that great although has improved greatly today lol.
Im not sure how correct i am on this, but would it be a possible fix to load say a rom update.zip onto the sd card and load that through recovery mode to bring it up? If that would fix it could i possible get help on the adb code needed to pass the file from computer to the phone through fastboot usb or recovery.
Thank you very much for your help

Ok i think i have figured how to push files to my sd card however whenever i try it come up saying Failed ( remote:signature verify fail)

ok well i managed to move Cyanogen's newest rom over and update to that but its still hanging up at the vodafone screen upon booting, im lost for ideas.
Please any help how ever small would be amazing right now.

please help is desperatly needed.

i am having the same issue.... and it seems NO ONE has a bloody answer to why it is failing

I successfully update to 32A and root. Then i tried to update to MT3G OTA rom and now i'm stuck at Vodafone screen. Need help or ideas and how to recover..

i had the same problem, what i did was that i found a sd card adapter and hooked it up to my computer, its pretty quick and less hassle

waacow said:
I successfully update to 32A and root. Then i tried to update to MT3G OTA rom and now i'm stuck at Vodafone screen. Need help or ideas and how to recover..
Click to expand...
Click to collapse
take out your battery and after a few seconds put it back in, before it powers up go into fastboot(back+power) and that should do it

I still have a pretty red splash screen and stucked.
neoxtian said:
take out your battery and after a few seconds put it back in, before it powers up go into fastboot(back+power) and that should do it
Click to expand...
Click to collapse
I have same problem, but your solution didn't work for me.
I did as follows.
#1. typed following command in terminal.(well, I'm using Mac)
Code:
fastboot-mac flash recovery recovery-RAv1.2.0G.img
#2. pulled battery off from phone.
#3. pluged USB cable to phone and also Mac.
#4. pressed (ENTER) in the terminal, then fastboot-mac said '< waiting for device >'.
#5. put the battery in while pressing (back)+(power)
#6. then, pretty red vodafone splash screen come up.
#7. In the terminal, it still said '< waiting for device >'. Nothing was changed.
#8. On the phone, pretty red splash screen was still there. Nothing was changed.
Those are all I have done many times for last 2 days.
But, it didn't work.
Please let me know if there is something I missed.

I tried and stuck in the exactly same problem as [robotician]. I have MT3G.

robotician said:
#5. put the battery in while pressing (back)+(power)
#6. then, pretty red vodafone splash screen come up.
#7. In the terminal, it still said '< waiting for device >'. Nothing was changed.
Click to expand...
Click to collapse
THe red vodafone should not come up. You have to hold the back key longer perhaps, because it's supposed to go into the fastboot screen with all sorts of text and three androids on skateboards at the bottom.

@Niaski
was your rom made for the 32B or the 32A?
They are very diferent phones and mixing the roms causes the issue you are seeing.

Is my HERO REALLY BRICKED!!!???

my phones rooted and I have the Regaw mod ROM load on there, and its been good for a couple days now. Last night I went to sleep and forgot to charge my phone so figured the battery died. I plugged in it for about 10-15mins or so to turn it on and all it does is hang on the HTC bootscreen!!!! then I try to boot into recovery and all I get is at the bottom of the screen it says "Build : RA-HEROC-v1.5.2"!!!! Does this mean my phone is bricked!!!???

Remove the battery. Put it back in. Try to boot.
There are other solutions. As long as it turns on there should be a way to unbrick. Try RUU as well.

i tried the battery pull a couple times im trying the RUU now but what the hell could have bricked my phone over night?

I think what the guy in the 2nd post is trying to say, is that if it is booting, it isn't bricked.
It would be bricked if you couldn't do anything with it, then its like a brick.
I know it is probably a bit scary but ify ou can boot it at all, you most likely can fix it.
Did you make any changes (remove any files?) yesterday at some point, and this would have been the first restart?
I don't know, it could be a number of things.

It is probably not bricked. I bricked my G1 so I have some experience in that area. If you can boot into recovery it is not bricked. When I bricked my G1 I couldn't even get to recovery. let it charge a bit. Th battery is probably just dead. OR. take the battery out and plug it in and try to boot. Let it boot for about 15 mins or so.

no i didnt change anything at all, except my sd card said it was corrupted after unplugging it from my PC improperly. and I didnt reformat it right away. I just tried to RUU and i got an Error 170 a USB connection error

BAttitude7689 said:
no i didnt change anything at all, except my sd card said it was corrupted after unplugging it from my PC improperly. and I didnt reformat it right away. I just tried to RUU and i got an Error 170 a USB connection error
Click to expand...
Click to collapse
Where does the recovery image read from? I know we put it in the root folder of the SD, but does it actually boot from there? Could be your issue...
are you runnings apps2sd or whatever it is called?

yes that possibly could be my issue!! how can i fix my sd card or what should I do?

no I am not running apps to SD

BAttitude7689 said:
yes that possibly could be my issue!! how can i fix my sd card or what should I do?
Click to expand...
Click to collapse
BAttitude7689 said:
no I am not running apps to SD
Click to expand...
Click to collapse
I'm not so sure. I am pretty green when it comes to all this rooting stuff. I'm just trying to help figure it out.
Maybe try booting without the SD card in the phone? Could help to narrow down the issue.
I'm sure someone with more knowledge could help.

yea im booting it now with NO SD and its still hangs at the HTC screen

BAttitude7689 said:
yea im booting it now with NO SD and its still hangs at the HTC screen
Click to expand...
Click to collapse
Can you try plugging it into your USB connection and getting into the ADB shell (in CMD) to see if you can access the phone even though it seems stuck.
I know I did this and was able to monitor the logcat when I thought it was stuck, but it was really just doing a whole bunch of stuff.
Just an idea....again, I'm just fishing here trying to help you out.

it tells me error: device not found
i went to (CMD) then cd C:\android-sdk-windows\tools and then adb devices

you might have to manually rewipe your recovery partition in cmd. I had to do that after the official ruu messed up my phone- it wouldn't boot at all, I had to use the fastboot command: fastboot oem boot, then using my nandroid backup restored my recovery.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk

im kinda of a noob at some of this so kinda need to explain it out lol ...I just booted to recovery and pressed *vol up* and got me to Fastboot Mode then it says press <Menu> to reset device, should I do that option?

okay i pressed menu and all that got me was it hanging again at the HTC screen.. should i do all of this with my SD card in or out of the phone?

When you boot it and it gets into the "partial" recovery mode, does the PC see the phone? Can you put RA-Heroc-1.6.2 onthe SD card from there? If so, I'd try flashing the new recovery from ADB...very easy...and see if that gets you a bit further along.
You might also try cheating a bit. See if you can pull a nandroid from the SD card (might have to do this with a card reader), then get Flipz's Kitchen and restore the Nandroid after you boot into recovery.
Just a couple of things I'd try....from experience...
S

okay this is what happens i press vol down and power then is load where the androids are on skateboards and it says press <HOME> for recovery along with a Fastboot mode and Simlock option. I press home and then I see the HTC screen for about 30 secs and then where I normally would see the recovery menu with all the green writing i see all black except at the bottom is says
Build : RA-heroc-v1.5.2

sfox said:
When you boot it and it gets into the "partial" recovery mode, does the PC see the phone? Can you put RA-Heroc-1.6.2 onthe SD card from there? If so, I'd try flashing the new recovery from ADB...very easy...and see if that gets you a bit further along.
You might also try cheating a bit. See if you can pull a nandroid from the SD card (might have to do this with a card reader), then get Flipz's Kitchen and restore the Nandroid after you boot into recovery.
Just a couple of things I'd try....from experience...
S
Click to expand...
Click to collapse
To follow this and break it down a bit more for you:
1. Plug in USB with phone off
2. Turn on phone and get it to the "blank" recovery screen.
3. Run through the flashing of the recovery rom image again (see HERE) but start at step 13 or so.

Try doing the above post..

G1 Reverted to RC29 stuck at "Android system recovery utility"

I have a (formerly) rooted G1 that I've attempted to revert to stock RC29 by following the "Full Downgrade Guide" at the CyanogenMod wiki.
My device had HBOOT-1.33.2005, so I used the suggested fastboot command to roll it back to HBOOT-1.33.2003 from the g1boot.zip file linked on that page. This seemed to go well, after which I rebooted into the fastboot (which was still the skateboarding androids screen) again and saw the new (old) HBOOT in the information.
Powered off the phone, inserted the SD card loaded with the DREAIMG.nbh linked in the page, and reflashed the phone. Rebooted with Send+Menu+End, and the phone kept rebooting at the T-Mobile G1 logo screen.
So, I attempted the flash again from the bootloader menu, which is now the "rainbow" style, and shows HBOOT-0.95.(something). It immediately picked up the DREAIMG.nbh file on the SD card and asked if I wanted to flash, chose yes. Same result again: a boot loop at the G1 logo.
I redownloaded the DREAIMG.nbh file without the download accelerator I'd used before, placed it on the SD card, and booted into the bootloader again, flashed, and still the same looping.
So, I attempted to access the "recovery mode" by pressing and holding menu while powering on. I got the G1 logo, then a black screen... pressing Alt-L showed "Android system recovery utility", and nothing else.
Now, the phone will do nothing BUT Android system recovery utility, regardless of what buttons I press or do not press, and I have to remove the battery to turn the damn thing off. Pressing Alt-S, Alt-W, Alt-X, or anything else does nothing.
Where should I look to try to figure out how to recover this thing?

Is a simcard in the phone? Can you get into recovery and wipe incase the partitions are confused?
(Edit, the hint was the sim card)

There's no SIM in the phone at the moment. I can't do anything at the system recovery, except turn the log on or off with Alt-L (which I guess means it's not frozen).
It isn't recognized by ADB anymore, since it has some bastardized version of the stock T-Mobile image that has USB turned off (right? I'm new at this. ).

A bit more info:
I can get into "blue light" mode, and the light is amber/green when plugged into a charger. Sometimes, when I plug the charger in the phone will turn on immediately; but not always.
When I start the phone up and it boots into the broken recovery console, Windows does see an "HTC Dream" device, but ADB doesn't see it.

ezterry said:
(Edit, the hint was the sim card)
Click to expand...
Click to collapse
Should I, or should I not have the SIM in? For what its worth, the phone behaves exactly the same either way.
Thanks for the help.

I just had this exact experience; have you made any progress, goatlordbob?

same happened to me.
cant fastboot, loop at G1 screen, and all i can see in recovery is: Android system recovery utility
some1 find some solution?

why doesnt there seem to b any help for this matter, smh

bull.. s**t
I'm in the exact same boat now. I followed those directions *to the letter* and it put my G1 in this state. Thanks to the wiki maintainer for such wonderful attention to detail. /s
Is there NO way to recover from this?

try to flash this nbh file.... http://www.4shared.com/file/9izdCbvo/DREAIMG.html

ldrifta said:
try to flash this nbh file.... http://www.4shared.com/file/9izdCbvo/DREAIMG.html
Click to expand...
Click to collapse
How? None of the key commands work. Like the OP I can hit Alt+L and it shows ""Android system recovery utility" but that's as far as it goes.

Anyone bothered booting using home + power?

shadowch31 said:
Anyone bothered booting using home + power?
Click to expand...
Click to collapse
Yes - T-Mobile G1 logo, then blank screen forever.

[Q] Stock Nexus 4 bad install of 4.3 OTA

Hello, I tried searching for this but came up empty. I have a completely stock Nexus 4, received the OTA push for 4.3. Phone has never been rooted. After going through the install process it showed the android on it's back with a red triangle and said error. After a restart the phone just sits at the Google screen!!! I'm I boned or is there a fix for this? Any info would be greatly appreciated! Thank you!

Jesmuris said:
Hello, I tried searching for this but came up empty. I have a completely stock Nexus 4, received the OTA push for 4.3. Phone has never been rooted. After going through the install process it showed the android on it's back with a red triangle and said error. After a restart the phone just sits at the Google screen!!! I'm I boned or is there a fix for this? Any info would be greatly appreciated! Thank you!
Click to expand...
Click to collapse
Try going into fastboot and flashing the stock rom from google.

gmaxpwnage said:
Try going into fastboot and flashing the stock rom from google.
Click to expand...
Click to collapse
Not sure what mode I entered, Held vlm down + power. Says Fastboot Mode in red with a big green Start at the top. Options it gives me is Start, restart bootloader, recovery mode, and power off. If I try to enter Recovery mode it says no command. Don't see anything that allows me to reinstall

Jesmuris said:
Not sure what mode I entered, Held vlm down + power. Says Fastboot Mode in red with a big green Start at the top. Options it gives me is Start, restart bootloader, recovery mode, and power off. If I try to enter Recovery mode it says no command. Don't see anything that allows me to reinstall
Click to expand...
Click to collapse
Ok, found out on the no command screen I can hold power and hit vlm up and it brings me to system recovery with these options. Reboot system, apply update from ADB, wipe data/factory reset, wipe cache partition.
Not sure what to do sadly

Try following step:
1. Press Vol up and down and powerbutton same time to get to the fastboot mode as you mention.
2. Choice Recovery Mode and press power button. If you got luck you will see an android guy with red mark on the screen.
3. Press Vol Up and Power button same time for while don't let go it will pop up a list of option clean the cache and do factory reset, then reboot system.
If this method not working. Then hard method is flash your Nexus 4 with fastboot. Search the forum there few people already post how to flash 4.3 ROM with fastboot

Johnsonyc said:
Try following step:
1. Press Vol up and down and powerbutton same time to get to the fastboot mode as you mention.
2. Choice Recovery Mode and press power button. If you got luck you will see an android guy with red mark on the screen.
3. Press Vol Up and Power button same time for while don't let go it will pop up a list of option clean the cache and do factory reset, then reboot system.
If this method not working. Then hard method is flash your Nexus 4 with fastboot. Search the forum there few people already post how to flash 4.3 ROM with fastboot
Click to expand...
Click to collapse
Ok thank you, trying this now will update:good:

Didn't work Will try other method

Jesmuris said:
Didn't work Will try other method
Click to expand...
Click to collapse
Sorry to hear this bad news Hope the other method work for you!

Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:

Jesmuris said:
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Click to expand...
Click to collapse
I had a similar experience (kind of). I had issues side-loading 4.2.2 -> 4.3 on my N4. After it finished update and rebooted I got a black screen and nothing more. I ran through it and tried to update to 4.3 again, and then it worked.
Even though it worked I've been noticing issues with it. For example, I now can no longer uninstall anything. When I attempt to uninstall any app, the phone reboots. I'm backing up now with Titanium and am about to flash. I was hoping there would be a quick fix here, but such is life. Viva la impatience.

I have same problem my stock 4.2.2 stuck x boot load , did vol up+dwn +power now stuck in "Download Mode" do not unplug the device until the process is complete .

oneguy77 said:
I have same problem my stock 4.2.2 stuck x boot load , did vol up+dwn +power now stuck in "Download Mode" do not unplug the device until the process is complete .
Click to expand...
Click to collapse
This is what I eventually followed to get mine working. I just did scenario 2 and that worked perfectly for me, so far no issues, just having to get things back to where I had them before. The second link is actually more detailed. Just make sure you follow step by step. I guess i could have not done step D10 but wanted to make sure this route worked for me. Thank you again for those who pointed me in the right direction
http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1

Jesmuris said:
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Click to expand...
Click to collapse
I have the exact same problem but not sure how to get my PC to recognize fastboot in adb mode...

FYI if you flash to stock android 4.3 and you have the 16 GB Nexus 4, make sure that after you re-flash you have the full 16 GB and not 8 GB (unless you want to re-setup your phone twice like me). If you get this problem you can wipe cache and data from recovery and voila, all of your free space is back.
---------- Post added at 10:52 PM ---------- Previous post was at 10:44 PM ----------
zpilot said:
I have the exact same problem but not sure how to get my PC to recognize fastboot in adb mode...
Click to expand...
Click to collapse
If this is what I think it is, I was having the same problem. If I went into Control Panel on my PC and it would say that the driver is failing to load. To fix this I uninstalled the driver, rebooted, reinstalled Google USB Driver from the Android SDK Manager, restarted, and all was well after that.
I really have no explanation for why this fixed it, or it didn't work before, because other than fastboot, everything was working flawlessly with getting my phone to communicate with my PC.

[Q] Tablet Ultimate Brick

So i was trying the new beta for PA android and when i was on recovery wiping as usual, the wipe process just froze there for a while, i decided to leave it till it worked again but to no avail it didnt budge at all, so i commited the ultimate sin, and powered it off by holding the power button...
when i tried again tu turn it on the tablet would go thru the google with the padlock screen and then show me a black screen with a little logo of clockworkmod and a version number below, the screen itself has no use since no matter what button i press it does nothing, other than that the tablet keeps rebooting after that.
when i try any combination of buttons to access either the real recovery or the bootloader the tablet just plain ignores that im trying to turn it on, just doesnt work, it just turns on if im not pressing anything besides the power button.
to sum up to all my problems i would love to keep trying and see if at anypoint it will turn to bootloader, i havent seen the notification of the tablet being charged... meaning that i dont know if it has enough battery to last me the remaning ideas i had.
So in a nutshell
-no bootloader
-no fastboot
-no recovery
-cant tell if battery or not
Please if anyone knows how to fix or at least get me to a bootloader i would fix everything else, but i really need the guidance here

Have you tried another charger and cable? A simple idea, but not one to over look.
Without bootloader menu or recovery, not much you can do. I'd work on getting into one of those first. Not much you can do until then.

Osivanlou said:
So i was trying the new beta for PA android and when i was on recovery wiping as usual, the wipe process just froze there for a while, i decided to leave it till it worked again but to no avail it didnt budge at all, so i commited the ultimate sin, and powered it off by holding the power button...
when i tried again tu turn it on the tablet would go thru the google with the padlock screen and then show me a black screen with a little logo of clockworkmod and a version number below, the screen itself has no use since no matter what button i press it does nothing, other than that the tablet keeps rebooting after that.
Click to expand...
Click to collapse
Are you able to get adb to recognize the device with "adb devices"?

KJ said:
Have you tried another charger and cable? A simple idea, but not one to over look.
Without bootloader menu or recovery, not much you can do. I'd work on getting into one of those first. Not much you can do until then.
Click to expand...
Click to collapse
Yeah ive tried 4 other chargers, and nothing new, i know that the os itself takes care of the charging as does the recovery in some cases, but since i have non i dont know if its gonna charge at all or not and trying doesnt sound really appealing since i should save battery in case theres a solution and needs battery power
but thanks for the answer

[email protected] said:
Are you able to get adb to recognize the device with "adb devices"?
Click to expand...
Click to collapse
Dont really know how to check, i mean i could get into the tools and try the command Adb Devices but how should i even begin to test? i mean shouldnt i be in a adb static platform on the device? if i try to get into bootloader it just doesnt turn on, and when it does it goes straight to the black screen with the clockworkmod symbol and numbers
Thanks for the answer

Osivanlou said:
Dont really know how to check, i mean i could get into the tools and try the command Adb Devices but how should i even begin to test? i mean shouldnt i be in a adb static platform on the device? if i try to get into bootloader it just doesnt turn on, and when it does it goes straight to the black screen with the clockworkmod symbol and numbers
Thanks for the answer
Click to expand...
Click to collapse
if you have enough battery and can get pc to see is thru adb. you may be able to fastboot a new rom onto the device. You can from pc Request device to go into bootloader or fast boot from the PC..
This is your only shot.. I Would suggest borrow a friends Nexus 7 Full Battery . If you do not know how to do any of this . Use skips root kit and use the unbrick or factory reset. it will force your device into fast boot and flash a new rom.
Good Luck

erica_renee said:
if you have enough battery and can get pc to see is thru adb. you may be able to fastboot a new rom onto the device. You can from pc Request device to go into bootloader or fast boot from the PC..
This is your only shot.. I Would suggest borrow a friends Nexus 7 Full Battery . If you do not know how to do any of this . Use skips root kit and use the unbrick or factory reset. it will force your device into fast boot and flash a new rom.
Good Luck
Click to expand...
Click to collapse
yeh i know how to use the skip toolkit, yet i hope i have enough battery for the test, because the only friend that i know owns a nexus 7 left the country a few months back, so the battery sounds like its gonna be hard to get. Anyways, as u were saying theres a posibility that while the tablet is rebooting and rebooting it might be able to be found on the adb devices? and use the fastboot, cuz if thats true u would be the hero ive been waiting for...
imma check and tell u later,
thanks for the answer