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!!!
Hello guys!
I have read everything here on this topic, but I have some questions that I need answered:
I used this "super easy" root method with that chinese application http://forum.xda-developers.com/showthread.php?t=2439667
I then used the root checker app and it said that the phone is rooted.
And then I used Flashify to flash a clockwork recovery image onto my LG L9 and it flashed okay, but when I rebooted the phone it said Security Error on the LG screen.
Please tell me there is a way to fix this without erasing all the data on the phone...........
Thank You very much in advance!
I somehow managed to install that firmware, but now everything is inverted and backwards. Touchscreen is barely functioning. Even the colors are not the same. I did a hard reset but it keeps on being inverted.
My phone have the T-Mobile logo on top, I dont know which kdz and from where should I download it.
sqnkov said:
I somehow managed to install that firmware, but now everything is inverted and backwards. Touchscreen is barely functioning. Even the colors are not the same. I did a hard reset but it keeps on being inverted.
My phone have the T-Mobile logo on top, I dont know which kdz and from where should I download it.
Click to expand...
Click to collapse
Can you access "Backup" app by LG?
If so, make an backup of all you have in the phone, place it in your PC (or somewhere safe), connect your phone to PC, and install LG Mobile Support Tool. After it is installed, open it, click Options and then Upgrade Recovery.
All files and saves from the phone will be lost (except SD Card), but when the program finishes restoring system, you will be able to restore your saves, apps, settings etc. back.
Don't forget to backup and but it in your PC!
After restoring the system, put backup file back in your phone, then enter in "Backup" app, and then restore.
Hope it was clear
mihai.apostu98 said:
Can you access "Backup" app by LG?
If so, make an backup of all you have in the phone, place it in your PC (or somewhere safe), connect your phone to PC, and install LG Mobile Support Tool. After it is installed, open it, click Options and then Upgrade Recovery.
All files and saves from the phone will be lost (except SD Card), but when the program finishes restoring system, you will be able to restore your saves, apps, settings etc. back.
Don't forget to backup and but it in your PC!
After restoring the system, put backup file back in your phone, then enter in "Backup" app, and then restore.
Hope it was clear
Click to expand...
Click to collapse
Yes, you were clear enough, but I CAN NOT access LG recovery neither I can NOT install Clockwork mod. The only thing I get is the inverted touchscreen phone and the S/W upgrade mode...
How can I install CWM or enter any kind of recovery??
This is my second day trying to fix this, I am getting mad.
P.S. I have backed up everthing before that.
sqnkov said:
Yes, you were clear enough, but I CAN NOT access LG recovery neither I can NOT install Clockwork mod. The only thing I get is the inverted touchscreen phone and the S/W upgrade mode...
How can I install CWM or enter any kind of recovery??
This is my second day trying to fix this, I am getting mad.
P.S. I have backed up everthing before that.
Click to expand...
Click to collapse
So enter in S/W upgrade mode, then connect your phone to PC and do as i said. Install LG Mobile Support Tool, after installing open LG Mobile Support Tool, click Options, then click Upgrade Recovery (all this stuff is in LG Mobile Support Tool, not in your phone, your phone needs to be in S/W upgrade mode)
It will install official KDZ from LG servers to your phone, and it will be like new.
mihai.apostu98 said:
So enter in S/W upgrade mode, then connect your phone to PC and do as i said. Install LG Mobile Support Tool, after installing open LG Mobile Support Tool, click Options, then click Upgrade Recovery (all this stuff is in LG Mobile Support Tool, not in your phone, your phone needs to be in S/W upgrade mode)
It will install official KDZ from LG servers to your phone, and it will be like new.
Click to expand...
Click to collapse
I understand this. But it doesn't do anything. I have to enter the IMEI for the Recovery Update to start, and after it connects the phone it stops at the download phase where the timer stops and NOTHING happens.
Check the Driver
sqnkov said:
I understand this. But it doesn't do anything. I have to enter the IMEI for the Recovery Update to start, and after it connects the phone it stops at the download phase where the timer stops and NOTHING happens.
Click to expand...
Click to collapse
Make sure your phone is being recognised under Devices in control panel.
Regards,
SS
sqnkov said:
Hello guys!
I have read everything here on this topic, but I have some questions that I need answered:
I used this "super easy" root method with that chinese application http://forum.xda-developers.com/showthread.php?t=2439667
I then used the root checker app and it said that the phone is rooted.
And then I used Flashify to flash a clockwork recovery image onto my LG L9 and it flashed okay, but when I rebooted the phone it said Security Error on the LG screen.
Please tell me there is a way to fix this without erasing all the data on the phone...........
Thank You very much in advance!
Click to expand...
Click to collapse
I did the exact same thing as you, as soon as i rooted it i should have stopped its really all i needed, but no i had to go one step further and use flashify to install clockwork and yep when it rebooted i got the security error. The main issue i am having is that no matter what i try to do its like the phone is not being detected or seen by the programs via usb. i have installed the fastboot drivers, i have installed the lg united drivers, i let the support program install the drivers, still nothing. as soon as i plug in the usb to the phone windows pops up a message saying device not recognized, even though i see the lg united drivers in device manager under ports.
curiousgeorge23 said:
I did the exact same thing as you, as soon as i rooted it i should have stopped its really all i needed, but no i had to go one step further and use flashify to install clockwork and yep when it rebooted i got the security error. The main issue i am having is that no matter what i try to do its like the phone is not being detected or seen by the programs via usb. i have installed the fastboot drivers, i have installed the lg united drivers, i let the support program install the drivers, still nothing. as soon as i plug in the usb to the phone windows pops up a message saying device not recognized, even though i see the lg united drivers in device manager under ports.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2779985
I followed the same damn instructions from @cmahendra that you did and as soon as I got it rooted, I installed CWM via flashify and it rebooted and then BAM! " Security Error" and now I can't do anything with this phone.
I can't get into the "software" or "Download mode. When connecting to my Windows computer, it's not detected in Device manager, it just makes the sound like a device was connected, then immediately disconnected.
I have the LG Mobile Support Tool, but it doesn't work because the PC can't detect/install drivers for the phone. It has been detected for a short period a handful of times and is being detected as an OMAP 4430.
I have the LGT Universal driver pack as well and that doesn't help anything either.
gorilla p said:
http://forum.xda-developers.com/showthread.php?t=2779985
I followed the same damn instructions from @cmahendra that you did and as soon as I got it rooted, I installed CWM via flashify and it rebooted and then BAM! " Security Error" and now I can't do anything with this phone.
I can't get into the "software" or "Download mode. When connecting to my Windows computer, it's not detected in Device manager, it just makes the sound like a device was connected, then immediately disconnected.
I have the LG Mobile Support Tool, but it doesn't work because the PC can't detect/install drivers for the phone. It has been detected for a short period a handful of times and is being detected as an OMAP 4430.
I have the LGT Universal driver pack as well and that doesn't help anything either.
Click to expand...
Click to collapse
yes thats the one i followed, for the love of god could someone please tell me how to get these drivers intalled, everytime i install lg united drivers i cant install omap, if i can get omap installed then i cant get lg united drivers, one time i was able to have both installed i have no idea how i was so confused at that time cause i had tried so much stuff, but windows was still saying usb device not recognized. and i tried the offline fix mode but it got stuck at 15 percent something about phone not connected thru usb. even when i have omap or lg drivers installed and plug the phone in it is not activating in device manager i can only see it in hidden mode.
Same here. I asked for help and was accuses of blaming him and not asking respectfully enough. Idk what to do with this thing.
My G3 powered off and stopped booting today. It was connected to a laptop via an old frayed usb cable, and it suddenly shut off.
It was then that the power button stopped working and I saw the QHS usb loader device of death (Windows new device notification)
Intermittently I have seen the QHS USB 9008 device when connecting to my PC, but not always.
I tried to run the QCDiag tool, but it said failed to flash.
Any tips?
Is it possible a connection is loose? Wondering if I can open the phone up and fix it.
It was working mostly fine prior to this, with occasional issues of the SIM being undetected.
Did you try the following program?
"BoardDiag3.99c.zip" in the OP of this thread [FIX] Unbrick LG G3 stuck in Qualcomm HS-USB QDLoader 9008 mode?
It is certainly possible that the connection is unreliable. I always use the original USB cable, and preferably with a USB 2.0 port that's directly off of a PC motherboard rather than through a USB hub. Also, you might need a special driver. You can get it from here http://www.androidbrick.com/download/qdloader-hs-usb-driver/. Install the correct (32 or 64-bit, depending on which version of Windows you're running) driver with the phone disconnected from the PC, then reboot the PC, connect the phone and give Windows up to 10 minutes to install the driver. Every time you choose a different USB port after that, it'll have to load (not install) the driver again (that's standard for all USB devices. Then try the BoardDiag program again.
Also, if you can get this far, it's preferable to only use the BoardDiag software to flash a few very specific partitions rather than the entire 10B TOT. After flashing these partitions, then you can flash the 10B TOT with the regular TOT flashing software.
Use the screenshots in this thread as a guide for which partitions:
Unbrick lg g3 qhsusb_bulk, qualcomm 9008 workking 100% by board ver 2.9a.
Yes, I tried this tool but it said failed to flash after clicking on Start.
If I open up the device, is there anything I can check for?
ipaq_power said:
Yes, I tried this tool but it said failed to flash after clicking on Start.
If I open up the device, is there anything I can check for?
Click to expand...
Click to collapse
I've never opened up the G3 (further than removing the back/battery). The only reason I've heard of doing so regarding QHSUSB mode is if you have to force it into QHSUSB_BULK 9008 mode, but you'd have to Google for that - there are diagrams for two pins you need to short to get it into that mode but it sounds like you're there already so that might not be necessary.
Did you install the drivers I linked to (while the phone's disconnected from the PC?), reboot the PC, connect the phone to a USB 2.0 port and give the PC up to 10 minutes to load the drivers you installed?
I also highly recommend using an original good cable, so you might have to buy one from LG. It's possible that any very high-quality USB cable will work, but it's recommended to use the original (in good condition). I wouldn't use a USB cable with frayed wires at all. Next thing you know there'll be a short and possibly your PC, your PC's USB ports, and/or your phone or your phone's MicroUSB port will be blown.
Yeah the drivers were installed properly.
I tried to run the LG Smart Boot diagnostic tool, but the phone did not stay on for long enough to execute the checks.
It briefly connected to the tool before powering off again.
I have received a replacement phone, but it came with firmware version 35B.
ipaq_power said:
Yeah the drivers were installed properly.
I tried to run the LG Smart Boot diagnostic tool, but the phone did not stay on for long enough to execute the checks.
It briefly connected to the tool before powering off again.
I have received a replacement phone, but it came with firmware version 35B.
Click to expand...
Click to collapse
What do you want to be on, and do you want to be rooted or unrooted?
If you want to be unrooted on the latest ROM, just flash the 47A KDZ in @annoyingduck 's stickied return to stock thread in the General section, or if you have an activated Verizon SIM, take the two OTAs 35B->46A and 46A->47A.
If you want to be rooted, flash the 10B TOT using the .DLL that was extracted from the 35B KDZ, root using the Stump app, use TWRP Manager from the Play Store to put TWRP on, then flash the bootstack and ROM you want.
I have flashed my device probably 50 times at this point trying different ROMS. Yesterday I decided to give stock another shot, but now I'm stuck. I had to flash the stock recovery to update to Marshmallow after restoring my Lollipop backup. I'm not happy with it, but I cannot reflash TWRP. When I boot to bootloader the fastboot drivers no longer work. Windows device manager says it's an unknown device and the device descriptor failed. I can't even manually force it to install the driver for the device by picking it, because it says that the driver isn't for that device. I even tried resetting my crappy Windows tablet so that it would have nothing previously installed and then installed HiSuite, but the same problem there as on my desktop. I have also tried generic "universal" android drivers and sketchy Huawei drivers from a "how to unlock your bootloader" tutorial. I have unplugged it and replugged it several times, using various different USB ports (I have 10 of them, so no shortage there).
I can't flash recovery through fastboot because that isn't an option. When in normal mode the computer sees the device just fine as a MTP device and an ADB device, but when I try to run ADB commands they don't see the device either. At this point I am really trying to find any way I can root the phone, regardless of how sketchy, so I can use Flashify to restore TWRP and go back to CM13 or an AOSP. Does anybody know a working method to root besides flashing through fastboot? Thanks.
Darrian said:
I have flashed my device probably 50 times at this point trying different ROMS. Yesterday I decided to give stock another shot, but now I'm stuck. I had to flash the stock recovery to update to Marshmallow after restoring my Lollipop backup. I'm not happy with it, but I cannot reflash TWRP. When I boot to bootloader the fastboot drivers no longer work. Windows device manager says it's an unknown device and the device descriptor failed. I can't even manually force it to install the driver for the device by picking it, because it says that the driver isn't for that device. I even tried resetting my crappy Windows tablet so that it would have nothing previously installed and then installed HiSuite, but the same problem there as on my desktop. I have also tried generic "universal" android drivers and sketchy Huawei drivers from a "how to unlock your bootloader" tutorial. I have unplugged it and replugged it several times, using various different USB ports (I have 10 of them, so no shortage there).
I can't flash recovery through fastboot because that isn't an option. When in normal mode the computer sees the device just fine as a MTP device and an ADB device, but when I try to run ADB commands they don't see the device either. At this point I am really trying to find any way I can root the phone, regardless of how sketchy, so I can use Flashify to restore TWRP and go back to CM13 or an AOSP. Does anybody know a working method to root besides flashing through fastboot? Thanks.
Click to expand...
Click to collapse
There is none. The only safe way to root is to flash TWRP in fastboot. Right now, you can try to force update through update.app
Thanks for the reply, but:
1. I'm not looking for a safe method, just any method. I've tried the obvious suspects already (towelroot, kingroot, kingoroot)
2. I don't need to force an update, I am on the latest firmware now. If anything I may have to attempt to force a downgrade to open up vulnerabilities, but if I go back to lollipop then I will likely have issues flashing cm13.
Darrian said:
Thanks for the reply, but:
1. I'm not looking for a safe method, just any method. I've tried the obvious suspects already (towelroot, kingroot, kingoroot)
2. I don't need to force an update, I am on the latest firmware now. If anything I may have to attempt to force a downgrade to open up vulnerabilities, but if I go back to lollipop then I will likely have issues flashing cm13.
Click to expand...
Click to collapse
Oh. But like I said, there is none.
I have come to the same conclusion, but I'm still hoping if somebody has rooted it in another way that they will see this thread and share their method. Otherwise I may end up stuck on unrooted stock, which will kinda suck.
Darrian said:
I have come to the same conclusion, but I'm still hoping if somebody has rooted it in another way that they will see this thread and share their method. Otherwise I may end up stuck on unrooted stock, which will kinda suck.
Click to expand...
Click to collapse
Have you tried changing the drivers.?
Yes
So, I did not figure out how to root it without fastboot, but I did solve my problem. I dug out the cable that came with the phone, and using that cable my computer finally recognized it as an Android device when in fastboot mode. I don't know why it only works with that cable, but there it is, so I will have to make sure that cable never gets broken or lost.
Darrian said:
So, I did not figure out how to root it without fastboot, but I did solve my problem. I dug out the cable that came with the phone, and using that cable my computer finally recognized it as an Android device when in fastboot mode. I don't know why it only works with that cable, but there it is, so I will have to make sure that cable never gets broken or lost.
Click to expand...
Click to collapse
Glad you fixed it. :highfive:
I flashed TWRP which worked, rebooted into TWRP so that still worked then tried wiping but got a mount error, I tested if it would install the img anyway and still mount error, so I changed slot from A to B, since then its just black screen and not recognised on PC at all.
dekadude said:
I flashed TWRP which worked, rebooted into TWRP so that still worked then tried wiping but got a mount error, I tested if it would install the img anyway and still mount error, so I changed slot from A to B, since then its just black screen and not recognised on PC at all.
Click to expand...
Click to collapse
First of all, what did you wipe in TWRP? /data?
Have you ever installed an OTA update? If not, you can't boot into the other slot. Same if you restored via MSM. You need to do one local upgrade until the B slot is bootable.
That will be what it is, I didn't do a OTA update. Is there a way to get back to the original slot?
I tried deleting data.
dekadude said:
That will be what it is, I didn't do a OTA update. Is there a way to get back to the original slot?
I tried deleting data.
Click to expand...
Click to collapse
Mounting and formatting of /data is not supported on older TWRPs. Try the most recent one from mauronofrio here on XDA if you want to format it (at least for custom ROMs).
For Oxygen OS I would suggest using "fastboot -w" instead as OOS still can't be decrypted.
Probably either use the MSM tool or use "fastboot --set-active=a" and then try "fastboot -w" if it doesn't boot.
I can't currently get into TWRP though at the moment, after I changed slots its just powered off all the time and not recognised on pc I haven't used any tools though.
So I guess MSM tool might work, but would that work if currently the pc isn't recognising a usb device connected?
dekadude said:
I can't currently get into TWRP though at the moment, after I changed slots its just powered off all the time and not recognised on pc I haven't used any tools though.
So I guess MSM tool might work, but would that work if currently the pc isn't recognising a usb device connected?
Click to expand...
Click to collapse
It should automatically download the drivers if you connect it in EDL mode.
Macusercom said:
It should automatically download the drivers if you connect it in EDL mode.
Click to expand...
Click to collapse
Great, whats best guide for that, I will mention its the China version of phone think its HD1910
dekadude said:
Great, whats best guide for that, I will mention its the China version of phone think its HD1910
Click to expand...
Click to collapse
Download the correct version here and follow the instructions: https://forum.xda-developers.com/7t-pro/how-to/op7tpro-unbrick-tool-to-restore-device-t4002909
Macusercom said:
Download the correct version here and follow the instructions: https://forum.xda-developers.com/7t-pro/how-to/op7tpro-unbrick-tool-to-restore-device-t4002909
Click to expand...
Click to collapse
Thanks for help so far, one final thing I hope when I picked up phone it gave me the full screen battery power too low to turn on message so it gave me hope I can fix it, I charged it for about 10 minutes and it gave me the "bootloader unlocked press power to pause" screen.
What is best thing to do here? Let it fully charge then connect to PC and try the MSM tool or let it drain and then connect to pc instead of charger and let it charge till its recognised by pc?
dekadude said:
Thanks for help so far, one final thing I hope when I picked up phone it gave me the full screen battery power too low to turn on message so it gave me hope I can fix it, I charged it for about 10 minutes and it gave me the "bootloader unlocked press power to pause" screen.
What is best thing to do here? Let it fully charge then connect to PC and try the MSM tool or let it drain and then connect to pc instead of charger and let it charge till its recognised by pc?
Click to expand...
Click to collapse
Charge it for an hour with a wall plug and then follow the MSM tool instructions.
Macusercom said:
Charge it for an hour with a wall plug and then follow the MSM tool instructions.
Click to expand...
Click to collapse
Actually, I noticed I am able to now get into TWRP without connecting to pc, and switch back to slot A, but it said no OS installed.
Do I still need to flash via the MSM tool or can I just update TWRP then install stock rom, update then go back into TWRP and install custom? Or what is best way?
dekadude said:
Actually, I noticed I am able to now get into TWRP without connecting to pc, and switch back to slot A, but it said no OS installed.
Do I still need to flash via the MSM tool or can I just update TWRP then install stock rom, update then go back into TWRP and install custom? Or what is best way?
Click to expand...
Click to collapse
You can either flash OOS via the latest TWRP (and probably do fastboot -w) or I would just use the MSM tool which is much easier and gets you a fresh install
EDIT : Problem Solved!