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
Hey,
I was wondering if there is a way to give back system applications from another DHD, if previously I removed them?
E.G.:
- Copy from one DHD soundhound apk to my DHD
- Install it as system apk
- In titanium backup is recognized as system apk
So, is that possible?
Grettings
Yes, it is possible.
So there will not be any trace, that app was removed before?
If you have the .apk file, just load on your SD card and install via your favourite file manager. It shouldn't matter that the app is now installed into /data/app not /system/app .
Actual system apps like the dialer shouldn't be moved.
Well, yes thats true.
I removed amazon mp3, stock (app and widget) and soundhound. I am asking if it will not be revognized regarding to warranty. Is there any other way to return these apps as original installed? I saw something to do with RUU, but I dont have that app, also I uninstalled apps with titanium backup. Now I would like to retrieve them back and just freeze them. So in case that anything goes wrong with phone, I just unfreeze them and give phone to repair...
EDIT:
I tried with one application to copy it to /system/app and set permission as it should be (user read and write, group and others just read). After that I installed it from /system/app as I though it will be installed as system app, but it did not. My stupid thinking... :s
The RUU (ROM Update Utility) will reflash your handset back to default settings and apps. If you can find the correct RUU for your DHD then you can flash that.
You will lose any personal settings doing this, also contacts that are saved on the phone. Your SD card will remain as it is.
You should always make a backup before you remove anything, at least now in the future you will.
Yea well, it will learn me . However, maybe you can point me where to get RUU or even, how to search for correct RUU for my DHD?
Thank you alot for helping me in this crazy mess I did to myself...
Sure, if you take a look over in the dev section, one of the stickies is DesireHD Files. You should be able to find it in there.
Is your DHD unbranded?
I got it with contract of my provider. But there is no logotip of them, also there is no any applications from them, except sim toolkit, which is hided if I insert sim card from another provider (so yes, phone is sim unlocked by default). So I belive that is ubranded.
And software information:
Android version: 2.2
Baseband version: 2.6.32.21-gf3f553d
[email protected] #1
Thu Oct 28 13:24:11 CST 2010
Build Number: 1.32.405.6 CL278359 release keys
Software number: 1.32.405.6
Browser version: WebKit 3.1
I will try to search correct one and will edit this post in few mins, if I think I got one
EDIT:
By infos I gave from my phone and a little bit of compare, is it possible that this RUU is correct for me:
# RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.60.140e_26 .03.02.26_M_release_155891_signed
Should be fine, before you start ensure you have the correct HTC drivers, installing HTC Sync will ensure this.
HTC sync allready installed also sync with PC is done. Drivers should be fine as HTCsync recognize my phone. Should I do some backup with ROM manager, just in case if something goes wrong?
However I have now 4 hours to download this file, so also have time to do a backup . And after fresh install of this stock rom, first thing I will do is full backup hehe.
After running the RUU you will lose root, S-OFF & ClockworkMod Recovery, however with the RUU you are going to use, these can easily be reapplied.
Once you have done this make a Clockwork Mod backup, then if you have any issues, you have this "Virgin" state to restore to.
Andy, I really don`t know how to thank you for all your help . I just recover back my DHD with that RUU, as I though it is correct. For secure reason I checked software information and it match from start to end .
One last thing, how to make a Clockwork Mod backup?
No problem at all. I'm glad I could help.
I'm assuming you have now rooted & achieved S-OFF. From within Android Market download ROM Manager, flash ClockworkMod Recovery from within there.
Some users experience problems and have to flash ClockworkMod Recovery a second time from within ROM Manager.
Now that is done. Backups can be made from within ROM Manager "Backup Current ROM", or from within ClockworkMod Recovery.
Aha, so it should be done with ROM Manager, as I thought . I need S-OFF aswell? So back to work with Visionary and Easy Radio tool .
I own you a beer, juice or just coffee (next year Im moving from Slovenia to UK)
EDIT:
Backup is on the way
Again THANK YOU VERY VERY MUCH!
As I noticed, that this RUU is not 100% same as my old stock ROM (this one has less languages), I would like to ask you if it is possible:
- Create ROM backup with ROM Manager from another DHD from same country as I am (Slovenia)
- Get that backup on my SD card
- Recover that backup with ROM manager on my DHD
Is it possible?
Yes that would work. This is the order I would do it.
Other DHD
1). Create Backup (ROM Manager)
2). Factory Reset
3). Create 2nd Backup (CWM Recovery)
4). Restore 1st Backup
Your DHD
1). Create Backup
2). Restore Using 2nd Backup Above.
I would do this to avoid any issues with Google accounts, settings, etc...
Obviously the Other DHD needs to be rooted, S-OFF & have ClockworkMod Recovery installed.
What I`ve done wrong previously it was Stock CID... Original stock in Slovenia is HTC__032 (HTC-EastEurope), but I set it to HTC__001. Hope with this restore it will help me...
Performing this wouldn't affect your CID, If your CID is now HTC_001 then after this it will be the same.
But Easy Radio tool v2_2 should change it? First time I did root, I made Radio S-OFF, Super-CID and SimUnlock (all what without any need). After that I made Stock CID to HTC__001. So is it possible, that I changed that?
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!
Hi all,
I love this forum as it's got so much useful info so have just joined as I'm a little unsure of a few things and would really appreciate any help/advice.
Firstly, the big question, can I downgrade from 2.2 to 2.1 on a T-Mobile UK branded device without risking losing the warranty (only got the phone in March - just in case any hardware defects as I had the camera break a month after I got the phone!). I have read numerous guides and they seem to be associated with rooting and what confuses me is the stock roms I'm finding are for 1.14 not 2.1?
The reason is because (there may be an answer to this somewhere but have searched loads and can't find it) the Webkit browser on 2.2 seems to constantly crash. I didn't have the issue on 2.1 and have had the phone repaired twice, the issue occurs straight after a factory reset and is definitely an issue with 2.2 on T-Mobile UK branded firmware at least. T-Mobile UK assured me it was fixed but it certainly isn't as it crashed twice (just disappeared) within 5 minutes of browsing and later in the evening came up with the 'force close' error when browsing.
I loved using the stock provided browser over Opera/Skyfire etc and it was fine on 2.1...
So I am wondering whether T-Mobile UK have just bodged the firmware and whether rooting/debranding would give me a very stable version of webkit?
I had this with my first Wildfire after upgrading in December 2010, after two repairs they couldn't fix it so swapped for a new phone in March. The new phone was fine on 2.1 and this issue occurred again straight after the OTA update of 2.2 last night.
I'm really hoping someone can help with the above?
Many thanks in advance
1.14 is the ROM version number, and, is actually Android 2.1. But, you will not be able to downgrade without root. (Atleast easily).
If you wish to take the complex way out to downgrading to 2.1 without rooting and stuff, you can refer this guide here:
http://forum.xda-developers.com/showthread.php?t=921752
Excellent, many thanks 3xeno. I'll have a go at that. I am tempted to try unbranded 2.2 firmware as by the sounds of it the browser crashing issue might be specific to T-Mobile UK. I can't find other people reporting this issue anywhere and its happened to me with two phones, after 2 repairs with ota updates twice and after multiple factory resets.
Do you use webkit and get any crashes at all? I've tried other browsers but prefer the webkit one when it works, would be great if it played flash content like YouTube etc but I'll do some more research on that...
try dolphin browser HD(has many add-on's) or opera Mobile ,these are the best in the line & opera min for more data saving efficiency
Thanks all, I am having a lot of trouble with the SuperOneClick part though.
I have S-ON on boot and the boot loader that ends in 001 does that affect the ability of SuperOneClick to do Temp Root?
All I get is:
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
cannot stat 'C:\Documents and Settings\Marty\Desktop\HTC Downgrade\SuperOneClickv1.5.5\rageagainstthecage': No such file or directory
OK
chmod rageagainstthecage...
Unable to chmod /data/local/tmp/rageagainstthecage: No such file or directory
OK
Running rageagainstthecage...
It just says the last part for ages and never seems to go any further...
Do I need to do S-OFF using Unrevoke or similar?
It shouldn't, since the procedure was performed on an official Froyo release on HBoot 1.01.0001. BTW, You have to press 'Shell Root', not 'Temp Root'. Further make sure USB Debugging and all is on, as the author states.
Hi 3xeno,
I can confirm debugging is on and it is Shell Root I am trying but it just seems to stick on that last stage for ages.
I have the goldcard in, does that matter?
I have also tried unmounting the SD Card as mentioned on another thread?
It shouldn't matter. But, I think this should help you out:
http://forum.xda-developers.com/showpost.php?p=16634853&postcount=139
If you check the 2 posts above it, the user was experiencing similar problems as yours. So, I believe that solution should help.
(That guide is to downgrade to a WWE (Non Branded ROM) with HBoot 1.01.0001, and the 1st step is essentially the same as what you are attempting to do - Downgrade Misc Partition and flash an 'older' ROM)
Good Luck
Thanks 3xeno, I ended up doing the revolutionary thing in those steps and it says S-OFF now with Revolutionary at the top.
I was then able to use a stock RUU and install 2.1 on the phone but it looks different in that the clock widget and icons on the main screen weren't there? It's supposed to be the T-Mobile UK v2.1 firmware I thought?
I thought I might as well use unrEVOKed to root it anyway but I wondered if it was possible to revert it back to the way it was using the factory RUU if I needed any warranty repairs? Would reverting back then change the bootloader screen or is that permanently changed by Revolutionary?
martyp78 said:
Thanks 3xeno, I ended up doing the revolutionary thing in those steps and it says S-OFF now with Revolutionary at the top.
I was then able to use a stock RUU and install 2.1 on the phone but it looks different in that the clock widget and icons on the main screen weren't there? It's supposed to be the T-Mobile UK v2.1 firmware I thought?
I thought I might as well use unrEVOKed to root it anyway but I wondered if it was possible to revert it back to the way it was using the factory RUU if I needed any warranty repairs? Would reverting back then change the bootloader screen or is that permanently changed by Revolutionary?
Click to expand...
Click to collapse
Revolutionary introduces a new userspace issue. It can be fixed by flashing this (Needs Clockworkmod, I hope you had selected Yes to installing Clockworkmod to Revolutionary) -
http://forum.xda-developers.com/showthread.php?t=1156713
To change your bootloader from the Revolutionary one, you will need the HBoot.nb0 file from your TMobile Eclair RUU. Once you obtain that, you will need to follow this guide:
http://forum.xda-developers.com/showthread.php?t=1160251
So, essentially, once you perform this, you are back to factory stock, on a T-Mobile 2.1 ROM. (Essentially summing up my first post, its far easier to root and downgrade. )
Oh, and dont touch Unrevoked. Its not needed at all.
Many thanks 3xeno, really appreciate your help and such quick responses
I actually ended up with root (I think) as the super user icon is in there and I was able to do a nandroid backup on bootup.
Nice to be back to 2.1 though, I might leave it how it is at the moment and keep this info in mind to revert if needed for a warranty claim (fingers crossed it won't be a screen fault!).
One thing I'm really pleased about so far is that it doesn't seem to sync up immediately with my google account and fill my people list with a load of random e-mail addresses which is something I didn't like before.
So far so good, I'll have some fun playing with root now...
Thanks again
Cheers mate.
BTW, You can go to People > Menu Key > View > Check 'Only show Contacts with Phone Numbers'. It may not have synced immediately, but, it will, sooner or later.
EDIT: Did you flash the Sense Fix? If not, then, HTC Setup Wizard (The startup guide which greets you first thing when you boot up after a factory reset) will not work, implying that your Google Account is not setup on the phone. (Or, you'll have to do it manually.) Probably, that's why, its not syncing.
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: