[Q] Reverting to Stock Completely - Droid Incredible Q&A, Help & Troubleshooting

I have been having issues lately with my incredible (launch batch) overheating and shutting off without any cpu intensive processes running. My setup is
CyanogenMod 6.0.1-Inc
Rooted, S-Off
Radio BaseBand 2.15.00.07.28
I'd like to revert completely back to stock to see if the issue is a hardware problem, a particular application, or the rom itself (although based on http://forum.xda-developers.com/showthread.php?t=856369 it doesn’t seem like this’ll fix the issue, I would need stock anyways to RMA it). Problem is, I haven't been able to find any guide that is relatively recent. I have looked at the following guides/faqs:
http://unrevoked.com/rootwiki/doku.php/public/forever
http://forum.xda-developers.com/showthread.php?t=726791
but I am not sure if any of them are up to date, or are for my situation. From my understanding the procedure is something like flashing PB31img.zip (where to get this, I'm not sure) and re-locking the nand (to s-on) using unrevoked forever.
Is there any particular set of instructions that can be recommended to follow? Or do any of the guides listed above have the correct relative instructions for what I am trying to do?

Use this guide:
http://forum.xda-developers.com/showthread.php?t=786436
And use part 0 and part 2, DON'T USE PART ONE
I repeat, DO NOT USE PART ONE.
And you're done.

that looks exactly like what I needed, thanks! I'm not sure how I missed that post while searching the forums though. I'll try this tonight and report back.

Always glad to help

That guide worked like a charm. Granted, I'm still having the issues random reboot issues I was having before, but that's a whole other issue.
Thanks again wdfowty.

Related

Help with unlocking NAND

Okay, I know this is a total newb question, and I hope I won't get flamed for it.
I used Unrevoked3 in order to root my phone. I do have root access (Titanium Backup, Superuser Permission, Wi-fi tether all work) but my HBoot is still 79.0 The NAND is still locked and I figured out that I have to unlock it to install some custom ROMs, especially the CM nightlies which is what I want.
So I tried Toast's Rooting and Nand Unlocked Method, I tried Biles, I tried Simpleroot OTA (for about 7 hours and it drove me ****ing mad), and nothing seems to work so far. Every single PC36IMG I download from the forum threads, no matter what, the bootloader always gives me the 'Main Version is older!' fail message and refuses to load it.
Can anyone offer help? Step by step directions? Anything like that?
I've seen a lot of people with this issue, but I never saw the fix for it. What software version are you on now? 1.47? If so, if you don't care about losing everything, you might want to start over by running the stock RUU for either the original 1.32.651.1 or 1.32.651.6 ROMs.
http://forum.xda-developers.com/wiki/index.php?title=HTC_Evo_ROMs
Then you can start at the top and do it right. I flipped back and forth between toast's and TheBiles' tutorials, and I had no problem.
By the way, you are using the OTHER version of the PC36IMG.zip file for the 2nd part of the guides, right? There are two versions you need to use, you can't just re-use the first one when you need to do the second re-flash for full rooting. There is also an order when you're pushing those four files (including the recovery.img and the flash_image and whatever that other one is) because you have to set permissions, then run one, then upload another one, etc.
Let me know if you want a walkthrough, PM me or something.

Bricked Desire, possible SLCD model, need help please

Hi everyone
I posted earlier asking for help on rooting and flashing custom roms. I was kindly given the link to the complete guide in the desire development section.
I followed all the steps and successfully created a goldcard and flashed the device with the stock rooted desire rom, however that's as far as I got as now my phone's screen won't work at all. This is what makes me think it's an SLCD model as I've heard such problems as well.
I've tried using unrevoked to flash the slcd modified recovery image, that doesn't work either. I've all drivers installed correctly and followed everything precisely.
Any help will be greatly appreciated.
What rom exactly did you flash with?
I followed this guide theunlockr.com/2010/06/07/how-to-root-the-htc-desire
Basically I got as far as applying a stock Desire rom that was rooted. After that the screen no longer works. The phone itself works as unlocking and locking prompts the phone to light the hard buttons and also receiving calls work.
At this pointI'm not fussed if someone can tell me how to put a rom on there that will work whatever it be, i'll ust have to do it blind as I can't use the screen. I've got the goldcard ready.
A ROM guaranteed to work is the official Froyo. It cannot be rooted:
http://shipped-roms.com/shipped/Bra...3.00.32U_5.09.00.20_release_140022_signed.exe
An earlier ROM may work but it would depend on which ROM you flashed.
Thank you for replying, I will try this in the morning as I need sleep
Can you let me know if this will fix the problem with my screen not working?
Yes, that's the point of it...
You might want to view teppic74's FAQ as well...
http://forum.xda-developers.com/showthread.php?t=749551
My situation was a bit different.
I got an Asian ROM & wanted the European ROM. I followed 1 of the guides here & somehow i got a black screen (SLCD brick), possibly because I got the wrong RUU.
Found this link http://forum.xda-developers.com/showthread.php?t=748498
I followed method 1, didn't work.
But method 2 is a cure.
dsymbol said:
My situation was a bit different.
I got an Asian ROM & wanted the European ROM. I followed 1 of the guides here & somehow i got a black screen (SLCD brick), possibly because I got the wrong RUU.
Found this link http://forum.xda-developers.com/showthread.php?t=748498
I followed method 1, didn't work.
But method 2 is a cure.
Click to expand...
Click to collapse
That thread is out of date now. See the FAQ instead.
Thank you ever so much for that link teppic I had come across other stock ROMs however I hadn't come across that one, this has sorted all my problems and got me 2.2.
Thank you ever so much
Sent from my HTC Desire using XDA App

Need to return to stock but phone display does not work

Ok guys, I really need some help, this is proving far too difficult Im sorry for the long story, and i feel its gonna be really unclear whats actually happened but please bear with me and i will try and answer all your questions, i just need help!
I have a Desire Z (UK spec that is), which needs to be sent for warranty as the screen isnt working, the display is completely gone, bar 1 or 2 white vertical lines.
I rooted and S-off'd using the uberroot method, which i find out now is discontinued. I also has CM6.1.1 on the phone. Now I have used a program called Screencast to display my phones display on my laptop, and i managed to restore my stock rom backup (can you imagine how intense it was praying that the phone is restoring the backup without being able to veiw what the phone was doing!!! but it worked so wahey!)
Now i need to get back to S-on, and unroot. I knew i used gfree to get s-on but i coudlnt work out how i did it because i dont have adb installed on my laptop. I then realised i used the uber root method, which had all the needed files in one folder, and i ran adb from there. I have the partition 7 back up, which i have renamed as the wikis instructions.
The new gfree says i can just use the command gfree -s correct? But can i still do this given that i used the older gfree version? Or should i follow the intructions at the bottom of the wiki to restore that partition?
Also, do i need to get rid of clockwork mod? or has that been removed due to flashing a stock rom?
If you flashed a full stock rom then recovery should have been replaced with the stock version as well. If you just performed a restore of a backup through rom manager gui, then cwm is still on there. It's a bit unclear from your description what exactly you did to return to stock. To check if cwm is still on there you can turn off the phone and boot into recovery using that key combination that I can't seem to recall right now (vol down was hboot, trackpad I think it was...). Once booted into recovery you have ADB access to the phone. If you don't, then the stock recovery is most likely back in place.
As for gfree: you can use the current version to restore s-on status and that's also the safest way, really. It's not perfect, as the old gfree made quite some changes there with sim unlock and cid and what not which would be obvious if someone looked at the radio configuration. S-ON/S-OFF itself is determined by a single bit only. But then, it is highly unlikely that anybody at HTC would bother to check that deep, especially with a defective lcd - they just look for obvious things like physical damage or water damage.
EDIT: oh, what about hboot? Did you replace that with the engineering version? If so, that too would have to be restored to stock if you wanted to be perfect and leave no traces at all.
EDIT2: Technically, I think they couldn't even refuse warranty even if they found cyanogenmod on there as the lcd failure can hardly be attributed to that. I'm not quite up to date on the legal situation in the UK, only here in Germany, but that kind of thing has been mostly harmonised throughout the EU, so the differences shouldn't be too big.
I don't understand exactly, but flashing with ruu should amake desire z as never been touch as far i know. As far I know too, there would be a difficulty to regain s off, root with latest ruu.
Sent from my HTC Vision using XDA App

[Q] HTC Boot Screen Freeze

Google brings back a lot of people who have this problem but no-one seems knowledgeable enough to have a fix for it hence my post here. Since I followed the How to downgrade, Easy S-Off and the tried and tested radio.img flash guides and flashed Leedroid (13/01 epic stable build) I've had an infrequent (i don't reboot much) problem with my DHD freezing on the HTC screen during boot. I've solved this in the past by reflashing (as I can still enter the bootloader and Clockwork Mod) from an SD card but this is getting annoying.
The people on Google who are having this problem have said they've returned their phones however If I were to do that I would have to go straight to HTC as I got mine from eBay, are HTC going to helpful in this situation?
So Is there a known fix for this that I'm missing? Maybe the latest Leedroid?
On a side note if there is no fix is it even possible revert my DHD to level of stock such that HTC won't know I've been mucking around with it? I took to easy S-Off route that apparently can be reversed and I didn't SIM Unlock it but due to my over confidence I can't be sure I kept all the backups of the stock stuff that I should have kept.
Anyway, thanks guys. I'll just hang out here with no phone for a bit hoping there is a way to get it to boot because I'd really hate to lose some of the MMS message I've been sent .
You should do a full wipe and try a new rom, for example the newest LeeDroid or Android Revolution HD.
It is possible to revert to stock so that HTC will never know, just follow the S-ON instructions in my Radio Tool thread.
jkoljo said:
You should do a full wipe and try a new rom, for example the newest LeeDroid or Android Revolution HD.
It is possible to revert to stock so that HTC will never know, just follow the S-ON instructions in my Radio Tool thread.
Click to expand...
Click to collapse
Many thanks for the reply. I did a ClockworkMod wipe and went for the new Leedroid (I've no idea if its the best but it was the first I spotted after rooting my phone), guess I'll have to wait and see if it happens again but touch wood no problems so far.
I've just been looking through the Revolution thread and spotted your wipe tool so if it does happen again I'll try that. I'd also like to say many thanks for your s-off thread, its very well written and easy to understand, and your work supporting the DHD is outstanding.

[Q] Desire Z first time root questions, please help

Hi, I am have just got my HTC Desire Z/Vision and I am very new to rooting.
I checked on a lot of thread on how to root, s-off the phone before I can install custom ROM.
Some of the tread mention that I need to do firmware downgrade if my device has firmware version higher than 1.34, but I am not sure on my version and therefore I include my information below.
What is the easier way to root my phone?
If I use gfree, do I need to downgrade my firmware? Is there any side effect when I downgrade my firmware?
If I use VISIONary, do I need to downgrade my firmware?
Do I need to do S-Off in order to install custom ROM? or is rooting enough?
Hell a lot of question but I hope you guys can help me out with it.
Android version: 2.2.1
Baseband version: 12.28e.60.140fU_26.04.02.17_M2
Kernel version: 2.6.32.21-g6e170e7
Build number: 1.82.707.1 CL317545
Software number: 1.82.707.1
cruxiality said:
Hi, I am have just got my HTC Desire Z/Vision and I am very new to rooting.
I checked on a lot of thread on how to root, s-off the phone before I can install custom ROM.
Some of the tread mention that I need to do firmware downgrade if my device has firmware version higher than 1.34, but I am not sure on my version and therefore I include my information below.
What is the easier way to root my phone?
If I use gfree, do I need to downgrade my firmware? Is there any side effect when I downgrade my firmware?
If I use VISIONary, do I need to downgrade my firmware?
Do I need to do S-Off in order to install custom ROM? or is rooting enough?
Hell a lot of question but I hope you guys can help me out with it.
Android version: 2.2.1
Baseband version: 12.28e.60.140fU_26.04.02.17_M2
Kernel version: 2.6.32.21-g6e170e7
Build number: 1.82.707.1 CL317545
Software number: 1.82.707.1
Click to expand...
Click to collapse
First, welcome to the boards, it's always nice to welcome people into the world of rooting and flashing (the android kind!).
To start, you will have to get ADB installed and working. To do this, download the Android SDK from here: http://developer.android.com/sdk/index.html . make sure you have the Java SDK and JDK installed as well as the Android SDK requires that as a requirement.
Based on your information, you have the 1.82 system software and will need to downgrade. I am not 100% sure if this guide will be applicable to you since it was written for the 1.72, but look at this guide here: http://forum.xda-developers.com/showthread.php?t=905261
The above guide will help you in downgrading to 1.34, gaining root with gfree/rage, SIM-Unlock and S-OFF, installing ClockWordMod (a.k.a CWM) and flashing a new and shiny ROM for you.
I can completely understand how confusing alot of these guides can be, I spent about 3 hours trying to do the same thing as you a month ago. A year ago, I did the same thing with my old HTC Hero! So if you have any questions, just ask away. XDA is a great community.
Have fun
Thank you for your reply. It does help me to go through the right direction.
Understood that I need to downgrade my build to 1.34, but is there any major difference between my current build and the older build?
After following the guide to downgrade and install CWM, will it also allow me to backup my current official ROM?
As I love HTC Sense too much such a pity that I need to let it go. I am thinking of flashing back to the official ROM when I have the need to.
XDA is indeed to a great community. Great helps from great people
cruxiality said:
Thank you for your reply. It does help me to go through the right direction.
Understood that I need to downgrade my build to 1.34, but is there any major difference between my current build and the older build?
After following the guide to downgrade and install CWM, will it also allow me to backup my current official ROM?
As I love HTC Sense too much such a pity that I need to let it go. I am thinking of flashing back to the official ROM when I have the need to.
XDA is indeed to a great community. Great helps from great people
Click to expand...
Click to collapse
There are alot of fixes and improvements that HTC made between the 1.34 version and the newest 1.84 version. Those would be found with HTC in their changelogs. Also, each of these upgrades breaks the root access that the devs have created. Similar to that of iOS breaking each jailbreak method with each new version of iOS that is released (you will understand this analogy if you have an iPod Touch or something along those lines).
After gaining root, SIM-Unlock and S-OFF, installing CWM would allow you to perform a NANDroid backup (an EXACT image of your current installed ROM) so that you can go back to it at a later time.
If you are like myself (and seems that you are) you love how HTC's Sense overlay works and it just gets you. Keeps things simple while being infinitely customizable. When you do get around to flashing, I would recommend Virtuous as your ROM of choice. It is what I am running right now with no ill effects. The link to Virtuous is in my signature below.
If this is your first time flashing a custom ROM on an Android device, I can promise you that you will NEVER have a reason to go back to the stock ROM unless your phone is damaged physically and needs warranty repair. Even then, it is sometimes cheaper and easier for you to order the parts online and DIY your repairs (did it for my brother's BB Storm when he broke the screen).
Going back to my Hero, I have the stock Android 1.5 image saved somewhere, but I have never had to go back to it. Always found another newer/better custom ROM to flash. With my current DZ, I was fortunate enough to have stumbled onto Virtuous.
Have fun!
Yes, you're right. I like HTC Sense so I don't know if I will get used to the custom ROM without it.
I have checked on the Virtuous ROM previously and I will give it a try.
Yes, I saw plenty of decent ROM, they have nice UI but as you know first time rooting does give me goosebumps.
Will try it and I hope everything goes smooth.
Thanks a lot for your kind explanation, it does save me time in putting up all the pieces together
I bumped into a problem as I try to downgrade my firmware.
I followed the guide on this thread http://forum.xda-developers.com/showthread.php?t=905261 and I encountered error on step 11, when the phone goes into bootloader mode and tries to scan PC10IMG.zip file that I copied into the SDCard.
It said 'CID' incorrect!, Update Fail!
Anybody knows why I might have this issue? Is this because of the firmware difference as mentioned by Athrun88?
cruxiality said:
I bumped into a problem as I try to downgrade my firmware.
I followed the guide on this thread http://forum.xda-developers.com/showthread.php?t=905261 and I encountered error on step 11, when the phone goes into bootloader mode and tries to scan PC10IMG.zip file that I copied into the SDCard.
It said 'CID' incorrect!, Update Fail!
Anybody knows why I might have this issue? Is this because of the firmware difference as mentioned by Athrun88?
Click to expand...
Click to collapse
As stated in the thread you are using to downgrade, your CID must be one of the following:
g4rb4g3 said:
If your INFOCID is NOT one of these you need to make a goldcard to downgrade!
HTC__001
HTC__032
HTC__E11
HTC__203
HTC__Y13
HTC__102
HTC__405
HTC__304
HTC__A07
HTC__N34
HTC__J15
Click to expand...
Click to collapse
IF its not in the above list you must make a gold card first then use the thread that you listed to downgrade. To check your CID run the following commands:
check with:
Code:
adb reboot bootloader
fastboot oem boot
Click to expand...
Click to collapse
There is a link in the thread you listed on how to make a gold card. The method you are trying is comfirmed to also work with 1.82. So the reason you are having problems is NOT because your on 1.82 firmware, more than likely your CID is not listed above. Solution = GOLDCARD.
Thank you for the reply.
I have looked into the Goldcard method (http://forum.xda-developers.com/showthread.php?t=832503) and actually spent my time trying to accomplish the result.
Part 1 and part 2 are pretty straightforward but now I bumped into another problem when I tried to do part 3 as it requires me to have root access to execute the command.
I have tried to get the root access by following methods from different threads such as using rage (http://forum.xda-developers.com/showthread.php?t=834228).
For this method, I tried to do temp root and I am stucked on step 5. After launching 'Terminal Emulator' and running 'rage'. I can't seem to run the 'Terminal Emulator' again. When I launched it, it Force Closes. Tried to launch it again, my phone just displayed black screen and keys doesn't seem to be responding not till I off and on the phone (not reboot).
I also tried to use Visionary too but doesn't seem to have any luck.
Is there any other method I can try to get the root access?
Another question is after I followed Part 1 of the steps in http://forum.xda-developers.com/showthread.php?t=832503, when I boot up my computer, I can't seem to go to Windows. I am sure I selected physical disk instead of logical disk but I don't know why this happen. Anybody encounter the same problem?
I'm currently in the situation of wanting to root and S-off my Desire Z in order to update, either to official or (more likely) Virtuous ROM.
However before I do so I have a couple of questions.
1) How do I back up everything on my phone? I know my contacts and calendar will be fine as they are from my google account, also my email will be ok as that is also my google account. Photos etc I can just copy to my PC but what about all the apps I've installed, and my progress in them, my pair bluetooth devices, my wifi access points, my mesage apn settings etc etc?
I have tried Titanium Backup but not having paid for the full version, the info it gives you is a little limited so i'm not sure what it's backed up etc?
2) I currently have root via using Visionary, do I need to unroot and then go through the process with all the adb stuff? Also, will i need to uninstall the SuperUser I have installed?
3) I think my ADB is setup as I managed to get it to boot the phone into the bootloader, but when Itried to check my INFOCID using
Code:
fastboot oem boot
I got an error message saying that fastboot was not a recognised function (or something similar to that) Is this a problem?
ANy help really really appreciated as I am a total newb with Android but would love to move to a more up-to-date software version as I am currently on 1.34.
Thanks in advance.
valve90210 said:
I'm currently in the situation of wanting to root and S-off my Desire Z in order to update, either to official or (more likely) Virtuous ROM.
However before I do so I have a couple of questions.
.......................... lots of questions...............
ANy help really really appreciated as I am a total newb with Android but would love to move to a more up-to-date software version as I am currently on 1.34.
Thanks in advance.
Click to expand...
Click to collapse
You could wait until HTC releases a OTA update for your phone. Or as a alternative and avoiding being impatient, you could do a lot of reading and learning on this site to apply a custom rom. It is not that difficult at all, but do not expect a step by step walking trough the minute you ask for something here.
HLeenders said:
You could wait until HTC releases a OTA update for your phone. Or as a alternative and avoiding being impatient, you could do a lot of reading and learning on this site to apply a custom rom. It is not that difficult at all, but do not expect a step by step walking trough the minute you ask for something here.
Click to expand...
Click to collapse
Wow, thanks for your helpful post...
I've done loads of reading on the forum and have gone rather round in circles. I think I know what I'm doing but seeing as someone else who is new to it had posted a thread I thought I'd also ask a couple of questions that I had which were pertinent to the discussion, to firstly find out for myself and secondly to help anyone else that might be finding the thread otherwise useful.
I think I have sorted the abd problem I was having, it seems that various tools have moved to different folders in the latest version of the android sdk so when I was trying the "fastboot" line it was nt findint fastboot.exe as it was in a different folder.
Secondly I'm fairly happy to give the gfre stuff a whirl but before I do I just wanted a little confirmation about backing everything up...not a huge ask really and fairly essential I would say!
valve90210 said:
Wow, thanks for your helpful post...
I've done loads of reading on the forum and have gone rather round in circles. I think I know what I'm doing but seeing as someone else who is new to it had posted a thread I thought I'd also ask a couple of questions that I had which were pertinent to the discussion, to firstly find out for myself and secondly to help anyone else that might be finding the thread otherwise useful.
I think I have sorted the abd problem I was having, it seems that various tools have moved to different folders in the latest version of the android sdk so when I was trying the "fastboot" line it was nt findint fastboot.exe as it was in a different folder.
Secondly I'm fairly happy to give the gfre stuff a whirl but before I do I just wanted a little confirmation about backing everything up...not a huge ask really and fairly essential I would say!
Click to expand...
Click to collapse
You can use Astro File Explorer to back up your apps, Call Logs Backup and SMS backup will backup the sms threads and call logs or if you want to spend a couple of bucks Root explorer works well for me also. Once you have CWM you can make a Nandroid backup and will have an exact image of you phone at that point in time that you can go back to. I am waiting for my DZ to arrive and currently using an Inspire and 2 Captivates that other than minor differences in the procedures the backup maintenance is the same. The problem is that if you downgrade to a rom that allows CWM you cant back up the existing newer one. There are copies of it out there though. Just be careful if trying to go back to it and read carefully as I understand there are possible problems going back if the correct procedures are not followed. Good luck to you and as the previous poster stated about educating yourself, I fully agree. Read until you understand then read again to make sure you are not missing something. Follow directions EXACTLY and it usually avoids problems.
Sorry I see you are on 1.34 which I think means that once you get S-Off and root you can download rom manager from the market, install clockworkmod and you will be good to go with Nandroid backups.

Categories

Resources