Related
Hello,
I have probably bricked my Huawei Vision by rewriting boot image.
However, I can connect* it to PC and it sees my phone as "Huawei Handset" (same with Windows and Linux). But Windows misses its drivers (non-bricked phone worked); Linux seems to work. No OS can connect to it using default (downloaded) ADB, nor Fastboot, nor SoftwareUpdateTool.
Its PCI ID is 12d1:c002.
How could I reflash it? I would prefer the ways without disassembling the phone.
Thanks
----How to boot the phone, so you can connect it to PC:
1. turn off my phone completely (vol up + power for 10 seconds - release power for a seconds and repeat it once again)
2. prepare USB cable, so you can connect it in few seconds
3. hold vol down + power and after ~1s, connect USB cable (still hold vol down)
4. when Huawei logo appears, release both buttons - your phone is connected now
petoxxx said:
Hello,
I have probably bricked my Huawei Vision by rewriting boot image.
However, I can connect* it to PC and it sees my phone as "Huawei Handset" (same with Windows and Linux). But Windows misses its drivers (non-bricked phone worked); Linux seems to work. No OS can connect to it using default (downloaded) ADB, nor Fastboot, nor SoftwareUpdateTool.
Its PCI ID is 12d1:c002.
How could I reflash it? I would prefer the ways without disassembling the phone.
Thanks
----How to boot the phone, so you can connect it to PC:
1. turn off my phone completely (vol up + power for 10 seconds - release power for a seconds and repeat it once again)
2. prepare USB cable, so you can connect it in few seconds
3. hold vol down + power and after ~1s, connect USB cable (still hold vol down)
4. when Huawei logo appears, release both buttons - your phone is connected now
Click to expand...
Click to collapse
mine is not working i think mine is bricked completly
bricked my mobile...Help!!!!
I had installed the latest rooted russian firmware and unknowingly installed the ICS..Now my device stuck at boot and while connecting with sutlr error(cannot identify device) occurs..What to do:crying:???
sivakarthick said:
I had installed the latest rooted russian firmware and unknowingly installed the ICS..Now my device stuck at boot and while connecting with sutlr error(cannot identify device) occurs..What to do:crying:???
Click to expand...
Click to collapse
The thread called 'Problem with huawei vision' still seems to be active. You may want to try asking your question over there.
Huawei (u8850) unbricked
I just wanted to relate my experiences in de-bricking this U8850 phone.
I installed 'Apps_2.6.35.7-perf+root+CWM_recovery 5.0.2.8' (firmware.nb0) using SUT to get CWM, and then installed Danile's 4.1.2
Good as far as it goes, but i could not for the life of me reproduce his kernel (my kernels are always unreliable), so after many days of playing, i decided to take the phone back to stock to see if i could reproduce the huawei stock kernel as a base to work on.
The problem was, how do you revert to stock; the phone was no longer recognised by SUT?
So I took a stock .nbo file and extracted the content (some java extractor found with google) in the hope that I could create a CWM flashable zip of the stock firmware.. a bit of research later, and i thought i had got the gist, put boot.img and system.img into a zip with a modified script file, and voila... a bricked phone.
At this point, i had CWM, but if the phone booted, it showed a flash of blue screen (I didn't know these ran windows ), and back to huawei logo. Also I think i had to dismantle to disconnect battery to run CWM, as it's not available just on the volume-up-power restart.
So then I did more research, and came across QPST, Qualcom's tools. It seemed this should know something about the files i had extracted. I could not correlate everything in the extracted fileset with what QPST seemed to expect, but the first challenge was to get QPST and the phone talking. using various drivers, QPST would sometimes see it, sometimes not, but nothing good seemed to be coming from it. I returned to trying to get SUT to work on my brick; again, with some drivers it would connect, but a flash always resulted in Error 4000 - DEVICE_NOT_CONFIGURED.
Then I read somewhere that someone had found a driver change made SUT work, so i investigated drivers more.
What I found was that if i ran up CWM, I got two Huawei devices in XP for which I could not find drivers.
The devices showed up as VID_12D1&PID_1022&MI_00 and VID_12D1&PID_1022&MI_01.
I took the Huawei USB drivers folder, and copied the qcser.inf then changed entries under [QcomSerialPort] to match my VID/PID values.
(the two that had matching MI_ values).
On driver update, I had a serial port, plus something I'd not seen before - a USB storage device which contained the phone's partitions!!!
This certainly seemed promising... so into SUT again, same error 4000...
So the I tried QPST; and yes, it could see the phone. Scared to do anything to brick it further, I thought, ok, try some memory diagnostics.
On running the 'Memory Debug' tool, as soon as I tried to get a list, QPST said 'this phones in diagnostic mode, it must be in download mode to do memory diagnostics', but even better 'Do you want to set it into download mode now?'!!!!!
Yeah! click the button, and I see a screen I've only seen once before (and i don't know why last time), black, with a line added every few seconds... which from all my reading I know is a good sign.
OK, then I closed all QPST apps, and ran SUT.
This time, the firmware flashed no problem. Was a bit worried as boot time is long (but it was effectively 'first ever' boot for the phone).
I hope this helps someone else with this or another Qualcom based phone.
Basic lesson is:
If you see Error 4000, it may be that the phone is in diagnostic mode rather than download mode.
If you don't have drivers, or don't have the right drivers, check you VID and PID, and try putting them into the .inf file
QPST may have a simple use after all... to force a phone into download mode when SUT fails.
how to turn off huawei u8850 completely
hey,could you please help me.i am stuck on huawei logo.how can i turn off the phone completely.i cant remove the battery obviously.the above trick isnot working.plz.help me
bikeshrt said:
hey,could you please help me.i am stuck on huawei logo.how can i turn off the phone completely.i cant remove the battery obviously.the above trick isnot working.plz.help me
Click to expand...
Click to collapse
it's actually not difficult to remove the battery...
but i read somewhere the 'volume-up + power for five seconds' will hard restart, but re-press power immediately will then turn it off (not tested myself; the back of mine is already off at the moment.)
Anyone here interested in developing a 3.x kernel? seems other phones with msm8255 have successfully got one...
u8850 power off
btsimonh said:
but i read somewhere the 'volume-up + power for five seconds' will hard restart, but re-press power immediately will then turn it off (not tested myself; the back of mine is already off at the moment.)
Click to expand...
Click to collapse
now i have tried it, and no success.
However, what i have found to work - if your non-boot is actually booting the kernel, but failing to initialise the phone, then you can still use adb with it... I ran adb shell, and then used 'poweroff' to power off my phone, which then meant i could boot into CWM recovery....
i HAVE THE SAME PROBLEME? PLEASE CAN U HELP ME TO SOLVE IT BY GIVING ME DETAILS.
it is working, thank you bro
btsimonh said:
I just wanted to relate my experiences in de-bricking this U8850 phone.
I installed 'Apps_2.6.35.7-perf+root+CWM_recovery 5.0.2.8' (firmware.nb0) using SUT to get CWM, and then installed Danile's 4.1.2
Good as far as it goes, but i could not for the life of me reproduce his kernel (my kernels are always unreliable), so after many days of playing, i decided to take the phone back to stock to see if i could reproduce the huawei stock kernel as a base to work on.
The problem was, how do you revert to stock; the phone was no longer recognised by SUT?
So I took a stock .nbo file and extracted the content (some java extractor found with google) in the hope that I could create a CWM flashable zip of the stock firmware.. a bit of research later, and i thought i had got the gist, put boot.img and system.img into a zip with a modified script file, and voila... a bricked phone.
At this point, i had CWM, but if the phone booted, it showed a flash of blue screen (I didn't know these ran windows ), and back to huawei logo. Also I think i had to dismantle to disconnect battery to run CWM, as it's not available just on the volume-up-power restart.
So then I did more research, and came across QPST, Qualcom's tools. It seemed this should know something about the files i had extracted. I could not correlate everything in the extracted fileset with what QPST seemed to expect, but the first challenge was to get QPST and the phone talking. using various drivers, QPST would sometimes see it, sometimes not, but nothing good seemed to be coming from it. I returned to trying to get SUT to work on my brick; again, with some drivers it would connect, but a flash always resulted in Error 4000 - DEVICE_NOT_CONFIGURED.
Then I read somewhere that someone had found a driver change made SUT work, so i investigated drivers more.
What I found was that if i ran up CWM, I got two Huawei devices in XP for which I could not find drivers.
The devices showed up as VID_12D1&PID_1022&MI_00 and VID_12D1&PID_1022&MI_01.
I took the Huawei USB drivers folder, and copied the qcser.inf then changed entries under [QcomSerialPort] to match my VID/PID values.
(the two that had matching MI_ values).
On driver update, I had a serial port, plus something I'd not seen before - a USB storage device which contained the phone's partitions!!!
This certainly seemed promising... so into SUT again, same error 4000...
So the I tried QPST; and yes, it could see the phone. Scared to do anything to brick it further, I thought, ok, try some memory diagnostics.
On running the 'Memory Debug' tool, as soon as I tried to get a list, QPST said 'this phones in diagnostic mode, it must be in download mode to do memory diagnostics', but even better 'Do you want to set it into download mode now?'!!!!!
Yeah! click the button, and I see a screen I've only seen once before (and i don't know why last time), black, with a line added every few seconds... which from all my reading I know is a good sign.
OK, then I closed all QPST apps, and ran SUT.
This time, the firmware flashed no problem. Was a bit worried as boot time is long (but it was effectively 'first ever' boot for the phone).
I hope this helps someone else with this or another Qualcom based phone.
Basic lesson is:
If you see Error 4000, it may be that the phone is in diagnostic mode rather than download mode.
If you don't have drivers, or don't have the right drivers, check you VID and PID, and try putting them into the .inf file
QPST may have a simple use after all... to force a phone into download mode when SUT fails.
Click to expand...
Click to collapse
it is working thanks bro
Stock rom download plz.
btsimonh said:
I just wanted to relate my experiences in de-bricking this U8850 phone.
I installed 'Apps_2.6.35.7-perf+root+CWM_recovery 5.0.2.8' (firmware.nb0) using SUT to get CWM, and then installed Danile's 4.1.2
Good as far as it goes, but i could not for the life of me reproduce his kernel (my kernels are always unreliable), so after many days of playing, i decided to take the phone back to stock to see if i could reproduce the huawei stock kernel as a base to work on.
The problem was, how do you revert to stock; the phone was no longer recognised by SUT?
So I took a stock .nbo file and extracted the content (some java extractor found with google) in the hope that I could create a CWM flashable zip of the stock firmware.. a bit of research later, and i thought i had got the gist, put boot.img and system.img into a zip with a modified script file, and voila... a bricked phone.
At this point, i had CWM, but if the phone booted, it showed a flash of blue screen (I didn't know these ran windows ), and back to huawei logo. Also I think i had to dismantle to disconnect battery to run CWM, as it's not available just on the volume-up-power restart.
So then I did more research, and came across QPST, Qualcom's tools. It seemed this should know something about the files i had extracted. I could not correlate everything in the extracted fileset with what QPST seemed to expect, but the first challenge was to get QPST and the phone talking. using various drivers, QPST would sometimes see it, sometimes not, but nothing good seemed to be coming from it. I returned to trying to get SUT to work on my brick; again, with some drivers it would connect, but a flash always resulted in Error 4000 - DEVICE_NOT_CONFIGURED.
Then I read somewhere that someone had found a driver change made SUT work, so i investigated drivers more.
What I found was that if i ran up CWM, I got two Huawei devices in XP for which I could not find drivers.
The devices showed up as VID_12D1&PID_1022&MI_00 and VID_12D1&PID_1022&MI_01.
I took the Huawei USB drivers folder, and copied the qcser.inf then changed entries under [QcomSerialPort] to match my VID/PID values.
(the two that had matching MI_ values).
On driver update, I had a serial port, plus something I'd not seen before - a USB storage device which contained the phone's partitions!!!
This certainly seemed promising... so into SUT again, same error 4000...
So the I tried QPST; and yes, it could see the phone. Scared to do anything to brick it further, I thought, ok, try some memory diagnostics.
On running the 'Memory Debug' tool, as soon as I tried to get a list, QPST said 'this phones in diagnostic mode, it must be in download mode to do memory diagnostics', but even better 'Do you want to set it into download mode now?'!!!!!
Yeah! click the button, and I see a screen I've only seen once before (and i don't know why last time), black, with a line added every few seconds... which from all my reading I know is a good sign.
OK, then I closed all QPST apps, and ran SUT.
This time, the firmware flashed no problem. Was a bit worried as boot time is long (but it was effectively 'first ever' boot for the phone).
I hope this helps someone else with this or another Qualcom based phone.
Basic lesson is:
If you see Error 4000, it may be that the phone is in diagnostic mode rather than download mode.
If you don't have drivers, or don't have the right drivers, check you VID and PID, and try putting them into the .inf file
QPST may have a simple use after all... to force a phone into download mode when SUT fails.
Click to expand...
Click to collapse
HOLY GOD! F**K ME!!! I finally did it! THANKS A LOT, BRO! YOU'RE AWESOME!!!
My LG D605 does not boot and I have a black screen. Before brick i go via ADB to recovery on official KK. Mobile is dead USB dont work
I have the same problem help!!!
LoToR122 said:
My LG D605 does not boot and I have a black screen. Before brick i go via ADB to recovery on official KK. Mobile is dead USB dont work
Click to expand...
Click to collapse
No responses to Emergency mode flashing by KDZ?
Try at least with HARD RESET... Hold Power Key + Volumen Down key + Home key
When LG logo appears, release all the keys! Good luck!
LoToR122 said:
My LG D605 does not boot and I have a black screen. Before brick i go via ADB to recovery on official KK. Mobile is dead USB dont work
Click to expand...
Click to collapse
Give me a pm when you have 1 hour I might have an idea to save you.
christi9503 said:
Give me a pm when you have 1 hour I might have an idea to save you.
Click to expand...
Click to collapse
Can you help me? pls
kikobuendia said:
I have the same problem help!!!
Click to expand...
Click to collapse
First, there is no such thing as hardbrick (not anymore, most modern phones cant be hardbriked )
Be sure, u have all the drives and whatnots installed in the copmuter !
from: http://forum.xda-developers.com/showthread.php?t=2730501
[Q] How to install a .kdz?
[A] (Tutorial thanks to @[W]ar[H]ead, confirmed working by TaZRAge)
#1) First to get into download mode:
1. Remove battery
2. Put usb to computer and phone (w/o battery)
3. Hold "Vol up" button
4. Put battery back
You will get into download mode (aka emergency mode).
#2) Unpack kdz flasher, and install msxml.msi.
#3) Run KDZ_FW_UPD.exe set "type" to 3GQCT and "phonemode" to DIAG.
#4) Choose the .kdz file to flash. Download link is under the "Downloads"
#5) Click "Launch software update" and wait. Phone must be connected in download mode(!). KDZ installer might get stuck but DO NOT disconnect it. (Unless it stays that way for a hour as a example)
NOTE: .kdz is a .kdz, you cannot extract it. If you get a .zip from the LG .kdz site you did something wrong.
Cisf said:
First, there is no such thing as hardbrick (not anymore, most modern phones cant be hardbriked )
Be sure, u have all the drives and whatnots installed in the copmuter !
from: http://forum.xda-developers.com/showthread.php?t=2730501
[Q] How to install a .kdz?
[A] (Tutorial thanks to @[W]ar[H]ead, confirmed working by TaZRAge)
#1) First to get into download mode:
1. Remove battery
2. Put usb to computer and phone (w/o battery)
3. Hold "Vol up" button
4. Put battery back
You will get into download mode (aka emergency mode).
#2) Unpack kdz flasher, and install msxml.msi.
#3) Run KDZ_FW_UPD.exe set "type" to 3GQCT and "phonemode" to DIAG.
#4) Choose the .kdz file to flash. Download link is under the "Downloads"
#5) Click "Launch software update" and wait. Phone must be connected in download mode(!). KDZ installer might get stuck but DO NOT disconnect it. (Unless it stays that way for a hour as a example)
NOTE: .kdz is a .kdz, you cannot extract it. If you get a .zip from the LG .kdz site you did something wrong.
Click to expand...
Click to collapse
You don't know what you are saying. You can HARDBRICK ANY modern device. By definition hardbrick means phone won't turn on won't respond and in some cases recognized as usb when connected to pc as usb bulk or qcom usb. etc. You damage the second bootloader and tell me what happens. You will see what you get.
christi9503 said:
You don't know what you are saying. You can HARDBRICK ANY modern device. By definition hardbrick means phone won't turn on won't respond and in some cases recognized as usb when connected to pc as usb bulk or qcom usb. etc. You damage the second bootloader and tell me what happens. You will see what you get.
Click to expand...
Click to collapse
first this is offtopic. Second, u are wrong ! Unless the phone is pshisicaly damaged (misfuctioning components or damaged), u cant hardbrick the phone with uploading different soft. on it (unless u change voltages and overclok, if that is possible on the device). Ofecourse they are exceptions, but all major modern manufactors, make hardbrick proof devices. Also, how exactly would u modify the emergency mode, and more important even if you could, why wold u do it !?
More on to the topic, none of the operations of rooting, bootloader installing, kdz install or CMx install , gets near the emergency mode. It remains intact.
Just retry all normal steps for installing kdz or recovery again, check the cables, all drivers on pc, and is best to have a charged phone battery.
EDIT: @kikobuendia
i found this post, same operations as mentioned in first reply, but more detailed:
http://forum.xda-developers.com/opt...optimus-l9-ii-lg-d605-unroot-unbrick-t2964693
Cisf said:
first this is offtopic. Second, u are wrong ! Unless the phone is pshisicaly damaged (misfuctioning components or damaged), u cant hardbrick the phone with uploading different soft. on it (unless u change voltages and overclok, if that is possible on the device). Ofecourse they are exceptions, but all major modern manufactors, make hardbrick proof devices. Also, how exactly would u modify the emergency mode, and more important even if you could, why wold u do it !?
More on to the topic, none of the operations of rooting, bootloader installing, kdz install or CMx install , gets near the emergency mode. It remains intact.
Just retry all normal steps for installing kdz or recovery again, check the cables, all drivers on pc, and is best to have a charged phone battery.
EDIT: @kikobuendia
i found this post, same operations as mentioned in first reply, but more detailed:
http://forum.xda-developers.com/opt...optimus-l9-ii-lg-d605-unroot-unbrick-t2964693
Click to expand...
Click to collapse
I am not gonna reply again but I am just saying you have no idea. Do not talk unless you are sure you can hardbrick any device with just root and just writing on second bootloader partition. Read about it if you don't know. Do not argue about it.
I can't get into download mode
kikobuendia said:
I can't get into download mode
Click to expand...
Click to collapse
Then that's a hard brick pretty much. Pull the battery out and connect the phone to PC. Tell me if it gets recognized.
EDIT: OFC wait like 6 seconds then put it back and after that connect to USB.
When i connect it pc makes a sound
kikobuendia said:
When i connect it pc makes a sound
Click to expand...
Click to collapse
I don't care if it makes a sound or not it's like it gets recognized? Look into device manager.
christi9503 said:
I don't care if it makes a sound or not it's like it gets recognized? Look into device manager.
Click to expand...
Click to collapse
Yes but flashtool doesnt recognize it
kikobuendia said:
Yes but flashtool doesnt recognize it
Click to expand...
Click to collapse
If you want to get this fixed just listen to me. It won't work like this tell me the answers to my questions and we might solve your problem. What is your device recognized as. Make me a screenshot of device manager if you can't explain.
neutrondev said:
Then that's a hard brick pretty much. Pull the battery out and connect the phone to PC. Tell me if it gets recognized.
EDIT: OFC wait like 6 seconds then put it back and after that connect to USB.
Click to expand...
Click to collapse
I have the same probalem, cant get to download mode, when i connect to pc it recognise it in hs usb qdloader 9008, any solutions to fix it. I flashed wrong .tot file.
did you managed to unbricked it?
I have the same probalem, cant get to download mode, when i connect to pc it recognise it in hs usb qdloader 9008, any solutions to fix it. I flashed wrong .tot file.
Click to expand...
Click to collapse
No, no luck yet. Seems to be impossible.
I connect to this post cuz my d605 is also facing a similiar issue, no system, no recovery, no adb, download mode worked only twice, for the rest, only emergency mode works, phone cannot even charge.
Phone is recognized from pc, I uninstalled modem drivers but stays in Emergency only few seconds then it shuts down (not sure if its the battery, since it doesn't charge as well). It shuts down actually at the moment that LG mobile support tool seems to recognize it.
It worked couple of times, phone was keeping staying in emergency mode for the beginning of the procedure but at the moment it need to put the kdz into the phone, the phone die.
The two times download mode worked, same, just shutting down immediately. This with LG support tool or LG flashtool2014.
KDZ_FW_UPD worked the first time after install and then doesn't run anymore, on two different Win10 machines.
I have no idea how to come out of this nightmare, just want to flash it :/
Ag0n1a said:
I connect to this post cuz my d605 is also facing a similiar issue, no system, no recovery, no adb, download mode worked only twice, for the rest, only emergency mode works, phone cannot even charge.
Phone is recognized from pc, I uninstalled modem drivers but stays in Emergency only few seconds then it shuts down (not sure if its the battery, since it doesn't charge as well). It shuts down actually at the moment that LG mobile support tool seems to recognize it.
It worked couple of times, phone was keeping staying in emergency mode for the beginning of the procedure but at the moment it need to put the kdz into the phone, the phone die.
The two times download mode worked, same, just shutting down immediately. This with LG support tool or LG flashtool2014.
KDZ_FW_UPD worked the first time after install and then doesn't run anymore, on two different Win10 machines.
I have no idea how to come out of this nightmare, just want to flash it :/
Click to expand...
Click to collapse
well, sorry for not replying earlier. My phone was on guarantee for about 2 months after I wrote the post. I just send it to LG Hellas via the e-shop I bought it from and in about 2-3 weeks, I had my D605 back like it was brand new. I searched a lot about my D605 hard bricked and I found that it is not fixable. My phone could not go into download mode though, as yours. Hope I helped you even a lil bit. Sorry for my bad English.
This might be a long situp to write this, but i've experienced that a lot of the excelvan users do not really know, where to get support for their device. I've bought this device because the price was low. And so is the quality. It is assembled with a JTY mt10 smarphone mainboard, connected to a 10,1'' touch display.
I've bricked the device and getting help to retrieve it back to life was a pain. No support from excelvan, so I've experimented with it, to find the best possible solutions. In order to help you save time on rechearching this issue, I'll now post this, hoping it helps you getting the tablet back to life and running.
Notice: this is for excelvan mt 10 tablet only. I have no idea, if this works for any other product, so don't ask me, just look around the forum to find help. If the real hardware is bricked, this won't work either, your device should be repaired by qualified service persons to proceed with this.
1 setup your pc to get started.
I've installed the following software on my windows 10 desktop pc:
- The MTK Droid tools, links are supplied by this forum
- The MTK Sp Flash tool, you'll find links for that in this forum or get it from mediatek
- Philz recovery, use google to find it
- Kingo Root, you'll find it at the kingo root home page
- The Mediatek VCOM USB Drivers for Windows 10 (As for my PC) at Mediatek.
- The stock rom for excelvan mt10 tablet, you'll find it on needrom, download for registered users only
Installation of the software on your pc is straight forward, just follow the on-screen installation instructions and you'll be good to go.
Probably your device is bricked already, so no further action needs to be taken on your device.
The first thing you'll have to do is to see, if your drivers can connect to the device. To achieve this, follow the procedure below.
1. After setting up the drivers package, connect the device to your PC, using original USB cable. There are a lot of cables around there, but please use the original provided cable, as it is not sure, that other cables have all pins connected for this, so do yourself a favour...
2 Go to the device manager in your pc and look for your phone's name or the mediatek VCOM driver to run. If the device is booted up, you'll find them, if your device is bricked, you'll have to initiate the META mode of the 6572, to establish the connection. Luckily, the device has a reset button, so if it is bricked, you'll need to connect it to your PC, open up the device manager and press the reset button. (I've opened the device the very first time, to unsolder the battery leads, but I didn't know then, that there was a reset button...) The reset button is located between the micro USB and the Headset connectors on the right upper side of the device, the little hole there, use an insulated papar clamp to press it. In the device manager, you will see the driver popping up and after a short time, shut down. This is normal operation, sometimes it starts reconnecting over and over again, but that's allright.
3. First, you should try to get the preloader back on the system. This is very useful, many devices are bricked by shooting off the preloader. Open up SP Flash Tool, load the scatter file from the unzipped stock rom image for the device. You'll see the used blocks and partitions used by the software in the right pane of the flashtools program. Uncheck all blocks first, then click the checkbox at the 'Preloader', the first entry in the right pane..
4. Now connect your device with the USB cable to the pc. Yes, this comes first. Now press the 'Download' button, the dropdown bar should tell you 'Download Only'. If not, please select this from the dropdown and press download. Now the program waits for the connection, so press the reset button of your device. If all is setup correctly, your device will connect and download will start. First, you'll see a red bar running at the bottom part of the programs's screen, shortly followed by a yellow bar, showing progress of the download. If the download was successfull, you'll be notified accordingly. Disconnect your device and wait 10 seconds, then reconnect it to the pc. If your download was successfull, your phone will be recognised and stay connected, please look in your device manager on your pc, to see connection startup. You'll see the battery charging icon on your device, so it shows, that it is recovered back into it's life.
5. Now it comes to flash the rest of the firmware, so go back to SP Flash Tools, select the scatter file again, check all blocks EXCEPT the preloader and flash it to the device the same way, you've flashed the preloader. Now that you've selected more blocks to flash, you'll see that this takes much more time to download. So please be patient, do not tamper with anything, go ahead, get yourself a coffee or a beer and relax. If everything is okay, flashtools will inform you if the download of the firmware is successfull. If yes, you are good to go, for the first startup of your device.
Disconnect the device from your pc and power it on. If all is right, it will boot up android and you're ready to install and customize it for you.
But sometimes things just don't work this way, what can you do ?
Well, in my case, I've shot my preloader at the first try to flash the stock rom. Yes, I did not obey the rule that I should not tamper with this preloader, so it was checked also. This was a big mistake, after unsuccessfull download, the device did not react any more. The second time (I've bricked it again, because I would like to know, how to restore a bricked file system). So I've formatted all partitions, reinstalled everything and it worked fine. You can do this with the SP Flash Tools also.
I was tired of the 'Factory Recovery Mode', a standard piece of software, which seems to be some sort of rudimentary, so I'd like to install a CWM recovery for that. It would let me install a ZIP Update from the SD card, so it seems more usefull than that rudimentary factory recovery, but how to establish that ?
Searched the web for a long time. Used MTK Droid Tools for that, but this didn't work on the device. It could not create the recovery because of two errors:
- No found kernel GZ
- No found split boot image.
The search for the solution to these both errors resulted in just one thing: There seems not to be a solution for that.
If I can find the time, I will try to solve this but in this moment....
In this case, you'll have just one option left, install Philz Recovery. It brings touch capab8illity also, so it just seems ideal to have that. Besides the fact, that you can use the touch interface, the software brings a ton of usefull options with it, so it is the best choise for your device. I've extracted the ZIP file and dropped all items on my desktop to have a quick access to it.
This can only be done on a routed device, so you'll need to root it before continuing. Not rooting the tablet will result in hanging up the recovery program, so no use. I've rooted the device using kingo root. It runs on my pc and the only things installed on my device are the kingo root super user module and the kingo link module, for connectivity. The latter installations are done by kingo root and your PC, so you'll not have to do this yourself.
Rooting the device will take some time, so be patient. My device is connected as a JTY MT 10 Smartphone, when kingo root recognises it. It can take up to an hour to root. Probably there are other rooting programs out there, which could do the same, but I've tested a few of them, nothing else worked properly. I'll be using kingo root for this device in the future. Be aware, that the rooting with kingo root is session dependable, so after rebooting your device, you'll have to root it again.
You may now run the setup program for philz recovery. It can take more times starting up the program to successfully install the recovery on your device. I had to start the program 5 times, to get it installed completely, so if it is not working the first time, don't panic and start it over again.
The standard recovery image from the stock rom is not the same size as the recovery from philz. The program warns you for getting IMEI lost, so if you don't want this to happen, quit installation here. If you know what you do AND you have a backup of IMEI (NVRAM folders of the device) just go ahead. If installation of the recovery was successfull, you'll be notified by the program running on your pc. Now you can boot your device into recovery, by hitting the apropriate button presented by philz recovery setup program on your pc. To do this on the device itselft, power it off, wait 20 seconds, press the VOL + button and hold this while then pressing the power button. Hold these untill your screen lights up and select 'Recovery' from the menu, use VOL + for selecting, use VOL - to confirm. If the program starts, you'll notice, that it is 'Upside-Down'. That should not bother you, for this little inconvenience you get paid with a superb recovery.
In the next section of this post, I'll cover the backup and restore issues, using MTK Droid Tools, explain how to reinstall an IMEI, how to install a new MAC adress on the device. So stay tuned...
Joshi
Does anyone has custom recovery for Excelvan MT10?
Hi all,
I wonder if somebody could help me.
At the moment I have a Z5 compact with a broken screen (totally black) and touch. I know it still can boot, because it responds to my fingerprint when booted up. However, it does respond to my finger, but still needs a patern on first boot, which I cannot do on account of the broken touch screen. Also, my computer detects the phone.
I want to access my data, but for that I would have to use the onscreen menu which pops up when I connect the phone with usb. That's impossible.
I looked around on the internet and it is possible to remotely control the screen or access via adb. However, for that I either need to install some app on the phone, enable usb-debugging or authorise access via adb. All of those are impossible.
My phone has un unlocked bootloader and is rooted, so as a last resort I've tried to flash a modified kernel to enable usb debugging by default. This fails. Probably because I make some mistake in modifying the kernel, but I don't know. There's not a lot of response from my phone, as you understand ... Besides, I've absolutely no experience modding myself.
Anybody any idea, please?
So I just fixed the same issue you're having this week. It required opening up the phone.
Basically the ribbon cable that connects the screen to the motherboard had become unseated and needed to be plugged back in for me.
The Z5C isn't the easiest phone to take apart but it's not that difficult either. Just requires some basic tools (Hair dryer, tweezers and some precision screw drivers). There's a bunch of videos showing you how on ifixit or youtube. You just have to go all the way to the part where they flip over the motherboard and unplug the two ribbon cables, one of those two will be the culprit.
This is the first and only phone I've taken apart so any amateur can do this.
Boot to recovery and connect your phone to PC
Nutchos said:
So I just fixed the same issue you're having this week. It required opening up the phone.
Basically the ribbon cable that connects the screen to the motherboard had become unseated and needed to be plugged back in for me.
Click to expand...
Click to collapse
Yes, actually I've had problems with a broken backlight before and opening the phone and re-adjusting the cable solved that. Not in this case however. Thanks for your suggestion, anyways.
mlleemiles said:
Boot to recovery and connect your phone to PC
Click to expand...
Click to collapse
Would recovery provide me with some way to enter my pattern via a PC, e.g. with ADB?
Actually, I'm not sure I had any recovery installed at all. I've tried this before and just tried it again. I press the on/off-button while holding volume down. After that no response whatsoever. My computer does not see any device when connected. I suppose my recovery does not work properly, but without screen I can't be certain.
mlleemiles, you are a _hero_!
After reading your post I decided to try flashing another recovery to try if that might work. Now I can access my files without ever having entered any pattern .
Nevermind that it turns out my files weren't encrypted and I thought they were.
If anyone has a similar problem in the future, this is what worked for me:
My exact situation:
- My phone runs a stock rom (downloaded from XperiCheck) with version 32.4.A.1.54. When my phone was still running ok I had the bootloader unlocked and my device rooted with Rootkernel.
Working solution:
- I downloaded Twrp, version 3.2.1, from this page:
https://forum.xda-developers.com/z5-compact/development/twrp-twrp-3-2-1-z5-compact-t3748952
- Shut down my phone by disconnecting the battery and reconnecting it again
- Started my phone in fastboot mode and flashed recovery to my phone with:
Code:
fastboot flash recovery recovery_suzuran_220218_2.img
- Booted my phone in recovery with volume down + on/off-button.
- Connected my phone to my PC, et voila.
Turns out I can also access my phone with ADB as root, so after backing up the entire internal memory, I might try to get some remote screen tool working.
So thanks for the help and if I find something interesting and new, I'll post that too.
Small update:
After successfully flashing Twrp I backed up the internal memory, so must of the important stuff was safe by then.
However, it turned out that my phone now wouldn't boot into anything other then Twrp. I decided to flash my rom again. First I installed my apb keys using Twrp:
Code:
adb push adbkey.pub /data/misc/adb/adb_keys
It turned out I already had usb debugging enabled.
I then flashed my original firmware again, and connected with adb. This time it connected correctly, without me having to click any dialogue on my phone. I fiddled with several remote control Android tools most of which didn't work. Finally, it turned out Vysor does exactly what I want to do. It is a bit unstable, but workable.
Anyways, I've finally managed to copy all the stuff I wanted from my phone.
This latest tool also allows you to boot your Samsung Smartphone and tablets into the download mode without pressing the physical keys. If in case your Samsung device physical keys are not working, then this latest Samsung tool is useful for all of you. The best thing about this tool is that it is not necessary to have the USB debugging active. The tool only detects your device and restarts it in download mode to do the flashing by ODIN.
How to use Samsung 300K Tool
This latest tool is useful for those users who have Samsung devices that do not enter download mode with the failure of keys.
After download file is complete simply Run for install.
Make sure that the Samsung drivers are installed
Before connecting the device open the program and the following screen instructions.
Now connect your device to the computer and make sure that the cable is properly or correctly connected, and the screen will change.
In this last step click on the figure of the image where the strain point and your cell phone connected or not enter the download mode quickly in 2 seconds, but I recommend doing the operation with the phone is connected.
Done.
Admin Edit: Attachment has been removed as it was flagged by Google as "uncommon download". Also locking thread.
speechless said:
This latest tool also allows you to boot your Samsung Smartphone and tablets into the download mode without pressing the physical keys. If in case your Samsung device physical keys are not working, then this latest Samsung tool is useful for all of you. The best thing about this tool is that it is not necessary to have the USB debugging active. The tool only detects your device and restarts it in download mode to do the flashing by ODIN.
How to use Samsung 300K Tool
This latest tool is useful for those users who have Samsung devices that do not enter download mode with the failure of keys.
After download file is complete simply Run for install.
Make sure that the Samsung drivers are installed
Before connecting the device open the program and the following screen instructions.
Now connect your device to the computer and make sure that the cable is properly or correctly connected, and the screen will change.
In this last step click on the figure of the image where the strain point and your cell phone connected or not enter the download mode quickly in 2 seconds, but I recommend doing the operation with the phone is connected.
Done.
Click to expand...
Click to collapse
The attached Samsung 300k file gives a CRC error when extracted. also its an exe and doesnt run on Windows 10. Is there an equivalent file that will allow my samsung galaxy T4 (sm-231 v4.4.2 Kitkat) to enter download mode? Its home key is not working right now. Using ADB i am able to enter Manual mode, but not Download mode! So ODIN does not recognize it ( ID:COM is not highlighted). I have installed the latest Samsung USB drivers.
any help will be most appreciated.
sifar786 said:
The attached Samsung 300k file gives a CRC error when extracted. also its an exe and doesnt run on Windows 10. Is there an equivalent file that will allow my samsung galaxy T4 (sm-231 v4.4.2 Kitkat) to enter download mode? Its home key is not working right now. Using ADB i am able to enter Manual mode, but not Download mode! So ODIN does not recognize it ( ID:COM is not highlighted). I have installed the latest Samsung USB drivers.
any help will be most appreciated.
Click to expand...
Click to collapse
When the phone is booted up normally and the way you would normally use it, when you connect your phone and open ODIN, does it still not pick up the phone on the COM port?
And (I'm sure you do), do you have USB debugging turned on and all the other usual things (like you mentioned, having installed the latest drivers)?
Samsung galaxy tab 4 (sm-t231) kitkat v4.4.2
Max_Terrible said:
When the phone is booted up normally and the way you would normally use it, when you connect your phone and open ODIN, does it still not pick up the phone on the COM port?
And (I'm sure you do), do you have USB debugging turned on and all the other usual things (like you mentioned, having installed the latest drivers)?
Click to expand...
Click to collapse
yes, i finally used "adb reboot download" to boot into download mode. Now when i am using ODIN and trying to root my cell by installing TWRP 3.2.1-0-degas.img.tar, it says PASS (success 1/fail 0), but my mobile still shows "DOWNLOADING..." with a horizontal blue line. I can also reboot and load normally, but it seems TWRP has not got installed and still ROOTCHECKER says my mobile is not rooted. Am i using the wrong versions of TWRP recovery or ODIN etc? Can you advice next steps?
sifar786 said:
yes, i finally used "adb reboot download" to boot into download mode. Now when i am using ODIN and trying to root my cell by installing TWRP 3.2.1-0-degas.img.tar, it says PASS (success 1/fail 0), but my mobile still shows "DOWNLOADING..." with a horizontal blue line. I can also reboot and load normally, but it seems TWRP has not got installed and still ROOTCHECKER says my mobile is not rooted. Am i using the wrong versions of TWRP recovery or ODIN etc? Can you advice next steps?
Click to expand...
Click to collapse
When you've flashed TWRP, the phone will stay in download mode. Nothing will change on screen, that is normal. You have to reboot the device manually, using the button combination it says, then immediately as the device restarts, you change the combination to boot into TWRP. All of these steps are explained in whichever thread or wherever you found TWRP.
As far as rooting is concerned; TWRP doesn't inherently root the device. It just replaces the bootloader to allow you to flash custom packages, like the one needed to root the device.
If you're struggling to get the device rooted and there isn't a very specific reason why you need root, then my best recommendation would be to rather just leave it stock.
As far as I know, flashing TWRP won't trigger Knox, so you'll still have that functionality. Recently, it's become less and less necessary to have root and fewer apps require it, as well.
Like I said, unless there is a very specific reason, you'll likely be better off just leaving it the way it is.
EDIT: I'm realising now the original problem was that your home button wasn't working. In that case, it'll be difficult to get into TWRP, anyway. I also made some assumptions about Knox, because this is on the Note8 sub forum. I don't know if your device has Knox. And You're on a rather old version of Android also, so I understand why you may want to root, but without your home button working, it could become difficult to get into the places where you need to be to make that possible.