i have a rogers magic with the perfected spl, i tried the one click rooting method anywayz cause i read it worked for some ppl, well it worked for me also, and i flashed the latest recovery image from amon ra and also wiped and loaded amon ra's 1.6.2 donut rom, everything went perfectly. the thing is lightning wont strike twice cause i cannot seem to use the one click root again and it has gone back to the stock recovery image.
Edit: I still have the recovery image loaded, and the perfect spl, should i just count my blessings or should i attempt to change my spl????
One touch root does not work on donut.
This is how to root a donut phone
http://theunlockr.com/2009/10/15/how-to-root-a-donut-phone-android-1-6/
You must downgrade to 1.5 cupcake first to root again.
No guys, i have a rogers magic, which means i was running 1.5 cupcake cause rogers refuses to update, i had to update that rom to fix the sms timestamp issue, as a result i have the perfect spl, but i tried the one click root and it worked to my surprise, so i then loaded the Amon Ra 1.6.2 donut rom and it worked flawlessly, i'm running it right now with no issues so far.
My question is should i try to change the perfected spl although i have root or should i carry on as normal
Wonder how the recovery can just go back to stock default??
Are you positive you actually flashed the recovery image into your phone and didnt just use adb to boot into ra recovery image ?
Somethings sounds very odd here :S
Yes i'm sure, i made an error, the recovery did not go back to stock. i was getting my timing wrong on the button pressing. i still have the latest amon ra recovery image which is 1.5.2 i think.
Its a PVT 32A Ship S-On H
Hboot-1.33.0010 (SAPP50000)
CPLD- 12
Radio-3.22.20.17
Is this the perfect SPL, if so how was i able to loada custom recovery image and most importantly shoud i try to change it or leave it alone.
I'm running Amon Ra 1.6.2 Donut rom now
any help would be appreciated
did the same tut from the unlockr and it works... its rooted and with amons recovery rom and im running the hofo rom aswell as i just updated the recovery rom so i can confirm its rooted
Related
I'm trying to root a MyTouch 3G 1.2 by following the guide at theunlockr.com, and when I get to the step for flashing the Amon RA recovery I get the error "remote: image update error". I've tried using both amon ra's latest (v1.7.0G) and the clockwork recovery and get the same error for both. I'm pretty sure it's not the gold card as it finds SAPPIMG.zip and updates fine. I've tried various SAPPIMG.zip's and everything works up until the point of flashing recovery. I've tried booting the recovery with fastboot as well and it just shows a white screen with the three skateboarding androids and hangs.
Any help would be very much appreciated, as I was unsuccessful at returning the phone to it's previous unrooted state either. I really need to get this solved asap even if it means returning the phone back to it's previous state. The phone belongs to my mom and I told her I'd root it for her thinking it'd be a pretty simple process.
Just an FYI: I do have previous experience with rooting and flashing roms, recovery, etc as I have a G1 that's currently using Amon RA v1.7.0 recovery and running cyanogenmod 5.0.7.
You do have the recovery in your tools folder and are using fastboot flash recovery recovery.img to fastboot flash it correct? Just one hundred percent sure I couldn't tell you how many times people have gotten the fastboot command wrong.
SAPPIMG should be SAPPIMG.img, not SAPPIMG.zip. this in itself should be Amon's perfect SPL that is being changed to this .img and not using the .zip
unfortuanetly unlockr doesn't have good info for the 1.2
dimmakherbs said:
SAPPIMG should be SAPPIMG.img, not SAPPIMG.zip. this in itself should be Amon's perfect SPL that is being changed to this .img and not using the .zip
unfortuanetly unlockr doesn't have good info for the 1.2
Click to expand...
Click to collapse
Opps I flashed the zip, though im running my phone rooted, its smooth except for a long boot up time...
It is supposed to be a ziip for our phones, ive only seen sappimgs with a .nbh or a .zip extension not single .img.
I had Leak 2.1v3 on my phone, and following the XDA thread, I've successfully rooted my Eris using the stock 8gb card. Twice. I re did the root thinking I corrupted the RUU file, or something else during the initial root. I have Amon recovery installed and accessible at will.
I have full access to my phone with adb shell with SU access, but I'm unable to boot into any custom rom. So far I've tried Evil Eris 3.0 and Aloysius. They install without errors, but on reboot the phone to access the rom, the phone will freeze or loop. I've tried waiting over 20 minutes with the HTC boot screen flashing about every 15 seconds after installing Aloysius.
I'm still showing hboot 1.49.0000 S-ON. Is this what is stopping me from booting a custom rom? Or am I missing something that will change the security status to off?
Suggestions? What am I missing?
Thanks
Ok, looks like I got somewhere, I managed to install the grdlock beta rom. Not sure why the other roms wouldn't install tho. They all came from the same source. hboot is still 1.49.0000 S-ON tho.
NAA_Silent said:
Ok, looks like I got somewhere, I managed to install the grdlock beta rom. Not sure why the other roms wouldn't install tho. They all came from the same source. hboot is still 1.49.0000 S-ON tho.
Click to expand...
Click to collapse
The new rooting method ("Incredible/Slide") does not currently replace the S-ON bootloader, so phones rooted this way will not have 1.49.2000 S-OFF on them.
As for your troubles, you need to Wipe /data (FR) in Amon_RA recovery before you install a new ROM. Amon_RA does not enforce wiping of the /system and /data partitions before a new rom is loaded from the SD card, so you probably ended up with a mixture of old ROM and new ROM in a couple of places. (The dev can pre-clean those partitions in the update-script, but I'm not sure if that happens for the ROMs you mentioned.)
Always a good idea to wipe before a new ROM install (not necessary for a Nandroid restore, though, because it does a wipe itself).
bftb0
I thought I'd wiped those caches within Amon recovery. Good to know that I'm not going insane with the 1.49 S-ON tho! I couldn't find anything anywhere to let me know the S-ON was normal. After I get everything up and running with the grdlock rom, I'll back it up and try one of the other roms, being darn sure to wipe everything Amons will let me wipe first. Thanks for the info!
It appears that the rom files that I was using were corrupt. Without the md5 info for those files I had no way of checking. I went to a different site and downloaded Aloysius 12, and it's up and running just fine now
Thanks for the nudges in the right direction!
After putting a new kernel on my device running cm 6 RC1 and supposedly clockworkmod recovery latest, I now do not have a working phone as it stops at the mytouch screen and does not go further, only thing available to use is fastboot which to my dismay, I am having the perfect spl error (remote: not allow), any insight in this problem would be much appreciated.
Trunekind said:
After putting a new kernel on my device running cm 6 RC1 and supposedly clockworkmod recovery latest, I now do not have a working phone as it stops at the mytouch screen and does not go further, only thing available to use is fastboot which to my dismay, I am having the perfect spl error (remote: not allow), any insight in this problem would be much appreciated.
Click to expand...
Click to collapse
Just reboot into Clockworkmod Recovery and flash a new rom and the old kernel
Clockwork recovery sometimes doesn't flash correctly through rom manager. Try downloading among RA's recovery and doing "fastboot flash recovery recovery.img". You will need an engineering spl though.
Sent from my HTC Magic using XDA App
Something went wrong. I don't know why all you new android nubs have to use "clockwork or "sp" recovery. A good ol Recovery image like Amon Ra's latest 1.7.0G works great. Anyway, you didn't brick the device. Just try re-flashing or flashing another rom. (one you know for a fact works) Oh, if you did a nandroid backup, I suggest you restore it. And if you can't get into "clockwork" recovery upon boot. Then I suggest you do what @caedus90 advised and flash Amon RA's recovery through ADB.
Hope this helps. And stop using those idiot friendly recovery alternatives. =P
later
xIoNiCx said:
Something went wrong. I don't know why all you new android nubs have to use "clockwork or "sp" recovery. A good ol Recovery image like Amon Ra's latest 1.7.0G works great. Anyway, you didn't brick the device. Just try re-flashing or flashing another rom. (one you know for a fact works) Oh, if you did a nandroid backup, I suggest you restore it. And if you can't get into "clockwork" recovery upon boot. Then I suggest you do what @caedus90 advised and flash Amon RA's recovery through ADB.
Hope this helps. And stop using those idiot friendly recovery alternatives. =P
later
Click to expand...
Click to collapse
OMG...I feel so dumb right now...I don't know why I didn't just stick with Amon's recovery...I got curious too and try to use Rom Manager to play around and now I am stuck as well...but my case is a little different in that I cannot get into recovery BUT my phone still boots right into Android like normal...
I flashed Amon's recovery via Rom Manager but still cannot get back into recovery...flashed ClockworkMod recovery but still no recovery...
So advice, please...I think I've learned my lesson and stay with the manual work from now on...lol...I was totally fine with Amon's recovery too...guess my curiosity will kill the cat eventually if I don't wise up...
What's the best way to get recovery back? I have Cyanogen's CM6 on my mt3g 32b...Much thanks for any advice...
UPDATE: Just thought I let you guys know that I was able to get Amon's recovery to work again by keep trying the reflash while in Rom Manager thanks to a tip from another member...Last time I'm touching Rom Manager...It's not a bad program, just us users who are causing problem...
I have just rootet my magic, but i cant backup my recovery with recovery flasher 1.1.3 .
I think the last 1.5 rom for magic 32a is patched against flash recovery.
And the rom manager doesnt support a backup of the current recovery.
How can backup my stock recovery??
Magic 32a s-on h
1.76.0009 spl
6.35 radio
no one an idea?
i'll be sure, before i flash a custom recovery, i am able to go back.
so i need a orginal recovery.img
the best would be the own, but i cant backup the recovery.
Its not that we don't know how it's just thar there is no reason to.. if you can get into the bootloader you can restore the stock rom via SAPPIMG.zip or SAPPIMG.nbh .. this includes the stock recovery.
Having a stock recovery on a custom rom is not very useful.
Just note while you have the 6.x radio you want a hero custom recovery
(Advance users unzip the sappimg and grab recovery.img ..)
thanks for the information about the SAPPIMG.zip or SAPPIMG.nbh, it was very usefull.
i'll try the clockwork recovery with the rommanager out of market.
i think this is possible, or isnt it?
with the 6.35 radio?
I've heard about lots of bricked phones thanks to clockwork/rom manager. Use AmonRA's recovery.
keinengel said:
I've heard about lots of bricked phones thanks to clockwork/rom manager. Use AmonRA's recovery.
Click to expand...
Click to collapse
In theory it will be fine if you use the hero recovery not the ion/magic one..
But given the confusion/problems/near bricks of others.. I agree getting the hero RA recovery and booting it manually with home+power is the safest way... that way if you goof you just boot android normally and try the flash again.
ok i will flash amonRA recovery.
like in this thread:
http://forum.xda-developers.com/showthread.php?t=756918
edt:
nice, it worked. thank guys for protect a maybe brick (with this sh.. rommanager clockwork)
edt2:
now i am using this rom:
http://forum.xda-developers.com/showthread.php?p=8142644#post8142644
best i have ever seen
I'm currently running CM6 with ramon recovery on my 32b magic and each time I flash a new nightly it comes pre-installed with Koush's Rom manager.
Would it be a simple case of installing clockwork recovery through the rom manager as it suggests or do I need to remove Ramon recovery first?
Has anyone had any success with Clockwork recovery on the 32b magic?
There's no reason it shouldn't work without removing recovery. However I've heard lots of people say clockwork didn't install right so they were left without recovery. Before flashing it, make sure you have a fastboot capable SPL (2010/'09/'05/'04) so you can boot in to the SPL and flash the recovery image from there, should the need arise
It is that simple, and I have had great success with Clockwork Recovery and ROM Manager.