Database Users

[Q] tf300t bootloop

hi everybody,
i have a strange situation. i am running cromxi 5.1.1 with kernel _thatv5. this i have already flashed a while ago, and everything was working perfectly (so i assume, i have done everything correct while wiping and flashing...).
but today when i startet my tab, it got a bootloop. at the end it says something like 'android is updated and apps are startet', but then starts booting from the beginning. unfortunately i cannot enter the bootloader menu with pressing the vol up key.
does anybody has an idea what went wrong?
as i said, it was working perfectly until today and i did not install any strange new apps...

koszmann said:
hi everybody,
i have a strange situation. i am running cromxi 5.1.1 with kernel _thatv5. this i have already flashed a while ago, and everything was working perfectly (so i assume, i have done everything correct while wiping and flashing...).
but today when i startet my tab, it got a bootloop. at the end it says something like 'android is updated and apps are startet', but then starts booting from the beginning. unfortunately i cannot enter the bootloader menu with pressing the vol up key.
does anybody has an idea what went wrong?
as i said, it was working perfectly until today and i did not install any strange new apps...
Click to expand...
Click to collapse
i mean the vol down key...

koszmann said:
i mean the vol down key...
Click to expand...
Click to collapse
So did you flash a new ROM today, or did it just stop working?
Sent from my TF300T using xda app-developers app

cmendonc2 said:
So did you flash a new ROM today, or did it just stop working?
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
no, i flashed it when it was released, before that, i was already running the previous versions of cromix.
so far without problems. today it stopped working.
i now managed to get into bootloader menu (took me quite a while...). i wiped everything and installed cromix5.1.1 from scratch. worked until all apps were installed and updated, then the same problem appeared again... i will try now to figure out, which app is responsible...

koszmann said:
no, i flashed it when it was released, before that, i was already running the previous versions of cromix.
so far without problems. today it stopped working.
i now managed to get into bootloader menu (took me quite a while...). i wiped everything and installed cromix5.1.1 from scratch. worked until all apps were installed and updated, then the same problem appeared again... i will try now to figure out, which app is responsible...
Click to expand...
Click to collapse
If you are using TI, make sure you dont restore system data. that usually ends in complications for me

koszmann said:
hi everybody,
i have a strange situation. i am running cromxi 5.1.1 with kernel _thatv5. this i have already flashed a while ago, and everything was working perfectly (so i assume, i have done everything correct while wiping and flashing...).
but today when i startet my tab, it got a bootloop. at the end it says something like 'android is updated and apps are startet', but then starts booting from the beginning. unfortunately i cannot enter the bootloader menu with pressing the vol up key.
does anybody has an idea what went wrong?
as i said, it was working perfectly until today and i did not install any strange new apps...
Click to expand...
Click to collapse
If you are constantly getting "Android is upgrading... Optimizing app __ of ___," you should try flashing an updated CROMi-X 5.1.1 ROM from this post http://forum.xda-developers.com/showpost.php?p=46957469&postcount=883
It's updated to fix the "Android is upgrading... on every boot" issue that was reported by some users. But, if you were using the Deodex version, then you might have a different issue and don't need this update.
And yes, I would also recommend clean install with "Wipe Dalvik & Cache" when installing CROMi-X 5.1.1. Weird and unexpected problems can sometimes occur when doing dirty flashing. Good luck :good:

After my first upgrading attempt (5.1 << 5.1.1) I've had the same issue. So I did a clean re-install (wipe cache + davlik) good luck.

yes, u have to do clean reinstall. if not it will stuck at bootloop again.

[Q] Nexus 4 updated to Kit Kat via OTA and got looped on boot

Hi, this is my first post here. I'm new into Android and I've always updated my Nexus 4 when the system prompts me to do it. Today, I got the notification to update from 4.3 to 4.4... I did it and restarted my phone. Then I got (and have been) stuck on the boot sequence after the Google logo. The thing is that I've tried to wipe and restart the phone by Bootloader (I don't know if I lost all of my files) and didn't work out. So now I'm trying with Nexus Root Toolkit but I don't know if that will work. I'm really needing some help, here in Venezuela not so many people have this cellphone and I really don't know how to proceed. I'm upset with Google for these kind of fails, my phone was working 100% good. Please help me! Sorry if my english is not so perfect.

I did experience the same.
Never rooted or unlocked bootloader & I was patiently waiting for OTA. It came and it was the worst thing to happen! Infinite bootloop!
I waited 2 hours, before I restarted the phone, but in vain. No use!
I never enabled debug settings, so i couldn't use ADB command and it wasn't recognizing my device!
Here is what worked for me:
1. Unlock bootloader (using fastboot command)
2. use fastboot to flash the factory image
3. I did remove (-w) wipe option, but still lost my data.
however image works, now phone is back to life!

Same case, nothing works.

I had the same problem, go stuck on a boot loop and then it just said 'no command' or 'error' with an android lying down. Im a noob so i used ncry toolkit to reset it to factory 4.3 and then i upgraded to 4.4 again and all worked fine. Did lose data though, but i had it all backed up.

Do a clean flash of KitKat via fastboot.

Similar Situation
Chidvilas said:
I did experience the same.
Never rooted or unlocked bootloader & I was patiently waiting for OTA. It came and it was the worst thing to happen! Infinite bootloop!
I waited 2 hours, before I restarted the phone, but in vain. No use!
I never enabled debug settings, so i couldn't use ADB command and it wasn't recognizing my device!
Here is what worked for me:
1. Unlock bootloader (using fastboot command)
2. use fastboot to flash the factory image
3. I did remove (-w) wipe option, but still lost my data.
however image works, now phone is back to life!
Click to expand...
Click to collapse
I'm in the same situation as most... Sadly I updated via the OTA distro that was released a few days ago. I looked into rooting options and I got the "go ahead" from a thread somewhere, saying it is a minor update. Knowing how easy it was to restore root priveliges when I upgraded from 4.2 to 4.3, I trusted their encouragement and installed the update. Then, like everyone else, I got stuck in the bootloop at the "circles" screen.
As a last resort, I tried to factory reset to no avail. I cleared the dalvik cache and wiped the cache partition a few times... Then I tried restoring it to factory defaults, again! Same results every time. Unfortunately, because of where it gets hung up, I can't seem to get my computer to talk to it. I certainly can't access the SD Card to do any backing up, but can look at the contents through CWM recovery mode (v6.0.2.3).
It's been awhile since I last was active in flashing my phone, so while I no longer consider myself a noob, I am definitely back to being a beginner. The fastboot commands don't seem to work, as I get stuck at "<waiting for device>". Does anyone know if there is a way to force it into a drive mode? Any additional help with this matter would be greatly appreciated, as currently it seems Google has bricked my phone!
Last question, it looks like it may be possible to force a mount through CWM; is that true using the "mounts and storage" menu? I spoke to Google briefly and they were of no help (they just told me to call LG). I'm going to try going into the T-Mobile store and seeing what they will say, but I'm not holding my breath for them to come up with a solution; I'm relying on the community to help me out!
STATS:
Bootloader: MAKOZ20i
HW Version: rev_11
Secure Boot: enabled
Lock State: unlocked
CWM: v6.0.2.3
Computer OS: Linux-Ubuntu 13.4
---------- Post added at 03:48 PM ---------- Previous post was at 03:39 PM ----------
NissanskylineN1 said:
Do a clean flash of KitKat via fastboot.
Click to expand...
Click to collapse
Sorry to sound so dumb, but can you point me in the right direction to find instructions on how to do that with Linux?

http://forum.xda-developers.com/showthread.php?t=2302780
Its actually way easier to set it up on Linux than on windows.
Edit: java jdk6 was giving me issues on install so I used openjdk instead and it works perfect.
Edit: (last one, I promise), I don't know how new you are to Linux but if you are super new, anytime that guide mentions "code" in a box, copy and paste one line at a time into the terminal. Leave out the dollar signs when copying.
AMarted said:
I'm in the same situation as most... Sadly I updated via the OTA distro that was released a few days ago. I looked into rooting options and I got the "go ahead" from a thread somewhere, saying it is a minor update. Knowing how easy it was to restore root priveliges when I upgraded from 4.2 to 4.3, I trusted their encouragement and installed the update. Then, like everyone else, I got stuck in the bootloop at the "circles" screen.
As a last resort, I tried to factory reset to no avail. I cleared the dalvik cache and wiped the cache partition a few times... Then I tried restoring it to factory defaults, again! Same results every time. Unfortunately, because of where it gets hung up, I can't seem to get my computer to talk to it. I certainly can't access the SD Card to do any backing up, but can look at the contents through CWM recovery mode (v6.0.2.3).
It's been awhile since I last was active in flashing my phone, so while I no longer consider myself a noob, I am definitely back to being a beginner. The fastboot commands don't seem to work, as I get stuck at "<waiting for device>". Does anyone know if there is a way to force it into a drive mode? Any additional help with this matter would be greatly appreciated, as currently it seems Google has bricked my phone!
Last question, it looks like it may be possible to force a mount through CWM; is that true using the "mounts and storage" menu? I spoke to Google briefly and they were of no help (they just told me to call LG). I'm going to try going into the T-Mobile store and seeing what they will say, but I'm not holding my breath for them to come up with a solution; I'm relying on the community to help me out!
STATS:
Bootloader: MAKOZ20i
HW Version: rev_11
Secure Boot: enabled
Lock State: unlocked
CWM: v6.0.2.3
Computer OS: Linux-Ubuntu 13.4
---------- Post added at 03:48 PM ---------- Previous post was at 03:39 PM ----------
Sorry to sound so dumb, but can you point me in the right direction to find instructions on how to do that with Linux?
Click to expand...
Click to collapse

[Q] Boot loop after upgrading Nexus 4 to 5.1

I recently got 5.1 update on my nexus 4. But after the update I am experiencing boot loop issue on my phone. This is a stock image and un-rooted phone which is out of warranty.
The phone was stuck in a 'Starting apps' message after the 'optimizing apps' for close to 3 hours. I rebooted the phone and was able to boot into 5.1 once.
I could not get a network and I restarted my phone. Since then, I have never been able to complete the full boot even once.
It either gets stuck in the animation of the 4 balls moving, or the 'optimizing apps' stage or the 'starting apps stage'.
I searched the internet and tried some solutions given by people who were facing a similar issue. But nothing seems to be working for me.
Solutions tried:
1) I rebooted into recovery mode and wiped the cache multiple times.
2) I rebooted into recovery mode and did a factory reset hoping that some apps which was causing issue optimizing/starting would be deleted.
3) I flashed a 5.1 as well as 5.0.1, 4.4.4 image using the NRT in the 'Soft-brick' mode. I faced the same issue with the loop. I can't get a adb connection to work since the developer options is not enabled I believe.
I cannot even find out which app is causing the issue as well since I don't get any logs during the boot. But I thought a factory reset should handle this problem.
I have already lost data since I didnt have a full backup. At this point, I just want to get my nexus back.
Please Help!!!

Ican understand how you must feel It looks like you have done everything. The only suggestion I can make that might help is seek out the SkipSoft Android Tool Kit. It will allow you to restore your nexus so check it out
https://www.google.com/url?sa=t&rct...=z2XaCTV2HIaBSAHTninuig&bvm=bv.91665533,d.b2w
I hope that helps you... I have used it successfully many time.

Thanks for your reply.
Is there any particular option on the toolkit I should be using to restore my Nexus? Or I should just try re-flashing stock firmware using the mentioned tool kit?

rajath575 said:
Thanks for your reply.
Is there any particular option on the toolkit I should be using to restore my Nexus? Or I should just try re-flashing stock firmware using the mentioned tool kit?
Click to expand...
Click to collapse
I would plug your Nexus 4 in via USB port
Select your device type Nexus 4 option 02
Then go to the next step and select the build number that you want to start
---------- Post added at 01:25 PM ---------- Previous post was at 01:23 PM ----------
Blacksmith5 said:
I would plug your Nexus 4 in via USB port
Select your device type Nexus 4 option 02
Then go to the next step and select the build number that you want to start
Click to expand...
Click to collapse
The SkipSoft tool kit will guide you through the whole process
skipsoft.net

Massive softbrick (haven't found a solution yet)

Hello everyone,
So here's my story: I got a 6P short after release and it's been amazing. After switching from a S6 I couldn't be happier until 3 days ago.
I was playing around with my phone (checking for updates on the play store if I recall correctly) and I was going to switch from 4g to wifi. I went ahead and pulled down my notification shade and went to press WiFi but misclicked and hit Hotspot which was below it. My phone suddenly froze big time and this is for the first time ever since purchase.
At first I thought I'd wait it out since the device was completely unresponsive, home button didn't work and neither did anything on screen. Buttons didn't make a difference either. 10 minutes went by and I ended up force restarting by holding down power + volume up. First part of my bootup went fine but when it got to the android boot animation after I put in my pin to allow the device to start it dropped from the smooth usual framerate down to 1 frame every 10-15 seconds and it slowed down further until it came to a complete halt around the time the android letters appear.
My first thought was corrupt rom so I went ahead and wiped data from the stock recovery. I was running completely stock with no modifications whatsoever. That didn't do anything. Phone still froze in the same boot phase. Desperate I unlocked bootloader to flash a clean fresh image to try to fix it and to my surprise that didn't change a thing.
As I was getting pretty desperate already I had one more idea and that was to flash up to the Dev preview. To my huge surprise it booted and I jumped from excitement. So I started setting up my phone again. I got past the prompt to insert sim card and I was now at the screen to choose a wifi network. As soon as I clicked into that the phone froze up again and at that point I lost all hope.
I wiped data in stock recovery and shut the phone down for the night. On day 3, today I woke up and tried starting the phone and it worked as if nothing had happened. I went through the setup and set up my phone on the N preview. At a certain point I was planning to go back to the latest official build but for now I was happy my phone was back from the dead. Later today I tried to restart my phone to clear all running apps etc and it froze up on boot.
I'm losing all hope that I'll be resolving this myself so I'm reaching out to the community to see if anyone's had this happen to them before and hopefuly for a solution. It's still under warranty so I can eventually send it back to the retailer but I'd rather not have a phone for 3 weeks.
Any and all help is appreciated.
Thank you for reading through my long and probably pretty boring story!

Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?

To the OP, is there any reason you did not flash to release version 6 instead of Dev preview ?
Also, any reason you can not simply do the "unenroll" from https://www.google.com/android/beta ?
It will require you to setup certain settings again as you will be back to a "factory reset".

DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
DJBhardwaj, i haven't specifically erased those partitions. I was under the impression wipe userdata along with reflashing did that. I will try that tonight when I get home!
Xdafly, I only updated up to N as a last resort because at first I had a locked BL. I was planning to unenrol but that would've been too late as it self bricked after a restart.

DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
Well I just did the erase thingy and my phone booted but wifi won't turn on. Enabling hotspot doesn't brick anymore but I now suspect WiFi might've been the issue. Any tips on how to find out what it could be and possibly fix it?
Edit: 2 restarts and a factory reset later I'm back to bricked same way as before.

try safe mode

mr.dj26 said:
try safe mode
Click to expand...
Click to collapse
That was my first thought, that was the restart that bricked it again. Safe mode shouldn't have made a difference since I hadn't even logged into Google account for apps.

After reading the very first post; sounds like bad WiFi hardware.
All the hanging has been related to WiFi or Hotspot.

I think you should get a replacement
Sent from my Purified NexusixP
If Someone Helped You Then Dont Just say Thanks...Hit The Thanks Button!

Is your phone rooted and did you install Xposed?
Over the weekend I shutdown my 6p (stock rooted with April security patch, Xposed v80) and charged it. When it turned it back up I kept getting "Unfortunately, nfc service has stopped". Long story short: I ended up factory reset my phone and reinstalled EVERYTHING and I still got into bootloop. Then I came across
https://github.com/rovo89/Xposed/issues/113
https://github.com/rovo89/android_art/issues/28
At the end of the second post rovo89 (developer of Xposed) fixed the bug in V83. I wiped my 6p once more and installed everything with v83. Problem solved.
Good luck!

Rooted for a few weeks -- rebooted and stuck on T-Mobile Screen + Random Vibration

Hello all! This is the second time this has happened to me, I've rooted my phone for about a week, and then for some reason when I decide to restart my phone -- it no longer boots up. It is stuck at the t-mobile screen and vibrates for a bit then stops, I have booted in to recovery mode and tried wiping that cache, but to no avail.
Any help would be appreciated -- or even how I can backup my data would be great too.

Wah gwan! My T-Mobile S7 Edge running TekHD v2. To have your phone running very nicely, you need to download the APD8 fireware. Make sure everything on your phone running APD8. download the files from max on highonandroid, flash the tar file twice using modified Odin from max. Once boot up screen say custom, next step download and extract TekHD.rar file .there's a part in the file that operates like cmd, right click and let it do its thing. Make sure your phone is on and a low USB debugging.
---------- Post added at 10:09 PM ---------- Previous post was at 09:43 PM ----------
Also this TekHD Rom is best for unlimited hotspot for Windows, Android and Mac. I have download about 20 more GB of files to make sure its good. The tutorial from max is good, the easiest way I see so far is to click on the root.dat in max files to add superSU. For TekHD click tekhd.bat. That was the easiest way after flashing the tar file. The hold process take 2 minutes once done right. I'm not a developer but a big Samsung Android fan. I have a Note 3,4,5 S6 Edge+ and S7Edge, I tried and tested many Roms at my own risk. Never had any problems. Make sure you always have the stock rom tar file for your device before any flashing any roms, is case something goes wrong you can start over.

first of all this is an eng boot root, so expect some hiccups and proble.. before u root make sure u back up everything then odin back to stock then root or else u will run into problems

You're going to have to ODIN back to stock. This seems to be happening to a lot of people (myself included) and a stock flash is the only way anyone has been able to recover. Flash all 4 files in ODIN simultaneously, but if you don't have a backup, try flashing the Home_CSC and see if it'll boot. I've heard reports that the Home-CSC file doesn't wipe your phone. If that doesn't work, then unfortunately you're going to have to re-flash, but this time use the standard CSC file, which will wipe your phone. Good luck.

I just had this happen for my second time and was stuck phoneless out of the house :/ I wish we could figure out the cause... Not sure if related, but my recovery has red text on the bottom "dm-verity verification failed"

ph00ky said:
Not sure if related, but my recovery has red text on the bottom "dm-verity verification failed"
Click to expand...
Click to collapse
No, that is not related, dm-verity verification fails because recovery still checks dm-verity even though the kernel does not.

Damn same thing just happened to me at work. Had to do factory reset...
When at that tmobile screen, hold down volume down + home button + power. It will reboot,and as soon as it does, switch volume down to vol up until it loads recovery to reset

This happened to me also. Go to lockscreen and security options and disable automatic security updates.

I think it could be new firmware update from Google. I tried to install TekHD Rom after update to the newest APG1. And it hapened to me also. Stuck on Samsung screen with random weird vibrations.

I can almost certainly say that the vibrate crash has something to do with the phone installing something behind the scenes. After getting the Amazon/Google/Samsung services multiple crash followed by the reset to the vibrating T-mobile screen I did a non-wipe ODIN, which works and works perfectly. What seems to not work though is re-installing root, it just leads back to the same screen, so I think Samsung is pushing something sneaky onto our phones probably through the security thing as mentioned.
---------- Post added at 01:41 PM ---------- Previous post was at 01:40 PM ----------
pawel30w said:
I think it could be new firmware update from Google. I tried to install TekHD Rom after update to the newest APG1. And it hapened to me also. Stuck on Samsung screen with random weird vibrations.
Click to expand...
Click to collapse
TekHD Only works on PD8, it's mentioned in the thread.

pawel30w said:
I think it could be new firmware update from Google. I tried to install TekHD Rom after update to the newest APG1. And it hapened to me also. Stuck on Samsung screen with random weird vibrations.
Click to expand...
Click to collapse
Can't run that ROM on APG1. If you want to try it, you will have to ODIN PD8. There is a post in a thread in this section that shows how.

I just had this same thing happen on PG1. Using ODIN with all of the various parts and Home_CSC got me back in without having to wipe and everything survived. Going to try and re-root with the engineering boot image now that I made a decent backup. Would be great if someone smarter than me figures out what is updating/changing and causing this problem.

I said it on page 1: In settings, go to lockscreen, then security options and disable automatic security updates.

rp3 said:
I said it on page 1: In settings, go to lockscreen, then security options and disable automatic security updates.
Click to expand...
Click to collapse
That might work to prevent this problem -- but what needs to be reverted once this problem starts? I can flash stock PG1 and if I use the (home_csc) it will fix the problem and not wipe my data.... but if I reflash the engineering bootloader it goes back to hanging at the tmobile screen.

im stuck on tmobile screen, and it keeps vibrating, idk what to do

swaggyyd said:
im stuck on tmobile screen, and it keeps vibrating, idk what to do
Click to expand...
Click to collapse
I haven't rooted but if your stuck just Odin back to stock.

I came to post that I'm having these issues as well, this is the second time it's happened to me.
The first time I had TEKHD on my Phone, and so with it constantly nagging to do a system update.
I figured when it did this the first time, it was because the update ran over my TEKHD side load "ROM" and corrupted. Ok , whatever, reloaded.
But now I'm just rooted, and stock ROM otherwise. Just happened to me again
Each time it's happened, I start getting "playstore has crashed" errors - dismiss and it comes right back. So I reboot, and then it boot loops and gets CRAZY hot. Man I've never been able to fry an egg on a phone quite like my S7 Edge...
Is there any light shed on what could be doing this? I may have to remain stock which makes me want to :crying: but I can't keep bothering my Work Admin's to unlock my Token account so I can re-register my same phone -
I shall try that home_CSC Flash when I get home though, hopefully I can recover it at least in a way to transfer token to my tablet or something.

posted that at work, I'm at home now. I tried to flash just the home CSC and that did not work, just booted into recovery with an error and wouldn't resurrect at all.
I shall try that disable auto updates thing though and see if it helps in the long run...

wotan2525 said:
I just had this same thing happen on PG1. Using ODIN with all of the various parts and Home_CSC got me back in without having to wipe and everything survived. Going to try and re-root with the engineering boot image now that I made a decent backup. Would be great if someone smarter than me figures out what is updating/changing and causing this problem.
Click to expand...
Click to collapse
you got a link for the home csc file you can send me I was good for about a month and a half and it finally happened to me as well and can confirm I was getting the play store/ google services errors right before the reboot and tmobile screen

Was having this issue as well, forgot that I needed to turn off Security policy updates.