Related
So I'm assuming that the "One Click Root" method is not going to work in Donut. Is that correct?
If so, I'll need to downgrade to Cupcake first. Does anyone have a download link? Is there anything I need to do before applying the update.zip to downgrade?
Thanks for your support
OolonColuphid said:
So I'm assuming that the "One Click Root" method is not going to work in Donut. Is that correct?
If so, I'll need to downgrade to Cupcake first. Does anyone have a download link? Is there anything I need to do before applying the update.zip to downgrade?
Thanks for your support
Click to expand...
Click to collapse
Go read the many stickies on rooting. You don't downgrade to Cupcake, you downgrade all the way back to RC29.
cigar3tte said:
Go read the many stickies on rooting. You don't downgrade to Cupcake, you downgrade all the way back to RC29.
Click to expand...
Click to collapse
Your suggestion doesn't make any sense since there are plenty of devices that shipped with 1.5 (i.e. rogers dream), which happen to be quite incompatible with 1.0 firmware. It is therefore impossible to downgrade to rc29.
If you're *very lucky*, the bootloader you have won't enforce versions and might actually allow downgrading to 1.5, in which case the 1c-root procedure will work.
lbcoder said:
Your suggestion doesn't make any sense since there are plenty of devices that shipped with 1.5 (i.e. rogers dream), which happen to be quite incompatible with 1.0 firmware. It is therefore impossible to downgrade to rc29.
If you're *very lucky*, the bootloader you have won't enforce versions and might actually allow downgrading to 1.5, in which case the 1c-root procedure will work.
Click to expand...
Click to collapse
My apologies, only thought of the G1.
lbcoder said:
Your suggestion doesn't make any sense since there are plenty of devices that shipped with 1.5 (i.e. rogers dream), which happen to be quite incompatible with 1.0 firmware. It is therefore impossible to downgrade to rc29.
If you're *very lucky*, the bootloader you have won't enforce versions and might actually allow downgrading to 1.5, in which case the 1c-root procedure will work.
Click to expand...
Click to collapse
Are you saying that I wouldn't be able to root using the "traditional" method?
OolonColuphid said:
Are you saying that I wouldn't be able to root using the "traditional" method?
Click to expand...
Click to collapse
Post your phone info before you ask that.
cigar3tte said:
Post your phone info before you ask that.
Click to expand...
Click to collapse
Sorry. It's a US T-Mobile G1
I would like to know the answer to this too. I was updating to 4.1.999, something went wrong and now im on 1.6 dev phone firmware. Im not sure if i can go back to rc29 or not or if i should even try. Won't going back to RC29 with the new SPL brick my phone?
(Current) Details are
G1 / Dream phone
firmware 1.6
hard SPL
Build: dream_devphone-userdebug 1.6 DRC83 14721 test-keys
Normal recovery console
Thanks
HardSPL won't brick phones, not to the same degree as dangerSPL anyways.
If you have a REAL SPL (i.e. Engineering, or Hard -- can't imagine why anyone would want that though since it doesn't offer any real advantage over Engineering), then there is ABSOLUTELY NO REASON to go flashing nbh's/downgrade to rc29. The reason for this is that these bootloaders do NOT enforce signatures, and DO allow full access to the system. The only reason for going to rc29 is if you have a RECENT VERSION UNHACKED device that is CARRIER BRANDED (and happens to be compatible).
If you have Engineering SPL or similar, then the ONLY thing that nbh's will do is RISK CREATING A BRICK.
Yes, you can brick *any* time you write an NBH, IPL, or SPL (not just the deathspl). Chances are low, but if something goes wrong, its dead.
sprarky said:
I would like to know the answer to this too. I was updating to 4.1.999, something went wrong and now im on 1.6 dev phone firmware. Im not sure if i can go back to rc29 or not or if i should even try. Won't going back to RC29 with the new SPL brick my phone?
(Current) Details are
G1 / Dream phone
firmware 1.6
hard SPL
Build: dream_devphone-userdebug 1.6 DRC83 14721 test-keys
Normal recovery console
Thanks
Click to expand...
Click to collapse
lbcoder said:
If you have a REAL SPL (i.e. Engineering, or Hard -- can't imagine why anyone would want that though since it doesn't offer any real advantage over Engineering), then there is ABSOLUTELY NO REASON to go flashing nbh's/downgrade to rc29. The reason for this is that these bootloaders do NOT enforce signatures, and DO allow full access to the system. The only reason for going to rc29 is if you have a RECENT VERSION UNHACKED device that is CARRIER BRANDED (and happens to be compatible).
If you have Engineering SPL or similar, then the ONLY thing that nbh's will do is RISK CREATING A BRICK.
Yes, you can brick *any* time you write an NBH, IPL, or SPL (not just the deathspl). Chances are low, but if something goes wrong, its dead.
Click to expand...
Click to collapse
OK cool. Thanks for that. That confirms a few things for me.
Now this might seem a little ignorant but how do i get my root back now? I have done several searches but couldn't really find anything that confirms the exact method for this situation.
If there is no reason to go back to RC29 and do that whole process again then whats the other way of doing it?
As i now have the normal recovery console back any attempt to try and flash CM's just results in the phone telling me i cant su (or don't have root)
Thanks again
Sounds like you have acess to fastboot with your spl you could use fastboot to flash cyanogen's or whichever recovery image you choose, then you would be able flash any rom's you would like through recovery
jackslim said:
Sounds like you have acess to fastboot with your spl you could use fastboot to flash cyanogen's or whichever recovery image you choose, then you would be able flash any rom's you would like through recovery
Click to expand...
Click to collapse
Yeah i do! that sounds exactly like what i need to do. You know of a how-to anywhere for doing this?
Cheers
Do you already have fastboot installed on your pc?? If not a simple search of theese forums can yield you instructions on setting up fastboot. Once you have it installed you can open up a terminal and go the directory in which your recovery image is stored and run the command
fastboot flash recovery cm-recovery1.4.img assuming you're using cyanogen's recovery
jackslim said:
Do you already have fastboot installed on your pc?? If not a simple search of theese forums can yield you instructions on setting up fastboot. Once you have it installed you can open up a terminal and go the directory in which your recovery image is stored and run the command
fastboot flash recovery cm-recovery1.4.img assuming you're using cyanogen's recovery
Click to expand...
Click to collapse
Hey,
Thanks for your help. Managed to get it all working they way you described after some searching and a few hours. Thanks again dude.
OolonColuphid - Hope i didn't hijack your thread too badly. Does any of the above information help you out at all? I found it fairly easy to flash the recovery from fastboot then flash back to whatever i want via the recovery console.
Cheers,
Sean
Alright, I've been doing some reading up on rooting and it sounds interesting. I tried following the steps on theUnlockr.com but keep running into issues. Just FYI, I recently upgraded to 1.6 Donut from 1.5 thru a phone update so it is NOT stock in my phone. Please let me know what I need to do (in lamens terms) so I can get this going.
G1/Dream
Firmware 1.6 Donut
Build Number: DRC83
Please let me know what I need to do (in lamens terms) so I can get this going.
ephayzee said:
Alright, I've been doing some reading up on rooting and it sounds interesting. I tried following the steps on theUnlockr.com but keep running into issues. Just FYI, I recently upgraded to 1.6 Donut from 1.5 thru a phone update so it is NOT stock in my phone. Please let me know what I need to do (in lamens terms) so I can get this going.
G1/Dream
Firmware 1.6 Donut
Build Number: DRC83
Please let me know what I need to do (in lamens terms) so I can get this going.
Click to expand...
Click to collapse
You're phone is still considered stock because it has unmodified software on it, even though you have 1.6 it's through the official OTA update whether installed manually or recieved in due time over your network. You can root your phone, pretty much just follow the steps outlined in this guide found on theese forums
http://forum.xda-developers.com/showthread.php?t=442480
jackslim said:
You're phone is still considered stock because it has unmodified software on it, even though you have 1.6 it's through the official OTA update whether installed manually or recieved in due time over your network. You can root your phone, pretty much just follow the steps outlined in this guide found on theese forums
http://forum.xda-developers.com/showthread.php?t=442480
Click to expand...
Click to collapse
Good looking man, thanks!
Does FlashRec still work on donut, or have they patched that exploit?
OolonColuphid said:
Does FlashRec still work on donut, or have they patched that exploit?
Click to expand...
Click to collapse
OMG! can u not read!
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
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
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
i'm relatively new to android, and i wondered if someone could take me through the steps required to take my gt540 from stock 1.6 to stock 2.1, make a backup, and then to install 2.3 on it. what order do things need to be done in? and what is fastboot? is it essential?
i've found a couple of beginners' guides on modaco, but neither seem to go through the whole process so i'm always left with more questions.
i have a carphone warehouse unlocked gt540. as i understand it i can install a cpw+fastboot 2.1 rom, and then install clockwork, back up the system, and then use fastboot to install the new 2.3 rom. is that correct?
any help most welcome, i've been puzzling over this for weeks!
http://androidforums.com/lg-optimus-gt540/276446-cyanogenmod-7-android-2-3-avaliable-gt540.html
use this guide.
but first of all you have to have Andoid SDK, platform-tools, Java JDK to be installed.