Related
I installed Visionary and everything was working perfect... But I made the stupid mistake to press Permroot and my G2 shut down and never bootup to Andrid OS..
I only see the HTC green logo .. I tried everything on recovery mode.. but I only get the HTC logo and the phone dont go anywere..
I tried to install the original G2 stock ROM but then the update fail saying Im trying to flash a older update. The room in the phone is newer than the update Im trying to install..,
Someone knows were I can find a Custom room that works in my Tmobile G2 USA...?
I need to install the room in recovery mode...ONLY .. because my phone do not boot-up.... So the ADB is disabled and the phone do not work... I only have access to recovery mode...
PLUS the phone is NOT rooted...
And Please dont tell me to do factory Reset.. because I did all that..If Im here is because I have tried everything and I dont get this phone to work.
Is there a room or a custom room somewhere that can be installed in my G2 by Recovery mode..?
If there is ,, can someone give me the link...?
My HBOOT screens says the following
VISION PVT SHIP S-ON
HBOOT- 0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMc-boot
Sep 2 2010, 17:59:38
boyfrom75 said:
I installed Visionary and everything was working perfect... But I made the stupid mistake to press Permroot and my G2 shut down and never bootup to Andrid OS..
I only see the HTC green logo .. I tried everything on recovery mode.. but I only get the HTC logo and the phone dont go anywere..
I tried to install the original G2 stock ROM but then the update fail saying Im trying to flash a older update. The room in the phone is newer than the update Im trying to install..,
Someone knows were I can find a Custom room that works in my Tmobile G2 USA...?
I need to install the room in recovery mode...ONLY .. because my phone do not boot-up.... So the ADB is disabled and the phone do not work... I only have access to recovery mode...
PLUS the phone is NOT rooted...
And Please dont tell me to do factory Reset.. because I did all that..If Im here is because I have tried everything and I dont get this phone to work.
Is there a room or a custom room somewhere that can be installed in my G2 by Recovery mode..?
If there is ,, can someone give me the link...?
My HBOOT screens says the following
VISION PVT SHIP S-ON
HBOOT- 0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMc-boot
Sep 2 2010, 17:59:38
Click to expand...
Click to collapse
Try the following link:
http://forum.xda-developers.com/showthread.php?t=842495
I already did try the link. But I dont understand what option to take..
The one of the options I think will work needs to have the phone ADB running ..
But my ADB is disabled because I can't get to the Android OS and the phone is not rooted..
I was reading that you can connect the phone to the Computer to fix it..
How do I do that ? What program do I need to run it ? But I dont like that option,,,, is to complicated..
Is there a way to fix the phone using the SD card on Recovery mode ?
boyfrom75 said:
I already did try the link. But I dont understand what option to take..
The one of the options I think will work needs to have the phone ADB running ..
But my ADB is disabled because I can't get to the Android OS and the phone is not rooted..
I was reading that you can connect the phone to the Computer to fix it..
How do I do that ? What program do I need to run it ? But I dont like that option,,,, is to complicated..
Is there a way to fix the phone using the SD card on Recovery mode ?
Click to expand...
Click to collapse
1) Just to clarify: VISIONary is a complete fail. Root using the rage method, then you can actually control what's happening to your device.
2) Did you ever flash clockwordmod recovery?
If you can boot into clockwork recovery you just need to flash another ROM.
Try posting this in the Q n A section. I know, posting a question in the QnA forum probably sounded like a CRAZY idea, but guess what, that is where this belongs.
tehseano said:
Try posting this in the Q n A section. I know, posting a question in the QnA forum probably sounded like a CRAZY idea, but guess what, that is where this belongs.
Click to expand...
Click to collapse
this guy is obviously new cut him some slack.....
just follow the instruction on the link carefully
idk why people are having trouble with VISONary i used it to root my phone n it worked....
im new on the forums but i know a thing or two about rooting
That's why I'm using Rom manager.. because its easier for my self.. as soon as you flash clock work recovery.. I believe that you can't go wrong.. I also did something similar and my phone also staid at the HTC screen.. but went back into recovery mode and clicked on restore and went in on my old Rom
sent from g2 using DHD Rom
boyfrom75 said:
I already did try the link. But I dont understand what option to take..
The one of the options I think will work needs to have the phone ADB running ..
But my ADB is disabled because I can't get to the Android OS and the phone is not rooted..
I was reading that you can connect the phone to the Computer to fix it..
How do I do that ? What program do I need to run it ? But I dont like that option,,,, is to complicated..
Is there a way to fix the phone using the SD card on Recovery mode ?
Click to expand...
Click to collapse
Ok, this is a snip from the link in the second post, it sounds like your are stuck in a boot loop with s-on, if so then this part is the part you need to try:
"*if you have stock or eng-recovery installed.
will the phone attempt to boot android at all? where is it stuck at?
a good min after it starts to try to boot, type these commands:
adb remount
adb shell
if you can get in shell then theres still hope. back out shell for a second and start here:
put the cwm recovery.img and wpthis.ko in your sdk folder
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb push recovery.img /data/local/recovery.img
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
# dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21 (now wait a min or 2 to give it time to finish)
#sync (give it another min or to just to be safe)
#reboot recovery
at this point you should be in cwm recovery. follow instructions above for flashing with s-on."
So now you are gonna have to install Andriod SDK to your computer and the drivers for the G2, there is gonna be a lot of reading and some downloading on your part to do this. Next your gonna have to download cwm recovery.img and wpthis.ko in your sdk folder and then follow the instructions above to recover your phone. Unfortunatly there is no one click fix. Its gonna take a lot of reading and understanding to do this on your part. Gonna have to learn to use ADB there a guide for that and run some basic command promts. Im no Dev or anything but I taught myself by doing a lot of reading, watching videos and a lot of searching. Hope you find the will to do it and recover you phone. Plus we are here to help walk you through some of it but your also gonna have to do some leg work to. GOOD LUCK.
I don't think the OP knows what adb is... you gotta do some more reading get over your fear of using your computer to fix your phone. Its really nothing to be afraid of and its not at all complicated.
Sent from my HTC Vision using XDA App
I'm gonna assume he knows what ADB is and if that's the case, your only option is using one of the full updates...from tmobile. It would have to be a new version of course, for your recovery to allow it. Trying reading through thr RUU threads, perhaps something or someone there can help.
Goodluck, and sry.
Sent from my HTC Vision using XDA App
android602 said:
That's why I'm using Rom manager.. because its easier for my self.. as soon as you flash clock work recovery.. I believe that you can't go wrong.. I also did something similar and my phone also staid at the HTC screen.. but went back into recovery mode and clicked on restore and went in on my old Rom
sent from g2 using DHD Rom
Click to expand...
Click to collapse
Brah its not even rooted yet
Sent from my T-Mobile G2 using XDA App
Not only does he not know what adb is... he didn't even have usb debugging enabled... Not sure that affect's whether or not he can use adb in the recovery or not... but just saying
omarsalmin said:
Not only does he not know what adb is... he didn't even have usb debugging enabled... Not sure that affect's whether or not he can use adb in the recovery or not... but just saying
Click to expand...
Click to collapse
USB debugging does need to be enabled. I know this because I always forget that step when I'm trying to use ADB on a new Android device.
If OP wants a working phone again, he'd better take his pretty-looking paperweight back to get it replaced (just drop it in your toilet first).
blackknightavalon said:
USB debugging does need to be enabled. I know this because I always forget that step when I'm trying to use ADB on a new Android device.
If OP wants a working phone again, he'd better take his pretty-looking paperweight back to get it replaced (just drop it in your toilet first).
Click to expand...
Click to collapse
WATER DAMAGE! Haha I don't think warranty covers that
I just read somewhere that in order for VISIONary to perm root you need to have S-OFF. OP made a boo boo by attempting to perm root with S-OFF.
omarsalmin said:
WATER DAMAGE! Haha I don't think warranty covers that
I just read somewhere that in order for VISIONary to perm root you need to have S-OFF. OP made a boo boo by attempting to perm root with S-OFF.
Click to expand...
Click to collapse
actually all the older guides (including the one I used to root my phone) said you ran perma root first then do s-off.
the perma root method in visionary was made before we even had s-off (only like a day before, but still before).
It sounds to me like your having the same problem that some people have been having with the rage method, only because you have s-on still your stuffed.
Basically for some reason newer phones seem to be getting a corrupt rom when perma rooting by any method. If you had s-off you could manually flash a recovery then a new rom.
Lennyuk said:
It sounds to me like your having the same problem that some people have been having with the rage method, only because you have s-on still your stuffed.
Basically for some reason newer phones seem to be getting a corrupt rom when perma rooting by any method. If you had s-off you could manually flash a recovery then a new rom.
Click to expand...
Click to collapse
The OP here used Visionary, not rage. Not sure which problem with rage you're referring to, because I've never seen anyone stuck in a boot loop just because they did rage.
His phone also seems to have been messed with before he got it, e.g. it's a G2 but running the DZ radio (which is fine, but implies someone has been doing things to it).
steviewevie said:
The OP here used Visionary, not rage. Not sure which problem with rage you're referring to, because I've never seen anyone stuck in a boot loop just because they did rage.
His phone also seems to have been messed with before he got it, e.g. it's a G2 but running the DZ radio (which is fine, but implies someone has been doing things to it).
Click to expand...
Click to collapse
2 people last week on the same day got partial bricks by using rage, I had to talk both of them through flashing a recovery manually in order to install a non corrupt rom.
I have a feeling the perma root process is corrupting roms on newer devices, not sure on the why though.
Lennyuk said:
2 people last week on the same day got partial bricks by using rage, I had to talk both of them through flashing a recovery manually in order to install a non corrupt rom.
Click to expand...
Click to collapse
You said this the other day, but I asked you for links and I don't think you replied (but maybe I missed that).
Are you sure they didn't use Visionary first ? That's usually what corrupts the ROM. Because rage is very very simple, it's not like Visionary which does complicated stuff. I really don't see how rage on its own can corrupt a ROM.
If you have any links to threads where people have not used Visionary, only rage, and have corrupted the ROM, then I'd be very interested.
steviewevie said:
You said this the other day, but I asked you for links and I don't think you replied (but maybe I missed that).
Are you sure they didn't use Visionary first ? That's usually what corrupts the ROM. Because rage is very very simple, it's not like Visionary which does complicated stuff. I really don't see how rage on its own can corrupt a ROM.
If you have any links to threads where people have not used Visionary, only rage, and have corrupted the ROM, then I'd be very interested.
Click to expand...
Click to collapse
Come on man, I shouldn't have to prove myself...
but here you go
http://forum.xda-developers.com/showthread.php?t=871288
and
http://forum.xda-developers.com/showthread.php?t=871552
both using RAGE and not VISIONARY.
Lennyuk said:
Come on man, I shouldn't have to prove myself...
but here you go
http://forum.xda-developers.com/showthread.php?t=871288
and
http://forum.xda-developers.com/showthread.php?t=871552
both using RAGE and not VISIONARY.
Click to expand...
Click to collapse
Sorry you took it that I was asking you to prove yourself. I wasn't, I was just asking for information, because I'm interested in the subject.
I'd seen those threads but do you know for certain they didn't try Visionary first, find it didn't work properly, then try rage ?
I could of course be wrong, but I don't see how rage can cause corruption because it doesn't do a lot, it just fires up a bunch of processes to exploit a way to get root. It's so much simpler than Visionary, which does a whole load of RAM disk stuff and other things that could be more risky if it goes wrong.
I suspect in those two cases that something else had already messed with their phones to cause the boot problem.
i need my phone rooted, Android 2.2- 0004 hardware- 3.70 Softy- 2.15.00.11.19 Baseband..... I will pay Via Paypal, I just needed rooted before I sell it! If any body can help Developers pls..... Remove this if it is pointless.
Thank you for your Time
Have they found a root method for 3.70 yet?
i dont know if they have yet...
Yes they have. Zikronix has a thread on how to do it.
Sent from my PC36100 using XDA App
Will unrevoked work?
No it doesn't...the unrevoked dev team is working on one.
leenypost was refering to this thread:
[ROOT][GUIDE] HBoot 2.02/2.10 SOFF - Root! The Final Frontier Edition - Upd. 12.21.10
i think they have but im not the one that wants to do it, i cant cuz my other evo got rooted with Simple root so i didnt have to do it the long Way but i dont have that phone anymore. Any takers?
All you need to do is follow the link ICEReaction posted. It's very straightforward.
just downgrade using a stock RUU then use old root methods
im VERY noob wen it comes to cmd, shell cd to etc. and all that i guess the hard part is the Command prompt i can open but wen changing or anything i get path not found etc
rayveno said:
just downgrade using a stock RUU then use old root methods
Click to expand...
Click to collapse
This will not work. If your phone is new and came with hboot 2.02 or 2.10 it is a no go. If you have an older EVO you can flash a rom with a lower SW version and then use an RUU that matches that version if you like and then use unrevoked to root... But that's way more work to then get back up to 3.70 than just following the supplied thread.
Thread moved to Q&A.
I have rooted my DHD using unrevoked3. I have super user permissions app, and clockwork mod recovery. Then I read that you can't install a custom rom without S-OFF. Do I still need to do the Visionary+ w/DHD eng script?
I thought my DHD still had S-ON but now I don't think I could have clockwork without it being off.... I'm confused.
Anyways I did go ahead and attempt the Visionary+, but perm root doesn't seem to do anything. I could probably skip that step I guess. The DHD script complains about busybox not being installed which is probably done during the perm root of visionary. I then installed Titanium Backup and did the check errors function and installed busybox. It said it installed, but terminal emulator still complains about busybox.
Confused. Can anyone help me?
drilus said:
I have rooted my DHD using unrevoked3. I have super user permissions app, and clockwork mod recovery. Then I read that you can't install a custom rom without S-OFF. Do I still need to do the Visionary+ w/DHD eng script?
I thought my DHD still had S-ON but now I don't think I could have clockwork without it being off.... I'm confused.
Anyways I did go ahead and attempt the Visionary+, but perm root doesn't seem to do anything. I could probably skip that step I guess. The DHD script complains about busybox not being installed which is probably done during the perm root of visionary. I then installed Titanium Backup and did the check errors function and installed busybox. It said it installed, but terminal emulator still complains about busybox.
Confused. Can anyone help me?
Click to expand...
Click to collapse
are you sure you have a DHD unrevoked is for the desire/evo/wildfire ect anyway however you rooted, you can use this tool to s-off
http://forum.xda-developers.com/showthread.php?t=857537
Thanks, I'll give it a try. =]
drilus said:
Thanks, I'll give it a try. =]
Click to expand...
Click to collapse
btw if you have rooted using unrevoked and have clockwork mod installed, you dont need to s-off to flash a rom, you already have write acess to the nand in recovery
How did you do that using unrevoked on DHD?
or you remove nandlock only with unrevoked and root with visonary ?
Something isn't right here. It isn't possible to root dhd with unrevoked
-----
Someone Swyped my idea.
Further information on Unrevoked & DHD
I seem to be having the same problem as the OP.
A bit of background: I just upgraded from my HTC Hero, and had some experience of rooting and installing custom ROMS on that device. My first job when I got my new HTC Desire HD was to get it rooted so I could get all Orange's crap off of it and have a streamlined new phone.
However, in my haste, I used Unrevoked, failing to notice the difference between a bog-standard HTC Desire and the newer HTC Desire HD. The upshot: Unrevoked *did* succeed in rooting my phone and installing ClockworkMod Recovery, but now the recovery partition thinks it's an old-fashioned HTC Desire and so won't install DHD ROMS. I can install bog-standard Desire ROMS to my heart's content.
So, I'm in a bit of a mess. I want to install a DHD ROM on my DHD, but I can't. Also, now that I've already gone through one rooting process, the standard procedure doesn't work, so I'm at a bit of a loss as to how to proceed. Any advice would be appreciated. Should I:
- try to get the phone back to its unrooted condition as it was when it came out of the box (in which case how do I do that?)
- flash a different recovery partition in the hopes that I can get it to recognise that my phone's a DHD and not an old standard Desire?
- fiddle about with the ROMs to get them to bypass the device checks (in which case how do I do that?)
Any other suggestions, let me know. It's possible I may have stumbled on a new method for rooting a DHD...
To fix it, just flash 1.32.405.6 RUU.
But I have to say, that is not possible
Desire ROMs on DHD, without S-OFF, everything is just simply wrong. Are you even sure that you have a Desire HD? Please send me a picture of your Desire HD running some Desire ROM.
oops
OK, it appears that there's a much simpler solution. Orange appear to have sent me the wrong phone.
Sigh...
Hahhahhah, good job Orange
Sent from my Desire HD using Tapatalk
ok, so to Orange's credit, I've sent back the wrong phone, and they've sent me the right one, next day delivery, having knocked 40% off the original price. Looking forward to playing with it this evening - I won't be touching Unrevoked with a barge-pole!
thanks @jkoljo for alerting me to the possibility that I might have been sent the wrong thing!
we get there in the end...
Very nice, good luck with your new phone
I have permerooted my DZ but now I seem to be having trouble understanding How to get S-Off and I can't do a nandroid backup unless I get S-off right.
Manarch101 said:
I have permerooted my DZ but now I seem to be having trouble understanding How to get S-Off and I can't do a nandroid backup unless I get S-off right.
Click to expand...
Click to collapse
Are you following the guide in the wiki?
Sent from my T-Mobile G2 using XDA App
Manarch101 said:
I have permerooted my DZ but now I seem to be having trouble understanding How to get S-Off and I can't do a nandroid backup unless I get S-off right.
Click to expand...
Click to collapse
First, yes you need S-Off to do a nandriod back up.
Second, you do not have permroot if you do not have S-Off. To get S-off there are several ways but I recommend using Rage+gfree found Here: in sub section "Rooting the Vision (G2/DZ) and DHD" This by far is the safest way to root.
But to let you make an informed decision there is also Visionary, now people in properly using this method, has produced a lot of soft bricks, I my self rooted this way, but again I still recommend using Rage+Gfree. But if you wish to still give Visionary a shot, Heres a link on how to properly use Visionary, make sure you follow everything to the "T". Read everything I have written in the post, do everything I have written in the post, then follow the videos exactly. But just to be clear, I am still recommending using the Rage+Gfree method. Happy Rooting.
ok joemm I tried the rage directions that you told me and I am not sure if it worked is there a way of knowing if it worked or not
Edit: nvm I can now get into CWM area which I could not get into before thanxs for the help and info.
What!!?? I know for a fact that you don't need s-off to do a nandroid. In fact, the ONLY thing s-off does that's of any significance is allow you to write to the system while it's booted - that's it. It's not some magic thing you absolutely need, just like having an ENG hboot isn't necessary to do 99% of the modifying you'll ever do.
This is a technical forum not some fire and brimstone 'do it or you'll die' sermon. Let's not construe fact and fiction/personal opinion on here. Just dish the facts unless otherwise rerquested.
As for gaining s-off, follow the wiki, push the files and you can literally copy and paste the commands if you need to (I suggest that so you don't screw up and brick your phone).
KCRic said:
What!!?? I know for a fact that you don't need s-off to do a nandroid. In fact, the ONLY thing s-off does that's of any significance is allow you to write to the system while it's booted - that's it. It's not some magic thing you absolutely need, just like having an ENG hboot isn't necessary to do 99% of the modifying you'll ever do.
This is a technical forum not some fire and brimstone 'do it or you'll die' sermon. Let's not construe fact and fiction/personal opinion on here. Just dish the facts unless otherwise rerquested.
As for gaining s-off, follow the wiki, push the files and you can literally copy and paste the commands if you need to (I suggest that so you don't screw up and brick your phone).
Click to expand...
Click to collapse
LOL..........how does he flash a custom CWM recovery with out having a rooted phone? Remember he is using ClockWorkMod to do a back up?
KCRic said:
What!!?? I know for a fact that you don't need s-off to do a nandroid. In fact, the ONLY thing s-off does that's of any significance is allow you to write to the system while it's booted - that's it. It's not some magic thing you absolutely need, just like having an ENG hboot isn't necessary to do 99% of the modifying you'll ever do.
Click to expand...
Click to collapse
S-OFF lets you flash unsigned images and overrides version checking ,it isn't just about writing to the system while booted. I think you may be confusing defeating the NAND write protection with the actual S-OFF.
As far as I know you need S-OFF to flash a custom recovery, and you need CWM recovery to do a nandroid backup. I have never tried flash_image but I would be suprised if that let you flash a custom recovery while S-ON, because flash_image is just a regular binary.
Sent from my HTC Desire Z
steviewevie said:
S-OFF lets you flash unsigned images and overrides version checking ,it isn't just about writing to the system while booted. I think you may be confusing defeating the NAND write protection with the actual S-OFF.
As far as I know you need S-OFF to flash a custom recovery, and you need CWM recovery to do a nandroid backup. I have never tried flash_image but I would be suprised if that let you flash a custom recovery while S-ON, because flash_image is just a regular binary.
Sent from my HTC Desire Z
Click to expand...
Click to collapse
True you can't flash a custom recovery and have it stick after a reboot but you can package it into an update.zip and flash it when you get into recovery. Aside from that you're phone performs the same. That's how we did everything on the MT slide before some one found a method to gain s-off. Of course there were no custom MTD partitions and we couldn't change the splash but that falls into the 1% of things the average 'rooter' will not attempt. The only reason we needed the ENG hboot was so that adb would catch our phone in recovery every time without running a loop.bat and praying to god. As far as NAND write protection, normally when a dev manages to break s-on they also break the write protection. At least that's what I've seen in phones with s-off. Are there any not like that?
Hopefully I didn't come off as an ass earlier, didn't mean it. I got 3 hours of sleep and I'm pulling a 13 hour day with a foot of fresh snow outside
I think you might be drawing too much comparison with earlier phones. The DZ and DHD have much stronger security than earlier phones. People familiar with experience of older HTC Android phones have often made incorrect assumptions about how things work on the DZ, some things are quite different (and typically much more complicated to unlock)
Sent from my HTC Desire Z
steviewevie said:
People familiar with experience of older HTC Android phones have often made incorrect assumptions...
Click to expand...
Click to collapse
Hell yes! And I'm one of them!
Last night I put some Cyanogen 6.1 flavoured ROM on my Magic/Sapphire. It was so easy: like 2 years ago or so I flashed some S-OFF ENG hboot, put some nice custom recovery on the phone and there I went, peacefully since ever. Reason for flashing the 6.1 CM was me giving the fone to my GF so that I can pick up a brand new Desire Z.
I came here, wanted to quickly crack that thing to play around with it and I find some gFree, Visionary, adb push stuff blah blah blah (I know my way around adb, that's not the point), it seems to have become alot more difficult than back in the days, as pointed out by steviewevie.
So, anyone willing to *quickly* summarize what has changed in the last 12 months regarding "rooting", "cracking" and ROM-customizing HTC devices for me...? I'm still, uhm... well, I'm shocked and overwhelmed. In the store I thought: cool, 7pm, device mine, home by 7:30, rooted by 8, Gingerbread-flavour on it by 8:30-9pm, ROM customization (settings and such) from 9-10, sleepy time by 10:30pm. Nah, it's past 10:30 and I'm still trying to figure out what's what with the new devices...
schaggo said:
Hell yes! And I'm one of them!
Last night I put some Cyanogen 6.1 flavoured ROM on my Magic/Sapphire. It was so easy: like 2 years ago or so I flashed some S-OFF ENG hboot, put some nice custom recovery on the phone and there I went, peacefully since ever. Reason for flashing the 6.1 CM was me giving the fone to my GF so that I can pick up a brand new Desire Z.
I came here, wanted to quickly crack that thing to play around with it and I find some gFree, Visionary, adb push stuff blah blah blah (I know my way around adb, that's not the point), it seems to have become alot more difficult than back in the days, as pointed out by steviewevie.
So, anyone willing to *quickly* summarize what has changed in the last 12 months regarding "rooting", "cracking" and ROM-customizing HTC devices for me...? I'm still, uhm... well, I'm shocked and overwhelmed. In the store I thought: cool, 7pm, device mine, home by 7:30, rooted by 8, Gingerbread-flavour on it by 8:30-9pm, ROM customization (settings and such) from 9-10, sleepy time by 10:30pm. Nah, it's past 10:30 and I'm still trying to figure out what's what with the new devices...
Click to expand...
Click to collapse
Its become more difficult because device manufacturers have made it more difficult. The "official" means to root the Vision is posted on the Vision wiki page here at XDA.
Sent from my T-Mobile G2 using XDA App
Thanks for the answer. I got the thing cracked in the meantime. The device feels so much smoother without Sense... and Gingerbread is good for one's soul
I was able to run an older version of Unrevoked to establish SU access, but Unrevoked Forever is incompatible with my radio version. So, I have SU access, but I cannot remove or convert any applications using Titanium Backup. TB runs, but it reboots the phone if I try to remove system apps. HBOOT shows S-ON since Unrevoked Forever was not able to complete due to the radio version. So, am I stuck with S-ON? Is Unrevoked Forever going to continue developing releases to cover 2.15.10.07.07?
If I understand correctly, I cannot flash an older radio version with S-ON. Please correct me if I am wrong.
Thanks!
HTC Incredible
2.3.4
Baseband: 2.15.10.07.07
you are correct,s-on will only let you go forward with "approved by htc" files. that means no backpeddling firmware to a rootable version,no flashing only a radio or recovery. im surprised that unrevoked even worked to get you su access,i was under the impression that all exploits had been patched in 2.3.4 source code. what happens if you try and install clockwork?
if you truly have su access,it seems it may be possible to use adb to rewrite the misc image,and thus be able to flash backwards in firmware.
however,from the sounds of the behavior youre describing for tibu,i dont believe you have su access. it prolly only put the app in the drawer,and was unable to place the matching binary.
we have been telling folks for months that they should become s-offed before the GB update,as it would be unrootable.
i bought an xtc clip awhile back that is supposed to support the incredible. i dont know that it will actually work,ill know for sure when it gets here. im told it only works with sim card phones,wich the inc is not,but its clearly listed in the supported devices.
your only real hope at this point is that someone finde a new exploit that will allow temp root and re-writing of the misc image so that you can flash older rootable firmware,or that alpharev/unrevoked can add the incredible to its supported devices list,as they use some sort of hboot trickery to get a hard patched permanent s-off hboot onto the phone first. from there you load a recovery thru hboot,then flash su in recovery.
sorry this isnt the news youre hoping for.
Thank you for the help.
It is odd. I definitely have su access through terminal, and I am running opengarden and barnacle wi-fi tether. I ran an older version of Unrevoked, and it did not complete the final step of s-off. Clockworkmod installed successfully, and I created a recovery image. Can we expect some way to root after the GB update? Is this just an HTC thing? I'm sorry for all of the questions, but I was soooo close!
efizzle said:
Thank you for the help.
It is odd. I definitely have su access through terminal, and I am running opengarden and barnacle wi-fi tether. I ran an older version of Unrevoked, and it did not complete the final step of s-off. Clockworkmod installed successfully, and I created a recovery image. Can we expect some way to root after the GB update? Is this just an HTC thing? I'm sorry for all of the questions, but I was soooo close!
Click to expand...
Click to collapse
If you already have clockwork mod, flash the unrevoked forever zip from here
When I flash the zip file, I get E:/ unsupported radio version. E: update failed.
Do you have adb set up and running? Are you fairly comfortable copy/pasting commands?
Sent from my ADR6400L using XDA Premium App
still with us? waiting for an answer to the above so we can procede
also is it possible you can post or PM me a link to the version of unrevoked you used?
if you dont have a link,just email me the whole file( [email protected] ) im extremely interested in trying to duplicate your condition and figuring out a reliable way for folks to downgrade and root.
Scotty,
I'm sorry for the delayed response.
I do not have ADB setup, but I have no problem following directions to get S-off and reclaim some memory!
I have emailed you the Unrevoked file to your email address. This should run perfectly on 2.3.4 with the exception of the last step of flashing unrevoked.zip for S-off. You will see the "unsupported radio version" errors on the phone's screen. Please let me know if there is anything else that I can do to help. Thank you for your help with this.
I got your email. I will put some stuff together for you,and try it out and see if it all works the way I hope it will. If so ill upload a mini-adb with some exploits files and post a guide. Basically,were just going to rewrite the misc image so you can downgrade back to froyo and run unrevoked forever. After you reroot and get s-off back,you can restore a backup of what you have now.
Sent from my ADR6400L using XDA Premium App
Subscribing to thread. Looks interesting, Im hopeful it works out. Good luck!
Sent from my ADR6300 using XDA App
Ok after reading this thread again. My guide for the merge on froyo or the stuff I have for gingerbread for the merge will not work on a non emmc device. 2nd who buys a xtc clip and doesn't look what they buy? The way it works is with the sim card slot. Inc doesn't have one so it isn't going to work. It also isn't listed as supported as it would be pointless to say it does.
If I am not mistake with s-on you can't flash the recovery partition. So how did you get clockworkmod? If you have clockworkmod then you can flash non htc files. Well actually I am not sure how that would work as you have s-on but clockworkmod. Since I have never been in that boat I am unsure.
So are we talking about the inc or inc 2? If inc I am trying to think back to the desire and what was possible on s-on. If I remember right you can dump the misc then flash a lower version ruu. I just can't remember if it doesn't even flash or if it does and doesn't downgrade the radio. By the way I got it in a pm/here scotty was planning to base helping you off my merge guide. By the sounds of it anyway.
Where the commands are not the same. As the partitions would be different. The misc-image is also not the same so if he had you flash the merge misc it will more than likely bork stuff. I am more than willing to help though. How ever I do not check the forums so you are better off pming me. I will say that nothing will probably work until unrevoked supports the new radio.
Edit: If the incredible works with a goldcard. Dump the misc partition and edit it for the firmware version you want to downgrade to. Then run a lower version ruu. When that is done run unrevoked. Of course I don't have a inc so I am not sure if that will work either. I also jumped a bit to conclusions so sorry for that. I also do not get your one post about the xtc clip here, yet in that other post say the clip doesn't support the inc.
thanks for your input,but rest assured we are in no way shape or form refering to anything to do with drellisdees's guide,your copy of it,or any other files,guides,etc. you have linked or posted on this site or yours.
he allready has root access and a recovery partition.
again,thanks for your input,but please stop confusing the issue with your references to merge guides.
for others watching this,a crude guide is now up on android forums:
http://androidforums.com/incredible-all-things-root/427344-2-3-4-root-downgrade-s-off.html
root 2.3.4 with unrevoked 3.22 has now been done successfully twice,and 1 has successfully roled back to 2.2.
more testers welcome
Confirmed. Worked for me. Was s on 2.3.4.
Sent from my ADR6300 using XDA App
My Incredible also is S-on with Verizon 2.3.4 OTA and never rooted. I'll give that "crude guide" a try tonight and report back how it went.
I'm just tired of all the low memory notifications and the constant force closes. Hopefully, I can have a custom mod installed tonight if things go well.
SUCCESS!!
Instructions from the website flawlessly for me.
I first rooted the phone. Then I tested it with some root only apps. They all worked. So ideally you can stop here if all you want is root but next OTA will take away root and then you'll be stuck again.
I completed all the steps and they worked. I was able to downgrade to 2.2 and then run unrevoke3 to root and also turn S-off. It did wipe the data clean. No files from my SDcard were deleted.
This is the time i've rooted my phone and the whole process took me an hour because I was being extra careful not to miss any steps. It all went smoothly.
glad it worked out for you. we finally worked out enuff bugs i put it up here as well: http://forum.xda-developers.com/showthread.php?t=1306400
efizzle seems to have dropped off the face of the earth everyone who reads this should make sure to click the "thanks" button in his first post. we wouldnt have it if hadnt figured out the 3.22 secret.(we would still have zergRush,but not root with access and the ability to make nandroids and backups with tibu so easily).
once again,thanks efizzle
Worked like a champ. I did a recovery back to 2.3.4 and it worked as expected. Also brought back all my force close issues. So I used ROM Manager and installed Cyanogen7 and am loving it.
clicking the thanks button a few times for this help
Ok, I'm on Linux, Ubuntu Lucid Lynx 10.04.3 to be exact, and I have adb installed. Where can I find the Linux version of unrevoked 3.22. I have found several places on the interwebz but I'm not sure if I trust those sources.
Help Please
Just like the op I have a Dinc that is on Gingerbread 2.3.4 and baseband 2.15.10.07.07 and desperate to have root. S-OFF would be nice, but root would be just fine for now.
More than happy to be the Guinea-pig on a Linux system.
sorry,i have no idea. i did a quick search and couldnt even find the windows version of 3.22 that i uploaded... i wanted to link it at its source,since it was emailed to me,but im not sure where he downloaded it from. you might follow the link in the first post credits to the original xda thread and ask on that thread,or send efizzle a private message and see if he can help you. in a worse case scenario,as long as you have 3.32 for linux,you could get temp root and downgrade with the "zergRush" method described in past #2. it doesnt require 3.22,but you wont be able to make a backup,or run titanium unless you can push SU,the binary,and busybox to their respective locations after acquiring a temp root.