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
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
Hello, i think my Optimus 2x is bricked. I flashed a wrong ROM and it would "freeze" at the LG logo. So I followed a guide that said would flash the phone to stock with NVflash. Anyway the guide said that I should go back to EXT3 FIRST before flashing but I forgot and now the phone won't even boot. Nothing happens when trying to turn it on. However my PC still sees APX/Nvidia recovery whatever when i plug it in.
Help.
Try this: http://forum.xda-developers.com/showthread.php?t=1229407
Also if nvflash doesn't work, try smartflash!
There is numerous threads with title brick, bricked and etc. Little search would be nice...
You can read my answer here -> http://forum.xda-developers.com/showpost.php?p=24024818&postcount=6
SP1996AC said:
Try this: http://forum.xda-developers.com/showthread.php?t=1229407
Also if nvflash doesn't work, try smartflash!
Click to expand...
Click to collapse
Tried that... The thing is, the phone seems to be completely DEAD. Reacts to nothing.
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: 0x033c2087415ff597
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
download command failed NvError 0x120002
command failure: bootloader download failed (bad data)
bootloader status: Bct file not found (code: 21) message: flags: 1073840124
I got the same results even when not holding vol up and down. But I'll try Memhis link.
Memhis said:
There is numerous threads with title brick, bricked and etc. Little search would be nice...
You can read my answer here -> http://forum.xda-developers.com/showpost.php?p=24024818&postcount=6
Click to expand...
Click to collapse
Yeah sorry I'm just really worried right now. It's not really my phone, so I'm trying to get it fixed quick. Thanks for the link
Memhis said:
There is numerous threads with title brick, bricked and etc. Little search would be nice...
You can read my answer here -> http://forum.xda-developers.com/showpost.php?p=24024818&postcount=6
Click to expand...
Click to collapse
It doesn't work! The phone is stuck in APX mode! Doesn't matter what I do, if i plug it Windows says APX. There has to be a way! But the phone doesn't react to any buttons, whatever I hold, or do, it's still in APX mode and dead.
install lg drivers and flash kdz firmware and then root the phone!
on the first post, i had the same problem a week ago. what fixed my phone was flash stock ROM using smartflash, with the .fls and .bin file. its just like newly bought phone after the flash. hope it helps!
Sent from my Optimus 2X using XDA
mrgian said:
on the first post, i had the same problem a week ago. what fixed my phone was flash stock ROM using smartflash, with the .fls and .bin file. its just like newly bought phone after the flash. hope it helps!
Sent from my Optimus 2X using XDA
Click to expand...
Click to collapse
I guess I have my p990 also stuck in APX mode. Smartflash doesn't detect my phone, and NVFlash (recovery) returns:
Please pick a recovery, or exit [1,2,X]?2
Attempting to flash external recovery...
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x028841484180d657
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
download command failed NvError 0x120002
command failure: bootloader download failed (bad data)
bootloader status: Bct file not found (code: 21) message: flags: 1073840124
Which is the same problem as ITSANDEN
Thing is, I ran xda forum end to end looking for people with same trouble as I and I could not find any help. It's like a loop! LOL
If nvflash doesn't work use Smartflash, and vice versa.... LOL :frustrated:
Anyway, I'll keep looking.
---------- Post added at 08:15 PM ---------- Previous post was at 07:33 PM ----------
mrgian said:
on the first post, i had the same problem a week ago. what fixed my phone was flash stock ROM using smartflash, with the .fls and .bin file. its just like newly bought phone after the flash. hope it helps!
Sent from my Optimus 2X using XDA
Click to expand...
Click to collapse
Memhis said:
There is numerous threads with title brick, bricked and etc. Little search would be nice...
You can read my answer here -> http://forum.xda-developers.com/showpost.php?p=24024818&postcount=6
Click to expand...
Click to collapse
Unfortunately SmartFlashTool doesn't work since the phone is running in APX and doesn't create port connection that SFT software can recognize.
Try to nvflash whole rom not just recovery. Ie pauls v10b. I hope it will work for you.
Sent from my LG-P990 using xda app-developers app
xtrustkillx said:
Try to nvflash whole rom not just recovery. Ie pauls v10b. I hope it will work for you.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
I tried both!
When I do the whole rom procedure it gives an error message, but since the cmd window closes right away i can't copy (or i am not aware of a way to retrieve the text....).
Supposedly after NVFlashing the whole ROM I should unplug the cable, install the battery and boot the phone.
At this point the phone doesn't boot, or at least nothing is showing on the screen.
Volume down+ power also doesn't work so I cannot do to CMW.
Do I need to send it to LG?
Thanks for your help anyways!
EDIT:
Actually I managed to keep the CMD window open and this is what I got:
Code:
C:\Users\Dinis\Desktop\desktop\android\Emergency>.\nvflash.exe --bct E1108_Hynix
_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --setbct --odmdata 0xC8000 --co
nfigfile android_fastboot_emmc_full.cfg --create --bl fastboot.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x028841484180d657
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
sending file: E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct
- 4080/4080 bytes sent
E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct sent successfully
odm data: 0xc8000
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
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBR
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: EB1
creating partition: LNX
creating partition: EB2
creating partition: DRM
creating partition: EB3
creating partition: SOS
creating partition: EB4
creating partition: UDA
creating partition: EB5
creating partition: UDB
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBR please wait.. done!
Formatting partition 6 APP please wait.. done!
Formatting partition 7 CAC please wait.. done!
Formatting partition 8 MSC please wait.. done!
Formatting partition 9 EB1 please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 EB2 please wait.. done!
Formatting partition 12 DRM please wait.. done!
Formatting partition 13 EB3 please wait.. done!
Formatting partition 14 SOS please wait.. done!
Formatting partition 15 EB4 please wait.. done!
Formatting partition 16 UDA please wait.. done!
Formatting partition 17 EB5 please wait.. done!
Formatting partition 18 UDB please wait.. done!
done!
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
sending file: system.img
- 851968/358400000 bytes sentdata send failed NvError 0x120002
command failure: create failed (bad data)
Can you enter fastboot now or still stuck in apx? Just in case: Turn off the phone. Remove battery and
hold it removed for few secs. Put it back and press and hold vol - and power button. Keep it pressed and then try smartflash.
Sent from my LG-P990 using xda app-developers app
xtrustkillx said:
Can you enter fastboot now or still stuck in apx? Just in case: Turn off the phone. Remove battery and
hold it removed for few secs. Put it back and press and hold vol - and power button. Keep it pressed and then try smartflash.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Still stuck in APX.
SmartFlash keeps not detecting it!
Thanks For Helping out!
Thats strange. Try to nvflash again without sim and sd card, different cable, different usb port (prefere those which are directly on motherboard on the back of your pc). Just a bunch of ideas.
Sent from my LG-P990 using xda app-developers app
xtrustkillx said:
Thats strange. Try to nvflash again without sim and sd card, different cable, different usb port (prefere those which are directly on motherboard on the back of your pc). Just a bunch of ideas.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Totally strange!! Now I tried again to nvflash with modaco's [ android.modaco.com/topic/335474-25-mar-nvflash-stock-rom-release-v10b-dated-1300166062-15032011/ ]
and it fails in the same way as Rusty's
Code:
(...)
Formatting partition 18 UDB please wait.. done!
done!
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
sending file: system.img
| 2818048/358400000 bytes sentdata send failed NvError 0x120002
command failure: create failed (bad data)
I tried 3 cables, and 3 usbports in my laptop. It worked before, so something must have gone wrong.
Weekend is coming, if I cant fix it Ill have to send to LG and buy a new one while waiting some (hopefully not many) time to get it back!
EDIT:
After some tries the data transferred increased
Code:
(...)
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
sending file: system.img
| 339935232/358400000 bytes sentdata send failed NvError 0x120002
command failure: create failed (bad data)
EDIT 2:
Until I turned off all services, browser and dropbox and what not and:
Code:
(...)
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
sending file: system.img
- 358400000/358400000 bytes sent
system.img sent successfully
sending file: boot.img
- 3420160/3420160 bytes sent
boot.img sent successfully
sending file: recovery.img
- 3958784/3958784 bytes sent
recovery.img sent successfully
But afterwards, it booted LG logo and sound and nothing else. I waited 20 minutes for something to happen until I removed the baterry and turned on again. and LG Logo only....
Then, I tried to battery off and volume down+data cable and i could smartflash. as result it booted once, No LG logo with blue halo but sound played, and again nothing happened for another half hour until i turned off and NVFLashed again and bricked the phone again.
So, now, back to step 1, My phone is stuck in APX and I don't think NVFlash will solve even if it works after 30 tries.
Maybe I have the solution:
Just download the right version of stock gingerbread, check this link:
http://www.todomovillg.es/elforodehomero/index.php?topic=317.0
With this .kdz file, you have to use the KDZ Updater and the LG driver.
Download the latest LG driver here and intall it right after: http://www.lg.com/ca_en/support/mc-support/mobile-phone-support.jsp
UNPLUG your phone before installing this driver.
And the KDZ Updater here: http://forum.xda-developers.com/attachment.php?attachmentid=420545&d=1287222698
When that's done, extract the KDZ Updater folder on your desktop.
1. Open it and install the msxml.msi file.
2. After that, run the KDZ_FW_UPD.exe
3. In that software, you will choose Type: 3GQCT and the PhoneMode: DIAG
4. Choose your recently downloaded .kdz file but DON'T LAUNCH SOFTWARE UPDATE yet.
5. PowerOff your phone and pull out the battery.
6. Hold Volume Down and plug in it to your computer with your USB cable.
7. Your phone must be in S/W UPGRADE Please wait while upgrading...
8. When that's done, just push the Launch Software Update button.
9. WAIT until it reboot and put your battery in.
10. When kdz updater finish, unplug your phone and Enjoy. :good:
Hope that help.
JasonBourne.Qc said:
Maybe I have the solution:
Just download the right version of stock gingerbread, check this link:
http://www.todomovillg.es/elforodehomero/index.php?topic=317.0
With this .kdz file, you have to use the KDZ Updater and the LG driver.
Download the latest LG driver here and intall it right after: http://www.lg.com/ca_en/support/mc-support/mobile-phone-support.jsp
UNPLUG your phone before installing this driver.
And the KDZ Updater here: http://forum.xda-developers.com/attachment.php?attachmentid=420545&d=1287222698
When that's done, extract the KDZ Updater folder on your desktop.
1. Open it and install the msxml.msi file.
2. After that, run the KDZ_FW_UPD.exe
3. In that software, you will choose Type: 3GQCT and the PhoneMode: DIAG
4. Choose your recently downloaded .kdz file but DON'T LAUNCH SOFTWARE UPDATE yet.
5. PowerOff your phone and pull out the battery.
6. Hold Volume Down and plug in it to your computer with your USB cable.
7. Your phone must be in S/W UPGRADE Please wait while upgrading...
8. When that's done, just push the Launch Software Update button.
9. WAIT until it reboot and put your battery in.
10. When kdz updater finish, unplug your phone and Enjoy. :good:
Hope that help.
Click to expand...
Click to collapse
I was trying your solution, but no luck.... I got in KDZ updater : connecting to phone. PHONE WAS NOT FOUND! Finished. any idea? I installed LG drivers, my phone is stuck, no power on, no volume down + power .... looks like its fully bricked, please help me guys
Do not use Smartflash, bro.
Use nvflash in this post, I used to have a half-brick O2X but this post saved me
http://www.modaco.com/topic/335474-25-mar-nvflash-stock-rom-release-v10b-dated-1300166062-15032011/
Good luck! Yuo will need it.
Try to use stefan's ics nvflash version, i think his thread is on page 3/4, then boot it up, if you're planning to use cm10 with the new bootloader use aio tool, or you can download the stock gb/froyo from modaco then nvflash it
Sent from my LG-P990 using Tapatalk 2
Someone fixed the problem yet??
my phone stuck at erecovery mode . i did flash it with new rom using the dc phoenix but it turn out failed.
here is the progress :
Build number: :COR-L29 9.0.0.193(SP53C636E2R1P12)
Model: COR-L29
Battery state: 4885mv
OEM lock state info:
FB LockState: LOCKED
USER LockState: LOCKED
OEM get bootinfo:
locked
Process identifier:18080917
Getting build number...
Getting base version...
Getting cust version...
Getting preload version...
Erasing ver .. .
File size: 5,037,310,948 bytes
Current version(CURVER): CORC00B000
Writing rescue_recovery_kernel partition
rescue_recovery_kernel partition UPDATE ...OK
Writing rescue_recovery_ramdisk partition
rescue_recovery_ramdisk partition UPDATE ...OK
Writing rescue_recovery_vendor partition
rescue_recovery_vendor partition UPDATE ...OK
USB Device REMOVAL
Type: @OEM83.inf,%tplinkfastboot%;Android Bootloader Interface
VidPid: VID_18D1&PID_D00D
Instance id: 5&118960b2&0&2
Looking for device in upgrade mode...
USB Device INSERTION
Type: @OEM148.inf,%busfilter.devicedesc%;USB Composite Device
VidPid: VID_12D1&PID_107E
Instance id: 5&118960b2&0&2
COM11: DBAdapter Reserved Interface (COM11)
COM12: Android Adapter PCUI (COM12)
8/29/2019 3:56:10 PM Starting to write device in UPGRADE mode...
Device found: XTX7N18830004739
8/29/2019 3:56:38 PM start to write update file
File to update: UPDATE_SD.APP
File size: 5,037,310,948 bytes
Current version(CURVER): CORC00B000
Process identifier:18080974
Validating file...
Looking for attached port...
Preparing to write...
Writing file 1 of 43: SHA256RSA...OK
Writing file 2 of 43: CRC...OK
Writing file 3 of 43: CURVER...OK
Writing file 4 of 43: VERLIST...
Error downloading file 4 of 43
Error writing software
8/29/2019 3:57:16 PM Writing device finished with ERROR
anyone can help me with this ?