Hi gang,
Any progress to report on rooting Sapphire 1.6 Tmobile ROM? I know it's early and people are still receiving the OTA update, but I'd imagine that most have received the 1.6 update OTA by now.
Also,... looking for direction on ROMs containing NATIVE EAS (Exchange Activesync).
Thanks
LB
Tmobile MyTouch 1.6
Yeah Please someone!
I just spent 5 hours trying to root this tmobile mt3g 1.6 and had no success. My copilot quit on me after 1.6 upgrade, trying to go to cm 4.1.11.1 which I heard was the latest version that works with copilot.
I did the OTA update to 1.6, and then downgraded to 1.5. Once I did that, I used flashrec to install cm-updater 1.4, and from there it was a piece of cake to flash Cyanogen's latest (4.1.999) mod.
Here is the link to the image you need to put on your phone: http://www.megaupload.com/?d=BLM4EDGE
Download that file, make sure it's named sappimg.nbh, reboot holding power and the volume down button. It will find the file and ask you if you wanna flash, say yes. Once you've rebooted you'll be in 1.5... now you can install flashrec and from there install a recovery image (like Cyanogen's Recovery 1.4).
Guide: http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
Thanks, I'll give it a try.
those are instructions to unroot........
I believe that Relentless Rooter might be able to handle even the 1.6 firmware. Also, Superboot by Paul @ MoDaCo should also do the trick.
Do a little research, and I'm sure you'll find exactly what you're looking for. Best of luck.
I've tried Relentless Rooter. Problem is, I'm on Windows 7. Doesn't seem to like the USB drivers. I'll give Superboot a try.
Thanks!
Just tried Superboot. Received "FAILED (remote: not allow)". I thinks it's my SPL (1.33.0006).
Thanks for the suggestion though.
LB
someone correct me if im mistaken but i always thought you had to go from Donut (1.6) to Cupcake (1.5) and then flashed a rom with a Donut ... That's how is supposed to be right?
//EDIT: I found this @ TheUnlockr
http://theunlockr.com/2009/10/15/how-to-root-a-donut-phone-android-1-6/
Tried the Unlocker already but without Unrooting back to Cupcake. Now forgive me but, even unrooting back to Cupcake will still leave me with the same Radio and SPL, correct? I have the 0006 SPL which I thought was the issue with rooting.
The recovery image doesn't flash the Radio and SPL also or am I confused?
Thanks
Related
Ok, so I want to update to 1.6 aka "Donut", and as you may notice by looking at my signature. I have a Rooted MT3G, do I need to un-root my MT3G first? or can I update while my MT3G is rooted?
Jay_8698 said:
Ok, so I want to update to 1.6 aka "Donut", and as you may notice by looking at my signature. I have a Rooted MT3G, do I need to un-root my MT3G first? or can I update while my MT3G is rooted?
Click to expand...
Click to collapse
you can just flash the 1.6 ota just like you would a rom.... update.zip
this is the the plain 1.6 (donut) rom
http://developer.htc.com/google-io-device.html
there are also a ton of cooked 1.6 roms in the dev section if you wanna go that route
You'll need to wipe going from Cupcake to Donut so it doesn't really matter whether you have Root or not.
If you just want plain Donut, use that link above.
If you want Donut with root, use nk02's ROM.
If you want Donut with tether, apps2sd and all that stuff there are a few ROMs around now. Check out Amon_RA's Donut or Dwang's Donut ROM.
Of course, fastboot Amon_RA's Recovery to perform a nandroid backup of your stock phone (incase you ever have to send it in for warranty) and to flash the new zip.
Ok, so I used the guide here and every time I tried to install the 1.6 update. It said no signature found, the only reason I can think of this is because I have a ROM file named "update".
Can I delete the ROM file off my myTouch once I installed it or do I need to keep it there so the ROM would keep working?
Can anyone explain why the 1.6 update isn't working for me?
Thank you.
Jay_8698 said:
Ok, so I used the guide here and every time I tried to install the 1.6 update. It said no signature found, the only reason I can think of this is because I have a ROM file named "update".
Can I delete the ROM file off my myTouch once I installed it or do I need to keep it there so the ROM would keep working?
Can anyone explain why the 1.6 update isn't working for me?
Thank you.
Click to expand...
Click to collapse
It is the exact same process as you did to your hero rom. It looks like you already did the 1 touch root so simply turn on phone and then mount phone via cable and transfer the file and rename it "update.zip". After that, disconnect the cable and turn off the phone and then hold the home + power button. Wipe the data and then install the update like you did before and voila, you're done.
To see it all in a video, I believe I followed this when I did it
http://www.youtube.com/watch?v=1o2ujqazjcY
Hello,
I have a problem with my G1.
I got my G1 maybe a month ago. It had firmware 1.1 and radio module 1.22.12.29. Back then I did not realize it was a radio image compatible with firmware 1.0 as far as I gather from the HTC website.
At first, I did not intend to root it at all, a decision later I would regret. Well, it worked OK, only it was not updated. I was told I would receive the update over-the-air in 4 days. At first they said it would be to 1.5, but it turned out my operator started to upgrade straight to 1.6.
And so I did receive it in 4 days and the problems began.
Basically, the voice quality is so bad that half of what I say is ununderstandable. My voice sounds metalic and I cannot have a coherent conversation over the phone. It is a business phone, so you can imagine it is rather annoying when I have to struggle to be understood by clients.
Ok, so I checked the bootloader for the radio image version and I found out it was still version 1.22.12.29. As per the HTC website I should have 2.22.19.26I. So, obviously the radio firmware was not updated as it should be as per the HTC website. Thus, it seems the reason voice quality is so poor is the outdated radio firmware.
Since I did not plan to return my new phone to my operator (I had no time for it), I decided to root the phone and update the radio firmware myself. It seemed simple enough and I use Unix and Linux since 15 years, so it seemed it would pose no problem.
Quickly I learned that rooting 1.6 is not so simple. One-click method fails. Only goldcard worked and after a few days of struggle I finally got back to firmware RC7 and rooted the device.
Right after I updated the recovery image to CM 1.4, but before I flashed the CM ROM I attempted to update the radio firmware as was suggested by one tutorial I followed as well as the CM website.
Well, it all went smooth. After the update I pressed Home and Back, it rebooted, back to recovery CM1.4, one more time Home and Back and I was back to the working phone. I checked the radio firmware and lo and behold, it was still version 1.22.12.29. No errors, nothing, smooth update process and no result. I repeated it at least 5 times to no avail.
I decided to install CM 4.2.7.1 ROM and try to update the radio then. Before the CM ROM I updated the SPL to HardSPL with success to have fastboot and went to install CM. It went smooth and I booted into this new rooted G1 ROM with ease.
Again, I attempted to update the radio firmware from recovery CM1.4 and again no results.
So, I am back to square one. I have again firmware 1.6 only from CM instead of stock HTC, and I cannot use this phone for calling.
So, summarizing, I got the phone with firmware 1.1, but radio firmware from 1.0. Why it was not updated together with the system I do not know. Then I got an update to 1.6 and the radio firmware also did not upgrade. Then I went back to RC7 (firmware 1.0), rooted the phone, attempted the radio firmware update before installing CM ROM and failed. And finally, I installed HardSPL + HTC 1.6 recovery (as suggested on the CM website) + CM ROM and again failed to update the radio firmware to 2.22.19.26I. The update process is going without any errors. Verification, extracting, installation of radio image all go OK, the phone reboots but no radio updated.
Anybody any idea why it is like this? Why this phone refuses to update the radio from HTC website.
Any suggestions?
Oliwer
PS. One more thing, I was contemplating updating the radio via fastboot, but it seems after reading HTC website that fastboot is only for system and recovery image flashing. The radio has to go first adn from recovery console. Am I right on this?
I too have a problem updating to the 26i version. however i rooted at 1.5 using the one click root method and ive since switched from cyan 1.4 recovery and cyan roms to amon recovery and dwang roms. No matter which recovery i use, the 26 update flashes without an error but shows up as the same radio ive had all along (1.22.14.11) i made a thread about it but noone seems to have an answer. Sorry I couldnt help, but at least bumped up your thread and maybe someone can help us.
speedysilwady said:
I too have a problem updating to the 26i version. however i rooted at 1.5 using the one click root method and ive since switched from cyan 1.4 recovery and cyan roms to amon recovery and dwang roms. No matter which recovery i use, the 26 update flashes without an error but shows up as the same radio ive had all along (1.22.14.11) i made a thread about it but noone seems to have an answer. Sorry I couldnt help, but at least bumped up your thread and maybe someone can help us.
Click to expand...
Click to collapse
Thanks for sharing!
At least I know I am not alone here with this problem.
Since it's Christmas and I have some more time, I decided to do a Nandroid backup and wipe my phone back to the original rom with 1.0 firmware (RC7).
I used my goldcard and I flashed it in a few minutes. I logged back into 1.0 firmware with the original bootloader and recovery console.
Next I put everything on my goldcard, flashed the recovery CM1.4 from the terminal, went to the bootloader, flashed update.zip with the newest radio 2.x from HTC, everything went smooth. Reboot and again NO change of the firmware. Tried a few more times flash the radio and HardSPL together to no avail. I restored my backup and found myself back to square one.
One think I noticed, and I wonder if you get the same, is that when I flash the radio, the phone reboots back to the recovery console and shows "Formating Cache..." message. It does not tell me anything like Please reboot, just this message. Meanwhile I can move the cursor up and down the recovery menu, so the phone has not hang up. It just sits at the recovery until I reboot it. Once I waited 30 minutes to see if it reboots itself and it does not. So, I press Home+Back and then it reboots fully and after loging in I check the radio and NO change.
So, I wonder if your phone does the same?
Oliwer
PS.
T-Mobile G1 - w/ ROOT
DREA110 PVT 32B
HardSPL 10.95.3000
Recovery image: HTC Android 1.6 (from HTC website)
Class IV 8GB SD Card w/ Ext 4 Partition and Swap partition
That's a huge wall of text, and it's Christmas so I'm a little merry
When flashing the radio image w/ Cy's recovery you must flash as an update.zip using alt-s, press whatever key you need to press to confirm and reboot using home+back. If you use flash any zip or use the trackball to reboot the radio image (or SPL) will not reboot in the required way to complete installation.
AdrianK said:
When flashing the radio image w/ Cy's recovery you must flash as an update.zip using alt-s, press whatever key you need to press to confirm and reboot using home+back. If you use flash any zip or use the trackball to reboot the radio image (or SPL) will not reboot in the required way to complete installation.
Click to expand...
Click to collapse
I tried all possible ways. Just a few minutes ago I went to CM1.4 recovery, used the update from update.zip, pressed Home+Back, rebooted back to recovery console, pressed Home+Back again, booted to CM4.2.10, punched the PIN code, checked the About Phone section and I am still with 1.22.x radio firmware.
This phone simply refuses to update the firmware in any known way.
So, my plan now is to un-root it back to the state I got it 2 months ago and return it to the operator and request upgrade of radio, since Donut with an old radio is basically useless. People simply do not understand half of what I say even if I speak slowly and quietly.
Cheers,
Oliwer
You have to press
Cam+power and it will show radio
....
In settings that radio has nothing to do with one installed...Do you know that the radio does?
It allows custom roms like cyan to be installed while keeping root access. The rom allows some tmo apps like account to still be used here in the states.
yes oliwer i get the same formatting cache message but nothing else happens. i tried in cyans recovery and amons recovery using only button shortcuts and not the trackball. i always named the radio update.zip, but still no luck. Im not sure if the 26i radio requires a certain version before it can upgrade, like maybe i have to upgrade to another radio before i can get to 26i? im not quite sure...ive run out of ideas on what to do. I dont have a warranty or anything on my g1. does the fact im using a donut rom on a cupcake radio have anything to do with it? if i had a cupcake rom and upgraded the radio to 26i from there would it work? i know these might sound like dumb ideas but im still relatively new to the scene and im running out of ideas as to why this is happening or why i cant solve it..
bump? anyone have a solution for us? or advice?
i just realized that i had android 1.1 with the 1.22.14.11 radio when i first got my phone, when t-mobile gave me the 1.5 update, i was still stuck on the same radio for some reason. After that I used the one click method to root and ive been on dwang donut rom ever since with the same dated radio...Ive tried using cyans recovery to flash and still no luck, no error, it says its updated but when i check the baseband or stock spl its still the same radio. I never went for a danger spl when i rooted because i was afraid to brick so i cant fastboot a radio update. I asked in another topic if it was possible to use the "flash_image" command in terminal to flash the radio but i dnt think itll work and i dont wanna risk it. If anyone has any advice or a possible solution please keep us updated.
Thank you!
Turn your phone off, hold the camera button down, and power on your phone.
What do you see?
each time before and after the flashing of the radio using cyans or amons recovery image id get the same rainbow screen saying
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.14.11
Serial0
so im still stuck on the Android 1.1 radio.
speedysilwady said:
yes oliwer i get the same formatting cache message but nothing else happens. i tried in cyans recovery and amons recovery using only button shortcuts and not the trackball. i always named the radio update.zip, but still no luck. Im not sure if the 26i radio requires a certain version before it can upgrade, like maybe i have to upgrade to another radio before i can get to 26i? im not quite sure...ive run out of ideas on what to do. I dont have a warranty or anything on my g1. does the fact im using a donut rom on a cupcake radio have anything to do with it? if i had a cupcake rom and upgraded the radio to 26i from there would it work? i know these might sound like dumb ideas but im still relatively new to the scene and im running out of ideas as to why this is happening or why i cant solve it..
Click to expand...
Click to collapse
I do not know, really, why the radio refuses to upgrade. Since my last message I have read tons of posts on this issue and nearly ALL people can upgrade the radio firmware easily, just like the SPL. Somehow, I can upgrade the SPL to whatever I want, but not the radio. Very strange indeed and no luck so far.
Oliwer
speedysilwady said:
bump? anyone have a solution for us? or advice?
i just realized that i had android 1.1 with the 1.22.14.11 radio when i first got my phone, when t-mobile gave me the 1.5 update, i was still stuck on the same radio for some reason.
Click to expand...
Click to collapse
Exactly the same in my case. Except they upgraded straight to 1.6. Before the upgrade I have 1.1 firmaware and quality of voice was perfect. After the upgrade things went south.
speedysilwady said:
After that I used the one click method to root and ive been on dwang donut rom ever since with the same dated radio...Ive tried using cyans recovery to flash and still no luck, no error, it says its updated but when i check the baseband or stock spl its still the same radio.
Click to expand...
Click to collapse
Same thing with me.
speedysilwady said:
I never went for a danger spl when i rooted because i was afraid to brick so i cant fastboot a radio update.
Click to expand...
Click to collapse
Well, I installed HardSPL and it worked despite the old radio. HardSPL offers FASTBOOT and I use it at times. This is safe, at least for me.
speedysilwady said:
I asked in another topic if it was possible to use the "flash_image" command in terminal to flash the radio but i dnt think itll work and i dont wanna risk it.
Click to expand...
Click to collapse
Well, I did, but it does not work since flash_image updates partitions and G1 does not have radio partition. So, when you try to update the radio.img it tells you no radio partition. It is only possible for Roger G1 since it has radio partition unlike all other G1s and there you could upgrade the radio with flash_image.
speedysilwady said:
If anyone has any advice or a possible solution please keep us updated.
Thank you!
Click to expand...
Click to collapse
Yeap! I just practised how to un-root the phone straight to 1.6 with the original SPL and recovery and I was able to restore my phone to the state before rooting and I plan to give it back to my operator under warranty and ask to get this radio fixed. I will do it next week. I will report if the authorized service will be able to upgrade the radio.
Oliwer
i was reading instructions on how to root but i belive its more difficult to root a 32b version. can someone show me the easiest way to root a 32b mytouch?
thank you so much.
Check out the Cyanogen wiki for instructions to flash his rom on your Mytouch, the instructions are simple. Yes, you also get root access.
when i attempt to flash to the sappimg i get an error saying "Main version is older"
and in the cyan wiki it says the goldcard method does not work.
im having the same problem...i never had these many problems rooting a phone . I have a g1 that i rotted flawlessly. not only did i hear the gold card method doesn't work but it also is very complicated. Im stuck! I really wish the one click root method work for the 1.6
Pvt 32b
hboot 1.33.0007 sapp3000
cpld10
radio 2.22.19.26i
when i had my g1 rooting was easy, this is a nightmare.
I think you have to downgrade to 1.5 to root. That's what I did. Good luck!
Also as mentioned before, check out the cyanogenmod wiki. It gives a very detailed instructions list to help you out.
downgrading to 1.5 is the problem we CANT!!!!
BossLady said:
downgrading to 1.5 is the problem we CANT!!!!
Click to expand...
Click to collapse
exactly. if i could downgrade i wouldnt have made this thread
someone please help us.
does this not work?
http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
methodz said:
does this not work?
http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
Click to expand...
Click to collapse
for the third time...no. i cannont downgrade my phone.
i got an error saying "Main version is older"
trexxcrap2 said:
for the third time...no. i cannont downgrade my phone.
i got an error saying "Main version is older"
Click to expand...
Click to collapse
ARE WE THE ONLY TWO THAT GET THIS?!!!?
I think the only way is either suck it up and use the goldcard method or wait until flashrec updates the apk. we're screwed!
I had this message when I rooted my 32b device yesterday so I followed the gold card option and everything worked without a hitch.
I was told it didnt work in Windows 7 but it worked fine on my xp pc.
Happy to help if you have questions.
Cheers
Dave
Guess its a 32B problem, im able to downgrade to 1.5 but them im getting an error when im trying to use Flash Recover to back up my files.
http://www.youtube.com/watch?v=lR2bvjPXMdQ&feature=related
this video helped me root it by downgrading. If this doesn't work, I don't know..
Jeffmeister said:
Guess its a 32B problem, im able to downgrade to 1.5 but them im getting an error when im trying to use Flash Recover to back up my files.
Click to expand...
Click to collapse
Are you following this steps form the cyanogen wiki?
h t t p ://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_MT3G/Magic_Firmware_to_CyanogenMod
I had the problem with flash recovery when I was running it under 1.6. Once I downgraded back to 1.5, it works fine without a hitch. Flashrec version: flashrec-20090815.apk.
same error message
I'm getting the same error message. I have previously rooted around 10 mytouch phones without problems, but using the same procedure now is giving me that error. It looks like the Hboot software has been updated on any newer phones and is having an issue with updating (or backdating, I suppose) to 1.5
If anyone has a work around I would love to know it.
The old version of Hboot that used to work is HBOOT-1.33.0006
The new version, which is not working, is HBOOT-1.33.0007
Anyone know of a way to backdate the HBOOT software?
WTF....
This phone is impossible to root (over acting,but pissed off) I've tried everything I've read online...I was able to build a goldcard from unlockr's web page,and when installing the sappimg file the damn phone still doesn't want to give up the 1.6....there has got to be something or someone out there that has encountered this bullchip and fixed it
I have a 32B mytouch. did you try unrooting first, before rooting? Just a thought bc i had to do it before rooting, and i had never rooted my phone before that.
do i have root???
HBoot - 1.33.0006 (SAPP 30000)
CPLD - 10
Radio - 2.22.19.261
As i search the forum, i realized that i have "perfected SPL"...that would require me to go through "goldcard" method. I tried and it was so complicated for me...
And then i saw this thread http://forum.xda-developers.com/showthread.php?t=633895 which said you should follow cyanogen's method on this site http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_MT3G/Magic_Firmware_to_CyanogenMod.
so i follow the steps and everything worked out and now i have cyanogens rom running on my MT3G. .... now my question is ....do i have root??...
can i flash other people's roms assuming i have all the right radio and SPL...
when i try to install Amon_RA's recovery img through Terminal Emulator, after i type $su and hit enter....nothing happens....it does not ask me for su permission????.....
Please Help....If i dont have root how was i able to flash cyanogens rom??
do i need to do the goldcard method....or am i set...with root.??
Hi, i have a problem, I need some help solving it.
I have branded Hero (G2 Touch) on T-Mobile. Being tired of waiting for T-Mobile to release their branded 2.1, I followed some instruction on this board and installed generic 2.1. Sadly, the instruction used the RUU for directly installing 2.1 and I did this^^
When I try to install an old 1.5 RUU (t-mobile or generic) I always get the error 140 bootloader version.
I then tried the rooting method, now I managed to install the Amon Ra's Hero Recovery and that works quite good, as I now can use nandroid again (I couldn't do since the 2.73 update).
I managed to restore some backups that were on 1.76, and I had android 1.5 installed again, but still I couldn't install the 2.73 RUU, still getting the bootloader error.
Now, either somebody can tell me how to install the RUU, so I can get back to original t-mobile ROMs and can use OTA to get from 2.73 to android 2.1,
or, somebody could send me a nandroid backup with 2.73 installed.
there might be another possibility: I extracted the rom.zip from the T-mobile 2.73 RUU and tried installing it via recovery... I got an error while opening the file (bad).
has anybody an idea how to solve my problem? pls don't tell me 'install custom roms' i heard that often enough and simply don't want to (though I might give it a try as soon as working sense 2.2 ROMs are ready)... i want to get back to official T-Mobile ROMs
thanks
JW 301 said:
Hi, i have a problem, I need some help solving it.
I have branded Hero (G2 Touch) on T-Mobile. Being tired of waiting for T-Mobile to release their branded 2.1, I followed some instruction on this board and installed generic 2.1. Sadly, the instruction used the RUU for directly installing 2.1 and I did this^^
When I try to install an old 1.5 RUU (t-mobile or generic) I always get the error 140 bootloader version.
I then tried the rooting method, now I managed to install the Amon Ra's Hero Recovery and that works quite good, as I now can use nandroid again (I couldn't do since the 2.73 update).
I managed to restore some backups that were on 1.76, and I had android 1.5 installed again, but still I couldn't install the 2.73 RUU, still getting the bootloader error.
Now, either somebody can tell me how to install the RUU, so I can get back to original t-mobile ROMs and can use OTA to get from 2.73 to android 2.1,
or, somebody could send me a nandroid backup with 2.73 installed.
there might be another possibility: I extracted the rom.zip from the T-mobile 2.73 RUU and tried installing it via recovery... I got an error while opening the file (bad).
has anybody an idea how to solve my problem? pls don't tell me 'install custom roms' i heard that often enough and simply don't want to (though I might give it a try as soon as working sense 2.2 ROMs are ready)... i want to get back to official T-Mobile ROMs
thanks
Click to expand...
Click to collapse
You'll need to use this guide (http://villainrom.co.uk/viewtopic.php?f=46&t=375) to make a goldcard, and downgrade using the HEROIMG.zip method (google it)
it doesn't work... I took the rom.zip, renamed it HEROIMG.zip and put it on my sdcard.
hboot finds it, loads it and then says "Main Version is older! Update Fail! Do you want to reboot device?"
what can I do now?
Have you checked to see if your goldcard has definitely worked?
it definitively is a goldcard, as I used it to install generic ROM on T-Mob device... still doesn't work now... but the problem is not that I try to install a ROM that's not meant for my device (thats what I understood goldcard does), but the problem seems to bee the bootloader-version the 2.1 RUU brought.
what can I do now?
Same thing happened t me a while back, I just re-tried every step from scratch and it worked the third time...!
what exactly did you do then? I tried so many things, at least I want to know, which steps to repeat over and over again
Just going to have a look at it for you, I am going through the processes as we speak so if I find a solution I will post back.
@JW 301 post the info in settings > About Phone
- Model number
- Firmware version
- Baseband version
- Kernel version
- Build numbr
- Software version
- Model number: HTC Hero
- Firmware version: 2.1-update1
- Baseband version 63.18.55.06PU_6.35.15.11
- Kernel version: 2.6.29-063c4d24 [email protected] #1
- Build number: 3.32.405.1 CL191507 release-keys
- Software version: 3.32.405.1
I want to get back to 2.73.111.26 (that is a T-Mobile ROM) so I can apply official T-Mobile OTA updates (by the way, I managed to get to VillainROM 12.0 yesterday, but went back. I want to use official ROMs...)
See new post here;
http://forum.xda-developers.com/showthread.php?p=7600524#post7600524
Had the same problem, I mean, EXACTLY the same.
This is what sorted it for me:
http://forum.xda-developers.com/showthread.php?t=726118
I have searched and searched, tried every method, but I am offically stuck (I think) - I'm prepping a rooted Eris for return - i had previously been able to flash the 2.1 RUU to return to stock, but it now will not work - I guess somewhere along the lines of rooting/ROM flashing my bootloader has changed (it is now v1.49.000) - I can't get any RUU to work (get ERROR in RUU interface) - I have also tried flashing a P00IMG through HBOOT, but it also errors out (something is older than something else - forgot exactly) - I have tried flashing new HBOOT/Recovery Image through ADB per a JCASE post, but that will not work either - I've gotten older ROM's loaded that will allow for new OTA updates, but they ultimately will not work (signature issues i believe) -
So the question is, is there a method that will get me back to 2.1 "stock" & get rid of Amon Ra recovery?
Again, I have searched and tried every method I could find - I have updated my SDK - help anyone?
Ive seen people just send in rooted ones without any problem, so I dont know if they'll check. But if your worried, i would just flash a 2.1 rom that looks like the stock, cause i dont think they'll know the difference.
Do you have a Nandroid backup from when you first rooted?
crax0r said:
Do you have a Nandroid backup from when you first rooted?
Click to expand...
Click to collapse
Unfortunately I don't have it - you wanna loan me yours?
I'm only kind of kidding....
download unzipme.zip which jcase removed on xda from here http://androidmobileos.com/?p=14928 Inside theres dowgrade rom that you flash through custom recovery (which ever one you use). After that you just follow the instructions (adb parts). Works very well. If you will have any issues with adb part as far as flashing back to stock recovery and hboot than check your hboot version and make sure its s-off. If its not you can get it s-off with batery pull trick.
i had an issue like this where the ruu would say that my phone was disconnected and told me to connect it to the computer,i was on a froyo rom,i flashed a 2.1 rom and the ruu worked,just an fyi just incase this might help if you want to return to stock 2.1,once you run the ruu and sync with google you wiil receive the july update also.
sent from my Eris using Tapatalk pro