Hi guys, I just got an used Kyros 7022 from eBay and while trying to install a custom firmware I unplugged the USB cable during the process by accident and now my tablet has a black screen, nothing shows up, when I plug it to the computer Windows will detect it as "Telechips TCC88xx VTC USB Driver" but I'm not able to flash it using the FWDN software because it throws an error message:
[ERROR] CFwdnDownload::Open_BOOT:No Boot File error!
[ERROR] CFwdnDownload:Load_UBS: Open BOOT Error!
I tried to restore to the stock rom but ADB.exe and FASTBOOT.exe will NOT detect the tablet even though Windows detects it and it is displayed under the device manager.
I would appreciate any help,
Thanks
I've done the same thing
I've managed to do the same thing on my Kogan Agora 8' (TC8803)
Have you had any luck fixing it?
My screen is black, cant get into fastboot/adb and FWDN fails aswell (FWDN tool V7 Open_BOOT: No Boot File error! Load_UBS: Open BOOT error! or if rom specified I get ERR_FWDN_UBS_ROM_LOAD_CRC_ERROR), even when shorting pins 7 & 8 (which did work previously until I put the wrong lk.rom on)
I have also looked through the Kogan Agora and TC8803 threads but no luck
Any suggestions welcome!
Related
Please HELP!
Yesterday I flashed my Odys Xelio (Allwinner A10) with CWM. After booting in a working state, I restarted in Recovery too full whipe and whipe dalvik, I installed gapps ans the compatibility.zip also from CWM.
After that I got stuck in a whitescreen. I can not access anything, not even CWM recovery anymore. In win 8 I only could see 1 to 2 undefined devices (should be a problem with the device AND a driver issue).
In Linux I could see a device in adb yesterday and could put it into "adb reboot recovery". Still whitescreen on the tablet, but I could push a recovery file with adb to the /sdcard/. Rebooting didn't bring me to another state.
Today I am not able to connect via adb. It always tells me "List of devices attached" and an empty list.
Display should be okay, no cable issue or sth. else. I really hope someone can help. Perhaps theres a way to JTAG the devices or there is a trick with pressing some buttons and using the USB cable...
BTW: While booting into CarbonRom the first time, the button-behaviour was strange or even totally not working. Perhaps that's a point?
THX in advance
EDIT: Now, after playing around with a needle into a "reset-hole" I finally found a way to see the device in adb. How do I go on!?
I was upgrading the current Stock rom on my ZTE Nubia Z5s Mini, I went through the recovery mode to load the new rom and got a message saying that the rom installed correctly, I rebooted the device and now its stuck at the MIUI logo or if I try to load the recovery mode I get the Nubia logo just to load back to the miui logo again. I got the rom from the MIUI site its v5.
I've left the phone for over an hour hoping it was just loading up but no change, the phone heats up and even has a charger screen when plugged in.
Anyway to get back into the recovery mode to load the original rom again or any other way of fixing this? help :crying:
I've no idea how to help you with this but I'm bumping the thread because I know how you feel.
Sent from my HUAWEI Y536A1
I'm trying to flush the rom by using adb but with an issue, even thou my device is recognized as Nubia Z5s Mini in device manager it still gives a driver error "these have been installed" and in cmd adb it does not see the device.
Update : Got drivers for install from Clockwordmod website but it will only accept the drivers if I set the phone as a modem in device manager when installing them, still not recognized by adb using CMD.
Solved driver issue and qusb_download issue, ADB drivers are done through all drives in device manager pointing to the Google USB drivers and select adb interface then run CMD from within the Google SDK program folder in platform-tools to read the device.
Now using emmc but need to generate EMMCBLD.HEX & 7x30_msimage.mbn if anyone can help, I can enter adb using recovery mode but blocked from making changes in fastboot mode, currently in download mode which can see a drive H but need the two files to proceed any further.
Hi!
First off let me say thanks to R_a_z_v_a_n for redirecting me and hope that I'll find my answer here ^^
So I Have this device called HP 7 VoiceTab 1321RA (not with Slate just HP 7 Voicetab), wanting to have a custom recovery then I tried to flash a CWM Custom Recovery for HP Slate 7 VoiceTab because I thought it was the same and ends up bricking my phone. It ends up in a bootloop which only shows HP sign for a few seconds and dead. But I managed to find out that I can access the recovery menu (or so I thought it is), but the options was choosing between Fastboot Mode, Normal Boot, Recovery Mode, and VART Mode.
I tried to enter Fastboot Mode before and tried to access it via PC but somehow I can't find the device by entering adb devices and fastboot devices. Anyways, I have downloaded a stock update.zip for it but not the original KitKat one which I get from the first time I bought it but rather the JB ones. I think by flashing this would help me recover the device but the only problem is I don't know which method should I use to Flash it. Since I don't have the Stock Recovery or ANY kind of recovery at all, I guess I'm stuck. And it won't start to the home page so I can't set the USB debugging options. Please guide me through this >.<
Thanks a lot!
Been fighting with it for 2 days now and still no result came.
So here's the update so far....
I tried on my other device in order to understand how my PC reads ADB and now I kinda gets it. But the problem is now can't get the device to enable USB Debugging because I can't access options at all.
Secondly, since I left it on for the night because charging seems to trigger the bootloop too, now I can't access the fastboot mode like I was last night. And it constantly repeating this sequence: [battery scene with the "charging battery" symbol] > [HP Powered by Android screen] repeated for 2-3 times > [low battery need charging screen] > repeat. And once I tried to connect to the PC, it goes to the same sequence too. When I tried to access the boot options (the screen which displays Fastboot Mode, Normal Boot, Recovery Mode, and UART Mode which I mention in Thread Starting post), it shows the low battery need charging scene and then repeating the same sequence as mentioned above.
I seem to figure out how to fix this but I still can't manage to access the fastboot mode yet. Will give update once I can try to.
Anyone can help me on this?
Thanks a lot!
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
I found my self in a deadlock!
PLEASE HELP :crying:
Could you unbrick yours
What service centre says about that problem i also ran in this problrm but i m trying to go to service centre for that
first off install drivers in your PC as admin
then use the official flashtool to flash ur stock firmware by entering fastboot or flashmode simple as that
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
Dude urs is a mtk device so sp flash tool should do the trick.... Just don't forget to install correct drivers....run both drivers and flash tool as admin..... Tell me when it's solved k
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
That is what im trying. To tell you urs is a mediatek device the official flashtool is sp flashtool
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
try to push the update.zip via adb sideload (Choose "update via ADB sideload" on recovery mode)using adb terminal on PC,as long as your tab can access the recovery mode.remember to backup all your data before u do it.
have a try it's 100% work on me
where I can download update.zip file? anyone can help?
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
can you explain how did you managed to charge the device??? please its a request......jst help me out :crying::crying:
Initially I tried to root the P9000 following this guide (http://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042), and it seems to have bricked my phone. I got this error, (BROM ERROR-1073676724), and now my phone won't boot, or boot into recovery mode. The PC only sees it if I plug it in and press the recovery buttons (Vol+ and power), and then it'll flash up for a short time before vanishing. I've found the only way to keep it visible in the device manager is to use the flashtool to attempt to flash something to it, but I get this error (BROM ERROR -1073414139). I've tried this on a Windows 10 and a Windows 7 PC with no dice on either. Any help would be much appreciated.
holygoatofsteel said:
Initially I tried to root the P9000 following this guide (http://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042), and it seems to have bricked my phone. I got this error, (BROM ERROR-1073676724), and now my phone won't boot, or boot into recovery mode. The PC only sees it if I plug it in and press the recovery buttons (Vol+ and power), and then it'll flash up for a short time before vanishing. I've found the only way to keep it visible in the device manager is to use the flashtool to attempt to flash something to it, but I get this error (BROM ERROR -1073414139). I've tried this on a Windows 10 and a Windows 7 PC with no dice on either. Any help would be much appreciated.
Click to expand...
Click to collapse
Fixed it, but I'll leave this up for anyone thinking they might have the same problem. I fixed this by flashing the stock ROM again, but with one key difference. Ensure you install all appropriate drivers, and then when you hit download, plug the phone in and attempt to put it into recovery mode. This will open the port just long enough for the flash tool to keep it open, and it will flash as usual.
Hi,
I'm a noob, have tried looking online and in these forums for answers, but am getting lost and am finding myself in over my head. So please be patient with me.
I have an Onda v891w CH V1 tablet with a quad core Z8300 that runs an English Windows 10 and Android 5.1. In a bold attempt to root my Android install, I ended up bricking my device. It now gets stuck on the animated logo screen when booting and never boots either of the 2 operating systems.
I've been browsing online and found a few guides for Onda tablets, but most deal with different models or different versions of the v891w (like the V5, or the Z3735 processor). I believe I've managed to find an Android rom or firmware for my device here, but I'm unable to install it. I'm very likely doing something wrong, I just can't figure out what.
First of all, the thread talks about pressing ESC or F7. I've tried hooking the tablet up to a powered usb hub, along with a usb keyboard and the content of the V891W CH中性固件（适用于V1版本32GB）-20160701.zip file on a usb key. Unfortunately I'm not able to get into the BIOS. I suspect that the usb hub doesn't supply enough power for all the devices. It's an EasyAcc D70 7 port hub with a 5V input.
I noticed in the replies in the thread I mentioned above that people were flashing img files from fastboot, so I've tried booting my tablet in bootloader mode, unlocked the bootloader using the command flashboot oem unlock and tried flashing the boot.img and/or system.img files from the archive using the commands fastboot flash boot boot.img and fastboot flash system system.img. That results in the error FAILED (remote: Flash failure: Not Found). On the tablet it says Failed to get partition boot: Not Found
I'm not sure what to try at this point. If there's anyone who wants to take pity on a newbie and walk me through some step by step instructions on what to try, I would be very grateful.
Update: I've now also tried an Anker 60W 3 PowerIQ Hub to connect the keyboard with the tablet and the usb key, without success. Both the Anker and the EasyAcc USB hub are powered hubs. I could really use some advice on how to get this Onda tablet back operational.