Related
I unlocked the bootloader and rooted it okay... then I flashed a ROM, that also worked fine. I tried to flash a kernel and now it just gets stuck on the HTC screen. I tried restoring my back up, still the same issue. Tried reflashing the ROM, same issue. Not sure how to get it back to normal at this point.
It sounds like the kernel you flashed is either a 2.3.3 kernel that doesn't work on 2.3.4, or it was a bad flash. You should be able to fix this by holding volume down when booting up (opens HBOOT) then choose Recovery and from the recovery you can then either enable USB Mass Storage device and transfer a stock kernel over USB to your SD card then flash the stock kernel, or if you already have a stock kernel on your SD card, you can just select it from the install from zip menu and flash.
This Kernel should work fine (it's stock with CIQ spyware removed):
http://forum.xda-developers.com/showthread.php?t=1224659
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Coriolis3ffect said:
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Click to expand...
Click to collapse
ROMs usually have kernels. You could just wipe Dalvick cache and cache and flash your original rom (which has it's original kernel). and that should work.
There's a sea of roms. You could try posting on a rom's thread whether a particular kernel is compatible. Just follow the spin of things. Saves from just going round in circles.
Coriolis3ffect said:
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Click to expand...
Click to collapse
Here's a scenario: If you installed a rooted stock 2.3.4 rom then decided to install Silverneedle kernel, your phone will get stuck in this boot-loop because the silverneedle kernel is not compatible with 2.3.4 yet. So by flashing a stock kernel over what is already on there, it should fix the problem. Before you flash the stock kernel clear cache and dalvik. After that flash the kernel and reboot the phone. Chances are it will boot normally. I doubt you will have to reflash a ROM to fix this.
Just cleared the dalvik and the cache, reflashed the ROM hoping to start completely fresh and its still getting stuck...
Coriolis3ffect said:
Just cleared the dalvik and the cache, reflashed the ROM hoping to start completely fresh and its still getting stuck...
Click to expand...
Click to collapse
Then flash a stock kernel. I have had the same problem before. I flashed a ROM, installed a kernel and stuck at HTC boot screen. The fix is to either install a stock kernel through bootloader or flash another ROM in recovery. If you want the best chance of it working the first time, then flash the stock rooted 2.3.4 ROM by xhausx. If you want to try other ROMs and kernels, make sure that your ROM and kernel are compatible. Also use the synergy wipe zip file before flashing to make sure everything is formatted properly. Also, did you flash the extra firmwares that came with the 2.3.4 update? If not, make sure you flash those along with the new radio that just came out.
Sent from my PG86100 using Tapatalk
Take it you didn't do a nandroid before flashing?
Sent from my PG86100 using xda premium
Tried to get my nandroid and it still got stuck..
Perhaps I should've also mentioned that my bootloader still says S-ON and I unlocked it using the HTC unlock method.
sn0b0ard said:
Then flash a stock kernel. I have had the same problem before. I flashed a ROM, installed a kernel and stuck at HTC boot screen. The fix is to either install a stock kernel through bootloader or flash another ROM in recovery. If you want the best chance of it working the first time, then flash the stock rooted 2.3.4 ROM by xhausx. If you want to try other ROMs and kernels, make sure that your ROM and kernel are compatible. Also use the synergy wipe zip file before flashing to make sure everything is formatted properly. Also, did you flash the extra firmwares that came with the 2.3.4 update? If not, make sure you flash those along with the new radio that just came out.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Not sure about any extra firmwares actually.... currently going to try flashing xhaus' ROM and hope that works...
Flashed the superwipe before flashing the ROM, then flashed the ROM... it went to the HTC screen for a second then just vibrated and then turned black.
When I go into the bootloader when it is loading up the images.... it kept saying "No Image!" for all of them. I'm not having any luck with this at all.
Coriolis3ffect said:
When I go into the bootloader when it is loading up the images.... it kept saying "No Image!" for all of them. I'm not having any luck with this at all.
Click to expand...
Click to collapse
Do you have it named exactly PG86IMG.ZIP?
Sent from my PG86100 using xda premium
Okay... you mentioned something about firmwares to flash... which ones are they?
I'm kinda lost at this point because I'm not sure about the specific order in which you are supposed to do things.
Which version of hboot do you have?
Sent from my PG86100 using xda premium
1.50.000 or whatever
Just follow this guide easy. Easy step by step.
http://forum.xda-developers.com/showthread.php?t=1231249
jayharper08 said:
Just follow this guide easy. Easy step by step.
http://forum.xda-developers.com/showthread.php?t=1231249
Click to expand...
Click to collapse
+1 on this. RUU method should be bullet proof
Coriolis3ffect said:
Okay... you mentioned something about firmwares to flash... which ones are they?
I'm kinda lost at this point because I'm not sure about the specific order in which you are supposed to do things.
Click to expand...
Click to collapse
It's in the post that xhausx made for the stock rooted 2.08.651.2 ROM.
URL: http://forum.xda-developers.com/showthread.php?t=1223979
List of new firmwares for the 2.08.651.2 update:
(If you do the RUU method, you should have all the firmwares installed automatically btw...)
Radio & PRI Updates Radio 0.97.10.0808 PRI 1.24_003
PG86IMG_radio_pri.zip (MD5: E28414AAC6F91CE9D7B3615B2999AD3A)
RPM Possible fix for Black SOD
PG86IMG_rpm.zip (MD5: DE69396C8922FAD3AC82E5F836EE95FB)
SBL Secure Bootloader?
PG86IMG_sbl.zip (MD5: 5604349AD611241CF1AC152FD3B0DE45)
TZ Trusted Zone - Not sure of it's purpose
PG86IMG_tz.zip (MD5: 75749FBCCE1331A5A85D2A154E15B276)
PG2F2_SPCUSTOM - No idea what it is
PG86IMG_pg2f2_spcustom.zip (MD5: 7A7DE8659A0771919A14B0C299CA18CC)
Click to expand...
Click to collapse
The link posted is for the GSM Evo 3D... will it work on CDMA?
Hey GUIs...I recently used the HTC official unlck to unlock ny EVO 3s and then I installed a ROM...I thought that the ROM might be the problem but it wasn't....first off when I installed it my Wimax, camera,WiFi, or video playback didn't work...she. I flashed the damn Sprint ROM back and still had the sane problems? Any thoughts?
What rom did you install? Did you install the kernal to go with that rom? Did you re-install the stock kernal when you went back to the stock rom?
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
I had installed.miui at first and then synergy and I didn't do either kernel for either 3 ROMS...where would u find them
Sent from my PG86100 using XDA App
megarain5 said:
I had installed.miui at first and then synergy and I didn't do either kernel for either 3 ROMS...where would u find them
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
You need the appropriate kernel for the rom to run properly. Kernels for each rom should be listed in the rom thread. If you are on hboot 1.5 you will have to flash the kernel separately in the bootloader or with the Flash GUI app.
sitlet said:
You need the appropriate kernel for the rom to run properly. Kernels for each rom should be listed in the rom thread. If you are on hboot 1.5 you will have to flash the kernel separately in the bootloader or with the Flash GUI app.
Click to expand...
Click to collapse
so even with me messing up the kernel once if i find the correct kernel everything will revert and work? because when i flashed miui it stuck on the startup screen and never loaded past that so if i find the kernel that solves everything?
I would at least wipe cache and dalvik after flashing the kernel. If you run into problems, you may need to fully wipe, then install the rom from stratch, then install the kernel right after.
sitlet said:
I would at least wipe cache and dalvik after flashing the kernel. If you run into problems, you may need to fully wipe, then install the rom from stratch, then install the kernel right after.
Click to expand...
Click to collapse
Well yeah thats the problem i did it using the flash gui app...the first kernel i tried which was a tiamut kernel didnt load....so i used rcmix_3d_evo_kernel...it accepted, when it went into reboot. it never loaded after that. But now when i go into my recovery...i can actually unpack that zip now. when beforehand, it would alwasy fail...does that mean something? im trying the way you just said by flashing it, then wipping the dalvik and cache and then flashing my rom, basically right now im bricked unless this works, and the way to help me not be bricked doesnt work because megaupload has been seized so i cant get the cwm to make my sd card. RUU doesnt work to flash it back to stock. Im pretty much stuck with a bricked phone...hopefully i find a way around this. theres a thread on here that refers to other people being bricked from this exact kernel.
sitlet said:
I would at least wipe cache and dalvik after flashing the kernel. If you run into problems, you may need to fully wipe, then install the rom from stratch, then install the kernel right after.
Click to expand...
Click to collapse
Hey you really helped me, i ended up being bricked but what i had to do was flash the kernel twice or idk exactly which worked but i had to fastboot flash the boot.img from the ROM i were gonna use and flash the kernel...now all of my things are back working, 4g, wifi,video playback and everyting...the thing is the kernel was a defective kernel IF NOT FLASHED CORRECTLY.
Hello,
I've been all over google and this site for the last two days trying to find a way to get my Evo 3d work! I tried searching the forum and unfortunately i kept getting server errors So i figured I would make a new thread in the hopes of figuring this out!
What happened:
I went through the rooting process, and I went to flash a ROM on to the phone and it would not load pass the HTC screen. I had a ROM on there of the stock version of the Sprint Evo 3d, unfortunately it wasn't the proper version and it did not allow 4G and such. So i tried to place another ROM on to the SD Card and flash it over, and for some dumb reason, I deleted the version of the Stock Rom that atleast enabled me to get the phone to turn all the way on. All I'm able now is to boot up to recovery, but I can't figure out what ROM to download to place on the phone to get me back to square one!!!
Help please!!
-Mike
jerseybizzle said:
Hello,
I've been all over google and this site for the last two days trying to find a way to get my Evo 3d work! I tried searching the forum and unfortunately i kept getting server errors So i figured I would make a new thread in the hopes of figuring this out!
What happened:
I went through the rooting process, and I went to flash a ROM on to the phone and it would not load pass the HTC screen. I had a ROM on there of the stock version of the Sprint Evo 3d, unfortunately it wasn't the proper version and it did not allow 4G and such. So i tried to place another ROM on to the SD Card and flash it over, and for some dumb reason, I deleted the version of the Stock Rom that atleast enabled me to get the phone to turn all the way on. All I'm able now is to boot up to recovery, but I can't figure out what ROM to download to place on the phone to get me back to square one!!!
Help please!!
-Mike
Click to expand...
Click to collapse
Hi jerseybizzle, I can certainly try to help you but you have to help me first.
1. Are you doing a factory reset and wiping dalvik cache before flashing?
2. What hboot version do you have?
3. Is your phone s-on or s-off?
4. Which rom did you try to flash that wouldn't boot?
wikdNoob said:
Hi jerseybizzle, I can certainly try to help you but you have to help me first.
1. Are you doing a factory reset and wiping dalvik cache before flashing?
2. What hboot version do you have?
3. Is your phone s-on or s-off?
4. Which rom did you try to flash that wouldn't boot?
Click to expand...
Click to collapse
1. Yes
2. 1.50
3. My phone says S-on but I have super user privileges and the guide I followed said I have the phone rooted whether or not it said S-Off or S-On.
4. I believe it was the ViperMod
jerseybizzle said:
1. Yes
2. 1.50
3. My phone says S-on but I have super user privileges and the guide I followed said I have the phone rooted whether or not it said S-Off or S-On.
4. I believe it was the ViperMod
Click to expand...
Click to collapse
If it was an ics Rom and you are having bootloops, it is most likely because you are s-on. I recommend getting s-off. The wire trick is easy to do, but you need to be careful.
http://forum.xda-developers.com/showthread.php?t=1585846
Sent from my ICS 3VO with Tapatalk 2
Did you flash the rom through fastboot? If you just booted into your recovery and attempted to flash the ICS version of that rom coming from GB it won't work since you still have S-ON and that doesn't let you flash certain things like kernels. You can still flash roms but you have to take a couple extra steps or achieve S-OFF.
To get your phone working again...
If you were just coming from a stock rooted rom before attempting to flash a new rom, simply download a stock rooted rom from the dev section, put it on your SD card, boot into recovery, wipe and reflash. Your phone should then boot up again.
Sent from my PG86100 using xda app-developers app
jerseybizzle said:
1. Yes
2. 1.50
3. My phone says S-on but I have super user privileges and the guide I followed said I have the phone rooted whether or not it said S-Off or S-On.
4. I believe it was the ViperMod
Click to expand...
Click to collapse
I'm guessing it was the ics version of vipermod, and since you're s-on your boot image didn't flash. So you're trying to boot an ics rom with a gingerbread kernel.
If you want to use an ics rom, you have a few choices. My favorite... Put a recovery image in the folder on your computer that has fastboot in it. Put the phone in fastboot mode and type in the command window, fastboot boot recovery.img, make sure that you name the recovery image on your comp. to "recovery.img". It should boot to recovery and you can flash away.
Something that's easier is to use 4ext recovery smart flash. I'm sure it works but I've never used it.
If you want to get back to your stock rom unrooted rom you could run an ruu.
Also, take coals advice and s-off that phone, you won't have nearly as many issues once you s-off, and you can use one of the splash screens in my Sig
flonker said:
Did you flash the rom through fastboot? If you just booted into your recovery and attempted to flash the ICS version of that rom coming from GB it won't work since you still have S-ON and that doesn't let you flash certain things like kernels. You can still flash roms but you have to take a couple extra steps or achieve S-OFF.
To get your phone working again...
If you were just coming from a stock rooted rom before attempting to flash a new rom, simply download a stock rooted rom from the dev section, put it on your SD card, boot into recovery, wipe and reflash. Your phone should then boot up again.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
I have a stock ROM finally loaded on to here now, but it won't allow me access to Wifi now! When I try to connect it just says "error". Any ideas?
jerseybizzle said:
I have a stock ROM finally loaded on to here now, but it won't allow me access to Wifi now! When I try to connect it just says "error". Any ideas?
Click to expand...
Click to collapse
Here's an idea, get flash image GUI, its free here at xda, google it. Then use it to flash the kernel from the stock rom that you have running and reboot. This should fix your WiFi. Let me know if I'm not being clear enough.
wikdNoob said:
Here's an idea, get flash image GUI, its free here at xda, google it. Then use it to flash the kernel from the stock rom that you have running and reboot. This should fix your WiFi. Let me know if I'm not being clear enough.
Click to expand...
Click to collapse
Where would I find the stock Kernel?
jerseybizzle said:
I have a stock ROM finally loaded on to here now, but it won't allow me access to Wifi now! When I try to connect it just says "error". Any ideas?
Click to expand...
Click to collapse
So, it sounds like wifi turns on just fine, you just get the error when attempting to connect to a network?
Have you tried resetting your router and rebooting your phone? Maybe remove that network from your saved preferences and resign in.
Sent from my PG86100 using xda app-developers app
jerseybizzle said:
Where would I find the stock Kernel?
Click to expand...
Click to collapse
Inside the rom that you flashed, just choose that rom with flash image GUI and it'll pull the kernel out for you
flonker said:
So, it sounds like wifi turns on just fine, you just get the error when attempting to connect to a network?
Have you tried resetting your router and rebooting your phone? Maybe remove that network from your saved preferences and resign in.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
The wifi won't turn on period. I'll click the icon for the Wi-Fi to turn on, and it just says error. No option to even try to connect!
jerseybizzle said:
The wifi won't turn on period. I'll click the icon for the Wi-Fi to turn on, and it just says error. No option to even try to connect!
Click to expand...
Click to collapse
If the app that was suggested to didn't do the trick, hit the stickies in the dev section on how to flash a rom with hboot 1.5 S-ON. I recommend the fastboot method, however, if you're so inclined, you can also go the route of getting S-OFF.
Most likely, some problems occurred when you tried to flash that ROM before and broke your wifi. So, if I were you, I'd grab a ROM (that viper ics should be fine if you still got it) and flash it through fastboot using a guide in the dev section. Be sure to read and understand the guide before attempting it.
The guide would be something like this...
1. Install the appropriate drivers and place a recovery on your PC.
2. Boot into your boot loader, select fast boot, and connect your device to your PC via USB.
3. Open a command prompt on your computer, switch to the directory containing drivers/recovery image
4. Type fastboot boot thenameofyourrecovery.img
5. Install the rom as you otherwise normally would using your phone, wiping data, clearing caches, installing zip.
NOTE: The above is not a guide, just an illustration of the guide you're looking for in the dev section.
Flashing a rom by this method allows you to flash roms with non stock kernels, so you can pretty much flash any rom made for your phone. This is the method I have used since day 1 and have never experienced any problems. You may also want to look into getting S-OFF, but I can't say much about that because I haven't done it myself (being content flashing through fastboot).
Hope this helps.
Sent from my PG86100 using xda app-developers app
flonker said:
If the app that was suggested to didn't do the trick, hit the stickies in the dev section on how to flash a rom with hboot 1.5 S-ON. I recommend the fastboot method, however, if you're so inclined, you can also go the route of getting S-OFF.
Most likely, some problems occurred when you tried to flash that ROM before and broke your wifi. So, if I were you, I'd grab a ROM (that viper ics should be fine if you still got it) and flash it through fastboot using a guide in the dev section. Be sure to read and understand the guide before attempting it.
The guide would be something like this...
1. Install the appropriate drivers and place a recovery on your PC.
2. Boot into your boot loader, select fast boot, and connect your device to your PC via USB.
3. Open a command prompt on your computer, switch to the directory containing drivers/recovery image
4. Type fastboot boot thenameofyourrecovery.img
5. Install the rom as you otherwise normally would using your phone, wiping data, clearing caches, installing zip.
NOTE: The above is not a guide, just an illustration of the guide you're looking for in the dev section.
Flashing a rom by this method allows you to flash roms with non stock kernels, so you can pretty much flash any rom made for your phone. This is the method I have used since day 1 and have never experienced any problems. You may also want to look into getting S-OFF, but I can't say much about that because I haven't done it myself (being content flashing through fastboot).
Hope this helps.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I ended up finally finding a ROM (CM) that would load on to the phone. The Wi-Fi is working now!
I just need to find a fix for the camera, neither the regular nor 3D camera will function now.
jerseybizzle said:
Thanks. I ended up finally finding a ROM (CM) that would load on to the phone. The Wi-Fi is working now!
I just need to find a fix for the camera, neither the regular nor 3D camera will function now.
Click to expand...
Click to collapse
Which cm rom exactly? I thought the camera works with all the cm roms. It sounds like you still have kernel issues, and until you figure out how to flash a kernel or boot image, you'll always have these types of issues, bootloop, broken WiFi/camera. I know that the instructions that flonker gave you are intimidating but after you've done it once you'll see how simple it is.
One limitation of HTC dev unlocking is that you can't write to the boot partition from recovery, the kernel resides in the boot partition. You can, however, write to boot from within the android system. That's why flash image GUI is so handy for people with s-on and HTC dev unlocked. Just open the app, find the rom you'd like to flash and select it, the GUI will extract the kernel from the rom zip and flash it. Then you just boot into recovery and flash the same rom that you selected with the GUI. It'll flash everything but the boot image, but that's ok because you already flashed the kernel with flash image GUI. Make sure you do a factory reset and wipe the dalvik cache.
When I was s-on I always chose fastbooting to recovery, when you do that it actually loads the recovery onto the boot partition and gives you permission to write to boot, so its like flashing should be. Just wipe, flash, enjoy.
Hope this helps.
Wikd said:
Which cm rom exactly? I thought the camera works with all the cm roms. It sounds like you still have kernel issues, and until you figure out how to flash a kernel or boot image, you'll always have these types of issues, bootloop, broken WiFi/camera. I know that the instructions that flonker gave you are intimidating but after you've done it once you'll see how simple it is.
One limitation of HTC dev unlocking is that you can't write to the boot partition from recovery, the kernel resides in the boot partition. You can, however, write to boot from within the android system. That's why flash image GUI is so handy for people with s-on and HTC dev unlocked. Just open the app, find the rom you'd like to flash and select it, the GUI will extract the kernel from the rom zip and flash it. Then you just boot into recovery and flash the same rom that you selected with the GUI. It'll flash everything but the boot image, but that's ok because you already flashed the kernel with flash image GUI. Make sure you do a factory reset and wipe the dalvik cache.
When I was s-on I always chose fastbooting to recovery, when you do that it actually loads the recovery onto the boot partition and gives you permission to write to boot, so its like flashing should be. Just wipe, flash, enjoy.
Hope this helps.
Click to expand...
Click to collapse
I have been flashing roms and kernels and such for awhile on several different phones and literally almost everything you said makes no sense and that goes for the other guy 2 posts above yours. WTF is flash image GUI? Is that an app, you never even say.
The other guy is telling him to flash a rom but describes to him how to flash a recovery image to his phone...have you guys ever done this before or are you just making stuff up as you go?
flukeSG2 said:
I have been flashing roms and kernels and such for awhile on several different phones and literally almost everything you said makes no sense and that goes for the other guy 2 posts above yours. WTF is flash image GUI? Is that an app, you never even say.
The other guy is telling him to flash a rom but describes to him how to flash a recovery image to his phone...have you guys ever done this before or are you just making stuff up as you go?
Click to expand...
Click to collapse
Those guys probably don't even have EVO 3D's anymore. Do you read dates before posting? Threads a year old :screwy:
Sent from my PG86100 using xda app-developers app
RayTrue04 said:
Those guys probably don't even have EVO 3D's anymore. Do you read dates before posting? Threads a year old :screwy:
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Yes I do, I was looking for information and I read the entire thread. Just because they posted it a year ago doesn't make the info any less wrong.
First, let me apologize for my ignorance. Just made the move from the iDevice and am trying to navigate my way through this...
Currently, I have the 05/21/2013 Cyanogenmod nightly on my HTC One. I am having some issues with the call quality. If this weren't my daily driver that I use for work, I would just deal. I like this ROM and it seems to be pretty solid.
My question is, how to I get back to either the AT&T stock ROM, or some variant thereof? I tried flashing TrickDroid and the ROM (found here http://forum.xda-developers.com/showthread.php?t=2242319) using ClockworkMod recovery. Both resulted in the HTC One screen displaying and not moving past that. I was able to restore a backup both times.
I am obviously missing a step, but I have yet to figure it out. Any help would be appreciated.
There's a RUU in the Android development section that will bring you back to stock. be warned, you obviously lose root and it will probably flash stock recovery. RUUs are like iTunes IPSW packages to equate them to something you know.
As for flashing TrickDroid, first boot can take a while, up go several minutes in fact. I haven't had any problems flashing between CM10, ARHD, and TrickDroid aside the occasional Aroma hiccup
Sent from my HTC One
unremarked said:
There's a RUU in the Android development section that will bring you back to stock. be warned, you obviously lose root and it will probably flash stock recovery. RUUs are like iTunes IPSW packages to equate them to something you know.
As for flashing TrickDroid, first boot can take a while, up go several minutes in fact. I haven't had any problems flashing between CM10, ARHD, and TrickDroid aside the occasional Aroma hiccup
Sent from my HTC One
Click to expand...
Click to collapse
Thanks for the reply. I will try TrickDroid again.
Am I correct in flashing the TrickDroid zip from the device using ClockworkMod recovery, or is there a different method I should be using?
ScubaR6 said:
Thanks for the reply. I will try TrickDroid again.
Am I correct in flashing the TrickDroid zip from the device using ClockworkMod recovery, or is there a different method I should be using?
Click to expand...
Click to collapse
I don't think it matters, but I use TWRP to great success.
unremarked said:
I don't think it matters, but I use TWRP to great success.
Click to expand...
Click to collapse
Sounds like you are doing it correctly. Making sure of course that you have a backup if you're having trouble flashing trickdroid you can try clearing your cache and dalvik cache from within recovery. Sometimes it is also useful to wipe your data as well.
TWRP worked like a charm. Not sure why I couldn't get it done with CWM. Thanks for the help guys!
It should work fine no matter what the recovery. I like CWM more than TWRP and my install was clean.
Sent from my HTC One using xda app-developers app
I have been running MeanBean for a few months and am not very happy with the battery life and certain other "Features" and would like to flash the ICS ROM listed below. I have tried a few times to flash it but it won't install. It stalls trying to install and just sits there for up to an hour with no progress. I have wiped everything several times and get the same results. I end up having to go back to MeanBean also listed below (Which installs just fine in about 5 minutes.) I've re-downloaded the ROM several times getting the same size.
I've recently started getting random reboots with no error report generated. That and the poor battery life begs me to go back to ICS... If It would install. I have 1 year left on the contract so a new phone is not in the cards.
Any suggestions?
Kernel: 3.4.10-g19136fe
Baseband: 1.05.11.0606
Build: 3.16.651.3
S-ON
Thanks! ?)
jocarog said:
Try either mean rom ics if you haven't updated your firmware or meanbean jelly bean if you did update to the latest firmware, both have all the instructions in the op for s-on installation should be easy...
http://forum.xda-developers.com/showthread.php?t=2048229 (meanbean) :good:
http://forum.xda-developers.com/showthread.php?t=1727167 (mean rom)
Both are pure stock with a bunch of tweaks that will give you good battery life and performance, only con is that both haven't been updated in a while but are pretty stable... (ics mean rom not being developed at all anymore)
Click to expand...
Click to collapse
Micro Maniac said:
I have been running MeanBean for a few months and am not very happy with the battery life and certain other "Features" and would like to flash the ICS ROM listed below. I have tried a few times to flash it but it won't install. It stalls trying to install and just sits there for up to an hour with no progress. I have wiped everything several times and get the same results. I end up having to go back to MeanBean also listed below (Which installs just fine in about 5 minutes.) I've re-downloaded the ROM several times getting the same size.
I've recently started getting random reboots with no error report generated. That and the poor battery life begs me to go back to ICS... If It would install. I have 1 year left on the contract so a new phone is not in the cards.
Any suggestions?
Kernel: 3.4.10-g19136fe
Baseband: 1.05.11.0606
Build: 3.16.651.3
S-ON
Thanks! ?)
Click to expand...
Click to collapse
since you are s-on, are you flashing the kernel/boot.img separately? or thru fastboot? If I'm not mistaken when you are s-on you have to flash the rom twice (meanben OP and meanrom ICS OP instructed) so the kernel gets installed... Good luck!
P.S. you need to update your radio/baseband but for that you need to be s-off.
I have the same problem, except for me when I install the MeanRom zip, it reboots while it installs the kernel and then hangs. I'd really like to get this rom working again! Really the onnly reason was because I heard that Sprint limited MMS sizes on JB, and ICS was supposedly unaffected, so I wanted to see if it was true.
numel007 said:
I have the same problem, except for me when I install the MeanRom zip, it reboots while it installs the kernel and then hangs. I'd really like to get this rom working again! Really the onnly reason was because I heard that Sprint limited MMS sizes on JB, and ICS was supposedly unaffected, so I wanted to see if it was true.
Click to expand...
Click to collapse
Try a different download, did you checked the md5?? If you are s-off it should be easy to flash...
jocarog said:
Try a different download, did you checked the md5?? If you are s-off it should be easy to flash...
Click to expand...
Click to collapse
I'm s-off, and I thought maybe there was something wrong with the md5 also, but it checks out fine. I also tried downloading an older version, then dirty flashing the newer version, but that didn't work either and it hung at the same spot. I've never had problems before with flashing roms before... althoughI've never been able to flash a kernel correctly for some reason. Custom kernels and my phone just never work
numel007 said:
I'm s-off, and I thought maybe there was something wrong with the md5 also, but it checks out fine. I also tried downloading an older version, then dirty flashing the newer version, but that didn't work either and it hung at the same spot. I've never had problems before with flashing roms before... althoughI've never been able to flash a kernel correctly for some reason. Custom kernels and my phone just never work
Click to expand...
Click to collapse
thicklizard has a kernel stabilizer in his dev folder made by viperboy, my replacement doesn't like custom kernels if I don't flash that right after the kernel, did you used superwipe or just wiped in TWRP?
jocarog said:
thicklizard has a kernel stabilizer in his dev folder made by viperboy, my replacement doesn't like custom kernels if I don't flash that right after the kernel, did you used superwipe or just wiped in TWRP?
Click to expand...
Click to collapse
A stabilizer? Does that work across all roms Sense and AOSP? Or just certain types? I only wiped in twrp, but according to instruction to install kernels, all you need to do is wipe cache and dalvik before flashing right?
numel007 said:
A stabilizer? Does that work across all roms Sense and AOSP? Or just certain types? I only wiped in twrp, but according to instruction to install kernels, all you need to do is wipe cache and dalvik before flashing right?
Click to expand...
Click to collapse
You need to do a super wipe and in the same session I would flash the custom kernel and yes the stabilizer works on sense and aosp...
numel007 said:
A stabilizer? Does that work across all roms Sense and AOSP? Or just certain types? I only wiped in twrp, but according to instruction to install kernels, all you need to do is wipe cache and dalvik before flashing right?
Click to expand...
Click to collapse
Are you positive you are S-OFF? You used Facepalm,DirtyRacun,or Moonshine?
S-OFF and htcdev unlocked are 2 totally different things
Sounds to me like you are just htcdev unlocked
jocarog said:
You need to do a super wipe and in the same session I would flash the custom kernel and yes the stabilizer works on sense and aosp...
Click to expand...
Click to collapse
If I superwipe, I'll need to reflash the rom correct? And then without rebooting, install the stabilizer, wipe cache and dalvik, then Komodo?
bigdaddy619 said:
Are you positive you are S-OFF? You used Facepalm,DirtyRacun,or Moonshine?
S-OFF and htcdev unlocked are 2 totally different things
Sounds to me like you are just htcdev unlocked
Click to expand...
Click to collapse
I believe I am s-off, as my bootloader reads. I used DirtyRacun (which had a number of problems.)
Oh and my Hboot is 1.19.222 if that helps
numel007 said:
If I superwipe, I'll need to reflash the rom correct? And then without rebooting, install the stabilizer, wipe cache and dalvik, then Komodo?
I believe I am s-off, as my bootloader reads. I used DirtyRacun (which had a number of problems.)
Oh and my Hboot is 1.19.222 if that helps
Click to expand...
Click to collapse
Yup looks like you are s-off
Komodo won't work on sense roms
bigdaddy619 said:
Yup looks like you are s-off
Komodo won't work on sense roms
Click to expand...
Click to collapse
Oh I know Komodo doesn't work, forgot to mention I'm running ReVolt to test if I can install kernels... Just tried the stabilizer, and then the kernel. Still no luck Get put in a bootloop
numel007 said:
If I superwipe, I'll need to reflash the rom correct? And then without rebooting, install the stabilizer, wipe cache and dalvik, then Komodo?
I believe I am s-off, as my bootloader reads. I used DirtyRacun (which had a number of problems.)
Oh and my Hboot is 1.19.222 if that helps
Click to expand...
Click to collapse
If you are going to go back to ics mean rom do not flash Komodo! That's for aosp 4.2.2, you might want to use an ics kernel... I don't remember the name but zarbos had one and I think flar2 had another one, and flash rom, then custom kernel, then stabilizer, reboot...
jocarog said:
If you are going to go back to ics mean rom do not flash Komodo! That's for aosp 4.2.2, you might want to use an ics kernel... I don't remember the name but zarbos had one and I think flar2 had another one, and flash rom, then custom kernel, then stabilizer, reboot...
Click to expand...
Click to collapse
Yeah forgot to mention what rom I'm using. But I tried to use I believe Arc-Reactor a while back with Sense and the same thing happened then too
numel007 said:
Oh I know Komodo doesn't work, forgot to mention I'm running ReVolt to test if I can install kernels... Just tried the stabilizer, and then the kernel. Still no luck Get put in a bootloop
Click to expand...
Click to collapse
Try a lower speed meaning 1.7ghz or 1.8ghz some phones don't like to be OC'ed
bigdaddy619 said:
Try a lower speed meaning 1.7ghz or 1.8ghz some phones don't like to be OC'ed
Click to expand...
Click to collapse
I'm using the 1.5 version when I flash. I also tried the 1.7 before, and neither work. I think I have a busted phone or something lol
numel007 said:
I'm using the 1.5 version when I flash. I also tried the 1.7 before, and neither work. I think I have a busted phone or something lol
Click to expand...
Click to collapse
hmmmmm weird
BTW is revolt even for the EVO LTE? NVM found it
bigdaddy619 said:
hmmmmm weird
BTW is revolt even for the EVO LTE?
Click to expand...
Click to collapse
Well seeing as there is a thread here, someone ported it at least. It's really really nice though I'd love to get my own kernel working on it. You don't think that maybe since it's a hybrid of three different roms, that would be affecting the installation? I guess perhaps I could superwipe, install rom, install stabilizer, and then kernel.
Link to ReVolt: http://forum.xda-developers.com/showthread.php?t=2337740
numel007 said:
Well seeing as there is a thread here, someone ported it at least. It's really really nice though I'd love to get my own kernel working on it. You don't think that maybe since it's a hybrid of three different roms, that would be affecting the installation? I guess perhaps I could superwipe, install rom, install stabilizer, and then kernel.
Link to ReVolt: http://forum.xda-developers.com/showthread.php?t=2337740
Click to expand...
Click to collapse
IDK I only use sense roms so not really sure what the problem might be
bigdaddy619 said:
IDK I only use sense roms so not really sure what the problem might be
Click to expand...
Click to collapse
I could experiment quickly. I'll do the installs with Elemental 1.5 and MeanBean and see if I can boot.
Update: Flashed, rom appears to be stuck in boot animation.
Update 2: Booted! Wow, alright guess I'll try the same with ReVolt now...