Related
I am completely stuck as of now, tried everything! No idea what else I could try. I basically can install any rom just fine, Dwang 1.12 works fine, Cyanogen Mod 4.2.5 works fine too. I am not able to install the latest ones by either though, what could be the issue?
I have rooted MyTouch 3g.
What do you have on your phone right now, and what methods have you tried? What have your steps been?
I have 2 MyTouch 3g phones actually, one is my roomie's and I can install dwang's 1.13 just fine on it, weird .
For dwangs:
Backup
Wipe
Install
Reboot and get stuck on the MT3G boot screen
For Cyanogens:
Backup
Wipe
Install rooted Base
Install Cyanogens
Reboot and get stuck at MT3G boot screen.
It is my understanding that Dwang's latest is based off Cyanogen's 4.2.6, thus I can see why both of them won't work. But why?
I am on Cyanogen's 1.4 recovery tools, I've had Amon RA 1.3.2, as well as RA 1.4.
HBOOT: 1.33.0006 (SAPP30000)
Radio: 2.22.19.26I
anybody?
afive720 said:
anybody?
Click to expand...
Click to collapse
Sorry i can't help, but just to add on... I'm having almost the same issue, but with a G1. Although i can install any of Dwang's versions, including 1.13, but as far as cyanogen goes, 4.2.5 works great, but 4.2.6 and 4.2.7.1 i get stuck at the g1 logo when trying to flash. If anyone can help my set up is
SPL 1.33.0006
Radio 2.22.19.26I
Amon_RA recovery-RA-dream-v1.2.3.img
have you both done thorough wipes through the console?
Are you flashing the signed developer zip file before trying to flash the rom itself?
The process should be...
Wipe
flash signed dream developer zip
NO REBOOT
flash the rom zip on top of the previous zip
Reboot
you can find links to the signed dream dev zip here
http://forum.xda-developers.com/showthread.php?t=593626
Since the first guy has a mt3g, you'll need to find that primary file. The dream one wont do it for you.
check cyanogen's wiki over at cyanogenmod.com
I've had a similar problem. I follow all the instructions correctly, but Dwang's 1.13 works and CM doesn't. For CM I did everything, wiped, flashed 1.6, flashed CM, rebooted, and then it would go back into Recovery for some reason. I'd reboot again and it'd hang on the Rogers screen for me. I couldn't fix it so I wiped, flashed Dwang's, and his worked fine. No clue why CM wouldn't work for me since that's the ROM I actually wanted.
DiSTroy3d said:
For CM I did everything, wiped, flashed 1.6, flashed CM, rebooted, and then it would go back into Recovery for some reason. I'd reboot again and it'd hang on the Rogers screen for me.
Click to expand...
Click to collapse
Yes the first reboot writes the radio files. The second boot writes the cache.
You will have to hit reboot when the cache writing stops. (reboot will become an option in the recovery)
This is the first boot of a brand new OS as far as your phone is concerned and it will take a few minutes. The boot process will take a while. The phone is writing and moving the entire android OS.
I have had mine hang for about 10 minutes before. Sometimes it is 5 minutes.
Mine normally hangs for about 2-5 in the G1 boot screen and another 3-5 in the cyanogen logo.
So I was running OpenEclair v1.1.1, and since putting eclair on it, I've been unable to flash to any other rom. It goes through the wipe/install process, but when the device reboots I just get the rogers screen forever. I can then go back into recovery and re-flash OpenEclair to get it working again. I just got through all that hassle with rogers and made it out with my data and my root, so I was now attempting to fix this issue, and figured it couldn't hurt to upgrade my radio and try out amon ra's 1.5.2R image.
Unfortunately, I downgraded the SPL to 1.33.0009 right after trying to flash another ROM which didn't work, and performed the downgrade before I put a working ROM back on it (to use flashrec to get to amenra's), so at present I can only get into the SPL. My cyanogen1.4 recovery seems to be gone as I just get the original triangle ! logo (no menu or anything) when trying to start up in recovery mode.
Now what did I do, and how far back do I need to dig through tutorials to get back to a working rooted ROM? I'm not really sure what point I'm actually at, whether I still have root or not, or where to start.
Ninzoku said:
So I was running OpenEclair v1.1.1, and since putting eclair on it, I've been unable to flash to any other rom. It goes through the wipe/install process, but when the device reboots I just get the rogers screen forever. I can then go back into recovery and re-flash OpenEclair to get it working again. I just got through all that hassle with rogers and made it out with my data and my root, so I was now attempting to fix this issue, and figured it couldn't hurt to upgrade my radio and try out amon ra's 1.5.2R image.
Unfortunately, I downgraded the SPL to 1.33.0009 right after trying to flash another ROM which didn't work, and performed the downgrade before I put a working ROM back on it (to use flashrec to get to amenra's), so at present I can only get into the SPL. My cyanogen1.4 recovery seems to be gone as I just get the original triangle ! logo (no menu or anything) when trying to start up in recovery mode.
Now what did I do, and how far back do I need to dig through tutorials to get back to a working rooted ROM? I'm not really sure what point I'm actually at, whether I still have root or not, or where to start.
Click to expand...
Click to collapse
Have you got a fastboot mode you can boot into? At least then you could fastboot boot a (non-peristent) recovery image to let you then restore from a nandroid backup...assuming you have some good backups either on the phone or on a PC that can be copied to the phone.
I should note you haven't said what kind of phone you have (G1 or Magic) or really provided anything resembling a complete set of relevant information about your phone and its current state. So it's hard to help.....even if this was the right forum...and it isn't.
Try formatting or using a new memory card.
I'm using a rogers Dream, I have a 2gb SD card with 32MB linux swap and 500MB ext3
HAD 1.33.2005 SPL, 1.4 cyanogen recovery image.
Now I have 1.33.0090, can't get into recovery.
Trying to boot normally brings me to a rogers screen.
I CAN get into fastboot, can I put cyanogen's recovery back on?
Sorry if this is the wrong forum, where should I have posted?
Also, I don't know what information IS relevant to this, so please bear with my noobness.
Is there a recovery that will let me flash a ROM without changing the SPL back to 2005? Apparently if I can get the phone to boot up I should be able to use flashrec to upgrade the radio and SPL from the point I'm currently at.
Moved as not Android Development.
So I'm not sure what I did but the phone boots now...
Holy sh** it wasn't just me. I have this SAME problem. After flashing eclair and wiping and flashing another ROM it just stays at my splashscreen FOREVER. Even broke my nandroid, so I can't restore. How I fix mine everytime: Flash a rom OVER open eclair boot up... you'll probably get a sht load of force closes and all that but once you ge tto login screen just reboot into recovery and wipe and flash or nandroid restore then it should work.
If you guys are rogers, then you will most likely be ebi1, in which case, dont forget that you must also flash an ebi1 kernal to get past the boot screen.
So the phone booted into the original 1.5, I didnt realize the downgrade of my SPL flashed the ROM too. I put flashrec on and flashed Amen Ra's new recovery image and the rogers radio update, this is what I'm at now.
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA21000)
CPLD-4
Radio-3.22.26.17
Trying to flash to a custom rom again still fails. I've tried cyanogenmod, super D, and openEclair, it doesn't seem to matter. Where can I get an ebi1 kernel to flash?
E: looking at your signature, it seems I've got the right radio, I'll try using that port tool.
That did the trick! I followed the steps in your signature, flashed a rom, then flashed the ebi1 kernel and my phone booted like a dream. Pun intended.
Edit: So I'm back to only being able to run openeclair. Flashing cyanogen and then briancrook's ebi1 kernel still only gives me the rogers screen. I am however able to flash back to openEclair to get access to a working device again.
Edit: openEclair is running like garbage, it keeps completely locking up the device, I haven't even been able to log into my gmail account to get my contacts back.
Okay, I've managed to get the rom running smoothly by wiping everything, flashing the non-ramhack version of openEclair 1.2.2, then flashing the 1.2.2 ebi1 kernel. Unfortunately for some reason when I do get into eclair, I have no phone app, no settings, and no contacts app, even tho the contacts still work if i try to message someone. This is infuriating.
Hi,
I tried flashing the brand new CyanogenMod 5 with Eclair for G1, and I seem to be in "serious" trouble now.
Before flashing:
I had already installed DangerSPL for a few months with no issue
Had the latest radio
Was happily running SuperD1.9.3 with WG Kernel and JIT enabled
Made a Nandroid backup just in case I wished to go back
Wiped Dalvik-cache and Data/Cache to avoid boot loops
All of this with Cyan's Recovery 1.4.
After flashing the ROM and the Gapps, my phone restarted and got stuck on the G1 screen (no boot screen) for, maybe 15 to 30 minutes, which seemed a bit long for me... I finally decided to remove the battery, went back to recovery and made a Nand restore.
But after the restore, rebooting had the same effect : stuck on G1 screen.
I tried flashing several custom roms with no luck (all stuck on G1 screen).
I finally decided to flash the official ADP1.6 ROM from HTC (signed-dream_devphone_userdebug-ota-14721.zip) which installed fine (and updated the radio by the way), and it finally booted on stock Donut.
I tried then to reinstall custom roms but get stuck on G1 screen everytime I try... and flashing Amon_RA's recovery won't work (i keep booting on the stock recovery). But as a workaround, I can use fastboot to boot into Amon_Ra's recovery.
The questions now are :
did I lose root access, thus preventing from installing custom ROMs ?
if so, is it possible to downgrade while being under DangerSPL ? Won't it brick the phone ?
Is there anybody else who had the same problem with upgrading to Cyan's 5 ?
I really need to get custom roms back, stock sucks on G1... but there is no way i can afford bricking my phone.
Thanks for help guys!!
As long you can get to your custom recovery menu, you still have root access.
Keep the Danger SPL, not worth changing it and the Danger SPL has fastboot also.
It takes a while to boot into a newly flashed ROM so just wait 5-15 min.
Do these steps:
1)Do a FULL WIPE of the phone (data, dalvik-cache, ext, battery stats, and rotation ****You won't have some of these options with Cyanogen's recovery. Just wipe what you can****)
2)Repair the ext partition
3)Flash CyanogenMod 5.0.7-DS-Test 1 (this is the g1/mt3g version)
4)Without wiping or rebooting, flash the gapps .zip file
5)Reboot and set up the ROM
6)Flash the latest Amon_RA recovery for your device. Cyanogen uses Amon-RA's recovery now.
1. Upgrade your recovery....cyanogen stopped working on his a while ago, upgrade to Amon_RA's recovery.
2. You only have to wipe data/dalvik, and maybe sd-ext. you do NOT have to wipe battery stats or rotation EVER.
3. Flash CM Rom
4. Flash gapps
Unfortunately, exact same thing.
Stuck on G1 screen.
Reverted back again to adp 1.6
Any other suggestions ?
alou2 said:
Unfortunately, exact same thing.
Stuck on G1 screen.
Reverted back again to adp 1.6
Any other suggestions ?
Click to expand...
Click to collapse
Give us your spl (hboot) and radio. Go into fastboot and type exactly what you see.
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA20000)
CPLD-4
RADIO-2.22.19.26I
Good ?
alou2 said:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA20000)
CPLD-4
RADIO-2.22.19.26I
Good ?
Click to expand...
Click to collapse
Try upgrading your radio? You shouldn't HAVE to, but it might work.
Are you on Amon_RA's recovery now?
I'll try upgrading radio, but it's weird I can't switch back to other custom donut builds...
I've used Amon-RA's recovery to wipe and install the ROM this time.
For some odd reason though, it seems i can't "install" Amon_RA recovery (it seems to switch back to stock recovery), but just boot it through fastboot...
alou2 said:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA20000)
CPLD-4
RADIO-2.22.19.26I
Good ?
Click to expand...
Click to collapse
make sure you're flashing the right recovery. dream still has two options. just like mytouch has H or G.
the one with "R" on the end of it is for rogers, one without it is for USA ones.
What files are you flashing? It sounds like you're flashing an old 1.6 base that has a recovery image included. Are you flashing the DRC83 Defanged as a base?
OK so I tried to take a fresh start on this.
I installed Amon_RA's 1.6.2 as recovery (not the Roger's one, I'm in France and the US tools always worked)
did a nandroid backup to stop reinstalling everything over again each time I want to make a phone call...
used it to repartition the SD (FAT / EXT2 / SWAP), thus formatting everything
wiped everything (except battery and orientation)
Flashed DRC83 Defranged
Without rebooting flashed CM5.0.7-t1
Without rebooting flashed Gapps
And it still gets stuck on the first boot screen (left it for about 20mn on it)...
Then I tried installing DRC83 defranged and it still gets stuck on the damned boot screen !!!
Through adb I can get to shell while on recovery, but the su command prints out :
/sbin/sh: su: not found
Is it normal ?
I can't find the /proc/last_kmsg file (just /proc/kmsg). Is there any log file that could help here ?
I'm going to nand back to stock 1.6, hoping it will start without having to flash the radio+recovery one again...
I noticed something weird when i nand back to my pre-CM5 WG-SuperD backup :
when it boots, it gets to the first boot screen and if USB is connected, i get a "fastboot usb" in a red box on top left of the screen.
To sum up :
phone's definitely not bricked, but won't run any custom rom anymore, but it still permits custom recovery installation/boot.
Something must have been broken/deleted somewhere.
Still asking the (dumb?) question : do I still have root, since su doesn't works (even using terminal server) ?
By the way, I really appreciate you guys taking time to read and answer my posts. Really
alou2 said:
OK so I tried to take a fresh start on this.
I installed Amon_RA's 1.6.2 as recovery (not the Roger's one, I'm in France and the US tools always worked)
did a nandroid backup to stop reinstalling everything over again each time I want to make a phone call...
used it to repartition the SD (FAT / EXT2 / SWAP), thus formatting everything
wiped everything (except battery and orientation)
Flashed DRC83 Defranged
Without rebooting flashed CM5.0.7-t1
Without rebooting flashed Gapps
And it still gets stuck on the first boot screen (left it for about 20mn on it)...
Then I tried installing DRC83 defranged and it still gets stuck on the damned boot screen !!!
Through adb I can get to shell while on recovery, but the su command prints out :
/sbin/sh: su: not found
Is it normal ?
I can't find the /proc/last_kmsg file (just /proc/kmsg). Is there any log file that could help here ?
I'm going to nand back to stock 1.6, hoping it will start without having to flash the radio+recovery one again...
I noticed something weird when i nand back to my pre-CM5 WG-SuperD backup :
when it boots, it gets to the first boot screen and if USB is connected, i get a "fastboot usb" in a red box on top left of the screen.
To sum up :
phone's definitely not bricked, but won't run any custom rom anymore, but it still permits custom recovery installation/boot.
Something must have been broken/deleted somewhere.
Still asking the (dumb?) question : do I still have root, since su doesn't works (even using terminal server) ?
By the way, I really appreciate you guys taking time to read and answer my posts. Really
Click to expand...
Click to collapse
I run into the same issue, I was upgrading from the latest cm 1.6 and after trying a few different things, after wiping with alt+w, I reinstalled danger-spl then installed the cm update, then the google apps; after doing this, it worked fine. BTW, it took about 15 mins to boot up though.
alou2 said:
OK so I tried to take a fresh start on this.
I installed Amon_RA's 1.6.2 as recovery (not the Roger's one, I'm in France and the US tools always worked)
did a nandroid backup to stop reinstalling everything over again each time I want to make a phone call...
used it to repartition the SD (FAT / EXT2 / SWAP), thus formatting everything
wiped everything (except battery and orientation)
Flashed DRC83 Defranged
Without rebooting flashed CM5.0.7-t1
Without rebooting flashed Gapps
Click to expand...
Click to collapse
There is your problem. DO NOT FLASH THE DRC83 BASE!!!
Just repartition your sdcard (if you want to), upgrade to ext3 or ext4, then follow the last 2 steps.
Hi UberMario,
I just reinstalled DangerSPL using Amon_ra's recovery, and then directly flashed CM5 + Gapps (no reboot inbetween).
It's been stuck on the 1st splash screen for 30 minutes now...
I'm letting it for another 30mn (although I think it's useless) and will eventually revert back to stock 1.6... again...
I just don't get what's wrong...
I'm going to try redownloading the archives in case they would've been corrupted, but being unable to install anything else than an official htc firmware seems like a symptom to me... isn't it ?
alou2 said:
Hi UberMario,
I just reinstalled DangerSPL using Amon_ra's recovery, and then directly flashed CM5 + Gapps (no reboot inbetween).
It's been stuck on the 1st splash screen for 30 minutes now...
I'm letting it for another 30mn (although I think it's useless) and will eventually revert back to stock 1.6... again...
I just don't get what's wrong...
I'm going to try redownloading the archives in case they would've been corrupted, but being unable to install anything else than an official htc firmware seems like a symptom to me... isn't it ?
Click to expand...
Click to collapse
I'm not sure if this will make a difference, but flash Gapps first then flash CM5 then reboot and everything should work...
or
You might want to check and make sure your MD5 is correct too..
why would you flash gapps first? you have to flash it on top of cm5.
Yeah... quite sure this won't help.
What could prevent the phone from booting custom firmwares but still allowing to install them ? (and finally I can still run the su command through adb, and get root access, but apps can't get root...)
tehseano said:
why would you flash gapps first? you have to flash it on top of cm5.
Click to expand...
Click to collapse
I rooted my G1 for the first time. I flashed CM 5.0.7 then GApps (no reboot in between). When the phone booted, none of the Google Apps were on the phone. Went back to recovery and did a wipe and flashed GApps then CM (no reboot) and everything installed correctly. Someone said to flash CM first then GApps, but that didn't work for me. Weird.
hopefully this is where this goes. >_> if not, please guide me to where i need to be.
OK. so what is going on:
-right now i am using a STOCK version of 2.2.1 FRG83D, that i rooted with superoneclick.
-i used rom manager to flash RA recovery, because somehow i can't flash roms with clockwork anymore. errors out every time, regardless of version
-i can flash new custom roms using RA, etc etc, but cannot flash roms and restore to old backups
-if i try to USE a custom installed rom, no matter which it is (i have tried a few gingerbread, nxsense, and some 2.2.1 roms), they will ALWAYS reboot after using them for a few seconds, regardless of what i am doing (setting up, using market, or just letting it sit and do nothing)
what i have done before this happened:
-i was using nxsense perfectly fine. great rom, ran great.
-updated rom manager, and clockwork recovery
-tried to flash a new boot animation, but noticed that the new clockwork won't install older .zips that use assert-scripts(?)
-tried to downgrade clockwork, and it randomly restarted the phone during the downgrade
-wanted to try gingerbread, so i flashed the new(er) hboot 0.35.0017 even though i think i had it already, and installed the rom succesfully.
-the rom wouldn't let me download from the market, as it restarted when i tried to download anything.
-i thought the problem was with the new hboot, so i went through a tutorial to revert it back to 0.33.0012 and went back to eclair, so i updated up to frg83d (and obviously got the 0.35.0017 hboot back through updating) and rooted.
the rom i am using now (stock with root) runs fine. haven't really found any real problems.
i just have NO clue why i can't use custom roms. i would absolutely LOVE if someone could help me on this.
I also had similar problem two days ago. I upgraded my clockworkmod recovery to 3.0.0.5 and tried to flash MM CM7 v14. All the problem began. I cannot restore any custom roms except the stock froyo and MM CM7 restarts like crazy whenever I try to install any apps from the market. After that, I also tried RA recovery. No luck. Luckily, I finally find out that the latest recovery messes up my ext3 partition. So, I backup and format my SD card, recreate ext3 partition, restore the SD card, downgrade clockworkmod to 2.5.1.4, wipe everything, fix permission and install MM CM7. It finally works. Hope this help.
PS: as long as I downgrade the clockworkmod, I can restore any custom roms.
Never flash now you will brick it soon
Sent from my Nexus One using XDA App
Latest ClockworkMod was known to have some problem, perhaps.
Use Amon_Ra's, if you want to be sure, and wipe everything (data & dalvik-cache) when going from ROM to ROM. Use Titanium Backup for restoring the apps.
ricky9237 said:
I also had similar problem two days ago. I upgraded my clockworkmod recovery to 3.0.0.5 and tried to flash MM CM7 v14. All the problem began. I cannot restore any custom roms except the stock froyo and MM CM7 restarts like crazy whenever I try to install any apps from the market. After that, I also tried RA recovery. No luck. Luckily, I finally find out that the latest recovery messes up my ext3 partition. So, I backup and format my SD card, recreate ext3 partition, restore the SD card, downgrade clockworkmod to 2.5.1.4, wipe everything, fix permission and install MM CM7. It finally works. Hope this help.
PS: as long as I downgrade the clockworkmod, I can restore any custom roms.
Click to expand...
Click to collapse
omfg thank you so much!!! <3 worked like a charm
kevvibot said:
omfg thank you so much!!! <3 worked like a charm
Click to expand...
Click to collapse
You're welcome. Glad to know my experience can help solving yours too.
Definitely a problem with Clockwork 3.0.0.5! I just went through madness trying to figure out WTF was up as well. The only fix was to completely format and re-partition my card then use RA instead of CW, works great now and I don't know if I will use CW again! What a pain...kinda regret having paid for ROM Manager now after this latest fiasco.
I have no idea what happened, my Hero has been rooted for over a year now and never had any problems. I flashed a herodeck rom version 1.2 and after that I could not flash any more roms but could restore all my nandroids. So I used this, RUU_Hero_C_Sprint_2.27.651.5_R_signed_release.rar, to go back to stock and installed unrevoked, and all went well. I then flashed this TeamHeroC-2.3.5-01OCT-CM-V2.zip and finally it worked and was working great until last night my battery went dead and when I plugged it in to charge it powered up to the white HTC screen and has been stuck there since. I have tried to reflash , restore nandroids, and even hboot a HERCIMG and that is when I noticed S-ON. and since this has happened every file I try to flash comes up corrupt and the latest CM rom came up no signature, and I keep getting errors such as this. So right now all I can do is boot into recovery or Hboot. Please someone help me with this. I love this phone!
williams1978 said:
I have no idea what happened, my Hero has been rooted for over a year now and never had any problems. I flashed a herodeck rom version 1.2 and after that I could not flash any more roms but could restore all my nandroids. So I used this, RUU_Hero_C_Sprint_2.27.651.5_R_signed_release.rar, to go back to stock and installed unrevoked, and all went well. I then flashed this TeamHeroC-2.3.5-01OCT-CM-V2.zip and finally it worked and was working great until last night my battery went dead and when I plugged it in to charge it powered up to the white HTC screen and has been stuck there since. I have tried to reflash , restore nandroids, and even hboot a HERCIMG and that is when I noticed S-ON. and since this has happened every file I try to flash comes up corrupt and the latest CM rom came up no signature, and I keep getting errors such as this. So right now all I can do is boot into recovery or Hboot. Please someone help me with this. I love this phone!
Click to expand...
Click to collapse
Check md5sums of the zips in your sd card to verify no corrupt files. Also make sure signature verification is not toggled in CWM.
dastin1015 said:
Check md5sums of the zips in your sd card to verify no corrupt files. Also make sure signature verification is not toggled in CWM.
Click to expand...
Click to collapse
Thanks for the advice, I will check the Md5sums but I am actually using darchstar's RA recovery at the moment. Also I have formatted my sd card a couple of times and ran disk check on it and also downloaded the roms and files several times.
Hi,
If u have the time, unroot the same way again and then reroot but this time use ROM manager(free version). Update to latest recovery and then
Start over.
It sucks but without the proper knowledge its difficult to fix some issues. So starting over is easiest.
Good luck
V'sHERO on Tapatalk
I'm having the same problem but I cant even flash the stock ROM.
blacksapphire08 said:
I'm having the same problem but I cant even flash the stock ROM.
Click to expand...
Click to collapse
Can u flash anything else?
If so, u may just have a bad download or u have to do at least a factory reset b4 flashing anything.
Good luck
Unroot zip file is also EZ if u just want stock out of the box back on ur phone.
V'sHERO on Tapatalk
vidaljs said:
Hi,
If u have the time, unroot the same way again and then reroot but this time use ROM manager(free version). Update to latest recovery and then
Start over.
It sucks but without the proper knowledge its difficult to fix some issues. So starting over is easiest.
Good luck
V'sHERO on Tapatalk
Click to expand...
Click to collapse
Again thanks for the advice but I can't even do that now as I am stuck on the HTC screen and all I can do besides look at a white HTC screen is boot recovery (darchstars RA recovery) and boot into bootloader. Everything I try to flash will not verify for some reason or another(corrupt or unsigned or something crazy like that) and the RUU will not connect to the phone because it is stuck at the white HTC screen. This one has really stumped me as I have brought this phone back from some bad predicaments, or at least I thought they were. I did get it to try and flash a hercimg of an extracted RUU that is on this forum but it ends up saying no image found and just goes back to the bootloader menu.
williams1978 said:
Again thanks for the advice but I can't even do that now as I am stuck on the HTC screen and all I can do besides look at a white HTC screen is boot recovery (darchstars RA recovery) and boot into bootloader. Everything I try to flash will not verify for some reason or another(corrupt or unsigned or something crazy like that) and the RUU will not connect to the phone because it is stuck at the white HTC screen. This one has really stumped me as I have brought this phone back from some bad predicaments, or at least I thought they were. I did get it to try and flash a hercimg of an extracted RUU that is on this forum but it ends up saying no image found and just goes back to the bootloader menu.
Click to expand...
Click to collapse
Try downloading a recovery from Dastin's thread. Rename it HERC.IMG and place in the root of the SD card. Bootloader and flash. Power down then hold home and power back up to see if recovery worked. See if you can get any recovery flashed at all and if you do you can fix anything then.
¦¦self proclaimed resident prick¦¦
I finally got clockwork recovery 2.5.0.7 by using adb to push to sd card and then flashing from adb. Still can not do anything else, it is still acting the same.
http://forum.xda-developers.com/showthread.php?t=1063843
Try this there's alot of good links.
Sent from my DROID3 using xda premium
You might want to try getting s-off via darch's method. Then flash the eng-spl. Then do a fastboot erase system -w. Then reflash your recovery to see if that helps. If you need any of the files mentioned just pm me and I'll send you a dropbox link. You should be able to get back up and running this way. Good luck.
Locked & Loaded
""Shooter on Deck""
laie1472 said:
You might want to try getting s-off via darch's method. Then flash the eng-spl. Then do a fastboot erase system -w. Then reflash your recovery to see if that helps. If you need any of the files mentioned just pm me and I'll send you a dropbox link. You should be able to get back up and running this way. Good luck.
Locked & Loaded
""Shooter on Deck""
Click to expand...
Click to collapse
Ok I downloaded 1 of the zip files for darch's eng spl because the first link sems to be down. But I transfered the zip onto my sd card with card reader/writer and computer and then flashed it with clockwork 2.5.0.7 and I now have s-off again finally. So before I do anything else I am going to wait and se what you guys think I should do now. Thanks for all the help guys
williams1978 said:
Ok I downloaded 1 of the zip files for darch's eng spl because the first link sems to be down. But I transfered the zip onto my sd card with card reader/writer and computer and then flashed it with clockwork 2.5.0.7 and I now have s-off again finally. So before I do anything else I am going to wait and se what you guys think I should do now. Thanks for all the help guys
Click to expand...
Click to collapse
Are you formatting boot, system, cache, and data before flashing any of these roms? I do it 3x for each partition to make sure everything is wiped clean.
I have always thought that unrevoked was a permanent s-off unlike darch's which is temporary. I have both. I have always felt that if i can get into recovery, I'm golden. Make sure everything is wiped (not just data and cache) before you flash a new Rom.
Sent from my wildheroc using XDA App
Drunkpilot said:
Are you formatting boot, system, cache, and data before flashing any of these roms? I do it 3x for each partition to make sure everything is wiped clean.
I have always thought that unrevoked was a permanent s-off unlike darch's which is temporary. I have both. I have always felt that if i can get into recovery, I'm golden. Make sure everything is wiped (not just data and cache) before you flash a new Rom.
Sent from my wildheroc using XDA App
Click to expand...
Click to collapse
Yes, a couple of times, manually and with Light's format and Caulkin's format. and also I tried to fastboot hercimg.zip of the extracted RUU and all was going well and it actually finally asked if I wanted to apply the update like it is suppose to and it started loading and then when it finished it rebooted hboot and tried to install it again and also at this point I had s-on again. So I redone everything and am now back to s-off.
williams1978 said:
Yes, a couple of times, manually and with Light's format and Caulkin's format. and also I tried to fastboot hercimg.zip of the extracted RUU and all was going well and it actually finally asked if I wanted to apply the update like it is suppose to and it started loading and then when it finished it rebooted hboot and tried to install it again and also at this point I had s-on again. So I redone everything and am now back to s-off.
Click to expand...
Click to collapse
Are you still on a stock "sense" rom right now? What is your PRL, Radio, and PRI? Make sure everything is updated and you should be ready to go now. Since you are S-off now, I would place a HERCIMG.zip on your sd card of a recovery (I've been liking the 4.0.1.4 Orange Lantern that Dastin compiled (which is an unofficial CWM) just so that I have it at the ready in case anything goes south.
If your s-off again make a nand if you can. Also like dp asked what rom, radio, are you on???. Also imo you should flash Ra1.7 untill your back up and running for this process and just revert back when all this is done. Also you should do a fast boot erase system -w to clear everything out. Then backup your sd to your pc and format it as well. Once threw your pc and restore the defaults and then threw your recovery. Which is y I suggest Ra it makes it quick and easy. Ill check back here to see were your at threw out the day.
Edit: Pm sent.
Locked & Loaded
""Shooter on Deck""
The last rom I was on was [ROM][03-OCT-2011][TeamHeroC-2.3.7 - 2.6.35 Kernel] but I am stuck at the white HTC screen right now has been all day. When you say RA 1.7 recovery are you talking about Darchstar's RA 1.7?
Still no luck everything I try to flash fails, I kept getting an error 5 in clockwork recovery when trying to flash CyanogenMod 7 for the HTC Hero (CDMA) :: V7.1.0 (9 Oct 2011).
williams1978 said:
The last rom I was on was [ROM][03-OCT-2011][TeamHeroC-2.3.7 - 2.6.35 Kernel] but I am stuck at the white HTC screen right now has been all day. When you say RA 1.7 recovery are you talking about Darchstar's RA 1.7?
Still no luck everything I try to flash fails, I kept getting an error 5 in clockwork recovery when trying to flash CyanogenMod 7 for the HTC Hero (CDMA) :: V7.1.0 (9 Oct 2011).
Click to expand...
Click to collapse
Yes, I am.
Locked & Loaded
""Shooter on Deck""
Okay I switched recoveries to RA 1.7. I have tried several times to flash CyanogenMod 7 for the HTC Hero (CDMA) :: V7.1.0 and each time a different file comes up corrupt but I have been checking the md5's after it is on the sd card and they have been good. It is crazy, I can flash everything but Roms.
You should do a fastboot erase system -w.
Locked & Loaded
""Shooter on Deck""