Hi there, total newb here but slowly learning.
My Moto Z Play from Best Buy(bought on eBay, i.e. don't have receipt and can't take it back), is having issues finding WiFi networks and Bluetooth devices. I am rooted, with xposed, Chinese TWRP.
#1. When I turn on WiFi, I get, "searching for wi-fi networks" forever even though I have wifi at home. I can work around this by going though WiFi>Add Network>Typing in the network name and entering the security & password info in manually. Also, while my wifi is on, and I am connected to my home network, the "searching for wi-fi network" is always showing. Anybody out there with some ideas to fix this? I'm guessing that the hardware works fine since I am able to connect to WiFi, albeit, through the workaround I described.
#2. Secondly, my bluetooth never recognizes "available devices." It simply searches, and searches before stating, "No nearby bluetooth devices were found." Funny thing though, my Macbook can see and pair. I even sent a file from Macbook to the phone. Same as issue #1, I'm guessing the hardware is fine, but something is definitely wrong. Any ideas are welcomed, and if you help me I will click "thank you" or anything else you want as long as I can keep my dignity.
#3. Is it possible a security update might fix these issues? And if so, can I OTA update these updates if I'm rooted?
You're the best
I would do a factory reset first.
What firmware do you have on your device?
You can't flash an ota while rooted, running xposed and with TWRP installed.
Flashfire won't flash it either.
Flashing firmware other than your specific carriers firmware May's cause your phone to loose your IMEI, So don't flash anything if you're not 100% positive.
You'll probably need to flash the modem files.
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
I would do a factory reset first.
What firmware do you have on your device?
You can't flash an ota while rooted, running xposed and with TWRP installed.
Flashfire won't flash it either.
Flashing firmware other than your specific carriers firmware May's cause your phone to loose your IMEI, So don't flash anything if you're not 100% positive.
You'll probably need to flash the modem files.
Sent from my XT1635-02 using [Urid=75858']XDA-Developers Legacy app[/URL]
Click to expand...
Click to collapse
Thank you. I'm not 100% what you mean by firmware, but I'm running Android 6.0.1 and the phone was bought and sold in the U.S. but it's not the Verizon version. Checking the firmware threads I'm fairly sure the stock firmware for this phone isn't available.
natsousa said:
Thank you. I'm not 100% what you mean by firmware, but I'm running Android 6.0.1 and the phone was bought and sold in the U.S. but it's not the Verizon version. Checking the firmware threads I'm fairly sure the stock firmware for this phone isn't available.
Click to expand...
Click to collapse
Go to about phone and you'll see software channel, this is really important because if you pick the wrong firmware package you could end up with a no IMEI phone.
Basically useless.
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
Go to about phone and you'll see software channel, this is really important because if you pick the wrong firmware package you could end up with a no IMEI phone.
Basically useless.
Sent from my XT1635-02 using [/URL]
Click to expand...
Click to collapse
Ok. It says "retus"
Retail us, there's firmware available found here https://mirrors.lolinet.com/firmware/moto/addison/official/RETUS/
Back up your EFS in TWRP and upload it somewhere safe.
Sent from my XT1635-02 using XDA-Developers Legacy app
---------- Post added at 06:02 PM ---------- Previous post was at 06:00 PM ----------
Have you attempted a factory reset?
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
Retail us, there's firmware available found here https://mirrors.lolinet.com/firmware/moto/addison/official/RETUS/
Back up your EFS in TWRP and upload it somewhere safe.
Sent from my XT1635-02 using XDA-Developers Legacy app
---------- Post added at 06:02 PM ---------- Previous post was at 06:00 PM ----------
Have you attempted a factory reset?
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I have not tried factory reset.
0. Do you recommend trying this first, before flashing the firmware?
1. To do this I go through TWRP>Wipe> and wipe data, cache, and Dalvik correct?
2. Will factory resetting remove root, xposed, etc? My guess is yes, but I'm also guessing I can re-root later.
Thank you
Through TWRP is fine, but just do a nandroid prior or even better download the lastest firmware package from the link I gave you.
TWRP isn't allows cooperative, speaking from experience.
Basically after a factory reset you'll set the phone back to the way it came out of the box except TWRP recovery will remain.
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
Through TWRP is fine, but just do a nandroid prior or even better download the lastest firmware package from the link I gave you.
TWRP isn't allows cooperative, speaking from experience.
Basically after a factory reset you'll set the phone back to the way it came out of the box except TWRP recovery will remain.
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'm tempted to just use TWRP because I'm not familiar with the other method. If I did decide to get the file you sent though, do I simply flash it through TWRP?
natsousa said:
I'm tempted to just use TWRP because I'm not familiar with the other method. If I did decide to get the file you sent though, do I simply flash it through TWRP?
Click to expand...
Click to collapse
No they are flashed through fastboot or RSD lite.
Sent from my XT1635-02 using XDA-Developers Legacy app
---------- Post added at 08:25 PM ---------- Previous post was at 08:13 PM ----------
Keep it as simple as possible.
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
No they are flashed through fastboot or RSD lite.
Sent from my XT1635-02 using XDA-Developers Legacy app
---------- Post added at 08:25 PM ---------- Previous post was at 08:13 PM ----------
Keep it as simple as possible.
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
So I downloaded the firmware from your link and flashed through fast boot these commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
I did not flash:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
which some guides recommended I do. After flashing the boot, recovery, system, and oem I still have the same wifi and bluetooth problems. Should I have flashed the second set of commands?
When trying to backup the "system image" through twrp there was always an error. Is it possible that the system image is messed up somehow and this is what is causing the problem? Thanks again
natsousa said:
So I downloaded the firmware from your link and flashed through fast boot these commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
I did not flash:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
which some guides recommended I do. After flashing the boot, recovery, system, and oem I still have the same wifi and bluetooth problems. Should I have flashed the second set of commands?
When trying to backup the "system image" through twrp there was always an error. Is it possible that the system image is messed up somehow and this is what is causing the problem? Thanks again
Click to expand...
Click to collapse
Could be a hardware issue. I would play it safe and not flash any modem or any other files that you didn't flash.
Re flash twrp
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
Could be a hardware issue. I would play it safe and not flash any modem or any other files that you didn't flash.
Re flash twrp
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thank you very much sir. You have been a great help even though I'm still stuck with this problem. I'm guessing that when Nougat comes out maybe it will fix this.
Last questions if you would:
1. Do you think factory reset through recovery might solve anything?
2. There is a security update available. If I update will I still be able to root using the chinese twrp method?
Best
natsousa said:
Thank you very much sir. You have been a great help even though I'm still stuck with this problem. I'm guessing that when Nougat comes out maybe it will fix this.
Last questions if you would:
1. Do you think factory reset through recovery might solve anything?
2. There is a security update available. If I update will I still be able to root using the chinese twrp method?
Best
Click to expand...
Click to collapse
Take the update but you'll have to fully unroot and flash the stock recovery in order for the ota to successfully flash, if you're running xposed or did any ticketing ,then a full flash of all soarsechunks,OEM,recovery and boot IMG should be flashed.
Yap a big pain in the ass.
You can then reflash the Chinese TWRP and re root afterwards.
I wait for the firmware packages to be up loaded and flash it through fastboot.
Sent from my XT1635-02 using XDA-Developers Legacy app
---------- Post added at 04:16 PM ---------- Previous post was at 04:13 PM ----------
I'm trying to get a flash able stock ROM done but I'm waiting till next week to give a try , I'm just to busy this week to experiment.
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
Take the update but you'll have to fully unroot and flash the stock recovery in order for the ota to successfully flash, if you're running xposed or did any ticketing ,then a full flash of all soarsechunks,OEM,recovery and boot IMG should be flashed.
Yap a big pain in the ass.
You can then reflash the Chinese TWRP and re root afterwards.
I wait for the firmware packages to be up loaded and flash it through fastboot.
Sent from my XT1635-02 using XDA-Developers Legacy app
---------- Post added at 04:16 PM ---------- Previous post was at 04:13 PM ----------
I'm trying to get a flash able stock ROM done but I'm waiting till next week to give a try , I'm just to busy this week to experiment.
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I was able to get the wifi and bluetooth working! I factory reset through stock recovery and then wiped cache also and it works now I learned quite a bit through the whole process thanks to you. Beginning to feel somewhat comfortable with some simple developer stuff.
natsousa said:
I was able to get the wifi and bluetooth working! I factory reset through stock recovery and then wiped cache also and it works now I learned quite a bit through the whole process thanks to you. Beginning to feel somewhat comfortable with some simple developer stuff.
Click to expand...
Click to collapse
Just be careful. Glad it worked out.
Sent from my XT1635-02 using XDA-Developers Legacy app
Related
Here's a kernel extracted from
Operator: Customized IT
Network: GENERIC
Version: 32.2.A.0.224 / R9C
ftf
and patched using Tobias Waldvogel's tool from this thread.
Posted here for convenience only. I will not provide any support if anything goes wrong. Should only be used with 32_2_A_0_224 system rom on single sim E6553
All thanks should go to Tobias for his excellent work on his kernel patching tool and to those who provided the utilities that are included.
As always, you flash at your own risk.
Flash in the usual way:
1. unzip boot image. Unzipped file is called boot-patched-RIC-disabled_ivy_32_2_A_0_224.img
2. make sure you have the fastboot utility installed on your computer.
3. boot phone into fastboot mode
4. TEST: fastboot boot boot-patched-RIC-disabled_ivy_32_2_A_0_224.img
5. ONLY IF test successful (Phone boots from image, TWRP can be selected after yellow light, system boots and no issues, flash:
- fastboot flash boot boot-patched-RIC-disabled_ivy_32_2_A_0_224.img
Please, port it for dual sim! E6533
Sent from my E6533 using XDA-Developers mobile app
Running
The kernel is running on My E6553 with 6.0.1. Thanks a lot.
Hi, I have this error:
Can you make a flashable zip with the DRM RESTORE?
jug68 said:
Hi, I have this error:
Click to expand...
Click to collapse
"Too many links" could indicate a USB driver or USB cable issue, but certainly DON'T attempt to flash until you can reliably boot from the image.
You could try a different image to see if there's something wrong with the one I posted?
What about other fastboot commands? Do they work?
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot back into bootloader
Learnincurve said:
"Too many links" could indicate a USB driver or USB cable issue, but certainly DON'T attempt to flash until you can reliably boot from the image.
You could try a different image to see if there's something wrong with the one I posted?
What about other fastboot commands? Do they work?
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot back into bootloader
Click to expand...
Click to collapse
Hi, I managed and flashed kernel, thank you
jug68 said:
Hi, I managed and flashed kernel, thank you
Click to expand...
Click to collapse
Hi Jug68,
Please can you post here what you did to correct the problem? It might help others.
BR.
Learnincurve said:
Hi Jug68,
Please can you post here what you did to correct the problem? It might help others.
BR.
Click to expand...
Click to collapse
Hi Learnincurve,
I just flashed new rom, this time Customized DE-NL 6.0.1 rom (which my Z3+ came from ) which i downloaded with xperifirm, and after that i could flash any kernel!
I think when i flashed customized IT something goes wrong, because i had problem with camera, i could not take video normally, it was laggy and it freezes.
jug68 said:
Hi Learnincurve,
I just flashed new rom, this time Customized DE-NL 6.0.1 rom (which my Z3+ came from ) which i downloaded with xperifirm, and after that i could flash any kernel!
I think when i flashed customized IT something goes wrong, because i had problem with camera, i could not take video normally, it was laggy and it freezes.
Click to expand...
Click to collapse
Thanks for sharing.
BR.
Good afternoon. When I tested the file and did "fastboot boot boot-patched-RIC-disabled_ivy_32_2_A_0_224.img" TWRP can be selected but when I restart does not leave the logo of Sony. Could you help me?
greetings to all
---------- Post added at 04:05 PM ---------- Previous post was at 04:03 PM ----------
I have to delete something when I'm flashing?
Aeroflyer said:
Good afternoon. When I tested the file and did "fastboot boot boot-patched-RIC-disabled_ivy_32_2_A_0_224.img" TWRP can be selected but when I restart does not leave the logo of Sony. Could you help me?
greetings to all
---------- Post added at 04:05 PM ---------- Previous post was at 04:03 PM ----------
I have to delete something when I'm flashing?
Click to expand...
Click to collapse
Are you restarting from TWRP?
BR.
is it work on lock bootloader"?
Learnincurve, I resolved my problem. I flash the new rom and excluded my data, then he began to work well.
So far no anomaly detected. Thank you all
amirh8466 said:
is it work on lock bootloader"?
Click to expand...
Click to collapse
No
BR.
with this kernel I have problems with streaming vídeos. I simply can't watch vídeos on Facebook & Youtube :/
So I just went back to 7.1.2 from O and I tried using the fasboot boot to install tarp but in hanging on the twrp loading screen. I've downgraded all the way to March 7.1.1 and the same issue occurs. Any hel?
Google edition pixel not Verizon
Yes bootloader is unlocked
bennyboy2120 said:
So I just went back to 7.1.2 from O and I tried using the fasboot boot to install tarp but in hanging on the twrp loading screen. I've downgraded all the way to March 7.1.1 and the same issue occurs. Any hel?
Google edition pixel not Verizon
Yes bootloader is unlocked
Click to expand...
Click to collapse
Which version are you trying?
Are you booting to TWRP from fastboot or installing twrp from fastboot?
Try booting to twrp from fastboot and then installing TWRP with the ZIP
Latest version only give me bootloops
twrp-pixel-installer-marlin-3.0.2-0-RC1.zip works for me though.
parakleet said:
Which version are you trying?
Are you booting to TWRP from fastboot or installing twrp from fastboot?
Try booting to twrp from fastboot and then installing TWRP with the ZIP
Latest version only give me bootloops
twrp-pixel-installer-marlin-3.0.2-0-RC1.zip works for me though.
Click to expand...
Click to collapse
I am using the boot command I can't get passed the twrp boot screen unless it takes more then 10 minutes to boot up first time
Sent from my Pixel XL using Tapatalk
bennyboy2120 said:
I am using the boot command I can't get passed the twrp boot screen unless it takes more then 10 minutes to boot up first time
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I'm having the exact same problem as we speak... had it with skipsoft toolkit and doing it manual through adb..
I'm using "twrp-3.0.2-0-RC1-fastboot-marlin.img"
I'm just going to leave it on that start screen for 30ish mins see if anything happens.
btw I also reverted from Android O to N
RedBlueGreen said:
I'm having the exact same problem as we speak... had it with skipsoft toolkit and doing it manual through adb..
I'm using "twrp-3.0.2-0-RC1-fastboot-marlin.img"
Click to expand...
Click to collapse
Keep me posted if you get it, I'm trying some other methods
Sent from my Pixel XL using Tapatalk
RedBlueGreen said:
I'm having the exact same problem as we speak... had it with skipsoft toolkit and doing it manual through adb..
I'm using "twrp-3.0.2-0-RC1-fastboot-marlin.img"
I'm just going to leave it on that start screen for 30ish mins see if anything happens.
btw I also reverted from Android O to N
Click to expand...
Click to collapse
I also went from 7.1.2 back to 7.1.1 March update still had the issue
Sent from my Pixel XL using Tapatalk
bennyboy2120 said:
Keep me posted if you get it, I'm trying some other methods
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Yeap will do. Might try an older version of twrp.img if nothing happens in 30mins
---------- Post added at 04:52 PM ---------- Previous post was at 04:17 PM ----------
bennyboy2120 said:
I also went from 7.1.2 back to 7.1.1 March update still had the issue
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
nothing.. still on the loading screen
RedBlueGreen said:
Yeap will do. Might try an older version of twrp.img if nothing happens in 30mins
---------- Post added at 04:52 PM ---------- Previous post was at 04:17 PM ----------
nothing.. still on the loading screen
Click to expand...
Click to collapse
Weird. I don't know what could be causing it. I'll check partition chance maybe after going to o?
Sent from my Pixel XL using Tapatalk
bennyboy2120 said:
Weird. I don't know what could be causing it. I'll check partition chance maybe after going to o?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
came across this..
https://forum.xda-developers.com/showpost.php?p=72452371&postcount=1769
and this is the thread on how to do it.. (dont understand it)
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
not sure if it has anything to do with it.
---------- Post added at 05:41 PM ---------- Previous post was at 05:22 PM ----------
im in a bootloop now..
dont think ill be able to get out of it
RedBlueGreen said:
came across this..
https://forum.xda-developers.com/showpost.php?p=72452371&postcount=1769
and this is the thread on how to do it.. (dont understand it)
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
not sure if it has anything to do with it.
---------- Post added at 05:41 PM ---------- Previous post was at 05:22 PM ----------
im in a bootloop now..
dont think ill be able to get out of it
Click to expand...
Click to collapse
I'm looking into the VBS now, also looking at partition differences because of the O beta
Sent from my Pixel XL using Tapatalk
bennyboy2120 said:
I'm looking into the VBS now, also looking at partition differences because of the O beta
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
fixed my bootloop... thought i messed up really bad.. Gonna leave it for now.. giving me a headache.
Let me know if you find a fix please <3
It is happening when you revert from O back to N. Now I'm sure most of this is overkill but not sure which part actually resolved it. Here's how I fixed it -
in recovery, format userdata via fastboot (i actually did erase data first, then format data)
switch to the other slot and do the same
Flash latest N factory image
reboot to welcome screen
reboot into recovery
switch to other slot and flashed latest N factory image again (overkill, I know)
reboot to welcome screen
reboot to bootloader
set twrp as boot image and it will boot successfully into temporary twrp
install twrp zip
install the image signer zip
restart to welcome screen
restart to recovery
do steps 1 and 2 again
restart
profit
If you need more specific instructions, let me know and I'll type it out and make it more clear. Good luck.
mattyb65 said:
It is happening when you revert from O back to N. Now I'm sure most of this is overkill but not sure which part actually resolved it. Here's how I fixed it -
in recovery, format userdata via fastboot (i actually did erase data first, then format data)
switch to the other slot and do the same
Flash latest N factory image
reboot to welcome screen
reboot into recovery
switch to other slot and flashed latest N factory image again (overkill, I know)
reboot to welcome screen
reboot to bootloader
set twrp as boot image and it will boot successfully into temporary twrp
install twrp zip
install the image signer zip
restart to welcome screen
restart to recovery
do steps 1 and 2 again
restart
profit
If you need more specific instructions, let me know and I'll type it out and make it more clear. Good luck.
Click to expand...
Click to collapse
What's the command to swap to the other partition? Thank you!!!
Sent from my Pixel XL using Tapatalk
mattyb65 said:
It is happening when you revert from O back to N. Now I'm sure most of this is overkill but not sure which part actually resolved it. Here's how I fixed it -
in recovery, format userdata via fastboot (i actually did erase data first, then format data)
switch to the other slot and do the same
Flash latest N factory image
reboot to welcome screen
reboot into recovery
switch to other slot and flashed latest N factory image again (overkill, I know)
reboot to welcome screen
reboot to bootloader
set twrp as boot image and it will boot successfully into temporary twrp
install twrp zip
install the image signer zip
restart to welcome screen
restart to recovery
do steps 1 and 2 again
restart
profit
If you need more specific instructions, let me know and I'll type it out and make it more clear. Good luck.
Click to expand...
Click to collapse
any chance you could list all the commands?
bennyboy2120 said:
What's the command to swap to the other partition? Thank you!!!
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
to set it to A: fastboot --set-active=_a
to set it to B: fastboot --set-active=_b
---------- Post added at 03:59 PM ---------- Previous post was at 03:57 PM ----------
RedBlueGreen said:
any chance you could list all the commands?
Click to expand...
Click to collapse
Yeah - give me a bit and ill type it out.
---------- Post added at 04:26 PM ---------- Previous post was at 03:59 PM ----------
Ok - here's the list. Let me know if you run into any issues
in recovery, format userdata via fastboot (i actually did erase data first, then format data)
fastboot erase userdata
fastboot format userdata
switch to the other slot and do the same
fastboot --set-active=_a
Flash latest N factory image downloaded from here: https://developers.google.com/android/images I used N2G47O
fastboot flash bootloader bootloader-marlin-8996-012001-1703151359.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-012901-1702171013.img
fastboot reboot-bootloader
fastboot -w update image-marlin-n2g47o.zip
reboot to welcome screen
fastboot reboot
reboot into recovery
switch to other slot and flashed latest N factory image again (overkill, I know)
fastboot --set-active=_b
fastboot flash bootloader bootloader-marlin-8996-012001-1703151359.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-012901-1702171013.img
fastboot reboot-bootloader
fastboot -w update image-marlin-n2g47o.zip
reboot to welcome screen
fastboot reboot
reboot to bootloader
download RC1 image from here https://dl.twrp.me/marlin/ and set twrp as boot image
fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img
once it boots into temporary TWRP, click on install and navigate to RC2 twrp zip
install the verified boot signer zip in TWRP(attached)
restart to welcome screen
restart to recovery
do steps 1 and 2 again
restart
fastboot reboot
profit
mattyb65 said:
to set it to A: fastboot --set-active=_a
to set it to B: fastboot --set-active=_b
---------- Post added at 03:59 PM ---------- Previous post was at 03:57 PM ----------
Yeah - give me a bit and ill type it out.
---------- Post added at 04:26 PM ---------- Previous post was at 03:59 PM ----------
Ok - here's the list. Let me know if you run into any issues
in recovery, format userdata via fastboot (i actually did erase data first, then format data)
fastboot erase userdata
fastboot format userdata
switch to the other slot and do the same
fastboot --set-active=_a
Flash latest N factory image downloaded from here: https://developers.google.com/android/images I used N2G47O
fastboot flash bootloader bootloader-marlin-8996-012001-1703151359.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-012901-1702171013.img
fastboot reboot-bootloader
fastboot -w update image-marlin-n2g47o.zip
reboot to welcome screen
fastboot reboot
reboot into recovery
switch to other slot and flashed latest N factory image again (overkill, I know)
fastboot --set-active=_b
fastboot flash bootloader bootloader-marlin-8996-012001-1703151359.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-012901-1702171013.img
fastboot reboot-bootloader
fastboot -w update image-marlin-n2g47o.zip
reboot to welcome screen
fastboot reboot
reboot to bootloader
download RC1 image from here https://dl.twrp.me/marlin/ and set twrp as boot image
fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img
once it boots into temporary TWRP, click on install and navigate to RC2 twrp zip
install the verified boot signer zip in TWRP(attached)
restart to welcome screen
restart to recovery
do steps 1 and 2 again
restart
fastboot reboot
profit
Click to expand...
Click to collapse
You the man!!!!
Sent from my Pixel XL using Tapatalk
mattyb65 said:
to set it to A: fastboot --set-active=_a
to set it to B: fastboot --set-active=_b
---------- Post added at 03:59 PM ---------- Previous post was at 03:57 PM ----------
Yeah - give me a bit and ill type it out.
---------- Post added at 04:26 PM ---------- Previous post was at 03:59 PM ----------
Ok - here's the list. Let me know if you run into any issues
in recovery, format userdata via fastboot (i actually did erase data first, then format data)
fastboot erase userdata
fastboot format userdata
switch to the other slot and do the same
fastboot --set-active=_a
Flash latest N factory image downloaded from here: https://developers.google.com/android/images I used N2G47O
fastboot flash bootloader bootloader-marlin-8996-012001-1703151359.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-012901-1702171013.img
fastboot reboot-bootloader
fastboot -w update image-marlin-n2g47o.zip
reboot to welcome screen
fastboot reboot
reboot into recovery
switch to other slot and flashed latest N factory image again (overkill, I know)
fastboot --set-active=_b
fastboot flash bootloader bootloader-marlin-8996-012001-1703151359.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-012901-1702171013.img
fastboot reboot-bootloader
fastboot -w update image-marlin-n2g47o.zip
reboot to welcome screen
fastboot reboot
reboot to bootloader
download RC1 image from here https://dl.twrp.me/marlin/ and set twrp as boot image
fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img
once it boots into temporary TWRP, click on install and navigate to RC2 twrp zip
install the verified boot signer zip in TWRP(attached)
restart to welcome screen
restart to recovery
do steps 1 and 2 again
restart
fastboot reboot
profit
Click to expand...
Click to collapse
Where is the Verified Bootloader?
[/COLOR]
bennyboy2120 said:
Where is the Verified Bootloader?
Click to expand...
Click to collapse
last download link.. install it after you install RC2
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
cant get root to work.. always bootloops..
RedBlueGreen said:
[/COLOR]
last download link.. install it after you install RC2
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
cant get root to work.. always bootloops..
Click to expand...
Click to collapse
how are you trying to root?
RedBlueGreen said:
[/COLOR]
last download link.. install it after you install RC2
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
cant get root to work.. always bootloops..
Click to expand...
Click to collapse
You need to flash the boot signer zip. This has been covered in many threads.
https://forum.xda-developers.com/an...-boot-images-android-verified-t3600606/page16
Hello XDA, I am trying to figure out all the steps to get mainly Twrp, Magisk, Viper and, Substratum working correctly without any hiccups. I have been reading the forums all day and trying to get all the files necessary to get all that working and the files to revert to stock if it doesn't work. I know after the Bootloader is unlocked I won't be able to relock it due to no Moto signed boot images. I just don't want to brick it and be here with other problems later.
So far I have done the following
1. Installed ADB and Fastboot + Drivers
2. Done everything to get the code to unlock bootloader
3. Downloaded the files to flash twrp from (https://forum.xda-developers.com/z2-force/development/twrp-3-1-1-0-moto-z2-force-nash-t3687421)
4. Downloaded the latest stock NCX26.122-59-8 to extract the boot img and patch it with Magisk manager from (https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859)
I think I have everything I need to get it rooted. Here's where I get kinda confused. My phone (XT1789-03 Sprint) is on NCXS26.122-59-8-11 November patch (I think the S is for sprint lol). Would It be okay to flash the Magisk patched boot img from the one I downloaded after I unlock the bootloader? Is Twrp necessary? Is there anything else I need to know about? Thanks in advance.
This forum just died? What the hell noone helps anymore???
Sent from my XT1650 using Tapatalk
TWRP is official now. Download the bootable image from https://twrp.me/motorola/motorolamotoz2force.html and the corresponding zip. Boot to twrp and flash the zip. Flash Magisk and install what you want that needs root. Hint: I'd advise the Viper4Android from Magisk modules in the magisk app.
Uzephi said:
Boot to twrp and flash the zip.
Click to expand...
Click to collapse
What do you mean by this? Fastboot flash TWRP, but then flash what zip?
breakerfall said:
What do you mean by this? Fastboot flash TWRP, but then flash what zip?
Click to expand...
Click to collapse
Do NOT flash the twrp img. "Fastboot boot imagename.img" then flash the twrp zip if you wish to have it as your recovery. You can find both on twrp.me.
This hard.. even with instructions u don't know what to flash where and what it will achieve lol. I just want unlock and root. What's the easiest way to do that on sprint z2 force?
So far I understand u need to install twrp to root with magisk, then use twrp to flash magisk Img, then boot up install magisk apk and u should be rooted. Hope I've got that all right.
But do any of the images on this site also unlock gsm on sprint or TMobile?
Sent from my Moto Z (2) using Tapatalk
Uzephi said:
Do NOT flash the twrp img. "Fastboot boot imagename.img" then flash the twrp zip if you wish to have it as your recovery. You can find both on twrp.me.
Click to expand...
Click to collapse
Not trying to be a **** here, but what exactly do you mean by imagename.img? .. the twrp.img file? and if I don't want TWRP as recovery, then are you saying that it will remain stock if I don't flash the twrp.zip file?
I recently did this on an Essential phone, and the process was: fastboot flash TWRP.img, reboot to TWRP (recovery), flash stock boot.img, then flash magisk.zip.
The last phone I rooted/rommed before that was a Nexus 6, and **** was different then.
breakerfall said:
Not trying to be a **** here, but what exactly do you mean by imagename.img? .. the twrp.img file? and if I don't want TWRP as recovery, then are you saying that it will remain stock if I don't flash the twrp.zip file?
I recently did this on an Essential phone, and the process was: fastboot flash TWRP.img, reboot to TWRP (recovery), flash stock boot.img, then flash magisk.zip.
The last phone I rooted/rommed before that was a Nexus 6, and **** was different then.
Click to expand...
Click to collapse
Yes, just boot it. If you flash, your phone will boot to recovery. Don't flash the TWRP image!!
---------- Post added at 07:25 PM ---------- Previous post was at 07:24 PM ----------
jmagi said:
So far I understand u need to install twrp to root with magisk, then use twrp to flash magisk Img, then boot up install magisk apk and u should be rooted. Hope I've got that all right.
Click to expand...
Click to collapse
You don't flash the TWRP.img file!!! You fastboot boot it. It will temp boot to twrp
Uzephi said:
Yes, just boot it. If you flash, your phone will boot to recovery. Don't flash the TWRP image!
Click to expand...
Click to collapse
Ahhhh!
Fastboot boot TWRP.img, then just flash the magisk.zip in TWRP, right?
Thank you!
Also, @jmagi -- you shouldn't have to manually install the magisk apk. Flashing the magisk.zip in TWRP should result in a Magisk app in your "all apps" next time you boot.
Uzephi said:
Yes, just boot it. If you flash, your phone will boot to recovery. Don't flash the TWRP image!!
---------- Post added at 07:25 PM ---------- Previous post was at 07:24 PM ----------
You don't flash the TWRP.img file!!! You fastboot boot it. It will temp boot to twrp
Click to expand...
Click to collapse
Ohhh thats how it works. So i dont have to install twrp from playstore?
Sent from my Moto Z (2) using Tapatalk
jmagi said:
Ohhh thats how it works. So i dont have to install twrp from playstore?
Click to expand...
Click to collapse
No, you don't
Uzephi said:
No, you don't
Click to expand...
Click to collapse
Ok got it thank you. So fastboot boot twrp, and from twrp flash magisk.img then run magisk after bootup.
I too havent rooted a phone since droid4 which was just doubleclick a bat file lol. All this twrp stuff is new to me. Hope i got it right. Love this phone. Might get another one soon and the qwerty keyboard mod is expected on amazon within a couple months. Only reason i upgraded.
Sent from my Moto Z (2) using Tapatalk
jmagi said:
Ok got it thank you. So fastboot boot twrp, and from twrp flash magisk.img then run magisk after bootup.
I too havent rooted a phone since droid4 which was just doubleclick a bat file lol. All this twrp stuff is new to me. Hope i got it right. Love this phone. Might get another one soon and the qwerty keyboard mod is expected on amazon within a couple months. Only reason i upgraded.
Click to expand...
Click to collapse
Some people had issues and needed to wipe user data after flashing magisk
Hi. Sorry for my bad english..
I'm trying to root and setup the TWRP...
When I have install and enter the TWRP I don't have any storage and I can't Backup... And I can't install Magisk... I'm stuck...
Pic.
Someone have a solution?
Regards
you can try different things?
format data partition using twrp.
If that didnt work try flash stock recovery and erase everyting.
Or ompletely reflash everything:
i dont know... but you can try to put this zip (http://oxygenos.oneplus.net.s3.amazonaws.com/O2N_OBT_17801_OXYGEN_SIGN_wipe.zip.zip) on your phone then flash stock recovery and then flash this downloaded zip... it will install OOS 4.7.5 from there reinstall to whatever you were on... But this method will erase everything on your phone!
Going cracy :\ What am I doing wrong?
0kk0 said:
you can try different things?
format data partition using twrp.
If that didnt work try flash stock recovery and erase everyting.
Or ompletely reflash everything:
i dont know... but you can try to put this zip (http://oxygenos.oneplus.net.s3.amazonaws.com/O2N_OBT_17801_OXYGEN_SIGN_wipe.zip.zip) on your phone then flash stock recovery and then flash this downloaded zip... it will install OOS 4.7.5 from there reinstall to whatever you were on... But this method will erase everything on your phone!
Click to expand...
Click to collapse
Thanks for awnser. I will try
Every time I want to get in to TWRP I need to install it again, every time... "fastboot flash recovery twrp.img" ...
BTW The first problem I got was to install the ADB setup and get the files to show up on my c: drive... I think I give up.
SweDunda said:
Every time I want to get in to TWRP I need to install it again, every time... "fastboot flash recovery twrp.img" ...
BTW The first problem I got was to install the ADB setup and get the files to show up on my c: drive... I think I give up.
Click to expand...
Click to collapse
yeah me 2... i also installed drivers then files showed up in windows explorer
And twrp will be replaced on boot/reboot unless you root after flashing twrp with something like magisk...
Can someone please give me a "IDIOT proof" "HOW TO GUIDE" to me ?
Once you're on TWRP, did you flash Magisk just after, before rebooting on system?
If not, you lose twrp at every reboot. You'll be on stock recovery systematically.
abel06 said:
Once you're on TWRP, did you flash Magisk just after, before rebooting on system?
If not, you lose twrp at every reboot. You'll be on stock recovery systematically.
Click to expand...
Click to collapse
The thing is I can't flash anything. My device have no free space. I can't even backup. look at the pics in the first post.
Ah ok, thanks.
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase boot
fastboot erase recovery
And flash this one via fastboot: https://forum.xda-developers.com/oneplus-5/development/twrp-oneplus-5-wip-t3626134
EugenStanis said:
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase boot
fastboot erase recovery
And flash this one via fastboot: https://forum.xda-developers.com/oneplus-5/development/twrp-oneplus-5-wip-t3626134
Click to expand...
Click to collapse
Thanks. But can you explain little more in detail how I´m doing that? It was over 5 years ago I done this things
https://youtu.be/X1D4PhdhAac
What is my problem? :/
**** ME!!!! It will not boot now.... Spinning boot logo... I hope I not bricked it now
what i would do is flash stock recovery... and then format everything
Then flash rom or restore twrp backup or whatever..
i also had this prblem btw
---------- Post added at 07:29 PM ---------- Previous post was at 07:28 PM ----------
i can if you want describe it more if you are noob? joking
0kk0 said:
what i would do is flash stock recovery... and then format everything
Then flash rom or restore twrp backup or whatever..
i also had this prblem btw
---------- Post added at 07:29 PM ---------- Previous post was at 07:28 PM ----------
i can if you want describe it more if you are noob? joking
Click to expand...
Click to collapse
Please tell me how I do that in the best way? A little stressed up now
SweDunda said:
Please tell me how I do that in the best way? A little stressed up now
Click to expand...
Click to collapse
Download:
1) MINIMAL ADB & FASTBOOT : https://goo.gl/UbFXdA
2) STOCK OOS FILE : http://oxygenos.oneplus.net.s3.amazonaws.com/O2N_OBT_17801_OXYGEN_SIGN_wipe.zip.zip
this is nougat 4.7.5 if i remember it correctly
3) Stock Recovery : https://goo.gl/2kmbB7
4) Flash stock recovery (fastboot flash recovery [recoveryfilename.img])
5) In recovery erase everyting incl personal data.
6) fastboot boot [twrpfilename.img]
This wil boot twrp once so you can place OOS rom in internal storage
7) reboot to recovery.. and install zip you just placed on phone.
8) reboot... if everything works, then reinstall twrp codeworkx or blu_spark
9) after flashing twrp...boot to twrp and flash magisk... this will root your phone and this way twrp will not be replaced after first boot with stock recovery.
10) let me know if you have questions or if it worked etc :good:
When I try to bootloader "Powerbutton + volumedown" it say "Your device is corrupt. It can't be trusted and will not boot" ..................... F.U.C.K meee!
try VOLUME UP + POWER
this should send you straight to fastboot
try unlocking your bootloader then is your first prioriy i think
---------- Post added at 07:57 PM ---------- Previous post was at 07:52 PM ----------
if that also doenst work check this thread: https://forum.xda-developers.com/oneplus-5t/help/device-corrupt-trusted-boot-t3718158
0kk0 said:
try VOLUME UP + POWER
this should send you straight to fastboot
try unlocking your bootloader then is your first prioriy i think
Click to expand...
Click to collapse
Thanks! yes I got in to Fastboot and trying to get it unlocked. The device trying to boot again but I do not think it can... Boot logo of death.
I have a USA variant, just got the Oreo / EMUI 8.0 update. Everything is stock.
I got my bootloader unlock code from Honor support (via the Google forms the USA Support tweeted out).
All guides for unlocking the bootloader and rooting are for Nugat (7.0).
I am wondering a few things.
1) Has anyone unlocked/rooted Oreo? What steps did you take? What TWRP version are you using (a link is preferable, if you have one)? Did you use the multi-tool, or directly with adb?
2) What root solution did you use? I prefer SU over magisk (for the ability to use xposed), but I heard SU isn't working, only magisk? What version did you use?
3) What backup system do you use when your phone will wipe everything for unlocking the bootloader? Is the Huawei stock "Backup" app that it comes with any good? Any better ones to use?
Basically there's no walkthrough for rooting with the current setup. It'd be awesome if someone wrote one that was basically:
- Backup using W method (backup app, or alternative).
- Unlock bootloader using X method (adb/multi-tool/whatever).
- Root using Y method (TWRP version, SU or magisk, and version numbers)
- Do Z activity (anything else to flash after? xposed? etc.?)
Any thoughts appreciated.
arebelspy said:
I have a USA variant, just got the Oreo / EMUI 8.0 update. Everything is stock.
I got my bootloader unlock code from Honor support (via the Google forms the USA Support tweeted out).
All guides for unlocking the bootloader and rooting are for Nugat (7.0).
I am wondering a few things.
1) Has anyone unlocked/rooted Oreo? What steps did you take? What TWRP version are you using (a link is preferable, if you have one)? Did you use the multi-tool, or directly with adb?
2) What root solution did you use? I prefer SU over magisk (for the ability to use xposed), but I heard SU isn't working, only magisk? What version did you use?
3) What backup system do you use when your phone will wipe everything for unlocking the bootloader? Is the Huawei stock "Backup" app that it comes with any good? Any better ones to use?
Basically there's no walkthrough for rooting with the current setup. It'd be awesome if someone wrote one that was basically:
- Backup using W method (backup app, or alternative).
- Unlock bootloader using X method (adb/multi-tool/whatever).
- Root using Y method (TWRP version, SU or magisk, and version numbers)
- Do Z activity (anything else to flash after? xposed? etc.?)
Any thoughts appreciated.
Click to expand...
Click to collapse
Already covered in this thread.
https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500
mrmazak said:
Already covered in this thread.
https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500
Click to expand...
Click to collapse
That didn't even cover a fraction of the questions I posted. It *maybe* gave the relevant TWRP build, though even that is in question, as one of the most recent posts was "I couldn't get any of the TWRP versions listed in this thread to work fully. " and suggesting something else.
I'm curious if anyone has actually rooted stock 8.0 and what process they used.
arebelspy said:
That didn't even cover a fraction of the questions I posted. It *maybe* gave the relevant TWRP build, though even that is in question, as one of the most recent posts was "I couldn't get any of the TWRP versions listed in this thread to work fully. " and suggesting something else.
I'm curious if anyone has actually rooted stock 8.0 and what process they used.
Click to expand...
Click to collapse
It also said backup partitions when in twrp image mount, and flash magisk 16 for root.
I'm about to try this same exact thing the twrp Oreo thread is a little confusing.
K easy part done bootloader unlocked
Update: installed twrp. Did a few backups. Flashed magisk. Rooted now restoring apps in titanium backup. Adaway finally and going to clean up system. ? Safety net passes. Just a little confused on how to restore if I end up in a boot loop. I'm trying to backup still in twrp. But can't backup data and I don't see boot.img to backup. So yeah I'm scared.
arebelspy said:
That didn't even cover a fraction of the questions I posted. It *maybe* gave the relevant TWRP build, though even that is in question, as one of the most recent posts was "I couldn't get any of the TWRP versions listed in this thread to work fully. " and suggesting something else.
I'm curious if anyone has actually rooted stock 8.0 and what process they used.
Click to expand...
Click to collapse
I had posted that. Use this TWRP. Flash Magisk 16 through TWRP. Enjoy root.
---------- Post added at 11:45 PM ---------- Previous post was at 11:41 PM ----------
allrockedout said:
K easy part done bootloader unlocked
Update: installed twrp. Did a few backups. Flashed magisk. Rooted now restoring apps in titanium backup. Adaway finally and going to clean up system. Safety net passes. Just a little confused on how to restore if I end up in a boot loop. I'm trying to backup still in twrp. But can't backup data and I don't see boot.img to backup. So yeah I'm scared.
Click to expand...
Click to collapse
Flashing kernel.img and system.img from the Oreo update.zip should completely fix a bootloop/brick. I had messed around and bootlooped one of mine, and had to extract those .img files to flash them through fastboot to restore my phone. It will erase the system though so a backup of data through Titanium Backup should be safe.
ryang872 said:
I had posted that. Use this TWRP. Flash Magisk 16 through TWRP. Enjoy root.
---------- Post added at 11:45 PM ---------- Previous post was at 11:41 PM ----------
Flashing kernel.img and system.img from the Oreo update.zip should completely fix a bootloop/brick. I had messed around and bootlooped one of mine, and had to extract those .img files to flash them through fastboot to restore my phone. It will erase the system though so a backup of data through Titanium Backup should be safe.
Click to expand...
Click to collapse
Where can I get system.img and kernel.img can you share it. I'm barely able to reboot keeps rebooting and booting into safe mode. Takes me like 10 minutes to boot to system. can barely get into twrp
allrockedout said:
Where can I get system.img and kernel.img can you share it. I'm barely able to reboot keeps rebooting and booting into safe mode. Takes me like 10 minutes to boot to system. can barely get into twrp
Click to expand...
Click to collapse
Gonna upload them now. I'll edit this post when they're finished. Did you have root before updating to Oreo?
ryang872 said:
Gonna upload them now. I'll edit this post when they're finished. Did you have root before updating to Oreo?
Click to expand...
Click to collapse
No I waited for Oreo before I rooted. I just rebooted again and booted back to system fine. I made a bunch of backups in twrp. But there useless if you don't have booted.img system and data.
allrockedout said:
No I waited for Oreo before I rooted. I just rebooted again and booted back to system fine. I made a bunch of backups in twrp. But there useless if you don't have booted.img system and data.
Click to expand...
Click to collapse
there is no "boot.img" on oreo.
the traditional boot.img has been split into 2 partitions. kernel.img and ramdisk.img.
mrmazak said:
there is no "boot.img" on oreo.
the traditional boot.img has been split into 2 partitions. kernel.img and ramdisk.img.
Click to expand...
Click to collapse
So we need kernel.img ramdisk.img which is boot. Than we need system and data. How do you flash the kernel and ramdisk when in twrp? I'm guessing ramdisk we select recovery ramdisk...and kernel? I got system and data backed up
Flashing kernel.img through "fastboot flash boot kernel.img" absolutely solved my bootloop/brick problem. I am completely new to Huawei phones so if I'm wrong please don't let me spread misinformation.
---------- Post added at 12:43 AM ---------- Previous post was at 12:41 AM ----------
allrockedout said:
So we need kernel.img ramdisk.img which is boot. Than we need system and data. How do you flash the kernel and ramdisk when in twrp? I'm guessing ramdisk we select recovery ramdisk...and kernel? I got system and data backed up
Click to expand...
Click to collapse
You'd need to flash kernel as boot through fastboot(fastboot flash boot kernel.img). TWRP would be ramdisk (fastboot flash recovery_ramdisk *****.img). System and Data backed up through TWRP can be restored through TWRP. At least those worked for me in restoring a bootloop/brick.
---------- Post added at 01:00 AM ---------- Previous post was at 12:43 AM ----------
allrockedout said:
Where can I get system.img and kernel.img can you share it. I'm barely able to reboot keeps rebooting and booting into safe mode. Takes me like 10 minutes to boot to system. can barely get into twrp
Click to expand...
Click to collapse
system.img kernel.img
EDIT: This is for L34 update.zip. I'm going out on a limb by assuming that all honor 7x/mate se versions are the same minus the modem_***.img files. USE AT YOUR OWN RISK.
allrockedout said:
So we need kernel.img ramdisk.img which is boot. Than we need system and data. How do you flash the kernel and ramdisk when in twrp? I'm guessing ramdisk we select recovery ramdisk...and kernel? I got system and data backed up
Click to expand...
Click to collapse
Each partition is it's own. Kernel is kernel, ramdisk is ramdisk, etc.
Recovery_ramdisk is recovery_ramdisk
I preferred to make each partition backup as images. Using adb shell and DD commands.
I know it is not in this thread. But in the "(nougat) twrp complete" thread.
This is linked in I believe post two. Where it describes making backup useing DD.
But the partitions are different in oroe, so need to use different codes as in that thread.
I just posted almost same thing yesterday with the links.
Use this guide to make back up. But substitute the partition layout from the following link
Oreo layout
I might be putting together a script that does the backup form you . And put it into a zip file that you run as a twrp install.
I like that idea. Now I said it out load, yeah I like it
I made first draft of my dd back up install.
It makes new directory on external card "twrp_backup" then makes dd copies of all 56 partitions. It takes a while to complete. , but gives you all the partitions, as they are. I added echo lines to the script to give you stautus of the backup, but the output is not shown on trwp install window. And it appears to be doing all the lines of the script at same time, not one at a time. So even if the echo commands printed output , it would be all at once.
well hold off on that statement of "it works" 30 minutes plus and still running.
No errors in current log, Adb shell ls (backup directory) shows all partitions. But mtp only showing 42 out of 56.
It appears to be hanging somewhere.
Will update when I find it.
update..
It worked. All 56 partitions backed up. took over an hour. then I realized I had internal storage full of junk. Userdate backup took 23GB.
as long as your data is not so full, should be better time.
maybe someone else can help edit it to be better script.
completed recovery log attached. Truncated to remove screen timeout (sleep and wake messages)
mrmazak said:
I made first draft of my dd back up install.
It makes new directory on external card "twrp_backup" then makes dd copies of all 56 partitions. It takes a while to complete. , but gives you all the partitions, as they are. I added echo lines to the script to give you stautus of the backup, but the output is not shown on trwp install window. And it appears to be doing all the lines of the script at same time, not one at a time. So even if the echo commands printed output , it would be all at once.
well hold off on that statement of "it works" 30 minutes plus and still running.
No errors in current log, Adb shell ls (backup directory) shows all partitions. But mtp only showing 42 out of 56.
It appears to be hanging somewhere.
Will update when I find it.
maybe someone else can help edit it to be better script.
Click to expand...
Click to collapse
To return to stock recovery and factory reset what do I restore? Do I need to wipe anything?
allrockedout said:
To return to stock recovery and factory reset what do I restore? Do I need to wipe anything?
Click to expand...
Click to collapse
none of those would be stock recovery. Because in order to have made that backup, you would have been on twrp. So the backup would be also twrp.
need to get the stock oreo recovery from extracting the recovery_ramdisk from update.app. update.app is in the update.zip of your oreo update. The main zip , not the "public" or "hw" one.
once you have the image. select install menu in twrp. change to install image. And install to "recovery ramdisk" also can be done with fastboot.
mrmazak said:
none of those would be stock recovery. Because in order to have made that backup, you would have been on twrp. So the backup would be also twrp.
need to get the stock oreo recovery from extracting the recovery_ramdisk from update.app. update.app is in the update.zip of your oreo update. The main zip , not the "public" or "hw" one.
once you have the image. select install menu in twrp. change to install image. And install to "recovery ramdisk" also can be done with fastboot.
Click to expand...
Click to collapse
K im downloading the update.zip now from firmware finder. I want to do another clean install magisk is force closing now. I'm using the p10 lite twrp.
---------- Post added at 10:13 AM ---------- Previous post was at 09:39 AM ----------
mrmazak said:
none of those would be stock recovery. Because in order to have made that backup, you would have been on twrp. So the backup would be also twrp.
need to get the stock oreo recovery from extracting the recovery_ramdisk from update.app. update.app is in the update.zip of your oreo update. The main zip , not the "public" or "hw" one.
once you have the image. select install menu in twrp. change to install image. And install to "recovery ramdisk" also can be done with fastboot.
Click to expand...
Click to collapse
im having trouble extracting update.app i cant open it on my pc.
---------- Post added at 10:24 AM ---------- Previous post was at 10:13 AM ----------
allrockedout said:
K im downloading the update.zip now from firmware finder. I want to do another clean install magisk is force closing now. I'm using the p10 lite twrp.
---------- Post added at 10:13 AM ---------- Previous post was at 09:39 AM ----------
im having trouble extracting update.app i cant open it on my pc.
Click to expand...
Click to collapse
im downloading huawei update extractor
K I'm going to extract this
Here is stock recovery ramdisk for Honor 7x USA Oreo. https://drive.google.com/file/d/1IylCAhGs304boVkSXnSRrQQ1B5ozHwcX/view?usp=drivesdk
I haven't tested it yet. Going to flash in twrp. Hopefully boot back into stock recovery and factory reset.
I also extracted kernel.img.
I successfully flashed kernel and ramdisk recovery. I rebooted back into stock recovery. Going to try factory reset now.
?
Wouldnt boot up.
Flashed kernel.img through twrp didnt work had to flash through adb and it seems to be booting now.
HELL YEAH!! ok booted up to system now.