Greetings all.
I just recently semi-bricked my Desire, I was uing 'Oxygen 2 RC2' and tried to partition my sdcard through 'AmonRA Recovery' and something went wrong and I ended up with a semi-bricked phone. I couldn't establish any connection with my SIM or SD-card.
I was tipped to install a original RUU which after a few tries worked and I recived a phone with the latest official Sense rom, HBOOT-0.93.0001 and S-ON of course.
After 'fastboot oem enableqxdm 0' is fastboot mode I atleast had connection with my SIM and SD-card and now a I have a semiworking but not rooted phone.
Now I want to root my phone and take back my USB-connectitvity but after reading this I understand that I need root for the USB-brick fix, to work but how do a get root with 'HBOOT-0.93'? Paul O'Brians root method only works for 'HBOOT 0.80' and lower and 'UnrEVOked' only works when having USB connection.
So how do I go about getting root and fixing my USB-Brick on my phone?
Thanks /ZeD
I have found a couple of "downgrade" tools but they haven't helped me much since everyone workd from within a fully booted system with a working USB-link which I have not.
Can a downgrade be done with a simple but old RUU file?
An old RUU file will not work.. I have the same problem, and got the same guide on how to fix it. But I sent it in for repair just hourse before, so I didnt have the chance to try it out. I unrooted my Desire as well with no luck. But as I read the guide, a rootet phone is not necessary?
For me it was, I had a another kind of fault at first my USB-brick happend when installing the ariginal RUU. What I should have done was to install a old RUU with 'HBOOT 0.80', root that and do the USB-brick fix, but I didn't know that I would get one ^^.
Blubba10 said:
a rootet phone is not necessary?
Click to expand...
Click to collapse
From the first step in that guide .
1. Follow this r5 rooting guide to do Step 1 of the rooting.
That will give you a basic ROM to work with, with root capability.
Click to expand...
Click to collapse
Well, I installed RUU with Hboot 0.80.. And then innstalled updates.... How noob is that?! Just asking..
Blubba10 said:
Well, I installed RUU with Hboot 0.80.. And then innstalled updates.... How noob is that?! Just asking..
Click to expand...
Click to collapse
I don't fully understand what you mean but when you have that kind of USB-brick that I have you need a rooted phone to fix it and the old way of rooting a Desire where you don't need it plugged to the computer can only root phones with 'HBOOT 0.80' or lower, the 'unrEVOked' way of rooting a Desire can be used on phones with newer bootloaders but need 'USB Debugging' which can't be used when a USB-brick is in play.
This is what you call a catch22 .
I have now seen a thread where a dude fixed a USB-brick on a non-rooted phone but the exploit that was needed is nowhere to be found. Well, well the hunt is on.
the easiest way to downgrade.
http://forum.xda-developers.com/showthread.php?t=768256
mariosraptor said:
the easiest way to downgrade.
Click to expand...
Click to collapse
This might come of as being rude but thats not my intention but I have several thread on diffrent forums out about my issue and most of the answers I recieve is from people that doesn't read my first post.
I cant use that downgrade tool since I don't have any contact with my phone through the usb cable.
if you use a card reader to put the PB99 file on the root of your sd card? boot into hboot it will recognize the PB file and prompt for doangrade.
no need to be rude as no intention were to make you feel offended.
if it is of no help no hard feelings,
cheer up and have nice holidays and a Happy New Year!!!
Freddan80 said:
This might come of as being rude but thats not my intention but I have several thread on diffrent forums out about my issue and most of the answers I recieve is from people that doesn't read my first post.
I cant use that downgrade tool since I don't have any contact with my phone through the usb cable.
Click to expand...
Click to collapse
I'm just a bit tired of working with this **** all weekend and answering in my ' cry for help threads' with I don't have root so I cant do that or I don't have a usb connection so I cant do that.
For the USB-brick fix to work I need root and for the downgrade to work I need a connection, it's just one way around my problem which seem to work but I only get 'permission denied' or 'that location is nonexistent'.
If anyone with more knowhow than me wants to take a look, the only thing that would actually fix my issue is here.
My meaning was to say that I think i have the same usb-brick as you (phone is now sent in for repair). It was rooted, but I unrooted it to hboot 0.80 and innstalled updates, wich resulted in hboot 0.93 in hope for it to fix itself. It didnt. As you say, you need root to fix brick. The only solution wich seems to work is this: http://forum.xda-developers.com/showthread.php?t=879068.. It seems to work for some people, not for me... And not for you as well, if i understand your latest reply correctly..
Yeah that's one of the fix I have tried.
It's kind of strange that that doesn't work, cause we should be able to write to that folder but for me it's like it isn't there at all. I checked my spelling and checked with 'androlib' that the working folder for 'Android Terminal Emulator' was in fact 'jackpal.androterm.
SUCCESS!!!!
I finally found a terminal that could give me enough "root" to use the exploit that gave me enough "root" to flash the fix. My phone is fully working now. Time to root the sucker again .
Freddan80 said:
SUCCESS!!!!
I finally found a terminal that could give me enough "root" to use the exploit that gave me enough "root" to flash the fix. My phone is fully working now. Time to root the sucker again .
Click to expand...
Click to collapse
Woooow man tell me how you did it imediately i have the 100% exact same problem as you did...tried update.zip, signature error, tried exploit with Terminal Emulator, no premissions...pleaaase tell me how you did it i am really desperate
godina said:
Woooow man tell me how you did it imediately i have the 100% exact same problem as you did...tried update.zip, signature error, tried exploit with Terminal Emulator, no premissions...pleaaase tell me how you did it i am really desperate
Click to expand...
Click to collapse
I used 'Better Terminal Emulator' never could get 'Android Terminal Emulator' to work.
I then used the commands given in the link I posted but instead of using 'data/data/jackpal.androidterm/*', I used '/data/data/*.
and then I did what the other thread said, made them executableand ran the exploit and then flashed my modified USB-brick fix.
Omg omg omg this could really be it i will try it asap, will post how it went...and does your bt, radio and usb all work?
Edit: where did you get this "Better Terminal Emulator" and how did you install it? I tried looking in market but didnt found tthis app
here it is http://forum.xda-developers.com/showthread.php?p=10058480#post10058480.
godina said:
Omg omg omg this could really be it i will try it asap, will post how it went...and does your bt, radio and usb all work?
Edit: where did you get this "Better Terminal Emulator" and how did you install it? I tried looking in market but didnt found tthis app
Click to expand...
Click to collapse
Ok I give up
Tried to download Better Terminal Emulator Magic, but it has been removed from market, looked for Pro version, cant download because there is no paid app support in Slovenia, so I can not download any paid app...
Is there any way for me to get this Better Terminal Emulator or will I just have to send the phone to repairs?
godina said:
Is there any way for me to get this Better Terminal Emulator or will I just have to send the phone to repairs?
Click to expand...
Click to collapse
You can obtain a copy here, but I'm not to sure about support.
Related
Hey, I'm trying to NAND Unlock my HTC Evo and I came across a problem with the PC36 file. It gives me an error I'm assuming because I have the latest update that says "Main version is older". On top of this, I have a macbook and it seems I can't use simpleroot. Does anybody know of another method to nand unlock that wouldn't be too complicated? I'm quite the noob. Thanks in advance XDA and everyone else!
Djlevy said:
Hey, I'm trying to NAND Unlock my HTC Evo and I came across a problem with the PC36 file. It gives me an error I'm assuming because I have the latest update that says "Main version is older". On top of this, I have a macbook and it seems I can't use simpleroot. Does anybody know of another method to nand unlock that wouldn't be too complicated? I'm quite the noob. Thanks in advance XDA and everyone else!
Click to expand...
Click to collapse
Hey dood, there are several threads on this. Since you are new ill point you in the right direction, but please try to use the search function next time.
Use SimpleRoot. It can be found under the development section.
Dredge said:
Hey dood, there are several threads on this. Since you are new ill point you in the right direction, but please try to use the search function next time.
Use SimpleRoot. It can be found under the development section.
Click to expand...
Click to collapse
he said in his post he can't use simpleroot because he has a mac,
I think if you use unrevoked3 first then you can do this it will allow you to do everything from the phone you must use unrevoked3 first to get su priveledges. that you can search for.
http://forum.xda-developers.com/showthread.php?t=732834
ifly4vamerica said:
he said in his post he can't use simpleroot because he has a mac,
I think if you use unrevoked3 first then you can do this it will allow you to do everything from the phone you must use unrevoked3 first to get su priveledges. that you can search for.
http://forum.xda-developers.com/showthread.php?t=732834
Click to expand...
Click to collapse
Thanks so much, I'm about to give this a shot. I'll let you know.
Well that sucks, it still is giving me the "main version is older" error.
You should be able to use this to get a custom recovery
http://www.unrevoked.com/recovery/
Then do this to gain full root and nand unlock
http://forum.xda-developers.com/showthread.php?t=732834
follw this very carefully, do just what it says and you should be good to go, this is the long way around but as you have a mac it is the only way i know how to do it. Somebody else may chime in if there is a better way.
The unrevoked site has an option for mac as you should see it for download there.
Ahhh, yeah the issue is I have 1.47.
Djlevy said:
Ahhh, yeah the issue is I have 1.47.
Click to expand...
Click to collapse
If you run unrevoked three then use that method from the video you should be able to get full root and nand unlocked. just did it on a spare evo.
This may be considered a stupid question, but should I be downloading these files to my phone or just dropping them in the file as a disk drive?
the unrevoked you run from your computer, the others are dropped on the root of your sd card, i believe the instructions tell you exactly what to do, just do that verbatim and you will be fine
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.
Okay I have a G2, just got it and I need to perm root it. I looked at the sticky guide but most of the links aren't loading for me, don't know why, either thread isn't there or link expired or w/e. I don't know, but I need some help.
First, how do I find out if I have 1.72 or an earlier version
Second, do I use "rage"? method or VISIONary and what's the latest version of visionary?
Third, about how long does the process take?
Any help is appreciated.
James_Caliber said:
Okay I have a G2, just got it and I need to perm root it. I looked at the sticky guide but most of the links aren't loading for me, don't know why, either thread isn't there or link expired or w/e. I don't know, but I need some help.
First, how do I find out if I have 1.72 or an earlier version
Second, do I use "rage"? method or VISIONary and what's the latest version of visionary?
Third, about how long does the process take?
Any help is appreciated.
Click to expand...
Click to collapse
Every thing you need to know about rooting is in here http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision just start reading from Rooting the Vision (G2/DZ) and DHD or you can read the whole page. Don't use VISIONary, you have a chance of getting stuck in a boot loop, use Rage and GFree. You'll need the android SDK to get ADB. I'm not sure how long rooting takes, I haven't done it yet as I don't have my G2 until next week but I have been reading about root for the past week. From what I know, 1.72 is only if you have a Desire Z. If you have any more questions, I'm sure me or another member can answer you.
KoolKidsKlub said:
Every thing you need to know about rooting is in here http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision just start reading from Rooting the Vision (G2/DZ) and DHD or you can read the whole page. Don't use VISIONary, you have a chance of getting stuck in a boot loop, use Rage and GFree. You'll need the android SDK to get ADB. I'm not sure how long rooting takes, I haven't done it yet as I don't have my G2 until next week but I have been reading about root for the past week. From what I know, 1.72 is only if you have a Desire Z. If you have any more questions, I'm sure me or another member can answer you.
Click to expand...
Click to collapse
Do you know what the 1.72 # refers to? Is it the build number or something else?
Thanks a lot for your help though. I'll start reading
James_Caliber said:
Do you know what the 1.72 # refers to? Is it the build number or something else?
Thanks a lot for your help though. I'll start reading
Click to expand...
Click to collapse
If you have a Tmobile G2 (from your first post, I assume you do) you don't need to worry about 1.72 it for the Desire Z. There are three methods to root with, them being Visionary, Rage, gfree. Gfree by far has caused the least amount of problems. If you know ADB rooting should be pretty simple, just follow the wiki on rooting with gfree. If your not familiar with ADB, there are methods to root without having to use it. But its always good and recommended to have it installed and running. There are guide here to help walk you thru it, but if for some reason its to difficult or you don't quite understand it, like I said there are methods to root with out it. There is a modified way to run gfree with your home computer and terminal emulator on your phone. Also the visionary method too, now many people have had problems with visionary, I'm not one of them, it is how I rooted my phone, but I can't stress the importance of reading and putting the time into understanding what you are and want to do to modify your phone, far to many people act before understanding and run into many problems including bricking there phones, I know some of the threads are really long in this forum but that's no excuse, whenever I try something new I read the entire thread first start to finish because any problems you may have, the solution has probably already been givin somewhere in the thread. There is no rush to jump into something you don't understand, my suggestion is to invest the time to read and understand how to root you phone first.
Sent from my HTC Vision using XDA App
Even if you root using rage, you can still install and use gfree on your phone. I can confirm that it works.
Just stay away from Visionary.
blackknightavalon said:
Even if you root using rage, you can still install and use gfree on your phone. I can confirm that it works.
Just stay away from Visionary.
Click to expand...
Click to collapse
This.
This is my first Android phone and I was able to follow the Wiki and root it pretty easily. The only part I didnt do was installing the Engineering Hboot. Just cause it is labeled as optional and unnecessary and the warning about bricked phones scared me away from it.
This ADB Guide for Noobs was pretty helpful in the process too
http://forum.xda-developers.com/showthread.php?t=865685
With that link and the Wiki your all set.
boost3d23 said:
This.
This is my first Android phone and I was able to follow the Wiki and root it pretty easily. The only part I didnt do was installing the Engineering Hboot. Just cause it is labeled as optional and unnecessary and the warning about bricked phones scared me away from it.
This ADB Guide for Noobs was pretty helpful in the process too
http://forum.xda-developers.com/showthread.php?t=865685
With that link and the Wiki your all set.
Click to expand...
Click to collapse
You're missing out with the engineering bootloader. You'll have more recovery options with it installed.
blackknightavalon said:
You're missing out with the engineering bootloader. You'll have more recovery options with it installed.
Click to expand...
Click to collapse
I might install it later on, if that is possible and wont cause issues.
boost3d23 said:
I might install it later on, if that is possible and wont cause issues.
Click to expand...
Click to collapse
Yeah that's what I'm going to do. I'm going to root the phone then when I feel more comfortable, I'm going to flash the engineering HBOOT. It's not that I'm scared, well I sorta am but I would rather not do something that isn't necessary. I'm coming from a rooted G1 so I know what it does and everything, I just don't think its necessary. The way I look at is is this, if you flash the HBOOT then your a lot safer because you can use fastboot flash to save your self from a semi-brick, but at the same time, flashing the HBOOT is also dangerous because you can brick your phone beyond repair.
*bump*
Sorry guys, I know this is an old thread, but isn't it better to post on something existing rather than creating a new thread? Hopefully I'm right...
Anyhow, I'm a Sprint convert and I now have the G2. Rooting the Samsung Epic I had was super easy, because I downloaded a one-click script that did everything for me. However, I'm fairly tech-savvy and accomplished just about everything for the rooting procedures using gfree and rage.
However, when I use gfree_verify, I get the message 'verify could not initialize the device!'. I think I run into my problem when I get to this part:
# /data/local/tmp/root
# sync
when I run the first line, I get a message about file existing that it says to expect... but it also says that "the rest of the script should still run ok". Well, after I get the file existing message, it goes back to the prompt. If there was a script that ran after that message, wouldn't I see other messages before it returned to the prompt?
I hope I'm making sense... and I hope I posted this in the right place. I'm dying to get a Sense ROM on my phone, but I need to get some sleep for work tomorrow. Any help that everyone could provide would be EXTREMELY appreciated Thanks so much!!
...EDIT...
Apparently, despite my lack of luck with verification, root is in place in my phone and has stayed after reboot. I've flashed clockwork and have used Superuser access... all seems to be well! Thanks anyway
Hi,
I red a lot about these problem, but non of the posts helped me!
I had the latest version of the frimware. I read/write in hebrew so the RTL problem was really annoying! so i decided to root my phone and install rom that has RTL fix.
I did downgrade and i rooted my phone, but i cant get rid off the the radio (s-on).
I rooted with visionary+, but when i open the "easy radio tool", and i press on "do it", it stuck at the end. i waited one hour, and i know that it used to take 20 sec.
I tried other computer, i did factory reset, i even made gold card... nothing. still stuck. i tried to do h-boot with terminal emulator, after i press su its ok, with the #, but the next it says "cant open sdcard/dhd/check". i tried different sdcard but it doesnt matter.
Now i have android version 2.2, kernel 2.6.32.21 and software 1.32.405.6.
Please tell me what i do wrong, i spent 10 hours for nothing!!
Thank you very much!
mozes77 said:
Hi,
I red a lot about these problem, but non of the posts helped me!
I had the latest version of the frimware. I read/write in hebrew so the RTL problem was really annoying! so i decided to root my phone and install rom that has RTL fix.
I did downgrade and i rooted my phone, but i cant get rid off the the radio (s-on).
I rooted with visionary+, but when i open the "easy radio tool", and i press on "do it", it stuck at the end. i waited one hour, and i know that it used to take 20 sec.
I tried other computer, i did factory reset, i even made gold card... nothing. still stuck. i tried to do h-boot with terminal emulator, after i press su its ok, with the #, but the next it says "cant open sdcard/dhd/check". i tried different sdcard but it doesnt matter.
Now i have android version 2.2, kernel 2.6.32.21 and software 1.32.405.6.
Please tell me what i do wrong, i spent 10 hours for nothing!!
Thank you very much!
Click to expand...
Click to collapse
did you downgrade 1st
like in this thread
http://forum.xda-developers.com/showthread.php?t=905003
how did you get root only with Visionary since visionary doesn't work since 1.72
and if you are really S-OFF (you should see it in the HBOOt menu ...when you restart press Power button and volume down and hold them....), the, instal the latest HTC sync , just to have the latest adb drivers, and take care...when you us Easy radio tool to keep the phone screen on, and on the main window...cause a SUPER USER window is gonna appear to ask for Super user permission ...of course you press YES
Hi
Tank you very much for the answer.
Yes, i did downgrade exactualy like in the post (i had Gingerbread , i didnt have to do the froyo-section 2a right? :/ )
After that i did root with visionary that is very simple after i downgrade to 1.32.
I didnt finish the radio tool, but i had the superuser permission and i pressed "yes".
Doesnt work.
Any other ideas?
mozes77 said:
Tank you very much for the answer.
Yes, i did downgrade exactualy like in the post (i had Gingerbread , i didnt have to do the froyo-section 2a right? :/ )
After that i did root with visionary that is very simple after i downgrade to 1.32.
I didnt finish the radio tool, but i had the superuser permission and i pressed "yes".
Doesnt work.
Any other ideas?
Click to expand...
Click to collapse
and what does it say...theres a error message or something ????
did you chech in hboot menu if you have ENG S-OFF like i said ???
and did you instal the latest htc sync
OMG i think o missed a step
you did root with Visionary but you didn't ENGS-OFF (i guess)
did you followed this guide???
http://forum.xda-developers.com/showthread.php?t=855403
if not..
DO IT and after that RADIO S-OFF should work
but 1st ENG S-OFF
hi
I checked, its still s-on...
I have the last htc sync.
I understood that it doesnt matter what you do first, but i will try.
i tried the eng s-off but i have the same problem, it stuck in the middle, when it says "verifying and disabling write protection". there is not any error message like the easy radio tool, it just stuck, no matter how long i wait.
mozes77 said:
i tried the eng s-off but i have the same problem, it stuck in the middle, when it says "verifying and disabling write protection". there is not any error message like the easy radio tool, it just stuck, no matter how long i wait.
Click to expand...
Click to collapse
Are u sure u have perm root. On what Rom are you now ? You should be still in the 1.32 build version. Try perm root again with visionary and after that eng s-off
hi
I did perm root with visionary, and im on 1.32-doesnt work
I gave up, never mind but thank you very much for your help anyway.
i hope that i will find another solution soon.
mozes77 said:
I did perm root with visionary, and im on 1.32-doesnt work
I gave up, never mind but thank you very much for your help anyway.
i hope that i will find another solution soon.
Click to expand...
Click to collapse
Usb debugging is enabled ....in settings/app/development ??
Something, somewhere u do something wrong ....it works for everybody.
eng s/off worked np for me but I kept getting stuck at radio.
in the end i plugged the device into another usb port on my computer and it simply worked.
Ok i did it!!!! With the terminal emulator. It was much easier and worked!! Anyway, thanx everybody for the help!
Sent from my Desire HD using XDA App
mozes77 said:
Ok i did it!!!! With the terminal emulator. It was much easier and worked!! Anyway, thanx everybody for the help!
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
glad to here that..... aspect you on Android Revolution thread
Hi all
For the last few weeks I have been trying to fix my HTC Desire back to some sort of working state. After awhile, I managed to get back to stock (from CM7), but soon realised I had the USB brick and SD Card issue. For info I used the stock HTC 2.3 Gingerbread RUU and used Alpharev PB99IMG_downgrade.zip for HBOOT (I was using Alpharev S-OFF with CM7).
So, I followed this guide, http://android.modaco.com/topic/309939-usb-brickrickrolledb0rked-fixed/ and managed to mount the SD Card. However, I could not get the update.zip file to apply because I was no longer rooted.
So I followed the guide linked in the USB brick article, http://android.modaco.com/topic/307...ide-now-with-hboot-080-and-os-to-121-support/ and soon realised that I did not have the HBOOT version required. Either 0.75 and below, or, 0.80 and below. I have 1.02.0001.
Not a problem, I thought. I will follow this guide to downgrade, http://forum.xda-developers.com/showthread.php?t=768256 as it specifically says that "...the downgrade does not depend on any version of HBOOT" which is what I need. However, first step is to get a working Goldcard. This is where I start to get into trouble and I'm already losing track of what I'm doing, but I soldier on...
How do I create a Goldcard? I followed this guide, http://android.modaco.com/topic/305672-creating-a-goldcard/ and got stuck at running the ADB command as because my USB is broken, Windows 7 (x64) refuses to see the Phone. Luckily, my father has the same phone, so I put my SD Card into his Desire and managed to create a Goldcard (he is running CM7 on his Desire too).
So Goldcard in hand, I go back to the downgrade guide and then spot my next issue. I can't get Windows to see the phone to use ADB commands and I also can't get Windows to see the phone when it is booted up (the charge light won't even come on now), meaning I can't run the downloaded application.
Not to be outdone I went back to the Rooting Guide and tried both of the downloads with the "step1-windows.bat" command just in case they did work, but both give an error, which on searching, is to do with the HBOOT version being incompatible.
I tried putting on the PB99IMG_downgrade.zip file from Alpharev again, then re-running the HTC 2.3 Gingerbread stock RRU and taking the ROM.zip folder and re-loading it on to the phone, but it hasn't changed the HBOOT version. So my cry for help is.... how can I downgrade HBOOT without using ADB commands or having to have Windows detect my phone? I'm basically stuck with Fastboot and my SD Card.
Even though my phone looks stock, I can't call people as it disconnects straight away, the USB is broken and the battery drains stupidly quickly.
Thanks for any help!
now this IS a sticky situation.. well done on what you've done so far by the way.
On my guide there's a section on how to temproot and flash recovery without USB connection, then flash a recovery that restores usb functionality, but it's only been tested on 2.2 and S-OFF... could be worth a try though
bortak said:
now this IS a sticky situation.. well done on what you've done so far by the way.
On my guide there's a section on how to temproot and flash recovery without USB connection, then flash a recovery that restores usb functionality, but it's only been tested on 2.2 and S-OFF... could be worth a try though
Click to expand...
Click to collapse
Hi bortak,
Thanks for the reply. It is a bit of a strange situation I agree. I've been putting off signing up and posting for help as I feel quite dumb for breaking my own phone, but I have to admit defeat on this one.
I saw your reply also in this similar topic, http://forum.xda-developers.com/showthread.php?t=1290391, so I will definitely try your suggestion and report back.
Appreciate you taking the time to post.
Thanks.
USB Brick on official GB 2.3.3 and HBoot 1.02
I still have the same problem and tried to get temp. root with the "rageagainstthecage" and terminal emulator method:
http://forum.xda-developers.com/showthread.php?t=691639&page=73
But I had no luck. There is no way to write the Misc patition... I´d like to downgrade (to Froyo), but without USB it seems to be impossible. Alpharev did not work. Revolutionary needs USB !USB brick with official Gingerbread, S-ON and HBoot 1.02 seems to be a dead end so far....
dexterm1 said:
I still have the same problem and tried to get temp. root with the "rageagainstthecage" and terminal emulator method:
http://forum.xda-developers.com/showthread.php?t=691639&page=73
But I had no luck. There is no way to write the Misc patition... I´d like to downgrade (to Froyo), but without USB it seems to be impossible. Alpharev did not work. Revolutionary needs USB !USB brick with official Gingerbread, S-ON and HBoot 1.02 seems to be a dead end so far....
Click to expand...
Click to collapse
well this sucks, it's also strange how there is so many people at once with exactly same problem as well!
you could call HTC and ask if they'd fix it for you, and say that this happened after you did the update.
bortak said:
well this sucks, it's also strange how there is so many people at once with exactly same problem as well!
you could call HTC and ask if they'd fix it for you, and say that this happened after you did the update.
Click to expand...
Click to collapse
I´ll have a try
just fixed my desire 1 hour ago and it works.
look at this http://forum.xda-developers.com/showthread.php?t=1296916
What I did:
I was able to connect my pc and phone through wi-fi and adb worked (adb connect phones-IP-address ) and then pushed, chmod'd 755 and executed zergrush. Gained root via cmd with adb shell in windows and after that I just pushed flash_image and mtd0.img to phone and ran it like you supposed to in the guides (chmod 755 and execute). Rebooted and voila! USB connection is working and now my phone signal isn't dropping anymore - phone fixed!
I fixed my unrootet Phone (official GB 2.3.3, HBoot 1.02, S-ON, USB Brick)!!!!
I wifi connected with adb and got temp root with zergRush!
Then from cmd in adb shell I flashed the misc with mtd0.img!
Rebooting and everything was fine ))
Many thanks to all of you!!!
dexterm1 said:
I fixed my unrootet Phone (official GB 2.3.3, HBoot 1.02, S-ON, USB Brick)!!!!
I wifi connected with adb and got temp root with zergRush!
Then from cmd in adb shell I flashed the misc with mtd0.img!
Rebooting and everything was fine ))
Many thanks to all of you!!!
Click to expand...
Click to collapse
Hi, pls. tell us how did you managed to connect your unrooted phone over wifi with adb? I get only "unable to connect to ... ip ..."
You may now want to install 4ext touch recovery now u have sorted it. This has a USB unbrick feature and will save a lot of time should this happen again
exocetdj said:
You may now want to install 4ext touch recovery now u have sorted it. This has a USB unbrick feature and will save a lot of time should this happen again
Click to expand...
Click to collapse
I can not install anything without root, and i can't root 2.3.3 software.
try this,
http://theunlockr.com/2010/09/20/how-to-root-the-htc-desire-unrevoked-method/
mine was 2.3.3 after the manual update but now rooted
exocetdj said:
try this,
http://theunlockr.com/2010/09/20/how-to-root-the-htc-desire-unrevoked-method/
mine was 2.3.3 after the manual update but now rooted
Click to expand...
Click to collapse
Ignore this, you can't root 2.3.3 with unrevoked
r5_alpine said:
I can not install anything without root, and i can't root 2.3.3 software.
Click to expand...
Click to collapse
Use revolutionary instead
http://theunlockr.com/2011/08/02/ho...android-phone-using-the-revolutionary-method/
Instructions are all there, read them several times
Sent from my HTC Desire using XDA
eddiehk6 said:
Ignore this, you can't root 2.3.3 with unrevoked
Use revolutionary instead
Instructions are all there, read them several times
Sent from my HTC Desire using XDA
Click to expand...
Click to collapse
I can't do both of this, because my phone is not recognized by PC in any way, i must root it without PC.
If you have 2.3 connect to same wifi as your pc and adb connect to your phone's IP. Then run zergrush and you will have temproot over adb from your pc. Then you can flash your mtd0.img and your brick will be resolved
Sent from my HTC Sensation Z710e using XDA
matus.karahuta said:
If you have 2.3 connect to same wifi as your pc and adb connect to your phone's IP. Then run zergrush and you will have temproot over adb from your pc. Then you can flash your mtd0.img and your brick will be resolved
Sent from my HTC Sensation Z710e using XDA
Click to expand...
Click to collapse
I have tried this too, but i get unable to connect error. And on phone i can't enable adb over wifi without root. I have tried almost everything what i found, and im still on the same step.
r5_alpine said:
I have tried this too, but i get unable to connect error. And on phone i can't enable adb over wifi without root. I have tried almost everything what i found, and im still on the same step.
Click to expand...
Click to collapse
Are you on 2.3 from htcdev? Because that version has adb over wifi enabled by default as it is a dev version. Are you S-on?
matus.karahuta said:
Are you on 2.3 from htcdev? Because that version has adb over wifi enabled by default as it is a dev version. Are you S-on?
Click to expand...
Click to collapse
Yes i have flashed it via bootloader from sd card, hoping to resolve the problem, but it become worse. With previous firmware there was no problem temp rooting, now it seems impossible. And yes i am S-ON.
r5_alpine said:
Yes i have flashed it via bootloader from sd card, hoping to resolve the problem, but it become worse. With previous firmware there was no problem temp rooting, now it seems impossible. And yes i am S-ON.
Click to expand...
Click to collapse
Have you tried running RUU while connected with fastboot? Have you tried flashing anything while in fastboot? I am just throwing suggestions at the wall, anything might work or brick...
matus.karahuta said:
Have you tried running RUU while connected with fastboot? Have you tried flashing anything while in fastboot? I am just throwing suggestions at the wall, anything might work or brick...
Click to expand...
Click to collapse
The phone is not seen by pc in any statement, not in bootloader, or fastboot, or recovery. I need to either downgrade to 2.29 rom version, or to root it in some way.