Related
I flashed my stock. 2.1 Milestone (rooted) preparing it for froyo. Apparently the .sbf was corrupt or wrong;
GOT_TELUS_2_2_1FULL.sbf
I am told the correct sbf is;
BL_9078_GOOD_sholes_HS_Consumer_replacer.sbf\BL_9078_umts_sholes_HS_Consumer_replacer.sbf.
- Now It’s stuck in bootloader mode
-RSD Lite seems to recognize phone but the “Start” button remains disabled, grey, it can’t be pushed (with either .sbf file.)
-I’ve loaded a fresh copy of RSD Lite v5.0 (previously had v4.7). Both behave the same; the start button is disabled.
I want to save this phone and am looking for alternative tools or methods to ultimately flash the proper .sbf…Help please!!!
BOOTLOADER SCREEN BELOW
PHP:
Bootloader
90.74
Err:A5,69,35,00,27
Battery OK
OK to Program
Transfer Mode:
USB
RSD LITE SCREEN BELOW
PHP:
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x009074
DRM Version: N / A
AP Die ID: 06a0010c60720304000000000400
BP Die ID: 0000000000000000000000000000
AP Public ID: 4bd4854c5cb58e173025f2751e09441b44fa681f
BP Public ID: 0000000000000000000000000000000000000000
-----------------------------------------------------------------------
Model Port No Port Type IMEI/ESN/MEID Status
S Flash OMAP3430 1 USB N/A connected
(I’ve successfully flashed my other Millstone an many other phones)
Any help is greatly appreciated,
PK
The greyed out start button is an error in RSD. What you want to do is rename that really long sbf file to a one letter name such as a.sbf
If you are planning on rooting, you can flash the VR from android.doshaska.net/rootable but I would not try it until those bootloader errors get corrected. Be careful on the site I gave you, one sbf is for bootloader version 90.78, the other is for yours (90.74)
Hope that helped.
Sent from my Milestone using XDA Premium App
Thanks skadude66
That kinda worked, I renamed it “A” and also had to put it in the root on my C; drive. The button worked.
The bad news is it wouldn’t take. I got the following error message:
PHP:
Device Properties
EMEI/ESN: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Boot Version: N / A
DRM Version: N / A
PHP:
Status
Failed flashing process Failed flashing process (0x7100); phone connected.
(I also discovered by hunting around that I almost tried to flash the wrong ver of.sbf, 90.78 instead of 90.74. It didn’t make any difference though.) Failed.
Regards, PK
pk2 said:
Thanks skadude66
That kinda worked, I renamed it “A” and also had to put it in the root on my C; drive. The button worked.
The bad news is it wouldn’t take. I got the following error message:
PHP:
Device Properties
EMEI/ESN: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Boot Version: N / A
DRM Version: N / A
PHP:
Status
Failed flashing process Failed flashing process (0x7100); phone connected.
(I also discovered by hunting around that I almost tried to flash the wrong ver of.sbf, 90.78 instead of 90.74. It didn’t make any difference though.) Failed.
Regards, PK
Click to expand...
Click to collapse
Try using the latest version of Motorola USB drivers, your phone might not be completely recognized.
EDIT: http://androidforums.com/droid-all-...hing-process-0x7100-rsd-lite.html#post1274587
I used that to help me out when I had that error as well. It worked for me, it should for you as well.
Thanks. good read so far. Nice to know I'm not alone and there may be a way. I think the trick when I did this on my other Milestone was copying the sbf here there and everywhere. Haven't updated the latest usb drivers.
Regards, PK
Well crap,
I downloaded v.5 moto usb drivers from moto. One self installing program. RSD doesn't see the phone at all now. Tried twice. Uninstalled drivers with program "total uninstaller" (normally very good), still nothing in RSD.
Seem to recall having to manually install either HTC or moto drivers. Guess I got to hunt around and find out what the moto trick is.
crap.
Regards. PK
Finally new Moto Drivers (v5.0) installed, start button in RSD "start" button works but when pushed, RSD reads "Flash Failed"
Any help? PK
try RSD v4.7, maybe its the RSD problem.
Have you check out your system hardware manager to see if the Milestone was recognized completely?
Hi,
i got same problem 2 days ago.
at my point i just had to install a new rom.
if you get in Open Recovery try to install miui oder CM.
I got the same error when i tried to install CM7. So I installed MIUI and voila everything worked.
Thanks for the reply's!
I tried all of above and it still "failed" to flash.
I can't get into open recovery or the stock "recovery" utility (this phone was stock when this all started).
The phone shows up in "devices and printers" as "unspecified-S flash omap3430a" not as Milestone
Regards, PK
I was having a similar problem. How are you getting into the bootloader? I was using the volume button.
For whatever reason, when I got into the bootloader using the D-pad, RDS Lite found the phone.
I still can't seem to flash anything properly, but it found it.
It pretty much jumps straight to boot loader mode all by itself after powering up. No button combination takes me anywhere but the boot-loader. There's no way to get out of it either.
Thanks, pk
Stuck in boot loader milestone usb drivers
Man I've tried all of above.
The one thing someone mentioned is "is the phone was recognized by win764" . Not really, It only shows up Under "Devices & printers" as "unspecified":
S Flash OMAP3430
I have tried every Moto. USB Driver set I can find. None do anything different. I can not find any manually installable drivers.
(My working hacked milestone_eu shows up as "unspecified" ) to.
Makes me think Maybe my drivers ar screwed. How can I put them in manually without an install a pckage I wonder. Anyone had this prob?
I can't do anything with the either phone, from the computer, when tied together with USB (I.E. access sd card, portal, etc.)
Thanks PK
bump -please
Just to clarify, you have two Milestone's, one is stuck in bootloader mode, the other works. Connecting either to your computer show 'unspecified'. Is that correct?
First, the bootloader version doesn't matter, I've had 90.73, 90.74 and 90.78 on my milestone at diferent times, doesn't make any diference.
The error code you got in bootloader mode (ending in 27) means one of the signed partitions failed the signature check, probably the result of a bad flash. Reflashing usually fixes that.
Your problem sounds like a problem with your USB on your PC, either drivers or a hardware problem (most likely drivers). Fixing your pc should allow you to reflash your milestone correctly.
When connecting a Milestone in bootloader mode to RSD lite, RSD cannot extract the IMEI info etc, the display you pasted is what I would expect when connecting in bootloader mode. If you connect to RSD when the Milestone is booted up (running android), it will show the IMEI etc. All you need to check is that RSD says its connected and its usually ready to flash..
Things you can try:
1: Try flashing from another computer
2: Dual boot Ubuntu on your PC, then try flashing with sbf_flash (google it), no additional drivers are needed, should work straight out the box.
3: Uninstall EVERYTHING on your pc from motorola, then in system/device manager uninstall all the windows USB drivers, reboot and let windows reinstall the USB drivers, then try re-installing the motorola USB drivers and RSD lite.
4: Try a diferent USB cable, also try a diferent USB port. Connect directly to the computer, do not use a USB hub.
Hope this helps.
Hello,
I was recently trying to load a stock rom on my LG540 and the process was interrupted because of a power failure. But the phone luckily booted into "download mode". I want to reflash using the procedures discussed in various posts on bricked phones, but my computer can no longer recognize the phone. The KDZ updater reports "Phone not Found". The correct drivers are installed and I am running windows 7 home edition.
Any thoughts as to how to get the computer recognize the phone?
Thanks, MN
maybe using "Run as administrator"
Try installing these drivers, they helped me when I first used KDZ. The links are from a hungarian site.
http://www.4shared.com/file/Zx52g1kl/Optimus_GT540_pc_sync.html
I think the bootloader is corrupted, it's basically "bricked", but not fully
Drivers must be the issue. Try uninstalling LG driver, reinstall it or use Windows Update to install drivers.
Bricked GT540
Maybe you can use LGDP2 ??
I was trying to flash the lollipop kdz to my phone and was having problems with drivers but then one time it apparently was working but it still gave me an error popup so I unplugged it and now it always boots into firmware update mode :crying: Now I can't get the drivers to install. It shows 3 devices: Mtp device, LGE Android phone, and CDC Serial port (this is just from memory so the actual names might be slightly different). The MTP device always gives the error "Failed to start" and the other 2 say no driver found. I have tried different pcs and driver versions with the same results. I tried this but it says no drivers found. Does anyone know of a fix for this? Is there a way to manually specify the drivers to use or something?
I updated the drivers to the version from LG's website and now the drivers seem to be working except for the mtp one. Now when I try to flash it give the error "Connection to server failed, try again in a moment" and if I click retry it fails with the message "Upgrade stopped due to an error". Anyone have suggestions on how to fix?
Update: I tried the tot method as well and it fails with an error getting model name.
jonmast said:
Update: I tried the tot method as well and it fails with an error getting model name.
Click to expand...
Click to collapse
Make sure that you have the correct drivers installed. For Verizon they should be the LG_VZW_United_WHQL_v2.20.0 one. Use the lg flash tool 2014 http://forum.xda-developers.com/showthread.php?t=2797190 and a kdz file. I believe that you can update to lollipop directly with the lg flash tools. I could not install the lollipop kdz as I kept receiving the same issue "cannot connect to server" so I installed stock 4.4.2 that my device came with and updated to lollipop ota. If you install the the same stock software that your phone shipped with it will still say "cannot connect to server" but it will indeed update your software. I believe that the key is to making sure you install the same stock software your device shipped with for it to actually update to your phone in my experience.
I am using the drivers you mentioned. Do you know if the mtp driver failing is an issue? Also, I tried 3 different kdz versions with the same results.
Do you have a custom recovery like TWRP or CWM?
mach01 said:
Do you have a custom recovery like TWRP or CWM?
Click to expand...
Click to collapse
No
So I think I may have bricked my phone unless I can get the H811 20i KDZ file but even that may not be good enough to save it. I'll start with where I am currently at. On boot I get the error:
Secure booting error!
Error code: 1003
Modified
I am able to get into download mode by pressing the up volume key or into the wipe mode by pressing the down volume key. However, no matter what I try I can't seem to get it to reboot normally.
Here is what I did to get myself into this situation:
I stepped through the guide to install MM and then I performed the fastboot OEM unlock and booted into TWRP. I then installed SuperSU and rebooted. Then for reasons unknown I decided I would relock the boot loader and so I ran the command fastboot oem lock. I fully understand the stupidity of that thought now but didn't think very clearly at the time.
Here is what I have tried:
Using the LG Support Tool I attempted an Upgrade Recovery which failed.
Using the guide on here to return to stock I attempted the method using the kdz file for h811 10n but that fails at the upgrading your phone with the error message "Upgrade stopped due to an error". I have attempted the retry button numerous times without any change in responses.
At this point in time I am game to try anything.
:fingers-crossed:
Thanks to autoprime I am now downloading the kdz for MM and when it is complete I will attempt to use LGUP to restore it.
Well I get an error message from LGUP stating that I don't have the correct DLL for H81120i installed. I attempted to replace the dll with the one inside the MM kdz but that didn't work.
bbenz3 said:
Thanks to autoprime I am now downloading the kdz for MM and when it is complete I will attempt to use LGUP to restore it.
Well I get an error message from LGUP stating that I don't have the correct DLL for H81120i installed. I attempted to replace the dll with the one inside the MM kdz but that didn't work.
Click to expand...
Click to collapse
Use LGBridge. Put it in download mode. Click on update error recovery.
Vseprz said:
Use LGBridge. Put it in download mode. Click on update error recovery.
Click to expand...
Click to collapse
Oh I wish it were that simple. I had tried it last night but attempted it again as I couldn't remember what happened. I get an error message stating "Connect your mobile device to the USB port. If it is already connected, contact LG customer service."
At this point I think I may just need the MM dll to use with LGUP. I attempted to use an MSI packaging utility to replace the dll in the 0.0.3.23 installer with the dll I extracted from the kdz file but that got me nowhere.
I attempted to use the LG FlashTool v1.8 and found out that the dll that I extracted is ver 0.0.3.21 which is older than the msi version found on here. Does anyone know how to get a newer one?
bbenz3 said:
Oh I wish it were that simple. I had tried it last night but attempted it again as I couldn't remember what happened. I get an error message stating "Connect your mobile device to the USB port. If it is already connected, contact LG customer service."
At this point I think I may just need the MM dll to use with LGUP. I attempted to use an MSI packaging utility to replace the dll in the 0.0.3.23 installer with the dll I extracted from the kdz file but that got me nowhere.
Click to expand...
Click to collapse
I had the same error and sucessfully used lgbridge. You probably need to reinstall your usb drivers.
OK I'll give that a shot.
No go...
I uninstalled anything I could find related to LG. I then reinstalled the LG Bridge software which then updated the USB drivers to 4.0.4. I then rebooted my computer and attempted it again and I got nothing but the same error.
bbenz3 said:
OK I'll give that a shot.
No go...
I uninstalled anything I could find related to LG. I then reinstalled the LG Bridge software which then updated the USB drivers to 4.0.4. I then rebooted my computer and attempted it again and I got nothing but the same error.
Click to expand...
Click to collapse
I had this exact same issue when upgrading my phone. Didn't do it correctly and it took me about 3 hours before I got my phone working again. It was about a week ago on another computer, but I'll try to recall what I did when it finally clicked in my mind.
Download H81120i_00_0201.kdz flashable zip from here (1.6GB Feb-04-16):
http://downloads.codefi.re/autoprime/LG/LG_G4/H811/H81120i/
Download LGUP and install it. I used the DropBox link in this thread:
http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Remember to install the LGUP_8994_DLL file BEFORE LGUP_Install
Download and install LG Bridge (for the USB drivers) here:
http://www.lg.com/uk/support/pc-suite
Select the LG 815 model, the drivers will work. I only used the LG Bridge to install the USB drivers. Nothing else.
OK, now here's where your phone comes in.
Step 1: Turn off your phone (pull the battery if you must, but put it back in).
Step 2: Hold the VOLUME UP button and plug the USB cable into your PC. This puts your phone into DOWNLOAD MODE.
Step 3: On your PC, open up LGUP. The program shoud recognize the phone as H811 in COM3 or COM4. Highlight it and click the SELECT button.
Step 4: Under the "Process" row, select UPGRADE
Step 5: Click the blank space under File Path, it will pop up a [...] [X] at the end. Click the [...].
Step 6: Select the H81120i_00_0201.kdz and click on Start. The program will push the STOCK H811 MM ROM to your phone. This will bring your phone out of Brick mode, but you will have to go through the entire rooting process again.
Donut42 said:
I had this exact same issue when upgrading my phone. Didn't do it correctly and it took me about 3 hours before I got my phone working again. It was about a week ago on another computer, but I'll try to recall what I did when it finally clicked in my mind.......
Click to expand...
Click to collapse
Woohoo!!!!!!!!!!!!!! I changed two things and I'm not certain which one it was that finally made it work but I followed your steps and installed the LGUP_DLL before the application (upon re-reading the original thread for the LGUP program I see that is the way you were supposed to do it the whole time, so much for reading comprehension) and the other was I ran it from a Win 7 VM instead of Win 10.
Big thanks to you and also to bender_007 for walking me through a bunch of stuff and recommending the VM approach.
I did the exact same thing, but I cannot get LGUP to recognize my device. Uninstalled and reinstalled drivers and all. Any other ideas?
I did the following:
Installed Windows 7 in a VM
Installed the LG Bridge software and ran in do it should update
Installed the LGUP DLL
Installed the LGUP software
Connected phone to VM
Then ran LGUP tool
bbenz3 said:
I did the following:
Installed Windows 7 in a VM
Installed the LG Bridge software and ran in do it should update
Installed the LGUP DLL
Installed the LGUP software
Connected phone to VM
Then ran LGUP tool
Click to expand...
Click to collapse
Just tried this, but still showing as unknown device. I thought that was going to work.
---------- Post added at 04:39 AM ---------- Previous post was at 04:20 AM ----------
What does the phone show up in Device Manager as when it is in download manager? Mine is showing as LGE Androidnet USB Serial Port. Is this the same for you?
hv same problem. but problem is pc can't recognize the phone for below step:
Step 3: On your PC, open up LGUP. The program shoud recognize the phone as H811 in COM3 or COM4. Highlight it and click the SELECT button.
can recognize another G4.
ilovelg4ever said:
hv same problem. but problem is pc can't recognize the phone for below step:
Step 3: On your PC, open up LGUP. The program shoud recognize the phone as H811 in COM3 or COM4. Highlight it and click the SELECT button.
can recognize another G4.
Click to expand...
Click to collapse
same... I think it might have to do with the from that was installed when I relocked the boorloader. I'm so stupid for that.
I was trying different drivers, but none have helped lgup to recognize my phone.
esteho said:
same... I think it might have to do with the from that was installed when I relocked the boorloader. I'm so stupid for that.
I was trying different drivers, but none have helped lgup to recognize my phone.
Click to expand...
Click to collapse
first of all, how can we make PC detect our G4?
actually, even w/o any drive installed in PC, the PC should detect G4 if it works normally.
Device Manager shows my device, but as "LGE AndroidNet USB Serial Port". From what I have read this may be it's bricked mode. Is there anyone with an idea on how to come back from this?
esteho said:
same... I think it might have to do with the from that was installed when I relocked the boorloader. I'm so stupid for that.
I was trying different drivers, but none have helped lgup to recognize my phone.
Click to expand...
Click to collapse
saaaaame......
model COM Ports
unknwon [com41, xTreme 3]
Can't use Send_command too.
MM relocked the boorloader was stupid.
I had this exact error yesterday. I used cdmatool to get some bands enabled so I could get AT&T LTE with an AT&T sim and T-Mobile phone. All went well, and on my way out I figured since I had done the fastboot oem unlock, I should probably relock it. BAD IDEA.
By the time I found this article I had figured that somehow I needed to reflash to a ROM with a unmodified bootloader. This article is great! Such a rare treasure - all of the links to the necessary software and a short-but-sweet guide all in one. This post saved me hours, maybe days, of searching and trial-and-error.
By the way, since I had already installed the LG device drivers (available here) it was not necessary to download and install the whole LG Bridge.
THANKS!
Many times tried to flash my H811 to 20i but always ended with blank screen...is it have to wait until 5 to 10 minutes to get the phone rebooted after flashing with LGUP? Because usually ended with blank screen and qd mode, have to revive using qfil, imei unknown, camera and google play store always closes.
I'm new to this forum, just throwing that out, so if I don't specify something, please let me know.
So, I have a Doogee x5 (not my main phone, recently bought a new one, so this one is just for stuff) that I softly-bricked via the kingroot app, since I was trying out this app before using it on my main phone. Now, why would I do that? My main phone is doogee shoot 2 which has a very annoying bloatware that opens the browser randomly. I did a little bit of searching, and turns out it was a system app. So naturally, I searched how to get rid of it, and saw that there was only a single answer: rooting the device. Now, I'm not an expert with this, so I searched for basic and simple solutions. I decided to try the method on my side-phone first, and thank god I did that.
Now, the Doogee X5 is stuck in a boot-loop, it does boot in recovery mode, it won't update or flash new ROMs (via "install updates from SD card") since for some reason, the installation is always aborted, and I don't know what to do next....
Would be glad for any help!
Thanks in advance, Raph/
Raphaeloper said:
I'm new to this forum, just throwing that out, so if I don't specify something, please let me know.
So, I have a Doogee x5 (not my main phone, recently bought a new one, so this one is just for stuff) that I softly-bricked via the kingroot app, since I was trying out this app before using it on my main phone. Now, why would I do that? My main phone is doogee shoot 2 which has a very annoying bloatware that opens the browser randomly. I did a little bit of searching, and turns out it was a system app. So naturally, I searched how to get rid of it, and saw that there was only a single answer: rooting the device. Now, I'm not an expert with this, so I searched for basic and simple solutions. I decided to try the method on my side-phone first, and thank god I did that.
Now, the Doogee X5 is stuck in a boot-loop, it does boot in recovery mode, it won't update or flash new ROMs (via "install updates from SD card") since for some reason, the installation is always aborted, and I don't know what to do next....
Would be glad for any help!
Thanks in advance, Raph/
Click to expand...
Click to collapse
Nobody is aware of any solution?
Have you tried flashing Official ROM via SP FLASH TOOL
perhaps that should be successful
That requires (if you already know this then skip it):
- doogee X5 preloader drivers (and by that I mean MediaTek MT6580 preloader drivers, or something like MediaTek MT65xx preloader drivers)
- SP Flash tool
- PC with Windows, and USB cable to connect it
- Official Doogee X5 ROM
And also, you should have some instructions how to connect it when flashing. On my doogee device (not X5) was something like, Click download in SP Flash Tool + Power + Volume Up + connect it to pc
zicmortal said:
Have you tried flashing Official ROM via SP FLASH TOOL
perhaps that should be successful
That requires (if you already know this then skip it):
- doogee X5 preloader drivers (and by that I mean MediaTek MT6580 preloader drivers, or something like MediaTek MT65xx preloader drivers)
- SP Flash tool
- PC with Windows, and USB cable to connect it
- Official Doogee X5 ROM
And also, you should have some instructions how to connect it when flashing. On my doogee device (not X5) was something like, Click download in SP Flash Tool + Power + Volume Up + connect it to pc
Click to expand...
Click to collapse
I've tried it, but the phone isn't detected by the PC, and I'm pretty sure I installed the preloader driver correctly...
Raphaeloper said:
I've tried it, but the phone isn't detected by the PC, and I'm pretty sure I installed the preloader driver correctly...
Click to expand...
Click to collapse
This happened to me once (same device) , try flashing a stock rom in SPFLASHTOOL (that you're sure that works) while pressing volume up button (usually it takes more than 15 secs of pressing for device to get detected), don't stop pressing it, then it will enter to META mode, a MTK brick-fixing mode integrated in DOOGEE X5, just while you press that volume up button, device should come to life for long enough to flash a stock working rom to it, don't stop pressing while rom is fully flashed
sorry bad english
hope it helps