bad firmware flash on U10L smartwatch help needed please
I have a bricked U10L smart watch and I am looking for any help here. In following the firmware upgrade video I got tne the point of connecting the watch. However I did that before hitting download on the flash tool. I think that was a huge mistake as my windows 7 box installed a driver from microsoft. I did not get a pop up window letting me choose the driver from the downloaded files. So when I replugged the watch in it did start downloading but the firmare update to v006 failed. Now the watch isn't recognized and so I can't force the driver to be installed. I get "Windows has stopped this device because it has reported problems. (Code 43)" The driver details show "no driver are required or have been loaded for this device". I realize I should never have plugged it back in with the wrong driver file. live and learn I guess. Is there anything I can do or is it basically a brick. I have tried unistallng the driver and installing from the downloaded file but when I select the driver file it won't install as it doesn't recognize the hardware. Any help would be appreciated but my feeling is I'm out of luck here
jm_maclaren said:
I have a bricked U10L smart watch and I am looking for any help here. In following the firmware upgrade video I got tne the point of connecting the watch. However I did that before hitting download on the flash tool. I think that was a huge mistake as my windows 7 box installed a driver from microsoft. I did not get a pop up window letting me choose the driver from the downloaded files. So when I replugged the watch in it did start downloading but the firmare update to v006 failed. Now the watch isn't recognized and so I can't force the driver to be installed. I get "Windows has stopped this device because it has reported problems. (Code 43)" The driver details show "no driver are required or have been loaded for this device". I realize I should never have plugged it back in with the wrong driver file. live and learn I guess. Is there anything I can do or is it basically a brick. I have tried unistallng the driver and installing from the downloaded file but when I select the driver file it won't install as it doesn't recognize the hardware. Any help would be appreciated but my feeling is I'm out of luck here
Click to expand...
Click to collapse
I left the watch conected to a charger overnight and this morning it was working and updated to v006. I cannot explain this, the firmware gods were smiling on me
Hey man I have the same problem now.....Wonder if You found any solution other than the miracle that happened to You ;P
Its happened to me twice, in both cases leaving the watch charging overnight led it to be able to reboot with updated firmware. As there seemed little change between firmware revisions I leave it alone now. I can't explain why the watch did this it just did! Nor have I found another way to revive after the firmware flash. Sorry I'm not more helpful to you.
Related
So apparently, I went home and usually put my phone into my desk.
While I took it from my pocket, I noticed the hardware buttons were lit but no display, I removed the battery to restart, during the week, frozen screen were occurring a dozen times when playing Clash, that though I didn't mind I just said to myself I will reflash the rom in the weekend.
But up to now,
It won't turn on, recovery mode or anything also doesn't work
It wont charge
Tried a new battery but still no luck
I think PC reads it but SPFT wont
Any suggestion on how I can revive my phone?
Attached is the error I get from SPFT
I don't own the A120 anymore. That is almost similar to this, as you might know.
Anyway, as nobody has answered your question, I will try to help as much as I can.
Does it give you a haptic feedback(vibration) when you try to power on the device?
Are you saying that it won't turn on completely?
If it is being detected on the computer and not on SPFT, you might want to check with the drivers you have. Do you have the MTK VCOM drivers installed? (I'm not really sure about the name, but it was something like that).
And try flashing the Stock ROM with SPFT with your battery removed from the phone.
Download the drivers.
Connect your phone without the battery and keep your device manager open, if it shows a device with a yellow exclamation mark beside it, right click and click on properties. You will have to do this quickly.
Once that is done, go to driver tab on the properties window. Select Update Driver. Browse my computer and enter the location of your downloaded and unzipped drivers.
(You might get a digital signature error or something similar. I'll tell you how to bypass that in the end. If you get that, go to the end, follow those steps and then come back and do all the steps after the downloading part.)
If the drivers are successfully installed, then unplug your device, run the SPFT and load the Scatter file of the Stock ROM.
Now select Download only and start the download, it will wait for you to connect the phone.
Plug in your phone without the battery. This should initialize the download process.
Now wait for the flash to be completed and if it is successful, take out your phone and boot it. If it boots up, congratulations.
If it does not, flash the same ROM the same way another time and check, if it is still not working, try with Firmware upgrade mode, twice. It should work in those tries.
Digital Signature Error bypassing.
I know only one method which works on Windows 8 and above(Tested).
Hold the Shift key while pressing Reboot.(Yes, you have to reboot your PC)
Once there is a blue screen with options, you should see "Troubleshoot". Select that.
Then Advanced Options and then Start Up settings. Then press Restart.
This will show you a menu with a lot of options. Select the option number which says "Disable Driver Signature Enforcement".
This will log you into the PC normally, but now, you can go back and do all the steps again and you won't get an error.
Cheers!
If this still doesn't help you, let me know on what happens so I can try to get you back your phone. Hope this helps.
WalterWh1te said:
I don't own the A120 anymore. That is almost similar to this, as you might know.
Anyway, as nobody has answered your question, I will try to help as much as I can.
Does it give you a haptic feedback(vibration) when you try to power on the device?
Are you saying that it won't turn on completely?
If it is being detected on the computer and not on SPFT, you might want to check with the drivers you have. Do you have the MTK VCOM drivers installed? (I'm not really sure about the name, but it was something like that).
And try flashing the Stock ROM with SPFT with your battery removed from the phone.
Download the drivers.
Connect your phone without the battery and keep your device manager open, if it shows a device with a yellow exclamation mark beside it, right click and click on properties. You will have to do this quickly.
Once that is done, go to driver tab on the properties window. Select Update Driver. Browse my computer and enter the location of your downloaded and unzipped drivers.
(You might get a digital signature error or something similar. I'll tell you how to bypass that in the end. If you get that, go to the end, follow those steps and then come back and do all the steps after the downloading part.)
If the drivers are successfully installed, then unplug your device, run the SPFT and load the Scatter file of the Stock ROM.
Now select Download only and start the download, it will wait for you to connect the phone.
Plug in your phone without the battery. This should initialize the download process.
Now wait for the flash to be completed and if it is successful, take out your phone and boot it. If it boots up, congratulations.
If it does not, flash the same ROM the same way another time and check, if it is still not working, try with Firmware upgrade mode, twice. It should work in those tries.
Digital Signature Error bypassing.
I know only one method which works on Windows 8 and above(Tested).
Hold the Shift key while pressing Reboot.(Yes, you have to reboot your PC)
Once there is a blue screen with options, you should see "Troubleshoot". Select that.
Then Advanced Options and then Start Up settings. Then press Restart.
This will show you a menu with a lot of options. Select the option number which says "Disable Driver Signature Enforcement".
This will log you into the PC normally, but now, you can go back and do all the steps again and you won't get an error.
Cheers!
If this still doesn't help you, let me know on what happens so I can try to get you back your phone. Hope this helps.
Click to expand...
Click to collapse
Thanks bro, but I already gave up and bought a new one because I badly need an android device for my mini accounts in CoC. Haha but I am till trying to revive my Rio during my free time, this has been my phone for 1 1/2 year..
Yes I am aware that Rio is rebranded A120, I also asked from CM12.1 and AOSP LP Wiko Rainbow threads and some suggested help. Tried all that but still same errors.
No, there's no response of any kind including vibration when turning on. Hmn, as per the drivers, I've been using Tinno Driver since the jelly bean era of this phone, no problems or whatsoever from jb to kk to lp using that driver, so I thought there would be no problems. Still no luck in getting success. Using different versions of SPFT, using sp flashable Rio jb, kk, MMX A120 jb, kk, Wiko kk,lp stock roms, still no luck. Tried every port and cord. And I am using the Win7 64bit, I also resorted to MTK drivers, both the preloader and Da. Still.. No luck. Haha. I also tried, download only, format all+download, and firmware upgrade option with every possible combination from above but no success..
Thanks for your answer btw!
I was trying to flash CM11 ROM in my Samsung Galaxy Ace GT-S5830, for that I have also installed CWM 6.0.5.3. While flashing ROM from recovery it failed with some error message, I tried it once again and again it stopped with the same error message. I decided to try some other ROM and kept mobile on side to search new rom, the mobile was still in recovery mode connected with usb for charging, after a minute as I saw at my mobile it was not in recovery mode, the screen was OFF. I tried to restart it again & again but failed, I even tried to start it in recovery mode but failed. Tried overnight charging, thinking that its battery is down, but failed to restart it. Then I searched about it on google, and came to know it was bricked with solution to flash it with stock rom using Odin, if it is still getting detected in PC. My PC is still detecting my mobile, tried flashing stock rom using Odin, but it is getting stuck at "< 1 >setup connection...". I don't know what to do now. My mobile is not in warranty, so no way in getting it repaired from service center. If anyone know any solution for this, then please tell me. I am eagerly waiting for your reply. Moderators, please don't delete this thread saying to go and search for same kind of threads, I have already done that & at last posted in new thread. Please Help me as soon as possible. Thanks..
http://download1187.mediafire.com/eew353b6p3sg/y2yja47mu5ew4g5/samsung+Galaxy-Ace+gt-s5830.rar
Extract it, open "S5830_Odin+Multi+Downloader+v4.38.exe" then in the OPS section select the .ops file in the extracted folder, then give a check on "One package" check box. Then on the bottom press the "One package" button and select the firmware in the folder and you're done !
P.S. If that doesn't work, try reinstalling Samsung USB Drivers, removing Kies, switching cables, ports or even PC's (if possible)
Reposting it here, since this is the Lenovo sub-forums. Probably may find more help here.
I was using the Allegro ROM for the A1000G and it was running fine and dandy without any problems. Last night I tried installing a game and after I restarted it, it didn't turn on. I thought that maybe the device had low battery or something. So I plugged it in and let it charge for an hour and it still didn't turn on. Than I let it charge overnight and in the morning, it still doesn't turn on. So I tried to flash the Stock ROM for Lenovo a1000g and I got an error saying the storage was different or something - Error 3182 Message: BROM ERROR: S_STORAGE_NOT_MATCH (3182) [Edit - Tried to find the error, this is the one]
It was probably because the Allegro ROM was installed before it stopped working. So after that failed attempt at Flashing the Stock ROM - I don't get the battery indicator anymore and no matter what I try inside SP Flash Tool, it doesn't detect the device and the flashing process doesn't work. I tried installing and uninstalling all the MTK and Mediatek drivers but still not working. It shows up as MediaTek DA USB VCOM (Android) but it doesn't disappear, unless I remove the usb cable.
Before when I flashed the Allegro ROM and as seen across other youtube tutorials and guide, the device would show up for 2-4 seconds before disappearing and the SP Flash Tool would start working. Now it is just blank and the MediaTek DA USB VCOM (Android) doesn't go, no matter what.
Please, I would appreciate help. Since I don't have much knowledge regarding this. What must I do? I am depending on you guys.
~Aaron.
Bump. Please someone help.
__PUMA__ said:
Bump. Please someone help.
Click to expand...
Click to collapse
Thread closed as duplicate. I have left this one open
https://forum.xda-developers.com/th...p-lenovo-a1000-g-indian-version-hard-t3630644
but closed the others. Please do not make any more duplicates
Sawdoctor
Reposting it here, since this is the Lenovo sub-forums. Probably may find more help here.
I was using the Allegro ROM for the A1000G and it was running fine and dandy without any problems. Last night I tried installing a game and after I restarted it, it didn't turn on. I thought that maybe the device had low battery or something. So I plugged it in and let it charge for an hour and it still didn't turn on. Than I let it charge overnight and in the morning, it still doesn't turn on. So I tried to flash the Stock ROM for Lenovo a1000g and I got an error saying the storage was different or something - Error 3182 Message: BROM ERROR: S_STORAGE_NOT_MATCH (3182) [Edit - Tried to find the error, this is the one]
It was probably because the Allegro ROM was installed before it stopped working. So after that failed attempt at Flashing the Stock ROM - I don't get the battery indicator anymore and no matter what I try inside SP Flash Tool, it doesn't detect the device and the flashing process doesn't work. I tried installing and uninstalling all the MTK and Mediatek drivers but still not working. It shows up as MediaTek DA USB VCOM (Android) but it doesn't disappear, unless I remove the usb cable.
Before when I flashed the Allegro ROM and as seen across other youtube tutorials and guide, the device would show up for 2-4 seconds before disappearing and the SP Flash Tool would start working. Now it is just blank and the MediaTek DA USB VCOM (Android) doesn't go, no matter what.
Please, I would appreciate help. Since I don't have much knowledge regarding this. What must I do? I am depending on you guys.
~Aaron.
Bump. Please someone help.
So yeah, I screw up by a lot, but let's see if someone can help me/
I tried to update twrp on my phone and it got bricked, ADB was not seeing the device but Mi FlashTool was with a code but not COM, tried changing the phone drivers brom 900E to QL8000 and it got registered by MiFlashtool as COM and another code, the phone was still showing there even if I could not make the phone go to fastboot mode, just blackscreen; I tried to reinstall stock rom with it but got stuck at "flashing", disconnected the phone, the phone was still bricked in a black screen, when trying to reconnect the phone again to the pc, Win10 now displays an error
https://imgur.com/a/VS1yh6t
,
https://imgur.com/a/4PxUD7E
, I already tried uninstalling the device, deleting and reinstalling the drivers (unable because for some reason they won't appear now, but already tried installing the from their 1st party and prom MiFlashTool), so the phone won't turn on, display anything, go into recovery/fastboot, and I don't know what to do now, is the phone lost? I hope you can help me with this issue.
Hello Bro. Try install latest Mi Flash Tool latest version and then install the drivers. For my it's works in windows 10.