Related
I was following this video on instruction on unlocking my atrix on youtube titled "Motorola Atrix: Unlock and Upgrade to GB - Unlock P1"
My atrix was already updated to 2.3.4
Now Using RSD Lite.. idk what happened, the process failed.. and everytime I turn on my phone, it tells me "OS not found" or something like that.
It says:
SVF:105:1:2
Failed to boot 0x1000
NO OS detected, going to RSD mode in 5 seconds
Press a key to stop count down
Available Modes are:
1.RSD
2. Fastboot
3. NvFlash
4. BP HW Bypass RSD
5. BP HW BYPASS QC DLOAD
6. BP HW Diag & Boot AP
7. BP HW Bypass BP Only
8. BP SW Bypass RSD
9. Android Recovery
10. Boot Android (No BP)
11. Device UID
12 console=ttyS0, 115200n8
13. Early USB Enumeration
14. BP Tools
Can someone please help my get my phone working again.. I can't even live like a day without my phone. Is my phone hardbricked or is there any way to revive it?
Any help would be appreciated.
Thanks
try the next step
Just continue the fastboot commands and you should be fine, same thing happen to me
Sent from my MB860 using XDA App
Javi97100 said:
Just continue the fastboot commands and you should be fine, same thing happen to me
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Which fastboot commands, because I tried to use the ones such
fastboot flash preinstall preinstall.img
fastboot reboot
but nothing worked.
Try this
fastboot oem unlock
(Then it will give you a code, and type it again with code at the end)
Then when phones says unlocked
Type
fastboot reboot
Sent from my MB860 using XDA App
cpatel90 said:
Now Using RSD Lite.. idk what happened, the process failed.. and everytime I turn on my phone, it tells me "OS not found" or something like that.
It says:
SVF:105:1:2
Failed to boot 0x1000
Click to expand...
Click to collapse
Guys, where do you get the courage to do the unlock process that bricked so many phones without reading instructions?
When flashing pudding over OTA 2.3.4, Failed to boot is a common error.
You need to redo the fastboot unlock commands and all will be fine.
This is explained in the pudding thread, and gets explained every day again and again with each new thread that newbies create.
xploited said:
Guys, where do you get the courage to do the unlock process that bricked so many phones without reading instructions?
When flashing pudding over OTA 2.3.4, Failed to boot is a common error.
You need to redo the fastboot unlock commands and all will be fine.
This is explained in the pudding thread, and gets explained every day again and again with each new thread that newbies create.
Click to expand...
Click to collapse
Also if you do some looking around you'll find this http://forum.xda-developers.com/showthread.php?t=1182871 which I think was a SUPER easy way to unlock my bootloader and I didn't run into any of the issues that so many have ran into.
From unlocked/rooted GB Atrix
thanks for the help guys.. but i think its over for my phone.
it doesn't even turn on anymore. the green light comes on for one second and turns back off. i think i'll just have to get a new phone.
cpatel90 said:
thanks for the help guys.. but i think its over for my phone.
it doesn't even turn on anymore. the green light comes on for one second and turns back off. i think i'll just have to get a new phone.
Click to expand...
Click to collapse
You weren't a hard brick. You just didn't complete the steps. Did you do something else to it since your initial post? Sounds like your battery is drained, which means you need to charge it externally.
cpatel90 said:
thanks for the help guys.. but i think its over for my phone.
it doesn't even turn on anymore. the green light comes on for one second and turns back off. i think i'll just have to get a new phone.
Click to expand...
Click to collapse
uhh... sounds like your battery is drained. find someone who can charger your battery (another Atrix owner, or a Droid X owner) and try again PROPERLY.
you were trying to flash PREINSTALL to your phone? that is NOT the OS. that roots your phone once it's already installed. you need to install the SYSTEM.img and related files. you really need to read the entire guide as it so far looks like you didn't read anything.
you need to use moto-fastboot to flash System images, not regular fastboot.
http://forum.xda-developers.com/showthread.php?t=1138092
use these images and this guide, which coincidentally warns you NOT to RSD from the stock 2.3.4 and is stickied at the top of the dev forum.
http://forum.xda-developers.com/showthread.php?t=1160408
i seem to have hard bricked my atrix, doing the same thing.. well, my brother did anyway. but i somehow forced it to download mode. and re-flashed it. Works perfectly.
caleb4992 said:
i seem to have hard bricked my atrix, doing the same thing.. well, my brother did anyway. but i somehow forced it to download mode. and re-flashed it. Works perfectly.
Click to expand...
Click to collapse
that's a soft brick.
svf :105.1:2
failed to boot 0x1000
show this..........
i cant to move it to android recovery cause there no option to move
after showing this error automatically switch off my phone.....
any solution
bivrat said:
svf :105.1:2
failed to boot 0x1000
show this..........
i cant to move it to android recovery cause there no option to move
after showing this error automatically switch off my phone.....
any solution
Click to expand...
Click to collapse
Yea, thats a hard brick
Sent from my MB860 using XDA App
bivrat said:
svf :105.1:2
failed to boot 0x1000
show this..........
i cant to move it to android recovery cause there no option to move
after showing this error automatically switch off my phone.....
any solution
Click to expand...
Click to collapse
bivrat,
You've asked this same thing maybe like 5 times already and each time we've told you that there is no fix and you have to get a new phone.
Need urgent reply
Guys.. i have a favour to ask!
m in a search for a second hand moobile and found this ATRIX 4G unlocked edition which has run into this problem!
"A recent Over The Air upgrade 2.3.6 to the phone (which should have been avoided on a rooted phone) has made the phone non working.
The phone does not boot, and displays the message:
Failed to Boot 1...
Entering RSD Mode."
Guys please let me know if this coud be fixed or not, as i am in a real mood to buy this one!
bivrat said:
svf :105.1:2
failed to boot 0x1000
show this..........
i cant to move it to android recovery cause there no option to move
after showing this error automatically switch off my phone.....
any solution
Click to expand...
Click to collapse
Did you try the Unlock v4.2 app from this site? Option 3 of the menu very well might fix it for you. Well worth a shot if you haven't tried it yet.
Ok so apparently I flashed a the kitchen sink rom and when phone booted up it stop and said fail to boot 2 but I flashed the and files in the video from qbking77 and now it says fail to boot 4 can anybody help me please. It the only phone I got and I'm not available for an upgrade till february
Robert5686 said:
Ok so apparently I flashed a the kitchen sink rom and when phone booted up it stop and said fail to boot 2 but I flashed the and files in the video from qbking77 and now it says fail to boot 4 can anybody help me please. It the only phone I got and I'm not available for an upgrade till february
Click to expand...
Click to collapse
What version soft ware did you start with.
the android version ? i was running on 2.3.5 it first said fail to boot 2 and thn after i flashed the sbf file it went to boot 4 do u know how i can fix this
Robert5686 said:
the android version ? i was running on 2.3.5 it first said fail to boot 2 and thn after i flashed the sbf file it went to boot 4 do u know how i can fix this
Click to expand...
Click to collapse
You can't flash custom ROMs with a locked bootloader
Sent from my MB855 using xda app-developers app
Yeah i didnt know that but idk y does the bootloader have to be unlocked cuz i flashed the beats audio one and didnt do this
What sbf did you flash?
Sent from my MB855 using xda app-developers app
mof9336 said:
What sbf did you flash?
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Also having the same issue, I just got root, and I tried to install Jellybean from Jokersax with my battery at 5% which was dumb, but anyways now I get failed to boot 4, I can get it into fastboot protocol support, or rsd mode, and that's it, I've tried to flash some stock files, but no good, I also have a locked bootloader & am on 2.3.5
i flashed the one from qbking77 video i only flashed the one and my batery was drained cuz it wasnt full but the proccess said succes but it went to fail to boot 4 and now it says battery to low to flash but i can get a new battery real quick i jux need to know wat sbf file to flash do u know any that i can flash and would work like i said its the only phone i have and im not available for an upgrade till later and i need my phone
Failed to boot 4 Starting RSD Mode
The Story:
I started having issues with the phone becoming slower and slower and crash prone so i figured this would be a good time to flash an alternate rom. I have had root for some time and i unlocked the boot loader probably about two weeks ago. I had tried a few roms by Th3Bill and i kept having issues so i thought id try to re-lock the boot loader as i couldn't flash any of his roms even with is recovery in place to see if unlocking it again would solve my issue. Also i was running 2.3.4 NOT 2.3.5 so it wasn't due to that.
I just followed the steps outlined here from Link:
Relocking without Full SBF flash
Factory reset phone Menu/Settings/Privacy/Factory Data Reset DO NOT SKIP THIS STEP
Reboot phone into fastboot mode: VOL down/Power. Use VOL down to scroll though options til you see "fastboot" then VOL up to enable. and connect phone to computer
Open command prompt in the moto-fastboot folder and type the following using the <enter> key after each command:
moto-fastboot devices
moto-fastboot erase recovery
moto-fastboot flash recovery stock_recovery.smg
moto-fastboot reboot
Disconnect phone from computer
Start RSD Lite on your computer
Reboot phone into RSD mode: VOL down/Power. Use VOL down to scroll though options til you see "RSD" then VOL up to enable.
Connect phone to computer.
Flash nopudding4u.sbf.
Close RSD Lite and disconnect phone.
Reboot phone
Once i completed the Flash nopuding4u.sbf step it failed giving the status: "Failed flashing process. Failed Flashing process. Phone[0000]: THe "Secure_Motorola_Flash" Interface could not be found. The super-file is secure and for re-flash; the phone needs a super-file that is not secureand not for reflash. (0x7066);Phone connec"
It is not just booting to the first Motorola Dual Core Technology splash screen and showing:
Failed to boot 4
Starting RSD Mode
I've been looking for a solution to the issue for about 30 minutes and have found nothing helpful.
Nopudding4u.sbf relocks your phone, however I would recommend using the 198_7.sbf file instead. U can still unlock with pudding.sbf but you will be able to get back running.. after u flash the stock sbf u will probably need to go into recovery and do a factory reset.
Sent from my MB855 using xda app-developers app
Did you fix,
Tempest_Inc said:
The Story:
I started having issues with the phone becoming slower and slower and crash prone so i figured this would be a good time to flash an alternate rom. I have had root for some time and i unlocked the boot loader probably about two weeks ago. I had tried a few roms by Th3Bill and i kept having issues so i thought id try to re-lock the boot loader as i couldn't flash any of his roms even with is recovery in place to see if unlocking it again would solve my issue. Also i was running 2.3.4 NOT 2.3.5 so it wasn't due to that.
I just followed the steps outlined here from Link:
Relocking without Full SBF flash
Factory reset phone Menu/Settings/Privacy/Factory Data Reset DO NOT SKIP THIS STEP
Reboot phone into fastboot mode: VOL down/Power. Use VOL down to scroll though options til you see "fastboot" then VOL up to enable. and connect phone to computer
Open command prompt in the moto-fastboot folder and type the following using the <enter> key after each command:
moto-fastboot devices
moto-fastboot erase recovery
moto-fastboot flash recovery stock_recovery.smg
moto-fastboot reboot
Disconnect phone from computer
Start RSD Lite on your computer
Reboot phone into RSD mode: VOL down/Power. Use VOL down to scroll though options til you see "RSD" then VOL up to enable.
Connect phone to computer.
Flash nopudding4u.sbf.
Close RSD Lite and disconnect phone.
Reboot phone
Once i completed the Flash nopuding4u.sbf step it failed giving the status: "Failed flashing process. Failed Flashing process. Phone[0000]: THe "Secure_Motorola_Flash" Interface could not be found. The super-file is secure and for re-flash; the phone needs a super-file that is not secureand not for reflash. (0x7066);Phone connec"
It is not just booting to the first Motorola Dual Core Technology splash screen and showing:
Failed to boot 4
Starting RSD Mode
I've been looking for a solution to the issue for about 30 minutes and have found nothing helpful.
Click to expand...
Click to collapse
Hello, did you fix your phone. i am in the same issue now.. please guide me or help me to fix the phone.I have been trying for 3 days,, thanks.
Tried to flash MIUI without unlocking the bootloader
keljoe2804 said:
Also having the same issue, I just got root, and I tried to install Jellybean from Jokersax with my battery at 5% which was dumb, but anyways now I get failed to boot 4, I can get it into fastboot protocol support, or rsd mode, and that's it, I've tried to flash some stock files, but no good, I also have a locked bootloader & am on 2.3.5
Click to expand...
Click to collapse
It is was initially stuck on failed to boot 2 and Starting RSD mode. Then I used RSD lite to flash the stock sbf, and my computer went to sleep in the middle of the flash and failed. Now it is stuck on Failed to boot 4, Starting RSD mode, Battery is too low to flash.
I am not in the US right now, so cannot take it to the Sprint store. PLEASE HELP!!!
OK, I will start off by saying I have (nearly) completely screwed myself.
I have a P769 (TMO; does this mean BK?).
I followed this (http://forum.xda-developers.com/showthread.php?p=38677123http://forum.xda-developers.com/showthread.php?p=38677123) to root the device and successfully made it through (using V20D KDZ).
Then then tried to flash this ROM (http://forum.xda-developers.com/showthread.php?t=2335984). Unforunately, I did not have an unlocked bootloader and now I am receiving a Security Error at boot. Even more unfortunate is that I did NOT do a backup so I am truly in a bad place now.
I tried to run through the first step of rooting but the software will not detect the phone as being connected and tells me to connect the USB cable. I have installed the drivers that are in that post but admittedly I may have updated them after rooting.
At this point I only have access to fastboot so I am trying that method but I cannot find any system.img files to be able to flash the system partition.
What do I do now? Can anyone help me? I have exhausted every Google search and XDA search. I may be missing something but I feel I am in a very bad place now and need to get this phone back up and running.
thchipmunk said:
OK, I will start off by saying I have (nearly) completely screwed myself.
I have a P769 (TMO; does this mean BK?).
I followed this (http://forum.xda-developers.com/showthread.php?p=38677123http://forum.xda-developers.com/showthread.php?p=38677123) to root the device and successfully made it through (using V20D KDZ).
Then then tried to flash this ROM (http://forum.xda-developers.com/showthread.php?t=2335984). Unforunately, I did not have an unlocked bootloader and now I am receiving a Security Error at boot. Even more unfortunate is that I did NOT do a backup so I am truly in a bad place now.
I tried to run through the first step of rooting but the software will not detect the phone as being connected and tells me to connect the USB cable. I have installed the drivers that are in that post but admittedly I may have updated them after rooting.
At this point I only have access to fastboot so I am trying that method but I cannot find any system.img files to be able to flash the system partition.
What do I do now? Can anyone help me? I have exhausted every Google search and XDA search. I may be missing something but I feel I am in a very bad place now and need to get this phone back up and running.
Click to expand...
Click to collapse
A system.img is to big to flash in fastboot. Follow Lelus directions http://forum.xda-developers.com/showpost.php?p=43021469&postcount=5
Sent from my LGMS769 using xda app-developers app
kuma82 said:
A system.img is to big to flash in fastboot. Follow Lelus directions http://forum.xda-developers.com/showpost.php?p=43021469&postcount=5
Sent from my LGMS769 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the suggestion. I just tried it and I get an error"
Updating is not possible any longer due to a fatal error while the LG Mobile Phone Software Update.
Click to expand...
Click to collapse
I am still getting the security error even though other threads said I should be able to get rid of it.
Is it possible to create a custom update.zip to flash with?
When I do the recovery it returns my phone as a P769BKGO if that helps with anything.
thchipmunk said:
Thanks for the suggestion. I just tried it and I get an error"
I am still getting the security error even though other threads said I should be able to get rid of it.
Is it possible to create a custom update.zip to flash with?
Click to expand...
Click to collapse
What os are you running also what kdz are you trying to flash ?
Lelus said:
What os are you running also what kdz are you trying to flash ?
Click to expand...
Click to collapse
I am running 32-bit Windows 7 Professional Service Pack 1. I tried flashing V20D_00.kdz (using the offline flash) as well as the V10G_00.kdz and V10E_00.kdz.
Using the offline flash method I constantly get the error of cannot connect to phone no matter how many times I restart the PC or phone and unplug USB.
thchipmunk said:
I am running 32-bit Windows 7 Professional Service Pack 1. I tried flashing V20D_00.kdz (using the offline flash) as well as the V10G_00.kdz and V10E_00.kdz.
Using the offline flash method I constantly get the error of cannot connect to phone no matter how many times I restart the PC or phone and unplug USB.
Click to expand...
Click to collapse
you already flashed ics xloader and uboot with fastboot and kdz files names are all CAPS right ?
Lelus said:
you already flashed ics xloader and uboot with fastboot and kdz files names are all CAPS right ?
Click to expand...
Click to collapse
All caps, correct.
Should I do fastboot and then run the offline method?
I did do the fastboot then tried the recovery phone option from the support tool.
I did find a recovery I made that included (for some reason) only the recovery and boot.
thchipmunk said:
All caps, correct.
Should I do fastboot and then run the offline method?
I did do the fastboot then tried the recovery phone option from the support tool.
I did find a recovery I made that included (for some reason) only the recovery and boot.
Click to expand...
Click to collapse
Don't worry about stock recovery it's useless, just flash ics xloader and uboot http://forum.xda-developers.com/showthread.php?t=2292828 option #5
, put your phone into s/w upgrade mode and try offline method
Lelus said:
Don't worry about stock recovery it's useless, just flash ics xloader and uboot http://forum.xda-developers.com/showthread.php?t=2292828 option #5
, put your phone into s/w upgrade mode and try offline method
Click to expand...
Click to collapse
I'll reboot and then try that again. I'll check back afterwards.
Should I do anything extra like start the offline flash from scratch as far as drivers? I'm not even sure where to begin in regards to what drivers/files to remove.
Thank you! Thank you! Thank you!
Now I just need to figure out the screen calibration.
Also, what can I do with this now? Do I need to unlock the bootloader to load custom ROMs without getting a security error?
Sorry for my lack of knowledge. My last phone was a Bionic and that was the easiest phone to root and add a ROM to.
unfortunately i find myself in this situation
gettin security error after what i assume was me trying to flash on a locked bootloader
anyway, i can't figure this out, the whole flashing fastboot and what not
i read through the readme and installed the drivers for the "other/unknown" device that pops up
this is what i try to do next
open up start.bat
enter 5 and hit enter
remove battery from phone (as instructed) and hit any key
boot phone into sw upgrade (holding vol up and plugging in usb cable)
device seems to be picked up and i see the "wait 5 seconds" (german?) and the image is revered horizontally on my phone
now after 4/5 seconds it says "waiting for device", which then i put the battery in
but NOTHING happens after this, it hangs at "waiting for device"
can someone please tell me what i'm doing wrong?
otherwise i think i'm left with a totally effed lg optimus l9
rotatorkuf said:
unfortunately i find myself in this situation
gettin security error after what i assume was me trying to flash on a locked bootloader
anyway, i can't figure this out, the whole flashing fastboot and what not
i read through the readme and installed the drivers for the "other/unknown" device that pops up
this is what i try to do next
open up start.bat
enter 5 and hit enter
remove battery from phone (as instructed) and hit any key
boot phone into sw upgrade (holding vol up and plugging in usb cable)
device seems to be picked up and i see the "wait 5 seconds" (german?) and the image is revered horizontally on my phone
now after 4/5 seconds it says "waiting for device", which then i put the battery in
but NOTHING happens after this, it hangs at "waiting for device"
can someone please tell me what i'm doing wrong?
otherwise i think i'm left with a totally effed lg optimus l9
Click to expand...
Click to collapse
Odds are, you are doing nothing wrong. Check your android version, if you are on 4.2+ (JellyBean) you can't unlock your bootloader quite yet. Here is the thread you should keep track of at the moment http://forum.xda-developers.com/showthread.php?t=2277639&page=152
Insert battery more quickly
rotatorkuf said:
unfortunately i find myself in this situation
gettin security error after what i assume was me trying to flash on a locked bootloader
anyway, i can't figure this out, the whole flashing fastboot and what not
i read through the readme and installed the drivers for the "other/unknown" device that pops up
this is what i try to do next
open up start.bat
enter 5 and hit enter
remove battery from phone (as instructed) and hit any key
boot phone into sw upgrade (holding vol up and plugging in usb cable)
device seems to be picked up and i see the "wait 5 seconds" (german?) and the image is revered horizontally on my phone
now after 4/5 seconds it says "waiting for device", which then i put the battery in
but NOTHING happens after this, it hangs at "waiting for device"
can someone please tell me what i'm doing wrong?
otherwise i think i'm left with a totally effed lg optimus l9
Click to expand...
Click to collapse
I've found that the process completes if you put the battery back in , right after you reconnect the USB.
mven45 said:
I've found that the process completes if you put the battery back in , right after you reconnect the USB.
Click to expand...
Click to collapse
hi iam in the same boat have you figured any thing out please help i also may have found away if you by chance had your lg pc suit installed and setup prior to this mishap
maso321 said:
hi iam in the same boat have you figured any thing out please help i also may have found away if you by chance had your lg pc suit installed and setup prior to this mishap
Click to expand...
Click to collapse
If you're running a Windows 8 OS, that's the reason it's not working.
Sent from my LGMS769 using XDA Premium 4 mobile app
rotatorkuf said:
unfortunately i find myself in this situation
gettin security error after what i assume was me trying to flash on a locked bootloader
anyway, i can't figure this out, the whole flashing fastboot and what not
i read through the readme and installed the drivers for the "other/unknown" device that pops up
this is what i try to do next
open up start.bat
enter 5 and hit enter
remove battery from phone (as instructed) and hit any key
boot phone into sw upgrade (holding vol up and plugging in usb cable)
device seems to be picked up and i see the "wait 5 seconds" (german?) and the image is revered horizontally on my phone
now after 4/5 seconds it says "waiting for device", which then i put the battery in
but NOTHING happens after this, it hangs at "waiting for device"
can someone please tell me what i'm doing wrong?
otherwise i think i'm left with a totally effed lg optimus l9
Click to expand...
Click to collapse
Take out battery and USB cable from phone
Enter #5
Plug in USB when it tells you
Wait 5 seconds or less then place battery in
once in fastboot mode remove battery for a couple of seconds then replace
take out the usb press the vol + then reconnect
S/W upgrade mode achieved.
Flash accordingly. . .
Nathan.7118391 said:
Take out battery and USB cable from phone
Enter #5
Plug in USB when it tells you
Wait 5 seconds or less then place battery in
once in fastboot mode remove battery for a couple of seconds then replace
take out the usb press the vol + then reconnect
S/W upgrade mode achieved.
Flash accordingly. . .
Click to expand...
Click to collapse
Hey Nathan did you ever get your device operating again?
Sent from my LGMS769 using XDA Premium 4 mobile app
kuma82 said:
Hey Nathan did you ever get your device operating again?
Sent from my LGMS769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope! I had to do a warranty exchange. I was copying the system image then I thought it finished so I unplugged the phone. May I tried my best to get the phone back but I could only get into fastboot mode, but hey lesson learned. Though I did see this tool that someone here was trying to use to flash bin and fls files in 3 minutes! But it only works for p790 Optimus black. Which sucks because I could get my phone into an inverted S/W upgrade mode (yeah I know it's on the real one) but it only lasted for about 3 minutes then shut down so doing the offline fix just took too long. I would get to about 23% install and the phone would just turn off. . so close! LOL
EDIT: YEAH got the phone to finally work! No exchange now, take that LG! Just kept trying there offline fix
Nathan.7118391 said:
Nope! I had to do a warranty exchange. I was copying the system image then I thought it finished so I unplugged the phone. May I tried my best to get the phone back but I could only get into fastboot mode, but hey lesson learned. Though I did see this tool that someone here was trying to use to flash bin and fls files in 3 minutes! But it only works for p790 Optimus black. Which sucks because I could get my phone into an inverted S/W upgrade mode (yeah I know it's on the real one) but it only lasted for about 3 minutes then shut down so doing the offline fix just took too long. I would get to about 23% install and the phone would just turn off. . so close! LOL
EDIT: YEAH got the phone to finally work! No exchange now, take that LG! Just kept trying there offline fix
Click to expand...
Click to collapse
I'm trying to restore my P769 to stock (Stuck LG logo), and getting nowhere.
How did you get the flash to work? What error did you get when the phone would turn off? How did you get the inverted S/W mode?
My phone only got to 17-20% before getting an connection error using the offline booth method, this was with both JB and ICS u-boot/boot/recovery .imgs from the P769 ROMs--should I try the steps in unlocking the bootloader to at least get to a bootable state?
Nathan.7118391 said:
Nope! I had to do a warranty exchange. I was copying the system image then I thought it finished so I unplugged the phone. May I tried my best to get the phone back but I could only get into fastboot mode, but hey lesson learned. Though I did see this tool that someone here was trying to use to flash bin and fls files in 3 minutes! But it only works for p790 Optimus black. Which sucks because I could get my phone into an inverted S/W upgrade mode (yeah I know it's on the real one) but it only lasted for about 3 minutes then shut down so doing the offline fix just took too long. I would get to about 23% install and the phone would just turn off. . so close! LOL
EDIT: YEAH got the phone to finally work! No exchange now, take that LG! Just kept trying there offline fix
Click to expand...
Click to collapse
How did you solve this? I am at the same steps, I get into mirrored software mode and then I attempt the offline fix. I have even started the offline fix early to save time. And yet it will only stay on for 2 and a half minutes or so and then shuts off. The farthest i have been able to get it to go is 41%. I have tried fastboot mode to try and send boot.img and it just says that it cannot find the boot partition. So it looks like my only option is the offline fix but it doesn't have enough time to complete. I have tried about 20 or so times how many tries did it take for you? Did you do anything special to get it to finish? any advice on how to get it to finish? Spent about 6 hrs last night trying to get this phone back up and running and this is where i am stuck. Its lame cuz i woke up to the phone like this it was fine when i went to bed. And was for months.
How to fix partion problem !!!
After countlss hours of messing with the LG P769 This is how i got into S/W mode to work !:laugh:
ASSUMING you know how to install fastboot drivers there are instructions on the forum ...so follow those guide note fastboot drivers work best on windows 7 windows 8 was giving me hard time ...
1.install fastboot drivers
2.run lelus script at the same time hold vol+ button once the script shows the OMAP device close the script and immediately put the battery back in .The LG phone will boot into S/W mode !
Make sure you write down your imei or serial number AND make sure battery is fully charged . then
Now simply use the LG software tool or the KDZ offline flasher look around the forum for how to guides
Thats it
tawhid111 said:
How to fix partion problem !!!
After countlss hours of messing with the LG P769 This is how i got into S/W mode to work !:laugh:
ASSUMING you know how to install fastboot drivers there are instructions on the forum ...so follow those guide note fastboot drivers work best on windows 7 windows 8 was giving me hard time ...
1.install fastboot drivers
2.run lelus script to get into fastboot at the same time hold vol+ button once the script shows the OMAP device close the script and immediately put the battery back in .The LG phone will boot into S/W mode !
Make sure you write down your imei or serial number AND make sure battery is fully charged . then
Now simply use the LG software tool or the KDZ offline flasher look around the forum for how to guides
Thats it
Click to expand...
Click to collapse
So you solve it! :good:
:/
tawhid111 said:
How to fix partion problem !!!
After countlss hours of messing with the LG P769 This is how i got into S/W mode to work !:laugh:
ASSUMING you know how to install fastboot drivers there are instructions on the forum ...so follow those guide note fastboot drivers work best on windows 7 windows 8 was giving me hard time ...
1.install fastboot drivers
2.run lelus script at the same time hold vol+ button once the script shows the OMAP device close the script and immediately put the battery back in .The LG phone will boot into S/W mode !
Make sure you write down your imei or serial number AND make sure battery is fully charged . then
Now simply use the LG software tool or the KDZ offline flasher look around the forum for how to guides
Thats it
Click to expand...
Click to collapse
Still unable to do it, when I plug the cable holding vol+ it just reboot normally :/
foreverman said:
Still unable to do it, when I plug the cable holding vol+ it just reboot normally :/
Click to expand...
Click to collapse
Then try enter in lelus fastboot mode, ad then flash x-loader, uloader, boot.img and recovery.img from stock rom for your device type model. Then repeat steps 1 and 2
Where can I find the lelus script?
Sent from my Note II
Sorry for reviving such an old thread, but oh well...
Your procedure doesn't seem to work with my device. Just to make sure we are using the same driver packages, can you post a link to the fastboot driver you have successfully used?
My L9 is always showing this "partition doesn't exist" error message, no matter what I try. Lelus's script seems to do the job and the phone is detected as a fastboot device, and can even be detected in LG Flash Tool (using a 910K cable), but flashing will stop after a little over 2 minutes, because the phone disconnects. During all of my attempts, the screen stays black.
Any hint?
ciccillover said:
Sorry for reviving such an old thread, but oh well...
Your procedure doesn't seem to work with my device. Just to make sure we are using the same driver packages, can you post a link to the fastboot driver you have successfully used?
My L9 is always showing this "partition doesn't exist" error message, no matter what I try. Lelus's script seems to do the job and the phone is detected as a fastboot device, and can even be detected in LG Flash Tool (using a 910K cable), but flashing will stop after a little over 2 minutes, because the phone disconnects. During all of my attempts, the screen stays black.
Any hint?
Click to expand...
Click to collapse
Then you need a Technician with a Octopus Box to repair your partition table...
ciccillover said:
Sorry for reviving such an old thread, but oh well...
Your procedure doesn't seem to work with my device. Just to make sure we are using the same driver packages, can you post a link to the fastboot driver you have successfully used?
My L9 is always showing this "partition doesn't exist" error message, no matter what I try. Lelus's script seems to do the job and the phone is detected as a fastboot device, and can even be detected in LG Flash Tool (using a 910K cable), but flashing will stop after a little over 2 minutes, because the phone disconnects. During all of my attempts, the screen stays black.
Any hint?
Click to expand...
Click to collapse
Can you boot into recovery? We now have a custom recovery for locked bootloaders (and CM roms). If you can get into recovery, I would try some adb commands to mount the partitions.
No, no recovery. Just to make sure that I'm not doing it wrong, what is the key combination to boot to recovery?
I have also tried:
Code:
fastboot boot some_recovery_image.img
It says ok, but the phone just hangs at the black screen and becomes undetectable as a fastboot device, until I pull the battery. So, unless the some_recovery_image.img is unsuitable for my P760 (which may be!), there is something seriously wrong I think.
Or maybe I can try the same command with the custom recovery for bootloader locked phones... Where can I find it?
ciccillover said:
No, no recovery. Just to make sure that I'm not doing it wrong, what is the key combination to boot to recovery?
I have also tried:
Code:
fastboot boot some_recovery_image.img
It says ok, but the phone just hangs at the black screen and becomes undetectable as a fastboot device, until I pull the battery. So, unless the some_recovery_image.img is unsuitable for my P760 (which may be!), there is something seriously wrong I think.
Or maybe I can try the same command with the custom recovery for bootloader locked phones... Where can I find it?
Click to expand...
Click to collapse
Your EMMC partition is wiped or fried... you really need a JTAG service or a Box like octopus because your L9 is Hard-bricked...
Thanks for your opinion. Yet, I still want to hear from others.
I'm running into more and more problems with the L9 as their me grows.
-Fastboot doesn't work under Windows 8.1 and 10, but under the now obsolete(for me) Windows 7, unlike my other devices, which are fine with Win 10.
-ADB seems to work, but requiring the device to be still able to boot.
-I always boot to recovery from within Android as long as the L9 ain't bricked. After a failed rom install, during which the sd card failed(could no longer write or be formatted afterwards, the last time stamps of files and folders were set during the failed install) I discovered a problem with TWRP(Artas182x's and Edwin's), which may have been present since a long time: Trying to invoke TWRP via keypress will brick the device!
So, if my P760 no longer boots, there's only download mode available, sort of the final line of defense.
-There's sort of a trick if even download mode fails: After a failed attempt unplug phone, force switch-off, if the phone is in brick state. Then switch on, force switch-off again, and only then attempt download mode again. And have patience while holding down the vol button, it might take up to 20 seconds for the phone to switch itself on into download mode. (A single forced powerdown will cause Fastboot NOT to work the next time)
But I'm absolutely clueless about the recovery issue, for now TWRP is semi-working, can only be accessed via Android, as long as the phone is fully working.
W/o Fastboot, I now have flashed stock rom several times and rooted it with Kingo rooter just to be able to run Flashify to install TWRP. If Flashify is the culprit for the TWRP issues, I could need a recommendation for a better working app.
ciccillover said:
Thanks for your opinion. Yet, I still want to hear from others.
Click to expand...
Click to collapse
Tried OMAP flasher ? It needs memory configuration file in order to work with our device
No, I didn't. I have sold the phone for spares.
Inviato dal mio LG-D855 utilizzando Tapatalk
I never needed the OMAP drivers and tools. As they are ancient, they will probably make even more problems with newer Windows versions.
I could by no means invoke Fastboot on this device with Windows 8.1 and 10, Seven worked. So you had to go for Download Mode instead to recover to stock rom, then root with the Kingo tool, then install TWRP via Rashr or Flashify, the most time consuming way to recover from the frequent bricks.
And the LG Flash Tool 2014 always needed several attempts to get the job done. The latest official recovery tool from LG works in D/L Mode, but will always download the rom image anew.
i have updated my phone moto e to android L OTA manually and since then it worked really well but only few bugs were there .
later again i saw a 13mb file of bugs fix manually update which i have downloaded and installed in my phone which got bricked and this occurred :
My phone shows only one Motorola M logo image and while connecting to charger it shows only this image
Help me out to work my mobile as before it use to be !!
can any one help regarding this problem.
Srinivas0009 said:
i have updated my phone moto e to android L OTA manually and since then it worked really well but only few bugs were there .
later again i saw a 13mb file of bugs fix manually update which i have downloaded and installed in my phone which got bricked and this occurred :
My phone shows only one Motorola M logo image and while connecting to charger it shows only this image
Help me out to work my mobile as before it use to be !!
can any one help regarding this problem.
Click to expand...
Click to collapse
its because u have charger connected..take it out and boot up..
-Adarsh- said:
its because u have charger connected..take it out and boot up..
Click to expand...
Click to collapse
sorry but i couldnt start my phone !!! it shows me motorola M logo and doesnt go forward from it
Srinivas0009 said:
sorry but i couldnt start my phone !!! it shows me motorola M logo and doesnt go forward from it
Click to expand...
Click to collapse
Hard reset
Sent from my XT1022 using XDA Premium mobile app
Soft Brick
That's only a soft brick, the good thing is it turns on, if it was a hard brick you would have to do a blankflash of the bootloader, which as the device has only just been released it won't be available. Just a few things, because this is only a soft brick you may be able to sort it out. Be careful, when you're doing an OTA update be sure to have the stock recovery because if you have a custom recovery such as TWRP or CWM it won't install the update that's why when you have an OTA update it's best to flash the stock recovery so that it will be able to install Motorola's OTA update. If you haven't got the stock recovery img flashed on your device then you will need to. Download the stock recovery img, you can do it on one of the Moto Tool's that's floating around. Then enter your bootloader, fastboot mode by powering off the device and holding POWER + Volume down buttons together but don't let go until you see your bootloader. Make sure you have ADB and Fastboot drivers installed on your PC, download the recovery img for your device (stock one) save it to your desktop and then do the following. Locate your ADB and Fastboot driver folder and then open a command prompt window in your folder and type to following, without the apostrophes, 'fastboot devices' and if you see your device you're connected ready to flash. After that, type 'fastboot flash recovery recovery.img' and it will flash the stock recovery partition for your device. When you have done that you can boot into recovery, scroll with your volume buttons until you see 'recovery' click on it and you will see 'Wipe Factory' click that and it will revert your phone back to stock! Hopefully then your problem should be fixed, if not then you will need to wait for the Factory Images, or I think you are able to download them off Motorola's website, if not then you'll have to wait! Just remember in future to always make a backup of your current firmware, then if something like this does go wrong you always have something to fall back on if your device does get bricked!
Hope this helped you