I recently got a new tablet, the Digiland DL701Q, after my last tablet, the Galaxy Tab 2, broke from a cracked screen. Its not a well known tablet, but it was $50, so I said what the hell, let me take it. I rooted my last tablet through specific instructions from a video, however I can't find any videos or even articles on how to root this anywhere. Since I have no expertise in this area, I was wondering if anyone can help me root my tablet. Any help at all would be appreciated, thanks.
I need to root this puppy also, so someone please help!
the custom version of Android they have does not run correctly with my web program I am using it for.
EvilPenguin42 said:
I recently got a new tablet, the Digiland DL701Q, after my last tablet, the Galaxy Tab 2, broke from a cracked screen. Its not a well known tablet, but it was $50, so I said what the hell, let me take it. I rooted my last tablet through specific instructions from a video, however I can't find any videos or even articles on how to root this anywhere. Since I have no expertise in this area, I was wondering if anyone can help me root my tablet. Any help at all would be appreciated, thanks.
Click to expand...
Click to collapse
I just rooted the one I picked up, go here http://www.mgyun.com/en/getvroot Download that and let it install. Then turn on usb debugging on the tablet, connect it and let it install the misc stuff. Once root is clickable click it, Reboots and comes back up. Should be rooted but use a Chinese app. Download root checker to verify and on the pop up hit the right button. Once passes download supersu from market, open it to install hit the left option on the popup, click the check mark box and right button. Then do the restart supersu asks for, wait for a reboot and verify supersu can grant access with root checker.
Now if you get 3 Chinese apps two you can uninstall but the original one like supersu you can't. Download root browser from market got to system>app and look for irootsu.apk. (Also may have a SuperUser.apk Delete it as well) Long press and delete followed by enjoy I also played with the app they have so may have been where some apps came from you may find you don't have.
---------- Post added at 10:06 PM ---------- Previous post was at 10:05 PM ----------
Just curious bestbuy black friday btw?
Gracias
2fast4u88 said:
I just rooted the one Download that and let it install. Then turn on usb debugging on the tablet, connect it and let it install the misc stuff. Once root is clickable click it, Reboots and comes back up. Should be rooted but use a Chinese app. Download root checker to verify and on the pop up hit the right button. Once passes download supersu from market, open it to install hit the left option on the popup, click the check mark box and right button. Then do the restart supersu asks for, wait for a reboot and verify supersu can grant access with root checker.
Now if you get 3 Chinese apps two you can uninstall but the original one like supersu you can't. Download root browser from market got to system>app and look for irootsu.apk. (Also may have a SuperUser.apk Delete it as well) Long press and delete followed by enjoy I also played with the app they have so may have been where some apps came from you may find you don't have. [COLOR="Silvel
You'reIZE=1]---------- Post added at 10:06 PM ---------- Previous post was at 10:05 PM ----------[/SIZE]
[/COLOR]Just curious bestbuy black friday btw?
Click to expand...
Click to collapse
Thanks for the site, but didn't work... I just ended up with a bunch of Chinese apps and my antivirus giving alerts every 2 second that this was spyware. It worked flawlessly until I had to verify that it worked, which then root checker told me it didn't. I tried it three times, with and without my antivirus. It looked like a nice go, but got any other ideas? Any help would be appreciated. (BTW, yeah, I did get it at best buy. You too?)
ok I downloaded this file. called unconfirmed291871.crdowload
What do I do with it
nothing can read it??
2fast4u88 said:
I just rooted the one I picked up, go here http://www.mgyun.com/en/getvroot Download that and let it install. Then turn on usb debugging on the tablet, connect it and let it install the misc stuff. Once root is clickable click it, Reboots and comes back up. Should be rooted but use a Chinese app. Download root checker to verify and on the pop up hit the right button. Once passes download supersu from market, open it to install hit the left option on the popup, click the check mark box and right button. Then do the restart supersu asks for, wait for a reboot and verify supersu can grant access with root checker.
Now if you get 3 Chinese apps two you can uninstall but the original one like supersu you can't. Download root browser from market got to system>app and look for irootsu.apk. (Also may have a SuperUser.apk Delete it as well) Long press and delete followed by enjoy I also played with the app they have so may have been where some apps came from you may find you don't have.
---------- Post added at 10:06 PM ---------- Previous post was at 10:05 PM ----------
Just curious bestbuy black friday btw?
Click to expand...
Click to collapse
sirtronics said:
ok I downloaded this file. called unconfirmed291871.crdowload
What do I do with it
nothing can read it??
Click to expand...
Click to collapse
That is an unfinished Chrome download. You need to download that file again lol
Sent from atop my space unicorn
Ok so I used IE to download, but my anti virus says it is malware and wont let me open it...
sparky_005 said:
That is an unfinished Chrome download. You need to download that file again lol
Sent from atop my space unicorn
Click to expand...
Click to collapse
Don't bother...
Don't bother, I went through all that as well. I disabled my antivirus, my firewall, let it download, run, and connect to my tablet, yet it still produced no result. The program said my device was rooted, however once I downloaded root checker it said that it wasn't... I even tried Kingo to no avail, (its the same auto-rooting thing but only made in America for Americans), and I have been looking anywhere to root this thing. I'm betting now that the only thing that'll work is an manual rooting process, however if anyone has any ideas I'd be glad to try them. Thanks.
Doesn't work ehh? Being a old dev that quit and hasn't posted here for awhile. I wouldn't come back to just post something to screw with you guys. It does work and here you go as I snapped these laying in bed. As I happened to be bored, remembered I had posted it here so decided to check back. It might detect as malware as I never scanned anything honestly as didn't care to. I guess if you guys can't figure it out I can unroot it and post screenshots with steps but really isn't that hard. But won't be till I actually get a chance to do so.
Also once you gain root with the non english app you have to install supersu as I had said previously.
---------- Post added at 11:37 PM ---------- Previous post was at 11:32 PM ----------
Sorry for the large pics and iroot isn't the same as kingo btw :good: As just because is a one click solution doesn't mean that it uses the same exploit. Another thing the tablet isn't even actually locked if you want to root it via adb.
---------- Post added at 11:58 PM ---------- Previous post was at 11:37 PM ----------
Just connected it to wifi and see it has a ota in which it blocked other root methods and removed root access via adb. So the above may not work if you took it as I haven't did it yet.
iroot works, even after the update. You need to give root permission in Chinese version of SU and you will be good to go. Install English version apps/uninstall all the Chinese and you're set. I didn't find any need to disable antivirus etc., just make sure your drivers are installed.
I'll give it another try, and just to be clear, here is what I should do: First, download the program, let it install the drivers. Let it do the rooting process and restart. Then I should install SuperSU and have it restart like it says to. After all that I should install and check the root using Root Checker? If it works I'll get back to you guys, I think I forgot to install SuperSU before using root checker.
Protocol 9 said:
iroot works, even after the update. You need to give root permission in Chinese version of SU and you will be good to go. Install English version apps/uninstall all the Chinese and you're set. I didn't find any need to disable antivirus etc., just make sure your drivers are installed.
Click to expand...
Click to collapse
Speaking of rooting after the update...Would anyone be able to post or PM me the FWUpgrade.apk/FWUpgrade.odex files from the system/apps folder? I moved those files from that folder on my device to prevent the update to prevent losing root, but then they accidentally got deleted (DOH!) from where I put them. If iroot does work on the DL701Q after the recent update, I'd like to get it on there and re-root, but I can't do it now with the updater files missing!
PM sent, no odex for those files. I am working on a quick guide to help with iroot and install of TWRP, including getting touch to work...
Screenshots/rooted 4.4.0 A86_V004 w/TWRP Touch Recovery Installed
DL701Q/Root Guide, Install TWRP Touch Recovery
Please use link to go to updated guide, this will save me from trying to update both copies, any feedback welcome to help make the guide better or more useful is welcome.
Thanks, Proto
Updated Guide
Protocol 9 said:
Go ahead and system/wireless update your tablet to 4.4.0/A86V_004.
Download SuperSU from the play store
Download/extract the iroot installer to your DESKTOP. iroot download page
Insure that you have all drivers installed, the automatic installs should suffice but you may need to boot into fastboot (hold volume down/power until menu comes up, use volume key to select fastboot and connect to pc), mode seperately in order to get the(M65XX) driver, if the iroot program doesn't automatically install.
Run iroot as Administrator, when complete, it will tell you in English that the you have root, however the SU toast notification will be in Chinese. Click the left icon to grant su permissions to continue. You may get a couple of Chinese apps that piggy back on the download, no worries, you can delete them later, they seem to be system cleaners/task managers.
Go ahead and back out of all of that and disconnect your tablet. Run you SuperSU app. Again the Chinese version may ask you to grant permission. Go ahead and click the left character in the notification to grant. Once SuperSU has permissions you are free to administer root privileges as you would on any other device.
Ok on to the tricky stuff, (well, hopefully not for you)
Again go ahead and download/extract this to your desktop. Easy Magic TWRP Installer for MTK devices w/ubifs
Connect your tablet to PC w/USB Debugging on.
Run the executable as Administrator. You will need to run this install MANUALLY in order to get the touch screen orientation correct the first time.
Download and copy the stock recovery from the link below somewhere on your pc.
Start the program and select NO for manual.
You will be prompted to place stock recovery in the STOCK folder, go ahead and copy it in there.stock recovery image
Follow the rest of the prompts, if the program does not detect your resolution it is; 1024X600.
You will be asked if you have a flipped screen, click YES
You will be asked if you have touch screen problems, click YES
You will then be presented with a selection of screen orientation options, click the radio button for Normal Screen Swap XY Flip Y
The program will then continue with the installation and boot into recovery (TWRP Touch). If everything is correct, you should have fully functional touchscreen functionality (although it seems upside down, buttons on left).
Use the stock recovery below for unpack/repack if you get into trouble and lose stock (English) recovery, (you won't effect the actual chinese stock recovery):
stock recovery image
Don't forget that this device has a reset button on the back which will assist you to boot up normally, should you run into problems. Best of luck.
If you feel that you have hosed up your recovery through any attempts, I will assist you in returning to stock, which can also be pushed by the TWRP installer. Please give credits/thanks to the great teams that created the iroot and Easy Magic installers. This is simply a guide I created none of the programs or content.
Disclaimer: What you do with your device is your own responsibility, these instructions are offered as a guide, please post any shortcuts or errors you may find for the benefit of the community..
Click to expand...
Click to collapse
I really don't mean to be a nuisance, but this stupid thing still isn't working for me. I downloaded iroot, let it run, and at the end it said my device was rooted. I started up SuperSU, and it said something like the SU binary needs to be updated, and I let it update, only to have it say it failed. I don't get what I'm doing wrong, my tablet is up to date, my computer is up to date, I reinstalled iroot and supersu multiple times, and restarted everything like 5 times. Also, root checker says its not rooted, however it also says the system appears to be running very slow. Do any of you mind explaining the steps like you would to a five-year-old? I feel like an idiot not being able to do this.
Not at all, it took me several attempts to get this to work, wait for the actual Chinese SU notification to show up to approve, this seems to be hit an miss.
Protocol 9 said:
Not at all, it took me several attempts to get this to work, wait for the actual Chinese SU notification to show up to approve, this seems to be hit an miss.
Click to expand...
Click to collapse
EvilPenguin42, first of all make sure you are downloading and using the PC version of iRoot (version 1.7.9 right now), not the one that you download as an apk and run straight from the tablet. The latter one does not work (it may say rooting succeeded but when you reboot you aren't rooted). Protocol 9's instructions might not have been clear about that distinction.
Note added for PC Version, thank you...
I'm using the PC version, I've tried the apk one as well to no avail, but does the SU notification comes up on your computer? Where am I supposed to see it? Also,do you mean I have to re-root it multiple times using the program? And probably should've asked this sooner, what does SU mean and the SU binary in SuperSU? I'm sorry for being an idiot, but I miss being able to use root privileges. Thanks in advance
EvilPenguin42 said:
I'm using the PC version, I've tried the apk one as well to no avail, but does the SU notification comes up on your computer? Where am I supposed to see it? Also,do you mean I have to re-root it multiple times using the program? And probably should've asked this sooner, what does SU mean and the SU binary in SuperSU? I'm sorry for being an idiot, but I miss being able to use root privileges. Thanks in advance
Click to expand...
Click to collapse
Sent you a PM, lets try to start from scratch.....
Related
I'm a complete noob and I've searched the forums and can't find an answer to my questions. (I'm sure there's some answer in Japanese on a Japanese forum somewhere, but my Japanese is not up to that level.)
I have a Toshiba Regza IS04 from AU (in Japan).
Running Android 2.2.2
Baseband Version 5014.1907.39
Kernel Version 2.6.32.9-rel [email protected] #1
Build Number FFK300
I have been researching rooting on and off for months since I first got the phone and have decided I would like to root it. My reasons for rooting:
1. I want to get rid of all the apps that were pre-installed that I don't use.
2. I would like to have the latest version of Android 4.0 Ice Cream Sandwich. (I doubt that another authorized upgrade from au is ever going to happen, since the 2.1 to 2.2 upgrade.)
It seems from reading forums that there are special builds of an OS depending on the phone?
My questions:
1. What is the best way to backup my phone before rooting?
2. What would be the best rooting method for my phone (SuperOneClick?)?
3. How can I (or even can I) upgrade my Android to 4.0?
Thanks for any help!!
Sam
To answer my own question, in case any one else wants to know:
Okay... it looks like I cannot post external links... until I post 8 times, which I don't really predict doing... so I'm going to try just removing the http at the beginning and see if it will go.
Superoneclick v2.2 does NOT work with this phone. It gets through "Rooting device... Step #7" but cannot remount.
Unrevoked does not work.
Z4root also does not work.
But I found a Japanese site with directions that did work! YES!!
hibari.2ch.net/test/read.cgi/smartphone/1320415141/
Somewhere in the page was the following information and link:
■auto_rootkit_is04_v0.5+suhax
hotfile.com/dl/134084004/f59084e/auto_rootkit_is04_v0.5suhax.zip.html
I downloaded the zip file and extracted it. I clicked on adb.exe first and then clicked on the auto_rootkit_is04 batch file. I just hit enter after each step. (It's in Japanese, but all it says is each step it is doing and then to hit any key.)
The first time I ran it, it did not work. The second time, I turned my phone off and on again before trying anything, and bingo: I had root!
Some of the Japanese threads were saying something about the problem with superoneclick was that the is04 took too long to mount and so there was an error. At least, I think that's what it said. My Japanese is okay, but not always good enough for this type of stuff.
I hope this can help someone else.
Thank you so much for this response!
I have the same phone, and I've been wanting to root it for a long time. There were so many pre-installed applications that are just hogging room, especially since I can't read Japanese well enough (yet).
-T
I hope it works for you too!
I spent probably the equivalent of 2-3 days searching over the last few weeks, but couldn't find anything that I was comfortable with trying.
This morning, I finally got the nerve up to try superoneclick and was really disappointed when it wouldn't work. Then I started trying all kinds of methods, and about 8 hours later finally came across the method that worked!
It's probably the only thing frustrating sometimes about having a Japanese phone: lack of English support!
Now I'm just hoping I don't break it! I'm backing up all the apps with Titanium backup before I start deleting them one by one. I would hate to delete something that is crucial to the system and not be able to restore it. I'm also looking into other ways to backup the system.
One word of warning. Your au one market will not work unless you do one more step. It's mentioned in English in the readme file. I didn't bother because I never download from it anyway. (Although, I probably should just so I'll keep getting updates on some of the J apps that I do have.)
Deleted
Deleted
the rootkit d/l has been removed. anyone know where to get it?
The File
I'm not sure if this is against the forum rules, but I have a copy of the zip file (well, a zipped up copy of the folder) from my computer. If you pm me, and I can send you it.
-T
■auto_rootkit_is04_v0.5+suhax
hotfile.com/dl/134084004/f59084e/auto_rootkit_is04_v0.5suhax.zip.html
link die;
anyone help me another link for that file & help me root this device step by step?
Thanks
The post above dissolution said they had one, but good luck getting a reply. I'm emailed twice and nothing.
私はローボーボブ。 Haro！！
Latest rootkit for FFK300
Here is the latest rootkit,
IS04 root toolkit ver 4.0.1
http://www1.axfc.net/uploader/Ne/so/131631
DL key ; is04
And other informations;
- Custom kernel(overclock, compcache, +others)
http://marijuana.ddo.jp/is01/index.php?moddir=downloads&action=visit&cid=9&lid=47
- Custom kernel(CWM on ramdisk, ported from Xperia, modUI)
http://www.mediafire.com/?jkz5nek59y3hpaf (reported kernel unstable)
# FFK301 stock ROM update - (rootkit does not work, still can be rooted.)
http://spf.fmworld.net/sw_update/kddi/is04/update/
- scroll to bottom and click on blue rectangle.
# kernel source code
http://spf.fmworld.net/oss/is04f/index.html
- some files are missing, extract them from T-01C(DoCoMo).
http://www.fmworld.net/product/phone/sp/android/develop/t-01c_froyo_oss/
help! rooting regza inquiry..
[/COLOR]
samkk75 said:
To answer my own question, in case any one else wants to know:
Okay... it looks like I cannot post external links... until I post 8 times, which I don't really predict doing... so I'm going to try just removing the http at the beginning and see if it will go.
Superoneclick v2.2 does NOT work with this phone. It gets through "Rooting device... Step #7" but cannot remount.
Unrevoked does not work.
Z4root also does not work.
But I found a Japanese site with directions that did work! YES!!
hibari.2ch.net/test/read.cgi/smartphone/1320415141/
Somewhere in the page was the following information and link:
■auto_rootkit_is04_v0.5+suhax
hotfile.com/dl/134084004/f59084e/auto_rootkit_is04_v0.5suhax.zip.html
I downloaded the zip file and extracted it. I clicked on adb.exe first and then clicked on the auto_rootkit_is04 batch file. I just hit enter after each step. (It's in Japanese, but all it says is each step it is doing and then to hit any key.)
The first time I ran it, it did not work. The second time, I turned my phone off and on again before trying anything, and bingo: I had root!
Some of the Japanese threads were saying something about the problem with superoneclick was that the is04 took too long to mount and so there was an error. At least, I think that's what it said. My Japanese is okay, but not always good enough for this type of stuff.
I hope this can help someone else.
Click to expand...
Click to collapse
hi!
I am a newbie here and like you all, I would also like to root my regza phone. Can someone give a working auto_rootkit because the link above is not working. I have searched it as well on the net but still all will lead me to dead hotfile link. Or someone could send me the file instead to my yahoo mail [email protected] tnx in advance
And also i have downloaded this rootkit instead from IS04 and downloaded. After dowloading, I click the adb file and it appears a command screen with commands running so fast. Next i did click the root file and there appeared a command screen with all sorts of command running so fast. My question is, i did not received any confirmation that the rooting process was succesfull. And also i have read to other forums that one thing you will notice that rooting was successfull is that 'superuser" will be automatically installed.
Please help me on this one. To be honest I started exploring this process since i have this phone and there are apps that i wanted to uninstall not unless i root the phone.
Thank you in advance
marvz,
Dissolution said:
I'm not sure if this is against the forum rules, but I have a copy of the zip file (well, a zipped up copy of the folder) from my computer. If you pm me, and I can send you it.
-T
Click to expand...
Click to collapse
hi there!
Can you send to my e-mail [email protected] the said file so that i could root my regza phone?
thank you for your help> ^_^
Question to get root on phone regza
samkk75 said:
To answer my own question, in case any one else wants to know:
Okay... it looks like I cannot post external links... until I post 8 times, which I don't really predict doing... so I'm going to try just removing the http at the beginning and see if it will go.
Superoneclick v2.2 does NOT work with this phone. It gets through "Rooting device... Step #7" but cannot remount.
Unrevoked does not work.
Z4root also does not work.
But I found a Japanese site with directions that did work! YES!!
hibari.2ch.net/test/read.cgi/smartphone/1320415141/
Somewhere in the page was the following information and link:
■auto_rootkit_is04_v0.5+suhax
hotfile.com/dl/134084004/f59084e/auto_rootkit_is04_v0.5suhax.zip.html
I downloaded the zip file and extracted it. I clicked on adb.exe first and then clicked on the auto_rootkit_is04 batch file. I just hit enter after each step. (It's in Japanese, but all it says is each step it is doing and then to hit any key.)
The first time I ran it, it did not work. The second time, I turned my phone off and on again before trying anything, and bingo: I had root!
Some of the Japanese threads were saying something about the problem with superoneclick was that the is04 took too long to mount and so there was an error. At least, I think that's what it said. My Japanese is okay, but not always good enough for this type of stuff.
I hope this can help someone else.
Click to expand...
Click to collapse
Hi
I have this phone too. And I try to get root, you can send for me the link of you downloaded and explain for me how you made it.
Other question, I can use this phone to call in brasil?
Thank you.
:good:
My phone just had this phone and I'm trying to update it before rooting. It came with 2.1-update 1 OS version and I'm trying to update the phone to it's latest official 2.2.2.
I've downloaded the necessary 256mb file update but it didn't work. Even tried using the recovery but is still not working.
Based on my research about this phone, There's no way to update without the phone downloading the app from the official website, using the SIM and au logins.
We've lost the sim (UIM) card that came with the phone. So I guess its stuck on its current OS. I'm having trouble installing apks (Gingerbreak and even normal apps) as it always gives me the error "parsing error" or something.
Is there anyone could help?
EDIT:
I have successfully updated the phone from Android 2.1-update1 to Android 2.2.2.
Download all the necessary files here:
http://www.fmworld.net/product/phone/is04/
I have used the method of updating from the least upgrade and up to the latest. I have managed to download 3 separate files for the upgrade, namely:
IS04_RC2_RC3RE_DL.zip
IS04_RC_4.zip
IS04_TO_SP_FYRC_4.zip <- froyo update
I have extracted all the files on the sd card. make sure that the ".enc" file is found on the root of the SD Card and on the "prg" folder.
I have updated it using the recovery mode (power + volume up + camera button).
I am now currently trying to Root the device using Gingerbreak and seems that it's taking too long to root.
Also. I have able to root the 2.1-update OS using z4root.
help me
hi.. i didn't my phone plz send me ...................................................auto_rootkit_is04_v0.5+suhax
hotfile.com/dl/134084004/f59084e/auto_rootkit_is04_v0.5suhax.zip.html
thnxx.. in advance..
Root
I rooted mine with http://unlockroot.com/
root_toolkit_is04_v4.3.zip
www1[dot]axfc[dot]net
/uploader/Ne/so/135399
Password is "is04".
suhax
www[dot]4shared[dot]com
/zip/pHLT8kqe/suhax.html
Sent from my IS04 using xda premium
more detail please
samkk75 said:
.....
I downloaded the zip file and extracted it. I clicked on adb.exe first and then clicked on the auto_rootkit_is04 batch file. I just hit enter after each step. (It's in Japanese, but all it says is each step it is doing and then to hit any key.)
The first time I ran it, it did not work. The second time, I turned my phone off and on again before trying anything, and bingo: I had root!
.....
.....
I hope this can help someone else.
Click to expand...
Click to collapse
Thx so much for your posts.
I am so glad to finally find someone with the same phone, the same problem and intentions
I do, however, need more info:
Did you extract the files into any particular folder? You obviously hooked up in de-bug mode, but did you command prompt anything?
I tried your steps but get nothing to 'hit enter' on. I have also tried the other (different version) toolkit.
You can IM me or email or post or come around and root my phone yourself - I will sell you my car, house, wife...
... as you can tell I am a little frustrated ...
lets just IM/email for now
Thx in advance,
Kaz
---------- Post added at 12:34 PM ---------- Previous post was at 12:29 PM ----------
orgia82 said:
I rooted mine with http:!!unlockroot*com/
Click to expand...
Click to collapse
Didn't get to try it - was too tied down with all the additional ^%$&#$ I had to download to get to it.
help
as everyone can see that link isnt working anymore,so im here asking someone whos still have it to upload :fingers-crossed: again．．．．
It looks like we have to move our discussion here, so I went ahead and started a thread.
As of now, there is root for the mediapad, but the only way to root the springboard is by flashing it with a rooted mediapad cust.img - which gives you root but loses your 4g.
So for us Springboard users, we either need root or a way to get 4g back if flashing it as a mediapad. Anybody with thoughts or leads or any know-how?
Finally,
Special room for Huawei Media Pad created,
Thanks to TS
I'm very glad,
Now i'm waiting the master in here to modified this device
cause i still newbie
Actually I Prefer The 3G More THan The 4G For Some Reason I Felt 4G Wasnt Stable Enough....So Im Enjoiying My Mediapad In 3G More Than My Springboard In 4G......
from the other thread, Rumbi wrote:
Yap, only thing you have to do is install Superuser and Busybox from Market and copy "su" from /hwcust/oversea_hk/preload/fixed/bin/ to /system/xbin (e.g. with ES File Explorer with root and r/w enabled), and you are ready to go
I've installed SU & BusyBox. I cannot move the SU file over to /system/xbin. A message tells me that I am not root.
However, when I run Root Check Basic I am told I have root.
I ran Root Check before & after I installed S7-301u V100R001C232B012(Root_version) and Root Check said I did not have root.
So the real question is, How do I really know if I have root?
*****
Actually I installed BusyBox Installer. I'm asked to pick a version to install:
1.19.3
1.19.2
1.18.5
1.18.4
1.17.1
None of these will install.
I also have the option to install a "Custom Tune" is there one? I'd gladly pay for BusyBox pro to get BusyBox running
*******
I powered off the device. Put my sdCard back in (the rooted firmware was removed from it). Then installed the SuperUser update from the market.
Ran that - it said everything was OK. Then I forced it to update - it crashed - so I force closed it. I then realized I could not run the original SuperUser app anymore.
Next, I opened up Root Explorer and was able to move the su file over to the xbin. But now BusyBox is not acting right - It said that it was having problems installing, and I'd need to reflash (or reload - I can't recall) the rom.
I'm rebooting, and going to try to install BusyBox....to be clear on which BusyBox..it's this one:
https://market.android.com/details?...t=W251bGwsMSwyLDEsInN0ZXJpY3Nvbi5idXN5Ym94Il0.
*****
Just realized in Root Explorer, to tap the little gray box at the top. After you tap it it should read "Mount R/O"
Now you can long press a folder/file and change the read/write permission.
Rumbi,
You said to r/w enabled the su file....is that check ALL the boxes?...Read, Write, Execute Special?????
IIRC, i had some problems with busybox, too. Copy the file from the attachment to /system/xbin and try the installer again.
And i said to enable r/w support for the /system folder. There are two checkboxes in ES File Explorer. First checkbox is enable root permission for ES File Explorer and second checkbox is "Mount / and /system writable".
Now you should be able to copy whatever file you want to /system/xbin. That's how i have done it. If you have any further questions, feel free to ask. I'll try to explain.
PS. You don't ne to alter file permissions of the su-binary but mine are "rwx r-x r-x".
Rumbi, how do you feel about the High resloution mode, does it slow the tablet down? Have you had a chance to use any tegra 2 devices and if so how does the mediapad with the snapdragon compare when in standerd/high-res mode?
Nothing to complain about the Hi-Res-Mode but i don't have any Tegra2-Devices to compare, sorry.
Haven't tried any games in hi-res-mode but normal usage is just fine.
Thanks. Ill try this out. When i try to install busybox it hangs first, then i force close and run again. Then i get the message about reflashing Rom. But i know i have root. I installed connectbot and ran su and got #
Heres how i got root (im away from my pc right now so i try to be as accurate as possible) :
Installed Hauwei modified rom (its the one that says "(root) " in the file name.
Installed Root explorer
Installed Superuser
Install busybox
Install Connectbot
Put my microsd back in (with the firmware AKA dloa folder removed)
I could not get root explorer to allow rw permissions until i slid the sd card out and back in whil the device was on.
Then i ran connectbot as local and typed su hit enter then superuser popped up asking fo allow connectbot to access. Hit allow an type su hit enter an you should get # This took 3 reinstalls of the firmware to work wjthout errors. The first times resulted in superuser needing to be force closed.
I also ran superuser and went into settings and updated it eventhouh its not neede. There i got a read out saying that busybox is not installed, but it does say i have root.
Sent from my HUAWEI MediaPad using xda premium
Honestly i havent noticed a big difference between high resolution an standard.
The only issue with high res is the small icons and buttons are difficult to hit sometimes
Sent from my HUAWEI MediaPad using xda premium
Do i need to unzip this file first?....
.... Nevermind... I unzipped it and put the busybox file in th system/xbin folder.
I installed busybox installer by JRummy16. This time and it worked!!!!!!!
Now its on to figuring out 4G and tryiying to use it as a phone.
What is the xml file i need to edit?
Sent from my HUAWEI MediaPad using xda premium
Good, that you have worked it out now What exactly do you want to do? To get to the hidden menu, you have to open the calculator and type: ()()2846579()()=
To edit the XML-Files, you have to extract the cust.img... But now that you have root, yo can edit whatever is available via root explorer
€dit: To get 4G working again, maybe with someone with an original Springboard (not a flashed one) can copy the folder /system/lib/. This should be possible even without root. I think it has something to do with the ril-files...
after updating my mediapad to S301uV100R001C232B012, i have problem with 2x Client (RDP client) now, few second after conecting to rdp session, is app 2X client crashing, with error 2x Client has stopped unexpectedly (process com.tux.client), is here anybody with this problem? thanks...
Rumbi said:
€dit: To get 4G working again, maybe with someone with an original Springboard (not a flashed one) can copy the folder /system/lib/. This should be possible even without root. I think it has something to do with the ril-files...
Click to expand...
Click to collapse
How about this - link
I'll look at it, thank you And these are the libs from an unmodified Springboard, aren't they?
yes indeed. I broke the silly thing, so I haven't played with it much. guess I will have to call about how to get it fixed.
knoxjon said:
How about this - link
Click to expand...
Click to collapse
Even though I have no clue of what to do with this, THANKS! I tried to open an .so file in notepad, but no luck, but I'm assuming that the geniuses here know what to do.
On an off-root topic - How do you take a screen cap? I accidentally did it yesterday while my MediaPad was lagging, but don't know how I did it.
The Hi Suite that comes with the device can do this, but require a computer and usb hooked up. Useful, but not as practical as doing it from the tablet itself.
The *.so files are a bit like drivers for the internal components. I'll try to find differences between T-Mobile and Huawei so maybe we get 4G working again.
tedbone said:
Even though I have no clue of what to do with this, THANKS! I tried to open an .so file in notepad, but no luck, but I'm assuming that the geniuses here know what to do.
On an off-root topic - How do you take a screen cap? I accidentally did it yesterday while my MediaPad was lagging, but don't know how I did it.
The Hi Suite that comes with the device can do this, but require a computer and usb hooked up. Useful, but not as practical as doing it from the tablet itself.
Click to expand...
Click to collapse
I'm not sure how to screencap. It's so easy on CM that I've gotten lazy. Plus I rarely do it. I know there are a ton of apps for that, tho. But you could probably google "gingerbread screen capture" and find a better answer. But not with gingerbread. I'm blanking on the name for this version of android.
knoxjon said:
I'm not sure how to screencap. It's so easy on CM that I've gotten lazy. Plus I rarely do it. I know there are a ton of apps for that, tho. But you could probably google "gingerbread screen capture" and find a better answer. But not with gingerbread. I'm blanking on the name for this version of android.
Click to expand...
Click to collapse
Honeycomb
I've been Googling searches like that, and end up with actual screen shots of Honeycomb os..I'll keep looking...
Tried this (from here), but no luck:
Screen capture
Android natively supports the ability to capture a screenshot by method of pressing both the power and volume-down buttons at the same time on an Android device. This native support was first included within the Android 4.0 (Ice Cream Sandwich) update, which is first seen on the Galaxy Nexus smartphone.[86] Previously, Android did not feature native support for screen capturing which would have likely been due to security concerns. Furthermore, prior manufacturer and third-party customizations as well as using a PC connection (DDMS developer's tool) were the only known methods of capturing a screenshot on Android.
I've looked through the *.so files and many of them are exactly the same, but some are different. One file caught my interest. I've attached it here for anyone who wants to try. Please only use it, if you have a T-Mobile Springboard with flashed root Firmware. Copy the content of the zip-file to /system/lib and overwrite the existing file. But make a backup first! After copying you have to set the correct file permission (rw- r-- r--) and reboot the tab. Hopefully 4G works again with this little trick.
Hi all,
First off, just want to say thanks to all of the hardworking devs out there that put a lot of time and effort into these projects. You guys are really awesome!
Secondly, I tried to post this as a reply in the developer's forum, but didn't have enough posts to qualify.
That all being said, I followed all of the instructions in Indirect's post here, but can't get the Nook Tablet to bring up recovery mode when I reboot. It just continues to load the standard B&N image. I even tried a factory reset to see if that would work, but same problem. I verified that the files on the micro-SD card match those as shown in Albert's excellent video here. The device is still running 1.4.0.
Any assistance is greatly appreciated!
No luck here either...I tried the root while watching Albert's You Tube video at the same time. I think the significant thing is that my screen displays something like:
Extracting files to SYSTEM...
Setting SYSTEM:bin/su permissions to 06755...
Creating SYSTEM:xbin/su symbolic link...
Installation Complete!
Install from sdcard complete.
Whereas the screen in the video shows:
Extracting files to SYSTEM...
Setting SYSTEM:bin/su permissions to 06755...
Creating SYSTEM:xbin/su symbolic link...
Installing GApps 29110878
For Android 2.3.5 Customized for the nook tablet
Mounting data...
Extracting files to data...
Unmounting data...
Install complete. Enjoy!
Installation Complete!
So clearly my install seems to silently abort somewhere in the middle...
Any insight or advice would be appreciated!
Removed...
~ Veronica
Sent from XDA premium using my Nook Tablet
Beatbox,
Just re-reading your post I think I got farther than you, but also got stuck on your issue earlier. If you keep the Nook plugged into the PC via the USB cable during the power on, the Nook will boot into the recovery mode - that at least was what got me past your issue.
It's not about Rooting OR recovery. It's about the fact that this method is still being worked on. Indirect has been making modifications to the various files and it is my opinion that the file used in Albert's video is NOT the same file that would be downloaded if you went and obtained it right now.
I would wait this out until Indirect writes an updated post explaining that the method is finalized.
If this is not an option the original root method works perfectly.
Land - when you say "original root method" are you talking about something that predates Albert's solution?
jearley9 said:
Land - when you say "original root method" are you talking about something that predates Albert's solution?
Click to expand...
Click to collapse
See this Thread
If you are running 1.4.1 you will need to downgrade first.
See Here
jearley9 said:
Beatbox,
Just re-reading your post I think I got farther than you, but also got stuck on your issue earlier. If you keep the Nook plugged into the PC via the USB cable during the power on, the Nook will boot into the recovery mode - that at least was what got me past your issue.
Click to expand...
Click to collapse
Cool jearley9, this did indeed work for me and I was able to load the image. Problem now is that I always end up at the normal B&N Setup screen. Were you able to get past that part?
And thanks to all the other thread participants. I know it takes time to work these things out, so no biggie. We all get a little too excited and impatient with things like these sometimes.
Thanks - looking it over now...
---------- Post added at 02:58 PM ---------- Previous post was at 02:53 PM ----------
Beat,
Does your screen match my screen or the one in Albert's video? If it matches then you and I have the same problem. If not then you have something different going on...
jearley9 said:
Thanks - looking it over now...
---------- Post added at 02:58 PM ---------- Previous post was at 02:53 PM ----------
Beat,
Does your screen match my screen or the one in Albert's video? If it matches then you and I have the same problem. If not then you have something different going on...
Click to expand...
Click to collapse
Definitely matches yours. Just didn't know if you got further than I did after rebooting.
Land Master said:
See this Thread
If you are running 1.4.1 you will need to downgrade first.
See Here
Click to expand...
Click to collapse
Just wanted to provide an update. I attempted the instructions from the original rooting thread (my nook tablet doesn't have 1.4.1 yet, so didn't need to downgrade). When I ran the batch file to root, it detected that the device was already rooted - which I quote from the script, "Is bothersome."
Okay, so i think my device is half-rooted somehow. Just can't get the new home screen that I'm seeing on all the videos. I'll keep you guys updated with my further troubleshooting attempts.
Beat, you and I are at least synchronized - I too tried the original root method, and I had the same exact problem as you describe... a message saying "already rooted". I did a system reset right before I tried the root, so I don't see how it could be "already rooted".
I just purchased my Nook yesterday. I am wondering if there are newer units (mine included) that are more resistant to being rooted?
I'm having the same issue, but I can use the search function to determine that apps WERE installed (and will execute properly). I believe that Indirect has removed ADW launcher and Homecatcher from the zip we're suppossed to drop onto the SD Card. My guess is that we're waiting for him to come up with a solution to the "Market not showing up in launcher" issue.
Can someone confirm this?
Well any other tactics I've tried have been to no avail, so I'll just be patient and wait for Indirect to address it. I'm sure he has enough on his plate without us bugging him.
Many thanks to him again for even working on something like this.
Edit:
Okay, for some reason I missed Albert Wertz's helpful Youtube comment:
Please Vote this comment up so everyone else can read it among all the others. Indirect is making some changes to the script, if you dont get adw to launch right after the first reboot from root, you may have to download it manually from the market. You can use the N button menu search function to pull up market by typing M in the search. You can launcher it from here. Until the bugs are worked out, you may only be able to install from market, sideloading may still be an issue. Indirect is fixin
Click to expand...
Click to collapse
I did this and have no problem bringing up the Android Market now. Just installed an app successfully. Not sure where it lives though. I could only seem to launch it from the Recently Downloaded icon at the bottom bar.
Edit 2:
Okay, just restarted after installing the ADW and now it prompted me to start with it. Only issue I have now is if I hit the N button, it reverts back to the original Barnes & Noble homescreen and I have to reboot to launch ADW again.
I got pretty much to the same place - I downloaded HomeCatcher but that seems to be non-functional - Looks like the Nook home screen is winning this round...
jearley9 said:
Beat, you and I are at least synchronized - I too tried the original root method, and I had the same exact problem as you describe... a message saying "already rooted". I did a system reset right before I tried the root, so I don't see how it could be "already rooted".
I just purchased my Nook yesterday. I am wondering if there are newer units (mine included) that are more resistant to being rooted?
Click to expand...
Click to collapse
To truly "reset" the system run the downgrade I linked previously EVEN IF you are on 1.4.0. After that it will be just like you took the NT out of the box. Then run the Indirect Root Batch and the "you are already rooted" should be gone. I would hope so anyway
Land,
I did the press and hold 9 times and got back to factory state.
Also, I tried Brianf21's files and I got the same problem as you. If I try to open Update.Zip from Windows it gives me "Please insert last disk of a multi-volume set...". I would guess that the zip file is malformed or incomplete, but that's just a guess...
-jearley
jearley9 said:
Land,
I did the press and hold 9 times and got back to factory state.
Also, I tried Brianf21's files and I got the same problem as you. If I try to open Update.Zip from Windows it gives me "Please insert last disk of a multi-volume set...". I would guess that the zip file is malformed or incomplete, but that's just a guess...
-jearley
Click to expand...
Click to collapse
I copied this post to the Development Thread in my recent reply to Brianf21. It is conceivable at this point that you and I are the only ones that have tried this. lol
Please put information regarding future attempts in that thread to help him troubleshoot.
Glad to see that you were able to reset. I don't believe it will be necessary again if Brian fixes the issue. To my knowledge simply entering CWM using his image had NO affect on my NT.
Land,
Sorry I can't comply with your request - the forum software won't let me post in the development area due to my "newness" - I am 53 years old and have 30 years of software/firmware development experience, but to this forum I am a "newbie"
jearley
jearley9 said:
Land,
Sorry I can't comply with your request - the forum software won't let me post in the development area due to my "newness" - I am 53 years old and have 30 years of software/firmware development experience, but to this forum I am a "newbie"
jearley
Click to expand...
Click to collapse
Alrighty then.... I don't know if I should laugh or cry. You can't even "post" in the Dev section? I wonder how many posts you need. Seems a little extreme to me but you will get there soon enough I guess.
In the meantime I'll make sure that your comments are known. Thanks!
Anyone here know their phones well enough to tell me what kind of Root I need?
If anyone can recommend a Root method that might work for the following phone configuration, I'd greatly appreciate it..
My phone is custom built by a Sonim OEM, but factory modified to the Companies own brand.. its comparable to the Sonim A3, at least in outward functionality and durability, being waterproof, etc... but the internal hardware compilation is likely different, but I'm not sure how..
Here is my log from Android System Info.. it says at the bottom, user is root? but I dont have root access.. i ran Root Checker Basic, and it said I dont have a rooted phone.. I also did the terminal test & su was unrecognized and returned $ and not #
Here are the specs:
Android version : 4.2.2
Release Codename : REL
API LEVEL : 17
CPU ABI : armeabi-v7a
Manufacturer : alps
Bootloader : unknown
CPU ABI2 : armeabi
Hardware : mt6572
Radio : unknown
Board : mbk72_wet_jb3
Brand : alps
Device : mbk72_wet_jb3
Display : A8_V1.0
Fingerprint : alps/mbk72_wet_jb3/mbk72_wet_jb3:4.2.2/JDQ39/1378194655:user/test-keys
Host : android
ID : JDQ39
Model : A 8
Product : mbk72_wet_jb3
Tags : test-keys
Type : user
User : root
thanks for any advice or recommendations for possible Root-exploit matches
-
It took them an entire month to make this phone from nothing... and it was kind of done through some back channels, and what not.. probably because it was made off the clock..
so I can't really just go directly and ask the person who built it more details...
so, there isnt any bloatware or anything like that,.. i need root for mostly just the control of functionality and for future apps
-
I cant really wrap my head around the fact that Google wouldnt offer its users an official and simple, built-in Rooting method for its little Android platform.
Carriers who want to prohibit rooting could just remove or block the feature from their own phones, if they chose to do it
In other countries, such as Australia, they require the Phone companies to stand behind warranties for their Phones Hardware, even after its been rooted, and the burden of proof is on the Phone company to prove that any hardware-related problem was caused by the rooting
and many more countries have no such laws or care for anyone rooting their devices
it seems Android is made by Americans, for Americans, and the rest of the world is being dragged along by the neck
-
Actually, I take that back, they arent making phones 'for Americans', they are making them for service providers, not the end user.
Google - has decided that the interests of the Carriers are more important than the needs of the people
Which makes Android not a "Free & Open Source" platform for the people, but a platform built for money-making companies, for the profit-mongering, uber-wealthy telecom giants
Giants which are so wealthy and so powerful, and exist under such a flawed and corrupt system as the U.S Government is, that they are free to influence & control legislation through the use of special-interest lobbyists working for their monetary gain & control and against the people of the United States, to create silly little trash acts like the Digital Millennium Copyright Act.. as if the people were toys or tools existing to line the walls of their offices with gold & silver.
and the other 99.9% of the enslaved American people have no say in that matter.. there wasnt a vote.. it wasn't democratic in any fashion whatsoever, except as far as anything that happens in America they choose to simply call "Democratic", as if propaganda for population control or to keep the wheels of capitalism spinning profits off the wall.. whilst seemingly oblivious to the actual meaning of the term.
and that, in turn, spills over America's borders and fills the rest of the world with similarly sad & pathetic feelings of no self-worth, powerlessness, and subservience to corporate interests... bending the backs of the world's masses, crippling their view of their own personal rights & freedoms, and standing in the world... amazed & in awe that the people in the most developed country in the world and so-called most "Free", are silently taking anything handed to them, just as the people living in regime-controlled governments like North Korea, Cuba, or Iran do.... the only difference being that the power is shifted from Central Governments to mega-conglomerate Self-invested, in-it-to-win-it, profit-above-all, Privately owned & operated Corporations that can never do anything in the best interests of others, nor act in any way other than making the most money, regardless of the type of society they create, how they manipulate and pollute the Government & Political System, and destroy the basic freedoms & rights of the people
Thanks G$$GLE, for playing the game we all know & hate
What happens in America is always in the best interests of Very large, powerful, & privately owned corporations with no other care or concern to anything or anyone other than securing a profitable environment for themselves at any expense, the ends always justifying the means, in their cases.
you can have what you want the moment you become a billionaire and have 20 other Billionaires who want to create a more profitable condition in the market, and can hire the most powerful D.C. Lobbyists in America to Bribe, Coerce, Threaten, Blackmail, Work-Over, Negotiate, Pay-off, Corrupt, Deceive, Trade Political Favors or otherwise Control & Own the Legislators and "good'ol" boys, of the good'ol U.S. of A.
.
chinarabbit said:
Anyone here know their phones well enough to tell me what kind of Root I need?
If anyone can recommend a Root method that might work for the following phone configuration, I'd greatly appreciate it..
My phone is custom built by a Sonim OEM, but factory modified to the Companies own brand.. its comparable to the Sonim A3, at least in outward functionality and durability, being waterproof, etc... but the internal hardware compilation is likely different, but I'm not sure how..
Here is my log from Android System Info.. it says at the bottom, user is root? but I dont have root access.. i ran Root Checker Basic, and it said I dont have a rooted phone.. I also did the terminal test & su was unrecognized and returned $ and not #
Here are the specs:
Android version : 4.2.2
Release Codename : REL
API LEVEL : 17
CPU ABI : armeabi-v7a
Manufacturer : alps
Bootloader : unknown
CPU ABI2 : armeabi
Hardware : mt6572
Radio : unknown
Board : mbk72_wet_jb3
Brand : alps
Device : mbk72_wet_jb3
Display : A8_V1.0
Fingerprint : alps/mbk72_wet_jb3/mbk72_wet_jb3:4.2.2/JDQ39/1378194655:user/test-keys
Host : android
ID : JDQ39
Model : A 8
Product : mbk72_wet_jb3
Tags : test-keys
Type : user
User : root
thanks for any advice or recommendations for possible Root-exploit matches
-
Click to expand...
Click to collapse
You have a device with a MediaTek CPU in it. Use this to root:
http://forum.xda-developers.com/showpost.php?p=43163569&postcount=7
If you need help installing drivers on your PC try www.snappea.com and install on PC, it will install an adb driver that will work for what we need.
Hope this helps!
How is it even possible to make having administrator access to your phone illegal?
"As of March 5, 2013 it is illegal to unlock a phone under the Digital Millennium Copyright Act for use with other carriers without the consent of the carrier. "
How does that even work exactly? it doesnt. It's something the carriers dreamed up to make things conform to their very narrow need to have marketing control, to force the use of their apps, most likely for Demographic & Psychographic information & usage statistics gathering... and for dominating the market & maximizing profits.
On the other hand, any scrub on the planet is free to make an application which adds malware or spyware to your phone, cause it to behave in any malicious way they can scheme up, actually allow/encourage them to gather your personal data, PIN numbers, Record your keystrokes, monitor your real-time location, and basically completely whore out your phone in every way imaginable.. and you cant do anything about it
its their "right" as app-makers... its NOT your right to stop people from collecting personal information or recording every single thing you type on your phone for their timely review at their leisure
ok. i think we got that straight, So everyone else on the planet can access your phone and collect your private data, EXCEPT for you
The Carriers, Google, and most likely the CIA, NSA & HLS want to block all users from being able to stop programs which steal your info & monitor you closely.
thats really what this is all about. You have no ability to stop the spying and data collection on your phone..
they have total access to anything they might ever want to do remotely on your phone
and you are going to sit there and let it happen.
I hope the NSA at least gave the people at Google special jackets that have the interior embroidered with: "I sold out every user in America, and all I got was this special super-secret jacket", like they did for the Facebook guys
.
Klown80 said:
You have a device with a MediaTek CPU in it. Use this to root:
http://forum.xda-developers.com/showpost.php?p=43163569&postcount=7
If you need help installing drivers on your PC try www.snappea.com and install on PC, it will install an adb driver that will work for what we need.
Hope this helps!
Click to expand...
Click to collapse
Wow! thanks.. it took me like 3 seconds to root my phone.. just plugged it in with USB Debugging, didnt need drivers or anything, after I plugged it in 2 inaccessible drives showed up in my computer.. ran that .exe file, after like 3 seconds my phone restarted and its totally rooted
After reboot, SuperUser asked if Adblock plus could run..
then I Opened up a terminal window, typed: su & hit enter, SU asked me for permission, then I got the #...
then I ran Rootchecker basic, I clicked "verify root access", SU asked me if I wanted to allow root checker, then it said Congrats, I have root access..
sweet....
that was very cool of you..
thanks alot!
-
chinarabbit said:
Wow! thanks.. it took me like 3 seconds to root my phone.. just plugged it in with USB Debugging, didnt need drivers or anything, after I plugged it in 2 inaccessible drives showed up in my computer.. ran that .exe file, after like 3 seconds my phone restarted and its totally rooted
After reboot, SuperUser asked if Adblock plus could run..
then I Opened up a terminal window, typed: su & hit enter, SU asked me for permission, then I got the #...
then I ran Rootchecker basic, I clicked "verify root access", SU asked me if I wanted to allow root checker, then it said Congrats, I have root access..
sweet....
that was very cool of you..
thanks alot!
-
Click to expand...
Click to collapse
No problem! I am glad I could help. I can also point you in the direction of possibly backing up your firmware incase you ever need to reflash the stock firmware.
Klown80 said:
No problem! I am glad I could help. I can also point you in the direction of possibly backing up your firmware incase you ever need to reflash the stock firmware.
Click to expand...
Click to collapse
great! so how does that work? thanks!
also, do you think SuperSU, or the Superuser ClockworkMod is better?
chinarabbit said:
great! so how does that work? thanks!
also, do you think SuperSU, or the Superuser ClockworkMod is better?
Click to expand...
Click to collapse
I personally prefer SuperSU but to each their own.
Use this to back up, it works on most MTK devices:
http://forum.xda-developers.com/showthread.php?t=2160490
Klown80 said:
Use this to back up, it works on most MTK devices:
http://forum.xda-developers.com/showthread.php?t=2160490
Click to expand...
Click to collapse
well, i tried downloading the MTKDroidTools v2.4.8 from the site, which took me to depositfiles.com. but I got a warning that it was an:
"Android/exploit.lotoor.DH trojan", when auto-scanning before completing Download..
any other versions or other tools or Download Links you know about?
thanks
chinarabbit said:
well, i tried downloading the MTKDroidTools v2.4.8 from the site, which took me to depositfiles.com. but I got a warning that it was an:
"Android/exploit.lotoor.DH trojan", when auto-scanning before completing Download..
any other versions or other tools or Download Links you know about?
thanks
Click to expand...
Click to collapse
That is because there is an android exploit in the package, that program can also root some devices but your A/V is picking up the exploit since technically it is a linux exploit, but it is used to root the phone is all. Any other link you get to download that file will say the same since the exploit is packaged into the file.
Klown80 said:
That is because there is an android exploit in the package.
Click to expand...
Click to collapse
Ok, i DL'd it.. I do have a couple questions..
1st, does your phone have to be off before you begin? I dont see "Create Scatter"
and, in SuperSU, everytime I start it, it asks "The SU binary needs to be updated. Continue?" then "If you have a custom recovery like TWRP or CWM, that can be used to (try to) install the SU binary. This is recommended for HTC devices. How would you like to Install he SU binary? [Normal] [TWRP/CWM]
click Normal says "Installing, please wait...".. then it says "Installation Success !"
it does this every single time SuperSU is clicked.. any ideas?
thanks
chinarabbit said:
Ok, i DL'd it.. I do have a couple questions..
1st, does your phone have to be off before you begin? I dont see "Create Scatter"
and, in SuperSU, everytime I start it, it asks "The SU binary needs to be updated. Continue?" then "If you have a custom recovery like TWRP or CWM, that can be used to (try to) install the SU binary. This is recommended for HTC devices. How would you like to Install he SU binary? [Normal] [TWRP/CWM]
click Normal says "Installing, please wait...".. then it says "Installation Success !"
it does this every single time SuperSU is clicked.. any ideas?
thanks
Click to expand...
Click to collapse
Ok, first for SuperSU. open it again and choose continue then normal. Then hit the home button on your phone to exit app without closing it. Now please go into Settings > Applications > All and find the chinese installed superuser app. (It looks like a blue shield) Tap that app and then on next screen choose disable or uninstall. Now go back and open SuperSU again and if it asks to update binary again choose continue and normal and you should be good to go. Try Root checker afterwards to verify. This Vroot works good but it can be a bit of a pain on some devices to get rid of the superuser it installs so you can switch to english Superuser or SuperSU
Then open MTK Droid Tools and connect PC with phone powered on, click on the root, back up, recovery tab and then click the big back up button. If back up button is greyed out you will have to click the root button in bottom right corner to allow adb shell root access to make the back up. (make sure you hit grant on phone when you click the root button on MTKDT)
You dont need to create scatter file to back up with MTK, only if you want to pull files using SP flash tool but MTK does same thing on its own.
Klown80 said:
Ok, first for SuperSU. open it again and choose continue then normal. Then hit the home button on your phone to exit app without closing it. Now please go into Settings > Applications > All and find the chinese installed superuser app. (It looks like a blue shield) Tap that app and then on next screen choose disable or uninstall. Now go back and open SuperSU again and if it asks to update binary again choose continue and normal and you should be good to go. Try Root checker afterwards to verify. This Vroot works good but it can be a bit of a pain on some devices to get rid of the superuser it installs so you can switch to english Superuser or SuperSU
.
Click to expand...
Click to collapse
well, I updated, then i swiped down from the top and went to settings from there, apps > all, then Forced stopped the Vroot SU app, I then disabled it.. then I went back to SuperSU, it updated it normally, it took about 5 times longer, then it said "Installation Failed"
I dont know, the version of Vroot I downloaded has an English Superuser, and it looks pretty full-featured... it looks more full-featured than SuperSU, just from what i've seen, but maybe i'm not even seeing the real SuperSU program yet... though there are some small English misspellings in the VrootSU
If I cant fix SuperSU, I'd be fine using that one, but SuperSU says you cant just uninstall it.. you need to get another one working first.. is that done by Disabling SuperSu, and then enabling Vroot's SU, as simple as that?
thanks for all the help
chinarabbit said:
well, I updated, then i swiped down from the top and went to settings from there, apps > all, then Forced stopped the Vroot SU app, I then disabled it.. then I went back to SuperSU, it updated it normally, it took about 5 times longer, then it said "Installation Failed"
I dont know, the version of Vroot I downloaded has an English Superuser, and it looks pretty full-featured... it looks more full-featured than SuperSU... If I cant fix SuperSU, I'd be fine using that one, but SuperSU says you cant just uninstall it.. you need to get another one working first.. is that done by Disabling SuperSu, and then enabling Vroot's SU, as simple as that?
thanks for all the help
Click to expand...
Click to collapse
You may need to run Vroot again to get root access back would be quickest way to get root back if you lost it. Then try this open SuperSU, then hit continue, then normal. Now to into Settings for SuperSU, there scroll down and find Install SuperSU into /system. It will tell you that you need to clean up and reboot. Once rebooted see if chinese superuser app is gone. If so, try root checker now and see if superSU pop up box asks you to grant.
If you prefer to just use the chinese superuser app then you can just uninstall SuperSU via play store or within Settings > Applications > All.
Klown80 said:
You may need to run Vroot again to get root access back would be quickest way to get root back if you lost it.
Click to expand...
Click to collapse
Well I didnt lose Root, I Cleared SuperSu's cache then disabled it.. Then I Cleared the cache then re-enabled VrootSU, now Vroot is re-logging everything and monitoring everything again.
I'm new to this actually, I see vRoot has Permissions, System Optimize, Clean Internal System Apps, Root Access Management on a Per-Program basis for Allow, Deny, or Ask;.. Process Management with User & System labels.. Boot Management with User & System labels, Delete Unnecessary Files to clean up space...
Can SuperSU do things vRoot Cant?
I'll probably talk to one of my local Chinese in-laws who's really into Linux and Rooting Androids, and ask him what he uses as well.. next time I see him..
it seems most people on XDA prefer SuperSU... I dont like the fact that there's a paid pro version really..
but.. I guess If later I learn I need something more, I'll revisit SuperSU & other programs..
I'll work on the backup now, thanks
hmm, well it seems to not recognize my phone.. the bottom says "The device isnt revealed, Connect or reconnect a cable"
There is no "root" button on the bottom right, only a clickable "ADB Terminal" button, and a greyed-out "reboot" button
The phone information tab shows no phone info, and the 'root, backup, & recovery' tab has 2 checkboxes I can check "Backup Userdata & Cache" and "Leave Flash Tool files on SD card"
The 'Backup', 'Superuser', 'Build.prop', and 'Delete China' buttons are all greyed out .. (what does delete china do?)
in the middle section, "Recovery & Boot" is a button I can click, with a "To choose the boot.img" radio button accessible as well
then of the bottom 4 options, only the "To process file ROM_from Flash Tool" bar is greyed out, the other 3 bars are clickable:
-To prepare blocks for Flash Tool
-To unpack yaffs2 the section
-To create updates for modified recovery
--
The Phone is powered on.. I tried connecting in USB_debugging mode, and not in USB debugging mode.
I connected & reconnected the cable, closed & restarted the program every time.. and I tried both starting the program, then connecting, as well as connecting first, then starting the program... tried rebooting as well.. and also tried with AV turned off, just in case, although I made an exception to the programs directory in my ESET NOD32 Smart Security
and if I first turn off USBdebugging, then connect the phone to the computer, and then click "Turn on USB Storage" on the android prompt screen on the phone, it opens up 2 separate explorer windows to 2 different drive contents..
and thats where I am.. any Ideas?
thanks again
well, I plugged it in today and tried again, and it worked.. or is working.. takes quite a while..
not sure what changed it, the only things I did differently was install busybox, make a titanium back up, try some usb host programs to get my USB to read an external device (which it still doesnt, any ideas about that?) and i'm using a longer thicker cable I bought today, a better quality one than the thin short black one that came with the charger..
well, it just asked me to pack the file, so i guess its on the last section..
anyway, thanks.. do you know which version of CWM I can use? or do I need CWM? Or can you recommend a NAND backup or is this a NAND backup, and I dont need another one?
thanks again
chinarabbit said:
well, I plugged it in today and tried again, and it worked.. or is working.. takes quite a while..
not sure what changed it, the only things I did differently was install busybox, make a titanium back up, try some usb host programs to get my USB to read an external device (which it still doesnt, any ideas about that?) and i'm using a longer thicker cable I bought today, a better quality one than the thin short black one that came with the charger..
well, it just asked me to pack the file, so i guess its on the last section..
anyway, thanks.. do you know which version of CWM I can use? or do I need CWM? Or can you recommend a NAND backup or is this a NAND backup, and I dont need another one?
thanks again
Click to expand...
Click to collapse
Sounds like it was most likely the cable you were using, I went out and bought a nice big expensive one, since most devices use the same type of connector it seems, and have never had any issues getting any device to connect that I have used it on thus far.
MTK droid tools backed up your stock firmware, but you can also pull your stock recovery out of that back up and repack it into a CWM based recovery using MTK DT too. I can help if you like, let me know.
If you ever need to reflash the firmware you can either use SP flash tool or you can make the above mentioned CWM recovery and use it to flash the firmware back to device too.
Hope this helps!
Hello ive not done any guides before but since i had to search all over to try find out what i was looking for and stumbled across a lot of good information and thought id share it. None of this was my findings but there isn't anything clear on how to actually accomplish this on a Fire stick.
Im going to attempt to share how i have managed.
This guide assumes you already know how to transfer files to your stick.
First off, current Fire stick os is 5.2.1.0 and is rootable with Kingoroot.
https://root-apk.kingoapp.com
1. Download Kingoroot and ADB to your Fire stick, do this whichever way you normally get apk/files onto your Fire stick.
2. Download Kingoroot superuser and ADB to your Fire stick.
3. Run the Kingoroot tool and let it finish, when you have root, install Kingo roots Superuser. (If you install this before rooting it wont make any difference).
Now you should have a rooted Fire stick on 5.2.1.0 with Kingoroots SuperUser.
Now its time to downgrade your Fire stick. This file was provided by AFTVnews over at another thread and cuki3r3k83bln accomplished downgrade on the thread also so please leave thanks for them as before he posted the file and information i had no idea it was possible. Im suggesting to download the 5.0.5 file as i did because this was when firestarter worked with home button detection.
Download Fire Stick os 5.0.5
http://amzdigitaldownloads.edgesuit...te-kindle-montoya-54.5.3.7_user_537174420.bin
Once you have it downloaded rename the downloaded file to update.bin.
Im going to explain how i did it, i know there is many other variations on how to accomplish this and im not too familiar with adb commands but the way i will show is the way it worked for me.
We need to transfer the downloaded and renamed update.bin to the Fire stick so if you would like to transfer it with apps to fire or through command or any other variation thats fine but ill show commands used from windows laptop using adbLink.
Please note, if your using a different method to transfer you will have to slightly modify step 5 on where your update.bin is stored so cd /sdcard/download. if your update.bin is stored in download folder.
Another note is to make sure your file name is correct, mine was named update.bin.bin rather than update.bin this was fine just make sure to name it correctly or you will have to modify step 6 and step 8.
1. Open up adbLink and connect your device.
2. Push the update.bin to the sdcard. (this takes quite alot of time as your pushing 311mb file so be patient)
3. Once pushed you need to open up ADB Shell.
4. Run the command: su
5. Run the command: cd /sdcard
6. Run the command: mv ./update.bin /cache/
If you get an error about no space on device do the following:
Run the command rm -f /cache/*.bin
Run the command rm -f /cache/*.zip
Run the command exit
Run the command exit then reopen ADB Shell in adbLink repeat step 6.
7. Run the command cd /cache/recovery
8. Run the command echo --update_package=/cache/update.bin > command
9. Run the command reboot recovery
Your Fire stick should automatically start the downgrade and take 10 minutes or so.
As soon as its finished go back to your Kingoroot app and re-root your Fire stick. Then block updates (method 1) using AFTVnews guide at:
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/
You should now be on 5.0.5 rooted and have updates blocked
All your apps should be still intact. Make sure you uninstall appstarter/firestopper and reinstall firestarter 3.2.3 (if you use it)
Then follow AFTVnews guide on how to re-enable it here:
http://www.aftvnews.com/how-to-cont...v-and-fire-tv-stick-software-version-5-0-5-1/
Please give the credit deserved to @AFTVnews.com and @cuki3r3k83bln
Its suggested all over to hold off before doing anything that could brick the device until rbox releases a recovery.
Please do not use any type of Su modifying tool/script/apk eg: SuperSume as these do not work and you will end up with a small brick.
Also its been pointed out to me by @deanr1977 that if your going to use this guide and decide to update Fire Stick os in the future, it maybe safer to unroot it first.
With that out of the way please excuse the bad layout of the guide as im no expert and would like to just share my experience.
Would I be able to go back to 5.2.1.0 once custom recovery and rom is released?
FireTho1 said:
Would I be able to go back to 5.2.1.0 once custom recovery and rom is released?
Click to expand...
Click to collapse
i cant see any reason why not, either grab the 5.2.1.0 .bin file and follow the guide using that or let it automatically update after re-enabling updates.
Are there any reasons for downgrading to 5.0.5? Does it have any advantages?
Bierfreund said:
Are there any reasons for downgrading to 5.0.5? Does it have any advantages?
Click to expand...
Click to collapse
As far as im aware upto now, it seems that Firestarter home button detection works as it should, and firmware after this Firestarter will not work with home button detection.
Which is a big thing for me personally as i only use Firestick for netflix and kodi and its much easier to launch from within Firestarter.
Its good to know that the process of upgrading/downgrading is applicable to Fire stick as you never know what Amazon will try to take from you.
You sir are my hero. Kudos for the tutorial!
sconnyuk said:
i cant see any reason why not, either grab the 5.2.1.0 .bin file and follow the guide using that or let it automatically update after re-enabling updates.
Click to expand...
Click to collapse
Its not recommended to let it auto update from root, unroot first then re-enable the update progress.
Also please can you note in your guide that its not recommended to try to swap the Su for Chainfires Su with the Super Sume or Super Sumepro app because so many people on this forum have bricked with this method & if any new users try your way & after want to unroot/swap method after the first boot they could have a non working device.
Ive not tried this guide myself (i dont need too) but if its working fine this info would be good to have here.
deanr1977 said:
Its not recommended to let it auto update from root, unroot first then re-enable the update progress.
Also please can you note in your guide that its not recommended to try to swap the Su for Chainfires Su with the Super Sume or Super Sumepro app because so many people on this forum have bricked with this method & if any new users try your way & after want to unroot/swap method after the first boot they could have a non working device.
Ive not tried this guide myself (i dont need too) but if its working fine this info would be good to have here.
Click to expand...
Click to collapse
Fair point about pointing out about the brickable and dangerous su swapping methods with supersu me etc.
I will add a mention about it after the line that reads:
'Its suggested all over to hold off before doing anything that could brick the device until rbox releases a recovery.'
As for not recommended to auto update while rooted, ive had 2 sticks and a Fire Tv 2 auto update from 5.0.5 to 5.0.5.1 and then to 5.2.1.0 when my router was reset, (im sure im not the only one from what ive read either).
But since im a helping type of guy ill add this also.
Ok mate, just going by what's been said from the AFTVNews & Amazon Firestick forums. Glad you are including this thanks, Its just some only skim through the threads & read only the parts they want to so if this is included it may cut down on the "I've bricked my Amazon device please help threads" which clog up the forum.
Sent from my SM-G900F using Tapatalk
i'm trying to downgrade to the point where display mirroring worked on windows devices, this is before 5.0.5, can i use this method to downgrade to another bin before 5.0.5?
sins07 said:
i'm trying to downgrade to the point where display mirroring worked on windows devices, this is before 5.0.5, can i use this method to downgrade to another bin before 5.0.5?
Click to expand...
Click to collapse
Id take a stab and say if your stick originally came with a firmware below 5.0.5 but I honestly do not know as ive not tried but I cant see why it wouldnt work. You can go from 5.2.1.0 to 5.0.5.1 or to 5.0.5 so id imagine so.
What features have been removed by 5.0.5? Im interested myself and may try this myself if there is features I could use.
Amazing! I can't believe this was hard to find as all the news out there say you can only root the stick using a hardware mod.
I downgraded and rooted both my Sticks. Installed Firestarter 3.2.3, installed Seeder, removed unneeded processes from running and these things are super quick now. You still have to load the crappy slow Amazon launcher to keep the settings but oh well. Nicely done, now I hope a recovery option comes out and I can mess around further . Heatsink and overclocking anyone? lol
@vulcan4d recovery & prerooted rom is being worked on at the moment by rbox in this forum
Sent from my SM-G900F using Tapatalk
vulcan4d said:
Amazing! I can't believe this was hard to find as all the news out there say you can only root the stick using a hardware mod.
I downgraded and rooted both my Sticks. Installed Firestarter 3.2.3, installed Seeder, removed unneeded processes from running and these things are super quick now. You still have to load the crappy slow Amazon launcher to keep the settings but oh well. Nicely done, now I hope a recovery option comes out and I can mess around further . Heatsink and overclocking anyone? lol
Click to expand...
Click to collapse
Can I ask what processes you removed/stopped and how you accomplished this?
Id like to do the same on 2 of my sticks.
sconnyuk said:
Can I ask what processes you removed/stopped and how you accomplished this?
Id like to do the same on 2 of my sticks.
Click to expand...
Click to collapse
I would like to give credit to this post for removing unneeded services:
http://forum.xda-developers.com/fire-tv/help/root-disabling-apps-services-bloat-t3325333
I only found a few from the list but that list was meant for a Fire TV so I'm sure there is more running. Just launch ADB Shell in ADBFire/Link and type pm disable <service_name>
vulcan4d said:
I would like to give credit to this post for removing unneeded services:
http://forum.xda-developers.com/fire-tv/help/root-disabling-apps-services-bloat-t3325333
I only found a few from the list but that list was meant for a Fire TV so I'm sure there is more running. Just launch ADB Shell in ADBFire/Link and type pm disable <service_name>
Click to expand...
Click to collapse
Thanks ive disabled them as per the guide you linked to. Can I further ask what the program seeder does and whether to have it set to aggressive or not?
Thanks for the info.
@sconnyuk i've downgraded successfully kingo root'ed stick 5.2.1->5.0.5 . But funny thing was under root shell command "wipe data " .It wiped device clean but root still stays on . Got OTA disabled and my other king root 5.0.5 stick will have similar treatment .
nicefile said:
@sconnyuk i've downgraded successfully kingo root'ed stick 5.2.1->5.0.5 . But funny thing was under root shell command "wipe data " .It wiped device clean but root still stays on . Got OTA disabled and my other king root 5.0.5 stick will have similar treatment .
Click to expand...
Click to collapse
You will need to unroot it for root to go.
Kingoroot has the option to do this if its what you want.
You need mouse toggle for fire tv to navigate to the 'in app' menu icon if not plug fire stick into pc and run Windows version of Kingoroot to unroot.
Interesting, I just bought a 3rd Amazon stick to root. After running KingRoot, I've noticed I did not need to install KingUser at all. If you launch KingRoot again it allows you to launch KingoUser which is the same thing. I'm assuming that KingUser is just an updated version of what KingRoot already installs.
Sconnyuk, I checked all the boxes and chose Moderate. This was also mentioned in the XDA forums however sadly I cannot find the post anymore. Seeder is an application that has been around for a while which improves the response time on Android devices. There is a lot of technical details into how it works, but the point is the Amazon stick is not the fastest thing in the world and anything helps. Give it a try and see for yourself.
sconnyuk said:
Id take a stab and say if your stick originally came with a firmware below 5.0.5 but I honestly do not know as ive not tried but I cant see why it wouldnt work. You can go from 5.2.1.0 to 5.0.5.1 or to 5.0.5 so id imagine so.
What features have been removed by 5.0.5? Im interested myself and may try this myself if there is features I could use.
Click to expand...
Click to collapse
Miracast display mirroring became non-compliant with windows systems, it still works fine with android.