Related
Hi guys,
So it's been quite a long time since I last attempted to root or flash a custom recovery/rom on an android device... So long in fact that I can only remember as far back as the Sony-Ericsson Xperia X8, and the Samsung Galaxy S2.
Since then, I've become VERY rusty because, due to the area of work I'm in, I needed an iPhone (oh jeez was that just torture).
Anyway, I'm now an owner of an 8GB Samsung Galaxy J5 (SM-J500FN) and being quite tech savvy, you can probably guess that I've already run out of the 4GB space provided. So, I've decided to try and jump back into the world of rooting and flashing custom roms/recoveries.
BUT! Because I've been out for so long, my young, naive, scared Sh*tl*ss self has re-emerged, because he's looked through LOADS of threads and guides on how to do this and has gone... NOPE!
So this is why I'm here. I'm very aware that there are loads of guides out there, but I've a few questions about it all, and hopefully with any luck, this could be turned into an AiO (All in One) guide for those just starting with this concept.
Even so. Here's a few things I'd like out of this... First, I'm very much interested in having TWRP as my recovery. I did use CWM back in the day but found it non-user friendly (but that's just me). I'd also like to have either Cyanogen 12.1 or 13 (though I've seen that there are still bugs in 13 whereas 12.1 is virtually bugless).
So here are my questions:
I've read that you need a key to unlock the Samsung Bootloader to enable you to flash TWRP. Is that true with the J5? (NOTE: I did enable OEM Unlocking in the Developer options)
If I flash TWRP, will my phone get completely wiped, or not?
Will KNOX try to interfere with the flashingof TWRP, or once TWRP is flashed, will KNOX generally bugger about with the phone? (I've heard that KNOX will prevent the device from accessing Samsung servers if it deems the device to be "Unofficial")
How likely is it to brick the phone through flashing the recovery?
I know those questions are probably really simply answered in guides but that's not the point of this, I'd rather have somewhere, one place, where people can see all the answers rather than having to go looking for hours and end up getting very scared! xD
Finally:
How do I flash TWRP onto my J5 (SM-J500FN)? (I've seen loads of guides to this all doing it in very weird and colourful ways, but all very, very different!) Please don't point me to some random guide, I'd like more of a lay-mans terms on how to do this as it's all confusing.
How do I flash Cyanogen 12.1/13? (Is this the same as CWM where you click "Install" select the .zip and then it does it for you?
As said above, this is designed mainly for piece of mind, but also a more definitive thread to how to successfully achieve this!
My experience of flashing TWRP is from using the same phone as yourself SM-J500fn and its all really simple.
Please remember that I'm just another guy who uses this site so I'm only sharing my experience of using the same phone.
You have already unlocked the OEM in the developer settings so no need to worry about bootloader like in some other phones.
Make sure that you download the most current version of the recovery that you want to use.
I had trouble with a recovery before and it was just due to the fact that the recovery was not good.
I'm pretty sure that you will lose all warranty from flashing a custom recovery but KNOX has not given me any trouble.
I didn't lose any info off my phone when I simply flashed a recovery only when I either flashed a new ROM via ODIN or a custom ROM via TWRP.
It was a really simple easy thing for me to do. Once i made sure that I had all the drivers and ODIN and TWRP downloaded then out only took a few mins.
Installation of Cm 12.1 was just a case of pressing the correct buttons but I made sure I did a full back up and good wipe before installing.
I have purposely only given you my experience of doing this no guides / downloads etc. I'm not a developer just somebody who enjoys paying around with my Android phone.
Hope that was of some help. I'm happy to share what experience I have.
John
Not sure what guides you have looking, but not the right ones.
1- No key needed to unlock bootloader, only OEM Unlocking
2- TWRP will wipe the partitions you select, but that doesn't mean more user space, the user space partition (internal data) size is fixed
3- KNOX doesn't interfere, KNOX is a system protection on Samsung ROMs
4- If you read the instructions carefully there's problem, it's not that difficult
You need a recovery based on what ROM you will install
[RECOVERY] [TWRP-3.0.2-0] Samsung Galaxy J5 [MM][Android 6.0.1]
[RECOVERY][TWRP 3.0.2-0]TWRP Recovery for Samsung Galaxy J5 (2015) [Android 5.1.1]
Each recovery has is own instructions, just follow and you should have problems, same with custom roms
[ROM][UNOFFICIAL][5.1.1]CyanogenMod 12.1 for Samsung Galaxy J5 (2015)
Thats the only build from source (til now), the others are ports, ports can have more bugs a less security updates and CM updates integration.
***UPDATE***
Thanks to reply, I have now successfully done everything I set out to do, and created follow-up guide!
You can find it HERE
Original Post below:
Hello Everyone!
I'd like to start off saying I used to have a Nexus 4, with TWRP and Lollipop-based CyanogenMod. I was able to install this all by myself, and keep both TWRP and the ROM updated. I also flashed custom radio to unlock the LTE capability on that phone. My tool of choice to help customize the phone was Nexus Root toolkit.
I was able to follow guides posted long ago on these forums, to do what I wanted with the Nexus 4 back in 2013/2014, but it seems I'm not so capable these days. I've hit such a roadblock with lack of root and constant stutters/slowdowns with everyday use on my current device, the Axon 7, that I must get away from the stock software. I heard it was not so easy with other devices, and while a few devs have posted wonderful guides for users, it's just not enough for a true beginner like me. From skimming guides posted, it seems like devs already expect you to have installed custom recovery, or unlocked bootloader. Then when I try to do these things, so I can move onto custom ROM, it seems the guides are out of date or just not step-by-step enough for me to use, and I don't want to take a risk and brick my device trying things that I'm not sure about. I'm a power user through and through, but not so up-to-date or knowledgeable enough to be able to follow the guides already on the forums. Consider me 1 out of 5 on tech level for Android software.
Here's the model/software already on my device: Stock everything, from bootloader and recovery, to ROM.
Model: A2017U, Nougat 7.0 on B15 ROM
What I still need clarification on:
with my device already running on nougat, do I need to install the nougat universal bootloader/radio I saw in earlier guides?
will LineageOS have any downgrades in regard to audio quality, on either the headphone output or speakers?
will my ROM of choice have Daydream VR support? if not what would be needed?
this is not a big deal, but do I need a special app or entire custom ROM if I'm interested in a temporary unroot to use apps like Android Pay?
Here's what I want on my device: TWRP, LineageOS with root.
If anyone, expert users and devs alike, could reply with current known-good info about the following, I and a lot of other users would be eternally grateful:
unlocking the bootloader, installing TWRP, and LineageOS, in a stupidly long but simple step-by-step process.
Quick follow-up info:
What I can do so far: download current LineageOS nightly, correct version of root .zip, and TWRP from official websites
NO, I'm not good with using ADB on Windows to get things done. I had to ask a friend to help me install it on windows, the guide he sent was much easier than the one i was using, and he still had to walk me through how to use it once installed to help me unlock bootloader/root on another device, Zenphone Zoom if anyone is interested.
PLEASE, don't link me to other guides for any part of this process, if the steps are thorough and relevant, please copy here, of course with all due credit given to original poster.
Feel free to let me know if more info about my knowledge level or device is needed to help you work on my request.
Thanks for reading, here's to several years more of everyone enjoying this wonderful device!
ok there is three real steps, but it can be aheadache, mainly because you didn't unlock before going to nougat.
Step 1. Downgrade to B29 Marshmallow - go here https://www.zteusa.com/axon-7/ and on the support tab in software updates is a full B29 software package. Download it, unzip it once, then put the update.zip file on your SD card.
- on the phone, in developers options, turn on OEM unlocking (it is needed to flash from sd card)
- boot phone to recovery, choose update from sd card, pick the update.zip from the sdcard, the phone will flash the B29 software. It is a bit slow, let it do what it needs to do.
Step 2. Unlock phone and install TWRP - go here https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514 download the miflash program, fastboot unlock program, and twrp for B29.
- instructions are all there, just do what it says.
Step 3, Install LineageOS - https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-14-1-zte-axon-7-t3545679 very straight forward. Don't forget to install first the bootloader, then the rom, then gapps.
What makes this so hard is not being easily able to unlock in nougat. Most of us here unlocked way before marshmallow
No need to downgrade to b29.
lafester said:
No need to downgrade to b29.
Click to expand...
Click to collapse
I was thinking this too. Should be as simple as the steps below
1) Flash signed twrp using axonroot tool - this pry's open the door
2) Using twrp, flash fastboot (b20_fbop or something?) - opens door wider
3) Enable usb debugging and oem unlocking in developer options
4) reboot to fastboot/bootloader mode
5) fastboot oem unlock - door is now wide open
Done.
gpz1100 said:
I was thinking this too. Should be as simple as the steps below
1) Flash signed twrp using axonroot tool - this pry's open the door
2) Using twrp, flash fastboot (b20_fbop or something?) - opens door wider
3) Enable usb debugging and oem unlocking in developer options
4) reboot to fastboot/bootloader mode
5) fastboot oem unlock - door is now wide open
Done.
Click to expand...
Click to collapse
Is that a "should work" or "does work" because I'm trying to root and install LOS also on stock non rooted nougat Axon 7 and so far I've gotten nowhere and no one seems to be able to give me a list that says Yes this works
Help needed
I followed the instructions and is apparently in a boot loop. Initially it was working but now it is not. I can't even wipe the device to start from scratch. Is there another ROM available to try?
kingoftheafro said:
Is that a "should work" or "does work" because I'm trying to root and install LOS also on stock non rooted nougat Axon 7 and so far I've gotten nowhere and no one seems to be able to give me a list that says Yes this works
Click to expand...
Click to collapse
This is exactly the reason I made my post, I need concrete answers not guesses. Glad to see someone else needs the same answers
kaiso said:
I followed the instructions and is apparently in a boot loop. Initially it was working but now it is not. I can't even wipe the device to start from scratch. Is there another ROM available to try?
Click to expand...
Click to collapse
Did you downgrade to Marshmallow B29 first or skip this step?
[email protected] said:
This is exactly the reason I made my post, I need concrete answers not guesses. Glad to see someone else needs the same answers
Click to expand...
Click to collapse
I'm praying that someone will compile the information spread about into 3 guides that are model specific so people like us won't rack our heads trying to figure out what on earth to do.
[email protected] said:
Hello Everyone!
Model: A2017U, Nougat 7.0 on B15 ROM
What I still need clarification on:
1with my device already running on nougat, do I need to install the nougat universal bootloader/radio I saw in earlier guides?
2will LineageOS have any downgrades in regard to audio quality, on either the headphone output or speakers?
3will my ROM of choice have Daydream VR support? if not what would be needed?
4this is not a big deal, but do I need a special app or entire custom ROM if I'm interested in a temporary unroot to use apps like Android Pay?
Here's what I want on my device: TWRP, LineageOS with root.
If anyone, expert users and devs alike, could reply with current known-good info about the following, I and a lot of other users would be eternally grateful:
unlocking the bootloader, installing TWRP, and LineageOS, in a stupidly long but simple step-by-step process.
Quick follow-up info:
What I can do so far: download current LineageOS nightly, correct version of root .zip, and TWRP from official websites
5NO, I'm not good with using ADB on Windows to get things done. I had to ask a friend to help me install it on windows, the guide he sent was much easier than the one i was using, and he still had to walk me through
Click to expand...
Click to collapse
Ok, I've edited your post to clear some of the clutter and numbered everything so I can answer everything.
1. No, bootloader updates are only for users who haven't updated to B15 (through official means)
2. Only audio issues are with the front facing speakers. The way they sound is if you turn them up to 100% and then push it even higher to like 140%. So if you keep it at about 71% they sound normal. Check this guide here to get even better quality on overall sound (headphones, speakers)
3.B15 and LOS both work with Daydream. I currently use LOS with my Daydream headset currently.
4.Magisk with this kernel here. Currently have fully functioning Android Pay with LOS.
5. This is a big problem. If you're not comfortable with ADB you should maybe rethink messing with this phone. EDL mode (which is how I flash TWRP and subsequently the B20 bootloader to unlock) is very similar to ADB and the tools needed to flash in EDL can brick your device. Learning how to use ADB isn't bad but it's good as a fallback so you're not relying on strangers to help you out in a pinch (which most will, I just like having the ability to do things mostly myself).
---------- Post added at 10:05 AM ---------- Previous post was at 09:55 AM ----------
nolimit78 said:
I'll keep on saying this as much as I need to, I get where you're coming from. There's a lot of data about the correct way of doing things. Best thing to do is read and search. When I got my phone B29 was the new hotness and there was a bunch of older data floating around that I had to sift through. But I did it, I sifted and found my own way and combined two different methods to get my phone rooted and flashed with LOS. Honestly, the trial and error, the searching, the sifting is totally worthwhile because while this device is /DIFFERENT/ compared to methods for HTC and Samsung products, it's not harder. It's better to get yourself properly antiquated to the device you plan on flashing/hacking/rooting because there is /always/ a chance for bricking. Then another thread will be created asking for help to unbrick. Take the time, read now, read everything, understand your device, then push forward.
Click to expand...
Click to collapse
I quoted this because this thread is like the third I've seen in the last couple days. But to offer some help, this is the guide that I've followed with two phones one running B29 stock and one running B15 Stock. It remains the same because of the use of EDL. It's also good in case you want to go back to complete stock (which at the time was speculated would brick your device) but I read between the lines and discovered that it's just not a big deal. Once you get TWRP installed, make sure your Data partition is EXT4, flash LOS, flash GApps and you're good to go.
The hardest part of the process, is getting your drivers to be recognized properly for the EDL flashing tool to work. Anti-Virus softwares tend to throw false positives with tools like the EDL Flashing tool. I installed a fresh copy of Windows 7 JUST to have a flashing station ready JIC. Once I did that, smooth sailing.
nolimit78 said:
Ok, I've edited your post to clear some of the clutter and numbered everything so I can answer everything.
1. No, bootloader updates are only for users who haven't updated to B15 (through official means)
2. Only audio issues are with the front facing speakers. The way they sound is if you turn them up to 100% and then push it even higher to like 140%. So if you keep it at about 71% they sound normal. Check this guide here to get even better quality on overall sound (headphones, speakers)
3.B15 and LOS both work with Daydream. I currently use LOS with my Daydream headset currently.
4.Magisk with this kernel here. Currently have fully functioning Android Pay with LOS.
5. This is a big problem. If you're not comfortable with ADB you should maybe rethink messing with this phone. EDL mode (which is how I flash TWRP and subsequently the B20 bootloader to unlock) is very similar to ADB and the tools needed to flash in EDL can brick your device. Learning how to use ADB isn't bad but it's good as a fallback so you're not relying on strangers to help you out in a pinch (which most will, I just like having the ability to do things mostly myself).
---------- Post added at 10:05 AM ---------- Previous post was at 09:55 AM ----------
I quoted this because this thread is like the third I've seen in the last couple days. But to offer some help, this is the guide that I've followed with two phones one running B29 stock and one running B15 Stock. It remains the same because of the use of EDL. It's also good in case you want to go back to complete stock (which at the time was speculated would brick your device) but I read between the lines and discovered that it's just not a big deal. Once you get TWRP installed, make sure your Data partition is EXT4, flash LOS, flash GApps and you're good to go.
The hardest part of the process, is getting your drivers to be recognized properly for the EDL flashing tool to work. Anti-Virus softwares tend to throw false positives with tools like the EDL Flashing tool. I installed a fresh copy of Windows 7 JUST to have a flashing station ready JIC. Once I did that, smooth sailing.
Click to expand...
Click to collapse
I've already used EDL mode from that page to put a fresh copy of stock nougat to, among other things, reduce the potential issues upgrading causes. So all I should have to do is flash B15-NEW_TWRP (Nougat) from that page and then fastboot unlock?
from there reset data/cache, flash custom ROM.
flash gapps
reboot, install apps.
?????
KyJelly69 said:
I've already used EDL mode from that page to put a fresh copy of stock nougat to, among other things, reduce the potential issues upgrading causes. So all I should have to do is flash B15-NEW_TWRP (Nougat) from that page and then fastboot unlock?
from there reset data/cache, flash custom ROM.
flash gapps
reboot, install apps.
?????
Click to expand...
Click to collapse
Yup.
kingoftheafro said:
Is that a "should work" or "does work" because I'm trying to root and install LOS also on stock non rooted nougat Axon 7 and so far I've gotten nowhere and no one seems to be able to give me a list that says Yes this works
Click to expand...
Click to collapse
In case you still need all this, I made a new guide after successfully doing everything:
https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128
[email protected] said:
In case you still need all this, I made a new guide after successfully doing everything:
https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128
Click to expand...
Click to collapse
Thank you for the guide, but I managed to get everything done without having to downagrade from Nougat. I was having issues with my Windows variant recognizing my phone after drivers were installed so I used Linux Mint 18.1 and everything went smooth as a whistle. I think the mods should pin your thread post.
I followed the rootjunkie YouTube videos, worked perfectly and the files were all available.
Sent from my ZTE A2017U using Tapatalk
I hate asking this as each has his own preference, however, I have only just ordered my ZTE Axon device as it was such a good offer, being even cheaper than brand new 2018 mid rangers! I purchased the device brand new and sealed for just £193 ($274) so you cannot go wrong.
My current phone was the Sony Xperia XZ Premium but I am giving it away to my wife and need another to replace it.
After some reading it seems the first thing I need to do is install all drivers and run the Axon 7 Tool kit. This will unlock bootloader, root and flash recovery from my understanding.
Then I can proceed to installing a custom rom of my choice followed by immediately flashing a modem otherwise I will not have any signal. Would this be everything needed to successfully running a custom rom trouble free?
Lastly, I would like a simple rom, preferably based on stock/vanilla Android, slim and bloat free. Something very basic, bug free and made for pure speed and decent battery. What are the top recommended roms with this regard? I did look into these, anything better? What are the differences? Thank you so much for your advise.
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143
https://forum.xda-developers.com/axon-7/development/rom-dark-rom-t3654264
kanej2006 said:
I hate asking this as each has his own preference, however, I have only just ordered my ZTE Axon device as it was such a good offer, being even cheaper than brand new 2018 mid rangers! I purchased the device brand new and sealed for just £193 ($274) so you cannot go wrong.
My current phone was the Sony Xperia XZ Premium but I am giving it away to my wife and need another to replace it.
After some reading it seems the first thing I need to do is install all drivers and run the Axon 7 Tool kit. This will unlock bootloader, root and flash recovery from my understanding.
Then I can proceed to installing a custom rom of my choice followed by immediately flashing a modem otherwise I will not have any signal. Would this be everything needed to successfully running a custom rom trouble free?
Lastly, I would like a simple rom, preferably based on stock/vanilla Android, slim and bloat free. Something very basic, bug free and made for pure speed and decent battery. What are the top recommended roms with this regard? I did look into these, anything better? What are the differences? Thank you so much for your advise.
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143
https://forum.xda-developers.com/axon-7/development/rom-dark-rom-t3654264
Click to expand...
Click to collapse
As for the SL!M roms i made ( making some advertisement here ) i only can advise looking at these ones as they are aroma roms and can be debloated further. Battery tweak is included and choice between SuperSU and Magisk is possible. These roms are stock-based as to preserve, imo, the sound quality of the phone as it came out of the box. No bug issues imo and fully up to date :
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
Based on MiFavor5.0 (CN) but fully applyable on all versions
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Based on stock G version but fully applyable on all versions and with the latest security patches of the A2017G-N(ougat)-B09
But then again others can comment on my slim roms better then i can perhap :cyclops:
Futhermore i do not advice https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143 as it is was my first version of MiFavor 5.0. Instead use the first link.
Didn't used the last one you mentioned based on LOS but others can advice more into this.
Good Luck and ENJOY !
raystef66 said:
As for the SL!M roms i made ( making some advertisement here ) i only can advise looking at these ones as they are aroma roms and can be debloated further. Battery tweak is included and choice between SuperSU and Magisk is possible. These roms are stock-based as to preserve, imo, the sound quality of the phone as it came out of the box. No bug issues imo and fully up to date :
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
Based on MiFavor5.0 (CN) but fully applyable on all versions
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Based on stock G version but fully applyable on all versions and with the latest security patches of the A2017G-N(ougat)-B09
But then again others can comment on my slim roms better then i can perhap :cyclops:
Futhermore i do not advice https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143 as it is was my first version of MiFavor 5.0. Instead use the first link.
Didn't used the last one you mentioned based on LOS but others can advice more into this.
Good Luck and ENJOY !
Click to expand...
Click to collapse
^ Thank you very much raystef66 for your speedy response! I will go for this version - https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Fingers crossed I should receive my Axon 7 Sunday or Monday at the very latest. First Thing I'll run the Axon 7 Toolkit so that I can unlock the bootloader, have recovery and root then I'll be able to flash your rom, looking forward into doing so!
I'll keep you informed in the coming days when complete. :good:
kanej2006 said:
^ Thank you very much raystef66 for your speedy response! I will go for this version - https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Fingers crossed I should receive my Axon 7 Sunday or Monday at the very latest. First Thing I'll run the Axon 7 Toolkit so that I can unlock the bootloader, have recovery and root then I'll be able to flash your rom, looking forward into doing so!
I'll keep you informed in the coming days when complete. :good:
Click to expand...
Click to collapse
Yeah, very exciting isn't it :good: It's a damn good phone, quick, nice quality screen and an amazing sound... !
I assume you'll get the G version ? The SL!M➃ is based on this G-version (btw, take a look at the DownloadCenter to have all necessary files) and keeps all things to stock. Just some minor mods and improvements, nothing fancy as to stay stock. With the battery tweak included i always get >7h SOT. But that depends of course on usage. But then again i do alot in a day . Some others have no benefit on the battery tweak but i'll hope you end up with a descent SOT.
Keep us posted :good:
raystef66 said:
Yeah, very exciting isn't it :good: It's a damn good phone, quick, nice quality screen and an amazing sound... !
I assume you'll get the G version ? The SL!M➃ is based on this G-version (btw, take a look at the DownloadCenter to have all necessary files) and keeps all things to stock. Just some minor mods and improvements, nothing fancy as to stay stock. With the battery tweak included i always get >7h SOT. But that depends of course on usage. But then again i do alot in a day . Some others have no benefit on the battery tweak but i'll hope you end up with a descent SOT.
Keep us posted :good:
Click to expand...
Click to collapse
Sounds good! I would be happy with around 7 hours SOT. Once received I'll let you know what version I receive, however, I'm guessing I'll get the Chinese version as it's coming from Dubai, UAE (Middle East) and most likely it'll come from China and not EU as it's much closer.
I have everything ready accept for a flashable TWRP. The link appears down for me and I was not able to find a flashable version, could you please give me a link of a working one? I was only able to find a non flashable version which is run via CMD/fastboot commands.
I would much rather a flashable recovery in which I can flash once installing your rom along with SuperSU or Magisk. Regards!
kanej2006 said:
Sounds good! I would be happy with around 7 hours SOT. Once received I'll let you know what version I receive, however, I'm guessing I'll get the Chinese version as it's coming from Dubai, UAE (Middle East) and most likely it'll come from China and not EU as it's much closer.
I have everything ready accept for a flashable TWRP. The link appears down for me and I was not able to find a flashable version, could you please give me a link of a working one? I was only able to find a non flashable version which is run via CMD/fastboot commands.
I would much rather a flashable recovery in which I can flash once installing your rom along with SuperSU or Magisk. Regards!
Click to expand...
Click to collapse
The TWRP is inside the toolkit, so you can flash it downthere imo. Never done this that way though as in those early days i used this one to do everything. But use the toolkit and you're good to go.
raystef66 said:
The TWRP is inside the toolkit, so you can flash it downthere imo. Never done this that way though as in those early days i used this one to do everything. But use the toolkit and you're good to go.
Click to expand...
Click to collapse
Ah good to hear, glad it's included in the kit. So I can simply use the one from the kit to flash recovery after flashing your rom? Because in the instructions it mentions we have to manually flash recovery after the rom.
kanej2006 said:
Ah good to hear, glad it's included in the kit. So I can simply use the one from the kit to flash recovery after flashing your rom? Because in the instructions it mentions we have to manually flash recovery after the rom.
Click to expand...
Click to collapse
That depends. I dont know what version of twrp is installed via the toolkit. Perhaps it checkes for the latest when it updates but not sure. But if a certain version is installed which is not the latest, put the latest twrp.img onto your int or extSD and flash via your twrp you've installed.
Second, if your phone would be an CN version and not a G, you'll have to install the Universal BL and your specific modem as described in the rom thread. You can find them in the link of the rom thread. So, after installing the Universal BL (which has an older version of twrp !) , you'd have to install the latest via twrp too. So just flash the twrp image and you're good to go.
Btw, i made a flashable zip before of that Universal BL which replaces the old twrp with the 3.1.1.0 version, which will do fine too.
Here's the link : https://androidfilehost.com/?fid=673791459329066038 (it also works on the SLIM4 as it just replaces twrp)
So after installing this version, you dont need to flash another twrp (as it brings you to the 3.1.1.0 as said)
kanej2006 said:
Ah good to hear, glad it's included in the kit. So I can simply use the one from the kit to flash recovery after flashing your rom? Because in the instructions it mentions we have to manually flash recovery after the rom.
Click to expand...
Click to collapse
Uuhh. I think you'll get the G version. Anything else than China and US gets G. With that said, I recommend you two things:
- (If you get a G) Use Controllerboy's guide instead of the toolkit. Lately a lot of stuff is going wrong with the toolkit
-Whatever happens, DO NOT ATTEMPT TO RELOCK THE BOOTLOADER.
-Once you have TWRP, just follow the instructions on each ROM. Never flash stuff from other models.
-Take the TWRP img either from raystef66's download center or from twrp.me
raystef66 said:
I dont know what version of twrp is installed via the toolkit. Perhaps it checkes for the latest when it updates but not sure. But if a certain version is installed which is not the latest, put the latest twrp.img onto your int or extSD and flash via your twrp you've installed.
Second, if your phone would be an CN version and not a G, you'll have to install the Universal BL and your specific modem as described in the rom thread. You can find them in the link of the rom thread. So, after installing the Universal BL (which has an older version of twrp !) , you'd have to install the latest via twrp too. So just flash the twrp image and you're good to go.
Btw, i made a flashable zip before of that Universal BL which replaces the old twrp with the 3.1.1.0 version, which will do fine too.
Here's the link : https://androidfilehost.com/?fid=673791459329066038 (it also works on the SLIM4 as it just replaces twrp)
So after installing this version, you dont need to flash another twrp (as it brings you to the 3.1.1.0 as said)
Click to expand...
Click to collapse
Will do. You are right, the toolkit automatically checks for the latest update and it finds version 3.1.1.0.
Choose an username... said:
Uuhh. I think you'll get the G version. Anything else than China and US gets G. With that said, I recommend you two things:
- (If you get a G) Use Controllerboy's guide instead of the toolkit. Lately a lot of stuff is going wrong with the toolkit
-Whatever happens, DO NOT ATTEMPT TO RELOCK THE BOOTLOADER.
-Once you have TWRP, just follow the instructions on each ROM. Never flash stuff from other models.
-Take the TWRP img either from raystef66's download center or from twrp.me
Click to expand...
Click to collapse
I did see on the forum users attempting to relock the bootloader and it worsened things, I will not attempt this.
Should be able to let you know tomorrow or the day after what version I get and hopefully when I successfully gain recovery and root access!
I just hope I don't get the dead microSD bug that many people have mentioned. Top of the range 64Gb/128Gb MicroSD cards can be costly so I would not like to have them corrupted!
@raystef66, Do you have any other download links for your rom aside from androidfilehost? I tried several different servers but all keep randomly freezing otherwise saying 5 hours, 6 hours, 11 hours and 15 hours. Extremely slow download.
If you want to try a more Android vanilla ROM, then I suggest AICP. Be sure to use the unofficial builds by genesixxbf3. They are very stable and have good features.
https://forum.xda-developers.com/axon-7/development/rom-aicp-12-1-t3611013
kanej2006 said:
@raystef66, Do you have any other download links for your rom aside from androidfilehost? I tried several different servers but all keep randomly freezing otherwise saying 5 hours, 6 hours, 11 hours and 15 hours. Extremely slow download.
Click to expand...
Click to collapse
Yeah, sometime AFH can be cruel. Just depends. I tried the Washington DC just a moment and no problems there. I just advice, take one and let it take it's time. Some way or another the download speed gets stable enough And then again, you still have a bit of time don't you or has it dropped of yet with the postman :cyclops: Do I Hear a heartbeat there ? :good:
raystef66 said:
Yeah, sometime AFH can be cruel. Just depends. I tried the Washington DC just a moment and no problems there. I just advice, take one and let it take it's time. Some way or another the download speed gets stable enough And then again, you still have a bit of time don't you or has it dropped of yet with the postman :cyclops: Do I Hear a heartbeat there ? :good:
Click to expand...
Click to collapse
Haha, no, not yet received! Where I am living at the moment, the weekend is Friday and Saturday, Sunday to Thursday work, strange but that's the way it is.
The seller estimates the item to arrive on Sunday or Monday, hopefully Sunday.
In the end the Netherland's sever finally managed to get me the 2.1Gb download complete. I did try others but were slower. Good thing in your rom you included the 3 different models for the Axon 7. I'm yet to see which one I receive!
Confirmed G version received.
kanej2006 said:
Confirmed G version received.
Click to expand...
Click to collapse
The AcTiOn can begin :good:
Use this guide like said above and you'll be ok.
raystef66 said:
The AcTiOn can begin :good:
Use this guide like said above and you'll be ok.
Click to expand...
Click to collapse
Not working, been trying for hours.
Not connecting despite all drivers installed, including Qualcom driver. Followed all instructions as stated. Stuck from number 20. When entering this command I get ''failed to connect''
When typing in adb devices it finds my device.
1) Backup all the data of your phone's internal memory that you don't want to lose. Copy it to your PC
2) Download the axon7tool from here: http://www.filedropper.com/axon7tool-15-win64
3) Download minimal adb and fastboot from here: https://www.androidfilehost.com/?fid=457095661767103465
4) Unzip the minimal adb and fastboot file, place the folder with the files in it somewhere you can easily find it
5) Place the axon7tool exe in the same folder as adb.exe and rename it to "axon7tool.exe" (it's easier to work with that way)
6) Download the TWRP .img and .bin files from here: https://drive.google.com/open?id=0B4...nlaZU1NRldoRjA
7) Place the TWRP .img file in the same folder as "adb.exe" and "axon7tool.exe", rename it to "recovery.img"
8) Make a copy of the "recovery.img" file and name it "recovery.bin". Leave it in the same folder
9) Go to settings in your phone and go to "About Phone". Tap "Build Number" 7 times to make the Developer Options available
10) Go to "Developers options" and tick "Allow OEM unlock" and "Android Debugging"
11) Connect your Axon 7 to your PC
12) Open a command window by holding shift and right-clicking in a blank space in the folder where the "adb.exe", " axon7tool.exe", "recovery.img" and "recovery.bin" files are located. Click "Open command window here"
13) Type "adb devices" and hit enter. You should see one device with some code listed
14) Type "adb reboot edl" and hit enter. Your device will reboot to EDL mode. It appears to be off, but it is in fact in EDL mode.
15) Go to Device Manager on your pc and verify your Axon 7 is listed as "QUSB_BULK"
16) In command, type "axon7tool -r gpt boot recovery" and hit enter
17) After it is executed, your phone will reboot. Wait until it has fully booted.
18) In command, type "adb reboot edl"
19) Verify you now have 3 backup files in your ADB folder for gpt, recovery and boot. These are backup files in case something goes wrong
20) In command, type "axon7tool -w recovery" - STUCK HERE - FAILED
kanej2006 said:
Not working, been trying for hours.
20) In command, type "axon7tool -w recovery" - STUCK HERE - FAILED
Click to expand...
Click to collapse
You're on nougat ? Look into about phone for that.
Afaik, you'll have to be on MM. So downgrade/rollback if on Nougat (look into DownloadCenter for B10 or B11) and do the procedure all over again.
Imo it's due to that.
edit: sure you have the recovery.img and bin in your adb folder ?
raystef66 said:
You're on nougat ? Afaik, you'll have to be on MM. So downgrade/rollback if on Nougat (look into DownloadCenter for B10 or B11) and do the procedure all over again.
Imo it's due to that.
edit: sure you have the recovery.img and bin in your adb folder ?
Click to expand...
Click to collapse
No, I am on stock MM.
kanej2006 said:
No, I am on stock MM.
Click to expand...
Click to collapse
Should work then.
Can you download recovery again. Check all characters if they're all written ok.
Sure the toolkit cannot bring enlightment too ?
Hi,
I'm French and my level in english is not very high.
So I try to unlock my wife's phone but I havbe understood that it is no more possible with the classic way with huawei support.
Does exist another way tu do this ? Or is it definitivly impossible ?
No french forum can explain this.
As I can see many custom Roms here I keep a hope !
Hi, yes it should be still possible.
DC-Unlocker is what you need. The operation has a cost in credits, 4$ are necessary to unlock the device since it's the cost that DC asks from retrieve bootloader code from your device.
If you're definitely motivated to do it, it's your only chance but luckily it's an acceptable prize.
RedSkull23 said:
Hi, yes it should be still possible.
DC-Unlocker is what you need. The operation has a cost in credits, 4$ are necessary to unlock the device since it's the cost that DC asks from retrieve bootloader code from your device.
If you're definitely motivated to do it, it's your only chance but luckily it's an acceptable prize.
Click to expand...
Click to collapse
hi, does dc-unlocker work on Emui 8 as well? PRA-LX1 model, build 8.0.0.399 (C432)...
turboxav said:
Hi,
I'm French and my level in english is not very high.
So I try to unlock my wife's phone but I havbe understood that it is no more possible with the classic way with huawei support.
Does exist another way tu do this ? Or is it definitivly impossible ?
No french forum can explain this.
As I can see many custom Roms here I keep a hope !
Click to expand...
Click to collapse
What you mean by "unlock".
60nine said:
hi, does dc-unlocker work on Emui 8 as well? PRA-LX1 model, build 8.0.0.399 (C432)...
Click to expand...
Click to collapse
With my p10 lite with emui 8 it worked. So why not
0
yes
I Have unlock my phone yesterday with dc unlocker
Seppppx said:
You can downgrade (idk if it is possible from emui 8 I don't even own this phone) and then you can follow this tutorial to unlock your bootloader (FOR FREE) https://forum.xda-developers.com/p8lite/general/guide-unlock-bootloader-root-device-t3977067
Edit : found this guide with HiSuite it may work https://youtu.be/xFCLpgGZEJM
Click to expand...
Click to collapse
Yeah, but not for Huawei P8 Lite 2017 version... I found this to be possible just for older phones (like the original P8 lite) which can be downgraded to Android 5. Newer ones can't be flashed with unsigned firmware (= firmware which is not straight from damn Huawei who decided not to provide the bootloader codes in the first place) so the only way apparently is to use paid software like DC-Unlocker as stated in this official XDA thread --> https://www.xda-developers.com/huawei-honor-unlock-bootloader-fee/
60nine said:
hi, does dc-unlocker work on Emui 8 as well? PRA-LX1 model, build 8.0.0.399 (C432)...
Click to expand...
Click to collapse
Unlocked the bootloader yesterday! I have Huawei P8 Lite 2017 PRA-LX1 and had latest Emui 8 build on it... Bought the code for 4€ from DC-Unlocker, and required around 2 minutes for unlocking. You can follow this guide --> https://www.youtube.com/watch?v=4xYybHAlWaQ
I tried so hard to get the code for free, and I know modding should not cost people money. But at the end of the day, I think those 4 euros were worth it
Yeah,4 Euros is ok and the only method!!!
-CALIBAN666- said:
Yeah,4 Euros is ok and the only method!!!
Click to expand...
Click to collapse
And also worth it if we consider fact that our phone is now EMUI free. ?
DunoCZ said:
And also worth it if we consider fact that our phone is now EMUI free.
Click to expand...
Click to collapse
Dear all,
sorry in advance for the silly question but in this regard I am dumb as a brick.
I run DC Unlocker, got the phone unlocked but now the only thing I have is the stock boot telling me the phone is unlocked and therefore cannot be trusted. From there on, I do not know how to procede in order to install TWRP recovery + LineageOS 17.1. I tried to install TWRP but it only runs after a factory reset with the "stock" Huawei eRecovery and every time I reboot (I even got to the point of installing LineageOS via fastboot) it is always back to square one.
Again, sorry, but the last phone I "worked on" was an HTC Desire HD some 8 years ago, therefore you can guess I lost some years of advancements
Thank you for any help regarding the steps I am missing, links to guides much much appreciated.
Best and ciao from Italy
af1985 said:
Dear all,
sorry in advance for the silly question but in this regard I am dumb as a brick.
I run DC Unlocker, got the phone unlocked but now the only thing I have is the stock boot telling me the phone is unlocked and therefore cannot be trusted. From there on, I do not know how to procede in order to install TWRP recovery + LineageOS 17.1. I tried to install TWRP but it only runs after a factory reset with the "stock" Huawei eRecovery and every time I reboot (I even got to the point of installing LineageOS via fastboot) it is always back to square one.
Again, sorry, but the last phone I "worked on" was an HTC Desire HD some 8 years ago, therefore you can guess I lost some years of advancements
Thank you for any help regarding the steps I am missing, links to guides much much appreciated.
Best and ciao from Italy
Click to expand...
Click to collapse
Did you after fastboot oem unlock leave phone format yourself right?
DunoCZ said:
Did you after fastboot oem unlock leave phone format yourself right?
Click to expand...
Click to collapse
Don't fully get your question. Current situation is: Phone unlocked with DC Unlocker. When I switch it on I get the "phone is unlocked" message and if I don't do anything it starts booting stock OS, otherwise goes into Huawei eRecovery. If from Huawei eRecovery I do a full wipe, it starts TWRP. But even if I work on TWRP, when I reboot it is all back to "phone is unlocked". And again, and again. Hope it is clearer.
Thanks
af1985 said:
Don't fully get your question. Current situation is: Phone unlocked with DC Unlocker. When I switch it on I get the "phone is unlocked" message and if I don't do anything it starts booting stock OS, otherwise goes into Huawei eRecovery. If from Huawei eRecovery I do a full wipe, it starts TWRP. But even if I work on TWRP, when I reboot it is all back to "phone is unlocked". And again, and again. Hope it is clearer.
Thanks
Click to expand...
Click to collapse
Yeah I get it now, the problem is if you wanna go to twrp sometimes you have to press volume up and hold it until logo shows up, sometimes you had to hold both volume buttons etc. It's kinda wierd but the factory format from erecovery is in twrp disabled due to this because sometimes it wont let you boot until format (that triggers almost anything like fastly restarting to and from recovery etc.).
So keep calm it's "normal".
af1985 said:
Don't fully get your question. Current situation is: Phone unlocked with DC Unlocker. When I switch it on I get the "phone is unlocked" message and if I don't do anything it starts booting stock OS, otherwise goes into Huawei eRecovery. If from Huawei eRecovery I do a full wipe, it starts TWRP. But even if I work on TWRP, when I reboot it is all back to "phone is unlocked". And again, and again. Hope it is clearer.
Thanks
Click to expand...
Click to collapse
Just for your information, TWRP on this device is not fully supported. Every TWRP version you may find on XDA forums for this particular device is different. In my case TWRP back up doesn't work, wipe cache doesn't work, format data only breaks the system partition , flash GSI's from TWRP also doesn't work XDXD
The only thing I could do from TWRP was flash Magisk and hope that nothing will go wrong in the future ...XD got it? Flash and forget ???
Momin8454 said:
Just for your information, TWRP on this device is not fully supported. Every TWRP version you may find on XDA forums for this particular device is different. In my case TWRP back up doesn't work, wipe cache doesn't work, format data only breaks the system partition , flash GSI's from TWRP also doesn't work XDXD
The only thing I could do from TWRP was flash Magisk and hope that nothing will go wrong in the future ...XD got it? Flash and forget
Click to expand...
Click to collapse
Lol you are dumb...
DunoCZ said:
Lol you are dumb...
Click to expand...
Click to collapse
Well, I didn't had any knowledge of it. Turns out my EMUI version was more recent one that's why I had more issues with TWRP.
And I was just sharing my experience with Honor 8 lite.
DunoCZ said:
Yeah I get it now, the problem is if you wanna go to twrp sometimes you have to press volume up and hold it until logo shows up, sometimes you had to hold both volume buttons etc. It's kinda wierd but the factory format from erecovery is in twrp disabled due to this because sometimes it wont let you boot until format (that triggers almost anything like fastly restarting to and from recovery etc.).
So keep calm it's "normal".
Click to expand...
Click to collapse
Thank you for your support. To reinstate some order in the procedure, yesterday I reinstalled EMUI from eRecovery and now I am back to "zero-point-one", aka right after DC Unlocker: when I switch on the phone it says it is unlocked and then launches stock OS. From now on what should I do to have in the end LineageOS 17.1 installed? Again, thanks for your time
Some advice from a beginner
af1985 said:
Thank you for your support. To reinstate some order in the procedure, yesterday I reinstalled EMUI from eRecovery and now I am back to "zero-point-one", aka right after DC Unlocker: when I switch on the phone it says it is unlocked and then launches stock OS. From now on what should I do to have in the end LineageOS 17.1 installed? Again, thanks for your time
Click to expand...
Click to collapse
Hi!
So, I installed Lineage OS 17.1 on my sister's phone just two days ago, maybe I can give you some advice being myself a beginner. So, first of all, I guess you have enabled OEM unlock (otherwise you could not flash TWRP I guess? I don't think this is the point anyway) If not so, go to Developer Options --> Enable OEM unlock and you will see both the bootloader and FRP unlocked.
The try to follow the DarkJoker360's Lineage OS 17.1 install guide step by step (don't forget to flash the los_patches_prague.zip!). The right version of TWRP is important too for compatibility issues, so install the version he provided.
Anyway, as @DunoCZ pointed out, for entering TWRP recovery you have to press Volume UP button + Power button and keep them pressed until you get to the TWRP. Otherwise, what the device does is either booting up or go to the screen like "Press Volume UP for at least 3 seconds to go to erecovery" and if you do that, it will go into Huawei's own recovery.
Another thing is... Did you do a full wipe (system, data, cache, dalvik/art cache) in TWRP before trying to flash the new ROM? (don't just do the factory reset in Huawei's recovery, I read somewhere it doesn't wipe everything like the advanced one in the custom recovery)
af1985 said:
Don't fully get your question. Current situation is: Phone unlocked with DC Unlocker. When I switch it on I get the "phone is unlocked" message and if I don't do anything it starts booting stock OS, otherwise goes into Huawei eRecovery. If from Huawei eRecovery I do a full wipe, it starts TWRP. But even if I work on TWRP, when I reboot it is all back to "phone is unlocked". And again, and again. Hope it is clearer.
Thanks
Click to expand...
Click to collapse
Because as you wrote here, the stock OS booted up before you installed stock from again via Huawei erecovery. So my wild guess is that the wipe you did before flashing Lineage OS wasn't a full wipe?
---------- Post added at 10:30 AM ---------- Previous post was at 10:06 AM ----------
By the way, after installing Lineage OS 17.1 I found out there were indeed some very important problems in the ROM as noticed by other testers too...
The reason why I changed the ROM on the device was mainly because of two reasons:
1) Short battery life
2) Not enough memory
And unfortunately, on Lineage OS 17.1:
1) Battery life not good enough. Unless you fix it by patching a new kernel, be always wary of apps running on your device etc., the battery ran short even after replacing the internal battery. Alas. Besides, I wanted something stable for my sis who threatened me to buy an iPhone if I couldn't fix her phone lol
2) Very big problem with memory: I couldn't find a way to write to the SD card as other users pointed out. It is read by the device, but apparently it is read only and even with root permissions I couldn't find a way to obtain write permission for the apps. Perhaps some options in fstab mount file should be changed, but honestly, I tried with my below-average knowledge of Linux and gave up :crying:
But then... I tried Lineage OS 15.1 and this one worked much, much better. Battery life is super good and has the adoptable storage option for the SD card! This way, instead of those 9 gigs of memory now the phone has more than 70! And honestly, this ROM solved both the most important problems of this phone
(PS: sorry for the long posts lol)
(PPS: if you decide to switch to 15.1, remember to decrypt the memory following this post otherwise you won't be able to install more that a bunch of apps on the phone. Besides, remember to flash Dil3mm4 's TWRP recovery)
Jujub said:
Hi!
So, I installed Lineage OS 17.1 on my sister's phone just two days ago, maybe I can give you some advice being myself a beginner. So, first of all, I guess you have enabled OEM unlock (otherwise you could not flash TWRP I guess? I don't think this is the point anyway) If not so, go to Developer Options --> Enable OEM unlock and you will see both the bootloader and FRP unlocked.
The try to follow the DarkJoker360's Lineage OS 17.1 install guide step by step (don't forget to flash the los_patches_prague.zip!). The right version of TWRP is important too for compatibility issues, so install the version he provided.
Anyway, as @DunoCZ pointed out, for entering TWRP recovery you have to press Volume UP button + Power button and keep them pressed until you get to the TWRP. Otherwise, what the device does is either booting up or go to the screen like "Press Volume UP for at least 3 seconds to go to erecovery" and if you do that, it will go into Huawei's own recovery.
Another thing is... Did you do a full wipe (system, data, cache, dalvik/art cache) in TWRP before trying to flash the new ROM? (don't just do the factory reset in Huawei's recovery, I read somewhere it doesn't wipe everything like the advanced one in the custom recovery)
Because as you wrote here, the stock OS booted up before you installed stock from again via Huawei erecovery. So my wild guess is that the wipe you did before flashing Lineage OS wasn't a full wipe?
---------- Post added at 10:30 AM ---------- Previous post was at 10:06 AM ----------
By the way, after installing Lineage OS 17.1 I found out there were indeed some very important problems in the ROM as noticed by other testers too...
The reason why I changed the ROM on the device was mainly because of two reasons:
1) Short battery life
2) Not enough memory
And unfortunately, on Lineage OS 17.1:
1) Battery life not good enough. Unless you fix it by patching a new kernel, be always wary of apps running on your device etc., the battery ran short even after replacing the internal battery. Alas. Besides, I wanted something stable for my sis who threatened me to buy an iPhone if I couldn't fix her phone lol
2) Very big problem with memory: I couldn't find a way to write to the SD card as other users pointed out. It is read by the device, but apparently it is read only and even with root permissions I couldn't find a way to obtain write permission for the apps. Perhaps some options in fstab mount file should be changed, but honestly, I tried with my below-average knowledge of Linux and gave up :crying:
But then... I tried Lineage OS 15.1 and this one worked much, much better. Battery life is super good and has the adoptable storage option for the SD card! This way, instead of those 9 gigs of memory now the phone has more than 70! And honestly, this ROM solved both the most important problems of this phone
(PS: sorry for the long posts lol)
(PPS: if you decide to switch to 15.1, remember to decrypt the memory following this post otherwise you won't be able to install more that a bunch of apps on the phone. Besides, remember to flash Dil3mm4 's TWRP recovery)
Click to expand...
Click to collapse
Check out my SPECTRUM profile I wrote even simple tut how to flash kernel and enable adoptable storage
Hey guys,
I was using TWRP + Lineage 15.1 ROM on my Fire HD 8 (2018 - 8th Gen) but decided to return to stock ROM and get rid of it.
As I didn't find any guidance anywhere I've tried to sideload the original stock ROM through TWRP even I didn't really think that was a good idea. I upladed the file (update-kindle-Fire_HD8_8th_Gen-PS7315_user_1958_0018354775684.bin - perhaps not the correct file anyway ) which resulted in boot loop. I now cannot access TWRP. Does anyone please have a link with instructions how to unbrick my device or even better with instructions to directly flash the stock ROM for 8th Gen please? I only keep finding links for older devices.
Many thanks guys.
ertech said:
Hey guys,
I was using TWRP + Lineage 15.1 ROM on my Fire HD 8 (2018 - 8th Gen) but decided to return to stock ROM and get rid of it.
As I didn't find any guidance anywhere I've tried to sideload the original stock ROM through TWRP even I didn't really think that was a good idea. I upladed the file (update-kindle-Fire_HD8_8th_Gen-PS7315_user_1958_0018354775684.bin - perhaps not the correct file anyway ) which resulted in boot loop. I now cannot access TWRP. Does anyone please have a link with instructions how to unbrick my device or even better with instructions to directly flash the stock ROM for 8th Gen please? I only keep finding links for older devices.
Many thanks guys.
Click to expand...
Click to collapse
It seems that the bootloader files for OS 6 (TZ and LK) are incompatible with OS 7.3.1.5. I found that you could not even shut down the tablet when it was bootlooping: holding the power button down for >30 seconds did nothing. To stop it you need to open the tablet and disconnect the battery.
You will need to copy a version of OS 6 onto a micro SD card (change the file extension from '.bin' to '.zip'). Insert the micro SD, after reconnecting the battery and putting the rear shell back on. You should be able to boot into recovery (TWRP) with the left volume button/ power button. Wipe system and data then flash the OS 6 zip.
Locate the newer thread for unlocking the HD 8/ 8th gen. tablet (amonet-3) and download the latest amonet version (currently 3.0.1) and the 'return to stock' zip, then follow the instructions in that thread to return to stock. Essentially you unzip the two downloads, merge, and run the return to stock script. From TWRP you boot the tablet into hacked fastboot mode and the script will restore stock boot and recovery images (unpatched). After a reboot you should be able to enter standard Amazon recovery mode. If you then ADB sideload the OS 7.3.1.5 software you will eventually boot into OS 7 (Pie).
Link to 'amonet-3' thread: https://forum.xda-developers.com/showpost.php?p=80166353&postcount=1
@MontysEvilTwin I haven't updated mine to 7.x release but wanted to see if you have been able to successfully unlock and root on newer firmware?
I'm guessing as you said bootloader files for OS 6 (TZ and LK) are incompatible, its not going to work?
madman said:
@MontysEvilTwin I haven't updated mine to 7.x release but wanted to see if you have been able to successfully unlock and root on newer firmware?
I'm guessing as you said bootloader files for OS 6 (TZ and LK) are incompatible, its not going to work?
Click to expand...
Click to collapse
I've had no luck unlocking the Karnak (or Mustang). I think there a couple of issues. The unlock doesn't work with the OS 7.3.1.5 bootloaders, you get a bootloop. I expected this as it is only the very first version of the Karnak LK file (OS 6.3.0.0) that has the necessary vulnerability for a full unlock. However if you use a modified version of Amonet to flash the OS 7.3.1.5 PL and TZ plus the OS 6.3.0.0 LK you get a bootloop, even without unlocking and unpatched stock boot and recovery images. It may not be impossible, I am hoping that the unlock authors (@xyz` and @k4y0z) will take a look at some point.
Thank you very much @MontysEvilTwin for your response and great explanation. Opening the device, disconnecting the battery and taking all these steps just to flash the stock ROM and selling it for a few pounds is probably way more effort than what it's worth. I'll probably just sell the case and hand the device for a safe disposal. It might be perhaps worth it to create a separate topic with a step by step walkthrough to safely revert a rooted device with TWRP & custom ROM back to Stock ROM for less advanced users like me? (I appreciate what I attempted to do was a bit stupid, just saying it would be useful having this explained somewhere...)
As I'm not going to use "Karnak" any more I'd like to thank everyone here for all their contributions as you made my experience with my device significantly better and also to thank everyone who found time to answer my questions. I just wanted to say that you're doing an amazing thing and making people like me happy. :good:
ertech said:
Thank you very much @MontysEvilTwin for your response and great explanation. Opening the device, disconnecting the battery and taking all these steps just to flash the stock ROM and selling it for a few pounds is probably way more effort than what it's worth. I'll probably just sell the case and hand the device for a safe disposal. It might be perhaps worth it to create a separate topic with a step by step walkthrough to safely revert a rooted device with TWRP & custom ROM back to Stock ROM for less advanced users like me? (I appreciate what I attempted to do was a bit stupid, just saying it would be useful having this explained somewhere...)
As I'm not going to use "Karnak" any more I'd like to thank everyone here for all their contributions as you made my experience with my device significantly better and also to thank everyone who found time to answer my questions. I just wanted to say that you're doing an amazing thing and making people like me happy. :good:
Click to expand...
Click to collapse
OK, if you just want to unbrick it is quite easy. If you have the latest TWRP (you will have if you unlocked with amonet version-3 for thIs tablet) it is likely that your bootloaders are unchanged. To get out of the bootloop you can either disconnect the battery or let it run down. Then you should be able to boot into recovery. From there you can flash a backup of your previous OS, or wipe system and data and reflash a stock OS 6 update.