Related
I've had a lot of trouble upgrading to KitKat. After attempting to flash different image files for stock recovery/boot/system, I found it impossible to completely unroot the phone using the instructions posted because the phone kept re-rooting itself. Finally, I S-offed, wrote superCID, used the Telus RUU, applied the OTA downloaded to the phone, changed the CID back to GLOBA001 (my carrier is WindMobile). And finally! I know I relocked and unlocked the bootloader somewhere in the process, but I can't quite remember when.
Now, before I even think of re-rooting the phone or installing a custom recovery, I'd like to create a backup of the stock boot, recovery, and system. I tried running
Code:
fastboot boot openrecovery-twrp-2.7.1.1-zaracl.img
using the special KitKat TWRP. There's a message about boot.img being downloaded successfully but the phone reboots to a black screen.
I know that TWRP 2.7.1.0 downloaded from their website worked fine on my phone before I ran the RUU . So I'm not sure that the new TWRP is incompatible with my phone.
If I wanted to use adb instead, I'd need to root the phone before being able to pull the stock recovery, boot, and system images using adb shell. If I have to resort to rooting, is there any way to do so without flashing a custom recovery first? If there is, I might be able to unroot the phone afterward and make it stick. (Delete the supersu apk and su binary, right?)
I remember that the first time my phone attempted to download and apply the OTA automatically, my phone wiped itself. It was a lot of hard work to get it back to a usable state, but it was my own fault for not having a proper backup. I'd like to avoid making that mistake again, and have a stock backup handy on my computer in case there are carrier updates for my phone in the future.
To re-iterate, possible to back up stock everything without root? If not, possible to root without installing custom recovery?
You can no longer boot into a custom recovery, you have to actually flash it.
As far as having the stock recovery and boot, those are actually inside the OTA so you can pull it from there.
Since you'll have the stock recovery already, you can flash TWRP and use that to backup boot and system.
When you need to go stock, just use TWRP to restore your backup and then manually flash the stock recovery.
Since you made the device S-OFF, I recommend that if you need to lock/unlock the bootloader that you use the commands in this thread versus using the htcdev method as that wipes the /data/preload/ folder (as part of its normal /data wipe) which includes a few stock apps.
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
Locking the bootloader won't do anything, it's only unlocking using the htcdev token that causes the data wipe. So if you haven't unlocked using the htcdev method since running the RUU you will still have the 2 - 3 apps.
I don't know if the /data/preload/ folder is a requirement for a successful OTA update or not but I checked inside my OTA zip for my phone and it does include the 3 items stored there for the VM variant.
The unlock was AFTER the RUU. I ran the RUU, then used the OTA to upgrade to KitKat, then unlocked the bootloader again. However, I didn't notice any apps disappearing and the OTA zip for Wind also has a /data/preload folder.
*Shrugs* Seems good enough to me. TWRP, here I come!
needing wind stock stuck with wind awsy amd wont connect
I have an unlocked desire 601 it finds only wind away I'm trying to get a backup of the stock Rom to flash it does anyone k ow if there any around or even a back up I can use to try to get my phone working on wind home
jayjsteez said:
I have an unlocked desire 601 it finds only wind away I'm trying to get a backup of the stock Rom to flash it does anyone k ow if there any around or even a back up I can use to try to get my phone working on wind home
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2804427
needing help for s-off
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
hey i have unlocked desire 601 but only says wind away and wont connect ive knoticed the wind version is the same as the other versions but im wondering do i need the wind rom in order for it to pick up the wind home i cant seem to find anywhere online the wind rom and everytime i try to s-off it saysfailed and ive followed everything is there any insite you could give me to help me with this issue if its fixable again my phone says wind away but wont connect to it and i need to get it working as its my only device and carrier i use thx
---------- Post added at 11:29 PM ---------- Previous post was at 11:16 PM ----------
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
hey i have unlocked desire 601 but only says wind away and wont connect ive knoticed the wind version is the same as the other versions but im wondering do i need the wind rom in order for it to pick up the wind home i cant seem to find anywhere online the wind rom and everytime i try to s-off it saysfailed and ive followed everything is there any insite you could give me to help me with this issue if its fixable again my phone says wind away but wont connect to it and i need to get it working as its my only device and carrier i use thx
-Duir- said:
You can no longer boot into a custom recovery, you have to actually flash it.
As far as having the stock recovery and boot, those are actually inside the OTA so you can pull it from there.
Since you'll have the stock recovery already, you can flash TWRP and use that to backup boot and system.
When you need to go stock, just use TWRP to restore your backup and then manually flash the stock recovery.
Since you made the device S-OFF, I recommend that if you need to lock/unlock the bootloader that you use the commands in this thread versus using the htcdev method as that wipes the /data/preload/ folder (as part of its normal /data wipe) which includes a few stock apps.
Click to expand...
Click to collapse
I don't understand how you can pull the stock recovery from the OTA. I thought OTA's are immediately installed, instead of stored untill you want to install it? So, how do you backup the stock recovery?
It is saved until you want to install. When it go finishes Downloading, just choose install later. And you will be able to copy it into other storage devices and extract files and what not. I'm not sure if it stores in internal or external I'm 80% sure external sd if you have one.
Sent from my HTC0P4E1 using XDA Free mobile app
WARNING: This ABSOLUTELY HAS THE POTENTIAL TO BRICK YOUR DEVICE. Please tread carefully. I am NOT responsible if you damage your device. This can be very dangerous, PLEASE do not do this unless you know you absolutely want/need to. You have been warned.
Important information:
This is for US Model x727 running the 5.8.019s version of the US ROM. If you flashed the chinese ROM, this will not help you at all.
Afterwards you should still have US ROM and features at version 5.8.019s
Your device should be persistently unlocked after successfully performing this procedure.
This zip file replaces the aboot and xbl (basically, the bootloader) with the versions from the LE_ZL1_LEX720-CN-FN-WAXCNFN5801811021S-5.8.018S.zip ROM file. I can't guarantee this will work for everyone (or even anyone). I can only tell you that it worked for me.
NOTE: If this makes you happy, please consider donating by clicking on the "donate to me" button under my handle at the left. I am broke and trying to recoup the cost of this device
Requirements (what I *think* you'll need):
US Le Pro3 running the US ROM updated to 5.8.019s OTA (If you're running the chinese ROM because you were impatient and didn't want to wait for the grownups to work out a procedure, this will not help you).
TWRP Image (I used the chinese one)
Zip File listed below
Somewhere to put the zip file for flashing if you don't want to have to wipe your device (I've heard of people successfully using an OTG storage device? I just wiped mine so you're on your own to figure this out)
This is the procedure I followed:
Have ADB/Fasboot tools on your computer (I am not helping you here, it you're lucky, maybe your friends will help)
Make sure you have enabled the developer tools, turned on USB debugging, and authorized your computer on your device (again, I'm not helping with that)
Make sure adb can see your device when you run "adb devices"
Run "adb reboot bootloader"
Run "fastboot devices" to make sure you see your device
Run "fastboot oem unlock-go" to unlock your device temporarily
Run "fastboot oem device-info" to verify unlock status
Run "fastboot boot recovery_twrp.img" (or whatever the twrp image filename is on your computer) to boot up to TWRP
NOTE: If you don't read chinese and you haven't done this before, you'll be presented with a screen in chinese with two buttons next to each other and a swipe underneath them. THE BUTTON ON THE RIGHT lets you change the language. Press it, thank me later.
If you have an OTG device with the bootloader replacement zip on it, skip this step. If you have to use your device's storage, and your storage is encrypted, you'll have to wipe all the data. Go to Wipe, choose Format Data and follow the instructions. YOU WILL LOSE EVERYTHING ON YOUR DEVICE. Be warned.
If you wiped your data partition, you'll need to push the zip file to the storage. Run "adb push x727-5.8.019s_bootloader-unlock.zip /sdcard/"
Now press "Install", select the x727-5.8.019s_bootloader-unlock.zip file and flash it.
Reboot back to your system. If you wiped data, your device will now proceed to re-initialize itself as if from the factory
Your system should still be running the full US ROM, but it should also now be persistently unlocked. Don't do any updates, your device likely won't remain unlocked if you run an update. And there's no guarantee you'll be able to re-unlock after doing so.
NOTE: If you flash TWRP to the recovery partition, the OS will likely reset it to the factory recovery UNLESS YOU ROOT THE SYSTEM. Your device is still unlocked, the recovery was just restored by the system, don't freak out. Be warned. I don't have time to answer stupid questions, neither does anyone else.
Download: x727-5.8.019s_bootloader-unlock.zip
MD5: 8eff2a1e29c9959259e7db1dd5c74a67
Special thanks to @hondajohn88 for taking the leap and experimenting with the chinese rom on his own device.
Reserved
Is it possible to have the chinese bands with the US rom on the x727? because I'm bringing the phone to asia and i need band 41
How about pulling us the modem image from the US version now since you have it unlocked. The Grossoshop is great except a few of us have flashed this over the CN ROM and the CN modem seems to be lacking a few bands.
awesome job! i knew we'd figure out root/unlock eventually. wonder if Le Eco accidently let this happen or did it on purpose so they can have plausible deniability
edit - did you also by chance backup the stock bootloaders?
Kick ass man!!! I get my phone next week when my dad comes down to visit me in Colombia. Can't wait to do this once it arrives
I was happy till I saw .. "Run "fastboot oem unlock-go" to unlock your device temporarily"
for some reason I don't get it to work like you guys do. it will give the same error as with the original firmware. Ill try but I doubt it will work for me
Its going to be pointless for me to try .. I don't understand why you guy can have temp bootloader while I cant
And yes, I am on 19s
C:\adb>fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.005s
C:\adb>fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.091s]
finished. total time: 0.094s
bulls4ever said:
I was happy till I saw .. "Run "fastboot oem unlock-go" to unlock your device temporarily"
for some reason I don't get it to work like you guys do. it will give the same error as with the original firmware. Ill try but I doubt it will work for me
Click to expand...
Click to collapse
Yeah I absolutely have tried like 6 different adb/fastboot's and nothing works for me either.
Not my first rodeo with annoying Windows drivers too.
I reset it to factory.. downloaded the 19s and upgraded again .. nothing will make it to allow oem unlock
If i try to run "fastboot boot recovery_twrp.img" will it brick the phone or just wont work?
---------- Post added at 06:20 PM ---------- Previous post was at 06:19 PM ----------
can you upload the "ADB/Fasboot tools" you used? maybe that is the problem but i doubt it
Just to make sure, you guys are checking "OEM Unlocking" in developer options, correct?
bulls4ever said:
I reset it to factory.. downloaded the 19s and upgraded again .. nothing will make it to allow oem unlock
If i try to run "fastboot boot recovery_twrp.img" will it brick the phone or just wont work?
---------- Post added at 06:20 PM ---------- Previous post was at 06:19 PM ----------
can you upload the "ADB/Fasboot tools" you used? maybe that is the problem but i doubt it
Click to expand...
Click to collapse
It won't be the fix. If adb/fastboot recognize the devices, changing versions shouldn't work. Sorry :-/ That being said, I suppose there's no hurt in trying. FWIW this is what worked for me on my Windows 7 box:
Code:
C:\Users\dr4stic>adb version
Android Debug Bridge version 1.0.36
Revision 19394af606f6-android
C:\Users\dr4stic>fastboot --version
fastboot version 19394af606f6-android
I got them by installing the Android SDK. The SDK manager indicates that my "Android SDK Platform Tools" (that the tools come from) are at version 24.0.4 and I can upgrade to revision 25.
This may be a dumb question, but I'm assuming you've set the "allow device bootloader unlocking" (or whatever it's called) in the developer settings... right?
ExTREmE99 said:
awesome job! i knew we'd figure out root/unlock eventually. wonder if Le Eco accidently let this happen or did it on purpose so they can have plausible deniability
edit - did you also by chance backup the stock bootloaders?
Click to expand...
Click to collapse
I did, but I didn't really need to. They're in the 5.8.019s OTA. They're the emmc_appsboot.mbn and xbl.elf files in the firmware-updates folder.
dr4stic said:
It won't be the fix. If adb/fastboot recognize the devices, it won't work. Sorry :-/
This may be a dumb question, but I'm assuming you've set the "allow device bootloader unlocking" (or whatever it's called) in the developer settings... right?
Click to expand...
Click to collapse
yes, i did
ITs bizarre that some can get the tem unlock and some don't.
Like I said . I reset to fabric, re-updated using the 19s that is in the forum. Enabled developer tools. Enabled OEM unlock and USB dev. I tried to mimic a brand new update to 19s ...
I wonder if it actually enable OEM but adb/fastboot wont say it is unlocked? unlikely but .. hey.. I'm desperate at this point lol
---------- Post added at 06:36 PM ---------- Previous post was at 06:33 PM ----------
My version is 1.0.32 ...
---------- Post added at 06:39 PM ---------- Previous post was at 06:36 PM ----------
no donuts
C:\adb>adb version
Android Debug Bridge version 1.0.36
Revision e02fe72a18c3-android
C:\adb>fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.015s
C:\adb>
bulls4ever said:
yes, i did
ITs bizarre that some can get the tem unlock and some don't.
Like I said . I reset to fabric, re-updated using the 19s that is in the forum. Enabled developer tools. Enabled OEM unlock and USB dev. I tried to mimic a brand new update to 19s ...
I wonder if it actually enable OEM but adb/fastboot wont say it is unlocked? unlikely but .. hey.. I'm desperate at this point lol
---------- Post added at 06:36 PM ---------- Previous post was at 06:33 PM ----------
My version is 1.0.32 ...
Click to expand...
Click to collapse
Who knows, maybe the lower version is misinterpreting the output. If you're really determined you can try upgrading your version of adb/fastboot. Like I said I use the sdk from google, so it's as updated as it'll get. Anything else is just someone repackaging what already exists.
After you "fastboot oem unlock-go" try booting the twrp image anyway. I doubt it'll work if it's misinterpreting the response (it would have be interpret it properly to send the boot image to the device for booting), but who knows. Maybe it will work anyway.
Saikou0taku said:
Just to make sure, you guys are checking "OEM Unlocking" in developer options, correct?
Click to expand...
Click to collapse
yes
Going to try the Android SDK shortly
bulls4ever said:
yes, i did
ITs bizarre that some can get the tem unlock and some don't.
Like I said . I reset to fabric, re-updated using the 19s that is in the forum. Enabled developer tools. Enabled OEM unlock and USB dev. I tried to mimic a brand new update to 19s ...
I wonder if it actually enable OEM but adb/fastboot wont say it is unlocked? unlikely but .. hey.. I'm desperate at this point lol
Click to expand...
Click to collapse
You know... if worse comes to worst and you desperately want to unlock, couldn't you just try installing the Chinese ROM listed by some of the other users? I don't know how that ROM would react to your phone being that it isn't unlocking at all, maybe it'll brick it, maybe it won't (I doubt it). The consequences of that would completely be of your own undertaking...
That being said, the chinese rom people talk about is signed by LeEco and thus would likely install without question. And it's bootloader would then be unlocked. We could make plans to return you to stock US firmwares at a later date. I suspect we're gonna have to get a solution together for that at some point anyway... My only suggestion would be that you do it while coming from the 5.8.019s (which you already are) because that's where my firmwares are coming from.
Android SDK will give the same results as expected ...
Not that desperate ... I'm desperate to keep LeEco cause I like it. But do not want to go to Chinese way as it will lose bands and currently we don't even have ways to come back to US rom.
My "desperation" is that the deadline to decide if I will keep the phone or return is approaching.
What I need to figure it out is why some have tem unlock and some don't. My windows is 10. Maybe windows issue (I doubt it)? will try windows 7 later
bulls4ever said:
Android SDK will give the same results as expected ...
Not that desperate ... I'm desperate to keep LeEco cause I like it. But do not want to go to Chinese way as it will lose bands and currently we don't even have ways to come back to US rom.
My "desperation" is that the deadline to decide if I will keep the phone or return is approaching.
What I need to figure it out is why some have tem unlock and some don't. My windows is 10. Maybe windows issue (I doubt it)? will try windows 7 later
Click to expand...
Click to collapse
No, windows should have nothing to do with it. I'm assembling a "return to US" rom as we speak... but I won't feel comfortable about releasing it until it's been tested. And also I need lunch...
dr4stic said:
No, windows should have nothing to do with it. I'm assembling a "return to US" rom as we speak... but I won't feel comfortable about releasing it until it's been tested. And also I need lunch...
Click to expand...
Click to collapse
I'm going to use this method later today and can report back any issues. By the way, you are the man!
Is super super flash able after bootloader is unlocked?
yeah .. windows wasn't the issue. I tested on Ubuntu and it was a no go.
Is it possible that LeEco released like 2 versions being the first a mistake of leaving the bootloader sort of unlocked and then a second with it locked?
I am running out of reasons for not being able to unlock it while some are able to
Software up to date issue
HI all, just got this M8 and it is an ATT Version. but I believe it is unlocked because I am using it with cricket.
When trying to update Android Tells me software is up to date ?
Android version 5.0.2
HTC Sense Version 6.0
Software Number 4.28.502.1
HTC SDK API Level
I am pretty sure that ATT has updated to Marshmallow by now / So why can't I update? I am on wifi and 4G/LTE Could it be because I am using a Cricket Sim Card in the Phone ?
I have downloaded the RUU for Marshmallow software version 6.20.502.5. Should I continue with the Manual update ?
I believe this phone was originally purchased from ATT on May of 2016 if it makes any difference , figured I post it. since it could be a newer version of HTC M8.
Also is there a way to back up my current stock rom, without Rooting phone ? Thanks for all your help.
As I cannot root my phone, because when I go into developer option and search for S-off That option is not there and I can't Continue.
My responses below in red font:
ELEVO said:
HI all, just got this M8 and it is an ATT Version. but I believe it is unlocked because I am using it with cricket.
When trying to update Android Tells me software is up to date ?
I am pretty sure that ATT has updated to Marshmallow by now / So why can't I update? I am on wifi and 4G/LTE Could it be because I am using a Cricket Sim Card in the Phone ?
That is correct, the AT&t version (and most US versions) can only OTA update if connected to the proper branded carrier (AT&T in this case). Therefore, the RUU is your best option to update.
I have downloaded the RUU for Marshmallow software version 6.20.502.5. Should I continue with the Manual update ?
You can. But you need to flash the 6.20.502.5 firmware first, before you can flash the RUU. See instructions to flash the firmware here: https://forum.xda-developers.com/showpost.php?p=67123738&postcount=7
Then run the RUU. Keep in mind, that RUU will wipe the phone. So backup your data to an off-phone location (cloud, computer, etc.) before RUU.
Also is there a way to back up my current stock rom, without Rooting phone ? The current Lollipop ROM? No, there will be no way to revert to LP by official means, once you RUU to Marshmallow. I doubt you will find the need or desire to "downgrade" to obsolete LP version. If for some reason you did want to, there are options, but would require unlocking the bootloader (to install custom recovery and flash a Lollipop ROM), or s-off (which would allow you to "downgrade" by RUU - which is not allowed with s-on).
As I cannot root my phone, because when I go into developer option and search for S-off That option is not there and I can't Continue.
You are misunderstanding a couple things:
1) s-off is not a setting in Developer Options. s-off can only be obtained with sunshine app ($25)
2) You don't need s-off to root this device. Simply unlock the bootloader, install TWRP, and flash SuperSU to root
Click to expand...
Click to collapse
Detailed
redpoint73 said:
My responses below in red font:
Click to expand...
Click to collapse
Thanks for the detailed reply, really helpful and greatly appreciated :good:
Two more Questions, Can I upgrade to an official DEV Edition RUU on this ATT Device? or would I have to use a Custom Dev ROM ? as I am trying to Tether with my phone, just like my official Developer HTC M8 I purchased in 2014 , Seems AT&T phone wont allow me to Tether ?
Also once I flash firmware and upgrade to official RUU will need to Unlock and Root Loader? Will doing upgrading to official Marshmallow Relock bootloader and Un Root Phone ? Back to Stock ? Thanks again, I will be attempting this pretty soon. Thanks again
For the Record, I have made a back up of my Lollipop via TWRK. I also backed it up using Titanium back up, just in case.
Again, my responses in red font:
ELEVO said:
Thanks for the detailed reply, really helpful and greatly appreciated :good:
You're welcome. Always happy to help!
Two more Questions, Can I upgrade to an official DEV Edition RUU on this ATT Device?
You can't flash the Dev Edition RUU with s-on. Even though the versions are very similar (same model ID - MID) the two versions have different carrier ID (CID). Wrong carrier ID will make the Dev Ed RUU fail, by definition. And the only way to change CID is with s-off. Further, its not really necessary to flash the Dev Ed RUU (and not worth spending money of s-off) to accomplish what you want (see more below)
or would I have to use a Custom Dev ROM ? as I am trying to Tether with my phone, just like my official Developer HTC M8 I purchased in 2014 , Seems AT&T phone wont allow me to Tether ?
Its correct that the AT&T stock ROM disables tethering. Flashing most custom ROMs (or the Dev Ed ROM) will enable tethering - as well as remove annoying AT&T branding and bloat apps. Flashing the Dev Ed RUU is not necessary to accomplish this.
Also once I flash firmware and upgrade to official RUU will need to Unlock and Root Loader? Will doing upgrading to official Marshmallow Relock bootloader and Un Root Phone ? Back to Stock ? Thanks again, I will be attempting this pretty soon. Thanks again
You need to relock the bootloader in order to flash firmware and RUU (command: fastboot oem lock). Once the RUU is complete, the phone will be on a fully stock "factory" image. So you will be unrooted. You will also be back to stock recovery (no longer have TWRP installed). From there, what you want to do:
1) Unlock the bootloader again. Either use the same unlock bin code you used to unlock BL before. Or get a new code from HTCDev.com
2) Flash TWRP back to the phone with fastboot. TWRP 3.0.2 is recommended for compatibility with MM firmware.
3) Flash the desired custom ROM. The custom ROM will be rooted (if you flash the Dev Ed ROM, you can select root in the AROMA installer).
For the Record, I have made a back up of my Lollipop via TWRK. I also backed it up using Titanium back up, just in case.
Always good to make backups. Although be aware, that RUU will wipe the phone, including internal storage. So if you picked internal storage as your backup location, you'll want to move/copy to another location (removable SD is okay, otherwise to computer or cloud).
Also note that restoring app data (as well as call logs, SMS) using Titanium, after RUU or ROM flash should be okay. But don't restore any system data, as this can cause problems.
Click to expand...
Click to collapse
redpoint73 said:
Again, my responses in red font:
Click to expand...
Click to collapse
Ok i came back to this old post. I forgot all about it, it really is helping me alot.
My questioin is after i Relock the bootloader can i do a factory wipe? will this remove everything from my phone and bring it back to stock?
I relocked my phone, but all my apps and contacts are their.
Bricked ?
ELEVO said:
Ok i came back to this old post. I forgot all about it, it really is helping me alot.
My questioin is after i Relock the bootloader can i do a factory wipe? will this remove everything from my phone and bring it back to stock?
I relocked my phone, but all my apps and contacts are their.
Click to expand...
Click to collapse
I think i may have bricked my phone? I went and installed an RUU firmware file for Marshmallow as most instruct to do via Fastboot. All went well, installation completed and i was able to send command to phone to reboot. when it tried to reboot. white screen with HTC Comes on and then goes almost black with a very light dark grey background.
Phone would not reboot into anything but dark screen. even when i restarted it with power button. the only thing that worked for me, was Holding Down Power/Volume and quickly hit the volume down button before device would vibrate to reboot, that took me into recovery. Below is what i see in Recovery.
Phone now has new software
***RELOCKED***
m8_UL_CA PVT SHIP S-ON
HBOOT-3.1.0.0000
RADIO-4.0 [email protected]
OpenDSP-V56.2.2-00593-M8974_FO.0126
0S-6.20.502.5
eMMC-boot 2048MB
APR 14 2016,19:39:46.0
HBOOT
<Vol UP> to previous item
<Vol Down> to next item
<Power> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
I was able to run and "IMAGE CRC" via boot loader. it gave me alot of numbers after calculating. not sure if that is a good sign ?
Things I've tried in Recovery.
1. Recovery goes back to black screen.
2. SHOW BARCODE Works- 3 bar codes showed up.
3. Fastboot works. but when i try command "adb devices" it says list of devices attached. but nothing shows up
4. Tried to do a factory reset and tries to do it, then a black phone pops up on screen with green arrow sgoing in circles for like 10 seconds. then reboots to dark screen.
Please Help :crying: Thanks
Can anyone help me with this? I bought the phone with me on vacation and now using an HTC Developer Edition that the button down doesn't work and Volume down button us sunk in But at least i have my phone with all my contacts and apps , For now ?
I would like to know if i can unbrick my other HTC . Thanks.
Late in responding, as I was on work travel myself, and not on XDA for over a week.
ELEVO said:
I think i may have bricked my phone?
Click to expand...
Click to collapse
It's basically impossible for you to do anything with an s-on M8 that will actually brick it. That is the good thing about s-on.
ELEVO said:
I went and installed an RUU firmware file for Marshmallow as most instruct to do via Fastboot. All went well, installation completed and i was able to send command to phone to reboot. when it tried to reboot. white screen with HTC Comes on and then goes almost black with a very light dark grey background.
Click to expand...
Click to collapse
I think you only flashed the firmware.zip and not the RUU. Based on the condition here, and your other thread you created here: https://forum.xda-developers.com/htc-one-m8/help/htc-one-e-m8-fastboot-issues-t3757628
I clearly described above to flash the firmware.zip then the RUU. They are 2 completely different things. Firmware is about 80 MB and only contains hboot, radio, and a few other things. RUU is a full image that is 1.5 GB.
No boot after flashing signed firmware is normal, as it expects the RUU to be run afterwards.
ELEVO said:
Fastboot works. but when i try command "adb devices" it says list of devices attached. but nothing shows up
Click to expand...
Click to collapse
adb doesn't work in fastboot mode. Only fastboot commands will work in fastboot mode. You can only use adb when booted to OS (not an option for you, obviously) or alternately in custom recovery TWRP. So what you describe (adb not working) is normal and expected.
However, fastboot is enough to get the phone working from the described condition.
Hello, I'm Daniel,
My problem: I have unlocked my HTC Desire 825's bootloader a few months back, don't ask me why, I didn't know what I was doing. My device is S-ON, not rooted and has its bootloader unlocked. It has TWRP installed and working. When trying to install a new OS (it was my first time trying) I did not backup anything, wiped my system and pretty much every partition on the phone. Now there is nothing that I can boot to. I have attempted to download some 2PUKIMG's for returning my phone to stock but my CID prevented me from installing them as they were not the right ones, if anybody knows where to get the H3G_ROI 2PUKIMG for free I'm all open ears. I do not have a supercid and cannot change it because of S-ON, things like moonshine wont work and I've already tried firewater(basically the old version of moonshine) but I do not have superuser and supersu installation does not work properly. For some reason fastboot does not work with my laptop(I do not think that it is the phone's fault). ADB works just fine when I launch into TWRP. I've looked around at as many places as possible but due to the phone's recent launch just over a year ago I could not find much apart from paid downloads for the 2PUKIMG's I need but I highly doubt that paying for the download will get me to where I want.
What I need is either another tested method to S-OFF my device via ADB/TWRP/Fastboot(if I get it to work) or the 2PUKIMG H3G_ROI. The S-OFF would allow me to install superuser and/or install any 2PUKIMG with the supercid. The 2PUKIMG will(obviously) return the stock ROM to my phone.
Thank you for any replies and/or help and it is very appreciated!
-Daniel
Have you tried http://forum.gsmdevelopers.com/showthread.php?t=24278
---------- Post added at 10:00 AM ---------- Previous post was at 09:54 AM ----------
Also, have you tried side loading while in recovery? Just send the superuser file to phone and install through recovery
Post your getvar result please.
fastboot getvar all
Hi, do not worry
I already had this problem and I ended up solving it,
I made a post on how I solved it
you can find it right here
Good luck, If you have any questions, please do not hesitate
A month ago I unlocked the bootloader to get root access but i started getting troubles with some apps. Today i decided to return it to stock so i did what i used to do with my nexus devices that was to flash clean firmware(the one from the this forum) and re lock bootloader.
After the bootloader lock I got the message that my device was corrupted and wasn't able to boot. I used the Msmdownload tool to fix it. Everything was great until I realized there was no bootloader or modem versions in the bootloader. Also I am not getting the latest update.
TL;DR
Unlocked to root
Root caused problems
Factory reset, clean firmware flash, oem lock
Device corrupted message, no boot
MsmDownloadTool to unbrick.
Can boot into system
No boot or baseband version, no february update.
You faked up with restoring device after device is corrupted message
Richard_Black said:
A month ago I unlocked the bootloader to get root access but i started getting troubles with some apps. Today i decided to return it to stock so i did what i used to do with my nexus devices that was to flash clean firmware(the one from the this forum) and re lock bootloader.
After the bootloader lock I got the message that my device was corrupted and wasn't able to boot. I used the Msmdownload tool to fix it. Everything was great until I realized there was no bootloader or modem versions in the bootloader. Also I am not getting the latest update.
TL;DR
Unlocked to root
Root caused problems
Factory reset, clean firmware flash, oem lock
Device corrupted message, no boot
MsmDownloadTool to unbrick.
Can boot into system
No boot or baseband version, no february update.
Click to expand...
Click to collapse
I don't have either listed in my bootloader and received last update
---------- Post added at 09:40 PM ---------- Previous post was at 09:37 PM ----------
EugenStanis said:
You faked up with restoring device after device is corrupted message
Click to expand...
Click to collapse
So what is the correct method how I'd he mess up the restore. I used the msm tool just like I did on my op6t is there something new to do it correctly on op7tpro?
toolhas4degrees said:
So what is the correct method how I'd he mess up the restore. I used the msm tool just like I did on my op6t is there something new to do it correctly on op7tpro?
Click to expand...
Click to collapse
No, but in this case he should leave bootloader unlocked because relocking after unlock is buggy and somethins is corrupted like it was in my case and they had to replace mobo.