For kicks I tried a GSI ROM on my Jelly 2. It worked well except GSI ROMs don't seem to work well with VZW. So I'm looking to revert to the stock ROM. I have gone through the guide they posted here https://drive.google.com/file/d/1qVlaYucvE44ZJqF1RCHGknEBQWy_Z65m/view and I have the drivers installed and the phone is recognized as "MediaTek PreLoader USB VCOM (Android) (COMx)". Using their flash tool linked from the doc, the tool recognizes the phone on COMx (x depends on which USB port the cable is plugged into) and when I click "Start All" in the tool, in about 3-5 seconds the progress bar fills red to 100% and says "DA" in front of it. Then at about 125s, "DA" changes to "DA ERROR" and that's the end of the process.
Here are some screenshots showing the port in device manager and the flash tool with the "DA ERROR".
I've tried this from different laptops and different cables (the one that came with the phone and a different USB-A to USB-C cable) with no joy. I'm working with their support, but the time difference means communication is slow.
I've tried this with the bootloader locked and unlocked.
The IMEI for the Jelly 2 was recognized as a Jelly Pro, so Unihertz support provided me with an OTA file and instructions for installing it by downloading it to the phone and the using their built in local flash option to install it. They also provided 2 new IMEI numbers that I manually entered after flashing the OTA. This all worked fine, but they note that the IMEIs will revert to their original values after a factory reset. This was done before I flashed the GSI ROM, so I'm mentioning it in case it gives insight into whatever "DA ERROR" means.
Has anyone gone through this process successfully and have any tips?
bra1niac said:
For kicks I tried a GSI ROM on my Jelly 2. It worked well except GSI ROMs don't seem to work well with VZW. So I'm looking to revert to the stock ROM. I have gone through the guide they posted here https://drive.google.com/file/d/1qVlaYucvE44ZJqF1RCHGknEBQWy_Z65m/view and I have the drivers installed and the phone is recognized as "MediaTek PreLoader USB VCOM (Android) (COMx)". Using their flash tool linked from the doc, the tool recognizes the phone on COMx (x depends on which USB port the cable is plugged into) and when I click "Start All" in the tool, in about 3-5 seconds the progress bar fills red to 100% and says "DA" in front of it. Then at about 125s, "DA" changes to "DA ERROR" and that's the end of the process.
Here are some screenshots showing the port in device manager and the flash tool with the "DA ERROR".
I've tried this from different laptops and different cables (the one that came with the phone and a different USB-A to USB-C cable) with no joy. I'm working with their support, but the time difference means communication is slow.
I've tried this with the bootloader locked and unlocked.
The IMEI for the Jelly 2 was recognized as a Jelly Pro, so Unihertz support provided me with an OTA file and instructions for installing it by downloading it to the phone and the using their built in local flash option to install it. They also provided 2 new IMEI numbers that I manually entered after flashing the OTA. This all worked fine, but they note that the IMEIs will revert to their original values after a factory reset. This was done before I flashed the GSI ROM, so I'm mentioning it in case it gives insight into whatever "DA ERROR" means.
Has anyone gone through this process successfully and have any tips?
Click to expand...
Click to collapse
Answering my own question, while I could never resolve the DA ERROR running the SP TOOL on a Windows laptop, it worked running the Linux version from a bootable thumb drive on the same laptop. No idea on this one but I'm not going to dig any deeper. I used fireiso-2.0.0 as the bootable Linux thumb drive and downloaded the Linux SP Tool after the system booted up. Ran it with no changes to anything and it just worked.
Related
I installed 4 different romsof JB on my Razr and the results are always the same: Loss of USB connectivity
The USB connectivity not working, my pc does not recognize my phone, either MTP or Mass Storage .... nothing went wrong in the installation did everything step by step, after flashing the rom, I warned of the recovery that might have been lost root access, if and only wanted to fix that if I put all my works between exept the usb transfer. I use BMM 0.3.4...
The drivers are installed properly on my pc because ICS works fine with USB mode. I tried different cables and different computers but the result is the same.
Any Help? Please!!
I have exactly the same problem.
My razr is GSM - LATAM device. By february I installed JB leak from China. After some time with it, I decided to go back to stock ICS due to some locale issues/random bugs.
Now my razr lost all USB connectivity. RSDLite can't "see" my phone even if I boot on AP Fastboot mode.
Openned this topic today: http://forum.xda-developers.com/showthread.php?t=2178919&highlight=usb+connectivity
I managed to switch back to moto's stock ICS through a NANDROID that a guy uploaded.... had to use a micro-SD so I could pass the zip to my phone.
Still, my phone has no USB connectivity at all. =(
emmanueldmc said:
I installed 4 different romsof JB on my Razr and the results are always the same: Loss of USB connectivity
The USB connectivity not working, my pc does not recognize my phone, either MTP or Mass Storage .... nothing went wrong in the installation did everything step by step, after flashing the rom, I warned of the recovery that might have been lost root access, if and only wanted to fix that if I put all my works between exept the usb transfer. I use BMM 0.3.4...
The drivers are installed properly on my pc because ICS works fine with USB mode. I tried different cables and different computers but the result is the same.
Any Help? Please!!
Click to expand...
Click to collapse
The charging port is failing. Mine is doing the same. Sent it in for warranty repairs and they claimed it was fine. Moto tech support is worthless and you are better off finding someone to replace it or doing it yourself.
Hello guys, I have this GT-I9300 I tried to flash two days ago, rather unsuccessfully. First I rooted it successfully and then installed TWRP 2.7.0.0. I used this recovery to install the Android Revolution HD 52.0 ROM. I did a full wipe then installed the ROM, it however, didn't complete flashing. It failed during the moment it was flashing the modem with an "assert failed" message, but it presented me with a "NEXT" button. I used this to reboot the phone. The phone rebooted well, however, the IMEI is blank and under Settings, the normal stuff that enable me to choose between MTP, Tethering, etc are missing. Connecting it to my PC makes no difference either, my PC does not recognize the phone, the normal USB sounds are not there, I've switched cables and the result is the same. The cables I've used are working well as I can use them with my G2 well. Without the ability to connect the phone with my PC I can't do anything with ADB. What can I do guys?
Flash stock firmware with Odin
I fixed the problem. I flashed the kernels in this page one by one until the "Patched_XXEMC2_Modem.zip" contained in the page fixed both my IMEI null/null and Baseband Unknown errors. All is well now.
Hopefully somebody can help me this this. I was attempting to flash back to the original firmware to get back to the unrooted ROM and it seems like during the process the phone or cable disconnected and now it's stuck on the Firmware Update screen and the little console box on the bottom reads "VUSER B99". The computer seems to recognize the phone in device manager as LGE Androidnet for VZW, however nothing seems to change when I try to run the LG flash program. I've used the program twice before and both times it worked perfectly.
I've tried booting into TWRP recovery, entering download mode, and battery pulls, but nothing changes once it boots. I'm using the LGFlash tool and VS98510B_03.tot. I had the JasmineROM v5.0 on it before I was trying to revert back. Has anybody seen this before? I tried searching and found a few similar problems, but no conclusive solutions and none for the G3.
Update --> solved
In case this happens to anyone else, I found the solution was to use a different computer. For whatever reason, I was no longer able to use the computer that I had previously used for flashing the stock firmware. Apparently, the stock cable that I have, and was using, is slightly worn out and the computer lost the connection during the process, which soft bricked the phone on the update firmware screen.
I downloaded all programs and drivers on a new windows 8 laptop and it worked on the first try. Hopefully this helps if this happens to anyone else.
Hi guys
I've just received Tanix TX9S android box and I'm trying to flash a custom rom but my computer doesn't detect the box. I'm using Win 10 Pro 64bit and I've tried reinstalling the burning tool, installing with driver signature off, restarting, changing usb ports on both the pc and the box but it just doesn't work. I'm using this cable: https://www.aliexpress.com/item/4000574237363.html
Any ideas?
kalehrl said:
Hi guys
I've just received Tanix TX9S android box and I'm trying to flash a custom rom but my computer doesn't detect the box. I'm using Win 10 Pro 64bit and I've tried reinstalling the burning tool, installing with driver signature off, restarting, changing usb ports on both the pc and the box but it just doesn't work. I'm using this cable: https://www.aliexpress.com/item/4000574237363.html
Any ideas?
Click to expand...
Click to collapse
Cable Looks Quite Thin, It Says IUts A Data Cable So Should Work Just Might Not Provide Enough Power, Try Connecting Power At Same Time, that may help, or you might have to use mask rom mode to force your box to be detected
I tried connecting power but to no avail. I don't think I will be opening the box so I'll have to live with stock ROM
kalehrl said:
I tried connecting power but to no avail. I don't think I will be opening the box so I'll have to live with stock ROM
Click to expand...
Click to collapse
Aww, something you should try, when you eventually upgrade and it becomes a spare device
Maybe I can try with an sd card.
I also have some logs in amlogic folder.
I've noticed 'NoDeviceConnected' error and sometimes 'Other device'.
kalehrl said:
Maybe I can try with an sd card.
I also have some logs in amlogic folder.
I've noticed 'NoDeviceConnected' error and sometimes 'Other device'.
Click to expand...
Click to collapse
Yhea SD Card Is Another Option, i Just Generally don't recommend This Method as if you flash a incompatible firmware and your device wont turn on then USB Burn Tool Will Be needed To Fix And Flash From a "Bricked" State
I managed to flash my box.
I used the latest burning tool v3.1.0. During the installation, I plugged my box into the computer and saw that it not only installed world cup drivers, but additional ones as well which was a good sign. I also had to use the power supply because usb didn't output enough power.
kalehrl said:
I managed to flash my box.
I used the latest burning tool v3.1.0. During the installation, I plugged my box into the computer and saw that it not only installed world cup drivers, but additional ones as well which was a good sign. I also had to use the power supply because usb didn't output enough power.
Click to expand...
Click to collapse
I have the same issues. At the moment that you plugged in your box with usb cable was your box already on power? en did you have to use the reset by toothpick reset at the time you plugged in?
BUZZTV XRS4900
Yes, already on power and I used a toothpick.
But flashing is hit and miss with amlogic burning tool.
Sometimes it works, sometimes doesn't.
Try a different computer because for one of my boxes I had to use a Windows 7 machine.
kalehrl said:
Yes, already on power and I used a toothpick.
But flashing is hit and miss with amlogic burning tool.
Sometimes it works, sometimes doesn't.
Try a different computer because for one of my boxes I had to use a Windows 7 machine.
Click to expand...
Click to collapse
Thank you.. I tried several options and cables and pc's.
When on power the toothpick doesn't work because it is already operational i guess
I try the mask rom method. Hope that will do the job
kalehrl said:
I managed to flash my box.
I used the latest burning tool v3.1.0. During the installation, I plugged my box into the computer and saw that it not only installed world cup drivers, but additional ones as well which was a good sign. I also had to use the power supply because usb didn't output enough power.
Click to expand...
Click to collapse
this doesn't sound like a good sign to me... world cup drivers !!??
I've yet to flash my box and I'm really put off by the fact that guides mention to ignore virus warnings and just to click OK. I haven't yet seen it uploaded onto xda either which makes me confident.
Try older versions of the Amlogic USB Burning Tool, newer versions might not work with older boxes.
You can find most of the versions here: Amlogic USB Burning Tool - All Versions
The problem was the cable. The Chinese one I bought first didn't work properly. The cheapest one from Amazon worked fine.
Same here mine to does not detect but i have noticed in device manager it appears an unknown device
Reinstall the driver.
EdT586 said:
Try older versions of the Amlogic USB Burning Tool, newer versions might not work with older boxes.
You can find most of the versions here: Amlogic USB Burning Tool - All Versions
Click to expand...
Click to collapse
thxy men, i tried use the latest version and don't work, after saw ur comment i can revive my tv boxes
Hello to all,
I tried to install GrapheneOS today.
I managed to unlock the bootloader.
But when I had to install GrapheneOS I encountered the error "Error: Failed to execute 'claimInterface' on 'USBDevice': Unable to claim interface." with the installation via the web interface of my browser (there were disconnections while I just used the new cable of my Pixel) and another connection error but I don't remember it ("device not found" maybe)
Before this, I tried the command line installation from Windows 11 and encountered the "waiting for any device" error when running "./flash-all.bat"
I should point out that I had performed the driver search via Windows update and Windows had not found anything even in the optional updates.
When I went to the device manager, I didn't see any devices that needed drivers installed / I didn't see the Pixel (which was connected via USB-C / USB-C (Thunderbolt)
So my assumption is that the powershell script ran when I tried to install GrapheneOS (it was still running in the background, I should have stopped closing Powershell) via the browser-based installation and there was a disconnect which resulted in a brick.
After the ROM flash attempt, I rebooted my phone and got the warning tips about the bootloader being unlocked and the ROM not being official with the traditional "g.co/ABH" link.
My second hypothesis is that my phone has no battery left because it came without a charger, so I used the charger of my OnePlus to charge it but it was charging very slowly (estimated 3+ days...).
What do you think about it ?
Should I buy the official Google 30W charger to see what it does? even if I think I have no choice.
Do you think I could debrick my phone (if it is bricked) ?
I am attaching a picture of what my phone is currently displaying (even when it is not plugged in)
take phone off the laptop and charge over night, if the oem unlock is enabled, there shouldnt be any issue in using google recovery or flashing any other method
Ok thank you, I'll do that
Hope it will work
Holdor said:
Hello to all,
I tried to install GrapheneOS today.
I managed to unlock the bootloader.
But when I had to install GrapheneOS I encountered the error "Error: Failed to execute 'claimInterface' on 'USBDevice': Unable to claim interface." with the installation via the web interface of my browser (there were disconnections while I just used the new cable of my Pixel) and another connection error but I don't remember it ("device not found" maybe)
Before this, I tried the command line installation from Windows 11 and encountered the "waiting for any device" error when running "./flash-all.bat"
I should point out that I had performed the driver search via Windows update and Windows had not found anything even in the optional updates.
When I went to the device manager, I didn't see any devices that needed drivers installed / I didn't see the Pixel (which was connected via USB-C / USB-C (Thunderbolt)
So my assumption is that the powershell script ran when I tried to install GrapheneOS (it was still running in the background, I should have stopped closing Powershell) via the browser-based installation and there was a disconnect which resulted in a brick.
After the ROM flash attempt, I rebooted my phone and got the warning tips about the bootloader being unlocked and the ROM not being official with the traditional "g.co/ABH" link.
My second hypothesis is that my phone has no battery left because it came without a charger, so I used the charger of my OnePlus to charge it but it was charging very slowly (estimated 3+ days...).
What do you think about it ?
Should I buy the official Google 30W charger to see what it does? even if I think I have no choice.
Do you think I could debrick my phone (if it is bricked) ?
I am attaching a picture of what my phone is currently displaying (even when it is not plugged in)
Click to expand...
Click to collapse
Make sure you have this installed. Also, would suggest you use USB-C to USB-A.
Also make sure your Platform Tools are up-to-date.
You can also use Android Flash Tool to get back to stock.