Hi so, this is my story.
A couple of days ago my phone fell from my pocket while getting out of my car into the driveway. When i noticed i didn't have it i started calling it, and found it ringing outside. When i grabbed it it had the back panel destroyed but no visible damage to the screen (phew). It was working. Next day, battery is dead, so I connected to a USB cable from my PC, but no cigar, the LED was flashing red and it wouldn't turn on. I seached on the forums an finally got it to turn on, but I didn't have a signal. I went to check service providers and it showed an error. Came to the forums again and found out about all this unknown IME and baseband that people were talking about, and I seem to have the same problem. However, I could not solve it with any of the solutions I could find here.
What I've tried:
http://forum.xda-developers.com/showthread.php?t=2347060
(tried this 3 times and no luck)
Flashing several other radios (48 84 33 even 27)
Installed CWM (touchscreen)
Installed a custom ROM (CM10.1)
Flashed android stock 4.2.2
Other details:
I do have Wifi and bluetooth
The baseband version shows correctly in fastboot mode
The battery problem (flashing red light problem seems to still be there, I am charging now only with wall socket to see if it gets fixed)
I opened up the phone, and there is no visible damage to it from the inside, I also took out the battery and checked the connector for the modem
Attached some Screenshots
Can anybody help me, or guide me in some direction please, I really want my phone back. (I'm using my old Nexus one in the meantime )
Some screenshots attached
Just an idea: take your SIM off and on. Try firmly align it.
I have had (having from time to time) the same problem with my S2. And that always works. I guess because my SIM is very old but it may be from some dislocation of the card.
Hope it helps.
thorindwarf said:
Just an idea: take your SIM off and on. Try firmly align it.
I have had (having from time to time) the same problem with my S2. And that always works. I guess because my SIM is very old but it may be from some dislocation of the card.
Hope it helps.
Click to expand...
Click to collapse
I have tried with a couple of SIM cards, and also without it. No luck, the SIM Cards were pretty old tho, I will try with a new one and see what happens.
Other thing, Shouldn't I see the IMEI and baseband without a SIMCARD in anyways??
Thanks
I have never tried myself but maybe if you put the phone in diagnostic mode and connect it to lgnpst or qpst using the same drivers you used to unbrick the phone, you might be able to read the nvram and look for signs of memory corruption and perhaps correct the values? This is just an idea. I am not an expert and this might not work at all or make things even worse. Perhaps you can pm gigadroid and ask him his opinion?
Sent from my cm_tenderloin using xda app-developers app
I know you said you've flashed stock 4.2.2, but have you tried doing a full flash to a Nexus factory image?
https://developers.google.com/android/nexus/images#occam
You will need Fastboot installed (I recommend using the SDK to install it if you haven't already http://developer.android.com/sdk/index.html). It reflashes every partition on your phone to stock (more than what you can flash/restore through recovery). It's a bit of a "nuclear option" for fixing any software related issue.
raptir said:
I know you said you've flashed stock 4.2.2, but have you tried doing a full flash to a Nexus factory image?
https://developers.google.com/android/nexus/images#occam
You will need Fastboot installed (I recommend using the SDK to install it if you haven't already http://developer.android.com/sdk/index.html). It reflashes every partition on your phone to stock (more than what you can flash/restore through recovery). It's a bit of a "nuclear option" for fixing any software related issue.
Click to expand...
Click to collapse
Hi, I already tried that, the 4.2.2 that i flashed was from there :/ (with fastboot)
Also I completely took apart the phone today, and the motherboard seems fine (for what the naked eye can see)
The battery seems to drain really fast tho.
pocketrussian said:
I have never tried myself but maybe if you put the phone in diagnostic mode and connect it to lgnpst or qpst using the same drivers you used to unbrick the phone, you might be able to read the nvram and look for signs of memory corruption and perhaps correct the values? This is just an idea. I am not an expert and this might not work at all or make things even worse. Perhaps you can pm gigadroid and ask him his opinion?
Sent from my cm_tenderloin using xda app-developers app
Click to expand...
Click to collapse
Thank you, I will do that as soon as I figure out how to do it.
With diagnostic mode you mean that download mode or there is another one?
Also I noticed that every time i use LGNPST a window saying that my device is being installed pops up, could it be a driver issue?
I don't think that this would work in download mode. I just tried with LGNPST in download mode and it's asking for an spc code. I tried 000000 but I didn't work. I tried qpst and it says it can't read phone settings in download mode. Again, I don't know much about this but there must be another mode (diagnostic) for which this might work. I googled but wasn't able to find any # codes that work on the n4. Perhaps from the terminal emulator if your phone is rooted. I wish I could help more but I just got this n4 recently and I am not an expert in any of this stuff.
Sent from my cm_tenderloin using xda app-developers app
Same problem here...
venec said:
Hi so, this is my story.
A couple of days ago my phone fell from my pocket while getting out of my car into the driveway. When i noticed i didn't have it i started calling it, and found it ringing outside. When i grabbed it it had the back panel destroyed but no visible damage to the screen (phew). It was working. Next day, battery is dead, so I connected to a USB cable from my PC, but no cigar, the LED was flashing red and it wouldn't turn on. I seached on the forums an finally got it to turn on, but I didn't have a signal. I went to check service providers and it showed an error. Came to the forums again and found out about all this unknown IME and baseband that people were talking about, and I seem to have the same problem. However, I could not solve it with any of the solutions I could find here.
What I've tried:
http://forum.xda-developers.com/showthread.php?t=2347060
(tried this 3 times and no luck)
Flashing several other radios (48 84 33 even 27)
Installed CWM (touchscreen)
Installed a custom ROM (CM10.1)
Flashed android stock 4.2.2
Other details:
I do have Wifi and bluetooth
The baseband version shows correctly in fastboot mode
The battery problem (flashing red light problem seems to still be there, I am charging now only with wall socket to see if it gets fixed)
I opened up the phone, and there is no visible damage to it from the inside, I also took out the battery and checked the connector for the modem
Attached some Screenshots
Can anybody help me, or guide me in some direction please, I really want my phone back. (I'm using my old Nexus one in the meantime )
Some screenshots attached
Click to expand...
Click to collapse
This is exactly what is going on with my phone, except I did not drop. Was there any resolution???
stenosis said:
This is exactly what is going on with my phone, except I did not drop. Was there any resolution???
Click to expand...
Click to collapse
Nope, no solution for me, tried everything that is here in xda, and nothing works :/
venec said:
Nope, no solution for me, tried everything that is here in xda, and nothing works :/
Click to expand...
Click to collapse
I'm with the same issue. Any good news?
elbosio said:
I'm with the same issue. Any good news?
Click to expand...
Click to collapse
Nope, tried everything nothing works so far
I'm thinking about sending it to this guys or wait for kitkat and hope for the best:
http://mobiletechvideos.mybigcommerce.com/lg-phones/
OK. Was your phone on 4.2 when you got it or did you revert to it. I once reverted to 4.2 but did a unbrick write to 4.3 lost my radio and all. But when I realized what I did I fixed by going back to 4.2 Leaving stock and ota each update which fixed my problem.
Sent from my Nexus 4 using xda app-developers app
I'm having the same issue so the phone is going back to Google for replacement. It has been acting wonky for a few days anyways.
I tried the Google factory flash script, flashed a few different radios, and followed this thread:
No luck.
I was running AOKP 2013-10-15 Nightly. And the problem started with the phone doing a constant boot loop for a few hours without me noticing. It was some kind of issue with the power button getting stuck that appears to have resolved itself but it took the radio with it.
Droid2drummer said:
OK. Was your phone on 4.2 when you got it or did you revert to it. I once reverted to 4.2 but did a unbrick write to 4.3 lost my radio and all. But when I realized what I did I fixed by going back to 4.2 Leaving stock and ota each update which fixed my problem.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yes it was 4.2, so you mean do the LGNPST thing and after flash 4.2 image?
I already did that with the 4.2.2 (JDQ39) image and still no luck
I had the same issue, and I solved it by flashing the factory images... Twice.
Related
[EDIT 3] Worked fine, finally, thanks for all the help.
[EDIT 2] Yeah, I don't know how it happened or what happened, but I got a lot further. I started to get Odin failing at recovery and then remembered this thread which I found earlier: http://forum.xda-developers.com/showthread.php?t=907261&page=2
Basically did it exactly like how the OP fixed it, and the phone is currently being flashed.
But now I have a different problem, seems I can't get a break.
http://img651.imageshack.us/i/stuck.jpg/
It's stuck there, should I just wait? Is it supposed to take a while? Or is there a problem? Been there for about an hour now.
[EDIT] So the phone works now, but Odin won't flash for me. What could the problem be if it's stuck on Initializing (or rather, Initialzing as the program puts it)? I've tried 1.61, 1.7, used the DI18 file and removed the md5 bit so that the file ends in .tar, etc
Hey, so I've been desperately trying to return my Epic to stock DI18, and I tried clockwork mod which didn't work, and then I tried doing it through Odin, and it kept hanging on Initializing.
Anyway, I keep trying with Odin, and ended up taking out my battery and putting it back in, but now the phone won't turn on. It doesn't turn on normally, not through download mode, not recovery, nothing.
Any help? What can I do? I tried searching but every result ends up being about turning on bluetooth or wifi, etc., and the few that are related to bricking talk about going into download mode to flash with Odin.
I hope you didn't take the battery out while flashing odin...
you can't turn it on in any way right?
can you charge it via usb? maybe you just ran out of power while flashing?
Uh, yeah, that's exactly what I did. Every time Odin would hang at Initializing, I'd have to remove the battery and restart the phone to try again.
God, I am so stupid, it is ridiculous.
The battery did have a decent amount of charge last time I checked though.
Hold down 1 and power and insert battery while holding them. That should get you into d/l mode. Taking out the battery while odin is stuck on initializing does not harm the phone.
Sent from my Bonzai'd Epic 4g.
I just did something like what you said leather, and I got it into download mode.
Now I'm afraid to do anything. Any reason why my flashing through Odin wouldn't work?
Odin is picky about the computer its running on. I used a laptop when i first started flashing..no issues ever.
Fixed my desktop and instantly ran into odin problems. Try changing USB ports and make sure youve got no firewalls running.
Sent from my SPH-D700 using XDA App
Yeah, what I don't know how it happened or what happened, but I got a lot further. I started to get Odin failing at recovery and then remembered this thread which I found earlier: http://forum.xda-developers.com/showthread.php?t=907261&page=2
Basically did it exactly like how the OP fixed it, and the phone is currently being flashed.
But now I have a different problem, seems I can't get a break.
http://img651.imageshack.us/i/stuck.jpg/
It's stuck there, should I just wait? Is it supposed to take a while? Or is there a problem? Been there for maybe 5-6 minutes now.
The factory always takes the longest; so give it time. And do NOT pull the battery at that point. Youll have to say good bye epic :<
Sent from my SPH-D700 using XDA App
How did this end up? Did it move past FACTORY FS?
Nope, still stuck in that same exact place. Is it supposed to take this long or has something gone wrong?
Could I unplug it and try again at this point, or would that brick it? It's just stuck there, what do I do? I'd love to try different usb ports and such, but I can't if I don't stop this process, just don't know how to do it without bricking it.
And thanks for the help so far.
Did you remove the. Md5 at the end of the tar file?
Sent from my SPH-D700 using XDA App
No, I put the md5 back to start from the beginning with everything as it comes from downloads and such.
What do I do about it right now though? Can I safely unplug it and restart it or...?
Seems like you have no choice but to unplug it. Removing the md5 shouldn't make a difference. Try a different USB port.
Sent from my SPH-D700 using XDA App
Yeah, thankfully it didn't brick. I feel like I'm walking through a minefield with this thing.
Anyway, switched ports, had the file renamed to end in .tar, made sure Odin was opened as administrator in Windows 7, and thankfully it flashed fine.
Now I'm back at vanilla 2.1, can start fresh in terms of upgrading, was having some problems earlier. Is that GPS locking problem present in 2.3? Assuming I put ClockworkMod 3 on it and have the file system reset to EXT4, can I just flash to 2.3 ROMs right away?
Such problems
Hi everyone,
Skip this first paragraph if you just want to read my steps from problems to solution:
I hope this post helps people who were in the same situation I was in.
A few days ago I just happened to read the news about the new gingerbread for the AT&T i997 Samsung Infuse. I read that it wasn't over the air. Because of what has been seeming as a bluetooth leak after trying everything to stop the leak up to hard resetting it, I figured I'd pray that gingerbread fixes it. So on went my quest in the last few days trying to get this gingerbread update as fast as I could.
1) I downloaded keys mini for the Samsung device which was needed for the upgrade. I installed it on my main pc which is windows 7 64 bit. After installation, it's first run, it automatically updated the application.
2) I plugged in my phone via usb and it said device not registered so I got in contact with a Samsung rep in chat who told me to register it and it would take 24 hours.
3) I registered on Samsung and waited about 48 hours and still no change.
4) Got impatient and read about GTG Ultimate unbrick which is supposed to return my stock phone back to it's out of box condition which eliminated what I thought as an error with my phone of it not being registered.
5) Now after plugging it in after the unbrick. I got a message stating "device already up to date". I kept getting this for the last couple days. Sigh
6) Read that I could download the new gingerbread stock ROM without being rooted. Just had to use the ODIN3 I got with the GTG Ultimate unbrick zip file and supply the ROM I997UCKL2-Homebinary.tar.md5 as the input file.
7) Follow basically same instructions as unbricking but not reformatting and just supplying the md5 file as the input for hte PDA button then clicking start.
8) Odin 3 message status window was stuck at setupconnection and I knew this wasnt right. It was stuck for over 15 minutes and it should only do that for a minute or less.
9) Unplugged usb and big error in red on Odin 3 (but didn't have a choice)
10) Tried removing battery and retrying the flash but now a bigger issue the screen was all colored specs or in other words multi colored spots. Rut roh!
11) After scratching my head and googling like crazy some others had the same issue and they mentioned removing the battery and trying again but didn't mention that the spots would remain on the screen while the items could be flashed fine.
12) Tried again this time it got past setupconnection but was stuck at initializing.
13) Thought to myself let me try it on my Windows Vista 32 laptop.
14) Voila. It worked. So don't give up if you see the colored spots on your screen. There still is a chance. I now have gingerbread. THANKS EVERYONE!
Next Morning Update:
I was too quick to be happy. It seems I am one of the small few who is having touch sensitivity issues and lag typing on the lower right side of the screen especially with the back key (backspace). I typed my first reply to an email and the third word in the backspace was completely disabled.
Glad you got it working.
Am i the only one when i saw "what now" immediately thought about that lead paint commercial ?
iSaint said:
Am i the only one when i saw "what now" immediately thought about that lead paint commercial ?
Click to expand...
Click to collapse
GTG Ultimate unbrick zip is missing can u re-up it plz?
Deleted by user
I suggest you to completely charge your phone for half a day and then try to power it on. It should at least get stuck in the M logo.
Sent from my MB525 using XDA App
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Was your battery low when you tried flashing? It will not charge in bootloader mode so if you're battery is low you will have issues. If you boot with volume up pressed does it give you a message?
Try the Mcgyver battery fix found in this forum.
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse
Deleted by user
I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
gookia2000 said:
Hi all, I am a proud owner of a t-mobile defy (for about 2 months now!) and my hands got itchy today and went ahead to "debrand" it following the guide by Higgsy.
I was trying to flash a uk 2.21 rom onto my t-mobile defy (rooted with z4root).
Well, I managed to do all the steps of the guide. my phone was recognised by rsdlite, i selected the uk 2.21 sbf file, i clicked start, and it started flashing the different code groups. Finally, it said "finished" and "PASS". Here is when the problem started. The phone did not reboot into android. It was just a blank screen with a white light on the top (where the green led is to inform you about new messages.)
i panicked and disconnected the phone (the white light turns off after disconnecting), took out the battery, tried rebooting, tried rebooting into recovery (power + vol down), tried rebooting into bootloader (power + vol up). Nothing worked. it just stayed dead.
I then plugged it back into the computer. immediately the white light came back on and rsdlite recognised my phone. i tried flashing again - same result. I then tried flashing the 2.52 uk rom - same result.
even more panicky now, i unplugged everything and decided to take a nap and hopefully think of some ingenious solution to the problem. now, after a 3 hour rest, i tried plugging the phone back into the computer. the white light comes on, but now rsdlite doesnt even recognise the phone.
In essence, is my phone bricked? I cannot:
1) load into recovery to do a nandroid restore (yes, i have a nandroid backup copy)
2) load sbf files from rsdlite. every sbf file i tried doesnt seem to work. now its worse as rsdlite doesnt even recognise my phone.
i have even tried doing a nandroid restore via adb. but i get the error message that no phone was detected in the command prompt. perhaps its because the phone was not started in recovery mode.
The only explanation i can think of is that i have recently updated to the t-mobile 3.6.360 update and that might be the reason why so many people before me were able to flash their defy's roms successfully while i got stuck.
Can anyone please help? I LOVED my defy more than any other phone, and 2 months was too shortlived!
Click to expand...
Click to collapse
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse
Deleted by user
Actually, all you have to do is press the power button while the LED is on and RSDLite is running. You will hear the USB detection sound and your phone will appear on the list. It won't appear as it normally would but it will be listed.
Then just choose the Froyo ROM and then click start to flash it. It'll take less than 10 minutes...
There's no other way that I know of to get it working. Even in the link that I posted, you can check and see that no one even bothered to give me an idea of what to do. I had to figure this out myself.
I figured it was the bootloader protection that was causing the problem so the logical choice was to flash the only T-Mo ROM available which happens to be the leaked Froyo.
It's been almost 24 hours and I've had no problems with FroYo so as far as I'm concerned, I'm good.
gookia2000 said:
Beach Head, thanks for your reply. you have provided me with a glimmer of hope!!! the leaked tmobile froyo sbf is one i have not tried. I will certainly try to flash my defy with that once i have gotten it recognised by rsdlite.
I believe my phone is currently not being recognised by rsdlite due to insufficient battery. (cant confirm this, as all i see when i plug in the usb is a white light on my phone. but ever since i started this entire nightmare, i think i have attempted flashing at least 5 different sbf files and considerable battery has been drained.) I will try the Mcgyver battery fix next.
skateguitar, THERE IS HOPE!!! i havent confirmed it yet but i think we all got stuck cos we were trying to flash from a "non-downgradeable" 3.6.360 firmware. and rsdlite does not recognise our phones due to low battery (your phone was left with a white light on after flashing for 1 whole night.) SO... i propose this course of action: 1) perform the Mcgyver battery fix and try to get our phones recognised by rsdlite first. 2) once recognised, flash with the leaked tmobile froyo sbf.
Does anyone have any better suggestions before i plunge head first to save my phone?
Click to expand...
Click to collapse
Yes all i wanted to say was that you might have lost your downgradability and thats why phone does not boot. Simple thing is to flash the original sbf like what beachhead suggested. It definitely should work.
Sent from my MB525 using XDA App
Guess what, it works!!!
Deleted by user
Glad I could help you out!
Enjoy Froyo!
gookia2000 said:
OHMYGOODNESS!!! I LOVE YOU GUYS!!!
My Defy has been flashed with the t-mobile froyo leaked rom and IT WORKS!!! I was so mentally set with the idea that my defy has been bricked and I just threw $400 down the drain... NOW I AM SO HAPPY!!!
Anyway, just for your information, here is what I did:
- I first tried to get my defy recognised by rsdlite. I tried Beach Head's suggestion of pressing the power button while the led is on to no effect. I reckon that the battery has just been drained too low. So, i went ahead with the McGuyver battery fix.
- Alas, with the wires protruding precariously from my phone, rsdlite finally recognised my phone. I went to load the leaked t-mobile froyo rom and went ahead flashing it.
- And, guess what, IT WORKS!!!
Thank you all so much, especially beach head, for your help in this forum! I would have gone to the mobile store to get another phone if not for you guys!!!
Click to expand...
Click to collapse
I have the same problem, and will probably end up trying to flash the leaked Tmobile Rom.
Can you point me to where you downloaded this file? I think I found the thread, but I want to be sure
Deleted by user
got it! Thanks!
Now to ultimately decide if I want to flash this, since it's non-downgradeable
To update, flashing this rom has fixed my phone. Yay! Thanks!
I wonder if it was the 3.66x update that Moto pushed out - this phone was brand new, bought in Dec 2010, no other hacking done on it...
Beach_Head said:
I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
Click to expand...
Click to collapse
How did you get it to show up in rsd
I'm not working on my phone because i think i messed it up enough, so i took it to a store that fixes phones. The guy told me that he had my battery on a universal charger and he still cant get rsd lite to recognize it... What can i do
Another Happy Defy User
Just to confirm, I was seeing the same thing gookia2000 was seeing. Here was my resolution in case it helps anyone:
I was able to get mine working by flashing the US Stock Froyo build as explained in this thread: http://forum.xda-developers.com/showthread.php?t=938708&highlight=bricked&page=2
I found this thread to be super helpful as it helped me confirm my suspicion that the battery being low was the issue: http://forum.xda-developers.com/wik...#Recover_Nearly_Bricked_Phone_.28hopefully.29
Thankfully my wife has the same phone so I borrowed her battery, otherwise I would have been going McGyver style per Sorensiim (da' man) as seen here:
http://forum.xda-developers.com/showthread.php?t=892026
So happy this nightmare is over - running Froyo is a little bonus love!
Thanks to all @ XDA!!!
-Dave
Defy wont come on get a white light!
im having the same prob i did the the steps but its not working is there anything else i can do or is there a video of the proceeder
I have the same issue with a Telstra defy. I can get RSD to recognise something is connected but it isnt listed as MB525 like before but as "S Flash OMAP3630" I have flashed various SBF files but nothing is changing.
So,the DHD was running perfectly fine till yesterday,when something strange started happening.The damn thing wouldn't show some widgets(all were non-HTC widgets btw) and a message about the SD card popped up,but I couldn't see what it was saying,as the phone rebooted.After it booted the battery had dropped from about 90% to 10% btw.What was strange?Well,as soon as screen went off,it wouldn't turn on again.Pulled battery,rebooted.The same again and again and again.I thought it had to do with my UV settings.Removed my scripts,rebooted.Still the same.I also removed some ram-optimization scripts I was testing,in case that was the problem.Again,nothing changed,the problem persisted.Then I changed kernels(LordClockan's Sense kernel v4,LeeDroid's kernel v4,RCMix Team's v11 and v10) to no avail.I also changed roms(RCMix3D to LordClockan's 0.8 ICS build and back),but STILL nothing.I even changed recoveries(From CWM 4.0.0.2 to 4EXT Touch 1.0.2 RC1) but it didn't fix the problem,even after a full wipe-format of ALL partitions.I tried removing the SD card and the SIM card in case one of them was causing the problem,but the same happened.
Then I thought "****,let's see what the hell happens".To better explain what happens,when I try to turn the screen back on(Even if it was off for like 1sec) it doesn't turn on.The buttons' lights turn on,but nothing responds.However,I can hear background notifications and stuff.While it's working,it also doesn't reboot or power off when prompted to do so,either through some app or through the power menu.
So,back to what I was saying,I decided to run a logcat to see what happens.But adb won't recognize the device at all.No matter if it's "adb reboot" or "adb logcat" or anything,it says "device not found".
So,what I haven't tried yet is changing radios,but:
i)I'm afraid it may finish it off in case something goes even more wrong
ii)I don't think it's in any way related to the problem
So,before I quit trying and call HTC for warranty purposes(IF I can still flash an official RUU for Christ's sake),do you guys have any ideas?I'm out of ideas right now.AND it sounds hardware related or something(Although I can still transfer files from my PC to the SD card).
Thanks in advance guys.
my phone wouldn't turn back on after a phone call ended, and it turns out the proximity sensor was playing up, so i used the recalibrator from here: http://forum.xda-developers.com/showthread.php?t=951858
this probably won't be the right solution for you, because this isn't the typical problem that the recalibrator solves, your problem sounds very strange. but it might be worth a shot anyway.
you should be able to get in to bootloader to flash a stock rom. If adb and the power menu are both not working, boot in to recovery from inside the 4ext recovery control app or Rom Manager app, then in recovery go to the power menu and there's the option to boot in to bootloader. and since you can put things on the SD still, put a PD98IMG.zip on the sd and away you go.
if that doesn't fix it, it's probably hardware unfortunately
good luck!
maatsby said:
my phone wouldn't turn back on after a phone call ended, and it turns out the proximity sensor was playing up, so i used the recalibrator from here: http://forum.xda-developers.com/showthread.php?t=951858
this probably won't be the right solution for you, because this isn't the typical problem that the recalibrator solves, your problem sounds very strange. but it might be worth a shot anyway.
you should be able to get in to bootloader to flash a stock rom. If adb and the power menu are both not working, boot in to recovery from inside the 4ext recovery control app or Rom Manager app, then in recovery go to the power menu and there's the option to boot in to bootloader. and since you can put things on the SD still, put a PD98IMG.zip on the sd and away you go.
if that doesn't fix it, it's probably hardware unfortunately
good luck!
Click to expand...
Click to collapse
Well,I know my way around the device,but sadly that's not enough this time.
Do you by any chance know what stock rom I should flash?I kinda lost track of things since I bought my Galaxy S II...
Thanks for the reply too pal.
Adb kill-server
Adb start-server
Then try and do other adb commands, see if that works
Sent from my HTC Desire HD A9191 using xda premium
tolis626 said:
Well,I know my way around the device,but sadly that's not enough this time.
Do you by any chance know what stock rom I should flash?I kinda lost track of things since I bought my Galaxy S II...
Thanks for the reply too pal.
Click to expand...
Click to collapse
No worries. I returned to stock last week for warranty, I flashed this: http://www.multiupload.com/BTJ8KY0KH9
from this thread: http://forum.xda-developers.com/showthread.php?t=905003
I used this one because it is easily re-rooted with visionary. So if you flash the stock rom and the problem is fixed you can head back in to rooting land straight away. But unfortunately, if you have to send it to HTC after all, they'll probably OTA upgrade it before giving it back
maatsby said:
No worries. I returned to stock last week for warranty, I flashed this: http://www.multiupload.com/BTJ8KY0KH9
from this thread: http://forum.xda-developers.com/showthread.php?t=905003
I used this one because it is easily re-rooted with visionary. So if you flash the stock rom and the problem is fixed you can head back in to rooting land straight away. But unfortunately, if you have to send it to HTC after all, they'll probably OTA upgrade it before giving it back
Click to expand...
Click to collapse
Thank you dude.Will try and report back.I hope everything goes too well.Or,in that aspect,too wrong in case I can get a new device.
So,after a downgrade to stock 1.32.xx version(the one maatsby posted) it seems to be solved...Strange indeed,but I'm happy!I love this phone.
I'm gonna check whether rerooting will make the problem reappear.I certainly hope not.
Anyway,thanks for the help,especially you maatsby!
tolis626 said:
So,after a downgrade to stock 1.32.xx version(the one maatsby posted) it seems to be solved...Strange indeed,but I'm happy!I love this phone.
I'm gonna check whether rerooting will make the problem reappear.I certainly hope not.
Anyway,thanks for the help,especially you maatsby!
Click to expand...
Click to collapse
no worries mate, and thanks for the update. I'm glad that fixed it!
It would be interesting to know what went wrong!
maatsby said:
no worries mate, and thanks for the update. I'm glad that fixed it!
It would be interesting to know what went wrong!
Click to expand...
Click to collapse
Yes,it would be interesting,but I even nandroid-ed back to my previous ROM(the one the problems first appeared on) and it's working flawlessly.If it does it again I'll make sure to post it here in case others have the same problem in the future.
Hey guys so I am facing weird problems. I have searched through the forums either I cant find anything or I am too scared to do any more experiments I really dont want to loose my Razr M XT 907.
Problems
Laggy performance at times
Camera gets stuck when I take pictures at times then I have to restart.
when I reboot my phone it shows AP Fast boot screen, then I have to access boot menu and select the second last option (Console something). It always shows Null:Null and when I change it back the phone reboots normally
Phone hangs sometimes and then responds with everthing I have clicked all at once.
The screen on off button responds a second late
I think you guys can help me better if I tell you what I did to this phone exactly since I got this phone.
What I did
I initially bought this phone with defaul OS 4.0.1 in Pakistan.
I then installed a Verizon system update of 250 MB that got my phone stuck on a boot loop (and made me cry almost)
I restored my phone to the settings it came in using this procedure
http://www.andromods.com/tips-trick/how-to-restore-unroot-droid-razr-m-xt907-stock-original-firmware.html
The phone worked fine for 2 days but then I got that update prompt again and it got annoying so I though maybe If i upgrade it to JB using the same RSD Lite method but a different ROM that may solve it.
So I applied the above Procedure using this ROM
http://forum.xda-developers.com/showthread.php?t=2250155
The method showed as Passed on RSD Lite but the phone got stuck on bootloop again so I paniced and tried restoring my phone abck to ICS using the method mention in the first link provided.
Then the phone got stuck on AP Boot Menu
Then I used DROID_RAZR_M_Utility_1.20 and used both methods 1 and two but it didnt work
Then out of the blue I went to the boot menu and I saw an option Switch Console (Null:null) I pressed up key on and null null changed to default:tty something it and the phone booted up just fine back to ICS
Now everytime I power off the phone it goes to AP Boot menu showing FASTBOOT REASON: Sticky bit factory_fastboot and I have to do the above to restart the phone.
What I need
Please help me restore my phone I dont want to brick it, I am a simple user I will need step by step guide
Anyone ?
Bump
Bump still looking for a solution
I have CM10 on mine and the camera is completely broken
Enter fastboot oem fb_mode_clear and problem gone.
v0ltage112 said:
Hey guys so I am facing weird problems. I have searched through the forums either I cant find anything or I am too scared to do any more experiments I really dont want to loose my Razr M XT 907.
Problems
Laggy performance at times
Camera gets stuck when I take pictures at times then I have to restart.
when I reboot my phone it shows AP Fast boot screen, then I have to access boot menu and select the second last option (Console something). It always shows Null:Null and when I change it back the phone reboots normally
Phone hangs sometimes and then responds with everthing I have clicked all at once.
The screen on off button responds a second late
I think you guys can help me better if I tell you what I did to this phone exactly since I got this phone.
What I did
I initially bought this phone with defaul OS 4.0.1 in Pakistan.
I then installed a Verizon system update of 250 MB that got my phone stuck on a boot loop (and made me cry almost)
I restored my phone to the settings it came in using this procedure
http://www.andromods.com/tips-trick/how-to-restore-unroot-droid-razr-m-xt907-stock-original-firmware.html
The phone worked fine for 2 days but then I got that update prompt again and it got annoying so I though maybe If i upgrade it to JB using the same RSD Lite method but a different ROM that may solve it.
So I applied the above Procedure using this ROM
http://forum.xda-developers.com/showthread.php?t=2250155
The method showed as Passed on RSD Lite but the phone got stuck on bootloop again so I paniced and tried restoring my phone abck to ICS using the method mention in the first link provided.
Then the phone got stuck on AP Boot Menu
Then I used DROID_RAZR_M_Utility_1.20 and used both methods 1 and two but it didnt work
Then out of the blue I went to the boot menu and I saw an option Switch Console (Null:null) I pressed up key on and null null changed to default:tty something it and the phone booted up just fine back to ICS
Now everytime I power off the phone it goes to AP Boot menu showing FASTBOOT REASON: Sticky bit factory_fastboot and I have to do the above to restart the phone.
What I need
Please help me restore my phone I dont want to brick it, I am a simple user I will need step by step guide
Anyone ?
Click to expand...
Click to collapse
I have solution but the android you will flash is android kitkat i don know if do u want reply me if u want to unbrick note: kitkat not supported root
lulz
Adriantech said:
I have solution but the android you will flash is android kitkat i don know if do u want reply me if u want to unbrick note: kitkat not supported root
Click to expand...
Click to collapse
Dude.. you know that you're responding to a thread that is literally a year old right?
cliMAKtic said:
Dude.. you know that you're responding to a thread that is literally a year old right?
Click to expand...
Click to collapse
And wath is the problem i cant help?
Adriantech said:
I have solution but the android you will flash is android kitkat i don know if do u want reply me if u want to unbrick note: kitkat not supported root
Click to expand...
Click to collapse
I also have a solution, but you would need another phone...
But as cliMAKtic said, it's most likely way too late now. Same goes for your replies in other threads.
Adriantech said:
And wath is the problem i cant help?
Click to expand...
Click to collapse
You can, but I'm afraid you won't. You'll rather achieve the opposite by bringing obsoleted threads back to the top.
lem22 said:
I also have a solution, but you would need another phone...
But as cliMAKtic said, it's most likely way too late now. Same goes for your replies in other threads.
You can, but I'm afraid you won't. You'll rather achieve the opposite by bringing obsoleted threads back to the top.
Click to expand...
Click to collapse
ok
Hi guys, Last night I accidently unplugged my phone while installing ClockWORKMOD recovery. Now when I boot my device it is stuck on the Downloading screen. I tried everything including the posts here but the Odin software doesn't see my phone and removing the battery and reinstalling does nothing. I even wiped the phone and factory reset via the clockwork... No Luck. It will not install the Crash ROM either. I get error 7.
It seems like I bricked the phone but I know there is always a way back to life. At least I hope. Any help guys would be great.
thxs
Carlo
shpack said:
Hi guys, Last night I accidently unplugged my phone while installing ClockWORKMOD recovery. Now when I boot my device it is stuck on the Downloading screen. I tried everything including the posts here but the Odin software doesn't see my phone and removing the battery and reinstalling does nothing. I even wiped the phone and factory reset via the clockwork... No Luck. It will not install the Crash ROM either. I get error 7.
It seems like I bricked the phone but I know there is always a way back to life. At least I hope. Any help guys would be great.
thxs
Carlo
Click to expand...
Click to collapse
You need to properly install the correct drivers on your PC. There should be no reason that ODIN doesn't see your phone if they are installed correctly. A quick search of the forums should get you the proper drivers to install. You can also try Kies emergency recovery, but it is hit and miss. Good luck.
+1 if you can get into download you can Odin. Use the usb ports in the back of the pc. You might have to use a different computer also. For the life of me I can't get Odin on my pc to recognize the device but I have no problem with my laptop.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Wow, didn't we just fix this problem like 2-3 threads ago, IN THIS FORUM?
TheAxman said:
Wow, didn't we just fix this problem like 2-3 threads ago, IN THIS FORUM?
Click to expand...
Click to collapse
That's the thing, these exact same types of threads just keep rolling through one after the other...people don't search and they don't read. That's the reason they are in the situation they are in to begin with and it seems they just don't learn.
Fortunately, the AT&T S4 forum has come far enough along that the sticky threads and the threads like your guide can be linked for these people to put a little time into finding a solution for themselves. Most of them don't like it (they want it done for them), but if it is all they get, they will finally have to do something the right way on their own.
Actually, a few people are thankful for being pointed in the right direction, but most are still pissed because it means they have to do what they should have done in the first place...follow XDA rules, use the search function, and read. If you don't do everything for them and hand it to them on a plate they call you names and say you are a ****, unhelpful, etc... I just laugh about it because it becomes clear why their phone is F'ed up in the first place. The thing is, sometimes you just can't help people. Just every now and then, someone comes along that needs help and is willing to do things the right way.
You can NOT have kies drivers and samsung drivers loading at the same time, I do not use kies at all, and my pc has NEVER gave me a issue yet using odin, including in my G3 days. uninstall that worthless kies and proceed. If you have to use kies, load it as needed then remove it.
And as always with the lovely microsoft windows, after you un-install anything you have to reboot, for it to work properly.
Linux is my BUD!