[Q] Help!!! aka "is my phone bricked?" - Motorola Droid and Milestone General

So i plugged in my Milestone to my PC and ran the Motorola Software Update, in hopes that 2.2 will get flashed.
Everything went smoothly until the update stopped and my phone was stuck with "SW Update In progress... " on the screen. The Motorola program on my PC had disappeared.
I waited for a bit but nothing happened to my phone, so I took out the battery and rebooted it. Then it booted into the bootloader and said shows "Err:A5,69,4E,00,3D".
Tried to boot into Recovery (i rooted my phone with openrecovery a few months back) but same, won't load recovery, won't boot Android either. Same error message.
Then I tried to flash the vulnerable SBF again, RSDLite shows all ok but I still can't enter into Recovery mode. Then I tried to flash the whole SBF instead of just the vulnerable recovery, and RSDlite stopped at 19% with this error:
ERROR: Flash failure: Phone[0000]: Error flashing subscriber unit. Device API Error: 0xE003003F Address: 0xD304DB80 Command: ADDR (Error Code: e003003f),
Detailed Error Details: Direction of the Error=2000, Command Value=200000, Code Group Number=39
Device ID: 0
Click to expand...
Click to collapse
Did Google search on this, found nothing useful, I don't know what is the problem. Have tried UK, HK and SG firmware but nothing works. Did my phone just become a brick? Now the IMEI and other details doesn't even show up on RSDLite anymore...
My system is Windows 7 32-bit, using RSDLite 4.9, latest drivers (4.8.0). Here is the full RSDLite log:
00:21:44, January 25, 2011
Line: 527
ERROR: AP Die ID: 22700114fe980304000000002400
00:21:44, January 25, 2011
Line: 534
ERROR: BP Die ID: 0000000000000000000000000000
00:21:44, January 25, 2011
Line: 541
ERROR: AP Public ID: 449dd7999eac8318cda5dc848722cd304fb725de
00:21:44, January 25, 2011
Line: 548
ERROR: BP Public ID: 0000000000000000000000000000000000000000
00:25:42, January 25, 2011
Line: 340
ERROR: Phone[0000]: Error flashing subscriber unit. Device API Error: 0xE003003F Address: 0xD304DB80 Command: ADDR
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
00:25:42, January 25, 2011
Line: 1190
ERROR: Phone[0000]: Flash failed.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
00:25:42, January 25, 2011
Line: 597
ERROR: Flash failure: Phone[0000]: Error flashing subscriber unit. Device API Error: 0xE003003F Address: 0xD304DB80 Command: ADDR (Error Code: e003003f),
Detailed Error Details: Direction of the Error=2000, Command Value=200000, Code Group Number=39
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
Click to expand...
Click to collapse

What about the bootloader mode (aka fastboot mode)?
Does that work? Does a "fastboot devices" work at that point?
If fastboot sees your devices, you could flash from there.
Fastboot gives you the option to flash an update.zip, a specific partition or all partitions...
Sent from my Milestone using Tapatalk

A855 Boot Loop
Rooted - Rom Manager Clockwork Mod install
Liquid Frozen Yogurt 1.95
Phone boots to animation screen and reboots
Can not reboot into recovery
Will boot into bootloader
ADB recognizes phone when it is at animation screen in windows - "adb reboot recovery" reboots phone but not into recovery - same for "adb reboot bootloader"
Suggestions?
Love,
Guy with a pretty paperweight

Related

help me rsd lite error msg

help me error message rsd lite flashing error
iam used Droid a855 and bootloader 2c7c FRG32D
Code:
08:13:04, March 09, 2011
Line: 527
ERROR: AP Die ID: 1a90011715680304000000002400
08:13:04, March 09, 2011
Line: 534
ERROR: BP Die ID: 0000000000000000000000000000
08:13:04, March 09, 2011
Line: 541
ERROR: AP Public ID: ffffffffffffffffffffffffffffffffffffffff
08:13:04, March 09, 2011
Line: 548
ERROR: BP Public ID: 0000000000000000000000000000000000000000
08:20:33, March 09, 2011
Line: 962
ERROR: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE003003F Address: 0x152000 Command: ADDR
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\RDLOp.cpp
Device ID: 0
08:20:33, March 09, 2011
Line: 1190
ERROR: Phone[0000]: Flash failed.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
08:20:33, March 09, 2011
Line: 597
ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE003003F Address: 0x152000 Command: ADDR (Error Code: e003003f),
Detailed Error Details: Direction of the Error=2000, Command Value=200000, Code Group Number=257
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
and now restart the phone normal but cannot flashing the prl
I am Having Same issue. Phone Keeps failing. tried on Multiple computers and multiple os's (Windows 7 32/64, ubuntu) nothing seems to work. Only thing I have done to phone is Adeo (REDUX) and Superuser.
Now I want to go to 1.5.7 and I can not. I am attempting to flash back to vanilla 1.2.6 and am getting this error. ANY help with this would be greatly appreciated!
Been at this for a week now
BTW, Mine in an Atrix (AT&T) but same issue

[Q] Motorola Milestone Custom Roms? Locked Bootloader? Howto?

Well, hello guys i bought a Motorola Milestone from a friend yesterday.
And I'm that annoying kid that will probably step on your lawn again and again, but i apologize in advance for my stupid questions that will probably come after this.
But i have been at it for about 6-7 hours googling bouncing around to you youtube.
I was up halfway through the night yesterday to find a way to flash my phone with Cyna cyanogenmod.com
And through tutorials wiki.cyanogenmod.com/wiki/Motorola_Droid:_Full_Update_Guide
When i get to step:
9. Once it is selected, hit Start and wait for it to finish flashing the device.
10/28/11 12:18:51 New Log Started For Software Download.
10/28/11 12:18:55 00000de0 Phone.cpp 450 0 ERROR Generic failure when sending command.
10/28/11 12:18:55 00000de0 Phone.cpp 1556 0 ERROR GetPhoneID failed: ERROR.
10/28/11 12:19:01 The FlashLog key is turned off.
10/28/11 12:19:02 Multi upgrade started for 1 phones
10/28/11 12:19:02 [Device ID: 0] Flashing phone.
10/28/11 12:19:02 ERROR: Phone[0000]: Phone is not compatible with multi-interface super-file. - on device ID 0.
10/28/11 12:19:02 ERROR: Flash failure: Phone[0000]: Phone is not compatible with multi-interface super-file. (Error Code: 3b),
Detailed Error Details: Direction of the Error=No Direction, Command Value=0, Code Group Number=No Codegroup - on device ID 0.
10/28/11 12:19:02 [Device ID: 0] Phone[0000]: Phone is not compatible with multi-interface super-file.
10/28/11 12:19:03 Multi upgrade finished.
I get this error through searching someone said it was a bug place the *.sbf file in C:\, My documents i tried that same error.
I tried different versions of RSD lite i tried patching the pst_flash.ini file.
After i got shutdown here i tried to push a recovery image through my computer using recovery.img.
adb shell
adb flash_image bla bla bla
i get the error access denied.
Is there any ****ing way to give my telephone a custom rom or change my default Androd bootloader recovery for rom managers?
After a while i found this, i tho to myself was the bootloader locked the whole ****ing time?
ausdroid.net/2011/06/14/an-update-on-motorolas-locked-boot-loader-situation/
ausdroid.net/2011/04/27/confirmation-motorola-to-unlock-bootloaders-for-future-android-devices
If some kind soul out there could spread some light on my issues i will be in your debt forever.
P.S sorry for all the f*cks D.S
The Droid and Milestone are very similar, but have important differences. The Milestone has a locked bootloader, while the Droid doesn't. When it comes to rooting the Milestone and installing a custom ROM, steer clear of instructions for the Droid. It'll get you nowhere.
http://www.droid-developers.org/wiki/CyanogenMod_4_Milestone_FAQ
http://android.doshaska.net/cm7

[Q]CWM boot loop.Can't mount /emmc.nvflash not working.please help-SOLVED via nvflash

Friends..i am beginner+ to this forum.. i got stuck in a bad problem(bootloop) below. Please help me to save my O2x
Thanks in advance and appreciate all your help ..!!
Reason for bootloop:
===============
Flashed temasek CM7 and it worked perfectly.
Then flashed Horsepower 2X extreme kernel and it came up and worked.
Then when i re-started the phone, it enters into BOOTLOOP and stuck there forever.
Logs here:
--------------
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Tried below solutions:
===============
Read forums and tried Nvflash. Even it didn't work out. Exception are sometimes with bad data and other with Bootloader not specified.
Please suggest me some solutions to overcome this pblm...
See log below:
----------------------
Russ' NVFlash Recovery Flasher
1. CWM 4.0.1.5 Internal
2. CWM 4.0.1.5 External
X. Exit
-------------------------------
Please pick a recovery, or exit [1,2,X]?1
Attempting to flash internal recovery...
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x038820c440c09417
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
| 983040/1024992 bytes sentdata send failed NvError 0x120000
command failure: bootloader download failed
-------------------------------
Program will now exit
Press any key to continue . . .
Just reflash the Temasek ROM .zip and you'll probably be fine.
Re-flashestemask cm7..not working
wiped cache/data/david cache... and then flashed temask cm7 ...it again bootloops.... e:/can;t mount cache..
I tried with nandroid backup that i had taken during CM10..i didn't work out and bootloops...!!
Is there any possible solution to this ?
All my tries always ended up in -->
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Power it off, remove battery, hold vol- and insert USB cable.
If it shows something about SW Update on the screen, then just smartflash a stock ROM, then start again. Saves dicking around.
sw upgrade boot doesn't work either
Thanks for ur reply Rusty...!!
I tried SW upgrade boot also, it didn't work .. flashes lg logo and turns off... if i keep on holding vol - button, it blinks again and again.
I think i bricked my phone.. Internal sd-card /emmc,/cache)is not recognized/mounted.
It's pretty much impossible to brick it. NVFlash will fix it.
When you tried, was the phone plugged directly to the motherboard or through a hub/front ports? Direct is best.
Yes, i tried through serial port and tried with other port also, didn't enter S/W upgrade screen.. (Mine is Dell XP15 - win7 )
Have installed latest LG drivers and nvflash drivers are latest and showing up in device manager also..!!
Through nvflash it stucked - bad data or hangs for hours..!! (have tried changing data cable too)
Logs:
-------
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
\ 655360/1024992 bytes sentdata send failed NvError 0x120000
command failure: bootloader download failed
Is there any way to overcome this bad data error in nvflash ?
Any small clue to restore my O2X will be very helpful ..!!
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
data send failed NvError 0x120002
command failure: bootloader download failed (bad data)
vsnstarguy said:
Is there any way to overcome this bad data error in nvflash ?
Click to expand...
Click to collapse
Before giving up, borrow some time on a desktop computer, connect directly to a port on the motherboard, try again. Use a USB2 port.
Re- Use a USB2 port.
When i connect to usb3 ports, it detects APX device and 'NVIDIA USB Boot-recovery driver for Mobile devices' appears in device manager.:angel:
But when i try usb 2 port, it prompts as unkown device(usb device not recognized) -[ Lg drivers work with usb 3 ports] and not able to proceed further.
I have always used usb3 ports for rooting O2x and all- it went fine, should i still need to debug on usb2 unknown device issue ?
Nvflash worked..enters sw upgrade screen
Friends, nvflash works successfully and files sent successfully and phone enters S/W upgrade screen.
If i release usb cable, put the battery and power on with vol-down, it again enters into CWM and not S/W upgrade screen.
Need to know what are the next steps to do , also what are the files that i have to put in sdcard ?
addition to this.. adb also working..
Friends,.. now nvflash works and i am to do some basic ADB commands also..!! [Smartflash not working - due to phone not entering s/w upgrade]
C:\Users\Senthilnathan\AppData\Local\Android\android-sdk\platform-tools>adb shell
~ #
~ # ls
ls
boot init sys
cache init.rc system
data proc tmp
datadata res ueventd.goldfish.rc
default.prop root ueventd.rc
dev sbin ueventd.tegra.rc
emmc sd-ext
etc sdcard
Need your help - What are next steps i should do ? What are the files i need to download to make my O2x work? :fingers-crossed:
Well if you can ADB in recovery, I guess you should download a ROM, stick it on your SD card and flash it.
OR
Remove battery, hold vol down and plug in USB cable to get the S/W Update mode, then you can smartflash.
Rusty! said:
Well if you can ADB in recovery, I guess you should download a ROM, stick it on your SD card and flash it.
OR
Remove battery, hold vol down and plug in USB cable to get the S/W Update mode, then you can smartflash.
Click to expand...
Click to collapse
OR
http://forum.xda-developers.com/showthread.php?t=1054492
Smartflash not working.. removed battery, vol down and lug usb cable enters - just blinks again and again..
I tried adb to flash rom- below are the results... ( flashing through cwm again results in boot loop) ..
C:\Users\Senthilnathan\AppData\Local\Android\android-sdk\platform-tools>adb push Miui_v4_2.7.20-O2x-MultiLang.zip /sdcard/Miui_v4_2.7.20-O2x-MultiLang.zip
1947 KB/s (178451090 bytes in 89.495s)
C:\Users\Senthilnathan\AppData\Local\Android\android-sdk\platform-tools>fastboot -w update /sdcard/Miui_v4_2.7.20-O2x-MultiLang.zip
error: failed to load '/sdcard/Miui_v4_2.7.20-O2x-MultiLang.zip'
~#ls -lrth
-rwxrwxrwx 1 root root 170.2M Sep 16 2012 /sdcard/Miui_v4_2.7.20-O2x-MultiLang.zip
Still in same cwm bootloop.. CWM-5.0.2.7.. Please help -
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
MMarkkk said:
OR
http://forum.xda-developers.com/showthread.php?t=1054492
Click to expand...
Click to collapse
When i tried to push part5.img file form link provided,it gets through, but while re-startintg phone - it stucks in lg logo..!!
Logs:
====
G:\NVFlash>nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 14 part5.img
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x038820c440c09417
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: part5.img
/ 1566720/1566720 bytes sent
part5.img sent successfully
Still in cwm bootloop.. Can you please tell what should i have to do avoid this 'E: Can't mount cache/recovery/command' ?
vsnstarguy said:
When i tried to push part5.img file form link provided,it gets through, but while re-startintg phone - it stucks in lg logo..!!
Logs:
====
G:\NVFlash>nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 14 part5.img
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x038820c440c09417
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: part5.img
/ 1566720/1566720 bytes sent
part5.img sent successfully
Still in cwm bootloop.. Can you please tell what should i have to do avoid this 'E: Can't mount cache/recovery/command' ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1893047
Waiting for bootloader to initializer
Hi vsnstarguy,
I have a situation like yours. My device is dead and nothing shows on screen. I've tried that methods, nvflash, smartflash but my device is realy dead and I got the same status like you:
C:\O2x\NVFlash>nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final
_emmc_x8.bct --bl fastboot.bin --download 5 recovery-clockwork-5.0.2.0-p999.img
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 4
chip sku: 0xf
chip uid: 0x037c7008427f85d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader failed NvError 0x0
command failure: bootloader download failed
Nothing happens after this!!!!
Hekp me!
I've opened a thread about this but nobody could help me yet!
Thing is, most people manage to get passed that point. If you've plugged directly into the motherboards USB ports, have you tried another computer?
@cl06 - nvflash and adb works..!!
@cl06 - Dude, is you phone p990 or p999 ? you seem to be trying with p999.
Nvflash p990 correctly, it will work.. (got this from Rusty thread)
or navigate it to your nvflash folder for p990 and try below command--
nvflash --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 14 cwm-int.img
In above nvflash command - after download for p999 it will be 5 for p990 it will be 14.
For some intermittent issues, i changed usb cable and now nvflash works but im still in bootloop for which our friends here will help us

Question [SOLVED] Bricked device - can only access MIUI Recovery and Fastboot

I f****d up.
Hi everyone. I may have bitten more than I can chew. I'm trying to install a custom ROM to my recently unlocked Redmi Note 10 Pro. It's crDroid in case that's necessary.
I did a lot of things but I forgot most of them. Here's what I remember doing:
Connected my phone to my Linux computer.
Go into fastboot modevia the following command:
Code:
adb reboot bootloader
Use TWRP by running this in a terminal:
Code:
fastboot boot twrp.img
Went in to the wipe option in TWRP and do a complete factory reset and format data.
Pushed the custom ROM file to /sdcard.
Attempted to install the zip file via TWRP.
Got an error code. Forgot the code and I didn't take note of it. (Please make fun of me).
Attempted to reboot TWRP recovery by going to Reboot > Recovery
Reached stock MIUI Recovery.
And here I am.
I can only access MIUI Recovery 5.0 and fastboot mode, both by pressing the right buttons on the device.
I don't know what a bricked device is, but it sure does feel like my device is one.
Is there a way to solve this?
zepolyerf said:
I f****d up.
Hi everyone. I may have bitten more than I can chew. I'm trying to install a custom ROM to my recently unlocked Redmi Note 10 Pro. It's crDroid in case that's necessary.
I did a lot of things but I forgot most of them. Here's what I remember doing:
Connected my phone to my Linux computer.
Go into fastboot modevia the following command:
Code:
adb reboot bootloader
Use TWRP by running this in a terminal:
Code:
fastboot boot twrp.img
Went in to the wipe option in TWRP and do a complete factory reset and format data.
Pushed the custom ROM file to /sdcard.
Attempted to install the zip file via TWRP.
Got an error code. Forgot the code and I didn't take note of it. (Please make fun of me).
Attempted to reboot TWRP recovery by going to Reboot > Recovery
Reached stock MIUI Recovery.
And here I am.
I can only access MIUI Recovery 5.0 and fastboot mode, both by pressing the right buttons on the device.
I don't know what a bricked device is, but it sure does feel like my device is one.
Is there a way to solve this?
Click to expand...
Click to collapse
Drivers installed?
Hi! How can I check if drivers are installed? I'm on Linux, if that matters.
Your device isn't bricked until you can do absolutely nothing with it. Start by reflashing the factory firmware; this should get your device running again.
You should also still be able to boot TWRP just like you did. What ROM were you trying to use?
V0latyle said:
Your device isn't bricked until you can do absolutely nothing with it. Start by reflashing the factory firmware; this should get your device running again.
You should also still be able to boot TWRP just like you did. What ROM were you trying to use?
Click to expand...
Click to collapse
That's good to hear.
I'm trying to make another attempt to boot to TWRP. I'm currently in fastboot mode: running fastboot -l devices shows this:
Code:
f8b471a6 fastboot
usb:1-5
I tried to following official TWRP instructions to flash it. Ran fastboot flash recovery twrp.img and all I get is <waiting for device> as a response after running the command in the terminal.
I unplug the cable, then plug it back in to the computer, then this is what I got:
Code:
Sending 'recovery' (131072 KB) FAILED (Write to device failed (Device or resource busy))
fastboot: error: Command failed
Any ideas on how to get around this?
zepolyerf said:
That's good to hear.
I'm trying to make another attempt to boot to TWRP. I'm currently in fastboot mode: running fastboot -l devices shows this:
Code:
f8b471a6 fastboot
usb:1-5
I tried to following official TWRP instructions to flash it. Ran fastboot flash recovery twrp.img and all I get is <waiting for device> as a response after running the command in the terminal.
I unplug the cable, then plug it back in to the computer, then this is what I got:
Code:
Sending 'recovery' (131072 KB) FAILED (Write to device failed (Device or resource busy))
fastboot: error: Command failed
Any ideas on how to get around this?
Click to expand...
Click to collapse
Your device might not have a recovery partition; in A/B partition layout devices, recovery lives in the boot image.
A bit of an explanation:
When you use fastboot boot <image> you're telling the device to load the image you're sending - so if you use fastboot boot twrp.img you're telling it to load the TWRP.img on your computer. This is what you should be using if you want to boot TWRP.
When you use fastboot flash <partition> <image> you're telling bootloader to flash the specified partition with the specified image. So, if you used fastboot flash boot twrp.img, bootloader will overwrite /boot with the TWRP image...meaning the device will only boot into TWRP.
As for why the device would only boot into stock recovery after you flashed the custom ROM, I suspect that it didn't flash the kernel, or otherwise may have corrupted the boot image. So, when the device tries to start the kernel, it failed and just boots into recovery instead.
What should I do at this point if I can't do fasboot boot <image> or fastboot flash <parition> <image> because of the <waiting for device> thing I get everytime I run those commands?
zepolyerf said:
What should I do at this point if I can't do fasboot boot <image> or fastboot flash <parition> <image> because of the <waiting for device> thing I get everytime I run those commands?
Click to expand...
Click to collapse
Reboot to bootloader. If you're currently in recovery mode, cancel the command (Ctrl+C) and use adb reboot bootloader. If you're currently in bootloader but it's not responding, just use the button combo to force a reset.
Remember, you can only use fastboot commands in bootloader mode. If you're in recovery, you can only use some ADB commands, but in this case, I don't think that will be much help.
This is just soft brick. A hard brick means no life in the device as well. In your case, you can still access recovery and fastboot. You can either use MiFlash and use fastboot to flash the stock rom (your choice if you want to relock the bootloader or not) or flash miui recovery rom directly in the custom recovery.
If I remember correctly too, crDroid requires it's provided recovery instead of TWRP so maybe that's why the installation failed.
I went into fastboot mode by pressing Vol Down + Power buttons.
Plugged the phone in to my Linux machine. Have VirtualBox recognize my device.
Opened MiFlash tool. Selected the flash rom from Xiaomi's site. Got an Antirollback error. Here's the logs:
Code:
[4:41:24 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:41:25 AM]:GetScriptDevices
[4:41:28 AM]:add device f8b471a6 index 0
[4:41:48 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:41:48 AM]:GetScriptDevices
[4:41:51 AM]:FlashingDevice.flashDeviceList.Remove f8b471a6
[4:41:51 AM]:add device f8b471a6 index 0
[4:41:51 AM]:Thread start,thread id 11,thread name f8b471a6
[4:41:51 AM]:start process id 4212 name cmd
[4:49:16 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:49:16 AM]:GetScriptDevices
[4:49:16 AM]:add device f8b471a6 index 1
[4:49:24 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:49:24 AM]:GetScriptDevices
[4:49:24 AM]:FlashingDevice.flashDeviceList.Remove f8b471a6
[4:49:24 AM]:add device f8b471a6 index 1
[4:49:24 AM]:Thread start,thread id 12,thread name f8b471a6
[4:49:24 AM]:start process id 1704 name cmd
[4:49:25 AM]:Thread stopped, thread id 12, thread name f8b471a6
[4:51:22 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:51:23 AM]:GetScriptDevices
[4:51:23 AM]:FlashingDevice.flashDeviceList.Remove f8b471a6
[4:51:23 AM]:add device f8b471a6 index 1
[4:51:23 AM]:Thread start,thread id 19,thread name f8b471a6
[4:51:23 AM]:start process id 3400 name cmd
[4:52:26 AM]:GetUserInfo
[4:52:39 AM]:authentication edl error:Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
[4:56:31 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:56:31 AM]:GetScriptDevices
[6:00:17 AM]:open RegistryKey Software\XiaoMi\MiFlash\
[6:00:18 AM]:driver oem5.inf exists,uninstall,reuslt True,GetLastWin32Error
[6:00:19 AM]:install driver C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Google\Driver\android_winusb.inf to C:\Windows\INF\oem5.inf,result True,GetLastWin32Error
[6:00:19 AM]:set RegistryKey value:android_winusb.inf--oem5.inf
[6:00:19 AM]:mkdir "C:\Users\IEUser\.android"
[6:00:19 AM]:output:A subdirectory or file C:\Users\IEUser\.android already exists.
[6:00:19 AM]: echo 0x2717 >>"C:\Users\IEUser\.android\adb_usb.ini"
[6:00:19 AM]:output:
[6:00:19 AM]:open RegistryKey Software\XiaoMi\MiFlash\
[6:00:19 AM]:install driver C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Nvidia\Driver\NvidiaUsb.inf to ,result False,GetLastWin32Error Unknown error (0xe000022f)
[6:00:19 AM]:open RegistryKey Software\XiaoMi\MiFlash\
[6:00:20 AM]:install driver C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Microsoft\Driver\tetherxp.inf to ,result False,GetLastWin32Error Unknown error (0xe000022f)
[6:00:20 AM]:open RegistryKey Software\XiaoMi\MiFlash\
[6:00:21 AM]:install driver C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Microsoft\Driver\wpdmtphw.inf to ,result False,GetLastWin32Error Unknown error (0xe000022f)
[6:00:21 AM]:open RegistryKey Software\XiaoMi\MiFlash\
[6:00:21 AM]:driver oem6.inf exists,uninstall,reuslt True,GetLastWin32Error
[6:00:22 AM]:install driver C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\Driver\qcser.inf to C:\Windows\INF\oem6.inf,result True,GetLastWin32Error
[6:00:22 AM]:set RegistryKey value:qcser.inf--oem6.inf
[6:01:33 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[6:01:34 AM]:GetScriptDevices
[6:01:34 AM]:add device f8b471a6 index 1
[6:01:55 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[6:01:55 AM]:GetScriptDevices
[6:01:55 AM]:FlashingDevice.flashDeviceList.Remove f8b471a6
[6:01:55 AM]:add device f8b471a6 index 1
[6:01:55 AM]:Thread start,thread id 12,thread name f8b471a6
[6:01:55 AM]:start process id 6280 name cmd
[6:01:56 AM]:Thread stopped, thread id 12, thread name f8b471a6
Any idea on what to do next?
BigChungus321 said:
This is just soft brick. A hard brick means no life in the device as well. In your case, you can still access recovery and fastboot. You can either use MiFlash and use fastboot to flash the stock rom (your choice if you want to relock the bootloader or not) or flash miui recovery rom directly in the custom recovery.
If I remember correctly too, crDroid requires it's provided recovery instead of TWRP so maybe that's why the installation failed.
Click to expand...
Click to collapse
It might as well be a brick haha. I must be dumb (very likely) or there's just not a lot of clear and comprehensive resources out there to fix this kind of thing.
Ahh anti roll back error is pretty simple to fix, you just have to remove the check from the .bat files, there are tutorials on YT that can help, after that reflash stock rom in MiFlash.
If you're worried about anti roll back, don't worry, ARB value for the device has been 3 so far so it's safe to downgrade. Goodluck
Seeing a ton of Bricked Notes on here this last week, Y`all making me nervous about doing anything with mine lol
I faced this problem in linux got around it with usb 2.0 interface doesn't worked with usb 3.0 and above but my device was different when I got this recovery flash waiting problem. Also try to updated the platform tools.
So the solution was to entirely ditch Linux and use Windows to play with fastboot and adb commands via the terminal.
I don't understand why it worked when I did it on Windows when I was using the same platform tools on Linux. Oh well.

Question 'Your device is corrupt' message after failed Magisk A/B update. Flashed factory image, phone is now booting but message persists

I didn't realize that Pixels didn't work with Magisk's A/B update method, so I tried it, and afterwards I received the 'Your device is corrupt' on startup and the phone wouldn't boot.
I ended up flashing the December factory image (sans -w flag), and the phone now boots, but I still am receiving the 'Your device is corrupt' message on startup.
I did flash the patched init_boot, but the message existed before then.
Would anyone know of any steps I can take to get rid of this message? Preferably without data loss?
Thanks in advanced for any help.
Hmm. Try sideloading the OTA, see if that fixes it. Somehow, dm-verity got stuck in EIO mode. More details here
Edit: Did a little more research. In a ADB terminal (either recovery or system) you can use adb reboot "dm-verity enforcing"
Thanks for the reply.
Trying to sideload the OTA with adb sideload image.zip gives me the following error on my phone:
ERROR: recovery: footer is wrong
ERROR: recovery: Signature verification failed
ERROR: recovery: error: 21
I have verified the .zip hash matches the hash on the factory images site.
_____
If I try to run adb reboot "dm-verity enforcing" it gives me a "too many arguments" error in my terminal.
I did find this command, which seems the newer way of doing this:
fastboot flash vbmeta –disable-verity –disable-verification vbmeta.img
... but running that with the vbmeta.img from the OTA zip gives me this weird error:
fastboot: error: cannot load 'ûdisable-verity': No such file or directory (û character included)

Categories

Resources