Kobo
Arc, Arc 7, Arc 7HD and Arc 10HD
With the release of not 1 but 3 new devices from Kobo and no specific device forum I thought it time we consolidated any and all root / development available information on them under one roof. All credit for others work will be acknowledged if known.
If anyone has any info they feel should be added please post it and ill add it
The following devices and development status are list below
Kobo Arc - Root + recovery (POSSIBLE PROBLEM WITH NEW SYSTEM UPDATE, Arctic may no longer work)
Kobo Arc 7 - Root
Kobo Arc 7HD - Root + recovery
Kobo Arc 10HD - Root + recovery
Please support development on these projects, sign up to XDA and join in, we need all the help that we can get!
Kobo Arc
Root
Enable unknown sources In security options
Download arctic.apk to your tablet from http://zhuoweizhang.net/Arctic.apk and install, it will do the rest and install Chainfires SU
Enjoy your root access
Please note, the Arctic patch for the original arc may no longer work after a recent system update, possible solution would be to use fiddler to check what response the device receives to with the update, then hardreset device, connect to an access point directed to a proxy with fiddler running and change the response it gets, going to be a pure pain in the bum but it should work, ill maybe add that info later. Or work on a way to flash a ROM from stock recovery....
Credit to
zhuowei @ http://zhuoweizhang.net/ for Arctic.apk
Chainfire for SU
Recovery Mod
Root needed first!
And something like ROM Toolbox for all the various apps needed
Install the android SDK on your computer, you will need to add the google usb drivers, you will find them in the "extras"
Enable usb debug on the arc and install the generic google adb usb drivers
Plug in the device and let it install drivers, it WILL fail one device, manually install drivers for the failed "arc" device that's highlighted with an error, click on it and update the driver, browse, let me pick my own, show all devices, click next and have disc. Click browse and navigate to your android SDK>extras>google USB driver, for the correct drivers, select "ADB interface"
Delete or rename the file on the device located at /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 "adb push recovery.img /sdcard/
The next job is to open up a command window on your computer and navigate to adb folder, SDK>platform-tools. 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
Original ROM files
recovery Recovery
xloader Xloader
system System
misc Misc
logos Logos
crypto Crypto
cache Cache
bootlogo Bootlogo
bootloader Bootloader
boot Boot
efs Efs
Custom ROM files
Credit to
Me for recovery mod
Kobo Arc 7
Root
Fully setup device
Download impactor on PC from http://www.cydiaimpactor.com/
Download android SDK on PC, from http://developer.android.com/sdk/index.html
Run SDK manager and acquire the google USB drivers
Enable dev mode on device by going to settings, about kobo, and tap build number 7 times
Enable USB debug mode in developer options
Enable unknown sources in security options
Plug in device and let it install a USB composite device and a arc 7hd drive, it will fail on the third, go to device manager, and manually install drivers for the "arc" device that's highlighted with an error.
Click on it and update the driver, browse, let me pick my own, show all devices, click next, have disc. click browse and navigate to your android SDK>extras>google usb driver\android_winusb.inf, for the correct drivers, select ADB interface
Run the impactor program downloaded earlier, once loaded, click on start
Check your device screen, you should see an error message, click on decline then decline again and finally decline again, (not sure that makes any difference)
Go to the market place and download SU by Chainfire
EDIT: Impactor was updated which will now make the above work
Credit to
http://www.cydiaimpactor.com/ for the rooting tool
Chainfire for SU
howlinwolf430 for trying the unlock with the new impactor available above
Recovery Mod
howlinwolf430 has a working Recovery img up and running, tests continue but we look forward to seeing this soon!
Kobo Arc 7HD
Root
Fully setup device
Download impactor on PC from http://www.cydiaimpactor.com/
Download android SDK on PC, from http://developer.android.com/sdk/index.html
Run SDK manager and acquire the google USB drivers
Enable dev mode on device by going to settings, about kobo, and tap build number 7 times
Enable USB debug mode in developer options
Enable unknown sources in security options
Plug in device and let it install a USB composite device and a arc 7hd drive, it will fail on the third, go to device manager, and manually install drivers for the "arc" device that's highlighted with an error.
Click on it and update the driver, browse, let me pick my own, show all devices, click next, have disc. click browse and navigate to your android SDK>extras>google usb driver, for the correct drivers, select ADB interface
Run the impactor program downloaded earlier, once loaded, click on start
Check your device screen, you should see an error message, click on decline then decline again and finally decline again, (not sure that makes any difference)
Go to the market place and download SU by Chainfire
Credit to
http://www.cydiaimpactor.com/ for the rooting tool
Chainfire for SU
Recovery Mod
Ensure SU is working and you can get SU access with adb shell
download the recovery.img attached in to your adb folder
with the device connected to computer type the following
adb push recovery.img /sdcard/
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
ctrl-c
adb reboot recovery
Make sure you allow recovery to make changes when prompted or it will automatically revert to stock recovery
Kobo 7HD notes
Fastboot and Bootloader modes are ONLY available via adb/fastboot commands, there are NO hardware button combos.
adb reboot bootloader / fastboot reboot-bootloader
adb reboot recovery / fastboot reboot recovery
Recovery can be accessed by turning off the device, holding down "VOL DOWN" and turning on, keep VOL DOWN pressed until booted
APX mode can be accessed by plugging in a USB cable connected to a computer, turning off the device, holding down "VOL UP" and turning on, keep VOL UP pressed until booted, note that the screen remains BLACK and as far as I have worked out it is completely useless without certain files we do not have access to.
Kobo Arc 10HD
Root
Fully setup device
Download impactor on PC from http://www.cydiaimpactor.com/
Download android SDK on PC, from http://developer.android.com/sdk/index.html
Run SDK manager and acquire the google USB drivers
Enable dev mode on device by going to settings, about kobo, and tap build number 7 times
Enable USB debug mode in developer options
Enable unknown sources in security options
Plug in device and let it install a USB composite device and a arc 7hd drive, it will fail on the third, go to device manager, and manually install drivers for the "arc" device that's highlighted with an error.
Click on it and update the driver, browse, let me pick my own, show all devices, click next, have disc. click browse and navigate to your android SDK>extras>google usb driver, for the correct drivers, select ADB interface
Run the impactor program downloaded earlier, once loaded, click on start
Check your device screen, you should see an error message, click on decline then decline again and finally decline again, (not sure that makes any difference)
Go to the market place and download SU by Chainfire
http://www.cydiaimpactor.com/ for the rooting tool
Chainfire for SU
Recovery Mod
Ensure SU is working and you can get SU access with adb shell
download the recovery.img attached in to your adb folder
with the device connected to computer type the following
adb push recovery.img /sdcard/
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
ctrl-c
adb reboot recovery
Make sure you allow recovery to make changes when prompted or it will automatically revert to stock recovery
Kobo 10HD notes
Fastboot and Bootloader modes are ONLY available via adb/fastboot commands, there are NO hardware button combos.
adb reboot bootloader / fastboot reboot-bootloader
adb reboot recovery / fastboot reboot recovery
Recovery can be accessed by turning off the device, holding down "VOL DOWN" and turning on, keep VOL DOWN pressed until booted
APX mode can be accessed by plugging in a USB cable connected to a computer, turning off the device, holding down "VOL UP" and turning on, keep VOL UP pressed until booted, note that the screen remains BLACK and as far as I have worked out it is completely useless without certain files we do not have access to.
EDIT: 16th Feb 2014
Arc 10HD received an OTA update "update-ota832-ota932.zip" around the 10th of Feb. Initial look in to this suggests not only are there some system updates the but the bootloader is updated too, its only about 17MB
Edit 6
10HD received a OTA update
Edit 5
thanks to howlinwolf430 Arc 7 now has root, I need to confirm this and the method but I believe the new impactor has added another vulnerability that allows ROOT Thus the guide for the 7HD and the 7 is the same
Edit 4
Recovery img is now complete for the Arc 10HD and 7HD! There are some small configuration changes needed to fix some mounting issues but it backs up and restores just fine
Edit 3
Source code now available for all arcs, git for everything available https://github.com/dazza9075
Recovery Roms for Arc 7HD and 10HD almost complete, just testing to see if it restores correctly
Edit 2
Please note, the Arctic patch for the original arc may no longer work after a recent update
Bootloaders on the 7HD and 10HD appear to be unlocked.
Edit 1
Development on the Arc 7 has stagnated and I no longer have one to directly play with although I do have access if need be.
Sent from my arc 10HD using xda app-developers app
Support needed!
Hi everyone, if your reading this and have some experience in building custom ROMs for unsupported devices and wish to give us a guiding hand please jump on board and help where you can. We currently have working custom recovery's on all devices ( Arc 7 needing a little bit of testing ) but we are needing some support for the next steps!
Many thanks!
Arctic,apk
I have ordered a Kobo Arc online. Any idea if the Arctic.apk does or does not work on them with the system update. Just looking for confirmation
Nice work...I hope it won't remain an isolated effort
@dazza9075: I just ordered the Arc 10HD - can I safely update the software once I get it and root it AFTER? I didn't see any notes indicating otherwise, but I know from my other Android devices that usually the root/recovery methods are tied to a specific version.
Note I don't even know yet if it will require an update - I'm super-new to the Kobo ecosystem.
BTW: thanks for the work done - I never use an Android phone/tablet/media device that does not have root access and a recovery mechanism to save the day.
kayge said:
I have ordered a Kobo Arc online. Any idea if the Arctic.apk does or does not work on them with the system update. Just looking for confirmation
Click to expand...
Click to collapse
after the most recent and probably last system update it is disabled. I stopped my arc from updating so cant confirm without a full reset but the original author of the arctic apk has said it no longer works, I cant see any reason for him to lie.
Ipse_Tase said:
@dazza9075: I just ordered the Arc 10HD - can I safely update the software once I get it and root it AFTER? I didn't see any notes indicating otherwise, but I know from my other Android devices that usually the root/recovery methods are tied to a specific version.
Note I don't even know yet if it will require an update - I'm super-new to the Kobo ecosystem.
BTW: thanks for the work done - I never use an Android phone/tablet/media device that does not have root access and a recovery mechanism to save the day.
Click to expand...
Click to collapse
ok, Kobo will do a system update as soon as you turn the thing on, you cant even get around that (although some fiddling with fiddler might fool it if we can ID what is going on). however, to date there hasn't been an update that disables it. and if there was we can simply flash my stock ROMs which already have root and are flashable.
what we are lacking however is a custom ROM for any of the arcs. More importantly than that we are lacking people to help us!
Weird, I could not install the ADB drivers from the SDK (Win 7 64-bit Enterprise). Had to use my trusted Nexus Root Toolkit and worked fine with that.
I'm liking it so far....appreciate your work to document the rooting procedure.
Let's hope development will pick up at some point, it's a good device (I have the ARC 10HD - got it on sale + coupon in Canada).
Been meaning to ask: have any of you guys found a good screen protector for the Arc 10HD?
I realize this is off topic (sorry OP) but I feel there is ZERO chances I would get an answer elsewhere than in this thread - the only valuable one on XDA re Kobo.
Ipse_Tase said:
Been meaning to ask: have any of you guys found a good screen protector for the Arc 10HD?
I realize this is off topic (sorry OP) but I feel there is ZERO chances I would get an answer elsewhere than in this thread - the only valuable one on XDA re Kobo.
Click to expand...
Click to collapse
Actually I don't, I have a leather case for mine that acts as a stand and protector,i don't sell them either but I suspect that will change soon
Sent from my arc 10HD using xda app-developers app
Ipse_Tase said:
Weird, I could not install the ADB drivers from the SDK (Win 7 64-bit Enterprise). Had to use my trusted Nexus Root Toolkit and worked fine with that.
I'm liking it so far....appreciate your work to document the rooting procedure.
Let's hope development will pick up at some point, it's a good device (I have the ARC 10HD - got it on sale + coupon in Canada).
Click to expand...
Click to collapse
Bazaar, I thought they were the same drivers, well I'm glad it worked eventually, if you or anyone else wants to help with dev you could try searching if there are other devices with the same SoC , we are looking for same gpu/CPU combo that already has a working custom ROM.
Sent from my arc 10HD using xda app-developers app
Yep...I am looking in the Transformer TF-701t forums. I'm not on the software side of Hi Tech, so I'll have to do some reading as I am as frustrated as you with the lack of interest in this platform.
BTW: you may want to add to your tutorial that after booting in Recovery for the first time, the user should accept to make boot.img changes - as otherwise all the frequent updates will wipe the recovery you installed. I was too quick to reboot and now I have to push recovery again.
Or if you think this is not safe to make permanent (I did it on every other Android device I own) maybe that should be stated too. People might want to get OTA updates and it is my understanding that with a custom recovery you won't be getting them. Hell, I'm still hoping we will get a stock KitKat at some point.
Thanks...for being the only one that cares
PS. From what I read about Netflix (big user....I "cut the cord" a year ago) it seems we need 4.3 for Netflix to run in HD (DRM ****). All I can say is that I don't get HD now - so it seems true.
One good reason to hope for a Kobo upgrade. I am already plagued with Ouya being stuck at 4.1.2
Very surprised at the pack of interest in the Kobo tablets, given the impressive combination of awesome specs and very low price. Have an Arc 7 32gb and an Arc 7 16gb in the family and gathering my forces to root em both.
I've read the forum but am a bit thick. Bottomline, are the root guides here conformed working on the latest updates since November 2013?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
JoshReuben said:
I've read the forum but am a bit thick. Bottomline, are the root guides here conformed working on the latest updates since November 2013?
Click to expand...
Click to collapse
I just rooted my ARC 10HD 2 days ago, AFTER it got the last update (something one cannot prevent when setting it up for the first time).
JoshReuben said:
Very surprised at the pack of interest in the Kobo tablets, given the impressive combination of awesome specs and very low price. Have an Arc 7 32gb and an Arc 7 16gb in the family and gathering my forces to root em both.
I've read the forum but am a bit thick. Bottomline, are the root guides here conformed working on the latest updates since November 2013?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Should work fine, they updated the bootloader a couple of days ago on the 10HD but nothing appears to have changed, some system updates, some app updates, not a lot else from first impression
Ipse_Tase said:
I just rooted my ARC 10HD 2 days ago, AFTER it got the last update (something one cannot prevent when setting it up for the first time).
Click to expand...
Click to collapse
it updated the other day. ive been away for a bit so cant be sure when.
Kobo contact
I could not find a way to send an email to Kobo support or get in touch with someone in this company. As a legitimate user I have a legitimate question for them: what are the plans moving forward with software upgrades?
They don't seem to realize that part of the problem of not selling more devices is also the complete lack of communication (including advertising) from this company.
Mind blowing...
That being said, I love my Arc 10HD and seeing how much better my old Xoom is with KitKat, I can only imagine what it would mean for the Kobo family.
PS. I ended up buying this screen protector:
http://www.illumishieldstore.com/iL...e-Anti-Fingerprint-Replacements/dp/B00F6FJHNU
Ipse_Tase said:
I could not find a way to send an email to Kobo support or get in touch with someone in this company. As a legitimate user I have a legitimate question for them: what are the plans moving forward with software upgrades?
They don't seem to realize that part of the problem of not selling more devices is also the complete lack of communication (including advertising) from this company.
Mind blowing...
That being said, I love my Arc 10HD and seeing how much better my old Xoom is with KitKat, I can only imagine what it would mean for the Kobo family.
PS. I ended up buying this screen protector:
http://www.illumishieldstore.com/iL...e-Anti-Fingerprint-Replacements/dp/B00F6FJHNU
Click to expand...
Click to collapse
Ask your question at http://kobo.frontlinesvc.com/app/ask
They are usually pretty quick to get back to you, as for upgrades, I've not heard any news of anything so really don't know what the official line is, I've not heard any news on new devices either so we may get at least one supported is upgrade. Ideally though we need to nail our own ROM to be sure
Sent from my arc 10HD using xda app-developers app
Hi, first of all this is my first contribution to the forum. I've been using the resources until now but i wanted to contribute with something. This is not my development, and only gathered the information and put it here, so thanks to all the guys who help me in the first place.
I bought the Homesync waiting more from the device, and i now the device has so much potential but has been wasted for samgsung, they havent give a real update to the device and they left it at Android 4.2.2, with little support to apps in the store, with no suppor for multiwindow, and other things they could make for this device to success. Well, what we can do i to root it so we can gain access to other apps, and apps from independent markets or developers.
Requeriments:
1) Set your devide to a MJ3 ROM, either updating it or downgrading it from a stock ROM. You can get it from sammobile here http://www.sammobile.com/firmwares/3/?download=24442. I had to use Odin to downgrade to Stock Rom MJ3. If you dont know how to use Odin, in the same link you can read how to do it. Why MJ3? Because that ROM is working with root process im doing here.
2) After with the MJ3 ROM up and running. From your PC, do the following: download the superuser folder from the attachment below.
3) This part is thanks to the user K1MU, you can see his work here http://forum.xda-developers.com/showthread.php?t=2565758 ,before you try using this rooting program, you'll need to have the USB drivers installed for the homesync. Download here if you cant see your homesync when connected to the microUSB port.
http://developer.samsung.com/android/tools-sdks/Samsung-Android-USB-Driver-for-Windows;jsessionid=1cG8Jw2NLJgzwXpG3RhBjQ5tQLGMQTVw2xwJxQld0yyKlG6psQ1W!-2096422745
4) The next thing you must do is to enable USB debugging on your phone. Go to "Settings", "More...", then "Developer Options".
If "Developer Options" doesn't appear, then you'll need to enable it - go to "Settings", "More", "About Phone". Scroll down so the "Build Number" is visible, then tap on that several times until developer mode is enabled. In Developer Options, make sure "USB Debugging" is checkmarked.
5) Make sure that your computer is allowed to use USB debugging on your homesync. To do this, unplug your phone and unlock it. Then, plug in the USB cable. If you see an "Alllow USB debugging?" window pop up, tap on the "Always allow from this computer" to check it, then tap OK. If you don't see that popup, it's OK, you should be OK to proceed. This is going to appear in the Homesync.
6) Then you need to unpack the attached ZIP file somewhere onto your PC. You should have the following when done:
- a file called "install.bat"
- a file called "install.sh"
- a folder called "files"
7) Double click on the "install.bat" to run the root. It will root and reboot your phone. Once that's done, you're rooted!
The first thing that the install script will ask you is whether or not to install Busybox. Busybox is a program that provides a fairly extensive set of Linux shell utilities that a Unix user would expect to see. If you're not going to be using the shell (terminal emulator or adb shell) then you may not want to install Busybox. You may, however, find that some root-required utilities assume that Busybox is installed. If SuperSU asks you to update the su binary, choose the "Normal" method. If SuperSU asks you about disabling Knox, allow it. This exploit will NOT set the Knox Warranty Void flag. It will set the "Custom" flag, but that's nothing to worry about. While you're running this, you'll need to keep the phone awake and watch both the computer running the rooting script and your phone. You shouldn't unplug the phone unless you're prompted by the rooting script. Leave it connected until it's done.
8) In this point you will be rooted and ready to boom your Homesync.
I think i will be expanding this post, but for now this is it. Everything works fine with the phone using the homesync app.
Root Samsung Homesync gt-b9150
Hi everybody, Samsung homesync is root with Kingroot, that´s all, thanks/Hola a todos, el Samsung Homesync se rootea con Kingroot, es todo, gracias.
Hi everybody !
I got my new OPO phone Tuesday, and I decided to root & unlock it. I downloaded Bacon Root Toolkit v1.0.2, and runned it. I first opened it and wrote that i had an old version of android, because my OPO was not updated yet, so the rooting didn't work. So i updated Cyanogen Version on my OPO today, it's now 64GB SandStone, XNHP44S-KTU84Q. I clicked on Full Driver Installion - Automatic + Manual, and then went to Step 3 as recommended. I downloaded Google Drivers, then clicked on Configure ADB. So appears the Device Manager, i clicked on A0001 ( OnePlus One ) and then tried to Update Drivers Software, but i can't have the " Android Devices " in the selection, i only have " USB MTP Device ". And if i try to Fastboot the OPO, it doesn't appears anymore in the Device Manager.
My friends didn't have that problem so they couldn't help, maybe could you ?
Sorry for bad english, i'm a French student ...
Waiting for an answer soon ! Cya !
Chyquito said:
Hi everybody !
I got my new OPO phone Tuesday, and I decided to root & unlock it. I downloaded Bacon Root Toolkit v1.0.2, and runned it. I first opened it and wrote that i had an old version of android, because my OPO was not updated yet, so the rooting didn't work. So i updated Cyanogen Version on my OPO today, it's now 64GB SandStone, XNHP44S-KTU84Q. I clicked on Full Driver Installion - Automatic + Manual, and then went to Step 3 as recommended. I downloaded Google Drivers, then clicked on Configure ADB. So appears the Device Manager, i clicked on A0001 ( OnePlus One ) and then tried to Update Drivers Software, but i can't have the " Android Devices " in the selection, i only have " USB MTP Device ". And if i try to Fastboot the OPO, it doesn't appears anymore in the Device Manager.
My friends didn't have that problem so they couldn't help, maybe could you ?
Sorry for bad english, i'm a French student ...
Waiting for an answer soon ! Cya !
Click to expand...
Click to collapse
first off root kit is not needed to root your phone. Secondly you did not have to update it prior to rooting as well. Now I came across this issue with my friends phone the other day and used this method here.
It works just dont skip a step and please use the stickied method in General to root your phone. You learn nothing with root kits. Its also keeps you from searching properly and finding answers.....
...
playya said:
first off root kit is not needed to root your phone. Secondly you did not have to update it prior to rooting as well. Now I came across this issue with my friends phone the other day and used this method here.
It works just dont skip a step and please use the stickied method in General to root your phone. You learn nothing with root kits. Its also keeps you from searching properly and finding answers.....
Click to expand...
Click to collapse
I did Step 1 and Step 2 successfully, now i reached the Step 3, and did a) and b). When i do c) step, i cannot find my OPO in the list, it is int the " Hided Devices " and when i try to update drivers softwares, i just have : " Android Devices -> USB MTP Device ", and not, Google Inc. - Android Bootloader Interface., how can i find it ?
Chyquito said:
I did Step 1 and Step 2 successfully, now i reached the Step 3, and did a) and b). When i do c) step, i cannot find my OPO in the list, it is int the " Hided Devices " and when i try to update drivers softwares, i just have : " Android Devices -> USB MTP Device ", and not, Google Inc. - Android Bootloader Interface., how can i find it ?
Click to expand...
Click to collapse
you are confusing me if you followed the directions then put your phone in Fastboot mode you should see your phone popup in your device manager list.
Install the latest Samsung drivers: SAMSUNG USB Driver v1.5.33.0
Restart the computer (very important)
Go to Device Manager, find the Android device, and select Update Driver Software.
Select Browse my computer for driver software
Select Let me pick from a list of device drivers on my computer
Select ADB Interface from the list
Select SAMSUNG Android ADB Interface (this is a signed driver). If you get a warning, select Yesto continue.
Done!
Please dont take this wrong but is this your first android phone and rooting? If so there is soooo much you should be reading before doing this. Also make sure this is what you want to do. With rooting what goal are you trying to achieve
playya said:
first off root kit is not needed to root your phone. Secondly you did not have to update it prior to rooting as well. Now I came across this issue with my friends phone the other day and used this method here.
It works just dont skip a step and please use the stickied method in General to root your phone. You learn nothing with root kits. Its also keeps you from searching properly and finding answers.....
Click to expand...
Click to collapse
playya said:
you are confusing me if you followed the directions then put your phone in Fastboot mode you should see your phone popup in your device manager list.
Install the latest Samsung drivers: SAMSUNG USB Driver v1.5.33.0
Restart the computer (very important)
Go to Device Manager, find the Android device, and select Update Driver Software.
Select Browse my computer for driver software
Select Let me pick from a list of device drivers on my computer
Select ADB Interface from the list
Select SAMSUNG Android ADB Interface (this is a signed driver). If you get a warning, select Yesto continue.
Done!
Please dont take this wrong but is this your first android phone and rooting? If so there is soooo much you should be reading before doing this. Also make sure this is what you want to do. With rooting what goal are you trying to achieve
Click to expand...
Click to collapse
This is my second Android phone, and i never rooted my phone. A friend told me to do this and i have to do this if i want to get WiFi access at my school.
When i'm the Device Manager, the OPO doesn't appears in Fastboot mode... Neither Android Device...
I downloaded the Samsung Driver, but after rebooting the PC, i can't see any Android Device in the Device Manager. I only have MTP, that contain A0001, Android ADB Device, and something else useless. And i can't update Android ADB Device's Drivers Software...
Chyquito said:
This is my second Android phone, and i never rooted my phone. A friend told me to do this and i have to do this if i want to get WiFi access at my school.
When i'm the Device Manager, the OPO doesn't appears in Fastboot mode... Neither Android Device...
I downloaded the Samsung Driver, but after rebooting the PC, i can't see any Android Device in the Device Manager. I only have MTP, that contain A0001, Android ADB Device, and something else useless. And i can't update Android ADB Device's Drivers Software...
Click to expand...
Click to collapse
OK with android and rooting following instructions is key. By your response you did not follow all the steps. Please follow each one to the letter
There are more steps for you to do after a reboot
To root my phone I tried countless methods and apps and I don't know how many hours I spent for searching proper root method. But Finally I managed to do it myself.
Disclamer:I will not be responsible for any kind of damages to your devices, although it is less likely to happen.
Note: This method puts "root" word on your boot splash screen.
This method is for Coolpad Dazen 1 8297L-I00 (Released in India)
Please read the whole post before actually following.
Download:
Busybox, Terminal Emulator from playstore and Kinguser/Kingroot apk from http://www.kingroot.net/wap/download for your phone
And iRoot For your PC/Laptop from http://products.mgyun.com/api/downjump?id=4321 official web http://www.mgyun.com
You only need internet for downloading above files and after that You can disable it.
PROCEDURE FOR ROOT:
Part 1- Acquiring improper/temporary root or shopuld I say su binary
#1- Enable USB Debugging -Go to setting>About Phone>Phone Config info and Tap 5-6 time on build number to unlock Developer options Then get back in main Settings and under developer option enable usb debugging and allow mock location
#2- Install iroot on your Pc and launch it and connect your phone to your PC via usb.
#3- Within Few Seconds there will be a popup on your phone asking to allow USB debugging Tick on the Always allow from this computer and select OKAY
#4- Wait for sometime then on iroot software click on settings (gear Icon) on the top right corner
#5- On this screen there will be three rows of icons, Click on the second icon of second row (Anchor)
#6- After that a new screen and a dialog will appear Click on the button to remove the dialog
#7- And now click on the green button on the right bottom corner to begin the root process.
#8- If successful there will a smiling cartoon on Pc and phone will reboot. Now move to Part 2.
#9- If not then phone will not reboot and there will be a sad cartoon on Pc. Now click on the green button below that cartoon to retry.
#10- Keep repeating the 9th step untill you get success It could Take upto 9 or ten retries.
Now you should have gained su binary in your phone's /system/xbin/ and if you are lucky after rebooting you haven't lost the kingroot software.
Try su command in terminal emulator if you get '#' sign you are rooted and no need to go further but if after entering su you dont get any response neither '#' nor '$' Then keep going to part-2
Part 2- Making kinguser stay installed
#1- Install the previously downloaded kinguser.apk
#2- Open busybox and grant it root permission and there will be an option to install select it.
#3- after successfully installing busybox open Terminal emulator type the following command, if you are stuck on the previously typed su then either close the window or open new window and type following.
Code:
su
chattr +ia /data/app/com.kingroot.kinguser-1.apk
Now, if after typing the above commands you get'#' in response you are successfull. To check restart your phone you'll see kinguser is still there and working.
Tip: Take a backup of /system partition, just in case you later need it, type following command in terminal emulator
Code:
su
tar -c /system/*>> /storage/sdcard1/system.tar
If in this post I have broken any rules please let me know because this is the first time I am posting a tutorial on XDA
Important threads for dazen1
[Create system.img for dazen1 for unbricking purpose] http://forum.xda-developers.com/android/help/guide-create-flashable-img-folder-tar-t3270166
[UNBRICK]Reviving Yulong Coolpad Dazen 1 http://forum.xda-developers.com/android/help/reviving-coolpad-dazen-1-8297l-i00-t3236337
[Discussion/Q&A kind of thread] http://forum.xda-developers.com/chef-central/android/root-extracting-boot-img-recovery-img-t3170809
good work mate.. is there unroot option also available in iroot did you try that? i haven't had experience with that app
Sent from my Coolpad 8297L-I00 using XDA Premium 4 mobile app
yes there is, And I have tried that. it does it's job. It removes the su binary and kingroot/superuser app from the system.
but the thing is,
once you have rooted with kingroot (when the root word is put on your boot screen), I am not exactly sure about this but as far as I have learned this method makes changes in the kernel/boot.img to put the root word on the boot splash screen and perhaps it could be why after installing ota update peoples devices gets in bootloop or either bricked
So, if anyone could get a device which is not rooted (not even attempted to root using kingroot or any other method which changes bootsplash screen) should take a backup of it first and also if possible upload for others
Word root appears on boot screen by making changes in params . it is the partition that contains boot logo in our phone... It has nothing to do with kingroot. root will appear if u root your device its coolpad's work.
Sent from my Coolpad 8297L-I00 using XDA Free mobile app
jackey31 said:
Word root appears on boot screen by making changes in params . it is the partition that contains boot logo in our phone... It has nothing to do with kingroot. root will appear if u root your device its coolpad's work.
Sent from my Coolpad 8297L-I00 using XDA Free mobile app
Click to expand...
Click to collapse
root word coming is not our problem. we need some ways to make a recovery for overs
Sent from my Coolpad 8297L-I00 using XDA Premium 4 mobile app