Related
The world's first ereader with a color Mirasol display is finally on the market, but unfortunately it's running a severely locked-down Android by the Korean bookstore chain Kyobo. The Kyobo ui is entirely in Korean, the browser blocks downloads, and the reader app is crap. In other words, it's basically useless to anyone outside of Korea. A few enterprising Americans have imported them and been extremely disappointed. Will someone please take a look at this device and see if it can be rooted or if something else can be done to make it of use to the rest of us?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Nate over at The Digital Reader has a firmware update that supposedly contains all of the installed apps. He is asking for someone to try and hack it. He has a download link for the firmware at The Digital Reader.
I also posted this as a question here on XDA:
http://forum.xda-developers.com/showthread.php?t=1432283
it is rooted since some time already.
files and instructions are in the following archive, but since instructions are in korean, i'll do a writeup below.
(argh! spambot won't allow this link, so you'll have to piece it together...)
www<dot>4shared<dot>com/zip/aLwRc7ZG/mirasol_rooting.html
edit: needed files are also in an attachment below
the gist is that you need to flash the boot partition via fastboot, setup root and busybox, and then modify secure->install_non_market_apps in settings.db.
you will need to have adb and fastboot from the android sdk working on your computer. There are many posts about this elsewhere, so i won't go into the details.
also, i only print filename without path, just find the corresponding file in the mentioned archive and modify the commands accordingly.
flash the boot partition via fastboot
first get your kyobo into fastboot mode (with usb cable attached) by pressing volume-down at bootup. timing here can be a bit finicky, but easiest seems to be to shut it down completely and then press just after pressing power.
issue a 'fastboot devices' on computer, if successful it should give you the response '???????????? fastboot' or similar. if empty or hangs, try again by rebooting the kyobo by pressing power with volume-up held (you can go into fastboot immediately after reboot by volume-down as expected).
when positive response above, you can flash by
Code:
fastboot flash boot boot.img
and then reboot by
Code:
fastboot reboot
edit: simplified fastboot instructions, thanks to smb_gaiden, whose button-poking-fu is strong.
setup root and busybox
with boot partition flashed you now have adb access, so let's use it. let the device boot as normal, and then issue the following.
Code:
adb push busybox /data/local/tmp
adb push fixsu.sh /data/local/tmp
adb push su /data/local/tmp
adb shell chmod 777 /data/local/tmp/busybox
adb shell chmod 777 /data/local/tmp/fixsu.sh
adb shell chmod 777 /data/local/tmp/su
adb shell /data/local/tmp/fixsu.sh
adb shell ln -s /data/local/tmp/busybox /system/xbin/busybox
after this, install some apk's from the archive
Code:
adb install superuser.apk
adb install blackmart.apk
fix non-market apps setting
only thing left is to change a setting to allow non-market apps to be installed. if you don't care about your current settings (locale, etc), you can just push the settings.db from the archive like so:
Code:
adb push settings.db /data/data/com.android.providers.settings/databases/
if you *do* care about your settings, you'll need to pull the settings.db, edit it in some sqlite db editor (set secure->install_non_market_apps to 1) and push the result.
that's it. all rooted. now you just need to install angry birds and yer' set ;-)
Adb doesn't seem to start properly on device
Hello.
I did succeed in flashing the bootloader via fastboot.
However when I boot device - I see adb on usb only for some initial seconds, and then it disappears.
For that matter my device already had December firmware on it.
Any ideas how to activate adb on device?
Thank you,
Leonid
it may be that persist.service.adb.enable is reset, stopping the adbd service. try flashing the attached boot image instead, see if that fixes it. it is the same as above, except that persist.service.adb.enable is ignored.
edit: i took a look at the december update, afaict it should pose no problem (very few changes in there).
Once these steps are done, how do you install google market?
Thanks.
edit: the original instructions were snafu, so i replaced them with something that should actually work.
getting android market running on the kyobo
needed files are in the attached archive.
install like so:
Code:
adb remount
adb push DrmProvider.apk /system/app
adb push MediaProvider.apk /system/app
adb push DownloadProvider.apk /system/app
adb push GoogleServicesFramework.apk /system/app
adb push Market-3.4.4.apk /system/app
adb push init.qcom.post_boot.sh /system/etc
adb push fix-shared-user.sh /data/local/tmp
adb shell chmod 777 /data/local/tmp/fix-shared-user.sh
adb shell /data/local/tmp/fix-shared-user.sh
wait for the reboot, find market in the menu, and off you go (with downloads this time ;-)
if downloads still do not work after this, try re-executing the last line. android periodically writes to the file we are modifying, which might clobber our changes if unlucky.
I am thinking about buying one of these because I have seen it on sale for 50% discount. However, the general reviews aren't too encouraging, so will rooting make any difference to overall performance?
fatboy1976 said:
I have seen it on sale for 50% discount.
Click to expand...
Click to collapse
where is that?
throwaway4096 said:
you'll need GoogleServicesFramework.apk and Market-3.4.4.apk from the following links:
http://androidmarketu.googlecode.com/files/GoogleServicesFramework.apk
http://forum.xda-developers.com/showthread.php?t=1391565
install like so:
Code:
adb remount
adb push GoogleServicesFramework.apk /system/app
adb push Market-3.4.4.apk /system/app
find Market in the menu and off you go.
Click to expand...
Click to collapse
I'm finding the market force closes when downloading an app.
May I seek help from someone who has rooted recently? I am finding it pretty difficult to get into fastboot. So some questions as I continue to play.
Which version is currently rootable? I bought mine this week and want to be sure it is still applicable with the method here.
Do I need a USB driver to work this hack? EDIT: Yes, found with a web search.
When do I press the volume keys? Immediately after power? Similar timing? When I see the flicker on the screen? When I see the logo? Before all that? EDIT: I did not need the volume up key to get into fastboot.
Thanks!
rooting for beginners
Some friends and i ordered the kyobo to solve our eye-problem (nystagm)
We still can´t figure out, how to root it.
Can you please give us some rooting instruktion vor beginners??
It would be so essential for us, as the kyobo is little worth without forgeign apps!
Thank you very much!
Joe
send2toonie said:
I'm finding the market force closes when downloading an app.
Click to expand...
Click to collapse
Hi, I am stuck with the same problem. Have tried many things?!
---------- Post added at 04:57 PM ---------- Previous post was at 04:32 PM ----------
smb_gaiden said:
May I seek help from someone who has rooted recently? I am finding it pretty difficult to get into fastboot. So some questions as I continue to play.
Which version is currently rootable? I bought mine this week and want to be sure it is still applicable with the method here.
Do I need a USB driver to work this hack? EDIT: Yes, found with a web search.
When do I press the volume keys? Immediately after power? Similar timing? When I see the flicker on the screen? When I see the logo? Before all that? EDIT: I did not need the volume up key to get into fastboot.
Thanks!
Click to expand...
Click to collapse
Hi, Managed to root my kyobo after about 8 h trying. I installed the firmware update on my kyobo, that is found on the web, as instructed from the SD card. Then I installed fastboot and adb on my computer (search for 'how to install fastboot and adb'), as I found instructions for that as well. To enter fastboot I kept Kyobos, volume down button for about 10 sec, when booting the device (kyobo connected to computer with USB) - nothing happens -> however on my computers command window (cmd), 'fastboot devices' command produces an answer with '? ..' as it should. The biggest issue I had was to get adb working. For this purpose I installed and removed a couple of USB drivers - I don't really know how I got it to work finally.
You can tell if you have succeeded installing a useful usb driver, if you enter the 'adb devices' command in the cmd window and it returns a device number. Then you are ready to go with the rest of the commands/instruction as seen in the insturction of this thread.
From the blackmart application I was able to install many useful applications - the Launcher application can replace the Kyobo "home" application, which is very useful.
I installed android market as well, but so far I have not been able to download and install applications. I think It might be a permission issue between kyobo software and the installed android market?
Hey Guys!
is there a way to root the kyobo via mikrosd?
thanks a lot
Joe
Hey Joe. I've seen you on this forum as well as The Digital Reader asking for help with the Kyobo rooting. I too am a beginner and I'm trying to build up the nerve to try it. Wish us both luck and I hope someone can share rooting-for-dummies with us.
@fatboy1976: rooting won't improve performance in itself. it makes the device better as you can install apps, but ofc the hardware is still the same.
@send2toonie: yes, sorry about that. it worked for me, but only thanks to other changes. it's hard to keep track :-/. i updated the original post with new instructions which should work properly.
@smb_gaiden: hah, excellent, i never tried that! original post updated.
@Joe84: it should be possible to root via microsd by creating an update.zip. i haven't gotten around to trying that yet, but maybe in future. for now this is as simple as it gets.
Kaarlos said:
Hi, I am stuck with the same problem. Have tried many things?!
---------- Post added at 04:57 PM ---------- Previous post was at 04:32 PM ----------
Hi, Managed to root my kyobo after about 8 h trying. I installed the firmware ...(updated -see above..) .., which is very useful.
I installed android market as well, but so far I have not been able to download and install applications. I think It might be a permission issue between kyobo software and the installed android market?
Click to expand...
Click to collapse
Jep! With the updated instuctions the Android Market now finally works!! Thanks! (Installed twice)
Kaarlos said:
Jep! With the updated instuctions the Android Market now finally works!! Thanks! (Installed twice)
Click to expand...
Click to collapse
Hi,
Could you post the OS/processor version and driver name that got adb working for you. If you can also remember the keys pressed to put the Kyobo in the correct boot mode for adb, that would be nice too.
I have also managed to load apps on my Kyobo but that is without having su, Superuser, adb and Android Market working. The above info would be helpful in fixing that. Holding the volume down fir 10 seconds after pressing power on puts the Kyobo into fastboot mode. Adb requires a different mode and set of key presses. This is because there is a menu of boot options being displayed which can't be seen on the Mirasol screen. I suspect this is because of display settings within the boot.img but that is only a guess on my behalf.
Hello,
Here is the short story.
I have Samsung Galaxy ACE which is rooted.
Till y'day I was using CM9 Beta 8 ICS 4.0.4 and it was working well.
I installed CM10 JB for Galaxy Ace alpha1 from "hxxp://maclaw.pl/?page_id=180#comment-3642"
Now the problem is, JB doesn't have File Manager installed and I need to install TB to revert my backups.
Due to some unknown reason I am not able to access internet on my device either through GPRS or 3G connection.
I am desperately looking for a way to access my SDCARD wherein I have all my apk's which I can install however, without File Manager I am not sure how to install an apk.
I did some google search and came across topics about installing apk using Android SDK etc.. however I would not want to work on SDK as I feel its bit tedious job for me.
I also tried Android Injector however that didnt work even if I have enabled USB debugging Mode for adb + apps.
Now, I am hoping that, I can use the Terminal Emulator which is preinstalledo n my phone to install apk present on my sdcard.
However, I am not sure how to do that, It would be really appreciated if anyone can suggest the steps to install apk present on my sdcard from Terminal Emulator available on my phone.
Here are some of the screen captures
http://imageshack.us/photo/my-images/855/screenshot2012072418240.png/
http://imageshack.us/photo/my-images/52/screenshot2012072418234.png/
http://imageshack.us/photo/my-images/822/screenshot2012072418230.png/
Thanks
Never mind...
I managed to install Astro File Manager apk from Terminal Emulator.
For those who are interested, here is what I had done.
Previously, I wasn't able to browse sdcard contents from TE,
I rebooted my phone once, fired up TE again
~Android$ su
Allow root access for TE
~Android# cd sdcard
~Android# ls ( Contents of SD card are listed ) I had copied astrofm.apk on root of SDCARD
~Android# pm install astrofm.apk
Success !
Thanks
P.S. This thread can be closed.
@@
hsotnas said:
Never mind...
I managed to install Astro File Manager apk from Terminal Emulator.
For those who are interested, here is what I had done.
Previously, I wasn't able to browse sdcard contents from TE,
I rebooted my phone once, fired up TE again
~Android$ su
Allow root access for TE
~Android# cd sdcard
~Android# ls ( Contents of SD card are listed ) I had copied astrofm.apk on root of SDCARD
~Android# pm install astrofm.apk
Success !
Thanks
P.S. This thread can be closed.
Click to expand...
Click to collapse
Awesome guide !!!! , thanks bro !! :good::fingers-crossed:
Thank you for the guide
it works. thank you
works, thanks
hsotnas said:
Never mind...
I managed to install Astro File Manager apk from Terminal Emulator.
For those who are interested, here is what I had done.
Previously, I wasn't able to browse sdcard contents from TE,
I rebooted my phone once, fired up TE again
~Android$ su
Allow root access for TE
~Android# cd sdcard
~Android# ls ( Contents of SD card are listed ) I had copied astrofm.apk on root of SDCARD
~Android# pm install astrofm.apk
Success !
Thanks
P.S. This thread can be closed.
Click to expand...
Click to collapse
I very much appreciate the quick tutorial!
However, with that being said, I am having an issue trying to install my .apk onto my Motorola Xoom (Rooted running CM10.1) through the use of Terminal Emulator. I first tried installing the .apk from my File Manager and just clicking on the icon, and clicking Install, like one would think one should be able to do. When that method failed, multiple times(kept saying "insufficient storage, please delete files through app manager") which by the way, I know for a fact I have 15.8GB of storage left on my Xoom, so this should not be the issue. I then decided to try and install through Terminal Emulator. Now one would think it would be about the same as using adb commands on a Computer, which it somewhat is I guess you could say. So I go to T.E. and type the commands to get Super User access, then cd sdcard to go into the directory, then cd download because this is where my file is located, then I type pm install ****.apk.
I get a line of command that says: a) pkg: ****.apk and then b) Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE], and then the command line just goes back to my download folder directory.
I've had this issue before on my Galaxy S3, but can't remember how I ended up resolving the issue. Think I did a factory data reset/wipe, which I don't want to have to do to my Xoom. So any assistance would be much appreciated. I do understand that your device was a Galaxy ACE, but I wouldn't think it would matter as to what the device is, since it is the same install method/command for any Android device essentially. Hope someone can help out. If not, I may have to post in another Device Thread (Motorola Stingray Xoom I would assume).
Many thanks in advance, and I will click the Thank You, if any responses come through.
Really appreciate for the guide man
Sent from my LG-P700 using xda app-developers app
Thanks for the reply... short, to the point, and it works.
DannyShane said:
I very much appreciate the quick tutorial!
However, with that being said, I am having an issue trying to install my .apk onto my Motorola Xoom (Rooted running CM10.1) through the use of Terminal Emulator. I first tried installing the .apk from my File Manager and just clicking on the icon, and clicking Install, like one would think one should be able to do. When that method failed, multiple times(kept saying "insufficient storage, please delete files through app manager") which by the way, I know for a fact I have 15.8GB of storage left on my Xoom, so this should not be the issue. I then decided to try and install through Terminal Emulator. Now one would think it would be about the same as using adb commands on a Computer, which it somewhat is I guess you could say. So I go to T.E. and type the commands to get Super User access, then cd sdcard to go into the directory, then cd download because this is where my file is located, then I type pm install ****.apk.
I get a line of command that says: a) pkg: ****.apk and then b) Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE], and then the command line just goes back to my download folder directory.
I've had this issue before on my Galaxy S3, but can't remember how I ended up resolving the issue. Think I did a factory data reset/wipe, which I don't want to have to do to my Xoom. So any assistance would be much appreciated. I do understand that your device was a Galaxy ACE, but I wouldn't think it would matter as to what the device is, since it is the same install method/command for any Android device essentially. Hope someone can help out. If not, I may have to post in another Device Thread (Motorola Stingray Xoom I would assume).
Many thanks in advance, and I will click the Thank You, if any responses come through.
Click to expand...
Click to collapse
Hi DannyShane,
Not sure if this is still relevant and you are around here, since it's been a very long time and I stopped using Android
I am not an Android geek but here are my 2 cents...
You need to keep .apk file on the root of the SD CARD instead of a folder. IIRC, I had the same exact error which you had mentioned, I was trying to install .apk which was placed in a folder and it didnt work., then I had to move the .apk file to root and it worked flawlessly.
Extremely sorry for the very late response though. I use my secondary e-mail for this forum and missed replies on this thread.
@ All others who have replied, I am glad that, my little finding helped you guys.
Cheers :angel:
I have a few things to add to hsotnas answer. The insufficent space error seems to be a very generic error on android that can have various causes. Maybe there is something like this in the android source code:
PHP:
try{
installApk();
} catch (Exception ex){
output("Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]");
}
If you understand what I mean
I had this error myself a few days ago and for me it was caused by some left over files in the /data/app-lib directory. It was a self-developed application and I added a library to this directory manually. As I uninstalled the application, it wasn't removed and the reinstall failed with the above mentioned error. So make sure the directories /data/data/app.package.name/ and /data/app-lib/app.package.name/ are empty.
I tried this, to install the play store apk. But I get the error INSTALL_FAILED_INVALID_URI. What is this error refering to?
PSV_Supporter said:
I tried this, to install the play store apk. But I get the error INSTALL_FAILED_INVALID_URI. What is this error refering to?
Click to expand...
Click to collapse
Me too same thing happens when I try to install 3.apk
the command used is "pm install apps/*.apk"
Mine are backups of play store
Thankyou for this tutorial... IT WORKS.. Can't believe it.. You made my day. Thankyou :good:
I'm trying to recover an old tablet and need to install a file manager... the touch screen inst working so I thought terminal would do the job... but .APK's dont show when I go to the root of the SD card and type 'ls'
An ideas?
Thanks it works
failed on me ..
Hi,
Can someone if any provide us with his experience with unlocking HTC Butterfly (Singapore & China Version) and installing recovery ??
Is there any success on this matter??
Unlocked successfully but still no working recovery !!!!
kdahri said:
Unlocked successfully but still no working recovery !!!!
Click to expand...
Click to collapse
Depends on which phone you are talking about.
920e (China Version) you can use DNA's recovery.
920d (International Version/Singapore version?) unlock available but no working recovery.
katsuya82 said:
Depends on which phone you are talking about.
920e (China Version) you can use DNA's recovery.
920d (International Version/Singapore version?) unlock available but no working recovery.
Click to expand...
Click to collapse
I have the 920e, DNA recovery DEFINITELY DOES NOT WORK! So far no one has gotten recovery working on 920e. I am in China currently and reading through all the chinese sites people are trying to use TWRP and CMW posted on XDA but no luck.
jlevy73 said:
I have the 920e, DNA recovery DEFINITELY DOES NOT WORK! So far no one has gotten recovery working on 920e. I am in China currently and reading through all the chinese sites people are trying to use TWRP and CMW posted on XDA but no luck.
Click to expand...
Click to collapse
Sorry if I'm wrong, but I found all those info from google, it seems these people are able to boot into recovery to flash SU
The Chinese sites are very confusing when they are naming the phone. Many sites just call it X920e/Butterfly/DNA but they are acutally 3 different phones.
http://www.netded.com/a/jingpinshouji/2012/1228/25162.html
http://baodian.zol.com.cn/detail_19037.html
http://htc.zol.com.cn/113/33080_1123081.html
katsuya82 said:
Sorry if I'm wrong, but I found all those info from google, it seems these people are able to boot into recovery to flash SU
The Chinese sites are very confusing when they are naming the phone. Many sites just call it X920e/Butterfly/DNA but they are acutally 3 different phones.
http://www.netded.com/a/jingpinshouji/2012/1228/25162.html
http://baodian.zol.com.cn/detail_19037.html
http://htc.zol.com.cn/113/33080_1123081.html
Click to expand...
Click to collapse
I've tried all of those and none work. Look at the screenshot for the 1st link, that's a recovery for the Galaxy S2. Hard to trust some of those chinese sites, that's why I come here knowing that the good devs of XDA will figure things out
Had the chance to sneak into China and get a HTC Butterfly (920e variant) there for myself. Full of Chinese crap apps and no Google apps at all
Anyway, unlock (via htcdev) worked fine but that's pretty much where the fun stops so far. Like jlevy73 I tried pretty much everything written anywhere on the interwebz and nothings works. No recovery, no root, no gapps, no play store.
red_trela said:
Had the chance to sneak into China and get a HTC Butterfly (920e variant) there for myself. Full of Chinese crap apps and no Google apps at all
Anyway, unlock (via htcdev) worked fine but that's pretty much where the fun stops so far. Like jlevy73 I tried pretty much everything written anywhere on the interwebz and nothings works. No recovery, no root, no gapps, no play store.
Click to expand...
Click to collapse
Yep, quite sad.
Off topic, anyone here with the X920e having issues with HTC Sense Weather? I'm in Beijing and the weather is off by about 10F. It's also night but the icon shows the sun. I've cleared data for both weather and HTC Sense but no luck. GPS is working ok though.
red_trela said:
Had the chance to sneak into China and get a HTC Butterfly (920e variant) there for myself. Full of Chinese crap apps and no Google apps at all
Anyway, unlock (via htcdev) worked fine but that's pretty much where the fun stops so far. Like jlevy73 I tried pretty much everything written anywhere on the interwebz and nothings works. No recovery, no root, no gapps, no play store.
Click to expand...
Click to collapse
u can still flash DNA recovery and gain temp root, just u can't use the full function of recovery. from there you can still install Google Play etc, and remember not to reboot the phone.
I'm wondering if you bought 920e and use it outside of China, will you be able to connect to 3G services? I thought 920e is TD-CDMA instead of WCDMA.
katsuya82 said:
u can still flash DNA recovery and gain temp root, just u can't use the full function of recovery. from there you can still install Google Play etc, and remember not to reboot the phone.
I'm wondering if you bought 920e and use it outside of China, will you be able to connect to 3G services? I thought 920e is TD-CDMA instead of WCDMA.
Click to expand...
Click to collapse
How do you flash gapps if you cannot get into recovery? How do you flash SU without getting into recovery? Perhaps I am missing something obvious.
The 920e is WCDMA only so in China it would be compatible with China Unicom. TD-CDMA is what China Mobile uses. The 920e would be compatible with ATT in the US.
katsuya82 said:
u can still flash DNA recovery and gain temp root, just u can't use the full function of recovery. from there you can still install Google Play etc, and remember not to reboot the phone.
I'm wondering if you bought 920e and use it outside of China, will you be able to connect to 3G services? I thought 920e is TD-CDMA instead of WCDMA.
Click to expand...
Click to collapse
More or less (once more) just confirming / repeating what jlevy73 said:
- How do you gain temp root if the (DNA) recovery doesn't seem to work properly?
- Why not reboot the phone? oO Because of the broken recovery? That is not run in a normal boot up.
- the x920e is made to work with China Unicom exclusive (but interestingly isn't simlocked) in Mainland China and they use WCDMA which works perfectly here in Europe. No 4G chip, though.
red_trela said:
More or less (once more) just confirming / repeating what jlevy73 said:
- How do you gain temp root if the (DNA) recovery doesn't seem to work properly?
- Why not reboot the phone? oO Because of the broken recovery? That is not run in a normal boot up.
- the x920e is made to work with China Unicom exclusive (but interestingly isn't simlocked) in Mainland China and they use WCDMA which works perfectly here in Europe. No 4G chip, though.
Click to expand...
Click to collapse
It's possible that recovery was installed, we're just not able to access it in the traditional way. I am going to try and adb push superuser into recovery. If that works, then we will have root and can then push google apps into recovery. I am going to give it a go and see what happens.
jlevy73 said:
It's possible that recovery was installed, we're just not able to access it in the traditional way. I am going to try and adb push superuser into recovery. If that works, then we will have root and can then push google apps into recovery. I am going to give it a go and see what happens.
Click to expand...
Click to collapse
Having any success? Tried it myself and while adb reports success, there's no su once I boot the device normally.
---------- Post added at 04:57 PM ---------- Previous post was at 04:49 PM ----------
red_trela said:
Having any success? Tried it myself and while adb reports success, there's no su once I boot the device normally.
Click to expand...
Click to collapse
Okay, just embarassing myself a little here. If I first mount /system before pushing anything in there, it actually works! Rooted Thanks katsuya82 and jlevy73 for the necessary hints
---------- Post added at 05:05 PM ---------- Previous post was at 04:57 PM ----------
red_trela said:
Okay, just embarassing myself a little here. If I first mount /system before pushing anything in there, it actually works! Rooted Thanks katsuya82 and jlevy73 for the necessary hints
Click to expand...
Click to collapse
Trying to make use of it (by trying to boot into recovery from rom manager) fails, though.
On the positive side, pushing the play store worked easily. Full access to the store but still no root
red_trela said:
Having any success? Tried it myself and while adb reports success, there's no su once I boot the device normally.
---------- Post added at 04:57 PM ---------- Previous post was at 04:49 PM ----------
Okay, just embarassing myself a little here. If I first mount /system before pushing anything in there, it actually works! Rooted Thanks katsuya82 and jlevy73 for the necessary hints
---------- Post added at 05:05 PM ---------- Previous post was at 04:57 PM ----------
Trying to make use of it (by trying to boot into recovery from rom manager) fails, though.
On the positive side, pushing the play store worked easily. Full access to the store but still no root
Click to expand...
Click to collapse
Good to see you made progress. I also have root but still don't have access to the play store. I was able to push the store and it's in my app folder but when I try to open it, it immediately closes.
What adb command did you use to push the play store? I think I might have set the wrong permissions with chmod.
These are the commands I used:
adb push system/app/Phonesky.apk /system/app
adb shell chmod 6755 /system/app/Phonesky.apk
---------- Post added at 09:30 PM ---------- Previous post was at 09:28 PM ----------
red_trela said:
Having any success? Tried it myself and while adb reports success, there's no su once I boot the device normally.
---------- Post added at 04:57 PM ---------- Previous post was at 04:49 PM ----------
Okay, just embarassing myself a little here. If I first mount /system before pushing anything in there, it actually works! Rooted Thanks katsuya82 and jlevy73 for the necessary hints
---------- Post added at 05:05 PM ---------- Previous post was at 04:57 PM ----------
Trying to make use of it (by trying to boot into recovery from rom manager) fails, though.
On the positive side, pushing the play store worked easily. Full access to the store but still no root
Click to expand...
Click to collapse
Good to see you made progress. I have root but don't have access to the play store. I was able to push the store and it's in my app folder but when I try to open it, it immediately closes.
What adb command did you use to push the play store? I think I might have set the wrong permissions with chmod.
These are the commands I used:
adb push system/app/Phonesky.apk /system/app
adb shell chmod 6755 /system/app/Phonesky.apk
jlevy73 said:
Good to see you made progress. I also have root but still don't have access to the play store. I was able to push the store and it's in my app folder but when I try to open it, it immediately closes.
What adb command did you use to push the play store? I think I might have set the wrong permissions with chmod.
These are the commands I used:
adb push system/app/Phonesky.apk /system/app
adb shell chmod 6755 /system/app/Phonesky.apk
---------- Post added at 09:30 PM ---------- Previous post was at 09:28 PM ----------
Good to see you made progress. I have root but don't have access to the play store. I was able to push the store and it's in my app folder but when I try to open it, it immediately closes.
What adb command did you use to push the play store? I think I might have set the wrong permissions with chmod.
These are the commands I used:
adb push system/app/Phonesky.apk /system/app
adb shell chmod 6755 /system/app/Phonesky.apk
Click to expand...
Click to collapse
And how did you get root? Ah, figure chmodding su isn't enough and I should also chmod the apk, reading what you did with Phonesky.apk Nope, still no working root
Play Store itself is only one part, you need some of the gapps stuff too. Not sure which, just installed what looked important (GoogleLoginService.apk, GoogleServicesFramework.apk and such). Didn't need to chmod anything gapps related. Oh and use the right version for Android 4.1, not 4.2
red_trela said:
And how did you get root? Ah, figure chmodding su isn't enough and I should also chmod the apk, reading what you did with Phonesky.apk Nope, still no working root
Play Store itself is only one part, you need some of the gapps stuff too. Not sure which, just installed what looked important (GoogleLoginService.apk, GoogleServicesFramework.apk and such). Didn't need to chmod anything gapps related. Oh and use the right version for Android 4.1, not 4.2
Click to expand...
Click to collapse
Really that's all I did, push su, superuser and busybox then chmod them. When I rebooted I had superuser installed and was able to install root explorer, titanium, etc.
red_trela said:
And how did you get root? Ah, figure chmodding su isn't enough and I should also chmod the apk, reading what you did with Phonesky.apk Nope, still no working root
Play Store itself is only one part, you need some of the gapps stuff too. Not sure which, just installed what looked important (GoogleLoginService.apk, GoogleServicesFramework.apk and such). Didn't need to chmod anything gapps related. Oh and use the right version for Android 4.1, not 4.2
Click to expand...
Click to collapse
Frustration, lost root and after pushing all the google apps, framework, etc still don't have access to play store. Guess I will have to wait until a real recovery is released.
jlevy73 said:
Really that's all I did, push su, superuser and busybox then chmod them. When I rebooted I had superuser installed and was able to install root explorer, titanium, etc.
Click to expand...
Click to collapse
Okay, I was just being stupid, once again: only did chmod 755 on the su binary instead of 6755. Also, the Superuser.apk (like any other apk) doesn't need more privileges than 644.
Now that I have root, I used rom manager (which is the recovery I use), to install gapps completely (did a cherry pick before). Worked perfectly. So the recovery of the DNA is fully working except something with the screen driver is messed up.
red_trela said:
Okay, I was just being stupid, once again: only did chmod 755 on the su binary instead of 6755. Also, the Superuser.apk (like any other apk) doesn't need more privileges than 644.
Now that I have root, I used rom manager (which is the recovery I use), to install gapps completely (did a cherry pick before). Worked perfectly. So the recovery of the DNA is fully working except something with the screen driver is messed up.
Click to expand...
Click to collapse
Btw, do you have the x920e? After several more hours of frustration still don't have root or gapps. Are you by chance in Beijing? :cyclops:
jlevy73 said:
Btw, do you have the x920e? After several more hours of frustration still don't have root or gapps. Are you by chance in Beijing? :cyclops:
Click to expand...
Click to collapse
Yes, I do. How did you actually manage to lose root? No, not in Beijing or Asia anymore.
Hi, Im trying to write a terminal script to batch install apk files from my sdcard
Here's the code I have
# Place apk files in Sdcard/apps/ folder
# Insert command lines in following format
# pm install "sdcard/apps/appname.apk"
pm install sdcard/apps/"Google_Maps_6_14_4.apk"
pm install sdcard/apps/"Quick Boot.apk"
However some times it gives an error " INSTALL_FAILED_INVALID_URI"
following is the o/p:
[email protected]:/ # sh sdcard/inst.sh
pkg: sdcard/apps/Google_Maps_6_14_4.apk
Failure [INSTALL_FAILED_INVALID_URI]
pkg: sdcard/apps/Quick Boot.apk
Success
I think perhaps this is due to series of commands without pause.
Any idea to get this working
Why don't you use ADB?
Sent from my Nexus 4 running Android 4.2.2
mihahn said:
Why don't you use ADB?
Sent from my Nexus 4 running Android 4.2.2
Click to expand...
Click to collapse
Perhaps due to unavailability of PC. Or wanting to batch install with just the phone
-------------------------------------------------------
You should use Titanium Backup to batch install apps of there are other options too.
However, if you rather prefer Terminal,
Try to add pause command with significant time interval after each installation command. Because next command will be rejected until the previous one is completed. I think that's the problem.
Yep, you read that right and I'm not trolling. THE ZMAX IS ROOTED!!
Discaimer and N00Bproof warning:
We have root, yes, but that doesn't mean get hasty. At the moment, there are partition images (system, boot and recovery) in my and other users' possession (free of access to all), but we don't have a working recovery at the moment and this process involves deleting the stock recovery (it will make sense later). So, if you screw up and get root-happy, there's no way to recover until we get a recovery and a custom rom, and even then you might be screwed because we don't have access to the bootloader to use fastboot. Things may change, but root-use with caution.
Also, once you root, DO NOT TAKE ETAs from T-Mo and ZTE!!!!!!! Now that we have root, we can capture the OTA and make it root-friendly. To make a long story short, the updater-script (thing that tells your recovery where and how to flash stuff) has a list of stuff it has to... well... flash. If you, for example, delete the stock ZTE Music app, and the ETA replaces the app with a new version, it's going to stop (because the script requires a REPLACEMENT and not a PLACEMENT, computers don't have the best common sense), then it will interrupt and you will likely be bricked. This shouldn't be a problem because you don't have a recovery to begin with, but I'm not taking chances here.
NOW! Let's Root. This is a long process, so don't expect to do anything for a good 10-20 minutes.
FIRST: KINGROOT
This is one of those things where your mileage may very, there have been many different ways to get KingRoot (not King"O"Root, two different apps) to work, but this one was the one that worked for me. I'll also place alternate KingRoot methods in the second post if you wanna try those. Just for the sake of knowledge, this was run on a T-Mobile ZTE ZMAX, Android 4.4.2, build 22. I don't know if it makes a difference that I factor reset my phone before doing another round of root attempts (not this one specifically, maybe a couple hours worth of attempts).
Credits to @fire3element for this method.
1) Download KingRoot APK from here (the first one with the image of the phone if you are on the desktop site).
2) Install KingRoot and run it. It will restart the phone, and it will fail (or, if you have some Android God luck, it may succeed), this is supposed to happen.
3) Clear KingRoots cache and data (in that order) and power off the phone (not reboot). Then, power it back on again.
4) Now this is where things get... well complicated for this part. You are going to need to load your RAM with a bunch of processor heavy stuff. The person that made this method used CounterSpy and Final Fantasy Type-0 in the PPSSPP v1.0.1-411 emulator, but for those of you that don't have access to that, get creative and load up. Here is what I had running (all at the same time, mind you).
Note: Force Stop Task Manager in the app settings first or it will purge to free memory automatically and this won't work.
1. Next Launcher Lite
2. Apex Launcher
3. Nova Launcher
4. Cheetah Launcher
5. CM Launcher
6. Mi Launcher
7. 25 tabs on Google Chrome (No joke)
8. Both Temple Runs
9. Fruit Ninja
10. Google Play Store
11. Google Now
12. Google Play
13. Amazon
14. Google Play Music
Mine was definitely a bit extreme but I knew all of this stuff would guarantee a good memory hogging.
5) Run all of your apps at the same time. The TL;DR for this is that apparently it's some exploit that the app uses as a buffer overflow. Now, go to settings and Force Stop KingRoot. Then Run it again. If it works, you should go from 0 to 100 real quick (no pun intended). It shouldn't progess slowly or reboot the phone to do this, but your journey does not stop here.
Click to expand...
Click to collapse
If you did it correctly, the screen from a successful root will have a green checkmark. Run RootChecker to verify root status.
SECOND: PERMA-ROOT
Now you need to permanently root the phone. This method was all @jcase, and simplified by another user. I encourage you to read JCase's original G+ post to learn something, as this guy is the master of exploits, and we are on XDA to learn.
Credits to @xtremeasure for the simplification of JCase's process.
1) Plug phone into computer...
2) Open cmd type "adb shell" (without quotes, moving forward, type all commands without quotes). This will open a terminal for the phone.
3) While in ADB Shell, type "su" to gain root shell privileges
4) Type "getprop ro.build.fingerprint"
Output for that command should be...
zte/P892T57/draconis:4.4.2/KVT49L/20140804.141306.18686:user/release-keys (the part with P892T57 may be different depending on what model ZMAX You have). If you haven't updated that number will be different, this ok, just replace the number in the next command with whatever your output is.
5) type "setprop persist.sys.k P892T57"
6) type "getprop persist.sys.k" and your output should be your build number
7) type "cd /dev/block/platform/msm_sdcc.1/by-name/" to change directories so that we can back up your recovery image (remember I said something about that?) and set the boot to our recovery partition.
8) type "dd if=recovery of=/sdcard/recovery.img" to backup the recovery image.
9) type "dd if=boot of=recovery" to set recovery as boot. Another TL;DR is that this disables the write protection set by the stock recovery, allowing you to write to the system. It will mount the /system partition upon boot.
DELETE KINGUSER NOW
10) type "reboot recovery" and restart your phone. YOU MUST RESTART WITH THIS COMMAND!!!!! It will boot straight into Android, this is good, that means you haven't screwed up anything.
11) Reopene the adb shell (using "adb shell") in your command prompt or terminal (for OSX and Linux) and type "Id". If your output is "uid=0(root) gid=0(root) context=u:r:shell:s0" then It worked...
12) Remount system as writable "mount -o rw,remount /system"
13) Manual install for supersu you can get that here: http://download.chainfire.eu/supersu
14) Type "exit" into the terminal/command and it should drop you back to your normal cmd...unzip the su zip anywhere you want in your cmd switch to that directory...
14B) I advise taking the "su" binary and "install-recovery.sh" file from the superSU folder you downloaded and putting them in the same place (on the desktop or wherever your adb.exe is if you didn't set $PATH on your computer). su can be found in the "arm" folder and install-recovery.sh can be found in the "common" folder. It is important to note that where ever your files are, you will have to type that path (if it isn't in the same directory as your adb). So, as an example, I put mine on the desktop, so I have to type "adb push ~/Desktop/su /data/local/tmp/su". If you do not know how to do that, then stop what you are doing and research it, as that's just too much to explain.
15) "adb push su /data/local/tmp/su"
16) "adb push install-recovery.sh /data/local/tmp"
17) Reenter adb shell with "adb shell"
18) Make sure system is mounted writable with "mount -o remount,rw /system"
19) Move the so files into place with these commands
"cat /data/local/tmp/su > /system/xbin/su"
"cat /data/local/tmp/su > /system/xbin/daemonsu"
"cat /data/local/tmp/install-recovery.sh > /system/etc/install-recovery.sh"
20) Give them all permissions
"chmod 755 /system/xbin/su"
"chmod 755 /system/xbin/daemonsu"
"chmod 755 /system/etc/install-recovery.sh"
21) Reboot your phone to complete install with "reboot"
22) After rebooting go into the play store and install the supersu app. It's going to tell you the su binary is out of date to fix that we need to open the adb shell on our pc again with "adb shell"
23) Reboot into recovery (you're really rebooting the system with r/w privileges) using "reboot recovery"
24) Once rebooted open the app and update your binaries one finished reboot add your done 100% perm rooted
Click to expand...
Click to collapse
Now, you are rooted! If you did everything right, you should be good. Now people are going to ask, "Is there a script for this?" The short answer is No, don't hold your breath for something immediate. There was a user that said he would be happy to make one for the second half, but the writing, testing and verification of success alone on that will take some time, as the wrong line of code can make you end up with a good old fashioned paperweight. I can verify Xposed works fine, Viper4Android works fine, and if you try to delete system apps, they will just reinstall themselves (I recommend using "System App Remover (ROOT)" on the play store, as it will actually tell you which apps are and aren't safe to install. If you have any questions, after searching of course, feel free to ask. If I can't answer, some freaking body can lol.
CREDITS:
@tech_yeet for showing us the KingRoot
@jcase for his amazing work
@xtremeasure for his method
@fire3element for his method
@the zMAX Community for staying dedicated when the going got tough, it's been a long road. Here's to custom roms and a TWRP recovery!
Please share this with others, as there is a big community of people begging for this info, let's share the love . If I forgot to credit you, let me know and I'll fix that!
ADDITIONAL INFORMATION
If you by some chance flash the TWRP Recovery Image (found in post 2), and would like to revert back to root ability (being able to write to system). Please follow the steps below:
1. cd /dev/block/platform/msm_sdcc.1/by-name
2. su
3. dd if=/sdcard/recovery.img of=recovery
4. reboot recovery
Please make sure you have the recovery in your sdcard root folder.
Alternate Root Methods and ZTE Custom ROMs/Kernels/etc
If the above first part doesn't work for you, you can find alternative root methods
Alternate Method 1 HERE
Alternate Method 2 HERE
As I see more added, I'll add them here.
CUSTOM STUFF
TWRP Image for ZTE ZMAX
Q&A/Other [UDPATED MAY 13, 2015 @ 5:45PM]
If A question is asked and you feel like it needs to be here, please tag or DM me with the Q AND THE A so that I can do so.
OTHER:
Original Discussion Thread for the ZTE ZMAX
Please see fire3element's post on what each screen in the KingRoot app means
WHAT THE SCREENS MEAN IN THE APP
That's a whole lot to swallow but I'm glad to see y'all can finally get rooted. Definitely not a method for noobs or the faint of heart but its a HUUUGE step in the right direction. Thanks to everyone responsible for this.
Hroark13 has TWRP - http://androidforums.com/threads/zte-zmax-twrp.918537/
mingolianbeef said:
Yep, you read that right and I'm not trolling. THE ZMAX IS ROOTED!!
Discaimer and N00Bproof warning:
We have root, yes, but that doesn't mean get hasty. At the moment, there are partition images (system, boot and recovery) in my and other users' possession (free of access to all), but we don't have a working recovery at the moment and this process involves deleting the stock recovery (it will make sense later). So, if you screw up and get root-happy, there's no way to recover until we get a recovery and a custom rom, and even then you might be screwed because we don't have access to the bootloader to use fastboot. Things may change, but root-use with caution.
Also, once you root, DO NOT TAKE ETAs from T-Mo and ZTE!!!!!!! Now that we have root, we can capture the OTA and make it root-friendly. To make a long story short, the updater-script (thing that tells your recovery where and how to flash stuff) has a list of stuff it has to... well... flash. If you, for example, delete the stock ZTE Music app, and the ETA replaces the app with a new version, it's going to stop (because the script requires a REPLACEMENT and not a PLACEMENT, computers don't have the best common sense), then it will interrupt and you will likely be bricked. This shouldn't be a problem because you don't have a recovery to begin with, but I'm not taking chances here.
NOW! Let's Root. This is a long process, so don't expect to do anything for a good 10-20 minutes.
FIRST: KINGROOT
This is one of those things where your mileage may very, there have been many different ways to get KingRoot (not King"O"Root, two different apps) to work, but this one was the one that worked for me. I'll also place alternate KingRoot methods in the second post if you wanna try those. Just for the sake of knowledge, this was run on a T-Mobile ZTE ZMAX, Android 4.4.2, build 22. I don't know if it makes a difference that I factor reset my phone before doing another round of root attempts (not this one specifically, maybe a couple hours worth of attempts).
Credits to @fire3element for this method.
If you did it correctly, the screen from a successful root will have a blue envelope with a checkmark. Run RootChecker to verify root status.
SECOND: PERMA-ROOT
Now you need to permanently root the phone. This method was all @jcase, and simplified by another user. I encourage you to read JCase's original G+ post to learn something, as this guy is the master of exploits, and we are on XDA to learn.
Credits to @xtremeasure for the simplification of JCase's process.
Now, you are rooted! If you did everything right, you should be good. Now people are going to ask, "Is there a script for this?" The short answer is No, don't hold your breath for something immediate. There was a user that said he would be happy to make one for the second half, but the writing, testing and verification of success alone on that will take some time, as the wrong line of code can make you end up with a good old fashioned paperweight. I can verify Xposed works fine, Viper4Android works fine, and if you try to delete system apps, they will just reinstall themselves (I recommend using "System App Remover (ROOT)" on the play store, as it will actually tell you which apps are and aren't safe to install. If you have any questions, after searching of course, feel free to ask. If I can't answer, some freaking body can lol.
CREDITS:
@tech_yeet for showing us the KingRoot
@jcase for his amazing work
@xtremeasure for his method
@fire3element for his method
@the zMAX Community for staying dedicated when the going got tough, it's been a long road. Here's to custom roms and a TWRP recovery!
Please share this with others, as there is a big community of people begging for this info, let's share the love . If I forgot to credit you, let me know and I'll fix that!
Click to expand...
Click to collapse
I have followed EVERYTHING step by step over and over again, and yet i still cant get this to work.
Basically, everything is fine up until reboot recovery.
it goes into android, but i dont start off as root, i start off as if i wasnt rooted, and i always have to do "su" to gain privledges.
afterwards, mount -o remount,rw /system/ does work but i cant write to it still for some reason.
has anyone else gotten this!? have any of you got a clue how to fix?
Here is some more info for those of you wondering what the KingRoot app is doing.
Screenshots will follow.
Text ABOVE the screenshot is for the image directly under it.
Let's begin -------------->
FIRST SCREEN WHEN YOU OPEN KINGROOT
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SECOND SCREEN
- CLICK BUTTON TO BEGIN ROOT -
ROOTING IN PROGRESS...
ROOT FAILURE
[Blue Button]: SUBMIT (submits the error report to KingRoot devs)
ROOT FAILURE
ROOT FAILURE
NO DATA CONNECTION (WiFi or cellular singnal required)
[Blue Button]: ANDROID SETTINGS MENU
SUCCESSFUL ROOT
IF YOU SEE THIS MESSAGE POP UP DURING ROOTING, JUST LEAVE IT ALONE. LET THE ROOT FINISH
SUCCESSFUL ROOT
[trash can]: [...]: [...]:
SUCCESSFUL ROOT
[Blue Button]: PURIFICATION (I believe this is similar to fixing permissions)
- CLICK IT AND LET IT RUN -
^ from clicking blue button above ^
PURIFICATION PROCESS
xIP- said:
I have followed EVERYTHING step by step over and over again, and yet i still cant get this to work.
Basically, everything is fine up until reboot recovery.
it goes into android, but i dont start off as root, i start off as if i wasnt rooted, and i always have to do "su" to gain privledges.
afterwards, mount -o remount,rw /system/ does work but i cant write to it still for some reason.
has anyone else gotten this!? have any of you got a clue how to fix?
Click to expand...
Click to collapse
Should just be mount -o remount,rw /system
No extra slash
Sent from my Z970 using XDA Free mobile app
---------- Post added at 04:40 PM ---------- Previous post was at 04:36 PM ----------
I would the recovery image restore commands added.. If people feel the need to recover and try again they should run these
cd /dev/block/platform/msm_sdcc.1/by-name
su
dd if=/sdcard/recovery.img of=recovery
reboot recovery
*edited to remove a potentially harmful commands per jcase's advice*
Sent from my Z970 using XDA Free mobile app
xtremeasure said:
Should just be mount -o remount,rw /system
No extra slash
Sent from my Z970 using XDA Free mobile app
---------- Post added at 04:40 PM ---------- Previous post was at 04:36 PM ----------
I would the recovery image restore commands added.. If people feel the need to recover and try again they should run these
cd /dev/block/platform/msm_sdcc.1/by-name
su
dd if=boot of=boot
dd if=/sdcard/recovery.img of=recovery
reboot recovery
Sent from my Z970 using XDA Free mobile app
Click to expand...
Click to collapse
even with just one slash I still have a problem
Sent from my Z970 using XDA Free mobile app
Ok, so I am about to flash back the stock recovery from my backup and see if I can go through all these steps again to figure out what is going wrong.
I have a theory as to where and why KingUser is locking down SU in xbin. After I restore stock recovery, I will then Factory Reset and attempt to log my progress.
Stay tuned and I will try to report back later today. Hopefully with more insight on this problem.
@xIP-
Are you talking about pushing "su" , "daemonsu" , and "install-recovery.sh" files to /system ?
Keeps saying permission denied?
If that is the case, you can not. KingUser has a lock on system and is already in place as SU in /system/xbin
You will most likely need to factory reset and try again.
---------- Post added at 12:57 PM ---------- Previous post was at 12:37 PM ----------
UPDATE UPDATE!!!
Do not run the dd if=boot of=boot command
Could brick your device. As per Jcase warning. Wait for more info
fire3element said:
Ok, so I am about to flash back the stock recovery from my backup and see if I can go through all these steps again to figure out what is going wrong.
I have a theory as to where and why KingUser is locking down SU in xbin. After I restore stock recovery, I will then Factory Reset and attempt to log my progress.
Stay tuned and I will try to report back later today. Hopefully with more insight on this problem.
@xIP-
Are you talking about pushing "su" , "daemonsu" , and "install-recovery.sh" files to /system ?
Keeps saying permission denied?
If that is the case, you can not. KingUser has a lock on system and is already in place as SU in /system/xbin
You will most likely need to factory reset and try again.
---------- Post added at 12:57 PM ---------- Previous post was at 12:37 PM ----------
UPDATE UPDATE!!!
Do not run the dd if=boot of=boot command
Could brick your device. As per Jcase warning. Wait for more info
Click to expand...
Click to collapse
Remember remove kinguser after you run the dd commands but before you reboot recovery...
Sent from my Z970 using XDA Free mobile app
xtremeasure said:
Remember remove kinguser after you run the dd commands but before you reboot recovery...
Click to expand...
Click to collapse
Just so this is clear... full Root uninstall through the KingUser app, or just uninstall it through android app settings menu.
^ In case someone else has the same question ^
fire3element said:
Just so this is clear... full Root uninstall through the KingUser app, or just uninstall it through android app settings menu.
^ In case someone else has the same question ^
Click to expand...
Click to collapse
I would do a full root uninstall....
The backdoor keeps root for adb so installing the new su shouldn't be an issue
Sent from my Z970 using XDA Free mobile app
Got it. Will report back after this headache is done. *slams head on desk*
I just read the boot flash advice, I am not going to do it because I know that's a stupid idea, but if it does in fact let us flash boot.IMG, omg overclocking, custom kernels, full read write, awesome recovery, dual boot custom Roms with custom kernels here we come.
Unlocked boot.IMG
Can you Ya hoooouoo
And subscribed.
Sent from my Z970
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
fire3element said:
Ok, so I am about to flash back the stock recovery from my backup and see if I can go through all these steps again to figure out what is going wrong.
I have a theory as to where and why KingUser is locking down SU in xbin. After I restore stock recovery, I will then Factory Reset and attempt to log my progress.
Stay tuned and I will try to report back later today. Hopefully with more insight on this problem.
@xIP-
Are you talking about pushing "su" , "daemonsu" , and "install-recovery.sh" files to /system ?
Keeps saying permission denied?
If that is the case, you can not. KingUser has a lock on system and is already in place as SU in /system/xbin
You will most likely need to factory reset and try again.
---------- Post added at 12:57 PM ---------- Previous post was at 12:37 PM ----------
UPDATE UPDATE!!!
Do not run the dd if=boot of=boot command
Could brick your device. As per Jcase warning. Wait for more info
Click to expand...
Click to collapse
Is there anyway to do it without a factory reset? Could I just remove kinguser? or it must be factory reset? and will I have to reroot with factory reset?
Sent from my Z970 using XDA Free mobile app
Sorry guys, kinda been running around all day, have a lot of catching up to do I see. I'll fix the thread with updated information that people have so generously contributed!
DroidisLINUX said:
I just read the boot flash advice, I am not going to do it because I know that's a stupid idea, but if it does in fact let us flash boot.IMG, omg overclocking, custom kernels, full read write, awesome recovery, dual boot custom Roms with custom kernels here we come.
Unlocked boot.IMG
Can you Ya hoooouoo
And subscribed.
Sent from my Z970
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
Click to expand...
Click to collapse
I know right!!! First hurdle... done... second hurdle, bootloader with no fastboot lmao...
a bit unclear on this
are we actually rebooting into recovery or its supposed to go straight back into the phone
i was never able to get into recovery
10) type "reboot recovery" and restart your phone. YOU MUST RESTART WITH THIS COMMAND!!!!! It will boot straight into Android, this is good, that means you haven't screwed up anything.
"cat /data/local/tmp/su > /system/xbin/su"
"cat /data/local/tmp/install-recovery.sh > /system/etc/install-recovery.sh"
getting permission denied when running this.
"chmod 755 /system/xbin/su"
"chmod 755 /system/etc/install-recovery.sh"
as well as operation denied or something along those lines. any help would be nice. also and running id on adb. its showing.
uid=0(root) gid=0(root) context=u:r:init:s0
rather than
uid=0(root) gid=0(root) context=u:r:shell:s0
xIP- said:
I have followed EVERYTHING step by step over and over again, and yet i still cant get this to work.
Basically, everything is fine up until reboot recovery.
it goes into android, but i dont start off as root, i start off as if i wasnt rooted, and i always have to do "su" to gain privledges.
afterwards, mount -o remount,rw /system/ does work but i cant write to it still for some reason.
has anyone else gotten this!? have any of you got a clue how to fix?
Click to expand...
Click to collapse
You have to exit adb shell to push files to /data/local/tmp, which does not require root. That was a major exploit in earlier android versions, as people would push scripts to /data/local/tmp without root, run the exploit in the directory, and it would root. That was patched of course, but that directory can be accessed without root. Once you use "reboot recovery" to reboot, then just plug your phone back up and type "adb shell" to which the phone should respond with a "#" instead of a "$". If you have the $, you are not root and need to go back. If you do, just be patient with it and make sure you are not just copying and pasting (I know this can be the root of the issue at times with command, just type it out). It should work, the second half is the easy part lol.