Related
My milestone(Telus; BL 90.74) is pretty much bricked. I tried to do this, but like with everything else I do modding wise I failed horribly. It got to the point to where whenever I tried turning on my phone, it would stay frozen on the M logo. I've wasted my entire day searching from blogs to forums to videos trying to fix this but nothing worked. And now my phone won't even turn on unless I access the bootloader menu.
I know I have to reflash the sbf file, but the thing is my computer no longer detects my phone since the disaster. I'm really frustrated and stressed because of this. I thought doing a factory reset would do something but now all of my data on the phone is gone for nothing.
Can anyone please help? I know there's like 7 threads on this, but none of them help even if I follow the instructions step by step.
have made a backup? to open recovery?
Shoib said:
My milestone(Telus; BL 90.74) is pretty much bricked. I tried to do this, but like with everything else I do modding wise I failed horribly. It got to the point to where whenever I tried turning on my phone, it would stay frozen on the M logo. I've wasted my entire day searching from blogs to forums to videos trying to fix this but nothing worked. And now my phone won't even turn on unless I access the bootloader menu.
I know I have to reflash the sbf file, but the thing is my computer no longer detects my phone since the disaster. I'm really frustrated and stressed because of this. I thought doing a factory reset would do something but now all of my data on the phone is gone for nothing.
Can anyone please help? I know there's like 7 threads on this, but none of them help even if I follow the instructions step by step.
Click to expand...
Click to collapse
Do you get any error shown while going into bootloader mode?
Sent from my Milestone using Tapatalk
maybe try a diffrent computer first or try the official motorola update software?
press "up" on keyboard when power on, can it be detect by rsd now?
Sent from my Milestone using XDA App
max_avatar said:
have made a backup? to open recovery?
Click to expand...
Click to collapse
No, I haven't made a backup yet. I haven't accessed openrecovery either, the guide gave me a headache.
sileshn said:
Do you get any error shown while going into bootloader mode?
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
It says "Battery Ok
Ok to program
connect USB
Data Cable"
smokeymacweed said:
maybe try a diffrent computer first or try the official motorola update software?
Click to expand...
Click to collapse
I could try that by putting an official update.zip so the boot loader will accept. Problem is there isn't any updates further to what I have and froyo womn't come anytime soon unless you were referring to something else.
DummyPLUG said:
press "up" on keyboard when power on, can it be detect by rsd now?
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
Let me try this. I'm going to bed for now, Ill post results tomorrow.
You can try installing your usb drivers again and try.Since you did not get any error in the bootloader mode, it could be problems with your usb drivers.
Uninstall the usb drivers and reinstall them again. Then try.
BTW, which version of rsdlite are you using?
Helo
Maybe tray this:
- Download an RSD Lite (I use 4.7)
- Download an GOT firmware from: and-developers.com / sbf:milestone (bottom of site)
- Set the phone to bootloader mode
- Start RSD Lite with Administrator permissions
- Connect the phone
- Select the downloaded sbf file
- When U see phone connected click Start
Sorry for my english
xdazoli said:
Helo
Maybe tray this:
- Download an RSD Lite (I use 4.7)
- Download an GOT firmware from: and-developers.com / sbf:milestone (bottom of site)
- Set the phone to bootloader mode
- Start RSD Lite with Administrator permissions
- Connect the phone
- Select the downloaded sbf file
- When U see phone connected click Start
Sorry for my english
Click to expand...
Click to collapse
Ok, I did everything you said and flashed it with A853_Telus_Firmware_SHOLS_U2_03.10.0__USASHLSMR2TLSB1B2B505F.0R_1FF.sbf. But now it still gets stuck at the moto sign
Edit: I think I might have a solution as I flashed the phone with vulnerable_recovery_only_RAMDLD90_78.sbf which will let me use an update.zip. The only problem is I can't access my memory card and I don't have anything that could at home.
Edit: Ok, I fixed my phone and now it has 2.2.1. Thanks guys, I appreciate the help.
Ok guys ... this is the problem ...:crying:
I have (had) a Droid Bionic running ics leak 232 in Brazil (GSM/UMTS ... thanks to xda developers - "bionic in t mobile" thread).
While messing around with the phone connected to linux (baaad idea) at some point I deleted the bootloader ("happy finger" + lack of knowledge os linux).
Now, my phone doesnt power up and RSD Lite doesnt recognize it when connected but, when I connect it to the PC, a green light lits at the top right corner of the phone and Windows recognize it, at the device manager, as a OMAP4430 USB under TI Board tab. This leads me to think that some kind of life still exists down there or, the hardware is alive and waiting for the right software.
After a long quest for a solution, I found this: "forum.gsmhosting.com/vbb/f634/unbrick-dead-samsung-gt-i9250-galaxy-nexus-gt-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/index9.html".
Now I think this is the way out of this mess (is the same hardware, OMAP platform from Texas Instrument), if exists any, but this was made for Samsung, by Samsung technicians, and doesnt apply to Motorola. :crying: again.
So, is there anyone who can help me, or have any idea of what can be done (other than trow it away or use it as a paper weight)?
Any help would be most appreciated.
Regards
I saw you haven't had any replies yet. My roommate had a similar problem, he managed to mount his system partition automatically and thought his SD card was partitioned into 10 or more partitions.
So he reformated the mount and had a dead phone right after, said he only got a small white light on his notification light when plugged in.
I didn't get a chance to check it out before he took it to Verizon for a refurb, so sadly I'm not much help. Just thought I'd input anything I knew since you still had an empty thread. Hope it comes back alive!
Sent from my kitchen toaster.
Have you tried using the command line version of moto-fastboot? It might work, but might not work... I think you need to boot into fastboot mode, but I could be wrong... Either way it's worth a try.
Also, does anything happen when you try to hold down the vol+ and VOL- buttons when powering on the phone?
Sent from my XT894 running ICS
its dead
danifunker said:
Have you tried using the command line version of moto-fastboot? It might work, but might not work... I think you need to boot into fastboot mode, but I could be wrong... Either way it's worth a try.
Also, does anything happen when you try to hold down the vol+ and VOL- buttons when powering on the phone?
Sent from my XT894 running ICS
Click to expand...
Click to collapse
Thank you for your answer danifunker;
The phone is dead. Pressing buttons does nothing. The only thing that happens is to lit the notification green light at the top right corner of the screen WHEN a plug it in my PC and windows keep telling me this is a unknown device. I unsuccessfully used OMAPFlash, but installing the usb drives that came with it, when I plug it to the PC, windows device manager shows me a new device "OMAP4430 USB" under a new tab "TI Board" , whitch is not recognized by RDS lite or adb or fastboot. Is only recognized by OMAPFlash. If you dont know about OMAPFlash, I found it here http://forum.xda-developers.com/showthread.php?t=1701471 , but this procedure is for a Samsung, witch uses the same platform (OMAP4430), but I dont have the right configurations for the Droid Bionic.
Just the same
chrisp6825 said:
I saw you haven't had any replies yet. My roommate had a similar problem, he managed to mount his system partition automatically and thought his SD card was partitioned into 10 or more partitions.
So he reformated the mount and had a dead phone right after, said he only got a small white light on his notification light when plugged in.
I didn't get a chance to check it out before he took it to Verizon for a refurb, so sadly I'm not much help. Just thought I'd input anything I knew since you still had an empty thread. Hope it comes back alive!
Sent from my kitchen toaster.
Click to expand...
Click to collapse
Thank you for your interest.
If you have any further notice about your roommate problem, please let me know.
And, if you manage to post a reply from your kitche toaster, I am sure you will be able to help in this problem. looking forward for that. :laugh:
pjcw said:
Thank you for your interest.
If you have any further notice about your roommate problem, please let me know.
And, if you manage to post a reply from your kitche toaster, I am sure you will be able to help in this problem. looking forward for that. :laugh:
Click to expand...
Click to collapse
Can you explain exactly how you deleted the bootloader off of the Bionic? Knowing EXACTLY (what you ran, what you typed) what you did will help us help you.
As an aside, I had no idea there was a SGSII-OMAP variant, but I am not big on the Samsung phones, just assumed they've only been using their own SoCs for a while now...
Hi podspi.
Sorry for the delay.
As a matter of fact, wasnt me that bricked the phone. A friend o mine tryed to flash a gelly beam version, and did it via Fastboot,, under Linux (of witch I know almost notingh).
He told me that the problem was that he made:
fastboot erase mbm
and then
fastboot reboot bootloader
and so the bootloader was lost. He missed a step.
Any help will be greatly aprecieted.
Regards
IOW, since the mbm has been erased, and the mbmflashable hasn't been flashed, there is no way to get it into the bootmenu sceen anymore, right?
Hmmm. Let me ask some other folks too.
Sent from my ASUS Transformer Infinity Running Tapatalk.
I wonder if a factory cable would work to get it to flash mode? Why would you even mess with the bootloader trying to install ICS? You do that through recovery, not fastboot.
I was on ICS ... This was an attempt to get it to JellyBeen ... I, also, dont know why. I was perfectly happy with ICS working in GSM/WCDMA. This is why I am so sad ... It was a very stupid thing to do ... As a matter of fact, I will get a factory cable, but I dont think this is gonna help. Anyways, I am keeping it by side to remember me not to mess with things that are working fine. I'm kind of losing hope that it can fixed.
Regards
pjcw said:
I was on ICS ... This was an attempt to get it to JellyBeen ... I, also, dont know why. I was perfectly happy with ICS working in GSM/WCDMA. This is why I am so sad ... It was a very stupid thing to do ... As a matter of fact, I will get a factory cable, but I dont think this is gonna help. Anyways, I am keeping it by side to remember me not to mess with things that are working fine. I'm kind of losing hope that it can fixed.
Regards
Click to expand...
Click to collapse
I think we need to figure out how you flash mbm back onto there. Actually, I think it's mbmloader that you need on there...
mbm = Motorola Boot Manager (?) maybe.
After reading this page: http://omappedia.org/wiki/Bootloader_Project
I believe, mbm = uboot, mbmloader = x-loader
Just found this page... http://www.droid-developers.org/wiki/How_to_load_mbmloader_from_SD_card
download the SBF and grab the mbmloader for ICS. See if you can get a little further...
SamuriHL sHouse of Bionic restored mine when all I could get was fastboot.
Sent from my DROID BIONIC using xda premium
It won't help this. It needs to be flashed at the omap level and since moto isn't about to release the configuration files for the Bionic you can consider this one permanently bricked.
Sent from my Xoom using Tapatalk 2
I tend to agree with SamuriHL. I was thinking that the configuration souldn't be so diferent than others (like Samsung) that uses the same platform (omap). I know that it's naive, but what else could I do. Also, I need the signed files for x-loader and u-boot, of witch I think danifunker is right, this means mbm and mbmloader, that I have, but they came in bin format and not image format (.img). I will try to convert them to .img, but I am at the end of my resources (not that they are so many), and will give up shortly. At this point (giving up), I will buy another cellphone AND IT WONT BE A MOTOROLA, Probably a HTC or a Samsung. But I will keep Bionic at my desktop, as a paperweight, to remind me how I liked it, how I mess things up.
Anyways, if I manage to solve this problem, I will post here, and I wish to thank everyone that spare their time to try to help people. If anyone have any suggestion, I'll be glad to follow.
If you modify them in any way they'll no longer be signed and won't work. Someone else already went through several weeks of trying to fix their phone that had similar issues. He's well connected and still couldn't get the necessary files. Don't necessarily give up on Moto, though...it's not their fault we're stuck with locked bootloaders. Blame VZW for that one. Even Samsung was forced to lock the S3 on VZW. Things may change some day. We'll have to wait and see.
You can always get RAZR i with the unlockable bootloader! that might make things a bit easier...
IT'S DONE!!!!!!!!!
IT'S DONE ....... IT IS ALIVE AGAIN :highfive:
Guys. My phone is alive again. Thanks to FRAGULINA and PICGRABBER for their unvaluable help. It is now running GSM with data enabled (3G) with ICS 232, rooted, thanks to FRAGULINA and HTCFlyerX ( http://forum.xda-developers.com/showthread.php?p=31101192&highlight=build+prop#post31101192).
Well, I'm attaching 2 zip files. One is omapflash and the other is "THE FILES", and instructions on the "release_notes.txt". This works on LINUX.
And works like a charm. Took me (much) less than 5 minutes to get me from a dead phone to bootloader fastboot. And the rest is history. Well known procedures.
Thanks to all of you that helped or tryed to help.
Enjoy.
To those who have an interest in new challanges (as I know you are), i'm opening a new quest and would appreciate your thoughts.
I have at hand an atrix 2 and I want to find where in hell is the subsidy code writen at and how can I read it. This new quest will be at the proper location at the atrix 2 forum.
I think we won this challange. Lets go for another.
Any doubts I am available to help.
Regards.
Holy.....uh, well, WOW! I'm in awe here on this one. WELL DONE!!!!!!!
SamuriHL said:
Holy.....uh, well, WOW! I'm in awe here on this one. WELL DONE!!!!!!!
Click to expand...
Click to collapse
Can we use this method to flash any firmware to the phone? Lets say you load the latest ICS, maybe we use this method which restores the most original bootloader to the phone and then flash to any version?
Which version did you fastboot to?
pjcw said:
IT'S DONE ....... IT IS ALIVE AGAIN :highfive:
Guys. My phone is alive again. Thanks to FRAGULINA and PICGRABBER for their unvaluable help. It is now running GSM with data enabled (3G) with ICS 232, rooted, thanks to FRAGULINA and HTCFlyerX ( http://forum.xda-developers.com/showthread.php?p=31101192&highlight=build+prop#post31101192).
Well, I'm attaching 2 zip files. One is omapflash and the other is "THE FILES", and instructions on the "release_notes.txt". This works on LINUX.
And works like a charm. Took me (much) less than 5 minutes to get me from a dead phone to bootloader fastboot. And the rest is history. Well known procedures.
Thanks to all of you that helped or tryed to help.
Enjoy.
To those who have an interest in new challanges (as I know you are), i'm opening a new quest and would appreciate your thoughts.
I have at hand an atrix 2 and I want to find where in hell is the subsidy code writen at and how can I read it. This new quest will be at the proper location at the atrix 2 forum.
I think we won this challange. Lets go for another.
Any doubts I am available to help.
Regards.
Click to expand...
Click to collapse
This is unbelievable. After talking with you on Gtalk, I thought this was a permanent brick. Thanks for the files...I have a guy on gtalk right now who can benefit from these.
I was rooting my phone I got to the point where I accepted the 4.4 update it downloaded installed shut off and that was it. I have tried every button combination, It had plenty of charge, and just to make sure I plugged it into a wall charger for 20 minutes. Any suggestions? The screen doesn't come on at all. Thanks, Garrett.
Follow the instructions on how to enter stock recovery. This should help.
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/94946/p/30,6720,8696
Sent from my XT1060 using Tapatalk
Still no luck...
garrettpen said:
Still no luck...
Click to expand...
Click to collapse
Sorry bud. Sounds like you might have bigger issues than I can help you with. However, you should try to connect it to your computer and see if you get anything. Also keep trying to power it on while on a USB or charger.
Hopefully someone with a similar experience can chime in.
Sent from my XT1060 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2477132
You can try to flash your phones stock ROM using this tool kit if you can get into the Boot loader. I just used it to flash back to stock on my sprint moto x. I know you are in a different situation but I can't hurt to try
Sent from my XT1056 using Tapatalk
garrettpen said:
I was rooting my phone I got to the point where I accepted the 4.4 update it downloaded installed shut off and that was it. I have tried every button combination, It had plenty of charge, and just to make sure I plugged it into a wall charger for 20 minutes. Any suggestions? The screen doesn't come on at all. Thanks, Garrett.
Click to expand...
Click to collapse
hold power button for 1 min if you feel the phone vibrate that is good.
now try holding Volume Up + Power will it boot into the bootloader.
If yes great time to restore to stock
If No then your phone is hard bricked and you will have to get it replaced.
one easy way to find out if your phone is hard bricked is to plug it into the computer and see what drivers it tries to install
if it say qhsusb_dload then i know for a fact that your phone is Hard bricked.
If that is the case call your carrier or go to a local store and tell them that your phone was on 4.2.2 and you downloaded the 4.4 OTA and it rebooted to install it and now it won't turn on at all they should give you a brand new phone because it was the phones problem.
When you get your new phone please post here first with What Carrier Moto X you have and what android version it is on 4.2.2 / 4.2.2 Camera Update / 4.4. and i will help you get your phone rooted and up and running correctly
Good Luck My Friend and please don't be afraid to ask for help
Mist likely hard bricked, you're not the only person this has happen too and won't be the last, if you're getting the driver mussing as previously posted ,I agree and its hard bricked. Which 4.2 stick firmware where you on? Pre camera update? At least you can call you're carrier and say you attempted to install an ota which in fact did brick your phone don't tell them you tried to root it of course, good.luck
Sent on my Moto X
I'll gladly leave lg g4 forum been the most un helpful experience ever between 140 views on both threads ..and even from the most recognized devs with nothing but simplistic answers and guides that ive read already yet the needed answers are known ..... must be considered extra work to explain and help out with my indepth matter .The minute you run across a forum with someone who had this issue almost exactly they say oh edit...fixed now .
But the most stupidest of questions can get answered on here .
Had to waist money on a nexus 5x all cause no one can explain how this great Lg up tool works but apparently it is a botched process if your device shows as Unknown model with no fix no in depth explanation Lg bridge does not work for a true soft brick it only meant to upgrade a device that actually as a bootable O.S
So where does that leave me
Sent from my Nexus 5X using XDA Free mobile app
Did you post your issue in the official LG UP thread or in the back to stock marshmallow kdz thread where the file that you need to get this back to stock using LG Up is listed. If you would have searched in the kdz back to stock thread you would have seen that another user helped me with the exact same issue ss you. Was ready to turn my phone in for warranty before finding my answer there. Your phone is still able to boot into recovery manually but you have to do it a few times then you install a rom that's saved on your sd card and your phone will boot up. Hopefully you still have your G4 and can try this method.
Sent from my LG-H811 using Tapatalk
srod562 said:
Did you post your issue in the official LG UP thread or in the back to stock marshmallow kdz thread where the file that you need to get this back to stock using LG Up is listed. If you would have searched in the kdz back to stock thread you would have seen that another user helped me with the exact same issue ss you. Was ready to turn my phone in for warranty before finding my answer there. Your phone is still able to boot into recovery manually but you have to do it a few times then you install a rom that's saved on your sd card and your phone will boot up. Hopefully you still have your G4 and can try this method.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Really I'm thinking not explain to me how my lg g4 phone can boot into recovery manually when i relocked the boot loader through adb.
All I have is down load mode No regular O.s boot no fast boot mode
Its all secure boot error 1003
I download the kdz 20i from auto primes code fire link that's the only kdz for 20i around .
The issue is lg up tool sees my device as Unknown model because I was on a ROM when this happened apparently there's no fix unless you can boot into the O.s and edit the ROM
Sent from my Nexus 5X using XDA Free mobile app
srod562 said:
Did you post your issue in the official LG UP thread or in the back to stock marshmallow kdz thread where the file that you need to get this back to stock using LG Up is listed. If you would have searched in the kdz back to stock thread you would have seen that another user helped me with the exact same issue ss you. Was ready to turn my phone in for warranty before finding my answer there. Your phone is still able to boot into recovery manually but you have to do it a few times then you install a rom that's saved on your sd card and your phone will boot up. Hopefully you still have your G4 and can try this method.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
What do you mean a few times power and volume down and release power and press it again then choose wipe with YES
Yea I tried all that its secure boot error because my boot loader is re-Locked while I was rooted and with twrp
Sent from my Nexus 5X using XDA Free mobile app
I'm wanting to believe that I need to just forget I have the g4 and break it in 3 half's and toss it
So the headache goes away
Sent from my Nexus 5X using XDA Free mobile app
androidddaaron said:
I'll gladly leave lg g4 forum been the most un helpful experience ever between 140 views on both threads ..and even from the most recognized devs with nothing but simplistic answers and guides that ive read already yet the needed answers are known ..... must be considered extra work to explain and help out with my indepth matter .The minute you run across a forum with someone who had this issue almost exactly they say oh edit...fixed now .
But the most stupidest of questions can get answered on here .
Had to waist money on a nexus 5x all cause no one can explain how this great Lg up tool works but apparently it is a botched process if your device shows as Unknown model with no fix no in depth explanation Lg bridge does not work for a true soft brick it only meant to upgrade a device that actually as a bootable O.S
So where does that leave me
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
I actually posted my solution in the 20I thread relatively early. I am sorry no one helped you sooner.
If you used an iternational Rom and have an unrecognized model LGBridge is able to update your phone through update error recovery.
Vseprz said:
I actually posted my solution in the 20I thread relatively early. I am sorry no one helped you sooner.
If you used an iternational Rom and have an unrecognized model LGBridge is able to update your phone through update error recovery.
Click to expand...
Click to collapse
0fx
This is impossible lg bridge is not a semi brick or full brick fix tool its a upgrade tool from what I see
lts for a device that's in a bootable operating state allowing firmware upgrade .
It can only read in a device in mtp mode If you only have download mode that doesn't help at all Withp lg bridge The unknown device model issue is only seen with the Other tool Caller Lg up.
I go on and on and on and noone takes my exact scenario and breaks it down .
Sent from my Nexus 5X using XDA Free mobile app
androidddaaron said:
0fx
This is impossible lg bridge is not a semi brick or full brick fix tool its a upgrade tool from what I see
lts for a device that's in a bootable operating state allowing firmware upgrade .
It can only read in a device in mtp mode If you only have download mode that doesn't help at all Withp lg bridge The unknown device model issue is only seen with the Other tool Caller Lg up.
I go on and on and on and noone takes my exact scenario and breaks it down .
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
Did you even try it? My phone was in the 1003 boot error with unknown model in LGUp. I only had download mode. Give it a shot before you dismiss it.
Vseprz said:
Did you even try it? My phone was in the 1003 boot error with unknown model in LGUp. I only had download mode. Give it a shot before you dismiss it.
Click to expand...
Click to collapse
I did once I couldn't get bridge to connect with update recovery error
Then difference here is was you boot loader relocked or still unlocked mine is re locked in this state
Sent from my Nexus 5X using XDA Free mobile app
androidddaaron said:
I did once I couldn't get bridge to connect with update recovery error
Then difference here is was you boot loader relocked or still unlocked mine is re locked in this state
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
Actually my bootloader was locked at the point I used LGBridge.
Not being able to connect suggests driver problems. Reload them and try again.
Vseprz said:
Actually my bootloader was locked at the point I used LGBridge.
Not being able to connect suggests driver problems. Reload them and try again.
Click to expand...
Click to collapse
So you had twrp plus rooted and relocked boot loader all before attempting lg bridge that's my exact scenario but what about bridge trying to install then Lg bridge AIR Drivers
Sent from my Nexus 5X using XDA Free mobile app
Vseprz said:
Actually my bootloader was locked at the point I used LGBridge.
Not being able to connect suggests driver problems. Reload them and try again.
Click to expand...
Click to collapse
No that's not true I guarantee you wasn't
Relocked boot loader u couldn't have been
I am for sure about this and lg bridge sees my device when I choose update recovery error it tells me there are No update errors that can be recovered
So how does that prove it fixed yours when we was in the same scenario?
Sent from my Nexus 5X using XDA Free mobile app
androidddaaron said:
No that's not true I guarantee you wasn't
Relocked boot loader u couldn't have been
I am for sure about this and lg bridge sees my device when I choose update recovery error it tells me there are No update errors that can be recovered
So how does that prove it fixed yours when we was in the same scenario?
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
I made a mistake when upgrading my phone from LP to MM and accidentally left my Bootloader locked when trying to upgrade, nearly bricking my phone. I was receiving a 1003 error every time I tried to boot. I posted this in a different thread last month for someone else who had the same problem.
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.../H811/H81120i/
Download LGUP and install it. I used the DropBox link in this thread:
http://forum.xda-developers.com/g4/h...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.
Click to expand...
Click to collapse
Donut42 said:
I made a mistake when upgrading my phone from LP to MM and accidentally left my Bootloader locked when trying to upgrade, nearly bricking my phone. I was receiving a 1003 error every time I tried to boot. I posted this in a different thread last month for someone else who had the same problem.
Click to expand...
Click to collapse
Once again I was on a ROM when in did all this if it wasn't for that fact Lg Up would see my device model as h11 not unknown
So tell me how to get past the Unknown device model issue due to bring on a Custom Rom when this happened
Sent from my Nexus 5X using XDA Free mobile app
Donut42 said:
I made a mistake when upgrading my phone from LP to MM and accidentally left my Bootloader locked when trying to upgrade, nearly bricking my phone. I was receiving a 1003 error every time I tried to boot. I posted this in a different thread last month for someone else who had the same problem.
Click to expand...
Click to collapse
The issue lies in step 3
The phone doesn't recognize as h811 it is as unknown model
If you know a way around that I'd love to know because every day I Go to snap the phone in half and recycle it as trash I stop my self thinking maybe one person will get that I was on a ROM when this happened and have a solution for Lg up to see my device as h811
Sent from my Nexus 5X using XDA Free mobile app
androidddaaron said:
The issue lies in step 3
The phone doesn't recognize as h811 it is as unknown model
If you know a way around that I'd love to know because every day I Go to snap the phone in half and recycle it as trash I stop my self thinking maybe one person will get that I was on a ROM when this happened and have a solution for Lg up to see my device as h811
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
That sounds like a driver issue. When I did mine I was also on a custom ROM. I had to manually remove all LG drivers via the Device Manager and install the LG Bridge for its LG USB drivers before the LGUP tool would recognize it. Before I did that it wouldn't even see my phone.
Donut42 said:
That sounds like a driver issue. When I did mine I was also on a custom ROM. I had to manually remove all LG drivers via the Device Manager and install the LG Bridge for its LG USB drivers before the LGUP tool would recognize it. Before I did that it wouldn't even see my phone.
Click to expand...
Click to collapse
I would like to think that butt LG up is evidently seeing a connection from my phone to the PC it's just reading the device model as unknown because if I unplug the phone it goes back to reading nothing I plug it back in pops up red box model unknown I know it's reading the phone in LG up because it actually tells you the ROM it detects which is Xtreme ROM by micro mod
Not only that LG Mobile support tool read my phone and says software is up-to-date LG flash tool 2014 attempts to flash but fails because it is not compatible apparently with Android 6.0
Nlg bridge when I try to use that tool sees my phone when I choose update recovery error and says there are no recoveries to update I don't believe it's a driver issue I think it's the fact that I'm stuck on a ROM that is edited in some fashion that will not allow the tool to to proceed to the next step and if you look at the LG up thread it talks about a member explaining about the unknown device model issue is due to the ROM developer editing his ROM name somehow
Everyone that has gotten past the unknown device model happen to have an unlocked bootloader or was just trying to do a regular upgrade and still had an OS to boot into there's just no way around this mess
Sent from my Nexus 5X using XDA Free mobile app
Guess this thread has run its course
Closed at OP's request
So i have a Moto g xt1072 wich i got second hand.. i got it into recovery mode and eventually got it working, but it was really unstable, so i wanted to reflash the stock rom, because it looked like the current one on the phone was corrupted (i was running android 6.0) (btw i have a xt1068 as my daily driver, but i want this to work again)
So i started flashing http://forum.xda-developers.com/moto-g-lte/general/stock-6-0-marshmallow-europe-reteu-t3338075 <-this
but i had errors and it was failing multiple times.. so i looked up some tutorials, and most of them were unlocking the bootloader at the beginning, so i was unlocking and locking the bootloader trying to get the commands to work,
then i found a tutorial wich coppyd all of the commands at once, so i tried that.. screen went black..
Wont boot into recovery, 3sec method or 120 sec method, and connects to my pc as QHSUSB_BULK
luckily i made a picture of the recovery when i tried to flash:
http://imgur.com/8avCk3T
I think i may need to blank flash, but im not certain..
I would also like to find the firmware for this phone that wont brick it..
Can anyone help?
Need more info?
Please just ask me, i will respond immediately
i dont care what i need to do.. even if i need to hardwire (because im really good at those finicky things)
Thanks for reading XD
Same issue here. I flashed a stock image and something must've gone wrong at some point
hamzahrmalik said:
Same issue here. I flashed a stock image and something must've gone wrong at some point
Click to expand...
Click to collapse
you probably also flashed the vootloader and the bootanimation, these are known to give problems, but ive foubd a test point on the pcb which brings the phone in a les hard bricked state, but ive yet to find a method to unbrick the phone..
ill keep you posted
ora69 said:
you probably also flashed the vootloader and the bootanimation, these are known to give problems, but ive foubd a test point on the pcb which brings the phone in a les hard bricked state, but ive yet to find a method to unbrick the phone..
ill keep you posted
Click to expand...
Click to collapse
Sorry could you please explain. How can a phone be less hard bricked. Thanks
Sent from my A0001 using Tapatalk
hamzahrmalik said:
Sorry could you please explain. How can a phone be less hard bricked. Thanks
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
okay, so there are different types of hardbricks, all act the same, but one is harder to unbrick than the other, there is qh usb bulk and qhas bulk with numbers behind it, search for force unbrick lg g2,
now the problem is, it should be easy to unbrick the phone at thsi point, but im not an expert in that and have no idea what to do now xD so i posted it on xda, but no one answered me.. xD hopefully this clears it up some more
ora69 said:
okay, so there are different types of hardbricks, all act the same, but one is harder to unbrick than the other, there is qh usb bulk and qhas bulk with numbers behind it, search for force unbrick lg g2,
now the problem is, it should be easy to unbrick the phone at thsi point, but im not an expert in that and have no idea what to do now xD so i posted it on xda, but no one answered me.. xD hopefully this clears it up some more
Click to expand...
Click to collapse
Oh ok I get you. Mines USB bulk 9000 or something i can't remmeber now
Sent from my A0001 using Tapatalk
ora69 said:
So i have a Moto g xt1072 wich i got second hand.. i got it into recovery mode and eventually got it working, but it was really unstable, so i wanted to reflash the stock rom, because it looked like the current one on the phone was corrupted (i was running android 6.0) (btw i have a xt1068 as my daily driver, but i want this to work again)
So i started flashing http://forum.xda-developers.com/moto-g-lte/general/stock-6-0-marshmallow-europe-reteu-t3338075 <-this
but i had errors and it was failing multiple times.. so i looked up some tutorials, and most of them were unlocking the bootloader at the beginning, so i was unlocking and locking the bootloader trying to get the commands to work,
then i found a tutorial wich coppyd all of the commands at once, so i tried that.. screen went black..
Wont boot into recovery, 3sec method or 120 sec method, and connects to my pc as QHSUSB_BULK
luckily i made a picture of the recovery when i tried to flash:
http://imgur.com/8avCk3T
I think i may need to blank flash, but im not certain..
I would also like to find the firmware for this phone that wont brick it..
Can anyone help?
Need more info?
Please just ask me, i will respond immediately
i dont care what i need to do.. even if i need to hardwire (because im really good at those finicky things)
Thanks for reading XD
Click to expand...
Click to collapse
So that link to another thread in XDA forum, I think I had a similar experience. I too have the XT1072 as I live in the UK. now here on XDA you have to be careful and ask 3 4 maybe 5 times before someone listens properly. I know it is hard for the devs with so many dumb noobs asking so many dumb questions, I include myself as a noob so no worries. Anyway to get to the point that link is not referring to our phone the XT1072. You should ignore LTE in your search criteria, it will always point you towards the 2015 model and believe you me all roms in my experience area very device specific. You need to simply put Moto G 2nd gen 2014 in search criteria when it comes to searching for custom recoverys and/or stock ROMS. The Titan.IMG is always a safe bet if I remember correctly, dont take my word for it, I have been known to have a memory like a sieve now and again, the problem with getting older, cache gets smaller and smaller, lol! Best of luck!
hamzahrmalik said:
Sorry could you please explain. How can a phone be less hard bricked. Thanks
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Read the beginning on this article: http://rootmyandroid.org/how-to-unbrick-your-android-device-the-ultimate-guide.html/
the bricked term is a common misconception for phones that still turn on..