Related
I haven't done a factory reset yet but I would love to avoid it if possible.
I went to take a picture of the wife's newly decorated Christmas tree and the stock camera fails to fully start. It behaves as if it can not use the hardware. When I look at the back there is a small red light/laser that refuses to go out unless the phone is rebooted.
I've rebooted the phone a few times and tried Manual Camera and a couple others .. same behavior.
The phone is running 6.0.1 and is rooted.
Anyone seeing this and have any ideas?
Are you using the stock kernel
I am having the same problem. I flashed with the factory image and the camera won't work in any apps. Stock camera, Snapchat, Instagram, etc. Flashlight had not been working from the Quick Settings tiles, but it did work after wiping cache and dalvik in TWRP.
I saw someone mention on reddit that it can be an issue with using NRT to flash (I didn't use it) and something about vendor.img. I reflashed vendor.img and it didn't change anything.
SuperSmashedBro said:
Are you using the stock kernel
Click to expand...
Click to collapse
Yep. With the exception of being rooted and using a few utils like root explorer and recently ... nothing special. I did just notice Google Play Services *****ed and said there was an error but it wasn't specific about the error. I did bounce the cache for Google Play Services after seeing that.
Nothing odd about this phone ... it's been top notch for the last month.
fury683 said:
I am having the same problem. I flashed with the factory image and the camera won't work in any apps. Stock camera, Snapchat, Instagram, etc. Flashlight had not been working from the Quick Settings tiles, but it did work after wiping cache and dalvik in TWRP.
I saw someone mention on reddit that it can be an issue with using NRT to flash (I didn't use it) and something about vendor.img. I reflashed vendor.img and it didn't change anything.
Click to expand...
Click to collapse
I wonder if it's the vendor.img that caused this. Hmm.. I wonder if the vendor.img from 6.0 would sort it. hmm.
aergern said:
I wonder if it's the vendor.img that caused this. Hmm.. I wonder if the vendor.img from 6.0 would sort it. hmm.
Click to expand...
Click to collapse
I am trying a reflash of the factory image again. Will try out the camera upon first boot before proceeding with TWRP/root/Xposed. It's optimizing my apps right now, I'll let you know in a minute.
---------- Post added at 08:49 PM ---------- Previous post was at 08:45 PM ----------
Full reflash (without wiping userdata) with factory image seems to have worked... Now to try proceeding one step at a time with TWRP/root/Xposed to see if it breaks again.
fury683 said:
I am trying a reflash of the factory image again. Will try out the camera upon first boot before proceeding with TWRP/root/Xposed. It's optimizing my apps right now, I'll let you know in a minute.
Click to expand...
Click to collapse
Yeah, I tried flashing the 6.0 vendor.img and Manual Camera started and I got visual but it froze. I did get a complaint that something was wrong with my system. So I'm trying the 6.0.1 vendor.img. Let me know what you find.
I had this issue on 6.0 when I was trying to do systemless root. I was given boot.img options that were modified (L, M and N) L didn't allow root, N borked the camera, M worked. I would think it's the boot.img
aergern said:
Yeah, I tried flashing the 6.0 vendor.img and Manual Camera started and I got visual but it froze. I did get a complaint that something was wrong with my system. So I'm trying the 6.0.1 vendor.img. Let me know what you find.
Click to expand...
Click to collapse
No dice. Reflashing the 6.0.1 vendor.img did squat. I'll wait.
darkamikaze said:
I had this issue on 6.0 when I was trying to do systemless root. I was given boot.img options that were modified (L, M and N) L didn't allow root, N borked the camera, M worked. I would think it's the boot.img
Click to expand...
Click to collapse
So reflashing the system.img and waiting for Chainfire to make a new boot image could be the solution. That kinda sucks but it could be the only solution.
darkamikaze said:
I had this issue on 6.0 when I was trying to do systemless root. I was given boot.img options that were modified (L, M and N) L didn't allow root, N borked the camera, M worked. I would think it's the boot.img
Click to expand...
Click to collapse
I am using the "traditional" root method and used the angler-mdb08k-boot.zip by Chainfire, which is what I have used before.
fury683 said:
I am using the "traditional" root method and used the angler-mdb08k-boot.zip by Chainfire, which is what I have used before.
Click to expand...
Click to collapse
Same here. Using the same root method each time with my Nexus 6 was never an issue.
Damn. hmm.
Using a 6.0 boot.img or kernel will break the camera on 6.0.1. You can use the new supersu 2.61 on the new 6.0.1 update and root works fine and so does the camera
edd247 said:
Using a 6.0 boot.img or kernel will break the camera on 6.0.1. You can use the new supersu 2.61 on the new 6.0.1 update and root works fine and so does the camera
Click to expand...
Click to collapse
Oh. So just flash supersu 2.61 instead of using the boot.img and supersu 2.5x method. Good. I'll give that a whirl.
I just used the 2.61 systemless root and it appears to be working OK. I just flashed Xposed and am rebooting (optimizing apps for the 3rd time tonight...). Process is pretty painless.
Flash factory image (my batch file was modified to NOT wipe userdata (-w removed))
Flash TWRP
Install SuperSU 2.61 from TWRP --- DO NOT INSTALL ROOT FROM TWRP IF/WHEN IT ASKS
---------- Post added at 09:31 PM ---------- Previous post was at 09:19 PM ----------
Xposed installed and it all seems to work OK.
fury683 said:
I just used the 2.61 systemless root and it appears to be working OK. I just flashed Xposed and am rebooting (optimizing apps for the 3rd time tonight...). Process is pretty painless.
Flash factory image (my batch file was modified to NOT wipe userdata (-w removed))
Flash TWRP
Install SuperSU 2.61 from TWRP --- DO NOT INSTALL ROOT FROM TWRP IF/WHEN IT ASKS
---------- Post added at 09:31 PM ---------- Previous post was at 09:19 PM ----------
Xposed installed and it all seems to work OK.
Click to expand...
Click to collapse
I just erased and reflashed each partition except userdata so it's doing it's thing. Once it's back up then I'll just use 2.61 and be done with it.
Thanks. Just hope I don't have to look at the boot animation much longer ...
Anyone try the modified MMB29N boot.img thats on the Unlock/Root/Flash Guide to see if it breaks the camera while rooting traditionally?
fury683 said:
I just used the 2.61 systemless root and it appears to be working OK. I just flashed Xposed and am rebooting (optimizing apps for the 3rd time tonight...). Process is pretty painless.
Flash factory image (my batch file was modified to NOT wipe userdata (-w removed))
Flash TWRP
Install SuperSU 2.61 from TWRP --- DO NOT INSTALL ROOT FROM TWRP IF/WHEN IT ASKS
---------- Post added at 09:31 PM ---------- Previous post was at 09:19 PM ----------
Xposed installed and it all seems to work OK.
Click to expand...
Click to collapse
I did this ...
fastboot erase system
fastboot erase cache
fastboot erase boot
fastboot erase vendor
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
fastboot reboot
Seems to be stuck at the bootloader animation ... so far .. 20 minutes? I shouldn't have to wipe userdata .. right?
captainwahid said:
Anyone try the modified MMB29N boot.img thats on the Unlock/Root/Flash Guide to see if it breaks the camera while rooting traditionally?
Click to expand...
Click to collapse
I used the only Angler boot.img in the list and it worked to root but the camera was screwed.
this one? http://forum.xda-developers.com/showpost.php?p=64004628&postcount=1195
New factory image is up.
https://developer.android.com/preview/download.html
Just put dev preview 3 back on my device, now I need to give this a go, thanks!
Encryptable boot/kernel for NPD56N:
https://www.androidfilehost.com/?fid=24572369242686514
aoaleman said:
Encryptable boot/kernel for NPD56N:
https://www.androidfilehost.com/?fid=24572369242686514
Click to expand...
Click to collapse
So I flash this instead of boot?
aoaleman said:
Encryptable boot/kernel for NPD56N:
https://www.androidfilehost.com/?fid=24572369242686514
Click to expand...
Click to collapse
Does this keep us unencrypted?
Sent from my Nexus 6
-DarkKnight- said:
So I flash this instead of boot?
Click to expand...
Click to collapse
You can if you are decrypted and don't feel like being forced to being encrypted.
---------- Post added at 12:41 PM ---------- Previous post was at 12:41 PM ----------
chopt51 said:
Does this keep us unencrypted?
Sent from my Nexus 6
Click to expand...
Click to collapse
Yes it does. It does not touch your current setup.
aoaleman said:
You can if you are decrypted and don't feel like being forced to being encrypted.
---------- Post added at 12:41 PM ---------- Previous post was at 12:41 PM ----------
Yes it does. It does not touch your current setup.
Click to expand...
Click to collapse
Thank you! I was not sure if I wanted to bite the bullet and go encrypted or wait for an unencrypted zip, but now I dont have to choose!
Also is anyone able to root it yet?
aoaleman said:
Encryptable boot/kernel for NPD56N:
https://www.androidfilehost.com/?fid=24572369242686514
Click to expand...
Click to collapse
Thank you very much indeed. Works very well, dirty flashed np4 system.img in twrp after flashing this boot.img. all good
---------- Post added at 03:28 AM ---------- Previous post was at 03:26 AM ----------
-DarkKnight- said:
Thank you! I was not sure if I wanted to bite the bullet and go encrypted or wait for an unencrypted zip, but now I dont have to choose!
Also is anyone able to root it yet?
Click to expand...
Click to collapse
Yes, rooted with beta su 2.74
madsurgeon said:
Thank you very much indeed. Works very well, dirty flashed np4 system.img in twrp after flashing this boot.img. all good
---------- Post added at 03:28 AM ---------- Previous post was at 03:26 AM ----------
Yes, rooted with beta su 2.74
Click to expand...
Click to collapse
I flashed su 2.74, and its forcing me into "safe mode"
This was my sequence:
1. Reboot to recovery
2. Flash above linked boot.img as boot
3. Reboot recovery
4. Flash system.img
5. Reboot recovery
6. Flash su 2.74
7. Reboot system
madsurgeon said:
This was my sequence:
1. Reboot to recovery
2. Flash above linked boot.img as boot
3. Reboot recovery
4. Flash system.img
5. Reboot recovery
6. Flash su 2.74
7. Reboot system
Click to expand...
Click to collapse
Would I be able to follow that if I was coming from MM and wanted to try preview 4 or is that only for people that were running preview 3 already?
Sent from my Nexus 6 using XDA-Developers mobile app
madsurgeon said:
This was my sequence:
1. Reboot to recovery
2. Flash above linked boot.img as boot
3. Reboot recovery
4. Flash system.img
5. Reboot recovery
6. Flash su 2.74
7. Reboot system
Click to expand...
Click to collapse
Still safe mode :/
MrMiami81 said:
Would I be able to follow that if I was coming from MM and wanted to try preview 4 or is that only for people that were running preview 3 already?
Click to expand...
Click to collapse
You'd have to be on the latest bootloader and maybe radio, then you can wipe data and system and do the above, you can't dirty flash N over M
---------- Post added at 09:48 PM ---------- Previous post was at 09:45 PM ----------
-DarkKnight- said:
Still safe mode :/
Click to expand...
Click to collapse
Try this when in safe mode: power off, reboot to recovery flash su and reboot system
Alternatively(once in recovery from safe mode)
1. Flash boot.img, reboot system then go back and flash su
Or
2. Make nandroid of data, clean flash and restore from tibu/nandroid option
I'm sorry i can't help you further mate, that's the extent of my knowledge about this
madsurgeon said:
You'd have to be on the latest bootloader and maybe radio, then you can wipe data and system and do the above, you can't dirty flash N over M
---------- Post added at 09:48 PM ---------- Previous post was at 09:45 PM ----------
Try this when in safe mode: power off, reboot to recovery flash su and reboot system
Alternatively(once in recovery from safe mode)
1. Flash boot.img, reboot system then go back and flash su
Or
2. Make nandroid of data, clean flash and restore from tibu/nandroid option
I'm sorry i can't help you further mate, that's the extent of my knowledge about this
Click to expand...
Click to collapse
Does adaway and Titanium Backup work using this method on DP4?
QuickInfo said:
Does adaway and Titanium Backup work using this method on DP4?
Click to expand...
Click to collapse
i don't use adaway, i manually push a modified hosts file into system/etc, that works and
tibu seems to restore only data(even with a clean flash), so i install the apk from tibu backup folder and then restore data from tibu
flash directly from Android Developers using adb command.
However, it has been 20 minus and I am still looking at the "Google" sign. Should I try to re-flash it over or keep waiting?
PS. it took me 40 minus+ to wipe data and cache....
madsurgeon said:
i don't use adaway, i manually push a modified hosts file into system/etc, that works and
tibu seems to restore only data(even with a clean flash), so i install the apk from tibu backup folder and then restore data from tibu
Click to expand...
Click to collapse
Titanium Backup will work once you set SELinux to permissive. I did so by using the following zips:
http://forum.xda-developers.com/showpost.php?p=66371718&postcount=7
Anyone having issues with Bluetooth connectivity? I'll be listening to much over Bluetooth and the connection will drop. A few seconds later it will reconnect and continue on.
When it does this, the Bluetooth icon also disappears from the status bar.
Happens in my car (aftermarket Kenwood) and with my insignia Bluetooth speaker.
Sent from my Nexus 6 using Tapatalk
I must be doing this wrong but I get failure every time I try it
Sent from my Nexus 6 using Tapatalk
rgraville said:
Titanium Backup will work once you set SELinux to permissive. I did so by using the following zips:
http://forum.xda-developers.com/showpost.php?p=66371718&postcount=7
Click to expand...
Click to collapse
Thanks! I've been wanting to come back to N for a while now (dumped it when DP2 sucked) but the Titanium restore issue has been keeping me away. This is good news.
After rooting your Moto G Osprey and flashing for example the wrong SU SuperUser zip or not in Systemless mode, a lot of People stuck into a Bootloop and can't get out.
You can get out of this Bootloop by pressing followings:
1. Hold Power Button down until your Phone turns of.
2. Right after it turns of, press and hold only the Volume Down Button.
You should now have access to the Bootloader again.
Einherjer* said:
After rooting your Moto G Osprey and flashing for example the wrong SU SuperUser zip or not in Systemless mode, a lot of People stuck into a Bootloop and can't get out.
You can get out of this Bootloop by pressing followings:
1. Hold Power Button down until your Phone turns of.
2. Right after it turns of, press and hold only the Volume Down Button.
You should now have access to the Bootloader again.
Click to expand...
Click to collapse
I was stuck in the bootloop and now by following your steps..I ended up in fastboot mode...I probably have installed wrong version of superSU zip...so now could u tell what should I do from the fastboot screen....pls help..
UtkKing said:
I was stuck in the bootloop and now by following your steps..I ended up in fastboot mode...I probably have installed wrong versions of supers zip...so now could u tell what should I do from the fastboot screen....pls help..
Click to expand...
Click to collapse
Flash SuperSU correctly... look in my signature for a link to the proper way to root any Moto G 2015 device.
UtkKing said:
I was stuck in the bootloop and now by following your steps..I ended up in fastboot mode...I probably have installed wrong version of superSU zip...so now could u tell what should I do from the fastboot screen....pls help..
Click to expand...
Click to collapse
Try to get into Recovery. I think you mean the Bootloader instead of "Fastboot Mode". From the Bootloader you should have access Into Recovery.
Einherjer* said:
Try to get into Recovery. I think you mean the Bootloader instead of "Fastboot Mode". From the Bootloader you should have access Into Recovery.
Click to expand...
Click to collapse
So from the recovery I should install SuperSU 2.78 by writing :
echo SYSTEMLESS=true>>/data/.supersu
In the terminal of TWRP as stated in the thread posted by acejavelin.
---------- Post added at 08:25 PM ---------- Previous post was at 08:04 PM ----------
acejavelin said:
Flash SuperSU correctly... look in my signature for a link to the proper way to root any Moto G 2015 device.
Click to expand...
Click to collapse
Acejavelin i followed ur thread and installed superSU 2.78 as u said in ur thread...i am now able to boot my device normally..thanx for that...
But i cannot see SuperSU in my app drawer..
Moreover when i installed Root Checker, it showed that my device is not rooted...why is it so??and what should i do now??
UtkKing said:
So from the recovery I should install SuperSU 2.78 by writing :
echo SYSTEMLESS=true>>/data/.supersu
In the terminal of TWRP as stated in the thread posted by acejavelin.
---------- Post added at 08:25 PM ---------- Previous post was at 08:04 PM ----------
Acejavelin i followed ur thread and installed superSU 2.78 as u said in ur thread...i am now able to boot my device normally..thanx for that...
But i cannot see SuperSU in my app drawer..
Moreover when i installed Root Checker, it showed that my device is not rooted...why is it so??and what should i do now??
Click to expand...
Click to collapse
No offense, but did you read the posting?
The echo command doesn't install anything and isn't magic, it creates a file called /data/.supersu that contains the parameter "SYSTEMLESS=true", then you install (flash) SuperSU normally. The installation script for SuperSU sees the file created with the echo command and performs a systemless install. If you look at the pictures attached to the first post, you will see how it should look when done properly.
If that fails (and only if it fails), which does in less than 1% of devices for some reason, find SuperSU 2.62-3 beta and flash it... It must be that EXACT version and it's in post #2 of my rooting method. Once it's up with this version update the app via play store then open the app and update the binary.
acejavelin said:
No offense, but did you read the posting?
The echo command doesn't install anything and isn't magic, it creates a file called /data/.supersu that contains the parameter "SYSTEMLESS=true", then you install (flash) SuperSU normally. The installation script for SuperSU sees the file created with the echo command and performs a systemless install. If you look at the pictures attached to the first post, you will see how it should look when done properly.
If that fails (and only if it fails), which does in less than 1% of devices for some reason, find SuperSU 2.62-3 beta and flash it... It must be that EXACT version and it's in post #2 of my rooting method. Once it's up with this version update the app via play store then open the app and update the binary.
Click to expand...
Click to collapse
Ok so should i flash SuperSU 2.62-3 BETA after creating the file /data/.supersu again with the same method??
---------- Post added at 09:41 PM ---------- Previous post was at 09:25 PM ----------
UtkKing said:
Ok so should i flash SuperSU 2.62-3 BETA after creating the file /data/.supersu again with the same method??
Click to expand...
Click to collapse
Thanx Acejavelin..i flashed the lower version of SuperSU and now it worked...my phone has been rooted and SuperSU has also appeared in the app drawer...thanx again...:good::good:
Btw should i update SuperSU from play store???is it safe to update?
UtkKing said:
Ok so should i flash SuperSU 2.62-3 BETA after creating the file /data/.supersu again with the same method??
---------- Post added at 09:41 PM ---------- Previous post was at 09:25 PM ----------
Thanx Acejavelin..i flashed the lower version of SuperSU and now it worked...my phone has been rooted and SuperSU has also appeared in the app drawer...thanx again...:good::good:
Btw should i update SuperSU from play store???is it safe to update?
Click to expand...
Click to collapse
It's safe, after updating the application, just open it and let it update the su binaries (normal way) automatically. Reboot and you are done.
BTW, you could have flashed the latest one as you have already done the Echo command. The chances of a failure are slim anyway.
Broadcasted from Zeta Reticuli
[GUIDE]FULL ROOT IN NOUGAT MATE 8 (PHH SUPERUSER with TWRP 3.1.0-0)
I created this thread so user can try other alternative root instead of SuperSU. This is full root with decrypted data partition in TWRP without formatting your data partition.
REQUIREMENTS
Unlocked Bootloader
Working and running Nougat (Stock firmware)
TWRP 3.1.0-0 (Nougat) Here (Credit to @surdu_petru & @OldDroid for making it possible to mate 8 & @franzyroy for not giving up hope :good: )
phh's SuperUser Here (config : noverify)
Must in untouched Stock boot
BEFORE PROCEED
BACKUP BACKUP BACKUP your data.
Copy superuser_noverify.zip into mSDCard
STEPS
1. Unlock Bootloader
2. Flash twrp-3.1.0-next-v3.img via ADB
3. Reboot to TWRP (It will take about 30 seconds or less to enter TWRP)
4. Install superuser_noverify.zip
5. Reboot to system
6. Go to playstore and Install phh's SuperUser app
Have fun!!
Cheers
Big Big Thnx To This Method Very very Thnx dexz To This Full Root Owner Of mate 8 Congratulations All
---------- Post added at 10:25 PM ---------- Previous post was at 10:22 PM ----------
dexz Which Rom used c185b560 or c432560 or c636b563 And thnx
misho_20063 said:
Big Big Thnx To This Method Very very Thnx dexz To This Full Root Owner Of mate 8 Congratulations All
---------- Post added at 10:25 PM ---------- Previous post was at 10:22 PM ----------
dexz Which Rom used c185b560 or c432560 or c636b563 And thnx
Click to expand...
Click to collapse
I have tested C636B521/B563, C432B560, AL10C00B577 & TL00C17B575 (in stock firmware). Rest of the region I think should be working.
From the reality of your experience Of this All Rom C636B521/B563, C432B560, AL10C00B577 & TL00C17B575 Which Is Best ?????? And Which Rom Used Now In Phone Use
Interesting.... I gonna perhaps test your method. Because mine works but not for all (like me unfortunalely contrary to what I thought).
---------- Post added 11-03-2017 at 00:26 ---------- Previous post was 10-03-2017 at 23:58 ----------
@dexz
Did you see that? It could help us for the root.
Edit:
I tried but it doesn't work for me with Nougat
misho_20063 said:
From the reality of your experience Of this All Rom C636B521/B563, C432B560, AL10C00B577 & TL00C17B575 Which Is Best ?????? And Which Rom Used Now In Phone Use
Click to expand...
Click to collapse
Currently I'm using C636B563 that's my original region but I personally prefer AL10 because of battery performance slightly better
franzyroy said:
Interesting.... I gonna perhaps test your method. Because mine works but not for all (like me unfortunalely contrary to what I thought).
---------- Post added 11-03-2017 at 00:26 ---------- Previous post was 10-03-2017 at 23:58 ----------
@dexz
Did you see that? It could help us for the root.
Edit:
I tried but it doesn't work for me with Nougat
Click to expand...
Click to collapse
Nice. I will try the link later.
Getting bootloop after rebooting... any idea?
Installation of files was succesfull, no errors in twrp.
Leo_83 said:
Getting bootloop after rebooting... any idea?
Installation of files was succesfull, no errors in twrp.
Click to expand...
Click to collapse
did u format your data before hand?
Sent from my Mate 9 using XDA Labs
eddmecha said:
did u format your data before hand?
Sent from my Mate 9 using XDA Labs
Click to expand...
Click to collapse
Yes followed the steps one by one...
Edit: One thing worth mentioning is that I used the update_data.zip from the russian link, when I orignally installed Nougat this was the only file that worked for me.
Edit2: Redid the steps but used the update_data-zip posted by Sillanwali in his thread to update to nougat C432B560 but I get "Error: 7....."
After the step 4, I preconize to reboot the recovery. It's advised after a "Format data".
Leo_83 said:
Yes followed the steps one by one...
Edit: One thing worth mentioning is that I used the update_data.zip from the russian link, when I orignally installed Nougat this was the only file that worked for me.
Edit2: Redid the steps but used the update_data-zip posted by Sillanwali in his thread to update to nougat C432B560 but I get "Error: 7....."
Click to expand...
Click to collapse
Make sure you are running unmodified stock firmware. As method above only patch boot img and push superuser files. Do not install decrypted boot img. It need untouched stock boot .
Once you completed the steps and reboot to system. It will normally bootloop twice then you will stuck at huawei logo about 3-5mins.
franzyroy said:
After the step 4, I preconize to reboot the recovery. It's advised after a "Format data".
Click to expand...
Click to collapse
It's optional step but normally most of my experiments I don't even need to "reboot to recovery" but I will add it as optional step in OP.
dexz said:
Make sure you are running unmodified stock firmware. As method above only patch boot img and push superuser files. Do not install decrypted boot img. It need untouched stock boot .
Once you completed the steps and reboot to system. It will normally bootloop twice then you will stuck at huawei logo about 3-5mins.
Click to expand...
Click to collapse
It's just not working for me. I was on stock firmware, only unlocked bootloader, I did not install decrypted boot.img.
I left the phone for roughly about 15 min (one Fifa game) in screen, it doesn't get past Huawei logo and I haven't seen it reboot.
Edit: What about the update_full_hw.zip is that not needed after formating data?
Edit2: Tried again but these time rebooting into recovery after formating data as suggested by @franzyroy but it didn't make a difference still bootloop
Leo_83 said:
It's just not working for me. I was on stock firmware, only unlocked bootloader, I did not install decrypted boot.img.
I left the phone for roughly about 15 min (one Fifa game) in screen, it doesn't get past Huawei logo and I haven't seen it reboot.
Edit: What about the update_full_hw.zip is that not needed after formating data?
Click to expand...
Click to collapse
Yes. That's the file we need to install (update_data_*.zip) at step no. 6
Leo_83 said:
Edit2: Tried again but these time rebooting into recovery after formating data as suggested by @franzyroy but it didn't make a difference still bootloop
Click to expand...
Click to collapse
Yes. Doesn't make any difference. That's why I skipped reboot to recovery after format data
dexz said:
Yes. That's the file we need to install (update_data_*.zip) at step no. 6
Click to expand...
Click to collapse
Aha thought it was just the update.zip file my bad *Hides in shame*
Leo_83 said:
Aha thought it was just the update.zip file my bad *Hides in shame*
Click to expand...
Click to collapse
so u actually flash update.zip instead of update_data_hw.zip?
Sent from my Mate 9 using XDA Labs
I setup All Method And Now My Phone Full Rooted 100% And All App With Root Working Well Very Very Thnx Man dexz Congratualtion Of All Owner Mate 8 Final The Root Is Full
misho_20063 said:
I setup All Method And Now My Phone Full Rooted 100% And All App With Root Working Well Very Very Thnx Man dexz Congratualtion Of All Owner Mate 8 Final The Root Is Full
Click to expand...
Click to collapse
I'm glad you got it full root.
Leo_83 said:
Aha thought it was just the update.zip file my bad *Hides in shame*
Click to expand...
Click to collapse
:laugh:
eddmecha said:
so u actually flash update.zip instead of update_data_hw.zip?
Sent from my Mate 9 using XDA Labs
Click to expand...
Click to collapse
Indeed I did lul
dexz said:
:laugh:
Click to expand...
Click to collapse
Working like a charm!! Thanks dexz!
Hello there,
Although we have done these things tens of times recently we are having some issues with the updates if we are rooted and have magisk modules installed.
I just want to write a small guide to overcome these things which might be helpful.
1) Download the full update zip form Settings/system/system updates/ it is downloaded inside Internal/.ota folder which is hidden by default. or download from anywhere and keep in your storage.
2)Install and Open Mixplorer file manager (MANDATORY) from HERE (Trust me its the best file manager Thanks to @HootanParsa ) if you are already on Pie Be on latest blu_spark TWRP V9.100 HERE Thanks to @eng.stk and skip #3
3) Go to .ota folder open the update zip and delete Compitibility.zip (extracting and repacking is not necessary)
4) Go to Magisk Manager and disable all magisk modules. (Mandatory else there will be reboot issue)
5) Reboot to recovery and flash Full update.zip
6) Flash latest Magisk Zip HERE Thanks to @topjohnwu (it keeps your TWRP alive)
7) Reboot System
8) Open Magisk Manager and Enable all modules and reboot your phone
Cheers!!
Note: if you still get reboot issues just keep a latest magisk modules remover in your storage HERE reboot to TWRP and flash it and reboot to system.
Don't forget to smash Thanks Button ??
I believe you need to delete the compatibility zip also to flash in TWRP ?
benny3 said:
I believe you need to delete the compatibility zip also to flash in TWRP ?
Click to expand...
Click to collapse
Yeah it's a must read no 3
intoxicated.mad said:
Yeah it's a must read no 3
Click to expand...
Click to collapse
My bad i missed #3. I'm installing beta 22 as we speak.
benny3 said:
My bad i missed #3. I'm installing beta 22 as we speak.
Click to expand...
Click to collapse
I made it bold for you lol
Might want to fix the link to MiXplorer. It takes you to the the thread, but opens it in reply mode.
Anyone successfully remove webview? Titanium shows Frozen and won't defrost. Debloater works great otherwise.
Sent from my OnePlus5T using XDA Labs
tcat007 said:
Anyone successfully remove webview? Titanium shows Frozen and won't defrost. Debloater works great otherwise.
Sent from my OnePlus5T using XDA Labs
Click to expand...
Click to collapse
On H2OS I did delete that manually and installed bromite webview but it didn't work on OOS, BTW if you keep Chrome you won't have issues I guess.
intoxicated.mad said:
4) Go to Magisk Manager and disable all magisk modules. (Mandatory else there will be reboot issue)
Click to expand...
Click to collapse
And if you forgot to disable the magisk modules(like i did :angel: ), just flash "Magisk Uninstaller" - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445, then the Magisk installer and then.... nooo more rebooting problem.
Thanks for the guide :good:
getting error 7 on twrp you got the link the the stock boot image of pie by any chance??
Dragonlord07 said:
getting error 7 on twrp you got the link the the stock boot image of pie by any chance??
Click to expand...
Click to collapse
Did you use Mixplorer to delete the compatibility.zip??
boot.img will be of no use if you have a corrupted zip
intoxicated.mad said:
Did you use Mixplorer to delete the compatibility.zip??
boot.img will be of no use if you have a corrupted zip
Click to expand...
Click to collapse
did it on a desktop so using 7 zip
---------- Post added at 04:08 PM ---------- Previous post was at 04:05 PM ----------
Dragonlord07 said:
did it on a desktop so using 7 zip
Click to expand...
Click to collapse
nvm it worked
Dragonlord07 said:
did it on a desktop so using 7 zip
---------- Post added at 04:08 PM ---------- Previous post was at 04:05 PM ----------
nvm it worked
Click to expand...
Click to collapse
I had problem with 7 zip that's why I didn't mention,
Glad it worked for you :good:
@intoxicated.mad, FYI I took the Telegram link out of the OP as doing so is no longer allowed.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
Click to expand...
Click to collapse
the Doctor said:
@intoxicated.mad, FYI I took the Telegram link out of the OP as doing so is no longer allowed.
Click to expand...
Click to collapse
Nevermind, I'm sorry for including it
Guide updated with blu_spark TWRP V9.91 link no need to delete compitibility.zip now!! Cheers
Hello, after installing blu_spark TWRP V9.91 i cannot get into Recovery anymore, the screen remains black and the led turns on. I need to restart and then reflash TWRP thru their update application. Im disabling Magisk modules and have even tried setting the core only mode but nothing seem to work. I have tried installing blu_sparks kernel and it works fine, only recovery TWRP does not work. Im stuck not being able to install the ltest update since normal TWRP does not support it and for some reason the process explained in this forum does not work for me. Any ideas? I must be doing something wrong. Thanks in advance.
mestradab said:
Hello, after installing blu_spark TWRP V9.91 i cannot get into Recovery anymore, the screen remains black and the led turns on. I need to restart and then reflash TWRP thru their update application. Im disabling Magisk modules and have even tried setting the core only mode but nothing seem to work. I have tried installing blu_sparks kernel and it works fine, only recovery TWRP does not work. Im stuck not being able to install the ltest update since normal TWRP does not support it and for some reason the process explained in this forum does not work for me. Any ideas? I must be doing something wrong. Thanks in advance.
Click to expand...
Click to collapse
I think you are on Oreo or decrypted and blu_spark TWRP v9.91 isn't compatible with that as far as I know, so ignore that part and try using previous version.
Hi, yes, I'm on Oreo but encrypted. Anyway, I tried with bluspark TWRP 9.85 which actually boots fine but when installing the update I get the same error as with official twrp, some zip compatibility error. I did delete compatibility.zip from the zip file but still doesn't doesnt do the trick.
Regards
mestradab said:
Hi, yes, I'm on Oreo but encrypted. Anyway, I tried with bluspark TWRP 9.85 which actually boots fine but when installing the update I get the same error as with official twrp, some zip compatibility error. I did delete compatibility.zip from the zip file but still doesn't doesnt do the trick.
Regards
Click to expand...
Click to collapse
Did you delete using Mixplorer??
Make sure you follow every word properly