Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I MEAN NO HARM AND DON'T WANT TO FLOOD THE FORUMS BY CREATING ANOTHER THREAD. I COULDN'T FIND A CLEAR TUTORIAL FOR REVERTING BACK TO ANOTHER ROM FROM H2O 2.5.1. SO I MADE THIS.
MY ORIGINAL POST OnePlus Forums
Just wanted to let know that I managed to revert back to CM 14.1 Official & OOS 3.1.0 without problems!
First make sure you have a terminal made EFS backup & TWRP made /persist backup!
Make sure you have made those before you flashed H2O 2.5.1.
If you don't have a valid backup, I really don't recommend following my steps in any way!
WARNING DO NOT FOLLOW MY STEPS IF YOU DON'T KNOW WHAT YOU ARE DOING!
IF YOU IGNORE THIS AND DON'T HAVE BACKUPS, YOUR PHONE WILL BE NOTHING MORE THAN BRICK!​
WHAT I DID
- Make sure you have a custom recovery. I'm using HybridRecovery_v3.4.imghttp://forum.xda-developers.com/one...0-2-hybrid-supports-oos-t3362904/post66466393
- Make sure that OEM unlock is enabled under developer settings in your phone.
- Make sure that ADB debugging is enabled under developer settings in your phone.
- Connect phone to PC and grant permission to communicate with your phone.
- Grab your modemst1.bin & modemst2.bin files and put them in the same directory where ADB is installed/unpacked.
- Boot phone in bootloader/fastboot
- Start a new ADB session
- fastboot devices
- Check if any device is recognized
- This is the moment where you still can return to H2O.
Side note: H2O 2.5.1. is a fine OS and worked great for me. Maybe I'll return to it some day, but for now I'll be using CM 14.1
LET'S BEGIN
- Fastboot erase modemst1
- Fastboot erase modemst2
- Fastboot flash -S 512M modemst1 modemst1.bin
- Fastboot flash -S 512M modemst2 modemst2.bin
- Unplug your phone and then turn it off you by holding the power button
- Boot your phone into recovery
- Restore the /persist partition with TWRP/HybridRecovery
- Flash a ROM
One thing to mention is that when I restored a backup of CM 14.1 my data connection seemed forever lost.
I managed to fix that by deleting my network settings in the "Settings" app of Android. I also rebooted in recovery and deleted Dalvik/Art cache & cache.
Reboot your phone to system.
Voila, your phone is reverted and both of the IMEI's are still intact!
Any questions? I'll try to answer them as quickly as possible!
Restore the /persist partition with TWRP [NEW STEP]
how???
aliasgertaj said:
Restore the /persist partition with TWRP [NEW STEP]
how???
Click to expand...
Click to collapse
install Hybrid TWRP and then you will see the option. Search the forum for it. You'll find it
aliasgertaj said:
Restore the /persist partition with TWRP [NEW STEP]
how???
Click to expand...
Click to collapse
-Do you have a backup from your whole system made in TWRP?
-Do you have the modem files backed up via terminal?
If both are yes, you can follow my steps.
If not, stop.
aliasgertaj said:
Restore the /persist partition with TWRP [NEW STEP]
how???
Click to expand...
Click to collapse
Thread HybridRecovery (Use the 3.4 Version)
http://forum.xda-developers.com/one...0-2-hybrid-supports-oos-t3362904/post66466393
ok thnx dude
Stupid question whats the command to backup the modem
MRDICKHEAD said:
Stupid question whats the command to backup the modem
Click to expand...
Click to collapse
Not my video, but here you go!
Just FYI, I flashed back to OxyGenOS 3.1.0 and it works perfectly fine!
The last numbers proof it.
I've cut away the other part of my screenshot due to privacy.
Tunatje said:
Not my video, but here you go!
Click to expand...
Click to collapse
Thanks
Hi,
Thank you for your thread.
I am assuming this tutorial won't apply if I already erased my modemst without taking a backup? Because if I were to backup anything now it would just be an empty file?
rajatdixit said:
Hi,
Thank you for your thread.
I am assuming this tutorial won't apply if I already erased my modemst without taking a backup? Because if I were to backup anything now it would just be an empty file?
Click to expand...
Click to collapse
So sorry to hear that. Indeed, you will have a empty file.. You never made a Nandroid backup? If not, this is a hard lesson you have learned to read always the threads about flashing stuff for the first time. It's always mentioned that you have to make sure you have a full Nandroid backup.
Tunatje said:
So sorry to hear that. Indeed, you will have a empty file.. You never made a Nandroid backup? If not, this is a hard lesson you have learned to read always the threads about flashing stuff for the first time. It's always mentioned that you have to make sure you have a full Nandroid backup.
Click to expand...
Click to collapse
No, unfortunately I didn't. Yes its a hard lesson. I only have 1 IMEI working now.
Thank you for your input
I tried this one and it actually worked
http://forum.xda-developers.com/oneplus-2/general/howto-revert-firmware-hydrogenos-2-5-to-t3512065
please help...
i flashed into h2os for volte in mu oneplus two and then i flashed cm official 14.1 but then my phone started frequenlt rebooting . i though that might be a rom bug so i flashed rescuration remix rom but then too my phone is frequently rebooting . please help me tired of this. give me step by step solution for this. thank you.
.bin file Copy Paste ???
I dont know this is a proper Question (If not I m Sorry)
My other OPT have RR rom (before H2OS 2.5) is there any way that can enable me to copy .bin file from the other OPT & get both sim working.
Please Help
TIA
Sunil Jagtap said:
I dont know this is a proper Question (If not I m Sorry)
My other OPT have RR rom (before H2OS 2.5) is there any way that can enable me to copy .bin file from the other OPT & get both sim working.
Please Help
TIA
Click to expand...
Click to collapse
You mean, duplicate the IMEI?
Tunatje said:
You mean, duplicate the IMEI?
Click to expand...
Click to collapse
No, I mean can, I edit it with what no. my OPT has before.
Or
how can, I revert back to H2OS 2.5 with both sim working, tried every thing but after boot only SIM 1 is working
Thanks in Advance
Sunil Jagtap said:
No, I mean can, I edit it with what no. my OPT has before.
Or
how can, I revert back to H2OS 2.5 with both sim working, tried every thing but after boot only SIM 1 is working
Thanks in Advance
Click to expand...
Click to collapse
Hi,
You can't edit a IMEI. At least, not that I'm aware of. I've read that people used a HEX editor but not sure how that works or how much time that costs.
My thread is only for people with a modemst1.bin/modemst2.bin backup made through terminal..
However, there is a new guide for people without a backup, but think it's applicable if you haven't used the "erase" command.
https://forums.oneplus.net/threads/...r-flashing-hydrogen-os-video-included.477463/
rrbjerry said:
i flashed into h2os for volte in mu oneplus two and then i flashed cm official 14.1 but then my phone started frequenlt rebooting . i though that might be a rom bug so i flashed rescuration remix rom but then too my phone is frequently rebooting . please help me tired of this. give me step by step solution for this. thank you.
Click to expand...
Click to collapse
I've send you a PM.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
Requirements
Root+Bootloader Unlocked
Flashing Instructions
After Unlocking Bootloader (If you dont know how to do it then go here)
[url]https://forum.xda-developers.com/meizu-m2-mini/how-to/guide-unlock-bootloaderinstall-twrp-t3390799[/URL]
Enter In fastboot.Then type.
"fastboot flash recovery recovery.img"
wait a minute turn off the phone. and enter recovery (Power + vol up until vibration)you'll Be in TWRP
Download Links
Old Recovery Version 2.8
[url]https://drive.google.com/open?id=0Bz6Fq2POoJTlMXd3YzJhTnUxeVU[/URL]
Mid Recovery 3.10 Latest
[url]https://drive.google.com/open?id=0Bz6Fq2POoJTlYnpCaXhSOUxjX0E[/URL]
New Recovery 3.1.1
[url]https://drive.google.com/file/d/0Bz6Fq2POoJTlRjh4ZkppWUJ4Qm8/view?usp=drivesdk[/URL]
Latest Recovery 3.2.1
[url]https://drive.google.com/file/d/1ftYtD2Tm0MdKBv_ZtVQHGJEcCuflb6Oe/view?usp=drivesdk[/URL]
Don't Forget To Press Thanks if you like it :good: :good:
Regards~
Murtaza Piplod
what's news bro?
ADIB27 said:
what's news bro?
Click to expand...
Click to collapse
updated with latest features of the latest recovery released by TWRP read changelogs at there TWRP site
heelo there,
my meizu m2 now keep rebooting and enter the twrp recovery.
even i hold the power button, it still cannot totally shutdown the phone.
any solution?
please help me.
maxisgsm said:
heelo there,
my meizu m2 now keep rebooting and enter the twrp recovery.
even i hold the power button, it still cannot totally shutdown the phone.
any solution?
please help me.
Click to expand...
Click to collapse
Try clear dalvik and cache.
adarshm4you said:
Try clear dalvik and cache.
Click to expand...
Click to collapse
the problem is after the phone reboot, it enter twrp menu, dan go to format menu then reboot again ......
maxisgsm said:
the problem is after the phone reboot, it enter twrp menu, dan go to format menu then reboot again ......
Click to expand...
Click to collapse
I think there will be some mess in installed os reflash it after taking a backup.
adarshm4you said:
I think there will be some mess in installed os reflash it after taking a backup.
Click to expand...
Click to collapse
my phone hang while i do a format storage.
maxisgsm said:
my phone hang while i do a format storage.
Click to expand...
Click to collapse
Go twrp recovery and do advance wipe and flash os then.Connect to pc and copy files to memory card and then.Flash it from there since your hang issue will not affect installing.It will solve all problems.Always keep backups before doing anything.
adarshm4you said:
Go twrp recovery and do advance wipe and flash os then.Connect to pc and copy files to memory card and then.Flash it from there since your hang issue will not affect installing.It will solve all problems.Always keep backups before doing anything.
Click to expand...
Click to collapse
every time the phone boot into twrp, it only go back to last state and keep fail then reboot...... it will cycle until battery die. i cannot go anywhere in twrp .....
now i at fastboot state, when i try to flash stock rom, it gave me the error
G:\adbFire>fastboot flash update update_8.zip
sending 'update' (1115283 KB)...
OKAY [ 88.153s]
writing 'update'...
FAILED (remote: partition table doesn't exist)
finished. total time: 88.237s
Your partition got messed by installing custom rom.This problem is uncommon.I cant find good solution for m2 in xda or any forums.Brother just bricked your phone.These cases occur when wrong kernal flash,flashing radio etc.I found this problem only in one plus.
Check these before doing anything in adb
Properly detects the device to avoid errors
Detect if bootloader is locked and temporary unlock it if that is the case.If it temporarly locked again,got to fastboot and unlock it as you know the process.
Try Perform this:
Flashing twrp recovery.img.If no error comes flashing custom or
Twrp is unable to create new partitions...Then
Fastboot boot recovery.img (of stock flyme)
fastboot flash recovery boot.img
Going to stock rom is only nice way i think so.
Boot.img can be found inside rom zip of flyme.Go for flyme first.
It isn't the best method to flash a different rom, but as the cmd implies its perfectly fine for flashing an update of the same rom.Since phone is prime important now.Go back custom then.
Some helpful links linkshttps://forum.xda-developers.com/meizu-m2-mini/how-to/install-stock-recovery-meizu-m2-mini-t3433916
Or wait for any heads to reply:silly:
adarshm4you said:
Your partition got messed by installing custom rom.This problem is uncommon.I cant find good solution for m2 in xda or any forums.Brother just bricked your phone.These cases occur when wrong kernal flash,flashing radio etc.I found this problem only in one plus.
Check these before doing anything in adb
Properly detects the device to avoid errors
Detect if bootloader is locked and temporary unlock it if that is the case.If it temporarly locked again,got to fastboot and unlock it as you know the process.
Try Perform this:
Flashing twrp recovery.img.If no error comes flashing custom or
Twrp is unable to create new partitions...Then
Fastboot boot recovery.img (of stock flyme)
fastboot flash recovery boot.img
Going to stock rom is only nice way i think so.
Boot.img can be found inside rom zip of flyme.Go for flyme first.
It isn't the best method to flash a different rom, but as the cmd implies its perfectly fine for flashing an update of the same rom.Since phone is prime important now.Go back custom then.
Some helpful links linkshttps://forum.xda-developers.com/meizu-m2-mini/how-to/install-stock-recovery-meizu-m2-mini-t3433916
Or wait for any heads to reply:silly:
Click to expand...
Click to collapse
adb cannot detect my devices ..... if i not mistake, last time i unlcock my OnePlus one without any problem, and adb can detect my phone,
now cannot detect ....
@murtaza1326
TWRP 3.2.1.0 is out!
Update the post
rushiranpise said:
@murtaza1326
TWRP 3.2.1.0 is out!
Update the post
Click to expand...
Click to collapse
post updated new latest 3.2.1 TWRP is added @Dinolek TWRP is alread there in his post so I don't think i should repost it here ??
Regards~
how to recovery install meizu m2 mini flyme 6.2.0.0g
thanks sir.. i wanna install this twrp
Pretty good!
This is outdated. You can still use this procedure if you want, but there is now a flashable zip that can be used for upgrades, or clean installs in this thread, unless you have an AT&T H900.
If you have an AT&T H900 and would like to upgrade to stock Nougat, then you can follow the procedure below. You only need to flash the kernel (boot.img) and system (system.img). Nougat works OK with the rest of the MM firmware.
I have not gotten verification that the modem firmware is OK for the H900. On a lot of other devices, the modem is the same for the AT&T and T-Mobile versions, but need to be sure.
If you have an H900, follow the procedure below, but do not flash the modem, or rpm for now. Nougat works with the MM modem, and rpm. Once I find a brave soul that is willing to test the modem, and rpm on the H900, I will update this post. If you are willing, I can give you the instructions to backup your modem and rpm partitions. This is something that will either work, or won't, but you can revert -- it isn't going to brick your phone, but you MUST have backups of those partitions. I don't have them since I don't own an H900.
Here is the quick and dirty on how to upgrade to Nougat and keep root. Edited to add modem, and rpm...
First the usual disclaimers:
You blow up your phone, that is on you.
This method has only been tested on STOCK rooted MM v20L -- anything else, and you are in uncharted territory.
* Download boot.img
SHA1: 0ac43ba62c7bd548bf25f4f3125dc07dbf49a859
* Download system.img
SHA1: 7916482970b2c4113b79d41ff89f00c41f783008
* Download modem.img NOT FOR H900
SHA1: 76e4a1dc098b1497f31ed7de3fc21d8365ebc025
* Download rpm.img NOT FOR H900
SHA1: 90a98e04c2083303378898d37857766fdfb01525
Until I (or someone else) makes a flashable zip, you will have to do it manually:
* adb reboot recovery
* adb push boot.img /sdcard
* adb push system.img /sdcard
* adb push modem.img /sdcard
* adb push rpm.img /sdcard
* adb shell
* cd /dev/block/bootdevice/by-name
* dd if=/sdcard/boot.img of=boot
* dd if=/sdcard/system.img of=system
* dd if=/sdcard/modem.img of=modem
* dd if=/sdcard/rpm.img of=rpm
* exit
* adb reboot system
It will complain about running out of space when you are flashing system -- you can safely ignore this.
Once you reboot, it will upgrade you to Nougat. I have deleted the recovery-from-boot.p so you will not lose TWRP, but you will lose root (temporarily). Also, all the crapware will come back if you debloated.
Once the upgrade is complete and you are back, you can reboot to recovery and flash your su binary of choice to regain root, and then proceed to clean all the crap up again.
In the event that you don't want to go through all this crap, I will be posting (unless someone beats me to it) an update.zip that is debloated and pre-rooted this weekend (don't have time till then).
I have tested this on my own phone, so I know it works. Again, I was running stock v20L that had been rooted with dirtycow, and SuperSU for my su bin.
Lastly, make sure you enable developer mode and disable automatic updates
-- Brian
May try this on a 20j rooted with Magisk tonight. Thanks!
*edit*
Just in case anyone else is on 20j. You can flash Magisk v13 after pushing boot and system.
I've already updated to nougat.... Is there nothing I can do for root...... ??
Well, you can try rolling back to v20L. Go into download mode and see if you can use LG UP to flash the v20L KDZ. If they didn't increment the roll back version, then you are good to go. If they did, then I dunno. I will be trying some things this weekend.
-- Brian
Many thanks! Backing up and downloading now Will report back with status once done
@eigokyoukan Please post the exact path to the by-name devices so I can update the post. You will know if you are in the right directory if you type ls and see boot, system, modem, laf, etc, etc...
Thanks,
-- Brian
The path is
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
alotmoore said:
The path is
View attachment 4216256
Click to expand...
Click to collapse
So replace "Something" with the second to last line of code in your picture?
Just got done flashing and upgrading, worked like a charm! Thank you again for the images.
The directory you want to go to in the middle step is (you were close!):
* cd /dev/block/platform/f9824900.sdhci/by-name
Just got to flash SU again and debloat and I'll be back to my normal setup!
EDIT: Just wanted to report back that just flashing the latest SuperSU package got me back up running on root just fine, and am running smooth so far on errything
It worked and I was able to root with the latest Magisk. Passes safetynet and I'm able to use Android Pay too!
VERY nice guide, works perfect. Great job to the OP
now if we could get xposed interlaced into the stock rom somehow
https://github.com/abforce/xposed_art_n/blob/master/README.md
just got ported for 7.1.2
chaitea said:
It worked and I was able to root with the latest Magisk. Passes safetynet and I'm able to use Android Pay too!
Click to expand...
Click to collapse
Will magisk work if I've already updated through LG Bridge from stock to stock nougat...?
Does your baseband say unknown after the upgrade?
alotmoore said:
Does your baseband say unknown after the upgrade?
Click to expand...
Click to collapse
There's is a number. I added an attachment.
Here's mine. No number.
I will edit the first post to reflect this, but the reason that the baseband is unknown is because we haven't flashed the modem yet. The phone works fine with the old modem firmware, but I will be making a flashable modem. Newer is ALWAYS better -- right? /s
-- Brian
If i'm already on 7.0 there isn't any method to get root Right? or you will make a flasheable rom pre-rooted? If ask because im gonna make the update right now, i will lose my TWRP? i will use LG Bridge
@rafaelox24 If you are already on 7.0, then you have lost root, and there is no (currently) known way to root. If you upgrade to 7.0 using LG Bridge, you will lose root forever (well most likely).
If you are still on MM 6.0.1, then use the instruction provided here, and you can keep root.
Oh, Well thanks for your response, i will wait for a flasheable rom, i don't know who, but someone say that ara going to do a flasheable zip, i supposed that means will be able to flash with custom Recovery.
OK, I added the modem firmware. If you have already flashed boot and system, just follow the same procedure, but skip those and go right to flashing the modem. You will then have a nice baseband version in your settings / about phone / software info. It makes a big difference too. My phone had no service after a reboot for about 30 seconds, now it locks onto the cell immediately.
-- Brian
First off, a HUGE thank you to @autoprime (for paving the way) and @waylo (for his assistance on getting this going after I found the KDZ)
I am currently storing these in my google drive account, so please be gentle till I have a better host location:
Below are the downloads for the LG-H83020N firmware
Folder with all the LG830 firmware I have so far:
LG830 (G5)
LG-H83020N-Flashable.COMPLETE-ARB01.zip
As always, COMPLETE is 100% stock
Flash COMPLETE zip -> wipe cache partition -> flash Magisk ZIP (or SuperSU if you insist) to root and keep TWRP
OPTIONAL: After flashing, remount /system RW -> delete recovery-from-boot.p to guarantee TWRP sticks
LG-H83020N-Flashable.Bootloader-ARB01
LG-H83020N-Flashable.Modem-ARB01.zip
LG-H83020N-Flashable.Boot.zip
H830N_00_1017.kdz (HUGE Thank you to @Azul Baseem for the upload)
For instructions, follow the same instructions as you would in any other KDZ/ZIP thread. For Example
Feel free to hit thanks.
Also feel free to hit up autoprime's All in One thread HERE
Thank you very much bedwa!
Kdz link updated!
Thank you @bedwa as always.
I fear my only true contribution here is MD5 confirmation of the files:
LG-H83020N-Flashable.COMPLETE-ARB01.zip 8a49733028bef23d775bf542eb62b726
LG-H83020N-Flashable.Boot.zip ddea9d814f66266de34a154f0c7f6b41
H830N_00_1017.kdz 732b717af8d77501342be445002c4fae
Edit: Also, since someone will definitely miss it in the title, this is confirmed to still be on Anti-Rollback 1. You're free to flash back and forth between 20A if you need to Dirtycow your phone again.
Keeping me honest, I swear I'll remember them next time.
Thanks for the upload. I was able to update just fine thanks to this.
BTW... It still has H83020m mentioned in the body of the OP instead of H83020n.
shinji257 said:
Thanks for the upload. I was able to update just fine thanks to this.
BTW... It still has H83020m mentioned in the body of the OP instead of H83020n.
Click to expand...
Click to collapse
Fixed. That's what I get for using the copypasta method. Missed the one. :silly:
help me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i had this issues when i try to flash it i already use uppercut
solved
running 20N , so far so good, just notice a small problem with GPS , it is a bit spotty today. @bedwa : Can you make a slim down version ? like removing LG/TMO/Google stuffs ? and reduce /system partition size ?
abced123 said:
running 20N , so far so good, just notice a small problem with GPS , it is a bit spotty today. @bedwa : Can you make a slim down version ? like removing LG/TMO/Google stuffs ? and reduce /system partition size ?
Click to expand...
Click to collapse
That would be trickier. All of these are the partition images. To make a slim zip like that I'll have to either unpack and build or unpack and attempt to repack. I might, but not likely at this time.
Thank you so much for making this. So happy to be rooted and on the latest build thanks to your hard work. =)
fc3211 said:
Thank you so much for making this. So happy to be rooted and on the latest build thanks to your hard work. =)
Click to expand...
Click to collapse
Quite welcome... It's more time consuming than hard work, but the appreciation and thanks is greatly appreciated as well.
@bedwa
I am running on rooted H83020a with TWRP and SuperSU installed. In order to upgrade to 20N by keeping all my current settings and data along with root and TWRP, what are the steps should I follow?
1. Take a complete backup using LG Backup
2. Boot into TWRP
3. Flash Complete Zip (H83020N) from TWRP
4. Flash SuperSU Zip
5. Reboot System
6. Restore the complete backup from LG Backup
Does this work okay? Or, do I need to do anything else, like Wipe Data/Partition etc.? Sorry for the noob question.
Hello,
If I flash boot and bootloader, will it lock my bootloader and brick the phone if I am on LineageOS?
nizarp said:
@bedwa
I am running on rooted H83020a with TWRP and SuperSU installed. In order to upgrade to 20N by keeping all my current settings and data along with root and TWRP, what are the steps should I follow?
1. Take a complete backup using LG Backup
2. Boot into TWRP
3. Flash Complete Zip (H83020N) from TWRP
4. Flash SuperSU Zip
5. Reboot System
6. Restore the complete backup from LG Backup
Does this work okay? Or, do I need to do anything else, like Wipe Data/Partition etc.? Sorry for the noob question.
Click to expand...
Click to collapse
Backup is always good, shouldn't have to restore it as it's updating from a previous version and doesn't wipe data when upgrading. But that's the correct process with or without #6.
azizo07 said:
Hello,
If I flash boot and bootloader, will it lock my bootloader and brick the phone if I am on LineageOS?
Click to expand...
Click to collapse
Shouldn't, but it would always be a good idea to backup beforehand. I would however only flash the bootloader, as the boot is the kernel and will be different than what LineageOS uses though.
I just boot into TWRP and flashed the complete zip and then flashed the latest SuperSU Zip. I pressed Reboot System after that, but, I am now stuck in a boot loop. Phone shows LG logo and reboots again and again.
I tried the Power button + Vol Down method, but, it doesn't work too. It gets to Factory reset screen, and after Yes and Yes, it goes to back to boot loop again. I am able to get into Download Mode and Fastboot Mode. Can I do something from here?
Can someone help please? Anyway to get into TWRP or recovery?
Sounds like you will need to LGUP or Uppercut your phone back to stock 20A. Then dirtycow back TWRP. Then try flashing the new ZIP again. Skip Supersu this time and try Magisk instead.
Thanks. I flashed back to 20A using LGUP and KDZ file. Need to dirtycow back TWRP now. I'm still wondering what went wrong in my process.
1. Take a complete backup using LG Backup
2. Boot into TWRP
3. Flash Complete Zip (H83020N) from TWRP
4. Flash SuperSU Zip
5. Reboot System
Click to expand...
Click to collapse
Do I need to reboot to TWRP once after flashing instead of Reboot System directly after flash? Any idea?
No, rebooting into TWRP wouldn't do anything. There's a script you might need to get into and delete prior to rebooting. But that only ensures that TWRP stays.
"After flashing, remount /system RW -> delete recovery-from-boot.p to guarantee TWRP sticks"
That having been said, I've done this before and STILL not had TWRP stay. Some recommend wiping /cache as well.
OR, again, use Magisk instead and don't use SuperSU.
Even if TWRP didn't stick, you should have been booting into system fine. You wouldn't be rooted, TWRP would be gone, but system shouldn't have been messed up. So something got borked, I'd have to guess, because of SuperSU.
New security patch update alert
Hi, I created this thread because I have solved the problem of the 4g at the time of losing my "moto g5 imei".
Just installed the "dotos rom v2. 2" 06/05/2018, I went into the bootloader, did the respective backup (currently at H +), and entered modem commands in fastboot mode, all this with the 64 twrp, say because I have read that he has to go to twrp's 32 " , but no, I didn't do it, well, at the time of start the rom again because you will have 4 g, well that was my case, I don't know if it will work with some of you, perhaps to serve them, my specific model is the xt1670.
Anyway here are the steps:
1 -- Get a backup of the file "EFS" (currently with H +), to me only appears me with the 64-bit TWRP '
2 -- Install the rom "dotOS v2.2 - 20180506 ", if you don't have any rom with android 8.1, install first the TWRP 64 and then the rom "dotos".
3 -- Once installed restart mobile to bootloader, and do not change anything.
4 -- Just enter via adb fastboot commands:
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
5 -- Will restart automatically, and you will already have the 4 g network.
6 -- Finally performs a backup of the file "EFS" 4g.
POSSIBLE PROBLEM...
Lack say something, possibly the "imei sv" is set to 0, the solution for me was after having keep the new file efs with 4 g, I installed the "moto g5 official rom (android 7.0)", with full commands, including modems, obviously we will lose the imei, but because we have our file efs 4g, we will restore it, we go back to bootloader mode, install again the 64 twrp, we also install the file "no verity opt encrypt 6.0", then, we return to the main menu of the twrp and restore, and choose the file that we have recovered the EFS 4 g, and " ready, we have a imei, imei sv, and 4 g correctly, upon restart, if you like you make another backup of the definitive efs file, and ready, now if you want to go back to the stock rom, already not to enter modem commands, thats all.
PD: Sorry for my english, I used a translator for this... And sorry for the links, xda will not allow me...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How i get backup of EFS file ?
Thanks for the tutorial, it has served me many gracais since I was 4 months in 3g. just follow the letter
Kindred403 said:
How i get backup of EFS file ?
Click to expand...
Click to collapse
Sorry for the delay in responding, you can only get the EFS file from the recovery Cedric TWRP 64 bits, that is very important, and being in the Backup menu, select the EFS file.
Finally my 4G is back! Thank you very much!
If I update after doing this, will I lose IMEI and have to flash stock again?
ap4ss3rby said:
If I update after doing this, will I lose IMEI and have to flash stock again?
Click to expand...
Click to collapse
No, not at all, just ignore the modem commands, and if you mean to install custom ROMs, will go normal, no errors
sashUser_2 said:
Hi, I created this thread because I have solved the problem of the 4g at the time of losing my "moto g5 imei".
Just installed the "dotos rom v2. 2" 06/05/2018, I went into the bootloader, did the respective backup (currently at H +), and entered modem commands in fastboot mode, all this with the 64 twrp, say because I have read that he has to go to twrp's 32 " , but no, I didn't do it, well, at the time of start the rom again because you will have 4 g, well that was my case, I don't know if it will work with some of you, perhaps to serve them, my specific model is the xt1670.
Anyway here are the steps:
1 -- Get a backup of the file "EFS" (currently with H +), to me only appears me with the 64-bit TWRP '
2 -- Install the rom "dotOS v2.2 - 20180506 ", if you don't have any rom with android 8.1, install first the TWRP 64 and then the rom "dotos".
3 -- Once installed restart mobile to bootloader, and do not change anything.
4 -- Just enter via adb fastboot commands:
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
5 -- Will restart automatically, and you will already have the 4 g network.
6 -- Finally performs a backup of the file "EFS" 4g.
POSSIBLE PROBLEM...
Lack say something, possibly the "imei sv" is set to 0, the solution for me was after having keep the new file efs with 4 g, I installed the "moto g5 official rom (android 7.0)", with full commands, including modems, obviously we will lose the imei, but because we have our file efs 4g, we will restore it, we go back to bootloader mode, install again the 64 twrp, we also install the file "no verity opt encrypt 6.0", then, we return to the main menu of the twrp and restore, and choose the file that we have recovered the EFS 4 g, and " ready, we have a imei, imei sv, and 4 g correctly, upon restart, if you like you make another backup of the definitive efs file, and ready, now if you want to go back to the stock rom, already not to enter modem commands, thats all.
PD: Sorry for my english, I used a translator for this... And sorry for the links, xda will not allow me...
Click to expand...
Click to collapse
Please make a video of it ?
I don't know why you keep saying you have to install dotos to do this? Worked on atomic os.
After doing the fastboot commands the IMEI went to 0 but then after restore the EFS it came back to normal....
I can't say if 4g is back because where I am I had never got 4g before.. I'll have to travel somewhere to see if 4g is back!
Seems possible that 4g is back now! Thanks! ?
Sadly this didn't fix my 4g not working issue ?
This worked perfectly, and I was just thinking about buying another phone. Thanks a lot!
where do we have to take backup of efs. stock rom or dotOS rom ??
Varun Maheshwari said:
where do we have to take backup of efs. stock rom or dotOS rom ??
Click to expand...
Click to collapse
First things first, you gotta be sure you are on stock rom AND have 3G signal. If you don't, flash the latest Pixel Experience so you get IMEI and 3G back (may need to reboot phone twice, I did). After that, you have to flash back stock rom via fastboot mode so make sure you enabled USB debugging (I'm assuming you already know that), but don't run the commands 'fastboot erase modemst1' and 'fastboot erase modemst2'. If you run these, you'll have to start all over. Once you're all set, backup EFS partition using TWRP 3.2.1-0 (64bit version linked above), save it somewhere safe, install dotOS rom (I used the exact version the tutorial suggests, so I would just stick with that), reboot to system (again, you may have to reboot it twice) and you should have 4G/LTE signal. Now create a new EFS backup, save it somewhere safe, and reinstall stock ROM, but this time including those two commands (I installed the latest version with July 2018 security patch). After that, reinstall TWRP 64bits, restore the EFS backup you created while on dotOS and you're done. On First boot you may face some problems while trying to use 4G, it may keep switching between 4G and 3G all the time making it impossible to connect, but should it happen to you, a simple reboot fixes the issue. If you wish to root your phone after the process (like I did for PoGO spoofing) just install 32bit TWRP 3.2.2-0 and flash Magisk 16.7 beta and reboot phone twice (First time may have 4G issue again, rebooting fixes it). Sorry for the late response, it's way past midnight here in Brazil. Hope you get It working again
I finally got my 4g back after a long time thanks brother!!!!
patricksouza472 said:
First things first, you gotta be sure you are on stock rom AND have 3G signal. If you don't, flash the latest Pixel Experience so you get IMEI and 3G back (may need to reboot phone twice, I did). After that, you have to flash back stock rom via fastboot mode so make sure you enabled USB debugging (I'm assuming you already know that), but don't run the commands 'fastboot erase modemst1' and 'fastboot erase modemst2'. If you run these, you'll have to start all over. Once you're all set, backup EFS partition using TWRP 3.2.1-0 (64bit version linked above), save it somewhere safe, install dotOS rom (I used the exact version the tutorial suggests, so I would just stick with that), reboot to system (again, you may have to reboot it twice) and you should have 4G/LTE signal. Now create a new EFS backup, save it somewhere safe, and reinstall stock ROM, but this time including those two commands (I installed the latest version with July 2018 security patch). After that, reinstall TWRP 64bits, restore the EFS backup you created while on dotOS and you're done. On First boot you may face some problems while trying to use 4G, it may keep switching between 4G and 3G all the time making it impossible to connect, but should it happen to you, a simple reboot fixes the issue. If you wish to root your phone after the process (like I did for PoGO spoofing) just install 32bit TWRP 3.2.2-0 and flash Magisk 16.7 beta and reboot phone twice (First time may have 4G issue again, rebooting fixes it). Sorry for the late response, it's way past midnight here in Brazil. Hope you get It working again
Click to expand...
Click to collapse
thankyou so much..it worked
Guys I can not get 4g back at all, I run the command fastboot erase modemst1
fastboot erase modemst2 on pixel rom as I only have 3G andnd this wiped my IMEI and put it to 0, so then I had to reinstall stock oreo rom with all the commands (not erase modemst etc) then wipe then install pixel rom to get 3g back, I can't get 4g how do I do it it's driving my crazy!
please help
Any update? I really need 4G working again, the erase modemst1/2 commands just wiped my IMEI on this guide, then I had to start all over again just to get 3G working and my IMEI back again.
junglebungle said:
Any update? I really need 4G working again, the erase modemst1/2 commands just wiped my IMEI on this guide, then I had to start all over again just to get 3G working and my IMEI back again.
Click to expand...
Click to collapse
Have a look at this guide. It is for Potter, but the same principles apply to Cedric
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
NZedPred said:
Have a look at this guide. It is for Potter, but the same principles apply to Cedric
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
Click to expand...
Click to collapse
Wow that looks very difficult, I don't want to mess up my phone even more
I mean I have IMEI and 3G, I just need my 4G back..
junglebungle said:
Wow that looks very difficult, I don't want to mess up my phone even more
I mean I have IMEI and 3G, I just need my 4G back..
Click to expand...
Click to collapse
Quite often 4G is missing for the same reason. What rom are you on right now? If you are on stock nougat, then flash this zip
https://androidfilehost.com/?fid=3700668719832240875
All this zip does is fix the ownership of a couple of folders in the persist partition. If this is the issue you're facing (can't tell for sure without getting some info from your phone), you should get back 4G.