Related
Hi!
I've been using Androwook 2.0 for a while and love it. However, I'd like to try 2.1 and the BAKED ROMs. Based on feedback on the forum, I want to use the Team Win recovery (TWRP) as opposed to my currently installed Clockwork Recovery.
Problem is, I can't work out how to replace CWR with TWRP. I've downloaded GooManager and instructed it to install the TW recovery. It says it's done so but when I reboot to recovery it takes me back to CW.
So, question is: how can I replace Clockwork Recovery with TWRP on a TF201?
Many thanks in advance for your thoughts!
Regards,
mroshaw
mroshaw said:
Hi!
I've been using Androwook 2.0 for a while and love it. However, I'd like to try 2.1 and the BAKED ROMs. Based on feedback on the forum, I want to use the Team Win recovery (TWRP) as opposed to my currently installed Clockwork Recovery.
Problem is, I can't work out how to replace CWR with TWRP. I've downloaded GooManager and instructed it to install the TW recovery. It says it's done so but when I reboot to recovery it takes me back to CW.
So, question is: how can I replace Clockwork Recovery with TWRP on a TF201?
Many thanks in advance for your thoughts!
Regards,
mroshaw
Click to expand...
Click to collapse
you could use fastboot method: http://www.teamw.in/project/twrp2/93
also it is recommended to use AndroidRoot bootloader: http://forum.xda-developers.com/showthread.php?t=1774352
Thank you for the reply. I'm not that comfortable with that level of tweaking and I had really hoped that Goo Manager would sort me out. Is it a known issue that Goo Manager cannot install TWRP if another recovery is present?
If so, I'll give the fastboot method a go at the weekend.
You really shouldn't be flashing anything if you don't know what its actually doing on your device.
Danny80y said:
You really shouldn't be flashing anything if you don't know what its actually doing on your device.
Click to expand...
Click to collapse
I think most of us are unaware of exactly what is going on behind the scenes when you tell an app to update the recovery. The fact that he is searching for alternative methods to GooManager since it doesn't work seems rather valid. I flashed twrp via the fastboot method. I did not use the AndroidRoot bootloader.
Danny80y said:
You really shouldn't be flashing anything if you don't know what its actually doing on your device.
Click to expand...
Click to collapse
Yeah, not a particularly helpful response to be honest. If you don't know the answer to the question, probably best not to post a reply.
emptyshell said:
The fact that he is searching for alternative methods to GooManager since it doesn't work seems rather valid
Click to expand...
Click to collapse
Indeedy - thanks for that.
The Androwook flashing process felt really safe and gave a lot of less techy Prime users access to a ROM that transformed (excuse the pun) the TF201 into a usable device. I don't think a lack of a full understanding of the inner workings of the technology or process should stop people from using it or from asking questions. Otherwise, what's the point of the forum?
If anyone is able to answer the question as to why Goo Manager will not install TWRP on top of an existing CW recovery, I'd greatly appreciate it. :good:
emptyshell said:
I think most of us are unaware of exactly what is going on behind the scenes when you tell an app to update the recovery. The fact that he is searching for alternative methods to GooManager since it doesn't work seems rather valid. I flashed twrp via the fastboot method. I did not use the AndroidRoot bootloader.
Click to expand...
Click to collapse
I had problem with GooManager too, so I flashed TWRP manually via fastboot.
Be aware her if you want to use twrp backup/restore you'll probably need modified bootloader as stated above. Twrp uses .img backup format, not blob, and modified bootloader can handle them correctly, which is not the case of original one.
You could have a non functional restore process for /boot. One solution could be to reflash the ROM after the restore in that case, so if you don't want to modify the bootloader always keep the zip of the ROM that you backup.
Thanks all.
I'll go the manual route then, I think. Be as well to go the whole hog and do the modified boot loader too, by the sounds of things.
Thank you for your useful responses and input - much appreciated.
Couple of things to be aware of, firstly, fastboot method for installing twrp not too hard, read the instructions a couple times before you proceed. If you do run into problems, go back to the forum and ask, don't try to "fix" it with a method that hasn't been proven. Secondly, when you install twrp, you can forget you cwm backups, they are now worthless. That being said, make a back up in twrp at your earliest convinence.
Third, read the instructions, most are pretty clear but if you don't understand something ask before you start you can save yourself a lot of trouble.
[update 2] I just summarized a way to backup and restore (all based on other great DEV's work, just put in one place) your TS before your play with your TS here: http://forum.xda-developers.com/showthread.php?p=52820278#post52820278
Go check it if you plan to root your TS!
[update] With the help of cheahcl, I got the latest F/W for 4th List 1/8/2100. With the MTK SP_Flash_Tool, I was able to upload a corrected F/W for my TS and everything goes back to normal!
Thanks for cheahcl for his dump and Lokifish Marz for his All in one tools! You guys really saved my day! (and my TS).
A Quick summary: Do NOT use any method on XDA yet to root or change TWRP recovery! It seems the TS of 4th list is different in some way than the ones before which render most of stuffs here invalid. However, fear not to play around since now we have a way to go back to stock!
In my experience, I found that it's really difficult to truly brick a MTK based system. The system will just reject flashing at slightest sign that a F/W is not compatible. The only cache is you need to have the "correct" F/W specifically for your TS!
In my observation, OMate made changes between each delivery. For Example, the 4th list of 1/8/2100 is different in (At least F/W configuration) of the 3rd or earlier 1/8/2100.
------------------------below is my original story of what I tried and failed--------------------------
Just got mine (1/8/2100) 5 hrs ago! I am on the 4th list. The delivery in FAST!
The watch starts normally. I played with it for a while, than decided to root it, install TWRP and apply the security hack made by +Lokifish Marz
Now I have a brick! Just after 30 min I receive the watch!
<<Can anyone help me here?>>
First of all, in respecting to all great DEVs, I have NO intention to blame anyone else but myself. (I did this to my own watch!)
Second, I have been rooting Android since Cupcake day, so I am not a Noob... (or so I think...) I am very familiar with ADB/fastboot... and use almost daily.
So here is the guide to brick. If Anyone have any idea please help me out!
--------------------------------------------------------------------------------------------------
1st, I tried to use this tool to root+TWRP+scurity patch http://forum.xda-developers.com/showthread.php?t=2713183&page=2 knowing it's NOT tested against 1/8/2100. I just tried anyway... The script went with a lot of errors, it seems the script cannot locate correct files but still push the security patched files into the /system/app (and other places).
I turn on the watch, but it just stuck at boot logo (the orange "Truesmart" logo without animation)
Also, the Recovery is still stock, TWRP is no where to be seen.
Since ADB still works, I adb reboot couple times, pull the battery, let the watch run for 2hrs, etc... Nothing works. The watch just stuck at the boot logo.
Than I follow this thread http://forum.xda-developers.com/showthread.php?t=2641261 and http://forum.xda-developers.com/showthread.php?t=2641261 with Stock firmware downloaded from http://d-h.st/users/Lokifish Marz/?fld_id=30814#files (Omate_1-8_2100_TrueSmart_20140328.zip)
I installed all drivers, restarts my Win 7 (x86) pc (several times), and after several attempts the Flashtool just flash in the Firmware.
The Tools flash with a green Check mark, indicating everything is ok!
However the watch just become a brick after this....
Than this completed the brick process! Now the watch won't even turn on, when I try to use Flash tool again, it always say S_FT_ENABLE_DRAM_FAIL. Google this and you find it's due to flashing wrong F/W, but I don't know where went wrong!
Anyone else have same problem or it's just me? Anyone have solution?
You said everything...
You made mistake but that shouldn't be problem.
You soft brick it using wrong recovery image and root tool but as you said, you had adb and fastboot on - so if you know what are you doing and I see you know (except of that pary of flashing something that's not for your device .) you should be able to flash stock firmware back.
If you can flash another firmware, try with other firmware...
Don't know what else to say....
Omate build piece of sh*t and we'll all have problems with it...
It's very hard to differentiate devices.
All of them has same nr on mother boards and, as I said, we will all have problems with Omate and their TrueSh*t...
Sent from my C6903 using Tapatalk
funky0308 said:
You said everything...
You made mistake but that shouldn't be problem.
You soft brick it using wrong recovery image and root tool but as you said, you had adb and fastboot on - so if you know what are you doing and I see you know (except of that pary of flashing something that's not for your device .) you should be able to flash stock firmware back.
If you can flash another firmware, try with other firmware...
Don't know what else to say....
Omate build piece of sh*t and we'll all have problems with it...
It's very hard to differentiate devices.
All of them has same nr on mother boards and, as I said, we will all have problems with Omate and their TrueSh*t...
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Ha! Very true! I think you are right! I believe Omate have many segmentation on their HW/SW, even with same model number.... A lot of things changes between versions which makes the "factory image" not compatible....
Anyone has the latest (4th list) 1/8/2100 TS who could dump their whole image for me would be helpful...
I would like to help you but mine is 2nd list and it's still on customs office...
Omate shipment experts, you just gotta love them....
Sent from my C6903 using Tapatalk
Not sure what to tell you on this. A board revision change is possible as the Omate_1-8_2100_TrueSmart_20140328.zip was from a 1/8 2100. I can't even test stuff anymore as I gave one to a tech student that's studying network and system security and the other four were stripped down, reworked into data gathering modules and then donated to near space projects.
Lokifish Marz said:
Not sure what to tell you on this. A board revision change is possible as the Omate_1-8_2100_TrueSmart_20140328.zip was from a 1/8 2100. I can't even test stuff anymore as I gave one to a tech student that's studying network and system security and the other four were stripped down, reworked into data gathering modules and then donated to near space projects.
Click to expand...
Click to collapse
Thanks Lokifish for your comment... Is there anyway to get a latest F/W? If you know anyone I could contact, please PM me... Thanks!
Anyone have yet received a 1/8/2100 on 4th list could PM me a Factory F/W dump?
I tried another XP PC with all steps checked and rechecked but still... No luck...
Teach me how to do a dump and I'll dump it for you. I was also looking how to backup my stock firmware before playing around, seeing as no one has our version of firmware uploaded for restore yet.
Also received mine yesterday and firmware version is 20140513, pretty damn recent.
You guys are going to have to help each other out on this one. I've already deleted 90% of any and all Android dev stuff from my personal file server and computer. This includes tools, guides and work going as far back as the original HTC Evo.
cheahcl said:
Teach me how to do a dump and I'll dump it for you. I was also looking how to backup my stock firmware before playing around, seeing as no one has our version of firmware uploaded for restore yet.
Also received mine yesterday and firmware version is 20140513, pretty damn recent.
Click to expand...
Click to collapse
Thanks a lot! First of all, Currently don't do anything posted on XDA yet since most of them will not work with this version of TS... (This is where I am now...)
First of all, please get all necessary tools directly from this post "All Tools" http://forum.xda-developers.com/showthread.php?t=2734687 (Do NOT download or install any other things there!)
Follow those steps: (modified from link above)
1. Download "All Tools"
2. Install Universal ADB Drivers (included in All Tools) <--If you already have ADB up and running, it's not necessarily, then.
3. Enable USB Debugging on watch
4. Launch MTKDroid Tools
5. Connect watch to PC
6. Please follow the instruction from here: http://www.chinaphonearena.com/foru...up-MTK6592-MTK6589-MTK6577-and-all-MTK-Phones
a. Skip everything above and just starts from "B) Open ADB prompt to begin communication with the phone" .
b. Don't worry about the recovery thing... TS comes with a recovery which is not locked and you can do everything this article said with only stock recovery. (also no busy box is needed, nor su since TS run everything in root!)
c. You could also refer to the video guide below for details
7. it's okay to just provide the file you got after finishing the step "C) Read back the ROM with MTK Droid Tools" I should be able to do the Step D) and after myself.
Thanks a lot for your help!
Lokifish Marz said:
You guys are going to have to help each other out on this one. I've already deleted 90% of any and all Android dev stuff from my personal file server and computer. This includes tools, guides and work going as far back as the original HTC Evo.
Click to expand...
Click to collapse
Dear Lokifish,
Could you please still keep those tools on the host servers so people can still access them? (Like "All tools", etc.) Please...... (I need a emoticon of a small kitten with big eyes here...)
Thanks!
ok will get it to tonight. about 6 hours time. cheers
lssong99 said:
Dear Lokifish,
Could you please still keep those tools on the host servers so people can still access them? (Like "All tools", etc.) Please...... (I need a emoticon of a small kitten with big eyes here...)
Thanks!
Click to expand...
Click to collapse
The space was given to me for free as a recognized developer and contributor. Seeing that I have left development completely, it is not right that I continue to use the services. So at the end of the week the files will be purged and I will ask the xda remove my developer and contributor status.
Lokifish Marz said:
The space was given to me for free as a recognized developer and contributor. Seeing that I have left development completely, it is not right that I continue to use the services. So at the end of the week the files will be purged and I will ask the xda remove my developer and contributor status.
Click to expand...
Click to collapse
Oh! I see the situation... In this case, may I have your permission to host those files somewhere (maybe by XDA moderator, or ...me?) so they could still be accessible?
I could feel your feeling on this fiasco. Must be quite frustrate experiences for you...
lssong99 said:
Oh! I see the situation... In this case, may I have your permission to host those files somewhere (maybe by XDA moderator, or ...me?) so they could still be accessible?
I could feel your feeling on this fiasco. Must be quite frustrate experiences for you...
Click to expand...
Click to collapse
https://dl.dropboxusercontent.com/u/25414599/!Files_to_FlashTool.rar
I've done step D as well, good to just flash it I guess.
Let me know if it worked, before I start messing about. I'm not good in all these stuff. Been flashing since HD2 days but still, just a tutorial follower, can probably count Linux commands I know with 1 hand.
cheahcl said:
https://dl.dropboxusercontent.com/u/25414599/!Files_to_FlashTool.rar
I've done step D as well, good to just flash it I guess.
Let me know if it worked, before I start messing about. I'm not good in all these stuff. Been flashing since HD2 days but still, just a tutorial follower, can probably count Linux commands I know with 1 hand.
Click to expand...
Click to collapse
Dear cheahcl,
Thank you soooo much for the image! I successfully restored my TS and now EVERYTHING GOES BACK TO NORMAL!
If you want to play around, please don't forge to back up your IMEI! since the MTK SP_Flash_Tool will wipe your IMEI!
Please follow this guide here: http://forum.xda-developers.com/showthread.php?t=2631953 under "IMEI Backup Procedure" before proceed anything dangerous!
After this, you are good to go! MTK is non-brickable (from what I learned for the past day... All you need is a corrected factory F/W!)
Thank you! Thank you! Thank you! Thank you! Thank you! Thank you!!
lssong99 said:
Dear cheahcl,
Thank you soooo much for the image! I successfully restored my TS and now EVERYTHING GOES BACK TO NORMAL!
If you want to play around, please don't forge to back up your IMEI! since the MTK SP_Flash_Tool will wipe your IMEI!
Please follow this guide here: http://forum.xda-developers.com/showthread.php?t=2631953 under "IMEI Backup Procedure" before proceed anything dangerous!
After this, you are good to go! MTK is non-brickable (from what I learned for the past day... All you need is a corrected factory F/W!)
Thank you! Thank you! Thank you! Thank you! Thank you! Thank you!!
Click to expand...
Click to collapse
don't sweat it, haha i needed to backup my original firmware as well anyways, seeing how scarce it is around here and all the weird discrepancies in HW/SW versions. good to know i can always fall back on this file. haha yeah i've also backed up my imei. time to play around and see.
cheers
Ive managed to get my brand new watch stuck in a bootloop after using framaRoot to root it. (I know, I know)
Now, I am able to boot into recovery mode or factory, and tried a factory reset. No luck, so i'm pretty sure the issue is in the /system partition.
Does anyone know if there are zip files somewhere that i can flash from recovery, to restore the system partition?
Device:
- 1GB / 8GB / 2100MHz Version
- Originally unrooted
- OUI 2.1
- Modem Ver: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
- No other modifications besides the rooting (which did work already before I rebooted)
Spoetnicus said:
Ive managed to get my brand new watch stuck in a bootloop after using framaRoot to root it. (I know, I know)
Now, I am able to boot into recovery mode or factory, and tried a factory reset. No luck, so i'm pretty sure the issue is in the /system partition.
Does anyone know if there are zip files somewhere that i can flash from recovery, to restore the system partition?
Device:
- 1GB / 8GB / 2100MHz Version
- Originally unrooted
- OUI 2.1
- Modem Ver: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
- No other modifications besides the rooting (which did work already before I rebooted)
Click to expand...
Click to collapse
The TS (or any MTK based system) does not use the usually "recovery backup/restore" way we familiar of, instead it goes the "special tool on PC backup/restore" method. You need ask people who receive their watch in around the same time as yours with same configuration to backup their watch FW with MTK tools than restore with said FW.
Basically what I had done in this thread!
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Sent from my HTC_One_max using XDA Premium HD app
lssong99 said:
The TS (or any MTK based system) does not use the usually "recovery backup/restore" way we familiar of, instead it goes the "special tool on PC backup/restore" method. You need ask people who receive their watch in around the same time as yours with same configuration to backup their watch FW with MTK tools than restore with said FW.
Basically what I had done in this thread!
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Sent from my HTC_One_max using XDA Premium HD app
Click to expand...
Click to collapse
Thanks!
Im pretty sure that I was on 'Omate_TrueSmart_20140513.103530_V2.0' before I bricked it, so that gives hope
I dont have it with me right now, but Ill try it as soon as I get back home on monday
Thanks again for the tutorials and reply
lssong99 said:
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Click to expand...
Click to collapse
HEY! It worked
I'm back at a functional Truesmart
Thank you soo much
And in case three smiley's aren't enough:
Also, quick note for other people bricking their phone, my issue (after I bricked it again), was that I used an app to change the density property, which broke the boot of the watch.
The app that broke my watch was: https://play.google.com/store/apps/details?id=com.birdapi.android.dpi
Hi all,
I'm having trouble getting Safestrap to install and work properly on my VerizonSG4. Phone is rooted with stock ROM and still on 4.3 with updates and notifications blocked.(SDM frozen with TB) Other mods include Exposed Framework using 2 modules,Greenify, Busybox, and a couple other root dependent apps that are not likely to be the issue. The problem I'm having is that upon getting Safestrap to install (which took multiple attempts) it will open to the screen where you can choose to install or uninstall recovery and when I hit install it does its thing but shows "State: Not Installed". However, I DO get a little pop up at the bottom of the screen that says" Installation Complete". Safe System says " Not Active" and " Reboot to Recovery" is grayed out so that I can't select it. Manual reboot into recovery brings up stock recovery so I'm not sure what's going on. I've tried everything I can think of to make it work including defrosting SDM, disabling my antivirus, verifying that USB debugging is enabled, etc. So I'm frustrated and could use some insight. I'm obviously missing something or doing something wrong so any help would be greatly appreciated. Oh, and the apk that I downloaded was Safestrap-JFLTEVZW-3.71which is supposed to be the correct on for Verizon MK2.
Thanks in advance
markctco said:
Hi all,
I'm having trouble getting Safestrap to install and work properly on my VerizonSG4. Phone is rooted with stock ROM and still on 4.3 with updates and notifications blocked.(SDM frozen with TB) Other mods include Exposed Framework using 2 modules,Greenify, Busybox, and a couple other root dependent apps that are not likely to be the issue. The problem I'm having is that upon getting Safestrap to install (which took multiple attempts) it will open to the screen where you can choose to install or uninstall recovery and when I hit install it does its thing but shows "State: Not Installed". However, I DO get a little pop up at the bottom of the screen that says" Installation Complete". Safe System says " Not Active" and " Reboot to Recovery" is grayed out so that I can't select it. Manual reboot into recovery brings up stock recovery so I'm not sure what's going on. I've tried everything I can think of to make it work including defrosting SDM, disabling my antivirus, verifying that USB debugging is enabled, etc. So I'm frustrated and could use some insight. I'm obviously missing something or doing something wrong so any help would be greatly appreciated. Oh, and the apk that I downloaded was Safestrap-JFLTEVZW-3.71which is supposed to be the correct on for Verizon MK2.
Thanks in advance
Click to expand...
Click to collapse
After rooting your phone with presumably saferoot did you open up SuperSu and update it's binary?
Sounds like a Superuser problem. Either open up SuperSu and update binary the " normal" way or run saferoot again if that doesn't work and then update binary. Then you should be OK to install SafeStrap.
Sent from my SCH-I545 using Tapatalk
Solved it!
Mistertac said:
After rooting your phone with presumably saferoot did you open up SuperSu and update it's binary?
Sounds like a Superuser problem. Either open up SuperSu and update binary the " normal" way or run saferoot again if that doesn't work and then update binary. Then you should be OK to install SafeStrap.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Thanks for the response, and I actually figured it out last night. But you were on the right track. After trying a download from a different source the apk installed, opened up and showed that I wasn't rooted! Surprised me because the app itself needed super user rights itself so I knew I was rooted. Turns out I needed to have the paid/full version of SuperSU! Bought it and I now have Safestrap. I know I should probably always purchase the full versions of such high tech apps but damn it would have been nice if someone...anyone would have said that. I'm guessing there are other versions of SuperUser that may work differently right out of the box? IDK but I'm up and running and grateful that I didn't brick my phone. Been down that road before and know that it doesn't take much to mess things up.
Anyway, thanks to all that read and maybe this will help someone else
markctco said:
Thanks for the response, and I actually figured it out last night. But you were on the right track. After trying a download from a different source the apk installed, opened up and showed that I wasn't rooted! Surprised me because the app itself needed super user rights itself so I knew I was rooted. Turns out I needed to have the paid/full version of SuperSU! Bought it and I now have Safestrap. I know I should probably always purchase the full versions of such high tech apps but damn it would have been nice if someone...anyone would have said that. I'm guessing there are other versions of SuperUser that may work differently right out of the box? IDK but I'm up and running and grateful that I didn't brick my phone. Been down that road before and know that it doesn't take much to mess things up.
Anyway, thanks to all that read and maybe this will help someone else
Click to expand...
Click to collapse
I'm not sure why you had to get a paid version of su. I had the SU zip and installed it as part of the upgrade/downgrade method
sent by baja kitkat S4
Definitely shouldn't need the paid version but hey good to support Chainfire anyways.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Definitely shouldn't need the paid version but hey good to support Chainfire anyways.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yes, I found that odd also. When I switched to the other apk download it installed but said I did not have root, so I backed out one step and under the apk download that I selected was text in red that said "full version of SuperSu is required to complete this operation." So I paid for the full version, rebooted and everything worked fine from there. At that point the price was worth it, plus I typically use free versions of apps if I can get away with it so by supporting the Dev, as stated, perhaps I made a small deposit in the karma bank
Now I'm just trying to figure out if I need to do a factory reset before installing Hyperdrive. This is not my first ROM install but is under this format, so i want to take every precaution. Any suggestions? Leaning towards doing it except for concern about my phone downloading KitKat before I can reinstall TB and block it. Maybe I just need to be quick fingered. Again, open for suggestions.
Thanks in advance
markctco said:
Yes, I found that odd also. When I switched to the other apk download it installed but said I did not have root, so I backed out one step and under the apk download that I selected was text in red that said "full version of SuperSu is required to complete this operation." So I paid for the full version, rebooted and everything worked fine from there. At that point the price was worth it, plus I typically use free versions of apps if I can get away with it so by supporting the Dev, as stated, perhaps I made a small deposit in the karma bank
Now I'm just trying to figure out if I need to do a factory reset before installing Hyperdrive. This is not my first ROM install but is under this format, so i want to take every precaution. Any suggestions? Leaning towards doing it except for concern about my phone downloading KitKat before I can reinstall TB and block it. Maybe I just need to be quick fingered. Again, open for suggestions.
Thanks in advance
Click to expand...
Click to collapse
You should have plenty of time. I've flashed back to stock so many times and never had that update pop up before I could freeze SDM
I have an MDK phone so I'm not 100% up to speed on what you should do... @decaturbob has done it all and I'm sure would help send you down the right path
Sent from my SCH-I545 using Tapatalk
markctco said:
Yes, I found that odd also. When I switched to the other apk download it installed but said I did not have root, so I backed out one step and under the apk download that I selected was text in red that said "full version of SuperSu is required to complete this operation." So I paid for the full version, rebooted and everything worked fine from there. At that point the price was worth it, plus I typically use free versions of apps if I can get away with it so by supporting the Dev, as stated, perhaps I made a small deposit in the karma bank
Now I'm just trying to figure out if I need to do a factory reset before installing Hyperdrive. This is not my first ROM install but is under this format, so i want to take every precaution. Any suggestions? Leaning towards doing it except for concern about my phone downloading KitKat before I can reinstall TB and block it. Maybe I just need to be quick fingered. Again, open for suggestions.
Thanks in advance
Click to expand...
Click to collapse
the steps listed in surge's method are pretty easy and there is a video. Once you have rooted NC5 deox rom installed, then you can flash another rom right over the top as you would normally do. I installed Bajarom.
- roms go in stock slot
- be sure to flash SU update.zip (a step in safestrap right after you flash hyperdrive)
decaturbob said:
the steps listed in surge's method are pretty easy and there is a video. Once you have rooted NC5 deox rom installed, then you can flash another rom right over the top as you would normally do. I installed Bajarom.
- roms go in stock slot
- be sure to flash SU update.zip (a step in safestrap right after you flash hyperdrive)
Click to expand...
Click to collapse
Ok, thanks, but now I'm hung up again. But first of all let me say that there are numerous methods to be found online and I'm not familiar with surge's method, plus I'm not sure exactly how or when to flash the SU update .zip you mention. With that being said, after getting Safestrap to run I decided to flash a Hyperdrive ROM. Following several a combination of instructions and videos, I settled on Hyperdrive RLS12 as it claims to work with 4.3/MK2. But I've also seen that I need to flash the correct module, in this case JFLTEVZW-MK2-modules.zip file. There are conflicting instructions as to whether to flash both zips together or to flash the ROM and then the module just before rebooting. I've also read that I need to wipe cache etc. before rebooting.
Long story short, no matter what I try, I always get the same results...I see the Verizon Galaxy S4 logo followed by a black screen followed by a new boot audio? followed by over 30 minutes of black screen and a very hot battery. I have wiped rom slots between flashes, tried different ROM slots, just about everything I can think of besides the SU update. So perhaps someone can provide some detail on that step and some clarity on the other steps that vary from source to source.
I'm sure I'm doing something wrong but have gotten to a point where I'm just going to leave it alone for a while and use my stock ROM until I can get some help UGHHH
Thanks in advance
markctco said:
Ok, thanks, but now I'm hung up again. But first of all let me say that there are numerous methods to be found online and I'm not familiar with surge's method, plus I'm not sure exactly how or when to flash the SU update .zip you mention. With that being said, after getting Safestrap to run I decided to flash a Hyperdrive ROM. Following several a combination of instructions and videos, I settled on Hyperdrive RLS12 as it claims to work with 4.3/MK2. But I've also seen that I need to flash the correct module, in this case JFLTEVZW-MK2-modules.zip file. There are conflicting instructions as to whether to flash both zips together or to flash the ROM and then the module just before rebooting. I've also read that I need to wipe cache etc. before rebooting.
Long story short, no matter what I try, I always get the same results...I see the Verizon Galaxy S4 logo followed by a black screen followed by a new boot audio? followed by over 30 minutes of black screen and a very hot battery. I have wiped rom slots between flashes, tried different ROM slots, just about everything I can think of besides the SU update. So perhaps someone can provide some detail on that step and some clarity on the other steps that vary from source to source.
I'm sure I'm doing something wrong but have gotten to a point where I'm just going to leave it alone for a while and use my stock ROM until I can get some help UGHHH
Thanks in advance
Click to expand...
Click to collapse
have you looked at any youtube videos concerning S4 and safestrap?
decaturbob said:
have you looked at any youtube videos concerning S4 and safestrap?
Click to expand...
Click to collapse
Absolutely! But good news, phone is now booting! I tried flashing both zips together and it's working...at least I think it is. Displaying what I think is Google Play Edition boot image, 4 dots, yellow green red and blue zooming in and out. Not sure how long this is supposed to go on but I'm further along than previously. Any suggestions in case I end up in a boot loop or how long to wait to decide?
markctco said:
Absolutely! But good news, phone is now booting! I tried flashing both zips together and it's working...at least I think it is. Displaying what I think is Google Play Edition boot image, 4 dots, yellow green red and blue zooming in and out. Not sure how long this is supposed to go on but I'm further along than previously. Any suggestions in case I end up in a boot loop or how long to wait to decide?
Click to expand...
Click to collapse
Did you check the thread for compatibility of roms with ss?
sent by baja kitkat S4
decaturbob said:
Did you check the thread for compatibility of roms with ss?
sent by baja kitkat S4
Click to expand...
Click to collapse
Yup! As a matter of fact this is the video I watched that shows Hyperdrive RSL12 on the exact same phone as mine with 4.3 MK2 build.I think this is also the one that suggests flashing the module at the end. I've watched so many videos I can't remember which ones say what.
Am I missing something? I've made sure that I have USB debugging checked as well as unknown sources before flashing, I've tried flashing both zips at the same time and individually, even tried again without selecting any music players besides the Samsung one and not picking any audio mods when setting up the rom as per someones post on some blog somewhere. I've changed boot image, keyboards...I'm just about over this ROM. It can clearly be used with 4.3 but just not for me I quess? I've even considered backing up my stock rom and doing a factory reset on my phone and then starting from scratch. I'm just hoping I don't have to update to KitKat, which by the way is what Hyperdrive's website states you have to do, but this video contradicts that. UGHHH AGAIN!
http://www.youtube.com/watch?v=pA8cV3-r3oU
Wow, really? Nothing? No one? I thought this was where all the Android Root and Rom specialist hung out? Am I posting in the wrong thread or something? I cannot be the only one with this problem, can I?
markctco said:
Wow, really? Nothing? No one? I thought this was where all the Android Root and Rom specialist hung out? Am I posting in the wrong thread or something? I cannot be the only one with this problem, can I?
Click to expand...
Click to collapse
Alright since your trying Rls12 this should be easy since that's for Mk2.. Which your on.
Hop into SafeStrap and create a ROM slot. After its created activate that ROM slot. Then for good measure once your on that ROM slot wipe it.. Factory data reset. Then proceed to flash the Hyperdrive zip. Once that's finished don't leave SafeStrap until you'll flash those modules.
Then you can wipe cache and Dalvic again before rebooting.
If that's still not working for you I'm not sure where the problem lies. You're using SafeStrap v3.71 right?? Not version 3.72..
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Alright since your trying Rls12 this should be easy since that's for Mk2.. Which your on.
Hop into SafeStrap and create a ROM slot. After its created activate that ROM slot. Then for good measure once your on that ROM slot wipe it.. Factory data reset. Then proceed to flash the Hyperdrive zip. Once that's finished don't leave SafeStrap until you'll flash those modules.
Then you can wipe cache and Dalvic again before rebooting.
If that's still not working for you I'm not sure where the problem lies. You're using SafeStrap v3.71 right?? Not version 3.72..
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Thanks for responding! And yes I'm using that version of Safestrap and did everything you mentioned as per this video:
http://www.youtube.com/watch?v=l4F5UYDcQ5A
The only thing I can think of comes from something someone else mentioned about updating superuser binaries which made me realize that SuperSu, which is what I have doesn't appear to have that option. I checked the Play Store and there is the original Super User apk that I've used before to root other versions before all this bootloader crap started. I remember updating binaries in that version...I think. It may have been an option in CWM which I've also used. Could that be the issue? SuperSu acts just like Super User, asking for permissions and whatnot, but maybe Safestrap needs the other version. I think I'm going to uninstall or freeze (better idea) SuperSu and install the regular SuperUser. What gets me thought is that they are both developed by Chainfire, so I'm not sure what the difference would be. I do know that something is not right because I'm confident I'm doing everything as instructed.
HOT DAMN! I got it! It was a SuperSu issue, just took me a bit to figure out how to update binaries. It doesn't just have a button for that, had to uninstall and reinstall newest version.
Wow, what a trip that was! And I love the ROM.Gotta go and play now though
Thanks for everyones help and patience!
markctco said:
Hi all,
I'm having trouble getting Safestrap to install and work properly on my VerizonSG4. Phone is rooted with stock ROM and still on 4.3 with updates and notifications blocked.(SDM frozen with TB) Other mods include Exposed Framework using 2 modules,Greenify, Busybox, and a couple other root dependent apps that are not likely to be the issue. The problem I'm having is that upon getting Safestrap to install (which took multiple attempts) it will open to the screen where you can choose to install or uninstall recovery and when I hit install it does its thing but shows "State: Not Installed". However, I DO get a little pop up at the bottom of the screen that says" Installation Complete". Safe System says " Not Active" and " Reboot to Recovery" is grayed out so that I can't select it. Manual reboot into recovery brings up stock recovery so I'm not sure what's going on. I've tried everything I can think of to make it work including defrosting SDM, disabling my antivirus, verifying that USB debugging is enabled, etc. So I'm frustrated and could use some insight. I'm obviously missing something or doing something wrong so any help would be greatly appreciated. Oh, and the apk that I downloaded was Safestrap-JFLTEVZW-3.71which is supposed to be the correct on for Verizon MK2.
Thanks in advance
Click to expand...
Click to collapse
Edited
---------- Post added at 10:01 PM ---------- Previous post was at 09:57 PM ----------
Install Terminal Emulator. Type su and press enter. Then type setenforce 0 with a space after setenforce. Then press enter and reopen SafeStrap and all is well. The reboot recovery button will not be greyed out no more.
James- tech for a site dealing with Android day and night!
From many many different threads and frankly confusing instructions I think I have puzzled together the following solid guideline for my kindle fire hdx from basic root to custom rom. Currently my firmware is 13.3.1.0.
Could someone take a look at this and tell me if I got this right or if I need to do stuff differently (or could do them better)? Don't assume that something is obvious, if it isn't written down, don't be shy to mention it. I would be ever so grateful .
Edit: I'm updating my experience as I move along the list and get more info just in case this might be useful to someone who is just as lost as I was in the beginning
Obligatory disclaimer: this is just a step-by-step guideline that worked for me. I'm not responsible if you chose to follow any of these steps and damage or brick your device.
Guideline:
-Download firmware version 3.2.3.2 and upgrade directly from any of the previous version by putting the file into the internal storage of the kindle, going to settings>device>system update on the kindle and installing the update from there.
-Root with Towelroot in the HDX toolkit downloaded from here (Edit: I got various error messages at this step but got it to work in the end. The 3rd post here shows what I did to get it working after getting error message 2 and 3 at various times)
-block OTA also with the tool in the HDX toolkit (is there a way to safely check that this worked? Edit: It worked )
-connect to wifi and install Flashify from the playstore (Edit: I ended up installing File Expert and flashify on another android device, backing up the flashify apk and sideloading it with ES File Explorer from the amazon app store to the kindle, I guess I could have also download the apk somewhere but I have trust issues.)
-download the img of TWRP 2.8.5.0. and put it in internal storage of kindle (had no problems)
-use flashify to save original stock recovery (had no problems)
-Use flashify to flash TWRP (had no problems)
- Boot into recovery mode via flashify to see if it worked (had no problems)
Now either A)
-download CM11 image and gapps and put the zip files on internal storage
-Edit: disconnect Kindle from USB afterwards
- go into TWRP recovery mode (by powering off kindle and then pressing power and volume at the same time)
- make backup of original stockrom under backups and save copy on your Computer
- wipe system, data, cache and dalvik cache under wipe/advanced (all except internal)
- flash cm11 image and gapps (under install and then find them in the files)
- reboot
-Edit: I had the wifi not connecting problem that some people have with CM11 but a reboot took care of it.
-Edit 2: I couldn't get the kindle app to work on CM11 (it wouldn't synch my books, the device wasn't recognized by amazon and it would crash every time I logged in.) so I ended up replacing it with the Nexus rom. If the chance of this happening doesn't bother you then CM11 seems to still be a good choice.
or B)
- download HDX thor nexus rom and gapps and put the zip files on internal storage
- go into TWRP recovery mode (by powering off kindle and then pressing power and volume at the same time)
- make backup of original stockrom under backups and save copy on your Computer
- wipe system, data, cache and dalvik cache under wipe/advanced (all except internal)
- Edit: disconnect Kindle from USB afterwards
- flash nexus rom and gapps (under install and then find them in the files)
- reboot
- Edit: I'm very happy with it, it works flawlessly. Since it's based on Jelly Bean I may try replacing it with another rom sometime in the future, but I'm in no hurry
Mostly correct, you can update directly to 3.2.3.2 no need for incremental steps. The only way to know if ota blocker worked is to check for update but there's really no need, as soon as you've run towel root just disable WiFi as it won't be needed anymore.
Where is unlock bootloader? As I know, you cannot flash TWRP without unlocking bootloader?!
uhraman said:
Where is unlock bootloader? As I know, you cannot flash TWRP without unlocking bootloader?!
Click to expand...
Click to collapse
You can flash a cuber signed TWRP on a locked bootloader, as long as you're below 3.2.4.
derpadoodle said:
You can flash a cuber signed TWRP on a locked bootloader, as long as you're below 3.2.4.
Click to expand...
Click to collapse
Thanks for your replies! Is the method uhraman hinted at the better one?
snorklm said:
Thanks for your replies! Is the method uhraman hinted at the better one?
Click to expand...
Click to collapse
Fully unlocking your bootloader is definitely worthwhile but it's quite a complicated endeavour and not required for running the current custom recoveries and ROMs. I'd recommend you stick with your current method and read up on the unlocking process once you're more conformable working with this device.
derpadoodle said:
Fully unlocking your bootloader is definitely worthwhile but it's quite a complicated endeavour and not required for running the current custom recoveries and ROMs. I'd recommend you stick with your current method and read up on the unlocking process once you're more conformable working with this device.
Click to expand...
Click to collapse
Could I bother you to give me a few examples on *why* it is worthwhile? Thanks!
snorklm said:
Could I bother you to give me a few examples on *why* it is worthwhile? Thanks!
Click to expand...
Click to collapse
- more robust recovery options when recovery (TWRP) is damaged/inaccessible; better chance of reviving a bricked device
- some custom roms install/operate better with unlocked BL (technically should not be needed but sometimes seen in early builds)
- some DRM aware apps on custom roms work better with unlocked BL(eg: playstore, prime)
Guidance form derpadoodle is sound. Enjoy what you have achieved thus far; revisit BL unlock when you are more comfortable with device/technique.
Davey126 said:
- more robust recovery options when recovery (TWRP) is damaged/inaccessible; better chance of reviving a bricked device
- some custom roms install/operate better with unlocked BL (technically should not be needed but sometimes seen in early builds)
- some DRM aware apps on custom roms work better with unlocked BL(eg: playstore, prime)
Guidance form derpadoodle is sound. Enjoy what you have achieved thus far; revisit BL unlock when you are more comfortable with device/technique.
Click to expand...
Click to collapse
Thanks for the sound advice, I will probably never feel comfortable enough for that , especially because I haven't achieved much at all yet. I haven't even flashed TWPR yet.
Yay, I did it. CM11 seems to be working as intended! Thanks again for everyone who replied and also to everyone who put so much work into making and improving all the tools and software necessary to make this kind of thing even possible, I appreciate it!
What firmware were you on to begin your process mate... ?
B3NJY said:
What firmware were you on to begin your process mate... ?
Click to expand...
Click to collapse
I was on 3.0.5 when I got the device. Amazon didn't upgrade the firmware at all before sending it out, then I upgraded to 13.3.2.3. Why do you ask?
Hmm, I have now noticed that the kindle app is not working properly. I can sign in (though every time I sign in or deregister my account the app crashes) but it's not synching any of my books. They don't show up at all. The device (named android device 2 in the kindle app settings) does also not show up under my devices on amazon. Anyone know what the problem could be because this is a bit frustrating. Is this a bug with CM11 or with the amazon app?
snorklm said:
Hmm, I have now noticed that the kindle app is not working properly. I can sign in (though every time I sign in or deregister my account the app crashes) but it's not synching any of my books. They don't show up at all. The device (named android device 2 in the kindle app settings) does also not show up under my devices on amazon. Anyone know what the problem could be because this is a bit frustrating. Is this a bug with CM11 or with the amazon app?
Click to expand...
Click to collapse
Can't say definitively but I would lean towards CM11 as all Amazon apps (kindle/prime/shopping/video) work fine with the Nexus ROM (v2.0.5) which is layered on the same hw/fw base as CM11. Don't get me wrong; CM11 (and the devs who adapted to the HDX) are great! But there may still be a few hiccups with native Amazon apps.
Davey126 said:
Can't say definitively but I would lean towards CM11 as all Amazon apps (kindle/prime/shopping/video) work fine with the Nexus ROM (v2.0.5) which is layered on the same hw/fw base as CM11. Don't get me wrong; CM11 (and the devs who adapted to the HDX) are great! But there may still be a few hiccups with native Amazon apps.
Click to expand...
Click to collapse
Thanks for the opinion! I couldn't find any solution to the problem anywhere online and therefore just finished replacing CM11 with the Nexus rom, now the kindle app works perfectly fine and I'm very satisfied with what I've got. I will keep an eye out on rom development but for now I'm resting on my laurels :victory:. Considering that I was helplessly lost when I first came to the board I'm very happy with how smoothly everything went. But I really needed that step-by-step list I made and the assurance from the pros that it was correct, otherwise I would have probably made a careless mistake :silly:. Maybe it will be useful to a few other newbies as well. Not sure I will ever dare to fully unlock the bootloader like some suggested I might want to do at a later point in time, but we will see . Thanks again for the help!
snorklm said:
Thanks for the opinion! I couldn't find any solution to the problem anywhere online and therefore just finished replacing CM11 with the Nexus rom, now the kindle app works perfectly fine and I'm very satisfied with what I've got. I will keep an eye out on rom development but for now I'm resting on my laurels :victory:. Considering that I was helplessly lost when I first came to the board I'm very happy with how smoothly everything went. But I really needed that step-by-step list I made and the assurance from the pros that it was correct, otherwise I would have probably made a careless mistake :silly:. Maybe it will be useful to a few other newbies as well. Not sure I will ever dare to fully unlock the bootloader like some suggested I might want to do at a later point in time, but we will see . Thanks again for the help!
Click to expand...
Click to collapse
Glad to hear everything is working well! My daily driver is on Nexus and I could not be happier. Everything works as it should. No need to unlock the bootloader unless you plan to do more modding. Enjoy your device!
Nice. I think everybody needs this kind of guide. Whenever a question is asked it just kind of trails off most of the time.
I'm still working on the downgrade piece.
johnwaters said:
Nice. I think everybody needs this kind of guide. Whenever a question is asked it just kind of trails off most of the time.
I'm still working on the downgrade piece.
Click to expand...
Click to collapse
Agreed, I was overwhelmed by all the different threads and possibilities at first. I ended up approaching it like any other research project for a paper or presentation and dumped every solid (and recent) piece of good advice into Evernote and sorting it out there. But writing and updating guides (especially with the fast development I have observed) would be a lot of work, I understand completely why no one would volunteer to do it and everybody would rather answer questions on a case by case basis.
First of all thank you very much! I was looking for something like this, since i am also new to rooting devices and this stuff...
I got a new fire hdx 7 with 13.3.02
I haven't tried anything yet, I am still reading threads and i got some questions here:
http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813
-> I can only find 3.2.3.2 here, which is the firmware u used? Or did you mean another one?
http://forum.xda-developers.com/show....php?t=2665683
-> the second link for hdx toolkit isnt working
How do i get the playstore on my device?
are there anywhere more informations regarding flashify? since i have no idea what this is...
thank you!
dynein said:
First of all thank you very much! I was looking for something like this, since i am also new to rooting devices and this stuff...
I got a new fire hdx 7 with 13.3.02
I haven't tried anything yet, I am still reading threads and i got some questions here:
http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813
-> I can only find 3.2.3.2 here, which is the firmware u used? Or did you mean another one?
http://forum.xda-developers.com/show....php?t=2665683
-> the second link for hdx toolkit isnt working
How do i get the playstore on my device?
are there anywhere more informations regarding flashify? since i have no idea what this is...
thank you!
Click to expand...
Click to collapse
First thing you want to do is block OTA (over the air updates) or your device may be upgraded by Amazon to a level that gives you less options. Suggest using HDX Toolkit (here) to both root and block OTA. Then install twrp (here). From there you can opt to replace Fire OS will several different roms including Nexus, CM11 or CM12.
Flashify is an app that allows flashing recovery and roms from from within Android vs adb or a recovery environment. You can grab it from the Play store or another market. It's a dangerous tool; use with extreme caution.
Be aware that any of the above actions, if executed incorrectly, can permanently brick your device with little/no hope of recovery (guess that's the definition of permanent). Read, read and read some more before taking any action. Be sure to keep WiFi off on your device until OTA is blocked to prevent auto-updates.
hi guys
newest firmware is out, completely solved the constant flash of the screen during sleep mode (as a result, battery will last much longer)
as usual, flash with stock recovery (WW-5.17.44.68 is recommanded) and than go back to TWRP, if you didn't unlock your bootloader just wait till
you can trigger the update via the Settings -> Software Update option.....
So far I can confirm it boots alright, still on Android 7.0 and the security patch is updated to 5 Feb 2018 (which is pretty cool, no KRACK or BLUEBORNE exploits....)
discussion?
Chaosruler said:
hi guys
newest firmware is out, completely solved the constant flash of the screen during sleep mode (as a result, battery will last much longer)
Click to expand...
Click to collapse
Interesting, was this an issue with the WW-5.17.44.68 update or has this been an ongoing issue? I didn't bother with the previous one because it didn't seem to do a whole lot, but never noticed this issue.
Chaosruler said:
as usual, flash with stock recovery (WW-5.17.44.68 is recommanded) and than go back to TWRP, if you didn't unlock your bootloader just wait till
you can trigger the update via the Settings -> Software Update option.....
Click to expand...
Click to collapse
I hate doing this juggle. Big part of why I don't try to update unless it's significant :/
Chaosruler said:
So far I can confirm it boots alright, still on Android 7.0 and the security patch is updated to 5 Feb 2018 (which is pretty cool, no KRACK or BLUEBORNE exploits....)
Click to expand...
Click to collapse
Thanks for the heads up on this. I check the release thread often in hopes of Oreo, but they don't bother putting this information on their small updates. I think I'll update just because of that really, although Oreo would have been nice too :silly:
Chaosruler said:
discussion?
Click to expand...
Click to collapse
I feel like there's probably only 2 or 3 people who check these forums often nowadays, which is a shame because the phone is quite nice, and even has the bootloader unlocked as well. But ASUS seems to have too many phones that need updates and we're left in the dust waiting. Both XDA and Zentalk forums have people complaining and talking about this being their last device, which is reasonable and align with my thoughts as well. Really though, I want to go and make my own ROM for this phone, but don't really have the time, resources, or experience to tackle it just yet. Maybe I can use it in the future for practice
Update Impressions
Happy to report that the update has improved my phone's performance. Before, when I would go to the gym, listening to Spotify via Bluetooth would drain the battery from 95%->60%. Post update, battery stayed above 80% from full charge. It also feels a bit faster overall. It's a bit too early to tell if it's for better or for worse, but right now I'm leaning towards better. Negative would be it reinstalls the bloatware, but after rerooting and using Titanium Backup, they were removed without issue.
If you're rooted with TWRP installed, I'll list the update procedure I did, since we don't get the OTA updates. I'm also writing it up just to have it for reference. I have the ZS570KL @ 2.15GHz so make sure if you're Pro(2.4GHz) you make adjustments. You'll also need a computer (I use Win10 but any computer with fastboot installed will work really) with fastboot in order to reflash TWRP.
Part 1: Returning to stock recovery and updating
1. Downloaded update from Here. 2.15GHz should be the second one down.
2. Downloaded stock recovery from Here. /u/Ryder. has pointed out the Zentalk forum has the latest recoveries available, so check there first. At the time of writing, I was pushed to login to view that forum, so instead I just grabbed the latest available from AndroidFileHost, 5.15.44.2562.
3. Move both to SD card. I don't think this might be necessary, but I know it works. I think stock recovery only reads off the SD card, but I can't recall. If you can't navigate to the files during the update, try doing this step.
4. Reboot into TWRP by turning the phone off, and then powering on while holding the Volume Down button.
5. In TWRP, hit Install, navigate to the SD card, and select the stock recovery. Swipe to flash it.
6. Reboot into recovery again. Once you see the ASUS logo, spam the volume keys. I had an issue where it would boot into a "No Command!" screen. Pressing the volume keys while it's loading up the recovery pushes it to load properly. If you get stuck in the "No Command" screen for more than 2 minutes, reboot by pressing and holding VolumeDown+Power buttons.
7. Once in stock recovery, select apply update, navigate to the update file and flash.
8. Reboot into updated firmware!
Part 2: Reinstalling TWRP
1. On your fastboot enabled computer, download TWRP 3.2.1* from Here. Rename the file something short to make it easier to flash (I renamed it to TWRP.img). *3.2.1 is available in the Mega. At the time of writing, I only checked the AndroidFileHost link and didn't check to see if there was an updated build for it. It is Oreo compatible, so when they finally get around to giving us Oreo, you'll have a suitable recovery to go along with it. Thanks to /u/Ryder. for the heads up.
2. Open a command window. Make sure you either move the file to the directory it opens to, or navigate to the folder it's in.
3. Put your phone into fastboot by shutting it down, then powering on while holding the volume up button. It should say FASTBOOT on the screen.
4. Plug phone into computer.
5. Run the command "fastboot flash recovery [TWRP.img]" where [TWRP.img] is whatever your file name is.
6. Reboot into recovery to test it!
Part 3: (Optional) Rooting your phone with Magisk
1. Download the Magisk Manager APK from Here. Only grab it from here, I don't think the PlayStore one is legitimate.
2. Open Magisk Manager, and hit install. It should prompt you to download Magisk 16. Hit install in the popup. Let it download.
3. Reboot into TWRP. Hit install, and navigate to the file (should be something like InternalStorage/MagiskManager/Magisk-v16.zip). Install it. Before rebooting, I recommend wiping Dalvik/Art and Cache.
4. Open Magisk Manager to check if it's installed. Enjoy root!
Hope this helps someone out there. With the infrequent, non-OTA updates, I have to remember how to do this every time I update. It's easier to have it written down for reference.
Awesome guide!
I think its worth to mention that Win10 is not a must, you can use any Windows from XP forwards as long as you install the android adb driver and software, you can also use Linux (most package managers handles symlink to adb) as well as Mac....
Also the adjustment done between the snapdragon 820 and snapdragon 821 version is not just around the update file downloaded but it's super important to make sure to not do that mistake, not all recoveries handle checking and if you flash the wrong file you might brick your device, even though its likely you could fastboot your fw slowly, youd lose all your data, so its better to back up your data on your sd card
Error when I try to download.
This the response I get from ASUS's website:
An error occurred while processing your request.
Reference #132.563d717.1520889776.1930fb2f
asianflipboy said:
Happy to report that the update has improved my phone's performance. Before, when I would go to the gym, listening to Spotify via Bluetooth would drain the battery from 95%->60%. Post update, battery stayed above 80% from full charge. It also feels a bit faster overall. It's a bit too early to tell if it's for better or for worse, but right now I'm leaning towards better. Negative would be it reinstalls the bloatware, but after rerooting and using Titanium Backup, they were removed without issue.
If you're rooted with TWRP installed, I'll list the update procedure I did, since we don't get the OTA updates. I'm also writing it up just to have it for reference. I have the ZS570KL @ 2.15GHz so make sure if you're Pro(2.4GHz) you make adjustments. You'll also need a computer (I use Win10) with fastboot in order to reflash TWRP.
Part 1: Returning to stock recovery and updating
1. Downloaded update from Here. 2.15GHz should be the second one down.
2. Downloaded stock recovery from Here. I just grabbed the latest available, 5.15.44.2562.
3. Move both to SD card. I don't think this might be necessary, but I know it works. I think stock recovery only reads off the SD card, but I can't recall. If you can't navigate to the files during the update, try doing this step.
4. Reboot into TWRP by turning the phone off, and then powering on while holding the Volume Down button.
5. In TWRP, hit Install, navigate to the SD card, and select the stock recovery. Swipe to flash it.
6. Reboot into recovery again. Once you see the ASUS logo, spam the volume keys. I had an issue where it would boot into a "No Command!" screen. Pressing the volume keys while it's loading up the recovery pushes it to load properly. If you get stuck in the "No Command" screen for more than 2 minutes, reboot by pressing and holding VolumeDown+Power buttons.
7. Once in stock recovery, select apply update, navigate to the update file and flash.
8. Reboot into updated firmware!
Part 2: Reinstalling TWRP
1. On your fastboot enabled computer, download TWRP 3.1.1 from Here. Rename the file something short to make it easier to flash (I renamed it to TWRP.img).
2. Open a command window. Make sure you either move the file to the directory it opens to, or navigate to the folder it's in.
3. Put your phone into fastboot by shutting it down, then powering on while holding the volume up button. It should say FASTBOOT on the screen.
4. Plug phone into computer.
5. Run the command "fastboot flash recovery [TWRP.img]" where [TWRP.img] is whatever your file name is.
6. Reboot into recovery to test it!
Part 3: (Optional) Rooting your phone with Magisk
1. Download the Magisk Manager APK from Here. Only grab it from here, I don't think the PlayStore one is legitimate.
2. Open Magisk Manager, and hit install. It should prompt you to download Magisk 16. Hit install in the popup. Let it download.
3. Reboot into TWRP. Hit install, and navigate to the file (should be something like InternalStorage/MagiskManager/Magisk-v16.zip). Install it. Before rebooting, I recommend wiping Dalvik/Art and Cache.
4. Open Magisk Manager to check if it's installed. Enjoy root!
Hope this helps someone out there. With the infrequent, non-OTA updates, I have to remember how to do this every time I update. It's easier to have it written down for reference.
Click to expand...
Click to collapse
It's better to use everytime the latest stock recovery from the latest firmware. You can find it here: https://www.asus.com/zentalk/tw/thread-185884-1-1.html?_ga=1.231834332.2123005859.1491423435
5.15.44.2562 version is the latest available from android file host, but it's not the latest recovery.
I also suggest the latest twrp which is the 3.2.1-0 version now and is compatible with oreo
Chaosruler said:
Awesome guide!
I think its worth to mention that Win10 is not a must, you can use any Windows from XP forwards as long as you install the android adb driver and software, you can also use Linux (most package managers handles symlink to adb) as well as Mac....
Click to expand...
Click to collapse
You're right about that. I've updated my post to reflect it.
Chaosruler said:
Also the adjustment done between the snapdragon 820 and snapdragon 821 version is not just around the update file downloaded but it's super important to make sure to not do that mistake, not all recoveries handle checking and if you flash the wrong file you might brick your device, even though its likely you could fastboot your fw slowly, youd lose all your data, so its better to back up your data on your sd card
Click to expand...
Click to collapse
This 100%. I think that it's important to backup any data that isn't already backed up. I can only hope that those who do have to go through this update process (as opposed to OTA updates) are careful with which versions they install.
Ryder. said:
It's better to use everytime the latest stock recovery from the latest firmware. You can find it here: https://www.asus.com/zentalk/tw/thread-185884-1-1.html?_ga=1.231834332.2123005859.1491423435
5.15.44.2562 version is the latest available from android file host, but it's not the latest recovery.
I also suggest the latest twrp which is the 3.2.1-0 version now and is compatible with oreo
Click to expand...
Click to collapse
Thanks, didn't realize there were updates for either. I've updated the post I made to reflect both changes. In regards to the Zentalk forum, I kept getting asked to login, so that's why I opted to use the AndroidFileHost link instead. I think it may have been because I was on mobile at the time. In any case, I dodn't have to login when viewing the forum on my laptop (might be adblocker?). Even though the older stock recovery worked fine for me, I think others should use the updated stock recovery to avoid any issues.
I didn't check the Mega for the updated TWRP. Didn't really expect it to be updated since we don't have Oreo yet, but it's nice to see that it's been made available. I've updated my own recovery to 3.2.1 and it's working fine.
indiana99 said:
This the response I get from ASUS's website:
An error occurred while processing your request.
Reference #132.563d717.1520889776.1930fb2f
Click to expand...
Click to collapse
Are you still having issues getting the update file? I can upload it if their website is still giving you issues.
asianflipboy said:
You're right about that. I've updated my post to reflect it.
This 100%. I think that it's important to backup any data that isn't already backed up. I can only hope that those who do have to go through this update process (as opposed to OTA updates) are careful with which versions they install.
Thanks, didn't realize there were updates for either. I've updated the post I made to reflect both changes. In regards to the Zentalk forum, I kept getting asked to login, so that's why I opted to use the AndroidFileHost link instead. I think it may have been because I was on mobile at the time. In any case, I dodn't have to login when viewing the forum on my laptop (might be adblocker?). Even though the older stock recovery worked fine for me, I think others should use the updated stock recovery to avoid any issues.
I didn't check the Mega for the updated TWRP. Didn't really expect it to be updated since we don't have Oreo yet, but it's nice to see that it's been made available. I've updated my own recovery to 3.2.1 and it's working fine.
Are you still having issues getting the update file? I can upload it if their website is still giving you issues.
Click to expand...
Click to collapse
I think it might be worth to upload recoveries to xda for ZFdeluxe including TWRP
asianflipboy said:
Are you still having issues getting the update file? I can upload it if their website is still giving you issues.
Click to expand...
Click to collapse
No. Thank you very much for asking. I downloaded from a different location.
indiana99 said:
No. Thank you very much for asking. I downloaded from a different location.
Click to expand...
Click to collapse
Good to hear.
Chaosruler said:
I think it might be worth to upload recoveries to xda for ZFdeluxe including TWRP
Click to expand...
Click to collapse
Hmm, I think I'll do that. I'll make some small zip files for each.
---------- Post added at 09:56 PM ---------- Previous post was at 09:16 PM ----------
indiana99 said:
No. Thank you very much for asking. I downloaded from a different location.
Click to expand...
Click to collapse
Chaosruler said:
I think it might be worth to upload recoveries to xda for ZFdeluxe including TWRP
Click to expand...
Click to collapse
Ryder. said:
5.15.44.2562 version is the latest available from android file host, but it's not the latest recovery.
Click to expand...
Click to collapse
Sorry for re-quoting all of you, but do you guys see the update anymore? It might have been why /u/indiana99 couldn't find it. I went to check while making the zip packs and it's not there... Maybe there was some issue with the build? It's got me a bit shook that it's suddenly not on the website.
Link for WW-5.17.44.87 (newest firmware) for the 821 variant (sorry 820 variant, I didn't download what's not mine)
https://drive.google.com/open?id=1XkqFVIMzyGnUxHIf5btu1uoyjTRxah1C
if anyone happened to did download the 820 variant, please share?
Chaosruler said:
Link for WW-5.17.44.87 (newest firmware) for the 821 variant (sorry 820 variant, I didn't download what's not mine)
https://drive.google.com/open?id=1XkqFVIMzyGnUxHIf5btu1uoyjTRxah1C
if anyone happened to did download the 820 variant, please share?
Click to expand...
Click to collapse
Sorry. I misread the OP. I am unable to locate WW-5.17.44.87 for the 820 variant. I would appreciate someone sharing.
Chaosruler said:
if anyone happened to did download the 820 variant, please share?
Click to expand...
Click to collapse
indiana99 said:
Sorry. I misread the OP. I am unable to locate WW-5.17.44.87 for the 820 variant. I would appreciate someone sharing.
Click to expand...
Click to collapse
That's weird to me though. I just checked again and both variants are missing the current update, 5.17.44.87. Did they pull it for some reason? As far as I can tell, my phone is behaving pretty normally. Anyone that's updated notice anything weird?
I've removed the link. This article claims that we're finally getting the update by the end of March!
https://www.phonearena.com/news/Asu...-ZenFone-3-Deluxe-receive-Oreo-March_id103395
Finally!