Ok im going to return my g1 because it goes straight to recovery mode. They said they were going to send me another one but the problem is that i got JFv1.41. I cant go to boot mode to go back to RC29. Will I get in trouble if i send it in with JFv1.41?
Please help...
Probably wont get a replacement. If it goes into recovery then turn phone off, pull sd card, put jf's rc33 update on sd card, put sd card back in g1 and run update to get it going again.
If i put RC33 on it would i get a replacement now with RC33?
jgu71424 said:
If i put RC33 on it would i get a replacement now with RC33?
Click to expand...
Click to collapse
First things first, you need to get g1 going again. Once you get it running again the follow this link on downgrading to factory. You have to get it going, flash back to rc29, then if you choose you can flash rc33 official rom but thats up to you. The important thing is to get it back to original state though. Then you can return it once you are all done setting it back to the way you got it.
http://forum.xda-developers.com/showthread.php?t=442480
Ok what if i cant get it pass recovery do you think tmobile will check. Will they give me a fine for hacking it.
jgu71424 said:
Ok what if i cant get it pass recovery do you think tmobile will check. Will they give me a fine for hacking it.
Click to expand...
Click to collapse
Find out if you can first, run update again.
Ok but what if i cant will i get a fine do you know?
And thanks im going to try RC33 see if it works.
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!
I have a T-Mobile MyTouch 3g 1.2 and I have tried to unroot it and load the original rom back on it and for the life of me I can't. It updates the sappimg just fine in hboot until it gets to system and then I get some sort of error and have to reroot it and flash CM6.1 RC1 back on. I have tried running Universal Androot to unroot it with no success. Well, today I downloaded this nice little app from the Market called z4root by RyanZA(I think that's his name) and low and behold it actually unrooted my phone. I confirmed this by rebooting, opening rom manager app and it told me I need root to use it. I used z4root to reroot with no problems. My question is how would I flash the original T-mobile rom if I use this app to unroot my phone. Could I use the RUU.exe or is there a better way? I really want to go back to stock when the OTA for this phone comes out. I don't need to right now, but I just want to know how and try it so I know I can do it when the time comes. Would it be best to use a goldcard after unrooting to load sappimg? If anyone has any ideas or experience doing this please advise and I appreciate everyone here. This forum is great. I am a noob to Android devices and have been coming here about every day to read, read, read. I have learned so much here. Some of it is still gibberish to me, but I am learning. Thanks all!
When not flash a 32A 'port' of the mytouch 1.1 froyo ROM? It will perform exactly the same as any official update.
I was thinking about doing that, but after trying to go back to stock and failing I have kind of made it a challenge to get this done and figure it out. I guess since no one knows what to do I will just keep trying blind and keep reading. Thanks all and have a great day.
Hi,
I updated my Magic Vodafone to official froyo 2.2.1, but now I can't obtain root permission, because I rooted the phone with androot when magic had 1.6 on and before the update I not unrooted.
Now all programs like androot, one click root, z4root, can't root or unroot. Superuser is present but doesn't work and I don't know how to remove or make work.
Can anyone do this?
Or, can I downgrade to 1.6? if yes, how?
Thank you all.
EDIT: I used SuperOneClick
I had the same problem.
I was rooted on 1.6 and got the OTA update. I did a hard reset on the phone and ran superoneclick. I had to run it a few times before I got root again. main problem was it was on a loop so turning on and off the debug mode eventually worked.
creative0100 said:
I had the same problem.
I was rooted on 1.6 and got the OTA update. I did a hard reset on the phone and ran superoneclick. I had to run it a few times before I got root again. main problem was it was on a loop so turning on and off the debug mode eventually worked.
Click to expand...
Click to collapse
superoneclick solves the root problem. But how do i get to the donut rom?
Tried adding a recovery but it does not stick with the 2.2.1, it reverts to the default one.
Please add the steps to go to the 1.6 donut.
Thanks
htcmagic said:
superoneclick solves the root problem. But how do i get to the donut rom?
Tried adding a recovery but it does not stick with the 2.2.1, it reverts to the default one.
Please add the steps to go to the 1.6 donut.
Thanks
Click to expand...
Click to collapse
unfortunately froyo deletes custom recovery, anyone a solution?
stephenking said:
unfortunately froyo deletes custom recovery, anyone a solution?
Click to expand...
Click to collapse
On the first page.
is there any way to reset firmware?
There are a number of ways, through phone settings,booting into recovery and if you're rooted via RUU. Why would you want to reset? It'll delete all phone storage data.
i need to go back android 2.1 and root..
How can i do it via phone settings?
If i go to recovery it's shows me a phone and a red triangle with exclamation point.. what is recovery do?
ty!
If you are on 2.2, there is nothing you can do.
Gosh your late on rooting.. v2.2 doesnt support rooting, check : http://forum.xda-developers.com/showthread.php?t=899892
I thought you could get temp root on 2.2 and this is why you can then downgrade to 2.1, even though the HBOOT cannot be downgraded as of yet.
http://forum.xda-developers.com/showthread.php?t=921752
n!k said:
I thought you could get temp root on 2.2 and this is why you can then downgrade to 2.1, even though the HBOOT cannot be downgraded as of yet.
http://forum.xda-developers.com/showthread.php?t=921752
Click to expand...
Click to collapse
Yes, but that is pointless as of now, unless you *desperately* want Eclair over official Froyo, in which case, by all means, the method is valid.