Hi I plan to unroot my phone for warranty purposes.
I'm using a Desire Z with
baseband: 12.28b.60.140eU_26.03.02.26_M
build: 1.34.707.5 CL273326 release-keys
I've rooted the phone using gfree method.
This is what I plan to do:
1) Restore back to stock ROM (done)
2) Restore stock recovery.
- i have extracted the recovery.img from this RUU:
RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e _26.03.02.26_M_release_155556_signed.exe
- Will be flashing using this guide:
http://forum.xda-developers.com/showthread.php?t=902493&highlight=flash_image
-Yet to flash that .img
3) S-on.
- Using this guide:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Turning_S-On
4) Restore factory settings.
I have extracted the .img from the RUU i mentioned. My question is whether that .img is flashable on all Desire Zs because it is the same RUU that was featured in the rooting procedure for build 1.72.
I understand that there has been a lot of unrooting threads, but none seem to deal specifically with the compatibility of the recovery image.
Any help is much appreciated.
I'm not sure that if I just skip to S-on then the custom recovery (CWM in this case) will not show up. Does it?
Can anyone help?
I just need to know whether recovery images from different Vision RUUs (except TMOUS ones) are identical and flashable on any Desire Z.
As mentioned I already have a stock recovery.img from a 1.34 RUU, but the location ID might not be the same. Are stock recovery images dependent on location IDs?
The recovery should be completely independent from the CID. If the partitioning scheme is the same (and you can check that by verifying if the sizes of the images that make up your original ROM and those of the RUU are identical) you should be fine.
Cool. I went ahead with flashing the stock recovery and sure enough my phone isn't bricked and when I boot into recovery, it is of a red triangle.
Weirdly enough ROM Manager still tells me I have CWM 2.5.1.3 though...
Guess ppl can start using that recovery.img as a stock recovery.
Thanks a thousand times!
EDIT:
I tried to S-On using the guide on the Wiki but it did not work.
So i tried using terminal emulator to do the following:
# cd /data/local
# chmod 777 gfree
# ./gfree -s on
Click to expand...
Click to collapse
sure enough when i booted into (trackpad + power button) i see it say s-on.
Am i officially 'unrooted' now?
There was supposed to be a 'sync' command after './gfree -s on', but I forgot to do it. Am I still good to go?
You're okay. The sync command makes sure the caches are written to disk, but since you are S-ON it means they were written.
so if it so happened this phone gets returned to me after warranty claims, so I just
# cd /data/local
# chmod 777 gfree
# ./gfree -s off
to turn it s-off again? Or do I need to go through running rage again?
UPDATE: Got my phone back. Had to re-root the phone all the way from running rage.
weirdly enough, although the bootloader screen shows S-on, I am still able to use shootme? This means I'm still rooted, am I right?
Yup. Remove the Superuser app and it at least shouldn't be as obvious that you're rooted
hrmm superuser doesn't seem to be removable by conventional means... I don't remember installing it either. When I push it to the phone, I pushed it to the sdcard. Now i booted the phone without the sdcard, but superuser is still there...
Do I restore factory settings instead?
EDIT: nvm, Factory reset-ed. Everything looked factory. Wish me luck.
Nice, glad everything worked out...
djfoo000, glad it all worked out for you.
I have a Bell Desire Z, like yours and wanted to do something similar. While your steps are clear, i just wanted to confirm a few points:
1. In your very first post, when you said "Restore back to stock ROM (done)" i am guessing (99% sure) you meant that you restored back the ROM which you had backed up right after you installed ClockworkMod? Or did you use some other ROM image?
2. So even after you used gfree to turn back S-ON, you still had root privileges because of Superuser. How about after you did the factory reset, which presumably removed Superuser - did you still have root privileges?
3. Would it be possible for you to upload the stock recovery img file somewhere? If not, its okay as well.
Thanks
1) Yes. That stock ROM i mentioned was of a nandroid backup that restored everything prior to flashing a ROM that restored everything including apps and an unfinished Angry Birds (haha), instead of a clean one.
2) Yeah weirdly enough ShootMe still snaps screenshots. My guess is that root access is needed to install shootme as a system app and is not required beyond that. So even after s-on, shootme continues to operate due to it already being in the system app folder.
After I factory reset-ed, superuser and terminal emulator was gone. Since I was in a hurry to return the phone to the dealer I did not bother to download terminal emulator to input the 'su' command to check for root privileges. Sorry if it did not answer your question regarding root after factory reset.
3) Here's the file I extracted:
http://www.megaupload.com/?d=K8DVSNLX
I'm not 100% sure if it'll work on other Desire Zs since mine was not a carrier branded Desire Z.
Best of luck!
Excellent. Thanks djfoo000.
Couple of more questions -
1. do you know of any way for me to backup my existing recovery? I still havent installed CwM or other recovery image on my Desire Z (still stock).
Fastboot has commands to erase the recovery or flash a new one, but nothing that i could find to backup current recovery.
2. Also, would having S-ON and CID as 111111111 have any impact on doing a factory reset through stock recovery on the stock ROM? I dont think it will turn S-OFF and even more unlikely that it will change the CID, but will it do anything else? like go into a boot loop or some other weird thing?
lol i'm a noob user just like you. I just happen to gather enough info to do what I wanted to do.
1) I have no idea of a way to backup the stock recovery. Maybe searching the phone for a recovery.img (if there ever is one in the phone) and pull that?
2) I dunno anything about CIDs...
Might need help from other senior users from the forums.
testerman123 said:
1. do you know of any way for me to backup my existing recovery? I still havent installed CwM or other recovery image on my Desire Z (still stock).
Fastboot has commands to erase the recovery or flash a new one, but nothing that i could find to backup current recovery.
2. Also, would having S-ON and CID as 111111111 have any impact on doing a factory reset through stock recovery on the stock ROM? I dont think it will turn S-OFF and even more unlikely that it will change the CID, but will it do anything else? like go into a boot loop or some other weird thing?
Click to expand...
Click to collapse
1. There may well be a stock ROM/RUU image that you can pull that stock recovery from, as you've mentioned above. Or if not, you could always "dd" the recovery partition to back it up, though I double that will be necessary.
2. Did you mean S-OFF ? No, it won't have any impact, the factory reset won't touch the radio config partition, which is where S-OFF, SuperCID etc are stored.
Thanks djfoo000 for trying - you have been helpful.
Steviewevie, thanks for responding.
I think dd would be the answer as well, now the only question is where is the recovery located? like the "if=" parameter.
After that off to the races with CwM (and a nandroid backup of my existing firmware, of course), and a custom ROM! Steviewevie and djfoo000 - didnt notice a mention of any custom roms you guys were using. any suggestions?
Edit:
Looked around a little bit to see what the if parameter would be.
when i did
$ su
# cat /proc/mtd
under adb shell and terminal emulator, i did not get a list of partitions.
BUMP!! anyone?
testerman123 said:
Looked around a little bit to see what the if parameter would be.
when i did
$ su
# cat /proc/mtd
under adb shell and terminal emulator, i did not get a list of partitions.
Click to expand...
Click to collapse
The G2 does not use raw flash, so partitions will not show up as mtd devices. You should be able to do a
# cat /proc/emmc
if you are just trying to see the partition map...
Thanks ianmcquinn! That worked great.
Got my hboot, recovery and boot backed up just in case.
The curious thing, though, is that the stock unbranded recovery from 1.34.405.5 RUU that djfoo uploaded is only 3.85MB, while my backed up recovery is 8.5MB. whats up with that?
i can confirm that when I flash the recovery.img i uploaded, the unrooting works fine. And it is 3.85MB as mentioned.
Related
I am having an issue and although it is similar to others i haven't been able to solve it through the suggestions that others have posted
I have rooted my phone and installed CM7 and ended with an issue. I decided to unroot my phone and go back to stock. Stupid move. I am now stuck in a boot loop and the HBOOT was reflashed.
This is my set up
VISION PVT S-ON
HBOOT-0.82.0000
MICROP-0425
RADIO-26.02.01.15_M2
eMMC-boot
Sep 2 2010, 17:59:38
Also I have CWM 3.0.2.4 Installed
I cant install a froyo image right... Due to the CWM and i cant install an unsigned gingerbread image right due to the S-ON am i stuck or is there something that i can do.
I Think That a signed gingerbread rom would work but the one post of it that i can find i can't download from for some reason.
Any Help is Awesome.
You custome recovery? You could flash a new rom on there s-off jus take sign checks in bootloader, not recovery, a simple wipe and reflash of cm 7 would brring phone bacl
ilostchild said:
You custome recovery? You could flash a new rom on there s-off jus take sign checks in bootloader, not recovery, a simple wipe and reflash of cm 7 would brring phone bacl
Click to expand...
Click to collapse
Close, but not quite. From what I've been told (haven't tested myself) but when you s-on it will say its flashing, but boot.img will not flash.
Now you could try wiping and reflashing same exact cm rom you had and is a small chance will work, but if it doesn't you can do this:
You will need a wpthis.ko specfic to whatever kernal is currently installed. You will also need adb installed and working.
put wpthis.ko in sdk folder
Have phone connected to comp.
Boot into recovery.
Goto advanced mounts and mount /data
Then type:
adb remount
adb push wpthis.ko /data/local/wpthis.ko
adb shell should bring up #
insmod /data/local/wpthis.ko (should get function not implemented error)
Then go back to advanced mounts and unmount /data
Now wipe and flash rom of choice.
Once your up and running, rerun gfree.
Good luck, let me know how it goes.
fastludeh22 said:
Close, but not quite. From what I've been told (haven't tested myself) but when you s-on it will say its flashing, but boot.img will not flash.
Now you could try wiping and reflashing same exact cm rom you had and is a small chance will work, but if it doesn't you can do this:
You will need a wpthis.ko specfic to whatever kernal is currently installed. You will also need adb installed and working.
put wpthis.ko in sdk folder
Have phone connected to comp.
Boot into recovery.
Goto advanced mounts and mount /data
Then type:
adb remount
adb push wpthis.ko /data/local/wpthis.ko
adb shell should bring up #
insmod /data/local/wpthis.ko (should get function not implemented error)
Then go back to advanced mounts and unmount /data
Now wipe and flash rom of choice.
Once your up and running, rerun gfree.
Good luck, let me know how it goes.
Click to expand...
Click to collapse
If that's true then at first attempt at root would fail and couldn't install cm at all?
Also if that's the case look in the forums how to get s-off and eng-boot on from the help guides
But if anythinf do some real good reading b4 attempting so don't hose your phone
Fixed
Thanks to all i knew that it had been posted. I ended up reflashing with the Gingerbread Official Rom Leak and it worked perfectly. Thanks to Football and ilostchild.
compgeek13 said:
Thanks to all i knew that it had been posted. I ended up reflashing with the Gingerbread Official Rom Leak and it worked perfectly. Thanks to Football and ilostchild.
Click to expand...
Click to collapse
But can you root now? I didn't suggest the offical gb because I haven't looked into if there is a root method for it.
I guess you could replace the misc.img to downgrade and re root if all else fails.
And ilostchild, I'm not understanding your question. You go s-off before ever flashing a custom rom like cm.
fastludeh22 said:
But can you root now? I didn't suggest the offical gb because I haven't looked into if there is a root method for it.
I guess you could replace the misc.img to downgrade and re root if all else fails.
And ilostchild, I'm not understanding your question. You go s-off before ever flashing a custom rom like cm.
Click to expand...
Click to collapse
there is no root or temp root for the new rom, once flashed kinda stuck on there, gignerbreak wont work either
im asking how is he running recovery/rom and still s-on i seen a few ppl with this, and im askin how he do that?
Hi everyone,
I'm using a HTC Wildfire and am considering changing from stock (HTC non-branded) to CyanogenMod for a number of minor reasons. Could anyone just confirm that I got a few points right before I get started:
- Recovery is totally independent from the ROM itself, right? So I can flash ClockWorkMod Recovery only, continue to use the stock ROM, but have the additional features of ClockWorkMod available, such as backup, with which I can create a complete backup of the stock ROM. In case I don't like CyanogenMod, I can restore the stock image and be exactly where I left it, Apps, Settings and everything (of course the new Recovery will still be installed.) Is this correct?
- I'm planning to do the following steps (I read about the details, just want to confirm the basics):
x use the Revolutionary way to S-OFF and install new Recovery
x create full image backup of the stock ROM using the new Recovery
x install new ROM (ClockWorkMod)
x if I don't like CM: restore image created before to return to stock
-> This should work, shouldn't it?
- One more: What will happen if the the phone is S-OFF, an alternative Recovery is installed, and a HTC Firmware-Update is attempted? Will this work at all, will it update just the ROM, or will it update the Recovery, too? S-OFF will not be changed back to S-ON, right?
Thanks for your help.
Regards
1. Yes, the recovery is in it's own partition and is independent from the ROM
2. The recovery creates a "snapshot" of your current ROM. So when you restore, it'll be just the way you left it.
3. There's no need to do any HTC Firmware updates after installing a custom ROM (infact, I'm almost 100% sure that it won't work)
As a basic answer yes you go ahead with what you posted.just make sure your hboot version is compatible with revolutionary 1st etc etc.
As for HTC firmware update question,if your talking about the over the air updates I'm not sure but I think it would update your hboot thus reverting back to s-on status again so best not accept it if you do get one (turn off in settings)
Edit : ninja'd lol
Sent from my HTC Wildfire using XDA App
slymobi said:
As a basic answer yes you go ahead with what you posted.just make sure your hboot version is compatible with revolutionary 1st etc etc.
Click to expand...
Click to collapse
Yes, of course.
As for HTC firmware update question,if your talking about the over the air updates [...]
Click to expand...
Click to collapse
No, the manual ones you can download directly from HTC and install via USB. My understanding was that this would kill everything flashable, including radio and recovery. It would be reassuring to have a worst-case way to go back to stock in case the image-restore fails for whatever reason.
150d said:
Yes, of course.
No, the manual ones you can download directly from HTC and install via USB. My understanding was that this would kill everything flashable, including radio and recovery. It would be reassuring to have a worst-case way to go back to stock in case the image-restore fails for whatever reason.
Click to expand...
Click to collapse
Ah sorry never dealt with any firmware updates. There are ruu.exe to help get back to stock if something goes wrong I think.
Sent from my HTC Wildfire using XDA App
You can go completely back to stock, s-on and all but believe me once you have cwm installed there really is no point unless its for warranty reasons, backup fails are rare with the latest recoveries + if it does fail with your first backup you can always post here and we will explain how to extract a stock Rom from an ruu to put things back to how they where before or you can flash a custom sense Rom and modify it to your liking.
Sent from my HTC Wildfire using xda premium
Scratch0805 said:
You can go completely back to stock, s-on and all
Click to expand...
Click to collapse
That's great.
[...] but believe me once you have cwm installed there really is no point unless its for warranty reasons[...]
Click to expand...
Click to collapse
Yea, exactly. I'm a little on the paranoid side, I know... ;-)
Ok, I'm on my way now. I've performed the "Revolutionary" S-OFF and am now running "Revolutionary CWM v4.0.1.4". Is this an out-of-date version?
I've read about ROM-Manager being able to auto-check for and flash a new Clockworks Recovery, but I've also read that ROM-Manager needs root. I have not yet flashed a new ROM, so I assume that I'm not yet rooted, am I? Can I find a ZIP of CWM that I can directly flash from the SD-card?
Does the CWM-version I'm running have any effect on the "quality" of the image backup? In other words, if I create a backup now, will I be able to restore it later running a different version of CWM?
The "different version backup restore" is a bit wonky and won't always work.
To flash a different recovery from the SD card do this:
1. Place this file on your SD card (Not in any folders!): http://www.multiupload.com/74EW2VPNHL
2. Boot into the bootloader
3. Wait a bit and then it should prompt you to update
4. Click the volume+ key to update
5. Remove SD card
6. Boot into the new recovery and insert the SD card
7. Go under mounts and select Mount USB storage
8. Delete the PCIMG file from your computer
nejc121 said:
1. Place this file on your SD card (Not in any folders!): http://www.multiupload.com/74EW2VPNHL
Click to expand...
Click to collapse
I tried to, but I couldn't use the link. The whole domain seems to be down - maybe another holy crusade of Big Content, who knows. They sure leave fans in their wake, don't they.
Since you indicated that updating would be ok for the wildfire I went to http://www.clockworkmod.com/rommanager and downloaded the file recovery-clockwork-5.0.2.0-buzz.zip.
However, I'm not sure how to handle it: If I put it on the card under this name, nothing happens on bootloader-start. In recovery, I can select the file and install it, and then I immidiatly get a newly colored menu with the new CWM version 5.something. However, once I restart, the old CWM (v4.x) is there again.
I assume I need to use a magic filename so that the bootloader performs the update, not the (already running) recovery. Right?
**EDIT: Ah, disregard. I believe I found the answer myself.
Do you have fastboot?
If you do I can give you the recovery.img I'm using, which you can flash via fastboot.
Yes, fastboot is available.
Thank you.
Okay, here's how you flash a recovery via fastboot.
1. Extract the .zip I attached to the location where you fastboot is
2. Reboot phone in the bootloader
3. Select fastboot and attach USB cable
4. Open up the command prompt and type in "cd [location of fastboot]
5. Type in "fastboot flash recovery recovery.img"
6. You're done
Oh and by [location of fastboot] I mean that you type in the location of fastboot.
Wow - this was fun. There was something really curious going on with my device: Whatever I tried, no "official" way worked to modify CWM v4 to v5. In every case, the menu of the new version showed up and was usable, but was gone again after restart. After the file-on-card method got me nowhere (file was not recognized), I tried the high road and installed ROM-Manager. This complained about missing su. So I installed su. After that ROM-Manager downloaded CWM v5 and put it onto the card (into a file named update.zip - ahh... ) On restart, the CWM-install-screen came up, then the v5 menu.
And after restart, it was gone again. Even ROM-Manager was confused: He showed v5 as "installed", when in fact it was still v4. ;-)
So finally I downloaded the Android SDK (to get fastboot.exe) and performed the flash as you suggested in the first place. And it worked. First try, without hitch, permanently.
Thank you very much for your help!
Regards
The problem with ROM Manager's version is that it's only temporary and can only be accessed from the ROM Manager itself
Hi
i have V20c Stock ROM and its rooted ( lg p930)
i didnot know v20c boot loader is locked and install clockworkmod 6.0.1.5 via rom manager
now it donot go to stock recovery mod for factory reset.
i need to factory reset my phone and it has many problems and errors , how can i unistall and remove cmw ?
every time i try to do a factory reset phone dont boot and try to go cwm recovery menu
here is the screenshot
HELP PLEASE !!
Do you have a backup of the recovery partition? If so, you can flash it back if you have root.
If not, you can follow this guide in full and you will be returned to a rooted V20c: http://forum.xda-developers.com/showthread.php?t=1969070
If however you want CWM, you will need to follow the unbricking guide.
drumist said:
Do you have a backup of the recovery partition? If so, you can flash it back if you have root.
If not, you can follow this guide in full and you will be returned to a rooted V20c: http://forum.xda-developers.com/showthread.php?t=1969070
If however you want CWM, you will need to follow the unbricking guide.
Click to expand...
Click to collapse
Thanx for your help
This is my first android phone , i just wana have the stock recovery menu, is there any other ways ?
What is back up of recovery partition and how to make it ?
My phone is working now and i did root it from this way : http://forum.xda-developers.com/showthread.php?t=1886460
if i should change the rom and update it again how much is the risk of doing this process?
Sent from my LG-P930
nss007 said:
Thanx for your help
This is my first android phone , i just wana have the stock recovery menu, is there any other ways ?
What is back up of recovery partition and how to make it ?
My phone is working now and i did root it from this way : http://forum.xda-developers.com/showthread.php?t=1886460
if i should change the rom and update it again how much is the risk of doing this process?
Sent from my LG-P930
Click to expand...
Click to collapse
Well that's certainly interesting. Sure enough the method you linked to does work with the AT&T V20c ROM. I don't think anyone here was aware of this method.
In that case, you can restore the recovery using the file I attached to this post (see below). Extract it and place the img file on your phone's SD card. Then use terminal emulator (from the market) or adb to issue the following commands:
Code:
su
dd if=/sdcard/v20c-recovery.img of=/dev/block/mmcblk0p13
Then you should be back to normal. Be extra careful when typing the last part of that (mmcblk0p13) as typing the wrong number on the end can potentially brick the phone.
Thanx i'll try the file you attached
Yes i used this method and i confirm that it can root the v20c very easy but do not unlock the bootloader
Sent from my LG-P930
drumist said:
In that case, you can restore the recovery using the file I attached to this post (see below). Extract it and place the img file on your phone's SD card. Then use terminal emulator (from the market) or adb to issue the following commands:
Code:
su
dd if=/sdcard/v20c-recovery.img of=/dev/block/mmcblk0p13
Then you should be back to normal. Be extra careful when typing the last part of that (mmcblk0p13) as typing the wrong number on the end can potentially brick the phone.
Click to expand...
Click to collapse
thanx, it works
i have another question !
what are the benefits of cyanogen rom into ics stock rom ?
does it worth i flash cyanogen or other custom roms ?
Hey All,
Model: HTC One M8 - 0p6b160
CID: TELUS0001
Got a HTC One M8 the other day, I have already dev unlocked it via HTC, but I'm looking to have root and if possible s-off but stay on the stock image.
I've been wanting to backup the recovery image (since there seems to be very little resources for the TELUS001 CID) but from everything I've read this can only be done once you have root using adb and dd. To get root I need to install TWRP or PHILZ.
What I'm not clear about:
Are TWRP or PHILZ replacing the recovery image? Is there actually a way to backup recovery image? or did I miss something.
When TWRP/PHILZ do a backup is it just the current installed state of the phone?
Reading a post on another forum (can't post link cause I'm new) they talk about doing a temporary flash, but I didn't seem to be able to make that work using: fastboot boot twrp-m8-recovery.img
In the future I want to go to Android L, will any of this prevent it?
Thanks
felix2000 said:
Are TWRP or PHILZ replacing the recovery image? Is there actually a way to backup recovery image? or did I miss something.
When TWRP/PHILZ do a backup is it just the current installed state of the phone?
Reading a post on another forum (can't post link cause I'm new) they talk about doing a temporary flash, but I didn't seem to be able to make that work using: fastboot boot twrp-m8-recovery.img
In the future I want to go to Android L, will any of this prevent it?
Click to expand...
Click to collapse
1 and 3. You can backup stock recovery by booting into custom recovery that is located on your computer, instead of flashing custom recovery to the phone. This is already what you have described in Item 3. Is your phone in fastboot mode? The TWRP file is located in the same folder as fastboot.exe? Are you sure you have fastboot connectivity? To check this, type "fastboot devices" (with no quotes) and see if your device ID comes up.
Also, a great many stock recoveries are already posted here: http://forum.xda-developers.com/showthread.php?t=2701376
This thread also describes the process of backing up stock recovery via fastboot.
2. Not sure what you are asking. But yes, recovery can't backup something that isn't there (just current installed state).
4. Having custom recovery will prevent install of OTA, if that is what you mean. But return to stock recovery and restore any system files altered by root allows install of OTA. Or you can just install a custom ROM based on Android L when it comes out, as custom ROMs are sure to come quickly after L is available. Maybe even sooner than your version's OTA.
This is the official 5.0.1 Lollipop (4.20.531.4) Sense 6.0 OTA for T-Mobile HTC One M8. (4.20.531.4)
Nothing modified. Just a straight copy. Enjoy!
If you just need the firmware or rom you can download the zip and extract what you need from it. It's pretty simple.
I'll try to get around to extracting everything and posting links for the individual firmware as well. Don't get mad if I don't get around to it though.
Don't do anything with this unless you know what you're doing.
Download Link: https://docs.google.com/uc?export=download&confirm=mOs6&id=0B83tee7zNQDVTTRsTjJ1dzhHeUU
Would it be possible to upgrade to this without having to flash back to stock first?
How to go back to stock and apply OTA.
douglasf01 said:
Would it be possible to upgrade to this without having to flash back to stock first?
Click to expand...
Click to collapse
Going back to stock and flashing this is not that hard. The main thing is to have a stock ROM that is not rooted and the correct stock recovery.
So here are the steps I used via TWRP custom recovery. Note I was coming from 4.4.4 kit kat
- first you need to be on a stock t-mobile rom. I used my original backup.
- then I used TWRP to backup - note I made sure that compressed was not checked
- then unziped TMOUS-M8-3.32.531.2-Stock-TWRP.zip (which is located in this group just a different thread) and copied the files from this backup onto my backup replacing the files
- then I booted into recovery and restored this backup and at the end when it says that the backup is not rooted do you want to root? Make sure you click 'No' and reboot
- At this point I made sure that I removed any programs that relied on root xposted, greenify, reboot programs, etc. I also made sure that I had no root. I used adb shell then typed 'su'.
- At this point I then rebooted into recovery and made another backup (just in case) and then I went into the boot-loader.
- I flashed the 3.32.531.2 recovery (https://www.androidfilehost.com/?fid=95897840722642978) via the 'fastboot flash recovery recoveryfile.img' command and rebooted.
- next up I downloaded the OTA via the about phone and installed and bingo you are updated.
hope this helps.
-brad
bradley_e_smith said:
Going back to stock and flashing this is not that hard. The main thing is to have a stock ROM that is not rooted and the correct stock recovery.
So here are the steps I used via TWRP custom recovery. Note I was coming from 4.4.4 kit kat
- first you need to be on a stock t-mobile rom. I used my original backup.
- then I used TWRP to backup - note I made sure that compressed was not checked
- then unziped TMOUS-M8-3.32.531.2-Stock-TWRP.zip (which is located in this group just a different thread) and copied the files from this backup onto my backup replacing the files
- then I booted into recovery and restored this backup and at the end when it says that the backup is not rooted do you want to root? Make sure you click 'No' and reboot
- At this point I made sure that I removed any programs that relied on root xposted, greenify, reboot programs, etc. I also made sure that I had no root. I used adb shell then typed 'su'.
- At this point I then rebooted into recovery and made another backup (just in case) and then I went into the boot-loader.
- I flashed the 3.32.531.2 recovery (https://www.androidfilehost.com/?fid=95897840722642978) via the 'fastboot flash recovery recoveryfile.img' command and rebooted.
- next up I downloaded the OTA via the about phone and installed and bingo you are updated.
hope this helps.
-brad
Click to expand...
Click to collapse
I dont have an original backup of my device, which is a rookie mistake I know. I just never intended to go back to stock.
Since my phone is going to be a work/personal phone I cant have it rooted or flashed with a 3rd party rom. Would this TMOUS-M8-3.32.531.2-Stock-TWRP.zip be ideal to use to flash back to stock on? This will also reset my recovery back to stock also?
Thanks
douglasf01 said:
I dont have an original backup of my device, which is a rookie mistake I know. I just never intended to go back to stock.
Since my phone is going to be a work/personal phone I cant have it rooted or flashed with a 3rd party rom. Would this TMOUS-M8-3.32.531.2-Stock-TWRP.zip be ideal to use to flash back to stock on? This will also reset my recovery back to stock also?
Thanks
Click to expand...
Click to collapse
Not being an expert and all, flashing the stock rom will not set the recovery back. Basically you need to restore the ROM and then the recovery. I would like to add that the above worked for me, but I am researching a wifi issue I am having so take what I did with a grain of salt.
**update**: I ended up doing a factory wipe and now the wifi works.... oh well.
-brad
bradley_e_smith said:
Not being an expert and all, flashing the stock rom will not set the recovery back. Basically you need to restore the ROM and then the recovery. I would like to add that the above worked for me, but I am researching a wifi issue I am having so take what I did with a grain of salt.
**update**: I ended up doing a factory wipe and now the wifi works.... oh well.
-brad
Click to expand...
Click to collapse
This command fastboot flash recovery recoveryfile.img, did you have to select any options or switches for it to work correctly? The reason I ask is that when I opened up a CMD and CD to the adp/fastboot folder I ran the command line and was given a list of switches/options to run it with.
Any suggestions here?
douglasf01 said:
This command fastboot flash recovery recoveryfile.img, did you have to select any options or switches for it to work correctly? The reason I ask is that when I opened up a CMD and CD to the adp/fastboot folder I ran the command line and was given a list of switches/options to run it with.
Any suggestions here?
Click to expand...
Click to collapse
No, I just downloaded the recovery file, did 'adb reboot-bootloader', then did the 'fastboot flash recovery recoveryfile.img' (where recoveryfile.img is the actual filename).
bradley_e_smith said:
No, I just downloaded the recovery file, did 'adb reboot-bootloader', then did the 'fastboot flash recovery recoveryfile.img' (where recoveryfile.img is the actual filename).
Click to expand...
Click to collapse
I see, that is not the case for me. If anything I have the utility that can do all this, but that wasnt working for me either.
I guess I am just lost on this I suppose, especially since I didnt do anything but apply TWRP and root the phone, but kept the phone with the stock rom and not a 3rd party rom. I would figure killing the root and applying a stock recovery would be all I would need to do in order to OTA and be updated.
I have noticed each time I have flashed the recovery through the utility, I try to get in to the stock recovery and the phone acts as if it is not there and displays a red triangle with an exclamation point in it. I imagine this is an indicator letting me that a recovery is not present.
Any thoughts ?
This is the issue I am presented with trying the CMD with fastboot
douglasf01 said:
I see, that is not the case for me. If anything I have the utility that can do all this, but that wasnt working for me either.
I guess I am just lost on this I suppose, especially since I didnt do anything but apply TWRP and root the phone, but kept the phone with the stock rom and not a 3rd party rom. I would figure killing the root and applying a stock recovery would be all I would need to do in order to OTA and be updated.
I have noticed each time I have flashed the recovery through the utility, I try to get in to the stock recovery and the phone acts as if it is not there and displays a red triangle with an exclamation point in it. I imagine this is an indicator letting me that a recovery is not present.
Any thoughts ?
Click to expand...
Click to collapse
That is what you would see if you go into recovery. To see more all you do is press both volume keys (up and down) at the same time and press the power button. Then you should see a menu. The stock recovery is not as nice as TWRP.
If you remove root that still may not work (and if someone else knows more please chime in) b/c when you root, it changes the filesystem. I am unsure what the OTA checks on so I would try your 'unroot' method, but if that doesn't work you may need to install a stock un-rooted ROM.
---------- Post added at 11:32 AM ---------- Previous post was at 11:31 AM ----------
douglasf01 said:
This is the issue I am presented with trying the CMD with fastboot
Click to expand...
Click to collapse
it looks correct, are you sure you have the file exactly typed out and also make sure you are the boot-loader screen.
bradley_e_smith said:
That is what you would see if you go into recovery. To see more all you do is press both volume keys (up and down) at the same time and press the power button. Then you should see a menu. The stock recovery is not as nice as TWRP.
If you remove root that still may not work (and if someone else knows more please chime in) b/c when you root, it changes the filesystem. I am unsure what the OTA checks on so I would try your 'unroot' method, but if that doesn't work you may need to install a stock un-rooted ROM.
---------- Post added at 11:32 AM ---------- Previous post was at 11:31 AM ----------
it looks correct, are you sure you have the file exactly typed out and also make sure you are the boot-loader screen.
Click to expand...
Click to collapse
I went into the supersu application and there was an unroot option that clears the cache, system, and modifies something. I also flashed the stock recovery back after your last comment, I have never owned an HTC Android device and wasnt aware that was a default. I am going to try the OTA and see if this works out. I will let you know.
I have always just reflashed stock recovery.... Made sure I enabled all of the apps I disabled (like bloatware or whatnot), and then was always able to update. I actually can't recall if unrooting was required.
But I do know that locking the boatloader is not necessary.
---------- Post added at 03:15 PM ---------- Previous post was at 03:14 PM ----------
I am just sad to say goodbye to Xposed....
T-Mobile US 4.20.531.4 firmware
Here is the new T-Mobile US firmware from today with the recovery and boot.img removed, just need someone to do their magic and remove red text.
https://dl.dropboxusercontent.com/u/...4/firmware.zip
douglasf01 said:
This command fastboot flash recovery recoveryfile.img, did you have to select any options or switches for it to work correctly? The reason I ask is that when I opened up a CMD and CD to the adp/fastboot folder I ran the command line and was given a list of switches/options to run it with.
Any suggestions here?
Click to expand...
Click to collapse
When you get the red triangle, hold volume down for a few seconds...you should get a log screen (although it may be volume up, I can't remember, try both)...it will tell you what is wrong.
Also, from my past experiences, if I didn't flash a new stock Rom (but just tried to "clean up" my existing stock Rom), I would run into problems because I had some app on the phone that even if I had deleted it, had originally modified build.prop... And that is one key thing the update checks before proceeding with install. So you have to make sure you have a stock build.prop file.
Anyone notice when WiFi is on 4glte icon is also on at the same time too just like kk4.4.4? It supposed to be when WiFi is on and 4glte icon should be off.
douglasf01 said:
This is the issue I am presented with trying the CMD with fastboot
Click to expand...
Click to collapse
You need to rename the recovery file.
Avoid using '+' in files names.
If you have spaces in a file name, ALWAYS put a "quotation mark" around the file name.
DROITURK182 said:
Here is the new T-Mobile US firmware from today with the recovery and boot.img removed, just need someone to do their magic and remove red text.
https://dl.dropboxusercontent.com/u/...4/firmware.zip
Click to expand...
Click to collapse
The link doesn't seem to work.
epsix said:
Anyone notice when WiFi is on 4glte icon is also on at the same time too just like kk4.4.4? It supposed to be when WiFi is on and 4glte icon should be off.
Click to expand...
Click to collapse
This is something that always happens with HTC devices. I don't know why.
OfficialLocdoGg said:
This is something that always happens with HTC devices. I don't know why.
Click to expand...
Click to collapse
Yeah, I try changing the sku id in ACC/default.xml to metro pcs, and other carriers it works but not good signal.
Okay, I have got APNs unlocked, root, restriction-free tethering working over IPv6, busybox installed, and a kernel with modified initramfs. Anyone interested in a nice simple debloated stock ROM?