Hi... I'm trying to be as concise and as detailed as possible here:
OK.. I'm trying to flash this ulefone S8 Pro with the STOCK ROM from the ulefone website. I'm using Debian Linux and the SP Flash Tool 5.1804.00 for Linux. I've disabled modemmanager (no conflict there) and I'm able to see from the logs that the device is recognised.
The device itself had it's stock boot.img flashed with a patched version (MagiskManager)and the boot loader has been unlocked - and all was working fine... someone decided to mess about deleting files from /system and the phone refused to boot.
So.... I took the device back and flashed boot, recovery and cache from the stock image using fastboot - all fine... then when it came to system.img - I found out that system-sign.img from the stock ROM wouldn't flash via fastboot - I got an error saying something along the lines of:
Code:
"Invalid sparse file format at header magi error: write_sparse_skip_chunk: ([I]I forget the size[/I]) is not a multiple of the block size 4096"
So, after a bit of googling - I was going to try the SparseConverter tool.. but this seemed to not like the system-sign.img and so I gave up on that idea..
Then I realize I probably need to be using the SP Flash tool - so.. I boot back into Linux and here's what happens.. When the phone is turned on.. I can hold power on + volume up to get the little menu (flashboot, recovery or normal boot) and it ignores this... it goes right to Recovery with "NO COMMAND" - no combination of button pushing does a thing... it will sit at no command, occasionally flashing the screen. When i plug it in.. and don't touch it.. same thing.. straight to no command.. when I turn it on (not plugged in) it does the same thing... when connecting to PC and SP Flash... I hit DOWNLOAD in SP FLASH and then with phone off (battery in) I connect it to the the PC and i get the red bar to 100% and then:
Code:
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:1c.3/0000:05:00.0/usb1/1-2
[email protected]/devices/pci0000:00/0000:00:1c.3/0000:05:00.0/usb1/1-2/1-2:1.0
[email protected]/devices/pci0000:00/0000:00:1c.3/0000:05:00.0/usb1/1-2/1-2:1.1
[email protected]/devices/pci0000:00/0000:00:1c.3/0000:05:00.0/usb1/1-2/1-2:1.1/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 2000
device pid = 2000
com portName is: /dev/ttyACM0
Total wait time = -1522456507.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
connect DA end stage: 2, enable DRAM in 1st DA: 0
COM port is open. Trying to sync with the target...
Failed to Connect DA: S_BROM_DOWNLOAD_DA_FAIL
Disconnect!
BROM Exception! ( ERROR : S_BROM_DOWNLOAD_DA_FAIL (2004)
[H/W] Fail to download DA to baseband chip's internal SRAM!
[HINT]:
1. There's an cable communication problem between FlashTool and BootROM.
2. Target might be shutdown unexpectedly or target lost power supply.
[ACTION]
1. Try again.
2. Proceed H/W checking in download cable and target side com port.
3. Monitor if power-drop occured in target side.)((ConnectDA,../../../flashtool/Conn/Connection.cpp,146))
I've tried all USB ports. Various cables etc etc.. I've tried connecting with phone off and no battery (same thing - same output) - with the battery, without battery and putting battery in after connecting.. taking battery out and putting back in, pushing volume buttons on connecting USB... i've done it all.. same error all the time...
I'm almost to the point where I throw in the towel here... but I thought someone might have some clue or idea what to do now.
Any help appreciated.
Oh yeah.. lastly... dmesg | grep usb gives the following
Code:
[13640.521933] usb 1-2: New USB device found, idVendor=0e8d, idProduct=2000
[13640.521940] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[13640.521945] usb 1-2: Product: MT65xx Preloader
[13640.521949] usb 1-2: Manufacturer: MediaTek
[13643.171638] usb 1-2: USB disconnect, device number 13
[email protected]:~/Downloads$
found out how to unbrick!
OK!! SO... After a LOT of messing about I finally figured this out. What I did was start SP FLASH TOOL and put it in DOWNLOAD mode and then hit the DOWNLOAD button. I then connected the USB lead to my phone but NOT the PC (with the battery in the phone and the phone powered off) THEN I held down the volume up and volume down buttons together and kept holding them... I plugged the USB into the PC and kept holding the volume buttons... lo and behold it worked. I was too scared to let go of the volume buttons, so I just held them until the process had completed.
Hold volume down button when you plug usb lead in and hold until it starts flashing rom!
Also to enter recovery menu, press power + volume up when the command not found message appears.
Checkout guide video https://mega.nz/#F!MqYHCKDS!dqw4xFPs6ZnWI3fH21ZFLA
Related
flashed new rom with sad consequesces. Unable to get tab out of booting recovery kernal image. unable to reconnect to tablet as it show usb not recognized. have updated usb files with naked usb zip and also new fv flash files. still not getting anywhere. I have tried to flash recovery at apx but not working. Is there any hope or have I created a true brick/
Is your PC recognizing the gTab in APX mode (Power and Vol [-])? Does nvflash complete? Post screenshots.
usb not recognized
rajeevvp said:
Is your PC recognizing the gTab in APX mode (Power and Vol [-])? Does nvflash complete? Post screenshots.
Click to expand...
Click to collapse
usb not recognized, tablet goes into apx but the computer does not recognize it. I have tried several different driver combinations and it still cant' see it. I think that I somehow screwed up the driver in the tablet. but can't even get it to connect to the computer. I tried a linux connection and it didn't recognize it either. I was using a live cd and tried to get the startup to locate a driver, no such luck. Is there a way I can completly format the tablet??? I can't get it past the boot loader error. thanks for your input up to now. hope someone has answers for me. I may have created a very nice parts machine.
mfmmetz said:
I think that I somehow screwed up the driver in the tablet.
Click to expand...
Click to collapse
You can't screw-up the APX-mode USB driver on the gTablet--it's built into the system firmware --ie. it's hard-coded. A HW error is a more likely culprit (if, indeed, the PC doesn't see the tablet in APX mode) . Disassemble the gTab and carefully inspect the USB port and surroundings for stray bits of metal, or solder, or cut traces, etc.
I tried a linux connection and it didn't recognize it either. I was using a live cd and tried to get the startup to locate a driver, no such luck.
Click to expand...
Click to collapse
Since you can use Linux, do this:
1. Boot into Linux.
2. Put the tablet into APX mode (the screen will turn off).
3. Plug the cable from the tablet into the PC.
4. Run these command (only the stuff in bold) and post their output (or a screenshot):
Code:
$ [B]dmesg | tail -n20[/B]
...
[ 7872.447589] usb 1-2.2: new full-speed USB device number 8 using ohci_hcd
[ 7872.552503] usb 1-2.2: New USB device found, idVendor=[B]0955[/B], idProduct=[B]7820[/B]
[ 7872.552514] usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 7872.552521] usb 1-2.2: Product: APX
[ 7872.552528] usb 1-2.2: Manufacturer: NVIDIA Corp.
$ [B]lsusb
[/B]...
Bus 001 Device 008: ID [B]0955:7820 NVidia Corp.[/B]
...
$
I can't get it past the boot loader error.
Click to expand...
Click to collapse
Take a snap and post it.
Hello to all,
Everything went wrong on flashing with SP Flash tool. The Preloader of Scattered file was checked and all others.
The problem is strange for me and I see that there are other with the same issue without an answer.
Fist of all I did everything described in forums. The driver of MT Preloader Vcom port is installed correctly. In Device Manager LTP com port is detected and as it is normal it disconnects in 2-5 seconds. If I change the USB port on PC it changes the COM port which is the previous detected.
The issue is that my latest SP Flash Tool 5.14 or even 3.13 older one, can't establish permanent connection with the COM port of the MTK 6589. I tested with different cables and different OS (XP and Windows 7 32 bit) on different computers with first pressing Download button of SP Flash Tool and then plugging the cable. If I don't press Volume Down button of my Huawei Ascend G610s it can't be dected of SP Flash. After pressing Volume Down the enters into Meta mode BUT .... SP Flash Tool report:
BROM ERROR : S_BROM_DOWNLOAD_DA_FAIL (2004)
[H/W] Fail to download DA to baseband chip's internal SRAM
[HINT]: 1. There's an cable communication problem between FlashTool and BootROM.
2. Target might be shutdown unexpectedly or target lost power supply.
[ACTION]
1. Try again.
2. Proceed H/W checking in download cable and target side com port.
3. Monitor if power-drop occured in target side.
At some reason COM port is constantly disconnecting and connecting without establishing permanent connection with SP Flash Tool. The red bar pops up and shows 100% done.
Any idea for this issue? You will help a lot of people which don't have the answer what to do.
Best Regards
niki_help said:
Hello to all,
Everything went wrong on flashing with SP Flash tool. The Preloader of Scattered file was checked and all others.
The problem is strange for me and I see that there are other with the same issue without an answer.
Fist of all I did everything described in forums. The driver of MT Preloader Vcom port is installed correctly. In Device Manager LTP com port is detected and as it is normal it disconnects in 2-5 seconds. If I change the USB port on PC it changes the COM port which is the previous detected.
The issue is that my latest SP Flash Tool 5.14 or even 3.13 older one, can't establish permanent connection with the COM port of the MTK 6589. I tested with different cables and different OS (XP and Windows 7 32 bit) on different computers with first pressing Download button of SP Flash Tool and then plugging the cable. If I don't press Volume Down button of my Huawei Ascend G610s it can't be dected of SP Flash. After pressing Volume Down the enters into Meta mode BUT .... SP Flash Tool report:
BROM ERROR : S_BROM_DOWNLOAD_DA_FAIL (2004)
[H/W] Fail to download DA to baseband chip's internal SRAM
[HINT]: 1. There's an cable communication problem between FlashTool and BootROM.
2. Target might be shutdown unexpectedly or target lost power supply.
[ACTION]
1. Try again.
2. Proceed H/W checking in download cable and target side com port.
3. Monitor if power-drop occured in target side.
At some reason COM port is constantly disconnecting and connecting without establishing permanent connection with SP Flash Tool. The red bar pops up and shows 100% done.
Any idea for this issue? You will help a lot of people which don't have the answer what to do.
Best Regards
Click to expand...
Click to collapse
I have the same problem please help
Hi ...what is the phone model?
In my case the issue was solved with a hardware "kick" with button combination because at some reason the MTK preloader was put the phone in nonsense turning on and off the without being able to establish permanent connection. I tried all the MTK drivers but the issue was some kind of bug which actually was constant switching off. My model phone was Huawei G610s. What I did was to hold Power, +, - button together for about 5 seconds then release power still holding + and - button, and after 4-5 seconds release + button while holding - button for 4 seconds. This kicked out from the constant disconnection and SP flash tool was able to finalize the flash. Without this every time the error was as your have described.
Hi,
Yesterday a friend of mine gave me a LG L9 (P760). Some months (or maybe years) ago he changed this phone for a new one and stored it without battery. 2 days ago he tried to turn it on but no life, same result when he connected it to the wall charger.
I tried connecting it without battery to the PC (on Ubuntu, if I use windows 10 the device keeps disconnecting and connecting and I can't install the OMAP4430 driver because win says they are already updated (it isn't so, uses the driver for "usb enumeration failure")) and is recognized, via lsusb, as "ID 0451:d00f Texas Instruments, Inc.".
If i launch dmesg it gives (more than one time):
Code:
[ 973.692035] usb 1-6: new high-speed USB device number 26 using ehci-pci
[ 973.825080] usb 1-6: unable to get BOS descriptor
[ 973.825953] usb 1-6: New USB device found, idVendor=0451, idProduct=d00f
[ 973.825958] usb 1-6: New USB device strings: Mfr=33, Product=37, SerialNumber=0
[ 973.825961] usb 1-6: Product: OMAP4430
[ 973.825964] usb 1-6: Manufacturer: Texas Instruments
[ 976.826505] usb 1-6: USB disconnect, device number 26
.
I tried using the method suggested here: http://vincenzoml.blogspot.it/2013/08/lg-l9-unbrick-script.html. I can get into fastboot but then it says
Code:
sending 'u-boot' (1024 KB)...
OKAY [ 0.675s]
writing 'u-boot'...
FAILED (remote: partition does not exist)
What can I do? Is there a possibility to make this phone work again?
Thanks in advance to all!
Under Win7 i had both the LG drivers and the Google SDK drivers installed. Under Win10 also, but the Google drivers can't be found in device manager. Anyway, in contrary to Win7, the LG drivers and LG software xan niw detect my phone and work, with the exception of Fastboot. Under Win7 and with a custom rom, LG drivers were only good to provide a virtual com port in D/L mode.
And the morale of this tale: These outdated OMAP drivers were never of any use to me.
That's the normal behavior of the OMAP Chip, the only thing you've to do is to re-flash putting back the battery and then, connecting your device over USB while holding Vol+.
Ah, no battery. While it's sometimes recommended to remove the battery during unbricking, i think it's simply impossible to do this or anything w/o battery, despite the 0,5A power via usb.
After a failed attempt to invoke D/L mode, you can remove the battery shortly, or switch the phone on and (force) off for an extra time, to try again. Otherwise it's more likely that D/L mode will again fail.
lecorbusier said:
Ah, no battery. While it's sometimes recommended to remove the battery during unbricking, i think it's simply impossible to do this or anything w/o battery, despite the 0,5A power via usb.
After a failed attempt to invoke D/L mode, you can remove the battery shortly, or switch the phone on and (force) off for an extra time, to try again. Otherwise it's more likely that D/L mode will again fail.
Click to expand...
Click to collapse
I have the battery! The problem is that fastboot can't find the partitions
If the first hurdle has been passed, and there is actual access to the phone(i'm not sure whether this is the case here), the partitions really got deleted or damaged. Unbricking with a stock rom is the only option. Or professional service (better a new phone) if that ain't possible.
Can't you try this, please? http://forum.xda-developers.com/showthread.php?t=2546571 I've found it on the forum just a couple of minutes ago, I hope it helps .
Good luck!
I have the same problem.
If x-loader and u-boot partitions does not exist, we do not have the bootloader, and you can't do anything to make the phone work aside from JTAG.
I tried to boot recovery from computer without flashing using 'boot' command (fastboot boot recovery.img) and this still doesn't work because I don't have bootloader.
Method from post above does not work for me.
Hello everyone,
I have a situation that has around 4 months now, and I can't fix it even after reading every piece of information I could grab on this forum and google.
I'm usually the guy that prefers to play safe and not flash any kind of Android device to avoid this kind of headaches, but out of the blue (i believe it was a power grid failure), my box wouldn't boot past the logo. It's a Mini M8S II (S905X). I contacted the support at Gearbest (where I bought it) and they said it could not be fixed and refunded half the money. So no luck there.
After 4 months of research and testing and failing to unbrick this box, here are the conclusions I took:
- When I try to flash any firmware with USB Burning Tool it recognizes easily, but always stops at 7% (U-Boot/Send Command Error or something like that). Tried 2 cables, 2,0 and 3.0 USB ports, and different versions of USB Burning Tool (had time to try many combinations)
- When I try to flash any firmware with SD Card, it shows the cute and lovely android but ends up with a red cross on the end. (tried all kinds of combinations with the erasing flash option, all types of firmwares I could find for this box, etc)
- When I try to access the recovery without SD Card using the toothpick, nothing happens.
- I tried the "sd_MINIM8SII_rv102" extracted to the sd card, nothing happened.
- Tryed many firmwares with USB Burning Tool, rv109, rv112, and others for S905X...... nothing goes in this box =/
After some deeper research, I tried extracting the "update.zip" from "sd_MINIM8SII_rv102" to sd card and replacing the recovery.img with the one from TWRP for S905X v3.0.2. It boots successfully to TWRP asking if I want to keep the system read-only. (at this point I saw the light at the end of the tunnel) Tried right away to flash a firmware from it, failing with messages saying the are no mounting points for /data and no /system partition and what not. Then I noticed the internal memory says 0Mb, in the recovery. Is that the problem?
I've also seen stuff like dropping a u-boot.bin (tried botfap's u-boot.bin.sd.bin) and stopping u-boot to access u-boot shell. From there you can flash the recovery.img and dtb.img and stuff like that. Can't find much information on that and didn't had much luck with it either.
What am I missing? what can I do? I'm up for anything other than using this Box as a tall beer coaster.
How about the short circuit method? I'm lost.... I just want it working again =(
Here goes some images with the error from USB Burning Tool:
imgur.com/a/GFhJu
imgur.com/a/5LIn5
Have you tried starting usb tool flash and then plugging in the box after flashing already started in software? That worked for me. Found the fix on another forum.
Sent from my SM-G900V using Tapatalk
Koognod said:
Have you tried starting usb tool flash and then plugging in the box after flashing already started in software? That worked for me. Found the fix on another forum.
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
If you mean pressing start on usb burning tool and then plug the USB cable. Then yes, tryed it several times with many diferent ROM's =( always the same output.
It was one of the many tricks/tips i've found. But still no difference..... thank you tho!
when u get error message at usb burning tool after press start, just continue with reconecting usb cable with and w/o press reset button..
actually last hour i get some trouble like you, error in usb burning tool because device disconected automaticly after 10 second maybe, but i just try recconect the usb cable, n viola, usb burning working n install my rom..
i think if your pc still recognizing ur tv box via usb cable, u still can doing flash with that usb burning..
clasie said:
when u get error message at usb burning tool after press start, just continue with reconecting usb cable with and w/o press reset button..
actually last hour i get some trouble like you, error in usb burning tool because device disconected automaticly after 10 second maybe, but i just try recconect the usb cable, n viola, usb burning working n install my rom..
i think if your pc still recognizing ur tv box via usb cable, u still can doing flash with that usb burning..
Click to expand...
Click to collapse
Thats what I thought, if the USB Burning Tool recognizes there is hope!! lol
but the truth is.... I keep hearing the "Keep trying" on several forum topics...... I try reconnecting and refreshing several times..... I tryed with several USB Burning Tool versions, I tryed with several combinations of installing drivers with and without the reset button when connecting...... several things....... the computer sometimes recognizes as "GX-CHIP" and sometimes as "Worldcup Device"........ would there be the problem? I keep hiting the 7% wall with the "UBOOT/Disk initialize/Send command/Error result" message..... very frustrating! =/
Here goes more information from the error log:
[20:04:54 876][HUB1-2][Inf]--Device is connected
[20:04:54 876][HUB1-2][Inf]--Close device handle 0x00000660
[20:04:54 938][HUB1-2][Inf]--Open device handle \\?\usb#vid_1b8e&pid_c003#5&1003806&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed} 0x000008c0
[20:05:00 001][HUB1-2][Inf]--0-7-0-16
[20:05:00 002][HUB1-2][Inf]--CheckFileRunState succeed
[20:05:00 002][HUB1-2][Inf]-- low_power
[20:05:00 007][HUB1-2][Inf]--Send command success
[20:05:00 010][HUB1-2][Inf]--Read command status success
[20:05:00 010][HUB1-2][Inf]-------------Download meson1.dtb-----------
[20:05:00 012][HUB1-2][Inf]--0-7-0-16
[20:05:00 012][HUB1-2][Inf]-- download mem dtb normal 79872
[20:05:00 012][HUB1-2][Inf]--Send download command success
[20:05:00 025][HUB1-2][Inf]--Read command status success
[20:05:00 037][HUB1-2][Inf]--Transfer complete
[20:05:00 037][HUB1-2][Inf]--Send download get_status command succeed
[20:05:00 041][HUB1-2][Inf]--get_status success
[20:05:00 542][HUB1-2][Inf]-------------ERASE FLASH-----------
[20:05:00 542][HUB1-2][Inf]--disk_initial 1
[20:05:00 542][HUB1-2][Inf]--Send command success
[20:05:01 671][HUB1-2][Err]--failed:[20:05:01 671][HUB1-2][Err]--Check command return failed
[20:05:01 688][HUB1-2][Err]--[0x30201004]UBOOT/Disk initialize/Send command/Error result
have you ever managed to resolve this issue?
I'm trying to clone the phone disk by using https://github.com/bkerler/mtkclient.
It's working flawlessly using the command mtk rf, but I terminate the program using Ctrl+C because I need to clean my pc drive first.
I don't think this would cause problem since it's only read operation.
When I try to reconnect using mtk again, It's shows error on DA_send, then handshake failed and finally, the phone shows no life, since mtk doesn't even detect it again.
I'm running dmesg to check if my linux desktop detect the usb device and it shows.
Code:
device descriptor read/64.
Device not responding to setup address.
device not accepting address X, error -71
unable to enumerate USB device
Is the phone dead?
Is it on BROM mode or something else?
I've read on some forum to press all button for 15s it did not work. and prying the battery is above my ability right now.
Any helps is appreciated, thanks!
I have usually have good response from LONG press power button. Sometimes it takes 30Secs or more to reset from brom. (not same device though)