Related
Hi Guys, i think that i have softbricked mi Zenpad :silly:
So, i have used KingRoot in order to have root permission, after i have use super_me or something like this in order to change KingUser app with SuperSu app, but after the reboot it has gone in bootloop
I have tried to reset it using standard recovery (by ASUS) but it doesn't works, it is still in bootloop.
Can you help me ? (again :laugh
Thanks to a Jappanase blog i was able to unbrick my tablet and install CM 13.0 without have a funcrional rom: {Mod edit}
------------------------------------------------------------------------
How to solve:
1_ Download the following zips in a folder
Code:
[URL="https://vasy.ru/TWRP/P024/"]https://vasy.ru/TWRP/P024/[/URL] TWRP
[URL="http://4pda.ru/pages/go/?u=http%3A%2...zip&e=48313529"]http://4pda.ru/pages/go/?u=http%3A%2...zip&e=48313529[/URL] CM 13.0
[URL="http://opengapps.org/?download=true&arch=arm&api=6.0&variant=pico"]http://opengapps.org/?download=true&arch=arm&api=6.0&variant=pico[/URL] G APPS
[URL="http://d-h.st/8FqR#"]http://d-h.st/8FqR#[/URL] ADB and other utilities . Thanks to @backwardastep
2_ Move CM 13.0 and G APPS in a sd card and insert it into the tablet
3_ Unzip z380klroot_w_xposed
4_ move the TWRP.img in the "z380klroot_w_xposed" folder
5_ open cmd on Windows and move in the z380klroot folder. Type:
Code:
cd C:\Users\XXX\Desktop\z380klroot_w_xposed
6_ Connect the tablet
7_ Then type:
Code:
fastboot boot twrpxx.xx.xx.img
the tablet will start to looking for a device
8_ Press power + "volume +" in order to put the tablet in recovery (you can also put the tablet in recovery mode before the point 7)
9_ Then it should boot a temporany TWRP
10_ From TWRP wipe all data and install first CM 13.0 and GAPPS as usual
Now you have a working CM 13.0
PS. i noted in the Andmen blog's that exist also an Resurrection Remix
Code:
[URL="https://mega.nz/#F!3JtglKKJ!JIL2MZnzTg1vgW8mLLd8kA"]https://mega.nz/#F!3JtglKKJ!JIL2MZnzTg1vgW8mLLd8kA[/URL]
Custom Kernel CM-13.0
For Asus P024 cm13 Z380KL
NEOX_P024-cm13-v1.0-U700-zram
The problem is twrp can't be touch, the display seems locked
bangdes said:
The problem is twrp can't be touch, the display seems locked
Click to expand...
Click to collapse
yeah, i have exaclty the same problem: http://forum.xda-developers.com/and...z380kl-unrootable-t3213933/page3#post69032596
i'm kinda of stuck :silly:
How do you flash back to ASUS's stock ROM? I downloaded 4.8.0_WW off 4PDA but it gives me an error when trying to flash it via TWRP. Any ideas?
xDark_ said:
How do you flash back to ASUS's stock ROM? I downloaded 4.8.0_WW off 4PDA but it gives me an error when trying to flash it via TWRP. Any ideas?
Click to expand...
Click to collapse
You cannot flash the stock rom from twrp.
Stock roms work only with stock recovery
giorgiofolle said:
You cannot flash the stock rom from twrp.
Stock roms work only with stock recovery
Click to expand...
Click to collapse
So I would have to reflash the stock recovery and use that to flash stock? If I use ASUS's FlashTool would that reset everything back to stock?
Sent from my Samsung SM-G930T using XDA Labs
xDark_ said:
So I would have to reflash the stock recovery and use that to flash stock? If I use ASUS's FlashTool would that reset everything back to stock?
Sent from my Samsung SM-G930T using XDA Labs
Click to expand...
Click to collapse
1. yes, you should flash before the stock recovery and then the stock rom
2. I don't know, i have never used asus flash tool, but i think that you should have anyway the stock recovery file
Again, i repeat, if someone know how copy the stock recovery, i can do it. My tablet have still the stock one and i could copy and post here !
I've tried to flash recovery image in adb fastboot and stock rom in asus flash tool but it doesn't work
Sent from my GT-I9300 using XDA-Developers mobile app
giorgiofolle said:
1. yes, you should flash before the stock recovery and then the stock rom
2. I don't know, i have never used asus flash tool, but i think that you should have anyway the stock recovery file
Again, i repeat, if someone know how copy the stock recovery, i can do it. My tablet have still the stock one and i could copy and post here !
Click to expand...
Click to collapse
bangdes said:
I've tried to flash recovery image in adb fastboot and stock rom in asus flash tool but it doesn't work
Sent from my GT-I9300 using XDA-Developers mobile app
Click to expand...
Click to collapse
Gonna try this:
{Mod edit}
(use GTranslate)
Do you have a link to the stock recovery @bangdes?
Edit: I flashed this (https://www.asus.com/zentalk/tw/thread-147621-3-1.html) and now I just get an ASUS logo that eventually goes to the "Powered by Android" screen. Gonna try flashing stock now.
Edit 2: Gave me an error 7. Gonna try charging it up and flashing it again while I research what's up.
Edit 3: tried booting TWRP over stock recovery and adb sideloading it. finished saying total xfer: 1.09x and booted me to a black screen once I tried rebooting (TWRP gave me a No OS warning) saying it couldn't find drivers for Qualcomm HD-9008. ****, I think I just hard bricked my tablet yet again. Rebooted into driver signature disabled mode and it says "unknown device". Can't even turn off the damn thing.
xDark_ said:
Gonna try this:
{Mod edit}
(use GTranslate)
Do you have a link to the stock recovery @bangdes?
Edit: I flashed this (https://www.asus.com/zentalk/tw/thread-147621-3-1.html) and now I just get an ASUS logo that eventually goes to the "Powered by Android" screen. Gonna try flashing stock now.
Edit 2: Gave me an error 7. Gonna try charging it up and flashing it again while I research what's up.
Edit 3: tried booting TWRP over stock recovery and adb sideloading it, booted me to a black screen once I tried rebooting saying it couldn't find drivers for Qualcomm HD-9008. ****, I think I just hard bricked my tablet yet again. Rebooted into driver signature disabled mode and it says "unknown device". Can't even turn off the damn thing.
Click to expand...
Click to collapse
my z380kl is latest (2016) version and cannot enter to recovery stock, or maybe the stock recovery doesn't exist.. it's weird
bangdes said:
my z380kl is latest (2016) version and cannot enter to recovery stock, or maybe the stock recovery doesn't exist.. it's weird
Click to expand...
Click to collapse
The stock recovery is just an Asus logo I think. That's what it is for me with the flashed recovery using the link above.
Sent from my Samsung SM-G930T using XDA Labs
I've tried thousand time and no luck, I found the stock recovery from 4pda. But I forgot the link
Ok, lil update. Found out a potential unbricking method:
{Mod edit}
Also this thread is just dedicated to this brick: {Mod edit}}
And here's a few others who have the same issue: {Mod edit}
According to a guy who natively speaks Russian, this is a hardbrick that can't be repaired without sending it in to the OEM.
Kinda wish I had a little birdie that could fly into the ASUS office (I've been there, actually pretty nice. Lounge chairs with tablets and phones on display to play with while you wait, and a TV that was playing Finding Nemo in Chinese. Plus staff was nice enough, I just played dumb about what happened lol) and just tell me what exactly I can do to fix this. Even worse, the one year warranty is almost up so I'm gonna have to fork over cash if I send it in to be repaired AGAIN. This makes me want to send this tablet off to repair and sell it off for a NVIDIA Shield or something, Jesus. I got burned by Asus with the ZF2 and yet I still fell into this trap. Same with Samsung, I guess I'm just a masochist or something. Anyways, currently juggling fixing/rooting my S7 along with school work, so it'll be a few days or so until I can start experimenting with this. On a sidenote, damn the OPO is good. Still flies after three years of daily usage
Back to factory firmware
I found pretty good guide here to help restore the z380KL back to factory firmware.
{Mod edit}
squall77 said:
I found pretty good guide here to help restore the z380KL back to factory firmware.
{Mod edit}
Click to expand...
Click to collapse
If you're going to spam, at least make an unbricking tutorial.
xDark_ said:
If you're going to spam, at least make an unbricking tutorial.
Click to expand...
Click to collapse
I apologize if it looks like a spam, I am just suggesting that you should at least try to restore the stock system partition before trying to flash stock rom using TWRP as it does not work with the custom ROM system partition. As far as I have tried I couldn't boot into stock recovery, maybe it doesn't have one on my model. I can only boot into fastboot.
Best bet is to try to boot into custom recovery and restore the stock system partition from a backup file and then flash the stock rom and see whether it works.
squall77 said:
I apologize if it looks like a spam, I am just suggesting that you should at least try to restore the stock system partition before trying to flash stock rom using TWRP as it does not work with the custom ROM system partition. As far as I have tried I couldn't boot into stock recovery, maybe it doesn't have one on my model. I can only boot into fastboot.
Best bet is to try to boot into custom recovery and restore the stock system partition from a backup file and then flash the stock rom and see whether it works.
Click to expand...
Click to collapse
No, I'm asking you that if you're going to spam your own site then at least make a tutorial that's useful, not just a tutorial everyone who wants to flash CM13 already knows how to do.
hi, pls help.
never got to step 9.
after type fastboot boot twrpxx.xx.xx.img, stuck at waiting devices
hafizhans said:
hi, pls help.
never got to step 9.
after type fastboot boot twrpxx.xx.xx.img, stuck at waiting devices
Click to expand...
Click to collapse
Can you boot into ADB normally? Like type in adb devices before you type in any commands
Hello, i accidentally flash twrp on to my phone (should just boot it). Now i dont have stock recovery anymore. i have tried flash my phone using stock recovery i got from here, here and here. but still no luck. anyone can help?
my phone firmware is latest marsmallow. Unlocked Bootloader and Rooted using miaulightouch method.
Thanks,
FRezING
FRezING said:
Hello, i accidentally flash twrp on to my phone (should just boot it). Now i dont have stock recovery anymore. i have tried flash my phone using stock recovery i got from here, here and here. but still no luck. anyone can help?
my phone firmware is latest marsmallow. Unlocked Bootloader and Rooted using miaulightouch method.
Thanks,
FRezING
Click to expand...
Click to collapse
The links you give mostly for L.. I don't know if that will work on M though
Try to extract boot.img from your Asus zip and flash it, root might lost (?)
#sfmbe
Sent from my ASUS_Z00RD using XDA Labs
testeraphy said:
The links you give mostly for L.. I don't know if that will work on M though
Try to extract boot.img from your Asus zip and flash it, root might lost (?)
#sfmbe
Sent from my ASUS_Z00RD using XDA Labs
Click to expand...
Click to collapse
Thanks for reply, ya all of them for Lollipop because i have tried to flash boot.img from stock Marshmallow but still no recovery so i tried using Lollipop still no luck. Yesterday i tried back2stock method the rom flashed sucessfully but still no stock recovery.
Thanks,
FRezING
FRezING said:
Thanks for reply, ya all of them for Lollipop because i have tried to flash boot.img from stock Marshmallow but still no recovery so i tried using Lollipop still no luck. Yesterday i tried back2stock method the rom flashed sucessfully but still no stock recovery.
Thanks,
FRezING
Click to expand...
Click to collapse
So, I'm curious about it, and flash twrp myself just awhile ago...
And got bootloop, really... wait, seriously?
I'm like
How did the other day I'm able to survive this? It boot normally,
After 1st successful boot, flashing root, (I don't remember but just say I'm booting twrp this time), xposed, aware that root lost after reboot, I did my backup here,
Then deciding to start from scratch, installing official Asus, boot normally, flash twrp, rooting,rebooting few times and somehow root intact, install xposed, root lost...
Restart again, install Asus official (I'm not restoring my backup, really, the only thing I know how to install stock is by stock recovery itself) , boot twrp, install root by system, reboot, root intact, xposed, root intact, surfing net, registering xda yesterday, just now replying to your thread, then you can read from above again...
Just few minutes ago, restore recovery from backup (still bootloop though), installing Asus again, and make this reply...
Sorry can't help you, even I'm confused right now
Sent from my ASUS_Z00RD using XDA Labs
testeraphy said:
So, I'm curious about it, and flash twrp myself just awhile ago...
And got bootloop, really... wait, seriously?
I'm like
How did the other day I'm able to survive this? It boot normally,
After 1st successful boot, flashing root, (I don't remember but just say I'm booting twrp this time), xposed, aware that root lost after reboot, I did my backup here,
Then deciding to start from scratch, installing official Asus, boot normally, flash twrp, rooting,rebooting few times and somehow root intact, install xposed, root lost...
Restart again, install Asus official (I'm not restoring my backup, really, the only thing I know how to install stock is by stock recovery itself) , boot twrp, install root by system, reboot, root intact, xposed, root intact, surfing net, registering xda yesterday, just now replying to your thread, then you can read from above again...
Just few minutes ago, restore recovery from backup (still bootloop though), installing Asus again, and make this reply...
Sorry can't help you, even I'm confused right now
Sent from my ASUS_Z00RD using XDA Labs
Click to expand...
Click to collapse
It's ok thanks for your help tho, my phone still usable im just curious why the stock recovery still missing after flashing it via fastboot. u can use back2stock method if bootloop that method really handy no need to wipe anything i use it before when bootloop and my data still there.
FRezING said:
It's ok thanks for your help tho, my phone still usable im just curious why the stock recovery still missing after flashing it via fastboot. u can use back2stock method if bootloop that method really handy no need to wipe anything i use it before when bootloop and my data still there.
Click to expand...
Click to collapse
My phone already recovered by the time I'm replied above, and somehow.. systemless work.. duh
back to topic
Sent from my ASUS_Z00RD using XDA Labs
testeraphy said:
My phone already recovered by the time I'm replied above, and somehow.. systemless work.. duh
back to topic
Sent from my ASUS_Z00RD using XDA Labs
Click to expand...
Click to collapse
How did u fix dat issue? no recovery here and on booting logo it shows invalid boot.img
Plz help
arunperul said:
How did u fix dat issue? no recovery here and on booting logo it shows invalid boot.img
Plz help
Click to expand...
Click to collapse
Sorry, which part?
If about how I got my recovery back then, I don't really understand, let's assume I have my backup that time. now I have my backup, for real.
From what I understand, invalid boot mean either you got broken boot images or locked bootloader, so which one is familiar to you?
Anyway, you can try to flash back stock boot (grab from asus zip) and stock recovery (if you have them, or find on this forum?).
I don't know if locked bootloader can flash boot/recovery, never tried it myself. So, good luck!
Sent from my ASUS_Z00RD using XDA Labs
Hi guys,
I have a honor 6 plus (PE-TL10), it was running EMUI 4. I flashed TWRP 2.8.7 and then wiped all partitions through it(cust,system,etc) then flashed stock recovery back, now i am trying to install EMUI 4.0.1(Android 6.0) via 3 buttons Huawei update but it stops at 5% and fails. Can you guys provide me with any help, I really need it.
Also now when i am trying to wipe data thru stock recovery i get an weird error message at almost 25% saying "reset balong modem setting fail", which making it more difficult to get back stock rom.
Just last question; the Unbrick option in the "HONOR_6_and_6Plus_Multi-Tool", wil it restore the device to stock rom and fully functional state after that or it will miss some parts of the stock rom ?
Many thanks and regards
demonjo2001 said:
Hi guys,
I have a honor 6 plus (PE-TL10), it was running EMUI 4. I flashed TWRP 2.8.7 and then wiped all partitions through it(cust,system,etc) then flashed stock recovery back, now i am trying to install EMUI 4.0.1(Android 6.0) via 3 buttons Huawei update but it stops at 5% and fails. Can you guys provide me with any help, I really need it.
Also now when i am trying to wipe data thru stock recovery i get an weird error message at almost 25% saying "reset balong modem setting fail", which making it more difficult to get back stock rom.
Just last question; the Unbrick option in the "HONOR_6_and_6Plus_Multi-Tool", wil it restore the device to stock rom and fully functional state after that or it will miss some parts of the stock rom ?
Click to expand...
Click to collapse
For you to restore to stock you need to flash boot, recovery, system and cust.
Make sure you have stock boot and recovery to for forced update (3 buttons).
What happens in most of the cases is boot and recovery files are corrupt.
I would try the unbrick of the Multitool. If it fails, I would flash manually all img files for each partition. But using the same firmware version as the last installed one.
Post your results and I will try to help.
1:Extract the ROM with huawei update extractor
2:download latest minimal adb and fastboot drivers and install them
3ut the extracted system.img,recovery.img,cust.img,boot.img and userdata.img into the fastboot.exe folder
4: boot into the fastboot mode
And finally flash the above mentioned imgs one by one with this command
fastboot flash XXX XXX.img
After flashing files type
Fastboot reboot
and every thing should be fine again
Sent from my H30-U10 using Tapatalk
zinko_pt said:
For you to restore to stock you need to flash boot, recovery, system and cust.
Make sure you have stock boot and recovery to for forced update (3 buttons).
What happens in most of the cases is boot and recovery files are corrupt.
I would try the unbrick of the Multitool. If it fails, I would flash manually all img files for each partition. But using the same firmware version as the last installed one.
Post your results and I will try to help.
Click to expand...
Click to collapse
Thank you for answering, I did used Huawei MultiTool and Unbricked my device. I flashed four img files(SYSTEM,CUST,RECOVERY,BOOT) and now i am back to stock rom and running smoothly.
I tried to use force update feature on my device after that but again i got the same result, it stopped at 5% and failed. I guess i will keep it the way it's now.
Many thanks; you guys are awesome!
hamzio7 said:
1:Extract the ROM with huawei update extractor
2:download latest minimal adb and fastboot drivers and install them
3ut the extracted system.img,recovery.img,cust.img,boot.img and userdata.img into the fastboot.exe folder
4: boot into the fastboot mode
And finally flash the above mentioned imgs one by one with this command
fastboot flash XXX XXX.img
After flashing files type
Fastboot reboot
and every thing should be fine again
Sent from my H30-U10 using Tapatalk
Click to expand...
Click to collapse
Thank you, I did that except for userdata.img file, the Huawei MultiTool only mentioned 4 files(system,recovery,boot,cust). Now my device is running back again on stock rom. Should I flash userdata.img file or is it ok?
Just a question that i keep asking myself; inside the stock update.app file there are 22 img files, what do they do? I only flashed four of them so what purpose do the rest serve as? if the device can operate fully functional with four of them!
Many thanks,
demonjo2001 said:
Thank you, I did that except for userdata.img file, the Huawei MultiTool only mentioned 4 files(system,recovery,boot,cust). Now my device is running back again on stock rom. Should I flash userdata.img file or is it ok?
Just a question that i keep asking myself; inside the stock update.app file there are 22 img files, what do they do? I only flashed four of them so what purpose do the rest serve as? if the device can operate fully functional with four of them!
Many thanks,
Click to expand...
Click to collapse
It's for the other partitions like cust, modem etc.
demonjo2001 said:
Thank you, I did that except for userdata.img file, the Huawei MultiTool only mentioned 4 files(system,recovery,boot,cust). Now my device is running back again on stock rom. Should I flash userdata.img file or is it ok?
Just a question that i keep asking myself; inside the stock update.app file there are 22 img files, what do they do? I only flashed four of them so what purpose do the rest serve as? if the device can operate fully functional with four of them!
Many thanks,
Click to expand...
Click to collapse
Don't use any other img file. And don't flash userdata.
If it works, don't change it. ?
Got similar issue on my honor 6. Can't update via SD card method or 3 button after leaving developer preview. Not even OTA updates install. All fail at 5%. So I'm stuck on B830 for now. Will try for a solution later.
goldfinv said:
Got similar issue on my honor 6. Can't update via SD card method or 3 button after leaving developer preview. Not even OTA updates install. All fail at 5%. So I'm stuck on B830 for now. Will try for a solution later.
Click to expand...
Click to collapse
Fastboot woukd be the only choice.
Sent from my honor 5X using XDA Labs
adriansticoid said:
Fastboot woukd be the only choice.
Click to expand...
Click to collapse
I've installed several versions of 6.0 via fastboot. Same thing. I just get stuck on that version. Can't even reinstall same version.
goldfinv said:
I've installed several versions of 6.0 via fastboot. Same thing. I just get stuck on that version. Can't even reinstall same version.
Click to expand...
Click to collapse
What partitions did you flash?
Sent from my Galaxy Tab 3 using XDA Labs
adriansticoid said:
What partitions did you flash?
Click to expand...
Click to collapse
The usual. Boot. System. Recovery. Cust.
goldfinv said:
The usual. Boot. System. Recovery. Cust.
Click to expand...
Click to collapse
No errors in fastboot?
Sent from my Galaxy Tab 3 using XDA Labs
adriansticoid said:
No errors in fastboot?
Click to expand...
Click to collapse
None. Just errors in software update/upgrade. Right now I'm looking into testing different stock recoveries.
goldfinv said:
None. Just errors in software update/upgrade. Right now I'm looking into testing different stock recoveries.
Click to expand...
Click to collapse
Goodluck with it man. I am sorry I can't help you any further as I am new in hsing fastboot. I got used to Odin in Samsung.
Sent from my Galaxy Tab 3 using XDA Labs
goldfinv said:
None. Just errors in software update/upgrade. Right now I'm looking into testing different stock recoveries.
Click to expand...
Click to collapse
There's no other solution, either stock img files or some sort of transitional package.
zinko_pt said:
There's no other solution, either stock img files or some sort of transitional package.
Click to expand...
Click to collapse
Stock is a no go for me. I'll try transition package next. Maybe only just the recovery. Might work for the OP as well.
goldfinv said:
Stock is a no go for me. I'll try transition package next. Maybe only just the recovery. Might work for the OP as well.
Click to expand...
Click to collapse
Let us know if you fixed it.
Sent from my Galaxy Tab 3 using XDA Labs
Same issue with me as well please help me in this case.
zinko_pt said:
For you to restore to stock you need to flash boot, recovery, system and cust.
Make sure you have stock boot and recovery to for forced update (3 buttons).
What happens in most of the cases is boot and recovery files are corrupt.
I would try the unbrick of the Multitool. If it fails, I would flash manually all img files for each partition. But using the same firmware version as the lasthttps://cdn-cf-3.xda-developers.com/images/smilies/frown.gif installed one.
Post your results and I will try to help.
Click to expand...
Click to collapse
Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.
In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app
nhatminhng said:
Hey guys, I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Fastboot format your partitions and use flash-all.bat with a stock Google image.
nhatminhng said:
Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.
MidnightDevil said:
In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
jhs39 said:
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.
Click to expand...
Click to collapse
v12xke said:
Fastboot format your partitions and use flash-all.bat with a stock Google image.
Click to expand...
Click to collapse
Thanks guys for helping. I fixed it.
I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps
fastboot format system
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...
nhatminhng said:
Thanks guys for helping. I fixed it. I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...
Click to expand...
Click to collapse
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.
v12xke said:
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.
Click to expand...
Click to collapse
Yes sir of course I read it. But I dont understand this step.
Open a terminal and navigate to the unzipped system image directory.
Click to expand...
Click to collapse
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.
nhatminhng said:
Yes sir of course I read it. But I dont understand this step.
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.
Click to expand...
Click to collapse
Hi... Here's a pretty good detailed process on how to unlock/flash, etc...
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page549
Also, before using any toolkit, I suggest using manual commands and getting comfortable with it. At least, you learn exactly what command do what! Simply pressing a button in a program may result in a bricked device. Plus with command line you learn something. :good:
@nhatminhng How did you get your phone fixed? is your phone unlocked?
tjchuot287 said:
@nhatminhng How did you get your phone fixed? is your phone unlocked?
Click to expand...
Click to collapse
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.
nhatminhng said:
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.
Click to expand...
Click to collapse
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.
tjchuot287 said:
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.
Click to expand...
Click to collapse
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes i can. I tried to sideload multiple version of OTA but all have failed.
tjchuot287 said:
Yes i can. I tried to sideload multiple version of OTA but all have failed.
Click to expand...
Click to collapse
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.
v12xke said:
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.
Click to expand...
Click to collapse
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Click to expand...
Click to collapse
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.
v12xke said:
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.
Click to expand...
Click to collapse
Now i have unlocked bootloader but the phone keep restart and stuck at logo again. i followed @Heisenberg thread but same result.
Hi!
I'm looking for a way to either root/twrp v1.2.0b02 (coming from stock files), or a way to apply the ota on a twrp'd/rooted v1.2.0b01.
I have tried this guide without luck starting from the point where the tool tries to flash twrp. when the phone tried to reboot into bootloader it just rebooted to the system.
With this guide i can't apply B02 as i get a mismatch error (forgot what the actual message was called).
any ideas?
thanks in advance!
edit: further information: i am currently on 7.1.1 b01 with unlocked-BL/twrp/root thanks to this guide, BUUUT i can not update from that to b02.
when i flash stock recovery and try to update via ota i get a "package mismatch" error during the update installation process while in the (stock-) recovery.
1. Which version are you running?
2. are you already unlocked and
rooted?
If yes, just flash stock recovery with axon7tool and update your system in the usual way. If done, flash back TWRP and supersu. Done.
Gesendet von meinem ZTE A2017U mit Tapatalk
Its a good question. For e.g. I'm on b10 G version rooted. How to come to A2017GV1.2.0B02 rooted?
Just the same. Install stock recovery and follow the update process as described everywhere in this forum.
marcus.linkenbach said:
1. Which version are you running?
2. are you already unlocked and
rooted?
If yes, just flash stock recovery with axon7tool and update your system in the usual way. If done, flash back TWRP and supersu. Done.
Gesendet von meinem ZTE A2017U mit Tapatalk
Click to expand...
Click to collapse
1.
[...]or a way to apply the ota on a twrp'd/rooted v1.2.0b01.
Click to expand...
Click to collapse
2. trying it right now.
edit: results in a package mismatch.
Flaîm said:
1.
2. trying it right now.
edit: results in a package mismatch.
Click to expand...
Click to collapse
What ended in a package mismatch? Flashing the recovery or updating? (Sorry, didn't see your first quote)
Sent from my ZTE A2017U using XDA Labs
marcus.linkenbach said:
What ended in a package mismatch? Flashing the recovery or updating? (Sorry, didn't see your first quote)
Sent from my ZTE A2017U using XDA Labs
Click to expand...
Click to collapse
the update itself.
Hello,
I'm on A2017GV1.2.0B02, and I'd like to root it.
I have installed adb and axon7toolkit, but it seems there's no stock recovery anymore since 7.x firmware. So when I issue adb edl reboot, the phone is just rebooting the OS. :/
Which steps must I follow for rooting my stock A2017GV1.2.0B02 ?
Thanks.
Jeremy-X said:
Hello,
I'm on A2017GV1.2.0B02, and I'd like to root it.
I have installed adb and axon7toolkit, but it seems there's no stock recovery anymore since 7.x firmware. So when I issue adb edl reboot, the phone is just rebooting the OS. :/
Which steps must I follow for rooting my stock A2017GV1.2.0B02 ?
Thanks.
Click to expand...
Click to collapse
the command to edl is: adb reboot edl.
To boot into recovery it's just power + vol+ button.
But since nougat you cannot boot into bootloader anymore. This would be necessary to unlock the bootloader. Therefore you would have to follow the steps I already mentioned in this thread.
Sent from my ZTE A2017U using XDA Labs
---------- Post added at 01:49 PM ---------- Previous post was at 01:41 PM ----------
Flaîm said:
the update itself.
Click to expand...
Click to collapse
B01 is what? Android 7.0 or 7.1.1? If you are already on 7.1.1 you don't have to flash anything. You will receive the update to B02 OTA. Otherwise you have to follow the official steps to get where you want to be. Described a lot on xda.
Sent from my ZTE A2017U using XDA Labs
Thanks for the answer, but there's no recovery for the B02 7.1.1.
Jeremy-X said:
Thanks for the answer, but there's no recovery for the B02 7.1.1.
Click to expand...
Click to collapse
You are triyng to update your sistem with twrp and the stock update.
you need to go back to stock recovery, aply update from system, wait for process and then, reboot edl, and reflash recovery.
then from recovery root
Flaîm said:
I have tried this guide without luck starting from the point where the tool tries to flash twrp. when the phone tried to reboot into bootloader it just rebooted to the system.
Click to expand...
Click to collapse
My stuff was for reinstalling TWRP on an unlocked phone after Nougat deleted it.
You should try axon7toolkit and see if that does the stuff. Another way around would be to downgrade your phone to B10 (Marshmallow) via MiFavor's update by sd thingy, (i'm not 100% sure if it lets you get to mm from nougat, but it's definitely worth a shot) then trying the BL unlock thread (NOT mine!)
Choose an username... said:
My stuff was for reinstalling TWRP on an unlocked phone after Nougat deleted it.
Click to expand...
Click to collapse
ooooh! guess i misinterpreted the guide then. i never had the problem to begin with as i already unlocked my bootloader on 6.0b10.
ayways, i am currently on 7.1.1 b01 with twrp/root thanks to this guide, BUUUT i can not update from that to b02.
when i flash stock recovery and try to update via ota i get a "package mismatch" error during the update installation process inside the (stock-) recovery.
Flaîm said:
ooooh! guess i misinterpreted the guide then. i never had the problem to begin with as i already unlocked my bootloader on 6.0b10.
ayways, i am currently on 7.1.1 b01 with twrp/root thanks to this guide, BUUUT i can not update from that to b02.
when i flash stock recovery and try to update via ota i get a "package mismatch" error during the update installation process inside the (stock-) recovery.
Click to expand...
Click to collapse
Okay that happened to me. By "this guide" you mean what I posted close to the end right? the xda app just shows me the last post lol
Try to download the full B02 package. Some guy mirrored the full package on one of the B02 posts. Then try to use MiFavor's own updater. It worked for me, can't see why you couldn't use that
Choose an username... said:
Okay that happened to me. By "this guide" you mean what I posted close to the end right? the xda app just shows me the last post lol
Click to expand...
Click to collapse
here's the non-bb coded link https://forum.xda-developers.com/axon-7/how-to/guide-reinstall-twrp-root-update-to-t3578552
Choose an username... said:
Try to download the full B02 package. Some guy mirrored the full package on one of the B02 posts. Then try to use MiFavor's own updater. It worked for me, can't see why you couldn't use that
Click to expand...
Click to collapse
didn't see a b02 fota, sorry. mind linking it?
Flaîm said:
ooooh! guess i misinterpreted the guide then. i never had the problem to begin with as i already unlocked my bootloader on 6.0b10.
ayways, i am currently on 7.1.1 b01 with twrp/root thanks to this guide, BUUUT i can not update from that to b02.
when i flash stock recovery and try to update via ota i get a "package mismatch" error during the update installation process inside the (stock-) recovery.
Click to expand...
Click to collapse
enable bootloader unlock in developer settings...
pelelademadera said:
enable bootloader unlock in developer settings...
Click to expand...
Click to collapse
hmm...
(attachment)
Flaîm said:
ooooh! guess i misinterpreted the guide then. i never had the problem to begin with as i already unlocked my bootloader on 6.0b10.
ayways, i am currently on 7.1.1 b01 with twrp/root thanks to this guide, BUUUT i can not update from that to b02.
when i flash stock recovery and try to update via ota i get a "package mismatch" error during the update installation process inside the (stock-) recovery.
Click to expand...
Click to collapse
You'll always get that mismatch regarding what you do or try. You'll need a custom made twrp flashable zip. Tron1 and I have tried to make one but no success. We will try to make a full flashable zip based on the full image.
Even if you flash your stock recovery back and do the OTA, you'll always get a mismatch regardless what others might say.
raystef66 said:
You'll always get that mismatch regarding what you do or try. You'll need a custom made twrp flashable zip. Tron1 and I have tried to make one but no success. We will try to make a full flashable zip based on the full image.
Even if you flash your stock recovery back and do the OTA, you'll always get a mismatch regardless what others might say.
Click to expand...
Click to collapse
that's what i was afraid of.
guess the zips again will be split into bootstack and system like his other flashable images, right?
Flaîm said:
that's what i was afraid of.
guess the zips again will be split into bootstack and system like his other flashable images, right?
Click to expand...
Click to collapse
Most likely.