Database Users

Nexus 4 only with 5 GB partition!?

Hello gents,
After messing around with the fastboot yesterday i got back to stock Android and realised i have only a 5GB partition....
I formatted the phone and installed again the stock Rom but that didn't work.
Anybody as any idea on how to solve this problem? thanks:good:

Anyone?

Fix for 16GB N4 showing as 8GB
I just experienced the same exact problem, and wasn't able to find a solution until I followed this guide: http://forum.xda-developers.com/showthread.php?t=2033692
Make sure you have the latest occam image https://developers.google.com/android/nexus/images#occam
Use 7-Zip to extract the files from within the .tgz file, and then the .tar file.
Shift + Right Click in the folder to Open a Command Prompt, and run the following commands:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
fastboot -w update image-occam-jwr66y.zip

jsteg94 said:
I just experienced the same exact problem, and wasn't able to find a solution until I followed this guide: http://forum.xda-developers.com/showthread.php?t=2033692
Make sure you have the latest occam image https://developers.google.com/android/nexus/images#occam
Use 7-Zip to extract the files from within the .tgz file, and then the .tar file.
Shift + Right Click in the folder to Open a Command Prompt, and run the following commands:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
fastboot -w update image-occam-jwr66y.zip
Click to expand...
Click to collapse
Its a common error after flashing the factory images and all you usually have to do is this:
-Boot into STOCK RECOVERY (If you are running a custom recovery you must flash to stock)
-Clear cache
-Factory reset
which is right at the top of el daddy's thread

kzoodroid said:
Its a common error after flashing the factory images and all you usually have to do is this:
-Boot into STOCK RECOVERY (If you are running a custom recovery you must flash to stock)
-Clear cache
-Factory reset
which is right at the top of el daddy's thread
Click to expand...
Click to collapse
Thanks, kzoodroid. I didn't realize that you had to be in Stock Recovery. Every time I followed the above steps on el daddy's thread, I was using TWRP, which never solved the problem.

Well i´ve been trying and trying... its simple to follow the guide but wen i get to this step fastboot -w update image-occam-jdq39.zip the CMD crashes all the time...
I´ve restarted the computer and everything but it crashes always...
And also i can´t get into stock recovery... The droid with the triangle come up the i press power and then vol up but nothing happends...

Yeah, i think i just found a easy way to go around this problem!
Very simple:
1. After flashing the stock rom use Nexus Root Toolkit to do a OEM Lock
2. Run CMD fastboot and use this command: fastboot oem unlock. You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
3 Restart and that's it! Your back to 13GB again
Thanks to all for your help. I will share this info on El Daddy thread.

SWEagle said:
Yeah, i think i just found a easy way to go around this problem!
Very simple:
1. After flashing the stock rom use Nexus Root Toolkit to do a OEM Lock
2. Run CMD fastboot and use this command: fastboot oem unlock. You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
3 Restart and that's it! Your back to 13GB again
Thanks to all for your help. I will share this info on El Daddy thread.
Click to expand...
Click to collapse
I've had this issue come up more times than I can count, and just the other day I wasn't able to get back to the full storage allotment after several attempts following the steps to erase all the partitions and reflash. I did exactly what you did by flashing the factory images, re-locking the bootloader, then unlocking it again, and my storage was back to normal. I'm not exactly sure what happened, but I discovered this works, just as you did

hp420 said:
I've had this issue come up more times than I can count, and just the other day I wasn't able to get back to the full storage allotment after several attempts following the steps to erase all the partitions and reflash. I did exactly what you did by flashing the factory images, re-locking the bootloader, then unlocking it again, and my storage was back to normal. I'm not exactly sure what happened, but I discovered this works, just as you did
Click to expand...
Click to collapse
Cool! :laugh:

SWEagle said:
Well i´ve been trying and trying... its simple to follow the guide but wen i get to this step fastboot -w update image-occam-jdq39.zip the CMD crashes all the time...
I´ve restarted the computer and everything but it crashes always...
And also i can´t get into stock recovery... The droid with the triangle come up the i press power and then vol up but nothing happends...
Click to expand...
Click to collapse
With my phone I have to press power and volume+ a bunch of times to get it to finally go into stock recovery it never does it on the first few tries and can take a few minutes of playing to hit them perfectly to get it to open.

SWEagle said:
Yeah, i think i just found a easy way to go around this problem!
Very simple:
1. After flashing the stock rom use Nexus Root Toolkit to do a OEM Lock
2. Run CMD fastboot and use this command: fastboot oem unlock. You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
3 Restart and that's it! Your back to 13GB again
Thanks to all for your help. I will share this info on El Daddy thread.
Click to expand...
Click to collapse
Wow, that's actually a lot easier. Thanks for finding a simpler way, SWEagle! I'll try that next time.

jsteg94 said:
Wow, that's actually a lot easier. Thanks for finding a simpler way, SWEagle! I'll try that next time.
Click to expand...
Click to collapse
Instead of using the toolkit you probably could just use fastboot to lock the device too.
fastboot oem lock

kzoodroid said:
Instead of using the toolkit you probably could just use fastboot to lock the device too.
fastboot oem lock
Click to expand...
Click to collapse
I thought about that too. It might work. If it does it's even easier

[Q] Erase modemst1 -modemst2 fastboot i9505 faulty gps

Hello guys,
I've deviced to open a thread since i'm out of options and helpless. I've been busy trying to get my gps to work on my i9505 running on cm12.0 (optimized-final). Before yesterday i ran cm12.1 nightlys but because i had bluetooth and gps problems i decided to run a more stable built, so i did a full wipe with twrp (wipe>wipe data) and installed the rom.
Bluetooth issues resolved but gps still not working.
Ive tried several procedures, like installing gps status and downloading the agps files, and configuring the gps.conf file. Both didnt work unfortunately.
After some research i found out that a lot of people experiencing gps problems with the cm12 roms. A much suggested solution would be to use fastboot to execute the following commands; "fastboot erase modemst1" and "fastboot erase modemst2".
So now i used several procedures (via xda-developers and others) to install adb/fastboot and the necessary drivers but fastboot keeps failing to recognize my device (adb works properly though).
After more research i discovered that fastboot doesn't work with the i9505 (non-google edition). Can someone confirm this?
Ive spend several hours trying to make it work but fastboot just won't recognize my device, so i assume the i9505 just isnt compatible. The annoyance is strong with this one.
Does someone has the expertise to see pass this problem? Is there maybe a way to erase the modem cache through adb? Or is there a downloadable script or app i can run from my phone?
You would help me so much!
Much obliged.

I don't know about the fastboot issue, but to correct your issues you need to get back to square one so you can try again. Install a stock ROM using Odin. That should restore your GPS functions. From there, you can try a custom ROM again if you wish.

Strephon Alkhalikoi said:
I don't know about the fastboot issue, but to correct your issues you need to get back to square one so you can try again. Install a stock ROM using Odin. That should restore your GPS functions. From there, you can try a custom ROM again if you wish.
Click to expand...
Click to collapse
Thanks for your reply. But yeah, ive read about this solution but i wanted to try the fastboot command first. But since its not working i will go back to stock and start over.
Would i mess my gps up again if i restore a twrp backup after installing stock?

Possibly. GPS functions are modified through the gps.conf file and your backup could restore settings that would bring your problem back. It's best to not use your backup.

bassld said:
Thanks for your reply. But yeah, ive read about this solution but i wanted to try the fastboot command first. But since its not working i will go back to stock and start over.
Would i mess my gps up again if i restore a twrp backup after installing stock?
Click to expand...
Click to collapse
Our device doesn't have fastboot. No Samsung devices has fastboot.

Hello,
Is there any ideas how to use those commands on i9505 with TWRP maybe?:
"fastboot erase modemst1" and "fastboot erase modemst2"
Thanks

Dionizas said:
Hello,
Is there any ideas how to use those commands on i9505 with TWRP maybe?:
"fastboot erase modemst1" and "fastboot erase modemst2"
Thanks
Click to expand...
Click to collapse
No. Samsung does not have fastboot thus those commands will never work.

[FIX] Phone Reboots Into Recovery Mode & Can Only Be Started From Fastboot

Thanks to xda member @Shooting Star Max for the original post for this solution
If your phone is always rebooting into recovery, and the only way to boot normally is by using the bootloader, follow these instructions:
Some users recommend removing your SD before doing the following as incorrectly formatted SD Cards could cause the phone to boot into recovery instead of booting normally.
1) Boot into TWRP recovery.
2) Plug your Cedric into your computer (which needs to have drivers and fastboot installed).
3) Open a command prompt window and type:
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/misc misc.img
This will make a backup of the misc partition just in case.
4) Type the following:
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
This will clear the misc partition. You might get a message regarding lack of space, but it's okay.
5) Your Cedric will boot normally again

TheFixItMan said:
Thanks to xda member @Shooting Star Max for the original post for this solution
If your phone is always rebooting into recovery, and the only way to boot normally is by using the bootloader, follow these instructions:
1) Boot into TWRP recovery.
2) Plug your Cedric into your computer (which needs to have drivers and fastboot installed).
3) Open a command prompt window and type:
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/misc misc.img
This will make a backup of the misc partition just in case.
4) Type the following:
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
This will clear the misc partition. You might get a message regarding lack of space, but it's okay.
5) Your Cedric will boot normally again.
Click to expand...
Click to collapse
I did the procedure and everything went back normal.
I did a backup with the twrp and when I went to restore and go back everything as before, it will continue to restart in the bootloader and I must confirm with the power key to boot the system.
I tried to repeat the procedure but nothing to do does not work anymore.
Some help thank you

masterdex said:
I did the procedure and everything went back normal.
I did a backup with the twrp and when I went to restore and go back everything as before, it will continue to restart in the bootloader and I must confirm with the power key to boot the system.
I tried to repeat the procedure but nothing to do does not work anymore.
Some help thank you
Click to expand...
Click to collapse
As long as you have fully booted your phone before trying again I don't see why you couldn't repeat it
Or reflash the recovery and try again

[/ATTACH]
TheFixItMan said:
As long as you have fully booted your phone before trying again I don't see why you couldn't repeat it
Or reflash the recovery and try again
Click to expand...
Click to collapse
Still tried on minimal adb and phower shell does not work. I attach pictures.

masterdex said:
[/ATTACH]
Still tried on minimal adb and phower shell does not work. I attach pictures.
Click to expand...
Click to collapse
Make sure adb is connected properly
Code:
adb kill-server
adb devices
Your device should be displayed as connected & should be the only device listed
If it still doesn't work then the only solution I can think of is restoring your stock firmware by fastboot - do not flash the bootloader part of the firmware

TheFixItMan said:
Make sure adb is connected properly
Code:
adb kill-server
adb devices
Your device should be displayed as connected & should be the only device listed
If it still doesn't work then the only solution I can think of is restoring your stock firmware by fastboot - do not flash the bootloader part of the firmware
Click to expand...
Click to collapse
Yes is connected. If only I could find the firmware for my XT1675 16gb / 2gb single sim model.

masterdex said:
Yes is connected. If only I could find the firmware for my XT1675 16gb / 2gb single sim model.
Click to expand...
Click to collapse
Same phone as mine & Iv never had this problem - I use lineageos - try flashing that
Other than that I can't suggest anything else

Thank you anyway. They persistently waited for Lenovo to provide the tools and release the firmware for my model that is currently unavailable.
I've tried all the constructions here, but they all have background noise during calls and fixed gps in over a minute and it's not accurate.
Do you have my own model with the same features?

masterdex said:
Thank you anyway. They persistently waited for Lenovo to provide the tools and release the firmware for my model that is currently unavailable.
I've tried all the constructions here, but they all have background noise during calls and fixed gps in over a minute and it's not accurate.
Do you have my own model with the same features?
Click to expand...
Click to collapse
I have the XT165 running lineageos
No problems with calls - iv changed the build.prop to edit call volume (see my last post in the lineageos thread)
No problem with gps
You could try running these commands in fastboot as this was a fix for gps in past moto devices
Code:
fastboot erase modemst1
fastboot erase modemst2

Okay, now I'm just trying to build stock, if I think I bought the phone, just the time to get home and unlock bootloader and put custom rom, I almost do not know the functions of building stock. Now I see how it behaves and I guess if I install Lineage again and make all the corrections you've suggested very kindly thanks.

TheFixItMan said:
4) Type the following:
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
This will clear the misc partition. You might get a message regarding lack of space, but it's okay.
Click to expand...
Click to collapse
Clearing the whole misc partition may be overkill and cause other issues. In the LG threads they currently suggest clearing only the first 256 bytes.

ST Dog said:
Clearing the whole misc partition may be overkill and cause other issues. In the LG threads they currently suggest clearing only the first 256 bytes.
Click to expand...
Click to collapse
This works fine for our users - its been tested & no one has reported any issues

TheFixItMan said:
This works fine for our users - its been tested & no one has reported any issues
Click to expand...
Click to collapse
That's cool. Just a thought.
Different OEs put different stuff there, but really no reason to clear it all if only part is the problem.
And one never knows when they might change the usage.
Oh, and masterdex above appears to have had some issue.

ST Dog said:
That's cool. Just a thought.
Different OEs put different stuff there, but really no reason to clear it all if only part is the problem.
And one never knows when they might change the usage.
Oh, and masterdex above appears to have had some issue.
Click to expand...
Click to collapse
It worked for him but then he restored old phone backups - I recommended flashing lineageos from scratch

Nothing to do, I tried again to download Lineage, make a clean installation by deleting all the entries in the TWRP, configuring the phone restarted in recovery, and rewriting the procedure, the result does not change always restarts the bootloader.
At this point you only have to install the firmware from scratch, someone knows where to find firmware stock model XT1675 16gb storage and 2 gb sin ram single sim?

masterdex said:
Nothing to do, I tried again to download Lineage, make a clean installation by deleting all the entries in the TWRP, configuring the phone restarted in recovery, and rewriting the procedure, the result does not change always restarts the bootloader.
At this point you only have to install the firmware from scratch, someone knows where to find firmware stock model XT1675 16gb storage and 2 gb sin ram single sim?
Click to expand...
Click to collapse
This is rom stock Cedric work on XT1675 16 gb 2 gb ram installed on Motog5 brand Tim :https://www.youtube.com/watch?v=EMyaDv1lcYg

TheFixItMan said:
I have the XT165 running lineageos
No problems with calls - iv changed the build.prop to edit call volume (see my last post in the lineageos thread)
No problem with gps
You could try running these commands in fastboot as this was a fix for gps in past moto devices
Code:
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
I tried to give these commands fastboot but the result and that when I restart the phone no longer sees the sim and I have to reinstall the original firmware with fastboot. Tried twice the same result, are you sure you have the right commands?

My Cedric is listed on the adb devices code when it's turned on. But if I restart to twrp then it's not listed. Now how can I perform this
Sent from my Motorola Moto G 2014 using XDA Labs
---------- Post added at 11:57 AM ---------- Previous post was at 11:52 AM ----------
It is listed when I turned off the Mtp. But when I give the first command to backup the misc folder I get
[?] /dev/block/platform/soc/7824900.sdhci/by-name/misc: 1048576/?.
Sent from my Motorola Moto G 2014 using XDA Labs
---------- Post added at 12:17 PM ---------- Previous post was at 11:57 AM ----------
Again solved it. I just backed up the misc in twrp itself by copying the misc file to the /sdcard using the inbuilt file manager of twrp. Then tried the second command. It worked like charm. Thank you
Sent from my Motorola Moto G 2014 using XDA Labs

Perfect!
Thank you, TheFixItMan! I have an XT1672, Android 7.0 Stock Rom, and I was having this problem after trying the November update via OTA. The correction steps worked perfectly! Happy New Year!

Thanks hope to try this tonight, have you had feedback that this works? Thanks

Second SIM isn't working anymore - Lenovo K6

After buying Lenovo K6, it was okay with the marshmallow firmware, then I recieved the Nougat update and I didn't really like it, So I installed AOKP custom rom and then I wanted to get back to the stock firmware, which is mm.
I flashed it fine but the second SIM is not working anymore, it says " No service | Orange EG "
It's detected but it doesn't really work, any help please ??

did u checked baseband

i think it is basebend issue..firstly you have to have adb&fastboot on your computer,then plug your phone on computer,open adb and type: adb reboot bootloader(it boots in fastboot),then type: fastboot erase modemst1 and then: fastboot erase modemst2,then:fastboot erase cache and then fastboot reboot..now both sims should work...

@ilia1998, Oh my god .. you saved my life, I don't know how to thank you, trust me you're a life savior!!
Thanks a lot <33333

no problem bro...

Now VOLTE isuue
ilia1998 said:
i think it is basebend issue..firstly you have to have adb&fastboot on your computer,then plug your phone on computer,open adb and type: adb reboot bootloader(it boots in fastboot),then type: fastboot erase modemst1 and then: fastboot erase modemst2,then:fastboot erase cache and then fastboot reboot..now both sims should work...
Click to expand...
Click to collapse
after doing this SIM 2 is working but now volte stopped working. What should I do now?
:crying::crying::crying::crying::crying:

Rkladwal said:
after doing this SIM 2 is working but now volte stopped working. What should I do now?
:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
i don't know about volte..which rom are you using?

working now
ilia1998 said:
i don't know about volte..which rom are you using?
Click to expand...
Click to collapse
Thanks for your response. I flashed stock Rom again and do this procedure again. Now both SIMs + VOLTE is working.

Rkladwal said:
Thanks for your response. I flashed stock Rom again and do this procedure again. Now both SIMs + VOLTE is working.
Click to expand...
Click to collapse
How did you fixed VoLte ? i am still not able to access VoLte i flashed Stock Rom also...

Hi , Many many thanks... Much appreciated. I have been trying it by re installing approx last 6month, and elapsed much time... NOW SUCCESS !!!! Thanks xda-developers.

ilia1998 said:
i think it is basebend issue..firstly you have to have adb&fastboot on your computer,then plug your phone on computer,open adb and type: adb reboot bootloader(it boots in fastboot),then type: fastboot erase modemst1 and then: fastboot erase modemst2,then:fastboot erase cache and then fastboot reboot..now both sims should work...
Click to expand...
Click to collapse
I had a strange problem with my Lenovo K6 Power. It was working with 4G network only. In my place I have installed 2G network booster for better signal reception but my mobile was unable to get 2G network. I tried various solutions from resetting the phone to flashing older Marshmallow ROM but nothing works. Finally I arrive at this page and follow these steps and bingo! My mobile get full network and become useful once again! Thank you so much...!:good::good::good:

Lenovo k6 note sim2 and volte fix
Hi 2 all today I'll tell u an easy way to fix volte in lenovo k6 note so to fix this we have to flash stock rom here is the link for that --> mail.me after flashing stock rom u may get volte if u dont get volte do not worry just flow the steps
*Open ur dialpad type *#4636#*#* it will open engineering mode go to phone information and select lte only option and down there press button refresh and update button now come out to home screen and again open dialer and type ####862# it will open easy image there u have to select in(##) India and it will update ur system and u will get volte option enabled..have a gud day guys any doubts mail me email: [email protected] I will be in touch with u guys tq

After following the procedure I am not left with a bigger problem, the phone can't read simcard, the imei is blank and baseband version unknown. Anyone with a hint on how to restore the imei or another way to get my phone back to reading the simcard?

ilia1998 said:
i think it is basebend issue..firstly you have to have adb&fastboot on your computer,then plug your phone on computer,open adb and type: adb reboot bootloader(it boots in fastboot),then type: fastboot erase modemst1 and then: fastboot erase modemst2,then:fastboot erase cache and then fastboot reboot..now both sims should work...
Click to expand...
Click to collapse
i tried these commands.....after that my phone serial number says unknown and imei number showing 0
please help me sir....any sim is not supporting anymore in phone....

Help me
Im using k6 note 4gb ram.
Sim2 error and i cant find any solution, baseband not showing error, booth imei also showed normal.
Please help me.
Pict attach

If you would have been near me i would have hugged and kissed you. It worked like a charm. After struggling for so many hours and watching umpteen videos i happened to come across your site. Thank You very much.
ilia1998 said:
i think it is basebend issue..firstly you have to have adb&fastboot on your computer,then plug your phone on computer,open adb and type: adb reboot bootloader(it boots in fastboot),then type: fastboot erase modemst1 and then: fastboot erase modemst2,then:fastboot erase cache and then fastboot reboot..now both sims should work...
Click to expand...
Click to collapse

thanks
thanks

cupliz said:
Im using k6 note 4gb ram.
Sim2 error and i cant find any solution, baseband not showing error, booth imei also showed normal.
Please help me.
Pict attach
Click to expand...
Click to collapse
I have the same problem, flashing stock rom so many times but sim2 not working "no services"
i try this too :
" adb reboot bootloader(it boots in fastboot),then type: fastboot erase modemst1 and then: fastboot erase modemst2,then:fastboot erase cache and then fastboot reboot"
but not solved the problem......trying with ####862# then select my country Code then also not solved the problem.
anyone in here can give me the solution ?

Me2018 said:
After following the procedure I am not left with a bigger problem, the phone can't read simcard, the imei is blank and baseband version unknown. Anyone with a hint on how to restore the imei or another way to get my phone back to reading the simcard?
Click to expand...
Click to collapse
restore the qcn file with QFIL tool u can resote ur imei numbers
https://forum.xda-developers.com/k6-power/help/qcn-file-lenovo-k6-note-t3663024

i think it is basebend issue..firstly you have to have adb&fastboot on your computer,then plug your phone on computer,open adb and type: adb reboot bootloader(it boots in fastboot),then type: fastboot erase modemst1 and then: fastboot erase modemst2,then:fastboot erase cache and then fastboot reboot..now both sims should work...
Click to expand...
Click to collapse
I got my baseband unknown and iemi 0 because of this.
somehow i got someone's qcn file of k6 power and flashed it through QFIL, it had someone else's imei number, then i replaced my imei with something called WriteDuelIMEI application, at first it wasn't showing up COM port then i rooted my phone with magisk, and executed the following commands from adb
Code:
adb shell
su
setprop sys.usb.config diag,adb
and bingo, it showed COM port and I wrote both my IMEI numbers and clicked start, it successfully did put both IMEI numbers but still sim cards were off and no network.
Then on next day, I used Lenovo Moto smart Assistant and flashed again with the instructions from it.
after flashing and rebooting, it was showing both of my sim networks.
Though volte isn't working in my phone and never worked before for some reason.
Still it's good enough to make some calls thorugh 2G or 3G networks.
Hope it helps someone.

[Root][Oreo][Guide] How to flash and root G5 with (opt. remove encryption)

Hello guys,
after testing around for days i thought it might be helpfull to post the honestly pretty easy procedure to install stock Oreo, root it and remove encryption if needed.
Disclaimer:
I am not responsible for bricked devices, dead SD-cards, lost data, etc.
Back up your data, app settings, be sure you remember your passwords, your device will be empty!​
Edit: It seems, theres a bug that, if you read this post on XDA labs, won't show you everything, it seems like it randomly skips some parts.
What you need:
Unlocked Bootloader
Motorola USB drivers
15 sec adb and fastboot uploaded by myself since the original links aren't working anymore https://multifilemirror.com/hgxxyrfyd7rx.
I originally got them from here (you may have to go into your device manager and select the adb drivers for your phone f.e. when you want to use adb push in recovery, see original xda site).
This will also install the google drivers.
TWRP 32bit (v.3.2.3-0)
TWRP 64bit (v.3.2.1-0)
Disable Dm-Verity & ForceEncrypt from here
Magisk and MagiskManager. Newest should probably work, i used Magisk-18.0 and MagiskManager-6.1.0
Most recent Oreo firmware (edit 08.19)
(I used this Oreo firmware found in this post)
Steps:
Be sure you backed up your data and app settings, your pictures, downloads, etc. It will all be lost!
Please read all steps before you begin.
Extract the firmware into your adb folder (where you installed adb, should contain 4 files), copy both twrp (32 & 64 bit) in there, too.
Boot into bootloader (hold power+vol down) and open a terminal inside your adb folder (shift+rightclick) and type in
Code:
fastboot flash recovery name_of_twrp64bit_file.img
Boot into recovery (select recovery with vol buttons, then press power) and make a backup of EFS partition and persist folder (use file manager under advanced) and make another backup of system, boot and data and save both backups and persist to your SD-card or better your computer, too.
reboot into bootloader and check if your bootloader version is B.8.31 or above.
If it is B.8.31 or above DON'T FLASH BOOTLOADER!!! Because if you flash bootloader of the same version or below, it would hardbrick your device!
That also means if you f.e. want to downgrade to Nougat, just ignore following lines:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Also, unless youre sure your persist is absolutly ok (check here), please also omit the following lines:
Code:
fastboot erase modemst1
fastboot erase modemst2
They would reset your IMEI and usually it gets restored from your persist, but only if its not buggy.
Even if your persist is fine, as far as i know theres no harm in not using this commands (my persist is fine and i didnt use them).
Now paste following commands in your command promt in adb, in case you are BELOW B.8.31, add the bootloader commands from above between the first and second line:
Code:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Please make sure that it really flashed all sparsechunk 0-8.
Let your phone reboot itself after installation is done, then return to bootloader and flash twrp 64bit:
Code:
fastboot flash recovery name_of_twrp64bit_file.img
Boot into recovery, since your device is encrypted it will ask for a password, click cancel, then go to WIPE and click on FORMAT DATA and confirm with yes.
This will remove the encryption of your data partition.
Go back to twrp main page and click on REBOOT then RECOVERY.
Once back in twrp, either copy Disable Disable_Dm-Verity_ForceEncrypt.zip and Magisk-18.zip and MagiskManager-6.1.apk to your SD-card or use
Code:
adb push name_of_file /external_sd
or
adb push name_of_file /sdcard
to copy the files to your SD-card (external_sd) or Internal-Storage (sdcard). For this you may have to manually configure your adb drivers in device manager, see here under Notes.
In twrp go now to INSTALL and flash "disable-dm-verity&encrypt" an then REBOOT and SYSTEM.
Return to recovery and flash "Magisk-18.0.zip", wipe Cache/Dalvik at the end and reboot System
Once System has rebooted, install MagiskManager-6.1.0.apk from your SD-card.
MagiskManager should say that Magisk is installed and in settings under security, your phone should be decrypted.
Note: MagiskManager will only show full information when it has internet access, all you see without is if Magisk is installed.
If you want to encrypt your device again, do it but flash twrp 32bit, too, if it asks for a password, it should be your usual password which you also have to enter on every boot.
Some explanation:
Why twrp 64bit?
Because twrp 32bit is able to bypass encryption, however, it causes some problems:
In fact, probably every twrp without the bypass encryption feature would work f.e. older 32bit version 3.1.0. but 64bit offers some features as EFS backup.
If you flash 32bit directly it can bypass the standard encryption but formatting data fails every time when you booted System previously.
When you reboot recovery and format data again it works, but it needs to fail first, just rebooting into recovery 2 times doesnt work.
I dont know what would happen if you (after using your phone normally) reboot recovery and f.e. want to do a backup from data, though im sure i testet it out, but i probably forgot.
You need it later when you want to encrypt your phone again, for me it didnt decrypt data after i reencrypted my phone using my password.
Why reboot System between flashing Disable-encryption and Magisk?
If you do not, you get heavy lags in the first 2 minutes after rebooting System, MagiskManager will say that Magisk isnt installed and then your phone will crash and reboot. But after that 2. reboot everything works fine again, Magisk is back, no lags.
I remembered this post from Johny Cipeli, between flashing no-verity and magisk he wrote to reboot, so i tried and it worked without lags and crash.
You don't need to remove encryption:
You can root your phone without flashing Disable_dm-verity_and_force-encrypt, use then twrp 32bit, dont format data, just flash magisk.
I can say that it should work, because that was one of my first attempts (and it worked for me), however i didnt write down what i was doing so i cant tell you step by step.
Additional:
In case you're searching Viper4Arise for Oreo, the Aroma installer won't work, use the Magisk module and install in MagiskManager. You can download it here from Zackptg5
If youre also annoyed by that One-Nav vibration, you can try using ExKernelManager app and activate the powersave mode. Although i think its officially not for G5, the app works, maybe that only refers to the Kernel and not to the app.
I tried Flyhigh Kernel, it didnt boot after flashing it, if you know a working Kernel for G5 which can disable One-Nav vibration, please write an answer.
My device:
Rooted Stock Oreo 8.1.0: OPP28.85-16
Bootloader: B.8.31
Model: XT1676 reteu
Stock Kernel
Thanks to:
Snoop05 for 15 sec adb and fastboot.
TheFixItMan for twrp.
Zackptg5 for "Universal DM-Verity, ForceEncrypt, Disk Quota Disablers".
topjohnwu for Magisk.
freeZbies for Official Oreo 8.1.0 OPP28.85-16 Fastboot Firmware.
Wolfcity, woozie.2007 and TheFixItMan for answering many of my questions!

- reserved -

ok friend, thank you for this. I think you dont need to flash twrp 64, i only flash official twrp 32, which indeed doesnt have the option for backup persist, but only efs. Maybe is someone else that will try your method to decrypt, I will try next time when I flash the stock, maybe to the next patch update. Good luck and A happy new year !!!
---------- Post added at 01:31 AM ---------- Previous post was at 01:26 AM ----------
LE: You cant root without format data partition, because flashing twrp, when twrp decrypt data you cant see anything on data partition, so you need to format it even if dont need to decrypt the phone

Nice guide @G5-User7080 .
For me everything seems to be correct, I can´t say anything device specific as I own a potter but there shouldn´t be big differences.
There´s one sentence I´m not sure about:
G5-User7080 said:
Because if you flash bootloader of the same version or below, it would hardbrick your device!
That also means if you f.e. want to downgrade to Nougat, just ignore following lines.....
Click to expand...
Click to collapse
It´s clear that downgrading the bootloader can hardbrick your device but why should there be any risk in flashing the same bootloader?
If I flash the fastboot firmware I´m on shouldn´t it be ok? Where did you get that information from?
I´m about to do that on a device of a friend of mine , he is rooted on 7.0 and wants to go the way to flash the firmware he´s on and after that take the OTA up to Oreo.
He could flash the Oreo firmware directly but he prefers to use the firmware from which he knows it´s working and is the correct one.
Very careful guy.
Edit: I just recognized that the part you called steps incl.the part I quoted isn't visible in XDA Labs, I'm only able to see it in mobile browser. Also some download links aren't there, on XDA Labs there is only the one for the 64bit recovery visible, not the one for 32bit. Maybe it's some kind of format problem, bb codes or else.

Some screenshots from XDA Labs and Chrome mobile to show the differences.

Wolfcity said:
It´s clear that downgrading the bootloader can hardbrick your device but why should there be any risk in flashing the same bootloader?
If I flash the fastboot firmware I´m on shouldn´t it be ok? Where did you get that information from?
Click to expand...
Click to collapse
I read this more then one time, although i could just find one source for now: "Flashing bootloader of equal or minor version will hardbrick your device" from Oreo Fastboot firmware.
I dont know why flashing bootloader of the same version would do lead to a hardbrick, but didnt want to try it out myself, also i see no problem in not flashing the bootloader when you already have the same version.
Wolfcity said:
Edit: I just recognized that the part you called steps incl.the part I quoted isn't visible in XDA Labs, I'm only able to see it in mobile browser. Also some download links aren't there, on XDA Labs there is only the one for the 64bit recovery visible, not the one for 32bit. Maybe it's some kind of format problem, bb codes or else.
Click to expand...
Click to collapse
Thats weird, i dont have XDA labs (thats the mobile app, right?), i wrote it on XDA desktop version and only used the size, code, color and list tags, hmm maybe it has problems with the sorted list, for every other part i used the unsorted ones with dots instead of numbers.
Quick test:
Test One:
this is made
in an unordered
list, using
list tags
Test Two:
this is now made
in an ordered list
counting from one to four
using list=1 tags
Can you read both lists with each four points?
And thanks for mentioning the bootloader thing,.. i realized i forgot to paste the lines in to flash bootloader in case you are below b8.31 ehee..

Wolfcity said:
Some screenshots from XDA Labs and Chrome mobile to show the differences.
Click to expand...
Click to collapse
wtf, it just skips random parts ?!!!
I have no idea what could cause this.. ill better add a note at the beginning of the post...wow

To flash the same vers of bootloader is not a problem, only the below one will hardbrick the phone

G5-User7080 said:
wtf, it just skips random parts ?!!!
I have no idea what could cause this.. ill better add a note at the beginning of the post...wow
Click to expand...
Click to collapse
Your lists are both readable.
I took a look at the BB codes as it's known that some of them are not working on XDA Labs like SIZE or HIGHLIGHT. In that case the BB codes are shown in the text but there's nothing missing.
Maybe it has something to do with the use of
[*] in your text?
Edit: Have you changed something in your text now? It seems to be complete on XDA Labs now too...

Wolfcity said:
Your lists are both readable.
I took a look at the BB codes as it's known that some of them are not working on XDA Labs like SIZE or HIGHLIGHT. In that case the BB codes are shown in the text but there's nothing missing.
Maybe it has something to do with the use of
[*] in your text?
Edit: Have you changed something in your text now? It seems to be complete on XDA Labs now too...
Click to expand...
Click to collapse
the [*] just create new lines for a list, and yes, i edited it two times, first, i added that one should use the bootloader commands in case of being below b831 and then i added the info about missing things on xda labs, but i didnt change anything on the lists itself,...