Related
Hi guys, was having a few problems with my phone and decided that I'd flash the stock ROM again.
Went into ODIN as you do, and as I was flashing the stock ROM, for some reason or another I heard the disconnect/reconnect noise that Windows makes when you remove a device then FAIL came up in ODIN.
Now my phone's stuck with a phone connecting to a computer on the charge screen, it can't go into recovery mode but it can go into download mode.
Tried connecting it to my PC in download mode, and even though I've got the Samsung USB Drivers installed I get the 'USB Device Not Recognized' message, which means I can't flash the stock ROM in ODIN anymore.
Does anyone have any advice? Thank you.
JoshS2 said:
Hi guys, was having a few problems with my phone and decided that I'd flash the stock ROM again.
Went into ODIN as you do, and as I was flashing the stock ROM, for some reason or another I heard the disconnect/reconnect noise that Windows makes when you remove a device then FAIL came up in ODIN.
Now my phone's stuck with a phone connecting to a computer on the charge screen, it can't go into recovery mode but it can go into download mode.
Tried connecting it to my PC in download mode, and even though I've got the Samsung USB Drivers installed I get the 'USB Device Not Recognized' message, which means I can't flash the stock ROM in ODIN anymore.
Does anyone have any advice? Thank you.
Click to expand...
Click to collapse
Try installing samsung kies. The usb drivers are included.
princeownt said:
Try installing samsung kies. The usb drivers are included.
Click to expand...
Click to collapse
I have it installed, and I installed the USB drivers from the soft bricked sticky in this section. Neither have helped.
Hi!
Hi, you guys install ADB on your system? And also USB debugging mode on the phone?
Should be turned on which can be done by going to Settings>Applications>Development and select USB debugging.
Try this, for me its works
MafiaDroid said:
Hi, you guys install ADB on your system? And also USB debugging mode on the phone?
Should be turned on which can be done by going to Settings>Applications>Development and select USB debugging.
Try this, for me its works
Click to expand...
Click to collapse
I can't even turn the phone on at the moment. Only thing I can do is go into Download mode.
Help
Try this, take out the battery, then press and hold the ON button for 7-10 seconds (the longer the better). Reinsert the battery, then press ON button to start it. This is a soft reset, and wipes the temporary memory and empties all remaining power in the circuits. This helps on many phones and even laptops that won't start properly or show anything on screen.
If this does not work, try the next step. Again, do as above. But after inserting the battery, do not turn the phone on, but press and hold the ON button and the HOME button at the same time for 7-10 seconds. This is a hard reset, and works best if done after a soft reset. Just be sure the battery has at least some juice in it and isn't empty. If possible, try with another battery if this does not work.
Hope this helps!
Try going to device manager, you will probably find your device as an unrecognized device, uninstall the drivers, unplug and then plug it again and see.
if the prblm is hard then do a fresh installation of kies,device etec etc.....but if u have ur device in the device list on pc then first uninstall it...if possible try recovery mode and reset...
I tried everything you guys have suggested and none of that worked. Anyone else got any ideas?
Try everything (and I mean everything) on the following list. Given the problems you've had & that you've already tried some of these things, I'd try another PC. And if it doesn't work first go on another PC, then go thru the list & try everything on the 2nd PC.
*Ensure Kies & it's processes aren't running in Windoze task manager. Kill them if they are.
*Try different USB ports; you must be using a 'powered' or mainboard port.
*Try different USB cables (particularly the cable that came with the phone if you're not using it now)
*Try different versions of Odin (search on here/Google)
*Uninstall Kies, reboot, redownload & reinstall it, reboot, try the flash again. Also run Windoze Update.
*And if all this fails, try a different PC.
Tried all the above and a different PC.
It didn't work. I could fix the phone if the computer would pick up that the phone's connected - it just doesn't.
Total Removal of KIES including registry entries .
Reboot PC install a new copy of Kies .
Phone backup data and factory reset .
Set phone to USB storage mode using the Samsung cable connect to PC and wait for Windows to find USB drivers .Remove cable reboot phone .
Start Kies connect with cable wait for Kies to find the phone .
Note USB Debugging OFF and cable connects to a direct motherboard port only .
Nothing then only further suggestion would be to Format the PC and start over with a clean Windows install .
jje
I can't turn the phone on, it's stuck on the phone, triangle, PC screen.
I've tried fresh installs on three different PC's.
JoshS2 said:
I can't turn the phone on, it's stuck on the phone, triangle, PC screen.
I've tried fresh installs on three different PC's.
Click to expand...
Click to collapse
That's a forced download mode.
Try a blind flash to a stock firmware from Odin while connected to your computer with the phone on this screen. Even if Odin doesn't seem to register that it's connected. I've heard of at least one person this worked for.
At this point, you really have nothing to lose by trying this.
Bit of an update, I plugged it in again and it installed some drivers and ODIN picked it up. Only for it to disconnect a few moments later, now it keeps disconnecting and reconnecting over and over but ODIN's not picking it up.
JoshS2 said:
Bit of an update, I plugged it in again and it installed some drivers and ODIN picked it up. Only for it to disconnect a few moments later, now it keeps disconnecting and reconnecting over and over but ODIN's not picking it up.
Click to expand...
Click to collapse
I know you said you tried a different cable, but that sounds suspiciously like a bad cable.
It's not the cable, thanks any way.
Update 2: I managed to get it to connect long enough to flash the stock Kernel. Still didn't reboot. Then I connected it again and flashed the stock ROM, which bricked it again. Then I flashed the stock kernel and it works!
However, there is a problem:
When the phone gets turned off, it constantly shows the charging battery icon with warning triangle and a thermostat next to it. I can't turn the phone on because of this unless I go into Recovery mode and reboot system.
Any ideas? Thanks.
JoshS2 said:
It's not the cable, thanks any way.
Update 2: I managed to get it to connect long enough to flash the stock Kernel. Still didn't reboot. Then I connected it again and flashed the stock ROM, which bricked it again. Then I flashed the stock kernel and it works!
However, there is a problem:
When the phone gets turned off, it constantly shows the charging battery icon with warning triangle and a thermostat next to it. I can't turn the phone on because of this unless I go into Recovery mode and reboot system.
Any ideas? Thanks.
Click to expand...
Click to collapse
Now this sounds like a faulty/dirty/bad usb port.
ctomgee said:
Now this sounds like a faulty/dirty/bad usb port.
Click to expand...
Click to collapse
This was my original thought and my reasoning for flashing a stock ROM in the first place!
JoshS2 said:
This was my original thought and my reasoning for flashing a stock ROM in the first place!
Click to expand...
Click to collapse
I in no way recommend this, and not sure I would do it if I ever started having this issue...
BUT - I have heard that some people faced with this condition have fixed it by physically moving the small wafer board inside the USB port with a precision screwdriver (gently!) to a more "centered" position.
If that doesn't work, look at replacing that part. Either via warranty service if you still have it, or a service center.
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 phone is on version S124. It is dead right now. Only red light shows when connected to charger and it turns of after some time.
This problem happened before also, I took it to Lenovo service center, they did something and my phone was back on. It is out of warranty, I had to pay for servicing. This has happened again, how can I fix it at my home?
I have SP flash tools, S124 ROM and Windows 7 PC.
Thanks.
NexR said:
My phone is on version S124. It is dead right now. Only red light shows when connected to charger and it turns of after some time.
This problem happened before also, I took it to Lenovo service center, they did something and my phone was back on. It is out of warranty, I had to pay for servicing. This has happened again, how can I fix it at my home?
I have SP flash tools, S124 ROM and Windows 7 PC.
Thanks.
Click to expand...
Click to collapse
Reflash your firmware!
In development section you will find some good tutorials!
Here is one link!
http://forum.xda-developers.com/lenovo-p780/development/rom-lenovo-p780-pre-rooted-official-t2553725
stympy said:
Reflash your firmware!
In development section you will find some good tutorials!
Here is one link!
http://forum.xda-developers.com/lenovo-p780/development/rom-lenovo-p780-pre-rooted-official-t2553725
Click to expand...
Click to collapse
Hi stympy!
I tried that exact thing at first. The problem is it does not recognize my phone on connecting via USB cable. Drivers were correctly installed as I could successfully flash firmware few days before. Now when I connect it to PC via USB cable, it does not show up in device manger, nor is it recognized by SP flash tool (stuck at Searching). Red LED turns on connecting to USB on PC/Power. I have tried all USB ports on my PC and also tried different USB cables.
I have also tried the "plug-in then reset via button on back" method. Not working.
Any idea what's going on?
NexR said:
Hi stympy!
I tried that exact thing at first. The problem is it does not recognize my phone on connecting via USB cable. Drivers were correctly installed as I could successfully flash firmware few days before. Now when I connect it to PC via USB cable, it does not show up in device manger, nor is it recognized by SP flash tool (stuck at Searching). Red LED turns on connecting to USB on PC/Power. I have tried all USB ports on my PC and also tried different USB cables.
I have also tried the "plug-in then reset via button on back" method. Not working.
Any idea what's going on?
Click to expand...
Click to collapse
Hi. Try this:
Uninstall curent drivers.
Reboot computer or laptop.
After reboot open device manager window
Look om ports area on device manager
Plug the phone now
Something with MTK69XX should appear.
If this appear you are on the good track.
If not tell me and we look for something else!
stympy said:
Hi. Try this:
Uninstall curent drivers.
Reboot computer or laptop.
After reboot open device manager window
Look om ports area on device manager
Plug the phone now
Something with MTK69XX should appear.
If this appear you are on the good track.
If not tell me and we look for something else!
Click to expand...
Click to collapse
OK, tried this. When I plug in a device, like my printer, or my other android phone, Device manager window automatically refreshes device list. This does not happen when I plug-in my p780.
Hi all,
by cons for several weeks I've a concern with my redmi Note 2 and I can't find the answer to my problem on the forum or even the Internet.
Since the last update 7.2.2 (global) I have the Recovery MIUI who crushed the TWRP. I changed to test 6.3.17. The update to the .24 went wrong and I don't know why. Since the phone is bootloop. But the problem is that my phone is not recognized by any PC. I tried several PCs, several cables, several drivers, with or without the Fastboot, unable to connect. Therefore impossible to load a new version. I don't think it's material problem because the phone recharge well with a cable to the socket.
Is there another handling or debug decision to restart the phone? I'm in France for information.
thank you in advance if you can point me to a solution !
Hope someone can help me.
Manu
Can the phone boot to miui recovery? If so, you should be able to use miui recovery to flash TWRP (I think you will need one with a signed install zip). You only need to take out the external SD, put it in one of those cheap USB card readers, copy your recovery and ROM to the SD, put it back in the phone, flash TWRP with miui recovery, and then flash the ROM with TWRP (I am assuming that miui recovery can install things from the external SD - if not, then none of this will work).
Hi Bro,
Yes it boot in MIUI recovery but impossible to get access to the SD Card...
I tried to put the file on the SD card but you can't choose the path, I think the recovery will look only in the internal memory ... And as I can't access the internal memory..
I despair !!
Thanks o lot for your help
DarthJabba9 said:
Can the phone boot to miui recovery? If so, you should be able to use miui recovery to flash TWRP (I think you will need one with a signed install zip). You only need to take out the external SD, put it in one of those cheap USB card readers, copy your recovery and ROM to the SD, put it back in the phone, flash TWRP with miui recovery, and then flash the ROM with TWRP (I am assuming that miui recovery can install things from the external SD - if not, then none of this will work).
Click to expand...
Click to collapse
manu33xtro said:
Hi Bro,
Yes it boot in MIUI recovery but impossible to get access to the SD Card...
I tried to put the file on the SD card but you can't choose the path, I think the recovery will look only in the internal memory ... And as I can't access the internal memory..
I despair !!
Thanks o lot for your help
Click to expand...
Click to collapse
Ok - but have you tried the Mediatek SP Flash Tool?
Of course yes but the real problem is that the phone is not recognized by the PC and therefore can't load anything ...
Even changing drivers or cables or PC, nothing to do.
DarthJabba9 said:
Ok - but have you tried the Mediatek SP Flash Tool?
Click to expand...
Click to collapse
manu33xtro said:
Of course yes but the real problem is that the phone is not recognized by the PC and therefore can't load anything ...
Even changing drivers or cables or PC, nothing to do.
Click to expand...
Click to collapse
So, when the battery is removed, and you connect the USB cable, the phone is not even vibrating (and making that weird sound) every couple of seconds or so?
Yes you're right : every 10s the phone vibrate...
DarthJabba9 said:
So, when the battery is removed, and you connect the USB cable, the phone is not even vibrating (and making that weird sound) every couple of seconds or so?
Click to expand...
Click to collapse
manu33xtro said:
Yes you're right : every 10s the phone vibrate...
Click to expand...
Click to collapse
Well, then it is very strange that you can't use the SP Flash Tool. If the phone vibrates, then the device is recognised, and you should be able to flash anything you want with the SP Flash Tool! How exactly were you trying to use the Flash Tool?
I tried so many solutions I really don't know exactly how I used the software.
I will again try everything.
But against any changes when I look in the USB settings of the PC, the phone doesn't appear.
I try again just now, thank you for your help.
DarthJabba9 said:
Well, then it is very strange that you can't use the SP Flash Tool. If the phone vibrates, then the device is recognised, and you should be able to flash anything you want with the SP Flash Tool! How exactly were you trying to use the Flash Tool?
Click to expand...
Click to collapse
manu33xtro said:
I tried so many solutions I really don't know exactly how I used the software.
I will again try everything.
But against any changes when I look in the USB settings of the PC, the phone doesn't appear.
I try again just now, thank you for your help.
Click to expand...
Click to collapse
With the SP Flash Tool, all you need is the correct "scatter" file (MT6795_Android_scatter.txt), and the image(s) that you want to flash. If the phone is vibrating, then the SP Flash Tool should be able to connect to it when you click "Download". Just make sure that you first untick everything that you do NOT want to flash. I would try flashing the boot image (boot.img) first. If that succeeds, then try the TWRP recovery image.
Ok. I'm going to try again with "http://en.miui.com/forum.php?mod=viewthread&tid=196175&highlight=sp%2Btool%2Bflash%2Bredmi%2Bnote%2B2"
DarthJabba9 said:
With the SP Flash Tool, all you need is the correct "scatter" file (MT6795_Android_scatter.txt), and the image(s) that you want to flash. If the phone is vibrating, then the SP Flash Tool should be able to connect to it when you click "Download". Just make sure that you first untick everything that you do NOT want to flash. I would try flashing the boot image (boot.img) first. If that succeeds, then try the TWRP recovery image.
Click to expand...
Click to collapse
Well... Install again drivers MTK but nothing... The phone vibrates well but the PC still doesn't see ... It's late now, I look again tomorrow night.
Thanks again.
manu33xtro said:
Ok. I'm going to try again with "http://en.miui.com/forum.php?mod=viewthread&tid=196175&highlight=sp%2Btool%2Bflash%2Bredmi%2Bnote%2B2"
Click to expand...
Click to collapse
manu33xtro said:
Well... Install again drivers MTK but nothing... The phone vibrates well but the PC still doesn't see ... It's late now, I look again tomorrow night.
Thanks again.
Click to expand...
Click to collapse
Perhaps you might want to describe what exactly happens when do you what exactly?
Hi,
Ok that's what I do with an old PC with Win XP.
- install media Tek USB VCOM drivers for Win XP -> installation complete
- launch SP Flash Tool with administrator rights)
- use scatter file from Redmi Note 2 rom
- use download agent "MTK_AllInOne_DA.bin"
- press download button
- connect phone with UCB cable and waiting... and waiting...
- and I can't see it in device manager !
No way again !
I will try again...
DarthJabba9 said:
Perhaps you might want to describe what exactly happens when do you what exactly?
Click to expand...
Click to collapse
manu33xtro said:
Hi,
Ok that's what I do with an old PC with Win XP.
- install media Tek USB VCOM drivers for Win XP -> installation complete
- launch SP Flash Tool with administrator rights)
- use scatter file from Redmi Note 2 rom
- use download agent "MTK_AllInOne_DA.bin"
- press download button
- connect phone with UCB cable and waiting... and waiting...
- and I can't see it in device manager !
No way again !
I will try again...
Click to expand...
Click to collapse
Strange! I am assuming that when you connect the phone with the USB cable, the battery has been removed from the phone? If so, then it should work.
Perhaps you should try first connecting the phone, and then waiting until it has vibrated once or twice, before clicking the "Download" button?
Yes I removed battery before connect the phone to PC. I tried also with battery and nothing changed.
I even changed the cable to be sure.
Which seems to me most strange is that I see nothing in the device manager, as if the phone wasn't connected. Whatever the installed driver is the same result. I think it should at least have the phone on the COM or USB port ...
I will try again this night to be sure with all steps one by one. And I will also try with ACER tablet I and runs Android 5.1. Maybe it will be recognized.
Otherwise I also tried to pass a Linux PC as a last resort.
Thanks again for your help.
DarthJabba9 said:
Strange! I am assuming that when you connect the phone with the USB cable, the battery has been removed from the phone? If so, then it should work.
Perhaps you should try first connecting the phone, and then waiting until it has vibrated once or twice, before clicking the "Download" button?
Click to expand...
Click to collapse
manu33xtro said:
Yes I removed battery before connect the phone to PC. I tried also with battery and nothing changed.
I even changed the cable to be sure.
Which seems to me most strange is that I see nothing in the device manager, as if the phone wasn't connected. Whatever the installed driver is the same result. I think it should at least have the phone on the COM or USB port ...
Click to expand...
Click to collapse
Yes, it should. The fact that the phone vibrates when connected indicates that the PC and phone are communicating - but it may well be that a low-level driver in the phone has been overwritten (which may mean that this is a lost cause). A final idea - can miui recovery access usbotg?
Hum good question. In fact I don't know. I'll ask the MIUI forum.
I got home late from work so I don't do tests tonight, I'd see it all tomorrow including the connection with my tablet ...
Thanks
DarthJabba9 said:
Yes, it should. The fact that the phone vibrates when connected indicates that the PC and phone are communicating - but it may well be that a low-level driver in the phone has been overwritten (which may mean that this is a lost cause). A final idea - can miui recovery access usbotg?
Click to expand...
Click to collapse
Hi,
I tried to connect with an Acer Tablet with Android 5.1.1 but nothing appends...
I tried also with a Linux PC (Debian) and if I can see a Samsung A3 phone dirrectly, no way for my Redmi Note 2...
There really I despair : I think I can't access any of the phone. Can't do anything !
If you have any other solution but you help me a lot already, and thanks for that.
Can be a micro crack on the USB plug into the phone if it's not a software problem ... Let's go for it apart and look at this ...
Thanks again bro.
Manu
DarthJabba9 said:
Yes, it should. The fact that the phone vibrates when connected indicates that the PC and phone are communicating - but it may well be that a low-level driver in the phone has been overwritten (which may mean that this is a lost cause). A final idea - can miui recovery access usbotg?
Click to expand...
Click to collapse
manu33xtro said:
Hi,
I tried to connect with an Acer Tablet with Android 5.1.1 but nothing appends...
I tried also with a Linux PC (Debian) and if I can see a Samsung A3 phone dirrectly, no way for my Redmi Note 2...
There really I despair : I think I can't access any of the phone. Can't do anything !
If you have any other solution but you help me a lot already, and thanks for that.
Can be a micro crack on the USB plug into the phone if it's not a software problem ... Let's go for it apart and look at this ...
Thanks again bro.
Manu
Click to expand...
Click to collapse
I don't think it is a crack on the USB plug. It seems to me to be a low-level driver problem - ie, the drivers on the phone that are active when the phone is not (fully) booted up. I don't have the right terminology for these drivers, but they are possibly part of the bootloader. If that is the problem, then I don't know how you would solve this problem.
Hi, i bought power 2, phone not open and noting happen when press power or vol+ - together + power, or ....try everything
Bricked when try flash twrp recovery. later i try flash rom again, my computer see phone when phone is closed. can not open already. But now my computer not see the phone:A request for the USB device descriptor failed.
What can i do, and sorry for my english
This phone can't be bricked (mostly). You can easily restore the stock firmware, just download stock rom from official site, extract it. And use sp flash tool not the one that comes with the official rom. Open sp flash tool.
Load scatter file from official rom, you can leave the DA file for all mtk phones that comes with stock rom or use the one in sp flash tool (just leave it as it is) in the user interface of sp flash tool.
Make sure it says "download only" from the drop box. Click download then connect the phone to your computer. Flashing will start and should take about 1 minute and 30 seconds to finish.
If flashing doesn't start. Make sure you have vcom drivers installed. (Also for flashing to start, phone must be turned off obviously, but since you have semi brick, you don't have to worry about that).
Rebel_X said:
This phone can't be bricked (mostly). You can easily restore the stock firmware, just download stock rom from official site, extract it. And use sp flash tool not the one that comes with the official rom. Open sp flash tool.
Load scatter file from official rom, you can leave the DA file for all mtk phones that comes with stock rom or use the one in sp flash tool (just leave it as it is) in the user interface of sp flash tool.
Make sure it says "download only" from the drop box. Click download then connect the phone to your computer. Flashing will start and should take about 1 minute and 30 seconds to finish.
If flashing doesn't start. Make sure you have vcom drivers installed. (Also for flashing to start, phone must be turned off obviously, but since you have semi brick, you don't have to worry about that).
Click to expand...
Click to collapse
Vdcom drivers already installed but not using. becouse computer does not see phone.
Unknown usb device . A request for the USB device descriptor failed. (code 43)
if i solve this, maybe i can flash rom
Rebel_X said:
This phone can't be bricked (mostly). You can easily restore the stock firmware, just download stock rom from official site, extract it. And use sp flash tool not the one that comes with the official rom. Open sp flash tool.
Load scatter file from official rom, you can leave the DA file for all mtk phones that comes with stock rom or use the one in sp flash tool (just leave it as it is) in the user interface of sp flash tool.
Make sure it says "download only" from the drop box. Click download then connect the phone to your computer. Flashing will start and should take about 1 minute and 30 seconds to finish.
If flashing doesn't start. Make sure you have vcom drivers installed. (Also for flashing to start, phone must be turned off obviously, but since you have semi brick, you don't have to worry about that).
Click to expand...
Click to collapse
My phone opened, but computer cannot see storage.i think phone's usb ports damaged. i can flash rom with sp flash tool only.
fastboot and recovery not working. i cant make root too. what can i do i dont know. recovery cant open, writing "no command".
faysoft said:
My phone opened, but computer cannot see storage.i think phone's usb ports damaged. i can flash rom with sp flash tool only.
fastboot and recovery not working. i cant make root too. what can i do i dont know. recovery cant open, writing "no command".
Click to expand...
Click to collapse
Go to developer mode menu (if you don't have it, tap on "build number" in "about phone" from settings, seven times and it will be activated). Then change how your USB acts when connected with computer.
If you can't, just use ES File explorer to send files between your computer and phone in FTP or SMB mode over WiFi.
Have the same problam.
The pc recognize the vcom device but only for 2-3 secconds and then disaper, then i get an error with sp flashtool.
Phone isnt tured on. At all.
I also have the same problem.
Is anyone has success with unbricking Power II in such case?
pacmancoder said:
I also have the same problem.
Is anyone has success with unbricking Power II in such case?
Click to expand...
Click to collapse
I do not know if it is late. I had the same problem with another phone. I was solved as follows:
1. Unplug the usb cable from the computer
2. Power off the phone
3. Press download on sp flash tool
4. Holding vol+ and power, plug the usb cable on the computer.
Hi,
can anyone provide me with nvram /nvdata backup please of Ulephone power 2?
I have probably correct IMEI, valid MAC fo Wifi/BT ...
It looks like my serial number changed to 123456789ABCDEF and I have no idea how to change it to original because MAUI (?) stucked on get kernel
I can find original box with correct serial and IMEis on stick
The only one problem with mobile is I am not able connect to mobile network - registration SIM to mobile network always fail.
and at MTK engineer I have only Bluetooth, FM Receiver, Wifi, Wifi CTIA, Wifi Display
I have nothing like Radio, CDS etc ...
OEM unlocked, TWRP, rooted
Some information probably lost when flashing
And of course another problem :
except GPS and proximity, all sensors does not work - G sensor, acceleration, magnetic sensor, compass . Probably configuration data is located at nvdata
i tried flash 5MB file nvdata.bin from different MTK 675x device, but nothings change
I tried flash 33 MB nvdata.img from same MTK 675x device, but I lost IMEI and nothing solved
This is why I need 33 MB NVDATA.IMG from another functional Ulephone power 2
I can change IMEI at MTK then ...
I had to flash , because phone was unusable - it stucked mostly on obtaining IP address wifi
after a while, phone disconnected from wifi and cant find any wifi or if find, then cant connect because of some security issue , after restart all was OK ...
Thanks