I used hasoon's tool to root and flash t-mo stock ICS a week ago. Yesterday my battery completely died, and now I can only boot to TWRP and the backlight doesn't go on. TWRP reports 66% battery charge constantly, regardless of actual battery level. I have seen others with similar issues but nothing seemed to match this behavior exactly. I was thinking of trying to go through the root process again, but thought that I would post this here in case others had the same issue, and to provide a single thread as a resource for others that might come upon the problem. I am using twrp 2.0.0 from hasoon's v3.0 root app. TIA!
Ofc I fixed it right after my post, after hours of messing with it. It was fairly simple in retrospect:
I went to reflash the bootloader, but during the fastboot step the backlight went on so I just selected reboot during fastboot and the system booted properly. Hop this helps someone! I'll be upgrading my recovery in hopes that this doesn't happen again. Probably just a bug related to the battery level going to low.
Glad to see you fixed it. Go to the Play Store and buy 4EXT (It's $3). Flash the recovery. It is a lot better than TWRP
I'm glad to see your problem was resolved
In the future, please keep all question/help related threads in the Q&A section. Thank You.
Thread Closed.
-------------------------------------
Nine months before I was born, my dad took me to a party where he met my mom and took her home.
Brought to you courtesy of my Galaxy Note (i717), using XDA Premium.
Related
So, SGH-177 had been rooted and installed CM7, then Unnamed, then AOKP. All were pretty buggy. We wanted to bring it back to factory (with root if possible). Not for a warranty claim, just so it would be somewhat stable.
Anyway, I found a one click ODIN solution for UCKH7 stock. I used that, it passed. then the phone just looped through the AT&T "Rethink Possible" splash screen. I tried to get into recovery mode, but it wouldn't load, so I flashed the Siyah kernel to get CWM on there. Still I can only get into download mode and the phone loops the splash screen.
I hoped that it was just taking some time to load up the first time, so I left it overnight. Still stuck on the splash screen this morning.
I spent hours on here last night and found lots of people saying that if you have access to download mode, or recovery mode, you should be able to fix it. I wasn't able to find any answers as to how.
Help?!
I've had this same problem before. what always fixes it for me is to get into the factory 3e recovery to do a reset. I know you said you couldnt get there but make sure (while the phone is off; remove battery if you have to before this) you are holding down both Volume buttons and the power button at the same time until you see the "Samsung Galaxy SII" screen, then release the buttons.
factory reset, then it should be fine.
If you can't get to recovery, read some more on here. I'm sure something is out there, but I don't know what it is.
Here are two posts that might help you out. I've been doing the same research since my "Oh crap its stuck in a bootloop I'll sell it cheap on eBay" SGII is due to arrive today or tomorrow.
http://forum.xda-developers.com/showthread.php?t=1451590
http://forum.xda-developers.com/showthread.php?t=1580885
Best of luck to you!
UnNamed buggy?
Out of curiosity how did you root and flash, cause that is probably one of the most stable builds we have with minor changes to stock.
Anyways good luck getting back to stock.
So, for some reason, the next time I tried booting into recovery, it worked. I got a couple errors, but then it booted up just fine. Don't know why it wouldn't get into recovery before.
Everything seems to be working as it should so far.
I'm guessing this may be why some of the threads I had seen didn't really offer a solution. Sometimes it finally works if you just hold your head right.
Thanks all!
Regarding UnNamed... I don't recall the method I used to root, it's been a long time and I've done various work on this (my wife's phone) and my Nexus One. Easy to get it confused. I flashed it through CWM recovery, factory wipe, flash from SD.
It worked fine for a while (a couple months), then it got really glitchy. Unable to answer phone calls, random reboots, etc.
Major Wood said:
I flashed it through CWM recovery, factory wipe, flash from SD.
It worked fine for a while (a couple months), then it got really glitchy. Unable to answer phone calls, random reboots, etc.
Click to expand...
Click to collapse
Did you also wipe cache and dalvik? May have been the problem...
I don't recall, but would be surprised if I hadn't done that
A year ago. When I first started flashing roms. I spent an entire week just reading the atrix forums and learning. I planned. I schemed. I asked questions. Through pm. And googled a LOT. Then when I had learned enough I did it. Point is....if yer not willing to have patience and learn as much as u can before u jump into this. Then its maybe not for you.
Sent from my SGH-I777 using Tapatalk 2
I bought a fascinate from good ol craiglist for a friend. When I bought it I noticed the original user had already rooted it and installed CM7.
Because I didnt know what he had done to it I decided to start from scratch and used Odin and flashed powerwashed_20_b3_Full_ec09modem and the atlas_v2.2.2.pit
After that I flashed cwm4_fixed_for_cm7-ODIN.tar and began getting ICS on this baby (teamhacksung-ota-eng.BUILD2.zip followed by build 11 at the time).
Everything was gravy and I gave the phone to my friend who was a happy panda. Several weeks later he calls and tells me the phone is stuck in recovery, I assume he borked something so I headed over thinking I will just Nandroid the ICS ROM that I set up before I gave it to him.
Funny thing was after rebooting from the Nandroid, the phone goes back to recovery! I was a little confused but assumed that maybe the Nandroid went bad when I backed it up. So I decided to just reflash build 11 again, after the flash was successful i reboot and.... back to recovery?
At this point I was pretty confused, CWM appeared to be working but it wasnt. Nothing was working, not even flashing CM7. The only way I got it to work again was to Odin the powerwashed_20_b3_Full_ec09modem and the atlas_v2.2.2.pit again. So that was what I did and got him back to ICS (build 13 this time).
Thinking it was a freak occurence I didnt pay it any mind, until he called me again several weeks later saying its stuck in CWM again!? So I check it out and sure enough it keeps booting to recovery and not able to nandroid or flash anything (even tho it says it does successfully).
At this point I assume its a hardware issue but dont understand what exactly, I bought another on craiglist and will swap with him and further investigate the issue.
I looked around the forums to see if anyone had a similar issue but have not seen anything like this. Anyone have any ideas??
This is most likely caused by doing the three finger reboot on the newer ICS roms. Tell them to pull the battery instead the next time their phone locks up. Also, there is boot loop breaker in the development section.
Sent from my SCH-I500 using xda premium
I assumed that as well, however my friend has no experience with these devices and would never hold down all three buttons for any reason. Both times he had reported that the phone randomly went into recovery on its own.
He could be BSing me of course, but I'll be testing it when I get it back tomorrow and see if I can recreate the scenario.
But I will be including the boot loop breaker file in the SD card and see if that at least makes this phone usable again instead of having to use ODIN every time. So thanks for that info!
Check kernel settings. Sleep Of Death, maybe?
I am panicking. I just purchased my HTC Rezound from Verizon just a couple weeks ago and after unlocking/rooting, I tried to flash a ROM using CWM and now every method I try that I've found in forums takes me right back to that infinite HTC White boot screen. I can do me best to walk through the process I took to get to this point but to be honest, I'm not too greatly familiar with the Android development 'lingo' so I hope I'm able to communicate with you well enough. Ultimate result: I would JUST like to return my phone to factory settings, fresh from box and start over from the day I got it. If this is possible I will be forever grateful.
AbstractAngy said:
I am panicking. I just purchased my HTC Rezound from Verizon just a couple weeks ago and after unlocking/rooting, I tried to flash a ROM using CWM and now every method I try that I've found in forums takes me right back to that infinite HTC White boot screen. I can do me best to walk through the process I took to get to this point but to be honest, I'm not too greatly familiar with the Android development 'lingo' so I hope I'm able to communicate with you well enough. Ultimate result: I would JUST like to return my phone to factory settings, fresh from box and start over from the day I got it. If this is possible I will be forever grateful.
Click to expand...
Click to collapse
If you're seeing anything on the screen, you're NOT bricked. When you flash a ROM, the first boot up almost always takes a long time. I've had to wait over 10 minutes before.. that's kind of extreme, but seriously, try flashing the ROM again and check the clock and wait at least 10 to 15 minutes before pulling the battery.
And remember - if you can get to the bootloader, recovery or a white HTC screen, you're not bricked.
Edit: A word of advice, don't use CWM. Use Amon Ra. CWM can't charge the battery when the battery is at 0%. I believe this is an issue with TWRP recovery as well (plus TWRP can't run some scripts certain ROMs/themes need). Amon Ra is the most robust recovery on the Rezound.
Yeah cwm could cause a lot of issues, make sure to use amon Ra.
Sent from my Rezound using xda app-developers app
AbstractAngy said:
I am panicking. I just purchased my HTC Rezound from Verizon just a couple weeks ago and after unlocking/rooting, I tried to flash a ROM using CWM and now every method I try that I've found in forums takes me right back to that infinite HTC White boot screen. I can do me best to walk through the process I took to get to this point but to be honest, I'm not too greatly familiar with the Android development 'lingo' so I hope I'm able to communicate with you well enough. Ultimate result: I would JUST like to return my phone to factory settings, fresh from box and start over from the day I got it. If this is possible I will be forever grateful.
Click to expand...
Click to collapse
If you have any questions or need help, hit me up on Gtalk @ [email protected]. I would be more than happy to assist you.
See my thread here - http://forum.xda-developers.com/showthread.php?t=1872651
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
Hello, all. First, I'd like to say thank you for taking the time to read this and potentially try and help me out. Any assistance with this matter would be greatly appreciated!
I added the (Non-standard) to the title, as I've been flashing and modding this phone for over two years, and I've never experienced this issue. I'm not the type to ask for assistance, as my research skills are well above par, but after digging through literally countless forums and topics, I have yet to find anything quite like my situation...
ISSUE: Performed recent flash attempt to epinter's CM10.1. Now loads to Moto splash, sits there the usual few seconds, but when it comes time to load the rom, it reboots and starts the process again... (I swear I think I see it trying to load the rom splash for like a micro second, but then it could just be the delirium of long hours researching and fighting this problem.) Now, you might be thinking, "Eh, pretty common...", right? Yeah, me too, until I couldn't fix it like I've done a million times before... I can boot into recovery. I have performed ALL standard actions regarding flashing a new rom, yet the problem persists. The problem persists now no matter what rom I attempt to flash. Now you might be thinking, "Just flash your nandroid recovery...", but I wish, oh how I wish I could... I am currently using CWM-based Recovery 5.0.2.7, although I've tried more than a few different recoveries since this issue, all provide the same results... Which is nothing. I'm at the end of my rope here.
I've even tried flashing TWRP (two different versions) so I could at least get some charge to the battery so I could continue this debacle, but it hangs at the TeamWin splash screen...
Fastboot loads fine. Wipes performed to system, caches, partitions, etc, to no avail... Battery pull, already tried...
I've covered all the basic fixes, but my issue seems to be bigger than my knowledge base (at the moment).
Okay, here's the exact details of what led up to this...
My Atrix WAS unlocked, rooted, and using RR's CWM for recovery at the time. I had flashed everything coming and going as the scene grew, but eventually went back to CM7.2 and had been running it for ages. Well, I decided to try something new, and settled on trying BeanStalk. Flashed Aroma Prep, no problem. Flashed ROM and Gapps, no problem. Booted up fine. Decent start on the rom, but a little too buggy yet for me. So on this note I wiped and restored my CM7 nandroid backup, no problem. All was well, until I came across epinter's CM10.1 and thought, "Eh, why not?" (...and now look at the mess I'm in!) Performed a new nandroid backup of my CM7, and began the process that ended me... Everything went along just fine. Performed all my wipes, flashed my zips, rebooted, and BAM... boot loop! Little did I know what kind of headache I was in for, until I couldn't restore my backup. Now, I'm just praying I find a solution before my battery drains out completely...
SIDE NOTE: While attempting to restore fails and just resets recovery back to the main screen, there are no visible errors reported. Attempting to flash ANY of my other roms results in the same behavior. Flashes "appear" to go smoothly, but the end result is the same... I did notice upon attempting to flash BeanStalk again that there is an error reported in the aroma installer. It performs all wipes correctly, but when it comes time to actually install, it reports a broken symlink error, or something to that effect... (I would reproduce the install error message, but at the moment I'm trying to hang onto as much battery life as possible. My apologies for the inaccuracy of any statement.)
PLEASE, LADIES AND GENTLEMEN, I BEG OF YOU... If anybody has been unfortunate enough to have found themselves in my shoes, then hopefully you were lucky enough to get it figured out by now and would be willing to pass along the info. Although not my primary phone anymore, it still gets more than it's share of use. I'd hate to see it go out this way...
Any help to guide me in the right direction would be most appreciated! Thank you all in advance!