Related
So, after finding some amazing Black Friday deals (Inc and Fascinate for free, no activation fee!) I finally decided to get off my 6 month expired t-mobile contract.
Already rooted my girlfriends Galaxy S Fascinate (wow easiest root i've done... also what a beautiful screen.)
Than came all of my confusion regarding my inc.
I upgraded to the latest November update (I know, bad Embrace!) than realized I could not easily root it. It is the SLCD version
After hunting around all of my favorite phone forums I have found a few downgrade guides, and a lot of warning about a screen brick on the SLCD inc.
I have also read that you can downgrade an SLCD with certain rom and recovery packages(amon_ra). But I can not seem to find any clear instructions or any confirmation of what roms work and what do not.
I'm slightly OCD and the VZ bloatware is murder.
I am aware that Unrevoked is working on a fix but I would love to root this thing asap.
Thanks XDA... Second post after many years of lurking.
TL;DR: SLCD Inc, Nov OTA, Need Root.
I would suggest trying to reflash an older 2.1 or 2.2 RUU then root that.
From what I understand using the downgrade methods out there will brick an SLCD screen.
Am I wrong? I would like to think that as long as I am flashing a stock rom it won't brick anything, but If I flash the wrong recovery I will brick it.
Does anyone have any experience downgrading the latest ota with an slcd inc?
I've never had a problem rooting a phone and I rooted at least 20, but for some reason this one scares me D:
I don't have an SLCD so you'll have to wait for somebody else to chime in. As far as I know, the RUU should be fine and flashable in even an unrooted stock HBOOT since it is signed.
I would just make sure that the RUU you are using came from an SLCD phone. An older 2.2 RUU should be fine. Perhaps there are no 2.1 RUUs for the SLCD? I don't really know. But flashing a stock ROM is not going to brick a phone if it came from that phone.
So I cheated.went to Verizon told them I was having random reboots after the latest update... replaces it
Now I'm rooted
Sent from my ADR6300 using XDA App
Embrace said:
So I cheated.went to Verizon told them I was having random reboots after the latest update... replaces it
Now I'm rooted
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Whatever works works, but in case anybody else is wondering, it has been confirmed that it does indeed work if you have the latest OTA to simply flash an older RUU through HBOOT, root it and turn S-OFF, and then you can flash whatever you want on it.
Hi Everyone,
Been lurking here a long time... first on my Moto Droid and now the Incredible. Ran into my first unsolvable (by me) issue. I've had the Incredibly since beginning of December (SLCD). I rooted it via unrevoked, ran SkyRaider for a while changed roms, back to SkyRaider. I've had no issues. Last week I started getting random reboots... phone would reboot, then reboot multiple times from Incredible logo... then finally start up and my icons and wall paper would all be screwed up. Needless to say I've searched a ton and the only answer I've found is this points to a defective phone. So now I'm trying to get it back to stock - which I haven't been able to find a how-to or any info for anything as new as the current Roms. I was able to install a stock rooted rom, get s-on but then I can't figure out how to un-root it and get the stock recovery on as the only stock rom I found was rooted and that doesn't help me on the stock recovery.
Any suggestions?
Thanks,
Jon
There should be pb img you load up in hboot. I've used it worked like a charm. I'll see if I can find it and put the link up. Since you have an slcd screen also don't use any ruu's that downgrade to 2.1 it was made for oled screens it will brick the slcd screen incredibles.
just found it
http://www.incredibleforum.com/foru...s/5723-how-get-back-complete-stock-s-off.html
check that out.
shawn328 said:
There should be pb img you load up in hboot. I've used it worked like a charm. I'll see if I can find it and put the link up. Since you have an slcd screen also don't use any ruu's that downgrade to 2.1 it was made for oled screens it will brick the slcd screen incredibles.
just found it
http://www.incredibleforum.com/foru...s/5723-how-get-back-complete-stock-s-off.html
check that out.
Click to expand...
Click to collapse
Thats the version I edited from this original post found on this forum
http://forum.xda-developers.com/showthread.php?t=786436
Has all the files that are that are in the first link. Both threads unroot you to the 3.26 build and thats a good thing.
Thanks, that's the one I had followed originally and it wasn't working for me (but I had an unstable rom on there). Once I got something stable enough to boot I did the RUU method and it did the trick. Off to the verizon store today!
Thanks,
Jon
Hi,
I just got my dhd back from repair and they updated it to 2.50.405.2 -.-
Is this downgradable yet to root ? I ****in hate standard roms
Please help..
Thanks
i think versions above 2.37 can't be downgraded yet.
i am waiting for downgrade of 2.42 as well. just wait
I to have 2.50.405.2 after repair.
I found rooted this version
http://forum.xda-developers.com/showthread.php?t=1155634&highlight=2.50.405.2
But dont know will it help to change ROM.
If some one will find some solution please share it.
gingerbreak 1.2 not working with 2.50
Well, u need clockworkmod to flash it which u need rom manager for. And for rom manager u need root
I think we'll have to wait.. But the 2.37+ downgrade has been in development for about 2 months now.. Taking way to long
Probably waiting to see which bootloaders are unlocked, as promised.
Due out in September.
Sent from my Desire HD using Tapatalk
Any more on the matter, I want to downgrade so I can root?
+Nybras+ said:
Any more on the matter, I want to downgrade so I can root?
Click to expand...
Click to collapse
If u are S-OFF then u can downgrade to 2.36 by using the RUU version then root ur device,
edit:- i´ve done it more than 3times after updating from 2.36 to 2.50 "OTA" (believe me u can)
U can get the 2.36 ruu here:-
http://forum.xda-developers.com/showthread.php?p=13381205
So,if i'm novice and i don't have s-off with 2.50 only thing i can do is wait for downgrade?is that right?
Sent from my Desire HD
dwyaneW said:
So,if i'm novice and i don't have s-off with 2.50 only thing i can do is wait for downgrade?is that right?
Sent from my Desire HD
Click to expand...
Click to collapse
Now you can..
http://forum.xda-developers.com/showthread.php?t=1152233
I was waiting for this too, and now it seems like we can downgrade and root our devices. What could worst case scenario be, if something went wrong?
Have you ever rooted a device before?
Nn,im freshmani didn't do anything about this..so i need some simple manual how to do it?this link seems complicated for me nowi dont have,root,s-off etc..
Sent from my Desire HD
dwyaneW said:
Nn,im freshmani didn't do anything about this..so i need some simple manual how to do it?this link seems complicated for me nowi dont have,root,s-off etc..
Sent from my Desire HD
Click to expand...
Click to collapse
Dont worry, in a couple of hours we'll have an updated method and toolkit available to downgrade.
Edit: My Method and Toolkit have been updated.
http://driphter.com/index.php?topic=3867.0
Thanks a lot ,,, Guide from JSLEnterprises was so amazing and very helpful
can't wait to get my new ROM !
Edit:
DONE!
DHD is now rooted with Radio and ENG S-OFF.
Thank you so much.
Now moving on to flash another rom, and try and figure the whole fing about the radio out..
I successfully downgraded and rooted my desire hd 2.42.415 at last. Thanks a million JSLEnterprises. You are awesome
Trivial Question
I have a trivial question, I am very interested in rooting using this method, however I have recently encountered an issue with my stock rom ever since I did the OTA update to 2.43.611.1 The issue is HTC Sence has stopped unexpectedly window pops up quite often & in talking to telus my provider & HTC them selves, they both say the phone needs to be repaired,
My question since I encountered the problem immediatly upon doing the OTA update should I get it repaired first or just try rooting to see if that fixes it.
Also if possible can I be pointed in the direction of how to return to stock Telus if I end up rooting & the probelm still persists?
My thanks to thoes who have diligently be working & involved in helping others & myself reach root status on higher Build numbers.
Great Work!
gixer131 said:
I have a trivial question, I am very interested in rooting using this method, however I have recently encountered an issue with my stock rom ever since I did the OTA update to 2.43.611.1 The issue is HTC Sence has stopped unexpectedly window pops up quite often & in talking to telus my provider & HTC them selves, they both say the phone needs to be repaired,
My question since I encountered the problem immediatly upon doing the OTA update should I get it repaired first or just try rooting to see if that fixes it.
Also if possible can I be pointed in the direction of how to return to stock Telus if I end up rooting & the probelm still persists?
My thanks to thoes who have diligently be working & involved in helping others & myself reach root status on higher Build numbers.
Great Work!
Click to expand...
Click to collapse
The reason you're getting the error after the ota update is the same reason why people get issues after installing custom roms and not wiping their device... the old cache and user data conflicts with the update.
Downgrading and then flashing a custom rom along with flashing an updated radio will remedy the problem. I dont believe you'll want to use the initial radio release, I highly recommend flashing the radio from the 2.52 korean release to your Telus DHD, along with the ril's from that release and replacing the ones in the rom you will flash via cwm recovery. ENG S-OFF is required to flash a new radio or recovery img.
Once you downgrade, you can always return to the stock 2.43.661.1 rom. There is a thread in the Desire HD/Inspire 4G Forum on Driphter.com where I've placed the RUU's of common builds (especially for Telus and AT&T). If returning the device for warranty purposes, you must Radio S-On prior to Installing the stock rom via the RUU. The RUU Itself will set ENG to SHIP, and unroot.
Excellent, Greatly appreciated.
Might try rooting as soon as tonight. Kind of excited to have a functional device again!
I am glad that it worked, i thought OH **** the other day, when i found out that i shouldn't have updated to 2.50, if i was about to root..
Big thanks to you JSL, nice work, and easy tuturial!!
I can see that in /HTC ACE TOOLKIT
is a splash screen changer, and a boot animation changer.. how do i use them?
Cheers guys I will try that downgrade guide. Just a note though. The file fize of the version of HTC Sync for the Desire HD I'm downloading is 66.6MB. I hope that isn't an omen for this to go horrendously wrong
giusdk said:
I am glad that it worked, i thought OH **** the other day, when i found out that i shouldn't have updated to 2.50, if i was about to root..
Big thanks to you JSL, nice work, and easy tuturial!!
I can see that in /HTC ACE TOOLKIT
is a splash screen changer, and a boot animation changer.. how do i use them?
Click to expand...
Click to collapse
they're explained in coles notes way at the bottom of the 9 step thread
I have a Desire Bravo (A8181)
I installed Gingerbread 2.3.3 using the file from the HTC site.
I am not happy with it ( spontaneous reboots, drains battery, other crazy stuff)
I don't want to root so I'd just like to go back to 2.2
Can someone link to a procedure to get back to 2.2.
People are using Official 2.3.3 mostly as a troubleshooting tool or for warranty purpose.
However you cant downgrade it by RUU to lower version. The RUU will not proceed giving version problems.
The only way would be to SOFF using revolutionary and thereafter if you really want FROYO you can choose from many of the stock offerings available at Desire Development section.
My phone is not rooted
Is there anything else to do, besides SOFF and getting FROYO. Do I have to root the phone?
desirus said:
My phone is not rooted
Is there anything else to do, besides SOFF and getting FROYO. Do I have to root the phone?
Click to expand...
Click to collapse
You dont have to root the phone if you use revolutionary. But definitely will have to go SOFF. If you are worried because of brick possibility then you must know that with Android 2.3.3 the way to root is via SOFF. Actually with revolutionary SOFF is the main thing. After that you can flash a rooted rom from recovery if you want which is a low risk activity.
I would personally recommend Mildwild 5.0 based on CM7.2 as one of the most stable rom.
OK thanks
Can I use this wiki?
http://wiki.cyanogenmod.com/wiki/HTC_Desire_(GSM):_Full_Update_Guide
I think it is what you are talking about except it links to cyanogen mods, why is mildwild better than cyanogen?
Also I just went tinto bootloader and see I already have S-OFF
"BRAVO PVT1 SHIP S-OFF"
I don't know how this happened, do I still do S-OFF and install custom recovery image?
desirus said:
OK thanks
Can I use this wiki?
http://wiki.cyanogenmod.com/wiki/HTC_Desire_(GSM):_Full_Update_Guide
I think it is what you are talking about except it links to cyanogen mods, why is mildwild better than cyanogen?
Also I just went tinto bootloader and see I already have S-OFF
"BRAVO PVT1 SHIP S-OFF"
I don't know how this happened, do I still do S-OFF and install custom recovery image?
Click to expand...
Click to collapse
NO need to s-off if u r s-off, get 4ext recovery updater apk install it, run it, now u will have the latest recovery.
now u can pretty much put what ever rom u want on.
Just read instructions in the thread the rom came from and remember to NANDROID BACKUP as soon as u install the recovery.
I did manage to install Mildwild ( I couldn't get 4ext to install so I re did the s-off, rooted and installed Mildwild 5)
Thank you very much for the advice.
I still get spontaneous shutdown of my phone so I have to research this problem.
desirus said:
I still get spontaneous shutdown of my phone so I have to research this problem.
Click to expand...
Click to collapse
I think that comes from your device being a PVT1. These type of desires are known to reboot when overheating due to a motherboard problem.
Sent from my toaster
unlock the bootloader, flash a clockworkmod recovery and flash an android 2.2 rom. i think that is the easiest way.
Sent from my HTC Desire using xda app-developers app
huhu2207 said:
unlock the bootloader, flash a clockworkmod recovery and flash an android 2.2 rom. i think that is the easiest way.
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
I just ordered an original battery from HTC, if I can't find a software fix to 2.3.7 and if the new battery doesn't work then I will go back to 2.2.
But I think that because I used the official RUU from HTC for 2.3, then I have to use a custom ROM for 2.2. If I am wrong then please tell me, after all these problems I would use an official 2.2 ROM if it would make my problems go away.
desirus said:
I did manage to install Mildwild
I still get spontaneous shutdown of my phone so I have to research this problem.
Click to expand...
Click to collapse
abaaaabbbb63 said:
I think that comes from your device being a PVT1. These type of desires are known to reboot when overheating due to a motherboard problem.
Click to expand...
Click to collapse
desirus said:
I just ordered an original battery from HTC, if I can't find a software fix to 2.3.7 and if the new battery doesn't work then I will go back to 2.2.
But I think that because I used the official RUU from HTC for 2.3, then I have to use a custom ROM for 2.2. If I am wrong then please tell me, after all these problems I would use an official 2.2 ROM if it would make my problems go away.
Click to expand...
Click to collapse
The key is you still get spontaneous reboots. That means it is not related to ROM.
I agree with the assessment of abaa.... Your problem seems to be hardware related and nothing you can do other than replace motherboard. However if you want to rule out battery problems just keep it connected to charger and play a heavy game. If it reboots then your motherboard problem is confirmed.
The problem is shut down.
I haven't had rebooots
But I'll try heavy gaming while plugged in
I have a bit of good news, I think
I have made some changes to user options, according to some suggestions I found and have some good results.
After my changes, In 6 days I have had only one freeze ( where the phone was asleep and only a battery pull could fix the problem).
Before the changes I had 4-8 freezes each day, for a few weeks.
I will do some more testing but i think it is because of one of two reasons. Either because I swithced to "GSM only" from "GSM/WCDMA ( WCDMA prefered)" Or because I selected " Use only 2G networks"
I'll play around for a week or two but that is my interim result.
Incrediblec XD ship S-On
Hboot-0.92.0000
microp-0417
touch panel-atmelc03_16ac
Radio-2.15.10.07.07
Jul 23 2010, 18:06:51
Hello, first thank you for an amazing and current forum, I'd been researching my issue for a while, but most things are dated around 2010. I've experience rooting and ROMing a Droid X with multiple ROMS, but I use the original Incredible as my main phone because I still love it. Well, I originally rooted my Inc with Unrevoked3 I believe. I left the ROM as stock up until a couple months ago when I put CM7.2.0 on it.
About a week ago, the phone would always have working mobile data. Yet, if I received or tried to make a call, I couldn't and then I would lose texting ability. Then, a couple days ago, I was using the Inc for wifi tethering when suddenly it went into an Incredible bootloop. I tried booting to the cyanogen recovery, but it will quickly loop out of it as well.
I went to pvillecomp.com/ and downloaded all the stock Inc software. I individually renamed files to PB31IMG.zip and tried to have HBoot pick up on them. Hboot will see the files, but then do nothing. Except, the originally ROM will get checked and come back and say that the current version is older and can't be flashed.
I've always tried the RUU software for hboot and the original ROM. I either get a usb error or a low battery error even if the battery is charged. Granted, I'm trying the RUU from the phone's bootloader screen.
Does anyone have some support they could throw this way? I use my phone for internet and everything. Thank you all.
-Nevin
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
NevinInc said:
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
Click to expand...
Click to collapse
did you flash any radios? Flashing radios always ends up bad.
NevinInc said:
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
Click to expand...
Click to collapse
S-off, flash TWRP (because CWM sucks) and flash a new rom. This should fix everything. Flashing a radio DOES not screw everything unless you do not know what to flash, in that case you should not be flashing radios.
I'm looking into the TWRP stuff right now since I've only experience with CWM. My only concern is that I still have S-on. How can I get S-off on my phone when I've only access to the bootloader? Sorry if this is a bit off a noob post, I've simply not the experience with the incredible to know. Thank you so much.
-Nevin
123421342 said:
S-off, flash TWRP (because CWM sucks) and flash a new rom. This should fix everything. Flashing a radio DOES not screw everything unless you do not know what to flash, in that case you should not be flashing radios.
Click to expand...
Click to collapse
Btw, no I didn't flash the radio. That was the only thing I didn't attempt to flash. Yet, when attempting to flash anything else, nothing worked. Still wondering about getting S-off before using TWRP, but hopeful to still get it working. Thank you again.
NevinInc said:
I'm looking into the TWRP stuff right now since I've only experience with CWM. My only concern is that I still have S-on. How can I get S-off on my phone when I've only access to the bootloader? Sorry if this is a bit off a noob post, I've simply not the experience with the incredible to know. Thank you so much.
-Nevin
Click to expand...
Click to collapse
BUMP/UPDATE:
Yes, I'm still at it trying to get my Dinc out of it's bootloop and up/running. It's difficult at this point to say what all I've tried. At one point I wanted to use htcdev.com to ensure the bootloader was unlocked/etc. I've had much trouble trying to get fastboot to work correctly on my pc. I've seem to get stuck on "waiting for device" which appears to be a driver error.
I gave up on that and started focusing on the RUU process. I've tried to install the entire Gingerbread 605.3 file. I fixed the error usb 170 by updated or changing htc sync software. Now I'm left with error 140 bootloader error.
I've also updated hboot using the ruu process for version 605.2. This worked on my pc and got me partially excited. Now my hboot shows up as "Locked" now at the top. I also downloaded a different Stock.img file. Hboot detected this and begun the install process. Everything came up as complete and upon reboot went right back into the white screen/incredible bootloop.
So since posting before I've updated htc sync on my pc and have officially relocked my bootloader. I don't mind RUU'ing things to stock, but now gotta get past the Error 140. Any ideas?
So I'm not sure how many are looking at this or have had ideas, but I was able to use htcdev to unlock the bootloader.
Before unlocking the bootloader I was able to RUU to image .15. After this is when I unlocked the booloader. The RUU said it was complete, but I still only bootloop on the incredible white screen. Now, some of the pb31img.zip files I've come across don't even try to install. This includes signed and unsigned .15 img files. Currently these are the new settings to the phone:
Bootloader: unlocked, s-on
hboot 1.07.0000
radio - 2.15.10.12.20
Image version: 4.08.605.15
The last option I can think of is to try using fastboot, but won't that essentially do the same thing? If you think fastboot is the way to go, can u link me or give me some basics on using it. Obviously I used it for unlocking the bootloader so it can't be that complicated.
Are there any other ideas or should I give up on my Dinc? Looking forward to hear what you think. Thanx.
-Nevin
somebody recommended you install TWRP and install a stable Jellybean ROM. Did you try that?