I have a CM ROM with Android 4.2.2 running now.
Whenever I try a 4.3 or 4.4 ROM in TWR or CWR I get a failed error during flashing.
If I fastboot flash one of the newer recoveries like the ones listed in the 4.4 rom threads, the phone will just go black when it tries to enter recovery mode and I have to flash back one of the regular recoveries to get back into the phone.
I am pretty sure that the phone is failing flashing the newer mods because the two recoveries I am trying to use can't handle them, but why wont the newer recoveries work when I fastboot flash them, flashboot reads successful.
Any help would be greatly appreciated.
Thanks!
What is the filename of the new recovery you're trying to flash? And what is the command you're using?
Sent from my Evita
timmaaa said:
What is the filename of the new recovery you're trying to flash? And what is the command you're using?
Sent from my Evita
Click to expand...
Click to collapse
recovery.img which is got from the CM 11 thread (http://forum.xda-developers.com/showthread.php?t=2541998)
fastboot flash recovery recovery.img
add this command after flashing the recovery...
fastboot erase cache
bzhmobile said:
add this command after flashing the recovery...
fastboot erase cache
Click to expand...
Click to collapse
Just tried it. Still just goes to a black screen when I try to enter recovery, and then it reboots again into CyanogenMod
Could it be because I am s-on?
Better to be S-off (not mandatory I think), What is your hboot?
Try with latest TWRP or Philz touch recovery to see if it the same
Okay I got S-Off but it still won't boot to any recoveries newer than TWRP 2.6.3.0 or CWMR 6.0.3.1
It's hard to tell what's gone wrong but now that you're s-off you should try running an RUU so you can start with a clean slate.
Sent from my Evita
timmaaa said:
It's hard to tell what's gone wrong but now that you're s-off you should try running an RUU so you can start with a clean slate.
Sent from my Evita
Click to expand...
Click to collapse
Just ran 3.18 RUU and it was successful. Can you link me to the recovery that you're using?
The SCID + S-OFF + RUU 3.18 seemed to have done the trick!
Thanks for all the help!
Good news, no problems. When someone on XDA helps you please press the thanks button on the posts that were helpful as well as saying thanks.
Sent from my Evita
timmaaa said:
Good news, no problems. When someone on XDA helps you please press the thanks button on the posts that were helpful as well as saying thanks.
Sent from my Evita
Click to expand...
Click to collapse
Done and Done!
Now, I have the more difficult task of picking the best KitKat Rom
veritas2884 said:
Just ran 3.18 RUU and it was successful. Can you link me to the recovery that you're using?
Click to expand...
Click to collapse
If you are looking to flash a 4.3 or lower Rom TWRP 2.6.3.0 will be fine.
If you want to go to 4.4 you can try this custom TWRP:
http://forum.xda-developers.com/showthread.php?t=2558503
@jrior001 just posted this today.
Madcat8686 said:
If you are looking to flash a 4.3 or lower Rom TWRP 2.6.3.0 will be fine.
If you want to go to 4.4 you can try this custom TWRP:
http://forum.xda-developers.com/showthread.php?t=2558503
@jrior001 just posted this today.
Click to expand...
Click to collapse
I will give it a whirl. Thanks! Any suggestion on which 4.4 is most stable? I tried the beanstalk 4.4 build but after about five mins of using it, it devolved into boot loops. I also tried the official CM 11 nightly but it wouldn't even post. Maybe it will work better with the new twrp.
Sorry, but asking which ROM/kernel is best/most stable isn't allowed here. This is because to say one is better/faster/more stable is to infer that the other ROMs are inferior in some way. This isn't fair to the devs who spend countless hours of their spare time providing us with these awesome ROMs free of charge. It's simply a matter of flashing and testing for yourself, it only takes a few minutes to flash a ROM. Reading the last few pages in a ROM thread goes a long way too, you'll find out pretty fast how the ROM is performing.
Sent from my Evita
Related
Hi guys
I hope this is the right forum here, but I have still the same problem after asking google for hours.
I unlocked my one s via htcdev and the I want to install trickdroid but after flashing the boot.img nothing works any longer.
At the moment I get team win recovery running and I try to install cyanogen but it doesn't load. There is only the boot animation.
Hopefully you can help me to get anything running on my one s.
swtcw
PS: I'am really new to android!
swtcw said:
Hi guys
I hope this is the right forum here, but I have still the same problem after asking google for hours.
I unlocked my one s via htcdev and the I want to install trickdroid but after flashing the boot.img nothing works any longer.
At the moment I get team win recovery running and I try to install cyanogen but it doesn't load. There is only the boot animation.
Hopefully you can help me to get anything running on my one s.
swtcw
PS: I'am really new to android!
Click to expand...
Click to collapse
So as i understand it you can get into recovery ? how did you flash the boot.img?
Did u clear cache and factory reset?
swtcw said:
Hi guys
I hope this is the right forum here, but I have still the same problem after asking google for hours.
I unlocked my one s via htcdev and the I want to install trickdroid but after flashing the boot.img nothing works any longer.
At the moment I get team win recovery running and I try to install cyanogen but it doesn't load. There is only the boot animation.
Hopefully you can help me to get anything running on my one s.
swtcw
PS: I'am really new to android!
Click to expand...
Click to collapse
What hboot/exact steps for flashing? S3 or S4 processor?
Whats the exact rom and version you're trying to flash?
Sent from my HTC One S using xda premium
Check the HBOOT version that you are using with that required. That is the biggest problem when it comes to bootloops in this phone.
Basic question - are you flashing the correct boot.img for the ROM you want.
ie for Cyanogenmod you need to flash the exact boot.img from that ROM.
Thanks for your answer.
At the moment I am running clockwork as recovery. I've tried to flash trickdroid and I used these instructions at
trickdroid.org for the international one s. But after flashing the boot.img and doing fastboot erase cache
nothing happens and I couldn't load anything anymore.
PS: My phone has a S4 processor (with 1,5GHz is this right?)
swtcw said:
Thanks for your answer.
At the moment I am running clockwork as recovery. I've tried to flash trickdroid and I used these instructions at
trickdroid.org for the international one s. But after flashing the boot.img and doing fastboot erase cache
nothing happens and I couldn't load anything anymore.
PS: My phone has a S4 processor (with 1,5GHz is this right?)
Click to expand...
Click to collapse
Yep, S4 is 1.5GHz
Sent from my HTC One S using Tapatalk 2
Can I reflash my originial stock rom? I have no backup.
I found an instruction at usp-forum.de/htc-one-s-root-flash-hack/87944-how-to-htc-one-s-stock-rom-wiederherstellen.html - it worked fine,
I flashed the stock_recovery.img with "fastboot flash recovery stock_recovery.img" and the I did "fastboot oem lock".
I also downloaded a installer exe with the RUU - it found my device and started to install, but it stopped sometimes and said, that
I have a wrong installer or RUU (something like signature error 132). Where and how can I find the right RUU?
Hiya. Any help appreciated here, Got hold of a Rogers One X (evita)
Heres where I am at right now:
I unlocked the bootloader and attempted to flash CM11 (Got an error regarding update package) *I made no backup- Noob, I know.*
Now, at the very most all I can get into is CWM/TWRP (I can flash both of these without issue using fastboot)
I have attempted to re-lock the bootloader (which says relocked) but I have tried the 2 rogers RUU files I managed to find and both fail with an error 115 and leave me on the htc logo, and boot to bootloader only.
I tried to flash some custom roms, some seem to flash ok but just boot-loop.
I am not SuperCID, and the phone is S-ON.
Hboot-2.14.0000
Radio-0.23a.32.09.29
Nov 26, 2012
I cannot figure what to do next. I dont care what goes on the phone as long as i can get it working. Its been a long time since I messed with android, I only bought this phone for this reason lol, but I made the mistake of staying up too late and probably skipping half of the tutorials i was following.
Any help appreciated.
:laugh:
What version of TWRP are you using? Why did you relock the bootloader? You should unlock that again. Did you flash the boot.img from the ROM zip via fastboot after flashing the ROM in TWRP? You need to do this because you're s-on. You should read the Evita FAQ thread in my signature, as well as the How-To Guide For Beginners thread.
Sent from my Evita
timmaaa said:
What version of TWRP are you using? Why did you relock the bootloader? You should unlock that again. Did you flash the boot.img from the ROM zip via fastboot after flashing the ROM in TWRP? You need to do this because you're s-on. You should read the Evita FAQ thread in my signature, as well as the How-To Guide For Beginners thread.
Sent from my Evita
Click to expand...
Click to collapse
Wow, timmaaa, thanks for the superfast answer chap!
So, unlock the bootloader, flash the Rom (CM11), then the Boot.img extracted from the rom via fastboot?
Sounds like a plan. I will try that now. I think to be honest, I came home last night and ended up following a bit of one tut, a bit of another, and never really read properly. Call it friday evening alcohol induced noobness syndrome.
That should be it. You need to make sure you use the correct version of TWRP though, you're looking for the unofficial modified TWRP 2.6.3.0 by jrior001 in our Original Android Development section.
Sent from my Evita
timmaaa said:
That should be it. You need to make sure you use the correct version of TWRP though, you're looking for the unofficial modified TWRP 2.6.3.0 by jrior001 in our Original Android Development section.
Sent from my Evita
Click to expand...
Click to collapse
Thank you. The boot.img thing got me a bit further so far. I will get that version of TWRP installed and try the CM11 again, as i think thats where I want to be at. It should be as simple as CM11 flash, Boot.img flash, then Gapps and im done, right?
Perform a full wipe (cache/dalvik cache/factory reset/system), flash CM, flash gapps, flash boot.img, reboot into ROM.
Sent from my Evita
timmaaa said:
That should be it. You need to make sure you use the correct version of TWRP though, you're looking for the unofficial modified TWRP 2.6.3.0 by jrior001 in our Original Android Development section.
Sent from my Evita
Click to expand...
Click to collapse
Ok one last question Timmaaa, I have installed that TWRP, flashed CM11, also Gapps and the boot.img , and now I just get the rom bootlogo (spinning cyanogen etc) and nothing, it just sits there. Is there anything else that may need to be done? If theres not anything obvious, ill go read some more!
Thanks for the help so far!
scibot said:
Ok one last question Timmaaa, I have installed that TWRP, flashed CM11, also Gapps and the boot.img , and now I just get the rom bootlogo (spinning cyanogen etc) and nothing, it just sits there. Is there anything else that may need to be done? If theres not anything obvious, ill go read some more!
Thanks for the help so far!
Click to expand...
Click to collapse
What is the filename of the ROM zip you flashed? Did you check the md5 of the file after you downloaded it? Are you sure the flashing of the boot.img was successful?
Timmaaa, it seems it just took ages. I went downstairs for some juice, came back up and there it was, the setup screen! Beautiful.
Thanks for the help, it seems its not the technical i need to brush up on, but my paying attention and reading - lol!
Thanks again man! :good:
I have an AT&T HTC One x. Its ***Tampered*** ***Unlocked*** HBOOT 1 .09. 0000 S-ON
I had been running an older version of TWRP, and decided I was going to clear my phone and do a fresh start. I know, I know, I should have made a backup, but I felt pretty confident in what I was doing, and was in too much of a hurry to rationalize this.
I wiped both the OS and previous version of TWRP in order to update to the new ones. While in fastboot I flashed CLEANrom and the new version of TWRP, and my administrative command prompt confirmed that they were installed successfully. Even cleared the cache afterwards. Now is the difficult part. I've researched, and researched, and cannot find a solution for this problem. I keep having a Boot Loop.... I'm stumped guys... I need some sort of help, be it technical, or something to drink lol
Previous ROM was CM 10, with TWRP and PA GAPPS :good:
Check the Evita FAQ thread in my signature, your answer probably lies within.
Sent from my Evita
timmaaa said:
Check the Evita FAQ thread in my signature, your answer probably lies within.
Sent from my Evita
Click to expand...
Click to collapse
I don't see anything in your FAQ that I haven't already tried unfortunately.....
Exactly which version of TWRP is currently installed? Did you flash the boot.img via fastboot?
Sent from my Evita
timmaaa said:
Exactly which version of TWRP is currently installed? Did you flash the boot.img via fastboot?
Sent from my Evita
Click to expand...
Click to collapse
It's the newest version of TWRP that is out, and yes, I flashed it via Fastboot, and it says successful on both the recovery install and ROM install.
Have you tried flashing another ROM? I asked for the exact recovery version for a reason, please provide that information.
Sent from my Evita
---------- Post added at 03:48 PM ---------- Previous post was at 03:43 PM ----------
Also it isn't completely clear to me that you're flashing the boot.img from the ROM zip via fastboot after flashing the ROM in TWRP. Are you extracting the boot.img from the ROM zip and doing that or not?
Sent from my Evita
1332858898
timmaaa said:
Have you tried flashing another ROM? I asked for the exact recovery version for a reason, please provide that information.
Sent from my Evita
Click to expand...
Click to collapse
TWRP 2.7. And yes, I have flashed about 4 Roms all succeeded according to fastboot and still getting the boot sequence.:good:
Yes I have extracted the boot.img
timmaaa said:
Have you tried flashing another ROM? I asked for the exact recovery version for a reason, please provide that information.
Sent from my Evita
---------- Post added at 03:48 PM ---------- Previous post was at 03:43 PM ----------
Also it isn't completely clear to me that you're flashing the boot.img from the ROM zip via fastboot after flashing the ROM in TWRP. Are you extracting the boot.img from the ROM zip and doing that or not?
Sent from my Evita
Click to expand...
Click to collapse
yes the boot.img file was extracted. I get a confirmation that it was successful when I flash it on fastboot
Exactly which ROMs have you tried to flash?
Sent from my Evita
timmaaa said:
Exactly which ROMs have you tried to flash?
Sent from my Evita
Click to expand...
Click to collapse
CM 10.2, CM 11, CLEANrom 7.0. all via fastboot with confirmations.
outcold32 said:
CM 10.2, CM 11, CLEANrom 7.0. all via fastboot with confirmations.
Click to expand...
Click to collapse
Why are you flashing roms via fastboot? -_- You're making your life difficult. Wipe everything in TWRP then flash in TWRP. ALso, you should really s-off and update your firmware/hboot. via RUU. You will likely encounter issues running a newer software on an such an old firmware.
exad said:
Why are you flashing roms via fastboot? -_- You're making your life difficult. Wipe everything in TWRP then flash in TWRP. ALso, you should really s-off and update your firmware/hboot. via RUU. You will likely encounter issues running a newer software on an such an old firmware.
Click to expand...
Click to collapse
If you would have read the thread, you would have noticed, that I am in bootloop, therefor I cannot access the recovery. And I have to have access to the ROM on my phone in order to flash anything via TWRP so this is moot. My question isn't how to flash roms, it's why am I getting a loop when I am successful on a clean partition and clean flash of both the recovery and ROM? And to me, fastboot is way easier than TWRP. I guess I could get a UART and try to debug the sequence myself, but I have more important things to do than that. I was posting to see if anyone had any similar problems. And this phone is an original model and I haven't really bothered with the security off, since I only wanted to get rid of sense in the first place. It was unlocked well before any commercial unlocker was available for the evita(Literally no stable CM10 at all at the time), so it's a little finicky in the first place. I ran the RUU after I re-locked the bootloader, and I'm at least out of the loop. I'm just going get to a more stable version so that this process will be more streamline when I re do my unlock and stuff.
So I guess the only solution at this point I have for any problem like this is to use the proper RUU. I tried a couple of times with no success, and it seemed the charm was to re lock the bootloader ( Fastboot oem lock) in order to properly and successfully get the RUU to work.:good:
Wth are you even on about? Of course you can access recovery in a bootloop. How are you getting to fastboot without accessing the bootloader? from the bootloader you can access recovery. If recovery isn't loading SCREW flashing a rom, reflash your recovery, 2.7 TWRP preferably. and then boot to recovery, mount your USB, copy the rom and flash it. Recovery is more important than having a ROM.
I know what I am talking about, do you know what you're talking about?
FFS I am trying to help you, there's no reason for you to be an ass. You're having issues BECAUSE you're flashing your rom via fastboot. You cannot flash a rom via fastboot.
exad said:
Wth are you even on about? Of course you can access recovery in a bootloop. How are you getting to fastboot without accessing the bootloader? from the bootloader you can access recovery. If recovery isn't loading SCREW flashing a rom, reflash your recovery, 2.7 TWRP preferably. and then boot to recovery, mount your USB, copy the rom and flash it. Recovery is more important than having a ROM.
I know what I am talking about, do you know what you're talking about?
FFS I am trying to help you, there's no reason for you to be an ass. You're having issues BECAUSE you're flashing your rom via fastboot. You cannot flash a rom via fastboot.
Click to expand...
Click to collapse
You didn't read the thread. I'm not being an ass. The information is already there.I can not access the recovery at all. That's why I am in in this situation. And again, if you had read the whole thread, or the even the original post, you would know that I cannot access the recovery. The only reason I'm being as detailed as I am is so I don't have to repeat myself, as well as for other people who may encounter this problem. And Yes I know what I am talking about. If I didn't I probably wouldn't have gotten to this point, right?
Okie dokie. No point in arguing. You're right. I'm wrong. Glad it's all working now.
Sent from my One XL using xda app-developers app
outcold32 said:
You didn't read the thread. I'm not being an ass. The information is already there.I can not access the recovery at all. That's why I am in in this situation. And again, if you had read the whole thread, or the even the original post, you would know that I cannot access the recovery. The only reason I'm being as detailed as I am is so I don't have to repeat myself, as well as for other people who may encounter this problem. And Yes I know what I am talking about. If I didn't I probably wouldn't have gotten to this point, right?
Click to expand...
Click to collapse
Exad is right in saying that the reason you're having problems is because you're attempting to flash ROMs with fastboot. That isn't how it's done. The correct way is to flash your ROM with recovery. You're barking up the wrong tree, not only that but you're arguing with experienced people who are only attempting to help get you out of the mess that you've gotten yourself into. You came here for advice, but there's no point in asking for advice if you're just going to argue and dismiss what you're being told to do.
You said you can't access your ROM so you can't flash anything, that makes absolutely no sense, which leads me to believe you don't really know what you're doing. Get out of the mindset that you need to use fastboot, it's wrong. You're dealing with people who have extensive and intimate knowledge of this device, trust us, we know what we're talking about.
Exactly why can't you access recovery? If you can issue fastboot commands that means you can access your bootloader, if you can access your bootloader that means you can use your volume keys to scroll through the options and the power button to select recovery. What happens when you do that? Exactly which recovery have you flashed to your device? I need to the full filename of the recovery that you've flashed.
Sent from my Evita
outcold32 said:
And this phone is an original model and I haven't really bothered with the security off, since I only wanted to get rid of sense in the first place. It was unlocked well before any commercial unlocker was available for the evita(Literally no stable CM10 at all at the time), so it's a little finicky in the first place.
Click to expand...
Click to collapse
S-on is a downright dangerous place to be, if the phone is also SuperCID (which is very likely, since its the AT&T variant). exad is right in recommending s-ff, as he is about a good many things.
Hey guys,
today I got my HTC One S s4. I directly opened the bootloader, installed twrp2.5.0.0 and flashed vanir rom. Afterwards I stuck in a bootloop. Went back into recovery and flashed TwistedKat, next bootloop. Flashed twrp2.6.3.0 from the cm11.2 thread. Reboot into recovery and installed the cm11 rom another time bootloop. So i flashed ClockworkMod 6.0.4.5 and flashed cm11 another time and bootloop. Now I don't really don't know what to do and what the problem is.
Hope you guys can help me out
cheers,
finn
Finnit0 said:
Hey guys,
today I got my HTC One S s4. I directly opened the bootloader, installed twrp2.5.0.0 and flashed vanir rom. Afterwards I stuck in a bootloop. Went back into recovery and flashed TwistedKat, next bootloop. Flashed twrp2.6.3.0 from the cm11.2 thread. Reboot into recovery and installed the cm11 rom another time bootloop. So i flashed ClockworkMod 6.0.4.5 and flashed cm11 another time and bootloop. Now I don't really don't know what to do and what the problem is.
Hope you guys can help me out
cheers,
finn
Click to expand...
Click to collapse
Did you flash the kernel (boot.img) via fastboot immediately after flashing the rom?
As LS. xD already said: You have to flash the Kernel in fastboot.
Extract the boot.img from the cm zip and type in fastboot
flash boot boot.img
Gesendet von meinem HTC One S mit Tapatalk
LS.xD said:
Did you flash the kernel (boot.img) via fastboot immediately after flashing the rom?
Click to expand...
Click to collapse
?jonas! said:
As LS. xD already said: You have to flash the Kernel in fastboot.
Extract the boot.img from the cm zip and type in fastboot
flash boot boot.img
Click to expand...
Click to collapse
Actually thats it! Thanks a lot! Didn't read about it in any flashing instructions. And I don't really understand why it is necessary to flash the boot.img [Kernel] seperately?
cheers,
Finn
Finnit0 said:
Actually thats it! Thanks a lot! Didn't read about it in any flashing instructions. And I don't really understand why it is necessary to flash the boot.img [Kernel] seperately?
cheers,
Finn
Click to expand...
Click to collapse
Security flag (S-ON) blocks writing boot partition via Recovery. Unlocked bootloader allows writing boot partition via fastboot only. Have you tried getting S-OFF yet?
Sent from my beloved HTC One S using (most time buggy) Tapatalk
LS.xD said:
Security flag (S-ON) blocks writing boot partition via Recovery. Unlocked bootloader allows writing boot partition via fastboot only. Have you tried getting S-OFF yet?
Sent from my beloved HTC One S using (most time buggy) Tapatalk
Click to expand...
Click to collapse
So far I haven't, future plans because I would like to update to the 1.35a.32.45.27 radio from the One XL and sounds like it makes flashing quiet easier. But so far I don't see a way without windows pc? I am on mac .
cheers Finn
Finnit0 said:
So far I haven't, future plans because I would like to update to the 1.35a.32.45.27 radio from the One XL and sounds like it makes flashing quiet easier. But so far I don't see a way without windows pc? I am on mac .
cheers Finn
Click to expand...
Click to collapse
Working adb on your PC. Yes, that means OS X, linux, Windows, etc. are all supported. --> FIREWATER S-OFF
LS.xD said:
Working adb on your PC. Yes, that means OS X, linux, Windows, etc. are all supported. --> FIREWATER S-OFF
Click to expand...
Click to collapse
Thanks man, you have helped quiet a lot with the start of using my One S. One more question. Is it worth it to update to hboot 2.16.00?
cheers Finn
Finnit0 said:
Thanks man, you have helped quiet a lot with the start of using my One S. One more question. Is it worth it to update to hboot 2.16.00?
cheers Finn
Click to expand...
Click to collapse
Just some Sense based roms are running on HBoot 2.16. I prefer AOSP based roms e.g. PAC or TwistedKat Most roms are for HBoot 2.15
Sent from my beloved HTC One S using (most time buggy) Tapatalk
OK guys let me tell you about my issue's
I'm using TWRP 2.7.1.0 (Tried 2.7.0.2 no difference) S-off, Unlocked, latest firmware from Santods files. The phone works fine with Sense ROMS but for the life of me I can't flash a GPE ROM. They fail every time. Santod tried to help me out the best he could by having me replace the Boot.img from the ROM I was flashing thinking that I was on a secure Boot image (And I may be but I replaced it and they still won't flash). Mr. Jaydee82 also modified a ROM for me to try out (although I'm not sure exactly what he did to it) and it wouldn't Flash properly either. When I try to flash these ROMs it will appear to flash properly and then they will go to the bootscreen and just sit there and churn. Depending on the ROM some will time out and power down the device and some will just sit there forever until I do a virtual battery pull. I'm freaking desperate to find out what is going on with this device and I don't feel right bugging Santod so I decided to post this in hope of more ideas about what could possibly be going on with my device. Any and all help greatly appreciated!!!
Thanks!
Duckman_UF said:
OK guys let me tell you about my issue's
I'm using TWRP 2.7.1.0 (Tried 2.7.0.2 no difference) S-off, Unlocked, latest firmware from Santods files. The phone works fine with Sense ROMS but for the life of me I can't flash a GPE ROM. They fail every time. Santod tried to help me out the best he could by having me replace the Boot.img from the ROM I was flashing thinking that I was on a secure Boot image (And I may be but I replaced it and they still won't flash). Mr. Jaydee82 also modified a ROM for me to try out (although I'm not sure exactly what he did to it) and it wouldn't Flash properly either. When I try to flash these ROMs it will appear to flash properly and then they will go to the bootscreen and just sit there and churn. Depending on the ROM some will time out and power down the device and some will just sit there forever until I do a virtual battery pull. I'm freaking desperate to find out what is going on with this device and I don't feel right bugging Santod so I decided to post this in hope of more ideas about what could possibly be going on with my device. Any and all help greatly appreciated!!!
Thanks!
Click to expand...
Click to collapse
What did you use to s-off; firewater or sunshine? Are you able to flash/boot AOSP roms? Did you take the 1.55.605.2 OTA before?
krazie1 said:
What did you use to s-off; firewater or sunshine? Are you able to flash/boot AOSP roms? Did you take the 1.55.605.2 OTA before?
Click to expand...
Click to collapse
I used Firewater I'm able to Flash all of the Sense ROM's not sure if they are considered AOSP. Give me an example of one and I'll try it. I'm not 100% sure if I took the OTA update before I Rooted and S-offed/unlocked the device but I think I did. I Flashed Santods Nobootimg firmware via ADB to be sure I was on the latest firmware. I know my radios were up to date before doing this but I wasn't sure about the FW so I flashed it. Flashed fine, didn't need to flush again, flashed fine first time.
Duckman_UF said:
I used Firewater I'm able to Flash all of the Sense ROM's not sure if they are considered AOSP. Give me an example of one and I'll try it. I'm not 100% sure if I took the OTA update before I Rooted and S-offed/unlocked the device but I think I did. I Flashed Santods Nobootimg firmware via ADB to be sure I was on the latest firmware. I know my radios were up to date before doing this but I wasn't sure about the FW so I flashed it. Flashed fine, didn't need to flush again, flashed fine first time.
Click to expand...
Click to collapse
I'll post a link to a aosp ROM but first can you link me to the firmware file you flashed?
krazie1 said:
I'll post a link to a aosp ROM but first can you link me to the firmware file you flashed?
Click to expand...
Click to collapse
4th one down and this was per Santod's instuction so I'm sure it's good.
http://www.androidfilehost.com/?w=files&flid=13966
Duckman_UF said:
4th one down and this was per Santod's instuction so I'm sure it's good.
http://www.androidfilehost.com/?w=files&flid=13966
Click to expand...
Click to collapse
Alright so you flashed it in bootloader right like this video?
http://youtu.be/e21qb7iZAOo
Here is a aosp ROM cm11 download the 20140801 build wipe and flash.
https://download.cyanogenmod.org/?device=m8
krazie1 said:
Alright so you flashed it in bootloader right like this video?
http://youtu.be/e21qb7iZAOo
Here is a aosp ROM cm11 download the 20140801 build wipe and flash.
https://download.cyanogenmod.org/?device=m8
Click to expand...
Click to collapse
Yes, ADB Fastboot Hboot...exactly as video instructed. No problems at all.
I'll give it a shot!
krazie1 said:
Alright so you flashed it in bootloader right like this video?
http://youtu.be/e21qb7iZAOo
Here is a aosp ROM cm11 download the 20140801 build wipe and flash.
https://download.cyanogenmod.org/?device=m8
Click to expand...
Click to collapse
Is a Gapps package needed for this ROM. Ive used Cyanogen ROM's before just not on this Phone.
Duckman_UF said:
Yes, ADB Fastboot Hboot...exactly as video instructed. No problems at all.
I'll give it a shot!
Click to expand...
Click to collapse
Forgot to link the GAPPs you need these for all AOSP roms, download and flash right after CM11
https://goo.im/gapps/gapps-kk-20140606-signed.zip/
krazie1 said:
Forgot to link the GAPPs you need these for all AOSP roms, download and flash right after CM11
https://goo.im/gapps/gapps-kk-20140606-signed.zip/
Click to expand...
Click to collapse
Thats what I thought..Thanks! About to dl Gapps and give it a shot.
krazie1 said:
Forgot to link the GAPPs you need these for all AOSP roms, download and flash right after CM11
https://goo.im/gapps/gapps-kk-20140606-signed.zip/
Click to expand...
Click to collapse
Yep flashed fine...no problems.
Duckman_UF said:
Yep flashed fine...no problems.
Click to expand...
Click to collapse
OK then, did you try both GPE ROMs for the vzw variant? Download the newest version of sinlessrom and wipe advanced (cache, dalvik cache, data & system) in TWRP.
http://www.androidfilehost.com/?fid=23578570567721616
krazie1 said:
OK then, did you try both GPE ROMs for the vzw variant? Download the newest version of sinlessrom and wipe advanced (cache, dalvik cache, data & system) in TWRP.
http://www.androidfilehost.com/?fid=23578570567721616
Click to expand...
Click to collapse
Already tried...Various Roms, various versions, 2 versions of TWRP (As stated) Aroma, non Aroma...They all just sit there and churn away on the boot screen or power down the device. I always wipe in that fashion
Man I'm out of ideas, I really want to help but can't think of anything. I'll still look and see if I can find anything.
krazie1 said:
Man I'm out of ideas, I really want to help bit can't think of anything. I'll still look and see if I can find anything.
Click to expand...
Click to collapse
I really appreciate your help. Santod and me went back and forth via PM a few times and JayDee modified his Rom for me and now you. IDK....I'm dumbfounded. If you think of anything let me know. I'll just stay on AOSP for now. Always liked Cyanogen's stuff anyway, just never even thought about them since their ROMS are not in the forums. They used to be for my various other phones. Never really though about them not being on XDA until we did this just now. Thanks again for you time and help!!!
Duckman_UF said:
I really appreciate your help. Santod and me went back and forth via PM a few times and JayDee modified his Rom for me and now you. IDK....I'm dumbfounded. If you think of anything let me know. I'll just stay on AOSP for now. Always liked Cyanogen's stuff anyway, just never even thought about them since their ROMS are not in the forums. They used to be for my various other phones. Never really though about them not being on XDA until we did this just now. Thanks again for you time and help!!!
Click to expand...
Click to collapse
Yeah cm11 is what I'm currently using, it recently had a speakerphone issue but its been fixed since 7/30. The only AOSP ROMs that have incorporated the fix are cm11, liquidsmooth & aokp. Here is the section for all the aosp ROMs they are universal so means 1 zip for all HTC One M8 variants.
http://forum.xda-developers.com/htc-one-m8/orig-development
Have you tried a RUU?
young0ne said:
Have you tried a RUU?
Click to expand...
Click to collapse
What do you mean? I put the phone in RUU when when flashing the firmware with ADB??
Duckman_UF said:
What do you mean? I put the phone in RUU when when flashing the firmware with ADB??
Click to expand...
Click to collapse
it put stock back on the phone just like it was new out of box. it re installs everything from factory.
Thanks!
GNU con Linux