Database Develop

[Q] New to tablets and ROM

Hello ya'll, I'm new to the forum, I joined because of the wealth of information here.
So I'm not new to Android, had one ever since I was 16. I rooted both my droid phones(droid X with that awesome slider keyboard, and RAZR MAXX) to remove those pesky bloatware apps, but didn't ROM them, as it just wasn't something I wasn't aware of when I did it. So rooting was as far as I got.
But rooting and ROM-ing a tablet seems like it could be a daunting job, I'm new to the tablet world But I already have most of the tools, from previous roots, minus a few that are platform specific that I'm currently downloading to support the new CROMBi-X
I figure I'll go about getting everything I need, so when I get my tablet back from the shop, I'll be able to dive right into the CROMBi ROM.
//
I don't want to brick my tablet so hence the questions I am unclear on.
//
Question 1: Asus doesn't have the standalone unlock tool on their website. How do I go about getting that tool to unlock the tablet? Was it done OTA or downloaded and installed onto the tablet?
I have searched a few places, and browsed the developer forums, but haven't come up with a surefire way yet. I've seen everything from asking ASUS to unlock the tablet, to flashing CWM recovery, and than flashing a rooted version of the stock ROM, 've read several of the forums, but I need a little bit of "English" on the topic, as this is something new to me. I did come across a root.zip link but I'm not entirely sure that is what I am looking for, or if it is version/BLoader specific. If it is, then that pretty much covers that question.
Question 2: Are all the drivers on the ROM? Or do I need to use something like [ADB/FB/APX Driver] Universal Naked Driver 0.7?
Question 3: Mods. Are they downloaded OTA from the play store, or is there a list of compatible mods for the ROM? I realize that most of them are probably cosmetic right? I'm probably asking in the wrong forum, but since this is LINUX based, once rooted, if I put Ubuntu on the tablet, and then run a ROM on top of it? or Do I have to choose between one or the other?
I'm only asking because I run a few programs that aren't able to run on the android platform that I use for recreational purposes.
Anyway, that about covers a few of the base questions I have for now. Time to get ready for work. Thanks for any help in advance!

For 1:
It's on ASUS website
www.service.asus.com/#!downloads/c1wax
Version V1.0
Unlock Device App: Unlock boot loader of TF701T.(Only works with 4.2 JB and later OS)
For 2:
It's been a while since I rooted however I think you only need fastboot to be able to put the custom recovery on the tablet. If you have ADB/FB drivers already installed your pc should see your tablet without an issue. I don't know what APX is.
For 3:
Not sure what you mean by Mods. And last I checked I don't think that you can and Linux to this tablet yet however even if you could you only get one or the other.
Oh and make sure you read through all of the instructions for rooting and roming

Gone_phishing said:
Hello ya'll, I'm new to the forum, I joined because of the wealth of information here.
So I'm not new to Android, had one ever since I was 16. I rooted both my droid phones(droid X with that awesome slider keyboard, and RAZR MAXX) to remove those pesky bloatware apps, but didn't ROM them, as it just wasn't something I wasn't aware of when I did it. So rooting was as far as I got.
But rooting and ROM-ing a tablet seems like it could be a daunting job, I'm new to the tablet world But I already have most of the tools, from previous roots, minus a few that are platform specific that I'm currently downloading to support the new CROMBi-X
I figure I'll go about getting everything I need, so when I get my tablet back from the shop, I'll be able to dive right into the CROMBi ROM.
//
I don't want to brick my tablet so hence the questions I am unclear on.
//
Question 1: Asus doesn't have the standalone unlock tool on their website. How do I go about getting that tool to unlock the tablet? Was it done OTA or downloaded and installed onto the tablet?
Click to expand...
Click to collapse
sleepy2 gave you the link. You find the Unlock Tool under "Utilites" on the TF701 downloads page
I have searched a few places, and browsed the developer forums, but haven't come up with a surefire way yet. I've seen everything from asking ASUS to unlock the tablet, to flashing CWM recovery, and than flashing a rooted version of the stock ROM, 've read several of the forums, but I need a little bit of "English" on the topic, as this is something new to me. I did come across a root.zip link but I'm not entirely sure that is what I am looking for, or if it is version/BLoader specific. If it is, then that pretty much covers that question.
Click to expand...
Click to collapse
.
First you need to determine what firmware you are running now and decide which JB version you want to run.
Check under Settings > About Tablet > Software version. On stock your firmware version and bootloader version are identical.
If you are on JB 4.3 you have either 10.26.1.7 or 10.26.1.18 (if you have the former, update to .18)
If you are on JB 4.4.2 you have 11.4.1.17
On JB 4.3
a) You can root the tablet without unlocking the bootloader with Towelroot v1.
b) You can unlock, flash CWM and then flash sbdag's stock rooted rom, one of several custom roms or just the root.zip
On JB 4.4.2
Right now there is no way to root without unlocking the bootloader and flashing a custom recovery first.
Once unlocked and with CWM installed, you can flash sbdag's rooted stock rom or flash the root.zip.
CROMi-X 7.0 for 4.4.2 is in the works. I do not know if the other custom roms (CM, CROMi-X 6, CROMbi-KK) are compatible with the 11.4.1.17 bootloader yet, but that's just a matter of time.
To install CWM follow the insructions here:
http://forum.xda-developers.com/showthread.php?t=2604462
Question 2: Are all the drivers on the ROM? Or do I need to use something like [ADB/FB/APX Driver] Universal Naked Driver 0.7?
Click to expand...
Click to collapse
Try it. I did not have to install new adb/fastboot drivers and the device drivers installed on my PC automativcally. YMMV
Open Device Manager, then connect the tablet. Let the drivers install and see if it shows up in Device Manager.
Then boot the tablet into fastboot, connect it to PC and see if it shows up as a fastboot device.
Enable USB debugging in Developer Options, then connect the tablet booted into Android and see if it shows up as ADB interface in Device Manager.
If you need drivers you can use the ones you mentioned.
Question 3: Mods. Are they downloaded OTA from the play store, or is there a list of compatible mods for the ROM? I realize that most of them are probably cosmetic right?
Click to expand...
Click to collapse
You'll find mods in the rom thread or at least the links for those that work with that rom.. No OTA updates
I'm probably asking in the wrong forum, but since this is LINUX based, once rooted, if I put Ubuntu on the tablet, and then run a ROM on top of it? or Do I have to choose between one or the other?
I'm only asking because I run a few programs that aren't able to run on the android platform that I use for recreational purposes.
Click to expand...
Click to collapse
There's a thread in the TF700 dev section on dual booting Android and Ubuntu. Not aware that anybody has tried it on the TF701.

Thanks for the link Sleepy! I had searched the website a couple times before, but I must have missed that part of it. Every other time I went somewhere to find it, it came back page unavailable. I'm really disliking this Kuwaiti right now! Well I won't know until I get the tablet back what JB is on it, but I imagine it would be sent back to a factory setting because of the issues I was having, or just get a whole new tablet all together depending on what was causing it not to charge.
I appreciate the clarification on everything guys, without the tablet in my hands I'm pretty much downloading everything I can that might help me out. I already have CWM, and several versions of it to be on the safe side.
I have been doing nothing but non-stop research, but it's daunting to try and go through 115 pages of information and tools, and version changes and what's compatible and how to use them. Watching videos has simplified it a little bit.
The reason I asked about Ubuntu, was I saw it dual booted to an older CROMi 2.X on the 700T
I used to run XP pro/Ubuntu on my laptop. Which was really nice when I needed a lightweight OS to free up processing power. Well before I had to format due to a near catastrophic drive failure and unrepairable data corruption. Anyway, that is a project for another time, one thing at a time!
I'll be around, busy with work 6 days a week!
Thanks again!

berndblb said:
First you need to determine what firmware you are running now and decide which JB version you want to run.
Check under Settings > About Tablet > Software version. On stock your firmware version and bootloader version are identical.
If you are on JB 4.3 you have either 10.26.1.7 or 10.26.1.18 (if you have the former, update to .18)
If you are on JB 4.4.2 you have 11.4.1.17
Click to expand...
Click to collapse
4.4.x is KitKat, not Jelly Bean, isn't it?

pelago said:
4.4.x is KitKat, not Jelly Bean, isn't it?
Click to expand...
Click to collapse
Yes.

List of repairs done
So what I thought was a simple battery not charging issue turned out to be a host of things. I had to have the LCD, Touchpadboard, Docking cable and LCD cable replaced, luckily I was under warranty. I imagine that would have been expensive!

Brand new, 4.2.2, Any reason not to update to latest firmware?

Hi folks,
Just got my TF701T from Amazon on the $279 deal. I've connected it to my wifi but have not even set up a google account for it yet. It's doing an initial charge.
Is there any compelling reason not to let the update happen? The main short term use for the tablet will be that my 7 year old son will play games on it. Eventually, I'd still like to unlock it and maybe to a custom OS, but for now it's plain Jane use.
The only special thing I might want to do is get Helium/Carbon going so I can backup / restore game positions for him... I've got his status on several games saved from another tablet that had root and I backed them up. Would like to restore if possible. Does this require root?
Thanks. Looking forward to advice.
Marc

Hi, before giving my opinion, I would suggest you to look through the forum while you are here. That said, I have some opinions against updating to 4.4.2. The main reason is that there are some battery issues on that boot loader for some unknown reason. Also, there is no root exploit available for the 4.4.2 version without having to unlock the boot loader. I was told that 4.3 was the best to stay on right now if you can.I just recently got my tablet too from that same deal. On 4.3 there is a easy root exploit called towelroot available, so you can root without unlocking.
---------- Post added at 01:48 AM ---------- Previous post was at 01:48 AM ----------
I also believe that carbon needs root for using it. If you have any questions, feel free to ask!!

royredman said:
Hi, before giving my opinion, I would suggest you to look through the forum while you are here. That said, I have some opinions against updating to 4.4.2. The main reason is that there are some battery issues on that boot loader for some unknown reason. Also, there is no root exploit available for the 4.4.2 version without having to unlock the boot loader. I was told that 4.3 was the best to stay on right now if you can.I just recently got my tablet too from that same deal. On 4.3 there is a easy root exploit called towelroot available, so you can root without unlocking.
---------- Post added at 01:48 AM ---------- Previous post was at 01:48 AM ----------
I also believe that carbon needs root for using it. If you have any questions, feel free to ask!!
Click to expand...
Click to collapse
Thanks. I've used Carbon and believed it requires root, too. I'm a bit surprised that Towelroot wouldn't work on 4.4.2, as it was originally designed for 4.4.2 on Samsung and similar related kernel units. I've used it on my Samsung S4, and it required being on a pretty up to date 4.4.2 build. Wouldn't work on 4.3. But it may be different on the Asus.
I saw a mention off battery drain on 4.4.2 but without details. I'll continue looking. For now I've charged then powered off the tablet. No time to set it up tonight anyway. Seems like a very nice unit though.
Thanks for your reply!
Marc

Frankenscript said:
Thanks. I've used Carbon and believed it requires root, too. I'm a bit surprised that Towelroot wouldn't work on 4.4.2, as it was originally designed for 4.4.2 on Samsung and similar related kernel units. I've used it on my Samsung S4, and it required being on a pretty up to date 4.4.2 build. Wouldn't work on 4.3. But it may be different on the Asus.
I saw a mention off battery drain on 4.4.2 but without details. I'll continue looking. For now I've charged then powered off the tablet. No time to set it up tonight anyway. Seems like a very nice unit though.
Thanks for your reply!
Marc
Click to expand...
Click to collapse
Yeah, from what I understand, towelroot worked on the galaxy s4 (my current awesome phone) because the exploit wasn't patched at that time for the phone, but sadly Asus patched it as for the 4.4.2 drain, Netflix seems to be one of the couple of apps that is really draining power. Not really sure about it, but I'm probably not going to update until the next update is released.

royredman said:
Yeah, from what I understand, towelroot worked on the galaxy s4 (my current awesome phone) because the exploit wasn't patched at that time for the phone, but sadly Asus patched it as for the 4.4.2 drain, Netflix seems to be one of the couple of apps that is really draining power. Not really sure about it, but I'm probably not going to update until the next update is released.
Click to expand...
Click to collapse
Thanks. I read up a bit and indeed see how they patched the exploit before the 4.4.2 build, so sadly no Towelroot in Kitkat for us, without unlocking the bootloader and voiding warranty.
Since I will be using the tablet just for kid use, 4.3 will be just fine for now. Which of the (US) firmwares is the best to flash? I'm having some trouble relating the build numbers listed to the "4.2.2 / 4.3 / 4.4.2 etc" nomenclature. I've been reviewing the Device Essential Material thread but I'm still learning the ropes on the Asus.
So as I understand it, I get the right one downloaded, unzip it (one level), put it in sdcard root directory, reboot, and it auto-applies. Is that correct? Then Towelroot,, presumably SuperSU, then I can freeze the update processes with TiBU or somesuch. IS there a good description of what to freeze to prevent further update notices?
Anything else I should know? I'm still catching up.
Marc
PS. Based on THIS POST it sounds like I want 10.26.1.18 . Do you agree?

Frankenscript said:
Thanks. I read up a bit and indeed see how they patched the exploit before the 4.4.2 build, so sadly no Towelroot in Kitkat for us, without unlocking the bootloader and voiding warranty.
Since I will be using the tablet just for kid use, 4.3 will be just fine for now. Which of the (US) firmwares is the best to flash? I'm having some trouble relating the build numbers listed to the "4.2.2 / 4.3 / 4.4.2 etc" nomenclature. I've been reviewing the Device Essential Material thread but I'm still learning the ropes on the Asus.
So as I understand it, I get the right one downloaded, unzip it (one level), put it in sdcard root directory, reboot, and it auto-applies. Is that correct? Then Towelroot,, presumably SuperSU, then I can freeze the update processes with TiBU or somesuch. IS there a good description of what to freeze to prevent further update notices?
Anything else I should know? I'm still catching up.
Marc
PS. Based on THIS POST it sounds like I want 10.26.1.18 . Do you agree?
Click to expand...
Click to collapse
You can use any on. I just used the one that was on my tablets before (which was US). 10.26.1.18 is the 4.3 file to grab. Yup, unzip once and put it on the sd root file. For me, when I rebooted it, it let me know that there was a downloaded update detected (NOT the normal "click this button to download the system update")(be really careful about that one). Once I tapped the detected update file, it showed me it was the 10.26.1.18 file and I told it to install it.
If you want to see what to freeze, go into the towelroot thread in the Q&A section and look for my posts on the last page or so. I was asking exactly the same thing and they answered it all for me. Good luck and let me know if it goes well!!

Frankenscript said:
Thanks. I read up a bit and indeed see how they patched the exploit before the 4.4.2 build, so sadly no Towelroot in Kitkat for us, without unlocking the bootloader and voiding warranty.
Since I will be using the tablet just for kid use, 4.3 will be just fine for now. Which of the (US) firmwares is the best to flash? I'm having some trouble relating the build numbers listed to the "4.2.2 / 4.3 / 4.4.2 etc" nomenclature. I've been reviewing the Device Essential Material thread but I'm still learning the ropes on the Asus.
So as I understand it, I get the right one downloaded, unzip it (one level), put it in sdcard root directory, reboot, and it auto-applies. Is that correct? Then Towelroot,, presumably SuperSU, then I can freeze the update processes with TiBU or somesuch. IS there a good description of what to freeze to prevent further update notices?
Anything else I should know? I'm still catching up.
Marc
PS. Based on THIS POST it sounds like I want 10.26.1.18 . Do you agree?
Click to expand...
Click to collapse
You got it.
The .18 firmware is the JB 4.3. But stick to your SKU (US, WW - whatever it is now).
Once rooted freeze DMClient and CMClient and you won't be bothered with OTA updates.

Thanks! It's all done.
For anyone who reads this and needs to do the same thing, it was super easy. Just plugged the new Tab into the PC via USB, opened up to "Internal Storage", copied the UL-K00C-US-10.26.1.18-user.zip file over there, and rebooted. It auto-applied, rebooted again. Eventually I had to delete the .zip file from the internal storage, because on each reboot it would notice it and spend time figuring out if it had new updates or not.
Then Towelroot, SuperSU, and used App Quarantine-Root to freeze DMClient and CMClient. Rebooted again and no more update waiting for download messages.
I'm good to go!

royredman said:
Hi, before giving my opinion, I would suggest you to look through the forum while you are here. That said, I have some opinions against updating to 4.4.2. The main reason is that there are some battery issues on that boot loader for some unknown reason. Also, there is no root exploit available for the 4.4.2 version without having to unlock the boot loader. I was told that 4.3 was the best to stay on right now if you can.I just recently got my tablet too from that same deal. On 4.3 there is a easy root exploit called towelroot available, so you can root without unlocking.
---------- Post added at 01:48 AM ---------- Previous post was at 01:48 AM ----------
I also believe that carbon needs root for using it. If you have any questions, feel free to ask!!
Click to expand...
Click to collapse
First, i can confirm battery issues with 4.4.2. Android sometimes does not go to deepsleep (even if there are no addition apps installed, it seems a general problem). If i charge the tablet to 100% and go to bed, on the next morning i can be glad, if i have 30% battery left. Not always, but every 2.nd or 3rd night.
Second, a little question. Becauce of this "bug" i'd like to root my tablet and use a custom rom. I would like to use this method "http://forum.xda-developers.com/showthread.php?t=2604462 <- [MOD] JB 4.3+ | TF701T | Flashable Root Method v2 | Asus Stock 10.26.1.7/18
My first problem is the unlock app from asus. On the support site a text says: "1. Only suitable for Android4.2 Jelly Bean OS version" . But, according to most of the threads here, i should also work with 4.4.2??
The second question is, if the root method i just linked, works without any problems with the last asus update 4.4.2?
Using the tablet with this battery issue is horrible.
Thanks!

Hypothetix said:
First, i can confirm battery issues with 4.4.2. Android sometimes does not go to deepsleep (even if there are no addition apps installed, it seems a general problem). If i charge the tablet to 100% and go to bed, on the next morning i can be glad, if i have 30% battery left. Not always, but every 2.nd or 3rd night.
Second, a little question. Becauce of this "bug" i'd like to root my tablet and use a custom rom. I would like to use this method "http://forum.xda-developers.com/showthread.php?t=2604462 <- [MOD] JB 4.3+ | TF701T | Flashable Root Method v2 | Asus Stock 10.26.1.7/18
My first problem is the unlock app from asus. On the support site a text says: "1. Only suitable for Android4.2 Jelly Bean OS version" . But, according to most of the threads here, i should also work with 4.4.2??
The second question is, if the root method i just linked, works without any problems with the last asus update 4.4.2?
Using the tablet with this battery issue is horrible.
Thanks!
Click to expand...
Click to collapse
Reg. Battery drain: Did you run Netflix on those nights you had that severe battery drain?
Reg. Unlock: The tool should work on any fimware version. Just run it. Worst case scenario: It won't work.
Reg. Root: Why would you root the stock rom if you want to replace it with a custom rom anyway?
To install a custom rom you need to:
A) unlock the bootloader
B) flash a custom recovery in fastboot
C) create a nandroid of your stock rom in recovery
D) wipe cache, Dalvik and data using your custom recovery
E) flash the custom rom (which is rooted anyway).
For general reference on flashing custom roms to the Transformer, check out my guide here:
http://forum.xda-developers.com/showthread.php?t=2688891
NOTE: This is a guide for the TF700!! The general instructions on flashing, fastboot commands etc still apply. The specifics like recovery and version, bootloader and version etc DO NOT.
For TF701 specific instructions check out the OP of the CROMi-X thread in the Development section for the TF701 here on XDA.

berndblb said:
Reg. Battery drain: Did you run Netflix on those nights you had that severe battery drain?
Reg. Unlock: The tool should work on any fimware version. Just run it. Worst case scenario: It won't work.
Reg. Root: Why would you root the stock rom if you want to replace it with a custom rom anyway?
Click to expand...
Click to collapse
Thanks. Yes i know. I like the look the stock rom has. Therefore i first wanted to test, if i can stop the battery drain, if i use apps like greenify to send a few apps to deepsleep.
I rooted yesterday and tested it. Unfortunately, even with greenify i have the same problem. Every time i use the keydock, the tablet does not go into deepsleep mode. I checked with wakeup detector if i can find out which app is bad, but there are no apps which wake up the tablet more that 5 or 6 times.... If i use the tablet without the dock i dont have this problem (or just when i use netflix and dont reboot after usage)
Now i will try a custom rom....maybe it helps.
Thanks !

blu advance 5.0 hd compatible?

Hey so do you think the blu advance 5.0 hd will be compatible with the work being done on the R1 hd? I would really like to jump on this hype train with my similar but slightly less powerful phone.
I am hoping that I will be able to install a custom rom like R1 users. I also want to root my phone to disable google services in the meantime.

xda123455 said:
Hey so do you think the blu advance 5.0 hd will be compatible with the work being done on the R1 hd? I would really like to jump on this hype train with my similar but slightly less powerful phone.
I am hoping that I will be able to install a custom rom like R1 users. I also want to root my phone to disable google services in the meantime.
Click to expand...
Click to collapse
That phone is based on the 6580 SoC, the R1 uses a 6735. There is a site that lists some roms for blu products that may help, I don't know how reliable they are, I have never used them, but if you want to check it out...
http://www.blu-dev.com

kal250 said:
That phone is based on the 6580 SoC, the R1 uses a 6735. There is a site that lists some roms for blu products that may help, I don't know how reliable they are, I have never used them, but if you want to check it out...
http://www.blu-dev.com
Click to expand...
Click to collapse
Thanks I checked out the site and it seems like there is no blue advance 5.0 roms and no forum activity =/

xda123455 said:
Thanks I checked out the site and it seems like there is no blue advance 5.0 roms and no forum activity =/
Click to expand...
Click to collapse
If your wanting to root it, I'm hearing Kingroot is working, never used it though, so I can't say if it works or if it's safe??

kal250 said:
If your wanting to root it, I'm hearing Kingroot is working, never used it though, so I can't say if it works or if it's safe??
Click to expand...
Click to collapse
I've tried Kingroot, Kingo Root and Frama root. All with no luck.

devanttrio said:
I've tried Kingroot, Kingo Root and Frama root. All with no luck.
Click to expand...
Click to collapse
Did you use the desktop versions? Those have higher success rates. I tried rooting an HTC that way and it worked flawlessly even when the apk didn't.

Autolounge said:
Did you use the desktop versions? Those have higher success rates. I tried rooting an HTC that way and it worked flawlessly even when the apk didn't.
Click to expand...
Click to collapse
I did.
I also tried the apps, of the ones that have apps.

devanttrio said:
I did.
I also tried the apps, of the ones that have apps.
Click to expand...
Click to collapse
You're going to have to do it manually.

no go on kingo
I'm in the same boat. I've got 20 of these BLU Advance 5.0 HD devices and I need to root them to gain access to the VirtualSensor app to emulate a gyroscope. I've tried Kingo and Mobogenie (barf-boo-hisssss). I'm wondering if kingo isn't working on these since they have Marshmallow. I read somewhere they originally shipped with Lollipop.
Did you get anywhere Devanttrio??

trc117 said:
I'm in the same boat. I've got 20 of these BLU Advance 5.0 HD devices and I need to root them to gain access to the VirtualSensor app to emulate a gyroscope. I've tried Kingo and Mobogenie (barf-boo-hisssss). I'm wondering if kingo isn't working on these since they have Marshmallow. I read somewhere they originally shipped with Lollipop.
Did you get anywhere Devanttrio??
Click to expand...
Click to collapse
consider yourself blessed my friend, i'd like to root mine just to get marshmallow.... i have lollipop and checked for updates and says i'm up to date, i can only install 1 app at a time because there is no room on the internal storage, i have to move every app to sd card and then clean cache for each and every app i want.. never recommending blu to anyone

trc117 said:
I'm in the same boat. I've got 20 of these BLU Advance 5.0 HD devices and I need to root them to gain access to the VirtualSensor app to emulate a gyroscope. I've tried Kingo and Mobogenie (barf-boo-hisssss). I'm wondering if kingo isn't working on these since they have Marshmallow. I read somewhere they originally shipped with Lollipop.
Did you get anywhere Devanttrio??
Click to expand...
Click to collapse
I was able to root mine successfully the long way.... had to obtain a dump of the boot.img / recovery.img using software that I'm not sure of the policy of discussion on here at XDA - compile TWRP - unlock bootloader - fastboot boot the compiled recovery - flash SuperSU to get patched boot.img (kitchen was being dumb and systemless root didn't want to work) - Flash SuperSU in system mode - Convert SuperSU.apk to system app so it doesn't get removed every reboot. I can post my compiled TWRP when I'm back at my office or grab it from my repository that I'm trying to establish - https://bluroms.info . Sorry for the design mess / lack of much there at moment haven't had much free time lately in process of cleaning up the device kernel sources to build from source... its sort of ... messy in there...... can post on github if anyone wants in

zjr8 said:
I was able to root mine successfully the long way.... had to obtain a dump of the boot.img / recovery.img using software that I'm not sure of the policy of discussion on here at XDA - compile TWRP - unlock bootloader - fastboot boot the compiled recovery - flash SuperSU to get patched boot.img (kitchen was being dumb and systemless root didn't want to work) - Flash SuperSU in system mode - Convert SuperSU.apk to system app so it doesn't get removed every reboot. I can post my compiled TWRP when I'm back at my office or grab it from my repository that I'm trying to establish - https://bluroms.info . Sorry for the design mess / lack of much there at moment haven't had much free time lately in process of cleaning up the device kernel sources to build from source... its sort of ... messy in there...... can post on github if anyone wants in
Click to expand...
Click to collapse
I've been trying to root a Blu Advance 5.0 HD for a while now and stumbled on this post. I visited your site but am not sure what a 'Scatter File' is, or in what order I need to do things in order to get root.
If you could provide a little more detailed info that would be very much appreciated.
Thanks!
rAy
EDIT: Sorry, to clarify I tried all of the other PC and APK rooting solutions but was able to unlock the bootloader using ADB. I guess I'm just looking for the proper way to root and add TWRP. Thanks!

ray2jerry said:
I've been trying to root a Blu Advance 5.0 HD for a while now and stumbled on this post. I visited your site but am not sure what a 'Scatter File' is, or in what order I need to do things in order to get root.
If you could provide a little more detailed info that would be very much appreciated.
Thanks!
rAy
EDIT: Sorry, to clarify I tried all of the other PC and APK rooting solutions but was able to unlock the bootloader using ADB. I guess I'm just looking for the proper way to root and add TWRP. Thanks!
Click to expand...
Click to collapse
I found a option in developer settings that is "Enable OEM unlocking" and it makes it so you can unlock the bootloader from fastboot, if you do adb reboot-bootloader and then fastboot unlock it should undo the bootloader for you

zjr8 said:
I was able to root mine successfully the long way.... had to obtain a dump of the boot.img / recovery.img using software that I'm not sure of the policy of discussion on here at XDA - compile TWRP - unlock bootloader - fastboot boot the compiled recovery - flash SuperSU to get patched boot.img (kitchen was being dumb and systemless root didn't want to work) - Flash SuperSU in system mode - Convert SuperSU.apk to system app so it doesn't get removed every reboot. I can post my compiled TWRP when I'm back at my office or grab it from my repository that I'm trying to establish - Sorry for the design mess / lack of much there at moment haven't had much free time lately in process of cleaning up the device kernel sources to build from source... its sort of ... messy in there...... can post on github if anyone wants in
Click to expand...
Click to collapse
Like the others said, I would really appreciate if you could give an explanation or tutorial on how to use these files that you uploaded to root the phone. I'm willing to donate some money if required. I only know basic technical stuff haha.

CreativiTimothy said:
Like the others said, I would really appreciate if you could give an explanation or tutorial on how to use these files that you uploaded to root the phone. I'm willing to donate some money if required. I only know basic technical stuff haha.
Click to expand...
Click to collapse
I too am trying to root this device, and am unclear on a few of the steps here. I actually found your site with the recovery and boot images independently, really appreciated! I am at the point where I just need to patch the boot image, though I am not sure how to do this. If you could help me out with this step I might be able to put together some sort of list of steps to get through the whole process if you don't have the time.
Any help would be appreciated, thanks!

Question's Regarding 5.3.2

So every post seems to address only 5.3.1. I can't find a SINGLE thing about rooting the 2015 5th gen Fire that runs 5.3.2. Am I the only person not able to find answers? King Root cant unlock, I can't figure out a solution and I can't stand the interface.
Purchased this for my son and he won't even use it. And He's 5. If I can't load CM or another custom rom soon I'm gonna smash it. At least I will feel better afterwards! I HATE that companies do this. Please help!

you can downgrade and then you can root

Ubuntu_noobi said:
So every post seems to address only 5.3.1. I can't find a SINGLE thing about rooting the 2015 5th gen Fire that runs 5.3.2. Am I the only person not able to find answers? King Root cant unlock, I can't figure out a solution and I can't stand the interface.
Purchased this for my son and he won't even use it. And He's 5. If I can't load CM or another custom rom soon I'm gonna smash it. At least I will feel better afterwards! I HATE that companies do this. Please help!
Click to expand...
Click to collapse
Fair bit of info on 5.3.2; sorry you couldn't find it. As for rooting simply roll back to 5.3.1 and then use the SuperTool to root (do not use Kingroot directly). See forum index in General thread for additional detail.

Davey126 said:
Fair bit of info on 5.3.2; sorry you couldn't find it. As for rooting simply roll back to 5.3.1 and then use the SuperTool to root (do not use Kingroot directly). See forum index in General thread for additional detail.
Click to expand...
Click to collapse
I've tried moving the factory update after downloading it to the DCIM, when trying to update, it states that you can't update because it's an older version of the os. Is it required to side load?

Ubuntu_noobi said:
I've tried moving the factory update after downloading it to the DCIM, when trying to update, it states that you can't update because it's an older version of the os.
Click to expand...
Click to collapse
Wrong procedure. See forum index for details, in particular the first two posts in this thread.
Ubuntu_noobi said:
Is it required to side load?
Click to expand...
Click to collapse
Yes.

So glad I found this post. Researching the same thing. Trying it out now
Sent from my iPhone using Tapatalk

yungskeeme01 said:
So glad I found this post. Researching the same thing. Trying it out now
Click to expand...
Click to collapse
Any new info to share? I still haven't been able to figure it out

Ubuntu_noobi said:
Any new info to share? I still haven't been able to figure it out
Click to expand...
Click to collapse
What exactly are you trying to "figure out"? Responded a few days ago with downgrade/rollback links which includes a step-by-step video.

Ubuntu_noobi said:
Any new info to share? I still haven't been able to figure it out
Click to expand...
Click to collapse
I downgraded to 5.3.1. Rooted the fire and am now running CM 12.1. Very smooth!. Took me a awhile to get since I have a Mac but got it working. Used Rootjunky's YouTube video on how to restore. That's how I downgraded. Then used his Supertool for Mac and rooted. I then installed Flashfire and put CM12 on the tablet.
Sent from my iPhone using Tapatalk

Ubuntu_noobi said:
Any new info to share? I still haven't been able to figure it out
Click to expand...
Click to collapse
Davey126 already answered it here.
Davey126 said:
Fair bit of info on 5.3.2; sorry you couldn't find it. As for rooting simply roll back to 5.3.1 and then use the SuperTool to root (do not use Kingroot directly). See forum index in General thread for additional detail.
Click to expand...
Click to collapse
I also bought the Fire a few days ago and I dealt with 5.3.2 by first using "adb sideload" to go to 5.3.1 and then rooting it.
I had problems with rooting via the SuperTool, as it used an old KingRoot version and after several rooting attempts when it finally succeeded, the SuperTool had problems removing KingRoot and replacing it with SuperSu (this error made it lose root somehow). Same problem occurred when I used the SuperTool but with the newest KingRoot, so instead of using the SuperTool I used newest KingRoot directly and decided not to replace it with SuperSu.
All is fine now, lockscreen ads are gone, AdAway is installed and OTA updates blocked.

amerkiller1995 said:
I used KingRoot directly and decided not to replace it with SuperSu.
Click to expand...
Click to collapse
FYI - recognize KingRoot is a shady tool whose authors have uncertain motivations. Even after rooting it continues to send/receive information without apparent reason. One has to question any app that is offered for free and aggressively resists being uninstalled. Given the unknowns I would reconsider the decision to retain KingRoot/KingUser.

amerkiller1995 said:
Davey126 already answered it here.
I also bought the Fire a few days ago and I dealt with 5.3.2 by first using "adb sideload" to go to 5.3.1 and then rooting it.
I had problems with rooting via the SuperTool, as it used an old KingRoot version and after several rooting attempts when it finally succeeded, the SuperTool had problems removing KingRoot and replacing it with SuperSu (this error made it lose root somehow). Same problem occurred when I used the SuperTool but with the newest KingRoot, so instead of using the SuperTool I used newest KingRoot directly and decided not to replace it with SuperSu.
All is fine now, lockscreen ads are gone, AdAway is installed and OTA updates blocked.
Click to expand...
Click to collapse
I had the issue with King Root as well. What I did was download a newer version and replaced in the SuperTool folder
Sent from my iPhone using Tapatalk

Davey126 said:
FYI - recognize KingRoot is a shady tool whose authors have uncertain motivations. Even after rooting it continues to send/receive information without apparent reason. One has to question any app that is offered for free and aggressively resists being uninstalled. Given the unknowns I would reconsider the decision to retain KingRoot/KingUser.
Click to expand...
Click to collapse
Yes, it certainly gives that vibe. However my Fire is just a portable anime player, it's offline and there's nothing on it except anime, so I'll let it be.
BTW KingRoot flagged AdAway as a "risk"
yungskeeme01 said:
I had the issue with King Root as well. What I did was download a newer version and replaced in the SuperTool folder
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I've done that, it's in the post you quoted. Still, in the replacing step, the SuperTool deletes KingRoot, but then fails to put SuperSu in its place, it prints some errors to the console like ERR_WRITE or something.

amerkiller1995 said:
Yes, it certainly gives that vibe. However my Fire is just a portable anime player, it's offline and there's nothing on it except anime, so I'll let it be.
BTW KingRoot flagged AdAway as a "risk"
I've done that, it's in the post you quoted. Still, in the replacing step, the SuperTool deletes KingRoot, but then fails to put SuperSu in its place, it prints some errors to the console like ERR_WRITE or something.
Click to expand...
Click to collapse
Sorry if I misread it. I used the version included and KingRoot so I replaced it in Supertool and re-rooted using SuperTool and it removed it no issues. Whatever though, it got rooted one way or another!
Sent from my iPhone using Tapatalk

Awesome I will try again tonight

Solved!!! Finally!!!
Ubuntu_noobi said:
So every post seems to address only 5.3.1. I can't find a SINGLE thing about rooting the 2015 5th gen Fire that runs 5.3.2. Am I the only person not able to find answers? King Root cant unlock, I can't figure out a solution and I can't stand the interface.
Purchased this for my son and he won't even use it. And He's 5. If I can't load CM or another custom rom soon I'm gonna smash it. At least I will feel better afterwards! I HATE that companies do this. Please help!
Click to expand...
Click to collapse
TL;DR: THERE IS NO "One click" OPTION THAT WORKS. I DOWNLOADED ALL OF THEM. IVE TRIED EVERY DAMN ONE OF THEM. STOP SEARCHING. You MUST side load the system with the code necessary to make it capable to root. Downgrading to 5.3.1 was the secret, instead of trying to root on 5.3.2. I made a glossary of the confusing terminology, made a step by step walk through for noobs
SO, having felt encouraged by the response by people on this forum, last night I decided it was worth another try.
I finally figured out what I was missing. IF YOU CURRENTLY HAVE FIREOS VERSION 5.3.1, YOU MUST ROLL IT BACK THRU SIDE LOADING see here: SIDELOAD TUTORIAL
I tried to load straight onto the system disk and caused all kinds of problems. Once I followed that step by step, which TBH, was a lot of pausing and rewinding. I am not familiar with many terms so I made this...
Android Common Terms:
Boot: A sequence of commands written into the underlying software that tells the device what order to operate in
Bootloader: See Previous (this is the sequence I referenced previously)
Locked Bootloader: Think of trying to edit a PDF you did not create... Exactly.
ADB Fastboot: THIS IS A PROGRAM... NOT A FUNCTION. I still get this confused, thinking that it is a quicker version of the boot sequence... IT IS NOT. ADB Fastboot is a program that gives access to the base software code making it reachable to use certain sections of to "edit the PDF".
Custom Recovery: It is the new version of Windows 10 you were updating to when your crappy laptop you JUST bought came with Windows 8.1. Essentially.
Root: Remember the PDF? Well, if you work somewhere that has Adobe Reader, and you see the window on the right pop up with the ability to login to Adobe Online or whatever? Well, rooting is having login credentials to ACTUALLY edit that damn PDF.
Flash: Download from the internet, and install on your hard drive, or SD Card. It actually means you erase whatever is there completely first, then install. It's two steps, which is why they don't just call it installing... I think.
Partition: Have you ever worked in an office with cubicles? Exactly. A partition is a wall that you put up to segregate files, or programs, or whatever.
SuperTool: Based in your computer. RootJunky Went through and basically made one tool that has everything you need for rooting. PROBLEM IS THAT HE TELLS YOU TO DOWNLOAD ADB FASTBOOT AND DRIVERS AND A BUNCH OF STUFF, then says, or you can just download the SuperTool, which means, I now HAVE TWO OF ALL OF IT, and then I spend the next three hours trying to figure out if its the "custom rom that I sideload into the TWRP, or if the Flashed version of the bootloader gets added to the recovery image, but not before the drivers are flashed into the fastboot."
While this doesn't cover a lot, I hope that people in this community understand what it is like for someone unversed in the lingo to grasp exactly what is going on. I don't think we should speak like idiots and elementary students, but I also think we lose a ton of people that may have something to offer one day because they got frustrated with the terminology and gave up. Luckily, I stuck it out and gave it one last chance and I got it.
So, once I downgraded from 5.3.2 to 5.3.1, I went about trying to root the device, which was also a little confusing.
Step 1: Downgrade if you have 5.3.2 to 5.3.1
Step 2: Enable ADB and Debug in the Settings
Step 3: Hold down the Power and Volume Down button, release the power button once the device starts to reboot and a menu will popup
Step 4: Use the volume keys to access the first selection. This is how you access the "sideloading".
Step 5: Open the SuperTool, click on the batch file which should say Auto... because calling it SuperTool would be confusing
Step 6: follow the super easy instructions. Honestly.
It will walk you through the process and get you to the part about Kingroot and FlashFire and eventually root the device.
I honestly hope this helps someone. God knows it would have saved me from spending approximately 30 hours trying to figure this out.

[ROM] [Stock] J320A/J320AZ/J320AG deodex'd

Today i bring you the very first rom for our device.
It's only stock, but the installer includes enough options to keep us happy for a while.
The core installation includes a stripped down system menu with Google play and contacts. I also added, by default, the WiFi fix and hotspot mod. The rest of what you install is your choice.
Aroma options:
Choose which J320 you own
Debloat (fully customizable)
Deknox
Install root
Install busybox
Install Init.d
Install Xposed
Bugs:
None
If you find any let me know, but if you do not wipe, please don't even report bugs.
Link:
Download
Installation:
Flashfire
Enjoy
-D

This uses the same base files for each room, AQG1. So even tho the highest firmware for J320AG is only AQB1 you still get the July security update (minus the new sboot)
All devices are interchangable for me, on Cricket. Depending on your carrier maybe they'll all work for you too.

I have AT&T Samsung Galaxy Express Prime GoPhone, J320A. Owned it for one week. It has been carrier-unlocked. I'm now using T-Mobile SIM. Seems to work OK. Only issue I can find is where the SIM status page does not show my phone number.
I would appreciate pointers or maybe a place to look for installation steps. I assume I'll to need to root via Kingroot then replace with SuperSU (if possible). Then install FlashFire.​ I have rooted and installed ROMs on other devices (Galaxy Exhibit, 2012 Nexus tablet, Moto G), but seemingly devices are more locked-down these days. I understand that TWRP is not available for this device and likely will not be.
Last year, I bought a couple of inexpensive T-Mobile phones and "rooted" them with KingRoot which is still installed on those phones. (Not really thrilled about that.) I put rooted in quotes because it doesn't quite behave like a fully-rooted phone, IMO. I'm not very expert in these things, but I know how to follow steps and have used ODIN, TWRP, et cetera.
I'm leery of working with these more locked-down phones. Am I being paranoid and/or incorrect about these matters?
BTW, thanks for the ROM! I'm surprised there aren't more replies.
Maybe this phone is not as popular as I think it should be. Maybe it's too low-spec for the tech-savvy crowd. I got mine for just $64 at Walmart online, but they've since raised the price to $79. Seems like a good deal, even at that price.
I paid $15 to carrier-unlock it. I had to flash firmware (modem file?) before unlocking, then flash another file (restored modem?) after unlocking. I was following emailed instructions after the initial unlock procedure failed.

Here's the root thread
https://forum.xda-developers.com/galaxy-j3-2016/how-to/root-samsung-sm-j320a-galaxy-express-t3573628
There's a xposed module that does just that, never tried it tho, and of course it's not permanent.
https://forum.xda-developers.com/ga...pp-sim-changer-change-registered-sim-t2106490
I definitely like the phone and yeah, it's a good price.
Being locked does hurt it tho. No easy recovery and no roms from source. The only thing we might get will be ported. And with no kernel, porting is a pain to track down problems... but i like a challenge

My J3 was unlocked out of the box? Still don't quite get the different names for it though. Rooted with infixremix method and worked fi e until its download caused the dialer to crash whenever it was opened. Still trying to sort out the mess I made of this one.

original stock
hey do any of you guys know where I can get the original firmware to restore this device? mine is the S/W: j320aueu1ape9
on the box it says j320x UD

Odin files are posted here
https://forum.xda-developers.com/galaxy-j3-2016/how-to/root-samsung-sm-j320a-galaxy-express-t3573628

How is this ROM working out?
Can anyone -- or DamienMc, the creator -- post a review of how this ROM is working out? Brief or long; any type of review would be appreciated.
I'm thinking of trying this ROM and I haven't rooted my phone yet.
Although I did unlock the carrier via a paid unlocker site. I'm using it on T-Mobile with no apparent issues. My phone is stock, of course, except for being carrier-unlocked. …Several questions, if I might:
Are those "extra" AT&T and Samsung accounts present? (ref. screenshot)
Are Samsung factory (i.e.: theme-able) dialer, messaging, and contacts apps installed?
Is it still possible to theme the UI with the Samsung theme installer?
Finally, which bloat icons have been purged? (ref. screenshot) I realize one's idea of bloat may vary from individual.
Any feedback or commentary is welcome. Thank you for your consideration.

could it work on J320H?
i know it's for 320A/Az but i want to try it

danny8 said:
Can anyone -- or DamienMc, the creator -- post a review of how this ROM is working out? Brief or long; any type of review would be appreciated.
Any feedback or commentary is welcome. Thank you for your consideration.
Click to expand...
Click to collapse
I'm not going to review it (someone else can)
But I used it heavily before I started work on something new.
It's as stable as stock... cause it is stock Nothing tweaked just the few add-ons to let you tweak it easier.
About the bloat.
I did notice I should have left Samsung account (and maybe billing) with the standard install. Because you can't use the theme store without them. But they're in 'bloat'.
You can always install all the debloat options and have 100% deodex stock and edit to your liking.
hamzaeid said:
could it work on J320H?
i know it's for 320A/Az but i want to try it
Click to expand...
Click to collapse
Sorry bud, different chipset

How do we flash this to our device mainly because twrp and cwm ain't a thing for the j320a. Also I'm using kingroot and I cannot go to su I've tried also flashify does not work either does flashfire how would you go about rooting with su cause I've tried the mrw method and contanstaly it would pop up kinguser has stopped working so do you have another method of rooting the J320A. I just followed the first post about rooting it.

iiFir3z said:
How do we flash this to our device mainly because twrp and cwm ain't a thing for the j320a. Also I'm using kingroot and I cannot go to su I've tried also flashify does not work either does flashfire how would you go about rooting with su cause I've tried the mrw method and contanstaly it would pop up kinguser has stopped working so do you have another method of rooting the J320A. I just followed the first post about rooting it.
Click to expand...
Click to collapse
I just rooted my phone with Kingroot and used the mrw method to remove it well keeping my root. after got Su in my terminal emulator, I deleted the kingroot apk not the app itself. then just installed SuperSu thru my play store and been working just fine for me.

gus8347 said:
I just rooted my phone with Kingroot and used the mrw method to remove it well keeping my root. after got Su in my terminal emulator, I deleted the kingroot apk not the app itself. then just installed SuperSu thru my play store and been working just fine for me.
Click to expand...
Click to collapse
I've tried that it would just constantly spam me with kinguser has stopped working and that message would constantly spam me so I'm not ever using that way again.

iiFir3z said:
I've tried that it would just constantly spam me with kinguser has stopped working and that message would constantly spam me so I'm not ever using that way again.
Click to expand...
Click to collapse
Yeah i guess i never had kinguser app or apk i had to delete. Was just kingroot apk that i downloaded and used.

iiFir3z said:
I've tried that it would just constantly spam me with kinguser has stopped working and that message would constantly spam me so I'm not ever using that way again.
Click to expand...
Click to collapse
After mrc and kinguser crashes you should have supersu. You need to run that first, let it update the files and then reboot.
If su doesn't even get installed, have the apk ready and install.
Another thing you should make sure your really rooted, reboot after king and recheck.
Also what versions of kingroot and mrw are you using?

iiFir3z said:
I'm using Kingroot and I cannot go to SU. I've tried also Flashify does not work. Either does Flashfire. How would you go about rooting with SU…
Click to expand...
Click to collapse
I followed the rooting thread OP directions carefully and had many problems. My initial Kingroot was really ugly and heated the phone. I then attempted to use SuperSU-Me Pro (paid version). It was never able to complete, even after several tries. I struggled using various techniques over many hours. (I did have root with Kingroot.) Nothing would remove Kingroot 5.0.5, and as you probably know, Kingroot won't allow for many apps such as Flashfire. Very frustrating. I probably shortened the life of my phone and battery with all the crap I tried. Many pulls of my battery were needed.
I finally wrested control from Kingroot by uninstalling version 5.0.5 and installing Kingroot 4.5 instead. Then SuperSU-Me Pro did its work. Had I used Kingroot 4.5 from the outset, would things would have gone better? I don't know. The rooting process for this phone is a one-way trip with a dubious outcome. I know the Express Prime is not costly, but if you're risk adverse think twice before trying to root. I suppose you can undo the whole thing, but I haven't tried and likely will not.
Despite the problems I had, I believe using SuperSU-Me Pro was worth the cost and ultimately saved time. I'm glad I rooted my phone, but -- damn, it was a lot of effort compared to previous phones and my tablet.
I have not tried the de-odexed ROM posted in this thread's OP, but it's on my to-do list. I'm kind of afraid of messing with my phone for the time being. I'll post a review if and when I try it out.
For what it's worth, I wasn't able to get my built-in flashlight toggle to work. I ran the fix script via flashfire with no success. Update: Fixed after installing Busybox. Thanks, DamienMc!

danny8 said:
I wasn't able to get my built-in flashlight toggle to work. I ran the fix script via flashfire with no success.
Click to expand...
Click to collapse
You need busybox installed as well

Busybox
Oh, you're very good. It works!

Help! After flashing the rom, it does not let me log in to the google account and I can not exit that screen, the message it displays is as follows:

danny8 said:
I have AT&T Samsung Galaxy Express Prime GoPhone, J320A. Owned it for one week. It has been carrier-unlocked. I'm now using T-Mobile SIM. Seems to work OK. Only issue I can find is where the SIM status page does not show my phone number.
I would appreciate pointers or maybe a place to look for installation steps. I assume I'll to need to root via Kingroot then replace with SuperSU (if possible). Then install FlashFire.​ I have rooted and installed ROMs on other devices (Galaxy Exhibit, 2012 Nexus tablet, Moto G), but seemingly devices are more locked-down these days. I understand that TWRP is not available for this device and likely will not be.
Last year, I bought a couple of inexpensive T-Mobile phones and "rooted" them with KingRoot which is still installed on those phones. (Not really thrilled about that.) I put rooted in quotes because it doesn't quite behave like a fully-rooted phone, IMO. I'm not very expert in these things, but I know how to follow steps and have used ODIN, TWRP, et cetera.
I'm leery of working with these more locked-down phones. Am I being paranoid and/or incorrect about these matters?
BTW, thanks for the ROM! I'm surprised there aren't more replies.
Maybe this phone is not as popular as I think it should be. Maybe it's too low-spec for the tech-savvy crowd. I got mine for just $64 at Walmart online, but they've since raised the price to $79. Seems like a good deal, even at that price.
I paid $15 to carrier-unlock it. I had to flash firmware (modem file?) before unlocking, then flash another file (restored modem?) after unlocking. I was following emailed instructions after the initial unlock procedure failed.
Click to expand...
Click to collapse
Could you please tell the name of the service/company you used to carrier-unlock it ? (I'm in the same situation) Thanks! @danny8