I have a BLU Quattro 4.5 android device and when I try to connect via USB Debug mode and run ADB Device it will not find my phone. I have searched high and low in order to locate the driver with no luck. The generic USB driver from google won't even work. I have even run emulator from the phone and when I type: pm set-install-location 2, it comes back with Killed and then back to command prompt. When I type: pm get-install-location it comes back as 0[auto]. My phones main memory is 1 gb and 1.5 internal usb memory. With all of the main system apps updated on the main drive, the phone cannot handle ANY other apps, even when I put apps on the usb memory it is very sluggish. I need help in trying to install and run all of the apps from the external sd card and just have the system apps running on the main disk. I would also like any help in finding the driver needed to access the phone in ADB.
BLU Quattro 4.5"
4 GB Internal Memory( Broken up to 1 GB Main, 1.5 GB USB Storage, and not sure where the other .5 GB went.)
1 GB Ram
NVIDIA Tegra 1.5 GHZ Quad Core
16 GB Class 10 Micro SD Card
Android 4.0.4 ICS
Unlocked Running Straight Talk/T-Mobile Sim
GOT IT!!!!!!!!!!!!!!!!!!
plymouthrock99 said:
I have a BLU Quattro 4.5 android device and when I try to connect via USB Debug mode and run ADB Device it will not find my phone. I have searched high and low in order to locate the driver with no luck. The generic USB driver from google won't even work. I have even run emulator from the phone and when I type: pm set-install-location 2, it comes back with Killed and then back to command prompt. When I type: pm get-install-location it comes back as 0[auto]. My phones main memory is 1 gb and 1.5 internal usb memory. With all of the main system apps updated on the main drive, the phone cannot handle ANY other apps, even when I put apps on the usb memory it is very sluggish. I need help in trying to install and run all of the apps from the external sd card and just have the system apps running on the main disk. I would also like any help in finding the driver needed to access the phone in ADB.
BLU Quattro 4.5"
4 GB Internal Memory( Broken up to 1 GB Main, 1.5 GB USB Storage, and not sure where the other .5 GB went.)
1 GB Ram
NVIDIA Tegra 1.5 GHZ Quad Core
16 GB Class 10 Micro SD Card
Android 4.0.4 ICS
Unlocked Running Straight Talk/T-Mobile Sim
Click to expand...
Click to collapse
found generic driver from PDANET that finally allowed me to access my phone from ADB and I was able to make the necessary changes. Yippeee! pdanet.co
plymouthrock99 said:
found generic driver from PDANET that finally allowed me to access my phone from ADB and I was able to make the necessary changes. Yippeee!
Click to expand...
Click to collapse
Good news! I just bought the same phone, and I'm waiting on delivery as we speak. From the reviews I've read so far this phone delivers the most bang for the buck. I just hope that we'll be able too root it soon. How do you like it so far?
londonflu said:
Good news! I just bought the same phone, and I'm waiting on delivery as we speak. From the reviews I've read so far this phone delivers the most bang for the buck. I just hope that we'll be able too root it soon. How do you like it so far?
Click to expand...
Click to collapse
I have one as well and was able to root it with the latest bin4ry tool! Hopefully Blu will enhance their customer support as they gain more popularity and release some source code or dev tools for the phone. Or at least, since it's rooted, the device can eventually gain support from any devs.
Kah,
Can you post root instructions for us, please?
Sorry, I would've posted before but I wasn't sure if that would move the thread off track. It was very easy actually:
Make sure adb recognizes the device (mine said 123ABCDEF... or something like that for some reason. It doesn't matter apparently).
- Also I'm using windows 7 and after allowing the few default drivers to install, it worked instantly. ( I believe. I do remember messing around with some other software, but I think that was in hopes of finding a root tool. If you have any issues, I can post the names of other software I tried. The OP's method could possibly work too)
I downloaded Root_with_Restore_by_Bin4ry_v23.
- there's a new version out now, but I would expect it to work as well
I choose the normal mode and followed the directions.
- If I remember correctly, it gives you the option to install superuser or super su. I chose superuser, and it worked. But after using it for a bit, it gave me lots of issues with root privileges, so I installed super su from the market and I haven't had an issue since.
Any Information posted in this thread is Great!
I don't mind taking this off track of what the original thread. I like it that it is progressing the way it is, helps me out with other questions and anyone else that starts off with my problem probably wants additional information on what else could be done with these phones.
kah1593 said:
Sorry, I would've posted before but I wasn't sure if that would move the thread off track. It was very easy actually:
Make sure adb recognizes the device (mine said 123ABCDEF... or something like that for some reason. It doesn't matter apparently).
- Also I'm using windows 7 and after allowing the few default drivers to install, it worked instantly. ( I believe. I do remember messing around with some other software, but I think that was in hopes of finding a root tool. If you have any issues, I can post the names of other software I tried. The OP's method could possibly work too)
I downloaded Root_with_Restore_by_Bin4ry_v23.
- there's a new version out now, but I would expect it to work as well
I choose the normal mode and followed the directions.
- If I remember correctly, it gives you the option to install superuser or super su. I chose superuser, and it worked. But after using it for a bit, it gave me lots of issues with root privileges, so I installed super su from the market and I haven't had an issue since.
Click to expand...
Click to collapse
Average
I am still having issues with ram and touchscreen when main storage location gets full. It becomes very unresponsive and the touchscreen becomes very sluggish. Some things I cannot move to the external sd card and all the installed apps still get installed on primary drive even after changing default install location. I need to figure out how to install and run everything, including the android os.
londonflu said:
Good news! I just bought the same phone, and I'm waiting on delivery as we speak. From the reviews I've read so far this phone delivers the most bang for the buck. I just hope that we'll be able too root it soon. How do you like it so far?
Click to expand...
Click to collapse
plymouthrock99 said:
I am still having issues with ram and touchscreen when main storage location gets full. It becomes very unresponsive and the touchscreen becomes very sluggish. Some things I cannot move to the external sd card and all the installed apps still get installed on primary drive even after changing default install location. I need to figure out how to install and run everything, including the android os.
Click to expand...
Click to collapse
Try using Mounts2SD..
I doubt I'll get much help on this, but I'll give it a shot. I just got my Quattro 4.5 today, and tried to root it with Bin4ry. It never did the first reboot, it just turned the phone off. After a few minutes I turned it back on still connected to USB, Bin4ry tried to finish, but gave a permission denied error on the superuser apk. Now my phone is in continuous boot loop, it gets to the lock screen, but says Go Laucher and system UI has stopped, then reboots. Is this thing bricked? Holding volume down and power just goes to a modem download screen, but no USB connection or anything. :crying:
j21blackjack said:
I doubt I'll get much help on this, but I'll give it a shot. I just got my Quattro 4.5 today, and tried to root it with Bin4ry. It never did the first reboot, it just turned the phone off. After a few minutes I turned it back on still connected to USB, Bin4ry tried to finish, but gave a permission denied error on the superuser apk. Now my phone is in continuous boot loop, it gets to the lock screen, but says Go Laucher and system UI has stopped, then reboots. Is this thing bricked? Holding volume down and power just goes to a modem download screen, but no USB connection or anything. :crying:
Click to expand...
Click to collapse
I'm sorry to hear than man. Which version of Bin4ry did you use? You could try quickly using adb to boot into recovery mode while the phone is still in the process of booting. You'd have to keep sending
Code:
adb reboot recovery
until adb recognizes the device. Hopefully, it'll restart into recovery before it crashes. Not sure if it'll work, but it's an idea.
kah1593 said:
I'm sorry to hear than man. Which version of Bin4ry did you use? You could try quickly using adb to boot into recovery mode while the phone is still in the process of booting. You'd have to keep sending
Code:
adb reboot recovery
until adb recognizes the device. Hopefully, it'll restart into recovery before it crashes. Not sure if it'll work, but it's an idea.
Click to expand...
Click to collapse
Everything is fixed! I figured out how to get into recovery. I was able to do a factory reset from there and everything came back, actually maybe better. Then I found an old version of Bin4ry, v15, and tried again. This time it worked perfectly. This phone is pretty awesome, I just wish there was developer support for it.
j21blackjack said:
Everything is fixed! I figured out how to get into recovery. I was able to do a factory reset from there and everything came back, actually maybe better. Then I found an old version of Bin4ry, v15, and tried again. This time it worked perfectly. This phone is pretty awesome, I just wish there was developer support for it.
Click to expand...
Click to collapse
Great! How'd you manage to get into recovery mode despite the boot loop? In case anyone else runs into the same issue.
kah1593 said:
Great! How'd you manage to get into recovery mode despite the boot loop? In case anyone else runs into the same issue.
Click to expand...
Click to collapse
Hold volume up and power until it turns on. As soon as the screen changes to green, I let go of the power button and keep holding the volume up button until it's in recovery mode. It seems the power button release has to be timed right or else it just sits on the green screen, or powers off again. It takes a couple of tries for me. I probably did 10 factory resets last night before finally getting it rooted, lol. The built in recovery has an option to flash from external storage, kind of makes me wonder how easy this phone would be to get CWM working. Of course, the real problem is getting developers to write the custom ROMs for it. The only thing this $230 phone is missing from its $600 cousins is 4G LTE, but on Tmobile it doesn't even matter right now. It's still blazing fast even on stock with no overclock, I can't imagine how much more awesome it would be with a custom rom.
kah1593 said:
Sorry, I would've posted before but I wasn't sure if that would move the thread off track. It was very easy actually:
Make sure adb recognizes the device (mine said 123ABCDEF... or something like that for some reason. It doesn't matter apparently).
- Also I'm using windows 7 and after allowing the few default drivers to install, it worked instantly. ( I believe. I do remember messing around with some other software, but I think that was in hopes of finding a root tool. If you have any issues, I can post the names of other software I tried. The OP's method could possibly work too)
I downloaded Root_with_Restore_by_Bin4ry_v23.
- there's a new version out now, but I would expect it to work as well
I choose the normal mode and followed the directions.
- If I remember correctly, it gives you the option to install superuser or super su. I chose superuser, and it worked. But after using it for a bit, it gave me lots of issues with root privileges, so I installed super su from the market and I haven't had an issue since.
Click to expand...
Click to collapse
Can anyone post a link of where I'll find the proper drivers? It just shows BLU with an exclamation in my Device Manager. The PDANET trick did not work as it won't detect the device. - and if I can get this working, I'll post an actual tutorial for it.
If anyone could post an update.zip of the original rom that would be fantastic. - and clockwork 6 will run on our devices with some work. but right now, mine is a brick, it still has recovery but the stock rom is effed.
I'm in the same situation. I deleted my contacts.apk in hopes of replacing it with a stock version, now it's stuck in a boot loop, and factory reset doesn't help.
Alright guys, I hit the jackpot. I have CM 10.1 working on my Quattro 4.5. It all began when I read somewhere on the xda forums that the Quattro 4.5 and k-touch v9 are essential the same phone. I said before, my phone was bricked so I figured I do some more research and see what I could do. Turns out that person as right. I found a website ( http://www.needrom.com/phone-roms/k-touch/k-touch-v9/ ) that has 3 roms for the v9, CM 10.1, MIUI 3.4.5, and CM 10, and instructions to install them. I decided to take a leap of faith and follow the directions given for CM 10.1. The installation directions for custom recovery CWM 6.0.1.1 worked perfectly - only problem is after you've installed the recovery, the menus are in Chinese.
Once again, My phone was bricked and essentially completely erased. If your phone isn't bricked, it should be fine as long as you do a factory reset before. I would suggest doing this before installing the CWM recovery because I have no clue how to do the reset using the Chinese menu.
I downloaded the CM 10.1 rom from the website above and gapps for 4.2.2 as well (you can find this with google). If you're using one of the other roms, obviously make sure you're using the proper gapps version.
ADB works while in recovery so use this to push the zips to the phone. I say this because I've discovered the sd card directory changes depending if your phone is bricked or not (i.e. /emmc vs /sdcard).
Flash the rom zip, then gapps - select the 2nd option in the main menu then in the following menu, the 4th option. This should lead you to the directory containing your zip files. Choose the appropriate one, and let the CWM work its magic. ( also from messing around I can also tell you the first option in the main menu is to reboot)
Once you've reboot, everything should work perfectly - WIFI, bluetooth, brightness, camera, video recording, audio, microphone, not a single problem except the volume being much louder than before. It's amazing. I have straighttalk's $30 plan, so I'm still stuck with a dumbphone until I bump up to the unlimited everything at the end of the cycle, so I can't test the phone radio, but I would expect it to work considering everything else does as well. Let me know if I left something out. I would test the other roms, but I'm so happy and content with my phone working again, I don't want to go through the effort just yet.
I found a way to create an English recovery that works from the Chinese version. Just replace the recovery.img provided with this one. Here's the link: https://www.dropbox.com/s/5y6r9gvspvouhbo/recovery.img I don't think this should cause any issues because it hasn't for me, but remember you are using this at your own risk. Though if an issue does arise, I'll try my best to help.
Install with English Recovery?
Did you install with the English recovery, because I am stuck at CM10.1 boot screen installing with the English recovery.
I picked up this device from walmart for $29.99 with the intentions of learning some new development stuff.I
thought for 30 bucks there's gonna be a lot of these little "duallies" running around why not a cheap candidate?
So far as i can tell there is little info found about this device so I'm looking to collect what little is known about
it in one place in hopes to get a jump on it. First things first, I am responsible for my own actions as you are yours.
If your not sure ask or simply dont do, some of this stuff can brick your device!
*ROOT*
These are the instructions I followed to root.
http://www.androidarea51.com/all-things-root/working-root-for-lg-optimus-fuel-woot/
dont forget to install supersu
https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
and busybox afterwards!
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
*RECOVERY*
Downloaded "TWRP Manager" from play store.
twrp settings, I enabled the sd card patch.
Install twrp\device name :l34c\version i instaled: openrecovery-twrp-2.8.4.0-l34c.img
click install... wait... things will pop up..... things will go away... wait some more...
finally a dialogue that states sucess.
***ISSUES HAVE BEEN REPORTED OF LOSING RECOVERY OR THE ABILITY TO ENTER IT AFTER
A WIPE AS WELL AS PROBLEMS BACKING UP AND OR RESTORING.
I have "injected" twrp manager into the system using titanium backup (link2sd will work also). This seems to
prevent any issues I have read about previously mentioned. Also I have successfully preformed backups as
well as restores, both before and after wiping. I have not figured out how to enter twrp recovery upon boot
yet, so be careful of what you do!
*SAFE TO REMOVE APPS*
yet to come
I use "titanium backup" from the play store, still trimming.I can get it down to about 230MB
available "free" ram at the moment but not consistently.
Ok had an issue with a task manager improperly reporting free available ram... true availability was
around 150mb free. There are apps that have to be replaced when removed, for example a launcher
for a launcher but some do not. Again I'm still trimming and experimenting, right now my system rom
around 244mb free. Most every thing I have done has been on the phone its self without the need of a P.C.
*STOCK BACK UP*
Yet to come
Any candidates for a true stock rom? Ive hacked the crap out of this one so far without the need of a back up... i know tisk tisk tisk!
I'm going for a debloated deodexed stock rom, hopefully!
*DRIVERS*
The only ones I could find that actually work. The Verizon drivers mentioned for the g2, not surprising since it runs on vz towers!
http://forum.xda-developers.com/showthread.php?t=2432476
*TETHERING*
using the android wifi tether 3.3beta2
https://code.google.com/p/android-wifi-tether/
all settings untouched except
device profile
lg optimus 3d
device access does work as well as encryption
*XPOSED*
Does work, im using 2.6.1.
*DPI*
The app I'm using for safe keeping to test dpi settings
https://play.google.com/store/apps/details?id=com.oumugai.densityadjuster
200 not working
170 works
160 native
150 works
140 works
130 works
120 works (looks good)
110 works
Temporarily went back to native dpi for debloating purposes. Will revisit later.
After messing with DPI settings I'm having a"contacts has stopped working " when tapping on the phone app.
DPI set to 120 when I noticed. All dpi switches affect lg home launcher
so you will need another launcher.
ok so far thats what i got. whats the nexts step to a stock AOSP rom?
questions and/or constructive comments wecome
reserved
I've got a few of these that are bootlooping. They show the LG logo, and then TracPhone Wireless splash screen infinitely in a loop.
Two questions.
1 - Is there any way to recover them? I'm hoping for some sort of a dev tool that I could flash a stock image or something (like Odin is for Samsung phones)
2- When these phones started bootlooping, I installed TWRP on the other Fuels that I have, thinking that I didn't want it to happen to them. My understanding of the TWRP that's installed from TWRP manager doesn't flash a modified boot image, so you can't enter TWRP from a powered off (or in my case, bootlooping) phone. Is that correct? I flashed a custom boot image from elsewhere that allows me to tap vol up at the LG logo to boot to TWRP. Any idea if this is enough of a safeguard to in the even of similar boot loops?
Any chance you know how to get it in diag mode? I need to connect it to DFS but can't without diag. Thanks for your help!
DrPhant0m said:
I've got a few of these that are bootlooping. They show the LG logo, and then TracPhone Wireless splash screen infinitely in a loop.
Two questions.
1 - Is there any way to recover them? I'm hoping for some sort of a dev tool that I could flash a stock image or something (like Odin is for Samsung phones)
2- When these phones started bootlooping, I installed TWRP on the other Fuels that I have, thinking that I didn't want it to happen to them. My understanding of the TWRP that's installed from TWRP manager doesn't flash a modified boot image, so you can't enter TWRP from a powered off (or in my case, bootlooping) phone. Is that correct? I flashed a custom boot image from elsewhere that allows me to tap vol up at the LG logo to boot to TWRP. Any idea if this is enough of a safeguard to in the even of similar boot loops?
Click to expand...
Click to collapse
My apologies for the delayed response. I have a lot going on in life.
As for recovering them, use the device you have closest to stock to make a backup. Do this before you attach your account or put any thing in to it after a "fresh wipe". To the best of my knowledge there isnt a tool like odin available, i could be wrong though. You can push a back up to the looping devices via adb. in order to do this you must have previously enabled usb debugging. The instructions are available on the web, i my self dont know how to do this. If you can establish an adb connection im sure you can command it to boot into twrp. For setup and testing use one of the devices that doesnt have a problem to establish adb. There is a little info on another thread i created about investigating the boot process the link is in my signature for the defy. Please be patient with me as i have two jobs and a single father, im not a hacker or developer. just a normal guy that is fascinated by my little robot willing to learn any thing. now that I know this thread is becoming active Ill monitor a little closer. Also if there is any thing i can help with ill be glad to do so. Im wanting to get a second fuel just for dev and learning purposes.
Recovery
Is there a way to access recovery on the lg fuel? I am stuck in a boot loop because I disabled the home screen service as well as other things that I did not pay attention to. I do not have a custom recovery installed.
I've never been able to boot to recovery by way of button press. Seems like there's a way to get into boot loader mode though. Just can't remember off the top of my head, I'm at work now and don't have the fuel with me. I'll see what I can figure out in a few hours when I get home. In the mean time you can try button combos upon boot to include the home button. If we can get ADB talking to it there's a chance I can send you copies of the files needed. Give me more details of what you have done just before the boot looping.
Sent from my ALCATEL A564C using XDA Free mobile app
I bought the optimus fuel a few months ago and i've been using it primarily for a music player/run keeping devices during my jogs. I turned off mobile data and i've noticed that i still see signal bars on the top notification area - does this mean that the radios are still on?
I was wondering if there was some way to completely disable the cellular radios so that i could conserve battery life inbetween days where I don't run?
Thanks!
This is a pretty cool app....
https://play.google.com/store/apps/details?id=com.latedroid.juicedefender
Airplane mode and then turn WiFi back on does the trick. "Radios off" = ton more juice
Has anyone found out anything else for this little phone? I have the LG Optimus Fuel. Had it for a few months now. I rooted it as soon as I got it and uninstalled a few system apps like the LG keyboard, the default SMS app and Chrome along with 2 or 3 other Google apps. It's still running fine.
I installed TWRP recovery and a custom boot image so I could boot into recovery by pressing the up volume button. Works great. I made a full system backup and saved it to my external SD card and saved it to my Debian laptop.
Right now I'm just looking for a custom ROM for this little phone but can't find one. I'd love to get Cyanogenmod on this phone but there are none. I'd port it myself but I'm not able to at the moment.
reemobeens19 said:
...
*ROOT*
These are the instructions I followed to root.
http://www.androidarea51.com/all-things-root/working-root-for-lg-optimus-fuel-woot/
...
Click to expand...
Click to collapse
I'll expand on the above link because no one can view all of the info in that thread w/o registering for that site [PITA].
Load towelroot (www.towelroot.com). Upon running towelroot, press "welcome to towelroot v3" 3-times (quickly). Change 1337 0 1 0 4 0 to 1337 0 0 0 4 0 (change only the ONE to a ZERO), click "make it ra1n" and you're rooted. :good:
This was verified on an L34C running Android 4.4, Kernel 3.4.0+, build KRT16S.L34CV10c, Sw ver L34CV10c.
YMMV; IANAL
My apologies for the inconvenience, I was unaware for the need to register.
What I would like to do with the L34C is find a ROM with all the phone functionality removed, and few to no Google Apps (let me just add the ones I need). I am not planning on using it as a phone (I still have my old Casio flip-phone, need nothing else). My intention was to experiment with creating a PalmPDA "replacement", something small to carry around for addresses, notes/memos, calendar (you know, the stuff you used to do on PalmOS), and in addition figure out how to do record-level synchronization **locally** (as in I don't need to send my data to some dirt-floor shack in Bangalore just to have it sent back to a device 2 feet away from my computer). Additionally, would line to use it as a basic portable media player. Essentially, trying to re-create the Palm LifeDrive on Android.
To my knowledge there are no roms available for this device. Your best bet in my opinion is to remove apps 1 by 1 after rooting. Google each and find out what the risk and severity of removing them are. I have donated my device to a less fortunate fellow employee. So as of now I'm unable to help with testing. This method is what I do for all of my devices until I'm finally happy with its performance and functionality. Think of Android as the swiss army knife of the computer world, you can do just about any thing with it, you just gotta figure out what tools are useful to you and the ones you can do with out, then you gotta ask Google witch ones Android can function with out. I hope you find what your looking for in the little robot, its a really neat world inside there!
I hate to bump an old thread but, I also don't it necessary to start a new one, at least not yet anyway but, I too am looking for a way to flash stock ROM. I have LG34Cs to use as a reference..
Where is the link to exposed framework at for this phone?
All official twrp 3 images are broken on official site. Last good working was 2.8.7.0.
Here is working twrp 3.1.1 if anyone interested:
Code:
mega.nz/#!I0lhAYAY!fRbQtQjYFI2kiJOD0FSEBPnBJm0JZxpiBaw52kyOfQE
majexuj said:
All official twrp 3 images are broken on official site. Last good working was 2.8.7.0.]
Click to expand...
Click to collapse
What does broken mean in detail? Do I risk to brick my L34C when I flash official twrp 3 images?
Mac23 said:
What does broken mean in detail? Do I risk to brick my L34C when I flash official twrp 3 images?
Click to expand...
Click to collapse
Broken as in doesn't boot into recovery. The phone will still boot into android, assuming you have a working system, and within android with root you can flash a working recovery image over a broken flash with the dd command on the twrp device info page (twrp.me/lg/lgoptimusfuel.html). So no real risk of brick, just possible inconvenience that might require a battery pull.
I built twrp 3.2.1 with same sources but I have not tested it since my battery seems to have completely died and the phone won't boot with usb power alone.
Here is link anyway in case anyone is interested:
Code:
mega.nz/#!ssExSY7S!_B3FcAmclzRwCKTX461Tl_QhpdwwK0tmvhL-6zkKLRw
---
So, for Christmas my daughter's mom got her an A33 Q88H QuadCore Softwinner tablet, and we discovered the OS it came with had some very strange issues related to a lack of compatibility with Google Play, so I tried to get around that with software, but I needed to be rooted. However, I had bizarre difficulties with SuperSU, unlocking the bootloader, rooting, and even more difficulties trying to flash a custom recovery that I could use to ROOT-- the obscure china tablet had no TWRP or CWM support. I finally tried a very convoluted method of flashing what appeared to be a ROM for the A33 Allwinner tablet, which hadTWRP already installed, so I could use TWRP to root it, and then finally fix the software issues.
However, the process didn't work, and when I rebooted the phone, I found it stuck on a black screen with a tiny android symbol, and that's how it's been since. Holding volume and power button only reboots it to the same screen -- no bootloader or anything, so I can't find any way to try to flash a factory ROM to get it back to regular settings. When I plug it into my computer, it makes the input noise, and shows up in Device Manager as "Android Device" with "Android ADB Interface" drivers successfully installed, but ADB doesn't recognize it as a device, and I can't get it into any sort of download mode -- it isn't recognized in My Computer as a hard drive. So, I can't find a way to interface with the tablet to reflash a stock ROM. :frown:
It's her Christmas present, so I don't want to admit that I've broken it; I've been trying to solve it all night for 12 hours straight, but I just can't find anything that works! Is there any way you guys can help me? :crying:
I tried to attach some pics but the uploader isnt working.
bump