Hi
after a bad operation, my phone don't boot normaly. It's only vibrate and the screen still black.
To explain, firstly, all of update doesn't work as lot of nokia-HMD and provoke bootloop .
Thanks to Dhananjay Bhardwaj (https://www.the***********.com/), to resolve matter, I succeeded by switching slot B to slot A in fastboot mode to restore a correct boot.
Last days, I tried to update my phone with "ADB sideload" command and before updating, I switched slot but the current-slot was in “_a” and I put the value “b”.
Consequently, the phone don't boot normaly. It's only vibrate and the screen still black.
I can't boot in recovery mode to access to fastboot mode and change again the slot to "_a", initial value.
After different tests, only SP Flashtool detect my phone in download mode but I can't update because it is OEM locked.
If you have a solution, I take it. Furthermore, I'm in France and the warranty doesn't work in my country.
Thanks you
Hi,
got the same problem.
How did you manage to swith to slot b?
I've actually unlock my bootloader and execute the command fastboot flashing boot instead of boot_a
Now, I don't know how to enter recovery mode or download mode
Thx
Related
Hi,
A few days ago I woke up with battery at 1% asking to enter extreme mode and after I did some charging I noticed my battery is draining fast. Then I decided to restart my phone and it went into a bootloop.
I restarted this phone previously without any problems.
Now I can't enter download or recovery mode. I can only use fastboot on bootloader menu but not adb cause I can't enter download mode (adb shows no devices but fastboot shows).
My phone bootloader is locked, S-oFF production. Everything is stock, never changed anything.
Tried fastboot oem rebootRUU didnt work.
Tried fastboot boot recovery.img and failed as I need unlocked bootloader
fastboot oem unlock/lock shows unknown command
fastboot flash hosp hosp.img also didn't work
fastboot flash boot recovery.img didn't work.
All of them lead to a small HTC logo in the middle but then return to the bootloop.
I also tried removing SD card and rebooting but didn't work.
Is there any solution to this problem? Thanks.
A wild shot..
ttimt96 said:
Hi,
A few days ago I woke up with battery at 1% asking to enter extreme mode and after I did some charging I noticed my battery is draining fast. Then I decided to restart my phone and it went into a bootloop.
I restarted this phone previously without any problems.
Now I can't enter download or recovery mode. I can only use fastboot on bootloader menu but not adb cause I can't enter download mode (adb shows no devices but fastboot shows).
My phone bootloader is locked, S-oFF production. Everything is stock, never changed anything.
Tried fastboot oem rebootRUU didnt work.
Tried fastboot boot recovery.img and failed as I need unlocked bootloader
fastboot oem unlock/lock shows unknown command
fastboot flash hosp hosp.img also didn't work
fastboot flash boot recovery.img didn't work.
All of them lead to a small HTC logo in the middle but then return to the bootloop.
I also tried removing SD card and rebooting but didn't work.
Is there any solution to this problem? Thanks.
Click to expand...
Click to collapse
Have you tried a "Power Off" ... wait 10 to 20 secs ... then hold "vol down" and "power" at same time. See the little "HTC" twice before you release the buttons. That should put you in boot loader mode. Then we can go from there. If it doesn't then I don't know what to do. It is how I have recovered from my catastrophes... and I have had similar instances like yours.
Hi all,
I'm a bit stuck. Went to sleep last night with a working phone. Woke up this morning with the device turned off, and trying to turn it on always bumps me into Fastboot. I'm guessing my custom ROM tried and failed to update overnight...?
I can run fastboot commands, but trying to boot using a boot.img from a downloaded ROM (fastboot boot boot.img) still kicks me into Fastboot. Tried installing a Stock ROM, and the full install goes through, but still reboots to Fastboot.
I've downloaded the MSM tool and EDL package to see if I can get that to work, but you guessed it, I can't get into EDF mode (holding both vol buttons and connectting the phone sends me to Fastboot).
Anyone any ideas
Arran
In my case I fixed it by swapping to the other slot...
getvar current-slot to see the active partition
fastboot --set-active=a to set partition a instead.
Rebooted - all OK
Hello,
I got my Fairphone stolen and I had to get a new one and re-config my os onto it (I had Iodéos).
I followed the official instruction here https://iode.tech/en/iodeos-installation/#1648127755024-cd19692f-431b but got stuck when my phone never reached recovery mode. It is now stuck in the bootloader menu (Start/ Restart to bootloader/ Recovery mode/ Power off/ FFBM/ QMMI) and whatever the option I chose I keep comming back to this screen. The phone don't start normally anymore. The bootloader is unlocked and I never locked it before finishing the installation as I read it can brick the phone, still I'm stuck here. I tried everything I found on the internet (removing the battery and waiting etc). Fastboot commands work fine. Adb commands obviously does not. I'm kind of desperate... Any ideas ?
Thanks a lot in advance !
Better late than never.. when in fastboot mode run command:
Code:
fastboot --set-active=a
Then reboot.
Aanze said:
Better late than never.. when in fastboot mode run command:
Code:
fastboot --set-active=a
Then reboot.
Click to expand...
Click to collapse
Thanks ! I had already done this without result.
But I solved it by flashing FPOS to get out of the bootloop and flashing iodéOS after.
All the steps here if it can help someone.
Hello people!
Yesterday my Oneplus 7T informed me about the new OTA update to Android 12. I downloaded and installed the update, battery was >90%. Then I did the required restart but the phone was not booting again. After that I tried entering recovery mode (Volume up + power button) which was succesfull, but from this point there is no way to get the phone booting up normally.
I can enter the Recovery Mode or the Fastboot option.
I already wiped the cache, didn't help at all.
Boot reason shows: init_user0_failed.
Is there any way to get access to my data again or to boot up the system?
The phone is not rooted or anything like this. This is why I'm wondering how this could happen...I mean this was an official system update by Oneplus and it killed my phone...
Thankfull for any answers.
desMaxle said:
Hello people!
Yesterday my Oneplus 7T informed me about the new OTA update to Android 12. I downloaded and installed the update, battery was >90%. Then I did the required restart but the phone was not booting again. After that I tried entering recovery mode (Volume up + power button) which was succesfull, but from this point there is no way to get the phone booting up normally.
I can enter the Recovery Mode or the Fastboot option.
I already wiped the cache, didn't help at all.
Boot reason shows: init_user0_failed.
Is there any way to get access to my data again or to boot up the system?
The phone is not rooted or anything like this. This is why I'm wondering how this could happen...I mean this was an official system update by Oneplus and it killed my phone...
Thankfull for any answers.
Click to expand...
Click to collapse
Find out which slot the phone is trying to boot to and see if you can buy to the other.
If so, boot into that slot and redo the update with the full package instead of the update package
This post give instructions on how to do find out & switch the boot slot
https://forum.xda-developers.com/t/guide-how-to-root-oneplus-7t-without-twrp.3979307/post-81369381
wfred said:
Find out which slot the phone is trying to boot to and see if you can buy to the other.
If so, boot into that slot and redo the update with the full package instead of the update package
This post give instructions on how to do find out & switch the boot slot
https://forum.xda-developers.com/t/guide-how-to-root-oneplus-7t-without-twrp.3979307/post-81369381
Click to expand...
Click to collapse
The active slot right now is B. But when I try these commands:
$ fastboot --set-active=a
or
$ fastboot -aa
Should set the active slot to A.
Similarly
$ fastboot --set-active=b
or
$ fastboot -ab
Should set the active slot to B.
...it always says, that this is an unknown option
EDIT: Had to add ./ before command, but now it says
'Slot Change is not allowed in Lock State'
desMaxle said:
The active slot right now is B. But when I try these commands:
$ fastboot --set-active=a
or
$ fastboot -aa
Should set the active slot to A.
Similarly
$ fastboot --set-active=b
or
$ fastboot -ab
Should set the active slot to B.
...it always says, that this is an unknown option
EDIT: Had to add ./ before command, but now it says
'Slot Change is not allowed in Lock State'
Click to expand...
Click to collapse
Ah, forgot that your bootloader was locked.
If you can get into recovery you might try a factory reset, but that will wipe your data
Yeah the factory reset worked, sadly all data is gone. Guess I'm cured from Oneplus for the future. Really wtf..
BTW After factory reset I tried to install the Android 12 update via local update to avoid OTA. Same picture, it also results in not booting again.
But thanks anyway for your helpand fast reply!
I restarted my phone after being prompted to by a recent update. For a while the phone was stuck in a loop of booting to the android screen followed by the magenta tmobile screen before starting the process again over the course of 5 min.
Now the phone only boots into the recovery mode menu(?). The black screen with the oneplus logo that prompts you to pick a language before giving you the options of "view boot reason", "wipe data and cache", "advanced", and "exit" on the next screen.
View boot reason just says init_user0 failed.
I have wiped the cache and restarted, still boots into the recovery menu regardless.
I can boot into fastboot, but I do not have the bootloader unlocked. With the bootloader locked that means I cannot boot twrp recovery image from what I understand? And then unlocking the bootloader wipes the data.
I have managed to boot into EDL mode as well and the phone will show up as connected in the MSMDownload tool.
ADB does not work as far as I know since my phone no longer boots into android. (It displays the qualcomm snapdragon logo briefly before showing the aforementioned recovery menu).
Is there anything I can do recover my data given the above information? I have reached out to oneplus support as well and they said they'd get a more specialized person to reply to my case in 6-7 hours. Thanks for any help.
Corick said:
With the bootloader locked that means I cannot boot twrp recovery image from what I understand? And then unlocking the bootloader wipes the data.
Click to expand...
Click to collapse
Correct.
Also from what I understand, you cannot 'pull' files from internal storage from Fastboot mode, contrary to ADB mode (unless I am wrong).
Maybe you could try switching 'Active Slots' in Fastboot mode? With a little luck the other slot may still be bootable. It is not clear if this command will be permitted with stock ROM. You can do a little research but the fastboot commands should be:
fastboot getvar current-slot
fastboot set_active a (or b depending)
fastboot reboot
Robinlong said:
Correct.
Also from what I understand, you cannot 'pull' files from internal storage from Fastboot mode, contrary to ADB mode (unless I am wrong).
Maybe you could try switching 'Active Slots' in Fastboot mode? With a little luck the other slot may still be bootable. It is not clear if this command will be permitted with stock ROM. You can do a little research but the fastboot commands should be:
fastboot getvar current-slot
fastboot set_active a (or b depending)
fastboot reboot
Click to expand...
Click to collapse
Thanks for the info. I gave that a shot after and unfortunately it said Slot change is not allowed in lock state. Oneplus support did get back to me and said I'd have to send the phone in for repair. They said the device data is likely lost though so I'm not sure if it's worth sending it in vs just wiping and all that myself.