Hello Guys,
Ok, I have been searching and searching, but cannot find the answer to my problem. I am using the LG G Watch Tool to return my watch to stock, then update it with the OTA provided in an update.zip
1) My bootloader is unlocked (LG Unlock icon at bottom)
2) My ROM was rooted
Everytime I connect the watch while it is in the bootloader, it is recognized by my PC and it says Fastboot. When the ROM did boot up, it would also be connected through ADB and showing on the list of connected devices.
Based on the screenshot below, I am able to erase the system image, but it gets stuck sending the system.img. Even when I try boot.img, or any other ADB command, it delays indefinitely.
Any thoughts?
When I disconnect the device, it say error too many links
mischief4l said:
When I disconnect the device, it say error too many links
Click to expand...
Click to collapse
You shouldn't disconnect while fastboot is sending an image. The system images can be large and fastboot takes a small amount of time to send it over the interface. When it says sending [system] you'll want to look at your watch and down by the on-screen buttons, there should be some red or green text that says "Downloading..." flashing. You may also want to try another USB port.
Related
I have a Nexus 9 Wi-Fi model, my PC runs Windows 8.1, and I am not new to rooting and custom ROMs. I attempted to install the M dev preview to the tablet following the instructions on Google's site. In the process, my console window showed one of the instances of "sending sparse 'system'" had FAILED. Now the device will not boot. It is stuck on the white Google logo splash screen. ADB does not recognize it, although it does appear in Windows Device Manager as "MTP USB Device". When I attempt to turn the device off or reboot it using any combination of power and volume keys, the screen will go blank for a few seconds and then return to the Google logo. I cannot turn the device off.
I've never seen this before, even with a failed flash... it's supposedly just the system partition that failed, anyway. Any ideas how I can break free of this?
EDIT: I ended up locating this post. If I hold the power button down until the screen turns off and then immediately press and hold power+voldn, it will launch the bootloader.
I've no experience with flashing M. But I have a suspicion that you flash of the system.img failed because of an obsolete fastboot on your PC. I'd suggest starting by updating your Android SDK. Then you can try fastboot flashing the M system.img again. Or fastboot flash the stock 5.1.1/factory image to return to stock.
soft bricked is all it is.
Made sure I had the latest Fastboot, ADB
Rebooted into Fastboot
Ran the Flash All batch file and it failed to install the System
I found instructions on flashing manually this from what was post is very common.
You extract all files, flash the boot, reset, and flash all the others.
Do a Google search it was easy enough to find.
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.
Recently while flashing alpha version of MIUI marshmallow on my Mi 4w, my phone got completely bricked. Complete brick in the sense, it won't turn on, neither charge nor show any led indication. This guide should work on other phones also.Let's start:-
1) Although it seems like your phone wont turn on, your phone is actually working, it's just it wont show anything on the screen(no display).
Make sure your phone is charged properly(it will charge even if the led doesn't show any indication).
2) Download and install Mi flash tool and then Fastboot file of your device. http://en.miui.com/a-234.html
3) Unzip the fastboot image, a folder containing flash all.bat should appear if not, extract the extracted file again. Winrar should work fine.
4) Now open Mi flash tool(as administrator) and select the fastboot folder from Mi flash using browse option and also select the proper fastboot script according to need.
Note: Flash_all.bat will completely erase your internal storage.
5) Now press volume down(-) and power key to enter into fastboot. Note: it won't show any visual whatsoever but it'll work.
6) Connect your phone to your pc. It should show various flash devices connected to your computer and those devices may continuosly connect and disconnect. If not it'll show QHUSUB_BULK install the driver using device manager.
7) On Mi flash tool, some device name should show on the devices list if not click refresh and try reconnecting the device. Note: If you dont have proper drivers installed on your pc, this procedure won't work.
8) Finally click on flash and flashing will start. It'll take some time. Once done it'll show operation completed successfully.
9) Finally boot your device using power key.
Brick has received QHSUSB_BULK simple. This is the normal and regular encounter. Hardbrick, you must check point.
2ConHeo said:
Brick has received QHSUSB_BULK simple. This is the normal and regular encounter. Hardbrick, you must check point.
Click to expand...
Click to collapse
who said so?
tested and working
that normal check point is a pain in ass to execute in the first place
Thanks a ton.....It helped a lot
thank u...
thank
How do I put the phone into fastboot mode if it is hard bricked? It won't turn on, I get no responce from phone. When I use method connecting test point to metal cover on mother board of phone usb connects to PC and MiFlash recognizes phone. Try to flash though and I get an error message. No matter what ROM I use, zipped, unzipped or tgz file. Can my phone be unbricked? What am I doing wrong? I have a Mi Max 64GB and am using HELIUM Roms. Please help. Error message is:
The filename, directory name, or volume label is incorrect.(0x8007007b: Open programmer "MPRG*.hex").
I have no clue. Not my first time flashing ROMs or unbricking a phone. It is my first time on a Xiaomi. Only done blackberry and samsung before.
hammer77 said:
How do I put the phone into fastboot mode if it is hard bricked? It won't turn on, I get no responce from phone. When I use method connecting test point to metal cover on mother board of phone usb connects to PC and MiFlash recognizes phone. Try to flash though and I get an error message. No matter what ROM I use, zipped, unzipped or tgz file. Can my phone be unbricked? What am I doing wrong? I have a Mi Max 64GB and am using HELIUM Roms. Please help. Error message is:
The filename, directory name, or volume label is incorrect.(0x8007007b: Open programmer "MPRG*.hex").
I have no clue. Not my first time flashing ROMs or unbricking a phone. It is my first time on a Xiaomi. Only done blackberry and samsung before.
Click to expand...
Click to collapse
did you solve the problem ?
Rajdip said:
Recently while flashing alpha version of MIUI marshmallow on my Mi 4w, my phone got completely bricked. Complete brick in the sense, it won't turn on, neither charge nor show any led indication. This guide should work on other phones also.Let's start:-
1) Although it seems like your phone wont turn on, your phone is actually working, it's just it wont show anything on the screen(no display).
Make sure your phone is charged properly(it will charge even if the led doesn't show any indication).
2) Download and install Mi flash tool and then Fastboot file of your device. http://en.miui.com/a-234.html
3) Unzip the fastboot image, a folder containing flash all.bat should appear if not, extract the extracted file again. Winrar should work fine.
4) Now open Mi flash tool(as administrator) and select the fastboot folder from Mi flash using browse option and also select the proper fastboot script according to need.
Note: Flash_all.bat will completely erase your internal storage.
5) Now press volume down(-) and power key to enter into fastboot. Note: it won't show any visual whatsoever but it'll work.
6) Connect your phone to your pc. It should show various flash devices connected to your computer and those devices may continuosly connect and disconnect. If not it'll show QHUSUB_BULK install the driver using device manager.
7) On Mi flash tool, some device name should show on the devices list if not click refresh and try reconnecting the device. Note: If you dont have proper drivers installed on your pc, this procedure won't work.
8) Finally click on flash and flashing will start. It'll take some time. Once done it'll show operation completed successfully.
9) Finally boot your device using power key.
Click to expand...
Click to collapse
Link not working.
Using another mi flash tool also get nothing. How do I know I get into fastboot?
Already pressed volume down and power button but nothing happened. And checking fastboot devices nothing comes up. Also in mi flash tool nothing.
hi, i work helping my classmates when they stuck on their phones... ok, i'm apologize for my bad english but here is the thing, i now have one Huawei G610-U00 and the phone say "Encryption unsuccessful", i notice that him install the twrp recovery so i try flashing a new recovery using fastboot and the fastboot only say "sending 'recovery'" and nothing else happens(i left all the night, the phone only discharge the battery,), make a search on google and find info related and try them, try using sp flash, try installing a new zip, even try a force-update but when press the vol + and - and the power key, the phone go to recovery, also in the bootloader mode it only say "recovery_status:UPDATED" nothing else, the "adb devices" comand shows '0123456789ABCDEF' the "fastboot devices" show "mt6589_phone_720pv2", please need help i use the adb comand and try to format but only receive error messages, this is that i get on the recovery:
https://drive.google.com/file/d/0B_NnURitRMg-ZUZCUC1WaXVIQkdPSGRCaE90NUFUVUZodnBr/view?usp=sharing
https://drive.google.com/file/d/0B_NnURitRMg-RUN5ZjhWbklDUVRNeThFbXRMLUdfUUNoVkFJ/view?usp=sharing
https://drive.google.com/file/d/0B_NnURitRMg-ZGxqYlhMeTBhbVVXbERHWXNoN0xXYlgxTFdV/view?usp=sharing
https://drive.google.com/file/d/0B_NnURitRMg-bVJRODB1N3hXckxNbnhMZFBpajdhekxhaUc4/view?usp=sharing
Click to expand...
Click to collapse
goluisgerardo said:
hi, i work helping my classmates when they stuck on their phones... ok, i'm apologize for my bad english but here is the thing, i now have one Huawei G610-U00 and the phone say "Encryption unsuccessful", i notice that him install the twrp recovery so i try flashing a new recovery using fastboot and the fastboot only say "sending 'recovery'" and nothing else happens(i left all the night, the phone only discharge the battery,), make a search on google and find info related and try them, try using sp flash, try installing a new zip, even try a force-update but when press the vol + and - and the power key, the phone go to recovery, also in the bootloader mode it only say "recovery_status:UPDATED" nothing else, the "adb devices" comand shows '0123456789ABCDEF' the "fastboot devices" show "mt6589_phone_720pv2", please need help i use the adb comand and try to format but only receive error messages, this is that i get on the recovery:
Click to expand...
Click to collapse
I have a similar problem with Huawei Y320-U030, MTK 6572, Android 4.2.2 with many malware infections. Almost all applications keep crashing, Factory Reset from Settings does not work, but I can do it from the recovery and it seems to complete successfully but when the devices boots, all user applications and files are there. I have flashed it with stock ROM and backup ROM from an other working similar phone, the flashing process completed successfully but when the device boots all user files and applications are untouched, even after formatting the whole flash with Sp flashtool, Volcano box and Miracle box! An applications called DU Speed Booster is set as device administrator with a pattern lock which cannot be deactivated. Uninstalling the imo application makes the device reboot and hang on Huawei logo untill the battery is pulled out. I can't install any new apk or root the device even using PC. Music, videos, and photos in the internal memory can be copied with a computer but cannot be deleted. Formatting the internal memory with a PC seems successful but all files on the device are intact. Very interesting case indeed.
Dear everyone,
I have an ASUS MeMoPad 10 (ME103K) here which I vowed to fix. The user wanted to revert to Factory Defaults, lost power or something like this, and ended up with a bricked device.
I can only start it with power button + volume up, into Fastboot. Secure Boot is enabled.
I have Android SDK and minimal FastBoot installed. Have the Google USB Drivers on my desktop.
I tried flashing SuperBoot (ADB), but ADB simply lists "Waiting for Device". No devices can be listed. It does show up in Windows Device Manager: ASUS Android Bootloader Interface.
I have the following files available:
- SuperBoot r5
- Kernel: l-8064-r1_V12.16.1.12-201508071139-foss.tar
- UL-K01E-WW-12.16.1.12-user
- recovery-original-me103k
There is apparently no recovery.img for this device. The boot.img is in the UL-K01E-WW-12.16.1.12-user file
Power = ASUS logo then goes black
Power + Volume up = Fastboot
Power + Volume down = /
Power + Volume up+down = /
Is this the place I should be looking? I'm honestly not sure if I can catch up with the details: android.stackexchange.com/questions/124344/trying-to-flash-a-system-img-i-took-with-dd-failing
Any help would be much appreciated!
- Al
EDIT:
fastboot devices now detects #serialnumber
Alright, fastboot now detects my device. I installed PDANet which didn't do anything, and then downloaded another adbfastboot package which hit it.
I'm able to start writing boot.img, but that's what it stays at. It's an 8MB file, so it shouldn't take half an hour, I suppose?
I'm not getting any error message either, though.
EDIT: It seems that regardless of what commands I send, they stall and don't get executed. ADB doesn't seem to find any devices, only Fastboot does.
EDIT 2: Tried the same on my laptop. Different ports. Nothing goes further than for example "Writing 'boot' - that's it.
Bump (won't bump until tomorrow late)
B0mp
kab0mp
boink
Bwamp
Recover Asus Me103k (k01e)
1) Stock recovery:
View attachment k01e_stock_recovery.zip
3) Run it without flash:
Code:
fastboot boot k01e_stock_recovery.img
3) In recovery select to install UL-K01E-WW-12.16.1.12-user.zip (early placed on microsd)
4) Also can check boot ability:
Extract boot.img from update firmware zip UL-K01E-WW-12.16.1.12-user
And run it from fastboot:
Code:
fastboot boot boot.img
If Android loaded normaly after it, but after reboot you see FASTBOOT MODE, than execute this commands:
Code:
fastboot oem reset-dev_info
fastboot reboot
Asus MeMo pad ME103K/K01E bootloader unlock
sheinbo said:
Hi,
after all these years I remembered my asus memo... Such a fine displsay but ... . I discovered an unofficial rom for another old device ( samsung gt 5830) and so I'd like to ask you whether you know any possibility to "upgrade" the MeMo or any other way to pitch / patch it. Your reply here let me think that you are very attached to asus memo, maybe you are still interested.
Click to expand...
Click to collapse
Same here, running the device on Lollipop is awfully slow, KitKat is somewhat better though but those are the only two official ROM's which can be found and installed.
Tried to unlock the bootloader to try different ROM's but bootloader is locked, despite all info here on XDA, nothing seems to work and the bootloader remains locked. Unlock APK's also give no result.
Running out of options here, any suggestions will be appreciated.