Related
[ROOT GUIDE] How to root the FeiTeng mini N9300/Spreadtrum 6820 !!!
Hi All,
A lot of people out there buy Chinese phones for a good amount of reasons.For one they are cheap and
usually easy to work with.But there comes a time when that isn't enough resulting in many people looking
for ways to hack or the Android term "root" there phone to get the most out of it.Unfortunately they come
across many problems such as No brand name,Unknown brand name,or just no info about it whatsoever.
That is why i have created this guide on rooting the N9300
DISCLAIMER!! This method generally will work with any N9300 android phone i just might take
a few trys and will not harm it.HOWEVER if you do brick your phone i am not responsible.(See pics for details)
WARNING!!! Rooting a device will void ANY warranty you may have.
Phone Specs
Brand: FeiTeng,Spreadtrum,
Device: Hsdroid
Model: N9300
Android: ICS 4.0.3
Build number: 6829_C909_DJGT_V06
Build ID: MocorDroid 2.2.2
CPU: Armeabi-v7a
CPU Frequency: 1Ghz
Board: SP6820a
Display: 3.5 inch Capacitive screen
RAM: 256MB
ROM: 256MB
How to Root:
Lets begin with the actual rooting process
1. Download Z4Root.v1.3.0 and install it on device memory/internal memory (Don't install it on SD Card!!!) and don't open it after installing
2. Go to Setting -> Applications -> Development -> then enable USB debugging
3. Open & run Z4Root
4. Click Temporary Root option, wait till its done successfully and open it again
5. After doing the Temporary Root with no problems,Choose the Permanent Root option
6. Wait and see till it's done
7. After them Permanent Root has done, your device will reboot itself
8. After reboot has done, you will find Superuser has installed on your device
9. It's really easy & safe. But if it not successful & Superuser is not installed, try restarting your device and try from the first step
10. Please remember, this method is for the >>>> Mini <<<< N9300 :angel:
Info
That's it!You have Successfully rooted your device!Now you can install things like
Root App Uninstaller and get rid of root apps or Mount r/w r/o so you can edit
files int the /system folder! If this helped you, post a comment or :good: it,its always a help.
Or if you have a question feel free to ask and ill do my best to help!
Ravage32
question
tnx alot .. some one know how to install google play market on this phone ?
loonbg said:
tnx alot .. some one know how to install google play market on this phone ?
Click to expand...
Click to collapse
Your welcome!I am really trying to get that as well but so far it would always crash.I used uberizer to install it
but i would exit when your select "yes" when you put in your account. :/ I will keep trying and post here when
i find out!
Will this method work for the full sized Feiteng N9300? please reply and thanks
LeeJay7227 said:
Will this method work for the full sized Feiteng N9300? please reply and thanks
Click to expand...
Click to collapse
It should.It wont break it or anything so give it a try.
Ravage32 said:
It should.It wont break it or anything so give it a try.
Click to expand...
Click to collapse
You're full sure it wont break/brick? because i wouldnt know how to fix it :/ i mean i'm no newb to the custom rom/kernerl scene but all ive modded was an xperia x8 so a new device is kind of uncharted water
LeeJay7227 said:
You're full sure it wont break/brick? because i wouldn't know how to fix it :/ i mean i'm no new to the custom rom/kernerl scene but all ive modded was an xperia x8 so a new device is kind of uncharted water
Click to expand...
Click to collapse
Hmmm can you send me your build.prop file so i can have a look at the spec?
Ravage32 said:
Hmmm can you send me your build.prop file so i can have a look at the spec?
Click to expand...
Click to collapse
ordered the phone today, will send file as soon as it comes thanks for the answers mate
No problem . I do a little more research about it and see if i can find anything.
I recieved the phone today, how do i send you the build.prop ?
LeeJay7227 said:
I recieved the phone today, how do i send you the build.prop ?
Click to expand...
Click to collapse
its located in /system directory of your phone.
Copy it from there, and attach it to your next reply
i need root access to go to /system, no?
LeeJay7227 said:
i need root access to go to /system, no?
Click to expand...
Click to collapse
If you use Root Explorer you should be able to still copy the file to your sd card.
Then you can send it to me and i can see if you are able to root it and if there is
any backup firmware for your device. :good:
Ravage32 said:
If you use Root Explorer you should be able to still copy the file to your sd card.
Then you can send it to me and i can see if you are able to root it and if there is
any backup firmware for your device. :good:
Click to expand...
Click to collapse
Ahh root explorer :fingers-crossed:
LeeJay7227 said:
Ahh root explorer :fingers-crossed:
Click to expand...
Click to collapse
i had to put the file in a zip because the uploader said it was an invalid file...
LeeJay7227 said:
i had to put the file in a zip because the uploader said it was an invalid file...
Click to expand...
Click to collapse
Yes it should work! Try it and see if it roots!
If not there are many other rooting programs
Ravage32 said:
Yes it should work! Try it and see if it roots!
If not there are many other rooting programs
Click to expand...
Click to collapse
Thankyou! Is there any chance of bricking? :/
LeeJay7227 said:
Thankyou! Is there any chance of bricking? :/
Click to expand...
Click to collapse
I really doubt it. The only thing is there is a chance it wont root
Ravage32 said:
I really doubt it. The only thing is there is a chance it wont root
Click to expand...
Click to collapse
That's cool okay out of curiosity are there any sites which show how to flash the stock firmware in case of brick/ boot-loop?
LeeJay7227 said:
That's cool okay out of curiosity are there any sites which show how to flash the stock firmware in case of brick/ boot-loop?
Click to expand...
Click to collapse
There is 2 colors on N9300 (Black and White)
I found the firmware for black. Click here for Download
IF you use in on white it wont work. What color do you have?
My advice is to just root it. It wont brick it and then tell me if you are
successful or not. If not i will think of another way.
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.
Hey guys,
I couldn't find it anywhere and I don't really know if this is the right place to ask, but I'll give it a try...
I wonder how does the CF-Auto-Root for the nexus 5 works?
I can see in the windows batch file that it unlocks the bootloader (that's the easy part) and than boot with some image file.
It seems that this tool is not installing any custom recovery which I always saw is a necessary tool for rooting.
What exactly is this image file? what does it do? Where does it come from? What it contains?
Why it's device related (different image files for different nexus devices running the same stock version).
Thanks,
Casteel.
Casteel said:
Hey guys,
I couldn't find it anywhere and I don't really know if this is the right place to ask, but I'll give it a try...
I wonder how does the CF-Auto-Root for the nexus 5 works?
I can see in the windows batch file that it unlocks the bootloader (that's the easy part) and than boot with some image file.
It seems that this tool is not installing any custom recovery which I always saw is a necessary tool for rooting.
What exactly is this image file? what does it do? Where does it come from? What it contains?
Why it's device related (different image files for different nexus devices running the same stock version).
Thanks,
Casteel.
Click to expand...
Click to collapse
Unlocking and rooting is a piece of cake with CF Auto Root for the N5, i never xperienced issues with it. Download CF Root for the Nexus 5, unzip it with 7-zip. Enable usb debugging in developer options, then go into bootloader/fastboot mode, open the uznipped CF Root folder and press Root_windows.bat and follow instructions. Takes 30 seconds - 1 minute all in all.
Thanks, but...
gee2012 said:
Unlocking and rooting is a piece of cake with CF Auto Root for the N5, i never xperienced issues with it. Download CF Root for the Nexus 5, unzip it with 7-zip. Enable usb debugging in developer options, then go into bootloader/fastboot mode, open the uznipped CF Root folder and press Root_windows,bat and follow instructions. Takes 30 seconds - 1 munute all in all.
Click to expand...
Click to collapse
First, thanks for your response.
I don't have a problem with making it work.
As you said, it is super simple and no question it's a great tool.
My question is about how it works? What exactly does it do behind the scene?
Casteel said:
First, thanks for your response.
I don't have a problem with making it work.
As you said, it is super simple and no question it's a great tool.
My question is about how it works? What exactly does it do behind the scene?
Click to expand...
Click to collapse
It unlocks the BL and injects superSU in one go without having to flash a seperate superSU.zip with a custom recovery. Thats all.
gee2012 said:
It unlocks the BL and injects superSU in one go without having to flash a seperate superSU.zip with a custom recovery. Thats all.
Click to expand...
Click to collapse
What do you mean by "injects SuperSU" ?
It sounds very simple from the way you say it. Why can't I do this myself?
I believe it doesn't just mean copy it to the right place.
Does it also include putting the su binary in the right system path with the right permissions?
How does the root privilage is gained?
Does only unlocking the BL let me write to the system partition?
I would really appreciate some technical details to understand this rooting process and what this image file contains.
Thanks again!
Read this http://forum.xda-developers.com/showthread.php?t=2507211 and this http://forum.xda-developers.com/showthread.php?t=1980683. You can also do the root yourself manualy if that more comfortable for you.
gee2012 said:
Read this http://forum.xda-developers.com/showthread.php?t=2507211 and this http://forum.xda-developers.com/showthread.php?t=1980683. You can also do the root yourself manualy if that more comfortable for you.
Click to expand...
Click to collapse
gee2012, I really appreciate your help.
I've already read (most of) these two threads before posted here, and couldn't find an answer to my questions,
only general explanations about how to make it work and how to solve problems,
nothing about HOW it works and what it actually does.
I have already rooted my device with this tool, I don't have any discomfort with is,
just pure technological curiosity about how it works.
Sure, I can also root myself manually, but all the guides I read about it mentioned installing custom recovery, and that tool does it with out it.
Casteel said:
gee2012, I really appreciate your help.
I've already read (most of) these two threads before posted here, and couldn't find an answer to my questions,
only general explanations about how to make it work and how to solve problems,
nothing about HOW it works and what it actually does.
I have already rooted my device with this tool, I don't have any discomfort with is,
just pure technological curiosity about how it works.
Sure, I can also root myself manually, but all the guides I read about it mentioned installing custom recovery, and that tool does it with out it.
Click to expand...
Click to collapse
Look here https://www.google.com/search?q=how+root+works&ie=utf-8&oe=utf-8&aq=t and other sites how root works http://stackoverflow.com/questions/...hat-are-the-pre-requisites-for-it-to-work-wha.
With Google you can find anything
Actually, I read this also...
It only talks about gaining root privilage using some system exploit.
So, you're telling that CF-Auto-Root is running some script in its bootable image file that is using some kind of exploit to gain root access?
Shouldn't it be less "hacky" thing in nexus devices?
And how can it be that the image file is related to specific devices and not to specific stock versions?
What prevents from other apps to use this so called "exploit"?
This is probably what you are looking for...
Embedded in the boot image a folder cfroot with the SuperSU apk file, the su binary and the necessary init scripts and there is a binary under sbin does the remaining steps of copying the files to the respective places. It is not an exploit, it merely uses the boot image and the boot process to "install" SuperSU. You do not need a custom recovery to root your phone, merely the capability to copy the superuser files to the /system partition.
In more detail:
1. Embedded in the ramdisk is a folder "cfroot" with "99SuperSUDaemon, install-recovery.sh, su and Superuser.apk".
2. In the sbin folder in the ramdisk is a binary "cfautoroot" which does stuff like copy the above files to the correct locations and set the appropriate permissions, etc.
3. This file is called through the "recovery" script/binary in the sbin folder
4. The "recovery" script/binary is executed as a startup server via the init system in "init.rc" within the ramdisk
The result:
When you boot up, the superuser files are copied to the respective locations with the right permission, thereby rooting the system
OK! Now we're getting closer
Thank you very much.
But I still have some confusions...
You said:
craigacgomez said:
there is a binary under sbin does the remaining steps of copying the files to the respective places.
You do not need a custom recovery to root your phone, merely the capability to copy the superuser files to the /system partition.
Click to expand...
Click to collapse
How did the "cfautoroot" got to my phone sbin folder?
How do I get the capability to copy the superuser files to the system partition?
Putting things in these folders and set their appropriate permissions doesn't require root from the first place?
How is the init.rc calling the recovery script to run the cfautoroot? shouldn't I need root access to modify init.rc?
[Is the CF-Auto-Root source code available somewhere to see all these files you're talking about?]
It sounds like only unlocking the bootloader is giving me some sort of "root" capabilities to do all these stuff. is it true?
Will this method work in non Nexus devices either?
And what are all those "exploits" that so many rooting guides are talking about?
I'm guessing it desn't have anything with rooting Nexus devices since rooting them is kind of part of their existence, isn't it?
Thanks again! :good:
Casteel said:
OK! Now we're getting closer
Thank you very much.
But I still have some confusions...
You said:
How did the "cfautoroot" got to my phone sbin folder?
How do I get the capability to copy the superuser files to the system partition?
Putting things in these folders and set their appropriate permissions doesn't require root from the first place?
How is the init.rc calling the recovery script to run the cfautoroot? shouldn't I need root access to modify init.rc?
[Is the CF-Auto-Root source code available somewhere to see all these files you're talking about?]
It sounds like only unlocking the bootloader is giving me some sort of "root" capabilities to do all these stuff. is it true?
Will this method work in non Nexus devices either?
And what are all those "exploits" that so many rooting guides are talking about?
I'm guessing it desn't have anything with rooting Nexus devices since rooting them is kind of part of their existence, isn't it?
Thanks again! :good:
Click to expand...
Click to collapse
"cfautoroot" is a binary created by Chainfire which is embedded in the sbin folder in the kernel ramdisk. It's in the CF Auto Root boot image. Android kernels are essentially Linux kernels and have an init process which is basically a bootstrap/startup process. init.rc is part of this process. It is run when the kernel boots up. Anything within the init process is low-level and essentially run as "root". It kick-starts various other processes like zygote which is the Android process management system. This will help you understand the init process a bit better (http://www.mekya.com/blog/2012/03/android-initialization-from-init-rc-to-third-party-code/). In the init.rc file is a line which "executes" the file /sbin/recovery (which is embedded in the ramdisk along with cfautoroot). This in turn "executes" cfautoroot which takes care of copying the superuser files to the correct locations and setting the correct permission. All this is done within the init process and has elevated (root) permission.
Unlocking the bootloader does not root your phone. It simply allows you to flash "unsigned" (custom) boot images.
Any phone with the ability to flash a custom boot image can make use of this process.
Exploits make use of holes or workarounds to either flash a custom boot image or inject files into the system partition without unlocking the bootloader and are only needed if you cannot unlock the phone bootloader.
Hope this helps!
Casteel said:
Hey guys,
I couldn't find it anywhere and I don't really know if this is the right place to ask, but I'll give it a try...
I wonder how does the CF-Auto-Root for the nexus 5 works?
I can see in the windows batch file that it unlocks the bootloader (that's the easy part) and than boot with some image file.
It seems that this tool is not installing any custom recovery which I always saw is a necessary tool for rooting.
What exactly is this image file? what does it do? Where does it come from? What it contains?
Why it's device related (different image files for different nexus devices running the same stock version).
Thanks,
Casteel.
Click to expand...
Click to collapse
Thank you for asking the question and being polite yet persistent about getting your answer. I have been trying to get to this answer myself for some time now.
Sent from my Nexus 5 using Tapatalk
Great! now we're even closer :victory:
So in the boot process I have elevated privilages, that basically what I was missing.
But this bootable image file is not an image of the OS, isn't it?
It is an image of the kernel?
It is some sort of pre-handled file system that the device is booted into and than startup the OS?
Or something like that...?
Thanks for your patient and the very quiqc responses!
We're almost there...
Casteel said:
Great! now we're even closer :victory:
So in the boot process I have elevated privilages, that basically what I was missing.
But this bootable image file is not an image of the OS, isn't it?
It is an image of the kernel?
It is some sort of pre-handled file system that the device is booted into and than startup the OS?
Or something like that...?
Thanks for your patient and the very quiqc responses!
We're almost there...
Click to expand...
Click to collapse
The boot image is not the OS image. It contains the kernel and the ramdisk. The ramdisk is the basically the root filesystem (/) which the kernel mounts, after which the init process begins and init.rc is called. Nothing is ever persisted or modified in the root filesystem unless it is done during the init process or it is embedded in the ramdisk
craigacgomez said:
The boot image is not the OS image. It contains the kernel and the ramdisk. The ramdisk is the basically the root filesystem (/) which the kernel mounts, after which the init process begins and init.rc is called. Nothing is ever persisted or modified in the root filesystem unless it is done during the init process or it is embedded in the ramdisk
Click to expand...
Click to collapse
Nice.
I thought the root file system is part of the OS image.
So basically, I can have the same OS installed on my devices with different file systems according to what is defined in boot?
One last question and I will stop bother you
Why is the image file device related?
Meaning, why nexus 4, 5 and 7 have different CF-Auto-Root?
(Nexus 7 even got several).
Thanks again!
Casteel said:
Nice.
I thought the root file system is part of the OS image.
So basically, I can have the same OS installed on my devices with different file systems according to what is defined in boot?
One last question and I will stop bother you
Why is the image file device related?
Meaning, why nexus 4, 5 and 7 have different CF-Auto-Root?
(Nexus 7 even got several).
Thanks again!
Click to expand...
Click to collapse
Yes, you could theoretically change the way your filesystem is defined via the boot image, but Android as an OS expects some things.
And each device has different autoroot files because they have different kernels and some differences in some init scripts specific to the hardware. Some devices like the Nexus 7 have multiple version (LTE & non-LTE for example) and there are hardware differences and different kernels.
craigacgomez said:
Yes, you could theoretically change the way your filesystem is defined via the boot image, but Android as an OS expects some things.
And each device has different autoroot files because they have different kernels and some differences in some init scripts specific to the hardware. Some devices like the Nexus 7 have multiple version (LTE & non-LTE for example) and there are hardware differences and different kernels.
Click to expand...
Click to collapse
A thousand thanks, Craig Gomez!
You really helped.
I truely appreciate the patient and the kindful responses.
It was a nice first experience in this forum.
Thank you very much!
Casteel said:
A thousand thanks, Craig Gomez!
You really helped.
I truely appreciate the patient and the kindful responses.
It was a nice first experience in this forum.
Thank you very much!
Click to expand...
Click to collapse
Glad I could help you... It's what communities are all about... Sharing knowledge and experiences.
Sent from my Nexus 5
Excellent thread. Thanks to OP and members who responded.
Is it possible to insert the SuperSU Pro Key to flashable SuperSU (maybe with a little bit modification in the script?) so whenever I flash it, it is in Pro version automatically? No need for separate installation...
Odlanyer22 said:
Is it possible to insert the SuperSU Pro Key to flashable SuperSU (maybe with a little bit modification in the script?) so whenever I flash it, it is in Pro version automatically? No need for separate installation...
Click to expand...
Click to collapse
Why do you want pro.... You can enable all pro feature with out having pro key..... Check settings... It has an option for this...
Killwish said:
Why do you want pro.... You can enable all pro feature with out having pro key..... Check settings... It has an option for this...
Click to expand...
Click to collapse
So true sir...
There's no reason to answer why would I go to pro when I can enable pro features for free,,, when I have already the key.
What really matter for now is, if it possible to flash 2 apk in just 1 flashable zip.
I think its possible (somehow)... but I don't know how to create flashable zip. Moreover, I really don't know how to create additional script (or what script to be added) needed to be used in order for key be installed too while SuperSU is being flashed.
Seems like, I what to learn on how to create script that will command to install SuperSU then the key afterwards.
If I'm not mistaken (as I am not a developer or what but a totally noob)... commands/scripts in a flashable zip are written in .sh file?
Odlanyer22 said:
So true sir...
There's no reason to answer why would I go to pro when I can enable pro features for free,,, when I have already the key.
What really matter for now is, if it possible to flash 2 apk in just 1 flashable zip.
I think its possible (somehow)... but I don't know how to create flashable zip. Moreover, I really don't know how to create additional script (or what script to be added) needed to be used in order for key be installed too while SuperSU is being flashed.
Seems like, I what to learn on how to create script that will command to install SuperSU then the key afterwards.
If I'm not mistaken (as I am not a developer or what but a totally noob)... commands/scripts in a flashable zip are written in .sh file?
Click to expand...
Click to collapse
There is no ne to do this...... Just select any apk file abd put it to /system/app folder and restart your device
Would like to further understand something from this too
(i do have linux background)
Technically speaking, what is a rooted device? Is it having the su binary available? Is that what it means?
But then, supersu says that it needs a 'rooted device'.. this is quite rather confusing. doesnt supersu provide root access to apps?
couldnt you combine the key and the app using lucky patcher or a diffrent method?
My device:
Samsung Galaxy S2 Skyrocket (rooted)
Rom:AOSP
Carrier:At&t
Dont forget to thank me if i helped
Killwish said:
There is no ne to do this...... Just select any apk file abd put it to /system/app folder and restart your device
Click to expand...
Click to collapse
No luck... I flashed the SuperSU then push the key to system/app but the key didnt install itself.
That is why I am trying to fig.out how can I insert the key from the flashable zip.
biatche said:
Would like to further understand something from this too
(i do have linux background)
Technically speaking, what is a rooted device? Is it having the su binary available? Is that what it means?
But then, supersu says that it needs a 'rooted device'.. this is quite rather confusing. doesnt supersu provide root access to apps?
Click to expand...
Click to collapse
Not so sure, but a rooted device means having both the su binary and the root access manager (supersu)...?
shadowcreeper_1 said:
couldnt you combine the key and the app using lucky patcher or a diffrent method?
My device:
Samsung Galaxy S2 Skyrocket (rooted)
Rom:AOSP
Carrier:At&t
Dont forget to thank me if i helped
Click to expand...
Click to collapse
I'll thank you if you could give me the procedure on how to combine the key. (Or if I searched for it for giving me an idea)... I havent used Lucky Patcher before. If I am able to combine the two in just 1 apk, then I might just replace the existing apk from the flashable zip so when I flashed it, its in pro version automatically.
Odlanyer22 said:
No luck... I flashed the SuperSU then push the key to system/app but the key didnt install itself.
That is why I am trying to fig.out how can I insert the key from the flashable zip.
Not so sure, but a rooted device means having both the su binary and the root access manager (supersu)...?
I'll thank you if you could give me the procedure on how to combine the key. (Or if I searched for it for giving me an idea)... I havent used Lucky Patcher before. If I am able to combine the two in just 1 apk, then I might just replace the existing apk from the flashable zip so when I flashed it, its in pro version automatically.
Click to expand...
Click to collapse
ill do a little research on that, never attempted it myself but i hear you can and ive seen it happen
My device:
Samsung Galaxy S2 Skyrocket (rooted)
Rom:AOSP
Carrier:At&t
Dont forget to thank me if i helped
shadowcreeper_1 said:
ill do a little research on that, never attempted it myself but i hear you can and ive seen it happen
My device:
Samsung Galaxy S2 Skyrocket (rooted)
Rom:AOSP
Carrier:At&t
Dont forget to thank me if i helped
Click to expand...
Click to collapse
Ah no problem...
Let me research for that by myself.
So far, giving me an idea nearest to what I want to happen is a big help.
I'll give thanks, then.
UPDATE:
According to chelpus(DOT)defcon5(DOT)biz ...that was an exception to the capability of Lucky Patcher. It cannot be patched when the apps are in two parts (apk and pro key)... Btw, still thanks to everyone who effort to helped me.
Waiting for one who can really help me out for what I want.
Odlanyer22 said:
Ah no problem...
Let me research for that by myself.
So far, giving me an idea nearest to what I want to happen is a big help.
I'll give thanks, then.
UPDATE:
According to chelpus(DOT)defcon5(DOT)biz ...that was an exception to the capability of Lucky Patcher. It cannot be patched when the apps are in two parts (apk and pro key)... Btw, still thanks to everyone who effort to helped me.
Waiting for one who can really help me out for what I want.
Click to expand...
Click to collapse
Brother I tried this and it works for me.... You have to restart after putting apk file to system/app folder
---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------
Odlanyer22 said:
No luck... I flashed the SuperSU then push the key to system/app but the key didnt install itself.
That is why I am trying to fig.out how can I insert the key from the flashable zip.
Not so sure, but a rooted device means having both the su binary and the root access manager (supersu)...?
I'll thank you if you could give me the procedure on how to combine the key. (Or if I searched for it for giving me an idea)... I havent used Lucky Patcher before. If I am able to combine the two in just 1 apk, then I might just replace the existing apk from the flashable zip so when I flashed it, its in pro version automatically.
Click to expand...
Click to collapse
Restart your device after putting apk to system /app folder
nthsfrn cels
Killwish said:
Brother I tried this and it works for me.... You have to restart after putting apk file to system/app folder
---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------
Click to expand...
Click to collapse
Are you really pertaining to "pro key" apk too or other apk file?
It works for other apk but didn't work for pro key apk (in my case)...
AND I am wrong for my term "push" when I did not actually push it, but rather flashed it...
I flashed it right after flashing flashable SuperSU.
I placed the pro key inside a zip file>system>app (Idk where that zip file originated)... then flashed it
(all via cwm recovery).
(Btw, that zip file is really meant to flash apk to system/app or system/framework if you are afraid to push.)
Then after that, "reboot system now".
Viola! Nothings happen, but to go to system/app (look for the pro key) then install it there then restart.
(It works after that.)
..
Killwish said:
OK bro I have made flashable zip supersu.
Its here
View attachment 2841612
It is super user 2.01 pro
Flash it with any custom recovery
Click to expand...
Click to collapse
downloading and will try it later:good:
Killwish said:
OK bro I have made flashable zip supersu.
Its here
View attachment 2841612
It is super user 2.01 pro
Flash it with any custom recovery
Click to expand...
Click to collapse
OMG!
Downloading and try it ASAP...
FEEDBACK:
It doesn't work. Maybe you just put the pro key inside the zip and you didn't even bother to modify the script so its useless.
Only free version will going to install in the end.
Odlanyer22 said:
OMG!
Downloading and try it ASAP...
FEEDBACK:
It doesn't work. Maybe you just put the pro key inside the zip and you didn't even bother to modify the script so its useless.
Only free version will going to install in the end.
Click to expand...
Click to collapse
Not just copy pasted...... Sorry for that but now i updated file again...
Download again that file
this time 100% working
Killwish said:
Not just copy pasted...... Sorry for that but now i updated file again...
Download again that file
this time 100% working
Click to expand...
Click to collapse
Sorry!
Ok, I'll try to redownload...
Btw, thank you very much for the effort sir!
Killwish said:
OK bro I have made flashable zip
Its here
UPDATED
It is super user 2.01 pro
View attachment 2841940
Flash it with any custom recovery
Click to expand...
Click to collapse
Maybe you're unaware of this but i think you should remove this download immediately, you're givivg away the pro version for free
respawn
harrymason37 said:
Maybe you're unaware of this but i think you should remove this download immediately, you're givivg away the pro version for free
respawn
Click to expand...
Click to collapse
Okk ... I'll ... thank you sir
biatche said:
Would like to further understand something from this too
(i do have linux background)
Technically speaking, what is a rooted device? Is it having the su binary available? Is that what it means?
But then, supersu says that it needs a 'rooted device'.. this is quite rather confusing. doesnt supersu provide root access to apps?
Click to expand...
Click to collapse
Yes, exactly.
The problem is that people have adopted the term rooted to also mean access to the root of the filesystems, iow, the / directory. ("Just place this file on the root of your SD card," being the most common example of that usage.)
Anyway, with / access you can remount /system to rw instead of ro, and from there you can install the su binary (either in /system/bin or /system/xbin depending on how the dev made the installer).
The apk is simply the front end (user facing) management layer.
And then toss in the common Linux misunderstanding that's bled over to Android that su stands for super user. It doesn't, it stands for set user, but without arguments (the way most people have seen it) defaults to setting you to the root user.
As a Linux user, it might be just as well to think of the apk as your sudo access assistant, and to think of the grant/deny popup as analogous to confirming access with your password.
If you haven't already, install a good busybox (I prefer this one) -
Check out "BusyBox"
https://play.google.com/store/apps/details?id=stericson.busybox
And then Terminal Emulator and look around just as you would on Linux.
Your filesystem layout will make more sense one you use the df and mount commands there.
Hope this helps.
PS - Also, a thank you for taking down the pro download.
harrymason37 said:
Maybe you're unaware of this but i think you should remove this download immediately, you're givivg away the pro version for free
respawn
Click to expand...
Click to collapse
Let me be the one to apologize sir.
He just helping me out. But I do understand it too...
I really sorry!
And finally, it works 100%
All I want to know now is how did he insert the pro key. XD
So I can do it by myself anytime.
[CASE CLOSED]
Hi there are a few version of the Galaxy Tab 4 8.0 that have no support for a custom recovery.
Source files have been found and are ready to be worked with.
The devices we would like to bring support to are the:
T330NU source file:
http://www.4shared.com/zip/UG28maH2ce/SM-T330NU_NA_KK_Opensource.html
T335K source file:
http://www.4shared.com/zip/9Y4qzw1zce/SM-T335K_KK_Opensource.html
T335L source file:
http://www.4shared.com/zip/nZ4xmfNgba/SM-T335L_KK_Opensource.html
T337a source file:
http://www.4shared.com/zip/21kf9dZYce/SM-T337A_NA_KK_Opensource.html
Boot.img dumped from device T330NU:
http://www.4shared.com/file/nOAtJQbCba/boot.html
Recovery.img dumped from device T330NU:
http://www.4shared.com/file/mSkFIM0Bce/recovery.html
If ANYONE is willing or knows someone who could be willing to port a custom recovery to these devices it would be greatly appreciated if you could pass on the message and spread the word. If we all do work together we should be able to get this done.
There are many people who are willing to test the final work. Thanks in advance.
Hey, I am dedicated to get a recovery for this device also. I am pretty good with computers but have never worked on a recovery project. I do have Linux and can help if needed on anything.
There should be a guide on xda
smknutson said:
There should be a guide on xda
Click to expand...
Click to collapse
I tried recovery builder but had no luck. Was not able to download files after building. Says build has been queud or something like that. Was having trouble getting the stock recovery img off of the phone.
Leonidas87 said:
I tried recovery builder but had no luck. Was not able to download files after building. Says build has been queud or something like that. Was having trouble getting the stock recovery img off of the phone.
Click to expand...
Click to collapse
I have my stock recovery.img if needed
pre4speed said:
I have my stock recovery.img if needed
Click to expand...
Click to collapse
Which Galaxy tab version do you have?
And have did you extract your stock recovery img?
Leonidas87 said:
Which Galaxy tab version do you have?
And have did you extract your stock recovery img?
Click to expand...
Click to collapse
I have the 337a and yup pulled recovery.img and boot.img
pre4speed said:
I have the 337a and yup pulled recovery.img and boot.img
Click to expand...
Click to collapse
My last message had a spelling mistake sorry about that. How did you pull those files tho? I've been having trouble on this device
Leonidas87 said:
My last message had a spelling mistake sorry about that. How did you pull those files tho? I've been having trouble on this device
Click to expand...
Click to collapse
In terminal, type su dd if=/dev/emmc/"boot partition" of=/sdcard/recovery.img
I think you need to enter after su. It will save it to your sd. This is assuming root. You enter your boot partition in the quotes. Use this to find your partitions.
https://play.google.com/store/apps/details?id=com.cls.partition
pre4speed said:
In terminal, type su dd if=/dev/emmc/"boot partition" of=/sdcard/recovery.img
I think you need to enter after su. It will save it to your sd. This is assuming root. You enter your boot partition in the quotes. Use this to find your partitions.
https://play.google.com/store/apps/details?id=com.cls.partition
Click to expand...
Click to collapse
Thanks for the help I think I understand. I have terminal ready and the app installed. Just not sure which partition is the one to fill in the quotations in the terminal.
I'm attaching pictures if that helps.
Also I'm sure I do not include the actual quotes when typing in terminal just to save myself from confusion. I do have root by the way
UPDATE:
THESE PICTURE WERE FOR MY GALAXY NOTE 3 DISRAGAURD THESE PHOTOS. My mistake I was on my phone when I read the message and tried to jump right into it
THERE ARE THE PHOTOS FROM MY GALAXY TAB 4.
These would be the correct locations I need clarification so I know which ones are boot and recovery for pulling/extracting in terminal.
These two represent your recovery and boot partitions. So in the quotes you'll put the mmcblk0p15 for recovery.img.
I found that pulling the recovery is that exact code, whereas pulling the boot was a different code, but found easily on the internet. I got the recovery easy, the boot was a little more work, but did get it.
pre4speed said:
These two represent your recovery and boot partitions. So in the quotes you'll put the mmcblk0p15 for recovery.img.
I found that pulling the recovery is that exact code, whereas pulling the boot was a different code, but found easily on the internet. I got the recovery easy, the boot was a little more work, but did get it.
Click to expand...
Click to collapse
Think I am not typing it exactly how it needs to be. Even tried copy and pasting. So close but yet so far lol. I really think we have all been making progress the last few days. This would help if I could get it to work. Would be useful and handy to have a backup for each device variation.
Pic did not upload for me the first time. Backup did not work yet. I must be typing or copy and pasting wrong
I'm trying to remember how I did it. I believe you open terminal, type su then press enter, then type the rest. Let me do it again and see what my steps were.
---------- Post added at 01:26 PM ---------- Previous post was at 01:13 PM ----------
Ok, I'm sorry. The code I gave you is actually for the boot.img not recovery. Here is the right code. Sorry again.
Type it exactly as I did and you'll find the backup on your sdcard (not external). I actually found the correct code in the 7.7" tab thread. Lol http://forum.xda-developers.com/showthread.php?t=1540641
pre4speed said:
I'm trying to remember how I did it. I believe you open terminal, type su then press enter, then type the rest. Let me do it again and see what my steps were.
---------- Post added at 01:26 PM ---------- Previous post was at 01:13 PM ----------
Ok, I'm sorry. The code I gave you is actually for the boot.img not recovery. Here is the right code. Sorry again.
Type it exactly as I did and you'll find the backup on your sdcard (not external). I actually found the correct code in the 7.7" tab thread. Lol http://forum.xda-developers.com/showthread.php?t=1540641
Click to expand...
Click to collapse
I'm just out right now but will give it a try as soon as I get home. Thanks again much help. Will report back.
Leonidas87 said:
I'm just out right now but will give it a try as soon as I get home. Thanks again much help. Will report back.
Click to expand...
Click to collapse
Ok I have got both recovery and boot.img backed up/pulled. Finally lol thanks a lot
I think we have most of the necessary files to get the job done. If you say you have got you boot.img and recovery backed up and so do I. We have source files also. All we need now is for the recovery to be compiled. For a skilled experienced developer to finish up what we started probably would not be too hard. If only we had someone to really take the time with us with some of the next key steps. I am looking up guides and resources all over the Internet but nothing concrete to get the job done ?
Leonidas87 said:
I think we have most of the necessary files to get the job done. If you say you have got you boot.img and recovery backed up and so do I. We have source files also. All we need now is for the recovery to be compiled. For a skilled experienced developer to finish up what we started probably would not be too hard. If only we had someone to really take the time with us with some of the next key steps. I am looking up guides and resources all over the Internet but nothing concrete to get the job done ?
Click to expand...
Click to collapse
Yeh, I hear that. Like I said before, I've got my buddies looking at it, but these devices that they don't own aren't a priority for them. I don't feel right bugging them about it every day. I'll see if there's anything I can find. I'm not a developer and get lost with code, but guides I can help to find if you have the build environment.
http://rootzwiki.com/topic/23903-how-to-compile-twrp-from-source/
http://forum.xda-developers.com/showthread.php?t=1943625
I am so lost with all that[emoji30]
Leonidas87 said:
Hi there are a few version of the Galaxy Tab 4 8.0 that have no support for a custom recovery.
If ANYONE is willing or knows someone who could be willing to port a custom recovery to these devices it would be greatly appreciated if you could pass on the message and spread the word. If we all do work together we should be able to get this done.
There are many people who are willing to test the final work. Thanks in advance.
Click to expand...
Click to collapse
if you are able to install an omnirom build environment on linux i will make you a local_manifest and show how to build.