Related
Hey guys,
I unlocked my Nexus [email protected] via fastboot oem unlock. It worked so far, the device rebooted but was stuck in a bootloop just showing the animated bubbles. So i bootet into bootloader by pressing power + vol-dwn to perform a factory reset. Now it bootload it says Downloading... Do not turn off target!! beneath the android icon with the open front.
Besides this my problem is, that I cannot select Recovery by using the vol-up / -down buttons. It just says start as if there is no alternative.
Is there any opportunity to perform a factory reset / exit the bootloop?
Thanks in advance,
Calle
Hi,
Unlocking the tablet effectively wipes everything. Try unplugging from PC and entering bootloader via keypress
Then see here
http://forum.xda-developers.com/showthread.php?t=2670400
Pay attention to the third post, you could also flash a custom recovery and sideload a ROM if you don't want stock
Best of luck!
demkantor said:
Hi,
Unlocking the tablet effectively wipes everything. Try unplugging from PC and entering bootloader via keypress
Then see here
http://forum.xda-developers.com/showthread.php?t=2670400
Pay attention to the third post, you could also flash a custom recovery and sideload a ROM if you don't want stock
Best of luck!
Click to expand...
Click to collapse
Thanks for pointing to that guide. It worked and my N10 is back to live
Dear XDA friends,
i always hoped not to be one of those guys, who f****d up their phones to the point of no return. I really screwed up this time. Well, here I'am writing you about my screw up.
I unlocked, rooted, flashed and repaired all kinds of android phones in the past years, never without problems, but I could always fix it somehow. Not so much this time.
Now I'm stuck at Bootscreen with the Zuk logo. I even have problems pinging the phone via ADB.
Sorry for my noobish question guys. Any help would be much appreciated.
triby said:
Dear XDA friends,
i always hoped not to be one of those guys, who f****d up their phones to the point of no return. I really screwed up this time. Well, here I'am writing you about my screw up.
I unlocked, rooted, flashed and repaired all kinds of android phones in the past years, never without problems, but I could always fix it somehow. Not so much this time.
Now I'm stuck at Bootscreen with the Zuk logo. I even have problems pinging the phone via ADB.
Sorry for my noobish question guys. Any help would be much appreciated.
Click to expand...
Click to collapse
I got this translated from a chinese website:
For fastboot mode:
The phone turned off; keep the connection turned off the data cable to the computer, press: [volume down key] [Power Key] waiting to enter the fastboot mode.
For recovery:
Turn off the device
Press and hold Power key
When vibrates Volume UP key + Volume Down key about 10 seconds
Release all key when Android logo appear then you will see Android System Recovery
Use Volume key to select Menu
Use Power key to Confirm
Can you enter any of these 2 modes?
Life Engineer said:
I got this translated from a chinese website:
For fastboot mode:
The phone turned off; keep the connection turned off the data cable to the computer, press: [volume down key] [Power Key] waiting to enter the fastboot mode.
For recovery:
Turn off the device
Press and hold Power key
When vibrates Volume UP key + Volume Down key about 10 seconds
Release all key when Android logo appear then you will see Android System Recovery
Use Volume key to select Menu
Use Power key to Confirm
Can you enter any of these 2 modes?
Click to expand...
Click to collapse
thank you life engineer! No luck . I'll try to send it back. Thanks again for you're help. Much appreciated!
hi xda, i am facing thesame problem with my lenovo zuk z1 phone. its on a bootloop. i can enter the recovery by pressing both up and down vol. keys, i have wiped data/factory reset and wiped cache partition and rebooted but it doesnt fix.. I tried to reboot to bootloader but is stuck on fastboot mode screen. ive tried to search a solution but none have helped. The connection between phone via usb to computer only lasts like 2 secs. during boot then it disconnects again beacuse of the bootloop. Can anyone pls. help.
rusty96379 said:
hi xda, i am facing thesame problem with my lenovo zuk z1 phone. its on a bootloop. i can enter the recovery by pressing both up and down vol. keys, i have wiped data/factory reset and wiped cache partition and rebooted but it doesnt fix.. I tried to reboot to bootloader but is stuck on fastboot mode screen. ive tried to search a solution but none have helped. The connection between phone via usb to computer only lasts like 2 secs. during boot then it disconnects again beacuse of the bootloop. Can anyone pls. help.
Click to expand...
Click to collapse
How does the bootloop look like?
crian said:
How does the bootloop look like?
Click to expand...
Click to collapse
The bootloop is just showing the ''ZUK logo'' in the middle of screen and "'powered by Android logo'' below,and the phone vibrates everytime it flashes these logos. I tried QFIL but it can only detects the unit on the first boot or first flash that is 2 secs. only from the time i press the power button, and then it disconnects and not detect the unit again. Does anyone know where can i find the scatter file , MTK ROM for zuk z1, i would like to try the SP flasher tool. Or if anyone have any idea how to solve this issue on lenovo zuk z1,pls. help.tnx
Can y get to fastboot ?
im facing the same problem after i had the stupid idea to lock the bootloader again, before that i flashed the phone successfully with the cm mod recovery and cm 13.
Has anyone found a solution to this ? or do i have to send it back ?
What i did exactly :
I locked the bootloader again and just to test it i tried flashing the recovery again , ofcourse it didn't work which was what i wanted.
Afterwards i rebootet the bootloader with sudo fastboot -i 0x2b4c reboot
now im stuck in a bootloop that i cant even stop , in other words i cant turn my phone off nor can i access the recovery or fastboot
Im feeling so stupid that i locked it again .... i will try to get into recovery after my phone ran out of battery but so far it looks quite bad...does anyone know if i will get a replacement even though it was my fault ? ( i don't need to say that it was my fault ..and the bootloader is now locked again )
UPDATE::
I found a promising thread about this problem, i will report back here if i was successful.
-> forum.cyanogenmod.org/topic/121913-after-nighty-update-to-20160212-the-zuk-is-bricked-without-salvation/
CPP11 said:
UPDATE::
I found a promising thread about this problem, i will report back here if i was successful.
-> forum.cyanogenmod.org/topic/121913-after-nighty-update-to-20160212-the-zuk-is-bricked-without-salvation/
Click to expand...
Click to collapse
pressing Vol + & Vol - the connecting the USB cable entered bootloader mode. YEAH!!!!
Need some help
And after that what to do I can get it to recovery and the fastboot mod but after that what to do my phone like this for a month now
Any solution?!
did you solve it i have exactly the same problem for a month now as well (Exactly same situation) Please help
---------- Post added at 01:20 AM ---------- Previous post was at 01:08 AM ----------
Amen Ghazy said:
And after that what to do I can get it to recovery and the fastboot mod but after that what to do my phone like this for a month now
Click to expand...
Click to collapse
did you solve it i have exactly the same problem for a month now as well (Exactly same situation) Please help
Please help , same problem
I am facing same issue too from 2 days. I didnt even try to flash custom roms or play with boot loader or recovery or anything. All of a sudden my phone entered boot loop. After two three bootloops phone is entering "12 apps optimized of 230 apps" mode, completing optimizing all apps and then failing to start apps, entering boot loop again.
Effort made so far to fix -
1) Went to recovery and cleared cache - didnt work
2) Went to recovery and did factory reset - factory reset did happen but boot loop didnt stop, I realized that factory reset happened because now its saying optimizing 120 apps instead of my 230 apps during the bootloop.
3) Went to recovery, Entered fast boot mode but not able to connect to PC. Fastboot devices is not showing anything. I made sure proper driver is installed after researching on XDA.
4) Went to recovery, Tried "Install update". Didnt install anything but browsed through folder structure and realized my data is intact
It will be great if someone can help me atleast recover my data before I handover phone to service center for fixing boot loop issue.
Same problem
crian said:
How does the bootloop look like?
Click to expand...
Click to collapse
i have same problwm what to do plz help mme
Abhishekjain31291 said:
i have same problwm what to do plz help mme
Click to expand...
Click to collapse
Explain in detail
errecez1 said:
pressing Vol + & Vol - the connecting the USB cable entered bootloader mode. YEAH!!!!
Click to expand...
Click to collapse
The link is not accessible now. Can you let me know what you have done. My phone is in a boot loop now and showing only Logo and 'powered by Android' message. It keeps turning on and off again and again.
Guys when u are in fast boot mode .. pls install Twrp ... After insatlling that press power button abd vibration comes hold volum doen+volume up button at the same time ..
Then u will be getting recovery Twrp mode .. then connect it to pc and u will see internal srorage in pc...now u have to copy any rom to the phone and install it via Twrp ... Thats all
Sorry For Re-posting Here. This is Solution
Why this is happening ?
Due to Dirty Flash from Zui or from COS/CMOD but suddenly Bootloader gets locked
May be Due to Some Custom Rom which only works with Old Bootloader ( And you are on latest 2.5 Zui QPST Flash)
Reasons are many. I also did same mistake. I flashed ZUI 2.5 using QPST then unlock bootloader using official site installed twrp after wiping cache system and data , Installed Lineage 0S JAN Build then without rebooting installed Lineage Nightly build (Latest) with Gapps After rebooting Phone goes into Restart endless loop on ZUK Logo. Blink and Vibrate .. After 1hr I figured it out but its 5am So slept.
HOW TO FIX ENDLESS REBOOT ON ZUK Logo ?
-> Identity vibrate patterns (Press Power Key I count 6- 7 Vibration pattern ) After long Vibrate immediately remove finger from power key.
->Once its Done (Phone completely off)
Download QPST and Official COS QPST from this Link https://goo.gl/InWQji OR https://goo.gl/iqrnlI (I am personally Very Thankful to D tech Terminal for posting Wonderful video on Youtube https://www.youtube.com/watch?v=4Dl6JkAVpuM
<- please install all drivers and software.->) @ankurpandeyvns Thanks bro.
Main Task is here and Lots of Patience is required and You also need to be very Blazing fast to achieve this.
-Once you download and install Qpst open Qfil
-Now press Volume Up only and connect USB (Just press POWER KEY only for 1 sec It will vibrate and connect)
-Without waiting hit Download button.
-Voila It will start flashing your phone again and Hence Your phone is now Revive..
-Once Revive You can use it to again flash custom Rom or stick to stock Rom if you want.
Keep Flashing !!!
Patience is Key here. And Don't lose hope.
:good:
EDITED:
While connecting to pc and by pressing Volume key you also need to press Power key for 1 sec or 2 sec until it gets detected. Thanks addicted777 (for tip)
rajendra0072 said:
Sorry For Re-posting Here. This is Solution
Why this is happening ?
Due to Dirty Flash from Zui or from COS/CMOD but suddenly Bootloader gets locked
May be Due to Some Custom Rom which only works with Old Bootloader ( And you are on latest 2.5 Zui QPST Flash)
Reasons are many. I also did same mistake. I flashed ZUI 2.5 using QPST then unlock bootloader using official site installed twrp after wiping cache system and data , Installed Lineage 0S JAN Build then without rebooting installed Lineage Nightly build (Latest) with Gapps After rebooting Phone goes into Restart endless loop on ZUK Logo. Blink and Vibrate .. After 1hr I figured it out but its 5am So slept.
HOW TO FIX ENDLESS REBOOT ON ZUK Logo ?
-> Identity vibrate patterns (Press Power Key I count 6- 7 Vibration pattern ) After long Vibrate immediately remove finger from power key.
->Once its Done (Phone completely off)
Download QPST and Official COS QPST from this Link https://goo.gl/InWQji OR https://goo.gl/iqrnlI (I am personally Very Thankful to D tech Terminal for posting Wonderful video on Youtube https://www.youtube.com/watch?v=4Dl6JkAVpuM
<- please install all drivers and software.->) @ankurpandeyvns Thanks bro.
Main Task is here and Lots of Patience is required and You also need to be very Blazing fast to achieve this.
-Once you download and install Qpst open Qfil
-Now press Volume Up only and connect USB (Just press only for 1 sec It will vibrate and connect)
-Without waiting hit Download button.
-Voila It will start flashing your phone again and Hence Your phone is now Revive..
-Once Revive You can use it to again flash custom Rom or stick to stock Rom if you want.
Keep Flashing !!!
Patience is Key here. And Don't lose hope.
:good:
Click to expand...
Click to collapse
I'm happy that my videos were helpful. Enjoy.
keeps vibrating showing logo again and again, neither won't turn off neither turn on till for so many hour until the charge is empty....
how to stop boot loop ??????
can you provide videos how to stop boot loop ??????
I just bought a wileyfox storm, then I followed the process to flash custom recovery and root the phone which done successfully.
After while I got an error massage and the desktop wont show up although I was able to access settings from status bar.
so I made a factory reset from recovery but didnt work
then downloaded the kipper rom from cyanogen but it wont pass the verification, it keep saying this is a crackling phone
So I downloaded the crackling rom for The SWIFT version and from recovery mode I flashed its zip file successfully,(PASSED THE VERIFICATION), then flashed supersu.zip.
I pressed reboot system
It shaut down but never come back to life, the only thing that works is the charging notification red light
Please Help
1- turn off your phone
2- plug it on pc with vol + pressed
3- now type on cmd "fastboot devices" normaly it appear
4- if you haven't unlocked bootloader unlock it with the command "fastboot oem unlock"
5- download cyanogen recovery from cyanogenmod site !!AND CHECK IF WRITEN RECOVERY FOR KIPPER!!
6- flash it via fastboot, type in cmd "fastboot flash recovery cyanogenmod-recovery-kipper.img
And wait
7- now type fastboot reboot
And press vol - during the reboot
8- now you're in cyanogen recovery, so flash the ROM and do not forget to wipe
bobslesbricoleurs said:
1- turn off your phone
2- plug it on pc with vol + pressed
3- now type on cmd "fastboot devices" normaly it appear
4- if you haven't unlocked bootloader unlock it with the command "fastboot oem unlock"
5- download cyanogen recovery from cyanogenmod site !!AND CHECK IF WRITEN RECOVERY FOR KIPPER!!
6- flash it via fastboot, type in cmd "fastboot flash recovery cyanogenmod-recovery-kipper.img
And wait
7- now type fastboot reboot
And press vol - during the reboot
8- now you're in cyanogen recovery, so flash the ROM and do not forget to wipe
Click to expand...
Click to collapse
Appretiate your kind response
Unfortunatly, this wont work for my case, I think I need a way to unbrick the phone, cant access to fast boot, my pc can see the phone only as CUALCOMM chip.
What's OS you're using?
bobslesbricoleurs said:
What's OS you're using?
Click to expand...
Click to collapse
Windows 7 X64
Did you install fastboot driver?
---------- Post added at 01:32 PM ---------- Previous post was at 01:31 PM ----------
Try to press vol + and vol - and power, tell if it vibrate?
bobslesbricoleurs said:
Did you install fastboot driver?
---------- Post added at 01:32 PM ---------- Previous post was at 01:31 PM ----------
Try to press vol + and vol - and power, tell if it vibrate?
Click to expand...
Click to collapse
Sir, I really appreciate your concern, but believe me it's a hard brick case, so I cant access any usual boot neither fastboot nor recovery.
I wish someone tells me how to unbrick it.
Plug usb and try two vol button in same time, tell me if vibrate, if not let it charge during 1 hour and retry
bobslesbricoleurs said:
Plug usb and try two vol button in same time, tell me if vibrate, if not let it charge during 1 hour and retry
Click to expand...
Click to collapse
Nothing happened, even after recharging
There is a probleme, you've just flashed the swift ROM, not really a reason to brick...
And the swift have same partition like the storm.
Where do you live? Me in france
bobslesbricoleurs said:
There is a probleme, you've just flashed the swift ROM, not really a reason to brick...
And the swift have same partition like the storm.
Where do you live? Me in france
Click to expand...
Click to collapse
I'm in Egypt
When i googled my problem i found the same happend with oneplus one phones,
The problem was hard brick due to wrong rom, and windows can see the phone only as Cualcomm hs-usb Qdloader 9008, same as my case. And the problem solved for the oneplus one, so I have some hope that my phone will come back to life.
kazparoph said:
I'm in Egypt
When i googled my problem i found the same happend with oneplus one phones,
The problem was hard brick due to wrong rom, and windows can see the phone only as Cualcomm hs-usb Qdloader 9008, same as my case. And the problem solved for the oneplus one, so I have some hope that my phone will come back to life.
Click to expand...
Click to collapse
Good news, if your problem is solved please post how you do on this thread or new to explain the tutoriel
bobslesbricoleurs said:
Good news, if your problem is solved please post how you do on this thread or new to explain the tutoriel
Click to expand...
Click to collapse
Ofcourse I will.
bobslesbricoleurs said:
Did you install fastboot driver?
---------- Post added at 01:32 PM ---------- Previous post was at 01:31 PM ----------
Try to press vol + and vol - and power, tell if it vibrate?
Click to expand...
Click to collapse
Hi I have a similar problem, I installed the correct cyanogenmod and recovery and it was working fine, but after today's update it shows the bootup logo and then gets stuck in a black flickering screen.
I can't seem to be able to boot neither to the recovery nor to the fastboot mode, no volume key combination seems to work.
All adb says is the device is unauthorized and fastboot doesn't seem to be able to even see the device.
I tried the vol+ and vol- and power and it does vibrate, if I use the vol+ only it seems to get stuck forever on the vendor's bootup logo and the device doesn't seem to be seen neither from fastboot nor adb.
Is there anything else I can try to unbrick it or is it gone?
Thank you in advance for your help
kazparoph said:
I just bought a wileyfox storm, then I followed the process to flash custom recovery and root the phone which done successfully.
After while I got an error massage and the desktop wont show up although I was able to access settings from status bar.
so I made a factory reset from recovery but didnt work
then downloaded the kipper rom from cyanogen but it wont pass the verification, it keep saying this is a crackling phone
So I downloaded the crackling rom for The SWIFT version and from recovery mode I flashed its zip file successfully,(PASSED THE VERIFICATION), then flashed supersu.zip.
I pressed reboot system
It shaut down but never come back to life, the only thing that works is the charging notification red light
Please Help
Click to expand...
Click to collapse
wow, exact same thing, kept saying my device is a crackling device so i flash a crackling rom, it went dead flash!
Please stop flashing crackling roms on kipper.
If it reports crackling is wrong maybe ota somehow messed up.
kazparoph said:
I just bought a wileyfox storm, then I followed the process to flash custom recovery and root the phone which done successfully.
After while I got an error massage and the desktop wont show up although I was able to access settings from status bar.
so I made a factory reset from recovery but didnt work
then downloaded the kipper rom from cyanogen but it wont pass the verification, it keep saying this is a crackling phone
So I downloaded the crackling rom for The SWIFT version and from recovery mode I flashed its zip file successfully,(PASSED THE VERIFICATION), then flashed supersu.zip.
I pressed reboot system
It shaut down but never come back to life, the only thing that works is the charging notification red light
Please Help
Click to expand...
Click to collapse
Have you tried to hold together for about 20 seconds the power button and sound button less ?
Strugglin
I have same problem, either stuck in bootloop (to the wileyfox screen and back to black) or just off. ONLY red charger light shows when I plug it in. Fastboot not working, recovery boot not working... NOTHING is working. On top of that I haven't even installed any roms, not rooted etc. All I did was reboot when it froze on a silly game I didn't mean to open WTFF
wileyfox dead
I have the same problem, bootloop, qualcomm 9008 no fastboot or adb recognition. I'm guessing was the OTA update cos I didn't install any roms at all. TOTAL waste of money, zero support too. It's a non-starter DO NOT BUY!!!!
maxxie00 said:
Hi I have a similar problem, I installed the correct cyanogenmod and recovery and it was working fine, but after today's update it shows the bootup logo and then gets stuck in a black flickering screen.
I can't seem to be able to boot neither to the recovery nor to the fastboot mode, no volume key combination seems to work.
All adb says is the device is unauthorized and fastboot doesn't seem to be able to even see the device.
I tried the vol+ and vol- and power and it does vibrate, if I use the vol+ only it seems to get stuck forever on the vendor's bootup logo and the device doesn't seem to be seen neither from fastboot nor adb.
Click to expand...
Click to collapse
Same here , interesting is the different device status between linux and windows,
at debian it's "offline" - at windows "unauthorized".
Have searched the forum but came up empty.
Hoping someone can help.
Purchased the phone used back in December and have been using it as-is. Two OTA updates came through fine. The latest OTA update has it stuck in a boot loop.
- I can get to fastboot with power and volume down buttons but all of the options either turn it off or stick it back in the loop again (Essential logo with powered by Android, NO dot animation)
- Can't see it via "adb devices" since developer mode was likely not enabled
- "fastboot devices" can see the phone but can't change slots or do anything else
I saw two other people who've posted something similar but no solution. Is my phone garbage?
Any help is appreciated.
harpoon said:
Have searched the forum but came up empty.
Hoping someone can help.
Purchased the phone used back in December and have been using it as-is. Two OTA updates came through fine. The latest OTA update has it stuck in a boot loop.
- I can get to fastboot with power and volume down buttons but all of the options either turn it off or stick it back in the loop again (Essential logo with powered by Android, NO dot animation)
- Can't see it via "adb devices" since developer mode was likely not enabled
- "fastboot devices" can see the phone but can't change slots or do anything else
I saw two other people who've posted something similar but no solution. Is my phone garbage?
Any help is appreciated.
Click to expand...
Click to collapse
Damn, that's a bit unlucky, this March update said it would make recovery from a loop after OTA update easier to recover from, which might just have helped you. Sorry not sure how to help fix at present.
you can try flashing one of these https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
be sure to pick one with the fastboot images
harpoon said:
- Can't see it via "adb devices" since developer mode was likely not enabled
- "fastboot devices" can see the phone but can't change slots or do anything else
Click to expand...
Click to collapse
A couple of questions:
- Is your BL unlocked (or is OEM Unlocking enabled)?
What happens if you try executing "fastboot flashing unlock"? NOTE: this would WIPE your data if successful.
- Can you get to the Recovery mode? It's when you pick "Recovery" option from fastboot mode, see the lying android with an exclamation sign, then hold Power and press VolumeUp to get to the Recovery menu.
kt-Froggy said:
A couple of questions:
- Is your BL unlocked (or is OEM Unlocking enabled)?
What happens if you try executing "fastboot flashing unlock"? NOTE: this would WIPE your data if successful.
- Can you get to the Recovery mode? It's when you pick "Recovery" option from fastboot mode, see the lying android with an exclamation sign, then hold Power and press VolumeUp to get to the Recovery menu.
Click to expand...
Click to collapse
Thanks for your response.
- I dont belive OEM unlocking is enabled.
- I can get to the fastboot menu, but the recovery mode option just takes me back to the 'powered by android' logo, not the green dead robot.
- When I try fastboot flashing unlock, I get the below error:
=============
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.013s
=============
yenkoPR said:
you can try flashing one of these https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
be sure to pick one with the fastboot images
Click to expand...
Click to collapse
Will this work even though I cannot see the device via adb? AND the device state is "locked".
harpoon said:
- I dont belive OEM unlocking is enabled.
- I can get to the fastboot menu, but the recovery mode option just takes me back to the 'powered by android' logo, not the green dead robot.
- When I try fastboot flashing unlock, I get the below error:
Click to expand...
Click to collapse
Dang... :\ Yeah, the last error means you don't have OEM unlock enabled. So, you can't flash the bts image via fastboot. One last thing I could think of is trying to get to recovery by the button combo. Although, if you are correct in saying you don't have USB debug enabled, it won't do much good, i.e. you won't be able to flash an OTA... :\
While device is OFF, press and hold Volume-Up button while pushing Power button to boot.
Your device will now be in Recovery mode. An Android logo with red exclamation mark should appear on screen. Hold the Power button, then press the Volume-Up button one time to see the recovery menu.
can you try this command on bootloader:
fastboot OEM unlock
harpoon said:
Have searched the forum but came up empty.
Hoping someone can help.
Purchased the phone used back in December and have been using it as-is. Two OTA updates came through fine. The latest OTA update has it stuck in a boot loop.
- I can get to fastboot with power and volume down buttons but all of the options either turn it off or stick it back in the loop again (Essential logo with powered by Android, NO dot animation)
- Can't see it via "adb devices" since developer mode was likely not enabled
- "fastboot devices" can see the phone but can't change slots or do anything else
I saw two other people who've posted something similar but no solution. Is my phone garbage?
Any help is appreciated.
Click to expand...
Click to collapse
Hi. A long time has passed and I want to know if you have solved your problem. I came across the same)
Rudter said:
Hi. A long time has passed and I want to know if you have solved your problem. I came across the same)
Click to expand...
Click to collapse
Nothing ! ..
my ph-1 still into the drawer ! .
I want to boot the phone to bootloader mode. However, when I come to the recovery mode, it says "[libfs_mgr]Error updating for slotselect" at the very bottom of the screen.
If I continue to choose Reboot to bootloader, it prints the same error message again a second time, and very quickly (less than 1s) reboots to the OS. So I can't go to the bootloader.
If anyone knows what happen and how to fix it, please help. Many thanks.
My phone is a totally new one:
- Model: Samsung Galaxy A73 5G
- Code name: SM-A736B/DS
d_t_kien said:
I want to boot the phone to bootloader mode. However, when I come to the recovery mode, it says "[libfs_mgr]Error updating for slotselect" at the very bottom of the screen.
If I continue to choose Reboot to bootloader, it prints the same error message again a second time, and very quickly (less than 1s) reboots to the OS. So I can't go to the bootloader.
If anyone knows what happen and how to fix it, please help. Many thanks.
My phone is a totally new one:
- Model: Samsung Galaxy A73 5G
- Code name: SM-A736B/DS
Click to expand...
Click to collapse
same issue with flip z 3
any solve for this problem yet ?
rassam said:
same issue with flip z 3
Click to expand...
Click to collapse
I have the same problem on the SM-A528B and any rom that installs even the originals with the bootloader locked to the original settings, still, my tele keeps blinking as if it had superimposed images... If anyone has a backup of the ROM STOCK, obviously without the data and EFS and can make it available I would appreciate it, I think it's some partition error, but so far I haven't been able to find any tutorial to clean and reinstall from scratch...
eslam.essa.2011 said:
any solve for this problem yet ?
Click to expand...
Click to collapse
This is what i did to solve
from PC adb reboot recovery --> Reboot to recovery
Select reboot to bootloader ---same time press both volume up and down and press power key to select.
somehow booted to bootloader downloading mode..try and update, thanks.
ansaziz777 said:
This is what i did to solve
from PC adb reboot recovery --> Reboot to recovery
Select reboot to bootloader ---same time press both volume up and down and press power key to select.
somehow booted to bootloader downloading mode..try and update, thanks.
Click to expand...
Click to collapse
Thanks it really works
ansaziz777 said:
This is what i did to solve
from PC adb reboot recovery --> Reboot to recovery
Select reboot to bootloader ---same time press both volume up and down and press power key to select.
somehow booted to bootloader downloading mode..try and update, thanks.
Click to expand...
Click to collapse
Thanks it really works
Marcelo Rock said:
I have the same problem on the SM-A528B and any rom that installs even the originals with the bootloader locked to the original settings, still, my tele keeps blinking as if it had superimposed images... If anyone has a backup of the ROM STOCK, obviously without the data and EFS and can make it available I would appreciate it, I think it's some partition error, but so far I haven't been able to find any tutorial to clean and reinstall from scratch...
Click to expand...
Click to collapse
ansaziz777 said:
This is what i did to solve
from PC adb reboot recovery --> Reboot to recovery
Select reboot to bootloader ---same time press both volume up and down and press power key to select.
somehow booted to bootloader downloading mode..try and update, thanks.
Click to expand...
Click to collapse
PodrÃas ayudarme a hacerlo?