Hi everyone, been using these forums for ages, but only recently here. My wife's G8 (RIO-L02 Dual-Sim, Asia-Pacific model) had a smashed screen so I replaced it, and only EMUI 3.1 was available. I've flashed custom ROMs to my Nexus 5 plenty of times with no problems at all.
Unfortunately, while I unlocked the bootloader and rooted my G8 just fine, flashing a Lineage OS14.1 ROM went very wrong, and I ended up in a bootloop. I decided to return to EMUI 3.1 and that also failed for a variety of unknown reasons.
Thankfully, after a day or so of messing around, I managed to find a Thai (Asia-Pacific) RIO-L02 stock ROM package. It wouldn't flash automatically (Force Upgrade method), but I used Huawei Update Extractor to get three .img files (boot.img, recovery.img and system.img) out of the UPDATE.APP file, used fastboot to flash them to the appropriate partitions, and it's back up and running, seems to be going fine. Great!
Now to my question: I've only flashed three of around thirty .img files that were in that Thai RIO-L02 UPDATE.APP. So far, I haven't noticed any issues running the phone, I wonder if that will remain the case, or if there are other important .img files in there that I should extract and flash manually?
Having got an OS going again, I tried using the EMUI Updater to install the whole UPDATE.APP but it failed. That strikes me as a bad thing, but again, no problems showing just yet.
Thanks to everyone who posts here, couldn't have done this without XDA (especially jimgodlike & mooooorz1981 whose posts were particularly helpful)
Related
Hi guys.
This post was made with the intent of help those who are having a hard time trying to update from CM 12 or older versions to CM 12.1.
Inicially I was having the "blkdiscard" error when trying to flash the ROM.
After a lot of searching, I found that the partitions where in a "wrong" format.
So, I tried and tried to change this manually with TWRP, with no success.
Looking in a post about a similar error, I found the answer of ircalf.
I'm posting it here with some modifications.
Italic text means my comments/adds to the guide. Normal text means ircalf comments.
1) The reason why I couldn't flash cm12.1 before was that my /system partition had a different size than what was expected by the cm package.
Apparently, that happens with the e977 original firmware.
So I flashed the european v10h kdz, in order to remake all the partitions in the correct size.
The .kdz file mentioned can be found here (used the V10H Europe Open). I used the LG Tool found here.
My setup at LG Flash Tool 2014 as follows: type 3GQCT, phone mode DIAG, open european kdz mentioned above. Then Normal flash > Start > English language > OK.
At the middle of the process, a connection error was given by the LG Updater, but don't worry and don't click OK at the new window. Just drag it and see that the process still going on.
2) I rooted and unlocked the booatloader again, same as always.
3) I flashed the latest nexus 4 bootloader and philz recovery (personal preferences, don't know if it makes any difference)
Nexus 4 bootloader can be found here.
4) I flashed cm12.1 and gapps, and it didn't boot (went to a black screen right after the bootloader logo)
Here it booted, but the initial configuration app always crashes.
5) I formated the /data and /system partitions and installed cm11, and it booted alright.
I didn't installed CM 11 but I did formated /data and /system. So...
6) I flashed cm12.1 again and it booted.
Didn't worked for me. Same initial config app crash.
Then I installed the latest Kevinjoa build and it worked.
7) I think that cm11 had nothing to do with it. The reason why cm12.1 didn't boot at first was probably because of the /data partition that needed to be formated.
... I also think that.
This process was made on a LG E977 device. I didn't tested on the E975, but probably it works there too.
If you did tested and it worked, please tell me so I can remove the "(not tested)" from the title.
Many thanks to everyone from the mentioned posts, you helped a lot.
Sorry for my bad english. Hope it helps.
Lg g2
After running a very very slightly modified stock room back from 10b (kitkat LG base image with bloatware removed), I finally had enough this past weekend and went looking for a new ROM for my LG G3 vs985.
I tried CM-12 initially, but as it was only nightlies and not a stable, I ended up with a few more problems than not, and they were noted so I moved on. After reading a few things, I decided to go with Resurrection Remix ROM. (I still want to.) After trying a few different times, I moved on to BlissPop, and got a similar-ish error, but it was simply a long overdue modem/radio flash. BlissPop installed fine. It's not exactly performing the greatest, though, so I went back to attempt installing Resurrection Remix.
When I try to flash it, however, I now get the following (somewhat confusing to me) error:
Code:
Comparing BASEBAND version MPSS.DI.2.0.1.c1.13-00053-M8974AAAAANPZM-1 to MPSS.DI.2.0.1.c1.13-00053-M8974AAAAANPZM-1_20140813_223054/b/modem_proc/core/securemsm/mba/src/mba_main.c
assert failed: g3.verifyh_baseband("MPSS.DI.2.0.1.c1.13-00053-M8974AAAAANPZM-1") == "1"
Now, mba_main.c is, at first glance, a compiler file (or code file, but that extension is what my classroom code has had since I started studying). So, I have no idea how to get it to the "right" baseband version.
I am not completely incompetent, thankfully, but I do have a couple of issues that may make it more difficult than I would normally imagine. Fastboot has not once worked with this phone. ADB works just fine, I can (and have) done everything from wipes to sideloads to install from zip files located on internal and external sd with no problems whatsoever. [Given what I have read, I'm going to assume the fastboot issue is related to Windows 8 and leave it at that; I could not get it to work in Linux either, however].
Any assistance would be greatly appreciated, and I hope everyone is having a good day.
Randomly, I resolved this. For anyone having a similar issue:
If you download the modem.zip for 23b and apply it via zip, it returns a lot more than just the baseband version when ROMS query it during the installation portion in TWRP.
The solution is to download the modem.img file from http://forum.xda-developers.com/verizon-lg-g3/general/reference-stock-img-files-t2966958 and then use the instructions in That post (the dd command lines for the modem block device in this case) from an adb shell as root for it to work.
Happy modding everyone
I was needing a new phone and saw a Linus Tech Tips video where he took an LG G3 and put LineageOS on it. So I thought I'd try it out for myself following his guidelines at https://linustechtips.com/main/topic/1058206-lg-g3-lineageos-tutorial/
I bought an LG G3 D851 (T-Mobile version) off EBay for this. It's my first Android phone (yes, experimenting on my first Android Phone), I've always used Windows phones. This is what I've done to the LG G3 so far:
I reverted back to KitKat. Everything seemed to have gone just fine.
Then I downloaded the the Full Purple Drake Root and ran that after I figured out that .gz files are a compressed file and that can be decompressed. Everything seemed to have worked fine.
Then I downloaded the TWRP app on the phone and tried to backup the recovery via the TWRP app, which I'm not sure if it worked correctly. But anyhow.
Now that I'm writing this I see I missed this step:
number seven: Select the TWRP file we copied over earlier in the app, flash it to recovery, and then reboot to recovery
Click to expand...
Click to collapse
I guess I just didn't understand what was meant by flashing it over and has just copied it to the phone's memory which I later wiped.
Well then I went into TWRP recovery and tried to do a recovery backup, which it seemed to do just fine. I rebooted and tried copying it over to the computer, which seems to not have worked. I just have an empty folder on my computer as we speak.
Then back in the TWRP recovery, I selected Wipe>Advanced Wipe, and select Dalvik, Cache, Data, Internal Storage, and System – then swipe to wipe.
Then I downloaded the latest version and nightly of LineageOS zip file and the Opengapps zip file but then had a hard time figuring how to get them to the phone.
I figured out that I could stick them on an SD card and slip it into the LG G3 that I'm working on and could see the files from the TWRP recovery menu.
So I tried to install the LIneageOS zip file several times and it didn't work. I'm guessing it's because I forgot to flash a certain file to TWRP recovery and am not sure how to do that, especially now with the phone only booting into recovery mode with the TWRP menu since it's wiped clean and will just display the LG logo and turn the LED different colors if I try to normal boot the phone.
Well I still want to try to fix the phone and go for LineageOS. I spent nearly all night working on it so I may give it a rest for a few days. But any help or pointers would be greatly appreciated.
Now that I think about it, I didn't do what I mentioned ok #4 above about flashing the TWRP recovery because TWRP recovery was installed with the full Purple Drake root. However, the Linus Tech Tips instructions point to them rooting the phone with the lite version of Purple Drake (root only) and then flashing the newest version of TWRP recovery. So I wonder if my problem has to do with my having the latest version of TWRP recovery on my phone.
Ok. So I think I'm making progress, although that's just a feeling I have since I'm not suite what I'm really doing.
Anyhow the error code was something like "Unknown Error, Error Executing Updater Binary in Zip, Zip is for LG G3 D851, this phone is...(blank)". So I found an article in DroidThunder.com talking about this very problem. It suggested unzipping the rom on my computer and looking for the updater-script file and erasing some lines that apparently only have to do with verification. Then re-zip and retry.
Now I'm getting a "No MD5 file" message followed by an "Error flashing zip" message.
Edit: After reading this I take it I have an older version of TWRP, that is, v2.7.1.0, whereas the newet versio (for this phone?) is apparently 3.3.1-0. That seems to have an effect on this. I wonder if it's possibly to flash a newer version of TWRP onto this bricked phone. Anyhow, I'll have to look into that later. It's time to call it a day.
So recently I've been focusing on these two threads:
[GUIDE] LG G3 D851 Unbrick Qualcomm 9008 Fully Working... Unbrickable D851! by Omar-Avelar
And:
[GUIDE][FIX][DISCUSSION] LG G3 Hard Brick Recovery by l33tlinuxh4x0r
But I can't get either of them to work. I guess the only other thing would be to try to find a ROM, preferably the original KitKat that came with the phone, and hope and pray that I can get TWRP recovery v2.7 to install it.
I have the original as a tot file. But as far as I understand, I need a zip file that's set up for TWRP recovery.
Anyhow, trying to get this phone running hasn't been easy and has made other problems. Now every time I turn on my Surface 3 I have to go through BitLocker authentication. Hopefully turning bcd Test Signing off will stop that. But I'm getting to the point that I'm feeling like giving up.
Well that's it. Last night I found a zip file for the original Marshmallow ROM for my G3. I got it onto the SD card, went into TWRP recovery, saw it install, restarted and...
Now it's hard bricked. I cannot even get into TWRP recovery. The screen won't show a thing. I tried several times to get it into any mode possible, normal boot, TWRP recovery boot, download mode, and that jumping the pins trick, and I can't get it to where I can do something with the phone.
So I'm giving up on all this rooting, custom recoveries and custom ROM stuff. It all seems like a good idea, and I'd love to be a part of it all. But I take it this isn't for me. So I give up.
Thanks to all who have worked on this and have made the helpful forums about these phones! Maybe if I were more competent I would have figured it out.
Well, I said I was giving up. But maybe not. I did give up trying to recover the phone from being bricked and sent it out to a JTAG shop. For about $40 the phone is supposedly fixed and on it's way back.
But when it's back, do I just leave it alone this time, or should I try to get Lineage OS back on it again? Well, this is something that I haven't made my mind up yet. I see where I had made several mistakes when I first tried to get LineageOS on it. Maybe I know enough now that it won't happen again. But at the same time there's no guarantee that I won't me it up again, and have to pay some $40 again to have it unbricked.
SUCCESS!!!
So I got my phone back with stock Marshmallow working. Then I carefully went through every step on the Linus Tech Tips site, including installing the latest version of TWRP, and the next thing I know I'm running LineageOS 16 on my phone!
This is great! It's my first Android Phone and I've got it setup just about perfect! The only thing I kind of miss is Wi-Fi calling. But that didn't work so well on the Alcatel Window's phones I had anyway. But I got all the apps and most of the music I need installed and am ready to go! I also have two batteries, and the original isn't too bad, so I might carry that around as a backup until I'm sure how much battery I'll be using.
I'll be coming back and thanking all the ones who's posts and work have helped me individually. But if you read this and are one of those who have worked on TWRP, LineageOS and anything else that has helped me, Thank You!
Hello everyone! I need some help because i'm out of ideas how to resolve the softbrick on my old phone. First i'll explain how i got it in this state:
So i have 2 meizu note 8 i don't use anymore (one with broken touch and lcd, and the other was perfectly fine), and because of boredom and covid restrictions i had the "brilliant ideea" to mess with them and update to android 10 with GSI treble roms. The original android was flyme os 7.1.6.1 EU. First i unlock the bootloader on both and installed twrp recovery. No problems so far , everything worked fine with flyme os. Then i tried to install gsi android 10 with twrp on one of the phone (the one that does not have the screen broken). I had an error with system partition not mounting , so i did a full format in twrp (cache, data, system,internal storage, boot,vendor) and then i managed to flash it. Android 10 GSI (Havoc Os) booted up but with problems : First i got a message right after boot "There's an internal problem with your device. Contact your manufacturer for details" then the config wizard crashed constantly, but i managed to finish the process and android is working (sort of ).The problem wich i called it soft brick is the fact that wifi, data sim,bluetooth, gps, sound are not working (not detected, nada....).Both IMEI are correctly recognized, but the basic functions of the phone don't work.
Having another identical phone with original firmware, i made a full twrp backup (21 partitions..with system,data,cache, modem,kernel,vendor ....everything) and restored it on the culprit. Flyme os booted up but with the exact same symtoms as with GSI 10. It seems i messed up somewhere so i reverted back to stock flyme os recovery and flashed the original software (update zip form their website). Still the same symtoms. So I went further and got the flyme os files for QPST / QFIL flash tool. Flashed it successfully with QFIL but no improvements. I suspected the modem firmware being corrupt and flashed it separately, but i just can't get it to work.
So any ideas? I have the msm partion table and trying to pull everything with adb root and adb shell from the other phone, and restore it back to the other, but got stuck somewhere....(i'm doing more research).
A short update. Apparently the persist and persistbak partitions got corrupted or formated by me (tho twrp does not have option to format persist). This partition is responsible for calibration data for all sensors and baseband. So that's why i had all these problems.
Right now i'm trying to pull those partition images form the other phone and flash them on the bricked one.
Got it resolved. Flashing persist.img partition resolved all my problems but the IMEI and baseband got deleted .So it was necessary to pull *.qcn backup file from the working phone with QFIL program, manually edit both IMEI within qcn file with HEX editor , adding the right ones, and then restore it in the bricked phone.
Now it's working as it should.
I'm writing this in case someone gets their phone soft-bricked like mine. Hope it helps. It got me 2 full days, researching and testing things out!
Hi, I got the same exact problem after doing the flashing using orangefox, all sensors and camera not working even after flashing the original global rom via Qfil. I have been looking for that persist.img file to help me fix the issue. could you please share the Persist.img file here? you will really help a brother
hi there! i have also the same problem... accidentally formatted all partitions in orangefox recovery, been going through all night in recovering my Meizu note 8 here.. i bricked it and been looking for a firmware everywhere, and now i found a flashable firmware through qspt, im getting the same problem here, i've been looking everywhere to where i can get persist image and qcn, im not sure if my emei is messed up though.. i really need ur help also... i need this phone for my game development progress
Hi! I need the flashable firmware of the Meizu Note 8 7.1.6.1G please. I can't find it anywhere.
X-NeRo-X said:
Got it resolved. Flashing persist.img partition resolved all my problems but the IMEI and baseband got deleted .So it was necessary to pull *.qcn backup file from the working phone with QFIL program, manually edit both IMEI within qcn file with HEX editor , adding the right ones, and then restore it in the bricked phone.
Now it's working as it should.
I'm writing this in case someone gets their phone soft-bricked like mine. Hope it helps. It got me 2 full days, researching and testing things out!
Click to expand...
Click to collapse
can you share file with us?
Moto G Stylus Metro PCS brand:
I'm brand new to this subject so please forgive any ignorance. I'm decent with linux but new to android stuff.
Tried flashing the latest weekly build of OmniROM - now seems to be stuck at boot screen and won't go past. I am coming from latest OTA update from Motorola.
Phone was not rooted prior to starting this.
I also accidentally wiped slot A with my factory image on it (oops).
TWRP did not ask for any decryption key so I ran:
fastboot erase userdata
and this seemed to fix errors that I was getting while flashing with respect to denying access.
What I've done:
-Unlocked bootloader
-Installed TWRP 3.5.0-10 from the g-stylus forum.
-wiped and formatted via TWRP
-flashed 5/23 weekly build of OmniROM
Now no matter what I do or what slot I flash to it will not get past the Omni boot load animated screen. I've run this for almost 2 hours and nothing happens.
Any ideas?
Thanks!
nutsnax said:
Moto G Stylus Metro PCS brand:
I'm brand new to this subject so please forgive any ignorance. I'm decent with linux but new to android stuff.
Tried flashing the latest weekly build of OmniROM - now seems to be stuck at boot screen and won't go past. I am coming from latest OTA update from Motorola.
Phone was not rooted prior to starting this.
I also accidentally wiped slot A with my factory image on it (oops).
TWRP did not ask for any decryption key so I ran:
fastboot erase userdata
and this seemed to fix errors that I was getting while flashing with respect to denying access.
What I've done:
-Unlocked bootloader
-Installed TWRP 3.5.0-10 from the g-stylus forum.
-wiped and formatted via TWRP
-flashed 5/23 weekly build of OmniROM
Now no matter what I do or what slot I flash to it will not get past the Omni boot load animated screen. I've run this for almost 2 hours and nothing happens.
Any ideas?
Thanks!
Click to expand...
Click to collapse
Weekly builds may be unstable. I'm actually curious on how you got a hold of such build for the this device. Most, if not all ROMs are unofficial for the stylus and updates for each rom varies by contributed developers.....
However, you say you're decent with Linux. I'm sure there's some developers here that would help you with various tools to learn on how to make your own version of any type of OS.
As for OmniRom, I'd probably ask @vache for some help, for he has his own unofficial version.
Also, I recommend that you have the latest platform tools and the moto software tool if you don't have these yet...
nevermind I got it working. I was flashing p2pstate.bin directly (somehow this works?) when instead I was supposed to extract the image files and flash the respective files.
Seems to boot up now. Thanks!
nutsnax said:
nevermind I got it working. I was flashing p2pstate.bin directly (somehow this works?) when instead I was supposed to extract the image files and flash the respective files.
Seems to boot up now. Thanks!
Click to expand...
Click to collapse
That's good you got it to work. One developer once told me, when all else fails, think outside of the box. You'll eventually get it to work somehow
I have your solution cuz I went through the same thing.. you have to start out with stock Android 10 so you have to be bootloader unlocked and rooted that way you can downgrade your software and it's only the super images that you have to downgrade.. so just flash your supers and you'll be fine but they have to be stock Android 10 it doesn't matter what firmware version because you're keeping the same modem file