Related
I searched before I posted this question since I know it is a common question but I can't seem to figure out the problem with my phone.
I recently just bought it and I decided to root it. I following the instructions from wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Nexus_One_Firmware_to_CyanogenMod When I went through the instructions, everything went through smoothly. No errors, all were complete installs but my Nexus One is stuck at the boot screen now. I waited for over 20 minutes but it wouldn't budge at all. I've done the procedure after "fastboot oem unlock" and "Flash CyanogenMod" already but it doesn't seem to make a difference. The flash that I'm currently using is the update-cm-5.0.5.1-N1-signed and gapps-passion-ERE36B-2-signed. Do you have any idea what could be wrong with it or what do you suggest any steps I should take to fixing it?
I don't think my phone is bricked since I'm able to go into Bootloader mode and Recovery.
Try a wipe and if not reflash and re wipe.
Mine is doing this too and i did exactly what OP did
Even after a wipe. Im reflashing right now
5.0.5.2 has just been released. Apparently fixes this bug. get it while it's hot.
Its still taking forever to boot. Im still watching it. What exactly do i do to do a "Wipe"?
Damn I don't have a microSD reader. =\
Is there any way to put the ROM on the microSD via Nexus One?
I'm having the same problem. This is on the recently released ATT compatible N1. I am able to go into Amon_Ra's 1.7 recovery and successfully install the V5.0.5.2 and gapps-passion-EPE54B-signed.zip but still have the same problem. Stuck on the X with the lock. I keep putting the original Rom back and doing it again after a full wipe and still have the same problem.
you dont have your usb cable? I was thinking about that too. Cause i know the nexus has its own memory internally but it doesn't show up under my computer. maybe you can push files through command prompt or something. or on linux
If you have the Amon_Ra's recovery you can do a wipe once you're in recovery.
If you made a backup of the original rom you can just put that back and boot into the original rom. once there, you can mount the usb and download it to the sdcard
you can also download the cyanogen updater from the android market and download the rom to your sdcard to install.
What did the trick for me was fresh install of Cyanogen 5.0.5 which i got to boot succesfully AND THEN use cyanogen updater to get to 5.0.5.2
jekyoo_style said:
Damn I don't have a microSD reader. =\
Is there any way to put the ROM on the microSD via Nexus One?
Click to expand...
Click to collapse
2 ways, either plug it in via usb and mount it from your notification bar on the phone, or download the rom via the web browser on your phone, then use Astro file browser(free) to move it from downloads to the root folder of your SD card, then flash from recovery.
dropshipinc said:
If you have the Amon_Ra's recovery you can do a wipe once you're in recovery.
If you made a backup of the original rom you can just put that back and boot into the original rom. once there, you can mount the usb and download it to the sdcard
you can also download the cyanogen updater from the android market and download the rom to your sdcard to install.
Click to expand...
Click to collapse
How long does it usually take to restore? I have about 18 lines of dots. Should it be taking this long?
5.0.5 first then update
Install the base 5.0.5 first then the google add on if you want the apps. After you boot like that update to the latest CM. I saw this some other place and this worked for me, don't wanna take anyone's credit.
Thanks everyone. 5.0.5.2 worked flawlessly once I was able to put it on my microSD.
If you guys don't have a MicroSD Reader, and have the AmonRA recovery, just boot to the recovery and chose I think the 3rd option (Toggle MS USB). You'll be able to see the phone as a mass storage device.
Here's the sequence of events, wonder if anyone can point me in the right direction for repair.
I am on Froyo, the initial leak rooted by Paul.
I wanted to get my market working, so I found this billg market fix + busybox update zip.
I installed RomManager, and it suggested I flash ClockworkMod Recovery, so I did. It guessed my phone correctly (I think) as the "Nexus One (GSM)". I'm now no longer totally sure - but that IS the T-Mobile version right?
Anyway, I flashed clockworkmod recovery, and then I chose the market fix, and then I rebooted.
Everything seemed OK but the first warning sign was no graphical boot screen (no sparking multi-colour X). It booted up OK but no connection to the network at all. I can not even enable wi-fi.
Not I'm not too sure what to do, would hate to make matters worse. I can boot into recovery and it is ClockworkMod recovery, but of course there are no backups on that thing I can restore to. I was using AmonRA recovery before.
Any thoughts?
TIA Paul
paulvallee said:
Here's the sequence of events, wonder if anyone can point me in the right direction for repair.
I am on Froyo, the initial leak rooted by Paul.
I wanted to get my market working, so I found this billg market fix + busybox update zip.
I installed RomManager, and it suggested I flash ClockworkMod Recovery, so I did. It guessed my phone correctly (I think) as the "Nexus One (GSM)". I'm now no longer totally sure - but that IS the T-Mobile version right?
Anyway, I flashed clockworkmod recovery, and then I chose the market fix, and then I rebooted.
Everything seemed OK but the first warning sign was no graphical boot screen (no sparking multi-colour X). It booted up OK but no connection to the network at all. I can not even enable wi-fi.
Not I'm not too sure what to do, would hate to make matters worse. I can boot into recovery and it is ClockworkMod recovery, but of course there are no backups on that thing I can restore to. I was using AmonRA recovery before.
Any thoughts?
TIA Paul
Click to expand...
Click to collapse
find a froyo radio update from somewhere. there on alot of the rom pages
and flash a new rom after the radio and see what happens
The latest clockworkmod is buggy for me too. You can flash back to amon's recovery in fastboot.
Quick update
Flashing the Froyo radio update was no help.
I re-flashed Amon RA recovery and now I'm reapplying the original Paul's frf50.
Fingers crossed.
Phew, OK I'm back on the air.
Now I have to try to figure out how to apply the market fix without using ClockworkMod!!!
Thanks for help/advice.
Paul
paulvallee said:
Phew, OK I'm back on the air.
Now I have to try to figure out how to apply the market fix without using ClockworkMod!!!
Thanks for help/advice.
Paul
Click to expand...
Click to collapse
Is it a zip you flash in recovery?
I have nexus one. This is my story. I had rooted my phone using universial android. I installed cyanogen mod and was a very happy user until I saw the MIUI Rom and then I flashed that. Then I saw that it was to unstable so I restored to a backup I made of cyanogen. After I started using cyanogen mod again it was very unstable and had random reboots and lots of force closes. So I just decided I was done with the rooting business so I was gonna use a passimg. Acsently I flashed the Korean passimg and I can't flash any of the other ones(except the frg33one because i cant update to frg83 after and lose root) So on the Korean Rom I rooted and installed clockworkmod. Then I noticed I couldn't install any custom rom(i tried CM6, CM6RC3,MIUI)and I kept getting errors.So while I was in clockwordmod restored one of my old stockrom backups before i had flashed any roms and it worked. But still when went to go and try and flash a rom it still gave me errors. But the most ANNNOYING thing of all is i would flash clockwordmod in rommanager than i would touch reboot to recovery. It worked. I got into clockwordmod but then when i would try and go back again a second time it wouldn't be there. It would be the stock android recovery and even when i would go to recovery though the bootloader it would still be stock recovery. I dont know what to do. As i said my bootloader isnt unlocked because i dont want to void my warrenty. my inital plan was if i ever needed to return this ting i could just i could just run a passimg and restore to to stock everything and there would be no traces. If i have to return my phone it would have to be last resort because I live in Canada and I would have to play ridiculous duties and taxes on it. Now i just want to make sure im able to install gingerbread on when it comes out. Also i forgot to mention that everytime i try to update my phone to 2.2.1 it always fails even though im on stock recovery(although even when i go into recovery and it is the stock recovery rommanager still says im running clockwordmod) PLEASE HELP!!!
ps. Im only 13 but i consider myself to be pretty techsmart for 13. I wouldnt mind using cmd/terminal and im running ubuntu 10.10 on my laptop.
ajam100 said:
I have nexus one. This is my story. I had rooted my phone using universial android. I installed cyanogen mod and was a very happy user until I saw the MIUI Rom and then I flashed that. Then I saw that it was to unstable so I restored to a backup I made of cyanogen. After I started using cyanogen mod again it was very unstable and had random reboots and lots of force closes. So I just decided I was done with the rooting business so I was gonna use a passimg. Acsently I flashed the Korean passimg and I can't flash any of the other ones(except the frg33one because i cant update to frg83 after and lose root) So on the Korean Rom I rooted and installed clockworkmod. Then I noticed I couldn't install any custom rom(i tried CM6, CM6RC3,MIUI)and I kept getting errors.So while I was in clockwordmod restored one of my old stockrom backups before i had flashed any roms and it worked. But still when went to go and try and flash a rom it still gave me errors. But the most ANNNOYING thing of all is i would flash clockwordmod in rommanager than i would touch reboot to recovery. It worked. I got into clockwordmod but then when i would try and go back again a second time it wouldn't be there. It would be the stock android recovery and even when i would go to recovery though the bootloader it would still be stock recovery. I dont know what to do. As i said my bootloader isnt unlocked because i dont want to void my warrenty. my inital plan was if i ever needed to return this ting i could just i could just run a passimg and restore to to stock everything and there would be no traces. If i have to return my phone it would have to be last resort because I live in Canada and I would have to play ridiculous duties and taxes on it. Now i just want to make sure im able to install gingerbread on when it comes out. Also i forgot to mention that everytime i try to update my phone to 2.2.1 it always fails even though im on stock recovery(although even when i go into recovery and it is the stock recovery rommanager still says im running clockwordmod) PLEASE HELP!!!
ps. Im only 13 but i consider myself to be pretty techsmart for 13. I wouldnt mind using cmd/terminal and im running ubuntu 10.10 on my laptop.
Click to expand...
Click to collapse
If you installed the original passimg then you'll have 2 files you'll want to remove if you don't want the stock recovery to keep flashing back when you reboot
Remount /system rw and remove:
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
Remove those, flash your custom recovery and you should be good to go.
With respect to the errors: Clear out the cache and dalvik-cache. Wipe and install your rom of choice, be it a stock repack, CM6, Enom etc.
With Amon's latest recovery *1.8.0.1 you can flash both signed (google) and signed (test) packages, so the official update will flash as well as a repack. If you flash the official 2.2.1 remember to pull remove those 2 files again or it will blow away your custom recovery on reboot.
I need to return it to stock before returning it, and I've got less than a week to do so. I've tried so many different methods and files, and the closest I've gotten is a stock/factory reset (with the original setup screen) with a root with Clockwork Recovery (CWR) installed.
I can't use the method in this thread, since this is for the T-Mobile version, and removing the T-Mobile apps and bootscreen would require my rooting it, which would put me back at square one:
http://forum.xda-developers.com/showpost.php?p=12590019&postcount=1
I did find a Wifi version of it in this post, but after flashing it multiple times (once after botching a recovery flash and being unable to boot into it), I think I found out that it's already rooted with CWR installed:
http://forum.xda-developers.com/showpost.php?p=14303822&postcount=3
And then I tried using this method (along with simply using fastboot to flash the stock recovery from the first link), and every time either CWR still came up, or no recovery came up and it simply booted into the OS when I tried to do the update or full factory reset option:
http://forum.xda-developers.com/showpost.php?p=12355315&postcount=1
EDIT: I also found this method looking through the boards, but sadly the files are also for the T-Mobile version:
http://forum.xda-developers.com/showpost.php?p=12453284&postcount=1
(I can't even access the flash_image file needed because the link is invalid)
Any help? I'd rather not return the Streak in its rooted state, even if it looks stock. If all else fails...I'll just use the method in link 2 to restore it, since at least it looks stock when it first boots up...
use the t-mobile method but the WI-FI only files instead of the t-mobile ones, then when you are back to stock get gingerbreak 1.20 and unroot it (this might be optional) then root it and then unroot it again, it gets rid of CWM and Superuser. It is completely at stock for me now.
also I used fastboot to flash the stock recovery before I used gingerbreak, I don't know if that helped or not but just to be on the safe side.
shadowswithin said:
use the t-mobile method but the WI-FI only files instead of the t-mobile ones, then when you are back to stock get gingerbreak 1.20 and unroot it (this might be optional) then root it and then unroot it again, it gets rid of CWM and Superuser. It is completely at stock for me now.
also I used fastboot to flash the stock recovery before I used gingerbreak, I don't know if that helped or not but just to be on the safe side.
Click to expand...
Click to collapse
I'll try that now, I'll post how it turns out. I tried using Gingerbreak to unroot earlier, but didn't think it would work since it just rebooted with no changes.
EDIT: Seems to work so far, I need to recharge before I can use the update or full reset options in the recovery and see if CWR is truly gone, but in any case, thank you so much, finally got it stock and unrooted.
Well, I tried what you said, and while I was able to remove the root through Gingerbreak, and I flashed the stock recovery through fastboot both before and after unrooting...CWR still came up. Tried rooting and unrooting it again, flashing the stock recovery through fastboot before and after unrooting again...CWR still came up.
I think I'll just give up and return it the way it is, I did a factory reset through CWR and turned it off (testing it once before that to make sure the setup screen would show and Superuser wasn't installed), I doubt anybody is going to notice anyway.
magus57 said:
Well, I tried what you said, and while I was able to remove the root through Gingerbreak, and I flashed the stock recovery through fastboot both before and after unrooting...CWR still came up. Tried rooting and unrooting it again, flashing the stock recovery through fastboot before and after unrooting again...CWR still came up.
I think I'll just give up and return it the way it is, I did a factory reset through CWR and turned it off (testing it once before that to make sure the setup screen would show and Superuser wasn't installed), I doubt anybody is going to notice anyway.
Click to expand...
Click to collapse
I'm in a similar situation. I tried DJ Steve's Honeystreak, got back to stock 2.2.2 but it was still rooted. Went the Gingerbreak route to unroot, root, then unroot again. Tried to flash stock update.pkg from Dell website and it booted into CWR. I would try to flash the recovery image using fastboot but 1) I don't have the recovery image and have never used fastboot and 2) it doesn't look like it would work even if I tried according to your results.
I got rid of cwr following by just following the recovery flash steps here, http://forum.xda-developers.com/showthread.php?t=1011654 nothing more and it was done.
jayfr76 said:
I got rid of cwr following by just following the recovery flash steps here, http://forum.xda-developers.com/showthread.php?t=1011654 nothing more and it was done.
Click to expand...
Click to collapse
I tried that as well, still has CWM, but I'm stuck in DELL logo loop. Can't flash anything successfully and can't boot into OS. Was up until 5am trying everything I read in the threads. Nothing. Everything I try gives me no errors, that's the wierd bit. All I need to do is break through the boot loop.
jayfr76 said:
I got rid of cwr following by just following the recovery flash steps here, http://forum.xda-developers.com/showthread.php?t=1011654 nothing more and it was done.
Click to expand...
Click to collapse
I tried the files from that thread, but they are for the t-Mobile version, not the wifi only version. Does anybody know where we can find a stock wifi only recovery image?
bimbot said:
I'm in a similar situation. I tried DJ Steve's Honeystreak, got back to stock 2.2.2 but it was still rooted. Went the Gingerbreak route to unroot, root, then unroot again. Tried to flash stock update.pkg from Dell website and it booted into CWR. I would try to flash the recovery image using fastboot but 1) I don't have the recovery image and have never used fastboot and 2) it doesn't look like it would work even if I tried according to your results.
Click to expand...
Click to collapse
Yeah, I wouldn't bother, doubt it'd work for you if it didn't work for me the however many times I tried it.
And if you've ever done anything in adb with the Android SDK, fastboot is similar - basically, you hold volume (-) and power, wait to get into fastboot, plug it into the computer, and use:
fastboot flash recovery recovery.img
to flash to the recovery. That also works for boot and system.
Bigirish said:
I tried that as well, still has CWM, but I'm stuck in DELL logo loop. Can't flash anything successfully and can't boot into OS. Was up until 5am trying everything I read in the threads. Nothing. Everything I try gives me no errors, that's the wierd bit. All I need to do is break through the boot loop.
Click to expand...
Click to collapse
Try doing the NVFlash method in APX mode, it's pretty much guaranteed to work. It's the method in the first link in my original post, and the files for the Wifi version are in the second post (extraded, the .rar file is like 14GB's, you only need the images p2 though p14 to flash). You'll still have root and CWR, but at least you'll be out of the boot loop and you'll still be able to at least remove root with Gingerbreak.
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""