Hi I just tried to flash Skydragon 4.0 on my bootloader unlocked, supercided with S-OFF one m8 running latest MM GPe firmware. The installation completed successfully but it gets stuck on the Google splash screen.
Does anyone know why this is? Do I need to be rooted? My recovery is TWRP 3.0.2
You shouldn't install any Sense based ROM on GPE firmware, won't work.
Sense based ROM requires Sense firmware. GPE system partition is too small for Sense based ROM.
When I tried flashing the Skydragon sense based firmware TWRP couldn't mount my internal storage, cache, system or data. Do I need an earlier version of TWRP or is it something else that's causing it?
I don't really understand what you're trying to say.
There is no Skydragon sense based firmware, only Skydragon sense based ROM.
Firmware and ROM are two different thing.
Are you saying you tried to install firmware.zip with TWRP ?
If yes .. this is wrong. You can't install firmware.zip with TWRP, you only fastboot flash it or use microsSD method.
Now you still have google splash screen when trying to boot ?
If yes, you still have wrong firmware problem.
Post your fastboot getvar all result without serial & imei no.
ash4naught said:
I tried flashing the Skydragon sense based firmware TWRP
Click to expand...
Click to collapse
As ckpv5 pointed out, firmware and ROM aren't the same thing. Firmware refers to hboot, radio, etc. that is separate from the ROM. Firmware is not installed in TWRP.
Did you convert to GPE using s-off and RUU; or just flashed a GPE based ROM?
Is your bootloader screen black or white?
Also, post the getvar info as directed by ckpv5 above.
I flashed the GPe firmware using fastboot and then flashed the GPe ROM using TWRP. Bootloader screen is black. I will post the getvar data.
ash4naught said:
I flashed the GPe firmware using fastboot and then flashed the GPe ROM using TWRP. Bootloader screen is black. I will post the getvar data.
Click to expand...
Click to collapse
As mentioned before you can't install a Sense based ROM on GPE firmware.
If you really want to install a Sense based ROM, you need to convert your device from GPE back to Sense.
This means you need to flash Sense firmware using fastboot, format data to get back the correct Sense partition then only you can install Sense ROM.
Thanks! I got it working
Related
I have no idea what to do here.
I had an RUU converted GPE device and I need to convert to 100% stock. I used RUU to flash the stock bootloader and change CID to 11111111.
I also reverted to S-ON.
I didn't install a Sense rom and now I'm stuck with GPE that is stuck in Safe Mode. All I have is Fastboot since the recovery is back to stock as well.
So what I have is:
Stock bootloader
S-ON
Stock recovery
GPE rom still installed
Formatted internal SD
I am completely stumped on what to do. Is my device bricked? I have to return it to HTC soon and all I have is Fastboot. I was wondering if I could flash the stock ATT img files using Fastboot, but all I have found are .zips and Nandroid backups.
Rikusaki said:
I have no idea what to do here.
I had an RUU converted GPE device and I need to convert to 100% stock. I used RUU to flash the stock bootloader and change CID to 11111111.
I also reverted to S-ON.
I didn't install a Sense rom and now I'm stuck with GPE that is stuck in Safe Mode. All I have is Fastboot since the recovery is back to stock as well.
So what I have is:
Stock bootloader
S-ON
Stock recovery
GPE rom still installed
Formatted internal SD
I am completely stumped on what to do. Is my device bricked? I have to return it to HTC soon and all I have is Fastboot. I was wondering if I could flash the stock ATT img files using Fastboot, but all I have found are .zips and Nandroid backups.
Click to expand...
Click to collapse
There is a post in the general forum about returning to sense after applying a GPE RUU. Follow it to the letter and it will get you back to sense, worked for me. Saying that my device was working fine so no idea if the post will be any help but I'm sure someone will be able to help if the post doesn't work.
oaklandm said:
There is a post in the general forum about returning to sense after applying a GPE RUU. Follow it to the letter and it will get you back to sense, worked for me. Saying that my device was working fine so no idea if the post will be any help but I'm sure someone will be able to help if the post doesn't work.
Click to expand...
Click to collapse
Thanks. I eventually figured it out. I flashed the stock recovery using Fastboot, booted into recovery, and did a full wipe. Then I flashed TWRP via Fastboot and did an advanced wipe including /system, but not internal SD. I then went back into Fastboot, flashed the boot.img from the AT&T rom (because I had S-ON), then I went back into TWRP and flashed the rom. Booted fine and now I have sense!
I wrote this out in detail in case anyone else ran into the same problem.
I just installed android revolution hd 4.4.4 20.3 ROM on my HTC One M8 over the previous version but when i reboot system, it goes back into the bootloader rather than start. Any help???
shaneadkins72 said:
I just installed android revolution hd 4.4.4 20.3 ROM on my HTC One M8 over the previous version but when i reboot system, it goes back into the bootloader rather than start. Any help???
Click to expand...
Click to collapse
Is your device GPE-based or Sense-based? It may not seem it, but the 2 are actually different enough that if your device is setup for one, it cannot boot the other (i.e. you cannot install a GPE-based ROM on a Sense-based phone without converting it). IIRC btw AR is Sense-based.
shaneadkins72 said:
I just installed android revolution hd 4.4.4 20.3 ROM on my HTC One M8 over the previous version but when i reboot system, it goes back into the bootloader rather than start. Any help???
Click to expand...
Click to collapse
Did you update firmware also? FIRMWARE 3.28.401.6 is obligatory before installing any 4.4.4 Sense-based ROM.
Same error here. I try various different roms (4.4.4 Sense based) and they all work just ARHD didn't work. I dont know what cause this error but you can try the other roms.
My firmware is 2.22.401.5
And here is the problem. Enter bootloader mode and upgrade your firmware.
Here are the instructions: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
or here http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
Same error
Try to restore stock recovery firmware bos
I originally had a stock sense M8 (bought it first day) but since October, I changed my phone to GPE (GPE Firmware and everything) and have been using 5.0 eversince using SkyDragon rom. Ran into issues a few weeks ago, and i've been waiting hard to go back to sense and use the newer 5.0 sense version.
However, today I ran into multiple issues, I thought installing the latest Sense Lollipop firmware and installing the latest ARHD 5.0 rom would do the trick, sadly that did not work.
I flashed the latest sense firmware and the ROM only for it to boot saying my Data is corrupt and i have to reset my phone, i say okay(was going to do that anyway) but then I access my recovery (TWRP) and my Internal storage/Cache/Data will not mount. I tried going back to GPE (atleast so my phone would work) but I cant do that either because even with the GPE firmware, the data partition wont mount and my internal storage shows 0 MB in TWRP, now im just stick in a bootloop/bricked device for hours. Any help would really be appreciated...thanks a lot.
Dev Edition RUU is what I would recommend. Partitioning is different on GPE versus Sense. So I'm guessing running the firmware only, since its not a complete image, did not change the partitioning back to the Sense partition scheme.
Converting from GPE back to Sense is not trivial, and not to be taken lightly. It seems like you tried to make up your own process instead of following any definitive guide or advice, which I do not recommend.
redpoint73 said:
Dev Edition RUU is what I would recommend. Partitioning is different on GPE versus Sense. So I'm guessing running the firmware only, since its not a complete image, did not change the partitioning back to the Sense partition scheme.
Converting from GPE back to Sense is not trivial, and not to be taken lightly. It seems like you tried to make up your own process instead of following any definitive guide or advice, which I do not recommend.
Click to expand...
Click to collapse
Thanks for your reply, to get this clear:
I should flash the Dev Edition RUU from (http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777) (3.28.1540.5) and then update the firmware to 4.16.1540.8 by just flashing that separate zip. However, if I flash the RUU wouldn't it relock my bootloader and put me on S-On and lose root and the custom recovery(Im terribly sorry if this sounds dumb, but my phone is soft bricked and I really need to get everything right this time), Is that the case if I flash the dev edition RUU? Thanks again.
Austin3161337 said:
However, if I flash the RUU wouldn't it relock my bootloader and put me on S-On and lose root and the custom recovery
Click to expand...
Click to collapse
No, RUU will not relock the bootloader. The only way the bootloader gets locked/unlocked is if you do so yourself.
Same with s-off, there is nothing that can change that aside from you making it s-on yourself.
Yes, you will lose custom recovery, as RUU will install stock recovery. So just flash stock recovery by fastboot after RUU. Then flash the ROM you want, which should already be rooted (so losing root is a moot point).
Official firmware.zip will also write stock recovery. So doing so would have caused the loss of TWRP anyway (unless it was a user modified firmware zip).
redpoint73 said:
No, RUU will not relock the bootloader. The only way the bootloader gets locked/unlocked is if you do so yourself.
Same with s-off, there is nothing that can change that aside from you making it s-on yourself.
Yes, you will lose custom recovery, as RUU will install stock recovery. So just flash stock recovery by fastboot after RUU. Then flash the ROM you want, which should already be rooted (so losing root is a moot point).
Official firmware.zip will also write stock recovery. So doing so would have caused the loss of TWRP anyway (unless it was a user modified firmware zip).
Click to expand...
Click to collapse
So I downloaded the RUU from (http://www.htc.com/us/support/htc-one-m8/news/) but its an .exe which requires me to plug my phone in which my computer cannot recognize because the phone won't boot at all, is there anyway I can install the RUU by not really needing to connect the phone to the computer? (Put the file in the external SD and install it via the bootloader maybe?) Any tips on that? Thanks
Austin3161337 said:
So I downloaded the RUU from (http://www.htc.com/us/support/htc-one-m8/news/) but its an .exe which requires me to plug my phone in which my computer cannot recognize because the phone won't boot at all
Click to expand...
Click to collapse
The phone doesn't need to boot into OS to run the RUU. It just needs to be able to get into bootloader/fastboot mode, which it can if the screen comes on.
If the device doesn't show on your PC, its a different issue. USB connectivity issue is almost always a driver issue. Install HTC Sync and HTC drivers, if you haven't already. Or uninstall and install them again.
I have a similiar issue. I had a tombile ruu.zip that a flashed as a 0P6Bimg.zip a kitkiat sense version for tmobile. Everything is cool and it runs fine. When I change cid and mid then flashed the sense lollipop firmware I lost my internal memory and twrp read storage as 0mb.
So idk
I flashed the Dev RUU as recommended by redpoint73, booted up and now it says that its updating to the latest firmware android 5.0 (OTA Update) However, I am going to install a custom recovery (TWRP) and put on ARHD instead, thanks for the help, and pretty much unbricking my device, lol.
Austin3161337 said:
I flashed the Dev RUU as recommended by redpoint73, booted up and now it says that its updating to the latest firmware android 5.0 (OTA Update) However, I am going to install a custom recovery (TWRP) and put on ARHD instead, thanks for the help, and pretty much unbricking my device, lol.
Click to expand...
Click to collapse
You're very welcome. Happy to help.
Did you have to do anything to get the RUU to run (like install drivers), or did you just end up running the RUU exe, and it worked?
redpoint73 said:
You're very welcome. Happy to help.
Did you have to do anything to get the RUU to run (like install drivers), or did you just end up running the RUU exe, and it worked?
Click to expand...
Click to collapse
I already had HTC Sync installed, had to boot into Fastboot USB for the thing to get recognized.
Every time i reboot phone i get stuck in bootloop , i have to wipe cache and dalvik cache to fix this . Fixed permissions in recovery, reflashed ROM , the problem still persists. Changed ROM . the problem is still there. I was using the same ROM before , didn't have this problem before , appeared out of nowhere.
Using Insertcoin ROM currently , ElementalX kernel.
Please help.
Anyone?
Did you attempt a factory reset while running a non-stock recovery?
If so, you need to put the stock recovery back on, let it complete the reset, then put your desired recovery back. This is true even if you are using a non-stock ROM.
jshamlet said:
Did you attempt a factory reset while running a non-stock recovery?
If so, you need to put the stock recovery back on, let it complete the reset, then put your desired recovery back. This is true even if you are using a non-stock ROM.
Click to expand...
Click to collapse
No i didn't attempt factory reset from within the ROM when using non-stock recovery.
But i will flash stock recovery back to check on this issue , Thanks.
It seems your boot files are crashed, try to flash boot.img
Sent from my HTC One using Tapatalk
Not nearly enough info:
1) What hboot, radio number?
2) What OS number (on bootloader screen) or main version (on getvar all)
3) What version InsertCoin you trying to flash? What other ROMs and version?
4) What version TWRP?
redpoint73 said:
Not nearly enough info:
1) What hboot, radio number?
2) What OS number (on bootloader screen) or main version (on getvar all)
3) What version InsertCoin you trying to flash? What other ROMs and version?
4) What version TWRP?
Click to expand...
Click to collapse
Insertion 7.1.8 (ON 5.0.2 LOLLIPOP)
Build number - 4.16.401.10 CL448934
M8_UL PVT SHIP S-ON
HBOOT - 3.19.0.0000
RADIO - 1.22.213311491.08G
OPENDSP - V46.2.2-00564-M8974-FO.0811
OS - 3.32.531.2
TWRP VERSION - 2.8.7.0
i guess there is a firmware mismatch.
This is originally a t-mobile version of M8 but it is sim-unlocked and i flash international version of any rom i flash. I also have no GPS Lock problem (might get fixed because of firmware? Tried everything FasterGPS, GPS status and Toolbox, no fix)
Being S-ON, i want to upgrade the firmware. How can i do that?
Can you explain to me in steps.
I've searched and have gotten really confused in these things like -
What RUU should i download (t-mobile or international?) and in what order should i do steps like relocking bootloader and stock recovery.
Need the solution in proper steps.
Thank you.
rahulsethi said:
i guess there is a firmware mismatch.
Click to expand...
Click to collapse
Firmware mismatch is your problem, as indicated by your radio number and OS number (on bootloader screen) which both correspond to Kitkat (Android 4.4.4).
rahulsethi said:
I also have no GPS Lock problem (might get fixed because of firmware?)
Click to expand...
Click to collapse
Most likely, yes.
rahulsethi said:
This is originally a t-mobile version of M8 but it is sim-unlocked and i flash international version of any rom i flash.
Being S-ON, i want to upgrade the firmware. How can i do that?
What RUU should i download (t-mobile or international?) and in what order should i do steps like relocking bootloader and stock recovery.
Click to expand...
Click to collapse
You need to use the T-Mobile US RUU (available here).
You can only run an RUU that matches your phone's carrier ID (CID) and model ID (MID), which in your case correspond to T-Mobile US. CID and MID can only be changed with s-off (have nothing to do with the ROM your flash).
What you want to do is:
1) Backup any personal data you want to keep (RUU will wipe the phone, including internal storage).
2) Relock the bootloader with command: fastboot oem lock
3) Connect phone to PC and run the RUU (its very self explanatory, just follow the prompts). Your firmware is not updated, and you are on the stock T-MOB Lollipop ROM, and stock recovery.
4) To get back to InsertCoin, unlock the bootloader again using the HTCDev.com website.
5) Flash current version TWRP in fastboot.
6) Flash InsertCoin.
I have an AT&T HTC One M8. It was already rooted when it bought it. Running stock 4.4.2
I have installed the most current version of TWRP. I created a successful backup.
I am trying to install the ROM for skydragon 5.5 but it just gets stuck on the startup screen (white android screen)
I am S-on.
I flashed (via fastboot) the boot.img from the Skydragon 5.5 Rom.
I installed Skydragon 5.5 Rom from the TWRP install screen.
(note - these are the instructions from skydragon website and it states I do not need S-off as long as I flash the boot image)
When I reboot it just hangs on the startup screen (white android screen)
I can recover to get back to a working phone but I would really like to upgrade to skydragon. I have been having constant problems with bluetooth headsets on the stock 4.4.2 and am hoping the newer skydragon ROM and boot.img would resolve the poor bluetooth sound quality issues.
Any help would be appreciated.
Thanks
You probably need to update your firmware/hboot.
gmgough said:
I have an AT&T HTC One M8. It was already rooted when it bought it. Running stock 4.4.2
I have installed the most current version of TWRP.
Click to expand...
Click to collapse
As mentioned, you need to update your firmware.
Current ROMs won't run properly (extreme long boot times, broken WiFi) on old firmware (hboot, radio, etc.).
Plus, the current TWRP will not flash ROMs properly on the old hboot.
I dont fully understand why but I lost my backup during my installation of the new skydragon ROM. The backups were on the SD card.......and then they vanished.
I did manage to barely avoid bricking my phone. I re-locked my phone, installed the HTC RUU for lollipop and got my phone back to working. I had been trying to use sunshine S-off tool so that I could upgrade the firmware but I couldnt get my phone to boot up to perform the S-off installation process.
I still want to install skydragon. These are the steps I think I need to take.
1. unlock/root my HTC M8
2. Install TWRP
3. Backup my phone
4. install the new Skydragon Lollipop ROM
* note - I assume that I dont need S-OFF since my firmware should have already been upgraded when I installed the HTC Lollipop RUU.
If my phone is S-off will the skydragon lollipop ROM installation automatically install the firmware? Or is that a separate installation?
1: You lost all because you ran a RUU !
2: A custom rom NEVER changes the firmware
gmgough said:
* note - I assume that I dont need S-OFF since my firmware should have already been upgraded when I installed the HTC Lollipop RUU.
Click to expand...
Click to collapse
To confirm whether the firmware was updated or not; what does it say on the hboot screen for hboot number, radio baseband, and OS number?
gmgough said:
If my phone is S-off will the skydragon lollipop ROM installation automatically install the firmware? Or is that a separate installation?
Click to expand...
Click to collapse
Flashing a ROM never updates your firmware. The firmware partitions (hboot, radio, WiFi, Bluetooth, etc.) are not included in a ROM zip.
Firmware flash is done as a separate action, usually via fastboot.
Actually I lost my backup before I installed the RUU......otherwise I would have reverted to my previous kitkat installation rather than installing the RUU and losing all my data. I know the RUU basically reimages all the memory.
I was using sideload to install the skydragon ROM. I suspect I did something wrong during one my fastboot flash commands or the adb sideload commands.