Related
I see many people having issues that are new to this kind of thing and here is a fairly simple troubleshooting guide that I have compiled that I think will help many of you get through rooting, Installing the Market, and installing twrp with no problems. This is a complete video walk through for those of you find the videos easier. I recommend that you watch the videos thoroughly before attempting this so that you can be sure that you make no mistakes…!!!
• Start off with a stock Kindle on original 6.2.1fw
• Go to this link for a video walkthrough to root the Kindle with Jcase’s Burrito root. All of the links are in the description of this video to do so. http://www.youtube.com/watch?feature=player_embedded&v=KapnjR89ICA
• Now to install the android Market this is another video walkthrough that is from the same person once again all of the links are in the video description for downloading what it is that you need to perform this action http://www.youtube.com/watch?featur...tion_598718&src_vid=KapnjR89ICA&v=rTkegVrnAvA
• Now to install a custom recovery (aka twrp2.0) this is also another video walkthrough also made from the same individual. Once again all of the files needed are in the video description http://www.youtube.com/watch?annota...&src_vid=KapnjR89ICA&feature=iv&v=JqKZLMaRSgc
• I have noticed that some people have problems getting stuck around 2:32 into the video where twrp is downloading and getting ready to install. If this happens to you and it is constantly “waiting for device” You may need to hit disconnect on your KF and run burrito root on your Kindle again, click “agree”,then click “You Rock”, Then click “root”. Once you do so you must re-open adb shell by opening a command prompt and typing the following:
cd c:\KindleADB to get into adb shell
adb devices to make sure your kindle is connected properly
adb root to get proper permissions
• Once you have done this re-open the run bat in KFU v0.9.1 and select option 5 again and it will install the twrp with proper root permissions.
• I have also noticed that some people also get stuck at 3:55 in this video at the firefire triangle. The fix for this is fairly easy and is explained in the video if you need a walkthrough step by step for doing this (Updating the drivers)here you go:
- Go to start Menu and right click on computer, Click manage
- In computer Management hit device manager
- I am guessing that you see your kindle connected in there with a yellow ! by it
- Right click on kindle and update driver software
- Click Browse my computer for driver software
- Click let me pick from the list of device drivers on my comp
- Click Next
- Click Have Disk
- Click Browse
- Navigate to your user folder in that window/ or wherever your .android folder is
- Double click on .android folder
- Double click on Driver Folder
- Now Click open
- Now click ok
- Click Next
- ClickInstall driver software anyway
• If you also need a link for installing cm7 here is another video to do so also by the same individual. I do not recommend this as of yet until all of the bugs are worked out in this as I have heard many people have had problems with video playback or sound (mainly in ics) and usually end up flashing back to a custom rom anyway. It is your device though so it is completely up to you
http://www.youtube.com/watch?featur...tion_828059&v=L-zTJWY3CRc&src_vid=JqKZLMaRSgc
UPDATE JANUARY 3rd 2012
• Here is a link for a newer rom install called MIUI. This Rom is very smooth and the only thing confirmed not working at the moment (January 2, 2012 is video playback. There are however some individuals working on this issue and will hopefully have video working soon. Thanks to leeech for the MIUI port and nat3mil for the video. Here is the link for the easy to follow video tutorial.
http://www.youtube.com/watch?feature=endscreen&v=OqiX-If5w_4&NR=1
• Here is link on how to resize your internal storage (aka custom partitioning). This is called FireParted made by eldarerathis. This is good for those of you that think that they have too much storage in one place and not enough in another. Playing with partitions can cause you to lose data that is not backed up previously to editing partitions, so use at your own risk. I myself am going to use this to expand the storage on my sd card. Here is the easy to follow video tutorial.
http://www.youtube.com/watch?v=Bkff-bI-FrY
Big thanks for every one of these videos, made by nat3mil. So be sure to thank him and subscribe to his channel for all the latest easy to follow videos!
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update January 7th 2012 This is a program to fix boot loop Problems easily (For Windows Only)
I noticed that many people are still having problems with getting stuck in a recovery boot loop, firefirefire boot loop (Yellow Triangle), Or even the kindle fire boot loop. This is a program to fix it automatically like the kindle fire Utility. I believe that it was made by Zombiepiratez, and he made this to change all of the headaches that many people are having with bootloop problems, proper file permission problems, and bricking problems, so be sure to thank him if this helps you. Once again this is a batch file made only for windows so for those of you that are not on windows, I will leave the common manual fixes below. Here is the link to his thread and download for the Fire Utility Unbrick:
http://forum.xda-developers.com/showthread.php?t=1428428
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I have also heard of the problem with some people getting caught in a boot loop and see a constant Kindle Fire boot screen. To fix this you must open up your cmd and type:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Also for people getting caught in a recovery boot (whenever they turn on their kindle they boot into recovery without hitting the power button do this in your cmd:
adb shell
su
idme bootmode 4000
reboot
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I hope that this clears up a lot of confusion for some of you weary of trying to do this to your kindle fire. I did all of this manually with my first Kindle. I have also used this method to be sure that it works and any problems that might come about when using this method and I have confirmed this to be successful. I really wanted to post this guide because I know that it is easier for some of you people new to this to follow along with a video. I know that some people say well there are a lot of tutorials out there but not one with a step by step and video links for a walk-through to do this whole procedure. If a mod could please sticky this I am sure that many would be greatful!!!
Remember that there is a thanks button…
DO not forget those who made this all possible:
Thanks to Jcase for Burrito Root & Vashypooh For KFU v.0.9.1 I would recommend that any of you that enjoy this and would like to see more mods such as these come out, to donate to these devs..
Thanks for the post. Really helped me out. Now that I have twrp 2.0 installed...
1.) how do I make a back up file (in case something happens when i try to flash a rom) so i can restore and recover to where i am at now
2.) once i do make a back up file, where is it saved and how would i access it, if i wanted to recover and restore.
3.) when i rooted my phone and flashed a new rom i had to use titanium back up to save all my apps and information. if i wanted to flash cm7, do i need to install titanium back up and do the same thing as i did on my phone or is the sd card untouched during the flashing process and all apps will remain?
Thanks
I was worried about doing this but now that I read your guide and seen the videos I am going to give this a try when I get settled in. Thank You!
I got a question as well
After installing the twrp2.0, what will happen to my Kindle? Does that mean the device is already rooted and good to go?
If I don't install the cm7, what can I do with the rooted KF?
You have to root the kindle before you can install the TWRP. the twrp 2.0 is used when you want to flash a rom and a few other things, (i think) you wont be able to install the twrp with out rooting first
babbabooey97 said:
Thanks for the post. Really helped me out. Now that I have twrp 2.0 installed...
1.) how do I make a back up file (in case something happens when i try to flash a rom) so i can restore and recover to where i am at now
2.) once i do make a back up file, where is it saved and how would i access it, if i wanted to recover and restore.
3.) when i rooted my phone and flashed a new rom i had to use titanium back up to save all my apps and information. if i wanted to flash cm7, do i need to install titanium back up and do the same thing as i did on my phone or is the sd card untouched during the flashing process and all apps will remain?
Thanks
Click to expand...
Click to collapse
I do believe that how to make a backup is on the install twrp2.0 video (the third one). I do not believe that you will have to install titanium backup like you do on your phone. I also do not believe that the sd card gets touched in the flashing process...
zwanzig said:
I got a question as well
After installing the twrp2.0, what will happen to my Kindle? Does that mean the device is already rooted and good to go?
If I don't install the cm7, what can I do with the rooted KF?
Click to expand...
Click to collapse
If you follow this guide in the order which was given everything will work out great after the first video your kindle will be Rooted. Twrp is really for creating a backup of your kindle in the current state and flashing different roms such as cm7 or ics... There are many things that you can do with a rooted Kindle really too many to name. You can run different market for starters which will give you more of a selection than what amazon has to offer. I did not mean to sound as if cm7 is not a good thing to use it is just not as stable as it could be and ics is still in the process of being worked on. I will be flashing to a different rom myself such as cm7 or cm9 or ics once they are stable with little or no bugs...
Awesome! Thanks again. I should be all set. one last question and I promise I am done bugging. if you install cm7 rom will you still get OTA updates that amazon sends out. I know on the most recent OTA update, it unrooted the kindle. As of now i am just rooted with go launcher running and i dont feel like trying to reroot if another update comes out. so if i flash to cm7 will i still receive these updates? I know this is the wrong thread for this but just thought you might know.
Thanks again for your help.. definite sticky
babbabooey97 said:
Awesome! Thanks again. I should be all set. one last question and I promise I am done bugging. if you install cm7 rom will you still get OTA updates that amazon sends out. I know on the most recent OTA update, it unrooted the kindle. As of now i am just rooted with go launcher running and i dont feel like trying to reroot if another update comes out. so if i flash to cm7 will i still receive these updates? I know this is the wrong thread for this but just thought you might know.
Thanks again for your help.. definite sticky
Click to expand...
Click to collapse
From what I understand if you are on a different rom such as cm7 you will not recieve a ota update, i could be wrong so do not quote me on that. I have however heard of people installing a modified 6.2.1 update that will help them update from the old fw to the previous one, so for them to have not gotten the update they must have either been using cm7 or turned their wifi off completely until they found a sure fix. Do a little searching on older threads you might find something when you do post back to this thread but make sure that you are sure that it does work as I would not like to have any mis-information in this thread... Thanks
[-_-] said:
From what I understand..... I would not like to have any mis-information in this thread... Thanks
Click to expand...
Click to collapse
Edited the quote for my own amusement.
What all do you use your KF for? I use mine while at work to keep from lugging my Mac around. Also for the occasional updates (socialnetworking=SN) and emailing.
Another question I would like to know is the types of differences there are when running alternatives in the ROM Dept.....fluid transitions, non changing wallpapers, and the like?
Can't give you a thanks yet because of low post count, but this is exactly the sort of thing someone needed to do.
I got home at 8:00 this morning and took a nap. I could not even sleep because I was so anxious to do this to my Kindle Fire, so I decided to get up from 2 hours of sleep in the last 48 hours and give this a shot. This was by far the best guide that I have seen to rooting the Kindle and I pulled it all off flawlessly. Thank you so much for posting this. I did have a few issues when trying to download the recovery file through Kindle Fire Utility, but I followed the guide to a tee and it worked for me perfectly!
I would thank you but I do not have enough posts to do so I hope that this thread gets pinned just in case I have some friends that need a sure fire way to do what I am about to show off to them.
Got my Kindle Fire Stuck in a bootloop.
This thread helped me a lot, now it's fixed!
Thanks a lot!
guides and explanations
Its good to see your hints, because all those really awsome videos have their traps and you can easily get trapped on it, as i did and i had a hard time to find the right way.
My secret for this is to fully understand why you have to do this and that, and here all the guides lack, because there is no explanation WHY you have to do this.
This needs more love. I was successful, because i know from my old background how a chmod works, why i had to install the drivers again and so on but it really took me a while to get this all done, because i didnt read this thread in time.
I also understand that developers are excited about their custom roms and the cyanogenMod, but really who wants to have a kindle fire without sound and a mod with so many bugs ?
I am so happy to have my kindle fire rerooted again after the latest update without opening it or using a special cable.
So this all works quite well, but the guides really need some more explanations to get a deeper understanding about what we are doing here.
I am still working on that, to learn the details.
I want to say a big thank you to all who invested their free time and to spread the knowledge about this awsome device and make the kindle fire a really usefull tablet.
Please keep on the good work ! And have fun with a fully rooted device. There are so many possibilities now !
JoshuaLintag said:
Got my Kindle Fire Stuck in a bootloop.
This thread helped me a lot, now it's fixed!
Thanks a lot!
Click to expand...
Click to collapse
You are very welcome I am glad to see that this guide helped you to get this accomplished!
Don't forget to give a big thanks to Jcase for Burrito Root and Vashypooh for Kindle Fire Utility!
BeerRunJoe said:
I got home at 8:00 this morning and took a nap. I could not even sleep because I was so anxious to do this to my Kindle Fire, so I decided to get up from 2 hours of sleep in the last 48 hours and give this a shot. This was by far the best guide that I have seen to rooting the Kindle and I pulled it all off flawlessly. Thank you so much for posting this. I did have a few issues when trying to download the recovery file through Kindle Fire Utility, but I followed the guide to a tee and it worked for me perfectly!
I would thank you but I do not have enough posts to do so I hope that this thread gets pinned just in case I have some friends that need a sure fire way to do what I am about to show off to them.
Click to expand...
Click to collapse
I am glad to see that you got through this flawlessly. This thread was made just for that very reason to help the lesser experienced user with any issues they might encounter without having to post threads that may get lost in all of the other "Help Me" threads...
If there is a mod that could please sticky this thread I do believe this will answer many questions for individuals and help new users pull off a flawless root, recovery, etc...
+1 on stickying this thread. I have just been pointing people having the same basic problems here. This thread (especially the OP) seems to be helping a lot of people who need help "filling in the blanks".
Good job [-_-]!
I have also directed many of my friends to this thread and they have also gotten through their minor problems. It is kind of funny because a lot of my friends tell me I think my kindle is bricked I just laugh say I doubt it and send them here. Can you also make a guide about going from cm7 back to a the amazon rom please. I put cm7 on my kindle and did not like it so I flashed badk and hit reboot and now I just keep booting up in recovery is there a way to get out of that?
BeerRunJoe said:
I put cm7 on my kindle and did not like it so I flashed badk and hit reboot and now I just keep booting up in recovery is there a way to get out of that?
Click to expand...
Click to collapse
Yes this will work...
1.Plug in USB cable to Kindle Fire on TWRP Recovery mode.
2.Bring up Command Prompt.
3.Key in adb shell.
4.Key in idme bootmode 4000.
5.Finally, key in reboot.
There you go..!!!
Great tutorial setup. Rooted, installed Android Market as mentioned without any issues. Have not installed the Recovery yet though.
Thanks for this thread.
Okay,I've read everything on this topic. I've tried almost everything (except using the factory cable). If you can help me fix this I will paypal you (or the charity of your choice) the $25 dollars I would've spent on a factory cable.
I just want to know if I'm missing anything before I try and make or buy a cable.
My Problem:
I rooted my Kindle fire 6.3 using KFU, everything went flawlessly
(This is when I should've stopped, enjoyed my new root, and be problem free...but I didn't)
I saw a thread for the CM9 Reloaded Rom and thought "Hey I should push my luck and install this rom immediately!"
so with KFU I installed TWRP and then from there all hell broke loose
and by all hell I mean that I got stuck in TWRP recovery and couldn't boot my device normally
blah blah blah, I tried everything and somewhere along the way wiped everything from my kindle, I dont know why or how but it happened
The only thing I can do now is boot into twrp recovery. I've tried literally everything but if there's anyways you can fix this I will paypal you the $25 I would've spent on the factory cable.
I will be on this forum all day seeing as it's sunday and I am ready and willing to answer any and all questions about my predicament to further clarify the issue.
THANKS!!
p.s.
This isn't a knock against ReloadedRom or TWRP, I understand people have worked hard on them and I really appreciate all the devs do around here. this is simply an IBM (Idiot Behind Machine) problem!
gdr425 said:
Okay,I've read everything on this topic. I've tried almost everything (except using the factory cable). If you can help me fix this I will paypal you (or the charity of your choice) the $25 dollars I would've spent on a factory cable.
I just want to know if I'm missing anything before I try and make or buy a cable.
My Problem:
I rooted my Kindle fire 6.3 using KFU, everything went flawlessly
(This is when I should've stopped, enjoyed my new root, and be problem free...but I didn't)
I saw a thread for the CM9 Reloaded Rom and thought "Hey I should push my luck and install this rom immediately!"
so with KFU I installed TWRP and then from there all hell broke loose
and by all hell I mean that I got stuck in TWRP recovery and couldn't boot my device normally
blah blah blah, I tried everything and somewhere along the way wiped everything from my kindle, I dont know why or how but it happened
The only thing I can do now is boot into twrp recovery. I've tried literally everything but if there's anyways you can fix this I will paypal you the $25 I would've spent on the factory cable.
I will be on this forum all day seeing as it's sunday and I am ready and willing to answer any and all questions about my predicament to further clarify the issue.
THANKS!!
p.s.
This isn't a knock against ReloadedRom or TWRP, I understand people have worked hard on them and I really appreciate all the devs do around here. this is simply an IBM (Idiot Behind Machine) problem!
Click to expand...
Click to collapse
If you know how to use fast boot try this command:
fastboot -i 0x1949 oem idme bootmode 4000
That should get you out of the twrp loop.
Sent from my Amazon Kindle Fire using XDA
gdr425 said:
Okay,I've read everything on this topic. I've tried almost everything (except using the factory cable). If you can help me fix this I will paypal you (or the charity of your choice) the $25 dollars I would've spent on a factory cable.
I just want to know if I'm missing anything before I try and make or buy a cable.
My Problem:
I rooted my Kindle fire 6.3 using KFU, everything went flawlessly
(This is when I should've stopped, enjoyed my new root, and be problem free...but I didn't)
I saw a thread for the CM9 Reloaded Rom and thought "Hey I should push my luck and install this rom immediately!"
so with KFU I installed TWRP and then from there all hell broke loose
and by all hell I mean that I got stuck in TWRP recovery and couldn't boot my device normally
blah blah blah, I tried everything and somewhere along the way wiped everything from my kindle, I dont know why or how but it happened
The only thing I can do now is boot into twrp recovery. I've tried literally everything but if there's anyways you can fix this I will paypal you the $25 I would've spent on the factory cable.
I will be on this forum all day seeing as it's sunday and I am ready and willing to answer any and all questions about my predicament to further clarify the issue.
THANKS!!
p.s.
This isn't a knock against ReloadedRom or TWRP, I understand people have worked hard on them and I really appreciate all the devs do around here. this is simply an IBM (Idiot Behind Machine) problem!
Click to expand...
Click to collapse
I'll help you if you'll spend the money on a factory cable anyway so you can get out of your next situation.
Read this post and make sure your drivers are in order.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
You'll have to get that done first before anything else. If you are completely lost, reading the first post in that thread wouldn't be a bad idea either.
Basically, you have to set the bootmode back to normal using either adb or fastboot... but like I mentioned before, you have to make sure your drivers are working and recognizing your KF.
kinfauns said:
I'll help you if you'll spend the money on a factory cable anyway so you can get out of your next situation.
Read this post and make sure your drivers are in order.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
You'll have to get that done first before anything else. If you are completely lost, reading the first post in that thread wouldn't be a bad idea either.
Basically, you have to set the bootmode back to normal using either adb or fastboot... but like I mentioned before, you have to make sure your drivers are working and recognizing your KF.
Click to expand...
Click to collapse
I'm sorry for asking noob like questions
I swear i've had an android phone rooted and all that for over 2 years...anyways
what do you mean "recognizing your KF"
It shows up in my list of devices when I plug it in
gdr425 said:
I'm sorry for asking noob like questions
I swear i've had an android phone rooted and all that for over 2 years...anyways
what do you mean "recognizing your KF"
It shows up in my list of devices when I plug it in
Click to expand...
Click to collapse
Just having it show up isn't good enough. With TWRP open... you need to have it show up exactly as "Android Phone -> Android Composite ADB Interface" and "Composite" must be in there.
If it does that... Go to your Kindle Fire Utility folder, open the tools folder inside there. Once you have that open, shift-right-click inside the folder and select "Open command window here" to get to the command line. Then inside that enter these two commands... one after the other....
Code:
adb shell idme bootmode 4000
adb reboot
Your KF should restart back into a normal boot and get you to your system.
EDIT: I guess I should mention that the "shift-right-click" inside a folder works in Windows 7, but I'm not sure that it does in previous versions.
When I did that, it reboots, shows the yellow triangle telling me to press the power button to enter recovery, if i press i get to twrp if i don't it just shuts off with the amber power button on
I think i may have to manually install the drivers?
gdr425 said:
When I did that, it reboots, shows the yellow triangle telling me to press the power button to enter recovery, if i press i get to twrp if i don't it just shuts off with the amber power button on
I think i may have to manually install the drivers?
Click to expand...
Click to collapse
If it's able to reboot with the "adb reboot" command, I'm guessing your drivers are working fine, but just to verify... What device is shown in the device manager when you have it booted into TWRP?
It's possible that you have a broken ROM flashed onto your device right now and it can't complete a normal boot. You might want to try flashing a new ROM...
If it's rebooting after issuing the commands, then you shouldn't have to press the power button once the yellow triangle comes up. Just give it a few seconds to get past that part and to the KF screen.
I was having the same issues yesterday after flashing, but resolved once I realized I could issue the commands.
if I dont press the power button it just shuts down, I actually figured out a fix for this brick that worked for me I'll post it in a thread today because i've seen a lot of people having the same problem without much success, THANKS to EVERYONE who helped me with this!
http://forum.xda-developers.com/showthread.php?t=1576675
should take care of your problem
Hello, so this is my first time trying to root an android device, and I think I messed up. I watched a tutorial on youtube on how to do it and successfully installed superuser and twrp from a batch file ( I had to install adb drivers first ). I wasn't really sure I did it in the correct steps, so I wanted to revert back to the stock os. I booted into twrp and wiped the data ( cache, system, etc) from twrp. I then mounted it and transfered the kindle fire update 6.3.1 to my KF. I used the option on twrp to revert back to stock using the newly transferred zip. It ran for awhile then prompted me to click reboot. So I did. And this is where it gets tricky
After the reboot, all I see is the boot screen displaying "kindle fire." It never booted and lasted like this for hours. I tried to boot into twrp but I think it got deleted. I googled the problem and found it was in some sort of fastboot loop. I tried many fixes, using adb and other fastboot commands. Every time I tried anything, all I got was "waiting for device." Also, I couldn't use adb shell because it said system/bin/sh was not found. I went to my computer and found that the kindle fire no longer showed up as a removable device, but it showed up in device manager as adb composite interface under android phone. I thought that somehow all of my system files got deleted and thats why it says system/bin/sh not found. I tried to use the adb push command to manually send the update.zip to the KF but it is no longer a mounted drive, so there is nowhere to send it to. I'm at a loss here, Ive tried numerous utilities such as KFU, firekit, unbrick utility. I just need to figure out a way to remount the KF and copy over the folder "system" in the update.zip. If anyone could help me that would be great, as I have been trying to fix this for three days now.:fingers-crossed:
Read the How To in the attached link and it should help you figure out what the problem is and get you unbricked, http://forum.xda-developers.com/showthread.php?t=1552547.
tazmanhawaii said:
Read the How To in the attached link and it should help you figure out what the problem is and get you unbricked, http://forum.xda-developers.com/showthread.php?t=1552547.
Click to expand...
Click to collapse
That doesn't really help me at all, as I have tried the solutions that what you just posted provides, and none of them have worked. I have tried flashing firefirefire and twrp to the kindle fire using fastboot, but to no avail. I think I need a bit more help than a beginner's guide can provide, but thanks for the link.
Marblesnake said:
That doesn't really help me at all, as I have tried the solutions that what you just posted provides, and none of them have worked. I have tried flashing firefirefire and twrp to the kindle fire using fastboot, but to no avail. I think I need a bit more help than a beginner's guide can provide, but thanks for the link.
Click to expand...
Click to collapse
First of all, when you try to revert to stock without wiping the necessary partitions, bad things will happen. What usually happens is you end up with some sort of frankenROM with no working shell and no custom bootloader or recovery.
Based on your description, it seems like you aren't in fastboot at all. You can confirm this by paying attention to the boot screen at the device starts up. If you see a bright Kindle Fire logo that stays bright, you're in fastboot. If you see a bright Kindle Fire logo that dims a little after a few seconds, you're no longer in fastboot and the device is trying to boot normally. What usually happens in situations like yours is, not only does the system have no way of booting, but there is also no working shell to send the necessary commands to change the bootmode, and you will receive the typical "system/bin/sh not found" error.
The problem is without a working shell, you cannot get into fastboot to install custom recovery and you cannot install recovery while booted "normally" without a working shell.
You have two options:
* Acquire a factory cable. A Motorola style factory programming cable to be exact. You can purchase one, or make one yourself. There is a thread in the KF General forum with information regarding both. The factory cable will put the device in fastboot so you will be able to install custom recovery and repair your system.
or
* Use Firekit. But in order for Firekit to work properly in your situation, you need to put the device in USBboot to install a "new" bootloader and recovery. This consists of opening the device and using the "shorting trick" as described in the Firekit thread. I would suggest creating a liveUSB with "persistence" and install the SoupKit. SoupKit comes with Firekit along with a number of other tools you may find useful.
Either way, you need to get custom recovery installed so you can wipe your system and data (factory reset) partitions and flash a new ROM. If it's the stock ROM you want, MoDaCo is your best bet. Once you install a custom ROM, there is no need to "root" as all custom ROMs come pre-rooted.
Hope that helps.
soupmagnet said:
First of all, when you try to revert to stock without wiping the necessary partitions, bad things will happen. What usually happens is you end up with some sort of frankenROM with no working shell and no custom bootloader or recovery.
Based on your description, it seems like you aren't in fastboot at all. You can confirm this by paying attention to the boot screen at the device starts up. If you see a bright Kindle Fire logo that stays bright, you're in fastboot. If you see a bright Kindle Fire logo that dims a little after a few seconds, you're no longer in fastboot and the device is trying to boot normally. What usually happens in situations like yours is, not only does the system have no way of booting, but there is also no working shell to send the necessary commands to change the bootmode, and you will receive the typical "system/bin/sh not found" error.
The problem is without a working shell, you cannot get into fastboot to install custom recovery and you cannot install recovery while booted "normally" without a working shell.
You have two options:
* Acquire a factory cable. A Motorola style factory programming cable to be exact. You can purchase one, or make one yourself. There is a thread in the KF General forum with information regarding both. The factory cable will put the device in fastboot so you will be able to install custom recovery and repair your system.
or
* Use Firekit. But in order for Firekit to work properly in your situation, you need to put the device in USBboot to install a "new" bootloader and recovery. This consists of opening the device and using the "shorting trick" as described in the Firekit thread. I would suggest creating a liveUSB with "persistence" and install the SoupKit. SoupKit comes with Firekit along with a number of other tools you may find useful.
Either way, you need to get custom recovery installed so you can wipe your system and data (factory reset) partitions and flash a new ROM. If it's the stock ROM you want, MoDaCo is your best bet. Once you install a custom ROM, there is no need to "root" as all custom ROMs come pre-rooted.
Hope that helps.
Click to expand...
Click to collapse
Thanks for the help. Yeah, I tried the firekit method but didn't use the shorting trick. I have scoured the internet for information and tricks and it seems like these are my last two options before I throw this thing out the window. I have seen your posts in other threads and you have been a great help throughout this ordeal.
factory cable
thank you for this information. I am in the same predicament. I am purchasing a factory cable from Amazon $1.27.
It is sold by Earlybirdsavings and is a 3ft micro USB factory cable for kindle fire and Motorola Xoom.
thank you for all the helpful information!
ive been seeing enough and more posts asking about flashing OxygenOS. I'll try and explain in simple terms. read carefully and only then try it.
I TAKE NO RESPONSIBILITY IF YOU SPOIL YOUR DEVICES. YOU ARE DOING THIS AT YOUR OWN RISK!
if you have a custom recovery skip to step 7
1. Your devices needs a custom recovery. to install one you need to be rooted. to root u need an unlocked bootloader. OnePlus claims that you wont loose warranty on rooting and unlocking so your safe there unless u do something wrong. so be cautious.
2.for unlocking rooting and flashing i recommend using Bacon Root Toolkit. even though i know to do it the Oldschool way. this is much more simple and u really cant go wrong with the toolkit its NoobFriendly. download the toolkit from the following link and install it along with the drivers. http://www.wugfresh.com/brt/
3. once installed choose the version of CM you are running. the toolkit will automatically download all required files. once in u will have to set up the drivers. the instructions for that are well explained in the toolkit please follow it there.
4. after the drivers are set up first u need to unlock. REMEMBER UNLOCKING WILL CLEAR ALL DATA!. so backup all required data.for the internal SD card u can connect the phone to the computer as an MTP device and copydata, for the apps you can backup using Helium and copy the helium folder to the computer. please do not post comments telling that you lost all data there is NO WAY to recover that data once you unlock.
5.press UNLOCK in the toolkit, it will guide you through the process. after unlock when you switch on the phone itll be as good as new you will have to go through the procedure of logging into google etc. once done head over to settings enable developer options and tick ADB. DONT FORGET TO DO THIS
6. Now you need to root your device. by default the toolkit uses SUPERSU to root and TWRP as custom recovery its perfectly fine unless you intend on changing it later on stick to these two. remember to tick CUSTOM RECOVERY under the root option. press root and follow the steps. it pretty much does everything u jut have to keep confirming.
7. Hoping that right now your rooted and have a custom recovery, if not please go through the previous steps.
now we need to download the oxygenOS head over to the forum and download or use this link https://oneplus.net/oxygenos, once downloaded check the size it should be 705MB incase its not the download again may be the download got corrupted.
8. IMPORTANT STEP FOR NEWBIES
once u download u have ONE .zip file named "oxygenos_1.0.0.zip" extract that file and u will get a folder named "oxygenos_1.0.0" leave it there DONT EXTRACT ANY FURTHER!. the folder will contain two files "oxygen_1.0.0_flashable.zip" "oxygen_1.0.0_flashable.md5" leave them as they are. preferably copy this folder containing the two files to the root of the phone. in simple terms put it in your phone memory without putting it into any other folder.
9. Now you have your files ready you need to head over to the recovery. two ways of doing it. you can go to settings developer options and tick advance reboot. now when u press reboot u get an option to reboot recovery and bootloader. choose recovery.
another way of getting to recovery is shut down the phone hold the buttons POWER+VOLUME DOWN once the phone comes on leave the power button and hold VOLUME DOWN till the recovery shows up.
10. Once your in TWRP u have an option to backup your rom. You could do this as a precaution if anything goes wrong u can restore from this backup file. fro backing up press backup and choose the partitions you want to backup and swipe to backup. the backup should be around 2-3gb i think. once backed up copy the file from the TWRP folder on your phone to the computer.
11. since you are changing the ROM completely you need to factory reset once before flashing. in TWRP press WIPE and swipe to factory reset. and go back to home dont reboot device.
12. FLASHING THE ROM: in TWRP press install in the list find the folder oxygenos_1.0.0. in that folder click on the file "oxygen_1.0.0_flashable.zip" and then swipe to flash. the flashing can take a while dont do anything while its in progress.
13.once flashed reboot system. the first reboot will take time let it happen do not get worried and try restarting just let it take its time it has to set up everything for u.
14. Now you should be having OXYGEN OS... use it appreciate it rather than criticizing it. incase u feel like customizing it try out XPOSED. though it is still in testing for L it shouldnt be too buggy. gravityBox is compatible with lollipop.
15. incase you feel like going back to CM.. head over to the toolkit connect the phone (remember to enable ADB) doesnt matter which build u set. press FLASH STOCK+UNROOT choose the CM build you want and let it do its work. follow the instructions.
some may point out that the toolkit has an option to flash the rom as well. yes it does but i wont dive into that now. this method is simple enough. but if u know how to do it that way u sure can
PS: KEEP YOU BATTERY FULLY CHARGED WHILE DOING ALL THIS. INCASE THE PHONE DIES WHILE FLASHING ITLL BE BRICKED.
please correct me if i went wrong anywhere.
hope this helps.
shoaib30 said:
ive been seeing enough and more .....
Click to expand...
Click to collapse
There is absolutely no need for this thread - it's all been covered before. Flashing OOS is no different to any other custom ROM.
You text/formatting is abysmal. You recommend using the toolkit, WTF? This device is the easiest ever created for unlocking/rooting and using a toolkit is a BAD idea as if it goes wrong you will end up confused and not knowing what to do next. Anyone who can't unlock / root / flash TWRP on this device should not be attempting to install a custom ROM anyway.
What you have posted is actually more confusing for a 'noobie' than what is already out there, I'd suggest this thread should probably be deleted and people with questions can simply search and find the useful instructions which already exist.
SimonTS said:
There is absolutely no need for this thread - it's all been covered before. Flashing OOS is no different to any other custom ROM.
You text/formatting is abysmal. You recommend using the toolkit, WTF? This device is the easiest ever created for unlocking/rooting and using a toolkit is a BAD idea as if it goes wrong you will end up confused and not knowing what to do next. Anyone who can't unlock / root / flash TWRP on this device should not be attempting to install a custom ROM anyway.
What you have posted is actually more confusing for a 'noobie' than what is already out there, I'd suggest this thread should probably be deleted and people with questions can simply search and find the useful instructions which already exist.
Click to expand...
Click to collapse
im sorry ill take it off. i had ppl asking me in person so i thought i can explain here and send the link to them. my bad
Please don't create duplicate threads. There are already threads open that cover this topic.
Thread closed.
Hello. I have a few questions on rooting this phone. (My first time rooting)
First off, Is this the same model as the ze550kl (I assume so but not 100% sure). I have attempted to root this phone through the instructions provided in posts on this website for model ze550kl but I must be doing something wrong with the programs ect. I have never rooted a phone and so this is my first try and I would really like a full in detail screenshot follow through if available to do with the programs once downloaded and any other programs you may need on windows 10 to get to where I need to be. I dislike the zenui so much that is my main reason to root the phone is to remove this and other bloatware as well as some of my friends have some apps that are pretty neat that I would like that are only available through root.. I have also tried other methods posted on YouTube but I think I'm doing something wrong on all of my attempts. I would also like to know if there is a way to make a backup of the original files prior to rooting so I can send my phone in because I have a 2 year warantee if something was to happen (dropped, broken, ect.). In relation to the screenshots if there is any files that have to be placed on the phones hard drive from something I download off the internet please state this specifically, I believe that one or 2 ways I have seen required this but it seems vauge and I don't think it was done correctly by me. I am great at following detailed instructions but I don't know what exactly it is I need to do as I have never done this before so if something has to have a specific name please note that.
Thank you for the help.
My ZF2L should be showing up any minute now, so I'll let you know when it gets here. I'm no expert, but I've been rooting my Android devices since 2009. I think I can help you out.
HampTheToker said:
My ZF2L should be showing up any minute now, so I'll let you know when it gets here. I'm no expert, but I've been rooting my Android devices since 2009. I think I can help you out.
Click to expand...
Click to collapse
Thank you, I think I'm just missing an important step. The zenui just isn't my style. Will be nice to be able to remove
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 02:07 PM ---------- Previous post was at 01:28 PM ----------
Yeah, I think you just need more comprehensive instructions. It happens from time to time. From what I can tell so far, it's a pretty straightforward process for those that are familiar with root, but to a beginner it can be a bit much. As soon as mah lazah is dunna chargin' I'll walk you through the steps I took to root it, install custom recovery, and make a backup of your entire system just in case you ever need to restore your phone to a stock-rooted-but otherwise unmodified state. I should have something up in the next couple hours ?
Updated, rooted, and installed custom recovery. I'll post a short write-up shortly.
First off, I'm going to answer your questions since I didn't previously.
Sorvas33 said:
First off, Is this the same model as the ze550kl (I assume so but not 100% sure).
Click to expand...
Click to collapse
No, they're different, but I'm not entirely sure by how much. I'm 100% sure that they're probably maybe 90% or so compatible, but there are differences. I just don't know them without checking. I wouldn't go flashing anything that doesn't explicitly state that it's for the 551 or is compatible or has had a 551 user test and report success. There are some things that are kind of universal (and we'll get into that a little), but for now let's just stick with using caution.
Sorvas33 said:
I would also like to know if there is a way to make a backup of the original files prior to rooting so I can send my phone in because I have a 2 year warantee if something was to happen (dropped, broken, ect.)
Click to expand...
Click to collapse
We'll make a backup using TWRP, but you'll have to be rooted. A TWRP backup (or nandroid backup) is like a snapshot of your current system. You can customize it and only backup certain parts of the system as well as restore certain parts, but I wouldn't worry about that. Most of the time you'll want a complete backup, anyway. But, to answer your question, no, you'll have to be rooted, but you can always unroot from the phone using the Supersu app. If the damage is physical an unrooted backup wouldn't matter anyway.
So, here's my (hopefully) brief write-up to acquire root, install recovery, make a backup, and ,optionally, install the Xposed framework. Before getting started be sure to have plugged your phone into your computer for Windows to download and install drivers for your ZF2L. Also, you will need to download and install adb in order to use command prompt to flash files to your phone. This link will take you to a thread here at XDA for Minimal ADB and Fastboot. This is the easiest way to install and use adb and fastboot on your computer. Once you have it installed you can proceed to the next steps.
First, you'll need to unlock your bootloader using the app found here. It's in a .zip files for whatever reason, so you'll need to use 7zip or WinZip or WinRAR or something on your computer to extract it and install to your phone. You can plug your phone in and place the extracted app on your external or internal storage or use a cloud storage app like Dropbox or Google Drive to transfer it to your phone. If you plug it in and place on your internal or external storage, then you'll need to use File Manager (it's a stock app) to find and install it. Once installed just run the app. It's extremely user friendly and straightforward. Your phone will reboot when it's done.
Next, you'll have to temporarily boot a modified boot.img using Minimal adb and fastboot. Once this step is completed and the phone boots up you'll need to go to the Play Store and install Supersu as well as Busybox if you want your root apps to work properly.
Go here on your computer and download the modified boot.img named boot_200007.img and place it in the Minimal adb and fastboot folder. As you can see in this screenshot:
my adb and fastboot folder is located at C:\Windows\Minimal ADB and Fastboot. Once you have the boot.img copied to the right folder go ahead and connect your phone, if it isn't already. Hold the power button and restart the phone. As soon as the screen goes off hold the volume up button until the phone boots into fastboot mode. If you have trouble with this, you can just turn the phone off, and then press and hold power and volume up until it boots into fastboot mode. Right click the Minimal adb and fastboot icon and select run as administrator. As long as it's installed correctly, the following commands shouldn't give you any error messages. Before we go further, let me briefly explain what we're doing at this point. We have two options: we can flash the boot.img which will physically write it to the proper partition on your phone, or we can simply boot the phone while the modified boot.img remains on your computer and unwritten to the phone, which is what we want to do in this case. To do this we enter the following command:
fastboot boot boot_200007.img
Your phone should reboot on it's own and once it does open the app drawer and check to see if Supersu is installed. If it isn't, open Play and install it, as well as Busybox. Open Supersu and make sure you have root. Once your done, open Busybox and install Busybox to /system/xbin and reboot when finished. At this point, you can disconnect your phone and ensure the Supersu does give you any errors. Test it by installing your favorite root apps, and since you're new to root, I'll give you some suggestions. You can do a google search to find Adaway. It isn't available in the Play Store because it's an adblocker and ads are Google's bread and butter, but it sure is nice to use apps without intrusive apps trying to sell you something no matter where you go. Root + Adaway have been solving that problem for years. Next we have Root Explorer which is my root file manager of choice. Another community favorite is ES File Manager. Both are great. Titanium Backup, Flashify (install it for the next step), and Viper4Android (not in Play search XDA) are all must have apps for root users. Install and open some of those (especially Flashify) just to verify that they work and let's move on the next step.
Download TWRP here and place it on either internal or external storage. Open Flashify and select Recovery Image and then find and select recovery551_200431.img. This will write the TeamWinRecoveryProject custom recovery to the recovery partition of your phone which will allow you to view, backup, restore, and modify all the relevant partitions that make up the Android operation system. At this moment, it's important to understand that you are now more than capable of completely and totally bricking your phone...but you're also capable of recovering from most problems that can arise from flashing mods and using root apps. This is where we'll make a complete backup for just that very reason.
After you've flashed TWRP using Flashify, you'll be prompted to reboot. Do so, and your phone will reboot into recovery. You'll see a message one the first run with a check box to disable modifications to system or something along those lines (can't remember exactly what it says lol), just don't check it. Leave the box uncheck and swipe the bar to allow modifications to system. Now, you should see the main menu. Select Backup and make sure that Boot, System, Data, and Cache are selected and rename the backup to something along the lines of "stock_rooted" or "stock_backup" if you wish and you're ready to create a nandroid backup. Swipe the button and give it a few minutes. Once done, just reboot and you're good to go.
Now to install Xposed, you'll first need to install the Xposed Installer .apk on your phone from here. To flash Xposed, reboot into recovery (turn off then hold power + volume down) and select Install then select the Xposed .zip package xposed-v80-sdk21-arm64.zip that you downloaded and placed on your internal (preferrably) or external storage beforehand. Once finished just reboot and you're done. Be warned that the first boot after installing Xposed will take a long time (approx. 5-10 minutes). Greenify, Gravitybox (LL), Youtube Adaway, Flat Style Bar Indicators, MaxLock, and NotifyClean are just a few of my favorite Xposed modules. Be sure to read the descriptions for these modules carefully and do not forget that Xposed modules can be tricky and cause problems if they're not compatible with your phone. Honestly, you should ask here before installing any modules that I haven't already mentioned.
Anyway, that's my brief write-up lol. Hopefully, that isn't too hard to follow. Don't hesitate to reply back if you encounter a problem, have any questions, or simply want to report your success and ask for tips. I'll leave you with this little tip: don't give up on ZenUI. It definitely doesn't hold a flame to stock Android, but if you use a third party launcher like Nova Launcher and use Developer Options to increase animation speed to .5 seconds (or turn them off entirely) it's really not so horrible, in my opinion. It's damn sure not TouchWiz.
HampTheToker said:
So, here's my (hopefully) brief write-up to acquire root, install recovery, make a backup, and ,optionally, install the Xposed framework. Before getting started be sure to have plugged your phone into your computer for Windows to download and install drivers for your ZF2L. Also, you will need to download and install adb in order to use command prompt to flash files to your phone. This link will take you to a thread here at XDA for Minimal ADB and Fastboot. This is the easiest way to install and use adb and fastboot on your computer. Once you have it installed you can proceed to the next steps.
First, you'll need to unlock your bootloader using the app found here. It's in a .zip files for whatever reason, so you'll need to use 7zip or WinZip or WinRAR or something on your computer to extract it and install to your phone. You can plug your phone in and place the extracted app on your external or internal storage or use a cloud storage app like Dropbox or Google Drive to transfer it to your phone. If you plug it in and place on your internal or external storage, then you'll need to use File Manager (it's a stock app) to find and install it. Once installed just run the app. It's extremely user friendly and straightforward. Your phone will reboot when it's done.
Next, you'll have to temporarily boot a modified boot.img using Minimal adb and fastboot. Once this step is completed and the phone boots up you'll need to go to the Play Store and install Supersu as well as Busybox if you want your root apps to work properly.
Go here on your computer and download the modified boot.img named boot_200007.img and place it in the Minimal adb and fastboot folder. As you can see in this screenshot:
my adb and fastboot folder is located at C:\Windows\Minimal ADB and Fastboot. Once you have the boot.img copied to the right folder go ahead and connect your phone, if it isn't already. Hold the power button and restart the phone. As soon as the screen goes off hold the volume up button until the phone boots into fastboot mode. If you have trouble with this, you can just turn the phone off, and then press and hold power and volume up until it boots into fastboot mode. Right click the Minimal adb and fastboot icon and select run as administrator. As long as it's installed correctly, the following commands shouldn't give you any error messages. Before we go further, let me briefly explain what we're doing at this point. We have two options: we can flash the boot.img which will physically write it to the proper partition on your phone, or we can simply boot the phone while the modified boot.img remains on your computer and unwritten to the phone, which is what we want to do in this case. To do this we enter the following command:
fastboot boot boot_200007.img
Your phone should reboot on it's own and once it does open the app drawer and check to see if Supersu is installed. If it isn't, open Play and install it, as well as Busybox. Open Supersu and make sure you have root. Once your done, open Busybox and install Busybox to /system/xbin and reboot when finished. At this point, you can disconnect your phone and ensure the Supersu does give you any errors. Test it by installing your favorite root apps, and since you're new to root, I'll give you some suggestions. You can do a google search to find Adaway. It isn't available in the Play Store because it's an adblocker and ads are Google's bread and butter, but it sure is nice to use apps without intrusive apps trying to sell you something no matter where you go. Root + Adaway have been solving that problem for years. Next we have Root Explorer which is my root file manager of choice. Another community favorite is ES File Manager. Both are great. Titanium Backup, Flashify (install it for the next step), and Viper4Android (not in Play search XDA) are all must have apps for root users. Install and open some of those (especially Flashify) just to verify that they work and let's move on the next step.
Download TWRP here and place it on either internal or external storage. Open Flashify and select Recovery Image and then find and select recovery551_200431.img. This will write the TeamWinRecoveryProject custom recovery to the recovery partition of your phone which will allow you to view, backup, restore, and modify all the relevant partitions that make up the Android operation system. At this moment, it's important to understand that you are now more than capable of completely and totally bricking your phone...but you're also capable of recovering from most problems that can arise from flashing mods and using root apps. This is where we'll make a complete backup for just that very reason.
After you've flashed TWRP using Flashify, you'll be prompted to reboot. Do so, and your phone will reboot into recovery. You'll see a message one the first run with a check box to disable modifications to system or something along those lines (can't remember exactly what it says lol), just don't check it. Leave the box uncheck and swipe the bar to allow modifications to system. Now, you should see the main menu. Select Backup and make sure that Boot, System, Data, and Cache are selected and rename the backup to something along the lines of "stock_rooted" or "stock_backup" if you wish and you're ready to create a nandroid backup. Swipe the button and give it a few minutes. Once done, just reboot and you're good to go.
Now to install Xposed, you'll first need to install the Xposed Installer .apk on your phone from here. To flash Xposed, reboot into recovery (turn off then hold power + volume down) and select Install then select the Xposed .zip package xposed-v80-sdk21-arm64.zip that you downloaded and placed on your internal (preferrably) or external storage beforehand. Once finished just reboot and you're done. Be warned that the first boot after installing Xposed will take a long time (approx. 5-10 minutes). Greenify, Gravitybox (LL), Youtube Adaway, Flat Style Bar Indicators, MaxLock, and NotifyClean are just a few of my favorite Xposed modules. Be sure to read the descriptions for these modules carefully and do not forget that Xposed modules can be tricky and cause problems if they're not compatible with your phone. Honestly, you should ask here before installing any modules that I haven't already mentioned.
Anyway, that's my brief write-up lol. Hopefully, that isn't too hard to follow. Don't hesitate to reply back if you encounter a problem, have any questions, or simply want to report your success and ask for tips. I'll leave you with this little tip: don't give up on ZenUI. It definitely doesn't hold a flame to stock Android, but if you use a third party launcher like Nova Launcher and use Developer Options to increase animation speed to .5 seconds (or turn them off entirely) it's really not so horrible, in my opinion. It's damn sure not TouchWiz.
Click to expand...
Click to collapse
Thank you man, I will try this when I get a chance (working 14 hour days ATM) but I will let you know how it goes.also what model member do you have. Because the box I have is we're I got my model number. I can't find the one listed on my box in the device itself.
Exact same model...ZE551KL.
In About Phone the model number is ASUS_Z00TD.
HampTheToker said:
Exact same model...ZE551KL.
In About Phone the model number is ASUS_Z00TD.
Click to expand...
Click to collapse
Exactly what I have. Sweet. I'll update you once I'm done. Thank you for your help and assistance. Any app advice? For uninstalling and cleaning hdd/ram. And theme?
Come on, bro...I gotta know if that's friendly enough to get you squared away...
HampTheToker said:
Come on, bro...I gotta know if that's friendly enough to get you squared away...
Click to expand...
Click to collapse
I should have time either tomorrow or next weekend all depending and I'll let you know then. Depends on how much I have to work. I check this post about once to twice a day. Thank you for your effort and time. I really do appreciate it.
Now I do have one more question on my mind. Does the Asus zenfone that we have keep a flash tracker? Meaning that it keeps track if a phone was rooted. The reason I ask is that I have a 2 year warantee and I know that this will "void" it unless I flash it back. But if they have a tracker then I need to make sure there is a way to reset that as well. From what I have read personally it is only Samsung that is keeping track in this way. Thanks for your help Mr.Toker
Yeah, that's mostly a Sammy thing. I'm coming from a Galaxy S4 that's been passed down to my six year old. I'm all too familiar with flash counters and KNOX security. Thankfully, I don't believe Asus has anything like that. That's one of the many reasons I chose this phone over anything Cricket had to offer. I don't care how good the hardware is, if it can't be unlocked and rooted, then I don't want it.
But, to answer your question more directly, no, I don't believe your warranty will be affected.
Also, I'm going to paste this warning from the developer that built TWRP for us.
Warning
Do not try to fix permission, if you do not know exactly what this is ?
Home > Advance > Fixpermission
Click to expand...
Click to collapse
Just figured I'd add that I believe I read unlocking your boot loader voids the warranty. As of right now, I'm pretty sure there's no way to root without unlocking it, and no way to re-lock it after unlocking.
Sent from my ASUS_Z00TD using Tapatalk
CKtheProblem said:
Just figured I'd add that I believe I read unlocking your boot loader voids the warranty. As of right now, I'm pretty sure there's no way to root without unlocking it, and no way to re-lock it after unlocking.
Sent from my ASUS_Z00TD using Tapatalk
Click to expand...
Click to collapse
"oem relock bootloader" should do the trick, but I haven't tried it. Sure, technically unlocking your bootloader and rooting voids your warranty, but it's not like either sends a message to Asus in the background stating that you've voided your warranty. The only way they'd know is if you sent it to them for a claim while still rooted. Even then, if it's bricked, it's bricked. They still won't know. If it's not bricked and it's just hardware, then you should be able to unroot.
Honestly, rooting your device has always been a risk to your warranty, but I've yet to have any issues with it since I started rooting my devices in 2009.
HampTheToker said:
"oem relock bootloader" should do the trick, but I haven't tried it. Sure, technically unlocking your bootloader and rooting voids your warranty, but it's not like either sends a message to Asus in the background stating that you've voided your warranty. The only way they'd know is if you sent it to them for a claim while still rooted. Even then, if it's bricked, it's bricked. They still won't know. If it's not bricked and it's just hardware, then you should be able to unroot.
Honestly, rooting your device has always been a risk to your warranty, but I've yet to have any issues with it since I started rooting my devices in 2009.
Click to expand...
Click to collapse
Yeah you're probably right. Luckily, I've never had to send a phone I rooted back in for repairs so I can't say anything about the process.
Sent from my ASUS_Z00TD using Tapatalk
Thanks for those root/recovery instructions, just got this same phone and model number yesterday and just now found the files needed ! You rock! What roms do you suggest?
tmjm28 said:
Thanks for those root/recovery instructions, just got this same phone and model number yesterday and just now found the files needed ! You rock! What roms do you suggest?
Click to expand...
Click to collapse
at present we have only stock rom, no custom rom is available for zenfone laser.