Hi folks, need some help with my MXQ Pro 4k android box. It is completely bricked and nothing that I've tried has helped. The box is recognized by the USB burn tool but stops at 7% every time trying to format. Using the SD card method shows the Android update bar but it just hangs. It seems locked into a bootloop which is perhaps corrupt.*
I've hooked up uart ttl and have made successful connection. Via uart, I can get to the gxl_p212_v1# prompt and can send commands via putty.
As a last resort, I'm trying to wipe the nand and for some reason the 'nand erase whole' command is not recognized. It comes up with Unknown command 'nand' - try help.
It recognizes mmcinfo, fatload... but no nand commands.
Does anyone know why it's not recognized, is it a putty version issue or something else? *Any help in getting the nand erased via putty or some other serial method would be greatly appreciated.
Related
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!
Hello,
a few weeks ago i flashed cwm and cyanogenmod 10.2 nightly to my L9. I wanted to use Link2SD to move some apps from internal memory, so i had to repartition the sd-card. Unfortunaly the phone would not let me remove the sd-card (seems like it is stuck because the eject-mechanism is not working). So i tried to repartition the memory with Aparted from within the phone and of course i accidentally removed the phones internal partition, instead of the sd-card partition. Now the phone won't respond to almost anything i have tried. That includes:
- turning the phone on
- booting to recovery
- s/w upgrade mode
With Lelus tool i am able to get a fastboot connection, it even looks like i am able to flash another recovery image (i have the omap drivers still installed from flashing the phone the first time). But in the end the phone itself does not respond to anything. When trying to install ics x and u boot with Lelus script it fails after complaining about a missing partition.
Do you know another way to restore internal partition(s)? Is there any hope to get the phone working again?
Thank you in advance
if all fails try this you may get lucky
http://forum.xda-developers.com/showthread.php?t=2546571
tawhid111 said:
if all fails try this you may get lucky
http://forum.xda-developers.com/showthread.php?t=2546571
Click to expand...
Click to collapse
Thanks a lot! Looks like LG Support Tool recognizes my phone now (there is no visual feedback on the phone screen in S/W Upgrade right?) But when i start to use the tool to recover from a failed upgrade, it always skips around 20-25% progress. For a moment the phone is not shown in my windows device manager and after that, it is recognized as Ti Board - Omap44xx every few seconds and then lost again, like the driver is not properly installed (is that possible after being able to get to fastboot and S/W Upgrade mode?). Any idea?
kidCurly said:
Thanks a lot! Looks like LG Support Tool recognizes my phone now (there is no visual feedback on the phone screen in S/W Upgrade right?) But when i start to use the tool to recover from a failed upgrade, it always skips around 20-25% progress. For a moment the phone is not shown in my windows device manager and after that, it is recognized as Ti Board - Omap44xx every few seconds and then lost again, like the driver is not properly installed (is that possible after being able to get to fastboot and S/W Upgrade mode?). Any idea?
Click to expand...
Click to collapse
The s/w mode from the unofficial fastboot is not going to work. I think you really messed up your phone doing that (aparted). You might be able to run a fastboot command to repartition it but I doubt it will work. Try this command select option 1 (just fastboot)
fastboot devices
fastboot oem format
You should have a look at this information as well http://www.omappedia.com/wiki/Android_Fastboot
Sent from my LGMS769 using XDA Premium 4 mobile app
my phone just LOGO,, try update offline error 4%
then i try with fastboot:
fastboot devices
fastboot erase u-boot
fastboot erase boot
fastboot erase recovery
fastboot flash u-boot 2.img
fastboot flash boot 3.img
fastboot flash recovery 4.img
now phone is dead,, i se on device manager omap4430 fastboot usb device only connect then disconect continuesly...
please helpp,,, #cry
This should help you fix it: http://forum.xda-developers.com/showthread.php?t=2119090
It will give you fastboot access again so you can flash the correct files.
I love omap devices, they seem to be difficult to hard brick with the exception of the high security models.
Sent from my Amazon Tate using Tapatalk
Hello friends,
I was using a General Mobile etab4 tablet,
rooted,
bootloader locked,
not backed up, i tried but apps wont recognize the brand,
the stock rom is not available anywhere but I managed to find some custom ones.
This tablet is actually a given by government for educational purposes, and it has no download mode, I can only initiate recovery mode with volume up+power button combo, and there is no sd card in it.
Here is what happened. It was running with problems so I decided to flash a custom rom I find on this forum. First I tried flashing using adb sideload. I got an error message "Installation aborted" with no error codes after verification step but it does not state whether verification is failed or not. I don't know what actually failed. Then I tried to flash it using adb shell as root (the system image was in /sdcard directory). It freezed, I exit the shell using Ctrl+C command. Then whenever I try to start shell i got "error:closed" message. I see my device with adb devices with sideload, but it is not seen in fastboot devices.
When I try to open it, I guess it enters in a small boot loop (screen flickers multiple times with brand name on it) and after some time I got dead android with no command written.
I tried,
reflashing it again with Android AIO Flasher,
use fastboot to unlock bootlader (it says "waiting for device") although adb devices sees it,
re-installing the adb drivers after uninstalling them,
disassembling the device to see if I can detach memory to edit it and to see if disconnecting the battery helps,
I even used a simple jig to see if i can initiate download mode (know it works for specific devices but you know hope)
Apparently, I messed up the device but the hardware must be all fine. So I think there must be a way out. What can you suggest, I wish I have unlocked the bootloader. I can send the pictures of its motheboard it helps,
Thanks in advance.
Previously, I had this phone rooted, and running CM12 with an open source gapps setup, with no problems. I also had TWRP installed, and an SD card with a copy of my ROM as I liked it, and my data.
Everything worked, and I was able to update my Android version and expand functionality quite a bit, which was useful while traveling abroad.
The other day however, when seconds before I had been using it as my hotspot, I tripped over the charging cord and dropped the phone quite hard on tile.
It broke into pieces, with the back coming off and the battery coming out.. The display is fine. I thought I killed it entirely, but I took the battery out and left it alone for half a day, and when I came home, I realized that it would:
1. Charge
2. Boot to recovery
3. Boot to download
This gave me some hope.
However, doing anything else would result in a bootloop.
I booted into recovery in preparation to re-flash my rom, and TWRP was not able to mount my SD card, and would not recognize my data there.
Additionally, when I tried to wipe everything but my SD card, TWRP failed to mount all partitions, as if something got corrupted.
When I tried to repair or change the file system type, this too failed. I cannot seem to get TWRP to recognize any storage. It says the phone is empty, with no internal, no external, and no OS.
Just a bunch of red "failed" lines every time I try to do something through the recovery.
I checked my SD card externally using an adapter on my mac, to make sure it was not corrupted. All my data is still there, including the backup of my ROM. However, since the phone will not recognize it, it's useless, and I can't find an Odin flashable .tar version of the CM12 ROM for this phone, plus when I tried to convert a copy to the correct file type, it failed to flash.
I tried to flash a copy of the stock rom (metroPCS version) to begin with, that I had saved on my computer.... which worked before when I messed up my initial flash. This time, It will flash successfully per Odin, but cause a bootloop.
Odin will still recognize my device... but adb from my mac terminal will not recognize it when I have the device connected or I would try to rebuild the file system that way.
I feel like I am going in circles and running out of options, or missing something..(possibly several things) but... I don't want to give up on this phone just yet, even if I had to demote it from daily driver use in the end ... any advice would be appreciated.... Thank you sooooo much!
Edited to add: I got ADB to recognize the device and ran a restore command, based on a file I had locally. This is what happened:
localhost:~ user$ adb restore ~/Downloads/cm-12-20150319-UNOFFICIAL-gardalte.zip
Now unlock your device and confirm the restore operation.
/sbin/sh: /sbin/bu: not found
Also adb remount resulted in a failed output.
Lastly, it appears abd only works in terms of recognizing my device when I am in recovery.
Hello everyone, a couple of months now are also thanks to you in the world of modding. Yesterday (i have a Xiaomi Mi A2 Lite) during the installation of a custom ROM using ADB, typing in the fastboot command "erase system", I wrote erase a_boot for error because before I was reading a post about it and I wrote it. Yes I know, I was too stupid. Result? The phone does not start up either in recovery or in fastboot mode, and from the PC it is recognized as COM port. I have already documented about it and tried to flash everything with the Qualcomm tool after installing the drivers but nothing. I tried the EDL by activating it manually to unlock port 9008, but still during the flash gives me error. I tried everything, do it all over again in a newly formatted and clean PC from any other driver, but nothing. During the flash, even if I put the firmware in the same directory, it still gives me error. Guys I'm desperate please. I do not know what else to do. I hope to receive your answers :crying::crying::crying:
I also have same problem.. if you find some solution then tell me also.. my device is different.. but problem is same.. device basically dead & can be recognised in com port