I tried to upgrade an old LG P-350 and - well, things went spectacularly wrong. Suffice it to say that when I turn it on, this is what I get on the screen:
Fastboot mode started
udc_start()
The phone does not seem to be utterly bricked, for when I connect it via USB to my Linux box here is the extra output I get on the screen of the P-350:
-- suspend --
-- reset --
-- portchange --
-- reset --
-- portchange --
STALL GET _DESCRIPTOR 128 6 38400 0 5
STALL GET _DESCRIPTOR 128 6 38400 0 5
STALL GET _DESCRIPTOR 128 6 38400 0 5
fastboot: processing commands
A Google search reveals that people have encountered similar issues, and solutions have been proposed. However, so far those solutions just plain don't work, due to incomplete and/or incorrect instructions, or simply because the symptoms are not quite the same as I am describing here.
Anybody got suggestions on how to get this handset out of this situation? I am not an XDA developer so please be specific.
I found out how to fix the problem. Thanks everybody for your feedback.
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
SomewhatIrked said:
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
Click to expand...
Click to collapse
Did your phone just reboot in the middle of doing something innocuous then start bootlooping? Were/Are you on total stock with bootloader locked? If both yes, it is probably hardware issue you are encountering.
Regarding sideloading, did you place your Android recovery in sideload mode?
Did you verify adb can "see" your device using "adb devices"?
SomewhatIrked said:
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
Click to expand...
Click to collapse
Well luckily I made this post today.
The more this goes on, the more I believe it to be hardware ...
@sfhub - reasonably innocuous. Had just opened one or 2 apps that morning. Not sure what had updated overnight app/os wise. Not anything interesting as far as I can tell. Once I managed to get it into recovery "adb devices" was returning the phone.
@bardhi92 - I saw that once I got in. However, I couldn't get it to see my phone.
Updated things I have tried and why I've all but thrown in the towel:
After the OTA rescue sideload failed I started trying a few different things. It stopped taking me into recovery mode more frequently, at least it seemed that way - it would just keep bootlooping. My main issue is that I has a locked bootloader, which stopped me whacking TWRP on and loading on a custom rom - just to see if that worked.
I thought it might let me sideload on a factory default img file. Turns out nope.
However I used NRT to "Flash Stock + Unroot" (with "Soft Brick/Bootloop" checked) which for some reason, then allowed me to get back into recovery mode. I had also removed the sim card/tray at this point. May have been either or neither of those that allowed me to get into recovery mode. Can't say for certain.
I cleared /cache and /data and then attempted the OTA rescue update again. This time it failed at 45% (according to my cmd prmpt) with the error: "* failed to read command: No error". I'm not sure text was on the phone at the time. But it did manage to boot into Android. I quickly stepped through the various intro steps (putting in the sim, adding my mail google account details).
I went to get a beer. Only to find it boot looping again.
Not to be deterred, I vowed to try again. Same steps as before (remove sim, nrt voodoo). This time however the OTA rescue worked and fully completed. I went through the intro steps again. This time I quickly turned on dev options, enabled usb debugging and sorted out the OEM bootloader. I thought this would be smart, just in case it hapened again. Once I chose to unlock ("fastboot reboot", selected yes), it decided to start boot looping again.
The main annoyance is: I don't think I have any proof of purchase, even though it's in warranty. That, and I now live in Dubai - so shipping back to the UK where I brought it is going to be killer. But I think it's the path of least resistance at the moment.
SomewhatIrked said:
The more this goes on, the more I believe it to be hardware ...
@sfhub - reasonably innocuous. Had just opened one or 2 apps that morning. Not sure what had updated overnight app/os wise. Not anything interesting as far as I can tell. Once I managed to get it into recovery "adb devices" was returning the phone.
@bardhi92 - I saw that once I got in. However, I couldn't get it to see my phone.
Updated things I have tried and why I've all but thrown in the towel:
After the OTA rescue sideload failed I started trying a few different things. It stopped taking me into recovery mode more frequently, at least it seemed that way - it would just keep bootlooping. My main issue is that I has a locked bootloader, which stopped me whacking TWRP on and loading on a custom rom - just to see if that worked.
I thought it might let me sideload on a factory default img file. Turns out nope.
However I used NRT to "Flash Stock + Unroot" (with "Soft Brick/Bootloop" checked) which for some reason, then allowed me to get back into recovery mode. I had also removed the sim card/tray at this point. May have been either or neither of those that allowed me to get into recovery mode. Can't say for certain.
I cleared /cache and /data and then attempted the OTA rescue update again. This time it failed at 45% (according to my cmd prmpt) with the error: "* failed to read command: No error". I'm not sure text was on the phone at the time. But it did manage to boot into Android. I quickly stepped through the various intro steps (putting in the sim, adding my mail google account details).
I went to get a beer. Only to find it boot looping again.
Not to be deterred, I vowed to try again. Same steps as before (remove sim, nrt voodoo). This time however the OTA rescue worked and fully completed. I went through the intro steps again. This time I quickly turned on dev options, enabled usb debugging and sorted out the OEM bootloader. I thought this would be smart, just in case it hapened again. Once I chose to unlock ("fastboot reboot", selected yes), it decided to start boot looping again.
The main annoyance is: I don't think I have any proof of purchase, even though it's in warranty. That, and I now live in Dubai - so shipping back to the UK where I brought it is going to be killer. But I think it's the path of least resistance at the moment.
Click to expand...
Click to collapse
So, you flashed the .TOT file, sideloaded the given OTA within the stock recovery bootloader that comes with the .TOT file, and cleared cache/factory reset?
Please condense it. If you managed to start up the phone, that's a huge success for people who have not been able to yet.
bardhi92 said:
So, you flashed the .TOT file, sideloaded the given OTA within the stock recovery bootloader that comes with the .TOT file, and cleared cache/factory reset?
Please condense it. If you managed to start up the phone, that's a huge success for people who have not been able to yet.
Click to expand...
Click to collapse
In short:
OTA rescue failed during adb sideload,
Tried bullhead-nbd90w-factory-d2f11c5f.zip & removed sim tray - seemed to allow access to recovery mode,
OTA rescue claims to have failed at 47% during adb sideload- still booted into android. However briefly. Went back to bootloop,
Tried bullhead-nbd90w-factory-d2f11c5f.zip & removed sim tray - seemed to allow access to recovery mode,
OTA rescue completed via adb sideload,
Turned on dev options (usb debug, oem unlock),
Booted to fastboot - unlocked bootloader. Now back to bootlooping
@bardhi92 - I could not get the LG utility to detect my phone. Will attempt again tomorrow.
SomewhatIrked said:
@bardhi92 - I could not get the LG utility to detect my phone. Will attempt again tomorrow.
Click to expand...
Click to collapse
IMO you shouldn't flash the TOT file. If you end up bootlooping again, your phone will be stuck in bootloader locked mode with no ability to unlock it.
If you were able to get your phone to boot into android once, there is really nothing the TOT file will do for you that you can't do from TWRP or bootloader, whereas once it locks your bootloader, there are problems you can no longer fix like EFS corruption (which likely isn't your problem).
In the end, you probably do have eMMC that is slowly starting to fail. There is usually error correction on the eMMC that can lock out bad blocks but if it gets to serious, it'll fail. This is why reflashing stuff over and over sometimes works.
Hi i have bootloop problems on this device. When i do factory reset in recovery mode samsunf logo blinks as it wants to start system but it restarts. Then second time samsung logo doesnt even finish until i do factory reset then logo blinks again and restarts after some time.
The code is (reboot recovery cause is check_boot_mode recoverybootmodewithkey)
Block based ota
Ive tried to flash device multiple times with different stock roms with same results.
If i flash with oreo its the same error code but with addition when doing fastory reser something about some cache in first deletion and a number 0
In pie that code is not present which i assume that device is ment for pie. Both frp and oem are locked.
When i flash combination file its rpmb provisioned and rpmb fused 1. In z3x box there is no option to fix that. And that is strange because as i remember while i was doing repair on samsung s8 it was easy. Factory binary was there but not on this budget model which is strange. I even tried to force error so it triggers emergency recovery mode for smart switch but smart switch is just aweful. I dont even get recognition in that program. It shows as unsuppported model. I reinstalled drivers as well it just doesnt work. Now i would be glad and it would be awesome to get into fastboot mode just so i write down commands. Adb sideload doesnt have those options. Since i understood adb and fastboot for me its number one solution for everything. But how the hell am i supposed to get into fastboot on this model. Im pretty sure block based ota is sign that its blocked becuase of oem unlock aka locked bootloader. Its a friends phone and i tell people dont do stuff if you dot know ehat you are doing. But even locked bootloaders and frp locked are fixable. Especially with multiple brains on XDA and GSMforums.
Does anybody have any solutuon to this problem because this is some kind of new security method which was not present on like 2 years before.
P. S Is there any combination out there made out of Pie?
I fixed the issue. Front camera was defected. Some type of short circuit. Main camera auto focus mechanism also defected. It works allright as soon you detach all cameras. The only problem which i have with this device is that Samsung is using same concept as HTC. One camera defected all cameras not working. This is new from Samsung because in past when one camera brakes camera app still works. Autofocus mechanism can break with fall of the phone. Its not an software issue!!!
i have a similar problem do find solution?
I recently tried to install a custom ROM in my samsung j6+ but halfway through it my PC turned off.
Then the problem starts i decided to reboot my phone but it shows this error "No command" " #Reboot recovery cause is [[check_bootmode]RebootRecoveryWithKey]#
Block-based OTA
Supported API: 3
# MANUAL MODE v1.0.0#
E:Failed to mount / cache: Invalid argument
The error message keeps appearing for just a fraction of a second then disappear and appear again
I tried to go to recovery mode but no luck i cant get to it
I drained the battery to turn off the device then go download mode but after get to it, it also keep restarting
help me please. thank you
I am following this guide
gearallnews.___/how-to-install-lineage-os-17-on-umidigi-a5-pro/ (sorry for the circumvent. felt it was important for the pros to check the source)
since I have a newer phone (at the time of this writing) Android 9.
but regardless of the above site or any instructions regarding "adb" and "fastboot" it always takes me to the black screen with tiny print at the bottom that says "fastboot mode.." and thats it. If I just do Vo+Pow it will take me to a menu from clearing cash to rebooting the system and factory reset. Can even boot to bootloader, but it gives me the same black screen with those tiny words at the lower left of the screen, everything else is blank.
I have to use the power button to shut off, then again to reboot to normal.
when I type fastboot devices, nothing,
adv devices (before the boot) will show the correct phone
All the other UMIDIGI AS5 PRO tutorials seem to work fine.
This is a dual sim, unlocked phone.
Any suggestions?
OK fixed all the issues (a5 pro driver missing, FIXED, mtk67xx installed)
(thought) I installed TWRP but when booting to bootloader, all it says is "fastboot mode..." and the screen in blank
So tried a different method, by rooting this from scratch, so first thing was to make a scatterfile.txt
Powered up the MTK DROID ROOT & TOOLS and got the following message (of course because of this, cannot use the ROOT button successfully)
Code:
--->>> Connect to device <<<---
--- ERROR : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!
--- Unknown ROM structure, backup NOT possible!
ATTENTION! File /system/recovery-from-boot.p which restore factory recovery in case of phone switching on in a normal mode Is Found!
"/data/local/tmp/pwn": error: Android 5.0 and later only support position-independent executables (-fPIE).
ATTENTION! Requests for confirmation on the device screen are possible!
What to I have to fix/clean up?
Thanks for any suggestions
EDIT: Yes the phone is still working fine, (other than th emessage the phone is not safe because the booloader is not locked)
Hello, I would like your help with my problem, I have a Xiaomi Redmi Note5, I was using it normally, I put it on the sofa and 10min later I see that thescreen is black and the buttons are not responding. So I decide to press the power button and the Mi logo appears, except that it ends there. The phone no longer boots on Android.
What I want above all is to recover my data, mainly my photos. (No I haven't activated the google cloud, I checked and there is nothing)
I think the problem is related to the storage of the phone which has saturated, for 2 3 days I had a message that there was less than 1.5G of storage left. My guess is that the storage has reached 100% and so the phone is bricked .. But that's just a guess.
I've read a lot to find a solution, but I don't have developer mode enabled or OEM unlock. I managed to use the fastboot mode and display the line with the phone id through the command: fastboot devices
On the other hand it is locked so impossible to use ADB, to my knowledge.
The recovery mode (volume up + power) does not seem to work, because nothing is happening.
I tried to load TWRP:
C:\adbfastboot flash recovery "twrp.img"
targetreported max download size of 536870912 bytes
sending'recovery' (42456 KB)...
OKAY [ 1.102s]
writing'recovery'...
FAILED(remote: Flashing is not allowed in Lock State)
I tried to unlock OEM :
C:\adbfastbootoem unlock
FAILED remote:Token Verify Failed, Reboot the device)
I also thought about emptying the cache in case it is the storage problem:
C:\adbfastbooterase cache
********Did you mean to fastboot format this ext4 partition?
erasing'cache'...
FAILED(remote: Erase is not allowed in Lock State)
Others infos:
C:\adbfastbootoem device-info
(bootloader)Verity mode: true
(bootloader)Device unlocked: false
(bootloader)Device critical unlocked: false
(bootloader)Charger screen enabled: false
I saw that there is an EDL technique by creating a contact (test point) in the phone, and I am ready to try that, I have already removed the back cover,but I did not find any info on how to use it to retrieve my data, only for fashing and wiping all the config… but that's really not what I want. If you know a technique allowing me to recover my data, I'd be glad.
Thanks for your help