Database Users

[ROOT]HowTo

The Xperia X10 Rooting Toolkit also works flawlessy with the Samsung Galaxy Note and gives you full root access (tested by myself)
Just follow the instructions to root/unroot the device here
http://forum.xda-developers.com/showthread.php?t=1319653

Confirmed working!

Since the ice cream sandwich is not out yet, what is the advantage of rooting it now?

clubtech said:
Confirmed working!
Click to expand...
Click to collapse
You are using AT&T and have the note,from wish retailer you buy yours?

please excuse my trivial question, but rooting the Note with the instructions you provided is it possible to install any kind of apk file?

finanziere said:
please excuse my trivial question, but rooting the Note with the instructions you provided is it possible to install any kind of apk file?
Click to expand...
Click to collapse
You don't need to root to install apks.

wonsanim said:
You are using AT&T and have the note,from wish retailer you buy yours?
Click to expand...
Click to collapse
eBay...
10chars

clubtech said:
eBay...
10chars
Click to expand...
Click to collapse
Thanks
is a little expencive on ebay

schölli said:
The Xperia X10 Rooting Toolkit also works flawlessy with the Samsung Galaxy Note and gives you full root access (tested by myself)
Just follow the instructions to root/unroot the device here
http://forum.xda-developers.com/showthread.php?t=1319653
Click to expand...
Click to collapse
could somebody tell me if this root method increase the binary counter??
thanks..

kersh said:
You don't need to root to install apks.
Click to expand...
Click to collapse
thanks, but I mean the non official apps or those that are cracked.
is it possible to install these without rooting the device?

m_adnan said:
could somebody tell me if this root method increase the binary counter??
thanks..
Click to expand...
Click to collapse
It won't
Sent from my GT-N7000 using xda premium

Worked for me! It was even easier than rooting an HTC Evo 4G. This thread, or at least the thread referenced in the first post, should be stickied in the Development sub-forum.

I am a Noob and I can Root my Note!
I had experience rooting a Milestone 2 with SuperOneClick and an unbranded Android Tablet with Z4Root. (Thanks to developers of these!)
Unfortunately, both these methods did not work on the Galaxy Note so I came here and found this thread.
Unfortunately, ADB drivers was an issue with the zergRush Exploit on first run. The easiest way to get around this is to install PDANet on Windows and have it install the drivers for you. No need to complete the whole installation, just watch when it's finished installing USB drivers and then when prompted to continue, just cancel. Then re-run the zergRush Exploit and it should do its magic (Again thanks to the developers who work on these!)
While I'm able to freeze some apps with ROM Toolbox, I'm unable to change boot animation or the battery icon. Would appreciate if anyone could help with this!

Rooting hav no relation to install official/crckd version of apk.
Rooting needed for those application which are needed to access your system data e.g backup etc
when you need to install these kinds of application (weather off/unoff) you needs Root.

The optional unrooting package works also perfectly (just for info)...
i have sent back my Galaxy Note to amazon just to wait for the white version of the Note.
This method won't increase your binary counter, so root and unroot it as often as you like
Never either had any problem at all after rooting it, so this method is also stable and won't crash your device in any way or crash any applications...

Root confirmed working here, superuser.apk doesn't have permissions set properly but still works, easy to fix, updates fine from market.

Awesome - confirmed working. This needs to be stickied... other websites are promoting netchips CWN kernel method instead of this MUCH simplier way.

For you noobs with a clean system (that means me!), get the following files:
Note I run a 64 bit windows box, get the 32 bit variants if necessary.
You need:
1) Latest version of Kies
www.samsung.com/ca/kies/index.html
download file for me was: Kies_2.0.3.11082_152_4.exe
2) Java:
www.oracle.com/technetwork/java/javase/downloads/index.html
Click on jdk and download. File for me: jdk-7u1-windows-x64.exe
3) android sdk:
developer.android.com/sdk/index.html
My file was: installer_r15-windows.exe
4) zergrush root script
http://forum.xda-developers.com/showthread.php?t=1312859
grab the zip file in that page i.e.
DooMLoRD_v1_UNROOTING.zip
and unzip it to your windows box.
Install 1, 2, 3 in that order.
Find the SDK Manager program in your sdk install directory, double click it, and download/update 'Android SDK Platform Tools'.
Note you can't run the sdk manager program from the command prompt, or it'll complain that directories are being locked.
Now follow the instructions on the zergrush page, i.e. do the 'before you begin' stuff.
Go to the directory where you unzipped the doomlord zip file, run the runme script from a command prompt,and that's it.
To test, download terminal monitor, run it, and do a 'su' then 'id' and see if it says you are root or not.
Good luck!
- Frank

sir can i ask a question?
after i install the cwm and i will make a nandroid back up before rooting the phone.
if i restore the unrooted back up. Will i go back to became un root again and go back to out of the box state?

will this work with the Korean version of the Note? thanks in advance.

[Q] Updating to 1.1 on touchnooter rooted touch

I have a Touch rooted with Touchnooter. My touch doesn't seem to want to update to 1.1 (I know doing so will kill GAPPS, but I'm okay with that). I've waited for the update to be pushed and I've also put the update file in my Nook directory. Is there something about Touchnooter that prevents the Touch from updating?

I haven't tried to update after using touchnooter, dont really know if it blocks nothing, OTA or prevents from updates, OTA or manullay, but you should restore a copy of your nook if you have it, or use nookrestore and then force a reset to also delete /data.
Or use adb to force restore
adb shell
echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt
reboot
Click to expand...
Click to collapse
and then reset normally and if it dosnt let you, force reset, force it shutting down your nook, then starting it up, and when the screen flickers press right and left bottom buttons, hold for 5+ seconds.
That will erase /system (restore) and /data (reset), and you should be able to update.

I do have a backup copy, but I was hoping I wouldn't have to do a restore to get the update. I mean, I'd really like to avoid that.
Have others been able to update their Touchnooter Touches to 1.1 without reverting?

kunchers said:
I do have a backup copy, but I was hoping I wouldn't have to do a restore to get the update. I mean, I'd really like to avoid that.
Have others been able to update their Touchnooter Touches to 1.1 without reverting?
Click to expand...
Click to collapse
Updating a TouchNootered NST have caused troubles in the past and is likely to do so with this update as well.
Even if it worked for other users it might not work for you as people do different things to their rooted NST.
I know it's a hassle, but you should really restore+reset your NST before updating if you want to avoid problems.

The OP's post has given me some hope as I do not wish to unroot/re-root-/update at this time, but have kept my NST's wireless off as I'm afraid of getting the update.
Am I to understand that a TouchNooter'd unit (1.6.24 on an NST1.0.1) will not get updated and there is nothing to fear?

TJay99 said:
Am I to understand that a TouchNooter'd unit (1.6.24 on an NST1.0.1) will not get updated and there is nothing to fear?
Click to expand...
Click to collapse
There's nothing in TN 1.6.24 that will block updates.
If you want to make sure, here's the cleanest way of doing so:
Block BN OTA Updates the EASY way
Yes, it's a Nook Color thread but it would work for Nook ST aswell.

TJay99 said:
The OP's post has given me some hope as I do not wish to unroot/re-root-/update at this time, but have kept my NST's wireless off as I'm afraid of getting the update.
Am I to understand that a TouchNooter'd unit (1.6.24 on an NST1.0.1) will not get updated and there is nothing to fear?
Click to expand...
Click to collapse
Blocking updates is also covered here http://forum.xda-developers.com/showthread.php?t=1346748 but with adb and sqlite.
Search for Blocking OTA updates: on the thread.

Yeah, I hear you. I gotta just do it. Strange though, why my Nook won't update.
ros87 said:
Updating a TouchNootered NST have caused troubles in the past and is likely to do so with this update as well.
Even if it worked for other users it might not work for you as people do different things to their rooted NST.
I know it's a hassle, but you should really restore+reset your NST before updating if you want to avoid problems.
Click to expand...
Click to collapse

Thanks ros87 and eded333 for the information.
As regards the adb/sqlite method, I just reviewed that thread and the specific "Blocking OTA Updates" section. Looks easy,... assuming one thing: that -- other than installing java JKD and the android SDK on my PC -- my NST (TouchNooter'd 1.6.2.4 on B&N1.0.1) already is set up to receive those commands listed. If it is, then I can simply connect the NST and type only those commands listed in the "Blocking OTA Updates" section. Right?
If that's not the case, what other procedures must I do in order to get it done? For instance, there are sections entitled "Setting up adb on the nook touch" and "Setting up root access on NST through adb and installing busybox". Would I need to do any part of those processes?
Much obliged if you can clear up that one matter for me!

I couldn't get my rooted 1.0.1 nook to update even manually. It silently deleted the update file and did nothing every time I tried.

Kralik said:
I couldn't get my rooted 1.0.1 nook to update even manually. It silently deleted the update file and did nothing every time I tried.
Click to expand...
Click to collapse
Hi, Kralik.
I wonder if it would keep downloading/deleting the update file in a perpetual cycle, though. Isn't that what would happen?

TJay99 said:
Thanks ros87 and eded333 for the information.
As regards the adb/sqlite method, I just reviewed that thread and the specific "Blocking OTA Updates" section. Looks easy,... assuming one thing: that -- other than installing java JKD and the android SDK on my PC -- my NST (TouchNooter'd 1.6.2.4 on B&N1.0.1) already is set up to receive those commands listed. If it is, then I can simply connect the NST and type only those commands listed in the "Blocking OTA Updates" section. Right?
If that's not the case, what other procedures must I do in order to get it done? For instance, there are sections entitled "Setting up adb on the nook touch" and "Setting up root access on NST through adb and installing busybox". Would I need to do any part of those processes?
Much obliged if you can clear up that one matter for me!
Click to expand...
Click to collapse
Touchnooter has adb enabled over wifi (If i'm not wrong), so you wouldnt have to enable it again, go directly into the OTA.

TJay99 said:
As regards the adb/sqlite method, I just reviewed that thread and the specific "Blocking OTA Updates" section. Looks easy,... assuming one thing: that -- other than installing java JKD and the android SDK on my PC -- my NST (TouchNooter'd 1.6.2.4 on B&N1.0.1) already is set up to receive those commands listed. If it is, then I can simply connect the NST and type only those commands listed in the "Blocking OTA Updates" section. Right?
Click to expand...
Click to collapse
You should be good to go if you install jdk + android sdk.
With TouchNooter 1.6.24 you should allready have adb access enabled via wifi.
---------- Post added at 08:34 PM ---------- Previous post was at 08:33 PM ----------
Kralik said:
I couldn't get my rooted 1.0.1 nook to update even manually. It silently deleted the update file and did nothing every time I tried.
Click to expand...
Click to collapse
Interesting, I need to take a closer look at the update process some day

Yep, same behavior with mine.
Kralik said:
I couldn't get my rooted 1.0.1 nook to update even manually. It silently deleted the update file and did nothing every time I tried.
Click to expand...
Click to collapse

TJay99 said:
Hi, Kralik.
I wonder if it would keep downloading/deleting the update file in a perpetual cycle, though. Isn't that what would happen?
Click to expand...
Click to collapse
That is my guess. Without knowing for sure you're left with two unpleasant options:
1) Your nook tries to update continuously: downloading, deleting, and wasting battery life,* or
2) Your nook actually updates and destroys everything!
So you might take the time to "block" OTA updates as other have mentioned. But then there's option...
3) You go through the rigors and just get the 1.1.0 firmware upgrade over and done with, rerooting afterwards.
*I wonder if this is related to the "I rooted my nook and now my battery life is toast" thread?

This is an excellent point. I've also experienced pretty sad battery life since applying Touchnooter.
I'll just bite the bullet and restore/re-root.
Kralik said:
1) Your nook tries to update continuously: downloading, deleting, and wasting battery life,* or
*I wonder if this is related to the "I rooted my nook and now my battery life is toast" thread?
Click to expand...
Click to collapse

kunchers said:
This is an excellent point. I've also experienced pretty sad battery life since applying Touchnooter.
I'll just bite the bullet and restore/re-root.
Click to expand...
Click to collapse
This is the best time to do that, finally got Gapps to work on 1.1 manully, at last!
If you wish to try it, here is my post:
http://forum.xda-developers.com/showthread.php?t=1346748

Kralik said:
That is my guess
1) Your nook tries to update continuously: downloading, deleting, and wasting battery life,* or
Click to expand...
Click to collapse
A good and interesting guess.
There are intervals defined for the update checks, but maybe if it finds an update but are unable to apply it, it end up in a loop..

GApps aren't actually that hard to enable if you use TouchNooter 1.6.24 and manually replace /nooter/boot/uRamdisk and /system/framework/framework.jar with the updated versions. Other than that step, very little difference in the rooting processes. If one is going to restore to factory and build up from there, what is the advantage to wading through all the manual steps?

Kralik said:
GApps aren't actually that hard to enable if you use TouchNooter 1.6.24 and manually replace /nooter/boot/uRamdisk and /system/framework/framework.jar with the updated versions. Other than that step, very little difference in the rooting processes. If one is going to restore to factory and build up from there, what is the advantage to wading through all the manual steps?
Click to expand...
Click to collapse
At this moment, fun, learning, and stability (for the moment it allways works, but I need more feedback from people that tried it) eventually, when I delete all the blob that Gapps dosn't need for them to work, and is installed on the default package of Touchnooter (Don't get me wrong I really think its a great method) you will get a cleaner install.
Anyway, If you don't want to go through all the steps you can use the new 1.1 Touchnooter to get root, and then use my GApps method.

Keep Root through OTA

Read up on this in my Google New reader app.
Just installed it to see if it works on our tabs, and it appears to.
What I believe it does is make a backuo of your root.
Before you do an OTA, you uninstall root (after you've backed up root) through the app, then after OTA you restore your root.
For those of you that like to stay stock, but have root, here's the link.
https://market.android.com/details?id=org.projectvoodoo.otarootkeeper

interesting But i bet acer is Already working on patching this... I also think that is what takes them so long to push updates.. Patching holes. to prevent dev. on There devices that we PAID For ...APPLE Ceo did not die He Quit and it working with Elvis at Acer... Giggles..

erica_renee said:
interesting But i bet acer is Already working on patching this... I also think that is what takes them so long to push updates.. Patching holes. to prevent dev. on There devices that we PAID For ...APPLE Ceo did not die He Quit and it working with Elvis at Acer... Giggles..
Click to expand...
Click to collapse
I guess you didn't understand what it does?
Doesn't your sig say "reading is power"?

yes i read what it does.. Just not sure how long it will remain valid and i d/loaded it will check it out give it a try

erica_renee said:
yes i read what it does.. Just not sure how long it will remain valid and i d/loaded it will check it out give it a try
Click to expand...
Click to collapse
It does nothing to the bootloader, merely retains root. After you backup root with the app, you get your OTA, then restore your root through the app.

OK What i do not understand.. is IF it can retain root thru the OTA.. ota updates change they system file permissions and protects them. The use some type of exploit to root the device. This app is doing the same Am i correct.. And if i am acer can plug that exploit. Also.. is this works to reroot afer a ota unrootes the device.. why will this not just root the tablet as well. looks like someone could take it apart and create a new way to root the tablet without DOWNGRADING or flashing a new rom..
IS the above true or am i just STUPID For thinking all of this... the dev might know something that is not known on the a500 forums ...

I can tell you exactly how it works.
In Linux there is a command called chattr which allows you to change the attributes on a file like in Windows (readonly for example). However, in Linux it is much more powerful. So, what you do, is set the chattr bit so NOBOBY can modify a file. Not even root. If root wants to change it, then root has to remove that bit first.
So, if you want to keep root you chattr it. Then when the update.zip runs and walks through the /system folder it cannot remove the su sticky bit because it has been chattr'ed.
However, some updates delete everything in the /system/xbin folder therefore the tool makes a backup to another folder called /system/backupsu. This backup usually remains. Usually, that is, unless ACER loads a NEW /system image. Like they need to expand the size, or want to reload everything, then they lay down a NEW system image and it's gone. ALL GONE.
Some ask, why don't you chattr to another folder other then system, well most other mount points have su sticky bit turned off, therefore making su not work from another mount.
So will ACER plug the chattr hole? I don't think so, this in the kernel and part of the file system. They could walk the system mount and un-chattr everything, but then again you can just use another approach.
The chattr trick normally only works on simple OTA's. For example, I think when ACER went to 3.2 they relaid down system. I could be wrong, I'd have to check my notes. But thankfully, most vendors don't reload system that often so you'r find that chattr'ng the su file works 99% of the time.
Hope this helps,
TD
---------- Post added at 06:25 PM ---------- Previous post was at 06:10 PM ----------
Also, 411 on rooting.
To root, you find a hole and then set the 'sticky bit' on an executable so it now runs as root for example: rwsr-xr-x. Notice the 's' in the owner permissions. When this file is executed it runs with the owners permissions on the file system. So to make a simple root, just copy the ash shell to /system/xbin make the file owned by root and then set the sticky bit. Now, if you are not root, you just run /system/xbin/ash and because this version of ash is owned by root and has the sticky bit set, you get the root(#) because the ash shell is now running as root.
So, you use the exploit to gain root and then set up a program to give you root anytime you want it. Usually that program is named su. Now, when an update runs, it walks the entire /system tree resetting all files to rwxr-xr-x which removes the sticky bit and breaks root.
What is heartbreaking, is you now need to use the exploit to get root so you can set back your sticky bit. If the update patched your exploit then you have find another one.
So, the question is, once you get root, how do you keep it. Using chattr is one way therefore if the update removes your exploit, hopefully it doesn't matter because you 'locked in' your sticky bit with chattr.
This is why once any version is rooted you can root most any other version. It now becomes possible to move back and forth through OTA's while allowing you to keep root. But time traveling a root OTA is only possible into the future, you can never go back in time prior to the invention of the root. But you can always travel forward with root. This is exactly how we root the 3.2.1. We take a tablet that has 3.0.1 on it and use iconia root exploit to root it. Then we lock it, add other backdoors, and roll forward in time through the minefields of the OTA's until it stops. Hopefully, you still have root. In other words, it's the flux capacitor and is what makes future rooting possible.
So it doesn't matter, as long as you chattr (chatter), because who cares if ACER's heart goes pitter patter <<== Sounds like a Roll'n Stone lyrics <lol>
"Don't you know the crime rate is going up, up, up, up, up
To live on this forum you must be tough, tough, tough, tough, tough
You got rats at ACER dreaming of the west side
Software bugs on upgrades
What a mess, this forum says chatter (chattr), so my root won't be shattered
My brains been battered, splattered all over this forum
but what's that matter.
Ah look at me, my root is chattr'ed
I'm not wanting my root shattered
Look at me- I'm a chattr'ed, look at me
Man time to go drink heavily.

"SOFTMOD" app
SORRY PPL COMPLETELY CONFUSED 2 DIFFERENT TOPICS IN 2 DIFFERENT THREADS - ALZHEIMER's RULES OK!! - Deleted this response

timmyDean your making my head spin. Thanks for the info.

ok as I was thinking this works unless acer pushes a full os.So I will continue to stay on custom roms.giggles

erica_renee said:
ok as I was thinking this works unless acer pushes a full os.So I will continue to stay on custom roms.giggles
Click to expand...
Click to collapse
Actually, I went back to 3.1 today to test it out. It worked through all updates, including full updates

kjy2010 said:
Actually, I went back to 3.1 today to test it out. It worked through all updates, including full updates
Awesome.
It seems interesting
Click to expand...
Click to collapse

kjy2010 said:
Actually, I went back to 3.1 today to test it out. It worked through all updates, including full updates
Click to expand...
Click to collapse
You the man. I could not recall if 3.0.1 to 3.1 to 3.2 did a system reload. What some OEM's do is erase /system. Lenovo did that when they went from 11 to 12 and then from 12 to 13. But, I could not recall if ACER did. You'll find that chattr works 99% of the time, maybe 100% on an ACER. That's why I turn off OTA's so they don't occur automatically. Then when one becomes available, I download and look at what they're changing before allowing it. This is really important now that they've locked the bootloader. If you take an OTA and it patches your root exploit, removes chattr, deletes your backup su, and breaks root then you might be stuck in the future with no root. If this happens you have to hope there's a way back without root.
So thanks.
---------- Post added at 03:28 PM ---------- Previous post was at 03:15 PM ----------
erica_renee said:
ok as I was thinking this works unless acer pushes a full os.So I will continue to stay on custom roms.giggles
Click to expand...
Click to collapse
Not a full system, it's how they load it is the key. They push full systems all the time and they really just copy over all new which keeps chattr'ed files. They really have to reformat /system (or destructively destroy it). They'll do this if they need to increase the size, change from ext3 to ext4, etc.
Hope this helps
TD

Thanks sirs for this if we get the doubtful ota I might do this n sell the tap to my little brother or keep it who knows lol
Sent from my HTC Inspire 4G using Tapatalk

timmyDean said:
You the man. I could not recall if 3.0.1 to 3.1 to 3.2 did a system reload. What some OEM's do is erase /system. Lenovo did that when they went from 11 to 12 and then from 12 to 13. But, I could not recall if ACER did. You'll find that chattr works 99% of the time, maybe 100% on an ACER. That's why I turn off OTA's so they don't occur automatically. Then when one becomes available, I download and look at what they're changing before allowing it. This is really important now that they've locked the bootloader. If you take an OTA and it patches your root exploit, removes chattr, deletes your backup su, and breaks root then you might be stuck in the future with no root. If this happens you have to hope there's a way back without root.
So thanks.
---------- Post added at 03:28 PM ---------- Previous post was at 03:15 PM ----------
Not a full system, it's how they load it is the key. They push full systems all the time and they really just copy over all new which keeps chattr'ed files. They really have to reformat /system (or destructively destroy it). They'll do this if they need to increase the size, change from ext3 to ext4, etc.
Hope this helps
TD
Click to expand...
Click to collapse
Yes i do understand. Maybe i did not explain what i was saying correctly.. Acer's update is not aware or looking for those files. There for they do not touch them. as they are just scanning and updating files to reflect there changes.. I to agree that its likely this will remain valid.Atleast we know it is for the os updates and release that are available up to now..

erica_renee said:
Yes i do understand. Maybe i did not explain what i was saying correctly.. Acer's update is not aware or looking for those files. There for they do not touch them. as they are just scanning and updating files to reflect there changes.. I to agree that its likely this will remain valid.Atleast we know it is for the os updates and release that are available up to now..
Click to expand...
Click to collapse
Exactly, so much for being blonde <lol>

6055U Root method found

Hello all, I found a method to Root and get a custom recovery on our cricket variant, no donations required! You need to find a copy of sugar qct with a username and password, I don't remember exactly where I found it but it shouldn't be too difficult to find. Then you need to let it update to the latest build, which includes the programmer for our phone. If you don't see 6055u in the list it's not up to date. From there, Hook up your phone (may need to manually put it in download mode. Press upgrade and then navigate to the install directory, look in /bin and find where it downloads all the mbm files. Replace the one that starts with an r with the TWRP recovery for 6055. You may have to overwrite it multiple times during the process. If you did it correctly you will be able to boot into TWRP, if not try again. If you don't close sugar I believe it won't overwrite the firmware files, but I haven't messed with it much. I will try to write a tool to make it easier when I have the time but I'm pretty busy. Feel free to pm me with any questions and I will help the best I can.
To get root just install supersu

F
dbgr said:
Hello all, I found a method to Root and get a custom recovery on our cricket variant, no donations required! You need to find a copy of sugar qct with a username and password, I don't remember exactly where I found it but it shouldn't be too difficult to find. Then you need to let it update to the latest build, which includes the programmer for our phone. If you don't see 6055u in the list it's not up to date. From there, Hook up your phone (may need to manually put it in download mode. Press upgrade and then navigate to the install directory, look in /bin and find where it downloads all the mbm files. Replace the one that starts with an r with the TWRP recovery for 6055. You may have to overwrite it multiple times during the process. If you did it correctly you will be able to boot into TWRP, if not try again. If you don't close sugar I believe it won't overwrite the firmware files, but I haven't messed with it much. I will try to write a tool to make it easier when I have the time but I'm pretty busy. Feel free to pm me with any questions and I will help the best I can.
To get root just install supersu
Click to expand...
Click to collapse
Did a Google search for "sugar qct" and I see a couple of million hits for "The Sugar Act"... :laugh:
Tried Root Genius, and it, of course doesn't work...
If you happen to find a link for the app or method you stated, I would be eternally grateful... My lovely wife and I upgraded our phones to the Cricket 6055U, and, since, while not an Android developer, per se, can find my way around the device without being scared off...
So, with due respect, I'd ask if you have the app or name correct?
Thanks, friend, and best respect.
--- edit ---
Oops... was premature... found it and am giving it a try... I'll post my results after I give it a shot...

http://forum.gsmhosting.com/vbb/f606/vf-895n-smart-prime-6-stock-rom-flash-tool-2033867/
This should help with setting up sugar. The only difference here is to update it and you also need a username and password that I don't have on me at the moment. It will be a few hours until I get home but I will update asap.
Edit: nevermind lol, good luck friend. You may need a decent battery percentage as well

pauljulian said:
F
Did a Google search for "sugar qct" and I see a couple of million hits for "The Sugar Act"... :laugh:
Tried Root Genius, and it, of course doesn't work...
If you happen to find a link for the app or method you stated, I would be eternally grateful... My lovely wife and I upgraded our phones to the Cricket 6055U, and, since, while not an Android developer, per se, can find my way around the device without being scared off...
So, with due respect, I'd ask if you have the app or name correct?
Thanks, friend, and best respect.
--- edit ---
Oops... was premature... found it and am giving it a try... I'll post my results after I give it a shot...
Click to expand...
Click to collapse
----- edit 2 -----
OK... apparently I'm an idiot... Running Windows 10 Pro, and the installer says it's going to install to an appropriate folder on C:\... yet, trying to find it, it really is weird.... I'm going to try on a VMWare Win 7 virtual PC, and see if I'm able to find it there, and move it to my actual C: drive...
If it works, I'll be grateful for your contribution and praise you to the highest heaven! :laugh:

pauljulian said:
----- edit 2 -----
OK... apparently I'm an idiot... Running Windows 10 Pro, and the installer says it's going to install to an appropriate folder on C:\... yet, trying to find it, it really is weird.... I'm going to try on a VMWare Win 7 virtual PC, and see if I'm able to find it there, and move it to my actual C: drive...
If it works, I'll be grateful for your contribution and praise you to the highest heaven! :laugh:
Click to expand...
Click to collapse
Can't seem to get the beast to work...
If you would be so kind, would there be any way you'd be able to write up a concise step-by-step thing, if you've made it work... I've got the .chm file open on my desktop, and have spent a few hours trying to make it work to no avail.
Again, if it worked for you, your process would be welcome.
Cricket Alcatel Idol 4, 6055U
---------- Post added at 03:36 PM ---------- Previous post was at 02:40 PM ----------
pauljulian said:
Can't seem to get the beast to work...
If you would be so kind, would there be any way you'd be able to write up a concise step-by-step thing, if you've made it work... I've got the .chm file open on my desktop, and have spent a few hours trying to make it work to no avail.
Again, if it worked for you, your process would be welcome.
Cricket Alcatel Idol 4, 6055U
Click to expand...
Click to collapse
My point is that the site recommended seems to insist on Lollipop on the small beast... and there doesn't seem to be a recommendation for the .bin files, and, when installing on Win 10, it seems to install the Sugar app into some directory on my C: drive that is really not that accessible... Did it using a VMWare Win 7 32-bit virtual, and was able to access the directory, copy and paste to my regular C: drive (old Windows geek since Win 3.11... and DOS 3), and it seemed to run... (of course, running as Administrator), but it really doesn't seem to work for me... Again, I freely admit that I'm likely not doing something right, but even after some research and the included .chm file, I seem to be missing something.
Again, and begging your indulgence for seeming like a noob or a rube, but if I'm not making it happen, I rather think that the tips would be lost on someone for whom this is their first Android device...
Kinda frustrating, as, even though I've been a tech-support guy and database developer for more than 30 years, this thing has me stymied...
I found it fascinating for the *#*# command, earlier, from another noble soul, and, obviously, I also found that the device as configured says, basically... "Don't give a damn... you can turn this sucker on, but as soon as you exit this menu, I'm gonna turn it off again."
Just a little frustrating, and it seems that most of the tips and tricks elsewhere seem to be thinking that new owners of the 6055U are running Lollipop.... aaarrrgggghhh....
If it needs Lollipop to work, and if there's a relatively painless way to downgrade, and then upgrade from a ROM, I'm good with that... the Idol 3 seemed to require that, and it worked well for me, with just an evening's work. This one? Cricket seems to have had a warped sense of humor about it... I seriously dig the device, and, since my Idol 3 broke, and my lovely wife's LG G-Stylo (which was a pain in the ass, and next-to-impossible to root, and then be just perpetually stuck at the logo screen with an unfixable boot loop, if one screwed it up, and just required sending the beast back to LG, as long as one took out Cricket's warranty plan... <sigh>), we took the plunge on this one...
Not much for which I require root, but, since I spent good money on some legit apps (and lucked into a few ... ahem... not legit apps that worked for me), these things require root... I know there's a way to do it, and the Sugar app seems promising, but, mildly autistic guy that I am (and 60 years old, with a memory that doesn't work as it used to), a slimmed-down step-by-step doc would be helpful... should some noble soul put such together...
Apparently, the root method has worked for at least one member here.... But this weird old Jewish hippie doesn't see the mental diagram....
Any help would be welcome, my friends and mishpocheh... ("dear family" --- been here enough years, albeit a relatively quiet member, that y'all might as well be family... )

Hey everyone, sorry about the confusion. I installed on Windows 10 pro with no issues. As far as the page I linked you can disregard everything but the app itself. The update that downloads is marshmallow, and I've had no issues overwriting the latest version. I may have gotten sugar from a different location though, as soon as I get a chance I will do a better write up with everything. A helpful way to find the install directory would be right click on the shortcut from the start menu and click find Target / open file location. If it brings you to the folder with the shortcuts do it again and you will have the install directory. The app should be in (install dir)/tool and the downloaded updates go in (install dir)/bin under a folder that only shows up once you start the process within sugar. I will try to compile the information into a more user friendly format tonight but I can't make any promises on that.

Also just to clarify, I didn't use any chm file

I'm wondering if you could upload your version you have on your pc. I just spent the last month in jail here in Orlando fighting a case and the only proof I've got is on my phone on a phone that I deleted my videos on. I really need the videos back too get a not guilty if I gotta pay for it it's cool but I'm out on bond and all the recover videos apps require root

I got this to work last night. Typed up some instructions but didn't get them posted. They're on my PC at home and I'm at work.
Basically use the copy of sugar in the download package in this thread and then start it and let it update https://forum.xda-developers.com/android/development/recovery-vodafone-prime-tab-7-t3548560
Those are the basic instructions too except we don't need to swap out bout and use the TWRP from deckersu thread.
Once flashed it'll automatically reboot. I found you had to make sure you caught this and booted into TWRP right away don't let the phone boot. Then transfer SuperSU in TWRP and flash.
---------- Post added at 11:29 AM ---------- Previous post was at 11:23 AM ----------
Asadullah said:
I'm wondering if you could upload your version you have on your pc. I just spent the last month in jail here in Orlando fighting a case and the only proof I've got is on my phone on a phone that I deleted my videos on. I really need the videos back too get a not guilty if I gotta pay for it it's cool but I'm out on bond an ind all the recover videos apps require root
Click to expand...
Click to collapse
FYI this root method wipes your phone so I don't know if this will help your situation or not.

In sugar there is an option to not wipe, it's under session settings or something to that effect

dbgr said:
In sugar there is an option to not wipe, it's under session settings or something to that effect
Click to expand...
Click to collapse
Wish I had noticed that!! Oh well, stoked to have root and it's good to start fresh. Got Xposed installed today and finally got that annoying charging light turned off. Working on getting wifi tetherng working. Then if I can figure out how to get the dialer to be friends with Google voice this phone will have all its annoyance fixed
Thanks so much for figuring this out and sharing!!

dbgr said:
In sugar there is an option to not wipe, it's under session settings or something to that effect
Click to expand...
Click to collapse
Appreciate the help

woodi5359 said:
https://forum.xda-developers.com/android/development/recovery-vodafone-prime-tab-7-t3548560.
Click to expand...
Click to collapse
Thank you for finding this thread, it is the same one I found but I couldn't remember where it was the other day when I started this thread. Hopefully this will help the people who have been having issues, although I will admit a more painless method would be preferable. I'm currently working on modifying a dirtycow exploit to simply flash the recovery and reboot into twrp, if I get it to work I will zip it all up and post it here.

woodi5359 said:
Wish I had noticed that!! Oh well, stoked to have root and it's good to start fresh. Got Xposed installed today and finally got that annoying charging light turned off. Working on getting wifi tetherng working. Then if I can figure out how to get the dialer to be friends with Google voice this phone will have all its annoyance fixed
Thanks so much for figuring this out and sharing!!
Click to expand...
Click to collapse
I got wifi tethering working I did a lot of things but I believe that did it was adding net.tethering.noprovisioning=true to my build.prop then I went into system/app and changed serviceentitlement.apk into serviceentitlement.oat using es file Explorer

Asadullah said:
I got wifi tethering working I did a lot of things but I believe that did it was adding net.tethering.noprovisioning=true to my build.prop then I went into system/app and changed serviceentitlement.apk into serviceentitlement.oat using es file Explorer
Click to expand...
Click to collapse
I just tested this and it indeed does work. Great find friend!

Asadullah said:
I got wifi tethering working I did a lot of things but I believe that did it was adding net.tethering.noprovisioning=true to my build.prop then I went into system/app and changed serviceentitlement.apk into serviceentitlement.oat using es file Explorer
Click to expand...
Click to collapse
Thanks for figuring this out!!! I'd been messing with it for a few days. The renaming the apk to .oat was the piece I was missing. That and a reboot got it working!!

dbgr said:
Hello all, I found a method to Root and get a custom recovery on our cricket variant, no donations required! You need to find a copy of sugar qct with a username and password, I don't remember exactly where I found it but it shouldn't be too difficult to find. Then you need to let it update to the latest build, which includes the programmer for our phone. If you don't see 6055u in the list it's not up to date. From there, Hook up your phone (may need to manually put it in download mode. Press upgrade and then navigate to the install directory, look in /bin and find where it downloads all the mbm files. Replace the one that starts with an r with the TWRP recovery for 6055. You may have to overwrite it multiple times during the process. If you did it correctly you will be able to boot into TWRP, if not try again. If you don't close sugar I believe it won't overwrite the firmware files, but I haven't messed with it much. I will try to write a tool to make it easier when I have the time but I'm pretty busy. Feel free to pm me with any questions and I will help the best I can.
To get root just install supersu
Click to expand...
Click to collapse
so im getting ready to purchase this device so there is root and twrp for it or no

Dude, did you read the thread at all? I don't mind helping but you gotta do your part. Yes there is TWRP and Root

dbgr said:
Hello all, I found a method to Root and get a custom recovery on our cricket variant, no donations required! You need to find a copy of sugar qct with a username and password, I don't remember exactly where I found it but it shouldn't be too difficult to find. Then you need to let it update to the latest build, which includes the programmer for our phone. If you don't see 6055u in the list it's not up to date. From there, Hook up your phone (may need to manually put it in download mode. Press upgrade and then navigate to the install directory, look in /bin and find where it downloads all the mbm files. Replace the one that starts with an r with the TWRP recovery for 6055. You may have to overwrite it multiple times during the process. If you did it correctly you will be able to boot into TWRP, if not try again. If you don't close sugar I believe it won't overwrite the firmware files, but I haven't messed with it much. I will try to write a tool to make it easier when I have the time but I'm pretty busy. Feel free to pm me with any questions and I will help the best I can.
To get root just install supersu
Click to expand...
Click to collapse
do you hold volume down when it reboots

link22534 said:
do you hold volume down when it reboots
Click to expand...
Click to collapse
It's volume up and power

Going back to stock rom, coming from lineageos 16 ????? Lenovo Tab4 10 Plus TB-X704F

Hey guys,
since I dont get neither Netflix nor Disney+ to work on my TB-X704F after having flashed LOS 16, I want to go back to stock rom. I've already tried to use Lenovo Smart Assistant but the flashing procedure always fails. I also tried QComLoader but also fails at 5%.
Is there a working way on going back to stock rom having TRWP ans LOS 16 installed???
Due to the fact that Netflix and Disney+ arent working (already tried Magisk module to change the tablets' fingerprint), I need to go back to stock rom.
Thanks in advance!!!!

Please use this tool to flash the stock rom: https://qfiltool.com/qfil-tool-v2-0-2-3

need help here. I'm flashed LineageOS previously. Can't install NetFlix hence i want to switch back to stock. I've installed the drivers and QFIL software. however when the device is off, i hold the volume up button then plug in the usb, but the QFIL software still show port not available. I entered the TWRP screen asking me to whether i can choose Boot to FFBM. Restart Bootloader.. etc. what should i choose?

I assume by "magisk module", you mean the termux props method? That's worked for me on several devices.
Also I really don't know how I can help you past that, most stock firmwares aren't designed to be flashed on modified devices. Very few manufacturers even support that (Samsung, LG and OnePlus are falriy major exceptions)
Edit: just realised the age of the thread, apologies.

rhchia said:
need help here. I'm flashed LineageOS previously. Can't install NetFlix hence i want to switch back to stock. I've installed the drivers and QFIL software. however when the device is off, i hold the volume up button then plug in the usb, but the QFIL software still show port not available. I entered the TWRP screen asking me to whether i can choose Boot to FFBM. Restart Bootloader.. etc. what should i choose?
Click to expand...
Click to collapse
I've got the same problem. What did you do in the end?

K14_Deploy said:
I assume by "magisk module", you mean the termux props method? That's worked for me on several devices.
Also I really don't know how I can help you past that, most stock firmwares aren't designed to be flashed on modified devices. Very few manufacturers even support that (Samsung, LG and OnePlus are falriy major exceptions)
Edit: just realised the age of the thread, apologies.
Click to expand...
Click to collapse
What exactly is the termux props method?
Is that to fix Magisk not authenticating? Or to allow the tool QFIL to restore stock?

boomhaueruk said:
What exactly is the termux props method?
Is that to fix Magisk not authenticating? Or to allow the tool QFIL to restore stock?
Click to expand...
Click to collapse
I mean the MagiskHide Props Config, which requires Termux. Basically you install the module, give Termux root and configure props with it. Then you use MagiskHide to hide magisk from them.
On the topic of reverting to stock, it's not possible. Custom firmware is almost always a one way process, and you understand if you do it things like the OP has described can and will happen. People who want things to "just work" use stock firmware, or an Apple device, it was never designed to not need tinkering.

K14_Deploy said:
I mean the MagiskHide Props Config, which requires Termux. Basically you install the module, give Termux root and configure props with it. Then you use MagiskHide to hide magisk from them.
On the topic of reverting to stock, it's not possible. Custom firmware is almost always a one way process, and you understand if you do it things like the OP has described can and will happen. People who want things to "just work" use stock firmware, or an Apple device, it was never designed to not need tinkering.
Click to expand...
Click to collapse
Goodness, I'm not a person who needs a 'just work' situation. It took weeks to get this onto stock and I've spent a long time reading up trying to fix Magisk. Surely there has to be a point when you're actually using the device and not just fixing it!
Basic things like being able to download and use apps...that seems like a reasonable request.
I think there's 'tinkering' and 'it doesn't work!'
Also, I've rolled back to stock roms before on various phones, recovery and so on - not with this tablet admittedly. Surprised it seems such a difficult or - as you say - impossible process. But hey.
That said, I appreciate the help! I really do.
So; I need to find 'Termux'. https://termux.com/
This says I get it from 'F Droid'. But I then found a link on their webpage to this;
https://f-droid.org/repo/com.termux_117.apk
I'm assuming that's the right one.
It looks like a terminal?
Googling for Termux Magiskhide props config got me to this youtube video;
It's in Indonesian, but shows you some steps. Would that be the best place to find instructions?

boomhaueruk said:
Goodness, I'm not a person who needs a 'just work' situation. It took weeks to get this onto stock and I've spent a long time reading up trying to fix Magisk. Surely there has to be a point when you're actually using the device and not just fixing it!
Basic things like being able to download and use apps...that seems like a reasonable request.
I think there's 'tinkering' and 'it doesn't work!'
Also, I've rolled back to stock roms before on various phones, recovery and so on - not with this tablet admittedly. Surprised it seems such a difficult or - as you say - impossible process. But hey.
That said, I appreciate the help! I really do.
So; I need to find 'Termux'. https://termux.com/
This says I get it from 'F Droid'. But I then found a link on their webpage to this;
https://f-droid.org/repo/com.termux_117.apk
I'm assuming that's the right one.
It looks like a terminal?
Googling for Termux Magiskhide props config got me to this youtube video;
It's in Indonesian, but shows you some steps. Would that be the best place to find instructions?
Click to expand...
Click to collapse
Is this going to be a problem?
Magisk is dropping support for hiding root access from apps
Magisk, the popular Android rooting tool, will continue to be developed by topjohnwu, but without its root hiding feature called MagiskHide.
www.xda-developers.com

boomhaueruk said:
Goodness, I'm not a person who needs a 'just work' situation. It took weeks to get this onto stock and I've spent a long time reading up trying to fix Magisk. Surely there has to be a point when you're actually using the device and not just fixing it!
Basic things like being able to download and use apps...that seems like a reasonable request.
I think there's 'tinkering' and 'it doesn't work!'
Also, I've rolled back to stock roms before on various phones, recovery and so on - not with this tablet admittedly. Surprised it seems such a difficult or - as you say - impossible process. But hey.
That said, I appreciate the help! I really do.
So; I need to find 'Termux'. https://termux.com/
This says I get it from 'F Droid'. But I then found a link on their webpage to this;
https://f-droid.org/repo/com.termux_117.apk
I'm assuming that's the right one.
It looks like a terminal?
Googling for Termux Magiskhide props config got me to this youtube video;
It's in Indonesian, but shows you some steps. Would that be the best place to find instructions?
Click to expand...
Click to collapse
You can install Termux from the Play Store if you have GApps. I did and it worked. And yes, it is a terminal. I've just upgraded to 17.1 on this device so I'm going to be doing it again sooner rather than later anyway.

K14_Deploy said:
You can install Termux from the Play Store if you have GApps. I did and it worked. And yes, it is a terminal. I've just upgraded to 17.1 on this device so I'm going to be doing it again sooner rather than later anyway.
Click to expand...
Click to collapse
Thanks.
I guess my other issue is I'm not actually sure what steps I'm supposed to do next.
That youtube video looks really dodgy!
It's nice to find someone else on this device. Mine has sat unused for months, I've decided to finally either get it to work properly or bin it. Todays the day.

boomhaueruk said:
Thanks.
I guess my other issue is I'm not actually sure what steps I'm supposed to do next.
That youtube video looks really dodgy!
Click to expand...
Click to collapse
Ok, so...
Make sure Magisk has "MagiskHide Props Config" and "Busybox For Android NDK" and root fully enabled. Hide must be disabled. If this isn't the case, do so and then reboot.
Open Termux. Type 'su' to give root access. Then type 'props' and follow the menu for your device. Type '1' for 'Edit device fingerprint'. Type 'f' for 'Pick a certified fingerprint'. Type '13' for 'Lenovo'. Type '2' for 'Lenovo Tab 4 8 Plus TB-8704F (8.1.0)'. If you have another device you might be out of luck. Type 'y' for 'yes'. Wait. Type 'y' again to reboot.
Configure MagiskHide to hide these parts of GPS + any other root sensitive apps. The screenshot I have was taken from a OnePlus but it shows the GPS that needs to be hidden. The less you can get away with hiding the better for performance reasons. Also make sure to repackage Magisk as 'Settings' and change the name of the 'TWRP' folder using a root file explorer (for some reason I don't have one) to... I'm partial to 'f**kyougoogle' personally, but anything will do. Reboot again and Disney+ should work just fine. If it doesn't, I can't help you.
I'd recommend moving to 18.1 before doing this, you'll have to start from square 1 but it means you're more up to date and won't have to do it again until someone builds 19.1 for this device. Can confirm, that build works.
This isn't without risk. Some apps specifically wanting android 11 might not work right. But it SHOULD fix root sensitive apps that use Safetynet. I also can't say anything about Widevine compatibility as I don't have Disney+ on this device.
boomhaueruk said:
Thanks.
I guess my other issue is I'm not actually sure what steps I'm supposed to do next.
That youtube video looks really dodgy!
It's nice to find someone else on this device. Mine has sat unused for months, I've decided to finally either get it to work properly or bin it. Todays the day.
Click to expand...
Click to collapse

K14_Deploy said:
Ok, so...
Make sure Magisk has "MagiskHide Props Config" and "Busybox For Android NDK" and root fully enabled. Hide must be disabled. If this isn't the case, do so and then reboot.
Open Termux. Type 'su' to give root access. Then type 'props' and follow the menu for your device. Type '1' for 'Edit device fingerprint'. Type 'f' for 'Pick a certified fingerprint'. Type '13' for 'Lenovo'. Type '2' for 'Lenovo Tab 4 8 Plus TB-8704F (8.1.0)'. If you have another device you might be out of luck. Type 'y' for 'yes'. Wait. Type 'y' again to reboot.
Configure MagiskHide to hide these parts of GPS + any other root sensitive apps. The screenshot I have was taken from a OnePlus but it shows the GPS that needs to be hidden. The less you can get away with hiding the better for performance reasons. Also make sure to repackage Magisk as 'Settings' and change the name of the 'TWRP' folder using a root file explorer (for some reason I don't have one) to... I'm partial to 'f**kyougoogle' personally, but anything will do. Reboot again and Disney+ should work just fine. If it doesn't, I can't help you.
I'd recommend moving to 18.1 before doing this, you'll have to start from square 1 but it means you're more up to date and won't have to do it again until someone builds 19.1 for this device. Can confirm, that build works.
This isn't without risk. Some apps specifically wanting android 11 might not work right. But it SHOULD fix root sensitive apps that use Safetynet. I also can't say anything about Widevine compatibility as I don't have Disney+ on this device.
Click to expand...
Click to collapse
Thanks.
OK. So, I've attached a few pics to show you where I am.
Booted, checked into Magisk for those settings. I can see 'Magiskhide', so I can untick that, but how do I ensure "Magisk has "MagiskHide Props Config" and "Busybox For Android NDK" and root fully enabled"
Root wise, I'm pretty sure it is, but yes, not sure how I double check!

boomhaueruk said:
Thanks.
OK. So, I've attached a few pics to show you where I am.
Booted, checked into Magisk for those settings. I can see 'Magiskhide', so I can untick that, but how do I ensure "Magisk has "MagiskHide Props Config" and "Busybox For Android NDK" and root fully enabled"
Root wise, I'm pretty sure it is, but yes, not sure how I double check!
Click to expand...
Click to collapse
They are Magisk modules, you go to there the puzzle piece is and search for them.

boomhaueruk said:
Thanks.
OK. So, I've attached a few pics to show you where I am.
Booted, checked into Magisk for those settings. I can see 'Magiskhide', so I can untick that, but how do I ensure "Magisk has "MagiskHide Props Config" and "Busybox For Android NDK" and root fully enabled"
Root wise, I'm pretty sure it is, but yes, not sure how I double check!
Click to expand...
Click to collapse
OK, found 'root checker' on the play store. And Termux.
so I have root.

K14_Deploy said:
They are Magisk modules, you go to there the puzzle piece is and search for them.
Click to expand...
Click to collapse
Ah! Got it. Ok, went into Magisk, went to the puzzle piece, found them both and...
Ah, I've just seen you've said "I'd recommend moving to 18.1 before doing this, you'll have to start from square 1 but it means you're more up to date and won't have to do it again until someone builds 19.1 for this device. Can confirm, that build works."
Right. I'd better go and find all the instructions for that. I've forgotten how I got this thing onto custom firmware, but I've got recovery installed.

boomhaueruk said:
Ah! Got it. Ok, went into Magisk, went to the puzzle piece, found them both and...
Ah, I've just seen you've said "I'd recommend moving to 18.1 before doing this, you'll have to start from square 1 but it means you're more up to date and won't have to do it again until someone builds 19.1 for this device. Can confirm, that build works."
Right. I'd better go and find all the instructions for that. I've forgotten how I got this thing onto custom firmware, but I've got recovery installed.
Click to expand...
Click to collapse
Go to the 18.1 thread on this forum and look for the instructions for flashing without being on stock. Also use TWRP 3.4.0.0. You will need a computer, as you have to wipe internal storage and use ADB.

K14_Deploy said:
Go to the 18.1 thread on this forum and look for the instructions for flashing without being on stock. Also use TWRP 3.4.0.0. You will need a computer.
Click to expand...
Click to collapse
I may stay where I am on Android 9. I've just seen it doesn't support sim and I sort of need that.
I can always come back and do that later, right?
I'm a bit worried about bricking it too. I might just get myself onto Android 9 working with the fix for now. It took me so long to get it onto custom rom the first time.

boomhaueruk said:
I may stay where I am on Android 9. I've just seen it doesn't support sim and I sort of need that.
I can always come back and do that later, right?
I'm a bit worried about bricking it too. I might just get myself onto Android 9 working with the fix for now. It took me so long to get it onto custom rom the first time.
Click to expand...
Click to collapse
Yeah of course, but you will have to start over if / when you upgrade

Ah. Hit a snag.
You said "Type '2' for 'Lenovo Tab 4 8 Plus TB-8704F (8.1.0)"
I've got the TB-8704L, the 10 inch.
Let me see if anythings listed.