To summarize:
Rogers EVO 3D GSM
No SIM Card currently in the phone
Had Stock ICS Update
Rooted the phone, causing it to become stuck in an irreversible restarting pattern
Phone (if left alone for a while) will turn itself off within 4-6 minutes, and restart. It will repeat. If it is plugged-in and charging, it (occasionally) does not turn off. If the music player is playing in the background, it will not turn off.
Problem will persist even if the SD Card is not present.
Have tried multiple solutions (see page 2) which haven't worked.
Could really use some help!
Hi there, I was hoping that the more experienced phone users here could help me with my problem.
My phone is an EVO 3D (Rogers GSM). A while back, I decided to try and root my phone (I had the ICS update at the time). I managed to S-OFF it and later unlock it, but I had a lot of trouble rooting the phone through conventional guides.
In trying to root my phone, it became stuck in a boot loop that would cause it to turn on, flash the HTC logo, but then turn off and repeat the process. This was a really annoying issue for me, that I couldn't resolve until as a last-ditch effort, I managed to install a stock RUU and fix the problem.
Finally, I was able to root the phone last week. But as soon as I did so, it began performing erratically again. This time, the phone would turn itself off and turn back on (and repeat the process infinitely) if I left it alone for 5-7 minutes.
I tried everything I could think of to fix the problem, even wiping the partition caches/dalvik drives and factory resetting it multiple times. But even with all that, it wouldn't resolve the issue. I heard that the SD card could've been the root of the problem, but even after taking it out the problem still occurs. I've also tried factory resetting it without the SD card, but to no avail.
So I decided to install my first ROM; Viper3D (1.0.0-Multi-8_14).
I was successful in installing it, and the new software was great, but unfortunately, the issue still carried over. Unless I was constantly doing something on my phone, the phone would shut reboot after 5-7 minutes. And it would keep repeating without end. More factory resets would not do anything, and I find myself unable to install Stock ROMs now.
A sort of "temporary" fix (when I want to keep the phone on for a bit) is to keep the music player playing. As long as a song is playing (even if the volume's off), the phone won't reboot.
Nothing else works.
I'm really at my wits' end here, and I hope that someone can help me with my problem. If you have any further questions you need answered before you can help me, by all means ask.
(Also, I'm not sure if this has any bearing on the issue, but my HBOOT downgraded after the root from 1.58 to 1.49. Could that be related to my problem at all?)
Thank you very much for your time.
ReversaI said:
Hi there, I'm relatively new in terms of anything phone-related, so I was hoping that the more experienced people here could try to help me with my issue.
My phone is an EVO 3D (Rogers GSM). A while back, I decided to try and root my phone (I had the ICS update at the time). I managed to S-OFF it and later unlock it, but I had a lot of trouble rooting the phone through conventional guides.
In trying to root my phone, it became stuck in a boot loop that would cause it to turn on, flash the HTC logo, but then turn off and repeat the process. This was a really annoying issue for me, that I couldn't resolve until as a last-ditch effort, I managed to install a stock RUU and fix the problem.
Finally, I was able to root the phone last week. But as soon as I did so, it began performing erratically again. This time, the phone would turn itself off and turn back on (and repeat the process infinitely) if I left it alone for 5-7 minutes.
I tried everything I could think of to fix the problem, even wiping the partition caches/dalvik drives and factory resetting it multiple times. But even with all that, it wouldn't resolve the issue. I heard that the SD card could've been the root of the problem, but even after taking it out the problem still occurs. I've also tried factory resetting it without the SD card, but to no avail.
So I decided to install my first ROM; Viper3D (1.0.0-Multi-8_14).
I was successful in installing it, and the new software was great, but unfortunately, the issue still carried over. Unless I was constantly doing something on my phone, the phone would shut reboot after 5-7 minutes. And it would keep repeating without end. More factory resets would not do anything, and I find myself unable to install Stock ROMs now.
A sort of "temporary" fix (when I want to keep the phone on for a bit) is to keep the music player playing. As long as a song is playing (even if the volume's off), the phone won't reboot.
Nothing else works.
To summarize:
Rogers EVO 3D GSM
Had ICS installed before root
Rooted, now phone is stuck in irreversible restarting pattern
Problem persists even without SD Card
Now using Viper3D ROM, but the problem remains
Could really use some help
I'm really at my wits' end here, and I hope that some of you can help me with my problem. If you have any further questions you need answered before you can help me, by all means ask.
(Also, I'm not sure if this has any bearing on the issue, but my HBOOT downgraded after the root from 1.58 to 1.49. Could that be related to my problem at all?)
Thank you very much for your time.
Click to expand...
Click to collapse
Sounds like a possible bad flash, you are obviously using the stock kernel, did you flash the new firmware, check setting about phone and will see baseband etc, that will tell if you have flashed the correct firmware, I too am with rogers. also using viper rom multi, hboot is the same and I have no such problem, here a screeny baseband, never mind the kernel
Please don't quote an op of that size next time but I'm on the correct firmware on my CDMA device and reboots happen occasionally it is most likely the ics update in general or just the kernel try a different one
Sent from my PG86100 using xda premium
No, mistake using tapatalk on my phone, anyways as I am a gsm phone and you already have a thread opened, wait for an answer from someone as I have no experience with cdma evo's, I would advice you to put more info as what rom you are using, hboot, firmware and service provider
sent on my Evil Evo running the special sauce kernel
It says:
UNLOCKED
SHOOTER_U PVT SHIP S-OFF RL
HBOOT-1.49.0008
RADIO-11.25.3504.06_M
OpenDSP-v02.6.0.2226.00.0202
eMMC-boot
Jul 15 2011, 14:39:25
Kernal Version
3.0.16-ge733189
[email protected] #1
SMP PREEMPT
(everything else is identical to yours, I think)
Baseband Version
11.77.3504.00U_11.25.3504.06_M
Build Number
1.11.401.110 CL68035 release-keys
Browser Version
WebKit/534.30
Yes, new firmware, what I would try is in recovery wipe all partitions except sdcard, wioe dalvik and cashe and factory wipe, then reflash the rom, I do have a custom kernel which might interest you, I do know that some people have had issue's with the viper rom, pm me if you want more info
sent on my Evil Evo running the special sauce kernel
Could you please help provide some step-by-step instructions, assuming you can remember them? Sorry. D:
Ok, 4ext recovery is hopefully what you have installed on your rooted phone? Have you made a nandroid back up of your existing rom?Boot into recovery you will see wipe and format, press that and you should see down near the bottom format all partitions except sdcard, press that also on that screen you will also see wipe dalvik & cashe and factory wipe. Then install zip from sd card and find the rom zip and flash, and wait, now just to let you know all your data will be erased, so contacts should be back up with gmail
sent on my Evil Evo running the special sauce kernel
I have ClockworkMod, actually. o-o
Should I get 4ext instead?
ReversaI said:
I have ClockworkMod, actually. o-o
Should I get 4ext instead?
Click to expand...
Click to collapse
yes that could be why you have an issue, 4ext is much better and prefered
Is there a way to get rid of one and add the other? Like, flash a new recovery or something?
Since your phone is rooted, you can just use the 4ext app to install the recovery. See my Web signature for a link to the free version.
Read, Search, Read again, ... Then Ask with Tapatalk 2
ReversaI said:
Is there a way to get rid of one and add the other? Like, flash a new recovery or something?
Click to expand...
Click to collapse
I believe if you install 4ext it over rides cwm but it was months ago since i did the upgrade, viper rom has an aroma installer which works much better with 4ext recovery, who rooted your phone?
flashallthetime said:
I believe if you install 4ext it over rides cwm but it was months ago since i did the upgrade, viper rom has an aroma installer which works much better with 4ext recovery, who rooted your phone?
Click to expand...
Click to collapse
It will overwrite, so no need to erase first.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Still working on it...
ReversaI said:
Still working on it...
Click to expand...
Click to collapse
yap it;s so easy just read the recovery b4 you make any selection and take your time
---------- Post added at 11:50 PM ---------- Previous post was at 11:47 PM ----------
coal686 said:
It will overwrite, so no need to erase first.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Click to expand...
Click to collapse
us old folks forget things:laugh: first sign of dementia :laugh::laugh::laugh::laugh::laugh::laugh:
---------- Post added at 11:57 PM ---------- Previous post was at 11:50 PM ----------
coal686 said:
It will overwrite, so no need to erase first.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Click to expand...
Click to collapse
flashallthetime said:
yap it;s so easy just read the recovery b4 you make any selection and take your time
---------- Post added at 11:50 PM ---------- Previous post was at 11:47 PM ----------
us old folks forget things:laugh: first sign of dementia :laugh::laugh::laugh::laugh::laugh::laugh:
Click to expand...
Click to collapse
i'll give you the apn's for rogers as I remember them by heart
Name rogers
apn rogers-core-appl1.apn
mmsc http://mms.gprs.rogers.com
mms proxy 10.128.1.69
mms port 80
apn types default,supl,mms
those are the settings for mobile and mms
Ok here is the deal you flashed Vipers ics rom unless you flash the latest kernel from that other guy you are going to experience random reboots.
So my suggestion is go download that other guy's kernel and install it.
spirithandler said:
Ok here is the deal you flashed Vipers ics rom unless you flash the latest kernel from that other guy you are going to experience random reboots.
So my suggestion is go download that other guy's kernel and install it.
Click to expand...
Click to collapse
gave him it already:good:
List of attempted solutions that have not worked:
Wiping everything (and formatting it) except for SD Card.
Wiping (and formatting) the SD Card
Installing a new ROM
Flashing a different kernel
Factory Resets
Wiping Dalvik & Cache
Wiping Dalvik/Cache BEFORE & AFTER installing a ROM
Stuff I haven't tried:
Re-locking the Phone
Reinstalling a stock RUU (not ROM)
Unrooting
Welcome to the world of the EVO 3D. Hate to be the one to say this but it's just one of those 3ds. Mine had random reboot problems and lockups no matter what ROM, kernel, firmware, root access, anything. Just happens to a lot of them. Some people report success with relocking and unlocking the bootloader and making sure you're S-Off but I've tried it all.
Maybe that's not the case for you but it seems to be for a lot of people.
You can follow me on Twitter - @NotSo1nter3stin
Related
I Have restorted to being the noob that signs up to ask a question...The other day I was driving (pre-root) and I look down to notice my phone had power cycled on its own. I thought it would come back one, boy I was wrong....
It spiralled into endless boot cycle. It would at first reboot get to the 4g screen and then back to the htc...over and over. I was able to get into Hboot, and atempt to do a factory reset that didnt help because it became a endless reboot that way as well.
Now before any of you say "why dont you warranty replace the phone" Im a VZW agent, alas we dont have a warranty on our phones when it comes to our concessions lines...
Now, at that point I said enough is enough and I delved into the world of rooting. I self taught everything within a few hours. I had my phone unlocked and ready to go. I picked Ineffabile (http://forum.xda-developers.com/showthread.php?t=1420513) to use as a rom, I followed the procedure to a T it installed correctly, but then when it came back on everything seemed to work fine...for about 5 minutes and then it happened agian a power cycle all over again. and again...and again. It now comes on works for about 5mins and then reboots.
Im at a complete loss at this point I have gone back into the SD card and deleted the ph98 file etc.... I just dont know what to do. I need this phone to work.
Any help is appreciated Thank you so much!
I know you said it's not the wcdma problem but will your phone stay booted with the back cover off?
Else I'd ruu back to stock. Could try the different radios and see if it helps.
If you want to try the older radios and are on the OTA you'll have to hexedit you mainver. There's a guide if you look.
older radios? Im still new to this so I applogize...
A couple weeks ago there was an OTA (over the air update) that updated the radios - what controls the calls part of your phone and can affect reception and other stuff, I don't know everything it does. So if you wanted to try the older ones there's a thread somewhere, I think by con247, that has the older ones.
Here's a couple guides to help you get familiar with rooting stuff:
http://androidforums.com/evo-3d-all-things-root/389787-beginners-guide-rooting-android-devices.html
http://androidforums.com/evo-4g-all-things-root/129648-quick-intro-rooting-those-new-rooting.html
You can try flashing the kernel again. Sometimes bootlooping is a kernel issue, although it doesn't seem to be the cause of your situation.
How about insurance? Do you have that? Can you still get it?
feralicious said:
A couple weeks ago there was an OTA (over the air update) that updated the radios - what controls the calls part of your phone and can affect reception and other stuff, I don't know everything it does. So if you wanted to try the older ones there's a thread somewhere, I think by con247, that has the older ones.
You can try flashing the kernel again. Sometimes bootlooping is a kernel issue, although it doesn't seem to be the cause of your situation.
How about insurance? Do you have that? Can you still get it?
Click to expand...
Click to collapse
I dont have insurance =/ and cant get it either. Im trying to find the radios, and what kernal should I be flashing? because I cannot find the one that should match the rom im using.
What I dont understand is why the phone powers on, works for a few moments like nothing is wrong what so ever. Then freezes and reboots.
Oh, there's a new way of packing a ROM with a script that then installs the kernel so I guess it's all together now on Ineffabilis. Here's a link to the MikMik forum where they still have the stock rooted kernel as a separate download:
http://themikmik.com/showthread.php...-Beats-Tweaks-2-01-605-11&p=164906#post164906
Just take off the part of the name before PH98IMG.zip, put it on your external sd card. Do a battery pull, then reboot into bootloader by holding volume down + power. It will flash it and I think reboot. Then delete the PHzip file after that.
Don't know if it will help...
Oh... when you flashed Ineffabilis, did you restore any data from a backup? If yes, try flashing again and not restoring any data, just set up everything again manually. Also, if you restored any data from another phone's backup that could have caused problems. Basically you don't want to restore data from a different ROM.
feralicious said:
Oh, there's a new way of packing a ROM with a script that then installs the kernel so I guess it's all together now on Ineffabilis. Here's a link to the MikMik forum where they still have the stock rooted kernel as a separate download:
Just take off the part of the name before PH98IMG.zip, put it on your external sd card. Do a battery pull, then reboot into bootloader by holding volume down + power. It will flash it and I think reboot. Then delete the PHzip file after that.
Don't know if it will help...
Oh... when you flashed Ineffabilis, did you restore any data from a backup? If yes, try flashing again and not restoring any data, just set up everything again manually. Also, if you restored any data from another phone's backup that could have caused problems. Basically you don't want to restore data from a different ROM.
Click to expand...
Click to collapse
This is a clean SD card, and I didnt create a backup because I couldnt get the phone past Hboot when it was doing boot cycles previous to the root. I re-ruu'd right now. And im starting from scratch. I used clockwork before, Im trying amon ra now.
Looking for help/suggestions.
I have 2 aria that developed random reboot for no apparent reason...
My work aria was rooted and s-off running cm7.1 for about a month with no issues, I've flashed kang cm7.2 and all seemed ok, but the next morning the phone was dead (it was at 50% before going to sleep). charged it in the morning (the battery was 0%), came to work and while it was on my desk the phone rebooted and continued to do that through out the day. At home, i did factory reset, did not help. I've put it back to s-on and put back the stack ATT 2.2, same results, continues to re-boot at random intervals. Thinking it was hardware, got my job to get me a different phone.
3 weeks later, my wife's aria (rooted but still s-on) running cm7.1 started to run extremely slow and battery would drain in about 5 hours. I've done factory reset, clear everything and it still doing random re-boots just like my aria.
With one aria, I thought that it was a hardware issue, but now 2 arias, looks like os/software. Resetting/ re flashing does not help.
Any suggestions would be highly appreciated.
Are the devices overclocked?
Theonew said:
Are the devices overclocked?
Click to expand...
Click to collapse
yes, they both were overclocked, do not remember at what level, i think whatever the cm7.1 default was.... I did put them back to 600, which did not help.
Thank you
was such a problem! htc aria repaired and the problem was in nand module! I advise to contact the warranty service center!
dimon2242 said:
was such a problem! htc aria repaired and the problem was in nand module! I advise to contact the warranty service center!
Click to expand...
Click to collapse
Thank you, I gave mine back at work, my wife's is out of warranty. Interesting that both of them developed the same problem (i haven't touched wife's in months). Do you know what may cause such a problem?
Did you try doing "format system" before doing a clean install? Also make sure you are using a recent version of Clockworkmod (5.x).
strykme said:
Thank you, I gave mine back at work, my wife's is out of warranty. Interesting that both of them developed the same problem (i haven't touched wife's in months). Do you know what may cause such a problem?
Click to expand...
Click to collapse
You should touch your wife('s) more often
Sorry, couldn't resist
Running CM-7.2.0-RC for about a month and the Airia just started random rebooting this morning. Nothing changed except some software updates -- such as Google Maps.
I restored to a NAndroid backup from 3 weeks ago and it still random reboots. Suspecting a hardware problem, I even put the SD card in another Airia and restored the older NAndroid backup, but still having the reboot problem.
Any thoughts?
yar2 said:
Running CM-7.2.0-RC for about a month and the Airia just started random rebooting this morning. Nothing changed except some software updates -- such as Google Maps.
I restored to a NAndroid backup from 3 weeks ago and it still random reboots. Suspecting a hardware problem, I even put the SD card in another Airia and restored the older NAndroid backup, but still having the reboot problem.
Any thoughts?
Click to expand...
Click to collapse
yea i do
malware
wipe the phone , then check it out
I have performed factory resets and all other formats and clear functions in Clockworkmod. Should I refomate the SD card too?
Sent from my Liberty using XDA
yar2 said:
I have performed factory resets and all other formats and clear functions in Clockworkmod. Should I refomate the SD card too?
Sent from my Liberty using XDA
Click to expand...
Click to collapse
Can, because possible errors on the SD card
I still have not solved the random reboot issues. I have two Arias with the exact same problem. I think I somehow contaminated the 2nd phone by swaping SD cards and loading a Nandroid backup from the 1st phone. Both phones are rooted.
I have tried loading 4 roms -- Liberated, CM7.1 stable, CM7.2 RC and Menjeni's version of CM9 and have the exact same random reboot problem Seems like the phones works for anywhere from 5 minutes to over an hour and then reboot.
When I load the different ROMs I wipe everything -- the factory data reset, all the caches and re-formats that CWM offers. I also reformatted the SD card and reloaded CWM via Rom Manger in an effort to completely clean the phone. I also ran two a virus/malware scans on the phone and SD card -- which found no errors.
Is there something else I can do to further clean the phones? Since the same problem is with both phones, I seriously doubt its a hardware problem.
Anyone interested in purchasing 2 somewhat functioning Arias?
yar2 said:
I still have not solved the random reboot issues.
Click to expand...
Click to collapse
yar2, what HBOOT version do you have on the two devices?
HBOOT 6.02.1002
Thanks for trying to help me with this!
yar2 said:
HBOOT 6.02.1002
Thanks for trying to help me with this!
Click to expand...
Click to collapse
OK. I'm assuming you have an AT&T Aria. If not let me know.
Here's what I'd suggest you do. I'm basically trying the most extreme steps to correct the issue so we can verify if the issue is something that can be corrected or not.
1) Reformat your SD card(s) with SD Formatter 3.1. This tool sometimes fixes hard to detect problems that aren't corrected when formatting with other methods. (Default settings are fine.)
2) Run the AT&T 2.2.2 RUU to revert your phone to almost 100% stock. I say almost because the RUU will NOT change your HBOOT, which means even after doing this process, you will still have S-OFF.
3) Try using the phone with the stock unmodified ROM to see if you experience the random reboots you described. If you do, the rest of the steps are not necessary and it's probably a hardware issue.
4) Install CWM by putting your phone into FASTBOOT mode, then using the Android Flasher utility to install the latest version of Clockworkmod. Use this version: http://www.mediafire.com/?lg6b63aqpi1cvbg (source). If you know how to do this from command line with the fastboot command line tool, that is fine too.
5) Boot into CWM. Do factory reset/wipe data and format system partition. Then install the ROM of your choice. I'd suggest something like a recent version of CM7 since it is very stable. If using CM7, install 20110828 gapps immediately after flashing CM7. Reboot and see how it goes.
Even if you already downloaded any of the above files, delete them and download them again this time around (or check the md5 sums if you know how). It's possible the files were corrupted when you downloaded them before and that is why you keep having problems.
Also, as an aside: Are you using third-party batteries with your devices?
Aria random reboot
Thanks drumist for all you advice! When I did my last attempt at a clean install, I used a spare SD card that had never been in the phone.
Both phones are AT&T Arias with the original batteries. I liked the Aria size so much that I upgraded my wife's expired Iphone contract when AT&T was providing a free Aria upgrade just to have a spare in case I damaged one by rooting. Now I have managed to mess up both phones!
I was thinking my next step would be to go back to a stock state, as you recommend. I was thinking of going even further and un-rooting and S-On. Do you think the problem could be in the Hboot partition? And wouldn't going back to S-on replace the Hboot?
I still think I somehow contaminated the 2nd phone by restoring a Nandriod backup from the first phone. The 2nd phone was working find until I did the restore.
Regardless, I will try what you suggest and let you know the results.
yar2 said:
I was thinking my next step would be to go back to a stock state, as you recommend. I was thinking of going even further and un-rooting and S-On. Do you think the problem could be in the Hboot partition? And wouldn't going back to S-on replace the Hboot?
Click to expand...
Click to collapse
Reverting the HBOOT to stock (and yes, returning to S-ON) has some risk -- i.e., if you make a mistake during the process, you can permanently brick the device, so I wouldn't recommend that except as a last resort. The RUU will reflash every other partition on your phone back to stock besides the HBOOT and is safe to do, so stick with that.
I still think I somehow contaminated the 2nd phone by restoring a Nandriod backup from the first phone. The 2nd phone was working find until I did the restore.
Click to expand...
Click to collapse
Yeah, it's possible. If that is the case, though, the HBOOT wouldn't be the problem (because Nandroid backups do not touch the HBOOT). The RUU will reflash every partition that Nandroid touches.
If you already tried using a different SD card, then I wouldn't worry about using that SD Formatter tool.
Can't find a copy of the AT&T 2.2.2 RUU. They took it off the HTC website. The instructions there are for an OTA update, which I can't do since I'm not running the stock rom.
---------- Post added at 02:51 PM ---------- Previous post was at 02:12 PM ----------
Never mind. I found a copy of the RUU on my laptop.
I have installed the hboot drivers and the phone shows up as a device on my computer, but the RUU says it can't find my phone. I am running Windows 7, if that makes any difference.
Got the RUU to load from an XP machine. Bad news is that the phone still randomly reboots.
I guess the only other step is to un-root and S-On. What have I got to lose. Can't use the phones as they are now.
Got a good way to do this?
hboot is 1.15 i am running 1.22.651.3 i have s-on and am unlocked... i am trying to get s off i am trying to flash to cm10 but i cannot get any were can someone please point me in the right direction ... i have read and read and read and nothing adds up to what happens.. .i use clock work mod to download and install when it boots into recovery it says it installs but the screen stays black i have to hard reset (power vol down and camera) it to get anywere then it goes back into recovery and i use the back up file i had to get my phone to work... what am i doing wrong...
No offense to the developer but I would steer clear on CM10 on the Evo. It ran fine on my Nexus but it really didn't do well on my Evo. The MMS didn't work worth a darn. The biggest issue I had was no data. I reflashed it. I wiped everything. I read the instruction 20 times. It just doesn't work well and has some bugs. There seems to always be some major bugs in the AOSP line of roms. Even on the Nexus G AOKP was a constant headache. I wish I could just say do these three steps and all will be flawless. Sorry, that just isn't the case.
Sorry to point this out but this topic goes on the q&a section not on development
HTC EVO LTE
Not sure what kc is talking about I have flawless data and mms on cm10. I have 4g and it works totally fine with no data issues whatsoever. Now the op is posting in the wrong place, but I would gladly help if the post was more clear. So are you s-off or not? If not it will require you to either get s-off or flash the boot.img separately. If you are s-off try using twrp not clockwork. I have been on twrp since I got the Evo in July and have had zero flashing issues.
Sent from my EVO using xda premium
---------- Post added at 09:52 PM ---------- Previous post was at 09:48 PM ----------
I will add mms has been flawless since using Gosms as has been discussed in the cm10 thread multiple times. Not sure if mms works otherwise, but go sms solves it if it is still being worked on. If you don't like/want to us Gosms then just install it solely for mms because it does send and receive them and they show up in the stock messaging app as well.
Sent from my EVO using xda premium
i have s on and all i can access is twrp and hboot
I'm not entirely sure how you managed to put [Q] in your thread title AND ignore the box that says "Is this a question?". There is a very, very clearly labeled section for questions and answers, and your question is one of the most asked here.
Here's your two step fix:
1. Learn where to post. (please)
2. You are S-ON. The reason why you see a black screen is because S-ON users can't flash kernels from recovery. You have to do it seperately. Custom ROMs like AOSP or ROMs that use custom kernels can't be flashed normally on S-ON.
3. No, you did not read. At all. We can tell because the very first thread in the Questions and Answers forum (http://forum.xda-developers.com/showthread.php?t=1869377) says the following:
Note: To those of you with CWM Recovery, it is recommended that you use TeamWin Recovery as it is better suited for our phones.
Brick This is a very serious problem, your device is catatonic and will not respond to the usual methods of power on/off or sim-pull. In some cases the phone comes back when the battery dies and is recharged, this isn't very often. There are un-bricking tools written by OEMs when they screw up (Samsung / Motorola) and there are tools written by developers working on S-OFF. They notice a very real danger and will supply the tool just in case (this is not possible in all cases). Bricking can and will be permanent in many situations
Boot loop There a different kinds of boot loop situations (also referred to as soft brick, please do not cry brick in the forums if it is a boot loop) the most common are a mismatch of kernel and ROM.
Help, my phone is stuck in a boot loop or my phone is stuck on HTC! Not a problem at all. Hold down the power button and continue to hold it, the capacitive buttons will begin flashing and phone will reboot. After the screen turns off let go of power for one second and the press and hold power and volume down to boot into the boot loader. This is known as a simulated battery pull. HTC built this in as a fail safe to reboot your phone, and it gives us a chance to jump into the boot loader should anything go wrong. Once you have successfully made it to the boot loader read through these forms of boot loop to understand what went wrong.
Known forms of boot loop
Generic Boot loop You have a working recovery and now you have installed your first ROM. There's just one problem every ROM you try boot loops but if you restore your back up and it runs fine. This is common when you haven't taken the time to wipe your phone before you flash. You can use a wipe script to clean your phone or you can systematically wipe Dalvik, Cache, Factory Restore, and then wipe System. Now you can flash your custom ROM (HBOOT 1.15+ requires you to flash the kernel separately)
Help my phone won't boot past the splash screen similar to a generic boot loop, the most common fix is to wipe the phone before flashing your ROM. Wipe your dalvik and cache, the factory reset and wipe system. You can now flash your new ROM
Kernel Issue You have flashed a kernel that may be corrupt, originate from a different base, or is just not supported by the ROM (not really the case these days, most developers are willing to share tweaks and custom code) The result is a phone that boots to a black screen and will hang or reboot.
Note: HBOOT 1.15+ requires you to flash the kernel separately, all relevant info to do so is in this guide.
Click to expand...
Click to collapse
In the future, if you have a question, consider placing it the forum that is meant for that. Sorry to sound like an ass, but I'm in a bad mood.
thank for the help...
I am running Cyanogen Mod 10.0 on the phone for 2 weeks and not even one issue. I updated to the latest TWP before I installed the ROM. I am never going back to gay Sense. Sorry but I can't stand sense. I love the build quality of the EVO more than any other phone on the market. I really hope they come out with a Nexus Device.
Download CyanogenMod from their site and you will not have an issue.
Go to the aokp thread and at the beginning says how to push the boot.img vías fast boot after that you should be fine flashing the rom
Sent from my EVO using xda premium
Can someone delete this thread? or move it? or help this guy read instructions on how and where to post things?
Yes I'm closing this. And OP WATCH your language. YOU posted in the wrong area, not the other way around... So it's YOUR fault and No ONE herer owes you ANYTHING.
On a side note, if everyone quotes the offensive language I have to delete that too... just an FYI
Not the first post a noob really wants to make...but I've been searching the forums for an answer to my problem, but can't seem to find the info on the issue I'm having. I've seen some that were close & tried what was posted there without any success. I've checked out the Don't Panic -- Please Read First, includes troubleshooting guide Thread By: om4
A few days ago, I tried to install CM10 on my 4G LTE w/S-ON / HBOOT- 1.19. I was able to unlock the bootloader & install TWRP. Everything seemed to go okay until I rebooted my phone after installing CM10. It just hung on the Cyanogenmod splash screen. I tried re-installing it & kept getting the same problem. Today, I tried to install MeanROM ICS v6.5, but it keeps saying install failed. If I let the phone boot up, it'll hang on the MeanRom splash screen. I can still get into fastboot so I know it has to be a software issue. I've been beating my head against the wall for the past few days & just don't know how to fix it. Right now I have a very expensive paperweight. I'm hoping someone can help me fix this & get my phone back up & running.
TIA
for the millionth time
flash the boot.img seperately in hboot
Get (Flash Image GUI) off the Play Store.
If yr S-ON then u have to flash the kernel separate. That's why the ROM's keep hanging.
sent from my EVO LTE
http://forum.xda-developers.com/showthread.php?t=1772769&highlight=fastboot+gui
flex360 said:
for the millionth time
flash the boot.img seperately in hboot
Click to expand...
Click to collapse
I've been trying this all day, but must be doing something wrong. I found this: http://forum.xda-developers.com/showpost.php?p=29417266&postcount=1397, but was wondering if you might have more info on option 3.
TIA
if you know how to Fastboot, go for it, but use the Boot.img from the ROM you are flashing.
popper668 said:
if you know how to Fastboot, go for it, but use the Boot.img from the ROM you are flashing.
Click to expand...
Click to collapse
It's the only option I have now, so I hope I can figure it out. Wish me luck. I know it's probably something stupid that I'm missing & it's driving me crazy. lol
For meanrom make sure you have twrp 2.2.2.0 or later to be able install. The kernel installer will force the phone to reboot upon first run, this is when the kernel installs. For cm10 or other aosp based roms be sure to properly wipe phone. Cache, dalvik, factory reset, and system. Fastboot the kernel using SDK, mini SDK, uniflash, or boot image flasher. Do not use clockwork mod recovery to install roms as it is known to damage internel storage and or misc partitions.
ADB Tools Mini SDK
Thanks for all the info!!! I'm glad I found this place!!! I was able to get my phone working again. I found this post: http://forum.xda-developers.com/showthread.php?t=1937949 from back in October and found out that I was putting the boot.img in the wrong location. Once I fixed that, I have my phone back. Now I have to get it re-activated because I had to switch back to my Hero because I wasn't sure how long this would take. I hope Sprint will activate it even though is not stock anymore.
buddahj said:
Thanks for all the info!!! I'm glad I found this place!!! I was able to get my phone working again. I found this post: http://forum.xda-developers.com/showthread.php?t=1937949 from back in October and found out that I was putting the boot.img in the wrong location. Once I fixed that, I have my phone back. Now I have to get it re-activated because I had to switch back to my Hero because I wasn't sure how long this would take. I hope Sprint will activate it even though is not stock anymore.
Click to expand...
Click to collapse
have your first thanks
lol
the thanks is for using the search function lol
Well now I have another small problem. When I try to use the camera or go into gallery, it says no external storage available. Looks like I'm off to search the forums again for a fix. I'm sure it's something minor.
It looks like it's the internal SD card. Under storage in settings it shows the external card's total space & the 3 GBs used for app data, ect...
When I try and mount the SD card, it says preparing card but doesn't do anything. I think I say something about changing something in TWRP.
Forgot to mention, I can't connect the phone via USB either.
Ha, fixed my SD card/USB issues by following the directions in this thread - http://forum.xda-developers.com/showthread.php?t=1812774
I've been searching all morning to find another thread to see if this has been answered before. I was trying to install a GSM Rom onto my Rezound. The install failed at around 2 %. I'm almost positive I thought I was on the correct ICS firmware, when apparently I wasn't. So instead of trying to fight installing the rom over and over again. I had a back up rom that I installed instead. My problem I think is that I didn't go back and re wipe everything after the failed install.
Which I could slap myself for, but my problem is this. The phone can go into Hboot, which gives me hope not all is lost. But I can't go into recovery or boot up. The phone will only load the white HTC screen then just reboots over and over again. I've seen where it tries to load recovery but then just reboots. I'm not sure if I have to reload the RUU or what I have to do. If anyone has had this problem or knows of a thread on how to fix it I would greatly appreciate it.
Edit: Just a little about my phone if it helps.
Vigor Pvt S-OFF RL
HBOOT - 2.25.0000
Radio - 1.22.10.0421r/1.22.10.0424r
OpenDSP- v13.6.0.7611.00.0104
eMMC-boot
Since you can't get to recovery it might be time to just put an RUU on you card and let hboot install it. Then you can install a recovery and then one of your backups.
Or just reinstall recovery
Sent from my Vivid 4G using Tapatalk 2
Ok, unfortunately I'm stuck at work and can't fix it right away. But I do thank you both for your help. I'll try the RUU first, since it needs to be done anyways. I was using Clockwork Mod Touch for my recovery before, is Amon Ra that much better ? I'll let you guys know the results soon as I can get it done.
stfumate said:
Ok, unfortunately I'm stuck at work and can't fix it right away. But I do thank you both for your help. I'll try the RUU first, since it needs to be done anyways. I was using Clockwork Mod Touch for my recovery before, is Amon Ra that much better ? I'll let you guys know the results soon as I can get it done.
Click to expand...
Click to collapse
I prefer CWM touch myself but the one from here not the official
stfumate said:
Ok, unfortunately I'm stuck at work and can't fix it right away. But I do thank you both for your help. I'll try the RUU first, since it needs to be done anyways. I was using Clockwork Mod Touch for my recovery before, is Amon Ra that much better ? I'll let you guys know the results soon as I can get it done.
Click to expand...
Click to collapse
If you plan to do a restore, stick to the same recovery.
Not sure how restoring over a previous rom borked your recovery though, that is weird.
mjones73 said:
If you plan to do a restore, stick to the same recovery.
Not sure how restoring over a previous rom borked your recovery though, that is weird.
Click to expand...
Click to collapse
Well I started off as I normally would, wiping data, wiping cache, wiping davlik, then installing. I tried one of the new JB roms Tron. But I couldn't get the GPS to work at all. So I stumbled across a GSM rom and went to install, it booted into it's own installation touch screen. I kept it simple not choosing many extras, then the last option was. Are you on ICS firmware? Which to my noobness, I've been running ICS roms since I acheived S-OFF. So I was pretty positive that I upgraded my firmware whenever I did that. So I chose Yes and it started to install, got to 2% and said it was done. Again I assumed the install had just failed and after having tried installing a GSM rom once before I had to go through and do it multiple times. I was tired and didn't feel like messing with it. So instead of rebooting, I went back into recovery and flashed another rom I had set on my SD card in case I didn't like the GSM. To which I think that my mistake came when I didn't either
A) Re-wipe my data, cache, davlik.
or
B) Restore my previous Rom from before.
So after the new rom installed and looked as everything went smooth. I selected reboot, the HTC white screen came up and the phone shut off. Then would power back up and display the HTC white screen and shut off again. So far the only thing I've been able to get it to do is the power cycle with the white screen and boot up in Hboot. But none of the options will work as the only thing it will do is power cycle. That's pretty much where I'm at until I can try reinstalling the RUU and flash the new(same) recovery.
The problem is nothing you've done there should have touched the recovery, that's why I find it weird.
I'd assume the rom asked which firmware you were on so it could installed the old firmware patch if needed.
Anyway, hopefully the RUU should straighten it out.
Well good news, re-installing the RUU fixed the phone. It re-locked my hboot, so I just finished unlocking that and re-flashing recovery. Thanks a bunch for all of your help. I greatly appreciate it !