Related
I flashed to GB from stock, i went to try a fission rom, wiped data and flashed and now im stuck on M logo. Ive seen prior posts on this problem and followed instruction on loading the sbf file thru rsd lite. So i did that, it executes the whole flash process and reboots my phone and that execution goes to 100% and it tells me to power my phone up manually. Heres the problem when it rebooted my phone it got froze at logo again and i could do nothing but pull battery. So is there any thoughts or advice as to what maybe im doing wrong or another way to get my phone up and running? THANX
Also i cant boot into clockworkmod only android system recovery...is this maybe why its not working?
go into recovery and wipe data/factory reset. Then reboot.
jgraham4598 said:
go into recovery and wipe data/factory reset. Then reboot.
Click to expand...
Click to collapse
I did try that it was one of the first methods tried it didnt help...Thanks for the reply tho
Scitzo382 said:
I did try that it was one of the first methods tried it didnt help...Thanks for the reply tho
Click to expand...
Click to collapse
What version of bootloader are you on? What version of SBF are you using?
bigshotrob22 said:
What version of bootloader are you on? What version of SBF are you using?
Click to expand...
Click to collapse
Bootloader 30.04 and sbf SHADO_X6_ 2.3.34
Scitzo382 said:
Bootloader 30.04 and sbf SHADO_X6_ 2.3.34
Click to expand...
Click to collapse
I believe that's the system only. You need the full sbf file
Sent from my DROIDX using XDA App
I replied to your post in the other post... anyway, yes you need to try wiping (multiple times) and then if that doesn't work, SBF, you can find SBF downloads on site in my sig.
bigshotrob22 said:
I believe that's the system only. You need the full sbf file
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
o If you have already flashed 2.3.32, and/or have 30.04 bootloader: 2.3.34 SYSTEM ONLY SBF:
• DIRECT LINK TO SBF: http://www.megaupload.com/?d=OXK9Q1ZG
i was going by that in SystmeAdmin-X's noob to droid x post sice i had 30.04 i used system only....will it be safe to do the full 2.3.32
snwagner said:
I replied to your post in the other post... anyway, yes you need to try wiping (multiple times) and then if that doesn't work, SBF, you can find SBF downloads on site in my sig.
Click to expand...
Click to collapse
Yes im new to forums this my first posts i realized after the fact that i should started a new thread so did....thanx for the replies i have tried several wipes and tried sbf with rsd lite. i used 2.3.34 since i have 30.04 boot loader and i still got stuck at M logo...should i do full file 2.3.32 with 30.04 bootloader?
Scitzo382 said:
Yes im new to forums this my first posts i realized after the fact that i should started a new thread so did....thanx for the replies i have tried several wipes and tried sbf with rsd lite. i used 2.3.34 since i have 30.04 boot loader and i still got stuck at M logo...should i do full file 2.3.32 with 30.04 bootloader?
Click to expand...
Click to collapse
You need to full sbf in order for your phone to work. The system only wil not work if you came from GB.
Sent from my DROIDX using XDA App
bigshotrob22 said:
You need to full sbf in order for your phone to work. The system only wil not work if you came from GB.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
OK thank you i will try that right now and post results
Thanks a million times over to Bigshotrob22 and snwagner, The full file worked like a charm u guys are awesome thanks for the support i got my baby back
Scitzo382 said:
Thanks a million times over to Bigshotrob22 and snwagner, The full file worked like a charm u guys are awesome thanks for the support i got my baby back
Click to expand...
Click to collapse
No problem...For future reference if your on froyo and you do the system only sbf it will work. The reason why you had to do the full sbf is because GB changes the stock recovery and other files I can't remember off the top of my head.
Sent from my DROIDX using XDA App
As the title says, After I unlocked the bootloader, and flashed a 2.3.4 rom, My Atrix sometimes will go up to the blur phase of the boot and then it will restart, but most of the time will just do a boot loop on the Red Moto Logo at boot, I can go into fastboot and recovery no problem...
Thanks on any help...
same thing
i get the same thing every now and then but i can get fastboot and recovery so im good i guess.
Did you wipe before you installed your ROM?
Do a fastboot -w then reinstall your ROM.
also do a factory reset and make sure your on the newest recovery
quicklyspent said:
Did you wipe before you installed your ROM?
Do a fastboot -w then reinstall your ROM.
Click to expand...
Click to collapse
Did the fastboot -w and reinstalled the ROM and it is doing the bootloop the same, first boot goes up to the blur phase and reboots, and afterwards just does the boot loop up to the motorola dual core red logo.
TechnoNeto said:
also do a factory reset and make sure your on the newest recovery
Click to expand...
Click to collapse
I have the latest recovery, thanks...
Flash back to stock and follow my guide
Sent from my MB860 using XDA Premium App
TechnoNeto said:
Flash back to stock and follow my guide
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Where can I find your guide, and should I SBF 1.83 or what..
It's in general under video how to go... Sorry I'm on my phone
Sent from my MB860 using XDA Premium App
http://forum.xda-developers.com/showthread.php?t=1179506
Sent from my MB860 using XDA Premium App
Did you make sure to use tenfar's CWM instead of ROM Manager's? My 2.3.4 install also bootlooped, and that ended up being the issue.
Sent from my ATRIX running CherryBlur 1.3.
I'm still having issues, I have the latest Recovery, and I have tried to flash through Recovery and still get the boot loops...
Just Flashed via RSD the SBF 1.2.6 and still have the reboots, I think that my phone it's bricked, I can go into RSD, Fastboot, Recovery, everywere, I can flash anything, but when it boots, it does a bootloop everytime... I
If someone has an answer please help...
poorg said:
Just Flashed via RSD the SBF 1.2.6 and still have the reboots, I think that my phone it's bricked, I can go into RSD, Fastboot, Recovery, everywere, I can flash anything, but when it boots, it does a bootloop everytime... I
If someone has an answer please help...
Click to expand...
Click to collapse
Take out the battery for 30 sec and then put it back press vol up while you turn on.... can you please post what it show up in your screen after this?
Sent from my MB860 using XDA App
mramirezusa said:
Take out the battery for 30 sec and then put it back press vol up while you turn on.... can you please post what it show up in your screen after this?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Starting RSD protocol support....
poorg said:
Starting RSD protocol support....
Click to expand...
Click to collapse
Ok I will post a guide and follow up give 1 minute
Sent from my MB860 using XDA App
mramirezusa said:
Ok I will post a guide and follow up give 1 minute
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Thanks for the help, really appreciate this...
poorg said:
Thanks for the help, really appreciate this...
Click to expand...
Click to collapse
Ok maybe is time for clean starp up, DEEP CLEAN, I did this script for a friend and it help:
Need Windows PC and UNLOCKED BOOTLOADER (when I said unlocked bootloader need to be that everytime you boot you saw "unlocked" tag at the left top corner)
1. Download and extract/unzip the following file in a new folder (example C:\atrix):
http://www.filesonic.com/file/15073...signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
2. You will end after extracted/unzip the file with something like this:
1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf
3. Download this file "CLEAN_2.3.4_ATT.zip" and extract/unzip to the same location (example C:\atrix)
http://forum.xda-developers.com/attachment.php?attachmentid=673330&d=1312203457
5. Run the script "clean" and follow exactly all the instrucctions!
6. This will install a Pristine Official ATT GB 2.3.4/4.5.91
Done!
Hope it help
mramirezusa said:
Ok maybe is time for clean starp up, DEEP CLEAN, I did this script for a friend and it help:
Need Windows PC and UNLOCKED BOOTLOADER (when I said unlocked bootloader need to be that everytime you boot you saw "unlocked" tag at the left top corner)
1. Download and extract/unzip the following file in a new folder (example C:\atrix):
http://www.filesonic.com/file/15073...signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
2. You will end after extracted/unzip the file with something like this:
1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf
3. Download this file "CLEAN_2.3.4_ATT.zip" and extract/unzip to the same location (example C:\atrix)
http://forum.xda-developers.com/attachment.php?attachmentid=673330&d=1312203457
5. Run the script "clean" and follow exactly all the instrucctions!
6. This will install a Pristine Official ATT GB 2.3.4/4.5.91
Done!
Hope it help
Click to expand...
Click to collapse
Ok, but mine does not say unlocked right now, I did Unlock the bootloader but after I flashed the 1.2.6 SBF it does not say it!!!!
I noticed you posted that you actually have unlocked bootloader just make sure that when you turn on the phone it said in the left top corner "unlocked", if it is not that case just follow intructions on this post:
http://forum.xda-developers.com/showpost.php?p=15930466&postcount=1
download the script and select option 1 from the main menu and then option 3 and complete all the steps
so you can re unlocked the bootloader
then follow the instrucionts that I posted before here
mramirezusa Thank You.... As you stated, everything went smoothly and my phone it's perfect again, something I noticed, when it boots, it's does not say unlocked anymore shoul'd I do the procedure with the the script that you sent posted above...
I believe this is what everyone is looking for.
http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard
Sent from my Xoom using xda premium
It says it's for MZ602. Will this still work with our current XOOMs.
Furthermore, will it work with a 3G XOOM that has yet to be upgraded?
It says Verizon. It is the same file we updated to. Ours was the mz600, but after the upgrade it became mz602. You know of any other Verizon xoom with 4g? They are going to sell the same xoom, just has the lte card in it this time.
Sent from my Xoom using xda premium
Well, I'm having trouble with it.
I'm using RSDLite and trying to flash the .SBF and it's saying:
"Error validating image files" under status, before I even hit start.
Then afterwards, I get:
"Failed flashing process. Failed flashing process. Unable to retrieve initialization values from INI..."
Thanks... Anybody knows if I flash one of the latinamerican image into a US 4G would brick the Xoom?
I think you have to extract it or unzip it.
Sent from my Xoom using xda premium
hammer4203 said:
I think you have to extract it or unzip it.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Extracted the .SBF from the .GZ file. It's just like.. RSDLite (v5.0) won't read some kind of .ini file. I have all the updated drivers, etc.
Great. After using this, my Xoom won't go past the boot screen.
It won't even boot into recovery. I can still access Fastboot and RSD.
Even after trying different unbrick solutions. Even after flashing back to HRI66.
Can't even get my Xoom to turn off now.
You may need the other cable to flash it in rsd mode. There is a special cable that looks exactly like the normal usb cable. It's wired different.
Sent from my ADR6400L using xda premium
You may need rsd lite on your PC and USB drivers to do it with the stock cable.
Sent from my Xoom using xda premium
hammer4203 said:
You may need rsd lite on your PC and USB drivers to do it with the stock cable.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Yeah.. That's what I'm doing it with. The stock USB cable included with the Xoom and RSDLite v5.4.4 with all the updated drivers.
My Xoom just sits there at the boot screen now, like I said, even after trying to flash back down to HRI66 afterwards to fix it.
I can still boot into Fastboot and RSD mode, but my Xoom stalls and doesn't enter recovery, even after trying another recovery img.
I thought I read something about needing a proper boot.img to go with the SBF file, but I even tried flashing AceXMachine's boot img and nothing.
So you guys haven't gotten this to work or are you just the lucky ones who had problems?
There is a stock version of sbf floating around that has 2 files in it one sbf and I can't remeber what the other one is. This is how they flashed ours for the 4g upgrade. It may be missing something. Can't the sbf be unpacked to the boot, system, recovery imgs? I read something along those linea in one of the dev forums. Not sure about that cable though. That's what worries me. It is suppose to activate something in the xoom so you can flash on rsd mode.
Sent from my ADR6400L using xda premium
dethrok said:
Well, I'm having trouble with it.
I'm using RSDLite and trying to flash the .SBF and it's saying:
"Error validating image files" under status, before I even hit start.
Then afterwards, I get:
"Failed flashing process. Failed flashing process. Unable to retrieve initialization values from INI..."
Click to expand...
Click to collapse
This is the issue I have. I do not have the official Xoom cable my dog ate it. Really it did. Looks like I will make a trip to Verizon and get one if necessary.
hammer4203 said:
There is a stock version of sbf floating around that has 2 files in it one sbf and I can't remeber what the other one is. This is how they flashed ours for the 4g upgrade. It may be missing something. Can't the sbf be unpacked to the boot, system, recovery imgs? I read something along those linea in one of the dev forums. Not sure about that cable though. That's what worries me. It is suppose to activate something in the xoom so you can flash on rsd mode.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Yeah, I think you're talking about this one. I downloaded that (from a mirror, as that link doesn't work) and everything I read said the smaller file (the one you're talking about) wasn't necessary.
And I haven't seen anything about using a special cable to flash your Xoom with RSDLite. Everything I've read just says the stock USB cable with updated drivers, so I have no idea.
zone23 said:
This is the issue I have. I do not have the official Xoom cable my dog ate it. Really it did. Looks like I will make a trip to Verizon and get one if necessary.
Click to expand...
Click to collapse
Find and download RSDLite 5.4.4. That's what fixed it for me.
dethrok said:
Extracted the .SBF from the .GZ file. It's just like.. RSDLite (v5.0) won't read some kind of .ini file. I have all the updated drivers, etc.
Click to expand...
Click to collapse
dethrok, you've got most of it right >extract the .SBF (I've had issues on 64 bit Win 7 machine, unless I've place the file at either the root of C: or else under c:\users\<my username>\ (??-weird??))
> make sure you have the latest drivers
> (this is the gotcha) you need to use RSDLite v5.4.4
>>Note: Yes the HLK75D SBF works and was designed with the original MZ600
Hardware, since the MZ602 is just the MZ600 w/ LTE
This should do it for you, however for good measure, I aways run a short script that unlocks, erases (boot/sys/rec/uda & cache partitions), flashes HR166 back onto the device & then relocks it. I know this is probably a waste of time; it just seems to SBF with less issues.
Here's the text out of the .bat I wrote:
(!!!Please bear in mind this will erase/format your device, so please make sure you have all personal data backed up.!!!)
If your system is already powered up and has USB debugging enabled you can remove the 1st REM statement & just execute the .bat file, otherwise reboot the device by holding down the volume up and power button > release both and then hold down the volume down button until the "fastboot" screen appears.
Copy the below text into notepad and save as a .bat file
REM adb reboot bootloader
fastboot oem unlock
REM Press and hold the volume down button
pause
fastboot erase boot
fastboot erase system
fastboot erase recovery
fastboot -w
pause
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
If you want to use this, you need to d/l the HRI66 build .img files from MotoDEV as well as having the
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
* you can also just REM out the fastboot commands that flash the HR166 image, so the device is completely blank and you can just load the HLK75D sbf via RSDLite, either way works........
** Remember after any OS flash, you should launch “Android recovery Mode” (press & release the down volume button after the red Motorola symbol appears when the device powers on) and reset the device to factory defaults.
Cheers,
Hat
That is the build number for our xoom. Why load the file if it can't be used to flash the xoom? There is something missing as to how it's done. I mean when the xoom came out they leaked an sbf file and it worked. This one just has to be unzipped first. Or does it?
Sent from my Xoom using xda premium
hammer4203 said:
That is the build number for our xoom. Why load the file if it can't be used to flash the xoom? There is something missing as to how it's done. I mean when the xoom came out they leaked an sbf file and it worked. This one just has to be unzipped first. Or does it?
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Now see, someone mentioned the other file included in that old .SBF, but no one ever answered as to what to do with it:
janjan said:
Do we need to flash both of these following?
1: 1.35-everest.reflash.sbf
2: VZW_MZ600_Signed_HRI39_Signed_MDM600BP_C_02.0F.00R_SW.combo.sbf
And what is 1.35-everest.reflash.sbf is for?
thanks
Click to expand...
Click to collapse
Actually, another person in that thread said they flashed the file first, rebooted, then flashed the .SBF. So I'm not sure anymore.
dethrok said:
Yeah, I think you're talking about this one. I downloaded that (from a mirror, as that link doesn't work) and everything I read said the smaller file (the one you're talking about) wasn't necessary.
And I haven't seen anything about using a special cable to flash your Xoom with RSDLite. Everything I've read just says the stock USB cable with updated drivers, so I have no idea.
Find and download RSDLite 5.4.4. That's what fixed it for me.
Click to expand...
Click to collapse
Thanks a lot guy that worked and I'm now back in business. Meaning my 3G is now operational. Don't have 4G in my area but I assume it works now as well. My device was unlocked and when I go into network now it shows CDMA/LTE.
Edit:
I did not have the official Xoom cable either.
Zone, did you flash the HLK75D SBF?
My sprint LG G2 was boot looping into TWRT after I accepted an OTA.
I've read several posts, http://forum.xda-developers.com/showthread.php?t=2477595 and this one http://forum.xda-developers.com/showthread.php?t=2448960,
the problem I get is I can not get into download mode, well, I did enter it, but it stuck at 0%, and my computer don't recognize it. Can not find the phone in "devices", installed the driver and still no avail. BTW, when I boot into TWRT, my computer can recognize the android device and ADB works then.
Since I cannot get past the download mode, I can not use the LG flash tool.. it says "LG USB/Parallel lock key is not detected".
Any suggestion is deeply appreciated.
Try this http://forum.xda-developers.com/showthread.php?t=2451696
[FIX] Installed TWRP and now you're stuck after OTA?
Sent from my LG-G2 using XDA Premium 4 mobile app
prking07 said:
Try this http://forum.xda-developers.com/showthread.php?t=2451696
[FIX] Installed TWRP and now you're stuck after OTA?
Sent from my LG-G2 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried, use ADB while the phone is in TWRT, went through and restarted, still boot into TWRT.
The command line in TWRT will pop up an error message saying "not enough space", although I do have enough space. So it didn't work either.
Sounds like you just need to keep messing with it until you can get it to recognize it in download mode and go back to stock. What Windows version do you have? i had some issues with 8 but 7 worked fine.
thenewak said:
Sounds like you just need to keep messing with it until you can get it to recognize it in download mode and go back to stock. What Windows version do you have? i had some issues with 8 but 7 worked fine.
Click to expand...
Click to collapse
I have Windows 7 64bit with all the latest patches.
Utahnewbie said:
I tried, use ADB while the phone is in TWRT, went through and restarted, still boot into TWRT.
The command line in TWRT will pop up an error message saying "not enough space", although I do have enough space. So it didn't work either.
Click to expand...
Click to collapse
Well, that Fix clear FOTA with zeros and it should end with "not enough space", this is normal.
I guess when your phone restarted into download mode and got stuck on 0%, it already overwrite maybe part of system partition, this is why only download or recovery works.
Did you made any nandroid backup before? If yes, restore at least boot & system from it. It should help, so you can boot normally. If you do not have any backup, well, maybe some other fellow Spring user can give u his boot & system backup files so you can restore them.
p.valenta said:
Well, that Fix clear FOTA with zeros and it should end with "not enough space", this is normal.
I guess when your phone restarted into download mode and got stuck on 0%, it already overwrite maybe part of system partition, this is why only download or recovery works.
Did you made any nandroid backup before? If yes, restore at least boot & system from it. It should help, so you can boot normally. If you do not have any backup, well, maybe some other fellow Spring user can give u his boot & system backup files so you can restore them.
Click to expand...
Click to collapse
Yes, I have a full nandroid backup before. I did a full restore from it after the boot-looping, but it didn't work, I still boot into TWRP and unable to boot into system.
Utahnewbie said:
Yes, I have a full nandroid backup before. I did a full restore from it after the boot-looping, but it didn't work, I still boot into TWRP and unable to boot into system.
Click to expand...
Click to collapse
so you followed that fix to clear FOTA, restored from backup, but when do "REBOOT SYTEM" from TWRP it ends again in recovery?
hmmm, how about these steps:
http://forum.xda-developers.com/showthread.php?t=2432476
using Flash Tool to restore stock ROM.
p.valenta said:
so you followed that fix to clear FOTA, restored from backup, but when do "REBOOT SYTEM" from TWRP it ends again in recovery?
hmmm, how about these steps:
http://forum.xda-developers.com/showthread.php?t=2432476
using Flash Tool to restore stock ROM.
Click to expand...
Click to collapse
No, it doesn't work, because my phone stuck at 0% in download mode and it doesn't show up in my device manager on PC.
I had the same problem
Utahnewbie said:
No, it doesn't work, because my phone stuck at 0% in download mode and it doesn't show up in my device manager on PC.
Click to expand...
Click to collapse
I used the fix from http://forum.xda-developers.com/showthread.php?t=2448960
except that I used the sprint .tot file. (http://storagecow.eu/index.php?dir=Xda/LG+G2/Stock/Sprint+LS980/)
Did you try to reinstall the drivers or use a different cable?
I encountered the same issue last night. I reinstalled the Verizon united drivers and rebooted my machine. The next time that I connected the device in download mode, device manager picked up the device. I had to re-run the LG tool, but it eventually progressed past 0% and my issue was fixed. You can reinstall the verizon drivers using the following link.
http://wacomalt.com/dropbox/LGG2/StockRevert/LG VZW_United_WHQL_v2.11.1.exe
I'm having the same issues with D802b after doing the 60mb OTA update. My phone didn't get a chance to actually do the download as on first restart it just went straight into TWRP and I haven't been able to get back since.
It's just looping back into TWRP each time. I've now completely wiped all parts of the phone including the internal SD card, I've even re-installed a new kernel and rom (The custom one I was using before this happened, from http://forum.xda-developers.com/showthread.php?t=2505682) from an attached USB (sd card reader) with successful installs through TWRP (including wiping cache etc), still reboots into TWRP on restart. I've also done a hard reset that was supposedly successful, still boots into TWRP.
Same as the OP, it won't 'install itself' properly in windows while in TWRP mode or in 'Software Download' mode (turn on with up and down buttons pressed down and plug data cable in). I've tried in vain to hunt down a specific D802 inf as pointing it at the universal driver didn't detect either.
I have installed the Android SDK, LG Suite, LG Universal drivers. I've then tried the B2CAppSetup (which works, but won't detect the device). I've then tried the FlashTool 1.0.54 and it gets all the way through but can't communicate with the device.
The only thing I haven't managed to do yet is to decompress the official kdz into a zip so I can flash it through TWRP. Haven't had much luck with LGExtract as of yet.
Rather baffled actually, as I'm sure the OP is.
Any thoughts?
---------- Post added at 08:55 PM ---------- Previous post was at 08:11 PM ----------
Having just posted all that above, I look further down the forum and someone linked to this thread below.
Fixed my issue, so I imagine it will sort yours out too.
http://forum.xda-developers.com/showthread.php?t=2451696
Update: I don't want to deal with this issue anymore.. just replaced it and got a new one
Utahnewbie said:
Update: I don't want to deal with this issue anymore.. just replaced it and got a new one
Click to expand...
Click to collapse
That is excellent, did they give you a hard time replacing it?
thenewak said:
That is excellent, did they give you a hard time replacing it?
Click to expand...
Click to collapse
No, because I microwaved it.
prking07 said:
Try this http://forum.xda-developers.com/showthread.php?t=2451696
[FIX] Installed TWRP and now you're stuck after OTA?
Sent from my LG-G2 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried that method many times and it does not work on the Sprint version. If you read through the thread you'll noticed that others with Sprint devices can not get that method to work.
The only method that worked for me was to use the LG Flash tool and flash the Sprint tot file and follow the instructions for the Verizion method for going back to stock.
---------- Post added at 01:41 AM ---------- Previous post was at 01:22 AM ----------
Utahnewbie said:
My sprint LG G2 was boot looping into TWRT after I accepted an OTA.
I've read several posts, http://forum.xda-developers.com/showthread.php?t=2477595 and this one http://forum.xda-developers.com/showthread.php?t=2448960,
the problem I get is I can not get into download mode, well, I did enter it, but it stuck at 0%, and my computer don't recognize it. Can not find the phone in "devices", installed the driver and still no avail. BTW, when I boot into TWRT, my computer can recognize the android device and ADB works then.
Since I cannot get past the download mode, I can not use the LG flash tool.. it says "LG USB/Parallel lock key is not detected".
Any suggestion is deeply appreciated.
Click to expand...
Click to collapse
Not really sure if this would've solve your problem but here's my possible theory to why you couldn't get it to work:
I was in the same situation. Took the OTA update and was boot looping into TWRP. Just like you, nothing in TWRP would fix it. I think you probably panicked and rush through the instructions and forgot some important steps. Make sure you did not install the Verizon driver by accident because that will cause problems with your Sprint phone not being properly detected by your computer. I did panicked and started to try to many things and somehow got a copy of the Verizon driver and installed it. ADB was able to see my phone but when I tried to sideload something through TWRP it would generate an error. I found out that I had both drivers(LG USB driver and the Verizon USB driver) installed and after removing the Verizon USB driver my computer was able to detect my phone properly. It's really important that after making any changes or installations of drivers you will need to reboot your PC to get the new changes to take effect.
You got the "LG USB/Parallel lock key is not detected" error is because you forgot to copy and overwrite the "MegaLock.dll" that's located at "C:\LG\LGFlashTool" directory.
To get into download mode you just need to press the +volume button only(do not hold or press the power button) and plug in the USB cable that's attached to your computer and Download Mode should come on. It will stay on 0% until the LG Flash tool flashes the Sprint stock rom onto the phone.
Once I got the phone to come up in Download Mode I had to go into Device Manager and find the device and then change the COM port to COM 41 then everything went smoothly as the instruction indicated. If you were not able to change the COM to COM 41 then it will never work.
If you're not sure that you have all the files then this is where I got mine from:
http://forum.xda-developers.com/showthread.php?t=2486738&page=7
or
http://forum.xda-developers.com/showpost.php?p=47849315&postcount=9
After I got the file above I followed the directions for the Verizon method below:
http://forum.xda-developers.com/showthread.php?t=2448960
Utahnewbie said:
No, because I microwaved it.
Click to expand...
Click to collapse
How long for? Thanks,
Sent from my Nexus 7 using Tapatalk
RedMist said:
How long for? Thanks,
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
four seconds
Utahnewbie said:
four seconds
Click to expand...
Click to collapse
That was enough to stop it booting? Cheers,
Sent from my Nexus 7 using Tapatalk
I'm using a droid razr m xt907 by verizon. Yesterday an update was released for 4.4.2 kitkat, my phone is still rooted and i can't find the safest way to unroot it so i can get the update. Does anyone know the best way to unroot and make sure everything's normal again so that the 4.4 update will work this time? It stops at around 25% into the update. Thanks for any help.
Edit: I've tried a factory restore, i unrooted completely. My kernell is normal, my stock recovery is normal. The update just isn't working, and i don't know the best way to fix it. My bootloader is locked, so there was never any custom recovery or ROM's installed.
I'm having the same problem. I unrooted before the update but still not working. The update get's to about 25% of install then fails. I've tried about 4 or 5 times today. Factory rest and uninstalling root didn't help either
mikegt11 said:
I'm having the same problem. I unrooted before the update but still not working. The update get's to about 25% of install then fails. I've tried about 4 or 5 times today. Factory rest and uninstalling root didn't help either
Click to expand...
Click to collapse
Exactly, i can't figure out what i'm supposed to do. Ive tried about that many times, and i've tried factory restoring, i've wiped the cache, etc.
Factory reset.
RSD to stock 4.1.2 in case some system app is missing.
Skip setup.
Try the update again.
Or just RSD to the new version.
Those would be my next steps.
Sent from my Nexus 7 using XDA Free mobile app
Coronado is dead said:
Factory reset.
RSD to stock 4.1.2 in case some system app is missing.
Skip setup.
Try the update again.
Or just RSD to the new version.
Those would be my next steps.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
I'll try this tomorrow when i have a chance, thank you for responding.
Coronado is dead said:
Factory reset.
RSD to stock 4.1.2 in case some system app is missing.
Skip setup.
Try the update again.
Or just RSD to the new version.
Those would be my next steps.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
do you know any good tutorials for how to use rsd for this? cuz i want to just rsd to the new version if you can help me find the files to do that, i have rsd lite already.
help
shadowwolfsl said:
do you know any good tutorials for how to use rsd for this? cuz i want to just rsd to the new version if you can help me find the files to do that, i have rsd lite already.
Click to expand...
Click to collapse
i got same problem. after download 446 mb update. try to instal. work about for 30 percent then suddenly restart and says that update failed
my device is rooted. then i remove root from the SU menu and keep failed to update
what should i do?
supercahyo said:
i got same problem. after download 446 mb update. try to instal. work about for 30 percent then suddenly restart and says that update failed
my device is rooted. then i remove root from the SU menu and keep failed to update
what should i do?
Click to expand...
Click to collapse
Personally i just modified the .xml file and loaded it via RSDLite.
shromy said:
Personally i just modified the .xml file and loaded it via RSDLite.
Click to expand...
Click to collapse
same thing that i did
Im mid process but heres the only answer ive found....
THERE IS HOPE HERE LOLZ
If ya all do let me know how the full strip and downgrade went....
If u find another way pls share info w me as well...
Lj-
Sorry all being a new user they would not let me post a link so I cut it up.......Still would not le5 me send it but u can email me directly and I'll gladly send u a direct copy or look on andromods the answer is there
---------- Post added at 08:15 PM ---------- Previous post was at 07:54 PM ----------
supercahyo said:
i got same problem. after download 446 mb update. try to instal. work about for 30 percent then suddenly restart and says that update failed
my device is rooted. then i remove root from the SU menu and keep failed to update
what should i do?
Click to expand...
Click to collapse
Step by step on andromods...and how to reroot there as well
Lj-
Sorry won't let me post links yet....
droid razr M kitkat update fail
I would like to know a solution, I'm tired of trying and do not get even with rsd lite.
this is my mail: [email protected]
galestz said:
I would like to know a solution, I'm tired of trying and do not get even with rsd lite.
this is my mail: [email protected]
Click to expand...
Click to collapse
because you have not modified the xml file after decompressing the entire zip.
It just won't work !
shadowwolfsl said:
I'm using a droid razr m xt907 by verizon. Yesterday an update was released for 4.4.2 kitkat, my phone is still rooted and i can't find the safest way to unroot it so i can get the update. Does anyone know the best way to unroot and make sure everything's normal again so that the 4.4 update will work this time? It stops at around 25% into the update. Thanks for any help.
Edit: I've tried a factory restore, i unrooted completely. My kernell is normal, my stock recovery is normal. The update just isn't working, and i don't know the best way to fix it. My bootloader is locked, so there was never any custom recovery or ROM's installed.
Click to expand...
Click to collapse
I also had a Razr M. i unroot it by SuperSU, but it won't update properly, same like others, 25%, then fail.
Steve977 said:
I also had a Razr M. i unroot it by SuperSU, but it won't update properly, same like others, 25%, then fail.
Click to expand...
Click to collapse
i got it functioning after rsd lite back to stock after a factory restore
shromy said:
because you have not modified the xml file after decompressing the entire zip.
Click to expand...
Click to collapse
I have found the solution, you have to edit the XML file that is in the ROM. and delete the lines containing the words ("oem" and "var"). then you put the phone in fastboot mode and use the rom with the modified file will have only about 18 steps then when the last file billboards will ask you turn on the phone manually and status, restart your phone and enter mode fastboot again and finished well. NOTE: remember to put the usb debugging before starting everything. everything you do will be at your own risk, but so what I Realize, and it worked and I have my razr m with kitkat and before I could not for the same reason of the root. thank you all
shadowwolfsl said:
I'm using a droid razr m xt907 by verizon. Yesterday an update was released for 4.4.2 kitkat, my phone is still rooted and i can't find the safest way to unroot it so i can get the update. Does anyone know the best way to unroot and make sure everything's normal again so that the 4.4 update will work this time? It stops at around 25% into the update. Thanks for any help.
Edit: I've tried a factory restore, i unrooted completely. My kernell is normal, my stock recovery is normal. The update just isn't working, and i don't know the best way to fix it. My bootloader is locked, so there was never any custom recovery or ROM's installed.
Click to expand...
Click to collapse
:victory::victory::victory::victory::victory:
I can resolve if u want reply me
Does it work while it is Rooted ?
galestz said:
I have found the solution, you have to edit the XML file that is in the ROM. and delete the lines containing the words ("oem" and "var"). then you put the phone in fastboot mode and use the rom with the modified file will have only about 18 steps then when the last file billboards will ask you turn on the phone manually and status, restart your phone and enter mode fastboot again and finished well. NOTE: remember to put the usb debugging before starting everything. everything you do will be at your own risk, but so what I Realize, and it worked and I have my razr m with kitkat and before I could not for the same reason of the root. thank you all
Click to expand...
Click to collapse
I'm sorry, but dows it work while my phone is rooted ? before i noticed your solution, i had to delete all root apps and SuperSU (along with the root) to update it. And Failed.
galestz said:
I have found the solution, you have to edit the XML file that is in the ROM. and delete the lines containing the words ("oem" and "var"). then you put the phone in fastboot mode and use the rom with the modified file will have only about 18 steps then when the last file billboards will ask you turn on the phone manually and status, restart your phone and enter mode fastboot again and finished well. NOTE: remember to put the usb debugging before starting everything. everything you do will be at your own risk, but so what I Realize, and it worked and I have my razr m with kitkat and before I could not for the same reason of the root. thank you all
Click to expand...
Click to collapse
im getting phone returned fail y
solution
Adriantech said:
:victory::victory::victory::victory::victory:
I can resolve if u want reply me
Click to expand...
Click to collapse
plz help me iwant your help
djdrews4357 said:
im getting phone returned fail y
Click to expand...
Click to collapse
princeabdullah1555 said:
plz help me iwant your help
Click to expand...
Click to collapse
We can't help either of you, if you don't give us details.
Sent from my HTC6525LVW using Tapatalk