My phone has been to 9.0.0.197,but now the phone can not boot anything.no screen, no recovery, no fastboot.but when i connect cable to pc can still show fastboot device.i tried funkeyhuawei,dc-unlocker to flash but still no on. Please help me! Thank you everyone!
when you plug it into the computer (windows) in device manager does it show adb bootloader ? or usb ser ?
ColaTao said:
My phone has been to 9.0.0.197,but now the phone can not boot anything.no screen, no recovery, no fastboot.but when i connect cable to pc can still show fastboot device.i tried funkeyhuawei,dc-unlocker to flash but still no on. Please help me! Thank you everyone!
Click to expand...
Click to collapse
If your phone is under warranty I would suggest sending it in to a service center.
The only other way is opening the back cover of the phone and using testpoint. Removing back cover will void warranty, and is not suggested if you don't know what you're doing.
tokoam said:
when you plug it into the computer (windows) in device manager does it show adb bootloader ? Or usb ser ?
Click to expand...
Click to collapse
yes can show the adb bootloader device. But phone still black screen
ColaTao said:
yes can show the adb bootloader device. But phone still black screen
Click to expand...
Click to collapse
FYI I was in the same situation as you, Huawei denied my repair and said I had water damage.And I clearly did not have water damage once they see black screen and red led they always deem it as water damage.There was also another post where someone claimed water damage as well after they sent in there bricked device.At the end of the day I had to use test point recovery to get my device working again.
tokoam said:
FYI I was in the same situation as you, Huawei denied my repair and said I had water damage.And I clearly did not have water damage once they see black screen and red led they always deem it as water damage.There was also another post where someone claimed water damage as well after they sent in there bricked device.At the end of the day I had to use test point recovery to get my device working again.
Click to expand...
Click to collapse
ok thank you！i will try!
Hello, can please explain what is test point recovery? How can i do test point recovery?
Each device has a few contacts on the main board for connecting test point consoles in case bootloader or USB port is destroyed but you need proprietary cable and software to accomplish that. USB to test point is not always possible.
Related
Hello Guys!
My friend bought a SGS2 and he whanted to root it and to put MiUi on it. Now he unpluged it while it was in the Odin doing something with PIT...
It stopped and now he can't go anymore in the download mode and the phone remains black...
is that a full brick? is there any chance to run it again?
do you need more informations?
I looked throuth the threds but i couldnt find something like that...
i hope anyone can help
Will Samsung repair that with Warranty?
Can i know why he disconnected his phone during using something with Odin?!
He made a Solid Brick he cant do anything else than Warranty or JTAG..
BlackRainX said:
Can i know why he disconnected his phone during using something with Odin?!
He made a Solid Brick he cant do anything else than Warranty or JTAG..
Click to expand...
Click to collapse
haha he moved so fast with the mouse and hit the cable to the phone... i dont know exactly...
1. what is JTAG?
2. are you 100% shore that its a compleat brick?
3. is there no unbrickable or something like that?
Oli28 said:
haha he moved so fast with the mouse and hit the cable to the phone... i dont know exactly...
1. what is JTAG?
2. are you 100% shore that its a compleat brick?
3. is there no unbrickable or something like that?
Click to expand...
Click to collapse
If after trying multiple things like removing battery and what not and the phone won't boot or enter download mode, yup, it's a complete brick
achillies400 said:
If after trying multiple things like removing battery and what not and the phone won't boot or enter download mode, yup, it's a complete brick
Click to expand...
Click to collapse
nice wait not really...
but cant change anything... its sad for the device!
does enyone know if samsung will repair that??
i hope so
Oli28 said:
nice wait not really...
but cant change anything... its sad for the device!
does enyone know if samsung will repair that??
i hope so
Click to expand...
Click to collapse
It's not the most correct thing to do (actually, not at all, it was your friend's fault entirely, also voiding the warranty), but your friend can tell them that the device began to heat while charging, he unpluged it and it died, sometimes it happens...
As for the JTAG you asked on the other post, it's a physical connector inside the cellphone used to write the flash memory, it involves opening the device, pinning some terminals and programming via PC, it's pretty common on embedded devices to load the program for the first time.
There is still a chance to get the phone back to its senses!
you will need 2 people to do this
read all 5 steps then only proceed!
1. Remove the battery.
2.Start odin in your pc.
3.connect the mobile to the pc using cable.
4.keep pressing the keys required to get in download mode. i.e. power+home+volume down key.
5.ask someone else to put the battery in your phone keeping the keys pressed!.
if every thing goes right Odin will detect the phone Flash it with a good rom you know which works! and never take out the cell from odin when its being flashed until odin says Success!
pankajkundalia said:
There is still a chance to get the phone back to its senses!
you will need 2 people to do this
read all 5 steps then only proceed!
1. Remove the battery.
2.Start odin in your pc.
3.connect the mobile to the pc using cable.
4.keep pressing the keys required to get in download mode. i.e. power+home+volume down key.
5.ask someone else to put the battery in your phone keeping the keys pressed!.
if every thing goes right Odin will detect the phone Flash it with a good rom you know which works! and never take out the cell from odin when its being flashed until odin says Success!
Click to expand...
Click to collapse
Won't work if the PIT wasn't completed therefore leaving the device void of a bootloader, but it's worth the try, you have nothing to lose...
Wow, nice will try today... I will get the phone... would get a free Pizza if i would make it work again! thank you guys for your answers. I will tell you what happend...
is there a how ti for jtag? Could Be the solution...
Sent from my Desire HD RUNNY using XDA App
How to JTAG:
You had to solder stuff, it's safer to try warranty
Omega Frost said:
How to JTAG:
You had to solder stuff, it's safer to try warranty
Click to expand...
Click to collapse
Thank you!
suddenly this with the battery didnt worked so im gona send it to the warraty....
And when they dont repair it for free or less than 50 $ I have to send it to the JTAG..
thank you guys for all your support
Afaik u never supposed 2 use pit options in odin for gs2 otherwise u end up with a brick anyway regardless if u remove the cable or not. perhaps read more and be more careful if u ever decide 2 flash again. i would not be happy with that friend lol.
Sent from my GT-I9100 using xda premium
Hi.
I need some help with my phone.
I tried unlocking the bootloader with SE Xperia Flasher but something went wrong.
I got to the point where it rebooted the phone, but when I got back in Windows my PC wont recognize my phone, I can't even charge it with a wall contact.
Is this possible to break thru the software? Because I sure didn't do anything to damage it physically.
Thanks for all your help
Anyone? =/
Stockis said:
Hi.
I need some help with my phone.
I tried unlocking the bootloader with SE Xperia Flasher but something went wrong.
I got to the point where it rebooted the phone, but when I got back in Windows my PC wont recognize my phone, I can't even charge it with a wall contact.
Is this possible to break thru the software? Because I sure didn't do anything to damage it physically.
Thanks for all your help
Click to expand...
Click to collapse
No, you cant brick your phone until bootloader is fully unlocked.
You can only get into "sof brick" state which is followed with red led blinking (three times after SE logo). I think this is that state, but, you didnt mentioned how is your device behaving now...
HeliumX10 said:
No, you cant brick your phone until bootloader is fully unlocked.
You can only get into "sof brick" state which is followed with red led blinking (three times after SE logo). I think this is that state, but, you didnt mentioned how is your device behaving now...
Click to expand...
Click to collapse
Strange. I don't get any red LED blinking. My phone boots with a blue LED (Fastboot?) and then turns on normally, I can use WIFI and Bluetooth and that's all I've been able to try so far. Haven't had any chance to test if it works with phone calls since i have no sim card for it. If it is "soft bricked", is there any possibility to know it for sure?
Thanks for helping me out
Stockis said:
Strange. I don't get any red LED blinking. My phone boots with a blue LED (Fastboot?) and then turns on normally, I can use WIFI and Bluetooth and that's all I've been able to try so far. Haven't had any chance to test if it works with phone calls since i have no sim card for it. If it is "soft bricked", is there any possibility to know it for sure?
Click to expand...
Click to collapse
If your phone boots up normally it means, thats not bricked
Dont know what blue led during bootup means, but didnt see it anytime on locked bootloader, so I expect that you were succesfull and have unlocked bootloader It probably is fastboot mode.
Remember that Windows recognize only devices in usb debugging on and with proper adb drivers installed.
Stockis said:
Thanks for helping me out
Click to expand...
Click to collapse
Use Thanks button
HeliumX10 said:
If your phone boots up normally it means, thats not bricked
Dont know what blue led during bootup means, but didnt see it anytime on locked bootloader, so I expect that you were succesfull and have unlocked bootloader It probably is fastboot mode.
Remember that Windows recognize only devices in usb debugging on and with proper adb drivers installed.
Use Thanks button
Click to expand...
Click to collapse
Well, that's good news.
Haha might be, if I'm lucky. ANy idea how to check if it really is unlocked?
Strangest thing is that the phone is recognized by the PC now, a few days later, doing nothing. Just plugged it in and both charger and USB connection os recognised. Really didn¨t do anything at all to make it work
What do you give me if I use the thanks button?
Stockis said:
Haha might be, if I'm lucky. ANy idea how to check if it really is unlocked?
Click to expand...
Click to collapse
Yes, try to flash any kernel for locked bootloader. If it will be successful, you are on unlocked bootloader If not, ant it will return error at the beginning of the flashing, you are still on locked bootloader.
Stockis said:
Strangest thing is that the phone is recognized by the PC now, a few days later, doing nothing. Just plugged it in and both charger and USB connection os recognised. Really didn¨t do anything at all to make it work
Click to expand...
Click to collapse
Windows... Windows... Dont you know them ?
Stockis said:
What do you give me if I use the thanks button?
Click to expand...
Click to collapse
Sorry, nothing except help
But trying to get more thanks because it will allow me to easily join the developers section. So expect thanks from every helpful posts
Stockis said:
Well, that's good news.
Haha might be, if I'm lucky. ANy idea how to check if it really is unlocked?
Strangest thing is that the phone is recognized by the PC now, a few days later, doing nothing. Just plugged it in and both charger and USB connection os recognised. Really didn¨t do anything at all to make it work
What do you give me if I use the thanks button?
Click to expand...
Click to collapse
To check if your bootloader is unlocked or not :
http://forums.asf-mobiles.com/Threa...er-is-locked-or-not-Guide?pid=654&mode=linear
So .short story.i have a nokia lumia 800 rm 801,and dosn't boot anymore.i wen't to a repair shop and the guy over there said that the bootloader needs to be reinstalled because it's bricked,but he can't do it)
this is what's i've tried: leaving for few hours to charger/usb cable,didn't worked.
if i connect it to pc for few seconds i see in control panel,nokia dload and it discconect it.
i can start recovery mode( that windows phone with the computer cable thing on my phone if i connect the phone to charger or usb and press camera volume up and power) but i can't start recovery mode without data cable/charger.
when i connect the phone to charger it vibrate(nothing on the screen shows)if i press the power button for half a second i see the t-mobile logo.and keeps apearing and vibrating random times i guess i didn't counted exactly.(restart loop or something)
when i connect the phone to usb it vibrates long,and keep connecting to pc and discconecting.
when it's not connected to charger or usb,don't give any sparkle of life(no vibrating,powering on,nothing)
any help please?if anyone would be that kind to help me ,or give me enough advices to fix it by myself...
bump
noxified said:
bump
Click to expand...
Click to collapse
Ok, you also contacted me by pm and I'm trying to help you, but I don't have a Lumia 800 so I don't know all the difference between a Lumia 710 and a Lumia 800.
So in short, before I unlocked my phone I had a similar issue then which you are dealing now, what I did is disconnect the phone from the pc and pressed the camerabutton and keep it pressed, on the same time I pressed the on/off button once but keep holding the camerabutton, the phone shows the recovery mode, so I connected the phone with zune and reinstalled my backup, that's it.
(It's not neccesary to dis- and reconnect, but I only tell you the way I did it.)
If that doesn't work I think you must read this thread from bypx,
http://forum.xda-developers.com/showthread.php?t=1457341
Succesz,
and if i don't have the backup? cant i just use someone else's backup?(for nokia lumia 800 rm-801 ofcourse)
on that guide i don't have dead usb flasing...
and without dead phone usb flasing i get this error:
ERROR: OSBL reported an error! Code: 0x30022
and in linux if i connect it in recovery mode,it gives me this error:
unable to mount windows mobile error initializing camera: -105 Unknown model
and discconects automaticly from recovery mode,entering automaticly in that reboot loop.
i think that the bootloader it's faulty.
when i connecting the phone to zune i get this error: C101002E
And i don't have a backup for restoring...
Ok, I do some research and contact you asap
Greetz,
ok,i will wait.
bump
noxified said:
bump
Click to expand...
Click to collapse
stop bumping, pls. This won't speed up a solution!
if anyone has an idea, they will help you.
And i already told you via pm what i know.
i tought if i was bumping someone would see the topic ,who know how to do it.
ok,i have borrowed atf box.what's next?
noxified said:
i tought if i was bumping someone would see the topic ,who know how to do it.
ok,i have borrowed atf box.what's next?
Click to expand...
Click to collapse
If you think that you can do it by yourself, search the tutorial for unlock the phone with the ATF box. If not, do like me: go in a service center for phones, pay 13 euro, and in 30 minutes you go home with the phone done ok without any complications. I changed in service my bootloader from dload to qualcomm.
Sent from my HTC Desire HD
whiperhack said:
If you think that you can do it by yourself, search the tutorial for unlock the phone with the ATF box. If not, do like me: go in a service center for phones, pay 13 euro, and in 30 minutes you go home with the phone done ok without any complications. I changed in service my bootloader from dload to qualcomm.
Sent from my HTC Desire HD
Click to expand...
Click to collapse
I tryed at a service,money ain't a problem.The guy over there couldn't do it.
noxified said:
I tryed at a service,money ain't a problem.The guy over there couldn't do it.
Click to expand...
Click to collapse
Try on other service. IMO is a complicated procedure for an inexperienced guy.
Sent from my HTC Desire HD
i tried on 5 services...
Hi there, I have a problem. I flashed a ROM and i guess it also flashed a kernel, while im on a locked bootloader... uh oh. The phone can still charge the battery and I get to the SONY logo but nothing after that.
I have tried plugging in a USB cable with VOL - but then windows tells me it cannot recognize the device. I have installed the flashtool drivers and PC companion drivers but no go. Any help would be appreciated.
http://forum.xda-developers.com/showthread.php?t=2775411
Here is a recovery guide
I have tried this method. My problem happens when connecting the device after setting up flashtool. Windows tells me the device could not be recognized (device descriptor request failed), the phone flashes a red led when i plug in the USB cable and then green for a split second right after. then blank nothing, and the error shows up on my desktop.
Mortify1 said:
I have tried this method. My problem happens when connecting the device after setting up flashtool. Windows tells me the device could not be recognized (device descriptor request failed), the phone flashes a red led when i plug in the USB cable and then green for a split second right after. then blank nothing, and the error shows up on my desktop.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2635830
Here is everything you need
I have done all of these steps now and still have the same issue. The drivers installed with no problem when I enabled test signing, but the phone still will not recognize on my computer.
Please join me on https://webchat.freenode.net/ in #xperiaroms maybe we can fix this
Mortify1 said:
I have done all of these steps now and still have the same issue. The drivers installed with no problem when I enabled test signing, but the phone still will not recognize on my computer.
Please join me on https://webchat.freenode.net/ in #xperiaroms maybe we can fix this
Click to expand...
Click to collapse
Im busy right now, try messaging a dev or posting somewhere.
(yay college. Teacher is wondering why im staring at the floor )
Bump. I have a dead phone here, I've tried another computer and I am still getting these errors. I might have to replace the mainboard
we need more info to understand what happened and possible fix... what rom where you using before flash? lb or ub? what rom and kernel did you try to install and how?
ptmaniac said:
we need more info to understand what happened and possible fix... what rom where you using before flash? lb or ub? what rom and kernel did you try to install and how?
Click to expand...
Click to collapse
It's hard to remember, my phone was in for repair for an entire month, but because of one chip on the back plate they deemed the issue a physical problem and didn't cover it under warranty.
I think I was trying to flash back to eXistenz but I believe I flashed a kernel by accident, slip of the hand I guess. I went to restart the phone and it became frozen on the SONY logo. The phone is LB. I just need a fix!
Mortify1 said:
It's hard to remember, my phone was in for repair for an entire month, but because of one chip on the back plate they deemed the issue a physical problem and didn't cover it under warranty.
I think I was trying to flash back to eXistenz but I believe I flashed a kernel by accident, slip of the hand I guess. I went to restart the phone and it became frozen on the SONY logo. The phone is LB. I just need a fix!
Click to expand...
Click to collapse
i think Envious_Data is right, flashing a stock .ftf with flashtool should fix your problems as flashing wrong kernel shouldn't hard-brick your phone, only soft-brick.
But since you can't get your phone properly recognized on the pc you either have a bricked motherboard (i don't think that's the case) or you are having driver issues on the pc (most likely). maybe try flashing on windows xp?
I agree with the above
I followed the instructions provided at the MEGA UNBRICK something thread situated here http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108/
Anyway, when I hold the volume-up button for 10 seconds, followed by plugging the Onyx with the PC, the system does't detect the device. What can I do now? And is there any alternative method to unbrick a hardbricked phone? I urgently need help
If you installed the drivers and the computer is not reckognizing the device, that's bad news. How did you manage to accomplish that?
aredpanda said:
If you installed the drivers and the computer is nota reckognizing the device, that's bad news. How did you manage to accomplish that?
Click to expand...
Click to collapse
I don't know. And ijust in case if you were being sarcastic, I used the same computer to replace the recovery of this phone.
Im not being sarcastic. The problem with the Android modding scene is that people got too used to blindly following steps without really knowing how they are affecting their devices. In order to get better chances at getting help, you'll need to describe what and exactly how you were altering your phone.
aredpanda said:
Im not being sarcastic. The problem with the Android modding scene is that people got too used to blindly following steps without really knowing how they are affecting their devices. In order to get better chances at getting help, you'll need to describe what and exactly how you were altering your phone.
Click to expand...
Click to collapse
I was using Bliss ROM with BluSpark kernel. Anyway, I downloaded 2 ROMS today, Sailfish OS and the stock H2OS for OPX. I wiped the phone and first flashed the Sailfish OS, but the phone was stuck in a bootloop which only was showing the oneplus logo and the text "Powered by Anrdoid". After that, I entered recovery, and did the normal pre-flash wipe again. This time I flashed the H2OS, but after I gave "Reboot to System", my phone just wont do nor display anything. Hardbricked, dead
Can you boot it into recovery? Your bat may be dead from extensively flashing stuff, so plug the phone to the power cable and press and hold VolDown+Power for some good 30s, then you can conclude your phone wont boot into recovery and maybe need an unbrick.
aredpanda said:
Can you boot it into recovery? Your bat may be dead from extensively flashing stuff, so plug the phone to the power cable and press and hold VolDown+Power for some good 30s, then you can conclude your phone wont boot into recovery and maybe need an unbrick.
Click to expand...
Click to collapse
Yeah, it didn't boot into recovery
Does the led light up when you plug the phone to the wall? If it does let it charge for an hour before attempting anything else.
After that and before trying anything else, make sure driver signature check is off and test mode is on. This varies slightly for Windows 7/8 vs 8.1/10. Which version are you running?
aredpanda said:
Does the led light up when you plug the phone to the wall? If it does let it charge for an hour before attempting anything else.
After that and before trying anything else, make sure driver signature check is off and test mode is on. This varies slightly for Windows 7/8 vs 8.1/10. Which version are you running?
Click to expand...
Click to collapse
No, it doesn't
aredpanda said:
Does the led light up when you plug the phone to the wall? If it does let it charge for an hour before attempting anything else.
After that and before trying anything else, make sure driver signature check is off and test mode is on. This varies slightly for Windows 7/8 vs 8.1/10. Which version are you running?
Click to expand...
Click to collapse
I turned off the signature check, W8
If your led doesnt light when your phone is plugged to the wall, this is behind the hard unbricking procedure and your phone is indeed, dead.
Sent from my ONE E1003 using Tapatalk
This issue has been resolved via PM,
Can a mod please close this thread?
No idea what it could be besides corrupt firmware which I've never heard of happening before. The Qualcomm utility should work just fine. Leave it plugged in for an hour or two and see if anything happens
Did you install the qualcomm drivers? If not do it again carefully with driver enforcement off. It works like a charm. Have bricked my device twice as of now and it worked.