My Android 4.1-4.2 (Sony xper. L) is stuck in bootloop. My ultimate goal is to recover my text and image (jpg) file data before flashing/resetting.
The phone is not rooted. The way forward it seemed to me is to start the phone in fastboot mode before extracting the system.sin file, from which I could then extract my data. It seems fastboot mode is also a prerequisite for other methods of data extraction.
But now, I cannt start my phone in fastboot mode. I could do this for a while (before I knew of the system.sin step). But now, starting the same way--unplug and replug battery after a few minutes, push and hold start button and volume-up button, I no longer get the blue light, but head directly into bootloop again.
How can I start my phone in fastboot mode?
Suggestions are welcome on my overall data-retrieval method. But I (a software dev but a phone newbie) presume I have to start the phone in fastboot mode first of all.
Thanks in advance!
Could it be that the phone is simply out of power, and you need to leave it in a charger for a while? (Occam's Razor in effect, I hope)
GL!
Note: Also, really really recommend services like Carousel (Dropbox) to automatically upload all photos and videos.
Thanks, deecept,
I do not believe lack of charging is the problem; since the phone does not shut down, but heads into boot loop. I have already taken care to charge it. Nevertheless, I will charge it again, just to make sure. Thanks for that advice.
Re backing up, this is irrelevant to the current problem.
bweaver said:
My Android 4.1-4.2 (Sony xper. L) is stuck in bootloop.
But now, I cannt start my phone in fastboot mode.
Click to expand...
Click to collapse
Did you try the 'repair' option through PC companion?
Edit: Sorry, you want your data back. So 'repair' might not work - not sure.
I guess you don't get any response by doing these from the terminal? Do you?
fastboot devices
adb devices
Related
Hey,
Yesterday I upgraded my gf's GT540 to 2.1 (v20B) (fooled around a bit with the no-logos-showing-at-boot error but got rid of that bug eventually by KDZ software upgrade) and later I tried fixing the "can't establish a reliable data connection to the server" bug by deleting the file located at /data/data/com.android.providers.settings/databases/settings.db. After a reboot, I got stuck in an infinite boot loop of the Android logo. No matter what update I reflashed, I was stuck with the infinite Android logo. I kind of fixed that problem by adb-ing inside the phone while the loop was going on and I tried to recursively delete everything in /data/data/.
Now, no matter what update I KDZ, every boot gives me constant "The process _________ has stopped unexpectedly...". I think the files are missing but I don't quite understand why, the updates should totally wipe everything from the device and then create a new file system bla bla bla... It's like no matter how I apply any update, or do a bunch of hard resets, it doesn't do anything to the phone.
BTW I haven't tried fastboot stuff (simply because holding the camera + power doesn't take me to fastboot for unknown reasons), and I don't know about the windows enabler or where to find it.
I spent like 10 hours trying to unbrick this phone and searched everything everywhere now and I am getting really annoyed and confused with what's going on so please somebody throw me some tips before I nail this device on the wall...
Damn, everything is so much easier with HTC devices...
Thanks for every chunk of info,
Jay
You can try to do a hard-reset - http://www.hard-reset.com/lg-optimus-gt540-hard-reset.html
PS. To turn on fastboot mode you should press Power (and hold it until the phone vibrates) and then press and hold Home button. Fastboot mode is just a black screen (there won't be any text displayed).
hash87 said:
You can try to do a hard-reset - http://www.hard-reset.com/lg-optimus-gt540-hard-reset.html
PS. To turn on fastboot mode you should press Power (and hold it until the phone vibrates) and then press and hold Home button. Fastboot mode is just a black screen (there won't be any text displayed).
Click to expand...
Click to collapse
I did at least 10 hard resets.
Holding the home button doesn't give me fastboot mode, it boots Android into safe mode...
PS: Somehow I have lost the ability to use ADB, which is quite annoying.
I forgot to mention - fastboot mode works only if you've ROM with fastboot - http://forum.xda-developers.com/showthread.php?t=828003
hash87 said:
I forgot to mention - fastboot mode works only if you've ROM with fastboot - http://forum.xda-developers.com/showthread.php?t=828003
Click to expand...
Click to collapse
Thank you I have managed to get to the blue FASTBOOT screen! Now I have a device named Android in the Device Manager, but I do not have drivers for it so fastboot console application is still stuck at < waiting for device >...
The drivers for fastboot installed for me just fine using windows update. You can also try drivers from this link: http://www.speedyshare.com/files/24707580/android_usb_windows.zip or http://pdanet.co/bin/PdaNetA245.exe
hash87 said:
The drivers for fastboot installed for me just fine using windows update. You can also try drivers from this link: http://www.speedyshare.com/files/24707580/android_usb_windows.zip or http://pdanet.co/bin/PdaNetA245.exe
Click to expand...
Click to collapse
Thank you, you are the hero of the day! Now I have succeeded in flashing back the v20a firmware!!
So to answer the first question, yes I followed the stickied guide up top, and yes, it successfully flashed the bootloader, wiped all data, and flashed stock ROM all to success. It appears my case is unique. I was told that it could be the battery connection, so I've done no fewer than half a dozen times of taking the back off, resetting the battery connection, and closing back up. It does not appear to be the battery.
I am stuck on the fastboot screen, the one where the android is lying down and blue squares project from an body. It shows me the controls I can make with the volume switches and the selection choice of 'Start'... but I cannot do anything. Before I went to flash I could move through the selection with Vol Up ONLY, but now I cannot even do that. Here's all the mode says:
Code:
FASTBOOT MODE
product name - grouper
variant - grouper
hw version - er3
bootloader version - 4.23
baseband version - n/a
serial number - ###############
signing - not defined yet
LOCK STATE - UNLOCKED
I've pretty spent the past twenty four hours on google searching through all the threads I've seen. They are either all dead, or most of them found the sticky fixed their problem. Has anyone heard of it coming to this?! All I can do is access fastbook VIA a DOS prompt and do fastboot commands, and if I disconnect the tablet from my PC, it'll remain in this mode with the screen on until the battery dies. Charging appears to charge the tablet, but again, no controls work. And yes, the buttons were set properly when I closed my tablet.
Anyone?
1) what is it exactly that your trying to do?
2) can u boot into the OS?
3) your recovery may be corrupt re-flash the recovery via fastboot
...Awesome... said:
1) what is it exactly that your trying to do?
2) can u boot into the OS?
3) your recovery may be corrupt re-flash the recovery via fastboot
Click to expand...
Click to collapse
I'm just trying to boot up! I don't know what happened, but I haven't been able to use it for school all week!
I cannot boot into the OS. Any time I plug this device in it sends me to the fastboot screen with no controls.
OK I just flashed CWMR 6.0.4.3 and it did not fix the problem.
Any other ideas?
I just repeated all the steps again to see if any of them failed before, they have not worked. So recap:
Stuck in fastboot mode
Android will not boot
Loose battery connection is not the problem
I am able to access fastboot on my computer
I have followed everything from the sticky (wipe everything, flash bootloader, flash image)
I have flashed a new recovery
I am still stuck in fastboot
I cannot control options in fastboot with the volume and power buttons
I can only access fastboot by charging my tablet
The only way the tablet will power down is when it completely depletes it's battery
As far as I can tell, nothing was wrong with the tablet when it was functioning
This happened when I went to charge my tablet, presumably when the battery ran flat running android
If I charge too long the tablet gets fairly hot.
That's about all the information I can provide. Is there anything else I can try? Please, I need a tablet for school and I cannot afford a new one!
Hi,
Last night google pushed out the Lolllipoop update to my phone. I have stock android, nothing is rooted or changed.
It downloaded the update, installed it and rebooted into a forever lasting startup animation.
After a night of this i tried to restart the phone, same situation as above.
I resorted to go into recovery mode and wipe the phone, get image of dead droid stating command not find.
Atleast bootloader works.
I use mac, im a bit geeky, but i have troubles find a good guide that lets me completely flash the phine back to 4.4 when you are in the situation of a halfass os on your phone.
HELP or at point to where i can complain to google
ropapa84 said:
Hi,
Last night google pushed out the Lolllipoop update to my phone. I have stock android, nothing is rooted or changed.
It downloaded the update, installed it and rebooted into a forever lasting startup animation.
After a night of this i tried to restart the phone, same situation as above.
I resorted to go into recovery mode and wipe the phone, get image of dead droid stating command not find.
Atleast bootloader works.
I use mac, im a bit geeky, but i have troubles find a good guide that lets me completely flash the phine back to 4.4 when you are in the situation of a halfass os on your phone.
HELP or at point to where i can complain to google
Click to expand...
Click to collapse
Long lasting boot animation means, it is call boot-loop. It happens to some people (including me) who upgraded to Lollipop. Try factory data reset using stock/custom recovery and see it is booting or not. It worked for me and some other people.
Factory data reset will erase all your data.
steps to boot in to stock recovery
1.Power off the Nexus 4.
2.Press and hold at the same time Volume Up, Volume Down and Power buttons.
3.When you’re at the Bootloader / Fastboot main screen press Volume Up until the Start text turns to Recovery mode.
4.Press Power to boot the Recovery Mode.
> shortly you will see a green Android laid on its back with a red exclamation mark.
5.Press and hold Power button and immediately press the Volume UP.
This will open the Stock Recovery mode of your Nexus 4.
You can download factory images for Kitkat 4.4 and Lollipop 5 from google website. Extract that file and you will find a file with the name Flash-All. Simply running the Flash-all script will erase all the contents in the phone. To avoid that, just remove the -w from the line
fastboot -w update ....zip
I hope this helps you!:good:
[resolved] Thanks
Thank you,
This should help people in the same situation. I did not manage to test your solution but the logic is there.
I found a toolkit for mac that rooted and installed kitkat 4.4.4. for me.
When google pushes lollipop again and if a boot-loop happens again, i will definitely give your method a go!
Thanks,
R
Hello everyone!
First of all - this is my first post here, so if I'm doing something wrong, please, correct me.
Three days ago i dropped my ALE-L21 into water closet (don't ask). I dismantled it and put into rice for 2 days. Today I decided to check if phone will start normally, but there is a following problem:
The phone is stuck into bootloop - after turning it on I see only the brand logo and after every 1 minute it vibrates for a while, the screen goes black and the brand logo appears once again. I tried to get it into recovery mode, but nothing happens. (none of button combination: holding power, power+volup or power+volup+voldown works. The phone always try to reboot)
I plugged it to PC and the only thing I can do is to get into fastboot (bootloader unlocked, phone rooted, but USB debugging is off, so adb doesn't see the device).
Any ideas of how can I fix that? Maybe just volume button is broken? Should I try to clean volume&power flex? Maybe there is an alternative solution to turn usb debugging mode on? Then I could try to recover it manually, with adb.
Flash the correct firmware in fastboot.
Szabi01 said:
Flash the correct firmware in fastboot.
Click to expand...
Click to collapse
How can I do that?
I can run fastboot by power+vol_down, but probably USB-debugging is turned OFF. ADB doesn't see any devices plugged in.
turbotramp said:
How can I do that?
I can run fastboot by power+vol_down, but probably USB-debugging is turned OFF. ADB doesn't see any devices plugged in.
Click to expand...
Click to collapse
If you pc doesn't recognize phone with adb or fastboot commands in fastboot you propably have some broken hardware.
But you can try this stuff if it recognize something.
Go to fastboot and flash TWRP with "fastboot flash recovery (recovery_filename_here).img" then try power + vol up, if it doesn't work you can try to extract UPDATE.APP app and flash system.img, boot.img, cust.img in fastboot. If TWRP works use this to re-install stock firmware https://forum.xda-developers.com/honor-4x/how-to/install-emui-4-1-4x-4c-g-play-g-play-t3515702.
Ok. Fastboot recognized my device, so I installed everything what you mentioned. Everything went 'OKAY', as it printed in cmd, but still there is no change. Whatever I am doing it freezes at brand logo and after some time reboots.
But I used branded ROM, which I downloaded from huawei website - it is the only one that not gives me "balong" error.
Any ideas before I give back my Huawei to the official service? Maybe there is some way to diagnose volume_up button?
Hey all, I recently flashed a new rom on my phone, which required me to factory reset my ticwatch I'm order to reconnect.
Upon doing to the first time, everything seems to have gone well, but had trouble connecting to the device. So I ran another factory reset. Since that one, I've been stuck in a boot loop.
I see the "device software can't be checked for corruption" screen for about 20 seconds, and then it vibrates, screen turns off, then I see the same screen again. And so on.
I tried letting the battery go to nothing and trying again, seems to be the same issue. I'm letting it charge and bootloop for now in case maybe I just don't have enough juice to make it through boot.
It is rooted, with custom ROM (followed a guide on this forum somewhere about half a year ago, was running great) and TWRP installed (at least it was, I've been unable to get to the recovery screen since the boot loop started). Cannot see it in adb ever in this process.
Anyone have any other suggestions? I remember the Samsung notes had a special USB tool that would bridge a couple pins to immediately go to recovery, is there a similar option here?
Can you get in usb mode,or fastboot or recovery maybe?There is solution..dont worry.I ghuess adb dont work,but you cant go to fastboot mode and boot twrp image and get in twrp recovery..in twrp recovery you need backup file..If you cant do that,we are going to another solution..
Yeah, I can't - via any combination of button holding - get into any booted mode. No recovery, no fastboot, nothing. If anything, some buttons seem to make it circle boot faster .
nieminen432 said:
Yeah, I can't - via any combination of button holding - get into any booted mode. No recovery, no fastboot, nothing. If anything, some buttons seem to make it circle boot faster .
Click to expand...
Click to collapse
,Yeah tough situation,and when you connect it to pc in that "broken mode" -boot loop and open adb shell on pc ,comand adb devices or fastboot devices,does it show device?When you screwed boot and you have twrp there must be option to get in twrp.One trick more go to manage devices in pc find your device if unknown you right klick on it,update drivers,manually,and then choose android,then android adb install device.
KristijanKG3 said:
,Yeah tough situation,and when you connect it to pc in that "broken mode" -boot loop and open adb shell on pc ,comand adb devices or fastboot devices,does it show device?When you screwed boot and you have twrp there must be option to get in twrp.One trick more go to manage devices in pc find your device if unknown you right klick on it,update drivers,manually,and then choose android,then android adb install device.
Click to expand...
Click to collapse
I tried adb devices, but not fastboot devices, thanks for the idea, I'll give it a go.
nieminen432 said:
I tried adb devices, but not fastboot devices, thanks for the idea, I'll give it a go.
Click to expand...
Click to collapse
Maybe it wont work,but if doesnt,we figure out something..Bootlop is not the end of your device..
No go on either command. Nothing shows up.
I'm half wondering if it's my battery at this point. I think I'm getting a new watch for Christmas anyway, so not a huge loss. But happy to keep trying if anyone else has any ideas.