First off I'd like to apologize to Boushh and everyone else for having to post this here and not in the actual rom thread, but rules are rules and being a lurker has its drawl backs.
Anyway, I installed the rom/kernel/gapps as per instructions. Everything worked great. No real issues. Then I tried to switch from 3g over to WiFi and kept getting errors. So I decided to reboot and thats when the fun started. I'll try to describe what happened next. The setup screen appeared in the background but had a metric ton of FC windows over top of it. I clicked through them... all. Fairly sure it was every single .apk that I have installed on the tab atm. Managed to get to the home screen, with FCs all the way through. Then I decided that it would be a great idea just to re-flash the whole package. Which has fixed problems like this on other devices that I own, but now I'm stuck in a boot loop. Not 100% sure what to do .. and due to overconfidence(stupidity) I didnt backup the stock rom.
Not 100% sure what to do from here, any advice would be greatly appreciated.
Related
Has anyone ever ran into a situation where the UI locks up after a boot? I keep searching through threads and can't find anything. I'm not sure if it's something I have installed or if there is actually something wrong with the device. I had a nook previously and never encountered this problem but on the new one I just got (ebay refurb) the problem just keeps coming back.
Basically, it boots just fine and starts to show the Launcher but then the screen goes black and leaves the soft buttons at the bottom. The only way to recover is to shut it down and start it back up.
The funny thing is it doesn't do it all the time... sometimes it boots just fine and never locks up while in the OS... it's only on boot it does this.
I've tried multiple different versions of cm7 and am getting the same thing on all versions. I've tried different kernels and stock speeds and it still happens.
Any help or advice would be appreciated!
Hmmm... well after hours of troubleshooting I think I pinpointed it to beautiful widgets
Sharing time!!
I did something quite stupid today and, in the interest of both comedy and warning, want to share it with the world.
In my rooted glory I began to think back to the V6 supercharger script that my Droid1 loved so much.
Long story short it did not do well on my droid and I ended up with a boot loop at the "Droid" soundbite. Hard to hide your mistakes when your phone is screaming every 5 seconds. All of the boot loop fixes failed.
Factory reset cleared up the boot loop but thanks to some .apk cleaning I am now stuck with no home screen. Installing a home screen replacement has not helped yet, but at least I have adb and still have root so some .apk moving from the backup directory should get me running in an hour or so.
Feel free to laugh knowing I have been hacking phones since my old xv6800. Also make sure you know the risks when you play with the file system on your phone.
Thanks mate, I feel for you. Yesterday I tried to update my Droid to 5.6.890 but first I had to Unroot it with Petes Motorola Root Tools and restore the /system/app folder. Unfortunately I left the downloaded apk zip in the restore folder which has been also restored to /system/app.
Then bootloop. And drooooooooooooid, drooooooooooooooid, droiiiiiiiiiiiiiiiiiiid. ^^
I had to manually root it, this thread helped http://forum.xda-developers.com/showthread.php?t=1236465
Then I restored /system/app again, but correctly this time.
Finally I could start the update and everything was working again...
Anyone who has a bricked DROID 3 phone (Verizon only), I may have a solution for you.
Requirements:
Windows platform
7-zip installed (and know how to extract files)
ability to follow all instructions exactly
willingness to factory reset/lose data on their phone
This unbrick method is NOT guaranteed to work, but it's very hopeful for most situations where other methods aren't working. If you are in desperate need of a fix, send me a PM and I'll link you some files to try.
Lastly: I will not be walking through anyone step by step on how to run this procedure -- the included instructions should be more than enough for most people. If you read the instructions and are thoroughly confused, then this fix isn't for you.
Almost back up and running now. Thankfully Marketplace pushed some apps and then notified me about it so I could open up the marketplace and install ADW. Once I got home back it was just a matter of reinstalling and rebuilding.
Oddly my Social Networking widget is no longer working correctly. A shame but only a minor issue overall.
Oddly the bootloop fix instructions you listed did not work for me. ./adb devices showed an entry but no info and told me I did not have any permissions on the device. I am running on Linux so it may have been a driver issue of some kind.
I'm sure what happened to the damn thing the other day, but.
I put my phone into Sleep Mode during a morning of hunting and when I tried to wake it back up it wouldn't respond. It had actually done this before, so I wasn't too concerned. It seems to be an issue with the leaked OTA.
So I pulled the battery, powered it back on, and stuffed it back in my pocket and drove 20 minutes back home. When I tried to check it afterwords it wouldn't wake up again; stuck at black screen.
Pulled the battery again, powered on and waited... and waited... and waited. After several minutes it would reboot again.
Sooo I plugged it into my computer and started to try to figure out what the hell happened. The logcat gave me no good indication as to what might be the issue, it just seemed to hang right after booting.
I deleted my replacement home (Launcher Pro) and that got me a little further. It would boot to the lock screen! But it would never respond to my inputs.
I resorted all system apps. Same thing, not responding, stuck on lock-screen in airplane mode.
I unrooted then re-installed the OTA leak. No change.
So I finally caved and decided to try a factory reset, which if failed, could almost totally screw me out of ADB access or worse.
But thankfully it totally worked! It booted right up and I was able to complete every setup screen without issue. Rooted, Titanium restored my apps and a pinch of data and I was back in business in 30 minutes!
Now I make sure that I never put the phone into Sleep Mode.
So hey guys, I just want to start off by saying that I really appreciate your help in this because I really messed up and keep in mind that this is my first Android device and I'm currently a total noob.
So my problem has a back story and here goes. So i decided that i wanted to root my phone and try to put CyanogenMod on it to get a somewhat similar experience to stock Android. So i used a YouTube video and successfully rooted my phone. After i rooted it i found out that CyanogenMod didn't have a stable or RC release for my AT&T HTC One so i decided i should unroot it and so i got the RUU_M7_UL_JB_50_Cingular.exe file from another YouTube video and everything was going fine until the installer said that i have an error and the installer closed down, and now I'm left with a black screen with an HTC logo and four caution indicators in the four corners. I tired to shut down the phone nothing happens, I tired to hard reset it and nothing happened the same screen stayed up. I was hoping that someone on this forum could help me cause you guys are my last resort.
Thanks in advance for any help, it means a lot.
Found a solution please close the post.
Hello,
This is my first time posting here, and I would like to request anyone on here to please assist me with the problem I am currently facing. I bought an unlocked, rooted HTC One with stock Android 4.3 installed as it's sole, primary OS this past summer. The person I bought it from is the one who actually rooted the phone, as my knowledge of such processes is fairly limited. I understand there are plenty of complications that I may run into dealing with this problem on my own and technical references may be lost on me, but I'm fairly competent enough to follow instructions from someone who may be able to help.
Here's the problem: I received an Android 4.4 OS update yesterday, which downloaded automatically and asked me if I wanted to install it. I thought the process would be fairly simple and I would not encounter any problems. However, when I asked the update to register and install, first it went into boot (I'm not certain which software was used for root), then the process started and everything seemed to be going fine until 'Patching files onto the whatever' came up and then it appeared that I encountered an error and the phone automatically went into what I can only assume is the bootloader menu? There were big Stock Android looking buttons on it which said things like Install, Root, Settings and a few others I don't recall. I tried to hit Install to see what happened and it brought me back to the part where 4.4 was supposed to be installed and I could read the error message at the end of it which said something like 'Error in patching files to zip folder or something', and I went back to the supposed bootloader menu. Confused and afraid, I think I pressed a button which I felt would allow me to reboot my phone and bring me back to my original 4.3 OS and that I would still be able to use my phone. First it said something like 'You no longer have root permissions', and there was an option where I could slide to apparently 'fix this', but I selected the 'don't fix' option as I obviously had no idea what I was doing. After this, the phone attempted to reboot, and a turquoise blue screen with strange markings came up on it and my phone hung. I killed the phone with the master power button and held it to switch off the phone.
BUT now, even since that has happened, my phone appears to be dead. It isn't starting up. When I put it on charge, the red LED doesn't show up. I have tried to used several ways to turn on my phone but it just wouldn't work.
I would like some light to be shed on this particular problem, and if anyone has experienced something similar to this, PLEASE, help me in fixing this. I am an eager learner and despite my limited, close to non-existent knowledge about dealing with a phone's OS, I know I can learn fast and follow instructions cleanly.
Please help me. Thank you.
To the admins I apologize if this is in the wrong section if it is please move it accordingly.
Hello everyone, I have an issue, hopefully someone can hel me and it starts like this. I and everyone else have been waiting for months for a safe root method and a recovery system such as TWRP OR CWM just incase I fudge something up flashing custom roms so I can always go back to stock. I came across a safestrap article and decided it was something similar to what I was looking for. So I decided to root using the big K. I know not the best choice, you can boo me now.
After a successful root, I installed safestrap. Unfortunately safestrap kept crashing upon starting the app, I couldnt even get it to set up. thats fine, I was just going to unroot and keep on living life, but then I stumbled upon Xposed installer, that modified and tweaked like a custom rom but without all the risk according to a website. I said hey thats worth a try and I did. After the Xposed installer setup and a reboot, I wad looking for mods on the web and all of a sudden my apps and system files started crashing to the point that I could not use my phone. I immedeately uninstalled Xposed installer ss soon ad my phone stabalized and unrooted.
I thought everything was good, 4 hours later the apps and system files started crashing again, so I did a reboot and I noticed that custom with the lock came up on intial startup. though I was told I was unrooted by the K program and even double checked using a rootchecker app, which stated I had indeed an unrooted phone. I did another reboot and no custom or logo came out. At this point I just wanted a working phone and As much as I hated doing so I did a factory reset. This seemed to have fixed the problem, but 4 days later my phone randomly went into a bootloop. I couldnt get it to stop so I took out the battery and that did not fix it.It was strange becuase I thought it might have been unrelated since it wasnt doing this when I had the issue with Xposed installer.
After yet another factory reset my phone seems to be fine, its still too early to tell though since its only been about a day. I had the normal google playstore and gvoice app crashing...Sigh..the only thing different was that sometime yesterday after the second factory reset a notification popup of unfortunately a sytem file stopped working came up. I acknowledged it, but thankfully I havent gotten any problems. I forgot what the notification read. hopefully its not related to what happened the other day.I dont know if this is related to one another, but I did notice that before I rooted my android system had automatically upgraded. I looked for issues like this on the net and saw people where having random bootloops after system upgrades and that unchecking scanning for wifi fixed the problem. though I did this and it did not work, thats why I did the second factory reset.
Now Im asking for help if any further issues arise. I love my Note3 and at this point I just want a reliable working device. Im keeping my fingers crossed and hopefully that will be the end of it, but in case it started to act up again, what can I do? any information and help is greatly appreciated. thanks.
Never uninstall any Xposed app that changes system files without first reverting any changes you made with it. Some of them are permanent until they are turned off in the App. Then you can disable the module.
You may want to look into this http://forum.xda-developers.com/showthread.php?t=2559715
I cannot stress this enough.
READ READ READ.
Too many times have I seen someone read a line or 2 then rush right in ultimately turning their very nice phone into the most expensive paperweight one could own.
On that link I posted, read it until your eyes are bleeding if you truly need to start from scratch.
I am not joking here.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Thanks man. it makes sense. I will look into it. you mentioned read. I have read what I thought was plenty, but always ideas and opinions differ, sometimes knowing too much and causing what they say decision paralysis. Because I still read about the Xposed experiences and different people go about it in a different way. but what you mentioned about reverting back makes alot of sense.