Hello everyone!
I am going to attempt to revert my Desire Z back to stock because I would like to send it in for repairs due to a broken screen. My phone is BELL branded Desire Z, and I got it only a couple months after it came out, stock version is probably around 1.34 I think..? I would provide details but the screen doesn't work and I'm not aware of any command line tools to retrieve that data. (Screen is solid black)
My issue is this:
I am currently running Cyanogen mod 6.1 with Clockwork recovery. I have S-OFF, and CID is whatever it was when I got it. (rooted with rage + gfree and didn't change the CID)
I know I have to install the Bell stock firmware, that being bell's ROM with sense UI, radio and recovery, but I'm not sure what order to do it in, or if I can just use the RUU (older version, the one that came with my phone so that I can obtain root in the future)
I seem to have the impression the RUU checks a version number of some kind and if flashing an older version number, it will not flash. (I could be wrong, that's what I need you for) It is also my understanding that the RUU flashes EVERYTHING, radio, recovery, hboot, etc. Can I use the old(er) RUU to flash my phone back to factory with out doing anything first? Again I've got CM mod 6.1 on there with the clockwork recovery, S-OFF, and regular hboot and CID.
Also, my screen is broken and I cannot see anything on the display, however, last time I checked I could still use the touch screen, although blindly, so if you have anything to help me, command line style is preferred.
Also, I'm not new to linux, I've been using it on my laptop for about 2 years, and I'm in school for programming (beginner still), so lay on the technical stuff, more than anything I'd like to learn...
Thanks for your help!
Related
Hi,
I'm at my wits end.
I've spent ages (most of last night and all of this morning !) looking through google and This forum, XDA developers etc etc etc and I'm no further forward
I have/had (not sure where I am at the moment.. will explain in a minute) a rooted Desire on FroYo. then my Desire started the overheating problem and randomly rebooting every 3 to 5 minutes. The only way I can keep it running long enough to do anything is to use an ice pack and chill the phone !
Anyway I tried to do a roll-back and lose root access etc and return my desire (UK Vodafone) to stock so I can send it in for a repair.
I initially used my nandroid backup to roll back to the previous version of my software, then I re did the official OTA to 2.2 and it SEEMED to work.. except I still seemed to have root access.. I certainly had the Superuser application in my applications list.
Apparently to delete superuser (or is it Superuser with capital S? I seem to have both?!) You need root (figures!) so.. ran unrevoked again, seemed to unroot again but :-
(a) try as I must i can't uninstall Superuser.apk. Tried using root manager, terminal and adb but I keep getting errors saying something about read write permissions?
(b) I have also read that I may need to restore the official Android recovery (have clockwork mod recovery at the moment) that needs to go too.
I just want to return my Desire back to store/factory.. but I can't seem to do this.
I'm feeling thick as cold mince at the moment.. Seems the process differs depending on different HBOOT versions/ device versions / root methods / day of week / alignment of the planets !!!
can anyone PLEASE help with an idiot (and boy do I mean IDIOT) proof guide to get rid of all traces of my naughtiness and back to a warranty friendly 2.2 Desire??
I think the simplest way is to use the windows-based RUU update files from shipped-roms.com as they'll replace your recovery with a stock one and unroot your phone (sends it completely back to stock vodafone).
The only vodafone UK one i see on there is..
http://shipped-roms.com/shipped/Bra...00.28U_4.06.00.02_2_release_126338_signed.exe
There are a couple of caveats:
1) you may need to downgrade your hboot before the RUU will sucessfully flash the phone. There's a bunch of threads in the developer forum on how to downgrade hboot, depends on your screen type, which leads to...
2) this is kind of important, is your screen SLCD or AMOLED? The vodafone uk RUU is dated mid-june, so it will almost certainly only work on AMOLED desires. If you got the phone before mid-july it's definitely AMOLED but if you're unsure there are threads about how to check (i think the easiest way is to pull up a dark screen such as the settings menu in a darkened room and see if the black areas of the screen are true black or just very dark grey like on an LCD pc monitor).
Providing your phone is AMOLED, once you've installed that RUU you can use the OTA upgrade in the about phone menu to go from 2.1 to 2.2.
please report back if you have got rid of Superuser that way because i have the same problem
i formatted my sd card and then updated OTA2.2 and for some reason i still have Superuser and i plan on returning to warranty for camera problems
supriz said:
please report back if you have got rid of Superuser that way because i have the same problem
i formatted my sd card and then updated OTA2.2 and for some reason i still have Superuser and i plan on returning to warranty for camera problems
Click to expand...
Click to collapse
Thats because the OTA (in contrast to a RUU) does not install a completely fresh image of the /system partition (where the root files normally are installed) but just replace/patch most of the existing files. Other files, like su will stay untouched.
You also won't be able to just remove those files as you are obviously s-on, which means even root can't write to system easily.
Some options for you are:
- find a RUU that fits your device and install it (there will be lots of instructions for flashing around) €: Watch out if you have an SLCD!!! Can't state that often enough...
- S-off your device, remove all root files from /system, flash the original recovery/splash/hboot via fastboot (this might help)
i had the same problem, i solved it by flashing a RUU then rerooted. i am fine now
unrooting the original stock rom
Hi guys, I have a similar problem. I rooted my desire with unrevocked 3.21 and everything was fine.
BUT I havent flashed any new rom, I still have the original rom, I was only interested in rooting.
Now I need to sell my phone so I want to restore factory settings.
Can I do it with just doing a "factory reset" or I need to flash using the RUU....exe?
thanks for your support!
Just to be safe use the ruu
Sent from my HTC Desire using XDA App
Help, I had a quick look about and couldn't find a similar thread, apologies if the is one tho as there is a lot to look through here and may have missed it.
Story is, I brought my desire z about a month ago not sure what software version it had but I preceded to flash it with a downgraded version ( 1.34.405.5 ) with a .executive RUU utility on my Windows 7 pc. Just to get used to things, I have flashed many phones before no problem.
Now tho I found what I believe to be the latest official ROM from here:
But everytime I run the thing I get error 132 signature update problem or something.
I have tried it while the phone is temp rooted, permanently rooted all the Ian drivers are fine I tried different versions of Windows. I just want to get back to the latest version and be able to update over the air from now on, thanks for reading.
What RUU are you trying to flash ? If it is the new Egypt version, please don't do it, and see the thread in the dev section for reasons why.
My DZ came with 1.34.405.5 and I have successfully flashed the RUU of this version from this forum, no problems.
It would be useful to find out what the current version is on your phone. It will tell you in Menu->Settings->About Phone.
Also it would be useful to check which HBOOT version to have, and whether you are S-OFF. Put the phone into hboot by having it powered off, then hold Volume Down and hold Power till it comes up with a white screen with skateboarding Androids.
It is possible to downgrade a ROM if you go through the procedure in this thread - http://forum.xda-developers.com/showthread.php?t=832503
Helo thanks for reply.
Im pretty sure the version i had on the phone phone was newer than the one i flashed on as i just wanted to have a trial run with a rom that definatly worked fine before trying custom ones ect.
Currently it is S-On HBOOT version is 0:85:0009 and software version is 1.34.405.5 (the one i flashed over the stock)
I cant link to the RUU i am trying to use but it says it is a WWE world/europe one and i also tryed 3 others just incase, all give the same error.
Version is 2.29.405.2 that im trying to get on my phone as i think thats the latest official one??
Your phone sounds like it is stock so far, so it'll probably only let you flash a ROM designed for your very specific model of phone. So if the phone was from a particular country, it will probably only let you flash a ROM from that country, not just any old WWE ROM.
So is 1.34.405.5 on there properly now, up and running ? If so then you could always root it and run gfree to get SuperCID etc, which will then let you flash whichever official ROMs you want (but be careful if it's a very new ROM that might not yet be rootable etc).
I'm not familiar with any ROMs starting with version number 2 though ?
A quick google for 2.29.405.2 brings up Desire & Desire HD links.
BE CAREFUL DUDE!!!!
Yeah phone is running fine, slightly less reliable than it was before i flashed tho but im putting that down to it being a slightly older version than the one that was on here before maby.
Im up for just sticking an official desire z ROM back on here and leaving it alone for now. If you could point me in the direction of a suitable ROM download that would be great, or is there someplace i can go and put my specific phones model in and get the factory shipped ROM back cus that would be even better.
That 2.29.405.2 update is for the standard desire and desire HD? Damn that could have turned out bad had it flashed to my phone.
These smart phones seem a bit more tricky to flash than the older phones im used to doing, is there a decent step by step guide you can link me to for help with flashing as i have come accross 3 different ways already.
If your phone doesn't have S-OFF etc, then you're only going to be able to flash very specific ROMs to your phone. Since we don't really know what original ROM your phone came with, I recommend that you root your phone (using the "rage" method) and get full S-OFF via "gfree". Guides to these two are below, along with a link to a guide to get adb working on your PC :
adb - http://forum.xda-developers.com/showthread.php?t=865685
rage - http://forum.xda-developers.com/showthread.php?t=834228
gfree - http://forum.xda-developers.com/showthread.php?t=855764
Also check out this handy guide, which has a lot of useful info - http://forum.xda-developers.com/showthread.php?t=835777
You will come across a method of rooting called "Visionary". This is in theory an almost one-click method of rooting. However, I personally wouldn't recommend it, because whilst it works faultlessly for some, it goes wrong for others, and when it goes wrong it quite often goes very badly wrong indeed.
If you don't understand some of the stuff in those guides, then please post up in that thread on it, and I'm sure someone will be able to help you out. Best to ask questions first rather than try some stuff out and realise you don't know what you're doing.
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
Hi Guys, I posted this in Android Software and Hacking General, but I didn't get a reply. Probably the wrong section!
my HTC Desire GSM is stuck in Fastboot and won't boot into the ROM. The background to this issue is that I installed S-Off and then ClockworkMod and flashed Cyogenmod 7 to see if it would fix a reboot issue on the phone. The damn thing just reboots itself when the CPU is used heavily...
Anywho, after realising that Cyogen wouldn't resolve the issue I flashed the standard Virgin UK rom back over it and upgraded to 2.22.351.2 via the system update feature. The problem was that ClockwordMod was still installed and I had to get rid of it to sent the phone off for repair to Virgin!
So I did further research and found that I could flash HBoot via the AlphaRev.nl downgrader tool. I downloaded it and popped it into the root of my SD card and it flashed the bootloader back to Hboot 0.80.0000. That should have been it, but all of the sudden the phone no longer boots into the Rom. All it does is to power on and then go into Fastboot. That's it! When I try putting the standard Virgin Rom back onto the SD it tries to load it and then says "Main Version is older!" "Update Fail!".
How do I get around this now? The phone doesn't boot, so I can't re-flash S-Off and start again, not am I able to run the stock Virgin Rom within Windows because it complains about the versions.
Is there any ways around this situation? I just want to get the phone back to stock so I can send it to Virgin and get it repaired.
P.S. I *have* used the search function and spent the last 4 hours testing various things but I'm now stuck.
Cheers Guys!
Mich
Well you obviously fckd up with the Downgrader, you should have run it first BEFORE RUU. Also did you flashed Stock Hboot prior to Downgrader? (if you used CM7 earlier)
I never played around with the hboot downgrading etc. so i wont be able to help you but im sure there is some workaround...
as your returning your phone anyway why don't you try the official HTC gingerbread update from the HTC developer site (sorry I don't have a link). It should return your phone to stock and when you get it back you need to use revolutionary to get s-off back. Also, there is a sticky from user bortac which has loads of help and trouble shooting advice.
iain2510 said:
as your returning your phone anyway why don't you try the official HTC gingerbread update from the HTC developer site (sorry I don't have a link). It should return your phone to stock and when you get it back you need to use revolutionary to get s-off back. Also, there is a sticky from user bortac which has loads of help and trouble shooting advice.
Click to expand...
Click to collapse
Any advice that uses the 2.3.3 RUU to fix something is plain bad advice - it can just make your problem a LOT worse.
@OP Go onto my guide, look at RUU problems for help
What you need to do:
-Make a goldcard (there is a tutorial there)
-Flash the WWE RUU
Guys, upgrading to Gingerbread has actually brought the phone back from the dead! =) And I can now return it to Virgin to get it repaired properly. The symptoms are that while the phone is plugged in and charging, and I'm doing stuff (taxing the CPU), the phone will eventually simply rebooting itself. Just *BANG*! And it's gone. And once it starts it's a bit of a run-away thing and just keeps on doing it until you leave the phone alone for a bit. Virgin had a look at it and simply re-flashed it, thinking that they could away with that. Typical, overworked, non-creative call centre workers..... I'm well pissed off with them!
Gonna send it back next week and force them to swap the motherboard or something, cause this is a serious fault with the phone.
Hello everyone, I'm running into a bit of a problem here with my sister's HTC EVO 4G.
You see her phone is a remanufactured replacement model from Sprint, and naturally it has a few minor problems with it. She wasn't thrilled with the battery life, so I rooted and flashed CM7.1 on her phone. She liked the rom and liked the extra battery life after I did some tweaking. Two Months later, for some odd reason, her phone will not connect to the data network at all. I flashed CM 7.2, same problem. Contacted sprint, where they refreshed the signal to the phone, no luck. So I concluded that it was a hardware error. Problem is, Sprint won't work on the phone without the Stock Sense Rom installed. I thought: "No big deal, I'll just flash it back to the stock sense rom" right? WRONG.
Never have I ever been so enraged by a cellphone. No matter what I do, no matter what I try, this phone absolutely REFUSES to go back to the stock rom. I've tried flashing several PC36IMG.zip files from the sdcard in HBOOT, and I have also tried several RUU updates from my PC while having the phone in Fastboot USB mode.
Quick Info:
Phone: HTC EVO 4G
Baseband: 2.15.00.12.19
HBOOT: 2.18.0001
Bootloader = Unlocked
Security = ON (S-ON)
Trying to flash PC36IMG.zip from HBOOT results in the phone loading the zip (with the little vertical progress bar on the side) and after loading completely, it just goes on it's merry way, checking for any other zip files and then HBOOT loads normally.
Running the RUU .exe files on my computer goes smoothly right up until somewhere in the update progress I get Error 155 (Unknown Error).
Now, it's my understanding that I don't need S-OFF to go back to the stock Sense rom, but I figured I should try to get S-OFF anyways. So I downloaded unrevoked and try to apply it from CWM, and it fails stating that it's not compatible with my radio version. Funny thing is, in all the radio lists for the HTC EVO 4G, I don't see 2.15.00.12.19 anywhere. In fact, 2.15.00.08.08 seems to be the newest one, unless I'm reading the lists wrong.
Either way I'm completely stuck here, and now I have a whining teenage sister screaming at me because she doesn't have a phone on a friday night. Go Figure.. Please guys, I know I'm a noobie here, but do me a solid. Please help me out, I'm stuck, frustrated, and I'm getting to the point where it's time to crack open a beer or 3 and say "f**k it".
Thanks in advance,
Alcolawl
you dont need s-off to return to stock..try the guide below in my signature to unroot and return to stock
XenonV said:
you dont need s-off to return to stock..try the guide below in my signature to unroot and return to stock
Click to expand...
Click to collapse
Does it matter which RUU version I download? (I've been extracting the rom.zips from the RUU's temporary files). I have the most current one on my computer named: "RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.15.00.12.19_NV_2.33_release_234563_signed". I usually take the Rom from that, rename it PC36IMG.zip, place it on a freshly formatted sdcard, and reboot into bootloader and hope for the best.
well, if you want the bootloader to be returned to factory stock settings then you can follow the guide below, BUT if you just want to UN ROOT, just copy a stock rom like the one you named, and flash it thru RECOVERY menu (install zip from sd card), dont install it from the bootloader (white screen)
XenonV said:
well, if you want the bootloader to be returned to factory stock settings then you can follow the guide below, BUT if you just want to UN ROOT, just copy a stock rom like the one you named, and flash it thru RECOVERY menu (install zip from sd card), dont install it from the bootloader (white screen)
Click to expand...
Click to collapse
Sounds easy enough. While messing around and waiting for Dominos to arrive, I decided to flash MikG (first time doing so, so I wasn't sure what to expect). Lo and Behold, I updated the PRL and Data Profile, and her Data works again. She also likes how Sense looks more so than CM7. Aesthetics > Functionality in her book I guess. If it comes down to having to bring the phone to the Sprint store, I'll try flashing the image through Recovery instead of Hboot.
Thanks for the help man, really appreciate it.
Alcolawl said:
Sounds easy enough. While messing around and waiting for Dominos to arrive, I decided to flash MikG (first time doing so, so I wasn't sure what to expect). Lo and Behold, I updated the PRL and Data Profile, and her Data works again. She also likes how Sense looks more so than CM7. Aesthetics > Functionality in her book I guess. If it comes down to having to bring the phone to the Sprint store, I'll try flashing the image through Recovery instead of Hboot.
Thanks for the help man, really appreciate it.
Click to expand...
Click to collapse
no problem :good::fingers-crossed: