So I need help badly! And of course, I've even asked if I could pay someone. I'm new to phones/tablets/android. Very comfortable with all things computer though. I bought the Amazon Kindle Fire HDX 8.9 for the second time off Ebay that Amazon did not want to register without a receipt from my seller's purchase. I wanted this tablet for the specs and also we do a lot with Amazon. I've been customizing my computer for years and I don't care the specs of the $50 fires that are coming out in 2017. However both my sellers were honest and gave me everything but their social security cards and said they had it registered in their name and called Amazon as well. It seems almost like Amazon is finding a way not to register these secondhand Fires that are discontinued without a receipt from the original owner for "security". So this is when I found out about rooting while googling my problem. I have the 4.2 OS. And I've read a lot of warnings about this particular model. Most of the advice is over two years old so I want to know what can currently be done to turn this tablet into an Android. Is it possible?
And can I get simple detailed instructions so that I don't "soft brick" or "hard brick" my device.
I got full refund from my first seller. The second one told me he would give me partial credit if I kept it and tried to root it. If it bricks he says he will refund me completely. He is under the impression that rooting isn't difficult.
Can someone please help me?
Wendy
justyermama said:
So I need help badly! And of course, I've even asked if I could pay someone. I'm new to phones/tablets/android. Very comfortable with all things computer though. I bought the Amazon Kindle Fire HDX 8.9 for the second time off Ebay that Amazon did not want to register without a receipt from my seller's purchase. I wanted this tablet for the specs and also we do a lot with Amazon. I've been customizing my computer for years and I don't care the specs of the $50 fires that are coming out in 2017. However both my sellers were honest and gave me everything but their social security cards and said they had it registered in their name and called Amazon as well. It seems almost like Amazon is finding a way not to register these secondhand Fires that are discontinued without a receipt from the original owner for "security". So this is when I found out about rooting while googling my problem. I have the 4.2 OS. And I've read a lot of warnings about this particular model. Most of the advice is over two years old so I want to know what can currently be done to turn this tablet into an Android. Is it possible?
And can I get simple detailed instructions so that I don't "soft brick" or "hard brick" my device.
I got full refund from my first seller. The second one told me he would give me partial credit if I kept it and tried to root it. If it bricks he says he will refund me completely. He is under the impression that rooting isn't difficult.
Can someone please help me?
Wendy
Click to expand...
Click to collapse
Device can be rooted w/o registering and install the custom ROM of your choice. But it will take some work, patience and tech experience. I can point you to the technical documents early next week if interested. Travelling with limited/no network access this weekend.
Davey126 said:
Device can be rooted w/o registering and install the custom ROM of your choice. But it will take some work, patience and tech experience. I can point you to the technical documents early next week if interested. Travelling with limited/no network access this weekend.
Click to expand...
Click to collapse
:angel: So I really appreciate the quick response, and you have renewed my hope for this situation. That would be absolutely great. I once had Linux OS on a used computer I bought and quickly reformatted so I could install Windows. I found it to be not very user-friendly. However, while I'm waiting for next week to come, should I study the Linux OS or is there anything I should read or concentrate on learning, off the top of your head, to make my journey a little bit easier? Thanks again.
jymama
WAITING Patiently for Direction to root/flash Blacklisted Kindle Fire 8.9
justyermama said:
:angel: So I really appreciate the quick response, and you have renewed my hope for this situation. That would be absolutely great. I once had Linux OS on a used computer I bought and quickly reformatted so I could install Windows. I found it to be not very user-friendly. However, while I'm waiting for next week to come, should I study the Linux OS or is there anything I should read or concentrate on learning, off the top of your head, to make my journey a little bit easier? Thanks again.
jymama
Click to expand...
Click to collapse
Still Waiting to find out how to turn my blacklisted fire hdx 8.9 4th gen into a usable tablet. When I found out it was possible, I decided I would give it a shot and accepted $50 of the $130 I paid and kept it. Anyone who can help someone who is good with a computer, but I have no experience/knowledge with androids, I'm willing to learn if someone could point out the way. This particular model of tablet is supposed to not be easy to do, and please take into consideration my inexperience with this, I am willing to put time and effort if I could get the information/specific directions. I'm willing to compensate someone for their time. Please help.
Thank you, Wendy
jyermama
justyermama said:
Still Waiting to find out how to turn my blacklisted fire hdx 8.9 4th gen into a usable tablet. When I found out it was possible, I decided I would give it a shot and accepted $50 of the $130 I paid and kept it. Anyone who can help someone who is good with a computer, but I have no experience/knowledge with androids, I'm willing to learn if someone could point out the way. This particular model of tablet is supposed to not be easy to do, and please take into consideration my inexperience with this, I am willing to put time and effort if I could get the information/specific directions. I'm willing to compensate someone for their time. Please help.
Thank you, Wendy
jyermama
Click to expand...
Click to collapse
Hi - as noted in my original response time, patience and some technical expertise will be needed to root the device via the 'bulk mode' approach. Unfortunately, time is not an abundant resource at present so you're pretty much on your own outside responding to specific questions. Below is the initial technical document which will undoubtedly seem overwhelming on initial inspection. You will likely want to read through the next few posts to adsorb guidance from the author (@draxie). Better yet, scan/search the thread for the word 'bulk' for related posts. Also see this post for links to a couple 'tools' that you will need to install on a Windows host before getting started. Good luck; ask questions as they arise.
bulk mode doc: https://forum.xda-developers.com/showpost.php?p=71430759&postcount=736
main bootloader unlock thread: https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
auxiliary thread (lots of good info): https://forum.xda-developers.com/kindle-fire-hdx/general/thor-4-5-5-2-easy-to-root-unlock-t3571240
Davey126 said:
Hi - as noted in my original response time, patience and some technical expertise will be needed to root the device via the 'bulk mode' approach. Unfortunately, time is not an abundant resource at present so you're pretty much on your own outside responding to specific questions. Below is the initial technical document which will undoubtedly seem overwhelming on initial inspection. You will likely want to read through the next few posts to adsorb guidance from the author (@draxie). Better yet, scan/search the thread for the word 'bulk' for related posts. Also see this post for links to a couple 'tools' that you will need to install on a Windows host before getting started. Good luck; ask questions as they arise.
bulk mode doc: https://forum.xda-developers.com/showpost.php?p=71430759&postcount=736
main bootloader unlock thread: https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
auxiliary thread (lots of good info): https://forum.xda-developers.com/kindle-fire-hdx/general/thor-4-5-5-2-easy-to-root-unlock-t3571240
Click to expand...
Click to collapse
I have done all the step in the link of bulk mode you post. It works very well with many KFHDX7 I have done but one of mine can't flash any ROMs although it can boot to recovery and bootloader. Could you help me?
P/s: It stuck at the white kindle fire logo after I flash any ROMs but I can boot to TWRP and fastboot.
Chatchum said:
I have done all the step in the link of bulk mode you post. It works very well with many KFHDX7 I have done but one of mine can't flash any ROMs although it can boot to recovery and bootloader. Could you help me?
P/s: It stuck at the white kindle fire logo after I flash any ROMs but I can boot to TWRP and fastboot.
Click to expand...
Click to collapse
Be sure to wipe storage before attempting to flash a new/different ROM:
- make sure the latest TWRP build is installed (link)
- boot into TWRP
- tap Wipe followed by Advanced Wipe
- tick all partitions EXCEPT 'Internal Storage'
- execute wipe (may take a few seconds)
- return to main menu and flash ROM of your choosing
- only ROMs customized for this device can be flashed
- some require a GAaps package and/or SuperSU; read ROM OP for details
If the above fails perform a comprehensive wipe that includes all partitions. Then reboot device into TWRP, re-download ROM and supporting packages and attempt to flash again.
Davey126 said:
Be sure to wipe storage before attempting to flash a new/different ROM:
- make sure the latest TWRP build is installed (link)
- boot into TWRP
- tap Wipe followed by Advanced Wipe
- tick all partitions EXCEPT 'Internal Storage'
- execute wipe (may take a few seconds)
- return to main menu and flash ROM of your choosing
- only ROMs customized for this device can be flashed
- some require a GAaps package and/or SuperSU; read ROM OP for details
If the above fails perform a comprehensive wipe that includes all partitions. Then reboot device into TWRP, re-download ROM and supporting packages and attempt to flash again.
Click to expand...
Click to collapse
I forgot unlock bootloader before flash ROMs on that HDX7. Do you think it made that problem?
These ROMs are work very well, because I flash 3 HDX7s by the same way with this HDX7 but there is no problem.
Please help me!
Chatchum said:
I forgot unlock bootloader before flash ROMs on that HDX7. Do you think it made that problem?
These ROMs are work very well, because I flash 3 HDX7s by the same way with this HDX7 but there is no problem.
Click to expand...
Click to collapse
Wipe and flash this ROM. Work? If so proceed with bootloader unlock using Fire Nexus as a temporary base.
Chatchum said:
Please help me!
Click to expand...
Click to collapse
This ^^ is both annoying and unnecessary.
Davey126 said:
Wipe and flash this ROM. Work? If so proceed with bootloader unlock using Fire Nexus as a temporary base.
This ^^ is both annoying and unnecessary.
Click to expand...
Click to collapse
It works very well.
Chatchum said:
It works very well.
Click to expand...
Click to collapse
Great! You should now be able to generate an unlock code specific to your device (step #1) and unlock the bootloader (step #3), possibly with the help of these drivers to enable fastboot communications from a Windows host.
I flashed wrong TWRP file, and now my HDX7 couldn't boot to recovery or bootloader by press power + up (down) button and it stuck in white logo.
Chatchum said:
I flashed wrong TWRP file, and now my HDX7 couldn't boot to recovery or bootloader by press power + up (down) button and it stuck in white logo.
Click to expand...
Click to collapse
You're in a world of hurt if device can not be placed into fastboot mode via <power>+<vol-down>. Your may need to attempt a recovery via 'bulk mode' which is neither easy nor assured.
https://forum.xda-developers.com/ki...isted-kindle-fire-hdx-8-t3636657/post73104157
Davey126 said:
You're in a world of hurt if device can not be placed into fastboot mode via <power>+<vol-down>. Your may need to attempt a recovery via 'bulk mode' which is neither easy nor assured.
https://forum.xda-developers.com/ki...isted-kindle-fire-hdx-8-t3636657/post73104157
Click to expand...
Click to collapse
I have tried to do via bulk mode but I can't boot to fastboot to do all of it
Chatchum said:
I have tried to do via bulk mode but I can't boot to fastboot to do all of it
Click to expand...
Click to collapse
Sorry this happened. Bulk mode is the last option short of replacing boards.
Related
Alright so there are a few users who are locked on Jelly Bean and are wanting to take the dive of unlocking and installing a custom rom. So I figured I'd put together this little guide to hopefully help y'all out.
I am not responsible for any damage you do to your device. Following this is your choice.This will void your Asus warranty and you assume all responsibility from here on out.
As long as you follow all directions in this guide your device will not be bricked. It will be unleashed to this beast of a tablets max power
Before you continue make sure you:
1. Have the drivers for your device installed on your computer
2. Have made the upgrade to Jelly Bean
3. Have the USB cable for your Prime
4. Have nerves of steel and the ability to read all and follow instructions in this guide.
Useful Information for total beginners: Some people using this guide may not even entirely understand what they are undertaking. This is not acceptable so it's time for some education. Android is a Linux based operating system (in it's self, not direly important information but it's nice background knowledge) which means that there are certain permissions to users. Having "root" permission is like being an "Administrator" on Windows systems. All devices come without "root" permissions as the total new users can do irreparable damage to their device. This is different than unlocking your boot loader. Unlocking your boot loader (in the Transformer Prime's case) is the act of saying to Asus "I willingly give up my devices warranty in exchange for the ability to totally control my device so I can flash custom software". Unlocking does not automatically give a device root permissions. This can only be obtained through an exploit or by flashing the proper thing after unlocking. Since I'm not perfect at wording (and it's best to educate yourself as much as possible on the subject) there is more info here:
http://www.androidpolice.com/2010/0...top-5-benefits-of-rooting-your-android-phone/
http://www.droidforums.net/forum/ga...53-explain-unlocking-boot-loader-rooting.html
Step 1 Download the Unlock tool here: http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_Prime_TF201/#download (navigate to Downloads, then select the OS as Android, then scroll to utilities and expand the menu. Find the unlock tool and download that. Don't worry about the "For ICS only" disclaimer. This has been confirmed working on Jelly Bean). Install this app on your Prime and run it. Connect to a network before doing so and follow all on-screen directions.
Step 2. By this point the unlock tool has done it's job and when you boot your Prime now has a nice "Your device is unlocked" message in the upper left corner of the screen. The next step is to flash a custom recovery image (TeamWin Recovery Project(TWRP) in this guides case). This may sound complicated but there are multiple easy ways to do this.
Option 1: Go to the TeamWin website and download the needed files as directed on the page and follow the instructions on the website to flash TWRP. (http://teamw.in/project/twrp2/93)
Option 2 (easy option): This option flashes TWRP running a file from your Windows computer. The file attached at the bottom of this guide needs to be downloaded and unzipped to your desktop. Once this is done you power of your Prime and turn it back on while holding the volume down button. Once the tab vibrates release the power button but continue to hold the volume down button.
Once this has been done you will see 4 icons pop up. One is the USB symbol. Navigate to that by pressing the Volume Down button until the icon is highlighted and press volume up to select it (the menu will say use Volume Up to navigate but this is incorrect). This will put your device into fastboot mode. Connect your Prime to your computer via the USB cable and open the folder you extracted earlier. Run the Windows Batch File. This will automatically flash the TeamWin Recovery image for the Jelly Bean bootloader.
Now that you have unlocked and have a custom recovery installed you can begin the flashing. To get into your recovery all you do is power up while holding volume down and select the RCK icon. This boots the recovery image and you'll be able to flash, back up, and restore roms. All threads will have a guide on how to flash the rom in the thread so I won't go into detail. I do suggest however, using a microSDcard to store downloaded roms for flashing as it is safer than internal storage. If you are looking to back up your apps then there's this amazing app called Titanium Backup on the Android Market. It's very powerful and can backup your apps as well as user data.
HELP! Something went wrong and I need help: As with all processes there can be issues that arise. Some are common and others are individual. Let's address some common problems for all you who are still nervous about this:
1. Everything seemed to go fine but my Prime won't boot into TWRP
SOLUTION: This problem comes up for a few reasons and is pretty common. A lot of time it's simply a bad download or you have the wrong files. Check the files you have and make sure they are the right ones. If so then download them again. Sometimes a download just gets corrupted. If neither of these solutions worked either try another method of installing TWRP outlined on their website or post here and either I or another helpful person will do everything possible to help
2. When I tried to flash a custom ROM it won't boot:
SOLUTION: Usually this is an issue specific to the ROM you are flashing. The basic list of problems to eliminate are:
1.Ensure you have a good download
2.Ensure you have the proper boot loader for the ROM (i.e. JB boot loader for Jelly Bean ROMs
3. Try reflashing the rom. Sometimes something just doesn't work and the only way to fix it is to reflash​
Vocab guide for totally new users:
Rom(s): Basically the operating system of your device.
TWRP: Team Win Recovery Project. Started by developers here at XDA and is a powerful recovery tool.
Brick/bricked device: Developer term for saying your device will no longer work due to software/roms and is basically a very, very expensive brick/paper weight.
FAQ: Q: My device is on Jelly Bean but the unlock tool will not work for me no matter what I do. What's wrong?
A: Asus has some issues as a company and certain people are completely unable to unlock their device no matter what. I suggest contacting Asus with your devices S/N and politely ask for an explanation and see if the issue can be resolved. Many users who have used the Asus RMA have still been unable to unlock afterwards.
Other useful links: http://www.youtube.com/watch?v=-pW05Jf87dg&list=UU7YzoWkkb6woYwCnbWLn3ZA&index=22&feature=plcp
Very comprehensive video guide with a full walkthrough to help all with this process. And of course all users can PM me with questions or ask them here.
SuperSU.zip attached is for those who want to root the stock rom. Any custom rom should already be rooted for you.
Good tutorial ..On your way to becoming a recognized contributer
Sent from my LG-P509 using Tapatalk 2
Unfortunately the unlocking tool doesn't work on my TFP, which currently is fully stock 10.4.2.17 and connected to network through wifi.
Tried rebooting, cold booting, waiting, cursing. Might try smashing it against a wall next.
Strange because I've read about many people confirming the tool working on JB. But no luck for me I guess.
DaLongTjeu said:
Unfortunately the unlocking tool doesn't work on my TFP, which currently is fully stock 10.4.2.17 and connected to network through wifi.
Tried rebooting, cold booting, waiting, cursing. Might try smashing it against a wall next.
Strange because I've read about many people confirming the tool working on JB. But no luck for me I guess.
Click to expand...
Click to collapse
The unlock tool doesn't work for about half the people on this forum. There is a separate thread about the whole unlock tool issue. Its useless. Asus refuses to do anything about it. They suggested RMA for some people to fix the unlock issue but when the tablet was returned, it was still locked. Take a look at the thread.
applesuckz said:
The unlock tool doesn't work for about half the people on this forum. There is a separate thread about the whole unlock tool issue. Its useless. Asus refuses to do anything about it. They suggested RMA for some people to fix the unlock issue but when the tablet was returned, it was still locked. Take a look at the thread.
Click to expand...
Click to collapse
I know. There are several threads concerning the unlock tool. My TFP went RMA 2 times, I was unable to unlock after both RMA's. I had root in ICS, but completely lost it after the JB OTA. I was hoping the recent OTA update would change something about the unlocking problems everyone's having, but for me it didn't change a thing.
The OP would be wise not to state that "Don't worry about the "For ICS only" disclaimer. This has been confirmed working on Jelly Bean". For it has be confirmed working on JB by a few user; many of us are unable to unlock even after the latest OTA.
Nothing works for me: reboot, cold boot, factory reset.
I desperately want to installl a custom rom on my TFP to see if that unleashes it's full potential. Right now I own a HTC One X+, which has the same cpu as the TFP but it's many times faster, smoother and less annoying. I still believe the TFP has the potential to be what it was intended to be, but ASUS software isn't going to do that for us.
DaLongTjeu said:
I know. There are several threads concerning the unlock tool. My TFP went RMA 2 times, I was unable to unlock after both RMA's. I had root in ICS, but completely lost it after the JB OTA. I was hoping the recent OTA update would change something about the unlocking problems everyone's having, but for me it didn't change a thing.
The OP would be wise not to state that "Don't worry about the "For ICS only" disclaimer. This has been confirmed working on Jelly Bean". For it has be confirmed working on JB by a few user; many of us are unable to unlock even after the latest OTA.
Nothing works for me: reboot, cold boot, factory reset.
I desperately want to installl a custom rom on my TFP to see if that unleashes it's full potential. Right now I own a HTC One X+, which has the same cpu as the TFP but it's many times faster, smoother and less annoying. I still believe the TFP has the potential to be what it was intended to be, but ASUS software isn't going to do that for us.
Click to expand...
Click to collapse
The issue is not Jelly Bean. The issue is sometimes the servers Asus uses to cross check your serial numbers loses some peoples S/N's. Without a registered S/N the unlock tool will not work. This is the fault of Asus and has been discussed many times. Developers have even decompiled the unlock tool and tried to reverse engineer it to solve this issue to no avail. Please, feel free to do some research if you doubt my answers. Many have spent hours doing so to only find out what they've been told.
McJesus15 said:
The issue is not Jelly Bean. The issue is sometimes the servers Asus uses to cross check your serial numbers loses some peoples S/N's. Without a registered S/N the unlock tool will not work. This is the fault of Asus and has been discussed many times. Developers have even decompiled the unlock tool and tried to reverse engineer it to solve this issue to no avail. Please, feel free to do some research if you doubt my answers. Many have spent hours doing so to only find out what they've been told.
Click to expand...
Click to collapse
I don't doubt your answer, I had never heard about any server-related issues though. Lots of people reported that their Prime's somehow had forgotten their serial numbers, but mine still has it's serial number. Also I registered my S/N online and it's still there, but I don't think that's related in any way. I RMA'd twice, I'm able to get OTA fm updates (possibly a clue that there are no server-side issues with my S/N), but now I'm unable to unlock.
Your guide is great and I really hope it helps many users unlock their Primes so they can get rid of the stock rom and flash a proper one onto their devices. You might want to insert a note though, that even though the unlock tool has been confirmed to work on some JB-primes there's still a chance it won't work (whatever the reason is).
OK let's stop squabbling about semantics here. Fact of the matter is that whoever's able to unlock at this point is quite lucky. The rest of us will just have to wait until ASUS fixes the issues or some whizzkid with too much time on his hands does.
You are a Gem, this finally made the process so much clearer
Shizbazki said:
You are a Gem, this finally made the process so much clearer
Click to expand...
Click to collapse
Thank you feel free to hit the thanks button
Sent from my Zio using xda app-developers app
Hi. I did all the steps you mentioned. In flashing TWRP I chose the 2nd option and everything went great.
The problem appears when I want to go to my recovery (power up holding volume down and then RCK) I get the droid with exclamation mark and nothing happens. Flashing recovery was succesful and I dont have an idea what could went wrong. I'm bit a new user of TF201 so would be grateful if You can help me
EDIT: Ah, I saw now that recovery is not flashing properly, saying sth like InvalidState.
EDIT 2: Ok I handled it myself, thanks again for the guide it was very useful!
Flashed Androwook this morning. Thanks for the painless guide.
Annoyed that nvflash isn't supported on Jelly Bean though. Now that I've flashed, can I get it?
GS_Dan said:
Flashed Androwook this morning. Thanks for the painless guide.
Annoyed that nvflash isn't supported on Jelly Bean though. Now that I've flashed, can I get it?
Click to expand...
Click to collapse
Nvflash is only available to users who did it while on ICS.
Sent from my Zio using xda app-developers app
McJesus15 said:
http://forum.xda-developers.com/showthread.php?t=1998359
Link to my guide thread in the general forum. If anybody has any questions you can PM me or comment there and it'll likely be answered quickly. I'll gladly guide anyone through this process if they need other information.
Click to expand...
Click to collapse
well, I'm unlocked and TWRPed, but what I would really like is root on my stock before flashing AW. So I can install and use TB for the apps...? (I'm on most current updated stock.)
BTW, your lil guide is stupendous. Stupid easy and took minutes. TYVM! I have only vaguely been following the TP forums, stock was fine enough for me, until recently. Was bored of flashing my phone and got the itch today to try something new with the TP. Did a backup, and ready to try some Wookie! Just that lil app issue, cause I'm lazy.
EDIT: correct me if I'm wrong, but after a bit of research (go figure!) it would appear that both Sparky and debugfs won't work on JB/most current stock? Tough sh** for me?
kingdazy said:
well, I'm unlocked and TWRPed, but what I would really like is root on my stock before flashing AW. So I can install and use TB for the apps...? (I'm on most current updated stock.)
BTW, your lil guide is stupendous. Stupid easy and took minutes. TYVM! I have only vaguely been following the TP forums, stock was fine enough for me, until recently. Was bored of flashing my phone and got the itch today to try something new with the TP. Did a backup, and ready to try some Wookie! Just that lil app issue, cause I'm lazy.
EDIT: correct me if I'm wrong, but after a bit of research (go figure!) it would appear that both Sparky and debugfs won't work on JB/most current stock? Tough sh** for me?
Click to expand...
Click to collapse
Once unlocked you can root with a flashable zip. Can't link to one but they're easy to find here on the TFP forum
Sent from my Zio using xda app-developers app
So this would be su.zip (or whatever it's called), and have the following structure?
su.zip
META-INF/
CERT.RSA
CERT.SF
MANIFEST.MF
COM/
GOOGLE/
ANDROID/
update-binary
updater-script
system/
app/
Superuser.apk
bin/
su
I just want to confirm if the file I found is correct or not. Does it need to be for a specific tablet/system? If it was just the app folder and the su binary I wouldn't ask, but the inclusion of metadata has me concerned as I can't seem to find one for the prime specifically.
EDIT: Yup, that's it. I stuck it on the internal storage, went into TWRP, choose "install", navigated to the zip, and it went without a hitch (installed the su binary and superuser app, effectively rooting the system).
Overall, this a good process for people that just want to root without all the hassle of replacing the whole OS.
the unlock tool failed to unlock on my tab... i think its because i did an RMA and asus changed the board inside the device..
GS_Dan said:
Flashed Androwook this morning. Thanks for the painless guide.
Annoyed that nvflash isn't supported on Jelly Bean though. Now that I've flashed, can I get it?
Click to expand...
Click to collapse
What do you think of androwook? Is much better than stock JB?
BashYaBro said:
the unlock tool failed to unlock on my tab... i think its because i did an RMA and asus changed the board inside the device..
Click to expand...
Click to collapse
Try contacting Asus.
sauliiin said:
What do you think of androwook? Is much better than stock JB?
Click to expand...
Click to collapse
Androwook 1.4 turns the prime into the tab it should be. Out scores stock by a lot on benchmarks
Sent from my Zio using xda app-developers app
sauliiin said:
What do you think of androwook? Is much better than stock JB?
Click to expand...
Click to collapse
Very fast, responsive. With the exception of the broken search (there is a fix), and a few other minor issues, I would not hesitate to flash it. Ver 1.5 is right around the corner with several things fixed, and apparently there will be a flashable update from 1.4.
mrwookie6379 said:
Just to give you guys a heads up I will be releasing v1.5 fairly soon to take advantage of the new update that is out but before anyone groans about only having just flashed v1.4 I will release it as an update to those already on v1.4 but also as a full ROM for those who want to skip v1.4 and go straight to v1.5.
Beta 1 for v1.5 was created this PM and is being uploaded for testing now so watch this space.
Click to expand...
Click to collapse
Awesome.
kingdazy said:
Very fast, responsive. With the exception of the broken search (there is a fix), and a few other minor issues, I would not hesitate to flash it. Ver 1.5 is right around the corner with several things fixed, and apparently there will be a flashable update from 1.4.
Awesome.
Click to expand...
Click to collapse
I really ansious about flashing androwook... Just have to found some time!! Thinking about doing it this weekend!
Well.... So do you think really worths the upgrade to Androwwok? I saw that the search bug has a fix, but are there too many other bugs?
And, the performance, is really much better?
Thansk for the answer, friend.
regards
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.
Trying to root Nougat (Android 7)? Then read the comments at the bottom please...
I will first state I do NOT own a Moto G4, I own the G3 and the X Pure which are both 3rd Gen devices, but I was requested to write this tutorial by a few users here due to lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto G3/4, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread. Remember, I do not own this device although the methods used are the same as similar devices.
Prerequisites:
0) Be running Marshmallow (Android 6.x) stock ROM, at this time Nougat (Android 7.x) is not working via any method.
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: As of 7/18/2016, Amazon ad-subsidised Moto G 4th Gen devices cannot be bootloader unlocked, therefore they cannot be rooted. Sorry, Lollipop and newer Android security changes pretty much put an end to that.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See TWRP's Moto G 2016 page
3) You need a copy of the latest stable SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device. SR1-SuperSU-v2.78-SR1-20160915123031.zip is the lastest version verified to work with this method.
Note: Do NOT use any 2.77 version, it was a beta intended specifically for the SG Note 7 and will not work, it does not harm but fails to root.
4) Reboot and start TWRP recovery, and PERFORM A COMPLETE BACKUP IN TWRP (Nandroid)!!!
How to do it:
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
EDIT: Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
Notes on Nougat/Android 7... At this time this method of rooting does not work properly on the official Nougat ROM for this device, it causes WiFi issues and interface problems (settings crashes, etc) and with no complete factory image there is no work fix other than to restore your Nandroid backup to pre-root status. If you wish to play with this method and try it, your on your own, I will try to assist but as I stated earlier I do not own this device. To my knowledge as of this posting, there is no working root on stock Android 7 on this device.
I can confirm this worked on my formerly-amazon XT1625 16GB G4. You will get an error about not being able to mount /data, but it proceeds and works anyway.
This is exactly what was missing! I rooted as normal with the latest SuperSU expecting it to just work like on other phones/tablets, but yeah. Before specifying systemless, it hung on boot. After following your instructions it booted right up. Thanks!
Also if you setup adaptable storage with your SDcard, so it works like internal storage, TWRP can't find any files on the SDcard. You will need to revert to non-adaptable storage for TWRP to find the supersu ZIP file.
And make sure you're using the latest SuperSU-- I accidentally tried a very old version which did not work!
Scared Noobie
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Appreciate this. I miss the old days where it was all simple. Everything was flashable. Never had to flash back to something or re flash.
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
Very rare...all you need is read, read, read and follow the instructions. Good luck
Very nice and just what I needed. Worked perfectly on my Amazon Moto G4 with ads. I got no errors or messages but booted fine-got caught in a boot loop once as the SuperSU file explains after it installs. Boots in less then a minute first time.
Marty
acejavelin said:
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Tomsgt said:
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Click to expand...
Click to collapse
cheers mate
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
zipjay said:
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
Click to expand...
Click to collapse
Your welcome... Just give click thanks on the first post, but if you feel absolutely compelled to buy me dinner, there is the Donate button.
Sent from my MotoG3 using Tapatalk
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
mikeruss said:
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
Click to expand...
Click to collapse
Can't you just use MTP mode of TWRP to copy the latest SuperSU to internal storage then flash after creating the config file?
Sent from my MotoG3 using Tapatalk
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
mikeruss said:
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
Click to expand...
Click to collapse
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
acejavelin said:
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
Click to expand...
Click to collapse
32 bit
Sent from my Moto G (4) using Tapatalk
thanks, xposed works fine
Well, I was planning on joining all of you with your Moto G4's soon, or possibly the G4 Plus... but since the Amazon version can't be unlocked anymore I got cold feet, and today Best Buy was running a special on the Moto X Pure 32GB edition for $249 (My Best Buy Elite members only), I pulled the trigger on that one instead. No change in helping though, I didn't have the device to begin with so I will continue to assist with this thread as I can.
Good day everyone.
Please, give me an advice. How to unlock FRP HONOR 5X (Android 6.0.1, EMUI 4.0, Kiw-L21) ????
Thank you for your advice
Tatrox said:
Good day everyone.
Please, give me an advice. How to unlock FRP HONOR 5X (Android 6.0.1, EMUI 4.0, Kiw-L21) ????
Thank you for your advice
Click to expand...
Click to collapse
remove your google accounts from the phone reboot
You can follow this guide to successfully unlock your phone.
Hope this helps you.
Did you ?
Hey !
Did you succeed unlock FRP ?
I have the same problem to be able to flash a stock recovery...
I have no access to the Stock Custom and I'm not able to remove any google Account (my Phone has no rom).
If you did something for this, please keep me inform
And excuse my language : I'm french.
Cheers
Did some searching around and found this thread.
http://forum.xda-developers.com/honor-5x/help/unlock-bootloader-issues-kiw-t3411032
The information is here:
tohc1 said:
To answer my own problem/ for anyone else having problems it is necessary to remove the factory reset protection (frp) to do this you need to remove all pin/password/fingerprint locks, then remove all google accounts and finally do a factory reset.
Then the usual adb/fastboot commands work fine.
As linux33it says the bootloader can be unlocked without the option in the developer options.
Click to expand...
Click to collapse
While this works for some - it failed to work for me. Maybe because I didn't enable a little option on the screen about allowing OEM unlock. Maybe. But I (stupidly?) ended up where I was sent in this external guide.
http://www.modaco.com/forums/topic/...our-honor-5x-official-and-unofficial-methods/
Basically went to this site and used their tool (cost me USD$16) to wipe the FRP.
https://www.dc-unlocker.com
Maybe if you enable the option about the OEM unlock in Developer Mode this isn't necessary..........
Hopefully this helps someone. So to outline - let me show what I did - including errors.
Wipe the phone / factory reset.
Reboot and ensure everything is removed. Factory reset again.
Tried the commands - got error.
Did search for FRP unlock and found site.
Followed instructions on site which led me to download DC Unlocker and pay for their FRP unlock.
Reboot and setup phone (with no accounts or password or fingerprints).
Enabled "OEM UNLOCK" in developer options (which I didn't see before.........)
Run commands (they all now work).
Bootloader unlocked successfully.
Device factory resets.
Setup device again skipping accounts/password/fingerprints.
Follow instructions for flashing TWRP and finishing up.
Complete.
Again - hopefully this helps someone.
id recomend official one.. seems easy
thilak devraj said:
id recomend official one.. seems easy
Click to expand...
Click to collapse
Explain please? What I'm putting forward is some information for persons that may not be as mobile tech inclined. Or persons over-eager like myself (actually bricked the phone and brought it back from boot-loop). While some information may be common knowledge for persons who do this often (or devs), persons just getting into it may make mistakes. Don't want them to do stuff and end up bricking the device.
khat17 said:
Explain please? What I'm putting forward is some information for persons that may not be as mobile tech inclined. Or persons over-eager like myself (actually bricked the phone and brought it back from boot-loop). While some information may be common knowledge for persons who do this often (or devs), persons just getting into it may make mistakes. Don't want them to do stuff and end up bricking the device.
Click to expand...
Click to collapse
Look at the twrp thread in android development section..
There is a detailed guide how to
khat17 said:
Explain please? What I'm putting forward is some information for persons that may not be as mobile tech inclined. Or persons over-eager like myself (actually bricked the phone and brought it back from boot-loop). While some information may be common knowledge for persons who do this often (or devs), persons just getting into it may make mistakes. Don't want them to do stuff and end up bricking the device.
Click to expand...
Click to collapse
It's a worthwhile effort. Appreciate it buddy.
khat17 said:
Explain please? What I'm putting forward is some information for persons that may not be as mobile tech inclined. Or persons over-eager like myself (actually bricked the phone and brought it back from boot-loop). While some information may be common knowledge for persons who do this often (or devs), persons just getting into it may make mistakes. Don't want them to do stuff and end up bricking the device.
Click to expand...
Click to collapse
Even newbies can do it right. Provided that they strictly follow the steps.
Sent from my Galaxy Tab 3 using XDA Labs
I agree. But I don't recall seeing anything in the original instructions about the FRP which shows / states ensuring OEM unlock is checked. Unless I missed it. I DO recall seeing it somewhere else in another thread where someone mentioned it. But I still don't know if the case is enabling it means you don't need to use the DC Unlocker program.
thilak devraj said:
id recomend official one.. seems easy
Click to expand...
Click to collapse
adriansticoid said:
Even newbies can do it right. Provided that they strictly follow the steps.
Sent from my Galaxy Tab 3 using XDA Labs
Click to expand...
Click to collapse
khat17 said:
I agree. But I don't recall seeing anything in the original instructions about the FRP which shows / states ensuring OEM unlock is checked. Unless I missed it. I DO recall seeing it somewhere else in another thread where someone mentioned it. But I still don't know if the case is enabling it means you don't need to use the DC Unlocker program.
Click to expand...
Click to collapse
you dont need dc unlocker, unless you have not checked "oem unlock" option in dev. options..(thats also only case if you were on lollipop)
and if you are on mm, you dont even need to check that option,
Thanks for that info. Next one I get my hands on will try that out and see.
thilak devraj said:
you dont need dc unlocker, unless you have not checked "oem unlock" option in dev. options..(thats also only case if you were on lollipop)
and if you are on mm, you dont even need to check that option,
Click to expand...
Click to collapse
khat17 said:
Thanks for that info. Next one I get my hands on will try that out and see.
Click to expand...
Click to collapse
what happened with the current one??
thilak devraj said:
what happened with the current one??
Click to expand...
Click to collapse
I had basically bricked it and brought it back. Think the one I got had some issues, because I couldn't update it at all. Even before rooting it wouldn't update. Then I realized that when the update was running it rebooted into TWRP - so I flashed back the stock recovery and tried again. No luck. This was done with disabling OEM unlock as well and still nothing. So I got an UPDATE.APP as well as a nandroid that I believe was supposed to be able to update the phone. None worked.
khat17 said:
It's a little bit of both. Those are the steps I followed to get root access. However, I don't recall seeing anything about the FRP in any of the previous guides.
As for my specific issue, I can't update regardless of what I try. After de-bricking the device I got it to this stage. I'll upload the screenshots shortly.
*EDIT*
So this is my phone now. Partly upgraded it seems. The device is now at B331 instead of B151, but still on EMUI 3.0
And what I want to point out is - after enabling DEVELOPER MODE - ensure you check the OEM UNLOCK option.
Because I can't confirm at this point if doing that will prevent having to pay for the FRP unlock.
Click to expand...
Click to collapse
But now that you've confirmed that there's no need to pay for the bootloader unlock, I would go ahead and do some experimenting if you suggest. For science. But I'm a little reluctant to try and re-lock the bootloader and then unlock it again. If you can confirm or even partly guarantee that it works however, I'll do some messing around with it. For science. Otherwise, I've managed to get the device to a working state now - wouldn't want to mess with it much.. Only if I can try something else to get EMUI 4 on it.
khat17 said:
I had basically bricked it and brought it back. Think the one I got had some issues, because I couldn't update it at all. Even before rooting it wouldn't update. Then I realized that when the update was running it rebooted into TWRP - so I flashed back the stock recovery and tried again. No luck. This was done with disabling OEM unlock as well and still nothing. So I got an UPDATE.APP as well as a nandroid that I believe was supposed to be able to update the phone. None worked.
.
Click to expand...
Click to collapse
thats something wiered,, you shouldve got it into service center before rooting, saying that it wasnt updating....
thilak devraj said:
thats something wiered,, you shouldve got it into service center before rooting, saying that it wasnt updating....
Click to expand...
Click to collapse
I live outside of the country of purchase. Doubt I can send it back now anyways. And I got it working so it's fine.
I like it better than the BLU and the Samsung I had. FAR easier to root. Even with the issues I had.
khat17 said:
I live outside of the country of purchase. Doubt I can send it back now anyways. And I got it working so it's fine.
I like it better than the BLU and the Samsung I had. FAR easier to root. Even with the issues I had.
Click to expand...
Click to collapse
how did you manage to get working??
thilak devraj said:
how did you manage to get working??
Click to expand...
Click to collapse
I posted it in this other thread.
khat17 said:
Hi all. I'd like to put forward some suggestions to be placed in the first post. I literally paid cash to learn and figure some stuff out. Even if you're good at following instructions or partially experienced in these things, when you're eager to get it done or impatient (like me) you find the fastest route.
Here are some links in case someone wants to just go through the whole thing themselves.
http://forum.xda-developers.com/honor-5x/how-to/unlock-frp-t3444584#post69917735
So here's what happened. I got the phone and was very eager to just get my stuff on it right away. Rooting is the first thing I wanted to do and looked that up to get it done. Made a mistake in the process and ended up paying cash to learn. Hopefully others will read this and not suffer the same fate.
What I Did (Including Mistakes)
Wipe the phone / factory reset.
Reboot and ensure everything is removed. Factory reset again.
Tried the commands - got error about FRP protection.
Did search for FRP unlock and found site.
Followed instructions on site which led me to download DC Unlocker and pay for their FRP unlock.
Reboot and setup phone (with no accounts or password or fingerprints).
Enabled "OEM UNLOCK" in developer options (which I didn't see/enable before.........)
Run commands (they all now work).
Bootloader unlocked successfully.
Device factory resets.
Setup device again skipping accounts/password/fingerprints.
Follow instructions for flashing TWRP and finishing up.
Complete.
Some other things to ensure you note - if you're migrating from any Samsung device, don't do restore of Samsung stuff like XPOSED to the Huawei. And don't just arbitrarily do a restore from Titanium either. Select only the apps you want to use, or do the longer process of getting them from Google then restoring the data after.
Something else I noticed on my KIW-L24 is that I can't update. At all. I tried using different methods including the UPDATE.APP file for the phone, but it just gets stuck in a boot-loop. Currently going to load the B151 UPDATE.APP and see if I can de-brick it. Will edit and update the thread.
*EDIT1*
And just my luck. Didn't work. So stuck in a boot-loop. Working on it and will update when done or I give up.
*EDIT2*
So during the boot-loop I held VOL-DOWN+PWR and it went to a FASTBOOT+RECOVERY option. From there I flashed TWRP back to it and the system is now up and working. So lesson learned there. No idea why my own won't go to 6 though. Don't mind 5, but wanted to go up to 6..............still - better to have it working than not working. So happy there.
Click to expand...
Click to collapse
Yeah. So after TWRP was flashed, I did a restore from a backup I found online. And that's how I managed to get it up. The restore was for 151 not 331.
khat17 said:
I posted it in this other thread.
Click to expand...
Click to collapse
anyway, nice to see that youve got it working,...
Hi,
Today I got my S7+ 5G in Germany. I tried to root via guide from s5e with own patched file. But I am not able to enter download mode, although bootloader is really unlocked. When select `fastboot mode` inside samsung recovery I run into a fastboot mode (as known from other devices, like oneplus). Has samsung change the behaviour?
Any advice?
EDIT:
Although the description in
https://forum.xda-developers.com/tab-s5e/how-to/galaxy-tab-s5e-sm-t720-root-t3947806
is very good, the botton-combo in step 11 is wrong: The device must be off. Vol+Up and -Down have to be pressed together and then plug in the USB-C cable to computer. Now download mode works.
But now I stuck in the middle of step 13 (after installing magisk and reboot - of course with power button and vol+up) - I run into bootloop...
Have to flash either original image or factory reset to get out: but in both cases: no root. Tried it several times, but still the same...
Maybe you could try this guide : https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root to see if it's any different.
You could also try to flash magisk beta to see if it solves the bootloop problem.
Also here is a troubleshooting guide for magisk issues which might be helpful : https://www.didgeridoohan.com/magisk/MagiskIssues
xperiefon said:
Maybe you could try this guide : https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root to see if it's any different.
You could also try to flash magisk beta to see if it solves the bootloop problem.
Also here is a troubleshooting guide for magisk issues which might be helpful : https://www.didgeridoohan.com/magisk/MagiskIssues
Click to expand...
Click to collapse
Thank you!
But I already had set up the tab without root. It is my first device w/o root ever. Will miss xprivacy and gravitybox and of course titanium backup. For adaway I use my pi-hole (and from outside via VPN). Maybe I give it a try again once TWRP exists (and hopefully custom roms). At least this is a good successor of my note 12.2pro.
caesar68 said:
Hi,
Today I got my S7+ 5G in Germany. I tried to root via guide from s5e with own patched file. But I am not able to enter download mode, although bootloader is really unlocked. When select `fastboot mode` inside samsung recovery I run into a fastboot mode (as known from other devices, like oneplus). Has samsung change the behaviour?
Any advice?
As soon as I get mine I will begin working at getting root working and building a device tree and creating twrp and lineage I posted a thread with more details.
Click to expand...
Click to collapse
Since these devices have snapdragon instead of usual Samsung's knox, do you think it would be possible to close an opened bootloader? I think an open bootloader voids the warranty, so I would like to be able to close it and service the tablet if needed. Otherwise it's going to be my first device without root, at least while the warranty lasts.
Jedi.Tester said:
Since these devices have snapdragon instead of usual Samsung's knox, do you think it would be possible to close an opened bootloader? I think an open bootloader voids the warranty, so I would like to be able to close it and service the tablet if needed. Otherwise it's going to be my first device without root, at least while the warranty lasts.
Click to expand...
Click to collapse
Once you unlock bootloader and trip knox, guarantee is gone forever
Looking forward how this is going on.
For me its pretty simple => no root no buy. I don't spend a lot of money on a device I can not do what I want.
Currently I own a Tab S2 and the specs of the 7+ are worth to think about an upgrade. But only with a real root access.
EugenStanis said:
Once you unlock bootloader and trip knox, guarantee is gone forever
Click to expand...
Click to collapse
Thanks for info. For some reason I thought that only applied to Exynos chips. Never had a Samsung device before
hurray said:
Looking forward how this is going on.
For me its pretty simple => no root no buy. I don't spend a lot of money on a device I can not do what I want.
Same for me there seems little interest from the community in supporting high end Samsung tablets. When I get mine I will get started on root development and lineage os ?
Click to expand...
Click to collapse
@Extreemator
It was always like that.
Thread lightly cleaned and edited as per XDA rule 2.1.
2.1 Language: XDA is a worldwide community. As a result, what may be OK to say in your part of the world, may not be OK elsewhere. Please don't direct profanity, sexually explicit language or other offensive content toward Members or their work. Conversely, while reading posts from other members, remember that the word you find offensive may not be offensive to the writer. Tolerance is a two-way street.
Click to expand...
Click to collapse
I will ask you politely to please refrain from futher use of improper language on this, or any other thread. Thank you all for your cooperation.
--Regards: Badger50