Hi, I'm new to this site..
So when I could not find stock recovery I tried this so called CMW recovery touch version, and as soon as I installed it my device doesn't boot anymore. it stuck at iBall logo and stuck there forever! I tried to connect it to Computer via USB. apparently, WinXP cant not find the device or any USB device for that matter. But somehow when I hold. and press Back key and Power button, the device LED is on(means somehow alive) with a blank screen and WinXP find ?USB Device!(?)
How to I restore my tablet! please help...
This tablet is Rebranded!
Info:
Model:iBall Slide i6012
RAM:1GB
INTERNAL MEMORY:8GB
SCREEN: 800×480 CAPACITIVE TOUCH
CPU:1.2gz Allwinner A10
Android Version :ICS 4.0.4
Please help me......
I've tried "use pin to restore " and "button combination " but not luck!
Before installing this,I install another WORKING(KIND OF) cwm modified. img.
You need a recovery specific to your device, provided you flashed it to the correct, i.e. recovery, partition.
thanks
bodh said:
You need a recovery specific to your device, provided you flashed it to the correct, i.e. recovery, partition.
Click to expand...
Click to collapse
The problem is that Window can not find my device. Sometimes it only appear as USB device and other times it doesn't recozniged at all. I tried updating ADB driver but that dont do any help...
http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1 try these.
also, "A. Install the drivers
1) Do not install the Samsung drivers or the pdanet drivers, or any other driver you come across. If you have, and you are SURE they are working properly, fine, leave them. Otherwise uninstall them if you are unsure;
2) Download the drivers from here;
3) Install the drivers. This step is the only part of the entire process that is not easy to explain, and may cause users some issues, depending on what drivers they had installed previously, what OS they are using, etc. etc. Bourne-nolonger has put together a very detailed step-by-step on how to install them. If you don't know how to install them, have a look at his post here. Note that the driver has to install twice: once when your device is booted normally (not required for this tutorial) with USB Debugging enabled in Settings, and once when your device is booted in fastboot (i.e., bootloader) mode (which is required for this tutorial). If you are using Windows 8, you will need to do this before installing the drivers."
from http://forum.xda-developers.com/showthread.php?t=1626895
I'll try it!
bodh said:
http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1 try these.
also, "A. Install the drivers
1) Do not install the Samsung drivers or the pdanet drivers, or any other driver you come across. If you have, and you are SURE they are working properly, fine, leave them. Otherwise uninstall them if you are unsure;
2) Download the drivers from here;
3) Install the drivers. This step is the only part of the entire process that is not easy to explain, and may cause users some issues, depending on what drivers they had installed previously, what OS they are using, etc. etc. Bourne-nolonger has put together a very detailed step-by-step on how to install them. If you don't know how to install them, have a look at his post here. Note that the driver has to install twice: once when your device is booted normally (not required for this tutorial) with USB Debugging enabled in Settings, and once when your device is booted in fastboot (i.e., bootloader) mode (which is required for this tutorial). If you are using Windows 8, you will need to do this before installing the drivers."
from http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
I'll try it....
USB is death!
hello again!,
I tried that and it does not work!
Computer can not even find my device.
When I plug in charger or USB cable,tab is light up and display iball logo and from there it stuck!
I mean it stuck forever!
What is APX mode?
Somehow when I press Menu and while still holding I pressed the power button simultaneously and my Computer Show "Unrecognized USB Device".
Please anyone help me. I dont even have the stock firmware to flash(if required) with!
Their Customer service is neglecting me and I'm really pisses!
Give me some light anyone
fastboot can not even open in my computer when I download and try to open! it said "can't find Winusbapi.dll"
while "winusbapi.dll" was in the same folder as the "fastboot.exe"!
I'm very new to this and it would be a great help if you can guide me to revive my only tablet!
After a little research, do you mean this recovery? [Not cwm at all] http://www.slatedroid.com/topic/35183-custom-recovery-for-c8a8m7/
Did you choose an option to flash it through partitions and storage menu? Did it allow you to back up your stock setup first (hopefully, if it is cwm-modeled)? If not, then I'm not sure I can help. Looks like your recovery is a recovery AND a kernel, packed into one [just leaned about this from a recent xda story]. I also found this: https://github.com/namko/midRecovery/downloads, with several other BETA versions. Maybe it would help you to google "iball slide". There is a stock 4.1.1 image on xda, which could also help. But overall, it looks like there is not much development for this device, and you should've researched the risks BEFORE tampering with your device!
p.s. I do not know what apx mode is. Also, is winusbapi.dll something that needs to be installed? Click it and see!
completely invisible to Computer.
Hi, can you show me the stock 4.1.1 image. I tried to find it but couldn't get it.
Please post a link here....
No, I did not flash with that modified recovery.
I'm. still amaze how a recovery.img can kill my tablet.
Im stuck in iBall logo. whenever I plug in tablet light up even if I switch it off before charging.
Window can only find my device as "Unknown USB Device ".
I updated ADB and still doesn't work.
I tried google and can not find anything other than piece by piece similarities.
all I want is to flash the stock recovery back!
I can not do it because my ADB is not recognizing my tablet!
I really appreciate your help though!
kcisrael said:
Window can only find my device as "Unknown USB Device ".
Click to expand...
Click to collapse
What ID "Unknown USB Device" in Device Manager?
I was wrong, it's an AOSP based rom; but it's a beta, and i will not recommend it, as it is probably quite far from stock. You didn't answer if that slate droid link is the recovery you took. That says it is not flashed, but rather externally booted.
This kind of recovery.img could kill a tablet in the following way: it looks as though these devices have both the kernel and the recovery together. [there's a recent xda article about a sony bootloader that addresses this.] If the kernel is bad, the device does not boot. Can you try a factory reset from your recovery's menu? So which recovery do you have, i.e. what does it say along the top?
can't see recovery menu
bodh said:
I was wrong, it's an AOSP based rom; but it's a beta, and i will not recommend it, as it is probably quite far from stock. You didn't answer if that slate droid link is the recovery you took. That says it is not flashed, but rather externally booted.
This kind of recovery.img could kill a tablet in the following way: it looks as though these devices have both the kernel and the recovery together. [there's a recent xda article about a sony bootloader that addresses this.] If the kernel is bad, the device does not boot. Can you try a factory reset from your recovery's menu? So which recovery do you have, i.e. what does it say along the top?
Click to expand...
Click to collapse
No, I did not flash with that recovery link you provided.
And I can not go beyond the "iBall" logo in the tab. So,no recovery menu. Also I tried all sort of Factory reset like "key" combination and "pinhole", none of them works!
can you help?
AllexBast said:
What ID "Unknown USB Device" in Device Manager?
Click to expand...
Click to collapse
hi,
ID:USB\VID_1F3A&PID_EFE8\5&1D3934BB&0&3
Need to remove the "Unknown USB Device" and install the driver again
No luck!
AllexBast said:
Need to remove the "Unknown USB Device" and install the driver again
Click to expand...
Click to collapse
Still the same!!!
kcisrael said:
Hi, I'm new to this site..
So when I could not find stock recovery I tried this so called CMW recovery touch version, and as soon as I installed it my device doesn't boot anymore. it stuck at iBall logo and stuck there forever! I tried to connect it to Computer via USB. apparently, WinXP cant not find the device or any USB device for that matter. But somehow when I hold. and press Back key and Power button, the device LED is on(means somehow alive) with a blank screen and WinXP find ?USB Device!(?)
How to I restore my tablet! please help...
This tablet is Rebranded!
Info:
Model:iBall Slide i6012
RAM:1GB
INTERNAL MEMORY:8GB
SCREEN: 800×480 CAPACITIVE TOUCH
CPU:1.2gz Allwinner A10
Android Version :ICS 4.0.4
Please help me......
I've tried "use pin to restore " and "button combination " but not luck!
Before installing this,I install another WORKING(KIND OF) cwm modified. img.
Click to expand...
Click to collapse
Download these USB debugging drivers...
http://www.mediafire.com/download/53vp6c6ka86rk3q/iBall_slide_Debugging_drivers.zip
and install them in your PC...
hope your PC will recognize your slide
bro how to hard reset using keys..??
kcisrael said:
hi, i'm new to this site..
So when i could not find stock recovery i tried this so called cmw recovery touch version, and as soon as i installed it my device doesn't boot anymore. It stuck at iball logo and stuck there forever! I tried to connect it to computer via usb. Apparently, winxp cant not find the device or any usb device for that matter. But somehow when i hold. And press back key and power button, the device led is on(means somehow alive) with a blank screen and winxp find ?usb device!(?)
how to i restore my tablet! Please help...
This tablet is rebranded!
Info:
Model:iball slide i6012
ram:1gb
internal memory:8gb
screen: 800×480 capacitive touch
cpu:1.2gz allwinner a10
android version :ics 4.0.4
please help me......
i've tried "use pin to restore " and "button combination " but not luck!
before installing this,i install another working(kind of) cwm modified. Img.
Click to expand...
Click to collapse
plz help me how to hard reset>>>
rundown:
Flashed skanky's cm10 onto the phone. Had been running great but performance was deteriorating. Some apps weren't working well. Previously I had cm7 on the phone so I decided to revert into that.
Booted into recovery
installed rom from mem
installed and popped up
seemed to be working fine, all my contacts would show and i could communicate over network. However, phone randomly would reboot. No warning, could be navigating in an app or anywhere....just boop....reboot.
tried to re-install once again from recovery, now I'm stuck after the samsung logo it has the "galaxyS cyanogenmod 7" logo. I'll see it flash...blank screen...then it pops up again and freezes there.
problem....can't boot into recovery
problem....installed USB drivers but still have an "unrecognized smBus and USB controller"
(which I'm sure leads to)
problem....odin doesn't recognize my device
aannn
problem....neither does sda with a "sda devices" command
suggestions?
jlangholzj said:
rundown:
Flashed skanky's cm10 onto the phone. Had been running great but performance was deteriorating. Some apps weren't working well. Previously I had cm7 on the phone so I decided to revert into that.
Booted into recovery
installed rom from mem
installed and popped up
seemed to be working fine, all my contacts would show and i could communicate over network. However, phone randomly would reboot. No warning, could be navigating in an app or anywhere....just boop....reboot.
tried to re-install once again from recovery, now I'm stuck after the samsung logo it has the "galaxyS cyanogenmod 7" logo. I'll see it flash...blank screen...then it pops up again and freezes there.
problem....can't boot into recovery
problem....installed USB drivers but still have an "unrecognized smBus and USB controller"
(which I'm sure leads to)
problem....odin doesn't recognize my device
aannn
problem....neither does sda with a "sda devices" command
suggestions?
Click to expand...
Click to collapse
try heimdall, switch usb ports, try different cables.
Hello All,
I've been reading posts from here for a long time but this is my first post.
I'm coming here as a last resort to save my Galaxy s2 (SGH-T989) which has a stock ROM.
Here's what happened.
I dropped my phone and then it got stuck in bootloop (it only boots until I see the "SAMSUNG" word animation and stops there).
At that point, ODIN 'sees' that there's a connected device; KIES keeps "connecting...." but can't actually connect; ADB does not show any connected device.
So, what I wanted to do was to factory "reset" the phone. The problem is I can't get the phone into Recovery mode. I believe it's because my volume down button was acting up when the phone was working. However, I can get to "Download Mode" using a USB Jig.
So, the next thing to do is to flash a new stock ROM. However, whenever I connect my phone when it's in "Download Mode", ODIN does not see it.
Yes, I've installed, re-installed, removed, re-installed all drivers and Kies and I've done that so many times you can't even believe it.
The problem is that the device driver "SAMSUNG Mobile USB CDC Composite Device" gives the following error "This device cannot start. (Code 10)", and I don't know why or how I can get rid of that. As mentioned above, I've tried all the device driver installation fixes but none has worked.
I mean, when the phone is not in Download Mode and I connect it to my PC, all device drivers are working fine with no error, but when it's in Download Mode, I get the error mentioned above "This Device cannot start.".
So, my questions:
1) Is there a way to get to Recovery Mode without using the button combinations? (The phone is in bootloop)
2) How can I fix the device driver error mentioned above to get ODIN to see my device?
3) Is there anything else I need to be doing?
This problem is really frustrating and I've been on it for more than 2 weeks and nothing has worked so far. Any help is greatly appreciated.
1. I think you have flashed an bad kernel if you cant get into recovery mode and i dont get it why your volume down acts like up?.
2. http://support.microsoft.com/kb/943104 try to maybe also disable kies and try again.
3. Kies is on, adb doesnt work at samsung/download screen, try to reinstall samsung usb drivers again :/ yes I know but to be sure, disable driver signature or something like that if you are on windows 8.x, try another usb cable.
2weeks dont sound good. I hope these tips could help a bit but I still wonder why your phone got in bootloop when you dropped it !?!? What were you doing at that time and did the battery go out?
wulsic said:
1. I think you have flashed an bad kernel if you cant get into recovery mode and i dont get it why your volume down acts like up?.
2. try to maybe also disable kies and try again.
3. Kies is on, adb doesnt work at samsung/download screen, try to reinstall samsung usb drivers again :/ yes I know but to be sure, disable driver signature or something like that if you are on windows 8.x, try another usb cable.
2weeks dont sound good. I hope these tips could help a bit but I still wonder why your phone got in bootloop when you dropped it !?!? What were you doing at that time and did the battery go out?
Click to expand...
Click to collapse
Thanks for the quick reply, wulsic.
1. No, I did not flash any kernel on this phone, everything on it is stock and was working just fine before it was dropped. I meant that the volume down was not working properly, not that it was acting like up.
2. I tried that but did not work
3. The drivers are working fine when the phone is not in Download Mode, it's only when it's in Download Mode that I get the error and I've tried re-installing drivers and everything, I think the problem is with the device itself not a driver problem.
I feel as if I have looked everywhere especially in these forums, but have found no answer.
I've stupidly bricked my Oneplus One by wiping off the OS, to the point where I cannot boot into recovery or bootloader. It just looks at me with a black screen. When I connect it to my laptop, there is a notifcation which says the drivers failed to installed. Also my laptop only recognises my phone as "UNKNOWN DEVICE" instead of "QHSUSB_BULK". All these guides tell me to fix my drivers. This is what it looks like in device manager. (SEE PICS)
This is what happens when I attempt to update via UPDATE DRIVER SOFTWARE>BROWSE MY COMPUTER FOR DRIVER SOFTWARE>SEARCH FOR DRIVER IN THIS LOCATION>C:\Users\Admin\Downloads\Qualcomm 2012\Qualcomm 2012\fre\Windows7>NEXT (SEE PICS)
Even when I try doing it by the HAVE DISK option, I'm greeted by this error. (SEE PICS)
I am in TEST MODE, I've tried DSEO, and booting while presssing the F8 key to dsable SE's. I have tried the ColorOS Setup.exe drivers, yet nothing. Tried ADB, nothing.
I cannot use the Qualcomm drivers, and therefore I cannot use the MSM8974DOWNLOADTOOL.
Is there anyway I can potentially make the laptop recognise my Oneplus One as QHSUSB_BULK rather than UNKNOWN DEVICE??
Is it even possible for the phone to recover? Or is it game over...?
Any aid and response will be immensely appreciated, thanks in advance!
So when trying to roll back to stock ROM I clearly messed something up and am now left with Kindle that does nothing but sit there, when connected to PC it was showing up as QHSUSB_BULK. From that I was able to locate the Qualcomm drivers so it shows up as "Qualcomm HS-USB QDLoader 9008" I have guides for fixing phones' stuck in this mode, but cant seem to find anything for the Kindle. I even have the app "MSM8974.exe" which will write images back to the MOne phone when they get bricked and are stuck in this mode. I am trying to see if I cant get that to write the BIN file to the Kindle, but so far nothing has worked. I have come across a few threads here, but so far nothing has worked (holding power button for a few mins to get past this mode doesn't work), ADB doesn't work, nor fastboot (or atleast I don't know how to get them to work). I know what COM port the phone is on, so I was wondering if anyone had a way to push a stock BIN/ZIP/Update when the device in stuck in this QHSUSB_BULK mode.
Any help would be awesome. thanks for reading.
kgillette said:
So when trying to roll back to stock ROM I clearly messed something up and am now left with Kindle that does nothing but sit there, when connected to PC it was showing up as QHSUSB_BULK. From that I was able to locate the Qualcomm drivers so it shows up as "Qualcomm HS-USB QDLoader 9008" I have guides for fixing phones' stuck in this mode, but cant seem to find anything for the Kindle. I even have the app "MSM8974.exe" which will write images back to the MOne phone when they get bricked and are stuck in this mode. I am trying to see if I cant get that to write the BIN file to the Kindle, but so far nothing has worked. I have come across a few threads here, but so far nothing has worked (holding power button for a few mins to get past this mode doesn't work), ADB doesn't work, nor fastboot (or atleast I don't know how to get them to work). I know what COM port the phone is on, so I was wondering if anyone had a way to push a stock BIN/ZIP/Update when the device in stuck in this QHSUSB_BULK mode.
Any help would be awesome. thanks for reading.
Click to expand...
Click to collapse
Unfortunately, there is no known recovery from this condition. You can google around for answers but none work reliably. As you are discovering Amazon devices are not like others: easy to brick and nearly impossible to recover. Sorry for your loss.
Didnt think Thor would be so easy to kill
Davey126 said:
Unfortunately, there is no known recovery from this condition. You can google around for answers but none work reliably. As you are discovering Amazon devices are not like others: easy to brick and nearly impossible to recover. Sorry for your loss.
Click to expand...
Click to collapse
That's what I was afraid of.. dang it all. Oh well. I bought the misses a new one just in case this one was messed up. I'm going to get a straight android tablet for me, that way I'm starting off with a less locked device.
Thanks though. I will still check from time to time to see if anyone finds a fix for this.
Found drivers and such for the bulkmode here:
Download dseo13b.zip unzip it and keep it on desktop. (for getting windows into testing mode to install the unsigned drivers, I have 10 and had to reboot windows and modify its boot sequence to disable driver signage)
----https://mega.co.nz/#!8JUkCBIK!X92cRxyY14saa4voLRinGwJUXQYZR37UUpvTMLzwOxM------
Download Qualcomm 2012 drivers unzip it and keep it on desktop.
-----https://mega.co.nz/#!VFsliZ7T!YfE7cx5bnHIvJbmkdHfNxp2Cgp1XrP9pNhquXPDVsxc----
google how to install "QUALCOMM 2012 drivers" and