Related
I had an incredible amount of trouble rooting my G1 after i got the OTA update. I looked for answers everywhere and there weren't many, and way too many "do a forum search" answers on forums. As if i hadn't tried searching haha.
Luckily i finally figured out how to do it.
The solution is to create the Unlockr's Goldcard. This creates an SD card that gets around the security of your current build.
If you want to skip a lot of steps (1-8) in the Unlockr's method, download the Goldcard Helper from the Market. This gives you the number you need without using adb. If you have a PC you can follow the Unlockr's guide from step 8 on and create your Goldcard.
(edit: from here downgrade to 1.5 and one click root will probably work)
I am assuming that most of you can figure out the rest, since i'm really busy right now, but i want to open a thread to point people in the right direction. If I see people having trouble i'll make a [Guide] when i get some time.
For now, Good Luck, and if you have it, try Super D. You'll feel like that G1 is like new again!
Sent from my HTC Vision using XDA App
Or you could just slap an rc29 .nbh file onto the sdcard, install that, and root as normal.
In theory...that's what everyone on forums keeps saying, but I was really frustrated because it doesn't work...at least it didn't work for me.
Were you ever able to do that successfully from the DMD64 build, or just rc30?
I don't know for sure, but I think a lot of people who were trying really hard to be helpful perhaps had rooted their phones before the last OTA update from T Mobile and therefore didn't realize there was a new problem.
Sent from my HTC Vision using XDA App
There are a couple of different nbh files for matching the particular region of your hardware. This technique most definitely DOES work, but since DREAM was available as ADP, anybody who ever HAD to was, by definition, either retarded, or bought it from someone who was retarded.
Well, I downloaded every findable .nbh file and none were allowed until I put them on a "goldcard."
Yes, I tried everything in the forums to the letter. I think I chiefly had trouble because everyone responded to other people with the same problem saying "it works, you just need to [insert common solution that I already tried]"
But I don't mean offence because I really do know that you are just trying to be helpful.
I just mean that unless you *actually* have rooted a DMD64 build, and you may have FAIK, you might just be adding to the problem...
Sent from my HTC Vision using XDA App
jontornblom said:
Well, I downloaded every findable .nbh file and none were allowed until I put them on a "goldcard."
Yes, I tried everything in the forums to the letter. I think I chiefly had trouble because everyone responded to other people with the same problem saying "it works, you just need to [insert common solution that I already tried]"
But I don't mean offence because I really do know that you are just trying to be helpful.
I just mean that unless you *actually* have rooted a DMD64 build, and you may have FAIK, you might just be adding to the problem...
Click to expand...
Click to collapse
All that a goldcard does is it bypasses the CID check. If you do, in fact, have a tmobile branded phone with OEM firmware, then there is no benefit from a goldcard since the CID check will obviously pass since the hardware's CID matches the nbh's CID. Whatever you did differently that made the "goldcard" work had nothing to do with it being a goldcard.
Ah! You are smart! You actually just cleared up what happened with my phone and why I had so much trouble!
Here is what happened: I had just received the phone (Rogers branded) and was extremely new to Android and rooting. I attempted to root got it all done, running with cm6 etc. I overclocking it, but had made a mistake in one of my CPU speeds, freezing my phone. When I tried to reboot to recovery, I accidentally rebooted to hboot and the the t-mobile nbh was still on my SD and it installed. So I ended up with t-mobile stock 1.5. So now I had to go to work, and just left it with the uptake t-mobile Rom. In the middle of the day I got a "there is an update available" notice. I thought it was for an app (noob, I know) and let it update. That is how I got a Rogers branded phone with t-mobile 1.6 DMD64 software and why I needed the goldcard to re-flash the t-mobile cupcake!
Thanks for persisting with me and helping me figure out the mystery.
Cheers!
Sent from my HTC Vision using XDA App
Thank you sir for finding this solution. I'm in almost the exact same shoes you were in. Noob to Android/rooting. Got this G1 from a friend with 1.6 DMD64 already on there. No root methods have worked so far. Going to try the goldcard sometime today. Will confirm whether it works..
Goldcard was what worked for me! 1-Click method, however, did not work.
Used the text-instructions/downloads from theunlocker.com. I can't post links on XDA yet, so the titles of the articles are "How To Root The HTC G1/Dream" with warnings of how it's an outdated method (but still the only one that works for my DMD64). Then I used "How To Load A Custom Rom On The HTC G1/Dream."
Did not use the videos on those websites...instead used a YouTube video for guidance. Its title is "How To Root Your T-Mobile G1 with Android 1.6 Pt 1."
Successfully running Cyanogen 6 now. Compared to 1.6...Ridiculous UI improvement and a ridiculous battery life decrease.
I tried em all, and gotta say thatv though I wanted android 2.x, Super D was IMHO, without a doubt, the best ROM for the G1.
Sent from my HTC Vision using XDA App
Hi guys,
tomorrow my Desire HD finally arrives, i've been doing some research into rooting ect and would like to ask a few questions .....
1) whats the best root method? i take it unreovked dosent work on the HD, ive read visionary works for permroot, i thought visionary was for the G2 not HD is this correct?
2) whats the diffence between, bootloader s-off and radio s-off ..... on the desire we only have bootloader s-off
3) my desire HD will be orange branded, if it comes with a newer software version , with an unrootable hboot, can i downgrade easlly to an older software version?
4) and finally how do you guys find the multi touch on the HD?, the lack of multi touch is one of the main reasons im upgrading.
thanks for you help
I followed the guide in the Development section to root my DHD and S-OFF, it's pretty easy to follow
I don't know anything about downgrading hboot or that stuff.
The multi-touch on my device is crap:
I shot a video of it. http://www.youtube.com/watch?v=vj5z08CC5AQ
Most times 2 points work, but with 3 and 4 points the sensor is going crazy!
Overloaded said:
I followed the guide in the Development section to root my DHD and S-OFF, it's pretty easy to follow
I don't know anything about downgrading hboot or that stuff.
The multi-touch on my device is crap:
I shot a video of it. http://www.youtube.com/watch?v=vj5z08CC5AQ
Most times 2 points work, but with 3 and 4 points the sensor is going crazy!
Click to expand...
Click to collapse
thats the guide i read, its always daunting rooting a new device isnt it nooooo dont say that the website said the hd support 4 point multi touch aslong as you dont get the axis flipping and it supports 2 touches though i'll be happy
if you are wanting to root your desire HD first check what firmware is already installed if its 1.72.405.3 this can't be rooted yet but if its still has older firmware 1.32.405.3 you are fine and you can root with Visionaryr14. so don't update your phone(if you have older firmware) to any new firmware until you are radio s-off.
if you do have 1.72.405.3 firmware you can now downgrade it to older firmware read thread below
http://forum.xda-developers.com/showthread.php?t=905003
but you will need installed on pc htc sync drivers which you can download from HTC site also need android sdk tools (need adb) which can be found here http://developer.android.com/sdk/index.html need
also been branded you will needed to make a goldcard on your sdcard to be able to downgrade but in the thread above the is a link to show how its done.
just hope you have older firmware on phone.
sorry matey didn't really read you post, different between the s-off's radio s-off is were its sercurity premanently off and eng s-off is were the h-boot has been patch telling the radio the sercurity is off.
If it comes with 1.72 or 1.75 firmware root I'd not availiable....Yet!
Sent from my Desire HD using XDA App
cattleprod said:
if you are wanting to root your desire HD first check what firmware is already installed if its 1.72.405.3 this can't be rooted yet but if its still has older firmware 1.32.405.3 you are fine and you can root with Visionaryr14. so don't update your phone(if you have older firmware) to any new firmware until you are radio s-off.
if you do have 1.72.405.3 firmware you can now downgrade it to older firmware read thread below
http://forum.xda-developers.com/showthread.php?t=905003
but you will need installed on pc htc sync drivers which you can download from HTC site also need android sdk tools (need adb) which can be found here http://developer.android.com/sdk/index.html need
also been branded you will needed to make a goldcard on your sdcard to be able to downgrade but in the thread above the is a link to show how its done.
just hope you have older firmware on phone.
sorry matey didn't really read you post, different between the s-off's radio s-off is were its sercurity premanently off and eng s-off is were the h-boot has been patch telling the radio the sercurity is off.
Click to expand...
Click to collapse
nickhammond121 said:
If it comes with 1.72 or 1.75 firmware root I'd not availiable....Yet!
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
thanks guys, i'll just have to wait till tomorrow to see what software version comes with my HD, i hope i wont have too much trouble rooting or downgrading tho, i have the htc drivers installed and im familiar with adb, thanks for your help
you should have no problems been able to downgrade then. you may want to use this ruu http://xdafil.es/DesireHD/RUU/RUU_A....140e_26.03.02.26_M_release_157531_signed.exe
as your PM98IMG.zip as it orange uk so may not need to make a goldcard.
Just to keep your hopes up i only got mine on friday it had the older firmware on.
i soon s-off and eng -s off, now i can not stop flashing roms finding the one i like best. i would say thou if you plan to flash up to the 1.72 rom dont flash a new custom kernel...yet
Thamks for all your help guys, i got my DHD earlier today, and it only took me 10 minutes to root and s-off it came with software version 1.40, i used visionary to root it, then used the one click radio s-off tool to s-off now im gunna download rom manager and flash cwm
Nice no having to downgrade enjoy
Swyped using a misguided desire HD with telepathy...
Hi
My dhd manges four multi touches with no problems.
Sent from my Desire HD using Tapatalk
First I made the mistake of using the HTC method for unlocking my bootloader, I didnt come here 1st & getting my phone downgraded afterwards proved to be a difficult task, as I tried the simplest method many times, and I just couldnt get it to flash via hboot. But I finally got a stock rooted 2.2.1 rom on here, & I followed the Ultimate s-off guide, and everything appeared to go well, but s-on remained. Terminal said it applied everything without any errors. I have heard that it is difficult to remove the **UNLOCKED** and get s-off after doing things the HTC way. I am pretty good at following guides, but I am stuck at the moment. Any help would be appreciated. As I said the bootloader is unlocked and I have a 2.2.1 rooted rom on here. Whats the best way to go from here? Thanks
Sent from my HTC Glacier using Tapatalk
I would try this http://forum.xda-developers.com/showthread.php?p=21563546
Sent from my HTC Glacier using xda premium
Man I am so excited! I sat back and read, I listened to others problems until I got a better understanding of what's going on. I managed to relock my bootloader, do a true root, s-off, & installed engineering hboot, and I feel lucky because I have the "bad chip" and I was so nervous, but I now have it done the right way! Thanks for any help that anyone has given.
the situation
i have a My touch 4g that i some how by the grace of God have rooted and unlocked the bootloader and i downgraded to 2.2.1
the problem
i have tried to flash several roms but only one stuck and flashed correctly which
is called glacier cream 7.1 CM based 4.0.3 but to even get that to flash i had to
flash the rom then flash the recovery img through adb. so now this rom has no camera and wifi wont work a new rom has come out and when i try to flash it i get this error and cant get passed it
ClockworkMod Recovery v5.0.2.7
--Installing: /sdcard/IcecoldSandwich-For_MT4G_
5.5.AOKP-singed.zip
Finding update package...
Opening update package...
Installing update...
assert failed:getprop("ro.product.device")=="
glacier" || getprop(ro.build.product") =="glac
ier
E:Error in /sdcard/IceColdSandwich-For_MT4G_5.5.
AOKP-singed.zip
(status 7)
Installation aborted.
if anyone can please tell me what i can do or if there is anything i can do
im a noob i only know a lil adb lingo and barely got this thing rooted and downgraded also my bootloader specs are this
***UNLOCKED***
GLACIER PVT SHIP S-ON
HBOOT-0.89.007
MICROP-0429
RADIO-26.13.04.19_M
eMMC-boot
Dec 13 2011,21:07:39
also i have CWMR installed
if someone could help me please i would be very greatful
thank you
First your S-ON so u have to do it using Adb
Second the file you downloading probably didn't finish downloading or is corrupt try downloading again.
Third: Your phone is ok the camera and wifi are known not to work for that ROM you flashed.
Sent from my HTC Glacier using xda premium
...Awesome... said:
First your S-ON so u have to do it using Adb
Second the file you downloading probably didn't finish downloading or is corrupt try downloading again.
Third: Your phone is ok the camera and wifi are known not to work for that ROM you flashed.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
thanks for the reply but how do you flash a rom through adb ?
and there is no way to get my s-off ?
No, because you're unlocked through HTCDev tool.
You need to relock and downgrade to have S-OFF.
And your problem is - since you're unlocked by HTCDev, you need to flash kernels manually, using fastboot. Google it.
And your other problem is posting questions in General section instead of Q&A, and giving your thread a crappy title to add to it.
You said unlocked bootloader? Is that via HTC?
Sent from my MyTouch 4G using xda premium
jjbadd385 said:
You said unlocked bootloader? Is that via HTC?
Sent from my MyTouch 4G using xda premium
Click to expand...
Click to collapse
yes i unlocked through the HTC.dev site i thought that was the only way until i found this other thread on how to do it manually
Jack_R1 said:
No, because you're unlocked through HTCDev tool.
You need to relock and downgrade to have S-OFF.
And your problem is - since you're unlocked by HTCDev, you need to flash kernels manually, using fastboot. Google it.
And your other problem is posting questions in General section instead of Q&A, and giving your thread a crappy title to add to it.
Click to expand...
Click to collapse
OK thanks for the help,thought this is were you post for help .....sorry about that
and as far as my title well that's what i need so that's what i asked for sorry if it was to crappy
so if a Moderator could please move this to the Q&A section that would be great and sorry about the post in wrong place like i said im still new to this .
and i did downgrade to 2.2.1 from 2.3.4 unless i did something wrong there ?
Maybe go back to stock and re-root? Lots of info here
Yes, you did wrong. If you have HBOOT 0.89.0007 - means you have the most updated HBOOT, and if you'd downgrade properly - you'd have HBOOT 0.86.0000.
You can still attempt to run gfree, but I doubt it'll do you any good.
You have 2 choices:
1) Stick with current setup and flash kernels from fastboot each time, like I said.
2) Modify misc_version again, relock bootloader, run "dowgrade" again, temp-root with Visionary and perm-root with gfree, following one of the many guides.
Your ROM won't flash, because it assumes something being written in the special file that describes the device as Glacier, but this assumption fails (most likely because the build you flashed previously messes something up in this file).
The other ROMs don't work, because you're not flashing the kernel.
Do some reading, please.
I can tell you this from experience, but I don't suggest you do anything until you calm down, gather your thoughts, and read some posts on this until it makes sense to you.
I had unlocked my bootloader via HTC. Then I realized it wasn't the best way, so I started doing this & that and having all sorts of issues. Only when you are ready, you need to relock your bootloader and then follow the very detailed guides on here to root and install the engineering hboot. I couldn't get s-off or downgrade to 2.2.1 until I relocked my bootloader. I don't know if that is the case for everyone, I only know I failed at every attempt to downgrade, until I relocked it. But please, be patient and try to read and understand a little before you attempt anything further.
Sent from my Black Ice'd Glacier using xda premium
Hey there!!!
So after a chat via pm with a fellow xda member, we found someone who did what most of us though was impossible, achieve an S-Off -able state after upgrading to the .11 firmware update. The user who achieved this has unfortunately been banned from the xda forums for reasons I don't know of, so you'll find a link to his page and tutorial in the bottom of the OP. I haven't personally tried this method all the way through yet, but it has been confirmed to work by a couple of the people over on his forum.
Apparently all you have to do is:
-Backup whatever data is on your phone
-Unlock your bootloader
-Flash a custom recovery(I prefer TWRP)
-Do a full system wipe(This WILL ERASE EVERYTHING on your phone, including your OS).
-Flash a "stock" 1.27.531.7 Rom (I know there's one floating somewhere in the dev forum section) OR restore a .7 Nandroid backup
-Wipe Cache and Dalvik
-Flash kernel
-Reboot
- Enable USB Debugging and make sure your battery is over 30%( I'd say 50% for good measure).
-Run the modified 1.27.531.8 RUU(Found in the link in the OP)
- Let it go through the motions (multiple reboots)
-BOOM. There you go. If all goes well you should be running the official(kind of) stock, S-Off capable, 1.27.531.8 Firmware, with the unmodified 1.44 hboot, meaning Revone AND Moonshine should both work, whichever you prefer.
If I forgot any steps I apologize, I'm typing this on the go, completely from memory. But if you're attempting this, I'm going to assume you've flashed a custom Rom before and know how to do it without bricking your phone. Good luck everyone!!! Feel free to post successes and failures for the rest of us!
Tutorial and Modified RUU:
link removed
Sent from my HTC One using xda app-developers app
ALL CRED FOR THIS DISCOVERY
GOES TO:
xboarder56 for the RUU :thumbup::thumbup::thumbup:
bloodbond3 For sharing this. :thumbup::thumbup:
MUCH THANKS MATES
Sent from my HTC One using xda app-developers app
1.54
But....this is not for 1.54 users, right?
Im on hboot 1.54 s-on ... Can s-off be axhieved following this tutorial
?
Nightf0x_007 said:
Im on hboot 1.54 s-on ... Can s-off be axhieved following this tutorial
Click to expand...
Click to collapse
I have now seen a post with this explanation:
No, this is for the US T-Mobile edition and WILL NOT assist in unlocking the 1.54 HBoot. Maybe the OP should add some backstory:
T-Mobile released an update about 2 months ago that changed the version incrementally. In doing so they updated the HBoot, but kept it on 1.44, and patched the hole used by Renovate and Moonshine. This mod tricks your US T-mobile phone into downgrading through RUU (since the HBoot version never changed it is working) and allowing S-Off... that being said dont be a dummy and RUU then take the update after the first boot lol.
This is a great tool, I am DL'ing it just in case, i already had mine done prior to the update and am running a GPE Converted phone now.
That being said I HIGHLY recommend doing this prior to taking the upcoming 4.2 or 4.3 update, They will be updating to the as-of now locked down 1.54 HBoot. At that time this mod should no longer work as downgrading your HBoot is only available while S-Off.
Maichel said:
I have now seen a post with this explanation:
No, this is for the US T-Mobile edition and WILL NOT assist in unlocking the 1.54 HBoot. Maybe the OP should add some backstory:
T-Mobile released an update about 2 months ago that changed the version incrementally. In doing so they updated the HBoot, but kept it on 1.44, and patched the hole used by Renovate and Moonshine. This mod tricks your US T-mobile phone into downgrading through RUU (since the HBoot version never changed it is working) and allowing S-Off... that being said dont be a dummy and RUU then take the update after the first boot lol.
This is a great tool, I am DL'ing it just in case, i already had mine done prior to the update and am running a GPE Converted phone now.
That being said I HIGHLY recommend doing this prior to taking the upcoming 4.2 or 4.3 update, They will be updating to the as-of now locked down 1.54 HBoot. At that time this mod should no longer work as downgrading your HBoot is only available while S-Off.
Click to expand...
Click to collapse
This is a post inception.... I made the post that was quoted that I am now quoting in my post......
Sent from my Nexus 10 using Tapatalk 4
This method has been floating around for s while now, since the update came out. But none the less, great guide op.
Sent from my HTC One using XDA Premium 4 mobile app
So wait I'm confused, lol did I not add enough backstory? Or was that from another thread?
Sent from my HTC One using xda app-developers app
EDIT: unconfused now. Mah bad
In simpler terms, a little less confusing, what Maichel is saying is that the RUU contains the unmodified 1.44 hboot, but still 1.44, so "technically" speaking, you're not downgrading your hboot at all.
Sent from my HTC One using xda app-developers app
Links to banned dev. Closed, link removed