Related
I cant seem to flash Oppo Firmware at all with TWRP it says FAILED!!! every time I try to flash Oppo's Firmware, Full Firmware or OTAs, it says the same thing FAIL!!!. Using TWRP 2.5.0.0 if you have done it, how did you do it? Did you set an special permissions in TWRP or anything?
drvsbsm said:
I cant seem to flash Oppo Firmware at all with TWRP it says FAILED!!! every time I try to flash Oppo's Firmware, Full Firmware or OTAs, it says the same thing FAIL!!!. Using TWRP 2.5.0.0 if you have done it, how did you do it? Did you set an special permissions in TWRP or anything?
Click to expand...
Click to collapse
Delete
drvsbsm said:
I cant seem to flash Oppo Firmware at all with TWRP it says FAILED!!! every time I try to flash Oppo's Firmware, Full Firmware or OTAs, it says the same thing FAIL!!!. Using TWRP 2.5.0.0 if you have done it, how did you do it? Did you set an special permissions in TWRP or anything?
Click to expand...
Click to collapse
Had the same problem, could not install any oppo ota or full roms with TWRP.
In the end i installed CM rom, then installed oppo full, I could then install OTA without problem, but you loose all your data
Left TWRP off for now
Warlord
I don't know why you're having problems my friend. I have installed everything via twrp on my Oppo. As soon as faux123 he wouldn't be doing a CM kernel for now, I downloaded the beta firmware and flashed it in TWRP. No problems here. Maybe another bad download? I did get a fail when I downloaded it to my computer and then transferred it to my phone, but when I downloaded it straight to my phone, I had zero problems.
BTW, what part of Ohio are you in?
housry23 said:
I don't know why you're having problems my friend. I have installed everything via twrp on my Oppo. As soon as faux123 he wouldn't be doing a CM kernel for now, I downloaded the beta firmware and flashed it in TWRP. No problems here. Maybe another bad download? I did get a fail when I downloaded it to my computer and then transferred it to my phone, but when I downloaded it straight to my phone, I had zero problems.
BTW, what part of Ohio are you in?
Click to expand...
Click to collapse
I got it working same problem here, it was a bad transfer to phone from PC because MD5 matched the rom, that's what had me so confused, I transfered it over again and its working. I read your other message over at Oppo forums and I don't think I can stay stock too much longer either. I really hope that faux, or maybe someone else will develop a kernel for custom 4.2.2 roms...........
I'm in Sidney
Whoa Sidney! That's pretty close. Small world. I'm sure we're the only ones on the Dayton area with an oppo lol
Sent from my Find 5 using Tapatalk 4 Beta
So I flashed the 7.1.1 update and everything was fine. I then tried to root through TWRP with the most recent version of recovery and and SuperSu and when I went to reboot it would get to the "Google" splash screen and go back to the warning. I then tried to restore to my Nandroid that I made right before the 7.1.1 flash but it does the same thing. I ended up doing a factory reset, still looping. I tried flashing an old firmware but it still would loop. I got desperate and did a full wipe and then flashed the old firmware from September's update but it still will not boot. I'm a long time lurker I just don't post much. Any help will be appreciated. Thanks in advance!
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
jamaniek said:
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
Click to expand...
Click to collapse
Ahh, great. I tried searching to see if anyone else posted anything, couldn't find it.
jamaniek said:
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
Click to expand...
Click to collapse
Wait are you able to get into Recovery?
ChazLanier said:
Wait are you able to get into Recovery?
Click to expand...
Click to collapse
Nope. And so are other folks.
But if you can, there's still hope to save your device.
What version of twrp were you using?? Also what company makes the storage (not memory) on your device?
jamaniek said:
Nope. And so are other folks.
But if you can, there's still hope to save your device.
Click to expand...
Click to collapse
I can still get into recovery. I just can't get it past the Google splash screen.
ChazLanier said:
I can still get into recovery. I just can't get it past the Google splash screen.
Click to expand...
Click to collapse
Have you tried installing custom ROM, instead of a stock one?
And tell us what @ArminasAnarion asked for. There may be a pattern here. :good:
I haven't tried a custom ROM. I'll try that if I get any down time at work. Also, I'll check for you @ArminasAnarion in a bit.
Might be a noob question, but how do I get the custom rom files over to my phone to flash in recovery?
ChazLanier said:
Might be a noob question, but how do I get the custom rom files over to my phone to flash in recovery?
Click to expand...
Click to collapse
Well if you cant access twrp then your not flashing anything; did you try downloading the latest Nexus 6p factory image and using adb to flash it?? If you need help with that I can lay it out for you. Also there was an efs partition issue with twrp 3.0.2-1 and down so make sure your twrp is 3.0.2-2!
ArminasAnarion said:
Well if you cant access twrp then your not flashing anything; did you try downloading the latest Nexus 6p factory image and using adb to flash it?? If you need help with that I can lay it out for you. Also there was an efs partition issue with twrp 3.0.2-1 and down so make sure your twrp is 3.0.2-2!
Click to expand...
Click to collapse
I can access TWRP. I haven't tried the latest factory image, only September's release. I just tried a custom rom and it gets to the Google screen but then loops just after the G starts to animate.
ChazLanier said:
I can access TWRP. I haven't tried the latest factory image, only September's release. I just tried a custom rom and it gets to the Google screen but then loops just after the G starts to animate.
Click to expand...
Click to collapse
Make sure your using twrp 3.0.2-2; and download the latest factory image for the Nexus 6p (NBD90X) and use adb (fastboot) to flash that whole thing. Extract the files to your android sdk platform tools folder then run the flash-all.bat file. (If you are using a 64gb or 128gb device DONT DO THIS) Only do this with the 32gb model. If its a 64 or 128 model go here -> http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and go to sub section 10. How To Flash The Factory Images (And Return To Stock) (On post two) and follow that.
ArminasAnarion said:
Make sure your using twrp 3.0.2-2; and download the latest factory image for the Nexus 6p (NBD90X) and use adb (fastboot) to flash that whole thing. Extract the files to your android sdk platform tools folder then run the flash-all.bat file. (If you are using a 64gb or 128gb device DONT DO THIS) Only do this with the 32gb model. If its a 64 or 128 model go here -> http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and go to sub section 10. How To Flash The Factory Images (And Return To Stock) (On post two) and follow that.
Click to expand...
Click to collapse
Downloading the image now. I'm familiar on how to flash stock images, they're how I usually do all of my updates.
ChazLanier said:
Downloading the image now. I'm familiar on how to flash stock images, they're how I usually do all of my updates.
Click to expand...
Click to collapse
Oh okay cool! Good luck!
ArminasAnarion said:
What version of twrp were you using?? Also what company makes the storage (not memory) on your device?
Click to expand...
Click to collapse
Samsung storage, and I thought I was on -2 but it seems like I was on -1.
ArminasAnarion said:
Oh okay cool! Good luck!
Click to expand...
Click to collapse
Newest image didn't work either..
Have you tried WugFresh's Nexus Root Toolkit? Not sure if it will work for your situation, but it has an option to restore to factory settings and unroot if you're soft-bricked or bootlooped. Might be worth a shot if everything else isn't working.
FWIW, I successfully updated to 7.1.1 NPF10C and rooted by using fastboot to flash bootloader, radio, boot, system, and vendor. Then used TWRP 3.0.2-2 to flash SuperSU 2.78 SR1. No issues.
Howie Dub said:
Have you tried WugFresh's Nexus Root Toolkit? Not sure if it will work for your situation, but it has an option to restore to factory settings and unroot if you're soft-bricked or bootlooped. Might be worth a shot if everything else isn't working.
Click to expand...
Click to collapse
No luck on this either.
Hi guys
What is the least troublesome way of getting to 7.1.1 rooted/twrp from 6.0 rooted/xposed/unlocked/twrp installed ?
I'm willing to wipe, and would really just like a flashable zip but don't see any.
I'm not that familiar with update.zip's , but it seems like that might be the long way around, is to wipe system, apply the update.zip from ZTE and then accept the latest OTA? I don't know if that overwrites TWRP or whether an update.zip will even apply over TWRP ... ?
thanks for any advice
bluenote73 said:
Hi guys
What is the least troublesome way of getting to 7.1.1 rooted/twrp from 6.0 rooted/xposed/unlocked/twrp installed ?
I'm willing to wipe, and would really just like a flashable zip but don't see any.
I'm not that familiar with update.zip's , but it seems like that might be the long way around, is to wipe system, apply the update.zip from ZTE and then accept the latest OTA? I don't know if that overwrites TWRP or whether an update.zip will even apply over TWRP ... ?
thanks for any advice
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
I don't know if you can get to 7.1.1 yet, but you can get to 7.0. I think you might have to wipe, and XPosed isn't availible for Nougat quite yet. The OTA update from ZTE won't work because your phone doesn't have the stock signature. Most stock ROMs you flash will take away TWRP and replace it with the stock recovery.
Miflash b15 full, take ota, flash twrp and su.
TWRP Flashable B19 (7.1.1) is coming
lafester said:
Miflash b15 full, take ota, flash twrp and su.
Click to expand...
Click to collapse
Thanks I muddled through by applying the B15 update.zip, then taking the OTA, and now I'm trying to get TWRP back and rooted.
bluenote73 said:
Thanks I muddled through by applying the B15 update.zip, then taking the OTA, and now I'm trying to get TWRP back and rooted.
Click to expand...
Click to collapse
You've probably figured it out, but I'll give you this just in case: https://forum.xda-developers.com/axon-7/help/upgraded-2017u-rooted-7-0-to-7-1-1-t3574033
I got the OTA update, and I stand corrected on not being able to receive them.
TheWoerbler said:
You've probably figured it out, but I'll give you this just in case: https://forum.xda-developers.com/axon-7/help/upgraded-2017u-rooted-7-0-to-7-1-1-t3574033
I got the OTA update, and I stand corrected on not being able to receive them.
Click to expand...
Click to collapse
Thanks. It was a new development that I didn't know about that miflash can be used, so once I found where to get it, and got through it's idiosyncracies (what a horrible f-ing app it is) it was smooth sailing.
Hey all.
I'm in need of a bit of help. I have a J5 and was getting sick of being told theres never any space to install apps, so I rooted it hoping to be able to remove the stock apps that come inbuilt like word, excel etc.... Anyway, I then decided to take it a step further and try and install a custom rom, long story short, im stuck with a green screen
I've been googling and following tutorials for hours now and I'm really at the point of giving up, so thought I would reach out incase i'm just over tired from it all and making silly mistakes.
I have TWRP 3.1.1-0 on my phone, I installed Lineage 14.1 figured out how to change the updater-script, green screen. I then installed a stock rom advanced I found here, green screen. I tried Aokp nightly nougat, green screen. After googling green screen I found a post saying its something to do with incompatibility from TWRP and that I need to install lollipop 5.1.1 firmware first before I can change to lilneage 14.1... Ive been googling for ages and I'm either coming to sites that want me to pay to download it at a reasonable speed or wait for hours. I'm a bit dubious as no other rom seems to have worked and I'm not sitting here with an empty phone.
Thanks.
LowKee84 said:
Hey all.
I'm in need of a bit of help. I have a J5 and was getting sick of being told theres never any space to install apps, so I rooted it hoping to be able to remove the stock apps that come inbuilt like word, excel etc.... Anyway, I then decided to take it a step further and try and install a custom rom, long story short, im stuck with a green screen
I've been googling and following tutorials for hours now and I'm really at the point of giving up, so thought I would reach out incase i'm just over tired from it all and making silly mistakes.
I have TWRP 3.1.1-0 on my phone, I installed Lineage 14.1 figured out how to change the updater-script, green screen. I then installed a stock rom advanced I found here, green screen. I tried Aokp nightly nougat, green screen. After googling green screen I found a post saying its something to do with incompatibility from TWRP and that I need to install lollipop 5.1.1 firmware first before I can change to lilneage 14.1... Ive been googling for ages and I'm either coming to sites that want me to pay to download it at a reasonable speed or wait for hours. I'm a bit dubious as no other rom seems to have worked and I'm not sitting here with an empty phone.
Thanks.
Click to expand...
Click to collapse
Flashing LP / MM / N ROMs based on AOSP/LOS over stock MM/ROMs based on stock MM --> green screen.
How to flash MM/N ROMs based on AOSP/LOS:
1) Install 5.1.1 stock firmware.
2) Install TWRP 5.1.1 (Nick's or Vince's).
3) Flash the MM/N ROM you want.
#Henkate said:
Flashing LP / MM / N ROMs based on AOSP/LOS over stock MM/ROMs based on stock MM --> green screen.
How to flash MM/N ROMs based on AOSP/LOS:
1) Install 5.1.1 stock firmware.
2) Install TWRP 5.1.1 (Nick's or Vince's).
3) Flash the MM/N ROM you want.
Click to expand...
Click to collapse
Don't suppose you know where I can find a copy, as I said in earlier post all the sites I find either take ages or want paying to upgrade to premium.
LowKee84 said:
Don't suppose you know where I can find a copy, as I said in earlier post all the sites I find either take ages or want paying to upgrade to premium.
Click to expand...
Click to collapse
Updato.
Awesome, went from 3 hour download to 15 minute download, finally some progress, thank you
LowKee84 said:
Awesome, went from 3 hour download to 15 minute download, finally some progress, thank you
Click to expand...
Click to collapse
Meh, tried to install but saying invalid zip file format.
LowKee84 said:
Meh, tried to install but saying invalid zip file format.
Click to expand...
Click to collapse
You extract the .zip and install it with Odin...
#Henkate said:
You extract the .zip and install it with Odin...
Click to expand...
Click to collapse
Okay, done that. So now I can install another rom from twrp or do I do it via odin?
LowKee84 said:
Okay, done that. So now I can install another rom from twrp or do I do it via odin?
Click to expand...
Click to collapse
TWRP.
You install only stock ROM with Odin (.tar format).
#Henkate said:
TWRP.
You install only stock ROM with Odin (.tar format).
Click to expand...
Click to collapse
Okay.
Anything else I need to do first? Do I need to root it again?
LowKee84 said:
Okay.
Anything else I need to do first? Do I need to root it again?
Click to expand...
Click to collapse
Most of the roms comes with root. In case it doesnt have root, you flash it after flashing the ROM.
#Henkate said:
Most of the roms comes with root. In case it doesnt have root, you flash it after flashing the ROM.
Click to expand...
Click to collapse
When I installed 5.1.1 it changed back to android recovery so I had to reinstall twrs recovery, then root again to be able to flash, but this time Lineage 14.1 finally installed
Thank you for your help.
LowKee84 said:
When I installed 5.1.1 it changed back to android recovery so I had to reinstall twrs recovery, then root again to be able to flash, but this time Lineage 14.1 finally installed
Thank you for your help.
Click to expand...
Click to collapse
So... I wanted to remove audioFx as I have no need for it, I had to root again... I tried the same root that I used originally but made it so it kept getting stuck on lineage boot screen and gave me no response on trying to boot to recovery. Any idea what went wrong?
Back to lineage again without root.
LowKee84 said:
So... I wanted to remove audioFx as I have no need for it, I had to root again... I tried the same root that I used originally but made it so it kept getting stuck on lineage boot screen and gave me no response on trying to boot to recovery. Any idea what went wrong?
Back to lineage again without root.
Click to expand...
Click to collapse
Did you flash the official SuperSU module from the lineage site?
No, I used Odin with the cf autoroot for my device.
I had problems with cf auto root, particularly the green screen on boot,try flashing the supersu from their site.
Tried it, used first one on the site, installed okay but can't see the su app anywhere, then tried the x86 version in case but wouldn't install.
Oh never mind, had to enable dev mode and enable root for apps and adb first, there is no actual app. I ran another app and it asked for root permission.
LowKee84 said:
Oh never mind, had to enable dev mode and enable root for apps and adb first, there is no actual app. I ran another app and it asked for root permission.
Click to expand...
Click to collapse
So it works?
It work
Hi. I bought 2nd hand zte axon 7 a2017. I found out it has root access but there was no su app. So downloaded superuser from chainfire from play store and it said binary occupied. Downloaded hardware info app and it suggested busy box is installed, rooted, su is phh su and showed the path where it is located. So downloaded phh su from play store and got full root access.! Good but seems like there is no custom recovery. It is still on stock recovery. Is this even possible..? What is the best way to put custom recovery as I really want a nandroid back up.. Please assist. Thank you
The axon7 has had its EDL programmer released and a leaked ZTE signed TWRP since shortly after the device went on sale. Anything is possible.
I would recommend nuking it... wipe the phone data and then install the latest full official firmware over whatever you have now. Then you can go back and start modding.
Jay_Nz said:
Hi. I bought 2nd hand zte axon 7 a2017. I found out it has root access but there was no su app. So downloaded superuser from chainfire from play store and it said binary occupied. Downloaded hardware info app and it suggested busy box is installed, rooted, su is phh su and showed the path where it is located. So downloaded phh su from play store and got full root access.! Good but seems like there is no custom recovery. It is still on stock recovery. Is this even possible..? What is the best way to put custom recovery as I really want a nandroid back up.. Please assist. Thank you
Click to expand...
Click to collapse
Thanks for replying. Just a thought is it possible to flash twrp on top of the existing set up..? And keep the root as it is.?
Should be, but it's not safe since you do not know the current root method.
Odds are fairly high that you have malware on the device. Be safe, nuke it.
Jay_Nz said:
Thanks for replying. Just a thought is it possible to flash twrp on top of the existing set up..? And keep the root as it is.?
Click to expand...
Click to collapse
Ok thanks for replying. Anti-virus shows device is clean. I'll do a clean one then as recommended . Flash official firmware first then flash twrp and probably will go for magisk root. Wish me luck as power button is mushed in and have to poke it real hard. I don't even know if bootloader is unlocked or not.. Haha
tdm said:
The axon7 has had its EDL programmer released and a leaked ZTE signed TWRP since shortly after the device went on sale. Anything is possible.
Click to expand...
Click to collapse
where to find these solutions??
Check for posts by tenfar for the signed twrp.
The firehose was included in one of the leaked update packages. I don't remember which one. I got my copy by running tcpdump while running tenfar"s twrp flasher.
Druboo666 said:
where to find these solutions??
Click to expand...
Click to collapse
tdm said:
Check for posts by tenfar for the signed twrp.
The firehose was included in one of the leaked update packages. I don't remember which one. I got my copy by running tcpdump while running tenfar"s twrp flasher.
Click to expand...
Click to collapse
also works in B32??i am on b32 and i am stuck with stock recovery as bootloader as been striped from b32 so this will give me TWRP back on B32??
Druboo666 said:
also works in B32??i am on b32 and i am stuck with stock recovery as bootloader as been striped from b32 so this will give me TWRP back on B32??
Click to expand...
Click to collapse
I don't know, you can try.
Jay_Nz said:
Hi. I bought 2nd hand zte axon 7 a2017. I found out it has root access but there was no su app. So downloaded superuser from chainfire from play store and it said binary occupied. Downloaded hardware info app and it suggested busy box is installed, rooted, su is phh su and showed the path where it is located. So downloaded phh su from play store and got full root access.! Good but seems like there is no custom recovery. It is still on stock recovery. Is this even possible..? What is the best way to put custom recovery as I really want a nandroid back up.. Please assist. Thank you
Click to expand...
Click to collapse
I just posted some huge verbose $hit on your previous post, just sayin
Hi, Thank you for your guidance so far. Question - if the previous owner just flashed stock rom then shouldn't g that get rid of root. As you can see from this 2nd post I checked on some root apps and it said it is rooted and su is phh so I downloaded phh su from play store and now rooted apps work fine. Some one pointed out chances of my phone having a malware are quite high so I just want to clean all up and have nandroid g back up. It is an awesome phone. As per your recommendation should I flash using miflash.? Would updating from sd card in phone settings not put it back to complete stock and get rid of root and everything.? When I restart I don't get that device can't be checked for corruption message. I'm on marshmallow at the moment so flashing nougat be ok whether it if from miflash or SD card firmware update.? Appreciate your assistance. Thank you
Yes, if the previous owner flashed stock only, you would not have root. He either flashed a malicious package or "helpfully" pre-rooted it for you. So you have untrusted and unknown, and regardless of what it may seem, not stock software.
There are several "return to stock" threads. I would study a couple to get a feel for how the procedure works and then follow one of them. Here's one I pulled up in a search:
https://forum.xda-developers.com/axon-7/development/rom-guide-how-to-restore-stock-a2017u-t3549227
I can't vouch for it, it's just the first one that popped up. However, it does seem to be very complete both in instructions and flashing everything from the boot stack on up to boot and system.
Note that b20 is rather old now -- I believe it's the first firmware that shipped on the device. You could make an effort to find newer files. But it's not really necessary, as you should get an OTA update notification after you boot into the stock system.
Good luck!
Jay_Nz said:
Hi, Thank you for your guidance so far. Question - if the previous owner just flashed stock rom then shouldn't g that get rid of root. As you can see from this 2nd post I checked on some root apps and it said it is rooted and su is phh so I downloaded phh su from play store and now rooted apps work fine. Some one pointed out chances of my phone having a malware are quite high so I just want to clean all up and have nandroid g back up. It is an awesome phone. As per your recommendation should I flash using miflash.? Would updating from sd card in phone settings not put it back to complete stock and get rid of root and everything.? When I restart I don't get that device can't be checked for corruption message. I'm on marshmallow at the moment so flashing nougat be ok whether it if from miflash or SD card firmware update.? Appreciate your assistance. Thank you
Click to expand...
Click to collapse
Hi thanks for the reply. I downloaded zip from zte and did an update from phone settings, it pumped me to marshmallow but next release version of zte up. Then another Ota and now I'm on nougat. Checked and root access is gone as expected but funnily enough app shows no root access but busy box binary yes.. Don't know if that's normal. Did a full factory reset too. Now I'm on full Chinese variant stock rom unrooted hence getting Ota. I pressed volume and power button together and managed to get to the screen with start in green and text screen. Other options included restart, power off, reboot to recovery and bootloader and it did show bootloader is locked. I'm thinking of unlocking bootloader, installing TWRP, then root through magisk and perhaps change to A2017U (usa firmware)... Fingers crossed. Thanks again..
tdm said:
Yes, if the previous owner flashed stock only, you would not have root. He either flashed a malicious package or "helpfully" pre-rooted it for you. So you have untrusted and unknown, and regardless of what it may seem, not stock software.
There are several "return to stock" threads. I would study a couple to get a feel for how the procedure works and then follow one of them. Here's one I pulled up in a search:
https://forum.xda-developers.com/axon-7/development/rom-guide-how-to-restore-stock-a2017u-t3549227
I can't vouch for it, it's just the first one that popped up. However, it does seem to be very complete both in instructions and flashing everything from the boot stack on up to boot and system.
Note that b20 is rather old now -- I believe it's the first firmware that shipped on the device. You could make an effort to find newer files. But it's not really necessary, as you should get an OTA update notification after you boot into the stock system.
Good luck!
Click to expand...
Click to collapse
But that's for the A2017U... Be careful with that, he can brick his phone or lose signal