Related
Hi guys I am looking for the best way to unroot my phone and return everything to the way it was out of the box.
I currently have full root with nand unlocked.
Thanks all.
Sent from my PC36100 using Tapatalk
From the unrevoked website:
How can this be removed or undone if I need to take my phone in for service?
Download the latest ''S-ON'' tool to a temporary location and follow the installation instructions above to run it. Once your phone is S-ON, you may lose root permanently if you install an official update
Click to expand...
Click to collapse
I would install an official update first (to get rid of root) and then use that tool to re-lock the NAND.
Here's the link. I can't post it since I'm a new user:
downloads[/url][DOT]unrevoked[DOT]com/forever/current/unrevoked-forever-son.zip
not that simple. first, run the s-on tool. then, flash your misc partition with toast's modified mtd-eng.img. finally, flash a stock pc36img.zip. sound all good?
Hmmm..... now I'm even more confused.
Sent from my PC36100 using Tapatalk
use the unrevoked s-on tool. then downlaod this thing. evo4g.me/downloads//count.php?target=evo-root.zip
unzip. put mtd-eng.img on your sdcard, nad adb push (which u need to set up if it isn't already) flash_image to /data/local. type:
adb shell
(make sure screen is on and unlocked) su (accept)
chmod 755 /data/local/flash_image
/data/local/flash_image misc /sdcard/mtd-eng.img
then flash a stock pc36img.zip from hboot.
Ummm...you dont need s on to unroot as i just sent a phone back that i unrooted....all i did was downgrade to an older rooted build then ran the ruu from latest update. That put s on for me and unrooted
Sent from my PC36100 using XDA App
Sorry if I sound stupid, but what is the s on tool?
Sent from my PC36100 using Tapatalk
JuggZaPoppiN said:
Sorry if I sound stupid, but what is the s on tool?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
When you do a NAND unlock (aka a full root), the bootloader is turned to S-OFF to allow you to flash non-official ROMs, recoveries, etc. The S-ON tool allows you to turn it back to the ON position which is standard for non-developer devices (aka consumer-level). When you first bought your phone, it said S-ON in the bootloader, top right (hold volume-down while turning on your phone). Now it says S-OFF. You need it back in S-ON position to make it look like you were on a stock ROM (as well as putting the stock ROM back on).
Product F(RED) said:
When you do a NAND unlock (aka a full root), the bootloader is turned to S-OFF to allow you to flash non-official ROMs, recoveries, etc. The S-ON tool allows you to turn it back to the ON position which is standard for non-developer devices (aka consumer-level). When you first bought your phone, it said S-ON in the bootloader, top right (hold volume-down while turning on your phone). Now it says S-OFF. You need it back in S-ON position to make it look like you were on a stock ROM (as well as putting the stock ROM back on).
Click to expand...
Click to collapse
Thank you. I will give all this a try and post back my results.
Sent from my PC36100 using Tapatalk
I'm in the same boat...
I need to do the same to my Evo. Would it hurt if I just flashed the latest stock RUU instead of messing with s-on s-off utilities etc? It is a newer version than what I have on my phone now.
Thanks,
Dan
ah, this is why i refuse to use unrevoked...i rather downgrade to 1.47 and then root my phone using 1.47 methods...lol but when i was on 3.29 (not using unrevoked) all i did was run the official RUU on my computer with my phone plugged in and it unrooted my phone, and gave me s-on and flashed stock recovery.
mrjeancw said:
ah, this is why i refuse to use unrevoked...i rather downgrade to 1.47 and then root my phone using 1.47 methods...lol but when i was on 3.29 (not using unrevoked) all i did was run the official RUU on my computer with my phone plugged in and it unrooted my phone, and gave me s-on and flashed stock recovery.
Click to expand...
Click to collapse
When I rooted my phone I did not use unrevoked either.
Is this a method that I can use to unroot my phone and return my phone to default?
JuggZaPoppiN said:
When I rooted my phone I did not use unrevoked either.
Is this a method that I can use to unroot my phone and return my phone to default?
Click to expand...
Click to collapse
yea, use the latest ruu or the 3.29 to be on the safe side and it will restore you completely to stock.
DON'T use the latest...
That is if you want to be able to root again afterwards. The latest RUU 3.30.651.2 has not been cracked yet and you will be stuck with stock rom, until a solution is found at least. I did this and now I regret it, use anything 3.29 or below and you will be fine.
Oh... and dont accept any OTA's (over the air updates) while on an older rom or the same thing will happen.
danh18 said:
That is if you want to be able to root again afterwards. The latest RUU 3.30.651.2 has not been cracked yet and you will be stuck with stock rom, until a solution is found at least. I did this and now I regret it, use anything 3.29 or below and you will be fine.
Oh... and dont accept any OTA's (over the air updates) while on an older rom or the same thing will happen.
Click to expand...
Click to collapse
He is right. I figured u wanted to unroot because ur sending back to sprint. If thats not the case then use 3.29 or under. I dont think they have found a root for 3.30....sorry bout that.
Is this not a rooted 3.30?....or am I mistaken?
http://forum.xda-developers.com/showthread.php?t=819838
So the main reason I am wanting to unroot is because I am currently having some issues with mms. ONLY on AOSP roms though, and want to see if I restore my phone back to factory default and then gain root access if my problems will be gone.
So if I run just the 3.29 ruu, then my phone will be back on default? I wont have to worry about the s-on s-off thing?
Been reading through the root guides and notice all the gfree topics. I got perm root using the rage method months ago and was wondering if there were any advantages to the gfree method and if so can I still do the gfree
Sent from my HTC Vision using XDA App
Yes, you can and should use gfree, see the Wiki for details.
The Wiki also has a good explanation of why the S-OFF you have from the eng hboot is effectively only a "fake" S-OFF, and it is much safer to have the full radio S-OFF via gfree.
Sent from my HTC Desire Z
steviewevie said:
Yes, you can and should use gfree, see the Wiki for details.
The Wiki also has a good explanation of why the S-OFF you have from the eng hboot is effectively only a "fake" S-OFF, and it is much safer to have the full radio S-OFF via gfree.
Sent from my HTC Desire Z
Click to expand...
Click to collapse
So I read the wiki and I see what you mean now between the fake s-off and full s-off.
I too did the rage method months ago and am wondering if there are any advantages of using gfree to get the true s-off, besides the safety issue. I have successfully unrooted my G2 using this method: http://forum.xda-developers.com/showthread.php?t=831398 so I am pretty sure that I will not have any troubles if I need to revert to stock in case of a warranty issue.
If I do end up doing a warranty exchange, I will reroot using gfree, but should I run gfree now regardless?
Also, will doing gfree make this process easier of reverting to stock? From reading the wiki, it doesn't specify if I have permarooted using rage if I need to unroot to do the gfree way or if I can just do it over my currently rooted phone.
Or maybe it did and I just missed it XD
Sorry for the length and barrage of questions, but I don't wanna screw this up!
Also, sorry if I thread jacked, didn't mean to, but I didn't see the point in starting a new thread for the same question, just a bit more detailed in questioning.
I went through the whole wiki and had the same questions you saved me a whole lot of typing.
G2 cm6.1.1
tazz9690 said:
I too did the rage method months ago and am wondering if there are any advantages of using gfree to get the true s-off, besides the safety issue. I have successfully unrooted my G2 using this method: http://forum.xda-developers.com/showthread.php?t=831398 so I am pretty sure that I will not have any troubles if I need to revert to stock in case of a warranty issue.
Click to expand...
Click to collapse
The advantages are that full radio S-OFF can help you recover from certain conditions. e.g. on the Desire Z, some users flashed the 1.72 OTA update and found then that they couldn't root it. But those who had radio S-OFF were able to downgrade back to 1.34 and root again. Those with the "fake" S-OFF lost their S-OFF because a stock hboot was flashed, and they couldn't downgrade so are currently stuck without root.
If I do end up doing a warranty exchange, I will reroot using gfree, but should I run gfree now regardless?
Click to expand...
Click to collapse
Yes, I highly recommend that you do.
Also, will doing gfree make this process easier of reverting to stock? From reading the wiki, it doesn't specify if I have permarooted using rage if I need to unroot to do the gfree way or if I can just do it over my currently rooted phone.
Click to expand...
Click to collapse
It doesn't really make any difference to going back to stock. You can undo gfree with certain options to the command (see the Wiki for details). Downgrading with the full radio S-OFF is safer too, because you keep the S-OFF (until you remove it via gfree).
Thank you for the explanation, you sold me on gfree, but I'm not 100% sure on that last part steviewevie. So you are saying that I can run gfree in my current permrooted state with the fake s-off that I have with the hacked hboot? I do not need to unroot first and can just run gfree on top of what I already have?
Sent from my T-Mobile G2 using XDA App
tazz9690 said:
Thank you for the explanation, you sold me on gfree, but I'm not 100% sure on that last part steviewevie. So you are saying that I can run gfree in my current permrooted state with the fake s-off that I have with the hacked hboot? I do not need to unroot first and can just run gfree on top of what I already have?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Yes, you can run gfree on top of your already permrooted and ENG Hboot. That's exactly what I did.
Sent from my T-Mobile G2 using XDA App
Thanks for all the help guys it is appreciated
G2 cm6.1.1
Agreed. I appreciate it as well.
So, I'm looking at the wiki right now, and I don't need to start from the beginning of the process, or do I?
Where exactly did you begin the process joemm?
Sent from my T-Mobile G2 using XDA App
Got it if already permrooted and running a custom kernel you have to flash an older kernel for it to work I had a backup of the stock rom I flashed then push the gfree to data/local ran the commands given and am good to go now thank you all for the help
G2 cm6.1.1
Ok so I ran gfree and it worked great. I just restored my backup of CM6 that I had and everything looks good.
Now final question, do I have to reflash the hboot now that I have true s-off?
I know flashing hboot is unnecessary, but I do use fastboot flash from time to time.
Also, I downloaded the hboot, but when I do a md5 checksum of the extracted file like it does on the wiki, it says md5sum not found. Any reason as to why?
tazz9690 said:
Agreed. I appreciate it as well.
So, I'm looking at the wiki right now, and I don't need to start from the beginning of the process, or do I?
Where exactly did you begin the process joemm?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Start from here:
"gfree version 0.02 and its options
Since the current version 0.02 gfree supports the following options:
Code:
gfree usage:
gfree [-h|-?|--help] [-v|--version] [-s|--secu_flag on|off]
-h | -? | --help: display this message
-v | --version: display program version
-s | --secu_flag on|off: turn secu_flag on or off
-c | --cid <CID>: set the CID to the 8-char long CID
-S | --sim_unlock: remove the SIMLOCK
-f | --free_all: same as --secu_flag off --sim_unlock --cid 11111111
In the following steps the -f will be used to mimic the behavior of the original gfree version that will do radio S-OFF, Super-CID and simunlock in one go.
If you are only interested in permanent root you only need radio S-OFF and then it is sufficient to use
Code:
# ./gfree -s off
instead of
Code:
# ./gfree -f
in the following commands.
And gfree can now also be used to set radio S-ON by using the "-s on" option and to change the CID back to the original value be using i.e. "-c T-MOB010" if you want or have to go back. In addition since version 0.03 gfree can also be used t just to remove the write protection from the emmc and remove the kernels write filter to the radion partitions by using the "-w" option. This is handy if you want to restore your partition 7 backup.
ON YOUR PC:
Unzip gfree_02.zip to a place on your computer. Navigate to where the files are on your computer, and type:
Code:
$ adb push gfree /data/local
Gfree should now be in your phone at /data/local
ON YOUR PHONE:
You should still have terminal emulator up, at a root prompt from earlier.
Now run:
Code:
# cd /data/local
# chmod 777 gfree
# ./gfree -f
# sync
You now have read-write access to your /system, hboot, and recovery partitions. But you still need to "lock in" root, and give you 'su' access in the future. So just do:
Code:
# /data/local/tmp/root
# sync
Wait a few seconds for the changes to "take".
Now reboot your phone.
Congratulations! You're perma-rooted, radio S-OFF, and should have read-write access to your /system! But more than that, your phone should also be SIM-unlocked, so that you can use a SIM card from any carrier (T-Mobile, AT&T, Vodofone, etc.) See below for more info about that.
At this point you might consider downloading the 'Rom Manager app from the Android market and using it to install the Clockwork recovery and back up via the nandroid "backup" option should things go terribly wrong for you in the next (optional) step.
Also, gfree created a backup of your original partition 7 at /sdcard/part7backup-<time>.bin -- You might consider copying this to a safe location on your computer!"
For those who want to know where this info comes from its here at the HTC Vision Wiki: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision
Thanks, yeah, I bit the bullet and thankfully started from there.
But now I have a new question.
Do have to reflash the hboot now that I have done the gfree method and now have true s-off instead of the fake s-off and the hacked hboot?
Do you know?
tazz9690 said:
Ok so I ran gfree and it worked great. I just restored my backup of CM6 that I had and everything looks good.
Now final question, do I have to reflash the hboot now that I have true s-off?
I know flashing hboot is unnecessary, but I do use fastboot flash from time to time.
Also, I downloaded the hboot, but when I do a md5 checksum of the extracted file like it does on the wiki, it says md5sum not found. Any reason as to why?
Click to expand...
Click to collapse
No you dont have to reflash the ENG Hboot, turn your phone off, then volume-down+power and on the first screen with the skateboarding andriod it will tell you on the first line "ENG S-OFF" which means you still have your ENG. Hboot, so you will be able to use fastboot.
Yeah I saw that but I just wanted to double check my assumption. Thank you for your help! I am all set now and worry free!
Sent from my T-Mobile G2 using XDA App
tazz9690 said:
Yeah I saw that but I just wanted to double check my assumption. Thank you for your help! I am all set now and worry free!
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Yes you are , have fun flashing.
Thank you I will. Now say, that I have to return my phone for warranty, I no longer have to change the version number of the pc10img.zip to revert back to stock like I used to have to do in this thread: http://forum.xda-developers.com/showthread.php?t=831398
since I have true s-off now. I can just flash the pc10img.zip and not have to worry about any repercussions by doing this, correct?
I just ran an experiment on my phone. Even if you rooted using Rage, gfree will still unlock everything.
tazz9690 said:
Thank you I will. Now say, that I have to return my phone for warranty, I no longer have to change the version number of the pc10img.zip to revert back to stock like I used to have to do in this thread: http://forum.xda-developers.com/showthread.php?t=831398
since I have true s-off now. I can just flash the pc10img.zip and not have to worry about any repercussions by doing this, correct?
Click to expand...
Click to collapse
I would say yes, you can just flash the pc10img.zip if you have gfree'd your phone with true radio s-off. I have not personally tried it myself, so again this is just my assumption, but found a few other post to agree with this:
Weaseal said:
If my understanding is correct, none of this matters if you did scotty2's gfree app to get S-OFF, since it doesn't muck with the hboot (rather, it modifies the radio config [NOT the radio]). So if you did that method to root/s-off (as opposed to the 'old'/alternate wpthis-eng-hboot method), you should be safe to flash PC10IMG without bricking. Can someone else sanity-check my logic?
Click to expand...
Click to collapse
steviewevie said:
You are correct. I think the OP is going to try and get this guide updated when he has the time.
Not sure this needs to be sticky at the moment, perhaps until it's been updated ?
Those who only have the eng hboot and not full radio S-OFF via gfree do need to be aware of this though.
Click to expand...
Click to collapse
Found these quotes here:
http://forum.xda-developers.com/showthread.php?t=838484&highlight=gfree&page=6
And heres a quote from someone who said they did flash pc10img after gfree with no issues:
luis86dr said:
I'm gfree'd and have flashed pc10img with no issues. If you have the hacked hboot that's different ballgame.
[G2/HTC Vision]
Click to expand...
Click to collapse
And when he says if you have a hack hboot, he means if that's all you have just root with ENG. Hboot, and not gfree. So it sounds like you should have no problems.
Found this quote from here Post #47:
http://forum.xda-developers.com/showthread.php?t=838484&highlight=gfree&page=5
You are a great man joemm. I appreciate the time you took to find that information.
I also appreciate everyone else who has helped me out in this thread.
Just makes me appreciate this forum even more!
Hey guys, I'd like to know how to uninstall clockwork recovery from my T-Mobile G2 in case I need to bring my phone in for repair.
I know this is an FAQ, but the method to do it with each phone seem to vary slightly.
My T-Mobile G2 has the following:
Persoshoot's OC kernel
Stock post-OTA ROM with permroot
S-OFF
Latest Clockwork Recovery
What would be the easiest and most straightforward way to restore clockwork recovery back to stock (without nuking everything else in the process)? I see threads saying to run flash_image and flashing the OTA_bootv2 Recovery, but IIRC that program isn't installed on the stock ROM by default.
Your help would be greatly appreciated!
If you used gfree to permroot and get radio s-off, you can just flash the pc10img.zip and it will take you back to stock completely: recovery, hboot, s-on, kernel, rom, etc.
If you did permroot by way of one of the old methods (visionary, rage, etc) you can still flash over the pc10img.zip, after some modifications. Refer to this thread on how exactly to do this: http://forum.xda-developers.com/showthread.php?t=831398
If you have to do the latter, make sure you follow the instructions to the T so as to not end up with a paperweight.
If you have the eng hboot and you have adb setup on your PC, then you can use fastboot to flash the stock recovery image (which you can extract from the stock PC10IMG.zip.
Sent from my HTC Desire Z
It never hurts to erase the recovery before you flash a new one... rather than flashing a new one in over top of the old one. Sometimes stuff breaks and thats one reason why.
tazz9690 said:
If you used gfree to permroot and get radio s-off, you can just flash the pc10img.zip and it will take you back to stock completely: recovery, hboot, s-on, kernel, rom, etc.
If you did permroot by way of one of the old methods (visionary, rage, etc) you can still flash over the pc10img.zip, after some modifications. Refer to this thread on how exactly to do this: http://forum.xda-developers.com/showthread.php?t=831398
If you have to do the latter, make sure you follow the instructions to the T so as to not end up with a paperweight.
Click to expand...
Click to collapse
To get permroot, I initially used an old method, but then unrooted. The unroot method I used is actually what's shown in the post you linked to. After unrooting, I did permrooted the "clean" way (the one that's documented on the wiki) using rage to get temproot, then using gfree to do the rest.
Because I used gfree to permroot, I can simply flash pc10img.zip without any problems right? Without needing to hex-edit the misc.img version number to the previous version number? Can I simply rename it update.zip and the HBOOT bootloader will pick it up, or will I have to flash it from within Clockwork Recovery? Why is it safe to flash pci10img.zip if you used the gfree method?
I didn't install the engineering hboot since the instructions said I didn't really need it unless I was a developer.
Keirnoth said:
Because I used gfree to permroot, I can simply flash pc10img.zip without any problems right? Without needing to hex-edit the misc.img version number to the previous version number? Can I simply rename it update.zip and the HBOOT bootloader will pick it up, or will I have to flash it from within Clockwork Recovery? Why is it safe to flash pci10img.zip if you used the gfree method?
Click to expand...
Click to collapse
Yes, that's right, except it shouldn't be called "update.zip", you want to call it "PC10IMG.zip" and place it on the root (top) folder of your SD card, then go into hboot where it should find it and ask if you want to flash it (give it a few seconds to open the file and check it first).
It is safe if you have full radio S-OFF via gfree, because that bypasses a lot of these checks, e.g. the "version is older" check, and also because when it flashes the stock hboot you will still have S-OFF.
It seems as though the OP has had his question answered but I'm also wondering the same question. I have gotten full root by the rage method. What do I do in my situation to get back to stock recovery while maintaining s-off and root. I actually just want to calibrate my battery and go back to clockwork
Lithium Ion batteries cannot be calibrated. There is no need. They dont have a memory like older battery types did, for example, nickel cadiums.
If at all possible, all you would be doing is retraining your phone with that process, not the battery. It is bad for li-ion batteries to be ran completely empty and it is not recommended if you care about the longevity of the battery.
Sent from my HTC Vision using XDA App
Thanks for your reply. I was told by someone that flashing your phone while it is plugged in kinda throws the battery off. I have noticed extremely short battery life after making this mistake so I thought it was needed. Would you still recommend doing it train the phone itself tho? I mean, my battery life is ridiculously short. Like six hours and my battery always depletes while I'm asleep.
Sent from sweet G2
Okay so it looks like there is a problem with applying the current perm root instructions to the Telus Desire HD... soliciting input here on how to make a proper root guide for Telus.
Something about the RUU downgrade to an earlier firmware is causing the DHD to lose sound (headset, speaker, everything). The perm-root and radio S-OFF proceeds as normal but sound is gone.
I've suggested that the next step could be to try and flash the Telus Ace RUU after getting radio S-OFF. Still awaiting confirmation as to whether this fixes the sound problem. One person attempted to flash back the Telus radio and this did not fix it. So it's got to be something else. HBOOT maybe?
So my question is, if you're on a higher build number (1.84.661.1) but you also have already achieved radio S-OFF, is there now any way to root the phone or install custom recovery? Without downgrading by RUU again?
Those of you who have experience with the DHD already might have some brilliant ideas, so I thought I'd ask =)
The first thing would be to look at the TELUS firmware and see if there are any drivers that are specific for the phone.
Sent from my Desire HD using Tapatalk
link to the file? thx
Look in the Dev forum for the one with Telus in its name.
This thread is falling off topic though... I'm specifically asking for people who can tell me more detail about what Radio S-OFF does and doesn't allow.
Let's forget this thread and go to the Telus thread in this QA section. The problem is not in hboot or radio, those have nothing to do with sound. The problem is in the ROM, and it's drivers most probably.
There is no way to properly root Telus ROM, so it is not possible to install custom recovery while you are using it. Please check the downgrade thread for my recommendations.
Okay fine, forget I ever mentioned Telus in this thread. Can someone just help me understand the limits of what Radio S-OFF does and doesn't allow?
Allows: more permanent S-OFF, which does not go away when you flash OTA or RUU. Disables write protection in internal memory, so you can flash ROMs. SuperCID allows you to flash anything from any carrier. Disables version checking, so you can sail between newer and older ROMs easily.
Does not allow: fastboot commands in bootloader, such as fastboot flash radio. So you cannot flash a radio & splash1 etc without ENG S-OFF.
jkoljo said:
Allows: more permanent S-OFF, which does not go away when you flash OTA or RUU. Disables write protection in internal memory, so you can flash ROMs. SuperCID allows you to flash anything from any carrier. Disables version checking, so you can sail between newer and older ROMs easily.
Does not allow: fastboot commands in bootloader, such as fastboot flash radio. So you cannot flash a radio & splash1 etc without ENG S-OFF.
Click to expand...
Click to collapse
Okay... so let's say you have radio S-OFF and you're using a newer build that normally wouldn't be rootable. Could you:
- Get the temporary rootshell (which is part of the downgrade instructions anyway)
- From the temporary rootshell, flash_image the custom recovery (which should be writable due to S-OFF)
- Reboot into custom recovery?
You would have to dd the recovery in, but yes that would work. Use command:
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21
I still do not get why you would want to downgrade, get S-OFF, go back to Telus, and then get ClockworkMod..
You may have to install busybox to get dd working, in that case call it with "busybox dd if=..."
jkoljo said:
You would have to dd the recovery in, but yes that would work. Use command:
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21
I still do not get why you would want to downgrade, get S-OFF, go back to Telus, and then get ClockworkMod..
You may have to install busybox to get dd working, in that case call it with "busybox dd if=..."
Click to expand...
Click to collapse
Well it's a conceivable scenario. Suppose you get your S-OFF, and then later on you have a reason to want to go back to stock RUU. The next time you want to be rooted or flash a custom ROM, wouldn't this be faster than doing a full downgrade first?
Well, ok, but who would want to go back to stock when there are custom roms..
Sometimes flashing a pure stock ROM is the only cure for having gotten a little too exuberant in one's hacking
Sent from my Nexus One using XDA App
Well, full wipe does the same trick.
Sent from my Desire HD using Tapatalk
I have searched and searched multiple forums. Attempted different methods of rooting. I believe I may have done something wrong in the terminal emulator my first time but my problem is this; I cannot temp root with visionary, just get a black screen after I it says attempting. When I try to unroot, visionary says the device does not appear to be rooted. So cwr can't flash recovery cause it lacks permission. I have the superuser in the app drawer and security is off but when attempting to gain those permissions either through adb or terminal, I get denied. I'm on a stock rom, did factory reset but superuser app still exists. Can anyone at least point me in the right direction? I can't root/unroot, flash roms, etc. Maybe there is an extremely manual way of solving this? Btw first post. Noob video = hilarious.
Visionary has a very high brick rate. You really should have done a lot more research before you decided on how you wanted to root your device.
WARNING - Do not use Visionary to permanent root your G2/DZ - high brick risk!
There are some guides littered through out XDA about how to bring back a phone that's been semi-bricked by visionary. Look around and see if some them will help you out.
Thanks, I am sure I'll find one to help me out but i only used Visionary to temp root, then terminal to try and permroot.
It's a lot easier to root with adb, that way if anything goes wrong you can copy your exact cmd for faster help.
Chances are you need adb set up to downgrade anyway, for visionary to work. in which case you should just use the recommended method
-Nipqer
As long as you don't have gingerbread. Try the no abd required method. Twice.
Sent from my HTC Vision using XDA Premium App
I have tried every method out there. Couldn't downgrade because security was off. I am not rooted so methods to return s-on did not succeed. Will not let me fastboot flash a recovery (Failed: not allowed). So with all the different guides i've followed to a t, my g2 no longer boots past the htc logo, but I can get into boot loader. Am I bricked? if not I know i'm well on my way. All I really wanted to do was flash a recovery, which I should have done first to back up blah blah. That visionary method is what initially put me in the dirt, followed guide from another site before I found xda, I never used perm root through visionary just temp root, and tried to keep the root through terminal emulator. Where can I go from here? I do have access to another stock g2 that my buddy owns if that would help any
Code:
VISION PVT ENG S-OFF
HBOOT-0.84.2000
MICROP-0425
RADIO-26.08.04.30_M3
eMMC-boot
As long as you're on 2.2, using Visionary for temp root (only) should be safe. +1 to ianmcquin's gfree method.
Edit: Didn't see your last post as our posts were simultaneous. So you can't flash a PC10IMG file thru hboot?
Sent from my HTC Vision using XDA App
Ditamae said:
As long as you're on 2.2, using Visionary for temp root (only) should be safe. +1 to ianmcquin's gfree method.
Edit: Didn't see your last post as our posts were simultaneous. So you can't flash a PC10IMG file thru hboot?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Could you elaborate a little further? Security is off so flashing an official is bad or so I have read. Also, flashing through hboot? How would I accomplish this?
So I might be totally wrong here, but if you could put any pre-rooted ROM inside a PC10IMG zip file onto your SD card (you'll have to use a micro adapter or another phone to get it there)... then you should be able to boot into bootloader and flash it. Though I've never been in a situation with no root and S-OFF... can anyone confirm or reject this idea?
Sent from my HTC Vision using XDA App
Is it safe to use the RUU to restore the phone with s-off?
Edit: No, no it is not XD
Okay. So I have the rom in a PC10IMG zip file on the root of my sd card. Now, specifically, what must I do to boot into said rom. If I can be helped I will do all the research in the world to avoid a noob situation like this again. Which so far seems very improbable thanks to this wonderful site and all the information I have absorbed trying to find a solution to my problem
Well, as I said, this makes logical sense to me, but I was hoping someone more knowledgeable than myself would confirm.... but if you want to try it you'll power down, then boot into bootloader by pressing the power button and volume down at the same time. Once in the bootloader, you should be prompted to flash the pc10img file. I think you'll press volume up to confirm and then the rest is automatic. But again, I don't know that this will work for sure... and I haven't been in your exact situation. If you want more details on flashing pc10img.zip files, I know it's out there on XDA. Also, in the event it works for you be sure to remove this file from your sd card right away... or rename it.
Sent from my HTC Vision using XDA App
flash cmw in fastboot
fastboot flash recovery recoveryname.img or whatever
Solved; I was finally able to flash cwm after I had altered the hardware id's of the android 1.0 driver, flashed a pre rooted odex stock rom and wam bam thank you ma'am, phone is now operational. Thanks for your help guys =]