Related
I have a Verizon DE moto x that has twrp recovery. My active display keeps getting stuck when I get a notification, so I think I need to flash (or however it must be done) a fresh rooted stock copy. Where can I find info on how to do this?
Sent from my XT1060
Since you aren't downgrading or anything, you won't have to worry about the bootloader, so just grab the Verizon 4.4 SBF and follow the instructions
mastarifla said:
Since you aren't downgrading or anything, you won't have to worry about the bootloader, so just grab the Verizon 4.4 SBF and follow the instructions
Click to expand...
Click to collapse
What is the difference between flashing firmware and flashing factory images?
Cozume said:
What is the difference between flashing firmware and flashing factory images?
Click to expand...
Click to collapse
As far as I know, the only verifiable "factory images" are the Developer Edition ones that Moto hosts on their personal website.
The SBF may/may not be official factory images. However, they are essentially accepted by the community as the next best thing, mainly because the zips follow the rules set by RSD Lite (Insider Moto Tool) and help prevent bad flashes/user error.
Flashing the SBF firmware manually (via fastboot commands) can raise a few problems of its own, if you don't know what you are doing you can cause serious damage to your device, which is why it is safer to use something like RSD Lite. If you are manually flashing, there is no "check" to verify that you installed them in the correct order or that you flashed all the files without missing anything. Therefore, it is much more risky, please know what you are doing if you plan on flashing this way.
mastarifla said:
As far as I know, the only verifiable "factory images" are the Developer Edition ones that Moto hosts on their personal website.
The SBF may/may not be official factory images. However, they are essentially accepted by the community as the next best thing, mainly because the zips follow the rules set by RSD Lite (Insider Moto Tool) and help prevent bad flashes/user error.
Flashing the SBF firmware manually (via fastboot commands) can raise a few problems of its own, if you don't know what you are doing you can cause serious damage to your device, which is why it is safer to use something like RSD Lite. If you are manually flashing, there is no "check" to verify that you installed them in the correct order or that you flashed all the files without missing anything. Therefore, it is much more risky, please know what you are doing if you plan on flashing this way.
Click to expand...
Click to collapse
Just to clarify. Using the rsd lite method will not mess with the boot loader nor the /media folder correct?
Sent from my XT1060
Swimboy46163 said:
Just to clarify. Using the rsd lite method will not mess with the boot loader nor the /media folder correct?
Sent from my XT1060
Click to expand...
Click to collapse
Depends on if you edit the xml file or not. The bootloader will be flashed by default and data will be wiped by default. It's been a while since I've used RSD but I think when it wipes /data it wipes everything (i.e. including /media). That being said, you could always take those steps out of the xml file.
piccit said:
Depends on if you edit the xml file or not. The bootloader will be flashed by default and data will be wiped by default. It's been a while since I've used RSD but I think when it wipes /data it wipes everything (i.e. including /media). That being said, you could always take those steps out of the xml file.
Click to expand...
Click to collapse
Will this work? http://www.youtube.com/watch?v=gDJvZe7_s0E
While yes it will work I would suggest learning HOW it works, take a look at the steps it goes through and see what is happening, don't rely on these kinds of tools, because they become useless if something bad happens. However, if you look at and modify the XML, it is literally only taking out a few lines of code, but if you want an automated version, then use the tool.
mastarifla said:
While yes it will work I would suggest learning HOW it works, take a look at the steps it goes through and see what is happening, don't rely on these kinds of tools, because they become useless if something bad happens. However, if you look at and modify the XML, it is literally only taking out a few lines of code, but if you want an automated version, then use the tool.
Click to expand...
Click to collapse
I can never get adb to run in command prompt. Mostly because windows is different from Mac.
Sent from my XT1060
Swimboy46163 said:
I can never get adb to run in command prompt. Mostly because windows is different from Mac.
Click to expand...
Click to collapse
I have a Windows 7 machine and I can never get adb to run in a command prompt, either. I have a driver problem.
I can only use mfastboot to do anything unless I can fix my driver problem.
Swimboy46163 said:
I can never get adb to run in command prompt. Mostly because windows is different from Mac.
Sent from my XT1060
Click to expand...
Click to collapse
There are a few tutorials for setting it up correctly, I'm not sure that you need the full SDK in order to do this, but I guess it's nice to have anyways. Try reading up a bit about it, I'm sure you can get it running in no time , after that you'll be much more familiar with these kinds of things.
OP, are you on 4.4? if so, then you don't have to worry about the bootloader. Just download the most current factory image from Motorola. The instructions for flashing the factory images are on their website. Go to www.motorola.com, go to the bottom of the page and click on "Developers". Its the same page you went to in order to get the bootloader unlock code. You have to request the factory image, and Motorola will email you a link, or there's several links to it floating around here.
The factory image will have the same bootlaoder version as you have installed as long as your are flashing the same OS version. It won't relock your bootloader, but you will lose root until you flash TWRP recovery. as far as the media partition, just back up your sdcard partition to your computer before flashing the factory image.
Here's the steps:
1. Plug your MX into the computer and back up all files you want to keep (photos, music, videos, downloads, etc...)
2. Download the 4.4 factory image from the source of your choice (If you don't get it from Motorola, make 100% sure you are downloading the correct file)
3. Make sure you have ADB and fastboot set up properly (and make sure you use the motorola fastboot (mfastboot.exe), bot the Google version)
4. Unzip the factory image and place all the files into the same folder as your adb and fastboot files.
5. Boot your MX into fastboot mode (power off, then hold all three buttons for approx 5 seconds and release)
6. Flash the files using mfastboot, and following the order provided in the included xml file.
7. Reboot.
8. Set your phone up and then restore the files you backed up to your computer
9. If you want root, then you will have to go back to fastboot and flash the TWRP recovery and let it install SuperSU.
10. Finally, PLEASE, make a nandroid back up once you have everything set up and before you make any alterations to it.
Thanks guys! The toolkit actually did the trick for me I was being lazy today lol
Sent from my XT1060 using Tapatalk
Swimboy46163 said:
Thanks guys! The toolkit actually did the trick for me I was being lazy today lol
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Thanks buddy for ruining it for everybody. If you would stop being on your rag and complaining like a girl none if this would have happened. Look at what you did little girl.
MOTO X Slapped
I have a Moto X Developer Edition rooted on Verizon with TWRP 2.6.3.1 and stock Android 4.4 on it. I have been trying to upgrade to 4.4.2 without doing the OTA, and without having to reflash TWRP.
So far, I have been unsuccessful.
I have tried Blur_Version.140.45.5.ghost_verizon.Verizon.en.US.zip (approximate file size 150MB) from multiple sources as all the posts I read keep saying that is what works. I have also tried a ~650MB version I found somewhere. In addition, I tried the upgrade located here: sbf.droid-developers.org/phone.php?device=0 which is called VZW_XT1060_4.4.2-KXA20.16-1.25.2_CFC_1FF.xml.zip (It's the 4.4.2 upgrade listed under Verizon US).
All of these fail. In TWRP, about 2-3 steps after it verified md5, it simply says "Failed" with no explanation as to why.
Here is my question:
How can I upgrade to 4.4.2 without a data wipe, and without having to reflash TWRP?
I have no interest in going to a ROM, I want to stay stock, and if I must, I will reflash the recovery if I have to, but I *really* don't want to.
Flash stock recovery, take the OTA, flash TWRP again.
It's so simple, so painless, so quick and it will not wipe your data.
tcrews said:
Flash stock recovery, take the OTA, flash TWRP again.
It's so simple, so painless, so quick and it will not wipe your data.
Click to expand...
Click to collapse
I was hoping to avoid that (Yep, I really am that lazy...) but that's what I was going to do tonight if I couldn't get my hands on a .zip to flash.
Ironically, I bought the Dev Edition specifically so things like this would be easy.
It is easy.....just need to do it.
I support my sister, her husband and my wife (as well as my own) who all have Moto X's. 2 seconds to flash recovery, however long it takes for the OTA to install and reboot and then 2 seconds to flash TWRP again. Heck...I'd just leave the stock recovery in place since it's not needed if you don't plan on flashing any ROMs. The OTA doesn't even remove root.
tcrews said:
It is easy.....just need to do it.
I support my sister, her husband and my wife (as well as my own) who all have Moto X's. 2 seconds to flash recovery, however long it takes for the OTA to install and reboot and then 2 seconds to flash TWRP again. Heck...I'd just leave the stock recovery in place since it's not needed if you don't plan on flashing any ROMs. The OTA doesn't even remove root.
Click to expand...
Click to collapse
Oh, that last bit is good to know! Well, I think even if it did remove root, getting it back is easy on the DE.
I think you're right though, I probably won't install TWRP again, I specifically got the Moto X because I was tired of messing around with stuff when I all I want is a rooted, stock Android experience.
So, after several hours of messing with this, and thinking the stock recovery had gotten messed up because the instructions I had for getting in to it were wrong, I finally got the OTA installing...
and it fails.
I don't know why, I haven't seen the error (I'm not looking at the phone when it fails).
So... Awesome.
Taegost said:
So, after several hours of messing with this, and thinking the stock recovery had gotten messed up because the instructions I had for getting in to it were wrong, I finally got the OTA installing...
and it fails.
I don't know why, I haven't seen the error (I'm not looking at the phone when it fails).
So... Awesome.
Click to expand...
Click to collapse
Are there files out so you can just flash 4.4.2 with mfastboot? Would be easiest.
kj2112 said:
Are there files out so you can just flash 4.4.2 with mfastboot? Would be easiest.
Click to expand...
Click to collapse
I assume so, but I haven't found any instructions specifically saying how to do that, except for the ones that tell you how to return to stock without using RSD Lite.
Unfortunately, I don't know enough about how all this stuff works to be able to figure out which bits and pieces to put together to get upgraded without wiping my data.
What really pisses me off is that I specifically bought this phone so I wouldn't have issues like this, and here I am...
BTW: The only thing the error says is "Error". That's it, nothing else.
Taegost said:
I assume so, but I haven't found any instructions specifically saying how to do that, except for the ones that tell you how to return to stock without using RSD Lite.
Unfortunately, I don't know enough about how all this stuff works to be able to figure out which bits and pieces to put together to get upgraded without wiping my data.
What really pisses me off is that I specifically bought this phone so I wouldn't have issues like this, and here I am...
BTW: The only thing the error says is "Error". That's it, nothing else.
Click to expand...
Click to collapse
This guide has a return to stock section. It will tell you how to flash the stock firmware.
http://forum.xda-developers.com/showthread.php?t=2603358
Unfortunately the moto x is not a simple phone for tinkering with, like say a nexus, even the dev edition.
It can be easier once you do fully understand everything. Just gotta know what applies to you...meaning mostly the locked versus unlocked methods for everything.
After owning an s2, a moto x and now an n5 (n7 too...but I don't tinker with it really....its a family device) I've come to the mind set that for flashers and rooters.....nothing at all beats owning a nexus. Every other device has some limitations that a nexus won't have.
kj2112 said:
This guide has a return to stock section. It will tell you how to flash the stock firmware.
http://forum.xda-developers.com/showthread.php?t=2603358
Unfortunately the moto x is not a simple phone for tinkering with, like say a nexus, even the dev edition.
It can be easier once you do fully understand everything. Just gotta know what applies to you...meaning mostly the locked versus unlocked methods for everything.
After owning an s2, a moto x and now an n5 (n7 too...but I don't tinker with it really....its a family device) I've come to the mind set that for flashers and rooters.....nothing at all beats owning a nexus. Every other device has some limitations that a nexus won't have.
Click to expand...
Click to collapse
Yeah, that's the page I was talking about when I said I found the full instructions...
I specifically bought this phone because I didn't want to mess around with it like this, I just wanted to root it so I could use Titantium Backup and be done with it... and now I'm stuck at a halfway point.... Again...
I'll probably end up just doing the full wipe and manually flash to 4.4.2 (RSD Lite doesn't see my device... yay), since I have gone from my mute button not working (with 4.2.2), to a really bad echo for whomever I'm talking to when it's on speakerphone (Even when speakerphone is muted... THAT made for a fun conference call...).
Taegost said:
Yeah, that's the page I was talking about when I said I found the full instructions...
I specifically bought this phone because I didn't want to mess around with it like this, I just wanted to root it so I could use Titantium Backup and be done with it... and now I'm stuck at a halfway point.... Again...
I'll probably end up just doing the full wipe and manually flash to 4.4.2 (RSD Lite doesn't see my device... yay), since I have gone from my mute button not working (with 4.2.2), to a really bad echo for whomever I'm talking to when it's on speakerphone (Even when speakerphone is muted... THAT made for a fun conference call...).
Click to expand...
Click to collapse
Flashing stock and rooting on an unlocked Moto x is basically the same as a nexus. It really is simple, once you are familiar with fastboot.
I guess there are toolkits that automate everything....like Samsung's Odin, and there's a few for nexus....but it really doesn't help anyone learn. And that's kinda what this hobby is all about.
But, I am sorry you're having trouble. Not sure what else to add. The guides are there, and they work. Usually. I can't think of anything to add to whats already been said.
Hope it works out for you!
kj2112 said:
Flashing stock and rooting on an unlocked Moto x is basically the same as a nexus. It really is simple, once you are familiar with fastboot.
I guess there are toolkits that automate everything....like Samsung's Odin, and there's a few for nexus....but it really doesn't help anyone learn. And that's kinda what this hobby is all about.
But, I am sorry you're having trouble. Not sure what else to add. The guides are there, and they work. Usually. I can't think of anything to add to whats already been said.
Hope it works out for you!
Click to expand...
Click to collapse
I don't think I'm articulating my issue properly. I understand how to do everything in the guides you mentioned, they're a piece of cake. That doesn't solve my problem.
My problem is that I want to get to 4.4.2 WITHOUT wiping my data, but can't do the update via OTA or flashing in recovery. RSD Lite doesn't work either.
The ONLY option I have available to me is to manually push the update with fastboot, which I can definitely do with the instructions provided... But those instructions require me to wipe my data.
I know it's possible to apply the update with fastboot without requiring me to wipe my data, but I don't know enough about the inner workings to know which steps to skip, and which need to be modified, in order to make that happen.
Taegost said:
I don't think I'm articulating my issue properly. I understand how to do everything in the guides you mentioned, they're a piece of cake. That doesn't solve my problem.
My problem is that I want to get to 4.4.2 WITHOUT wiping my data, but can't do the update via OTA or flashing in recovery. RSD Lite doesn't work either.
The ONLY option I have available to me is to manually push the update with fastboot, which I can definitely do with the instructions provided... But those instructions require me to wipe my data.
I know it's possible to apply the update with fastboot without requiring me to wipe my data, but I don't know enough about the inner workings to know which steps to skip, and which need to be modified, in order to make that happen.
Click to expand...
Click to collapse
It says right at the bottom of the return to stock section in the guide I linked too.....you can skip
Fastboot erase user data
fastboot erase cache
Though if you have any problems after, you might have to do it again and do erase those, before spending time trying to figure out what's wrong.
kj2112 said:
It says right at the bottom of the return to stock section in the guide I linked too.....you can skip
Fastboot erase user data
fastboot erase cache
Though if you have any problems after, you might have to do it again and do erase those, before spending time trying to figure out what's wrong.
Click to expand...
Click to collapse
Wow... Attention to detail -5
Sorry about that, when I looked through that article, I skimmed through and saw that the "Return to Stock" section was (almost) identical to the other instructions I was reading...But I missed that last paragraph when I looked at the link you provided, the directions I was using referenced that article but did not include that last bit...
Thank you for your patients, I feel like a dumbass now *sheepish grin*
Taegost said:
Wow... Attention to detail -5
Sorry about that, when I looked through that article, I skimmed through and saw that the "Return to Stock" section was (almost) identical to the other instructions I was reading...But I missed that last paragraph when I looked at the link you provided, the directions I was using referenced that article but did not include that last bit...
Thank you for your patients, I feel like a dumbass now *sheepish grin*
Click to expand...
Click to collapse
No worries!! .
And sorry, its userdata. My keyboard split the words up.
---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------
And, you may very well have issues doing that way. But its worth a shot first. If you do have issues, then you can erase those and repeat the process.
if using fastboot/mfastboot, I would still erase cache, as it doesn't touch your data/apps/config.
Another tip, use this mfastboot -> http://mark.cdmaforums.com/X-STUFF/Mfastboot-4.4.zip
or you can use RSDlite to flash the SBF, but there is a corresponding line for "erase data"
Two helpful links that will help explain what you saw...
Taking the OTA -> http://mark.cdmaforums.com/MotoX-OTA.html
various ways to Return to stock -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html
kj2112 said:
No worries!! .
And sorry, its userdata. My keyboard split the words up.
---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------
And, you may very well have issues doing that way. But its worth a shot first. If you do have issues, then you can erase those and repeat the process.
Click to expand...
Click to collapse
Alrighty, well I was able to successfully flash to 4.4.2 using the Fastboot instructions. Flashed TWRP afterwards and got root right back. Now that I know, this won't be a trial in the future (fingers crossed!)
Thanks for your help and patience
This is NOT a how-to or anything. Don't try to follow in my footsteps of stupidity and brick your phone.
That being said...
XT 1060 (Verizon)
I have been running 4.4.4 for quite a while now. Right after JCase released sunshine for our phones. (I have an unlocked bootloader.)
I had it rooted, and tried out the 5.0 ROMs a while ago. Flashed back to stock to wait for the update when we heard it was coming "very soon". But tonight I got impatient and decided I was going to re-root and switch back to CM12. So, I opened Moto X Toolkit (love that tool) and installed TWRP. When I manually rebooted I forgot to boot into recovery. Don't know if that had anything to do with the ensuing problems or not, but after that, I couldn't get it to boot into recovery.
So, I flashed back to stock 4.4.4 again. Tried rebooting into stock recovery... no joy.
So off I go again... one more attempt to flash stock 4.4.4. This time, when it asked me if I wanted to reboot into bootloader or android, I tried to boot into android. Sadly I missed the "a" and typed "ndroid". The toolkit began doing something... looks like it was running the flash all over again. I let it do its thing, then very carefully typed "android" so I wouldnt screw it up again.
It rebooted perfectly, but once it was up and running, I noticed all of my icons were blue. I quickly jumped into the "about phone section and noticed it said "4.2.2".
This is not supposed to be possible, so at this point I was half panicking and half curious... so I decided to do an even more stupid thing and accept the updates.
I am now updated completely to 4.4.4. Zero issues... recovery works fine, radio is fine, wifi and BT are fine.
This leads me to two questions (Directed to developers)...
1) Is there a possibility this is repeatable?
2) My curiosity is about to get me into trouble... I have two more Moto X's that are 4.4.4. Locked BL. I would like to know what the worst case scenario is. I know there is a possibility of "bricking", but that term has not, for a long time, meant what it originally did. How badly "bricked" might it be? Bootloops? Chance of recovering by flashing stock firmware or RSD? Or truly bricked?
You are lucky you didn't bricked it by installing ota
updates. Whatever you do please don't install any ota updates. Simple wait for the sbf and manually flash it with rsd. Don't even even attempt to downgraded
I know I got lucky, but that didn't answer either of my questions.
I wouldn't try to repeated it if I were you. Go to moto x bricked phones thread and read the comments. That will satisfy and answer your questions http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
Fadelight said:
This leads me to two questions (Directed to developers)...
1) Is there a possibility this is repeatable?
2) My curiosity is about to get me into trouble... I have two more Moto X's that are 4.4.4. Locked BL. I would like to know what the worst case scenario is. I know there is a possibility of "bricking", but that term has not, for a long time, meant what it originally did. How badly "bricked" might it be? Bootloops? Chance of recovering by flashing stock firmware or RSD? Or truly bricked?
Click to expand...
Click to collapse
1) I would NOT try to repeat it. You are lucky.
What likely happened is the toolkit flashed 4.2.2 via mFastboot, errored on GPT.BIN and Motoboot.img, and continued flashing the rest. Taking an OTA in this state USUALLY bricks the phone, however we have seen a few, like yourself, who reported it didn't brick.
Due to the sheer number of people and threads from those who have bricked doing this, the warnings have been... do NOT try it unless you don't mind if you turn your phone into a paper weight!
To be safe at this point, I would consider downloading the Verizon 4.4.4 SBF, and re-flashing it using Option 5 (and its pre-reqs) at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html to make sure everything is back to stock/consistent. Its your choice if you don't want to.
2) Worst case is you turn your phone into a paperweight.
Some have screwed it up very badly but have been able to recover following these instructions -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057 It is the last resort. You'll also see many in that thread who followed those instructions and were unsuccessful, leaving their phone unusable.
We've also seen a few who were able to reflash the latest rom (currently 4.4.4) via mFastboot, with a few "extra" commands and have been able to recover, but that is a very small number compared to those who have bricked.
That's the odd thing... it DIDN'T error on anything. I would've thought the same thing... error on motoboot and gpt.
I don't mind screwing up a phone and taking a day or two to get it back to operable. As long as there is a way to fix it, I'm good. I just don't want to completely brick the phone. That's why I asked if people meant truly bricked or the new standardized "bricked" which usually means nothing more than having to RSD.
Fadelight said:
That's the odd thing... it DIDN'T error on anything. I would've thought the same thing... error on motoboot and gpt.
I don't mind screwing up a phone and taking a day or two to get it back to operable. As long as there is a way to fix it, I'm good. I just don't want to completely brick the phone. That's why I asked if people meant truly bricked or the new standardized "bricked" which usually means nothing more than having to RSD.
Click to expand...
Click to collapse
I haven't used that tool kit. I do everything manually. So I don't know exactly what processes it runs, or what steps it takes when flashing. IF while flashing it does try to flash all parts, it should have given an error on GPT.BIN if it tried to downgrade, but at the same respect, if its a batch file that just runs the fastboot commands one after the other, if fastboot errors, it will just go to the next line in the bat file, so unless you are paying attention and watching it from start to finish, you could have missed the error.
Another possibility would be if you, or someone who had your phone, upgraded to 4.4.4 by flashing only system.img, and the older bootloader and partition table remained on your phone, then attempting to "downgrade" would not have failed (depending on the bootloader/gpt.bin on your phone).
As said... there are enough that have NOT been able to recover their phones, even after following the instructions in -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057 which are usually the last resort.
Yeah, the second it started running again after I typed "ndroid" by accident, I was in full-on panic mode, so my eyes were glued to the phone and the computer. I saw them flash.
As far as upgrading, I was on 4.4.0 until Sunshine was released... at which point I unlocked my BL and took all of the OTA updates. So it was on full 4.4.4.
This is the oddest thing I have seen in a long time. I was tempted to send a DM to JCase and ask him, but I figured that would probably go over like a fart in church.
Hey everybody,
I was on CM14.1, no issues, but decided to flash back to 6 and made the stupid mistake of trying to go straight with the standard motorola image. Now I am able to load the bootloader mode but cant do much after that. None of the partitions work, nor I can get data from bootloader info (tried retreieving flashing info to no avail). I am trying to find something I can use. Anyone has a suggestion?
Would you mind detailing which steps you took to flash? I think I know what your problem is, but I want to be sure first.
zstricky said:
Would you mind detailing which steps you took to flash? I think I know what your problem is, but I want to be sure first.
Click to expand...
Click to collapse
Sure!
- Got unlocked bootloader and installed cm14.1
- Decided to revert back to stock so downloaded 6.0 system image.
- instead of deleting the got.bin line from flashfile.xml I went to rsd and tried flashing it. It errored out and this took me where I am.
There is a flashable stock rom zip, but assuming you want to just use the official image that you already have you'll need to flash with fastboot. I saw that you posted on the thread 'return to stock etc'. Follow those fastboot steps, but be aware that there is a major omission: the instructions only go to system.img_sparsechunk.8, but there are 9 of those files and the phone will not boot if you only flash 8. As you go through fastboot flashing I think there will be a couple files that will give errors. Do an internet search on the error output line, but if I remember correctly the files that won't flash are no big deal and didn't affect my phone when I went ahead and ignored the errors.
I did man... The problem is... Something trully god messed up here. I am now getting hard stops related to aboot failures. I saw something similar on the xt1033 forums but we miss those same files.
Hi everyone,
Please forgive any n00b questions.
I got started with rooting / custom ROMs on a Nexus 4, and I didn't realize at the time that this made things really easy and I didn't need to learn very much about how everything worked. Fast forward to last week -- I decided, at long last, that I was tired of using stock MM on my T-Mo G4 / H811. How hard could it be? Probably not much different from playing on my old Nexus 4 right? Lol, maybe not.
So now 72 hours later, my phone is hard bricked and will not enter download mode. and I need some assistance, if anyone would be so kind.
I will try to recount what I did:
To start with, I was using a Mac, so I used Homebrew to install Android platform tools / ADB.
I decided I wanted to try out LineageOS so I went ahead and followed their very clear steps (on LOS wiki) to unlock the bootloader install TWRP. However, TWRP doesn't seem to have an official build for the G4(!) so I had to look up and use one of the betas from this post. Is this where I went off the rails already? [Of course, very stupidly I also failed to make a complete backup of anything before going on ahead. Rookie mistake.]
After unlocking bootloader and flashing my TWRP beta, I was able to boot into TWRP just fine. I followed the normal prescribed steps of doing a Wipe (normal TWRP defaults -- system, cache, etc.?) before flashing the latest LOS nightly (14.1-something) and also the nano-x64 variety of gapps. I rebooted and got stuck with the LOS boot animation. I let this go for 55 minutes, so I am pretty sure it was an actual bootloop, not just the 1st-time-startup and optimization going on.
I rebooted into TWRP and decided to try a different ROM to see if that was the issue. So I wiped again, flashed another ROM (I believe it was a flavor of AOKP 14.1.x), flashed gapps again, and gave it another try. Again got stuck with an endless bootloop (45 minutes).
Since this is my daily driver, I decided to go back to stock. Found this thread, downloaded the MM-debloated zip, pushed to phone, and again Wiped + Flashed. This time, when I hit reboot, my phone was immediately hard-bricked. No startup screen, no nothing. That was quite unexpected. Also, the first time I had ever HARD bricked a device that I was playing with. Yikes!
Since then, I got a hold of a PC, and have been trying to revive the device by flashing an image to the microSD and booting into Download mode, in the form of this thread or this one.
I did get this to work briefly yesterday, or at least I got to Download Mode / Firmware Update screen, and then attempted to run LGUP with the KDZ file. However I ran into an error at about 9%, and couldn't continue -- and then I had to give back my loaner PC for the day. I also noticed that the LG Mobile Support tool was recognizing my phone NOT as an H811 but as something like HX230 or ... whatever it was, it was definitely wrong. Which is worrisome.
Today I'm giving it another try but my phone will not enter Download Mode at all, nor respond in any other way. I'm curious if this is a battery issue? So I am simply charging it for the time being. I also re-formatted the microSD and re-flashed the single .img just to be safe, but still can't get a response out of the phone. On my PC's device manager it is showing up as the common Qualcomm 9008 that a lot of people seem to have seen. No recognition from LG Mobile Support tool, nor from LGUP.
So ... what now?
It's possible that once my battery gets some charge again, maybe I'll be able to enter DL mode. Let's hope so.
However, I am also totally in the dark about which software version I should be using. 20i? 20p? I have no idea what these refer to, and I did not make any prior notes to capture the state that my phone was in before this all began. So IF I get to DL mode I will definitely need further instruction on the CORRECT KDZ FILE to be flashing. Else I will just compound my problems.
ANY tips or suggestions will be appreciated! Thanks so much.
Should have verified being on 20o firmware
Upon further reading, quite obvious, at the top of this thread, I definitely should have followed the Prerequisite steps. I did NOT verify that I was on 20o firmware. "OR RISK BRICKING YOUR DEVICE" is right.
So I bricked my device, in exactly the way I was warned not to do, it seems.
Still, what's the next step? Any thoughts?
freeradical426 said:
Upon further reading, quite obvious, at the top of this thread, I definitely should have followed the Prerequisite steps. I did NOT verify that I was on 20o firmware. "OR RISK BRICKING YOUR DEVICE" is right.
So I bricked my device, in exactly the way I was warned not to do, it seems.
Still, what's the next step? Any thoughts?
Click to expand...
Click to collapse
try search for a fix if not may be @steadfasterX knows how to help you.
Re: searching for unbrick solutions
raptorddd said:
try search for a fix if not may be @steadfasterX knows how to help you.
Click to expand...
Click to collapse
Thanks, I have been looking around for solutions, but can't seem to find anything aside from the unbrick-guides that I've already listed / already attempted.
Will hope for help from @steadfasterX ! Or some other knowledgeable / benevolent party.
freeradical426 said:
Thanks, I have been looking around for solutions, but can't seem to find anything aside from the unbrick-guides that I've already listed / already attempted.
Will hope for help from @steadfasterX ! Or some other knowledgeable / benevolent party.
Click to expand...
Click to collapse
Ok what was the last KDZ file you flashed which had worked? 20o?
As you have hard bricked your device you can try the sdcard method again if it works flash 20o again (of it it was 20o).
If you flash a lower version you will hard brick again.
If the sdcard doesn't work anymore for you you can try to flash with QFIL but beware to use the right one. If you use the wrong one it will convert your device and believe me that's not what you want. I can share the good ones but unfortunately maybe on next week first.
Otherwise search on your own for 9008 unbrick but check the md5sum of the programmer!! Compare it with the Evil one mentioned in my ARB list here: http://tinyurl.com/antirollg4 and DO NOT USE THE EVIL one..
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Ok what was the last KDZ file you flashed which had worked? 20o?
As you have hard bricked your device you can try the sdcard method again if it works flash 20o again (of it it was 20o).
If you flash a lower version you will hard brick again.
If the sdcard doesn't work anymore for you you can try to flash with QFIL but beware to use the right one. If you use the wrong one it will convert your device and believe me that's not what you want. I can share the good ones but unfortunately maybe on next week first.
Otherwise search on your own for 9008 unbrick but check the md5sum of the programmer!! Compare it with the Evil one mentioned in my ARB list here: http://tinyurl.com/antirollg4 and DO NOT USE THE EVIL one..
Click to expand...
Click to collapse
Thanks very much for the guidance! The post that you linked to REALLY helps. Until now I really was not sure what 10n, 20i, 20o, etc. referred to, aside from just various software versions. Having a definition for anti-rollback and further links to explain, really helps! This gives me more information and I might be able to self-resolve from here. I will give it a shot.
As for your question ... unfortunately there was NO instance where I flashed a working KDZ file, and I didn't know (due to my past experience with my Nexus) that I needed to check the STOCK software version of my phone before beginning to play with ROMs. In other words, I have no idea if I was on 20i, 20o, 20p, etc. From what I understand, this makes things a lot more difficult
Having looked at the linked thread just a little bit, it appears that using a 20o KDZ is the best bet -- because I bricked my device using a 20i ROM so I expect it was due to violating the anti-rollback restriction.
I will look into it more closely and come back if I hit another brick wall. Thanks so much!
If anyone cares, here are the ending results of all this ...
#1 Be wary of anti-rollback restrictions before you flash anything to your G4. You WILL brick your phone!
I tried multiple rounds and multiple variations of all the MicroSD card methods that I could find. I could NOT succeed in unbricking my phone.
#2 Luckily ... I was able to convince LG that I was still technically under warranty!
Because I had the stock bootloop issue in May 2017, LG did an in-warranty repair for me, and replaced the motherboard. So last week, I simply told them "my phone is AGAIN unable to charge and will not power on, just like in May". Since it had only been 5-6 months since the first issue, they agreed to replace the motherboard again.
Moral of the story: you can definitely unbrick your phone by having LG replace the mobo XD XD
From here, I think I will just totally avoid doing any rooting or custom ROMs on my totally-stock G4 coming today in the mail. I will cross my fingers and hope we get OEM Nougat in the USA sometime in the next couple of months.
Thanks again for the help everyone!