Sorry if the thread is not in the right place and not fancy written, I don't use forums a lot..
So I've had that phone for about 3 years now. I've never rooted the device, never installed any custom roms, nothing. Only did a factory reset/wiped data couple of times.
One day I woke up (on 2nd of January), looked at my phone (it was charging whole night) and it was showing the "Google" logo. After that it switched to "colorful X", then it turns off, vibrates and all over again.
I was doing it until I took out the battery for a half an hour. Plugged it back in, turned on... Same thing was happening.
I've removed the battery again and plugged it back in. Pressed the power + vol up + vol down buttons in order to get into the bootloader. Got to the "recovery" and wiped the data/factory reset, and wiped the cache.
Restarted, didn't work.
Got mad here and decided to first time to attempt installing a rom. I've got to the google developer website where there are factory images. There were a couple of versions of the Galaxy Nexus. I didn't know which one to pick, so I've picked the first one (GSM with google wallet latest version). (I've already had Android SDK) so I've followed the instructions by using the "fastboot oem unlock"
then "flash-all". It failed. And the reason is when it rebooted, the bootloader locked again and the script couldn't continue installing/flashing.
So every time I unlock the bootloader and reboot, it locks it again.
I've decided to flash every img individually. By using this pattern:
fastboot oem unlock
fastboot flash bootloader bootloaderblabla.img
fastboot reboot-bootloader
fastboot flash...... and every single image including the radio, boot system, etc....
basically every time I flash and reboot, I unlock the bootloader.
That however didn't fix the problem, it was still remaining in the bootloop.
So I am not sure which version of the galaxy nexus I have, I've tried doing that will few versions of the factory images with no success.
So I came here, in a chance to get it fixed by some magic!
Please help?
Related
Here's my situation, maybe someone will find it interesting or know what's going on. I was running the EOS Jelly Bean (EOS-tf201-20120728-31.zip). Everything was running pretty well for a few days, then yesterday the device simply powered off. When I rebooted it got to the splash screen then shut off before it could get any farther. I figured it was a power issue, so I plugged it in and charged it for a while but get the same response. Around this point I started to get suspicious and tried to boot into recovery. It got to "Booting Recovery Kernel Image" then powers off the same way.
So then I proceed to go into fastboot and fastboot works great no power offs. Through that I am able to flash openrecovery-twrp-2.2.1-tf201.blob and the virtuous packaged boot as per this thread http://forum.xda-developers.com/showthread.php?t=1773280 as well as factory reset. I also tried a few other boot/recovery combinations and was able to make it into recovery. In twrp recovery I was able to install the latest Virtuous rom which got me back to stock and I thought good case closed. I even made it all the way into the OS and was able to install apps, wifi worked great, run the apps etc. Eventually the screen went blank though and I was stuck back in the same shutdown on boot scenario as described above. Now I'm able to fairly consistently flash openrecovery-twrp-2.2.1-tf201.blob, reboot, get into teamwin recovery, but now even that appears to be randomly powering off.
So now I'm guessing that it may just be bricked and is probably a hardware issue since the reboots appear so random, the unit was refurbished. At the same time I'm still holding out some hope that it's simply some boot code somewhere that was corrupted and I can flash something and get things back to normal again since I can still access fastboot and occasionally ADB and recovery. I've flashed from fastboot system/recovery/boot, any other thoughts or potential combinations I could try? Also anything I can do with those tools to debug it further and get more data on what may be the root cause?
Hello all,
I have followed several tutorials here on XDA, and even more video tutorials on YouTube, but I am stuck at the seemingly simple task of rebooting into recovery. I've rooted every Android device I have ever had, but this one is throwing me off...
I flash TWRP (from adb), erase cache, and then when I'm still in the bootloader, I go to bootloader>recovery and then for a split second I see the HTC logo with the pink "booting into recovery" text then it reverts back to the clean HTC logo and proceeds to reboot into the OS.
I've tried the whole process again and again, and still nothing. It doesn't say "TAMPERED" above UNLOCK (in the bootloader) either.
Any suggestions would be greatly appreciated, and thank you in advance
---
EDIT:
I managed to get it working. I let the phone sit (powered 100% OFF) while I brewed a pot of coffee (1-2 minutes), when I tried it one last time; it listed "TAMPERED" then "UNLOCKED" and allowed me to flash into recovery with no issues. I think the key is to let the phone sit for a bit while it is powered off. [MODs - Feel free to remove this thread if needed]
My wife was using her phone (completely stock, no mods whatsoever) and it started shutting down processes (contacts, calendar, etc). She held the power button down to manually shutdown and then rebooted shortly after. The next day, it started to do it again, so she did the same thing only this time it stuck on the "M" logo screen. When she brought it home, I held the power & vol down buttons in for 2 minutes and the phone began to reboot but still stuck on the "M" logo screen.
I began searching vigorously online for a solution and have tried everything. **NOTE** - I am completely unsure what version of software the phone was running before this happened. The first thing I tried was RSD Lite with the JB Stock file from Team US Cellular. The flashing fails during certain lines of the .XML file. I took suggestions from other users to delete the lines it fails on and let the file continue the flash. Once it reboots, it is still stuck on the "M" logo screen. I then tried all the other stock firmware files I could and the same result each time.
Next, I tried using ADB and Fastboot tools. My PC recognizes the phone when plugged in and running command "adb devices" shows the phone listed, but whenever I try to run a pull or other command, I get error:closed. I've tried all the solutions of making sure ADB files are updated, running the list of commands to get the daemon connection reset, etc. I can't push/pull anything using adb. I tried using mFastboot with no luck either.
I tried the above steps over and over for 3 days straight, hoping I missed something simple. My final option was to boot into Recovery Mode and run Wipe Data/Factory Reset. When I select that option, about 3 lines of command begin to run and the phone reboots and goes back to being stuck on the "M" logo screen. The command lines and reboot literally happen within 2 seconds. That tells me Factory Reset is corrupted, but I'm not 100% at this point.
Does anyone have any insight on if there is anything I can do at this point? It wouldn't be such a big deal to lose the phone, but we have pics/videos of our 2 year old that we never got backed up at home or in the cloud and they're very important to us. Unfortunately, the phone did not have and SD card. I'm honestly out of ideas at this point and have never felt so defeated.
I got brave and decided to just unlock the phone and attempt to install TWRP on it and that doesn't even work. It says it flashed it, but whenever I choose Recovery, it never boots to TWRP. It continues to use the stock recovery screen. I'm assuming this thing is just completely done for?
I was on my phone when suddenly it just booted off for no reason, weird right? So now it just stays on the "LG" boot up screen and now do anything. I've tried everything and done everything right (as far as I know) before I get into that let me tell you what my device can do as of now:
Devices DOES have fastboot oem unlock done
Phone was rooted as well and working perfectly (or so I thought until this happened)
ADB doesn't seem to work, but fastboot when connected to the computer does.
Ex: ADB devices (blank)
but fastboot devices (shows phone connected)
I've tried rebooting into recovery (Power + down) doesn't do anything, however, {Power + down} then finger off power then {Power + down} again takes me to "factory reset" option, if done so the phone just hangs and removing battery on way to take it back to fastboot on pc, or bootloop again.
I've done the following steps using [LG-H901] Stock .img Files (Boot, System, and Recovery)
Code:
fastboot flash system system.img
then
fastboot flash boot boot.img
and finally
fastboot flash recovery recovery.img
I've tried booting the phone and still gets me stuck on bootloop, and doing the same {Power + down} gets to the same "factory reset" option only then freezes my phone if I agree to do so.
Is there something I've done wrong or incorrect? I will provide as much info as requested.
Thanks guys!
Update: Phone booted up to lockscreen after finishing "Android is starting..." procedures, then kept bootlooping and it is now doing "Android is starting.." procedures again. I'll keep it updated if it keeps doing so or anything of the sort.
Did you reply YES when trying to enter recovery? It will ask 2 times and bith times answer YES ... And if you DO have TWRP installed it will boot into twrp recovery.
Double0EK said:
Did you reply YES when trying to enter recovery? It will ask 2 times and bith times answer YES ... And if you DO have TWRP installed it will boot into twrp recovery.
Click to expand...
Click to collapse
This is the weirdest thing, phone worked for a bit then shuts off and does the same thing. all files and everyhing was in tact. ANy main reason behind this? I am desperate not to delete everything because i have important photos on there that were still there when it re-started again right now.
So to recap: At the moment doing the {factory reset} got me as far as using phone for like 2 minutes before ****ting out and sending me on a bootloop yet again.
Important Questions:
On all my other devices I am able to connect via usb and read devices, but on this phone I get the message when connecting to my computer "LGE Android MTP Device: Failed" whats this about?
Is there any way to save internal photo album images other than getting this to boot up and pray it stays on long enough to transfer data?
UPDATE 2: Phone has booted up and not froze (yet)? Testing to see if it will keep working so far so good. Unfortunately all my **** was deleted which bummed me out, would have honestly prefered to lose a $600 phone than all the family, friend, ext photos I had on my phone I made the huge mistake of saving to internal memory and never backing up. Smh.
Update 3: Phone is back at it again with the bootloop. I have no idea what is wrong, I've repeated the steps twice and phone doesn't seem to let up. It's fine until I hit that restart or shutdown button then it goes into bootloop heaven. I'm guessing this phone is done for? On an unrelated note it did fall on me, but worked fine afterwards, it was just sudden when it started doing this. Unless anyone has more suggestions I'd be glad to hear them. As of right now, this phone is toast.
You tube how to bake phones in the oven.
It could fix some potentially loose solders..or since everything was already wiped you should get a warranty replacement.. Should still be under factory warranty.
Double0EK said:
You tube how to bake phones in the oven.
It could fix some potentially loose solders..or since everything was already wiped you should get a warranty replacement.. Should still be under factory warranty.
Click to expand...
Click to collapse
I am thinking the warranty route. Is there anything specific I should do before doing so? I hear having "fastboot oem unlock" {Bootloader Unlocked} voids the warranty. Is this true that you might know of? Either way thanks I appreciate the information.
Sorry so late..
But you can try to fastboot oem lock it.
Afternoon
I have a Lenovo 7" tablet which is sticking on boot...to describe:
tablet off, charge screen working fine (green battery)
can get into menu to select fastboot mode or recovery
fastboot works, at least screen appears!
recovery shows dead android/no command screen - how to access recovery?
booting up, get inital orange logo then a 'bing' and start of boot but then freezes on the second logo
tablet not visible on PC, even in fastboot mode (have installed drivers)
I'm looking to get this going but am a bit stumped. I tried reinstalling firmware but can't get SPF Tools to work with any available scatter files; I would like to install TWRP (I found a potential image file on XDA) but can't do this until the PC recognises it....and I'm going round in circles now....any suggestions gratefully received. :good:
Update
OK, post was maybe a bit premature - I've kinda fixed my issues.
Managed to get into recovery after watching many videos (most of which were wrong, but hey-ho, got me on the right path!). At dead android screen, press and hold in power + vol up + vol down together (there is a bit of knack, turn it on its side with buttons facing up seems to be easiest) - this fires up the recovery screen (android standard recovery).
I managed to get over my bootloop issue by performing a data wipe/factory reset and cache wipe, then restarted fine.
As this was a secondhand tablet (my usual purchases - good condition bootloops!) - once it booted up I got into the set-up screens only to discover a Google lock issue. I ran the FRP unlock from here: https://androidfilehost.com/?fid=11050483647474832839 using the instructions from here: http://forum.gsmhosting.com/vbb/f958/lenovo-tab-4-7-essential-tb4-7304f-frp-remove-2322527/ (Voltrans second post, not the original one which has a 404 error on the download site). This removed the FRP lock straight off and now I have a functioning tablet.
I'm probably going to try getting custom recovery on so will see how that goes - I'll post back
and...that's all folks....
OK, despite finding a TWRP recovery online https://twrpbuilder.github.io/downloads/twrp/#441 and downloading it, can I get the fastboot unlocked? no.
Apparently Lenovo locked them all up and threw away the key, so nothing more can be done here.
I tried various iterations of fastboot oem unlock and fastboot flashing unlock, and nothing works, just get an error - and yes, I did put developer options on, OEM unlocking ticked and USB debugging active.... :silly:
So, unless someone can point me in a direction on how to unlock it - I've reached the end of the road with this one