Related
Anyone know how I can restore to stock recovery? I rooted and flashed CWM recovery, but I need to restore to stock because I am having so many problems with random reboots that I see lots of people are also having problems with. I have downloaded the dump. If someone could tell what I need to do on would be extremely grateful.
Even on stock this thing has issues... Im gonna try and return it for a mytouch 4g instead....
Sent from my SGH-T839 using Tapatalk
Ace42 said:
Even on stock this thing has issues... Im gonna try and return it for a mytouch 4g instead....
Sent from my SGH-T839 using Tapatalk
Click to expand...
Click to collapse
That's my problem too, but I can't send it back until I get the stock recovery back. I installed CWM after I rooted.
see my next post for the 1 click
ehall2k7 said:
That's my problem too, but I can't send it back until I get the stock recovery back. I installed CWM after I rooted.
Click to expand...
Click to collapse
Me too, which is why I regret it now....I want a phone hat I less buggy, this thing crashes all the time which sucks. Also the phone won't get much faster since it doesn't have enough space for the galaxy s lagfix, which applies to this since it has rfs and not ext4 like it needs..
@person above, if we brick it then they would replace it, right? You would just need to do some "acting" in the store and play dumb with the rep, if you know what a mean.
Sent from my SGH-T839 using Tapatalk
I edited noobnl's one click uninstaller for epic4g with what i posted above.
Extreme warning: Untested! I do not know if it will work, use at your own risk. Possibility of bricking you!
This one click SHOULD
1. remove root and replace with original files
2. reflash stock bml8 over modified? one (I think CWM is bml8)
Theoretically it shouldnt brick you, but no guarantees.....
If anybody has the guts to test this let me know
updated to Here
http://forum.xda-developers.com/showthread.php?t=803682
that is the link to SuperOneClick its a Root app that you can also use to unroot the device.. i Haven't Received my other SK4G yet to test but it should work its universal and works on multiple phones.
hopefully those that have root can use this method to unroot
blu9987 said:
I edited noobnl's one click uninstaller for epic4g with what i posted above.
Extreme warning: Untested! I do not know if it will work, use at your own risk. Possibility of bricking you!
This one click SHOULD
1. remove root and replace with original files
2. reflash stock bml8 over modified? one (I think CWM is bml8)
Theoretically it shouldnt brick you, but no guarantees.....
If anybody has the guts to test this let me know and i'll post a thread in the dev forum
edit: updated the zip due to a silly error
edit2: in the off chance that you get "mount: operation not premitted" that means it failed to mount /system as rw and wont remove superuser. If you let it continue it will still flash over bml8 though. You can manually remove superuser another way. My phone was only permitting me to mount by
Code:
adb shell
su
(look on phone press allow for superuser popup)
remount rw
then removing all the files using these commands
Code:
adb shell rm /system/bin/joeykrim-root.sh (most likely not there this is old)
adb shell rm /system/bin/jk-su (same as above)
adb shell rm /etc/passwd (pretty sure this isnt here either)
adb shell rm /etc/group (same)
adb shell rm /system/bin/su
adb shell rm /system/xbin/su
adb shell rm /system/app/Superuser.apk
adb push playlogo /system/bin/playlogo
adb shell chmod 755 /system/bin/playlogo
adb shell rm /etc/resolv.conf
adb shell rm /system/bin/remount
adb shell rm /system/bin/busybox
Not saying that you'll have to do that could just be my phone since im on ext4 and such.
Click to expand...
Click to collapse
I'll try it out in the next few hours and let you know. I'm not worried if it bricks cuz I'm still in the 14 days to return it and have had nothing but problems with it random rebooting. I'll let you know. Thanks again.
ehall2k7 said:
I'll try it out in the next few hours and let you know. I'm not worried if it bricks cuz I'm still in the 14 days to return it and have had nothing but problems with it random rebooting. I'll let you know. Thanks again.
Click to expand...
Click to collapse
Just to give a heads up a bricked device will stay at the splash screen or may not even turn on, so it will be hard for them to know.I wish this phone was better, since I wanted I ever since I heard it was being remade by sammy.
Sent from my SGH-T839 using Tapatalk
blu9987 said:
I edited noobnl's one click uninstaller for epic4g with what i posted above.
Extreme warning: Untested! I do not know if it will work, use at your own risk. Possibility of bricking you!
This one click SHOULD
1. remove root and replace with original files
2. reflash stock bml8 over modified? one (I think CWM is bml8)
Theoretically it shouldnt brick you, but no guarantees.....
If anybody has the guts to test this let me know and i'll post a thread in the dev forum
edit: updated the zip due to a silly error
edit2: in the off chance that you get "mount: operation not premitted" that means it failed to mount /system as rw and wont remove superuser. If you let it continue it will still flash over bml8 though. You can manually remove superuser another way. My phone was only permitting me to mount by
Code:
adb shell
su
(look on phone press allow for superuser popup)
remount rw
then removing all the files using these commands
Code:
adb shell rm /system/bin/joeykrim-root.sh (most likely not there this is old)
adb shell rm /system/bin/jk-su (same as above)
adb shell rm /etc/passwd (pretty sure this isnt here either)
adb shell rm /etc/group (same)
adb shell rm /system/bin/su
adb shell rm /system/xbin/su
adb shell rm /system/app/Superuser.apk
adb push playlogo /system/bin/playlogo
adb shell chmod 755 /system/bin/playlogo
adb shell rm /etc/resolv.conf
adb shell rm /system/bin/remount
adb shell rm /system/bin/busybox
Not saying that you'll have to do that could just be my phone since im on ext4 and such.
Click to expand...
Click to collapse
I tried it and still no luck. Here is what I am seeing:
one click uninstaller based off of noobnl's
Press any key to continue . . .
copy and run the exploit (may take 2 minutes)
84 KB/s (0 bytes in 5392.000s)
2 KB/s (0 bytes in 88.000s)
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={2650, 2650}
[*] Searching for adb ...
[+] Found adb as PID 2390
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
remove joeykrim root method
mount: Operation not permitted
rm failed for /system/bin/joeykrim-root.sh, Read-only file system
rm failed for /system/bin/jk-su, Read-only file system
rm failed for /etc/passwd, Read-only file system
rm failed for /etc/group, Read-only file system
rm failed for /system/bin/su, Read-only file system
rm failed for /system/xbin/su, Read-only file system
rm failed for /system/app/Superuser.apk, Read-only file system
failed to copy 'playlogo' to '/system/bin/playlogo': Read-only file system
Unable to chmod /system/bin/playlogo: Read-only file system
rm failed for /etc/resolv.conf, Read-only file system
rm failed for /system/bin/remount, Read-only file system
rm failed for /system/bin/busybox, Read-only file system
copy recovery and flasher
384 KB/s (0 bytes in 313888.000s)
495 KB/s (0 bytes in 7864320.015s)
flashing recovery
RedBend Update Agent 6,1,14,1
FOTA : Make Block Device Nodes
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
open device file: Permission denied
bmldevice_get_size: bmldevice_open failed!src: /sdcard/bml8.bin
dst: /dev/block/bml8 partition size: 0x0
part_size: 0x0
reboot: Operation not permitted
wait 60 second
cleanup
done
Press any key to continue . . .
Do you think it would be possible to flash the bml8.bin with ODIN? I haven't tried to go into download mode but it should be possible seeing how its almost identical to the vibrant and it's made by samsung.
I wonder if this has a bootloader like htc devices where you can flash system images which have the stock recovery, or if the system dump has it, then we can do.. flash recovery /sdcard/xxx.img from term or adb or fastboot, which ever one.
Sent from my SGH-T839 using Tapatalk
you can try making your filesystem r/w before running it.. I dunno why its not mounting properly with adb...
you all have usb debugging enabled right?
Open up command prompt,
cd C:\path\to\uninstaller
adb shell
su
(check prompt on screen superuser)
mount -o remount,rw /dev/block/stl9 /system
then just click the run.bat while the first window is still open
Also before trying this try clearing data on superuser.apk on your phone
You can also try remounting to RW on your phone with like root explorer or terminal emulator... I honestly have no idea why adb keeps getting permission denied
blu9987 said:
you can try making your filesystem r/w before running it.. I dunno why its not mounting properly with adb...
you all have usb debugging enabled right?
Open up command prompt,
cd C:\path\to\uninstaller
adb shell
su
(check prompt on screen superuser)
remount rw
then just click the run.bat while the first window is still open
Also before trying this try clearing data on superuser.apk on your phone
You can also try remounting to RW on your phone with like root explorer or terminal emulator... I honestly have no idea why adb keeps getting permission denied
Click to expand...
Click to collapse
Okay so the original recovery is located on a different part, which CWM doesnt write to, allowing the old one to be used again using this method, correct?Just want to better understand how it works.
Ace42 said:
Okay so the original recovery is located on a different part, which CWM doesnt write to, allowing the old one to be used again using this method, correct?Just want to better understand how it works.
Click to expand...
Click to collapse
I'm pretty sure clockworkmod one click you guys used flashed CWM recovery to /dev/block/bml8 so this restores the original bml8 image
and heres a copy paste from the dump thread
Code:
bml4 1280 KB contains Sbl.bin (1310720 bytes) Secondary Boot Loader (loads the Linux kernel and passes the necessary arguments)
bml5 1280 KB contains Secondary Boot Loader (for recovery, ect)
bml8 7680 KB empty - on Epic 4G and Fascinate, contains recovery.bin
And since you all used the epic recovery flasher, i concluded that it probably flashed bml8 and that you just replace it with the stock bml8 ya?
Also the epic recovery flasher pushes recovery files into /system/bin which need to be removed and I realised that I didnt include that in the one click uninstaller *facepalm*
blu9987 said:
I'm pretty sure clockworkmod one click you guys used flashed CWM recovery to /dev/block/bml8 so this restores the original bml8 image
and heres a copy paste from the dump thread
Code:
bml4 1280 KB contains Sbl.bin (1310720 bytes) Secondary Boot Loader (loads the Linux kernel and passes the necessary arguments)
bml5 1280 KB contains Secondary Boot Loader (for recovery, ect)
bml8 7680 KB empty - on Epic 4G and Fascinate, contains recovery.bin
And since you all used the epic recovery flasher, i concluded that it probably flashed bml8 and that you just replace it with the stock bml8 ya?
Also the epic recovery flasher pushes recovery files into /system/bin which need to be removed and I realised that I didnt include that in the one click uninstaller *facepalm*
Click to expand...
Click to collapse
Oh I see, well I'll let you know how it turns out then.
Edit: In system /bin I have
-recovery(ukn file type)
-recoveryfiles(folder)
-recoveryres(folder)
Also these "bml" files are in /SYS/BLOCK <--according to root explorer
While /DEV/Block only shows "vold" folder, nvm term shows that bml is there
Ace42 said:
Oh I see, well I'll let you know how it turns out then.
Edit: In system /bin I have
-recovery(ukn file type)
-recoveryfiles(folder)
-recoveryres(folder)
Also these "bml" files are in /SYS/BLOCK <--according to root explorer
While /DEV/Block only shows "vold" folder, nvm term shows that bml is there
Click to expand...
Click to collapse
-recovery(ukn file type) comes with the stock system but the one click installer pushed over a modified one. Youd need to replace with the original...I'll add that into the uninstaller
-recoveryfiles(folder) is from the one click installer
-recoveryres(folder) is also from the one click installer
There is also
/system/xbin/remount
and
/system/xbin/busybox
and /system/bin/playlogo (which I already have in the uninstaller..the playlogo they use is what gives permanent root if i remember correctly)
It would be so much easier if somebody on 100% stock would gain temporary root using rageagainstthecage and root.sh and pull the images for a tar then we can put together a stock flash with factoryfs.rfs cache.fs intram.lfs recovery.bin boot.bin sbl.bin and modem.bin
If anyone is interested pm me and i'll give you the info you need on how to do it
blu9987 said:
-recovery(ukn file type) comes with the stock system but the one click installer pushed over a modified one. Youd need to replace with the original...I'll add that into the uninstaller
-recoveryfiles(folder) is from the one click installer
-recoveryres(folder) is also from the one click installer
There is also
/system/xbin/remount
and
/system/xbin/busybox
and /system/bin/playlogo (which I already have in the uninstaller..the playlogo they use is what gives permanent root if i remember correctly)
It would be so much easier if somebody on 100% stock would gain temporary root using rageagainstthecage and root.sh and pull the images for a tar then we can put together a stock flash with factoryfs.rfs cache.fs intram.lfs recovery.bin boot.bin sbl.bin and modem.bin
If anyone is interested pm me and i'll give you the info you need on how to do it
Click to expand...
Click to collapse
Thr thing is..I'm exchanging mines today so I will try what you said and then do a factory erase afterwards. If it leaves some files there's not much I can do, can you fix he uninstaller to add the other files today, ill really appreciate it.
Sent from my SGH-T839 using Tapatalk
Disregard this post i'll make something and put it up after portfolio is done in a few hours
I have attached a one click uninstaller for root, revised and will work. Just extract and run the run.bat
It should remove all root and reflash stock over clockworkmod!
If this works let me know and i'll post it in its own thread
Shameless triple post:
Anyone end up testing this? It would be highly beneficial if somebody could remove CWM and root, restore to stock, and follow some instructions to pull the necessary images to make an odin tar. I would do this myself but I don't have a sidekick. Or maybe once we get a working CWM make a pre-rooted odin flash
Hello experts,
I have experience of few Sony, Samsung devices. Rooting has been easy. Something or the other always works.
But, recently got a Celkon A59 (not sure who is the OEM) and no matter what I do, I can not root it. It is 2.3.6 device.
I have tried the following
1. zergRush
2. OneClickRoot
3. SRSRoot
4. manually copied su, busybox to /data/local/tmp. Tried RW mount of /system. But /system fails to mount in rw mode. I get an error
$ ./busybox mount -o rw,remount /dev/block/mtdblock11 /system
mount: permission denied (are you root?)
Click to expand...
Click to collapse
I think other methods are also failing due to remount is failing
5. Tried building my own update.zip with busybox, su etc.. When tried to load it in recovery mode, I get signature verification error. I also tried to sign it using signapk.jar. But, same result. Looks like the zip needs to be signed with manufacturers keys. But, with these OEM devices, you do not even know that!
Now I am out of ideas.
Android: 2.3.6
Kernel version: 2.6.37.7
Build: ALPS.GB2.MP.V2.24
Click to expand...
Click to collapse
Help!
-ajay
bump
can someone suggest what else I can try?
its easy
tri this bro
http://forum.xda-developers.com/che...-to-root-install-cwm-celkon-a59-easy-t3086120
I have the Pantech Discover
My phone is rooted because of WiFi issues
It only remembered the first 2 WiFi networks I came across after I bought the phone.
So I did all kinds of stuff to it to fix it. But I apparently screwed something up while fixing it, kind of. lol
Every time my phone restarts I have to go to the WiFi files and change the permissions in order for WiFi to turn on.
Other than that it works like a champ. This however isn't the problem.
I want to start fresh. Factory Rom would be great, but nobody has one.
There is an update to 4.1 jellybean for my phone OTA but It gets an error every time I try to update it.
Is there anything I can do?
ANY suggestions or help would be greatly appreciated
Thanks
TheAtreus said:
I have the Pantech Discover
My phone is rooted because of WiFi issues
It only remembered the first 2 WiFi networks I came across after I bought the phone.
So I did all kinds of stuff to it to fix it. But I apparently screwed something up while fixing it, kind of. lol
Every time my phone restarts I have to go to the WiFi files and change the permissions in order for WiFi to turn on.
Other than that it works like a champ. This however isn't the problem.
I want to start fresh. Factory Rom would be great, but nobody has one.
There is an update to 4.1 jellybean for my phone OTA but It gets an error every time I try to update it.
Is there anything I can do?
ANY suggestions or help would be greatly appreciated
Thanks
Click to expand...
Click to collapse
The update validates that dozens of files in /system including everthing in /system/app is there and unmodified. The user gj23 was kind enough to provide the original ICS /system files here: http://www.mediafire.com/folder/r3n3loxxlrv08/systemext4. I was able to help another user with the same problem get updated and suggest the following procedure.
Do this at your own risk. I do not recommend that you try to replace a file unless you are sure you removed or modified it or it shows up as invalid in the log. This can be tedious but far less tedious and risky than reconstructing the entire /system partition (voice of experience).
NOTE: Download and use the VooDoo OTA Rootkeeper application to temporarily unroot. You can use the app to restore root after the update. If you lose root several users have reported Framaroot 1.6 works with Jellbean, download here: http://forum.xda-developers.com/showthread.php?t=2130276.
Dowload the JB update on the phone and choose to delay the update.
Install an sd card in the phone and using a root explorer copy the update to the external sd card. The update is called gota_package.bin and is in /cache/recovery.
Rename the file you copied to the external sd card to gota_package.zip.
Open the last_log file in the /cache/recovery folder with a text editor, scroll to the bottom, and look for a message indicating which file failed the checksum validation.
Download the valid version of the file that failed from the site I posted above. If there is a file with the same name in the same folder but with a different extension (e.g. myfile.apk & myfile.odex) dowload both.
Using a root explorer copy the file(s) you downloaded to the appropriate directory on your device.
Access recovery mode. To do this shutdown the phone, hold the volume up key and the power key down, when you see "pantech" flash on then off let go of the power button. You should be at the green robot screen, if not try again. From here, hold down power, press up volume, then let go of both. You should see a menu of options if not try again.
Use the volume keys to navigate to the option that allows you to install an update from the external sd card, press power, select gota_package.zip, press power again to run the update.
If the update fails go back to step 4 and repeat the process.
If you know which /system/app files you removed you can download and copy all of them (both apk & odex) at once.
Ask if you have questions.
sandnap said:
The update validates that dozens of files in /system including everthing in /system/app is there and unmodified. The user gj23 was kind enough to provide the original ICS /system files here: http://www.mediafire.com/folder/r3n3loxxlrv08/systemext4. I was able to help another user with the same problem get updated and suggest the following procedure.
Do this at your own risk. I do not recommend that you try to replace a file unless you are sure you removed or modified it or it shows up as invalid in the log. This can be tedious but far less tedious and risky than reconstructing the entire /system partition (voice of experience).
Dowload the JB update on the phone and choose to delay the update.
Install an sd card in the phone and using a root explorer copy the update to the external sd card. The update is called gota_package.bin and is in /cache/recovery.
Rename the file you copied to the external sd card to gota_package.zip.
Open the last_log file in the /cache/recovery folder with a text editor, scroll to the bottom, and look for a message indicating which file failed the checksum validation.
Download the valid version of the file that failed from the site I posted above. If there is a file with the same name in the same folder but with a different extension (e.g. myfile.apk & myfile.odex) dowload both.
Using a root explorer copy the file(s) you downloaded to the appropriate directory on your device.
Access recovery mode. To do this shutdown the phone, hold the volume up key and the power key down, when you see "pantech" flash on then off let go of the power button. You should be at the green robot screen, if not try again. From here, hold down power, press up volume, then let go of both. You should see a menu of options if not try again.
Use the volume keys to navigate to the option that allows you to install an update from the external sd card, press power, select gota_package.zip, press power again to run the update.
If the update fails go back to step 4 and repeat the process.
If you know which /system/app files you removed you can download and copy all of them (both apk & odex) at once.
Ask if you have questions.
Click to expand...
Click to collapse
Can someone provide the gota_package.bin file?
jose makalolot said:
Can someone provide the gota_package.bin file?
Click to expand...
Click to collapse
Uploading gota_package.zip (renamed already), I'll PM you a link in a while.
sandnap said:
Uploading gota_package.zip (renamed already), I'll PM you a link in a while.
Click to expand...
Click to collapse
thank you sir
Sent from my SAMSUNG-SGH-I727 using Tapatalk 4
Wow... Totally lost hope in finding a solution.. I'm not sure which files have been modified due to me allowing apps to try and fix issues with my phone and getting the permissions to "stick" I'll take a look at what you've presented here and try to figure out which files I need to change
Sent from my PantechP9090 using xda app-developers app
attnav.apk first delinquent lol... I removed that soon after rooting.. so no surprise there. Ill let you know how it all goes
Update 1:
currently downloading (slowly) the update file.
While I wait I am checking my phones files with the list of files in the link above.
Ive created a mirror image of the folder structure on my computer where i download all the missing files in the appropriate folders. So far in the apps folder in the "A"s ive deleted 4 files family map.. the stupid driving app attnav and some other att bull..
I knew it would come down to this but wasn't anything I could do without the original files... THANK YOU GUYS sooo much
Update 2:
Final Count in the app folder was 16 missing files... Question. Should I remove the superuser.apk file?
Okay.... update worked... but now wifi isnt working... i cant change the wpa_ sup file to get wifi back on... sooooo anybody know how to root this version.. or possibly fixing the permissions on those GOD forsaken files so i dont have to keep changing them everytime i turn my phone on.
TheAtreus said:
Okay.... update worked... but now wifi isnt working... i cant change the wpa_ sup file to get wifi back on... sooooo anybody know how to root this version.. or possibly fixing the permissions on those GOD forsaken files so i dont have to keep changing them everytime i turn my phone on.
Click to expand...
Click to collapse
Well anyone who has this phone and does this... It works GREAT. BTW my root was still in place but superuser temporarily unrooted my phone and had rootkeeper enabled... I just unchecked temp unroot and its back in business...
Still does anyone know how to make the permissions stick... OR could Greg Jennings upload just the wifi files.
I know there are multiple files but all known associated files to the operation of wifi would be great. I was hoping this update would fix the issue but it didnt.
TheAtreus said:
Well anyone who has this phone and does this... It works GREAT. BTW my root was still in place but superuser temporarily unrooted my phone and had rootkeeper enabled... I just unchecked temp unroot and its back in business...
Still does anyone know how to make the permissions stick... OR could Greg Jennings upload just the wifi files.
I know there are multiple files but all known associated files to the operation of wifi would be great. I was hoping this update would fix the issue but it didnt.
Click to expand...
Click to collapse
What exactly do you do to get it working after a reboot? Can you access it with adb? More than likely you just need to mount the partition as read/write before making the changes
---------- Post added at 07:02 AM ---------- Previous post was at 06:50 AM ----------
TheAtreus said:
Okay.... update worked... but now wifi isnt working... i cant change the wpa_ sup file to get wifi back on... sooooo anybody know how to root this version.. or possibly fixing the permissions on those GOD forsaken files so i dont have to keep changing them everytime i turn my phone on.
Click to expand...
Click to collapse
I updated the tutorial above to address maintaining root or rerooting after the update.
sandnap said:
What exactly do you do to get it working after a reboot? Can you access it with adb? More than likely you just need to mount the partition as read/write before making the changes
---------- Post added at 07:02 AM ---------- Previous post was at 06:50 AM ----------
I updated the tutorial above to address maintaining root or rerooting after the update.
Click to expand...
Click to collapse
I got root back... luckily the superuser app is smarter than me.
When I turn the phone on, it wont even let the wifi turn on for a second... So I go to /data/misc/wifi and change the permission of wpa_supplicant.conf from rw-rw---- to rwxrwxrwx ... but it always reverts back if my phone ever turns off.
There are some other files I do the same way. I am doing this using ES File Explorer. Also that wpa file along with some others have root for the owner and for the group.
Im just tired of having to do that and remembering all the passkeys to all my friends networks because my phone cant.
TheAtreus said:
I got root back... luckily the superuser app is smarter than me.
When I turn the phone on, it wont even let the wifi turn on for a second... So I go to /data/misc/wifi and change the permission of wpa_supplicant.conf from rw-rw---- to rwxrwxrwx ... but it always reverts back if my phone ever turns off.
There are some other files I do the same way. I am doing this using ES File Explorer. Also that wpa file along with some others have root for the owner and for the group.
Im just tired of having to do that and remembering all the passkeys to all my friends networks because my phone cant.
Click to expand...
Click to collapse
If you have adb access to the phone type (hit enter after each line):
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p14 /system
mount -o rw,remount /dev/block/mmcblk0p25 /data
If you don't have access to adb download the "Android Terminal Emulator" app from the Play Store, open it and type:
Code:
su
mount -o rw,remount /dev/block/mmcblk0p14 /system
mount -o rw,remount /dev/block/mmcblk0p25 /data
Now, make your permission changes, reboot, and report back. If that doesn't work give me the full path of all files causing the issue and I will write a script that will take care of it.
Alright will do
Sent from my PantechP9090 using xda app-developers app
sandnap said:
If you have adb access to the phone type (hit enter after each line):
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p14 /system
mount -o rw,remount /dev/block/mmcblk0p25 /data
If you don't have access to adb download the "Android Terminal Emulator" app from the Play Store, open it and type:
Code:
su
mount -o rw,remount /dev/block/mmcblk0p14 /system
mount -o rw,remount /dev/block/mmcblk0p25 /data
Now, make your permission changes, reboot, and report back. If that doesn't work give me the full path of all files causing the issue and I will write a script that will take care of it.
Click to expand...
Click to collapse
Okay i followed the directions.
I rebooted my phone first
Connected it to my computer after it finished booting
Opened my command prompt
made sure my phone was detected
Ran adb shell (said it was out of date)
Here is a copy of what I did
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\System32>adb shell
adb server is out of date. killing...
* daemon started successfully *
[email protected]:/ $ su
su
[email protected]:/ # mount -o rw,remount /dev/block/mmcblk0p14 /system
mount -o rw,remount /dev/block/mmcblk0p14 /system
[email protected]:/ # mount -o rw,remount /dev/block/mmcblk0p25 /data
mount -o rw,remount /dev/block/mmcblk0p25 /data
[email protected]:/ #
Also here is a list of my mounts after reboot
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\System32>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,relatime,data=orde
red 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,rel
atime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,relatime,noauto_da
_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,relatim
e,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000
,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=low
er,errors=remount-ro 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1
023,default_permissions,allow_other 0 0
/dev/block/vold/179:33 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard1/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
[email protected]:/ #
None of what i did before stuck
Here is a list of the files, the status of the files, and what I change on each file.
/data/misc/wifi/wpa_supplicant.conf rw-rw---- O root G root CHANGED TO rwxrwxrwx (i didnt change the owner or group on any of them)
/data/misc/wifi/WCNSS_qcom_cfg.ini rw-rw---- O system G wifi CHANGED TO rwxrwxrwx
/data/misc/wifi/wpa_suplicant/wlan0 STAYED AFTER TRYING YOUR FIX it is rwxrwxrwx O wifi G wifi
/dev/network_latency rw-rw---- O root G root CHANGED TO rwxrwxrwx
/dev/network_throughput rw-rw---- O root G root CHANGED TO rwxrwxrwx
/dev/wcnss_wlan rw-rw---- O root G root CHANGED TO rwxrwxrwx
After reboot they all except the one I told you about changed back.
I honestly dont know what files do what for wifi... so I just changed these try and make the networks STICK... All I need to do to get wifi to actually turn on and act right is change that first file and it will turn on and take a network passkey and continue working until phone reboots. then i have to change the permissions again and re-enter the passkey for the networks.
Just read that wifi is controlled by the kernel.. When I rooted my phone (using the guide found here at xda ultimate... ) I believe it had the original ics kernel. Would that help?
Sent from my PantechP9090 using xda app-developers app
If you need any more information just let me know
Sent from my PantechP9090 using xda app-developers app
The permissions and ownership for the same files on my JB discover are:
/data/misc/wifi/wpa_supplicant.conf rw-rw---- O system G wifi
/data/misc/wifi/WCNSS_qcom_cfg.ini rw-rw---- O system G wifi
/data/misc/wifi/wpa_suplicant/wlan0 rwxrwx--- O wifi G wifi
/dev/network_latency rw------- O root G root
/dev/network_throughput rw------- O root G root
/dev/wcnss_wlan rw------- O root G root
It looks like the ownership is different for the first file but you have the same ownership and equal or looser permissions on the rest of the files. Try changing the ownership of wpa_supplicant.conf:
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p25 /data
chown system:wifi /data/misc/wifi/wpa_supplicant.conf
exit
exit
adb reboot
sandnap said:
The permissions and ownership for the same files on my JB discover are:
/data/misc/wifi/wpa_supplicant.conf rw-rw---- O system G wifi
/data/misc/wifi/WCNSS_qcom_cfg.ini rw-rw---- O system G wifi
/data/misc/wifi/wpa_suplicant/wlan0 rwxrwx--- O wifi G wifi
/dev/network_latency rw------- O root G root
/dev/network_throughput rw------- O root G root
/dev/wcnss_wlan rw------- O root G root
It looks like the ownership is different for the first file but you have the same ownership and equal or looser permissions on the rest of the files. Try changing the ownership of wpa_supplicant.conf:
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p25 /data
chown system:wifi /data/misc/wifi/wpa_supplicant.conf
exit
exit
adb reboot
Click to expand...
Click to collapse
That worked half way. Now I dont have to change any permissions in order to get wifi to turn on but now I have to enter in the passkey for the network every 3 minutes or so because it wipes it or something
UPDATE
Im the type to just fiddle with stuff till it works.. While this hasn't really fixed my issue it might explain whats going on more to you that know the inner workings of Android linux OS better than i do. After I type the passkey in for my wifi network I wait for it to connect and before it shuts off on me I restart my phone... I tried it with the regular connection I have and after that I was think OH maybe it just needed to restart to fix it so i tested with my 5G connection. I put the passkey in and turned my wifi off and then back on it lost the info for 5G and still had the regular... So I typed it in again and restarted my phone and now both are stored permanently (i assume)
TheAtreus said:
That worked half way. Now I dont have to change any permissions in order to get wifi to turn on but now I have to enter in the passkey for the network every 3 minutes or so because it wipes it or something
UPDATE
Im the type to just fiddle with stuff till it works.. While this hasn't really fixed my issue it might explain whats going on more to you that know the inner workings of Android linux OS better than i do. After I type the passkey in for my wifi network I wait for it to connect and before it shuts off on me I restart my phone... I tried it with the regular connection I have and after that I was think OH maybe it just needed to restart to fix it so i tested with my 5G connection. I put the passkey in and turned my wifi off and then back on it lost the info for 5G and still had the regular... So I typed it in again and restarted my phone and now both are stored permanently (i assume)
Click to expand...
Click to collapse
So it seems to be okay for now? It's strange that it wipes after a few minutes. In Settings > Backup & Reset do you have the "Back up my data" checkbox checked? It's a long shot but I wonder if it's synchronizing with the google server and your settings are being overwritten. If you have this selected you can try unchecking it. Have you tried doing a factory data reset?
On a different topic, have you tried booting to the recovery-evita.img since you updated to Jellybean? I am pretty sure they locked the bootloader with the JB update but wanted to confirm with others.
sandnap said:
So it seems to be okay for now? It's strange that it wipes after a few minutes. In Settings > Backup & Reset do you have the "Back up my data" checkbox checked? It's a long shot but I wonder if it's synchronizing with the google server and your settings are being overwritten. If you have this selected you can try unchecking it. Have you tried doing a factory data reset?
On a different topic, have you tried booting to the recovery-evita.img since you updated to Jellybean? I am pretty sure they locked the bootloader with the JB update but wanted to confirm with others.
Click to expand...
Click to collapse
This is what I got when I tried
C:\Users\Atreus\Downloads>fastboot devices
6603452b fastboot
C:\Users\Atreus\Downloads>fastboot boot recovery-evita.img
downloading 'boot.img'...
OKAY [ 0.640s]
booting...
FAILED (remote: Not Support !!)
finished. total time: 0.656s
C:\Users\Atreus\Downloads>
So it looks like they patched that... If somebody wanted root their phone like our. they would need to revert back to ICS do you know how to do that?
Updated OP with solution, many thanks to @fipsy for the final solution, here is his post for those that need help rooting this device: (UPDATE: Root for 4.2.2 at the end of the post)
fipsy said:
Last week I investigated a lot of days to solve the problem: (I'm sorry for not being able to post working links in this forum because I didn't write enough here. So you have to reconstruct my links yourself into your browser)
As omegadrive supposed you just have to exchange the su binary, give the right permissions and the Superuser App from the Playstore will immediately work.
The necessary USB drivers for the device are found here: http://yadi.sk/d/54lX5c2O386XU
They only work with Windows 7!
After starting the "adb shell" you can gain root permissions on the device by typing "su". The su distributed with the device in /system/xbin is not compatible with common superuser apks. So it has to be exchanged with the version 3.1.1 binary: http://downloads.androidsu.com/superuser/su-bin-3.1.1-arm-signed.zip
Copy it to your /sdcard. Then continue with adb shell:
Code:
$ su
# cd /system/xbin
Mount the system partition read/write:
Code:
# mount -o remount,rw -t rfs /dev/block/st19 /system
Rename the original binary for later use (if something fails):
Code:
# mv su su-orig
Copy the binary to the xbin folder:
Code:
# busybox cp /sdcard/su ./su
Change the permissions:
Code:
# chmod 6755 su
Mount the system partition read-only and exit:
Code:
# mount -o remount,ro -t rfs /dev/block/st19 /system
# exit
$ exit
Now install the Superuser App from the Playstore - and have fun! Do *NOT* Update the su binary from within the Superuser App or it will be overwritten with a non-working version!
Cheers, Volker
Click to expand...
Click to collapse
CUSTOM RECOVERY FINALLY POSSIBLE!!! Again, many thanks to @fipsy, here is his post:
fipsy said:
I finally made it! :laugh: Here is a working CWM Recovery for the HANNspree HANNSpad SN1AT71 (HSG1279).
I didn't fully test it but the backup function works. Also mounting and unmounting partitions works as well as the adb shell which is very important if the device is bricked and doesn't boot anymore.
Before connecting to the device via adb shell it is necessary to mount the /system partition (menu "mounts and storage") because otherwise /system/bin/sh cannot be found by adb shell.
The CWM recovery by default stores it's backups on the external SD-Card. The benefit is that the backup can easily be plugged out and stored apart from the device. But the recovery is also able to restore backups from the internal sdcard. Those backups can be made online on a running android system by using apps like "Online Nandroid Backup" and "Nandroid Manager". The benefit is that it's not necessary to reboot the device before backing up and you can keep on working.
There is one problem when creating backups in CWM Recovery: The date/time of the backup is always set to 1st of January 1970 due to a missing backup battery in this device. Look here: http://tau.shadowchild.nl/attn1/?p=341. So if you want to make backups with accurate timestamps you would have to set the actual time of the device using adb shell: Start adb shell and enter:
Code:
/system/xbin/busybox date -s "YYYY-MM-DD hh:mm:ss"
before making the backup.
To cut a long story short: Download the CWM-Recovery here: http://yadi.sk/d/ArprqzfFFWvy4 and flash it to your (rooted) device. How to do this:
Copy the file cwm-recovery.ima to your internal sdcard.
Either connect via adb shell and enter su
or run a Terminal Emulator and enter su
then enter
Code:
cat /sdcard/cwm-recovery.ima > /dev/block/acta
and you're done! Have fun! Comments are appreciated!
Perhaps someone likes to create an update.zip from it?
Edit (01/28/2014): There is a new version 6.0.3.3. Look here: http://forum.xda-developers.com/showpost.php?p=49835135&postcount=283
Edit (05/04/2014): There is a new version 6.0.3.3.a. Look here: http://forum.xda-developers.com/showpost.php?p=52416205&postcount=492
Click to expand...
Click to collapse
ROOT for new OTA 4.2.2 update:
fipsy said:
Good news for germany: The rollout began tonight! I just got the update to Android 4.2.2! :laugh:
Some people asked for the upgrade file to manually update from the recovery. Here it is: http://yadi.sk/d/igsBGsAjFpLsL
Edit (01/13/2014): Seems this update only works on devices with special G-Sensor hardware (KIONIX 3-axis Accelerometer).
@ig6677: There you will also find the META-INF you wanted.
For your information: After my update to Android 4.2.2 root has gone on my device! I expected this. All Apps that need root don't work anymore. I don't know what you did that root was still there after the update...
Furthermore in /system/xbin there is no su file anymore. Also my CWM Recovery has gone and was replaced by the Stock HANNspree recovery!
But whats new: If you connect to the device via adb shell you immediately have superuser rights! No su is needed for this anymore. So it's possible to restore the CWM Recovery using cat.
If you adb push the 3.1.1 su binary from your pc to the /sdcard on your device and after this execute my commands in the first posting of this thread the apps have su rights with superuser.apk again. But you will not be able to add new programs to the superuser app (if a new app requests superuser rights there is no popup). So this is no solution.
The Superuser App is not able to grant superuser rights on android systems > 4.1.1, but the App SuperSu is! So download the SuperSU ZIP from here: http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
Then copy it to your sdcard and install it using the Recovery. Voila! Everything works again!
Another issue: The Huawei E1750 Surfstick is not detected anymore. On 4.1.1 it was no problem to surf using this stick. But I think this is one of the "great features" of the new android versions...
Click to expand...
Click to collapse
New recovery version!
fipsy said:
:victory: Here it is: The new version 6.0.3.3 of CWM Recovery for the HANNspree HANNSpad SN1AT71 (HSG1279)
Beside some minor bugfixes the main benefit of this release is that there are no more errors when trying to restore the .android_secure folder. So the "dirty" workaround to restore this folder is not necessary anymore.
The .android_secure folder is also automatically restored together with the data partition when selecting "data" from the "advanced restore" options.
http://yadi.sk/d/OmsYk6TIGsBsB
Information on how to install you will find here: http://forum.xda-developers.com/showpost.php?p=49166546&postcount=133
Cheers, Volker
Click to expand...
Click to collapse
My original question:
Just bought this tablet on Cybermonday for a really good price, but can't find a way to root it for the life of me...
Main problem has been I can't see it using ADB (v1.0.31), always list no devices even with the latest generic Google ADB driver, which shows fine on device manager.
Tablet comes with Android 4.1.1 and no extras, is just a plain version of android with Play market and ES File Explorer pre installed and have access to android stock recovery.
Any ideas?
Also, just in case I start messing with the tablet, Any way I can backup the stock system just in case?
Thanks.
Update:
More info on the tablet...
Model name: SN1AT71
Hardware (According to CPU-Z): gs702a
Board: full_gs702a
Click to expand...
Click to collapse
Omegadrive said:
Just bought this tablet on Cybermonday for a really good price, but can't find a way to root it for the life of me...
Main problem has been I can't see it using ADB (v1.0.31), always list no devices even with the latest generic Google ADB driver, which shows fine on device manager.
Tablet comes with Android 4.1.1 and no extras, is just a plain version of android with Play market and ES File Explorer pre installed and have access to android stock recovery.
Any ideas?
Also, just in case I start messing with the tablet, Any way I can backup the stock system just in case?
Thanks.
Update 1:
More info on the tablet...
Model name: SN1AT71
Hardware (According to CPU-Z): gs702a
Board: full_gs702a
Click to expand...
Click to collapse
Update 2:
Found that this tablet is practically the same as the Ainol Novo 10 Hero (don't know if version 1 or 2 thou)
So looking in Google found a thread that has modded ADB drivers and following the instructions managed to get ADB to find the device.
Now to keep experimenting
Omegadrive said:
Update 2:
Found that this tablet is practically the same as the Ainol Novo 10 Hero (don't know if version 1 or 2 thou)
So looking in Google found a thread that has modded ADB drivers and following the instructions managed to get ADB to find the device.
Now to keep experimenting
Click to expand...
Click to collapse
Update 3:
After trying over 20 generic rooting methods I come back defeated, 6 hours of testing and nothing. :crying:
I also have picked up 2 of these devices (1 for me and 1 for my wife). I have tried every method I can find to root this, inclicking mutliple one click solutions, apps that are suposted to root, etc. and none of them seem to work, I think the reason why is because the device is being reconized as allready being rooted, SuperOneClick, Framaroot, and Kingo all stated that it was allready rooted ..but apps will not install as if the device was truly rooted. Also geting "access denied" when trying to access the root folder..
Applications that require root will install because they think it has root, they also will prompt stating to give root access/permissions, but when accepting, they simply lock up because they can't access the root correctly.
anyways, I'm done trying for now.. if anyone has any other ideas, please speak up and let us know. thanks!
also have one of these
Temil2006 said:
I also have picked up 2 of these devices (1 for me and 1 for my wife). I have tried every method I can find to root this, inclicking mutliple one click solutions, apps that are suposted to root, etc. and none of them seem to work, I think the reason why is because the device is being reconized as allready being rooted, SuperOneClick, Framaroot, and Kingo all stated that it was allready rooted ..but apps will not install as if the device was truly rooted. Also geting "access denied" when trying to access the root folder..
Applications that require root will install because they think it has root, they also will prompt stating to give root access/permissions, but when accepting, they simply lock up because they can't access the root correctly.
anyways, I'm done trying for now.. if anyone has any other ideas, please speak up and let us know. thanks!
Click to expand...
Click to collapse
I picked up one of these also, I tried a few of the rooting methods you guys listed before finding this post. also no sucess, Would love to get this working bit better,because stock rom is a bit sluggish when it shouldn't be given the specs.
OK, kept trying and found some interesting stuff, first of all a screenshot with the tablet info:
{
"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, it seems the tablet is already rooted but the root is just dummy or the interface has been disabled with deny set as default for any application.
So the trick to root it must be a way to replace de su binary or change the default permission to allow.
Any experts have any idea how to achieve this?
Sent from my HSG1279 using xda app-developers app
I thought about buying this Tab. But if there is no working root-methode or costumROM ability thats a dealbreaker for me.
You told that this tab should be identical to the "Ainol Novo 10 Hero". I dont know if that is true, because in one forum some guy told, that the HannSpee is chargeable via the USB-Port, and afaik the Ainol is not. You have the Hannspee, can you tell me if it is chargeable via USB ?
Anyway, on the german Amazon-site there is a guy that claims that costum-ROMs are working on the Ainol
I will ask him how he managed that and perhaps you can try that on you device. But I dont know if he answers, because responds on Amazon-rewievs are not like those in forums (often never answered)
hope some nerd comes up with a nice plan to break into this device......non-rooted devices are s**t!
greetz gerd
Omegadrive said:
OK, kept trying and found some interesting stuff, first of all a screenshot with the tablet info:
Second, it seems the tablet is already rooted but the root is just dummy or the interface has been disabled with deny set as default for any application.
So the trick to root it must be a way to replace de su binary or change the default permission to allow.
Any experts have any idea how to achieve this?
Sent from my HSG1279 using xda app-developers app
Click to expand...
Click to collapse
revnu said:
I thought about buying this Tab. But if there is no working root-methode or costumROM ability thats a dealbreaker for me.
You told that this tab should be identical to the "Ainol Novo 10 Hero". I dont know if that is true, because in one forum some guy told, that the HannSpee is chargeable via the USB-Port, and afaik the Ainol is not. You have the Hannspee, can you tell me if it is chargeable via USB ?
Anyway, on the german Amazon-site there is a guy that claims that costum-ROMs are working on the Ainol
I will ask him how he managed that and perhaps you can try that on you device. But I dont know if he answers, because responds on Amazon-rewievs are not like those in forums (often never answered)
hope some nerd comes up with a nice plan to break into this device......non-rooted devices are s**t!
greetz gerd
Click to expand...
Click to collapse
Well, I deduced it was identical to the Ainol Novo cause at least the hardware specs are identical and the board and CPU are reported by CPU - Z to be the same one. Tablet layout is a little different thou.
Anyway yes, this one charges through the USB port, but really slowly, good enough to have the USB connected while using it and will not drain the battery, but on my last test it barely charged 5% in 3 to 4 hours of while using it.
Crossing my fingers you can get in contact with that guy and we can figure out how to root this ****er lol
Sent from my XT910 using Tapatalk
Omegadrive said:
Well, I deduced it was identical to the Ainol Novo cause at least the hardware specs are identical and the board and CPU are reported by CPU - Z to be the same one. Tablet layout is a little different thou.
Anyway yes, this one charges through the USB port, but really slowly, good enough to have the USB connected while using it and will not drain the battery, but on my last test it barely charged 5% in 3 to 4 hours of while using it.
Crossing my fingers you can get in contact with that guy and we can figure out how to root this ****er lol
Sent from my XT910 using Tapatalk
Click to expand...
Click to collapse
He answered me, that his Hero came rooted when he bought it and that he simply had to install CWM. He posted a link with iinstructions but I bet it wont help, because the HANNSpree cames with kind of a fakeroot.
revnu said:
He answered me, that his Hero came rooted when he bought it and that he simply had to install CWM. He posted a link with iinstructions but I bet it wont help, because the HANNSpree cames with kind of a fakeroot.
Click to expand...
Click to collapse
Unfortunately it didn't worked, kept failing at validating files when it was installing from default recovery.
Anyway, going to try another method, these are the steps I followed:
1) Get ADB working and recognized.
a) Download these modded drivers and extract them.
b) Do this to install them since the drivers are not signed:
run CMD as admin
bcdedit -set TESTSIGNING ON
reboot
install driver from device manager
bcdedit -set TESTSIGNING OFF
reboot
c) Go to %userprofile%\.android folder and if it doesn't exist create a text file named "adb_usb.ini" (no quotes and make sure INI is the extension, not TXT), open it and just add "0x10D6" (no quotes), save it
d) open CMD as admin
adb devices
Your device should be recognized at this point, this is what I got:
C:\>adb devices
List of devices attached
0123456789ABCDEF device
2) Will update post with new findings here...
How to root the device
Last week I investigated a lot of days to solve the problem: (I'm sorry for not being able to post working links in this forum because I didn't write enough here. So you have to reconstruct my links yourself into your browser)
As omegadrive supposed you just have to exchange the su binary, give the right permissions and the Superuser App from the Playstore will immediately work.
The necessary USB drivers for the device are found here: http: //yadi.sk/d/54lX5c2O386XU
They only work with Windows 7!
After starting the "adb shell" you can gain root permissions on the device by typing "su". The su distributed with the device in /system/xbin is not compatible with common superuser apks. So it has to be exchanged with the version 3.1.1 binary: http: //downloads.androidsu.com/superuser/su-bin-3.1.1-arm-signed.zip
Copy it to your /sdcard. Then continue with adb shell:
Code:
$ su
# cd /system/xbin
Mount the system partition read/write:
Code:
# mount -o remount,rw -t rfs /dev/block/st19 /system
Rename the original binary for later use (if something fails):
Code:
# mv su su-orig
Copy the binary to the xbin folder:
Code:
# busybox cp /sdcard/su ./su
Change the permissions:
Code:
# chmod 6755 su
Mount the system partition read-only and exit:
Code:
# mount -o remount,ro -t rfs /dev/block/st19 /system
# exit
$ exit
Now install the Superuser App from the Playstore - and have fun! Do *NOT* Update the su binary from within the Superuser App or it will be overwritten with a non-working version!
Cheers, Volker
Omegadrive said:
Unfortunately it didn't worked, kept failing at validating files when it was installing from default recovery.
Anyway, going to try another method, these are the steps I followed:
1) Get ADB working and recognized.
a) Download modded drivers and extract them.
b) Do this to install them since the drivers are not signed:
run CMD as admin
bcdedit -set TESTSIGNING ON
reboot
install driver from device manager
bcdedit -set TESTSIGNING OFF
reboot
c) Go to %userprofile%\.android folder and if it doesn't exist create a text file named "adb_usb.ini" (no quotes and make sure INI is the extension, not TXT), open it and just add "0x10D6" (no quotes), save it
d) open CMD as admin
adb devices
Your device should be recognized at this point, this is what I got:
C:\>adb devices
List of devices attached
0123456789ABCDEF device
2) Will update post with new findings here...
Click to expand...
Click to collapse
umm, instead of using custom drivers, why not simply use the newest android Drivers? confirmed they work and device is reconized correctly, as long as you "install official droid drivers" then change the "adb_usb.ini" to only include 0x10D6 device, same as your last steps, but using official drivers, instead of custom ones. Maybe it has something to do with the failures?
---------- Post added at 08:00 PM ---------- Previous post was at 07:53 PM ----------
fipsy said:
Last week I investigated a lot of days to solve the problem: (I'm sorry for not being able to post working links in this forum because I didn't write enough here. So you have to reconstruct my links yourself into your browser)
As omegadrive supposed you just have to exchange the su binary, give the right permissions and the Superuser App from the Playstore will immediately work.
The necessary USB drivers for the device are found here: http: //yadi.sk/d/54lX5c2O386XU
They only work with Windows 7!
After starting the "adb shell" you can gain root permissions on the device by typing "su". The su distributed with the device in /system/xbin is not compatible with common superuser apks. So it has to be exchanged with the version 3.1.1 binary: http: //downloads.androidsu.com/superuser/su-bin-3.1.1-arm-signed.zip
Copy it to your /sdcard. Then continue with adb shell:
Code:
$ su
# cd /system/xbin
Mount the system partition read/write:
Code:
# mount -o remount,rw -t rfs /dev/block/st19 /system
Rename the original binary for later use (if something fails):
Code:
# mv su su-orig
Copy the binary to the xbin folder:
Code:
# busybox cp /sdcard/su ./su
Change the permissions:
Code:
# chmod 6755 su
Mount the system partition read-only and exit:
Code:
# mount -o remount,ro -t rfs /dev/block/st19 /system
# exit
$ exit
Now install the Superuser App from the Playstore - and have fun! Do *NOT* Update the su binary from within the Superuser App or it will be overwritten with a non-working version!
Cheers, Volker
Click to expand...
Click to collapse
thanks for this info. I'll test it out tonight, and let you know.
one question though.. so are you saying that future updates of SU will not work? if we do this, should we also disable auto-updates? If the software does update, will it break our system.. or simply that we need to reload the SU over again, but the OS will open, just limited to "non-rooted" ? ??
fipsy said:
Last week I investigated a lot of days to solve the problem: (I'm sorry for not being able to post working links in this forum because I didn't write enough here. So you have to reconstruct my links yourself into your browser)
As omegadrive supposed you just have to exchange the su binary, give the right permissions and the Superuser App from the Playstore will immediately work.
The necessary USB drivers for the device are found here: http: //yadi.sk/d/54lX5c2O386XU
They only work with Windows 7!
After starting the "adb shell" you can gain root permissions on the device by typing "su". The su distributed with the device in /system/xbin is not compatible with common superuser apks. So it has to be exchanged with the version 3.1.1 binary: http: //downloads.androidsu.com/superuser/su-bin-3.1.1-arm-signed.zip
Copy it to your /sdcard. Then continue with adb shell:
Code:
$ su
# cd /system/xbin
Mount the system partition read/write:
Code:
# mount -o remount,rw -t rfs /dev/block/st19 /system
Rename the original binary for later use (if something fails):
Code:
# mv su su-orig
Copy the binary to the xbin folder:
Code:
# busybox cp /sdcard/su ./su
Change the permissions:
Code:
# chmod 6755 su
Mount the system partition read-only and exit:
Code:
# mount -o remount,ro -t rfs /dev/block/st19 /system
# exit
$ exit
Now install the Superuser App from the Playstore - and have fun! Do *NOT* Update the su binary from within the Superuser App or it will be overwritten with a non-working version!
Cheers, Volker
Click to expand...
Click to collapse
OMG!!! IT WORKED!!!
MANY THANKS!!!
Now have full root privileges woot!!! Tested with Titanium backup and ES File explorer they accepted root and got permission prompts :highfive:
I will update the OP with your instructions, they worked beautifully, MANY THANKS AGAIN!!!
Btw, Do you have any idea on which custom recovery may work and if the bootloader can be unlocked? (if it is locked, I can't see anything when booting into fastboot mode and Windows doesn't recognize the tablet at that moment, only shows unknown device)
I want to make a backup of the stock rom and start testing CM builds on it.
Temil2006 said:
umm, instead of using custom drivers, why not simply use the newest android Drivers? confirmed they work and device is reconized correctly, as long as you "install official droid drivers" then change the "adb_usb.ini" to only include 0x10D6 device, same as your last steps, but using official drivers, instead of custom ones. Maybe it has something to do with the failures?
Click to expand...
Click to collapse
The original Android drivers never worked for me, used latest version 8.0 and the device was not recognized for some reason, only the modded drivers worked to recognize the ADB device. Btw, I'm using Windows 8.1 Pro and had to turn off driver signature to get the ADB drivers installed, maybe the issue was Win8.1 itself, but oh well, at least now we have a solution. :laugh:
fipsy said:
Do *NOT* Update the su binary from within the Superuser App or it will be overwritten with a non-working version!
Cheers, Volker
Click to expand...
Click to collapse
Update: After giving permissions with Superuser I went ahead and installed my SuperSU Pro license, gave it root rights (told it NOT to uninstall the other root app on prompt) and installed as a system app from within the app itself, reboot and voila! still fully rooted and binary updated (it replaced the other Superuser on reboot). So yeah, su binary updates are possible now :victory:
is there any custom recovery to install on this tablet?
Temil2006 said:
umm, instead of using custom drivers, why not simply use the newest android Drivers?
Click to expand...
Click to collapse
This also was my first attempt but it failed. So I went the same way as Omegadrive did: I identified the device as a clone of the "Ainol Novo 10 Hero" and searched for appropriate drivers. I found the same ones as Omegadrive did. And they seem to be the only ones that are working.
Temil2006 said:
one question though.. so are you saying that future updates of SU will not work? if we do this, should we also disable auto-updates? If the software does update, will it break our system.. or simply that we need to reload the SU over again, but the OS will open, just limited to "non-rooted" ? ??
Click to expand...
Click to collapse
I don't know if future binaries will work. When I manually updated the su-binary within the Superuser App it definitely didn't work anymore. Maybe because the su was exchanged with an older version (3.0.*). But Omegadrive said that updates are possible. So I don't know at the moment. Be careful anyway! Normally there is no reason for updating fully working binaries. The su binary is never updated automatically. So you don't have to deactivate any auto-updates.
Cheers, Volker
---------- Post added at 03:34 AM ---------- Previous post was at 03:04 AM ----------
Omegadrive said:
Btw, Do you have any idea on which custom recovery may work and if the bootloader can be unlocked?
Click to expand...
Click to collapse
The recovery mode is activated by pressing "Volume down -" and at the same time pressing the on/off key for about 3 seconds. Then releasing it while keep on holding down the "Volume -" until the recovery menu appears.
I think it will be possible to adapt the CWM Recovery. Perhaps we can investigate together on that!? Here the recovery file system table (for nandroid etc.). I just sent it to Ameer Dawood, the developer of "Online Nandroid Backup", so that he may integrate it into his App.
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /mnt/sdcard vfat /dev/block/actj (null) 0
2 /system ext4 /dev/block/actc (null) 0
3 /cache ext4 /dev/block/acte (null) 0
4 /data ext4 /dev/block/actd (null) 0
5 /data_bak vfat /dev/block/actf (null) 0
6 /boot vfat /dev/block/actb (null) 0
7 /recovery vfat /dev/block/acta (null) 0
8 /misc emmc /dev/block/actb (null) 0
9 /mnt/sd-ext vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 0
Oh nice, thanks for the help, I'm no programmer, just a tinkerer, I'm willing to test anything you throw this way lol
My main priority right now is to make a backup of the current rom and then look for a way to repartition the /data cause 1Gb for apps is way too low, specially when there are 13Gb free on /sdcard, as want to make it 4Gb for /data and rest internal. I'm assuming I have to install custom recovery for that, or can ir be done right now from ADB?
Sent from my HSG1279 using Tapatalk
If you want to store parts of the filesystem (like /data/app, /data/app-private, /data/dalvik-cache and libs) to the sd-card you probably will have to install a custom rom like cyanogenmod which supports additional partitions / filesystems on the sd-card (like ext2).
But you're right. The first thing to do before making any experiments is to make a full backup (nandroid) and be able to restore it from a recovery. So we first should investigate on that...
I just installed the CWM recovery for the Ainol Novo 10 Hero 2 for testing. The device started into the CWM recovery screen but then failed to mount some folders. The menu was working but most features were not functional. This means that the HSG1279 is *not* fully compatible with the Ainol Hero 2.
So we have to find another solution. I suppose it will be quite a lot of work to adapt the CWM recovery to this device...
This thread is made in an effort to root the ZTE Grand X 4 (Z957). At this point I've made some progress by using the Dirty Cow exploit to access a root shell via ADB, but have been unable to install su to the system partition.
Notes: stock rom, no custom recovery.
Exploit method:
Follow the instructions posted by Arinerron on GitHub regarding CVE-2016-5195 (under 10 posts, cannot share direct link)
When successful you will see "[email protected]:/ #" as your shell prompt, however the session will hang after any command. That said, /system/run-as is still updated allowing you to do the following:
$ adb shell
[email protected]:/ $ run-as
uid run-as 2000
uid 0
0 u:r:runas:s0
context 0 u:r:shell:s0
[email protected]:/ # id
uid=0(root) gid=0(root) groups=0(root),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0
you have access to the android system as root within this shell, but this is where I'm getting stuck. I'm not able to find a way to mount the system partition as read/write, and as such unable to install su. Also note that you will need to run the exploit again anytime you reboot the device. I have tried the following methods:
$ adb shell cp /sdcard/Download/su /system/bin/su
cp: /system/bin/su: Read-only file system
[email protected]:/ # mount -o rw,remount /system
mount: Permission denied
adb reboot disemmcwp
#still unable to remount the system partition
At this point I'll share what I've been able to do so far and see if anyone else has ideas for a next step.
Have you figured out how to root the z957.
This worked on my ZTE GrandX Max Plus to permanently disable the write protection on the system partition.
Good luck!!
reboot disemmcwp
If you ever want to re-enable being blocked from mounting system rw:
reboot emmcwpenab
Any luck on this root? I am looking to buy a phone on Cricket, but I need one that I can root.
Bump? Would love to see root here!
Bump, I've tried but I also get stuck on the same three methods:
$ adb shell cp /sdcard/Download/su /system/bin/su
cp: /system/bin/su: Read-only file system
[email protected]:/ # mount -o rw,remount /system
mount: Permission denied
adb reboot disemmcwp
#still unable to remount the system partition
Grand X 4
has anyone successfully rooted the grand x ?!
Thought I would post an update: Still no success on my end.
"Rooting" is easy, but breaking out of the selinux context to do anything is hard. ie. I expanded on timwr/CVE-2016-5195 by trying to use vikiroot to break out of the u:r:shell:s0 context. To do this adb push the vikiroot exploit to /data/local/tmp and then use the timwr method to run that exploit as root:
[email protected]:/ # /data/local/tmp/exploit
Unfortunately I could only get the reverse shell to work as a glorified echo. If anyone knows where I could find some c++ code for running a shell in android for me to work off of I'm willing to see how much further I can get in that direction.
As disemmcwp doesn't work I'm wondering if ZTE found a different way to lock down the system partition? Interestingly there is an OEM-specific settings button that is greyed out (find it at *#*#4636#*#*).
I'm running firmware from Wind/Freedom Mobile so I can access the bootloader and unlock it, but I can't install SU or anything from stock. Additionally, there is no TWRP released for this phone yet. I have no idea where to find the board config files for this phone. Without a custom bootloader I'm not sure how to make permanent changes to the rom at this point.
Thanks for your work on this. Stock Rom is pretty clean, but root would be great on this.
I've tried many different ways to root this phone. For weeks, I've tried. Nothing. I personally think that there is no way to, not now at least.
Don't know if this will help but, I found that they lock the bootloader under the developer settings!
Has anyone tried a one click root application like KingoRoot ?
Or is this more for doing it on your own without a service like that?
Previously I had tried a series of one click solutions but I haven't found any that support this device yet. Typically they use the same exploits we've tried to use the hard way
After slacking for awhile I was finally able to poke around some of the internals of the phone in FTM mode using qualcomm developer tools. Lots of nifty things in the embedded file system and plenty of opportunities to flash new boot loaders and roms to the device for those of you who have a locked bootloader, but unfortunately I haven't been able to extract a copy of the stock rom or bootloaders. I'm still lacking the information I need to compile a new one for the phone.
Where I stand:
Can create a root shell, cannot remount system as read/write for permanent root in stock rom.
Can install new boot loader, no twrp or other found for this hardware.
Can compile new twrp, no boardconfig files (handy to avoid bricking your phone)
Can explore EFS and access chip via FTM, not sure how or if possible to download current rom / bootloader from here.
Happy for any tips on what to try next!
Can you tell me which tools you used? I looked at the Qualcomm site and there are plenty to choose from.
If you can get those tools off of the site maybe I'll message you about grabbing a few items on my Christmas list! QPST includes the tools necessary, and the tools to backup the 425 should you accidentally brick your phone (basically impossible to truly brick a qualcomm if you have the right tools). Archive.org has a copy, don't remember where to find the driver pack but you'll need that too (and a windows build).
Read through some notes on marshmellow and sounds like you have to remount system from recovery. I'm camping for the next month but will try talking to the TWRP team about porting a bootloader to the phone when I get back.
Let me know if you make any headway!
try this adb command and see if you get a qualcomm serial port after reboot
Code:
adb reboot edl
if that doesnt work try
Code:
adb reboot bootloader
then run the attached
How did you get into diag mode? Just do the temp root method and setprop sys.usb.config diag,adb?
https://freeandroidroot.com/root-zte-grand-x-4/
This page claims to have a root method but does it actually work? I've tried twice with no success.
How's everyone here? I also am awaiting root for this device. It really needs some shine on it's mid levelness. So here is my friend's zte warp 7 work for root. He also got some killer roms for the Huawei ascend XT. He does great work. I'm sure if he had a grand x 4 he could move this along. Just a suggestion. This man can this done. Just a suggestion for all of us. https://forum.xda-developers.com/showpost.php?p=72560392&postcount=246
---------- Post added at 11:31 PM ---------- Previous post was at 11:10 PM ----------
https://forum.xda-developers.com/member.php?u=7934375
Anyone root this phone yet?
Sent from my Z956 using XDA-Developers Legacy app