I was flashing my Vibrant back to the stock ROM using ODIN, and it seemed to have shut off during the procedure. I've used ODIN several times beforehand, but I never had any issues with it, until now. Upon booting my vibrant i was presented with an unusual looking semi-brick screen. After a bit of research, I found out that there was a program, developed by Adam Outler, that supposedly would be the solution to this issue. Though, once it was installed, another issue arose. The Vibrant was not recognized by my laptop. Is there any possible solutions to my dilemma? I would greatly appreciate any support that can be provided
Below is a link an image of the screen that i am currently stuck on
i1209.photobucket.com/albums/cc398/jjjhhhppp/scan.jpg
This is a soft brick. Easily fixable. Go into my Miui guide, link in signature, and go to post two. The answer is there.
As for your phone not being recognized download a program called "Samsung Kies". Once installed it will automatically reinstall your drivers.
Sent from my SGH-T959 (Samsung Vibrant)
Installing Samsung Kies did not solve the issue, my phone is still not visible within Device Manager, ODIN is unable to find phone, Heimdall is unable to find the phone, Zadig states "0 devices found" even when the phone is connected, and finally, One-Click UnBrick gives me Unspecified Errors every time I try to run "unsoft brick"
Try to download the AIO Toolbox and reinstall the drivers that way. Then go back to NOOB's guide, post 2 and try again. Your image and his image has a striking similarity.
Also remember "You don't necessarily need the download mode image to be present. As long as you are getting the COM ID to light up yellow in ODIN, just flash back to stock like normal."
Ok, so after installing AIO toolbox and following NOOB's guide, still, my phone is not listed under ID:COM in ODIN, and it does not appear in device manager aswell. (Usually in device manager I would see "Gadget Serial", "Samsung USB Composite Device", "ADB Interface", "Samsung Mobile Modem 2", or something similar when the phone is connected)
jjjhhhppp said:
Ok, so after installing AIO toolbox and following NOOB's guide, still, my phone is not listed under ID:COM in ODIN, and it does not appear in device manager aswell. (Usually in device manager I would see "Gadget Serial", "Samsung USB Composite Device", "ADB Interface", "Samsung Mobile Modem 2", or something similar when the phone is connected)
Click to expand...
Click to collapse
Have you tried all of the button combinations for a forced download mode? I have nearly hard bricked once beofre, or so i though. My phone wouldnt power on at all, or atleast didnt give me an indication that it was booting. ie. no buttons lighting, etc. your phone is NOT boned. Try pulling the battery and letting it sit for a few minutes..
Once you do that, reinstall the windows drivers. as an added precaution, run odin as an administrator (even in xp). Flashing back to a stock rom probably wouldnt hard brick your pone, as I dont believe the stoc rom writes a new bootloader.
Try this :
1. Plug in USB cable (to PC)
2.Remove battery, simcard, memory card from phone.
3. Hold ONLY vol up/ voldown
4. Plug usb into PHONE.
5. Insert Battery (after inserting battery release the buttons)
6. Lastly, make sure your pc speakers are turned up, listen for the usb connect sound.
LIke i said, you dont have a hard brick. I believe the hard brik will either result in a reboot loop (not in all cases), or a black screen (someone else can chime in ad correct me). Just keep trying, you'll get it.
Related
I might have accidentally bricked my SGS 2. I get a screen saying:
"firmware upgrade encountered an issue. Please select recovery mode in kies and try again"
with a mobile phone and a computer logo with a Yellow triangle in between.
I know abt Rooting and ROM flashing etc and has been doing it for the last couple or years.
I flashed Franklin's XXKG3 Kernels, and before I could flash Chainfire's XXKG3 kernel, the USB ports refused to recognize my handset. I can still go into download mode but the Odin or Samsung Kies etc. won't do nothing.
Keeps saying "USB Device not recognized"
Please help!!!!
leo13aug79 said:
I might have accidentally bricked my SGS 2. I get a screen saying:
"firmware upgrade encountered an issue. Please select recovery mode in kies and try again"
with a mobile phone and a computer logo with a Yellow triangle in between.
I know abt Rooting and ROM flashing etc and has been doing it for the last couple or years.
I flashed Franklin's XXKG3 Kernels, and before I could flash Chainfire's XXKG3 kernel, the USB ports refused to recognize my handset. I can still go into download mode but the Odin or Samsung Kies etc. won't do nothing.
Keeps saying "USB Device not recognized"
Please help!!!!
Click to expand...
Click to collapse
Might help to reinstall KIES or try another computer.
Keeps saying "USB Device not recognized"
USB drivers problem remove Kies totally and reinstall .
Connect in mass storage mode and let windows find drivers .
That fails its broken phone .
jje
you broke your phone.
buy another SGS II
You can always try using a USB JIG to put the phone in download mode.
leo13aug79 said:
Keeps saying "USB Device not recognized"
Click to expand...
Click to collapse
Uninstall the Samsung USB Driver from Control Panel
START/Control Panel/Programs and Features
Select "SAMSUNG USB Driver for Mobile Phones" and then uninstall
reboot your PC and then re-install the Samsung USB Driver from:-
C:\Program Files\Samsung\Kies\USB Driver
and run "SAMSUNG_USB_Driver_for_Mobile_Phones.exe"
Doing that will make sure there is no USB driver corruption.
"firmware upgrade encountered an issue. Please select recovery mode in kies and try again"
Click to expand...
Click to collapse
I had the same problem on my SGS4g after updating to a leaked 2.3.4 rom, which would not make phone calls. Tried to use heidmall to downgrade by loading a new rom. After installing the usb driver as described here http://forum.xda-developers.com/showpost.php?p=14798367&postcount=1 . After reboot I get the error screen <phone..!..Computer> "firmware upgrade encountered an issue. Please select recovery mode in kies and try again". I then took the following steps.
I came across this site: http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series#Bricked_Screen Under the bricked section it mentions a couple things to try. I the reboot cycle with a couple of times and kept on getting the same screen. Still no go.
I took Odia's advice an did a complete removal of all usb drivers as mentioned and reinstalled kies. This was key in getting odin to recognize the phone again.
My solution:
I try Odin again to try to get it to recognize my phone. I open odin with the usb connected in this state and it is not recognized. I pull battery, it boots to error screen. I restart odin and then plug in the usb and it is recognized. I was then able to load my pit, pda, phone, csc back onto the phone with odin. The first time it tried to load the data it failed, the second time it worked!
Interestingly I never got the "Download Screen". I was still on the mentioned error screen, yet odin was able to still see the phone. The status bar still showed up on the error screen as the fresh rom was being loaded.
I thought I was totally bricked, but this method worked in my case. Hope something similar might work for you.
I still don't know I would get this error screen and have to go through this after loading the required usb driver for heimdall? Any ideas?
OMG! It's WORKING!
Thanks a lot to you all guys for the co-operation....
So, what did I do???? I uninstalled Kies and re-installed a couple of times but it won't access it. Tried Odin in all possible ways, No success. While playing and after ordering a "Jig" from some1 in USA,
I thought of something else and while the phone still being connected with the pc, I ran SuperOneClick, but it went on saying waiting for the device,.... I accidentally or in frustration hit the "HOME" button and it started doing something, USB drivers and Modem drivers installed on PC. Then I started Odin and the port went "Yellow". And I flashed it with the XXKG3.....
OMG! I'm so much relieved!!!!!!!! thanks God
thank you all too
Love your SGS2 and love God! Bless you all!
fvnktion said:
I had the same problem on my SGS4g after updating to a leaked 2.3.4 rom, which would not make phone calls. Tried to use heidmall to downgrade by loading a new rom. After installing the usb driver as described here http://forum.xda-developers.com/showpost.php?p=14798367&postcount=1 . After reboot I get the error screen <phone..!..Computer> "firmware upgrade encountered an issue. Please select recovery mode in kies and try again". I then took the following steps.
I came across this site: http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series#Bricked_Screen Under the bricked section it mentions a couple things to try. I the reboot cycle with a couple of times and kept on getting the same screen. Still no go.
I took Odia's advice an did a complete removal of all usb drivers as mentioned and reinstalled kies. This was key in getting odin to recognize the phone again.
My solution:
I try Odin again to try to get it to recognize my phone. I open odin with the usb connected in this state and it is not recognized. I pull battery, it boots to error screen. I restart odin and then plug in the usb and it is recognized. I was then able to load my pit, pda, phone, csc back onto the phone with odin. The first time it tried to load the data it failed, the second time it worked!
Interestingly I never got the "Download Screen". I was still on the mentioned error screen, yet odin was able to still see the phone. The status bar still showed up on the error screen as the fresh rom was being loaded.
I thought I was totally bricked, but this method worked in my case. Hope something similar might work for you.
I still don't know I would get this error screen and have to go through this after loading the required usb driver for heimdall? Any ideas?
Click to expand...
Click to collapse
I love you man! You saved my phone and me!
So what have we learnt today? Don't go screaming "brick!" everytime you encounter a problem
I had a same issue yellow triangle between Phone and PC symbol...
followed this step .. http://forum.xda-developers.com/showthread.php?t=1274337
just did like this on very first step to get into odin mode hold vol down and power for longer then usual to get into odin mode and by pass that yellow triangle between Phone and PC screen and then follow rest of it same and easy as right clicking on desktop LOL!
From my experience, only true brick I encountered was when I messed with boot loaders. If the screen shows anything at all, Odin will recognize it. Glad to hear it's fixed
Sent from my GT-I9100 using XDA App
Odia said:
Uninstall the Samsung USB Driver from Control Panel
START/Control Panel/Programs and Features
Select "SAMSUNG USB Driver for Mobile Phones" and then uninstall
reboot your PC and then re-install the Samsung USB Driver from:-
C:\Program Files\Samsung\Kies\USB Driver
and run "SAMSUNG_USB_Driver_for_Mobile_Phones.exe"
Doing that will make sure there is no USB driver corruption.
Click to expand...
Click to collapse
I´d tried to upgrade my Infuse SGH-i997 (AT&T) but I did something wrong and now the cell phone no work.
When it turn on says:
"firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
The computer recognize the cell phone but I don´t know what else I can do.
Any suggestion?
Can you get into download mode? If yes then reflash stock firmware using Odin
Sent from my GT-I9100 using Tapatalk
A bricked phone is a phone which will not respond. It maybe a soft brick or hard.
If you can get into download or recovery all you have to do is reflash. Wipe data & Cache. You will be up and running. If your phone is not recognised by your computer then reinstall kies.
Sent from my GT-I9100
Yep. Infuse Q&A (You're in the wrong section).
anjimgo said:
I´d tried to upgrade my Infuse SGH-i997 (AT&T) but I did something wrong and now the cell phone no work.
When it turn on says:
"firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
The computer recognize the cell phone but I don´t know what else I can do.
Any suggestion?
Click to expand...
Click to collapse
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Well, I got this same Firmware upgrade error. I can't get the computer to see it at all. It's almost like the USB port doesn't work anymore. I can get into the download mode but then it ends there. I cannot get into the bootloader at all. If I try, it goes to the error screen and if I boot normally, it goes to the error screen.
Brittlespeed said:
Well, I got this same Firmware upgrade error. I can't get the computer to see it at all. It's almost like the USB port doesn't work anymore. I can get into the download mode but then it ends there. I cannot get into the bootloader at all. If I try, it goes to the error screen and if I boot normally, it goes to the error screen.
Click to expand...
Click to collapse
I can't tell if you're asking for help or just letting people know, but anyway, considering all your previous posts were in the Epic 4G Touch forums, you've probably trashed your device flashing something meant for the I9100.
See this thread for confirmation of your new shiny brick, if my above assumption was correct: http://forum.xda-developers.com/showthread.php?t=1492323
this solution worked for a Galaxy s3 mini
fvnktion said:
I had the same problem on my SGS4g after updating to a leaked 2.3.4 rom, which would not make phone calls. Tried to use heidmall to downgrade by loading a new rom. After installing the usb driver as described here http://forum.xda-developers.com/showpost.php?p=14798367&postcount=1 . After reboot I get the error screen <phone..!..Computer> "firmware upgrade encountered an issue. Please select recovery mode in kies and try again". I then took the following steps.
I came across this site: http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series#Bricked_Screen Under the bricked section it mentions a couple things to try. I the reboot cycle with a couple of times and kept on getting the same screen. Still no go.
I took Odia's advice an did a complete removal of all usb drivers as mentioned and reinstalled kies. This was key in getting odin to recognize the phone again.
My solution:
I try Odin again to try to get it to recognize my phone. I open odin with the usb connected in this state and it is not recognized. I pull battery, it boots to error screen. I restart odin and then plug in the usb and it is recognized. I was then able to load my pit, pda, phone, csc back onto the phone with odin. The first time it tried to load the data it failed, the second time it worked!
Interestingly I never got the "Download Screen". I was still on the mentioned error screen, yet odin was able to still see the phone. The status bar still showed up on the error screen as the fresh rom was being loaded.
I thought I was totally bricked, but this method worked in my case. Hope something similar might work for you.
I still don't know I would get this error screen and have to go through this after loading the required usb driver for heimdall? Any ideas?
Click to expand...
Click to collapse
Thanks a lot. My teenage son thought he had bricked his S3 mini but I was able to fix it after reading this thread. Thanks.
I have been posting (and have had some nice people try to help) in the How to Recover Fascinate from any Brick thread for about a week and can't seem to find a solution. I have also searched the internet high and low looking for a solution with no success. Hopefully someone here has had the same issues and can point me in the right direction.
I rooted the Fascinate using a one click method and was able to get a Titanium backup but could not get into the proper recovery to do a system image. Stupidly, I flashed SP Recovery from within ROM Manager. From that moment on I when the phone is turned on it gets to the "Samsung" screen and locks.
I did my research and found out all I needed to do to fix is install ODIN and reflash the stock ROM again. The problem is that ODIN will not recognize the phone. I start ODIN, pull the phone battery, plug the phone into USB cable, push volume down to get the phone into download mode (Yellow Triangle). I keep getting USB Device Not Recognized errors from Win 7 (64-bit).
I tried installing Heimdall to load the correct drivers but it doesn't see the device either. I can connect my Droid or Droid 2 and Heimdall sees immediately so I know it is not a problem with the software or cable.
I have tried to install the correct USB drivers (even the ones listed on this site). I tried installing Kies and it doesn't see the phone either.
Since the phone is looping at the "Samsung" screen I can't change any settings in the phone as some have suggested. I really do not have any more ideas other that to use this phone as a very expensive door stop. Hopefully, someone here can help. Thanks in advance!!!
pscpa said:
I have been posting (and have had some nice people try to help) in the How to Recover Fascinate from any Brick thread for about a week and can't seem to find a solution. I have also searched the internet high and low looking for a solution with no success. Hopefully someone here has had the same issues and can point me in the right direction.
I rooted the Fascinate using a one click method and was able to get a Titanium backup but could not get into the proper recovery to do a system image. Stupidly, I flashed SP Recovery from within ROM Manager. From that moment on I when the phone is turned on it gets to the "Samsung" screen and locks.
I did my research and found out all I needed to do to fix is install ODIN and reflash the stock ROM again. The problem is that ODIN will not recognize the phone. I start ODIN, pull the phone battery, plug the phone into USB cable, push volume down to get the phone into download mode (Yellow Triangle). I keep getting USB Device Not Recognized errors from Win 7 (64-bit).
I tried installing Heimdall to load the correct drivers but it doesn't see the device either. I can connect my Droid or Droid 2 and Heimdall sees immediately so I know it is not a problem with the software or cable.
I have tried to install the correct USB drivers (even the ones listed on this site). I tried installing Kies and it doesn't see the phone either.
Since the phone is looping at the "Samsung" screen I can't change any settings in the phone as some have suggested. I really do not have any more ideas other that to use this phone as a very expensive door stop. Hopefully, someone here can help. Thanks in advance!!!
Click to expand...
Click to collapse
Control Panel/ User Account/ User Account Control settings- set to- Never notify- restart computer.
Should recognize phone. Reset to default when done and restart. Windows crap!
Thanks but this setting has always been set to "Never Notify"......any other ideas...please
I don't know nothing about it but the guy said " reset to default and restart (again)??
Sent from my SCH-I500 using xda premium
Followed the directions exactly. I think the OP wanted me to reset to default after I was done flashing. This is so strange....I figure if the people on XDA can't figure this out the phone is doomed.
Have you tried a different USB plug on the computer? Or a different USB cord? Or a different computer?
Sent from my SCH-I500 using XDA App
schu9120 said:
Have you tried a different USB plug on the computer? Or a different USB cord? Or a different computer?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I had to use a laptop to access my Fascinate because my desktop wouldnt even show it as unrecognized hardware, it was like it didnt even exist... I went in device manager and uninstalled all my usb devices, rebooted with everything but mouse/kb unplugged, installed SDK drivers for Nexus S, rebooted again (probably not needed but better safe than sorry) and I can now Odin into my phone... Hope this helps ya man... sucks bricking a phone
The Heimdall drivers won't work. Kies won't recognize it if it won't boot. There should be an option in Kies to install the driver. Drop down box in the top left corner. Did you try to install your driver that way?
have you installed the driver yet? samsung driver?
Uh hi.
I'm a herp.
So I may have accidently tried to root and flash my friend's Samsung Vibrant. It was going smoohtly but now, I'm all sorts of messed up.
The problem: I may have used the wrong kernel (zImage) when using heimdall-frontend (which I downloaded from xda). This is causing the phone to power on; it shows the Samsung Galaxy S 4g load screen, then Overstock, then the T-Mo logo sign (with the music), and then a longer Galaxy S load screen. After the load screen, the screen goes completely black, but all the touch buttons light up. Once like this, I can turn it off, and make it go back into recovery mode and also download mode.
Please help. I've been trying to solve this with my friend for about.. 4 hours.
P.S. I've looked up all the guides for using ODIN to get back to JFS, none works due to the reason that when I put it back into download mode, the computer does not recognize it. But it does at the same time. (it shows the "safetly remove hardware" and says that is an "USB mass storage device" ((but does not appear in "My Computer" when in the unresponsive screen-- but when in the download screen, it shows the same thing, only labeled "SAMSUNG USB Composite Device", which also cannot be accessed through "My Computer")
P.P.S. I'm sure it is a Samsung Galaxy S Vibrant, exclusive from T-Mobile. My computer is Windows Vista 32-bit, and I have as many Samsung drivers as humanly possible when it comes to the Vibrant.
Can anyone help a poor fool?
Try this, get in to download mode, open Odin, then disconnect the usb cable, then reconnect the usb cable and Odin should recognize it then. Good luck!
Using XDA premium, you should be too!
johnny12times said:
Try this, get in to download mode, open Odin, then disconnect the usb cable, then reconnect the usb cable and Odin should recognize it then. Good luck!
Using XDA premium, you should be too!
Click to expand...
Click to collapse
Sorry. That did not work. It just doesn't recognize it in ODIN when in download mode. My computer doesn't even see it. But it does say "Safely Remove Hardware" -- "SAMSUNG USB Composite Device"
Sounds really odd. Do you have any roms you can try reflashing from recovery?
Using XDA premium, you should be too!
depaer said:
Uh hi.
I'm a herp.
So I may have accidently tried to root and flash my friend's Samsung Vibrant. It was going smoohtly but now, I'm all sorts of messed up.
The problem: I may have used the wrong kernel (zImage) when using heimdall-frontend (which I downloaded from xda). This is causing the phone to power on; it shows the Samsung Galaxy S 4g load screen, then Overstock, then the T-Mo logo sign (with the music), and then a longer Galaxy S load screen. After the load screen, the screen goes completely black, but all the touch buttons light up. Once like this, I can turn it off, and make it go back into recovery mode and also download mode.
Please help. I've been trying to solve this with my friend for about.. 4 hours.
P.S. I've looked up all the guides for using ODIN to get back to JFS, none works due to the reason that when I put it back into download mode, the computer does not recognize it. But it does at the same time. (it shows the "safetly remove hardware" and says that is an "USB mass storage device" ((but does not appear in "My Computer" when in the unresponsive screen-- but when in the download screen, it shows the same thing, only labeled "SAMSUNG USB Composite Device", which also cannot be accessed through "My Computer")
P.P.S. I'm sure it is a Samsung Galaxy S Vibrant, exclusive from T-Mobile. My computer is Windows Vista 32-bit, and I have as many Samsung drivers as humanly possible when it comes to the Vibrant.
Can anyone help a poor fool?
Click to expand...
Click to collapse
Sounds like you used the wrong odin files. if your screen is showing a galaxy s 4g logo then you must have mistakenly flashed a galaxy s 4g odin/heimdall package. on the back of your phone what is the model number. What on earth is JFS? ive heard of JFD which is the stock firmware that the phone shipped with.
If you flashed the wrong bootloader you are more or less stuck between a rock and a hardplace and will require a jtag. now the fact that teh screen does turn on is a good thing.
You need to keep trying to get it into download mode maybe try using a jig. Once youve gotten it into download mode try every single usb port you can find on your pc. When i need to odin i need to use one of my usb ports on the rear io panel none of the others will work. Once you get odin running and recognizing your device use the files posted in my sig as the odin files. any others and i cant help you cuz i dont know what your source is. Odin should be able to recover your device if it is still booting to the splash screen.
If for whatever reason you cant boot into download mode but can get into recovery here is what you do: make sure you have the android SDK installed (dont know what that is go here: http://developer.android.com/sdk/index.html and follow their directions) then open up command prompt while in recovery type the following command: adb reboot bootloader this should put you into download mode. If nothing ive mentioned works you may require a JTAG there is a company called MOBILETECHVIDEOS (http://mobiletechvideos.mybigcommerce.com/) that has a JTAG service.
Good luck
-Cheers
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've been reading posts from here for a long time but this is my first post.
I'm coming here as a last resort to save my Galaxy s2 (SGH-T989) which has a stock ROM.
Here's what happened.
I dropped my phone and then it got stuck in bootloop (it only boots until I see the "SAMSUNG" word animation and stops there).
At that point, ODIN 'sees' that there's a connected device; KIES keeps "connecting...." but can't actually connect; ADB does not show any connected device.
So, what I wanted to do was to factory "reset" the phone. The problem is I can't get the phone into Recovery mode. I believe it's because my volume down button was acting up when the phone was working. However, I can get to "Download Mode" using a USB Jig.
So, the next thing to do is to flash a new stock ROM. However, whenever I connect my phone when it's in "Download Mode", ODIN does not see it.
Yes, I've installed, re-installed, removed, re-installed all drivers and Kies and I've done that so many times you can't even believe it.
The problem is that the device driver "SAMSUNG Mobile USB CDC Composite Device" gives the following error "This device cannot start. (Code 10)", and I don't know why or how I can get rid of that. As mentioned above, I've tried all the device driver installation fixes but none has worked.
I mean, when the phone is not in Download Mode and I connect it to my PC, all device drivers are working fine with no error, but when it's in Download Mode, I get the error mentioned above "This Device cannot start.".
So, my questions:
1) Is there a way to get to Recovery Mode without using the button combinations? (The phone is in bootloop)
2) How can I fix the device driver error mentioned above to get ODIN to see my device?
3) Is there anything else I need to be doing?
This problem is really frustrating and I've been on it for more than 2 weeks and nothing has worked so far. Any help is greatly appreciated.
1. I think you have flashed an bad kernel if you cant get into recovery mode and i dont get it why your volume down acts like up?.
2. http://support.microsoft.com/kb/943104 try to maybe also disable kies and try again.
3. Kies is on, adb doesnt work at samsung/download screen, try to reinstall samsung usb drivers again :/ yes I know but to be sure, disable driver signature or something like that if you are on windows 8.x, try another usb cable.
2weeks dont sound good. I hope these tips could help a bit but I still wonder why your phone got in bootloop when you dropped it !?!? What were you doing at that time and did the battery go out?
wulsic said:
1. I think you have flashed an bad kernel if you cant get into recovery mode and i dont get it why your volume down acts like up?.
2. try to maybe also disable kies and try again.
3. Kies is on, adb doesnt work at samsung/download screen, try to reinstall samsung usb drivers again :/ yes I know but to be sure, disable driver signature or something like that if you are on windows 8.x, try another usb cable.
2weeks dont sound good. I hope these tips could help a bit but I still wonder why your phone got in bootloop when you dropped it !?!? What were you doing at that time and did the battery go out?
Click to expand...
Click to collapse
Thanks for the quick reply, wulsic.
1. No, I did not flash any kernel on this phone, everything on it is stock and was working just fine before it was dropped. I meant that the volume down was not working properly, not that it was acting like up.
2. I tried that but did not work
3. The drivers are working fine when the phone is not in Download Mode, it's only when it's in Download Mode that I get the error and I've tried re-installing drivers and everything, I think the problem is with the device itself not a driver problem.