Related
Hi,
So I just purchased a Samsung Galaxy S II, and I've been trying a few different ROM's found on this site. The last thing I did was actually revert back to a stock Samsung Kernel and firmware. This worked fine, but it unrooted my device, which I knew would happen, but now I'm not able to root it again because when I put the device into download mode, ODIN, or better yet, my computer won't detect the device.
I have all the drivers installed, and I also deleted them all, and Kies, and started from scratch again after searching XDA for similar issues.
I don't believe this to be a driver issue, since I was able to root my device, and swap roms before I went back to the official kernel and firmware. I'm with Bell in Canada, so the versions I went back to were not the official Bell versions, since Samsung has not made them available.
I have a Mac, but I've been using Windows 7 and Odin under VMWare. I can connect my device to either OSX, or Windows 7 when the device is not in download mode, and everything works fine, and Odin detects the device (Not that that does any good of course)
When I connect the device under download mode, the Mac detects the device and asks me if I want to connect it to my Mac, or to Windows (As it should) but no matter which one I select, neither OS acknowledges the device after that point, where as when I'm not in Download mode, both OS's detect the device fine.
After all my troubleshooting with my computer based off of what I found online here, The only conclusion I have left is that there is something missing on the device that allows it to be found under download mode, but that aspect of all this is beyond my current skill level.
Anyone have any ideas?
Are you pressing the Volume Up button to continue in Download mode? Besides, Virtual machine isn't recommended I think.
Yes, Once the Custom ROM warning comes up, I press the Volume up button to continue.
That wasn't even necessary on the Stock Bell ROM. The warning didn't come up at all.
VM has been working fine up until now, so I don't think that's the problem, but I have been thinking of trying this on my old laptop that runs on windows if nothing else pans out.
Scott56 said:
Yes, Once the Custom ROM warning comes up, I press the Volume up button to continue.
That wasn't even necessary on the Stock Bell ROM. The warning didn't come up at all.
VM has been working fine up until now, so I don't think that's the problem, but I have been thinking of trying this on my old laptop that runs on windows if nothing else pans out.
Click to expand...
Click to collapse
Have you found anyway to Make Odin recognize to phone in download mode?? Im still struggling with that. my phone is on stock kernel and not rooted yet, ODIN finds it fine when the phone is on and USB Debugging is on, but once I put the phone on download mode it wont recognize it, I dont know why..
Could it be because of the ''SAMSUNG Mobile MTP Device'' driver failed to install correctly??
all other drivers are installed correctly.. I have tried to get the driver mentioned above to install correctly but it fails every time, with USB debugging on and off, i have wiped the phone and installed Kies and the drivers several times, Im clueless right.. anyone have any idea please help??
I myself am also suffering from this problem. However, USB seems to function fine while the phone is booted up or in recovery (For ADB). I'm wondering if necessary files may have become corrupted or deleted in reference to USB drivers (phone side mind you) that are used in download mode.
edit: It's also recognized in recovery mode.
Even if it can't be fixed I'd still like to understand why.
-Simply D
was looking for help on this and saw this thread, same problem too..
Connects to Odin and Kies fine when switched on "normally", can use USB mass storage mode Etc.
comes up with a USB device has malfunctioned message on PC when I connect USB cable when switched on and in download mode
EDIT:- just to add, if I try upgrading firmware via Kies it gets to the point where it switches the phone to download mode to upgrade it and has the same issue even with an official upgrade
Figuring download mode is outside the normal boot procedure, I hoped on an off chance that pulling my battery and sim for a few minutes would reset it. It did indeed. Download mode is now functional again, just to be certain I tested it right before pulling the battery to make sure it was still broken. And multiple flashes and reboots afterwards seem to confirm that it has returned to normal.
Anyone else who solves it with this method, please report back.
-Simply D
SimplyD said:
Figuring download mode is outside the normal boot procedure, I hoped on an off chance that pulling my battery and sim for a few minutes would reset it. It did indeed. Download mode is now functional again, just to be certain I tested it right before pulling the battery to make sure it was still broken. And multiple flashes and reboots afterwards seem to confirm that it has returned to normal.
Anyone else who solves it with this method, please report back.
-Simply D
Click to expand...
Click to collapse
Tried this and it didn't work for me :/ going to give it another try later, thanks for the suggestion either way
I am completely new to this so bear with me. I am trying to root my samsung fascinate. What are the steps i need to take to do so?
http://forum.xda-developers.com/showthread.php?t=1238070
Refer to section 5
http://bit.ly/uLiskn
Use guide by Droidstyle......nuff said
Sent from my SCH-I500 using XDA App
I have been able to do this on my wife's phone pretty easy and all I do it find a copy if CWM recovery (often called CWM all), a copy of update.zip, and the latest version if Odin. Use your factory USB cord and plug your phone into your PC. Let it install all the drivers. Once I stalled open your phone and mount the SD card so you can see it as a hard drive. Place the update.zip file on the SD card, but not in any folder. From there unhook your phone and power it down. Remove the battery and start Odin. Plug your USB part of the phone cord into the PC (don't connect it to the phone yet). Hold down the volume down button and power button while connecting the phone cord to the phone. You will see a yellow triangle and Droid on the screen. From there click the PDA button and find the CWM file you downloaded. Click start and let it do its thing. The phone will power down and you can then replace the battery and start your phone. I usually let my phone power up and then power it down again. After it is off you will then need to hold the volume up, volume down, and power button to boot into recovery. Once in Recovery you can choose the option to install update.zip. Let it do its thing and then reboot the phone. You should be good to go.
icemanwbs said:
Use guide by Droidstyle......nuff said
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Sent from my SCH-I500 using XDA App
zander78 said:
http://bit.ly/uLiskn
Click to expand...
Click to collapse
LMAO... you crack me up man.
millwood said:
I have been able to do this on my wife's phone pretty easy and all I do it find a copy if CWM recovery (often called CWM all), a copy of update.zip, and the latest version if Odin. Use your factory USB cord and plug your phone into your PC. Let it install all the drivers. Once I stalled open your phone and mount the SD card so you can see it as a hard drive. Place the update.zip file on the SD card, but not in any folder. From there unhook your phone and power it down. Remove the battery and start Odin. Plug your USB part of the phone cord into the PC (don't connect it to the phone yet). Hold down the volume down button and power button while connecting the phone cord to the phone. You will see a yellow triangle and Droid on the screen. From there click the PDA button and find the CWM file you downloaded. Click start and let it do its thing. The phone will power down and you can then replace the battery and start your phone. I usually let my phone power up and then power it down again. After it is off you will then need to hold the volume up, volume down, and power button to boot into recovery. Once in Recovery you can choose the option to install update.zip. Let it do its thing and then reboot the phone. You should be good to go.
Click to expand...
Click to collapse
Hi Guys-
I'm having a problem with my Samsung Fascinate as well. Its currently running Gingerbread 2.3.5 build EH03. I had my phone flashed to MetroPCS a couple of days ago with Talk/Text only. Now I'm trying to root my phone using Odin. I want to install CyanogenMod, because I ran it on my old HTC Hero and was satisfied with it.
The problem is that my phone will not mount as a USB Storage. I'm using a Mac, however I have Parallels running Windows XP SP3. I have installed the Samsung drivers from the Samsung website and the drivers do show up in the device manager, but it still doesn't mount as a USB storage device in Windows. On the phone I receive the notification that its USB Connected - select to copy files to/from your computer. But, again nothing happens when I select it.
Whenever I plug my phone in the USB port Odin recognizes it, but when I put the phone into download mode it doesn't show up in Odin. I've also tried to see if it shows up using ADB from the Android SDK. Its not listed as a device when I run the command adb devices.
Is there anyway to root the phone if its not showing up in Odin when its download mode?
stevebanks said:
Hi Guys-
I'm having a problem with my Samsung Fascinate as well. Its currently running Gingerbread 2.3.5 build EH03. I had my phone flashed to MetroPCS a couple of days ago with Talk/Text only. Now I'm trying to root my phone using Odin. I want to install CyanogenMod, because I ran it on my old HTC Hero and was satisfied with it.
The problem is that my phone will not mount as a USB Storage. I'm using a Mac, however I have Parallels running Windows XP SP3. I have installed the Samsung drivers from the Samsung website and the drivers do show up in the device manager, but it still doesn't mount as a USB storage device in Windows. On the phone I receive the notification that its USB Connected - select to copy files to/from your computer. But, again nothing happens when I select it.
Whenever I plug my phone in the USB port Odin recognizes it, but when I put the phone into download mode it doesn't show up in Odin. I've also tried to see if it shows up using ADB from the Android SDK. Its not listed as a device when I run the command adb devices.
Is there anyway to root the phone if its not showing up in Odin when its download mode?
Click to expand...
Click to collapse
no...you need odin to flash cwm recovery so you can three finger into that recovery to flash the superuser.zip
Try another Pc!
stevebanks said:
Hi Guys-
I'm having a problem with my Samsung Fascinate as well. Its currently running Gingerbread 2.3.5 build EH03. I had my phone flashed to MetroPCS a couple of days ago with Talk/Text only. Now I'm trying to root my phone using Odin. I want to install CyanogenMod, because I ran it on my old HTC Hero and was satisfied with it.
The problem is that my phone will not mount as a USB Storage. I'm using a Mac, however I have Parallels running Windows XP SP3. I have installed the Samsung drivers from the Samsung website and the drivers do show up in the device manager, but it still doesn't mount as a USB storage device in Windows. On the phone I receive the notification that its USB Connected - select to copy files to/from your computer. But, again nothing happens when I select it.
Whenever I plug my phone in the USB port Odin recognizes it, but when I put the phone into download mode it doesn't show up in Odin. I've also tried to see if it shows up using ADB from the Android SDK. Its not listed as a device when I run the command adb devices.
Is there anyway to root the phone if its not showing up in Odin when its download mode?
Click to expand...
Click to collapse
I think you can root the phone without having to flash CWM recovery, but it does require ADB so I don't know if that would be any help. FWIW, I have a mac too, and haven't had any luck using heimdall (it doesn't recognize the device), although I haven't tried any sort of VM or anything like crossover to use odin on it. I've just accepted using a windows machine when odin is required
Does your ADB work with other devices? For whatever reason, I couldn't get it working with the fascinate, then I tried it a few days ago and it worked all of a sudden. Another workaround is to use the wirelessADB app from the market. If you search for "galaxy s mac" you'll see that you're unfortunately definitely not alone in having connectivity issues with OSX.
k_nivesout said:
I think you can root the phone without having to flash CWM recovery, but it does require ADB so I don't know if that would be any help. FWIW, I have a mac too, and haven't had any luck using heimdall (it doesn't recognize the device), although I haven't tried any sort of VM or anything like crossover to use odin on it. I've just accepted using a windows machine when odin is required
Does your ADB work with other devices? For whatever reason, I couldn't get it working with the fascinate, then I tried it a few days ago and it worked all of a sudden. Another workaround is to use the wirelessADB app from the market. If you search for "galaxy s mac" you'll see that you're unfortunately definitely not alone in having connectivity issues with OSX.
Click to expand...
Click to collapse
very true...ADB is another option to root, but I never recomend it because most folks will have trouble using it....dont mean the in a condescending way, just sayin.
For sure, just thought I would throw it out there. Looks fairly simple actually from the guide nitsuj17 posted in the OP of the EH03 odin/heimdall package, well maybe straightforward would be a better word, just since it's laid out step-by-step.
I actually had problems using cwm... it failed to flash the su.zip properly. So I used the latest version of GeeWiz recovery on stock EH03. Worked fine. Roots every time. #hopethathelps
Sent from my SCH-I500 using xda premium
There is a thread with a stock root with voodoo lag fix and ROM manager. Step by step instructions as well.
Sent from my SGH-T959P using xda premium
cant install roms
Hi, guys new to rooting and custom roms but ive hit a snag.
I have acheived root by using section 5 here (http://forum.xda-developers.com/showthread.php?t=1238070)
but i cannot install any roms all i get when i select the zip file is a screen that shows the unpacking then it goes to a triangle with an exclamation point. then reboots into normal android loosing everything i had installed. i made a backup using rom manager but it has dissapeared so now i have nothing to lose. can anyoone help.
all i want to be able to do is put ics with very few apps and overclock my cpu
Any help would be great
Samsung fascinate running android2.3.5 with superuser
thx
1. You don't need to be root first before flashing roms.
2. It sounds like you're possibly booting into the stock recovery.
If you want to flash ICS, just follow the steps in that section 3 of the guide you've already been using.
I tried but it failed on step 9/10
So you're saying that it fails after you press start in odin (flashing the stock EH03 package)? What error are you getting and when exactly is it happening?
If you're not on any rom and just on stock EH03, I'd think you should be able to just odin the CWM recovery and install ICS from there.
not sure what the exact message was but yes after i hit start it initalized did nothing for about 3 minutes of the five and got a fail message
And you're sure you're using the correct files and selecting the right things in odin? Make sure the stock EH03 rom is in the PDA section, the atlas 2.2 file for PIT, and repartition is checked. Could possibly be a bad download too, I'd maybe try redownloading the files and trying again. Also, are you using Odin 1.3 that was linked in the guide?
Alternatively, you could just try flashing the CWM4 fixed for CM7 in odin, then three-finger into recovery and flash ICS from there.
Oh and just making sure you're getting into download mode the right way, I personally pull the battery, that way it doesn't reboot after you flash whatever it is you're flashing. If none of that works, I'd try a different USB port/cable. Is odin recognizing the device properly?
I really Need Help! My computer wont recognize my tablet in fastboot mode, and my tablet wont read my micro SD card, also when i turn it on normally it stays at splash screen and when its plugged in to the computer the computer starts installing the drivers and it fails to install each time. I go to troubleshooting options and it states code 10. which states device cannot start.
I Have looked for ways around this, like manually installing the drivers, and my computer wont let me. Also the tablet can go to both: bootloader, and Clockworkmod recovery.
I factory reset my tablet so I cannot install anything, untill i get it to connect to my computer.
I am running Windows 7 64-bit on my computer!
Any help is very much appreciated!
Thanks!
NewDev4IOS said:
I really Need Help! My computer wont recognize my tablet in fastboot mode, and my tablet wont read my micro SD card, also when i turn it on normally it stays at splash screen and when its plugged in to the computer the computer starts installing the drivers and it fails to install each time. I go to troubleshooting options and it states code 10. which states device cannot start.
I Have looked for ways around this, like manually installing the drivers, and my computer wont let me. Also the tablet can go to both: bootloader, and Clockworkmod recovery.
I factory reset my tablet so I cannot install anything, untill i get it to connect to my computer.
I am running Windows 7 64-bit on my computer!
Any help is very much appreciated!
Thanks!
Click to expand...
Click to collapse
Did you install the naked driver from here? http://forum.xda-developers.com/showthread.php?t=1426502 if not do that first once you get that working... then you should be able to fastboot to the pc... next thing I would concider is going to twrp recovery instead of cwm....either go for an older version or go the full gambit of nvflash then install the latest twrp... after that you should be set.....I can comment more on it if you need it....
Bricked Tablet Help
Gage_Hero said:
Did you install the naked driver from here? http://forum.xda-developers.com/showthread.php?t=1426502 if not do that first once you get that working... then you should be able to fastboot to the pc... next thing I would concider is going to twrp recovery instead of cwm....either go for an older version or go the full gambit of nvflash then install the latest twrp... after that you should be set.....I can comment more on it if you need it....
Click to expand...
Click to collapse
I tried installing those drivers but it didnt work
also i used WSG_Unbricker v.1.0.3
my system is wiped
is there any way to install the operating system on it
i need a link for an update.zip
thanks
i can now only go to fastboot mode and wipe data mode.
NewDev4IOS said:
I tried installing those drivers but it didnt work
also i used WSG_Unbricker v.1.0.3
my system is wiped
is there any way to install the operating system on it
i need a link for an update.zip
thanks
i can now only go to fastboot mode and wipe data mode.
Click to expand...
Click to collapse
What do you see in device manager with the tablet plugged into the pc and running in fastboot?
Maybe this helps
I had a similar issue but my tablet couldn't be identified by windows, at first i thought it was my drivers so i tried to install new ones but windows wouldn't let me stating the same code 10. At the end it was a defective usb cable, i bought a new one and everything worked all right the first time i plugged it in. And by the way i was stucked at the CWM loop. Hope this helps and sorry for my bad english.
Bricked tablet
sj010489 said:
I had a similar issue but my tablet couldn't be identified by windows, at first i thought it was my drivers so i tried to install new ones but windows wouldn't let me stating the same code 10. At the end it was a defective usb cable, i bought a new one and everything worked all right the first time i plugged it in. And by the way i was stucked at the CWM loop. Hope this helps and sorry for my bad english.
Click to expand...
Click to collapse
Thanks
Im not sure if it is a bad usb cable, i think it is my computer because my computer doesnt even recognize my iphone and i have itunes installed,
i think it is partially due to a funky computer for me.
BRICKED
Gage_Hero said:
What do you see in device manager with the tablet plugged into the pc and running in fastboot?
Click to expand...
Click to collapse
It says fastboot
I sent my tablet in to asus
just waiting on them to reply
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 all. I have been racking my brain for days and reading a billion posts and guides to no avail. I have flashed many a phone and have never had an issue until now. I have an SGH-I717 from AT&T unlocked and being used on T-Mobile. I was attempting to either go to a stripped Rom or Stock Rom to get rid of AT&T software. Well I noticed a couple of 4.3 Roms I had not tried before, I was currently on 4.0.4 stock rooted. So I started up CWM touch and started firing away, first Rom started acting strange with the screen coming on out of standby, so I decided to try the next one. Seemed awesome at first. Then I rebooted the phone after a couple of app installs. Boom, would not turn on. Blank screen, not responding to power button. Would go to CWM and Download mode. Hmm. Started fiddling, couldn't get Kies firmware recovery to get past 0%, tried Odin 1.83, 1.85 3.07 3.09, it kept crashing at getting pit for mapping. Windows 7 X64 pro, Was able to load a backup with cwm after copying through adb to internal sd. Didn't want that, attempted to flash again. Same thing. Got to adb with CWM up. Manually wrote 3e recovery to phone, bad idea. Now i can't do anything. Can't access the external sd to try and update.zip, can't get to adb no matter what, either drivers fail to install, hardware id missing, or some other nonsense. I tried an ubuntu 12 machine, windows xp (physical and virtual) several cables, and several windows 7 machines. All with similar results, linux won't recognize the phone through adb but will with lsusb and udev. I can get windows to recognize in factory mode, not odin mode, and odin will read the com port, but crashes on every machine at the pit phase. I tried heimdall and it complains that I don't have a matchine pit and I tried one that i found online and it is unable to write the pit file and just reboots the phone. I have been unable to manually flash anything from any point. Is there anything any of you can think of that I can try? I have heard of JTag and don't know much about it but read somewhere someone using and Arduino to do that, I have an arduino but its sound difficult due to size of the interface plug. Please help, phoneless and scared!!!
Since a Windows pc recognizes a lil bit, I would try using kies software and perform an emergency recovery.
Thanks for the reply
I entered the model SGH-I717 and then the S/N, tried this about 10 times with different cables and different Windows versions. Sticks at 0% after unpacking binary files. Stays there for a long time before failing and saying that it couldn't recognize the phone.
440bro said:
Since a Windows pc recognizes a lil bit, I would try using kies software and perform an emergency recovery.
Click to expand...
Click to collapse
Try ATT-I717
I will try that this evening thanks.
rangercaptain said:
Try ATT-I717
Click to expand...
Click to collapse
Updated Question
I have an arduino, is there any way without building a jtag interface or using a riff box to send some data to the phone through some of the pins directly and force it to accept adb commands or to push a file or some such? One thing to note on the 3e recovery I can see the filesystem and of course i did a factory reset so there is nothing there of use to me, however why won't the microsd card mount in stock recovery is that normal? Dummy me I had TWRP on it, then flashed CWM, and then manually used dd to write the stock back to it thereby making it difficult to do anything because 3e sucks. When I get home I'm going to try the OneClickUnbrick jar and see what that does. I have never tried it. There has to be a way to send data or arbitrary commands to the phone through the usb to force it to do what I want, isn't there a be my ***** adapter or something I can hook up to this paperweight?
One0f4K1nd said:
Hello all. I have been racking my brain for days and reading a billion posts and guides to no avail. I have flashed many a phone and have never had an issue until now. I have an SGH-I717 from AT&T unlocked and being used on T-Mobile. I was attempting to either go to a stripped Rom or Stock Rom to get rid of AT&T software. Well I noticed a couple of 4.3 Roms I had not tried before, I was currently on 4.0.4 stock rooted. So I started up CWM touch and started firing away, first Rom started acting strange with the screen coming on out of standby, so I decided to try the next one. Seemed awesome at first. Then I rebooted the phone after a couple of app installs. Boom, would not turn on. Blank screen, not responding to power button. Would go to CWM and Download mode. Hmm. Started fiddling, couldn't get Kies firmware recovery to get past 0%, tried Odin 1.83, 1.85 3.07 3.09, it kept crashing at getting pit for mapping. Windows 7 X64 pro, Was able to load a backup with cwm after copying through adb to internal sd. Didn't want that, attempted to flash again. Same thing. Got to adb with CWM up. Manually wrote 3e recovery to phone, bad idea. Now i can't do anything. Can't access the external sd to try and update.zip, can't get to adb no matter what, either drivers fail to install, hardware id missing, or some other nonsense. I tried an ubuntu 12 machine, windows xp (physical and virtual) several cables, and several windows 7 machines. All with similar results, linux won't recognize the phone through adb but will with lsusb and udev. I can get windows to recognize in factory mode, not odin mode, and odin will read the com port, but crashes on every machine at the pit phase. I tried heimdall and it complains that I don't have a matchine pit and I tried one that i found online and it is unable to write the pit file and just reboots the phone. I have been unable to manually flash anything from any point. Is there anything any of you can think of that I can try? I have heard of JTag and don't know much about it but read somewhere someone using and Arduino to do that, I have an arduino but its sound difficult due to size of the interface plug. Please help, phoneless and scared!!!
Click to expand...
Click to collapse
adb.exe works when the phone is in download mode. If you can get into 3e recovery you can factory reset. That usually clears up some issues.
I would try the reset, then go to a virgin pc running win 7 - the drivers are already in that os.
Connect with phone in download mode, run odin3 1.85 as administrator, flash a stock rom.