Related
like this!
i thought a purely ubuntu method would be helpful for those just starting out [like me] and the linux methods haven't been updated [to my knowledge].
1. charge your phone to at least 50%.
2. get adb.
BEARTARD said:
Install adb. Download it here: developer.android.com/sdk/index.html . adb is a little program distributed as part of the Android software development kit (SDK). Its job is to communicate with the phone from a shell (terminal). To install adb, I strongly suggest you copy the adb file from the tools directory into your system's /usr/local/bin directory. This way, it will always be in your path. If you don't intend to do development work on Android applications, feel free to delete the rest of the SDK after installing adb.
Click to expand...
Click to collapse
so, download that ^ . open it up and extract the adb file from the tools folder onto the desktop. now open up the terminal and type in:
gksu nautilus /usr/local/bin
drag the adb file in there and close nautilus.
3. pick a rom from the rom bible: forum.xda-developers.com/showthread.php?t=704567
i like the ota updated one from CR, the froyo ones were "too lacking" for me. although still awesome*
place the rom on your phone's sd card. don't unzip it. and remember where you put it.
4. download this 4shared.com/file/J6i52nwy/slideroot.html
make a folder somewhere [i use the desktop] and name it something, like "root". extract the downloaded files into that folder.
5. set the phone up to be rooted:
-unplug it from the computer if it is plugged in
-again, make sure it is charged to at least 50%
-settings > applications > development > USB debugging (check mark here)
-settings > connect to pc > charge only
-settings > wireless & networks > wifi unchecked (important)
-settings > sound & display > screen timeout > never
-now plug it back in
6. minimize all other windows.
open up a terminal and type:
cd
now drag the folder you extracted all the stuff from step 4 into the terminal window [faster than typing it all out ]. click the title bar of the terminal. press enter. don't close this terminal. we should now be inside the folder.
7. copy and paste these commands in order.
they make some time to complete, so be patient or risk KILLING YOUR PHONE TO DEATH. [also, i'm not sure which commands actually require sudo to run so i just included it in all of the commands, forgive my noobishness].
commands:
sudo adb devices
-to start it up and make sure your phone is recognized the first time, if not, try again:
sudo adb devices
sudo adb push exploid /sqlite_stmt_journals
sudo adb push flash_image /data/local
sudo adb push mtd0.img /data/local
sudo adb push update.zip /sdcard
sudo adb push esprimg.zip /sdcard/ESPRIMG.zip
-you might want to get a drink or say hi to some friends at this point; takes a while. just wait until it says it's done like the rest.
adb shell
cd /sqlite_stmt_journals
chmod 0755 exploid
./exploid
-at this time go to settings and turn wifi on and then back off before continuing
./exploid
-the password is : secretlol
you should now have a # instead of a $
cd /data/local
chmod 04755 *
/data/local/flash_image misc /data/local/mtd0.img
8. turn off the phone.
9. press and hold volume down and then power up; hold both buttons.
let go when see the 3 skateboarding androids.
10. wait until the bar on the side of the screen loads.
if you don't see the bar wait about 4 minutes and something should happen.
11. when it is finished, press volume up, when prompted, to apply the update.
wait some more!~
DON'T REBOOT when it is done.
12. DON'T REBOOT!
13. press volume down.
press volume down once to highlight recovery and select with the power/lock button to boot recovery.
on the recovery screen you will see a device with a red warning triangle.
hold volume up and power together for a second or so.
14. ignore the warning at the bottom.
press volume down and then power to select apply update.zip.
you will now be loaded into the clockwork recovery and will be able to flash the rom of your choosing from your sd card.
you can use your touchpad at the bottom now and select with it.
otherwise: volume butttons=navigation power/lock=select
15. do a backup of your phone with nandroid.
-pretty self explanatory > press backup >wait >??? >profit!
16. wipe the device.
this won't wipe your sd card though, so don't worry.
17.install a custom rom
scroll down and select "install zip from sd"
select choose "zip from sdcard"
find your rom and apply!!!
wait!!!!!!.....
reboot!
18. complain on the dev forums about how bad the roms are, how dead the phone is, and speculate about newer phones. also, make sure to start your own thread even if it is a question, general banter, or to post pictures .
/sarcasm
19. seriously don't do step 18.
>_O
20. update the radio if it is not the newest one.
forum.xda-developers.com/showthread.php?t=705064
sources/more info:
exploid method:
forum.xda-developers.com/showthread.php?t=754669
ubuntu set up:
forum.xda-developers.com/showthread.php?t=710056
rom bible:
forum.xda-developers.com/showthread.php?t=704567
go donate money to the active devs now.
Oh crap. I got quoted. Good job, man!
thanks! i didn't know how else to so eloquently explain adb, so i just quoted you. hopefully this will be of help to all three of those linux users out there on this forum!
It's kind of funny, I came on here to write a thread like this one. I noticed that there wasn't a single thread that combined the new root method with flashing the ENG build into one. You saved me some time.
I noticed that you don't have the part about updating to the newest Radio after the ENG build. Do the newer ROMs come with a Radio update in them?
@slughappy1: i reccomended updating to CR's OTA rom since going from stock to updated stock with root is the most logical step. therefore, a radio updatre is included.
to my knowledge, the nicer devs include the newer radio, other wise they make a mention of updating it. anyways, i'll include it in my tutorial for completeness sake. now if only i could figure out how to take non-blurry distance pictures with my slide >_>. sadly, i'll probably sell this off for a g2 =\.
Why sudo? I don't think adb need super user permission. Is it needed because you put it in /usr/local?
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
arifwn said:
Why sudo? I don't think adb need super user permission. Is it needed because you put it in /usr/local?
Click to expand...
Click to collapse
Some systems are setup incorrectly to handle giving users permission to write to the ADB device file when the phone is plugged in. The correct process is to fix the permissions on the dev file that udev creates. Here's a link to do that: http://forum.xda-developers.com/showpost.php?p=5300224&postcount=6.
Please ALWAYS refrain from using 'sudo' or 'su' unless you're ABSOLUTELY sure that it needs root and there's no (more) proper way to do it.
(On a side note, I'm always available to answer any simple or complicated Linux questions anyone may have. You can PM me to get my attention or GTalk: nbetcher at gmail dot com.)
Thanks for the post about not using sudo. It was a quick way to make sure users on various linux distros can get it to work without a whole bunch of rigmarole.
On another note about the udev rules mentioned, the "SYSFS{}" call is being deprecated and a revision will be needed soon.
So i tried to follow the intstruction but once i booted in recovery mode nothing happend
10. wait until the bar on the side of the screen loads.
if you don't see the bar wait about 4 minutes and something should happen.
this is the step where nothing i happening on my phone
huh!! no one cares to help me
You didn't give much information to learn where the problem might be. If you didn't get the loading bar on the side of the screen, your recovery didn't see the ESPRIMG.zip file in the root directory of your sd card. Mount it on the computer and see if it's there.
beartard said:
You didn't give much information to learn where the problem might be. If you didn't get the loading bar on the side of the screen, your recovery didn't see the ESPRIMG.zip file in the root directory of your sd card. Mount it on the computer and see if it's there.
Click to expand...
Click to collapse
Alright let me check if the sd card has ESPRIMG.zip. but i have a question no where in the instruction it says if i need to transfer the zip file to the sd card ?
Step number seven is one of the most important ones. Check those commands you pasted. Most of them copy files to various places on your phone.
The world's first ereader with a color Mirasol display is finally on the market, but unfortunately it's running a severely locked-down Android by the Korean bookstore chain Kyobo. The Kyobo ui is entirely in Korean, the browser blocks downloads, and the reader app is crap. In other words, it's basically useless to anyone outside of Korea. A few enterprising Americans have imported them and been extremely disappointed. Will someone please take a look at this device and see if it can be rooted or if something else can be done to make it of use to the rest of us?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Nate over at The Digital Reader has a firmware update that supposedly contains all of the installed apps. He is asking for someone to try and hack it. He has a download link for the firmware at The Digital Reader.
I also posted this as a question here on XDA:
http://forum.xda-developers.com/showthread.php?t=1432283
it is rooted since some time already.
files and instructions are in the following archive, but since instructions are in korean, i'll do a writeup below.
(argh! spambot won't allow this link, so you'll have to piece it together...)
www<dot>4shared<dot>com/zip/aLwRc7ZG/mirasol_rooting.html
edit: needed files are also in an attachment below
the gist is that you need to flash the boot partition via fastboot, setup root and busybox, and then modify secure->install_non_market_apps in settings.db.
you will need to have adb and fastboot from the android sdk working on your computer. There are many posts about this elsewhere, so i won't go into the details.
also, i only print filename without path, just find the corresponding file in the mentioned archive and modify the commands accordingly.
flash the boot partition via fastboot
first get your kyobo into fastboot mode (with usb cable attached) by pressing volume-down at bootup. timing here can be a bit finicky, but easiest seems to be to shut it down completely and then press just after pressing power.
issue a 'fastboot devices' on computer, if successful it should give you the response '???????????? fastboot' or similar. if empty or hangs, try again by rebooting the kyobo by pressing power with volume-up held (you can go into fastboot immediately after reboot by volume-down as expected).
when positive response above, you can flash by
Code:
fastboot flash boot boot.img
and then reboot by
Code:
fastboot reboot
edit: simplified fastboot instructions, thanks to smb_gaiden, whose button-poking-fu is strong.
setup root and busybox
with boot partition flashed you now have adb access, so let's use it. let the device boot as normal, and then issue the following.
Code:
adb push busybox /data/local/tmp
adb push fixsu.sh /data/local/tmp
adb push su /data/local/tmp
adb shell chmod 777 /data/local/tmp/busybox
adb shell chmod 777 /data/local/tmp/fixsu.sh
adb shell chmod 777 /data/local/tmp/su
adb shell /data/local/tmp/fixsu.sh
adb shell ln -s /data/local/tmp/busybox /system/xbin/busybox
after this, install some apk's from the archive
Code:
adb install superuser.apk
adb install blackmart.apk
fix non-market apps setting
only thing left is to change a setting to allow non-market apps to be installed. if you don't care about your current settings (locale, etc), you can just push the settings.db from the archive like so:
Code:
adb push settings.db /data/data/com.android.providers.settings/databases/
if you *do* care about your settings, you'll need to pull the settings.db, edit it in some sqlite db editor (set secure->install_non_market_apps to 1) and push the result.
that's it. all rooted. now you just need to install angry birds and yer' set ;-)
Adb doesn't seem to start properly on device
Hello.
I did succeed in flashing the bootloader via fastboot.
However when I boot device - I see adb on usb only for some initial seconds, and then it disappears.
For that matter my device already had December firmware on it.
Any ideas how to activate adb on device?
Thank you,
Leonid
it may be that persist.service.adb.enable is reset, stopping the adbd service. try flashing the attached boot image instead, see if that fixes it. it is the same as above, except that persist.service.adb.enable is ignored.
edit: i took a look at the december update, afaict it should pose no problem (very few changes in there).
Once these steps are done, how do you install google market?
Thanks.
edit: the original instructions were snafu, so i replaced them with something that should actually work.
getting android market running on the kyobo
needed files are in the attached archive.
install like so:
Code:
adb remount
adb push DrmProvider.apk /system/app
adb push MediaProvider.apk /system/app
adb push DownloadProvider.apk /system/app
adb push GoogleServicesFramework.apk /system/app
adb push Market-3.4.4.apk /system/app
adb push init.qcom.post_boot.sh /system/etc
adb push fix-shared-user.sh /data/local/tmp
adb shell chmod 777 /data/local/tmp/fix-shared-user.sh
adb shell /data/local/tmp/fix-shared-user.sh
wait for the reboot, find market in the menu, and off you go (with downloads this time ;-)
if downloads still do not work after this, try re-executing the last line. android periodically writes to the file we are modifying, which might clobber our changes if unlucky.
I am thinking about buying one of these because I have seen it on sale for 50% discount. However, the general reviews aren't too encouraging, so will rooting make any difference to overall performance?
fatboy1976 said:
I have seen it on sale for 50% discount.
Click to expand...
Click to collapse
where is that?
throwaway4096 said:
you'll need GoogleServicesFramework.apk and Market-3.4.4.apk from the following links:
http://androidmarketu.googlecode.com/files/GoogleServicesFramework.apk
http://forum.xda-developers.com/showthread.php?t=1391565
install like so:
Code:
adb remount
adb push GoogleServicesFramework.apk /system/app
adb push Market-3.4.4.apk /system/app
find Market in the menu and off you go.
Click to expand...
Click to collapse
I'm finding the market force closes when downloading an app.
May I seek help from someone who has rooted recently? I am finding it pretty difficult to get into fastboot. So some questions as I continue to play.
Which version is currently rootable? I bought mine this week and want to be sure it is still applicable with the method here.
Do I need a USB driver to work this hack? EDIT: Yes, found with a web search.
When do I press the volume keys? Immediately after power? Similar timing? When I see the flicker on the screen? When I see the logo? Before all that? EDIT: I did not need the volume up key to get into fastboot.
Thanks!
rooting for beginners
Some friends and i ordered the kyobo to solve our eye-problem (nystagm)
We still can´t figure out, how to root it.
Can you please give us some rooting instruktion vor beginners??
It would be so essential for us, as the kyobo is little worth without forgeign apps!
Thank you very much!
Joe
send2toonie said:
I'm finding the market force closes when downloading an app.
Click to expand...
Click to collapse
Hi, I am stuck with the same problem. Have tried many things?!
---------- Post added at 04:57 PM ---------- Previous post was at 04:32 PM ----------
smb_gaiden said:
May I seek help from someone who has rooted recently? I am finding it pretty difficult to get into fastboot. So some questions as I continue to play.
Which version is currently rootable? I bought mine this week and want to be sure it is still applicable with the method here.
Do I need a USB driver to work this hack? EDIT: Yes, found with a web search.
When do I press the volume keys? Immediately after power? Similar timing? When I see the flicker on the screen? When I see the logo? Before all that? EDIT: I did not need the volume up key to get into fastboot.
Thanks!
Click to expand...
Click to collapse
Hi, Managed to root my kyobo after about 8 h trying. I installed the firmware update on my kyobo, that is found on the web, as instructed from the SD card. Then I installed fastboot and adb on my computer (search for 'how to install fastboot and adb'), as I found instructions for that as well. To enter fastboot I kept Kyobos, volume down button for about 10 sec, when booting the device (kyobo connected to computer with USB) - nothing happens -> however on my computers command window (cmd), 'fastboot devices' command produces an answer with '? ..' as it should. The biggest issue I had was to get adb working. For this purpose I installed and removed a couple of USB drivers - I don't really know how I got it to work finally.
You can tell if you have succeeded installing a useful usb driver, if you enter the 'adb devices' command in the cmd window and it returns a device number. Then you are ready to go with the rest of the commands/instruction as seen in the insturction of this thread.
From the blackmart application I was able to install many useful applications - the Launcher application can replace the Kyobo "home" application, which is very useful.
I installed android market as well, but so far I have not been able to download and install applications. I think It might be a permission issue between kyobo software and the installed android market?
Hey Guys!
is there a way to root the kyobo via mikrosd?
thanks a lot
Joe
Hey Joe. I've seen you on this forum as well as The Digital Reader asking for help with the Kyobo rooting. I too am a beginner and I'm trying to build up the nerve to try it. Wish us both luck and I hope someone can share rooting-for-dummies with us.
@fatboy1976: rooting won't improve performance in itself. it makes the device better as you can install apps, but ofc the hardware is still the same.
@send2toonie: yes, sorry about that. it worked for me, but only thanks to other changes. it's hard to keep track :-/. i updated the original post with new instructions which should work properly.
@smb_gaiden: hah, excellent, i never tried that! original post updated.
@Joe84: it should be possible to root via microsd by creating an update.zip. i haven't gotten around to trying that yet, but maybe in future. for now this is as simple as it gets.
Kaarlos said:
Hi, I am stuck with the same problem. Have tried many things?!
---------- Post added at 04:57 PM ---------- Previous post was at 04:32 PM ----------
Hi, Managed to root my kyobo after about 8 h trying. I installed the firmware ...(updated -see above..) .., which is very useful.
I installed android market as well, but so far I have not been able to download and install applications. I think It might be a permission issue between kyobo software and the installed android market?
Click to expand...
Click to collapse
Jep! With the updated instuctions the Android Market now finally works!! Thanks! (Installed twice)
Kaarlos said:
Jep! With the updated instuctions the Android Market now finally works!! Thanks! (Installed twice)
Click to expand...
Click to collapse
Hi,
Could you post the OS/processor version and driver name that got adb working for you. If you can also remember the keys pressed to put the Kyobo in the correct boot mode for adb, that would be nice too.
I have also managed to load apps on my Kyobo but that is without having su, Superuser, adb and Android Market working. The above info would be helpful in fixing that. Holding the volume down fir 10 seconds after pressing power on puts the Kyobo into fastboot mode. Adb requires a different mode and set of key presses. This is because there is a menu of boot options being displayed which can't be seen on the Mirasol screen. I suspect this is because of display settings within the boot.img but that is only a guess on my behalf.
Since the phone is Japanese, it is hard to find information if there is a way to root the phone or information about it.
Can anyone direct me to the right path , google is not helping >_<
The typical "me too" reply
dharkness said:
Since the phone is Japanese, it is hard to find information if there is a way to root the phone or information about it.
Can anyone direct me to the right path , google is not helping >_<
Click to expand...
Click to collapse
As per subject, me too. Got this phone on the 1st of April, switched from iPhone thinking I was now free in the world of rooting and custom roms. Guess the joke was on me as there seems to be no support for modern Japanese phones.
Weird considering this is the country of the tech obsessed. Maybe I should learn Japanese, there must be local hackers
puckman said:
As per subject, me too. Got this phone on the 1st of April, switched from iPhone thinking I was now free in the world of rooting and custom roms. Guess the joke was on me as there seems to be no support for modern Japanese phones.
Weird considering this is the country of the tech obsessed. Maybe I should learn Japanese, there must be local hackers
Click to expand...
Click to collapse
2ch might have the answer, it is just in Japanese and I do not know what to search for. Sharp might be the motorola of Japan lockin their phones >_<
puckman said:
As per subject, me too. Got this phone on the 1st of April, switched from iPhone thinking I was now free in the world of rooting and custom roms. Guess the joke was on me as there seems to be no support for modern Japanese phones.
Weird considering this is the country of the tech obsessed. Maybe I should learn Japanese, there must be local hackers
Click to expand...
Click to collapse
http://ameblo.jp/mee-now/theme-10072066016.html
dharkness said:
http://ameblo.jp/mee-now/theme-10072066016.html
Click to expand...
Click to collapse
Yep, this link seems to list the instructions for rooting the 203SH. And there are pretty straightforward and easy, I think.
I don't speak Japanese, I use Google Translate, but I have already rooted a few Sharps (SoftBank and Docomo) and have studied the rooting methods so I am pretty sure I understand the instructions.
Here's what you need to do:
1. You need a 64-bit Windows 7.
2. The build version needs to be S0012, and Android version needs to be 4.1.2.
3. Install the Sharp ADB driver. Get it from here: https://sh-dev.sharp.co.jp/android/modules/driver_eng/
4. Obtain the following files/apps:
・su
・Superuser.apk
・busybox
・unlock_security_module (*** The value "1" will remove the MIYABI lock first and the the NAND lock. However, I can't make full sense of everything in the note so you'll probably need to research this on your own, or experiment.)
5. Turn on USB Debugging on the 203SH. Disable "sleep mode" (I haven't seen this setting before but it should be somewhere in the Settings > Development menu).
6. Using command prompt on your Windows PC, transfer the "unlock" program to the phone:
Code:
> adb push unlock_security_module /data/local/tmp/unlock_security_module
7. Execute the program:
Code:
> adb shell
$ cd /data/local/tmp
$ chmod 777 ./unlock_security_module
$ ./unlock_security_module 1
8. The above should unlock both MIYABI and NAND. You'll see various results being printed for about one minute before the entire operation completes. But this is the result you will be looking for:
Code:
Unlocked LSM.
Do setresuid...
OK.
9. The cursor should change from "$" to "#' which means you have root access.
10. And you will be able to push "su" and "busybox" to the /system folder, and install "Superuser.apk" as a system app (also push it to the /system/app folder).
11. More instructions are to follow (that's that the last note says).
MY ADVICE: Perform the above very carefully and do not forget that you might end up bricking your phone and the responsibility for this will be all yours. If you are not comfortable with executing shell commands (meaning you can understand what's going on), it's best not to try this.
If this method works, please post here. I will publish these instructions on my website.
I cant risk bricking my phone >_< already on my 2nd 203sh, i lost my first one and the deductable for a new phone is expensive >_<
cheeseus said:
Yep, this link seems to list the instructions for rooting the 203SH. And there are pretty straightforward and easy, I think.
I don't speak Japanese, I use Google Translate, but I have already rooted a few Sharps (SoftBank and Docomo) and have studied the rooting methods so I am pretty sure I understand the instructions.
Here's what you need to do:
1. You need a 64-bit Windows 7.
2. The build version needs to be S0012, and Android version needs to be 4.1.2.
3. Install the Sharp ADB driver. Get it from here: https://sh-dev.sharp.co.jp/android/modules/driver_eng/
4. Obtain the following files/apps:
・su
・Superuser.apk
・busybox
・unlock_security_module (*** The value "1" will remove the MIYABI lock first and the the NAND lock. However, I can't make full sense of everything in the note so you'll probably need to research this on your own, or experiment.)
5. Turn on USB Debugging on the 203SH. Disable "sleep mode" (I haven't seen this setting before but it should be somewhere in the Settings > Development menu).
6. Using command prompt on your Windows PC, transfer the "unlock" program to the phone:
Code:
> adb push unlock_security_module /data/local/tmp/unlock_security_module
7. Execute the program:
Code:
> adb shell
$ cd /data/local/tmp
$ chmod 777 ./unlock_security_module
$ ./unlock_security_module 1
8. The above should unlock both MIYABI and NAND. You'll see various results being printed for about one minute before the entire operation completes. But this is the result you will be looking for:
Code:
Unlocked LSM.
Do setresuid...
OK.
9. The cursor should change from "$" to "#' which means you have root access.
10. And you will be able to push "su" and "busybox" to the /system folder, and install "Superuser.apk" as a system app (also push it to the /system/app folder).
11. More instructions are to follow (that's that the last note says).
MY ADVICE: Perform the above very carefully and do not forget that you might end up bricking your phone and the responsibility for this will be all yours. If you are not comfortable with executing shell commands (meaning you can understand what's going on), it's best not to try this.
If this method works, please post here. I will publish these instructions on my website.
Click to expand...
Click to collapse
dharkness said:
I cant risk bricking my phone >_< already on my 2nd 203sh, i lost my first one and the deductable for a new phone is expensive >_<
Click to expand...
Click to collapse
I want to know. Can I use CWM on 203SH or not. I want to Hard reset phone. thank you.
last i check its only temp root
are you a Chinese too？ i got it from wp7bar in tieba
Sent from my SBM203SH using XDA Premium 4 mobile app
i can not execute chmod 777 ./unlock_security_module
It shows some error, how to proceed ?
Do you have rooting methods for Sharp Aquos 506sh?
Today, I finally have found where to post for newbies, so I post, thought 4 hours ago I posted on androidforums.
Here is very difficult to operate with this site, and to use this site for with android devices is quite impossible. Only in windows, and not every comfortable. Anyway, I see, that is the first university on the net
Click to expand...
Click to collapse
.
just enter in google: tablet h007 and you shall see the specification, cos I can`t post link now. If anyone has the backup for this model, it shall be about 560 MB. Let me know, not to trouble anyone.
The tablet was rooted by kingoroot, but as you know or not, kingoroot, offers root acces, as the 1 service started, when the device is on, but it does not provide general full root settings, as for example when we are in the recovery menu.
I used some kernel tuner application, and I did not make any backups at all. I edited the file with this application, called build.prop, where I change the attribute of user for superuser. In that way, I though, I could get permissions of full root, I did that, because, I could not see my system partition generally, only from total commander, I could see and do whatever I want. After, I rebooted, and the problem started.
I attach here, my device specifications: Which I watched, while I could use the device:
Android system recovery 3e with sw version: alps.kk1.mp1.v2.11. It is on the photo though but with the different name.
MS board: d95b
Mt6582 (Chip)
All the rest is on the photo
foto.lovestudio.biz/image.uploads/30-07-2015/original-9ec17e355b096718359535e5af42aa4c.png
I have windows vista 32bit 2 service pack.
MTKdroidTools, the application I tried, 4 different versions, 1, last, and 2 in the years, when my phone was produced. It does not read my phone, saying, it is not present. Though all 4 kind of drivers are installed, even adb device driver is installed and all is perfect, all is connected.
The only thing I can use in this mtkdroidtools is adb terminal. I enter there the following command: adv devices, which shows some number of device connected with sideload.
Something like that:
List of devices attached
01234565ABCDEFG recovery
but at the place of recovery, I have
List of devices attached
01234565ABCDEFG sideload
Then, after reading stack-exchange site, I understand, that now I can enter the system partition to get my build.prop file, to change superuser for user as it was before and to return in back to the device, and get my phone worked. But I can`t do that. Cos as I stated before, the device is rooted only by kingoroot, and I works only as the 1 st. service inside android operating system, but not in recovery menu.
So I cant use the following command to get it right. Cos when I enter any of them, but first of all, I enter: adb usb - it says: error: closed
You can then copy the file off the phone:
adb pull /system/build.prop c:\build.prop
You can now edit it in any text editor (recommend Notepad++ because it will preserve the Unix style line endings,) and then copy it back to the phone:
adb push c:\build.prop /system/build.prop
To work with adb terminal, of course I am in the recovery menu and I enter inside ADB SIdeload Application.
I know how to deal as you see, with this problem, but I can`t get to the file, to the system partition in the whole, cos as I understand, the phone is not rooted.
So guys, let`s see what happens next, I am looking forward to your suggestions.
lovestudio said:
.
just enter in google: tablet h007 and you shall see the specification, cos I can`t post link now. If anyone has the backup for this model, it shall be about 560 MB. Let me know, not to trouble anyone.
The tablet was rooted by kingoroot, but as you know or not, kingoroot, offers root acces, as the 1 service started, when the device is on, but it does not provide general full root settings, as for example when we are in the recovery menu.
I used some kernel tuner application, and I did not make any backups at all. I edited the file with this application, called build.prop, where I change the attribute of user for superuser. In that way, I though, I could get permissions of full root, I did that, because, I could not see my system partition generally, only from total commander, I could see and do whatever I want. After, I rebooted, and the problem started.
I attach here, my device specifications: Which I watched, while I could use the device:
Android system recovery 3e with sw version: alps.kk1.mp1.v2.11. It is on the photo though but with the different name.
MS board: d95b
Mt6582 (Chip)
All the rest is on the photo
foto.lovestudio.biz/image.uploads/30-07-2015/original-9ec17e355b096718359535e5af42aa4c.png
I have windows vista 32bit 2 service pack.
MTKdroidTools, the application I tried, 4 different versions, 1, last, and 2 in the years, when my phone was produced. It does not read my phone, saying, it is not present. Though all 4 kind of drivers are installed, even adb device driver is installed and all is perfect, all is connected.
The only thing I can use in this mtkdroidtools is adb terminal. I enter there the following command: adv devices, which shows some number of device connected with sideload.
Something like that:
List of devices attached
01234565ABCDEFG recovery
but at the place of recovery, I have
List of devices attached
01234565ABCDEFG sideload
Then, after reading stack-exchange site, I understand, that now I can enter the system partition to get my build.prop file, to change superuser for user as it was before and to return in back to the device, and get my phone worked. But I can`t do that. Cos as I stated before, the device is rooted only by kingoroot, and I works only as the 1 st. service inside android operating system, but not in recovery menu.
So I cant use the following command to get it right. Cos when I enter any of them, but first of all, I enter: adb usb - it says: error: closed
You can then copy the file off the phone:
adb pull /system/build.prop c:\build.prop
You can now edit it in any text editor (recommend Notepad++ because it will preserve the Unix style line endings,) and then copy it back to the phone:
adb push c:\build.prop /system/build.prop
To work with adb terminal, of course I am in the recovery menu and I enter inside ADB SIdeload Application.
I know how to deal as you see, with this problem, but I can`t get to the file, to the system partition in the whole, cos as I understand, the phone is not rooted.
So guys, let`s see what happens next, I am looking forward to your suggestions.
Click to expand...
Click to collapse
I am sorry, so no one knows, on 3 sites, no one knows. let me know, then I shall not check every hour this post. I t`s better to know, that nothing possible, that believe that smth. is possible. thanks.
After breaking the screen on my phone I spent the following months reading about how to extract data. It all comes down to enabling ADB debugging and having your computer authorised. Usually this can be done from recovery and you're good to go. However, if you have a broken phone that is fully stock, with ADB disabled and with no custom recovery support then your data is as good as bricked. Such was the case with me when I broke my rare Samsung G360G. However, my phone was supported by CF-AutoRoot by Chainfire, and this gave just the opening I needed to go full wide.
Prerequisites:
Your phone needs to be supported by CF-AutoRoot. Check on there and the new site linked for support of your phone. If it's not there then you will need to download a stock ROM and use the CF-AutoRoot site tool to generate a root package for you. But that is outside the scope of this tutorial. This procedure has only been tested on Samsung. Your phone should have a minimal working charge.
https://autoroot.chainfire.eu/
This tutorial is also based on Linux. It should be translatable to Windows and Cygwin. But for simplicity I'll just use the method I used on Linux. However, if using Odin like I do, you'll need Windows to finish it off.
Aside from this it assumes files in are named in a particular format with a certain file format.
Tutorial:
1. First you need to download a CF-AutoRoot package for your phone. Won't get far without it.
2. Open up a terminal in Linux. We need to download some depends so enter this command:
Code:
sudo apt-get install android-tools-adb android-tools-fsutils
3. We need to extract the archive contents out. Create a suitable folder inside your home folder to build the patch in and cd to it. This uses an example file named CF-AutoRoot-example.tar.md5. Substitute with your actual archive name. Like so.
Code:
mkdir cfar-adb
cd cfar-adb
tar -xf CF-AutoRoot-example.tar.md5
4. There should be a recovery.img and a cache.img.ext4 extracted out. We just need to modify the cache.img.ext4. But first we need to convert it to a workable format. From a sparse to a raw image.
Code:
simg2img cache.img.ext4 cache.raw.ext4
5. We need to mount the cache image
Code:
mkdir cache
sudo mount -t ext4 -o loop cache.raw.ext4 cache
6. The big one. Doing the mod. So now we need to modify the cfar cleanup script. We need to insert commands on the end to enable ADB and add the key to authorise the computer. The following will do just that in this fashion.
a)
You will need to load in the cfar-cleanup.sh file inside the cfroot folder from the cache point mounted. Locate the end and paste the following lines before the reboot and exit commands on the end. Don't save yet.
Code:
echo -n 'mtp,adb' > /data/property/persist.sys.usb.config
mount -o remount,rw /system
echo '' >> /system/build.prop
echo 'persist.service.adb.enable=1' >> /system/build.prop
echo 'persist.service.debuggable=1' >> /system/build.prop
echo 'persist.sys.usb.config=mtp,adb' >> /system/build.prop
chmod 644 /system/build.prop
mount -o remount,ro /system
mkdir -p /data/misc/adb/
echo '' >/data/misc/adb/adb_keys
chmod 640 /data/misc/adb/adb_keys
b)
Load up the ~/.android/adbkey.pub file in a text editor and copy the entire contents in the clipboard. Now back at the script locate that last echo command you pasted into it and set the cursor just after the first single quotation mark. Now paste the clipboard in! This will add your key in. Make sure it's only between the single quotes with no extra characters or line feeds. The lines will naturally split if they don't fit on screen. Otherwise it should be good to go.
c)
Okay now save the file. The above will enable ADB and authorise your computer on the main Android system after the rooting script has done it's work. Before it reboots normally.
7. We need to unmount the cache so it's ready for use.
Code:
sudo umount cache
8. We need to convert the raw image back into a sparse image.
Code:
img2simg cache.raw.ext4 cache.img.ext4
9. Okay were almost done. Now we repack the files into a new Odin archive. Choose a suitable new filename. Like I have done here with my example file.
Code:
tar -H ustar -c recovery.img cache.img.ext4 > cfar-adb.tar
md5sum -t cfar-adb.tar >> cfar-adb.tar
mv cfar-adb.tar cfar-adb.tar.md5
10. The final step! So now the new package is ready for use. We just to use Odin and flash it to the phone. Save the package to a USB stick if needed.
a)
Reboot into Windows. Or you can run it virtualised from Linux. But I prefer to use the real things when dealing with things of a delicate manner and working blindly. Unplug your phone from the computer if connected. Now load up Odin in admin mode.
b)
Just to make sure pull the battery from your phone. Give it a few seconds then put the battery back in and click the back cover on. Now hold down volume down, then home key, and finally hold down power. Wait for the vibration. Then release power after a few moments. Finally release the other keys. At this point press volume up briefly. You should have just put your phone blindly into download mode. I've done this numerous times.
c)
Plug your phone into your computer. After a moment you should see Odin respond with a device added. Usually the phone can vibrate also when it connects giving more positive signs. If nothing happens disconnect the phone from the computer and retry the last step again to put it into download mode. Took me a few tries before I could do it blindly. It helps if you have a working Samsung to test it out on so you can see what happens before you can only feel it.
d)
Now in Odin press the PDA (or AP) button. Select the cfar-adb.tar.md5 package you made up. If the package is fine it will pass the md5 test. Now press the Start button and watch it go! If all goes well it will upload recovery, cache, give you a pass and then the phone will reset. At this point it will be in the process of being rooted, enable ADB, then reboot. If something goes wrong then you may need to go back and check all the patched files. Then rebuild the package again. But be careful, if the ADB has been enabled in the build.prop file one time, you don't want to add it in again and create duplicates, no matter how keen. Once I had it added the only other major problem I encountered was using the correct adb key.
e)
Hopefully now your phone is rooted, has ADB enabled and is booting up normally. Give it a few minutes. You can even see signs of life in Odin with adds and removes on USB activity. Your phone should also vibrate at times. And making noises is also a good sign.
1.1. So I just cranked it up to eleven. Open a Linux terminal again and give it a test. With your phone plugged in.
Code:
adb devices
If all goes well then adb will find your phone as well as list your device as authorised. You can now open shell to the inside. USB debugging is now enabled.
Conclusion:
Well I hope this helps those who have their app data stuck under a broken screen. As long as it was to type in this tutorial It still took me less time to write this tutorial than to learn all that was needed and apply it to my phone. This ends here but for you it may be only the beginning. A next step would be a screen mirroring app which I think is a must have for visual feedback. And USB debugging opens up these possibilities. One thing to be careful of, in a related issue, is that just because you can use adb and the phone is also rooted doesn't mean it will all work at once. If you are tempted to "su" it in an adb shell and get right in there then SuperSU will ask for permission on a blank screen. As will also happen if you try to do an adb backup, it will ask for confirmation on screen. So just expect to work with USB debugging blindly unless you already have a screen mirroring app installed. If you don't have one installed that is your next step.
And on that note. Good luck!
Hi there,
Your tutorial on how to achieve this on Linux looks real neat and complete. Unfortunately, i'm on Windows and i would like to know if you would be able to rewrite this totorial for a Windows user?
I've been reading online for about a week and i've never saw such a complete guide to help newbies to ADB to be able to retrieve data on their locked broken devices.
Cheers!
Hi RaiM1986 and thanks for your kind words. Yes I wrote it so it would be useful to newbies and seasoned hackers alike. Plus I needed to write down some instructions in case I need to do it all again.
Looking at the tutorial it is a bit Linux-centric. I don't know how well it would translate to Windows. Though there would be Windows version of the tools used the main problem would be mounting the filesystem image and making modifications without corrupting it. Because of things like Linux file modes.
However the following tools may be of assistance.
ADB tools:
https://wiki.lineageos.org/adb_fastboot_guide.html
Cygwin provides Linux tools if needed:
http://www.cygwin.com
simg2img:
https://github.com/KinglyWayne/simg2img_win
For mounting the ext4 image:
https://www.osforensics.com/tools/mount-disk-images.html
img2simg and other tools:
https://forum.xda-developers.com/showpost.php?p=49235638&postcount=5
For the ADB key it should be in %USERPOFILE%\.android and other spots I've read of are C:\Windows\System32\config\systemprofile\.android
In case any of the above fails, since I haven't tested them, the easiest alternative might be to just download a Linux live CD, boot it and do the steps inside. Of course any work is lost when you shut it down. You could also boot it in VM program running on Windows.
Amazing guide, Hypexed! The amount of work you put in to figure this out is incredible.
However, I'm stuck on step 6c, where I'm supposed to save the cfar-cleanup.sh file. It's not letting me save it at all, either within the mount point or to another location, it says that I don't have permissions to save the file. I tried the 'sudo chown' to change ownership to try to edit the permissions, but that didn't work either with it still saying I can't have access to the file. Any ideas? There is probably a simple solution, but this is my first time really using Linux so I'm a noob. I'm using Ubuntu 18.04.1LTS installed, not live, dual-booted with Windows, if that's important to know
SpinningQyarks said:
Amazing guide, Hypexed! The amount of work you put in to figure this out is incredible.
Click to expand...
Click to collapse
Thank you for noticing. It really was the culmination of months of hacking and cracking. Not to mention research. I decided I had to write a guide so I could document what I did in case I needed to do it again. And of course if it helped anyone else.
However, I'm stuck on step 6c, where I'm supposed to save the cfar-cleanup.sh file. It's not letting me save it at all, either within the mount point or to another location, it says that I don't have permissions to save the file. I tried the 'sudo chown' to change ownership to try to edit the permissions, but that didn't work either with it still saying I can't have access to the file. Any ideas? There is probably a simple solution, but this is my first time really using Linux so I'm a noob. I'm using Ubuntu 18.04.1LTS installed, not live, dual-booted with Windows, if that's important to know
Click to expand...
Click to collapse
Sorry you got stuck. I can see some issues in my guide. Especially after trying to do 6c again. First I notice I didn't specify where to store all the folders. Somewhere in the home folder obviously but it looks like you sorted that out fine.
I have tested a working solution to the permissions problem. In fact two:
1. Locate cf folder in the cache mount point on the desktop and go into it. Now right click in the window to bring up the context menu and select "Open as Root". Open up the editor as before.
2.. In the terminal run the editor as root. For example:
sudo gedit cfar-cleanup.sh
I've tested this on Mint which is a "relation" of Ubuntu so should work the same.
Now the original permissions should be left intact. I checked and they didn't have the execute bit set which is unusual. It may help here to save your work on the file to a place you can save to in the meantime. So you don't get stuck again. And then unmount your cache mount point, extract the raw image again as per step 4 and remount as per step 5, if the permissions need restoring. They really should be as they are originally set in the image.
Then continue through to step 6 and beyond as you were.
Good luck!