Related
So I was randomly flying around on Google today, and I noticed that someone had claimed to root the Kobo Arc, and gave written instructions here -- http : // www . mobileread . com / forums / showthread.php?p=2584491 (Remove the spaces, XDA won't let me post an actual link, since I don't have 10 posts yet). After running through this myself, I went on the Google Play store and used root checker. Much to my surprise, it worked, and my device now has root access. I even tested with Root Explorer, and mounted the system partition as R/W, and I can move things in and out of it. I'm currently working on trying to get a custom ROM working, but I'm worried that I will cause a brick, since Cyanogen doesn't support the Arc. (yet...)
ThunderBird2678 said:
So I was randomly flying around on Google today, and I noticed that someone had claimed to root the Kobo Arc, and gave written instructions here -- http : // www . mobileread . com / forums / showthread.php?p=2584491 (Remove the spaces, XDA won't let me post an actual link, since I don't have 10 posts yet). After running through this myself, I went on the Google Play store and used root checker. Much to my surprise, it worked, and my device now has root access. I even tested with Root Explorer, and mounted the system partition as R/W, and I can move things in and out of it. I'm currently working on trying to get a custom ROM working, but I'm worried that I will cause a brick, since Cyanogen doesn't support the Arc. (yet...)
Click to expand...
Click to collapse
confirmed, was just going to post this but was beaten to it.
http://www.mobileread.com/forums/showthread.php?t=218928
ive attached the file but please go to that website and pay homage to whoever did this work...now to the next stop, a ROM
Device now has a working custom recovery see post 15
Sent from my Arc using xda app-developers app
dazza9075 said:
confirmed, was just going to post this but was beaten to it.
http://www.mobileread.com/forums/showthread.php?t=218928
In terms of a ROM do we not need a compatible boot loader that will allow unsigned ROMs?
ive attached the file but please go to that website and pay homage to whoever did this work...now to find a man about a ROM
Sent from my Arc using xda app-developers app
Click to expand...
Click to collapse
i have absolutely no idea what im doing but I think I have dumped 12 partitions using
dd if=/dev/block/mmcblk0p10 of=/sdcard/p10.img
is there anyone around that fancies a challenge? im in a position where bricking this thing isn't really much of a problem so if someones up for a challenge and wants to help im willing to lend myself and the device to this
Warning : Block of Text Ahead.
dazza9075 said:
confirmed, was just going to post this but was beaten to it.
In terms of a ROM do we not need a compatible boot loader that will allow unsigned ROMs?
ive attached the file but please go to that website and pay homage to whoever did this work...now to find a man about a ROM
Sent from my Arc using xda app-developers app
Click to expand...
Click to collapse
Haha. As soon as I found a thread called "root the Kobo Arc" on Google, I posted it here right away. Sorry if I deprived you of the satisfaction! *troll*
Joking aside, I'm not too sure about the bootloader. I think it's pretty locked down (since I put a nexus 7's cyanogenmod onto the data partition and rebooted. It tried to updated, but said validation failed, or something of that sort). I can't install any custom recoveries either, since I have no idea how to do it in the first place, and there's none made for the Arc.
Also, I analyzed the Arc with the "Droid Examiner" App from the play store (That is a really great app, just so you know), and found that it uses a board called "zeus". The funny thing, though, is that one of Sony's Xperia phones, also has a board called "Zeus", and there's Cyanogenmod for that (albiet not the latest version). However, these two devices have nothing in common. The closest thing to an Arc that has Cyanogenmod is the Nook HD/HD+, which uses the exact same chip (OMAP TI 4470).
If someone is smart enough (not me) to analyze the Cyanogenmod files for the Nook, and see how they work, that may lead into flashing the Arc.
Anyway, I'm resetting the Arc, since I'm having weird cases where the Arc would freeze after booting it from sleep mode, and I'd have to turn it off and on again. I think that was something else I did, since it happened before the root, but neh, I might as well try this all from factory default settings.
Sorry for the block of text, guys!
P.S. Using the stock Jelly Bean boot animation on the Arc looks amazing!:laugh:
Haha, its cool, like yourself I just happened to Google kobo arc root and for once my googe fu was up to the task and the root appeared
I've been looking at starting my own recovery mod branch but its no simple task by the looks of it, if their are similar devices we can use all their data and tweak it to ours which would help a lot!
Oh I think we have fast boot, I held vol down and pushed power on, it just sat at the kobo arc screen, I used the nexus 7 driver from the universal adb/fastboot driver I found on here and it connected up http://forum.xda-developers.com/showthread.php?t=2263822
I stumbled on some to good to be true program on Xda dev that apparently can root anything and unlock any bootloader once your in fastboot mode. I have tried that part and it said it was successful but i have no idea how to test this out yet, the program does a bunch of other stuff too, the adb stuff worked as did apk sending, and the rooting options knew i was rooted, it also has flashing functions, I'll be damed if I can find it now I'm at home though , I'll have another look.
I don't mind doing leg work but if someone can read the map it would be very helpful!
Edit, found it
http://forum.xda-developers.com/showthread.php?t=2399385
http://www.mediafire.com/?vwxpq62pa927s9c
Sent from my Arc using xda app-developers app
dazza9075 said:
Haha, its cool, like yourself I just happened to Google kobo arc root and for once my googe fu was up to the task and the root appeared
I've been looking at starting my own recovery mod branch but its no simple task by the looks of it, if their are similar devices we can use all their data and tweak it to ours which would help a lot!
Oh I think we have fast boot, I held vol down and pushed power on, it just sat at the kobo arc screen, I used the nexus 7 driver from the universal adb/fastboot driver I found on here and it connected up http://forum.xda-developers.com/showthread.php?t=2263822
I stumbled on some to good to be true program on Xda dev that apparently can root anything and unlock any bootloader once your in fastboot mode. I have tried that part and it said it was successful but i have no idea how to test this out yet, the program does a bunch of other stuff too, the adb stuff worked as did apk sending, and the rooting options knew i was rooted, it also has flashing functions, I'll be damed if I can find it now I'm at home though , I'll have another look.
I don't mind doing leg work but if someone can read the map it would be very helpful!
Edit, found it
http://forum.xda-developers.com/showthread.php?t=2399385
http://www.mediafire.com/?vwxpq62pa927s9c
Sent from my Arc using xda app-developers app
Click to expand...
Click to collapse
Um... Okay. I've installed the drivers (I think I installed them correctly), and I booted my device using "volume down + power". I have it connected to my System, but whenever I try to use one of the options in the Android Root Toolkit, it tells me it's waiting for the device. I don't know what I did wrong, but something's clearly not working.
As far as the recovery goes, I think that looking at the Nook Tablet from TWRP would work quite nicely. It runs on a similar processor ( I believe it's a OMAP TI 4430 ), and it seems to be quite similar in specs to the Arc. If only I was a bit better at programming...
ThunderBird2678 said:
Um... Okay. I've installed the drivers (I think I installed them correctly), and I booted my device using "volume down + power". I have it connected to my System, but whenever I try to use one of the options in the Android Root Toolkit, it tells me it's waiting for the device. I don't know what I did wrong, but something's clearly not working.
As far as the recovery goes, I think that looking at the Nook Tablet from TWRP would work quite nicely. It runs on a similar processor ( I believe it's a OMAP TI 4430 ), and it seems to be quite similar in specs to the Arc. If only I was a bit better at programming...
Click to expand...
Click to collapse
im usig the generic android adb driver and the bootloader driver for fast boot
im dumped all partitions and mapped them all out, see below for file system details
But again I'm blindly stabbing in the dark and most tutorials are a bit lacking in depth or not relevant to the kobo :/
Sent from my Arc using xda app-developers app
127|[email protected]:/ # blkid
/dev/block/dm-2: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/dm-1: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/dm-0: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p12: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p11: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p10: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p4: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
[email protected]:/ #
Okay, so I can't even push apps to the Arc using ADB. I think you have to boot into recovery (power + volume up). I don't know how to use the terminal at all (I'm lost, I know D: ), so I don't have that installed on the Arc. I remember being able to do ADB even with my Sony Reader (First gen, PRST1), so I'm not sure why the Arc isn't quite working. I have both drivers installed, BTW.
As for the recovery, I can't even find a method to flash it. I'm still trying everything I can, though. :\
Sent from my Arc using xda app-developers app
ive mapped out the following partitions and any info ive found about each of them, im not in a position to help at the moment, got a big day at work tomorrow, as mentioned above ive used several tools,
SuperSU,
ROM toolbox pro
busybox
remount
Below is a list of all the available partition names and numbers
/dev/block/mmcblk0p1 xloader
/dev/block/platform/omap/omap_hsmmc.1/by-name/xloader
348KB
/dev/block/mmcblk0p2 bootloader
/dev/block/platform/omap/omap_hsmmc.1/by-name/bootloader
1.50MB
/dev/block/mmcblk0p3 cypto
/dev/block/platform/omap/omap_hsmmc.1/by-name/crypto
Completely empty
64KB partition size
/dev/block/mmcblk0p4 EFS
Mounted as /FACTORY
/dev/block/mmcblk0p4:UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/efs /factory ext4 ro,relatime,barrier=1,data=ordered 0 0
20MB
/dev/block/mmcblk0p5 misc
/dev/block/platform/omap/omap_hsmmc.1/by-name/misc
Completely empty
128KB partition size
/dev/block/mmcblk0p6 Bootlogo
/dev/block/platform/omap/omap_hsmmc.1/by-name/bootlogo
Contains kobo arc picture
4MB partition size
/dev/block/mmcblk0p7 Logos
/dev/block/platform/omap/omap_hsmmc.1/by-name/logos
contains the battery charge logo
28MB partition size
/dev/block/mmcblk0p8 recovery
/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
data contains a GZ file, when decompressed we get a 8.5MB file of unknown type, exact same as in boot
5MB of data
16MB partition size
/dev/block/mmcblk0p9 boot
/dev/block/platform/omap/omap_hsmmc.1/by-name/boot
data contains a GZ file, when decompressed we get a 8.5MB file of unknown type, exact same as n recovery
4.5MB of data
8MB partition size
/dev/block/mmcblk0p10 CACHE
Mounted as /CACHE
/dev/block/mmcblk0p10: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/cache /cache ext4
rw,nosuid,nodev,noatime,errors=panic,barrier=1,nom blk_io_submit,data=ordered 0
0
768MB partition size
/dev/block/mmcblk0p11 SYSTEM
Mounted as /SYSTEM
/dev/block/mmcblk0p11: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/system /system ext4
rw,relatime,barrier=1,data=ordered 0 0
910MB partition size
/dev/block/mmcblk0p12 USERDATA
Mounted as /DATA
/dev/block/mmcblk0p12: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/userdata /data ext4
rw,nosuid,nodev,noatime,errors=panic,barrier=1,nom blk_io_submit,data=ordered 0
0
12GB partition size
Watching with interest. The root works. No frills CPU installed and working. There may be hope for this thing yet:good:
Moved to new thread and more appropriate forum - keep up the good work guys
im not sure that's going to work you know, ive had some permission errors with adb which suggests the root isn't full, terminal on the device works fine, but adb just has some problems, adb shell and the su seems to fix them.
http://www.gadgetsdna.com/android-terminal-adb-shell-command-list/1168/
http://www.addictivetips.com/android/make-nandroid-backups-on-android-without-booting-into-recovery/
im busy today but ive found these useful
i think Clockwork Recovery should be our focus at this point or if you have dumped your partitions(?) attempt to construct a rom for later use
or this should work too
Install any Custom Recovery with flash_image:
Just like the previous method, this method also requires following advanced steps and is not recommended if the first method is working for you. flash_image is a tool for Android devices that lets you rewrite your phone’s system partitions with partition image files and installing it to your device requires ADB. If you don’t already have ADB installed, check out our guide on installing ADB. Once you have ADB installed, flash the custom recovery image as follows:
WARNING: It is very important that the recovery image that you use in this method is compatible with your device. Else it will not work and flashing it could possibly brick your device.
Download flash_image and extract it from the zip file to a location on your computer. We extracted it to the main C drive (not in any folder) and will use that in the next steps.
Copy the recovery image for your phone to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
Enable USB debugging mode on your device from Menu > Settings > Applications > Development.
Connect your device to your computer via USB.
Open a Command Prompt window on your computer and enter the following commands: adb push c:\flash_image /sdcard/adb push c:\recovery.img /sdcard/adb shellsumount -o remount, rw /systemcp /sdcard/flash_image /system/bincd /system/binchmod 777 flash_imageflash_image recovery /sdcard/recovery.imgThis will first transfer flash_image and recovery.img to your phone. Then it will copy flash_image to the /system/bin folder of your Android device and make it executable. Finally, it will flash the custom recovery image to your device using flash_image.
Note that we used c:\flash_image and c:\recovery.img in the first two lines as we had these files extracted at the root of our C drive. If you extracted the files elsewhere, use the appropriate paths and if your recovery image has a different name, use the appropriate name.
Reboot your device once the process is finished and you’re done. You may exit adb and the Command Prompt window on your computer by entering ‘exit’ thrice.
dazza9075 said:
im not sure that's going to work you know, ive had some permission errors with adb which suggests the root isn't full, terminal on the device works fine, but adb just has some problems, adb shell and the su seems to fix them.
http://www.gadgetsdna.com/android-terminal-adb-shell-command-list/1168/
http://www.addictivetips.com/android/make-nandroid-backups-on-android-without-booting-into-recovery/
im busy today but ive found these useful
i think Clockwork Recovery should be our focus at this point or if you have dumped your partitions(?) attempt to construct a rom for later use
or this should work too
Install any Custom Recovery with flash_image:
Just like the previous method, this method also requires following advanced steps and is not recommended if the first method is working for you. flash_image is a tool for Android devices that lets you rewrite your phone’s system partitions with partition image files and installing it to your device requires ADB. If you don’t already have ADB installed, check out our guide on installing ADB. Once you have ADB installed, flash the custom recovery image as follows:
WARNING: It is very important that the recovery image that you use in this method is compatible with your device. Else it will not work and flashing it could possibly brick your device.
Download flash_image and extract it from the zip file to a location on your computer. We extracted it to the main C drive (not in any folder) and will use that in the next steps.
Copy the recovery image for your phone to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
Enable USB debugging mode on your device from Menu > Settings > Applications > Development.
Connect your device to your computer via USB.
Open a Command Prompt window on your computer and enter the following commands: adb push c:\flash_image /sdcard/adb push c:\recovery.img /sdcard/adb shellsumount -o remount, rw /systemcp /sdcard/flash_image /system/bincd /system/binchmod 777 flash_imageflash_image recovery /sdcard/recovery.imgThis will first transfer flash_image and recovery.img to your phone. Then it will copy flash_image to the /system/bin folder of your Android device and make it executable. Finally, it will flash the custom recovery image to your device using flash_image.
Note that we used c:\flash_image and c:\recovery.img in the first two lines as we had these files extracted at the root of our C drive. If you extracted the files elsewhere, use the appropriate paths and if your recovery image has a different name, use the appropriate name.
Reboot your device once the process is finished and you’re done. You may exit adb and the Command Prompt window on your computer by entering ‘exit’ thrice.
Click to expand...
Click to collapse
I've already tried that recovery method (I spent about two hours just googling), and it doesn't work with the Arc. The ADB won't let me push the image over.
As for Cyanogenmod, I tried something yesterday. A person on the Mobileread forums (apparently a Kobo employee) put out an update.zip file for the Kobo Arc. The file was quite old, and it's really just the 4.1.1 update that (I hope) we're all running. He said that as long as you put it on the root of the data partition, the Arc will flash it immediately. When I tried taking a Nexus 7's Cyanogenmod file and sticking it in the same place, the Arc started flashing it, but then just said there was an error with the update. So I personally think that you do require a properly signed ROM.
However, if you open up Kobo's update.zip using Winrar, a sidebar pops up that says "signed by SignApk". I don't know too much about this, but couldn't we use this "signapk" to sign our own ROMS and flash them?
Just a thought.
ThunderBird2678 said:
As for Cyanogenmod, I tried something yesterday. A person on the Mobileread forums (apparently a Kobo employee) put out an update.zip file for the Kobo Arc. The file was quite old, and it's really just the 4.1.1 update that (I hope) we're all running. He said that as long as you put it on the root of the data partition, the Arc will flash it immediately. When I tried taking a Nexus 7's Cyanogenmod file and sticking it in the same place, the Arc started flashing it, but then just said there was an error with the update. So I personally think that you do require a properly signed ROM.
However, if you open up Kobo's update.zip using Winrar, a sidebar pops up that says "signed by SignApk". I don't know too much about this, but couldn't we use this "signapk" to sign our own ROMS and flash them?
Just a thought.
Click to expand...
Click to collapse
I think there is a problem with the setup, I just flashed a CW recovery image and it worked, or didn't rather! but the concept did, transferred, flashed using adb, I had to replace it though as it was totally borked and kept restarting, apparently the touch based recovery methods can be like that, ill have some good time tomorrow night (UK time) if your about, and ill keep at it tonight if I get a chance!
copy recovery to adb location
adb push recovery.img /sdcard/
adb shell
su
cat /sdcard/recovery.img > /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
exit adb shell and type
adb reboot recovery
fixed it by holding power button and vol down to boot to fastboot recovery
then ran
fastboot flash recovery inputrecovery.img
inputrecovery being my original recovery file taken from partition 8!
ive updated the partition map on the post above with my progress, but it looks like we can flash to them my name so its probably less relevant now
oh ive ditched the drivers I was using and reinstalled the drivers from the official SDK, generic android adb for within android and android bootloader for fastboot
EDIT
Yaaas!! recovery replaced
ok, deleting or renaming /etc/install-recover.sh appears to have stopped custom recovery being changed back to stock after reboot, I used the recovery builder to make a build from partition 8, which it did without error, flashed using the above commands.
Still don't know what im doing though, but progress is progress
ill post a link to the custom recovery ive made soon, we need to make up some fstab file listing all the mounts etc, i tried one but it must be borked as recovery couldnt see anything
ok i have a working recovery http://jenkins.cyanogenmod.com/job/recovery/35325/artifact/
its not quite done, i need to mount the sdcard, its physical location is mounted, ie /data, but its virtual mount isn't /storage/sdcard
I have asked for some help so hopefully someone can help be on this, I think it needs to be symlinked
im going to need some help soon, so if your reading this with a kobo arc, I need you! im needing a hand folks! if your stuck getting this far let me know and we can PM to get it working
oh and recovery is also now persistant by deleting or renaming /etc/install-recover.sh"
Sorted folks!
I have made a stable and thus far, a working custom recovery.
its mounting everything and backing up / restoring works as it should, unless anyone can find any issues I consider this step in building a complete ROM completed,
you must have root, download arctic.apk and install on your tablet, you will need to enable unknown sources In dev options first
you must have android and java sdk also installed, you will need to add the google usb drivers in the android sdk, you will find them in the "extras"
Enable usb debug on the arc and install the generic google adb usb drivers
Delete or rename /etc/install-recover.sh this will make the custom recovery persistent
Copy the recovery.img to the SDCard, either by using drag and drop in windows ( to root of "internal storage") or by adb push, if you use adb push then remember to copy recovery.img to the same folder as adb
adb push recovery.img /sdcard/
The next job is to open up a command window and navigate to adb folder, type the following exactly, even better copy and paste them!
adb shell
su
cat /sdcard/recovery.img > /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
exit adb shell (ctrl+C) and type
adb reboot recovery
and bobs your uncle, one happy new recovery
Thanks for your hard work. Everything works quite well.
Sent from my Arc using Tapatalk 4
cancuck said:
Thanks for your hard work. Everything works quite well.
Sent from my Arc using Tapatalk 4
Click to expand...
Click to collapse
that's the easy bit, I have a feeling I need to make a couple of changes to the recovery.img but noting major, just a couple of other mounts I may have missed
I probably would like some help with the next bit however.
im just trying to build a development platform, I have a loathing for Linux as a desktop so will need to re educate myself without throwing my laptop out of the window, after that "challenge" the ROM should be easy
Well, I've just done it, and it works. Everything seems to be in order for the time being. I'm going to muck around with the new capabilities, and see what I can do.
<rant> I am annoyed at how many Windows users there are lurking here -- I mean, you can't even develop Android with Windows!!! Why is everything I find Windows oriented with no Linux option? </rant>
Here is the one click root zip with a (less verbose) Linux sh script. To quote the other thread,
Credit goes to the creator of the Zenfone 2 installer: @29y6145 Thread
You need ADB and fastboot installed first. Your distro has it, Google it.
Just unzip, and run:
Code:
chmod +x root.sh
./root.sh
And that's literally it. Thanks to the other people who found the files and wrote the commands
Download here: https://steelcowboy.me/zenfone_root.zip
hello..may explain further on how to do this method? is it terminal on the phone or on linux or on the windows (cmd)? and where's the zip file?
Not a newbie tutorial at all. You might want to appropriately title this or add instructions to make it newbie friendly.
cangcan said:
hello..may explain further on how to do this method? is it terminal on the phone or on linux or on the windows (cmd)? and where's the zip file?
Click to expand...
Click to collapse
It's a Linux sh script, so you run it in the Linux terminal. It's the same directions as the other tools, just for Linux
Jhdoubleoseven said:
<rant> I am annoyed at how many Windows users there are lurking here -- I mean, you can't even develop Android with Windows!!! Why is everything I find Windows oriented with no Linux option? </rant>
Here is the one click root zip with a (less verbose) Linux sh script. To quote the other thread,
Credit goes to the creator of the Zenfone 2 installer: @29y6145 Thread
You need ADB and fastboot installed first. Your distro has it, Google it.
Just unzip, and run:
Code:
chmod +x root.sh
./root.sh
And that's literally it. Thanks to the other people who found the files and wrote the commands
Download here: https://steelcowboy.me/zenfone_root.zip
Click to expand...
Click to collapse
I'm stuck in "waiting for devices" but at the start when i check my adb devices, my phone is there.
what's wrong ?
AceHa92 said:
I'm stuck in "waiting for devices" but at the start when i check my adb devices, my phone is there.
what's wrong ?
Click to expand...
Click to collapse
The phone takes a moment to reboot into fastboot mode, so the script has it wait for 30 seconds. Can you confirm that still nothing happens after 30 seconds? And the phone does boot into bootloader mode? If so, type
Code:
adb reboot bootloader
fastboot devices
into your terminal and see if it shows up. If it's not showing up you may have a problem with fastboot itself.
This seems to work (though the fastboot in Debian is too old, I needed to download a newer version) - but I end up with no Superuser app. What's wrong?
Worked perfectly for my memo pad 7 (176cx) Thank you so much!!
drbobb said:
This seems to work (though the fastboot in Debian is too old, I needed to download a newer version) - but I end up with no Superuser app. What's wrong?
Click to expand...
Click to collapse
Sorry for the late reply -- XDA didn't seem to notify me of a new post :/
Did you see all of the fastboot messages go by in both the terminal and the phone's screen? Did everything say "OKAY"? Did you try installing SuperSU from the Play Store to see if it rooted?
Jhdoubleoseven said:
Sorry for the late reply -- XDA didn't seem to notify me of a new post :/
Did you see all of the fastboot messages go by in both the terminal and the phone's screen? Did everything say "OKAY"? Did you try installing SuperSU from the Play Store to see if it rooted?
Click to expand...
Click to collapse
Yep, I think it was OKAY on all commands. I pulled in SuperSU from the store and all root functionality seems okay as well.
I don't understand much of what the script does, especially how
Code:
fastboot flash /system/bin/partlink supersu.tgz
is supposed to work - but then, I haven't looked too closely.
Awesome, really glad it worked out for you! And yeah, I'm not entirely sure -- usually gaining root is based on an exploit so I'd guess that it replaces system binaries with modified ones to allow root access, but haven't rooted many phones so not sure how it generally works. Especially
Code:
fastboot oem start_partitioning
Thanks for this. I tried other one clicks on my fedora 22 box and kept getting fastboot errors. This one worked flawlessly.
Interesting...
The approach is quite a bit different to the usual tethered TWRP suspects as the exploit tries to overwrite quite a few binaries. Naturally I had to try it on my ME572C and unfortunately it couldn't write a single one of those binaries.
therealprof said:
The approach is quite a bit different to the usual tethered TWRP suspects as the exploit tries to overwrite quite a few binaries. Naturally I had to try it on my ME572C and unfortunately it couldn't write a single one of those binaries.
Click to expand...
Click to collapse
That's not a Zenfone though my friend... this is only for Zenfone 2
Jhdoubleoseven said:
That's not a Zenfone though my friend... this is only for Zenfone 2
Click to expand...
Click to collapse
I know, but at some point I would hope that Asus gets an f'ing clue to develop things once and use that across multiple devices running similar hardware. It's already funny how my ME176C and ME572C run completely different Android implementations (one rootable, the other not) despite being somewhat similar.
It's probably a too obvious question, but as the tutorial is for newbies I feel allowed to do:
Do I need to have an unlocked bootloader to succeed in the rooting ? The reason for asking is that the script successfully restart the phone but then the fastboot commands don't work, I get stuck at "waiting for device".
Thanks.
Outdated security
Hey, your HTTPS certs are out of date. I added a temporary exception, then found the redirect failed. I think you server needs some updating...
Any chance of a mediafire or dropbox link?
I have a Eonon GA2114 (Android 4.4.4 RK3188 KLD) ROOTED car stereo.
I have searched this forum and cannot find what I am looking for so hoping someone can help or point me in the right direction?
I don't have many apps installed, but it seems as though the latest updates to Google, Maps, Sygic, etc. has resulted in an "insufficient storage" alert. I am quite happy with the stock ROM and don't really want to update to some of the custom ROMs that are available, but I do have a very technical background and have only ever owned Android devices.
Does anyone know or can point me towards instructions to change the system partition size? The system ships out with more than 8GB of internal space that I do not use and so would like to either repartition to a single large partition or reverse the size.
Thanks
I think you mean the /data (userdata) partition, and i'm pretty much in the same seat.
Got a brand new 16gig device that ships when a lousy 1gig of /data to store apps on, talk about drunken monkeys making the rom
got about 10 gig on the internal_sd that i'm guessing could be used instead.
I might try to remap that later, i guess you could root it and then either make a symblink there or look at the fstab and see if you could just remount it.
Could also flash Malaysk rom with gives you 2 gigs of userdata, not much more but alot better than 1gb
Yes, I mean the /data (userdata) partition and I checked, while driving to work, I actually have 13GB of userdata. I haven't used this space, but knew it was there when exploring the system when I first got it and for some reason I remembered 8GB. Regardless of the size, it's a waste of space if not utilised.
The system is already rooted.
I have considered Malaysk ROM, but I quite like the stock ROM, especially after installing my preferred launcher. I have already decreased the dpi from 240 to 180 so a lot better looking and a lot more screen space. Have got rid of bloat and so have a stock ROM to my liking.
These systems are well known for their mic troubles and I have taken this up with the manufacturer as I do work in the computer industry, but identifying electrical components and soldering is not something I am too confident with. The manufacturer did however, send me an updated update.img file. I've installed this and it made some improvement, but nothing so significant that I have actually started using the mic. It also has a new wallpaper and noticed that the default apps have been updated, but not sure how?
Anyway, if I don't like Malaysk I can revert back using the update.img file the manufacturer gave me, but 2GB still isn't enough. Hence, wanted to know how to do this myself.
Found this post: http://forum.xda-developers.com/gal...od-increase-partition-size-t3011162?nocache=1 by gsstudios
Obviously, connecting my system to a PC is not as easy and was wondering if anyone would know a bulletproof method of applying the instructions to my system given that it is a stereo with different hardware to a phone?
In the firmware we are using the partition we are discussing is determined by a "Parameter" file. These devices use a Rockchip processor.
In order to change this file I had to "Unpack" the IMG file, find the "Parameter" file and replace it with one from Malaysk firmware.
Then I was able to repack the firmware into a new IMG file, and flash my head unit. After that I did a Factory reset,
and the partition was reset to the new size. A Google search for Unpack Repack Rockchip Firmware will be helpful here if you are feeling adventurous,
or look around for DSA's factory rooted rom, He has included an expanded Parameter file in most of his builds.
I also found a way to choose where the apps get installed, google a bit for "adb shell pm set-install-location" I belive #1 would be the right choice here.
If that works to redirect everything to the big partition it would be a wonderfull solution.
Download a terminal for the rom and type in there instead of having to connect a computer to the HU etc etc.
Hey treech, thanks for the help. Sounds simple, so had a go over the weekend, I installed Terminal Emulator for Android by Jack Palevich and run the command "adb shell pm setInstallLocation2", which provided me with a long list of commands I could use and think the command executed successfully? Previously tried "adb shell pm setInstallLocation1", which produced an error stating device not found. Still getting the "insufficient storage" error so presume it has not worked, but will continue looking into this.
I would prefer rickthecabbie's solution, but in order to unpack the IMG file, I would need a Linux system (I have tried on Windows and couldn't do it). If all else fails, I'll dual-boot my PC or get a VM if that works? I would be really grateful if you can point me towards a tutorial/instructions if you know any or get the time, but appreciate your help as at least I've got somewhere to start my "Googling"
Wish I had done this. All I wanted was the larger partition, and going with malaysk opened up a whole new set of issues. For example, my single din unit has a separate led display that shows the radio station when the screen is closed. Since flashing Malaysk, it is stuck showing "Init" which is what it shows during bootup. I'm sure the stock rom had been modified by the OEM to update the display, and that's not present in the base Malaysk used. I will probably never have that display working again.
Sent from my A0001 using Tapatalk
lotherius said:
Wish I had done this. All I wanted was the larger partition, and going with malaysk opened up a whole new set of issues. For example, my single din unit has a separate led display that shows the radio station when the screen is closed. Since flashing Malaysk, it is stuck showing "Init" which is what it shows during bootup. I'm sure the stock rom had been modified by the OEM to update the display, and that's not present in the base Malaysk used. I will probably never have that display working again.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I asked the guys I bought the stereo from; if they had released an updated ROM or if they can provide me a download for the existing ROM. Their customer service so far, has been excellent; their English is not great and it can take a little extra time sending and waiting for messages, but they gave me a link.
At least, I know that if I mess things up, but haven't bricked it, I have got something to revert to.
You could try asking the seller/manufacturer for a link to the stock ROM?
rickthecabbie said:
In the firmware we are using the partition we are discussing is determined by a "Parameter" file. These devices use a Rockchip processor.
In order to change this file I had to "Unpack" the IMG file, find the "Parameter" file and replace it with one from Malaysk firmware.
Then I was able to repack the firmware into a new IMG file, and flash my head unit. After that I did a Factory reset,
and the partition was reset to the new size. A Google search for Unpack Repack Rockchip Firmware will be helpful here if you are feeling adventurous,
or look around for DSA's factory rooted rom, He has included an expanded Parameter file in most of his builds.
Click to expand...
Click to collapse
Do you know the name and location of the parameter file? And do you happen to still have the parameter file from Malaysk firware?
Thanks for the help.
tariqkhan.co.uk said:
Do you know the name and location of the parameter file? And do you happen to still have the parameter file from Malaysk firware?
Thanks for the help.
Click to expand...
Click to collapse
The Parameter file is simply called "parameter" .
It is located in the ROOT of the IMG file when I unpacked the IMG using "RK3066 IMG Mod Tool" I had to remame the IMG from update.img
to wendal.img and place it in the tool directory. After running the tool Unpack, the files from the IMG were located in the newly created Temp directory of the tool folder. I replaced the file "parameter' in Temp with the one from DSA's firmware which I unpacked with the same tool (in a different folder on my desktop, to prevent confusion). Then I ran the "Pack" function in the tool and it created a file called "update_new.img" this was the modified firmware I flashed to my head unit.
I will edit this post later to a step by step tutorial for those who might be confused.
Hey rickthecabbie, that would be awesome.
Do you have the parameter file by any chance?
I recently made a change to the screen density. I have an 800x600 system and you can only fit 2 rows of icons across the screen so changed the build.prop file to 180dpi and now it looks much like a normal tablet. Having restored the system after making this change; it restored with my changes to the build.prop file intact. I was thinking, could I possibly do the same? I can modify the parameter file using ES Explorer/Terminal and then restore the system, which should update the partitions?
Saves on all the packing and unpacking and mainly; installing dual-boot/debian on my Windows PC.
tariqkhan.co.uk said:
Hey treech, thanks for the help. Sounds simple, so had a go over the weekend, I installed Terminal Emulator for Android by Jack Palevich and run the command "adb shell pm setInstallLocation2", which provided me with a long list of commands I could use and think the command executed successfully? Previously tried "adb shell pm setInstallLocation1", which produced an error stating device not found. Still getting the "insufficient storage" error so presume it has not worked, but will continue looking into this.
Click to expand...
Click to collapse
Well, pretty sure you'll need a space between setInstallLocation and 0/1/2 or whatever you choose to test, haven't tried it myself yet due to lack of time.
treech said:
Well, pretty sure you'll need a space between setInstallLocation and 0/1/2 or whatever you choose to test, haven't tried it myself yet due to lack of time.
Click to expand...
Click to collapse
Yep, thought it would be something simple. Do you know of a command which would print which partition 0 and 1 and 2 is?
Don't really want it to set the install location to a partition that I wouldn't want it set to. Also, some apps are not movable so I don't think this would solve the issue right?
Not sure, you'll have to google it
And well best is to install a few bigger apps and see what happens i guess.
rickthecabbie said:
The Parameter file is simply called "parameter" .
It is located in the ROOT of the IMG file when I unpacked the IMG using "RK3066 IMG Mod Tool" I had to remame the IMG from update.img
to wendal.img and place it in the tool directory. After running the tool Unpack, the files from the IMG were located in the newly created Temp directory of the tool folder. I replaced the file "parameter' in Temp with the one from DSA's firmware which I unpacked with the same tool (in a different folder on my desktop, to prevent confusion). Then I ran the "Pack" function in the tool and it created a file called "update_new.img" this was the modified firmware I flashed to my head unit.
I will edit this post later to a step by step tutorial for those who might be confused.
Click to expand...
Click to collapse
I don't mean to bug you and do appreciate the advice so far, if you haven't got time to do the tutorial, do you know of a link to an existing tutorial?
Rick wrote up a superb step by step tutorial here:
http://forum.xda-developers.com/and...torage-fix-t3257827/post64037230#post64037230
jbleasdale said:
Rick wrote up a superb step by step tutorial here:
http://forum.xda-developers.com/and...torage-fix-t3257827/post64037230#post64037230
Click to expand...
Click to collapse
Thanks for the link.
Gave it a go and didn't work for me; I'm sure I've made a simple mistake somewhere although I tried twice.
As my system had already been wiped, I thought I would give DSA ROM a go and for anyone looking for a stock ROM, this is perfect. Any MODS included are a necessity in my opinion and some you will probably not even notice, but it has the 2GB system partition.
Is there a flashing bootlogo for MXPE 6.0 Custom Rom & Custom Kernel guide?
Screenshot below as to what I am running on my my phone. I am specically looking to replace the unlock bootloader warning bootlogo with something nice.
About Phone:
Hitti2 said:
Is there a flashing bootlogo for MXPE 6.0 Custom Rom & Custom Kernel guide?
Screenshot below as to what I am running on my my phone. I am specically looking to replace the unlock bootloader warning bootlogo with something nice.
About Phone:
Click to expand...
Click to collapse
This thread has what you need to get rid of the unlocked bootloader warning. Make sure you read carefully and get the marshmallow logo for your rom.
Here's a kernel tuning guide.
jason2678 said:
This thread has what you need to get rid of the unlocked bootloader warning. Make sure you read carefully and get the marshmallow logo for your rom.
Here's a kernel tuning guide.
Click to expand...
Click to collapse
It says its for
LPH23.116-18
Mine is
Hitti2 said:
It says its for
LPH23.116-18
Mine is
Click to expand...
Click to collapse
The one attached to the OP is for lollipop. You need the marshmallow one that Spasticdroid posted about a dozen pages in.
Gotya.
As if you hadnt known,I am new at this.
What can I use to get the location for the logo after downloading.
Is there like a copy url in es file explorer?
Then I can paste then write it down on paper.
Hitti2 said:
Gotya.
As if you hadnt known,I am new at this.
What can I use to get the location for the logo after downloading.
Is there like a copy url in es file explorer?
Then I can paste then write it down on paper.
Click to expand...
Click to collapse
The easiest thing to do would be to download it to a computer, unzip it, and use fastboot to flash logo.bin with the command in the OP of the logo thread.
Alternately you could probably use dd to flash it if you don't have access to a PC or just don't want to use one. I have not tested and would not recommend that.
Fastboot worked fine. It is far too easy to make a typo and trash your phone with dd; it isn't nicknamed disk destroyer for no reason. Assuming you download it to the default folder, unzip it there with a utility like es file explorer, and are the primary user of this device the command would look like this:
Code:
su
dd if=/data/media/0/Download/logo.bin of=/dev/block/mmcblk0p31
If you do go this route and get a command not found for dd, then you probably need to install busybox. Triple check all your inputs if you do this. Typos with dd can be nasty. I've modded plenty of devices this way, but just use fastboot when it is available. The syntax is easier with fastboot, and you don't have to worry about writing to the wrong block device since it handles them all by name.
Thanks a bunch. Be fire i proceed
Is there a way to backup the unlocked bootloader logo?
So if I ever need to replace it back.
Perferrably through fastboot. I've got a pc ready for adb and fastboot.
Hitti2 said:
Is there a way to backup the unlocked bootloader logo?
Click to expand...
Click to collapse
Essentially just reverse the arguments in the command I posted above.
Code:
su
dd if=/dev/block/mmcblk0p31 of=/data/media/0/Download/logo.img
That should leave you with an image of the logo partition in your /sdcard/Download folder.
jason2678 said:
Essentially just reverse the arguments in the command I posted above.
Code:
su
dd if=/dev/block/mmcblk0p31 of=/data/media/0/Download/logo.img
That should leave you with an image of the logo partition in your /sdcard/Download folder.
Click to expand...
Click to collapse
Do I have to use dd to backup the logo? Is there a cmd in fastboot or adb?
Thnx.
Hitti2 said:
Do I have to use dd to backup the logo? Is there a cmd in fastboot or adb?
Thnx.
Click to expand...
Click to collapse
You could use adb shell, but that just lets you use your computer keyboard instead of trying to type in a terminal app. The command to get a single partition remains the same.
There is an app called partitions backup & restore that can handle this without any command line use. Its available on the play store.
jason2678 said:
You could use adb shell, but that just lets you use your computer keyboard instead of trying to type in a terminal app. The command to get a single partition remains the same.
There is an app called partitions backup & restore that can handle this without any command line use. Its available on the play store.
Click to expand...
Click to collapse
Yea, I don't think I can use dd.
http://www.noah.org/wiki/Dd_-_Destroyer_of_Disks#Why_use_dd_instead_of_cp.3F
For linux. I am on a WIn7x64 computer.
And for Partitions Backup & Restore
one comment
Bricked. So it kinda works. It did keep my phone's efs/imei info. But upon reinstalling by phone was stuck in bootloop. I had to set my phone back to Android 4.0 which means some newer apps do not not work. & trying to reinstall different/newer android ROM is now impossible. I was barely able to get it back to working condition, but now slower than before. Unless you know how to reprogram the partitions, i would not mess with this app.
Click to expand...
Click to collapse
I think Ima leave the bootlogo alone.
Hitti2 said:
Yea, I don't think I can use dd.
http://www.noah.org/wiki/Dd_-_Destroyer_of_Disks#Why_use_dd_instead_of_cp.3F
For linux. I am on a WIn7x64 computer.
Click to expand...
Click to collapse
You're correct, dd is part of GNU coreutils, but you'll be able to use it even if you use adb shell from a windows computer. The dd binary resides on your phone (which is pretty much a linux environment, just android/linux instead of GNU/linux), not on the computer.
I don't think dd is there by default in a typical stock rom, but busybox adds the utilities stock android leaves out. I'm using busybox on rails from the play store with this phone.
I've been using linux for about 15 years, so have a comfortable, if uneasy, feeling for using dd. It is a powerful tool, but it is not fault tolerant and you usually have to run it as root to get the job done. Make a little typo or have an absent minded moment and reverse the if and of arguments and you can have a really bad day.
First, to clarify, the last time I rooted anything was a Galaxy S3 back in the day. I'm by no means an expert, I just figured I'd help out folks like me that haven't touched all these new tools, well, ever.
Just did this myself earlier today attempted to get Magisk root, but alas, I got stuck in a boot loop. Luckily I had muddled through getting the image first, otherwise I'd still be stuck in said boot loop. I figured I'd post this for anyone else trying to root these things just to make sure you have a backup you can trust (I generally don't trust rando images that folks post online). All of the instructions below are assuming you're on Windows 10 and using PowerShell just because that's the default these days. Without further adieu.
Download ADB/fastboot (on your Windows machine)
I downloaded adb/fastboot from google directly: https://developer.android.com/studio/releases/platform-tools
Just extract and browse to the platform-tools directory in Windows Explorer until you can see adb.exe and a bunch of other tools
Download the latest SP Flash Tool
I just grabbed it from here: https://spflashtools.com/
Please let me know if there's an "official" place to find SP Flash Tool, cause everything surrounding all the download sites seems a bit sus...
Enable USB Debugging (on the tablet)
Go to settings -> About tablet
Tap the Build number 10 times (until debugging mode unlocks)
Hit back and go to System
Click Advanced and then Developer Options
Enable USB Debugger
I also enabled OEM unlocking because the whole point of this is for me to run either AOSP or Lineage someday. I honestly don't know if unlocking the bootloader is needed for dumping your own images, but I highly suspect it's not.
Plug the tablet into your computer
You'll likely see a prompt on your tablet about allowing your computer to debug your tablet. I just checked the box and hit accept so I wouldn't see it again.
Get your scatter file (on your Windows machine)
I tried several things to get the scatter file (I guess this is like a partition table based on the contents I saw) but in the end, by far the easiest way was to just download the scatter file from the file system.
In the Windows Explorer window from before (platform-tools), hold down shift while left clicking and click on Open PowerShell window here
Now type the following to get a shell on your:
.\adb.exe shell
This will get you into the shell environment. Now type the following to verify your scatter file is there:
ls -al /system/data/misc/
In here you should see something like:
-rw-r--r-- 1 root root 13893 2008-12-31 19:00 MT8168_Android_scatter.txt
Now that we have the name, just type exit to get out of the shell
Download the scatter file
.\adb.exe pull /system/data/misc/MT8168_Android_scatter.txt
Open up the scatter file in your favorite text editor (for me, Notepad++)
Now you can see the partition layout, offsets, etc, etc
Dump your image(s) (on your Windows machine)
Now open SP Flash Tool (flash_tool.exe)
On the Download tab, make sure the Download-Agent is MTK_AllInOne_DA.bin
Now click Choose for the Scatter-loading file and browse to the scatter file you just downloaded
This should be in your platform-tools folder unless you moved it
Once the scatter file is loaded, the partition table should fill up with a bunch of partitions
Click on the Readback tab
Click Add
Double-click on the new entry
Navigate to where you want to save your image, and give it a name (in this case I'm starting with boot.img)
Remember how you opened the scatter file in a text editor? Search in the scatter file for boot.img
Make sure the region matches (should be EMMC_USER) between the scatter file and SP Flash Tool
Copy/paste the value for start_addr in the scatter file to Start Address in SP Flash Tool
Copy/paste the value for partition_size in the scatter file to Length in SP Flash Tool
Now do the same thing for recovery.img and any other images you'd like
If you want a full ROM backup, name the file something like ROM_0, then use Start Address of 0x0 and length as the start_addr for the second-to-last entry in the scatter file (in my case, it was 0xc1a80000, just make sure it doesn't start with f's)
Note: I don't know for sure if this is accurate or not, I'm still playing with it, but so far it appears to be. Probably?
Poking around in WwR MTK 2.51, it looks like for this particular device (100011885) I wanted a total dump of 0x73A000000. It looks like this number is derived from the first 8Mb of the EMMC_USER dump, so I'm not sure of an easier way than throwing WwR MTK at it for the moment.
Once you've got all the entries for what you'd like to dump, make sure to disconnect the tablet from your computer and power it off
Now click on Download in SP Flash tool
Once things grey out, then plug the tablet in. After a few seconds, you'll see the images start dumping.
Congrats, you have a boot.img (and whatever other images you wanted). Like I said, from here I tried using Magisk to patch the boot file, but when I flashed it in fastboot, after enabling OEM unlocking in Developer Options, it just kept popping up the initial Onn graphic along with the Orange State warning without getting to the "fancy" Onn graphic and the rest of the boot process. I was able to flash the original boot.img back and it once again booted properly again.
Also, for anyone interested, I've posted my dumped files for the 100011885 in my google drive: https://drive.google.com/drive/folders/17LtLtjKg4JJU9EJdIXPsyNjen0H-ilMX?usp=sharing
Maybe someone will have pity on me and figure out why Magisk isn't working?
Whenever I get a moment, I'll dump my 100003562 as well.
First, thanks a ton for this. I have been trying to pull a full system dump since I bought the tablet and had resorted to single pulls by name(very long and involved) I don't know if this will work for you, but on both of my 7 inch Gen 2 tablets, I just sideloaded Magisk Manager and then opened it (this was after unlocking the tablet) When I first opened MM it just said it needed to download some additional files for my environment. I clicked okay, it downloaded and installed the additional files. Once it rebooted, I open MM again and clicked install Magisk. On the next screen, I clicked direct install and let it do it's thing. After rebooting, root checker showed I had root, but I still can't get it to pass safetyNet. Root access does work as I have installed a few modules and busy box.