Related
Before you tell me to 'Google it' (which I have, and leads me to 1000 posts of people telling other people with the same problem to 'Google it'), please read.
I will PayPal anyone $20 with working instructions of how to resolve this
Phone: HTC Hero w/ chin
Carrier: Alltel
Story:
Switched from WM6 Palm Treo Pro to HTC Hero. Came with 2.1 and needed apps2sd. Want CM7 stable.
-Rooted using AndRoot.
-Installed SuperUser and Root Checker. Root Checker said I was good to go. SuperUser would not show any apps in the list this whole time.
-Installed Titanium Backup which said I needed BusyBox, but it would fail to install. Tried to install busybox and it said I was not rooted. Alright...
-Installed ClockworkMod and flashed recovery. Tried to reboot into clockwork recovery, but when I clicked it, it did nothing. When I clicked rom from sd card, and clicked the CM7, it said 'going to reboot now' but again, nothing happened.
I booted into recovery manually, but it was still in Android system recovery. Apparently there was some sort of rooting problem, so I tried z4root. Permanent root was stuck on 'rebooting', and temporary root said successful, but something was still wrong as BusyBox installer would say I was not rooted, and SuperUser app didn't show any programs to allow permissions.
I turned the phone off, and back on. It goes to the white 'HTC' screen, reboots, and then comes to a black page with a picture of a Hero and a red triangle and exclamation mark. I hold home and hit power, and it takes me into the Android system recovery. I wiped data and cleared cache, rebooted, and it does the same thing.
- - -
Now i've done many hours of research, and found nothing to help me. I guess i'm a bit confused on what the SDK does and how to use it, because it won't connect to my phone since I can't even boot my phone into the OS. I tried to download the RUU and rename it update.zip, but it says signature verification failed or not found in android recovery. I've done the clear data method by holding home, back, and power, but still nothing.
I need a clearcut answer for getting back to a stock Alltel 2.1 OS on my phone. I am more advanced than a basic user, and have flashed many roms on Windows Mobile, but remember I might not exactly understand everything.
I'm a silent browser on these forums but now I come to you guys for help. I hope to grow into a dev and hopefully help someone in the future in my position.
I read somewhere to wipe EXT2, but still confused on that process as it seems I don't know how to get into adb command line on my computer.
Try reflashing the cwm recovery. Sounds like you have no recovery image.
-----
Sent from my CDMA Hero. I got some hot Gingerbread-on-Hero action here!
Dumb question...did you flash a ROM? Maybe I missed it in your post, but I see you installed Clockwork, SuperUser and all that, but don't see that you flashed a ROM. *EDIT* I see you did...
So...worst case scenario, if you can't even boot your phone, just start over from scratch...
Download the original AllTel ROM from here.
If you don't have HTC Sync set up and can't restore from your computer, use this method to flash it...your phone should now boot...
Then try to reroot, using this (preferred) or this.
Download ROM Manager from the Market and install ClockworkMod Recovery
Boot to recovery (hold home and power at the same time).
Once in recovery, wipe cache, system, data and boot (make sure you don't wipe your sd card! Do it twice for good measure)
Select install .zip from SD card, select zip and you should be good to go with a rooted phone and a new ROM.
I think that should cover it...
Ok, on your first link to flash my phone, the step says:
"With phone powered on, do "adb reboot bootloader" to enter fastboot."
How do I get the command prompt on my computer to communicate with the phone? That was my biggest problem when reading other people's posts. I guess i'm a bit lost. I installed the r10 android sdk which I believe is the first step? And when my phone is connected to the computer to enter these commands, is it okay if it is sitting at that screen with the red triangle?
Thanks for your help btw your steps sound simple, and simple is nice. One step closer!
Do you have HTC Sync set up? If you do, you should be able to restore from that to get you back to official AllTel...That's going to be the easiest way to get you back to stock I think.
And...I am on a Mac So, helping someone on a PC is not my forte with ADB
I'd try setting up HTC Sync and get yourself back to stock that way.
EDIT - To get it to communicate, you need to set up ADB and all that. Then just use command prompts...Try this thread for help/instructions.
I actually got it to load that rom with vol down + power but eventually got to 'CID incorrect! Update fail!', so i'll try connecting to sync.
damienisxcore said:
I actually got it to load that rom with vol down + power but eventually got to 'CID incorrect! Update fail!', so i'll try connecting to sync.
Click to expand...
Click to collapse
What ROM? The AllTel one?
I have to take off until about 8:30 or so...get yourself set up with HTC Sync and get the USB drivers and all that set up, first thing you need to do is get your computer to talk to your phone...download the official AllTel RUU and restore to stock. That's task 1
Then we'll get ya rooted
I think I found a rom that worked. Currently rebooting. I can follow the rest and if I need anymore help, I'll give you a hollar. I should have had it right the first time, but I was following about 5 sets of different directions and mixing them around to avoid certain programs. I like yours though.
Send me a PM with your paypal e-mail and I can send it over. Least I could do.
OP, glad you got it. What rom?
Ranger, nice!
sent from a series of tubes.
il Duce said:
OP, glad you got it. What rom?
Ranger, nice!
sent from a series of tubes.
Click to expand...
Click to collapse
He flashed CM7. Gotta get him on aospCMod
damienisxcore said:
I think I found a rom that worked. Currently rebooting. I can follow the rest and if I need anymore help, I'll give you a hollar. I should have had it right the first time, but I was following about 5 sets of different directions and mixing them around to avoid certain programs. I like yours though.
Send me a PM with your paypal e-mail and I can send it over. Least I could do.
Click to expand...
Click to collapse
It's tough sometimes to follow things...and as much as we always tell people to search, ya know, the search kinda sucks I searched for all the threads I linked for you, but I knew what I was looking for. If you don't know what to look for, searching is kinda tough. Glad you got it!
Now...if you want a real ROM, I'll just toss this one out there In all actuality, CM7 and aospCMod are quite similar, I am just partial to aosp's builds.
Let me know if you need any more help.
- Did google searches and on here but my problems seem different to others or I don't understand the solution.
I installed the stock orange latest rom not knowing it would rid me of root and all that so I'm trying to get back to recovery so I can nanbackup back to leedroid.
What I have done so far -
1) Downgraded (was an absolute pain, took many attempts seems that rooting twice screws things over)
2) Rooted using visionary+ - comfirmed I am rooted
3) Installed rom manager and reflashed recovery with it.
4) Open recovery and get a Red exclamation mark in a red triangle.
Interwebz tells me this means I have no recovery or am not rooted. I am rooted and I have reinstalled recovery.
What have I got to do to fix this?
Please do help
:EDIT:
had an idea while trying to cold boot into it it is reading the file i have on there to downgrade with and I think that is causing the problems.
:EDIT2:
didn't fix it. Sigh. Really need help guys.
8igdave said:
- Did google searches and on here but my problems seem different to others or I don't understand the solution.
I installed the stock orange latest rom not knowing it would rid me of root and all that so I'm trying to get back to recovery so I can nanbackup back to leedroid.
What I have done so far -
1) Downgraded (was an absolute pain, took many attempts seems that rooting twice screws things over)
2) Rooted using visionary+ - comfirmed I am rooted
3) Installed rom manager and reflashed recovery with it.
4) Open recovery and get a Red exclamation mark in a red triangle.
Interwebz tells me this means I have no recovery or am not rooted. I am rooted and I have reinstalled recovery.
What have I got to do to fix this?
Please do help
Click to expand...
Click to collapse
ok my friend this could happen because you are not ablr to root the DHD perhpahs it has the last OTA or used an RUU to actualize to last version, doublecheck the firmware version on the phone, then i will explain a little more (i know its painful already have been victim by the rooting process)
good luck
I am getting so god damn pissed off with this. As I took my battery out for the 100th time I thought to my self mmm this is gonna break if I'm not careful and out pops my volume rocker. Had to bend it to get it back in. Don't evne understand why this is all happening. I did this all fine the first time around.
Firmware is 132.405.6
The rooting isn't the problem, its recovery which is.
Just discovered holding up and pushiung power button is meant to get you into CWM but i get "E:can't open /cache/recovery/command"
Annoyingly it lets me reboot and would ahve saved my volume rocker
:EDIT:
Christ I forgot to plug my phone up to the pc and run s-off. What a bloody moron.
I couldn't hate my self much more right now *strokes his bent volume rocker*
:EDIT2:
S-OFF didn't fix it either :/
Infact I can now no longer boot into recover, it freezes at the HTC logo.
Now that you have S-OFF, go to ROM Manager and reflash the ClockworkMod.
Sent from my Desire HD using Tapatalk
jkoljo said:
Now that you have S-OFF, go to ROM Manager and reflash the ClockworkMod.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
That didn't work, I had to manualy install it in the end. I now have V3.0.0.5 but I can't restore my backup because:
E:Format_volume: no MTD partition "boot"
What does this mean and how do I fix it? I need to get that backup back! It has everything :O
That backup was made with a V3 CWM. But I hear I need V2 to use with froyo? GAHHHHHHHHH.
Got to downgrade CWm now I guess. EURGH!
Rom manager wouldn't downgrade but I tryed upgrading to 3.0.0.6 in a hopeful attempt and appears to be working XD.
Then after alllll this I have to find out how to fix my echoing as it works on the stock rom so must be something i need to do to leedroid. I'm thinking radio change?
so i assume you finally downgraded to a "rooteable" android version... if still need help, send a PM so i will try to help u!
good luck!!
8igdave said:
I am getting so god damn pissed off with this. As I took my battery out for the 100th time I thought to my self mmm this is gonna break if I'm not careful and out pops my volume rocker. Had to bend it to get it back in. Don't evne understand why this is all happening. I did this all fine the first time around.
Firmware is 132.405.6
The rooting isn't the problem, its recovery which is.
Click to expand...
Click to collapse
.... got it, you hace to plug the hd to pc, debbugginng on, (charge only) download the rom manager, reflash the klockwork, and try again
good luck!
Sorry for the long read, this is half rant and half question.
Alright, I got a captivate a long time ago (about a year and 3 months ago), loved it, rooted it and installed cyanogenmod as soon as I got home, changed roms and kernals constantly, did whatever I wanted to do.
About 3 months ago my screen stopped working.. So I take it in and they give me a refurb captivate, looked brand new so I didn't mind. However, when I tried to get into recovery it didn't work, the 3-button-method just wouldn't work at all, period, so I try to get it to work, gets stuck in bootloop.. pretty much every time I try to flash a rom something goes wrong and I get stuck in a bootloop but I can usually get into recovery or download mode because I had CWM.
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
I guess my only option is to usb jig it, but honestly now I'm convinced that the phone is just faulty, I want to run the thing over.
-Pirate said:
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
Click to expand...
Click to collapse
If you would have actually searched you would have known it was a bug in the glitch. There are atleast 40 pages about that.
-Pirate said:
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Click to expand...
Click to collapse
If you flashed ICS you should know it takes 2 flashes for it to work first time. Having a jig around is always a good idea as well.
-Pirate said:
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
Click to expand...
Click to collapse
Stuff doesn't work as intended. Keep in mind everything is still in dev and not all devices are the same. But you should have searched a little more and it would have ran =/
U def don't need a jig. If it's booting it's not bricked. Try removing battery, start Odin, hold down power and down, plug in and put battery in. This should bring u to download mode.
prbassplayer said:
If you would have actually searched you would have known it was a bug in the glitch. There are atleast 40 pages about that.
Click to expand...
Click to collapse
I did start to see a few people with the problem, however many people do not follow up with what fixes their problem, and I did what a few people had said to do.
prbassplayer said:
If you flashed ICS you should know it takes 2 flashes for it to work first time. Having a jig around is always a good idea as well.
Click to expand...
Click to collapse
I should of mentioned that I did flash a few times, 3 total I think, it was getting stuck at boot.
prbassplayer said:
Stuff doesn't work as intended. Keep in mind everything is still in dev and not all devices are the same. But you should have searched a little more and it would have ran =/
Click to expand...
Click to collapse
I understand that **** happens but honestly my old captivate could always get into recover mode and download mode no matter what, it's extremely frustrating that something changed with the newer models. One of my questions was what caused the brick? I did nothing wrong from what I see and it was running perfectly until I tried to restart/boot into recovery.
Oh and mbc663, thanks but download mode doesn't work at all, nor does recovery obviously.
I can't say exactly what you are doing. Best advice I can do Re download your .zips Flash back to stock GB and try again.
-Pirate said:
About 3 months ago my screen stopped working.. So I take it in and they give me a refurb captivate, looked brand new so I didn't mind. However, when I tried to get into recovery it didn't work, the 3-button-method just wouldn't work at all, period, so I try to get it to work, gets stuck in bootloop.. pretty much every time I try to flash a rom something goes wrong and I get stuck in a bootloop but I can usually get into recovery or download mode because I had CWM.
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
I guess my only option is to usb jig it, but honestly now I'm convinced that the phone is just faulty, I want to run the thing over.
Click to expand...
Click to collapse
Last year, I had issues with my original Cap, and got a "new" one. I learned that the bulk of the Caps going out as replacements are referbs. The one I got was a 1008 build, and does not have 3 button recovery. There are minor differences with each and every Cap that's out there. That's why some have issues with ROM's and some don't, some can over clock like crazy, and some can't at all. My guess is you have a 1008 as well, but that really doesn't matter. You just have a different device and as you seem to already have learned.
It sounds like there is more research you need to do. Even though the devices are a bit different, if you are having issues with ROM's loading, then I would say it's more of a procedure issue, than one with your device.
My procedure, is,
Remove SD/Micro SD
Odin1 Click to Stock JF6, and Master Clear(This will erase EVERYTHING)
Root with One-Click Root
Use Sideload Wonder Machine to install ROM Manager, copy update.zip and 3buttonFix to my SD, then reboot into recovery
Once in recovery I install the 3buttonFix, and install my new ROM
For me this has proven to be a very good method versus going from one ROM to another. The Master Clear cleans EVERYTHING off of your SD, so there is no chance for anything to corrupt your new install. Anytime I read a post of a install gone FUBAR, USUALLY a Flash To Stock/Master Clear (FTS/MC) fixes it
Before using Odin 1 Click, check your devices build number!! If it is higher than 1012, I would NOT recommend using 1 click, there is a higher chance of hard brick on the newer devices
Kangi...if you flash a firmware package without bootloaders, you won't have to do the 3 button fix every time. And if you keep a copy of the update.zip on your pc you don't have to even root, let alone bother with side loading ROM manager.
Cezar has a no boots jf6 and after you run that, you can still use master clear in one click.
Sounds like you got one of the refurbs that is missing the SBL. Have you looked at this thread? http://forum.xda-developers.com/showthread.php?t=1129821
I've not had this problem myself but it sounds like that might help. If I remember reading correctly, once this is flashed it should stick as long as you don't flash any other bootloaders on top of it.
Its not missing the sbl. The sbl it has doesn't respond to key combos. Derpa sherpa moment for samsung I guess?
Rofl yeah...if it was missing the sbl it would be fuggin bricked!
studacris said:
Kangi...if you flash a firmware package without bootloaders, you won't have to do the 3 button fix every time. And if you keep a copy of the update.zip on your pc you don't have to even root, let alone bother with side loading ROM manager.
Cezar has a no boots jf6 and after you run that, you can still use master clear in one click.
Click to expand...
Click to collapse
I know, thanks. I'm such a creature of habit, I started doing it like this a bit over a year ago, and has worked flawlessly for me(just jinxed myself!) so I never saw a reason to "fix what aint broke".
I'll take a look at Cezar's thanks!
Yeah, missing SBL was a poor choice of words. My bad.
kangi26 said:
Last year, I had issues with my original Cap, and got a "new" one. I learned that the bulk of the Caps going out as replacements are referbs. The one I got was a 1008 build, and does not have 3 button recovery. There are minor differences with each and every Cap that's out there. That's why some have issues with ROM's and some don't, some can over clock like crazy, and some can't at all. My guess is you have a 1008 as well, but that really doesn't matter. You just have a different device and as you seem to already have learned.
It sounds like there is more research you need to do. Even though the devices are a bit different, if you are having issues with ROM's loading, then I would say it's more of a procedure issue, than one with your device.
My procedure, is,
Remove SD/Micro SD
Odin1 Click to Stock JF6, and Master Clear(This will erase EVERYTHING)
Root with One-Click Root
Use Sideload Wonder Machine to install ROM Manager, copy update.zip and 3buttonFix to my SD, then reboot into recovery
Once in recovery I install the 3buttonFix, and install my new ROM
For me this has proven to be a very good method versus going from one ROM to another. The Master Clear cleans EVERYTHING off of your SD, so there is no chance for anything to corrupt your new install. Anytime I read a post of a install gone FUBAR, USUALLY a Flash To Stock/Master Clear (FTS/MC) fixes it
Before using Odin 1 Click, check your devices build number!! If it is higher than 1012, I would NOT recommend using 1 click, there is a higher chance of hard brick on the newer devices
Click to expand...
Click to collapse
I didn't think anyone else was going to reply to this thread, whoops.
Thank you for helping me, but I'm still having trouble.
Rom manager doesn't show up in Market, Sideload wonder machine tells me [INSTALL FAILED OLDER SDK] with any apk of Rom manager I find.
kangi26 said:
3buttonFix to my SD, then reboot into recovery
Click to expand...
Click to collapse
How do you reboot into recovery when 3buttonfix hasn't been applied yet?
This sucks and is extremely frustrating, I feel like my captivate is just trolling me.
-Pirate said:
I didn't think anyone else was going to reply to this thread, whoops.
Thank you for helping me, but I'm still having trouble.
Rom manager doesn't show up in Market, Sideload wonder machine tells me [INSTALL FAILED OLDER SDK] with any apk of Rom manager I find.
How do you reboot into recovery when 3buttonfix hasn't been applied yet?
This sucks and is extremely frustrating, I feel like my captivate is just trolling me.
Click to expand...
Click to collapse
When I get home later tonight I'll link you everything you'll need. Again, VERY important, what is your build number? If it's 1012 or higher, don't use Odin 1 click
Sent from a autonomous device
kangi26 said:
When I get home later tonight I'll link you everything you'll need. Again, VERY important, what is your build number? If it's 1012 or higher, don't use Odin 1 click
Sent from a autonomous device
Click to expand...
Click to collapse
Ok, finally got it working, I did exactly what you said, I found the rom manager 3.00.002 or whatever and that worked with sideloader, it took some messing around with but I'm running ICS now, thank you so much man, you've helped me so much, and now I can change roms and keep up to date without worrying about constantly soft-bricking.
As for my build number, I'm not sure, the only thing I see under build number in settings is: "IML74k"
-Pirate said:
Ok, finally got it working, I did exactly what you said, I found the rom manager 3.00.002 or whatever and that worked with sideloader, it took some messing around with but I'm running ICS now, thank you so much man, you've helped me so much, and now I can change roms and keep up to date without worrying about constantly soft-bricking.
As for my build number, I'm not sure, the only thing I see under build number in settings is: "IML74k"
Click to expand...
Click to collapse
The build number is actually under your battery, and looks like 10.06, 10.07, 10.08 and so on. It is the production date
Edit** And as a side note, do NOT try to use the 3buttonFix with a GB ROM, it WILL brick your phone in a really bad way. ONLY use it with 2.1 or 2.2
kangi26 said:
The build number is actually under your battery, and looks like 10.06, 10.07, 10.08 and so on. It is the production date
Edit** And as a side note, do NOT try to use the 3buttonFix with a GB ROM, it WILL brick your phone in a really bad way. ONLY use it with 2.1 or 2.2
Click to expand...
Click to collapse
Is it weird that I don't have a build number? It seems I can't post pictures without a few more posts, maybe this will work: deleted
And thanks for the warning on the 3buttonfix, I'm going to have to read more about bootloaders though, I don't understand what you and studacris were talking about earlier in the thread, haha.
-Pirate said:
Is it weird that I don't have a build number? It seems I can't post pictures without a few more posts, maybe this will work: imgurDOTcom/26sXGl.jpg
And thanks for the warning on the 3buttonfix, I'm going to have to read more about bootloaders though, I don't understand what you and studacris were talking about earlier in the thread, haha.
Click to expand...
Click to collapse
I havent seen that before, there doesnt seem to be a build#
Might want to pull that photo, it's not too good having your IMEI number publicly displayed
kangi26 said:
I havent seen that before, there doesnt seem to be a build#
Might want to pull that photo, it's not too good having your IMEI number publicly displayed
Click to expand...
Click to collapse
Maybe because it's a refurb? and whoops didn't think about that.
-Pirate said:
Maybe because it's a refurb? and whoops didn't think about that.
Click to expand...
Click to collapse
I'm not sure why, mine is a referb, and I have a sticker with mine on it. Ooh well, it is what it is
Sent from a autonomous device
Howdy all,
My phone broke, so I'm back on the hero. I forget any and all stuff of how to's on this phone so bear with me. Basically, I'm a noob for the hero now.
So, recently, I followed the Cyanogenmod Full Update wiki guide, rooting it with the rageagainstthecage exploit. However, after my first time, my phone would eventually be so slow that it would seem to freeze. It's just so so so so slow. It's unusable. The lockscreen would come up, and i would touch the lock icon, which would vibrate. I would slide to unlock, but the screen doesn't react. at all. then it would vibrate, indicating an unlock, but the screen doesn't change at all. Occasionally, I'm able to accidentally enter an app, but I cannot read texts, answer calls, or reply to texts. Or do anything else.
Occasionally, I'll get a "app is unresponsive" message, but I can't force close/wait.
Oh, btw, when this happens, I can't get into my recovery (CWM 3.0.0.5). Also, I don't see the boot animation.
I have done an RUU stock reset, which fixed it once. The problem occurred again while on CM7, and I did another RUU reset, but the problem is now consistent throughout the stock sense. Omigawd what do i do?
Since I am now on stock that has usb debugging disabled, I can no longer access adb.
I am currently on absolute stock (fresh-out-of-the-box like), not rooted, and have S-OFF.
I am fairly well versed in fastboot and adb commands. When I try to access the recovery, I am sent to a black screen. When I plug in while in recovery and do "adb devices," I get my model number with the message "offline."
I AM OUT OF IDEAS! Someone. Please helpppp.
Thank you for reading. Thank you for helping.
Try a re-root with regaws rooter (the old version if you can get it) i swear by it. or Z4 root. once you have reestablished root, get Rom manager and flash the 2.4.0.7 recovery. then in rom manager go to downloads and get the cyanogen mod download of your choice( myself i prefer 7.0.3) and flash. you should be good to go from there.
as far as your adb it looks like your pc either isnt recocnizing your phone or you dont have the proper drivers installed.
Bout all i can tell ya ,one noob to another,,,
BTW, if you want to start completly from scratch, since your s-off,you can get a HERCIMG.img i think in the development sectin of this forum that is flashable from fastboot,,,try that ,,,Later man and good luck
Luckily you are S-Off. Can you put a HERCIMG.zip on the root of your sd card with a recovery (even CWM 2.5.0.7 will do) and then maybe try downloading another rom. Maybe you have a bad download. I am a big fan of Jaybob's TeamHeroc Rom which is a great CM7ish type of rom. Make sure that you format boot, cache, data, and system (I do it 3 times for each to make sure that it is really wiped) before you flash whatever rom you choose. You might have some leftover stuff that is causing some issues. Just wiping data and cache might not be enough. Here is a HERCIMG with a 4.0.1.4 recovery that you can load from H-Boot. I'm pretty sure that it's the Orange Recovery that I use.
hugabu said:
Howdy all,
My phone broke, so I'm back on the hero. I forget any and all stuff of how to's on this phone so bear with me. Basically, I'm a noob for the hero now.
So, recently, I followed the Cyanogenmod Full Update wiki guide, rooting it with the rageagainstthecage exploit. However, after my first time, my phone would eventually be so slow that it would seem to freeze. It's just so so so so slow. It's unusable. The lockscreen would come up, and i would touch the lock icon, which would vibrate. I would slide to unlock, but the screen doesn't react. at all. then it would vibrate, indicating an unlock, but the screen doesn't change at all. Occasionally, I'm able to accidentally enter an app, but I cannot read texts, answer calls, or reply to texts. Or do anything else.
Occasionally, I'll get a "app is unresponsive" message, but I can't force close/wait.
Oh, btw, when this happens, I can't get into my recovery (CWM 3.0.0.5). Also, I don't see the boot animation.
I have done an RUU stock reset, which fixed it once. The problem occurred again while on CM7, and I did another RUU reset, but the problem is now consistent throughout the stock sense. Omigawd what do i do?
Since I am now on stock that has usb debugging disabled, I can no longer access adb.
I am currently on absolute stock (fresh-out-of-the-box like), not rooted, and have S-OFF.
I am fairly well versed in fastboot and adb commands. When I try to access the recovery, I am sent to a black screen. When I plug in while in recovery and do "adb devices," I get my model number with the message "offline."
I AM OUT OF IDEAS! Someone. Please helpppp.
Thank you for reading. Thank you for helping.
Click to expand...
Click to collapse
I like Regaw's for rooting too. I used it the last time I did an RUU.
Isnt that what I said just before you ??? Lol
BTW Pilot, Where have you been? One of the most active members of the Heroc forum and all of a sudden ,poof, gone like a fart in the wind ! And then as if by magic, Poof, your back.I knew youd return, they always always return to the ol reliable Heroc. Good to see you around again bud, Later man,,,
Sent from my HERO200 using xda premium
hey guys just got back from vacation. Thanks for all your feedback. I switched phones to a temporary one now. I don't really feel like switching back to the hero cuz it costs money to activate phones. Also, I talked to an app developer about my problems. He told me that 1. the phone is way to old to be running gingerbread. Some nasty software probably carried over from my last flash onto the stock RUU flash. and that 2. whenever the problem occurs, I should let the battery drain before I do anything. Turns out, whenever the problem happens nowadays, I just let the battery drain and its all fixed. OKAY WTF. But all smiles now. Its my ipod-touch-like device now. I used regaws root.
THANKS GUYS SO MUCH.
Ok, so I ran into a VERY weird issue and was wondering if anyone else has experienced this or has a better solution then what I found.
My Nexus7 was running stock JRO03D. I had it rooted, using the Motley kernel with CWM Recovery - but outside of that, everything else was pretty stock. Anyway, I decided to upgrade to the 4.1.2 image. I pulled the one it downloaded automatically out of /cache and looked at the updater-script to see what it did. I noticed it replaced a lot, including the boot image, so I figured it would be better just to let it do everything and revert my custom stuff later. So I replaced the kernel with the stock JRO03D kernel and, using CWM, flashed the upgrade. Everything seemed to go perfect and it completed the upgrade. Prior to rebooting it, I also flashed the "unofficial" motley 4.1.2 kernel posted on XDA. I rebooted the device, and CWM warned me that 'su' needed to be fixed (how nice!) and made it suid again. It rebooted and after android "updated", everything was up and running. I confirmed in settings that it was on 4.1.2 with the custom kernel. SU was suid root as well. Perfect!
Not quite.
I decided to try rebooting into recovery to make sure CWM was still there, or flash it back if it wasn't. I opened up a terminal emulator, removed the new recovery-recovery image in /system, and did "reboot recovery". The Nexus7 rebooted, but rebooted right back into normal operation. Very weird. So I hooked it up to my computer, figuring CWM was gone, and tried to fastboot flash it back. Fastboot said it did, but I still wasn't able to reboot into recovery. I tried three different versions of CWM and even TWRP, but no dice. Every time I tried rebooting into recovery (using terminal emulator, adb shell or bootloader method) it just went right back into the normal boot process.
I spoke to some people on IRC who recommended reflashing the stock image from Google (without wiping user data). I reflashed the bootloader and then did a fastboot update <stock image>, and it said it replaced boot, recovery, system, etc. It rebooted automatically, and I tried going into stock recovery. That still did NOT work. Instead, I got a very sick looking android guy who was lying down with a red triangle with an exclamation point over him. I was a bit worried and upset at this point. I tried reflashing CWM/TWRP again, but nothing. When I did this, I no longer got the unhappy android image, but it just booted up normally.
I decided to try and doing a more thorough wipe, using fastboot to wipe cache/boot/recovery/system manually. Then I reflashed the bootloader and stock image. Still no recovery (stock or custom).
As you can imagine, I was getting even more concerned now. Especially since I was no without root and no way to get it back (since I couldn't get into recovery to flash the zip for it).
I tried every other thing I could think of to flash recovery back, but nothing worked. It wouldn't load at all.
Finally, I was about to do a complete factory reset and wipe/reflash of everything, but one last thought crossed my mind. I found the older (JRO03D) bootloader and flashed that. Reloaded bootloader and selected "Recovery". Voila, I was in TWRP Recovery Mode! (which was the last one I tried installing). I was able to reinstall my SU.zip and get everything back up and running.
SO, long story short, I'm now on 4.1.2, running the newer unofficial motley kernel and have su back. But I'm also stuck on the older 3.34 bootloader. If I try upgrading it back to 3.41, I won't be able to get into recovery.
Has this happened to anyone else? It doesn't seem like it. Is there a HW issue with my device causing this problem? I can't believe it's software related since I tried two different copies of the 3.41 image. Does anyone have any other suggestions on how I can upgrade the bootloader while keeping the ability to get into recovery mode?
Also, while everything *seems* to be working OK using 3.34, do you think it will cause other problems since I'm using 4.1.2?
Thanks.
*MOD EDIT* please don't quote the entire OP
Thanks for the bootloader info. I was in the same boat, and once I found your post, I went back to JRO03D and my recovery has returned.
Again, thanks, you F'n rule!!!
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
MetalWych said:
Thanks for the bootloader info. I was in the same boat, and once I found your post, I went back to JRO03D and my recovery has returned.
Again, thanks, you F'n rule!!!
Click to expand...
Click to collapse
No problem. I'm glad to hear that my solution above helped someone else, and also that I'm not the only one experiencing the problem. I assume you mean you only went back to the JRO03D bootloader and not the whole image, right?
What I'm most concerned about is that it seems like my N7 (and possibly yours as well) is defective. I'm not an uber-expert on Android, but I'm fairly knowledgeable. With a stock system, outside of userdata, that I reflashed multiple times from multiple sources, to have any type of recovery (stock or custom) not work is a bit upsetting. Since it works fine on the older bootloader, it definitely seems to be an issue with that. But since most people do not have the same issue, the only variable I can see being the difference is hardware.
Metallice said:
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It looked more like a warning symbol that something went very wrong then a stock recovery screen.
I've gone into stock recovery on other Android devices before, and it looked similar to CWM. There was a menu that allowed you to install "authorized" update.zip files, factory reset the device, etc. There was no menu here, just a very pissed off and sick looking android guy .
I believe I am having the same issue. Would you mind linking me to the bootloader which worked for you? Tried searching but couldn't find it. Thanks, and great post!
Sent from my SCH-I535 using xda premium
There's a big thread around here somewhere with people having the same problem as the op. Unfortunately, staying with the 3.34 bootloader is the only 'fix' I've read about. I still can't figure out why some people run into this problem and some don't. I used twrp to flash the update when it became available, and twrp continued to work afterwards.
spongers said:
I believe I am having the same issue. Would you mind linking me to the bootloader which worked for you? Tried searching but couldn't find it. Thanks, and great post!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
It took me a long time to find the old full JRO03D update, since Google only has the latest one on their page. I uploaded the bootloader out of it and you can download it here:
http://core.routed.com/bootloader-grouper-3.34.img
Reboot the Nexus7 into bootloader mode and run:
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
and then you should be able to flash recovery and get into it.
Metallice said:
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The android with the red triangle does not sound like the stock recovery, it is THE stock recovery.
Under JB 4.1.2 you do not need anymore to connect the N7 to a computer - like it had to be under JB 4.1.1 - to access the bootloader and then the recovery.
Now, pressing volume + power brings the bootloader , the up volume, one press, and then power press put the N7 to recovery. The recovery is the android with the red triangle. To enter in the recovery menu pressing power + volume up brings the menu with the following options:
i) reboot system now,
ii) apply update from ADB,
iii) wipe data/factory reset,
iiii)wipe cache partition.
Concerning specifically the OTA update for an unlock and root N7 there should be no problem during the process using stock recovery or CWM 6.0.1.0 as long as OTA Rootkeeper is set, before the installation, in order to keep root.
the fact that you were able to do volume down + power button into bootloader, then select recovery, makes me know its working. and the android guy on his back is the stock recovery... so everything is working fine. you said you flashed motley kernel, it may have something to do with that, and a few other things. you really need to understand how the N7 works, and what it will do if you do not do certain things.
what u should try is, fastboot flash recovery, then fastboot boot recovery
flash a different rom, i prefer Paul's Jr8 as its close to stock with nice little tweaks and see if your issue continues.
at the end of everything, i honestly find this more user error then device related. not everyone understands what the N7 is doing, and why.
smirkis said:
the fact that you were able to do volume down + power button into bootloader, then select recovery, makes me know its working. and the android guy on his back is the stock recovery... so everything is working fine. you said you flashed motley kernel, it may have something to do with that, and a few other things. you really need to understand how the N7 works, and what it will do if you do not do certain things.
what u should try is, fastboot flash recovery, then fastboot boot recovery
flash a different rom, i prefer Paul's Jr8 as its close to stock with nice little tweaks and see if your issue continues.
at the end of everything, i honestly find this more user error then device related. not everyone understands what the N7 is doing, and why.
Click to expand...
Click to collapse
Smirkis, my initial thought was that something went wrong in the upgrade process, possibly with the kernel like you suggested, so, as I mentioned in the OP, I flashed everything back to stock 4.1.2. I used flashboot to manually erase boot, cache, recovery and system. I then reinstalled the bootloader from Google's update tarball. I then used fastboot to update to image-nakasi-jzo54k.zip. At this point, outside of wiping sdcard, everything was stock 4.1.2.
While I will admit that I didn't realize that the dead-looking android meant stock recovery (and that's good to hear), subsequently flashing a custom recovery (CWM or TWRP) would continually fail to load it. In fact, I couldn't even boot into the recovery manually without flashing it. While using 100% stock, I attempted to flash three different versions of CWM and one version of TWRP. It claimed it updated, but I was not able to get back into recovery - either through bootloader, adb or "reboot recovery".
I know it's easy for people to always jump to the "user error" answer, but I fail to see how that is the case here. Based on your response, I don't think you actually read what I did and just jumped to the wrong conclusion, especially since I already tried your recommendation and much more. I am not running any custom ROM - everything was always stock outside of recovery, root and kernel. If you can explain your reasoning for thinking I did something wrong in all of my numerous attempts to get it working, I would appreciate it since maybe that would provide a solution. While I did attempt to use a custom kernel originally, that obviously isn't the issue if going back to stock didn't fix it.
Additionally, reverting back to the older bootloader magically fixed everything, while all other attempts failed. Subsequently reinstalling the custom kernel didn't break anything either. So if it wasn't the bootloader and something else was broken, I would assume it would be broken in both versions of the bootloader. The fact that this problem is affecting others, granted a small number, and the same solution works for them, leads me to believe that there is either a bug in the bootloader affecting some N7s or some rare HW defect causing a few of us problems.
There is a conversation about the new android update the boot-loader update and A Power management chip on the nexus 7.. It seems this chip is being changed out. The new chip functions the same as they have been using but Its not compatible with the old boot-loader . The above is the reason for the boot-loader change.. Google is aware of the troubles everyone in this thread is having . I would be looking for a new very tiny update in the near days. Just a guess im wondering if the truth is they are gearing up for the 3g version of nexus .maybe the pm chip being changed has a issue with the added radios. They did say ITS NOT A Chip upgrade but will not say why they are making the switch .
sorry i do not have a link . but everyone knows how to get to google groups ..
Happy Reading..
I just got another N7 in the mail today, gonna unlock n root it when i get off work. hopefully i end up in your situation so i can attempt to assist in resolving this. why the old bootloader works for you, and never worked for the rest of the world is beyond me. they updated it for a reason lol, i even called google the first week i got mine in july to tell them about the bootloader and they "said" they would forward that info to the development team. it took almost 3 months for them to fix it.
if the old one works for you, then use the old one. the only difference really is the fact that reboot to recovery thru bootloader actually works. if it works for you, don't upgrade.
mine on the other hand, couldn't get into recovery via bootloader. i was dieing for that upgrade, and when it came i was beyond relieved. i did a RMA this week because my first one had screen lift since the 2nd day i owned it lol, so i'll report back when i get home in an hour or so on my results.
smirkis said:
I just got another N7 in the mail today, gonna unlock n root it when i get off work. hopefully i end up in your situation so i can attempt to assist in resolving this. why the old bootloader works for you, and never worked for the rest of the world is beyond me. they updated it for a reason lol, i even called google the first week i got mine in july to tell them about the bootloader and they "said" they would forward that info to the development team. it took almost 3 months for them to fix it.
if the old one works for you, then use the old one. the only difference really is the fact that reboot to recovery thru bootloader actually works. if it works for you, don't upgrade.
mine on the other hand, couldn't get into recovery via bootloader. i was dieing for that upgrade, and when it came i was beyond relieved. i did a RMA this week because my first one had screen lift since the 2nd day i owned it lol, so i'll report back when i get home in an hour or so on my results.
Click to expand...
Click to collapse
Just to clarify, going from bootloader->recovery never worked for me either. Whenever I needed to get into recovery mode, I just opened up a terminal, su'd to root and then ran "reboot recovery", or occasionally doing it via adb. However, those methods always worked for me until I upgraded to the latest bootloader. Then, no custom recoveries would load via any method.
My Nexus7 was first generation. I actually picked it up in Sams Club the day before they were officially released. So if Google made any HW changes in the different revisions, that might explain the difference in results on 4.1.2. Though I imagine most people on XDA also picked theirs up out of the first batch, so I don't think that could be the case. What seems more likely is that there are minor hardware differences that are causing some people's to fail with the 3.41 bootloader, while most don't have that issue. It will be interesting to see if you experience the same issue on your new one though.
gunner1937 said:
Concerning specifically the OTA update for an unlock and root N7 there should be no problem during the process using stock recovery or CWM 6.0.1.0 as long as OTA Rootkeeper is set, before the installation, in order to keep root.
Click to expand...
Click to collapse
It didn't worked for me. I've tried Rootkeeper apk, but it was useless.
This was driving me crazy until I've found this topic! I've tried resetting it to original settings, using rootkeeper and traditional methods, nothing, zero!
At last, phonic saved my life, and finally I a could root my Nexus 7!
I never responded but my RMA worked as it should. but the issue has been resolved with recovery updates from the developers. the rest of the world who had issues should be good to go. I ended up selling my 16gb unit and got a 32 and it works as it should as well. are we all happy campers now?
Sent from my Nexus 7 using xda premium
I've had similar experiences where the way certain kernels install zips are packaged, the wipe custom recoveries at install. In that situation, I've never wiped anything from system, but rebooted into bootloader and fastboot boot recovery "recovery.img". Then from there install the recovery.zip. The worst is when this happens when you get flash happy away from home and the kernel doesn't work. No way to fix without a comp w/SDK. Glad you're back up and running.
(I cannot be held responsible if the aforementioned damages your device; do the research and own the process.)
I am so glad to have found this thread. This problem was beginning to drive me nuts.