Hi!
So what I want to do is only to create a nandroid backup. I dont want to install a custom ROM and I dont want to root my phone. So I tried to boot recovery-RA-hero-v1.5.2, but got a "FAILED: (remote: not allowed)". I have figured out that this is because I have a locked bootloader.
Now for my question. I would prefer not to go through the complicated process of creating a gold card. Is it enough to change my SPL? Im not really sure what a bootloader is... it feels as if it should be enough to change my SPL, but I want to be sure before I try it. Any information or link to good information would be greatly appreciated!
Cheers,
edit: Also, another question: what kind of check is it that I run into when I fail loading the recovery image? Is it the CID? Or a SIM-lock?
Well, from what I have learned it wont help to change my SPL. The question is, must I root my phone to get a nandroid backup? One question that have risen is, what is a bootloader? Is it the same thing as an SPL? Any help would be a real lifesaver!
to create a nandroid backup you need the custom recovery image, period.
not sure what you are talking about bootloader and spl, that stuff is not related to the recovery image. to change the spl you need the custom recovery aswell.
SPL ≠ recovery ≠ bootloader.
Bootloader is an actual part of the software, that loads the OS.
recovery, like the Amon Ra 1.5.2. recovery, is a toolkit to flash and manage your hardware / software. Something like a BIOS in a regular computer, with added ability to partition, flash other parts of the phone, or like you wanted: to backup the ROM entirely.
SPL is something that operates before the bootloader: Secondary Program loader; the small lead-in to it. Hero phones however (tested with the GSM version, test sample: 2 phones) have no limitation so no need for special SPL's for most roms / recovery's. Using a non updated or not most recently updated HTC RUU, you can use Flashrec 1.1.2 or 1.1.3 to get the Amon RA recovery effortless.
I believe, correct me if I'm wrong: That the CID lock, which is the SIM-lock, is on SPL level. However, this should not interfere with one of the other three. It simply allows you (or rather denies) to use a certain SIM card and register on certain networks.
Disclaimer: I'm not an Android guru. I only recently looked into this matter. Please correct me if I'm wrong.
Additionally, read the Wiki's:
http://wiki.xda-developers.com/index.php?pagename=GSM Hero Guides
kendong2 said:
to create a nandroid backup you need the custom recovery image, period.
not sure what you are talking about bootloader and spl, that stuff is not related to the recovery image. to change the spl you need the custom recovery aswell.
Click to expand...
Click to collapse
But for some reason I cant make a nandroid backup with my phone at its current state, so something must be done.
Uniqron said:
SPL ≠ recovery ≠ bootloader.
Bootloader is an actual part of the software, that loads the OS.
recovery, like the Amon Ra 1.5.2. recovery, is a toolkit to flash and manage your hardware / software. Something like a BIOS in a regular computer, with added ability to partition, flash other parts of the phone, or like you wanted: to backup the ROM entirely.
SPL is something that operates before the bootloader: Secondary Program loader; the small lead-in to it. Hero phones however (tested with the GSM version, test sample: 2 phones) have no limitation so no need for special SPL's for most roms / recovery's. Using a non updated or not most recently updated HTC RUU, you can use Flashrec 1.1.2 or 1.1.3 to get the Amon RA recovery effortless.
I believe, correct me if I'm wrong: That the CID lock, which is the SIM-lock, is on SPL level. However, this should not interfere with one of the other three. It simply allows you (or rather denies) to use a certain SIM card and register on certain networks.
Disclaimer: I'm not an Android guru. I only recently looked into this matter. Please correct me if I'm wrong.
Additionally, read the Wiki's:
http://wiki.xda-developers.com/index.php?pagename=GSM Hero Guides
Click to expand...
Click to collapse
Thank you very much!
Correct me if Im wrong, but does not Flashrec actually flash the recovery on my phone? Preferable I would like to just load it once to create a nandroid-backup, so nothing is changed on the phone.
Also, if I want to do it on the most recent HTC RUU, must I root the phone then? Or is there some other way?
Another question: Heros that are produced today, do they have this lastest HTC RUU that flashrec does not work on?
Cheers,
1: you can always fastboot into recovery, without flashing it
2: flashrec exploits a bug in 2.6.27 kernel. It's not linked to RUU.
adwinp said:
1: you can always fastboot into recovery, without flashing it
2: flashrec exploits a bug in 2.6.27 kernel. It's not linked to RUU.
Click to expand...
Click to collapse
Hi! Just to clarify: I want to fastboot into a custom recovery that allows nandroid. This isnt always possible without some effort, is it? Because I failed with some error message on my first attempts, as described in my first post.
Anyhow, I tried to use flashrec and it worked. However, it flashed the recovery image on my computer. This is not what I wanted. I would also like an easy solution that works for the version av Hero that flashrec does not work for.
I then tried to change the SPL as described in to "update-hero-hboot-1.76.2007-signed". After this I tried running "fastboot boot recovery-RA-hero-v1.5.2.img". This worked. However, I am unsure if it worked because I changed SPL or becuase I already had changed the recovery image with flashrec. Could someone clarify this for me? I really want to understand this before I dare help my friends with their phones.
sandis84 said:
Hi! Just to clarify: I want to fastboot into a custom recovery that allows nandroid. This isnt always possible without some effort, is it? Because I failed with some error message on my first attempts, as described in my first post.
Click to expand...
Click to collapse
this is correct. from some softwarelevel (2.73.110.26?) upwards you can not fastboot a recovery image.
sandis84 said:
Anyhow, I tried to use flashrec and it worked. However, it flashed the recovery image on my computer. This is not what I wanted. I would also like an easy solution that works for the version av Hero that flashrec does not work for.
Click to expand...
Click to collapse
in fact it is too late for that. you can try to get the original recovery image and flash it over the custom image, but i don't see the benefit for that.
sandis84 said:
I then tried to change the SPL as described in to "update-hero-hboot-1.76.2007-signed". After this I tried running "fastboot boot recovery-RA-hero-v1.5.2.img". This worked. However, I am unsure if it worked because I changed SPL or becuase I already had changed the recovery image with flashrec. Could someone clarify this for me? I really want to understand this before I dare help my friends with their phones.
Click to expand...
Click to collapse
AFAIK fastbooting of the recovery works now because you already have the custom recovery image (which you got through flashrec), so yes, flashing the spl was unnecessary.
tbh i wouldn't mess with that stuff more, you have a good setup now, any unnecessary flashing (especially of the spl) brings the danger of bricking your phone...
Uniqron said:
I believe, correct me if I'm wrong: That the CID lock, which is the SIM-lock, is on SPL level. However, this should not interfere with one of the other three. It simply allows you (or rather denies) to use a certain SIM card and register on certain networks.
Click to expand...
Click to collapse
You are wrong!
CID Lock ≠ SIM Lock
The CID lock (carrier id) prevents you from flashing a different carriers ROM to your device (i.e. a ROM with a different CID). The SIM lock prevents you from using a different carriers SIM in your device.
Regards,
Dave
Related
I've had this unlocked Hero SPL for a while now, and it's super useful for flashing unsigned updates and cool stuff like custom splashes. Unfortunately i've not been able to distribute it... until now!
WARNING
A PROBLEM FLASHING THE SPL CAN BRICK YOUR DEVICE - as such, proceed with caution. Don't flash this unless you need it, flash at your own risk, flash only to a GSM Hero and do not interrupt the flashing process (which happens on the first reboot after applying the zip). YOU HAVE BEEN WARNED!
The SPL, version 1.76.2007, is in the usual update zip format.
Download: MoDaCo
Enjoy!
P
MoDaCo splash...
http://android.modaco.com/content/s...ial-splash-on-your-device-with-a-modaco-logo/
P
What exactly is the SPL and what benefits will we get from flashing it?
modaco said:
it's super useful for flashing unsigned updates and cool stuff like custom splashes.
Click to expand...
Click to collapse
^^ What he said...
P
fleming222 said:
What exactly is the SPL and what benefits will we get from flashing it?
Click to expand...
Click to collapse
http://wiki.xda-developers.com/index.php?pagename=SPL%20Questions%3F
Searching is hard so why not get someone else to do it
Thanks modaco I will try it after christmas, just to be sure that my phone won't be bricked till I learn some things better
Nice!
Thanks Paul (and any other eventual leakers not mentioned).
Now I can get rid of my hacked SPL
do we copy this zip file to sd card and update through recovery image? like other radio, rom and theme applying?
Would I be right in thinking I need to CID unlock my Orange Hero (rooted) before I can flash an unlocked SPL? Or is that the whole point of an unlocked SPL?
Not planning on using phone on another network at the moment, just want rid of all locks.
I remember way back when, on my Kaiser, I needed to run Kaiserunlocker.exe when hardSPL'd it, but can't remember the exact procedure.
Many thanks
Phone:
UK Orange Hero (rooted)
ROM: MCR 2.8
Radio: 63.18.55.06IU_6.35.08.22
HBOOT:
hero cvt ship s-on
hboot-1.76.0007 (hero10000)
microp-010f
radio-6.35.08.22
on the device.
Thanks.. easy as cake.
Ready to flash all fun.
First your roms and now this ..
Forever thankfull.
Sulus1179 said:
Would I be right in thinking I need to CID unlock my Orange Hero (rooted) before I can flash an unlocked SPL? Or is that the whole point of an unlocked SPL?
Not planning on using phone on another network at the moment, just want rid of all locks.
Click to expand...
Click to collapse
There should be no need for that, and long as you have rooted phone and a custom recovery you should be able to flash it.
You're confusing CID lock with SIM lock. The SIM lock is what limits your phone to a specific network.
CID lock is software enforced "label" that is used to limit what software can be installed on your phone.
For example: Your Orange branded phone is identical hardware-wise to my sim-unlocked Nordic Hero. However the phones have different CID values. Assuming you havn't rooted it you would be stuck to just running Orange approved ROMs on it. No other ROM would be allowed to be installed even if your hardware is identical and can run it.
CID is a non-issue once the phone is rooted and you got a custom recovery on it that allow us to install whatever we want since it ignores CID.
I'm not that versed in the SIM lock function, but from what I've seen it seems you can get some code to disable it from within Android (look around on the forum for instructions), or there is the serial cable method (explained in a sticky on this forum).
Hope that explains it.
just flashed and flashed modaco startup image too. its so cool. thnx a lot Paul. btw. how to make startup images? cheers
Sulus1179 said:
Would I be right in thinking I need to CID unlock my Orange Hero (rooted) before I can flash an unlocked SPL? Or is that the whole point of an unlocked SPL?
Click to expand...
Click to collapse
Just flashed on a Orange Hero Thanks Paul.
This is what i have now:
HERO CVT ENG S-OFF
HBOOT-1.76.2007 (HERO10000)
Just a little Help
Noob... although i have done this on a windows mobile.... how do i flash it? just as i do it with an update.zip?
Thanks.... and please forgive my ignorance.
You read the first post which answers your question exactly.
P
flashed and done! thanks Paul
P.S. I HATE flashing SPL's because of what can go wrong if not done correctly
finally..superCID without a serial cable..~~
thanks paul,
flashed on t-mobile g2,
HERO CVT ENG S-OFF
HBOOT-1.76.2007 (HERO10000)
i tried to flash the startup image, but failed
EDIT: i flashed again and it works the startup image!!
thanks a lot paul
great work paul, will try this out
Works great just flashed it.
Anyone that can provide the original hero splash1 image logo so i can flash it over a t-mobile logo.
Thanks
Sorry, me again!
I needed to re-lock and ‘stockify’ my HTC M8 today for a few reasons. It ended up taking me 4 hours, and I still have no idea if it’s ‘back’ to the way it was before I rooted it. Before you carry on reading, please know I’m fully aware any lack of understanding is my fault, and perhaps I should have realised that compared to the N4s blissfully easy steps, the HTC was a massive can of worms. However, I’m going to ask the below anyway, so hopefully someone is friendly and helpful enough to aid me in my quest for enlightenment of android stuff without me having to spend more hours searching than actually reading useful stuff…
So coming from a Nexus 4, where the guide is super simple:
http://forums.androidcentral.com/ne...3923-guide-nexus-4-factory-image-restore.html
It turned out to be SERIOUSLY complicated. I’ve put down a ‘typical’ guide below, and put my questions about each step in bold. Sorry if it seems like I’m just complaining and being trite, but I’d like to know if A) I’ve missed a far easier way of doing this and if not B) is it just me that seems to have a massive amount of issues?
1. Made sure your device is S-Off. If not, download firewater and S-Off your device.
Assume this is just a thing that some phones have and some don’t?
2. Restore a nandroid of the stock Sense ROM, or find a stock ROM to flash. You'll have to dig around; I used a nandroid.
WHY? Is there no such thing as downloadable factory images for HTC One M8s? Also, where’s the step that says ‘run the commands fast boot erase user data, fast boot erase cache’ etc.?
3. Flash SuperSU.zip in recovery on top of the stock Sense ROM. You can find the SuperSU.zip here: http://download.chainfire.eu/396/SuperSU
Fair enough… still an another extra step compared to N4.
4. Use fast boot to flash the stock firmware zip to your device based on CID (this includes the stock recovery)
-This took SO MUCH EFFORT. Turns out I had to Super CID so that one of the recovery zips worked, because I was getting “FAILED (remote: 42 custom id check fail)” - and I’m now paranoid because I have no idea how important it is to get the correct CID-numbered ‘stock firmware’ etc. The ‘stock firmware’ zips seem to contain boot, radios, recovery .imgs, and with about 4 billion versions of the M8 apparently existing, could I have flashed a wrong boot or radio or something? ARE they even different per CID? Then I changed the CID back to O2___001 in case I need to take it in for warranty repairs, but is that trackable? Would someone know that I’ve messed around with the CID? Could someone going to look at my Nexus and be like “Oh this radio seems to be the one we’d expect on a HTC_001, NOT an O2___001 CID device, they must have tampered with it”.
—OH, and I had to boot into RUU mode as well, which apparently no one felt like explaining what the hell that’s for. So I’ve got and HBoot, a Fastboot, and RUU mode, which no clear way of knowing what to flash where…??
—-ALSO there was a HELL of a lot of faffing by people throwing around CID, MID, Verizon, Sprint, and comments like this doesn’t work on this AT&T model but will only work on non branded eu models with a flag attached to the speaker with an SSID of “600TZL” and a it MUST have a holographic projector otherwise your CID must equal the square root of the MID so that the factory image will know which ID your phone carrier provides through an inter web”.
5. Boot back up into sense, and follow this guide to remove the tampered banner in recovery. http://forum.xda-developers.com/show....php?t=2708565
-Is this just removing a banner? or is it ‘you’ve removed the banner from a visual point of view only, but if they actually look into it it will still appeared ‘tampered’.
6. Follow this guide to lock your boot loader and make it say **LOCKED** instead of **RELOCKED**. http://forum.xda-developers.com/show....php?t=2708571
-So ‘fast boot OEM lock’ doesn’t work on HTCs then- is that an N4 thing? Why all that complicated cmd line stuff? And on a side note, why is it that when referring to re-locking a N4 people call it just that- locking. But with an HTC people on XDA seem to say ‘to make the banner say locked’ as if its not actually locking it, just changing a bit of writing on the boot loader.
7. Boot your device back up, and open SuperSU. Go into settings and find the "full unroot" option and run that. Reboot your device like it suggests.
Does running the unroot zip (can’t find the thread) work? So I can make it appear like the HTC is brand new out of the box? Rather than having to go through the ‘first setup’ screen?
Other question: people seem to keep yammering on about modded RUUs, is there one? is there a couple? (i.e. should I view it a bit like TWRP and CWM- there’s others but there’s one everyone really uses). And if I ‘flash’ a modded RUU, again, is there an easily accessible stock one?
It's really not that complicated! I think the problem is comparing it to a Nexus 4 which is designed to be easily unlocked and locked, due to being a more developer orientated device.
An RUU is a stock image (like the Nexus images) and a modded one would just have the CID/MID requirement removed or something so it can be used on more phones. It would still be the stock, untampered image.
Also, the whole CID/MID thing is only applicable to American devices which vary between GSM and CDMA radios. ANY international modem will work in Europe and you will never find the wrong one.
S-Off is like unlocking the bootloader on a Nexus device except that in this case, its an extra step after unlocking the bootloader in order to be able to modify every partition and flash unsupported firmware in OEM mode. Every consumer phone is initially shipped S-On.
Thanks very much Veryone's v. helpful around here. Just a few more questions based on what you've said:
Matt said:
Also, the whole CID/MID thing is only applicable to American devices which vary between GSM and CDMA radios. ANY international modem will work in Europe and you will never find the wrong one.
Click to expand...
Click to collapse
Why did I have to Super-CID to install the stock recovery? And did I do the right thing by going back to my carrier CID afterwards?
Matt said:
S-Off is like unlocking the bootloader on a Nexus device except that in this case, its an extra step after unlocking the bootloader in order to be able to modify every partition and flash unsupported firmware in OEM mode. Every consumer phone is initially shipped S-On.
Click to expand...
Click to collapse
Although I've read in quite a few places I shouldn't have to S-On to take it in for a warranty repair, because some arrive to people S-off and they can't prove that you did it? Is that right?
Thank you for the step-by-step list. I am in the process of restoring my phone and all the guides say to look for "version-main", but that line is empty for me. What other information can I use to determine what recovery image to flash. Also the reason I want to go back to unrooted is so I can recieve OTA updates.
legolator said:
Thank you for the step-by-step list. I am in the process of restoring my phone and all the guides say to look for "version-main", but that line is empty for me. What other information can I use to determine what recovery image to flash. Also the reason I want to go back to unrooted is so I can recieve OTA updates.
Click to expand...
Click to collapse
this also happened to me- just another thing to confuse....
Can you not receive OTA updates if you're rooted? I thought it was just if you were running a different ROM?
tmorterlaing said:
this also happened to me- just another thing to confuse....
Can you not receive OTA updates if you're rooted? I thought it was just if you were running a different ROM?
Click to expand...
Click to collapse
I was under the impression that flashing a custom recovery removes the ability for the phone to install OTA updates. But I could of course be wrong about that.
Ok, so I have recently switched to a HTC One M8 and I am puzzled by a few things regarding unlocking the bootloader and flashing ROMs. Coming from a Samsung Galaxy s4 I have never really needed to worry about unlocking my bootloader. I have looked up on the subject and have found that with unlocking the bootloader using HTCdev you have to flash boot.img everytime after flasing a ROM on the HTC One. Does this also apply to the HTC One m8 ? If so does anybody have a better means of unlocking the bootloader without needing to do this after every ROM flash.
JJGLive said:
Ok, so I have recently switched to a HTC One M8 and I am puzzled by a few things regarding unlocking the bootloader and flashing ROMs. Coming from a Samsung Galaxy s4 I have never really needed to worry about unlocking my bootloader. I have looked up on the subject and have found that with unlocking the bootloader using HTCdev you have to flash boot.img everytime after flasing a ROM on the HTC One. Does this also apply to the HTC One m8 ? If so does anybody have a better means of unlocking the bootloader without needing to do this after every ROM flash.
Click to expand...
Click to collapse
You don't have to replace hboot unless you want to get rid of certain firmware messages, like the tampered flag. Unless you are sending your phone in for warranty work, you won't likely care about it, since you only see it in fastboot/hboot mode. The only thing the token does, besides unlock the boot loader, is remove certain preloaded apps, like the flashlight, which will screw up further OTA updates.
However, I would suggest you look into going S-off, as it makes locking/unlocking the boot loader possible without contacting HTC at all, and without messing up OTA updates. You also gain the freedom to change your CID (if you ever want to convert to stock Developer Edition), SIM unlock, and revert to older firmware if necessary (such as restoring an older RUU to go back to stock) However, S-off is "security off", so there is an increased chance of bricking the phone if you aren't careful.
Ok so what i understand is: To install a custom rom I first have to get s-off, then unlock bootloader, root and install custom recovery and I am good to go? Please help me if I have missed anything.
I am used to flashing a rom every week on my Samsung. This is why I am so worried that I might do something wrong.
Edit: I have also found this link: http://forum.xda-developers.com/showthread.php?t=2265618 please tell me if it is the correct way to do it.
JJGLive said:
Ok so what i understand is: To install a custom rom I first have to get s-off, then unlock bootloader, root and install custom recovery and I am good to go? Please help me if I have missed anything.
I am used to flashing a rom every week on my Samsung. This is why I am so worried that I might do something wrong.
Click to expand...
Click to collapse
I would suggest you use this guide.
Im going to use it this friday to root my phone.
Ok so if I understand correctly now...using that guide I will not need to use htcdev and it will not be neccesary for me to flash boot.img after every rom flash?
JJGLive said:
Ok so what i understand is: To install a custom rom I first have to get s-off, then unlock bootloader, root and install custom recovery and I am good to go? Please help me if I have missed anything.
Click to expand...
Click to collapse
Not quite. To flash a custom ROM, all you need to do is unlock the bootloader, install custom recovery, and flash a ROM. In addition, I highly recommend you make a nandroid backup before flashing anything
S-off is only needed if you want to avoid the bootloader unlocking method via HTCDev.com (and HTC therefore having a record of you unlocking by IMEI); or to flash hboot, radio, firmware, or a few other things (such as SIM unlock). S-off is not needed to flash a ROM.
One caveat, if your phone presently has older firmware, you will experience some severe bugs on any Sense 2.x based ROM (long boot times, broken WiFi or Bluetooth) and having S-off is required to manually update the firmware. So, while in literal terms, S-off is not needed to flash a ROM. But if the above applies to you, you need s-off to manually update the firmware and get the ROM to work correctly. Alternately, you can OTA to the latest firmware before modding the phone. You will need to list your phone's hboot and present software version for us to tell you what firmware you are on.
Also, its not necessary to root before flashing a custom ROM. You will be rooted after you flash a custom ROM.
JJGLive said:
Edit: I have also found this link: http://forum.xda-developers.com/showthread.php?t=2265618 please tell me if it is the correct way to do it.
Click to expand...
Click to collapse
Definitely not correct. That guide is for the M7. Be careful what device forum section you are in, and stay in the M8 section.
Hell, I feel like a noob again. Ok so no boot.img flash after flashing a rom is needed.
JJGLive said:
Hell, I feel like a noob again. Ok so no boot.img flash after flashing a rom is needed.
Click to expand...
Click to collapse
Nope, not needed. Boot.img will flash automatically along with the ROM. Don't assume that anything on the M7 applies to the M8. These things change as the hardware changes, and every device has its own subtle differences.
redpoint73 said:
Nope, not needed. Boot.img will flash automatically along with the ROM. Don't assume that anything on the M7 applies to the M8. These things change as the hardware changes, and every device has its own subtle differences.
Click to expand...
Click to collapse
Thank you so much...this also applies if I use the htcdev unlock. Still no boot.img then?
JJGLive said:
Thank you so much...this also applies if I use the htcdev unlock. Still no boot.img then?
Click to expand...
Click to collapse
Correct, no need to flash boot.img separately when flashing ROMs, if you unlock the bootloader via HTCDev.com (or by the S-off way).
redpoint73 said:
Correct, no need to flash boot.img separately when flashing ROMs, if you unlock the bootloader via HTCDev.com (or by the S-off way).
Click to expand...
Click to collapse
Thank you very much...I feel much more welcome in the htc one m8 thread than I did when I first started on the samsung s4 thread. You have made me feel very welcome!
Thankfully we have freegee for LG OG. Bootloader is really dangerous please keep in mind before you go for any tutorials
Alright, I will start at the beginning. I plugged my phone into my PC. HTC Sync manager popped up and told me there was an update for my device. So I was excited knowing it was the Marshmallow update. Everything was going smooth until my cable disconnected while it was installing. It failed and my phone was doing nothing. So like an idiot, I rebooted it.. Now my phone will not go past the HTC logo on boot. I tried wiping the cache partition from Android Recovery but no luck. I'm not really sure what to do at this point. My phone was not rooted, and it is *Locked*. I just want my phone back.. Any help would be so much appreciated, because I'm pretty unsure of what to do.
By the way I am not worried about saving what is on the phone. It's the HTC One M8 (Verizon).
Hi,
I'm a beginner here myself but based on what I read lately it might be possible to go into fastboot mode and flash a Lollipop RUU file.
You'll need a couple of tools on your PC (adb and fastboot) and a step by step guide, both easy to find with a quick search. The harder part is to locate the appropriate file to flash, at least I have trouble with that piece...
Good luck !
Gnondpom said:
it might be possible to go into fastboot mode and flash a Lollipop RUU file.
Click to expand...
Click to collapse
Depends on how far it got in the update. If enough of the MM update installed, LP may constitute a "downgrade", which is not allowed unless you have s-off. In that case, OP may need to use the Marshmallow RUU. But I agree, that RUU is the best bet. RUU will wipe the phone, but I think we're past the point of trying to recovery data at this point, anyway.
TO the OP, what does it say for OS number on the bootloader screen?
Presumably, the phone is s-on, as it sounds like it was never modified?
The Verizon RUUs are here: http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Another option to flashing the RUU using fastboot, is to put the RUU zip on an SD card (if you have one) and flash. Instructions are in the link (Option 2). This is probably easiest of the options (again, assuming you have an SD card), especially if you don't have fastboot setup, and aren't familiar with it).
redpoint73 said:
Depends on how far it got in the update. If enough of the MM update installed, LP may constitute a "downgrade", which is not allowed unless you have s-off. In that case, OP may need to use the Marshmallow RUU. But I agree, that RUU is the best bet. RUU will wipe the phone, but I think we're past the point of trying to recovery data at this point, anyway.
TO the OP, what does it say for OS number on the bootloader screen?
Presumably, the phone is s-on, as it sounds like it was never modified?
The Verizon RUUs are here: http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Another option to flashing the RUU using fastboot, is to put the RUU zip on an SD card (if you have one) and flash. Instructions are in the link (Option 2). This is probably easiest of the options (again, assuming you have an SD card), especially if you don't have fastboot setup, and aren't familiar with it).
Click to expand...
Click to collapse
OS # is (6.21.605.3) The update was just about finished before it disconnected. So I believe you are correct. I don't mind data loss, would rather just get the device functional again.
It is S-ON, it was never modified in any way. I will check out the links and see what I can do. Thank you for all the info!:good:
Hi guys,
Got a phone a need to revive. I received unusable. Mother gave it to my sisters friend and she said it doesnt work. I now see why cause he was trying to mod it.
I managed to once get into TWRP but cant anymore. It was UNLOCKED but now RELOCKED which I possibly made it a little harder for me.
So currently "fastboot getvars" reports back all the info. It's showing version-main 6.13.206.5 and I just want official O2 stock so can use the phone. Ideally sim unlocked but could hassle O2 for that later since it was my mother's contract.
Basically just want to get a working recovery image on and then flash stock. CID is 02__001
Any suggestion to revive this welcomed, please.
So it still have twrp on it ? If yes, boot to twrp recovery then restore the stock backup.
You can find all you need in my thread - https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Post #1 - how-to
Post #3 - you'll find the O2 stock backup
Post #5 - you'll find O2 firmware, install firmware after you restore the backup
ckpv5 said:
So it still have twrp on it ? If yes, boot to twrp recovery then restore the stock backup.
You can find all you need in my thread - https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Post #1 - how-to
Post #3 - you'll find the O2 stock backup
Post #5 - you'll find O2 firmware, install firmware after you restore the backup
Click to expand...
Click to collapse
No, I cannot get into it. When I select HBOOT, then select recovery it just shows white screen, ANDROID and then back to the menu. TWRP no longer works. That's what I'm trying to fix or put on a stock recovery image and then stock OS/firmware.
Just wondering if I need to UNLOCK it again and also do I need USB debug on. I cannot boot into OS so unable to set USB debug.
To UNLOCK bootloader can that be done if you can only get into bootloader menu? S-ON is enabled but not 100% that will stop recovering it? That's just for signed rom/firmware and I just need something stock.
You don't need usb debugging on to unlock the bootloader as it is done on fastboot mode (bootloader).
First I suggest you install the O2 firmware only then see whether you can boot to OS (assuming the OS is still stock base)
Second, re unlock bootloader with unlock_code.bin that you can get from htcdev.com, install twrp 3.x and restore the stock backup and relock bootloader and reflash firmware. This will get your device to fully stock.
So far, I don't see any RUU for your device version that you can get for free, only paid site has it.
Tainted said:
I managed to once get into TWRP but cant anymore. It was UNLOCKED but now RELOCKED which I possibly made it a little harder for me.
Click to expand...
Click to collapse
Relocking the bootloader renders the phone unable to boot into OS by definition, as it expects RUU to be run (but as mentioned, RUU is not available for your CID unless you pay - but it's not needed).
Also, you can't flash TWRP with a locked bootloader, again by definition. The primary limitation of an unlocked bootloader, is that it prohibits flashing unsigned recovery images.
So as suggested, simply unlock the bootloader again (with existing unlock bin code, or get a new one using the HTCDev.com process again). Then flash TWRP and a stock TWRP backup using ckpv5's backup collection (linked in his signature).
redpoint73 said:
Relocking the bootloader renders the phone unable to boot into OS by definition, as it expects RUU to be run (but as mentioned, RUU is not available for your CID unless you pay - but it's not needed).
Also, you can't flash TWRP with a locked bootloader, again by definition. The primary limitation of an unlocked bootloader, is that it prohibits flashing unsigned recovery images.
So as suggested, simply unlock the bootloader again (with existing unlock bin code, or get a new one using the HTCDev.com process again). Then flash TWRP and a stock TWRP backup using ckpv5's backup collection (linked in his signature).
Click to expand...
Click to collapse
ok, well made some progress.
unlocked the bootloader the official way. Very quick which I was surprised.
This then repoened up the recovery menu working.
then used fastboot to install latest twrp
then installed S.Team-JW-7.5.0.zip !!!
The install and everything looked good, no errors and now just not turning on. I think now it's a brick? Does not seem to be coming back to the bootloader menu and certainly does not try to boot.
Wondering if end of the line. Any suggestions? I assume need to get into TWRP and flash stock update from ckpv5.
Must say thanks for replies guys. ckpv5 you done some good work on here.
Tainted said:
The install and everything looked good, no errors and now just not turning on. I think now it's a brick? Does not seem to be coming back to the bootloader menu and certainly does not try to boot.
Click to expand...
Click to collapse
It's really hard to brick this phone (especially with s-on) just flashing TWRP and flashing ROMs. Probably not a brick.
At what point exactly did it shut down/not reboot? ROM installed with no errors, and when you tried to reboot, it went dark? You aren't specific on this point.
How much charge was on the battery when you were flashing the ROM? Did you leave it a long time flashing the ROM, or rebooting, that simply may have drained the battery to shutdown?
Try leaving the phone on charger for several hours, then hold power+vol up for a minute or so, and see if any change (even if just stuck on HTC logo screen).
redpoint73 said:
It's really hard to brick this phone (especially with s-on) just flashing TWRP and flashing ROMs. Probably not a brick.
At what point exactly did it shut down/not reboot? ROM installed with no errors, and when you tried to reboot, it went dark? You aren't specific on this point.
How much charge was on the battery when you were flashing the ROM? Did you leave it a long time flashing the ROM, or rebooting, that simply may have drained the battery to shutdown?
Try leaving the phone on charger for several hours, then hold power+vol up for a minute or so, and see if any change (even if just stuck on HTC logo screen).
Click to expand...
Click to collapse
Hi there,
Well I expect the bootloader to be separate from the rest so we can get into TWRP and normally get out of this situation?
The ROM install finished, battery was at about 80% and everything looked good and I let it reboot the phone. And then it went dead. Right now the PC keeps beeping as a device has just connected and then again as though it's disconnected. I'm watching the device manager and dont see it listed during the connect but device manager tree refreshes. My S7 edge shows up. It flash an orage dot twice, so appears to be a in loop.
I charged the phoned and no luck with any of the power+ vol +/- keys. No response from any of those? I let the phone sit till flat and no orange light and then charged it today and still nothing. Not sure if it's a bad battery but it was up at 83% showing in the TWRP menu and working plugged or unplugged.
It's become a challenge now to make it work, I havent had to mod phones since my HTC One which got heavily modded and then back to stock. I stopped doing that after modding every phone I had since HTC Desire Android 2.3. So been about 4 years since doing all this again. Never had one that was totally bricked.
Tainted said:
Well I expect the bootloader to be separate from the rest so we can get into TWRP and normally get out of this situation?
Click to expand...
Click to collapse
You are correct that bootloader (AKA hboot) is a separate partition, isn't touched by TWRP, and in fact is "protected", and can't be modified with s-on. Only an official signed zip (RUU, OTA, zip) can write to hboot when s-on, which is one of the reasons why I say this phone is hard to brick with s-on, just by flashing TWRP and flashing ROMs.
Tainted said:
Right now the PC keeps beeping as a device has just connected and then again as though it's disconnected. I'm watching the device manager and dont see it listed during the connect but device manager tree refreshes.
Click to expand...
Click to collapse
You won't connect to the phone by PC in any way, unless you can get the phone to power on, at least to bootloader.
A few additional suggestions/comments I made to another user (in another thread) who by strange coincidence has a very similar condition (apparent brick after flashing a ROM): https://forum.xda-developers.com/showpost.php?p=73062871&postcount=10
But to be honest, it's not looking too good, since the condition hasn't changed after charging and trying the button combos.
redpoint73 said:
You are correct that bootloader (AKA hboot) is a separate partition, isn't touched by TWRP, and in fact is "protected", and can't be modified with s-on. Only an official signed zip (RUU, OTA, zip) can write to hboot when s-on, which is one of the reasons why I say this phone is hard to brick with s-on, just by flashing TWRP and flashing ROMs.
You won't connect to the phone by PC in any way, unless you can get the phone to power on, at least to bootloader.
A few additional suggestions/comments I made to another user (in another thread) who by strange coincidence has a very similar condition (apparent brick after flashing a ROM): https://forum.xda-developers.com/showpost.php?p=73062871&postcount=10
But to be honest, it's not looking too good, since the condition hasn't changed after charging and trying the button combos.
Click to expand...
Click to collapse
Cheers for that. Not getting much except for the 2 brief flashes of orange light.
Any chance the battery is totally messed and this is the problem?
Tainted said:
Any chance the battery is totally messed and this is the problem?
Click to expand...
Click to collapse
It's possible. Or it might be something else like motherboard or emmc. It's impossible to say for sure.