Before I get flamed, let me say that I have done ALOT of research on the questions I am about to ask, and the fact of the matter that there is a lot of conflicting information out there. So please bear with me.
I am on a rooted phone, Android 4.1.1, Sense 4+, 3.18.502.6 radio, kernal version 3.4.10
Rooted with S-on
So here's my questions:
1. Can I install a custom rom with S-on?
2. If the answer is yes, can someone give me the quick run-down, or at the very least point me in the direction of another thread that I can refer to?
3. I have read conflicting threads that claim that with S-on, I need to flash the boot.img first, other threads say just go ahead and flash the ROM
Some of these threads are 30+ pages long and go back to 2012. If you miss one post in the thread then you're screwed. Any help is appreciated. For the record these forums have been extremely helpful. Successfully rooted two phones in the past year. I understand the rooting very, flashing custom roms gives me the willies.
First thing, why not just s-off and solve your problems? It's super simple. http://forum.xda-developers.com/showthread.php?t=2155071
But the answer is... Sometimes. Sometimes you need to flash the boot.img. If you're unsure, just do it anyways. This can be done by
1. Extracting the boot.img from the ROM zip archive you wish to flash.
2. Placing it in your adb working directory.
3. Enter fastboot on your phone.
4. fastboot flash boot boot.img
Sent from my HTC One X using Tapatalk 4
RollTribe said:
First thing, why not just s-off and solve your problems? It's super simple. http://forum.xda-developers.com/showthread.php?t=2155071
But the answer is... Sometimes. Sometimes you need to flash the boot.img. If you're unsure, just do it anyways. This can be done by
1. Extracting the boot.img from the ROM zip archive you wish to flash.
2. Placing it in your adb working directory.
3. Enter fastboot on your phone.
4. fastboot flash boot boot.img
Sent from my HTC One X using Tapatalk 4
Click to expand...
Click to collapse
Thanks Man! I'll give the S-off a shot. I'll take your advice and just flasht he boot.img, just to be on the safe side
I am thinking about flashing the CleanRom, unless anyone has any other suggestions
Fivetenfrank said:
Thanks Man! I'll give the S-off a shot. I'll take your advice and just flasht he boot.img, just to be on the safe side
I am thinking about flashing the CleanRom, unless anyone has any other suggestions
Click to expand...
Click to collapse
If you're s-off there's no need to flash boot.img.
Sent from my HTC One X using Tapatalk 4
RollTribe said:
If you're s-off there's no need to flash boot.img.
Sent from my HTC One X using Tapatalk 4
Click to expand...
Click to collapse
Thanks. One last question. Ok maybe not the last one but one more question regardless.
With custom roms, does the rom need to be based on the same firmware that's on my stock phone? I other words, right now my phone has build 3.18.502.6. I found a rom that I really like that's based on 3.8.402.1. Is that custom rom compatible with my phone?
Fivetenfrank said:
3. I have read conflicting threads that claim that with S-on, I need to flash the boot.img first, other threads say just go ahead and flash the ROM
Click to expand...
Click to collapse
The short (and incomplete) answer is that "it depends".
If you are s-on and hboot 1.14 or higher, you need to flash boot.img separately using fastboot. A few ROMs (ViperXL, some versions of CleanROM) will flash boot.img in the AROMA installer. But most will not.
Failure to do so will mean the kernel for the custom ROM is not flashed, and you will likely bootloop or be stuck on the boot screen.
Another option, as already mentioned, is to get S-off. But be aware that S-off means that all security checks are bypassed. Meaning you can flash lots of things, with security checks bypassed. Sometimes this is good, sometimes it can be really bad.
---------- Post added at 09:35 AM ---------- Previous post was at 09:29 AM ----------
Fivetenfrank said:
With custom roms, does the rom need to be based on the same firmware that's on my stock phone?
Click to expand...
Click to collapse
Typically no.
There are some exceptions. For instance, if you did OTA or RUU to get on the 3.18 stock ROM, the touch panel firmware was upgraded, and AOSP ROMs will not work right (no touch functions). The solution is to have S-off and downgrade the touch panel firmware.
Fivetenfrank said:
right now my phone has build 3.18.502.6. I found a rom that I really like that's based on 3.8.402.1. Is that custom rom compatible with my phone?
Click to expand...
Click to collapse
Link the ROM, and I can probably answer that for you pretty easily.
Notills his
redpoint73 said:
The short (and incomplete) answer is that "it depends".
If you are s-on and hboot 1.14 or higher, you need to flash boot.img separately using fastboot. A few ROMs (ViperXL, some versions of CleanROM) will flash boot.img in the AROMA installer. But most will not.
Failure to do so will mean the kernel for the custom ROM is not flashed, and you will likely bootloop or be stuck on the boot screen.
Another option, as already mentioned, is to get S-off. But be aware that S-off means that all security checks are bypassed. Meaning you can flash lots of things, with security checks bypassed. Sometimes this is good, sometimes it can be really bad.
---------- Post added at 09:35 AM ---------- Previous post was at 09:29 AM ----------
Typically no.
There are some exceptions. For instance, if you did OTA or RUU to get on the 3.18 stock ROM, the touch panel firmware was upgraded, and AOSP ROMs will not work right (no touch functions). The solution is to have S-off and downgrade the touch panel firmware.
Link the ROM, and I can probably answer that for you pretty easily.
Click to expand...
Click to collapse
It won't link to the rom because XDA won't let me because I am a new user. It's Scott's CleanRom version 6.5. It says its built on the 3.17 OTA build
My phone is a week old. It stock with 4.1.1 and 3.18.502.6. No OTA updates happening here. So can I assume the touchpanel firmware will NOT be an issue since 3.18 is stock?
And I'm not going to mess with S-off. Ill stick with S-on for now.
You should be fine to flash it. Like redpoint said, you may have to flash the boot.img. I can't remember whether CR6.5 flashes the boot.img for you or not. To be on the safe side, go ahead and flash it.
Fivetenfrank said:
It won't link to the rom because XDA won't let me because I am a new user. It's Scott's CleanRom version 6.5. It says its built on the 3.17 OTA build
Click to expand...
Click to collapse
Fair enough. CR6.5 will work great. One thing to note however, recent versions of TWRP (2.4 and 2.5) are known to be problematic and will not work with CR6.5. Either use an older TWRP (2.3) or use the official CWM.
Fivetenfrank said:
My phone is a week old. It stock with 4.1.1 and 3.18.502.6. No OTA updates happening here. So can I assume the touchpanel firmware will NOT be an issue since 3.18 is stock?
.
Click to expand...
Click to collapse
That would be the incorrect assumption. Since the phone came out of the box with 3.18, it will have the upgraded touch panel firmware. Meaning AOSP ROMs will not have a functional touch screen, unless you S-off and downgrade the touch panel firmware.
For Sense ROMs, its doesn't matter, you are fine with the upgraded touch panel firmware.
BTW, please hit the "Thanks" button for any posts that you found helpful!
redpoint73 said:
Fair enough. CR6.5 will work great. One thing to note however, recent versions of TWRP (2.4 and 2.5) are known to be problematic and will not work with CR6.5. Either use an older TWRP (2.3) or use the official CWM.
That would be the incorrect assumption. Since the phone came out of the box with 3.18, it will have the upgraded touch panel firmware. Meaning AOSP ROMs will not have a functional touch screen, unless you S-off and downgrade the touch panel firmware.
For Sense ROMs, its doesn't matter, you are fine with the upgraded touch panel firmware.
BTW, please hit the "Thanks" button for any posts that you found helpful!
Click to expand...
Click to collapse
I think I am in good shape. CleanRom is built on Sense. Ill flash the boot.img first to be on the safe side. Btw according to Scott's website for this Rom, with respect to TWRP vs CWM, this is what he says:
"Must have TWRP Recovery installed with unlocked bootloader! CWM Recovery not supported!" Can I get a clarification?
Once this is all done ill post and let everyone know how I made out. Going back now and "thanking" all who have replied
Fivetenfrank said:
I think I am in good shape. CleanRom is built on Sense. Ill flash the boot.img first to be on the safe side.
Click to expand...
Click to collapse
Since your phone is on 3.18, and CleanROM is 3.17 base, I don't know if you can be completely sure there haven't been kernel changes. You're right, it might be the same (or same enough) kernel, but to be on the safe side, it won't hurt to flash the boot.img.
Fivetenfrank said:
Btw according to Scott's website for this Rom, with respect to TWRP vs CWM, this is what he says:
"Must have TWRP Recovery installed with unlocked bootloader! CWM Recovery not supported!" Can I get a clarification?
Click to expand...
Click to collapse
Its an outdated statement. There was a time where CWM was only a unofficial (somewhat hacked) port, and caused some serious issues for some people, that then wrongly blamed scrosler and his ROM.
None of this is very relevant any longer. CWM is officially supported for our device. It works great with CleanROM 6.5 (its what I'm currently using); when I will guarantee you that the latest TWRP 2.5.0.0 will not work with CleanROM 6.5. And anything after TWRP 2.3.1.1 is known to be problematic for our device. So its really up to you, which recovery is the best to use.
If you pick CWM, this is the thread you want:
http://forum.xda-developers.com/showthread.php?t=2148909
redpoint73 said:
Since your phone is on 3.18, and CleanROM is 3.17 base, I don't know if you can be completely sure there haven't been kernel changes. You're right, it might be the same (or same enough) kernel, but to be on the safe side, it won't hurt to flash the boot.img.
Its an outdated statement. There was a time where CWM was only a unofficial (somewhat hacked) port, and caused some serious issues for some people, that then wrongly blamed scrosler and his ROM.
None of this is very relevant any longer. CWM is officially supported for our device. It works great with CleanROM 6.5 (its what I'm currently using); when I will guarantee you that the latest TWRP 2.5.0.0 will not work with CleanROM 6.5. And anything after TWRP 2.3.1.1 is known to be problematic for our device. So its really up to you, which recovery is the best to use.
If you pick CWM, this is the thread you want:
http://forum.xda-developers.com/showthread.php?t=2148909
Click to expand...
Click to collapse
Ok so noted. CWM is the way to go. So next question. How complicated is the process to remove TWRP before I flash CWM?
Fivetenfrank said:
Ok so noted. CWM is the way to go. So next question. How complicated is the process to remove TWRP before I flash CWM?
Click to expand...
Click to collapse
You don't have to remove TWRP. Just flash over the top of it with CWM.
Egrier said:
You don't have to remove TWRP. Just flash over the top of it with CWM.
Click to expand...
Click to collapse
Got it. Wish me me luck fellas. I am going to give this a whirl tonight
Hey while I have everyone's attention, are there any other roms out there worth checking out for someone like me? That's probably a loaded question given the fact that theres a boat load of Roms out there... but all opinions welcomed!
Fivetenfrank said:
Ok so noted. CWM is the way to go. So next question. How complicated is the process to remove TWRP before I flash CWM?
Click to expand...
Click to collapse
Just for the record, I'm not saying that CWM is necessarily better. Either CWM, or TWRP 2.3.1.1. Your choice. But TWRP 2.5 definitely does not work with CleanROM 6.5, and TWRP 2.4 has issues, also.
As already mentioned, no need to remove TWRP. Just flash CWM, and TWRP will be removed.
---------- Post added at 01:01 PM ---------- Previous post was at 12:58 PM ----------
Fivetenfrank said:
Hey while I have everyone's attention, are there any other roms out there worth checking out for someone like me? That's probably a loaded question given the fact that theres a boat load of Roms out there... but all opinions welcomed!
Click to expand...
Click to collapse
Yes, that is a loaded question. They are all worth checking out! To suggest one (or a few), would suggest the others are somehow "not worth" checking out. Which is really not fair to the devs that have worked so hard to give us these ROMs.
Look through the ROMs, and if any look interesting, try them. This is what most of us do. You already mentioned you aren't going to s-off yet, so the AOSP ROMs are out (due to the touch panel firmware issue).
redpoint73 said:
Just for the record, I'm not saying that CWM is necessarily better. Either CWM, or TWRP 2.3.1.1. Your choice. But TWRP 2.5 definitely does not work with CleanROM 6.5, and TWRP 2.4 has issues, also.
As already mentioned, no need to remove TWRP. Just flash CWM, and TWRP will be removed.
---------- Post added at 01:01 PM ---------- Previous post was at 12:58 PM ----------
Yes, that is a loaded question. They are all worth checking out! To suggest one (or a few), would suggest the others are somehow "not worth" checking out. Which is really not fair to the devs that have worked so hard to give us these ROMs.
Look through the ROMs, and if any look interesting, try them. This is what most of us do. You already mentioned you aren't going to s-off yet, so the AOSP ROMs are out (due to the touch panel firmware issue).
Click to expand...
Click to collapse
Yep, AOSPs are out. Thanks for all of your help everyone. Going to try this tonight. Hopefully I wont have a paperweight by this time tomorrow
Fivetenfrank said:
Yep, AOSPs are out. Thanks for all of your help everyone. Going to try this tonight. Hopefully I wont have a paperweight by this time tomorrow
Click to expand...
Click to collapse
Go slow follow directions and your phone will be fine. Don't skip steps or shortcut anything. That's where problems arise.
Sent from my HTC One XL using xda premium
also inpensi
31ken31 said:
Go slow follow directions and your phone will be fine. Don't skip steps or shortcut anything. That's where problems arise.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Thanks for the heads up. I am good on the instructions. I have found a multitude of posts outlining the steps. My biggest fear is/was the compatibility issue - flashing a rom that's not compatible with my phone. I tried flashing a Rom a couple of months ago on an HTC One X on 2.20, and I bricked it. I flashed the wrong Rom. Luckily AT&T didnt catch it and they gave me a new phone. I had to get another new phone this week past because my old HTC One X died for some unknown reason. AT&T gave me another one on warranty. This new one has the 3.18
Sounds like you flashed a ROM for the quad core "international" version (ENDEAVORU). Stick to this forum (says "AT&T" at the top) and any ROM you flash will be fine.
Or use my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237
redpoint73 said:
Sounds like you flashed a ROM for the quad core "international" version (ENDEAVORU). Stick to this forum (says "AT&T" at the top) and any ROM you flash will be fine.
Or use my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237
Click to expand...
Click to collapse
If my memory serves me correctly, that's exactly what I did.
Related
Hi everyone,
I got tired of waiting for any info regarding "official" JB on the Sensation.
In the family we have a Nexus4 and I am quite impressed with stock JB, so I decided to go for it on my Sensation.
I have unlocked the bootloaded but I haven't gained S-OFF yet.
I was about to go with the JuopunutBear trick but I am still not sure about which rom to flash, so I started looking ...
I went to CyanogenMod website and I see that there are nightlies available of CM10 for the Sensation. Looking at the guide on how to install CM on the phone, there are references to the "Revolutionary" tool which doesn't require any wire, or anything like that.
At the same time I am following the thread "CyanogenMod 10.1 Jellybean 4.2.2 - KANG" and I see that the modded 4.1.2 (made to look like 4.2.2) is in the work but there are "still" major updates coming out quite regularly. Basically, it is a work in progress.
Note: this is by no means a complain: these modded roms are awesome and the work of the devs is amazing: I am just stating matter-of-factdly that the rom is not "ready" yet.
So I came with two questions:
1) Why would I pick the Revolutionary tool (as suggested on the CM pages) vs the JuopunutBear trick?
2) Which ROM to pick? I definitely would like JB. I don't care for Sense (at all). 4.2.2 would be preferable but I understand it does not exist. My Sensation is my "primary" phone, so I need "everything" to work: bluetooth, reasonable battery life, camera, panorama, video ...
Why would I pick a modded vs "stock" CM10? And anyone has a clue of how "stable" is the nightly CM10 for the Sensation?
Do you have any suggestion?
Thanks!
yankeeDDL said:
Hi everyone,
I got tired of waiting for any info regarding "official" JB on the Sensation.
In the family we have a Nexus4 and I am quite impressed with stock JB, so I decided to go for it on my Sensation.
I have unlocked the bootloaded but I haven't gained S-OFF yet.
I was about to go with the JuopunutBear trick but I am still not sure about which rom to flash, so I started looking ...
I went to CyanogenMod website and I see that there are nightlies available of CM10 for the Sensation. Looking at the guide on how to install CM on the phone, there are references to the "Revolutionary" tool which doesn't require any wire, or anything like that.
At the same time I am following the thread "CyanogenMod 10.1 Jellybean 4.2.2 - KANG" and I see that the modded 4.1.2 (made to look like 4.2.2) is in the work but there are "still" major updates coming out quite regularly. Basically, it is a work in progress.
Note: this is by no means a complain: these modded roms are awesome and the work of the devs is amazing: I am just stating matter-of-factdly that the rom is not "ready" yet.
So I came with two questions:
1) Why would I pick the Revolutionary tool (as suggested on the CM pages) vs the JuopunutBear trick?
2) Which ROM to pick? I definitely would like JB. I don't care for Sense (at all). 4.2.2 would be preferable but I understand it does not exist. My Sensation is my "primary" phone, so I need "everything" to work: bluetooth, reasonable battery life, camera, panorama, video ...
Why would I pick a modded vs "stock" CM10? And anyone has a clue of how "stable" is the nightly CM10 for the Sensation?
Do you have any suggestion?
Thanks!
Click to expand...
Click to collapse
Number 1:
The S-OFF tool you use depends on your stock firmware/HBOOT.
If you want to use Revolutionary, which is by far easier. Then you must have Gingerbread (Android 2.3) / HBOOT 1.17.0006 to 1.18.0000.
If you have ICS (Android 4.0.3/4.0.4) and a HBOOT above 1.18.0000 then JuopunutBear is the path to follow.
Number 2:
4.2.2 does exist. (Branch: android-4.2.2_r1)
The CM10.1 (4.2.2) Kangs are brilliant and basically fully functional minus a few bugs here and there (LPA and video glitches seem to be the main bugs). The devs are fantastic at fixing and generally updating the device to make it run smoothly. The CM10 nightlies (4.1.X) work great if you want to use them and are fully functional as far as I can tell. (I've been using them for a few days now.)
Modded/kang is basically an enhanced version with more modules, optimization and bloat removal (CM10 has almost none, depending on how you see some apps). Most kangs come with a custom over-clocked kernel and several kernel fixes and governors which I personally prefer.
The choice between Cyanogen's nightlies and a kang is up to you. I generally download a kang ROM if I see something I like such as the kernels (and their governors) or their module support (NTFS/CIFS/USB-OTG). However kangs are generally a little more prone to bugs as the developer kangs features and then fixes them to work properly. If you see something in the ROM you want or need, then you should download it.
CM10 Nightlies are good if you want light-weight, out of the box stock android without sense. Battery life is good in general with CM10/CM10.1.
Since you're starting off, I suggest you try Albinoman887's CM10.1 (4.2.2) ROM. (http://forum.xda-developers.com/showthread.php?t=2115520)
If you just want simple "It works!", try CM10 Nightlies, or CM9 Stable.
Revolutionary tool is used to root and gain s-off if you're coming from a gingerbread Rom. The hboot is easily hacked. The ics hboot is more difficult, hence the need for the wire trick.
Go with CM10. As far as I know, its pretty stable. Strictly speaking, all cm roms are modded, the nightly versions tend to be more experimental and almost a beta stage. CM10.1 is probably less stable.
Thank you both for your suggestions: I didn't know about the "limitations" of the Revolutionary tool: I am on ICS and I think you guys saved me a whole bunch of time
I'll give CM10 a try then: i I don't like it, I'll try something else.
One last question, if I might: what's with the GApps?
Certain roms include them, other have a separate installer ... Wouldn't I be able to install any app via the play store anyway?
Thanks again, I really aprpeciate teh help.
yankeeDDL said:
Thank you both for your suggestions: I didn't know about the "limitations" of the Revolutionary tool: I am on ICS and I think you guys saved me a whole bunch of time
I'll give CM10 a try then: i I don't like it, I'll try something else.
One last question, if I might: what's with the GApps?
Certain roms include them, other have a separate installer ... Wouldn't I be able to install any app via the play store anyway?
Thanks again, I really aprpeciate teh help.
Click to expand...
Click to collapse
GApps includes the Google Play Store and other Google Apps. CyanogenMod was asked not to include Google Apps. I'm not quite sure why other developers do the same, but it's their choice and I'm sure they have a reason.
DennisBold said:
GApps includes the Google Play Store and other Google Apps. CyanogenMod was asked not to include Google Apps. I'm not quite sure why other developers do the same, but it's their choice and I'm sure they have a reason.
Click to expand...
Click to collapse
This is correct. When you flash a cm Rom, you need to flash gapps too, which includes gmail, play store, and othmp Google related apps like g+ and Google search.
Ok, but I do see several versions of the Gapps (a search on XdaDev shows several hits) and most of them look to be phone-specific, which makes little sense to me.
Shouldn't there be a "generic" Gapps (ok, maybe a different one per ICS, one for JB ... )?
Usually compatible gapps will be posted in the CM thread along with the rom itself.
Hey guys, i have an Incredible S. My mate is running a Sensation XE. I have my phone completely modded (S-OFF, Blackrose Hboot etc). My mate wants to root his.
If i just Unlock the bootloader via HTC Dev. Flash a custom recovery using the fastboot etc files from the ones i used. Can i just flash the ROM and use the command fastboot flash boot boot.IMG? Thanks
Sent from my Incredible S using xda premium
james1196 said:
Hey guys, i have an Incredible S. My mate is running a Sensation XE. I have my phone completely modded (S-OFF, Blackrose Hboot etc). My mate wants to root his.
If i just Unlock the bootloader via HTC Dev. Flash a custom recovery using the fastboot etc files from the ones i used. Can i just flash the ROM and use the command fastboot flash boot boot.IMG? Thanks
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
There's no garauntee it will work. Fastboot can fail writing the boot image while S-ON. It's why 4EXT has SmartFlash.
Install 4EXT if you want to use HTCDev, and enable SmartFlash.
james1196 said:
Hey guys, i have an Incredible S. My mate is running a Sensation XE. I have my phone completely modded (S-OFF, Blackrose Hboot etc). My mate wants to root his.
If i just Unlock the bootloader via HTC Dev. Flash a custom recovery using the fastboot etc files from the ones i used. Can i just flash the ROM and use the command fastboot flash boot boot.IMG? Thanks
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
DON'T for the love of god flash the hboot you use for your incredible S on his sensation! You'll hard brick his phone! use the sensation versions. If he's still on gingerbread, the the revolutionary tool to unlock the bootloader and gain s-off in one.
icanttinkofaname said:
DON'T for the love of god flash the hboot you use for your incredible S on his sensation! You'll hard brick his phone! use the sensation versions. If he's still on gingerbread, the the revolutionary tool to unlock the bootloader and gain s-off in one.
Click to expand...
Click to collapse
Okay. I wanna flash the boot.IMG on mine before s-off I had to do it manually. For me I had to downgrade.
He's on latest ICS
Sent from my HTC Incredible S using xda premium
james1196 said:
Okay. I wanna flash the boot.IMG on mine before s-off I had to do it manually. For me I had to downgrade.
He's on latest ICS
Sent from my HTC Incredible S using xda premium
Click to expand...
Click to collapse
Please correct me if I'm wrong.
Flash your boot image, your Incredible S boot image on his Sensation?
Kernels don't work like that.
Use JuopunutBear and the wire trick to S-OFF. It's less complicated, and doesn't require HTCDev unlock anymore (there's a guide here on xda somewhere).
icanttinkofaname said:
DON'T for the love of god flash the hboot you use for your incredible S on his sensation! You'll hard brick his phone! use the sensation versions. If he's still on gingerbread, the the revolutionary tool to unlock the bootloader and gain s-off in one.
Click to expand...
Click to collapse
DennisBold said:
Please correct me if I'm wrong.
Flash your boot image, your Incredible S boot image on his Sensation?
Kernels don't work like that.
Use JuopunutBear and the wire trick to S-OFF. It's less complicated, and doesn't require HTCDev unlock anymore (there's a guide here on xda somewhere).
Click to expand...
Click to collapse
both of you are confused i think
(he is talking about boot.img not bootloader )
he meant that after flashing a ROM for sensation XE he will flash the boot.img of the same rom
which is perfectly fine and also correct way of doing as he has unlocked bootloader
---------- Post added at 04:24 PM ---------- Previous post was at 04:20 PM ----------
james1196 said:
Okay. I wanna flash the boot.IMG on mine before s-off I had to do it manually. For me I had to downgrade.
He's on latest ICS
Sent from my HTC Incredible S using xda premium
Click to expand...
Click to collapse
you can flash the ROM for the sensation XE using custom recovery
then yes ..you need to flash boot.img of the same rom from fastboot
then its a perfect flash
now the same flashing boot.img process (in case of HTCDEV unlocked bootloader ) has been automated in 4EXT recovery ..via an option called "smartflash"
so
you can use that recovery ..go to tools section and enable smartflash
then flash the ROM (and dont reboot from the ROM flash itself if an option like that is given after flashing the ROM)
come back to recovery ..then reboot from recovery
this will take care of manually flashing the boot.img
---------- Post added at 04:40 PM ---------- Previous post was at 04:24 PM ----------
DennisBold said:
There's no garauntee it will work. Fastboot can fail writing the boot image while S-ON. It's why 4EXT has SmartFlash.
Install 4EXT if you want to use HTCDev, and enable SmartFlash.
Click to expand...
Click to collapse
I think you kinda said it reverse way
if the person did HTCDEV then fastboot flash of boot.img of a particular rom before or after flashing the ROM can never fail (unless the rom has multiple kernel options and the person fastboot flashed one kernel's boot.img while he chose another kernel when flashing the ROM)
there are multiple instances when smartflash (which actually does the same fastboot flash of boot.img but its automated in recovery ) failed (happens always when moved from GB to ICS/JB , also due to user choosing to reboot from ROM flash (couple of ROMS give this reboot option after rom flash happened ) itself which should not be done ..they should manually come back to recovery then do the reboot )
ganeshp said:
both of you are confused i think
(he is talking about boot.img not bootloader )
he meant that after flashing a ROM for sensation XE he will flash the boot.img of the same rom
which is perfectly fine and also correct way of doing as he has unlocked bootloader
---------- Post added at 04:24 PM ---------- Previous post was at 04:20 PM ----------
you can flash the ROM for the sensation XE using custom recovery
then yes ..you need to flash boot.img of the same rom from fastboot
then its a perfect flash
now the same flashing boot.img process (in case of HTCDEV unlocked bootloader ) has been automated in 4EXT recovery ..via an option called "smartflash"
so
you can use that recovery ..go to tools section and enable smartflash
then flash the ROM (and dont reboot from the ROM flash itself if an option like that is given after flashing the ROM)
come back to recovery ..then reboot from recovery
this will take care of manually flashing the boot.img
---------- Post added at 04:40 PM ---------- Previous post was at 04:24 PM ----------
I think you kinda said it reverse way
if the person did HTCDEV then fastboot flash of boot.img of a particular rom before or after flashing the ROM can never fail (unless the rom has multiple kernel options and the person fastboot flashed one kernel's boot.img while he chose another kernel when flashing the ROM)
there are multiple instances when smartflash (which actually does the same fastboot flash of boot.img but its automated in recovery ) failed (happens always when moved from GB to ICS/JB , also due to user choosing to reboot from ROM flash (couple of ROMS give this reboot option after rom flash happened ) itself which should not be done ..they should manually come back to recovery then do the reboot )
Click to expand...
Click to collapse
Thanks for your time. Yes that's what I meant. Smartflash doesn't work on my device so I wasn't sure.
Sent from my HTC Incredible S using xda premium
hi my problem is my phone is on hboot 1.09 s-off with downgraded lcd firmware and im gettting the same issue from all 4.2.2 roms. it runs perfectly until i lock the screen then the hw keys will light up and the screen is touch responsive but shows no immage and im wondering if anyone else has run into this problem or if anyone has any advice for what to try now. tried re flashing and 3 different 4.2.2 roms i tried xylon 2.7.7 with kernel 98, pacman, cm10 and i get the same result so i must be missing something because i cant seem to find anyone with the same issue. any help is much appriciated.
Try updating to 2.14 hboot and downgrade touchscreen fw. Then, wipe everything in twrp, make sure its 2.3.3.1 or under and reflash.
If you need to flash a new twrp because you're over 2.3.3.1, make sure to do fastboot erase cache after.
I'm currently running the 4.2.2 rom in my signature with little to no issues as a daily driver. Bear it mind it is an RC so it's normal to have a hiccup here or there.
Sent from my One X using xda app-developers app
exad said:
Try updating to 2.14 hboot and downgrade touchscreen fw. Then, wipe everything in twrp, make sure its 2.3.3.1 or under and reflash.
If you need to flash a new twrp because you're over 2.3.3.1, make sure to do fastboot erase cache after.
I'm currently running the 4.2.2 rom in my signature with little to no issues as a daily driver. Bear it mind it is an RC so it's normal to have a hiccup here or there.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
ok so that was a stupid question i figured out how to upgrade hboot now all im wondering is if after upgrading to 2.14 will i need to re unlock bootloader re s-off and then downgrade my touchscreen fw? because damn this is getting to be alot just to get 4.2.2 to flash and if i do all that and still have the same issue with the screen im going to end up being the proud owner of a very broken paper weight
duplotron said:
ok so that was a stupid question i figured out how to upgrade hboot now all im wondering is if after upgrading to 2.14 will i need to re unlock bootloader re s-off and then downgrade my touchscreen fw? because damn this is getting to be alot just to get 4.2.2 to flash and if i do all that and still have the same issue with the screen im going to end up being the proud owner of a very broken paper weight
Click to expand...
Click to collapse
RUU does not require/reset anything with S-OFF. Just run the RUU. RUU will be an .exe file.
If you are using the OTA instead (zip file) you would need to flash the stock recovery and flash the zip file from there. Still no relocking or anything needed, just stock recovery
where could i locate said ruu.exe
duplotron said:
where could i locate said ruu.exe
Click to expand...
Click to collapse
redpoint73's Resource Compilation click the link in my signature, there's a section of RUU links in the Original Post
exad said:
redpoint73's Resource Compilation click the link in my signature, there's a section of RUU links in the Original Post
Click to expand...
Click to collapse
awesome and just running the ruu i wont have to change my bootloader or anything? just flash and it should change the hboot?
duplotron said:
awesome and just running the ruu i wont have to change my bootloader or anything? just flash and it should change the hboot?
Click to expand...
Click to collapse
correct.
Hi, I'm wondering if you were able to fix the issue as I have the exact same problem with my phone and the only ROMs I am able to run without that black screen of death are Stock Sense ROMs.
Thanks
brazcub said:
Hi, I'm wondering if you were able to fix the issue as I have the exact same problem with my phone and the only ROMs I am able to run without that black screen of death are Stock Sense ROMs.
Thanks
Click to expand...
Click to collapse
Fastboot flash boot boot.img extracted from the Rom you're flashing.
Sent from my One X using xda app-developers app
Trust me, nothing works. I made a thread but it never caught on but many people have this problem and there is no fix. It's a problem due to the kernel. The only ROM I could find that works is the Carbon Rom.
http://forum.xda-developers.com/showthread.php?t=2212825
[5/11/13][ROM][AOSP]CarbonRom weekly unofficial builds JB 4.2.2 [evita]
-Sugardaddy
exad said:
Fastboot flash boot boot.img extracted from the Rom you're flashing.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I'm S-OFF so I don't think it has anything to do with that. I was talking about phone going to sleep and never waking up. It flashes CM Roms ok, boots them, everything works, except that whenever phone goes to sleep, the screen comes back completely black non responsive
---------- Post added at 07:26 AM ---------- Previous post was at 06:41 AM ----------
Arrow44 said:
Trust me, nothing works. I made a thread but it never caught on but many people have this problem and there is no fix. It's a problem due to the kernel. The only ROM I could find that works is the Carbon Rom.
http://forum.xda-developers.com/showthread.php?t=2212825
[5/11/13][ROM][AOSP]CarbonRom weekly unofficial builds JB 4.2.2 [evita]
-Sugardaddy
Click to expand...
Click to collapse
Thanks, I just installed Carbon and I can't believe it works. I had tried every single CM10.1 ROM but none of them worked. Thanks a lot.
Arrow44 said:
Trust me, nothing works. I made a thread but it never caught on but many people have this problem and there is no fix. It's a problem due to the kernel. The only ROM I could find that works is the Carbon Rom.
http://forum.xda-developers.com/showthread.php?t=2212825
[5/11/13][ROM][AOSP]CarbonRom weekly unofficial builds JB 4.2.2 [evita]
-Sugardaddy
Click to expand...
Click to collapse
You dont find it strange that it only affects certain people and not everyone?
Sent from my Sony Tablet S using xda app-developers app
Hey guys,
I'm still on the second snapshot build of 10.1 for the ville, but I'm getting kind of annoyed by the battery life, so I decided to move on to a nightly.
I read in the official nightlies thread that the 7/11 build was one of the most stable and battery friendly builds, so I'll just assume that. I can't, however, find a single source that documents all the steps so I'll just ask it here. Please tell me if I'm missing something, I don't like uncertainties with these things.
As far as I could see, this is what I need to do:
Optional: Gain S-off (not necessary but handy for the rest of this process I think) via Facepalm or so
Update my phone's firmware by these instructions http://forum.xda-developers.com/showthread.php?t=2322755
...including installing TWRP etc.
Wipe my caches (if I didn't already have to wipe everything in the previous step)
Flash the ROM and gapps
Could anyone please confirm this and tell me any things I should pay attention to? As of late, all the things like firmwares, kernels and radios make it a bit more difficult for me to grasp.
Thanks it advance, I hope I'm not the thousandth person asking this. I did look through the threads, you know ^^
P.S. Some interesting things, might you ask: I have S-ON, my HBOOT version is 2.15. If anything else isn't clear, let me know.
ThomasHunter said:
Hey guys,
I'm still on the second snapshot build of 10.1 for the ville, but I'm getting kind of annoyed by the battery life, so I decided to move on to a nightly.
I read in the official nightlies thread that the 7/11 build was one of the most stable and battery friendly builds, so I'll just assume that. I can't, however, find a single source that documents all the steps so I'll just ask it here. Please tell me if I'm missing something, I don't like uncertainties with these things.
As far as I could see, this is what I need to do:
Optional: Gain S-off (not necessary but handy for the rest of this process I think) via Facepalm or so
Update my phone's firmware by these instructions http://forum.xda-developers.com/showthread.php?t=2322755
...including installing TWRP etc.
Wipe my caches (if I didn't already have to wipe everything in the previous step)
Flash the ROM and gapps
Could anyone please confirm this and tell me any things I should pay attention to? As of late, all the things like firmwares, kernels and radios make it a bit more difficult for me to grasp.
Thanks it advance, I hope I'm not the thousandth person asking this. I did look through the threads, you know ^^
P.S. Some interesting things, might you ask: I have S-ON, my HBOOT version is 2.15. If anything else isn't clear, let me know.
Click to expand...
Click to collapse
if you are on hboot 2.15 it seems that you have already updated your firmware.
so you only have to install twrp,wipe system/data/cache 2-3x, flash the rom, flash the boot.img, flash gapps and you should be fine.
i'm on 7/13 nightly and it runs fine so far, no fc reboots and acceptable battery life.
NQNH said:
if you are on hboot 2.15 it seems that you have already updated your firmware.
so you only have to install twrp,wipe system/data/cache 2-3x, flash the rom, flash the boot.img, flash gapps and you should be fine.
i'm on 7/13 nightly and it runs fine so far, no fc reboots and acceptable battery life.
Click to expand...
Click to collapse
Hey, wow, now that you say it... That's kind of weird, I've been off stock for months now so I thought my firmware wouldn't auto update... But you're right. I thought I misquoted my notes in the OP but I just double checked, and I really have 2.15.
Well, thanks for noticing, and for your answer. I think I'll flash it soon then, now that the process is simplified!
By the way, do I have to flash boot.img via fastboot, or can I also do that from within TWRP? Can't seem to recall how I did that the previous time..
ThomasHunter said:
Hey, wow, now that you say it... That's kind of weird, I've been off stock for months now so I thought my firmware wouldn't auto update... But you're right. I thought I misquoted my notes in the OP but I just double checked, and I really have 2.15.
Well, thanks for noticing, and for your answer. I think I'll flash it soon then, now that the process is simplified!
By the way, do I have to flash boot.img via fastboot, or can I also do that from within TWRP? Can't seem to recall how I did that the previous time..
Click to expand...
Click to collapse
if you are on s-on flash the boot.img via fastboot.
if you are no s-off you dont have to do this step.
NQNH said:
if you are on s-on flash the boot.img via fastboot.
if you are no s-off you dont have to do this step.
Click to expand...
Click to collapse
Yeah, I'm S-On. Was just wondering if I could also flash boot.img via recovery, instead of via fastboot. But I'll use fastboot then. Thanks a lot!
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.
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