Database Info

Simple Guide for Rooting (Tweaks Coming Soon)

I owe much credit to toastcfh, none of this would be possibly without his work on originally rooting the EVO.
Getting Root & Recovery Mode
(My version, dumbed down even more)
You have three options with rooting:
1) Toasts Rooted ROM - Missing Apps in Market
2) Rooted Stock ROM - No 4G Support
3) Unrevoked Root Patch - No system access in recovery (can't remove sprint apps, etc)
To get a rooted stock ROM, you have to start with Toasts, instructions below; you can find details after.
If you want the Unrevoked Root patch, install a file browser on your EVO and install this.
1. Copy this to the root folder of the SD card, you can do this by syncing the Evo as a disc and just copying in windows.
2. Shut off the Evo, and hold the "volume down" button while powering it on until you see a white screen. Every question it asks, just answer yes. DO NOT UNPLUG, let it finish at all costs, no matter how long it takes.
3. Rename the file you copied to the SD card. (to avoid accidental re-flash and save it for later)
4. Download this and unzip to anywhere of you liking on your desktop. Run the setup, if it asks to accept and install a bunch of stuff, hit cancel, you wont be needing most of it. Select available packages and it will show a repository url, the actual url is irrelevant and will be google's be default...we want to expand the list and select SDK Platform 2.1. Accept an install the selection.
What you just did is installed the Android SDK which includes adb, a shell connector for your phone that we need to operate in recovery mode.
5. Hold the Windows key and press "R", type CMD in the run box. (Run the task with Administrative privileges if there is an option)
Type "cd " in the CMD window, do not forget the trailing space, it is important and DO NOT HIT ENTER yet.
Now, with that CMD windows open, go to the folder you installed the android sdk. There will be a "tools" folder, drag the tools folder into the cmd window.
Press enter, this will set your working directory to the tools folder.
6. If you have not installed drivers for your Evo, there is a folder that comes of the sd card called "HTC-Sync", run the setup in there and it will install sufficient drivers automatically.
After drivers are setup sync the phone using the HTC Sync mode, this will ensure we can control the phone using adb.
Go to your CMD window and type "adb reboot recovery", you will see your phone reboot...it will show a red warning icon on the screen afterwards, this is perfectly normal and good to see such.
7. Your phone should not be in recovery mode, but the filesystem will be offline. Download this to setup the shell for us before we can mount the filesystem. Run "recovery-windows.bat", if you are using Vista or Win7, make to sure right click the file and "Run as Administrator"...you will see another CMD window popup and do some work, just leave it open. You should now have the shell setup in Recovery Mode on your Evo.
8. Go back to your original CMD window we setup, type "adb shell" and hit enter, this will set all commands to work right on the phone. You should see a line with just "#", that is what we want.
Now type "mount /dev/block/mtdblock4 /system" and hit enter.
You should now have your Evo in recovery mode with a shell setup and filesystem mounted. This is where we can begin making changes.
Now that this has all been setup, you may want to go back after making some changes.
Repeat steps 5-8 to re-enter recovery mode with the filesystem mounted.
If you want to continue and do the stock update, check here.
Basically, copy that file to the SD and do steps 5-7.
Then use the onscreen (on the EVO Recovery Mode) to "Flash from ZIP" and select the rooted stock rom update.
WARNING: You must clear user data if the update creates issue, you will know right away.

so this is a third way of rooting, if i used a different way how do i get rid of it and use yours, i'm so tired and confused.

Post Removed to maintain consistancy, see 1st post in thread.

root rom and activesync?
I'm a complete noob here but: By using this method do I still retain the ability to run ActiveSync/Exchange support? (Didn't think this was in the SDK Platform 2.1)
What about Sense?

What the crap is up with the title of this thread? How us this a tweak or an optimization?
Good noob friendly guide, kinda tldr, but what I did readlooked good!
Change ur title

Neotelos_com;
[B said:
You have two options with rooting:
1) Toasts Rooted ROM - Missing Apps in Market
2) Rooted Stock ROM - No 4G Support[/B]
....
Click to expand...
Click to collapse
Any thought about the third option (i.e. unrevoked, new sticky, apk??) will it do the same things? i read users aren't losing full market, 4g etc.? Someone much smarter than me please weigh in.

adeyo said:
Any thought about the third option (i.e. unrevoked, new sticky, apk??) will it do the same things? i read users aren't losing full market, 4g etc.? Someone much smarter than me please weigh in.
Click to expand...
Click to collapse
Yes, adding in right now...just tested and it works well.
I need to check if it allows things to be changed in recovery mode (which is important for removing the Sprint bloatware)

johnsongrantr said:
What the crap is up with the title of this thread? How us this a tweak or an optimization?
Change ur title
Click to expand...
Click to collapse
I have plans for adding in tweaks, which will be delayed a bit...
Sorry for any inconvenience.

Neotelos_com said:
Yes, adding in right now...just tested and it works well.
I need to check if it allows things to be changed in recovery mode (which is important for removing the Sprint bloatware)
Click to expand...
Click to collapse
If you have root at all, and you have "rw" permissions for "system". You should be able to remove sprint apps when the phone is booted, assuming you dont have root while in recovery.
Is something different on the Evo that im missing?
can you not do this
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
ls
Then remove the apps like so
rm NameOfApp.apk
rm NameOfApp.odex
Not saying this will all work.. But if you have root, shouldnt this work to remove sprint apps.

Jus10o said:
If you have root at all, and you have "rw" permissions for "system". You should be able to remove sprint apps when the phone is booted, assuming you dont have root while in recovery.
Click to expand...
Click to collapse
You can make changes like that but it will not actually save to the NAND.
So...you can remove, but it will come back after reboot.

Neotelos_com said:
You can make changes like that but it will not actually save to the NAND.
So...you can remove, but it will come back after reboot.
Click to expand...
Click to collapse
Well thats all kinds of dumb..
I give it a week and there will be something better working.

Nice write up. The only problem is, I don't have the sync software on my sd card because the best buy employee knew about the evo's sd card problem and formatted it, erasing everything on the card. I checked htc's site and they had the drivers for download, but it keeps giving me an error saying it's not compatible. I'm using windows 7 64bit. Any ideas guys?

Jus10o said:
If you have root at all, and you have "rw" permissions for "system". You should be able to remove sprint apps when the phone is booted, assuming you dont have root while in recovery.
Is something different on the Evo that im missing?
can you not do this
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
ls
Then remove the apps like so
rm NameOfApp.apk
rm NameOfApp.odex
Not saying this will all work.. But if you have root, shouldnt this work to remove sprint apps.
Click to expand...
Click to collapse
you CAN remove apps like that, using toast's custom recovery. if you do your shell, and mount, in recovery, using adb, you can go to /system/app and rm whatever you want (be careful not to remove anything important, probably wise to pull whatever first, in case you need to push it back)
i had problems when i did an rm on a file, but that is because apparently i forgot to rm it's info in /data/data too. word to the wise

HTC Sync Torrent
http://thepiratebay.org/torrent/5609530
PLEASE SEED AFTER DOWNLOAD!

New android user here!
So to me it seems like all three have something they're not able to do. Seems best to wait for a root release that your able to take full advantage of, right?
I'm a former WM flasher , I need to learn android still. I want the free hot spot/tethering, more battery life as I need 2 batteries to make it through the day -.- (I kill apps constantly, 4g turned on rarely,ect, ect)
Any feedback is appreciated,
Sean

can someone point me in the right direction to do this using a mac not new to android just the mac os i did pretty much everything but im stuck on the htc sync part HELPPP PLZ thanks

kingcliff00 said:
can someone point me in the right direction to do this using a mac not new to android just the mac os i did pretty much everything but im stuck on the htc sync part HELPPP PLZ thanks
Click to expand...
Click to collapse
Try going to Settings -> Applications on the evo and enable usb debugging...if that5 gives you adb access that's all you need

confirmed working with unrevoked root method. It can tether 3G or 4G, depends on how you connected to the Sprint network. 3G was 0.80Mbps DL, 4G was 2.63Mbps DL.
Before using unrevoked root method, I had applied the sdcard patch already. so it doesn't matter if you applied the sdcard patch or not (OTA updated).

You really shouldn't kill tasks. Just cycle the battery a couple of times and turn your antennas off and on when u need them. Especially if u are in spotty 3g coverage. There already one or two official write ups that say task killing is bad I use to do it and got forceloses and errors all the time. Its not about how many tasks you have running I.e. memory, items about cpu and antenna signal that kills you're battery I'll find the link if I can. My battery life is pretty good and I'm a heavy user.
Sent from my PC36100 using Tapatalk

i cannot get recovery bat file to work. I am at the red exclamation point screen on my evo and i run the bat file as amdmin. it pops up for a second then closes and nothing happens.
Edit: NVM I figured it out. on to the next step.

[Q] help with IDeaUSA 7" tablet

Hi, everyone
I hope that I am in the right part for posting? I am new to this android thing.
I am trying to find a how to root idea usa 7" tablet from fry's for $77.00. Their is a lot of rooting programs but I have not been able to find anything on this model.
Also what would be a good rom to flash it with? I tried finding out if uberoid and cyanogenmod would work but I could not find any info on this model.
Not to sure what model I have that I would be able to flashing this rom with, either uberoid or CM7? Help
Model: MID, sv7206 v1.4, kernel 2.6.35.7-infotm
processor armv6 rev5,
hardware imapx200,
android 2.3.3,
brand infotmic,
display gri40,
release codename REL
bootloader unknown
I don't know if this is the right model IDea USA IUMID-0071 because the spec's are off. Http ://ideausa.us/produects.html but similar. I am looking for rom that is more update/modern. any potters?
Does anyone have the original rom for this or know how to make a backup this rom?
Well I am thinking that is might be this model but not to sure wm8650,SV7206 v1.4 or IDea USA IUMID-0071.
It's not flytouch
The screen is very slow on this model. Unless you use a pen then is works better.
Also hoping to be able to flash this to ics 4
Thanks

I just bought one, too. What a pos? it works but the screen is almost unusable, lots of mis-fires.
I did figure-out the real OEM web-page,
http://www.sinovideo.com.cn/Products/indexshow.asp?lang=EN&SortID=61&ID=85
This correctly identifies the installed 2.3 OS and reveals that it's some kind of 1 GHz processor. The real performance problem, however, is the 256 MB of memory, ouch!
I have not had any luck finding any updated ROMs. Actually, I suspect the installed ROM is tweaked to work around the defective screen (I think it's configured to ignore any 'touch' lasting less than 0.5 second?) so I'm not going to change it.
---------- Post added at 08:58 AM ---------- Previous post was at 08:49 AM ----------
FYI - I found another site that has lots of discussion about the "M7206" tablet
http://www.techknow.t0xic.nl/forum/index.php?board=51.0

Here's some more info. (Yes, I have continued to investigate even though I bad-mouthed it )
- This tablet is also sold as the "infotmic m7206"
- the screen works MUCH better if you use a stylus
Currently, my tablet seems to be getting about 24 hr standby battery-life, and the battery-usage report says "Cell standby" is using 75%, even though there's no cell radio? Some of the discussion on the techknow forum seems to be about this same issue but all the solutions seem to involve rolling your own ROM, which I'm not prepared to do. For now I just plan on leaving the tablet plugged-in overnight.

Rooting Idea USA Tablet
Oh my, what a mess...
This post is in regards to the Idea USA Tablet (Unable to Root)
My specs:
- Idea USA Tablet (Made in China)
- Model Number: MID (Unknown)
- Android Version: 2.3
- Kernel Version: 2.6.35.7
- Build Number: MID-userdebug 2.3 GRH55 (ENG)
Issues:
Whelp, I have tried the basics and I can't get this thing to root for anything. I was able to get it to hook into the PC through USB. There are 2 usb slots on the side of the tablet. I believe one is for HOST and the other usb is for OTG (Charging). Once I figured out the host port, then I had to download the drivers for this poorly made tablet...But, what drivers? You go to the Idea US website and you get no helpful information. So, there are no drivers made specifically for this $100 dollar generic tablet from FRY's. Ok... No big deal... So, I download the default "Android USB Drivers".
Peachy, it worked! Now, I can transfer files back and forth between the card(s). Wonderful, first step down, next step was to root. So, I read up on how to root with Super One Click.
Ok, so now, I set the tablet to "USB Storage" and "Host"...Then I download and run Super One Click.
Ok, I run the "Super One Click v.2.3.3"; by clicking the root button and then all I get is a frozen screen that reads:
Code:
Killing ADB Server.... Kill Server 0.11s
Starting ADB Server.... StartServer 4.09s * daemon not running. starting it now on port 5037* *daemon started successfully*
And then it just freezes the program. So, now I'm completely stuck. I mean I learned a great deal, that I can hook up a keyboard, mouse, etc to this thing, but, obviously Super One Click was not designed for these generic tablets. I have read other articles which have suggested that the .inf driver for the default "Android USB Drivers" needs to be edited for your specific tablet model and you must enter the specific CODE# for it to recognize for rooting with Super One Click... But, god forbid, I haven't found any useful information on where that might be. Also, someone suggested to install the Android SDK and edit those files along with the .inf files to make this work. But, that didn't work either. I did everything right. I turned off USB debugging and then I would wait for super one click to come up with waiting for device...but that never happened. I even tried it with USB debugging on... still nothing.
Has anyone created a generic batch program to root these types of devices? What am I doing wrong here?

Rooting Idea USA Tablet
Well, this took me all night to read and learn about how to root this basic tablet from Fry's.
First off, I tried many different things and it just didn't work. Using super one click is definitely out of the question for this particular tablet.
I read all night and thankfully found the forum article on how to solve this issue on xdadevelopers own forum.
As per quoted quotes below:
.....You can use gingerbreak to root this. Run it once and let it reboot, then use supermanager free from market to rename the su symlink from /bin/ to "old" or something, and reboot again.
You should now have root ........ It might take a couple of trys but it works.
You need to download supermanager from the market. Enable root in supermanager settings and click yes when superuser pops up.
Then use the file explorer within supermanager to navigate to the /bin/ directory and you will find a sysmlink called su
You need to rename this su symlink to old - completely take out the name su.
Just to be safe run gingerbreak again and then you can install busybox from market.
pablo11
Click to expand...
Click to collapse
Thank you so much Pablo11. The idea is to download the APK for GingerBreak from online onto your IDEA USA tablet directly. The trick here is that the brand name is IDEA "USA", but the real workings behind the "MID" is "ViMicro". You will notice that displayed as you turn on your tablet. So, in order to find real information about your MID device, you have to search articles for vimicro.
Once you run gingerbreak, your tablet will go completely nuts. Nothing will run right. Things will break and it will be a complete mess. It will however, install superuser apk. However, it will not work. You can download the Root Checker from the market and you will notice it is NOT rooted. So...thanks to pablo11, you will want to download supermanager from the google play market. Install it.
Next go into the supermanager settings and click on ROOT. Make sure root is enabled and checked marked in the settings. When you enable root in the settings, it will prompt you with "allow root?" Click on Yes. This will give you the access you need.
But, your not done, once again as per Pablo11, go to the super managers file manager section. Get to the root directory by clicking up, and then find the folder "bin". Look for the file "SU" and rename this to "old".
Now, you will be able install busybox and any thing else thats root.
By the way, restart your tablet again, and I "personally" recommend that you go into your settings> Privacy> Check mark both (Backup my data and Automatic Restore) and then click on Factory data reset. Start the tablet from like it was brand new. Don't worry it will keep the root that you did intact. You will just have to re-register the tablet with your existing gmail that you originally used with that tablet.
Lastly, use the root checker from the market and you will see that it is successfully rooted.
Okay... Now, my next step. To crack open this tablet and put in a bigger SD Card as the 2G SDCARD is way too small, especially if you want to use new roms and install a linux operating system onto it....

[Q] FileMate Clear 7" T720 tablet

Does anyone know if Z4Root will work on this tablet? Thanks!

I've been looking for one for 3 days now, I tryed onclickroot and z4root or something like that,, cant find anything Anyone please help!!

I'm still waiting for my tablet to be delivered...I'm gonna try SuperOneClick (crosses fingers)

I got one of these for my daughter for xmas. I spent a few days trying to root it with no luck. I'm not intimately familiar with android (some unix experience), but I tried all the options I could find for rooting Allwinner a10 devices. At first I ran into problems with adb unable to recognize the device for most one-click methods. I downloaded the android tools and was able to connect with the included adb. After studying the scripts, they all use the "adb root" command to gain root access on the device and copy the necessary files. Unfortunately, this command fails using adb from the tools. At first I thought this was due to my adb version, but after doing some research I think it is actually due to the device kernel. I believe it requires reflashing or some exploit to be able to gain root. I was able to install root explorer and I can browse all the necessary directories but I can't modify or copy the necessary files into them. Busybox told me there was an older version installed, but wouldn't let me install a newer version (again I think due to the permissions). Also, superuser would say it installed but the su binary did not show up on the bin directory. As the necessary directories are all owned by root, I couldn't figure out a way to modify the permissions...

I wound up returning the FileMate and got a Lenovo IdeaTab. Got that rooted in no time.

sorry i never saw this post i've bought 2 of these and i rooted them,
i wish i could get a better build for them though, too many app crashes and the internet connectivity sucks
i used a method by Bin4ry called root with restore, v17 worked any ways i have the zip if you would like it

ferny_dx said:
sorry i never saw this post i've bought 2 of these and i rooted them,
i wish i could get a better build for them though, too many app crashes and the internet connectivity sucks
i used a method by Bin4ry called root with restore, v17 worked any ways i have the zip if you would like it
Click to expand...
Click to collapse
Screw it, here it is for future reference.

How'd you do it!?!?
ferny_dx said:
Screw it, here it is for future reference.
Click to expand...
Click to collapse
FileMate Clear T720
Thank you very much for being the only person ever to have posted in regards to this tablet. I just got mine for christmas and have been trying to get it rooted. I've tried a lot of those one-click methods, and I've even tried this Bin4ary method. but it just hangs up on "daemon started sucessfully*"
Can you please direct me to the filemate drivers (if needed)
also, I have usb debugging endable, allowing 3rd party (not secure) files enabled. and pulling my hair out (enabled).
Thanks again.
Also, I'm running windows 7 and 8, (((maybe i should try win7))) hmm. i'll get back to you on that. Anyhow, any advice would be greatly appreciated, since returning it doesn't sound very fun.

jiberish05 said:
FileMate Clear T720
pulling my hair out (enabled)..
Click to expand...
Click to collapse
I laughed so hard. ok your going to have to install drivers by force,
first off do you happen to have android sdk installed? if you don't there is another way but its going to sound weird,
if you do have the android SDK installed:
1. go to your computer manager (by opening explorer, right click on the "computer" group on the left column and select manager)
2. look for any unrecognized item that appears, ( it will most likely be labeled "Clear" with a faded icon and a "?" sign on top
3. right click and choose "Update drivers", it will give you options, choose "Browse my computer for driver software", another option screen will show,
4. at the bottom of the window there will be an option that says "let me pick from a list of device drivers on my computer"
5. on the screen that appears there should be an option that says "ADB Interface", choose this
6. choose "Google, Inc.">"ADB Testing Interface version x.x.x.x" (I chose version 2.1.0.0)
that should do it next time you plug in the tablet try running ddms or open the cmd and type in "adb devices" (assuming you have adb installed) and it should show.
if this helps just hit the thanks button
[edit] I am running windows 8 btw [/edit]

ADB interface doesn't show up
Thank you very much for getting me farther, however I dont see ADB interface. I'm looking into it right now. I just re-installed the sdk drivers and will keep at it.
BTW, is it even worth doing this? the main reason I want to do it, is so i can connect my ps3 remote via bluetooth, and possibly a little overclocking. Have you had any luck OC it?
Thanks again Much appreciated:good:

jiberish05 said:
Thank you very much for getting me farther, however I dont see ADB interface. I'm looking into it right now. I just re-installed the sdk drivers and will keep at it.
BTW, is it even worth doing this? the main reason I want to do it, is so i can connect my ps3 remote via bluetooth, and possibly a little overclocking. Have you had any luck OC it?
Thanks again Much appreciated:good:
Click to expand...
Click to collapse
open up SDK manager and go to Extras>"Google USB Drivers"
also install everything in the "Android 4.0 (API 14)" section, I have other options installed if this still doesn't work.
its worth it just for the extra stuff that root comes with like titanium backup, but you cant over clock, if you go any higher than 1200 MHz it will lock up and you have to force it to reset.

cyberkeeper1 said:
HERE is the link to root as provided earlier
Click Here to download ADB universal drivers. they should work better than the google USB drivers.
---------- Post added at 12:20 AM ---------- Previous post was at 12:11 AM ----------
this seems kind of spammy. What backs up my claim is that you dont have more than 5 posts...
Click to expand...
Click to collapse
Thanks for the link to my post on android central, the link in that post just comes back the xda thread
Root MANY ANDROID! [Upd: 20.11.2013] - Added Z1 Root
Sent from my XT862 using Tapatalk

Rooted Filemate Clear
I just wanted to confirm I have also rooted the Clear with the Bin4ry v33 exploit using option 1. Although I received the following error:
remote object '/system/bin/ric' does not exist
.
Going to copy files to it's place
Rebooting again, please wait!
Could Not Find C:\Documents and Settings\Graham School\My Documents\Downloads\Ro
ot_with_Restore_by_Bin4ry_v33\ric
Restoring previous Backup! Please select the RESTORE MY DATA option now on your
device!
SuperSu installed and root apps working.

Rooted With Kingo
I just bought one of these cheap to play with and used Kingo to root it. Worked first time, no problem. The only issue I am having is that the SuperSu binaries are failing to update but root is still working. Titanium is working and Root Explorer so I can debloat. Hope that helps is anyone is still trying to use these

Jfender1005 said:
I just bought one of these cheap to play with and used Kingo to root it. Worked first time, lem. The only issue I am having is that the SuperSu binaries are failing to update but root is still working. Titanium is working and Root Explorer so I can debloat. Hope that helps is anyone is still trying to use these
Click to expand...
Click to collapse
please tell me where in the world you got the Kingo root?
As far as being unable to update binaries, try to find a custom recovery and install. From there, you can inject them via su-binary update.zip and bam!

Kingoroot
cyberkeeper1 said:
please tell me where in the world you got the Kingo root?
As far as being unable to update binaries, try to find a custom recovery and install. From there, you can inject them via su-binary update.zip and bam!
Click to expand...
Click to collapse
http://www.kingoapp.com/android-root.htm
That is the link for the Kingo site. The first time I saw it on here there was some question about whether it was safe becase it is not open source and used a Chinese SuperSu app. I felt safe using it on a tablet because I do no banking on it or anything, but the newest posts I have seen are that Kingo is safe. Hope that helps. And if you know where to find a custom recovery that will work with this app please let me know.

[Q] NEC Medias W N-05E root? (dual screen phone)

Hi!
Is there a root available or in the works for the dual-screen NEC Medias W N-05E?
The question has been asked (no answer so far) at the end of a thread under the N-05D but that's a quite different model.
I'd like to create a separate thread for this model to give it more visibility. Hope that's ok!
Thanks in advance!

bohemianRhapsody said:
Hi!
Is there a root available or in the works for the dual-screen NEC Medias W N-05E?
The question has been asked (no answer so far) at the end of a thread under the N-05D but that's a quite different model.
I'd like to create a separate thread for this model to give it more visibility. Hope that's ok!
Thanks in advance!
Click to expand...
Click to collapse
OK! I've made some progress on this: the japanese blogger "dupondroid" appears to say that run_root_shell (hosted at github)
successfully gives temp root. At least, that's my necessarily blurry understanding via google translate. Would any japanese readers here be able to post a better translation?
And a thread at r-2ch dot com links to the github commit in run_root_shell which made that possible: it's commit ID 811be8639aed64c158798a72a1d520a4d21e8b8b "Support N-05E"
Code:
+ { "N-05E", "A1000311", 0xc0094430, 0xc0093ebc }
So it definitely seems temp root is possible.
Sorry for the lack of links but I'm a new user so can't add them for now.

root is easy
bohemianRhapsody said:
OK! I've made some progress on this: the japanese blogger "dupondroid" appears to say that run_root_shell (hosted at github)
successfully gives temp root. At least, that's my necessarily blurry understanding via google translate. Would any japanese readers here be able to post a better translation?
And a thread at r-2ch dot com links to the github commit in run_root_shell which made that possible: it's commit ID 811be8639aed64c158798a72a1d520a4d21e8b8b "Support N-05E"
Code:
+ { "N-05E", "A1000311", 0xc0094430, 0xc0093ebc }
So it definitely seems temp root is possible.
Sorry for the lack of links but I'm a new user so can't add them for now.
Click to expand...
Click to collapse
root is easy via a tool called impactor.
however it's only temporary, I couldn't get /system mounted for rw. so I made a new recovery image to push.
that didn't work either, although I cannot write to recovery there is no error. recoverybkp was successful.
Also I found that the code to enter in recovery mode is based on your imei.
If I remember correctly digit 2,12,13,14 of your imei.
So possible attack vectors are:
1) kernel module to unlock partitions
2) figure out how update.dat files are constructed.
3) write to recovery partition

it0 said:
root is easy via a tool called impactor.
however it's only temporary, I couldn't get /system mounted for rw. so I made a new recovery image to push.
that didn't work either, although I cannot write to recovery there is no error. recoverybkp was successful.
Also I found that the code to enter in recovery mode is based on your imei.
If I remember correctly digit 2,12,13,14 of your imei.
So possible attack vectors are:
1) kernel module to unlock partitions
2) figure out how update.dat files are constructed.
3) write to recovery partition
Click to expand...
Click to collapse
I can't seem to get anything to work i'v tried Impactor did not work just gave me errors also tried run_root_shell but had to have some device.db file with I didn't really figured out, could some one please help?

Lukas_a_1996 said:
I can't seem to get anything to work i'v tried Impactor did not work just gave me errors also tried run_root_shell but had to have some device.db file with I didn't really figured out, could some one please help?
Click to expand...
Click to collapse
I used impactor 0.9.14, you just hook up the phone using microusb and put the phone in usb debugging mode under development options. then selecct "# start telnetd as root on port 22" from the pulldown and click start.
Then using a tool like putty ,telnet to your phone on port 22 (make sure it's connected to you wifi network when you do).
What android version are you running ? 4.1.2 is vulnarable for this attack.

it0 said:
I used impactor 0.9.14, you just hook up the phone using microusb and put the phone in usb debugging mode under development options. then selecct "# start telnetd as root on port 22" from the pulldown and click start.
Then using a tool like putty ,telnet to your phone on port 22 (make sure it's connected to you wifi network when you do).
What android version are you running ? 4.1.2 is vulnarable for this attack.
Click to expand...
Click to collapse
Thanks for the reply . I tried to run the command in impactor but whatever i do i get "Signature bugs unavailable" could it be that i have the wrong ADB drivers installed or is my Impactor setup wrong?
Edit: yeah im running 4.1.2 Build A1001231

You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.

it0 said:
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
Click to expand...
Click to collapse
All the adb commands basically work but nothing works with impactor i just get error

it0 said:
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
Click to expand...
Click to collapse
Bump!

How to Root Medias N05e
Dear All Pro
Does anyone show me how to root N05e? because there is very few information about that. I want to Swapfile to increase Ram size but it required N05e must be rooted.
So if anyone have any information about N05e, please share. Thanks

nguyenbuulam said:
Dear All Pro
Does anyone show me how to root N05e? because there is very few information about that. I want to Swapfile to increase Ram size but it required N05e must be rooted.
So if anyone have any information about N05e, please share. Thanks
Click to expand...
Click to collapse
There is a way for temp root N05E, basically u can use pm disable command or other su stuff. But u cannot mount system rw right now.

Some news about rooting
If someone in doubt, temp root is 100% working with run_root_shell https://github.com/android-rooting-tools/android_run_root_shell
With this I was able to copy full system, boot and recovery image. But I can't push new boot or recovery.
More than that, almost all fuctions in standard recovery mode (available through "reboot recovery" in root shell) are protected with some code. And it's not 2,11,12,13 numbers of IMEI.
Anyone know where to get this code? Or how to write new boot, recovery image? If we do so, we can get permanent root access =)
Maybe someone have Japanese friends? Search all English web, but maybe in Japan web there are some info.
P.S. with Impactor you only can start talnetd from root, becouse Impactor can't remount /system in rw mode and ro.kernel.qemu=1 option is not working

How to enter recovery mode?
Despite starting this thread, in the end I never did bother to attempt rooting.
Anyway, unfortunately now the phone refuses to boot. Not triggered by anything obvious, haven't installed any new software recently, etc. Just hung one day and then when I removed and re-inserted the battery, it won't get any further than the "docomo" splash screen. I.e. the OS doesn't appear to be getting bootstrapped at all. The "docomo" splash screen appears and disappears then the phone sits there with both screens powered up but blank.
As it happens, I had ADB Debug enabled in the developer options at the time, so I've tried to see if I can adb shell into the device, but no luck. Not surprised as it's clearly not getting far enough into the boot for that to work.
Any other suggestions? From the way it happened I do suspect it might just be hardware failure....
Not even sure how I enter recovery mode -- what are the key combinations for this?

bohemianRhapsody said:
Despite starting this thread, in the end I never did bother to attempt rooting.
Any other suggestions? From the way it happened I do suspect it might just be hardware failure....
Not even sure how I enter recovery mode -- what are the key combinations for this?
Click to expand...
Click to collapse
In recovery mode, clear cache, etc..
To get there hold volume down and power at the same time,then you'll see the broken android then wait/ press vol down a couple of times to see the menu.

GRbit said:
Some news about rooting
If someone in doubt, temp root is 100% working with run_root_shell https://github.com/android-rooting-tools/android_run_root_shell
With this I was able to copy full system, boot and recovery image. But I can't push new boot or recovery.
More than that, almost all fuctions in standard recovery mode (available through "reboot recovery" in root shell) are protected with some code. And it's not 2,11,12,13 numbers of IMEI.
Anyone know where to get this code? Or how to write new boot, recovery image? If we do so, we can get permanent root access =)
Maybe someone have Japanese friends? Search all English web, but maybe in Japan web there are some info.
P.S. with Impactor you only can start talnetd from root, becouse Impactor can't remount /system in rw mode and ro.kernel.qemu=1 option is not working
Click to expand...
Click to collapse
did you ever figure out the recovery keys?

hamishhhhs said:
did you ever figure out the recovery keys?
Click to expand...
Click to collapse
No I didn't(
I'm actually sold this phone and lost interest in the topic.

GRbit said:
No I didn't(
I'm actually sold this phone and lost interest in the topic.
Click to expand...
Click to collapse
do you by chance still have the files you dumped?
Ive teamed with a friend in twitter to try and make a rom for this but I haven't gotten very far

hamishhhhs said:
do you by chance still have the files you dumped?
Ive teamed with a friend in twitter to try and make a rom for this but I haven't gotten very far
Click to expand...
Click to collapse
Sorry, but this was too long time ago. Nothing left

GRbit said:
Sorry, but this was too long time ago. Nothing left
Click to expand...
Click to collapse
how would j be able to get the files from my phone?

hamishhhhs said:
how would j be able to get the files from my phone?
Click to expand...
Click to collapse
I dunno man.
I've already described (in the first post you have quoted) what I achieved with this github repo https://github.com/android-rooting-tools/android_run_root_shell . That's all I've got.

[SOLVED] Android Trojan.Gorilla.AM or Guerrilla.AM on my device OEM launcher...

(NOTE: this post is a duplicate of a similar thread I started on the Android Central user forum)
Hello everyone,
In the continuing saga of the Leagoo T5C i bought before the holidays from GearBest, I've seen the good (the price and overall build quality, along with a reasonably good user experience), the bad (some notifications that I just can't get rid of, among other things), and I now present you the ugly: after watching a review video on YouTube about my device, I learned that it came loaded with a Trojan called "Gorilla.AM"...
***EDIT: apparently, the Trojan's name could actually be "Guerrilla.AM", I'm not sure.***
Needless to say, I did as the tester had, and installed Malwarebytes, which, sure enough, found the exact same Trojan on my device.
You can watch the video here: https://www.youtube.com/watch?v=R5l3z7BvBtk
It so happens that it's embedded in Leagoo's own application launcher, called Sujet (in French; maybe it's called "Subject" in English, I don't know). I can force quit the application, since I use another launcher called Apex (good pick, by the way), but Malwarebytes can't seem to shake the Trojan off my device nonetheless.
A quick search on Google gives very little in the way of information about this malware, but I'd like to be on the safe side, so I came here.
Any contribution would be welcome at this stage.

Hi. I've seen your post on a french-speaking forum but for my own reasons I don't want to help there, too many morons.
Leagoo is well-known for smartphones with built-in spyware/adware. I've had both a Z5 and a M5 and both had such crap in the stock firmware.
This one is new to me but you'll probably have to follow the same steps to get rid of it.
Try
Code:
adb shell pm disable <internal name of that launcher>
first (from a PC connected to the device with ADB - zillions of tutorials available for this)
The internal name can be found by guessing or by using one of the many apps that will show you the information. One is https://play.google.com/store/apps/details?id=com.csdroid.pkg
If that fails, try adding "-k -user 0" to the command line.
If it fails again (denied) then you have no choice but to root your device first, then use this pm command from a root shell or directly delete the folder for "Sujet/Subject" from /system/app or /system/priv-app where you'll find it.

Lannig said:
Hi. I've seen your post on a french-speaking forum but for my own reasons I don't want to help there, too many morons.
Leagoo is well-known for smartphones with built-in spyware/adware. I've had both a Z5 and a M5 and both had such crap in the stock firmware.
This one is new to me but you'll probably have to follow the same steps to get rid of it.
Try
Code:
adb shell pm disable <internal name of that launcher>
first (from a PC connected to the device with ADB - zillions of tutorials available for this)
The internal name can be found by guessing or by using one of the many apps that will show you the information. One is https://play.google.com/store/apps/details?id=com.csdroid.pkg
If that fails, try adding "-k -user 0" to the command line.
If it fails again (denied) then you have no choice but to root your device first, then use this pm command from a root shell or directly delete the folder for "Sujet/Subject" from /system/app or /system/priv-app where you'll find it.
Click to expand...
Click to collapse
Hi,
OK, first off, thanks for the reply. Secondly, as I've stated before, I'm new to Android, and though I know my way around the command line in both Windows, Linux et OS X (not so much macOS: my MacBook Pro is 12-years old...), I suppose there are some things to set up first, before you can actually do what you suggest.
I understand that ADB stands for Android Debug Bridge, so is it an existing functionality in, say, Windows, that you can trigger from the command line, or a third-party software you have to install first?
On the Android side, what action should I take? Any Developer command to enable/disable to let ADB interact with my device the way it's supposed to?

Yes, you need to enable debug mode on your phone too. I could refer you to one of the zillion tutorials available on the net, but here's a summary.
Go to settings > about... (à propos)
Make at least 7 rapid touches on the line that says "build number" or its french translation.
This will make a new settings menu available from the main settings page: developer options
In this new menu, enable USB debugging.
Then you need to install ADB on your Mac and I'm at loss to help you there because I'm totally foreign to Macs. Never used one.
This seems like a good start: https://www.xda-developers.com/install-adb-windows-macos-linux/
Note: you may also try issuing the commands mentioned above from a terminal emulator running directly on your Android device, although I'm told that it's not exactly the same thing protection-wise.
Install this: https://play.google.com/store/apps/details?id=jackpal.androidterm and try typing the commands from the emulator window. If it works, no need for ADB (although having ADB will probably prove useful sooner or later and I encourage you to take the step).
EDIT: forget the guys from Phonandroid, they're brain-damaged beyond help

Lannig said:
Yes, you need to enable debug mode on your phone too. I could refer you to one of the zillion tutorials available on the net, but here's a summary.
Go to settings > about... (à propos)
Make at least 7 rapid touches on the line that says "build number" or its french translation.
This will make a new settings menu available from the main settings page: developer options
In this new menu, enable USB debugging.
Then you need to install ADB on your Mac and I'm at loss to help you there because I'm totally foreign to Macs. Never used one.
This seems like a good start: https://www.xda-developers.com/install-adb-windows-macos-linux/
Note: you may also try issuing the commands mentioned above from a terminal emulator running directly on your Android device, although I'm told that it's not exactly the same thing protection-wise.
Install this: https://play.google.com/store/apps/details?id=jackpal.androidterm and try typing the commands from the emulator window. If it works, no need for ADB (although having ADB will probably prove useful sooner or later and I encourage you to take the step).
EDIT: forget the guys from Phonandroid, they're brain-damaged beyond help
Click to expand...
Click to collapse
OK, thanks for the heads-up; I've already installed a Terminal emulator on the phone, so I'm gonna give it a go in a moment. I concur about Phoneandroid, alas: I've just received flak from one of the moderators because I'd double-posted on the same subject, whereas I'd just posted one thread, in the wrong part of the forum, according to him. Go figure...

OK, please feed back on your attempts, both from terminal emulator and through ADB.
Alas, I suspect that root will be required. It was for me on my Z5 and M5 to get rid of Leagoo's crapware.
Phonandroid is a bunch of losers with bloated egos posing as experts when 2/3 of the replies given are total BS.

"Er, Houston, we've had a problem..."
On Windows: "ADB is not a recognized name for a command applet..."
On OS X: "adb: command not found"
Stumped, I am...

"Er, Houston, we've had a problem..."
On Windows: "ADB is not a recognized name for a command applet..."
On OS X: "adb: command not found"
Stumped, I am...

(Additional question, not quite related: Aida64 indicates that my device runs a 4.4.49 version of the Android kernel, when the current version for Android 7.x is supposed to be 4.4.1; how does that compute--no pun intended--with my issue?)

Missing adb command is because the adb.exe (Windows) or adb (Mac) file is not in the command path. Either make the folder that contains the adb[.exe] file the current folder using the cd command or use whatever context menu for opening a command line window within the currently selected folder works, or even add that folder to the PATH variable. Google "add directory to path" for Windows and MacOS.
No idea about the kernel version. Minor kernel versions may vary within an Android release. Not surprising and most definitely unrelated to your problem. The crapware certainly isn't part of the kernel. It's most likely a system app i.e. a folder within either /system/app or /system/priv-app folders. You can't delete it without root, but you might be able to disable (freeze) it with the commands I gave you.

OK, thanks. I did "cd" to the folder where I had unzipped ADB on Windows (on the Mac, when I tried to open the ADB executable, I got a "cpu not supported" error message in the Terminal, as I feared, since my MBP is 32-bit-only, and most Mac applications nowadays only support 64-bit CPUs), and still got the "adb unrecognized command" error in PowerShell.
The phone was plugged in, and the right USB mode, so I'm still a bit baffled here. Gonna try it again with a different approach. Will keep you posted.
Over and out...

OK, here's what I got: "Error: java.lang.SecurityException: Shell cannot change component state for com.leagoo.launcher3/null to 2"
Basically, from my poor understanding of how Android works, it's root or die, right?

UglyStuff said:
OK, here's what I got: "Error: java.lang.SecurityException: Shell cannot change component state for com.leagoo.launcher3/null to 2"
Basically, from my poor understanding of how Android works, it's root or die, right?
Click to expand...
Click to collapse
I see that this phone has 7.x android. So, a Magisk Systemless flash might work. After rooting your device, get a good launcher integrate it to /system. Then delete your stock launcher all together.
Tell me if this works.
---------- Post added at 01:23 PM ---------- Previous post was at 01:20 PM ----------
rhn19 said:
I see that this phone has 7.x android. So, a Magisk Systemless flash might work. After rooting your device, get a good launcher integrate it to /system. Then delete your stock launcher all together.
Tell me if this works.
Click to expand...
Click to collapse
If you are new to this, use an app from play store for uninstalling and integrating apps.

Hi,
Yes, like I said, I'm a newbie when it comes to Android, so I'll abstain from rooting my device for now, but I'll keep your suggestions under advisement, because I suppose there'll be no other option in the long run. I'm gathering info on how to safely root a device.
I've done countless jailbreaks on iPhones, and it was always absolutely painless, but then, I had better understanding of how iOS works than I have Android, so until I know more about the OS, I'll keep my phone as it is.
Thanks again!

UglyStuff said:
Hi,
Yes, like I said, I'm a newbie when it comes to Android, so I'll abstain from rooting my device for now, but I'll keep your suggestions under advisement, because I suppose there'll be no other option in the long run. I'm gathering info on how to safely root a device.
I've done countless jailbreaks on iPhones, and it was always absolutely painless, but then, I had better understanding of how iOS works than I have Android, so until I know more about the OS, I'll keep my phone as it is.
Thanks again!
Click to expand...
Click to collapse
Jailbreaking vs Rooting is like 5-1 on difficulty level. Because Android is Open source while IOS is not. I would highly suggest you Root it if your phone does not have warranty. After all something that is on /system partition like your launcher will need superuser access to modify it. I cannot think of a way that wont void your warranty.
You can flash TWRP and then boot into aroma-fm but that will void your warranty. Rooting is the preferred option here.

Yeah, well, the phone is brand-new, and still under warranty, but that's not what's holding me back: I'd rather not brick it, most of all, because I need it, if not as my main phone, at least for connectivity.
I've read tutorials on this very website about using TWRP to flash a new baseband, but I'm curious about what firmware to choose, where to download it from to be sure it's not laden with bad stuff, and how sure I'll be to have an operable phone afterwards.

UglyStuff said:
Yeah, well, the phone is brand-new, and still under warranty, but that's not what's holding me back: I'd rather not brick it, most of all, because I need it, if not as my main phone, at least for connectivity.
I've read tutorials on this very website about using TWRP to flash a new baseband, but I'm curious about what firmware to choose, where to download it from to be sure it's not laden with bad stuff, and how sure I'll be to have an operable phone afterwards.
Click to expand...
Click to collapse
Why do you want a new firmware? I don't get you man, do you want to clear out the malware or try a new ROM? Because i think you would have to build a new ROM, there is not one available i guess.

That's the thing: the malware on my phone is part of the application launcher installed by the OEM. In other words, it's embedded inside the ROM. If I root my phone and somehow manage to get rid of this launcher, what's to tell me that Leagoo won't push it silently back onto my device under the disguise of an update?
I don't know what to do here. I understand that based on stock Android, each OEM applies a certain number of modifications to accommodate the hardware it used to build the phone, and since the SoC is brand-new, I gather there aren't many drivers available, unless I leave the current baseline in place.
I'm kinda caught between a rock and a hard place here...

UglyStuff said:
That's the thing: the malware on my phone is part of the application launcher installed by the OEM. In other words, it's embedded inside the ROM. If I root my phone and somehow manage to get rid of this launcher, what's to tell me that Leagoo won't push it silently back onto my device under the disguise of an update?
I don't know what to do here. I understand that based on stock Android, each OEM applies a certain number of modifications to accommodate the hardware it used to build the phone, and since the SoC is brand-new, I gather there aren't many drivers available, unless I leave the current baseline in place.
I'm kinda caught between a rock and a hard place here...
Click to expand...
Click to collapse
If you use malwarebytes after root that thing wont happen. And almost all of the OEMs have a trigger which voids when rooting or flashing firmware. After that the OEM wont give you updates unless you use the A/B partitioning system.

OK, I understand how rooting my phone would void the warranty: after all, it's a substantial change in the phone software, and the OEM can't be made responsible for any mishap that occurs after I've rooted the phone.
What's the A/B partitioning system (I suppose it helps partition your storage space)? I don't have a microSD card installed (I use the slot for my second SIM), but I do have 32 Gb of storage space, minus what's already used up.
Do you know KingRoot? Is it as good and (reasonably) safe a rooting tool as they say it is?