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!
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 was running CM10 experimental (supposedly stable) build and was having way too many issues: reboots 5+ times a day, random freezes requiring hard reboot, etc etc. I tried uninstalling latest apps...nope. Tried fixing permissions...nope. Finally decided to reinstall the ROM. Used CWM wiped all 3 times, went to istall from zip, couldn't find the ROM anywhere. I installed an older ICS ROM I found in there and it did it's thing until it was time to boot up...now it's stuck in boot loop. I tried removing battery, turning off with both buttons, connecting to usb...not recognized. It just keeps going thru the booting process until it says "Have a nice day!" and then starts over. How do I get in to fix this? I'm screwed....and of course use my phone all day for business......sheesh. Are there ANY JB ROMs out there that are actually stable...like in real life?
Love this site, love all of you helpful folks....pulling my hair out at this point...;-(
You're kinda asking a lot since jb has to be ported over at the moment which naturally leads to glitches such as the restarts. This is the price you pay to run jb months and months before the note is officially updated. at which time the source code will be come available and we will have rock solid jellybean builds. Until then we take what we get. Run the latest release candidate of cm9 until then if you want something super stable.
Also don't you have a backup you can restore? I'm not allowed to feel sorry for you if you never backed up your device.
Sent from my SAMSUNG-SGH-I717 using xda premium
Thanks for the reply JR, your statement " jb has to be ported over at the moment which naturally leads to glitches such as the restarts" is Greek to me. Are you saying that since it is not an official JB update, there will always be glitches? um...ok.
Yes, I have a few backups in there...but as I said, it is stuck in opening boot loop and I don't know how to get in there to restore or flash another ROM. I may be missing a simple fix here but until I know what it is, I don't know what it is. I have used search under boot loop, for an hour and have not found one thread explaining how to get out of it.
Hopefully someone will excuse my ignorance and point me to a thread or explanation of how to get past the boot loop.
Cheers
do you know how to boot into recovery?
if you can, then do that, and restore one of your backups..
if you dont know how to boot into recovery, you shouldn't be flashing roms until you do
AFAIK that means pressing volume up, home, and power until recovery lights up. Done that many times and all I get is the intermittent vibe, no flash, no screen at all.
I've poured over threads and google all day...no love. Just people telling me to restore my backups...gee thanks.
I CAN get it into Odin....can I flash a ROM from there? I followed one tutorial but when selecting a ROM, it wanted a tar file and I either had the ROM zip or unzipped, a bunch of folders with no tar file in any of them.
I'm not a moron, just screwed myself somehow and am looking for some help fixing it. I thought that's what these forums were for.
hold volume up and down and power at the same time; after the first "samsung" on the screen, release the power button, and keep holding the volume up and down, until recovery appears...
XDA is a development forum, not a newbie forum, and there is an assumption that people who flash stuff to their phones will have the basic knowledge to know how to recover from some of the problems that arise when you do something to your phone that requires the knowledge on how to fix things
The fact that you dont know how to get into recovery properly tells me you didnt bother to read and study enough on how to recover from a problem if you have one, sort of like trying to replace your water pump without actually practicing on a car..
search the forums if you need to find .tar files to restore your phone via Odin back to stock; there are several posts and threads that will show you how, but, try to recover your back up first
This ^^^^^. You have jumped into the deep end without knowing how to swim. Watch videos, read how-to's and look up words if you don't understand them. A basic knowledge of computer hardware and how a computer works pre-boot will also go a long way
redman9 said:
Thanks for the reply JR, your statement " jb has to be ported over at the moment which naturally leads to glitches such as the restarts" is Greek to me. Are you saying that since it is not an official JB update, there will always be glitches? um...ok.
Click to expand...
Click to collapse
It means there is no official jelly bean for the note at this time. Our devs have to take jelly bean code and modify it to work on the note which generally means a few hickups here and there.
Sent from my SAMSUNG-SGH-I717 using xda premium
Well thank you all for the help you have given. I was not releasing the power button after the first Samsung flash and thus not finding recovery. I have a functioning phone now, at least. I do, dig deep trying to find answers, and only post when I am truly stuck.
glad you got it fixed!
Hi everyone,
I have been frequenting XDA for quite a while. Hugely into android and custom roms and things of the sort, but have never had a real reason to post. I have either been lucky enough to be able to find what I need by searching, or figured it out myself. This time however, I am pretty stumped.
I did a fair amount of research before starting this, and am now seeing that I did not do quite enough. If I am in the wrong place please direct me to a better one.
Here is my issue:
I have an LG g2 that I recently picked up used. Phone has never been rooted or worked on...until now. Decided I would spend my weekend working on it. Successfully rooted, and installed TWRP. Decided to flash a rom, downloaded my rom as I have always done, put it on the sdcard, made a couple of nandroids, and flashed it. Everything seemed ok, booted back up, got the correct boot animation, but it bootlooped. No big deal Im thinking, go back into recovery and wipe a couple times. Still wont boot. Go back in and restore my nandroids, and they wont boot either.
So now I am worried. Try it a coulple more times, and somehow get it to reboot to the setup screen. Wont go past there. Do the trick to avoid it and cant get it to activate. Double check everything, power off, wipe, power back on and now it wont even load to there. I tried sideloading a different rom as well as what seems to be the stock software and nothing. Im lost, I need help. Any advice?
skizzyp said:
Hi everyone,
I have been frequenting XDA for quite a while. Hugely into android and custom roms and things of the sort, but have never had a real reason to post. I have either been lucky enough to be able to find what I need by searching, or figured it out myself. This time however, I am pretty stumped.
I did a fair amount of research before starting this, and am now seeing that I did not do quite enough. If I am in the wrong place please direct me to a better one.
Here is my issue:
I have an LG g2 that I recently picked up used. Phone has never been rooted or worked on...until now. Decided I would spend my weekend working on it. Successfully rooted, and installed TWRP. Decided to flash a rom, downloaded my rom as I have always done, put it on the sdcard, made a couple of nandroids, and flashed it. Everything seemed ok, booted back up, got the correct boot animation, but it bootlooped. No big deal Im thinking, go back into recovery and wipe a couple times. Still wont boot. Go back in and restore my nandroids, and they wont boot either.
So now I am worried. Try it a coulple more times, and somehow get it to reboot to the setup screen. Wont go past there. Do the trick to avoid it and cant get it to activate. Double check everything, power off, wipe, power back on and now it wont even load to there. I tried sideloading a different rom as well as what seems to be the stock software and nothing. Im lost, I need help. Any advice?
Click to expand...
Click to collapse
would really like someone to chime in...running linux.
Bump. Can anyone give me any advice?
skizzyp said:
Bump. Can anyone give me any advice?
Click to expand...
Click to collapse
Sounds like you need to restock and start over. I'd give you links but how to do so varies by which version or carrier the phone is from.
Hi guys I want to post my experience for future reference. Bought this phone (in Athens, Greece) because it's crazy value for money. After a week or so I was really satisfied with it. Just wanted some more Marshmallow features, like multiwindow. So I did my research and ended up following a related guide : steps-to-root-moto-e-2nd ge n. Everything went well, I unlocked the bootloader, flashed twrp, the phone rebooted and I chose to flash SD card as internal, and I was able to install my apps and settings. Then again following the guide steps I tried to flash SuperSU. This resulted to an endless bootloop, where the message " YOU HAVE UNLOCKED THE PHONE S BOOTLOADER....." kept showing up. So I started reading related post from many forums, most of them reproducing the same solutions, like "find your phone's official firmware and reflash". I downloaded many firmwares, all of them appeared (to me at least) suitable for my phone, but none of them had any result. The bootloop continued. I couldn't even flash ROMS from SD card, obviously because of the internal memory format I had done the first and only time the phone booted. Two days had passed and I was really frustrated, ready to take it to service ( or throw it against the wall). Until now I didn't want anything else but the official firmware. But what the heck, after so much efforts, anger and disappointment there is nothing wrong in trying new things. So when I came across the guide about installing cyanogen 13 on my phone, I decided to give it a try. TOTAL SUCCESS!!!! Now my phone is really "flying", is really fast and the most important: is really working again. Although I went through a second flashing of cyanogen 13 because I had the lame persisting idea to flash SuperSU again, with the same frustrating results. So the bottom line, and the reason for this post is : do not flash SuperSU on this phone because you will soft brick it, and don't get caught up with a "hunt" for the right firmware, you will only loose time and some sanity. This is my advice: Go ahead and install cyanogen, it is really great and has insane features. Big thanks to all the guys developing and contributing, you really saved me big time!!!!
vagfyt said:
Hi guys I want to post my experience for future reference. Bought this phone (in Athens, Greece) because it's crazy value for money. After a week or so I was really satisfied with it. Just wanted some more Marshmallow features, like multiwindow. So I did my research and ended up following a related guide : steps-to-root-moto-e-2nd ge n. Everything went well, I unlocked the bootloader, flashed twrp, the phone rebooted and I chose to flash SD card as internal, and I was able to install my apps and settings. Then again following the guide steps I tried to flash SuperSU. This resulted to an endless bootloop, where the message " YOU HAVE UNLOCKED THE PHONE S BOOTLOADER....." kept showing up. So I started reading related post from many forums, most of them reproducing the same solutions, like "find your phone's official firmware and reflash". I downloaded many firmwares, all of them appeared (to me at least) suitable for my phone, but none of them had any result. The bootloop continued. I couldn't even flash ROMS from SD card, obviously because of the internal memory format I had done the first and only time the phone booted. Two days had passed and I was really frustrated, ready to take it to service ( or throw it against the wall). Until now I didn't want anything else but the official firmware. But what the heck, after so much efforts, anger and disappointment there is nothing wrong in trying new things. So when I came across the guide about installing cyanogen 13 on my phone, I decided to give it a try. TOTAL SUCCESS!!!! Now my phone is really "flying", is really fast and the most important: is really working again. Although I went through a second flashing of cyanogen 13 because I had the lame persisting idea to flash SuperSU again, with the same frustrating results. So the bottom line, and the reason for this post is : do not flash SuperSU on this phone because you will soft brick it, and don't get caught up with a "hunt" for the right firmware, you will only loose time and some sanity. This is my advice: Go ahead and install cyanogen, it is really great and has insane features. Big thanks to all the guys developing and contributing, you really saved me big time!!!!
Click to expand...
Click to collapse
There's an issue with SuperSU when it tries to install in systemless mode.
Flashing it this way seems to do the trick, and has been confirmed by multiple users on this board: http://androiding.how/root-moto-g-2014-marshmallow/
If you're using CM13, there is no need to flash SuperSU. CM13 has its own root pre-installed, you can turn it on in Developer Options.