Database Users

[Q] 4.0.3 OTA Update Reboots shortly after startup.

Okay, I finally had time to update my A500 to ICS I was at 3.1 and was rooted. I went through several updates to get to ICS. 3.2, 3.2.1, a small patch, then 4.0.3. After the update finished, saying it was successful, my tab will reboot itself no longer than 30 seconds after it gets to the lock screen I don't have time to uninstall any apps that might be interfering with startup, not that i could tell whats doing it, and i don't have time to do the factory reset through the system menus Not sure why but the recovery (power&vol boot) only displays a red triangle over a dead droid so, guess my actual question is, how could i go about correcting this issue? I have ADB if needed, but I don't know were to start. any help would be appreciated. THANKS.
[Edit]
Okay, so I managed to turn off the wifi on my tab and it seems to stop restarting. When I do turn on the wifi, several apps give an error that they have stopped. after the second one pops up the tab then restarts unless the wifi is shut off. Any ideas as to what this may be would be appreciated.

Hi, sorry to say that i have the exact same problem.
Updated today from 3.2 to 4.0.3 and after first boot started the reboot sequence that only stopped after I managed to switch off the wifi...
I investigated a little but it seems this is quite an isolated issue... and all ways are leading to the factory reset...

StarCruiser said:
Hi, sorry to say that i have the exact same problem.
Updated today from 3.2 to 4.0.3 and after first boot started the reboot sequence that only stopped after I managed to switch off the wifi...
I investigated a little but it seems this is quite an isolated issue... and all ways are leading to the factory reset...
Click to expand...
Click to collapse
guess i'll give that a shot, i dont have much installed anyway...

Hi,
Got that problem too. Did a factory reset and it works fine now.
Sent from my HTC Desire HD using XDA

Here's on direct from Acer Support:
(of course us old dogs already know this trick)
Note: Clean boot will erase all the data/information which is saved on your tablet. Recommend you to back up the data before performing a clean boot. (yeah, like you can get in there to save it
1. Shutdown the power (press the power button for long time to shutdown).
2. Press and hold volume up key (the key next to rotation lock) until you finish step 4.
3. Press power button for 3 seconds until you feel device vibrates then release power button.
4. Once you feel device vibrates, very quick to switch on/off "rotation key" many times (this activity has to be done very fast, otherwise it will not success). To ensure you success, switch on/off rotation key when Acer logo appears on screen.
5. Wait for a while (you will see Erase Userdata and Erase Cache on top-left corner on screen), device will reboot and start from OOBE screen.

Managed to get it to work. Appreciate the help. Runs like a champ now.
Sent from my A500 using xda premium

[Q] My phone is dead on stock...(due to rooting/unlocked failure?) Please help!

Hello XDAers,
I am a real noob at rooting or android-related, and a true one voided of any knowledge regarding anything IT- related.
So dear veterans, please go easy on me.
Due to my prior success of rooting and flashing my Nexus 4 successfully a few months back with no issues, I decided to give it a try to flash a custom ROM for my dad's LG Optimus L7 - which seemed an easy task compared to configuring my Nexus 4 - since there was no need for inputting any command lines or any dealing with the abd (using the easy shortcut, that is).
So, I followed the guide here: http://forum.xda-developers.com/showthread.php?t=1906133 ...
I first factory resettled the phone because it was bloated, then applied the "RunMe.bat" from the "What you desire!" folder. (Everything was already backed-up beforehand.) But the process didn't success until I've retried again and again by re-plugging the USB in because the application/PC couldn't detect the phone. In the same time, I was running KDZ_FW_UPD.exe in the background, so unexpectedly for me the phone shut itself and pushed itself to a vividly green emergency screen, then in a few seconds switched back to a screen of purple-white-blue glitches. I had to close KDZ_FW_UPD.exe without knowing what quite happened since it seemed to be the cause and restarted the process with RunMe.bat.
I didn't manage to "Restore" it first due to the fact that the phone stopped responding due to a lag asking for an encryption key. It was lagging so hard and I had to close the cmd around 5 tries while it was processing, but succeeded later on.
And then, to verify whether I've actually suceeded in rooting L7, I installed Root Checker from the Play Store. And again, for the first few tries the program froze on screen for a long period of time due to "system performance", but after rebooting and restarting the app a few times again, the ROOTING proves to be a success. Just to be sure, around this time I've reloaded KDZ_FW_UPD.exe and it suceeded.
So I went to install CWM and ES. CWM for recovery boot and ES for removing pre-installed system apps as the phone was lagging so badly. I've downloaded the CWM restoring(something like ~6.0.28?) first and tried fastbooting immediately right after, but instead of getting the fastboot menu I got a screen emptied in black with these words:
[5020] "Secure booting error"
[5020] "Cause: boot certification verify"
No hard keys could do anything on the presumed "fastboot", and so I had to hard boot again. I thought that it might be due to the lack of memory(checked on ES later on that it was 310~MB/2GB), and so I've used ES to uninstall a lot of system apps which I deemed uneccessary. So I've Googled a bit and it became apparent to me that that I've didn't unlock the device properly, so lurked around and found a file called L7CWM that is supposedly to resolve my problem, but I presume that it's the CWM recovery image that I've installed. So in the end, I didn't bother with it but kept it on tab just in case.
I repeated the same process with CWM again, but this time, the screen was joined with all kinds of flowery glitches. Restarted the device, and it went only downhill: now the Home launcher stayed all pitch black and nothing appeared. I waited a few minutes, but nothing there until the notification bar appeared. The home screen is apparently dead, and so are the menu keys. Switched to Nova Launcher(installed it just in case Home Launcher fails), and still dead. I couldn't access using any of the menu keys and had unusable launchers.
Hopefully I could still access to the settings from my status bar, but when I did, it started crashing immediately.
I've repeated the attempt a few times after restarting the device a few times, but nothing helped. It only got worse that the when the launcher did SEEM to work. It only showed the wallpaper without showing any of the icons/apps. And crashes again.
I could still access to the App menu via the settings, but couldn't open any of them and when I tried to uninstall them, the screen frozes immediately right after I gain access to the page (white page though) and gain this message: "Unfortunately Package Uninstaller Stopped!"
Then I convinced myself that the only thing I could do at the time was to factory reset the phone and then everything would go alright since I've just had to restore the system apps.
But then the black screen of death came right along with it:
"Secure booting error"
It seems that I'm out of luck... ... But just to check if I'm still left with resorts, I've downloaded the L7CWM file online...
... ...but it still didn't help.
So now I'm being left with no other choices other than asking for help. I never really understand what KDZ_FW_UPD.exe does since I had the LG Driver already before installing it, which I presume was for updating the phone to a newer or older version. And too complex tech articles are kind of alien for me.
EDIT(1 hour later): Okay, now I figured out the reason why L7CWM didn't work was because I didn't extract it to the right folder (after double checked via notepad that I was supposed to directly put it into the C:\ drive). Now it worked(?), but then it didn't.
After launching Flash_Bootloader.bat:
This message now appeared on the L7:
"Sorry!"
"SuperSU is not responding.
Would you like to close it?"
"Wait - Report - Close"
and a few minutes later
"Sorry!"
"Unfortunately, SuperSU has stopped."
"Report - OK"
Now I think the bugs till now happened was due to the fact that I've deleted a file that was required for me to launch apps... Now I just need the right fix.
After 5 minutes of screen inactivity the phone restarted by itself, kind of creepy... ...
Flash_Recovery.bat did nothing.
Reboot2Recovery.bat made it reboot but still struck on the same menu.
Nothing seems to be effective via the phone anymore, seems like I have to rely on abd but then again I don't know how... ... My dad is also f*cking pissed off ^ ^;...
__________________________________
I think that I explained the logs pretty precisely in case I missed something... I'll be very very very very very very thankful if someone could tell me what has caused my phone to fail though.
For references, here are the phone's specifications:
Model Number: LG-P705g
Android version: 4.0.3 (Stock)
Rooted:Yes (root checker)
Baseband version: MSM7227A-1-AA
Kernel version: 3.0.8-perf
Build number: IML74K
Software version: V10e-AUG-10-2012
If I don't get the phone fixed to being usable soon I think that I will get butchered real hard... ... Preferably needs a step-by-step guide made for toddlers... ...

remove the battery for 10 seconds,put it back pres VOL+ and VOL - same time and than press the power button.when you feel a vibration press for many times the button wich is down in right,try for many times and maybe it will working :}

Cydes said:
Hello XDAers,
If I don't get the phone fixed to being usable soon I think that I will get butchered real hard... ... Preferably needs a step-by-step guide made for toddlers... ...
Click to expand...
Click to collapse
simple answer for your
just download your stock rom
go to emergency mode
and flash that stock rom

Phone boots to blue screen

My G2 suddenly just stopped working yesterday. When I try to power it on the phone either freezes shortly after the boot screen, gets to the homescreen then shuts off, or boots to an all blue screen. I can access TWRP but haven't been able to fix it with anything I've found. My pc isn't recognizing the phone so don't know if I can flash another rom. Also tried factory reset with no luck. Any help please this is driving me crazy!!!

The same thing just happened to me! Someone please help us! IS there a solution to this?

dsljk2009 said:
My G2 suddenly just stopped working yesterday. When I try to power it on the phone either freezes shortly after the boot screen, gets to the homescreen then shuts off, or boots to an all blue screen. I can access TWRP but haven't been able to fix it with anything I've found. My pc isn't recognizing the phone so don't know if I can flash another rom. Also tried factory reset with no luck. Any help please this is driving me crazy!!!
Click to expand...
Click to collapse
colbyrainey said:
The same thing just happened to me! Someone please help us! IS there a solution to this?
Click to expand...
Click to collapse
Ok, since there is little to no information out there I thought I would share how I created and fixed this problem.
I received a new phone under warranty because of a failing sim card reader. Naturally, the first thing I did once I received it was root it. Next, I thought I would be slick and use flashify to flash a custom recovery (TWRP). Little did I know, with the new version of Android, our phones have a locked bootloader. I freaked out when I saw some weird error messages about it and tried to power off the device in the middle of it booting. BIG MISTAKE. In hindsight, I am assuming that it was re-flashing the factory recovery when I powered it off.
It gave me a solid blue screen for two hours, unless I held the power button for 10 seconds, which would just repeat the process from black screen to solid blue screen repeatedly. I tried to reboot into recovery for 2 hours by holding volume down and power. 2 HOURS!
At that point, I realized that I may have some luck getting it into download mode by powering it off, then powering it on with volume up and power and plugging in a USB cable. VOILA! It booted up normally (somehow) and I got it running the OS.
After that, I made sure that I did a factory reset by reverting to stock using the LG Software Upgrade tool.
The moral of this story is, if you are going to try to install a custom recovery on 4.4.2, make sure you know what you're doing. It turns out an app called AutoRec did the trick for me.
dsljk2009 - I hope this message helps you, or anyone else who may think they've bricked their phones.
CHEERS LADS!
If this post helped you be sure to hit thanks!

colbyrainey said:
Ok, since there is little to no information out there I thought I would share how I created and fixed this problem.
I received a new phone under warranty because of a failing sim card reader. Naturally, the first thing I did once I received it was root it. Next, I thought I would be slick and use flashify to flash a custom recovery (TWRP). Little did I know, with the new version of Android, our phones have a locked bootloader. I freaked out when I saw some weird error messages about it and tried to power off the device in the middle of it booting. BIG MISTAKE. In hindsight, I am assuming that it was re-flashing the factory recovery when I powered it off.
It gave me a solid blue screen for two hours, unless I held the power button for 10 seconds, which would just repeat the process from black screen to solid blue screen repeatedly. I tried to reboot into recovery for 2 hours by holding volume down and power. 2 HOURS!
At that point, I realized that I may have some luck getting it into download mode by powering it off, then powering it on with volume up and power and plugging in a USB cable. VOILA! It booted up normally (somehow) and I got it running the OS.
After that, I made sure that I did a factory reset by reverting to stock using the LG Software Upgrade tool.
The moral of this story is, if you are going to try to install a custom recovery on 4.4.2, make sure you know what you're doing. It turns out an app called AutoRec did the trick for me.
dsljk2009 - I hope this message helps you, or anyone else who may think they've bricked their phones.
CHEERS LADS!
If this post helped you be sure to hit thanks!
Click to expand...
Click to collapse
Hey,
How did you power off your G2 before putting it into download mode? Im experiencing the same problem.
Please assist me.

jocyrus said:
Hey,
How did you power off your G2 before putting it into download mode? Im experiencing the same problem.
Please assist me.
Click to expand...
Click to collapse
I didn't get the blue screen but I kept getting the security error screen on my d802. To turn it off, I kept holding down the power button for about 10 seconds after the screen went blank. This caused the phone to remain powered off. After that, I was able to boot into download mode. Maybe this method will work for your phone.

audit13 said:
I didn't get the blue screen but I kept getting the security error screen on my d802. To turn it off, I kept holding down the power button for about 10 seconds after the screen went blank. This caused the phone to remain powered off. After that, I was able to boot into download mode. Maybe this method will work for your phone.
Click to expand...
Click to collapse
It didn't work. Any other suggestions? :|

jocyrus said:
It didn't work. Any other suggestions? :|
Click to expand...
Click to collapse
Don't know of any other methods because holding down the power button got the phone to turn off and allow me to get into download mode. From download mode, I was able to restore a stock 5.01 ROM to my phone via LG Mobile Support Tools.

LG G2 Bluescreen then no boot after disconnecting battery
Found my LG G2 with a completely blue screen. It would not turn off. Took it apart and disconnected the battery. Reconnected the battery and there was only a blank black screen and the phone would not boot. Zilch. Even with pressing the power button with the volume down to boot into recovery.....still zilch.
I sucessfully got my phone to work again using a hair dryer trick on an LG G3, which I found here.
1. I took the back off the phone, disconnected the battery, and removed the SIM card.
2. I then used a hairdryer on high heat and blew the heat over the uncovered areas for 10 minutes.
3. I let the phone from hot to warm, reconnected the battery and put it all back together with the SIM card replaced.
4. I booted into recovery and restored a TWRP backup, and my LG G2 is working like a champ again.

S4 Stuck on logo screen and restarts itself? Can only boot into Download mode.

So, yesterday my father said his S4 had just shut itself down and that now it only reboots itself and he can't boot the phone.
He asked me to see if I can get it working again and if not try to get the internal data of it, and we tried all evening to see if I could get it working with no success, we tried everything from changing to his second battery and I can't remember what made it work, but all of a sudden it was alive again and it worked for about 3 mins before restarting itself over and over again.
So now he has a phone that is stuck on the first logo screen (The screen that says "Samsung Galaxy S4") and I've tried to flash TWRP to see if I could get MTP to work for moving the files from the /data partition to my PC with no sucess.
He had decided to use his phone for a few more months before he would get a new phone but because of this he have now bought a S8.
So I want some help to see if anyone knows how I can get the files from the hard-bricked phone.
The phone was and is on stock Lollipop 5.0.1 and he hasn't touched the system in anyway until I tried to flash TWRP which did pass in Odin but it got stuck on the "Booting Recovery" until it restarted itself again. The weird thing is that the phone stays on in Download mode and doesn't restart itself there which leads me to think there isn't any hardware error.
Any help is much appreciated!

Just tried to reflash the system, got a little further but then it got into the same problem. It boots which is good, but after a a few seconds it restarts itself, I will attempt to move the files in this short period. But if anyone got a better idea, please tell me.
*Edit: It restarts way too often, sometimes (About 1/10 times) it manages to boot into the OS but then almost immediatly restarts. I've read that it might be the power button that has some dust inside it or something. Seems like after all it must be the hardware? But the weird thing is that it still can stay on inside the download mode, and when I'm holding the button there it shuts down, but not automaticly. I can get into the stock recovery but installing TWRP doesn't work.

If you tried installing TWRP 3.2.0-0 it has an issue with the S4. Use 3.1.1-0 or 3.1.1-1 instead. From there, you should be able to get the data off the internal storage. Once you do, give the side with the power button a firm whack on a table. If there's any grit in the power button, that may loosen it and restore the button to operating condition. Of course, you could get a replacement button but it may not be worth it despite the button being inexpensive and relatively easy to replace.

Strephon Alkhalikoi said:
If you tried installing TWRP 3.2.0-0 it has an issue with the S4. Use 3.1.1-0 or 3.1.1-1 instead. From there, you should be able to get the data off the internal storage. Once you do, give the side with the power button a firm whack on a table. If there's any grit in the power button, that may loosen it and restore the button to operating condition. Of course, you could get a replacement button but it may not be worth it despite the button being inexpensive and relatively easy to replace.
Click to expand...
Click to collapse
Not sure how I feel about whacking the phone (Even if it's firmly) on a table. But yes, I tried TWRP 3.2.0-0 so I'll try 3.1.1-1 later today. Thank you for the tip!

Well, I'm not saying you should bash it hard enough to break the phone, but it can't be a light tap either.
I didn't originally come up with the idea. I just promote it as a quick fix. A more permanent solution is to replace the button.

HELP! Stuck in Boot Logo w/ no Recovery Mode

Ok so before I started writing this I had only one problem now I'm worried my problem has gone from bad to worse.
I updated my 6T to 10.3.2 from the latest Beta after the process it prompted for a restart, upon restarting it got stuck in the boot animation. I tried going into Recovery and Download mode unsuccessfully so I went through the forums a bit and saw that someone who had the same problem successfully entered Recovery mode by pressing VOLUME UP+DOWN+POWER buttons simultaneously, I tried to do the same and my phone turned off and now it doesn't turn on! :crying:
Has anyone experienced this or know how to fix this? Any help will be much appreciated. Tia!

theDUD3 said:
Recovery mode by pressing VOLUME UP+DOWN+POWER buttons simultaneously, I tried to do the same and my phone turned off and now it doesn't turn on!
Click to expand...
Click to collapse
These should be clarified:
Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool.
Turn the phone off, let it sit. Then try turn it back on. Any response?

try to shutdown phone ...hold vol+ and power button for like 15 sec and restart your phone if this didnt work then u can try MSM tool

Thanks guys, got it working using MSM Tool!

regarding oneplus 6 got stuck on logo screen and recovery mode not working
was just going through some random stuff on my phone and suddenly my device automatically restarted and not it is stuck on logo screen. i and when i tried to open recovery mode, nope its is just not working either. i even tried the fastboot menu to open recovery settings but still no progress help me here...its urgent going though lockdown in country so no service either cant communicate with the fam also. HELP...!!!!

frankynehemimah said:
was just going through some random stuff on my phone and suddenly my device automatically restarted and not it is stuck on logo screen. i and when i tried to open recovery mode, nope its is just not working either. i even tried the fastboot menu to open recovery settings but still no progress help me here...its urgent going though lockdown in country so no service either cant communicate with the fam also. HELP...!!!!
Click to expand...
Click to collapse
You are likely going to lose your data. Know that going in if its not already backed up.
If you have the fastboot menu you can use the fastboot roms.
Or my least favorite option or what I would try last, MSM Tool (Tmobile 6Ts use a different tool).
IMPORTANT if you want to try and recover and data off your phone first, go to fastboot, and try and "boot" the TWRP img (not the installed one, one from your PC using the fastboot command). If that works you might be able to recover data. If that does worm, try dirty flashing the last ROM you were running and see if it boots.

No worries!
frankynehemimah said:
was just going through some random stuff on my phone and suddenly my device automatically restarted and not it is stuck on logo screen. i and when i tried to open recovery mode, nope its is just not working either. i even tried the fastboot menu to open recovery settings but still no progress help me here...its urgent going though lockdown in country so no service either cant communicate with the fam also. HELP...!!!!
Click to expand...
Click to collapse
Hello, I am sorry to hear of you having this issue, I just went through 3 1/2 days (off and on) of recovering my T-Mobile OnePlus 6t which I found a way to get my unlock code within 2 weeks of having it, so I rooted it and put a custom kernel on it, stuck on 9.0 never let me update as I was not familiar with A/B partitioning, yet! The answers I saw to your questions were spot on, I just had a little to add to it and I'm sure I am not alone. Real quick let me list what has gone wrong on the rare occasion it hit the fan with the 6t...
- When I would accidentally and rarely let my battery die it seemed like it took forever to get it to reboot, I mean it sat on my desk of DOA devices for 2 weeks!
- It often seems like the buttons do not always respond properly and never have when I needed them to. Been through this before, I've bricked and unbricked and flashed and re-flashed and wiped all weekend and I like Android 10 and all but seems everything is different for every build, and everything seems to have to go in the right order with the exact right file or you wind up in a jam, period..
- That said, the previous person that answered your question has likely encountered similar, I've heard of right down to the buttons not physically working, but I have been a Smart Device Master III Technician for over 5 years, i know my buttons were not broken.
- Most likely culprit that I just handled and worked, i did have to use the MSM tool, several times - and re-unlock the BL, several times I would not even get the chance to get to fastboot, just a screen saying Build and Hardware not a match"" in yellow letters and it just bootlooped. No fastboot is no good, but when you said the tool would show some signs of working but then not, I have 2 solutions that I needed on diffrent occcasions.
1 - As mentioned fully try other USB cables, and ports, if you pull the usb-c out of the port and hold <power + vol up + vol down> eventually it will do something, very picky, sometimes gotta move your fingers to different spots on the buttons and also after 15-20sec let go of power and hit and hold it again... after a few seconds before it vibrates stick the cable in connected to your PC and the screen will be black (obv) but the msm tool will pick up on it. I know about the cables because I take good care of my phones and cables and charging ports, however on my final fix today it showed in msm tool it was connected but waiting for device.... Fed up i put the phone down and moved the usb cable a little bit and it picked up on it and did its thing! That part was just the cable, getting into qualcomm mode or w.e. is a bit tricky sometimes.
- Also someone said set it down for a while and come back to it.. THAT WORKS!! Let it fully charge and often just plugging in charger turns it on, bootloop soft brick or however have you, very simiilar to an Apple device and their DFU (don't f up mode cause screen is black..)
I hope that helps you get in touch with your family and friends.. Whatever you do, don't give up bc if you have not got it yet, you will! One other note, there are a few different msm tools available and they look the same some same size, but the one that supposed to work on my phone didn't and one that they say only a fool would attempt to try actually saved me, so if all else fails, use a different msm tool/usb cable and you will get it! I don't think I can post links yet I am on here very rarely, but plan on more! I have received so much help from XDA throughout the years on thousands of phones with just software issues alone, aas well as guides to my own phones. I would be honored to give back as I also have some extensive knowledge on many devices but I am a noob in comparison to many! Stay safe, good luck and please update and let us/ me know how it worked out for you. If i can help further I will, I have every firmware file for the OP6t, recovery, tools, software, this is not new to me but I feel your frustration!