Database Develop

EMEI is 00000000 after upgrade to 4.3, what is my next step

Hi there,
I have searched high & low on the interwebs for a possible solution to my problem but have yet to yield any significant results.
I was on 4.2.2 Stock, Rooted, with bulletproof, and I had started to get random reboots and then 4 nights ago during the night it decided to get into a reboot loop. It would power up for about 20 mins and then restart again & again so when I woke up it was super hot.
So I thought it was time to update it to 4.3 now in the hope that this would resolve the issue but it didn't. I obtained the relevant RUU (Guru Reset M7 2.24.980.2 for HTC__039) from htc1guru and since I was only wanting to get the OTA in the hope that this would fix any other software issues, I only flashed the recovery. I then proceeded to do the large OTA update. This was successful. Then the reboots started again.
Time for a factory reset now, (which I realise I should have just done in the first place) but after setting up my details in the phone I am unable to get network over 3G/4G and when I go into look at the APNs, it says that no sim card is installed when it definitely is. When I go into Phone Info, it states that my EMEI is 00000000.
After looking around for what feels like hours, I read somewhere that I might need to flash the radio but I only have the radio from the previous RUU(Guru Reset M7 2.24.980.2) or can I use that since I can not find anything around RUUs for 3.63.980.2.? I don't want to make the situation any worse than it already is.
I am hoping that there is a simple explanation and fix & any help or guidance would be much appreciated.
Thanks in advance :good:

So you think the problem is that your software is upgraded and not your firmware? If so, you can solve that by dowgrading your software. If you can't find an updated RUU (nothing except a signed file from HTC should be called a RUU), there is still a solution:
- Find a system dump from a phone that is your CID and the version of Android you want. It will be a CWM or TWRP backup.
- Flash the appropriate custom recovery.
- Push the files to your phone in the appropriate directory (you may need to make a backup just to see what the right directory is).
- Restore the backup you just pushed to your phone.
Then factory reset and install the stock recovery. You may need to re-lock the bootloader (I'm not sure). Try to get the correct OTA. If you can't find it, try to download one and save as /sdcard/update.zip. Use the stock recovery to flash it. (You'll need to search for instructions on how to do that. It involves key combinations.) Finally, unlock the bootloader, make a backup, and (optionally) root. Don't install a custom kernel. If your problem persists, you likely have a hardware problem.

Thanks for your reply.
I have no idea if its software/firmware but its showing its on 4.3. I was speculating on the radio possibly needing to be reflashed due to one comment I read on a forum I randomly came across?
So I could use my very first backup I used through TWRP and push that to the phone?
While I am fairly new to Android(had to switch for the HTC ONE), I have been around idevices for a long time and have learnt to always keep multiple backups just in case
I left the bootloader unlocked as most guides say that you don't need to have it locked to get the OTA. I actually tried to find the manual OTA file and do it the way you suggested but at the time I had no luck.
I'll see what I can accomplish tonight.

Apologies on the noobness in regards to RUU.
Is it possible to use a RUU for lets say T-Mobile on an international variant? I see HTC released an RUU for T-Mobile for 4.3 but as far as I can see there isn't any others.

[email protected] said:
So I could use my very first backup I used through TWRP and push that to the phone?
Click to expand...
Click to collapse
That's the first thing I'd try, yes. But I'm guessing just as much as you are.

fenstre said:
That's the first thing I'd try, yes. But I'm guessing just as much as you are.
Click to expand...
Click to collapse
Hahahaha Well I trust your guess way more then mine
Would I need s-off to copy the previous backup back onto the phone or would I only need s-off if I had to push something to system(which I do not need to do)?
I tried last night to run rumrunner and it continually failed and basically told me I had 2 different scenarios to resolve it(the following is coming from memory and its very hazy). One was to use a different kernel and the other was to use another ROM, but that wasn't the preferred option.
At work now so will try and restore my original backup tonight at home. Thanks for your help.

[email protected] said:
Would I need s-off to copy the previous backup back onto the phone or would I only need s-off if I had to push something to system(which I do not need to do)? .
Click to expand...
Click to collapse
Sorry for my late response. You only need s-off to flash firmware that is older, for a different phone CID, or modified by a third party. Or to change other hidden partitions, like to modify the "TAMPERED" flag or to change the CID. Unlocking the bootloader is for changing partitions from fastboot mode: recovery, and maybe also system and boot. You do not need an unlocked bootloader to change these partitions from recovery if you already have a custom recovery installed. (You can definitely modify system and boot, but I'm not sure about modifying recovery with a locked bootloader.)

fenstre said:
Sorry for my late response. You only need s-off to flash firmware that is older, for a different phone CID, or modified by a third party. Or to change other hidden partitions, like to modify the "TAMPERED" flag or to change the CID. Unlocking the bootloader is for changing partitions from fastboot mode: recovery, and maybe also system and boot. You do not need an unlocked bootloader to change these partitions from recovery if you already have a custom recovery installed. (You can definitely modify system and boot, but I'm not sure about modifying recovery with a locked bootloader.)
Click to expand...
Click to collapse
No need to apologise, I'm just happy that someone has been able to assist me.
I have used one of my previous TWRP backups, unfortunately I couldn't use my very very first one as it was missing some files, it obviously didn't copy it all across for some reason
I now have my EMEI back (woohoo) but I think the backup I used has something wrong in the kernel as I think it has bulletproof installed. I am going to return it to stock but following a procedure here as I need to return it to HTC as the phone will not read any sim cards. I have tried 3 different sim cards and have also tested them in a firends HTC ONE and they all work in his. SO it looks like I do have an actual hardware issue with the phone which isn't cool just before Xmas.
I already have major withdrawals from being able to play ingress :crying:
Thanks heaps for your help.

[Q] Having trouble upgrading to 4.4.2 stock on Verizon

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

[Q] RUU

Hi, I did a lot of things with my One Mini 2 and I actually really don't know what to do anymore... So much options and yet there always seems to be a problem. Let me explain everything.
What I did:
-flashed a custom rom, then went back to a stock rom of this forum
-flashed the dt2w kernel, it messed up my phone so I then flashed the liberty one, which worked
But with the liberty one I had some memory problems, for exemple I couldn't take screenshots... That's why I decided that I wanted to put my phone just as it was when I bought it, I really hope that's possible, by that I mean having official firmwares etc, therefore being able to do official upgrades from my phone (is that what OTA is?).
I looked on internet and it looks like what I need is RUU, as it includes everything (from what I understood)... I know a lot of threads were made about this, but quite a few months ago, so that's why I'm making a new one, and to make things clear.
Also, I downloaded an official kernel from htcdev.com, but each time I tried flashing it with TWRP, it "failed".
So, if you guys have an answer, solution or, in best case, the actual RUU, that would be great.
Thanx

Linkalex1 said:
Hi, I did a lot of things with my One Mini 2 and I actually really don't know what to do anymore... So much options and yet there always seems to be a problem. Let me explain everything.
What I did:
-flashed a custom rom, then went back to a stock rom of this forum
-flashed the dt2w kernel, it messed up my phone so I then flashed the liberty one, which worked
But with the liberty one I had some memory problems, for exemple I couldn't take screenshots... That's why I decided that I wanted to put my phone just as it was when I bought it, I really hope that's possible, by that I mean having official firmwares etc, therefore being able to do official upgrades from my phone (is that what OTA is?).
I looked on internet and it looks like what I need is RUU, as it includes everything (from what I understood)... I know a lot of threads were made about this, but quite a few months ago, so that's why I'm making a new one, and to make things clear.
Also, I downloaded an official kernel from htcdev.com, but each time I tried flashing it with TWRP, it "failed".
So, if you guys have an answer, solution or, in best case, the actual RUU, that would be great.
Thanx
Click to expand...
Click to collapse
Still no RUU's avaiable as HTC wont release them. your best option is to use TWRP backup and restore.
Original stock backup

Thank you, but my backup kind of disappeared... I saw your post where there was the "HTC Original Backup.zip", I tried to flash but again it failed... Am I supposed to flash it as a backup?

Linkalex1 said:
Thank you, but my backup kind of disappeared... I saw your post where there was the "HTC Original Backup.zip", I tried to flash but again it failed... Am I supposed to flash it as a backup?
Click to expand...
Click to collapse
You need to send it as it is to your phone and use TWRP > restore. choose file and done.

Thanx so much for answering... I uses the backup you told me to. Although I had to use the "install" option instead of the backup one, it now works perfectly! But how do I know if my phone is "official"? Are the upgrades going to be made straight from the phone?

Linkalex1 said:
Thanx so much for answering... I uses the backup you told me to. Although I had to use the "install" option instead of the backup one, it now works perfectly! But how do I know if my phone is "official"? Are the upgrades going to be made straight from the phone?
Click to expand...
Click to collapse
Yes OTA updates should work just fine. just look for updates in settings>about >software update.
you may have one for polaris office.

Hi, I just want to check this too before I screw up wife's phone..
She has CM12 on her phone now as I replaced recovery as well as unlocking bootloader. Now she wants it back to stock as too many things crash on her. I get that I can install your backup but what worries me is that other posts have said you need the stock recovery to allow for OTA updates to work and the link to this no longer works.
She MUST have OTA updates or my balls will be removed, so can you please confirm this, but also explain why.
Thanks (on behalf of my testicles and unborn children!)
(Oh, and she wants it unrooted ant the bootloader relocked)

arm1e said:
Hi, I just want to check this too before I screw up wife's phone..
She has CM12 on her phone now as I replaced recovery as well as unlocking bootloader. Now she wants it back to stock as too many things crash on her. I get that I can install your backup but what worries me is that other posts have said you need the stock recovery to allow for OTA updates to work and the link to this no longer works.
She MUST have OTA updates or my balls will be removed, so can you please confirm this, but also explain why.
Thanks (on behalf of my testicles and unborn children!)
(Oh, and she wants it unrooted ant the bootloader relocked)
Click to expand...
Click to collapse
Stock Recovery
To unroot just lock bootloader:
fastboot oem lock

H811 unbrick help

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!

[STOCK] [H872] [20d] T-Mobile G6 Stock Collection

T-Mobile G6 H872 20D Stock Collection
Based on OEM 20d KDZ. Extracted and Repacked.
DISCLAIMER
Proceed at your own risk. I am not responsible for any damage to your device.
20d Firmware is ARB01
Flashing LAF WILL REMOVE TWRP from your laf partition and restore stock DL Mode
SysBoot ROMs will only work with 20a or 20d bootloaders
FILE BREAKDOWN
The following Zips DO NOT include stock LAF or Recovery
You must flash the provided LAF separately if you wish to go back to stock DL mode.
​
Bootloader: 20d Stock Bootloader ONLY
SysBoot: 20d Boot and System ONLY (Modem, Bootloader not included). These zips are adb sideload compatible.
FullStock: Full 20d Firmware Installation
StockLAF: Individual LAF image for returning to stock DL mode
TWRPLAF: Individual LAF image for replacing stock DL mode with TWRP
Magisk: You know. You must flash this after flashing any of the above packages if you want to stay rooted.
INSTRUCTIONS​
Make a FULL TWRP Backup using 3.2.3. Link to thread is below.
If you are already on my 11g/h or 20a SysBoot ROMs with root and you are able to mount System in TWRP, you should not need to Format Data.
If you are asked for a passcode in TWRP or are unable to mount System, Boot to TWRP and do a Format Data to remove encryption from your device.
Reboot back to Recovery after Formatting in order for TWRP to mount System.
Advanced Wipe - System, Data, Cache and Dalvik
Flash your chosen Zip using TWRP
You must have TWRP on recovery to flash LAF images.
It is recommended that Sysboot Images be flashed AFTER Bootloader or FullStock
If you Flashed SysBoot with Patched Kernel and Root, you are good to go. Otherwise, flash Magisk to maintain root access.
Wipe Cache/Dalvik
Reboot to system.
Your phone may reboot once or twice during the initial boot to system. This is normal.
Your phone may hang a while on the boot logo. This is also normal. If hang persists for too long, hold vol-down+power until phone powers off to reboot.
DOWNLOADS
Stable v1.0
Project Files have been moved to SourceForge​
TWRP 3.2.3 for H872 by @Eliminator74 - Thank you for all the work you have done for the G6!
Magisk + Magisk Manager
Bootloader - md5:d4035f43f0dcf47d818a234077f9e7f1
SysBoot ROM - md5:778994866d440676aea146ac289e3852
SysBoot w/Patched Kernel + Magisk Root - md5:f1398a45581b7ab8a90d48a9c6bed81f
FullStock ROM - md5:ff9d7a22a70abd0caf83377308778fe4
StockLAF - md5:785a64b6b4a25d01df0d25a09c0f6f73
TWRPLAF - md5:f8ea4e93dc417d2d31f5cb8b77530bfa
Please let me know if you run into any problems with them. Thanks!​
Other H872 Projects
H872 11G Stock Collection
H872 11H Stock Collection
H872 20A SysBoot ROMs (Stock and Rooted)
Announcement
I have officially moved to the V30 and no longer own the G6.
I will still be active in this community, but since I don't have the device any longer I will not be able to test any packages or issues that might arise.
All of my current projects have been tested. If anybody runs into problems, you can still let me know and I'll do my best to support my stock packages.
Thanks guys!
-weakNPCdotCom​
XDA:DevDB Information
[STOCK] h87220d, ROM for the T-Mobile LG G6
Contributors
weakNPCdotCom
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.2.3
Based On: 20d KDZ
Version Information
Status: Beta
Current Stable Version: 1.0
Stable Release Date: 2018-10-18
Created 2018-10-18
Last Updated 2018-10-19

@Ken C FYI the 20a and 20d SysBoots are not deodexed, so it might be worth trying 20d to see if your Hotspot works.

weakNPCdotCom said:
@Ken C FYI the 20a and 20d SysBoots are not deodexed, so it might be worth trying 20d to see if your Hotspot works.
Click to expand...
Click to collapse
Hotspot works but no fp sensor flashed 20d bootloader and Sysboot-mroot with a quick wipe (default wipe; cache data and dalvik) I mentioned it in the other thread. Was wondering if I should've flashed the full stock while I was at it.
Everything else works fine so far.
Sent from my LG-H872 using Tapatalk

Ken C said:
Hotspot works but no fp sensor flashed 20d bootloader and Sysboot-mroot with a quick wipe (default wipe; cache data and dalvik) I mentioned it in the other thread. Was wondering if I should've flashed the full stock while I was at it.
Everything else works fine so far.
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
Yeah I'm not sure why that would happen. Sorry about that man. I would try wiping system and cache without wiping data then flash FullStock followed by rooted sysboot. maybe some of the modem related images are causing the problem

weakNPCdotCom said:
Yeah I'm not sure why that would happen. Sorry about that man. I would try wiping system and cache without wiping data then flash FullStock followed by rooted sysboot. maybe some of the modem related images are causing the problem
Click to expand...
Click to collapse
Lol... Dude I noticed today that you and I have conversations spanning different threads.
I wiped everything, flashed full stock and the mroot zip and all seems good so far.
Sent from my LG-H872 using Tapatalk

Ken C said:
Lol... Dude I noticed today that you and I have conversations spanning different threads.
I wiped everything, flashed full stock and the mroot zip and all seems good so far.
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
sweet. should have debloated 20d sysboot posted later tonight

Lol I know I'm being stupid but can someone explain it to me more simply so I don't brick my lg please and thank you

weakNPCdotCom said:
sweet. should have debloated 20d sysboot posted later tonight
Click to expand...
Click to collapse
Not to put you on the spot man. Actually think it's kinda funny but take a look since you seem to be able to, and see if there's a 20e build out. I'm thinking security patch since they always say enhancement. But I was wondering, just wondering, if it's only a security thing would there be someway to get those updates without having to go through all this everytime? I'm not niave to not think there couldn't be something else in these updates I'm just curious what your thoughts on that may be.
Probably better off safe than sorry but noticed that build number last night somewhere. Europe probably so not here yet.
Sent from my LG-H872 using Tapatalk
---------- Post added at 06:41 AM ---------- Previous post was at 06:36 AM ----------
aquinoer said:
Lol I know I'm being stupid but can someone explain it to me more simply so I don't brick my lg please and thank you
Click to expand...
Click to collapse
I don't have time now but I saw your posts from yesterday. I'll look when I get a chance to see what your on about if somebody else doesn't answer your question. If it's a root thing your technically in the wrong thread for that. But I'll see in an hour or so if I can possibly point you in the right direction. What model number are you running? H870, h872,etc. If memory serves me correctly most everything in here should be post root.
Didn't want you thinking you were being left out to dry
Sent from my LG-H872 using Tapatalk

Ken C said:
Not to put you on the spot man. Actually think it's kinda funny but take a look since you seem to be able to, and see if there's a 20e build out. I'm thinking security patch since they always say enhancement. But I was wondering, just wondering, if it's only a security thing would there be someway to get those updates without having to go through all this everytime? I'm not niave to not think there couldn't be something else in these updates I'm just curious what your thoughts on that may be.
Probably better off safe than sorry but noticed that build number last night somewhere. Europe probably so not here yet.
Sent from my LG-H872 using Tapatalk
---------- Post added at 06:41 AM ---------- Previous post was at 06:36 AM ----------
I don't have time now but I saw your posts from yesterday. I'll look when I get a chance to see what your on about if somebody else doesn't answer your question. If it's a root thing your technically in the wrong thread for that. But I'll see in an hour or so if I can possibly point you in the right direction. What model number are you running? H870, h872,etc. If memory serves me correctly most everything in here should be post root.
Didn't want you thinking you were being left out to dry
Click to expand...
Click to collapse
I have h872 I just want to get security patch and have root lol

I'm going to assume that you've already looked into the root thread for the device.
If you have fwul on a thumb drive and know how to boot to it from your pc you really should be good to go. Just to make your life easier put twrp and magisk on your external SD card before you do anything.
Perform the laf switch in lgup.
Go through step 1 in fwul, but when you come to step 2 you'll be better off flashing it manually.
Rooting will put twrp on your laf partition and allow you to access it from there (using the method you used to get into download mode) to flash twrp to recovery and magisk to keep root. Op has these files set to not have to worry about some of this stuff but, first time through I'd want to do it by the book.
Theoretically if you have TWRP on recovery you should be able to flash one of his prerooted roms making the whole mess easier but I've not discussed that option with him. So don't try it unless you're adventurous.
This is from the op and takes place after you do step 1 through fwul (which seems to be all you really need that for)
https://forum.xda-developers.com/showthread.php?p=77811927
Biggest piece of advice I could give you would be to do a dry run of fwul and see what you get. That way you can work out any hang ups before you commit. And get a feel for how it operates.
The dangerous part is where you change the laf on the phone through the patched lgup program and have to do that cord pull deal. It seems to be good at the 10% mark. But to be safe once you get it set to go have the phone in one hand and cord in other. As soon as it goes from laf to the next partition
AS SOON AS YOU SEE IT CHANGE, PULL THE CORD!!!
Then boot into fwul and perform follow step one. Don't worry if unpacking seems to take forever, it jumped to 31% for me and felt like it got hung up. Be patient, like really patient and it'll eventually run through. Then finish out the commands that put twrp on laf.
You could if you want to do the reading, look through anything with my name attached. I had a hell of a time getting things right. Also just in case I missed something.
I'm still waking up but this should be what you need. I screwed it up a bunch of times and was probably lucky with no brick but like I said before it seems the laf switch is the dangerous part. I've been able to recover from everything else.
The link I posted is really specific and may help you more than me telling you from memory. So I'd read that after making sure you got the first part worked out procedure Wise from the root thread itself. (make sure you understand what you need to do for that part) Sometimes it's worth it to read through a whole thread to see the screw ups everybody else made plus there's a video some guy posted that shows it being done. Not to mention I could've missed something by accident.
Also just in case if you've got another sim card device hanging around I'd put the card in that and use it until you get this worked out correctly. Just so in the worst case you've got a working phone to use.
And honestly if anything I posted makes you uncomfortable hold off until you are. Things can be fixed but why stress if you don't need to?
@weakNPCdotCom
Did I miss anything?
Sent from my LG-H872 using Tapatalk

aquinoer said:
I have h872 I just want to get security patch and have root lol
Click to expand...
Click to collapse
I've actually been wondering about the security patch deal myself.
It would be cool if we could do the monthly patch without people being nice and making things easier than they could be. It's not like it's not appreciated But it would be nice to just flash an update if it's only security related and go on with our lives.
Do you think there's any chance in hell this device would see P? The chip would be what 3 gens behind by then?
I just don't see it since it took this long to see O. I mean I've pushed phones further than they say you can with help from this site. But officially I don't see it happening so it's up to people creating roms that have a chance to keep a device longer than that 2 yr cycle. And that hasn't happened yet on this device. I blame that on the year it took to work out root
I did notice the other day that my spare moto X pure can run an 8.0 rom. It needs a new screen and It's running stock now but it's way easier to work on than this thing.
I wonder, with all the different partitions involved now a days if there wasn't some way. On the lines of how we achieved root in the first place. I know there's all the integration within the system and all that but I can dream right?
Can't sleep and that had me thinking
@weakNPCdotCom
Do you have anything you could send me so I can work this stuff out when you move along? I totally appreciate your help and think it's cool that your decent like this, but it doesn't make sense to depend on you like some (myself included) do if your moving on. Ain't gone lie and say if there wasn't something interesting on that newer phone that we could use I wouldn't be interested. But I can't switch phones that often and I'd like to be able to pull this stuff off myself to, if nothing, else keep it updated. There's just not the development that this model could pull off being done and i really don't see it happening. Love aex but I've mentioned why I run stock (gag gag) like I've been.
PM me if your willing, no stress just figured I'd ask. Page of links would be useful. I think I have an idea what your doing but I'm not sure how to achieve it.
Sent from my LG-H872 using Tapatalk

Ken C said:
I've actually been wondering about the security patch deal myself.
It would be cool if we could do the monthly patch without people being nice and making things easier than they could be. It's not like it's not appreciated But it would be nice to just flash an update if it's only security related and go on with our lives.
Do you think there's any chance in hell this device would see P? The chip would be what 3 gens behind by then?
I just don't see it since it took this long to see O. I mean I've pushed phones further than they say you can with help from this site. But officially I don't see it happening so it's up to people creating roms that have a chance to keep a device longer than that 2 yr cycle. And that hasn't happened yet on this device. I blame that on the year it took to work out root
I did notice the other day that my spare moto X pure can run an 8.0 rom. It needs a new screen and It's running stock now but it's way easier to work on than this thing.
I wonder, with all the different partitions involved now a days if there wasn't some way. On the lines of how we achieved root in the first place. I know there's all the integration within the system and all that but I can dream right?
Can't sleep and that had me thinking
@weakNPCdotCom
Do you have anything you could send me so I can work this stuff out when you move along? I totally appreciate your help and think it's cool that your decent like this, but it doesn't make sense to depend on you like some (myself included) do if your moving on. Ain't gone lie and say if there wasn't something interesting on that newer phone that we could use I wouldn't be interested. But I can't switch phones that often and I'd like to be able to pull this stuff off myself to, if nothing, else keep it updated. There's just not the development that this model could pull off being done and i really don't see it happening. Love aex but I've mentioned why I run stock (gag gag) like I've been.
PM me if your willing, no stress just figured I'd ask. Page of links would be useful. I think I have an idea what your doing but I'm not sure how to achieve it.
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
Sorry for the delay in response. So, unfortunately when I tried debloating 20d I ran into a problem with the Calendar app crashing every 30 seconds. I spent hours trying to figure out which app I was removing that was causing that and I couldnt identify the problem. But I plan on revisiting the problem this coming weekend.
I have no problem sharing what I use to repack these.. I'll pm you the details in case you might want to give it a try.

weakNPCdotCom said:
Sorry for the delay in response. So, unfortunately when I tried debloating 20d I ran into a problem with the Calendar app crashing every 30 seconds. I spent hours trying to figure out which app I was removing that was causing that and I couldnt identify the problem. But I plan on revisiting the problem this coming weekend.
I have no problem sharing what I use to repack these.. I'll pm you the details in case you might want to give it a try.
Click to expand...
Click to collapse
Thanks man,
Something I've noticed on the 20d build. The "my places" app has been repeatedly closing. Not crashing and freezing it stops it. But when it would close it would close out settings at the same time.
Not sure if it was me or not. I been tweaking whatever I can. More curious if you'd seen it before yourself.
Saw you pm'ed me so I'll look at that. Feel like I live in a Morton's Salt label at the moment.
Sent from my LG-H872 using Tapatalk

LG G6 H872 - Software version H87220e
Can I install this on my phone I have LG G6 "LG-H872" - Software version H87220e - Kernel 3.18.71
or it has to be 20e?

can the lg g6 h872 be downgraded from h87220e to one with a bootloader for the available twrp for the T-Mobile lg g6?

Whew, so many options
I'm on rooted 20a now, TWRP on recovery and laf -- I want to go back to full stock/factory, INCLUDING laf and lafbak (returning the phone).
Does your FULLSTOCK zip do this, or do I have to flash laf after, or...?
TIA!

usmras said:
Can I install this on my phone I have LG G6 "LG-H872" - Software version H87220e - Kernel 3.18.71
or it has to be 20e?
Click to expand...
Click to collapse
macg13702 said:
can the lg g6 h872 be downgraded from h87220e to one with a bootloader for the available twrp for the T-Mobile lg g6?
Click to expand...
Click to collapse
Versions 11g - 20e are ARB01 and interchangeable. If you are rooted and/or already have TWRP on your phone then yes, you can flash the FullStock zip to downgrade. Otherwise, you will need to follow @runningnak3d 's root procedure which will require the KDZ for whatever version you want to end up on.
BUT.. I will put a 20e collection out for you guys asap.
RashaMatt said:
Whew, so many options
I'm on rooted 20a now, TWRP on recovery and laf -- I want to go back to full stock/factory, INCLUDING laf and lafbak (returning the phone).
Does your FULLSTOCK zip do this, or do I have to flash laf after, or...?
TIA!
Click to expand...
Click to collapse
FullStock does NOT replace your LAF or Recovery partitions. You can go back to stock LAF by flashing the StockLAF zip. However, I do not have any zips for recovery at the moment. I excluded these intentionally so people wouldnt lose all the hard work of rooting.
I dont have a 20d KDZ on hand, but I do have 20a. I can make a 20a recovery zip and add it to my 20a thread. Once it is available, you can put it on your phone's storage and flash it to recovery using TWRP already on your recovery partition (yes, even if TWRP is on recovery it can flash the recovery partition).
I can also include a stock recovery zip in the 20e package Ill be making.

weakNPCdotCom said:
FullStock does NOT replace your LAF or Recovery partitions. You can go back to stock LAF by flashing the StockLAF zip. However, I do not have any zips for recovery at the moment. I excluded these intentionally so people wouldnt lose all the hard work of rooting.
I dont have a 20d KDZ on hand, but I do have 20a. I can make a 20a recovery zip and add it to my 20a thread. Once it is available, you can put it on your phone's storage and flash it to recovery using TWRP already on your recovery partition (yes, even if TWRP is on recovery it can flash the recovery partition).
I can also include a stock recovery zip in the 20e package Ill be making.
Click to expand...
Click to collapse
If I just want to restore everything to factory stock, might it be just as easy to restore just laf from your ZIP, then use LGUP to flash the 20a kdz?
Thanks for all your hard work!

RashaMatt said:
If I just want to restore everything to factory stock, might it be just as easy to restore just laf from your ZIP, then use LGUP to flash the 20a kdz?
Thanks for all your hard work!
Click to expand...
Click to collapse
No problem m8! And yeah, if you want to download the KDZ I would use the patched LGUP that is linked in the H872 root thread

weakNPCdotCom said:
And yeah, if you want to download the KDZ I would use the flashed LGUP that is linked in the H872 root thread
Click to expand...
Click to collapse
Meaning this? LG-H872_Oreo-20a_Bootloader_B1.zip (W/LAF)