Database Develop

[Q] [S.O.S.] A rare MILESTONE brick situation!

Fellow androiders,
I believe I am in a really rare brick situation that no matter how I try, it still does not show any turn around.
[Introduction]
I bought a Korean version Milestone(Moto Qrty, as they put], and I took it to China. Because the original phone did not support sending Chinese text message, plus, too much telco provided apps are making the phone sluggish, I decided to follow my friend advice, to switch to widely available open-sourced Froyo (I wanted the CM).
[Problem]
I thought that the flashing process would not be too difficult and I could handle it by myself. But, it turns out that I have become a victim of an overly simplified version of flashing guide. I don't know what exactly have done wrong, after successfully rooted the phone, I vaguely remember that I have used CM ROM for Droid, instead of CM ROM for Milestone.
And that made my phone a brick. My phone will turn on, but will restart again and again after M logo(So-called M boot loop).
[Background information of the Phone and my PC environment]
Phone Model: A853
Original Bootloader version: A0.20
Original Android System: Froyo
RSD lite version: 5.3.1. (later switched to 4.6 due to the suspicion of RSD bug)
Operating System: Windows 7 64 bit, English
[What I have tried so far]
I have tried to follow many tips on the internet. Tips from Korean websites, from Chinese websites, and from English websites. Basically, these tips will let you flash back to the original ROM by using RSD lite.
But, no matter what I try, it will not fix the boot loop problem.
I've tried to
1) Bring the phone to the original status [did not work.]
- flash the bootloader into A0.20 (the original bootloader) with RSD lite;
(bl_a020_umts_sholesumts_skt_consumer_replacer.sbf)
- flash with original Froyo sbf (following the advice from Korean websites, flashed Clair first, and then flashed Froyo) with RSD lite.
(A853_2.1(Eclair).SBF / A853_2.2.1(Proyo).SBF)
* According to what Koreans say, it would make your phone into the original status, will even remove signs of root.
2) Used many combination of following bootloader and ROMs
- flash the bootloader into 90.78ch
(BL_9078_umts_sholes_GC_HS_Consumer_replacer.sbf)
- flash the bootloader into 90.78
(BL_9078_umts_sholes_HS_Consumer_replacer.sbf)
- GOT221 ROM
(GOT_RTEU_2_2_1FULL.sbf)
- And some other un-name-able ROMs
SGC_U2_03.04.0_USASHLSGCB1B2B5008.0R_PDS06A_HWp2a_1FF.sbf
3) Used many different OpenRecovery Variations
OpenRecovery v1.46
OpenRecovery 3.3
OpenRecovery GOT mod v2.1
4) Restore Nandroid backup which I made right before I made my phone brick.
5) Cleaned data/cache/dalvic as I do every flash, and tried boot without SIM card and SDCard.
[Some discoveries and successes]
- With 90.78ch + GOT2.2.1, it will show "Android" screen, but it will reboot as soon as the phone OS interface show up.
- According to my friend, when he flashed back to the original bootloader A0.20 + original froyo Rom, it showed TelCo Symbol "T" once (which is the booting screen right after M).
[Final Comment]
What I really want to know is that is it the time I give up on it? or is there any value of pursuing other knowledge on bring this phone back?
I really need this phone, and it will take some times to save money to buy another smartphone, I would really really appreciate if you can help me bring this phone back to normal.
Thank you.

some users reported problems with sdcard. try to boot without sdcard, and wipe everything after or before the flash process.
and i don think it's hard bricked...

Sir, I have tried so, somehow, I did not have lucks other had.

roofghost said:
Sir, I have tried so, somehow, I did not have lucks other had.
Click to expand...
Click to collapse
So you've tried flashing different bootloaders, with no success? I always thought flashing another bootloader version different from your own was risky.
If not, you can just try flashing the SBF from here: http://android.doshaska.net/rootable , then installing OpenRecovery, rooting the phone, flashing a custom ROM, etc.

..... my bad

I have the same issue,
in recovery there is message when wiping data/factory reset:
E:Error in CACHE:fota/log
(no space left on device)
I am wondering, if I move CACHE to SD would it help??
Yesterday I have installed original Rom (shols~) and phone booted once to android and when I have rebooted it, there is M bootloop again.
Please help me

skadude66 said:
So you've tried flashing different bootloaders, with no success? I always thought flashing another bootloader version different from your own was risky.
If not, you can just try flashing the SBF from here: android.doshaska.net/rootable , then installing OpenRecovery, rooting the phone, flashing a custom ROM, etc.
Click to expand...
Click to collapse
Thanks, did not work.
I have a feeling that the "doshaska" will know how to solve this. Anyone know how to contact or PM him?
Thanks.

By the way,
in this case, is there anyway can fix the brick via "console" in the OpenRecovery?
Thanks.

So... you have open recovery and can get to the console...
What happens if you copy CM to the updates folder and flash CM?

zeppelinrox said:
So... you have open recovery and can get to the console...
What happens if you copy CM to the updates folder and flash CM?
Click to expand...
Click to collapse
Yes, I can enter OpenRecovery and can get to the console.
And,
sorry about the CM, I think I will have to try that again and let you know then.
Is there any CM ROM you want me to try? (Hopefully with a reliable instruction. If you are busy, you can just leave this part, I will look for myself about the instruction.)
Truly thank you and glad to see new reply under this topic.

Well, use OR's mount as usb function and plug into your computer.
Copy the latest CM7 (I think that's what you want - or any ROM really) to the updates folder.
Wipe all caches
Then apply the update
It should "just work"
I mean, the hardest part is getting into OR lol
I'm surprised that your battery hasn't died yet

zeppelinrox said:
Well, use OR's mount as usb function and plug into your computer.
Copy the latest CM7 (I think that's what you want - or any ROM really) to the updates folder.
Wipe all caches
Then apply the update
It should "just work"
I mean, the hardest part is getting into OR lol
I'm surprised that your battery hasn't died yet
Click to expand...
Click to collapse
Can I install CM7 on Froyo? I thought that was for the Android 2.3.
I have just flashed back to the original bootloader of A0.20 (it was 90.78 as I play around with it.), and flashed the original korean .sbf froyo. Just to follow your suggestion.
I will try to install vulnerable recovery. I think in this way, I can use OpenRecovery again.
About my batter, I purchased a separate battery charger.
I will keep my status updated as soon as I try this out.
Thanks.

same problem and flash so many rom My milestone can't acess sdcard on recovery mode and android os.
Sent from my Milestone using XDA App

guys same problem here, help us

[HOWTO] Flashing OLD/NEW Baseband Using KDZ + Rooting + Installing Custom Recovery

Hi I found a similar article on androidforums.com so I thought id make one here as a lot of people still seem to not know how to flash basebands and go from there. Ill start from the beginning.
For those who don't understand what this is about.
Old Baseband = If you have the Stock Froyo (2.2) Android system on your phone then you have the OLD BASEBAND, and you do not need this unless you updated to past 2.2.2 then continue reading if you wish to root your phone the easy way.
New Baseband = If you updated to the Stock Gingerbread (2.3) Android System on your Optimus One, then you fit this category, Lg have implemented a new baseband in this update which makes any Roms based on the old baseband not function, as well as making it more difficult to root your phone
FLASHING OLD BASEBAND
If you're already on official Gingerbread version you will need to downgrade your version to Froyo 2.2.2 using KDZ Updater. This is because the new Gingerbread contains the new baseband, and the Froyo firmware is the old baseband.
To do this please go onto this link that contains kdz and the stock Froyo 2.2.2 Rom required to flash. The reason you need 2.2.2 is its the easiest and proven version to work with Gingerbreak to root your device.
http://forum.xda-developers.com/showpost.php?p=13396506&postcount=1
Notice: If by some ACCIDENTAL reason, your phone gets stuck in EMERGENCY MODE during flashing, follow the instructions on this link how to use KDZs functions to continue flashing the firmware you downloaded in Emergency mode.
http://forum.xda-developers.com/showthread.php?t=1275523
FLASHING NEW BASEBAND
The Kdz File for new baseband is below, use the same method as above only using the v20G .kdz file instead of the 2.2.2 v10E update.
This will update your phone to the official LG 2.3 firmware, in which the new baseband originated.
csmg.lgmobile.com:9002/swdata/WEBSW/LGP500/ANEUBK/V20g_00/V20G_00.kdz
If then stuck on LG Logo OR boot animation, try pulling and putting in your battery, turning on your phone and holding down volume down and home key, this should reset your phone to factory and then you will be able to boot into the stock gingerbread.
ROOTING
The easiest way to get root privileges on Old Baseband (2.2.2) firmware device is by using Gingerbreak apk. Just download it, install it and run it.
forum.xda-developers.com/attachment.php?attachmentid=600902&d=1305802958
To get Root access on the New Baseband (2.3.3) use SuperOneClick
http://forum.xda-developers.com/showthread.php?t=803682
Or direct link to the latest version
forum.xda-developers.com/attachment.php?attachmentid=778098&d=1320906597
Make sure, after you download the program, you go into your cmd, then go into the ADB folder, drag the ABD exe file into command prompt, delete the .exe part and add devices, so it look like this
OR
Download the ADB.zip attachment on this post, EXTRACT it so cmdXP and cmd7 are located inside the ADB folder in the Superoneclick directory, and run either version, depending on your windows version (This links you directly into ADB app, instead of manually dragging ADB.exe int cmd, really its just for your convinience.)
Then all you have to do is type the following lines.
adb devices
press enter
adb shell
press enter
then type in the following directly after
echo 1 > /data/local/lge_adb.conf
press enter.
Then go into Superoneclick.exe, select auto method and run root, this should then eventually root your device.
***WARNING***
Some Antivirus softwares will detect Superoneclick as a Virus.
IT IS NOT A VIRUS, just the types of exploite code it uses makes some antivirus software think of it as malicious. Just disable your AV for 5 mins before you extract Superoneclick.
RECOVERY
There's two popular custom Recovery versions for O1 - AmonRa and ClockworkMod
The easiest way to flash ClockworkMod Recovery is by downloading ROM Manager app from the Market (free or donate version doesn't matter) and choose to flash the latest recovery version and choose the option to Reboot in Recovery mode.
For Other Recoveries including Amonra there are a few links, but here is the one that has flashable zips
http://forum.xda-developers.com/showthread.php?t=1523050
Just flash the zip files in Clockworkmod recovery menu, after you install that through Rom Manager if you wish to use a different recovery.
Now that you got the right baseband + your device is rooted and loaded with a custom recovery you may install any Rom you wish that is based on the correct baseband such as
Mik_os 6.5.8 Cyanogenmod port (OLD BASEBAND).
http://forum.xda-developers.com/showthread.php?t=946354
[UNOFFICIAL][DEV/GEEKS-ONLY] Cyanogenmod 9 (Android 4.0.3)[BETA][NEW BASEBAND]
http://forum.xda-developers.com/showthread.php?t=1558213
OFFICIAL CYANOGENMOD Rom [NEW BASEBAND]
http://get.cm/?device=p500
Oxygen ROM 2.3.2 (Android 2.3.7)[NEW BASEBAND]
http://forum.xda-developers.com/showthread.php?t=1325386

Next time, search better
Also posted in wrong thread, this is developmentthread...

Don't know how many guides still to come on downgrading baseband.....
People...do search before making a new guide......
MODERATOR...plz look into this thread...
Sent from my LG-P500 using xda premium

fundoozzz said:
Don't know how many guides still to come on downgrading baseband.....
People...do search before making a new guide......
MODERATOR...plz look into this thread...
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Guys i did a search and looked into the sticky how to, and the only thing about downgrading baseband is using LGMDP, and kdz is only "mentioned" as a tool for unbricking your phone and flashing old firmware, new users would not know to use kdz.
Also this is a universal guide to root ANY lg optimus one together with having the old baseband, without having to mess around with SDK or LGMDP.
All members have to do now is look at this thread and all their questions are answered hopefully...

DIfference betweem this and doks.
This uses Official Lg KDZ updater, which means much less likely to brick your phone and if it does, KDZ is what is used to unbrick it anyway,
This option is much simpler to use for anyone.

I hear a lot about the new baseband making ROMs incompatible, but is there any advantage to the new baseband?

its not that they are making roms incompatiable, its that they are not designed for those Roms,
So far there has been no reports of any advantage having a new baseband, Lg engineers obviously decided on it for some reason, but the old baseband is more than fine, and in fact i have read several reports that with the new baseband gsm reception got worse in areas that they used to have fine reception, but thats all speculation.
Your best bet is to try for yourself, but if you want to make use of Roms such as miks cyanogen mod or others you have to use the old baseband.
There are other Roms available on the new baseband, so its upto you.
I suggest what rom you would like to install on your phone first, then pick the baseband it requires, as its only a simple flashing of your firmware.
Also note Gingerbreak.apk doesnt root any stock firmware past the 2.2.2 update.
Personally i pick the functionality and advantage of having a custom rom such as cyanogenmod over an update to the baseband

Does this guide work for Optimus T (LG P509) ? I have got one recently and currently using stock 2.2 on it. I don't know the difference between LG p500 and LG P509. I'm coming from T-Mobile G1 on which I'm using CM 7.1. Thanks for guidance.
Sent from my Dream/Sapphire using xda premium

Hi,
Doing a little search i found this thread
http://forum.xda-developers.com/showthread.php?t=960278
looking at it, i assume you can use this guide for p509, but i can not be 100% sure, try finding the t-mobile 2.2 kdz file, but yes not 100% sure the main difference.

deniso177 said:
DIfference betweem this and doks.
This uses Official Lg KDZ updater, which means much less likely to brick your phone and if it does, KDZ is what is used to unbrick it anyway,
This option is much simpler to use for anyone.
Click to expand...
Click to collapse
KDZ can brick your phone permanently. Dont use KDZ unless there is no other option, and using KDZ just to flash baseband is just dumb since there are better and safer methods. KDZ wipes out everything, so there is a high chance to brick, and it can't be fixed other than by going to the service center. This thread by doktornoktor is safer.
http://forum.xda-developers.com/showthread.php?t=1149530
Thanks anyway for sharing.

Gremaldin said:
KDZ can brick your phone permanently. Dont use KDZ unless there is no other option, and using KDZ just to flash baseband is just dumb since there are better and safer methods. KDZ wipes out everything, so there is a high chance to brick, and it can't be fixed other than by going to the service center. This thread by doktornoktor is safer.
http://forum.xda-developers.com/showthread.php?t=1149530
Thanks anyway for sharing.
Click to expand...
Click to collapse
I think KDZ is quite a safe method, rather than the LGMDP incorrectly backing up your NV2 and losing IMEI etc

Gremaldin said:
KDZ can brick your phone permanently. Dont use KDZ unless there is no other option, and using KDZ just to flash baseband is just dumb since there are better and safer methods. KDZ wipes out everything, so there is a high chance to brick, and it can't be fixed other than by going to the service center. This thread by doktornoktor is safer.
http://forum.xda-developers.com/showthread.php?t=1149530
Thanks anyway for sharing.
Click to expand...
Click to collapse
As you already quoted it, i said that this method is different from Doks.
As for wiping all data completely, so its all brand new and neat, then try to fiddle around with internals and possibly have a bug result from it.
KDZ is what is used to UNBRICK your phone in the first place, so go do some research before posting unnecessary things.
Lastly how about you show some respect and keep your negative and rude comments to yourself, if you dont like this method dont do it, dont abuse people in the process.

terratrix said:
I think KDZ is quite a safe method, rather than the LGMDP incorrectly backing up your NV2 and losing IMEI etc
Click to expand...
Click to collapse
And yep exactly, i personally prefer completely reinstalling something to make it work properly, then doing things dodgy.

tried using gingerbreak to root my device but stuck in rooting and exploit ph0ne does not reboot..
Sent from my LG-P500 using xda premium

ichigo200 said:
tried using gingerbreak to root my device but stuck in rooting and exploit ph0ne does not reboot..
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
it means your phone is past the firmware update that gingerbreak works on,
as it says in the first post, use kdz and the file in the link to flash your phone to that firmware, and then gingerbreak will work

You guys will only learn when you finally end up with a bricked phone. It has happened to several people, including me. I am not a noob, I have used KDZ before and I know very well how to use it. Most of the time, everything goes smoothly. But even if we follow all instructions to the letter, there is a chance of KDZ bricking our phone for good.
http://androidforums.com/lg-optimus...read-2-3-3-official-firmware.html#post3328455
A warning to anyone tempted to do this. Like the original poster, I also have an LG Optimus T. I am technically savvy (15 years IT experience) and I followed the directions to the letter, but the end result is a bricked, unrecoverable phone. Had I known the risks involved, I would have been perfectly content with Froyo and waited for the official upgrade to arrive.
Here is how mine failed: during the kdz update process, while the phone was on the "Emergency Mode" screen, the kdz updater program threw an exception and crashed. This caused the phone to be permanently locked in emergency mode. The buttons are unresponsive and the only way to turn it off is to remove the battery. With the battery in, it immediately goes to the emergency screen. No combination of button presses (eg, hard reset) does anything. The computer will still see the devices but only if I remove the battery and start the phone up by inserting the USB cable.
I have tried every method for recovery I could find including the following. In each case, I tried it with the modem device listed in device manager both disabled and enabled, as instructed in other recovery threads I found.
Flashing the original .kdz ROM in emergency and cs_emergency modes. When I did, it failed with an exception 4008.
Flashing the original .dz ROM with all of the tools I could find. LGMDP and LGDP2 could see the phone's COM port but beyond that, they could not communicate with the phone in any way. I couldn't even retrieve the IMEI number.
Updating the phone with the LG update software. It actually detects that the phone needs an update and starts to do one but it fails at the point where it tries to communicate with the phone.
Based on other posts I found for the same problem, I believe the phone is completely unrecoverable. I spent over six hours trying to solve the problem and I'm kicking myself for even trying this. I have put in a repair claim with LG and I'm waiting for instructions on how to proceed.
I would not recommend you try this unless you are not worried about destroying your phone. I imagine most installs go without a hitch but if the buggy kdz updater software crashes like it did for me, your phone will likely be bricked permanently.
Click to expand...
Click to collapse
http://androidforums.com/optimus-on...y-boots-stuck-emergency-mode.html#post3301128
In short, don't mess with KDZ unless you really have to.
Click to expand...
Click to collapse
IF you still think KDZ is safe, then go ahead, use it. I don't care if you end up with a bricked phone.
EDIT: The guys at the service center favour LGMPD over KDZ too

Gremaldin said:
You guys will only learn when you finally end up with a bricked phone. It has happened to several people, including me. I am not a noob, I have used KDZ before and I know very well how to use it. Most of the time, everything goes smoothly. But even if we follow all instructions to the letter, there is a chance of KDZ bricking our phone for good.
http://androidforums.com/lg-optimus...read-2-3-3-official-firmware.html#post3328455
http://androidforums.com/optimus-on...y-boots-stuck-emergency-mode.html#post3301128
IF you still think KDZ is safe, then go ahead, use it. I don't care if you end up with a bricked phone.
EDIT: The guys at the service center favour LGMPD over KDZ too
Click to expand...
Click to collapse
I have used KDZ more than 2 dozen times -.- Just used it again this morning. I never ended up with a bricked phone mind you. They favour LGMPD since it's more updated, while KDZ is a little old but still very good.
There is a fairly equal share of bricked phones using LGDMPD, eventhough they got it back by using other people's NV2, they need to hope they are lucky to escape the long arm of the law.

Gremaldin said:
You guys will only learn when you finally end up with a bricked phone. It has happened to several people, including me. I am not a noob, I have used KDZ before and I know very well how to use it. Most of the time, everything goes smoothly. But even if we follow all instructions to the letter, there is a chance of KDZ bricking our phone for good.
http://androidforums.com/lg-optimus...read-2-3-3-official-firmware.html#post3328455
http://androidforums.com/optimus-on...y-boots-stuck-emergency-mode.html#post3301128
IF you still think KDZ is safe, then go ahead, use it. I don't care if you end up with a bricked phone.
EDIT: The guys at the service center favour LGMPD over KDZ too
Click to expand...
Click to collapse
Mate your the one who clearly doesnt get it.
And i read your post on androidforums, you even managed to brick your phone installing custom recovery, clearly your phone software is buggy, not kdz, kdz is capable of recovering while in emergency mode as well, but of course there are freak accidents.
EVERYTHING has a WARNING.
Every single Rom, Kernel, Recovery also carry a chance of bricking your phone.
I have used Kdz dozens of times and never had a problem with it, in fact, its what solved my problems in the first place.
And exactly wat terra said, the way LGDMPD works can also cause bricked phoes or taking shortcuts to make things half work.
You have to know what your doing, and follow instructions TO THE WORD, and you should be fine, if your going to skim read then you brick your phone doing the simplest of tasks (such as repeatedly flashing zips without reloading recovery...)
I will always prefer kdz as thats what the firmware comes with originally + i prefer doing clean installs any day.

Please Help...
Guys please help me. everything was running fine until I decided to switch to stock 2.3.3. I was unaware with this baseband thing. I switched to stock 2.3.3. I did not like it, so decided to roll back to cm7, I did, and here i am with no signal in my phone... I did flash the old baseband, but am still stuck with no signal... am in real trouble, and now if I again switch to stock 2.3.3, then also I dont get a network coverage at all. Please help me buddies
---------- Post added at 04:39 PM ---------- Previous post was at 04:28 PM ----------
And yes one more thing, even if I flash back the old stock froyo, via kdz or lgmdp, I cant get the network coverage... the guy at LG service center says there's some problem with the board... but I dont think its the board problem, is there any way to diagnose this issue or am I *ucked?

shreyas.kukde said:
Guys please help me. everything was running fine until I decided to switch to stock 2.3.3. I was unaware with this baseband thing. I switched to stock 2.3.3. I did not like it, so decided to roll back to cm7, I did, and here i am with no signal in my phone... I did flash the old baseband, but am still stuck with no signal... am in real trouble, and now if I again switch to stock 2.3.3, then also I dont get a network coverage at all. Please help me buddies
---------- Post added at 04:39 PM ---------- Previous post was at 04:28 PM ----------
And yes one more thing, even if I flash back the old stock froyo, via kdz or lgmdp, I cant get the network coverage... the guy at LG service center says there's some problem with the board... but I dont think its the board problem, is there any way to diagnose this issue or am I *ucked?
Click to expand...
Click to collapse
Hey mate, well no gsm is normally caused by the wrong baseband, so flashing back to the old one should fix the problem, try to re-flash the stock froyo given in the link on first post and see if that works, and if still no coverage then its a hardware problem and Lg should replace it for you, just dont forget to flash back to stock again if you rooted it, then they should fix it within the warranty.

[Q] How to unlock bootloader on stock ICS (4.0.4) p970g?

I've successfuly gained root on my P970 with the framaroot-1.9.3.apk, and the Gimli exploit, but attempts at flashing a custom ROM led to the dreaded "security error" on boot up, leaving me with a semi-bricked phone. After some hair pulling and messing about with the official LG Mobile Support Tool, I was able to get everything back to stock ICS (4.0.4). In hindsight, I discovered from delving into the low signal-to-noise ratio of this and other forums on the intertubes, that the bootloader of my particular phone is locked, which prevents flashing even if you have root access (as I do).
I'd like to get the CyanogenMod (or other) ROM on my device as LG has dumped support for this device, and there's no official path to KitKat or beyond. Most of the seemingly outdated instructions appear to be geared towards a p970 with Froyo and Gingerbread on it, but I'm stuck with ICS. Also, most tutorials I've come across for unlocking the bootloader suggest starting with that adware bloated "Unlock Root" software for gaining root (which never worked for me) and the "Bootloader Unlocker", which hasn't worked either.
I'm running Linux and have access to Win7's as a VM, which is where I managed to revive the phone from the "security error" issue.
How can I unlock my bootloader, which is based on a stock ICS, with the goal of getting Cyanogenmod on this venerable little device?
Software version: P970g30e-302-220 (is this a 30e bootloader?)
Cheers

The Maker said:
How can I unlock my bootloader, which is based on a stock ICS, with the goal of getting Cyanogenmod on this venerable little device?
Software version: P970g30e-302-220 (is this a 30e bootloader?)
Click to expand...
Click to collapse
The million dollar question.
Most folks (including myself) started with either Froyo or Gingerbread, so we never had a locked bootloader.
Try here:
http://forum.xda-developers.com/showthread.php?t=1111771
http://forum.xda-developers.com/showthread.php?t=1487105
Read through carefully. There are multiple methods; some are complex. If you perform a search on this forum for "security error", you'll get many threads and possible solutions.
I wish I could help more, but it's something I never had to deal with.

androcraze said:
The million dollar question.
Most folks (including myself) started with either Froyo or Gingerbread, so we never had a locked bootloader.
Click to expand...
Click to collapse
Yeah, I made the mistake of "upgrading" my phone via the official LG recovery tool not knowing I was going to lock myself into truely vendor imposed planned obsolescence (although I do understand their position on the whole matter). It also explains why most of the tutorials are geared towards the former two versions of Android.
Try here:
http://forum.xda-developers.com/showthread.php?t=1111771.
Click to expand...
Click to collapse
This solution didn't work for me. Specifically, both the "UnlockRoot" program (which is adware infested bloatware) and the "Unlock Bootloader" tool did not work.
Like I mentioned, I was able to get root access with the framaroot tool, but the Unlock Bootloader tool just sat there saying "Flashing", but it didn't do anything (i.e., the phone sat there as if nothing happened for 30 minutes before I stopped the program). Phone works fine, but wasn't altered in any way that was noticeable.
http://forum.xda-developers.com/showthread.php?t=1487105.
Click to expand...
Click to collapse
This solution appears to patch an older V20 ROM, which I think would be the way to go, but this also didn't work for me. Namely, the SFT tool didn't seem to be able to communicate with my phone. The linked SFT seems to be a little outdated too, being at version "2011-02-26 v 1.2, 1.3".
In both cases, I've got the latest USB driver from LG and the latest official LG recovery tool. Both allowed me to restore my phone to stock settings after getting that "security error", so I know that my phone is at least able to communicate with the OS.
Read through carefully. There are multiple methods; some are complex. If you perform a search on this forum for "security error", you'll get many threads and possible solutions.
I wish I could help more, but it's something I never had to deal with.
Click to expand...
Click to collapse
The "security error" isn't the issue, at least not the primary one now. It's the locked bootloader, which is why I posted this specific thread, which should be fairly generic for those like me in the same boat. So far, the solutions mentioned above and the tools they recommend fail to unlock the bootloader on a stock ICS ROM, which in my case is a V30E ROM (I believe) on a TELUS branded phone.
In any case, thanks for those links. Unfortunately, the solutions did not work for my situation.
PS-is there a proper wiki for unlocking specific phones on the XDA website? Searching through hundreds of pages of often outdated forum posts is so tedious and inefficient. It is great for working through a problem with others though.

Someone said that flashing a Froyo ROM then rooting did the trick. Dunno.

Man I have a problem with my phone(can't flash anything bellow ics) but maybe I can help you. If you have root acces use Bootloader Unlocker tool (trust me it works.....and yeah I know that it doesn't say '"done" or something like that"). After this,download Rom Manager and flash CWM from it(you may have to try a few times before works).Then you can flash a custom rom via CWM. Please tell me if works and if you can flash a Rom bellow ICS.Almost forgot:you can acces CWM from phone turned off via key combo ( hold down G key and VOLUME PLUS and press Power.
CHEERS

[Q] How to go back to stock rom with a unlocked, 30.BC bootloader

Here is the problem.
I updated my xt1058 to 5.0.1 , so my bootloader was updated to the 30.BC version. It still is unlocked and I've TWRP installed too working good. After the update, a few days later using the stock rom, my phone got stuck on a bootloop, even after I wiped everything using TWRP the bootloop continued. In order to continue using the phone I installled the official CM12.1 rom over the stock, did all the wipes and then I could boot and use the phone.
My problem is that CM12.1 isn't fully functional yet, and I get random reboots, signal loss, and some apps crashes the phone and I really wish to come back to stock rom since I miss some stock features. There is a way to do this or I have to wait for a 5.0.1 SBF appear? And there is really no way to go back to stock 4.4.4 because the bootloader update right?
Thanks in advance for the help!

There may be ways that some will suggest using part from one rom, and parts from another... HOWEVER while that might give you what appears to be a "working phone" you may find some features not working, or some bugs that weren't there before because you have mismatched "parts" on your phone. And you will be at great risk for bricking your phone should you take an OTA in the future.
And yes, there is no 100% safe, and "will never brick" way to downgrade, even with an unlocked bootloader. It is why I spent the time writing this -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202 (which includes a collection of links to threads where people did brick trying to downgrade)
At this point, if you don't want to risk bricking your phone, and want to SAFELY get back to a Stock Motorola ROM, you need to wait until we see a leak of the Stock Moto SBF that is the same or newer build than the last update you flashed on your phone. It will bring all parts/pieces of your phone back into line.

So I'll have to wait the SBF, hope it doesn't take too long!
Thanks for the help.

blueflyingllama said:
So I'll have to wait the SBF, hope it doesn't take too long!
Thanks for the help.
Click to expand...
Click to collapse
It takes as long as it takes...
You wont see a 5.1 SBF util sometime after 5.1 starts pushing to ALL PHONES on all carriers, Moto has posted the Developer Images on their web site anywhere from a few weeks to a few months after the OTA update has been pushed. For all other carriers, since MOTO doesn't post/publish them, we are at the mercy of someone on the inside grabbing them and leaking them, so there is no telling how long that might take, and if it will definitely happen.

G870A, Soft Bricked, Need 4.4.4 or 5.1.1 completely stock "Unrooted" firmware file

G870A, Soft Bricked, Need 4.4.4 or 5.1.1 completely stock "Unrooted" firmware file
EDITED 12-27-15:
XDA Assist has sent me to this forum (Thanx). Info and questions follow, here are the basic details:
G870A variant of the samsung S5 (Active)
Stock, unrooted, carrier locked
interrupted power during OTA update from AT&T (most likely 5.1.1)
forced phone into "download mode" and attempted to flash 4.4.2 (NE4) instead of update (actual file used: G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5)
Phone stuck in bootloop with freeze/repeat at AT&T logo
unable to locate completely stock firmware file for 4.4.4 (G870AUCU1AOA1 or OA2) to flash back to most recent functional OS.
still currently able to force recovery mode or download mode.
**update:
As far as i know, the OTA for 5.1.1 did completely download but i dont think it "installed" because i removed battery during initial auto-reboot. The existing ROM would have been 4.4.4 mentioned above, updated and active official firmware from AT&T.
Basic Explanation of actions: I do fully realize that my actions and subsequent "incomplete" attempt to patch the software were unwise but i was merely weeks away from paying off the phone, owning it, having it unlocked by AT&T, properly rooting and installing a custom ROM (as i had successfully done to my wife's G900A). In a moment of panic, not wanting to be locked out of my phone forever by Lolipop, I ripped out the battery during the reboot that was loading Lolipop... every time I put the battery back in and hit power, the phone still attempted to load and write 5.1.1. So I thought maybe, the official firmware copy from 4.4.2, which my phone shipped with in 2014, might flash, even though i was not rooted or unlocked. Clearly i was mistaken but it was all i could think of under pressure.
At this point, I am Completely unconcerned about almost all data on phone or even the hardware EXCEPT for some extensive "memo" notes, which i desperately want to recover. I also dont care anymore about avoiding Lolipop because the memo data is more important to me. I am literally willing to rip the internal memory from this phone and send the SD to a data forensics company if that's what it takes, i no longer care about the phone at all... Having said that, recovering it myself and keeping the phone might be nice also.
Question: where might i find a completely stock firmware for 4.4.4 factory, UN-rooted,to flash; or what procedure might i use to directly pull data from the phone, while soft bricked, before doing a full factory reset?
Alternately, any advice on directions i may not have thought of yet?
I have looked pretty deep into the existing XDA forums for this info but i am only finding "custom ROMs" which are rooted or factory stock ROMS for 4.4.2 and most advice deals with rooting, then flashing. I am not rooting but simply flashing fully unrooted stock firmware AND starting in a bootloop/soft brick state. This is why i did a fresh thread.
Thanks in advance to anyone who might be able to help!

rtlarkin said:
Hello XDA Assist! After reading the stickies, i see that you may be able to direct me to the correct forum in which to post my main question. Here are the basic details:
G870A variant of the samsung S5 (Active)
Stock, unrooted, carrier locked
interrupted power during OTA update from AT&T (most likely 5.1.1)
forced phone into "download mode" and attempted to flash 4.4.2 (NE4) instead of update (actual file used: G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5)
Phone stuck in bootloop with freeze/repeat at AT&T logo
unable to locate completely stock firmware file for 4.4.4 (G870AUCU1AOA1 or OA2) to flash back to most recent functional OS.
still currently able to force recovery mode or download mode.
Completely unconcerned about all data on phone or even the hardware EXCEPT for some extensive "memo" notes, which i want to recover.
Question: where might i find a completely stock firmware for 4.4.4 to flash; or what procedure might i use to directly pull data from the phone before doing a full factory reset?
Alternately, advice on directions i may not have thought of yet.
Thanks a bunch!
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. To get you the expert help you need, I'm going to move this thread to the most relevant Q&A forum for your device. Good luck!

Hello,
I am not an expert or anywhere close but I understand the basics of Android flashing / rooting, etc.
I happened to have rooted my G870A from AT&T successfully using a thread from XDA and I noticed they also provided the original firmware for G870A in case of problems:
http://forum.xda-developers.com/att...to-root-g870aucu1aoa1-4-4-4-2-7-2015-t3025119
So I thought this may help you considering you're looking for an original firmware for your G870A.
What I suggest is to try to flash "G870AUCU1ANE4_Full_Odin.tar" (available from the thread I linked above, I didn't want to rip the links out of the thread) using Odin v3.09+.
I did not use this firmware to root my G870A (only used the updates) but everything worked on the first try.
Follow instructions in the thread I provided. If that still doesn't work, you may need an Android expert on the case.
I wish you good luck in your data recovery. And yes, I registered just to post a reply to your thread.
(also: if you want to root your G870A, the thread explains the proper way to do it!)

Appreciate the thought
dapr0b said:
I happened to have rooted my G870A from AT&T successfully using a thread from XDA and I noticed they also provided the original firmware for G870A in case of problems:
http://forum.xda-developers.com/att...to-root-g870aucu1aoa1-4-4-4-2-7-2015-t3025119
So I thought this may help you considering you're looking for an original firmware for your G870A.
What I suggest is to try to flash "G870AUCU1ANE4_Full_Odin.tar"
Click to expand...
Click to collapse
Really appreciate the thought, however, that particular file is the file that i had originally used before posting. i think since my phone was factory locked and unrooted i did not have the permissions needed to basically "roll back" my phone to 4.4.2 but i am not educated enough to be sure of the exact problem flashing that file.
Thanks again for suggesting it though! I am nearing the time when I will just have to give up and send off the internal memory for physical extraction and data recovery

Hello,
I am also not an expert or anywhere close but I understand the basics of Android flashing / rooting, etc.
With that said: Let the OTA happen. You will not lose the files unless you already started a factory reset. Then your sol. You will not be able to root but you have a better chance of retrieving the files you are looking for. The phone is not like a computer. You can't just pull the HD and sent it out. You either already had the 5.0 kernel or the 5.1 kernel loaded before you stopped the process. This makes it impossible to go back. You can only go forward.
Good luck and let us know how you make out.

re: take the OTA
Sgt.CM said:
With that said: Let the OTA happen. You will not lose the files unless you already started a factory reset.
Click to expand...
Click to collapse
Thanks for that idea. the trouble at this point is that im stuck in a bootloop that catches on the att logo. I agree that the only option now is to continue forward. i just need a fully official software newer than 4.4.4 to load through kies or odin. at least i "hope" the newer file will work.
so far i have only been able to find stock ROMs that are rooted, and i dont think i can load a rooted stock ROM onto a carrier locked un-rooted phone.
The part you mentioned about the kernal is probably true. i had not thought of that before.