Related
So,
I've bought an Samsung Galaxy S3 replica (read: fake, and i want only to root it no flash it):
Model number: S930
Android version: 4.0.3
Baseband version: DM_BASE_12A_W12.28_P1|sc8810_modem|07-13-2012 16:42:35
Kernel version: 2.6.35.7 [email protected] #3
Software version: T300_JYYS930_C3BOM_MLB_V6.6.5_20121105
Hardware version: 1.1.0
CPU: Spreadtrum
When I first plugged it my notebook (Win7 32bit) I've got in the device manager:
Other Devices
- Spreadtrum Phone
- Spreadtrum Phone
- Spreadtrum Phone
I'm trying to root it so I started my research, afts thousands of tests, I discoverd that
Other Devices
- Spreadtrum Phone >> Android Composite ADB Interface (driver instaled with Android SDK)
- Spreadtrum Phone >> SCI General U2S(AT) (COM3) (Google Search: Spreadtrum Drivers)
- Spreadtrum Phone >> SCI Vendor U2S(DIAG) (COM4) (Google Search: Spreadtrum Drivers)
So after all the yellow marks disappeard i've tried almost everything to root it:
- QQPhoneManeger for Android (which recognise the device like: Sprd S930 - allow me to access my "device root" but I can't change anything there, not even copy from it)
- UnlockRoot (which worked in my previous phone MTP65XX also an android replica)
- Odin
- PDA Net
- SparkyRoot
- Z4Root
- Poot-debug + Ministro II
- Instant-root
- Gingerbreak
- OneClickRoot
- SuperOneClick
And recently i've tried the DooMLoRD ROOT v18 - And I've only got:
adb is out of date. killing...
*daemon estarted succefully*
and nothing more, so i've went to search some more, and I've learned how to verify if adb recognise the device.
I added the C:\android-sdk\plataform-tools to my system path and tried the commands
adb devices
my answer was:
*daemon not runing. startin it now on port 5037*
*daemon started successfully*
List of devices attached:
....
Nothing, so i've tried
adb shell
my answer was:
error: device not found
So I re-checked all the drivers, unistalled and re-installed.
tried again same thing...
So now i'm stuck, all the solutions that i've fonund for the problem is now coverd
Is there any way to solve it? Or any way to root my device that isn't listed? Or any driver that's better for my device than the one in Android SDK?
Thanks in advance and sorry for the english.
UPDATE!!
Solved, yay!, view solutions below
Did you tried this method http://forum.xda-developers.com/showthread.php?t=1886460 ?
Press the THANKS button if i helped
HOPE IT WILL WORK !! GOOD LUCK !!!
Thanks, but already tryied this one.
karimkahale said:
Did you tried this method http://forum.xda-developers.com/showthread.php?t=1886460 ?
Press the THANKS button if i helped
HOPE IT WILL WORK !! GOOD LUCK !!!
Click to expand...
Click to collapse
Thanks, but this one also don't work, I forgot to list it. 'cause it's similar to the DooMLoRD .bat
All i got is the *daemon started successfully* answer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And than when I kill the adb process in the task maneger, it resume the running, but aways returning the answer
error: device not found
What I don't get is, if the windows system recognise my Android Composite ADB Interface, why the adb don't?
SOLVED!!!
I've made it. *so ****ing happy right now*
Solutions:
To - Device adb recognition.
Place Hardware ID VID_xxxx in {user home}/.android/adb_usb.ini.
Source
Subscribing the adb.exe files Download Here
Source
To - Rooting
I've used one of the previos methods i've tried
DooMLoRD ROOT v4
Thanks for the tipo karimkahale
And now i'm going to enjoy my 3 sleepless days victory.
Great!! Glad it worked!!
But just please press the THANKS button, it's much better
H_Bler said:
I've made it. *so ****ing happy right now*
Solutions:
To - Device adb recognition.
Place Hardware ID VID_xxxx in {user home}/.android/adb_usb.ini.
Font
Subscribing the adb.exe files Download Here
Font
To - Rooting
I've used one of the previos methods i've tried
DooMLoRD ROOT v4
Thanks for the tipo karimkahale
And now i'm going to enjoy my 3 sleepless days victory.
Click to expand...
Click to collapse
Hi everyone, I'm having the same problem with a similar phone, a S3 replica:
Model number: Z15A
Android version: 4.0
Baseband version: DM_BASE_12A_W12.28_P1|sc8810_modem|07-13-2012 16:42:35
Kernel version: 2.6.35.7 [email protected] #3
Software version: T300_JYYS930_C3BOM_MLB_V6.6.5_20121105
Hardware version: 1.1.0
CPU: Spreadtrum
It appears in the Device Manager (Win7 64bit) as:
Other Devices
- Spreadtrum Phone
- Spreadtrum Phone
- Spreadtrum Phone
I tried installing the USB driver that comes with the Android SDK ( sdk\extras\google\usb_driver ) using "Update driver..." but it only says that Windows could not find a driver there ( maybe because of the 64bit OS? ).
I think i will try and install a Win7 32 bit somewhere just in case, but nevertheless, could you elaborate a bit the solution you found please? (mostly the driver part, as I cannot find how to get the device recognized by Windows)
Thanks in advance.
sergimas said:
Hi everyone, I'm having the same problem with a similar phone, a S3 replica:
Model number: Z15A
Android version: 4.0
Baseband version: DM_BASE_12A_W12.28_P1|sc8810_modem|07-13-2012 16:42:35
Kernel version: 2.6.35.7 [email protected] #3
Software version: T300_JYYS930_C3BOM_MLB_V6.6.5_20121105
Hardware version: 1.1.0
CPU: Spreadtrum
It appears in the Device Manager (Win7 64bit) as:
Other Devices
- Spreadtrum Phone
- Spreadtrum Phone
- Spreadtrum Phone
I tried installing the USB driver that comes with the Android SDK ( sdk\extras\google\usb_driver ) using "Update driver..." but it only says that Windows could not find a driver there ( maybe because of the 64bit OS? ).
I think i will try and install a Win7 32 bit somewhere just in case, but nevertheless, could you elaborate a bit the solution you found please? (mostly the driver part, as I cannot find how to get the device recognized by Windows)
Thanks in advance.
Click to expand...
Click to collapse
Hello,
I, don't know if the trouble is because you have win 7 64bit, but I will say how i've made it.
Windows has already intalled the device as Spreadtrum with generic drives, so any other driver that you try to install tha isn't compatible with the ones windows associated with your device will be avaliated by the system as "no compatible with your device", so what you got to do is, uninstall this generics drivers so the "spreadtrum"s will be displayed with the yellow mark, and under the "other devices" section in the device manager, then, you install manually the spreadtrum drivers that you can find in searches in two of the "spreadtrum" devices (in the drivers i've found in google searches I've got 3 different drivers General, Vendor and Modem, but i've only used General and Vendor as the other "spreadtrum" device was an ADB interface and not a modem) and the other you also install manually but with the driver in the folder "usb_driver" in "android-sdk/extras/google".
Also, when you use "update driver" follow: Search in my computer> pick in a list> have a disc , then you search in the folders of android-sdk and of the spreadtrum drivers that you downloaded.
Hope it helps.
Just one more thing, i've made it with the root access but now my Play Store don't open... it opens loads a little and then close with (the com.android.vending stopped unexpectedly...
I've tried re-instal the native apk, factory reset, everything, bout nothing works :/
I had to re install all my aps via computer with the "adb install xxxx.apk. And every other aps work normally.
Happy holidays everyone.
If anyone have a clue of what to do, i'd like to try it
H_Bler said:
Hello,
I, don't know if the trouble is because you have win 7 64bit, but I will say how i've made it.
Windows has already intalled the device as Spreadtrum with generic drives, so any other driver that you try to install tha isn't compatible with the ones windows associated with your device will be avaliated by the system as "no compatible with your device", so what you got to do is, uninstall this generics drivers so the "spreadtrum"s will be displayed with the yellow mark, and under the "other devices" section in the device manager, then, you install manually the spreadtrum drivers that you can find in searches in two of the "spreadtrum" devices (in the drivers i've found in google searches I've got 3 different drivers General, Vendor and Modem, but i've only used General and Vendor as the other "spreadtrum" device was an ADB interface and not a modem) and the other you also install manually but with the driver in the folder "usb_driver" in "android-sdk/extras/google".
Also, when you use "update driver" follow: Search in my computer> pick in a list> have a disc , then you search in the folders of android-sdk and of the spreadtrum drivers that you downloaded.
Hope it helps.
Just one more thing, i've made it with the root access but now my Play Store don't open... it opens loads a little and then close with (the com.android.vending stopped unexpectedly...
I've tried re-instal the native apk, factory reset, everything, bout nothing works :/
I had to re install all my aps via computer with the "adb install xxxx.apk. And every other aps work normally.
Happy holidays everyone.
If anyone have a clue of what to do, i'd like to try it
Click to expand...
Click to collapse
I got to get the drivers installed. I've got:
- Android Composite ADB Interface
- SCI General U2S(AT) (COM4)
- SCI Vendor U2S(DIAG) (COM3)
I tried some of the rooting methods you list (z4root, OneClickRoot, SuperOneClick,...) and finally DooMLoRD ROOT v18, but the problem is that my /system directory is Read-Only, so no way is anything working.
I don't kno how to proceed now (noob here ), but I'll keep you posted if I find any solution.
Happy holidays, and good luck!
s550
I have a similar replica, the s560. Should this metod work on my phone? i want to install cyanogenmod on it
this one focalprice.com/MH0369B/35_Android_40_6820_10GHz_Smartphone_with_WiFi_TV_Bluetooth.html
sergimas said:
I got to get the drivers installed. I've got:
- Android Composite ADB Interface
- SCI General U2S(AT) (COM4)
- SCI Vendor U2S(DIAG) (COM3)
Click to expand...
Click to collapse
Hi!
I'm trying to do this myself, but I can't seem to install the drivers properly. Did you use 64-bit windows 7? And which drivers did you use?
Cause I used "SPREADTRUM SCI-USB2Serial-version-1.5.6.1" which I found via Google search, and none of the drivers I found are not digitally signed. That means they won't install properly in win 64-bit.
I only get: SCI USB2Serial (COM3) and SciCmpst Diaog (COM4), and they are both still with the yellow exclamation mark.
Anyone got a good tip for me?
Thanks in advance
teewee3 said:
Hi!
I'm trying to do this myself, but I can't seem to install the drivers properly. Did you use 64-bit windows 7? And which drivers did you use?
Cause I used "SPREADTRUM SCI-USB2Serial-version-1.5.6.1" which I found via Google search, and none of the drivers I found are not digitally signed. That means they won't install properly in win 64-bit.
I only get: SCI USB2Serial (COM3) and SciCmpst Diaog (COM4), and they are both still with the yellow exclamation mark.
Anyone got a good tip for me?
Thanks in advance
Click to expand...
Click to collapse
I've managed to install them on a 32-bit windows 7. Everything I tried on 64-bit just showed the yellow mark, although they where the x64 version drivers.
Regarding the rooting process, I followed this method (As I cannot post outside links yet, just Google: "Root Android 4.0 (Novo método) Atualizado x3") and it worked at last. It's written in portuguese but it's not too difficult to follow looking at the video.
I hope it helps a bit.
Now I was trying to install a custom CWM recovery, prior to install a custom ROM, but I really don't know which one should I use (nor CWM recovery nor ROM)
If someone can point me in any directions on how to continue, it would be great.
---------- Post added at 11:53 PM ---------- Previous post was at 11:46 PM ----------
H_Bler said:
Hello,
I, don't know if the trouble is because you have win 7 64bit, but I will say how i've made it.
Windows has already intalled the device as Spreadtrum with generic drives, so any other driver that you try to install tha isn't compatible with the ones windows associated with your device will be avaliated by the system as "no compatible with your device", so what you got to do is, uninstall this generics drivers so the "spreadtrum"s will be displayed with the yellow mark, and under the "other devices" section in the device manager, then, you install manually the spreadtrum drivers that you can find in searches in two of the "spreadtrum" devices (in the drivers i've found in google searches I've got 3 different drivers General, Vendor and Modem, but i've only used General and Vendor as the other "spreadtrum" device was an ADB interface and not a modem) and the other you also install manually but with the driver in the folder "usb_driver" in "android-sdk/extras/google".
Also, when you use "update driver" follow: Search in my computer> pick in a list> have a disc , then you search in the folders of android-sdk and of the spreadtrum drivers that you downloaded.
Hope it helps.
Just one more thing, i've made it with the root access but now my Play Store don't open... it opens loads a little and then close with (the com.android.vending stopped unexpectedly...
I've tried re-instal the native apk, factory reset, everything, bout nothing works :/
I had to re install all my aps via computer with the "adb install xxxx.apk. And every other aps work normally.
Happy holidays everyone.
If anyone have a clue of what to do, i'd like to try it
Click to expand...
Click to collapse
I guess it won't be the same, but I was having problems with my Play Store also. It did not loaded anything, just giving "Unable to connect" problems, and it was solved (momentarily) uninstalling all updates. That's going back to Android Market, though it updates itself afterwards to Play Store again. You can do it in Applicatins > Manage Applications > Google Play Store, and push the button "Uninstall updates".
As I said, i think it's not the same issue, but I just wanted to share it, just in case.
Where to find the drivers?
H_Bler said:
Hello,
I, don't know if the trouble is because you have win 7 64bit, but I will say how i've made it.
Windows has already intalled the device as Spreadtrum with generic drives, so any other driver that you try to install tha isn't compatible with the ones windows associated with your device will be avaliated by the system as "no compatible with your device", so what you got to do is, uninstall this generics drivers so the "spreadtrum"s will be displayed with the yellow mark, and under the "other devices" section in the device manager, then, you install manually the spreadtrum drivers that you can find in searches in two of the "spreadtrum" devices (in the drivers i've found in google searches I've got 3 different drivers General, Vendor and Modem, but i've only used General and Vendor as the other "spreadtrum" device was an ADB interface and not a modem) and the other you also install manually but with the driver in the folder "usb_driver" in "android-sdk/extras/google".
Also, when you use "update driver" follow: Search in my computer> pick in a list> have a disc , then you search in the folders of android-sdk and of the spreadtrum drivers that you downloaded.
Hope it helps.
Just one more thing, i've made it with the root access but now my Play Store don't open... it opens loads a little and then close with (the com.android.vending stopped unexpectedly...
I've tried re-instal the native apk, factory reset, everything, bout nothing works :/
I had to re install all my aps via computer with the "adb install xxxx.apk. And every other aps work normally.
Happy holidays everyone.
If anyone have a clue of what to do, i'd like to try it
Click to expand...
Click to collapse
Hi, Everyone!
I also have a Spreadtrum S930 phone. My problem is I can't even locate the SCI general and the SCI vendor drivers... Can somebody post a link or tell me where to find these drivers? Sorry... absolute noob here. Thanks.
Will
will_power00 said:
Hi, Everyone!
I also have a Spreadtrum S930 phone. My problem is I can't even locate the SCI general and the SCI vendor drivers... Can somebody post a link or tell me where to find these drivers? Sorry... absolute noob here. Thanks.
Will
Click to expand...
Click to collapse
You can find a them here for example ge.tt/8hWh71S/v/0 (it's a 7zip file).
Cheers.
sergimas said:
You can find a them here for example ge.tt/8hWh71S/v/0 (it's a 7zip file).
Cheers.
Click to expand...
Click to collapse
I got the drivers. They work. Thanks, Sergimas.
Playvinci
Is this how you added your drivers in the .ini file? Also did you have problems loading the drivers because when I installed it (win 7 64bit) it says its unsigned and said something about having a problem installing it. so that when i installed it, it looks like the picture below. would be great if you could post a pic tutorial. btw i can run my adb anywhere since i configured it for fastboot but i still cant find my device. bummer.
playvinci said:
Is this how you added your drivers in the .ini file? Also did you have problems loading the drivers because when I installed it (win 7 64bit) it says its unsigned and said something about having a problem installing it. so that when i installed it, it looks like the picture below. would be great if you could post a pic tutorial. btw i can run my adb anywhere since i configured it for fastboot but i still cant find my device. bummer.
Click to expand...
Click to collapse
In my case, at last I got a win 7 32bit, because I wasn't able to make it work on my 64bit.
I followed this tutorial (Google: "Root Android 4.0 (Novo método) Atualizado x3") to root it, which points to the drivers ( ge.tt/8hWh71S/v/0 ). Though this zip file has 64bit drivers, in my case they didn't work properly, I saw the same screen you post.
Regarding the .ini file, you should put only (I have that myself):
0x1782
In brief, I got the drivers, installed them on a win 7 32bit, and followed the tutorial above. Don't know which could be the problem with my 64bit system
I hope it helps.
Anyway, now I'm stuck with my system rooted. I don't know how to flash a CWM recovery image, nor how to flash a new ROM, because every app I tried to do it ( Mobile Odin, ROM Customizer, ROM Manager,... ) does not detect the phone, so it is unsupported and does not let me flash it .
If someone could help it would be greatly apreciated.
sergimas said:
In my case, at last I got a win 7 32bit, because I wasn't able to make it work on my 64bit.
I followed this tutorial (Google: "Root Android 4.0 (Novo método) Atualizado x3") to root it, which points to the drivers ( ge.tt/8hWh71S/v/0 ). Though this zip file has 64bit drivers, in my case they didn't work properly, I saw the same screen you post.
Regarding the .ini file, you should put only (I have that myself):
0x1782
In brief, I got the drivers, installed them on a win 7 32bit, and followed the tutorial above. Don't know which could be the problem with my 64bit system
I hope it helps.
Anyway, now I'm stuck with my system rooted. I don't know how to flash a CWM recovery image, nor how to flash a new ROM, because every app I tried to do it ( Mobile Odin, ROM Customizer, ROM Manager,... ) does not detect the phone, so it is unsupported and does not let me flash it .
If someone could help it would be greatly apreciated.
Click to expand...
Click to collapse
Thanks Sergimas. I havent tried with a 32 bit yet. I guess I'll borrow my friend's laptop for this and see if it works. BTW... with the .ini file, when you said i should only put "0x1782", that does mean that's the only hex code i need to place on the file and delete the rest? Appreciate much for your reply.
EDIT: So i finally got my adb recognize the device and was able to list the device id however when i used the doomlord and/or he portugese root, it said it wasnt able to root it.
EDIT: Lol so yeah. I dont know what I did but i was able to root my phone using the x64 files that sergimas gave and get this, I still have the yellow icons on both spreadtrum coms (general and vendor)! I mean its freakin yellow!
(If you right click on prorperties it still would show this error) " The drivers for this device are not installed. (Code 28)
Driver is not intended for this platform.
To find a driver for this device, click Update Driver."
I think what I did was, rather than update the first spreadtrum line with google's own file via sdk, I used the composite device that came from "jungo". Then I loaded Doomlord and viola it granted me superuser access! And just when I was about to give up. Lmao.
playvinci said:
Thanks Sergimas. I havent tried with a 32 bit yet. I guess I'll borrow my friend's laptop for this and see if it works. BTW... with the .ini file, when you said i should only put "0x1782", that does mean that's the only hex code i need to place on the file and delete the rest? Appreciate much for your reply.
EDIT: So i finally got my adb recognize the device and was able to list the device id however when i used the doomlord and/or he portugese root, it said it wasnt able to root it.
EDIT: Lol so yeah. I dont know what I did but i was able to root my phone using the x64 files that sergimas gave and get this, I still have the yellow icons on both spreadtrum coms (general and vendor)! I mean its freakin yellow!
(If you right click on prorperties it still would show this error) " The drivers for this device are not installed. (Code 28)
Driver is not intended for this platform.
To find a driver for this device, click Update Driver."
I think what I did was, rather than update the first spreadtrum line with google's own file via sdk, I used the composite device that came from "jungo". Then I loaded Doomlord and viola it granted me superuser access! And just when I was about to give up. Lmao.
Click to expand...
Click to collapse
Happy to read it, I didn't even try it with the yellow marks :laugh:
sergimas said:
I've managed to install them on a 32-bit windows 7. Everything I tried on 64-bit just showed the yellow mark, although they where the x64 version drivers.
Regarding the rooting process, I followed this method (As I cannot post outside links yet, just Google: "Root Android 4.0 (Novo método) Atualizado x3") and it worked at last. It's written in portuguese but it's not too difficult to follow looking at the video.
I hope it helps a bit.
Now I was trying to install a custom CWM recovery, prior to install a custom ROM, but I really don't know which one should I use (nor CWM recovery nor ROM)
If someone can point me in any directions on how to continue, it would be great.
---------- Post added at 11:53 PM ---------- Previous post was at 11:46 PM ----------
I guess it won't be the same, but I was having problems with my Play Store also. It did not loaded anything, just giving "Unable to connect" problems, and it was solved (momentarily) uninstalling all updates. That's going back to Android Market, though it updates itself afterwards to Play Store again. You can do it in Applicatins > Manage Applications > Google Play Store, and push the button "Uninstall updates".
As I said, i think it's not the same issue, but I just wanted to share it, just in case.
Click to expand...
Click to collapse
Thanks but as you said yourself, it's not the same issue :/
I've made some discoveries regarding the problem.
After i've got the root access i removed some system apps that i wouldn't use or that i wanted update the system app.
These are the removed apps:
- Download Provider UI
- Email
- ES File Explorer
- My Favorites
- Playtalk
- Water Locker
- Sprd Note
After that the phone bricked, i've made a forced reboot via adb, and when it came back the screen didn't stop blinking, so i've put everything back and started removing one by one, it turned out that the "Playtalk" was the one that couldn't be removed.
With the issue solved, i discoverd that my market/play store didn't work, and that i could'nt realize any download from the browser, so I re-installed everything again and did a factory reset, but it didn't work to solve the problem, after searching a lot, I noted that in my system apps there is no "dowload provider.apk" only the "download provider ui.apk" that i removed in the beginning, and i'm thinking thats the problem with browser, but I don't know if it is the same problem of the market/play store because it don't even open, when i tap the icon, the screen shows: Loading, then it closes, with the "the application stopped unexpectedly" but it don't even "wait" for me to force stop, I just get back to the app laucher screen.
So, If anyone has anything for me to try to solve the issue, it will be awesome 'cause i'm trying to solve it more than 2 weeks.
PS. I already tried to install the "download provider.apk" but every version I try i get the same two problems:
- Incompatible Shared User
or
- Older SDK.
Ps 2. Regarding the market/play store issue, i already tried to clear the data/cache and neither of them work.
H_Bler said:
I've made it. *so ****ing happy right now*
Solutions:
To - Device adb recognition.
Place Hardware ID VID_xxxx in {user home}/.android/adb_usb.ini.
Font
Subscribing the adb.exe files Download Here
Font
To - Rooting
I've used one of the previos methods i've tried
DooMLoRD ROOT v4
Thanks for the tipo karimkahale
And now i'm going to enjoy my 3 sleepless days victory.
Click to expand...
Click to collapse
thank you for sharing the info. i have the same phone and have been trying to research on how to root it as well. i've tried my best to understand your instructions but i just can't seem to get it. would you mind doing a walk through of the whole procedure? what files/tools do i need and how do i use them? i also can't seem to download the doomlord tool, i always get an error saying that the source file is damaged. i will appreciate any help. thanks in advance.
Hi, does anybody have any idea on how to root this? On their website they have an updater tool which says to get it into recovery you must push power and volume button only there is no volume button.. only physical button is a power button and then there is a reset hole in the back of the tablet. http://www.easypix.eu/smartpad750_en.html
I would like to at least root it and then see if there are any developers for this model.
Thanks.
I found a question from someone who has broken their same model tablet which was rooted, so it is possible.
You can get the proper windows drivers and connect to it through ADB. Using this method you can push clockwork mod touch, and the touch interface should work fine. You might have to use ADB terminals for keypresses as it starts though, I'm not sure how you would boot into recovery without a rom. But once in a rom, you can always select the reboot into recovery option.
do you have any guide for this, Im more just interesting in rooting it to start with. I think I figured out how to get it into some sort of recovery mode but windows wont let me install the recovery mode drivers so I cant do anything
bump
I just rooted it with unlockroot.com , It works for any tablet with the rockchip 2906 (Rk29).
Kevinjs said:
do you have any guide for this, Im more just interesting in rooting it to start with. I think I figured out how to get it into some sort of recovery mode but windows wont let me install the recovery mode drivers so I cant do anything
Click to expand...
Click to collapse
Hi there. Do you mind sharing the info how to get it into some sort of recovery mode . And with the tool from that web site. Was it difficult to do?
ADB does not find Easypix Smartpad EP750
Kevinjs said:
I just rooted it with unlockroot.com , It works for any tablet with the rockchip 2906 (Rk29).
Click to expand...
Click to collapse
It seems impossible for me, I installed the driver, now in the Windows device-manager you can find a "Class for rockusb devices" and there a "RK29 Device" but adb seems not fo find it.
While I see the device in my Windows device manager I pushed the Root-button from the unlockroot.com - tool, but after it tried to check via ADB there comes a popup "not detected any device ..."
Checking it with Ubuntu-Linux with the lsusb - command, this tablet has NO NAME, I can find the VendorID and the ModelID but after that, there is NOTHING , all other USB-Devices do have a name after its IDs, and trying to check via Davlik Debugging Monitor (ddms) you have to chose the name of your device,
but it is impossible to me, because I cannot chose NOTHING to use NOTHING with ADB ... has anybody an idea, how it may work, or has anybody a working ROM on his Easypix Smartpad EP750 which has root or at least a name ?
Maybe anybody has a working udev - entry for Linux ... pls post it here !!!
Under Windows I am able to flash the device with its own flashing-tool (RKBatchTool) but since now I did not find any ROM which I can flash instead of the original ROM - the latest I downloaded from Easypix-WebSite = 750_20120621 with Android 4.04 but no root-access,
I tried to flash a CM9, but the RKBatchTool told, that was no possible ROM for that device .....
ProJerem said:
It seems impossible for me, I installed the driver, now in the Windows device-manager you can find a "Class for rockusb devices" and there a "RK29 Device" but adb seems not fo find it.
While I see the device in my Windows device manager I pushed the Root-button from the unlockroot.com - tool, but after it tried to check via ADB there comes a popup "not detected any device ..."
Checking it with Ubuntu-Linux with the lsusb - command, this tablet has NO NAME, I can find the VendorID and the ModelID but after that, there is NOTHING , all other USB-Devices do have a name after its IDs, and trying to check via Davlik Debugging Monitor (ddms) you have to chose the name of your device,
but it is impossible to me, because I cannot chose NOTHING to use NOTHING with ADB ... has anybody an idea, how it may work, or has anybody a working ROM on his Easypix Smartpad EP750 which has root or at least a name ?
Maybe anybody has a working udev - entry for Linux ... pls post it here !!!
Under Windows I am able to flash the device with its own flashing-tool (RKBatchTool) but since now I did not find any ROM which I can flash instead of the original ROM - the latest I downloaded from Easypix-WebSite = 750_20120621 with Android 4.04 but no root-access,
I tried to flash a CM9, but the RKBatchTool told, that was no possible ROM for that device .....
Click to expand...
Click to collapse
How did u manage to flash through windows? i have one of these tablets that was handed out with some ****ty program that has been installed by a medical company to give out to patients , with a load of information about certain medical conditions, a load of ****e basically, i want to flash the original rom in order to wipe this crap program from it to allow me to use it as a normal tab . I managed to install the driver but cannot get it into any form of recovery mode in order for the device to show in the flashing program . Any help appreciated
hi i was wondering if you could let us no if it worked for you as i have 3 of them with pattern key lock and its saying im putting in the wrong email address which is the correct 1 and i can find any information to help me remove them.
Alright, here goes my first post. I have lingered in these forums for awhile, and have always found what I needed. This is the first time my searching on here, as well as google, has let me down.
To clarify, if I connect to my computer and have USB Mass Storage on, I can see it, move files to it and everything. My problem is, I am using my old phone (P500) to learn and practice ADB (I own a GNEX), and would like to install CWM via ADB, but I need to move files to the root of my sd.. but my phone won't show up if it's in debugging mode!
I have the drivers installed, and used a toolkit to root (worked fine, no errors). Am I missing something here or is there another issue?
Info:
Windows 7 64bit
Telus Mobility (Canada)
Model: LG-P500h
Android 2.3.3 (stock)
stock kernel
MissBizz said:
Alright, here goes my first post. I have lingered in these forums for awhile, and have always found what I needed. This is the first time my searching on here, as well as google, has let me down.
To clarify, if I connect to my computer and have USB Mass Storage on, I can see it, move files to it and everything. My problem is, I am using my old phone (P500) to learn and practice ADB (I own a GNEX), and would like to install CWM via ADB, but I need to move files to the root of my sd.. but my phone won't show up if it's in debugging mode!
I have the drivers installed, and used a toolkit to root (worked fine, no errors). Am I missing something here or is there another issue?
Info:
Windows 7 64bit
Telus Mobility (Canada)
Model: LG-P500h
Android 2.3.3 (stock)
stock kernel
Click to expand...
Click to collapse
Since the device is not getting detected with USB Debugging enabled it's safe to assume a bad driver installation. To verify tho, enable USB Debugging on the device and connect it to your PC. Go to Device Manager. Somewhere towards the top, assuming the drivers were installed will be a device "ADB Interface" with a subitem "Android Platform Sooner Single ADB Interface" or something similiar. If the "ADB Interface" item isn't there then the drivers weren't installed correctly. Uninstall them. Reboot computer. Rerun driver installation program. When it finished, reboot your PC. Power off the device. Connect it to your PC. Power on the device and let all drivers install. You should be good to go from here.
If you'd like a good known set of LGE USB drivers, download Android Flash Recovery, link is in my signature. Hope this helps.
EDIT:
Oh, and Welcome to XDA
This was done on a stock rom (works for 4.4)
I unlocked my bootloader first
http://forum.xda-developers.com/showthread.php?t=2363025&page=1
(you need to do the driver part for adb) (Windows 8 may need to change the "Samsung device", and set the driver to be "Android Bootloader Interface")
if you get a "error: device not found" your drivers are not setup, or you didn't accept the cert on the phone.
Thanks broodplank1337
Download root from
http://download.chainfire.eu/supersu
or for more info read here
http://forum.xda-developers.com/showthread.php?t=1538053
and put it in "C:\adb\sdk\platform-tools" (this is my adb.exe folder)
Download the "Samsung Galaxy S4 (i9505) / Download Recovery" from below
http://www.clockworkmod.com/rommanager
save the recovery-clockwork-6.0.4.4-jfltexx.img to the folder "C:\adb\sdk\platform-tools"
Now open up a command prompt (I did this as "run as administrator")
type "cd C:\adb\sdk\platform-tools" (or what ever the directory you extract your files)
enter this command
adb reboot bootloader <enter>
(or hold vol+/- while booting)
Once in bootloader,
In the command prompt type:
fastboot boot recovery-clockwork-6.0.4.4-jfltexx.img (this takes 1min to load after the file is sent)
This will boot into ClockworkMod
goto "install zip"
goto "install zip from sideload"
in the cmd type
adb sideload UPDATE-SuperSU-v1.80.zip
This sends to the phone and write to the phones Rom.
Now reboot, if asked, select no about the stock recovery overwriting the phone
when you boot into the OS download SuperSu from the market
and we have root without ODIN on a I9505G
I disappear alot and i DON'T read everyone's post
I update this when i need re-root
Sorry for the errors in this post
1. I still receive OTA Update with this root (I had to "clear data" on the "Google Service Framework" and then check for updates).
2. As long as you don't flash a different recover it should allow you to apply new updates. The first time i applied a update it failed half way though it. My phone booted but i could install any apps. It only worked after i put the recovery back and re-updated.
3. Once you have root you can flash a recovery using DD in the shell (backup the recovery first) read "[HOWTO] dump your rom"
Good job on writing this for the i9505g users ^^. I'm glad my root zip worked! hehe
:3
Good one! :good:
btw....
Download ClockworkMod 6.0.3.3 NORMAL from below
http://forum.xda-developers.com/show...light=recovery
aka Miustone_CWM_flash-NORMAL.zip
extract the recovery.img to the folder "C:\adb\sdk\platform-tools"
Click to expand...
Click to collapse
your link is not working... this LINK here is working
hey thanks!!
will give it a try tonight!
Will this work on 4.3?
Sent from my GT-I9505G using xda premium
Attempting to do this and for the life of me I can not get adb sideload to work correctly.
when my device is booted I can see it with adb however when I boot into recovery adb doesn't see the device. I have tried unplugging/plugging the cable on my phone.
I want to get this working so that I can root my device and make a backup of my stock images since I just got the 4.3 OTA. When I first got the phone I managed to flash TWRP on it and then put the SU file on the internal memory and flash it from there but I want to get a backup of the stock recovery before going that route in case there is a 4.4 update at a later point.
So could anyone please tell me what I am doing wrong. When my phone is in recovery my computer sees it but adb doesn't.
I am using windows 7 and (I believe) the latest tools from google. I got them right after I got the GES4 so they are at most a month old.
ChaoticUnreality said:
when my device is booted I can see it with adb however when I boot into recovery adb doesn't see the device. I have tried unplugging/plugging the cable on my phone.
Click to expand...
Click to collapse
Try re-installing the USB drivers while in recovery mode.
Start --> Control Panel --> Device Manager, then find and right-click the "SAMSUNG" or "MSM..." unrecognized device with the yellow exclamation point, choose "Update Driver Software" option, then "Browse my computer", then "Let me pick from a list of device drivers on my computer", then if presented with a list of categories select "All devices", then click "Have Disk..." button, and point to the same place where you downloaded the drivers. Pick "SAMSUNG Mobile USB Composite Device" and click Next. It may complain about the driver not being digitally signed, select "Install anyway."
Chahk said:
Try re-installing the USB drivers while in recovery mode.
Start --> Control Panel --> Device Manager, then find and right-click the "SAMSUNG" or "MSM..." unrecognized device with the yellow exclamation point, choose "Update Driver Software" option, then "Browse my computer", then "Let me pick from a list of device drivers on my computer", then if presented with a list of categories select "All devices", then click "Have Disk..." button, and point to the same place where you downloaded the drivers. Pick "SAMSUNG Mobile USB Composite Device" and click Next. It may complain about the driver not being digitally signed, select "Install anyway."
Click to expand...
Click to collapse
I'll have to try that when I get home. thanks.
ChaoticUnreality said:
I'll have to try that when I get home. thanks.
Click to expand...
Click to collapse
Another quick trick that has worked for me in the past is to simply plug the cable into a different USB port on the computer. Does the same thing as the other suggestion without going through the extra steps. Either way should resolve your problem.
Finally got a chance to try this worked perfectly once I changed USB ports and redid the drivers. Thanks
Great write-up
This was my first ever root on my first ever Android device. It went well.
There were a couple things confusing about the post, I just want to make sure I did things correctly.
]Link to Brood's unlocking the bootloader - Was that just to get the USB drivers installed? I didn't use that Clockworkmod or root.zip file
Not selecting yes on final reboot - With so many "no's", I thought it best to not say yes. Does that mean that if there's another OTA update, root will be lost and have to be redone?
Besides that, the biggest issue was getting good USB drivers. Visiting the Samsung site shows zero downloads for the i9505G phone, so I ended up getting the drivers from "phones-usb-drivers.blogspot.com" (can't post links yet), search Google for "free-download-samsung-gt-i9505g-galaxy", it should be a top hit. The actual download was from Samsung, and that got the drivers working for regular operation and the bootloader.
However, I couldn't find drivers that worked for the sideload of the SuperSU. Ended up having to add entries to the Google USB driver (android_winusb.inf) with the VID and PID values. Here's what I added to the x64 section, in case it helps someone else out:
Code:
;Samsung i9505G (GAA attempt to get adb drivers working)
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&MI_01
At that point when it booted into CWM recovery, I installed the drivers and was able to complete.
Now the happy owner of SuperSU running phone. Thanks again warwolfx0
I hope no one minds, but, I automated this.
<see new version later in thread>
Download that, extract it to a folder, install Koush's universal ADB driver in the ADB_USB folder, and then execute the run.bat and follow instructions.
Credits:
warwolfx0 for the OP
Koush for the universal ADB driver found here: https://github.com/koush/UniversalAdbDriver
warwolfx0 said:
Now reboot, if asked, select no about the stock recovery overwriting the phone
and we have root without ODIN on a I9505G
Click to expand...
Click to collapse
Sorry for what might be a stupid question, but I was not 100% sure based on how you word this.
So, if we follow your method, will we leave stock google recovery intact? I.e. we aren't overwriting it with cwm recovery? If so, that would be nice. All my other rooted devices I've installed custom recovery, but it would be nice to leave this one 100% stock except for the rooting.
Thanks.
Correct.
Etched in blood by a katana
Chahk said:
Try re-installing the USB drivers while in recovery mode.
Start --> Control Panel --> Device Manager, then find and right-click the "SAMSUNG" or "MSM..." unrecognized device with the yellow exclamation point, choose "Update Driver Software" option, then "Browse my computer", then "Let me pick from a list of device drivers on my computer", then if presented with a list of categories select "All devices", then click "Have Disk..." button, and point to the same place where you downloaded the drivers. Pick "SAMSUNG Mobile USB Composite Device" and click Next. It may complain about the driver not being digitally signed, select "Install anyway."
Click to expand...
Click to collapse
I had the same problem but was able to get it working by following the above instructions but then selecting “SAMSUNG Android Phone,” followed by “SAMSUNG Android ADB Interface." (I didn't have an option for "SAMSUNG Mobile USB Composite Device.")
I just rooted my phone following these instructions and it all worked great. Does anyone know if a phone that's been rooted like this will be able to accept and install an OTA update?
Thanks, Alan
carrot34 said:
I just rooted my phone following these instructions and it all worked great. Does anyone know if a phone that's been rooted like this will be able to accept and install an OTA update?
Thanks, Alan
Click to expand...
Click to collapse
Yes.
carrot34 said:
I just rooted my phone following these instructions and it all worked great. Does anyone know if a phone that's been rooted like this will be able to accept and install an OTA update?
Thanks, Alan
Click to expand...
Click to collapse
SamuriHL said:
Yes.
Click to expand...
Click to collapse
I don't have the 9505G yet (couple more days!), but there was a similar issue/discussion on the Nexus 7 board recently, and it was determined that if you were using SuperSU versions prior to 1.55 (which just came out in like the last 24 hours), the root would indeed block OTA's (because of an immutable system flag which was being inadvertently/unnecessarily set by the root process).
Discussion here.
But again, SuperSU 1.55 which just came out fixes the problem, so OTA's will indeed work again. So if you ever get stuck with an OTA, make sure to update SuperSU to latest first.
This is all assuming that the same issue would have presented itself on 9505G, which I would think it might. If not, then ignore this post.
Apparently we also have a device specific Odin flashable auto-root file.
The link below goes to ChainFire's website. The zip includes a version of odin.
http://download.chainfire.eu/348/CF-Root/CF-Auto-Root/CF-Auto-Root-jgedlte-jgedlteue-gti9505g.zip
occupational_hazard said:
Apparently we also have a device specific Odin flashable auto-root file.
The link below goes to ChainFire's website. The zip includes a version of odin.
http://download.chainfire.eu/348/CF-Root/CF-Auto-Root/CF-Auto-Root-jgedlte-jgedlteue-gti9505g.zip
Click to expand...
Click to collapse
We do. I got to test it yesterday and it works great. Restores the proper stock recovery when finished.
Sent from my Xoom using Tapatalk 4
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