Hello,
I wanted to install the newest nightly update. But when I tap "Install" it says "Unable to restart to recovery". Ive got a few questions here:
What causes this and why doesnt the errormessage explain itself?
Can I apply the update myself somehow (Where is it located and how can I apply it)?
Greetings,
Ravior
Honestly, if you don't know how to get to recovery then I highly suggest you stay away from modding android phones.
Beamed in by telepathy.
shivadow said:
Honestly, if you don't know how to get to recovery then I highly suggest you stay away from modding android phones.
Beamed in by telepathy.
Click to expand...
Click to collapse
Did I say anything about that? You assumed that and simply insulted me.
Of course I know how to get there. I did that several times for installing and trying out stuff. But how should I know that I can simply go there and apply the update by selecting it and chosing install. I asked for that information and you didnt gave it to me, instead you where insultive. Had a bad day or what?
can you boot in Recovery via adb (adb reboot recovery)
Have same issue. The other day I tried to go from viperone 3.5, s off, unlocked/rooted, twrp installed 3.0.
After the installation attempt using clean install, got stuck in a bootloop. Finally was able to install a stock rom 5.0 using ruu. S off, unlocked
Now I cannot log into recovery.. I get that splsh screen with red waning text below but the top section in red says cannot load recovery. I tried a few reasons over the last few days, trying fastboot/adb but can not load twrp. Tried everything from 2.8xxx to 3.xxx.
cid is 11111111.
Also tried some other ruu's but says its not for my device, but it is. Unlocked, m9, hima
scratching my head here, I must be missing something
RaviorMetal said:
Did I say anything about that? You assumed that and simply insulted me.
Of course I know how to get there. I did that several times for installing and trying out stuff. But how should I know that I can simply go there and apply the update by selecting it and chosing install. I asked for that information and you didnt gave it to me, instead you where insultive. Had a bad day or what?
Click to expand...
Click to collapse
If had read anything to do with installing ANY rom it will have detailed instructions on how to install it, usually it will tell you how to get to recovery too. Even if it doesn't tell you how to get to recovery it is a google search away.
Spoon feeding is a no-no. You must try to solve issues yourself before asking and refer to the forum for "obtuse" issues.
As for the detailed output of why it failed, usually you get some sort of error code or phrase as to why. If not then you have to start looking into logcat. You will notice that it failed to boot to recovery so manually doing it will resolve that, then you just follow whatever guide you were using after that step..
I understand that things can get overwhelming when flashing devices but it is all part of the learning curve and knowing how to navigate your device is essential before even considering changing anything.
Further more, I didn't insult you. I didn't intend to. It was an honest opinion because if you don't do the basics you WILL "become a cropper", you'll probably brick your device.
Back to basics is my advice before you proceed to mess with ANY device.
bigjailerman said:
Have same issue. The other day I tried to go from viperone 3.5, s off, unlocked/rooted, twrp installed 3.0.
After the installation attempt using clean install, got stuck in a bootloop. Finally was able to install a stock rom 5.0 using ruu. S off, unlocked
Now I cannot log into recovery.. I get that splsh screen with red waning text below but the top section in red says cannot load recovery. I tried a few reasons over the last few days, trying fastboot/adb but can not load twrp. Tried everything from 2.8xxx to 3.xxx.
cid is 11111111.
Also tried some other ruu's but says its not for my device, but it is. Unlocked, m9, hima
scratching my head here, I must be missing something
Click to expand...
Click to collapse
Yup, missing the cid is supercid. No longer valid. Cid and mid must match the firmware you're trying to install.
The bigger issue is not being able to get to recovery at all... Will it go to download mode?.
Obviously you've read flippy's thread and sneakyghosts thread?
Beamed in by telepathy.
Yes those threads brought me back from a soft brick....
I remember back when I first rooted and installed viper there has to be a way to change the cid, isnt there?
Thanks btw
bigjailerman said:
Yes those threads brought me back from a soft brick....
I remember back when I first rooted and installed viper there has to be a way to change the cid, isnt there?
Thanks btw
Click to expand...
Click to collapse
Yes there is, it's done via a command in fastboot but I can't remember if you can do it with just root or if you need s-off too..
Beamed in by telepathy.
So, obviously you both didn't read my thread since it contains a guide for changing your CID/MID...
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
So, obviously you both didn't read my thread since it contains a guide for changing your CID/MID...
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Aint nobody got time fo dat!. It's confusing for idiots like me.. My attention span is... Oo ice cream!..
Beamed in by telepathy.
Flippy498 said:
So, obviously you both didn't read my thread since it contains a guide for changing your CID/MID...
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
No honestly, I re read everything and t is right there, no question and it is appreciated. I was just concentrating on how to get back to a version of TWRP. Finally I was able to do that and still unlocked, S Off and have a TWRP 2.7 but every time I try to go higher I get the cannot boot recovery in the red letters. My bottom line was to install a 7.1.x rom. That is what caused all my original issue, tried to update into 7.1.1 RR Rom and everything crashed. I used a RUU you have in that thread (THANK YOU) and was able to get out of bootloop on RR bootanimation. I am running on stock 5.x, rooted as well.
Is there anyway to still move forward? Do I need to change the CID to match the firmware I choose within the device choices?
Thanks for all your earlier posts and it has become invaluable and thanks for any advice going forward.: good:
TWRP versions above 3.x require your M9 to be at least using firmware 3.x. The same applies to android 6/7 based roms. Either restore the correct CID for your SKU, flash the latest available 3.x RUU for that SKU and then install all missing updates via the software update function of the stock rom or restore the correct CID and look for a full-wipe firmware pack in Sneakyghost's firmware thread (located in the development section). Be aware that his packs don't contain a rom but that shouldn't be a problem at all if you want to install RR, anyway.
Related
Hi, first post in a long while.
I've got myself the HTC One M8 on contract with EE (Orange/T Mobile convergence here in the UK), after having it for a few weeks I've really got to the point where I want to mod it, remove apps and the like. So I went through the ballache that is the non root way of backing it up, HTCDev unlocked the bootloader and attempted to root it. Root doesn't stick it seems. I can't get S-off as I get the Whelp error. Sunshine says nope.
I've tried to extract the backups and mod them before restoring and they're either multipart tar archives that 7zip refuses to fully extract or with TWRP, the folders show up as files?!.
Reflashing to ARHD gives me a white screen with red text telling me it's internal software and shouldn't be public.
How do I gain control of my device? I'm fed up with having freaking kid mode on my power menu. I don't want Deezer on my phone.
Please, for the love of any deity that may or may not exist, please help me!
So no one knows how to get rw access on 4.4.3?
mrme01 said:
Hi, first post in a long while.
I've got myself the HTC One M8 on contract with EE (Orange/T Mobile convergence here in the UK), after having it for a few weeks I've really got to the point where I want to mod it, remove apps and the like. So I went through the ballache that is the non root way of backing it up, HTCDev unlocked the bootloader and attempted to root it. Root doesn't stick it seems. I can't get S-off as I get the Whelp error. Sunshine says nope.
I've tried to extract the backups and mod them before restoring and they're either multipart tar archives that 7zip refuses to fully extract or with TWRP, the folders show up as files?!.
Reflashing to ARHD gives me a white screen with red text telling me it's internal software and shouldn't be public.
How do I gain control of my device? I'm fed up with having freaking kid mode on my power menu. I don't want Deezer on my phone.
Please, for the love of any deity that may or may not exist, please help me!
Click to expand...
Click to collapse
mrme01 said:
So no one knows how to get rw access on 4.4.3?
Click to expand...
Click to collapse
I would try to get root working 100% first of all, as it sounds like something isnt right. I know you're not s-off but that should not stop you from unlocking your bootloader (which you appear to have done alright) and having root. Which guide did you follow to get where you are? Have you flashed SuperSU from recovery, did you check with a rootchecker app?
When did you try sunshine? Before you had made any modifications? I would have thought sunshine would have worked ok, it seems it requires a device running stock to run properly though, so I would use it before changing/flashing anything else.
gsmyth said:
I would try to get root working 100% first of all, as it sounds like something isnt right. I know you're not s-off but that should not stop you from unlocking your bootloader (which you appear to have done alright) and having root. Which guide did you follow to get where you are? Have you flashed SuperSU from recovery, did you check with a rootchecker app?
When did you try sunshine? Before you had made any modifications? I would have thought sunshine would have worked ok, it seems it requires a device running stock to run properly though, so I would use it before changing/flashing anything else.
Click to expand...
Click to collapse
Here's what I've done so far,
I downloaded the toolkit, used that once I had unlocked the bootloader, flashed a recovery (can't remember which one now), made a backup (multipart tars), flashed the root zip, tried to remove apps and realised I don't have RW access even with root, chmod in FX Explorer didn't take with an access denied. Got fed up, attempted to flash ARHD 11.1 as I used it on my old Sensation, didn't work (sat there for 20 minutes with red text telling me it's confidential), investigated to no avail how to extract the tars from the backup,tried Firewater and got several Whelps in a row (screen goes off just before the Whelp, like it wants to reboot but doesn't). Got the nope from firewater twice, reflashed the recovery to TWRP, tried to extract that (got errors on the APK directories, folders showed up as files). Got annoyed again and posted here.
I had ORD from my Sensation for a long time, almost weekly I was trying out new ROMs, but this is just deflatingly humiliating as I don't have the foggiest to get RW access. And what's worse is I don't know who I should complain to, HTC or EE for making it as watertight as a ducks bum.
Hopefuly this should shine some light on what to do next.
Can you give the outcome of :
Fastboot getvar all
And delete the serial and imei before posting the picture !
Mr Hofs said:
Can you give the outcome of :
Fastboot getvar all
And delete the serial and imei before posting the picture !
Click to expand...
Click to collapse
Is there anything I can give from the device itself? I'm at work and I don't have the right to install ADB or plug in any unknown devices into their machines.
mrme01 said:
Is there anything I can give from the device itself? I'm at work and I don't have the right to install ADB or plug in any unknown devices into their machines.
Click to expand...
Click to collapse
Getting your software numbers from the OS will do. But that's only needed now if you are on your original stock rom. Custom roms are usually based on .401 wwe versions so that could lead to wrong info !
mrme01 said:
Here's what I've done so far,
I downloaded the toolkit, used that once I had unlocked the bootloader, flashed a recovery (can't remember which one now), made a backup (multipart tars), flashed the root zip, tried to remove apps and realised I don't have RW access even with root, chmod in FX Explorer didn't take with an access denied. Got fed up, attempted to flash ARHD 11.1 as I used it on my old Sensation, didn't work (sat there for 20 minutes with red text telling me it's confidential), investigated to no avail how to extract the tars from the backup,tried Firewater and got several Whelps in a row (screen goes off just before the Whelp, like it wants to reboot but doesn't). Got the nope from firewater twice, reflashed the recovery to TWRP, tried to extract that (got errors on the APK directories, folders showed up as files). Got annoyed again and posted here.
I had ORD from my Sensation for a long time, almost weekly I was trying out new ROMs, but this is just deflatingly humiliating as I don't have the foggiest to get RW access. And what's worse is I don't know who I should complain to, HTC or EE for making it as watertight as a ducks bum.
Hopefuly this should shine some light on what to do next.
Click to expand...
Click to collapse
Very strange, I can understand firewater not working as its seems to only work on pre-4.4.3 firmware, so sunshine should really work (its the one that costs $25). Its up to the individual whether they want to go down the sunshine route or not, but it seems going fully s-off is the best way to go to make sure you don't have any problems flashing etc. I found this on the Sensation also.
I s-off'd my sensation and the process seemed ridiculously dodgy and involved hooking up to a pc to run a program, whilst using a thin piece of wire on the back of the phone. Essentially it tricked the phone into thinking it was going into a certain service mode so an exploit could be ran to gain s-off.
Sunshine s off:
http://forum.xda-developers.com/showthread.php?t=2792487
Mr Hofs said:
Getting your software numbers from the OS will do. But that's only needed now if you are on your original stock rom. Custom roms are usually based on .401 wwe versions so that could lead to wrong info !
Click to expand...
Click to collapse
Running stock.
As I can't do anything outside ot the browser here,
https://drive.google.com/folderview?id=0B-L4hmzi8YQScV9rZ0ZlcVVXTWM&usp=sharing
gsmyth said:
Very strange, I can understand firewater not working as its seems to only work on pre-4.4.3 firmware, so sunshine should really work (its the one that costs $25). Its up to the individual whether they want to go down the sunshine route or not, but it seems going fully s-off is the best way to go to make sure you don't have any problems flashing etc. I found this on the Sensation also.
I s-off'd my sensation and the process seemed ridiculously dodgy and involved hooking up to a pc to run a program, whilst using a thin piece of wire on the back of the phone. Essentially it tricked the phone into thinking it was going into a certain service mode so an exploit could be ran to gain s-off.
Sunshine s off:
http://forum.xda-developers.com/showthread.php?t=2792487
Click to expand...
Click to collapse
I never did S-off my Sensation and it did everything I wanted it to do. I had 4EXT on there with some strange flashing mode that seemed to make it work.
I've noticed dumlock on TWRP. Would that work for flashing the SU zip?
Your firmware definitely supports the latest roms. Try some custom roms. Easiest way to get it working. Maxumus HD is also a "stock" rom. Maybe that's worth a shot. And with the stock recovery it also works to get s-off via sunshine.
Mr Hofs said:
Your firmware definitely supports the latest roms. Try some custom roms. Easiest way to get it working. Maxumus HD is also a "stock" rom. Maybe that's worth a shot. And with the stock recovery it also works to get s-off via sunshine.
Click to expand...
Click to collapse
When I tried ARHD, all I got was a white screen and some red text like it was refusing to boot. What do I do if it happens? Dumlock? I always do a cache/dalvik wipe so it's not that.
When you install a custom rom you always need to perform a full wipe before installing it !
Mr Hofs said:
When you install a custom rom you always need to perform a full wipe before installing it !
Click to expand...
Click to collapse
It could be that, it's been months since I've played with ROMS as I stuck with CM on the Sensation since the release of the M8 as I knew I was going to upgrade to it.
Mr Hofs said:
When you install a custom rom you always need to perform a full wipe before installing it !
Click to expand...
Click to collapse
Nope, that didn't work. Still got the red text with ARHD 11.1 as it's the only ROM I have to hand.
I didn't say to try arhd again take another rom when you have time.
mrme01 said:
Nope, that didn't work. Still got the red text with ARHD 11.1 as it's the only ROM I have to hand.
Click to expand...
Click to collapse
Where do you get the red text? When flashing in recovery or does it flash ok but not boot up?
gsmyth said:
Where do you get the red text? When flashing in recovery or does it flash ok but not boot up?
Click to expand...
Click to collapse
I get the red text stratight after rebooting it Power and volume to do a battery disconnect. It seems to flash okay, sometimes it crashes and turns offafter exiting AROMA, other times it takes me back to TWRP. I just tried to reflash with Dumlock, no difference.
Turn off screen timeout option in the recovery. You got a pic from the bootloader and the red text
Mr Hofs said:
Turn off screen timeout option in the recovery. You got a pic from the bootloader and the red text
Click to expand...
Click to collapse
I don't have a 2nd phone to take a picture on. I doubt the screen timeout will do much as I can unlock it and when it comes back to recovery it works fine. But I'll try both of those suggestions when I get home in 5ish hours.
Thank you for your help so far, both of you. Much appreciated
Hello Everyone,
I am having an issue with my M8.
I decided to try out SkyDragon, give it a shot.
I downloaded the ROM, put it on my SDcard. Flashed Philz 6.25 recovery, did NOT make a nandroid backup (I know i'm an idiot),then proceeded to flash the rom via Philz.
I flashed the Rom, and followed all the instructions, I then rebooted the phone. Still stuck at the bootscreen. I read the Q&A and tried to flash the rom multiples times. Still stuck on the boot screen. I have an unlocked bootloader with S-ON.
I just got this phone a few months ago and I am unable to take it out of this state. Could use some help. Thank you.
Is your firmware up to date? Not sure about Skydragon specifically, but long boot times (along with broken WiFi) is often a symptom of outdated firmware.
Let the phone alone for 10 minutes or so, and see if it eventually boots, and isn't actually "stuck" (but rather just takes a REALLY long time).
To flash a different ROM, adb push it to internal storage, or put in on your SD with a USB card reader connected to your computer. Then boot into recovery and flash.
redpoint73 said:
Is your firmware up to date? Not sure about Skydragon specifically, but long boot times (along with broken WiFi) is often a symptom of outdated firmware.
Let the phone alone for 10 minutes or so, and see if it eventually boots, and isn't actually "stuck" (but rather just takes a REALLY long time).
To flash a different ROM, adb push it to internal storage, or put in on your SD with a USB card reader connected to your computer. Then boot into recovery and flash.
Click to expand...
Click to collapse
Hello,
I've actually tried flashing another ROM "Android HD Revolution" I believe. The phone shows the HTC Screen along with some red text at the bottoms saying "this build is for developer purposes only....". The phone then stays on the HTC screen for ~3mins then reboots and continues to boot loop.
You just need to flash the new firmware that is found in the sky dragon OP.
Easiest way is to use fastboot. Google fastboot firmware m8. Lots of guides out there. It's only a few commands.
Edit: Should have asked if you are s-off. That will make a difference in your ability to flash new firmware.
Sent from my HTC One_M8 using XDA Free mobile app
OLEO34 said:
You just need to flash the new firmware that is found in the sky dragon OP.
Easiest way is to use fastboot. Google fastboot firmware m8. Lots of guides out there. It's only a few commands.
Edit: Should have asked if you are s-off. That will make a difference in your ability to flash new firmware.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Hello Thanks for the reply.
However, I am currently S-ON, I have searched ways to achieve S-OFF but they all require installing a ROM. However, I cannot flash any rom, I will just get the bootloop. If you could advise on a method that would work for my situation, I would be very grateful.
Default-G8way said:
... However, I cannot flash any rom, I will just get the bootloop. If you could advise on a method that would work for my situation, I would be very grateful.
Click to expand...
Click to collapse
Start with fastboot getvar all command in fastboot/bootloader, put the result here (delete serialno and imei no.) .. then we'll see whether is there any stock ROM available for your device.
Default-G8way said:
Hello Everyone,
I am having an issue with my M8.
I decided to try out SkyDragon, give it a shot.
I downloaded the ROM, put it on my SDcard. Flashed Philz 6.25 recovery, did NOT make a nandroid backup (I know i'm an idiot),then proceeded to flash the rom via Philz.
I flashed the Rom, and followed all the instructions, I then rebooted the phone. Still stuck at the bootscreen. I read the Q&A and tried to flash the rom multiples times. Still stuck on the boot screen. I have an unlocked bootloader with S-ON.
I just got this phone a few months ago and I am unable to take it out of this state. Could use some help. Thank you.
Click to expand...
Click to collapse
You needed to make sure you have the latest GPE software, s-off and supper cid... Also you need to know and have ADB/FASTBOOT installed on your PC.. All which can be found throughout all of the various threads.... Right now you soft bricked your device and needed to return to stock... And stay the process over.
lilbigdude1 said:
You needed to make sure you have the latest GPE software, s-off and supper cid... Also you need to know and have ADB/FASTBOOT installed on your PC.. All which can be found throughout all of the various threads.... Right now you soft bricked your device and needed to return to stock... And stay the process over.
Click to expand...
Click to collapse
You don't "need" the latest gpe software. The rom runs fine on the latest sense firmware.
Mr Hofs said:
You don't "need" the latest gpe software. The rom runs fine on the latest sense firmware.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=53838669
So ? Just like i said.....no need for gpe
Issue Resolved!
Hello Everyone.
The issue is resolved. Through many flashes, wipes and commands. Its done. I was able to flash the rom, let the rom sit for ~20mins, and it finally booted up into Lollipop. I now have no wifi. However, I should be able to follow the FAQ to get S-OFF and fix my wifi!. Thanks team. I really appreciate it.
I got the bootloader unlocked with HTC Dev and rooted, installed TWRP. I installed Revolution (?) rom but had the restarting issue I presume because of the firmware being incompatible. Searching ways to achieve S-Off leaves me a bit confused though. Could someone hold my hand through the process or direct me to where I can update my Firmware and apply the newer Roms please? Thanks.
xgonzox said:
I got the bootloader unlocked with HTC Dev and rooted, installed TWRP. I installed Revolution (?) rom but had the restarting issue I presume because of the firmware being incompatible. Searching ways to achieve S-Off leaves me a bit confused though. Could someone hold my hand through the process or direct me to where I can update my Firmware and apply the newer Roms please? Thanks.
Click to expand...
Click to collapse
OMG do I agree with that post! When you ask about how to do this, they point you to a thread with 300+ post and say its in there, go read... Ive been reading for 2 freaking days and Im more confused then ever!!! CID, SUPERCID, brick without them... NO explanation from there. REALLY!?
Now some people go OUT OF THEIR way to help you, where others seem to just say search the forums. With any of the searches, there is 4000+++ hits, it would be time to upgrade before I read them all. Ive read. Im still reading. Heck, I'm about to ADB back to stock to by pass s-off because of the lack of info, or its scattered across 5 or 6 threads. Sorry for the rant, but Im tired, sleepy, and cant find the info on the threads. Ive done my time reading, came out worse then I started...
Guys, I know your first few weeks at xda can be frustrating, but there are reasons why we do it this way and why requests for hand-holding don't go over well.
First, this is, as the name says, a developers' forum where a certain amount of technical knowledge is assumed. All of us were noobs once, but we got past that by reading and asking intelligent questions, not throwing up our hands and begging to be spoon-fed. If you get less-than-helpful responses, it's often because what seems baffling to you is a question that gets asked regularly to the point that people get tired of dealing with it. S-off and firmware updating are in that realm.
Second, and more importantly, once you go s-off and start mucking with firmware, there is a very real chance of bricking your phone if you're not careful. So having a solid understanding of what you're doing is critical. The people who brick are the ones who rush the process and miss or skip important steps because they don't realize why they exist.
Now, having said that, I can give you a little guidance.
S-off for the M9 is pretty idiot proof at the moment. It's only possible through a paid app, Sunshine. You download it, install it, and it will tell you if s-off is possible for your phone. If so, you buy a license for $25 and run it. Done.
Updating firmware is trickier, but this thread is the best place to start. Read the whole thing from the beginning (especially the first few posts), and if there's anything you don't understand, asking specific questions will usually get you helpful responses.
Good luck!
Good advice from iElvis to go slowly and try not to rush before gaining necessary knowledge .
Usually for example with firmware flashing thread all relevant info is contained in the first four posts written by original poster.
Basically if you are S on you may only flash firmware that matches your currently installed software.
When you have S off (as described above by iElvis) then you may flash any firmware, by changing cid if necessary.
Firmware flashing done in download mode via command
Fastboot flash zip nameofirmware.zip
Phone will flash part of firmware then reboot to download mode,
Then you enter same command again and remainder of file is flashed.
Then you're good to flash custom roms based on the firmware you flashed.
Sent from my HTC One M9 using XDA Free mobile app
paul_59 said:
Good advice from iElvis to go slowly and try not to rush before gaining necessary knowledge .
Usually for example with firmware flashing thread all relevant info is contained in the first four posts written by original poster.
Basically if you are S on you may only flash firmware that matches your currently installed software.
When you have S off (as described above by iElvis) then you may flash any firmware, by changing cid if necessary.
Firmware flashing done in download mode via command
Fastboot flash zip nameofirmware.zip
Phone will flash part of firmware then reboot to download mode,
Then you enter same command again and remainder of file is flashed.
Then you're good to flash custom roms based on the firmware you flashed.
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
I am not new to xda or flashing roms , but definitely new to htc device. The problem is Alot of threads don't seem to explain "Why" .
your quote here has explained something so simple, that unfortunately was made to sound so complex in some other threads. Also many threads give slightly differing or slightly incomplete instructions. thats why I notice many people asking for a "FULL guide" and even some people offering to "donate if you can help me step-by-step update firmware" .
So , can i ask, just to clarify, after S-off, then SuperCID, we can flash any firmware update from any region? eg If i am from 1.32.710 i can flash 1.40.401 firmware? And ONLY then i can flash a custom rom that MUST be 1.40.401?
simonbigwave said:
So , can i ask, just to clarify, after S-off, then SuperCID, we can flash any firmware update from any region? eg If i am from 1.32.710 i can flash 1.40.401 firmware? And ONLY then i can flash a custom rom that MUST be 1.40.401?
Click to expand...
Click to collapse
Yes, you can flash any firmware for your model. You can't for example, flash cdma firmware on a gsm phone (nor should you try).
But you don't necessarily have to match rom to firmware. It's advisable for best performance, but not always necessary. in this case, however, there is a conflict between firmware and kernel across 1.32 and 1.40—they need to be the same. That means you can run a 1.40 rom over 1.32 firmware as long as you have a 1.32 kernel running (this is my current configuration). But if you have 1.40 firmware, you pretty much have to run a 1.40 rom.
I am missing somethihng some where.. Ive tried the steps above, although no "guide" said anything about supercid. However, Ive tried to flash the firmware, and i do get a cid mismatch error. So I'm stuck and lost. I dont know what to do... Cid is being reported differently depending on how I get it, Adb reports htc_001, the app and the scrip report CWE_001, and I cant seem to find anything to flash to it. Im literally pulling out my hair.
klloyd said:
I am missing somethihng some where.. Ive tried the steps above, although no "guide" said anything about supercid. However, Ive tried to flash the firmware, and i do get a cid mismatch error. So I'm stuck and lost. I dont know what to do... Cid is being reported differently depending on how I get it, Adb reports htc_001, the app and the scrip report CWE_001, and I cant seem to find anything to flash to it. Im literally pulling out my hair.
Click to expand...
Click to collapse
As far as I know, get S-off from Sunshine app. Easiest way. Then in adb set your sid to super cid..try here a full guide, after u have used sunshine app to get s-off http://forum.xda-developers.com/showthread.php?t=2317536 u need to get S-off first AFAIK....i agree its confusing.
Ok so real quick….I'm not tech savvy. I usually get the new HTC One, watch a youtube tutorial, and install ViperROM. This time around I get to the finish line and I keep getting the same "set_perm failed" …..I tried twrp hima 2.8.6.4 …still the same problem. I'm ready to give up. Please help me
We need more details.. Is your phone s-off? Also did you flash the correct firmware? And is your bootloader unlocked.
Sent from my HTC One M9 using XDA Free mobile app
NjEcTi0N said:
Ok so real quick….I'm not tech savvy. I usually get the new HTC One, watch a youtube tutorial, and install ViperROM. This time around I get to the finish line and I keep getting the same "set_perm failed" …..I tried twrp hima 2.8.6.4 …still the same problem. I'm ready to give up. Please help me
Click to expand...
Click to collapse
What exactly is "the finish line"? Like @bigp951 said, we need more details. Please list everything you've done to this point and exactly what you're doing that returns that error.
I'm no expert but the process i used was.
- Get phone, Unlock bootloader via htcdev, (hadnt realise the sunshine apk does both unlocking bootloader and s-off at the time >< doh!), then s-off using sunshine, flash custom recovery via fastboot, flash superSU and install superSU apk for root, flash 1.40.401.x firmware with fastboot, flash viper rom (i had to do this twice as the first time an error came up which was helpfully listed in the troubleshooting section of the dev's post for viper, boom, it was all done. Backed up for safety
hope that helps you get to the source of the error.
when you say you flashed supersu and then installed supersu apk, what does that mean? I ask because when you flash the beta-superSu it installs the apk for you. But then again you had to be rooted to get s-off (someone correct me if I am wrong). Also, did you check the md5 before you tried to flash? Did you file a ticket with team viper? What was the error that showed up on the first failed attempt? Did you post on the viperonem9 thread and ask them for help? what is your cid and mid? supercid may help... and what is the current state of the phone? Is it still working?? Can you go into recovery? Still lots of questions.
If you want a clean slate to start over with find the CORRECT RUU and run it. Then you will be stock all over again (disclaimer--Find the RUU thread and follow instructions completely).
Obviously I am no expert either. I just run through the troubleshooting list when problems arise. But I try to help or point you in the direction of someone who can.
EDIT- there is also a newer official version of twrp for the m9. As @jollywhitefoot asked, you did not state what the finish line is nor what you were doing to return the error. If you installed the rom and made a backup than it sounds like the phone was working...
bigp951 said:
when you say you flashed supersu and then installed supersu apk, what does that mean? I ask because when you flash the beta-superSu it installs the apk for you. But then again you had to be rooted to get s-off (someone correct me if I am wrong). Also, did you check the md5 before you tried to flash? Did you file a ticket with team viper? What was the error that showed up on the first failed attempt? Did you post on the viperonem9 thread and ask them for help? what is your cid and mid? supercid may help... and what is the current state of the phone? Is it still working?? Can you go into recovery? Still lots of questions.
If you want a clean slate to start over with find the CORRECT RUU and run it. Then you will be stock all over again (disclaimer--Find the RUU thread and follow instructions completely).
Obviously I am no expert either. I just run through the troubleshooting list when problems arise. But I try to help or point you in the direction of someone who can.
EDIT- there is also a newer official version of twrp for the m9. As @jollywhitefoot asked, you did not state what the finish line is nor what you were doing to return the error. If you installed the rom and made a backup than it sounds like the phone was working...
Click to expand...
Click to collapse
Seems like this was a waste of time drive by. For someone "screaming for help" you would think they would reply when someone tries to help them.
maybe he's asleep...lol
jollywhitefoot said:
Seems like this was a waste of time drive by. For someone "screaming for help" you would think they would reply when someone tries to help them.
Click to expand...
Click to collapse
yeah, I know what you mean they ask a question and disappear for 2 days LOL
or he's thrown the phone under a bus and hates us all!!!! >< either way, there is a lot of helpful tips and tricks to be found in these forums. I think as mentioned above a good idea may be to try to return fully to stock and start again.... carefully following each step to the letter.
tomorio said:
or he's thrown the phone under a bus and hates us all!!!!
Click to expand...
Click to collapse
Is that an "uh-oh" moment? lol gotta love that uh-oh protection
bigp951 said:
Is that an "uh-oh" moment? lol gotta love that uh-oh protection
Click to expand...
Click to collapse
RIP OP
I'm currently running Android Revolution HD on my new M9, unlocked, s-off also.
Found out that I have the battery is faulty, so I need to return it to stock, and get it back the shop for a replacement.
However, I stupidly didn't make a back up of my stock rom.
The CID of my phone is O2___01
I've downloaded the stock rom from this site, and flashed it using the RUU command. However when it flashes, then tells me to reboot, it still has Android Revolution HD on it.
I've spent a few hours browsing the forum, and still I've come to no avail.
Any help would be well appreciated!
Webbage said:
I'm currently running Android Revolution HD on my new M9, unlocked, s-off also.
Found out that I have the battery is faulty, so I need to return it to stock, and get it back the shop for a replacement.
However, I stupidly didn't make a back up of my stock rom.
The CID of my phone is O2___01
I've downloaded the stock rom from this site, and flashed it using the RUU command. However when it flashes, then tells me to reboot, it still has Android Revolution HD on it.
I've spent a few hours browsing the forum, and still I've come to no avail.
Any help would be well appreciated!
Click to expand...
Click to collapse
You don't provide much information so it's hard to help. So let's start at the bginning: What firmare version are you using? (It's stated in Download Mode in the line with "OS" at the beginning.)
You tried to flash a RUU? Which one? Have there been any error outputs? If yes, which ones? Since you're S-OFF flashing a RUU should not be a problem at all so these outputs are very important if you want any help.
I tried to flash 1.40.206.8 -> 2.10.206.2 from this page
Code:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Also I followed this,
Code:
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
downloaded the correct RUU zip, tried to flash, got the error code telling me I need to immediately flash again which I did. Rebooted, and it just set up Android Revolution HD again.-
My firmware currently is 2.10.206.2
Im sure it's something stupid I missing out?
Webbage said:
I tried to flash 1.40.206.8 -> 2.10.206.2 from this page
Code:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Also I followed this,
Code:
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
downloaded the correct RUU zip, tried to flash, got the error code telling me I need to immediately flash again which I did. Rebooted, and it just set up Android Revolution HD again.-
My firmware currently is 2.10.206.2
Im sure it's something stupid I missing out?
Click to expand...
Click to collapse
As far as I know Sneakyghost doesn't provide any RUUs. Those are only firmware packages that do not contain a rom. So it's no miracle that you're still booting ARHD.
You can download O2 RUUs from here, here or here. Any of the X.XX.206.X files will work since you are S-OFF. Do you have a SD card that is not bigger than 32gb? If yes, format it to fat32, copy one O2 RUU to its root directory and rename that file to "0PJAIMG.zip". If you then boot to Download Mode you will be asked to push the Volume Up button and the RUU will start flashing. If it reboots to system instead of rebooting to Download Mode you will have to power off your phone and boot to Download Mode manually. The RUU will continue then. At the end you will be asked to push the power button so that your phone gets shut down. If you now start your phone you will be back on a stock system.
Be aware that there is no RUU for your current firmware. Since you're S-OFF that doesn't matter but your phone will be downgraded at the end.
Ahh no wonder! haha
Going to try this shortly, so will let you know how I get on!
After its flashed, I'll be good to lock again and go s-on? Then return to the shop?
Webbage said:
Ahh no wonder! haha
Going to try this shortly, so will let you know how I get on!
After its flashed, I'll be good to lock again and go s-on? Then return to the shop?
Click to expand...
Click to collapse
Relock only after you successfully tested that your device is booting normaly. After that you theoretically could re-S-ON. (But I would never do that because there is always a risk of hardbricking your phone if you re-S-ON and there is anything still modified that you didn't notice. For safety reasons S-OFF should always be considered as a oneway.)
Edit: I'm not completely sure but I actually doubt that they will check whether your phone was S-OFFed or not. If I think about the people who are working at the O2 or vodafone shops in my city I would say they do not even know what a bootloader is...
Agreed, use the s-off command to change back to "LOCKED" and leave it s-off. Too much of a risk otherwise.
If in the unlikely event they see it, you can play dumb, because a few rare people have gotten s-off phones from the factory and it doesn't prove you did anything.
Flippy498 said:
Relock only after you successfully tested that your device is booting normaly. After that you theoretically could re-S-ON. (But I would never do that because there is always a risk of hardbricking your phone if you re-S-ON and there is anything still modified that you didn't notice. For safety reasons S-OFF should always be considered as a oneway.)
Edit: I'm not completely sure but I actually doubt that they will check whether your phone was S-OFFed or not. If I think about the people who are working at the O2 or vodafone shops in my city I would say they do not even know what a bootloader is...
Click to expand...
Click to collapse
All sorted mate! Thanks a lot for your help!
What recovery am I best restoring on it?
Webbage said:
All sorted mate! Thanks a lot for your help!
What recovery am I best restoring on it?
Click to expand...
Click to collapse
Didn't the RUU flash the corresponding stock recovery?
Flippy498 said:
Didn't the RUU flash the corresponding stock recovery?
Click to expand...
Click to collapse
My bad, I didn't check.
All sorted now, thanks again bud!