Using this method:
http://forum.xda-developers.com/showthread.php?t=858996
I'm on step 6, but when I click "temp root now" the screen just stays black and doesn't temp root at all. Any ideas how to fix this?
bballcat03 said:
Using this method:
http://forum.xda-developers.com/showthread.php?t=858996
I'm on step 6, but when I click "temp root now" the screen just stays black and doesn't temp root at all. Any ideas how to fix this?
Click to expand...
Click to collapse
What firmware are you on, gingerbread or froyo. If you are on 2.3.4, you can't gain temp root using gfree. You have to downgrade to 2.2.1 or whatever...
If you ARE on FroYo, make sure usb debugging is enabled and reboot between every attempt.
Sent from my HTC Mytouch 4G using XDA App
Please check your OS version in "Settings"/"About phone".
If you're not on 2.2.1, but on 2.3.4 - you'll need to downgrade before attempting the rooting guide. Read Glacier Wiki, section "Root", subsection "Gingerbread".
This works for 2.2.4 If you have Visionary installed now uninstall it.
Go here http://forum.xda-developers.com/showthread.php?t=1424023
stop after flashgc..... DO NOT DO THE STEP AFTER THAT. YOU WILL LOSE TEMP ROOT.
After you get the goldcard go here http://forum.xda-developers.com/showthread.php?t=858996
Follow this as if you are perm rooted DO NOT INSTALL VISIONARY.
This will get you all you need for s-off
You will need to also install the engineering hboot.
From there a custom recovery,,,,,,http://forum.xda-developers.com/showthread.php?t=756918 Start at step 7
GOOD LUCK !!!!
---------- Post added at 07:16 PM ---------- Previous post was at 07:09 PM ----------
Look for and download Coredroid rom, it is the ONLY one I have found that will flush the 2.2.4 out of the phone........you didnt state if you HTC dev unlocked. if you are you will NOT be able to go to the engineering hboot, you WILL be able to get s-off with the guide I gave you above.
You do not need to remain on Coredroid, try it, but flash whatever you want after the boot-up. Once it loads in the first time, it pushes all of the stock rom out.
First, it's 2.3.4, not 2.2.4. There is no Android 2.2.4 in existence on any phone.
Second, there's a proper guide for downgrading, with enough details - and you're pointing to a mess that doesn't work, unless you're unlocked by HTCDev tool.
,,,,,,now what
First, it's 2.3.4, not 2.2.4. There is no Android 2.2.4 in existence on any phone.
Second, there's a proper guide for downgrading, with enough details - and you're pointing to a mess that doesn't work, unless you're unlocked by HTCDev tool.
Mistake on my part for the version....bad keystroke....unintentional
The "mess" as you put it, does work and works like a charm. Its what I had to do on my phone, STEP BY AGONIZING STEP until I could get back in.
---------- Post added at 06:06 PM ---------- Previous post was at 05:58 PM ----------
Here is why I went down that road........ HTC dev unlock unrooted gives you this
$ chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/fre3vo
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
Locating access point...
This device does not support this exploit.
This device does not support this exploit.
The exploit has failed.
$
Check it for yourself, I only spent 16 hours trying to crack my phone open so I guess I know nothing since I am rooted S-off and flashing roms in recovery......
furydude39 said:
First, it's 2.3.4, not 2.2.4. There is no Android 2.2.4 in existence on any phone.
Second, there's a proper guide for downgrading, with enough details - and you're pointing to a mess that doesn't work, unless you're unlocked by HTCDev tool.
Mistake on my part for the version....bad keystroke....unintentional
The "mess" as you put it, does work and works like a charm. Its what I had to do on my phone, STEP BY AGONIZING STEP until I could get back in.
---------- Post added at 06:06 PM ---------- Previous post was at 05:58 PM ----------
Here is why I went down that road........ HTC dev unlock unrooted gives you this
$ chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/fre3vo
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
Locating access point...
This device does not support this exploit.
This device does not support this exploit.
The exploit has failed.
$
Check it for yourself, I only spent 16 hours trying to crack my phone open so I guess I know nothing since I am rooted S-off and flashing roms in recovery......
Click to expand...
Click to collapse
I would honestly not question Jackr1's knowledge. He definatly knows what hes talking about and knows alot more about these phones that the average rom flasher.
After using HTC dev, you don't need all that. You only need to go to the bootloader, which is now unlocked, and write "fastboot flash recovery recovery-of-your-choice.img", and from there you're done - you have a custom recovery and can do whatever you want to do (well, almost - because you need to flash a kernel manually for each ROM you flash, it won't work from recovery, and it didn't for you - that's why some ROMs worked for you and some didn't). As I wrote, no need for the mess.
The vast majority of users don't use HTC dev unlock, and hopefully won't use it. Today I happened to flash friend's Sensation, and discovered a bootloader after HTC dev tool - and indeed, even after achieving full S-OFF and changing them all over the place (flashed 2 different bootloaders to test), I couldn't make this thing flash a kernel from recovery, had to do it by fastboot. It's extremely annoying for serious flashers. I understand why HTC chose to go this way - they're allowing to flash, but prevent at least some noob crackflashers from hosing those devices by making the flashing process more demanding.
I hope you understand I know what I'm talking about, and I'm not writing for the sake of writing.
Just to be clear, I definitely am not questioning your knowledge or experience. I am telling you what I had to do to get root on my phone, none of the conventional wisdom seemed to work and I had to create a new path.
I will point out that the bootloader from HTC dev for the unlock procedure, I was not able to write over it.
Currently its locked, will not unlock, but I do have s off, and with that it was impossible to flash from bootloader. I kept getting "remote not allowed".
1) I agree with everything you said
2) For whatever reason, it didnt work for me that way, I couldnt format in recovery and have it stick, it just wasnt happening.
3) The only thing that worked, is what I posted. It is a long and drawn out process, but maybe someone can look at it and fix the mess created when someone goes the route of the dev unlock.
Jack_R1, I apologize for the way I sounded.
I was FINALLY able to reflash the hboot-eng.img into my phone. what a pain it was to get it back to that point.
Before all I would get was remote not allowed, kept plugging and got it in.
Beware - even with engineering bootloader, your kernels might not flash from recovery. I didn't have the engineering bootloader to try on Sensation, only hacked stock ones, so I can't say anything certain about it. If you want and have time, you can try to take a nandroid backup and flash completely another ROM - something on the lines of flashing ICS ROM if you're currently on Gingerbread, or vise versa (that will definitely cause the kernel to panic and won't load anything) - and see if it boots without the need to override the kernel manually from fastboot.
No need to apologize. Someone needs to sit and write a guide for HTC-Dev users, that will be simple enough to use. I just might not have enough time for it, though I can try. And I'll need someone to verify the procedure, too.
I am able to flash a new rom, back-up and restore from recovery.
Currently I am on the Ext4 recovery as that loaded in with the Coredroid rom when I flashed it.
So far I like it and see no reason to change it........ do you have any negatives on it ?
No, I don't. Since you flashed engineering bootloader after unlocking with HTC-Dev, I just suggested you to check something for the community It's your decision, to do or not to do it.
In any case, that's the problem. You don't know if you're able to restore and/or flash a new ROM from recovery, because you didn't flash any ROM that wouldn't boot with HTC stock kernel, which is present on the device, neither before nor after changing to Eng HBOOT. So you THINK you can flash ROMs and restore backups - but it might not be the case, not quite.
Here's info on on the way HTC-dev unlock affects you:
http://rootzwiki.com/topic/13695-a-couple-things-about-htcdev-unlock/
As you can see, once you have HTC-unlocked your bootloader, you can fastboot flash recovery and anything but HBOOT itself (need S-OFF for that), and you can't flash boot.img (kernel) from recovery. This was the case with you, until you moved to Eng HBOOT. Now you're in an unknown territory - flashing might work and might not. I didn't find prior cases reported, positive or negative.
Virtuous Quattro Beta R1 Glacier Flashed in recovery and booted up no issues
Sorry for the delay.....just a little busy
Ok, it means that Eng HBOOT works around the limitation of Ship HBOOTs when unlocked by HTC-Dev tool, allowing full functionality. I believe you're the first one to confirm that. Many thanks!
Glad I could help!!!
and now back to GB
Related
Need some help from the geniuses. And though it'll be clear I am not one of these geniuses, I wanted to mention this is my 5th Android phone and I've perma-rooted all of the others and flashed ROMs hundreds of times. I've also searched for a resolution to this with no luck. Lastly, I know some will argue this fits in General or Q&A, but this problem has been reported by a number of folks across phone lines without resolution and I think it is going to require real dev collaboration to solve and possibly help prevent this in the future, so I'm posting it in Dev.
Now, on to the problem....
Bought a MT4G yesterday and came home to root. Followed some of the great guides here to use Visionary R14 to get temproot and then "permaroot". I was getting S-OFF, but my root didn't seem to be lasting beyond reboot, maybe this was because I was showing 2.2 and not the 2.2.1 OTA update. So, I continued with the permaroot guide here: http://forum.xda-developers.com/showthread.php?t=834225 and all seemed to be going well. My root was surviving reboot and I had S-OFF, but the LAST STEP is to reboot again and check S-flag in HBOOT and that's where I went wrong. I'd left the PD15IMG file on the SD root and when it rebooted I guess I was holding the volume rocker up unintentionally, so it flashed this file without me being able to stop it. I rebooted and still showed S-OFF and 2.2.1, but now when I entered terminal emulator and type "su" I get an error about the user being unknown (doing a "ls su" in /system/bin shows su to be there, btw). Obviously the file screwed up root, and reverted my recovery from Clockworkmod to stock. From there I thought I'd reflash the OTA update.zip but I get an "invalid operation" error.
So I probably should have asked for help then, but I've been trying to follow downgrade guides and redo the root procedures but no joy, usually because they require root to initiate the downgrade (to flash a recovery and do a nandroid restore or to execute some steps of the script). I can get a # prompt when I run the rage scripts, but it appears to be losing root when I reboot. One attempt turned S-ON back on as well. My searching turned up a number of other users who have obviously had this problem with various android phones, and the only one to report successfully fixing flashed a non-root update.zip and did some sort of fixes to busybox.
In summary, I can't return the phone to T-mo because I bought it from an associate at work, and I appear to be stuck between root and non-root without any options that are clear to me to resolve the situation. I am somewhat familiar with adb, fastboot flashing, etc., so if someone can just help me fix su/busybox or somehow flash this back to stock so I can start over or something I would be HUGELY appreciative.
vettejock99 said:
Need some help from the geniuses. And though it'll be clear I am not one of these geniuses, I wanted to mention this is my 5th Android phone and I've perma-rooted all of the others and flashed ROMs hundreds of times. I've also searched for a resolution to this with no luck. Lastly, I know some will argue this fits in General or Q&A, but this problem has been reported by a number of folks across phone lines without resolution and I think it is going to require real dev collaboration to solve and possibly help prevent this in the future, so I'm posting it in Dev.
Now, on to the problem....
Bought a MT4G yesterday and came home to root. Followed some of the great guides here to use Visionary R14 to get temproot and then "permaroot". I was getting S-OFF, but my root didn't seem to be lasting beyond reboot, maybe this was because I was showing 2.2 and not the 2.2.1 OTA update. So, I continued with the permaroot guide here: http://forum.xda-developers.com/showthread.php?t=834225 and all seemed to be going well. My root was surviving reboot and I had S-OFF, but the LAST STEP is to reboot again and check S-flag in HBOOT and that's where I went wrong. I'd left the PD15IMG file on the SD root and when it rebooted I guess I was holding the volume rocker up unintentionally, so it flashed this file without me being able to stop it. I rebooted and still showed S-OFF and 2.2.1, but now when I entered terminal emulator and type "su" I get an error about the user being unknown (doing a "ls su" in /system/bin shows su to be there, btw). Obviously the file screwed up root, and reverted my recovery from Clockworkmod to stock. From there I thought I'd reflash the OTA update.zip but I get an "invalid operation" error.
So I probably should have asked for help then, but I've been trying to follow downgrade guides and redo the root procedures but no joy, usually because they require root to initiate the downgrade (to flash a recovery and do a nandroid restore or to execute some steps of the script). I can get a # prompt when I run the rage scripts, but it appears to be losing root when I reboot. One attempt turned S-ON back on as well. My searching turned up a number of other users who have obviously had this problem with various android phones, and the only one to report successfully fixing flashed a non-root update.zip and did some sort of fixes to busybox.
In summary, I can't return the phone to T-mo because I bought it from an associate at work, and I appear to be stuck between root and non-root without any options that are clear to me to resolve the situation. I am somewhat familiar with adb, fastboot flashing, etc., so if someone can just help me fix su/busybox or somehow flash this back to stock so I can start over or something I would be HUGELY appreciative.
Click to expand...
Click to collapse
Try the alternative method in my guide with rage instead of visionary and see if that helps. One thing is does is reinstall su and busybox. Also, make sure that you have deleted the PD15IMG.zip from your sdcard so that this doesn't happen again.
Hey! i had the same problem and all i had to do was re-flash the ROM and ive been fine ever since!
just either use the stock rom in the downgrading post, or flash one of the new ones i.e. icedglacier or Gorillas's. iceglaciers seems to be pretty functional right now gorillas is awesome just has a few kinks he's working on
vettejock99 said:
In summary, I can't return the phone to T-mo because I bought it from an associate at work, and I appear to be stuck between root and non-root without any options that are clear to me to resolve the situation. I am somewhat familiar with adb, fastboot flashing, etc., so if someone can just help me fix su/busybox or somehow flash this back to stock so I can start over or something I would be HUGELY appreciative.
Click to expand...
Click to collapse
try this (you should be s-off) and assuming you have busybox already installed.
run rage to get su in your terminal then run the following command in the terminal
busybox mount -o remount,rw /system
busybox chown 0 /system/bin/su
busybox chmod 4755 /system/su
install the superuser.apk if it's not already installed
make sure everything is working by opening a adb shell and typing "su" to verify.
use your phone normally and try rebooting after a few hours. hopefully the fs cache flushed and root is fixed permanently.
mrpanic7 said:
Hey! i had the same problem and all i had to do was re-flash the ROM and ive been fine ever since!
Click to expand...
Click to collapse
Okay, first things first - guess I have to try to see if I can even get S-OFF again or if I've completely screwed myself.
Going to try the alt root method, but I think I have been and it wasn't working. So unless me being tired at 1am was the cause, I may need some more help. Thanks.
Okay, followed the s-off guide, and ran the busybox commands posted above, and I am back to S-OFF and now I get "permission denied" instead of "unknown user root". I think this is progress, but still can't flash because I don't have root. I noticed opening Superuser keeps FC'ing...
Please post questions in Q&A section.
just follow this guide here, which you are already familiar with. it's for temp root using rage. but since your phone has the eng hboot with s-off it should become permanent once the FS flushes out to disk (flash)
http://forum.xda-developers.com/showthread.php?t=797042
follow the guide for root and mainly to get the su files installed just in case your's didn't instal properly prior. when you are done just type "sync" multiple times in your terminal
wait a while an hour or so. then reboot to verify that it's permanent.
Same thing happened to me with the unknown root user. What finally fixed it for me, was redoing the adb commands that put those files on your device so you could use rage. Once it re put the files on my phone, I did the rage commands again and it worked
Sent from my HTC Glacier using XDA App
Thanks, everyone! I am working again, and I cannot tell you how much I appreciate the help. I was THIS CLOSE to giving up on this phone.
Thanks again.
Mark
Nothing happens when I click "attempt perm root"...absolutely nothing. What the F is going on?
bballcat03 said:
Nothing happens when I click "attempt perm root"...absolutely nothing. What the F is going on?
Click to expand...
Click to collapse
You have to follow steps to unlock the bootloader (achieving S-off) before perm root will stick. Read the thread on achieving S-off. Don't do anything you don't fully understand, so read a lot. Afaik visionary does not perm root with one click without first having an unlocked bootloader.
EDIT: Read the resource bible. It's a sticky in the dev forum.
Swyped on my rooted MyTouch4G
I have s-off with 0.85.2007...everything works like a charm until I get to the permroot part...nothing happens when I hit it.
bballcat03 said:
I have s-off with 0.85.2007...everything works like a charm until I get to the permroot part...nothing happens when I hit it.
Click to expand...
Click to collapse
If you have s-off and you have the eng 2007 bootloader, you're rooted. Make sure you have the superuser app installed to your phone. If not, you can get it from the market. You need it to gain root privileges in apps. If you have superuser you can test root by opening terminal emulator. Type su and hit enter. If you get a root request confirm it. The $ symbol should change to #.
You shouldn't need visionary anymore. Once you confirm root, uninstall it.
Swyped on my rooted MyTouch4G
But without doing "permroot" in visionary, it's not permanent, correct? Cause I want it permanent, not temp.
Yes I have superuser installed.
bballcat03 said:
But without doing "permroot" in visionary, it's not permanent, correct? Cause I want it permanent, not temp.
Yes I have superuser installed.
Click to expand...
Click to collapse
Try what I said with terminal. If you type su and hit enter, you should see a #. If you do, congrats. Reboot and test terminal su command to see if your root sticks. Visionary won't tell you if you're rooted.
Swyped on my rooted MyTouch4G
Ok I redid everything again (without doing "attempt permroot") and did what you said and the $ changed to #...however, when I first did the temp root, and then went into terminal to do the:
- su
- "cd /data/local" etc....it changed from a $ to a # as well then...before I got to the end and rebooted.
So I am permrooted then and can change roms? Why didn't I have to do "attempt permroot" in visionary?
The unlocked.com
Precise...simple..quick...easy...works...
Hope it helps!
Sent from my HTC Glacier using XDA App
h0wlings0nnets said:
The unlocked.com
Precise...simple..quick...easy...works...
Hope it helps!
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Uh, that's not a website!
Like I said, you were already rooted. When you attempt perm root with Visionary, I don't think it tells you anything. Just make sure your root sticks by rebooting and then typing su in terminal. If you get the #, you can uninstall Visionary.
As for flashing ROMs: You need to flash a new recovery in order to make Nandroid backups and flash ROMs. Clockwork ROM Manager from the market will allow you to flash Clockwork Recovery on your phone. I don't know how much experience you have with flashing ROMs in general, but if you're a novice in any way I wouldn't start changing your system just yet. Read the resource bible, lurk the developer threads, and get a firm grasp on what you are doing. Get familiar with ADB and Fastboot. Be totally confident in your knowledge. You can still brick your phone or at the very least give yourself an unneeded heart attack and hours of troubleshooting sh!t.
Resource Bible
Good luck and congrats on root!
Yeah I am looking at the "how to flash a rom for noobs" thread out of the resource bible...it says "In the hboot menu select recovery and then the phone will restart. You will get a phone with yellow triangle error."
I select recovery and another screen came up regarding the clockwork with a bunch of options, it didn't restart. And when I selected the option that said "reboot" it did, but I didn't get a yellow triangle error
Any ideas there?
Sounds to me you already have Clockwork Recovery installed. You must have done that without knowing it. Beats me. I you go into HBOOT and select Recovery the phone will shut off and boot into recovery mode. If you got Clockwork Recovery version 2.x.x.x (with green typeface), that just means you have Clockwork recovery installed and can flash Froyo based ROMs (like Iced Glacier), make Nandroid backups, and a bunch of other stuff you probably shouldn't mess with.
Just know that you CANNOT flash Gingerbread based ROMs (like CyanogenMod 7) with CW v. 2.x.x.x
You need CW v. 3.x.x.x to use gingy ROMs.
Keep reading.
I PM'd ya, but no when I hboot and hit recovery, it doesn't reboot, it goes to "clockwork mod recovery v2.5.1.2
XfooYen said:
You have to follow steps to unlock the bootloader (achieving S-off) before perm root will stick. Read the thread on achieving S-off. Don't do anything you don't fully understand, so read a lot. Afaik visionary does not perm root with one click without first having an unlocked bootloader.
EDIT: Read the resource bible. It's a sticky in the dev forum.
Swyped on my rooted MyTouch4G
Click to expand...
Click to collapse
I'm having the same issue as the OP. I'm quoting because I had a permroot stick with s-on on my previous MT4G. (I just had it replaced, damn power button)
Explain please? Why would it work on one but not the other?
I would have posted this in the development forum in the thread that had this technique, but I don't have enough posts yet or something?
Anyway, I have S=off, and visionary temp root works fine. But permroot in visionary r14 doesn't work, it just flashes like the button is pushed then does nothing, like I didn't even hit it. So I need to run the temp root everytime my phone starts up.
I didn't setup the engineer bootloader yet, should I do that?
Does r11 work better?
What is the next step to get permroot to work?
Okay, here is the deal. I was trying to change around some stuff on my phone, the IMEI number to match the one on my prepaid tracphone. So far, before I changed the IMEI, i had it rooted and everything was slamming. But it would disconnect me after about a half hour. I am changing the IMEI to see if it fixes this, but after all this I had to revert back to a total stock flash of 2.2.1 HTC rom, it updated everything, one of those PBxx.img ones you do during the bootloader.
So now I've rooted it with visionary, and it hardly works, won't permaroot, but I get regular root. So I did another method on a wiki and have permaroot now. Updated SU, clockwork mod, ETC and everything works (well it installs and prompts me to give super user access then doesnt complain.)
HERE IS THE PROBLEM: I CANT CHANGE RECOVERY OR BOOTLOADER TO S-OFF
I have used gfree (multiple versions) to turn s off, and turn off all locks and to change the bootloader the nb0 one. BUT NOTHING gives.
>Clockworkmod from the rooted main screen, when i open the app, it won't install the clockwork mod recovery.
>When booting to recovery, the phone goes to stock recovery with the red triangle and phone. Upon where you have to push VOL UP + PWR button to see any options, and they are just the stock ones, (reboot, apply update:sdcard, etc)
I was wondering if someone had a signed image that they could link to me or send or whatever that has the s-off in a format that I can use with the BOOTLOADER; i.e.: Just put it on SD-CARD, hold "VOL UP+PWR" then it will do the update. U know, like radios are flashed.
If you can help me please, help me. I was so excited with this phone and moving along and now this.... ARG! lol. Thanks guys any and all input is appreciated no matter how irrelevant!
peace
GLACIER PVT SHIP S-ON
HBOOT-0.86.0000
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Sep 27 2010,11:12:59
You don't have perm-root.
Gfree can't work without root. Since you don't have perm-root without Gfree, you need temp-root.
While not S-OFF, you can't have perm-root. Period. End of story. Temp-root and execute Gfree.
Execute the rooting guide in Wiki properly, and you'll have S-OFF.
Of course, having no perm-root makes it impossible to flash recovery, or flash anything at all.
help.. tried root explorer, astro, es file..and have had no luck flashing to better roms...help
Sent from my HTC Glacier using XDA Premium App
If you are using Visionary R14, try R11. And f*ck wiki.
Jack_R1 said:
You don't have perm-root.
Gfree can't work without perm-root.
While not S-OFF, you can't have perm-root. Period. End of story.
Execute the rooting guide in Wiki properly, and you'll have S-OFF.
Of course, having no perm-root makes it impossible to flash recovery, or flash anything at all.
Click to expand...
Click to collapse
G-free turns s-off. If he has a bad eMMc chip, G-free is the only method he can use. And some phones have issues with the newer version of visionary.
lowandbehold said:
G-free turns s-off. If he has a bad eMMc chip, G-free is the only method he can use. And some phones have issues with the newer version of visionary.
Click to expand...
Click to collapse
I guess I wasn't clear enough in my response above, and wrote "perm-root" where just "root" was in order. Edited.
In any case, when was the last time you've read the Wiki? I suggest you look at it again.
I don't know if I am explaining correctly.
I applied the root method using visionary r14 because thats the latest from the site, it temp roots, but does not perma root.
I did a su, and got root, but I have to SU before i get root, it asks for SU permissions and I allow and I have root. (all this is done in a shell). So I know I have root, i can open up the system to read write and even delete some stock .apk and other files that aren't supposed to be deleted. So its all good. I can chmod 777, i know whats up there.
I did all this madness, SU updates to the most current binary, clockwordmod both an older and the newest version open, ask for and allow SU permission, and all that appears to work fine. EVEN with the friggen flash clockworkmod recovery, it says current recovery: clockworkmod x.x.x.x (meaning whatever the version is, tried a bunch).
BUT WHEN I BOOT TO RECOVERY OR BOOTLOADER, S-ON and friggen stock recovery for me. WHAT THE heck. its like its ignoring what I do to flash the bootloader.
Does anyone have a PBxx.IMG they can send, hopefully signed, that I can just use to update? or link to one? also, and update.zip for the stock recovery would work too.
HERE's the thing, its a T-mobile phone, and my TRACPHONE Prepaid sim works on it, but that *MIGHT* just be because TRACFONE = AT&T also T-Mobile=AT&T now also.
But I think the sim is unlocked, I'm waiting on other sim to come in the mail before I can verify for sure.
MAIN thing i need is a signed (or I'll even play with an unsigned) PBXX.img file for either the bootloader or recovery, or an update.zip one. At this point, if you have a lower version of 2.2.1 that has the whole entire shebang, (the radio, bootloader, os, recovery, etc) then I'll appreciate that too.
I just can't find it on here after days of searching and I am needing a push in the right direction. And google's overloaded with the SAME article just in different spam blog formats. Thx guyz
You CAN'T.
Everything you do when you're temp-rooted, DOESN'T GO TO THE eMMC! It stays in memory (eMMC cache), and the next time you reboot - everything is GONE. All your file deletions, chmods, etc - they're NOT REALLY EXECUTED. Reboot and see for yourself.
The only thing that will make it stay - is running gfree and gaining S-OFF.
The link, as everything else you're looking for, is in Wiki. Look in the Downgrade guide, there's a link for 2.2.1 RUU for MT4G. But it won't help you - you're just being stubborn and unwilling to read. YOU DIDN'T EXECUTE PERMAROOT PROPERLY, AND UNTIL YOU DO - YOU WON'T BE ABLE TO FLASH A DAMN THING.
The Wiki links to a Gfree method guide. Read it and execute it STEP BY STEP.
Okay, i did it
Here is what I did. I went in manually and copied the .nb0 to the file several times in a row.
Visionary does not work, the only way I can root this thing, without some type of temproot visionary app that messes up, is this way:
http://wiki.rootzwiki.com/index.php/HTC_myTouch_4G
Also, I am hoping I am correct, but this is how its laid out in the /dev block...
mmcblk0p18: HBOOT DATA (bits) And....
mmcblk0p21: RECOVERY DATA (bits) data or bits, whatever you want to call it. (its not a file)
Okay. So with that being said;
/dev/block/mmcblk0p18 = hboot 'file' and this is what i did.
Using 'dd' which is a unix command that just does low level convert and copy, will take the input file if=hboot_hacked_file.nb0 and then put it to the output device converting it and whatnot, the output file of=/dev/block/device
so it looks like this in example:
Code:
# dd if=/directory/filename.xxx of=/dev/block/output_device_or_file
Oh, and another thing that might just be paranoia... The wifi was on and it wasn't doing what it was supposed to do, I noticed it also being active unusually, I should have put wireshark on and checked it out, but didn't think about it at the time. Now that wifi off, it feels as if its fine now. It was almost like another user was in it. But thats probably just paranoia..... or the t-mob trying to mess me around!!!
This IS the gfree method, and you ARE running an app to gain temp-root there.
Copying the bootloader didn't help you at all, it was only a later step. It wouldn't stick if not for gfree.
Running gfree did.
Oh well, I guess that it's useless to explain. Glad it worked.
naw bro, its good that you explain what you mean, its not useless to explain anything. Here is what I'm saying... gfree -f is supposed to do the S-OFF right? well, it didn't. it also said failed or error or something at the end. Once I did the 'dd' command not just once, but several times and VERIFIED that it was working and different, while having # then I ran gfree again and it said SUCCESS at the bottom and THAT did it bro. SO that, in the end, turned my s-off and gfree unlocked my sim super unlock and cid unlock too.
I've cloned my IMEI because its legal, its my own phone and I'm not doing anything extra other than using it to make calls which I pay for at outrageous prepaid prices.
Does anyone know where that information is located by the way, just for information purposes... I've already done it using a hex editor and a part7.bin file... but I just am not quite sure on EXACTLY what I've done. like, the locations of what file or data that i've flashed. With CDMA, I usually enter QPST programming and all that and just just play till my heart's content... but now I'm trying to learn GSM and I want to know if there is a way to enter that kind of programming also. Or are us fellas forced to dump .bin files, hex edit, then reflash or reflex em...
Just lookin for some pushes in the right direction for programming in the GSM area.
Also if you have links to radios, all of them, previous and what not, I would appreciate it too
Flashing hboot, superuser or not, several times or not, didn't do a thing for unlocking.
For what reason gfree failed initially - I don't know, but when you ran it again and it didn't fail - that did it all. Otherwise you'd still be with S-ON, and the bootloader would still be the same.
You can't really argue against HW. That's how it works.
Radios are here:
http://forum.xda-developers.com/forumdisplay.php?f=796
Look for "Glacier Radios" sticky.
Like I said before as well. There are alot of issues with R14...find and use visionary R11. You are not the first person to have issues with visionary, and with the majority of them, the downgrade solved the problem.
Not true
I have try everything and nothing work. R11, r14 from visionary and it dosent work. Please devs try to get another method for the people that nothing work. I have hboot 0.86.0000
ahernandez646 said:
I have try everything and nothing work. R11, r14 from visionary and it dosent work. Please devs try to get another method for the people that nothing work. I have hboot 0.86.0000
Click to expand...
Click to collapse
Do you have Android version 2.3.4?
If so, Visionary won't work. You have to downgrade to 2.2.1 first. There is no way around this. But it's easy to do.
Skipjacks said:
Do you have Android version 2.3.4?
If so, Visionary won't work. You have to downgrade to 2.2.1 first. There is no way around this. But it's easy to do.
Click to expand...
Click to collapse
No, that's the froyo bootloader.
What happened when you ran visionary? Did you have usb debugging checked? Sometimes the temp root works on the first try, sometimes on the tenth. If it doesn't work, reboot and try again. If it still doesn't work after several attempts do a factory reset and try again. Sometimes a clean slate helps.
Sent from my HTC Glacier using XDA App
i do have 2.2.1 but i had a mytouch 3g slide and i root it. but for some reason i can't get the mytouch 4g to do it. i will re-try everything again.
Thanks to all that have reply.
I need to return my g2 for warranty reasons (part of the touchscreen doesn't respond) but I'm having alot of trouble unrooting it.
the bootloader never recognized the pc10IMG.zip on my sd card.
I'm wondering if it's an issue with my bootloader?
I have S-OFF
HBOOT-0.76.2000 (PC1010000)
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
any help will be greatly appreciated!
after having this issue for about 3 months, I've finally got it.
Formated a 2 gb sdcard and used that instead, it worked.
My rom is now stock, and so is my recovery, but the bootloader still looks the same, with fastboot and the skateboarding androids and everything.
is that the stock bootloader? I can't really remember, would like to make sure before I send it in.
Yes the bootloader is stock.
The only thing you might need to change is S-OFF back to S-ON
-Nipqer
s- on is a must *from experience*
MRguyandhis2 said:
s- on is a must *from experience*
Click to expand...
Click to collapse
What experience ?
I've swapped 3 g2's on hardware defects, no issues, very smooth process. I'm about to swap my last g2 for a cracked camera lens cover, if the warrantee is still valid. Yes, I received this g2 as a warrantee replacement, and notified them of the crack on arrival.
I keep reading about people having issues with warrantte, but never specifics.
lucky I didn't send it in yet, I completely forgot to check for S-off.
I'll have to check later, looks like I'm not sending it back till Saturday anyhow, but it's not as if I can actually use it while it's on stock since I'm on at&t and it's locked
when I was rooted with gfree, it unlocked itself, but now it's locked again, anyway to unlock it without voiding warranty? if not it's hardly going to matter.
Update: I put my sim in it and it's still unlocked! Hooray!
>update (again) : I can make calls, but no data
>>update: I'm absent minded sometimes.. that was because I needed to set att's apn
Also:
How do I check exactly (sorry, noob question) I can look for it a little more thoroughly tomorrow
don't think they care about the root, sent mine in many times with rooted roms and they seem to send my replacements and I'm on t-mobile, but just to be sure I don't think they care about S-on or off they might just care if the rom is significantly different like sense roms
I'm just really trying to make sure I get it unrooted correctly.
according to the guy on the phone, If I don't qualify for the warranty, my options will be to either pay for the repair, or pay $34 for their diagnostics on it (WTF?).
and the repair is going to be $100, since they'll going to replace the whole screen, even though I'm pretty sure the only issue is with the ribbon cable.
It's not going to hurt to make sure I have S-On, and it could potentially save me a lot of cash, so I might as well do it.
I'm pretty sure I only have to type something into the terminal emulator to find out?
not sure what that was though..
Well, my boot loader says S-off, and I can't figure out how to make it S-on since I don't have a part-7[something].bin on my SDcard.
from what I can find, I think I can make it S-on by using the official RUU, but I'm having trouble finding this, and almost tried to flash an ruu from the european HTC Hero (aka G2) by mistake.
[it's quite annoying that people call that the forums label that phone the G2 even though I don't think htc or any other carrier does in any case]
any help here? can I use somebody else's backup or would that result in a brick?
any alternative methods?
Update:
well apparently I can "Use gfree to set secu_flag = 1 and CID = T-MOB010 (or your corresponding original CID)."
although I'm not sure exactly how to do that.
I pretty sure it means that I could Gfree to gain temporary root, and then use the Terminal emulator to open up and modify a particular file in the system, and change the value of the parameter "secu_flag" to 1 (I'm not a complete n00b)
as for the CID, I think I may already have it set correctly, but it never hurts to check.
Am I on the right track?
almost right track.
Use psneuter to get temp-root, then run
./gfree -s on -c TMOB_010 (or whatever the cd is meant to be)
though psneuter only works for adb shell so you can't use term emulator to unroot.
and gfree only works on the 1.19 rom.
-Nipqer
If the screen is broken I believe all they do is change the screen and flash sense back on to it. I sent mine in with the screen not working and got the phone back with sense installed again + s-off. It looks like (for mine) they didn't care that it was rooted simply because it was a hardware fault and therefore did not matter whether it was rooted or not.
It is up to you whether or not you want to risk it, but with mine it was ok
Will check back with this thread when I get back from work in case I can help further!
Sent from my HTC Vision using XDA App
video
Zedomax has a guide on how to unroot the g2 on youtube. (not allowed to post a link)
I still can't get the S-off
Zedomax's video tutorial was pretty useless, he did the same thing I did, then booted into the bootloader and said "wierd it still says S-off..."
as for the the psneuters thing:
$ adb shell /data/local/tmp/psneuter kept getting permission denied
eventually I gave up and used vissionary to temp root.
then I pushed and did the chmod 777 step with gfree
but "# /data/local/tmp/gfree -s on -c T-MOB010" led to "/data/local/tmp/gfree: permission denied"
maybe I should try the "rage against the cage" root method?
I'm on 1.19.531 btw
I unlocked the Boot loader 2 weeks ago via Htcdev
Following this thread about acheiving S=OFF after HTCdev Unlocked.
GUIDE] How to get root/flash custom roms with HTCDEV unlock by Nipqer posted January 19,2012 adb push su /data/local/tmp/
GAING PERM ROOT.
> adb push busybox /data/local/tmp/
> adb push fixsu.sh /data/local/tmp/
> adb install SuperUser.apk
> adb shell chmod 755 /data/local/tmp/fixsu.sh
> adb shell chmod 755 /data/local/tmp/busybox
> adb shell /data/local/tmp/fixsu.sh
PERM ROOT WAS ACHEIVED, But I can not get S=OFF
I then followed the guide on the post.
EASY PERM/S-OFF FOR MYTOUCH 4G: G2/Desire Z PermRoot/S-OFF
http://forum.xda-developers.com/showthread.php?p=21563546
All commands seem to go flawlessly until
After following the directions on
Step Two:
Open term. emu. and type.
(DO NOT TYPE */# just commands.)
$) su
#) cp /sdcard/root_files/perm_root /data/local/perm_root
#) chmod 777 /data/local/*
#) /data/local/perm_root
http://forum.xda-developers.com/showthread.php?t=1035278
I get this error
chmod 777 /data/local/tmp/fre3vo is not working it show No such file or directory
I have all the proper files in the Platform tools folder in Adk
tried several times but no joy on S=off
Am I just going to have to stay with PERM ROOT, or will I have to downgrade to FROYO TO acheive S=OFF.
I have Android 2.3.4
SOFTWARE 2.32.531.1
HBOOT 0.89.0007
Any advice
I have the exact same problem, except I flashed a 2.2.1 stock Rom that had root permissions, and everything appeared to go well, but s-on remained. I'm interested in seeing how this turns out, because mostly I am being told that I am doing something wrong or not following the guides properly. However, I think its the HTC update that is complicating things...
Sent from my HTC Glacier using Tapatalk
HTC dev unlocked/Perm root/ NO S=OFF
I agree. I thought it might be that I unlocked a stock gingerbread rom and that was what was preventing me from S=OFF.
Although I have perm root and followed instructions. tried several times. still no joy.
I am wondering if someone typing the instructions left something out by mistake.
It is frustrating to get that far the get that chmod error.
Have you flashed a custom rom?
I have not tried yet. I have the stock Rom and the CM7 Rom saved. just cant bite the bullit.
You guys should take a look here
http://forum.xda-developers.com/showthread.php?p=21563546
Re lock and follow downgrade guides....easy cheesy...
4GBurn said:
I agree. I thought it might be that I unlocked a stock gingerbread rom and that was what was preventing me from S=OFF.
Although I have perm root and followed instructions. tried several times. still no joy.
I am wondering if someone typing the instructions left something out by mistake.
It is frustrating to get that far the get that chmod error.
Have you flashed a custom rom?
I have not tried yet. I have the stock Rom and the CM7 Rom saved. just cant bite the bullit.
Click to expand...
Click to collapse
Yes if you use adb/fastboot on your pc, to flash Clockwork recovery or 4ext recovery, you can then flash custom roms, all you want. But make sure you have adb/fastboot working because once you flash a custom Rom, you will have to then have to extract the boot.img from the Rom and flash it through fastboot. What I do is this:
1- download the Rom of your choice. Unzip it, and copy the boot.img into your adb directory on your pc.
2. Place the zipped Rom on your sdcard ( make it easy to find)
3. Boot your phone into recovery mode.
4. At this point, I do a Nandroid backup.
5. Wipe data/ factory reset
6. Wipe cache + davlik
7. Install .zip from sdcard - choose your Rom that you placed on sdcard ( be patient and be sure its finished)
8. Reboot your phone to hboot/FASTBOOT and plug in USB cable.
** on your pc click start--> run -> cmd --then in the command prompt type -->cd\ then type --> cd adb you should then be able to proceed to step 9.
9 type- fastboot flash boot boot.img
10 type- fastboot-windows reboot
At this point unplug your phone and wait for it to load your new Rom.
Again, this is what I do, and I have loaded 10 or more roms this way. But make sure you have either Clockwork or 4ext recovery on your device, and also that FASTBOOT is working on your pc. If you are not 100% comfortable, please don't try this...
Sent from my HTC Glacier using Tapatalk
out of sheer curiousity why would you unlock via htcdev?
--sent from my glacier.
rockstarar said:
out of sheer curiousity why would you unlock via htcdev?
--sent from my glacier.
Click to expand...
Click to collapse
In my case it was ignorance... Thinking it was the same as rooting. I wouldn't have if I had read here 1st, but a respected site that I read a lot, made it appear like a wonderful thing. And truthfully, if all you wanna do is load roms.. its not that bad. Just an extra step in flashing the boot.img from whatever Rom u choose. I do wish I hadn't though.
Sent from my HTC Glacier using Tapatalk
....people.. Never ever ever ever ever ever EVER use htcdev for unlock
Sent from my HTC Glacier using xda premium
nicgraner said:
....people.. Never ever ever ever ever ever ever use htcdev for unlock
sent from my htc glacier using xda premium
Click to expand...
Click to collapse
+ 1,000,000,000,000,000,000,000,000
1) You didn't extract the RAR properly, and/or you're trying to execute a script that is calling fre3vo while your SD card is mounted to your computer.
2) You didn't see that the guide you're using is LONG OUTDATED, and you need to downgrade the phone for it to proceed.
3) Read the previous threads on the subject.
4) Read the stickies BEFORE you start messing with something.
5) Relock your phone and proceed with downgrade.
6) Google it next time. You're yet another case of someone that comes around, doesn't read the stickies, and creates a thread "I did I-don't-know-exactly-what, now I'm doing something else that I shouldn't be doing but I don't know it, and it doesn't work out well".
I wish HTC released their unlock tool with basic Linux quiz that wouldn't allow using it unless you're at least likely to know what you're doing.
And I wish xda had a reading/googling comprehension test before allowing people to post...
I wish people that are seasoned and very knowledgable would stop assuming that you can learn EVERYTHING by reading. Sometimes when you read, people are speaking or typing in terms that are very confusing for someone that is brand new. Even better than that, if it is bothersome or aggravating to see someone ask questions, choose not to answer them rather than insult everyone that comes along to ask a question. I used to be a forum moderator, but it was for programming DirecTV satellite cards, and I know how frustrating noobs can be, but in this case, with phones there are so many different ways to achieve the same results, and it is confusing to know what to type where. I for one am very appreciative for any and all help that I receive, but have read until my eyes hurt, and some of the methods are not working on the HTC unlocked devices. I tried downgrading for 2 weeks and I never saw a section in the wiki that told me to relock my bootloader to downgrade. Anyway, thanks to all that have helped without making me feel like a total idiot when asking a question. Even more thanks to those that have chosen not to reply at all rather than post to insult me.
Sent from my HTC Glacier using Tapatalk
This forum is called "XDA-Developers" and not "XDA-Users" for a good reason. When you'll think about this reason, you'll probably understand the reason why new users should start by reading, reading and reading, rather than writing, and why not answering their questions will very quickly hurt them much more than being bashed in response to something stupid/lazy.
Jack_R1 said:
This forum is called "XDA-Developers" and not "XDA-Users" for a good reason. When you'll think about this reason, you'll probably understand the reason why new users should start by reading, reading and reading, rather than writing, and why not answering their questions will very quickly hurt them much more than being bashed in response to something stupid/lazy.
Click to expand...
Click to collapse
I agree to a certain degree, and I have learned a lot from you in the past 2 weeks, and I don't want u to think that I am ungrateful, because I am very appreciative for what you helped me with. In fact, I have continued to read for days. I'm trying to learn, but its not easy. A lot of the guides are not working for me because of my HTC update. I am trying methods on 2 different devices, one w/o the update is being more coopertive...
Sent from my HTC Glacier using Tapatalk