I am helping out a friend regarding his tablet Wave 8 HD+ (33GT HD).*
The tablet doesn't have any physical volume button.*
The problem is that he tried to update to the latest firmware but got stuck in recovery with error status 7. There is no way to scroll down to choose option (factory reset, enter ADB, etc.) since there is no physical volume button.
I was able to download the firmware from bluewave and it contains a flashing tool called Rockchip Batch Tool and *Rock chip driver.*
Problem is: laptop doesn't recognize the tablet as the GT, it will show as Android Device > Android ADB Interface in Device Manager.
Anyone has any idea what to do? Thanks
johncodog said:
I am helping out a friend regarding his tablet Wave 8 HD+ (33GT HD).*
The tablet doesn't have any physical volume button.*
The problem is that he tried to update to the latest firmware but got stuck in recovery with error status 7. There is no way to scroll down to choose option (factory reset, enter ADB, etc.) since there is no physical volume button.
I was able to download the firmware from bluewave and it contains a flashing tool called Rockchip Batch Tool and *Rock chip driver.*
Problem is: laptop doesn't recognize the tablet as the GT, it will show as Android Device > Android ADB Interface in Device Manager.
Anyone has any idea what to do? Thanks
Click to expand...
Click to collapse
Hello,
Please try posting your query here Ask any Query Newbie Friendly with all relevant details, the experts there maybe able to assist you.
-Vatsal
Related
Hi everyone and all the gurus here!
Help is much needed, the sad story is below.
1. Lauched LagFix (a trim utility) on my Fujitsu Stylistic M532
2. Some time passed, the device switched off by itself
3. Tried to boot with no luck, then to rest or enter in recovery mode - no effect, no any Android logos appeared. Just black screen, but a vibration when using power button and a lid lights when charging.
4. Win7 sees the tablet as Android device, but no discs are accessible (the Android device appears and dissappears subsequently in Win when pushing power button on/ off).
5. Tried several utilities (both Win and Dos) to restore the firmware, but all of them said there's "No device connected". Though Win sees the tablet in devices list anaway.
The LagFix developer stated that there's a so-called "Brick Bug" occurs to some devices because of the faulty memory controller when using his utility.
Couldn't someone please advice what to do or try to reanimate the tablet?
Million thanks in advance!
Hi,
As there's no section for your device on XDA, and I can't find a relevant thread for you.... This would be where to ask for help...
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck!
Thank you. Thread closed.
BRICKED 7inch Irola Tablet...PLEASE HELP
I am in DIRE need of some help with my tablet. I received this irola dx752 tablet bricked and cannot fix it for the life of me. I am able to hold power and volume up and get into recovery system version 4.2.01. I Have tried a factory reset and a wipe system cache and the tablet just reboots to the green robot with and exclamation mark. If I press volume up, it brings me back to the system recovery. Now i am not very versed in ADB but I tried to sideload just about every firmware I could find for an a13 allwinner a8 cortex 7inch tablet, since the irola website has taken down its firmware. Also, fastboot will not work on this tablet whatsoever (it just says waiting for device) when i enter any command. I have never seen this tablet boot into a rom of any kind and therefore cannot tell if USB Debugging was ever enabled. I also Have tried different drivers but the one that seem to hold is the Android ADB Interface. CAN ANYONE PLEASE GIVE ME SOME SUGGESTIONS OR SOME HELP? It would be greatly appreciated. Thank you.
Hi,
I can't find anything relevant on XDA for your device and issue, so you will need to ask for help here,
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck!
hello
so last time i wanted to install that "touch fix" for my Chuwi vi8, after a reboot my tablet wasn't able to boot anymore, it just won't stop top reboot, i can still boot to Windows with lock+up volume + home button, i can also go in the stock recovery mode, yes i already tried factory reset and it didn't worked, how can i fix it ? i already searched on google but i need to get clockworkmode... BUT HOW ??? i can't boot in android !!!...
JeanEudesExpire said:
hello
so last time i wanted to install that "touch fix" for my Chuwi vi8, after a reboot my tablet wasn't able to boot anymore, it just won't stop top reboot, i can still boot to Windows with lock+up volume + home button, i can also go in the stock recovery mode, yes i already tried factory reset and it didn't worked, how can i fix it ? i already searched on google but i need to get clockworkmode... BUT HOW ??? i can't boot in android !!!...
Click to expand...
Click to collapse
Hello
I'm sorry but I can't find anything related to your question/device.
> Android Development and Hacking > Android Q&A, Help & Troubleshooting or General Q & A thread
-Vatsal
so my tablet is dead ? ...
JeanEudesExpire said:
so my tablet is dead ? ...
Click to expand...
Click to collapse
You may ask for assistance in above thread or forum.
I rooted my tablet zenpad 8 z380kl by kingroot it's working fine but when I restarted the tab all applications get force stopped so I hard reset my tab then also same problem so I install the Rom again by using twrp recovery after completing installations my tab totally dead no response when I pressed the power button when connected to computer it shows unauthorized device adb also not detecting my tab it's totally hard bricked I need your help.
tamil28 said:
I rooted my tablet zenpad 8 z380kl by kingroot it's working fine but when I restarted the tab all applications get force stopped so I hard reset my tab then also same problem so I install the Rom again by using twrp recovery after completing installations my tab totally dead no response when I pressed the power button when connected to computer it shows unauthorized device adb also not detecting my tab it's totally hard bricked I need your help.
Click to expand...
Click to collapse
Hello,
Try posting your query here Ask any Query Newbie Friendly with all relevant details, the experts there maybe able to assist you.
-Vatsal
Hi everyone,
I own a Motorola Moto G2 (XT1068, dual sim) that came used with Android 6.0 on it.
I installed TWRP (twrp-3.0.2-3-titan.img) on it but failed to root Android 6.0 as well as 5.0 for whatever not yet understood reason. I don't do Android development for a living but I'm an IT professional, so handling adb and fastboot as well as reading and understanding instructions isn't a problem.
I flashed stock Android 4.4.4 (RETDEALL_XT1068_4.4.4_KXB21.85-14) which I successfully rooted by installing SuperSU via TWRP.
Next I updated SuperSU, verified that root access is indeed working and installed FlashFire, which I hoped to use to install OS upgrades, possibly without losing root. FlashFire is new to me (as of yesterday), everything else mentioned up to here is not.
I used the "Flash ZIP or OTA" action from within FlashFire and the previously downloaded update file in the /cache directory. I can't reproduce the file name since the phone is currently unusable and I didn't write the file name down prior to using FlashFire.
The state of the phone after this unsuccessful attempt was that of a broken USB device, i.e. unable to even register as whatever type of USB device. I learned that this can be fixed by holding the power button down for more than one minute, after which I managed to
get the phone to be shown as working "RELINK HS-USB QDLoader 9008" USB serial device in Windows 7 device manager.
I used the information in these two threads:
http://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Since I started with Android 4.4.4 trying to upgrade to 5.0, I had hoped that the blank flash package for one of these Android versions would help fix my problem, but as of now, this doesn't seem to be the case. At the end of the blank flashing process, I get the message
FAILED <blank-flash:sdl-transfer-image:sdl-hello: error sending packet>
After that, the phone still has a black screen and cannot boot into anything. Repeating blank flash works after resetting whatever part of it is still working by holding the power button down for about 30+ seconds.
Is there anything obvious (or maybe even not so obvious) that I missed?
Thanks for reading and any help and/or pointers in the right direction.
Hello and thank you for using XDA Assist,
please create an account and post your question in our Android Q&A section:
G 2014 Q&A, HELP & TROUBLESHOOTING
The experts there should be able to help you.
Kind regards & good luck
Trafalgar Square
XDA Assist