Database Info

[Q] ROOT Smartpad ep750

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.

[Q] USB BOS descriptor failed, "waiting for device", "Device cannot start. (Code 10)"

[Q] USB BOS descriptor failed, "waiting for device", "Device cannot start. (Code 10)"
Hello
The situation:
I'm trying to relock the bootloader and flash RUU, so that I can get rid of the tampered flag and start over.
I'm trying to use Hasoon2000's Toolkit to do this, but I'll try any method that sounds reasonable.
When I connect the HTC One S to the PC (running Windows 8) and select 'Mount as disk drive', the PC recognizes the device, and I can explore it. Using Hasoon's toolkit I select "Relock Bootloader" and click "Do Command". A first command prompt pops up, then my phone goes into fastboot, then I close the first prompt, then a second prompt follows and says "waiting for device".
I enter the Device Manager -> "Android USB Devices" -> "My HTC", -> Right click -> "Properties". In the Device Status field it says:
"This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
EXTRA INFO:
I didn't use Hasoon's toolkit to unlock the bootloader, I actually used the platform-tools from the SKD bundle thru the terminal on a mac pc. Then I flashed CWM onto the One S using "./fastboot flash recovery recovery_thefilename.zip". Then I reloaded bootloader, selected Recovery, then my phone's screen went black, turned back on, and I saw the Red Triangle with the Exclamation mark. According to a "How to" blog, which I didn't read until after the fact, I was supposed to hold down the power button and volume button at that point in time, but I didn't. I had no idea what was going on. I pressed the power button and my phone restarted, and now every time I reboot to recovery mode, it just restarts the phone and says "This build is for development purposes only. Any redistribution will result in legal action." or something like that.
OK THAT'S ALL.
I appreciate any help!
jire

The text in red is normal if you have a custom recovery.
Just get the device in fastboot USB mode.
Check with command: fastboot devices
To see if it is connected. I should return you sn number.
(Since you manually unlocked, this should be easy for u.)
Then manually flash a correct recovery (or use the toolkit with the custom option). Reboot in recovery. Flash ROM.
Verstuurd van mijn One S met Tapatalk

Can you try to execute fastboot oem lock command on Windows OS which have hTC drivers installed? I guess that you using Linux OS now... Just install Windows in VM and hTC drivers, adb and fastboot you can download on htcdev.com or from android bundle package... I'm pretty sure that you have problem with your drivers...
Sent from quietly brilliant HTC One S

USB 3.0 might be the issue
Hey guys, thanks for trying to help me out here, I appreciate it a bunch!
Before I go any further. I think I've learned what the problem is. Well, first of all, if you didn't catch it, I've been working thru this on both win and apple computers.
Hasoon's toolkit is only available for windows. Therefore, if I said/say I did something with his toolkit, that means I was using my win computer, which is actually a Surface Pro, which has USB 3.0 === THE PROBLEM
According to this: http://forum.xda-developers.com/showthread.php?p=29286429
Unfortunately, I haven't been able to test this hypothesis, yet, because I first need to find a win pc with USB 2.0. [Fact: I couldn't get androidfiletransfer.app to recognize my htc one S on my mac. Coincidence?]
real187: When you say to install a "correct" recovery, are you implying I currently have an incorrect recovery on my phone?
mikronac: I have virtually no experience with command prompt. I just got my Surface Pro last week :laugh: and I'm geeking out...So, what I'm saying is I don't know how to do "fastboot oem lock command" ... The htc drivers are installed, up-to-date and operating without a hitch.

It can't be problematic your usb 3.0.
Please deinstall your phone drivers and install them again...
If you know how to navigate to platform tools folder in Windows Explorer, only what you need to do is to hold shift key on keyboard and right click on mouse and select option open command prompt here. Than you type :
Adb devices
Response should be serial number of phone
Adb reboot bootloader (uab debugging must be enabled)
When it reboot in fastboot, type in cmd:
Fastboot oem lock
Sent from quietly brilliant HTC One S

I can confirm: It is USB 3.0
Hi, today I faced similar problem while trying to put my Sony Xperia S into fastboot. Only after finding this topic and switching from USB3.0 port to USB 2.0 did I manage to boot into fastboot. I have not tested, if I can boot into fastboot now, that the driver has been correctly installed via USB 2.0, but to avoid any troubles I suggest everyone to stick with USB2.0 for now.
I found this topic as I had the exact same error in Device Manager as OP in this topic.

maatriks said:
Hi, today I faced similar problem while trying to put my Sony Xperia S into fastboot. Only after finding this topic and switching from USB3.0 port to USB 2.0 did I manage to boot into fastboot. I have not tested, if I can boot into fastboot now, that the driver has been correctly installed via USB 2.0, but to avoid any troubles I suggest everyone to stick with USB2.0 for now.
I found this topic as I had the exact same error in Device Manager as OP in this topic.
Click to expand...
Click to collapse
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.

No USB 2.0
Aciong.Aksaya said:
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.
Click to expand...
Click to collapse
Hi,
I don't have USB 2.0 in my laptop.
Could you please help me how to proceed with USB 3.0?
Thanks in advance

dsuresh89 said:
Hi,
I don't have USB 2.0 in my laptop.
Could you please help me how to proceed with USB 3.0?
Thanks in advance
Click to expand...
Click to collapse
Problem solved with USB 3.0.
uninstall your 3.0 USB xtensible host controller driver provided by microsoft and install driver from INTEL.
Enjoy...

dsuresh89 said:
Problem solved with USB 3.0.
uninstall your 3.0 USB xtensible host controller driver provided by microsoft and install driver from INTEL.
Enjoy...
Click to expand...
Click to collapse
hey
there is no driver for 3.0 USB xtensible host controller for windows 8
and I already have a usb 2 but I have the same problem
I think that it came from windows 8
Thanks in advance

Unable to fastboot in Windows 8.1
Aciong.Aksaya said:
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.
Click to expand...
Click to collapse
Hey Bro,
I am facing the same issue. Unfortunately I don't have a USB 2.0 port in my computer. Im struggling to flash the boot file.
Please help

jire0006 said:
Hello
When I connect the HTC One S to the PC (running Windows 8) and select 'Mount as disk drive', the PC recognizes the device, and I can explore it. Using Hasoon's toolkit I select "Relock Bootloader" and click "Do Command". A first command prompt pops up, then my phone goes into fastboot, then I close the first prompt, then a second prompt follows and says "waiting for device".
I enter the Device Manager -> "Android USB Devices" -> "My HTC", -> Right click -> "Properties". In the Device Status field it says:
"This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
jire
Click to expand...
Click to collapse
I know it has been a long time but I just encountered the same problem with fastboot, an HTC One S and Windows 8.1. These steps from Microsoft (a registry edit workaround) enabled my computer to recognize the device and got fastboot seeing it too:
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
I'll paste the workaround here in case Microsoft take the page down:
To apply the workaround for a specific device, add a REG_DWORD value named SkipBOSDescriptorQuery that has a value of 1 to the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\usbflags\vvvvpppprrrr
(where vvvv is the device's Vendor ID, pppp is the device's Product ID, and rrrr is the device's Revision number. You can get the VID/PID/REV numbers from the device manager's details tab. This number is encoded in the HardwareIDs of the device)
1. Click Start, click Run, type regedit in the Open box, and then click OK .
2. Locate and then click the following subkey in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\UsbFlags
3. On the Edit menu, point to New, and then click Key.
4.Type the name of the new key in the following form:
vvvvpppprrrr
where
vvvv is a 4-digit hexadecimal number that identifies the vendor (idDevice from the USB Deviceescriptor),
pppp is a 4-digit hexadecimal number that identifies the product (idVendor from the USB Device Descriptor)
rrrr is a 4-digit binary-coded decimal number that contains the revision number of the device
(bcdDevice from the USB Device Descriptor).
5. On the Edit menu, point to New, and then click DWORD (32-bit) Value.
6. Type SkipBOSDescriptorQuery for the name of the DWORD Value, and then press ENTER.
7. Right-click SkipBOSDescriptorQuery, and then click Modify.
8. In the Value data box, type 1 , and then click OK.
9. Exit Registry Editor.
10. Unplug and re-plug the device for the workaround to take effect.
Click to expand...
Click to collapse
On mine that meant editing a registry key called 0BB40FF00100 that already existed.

windows 8 have a issue with ville fastboot... please make you sure you have a fix

zoodles said:
I know it has been a long time but I just encountered the same problem with fastboot, an HTC One S and Windows 8.1. These steps from Microsoft (a registry edit workaround) enabled my computer to recognize the device and got fastboot seeing it too:
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
I'll paste the workaround here in case Microsoft take the page down:
On mine that meant editing a registry key called 0BB40FF00100 that already existed.
Click to expand...
Click to collapse
THANK YOU SO MUCH. Fixed for me on HTC Magic

..
Problem is caused by Windows 8 and Windows 10. Just no compatibility for old hardware.. I'm disappointed from Microsoft Windows.
---------- Post added at 10:41 PM ---------- Previous post was at 10:17 PM ----------
Problem is caused by Windows 8 and Windows 10. Just no compatibility for old hardware.. I'm disappointed from Microsoft Windows. Btw, I tried all methods in forums and in YouTube too (updating USB Root Hub drivers). Nothing helps, just "Failed device enumeration". Windows 10.. I will go back to Win7, fortunately I don't have license for 10.. Pray about these who has...

Bruh, this worked like magic on my HTC One X+ !!!
Using Windows 10 Enterprise Build 17134 by the way
Thanks a lot!

Thank you very much bro. HTC One V good working.

[Q] Toshiba AT300SE-101 root

Hi,
Can I root my toshiba AT300SE-101 ?
Regards,

sdancer said:
Hi,
Can I root my toshiba AT300SE-101 ?
Regards,
Click to expand...
Click to collapse
Your lucky day
http://forum.xda-developers.com/show...php?p=42594876

Describe the steps
tasos66 said:
Your lucky day
http://forum.xda-developers.com/show...php?p=42594876
Click to expand...
Click to collapse
Tassos, can you please describe the steps you followed ?
Also verify or better upload the appropriate files to an upload server like rapidshare.
1) I changed the usb connection to debugging mode from settings of my tablet [AT300SE-101]
2) I installed the toshiba's WinUsb Driver [successfully installed]
3) I executed the motochopper's script run.bat and responded as this
deamon not running.starting it now on port 5037 *
deamon started successfully
stays here and nothing more !!

sdancer said:
Tassos, can you please describe the steps you followed ?
Also verify or better upload the appropriate files to an upload server like rapidshare.
1) I changed the usb connection to debugging mode from settings of my tablet [AT300SE-101]
2) I installed the toshiba's WinUsb Driver [successfully installed]
3) I executed the motochopper's script run.bat and responded as this
deamon not running.starting it now on port 5037 *
deamon started successfully
stays here and nothing more !!
Click to expand...
Click to collapse
Did you try using ADB Wifi? I've been able to do stuff with ADB wifi before. Not sure if this will work or not...but it's something worth trying..

sdancer said:
Tassos, can you please describe the steps you followed ?
Also verify or better upload the appropriate files to an upload server like rapidshare.
1) I changed the usb connection to debugging mode from settings of my tablet [AT300SE-101]
2) I installed the toshiba's WinUsb Driver [successfully installed]
3) I executed the motochopper's script run.bat and responded as this
deamon not running.starting it now on port 5037 *
deamon started successfully
stays here and nothing more !!
Click to expand...
Click to collapse
If you get this message and stack, then the adb driver is not installed correctly.
Connect the tablet to the computer.
Go to device manager, find an unknown device, right click and select update driver, select browse the computer for the driver and guide it to the folder you placed the adb driver.
When the unknown device mark is gone, you are ready to try again.
Use the following Motochopper http://mirror21.downloadandroidrom.com/download/GalaxyS4/root/motochopper.zip?token=

I dont know whats the problem.... but dont work

tasos66 said:
If you get this message and stack, then the adb driver is not installed correctly.
Connect the tablet to the computer.
Go to device manager, find an unknown device, right click and select update driver, select browse the computer for the driver and guide it to the folder you placed the adb driver.
When the unknown device mark is gone, you are ready to try again.
Use the following Motochopper
Click to expand...
Click to collapse
Hi
I already did this and win7 recognise the device as android Device --> Android ADB Interface. It says that this device works just fine.
Model Number AT300SE
Android version 4.1.1
Kernel version 3.1.10-00037-g59264fc
Build number JRO03C.000122808.95
Despite of that, in my computer device list i dont see anything only in the device manager as described before.
PS:How to work with ADB wifi ?
Sent from my AT300SE using xda app-developers app

tasos66 said:
If you get this message and stack, then the adb driver is not installed correctly.
Connect the tablet to the computer.
Go to device manager, find an unknown device, right click and select update driver, select browse the computer for the driver and guide it to the folder you placed the adb driver.
When the unknown device mark is gone, you are ready to try again.
Use the following Motochopper
Click to expand...
Click to collapse
Finally, I used another PC and it worked flawlessly !
Now my Toshiba AT300SE-101 is rooted !!
Thank you Tassos from Greece !! I am from Greece too ([email protected] city)
Best Regards,

sdancer said:
Finally, I used another PC and it worked flawlessly !
Now my Toshiba AT300SE-101 is rooted !!
Thank you Tassos from Greece !! I am from Greece too ([email protected] city)
Best Regards,
Click to expand...
Click to collapse
Γεια σου πατρίδα!
Thessaloniki city.

So I decided to resurrect this old tablet and turn it into a digital photo-frame. Decided just to reset it to factory settings. Easily done. I noticed there were no firmware updates. It is stuck on Jellybean. That can't be right, surely. A tablet that doesn't update to at least one new Android update!!

[Q] How to root a Yusun W808

Hi,
I have a very unknown phone from China, the Yusun W808 It is based on a qualcomm MSM8225q chipset. I ordered it from FastCardTech and asked for a Pre-root when I placed the order.
Upon receiving I found out that the phone was not rooted... They only put some instructions on a piece of paper inside the box.
I followed the instructions but as expected, no results...
The instructions
1. Please open usb debugging and connect to your pc.
2. Download USB driver ( Snappea ) and install to your pc, when the phone is recognized, please turn snappea off.
3. Go to task manager and kill wandoujia helper process.
4. Extract root tool to your pc ( The known motochopper tool from djrbliss ) and click run.bat, then press enter on your keyboard, and just wait about 1 min, it will remind you to press enter again and then it shuts down and auto reboot. Meanwhile do not touch anything on your phone or pc or the phone will get bricked.
5.Check menu- if there is a # icon, if yes, it's rooted, or do it again.
The problem is that my phone can't be recognized by my pc. snappea says " cannot get phone stats" and motoshopper wont go further than "Daemon started successfully"
So my first thought is that the problem lies with the usb driver. I have no idea how I can get the right USB driver for this phone
Does someone has any idea how I can continue my quest here?
Thanks in advance

Yusun W808 = iNobel N1 = Ai Nuobei N1
Parameters

[DOESN'T WORK] Restore lost IMEI (IMEI=0)

Ok guys, maybe this could work for those who lost their IMEI running a "fastboot erase all" or for any other reason. It's a theoretical solution, since I can't test it on my device because my IMEI works. So don't blame me if doesn't work.
1) Go on fastboot mode (vol down + power button) and select BP Tools
2) Connect the usb cable to computer
3) Open Windows Device Manager (write "devmgmt.msc" without quotes in the Start menu)
4) You will see "Motorola QC Diag Interface, click on it and update drivers, search driver on computer, manually search, PORTS (com and lpt), Motorola, Motorola QC Diag Port
5) Now your device is correctly recognized
6) download this tool (credits to lyriquidperfection, the tool isn't mine)
10) extract and open the tool, select Qualcomm NV tools
11) chose the right com port, connect your phone and go on secure options, check IMEI box, click Read (should be 000000000000000)
12) write your IMEI and click Write
13) tell me if it works
TESTED, UNFORTUNATELY IT DOESN'T WORK.
This thread can be closed.

Anyone tried?
Please let me know if this works:cyclops:

oversleeper said:
Anyone tried?
Please let me know if this works:cyclops:
Click to expand...
Click to collapse
I too have not lost my IMEI but tried this any way two problems the IMIE was wrong in the last digit mine is 55 the tool displayed 50 when ask to write 50 the tool displayed OK but on checking the IMIE had not changed.

robin0800 said:
I too have not lost my IMEI but tried this any way two problems the IMIE was wrong in the last digit mine is 55 the tool displayed 50 when ask to write 50 the tool displayed OK but on checking the IMIE had not changed.
Click to expand...
Click to collapse
The last digit is a check digit. But if you haven't lost your imei you can't overwrite it. Should try someone with imei=0

http://forum.xda-developers.com/showthread.php?t=2675326
There is a PDS script post in the general section perhaps post a link to this method there.
Sent from my XT1032 using XDA Free mobile app

I'll give this a try in a day or so, have an IMEI=0 device.

same here. My Imei is blank when i do *#06# but using this tool my imei is correct EXCEPT the last digit shows 0 instead of the right digit being 5

oversleeper said:
Ok guys, maybe this could work for those who lost their IMEI running a "fastboot erase all" or for any other reason. It's a theoretical solution, since I can't test it on my device because my IMEI works. So don't blame me if doesn't work.
1) Go on fastboot mode (vol down + power button) and select BP Tools
2) Connect the usb cable to computer
3) Open Windows Device Manager (write "devmgmt.msc" without quotes in the Start menu)
4) You will see "Motorola QC Diag Interface, click on it and update drivers, search driver on computer, manually search, PORTS (com and lpt), Motorola, Motorola QC Diag Port
5) Now your device is correctly recognized
6) download this tool (credits to lyriquidperfection, the tool isn't mine)
10) extract and open the tool, select Qualcomm NV tools
11) chose the right com port, connect your phone and go on secure options, check IMEI box, click Read (should be 000000000000000)
12) write your IMEI and click Write
13) tell me if it works
14) if it works offer me and lyriquidperfection a beer
Click to expand...
Click to collapse
Tested Twice, sadly it's not working, still IMEI 0