My success in rooting 8.5.1 - 8.9" Kindle Fire HD Q&A, Help & Troubleshooting

I thought I'd let folks know what I did in order to root on 8.5.1 and not have slowness. This isn't a complete walkthrough and assumes you have ADB drivers installed and working and access to ADB.
First I used the exploit found in this thread.
http://forum.xda-developers.com/showthread.php?t=2544736
I downloaded kindlehd2013_root.zip and also got the zip copy of superuser from
http://download.clockworkmod.com/superuser/superuser.zip
I extracted all to a folder. I then replaced the su from the kindlehd2013_root.zip with the superuser.zip armeabi folder version. Then you run the commands it has in the post.
adb push su /data/local/tmp/
adb push rootme.sh /data/local/tmp/
adb push exploit /data/local/tmp/
adb shell chmod 755 /data/local/tmp/rootme.sh
adb shell chmod 755 /data/local/tmp/exploit
Before I ran this last line I made sure su had the correct permissions:
type adb shell:
then ran the command
chmod 6755 /data/local/tmp/su
adb shell /data/local/tmp/exploit -c "/data/local/tmp/rootme.sh"
now you can get root via ADB by going into
adb shell
then run the command su
from there I made sure the su had the correct permissions again in the new location:
mount -o remount,rw /system
I had a complaint about space so I just removed the officesuite.apk in /system/apps to the sdcard
chown 0:0 /system/xbin/su
chmod 6755 /system/xbin/su
Then using the superuser.apk from the zip installed it.
adb install superuser.apk
Hope this helps others have success. From here you can follow the tutorials to get Google apps and such. I'd love to run an alternative ROM but have the LTE version and haven't been able to find one that has working LTE.

Hi Macman005!!
I want to use your method to root my Hd 8.9, I dont want too install a room, only install google services to use my chromecast. But before I want to Know:
How I move the officesuite.apk in /system/apps to the sdcard, if I have the space complaint you had?
I really appreciate any help you can provide

jaramosparra said:
Hi Macman005!!
I want to use your method to root my Hd 8.9, I dont want too install a room, only install google services to use my chromecast. But before I want to Know:
How I move the officesuite.apk in /system/apps to the sdcard, if I have the space complaint you had?
I really appreciate any help you can provide
Click to expand...
Click to collapse
On device you can use es file explorer -> enable root explorer from the left side the click on root explorer -> mount r/w -> then make sure /system is rw
Via ADB
adb pull /system/app/OfficeSuite.apk
adb shell
su for root
mount -o remount,rw /system
rm /system/app/OfficeSuite.apk

Hi Macman005
I had follow your instructions and I had manage to root my hd 8.9, total success!!!
Thanks!!

hi there folks,
so i've read through a bunch of guides and steps to accompish getting root on a kindle fire hd 8.9 running 8.5.1
i followed your above steps to the T but everytime i try and execute the exploit i get a error like this
***********
Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x80008000 form iomem
Attempt put_user exploit...
write: No space left on device
************
i read further into this post and in others that moving files around was the answer but i'm unable to move the files using
Code:
./adb shell
mv /system/OfficeSuite.apk /sdcard
i get a error like "failed cross device link"
so i'm guessing i'll only have access after rooting to move or delete files in /system
************
Code:
$ df
Filesystem Size Used Free Blksize
/dev 383M 32K 383M 4096
/mnt/asec 383M 0K 383M 4096
/mnt/obb 383M 0K 383M 4096
/system 872M 872M 0K 4096
/data 13G 372M 12G 4096
/cache 639M 10M 628M 4096
/efs 15M 4M 11M 4096
/mnt/sdcard 13G 372M 12G 4096
[email protected]:/system/app $
*********
any suggestions tips or links would be appreciated

Use adb pull to get the file out of /system/app then just try to delete it. I'm guessing it won't work though without root.
Did you check to see if su was in the /system/xbin/su dir?

macman005 said:
Use adb pull to get the file out of /system/app then just try to delete it. I'm guessing it won't work though without root.
Did you check to see if su was in the /system/xbin/su dir?
Click to expand...
Click to collapse
already tried rm -rf OfficeSuit.apk
pulling it leaves the file inplace
su is in place in xbin
Code:
[email protected]:/ $ cd /system/xbin/
[email protected]:/system/xbin $ ll
-rwxr-xr-x root shell 59392 2008-08-01 12:00 dexdump
-rwxr-xr-x root shell 63448 2008-08-01 12:00 hciconfig
-rwxr-xr-x root shell 36776 2008-08-01 12:00 hcitool
-rwxr-xr-x root shell 5608 2008-08-01 12:00 hdcp-test
-rwsr-sr-x root root 94208 2014-11-19 22:25 su
127|[email protected]:/sdcard $ su --help
Segmentation fault
139|[email protected]:/sdcard $ su touch test
Segmentation fault
139|[email protected]:/sdcard $ su
Segmentation fault
139|[email protected]:/sdcard $
i've tried tinkering with permissions with no luck
i'm not worried about root on the kindle os, i mostly want to stick CM11 on it - i recall reading a article on cyanogenmod's page about flashing the CM11 rom on the kindle it didn't mention that root was required i just kind of assumed it was to be able to install a second bootloader etc

If you don't need to follow my root you just use this tutorial. The root being slow isn't a big deal since you'll replace it with cm11
http://forum.xda-developers.com/showthread.php?t=2789289

macman005 said:
If you don't need to follow my root you just use this tutorial. The root being slow isn't a big deal since you'll replace it with cm11
http://forum.xda-developers.com/showthread.php?t=2789289
Click to expand...
Click to collapse
sweet thanks for the tip - i'll give this one a try (i'd tried a couple other methods with no success)

Everything good for me until:
adb shell /data/local/tmp/exploit -c "/data/local/tmp/rootme.sh"
Then I get:
Code:
Device detected: KFJWI (IMM76D)
Attempt acdb exploit...
KFJWI (IMM76D) is not supported.
Attempt fj_hdcp exploit...
Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x80008000 form iomem
Attempt put_user exploit...
After that nothing works. Any ideas where i might have taken the wrong turn?

Do you have su in the /system/xbin folder?

macman005 said:
Do you have su in the /system/xbin folder?
Click to expand...
Click to collapse
Thanks for reply macman.
I gave up... Followed the instructions you gave and all seemed well until step: adb shell /data/local/tmp/exploit -c "/data/local/tmp/rootme.sh"
So not sure but will check when I can try again. Would love to totally clean out amazon junk and turn into android pad.

Im having the same problem as Justanumber, and I'm not sure if I have the su in the /system/xbin folder

I was able to root 8.5.1. What I did was try the Bin4ry method, first option 1, when that didn't work option 2. It made my kindle run slow and was almost unusable. Being very patient due to the slowness, I tried the QEMU method. It seems like some things transferred to the kindle and others didn't and I got an error. I then went back to Bin4ry and ran unroot and got an error. The last thing I tried was to run root option 2 once more and success. I then went right to Hashcodes post and installed a second bootloader and cm11. I'm not a developer so I put everything I did. Maybe someone who knows what they are doing can figure out what is needed from all that. Whatever I did though, I got for on 8.5.1 without any issues once it went through
Sent from my HTC6525LVW using XDA Premium 4 mobile app

worked perfectly for me on 8.5.1, always a bit nervous messing with the kindle but no problems . Big thanks to the op. I didn't have any complaints about space, and there was none of the slowdown problems so many people complain about after rooting the new firmware. Now i have installed hashcode's cm12 port and its like a brand new gadget...

I got as far as "adb shell", but the su command returns "permission denied"
What exactly do you mean when you say "check su permissions." First time using ADB.

please help me
macman005 said:
I thought I'd let folks know what I did in order to root on 8.5.1 and not have slowness. This isn't a complete walkthrough and assumes you have ADB drivers installed and working and access to ADB.
First I used the exploit found in this thread.
http://forum.xda-developers.com/showthread.php?t=2544736
I downloaded kindlehd2013_root.zip and also got the zip copy of superuser from
http://download.clockworkmod.com/superuser/superuser.zip
I extracted all to a folder. I then replaced the su from the kindlehd2013_root.zip with the superuser.zip armeabi folder version. Then you run the commands it has in the post.
adb push su /data/local/tmp/
adb push rootme.sh /data/local/tmp/
adb push exploit /data/local/tmp/
adb shell chmod 755 /data/local/tmp/rootme.sh
adb shell chmod 755 /data/local/tmp/exploit
Before I ran this last line I made sure su had the correct permissions:
type adb shell:
then ran the command
chmod 6755 /data/local/tmp/su
adb shell /data/local/tmp/exploit -c "/data/local/tmp/rootme.sh"
now you can get root via ADB by going into
adb shell
then run the command su
from there I made sure the su had the correct permissions again in the new location:
mount -o remount,rw /system
I had a complaint about space so I just removed the officesuite.apk in /system/apps to the sdcard
chown 0:0 /system/xbin/su
chmod 6755 /system/xbin/su
Then using the superuser.apk from the zip installed it.
adb install superuser.apk
Hope this helps others have success. From here you can follow the tutorials to get Google apps and such. I'd love to run an alternative ROM but have the LTE version and haven't been able to find one that has working LTE.
Click to expand...
Click to collapse
Please help sir can you do a video of it on how to root the version 8.5.1 cause I cnt follow hard instruction pls lemme see

macman005 said:
Do you have su in the /system/xbin folder?
Click to expand...
Click to collapse
Could you specify a little on how to find this out?
I'm also getting stuck after:
adb shell /data/local/tmp/exploit -c "/data/local/tmp/rootme.sh"
"Attempt acdb explot...
KFJWI <IMM76D> is not supported.
Attempt fj_hdcp exploit...
Attempt msm-cameraconfic exploit...
Detected kernel physical address at 0x80008000 from iomem
Attempt put_user exploit...
Thanks

macman005 said:
I thought I'd let folks know what I did in order to root on 8.5.1 and not have slowness. This isn't a complete walkthrough and assumes you have ADB drivers installed and working and access to ADB.
First I used the exploit found in this thread.
http://forum.xda-developers.com/showthread.php?t=2544736
I downloaded kindlehd2013_root.zip and also got the zip copy of superuser from
http://download.clockworkmod.com/superuser/superuser.zip
I extracted all to a folder. I then replaced the su from the kindlehd2013_root.zip with the superuser.zip armeabi folder version. Then you run the commands it has in the post.
adb push su /data/local/tmp/
adb push rootme.sh /data/local/tmp/
adb push exploit /data/local/tmp/
adb shell chmod 755 /data/local/tmp/rootme.sh
adb shell chmod 755 /data/local/tmp/exploit
Before I ran this last line I made sure su had the correct permissions:
type adb shell:
then ran the command
chmod 6755 /data/local/tmp/su
adb shell /data/local/tmp/exploit -c "/data/local/tmp/rootme.sh"
now you can get root via ADB by going into
adb shell
then run the command su
from there I made sure the su had the correct permissions again in the new location:
mount -o remount,rw /system
I had a complaint about space so I just removed the officesuite.apk in /system/apps to the sdcard
chown 0:0 /system/xbin/su
chmod 6755 /system/xbin/su
Then using the superuser.apk from the zip installed it.
adb install superuser.apk
Hope this helps others have success. From here you can follow the tutorials to get Google apps and such. I'd love to run an alternative ROM but have the LTE version and haven't been able to find one that has working LTE.
Click to expand...
Click to collapse
I'm pretty proficient with ADB, so your steps were easy to follow. Now I have a rooted Kindle Fire HD 8.9 on 8.5.1.
Thank you

Hello,
I'm following these instructions. When I run su, i get "Permission Denied."
Any ideas? The steps before seem to run fine.
When i run the exploit, i see the follwing:
Device detected: KFJWI (IMM76D)
Attempt acdb exploit...
KFJWI (IMM76D) is not supported.
Attempt fj_hdcp exploit...
Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x80008000 form iomem
Attempt put_user exploit...
---------- Post added at 04:27 PM ---------- Previous post was at 03:48 PM ----------
I got it to work.
I enterd adb shell, then exploit again, without the rootme.sh argument.
Then su worked and I was able to get everything to run
Thanks for the instructions!

Related

[Q] Simple Root for EB13

Is there a simple, non-CWM flashing one-click root for stock EB13 Epics (I just want to tether to my rooted nook)?
I ask because a few months back I rooted my DI18 Epic with a "One Click Root" and, for some reason, all my apps became unlinked from the android market, and nothing I did worked to restore their connections. After a few hours of panic, I unrooted using the accompanying "One Click Unrooter," and the problem went away.
Then, I noticed my bluetooth was't working. I took it to the Sprint store, they ordered me a replacement phone, and then wouldn't exchange it because CWM was on my current phone. I got them to exchange it eventually, but I felt like a complete dumbass for not knowing it didn't come off in the one-click-unrooting process.
So, is there a way to just get root? And then is there a simple way to get rid of it (uninstall SU and such as well) in case I have to exchange the hardware?
I've read a lot of stuff about flashing stock with Odin, but all the dl links for Odin are 404'd, and I'd rather not have to go back to fresh stock every time I need to take my phone in. What's your advice?
SuperOneClick v1.7 worked for me.
Trickee360 said:
Is there a simple, non-CWM flashing one-click root for stock EB13 Epics (I just want to tether to my rooted nook)?
Click to expand...
Click to collapse
I don't know about "one-click", z4root might work, but there's anecdotal reports of it not working on Android 2.2.1. The one-click w/CWM redirector is the easiest way to root and definitely recommended if you want to do anything more advanced (ROMs, etc.). You can always return to stock everything with Odin.
That said, if all you want is root and nothing more, the manual version is relatively simple. It's really just three steps:
Use an exploit (rageagainstthecage-arm5.bin) to get "temporary root" (an ADB root shell).
Install Superuser's su binary to /system/xbin with the appropriate permissions (root.shell 4755).
Sideload Superuser.apk as a regular program, or download it from the market.
In which case "unrooting" is trivial. Just delete /system/xbin/su with root-explorer or something, and after remove Superuser via "Manage applications".
A while back I wrote up semi-detailed directions for doing this. They should work on EB13 with some modification. Here's some notes for EB13:
"rageagainstthecage-arm5.bin", "su", and "Superuser.apk" are all included in the one click package, that's the easiest place to get them.
Actually running "rageagainstthecage-arm5.bin" is the trickest part. There's a few ways to do it, and due to the nature of the exploit, sometimes only one or two of them will work for anyone. You can tell it works if on the next run of "adb shell" you get a "#" prompt instead of "$". Try these three ways in order until one of them works:
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp
adb shell chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
adb shell /data/local/tmp/rageagainstthecage-arm5.bin
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp
adb shell chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
adb shell (press return, and type below at the "$" prompt):
/data/local/tmp/rageagainstthecage-arm5.bin
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp
adb push root.sh /data/local/tmp
adb shell chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
adb shell chmod 755 /data/local/tmp/root.sh
adb shell /data/local/tmp/root.sh
With the last method's root.sh from the one-click package.
Once you have root, and have verified such by getting a "#" prompt with "adb shell", then run:
Code:
adb shell rm /data/local/tmp/rageagainstthecage-arm5.bin
adb shell rm /data/local/tmp/root.sh
adb shell mount -wo remount /dev/block/stl9 /system
adb push su /system/xbin
adb shell chmod 4755 /system/xbin/su
adb shell mount -ro remount /dev/block/stl9 /system
adb install Superuser.apk
If you do nothing more, OTA updates should apply just fine. The only caveat is that /system/xbin/su will lose the appropraite permissions, so Superuser will no longer work. To restore it, do the same steps above to regain "temporary root", then run:
Code:
adb shell rm /data/local/tmp/rageagainstthecage-arm5.bin
adb shell rm /data/local/tmp/root.sh
adb shell mount -wo remount /dev/block/stl9 /system
adb shell chmod 4755 /system/xbin/su
adb shell mount -ro remount /dev/block/stl9 /system
You shouldn't have to push a new "su" binary since it's already there, and similarly, you don't need to reinstall Superuser.

How to root manually/without Windows

There is already an excellent write-up on how to use SuperOneClick to root your Optimus V.
Unfortunately, you may not have a Windows machine available to run the util, or your PC hates the LG drivers, or you may wish to control how you go about rooting your device.
Hence this short write-up which, obviously, relies on pieces I got from that other write-up.
I. Rooting your device
1. You still need ADB!
2. Download the LG Optimus V Tools package from http://nexus.zteo.com/projects/tools/
3. Unzip it
4. Command-line:
Code:
adb push psneuter /data/local/tmp/
adb push su /data/local/tmp/
adb shell
cd /data/local/tmp
chmod 777 psneuter
chmod 777 su
./psneuter
5. You should be kicked out of the shell
6. Command-line:
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
cat /data/local/tmp/su > /system/bin/su
mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
(Oh look you are root!)
That's it. You now have permanent root access.
After rebooting your phone, adb should be back to logging you in as a regular user but typing "su" will do the trick.
Note: I realize that the version of SuperUser.apk that comes with SuperOneClick might be re-usable here. I haven't had any success with it but you may.
II. Flashing a new ROM
1. After rooting your device, obviously...
2. Get an image for the ROM you wish to flash...
Currently, my favourite one is a fairly recent version of Zefie's CM7.
You can find it by googling "update-cm-7-04282011-NIGHTLY-thunderc-Xionia-signed.zip" -- I will refer to it, below, as <your_rom_zip_file>
3. Get a minimum Google Apps package for flashing as well.
Here, I would google "gapps-gb-20110325-signed.zip" -- I will refer to it, below, as <your_gapps_zip_file>
3. Command-line:
Code:
adb push flash_recovery /data/local/tmp/
adb push recovery.img /sdcard/
adb push Debug-FormatSYSTEM.zip /sdcard/
adb push <your_rom_zip_file> /sdcard/
adb push <your_gapps_zip_file> /sdcard/
adb shell
su
chmod 777 /data/local/tmp/flash_recovery
/data/local/tmp/flash_recovery /sdcard/recovery.img
reboot recovery
4. In recovery: Flash Debug-FormatSYSTEM.zip
5. In recovery: Wipe cache and dalvik-cache
6. In recovery: Flash <your_rom_zip_file> -- this will take a while
7. Do not reboot!
8. In recovery: Flash <your_gapps_zip_file>
9. Now, reboot.
10. Let your phone think about life for a few minutes
11. Select "Skip" when your phone asks you to create/enter your account info
12. Launch the market; now, enter your main account information
Hey first of all let me tell you that I appreciate this guide. Now my problem is that I am such a noob that I may be doing this wrong.I download the file to my optimus.Then in an explorer I extract it, correct? After that once I put in the first line of command on terminal emulator I get an error that says "adb: permission denied". Please help this guide is my last resort.Whatever I do I can not root through windows.It would be nice if you could explain in more detail every step. Thanks!
help
can u please add a little more detail thank u very much appreciated.
SouthParkFan15:
adb is a tool that you run on your computer; it is available for Windows, Mac OS X and Linux. It is part of the Google SDK.
thizizjohnny:
Could you give me a little more detail regarding what detail you are interested in?
How do I unzip?.. is extract the same thing? I'm running Linux mint 10. How do I get adb? Excuse my noobness.
Sent from my VM670 using XDA App
Oh and one last thing.. does this work on android version 2.2.1?
Sent from my VM670 using XDA App
Yes this works with 2.2.1.
On Linux Mint, you can use the package manager or the unzip command in a terminal window.
apk:
Download the SDK at http://developer.android.com/sdk/index.html
Install it, then run "android" and select "Install platform tools"
I finally got adb on my system, but when I type in "adb devices" nothing comes up and when I do any command that involves the phone i get "error:device not found".Yes I have usb debugging on and yes I have all the right drivers installed and yes I have tried rebooting a million times, and no my computer has never recognized my phone the way it should.Let me also point out that though pdanet or droid explorer they can't find my device. Help please I'm desperate!
Oh, my. Sorry to read that.
Problem is, in 2.2.x, the exploits that give you root access rely on ADB itself so you couldn't be more out of luck.
On second thought...this may seem a bit weird but there may be a way. I have to think about it. It would involve using a file manager that agrees to "see" /data/local/tmp, running psneuter from there and keeping our fingers crossed. I'll keep you updated.
Alright thanks cyansmoke! Keep me informed.
I ran all of the steps for rooting and I didn't get one error. It didn't seem to work though. When I launch adb again after rebooting my phone I get permission denied when I try to run su.
Here is the cap from my command line. I have no idea why it didn't take.
C:\phone\LGOptimusVTools>adb shell
$ cd /data/local/tmp
cd /data/local/tmp
$ chmod 777 psneuter
chmod 777 psneuter
$ chmod 777 su
chmod 777 su
$ ./psneuter
./psneuter
property service neutered.
killing adbd. (should restart in a second or two)
C:\phone\LGOptimusVTools>adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# cat /data/local/tmp/su > /system/bin/su
cat /data/local/tmp/su > /system/bin/su
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
# exit
exit
C:\phone\LGOptimusVTools>adb shell
$ su
su
su: permission denied
$
It's possible that you have another su in your path that takes precedence.
Please try typing:
/system/bin/su
Hey, do you know if there is a way to upgrade my device to froyo 2.2.2? It's currently 2.2.1 and whenever I go to update system it says something like "Your system is up to date".Incase you have forgotten I have the optimus v that can't establish connections with the computer.So what I could do?I'm thinking that If I do that then maybe it could fix all of my problems (or some of them).Thanks
I don't think that it will help you no.
OK it's taking longer than I thought because my wife's LGV, after I restored it to stock, decided that it would not allow psneuter anymore.
Thus, I will need you to run these commands for me and let me know how that went:
1. First, copy psneuter to the root of your SD Card.
2. Then, download Terminal Emulator from the market
3. Run Terminal Emulator, type:
Code:
cp /sdcard/psneuter /data/local/tmp/
chmod 777 /data/local/tmp/psneuter
/data/local/tmp/psneuter
Now, if we are lucky, you should get kicked out of the terminal app (I know it's weird but there is a claim that it goes through adb(!))
Restart the terminal emulator. If we are double-lucky, your prompt should have changed from '$' to '#'
Fingers crossed. Still surprised to hear that terminal emulator would go through adb. No, let me rephrase that: I am moderately surprised, in fact, considering the limitations put on non-rooted apps.
After I put psneuter on the root of my sdcard.I go to terminal emulator and put in the first code and it says "cp: permission denied".Any suggestions?
SouthParkFan15 said:
After I put psneuter on the root of my sdcard.I go to terminal emulator and put in the first code and it says "cp: permission denied".Any suggestions?
Click to expand...
Click to collapse
Ah, my bad, no "cp" by default.
New instructions:
Code:
cat /sdcard/psneuter > /data/local/tmp/
chmod 777 /data/local/tmp/psneuter
/data/local/tmp/psneuter
After I put in the first code I get an error message saying "cannot create /data/local/tmp/: is a directory".
*facepalm*
Of course I should have written:
Code:
cat /sdcard/psneuter > /data/local/tmp/psneuter
I put in "cat /sdcard/psneuter > /data/local/tmp/psneuter" and I get an error message saying "cannot create /data/local/tmp/psneuter: directory nonexistent".
Any suggestions?

Manual Root - UPDATED: Temp Root?

Yes, I do understand that zergRush is for Gingerbread, but I've read so many threads on user SOC, and multiple versions of it at that, to gain root. From past experiences rooting phones (LG Optimus V, Samsung Intercept, HTC Vivid) I understand ADB, and how things work, but this phone really has me stumped.
So I've tried everything under the sun, multiple different SOC versions (you name it, i've tried it), TPSparkyRoot, among others. Nothing will root this phone, even used the unbricking guide after finding out that V10F(or J, can't remember) is unrootable. So now I'm not V18F, which from what everyone is saying is very rootable. Some say SOC 2.3.3 will root on first try, well not for me.
For some reason SOC was always stopping at Step #7, no matter what version I am on. Reading the log I would always see it stop and freeze up at a step that looked like it was trying to mount something, or remount something. I would try Shell Root and it would just give me the Gingerbreak error when it tried to run the zergRush exploit.
Now I even got my hands dirty and installed the SDK, ran ADB and tried to manually run the zergRush exploit, I knew it probably was going to spit out the same feedback as SOC did but it was worth a shot.
Now I'm really stuck, should I reflash the V10 firmware to try and manually zergRush the phone? Is there really a working method out there, I mean there has to be cause people have been rooting these phones.
Just to make everyone aware, when I flashed the V18F firmware it was a ROM (HO!NO!) that was suppose to already have been rooted (the download to the rom was in one of the unbricking guides I found). The only problem was once I install V18F there was no root, no Superuser app, nothing.
So I'm going to once again, ask the nice people here at the Nitro XDA Community to lend me some advice.
===========================
UPDATE:
Ok, so upon more reading, and gutting out codes and methods from devs everywhere (credit will be made later) I got temp root, although any application that I used to check for root always took forever, let me explain.
I ran these commands manually, as found in TPSparkyRoot
Code:
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot
I then waited until the phone booted back up completely and ran
Code:
adb shell rm /data/local.prop > nul
adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
adb reboot
I then waited for another full reboot. Now here is the weird thing, I can run "adb shell" and am automatically greeted with # instead of $. So I'm temp rooted right? I don't know what this script exactly is doing, the code looks to complex for my feeble mind to understand.
So now that I have root, I started pushing the required files into directories I couldn't access before.
Code:
adb remount
adb push su /system/bin/su
adb shell chown 0.0 /system/bin/su
adb shell chmod 06755 /system/bin/su
adb push busybox /system/bin/busybox
adb shell chown 0.0 /system/bin/busybox
adb shell chmod 0755 /system/bin/busybox
adb push Superuser.apk /system/app/Superuser.apk
adb shell chown 0.0 /system/app/Superuser.apk
adb shell chmod 0644 /system/app/Superuser.apk
Now I'm not sure but after step 2/3 in the TPSparkyRoot it would feed me errors on writting those files, manually entered though it worked, for some reason I think that the script was not executing a remount, because manually they worked fine.
So I seem to have temp root, restarting the phone will set the shell back to $. Google Play will offer an update for SuperUser and update correctly, but it never shows in my app drawer, and other apps seem to act funny when trying anything with root. Any ideas?

Rooting the Ampe A10 Dual core 3G

Rooting The Ampe A10 Dual core 3g ICS
1.
Download and install the drivers required to connect the tablet to a windows pc (I used Win7) not any old ADB drivers will do the first ones I came across didn’t work so I recommend downloading from here - http://www.topnotchtablets.com/installADBdriver (PDA Net for Android)
2.
Download the rooting program from this thread here
http://forum.xda-developers.com/showthread.php?t=1886460
Bin4ry…zip direct link - http://ul.to/h44f6vni
3.
Extract the contents of the zip folder into a directory on the pc
Rooting is done at your own risk!
4.
Plug the tablet into the pc and run the RunMe.bat file
Screen will pop up select option 1 Normal
follow the instructions on the screen, it will refer to the tablet and you need to select restore. Once updated a reboot will happen and root should be done, if you wish to check root download root checker from the android market
enjoy
you mite like Webkey for example to remotely use the Android
Thanks, I've already rooted the same device as Sanei N10 3G (MSM8625 CPU).
But do you know something about a recovery mod that works with this tablet?
recovery
Hello, I also Sanei N10. found recovery and third-party firmware if found give the link
murkin82 said:
Hello, I also Sanei N10. found recovery and third-party firmware if found give the link
Click to expand...
Click to collapse
Be careful, we're talking about the 3G version with Qualcomm Snapdragon CPU.
If you have anything but root, pls post it.
I have no Ampe A10/Sanei N10 Dual core 3G. recovery or firmware met?!
snapon said:
Rooting The Ampe A10 Dual core 3g ICS
2.
Download the rooting program from this thread here
http://forum.xda-developers.com/showthread.php?t=1886460
Bin4ry…zip direct link - http://ul.to/h44f6vni
Click to expand...
Click to collapse
First of all, thank you for your help!
Could you please upload this file on a site where one can really download it and isnʼt directed elsewhere to register for a paid package?
There are many good file sharing sites, even Googleʼs Drive.
murkin82 said:
Hello, I also Sanei N10. found recovery and third-party firmware if found give the link
Click to expand...
Click to collapse
The Ampe 10 seems to have its own recovery built in and can be started by turning the device off turn it back on hold both volume up and power. From this menu you can recover / update from the SD card. I found the original firmware here 86pp.com/download_view.asp and have installed this one you need to extract msm7627a_fw8937-ota-eng_mmc.zip from the downloaded zip copy it to the SD
I think the firmware can also be found here: szampe.com/support_down.asp? but as its all in Chinese its difficult to tell
Mazarin07 said:
First of all, thank you for your help!
Could you please upload this file on a site where one can really download it and isnʼt directed elsewhere to register for a paid package?
There are many good file sharing sites, even Googleʼs Drive.
Click to expand...
Click to collapse
Its not mine to re-distribute and you can download from that fileshare site without registering or paying you just use the 'Free' option and wait a little longer
thanks
thanks worked for me
murkin82 said:
Hello, I also Sanei N10. found recovery and third-party firmware if found give the link
Click to expand...
Click to collapse
Try this site slatedroid.com/blog/85/entry-96-aokp-cm9-cm10-installation-guide-for-ampe-a10-sanei-n10/
Thanks in advance!
W3sti said:
Thanks, I've already rooted the same device as Sanei N10 3G (MSM8625 CPU).
But do you know something about a recovery mod that works with this tablet?
Click to expand...
Click to collapse
Did you mean you rooted Sanei N 10 with dual core Qualcomm MSM8625? Could you please tell which method you followed, or how you managed to do it.
And also, will I ever be able to install Jelly bean on this particular tablet?
Thanks in advance!
Mt Everest said:
Did you mean you rooted Sanei N 10 with dual core Qualcomm MSM8625? Could you please tell which method you followed, or how you managed to do it.
And also, will I ever be able to install Jelly bean on this particular tablet?
Thanks in advance!
Click to expand...
Click to collapse
Try Tasselhofs rootscript at mediafire.com/?2jt4ft8xpfzyw2g
But in section :root I used this code:
Code:
adb root
adb shell "chmod 777 /system/local/tmp"
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot
@PING 1.1.1.1 -n 1 -w 5000 >NUL
adb wait-for-device
adb shell "echo \"ro.kernel.qemu=1\"> /data/local.prop"
adb reboot
@PING 1.1.1.1 -n 1 -w 5000 >NUL
adb wait-for-device
adb remount
adb shell "chmod 777 /system/bin"
adb push su /system/bin/su
adb shell "chown root.shell /system/bin/su"
adb shell "chmod 06755 /system/bin/su"
adb shell "chmod 06755 /system/bin/su"
adb shell "ln -s /system/bin/su /system/xbin/su"
adb push Superuser.apk /system/app/.
adb shell rm /data/local.prop
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
adb push busybox /data/local/tmp/.
adb shell "chmod 755 /data/local/tmp/busybox"
adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
adb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
adb shell "chown root.shell /system/xbin/busybox"
adb shell "chmod 04755 /system/xbin/busybox"
adb shell "/system/xbin/busybox --install -s /system/xbin"
adb shell "rm -r /data/local/tmp/busybox"
adb reboot
It's not necessary to use any other options than 1. and 2.
After that install Titanium Backup and check for errors and let TB fix it (Some permissions seems to be "broken".).
snapon said:
Try this site slatedroid.com/blog/85/entry-96-aokp-cm9-cm10-installation-guide-for-ampe-a10-sanei-n10/
Click to expand...
Click to collapse
You cannot use this CM9/10, i'ts only for Allwinner A10 CPU!
For now, I didn't found a working recovery.img for MSM8625.
It worked fine, thank you very much! :good:
One problem still exist: the build.prop file still cannot be edited, is write-protected.
---------- Post added at 10:24 PM ---------- Previous post was at 10:18 PM ----------
snapon said:
...I found the original firmware here 86pp.com/download_view.asp....
I think the firmware can also be found here: szampe.com/support_down.asp? but as its all in Chinese its difficult to tell
Click to expand...
Click to collapse
It was deleted from the first site.
On the second site, more specifically from here, you can download the firmware (version 3 Nov, 2012), but I am afraid that everyting is in Chinese.
....
W3sti said:
Try Tasselhofs rootscript at mediafire.com/?2jt4ft8xpfzyw2g
But in section :root I used this code:
Code:
adb root
adb shell "chmod 777 /system/local/tmp"
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot
@PING 1.1.1.1 -n 1 -w 5000 >NUL
adb wait-for-device
adb shell "echo \"ro.kernel.qemu=1\"> /data/local.prop"
adb reboot
@PING 1.1.1.1 -n 1 -w 5000 >NUL
adb wait-for-device
adb remount
adb shell "chmod 777 /system/bin"
adb push su /system/bin/su
adb shell "chown root.shell /system/bin/su"
adb shell "chmod 06755 /system/bin/su"
adb shell "chmod 06755 /system/bin/su"
adb shell "ln -s /system/bin/su /system/xbin/su"
adb push Superuser.apk /system/app/.
adb shell rm /data/local.prop
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
adb push busybox /data/local/tmp/.
adb shell "chmod 755 /data/local/tmp/busybox"
adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
adb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
adb shell "chown root.shell /system/xbin/busybox"
adb shell "chmod 04755 /system/xbin/busybox"
adb shell "/system/xbin/busybox --install -s /system/xbin"
adb shell "rm -r /data/local/tmp/busybox"
adb reboot
It's not necessary to use any other options than 1. and 2.
Hey in root you used the following commands means???how??
i have ordered this tablet and will reach me soon i think,i have the tasselhoof rootscript but it is as follows rite?
option 1 is to check the connection
option 2 is to root.
Then after choosing option 1 did you choosed option 2 or did something else???
can you explain briefly please??
Any help will be great...
Click to expand...
Click to collapse
I did root on my Sanei N10 3G Dualcore, but now I cannot find any recovery.img for CWM, can i use the one from single or quad core sanei N10 device?
I want to make a backup (nandroid) so waht can I do?
Thanks in advance
scotty2000 said:
I did root on my Sanei N10 3G Dualcore, but now I cannot find any recovery.img for CWM, can i use the one from single or quad core sanei N10 device?
I want to make a backup (nandroid) so waht can I do?
Thanks in advance
Click to expand...
Click to collapse
You cannot use an other image. For now it's not possible to use nandroid. Try "Titanium Backup Root" for a most complete backup.
---------- Post added at 08:47 PM ---------- Previous post was at 08:40 PM ----------
h.d.modi said:
...
Hey in root you used the following commands means???how??
i have ordered this tablet and will reach me soon i think,i have the tasselhoof rootscript but it is as follows rite?
option 1 is to check the connection
option 2 is to root.
Then after choosing option 1 did you choosed option 2 or did something else???
can you explain briefly please??
Any help will be great...
Click to expand...
Click to collapse
1. Edit the script, replace the code in section ":root", save the file and execute the script
2. Check the connection with option 1 and choose option 2 to root
3. If you don't know what i explained, ask somebody who knows a bit about batch-programming
its worked for sanei n10 dual core 3g tablet pc Thank you !
W3sti said:
You cannot use an other image. For now it's not possible to use nandroid. Try "Titanium Backup Root" for a most complete backup.
Click to expand...
Click to collapse
Thanks!
Is it possible to create an image out of an other one in an easy way and what do i need to do this?
Or is it to much complicated to work out an recovery image?
I am not really firm with those android things but willing to learn if possible with a "how to guide" for building recovery images
Worked great on Ampe A10, 5min job!
Any news about Android 4.1.x update/rom? Cyanogenmod? Any way to get Jellybean?
Tried to find a way to get jelly bean but i think there isn't any...
BTW, does anyone know SNES emulator that works with this tablet?

ADB Push Fails - Read Only File System; Unable to remount. Bad root?

Hey all,
I was trying to push nano to my phone and I get this:
C:\>adb push nano /system/bin
failed to copy 'nano' to '/system/bin/nano': Read-only file system
Trying remount:
C:\>adb remount
remount failed: Operation not permitted
Then from ADB shell, I try:
c:\>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o rw,remount /system
mount -o rw,remount /system
[email protected]:/ #
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
c:\>adb push nano /system/bin
failed to copy 'nano' to '/system/bin/nano': Permission denied
Any ideas? I'm rooted the superuser and busybox installed.
I rooted using this method:
http://forum.xda-developers.com/showthread.php?t=1956432
Apps get elevated privileges without error. Terminal emulator allows me to view system files. Unfortunately I need to edit some program files in /data/data and there doesn't seem to be any editor available (vi is acting very glitchy). I discovered this problem when I tried to push nano to my phone.
I also tried to access /data using gEditor and it says:
file list
/data
cannot change the directory.
Something is very wrong here. Do I need to re-root using a different method? Please advise. Thanks!
Update: I was able to get adb to work. It turns out I never flashed an unsecured boot image.
However, my nano installation doesn't work and gEditor crashes when I try to access the data folder. That will be for another thread.
For remount and push/pull commands to work, download adbd insecure from playstore . That's the only way you will be able to do the aforementioned commands.
Thanks for the tip. After rerooting the phone with an unsecured image I was able to use adb. I am able to use adb right now without adbd installed however.
Sent from my SGH-T889 using xda app-developers app
I was going crazy allover looking for an answer, and found it here...
Thanks.
Not compatible
teshxx said:
For remount and push/pull commands to work, download adbd insecure from playstore . That's the only way you will be able to do the aforementioned commands.
Click to expand...
Click to collapse
Is there any other option?? That software is not compatible with my android!!
You will have to flash a kernel which has adb secure set to 0.
Sent from my SGH-T889 using xda app-developers app

Categories

Resources