Database Develop

[Q] Help!!! aka "is my phone bricked?"

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

[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

QDL mode not found

This is the message I get when running tpdebrick.. The process works with my other tablets so i think the process and cabling are good? Is there anything that can be done?
[email protected]:~/Downloads/tpdebrick-v004$ sudo ./tpdebrick 32
checking doc files ...
Connect Touchpad then hold Power+Home+VolumeDown for 30 seconds ...
QDL mode not found
Aborting.

another one with different issues/fixable either?
Executing file...
Checking QDL mode...
Writing file tz.mbn ...
Sending MAGIC...
MSG: Qfprom Fuse List: Blowing FAILED
MSG: Failed Fuse addr:
MSG: 0x00000000
MSG: Error Status:
MSG: 0x00000000
Sending secureMode...
Sending openMulti ...
MSG: Open multi failed, unknown error
ERROR: Open multi failed, unknown error
Invalid openMulti response.
Cannot write file tz.mbn
Aborted.

Help me !! remote : flash_cmds error

i have zenfone 4 A400CG(kitkat) always display error facebook, system ui, youtube etc. now i flash with same rom.
on adb folder i type in cmd : fastboot flash boot boot.img(success) but when i type fastboot flash fasboot fastboot.img
"Failed (remote : flash_cmds error !" can u help me ?
flash cmds error solve problem, now i flash error : "fail: no enought DATA space,please free 998 MB at least"
i try flash raw file in SD Download, after that stuck Asus logo. help me...

Problem with on-boot password led to partial brick, need help [r13]

Hey guys,
I dun goofed when trying to do a routine backup.
First off, I'm trying to recover this without wiping, as I have some 2FA apps and other things that have secret keys that can't be recovered unless I can decrypt the darned thing
Rebooted into TWRP in order to do an image backup before I upgrade from arter97's kernel r13 to r14.
When TWRP comes up, it surprises me with a password prompt (instead of pattern unlock which is what it should be)
Reboot to system to remove encryption and then fix the password issue, greeted by "To start Android, enter your password" prompt, again instead of pattern unlock
Tried the numbers-to-pattern trick, no luck. Basically locked out of the phone now
Booted back into TWRP, while looking around for other options, accidentally chose "Slot A" which has gotten me stuck back on the old recovery
fastboot commands no longer work properly (see below)
Sometimes the commands hang, and I need to ctrl+c and re-run. I get very inconsistent results, as you'll see below
Code:
D:\adb>fastboot.exe boot twrp-3.2.1-0-cheryl.img
Sending 'boot.img' (23120 KB) FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
Trying to re-flash the kernel just hangs:
Code:
D:\adb>fastboot.exe flash boot arter97-kernel-r14-20200428.img
Tried switching to Windows Terminal/Powershell and got slightly different error:
Code:
PS D:\adb> .\fastboot.exe boot .\twrp-3.2.1-0-cheryl.img
Sending 'boot.img' (23120 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
PS D:\adb> .\fastboot.exe flash boot .\arter97-kernel-r14-20200428.img
Sending 'boot' (30176 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
PS D:\adb> .\fastboot.exe getvar all
getvar:all FAILED (Write to device failed (Unknown error))
Finished. Total time: 5.004s
PS D:\adb> .\fastboot.exe --set-active=a
PS D:\adb> .\fastboot.exe --set-active=b
fastboot: error: Device does not support slots
PS D:\adb> .\fastboot.exe --set-active=q
Slot q does not exist. supported slots are:
a
b
PS D:\adb> .\fastboot.exe --set-active=a
Setting current slot to 'a' FAILED (remote: 'Invalid Slot')
fastboot: error: Command failed
PS D:\adb> .\fastboot.exe --set-active=b
Setting current slot to 'b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
I'm sure the TWRP image is still there in slot b, but I can't get it to switch back.

Update:
I tried running the `fastboot --set-active=b` on a different (older) system which did finally work and allowed me to switch back over to TWRP, but I'm still having that decryption issue.
Anyone know why the encryption would suddenly switch from pattern unlock to "password" and how I could fix it?
Edit: After doing some more research on here, it sounds like my phone may have OTA'd itself to MR3 which may be the cause for the password issue.
Got an idea that I hope will work, which is to use the factory MR2 image, and comment out the lines for wiping data. Maybe that will bring it back?