So I decided to root my phone, following everything here (I am completely noob at this):
http://forum.xda-developers.com/showthread.php?t=694572
I did screw up on step 10 where instead of doing a "Flash zip from sdcard" I did a reboot and it booted into the original system. So I went through the process again from step one and did everything right this time.
I don't know if that broke the root or not, but I cannot flash anything on the phone, mainly new ROM.
When I try to wipe it will give me this error:
"error wipe dalvik via adb"
"error wipe ext via adb"
If I go and flash the ROM anyway, it will get stuck at the splash screen forever...
Fresh Rom 2.3.3 will give me the endless droid dance
Cyanogenmod 6.0.0 Test 4 For Hero CDMA will be stuck at the "X" animation
I can pull out the battery stuff and it still doesn't work. I am able to just restore my nandroid backup and the phone will work then.
Does anyone knows what did wrong? Or how I can get this to work?
PS: I have the "Superuser Permission" ninja is my apptray so I assume I rooted it correctly...
Make sure your battery its charged when flashing. Re-download whatever files you want to flash, sometimes they get corrupted during download. Which recovery are you using?
Sent from my Hero CDMA using XDA App
also if when your in the recovery image for the first time or you have been in there for awhile i get those errors but usually a shut down and the boot back into recovery works for me
I managed to get this working with Rom Manager after restoring the nandroid to the Sprint ROM. Running on Fresh 2.3.3 now, thanks for the reply!
Related
I followed the unlockr guide and did everything and now I am stuck on the g1 screen. I checked my radio and spl are the right number. I wiped everything then re-partitioned then re-updated it with the lastest rom and still stuck. Can anyone give me advice?
If you can get into recovery of bootloader than you aren't bricked.
I know it isn't bricked but it is still temporarily useless. I really want a custom ROM and I wish I knew why this thing was messing up.
You could always reflash using the .nbh file then go through the steps again =]
start from step 1 again
The only thing I could think of is when I updated the .spl I didn't wipe. Whenever I booted into the recovery (before using amon ra's, just the stock recovery) I didn't wipe the system before updating .spl. Whenever I wiped and tried to update .spl it would give me an error (I think the E:signature (5 files)). Anyways I will retry! Thanks for your help!
Hi Everyone,
This is my first time attempting to root my nexus one.
I used the One-click root application posted on these forums and the ROM manager to try and install Cyanogen 6.0RC2. Now my phone boots into the loading screen with the particles flying together to form an x, followed by the same animation in blue instead of the android colors, with a skateboarding android icon in the center. About 10 seconds later, it seems to fail and go back to the multi-colored animation. This loop continues forever until I yank the battery.
How do I get back to a working environment?
Did you install the froyo baseband?
Did you have 2.2 on before you installed CM6?
Did you wipe as is recommended by Cyanogen?
Try installing CM6 again THE PROPER WAY... read their post on the forums and then report.
I already had Froyo on here. How do I bust out of this boot cycle to try again?
pull and reinstall battery and boot to recovery
a boot loop is normally caused by an incorrect flash, either by the recovery just being weird or the phone not correctly wiping prior to flashing. Did you make backup before you flashed?
If so here is what you do.
Boot into recovery
go to wipe
wipe "data"
wipe "cache"
and wipe "dalvik-cahe" (so long as you only select these three your sd card will remain untouched)
(if you want to resstore back to stock)
go to restore/backup
hit restore nandroid
select the restore point
(if you want to continue to install CM6)
go to "install zip from sd car"
select the zip
once done install the gapps zip (if you donwloaded it)
reboot
Done
How do I get it to boot into recovery?
When I remove the battery, and then power it on, it goes right back into the boot loop.
Nevermind. It's working now. I think I forgot to wipe first.
Thanks so much for your help, everyone!
--
Ryan
Ok. I was running completely stock 2.32.651.2 on my HTC Hero CMDA. I had never rooted before. In the past as various points I had tried a few of the one click methods here and there with no luck, but I never had really done my homework and gave it a serious shot. Over the christmas break my brother in law and I were discussing phones and he told me that he thought Z4root would one click root me and encouraged me a bit not to be scared about trying it. This, combined with my dwindling internal memory gave me the push I needed to be serious about getting a custom rom onto the phone, but no matter what I do I can't seem to get anything to work. Here is an account of the steps I have taken so far.
-Downloaded Z4Root
-Ran Z4Root. It seemed to lock up, and after about 15 minutes I pulled the battery.
-Ran Z4Root again. It stuck on "Rebooting...", but phone was not locked up.
-Checked Apps drawer and found Superuser installed.
-Downloaded Rom Manager and successfully flashed ClockworkMod Recovery.
-Booted to recovery with Rom Manager and manually made a nandroid backup.
-Selected a custom rom (CM6.1) with Rom Manager with "wipe data and cache" selected. Phone booted to recovery and seemed to successfully load CM6.1, phone rebooted itself back into recovery. Whenever I selected reboot phone it would reboot back into recovery.
-Restored my nandroid.
-I then tried to load AOSPmod and NFXStock using the Rom Manager. Both locked up on the initial white HTC screen.
-I then tried to load CM6.1, AOSPmod, and NFXStock manually in recovery, making sure to wipe boot, system, data, and cache in the partitions menu with no success.
-I then ran z4root again and unrooted/rerooted. Each time I run it, it sits on the "rebooting" screen for up to 30 minutes. Phone is not locked up and if I rerun the program it tells me I have root.
-After speaking with some people on AOSP's irc channel I was able to get S-off (I was following instructions and don't recall the exact steps to do this), but with S-Off I tried flashing various roms using the H-boot method with them named HERCIMG.zip Same results: CM 6.1 booted to recovery, AOSPmod and NFXStock both lock on HTC screen.
Next I flashed 2.31.651.7 with the Hboot using a HERCIMG.zip I downloaded via this thread: http://forum.xda-developers.com/showthread.php?t=804692. I then used this thread to root the phone: http://forum.xda-developers.com/showthread.php?t=804296. After rooting I installed Rom Manager, flashed my recovery, and made a nandroid. I then tried to load CM 6.1. Same result; it loaded to the recovery screen. AOSP and NFXSTock both stuck on the HTC screen. I flashed my original nandroid back to my rooted 2.32.651.2
This morning I decided to try the PC RUU route and downloaded the official 2.27.651.5 RUU as provided in this thread: http://forum.xda-developers.com/showthread.php?t=694572. When I try to run it however, I get an error on my PC screen: Error [140] Bootloader version is incorrect.
ARG! Please help me to get a custom running!
Thanks,
JohnPublic
JohnPublic said:
Ok. I was running completely stock 2.32.651.2 on my HTC Hero CMDA. I had never rooted before. In the past as various points I had tried a few of the one click methods here and there with no luck, but I never had really done my homework and gave it a serious shot. Over the christmas break my brother in law and I were discussing phones and he told me that he thought Z4root would one click root me and encouraged me a bit not to be scared about trying it. This, combined with my dwindling internal memory gave me the push I needed to be serious about getting a custom rom onto the phone, but no matter what I do I can't seem to get anything to work. Here is an account of the steps I have taken so far.
-Downloaded Z4Root
-Ran Z4Root. It seemed to lock up, and after about 15 minutes I pulled the battery.
-Ran Z4Root again. It stuck on "Rebooting...", but phone was not locked up.
-Checked Apps drawer and found Superuser installed.
-Downloaded Rom Manager and successfully flashed ClockworkMod Recovery.
-Booted to recovery with Rom Manager and manually made a nandroid backup.
-Selected a custom rom (CM6.1) with Rom Manager with "wipe data and cache" selected. Phone booted to recovery and seemed to successfully load CM6.1, phone rebooted itself back into recovery. Whenever I selected reboot phone it would reboot back into recovery.
-Restored my nandroid.
-I then tried to load AOSPmod and NFXStock using the Rom Manager. Both locked up on the initial white HTC screen.
-I then tried to load CM6.1, AOSPmod, and NFXStock manually in recovery, making sure to wipe boot, system, data, and cache in the partitions menu with no success.
-I then ran z4root again and unrooted/rerooted. Each time I run it, it sits on the "rebooting" screen for up to 30 minutes. Phone is not locked up and if I rerun the program it tells me I have root.
-After speaking with some people on AOSP's irc channel I was able to get S-off (I was following instructions and don't recall the exact steps to do this), but with S-Off I tried flashing various roms using the H-boot method with them named HERCIMG.zip Same results: CM 6.1 booted to recovery, AOSPmod and NFXStock both lock on HTC screen.
Next I flashed 2.31.651.7 with the Hboot using a HERCIMG.zip I downloaded via this thread: http://forum.xda-developers.com/showthread.php?t=804692. I then used this thread to root the phone: http://forum.xda-developers.com/showthread.php?t=804296. After rooting I installed Rom Manager, flashed my recovery, and made a nandroid. I then tried to load CM 6.1. Same result; it loaded to the recovery screen. AOSP and NFXSTock both stuck on the HTC screen. I flashed my original nandroid back to my rooted 2.32.651.2
This morning I decided to try the PC RUU route and downloaded the official 2.27.651.5 RUU as provided in this thread: http://forum.xda-developers.com/showthread.php?t=694572. When I try to run it however, I get an error on my PC screen: Error [140] Bootloader version is incorrect.
ARG! Please help me to get a custom running!
Thanks,
JohnPublic
Click to expand...
Click to collapse
try amon ra recovery, full wipe including dalvik and flash one of the roms you listed above, like cm6.1 stable (from cyanogenmod.com) with the gapps (from jaybob413's rom thread in hero development). once it starts the boot, give it time, it may take a long time (10 min.) Hope it works.
I flashed RA 1.6.2
Wiped Data/Factory Reset
Wiped Dalvik Cache
Install zip from sd:
When I try CM6.1 I get the error:
E:Corrupt file: system/fonts/DroidSansFallback.ttf
E:Verification failed
When I try NFXStock I get the error:
E:Corrupt file: system/lib/libiconv.so
E:Verification failed
I don't have AOSP on my card right now to try it.
Now don't I feel silly! I re-downloaded CM6.1 and put it on the card and it seems to be firing up. I'm on the CM logo bootscreen right now. I have no idea how three separate zips all got corrupted en route to my card, but I suppose that must be what happened. Thanks for the help!
JohnPublic said:
I flashed RA 1.6.2
Wiped Data/Factory Reset
Wiped Dalvik Cache
Install zip from sd:
When I try CM6.1 I get the error:
E:Corrupt file: system/fonts/DroidSansFallback.ttf
E:Verification failed
When I try NFXStock I get the error:
E:Corrupt file: system/lib/libiconv.so
E:Verification failed
I don't have AOSP on my card right now to try it.
Click to expand...
Click to collapse
have you tried re-downloading the roms? it sounds like something is missing in them, which shouldn't be. if you are downloading from your phone, try a download from a computer and see what happens. where are you dl'ing the roms from? verification failure makes no sense..... also, did you recently update rom manager from market to 3.0.0.7? there was something listed in the changelog about verification failure fixed when using other recovery, i think....
EDIT: saw your last post, maybe your browser was acting up? delete the bad ones, get new ones, flash away
My nexus has been a great platform for running roms for quite a while now, but after installing CM6 as of late it has been really picky about what it can flash. For instance the only way I got it to install the normal stock rom afterwards was by putting it in as passimg.zip. Every time I try to flash something to it now, the signature verification fails. Anyone else have this problem?
Edit: If I install a rooted room, it gives me
"assert failed: !less_than_int(1277930906, getprop("ro.build.date.utc"))
E: Error in /sdcard/update blah blah .zip
(Status 7) Installation Aborted
Did you lose root?
I don't think so, I could try unlocking the boot loader again but it says unlocked at the top already...and it won't even flash normal signed passion roms...
what recovery do you have? have yopu tried fastboot flash recovery? like amon rah
I ended up using
http://forum.xda-developers.com/showthread.php?t=614850
to fix it.
It still refuses any update.zip file that isnt OTA...
every signature varification fails instantly. So I guess until I throw this phone in the trash pile or just use it for an MP3 player..its not going to be doing anything in the way of modding
If you've used the original shipping ROM tutorial/passimg, then you'll have a stock recovery that will of course only install released signed things.
Rusty! said:
If you've used the original shipping ROM tutorial/passimg, then you'll have a stock recovery that will of course only install released signed things.
Click to expand...
Click to collapse
right and I flashed clockworks recovery to get it off the standard. I guess I could go out and get Root again without it, but at this point I don't see the point with Gingerbread coming out. I'm just glad to not have a paper weight sitting next to my computer again.
btw Calling Tmo/HTC doesn't help. Most of the guys there don't have a clue what FRG83 is even lol
Keep in mind, if you have the stock on there, it will wipe out your custom recovery and restore it to the stock recovery every time you restart the phone.
So if you flashed Clockwork, after a reboot the stock recovery will be there again.
Yes amonra and cwr have options to toggle off verification best to start with amonra recovery then go through the steps
First of all I hope this is in the right place: I did do a search but still couldn't find any help.
Here's my problem:
After getting a (delicious) taste for customisation after rooting and lagfixing, I decided to give custom ROMs a go. Hours of indecision passed and ultimately I settled on Doc and Stefunel's magical ROM. Due to currently being on 2.1, I chose to follow the set of instructions provided on the page for doing so.
All was well up until the very final step. When rebooting the phone through ClockworkMod Recovery, instead passing the Samsung boot screen into the Android system, the phone boots into CWM recovery. I've tried doing another factory reset, and reinstalling the ROM to no avail. I've also tried mounting "/mnt/sdcard" in order to place another ROM to flash from, but I keep getting a message telling me to insert a disk (what happens when you don't mount).
That's pretty much all there is to it. I'd be massively grateful for any help!
-anti
If you have made a backup of your apps then flash the JPY with Odin and then make factory reset in recovery mode. Then root with CF Root 1.3 (Or something like that) and flash CWM Recovery. That's what I would do.
Sent from my GT-I9000 using XDA App
from the recovery menu try wipe cache and dalvik, and reboot