Database Info

Ok, I give up --- cant get out of G1 bootie, skateboards & CM/JF recovery -- help

G1 DREAM (really is a dream, right now, a little bad one a little embarrassing)
been 5 mos since I took root via Cyanogenmod's latest G1 stable and last theme was PHRASh Then I thought about checking out
some other themes and clockwork orange caught my eye... Orange is my favorite color, so wehen I saw there was some Orange theme I must've had a dare encounter with myself-- i recall actually installing the Orange theme..... when i asked the phone to flash the theme, it went into permanent G1. Gave it about 12 minutes. Rebooted into recovery (home menu power) and then did what I think got me in deep droid doo doo -- I attempted to restore to my last backup whch was the day before (and ironically the BEST backup i ever made I had it all humming so nice and fast) Guys -- instead of hitting restore to last backup... I actually hit nandroid backup. I know. That was a really bad day and its been a worse 50 hours. I know -- and Ive learned -- OK?
Since that time.... 50ish hours Ive lost track of what Ive done, but its a potpourri
bootloader is dev spl skateboarding, recovery is Cyanogenmod JesusFreke 1.4 recovery.
DREAM DREA100 PVT 320
HSPL10.95.3000
CPLD-4
RADIO 2,22.19.361
OCT 29 2008
SERIAL0 -- (fastboot i have fastboot as well)
at first flash of bootloader it says "NO IMAGE FOUND!"
If I press Home when it restarts in perpetual cyclical hell I get into CMJF recovery. I have executed every single option numerous times -- and have not been able to successfully flash anything else -- and now I dont know WHAT to flash. I even tried to go back to root!
If I dont press Home or Camera, I get this....
the awful permanent G1 screen. Forever and ever.
I have Wiped backed up, tried to get update.zip and just about ANYTHING into my sdcard but I dont think they have been successful installations to flash. I am not ADB enabled yet. Surely someone knows what this is all about and I am willing to take a flame for posting in the wrong forum if I can get something out of this, I will pitch in later and help y'all keep these forums in workin' order!
every optioon on the recovery screen which is recovery CM and JF 4.2
When I try to load files according to the instructions in xda and cm i cannot get it in fast enough on the g1 running on the frozen G1 screen because I dont known the time of mount the SDCARD has and when it begins (I know it opens for a while and then closes)
So i got droidexplorer and its almost impossible to get the file in there. I can get it in, and see it, and reboot the phone (and computer)( restore usb connection and I see the update.zip on the sdcard. Then I unmount the phone and reflash and it says something about not being able to find the file.
Whats next? Please dont assume I know what I am doing, I am sure you can tell -- but I am really good at following instructions!

Hello anyone?
I have been up all night trying to fix this phone and i am still not able to do so. I
I cannot get into recovery anymore ------
i am stuck on the hardspl and I have found fastboot again. But I cannot use frastboot if I cannot get any commands into it. Anyone?

ok i get it -
thanks for the help guys! I now have my phone working at a blitzing pace and i am leaving it alone for now. I dare myself to leave it unchanged for a week. Thanks mostly to one of the Dudes on Cyanogenmod.com -- who helped me piece together the missing parts.
Actually -- let me summarize even if only I am reading this
Androids levels of defenses are 1. HardSPL 2. Recovery and 3. normalcy. Lose normalcy (Ok, a beauty of a ROM) you have recovery to get the ROM back -- but the trick is -- can you get the necessary IMG file on your SDcard to update.zip with? Can you figure out ADB and push the update.zip? Can you figure out Fastboot and what it REALLY does and what you can and cannot do with FB? If you can do any of these or FB with ADB, then you have a good chance. Just dont lose the HardSPL. If you give up after frustration and while grinding your teeth waving a white flag, flash the DREAIMG.img file, then you have given up root and FB. But at least you are at RC29, the level where the froot can be found. It is weird hanging out in Android 1.0 lemme tell ya. Feels so 1980'ish with bellbottoms in late decline.
But now its android time at CM with Phrash.
Later

[Q] How do I get out of HBOOT on Evo 4G?

Hey all, huge fan of the site! I've seem to put myself into a situation, in an act of impatience,
-I simply copied PC36IMG.zip to the root of my sdcard.
-Then I rebooted the phone into HBOOT, and it did its thing.
But now it just keeps rebooting HBOOT. Have I bricked my phone? I would greatly appreciate the help. Thanks so much guys.

I am also in HBOOT
Had and error when flashing Cyn ROM through ROM Manager. I am now unable to use the recovery. Basically just stuck

Almost bricked
kecibuor said:
Had and error when flashing Cyn ROM through ROM Manager. I am now unable to use the recovery. Basically just stuck
Click to expand...
Click to collapse
Yeah. ROM Manager and ROM Manager Premium just hosed my phone. Luckily I'm geeky enough to have done the Factory Reset on the phone. I still couldn't book into HTC Sense. Just the HBOOT menu. So I surfed around, found the Stock PC32img.zip and flashed it twice (1st time Failed PU error). Then it finally booted.
Now it's like a brand new phone with the S-OFF still intacted. Now I'm going to reflash the unrEVOked 3.21 and get that back up. Then I will copy over my saved Nandroid Backups and restore the phone to the beginning of Oct (my last backup). Then finish adding in all the extras since. Oh... and also getting a refund on ROM Manager Premium since I'm still in the 24 hour refund period. Screw that app! I followed the instructions perfectly and BAM! Almost bricked phone.

[Q] Very, very long boot time after successful root/CM7 install.

I didn't post this in the CM7 thread because I believe my problem was a glitch during rooting, not CM7 which seems to work fine.
I recently dropped my Insight 4G which had been rooted and was running the Revolution ROMs and cracked the screen. I purchased a replacement phone, which arrived with the Gingerbread ROM from AT&T.
I decided to try CM7 this time and followed the instruction on wiki.cyanogenmod.com/wiki/HTC_Ace to the letter on rooting, installing clockworkmod, and installing the CM7 roms. Everything worked perfectly with one exception.
Now the phone takes > 10 mins (closer to 20 actually) to boot every time it reboots. I have tried restoring a nandroid backup of the Revolution ROMS from my original phone and everything works fine, but reboot is still very, very long. Restored CM7 from nandroid backup and tried to install RUU file to restore the phone to AT&T, but the software times out due to the extremely long boot time. Everything seems fine on the phone except for the boot time and I don't know what to do next.
After reading a lot of posts it appears that the instructions I followed have a similar effect to using the outdated Ace Hack Kit here. (Wish I'd used the new one). I am well and truly "Jammed Up"
Anyone have a possible fix? I am happy to do whatever it takes... not worried about data.

tricotec said:
I didn't post this in the CM7 thread because I believe my problem was a glitch during rooting, not CM7 which seems to work fine.
I recently dropped my Insight 4G which had been rooted and was running the Revolution ROMs and cracked the screen. I purchased a replacement phone, which arrived with the Gingerbread ROM from AT&T.
I decided to try CM7 this time and followed the instruction on wiki.cyanogenmod.com/wiki/HTC_Ace to the letter on rooting, installing clockworkmod, and installing the CM7 roms. Everything worked perfectly with one exception.
Now the phone takes > 10 mins (closer to 20 actually) to boot every time it reboots. I have tried restoring a nandroid backup of the Revolution ROMS from my original phone and everything works fine, but reboot is still very, very long. Restored CM7 from nandroid backup and tried to install RUU file to restore the phone to AT&T, but the software times out due to the extremely long boot time. Everything seems fine on the phone except for the boot time and I don't know what to do next.
After reading a lot of posts it appears that the instructions I followed have a similar effect to using the outdated Ace Hack Kit here. (Wish I'd used the new one). I am well and truly "Jammed Up"
Anyone have a possible fix? I am happy to do whatever it takes... not worried about data.
Click to expand...
Click to collapse
What I would do is return to a full stock. Then run the hack kit. But that is just me as I have never donebit with the CM wiki instructions

This is a common issue with the latest batch of Inspires (post Aug, 2011 MFG). The hardware is different and not compatible with any hboot except the one that ships with the GB RUU. If you downgraded as per the CM wiki, then you necessarilly installed an older hboot and this is the root cause of your problem.
You can easily replace the hboot on an S-OFF Inspire once it finally does boot by simply writing the later hboot image to the hboot partition (partition 18). There's instructions here:
http://paste.pocoo.org/show/495273/
You can jump into the IRC channel if you need some one-on-one help:
http://webchat.freenode.net/?channels=#liberatedAria

Ok, after many hours of fiddling I finally got it back.
I used the hack kit to re-install the stock RUU using the alternate (hboot) method. It took a LONG time, but was successful. I then used the hack kit to re-root the phone and installed CM7 nightlies. The ace hack kit is a wonderful tool, and I thank the author for making it.

Gene Poole said:
This is a common issue with the latest batch of Inspires (post Aug, 2011 MFG). The hardware is different
Click to expand...
Click to collapse
Hey Gene so what your saying is all Inspire batches post Aug, 2011 must be rooted using the current acehack kit only right?
And older methods of rooting will cause intermittent booting?
Crazy Food For Thought....

jadeus0831 said:
Hey Gene so what your saying is all Inspire batches post Aug, 2011 must be rooted using the current acehack kit only right?
And older methods of rooting will cause intermittent booting?
Crazy Food For Thought....
Click to expand...
Click to collapse
That is correct. The new AHK uses an HTC signed interim firmware patch put out for the DHD which has only a boot.img, radio.img and recovery.img. Fortunately, the radio and boot images are ones that are compatible with gfree and the S-OFF routines can be run without disturbing the rest of the firmware (hboot, system and data mainly), but unfortunately, the kernel is not compatible with the Inspire's graphics hardware so the process literally runs in the dark, and because of the GB changes, it must run in two stages involving both adb and fastboot. USB issues rampant among PCs (so many PC programs assume they are the only program you're ever going to run and so hijack the USB bus thinking you're never going to plug in any other device but theirs) so it is very important that both adb and fastboot drivers can run unimpeded. Occasionally a situation arises where adb runs OK, but fastboot fails and this leave the device in an intermediate state which is not in itself bad, but because there is a blank screen, users freak out and do everything but the right thing (usually involving a "wipe" from hboot) which really screws things up.

Hi Tricotec.
Please, could you describe the steps for doing it. I have the same problem.
Thanks.

nlennis said:
Hi Tricotec.
Please, could you describe the steps for doing it. I have the same problem.
Thanks.
Click to expand...
Click to collapse
i also need those steps.
i tried with ruu but white rebooting bootloader it takes around 10 minutes due to which connection time out occurs b/w phone and wire thus ruu is not installing properly, is there any way we can edit ruu exe file to wait for accepting connect for 10 minutes or so
or please tell other steps

sandeep88822 said:
i also need those steps.
i tried with ruu but white rebooting bootloader it takes around 10 minutes due to which connection time out occurs b/w phone and wire thus ruu is not installing properly, is there any way we can edit ruu exe file to wait for accepting connect for 10 minutes or so
or please tell other steps
Click to expand...
Click to collapse
Nice!! you messed the bootloader for not reading all the warnings. The only fix for the issue is this one:
http://tau.shadowchild.nl/attn1/?p=188

glevitan said:
Nice!! you messed the bootloader for not reading all the warnings. The only fix for the issue is this one:
http://tau.shadowchild.nl/attn1/?p=188
Click to expand...
Click to collapse
i did not did this, i hv gingerbread 2.47 ruu, and i am aware not to downgrade it
its done by my ebay friend, lol he ha sonly that older ruu and he updated 100's of inspire with that, its the first time he got a newer inspire
anyways thanks a lot xda rocks

[Q] Strange thing happened Whilst Rooting Desire

Hi, ive just tried s-off and rooting my HTC desire so that I can flash custom ROM's, this is my first time doing this ever and ive been studying it for weeks, I cant say I was calm about doing it, in fact I was bricking myself all the way through, however it seems to have gone well other than one slight thing.
After careful study I decided to go with a video and step-by-step insturctions on the unlockr site, including links to all the required files.
I have the Revo Stock hboot now and also have clockworkmod on my phone, I followed the root instructions to the letter as well as follow the video, however decided to use clockworkmod first to make a backup and restore image to my sdcard first incase anything went wrong, I then installed the superuser.zip file, it said this all went fine and installed successfully and enjoy, after a reboot of the phone, I have no superuser in the apps menu ?
Tried installing it again, once again it said successful and enjoy, but still no superuser in the apps menu ?
Im also new to these forums and wasnt sure if this was the right place to post this, any help would be greatly appreciated.

For S-OFF and root I used Rovolutionary.
And after that I changed partition table from stock hboot to cm7r2 using Alpharev.
Flashing custom rom hundreds times and I don't have any problem.
I suggest following: reflash and back to default stock froyo and try again.

[Q] Soft bricked my phone - please help!

Hi,
I just bought a HTC One S ville - great phone, but wanted to try MIUI.
I got S-OFF, had rooted it using the standard guide and had
clockwork-touch-5.8.3.1 for recovery.
I flashed MIUI but during load, it would hang - the same with Cyanogenmod 10, even though
I followed guides.
I had a nandroid and could revert, but HBOOT i tried "clear storage", and then must trouble started.
Now I couldn't mount SD card in recovery, and I couldn't boot into MIUI.
I followed this thread to gain access to the SD Card:
http://forum.xda-developers.com/showthread.php?t=1630459
But that didn't work since I can't reflash clockwork-touch-5.8.3.1 since I get remote: signature verify fail - maybe because
it's RELOCKED (?) - otherwise I might have been able to mount, butno luck.
As a last resort, I tried RUU, but gets connection error 170 on two PCs running Windows 7 - tried 5-6 times.
So, after 4 hours I'm fairly sad, I have no idea as what to do a part from retrying RUU. I had a Legend once, and it took me 20-30
tries to get RUU working on Windows 7.
Any help would be greatly appreciated since I'm about to give up for now ;(

I quick follow up - I resolved the problem by installing HTC Sync which I didn't have installed...
Hope this can help others.
Regards,
Fred

What hboot and carrier are you on, if not unlocked. Probably running the wrong ruu, or missing the drivers.