I'm currently stuck at the g1/tmobile screen.
I was using the latest Cyanogen mod rom and tried to flash to [xROM Eclair/AOSP] [2.01], this lead to being at the boot screen for 20+ minutes.
I then booted into recovery and hit make nandroid back up by mistake, so I've no back up.
As I still had the cyanogen.zip on my SDCard I wiped and reflashed that, rebooted and I'm now still stuck on the boot screen.
So I can access the recovery fine by taking out the battery and rebooting.
Any ideas?
I think the problem may have started as I don't think I've got the danger SPL that the [xROM Eclair/AOSP] [2.01] rom requires, (But I thought I'd try it after some conflicting posts in its thread.)
emoray said:
I'm currently stuck at the g1/tmobile screen.
I was using the latest Cyanogen mod rom and tried to flash to [xROM Eclair/AOSP] [2.01], this lead to being at the boot screen for 20+ minutes.
I then booted into recovery and hit make nandroid back up by mistake, so I've no back up.
As I still had the cyanogen.zip on my SDCard I wiped and reflashed that, rebooted and I'm now still stuck on the boot screen.
So I can access the recovery fine by taking out the battery and rebooting.
Any ideas?
I think the problem may have started as I don't think I've got the danger SPL that the [xROM Eclair/AOSP] [2.01] rom requires, (But I thought I'd try it after some conflicting posts in its thread.)
Click to expand...
Click to collapse
Did you even wipe when going between the 2 roms?
Ace42 said:
Did you even wipe when going between the 2 roms?
Click to expand...
Click to collapse
Mmmm I usually do, but maybe thats were I went wrong. I've wiped since and it's still stuck though.
emoray said:
I'm currently stuck at the g1/tmobile screen.
I was using the latest Cyanogen mod rom and tried to flash to [xROM Eclair/AOSP] [2.01], this lead to being at the boot screen for 20+ minutes.
I then booted into recovery and hit make nandroid back up by mistake, so I've no back up.
As I still had the cyanogen.zip on my SDCard I wiped and reflashed that, rebooted and I'm now still stuck on the boot screen.
So I can access the recovery fine by taking out the battery and rebooting.
Any ideas?
I think the problem may have started as I don't think I've got the danger SPL that the [xROM Eclair/AOSP] [2.01] rom requires, (But I thought I'd try it after some conflicting posts in its thread.)
Click to expand...
Click to collapse
Wipe everything, including your ext partition. But backup your apps first.
After that, flash the rom again and see if that works.
Bavilo said:
Wipe everything, including your ext partition. But backup your apps first.
After that, flash the rom again and see if that works.
Click to expand...
Click to collapse
Will removing the SD work in the same way? I'm not sure how to wipe the ext 4 partition. (I'm not concerned about my apps and that).
Thanks for the help!
EDIT: Stated in the [xROM Eclair/AOSP] [2.01] thread that a wipe isn't needed before update, 'came from cyan 4.2.11.1 and don't have to wipe anything'
emoray said:
Will removing the SD work in the same way? I'm not sure how to wipe the ext 4 partition. (I'm not concerned about my apps and that).
Thanks for the help!
EDIT: Stated in the [xROM Eclair/AOSP] [2.01] thread that a wipe isn't needed before update, 'came from cyan 4.2.11.1 and don't have to wipe anything'
Click to expand...
Click to collapse
"update" means coming from the previous xrom. you must wipe coming from cyans rom.
emoray said:
I'm currently stuck at the g1/tmobile screen.
I then booted into recovery and hit make nandroid back up by mistake, so I've no back up.
Click to expand...
Click to collapse
Why would you have no backup after running nandroid? Nandroid does not overwrite your old backup when you create a new one. They are timestamped in /sdcard/nandroid/SERIALNUMBEROFDEVICE/timestamp
Running the nandroid script from the console in recovery mode lets you choose the backup you want to restore. Just some food for thought
jmhecker said:
Why would you have no backup after running nandroid? Nandroid does not overwrite your old backup when you create a new one. They are timestamped in /sdcard/nandroid/SERIALNUMBEROFDEVICE/timestamp
Running the nandroid script from the console in recovery mode lets you choose the backup you want to restore. Just some food for thought
Click to expand...
Click to collapse
Ahhh well that'd been great if I hadn't just wiped my SD card to reformat the ext partition! DAMN!
Is it possible to mount the CD card whilst in recovery mode? Then with a clean EXT2/SD card, a wipe and reflashing the rom should work surely?
ums_enable if you have a custom recovery - do it in the console
and next time post in the right section please
not the right post
emoray said:
I'm currently stuck at the g1/tmobile screen.
I was using the latest Cyanogen mod rom and tried to flash to [xROM Eclair/AOSP] [2.01], this lead to being at the boot screen for 20+ minutes.
I then booted into recovery and hit make nandroid back up by mistake, so I've no back up.
As I still had the cyanogen.zip on my SDCard I wiped and reflashed that, rebooted and I'm now still stuck on the boot screen.
So I can access the recovery fine by taking out the battery and rebooting.
Any ideas?
I think the problem may have started as I don't think I've got the danger SPL that the [xROM Eclair/AOSP] [2.01] rom requires, (But I thought I'd try it after some conflicting posts in its thread.)
Click to expand...
Click to collapse
just wipe and start from scratch .repartition ,reflash and you'll be good
try hooking it up to adb and get a logcat while its on the boot screen and see if it is doing something, might just need to wait it out. My G1 was recently on the G1 boot screen for over an hour while busybox was re-writing a filesystem.
Related
G1 is stuck on T-Mobile G1 screen for over 10 mins HELP! I wiped everything.
If you want help, I recommend telling us specifically what you did (what Hero you were on, what version of Cyan you flashed, what recovery you're using)
But without knowing any of that, I'm going to suggest (assuming you have Amon_Ra's latest recovery) that you boot to recovery and wipe everything a couple times, then flash Cyan. By everything, I mean Factory Reset, Wipe EXT, Wipe Dalvik-Cache, and to be safe, Repair EXT. And do all those at least once, factory reset again, and flash.
guitargler said:
If you want help, I recommend telling us specifically what you did (what Hero you were on, what version of Cyan you flashed, what recovery you're using)
But without knowing any of that, I'm going to suggest (assuming you have Amon_Ra's latest recovery) that you boot to recovery and wipe everything a couple times, then flash Cyan. By everything, I mean Factory Reset, Wipe EXT, Wipe Dalvik-Cache, and to be safe, Repair EXT. And do all those at least once, factory reset again, and flash.
Click to expand...
Click to collapse
Yes Amon RA latest recovery. I wiped all that but i didnt do the repair part. Im trying to flash the latest cyanogen.
Well it's best to be safe rather than sorry, so wipe, wipe, and wipe again. afaik, wiping will do you no harm
guitargler said:
Well it's best to be safe rather than sorry, so wipe, wipe, and wipe again. afaik, wiping will do you no harm
Click to expand...
Click to collapse
Hahah alright thanks for the quick reply and i was on mlign 3.3
Don't forget the Htc Recovery first also
JAguirre1231 said:
Don't forget the Htc Recovery first also
Click to expand...
Click to collapse
Yup! Thanks i was trying to figure it out all night i wiped and wiped like he stated. Then i flash the HTC recovery and got cyanogen to work again. BTW how do i delete a thread? Like this one for instance. Keep it clean and less cluttered on XDA
androidboi209 said:
Yup! Thanks i was trying to figure it out all night i wiped and wiped like he stated. Then i flash the HTC recovery and got cyanogen to work again. BTW how do i delete a thread? Like this one for instance. Keep it clean and less cluttered on XDA
Click to expand...
Click to collapse
You don't mods will, and it wasn't flamed or anything so it'll probably stay for awhile
Ok, I'm guessing I misunderstood something. I'm a "noob" so bear with me...
here's what I did.
I was running cm v 4.2.9.1 and decided to try and upgrade to the latest version. I wiped and reflashed and got 4.2.14.1 running, but I felt it was slow (the reason I didnt use any other new version), so I came here looking to see any new roms.
I decided KiNgxKxlicK AOSP 2.1 rom looked cool, so I downloaded it and flashed it (yes I wiped first). I'm guessing this is where it went wrong. The rom took 30 mins to finally boot to home (longest ever) but the sweet nexus screen made it easier to bear. I DID NOT do anything with an spl or any radio (that part still kinda confuses me to be honest). I'm guessing this is why I am in the predicament that I am.
The KiNgxKxlicK AOSP 2.1 rom loads fine, but was VERY slow. I decided I'd just go back to cm v 4.2.9.1. I went to wipe and reflash, but the G1 screen never disappeared. I let it load for about 30 minutes and decided that was a bit ridiculous before removing the battery (mind you, it never got past the T Mobile G1 screen). I was, however, able to reflash KiNgxKxlicK AOSP 2.1 rom and run it. This is all I am able to do. When trying to reflash cyonagen it just hangs on the G1 screen.
I'm a noob so I don't know what went wrong or what I missed.
Can someone PLEASE help me out here and tell me what I need to do to fix this. Thanks
Additional Notes:
Can't get to settings running KiNgxKxlicK AOSP 2.1 AT ALL, and a lot of programs Force Close on the rom.
Thanks for any help/input you guys can provide.
Thanks
Do you have Amon Ra recovery?
No I do not believe so, as I am not exactly sure what that is?
UPDATE: I should also note I checked my SPL and Radio, both were very old (as I realized I followed an OLD guide when I rooted my phone)
I upgraded to the latest radio and SPL and still have the same problem...except King's rom doesn't force close when I go to "settings".....thats about the only difference (still slow/laggy, lots of programs still FC)
When you boot into recovery (holding home+power) it should tell you what recovery image you are using. (i.e. mine says v1.5.2 down at the bottom of the screen) I ran into a similar issue when I attempted to jump between roms without taking all the appropriate steps; all I did was reformat my sd card, wipe the phone, and reflashed my rom and it worked great after that.
I tried reformatting my sd card, even re-partitioned it and I'm still having the same problems:
CM wont get past g1 screen after flash, King's rom still pretty slow....
What do you gys recommend I do next? This is getting really frustrating
1st: Check if youre Formatting is correct
2nd: Wipe EVERYTHING
3rd: Re-Format
4th: Try downloading the ROM again. It could be an issue with the ROM's
5th: Check you have proper radio and SPL (1.33.2005 and 26I)
6th: Pray
Try them all hope one of them works for you dude.
why is it that that 99% of newbs are on cyanogen
@Macrophage001
1. how do I CHECK my formatting to see if its correct?
2. Doesn't formatting do this automatically? I also "wiped" in recovery...
4. Not the roms, I have multiple CM roms, one of which I've had for some time with no problems and have re-flashed over and over
5. As stated above, I did not have the latest at first, i did upgrade to the latest radio and hakyuro(sp) spl to no avail.
@zachattack052
We've all been told it's THE BEST, much before even making the decision to root. I honestly thought CM was the only rom available, that's how much he's praised around here and other forums.....it's just what everyone tells us.
Here's what i suggest you do:
1> Download Amon_RA's recovery from here
here is a link to his thread
2> Transfer the file you just downloaded to the root of your sd
use this code to mount your sdcard from recovery console itself if needed
Code:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
3>Disconnect usb and reboot to recovery (keep home pressed while powering on) or just type
reboot recovery if you are already in recovery console
4> Flash Amon's recovery:
Code:
#mount -a
#flash_image recovery /sdcard/recovery-RA-dream-v1.5.2.img
when complete, reboot to recovery again
5>Partion your sd using amon's recovery (All data on SD will be lost so backup if needed)
[Alt+P] then [Alt+0] or scroll down using the trackball or the volume keys
follow the prompts, set your swap-size to 96 MB (use the vol keys) and 512 MB ext2. when done use the back button to go back and reboot
The above step will give you the partitions required to run any rom. Please make sure you meet the radio and SPL requirements before flashing a rom.
6>Transfer the latest CyanogenMod rom to your SD and flash it.
I would suggest that you try bbuchacher's SuperD rom (it requires Haykuro's Danger SPL)
make sure you flash the radio first and then the SPL if you dont already have it
P.S. When anyone says full wipe, they mean doing a factory reset, wiping your ext partition and wiping the dalvik-cache. These are the first 3 options in Amon_RA's recovery's wipe menu
what i would do....
make sure you flash the HTC recovery files first before you flash the CM rom
go for the defanged version of HTC
so...(once u have amon ra's latest recovery installed)
wipe everything
flash htc / defanged (DO NOT REBOOT!!!)
flash cm latest rom
ALLOW IT TO LOAD FULLY
reboot (personal preference)
create a nandroid backup for future **** ups
enjoy ur rom!!
j.
airmcnair06 said:
@Macrophage001
1. how do I CHECK my formatting to see if its correct?
2. Doesn't formatting do this automatically? I also "wiped" in recovery...
4. Not the roms, I have multiple CM roms, one of which I've had for some time with no problems and have re-flashed over and over
5. As stated above, I did not have the latest at first, i did upgrade to the latest radio and hakyuro(sp) spl to no avail.
@zachattack052
We've all been told it's THE BEST, much before even making the decision to root. I honestly thought CM was the only rom available, that's how much he's praised around here and other forums.....it's just what everyone tells us.
Click to expand...
Click to collapse
1: Go to recovery console and type parted. A list will show up with your fat32,ext2/3/4,linux-swap settings.
2: Yes it does but you can never be too sure.
4: ok
thanx guys I followed the instructions MrBurrito and cqms13 gave and am now running the Super D rom just fine.
Thanks again!
very quick question..
did you wipe dalvik-cache?
Firerat said:
very quick question..
did you wipe dalvik-cache?
Click to expand...
Click to collapse
After installing the RA recovery, yes. I was running CM Recovery though when I began this thread, which is why I was not able to wipe dalvik
Here's the scenario:
Been running CM4.2.15.1 with Amon_RA's recovery v1.6.2 & default(?) SPL.
Nandroid backup.
Wiped data/factory reset.
Tried to flash OpenEclair1.2.2. Got error:
Code:
E: Can't symlink /system/xbin/bb/dirname
E: FAilure at line 73:
symlink /system/xbin/busybox SYSTEM:xbin/bb/dirname
So I wiped again and tried to Nandroid restore.
After "restore," I keep getting stuck on the "T-Mobile G1" screen after waiting 10ish minutes. Any suggestions? Am I not waiting long enough?
Did I "brick" my phone?
Well, you wiped to flash OpenEclair which currently requires the Danger spl (or you can create proper symlinks). Since you wiped and then tried to flash a rom onto your phone which formats the /system partition (here Android resides), I'm thinking you should reflash Cyanogen (after flashing the Htc Recovery of course).
So when I did the factory reset, that means I got rid of the "htc recovery"? The Amon_RA recovery is still working for me though.
EDIT:
So I've wiped again and tried to reflash the CM but again it's still stuck at the "G1" screen. Should I wipe dalvik? I don't understand why my nandroid restore isn't working..
atolar said:
So when I did the factory reset, that means I got rid of the "htc recovery"? The Amon_RA recovery is still working for me though.
EDIT:
So I've wiped again and tried to reflash the CM but again it's still stuck at the "G1" screen. Should I wipe dalvik? I don't understand why my nandroid restore isn't working..
Click to expand...
Click to collapse
The HTC recovery, as in the thing you flashed before you first flashed Cyanogen. I have always done this and I'm pretty sire that Cyanogen does not boot without having flashed the HTC recovery on a new flash (As in coming from another rom)
I can't load my phone to mount my sd card to put those files onto my phone..? I've been flashing roms all the time but I feel like a noob right now.
EDIT:
Oh it's a simple "push". Sorry, freaking out here is all.
EDIT:
successs!! turns out I needed to flash the "base" as described in http://wiki.cyanogenmod.com/index.php/Upgrading_From_Older_CyanogenMod_or_other_rooted_ROMs
Thank you so much for your help!
Phone: CDMA Hero
ROM: Freshhh2.0d
Recovery Image: 1.5.2
Well the story begins:
Last week installed Freshh2.0d rom everything worked perfect...... until I tried to screw with the lock screen (tried to install vanilla lock screen and for some reason it messed the rom soon I assign password to lock screen!!) To even realize it was the lock screen I had to reboot and flash the rom several times (maybe like 8-10!!!) then finally it started working!!!
But after the last flash, I started having force close issues with several core apps, like touch screen, google apps etc..... so this morning decided to reflash the rom one last time and see if it fixes the issues.... but I feel like I have done more than just that..... here is what I have done....
1. Re-flashed Freshhh2.0d rom, after reboot got stuck at "htc" screen that comes up after all the animations
2. I wiped or did a factory reset and flashed again..... same result
3. Wiped again and this time I wanted to download the rom again and while downloading rom, I stumbled up on new recovery image 1.6.2
4. I applied new recovery image with wiped or factory reset phone, rebooted in recovery and flashed rom
5. Again stuck under htc screen after all animations....
6. Went back to recovery image 1.5.2 and flashed rom
7. After all this the net result is still same...... stuck in htc screen....... not booting the phone!!!!
Can somebody point me to the right direction???? I am even thinking about trying a different rom and see if that comes up!!!
Ok, first go back to the 1.6.2 recovery.
Next, wipe the following:
Factory Reset
Dalvik Cache
SD: EXT (if you were using apps2sd this will nuke your apps, so be sure you have a backup).
Then reflash Fresh 2.0d (or whatever ROM you want to use).
If you still have problems I recommend doing the RUU to return it to stock and start over.
Same with me I have been trying to flash fresh 20d. On my first reboot it always gets stuck on HTC screen. I'm comming from Fresh 2.0b2. Don't know what else to try. Though I can do Nandroid and get back to Fresh2.0b2
smw6180 said:
Ok, first go back to the 1.6.2 recovery.
Next, wipe the following:
Factory Reset
Dalvik Cache
SD: EXT (if you were using apps2sd this will nuke your apps, so be sure you have a backup).
Then reflash Fresh 2.0d (or whatever ROM you want to use).
If you still have problems I recommend doing the RUU to return it to stock and start over.
Click to expand...
Click to collapse
I do not have back up of my apps and I am using apps2sd, is there a way at least I can get a list of apps in my sd? I tried to do cd /data/app under shell and it won't let me ......
bigd1231 said:
Same with me I have been trying to flash fresh 20d. On my first reboot it always gets stuck on HTC screen. I'm comming from Fresh 2.0b2. Don't know what else to try. Though I can do Nandroid and get back to Fresh2.0b2
Click to expand...
Click to collapse
When in doubt, always wipe before going to a new rom. When NOT in doubt, wipe anyhow.
Sure you can go to a new rom sometimes without a wipe...but 80% of the time you do much better going clean.
Also, how long have you waited on the HTC screen? I've seen that take upwards of 10 minutes.
I have waited as much as an hour. Also, I did do a Factory reset many times. I just don't know what else to try.
if none of that works. just use the right ruu for your device.
bigd1231 said:
I have waited as much as an hour. Also, I did do a Factory reset many times. I just don't know what else to try.
Click to expand...
Click to collapse
Did you wipe dalvik and SD: ext as well?
You should wipe everything there's an option for.
NO I actually didn't do that I'm going to try right now and post back THANK YOU Didn't wipe SD: ext
bigd1231 said:
NO I actually didn't do that I'm going to try right now and post back THANK YOU Didn't wipe SD: ext
Click to expand...
Click to collapse
Wipe all 3 again, then reflash.
Factory
Dalvik
SD: ext
Then let us know how it goes.
Your problems are caused by apps2sd... plain and simple. Fresh 2.0d's release notes tell you that you are going to have to wipe your sd:ext (as well as data wipe). That is because there were several versions of apps2sd floating around before and they aren't all compatible.
http://geekfor.me/new-release/fresh-20d/
Secondly make sure you are using ext3 and not ext2.
http://geekfor.me/faq/apps2sd/
Yes It worked Finally. I wiped all Three and reflashed it and waited 15 mins and it worked.
yes it worked. I wiped all 3 and worked
smw6180 said:
Wipe all 3 again, then reflash.
Factory
Dalvik
SD: ext
Then let us know how it goes.
Click to expand...
Click to collapse
Great! that did the trick!!!
Flipz, there is one shortcoming with 2.0d (not sure if its something inherent to the original rom itself!) When I use my corporate email on my Hero it forces me to assign password and when I do that and lock my screen phone stops responding there after. This happens when I am using vanilla screen lock update.... I can't unlock for anything.... any idea how to fix this?
Glad to hear you're both up and running.
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""