I have a Fairphone (original) and I passed the wrong file to adb sideload (yep, feeling dumb right now).
The phone now will not boot. It goes into a boot loop, even if I take the battery out, and then boot while holding power and volume up to get to recovery, it still goes into a loop.
I even tried this script to see if there was a brief window I could get into adb to repair during bootloop, but adb never finishes waiting for the device even after about 5 consecutive reboots.
If I plug the phone in to charge, the empty battery appears, but then after a few seconds it goes into a boot loop too.
Code:
#!/bin/sh
echo "Waiting for device."
./adb wait-for-device
echo "Freeze!"
./adb shell stop
I can get into factory/test mode by holding Volume Down and Power. This seems to be the only state I can get the phone into that doesn't involve a boot loop.
Factory mode looks (mostly) like this picture (my screen shows english translation as well as mandarin):
vi8.info/pic/2014-01/Factory-Mode-Menu.jpg
While in factory mode:
adb can connect
adb shell gives me a shell, but su in the shell gives me permission denied, so no root access it seems
adb sideload says error, disconnected.
fastboot cannot see the device
adb reboot bootloader takes me back into a bootloop
adb reboot recovery takes me back into a bootloop
Is there anything I can do from here to flash a working ROM onto my phone?
I'm on a Mac. I can get access to a Windows machine in a week or so and will try SP FLash when I do, but until then, is there anything that can be done with Mac only?
Related
So I got my phone stuck at the Google logo, but since my volume down button is busted due to a fall I can't get into bootloader or recovery using the traditional method of power +vol down. It there any known workaround for this dilemma?
Code:
su
reboot bootloader
...from any terminal emulator with root access.
If you're not rooted, not sure you can even do this via adb from a computer?
Code:
adb shell
reboot bootloader
Thanks for the tips, however, since the phone is stuck at the boot logo the adb command or fastboot don't work unfortunately
You may need to fix the button then. Otherwise you may be out of luck in your situation.
Hi druids of android,
I have an unlocked Asus TF300 with CM-11 and TWRP 2.8.1.0
Recently I've updated CM via OTA to the latest available snapshot and after that I've done factory reset from android UI (I lost my password so I decided to create a new g. account)
Now my tablet after reset shows Asus logo, 4 penguins and it stucks on blue striped treamwin splash screen.
Splash screen flickers every 6s. I see the device by lsusb, adb devices for 5 seconds, after the device disappears for a while and it backs again. I can do some adb commands like adb shell ls, cat, rm but I can't do any fastboot command to flash recovery or system.
Any fastboot call ends with 'waiting for device'. I call it through sudo and I've configured udev according to wiki.cyanogenmod.org/w/UDEV
I've tried restart tablet with power+volUp, power+volDown, with the same results descibed above. PaperClip+VolUp turns the tablet off.
I've found /cache/recovery/recovery.log file. (can't attach whole file because I'm a fresh member)
Partitions were mounted and the loop begins after:
Code:
SELinux contexts loaded from /file_contexts
Full SELinux support is present.
I:Boot command: boot-recovery
I'm fighting with it a few evenings and I decided to ask You for help.
I have the exact same problem. Happened last night after the Wipe Data option.
I have since read that that is a horrible thing to do.
I did try this - http://forum.xda-developers.com/showthread.php?p=63269550&nocache=1#post63269550
But I am unable to get to the fastboot screen still after dd-ing. The data partition dd took hours and hours. Left it overnight.
Help would be appreciated.
SOLVED!
Got TWRP working again!!
Follow this post right under the post of which link is above!
http://forum.xda-developers.com/showpost.php?p=64591975&postcount=88
I was unable to get the adb shell commands working separately after going into #.
So I just put in
Code:
adb shell "dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1"
adb shell "dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1"
This should fix it!
Hello guys.Finally i found solve for my TF300T loop on TEAMWIN logo.I read many threads in XDA forum for this problem but nothing happens .I had no fastboot with adb ,no recovery menu with adb and combinaiton keys until get this command "adb shell recovery --wipe_data" found.First you must install naked drivers 0.73 http://forum.xda-developers.com/showthread.php?t=2139767.Then plug usb tablet to pc(windows) and open cmd and enter the command "adb shell recovery --wipe_data"and press enter.
Sorry for my english
Gonna try this tonight. Did the same thing to my tablet yesterday. I am running the latest TWRP(Kang) and Katkiss MM 6.0.1 ver 24 Did a wipe of the cache and dalvik as I was having some issues. It then started random rebooting into Android. So I went into bootloader screen and tried to start recovery and accidently hit wipe data and got the boot loop. Now it just boots and reboots about 3 times and shuts down. I will try the naked drivers and your commands.
To point out ,that before i found solution fo my tablet,i had no fastbout wih comb-keys .My loop was only on the TWRP LOGO and never restarting or closing alone,until to press power button for 20s about to restart tablet or press reset button + power button for 20s to shut down tablet.I hope find solution and sorry fot my english again.
Thanks to tobdaryl member
stock, non-rooted Android 5.0
Phone is soft bricked, turns on and freezes on the yellow Sprint splash screen.
I need to recover some files on internal storage.
I know that I could install ADB and use the adb pull command to transfer files to a PC, but I am under the impression that USB debugging needed to be turned on, it is not.
Other options? Thank you.
Actually, it turns out that usb debugging was enabled.
while stuck in the bootloop at the sprint screen I use adb.exe with command prompt:
adb devices
device is recognized
adb pull /sdcard c:/recovered_files
"device unauthorized"
have to figure out how to get around the authorization
Also tried to flash a custom recovery (Philz and TWRP) Odin says it was successful every time, then it boots into and sticks at the Sprint screen. I reboot (remove battery) and it's still the stock recovery
Edit: fixed it. Learned that "install-recovery.sh" resets the recovery at each OS boot, so just needed to turn off "auto-reboot" in Odin. Once I had Philz recovery installed, used adb to pull all the files I needed.
Hi, I tried to install the OTA lollipop update with USB debug mode, the process did not go thru and the phone rebooted into recovery (teamwin). I did restore my backup with recovery successfully, but every time I rebooted from recovery, it went directly to the recovery again. I could power off my phone from recover, but when I power it on, it goes directly to recovery. I tried power phone off, hold volume up key, plug in USB cable, it does not enter download mode, instead it goes into recovery mode again.
It seems that I do have ADB access, but the devices shows in "recovery" mode and I can't switch to "adb shell"
C:\Users\adb_fastboot>adb devices
List of devices attached
09cb97618d0ae1c6 recovery
Please help!
I searched some old post and did the following to unbrick my phone.
In TWRP terminal command type this codes.
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
I had "no space left" type of errors reported after both commands. However after reboot, my phone boots up to normal system! Yeah!
By the way, can someone share a lollipop recovery backup file, so we can just load from recovery? I don't have the courage to go thru that USB debug session once more. Thanks!
Hey,
I was trying to install CM on a BQ Aquaris X5 Cyanogen with the CM Instructions
but some how I failed :crying::crying::crying:
The Phone is rebooting every time first the TWP logo appears, then some red error messages appear and then the BQ logo appears
now everything returns.
It is not possible to power down the phone
If the Vol up and the Power button is hold for some time the FASTBOOT MODE starts.
Vol Down and Power has no function
What can I do to safe my Phone?
solved...
MaLuFi said:
solved...
Click to expand...
Click to collapse
Hey, I will get a X5 cyanogen edition in some days and I have a question : Where did you get instructions to move to CM?
Thanks
There is a german forum: http://www.android-hilfe.de/forum/bq-aquaris-x5-forum.2542/
Sent from my Aquaris X5 using XDA-Developers mobile app
oficial...
https://wiki.cyanogenmod.org/w/Paella_Info
How to get out of a boot loop
mousse04 said:
Hey, I will get a X5 cyanogen edition in some days and I have a question : Where did you get instructions to move to CM?
Thanks
Click to expand...
Click to collapse
I had that same problem last week, and I managed to resolve it.
My mistake had been to omit that reboot after unlocking the boot loader, so I got into that same boot loop with booting to recovery (TWRP) -> TWRP throwing errors -> TWRP causing a reboot -> rebooting into recovery again -> same error -> reboot -> etc. etc.
Here is what you can do (at least it worked for me); thanks also to the helpful people in the TWRP IRC channel on freenode:
Power the phone down during a boot loop:
It is not necessary to wait until the battery is completely drained by
rebooting hundreds of times.
There is a small time slot where the phone should accept "adb" commands during rebooting. So there is a chance to submit an "adb" command if you just send it over and over again. It may take some reboots to catch that time slot, but if you do it often enough, it should succeed at some time.
This worked nicely for me:
Make sure the latest Android SDK is installed (which includes the "adb" command).
Connect the phone to the PC with via USB.
While the boot loop is in progress, open a shell window on the PC (using
Linux in my case) and enter this command:
sudo adb shell reboot -p
(without "sudo" for Windows users - did not try that)
Repeat the command over and over again.
Use [Cursor Up] to repeat it from the command line history.
Do this until the phone's LED lights up and it shows a large battery logo on the display to indicate that it is powered off and charging.
! This might take many repeated attempts, don't lose your patience !
Disconnect the phone from USB.
Reboot into fastboot mode.
If TWRP is installed, this is [Power]+[Vol+].
If the stock recovery is still active, this is [Power]+[Vol-].
Break a boot loop that keeps booting into TWRP recovery
Make sure the latest Android SDK is installed (which includes the "adb" command).
Connect the phone to the PC with via USB.
While the boot loop is in progress, open a shell window on the PC (using
Linux in my case) and enter this command:
sudo adb shell rm "/cache/recovery/*"
(Without "sudo" for Windows users - did not try that)
Repeat the command over and over again.
Use [Cursor Up] to repeat it from the command line history.
Do this until the boot loop stops, i.e. you see the TWRP screen, and it does not keep booting any more.
! This might take many repeated attempts, don't lose your patience !
Reformat the /data partition under TWRP's "Advanced" options.
Just trying to wipe will fail at this time.
Reboot into recovery once more (TWRP -> Reboot -> Recovery).
Wipe (TWRP -> Wipe; the normal wipe which wipes data, cache, and dalvik).
Reboot the phone to system (TWRP -> Reboot -> system).
--
Stefan Hundhammer (shundhammer / HuHa)