Hello XDA,
Recently, a Samsung Captivate Glide was given to me to see if I could repair it. They told me the phone wouldn't turn on anymore, the screen remained black. Although they said they had just replaced the battery, I insisted that the battery was the problem. Upon hooking it up to a multimeter it became apparent that the battery was in deep sleep so I recovered it with a sliced USB cable. The phone then turned on to charge, but since I didn't feel like waiting for it to charge I inserted my S2 battery to boot it up.
Upon booting up the phone the Rogers screen came up (it's the Rogers model - sch-i927r), it adjust the brightness a bit and then proceeded to sit there forever. Since it wouldn't boot up I tried checking if Download Mode was still working. And it was! Same goes for the Android Recovery. Since this phone was never rooted or had a custom recovery it still had Gingerbread. Since the owner needed some files that were still on the phone I decided to flash TWRP, the CM11 compiled one, copy all the files to my PC and proceed to flash CM11 after making a backup.
However the phone refused to flash TWRP. I also tried CWM and going back to Stock but had no positive results. I even tried different Odin versions and different PCs. All of them gave out the same error that I have attached as a Picture. Upon googling it it seems like the storage is in read only mode, which I learnt from the Galaxy Tab 10.1 forums and also that the only solution would be to go back to Samsung.
Lastly I attempted to wipe from the built in recovery It asked for a password, however the original owner claimed he never had one. Upon forcing the flash by entering the wrong password the phone said it completed successfully but looking at the internal storage proves otherwise as all the files are still there. Trying to reboot to the system makes it either go to a black screen or corrupt the GPU memory (possibly - see attached pics.).
Looking around on the XDA forums I stumbled upon a thread by @steadfasterX which made a mod to boot the phone from an SD card. Since the eMMC of the phone is likely corrupt and causing this, could we use an SD card as the internal storage and boot up from there?
I am out of ideas. I don't have a backup of the EFS so I am being really cautious and fixing it wouldn't be worth it. So please help me! Any help is very much appreciated!
Thanks in advance!
chrismin13 said:
Hello XDA,
Recently, a Samsung Captivate Glide was given to me to see if I could repair it. They told me the phone wouldn't turn on anymore, the screen remained black. Although they said they had just replaced the battery, I insisted that the battery was the problem. Upon hooking it up to a multimeter it became apparent that the battery was in deep sleep so I recovered it with a sliced USB cable. The phone then turned on to charge, but since I didn't feel like waiting for it to charge I inserted my S2 battery to boot it up.
Upon booting up the phone the Rogers screen came up (it's the Rogers model - sch-i927r), it adjust the brightness a bit and then proceeded to sit there forever. Since it wouldn't boot up I tried checking if Download Mode was still working. And it was! Same goes for the Android Recovery. Since this phone was never rooted or had a custom recovery it still had Gingerbread. Since the owner needed some files that were still on the phone I decided to flash TWRP, the CM11 compiled one, copy all the files to my PC and proceed to flash CM11 after making a backup.
However the phone refused to flash TWRP. I also tried CWM and going back to Stock but had no positive results. I even tried different Odin versions and different PCs. All of them gave out the same error that I have attached as a Picture. Upon googling it it seems like the storage is in read only mode, which I learnt from the Galaxy Tab 10.1 forums and also that the only solution would be to go back to Samsung.
Lastly I attempted to wipe from the built in recovery It asked for a password, however the original owner claimed he never had one. Upon forcing the flash by entering the wrong password the phone said it completed successfully but looking at the internal storage proves otherwise as all the files are still there. Trying to reboot to the system makes it either go to a black screen or corrupt the GPU memory (possibly - see attached pics.).
Looking around on the XDA forums I stumbled upon a thread by @steadfasterX which made a mod to boot the phone from an SD card. Since the eMMC of the phone is likely corrupt and causing this, could we use an SD card as the internal storage and boot up from there?
I am out of ideas. I don't have a backup of the EFS so I am being really cautious and fixing it wouldn't be worth it. So please help me! Any help is very much appreciated!
Thanks in advance!
Click to expand...
Click to collapse
you can not boot from sd card, you can use sd card as system partition, but you still need place kernel+ramdisk on internal flash.
You can try to replace bootloader
bubor said:
you can not boot from sd card, you can use sd card as system partition, but you still need place kernel+ramdisk on internal flash.
You can try to replace bootloader
Click to expand...
Click to collapse
Thanks for the reply, I'll try updating the bootloader. Would it be risky though? I couldn't flash anything else and have no nandroid backup. Also, how would I go about using the SD Card as system?
EDIT: Risked it, flashed correctly but I still get the same error and I still have the Rogers bootloader. Any other ideas?
chrismin13 said:
Thanks for the reply, I'll try updating the bootloader. Would it be risky though? I couldn't flash anything else and have no nandroid backup. Also, how would I go about using the SD Card as system?
EDIT: Risked it, flashed correctly but I still get the same error and I still have the Rogers bootloader. Any other ideas?
Click to expand...
Click to collapse
maybe check "phone bootloader update" on the left side, I think I didnt check when I did update, and it worked without checking.
First try this pack: http://dualhoki.vim.hu/bubor/dev/I927UCLG9_OneClick.exe
Try to repartition with pit file ( put pit file in pit box, no other files, and check re-partition)
You can find an alternative of odin http://glassechidna.com.au/heimdall/ . I remember there are many other options in heimdall, maybe you can find usefull error messages.
bubor said:
maybe check "phone bootloader update" on the left side, I think I didnt check when I did update, and it worked without checking.
First try this pack: http://dualhoki.vim.hu/bubor/dev/I927UCLG9_OneClick.exe
Try to repartition with pit file ( put pit file in pit box, no other files, and check re-partition)
You can find an alternative of odin http://glassechidna.com.au/heimdall/ . I remember there are many other options in heimdall, maybe you can find usefull error messages.
Click to expand...
Click to collapse
Hello,
Sorry for the late response. I got around to trying most of that. First off the PIT File was something that I was looking forward to since it seemed the most likely solution. However it didn't work, giving out a similar message as everything else. The OneClick also failed with a similar message. As for heimdall I couldn't get the drivers to work but even if I had it wouldn't have helped anymore most likely.
I am out of ideas. I highly doubt this phone is recoverable at this point.
Thank you for all the help so far!
Anyone got any other ideas? I think it's safe to call it dead at this point, but I am willing to try anything to fix it!
Thanks.
Related
Try to flash to JH2 (and repartition 512) - the stock B model firmware.
If it fails - try to push one of complete roms (doc_kalpik) and install it using clockwork.
Otherwise have no idea what is wrong.
.....
I will download the firmware files now,
any instructions on how to use clockwork? and install the complete rom?
Did you perform a repartition when you reflashed ?
ignore me wrong thread!
inshadesofgrey said:
I will download the firmware files now,
any instructions on how to use clockwork? and install the complete rom?
Click to expand...
Click to collapse
isnt there a install guide in doc-kaplik topic? In clockwork (might need to push update.zip and rom manually - dont remember how) choose install zip from sdcard and navigate to file you need.
i did......still didnt work
Sounds like what mine was doing when the internal SD died.
dupel said:
isnt there a install guide in doc-kaplik topic? In clockwork (might need to push update.zip and rom manually - dont remember how) choose install zip from sdcard and navigate to file you need.
Click to expand...
Click to collapse
will this work even if i didnt have clockwork on my phone?
I flashed the stock JH2 with 512.pit and reparition checked, but the phone goes to the samsung logo, and flash animation and to a blank screen with only the buttons lit up........ah, am losing all hopes really fast.
Now that you are on jh2 take out sim leave external sd inside charge it til full, turn on while and it will boot, saying no memory going internal or external.
So far that would be doa, unless someone found a way to fix or reformat external card but most people that sent it for repair with these symptoms had done doa exchange like me twice or samsung replaced external module meaning it was hardware issue. Sorry.
Sent from my i9000M
it's a long shot, but can I buy an external SD card and run android from there?
I am guessing the only hope is to buy a new phone then?
inshadesofgrey said:
Hi guys, I have been a silent observer of XDA for a while now and you guys have helped through the past 4-5 phones that I've had - but now, I am stuck, so I thought I'll ask for help.
I have a galaxy S (i90000-GT) - originally from Bell, Canada but unlocked. I was running the XJPH with lag-fix and two days ago, when the phone rebooted, it got stuck in a boot loop, samsung logo with black screen comes on, and it starts all over again. Now, I can get into download mode and I followed the process to install JM8, and the stock file (the US Vibrant stock file) and I tried this as well:howto-froyo-fw-i9000xxjpm-upgrade-via-odin-root-recovery-2e-lagfix/[
But to no avail. The boot loop is still there. With JM8, the phone boots up and the goes beyond the flash samsung logo (with the music) but loads to a black screen, with the lights on.
Am really frustrated as this is my only work phone (and I go back to work tomorrow). Without the phone, I am pretty much screwed. I dont care about the Data on the phone (have performed 3-4 data wipes during installing the above mentioned roms) . So anything you can advise, will help!
any ideas?
Click to expand...
Click to collapse
Have you wiped your data/factory reset & wiped your cache? Many phones get stuck at startup because of them.
Hi guys,
New to XDA, I have a Note 2 which was getting a bit sluggish but worked fine, I rooted and custom flashed TWRP and saved a NANDROID BACKUP using TWRP to SDCARD and kept that on the desktop for safe keeping.
The phone worked fine after that for some time, Now spontaneously I woke up in the morning with the phone stuck on the samsung logo screen, so i knew it was softbricked but i cant understand how that happened.
First thing i tried apart from multiple restarts, removing battery etc, was then boot into custom recovery TWRP and try and restore from SDCARD nandroid backup. But it says EVERYTHING CAN'T be mounted!
E: Unable to find partition size for '/boot''
E: Unable to find partition size for '/recovery'
E: Unable to find partition size for '/modem'
E: Primary block device '/dev/block/mmcb1k0p16' for mount point '/data' is not present!
unable to mount '/data', EFS, System, cache and so forth.....
The phone was sincerely working fine and this happened seemingly randomly while asleep. Phone hadnt dropped and was connected to charger, and prior to this was restarted several times with no issues.
I have been looking at endless articles, I changed to CWM, TWRP, Philz and Stock Recovery and ALL OF THEM are unable to mount. So this does NOT seem to be a problem in the recovery. I used TWRP 2.8.0.1 for my Note 2 as well as 2.7.0.1. So I have a perfect NANDROID RESTORE on my SDCARD and DESKTOP to fix this but no way of mounting it to recovery?
Odin works fine and each time i flashed the recovery it would work fine. Is there some way of fixing it with ODIN?
Any input here would be greatly appreciated, and hopefully this helps someone else with the exact same issue.
Cheers.
the9kill said:
Hi guys,
New to XDA, I have a Note 2 which was getting a bit sluggish but worked fine, I rooted and custom flashed TWRP and saved a NANDROID BACKUP using TWRP to SDCARD and kept that on the desktop for safe keeping.
The phone worked fine after that for some time, Now spontaneously I woke up in the morning with the phone stuck on the samsung logo screen, so i knew it was softbricked but i cant understand how that happened.
First thing i tried apart from multiple restarts, removing battery etc, was then boot into custom recovery TWRP and try and restore from SDCARD nandroid backup. But it says EVERYTHING CAN'T be mounted!
E: Unable to find partition size for '/boot''
E: Unable to find partition size for '/recovery'
E: Unable to find partition size for '/modem'
E: Primary block device '/dev/block/mmcb1k0p16' for mount point '/data' is not present!
unable to mount '/data', EFS, System, cache and so forth.....
The phone was sincerely working fine and this happened seemingly randomly while asleep. Phone hadnt dropped and was connected to charger, and prior to this was restarted several times with no issues.
I have been looking at endless articles, I changed to CWM, TWRP, Philz and Stock Recovery and ALL OF THEM are unable to mount. So this does NOT seem to be a problem in the recovery. I used TWRP 2.8.0.1 for my Note 2 as well as 2.7.0.1. So I have a perfect NANDROID RESTORE on my SDCARD and DESKTOP to fix this but no way of mounting it to recovery?
Odin works fine and each time i flashed the recovery it would work fine. Is there some way of fixing it with ODIN?
Any input here would be greatly appreciated, and hopefully this helps someone else with the exact same issue.
Cheers.
Click to expand...
Click to collapse
It is possible that your Nandroid Backup is corrupt. It happens. Also, as you tried everything, I think you should flash fresh stock rom via odin.
Press thumps up if you found this suggestion helpful.
Sent from my GT-N7100 using Tapatalk
ceomaverick said:
It is possible that your Nandroid Backup is corrupt. It happens. Also, as you tried everything, I think you should flash fresh stock rom via odin.
Press thumps up if you found this suggestion helpful.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Hi ceomaverick,
Thanks for replying so fast, I may have not explained clearly but, the NANDROID BACKUP should be fine, its on the SD but cant be seen by any of the Recoverys (TWRP,CWM,stock,Philz) because nothing is able to MOUNT. So whether or not the nandroid backup is corrupt doesnt matter because we cant use it yet, as first problem is mounting to use the custom recovery restore.
Thanks for the suggestion about the Stock ROM , I have been downloading that for the past few hours! (XME-N7100XXUFNI4-20141020155451.zip) haha! That is what I will try next via Odin, just not sure how to do it safely. I will try and google and article for re-flashing stock rom via odin to make sure i tick all the correct boxes. If anything works will be back to update.
Cheers
P.s If anyone is interested in looking for this phones Stock ROM I found it here:
samsung-updates.com/device/?id=GT-N7100 (Select the one for your country/region)
the9kill said:
Hi ceomaverick,
Thanks for replying so fast, I may have not explained clearly but, the NANDROID BACKUP should be fine, its on the SD but cant be seen by any of the Recoverys (TWRP,CWM,stock,Philz) because nothing is able to MOUNT. So whether or not the nandroid backup is corrupt doesnt matter because we cant use it yet, as first problem is mounting to use the custom recovery restore.
Thanks for the suggestion about the Stock ROM , I have been downloading that for the past few hours! (XME-N7100XXUFNI4-20141020155451.zip) haha! That is what I will try next via Odin, just not sure how to do it safely. I will try and google and article for re-flashing stock rom via odin to make sure i tick all the correct boxes. If anything works will be back to update.
Cheers
Click to expand...
Click to collapse
Well, no hassle really. ODIN 3.09 does a great job. Just dump your file in AP tab and start after MD5 is verified. You should be fine. Welcome.
Sent from my GT-N7100 using Tapatalk
ceomaverick said:
Well, no hassle really. ODIN 3.09 does a great job. Just dump your file in AP tab and start after MD5 is verified. You should be fine. Welcome.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Bad news, Odin failed halfway through. Was able to boot back into download mode thankfully. But after rebooting again, seems the phone is now HardBricked. Meaning it wont even turn on.
Not sure what options are left now (if any). Anyone know what to do with a Note 2 hardbrick (apart from use it as an expensive door wedge).
Cheers
the9kill said:
Bad news, Odin failed halfway through. Was able to boot back into download mode thankfully. But after rebooting again, seems the phone is now HardBricked. Meaning it wont even turn on.
Not sure what options are left now (if any). Anyone know what to do with a Note 2 hardbrick (apart from use it as an expensive door wedge).
Cheers
Click to expand...
Click to collapse
This should not happen unless the cable or the usb ports are faulty. ( or if u have not followed the instructions correctly )
Anyway,
Can u still go to download mode? If yes, try a different cable and flash.
If no, use a USB jig to revive your phone. Ebay has them in plenty. With this you might get into download mode.
Also, are u flashing the correct firmware?
I have flashed custom ROMs n number of times without a single instance of failure.
Best of luck.
Sent from my GT-N7100 using Tapatalk
ceomaverick said:
This should not happen unless the cable or the usb ports are faulty. ( or if u have not followed the instructions correctly )
Anyway,
Can u still go to download mode? If yes, try a different cable and flash.
If no, use a USB jig to revive your phone. Ebay has them in plenty. With this you might get into download mode.
Also, are u flashing the correct firmware?
I have flashed custom ROMs n number of times without a single instance of failure.
Best of luck.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Hi again,
Yes, I can fully appreciate why you would say that, from what I see ODIN is very straight forward and unless you do something totally (silly), like jiggle the cable or do something midway it should not hardbrick. Therefore it makes sense you suggesting the cable is faulty, but it seemed to copy over 32GB of data seemlessly in one go. Although i will change the cable as a precaution as there is a slight cut.
When I say hardbricked, I mean hardbricked as in no recovery and no download mode, and no display whatsoever no matter what you do.
[UPDATE] Okay, the strangest thing happened. After a whole day of charging the phone, sometimes trying it on for luck, hoping something would happen. I went to the doctors and came back, and oddly enough the screen had life!!! Yes, this gets bizarre, I repeat a clearly hardbricked phone resurrected back to life with a screen showing ("A firmware upgrade encountered an error, please retry with kies") or something like that, so overjoyed with this sign of life I carefully put it into download mode and its now waiting.... But before I try Odin again, I think I will take a leaf from Ceomavericks suggestion and get a brand new cable from another samsung phone and use that this time.
By the way Ceomaverick, last time i just tried to flash to stock rom using AP, and kept autorebook and Ftime checked.
This time I am seeing on a thread to do the following, please advise (given that my TWRP doesnt mount anything at all).
It says do this: from: http://forum.xda-developers.com/showpost.php?p=43760271&postcount=22
Open ODIN, and check Re-Partition, Nand Erase All, Auto Reboot and F. Reset Time. Uncheck all other boxes. Click the PIT button and select the PIT file appropriate for your device (16GB or 32GB). Click the PDA file and choose the Stock Rom you downloaded. Press start and wait.
File Type: rar PIT_t03g_0907_16GB.rar - [Click for QR Code] (899 Bytes, 84 views)
File Type: zip BOOTLOADER_N7100.zip - [Click for QR Code] (1.03 MB, 75 views)
click start.
If everything goes well, the process should succeed and the phone should reboot. Don't wait for the phone to boot into android. Immediatly boot into recovery, factory reset the phone and wipe cache. Reboot to Android.
Now, if everything worked well, your phone should boot into Android. And then sort out the sleep of death issue.
I think I will wait for some feedback before doing this and just enjoy that my phone is mysteriously back in download mode, perhaps a hardware issue......
Another thread reading http://www.theandroidsoul.com/unbrick-restore-samsung-galaxy-note-2-gt-n7100/
Cheers
UPDATE:
Now that we are back to softbrick, I tried download mode and ODIN again, this time it fails right near the end. Last time it failed somewhere in the middle. So it seems to randomly fail and this is with the brand new USB Sony PS4 Cable. I ditched the worn out samsung cable because of the first fail. So twice its failed, but at different points. If it doesnt hardbrick again this time I suppose I will keep repeating till it passes.
For now just a straight rom flash, not sure if i should repartition with the before mentioned PIT Files and bootloader etc. Wont do that unless im told.
Thanks
Attached (Fail Image)
the9kill said:
UPDATE:
Now that we are back to softbrick, I tried download mode and ODIN again, this time it fails right near the end. Last time it failed somewhere in the middle. So it seems to randomly fail and this is with the brand new USB Sony PS4 Cable. I ditched the worn out samsung cable because of the first fail. So twice its failed, but at different points. If it doesnt hardbrick again this time I suppose I will keep repeating till it passes.
For now just a straight rom flash, not sure if i should repartition with the before mentioned PIT Files and bootloader etc. Wont do that unless im told.
Thanks
Attached (Fail Image)
Click to expand...
Click to collapse
Good news is you can visit download mode.
Ok. Alternative.
Download Philz recovery latest version. Flash it via ODIN. If it succeeds, u can flash a touchwiz rom
If that fails, then your partition table is corrupt (asumming thr r no hardware issues. )
Download firmware from different region for your note 2. India maybe. And flash them. May be this might do the trick.
If all above fails, it has to b a hardware issue.
Sent from my GT-N7100 using Tapatalk
ceomaverick said:
Good news is you can visit download mode.
Ok. Alternative.
Download Philz recovery latest version. Flash it via ODIN. If it succeeds, u can flash a touchwiz rom
If that fails, then your partition table is corrupt (asumming thr r no hardware issues. )
Download firmware from different region for your note 2. India maybe. And flash them. May be this might do the trick.
If all above fails, it has to b a hardware issue.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Hi ceomaverick!
Just going to highlight what you said with a few questions please.
"Good news is you can visit download mode. " - Yes, and once I tried to flash it for the second time it got hardbricked round 2. So somehow me flashing it gives it a seemingly temporary hardbrick. That was some hours ago and still no way to turn it on or get any sign of life, just like yesterday before it miraculously came to life again. Which since it has happened once I am guessing it will come back to life again as i followed the exact same procedure as before but Odin failed much later on into the process rather than halfway through.
"Download Philz recovery latest version. Flash it via ODIN. If it succeeds, u can flash a touchwiz rom" - Okay I had Philz before I will reflash it when it comes up and i suppose search for a note 2 touchwiz rom. Philz as before wont be able to mount anything though, even sim card. As i did this prior none of them, TWRP, Philz or CWM can mount anything. So even if i have the ROM file i wont be able to use it on SD if the SD doesnt mount, but i can try it through Odin?
"If that fails, then your partition table is corrupt (asumming thr r no hardware issues. )" - I suspect this is the case hence not mounting, so do I use that PIT file and select Re-Partition in Odin to resolve that?
"Download firmware from different region for your note 2. India maybe. And flash them. May be this might do the trick." - Good idea, while the hardbrick is waiting to resurrect (LOL), I will start a download.
"If all above fails, it has to b a hardware issue. " - Again something I suspect, from forum could be this dreaded eMMC "insane samsung chip" problem which is as far as i know a 16gb internal SD? If so, perhaps there is a way to put in a 16gb SD and edit boot to mount from there as internal instead from the eMMC? Sorry if thats way out there, but i read something like this once.
Appreciate the help, waiting for it to spring back into life
the9kill said:
Hi ceomaverick!
Just going to highlight what you said with a few questions please.
"Good news is you can visit download mode. " - Yes, and once I tried to flash it for the second time it got hardbricked round 2. So somehow me flashing it gives it a seemingly temporary hardbrick. That was some hours ago and still no way to turn it on or get any sign of life, just like yesterday before it miraculously came to life again. Which since it has happened once I am guessing it will come back to life again as i followed the exact same procedure as before but Odin failed much later on into the process rather than halfway through.
"Download Philz recovery latest version. Flash it via ODIN. If it succeeds, u can flash a touchwiz rom" - Okay I had Philz before I will reflash it when it comes up and i suppose search for a note 2 touchwiz rom. Philz as before wont be able to mount anything though, even sim card. As i did this prior none of them, TWRP, Philz or CWM can mount anything. So even if i have the ROM file i wont be able to use it on SD if the SD doesnt mount, but i can try it through Odin?
"If that fails, then your partition table is corrupt (asumming thr r no hardware issues. )" - I suspect this is the case hence not mounting, so do I use that PIT file and select Re-Partition in Odin to resolve that?
"Download firmware from different region for your note 2. India maybe. And flash them. May be this might do the trick." - Good idea, while the hardbrick is waiting to resurrect (LOL), I will start a download.
"If all above fails, it has to b a hardware issue. " - Again something I suspect, from forum could be this dreaded eMMC "insane samsung chip" problem which is as far as i know a 16gb internal SD? If so, perhaps there is a way to put in a 16gb SD and edit boot to mount from there as internal instead from the eMMC? Sorry if thats way out there, but i read something like this once.
Appreciate the help, waiting for it to spring back into life
Click to expand...
Click to collapse
If the firmware from other region fails, then find pit file for 16gb to flash. If that too fails, I think your phone needs hardware repair.
Sent from my GT-N7100 using Tapatalk
Hello all,
i got a new phone, so decided to wipe mine before trying to sale, I wiped it from recovery tool which is CWM , I must have done something very wrong because when rebooting it askedme for my pin code again, so I knew it didnt delete anything, I type my pin code in, then the phone company screen appears for a few seconds and then finally the droid picture (green robot) shows up and it gets stuck there forever, nothing else can be done, I restart and same happens all logos and splash screens play until it ask for my pin code and after that it gets stuck in the same screen.
I already loaded full stock rom using odin but didnt fix it, I cannot acess the external sd card anymore , something I did I guess.
sumary:
CWM is on it, cant acess external card, and wont mount internal in windows
I already loaded a full rom using oding but it still asks for my pin code.
I dont know what else to do, please any help is appreciated.
My phone is galaxy s3 telcel mexico
luisfer99 said:
Hello all,
i got a new phone, so decided to wipe mine before trying to sale, I wiped it from recovery tool which is CWM , I must have done something very wrong because when rebooting it askedme for my pin code again, so I knew it didnt delete anything, I type my pin code in, then the phone company screen appears for a few seconds and then finally the droid picture (green robot) shows up and it gets stuck there forever, nothing else can be done, I restart and same happens all logos and splash screens play until it ask for my pin code and after that it gets stuck in the same screen.
I already loaded full stock rom using odin but didnt fix it, I cannot acess the external sd card anymore , something I did I guess.
sumary:
CWM is on it, cant acess external card, and wont mount internal in windows
I already loaded a full rom using oding but it still asks for my pin code.
I dont know what else to do, please any help is appreciated.
My phone is galaxy s3 telcel mexico
Click to expand...
Click to collapse
Did you have encryption enabled? Reading your post it sounds like you might have.
You might want to try flashing the stock recovery then doing a full wipe in it. That should clear up any encryption problems. I'm pretty sure this recovery is generic for both i747/i747m, but you should consult the linked thread for more details.
You might have to Odin your stock ROM on it again after the wipe to get a working ROM on the phone.
jason2678 said:
Did you have encryption enabled? Reading your post it sounds like you might have.
You might want to try flashing the stock recovery then doing a full wipe in it. That should clear up any encryption problems. I'm pretty sure this recovery is generic for both i747/i747m, but you should consult the linked thread for more details.
You might have to Odin your stock ROM on it again after the wipe to get a working ROM on the phone.
Click to expand...
Click to collapse
Thanks you very much, that step fixed everything , phone is now working and clean. thanks again!
I have what's probably a unique situation, though I hope not. For background info, I bought two I747s, one white and one blue, each with issues, but I intended to put parts together to end up with one good one.
When I did a factory reset on the blue one via the recovery menu, it returned a bunch of errors along the lines of "failed to mount /data." Then when it rebooted it would hang on the Samsung logo. Back in recovery mode it returns more of the same errors just booting into recovery mode, and factory reset still returns more of the same errors and doesn't fix anything. I flashed 4.3 with Odin in an attempt to fix it, but I got the boards mixed up, and that one had 4.4 on it, not 4.1 like I thought. I'm pretty sure it's hard bricked now (that whole can't downgrade thing) because it's unresponsive to everything. Though my computer does recognize that it's plugged in, more on that later.
So I figured, fine, I screwed up, I'll just use the other board with 4.1 on it from the white phone. Except when I did a factory reset on that one, it did the exact same thing! Same errors, same problem stuck at the Samsung logo. Except this time I'm not flashing sh*t until I know exactly what I need to do to fix it. In another post where the guy had the same issue with 4.1.1, it was solved by flashing 4.3 with Odin. And another post where the guy had no idea what version he had, he just knew it was lower than 4.3, his problem was also solved by flashing 4.3, But since my last efforts failed miserably, I'm very reluctant to try it until I get some knowledgeable input. I don't remember exactly which version is on there, it's 4.1.something. I'd also prefer not to upgrade beyond 4.1 because I'd like to unlock it and from what I'm reading you can only do it for free if you're on 4.1. So I guess I need a link to an Odin flashable 4.1 package?
As for the poor blue phone that used to have 4.4.something, and was mistakenly flashed with 4.3, I've heard about JTAG but I don't quite understand it, and I'm not sure it would work in my case since a lot of what I'm reading says that bricking which occurs from downgrading is often unfixable. However, Windows recognizes that a device is plugged in when I attach it via USB. It shows up in the Device Manager as QHSUSB_DLOAD. I am currently researching more on this and the method of booting from an SD card, except I don't have an SD card reader at the moment.
Any assistance, advice, links, information, and plain ole encouragement are always welcome and appreciated.
For the phone running 4.1, flash any stock rom in Odin. After flashing, boot into recovery and perform a factory reset, then boot the phone and use the free method to sim unlock. The important thing is to have the stock 4.1.1 dialler in order to access the hidden menu options?
For home hard bricked phone, you will have to try the debrick image method. If it doesn't work, a jtag service should be able to force flash a rom to the phone.
Wow, that was like a crazy fast reply!
What if the phone is 4.1.2? Can I still flash 4.1.1? I'm on the hunt for a 4.1.1 stock rom now.
Yes, you can flash 4.1.1 from 4.1.2.
audit13 said:
Yes, you can flash 4.1.1 from 4.1.2.
Click to expand...
Click to collapse
Apparently not always. I downloaded and flashed 4.1.1 with Oden 3.07, it rebooted, showed the android image like it was updating, progress bar finished, and then it just went blank. Now both phones are in the same condition of being hard bricked and showing QHSUSB_DLOAD in the device manager.
This is strange. I have downgraded approximately 10 i747m phones from 4.1.2 to 4.1.1, unlocked using the free method, and re-flashed back to 4.1.2 after unlocking.
http://forum.xda-developers.com/showthread.php?t=2371897
What options did you check in Odin? Where did you get the 4.1.1 ROM? I ask because the stock ATT 4.1.1 rom was apparently removed from sammobile.com.
How did you confirm that the phone was running 4.1.2?
I checked only auto reboot in Odin.
I found this link sammobile.com/firmwares/database/SGH-I747/ in this thread http://forum.xda-developers.com/galaxy-s3-att/help/downgrade-att-running-stock-4-4-2-rom-t3170938 , 7th post
The download was going absurdly slow, so I googled the exact file name being downloaded which was, I747UCDLK3_I747ATTDLK3_ATT, and found a google drive link at https://drive.google.com/file/d/0B_UTWXKFnZoNVFdSVjJEZlMwZjA/edit which was the first result after searching for the file name if that link doesn't work. I'm downloading the slow one now to compare it to the one I got from google drive.
I'm unsure if the phone was 4.1.1 or 4.1.2, that's why I asked if it's possible to flash 4.1.1 on top of 4.1.2. I was only trying to do a factory reset originally and had no intentions of flashing anything. I just wanted to wipe out all the crap on it from the previous user so I had only glanced at the version out of curiosity to see if it was unlockable via the free method. I remember it was 4.1.something.
I have an SD card reader on order. Hopefully I'll be able to unbrick one of them.
Do you, or anyone else, have any idea why a simple factory reset would cause errors like I described and then hang on reboot? At that point both phones were 100% factory and I hadn't done anything to them except put a battery in them to power them on. I've done a factory reset on four other S3s and this didn't happen.
It is definitely possible to flash 4.1.1 over 4.1.2 because the bootloader could not be downgraded until the mjb version.
That's what I've been reading. So where did I go wrong? Any idea why a factory reset would screw up like that?
Did you confirm the bootloader before flashing?
audit13 said:
Did you confirm the bootloader before flashing?
Click to expand...
Click to collapse
No, because I had no intentions of flashing it when I tried to do a factory reset. Then after that went bad it wouldn't boot, and I don't know how to check the boatloader when a phone will only go into recovery mode.
Where did you see reference to 4.1? It's possible that the modem or baseband was 4.1 but the bootloader was 4.3.
Under about device and then Android version. The one where if you tap it a lot you get the jellybean android that pops up. It wasn't the baseband version because that's a much longer number with the model number in it.
That screen doesn't tell you the bootloader.
As I said, I didn't check for the bootloader version before I ran into trouble because I only wanted to do a factory reset and I didn't intend to flash anything. I wouldn't imagine that it would have a different bootloader than the OS version unless that can happen without any user intervention because the previous owner was only concerned with selfies and games. She certainly didn't modify anything.
I cant explain what happened. This has never happened to me after flashing about 10 phones.
I believe it has something to do with the errors that were produced while trying to do a factory reset. What bothers me is that both phones did the exact same thing. Normally I'd say it was something I did, except that I didn't do anything but put a battery in them, boot up, find lots of junk installed, and then attempt a factory reset. On the first phone, I rebooted into recovery and tried it from there. On the second phone I tried it from inside the OS. Same results on both. The phones ran fine before that.
Any advice on how to do the boot from an SD card, or how to do the JTAG thing? I've been reading a lot but the information jumps around a lot. I'm comfortable with soldering and have an IT background if that helps.
It's possible that the recovery was corrupt or the partitions were corrupt.
Whenever I factory reset a phone, I always boot into recovery to do that, not from within the ROM.
Sounds to me like you did nothing wrong.
Did the previous owner have the phone from the time it was new?
Edit: for the phone that you flashed with 4.1.1, Odin said "pass" in the status window and the it auto rebooted?
audit13 said:
Did the previous owner have the phone from the time it was new?
Edit: for the phone that you flashed with 4.1.1, Odin said "pass" in the status window and the it auto rebooted?
Click to expand...
Click to collapse
I don't know for sure if she had it from new. Yes, for both phones Odin said pass in the window and then it rebooted. I had walked away when Odin finished with the first phone. I came back and it was dead. The second one I watched and it showed the android with the wireframe in his guts and the progress bar which moved across, and then it just went blank.
There were error messages about the partitions when I did the factory reset IIRC. Perhaps the recovery or the partition was corrupted like you said. It's just odd that both had the exact same identical problem with the exact same results. That's why I think that it must have been something I did, except that I didn't DO anything other than initiate a factory reset.
I took an i747m and reflashed stock the Telus 4.4.2 ROM.
In download mode, you should see the green Android guy with the words "Downloading...Do not turn off target" and a blue progress bar moving from left to right.
I did not check reset in Odin. Once it finished flashing the ROM, I removed the USB cable, removed the battery, replaced the battery, and booted the phone. I the Android guy with the wire frame for a few seconds, the screen went blank, and the phone started up with the Samsung logo.
Since you were getting errors with mounting the different partitions, you may have needed to flash the PIT and PDA files but I can't really say for sure as I have never encountered this problem.
I normally verify everything before I use Odin because phones that I have been given to fix have had all sorts of weird configurations.
You'll have to try the debrick guide. of use a jtag service. You could also do what I did and that is to look for people with phones that have a damaged screen and buy they at a steep discount.
Expert advice needed please. This is a puzzle that someone might enjoy solving.
Although I have a fair bit of experience with flashing, I tried to flash my 8.0 for the first time and it has dramatically failed. It was probably my fault - not an uncommon story.
What is less common is that I am struggling to figure out how to undo the damage I've done. What's really making this difficult is that no computer recognises the device as USB any more so I can't use Odin, Kies, etc to repair or return to stock. I have tried everything I can think of to deal with the USB issue, the usual cable, driver, port nonsense. I don't think the USB problem is Windows now.
I suspect one of these things may have happened:
The USB port just went bad coincidentally during this flash process (charge, no data). I have ordered a new port but it will take weeks to arrive.
Has the device come out of Developer/USB debugging mode somehow? I can't tell because I can't boot to an OS.
I wonder if the ROM flash has corrupted the firmware the deals with USB - is that possible? Where is the devices USB drivers located? Is it in the bootloader, something like BIOS?
I'm suspicious of the bootloader, as the screen is weirdly corrupted now when I turn on or reboot the device - fuzzy white lines rather than a logo - but that disappears when OS tries to load, or I go into Recovery/Download.
I actually did do a backup of the original ROM to the SD card; but restoring it doesn't work, just produces an endless Samsung boot, even if I then wipe and reset.
I can get into Download mode, and a Recovery (Philz for N5120) but since I can't connect to the devise with USB in any way, it's very hard to get the Recovery to flash anything new and useful. I did put my SD Card in another phone and copied over the stock ROM zip from Samsung, but it refuses to flash - I think because it doesn't like Philz Recovery? I can't think how to replace Philz Recovery with another by flashing, without USB.
I may have to wait to replace the USB port, but I fear that won't fix it. Until then, I can only think of one other thing to try, and that is to copy a ROM onto the SD Card through another phone, and try to flash it. Lineage doesn't flash, and nor does the stock zip I got from Samsung. Would anything else work?
Can I flash an alternative recovery from within the recovery? Philz only lets me flash zips, not img or tars.
So it's quite a mess, but if anyone has a brilliant idea of how to get out of this, I'd love to hear it.
THANK YOU if you have a genius idea.
So after a few days of working on this, I did manage to resolve it, and I thought I'd just add a note about how I escaped this obscure problem.
The device went bad because I stupidly flashed an incompatible Recovery to the device and somewhere between doing this, backup and restoring and flashing, it corrupted mostly everything including something in the bootloader.
Oddly enough, the solution seemed to be to mess up the Recovery even more by flashing something even more random - it seems this provoked the device into restoring its own basic Recovery. Using this to wipe and reset the device somehow enabled Download mode's USB interface to start working again so I was able to use Kies to return to stock, which repaired everything including the bootloader.
Finally, I flashed the correct Recovery for this device, and then managed to flash the ROM I wanted. A happy ending to a stressful story; the device now works better than it ever has done before.