Develop Bugs

[Q] Cant do any updates

Hello,
I have been having trouble with my phone for weeks now. Back in August I used Unrevoked to root my Droid Incredible. Everything worked fine.
But now, I need to update my radio firmware before I can effectively use any of the custom ROMs. I am still using version 1.00xxx of the radio software, and if I try to install any of the custom ROMs my GPS stops working. So I have repeatedly tried to update the radio. I download the ZIP file and try to install (after backing up, of course). I get the error "no image or wrong image" and the update won't install.
So I have tried to reformat my SD card using FAT32. Same error. I do not rename the ZIP file or do anything dumb like that.
Next I tried to unroot my phone. It is my understanding that these updates are actually a binary diff, so the right base version must be installed in order to do the update. When I tried to unroot using the stock version of the ROM, I get the same error. So at least my phone still works, but I cannot do any updates.
I have searched all the forums and have read that many people seem to have this problem. But there are no solutions that I have not tried.
Any suggestions? I would *really* appreciate any pointers.
AE

Bump
Any suggestions?

To begin with, are you s-off?

No. I was just thinking about doing that. I read the unrevoked forever site, and it seemed to indicate that there might be some kind of locking going on which is why the updates won't install. Is that the right thing to do?
I will follow those instructions and post again if there are difficulties.
Thanks for the response.
AE

Just curious but can't you just run the RUU?

android_enthusiast said:
No. I was just thinking about doing that. I read the unrevoked forever site, and it seemed to indicate that there might be some kind of locking going on which is why the updates won't install. Is that the right thing to do?
I will follow those instructions and post again if there are difficulties.
Thanks for the response.
AE
Click to expand...
Click to collapse
Therein lies your problem. You must be s-off in order to do what you're trying to do.
http://forum.xda-developers.com/showthread.php?t=774155

Hboot not responding to pc...zip

Ok, so this is a big problem for me. I recently got a new evo (little bro broke screen, so i got a replacement) and i instantly tried to root it. I am on hardware 0003 with hboot .79 running version 1.47. As you can see, I have gotten to 2.1 successfully. I started at 3.29 so this was pretty easy.
But now I have a huge problem. My hboot won't let me flash the pc.zips. I name them correctly, and it loads the zip, and even checks it, but just dumps me back at the menu with no error warning or anything. This is a really big problem. I can't even get back to froyo now.
So I downgraded to hb .79 software 1.47 using the rage against the cage and flashing misc method before the pc.zip. This took a few tries for the zip to update as well.
Then i used the flash exploit to try to root eclair. Everything went great. But my pc goes to checking, and then dumps me back at the menu.
Plz help me
Dk

I had the same issue hboot would search but than drop me back at main menu. This pc36 file woorked for me found it in another post let me know if it works.
View attachment PC36IMG.zip

jdh10475 said:
I had the same issue hboot would search but than drop me back at main menu. This pc36 file woorked for me found it in another post let me know if it works.
View attachment 438729
Click to expand...
Click to collapse
Thanks jdh. I. Will test in the morning. Could you tell me what is in the pc36img.zip? This would be very helpful for me to know what the he'll I am flashing. Does this fox the problem for pc.zips after it, or what? Any more info?

Did you make sure you have plenty of space on your SD card and that you still have S=OFF? I would also try the eng bootloader (.76) since it comes with S=OFF by default

I do have space, but I don't have s-off. I have just run the flash exploit though, so I think that gives me a chance to flash the eng build and then turn s-off. Correct me if I am wrong. I am just trying to root. Again, s is still on

dkdude36 said:
I do have space, but I don't have s-off. I have just run the flash exploit though, so I think that gives me a chance to flash the eng build and then turn s-off. Correct me if I am wrong. I am just trying to root. Again, s is still on
Click to expand...
Click to collapse
The flash exploit still works? I figured they would have fixed that by now, thats a pretty big security hole lol
ya, if you can get the # root prompt you should be able to flash the mtd-eng and then Toast's pc36img. Once you have root his part 2 guide should tell you how to do everything.
Edit: ignore that about the flash exploit, I forgot you said you downgraded lol

Hah ya I think that might be the problem. I did downgrade to the1.47, but I think something is broke. I will wipe, and do netarchy's method of deleting two files in 1.47 and then doing toasts part two (wow, fail htc. Only two files?) and report back. I will also check md5 which I have not yet done.

HBoot 76.200

not working. i am starting to get sort of annoyed. i can't even get back to froyo.

i am going to pm steelh. if he doesnt help, i am going to go to toast. unless anybody has any other suggestions of people i should ask before going straight to the root master

Invoke the OTA updates. About 3 times until you get to 3.29.
(Assuming s-off)
Then everything will work and you can flash whatever you want.

as i said before, s is not off. i am trying to get it off. it is much harder to do in 3.29, so i tried in 1.47 and i am stuck now. no otas. i am giving it another shot right now. thanks for trying

You need to downgrade farther. Go to 1.32
Make sure the s-off file is on your sdcard before you do so. You will lose USB until you upgrade back to 3.29

thanks for the suggestion. where can i find a 1.32 pc36im.zip so i can try it? i'm not even sure if it will accept it. could you post a link? i have rooted 1.32 before, so this should be a breeze

[Q] New evo Help with Root.

Im sorry if this is else where. Been looking through different fourms and been getting different info. I am familer w/ Rooting..I rooted my hero on my mac. I've just upgrade to the hero and am trying to root it. I already check and it has hboot 2.02. Iv seen serveral post thay say its not rootable yet, but saw somwhere that it was but not haveing any luck. Can someone point me in the right direction. Thanks in advance

#1 This should be in the Q+A Section.
#2 If you checked the Q+A Section, theres a sticky that has your answer.

Check out the 2 methods below.
[ROOT] ~~~ HTC EVO - Universal Auto Root ~~~ v1.9.4 (12/22/10)
or
[ROOT][GUIDE] HBoot 2.02/2.10 SOFF - Root! The Final Frontier Edition - Upd. 12.21.10
Good Luck

Thanks, Sorry about that.
Its been a while since I messed with rooting, Last time I just rooted my here and thats was it. So I feel lost and like im starting over.

from the first link posted
http://forum.xda-developers.com/showthread.php?t=838448
What is the difference from the two sets of insturctions. The first one and then the quick method. and which one should i follow?
Thanks

Please hellp im stuck
I followed the instructions from the link about when i get to step 5. I get a few erros but i continue as it says. When I finally get into recovery..(black background with green wording) i make my nandriod backup. then i go and do a full wipe. when i got to flash my rom it goes all the way through and errors out at the end. this is the error i get
assert failed write_raw_image
Installation aborts because of "Status 7
what am i doing wrong??
now when i turn on the phone it just shows the black screen with the picture of the phone and the red triange on it.
Thanks

Here is an easy step by step method thats about as easy as it gets:
http://androidforums.com/evo-4g-all-things-root/194918-rooting-dummies-extras.html

Im not looking to root just want to restore my phone. Can someone please help me?

Try to download and install an official RUU then. Pick the build version that matched the build of your phone before you tried rooting....assuming it might be 3.30.651.3?? since your HBOOT is 2.02.
Supersonic Shipped ROMs
EDIT: You followed the steps in post 1 of that root method thread right? I didn't see it mention anything about continuing if you encountered errors?? But if you said you wiped the phone and the ROM didn't load properly, then you prob don't have a ROM installed and encountered errors during root...you might also not be NAND unlocked. So if you can run the RUU, it should put you back to stock.

i have tried the ruu and it keeps saying my bat is less then %30 when its not.

stamason said:
i have tried the ruu and it keeps saying my bat is less then %30 when its not.
Click to expand...
Click to collapse
What is your battery at?
(Because unless my phone is above 45% I'll get that message)

its almost full i used my old hero to charge it. is there a way to force it to update..

Thanks for all the help
Well I finally got it back up and running to factory settings.. Thanks again to everyone for your help.

[Q] HTC Incredible running 2.3.4 and 2.15.10.07.07 - Please help get S-OFF

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.

[Q] MAJOR PROBLEM. Cannot S Off or Radio S-Off. BOOTLOADER CORRUPT

Hi everyone
I was advising somebody on rooting their Desire HD.
We got as far as installing the 1.32 stock ROM and I stupidly (and now I regret it so damn much) forgot about radio S-offing the device first so we tried Eng-S-Off. That said do not turn off the device because the bootloader is corrupt.
Then we tried the Radio S off tool and that said Unknown error, possibly connection.
How can we fix this?
EDIT: Will installing an RUU fix it?

raze599 said:
Hi everyone
I was advising somebody on rooting their Desire HD.
We got as far as installing the 1.32 stock ROM and I stupidly (and now I regret it so damn much) forgot about radio S-offing the device first so we tried Eng-S-Off. That said do not turn off the device because the bootloader is corrupt.
Then we tried the Radio S off tool and that said Unknown error, possibly connection.
How can we fix this?
EDIT: Will installing an RUU fix it?
Click to expand...
Click to collapse
Ya it will just do that way and do the rooting again after following these steps.....
find the stock splash screen here: http://forum.xda-developers.com/showthread.php?p=15430340&highlight=stock#post15430340
Uncompress that and put the .img file in the same folder as your fastboot file (in the Android SDK, it used to be in the Tools folder but nowadays they put it in the Platform-Tools folder), then open a CMD window, (Make sure the file is called splash1.img) and type:
fastboot flash splash1 splash1.img
That will restore the stock splash screen.
To restore the software you have to:
1: Find a 1.32.405.6 RUU that matches the original state of your phone. 2: Flash that RUU 3: Use Visionary R14 to Temproot and then Permroot 4: The Jkoljo's Easy Radio Tool to change the CID back to stock (If you phone was unbranded it will be HTC__001)
Now its ready to root again...
Hope that helps.

No I'm saying because the bootloader is corrupt, will installing an RUU restore the original bootloader?
There is no custom splash screen. We got as far as installing the 1.32 ROM.

raze599 said:
No I'm saying because the bootloader is corrupt, will installing an RUU restore the original bootloader?
There is no custom splash screen. We got as far as installing the 1.32 ROM.
Click to expand...
Click to collapse
I honestly think people are just copying and pasting stuff they've read somewhere without thinking about what they're saying. The bulk of that is nothing to do with the query you asked (apart from maybe the line about the RUU); I mean, replacing the splash image?! How's that going to help with a corrupted bootloader? Let alone telling you to download the full Android SDK just for that
On topic: the RUU should do it, but I've never tried it myself so you're probably safer waiting for someone with some actual experience to confirm before you flash. I have seen that error mentioned in one of the guides I used back when I rooted (January time), so I'll see if I can dig that out.
//sent from my Desire HD using Tapatalk; all errors entirely intentional.
---------- Post added at 08:07 AM ---------- Previous post was at 07:42 AM ----------
Okay, found it: a few people were having "bootloader corrupt" issues using the One-click ENG S-OFF tool.
Try the advice in that post (or maybe search that thread a bit further for mentions of "corrupt") before you waste time flashing a RUU. IIRC you can do Radio S-OFF & ENG S-OFF in any order (the ENG S-OFF tool has a box to tick whether you have Radio S-OFF or not); I don't think that's the problem here.

Thanks I will try that later. It seems like from the thread that if you didnt get a superuser message on the phone, nothing actually happened to the bootloader. We didnt get a superuser message on the phone. So could it be a false alarm and safe to reboot?
EDIT: By the way what the other user copied and pasted, I wrote originally lol but I didnt want to say that then in response.

raze599 said:
Thanks I will try that later. It seems like from the thread that if you didnt get a superuser message on the phone, nothing actually happened to the bootloader. We didnt get a superuser message on the phone. So could it be a false alarm and safe to reboot?
Click to expand...
Click to collapse
Yeah, that should be fine. If you didn't allow it root access when you ran it then it's not going to have been able to do anything. Reboot, clear the request in your superuser app and start again.
You don't mention it, but I assume you've already used Visionary to permroot before you tried the S-OFF tool? Just a thought when you mentioned you didn't get the su request on the phone.
raze599 said:
EDIT: By the way what the other user copied and pasted, I wrote originally lol but I didnt want to say that then in response.
Click to expand...
Click to collapse

Lol this is quite funny. I was actually instructing him over skype and then when I left Skype last night he did something and it worked lol THANK GOD!
I have no idea what he did but wierd things happen when I'm not looking lmao
Still though, since we have had some major problems, do you recommend that we install an RUU and start again from scratch? Just to avoid any future problems?
EDIT: Yes it was Permrooted, the superuser came up when he tried it himself and it worked.

I wouldn't bother personally; as long as you're s-off it doesn't matter how you got there. It's not like the phone's going to be left half s-on or something.
Besides, why let him waste time redoing that when he should be using that time to flash a load of new ROMs
//sent from my Desire HD using Tapatalk; all errors entirely intentional.

Thanks very much