AFTER ATTEMPTED DEV MANGO UPDATE 7661 build RECEIVED ERROR CODE C101002E
NOTE:I HAVE SUCCESSFULLY UPDATED 3 OTHER SAMSUNG FOCUS CELL PHONES AS WELL AS DOWNGRADED/FLASHED BACK TO ROM 7004 WITH NO PROBLEMS-SO IDK WUTS UP WITH THIS PHONE
I TRIED TO FLASH ROM BUILD 7004-BUT DURING THE PROCESS THE DOWNLOAD SCREEN ON MY CELL PHONE WENT BLANK.
I REMOVED THE BATTERY & WAITED FOR APPROX 5 MINUTES. THEN REINSERTED IT. ATTEMPTED POWERING UP & FELT VIBRATION BUT NO SCREEN DISPLAY. TRIED TO FIND RESTORE BACKUP ON ZUNE, BUT WOULDN'T LET ME RESTORE FROM ZUNE. ALSO COULDN'T FIND BACKED UP PKS FILE EITHER ON WP7 BACK UP TOOL--TRIED TO RETRIEVE FROM ARCHIVED FILE; BUT KEPT POSTING UNSUCCESSFUL LOAD OF ARCHIVED FILE. (also tried charging battery overnight, as well as used fully charged battery from 1 of my other samsung focus phones that are MANGOED already-but no luck either.)
I WAS ABLE TO OBTAIN DOWNLOAD MODE WITHOUT SCREEN DISPLAY & I
REATTEMPTED FLASHING ROM BUILD 7004--THIS TIME THE PHONE WENT COMPLETELY DEAD DURING THE ROM FLASHING; RECEIVED FAILED FLASH MESSAGE & NOW THE PHONE WILL NOT TURN ON, WILL NOT SOFT OR HARD RESET, WILL NOT GO INTO RECOVERY MODE, OR GO INTO DOWNLOAD MODE!!
ANY SUGGESTIONS--WILL A JIG POSSIBLY WORK?? ANY INPUT WOULD BE APPRECIATED!
I'm not sure a jig is going to help. But I guess your only possibilities are trying a jig or RMA. If you want to make a jig, read this post I wrote.
Good luck!
Heathcliff74
Heathcliff74
Thanks again for your quick response-- I'm going to try a jig & follow your post.
Wish me luck!!!
Related
I used the phone for about 2 days after I updated to mango. While I was at class the phone died because of low battery. Once I plugged it back up it's been stuck at the samsung screen for three days now. Tried format, tried download mode but can't get the software to do anything when I open it just says "cannot image file", and I tired recovering the phone with zune. It will get to Step 2 and do nothing more even after running for a good 10 hours. Any suggestions? Using Samsung Focus 1.3
bulletdog said:
I used the phone for about 2 days after I updated to mango. While I was at class the phone died because of low battery. Once I plugged it back up it's been stuck at the samsung screen for three days now. Tried format, tried download mode but can't get the software to do anything when I open it just says "cannot image file", and I tired recovering the phone with zune. It will get to Step 2 and do nothing more even after running for a good 10 hours. Any suggestions? Using Samsung Focus 1.3
Click to expand...
Click to collapse
There is a chance that the battery went below control charge and it appears dead. Before you do anything to the phone I recommend to replace the battery. There is a control circuit in the battery that tracks capacity. If the capacity falls below a critical value, it won't charge anymore and the battery appears dead.
edit: sorry, never mind, I didn't read your post carefully enough.
Do you have an expansion microsd card? if so, pull it out... might just be a cooincidence that you had one fail.
ROCOAFZ said:
Do you have an expansion microsd card? if so, pull it out... might just be a cooincidence that you had one fail.
Click to expand...
Click to collapse
Never used a SD card with phone, I went to ATT store and tried a new battery, didn't help. From reading it sounds like a firmware ordeal but like I said before the software for tye binaries won't do anything
tried running zune restore again, this time got a error message. Downloaded the windows phone support tools and and ran it. This time got a error of 80004005
This happened to me when I was trying to hack update to mango. I fixed it by doing these steps.
1) Restore it to the original ROM. I think it is 7004.
Here is a good tutorial (just read the description no need to watch the vid http://www.youtube.com/watch?v=hvw5gLY6sOc
2) Use Chevron hack to update to nodo.
3) Update to Mango
Not sure if it has changed where the device will auto update from 7004 to 7720, so you can check that right after you flash it.
Sk8rjwd said:
This happened to me when I was trying to hack update to mango. I fixed it by doing these steps.
1) Restore it to the original ROM. I think it is 7004.
Here is a good tutorial (just read the description no need to watch the vid
2) Use Chevron hack to update to nodo.
3) Update to Mango
Not sure if it has changed where the device will auto update from 7004 to 7720, so you can check that right after you flash it.
Click to expand...
Click to collapse
Followed the link and stuck at connecting my phone while it's in download mode, the computer wont recognize it so I can't start the flash. The search continues.
UPATE:
Finally got the computer to recognize the phone, I had to download the samsung usb drivers from their website. Installing mango right now. Should I try a recovery now that the phone is working that was made before the orginal mango update? Or should I just suck it up and start from scratch. THANKS Sk8rjwd!
bulletdog said:
I used the phone for about 2 days after I updated to mango. While I was at class the phone died because of low battery. Once I plugged it back up it's been stuck at the samsung screen for three days now. Tried format, tried download mode but can't get the software to do anything when I open it just says "cannot image file", and I tired recovering the phone with zune. It will get to Step 2 and do nothing more even after running for a good 10 hours. Any suggestions? Using Samsung Focus 1.3
Click to expand...
Click to collapse
i got this problem with my omnia gt 8350 , battery die, and now my phone is brick no power no nothing replace the battery still no go. no power, when i plug to usb the pc telling me to install driver called QHSUSB installed susses ,and in the device manager i can see the phone is detected, by the windows but, still cant reflash it, i dont have the rom for this device plus, i cant boot to download mode.
find another phone with a similar battery, running something other than wp7 and charge it till boot. you should be good to go from then on. happened to me once. lucky my dad has an incredible s so my mozart battery fit there and i could charge. i was on beta mango though. rtm mango fixed this issue for me where in several cases my battery died but i still managed to get it charged up normally
I have spent the past 3 hours scouring over these forums before doing a post and I could find lots of great information if I could just get past the perpetual loop and access either the Recovery or Download Modes of my phone.
It is a Telus Samsung Galaxy Fascinate [SGH-T989D] and I have been tinkering with it for that past 24 hours to get it rooted and play with some of the ROMs out there.
I have gotten past the 3e Recovery Issues, resolved a Soft Brick and tested out 3 ROMs but now I am completely stuck and I think it is entirely my own fault but now I need some assistance in getting out of it.
This morning I threw on ICS_NBv9.2 and as it warned it went into a bit of a panic mode and has hit a perpetual Boot Loop. Now every post I have read says go into Download Mode and Odin back to Stock...I can't...it comes up with the Battery Image twice and then starts the boot up cycle all over again. The other option is to Flash the ROM again...problem is it continuously cycles through the Boot and never goes anywhere.
I have tried multiple Cables, reinstalled the USB Drivers, tried on 4 different Computers (2 Linux and 2 Windows) and well lets just say I am at the end of my rope.
Is there any known way to stop this kernel panic and let me get back to stock and put a functional ROM on the phone.
Thanks in Advance.
I may be able to help you...
Here are some solutions I can think of from the top of my head.
Try to see if your phone will connect to samsung kies on your computer via USB, there should be a way to restore it from there.
If you can't do this, then the next step would be to try and enter CWM Recovery mode (you should have this installed already, just look online how to enter into recovery mode). Next, mount your phone using recovery and put a stable rom (.zip) onto your phone. Factory reset, and wipe your phone, then flash the rom.
If you can't enter CWM Recovery, then the next step I can think of is to find a stable rom and flash it through ODIN.
If this isn't working either, then you just made yourself a very stylish paper weight! congrats.
There may stil be hope that if you call your carrier and tell them a sob story like, "my phone restarted on it's own and now it won't work properly." - and answer no if they ask you if you flashed, or downloaded 3rd party apps - then they might send you a free replacement.
Next time you want to flash your phone, remember... MAKE A BACKUP (nandroid) FIRST. That way if anything goes wrong, you can just restore it back the way it was.
Here is a site that may help you as well for rooting and making a backup for the t-989D (samsung galaxy s2 x - telus):
http://androidforums.com/galaxy-s2-...d-ultimate-root-optimization-guide-steps.html
Good luck,
J
Try This..
Remove Data Cable from Phone
Remove battery and re insert after 3-5 secs
now try to enter Downloading mode..
then insert data cable. and flash stock FW.
it should work..
The Paper Weight Theory
Thanks Input_Method and ranjan.
Unfortunately the reboot takes effect and cycles through before Kies, ODIN or anything else can take hold of the device.
I have tried the cable trick, Recovery Mode is a no go and it would appear to be an issue with CWM mismatch which is causing the reboot.
Hoping that a local "phone hacker" can help me out with a JTAG reboot this weekend but I am not overly optimistic.
Thanks again.
I wanted to share my knowledge and experience from the past 2 days. Most of the help came from guides and posts on this forum so I wanted to give that back.
We were trying to root the SGS4G and because we're noobs we made the mistake of thinking it was a Vibrant. Got a Vibrant ROM and tried to flash it though Odin WITH re-partition checked. Everything we read said if you do either one of these things, you will brick your phone.
Sure enough we bricked the phone. It was trying to boot into the Vibrant ROM but was getting stuck on the word 'Vibrant' and then showing a whole lot of weird colored pixels. We then learned we'd made a massive mistake and that the phone wasn't a Vibrant after all.
We got a stock ROM for SGS4G and started trying to push them through Odin. Faced countless FAILS and freezes and finally it took us to the Recovery Mode and we tried the Restore option. It booted into a crippled SGS4G ROM. When it booted, it vibrated every 10 seconds or so and it had a null IMEI and unknown baseband.
We tried following a guide that wanted to change some text in the nv_data.bin but the numbers we were meant to be editing (0018810?) didn't exist in our nv_data.bin. So that didn't work for us.
In the meantime we tried to flash the stock ROM in Odin but kept getting FAILs and Freezes. With this step we lost even the crippled operating system and couldn't reach anything except the 'phone --!-- computer' screen. Luckily, this acts the same as download mode, so not bricked. We kept trying to push the stock SGS4G stock ROM (Froyo 2.2) several times and failing.
At one point we got a completely black screen, wouldn't turn on. Bricked again. We found this post on RootzWiki and it worked for us that time and brought it back from the black screen to download mode http://rootzwiki.com/topic/1820-how-to-unbrick-your-sgs4g/
Somehow we ended up at this guide here on XDA for fixing the "null/null" IMEI http://forum.xda-developers.com/showthread.php?t=1142829
We followed that guide. When you add the PIT file it automatically checks 'Re-Partition' in Odin, we didn't uncheck it. Bricked again. It was stuck on the Samsung logo and when we tried to get to download mode it got stuck on a black screen with the loading circle/lines and 2 computers were giving 'The USB device has malfunctioned' when we plugged it in. The unbrick guide above (RootzWiki) didn't help this time. We tried restarting the computer, let the phone rest without battery for half an hour, held power button for a minute without battery, still nothing.
Finally I accidentally pressed the power button (rather than the volume buttons to get into download mode) and it went to the samsung logo (as expected) and after that I was able to get into download mode. The key to this I think is to keep on trying powering on normally then try download mode over and over and eventually it should get unstuck and the computer should recognize it again.
Once I had it back in download mode, I followed this guide again BUT!!! I made sure to un-check re-partition and I did not check "Phone EFS Clear" (because I had tried that already before it was bricked and wanted to see if a straight ROM would work first). Everything worked perfectly, I got my IMEI and Baseband back, without modifying anything.
I don't know if this was a miracle, or if any of it will work for anyone else, but the moral of the story is don't give up even if you've done the absolute worst possible thing. I don't even think hardbrick exists on this phone after everything we were able to save it from.
Cheers
Hardbricks do exist on this phone but you have to try really hard to do it. A few people have managed it. Way to stick with it and recover your phone. I've done that more times than I can count.
hechoen said:
Hardbricks do exist on this phone but you have to try really hard to do it. A few people have managed it. Way to stick with it and recover your phone. I've done that more times than I can count.
Click to expand...
Click to collapse
I didn't feel like i really hard bricked it until i saw the USB computer connection error "device pluged in malfunctioned" in more than one PC.
Then i really felt like its a hardware BIOS chipset level problem now but man...
That story cracked me up. That is exactly why I spend days reading before I even root my phone. I made the mistake one time on my old G1 and it could not be revived.
Congrats on getting it working. (especially without flooding the q&a with redundant questions that have been described in detail several places )
hani1400 said:
I wanted to share my knowledge and experience from the past 2 days. Most of the help came from guides and posts on this forum so I wanted to give that back.
We were trying to root the SGS4G and because we're noobs we made the mistake of thinking it was a Vibrant. Got a Vibrant ROM and tried to flash it though Odin WITH re-partition checked. Everything we read said if you do either one of these things, you will brick your phone.
Sure enough we bricked the phone. It was trying to boot into the Vibrant ROM but was getting stuck on the word 'Vibrant' and then showing a whole lot of weird colored pixels. We then learned we'd made a massive mistake and that the phone wasn't a Vibrant after all.
We got a stock ROM for SGS4G and started trying to push them through Odin. Faced countless FAILS and freezes and finally it took us to the Recovery Mode and we tried the Restore option. It booted into a crippled SGS4G ROM. When it booted, it vibrated every 10 seconds or so and it had a null IMEI and unknown baseband.
We tried following a guide that wanted to change some text in the nv_data.bin but the numbers we were meant to be editing (0018810?) didn't exist in our nv_data.bin. So that didn't work for us.
In the meantime we tried to flash the stock ROM in Odin but kept getting FAILs and Freezes. With this step we lost even the crippled operating system and couldn't reach anything except the 'phone --!-- computer' screen. Luckily, this acts the same as download mode, so not bricked. We kept trying to push the stock SGS4G stock ROM (Froyo 2.2) several times and failing.
At one point we got a completely black screen, wouldn't turn on. Bricked again. We found this post on RootzWiki and it worked for us that time and brought it back from the black screen to download mode http://rootzwiki.com/topic/1820-how-to-unbrick-your-sgs4g/
Somehow we ended up at this guide here on XDA for fixing the "null/null" IMEI http://forum.xda-developers.com/showthread.php?t=1142829
We followed that guide. When you add the PIT file it automatically checks 'Re-Partition' in Odin, we didn't uncheck it. Bricked again. It was stuck on the Samsung logo and when we tried to get to download mode it got stuck on a black screen with the loading circle/lines and 2 computers were giving 'The USB device has malfunctioned' when we plugged it in. The unbrick guide above (RootzWiki) didn't help this time. We tried restarting the computer, let the phone rest without battery for half an hour, held power button for a minute without battery, still nothing.
Finally I accidentally pressed the power button (rather than the volume buttons to get into download mode) and it went to the samsung logo (as expected) and after that I was able to get into download mode. The key to this I think is to keep on trying powering on normally then try download mode over and over and eventually it should get unstuck and the computer should recognize it again.
Once I had it back in download mode, I followed this guide again BUT!!! I made sure to un-check re-partition and I did not check "Phone EFS Clear" (because I had tried that already before it was bricked and wanted to see if a straight ROM would work first). Everything worked perfectly, I got my IMEI and Baseband back, without modifying anything.
I don't know if this was a miracle, or if any of it will work for anyone else, but the moral of the story is don't give up even if you've done the absolute worst possible thing. I don't even think hardbrick exists on this phone after everything we were able to save it from.
Cheers
Click to expand...
Click to collapse
Wheooooooooowwww,..you just UNBRICKED mine, I know of the Battery pull etc...but the post you referenced
is MAGIC
This was not my first Rom nor Root on this phone, it weirdly happened while doing the GB starter....via ODIN, which i also used before..no clue what went wrong, oh well...
Thank you, thank you "i did"....Yohoooo
Yup i agree i like to read, reread then read as i do. This way i got a pretty good understanding of what I'm doing. Btw i have just started using one click and it is sooooo simple. I love it.
Sent from my SGH-T959V using XDA App
The link for fixing null/null IMEI is not working.
http://forum.xda-developers.com/showthread.php?t=1142829
diavel said:
The link for fixing null/null IMEI is not working.
http://forum.xda-developers.com/showthread.php?t=1142829
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=881162
Im still carrying this phone, stupid baseband unlock for iphone won't come out now I am carrying 2 phones, one as an ipod touch and the galaxy s! Good story, hope it can help others, but I am prepared to jump off of this bandwagon anytime now!
I followed this links w.mobilescommunity.com/android-tips-tutorial/208463-how-root-samsung-galaxy-s-blaze-4g.html[/url] instructions to a "T" and when the phone came back on it stops at the welcome screen no matter what. I tried to install ClockworkMod Recovery per these instructions /theunlockr.com/2012/04/17/how-to-root-and-install-clockworkmod-recovery-on-samsung-galaxy-blaze-4g/[/url] and it seemed to work as I get the OMR mode when I try to get the download screen without having it already cable connected to the PC. When I have it connected to the PC I am able to get to the "Download" mode. OI! I never have had a problem rooting before. The stock OS ICS 4.0.4 was on it and I bought it new from T-Mobile and then it did the OTA update a week ago. I have had nothing on it other than stock and a few camera apps. I have already tried to return it to OEM with the OMR recovery but its still the same, always booting to the welcome screen. When I try to get it into a mode, ether the recovery mode or the download mode, it sometimes vibrates several times and then "May" go into one or the other depending if its cable tethered or not. HELP PLEASE, I disabled and this is my only outside contact short of coming into town to use the Internet at a cafe. Thanks, Jeff
Blaze Soft Brick
fallendaemon said:
I followed this links w.mobilescommunity.com/android-tips-tutorial/208463-how-root-samsung-galaxy-s-blaze-4g.html[/url] instructions to a "T" and when the phone came back on it stops at the welcome screen no matter what. I tried to install ClockworkMod Recovery per these instructions /theunlockr.com/2012/04/17/how-to-root-and-install-clockworkmod-recovery-on-samsung-galaxy-blaze-4g/[/url] and it seemed to work as I get the OMR mode when I try to get the download screen without having it already cable connected to the PC. When I have it connected to the PC I am able to get to the "Download" mode. OI! I never have had a problem rooting before. The stock OS ICS 4.0.4 was on it and I bought it new from T-Mobile and then it did the OTA update a week ago. I have had nothing on it other than stock and a few camera apps. I have already tried to return it to OEM with the OMR recovery but its still the same, always booting to the welcome screen. When I try to get it into a mode, ether the recovery mode or the download mode, it sometimes vibrates several times and then "May" go into one or the other depending if its cable tethered or not. HELP PLEASE, I disabled and this is my only outside contact short of coming into town to use the Internet at a cafe. Thanks, Jeff
Click to expand...
Click to collapse
----- Did you ever get your Blaze fixed?....
pretty much the same problem i have!!! i currently have the samsung galaxy s blaze and rooted it to the custom rom from konane using the odis program, it said passed and auto rebooted my phone, but when it gets to the home screen where you touch the android to set up your phone like its brand new, when i hit the android bot all that happens is a message force closing a bunch of apps appear. i can get to the download mode to install new roms and i've tried to re root back to the stock rom but now my computer doesnt recognize my phone. i've downloaded and installed the samsung drivers from several different forums including the ones recommended here but still nothing. what im wondering is if theres a way to install the rom or driver from an sd card to the phone or something else that im missing, or is my phone just screwed? any and all help is greatly appreciated.
Hi everyone,
I'm hoping that someone can help me out with my device. I have a rooted sm-p900 that was working fine until a month ago when I tried to flash [ROM][7.1.x|SM-P900| Unofficial LineageOS 14.1 (v1awifi). I was busy multi-tasking and made the stupid mistake of flashing the rom before updating the BL. Since trying to do so, I have not been able to get past the first screen that says "Samsung sm-p900" . After the logo disappears, my screen remains lit but is just black.I could not restore my backup after either.
Where I am now:
- I can still access and use T.W.R.P. (latest 3.1.1) (If TWRP is left alone for too long, the device will reset to the same black screen and hang forever. If flashing a rom is taking long, the device will restart mid-flash as well.)
- I can still access download mode and use odin as well.
- I have since flashed the appropriate BL but that has not changed anything.
-I have tried clean flashing a magnitude of different roms and still come across the same problem.
I honestly have no idea how I can fix the device and have tried everything I know how. I would love to get it back as soon as possible. Any help is greatly appreciated, so thank you in advance!
jp2572 said:
Hi everyone,
I'm hoping that someone can help me out with my device. I have a rooted sm-p900 that was working fine until a month ago when I tried to flash [ROM][7.1.x|SM-P900| Unofficial LineageOS 14.1 (v1awifi). I was busy multi-tasking and made the stupid mistake of flashing the rom before updating the BL. Since trying to do so, I have not been able to get past the first screen that says "Samsung sm-p900" . After the logo disappears, my screen remains lit but is just black.I could not restore my backup after either.
Where I am now:
- I can still access and use T.W.R.P. (latest 3.1.1) (If TWRP is left alone for too long, the device will reset to the same black screen and hang forever. If flashing a rom is taking long, the device will restart mid-flash as well.)
- I can still access download mode and use odin as well.
- I have since flashed the appropriate BL but that has not changed anything.
-I have tried clean flashing a magnitude of different roms and still come across the same problem.
I honestly have no idea how I can fix the device and have tried everything I know how. I would love to get it back as soon as possible. Any help is greatly appreciated, so thank you in advance!
Click to expand...
Click to collapse
Have you tried taking it completely back to stock via Samsung Kies on your PC?
Sorry I don't have complete details, but it goes something like this (and if you search this site or Google, you'll find a good write-up on how to do a complete recovery using Kies):
1. If you can, make a backup using TWRP - if not, you are going to lose everything because of the next steps
2. Download and install the Kies software from the Samsung site and install it on your PC (I grabbed both versions, can install both on the same PC at the same time)
Make sure that it installs the Samsung USB driver
3. Connect to the tablet using the OEM cable - if you get a reaction from Kies, great
4. Somewhere in the Kies menu, you can tell it to do a complete recovery, including bootloader- if I remember correctly, you'll need your serial number (Sorry, been 18 months since I did just about the same thing and was able to recover it from my FUBAR, and I no longer run Windows so I can't step thru it)
It will go through downloading and flashing your tablet back to the state it was when you pulled it out of the box.
If you get to that point, you will have to go the whole route (including loading TWRP) to get it back to Lineage. It took me about two weeks to get it back to the way I had it before I was flashing and reading a book and talking to my wife all at the same time and didn't pay attention to what I touched on screen.
I apologize for the rambling and not having definitive statements, but I'm drugged up and been awake for the last 36 hours, and at my age that isn't a good combination.
Thank you so much for your help! I couldn't end up using that method because kies would not recognize my device for anything. It did get me inspired to try fixing it again however and it worked!
If anyone ever encounters the same or a similar problem, I just tried re-rooting it using odin and cf's autoroot file. It allowed me to be able to install roms again.
rhricik447 said:
Have you tried taking it completely back to stock via Samsung Kies on your PC?
Sorry I don't have complete details, but it goes something like this (and if you search this site or Google, you'll find a good write-up on how to do a complete recovery using Kies):
1. If you can, make a backup using TWRP - if not, you are going to lose everything because of the next steps
2. Download and install the Kies software from the Samsung site and install it on your PC (I grabbed both versions, can install both on the same PC at the same time)
Make sure that it installs the Samsung USB driver
3. Connect to the tablet using the OEM cable - if you get a reaction from Kies, great
4. Somewhere in the Kies menu, you can tell it to do a complete recovery, including bootloader- if I remember correctly, you'll need your serial number (Sorry, been 18 months since I did just about the same thing and was able to recover it from my FUBAR, and I no longer run Windows so I can't step thru it)
It will go through downloading and flashing your tablet back to the state it was when you pulled it out of the box.
If you get to that point, you will have to go the whole route (including loading TWRP) to get it back to Lineage. It took me about two weeks to get it back to the way I had it before I was flashing and reading a book and talking to my wife all at the same time and didn't pay attention to what I touched on screen.
I apologize for the rambling and not having definitive statements, but I'm drugged up and been awake for the last 36 hours, and at my age that isn't a good combination.
Click to expand...
Click to collapse
Try updating the bootloader again using odin
When this has happend factory reset
Flash the rom, addonsu and gapps in the same TWRP session
The rom should work then, I've been happily using it for about 6months now