Hi everyone,
after my phone was bricked during the ota kitkat update, i had to get the fzx file and flash from 4.1.2 to 4.4.2. and everything seemed to be working except now there is alot of issues with the wifi and 4g lte / cell services. I tried to get to the recovery menu but none of the options show up. I hold power, vol up and down, the black screen with white menu options comes up, i pick recovery. The android on the side with a red triangle comes up, ive tried hitting volulme up and down about 5000 times, alternating, the same time, but nothing works, the menu that is supposed to come up on that screen never comes up. Is there any way to fix this?
Related
I have the stock 'v10c' ROM on a 'Rogers' LG Optimus 3D.
This morning I was using the Google+ Android client and - without closing the app - pushed the power button to put the phone to sleep and put it in my pocket.
About 15 mins later I pulled the phone out of my pocket and it was dark, but the touch countrols were all lit up. I know that usually isn't good news. The phone was unresponsive.
I pulled the battery and tried to re-boot. It gets to the Rogers screen and then boot-loops, with a flash of the Rogers screen each time it restarts a cycle. Roughly 15 seconds apart.
I did vol+down+Power (guessing based on other phones) and it booted into a recovery (3e) menu that only offered me the chance to wipe all user data. Ok. I moved the cursor down using vol+down and sletected "yes" with Home. The phone then presented a triangle logo and the green android and sat there.
Meanwhile...I Googled. After about 10 mins I pulled the battery again and did the Vol+down+3D button+Power boot to the REAL recovery menu.
I then did a wipe / factory reset from the recovery menu. I have assumed the Home button is the enter button (BTW).
Again the triangle and the green android appear. They are still there 10 mins later.
Not sure what to do now...the phone won't boot and the factory reset won't fix it. But it isn't dead. I can still get to recovery, so in theory this is fixable. I just don't have time for it right now. :-/
I was wondering if maybe the phone had updated OTA in my pocket and I didn't realise it and I may have messed up the process. But I have never seen a phone do an OTA update without first notifying the user and seeking confirmation...so I that probably isn't the case.
Very annoying.
I'm posting this here in case anyone else has the same experience.
Anyone have any advice?
[Update: The Menu button is the enter button...not Home. So I did a real factory reset and the phone now boots to the "Welcome to your new phone" screen. *WHEW!*]
Uhmm... if Menu button is home button that means u have problem with build.prop. I never met with this kind of problem, however I think u just should turn on usb mode in cwm, put a ROM on phone, flash it and see how this will be. Don't forget to backup ur rom.
Sent from my LG-P920 using XDA Premium App
Hi there,
I've got the same problem with my LG P920.
Then I read your thread and now I can tell you how to fix...
The recovery is the right way to fix, but the homebutton is not the menu button.
You have use the Options Button the first from the left side or the 3d-button.
Than you came to factory default and you can restart youre device.
best regreads
Morphix
Anyone know the glitch that is causing this?
Sent from my LG-P925 using xda premium
If've got the boot-loop for the first time and it happend after a reboot comand on the comand app...
I have the same problem and no idea why it happens ..
I had this 2 times in one week! very anoying..
Hi All,
I had ICS installed on my TF101. However yesterday it totally discharged when it was asleep and I had trouble turning it on. I never had this happen with HC. So I decided to go back to HC. I had my tablet rooted and su backed up. Had recovery installed.
I flashed official US HC fw and everything went fine until I tried to reboot the tablet. It's now stuck at the EEE Pad loading logo with the blue bar approximately half filled in. No amount of button combinations does anything. I can't enter Vol + & Pow button to enter ADB, and when I try to enter recovery mode, the white text shows up saying searching for OTA recovery and that's it, still gets stuck at the blue bar.
Any ideas or ways to get to my recovery before I return my 2nd tf101? Thanks!!
(Btw, I'm not a newbie, I would NEVER do this whole thing if ICS was stable and worked like it's supposed to, but I refuse to own a 390$ half working tablet that crashes, has battery drain issue and gfx glitches after the FORCED ICS update!)
Have you tried cold-booting it? (power + vol-, wait untill you get the option to cold boot or wipe)
Also, I dont understand what you mean by "forced ics update". I ran my TF for several days without updating (albeit, with the annoying icon in the notification area).
Although I guess you bought the tablet new and recently Im still going to ask. Whats your serial number (3 first)?
Goatshocker said:
Have you tried cold-booting it? (power + vol-, wait untill you get the option to cold boot or wipe)
Also, I dont understand what you mean by "forced ics update". I ran my TF for several days without updating (albeit, with the annoying icon in the notification area).
Although I guess you bought the tablet new and recently Im still going to ask. Whats your serial number (3 first)?
Click to expand...
Click to collapse
Hi Goatshocker!
I have tried to cold boot it, but it does not allow me to get to the 2 icons you're talking about. When I hold down Vol - & Pow, it shows the regular white letters from bootloader, and gets stuck at the blue loading bar EEE Pad screen.
What I meant by force, is that after 4 delays of the update, ICS will install itself automatically! Even when the tablet is in sleep mode. That's what mine did.
In order to avoid this, the user would have to root his tablet and use Titanium Backup Pro, and disable certain system update processes. Which is NOT for the casual user or for anyone who wants to keep warranty intact.
The s/n I have starts with C2O.
I honestly need help.
I'm not sure what to categorize my issue under.
I am stuck in a screen with the green android and the spinning thing in the middle, with a progress bar, but the bar just has a moving animation, looks like it is moving to the left, not getting longer or filling up like usual progress bars.
I am unable to get to the boot loader or recovery.
The issue started after I flashed Cyanogen Mod 10.2 Stable.
it booted fine then, but when I went to use it, it would have a never ending cycle of app not responding at the part where it asks to sign in to cyanogenmod account. I got to settings without signing in by quickly sliding the status bar and clicked on factory reset.
From there it proceded to reboot and now I am stuck in the screen described.
I have tried all the button combinations, reset with pin, nothing will get to bootloader or recovery.
ADB does not find the device, also no devices found when try fastboot devices line.
I have also tried putting the firmware zip on a microsd, but nothing new happens either.
any suggestions appreciated.
** edited ** Issue is resolved. Turns out I just needed to wait longer (about 2 hrs) ... I did turn it off using combo of power and Vol -, left it off overnight, turned it on in the morning and left it alone. I finished whatever it was trying to do, and now CyanogenMod 10.2 stable is working great.
I recently gave my Verizon GSIII to my father, and it was rooted/unlocked/TWRP recovery. I gave it to him running a stock ROM (Clean ROM I believe) and no tweaks. It was 4.3 android version. All was well since April or so, but today he called me (from a different phone) with these symptoms:
1) He got a notification that made his notification LED pop on. He usually used the home button to turn on screen, and that didn't work. He tried the power button, and that didn't turn on the screen either.
2) I called his number and it did NOT go straight to voicemail. It rang 5 times and then went to VM. On his end, he heard and saw nothing. So the phone must have power I assume?
3) I had him hold down the power button for about 30 seconds - nothing seemed to happen.
My question is this: what should I do to try and troubleshoot this issue? I'm seeing him tonight for a little while, and I want a plan of attack. Should I try pulling battery/SIM/SD? Trying to boot into download or recovery mode? Anyone heard of this issue before? Thanks in advance for your help!
PsiPhiDan said:
I recently gave my Verizon GSIII to my father, and it was rooted/unlocked/TWRP recovery. I gave it to him running a stock ROM (Clean ROM I believe) and no tweaks. It was 4.3 android version. All was well since April or so, but today he called me (from a different phone) with these symptoms:
1) He got a notification that made his notification LED pop on. He usually used the home button to turn on screen, and that didn't work. He tried the power button, and that didn't turn on the screen either.
2) I called his number and it did NOT go straight to voicemail. It rang 5 times and then went to VM. On his end, he heard and saw nothing. So the phone must have power I assume?
3) I had him hold down the power button for about 30 seconds - nothing seemed to happen.
My question is this: what should I do to try and troubleshoot this issue? I'm seeing him tonight for a little while, and I want a plan of attack. Should I try pulling battery/SIM/SD? Trying to boot into download or recovery mode? Anyone heard of this issue before? Thanks in advance for your help![/QUOTE
If youd just included the led color. Could have saved you alot of time. As is. Could be anything.. Sorry. More input please
Click to expand...
Click to collapse
First off, my google pixel is 100% stock. Last night when I went to bed, I had no issues with my phone. I woke up in the middle of the night because the screen was on and very bright. It was the white google boot screen, but with a bunch of corrupted text sporadically over it, and it was stuck there. I held down the power button to reboot, but when it did it would get to my unlock screen, but be frozen there. After about 5 seconds on that screen, it would reboot itself, and just continue that over and over. I tried holding down the volume down button to get into the bootloader, but when I go into recover mode, it just gives me the logo of the green android guy with a red triangle exclamation point on it and it says "no command" below it. So I reboot, and the only way to stop the boot cycle is to to back into the boot loader and select shutdown, so that way it will stay off.
Any words of wisdom? I was really not looking to get a new phone at this point...
I'll add that I used the instructions here to try to apply a rescue OTA using ADB according to these instructions: https://drive.google.com/file/d/0Bz6x7k-VkpUJMlZ1aEliVnhMOHM/view. It completed successfully, but didn't make any improvement on the situation.
Update #2: I ended up trying to do a factory reset from recovery mode and that also doesn't seem to have helped.
Did you try installing a more recent OTA than what you originally had?
I already had the most recent OTA so I can't get a more recent one.
Try again in a few days when the February update is released. If it still doesn't work, it's possible a memory chip got fried.
If you're in the US, look up your nearest uBreakiFix location. They handle all Pixel warranties in the US. There are a number of reports in various threads of people getting their phone repaired for free, even outside of warranty.
I am in the US, but the nearest location for me is about 1.5 hours away. I guess I could give them a call to find out if it's worth the drive.
Why do you think a new OTA update would help where an old one wouldn't?
Is there any way I can flash the full image without having previously unlocked the bootloader?
Well i am experiencing the same problem on temporary basis since 2-3 days and the problem seems to be with the power button. I get it fix when i take it out of the body cover and try to clear the dust around power button and seems to fix it but it still happens in the morning or at night at home.