Related
Hi guys,
my wiley fox swift gets stuck in a continual optimising apps cycle. I can't enter recovery mode, when i press power+volume up it enters fastboot
(only see the black fastboot screen can't do anything). I did not change anything on my phone (not rooted) it worked fine yesterday and today i can't get it to work.
It's always optimising apps, if it's finished then i see the cyanogen logo and it starts optimising again shortly after.
I removed the battery and did wait about 15 minutes before putting it back in, i tried waiting (after 2 hours+ of it optimising i gave up),
i does not get recognised when i connect it to the pc (although i only used it to put stuff on the sd-card before) maybe a driver would fix this but i'm not sure which one.
I'm pretty clueless right now and i would be happy if someone can help me.
Saw the same thing on a friend's device today, used fastboot to factory reset the device. Insert USB in a powered-off device while holding vol+ then using fastboot do a "fastboot -w" to factory reset and recreate the (probably corrupted) data partitions.
i installed the minimal adb and fastboot connected my phone with my pc started it and tried it.
it doesn't recognize my phone and is stuck "waiting for any devices".
what can i do now? i'm not very experienced with android phones and fastboot.
dajohre said:
i installed the minimal adb and fastboot connected my phone with my pc started it and tried it.
it doesn't recognize my phone and is stuck "waiting for any devices".
what can i do now? i'm not very experienced with android phones and fastboot.
Click to expand...
Click to collapse
ADB needs debugging to be enabled in developer options
FASTBOOT will only work if the phone is in bootloader mode
I already said in my first post:
dajohre said:
I can't enter recovery mode, when i press power+volume up it enters fastboot
(only see the black fastboot screen can't do anything). I did not change anything on my phone (not rooted)
Click to expand...
Click to collapse
since i never changed anything in my phone I haven't enabled debugging in developer options, if I could access the bootloader mode I could reset my phone but like i said,
it enters fastboot and not the bootloader from which i could enter recovery mode
under these circumstances, can i do anything?
see here https://wiki.lineageos.org/devices/crackling/
Note they call bootloader mode Download
Ok i can access recovery mode now (it was explained wrong here)
i tried to factory reset but the problem still persits.
in recovery mode i did go to ->Wipe data/factory reset then i had the options (No/No/Yes -- delete all User data/No)
i choose the third option and it did load a short while. after a reboot it still wants to optimise apps.
what's the best option now? i can choose (Apply update\ Wipe data/factory reset\Wipe cache partition\wipe media\reboot to bootloader\View recovery logs)
Fix
Hi,
I had the same issue and wrote the Wileyfox customer support.
They provided me the following instructions to fix the issue:
Download:
* 1 - ZNH0EAS2NH
* 2 - ZNH2KAS7EB
* 3 - TOS111B
Repeat for File X in [1, 2,3] :
* Goto Recovery
* Update your phone using File X
Since this is my first post I am not allowed to post links.
Find the full document including file links here: h t t p s : / / we . tl / B1IpUP6wtB
Already after running the first update my phone booted again.
Only thing I noticed is that the UI feels a little laggy / slower than before.
Regards
I've got a Samsung Galaxy Tab S 8.4" which no longer has a working display. I want to back up as much of it as I can, so I've set to work on installing TWRP. I already installed and used it successfully on an identical device (but with the screen working!), but this time round, it just doesn't work.
TL;DR: My questions: Is there any way to add TWRP to my device without using Download Mode? Is there any way to check if TWRP is installed? And is there any way to, once I'm in Download Mode, determine that without exiting and without a display?
My process: I've tried getting into Download Mode both by shutting down, then holding the power, volume down, and home buttons for ten or so seconds, then following up with a volume up press to confirm that I want to use download mode; and by just typing reboot download in adb. I've then used Odin to flash it with TWRP. Odin shows a PASS, so I wait for the tablet to reboot into the normal mode.
Once there, I've tried to get into TWRP by both shutting down, then holding the power, volume up, and home buttons for ten or so seconds; and by just typing reboot recovery in adb. But, no matter how long I wait, my device never reconnects to my computer, and adb shell can't connect to it.
When I've rebooted into recovery, I seem to be able to press the power button once, and it reboots into the normal boot mode; this indicates to me that it's in the normal Recovery Mode, since this isn't default TWRP behaviour. That would mean that TWRP hasn't been successfully installed.
I came across this thread, which suggested that using Odin to flash a device while it's not in Download Mode would likely have no effect. My figuring, then, is that I haven't successfully booted into Download Mode ever.
Interestingly, when I ran Odin during what I thought was Download Mode, it did seem to restart the device when it was done (at least, after a bit I could connect to it normally with adb).
My question, then: Is there any way to add TWRP to my device without using Download Mode? Is there any way to check if TWRP is installed? And is there any way to, once I'm in Download Mode, determine that without exiting and without a display?
I know it's a bit of a tricky one, so :good: if you can think of an answer to any of those.
I wonder if the hdmi adaptors would work in recover, they are quite cheap to buy.
Your issue is likely that you're not manually booting to recovery IMMEDIATELY after flashing with Odin. TWRP is obviously successfully flashing.
You need to disable auto-reboot then when odin states PASS, force manual reboot by holding POWER + HOME + VOL DOWN for a few seconds then change to VOL UP whilst still holding the other buttons.
This is all gonna come down to timing, so you may have to do it several times until you get it.
In any case if all you need to back up is your stuff stored on internal storage, you don't need twrp for that. Just connect the tablet to the PC and use MTP to backup what you need.
Hello everyone,
a friend of mine is having problem with his M9. He recently downloaded an update to the phone, but after restart the phone no longer boots, says 0% battery and would not charge (just keeps heating). After a while on the charger it tries to boot (white screen with HTC logo), but after like 20 seconds it reboots.
I can make it enter the "service menu" (or how is it called) - white screen saying "Software status - modified, LOCKED, S-ON" and some menu items (I would post a picture but the forum won't let me because I am new...)
the problem is that Recovery mode does not work, there is just black HTC logo in infinite reboot loop. Reboot to bootloader just reboots to the same menu. The download mode basically says "Failed to boot to download mode. This build is for development purposes only..."
If I plug the phone to PC, while the menu is present, I hear a sound that is was plugged to PC, but a second later it's unplugged, so I was unsuccessful trying to make some sense to it using ADB.
Can the phone be saved? Thanks for help
Whats annoying is that the phone keeps rebooting until it runs out of battery power, I haven't found a way to prevent it from rebooting. So-called "smartphone"...
I tried to update the firmware using RUU_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.23.617.1.exe, but it said I don't have sufficient battery charge. So I plan to use the Fastboot-battery-recharge.bat overnight to give it a charge.
The problem however is that the command
Code:
fastboot getvar battery-voltage
returns "battery-voltage: " without the voltage itself. Anyone experienced this? I am using the latest minimal ADB and fastboot (1.4.3)
BTW the phone is originally EE UK.
I have been give samsung galaxy F41 with android version 9.0 but has limited functions which did not interest me. According to its specifications, it can be updated to android 10. I tried updating it using OTA method but it tells me there is no update and so I wanted to flash it using ODIN but it can not boot into download mode using the vol+, vol- and side Key combinations. Whenever I try it, it takes me to factory Mode and sometime it takes somewhere it gives me options of: recovery mode, fastboot mode and Normal boot. When I select Recovery Mode, it takes me to a window with the wording "No Commad". it stays there and then boot normally. When I select Fastboot mode, it stays there forever untill I press the side key and When I select Normal boot, it boots normally. please someone help me to boot this phone to download mode
press vol up and vol down together meanwhile connect your charger with ur pc and phone then it comes device unlock mode press vol up u will boot to download mode
Samsung Galaxy F41 Mobile Automatically switched off every 2 hours, and its starts after 1 hour,
how to fix it?
[SOLVED see post below]
Hi all,
Just bricked my Phone and can't access MSM. Hope you can help me. I will try to be very clear on the steps I took to get to this point.
Device: EU OnePlus 9 Pro
What is was trying to do: Go from rooted C.47 to Pixel Entended ROM
What I did:
Code:
Unrooted using Magisk uninstall option
Updated to c.48 through OTA
Go to lineageOS page on how to ensure all firmware partitions are consistent
very stupidly did not flash dtbo and vendor boot partition
did adb reboot fastboot in stead of abd reboot bootloader
Download the "lineage-19.1-20220701-recovery-lemonadep.img" and tried to temporaryly flash it by
fastboot flash boot <recovery_filename>.img
This resulted in the device getting stuck on the 1+ boot logo.
I can still force turn it off by holding Volume Up + Power.
When I try to access EDL by turned off and Vol UP + Vol Down + Plug and release, My PC makes a connection sound and the screen stay black for a while. After +- 10 seconds, the PC makes a disconnection sound and the phone boots up and gets stuck again on the 1+ bootup icon.
Also my phone won't stay turned off when plugged in the charger or pc
Yes, but what is it presenting as (i.e. EDL, fastboot, ADB, UMS...) when it connects?
If this is Windows, UsbLog.exe is handy to identify things popping up (as long as they have drivers installed).
For a list of devices that have ever tried to connect, try "enumusb.exe /l".
Both available here: https://www.temblast.com/windows.htm
Renate said:
Yes, but what is it presenting as (i.e. EDL, fastboot, ADB, UMS...) when it connects?
If this is Windows, UsbLog.exe is handy to identify things popping up (as long as they have drivers installed).
For a list of devices that have ever tried to connect, try "enumusb.exe /l".
Both available here: https://www.temblast.com/windows.htm
Click to expand...
Click to collapse
I will try this
I found the issue:
> EDL exits after 10 seconds if it is not captured by the MSM tool.
> The MSM tool only monitored 4 of my 10 USB ports
> So it was not captured because I was plugged in to an unmonitored USB port and rebooted after 10 seconds
> I have successfully used the MSM tool now
Oh! A bit off-topic, but I have never understood why EDL is commonly used over a "serial" port.
The interface that EDL presents is a generic USB bulk interface with two endpoints. You can use it just like that.
But no. They have to use a Qualcomm driver that makes it look like a "serial" port and then you can connect to that.
Me? I use a generic "WinUSB" Zadig driver. I have an EDL client that just connects to that fine.
So does the Python client implementation.
Also, I've never run into that 10 second timeout.
TraktorHenk said:
[SOLVED see post below]
Hi all,
Just bricked my Phone and can't access MSM. Hope you can help me. I will try to be very clear on the steps I took to get to this point.
Device: EU OnePlus 9 Pro
What is was trying to do: Go from rooted C.47 to Pixel Entended ROM
What I did:
Code:
Unrooted using Magisk uninstall option
Updated to c.48 through OTA
Go to lineageOS page on how to ensure all firmware partitions are consistent
very stupidly did not flash dtbo and vendor boot partition
did adb reboot fastboot in stead of abd reboot bootloader
Download the "lineage-19.1-20220701-recovery-lemonadep.img" and tried to temporaryly flash it by
fastboot flash boot <recovery_filename>.img
This resulted in the device getting stuck on the 1+ boot logo.
I can still force turn it off by holding Volume Up + Power.
When I try to access EDL by turned off and Vol UP + Vol Down + Plug and release, My PC makes a connection sound and the screen stay black for a while. After +- 10 seconds, the PC makes a disconnection sound and the phone boots up and gets stuck again on the 1+ bootup icon.
Also my phone won't stay turned off when plugged in the charger or pc
Click to expand...
Click to collapse
Your phone needs to be in OFF state mode when you're using EDL.
So, very simple:
Enter bootloader mode by holding both volume buttons with the power button together till your phone restarts and enters the bootloader.
From the bootloader screen you can use the volume buttons to navigate through the choices and you can select "Switch off".
When you complete this, you need to hold both volume buttons, and while holding them connect the cable (PC).
If you don't have or you don't have the correct Qualcomm EDL drivers installed, your phone will reboot or start to boot, it won't stay in EDL mode for longer than 10 seconds.
I also got the correct drivers for you, but you need to install the drivers manually while your device is in "EDL" mode, so, you need to be a bit "fast".
I have even a video for you, but need to upload it to YouTube so you can watch it.
I'll share you here the drivers just in case if you're familiar with a manual installation of the drivers.
ekin_strops said:
Your phone needs to be in OFF state mode when you're using EDL.
So, very simple:
Enter bootloader mode by holding both volume buttons with the power button together till your phone restarts and enters the bootloader.
From the bootloader screen you can use the volume buttons to navigate through the choices and you can select "Switch off".
When you complete this, you need to hold both volume buttons, and while holding them connect the cable (PC).
If you don't have or you don't have the correct Qualcomm EDL drivers installed, your phone will reboot or start to boot, it won't stay in EDL mode for longer than 10 seconds.
I also got the correct drivers for you, but you need to install the drivers manually while your device is in "EDL" mode, so, you need to be a bit "fast".
I have even a video for you, but need to upload it to YouTube so you can watch it.
I'll share you here the drivers just in case if you're familiar with a manual installation of the drivers.
Click to expand...
Click to collapse
Thanks for the help. The problem ended up to be a bit different than this for me, but this is a good post for anyone to find in the future!