Hi guys.
My uncle gave me his Galaxy S3 GT-i9300, asking me to fix it. The reason is that when turned on it is stuck at the Samsung Galaxy S3 logo, without booting to the system. I can boot to Download Mode, speaking about it later. I can boot to recovery, but it gives a lot of errors about can't mount partitions or directory and files not found (such as the photo below in the attachments). Searching a while I understood that these errors are caused by broken partitions. I've successfully booted in Download Mode, but I can't flash any file with odin. If using the .pit file to repartion the eMMC, it stucks to "Get Pit For Mapping" step or it fails with "Re-partition operation failed", it depends on the Odin version I use to do it. I've let the computer to his things with the "Get Pit For Mapping" for over a night, without success. Still stuck. I've tried to flash stock boot.img, stock recovery.img and various other single images from the Stock Firmware downloaded from Sammobile. I've also tried to flash twrp and cwm. No succes, all of them stock at a certain percentage. Boot and Recovery Image always fail at 2/3 of the operation with "Complete(Write) operation failed". Neither "Nand Erase all" option works, it also fails.
I've tried so many things, including booting from the SdCard short-circuiting a resistance ç(found a giude about it on xda), no success also with this. I can't neither flash bootloader or so.
Tried to flash change cable, change port or so. I've also changed computer, no success.
My idea was to boot into TWRP (my favourite custom recovery) to save at least the photos and the music, and then flash the stock firmware.
I actually can't resolve this. Can you please help me? All help will be appreciated.
P.S.: I could try to ADB Sideload the rom, but I couldn't find .zip packages of official OTA updates.
P.P.S.: Is there a way to pull out files through ADB Sideload? I couldn't find one...
Thanks, EmaMaker.
It really looks to me like the internal memory chip has failed.
audit13 said:
It really looks to me like the internal memory chip has failed.
Click to expand...
Click to collapse
Agreed. All options have been exhausted. It's dead.
As for the adb question, only if you have a working recovery that is adb enabled like twrp or cwm..
audit13 said:
It really looks to me like the internal memory chip has failed.
Click to expand...
Click to collapse
Oh come on, it can't be dead after a trivial recharge...
My s3's memory chip is still alive after 6 years and only the power button broke. And my new s3's main board (which was produced in 2012 as by written on the board) works perfectly.
Isn't there a way of completely erase the memory and reflash it, without problems?
I could make a friend change the emmc for me, replacing it with my old main board's one. Once an emmc is extracted and works as a stand-alone chip, can i try to recover files from it?
There are many s3 users whose phones are completely functional after many years of use but failed memory chips in any phone is possible.
I have a nexus 5, Samsung s4, and Samsung note 2 with defective internal memory chips. These were given to me by family and friends to use for parts. Before taking them apart, I tried everything I could to flash the phones without luck.
By normal means the phone is f00ked. Once you get to the point where it asks for pit file 9 times out of 10 the nand is corrupt. The problem is how sd memory works in the first place and its inherent flaws. That is why some phones work forever while others can die within days.
As the phones were built in many different factories using many differently sourced parts the chances of "Sudden Death Syndrome" is quite high. Some manufacturers actually purchase prebuilt cheap Chinese phones and rebrand them as their own.
If you wanted to change the nand I'm not sure if any of the chips are married to each other so that's a risk in itself. You can swap the board out with a salvage phone. You can try jtag. All of which could cost you the same as buying another s3. They are too cheap nowadays.
If you want a wierd example, my stock rooted s3 borked royally from turning off in the middle of the night due to no power. Turned it on and it puked a load of errors "e: unable to mount /****". I flashed the latest official cwm and then flashed the stock recovery and as I rebooted thinking that it was dead it booted to os!. All errors solved!. Lost root completely but at least I could flash it back to stock and start over.
That was when I started to see a pattern on the forums where twrp was the common denomination between the cases of borked phones so I googled it and there is documentation on twrp github which states the same but the cause is currently unknown. This is where I always state to be careful rooting your phone in the first place as twrp is the only recovery for nearly all phones, it has an inherent fault that no-one knows the cause of and it can lead to a dead phone. Where any other recovery is available I'd recommend that over twrp. I also noticed that the most common combo is twrp and custom roms as THE most likely to go tits up across all devices. If you must root keep it stock root.
Otherwise if twrp didn't kill it then its genuinely a dead nand, probably faulty at birth and it was a matter of time. I honestly think Samsung cheaped out on parts for the s3 and that is why so many fail.
shivadow said:
By normal means the phone is f00ked. Once you get to the point where it asks for pit file 9 times out of 10 the nand is corrupt. The problem is how sd memory works in the first place and its inherent flaws. That is why some phones work forever while others can die within days.
As the phones were built in many different factories using many differently sourced parts the chances of "Sudden Death Syndrome" is quite high. Some manufacturers actually purchase prebuilt cheap Chinese phones and rebrand them as their own.
If you wanted to change the nand I'm not sure if any of the chips are married to each other so that's a risk in itself. You can swap the board out with a salvage phone. You can try jtag. All of which could cost you the same as buying another s3. They are too cheap nowadays.
If you want a wierd example, my stock rooted s3 borked royally from turning off in the middle of the night due to no power. Turned it on and it puked a load of errors "e: unable to mount /****". I flashed the latest official cwm and then flashed the stock recovery and as I rebooted thinking that it was dead it booted to os!. All errors solved!. Lost root completely but at least I could flash it back to stock and start over.
That was when I started to see a pattern on the forums where twrp was the common denomination between the cases of borked phones so I googled it and there is documentation on twrp github which states the same but the cause is currently unknown. This is where I always state to be careful rooting your phone in the first place as twrp is the only recovery for nearly all phones, it has an inherent fault that no-one knows the cause of and it can lead to a dead phone. Where any other recovery is available I'd recommend that over twrp. I also noticed that the most common combo is twrp and custom roms as THE most likely to go tits up across all devices. If you must root keep it stock root.
Otherwise if twrp didn't kill it then its genuinely a dead nand, probably faulty at birth and it was a matter of time. I honestly think Samsung cheaped out on parts for the s3 and that is why so many fail.
Click to expand...
Click to collapse
Thanks for your exausting answer. I will search more about jtag in the next days. I tried to flash both twrp and cwm, none of them worked.
Related
I used Oden to flash a Samsung Galaxy S II rom to it and now, it only shows the Samsung logo at bootup. No recovery menu. If I try to access the recovery menu, it kicks me out and reboots. Samsung galaxy player 5.0 All Touch Buttons including home.
If you can get into download mode by holding volume down at boot, you can just reflash stock.
Sent from my YP-G70 using Tapatalk
Um, okay, for future reference NEVER FLASH ANYTHING NOT SPECIFICALLY MADE FOR YOUR DEVICE! I learned that the hard way, so not saying your stupid, just think a little more before you try to flash a rom for a dual core phone that's only resemblence to a Galaxy player is the word Galaxy. I find that for some reason, each phone has to have a different strain of android, and their roms never, NEVER, mix. So, I am stating this just to warn others new to android, not to make you look bad (I made a similar mistake of trying to flash cwm that someone assured me couldn't possibly brick my device, what a noob I was!).
Yup... NEVER flash something not designed for your device unless you know EXACTLY what the hardware differences are and how to deal with them, or you've been given specific instructions on how to port firmwares to your device.
(I9100 ROMs are so easy to run on I777 that they can be autoported with a CWM-flashable package now, but that's because the I777 is 95% identical to I9100. There will be nothing that can be "hellraised" to the Players, except possibly being able to creat "common" ROMs that target both International and US with a small zip file containing the differences flashable in CWM.)
Mate, I'm in the same boat where you used to be. Just a little worse.
Long story short: flashed, by mistake, the entire i9000 rom, including boot loaders, through Odin. Got a "black screen", "no reaction" brick. Computer won't detect no matter what button combo I throw at it.
Samsung Galaxy Wi-Fi 5.0"
YP-GB70CWXAZ (8GB) brazilian edition
I need some details about jtag and the micro-usb port. Also, in the current state, can I try to format a sd card & see if the player recovers from it? Like the Samsung Development Board? When everything is screwed, the usb pins can be used as a jtag port to avoid opening the device, even though I already did it.
PS: I've already located the 12 pins (jtag) & another 4 points on the main board. Just don't know how to check if the second ones are also jtag. The blue coating is also scrapped & ready.
Thanks.
Peace.
You might want to try AdamOutler oneclickrecovery before messing with JTAG. You can find it here.
This will upload a bootloader so you can re-flash the device with odin.
I have tried to recover my YP-GB70 (32gb korean version) with AdamOutler tools with 80% success.
Anyway thanks a lot for the tool and your great help.
What I did:
under odin I flashed original YP-GB70 32gb PIT plus the provided "AdamOutler bootloader and the latest korean firmware (pb is the same with any earlier FW version)
The result i got is almost perfect, i passed SAMSUNG logo, the boot ring tone and went the GALAXY sky where it stay looping. (All wipes where done before.)
My questions are:
-What is missing in this Flash process?
-Is the bootloader specific for US version or device related?
-Any idea of what I should do to succeed?
You are welcome to expertize this issue because a solution will be a good tool for many imprudent guys like me.
attached picks of 3 diferent trials done lately.
best regards from France
Lolo9393
I installed Chainfire3D (after hearing good things about it) and then realized the problems it causes, so i deleted the app and then its CF3D drivers from system/lib which didnt work properly anyways. Upon restart device doesnt boot anymore :crying: (welI maybe its on cause the battery generates heat, but its black screen) I also couldnt get titanium backup to work in the past just in case something like this happens cause it was constantly stuck on yahoo finance when backing up.
My main issue is I had alot of things (worth a couple days) installed on my phone, and dont want to lose all of it. Bad thing i didnt realize there is Nanadroid backup (cause its my first android phone) which works unlike titanium quickly and efficiently, but backing things up now after black screen is pointless no? i can acess CWM recovery, but dont want to factory reset yet.
So any way to inject those stupid CF3D drivers via ADB? Or maybe backup everything but that certain system/lib folder?
Edit: i ran into this:
On CF-Root just boot into recovery, ADB shell to it, and type "rootsh" (instead of "su") to have root shell access... if anything goes wrong, just "mount /system" and "/system/lib/cf3d_uninstall.sh" to remove the CF3D driver and restore the old one. Not very likely it will happen, but a good fallback option in case of issues (no need to reflash firmware or restore backup)
Click to expand...
Click to collapse
, unfortunately cf3d_uninstall.sh was one of the files i deleted, but maybe if someone who has Chainfire3D installed on S3 LTE can share that file, i can then inject it and restore the old drivers?
Seems mine suffered a similar fate.
a friend suggested SPB 3D loaded it. It sucked and caused lock-ups and delays. I uninstalled and the phone seemed to be fine after.
I plugged the phone in to charge overnight and about an hour later when going to bed the screen was stuck on the boot-up screen.
has not gone past this since.
Wanted to get the firmware restored and after trying to find a suitable stock one I took it to my SP for repair they tried to flash it but it fails every time, they said the motherboard is toast.
It will boot to flash mode so it can be uploaded but it doesn't work. Odin says no partitions.
Tried Heimdall it detects the phone but it tells me the image is corrupt and I also have no idea how to repair the partition that seems to be lost.
white 16GB Tmoble GS3
Actually my current issue is similar, it boots up says galaxy S3 then black screen. I can connect to odin, i can boot into clockwork, and i can flash roms, ODIN says everything is successful after i flash but when it boots it still goes to a black screen. this happened after i flashed a rom(that worked) and flashing a kernel that also previously worked....after that its been stuck....i can flash whatever with success but i cannot seem to get it past that Galaxy S3 screen....
I flashed the new FreeGS3 rom, and the TGST STOCK ICS Alpha37 kernel i cleared caches and wiped davliks not too sure where to go from here.....Do i need factory tmoble GS3 PIT file?
Redsalamander said:
Seems mine suffered a similar fate.
a friend suggested SPB 3D loaded it. It sucked and caused lock-ups and delays. I uninstalled and the phone seemed to be fine after.
I plugged the phone in to charge overnight and about an hour later when going to bed the screen was stuck on the boot-up screen.
has not gone past this since.
Wanted to get the firmware restored and after trying to find a suitable stock one I took it to my SP for repair they tried to flash it but it fails every time, they said the motherboard is toast.
It will boot to flash mode so it can be uploaded but it doesn't work. Odin says no partitions.
Tried Heimdall it detects the phone but it tells me the image is corrupt and I also have no idea how to repair the partition that seems to be lost.
Click to expand...
Click to collapse
Not to offend anyone the Dev app said he wasn't going to support it for the galaxy s3
Sent from my SCH-I535 using xda premium
Turns out mine was a faulty mainboard after dragging their feet to repair it including a delay due to them wanting to verify warantee with proof of purchase samsung finaly agreed to swap it out for a new one.
Redsalamander said:
Turns out mine was a faulty mainboard after dragging their feet to repair it including a delay due to them wanting to verify warantee with proof of purchase samsung finaly agreed to swap it out for a new one.
Click to expand...
Click to collapse
Well thing is on my end...i didn't flash whatever the OP had flashed. What i DID do though is flash a rom and a kernel on the same cwm event. when it rebooted...it just does this....
i have a backup file....its on my laptop though....with only using odin or cwm how can i push that file onto my phone? My CWM doesnt have USB mount else id just do that.....?
My phone was working fine on Thursday morning. Around noon I went to check my phone and it was off. I turned it on and it gets stuck at the initial Samsung boot screen. With the research and testing I have done so far the current state of the phone is...
- Any attempt at normal boot results in getting stuck at the initial Samsung boot screen.
- I am NOT able to enter recovery mode by any method I've tried so far.
- I AM able to enter download mode by holding volume down or both volume buttons while inserting the USB cable.
- The phone DOES charge via USB.
- Connecting to the computer gives a "USB Device Not Recognized" error.
- I have tried cleaning the USB port with alcohol pads as best I can and it had no effect.
- ADB does NOT see the devices (and I know ADB/Drivers/USB Debugging/etc is configured correctly because I develop with this device)
- The phone is NOT rooted nor have I changed ANYTHING within the past few weeks.
- The device IS carrier unlocked (not that this should matter at all).
- The phone does have Google Voice with Groove IP Lite installed (and I remember news that the GV API would change around this time, maybe it broke something?)
- ODIN 3 v1.85 can SOMETIMES see the phone at 0:[COM3] (I'm still trying to figure this out. I THINK it only works if I put battery in, boot to download mode by inserting USB, then after it boots to download I remove and re-insert USB to re-connect the device on the computer, but I'm not certain yet)
I was going to replace the device next month anyways so I don't really care about the device itself. What I am trying to figure out is whether there is any way to recover certain data such as memo notes or game/app data from the device? If I tried to install a new rom via ODIN will that wipe out my app data and notes and stuff or would the data persist like it would for a carrier-pushed update? Can I somehow pull this data off the device from within download mode before I try to flash the device? Am I going in the wrong direction and should be trying something entirely different to begin with? What do you guys suggest? Thanks.
I was waiting to see if anyone else would pitch in with useful information about recovering your data. However, since no one has, I can say that I am pretty sure that you will not be able to recover anything currently in any of the system partitions. (System, kernel, data, preload, etc.) Once you recover your phone, you will still almost certainly have the information that was on your internal sdcard (USB Memory.)
Using Odin3, you should open Odin on the desktop of your pc first, then use the method that works for you to get into download mode, and Odin should recognize your phone.
I understand that you are not too concerned about the device. I would point out that a working I777 that is in good working condition with a clean esn is worth probably $100.00 to $125.00 on Swappa. It would be in your best interest to recover the phone. (Or if that's too much trouble, you can always send it to me, lol.)
Since the phone can enter download mode and be recognized by the computer, it is almost certainly recoverable. The only possible reason that it would not be recoverable is if the problem is due to damaged emmc memory in some part of the system partitions. When you flash the stock firmware, or any firmware, you will lose any possible access to the data partition. You will most likely be required to enter recovery after the flash to perform a wipe data/factory reset before the phone will boot into the system. The data will not persist as it would for an over the air or kies update. But again, as I said in the other thread, you may retain the game data if it is saved to the sdcard. Memo notes are definitely stored in the data partition, so those are lost.
The only thing you can do within download mode is flash firmware, nothing else is possible. I don't know of any other direction you could be going than what we have discussed so far.
As I said before, someone with good developer skills and understanding may be able to help, but as far as I know, no one with that level of skill hangs out in this forum, or has any interest in the I777 any more.
creepyncrawly said:
I was waiting to see if anyone else would pitch in with useful information about recovering your data. However, since no one has, I can say that I am pretty sure that you will not be able to recover anything currently in any of the system partitions. (System, kernel, data, preload, etc.) Once you recover your phone, you will still almost certainly have the information that was on your internal sdcard (USB Memory.)
Using Odin3, you should open Odin on the desktop of your pc first, then use the method that works for you to get into download mode, and Odin should recognize your phone.
I understand that you are not too concerned about the device. I would point out that a working I777 that is in good working condition with a clean esn is worth probably $100.00 to $125.00 on Swappa. It would be in your best interest to recover the phone. (Or if that's too much trouble, you can always send it to me, lol.)
Since the phone can enter download mode and be recognized by the computer, it is almost certainly recoverable. The only possible reason that it would not be recoverable is if the problem is due to damaged emmc memory in some part of the system partitions. When you flash the stock firmware, or any firmware, you will lose any possible access to the data partition. You will most likely be required to enter recovery after the flash to perform a wipe data/factory reset before the phone will boot into the system. The data will not persist as it would for an over the air or kies update. But again, as I said in the other thread, you may retain the game data if it is saved to the sdcard. Memo notes are definitely stored in the data partition, so those are lost.
The only thing you can do within download mode is flash firmware, nothing else is possible. I don't know of any other direction you could be going than what we have discussed so far.
As I said before, someone with good developer skills and understanding may be able to help, but as far as I know, no one with that level of skill hangs out in this forum, or has any interest in the I777 any more.
Click to expand...
Click to collapse
Yeah. It was worth a shot but I think I am out of luck on this.
I tried using Odin 3 v1.85 and also Odin 3 v3.09 from 2 separate computers with several cables in order to flash the PDA/AP from 'I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5' but without any luck. After 10-20 minutes Odin says 'fail' and there is never any change on the phone screen at any point in the process. I also tried the 'I777UCKH7 OCD No BL.exe' one-click link from your signature links with a similar result. The program starts with factoryfs.img but the progress bar never moves and after 10-20 minutes it fails. The phone never shows any change at any point in the entire process.
I might be doing something wrong (perhaps with Odin I MUST flash the bootloader/phone/csc as well?) but it's looking more and more like the phone has a memory issue or something like that. Do you have any other suggestions? I'm willing to try anything at this point just to get the phone running for a few weeks while I decide on the next phone (hmmmm, Nexus 5, OnePlusOne, G3 or...)
Regardless of all that, thanks for all your help so far!
Both of those packages are complete in themselves. On the UCMD8 you only need the one tar in the PDA slot.
To discover if there is nand read/write corruption try this:
Instructions to clear nand read/write corruption. Instructions are specific. Do in order, and don't skip.
Odin3 v1.85 is recommended.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
For the record, no one writes those kinds of instructions as well as you do - both you and 4-2ndtwin have been great examples of how to help people for many years.
Thank you both for showing the rest of us how to convey help in an eloquent manner.
I tried your instructions with both v1.85 and v3.09 and although there was a brief glimmer of hope it looks like my device really is locked up beyond any further use. Odin shows the 'KERNEL' flash and the progress bar fills up in a second or two but then it goes to '<ID:0/003> NAND Write Start!!
' and like every other attempt it either hangs here indefinitely or fails after 10-20 minutes.
The only other things I can think of is to do a repartitioning or to physically disassembly the phone to look for any trouble spots (maybe a little dust or corrosion is shorting something) but of course being realistic there is virtually no chance of these having an effect.
I don't frequent the boards enough to know the standards here but I can say thank you for all the help you have provided. It's more than anyone can ask for such an old (but still good!) device.
Maybe it will take a jtag repair to get it going again, or perhaps there is actual eMMC damage, which can also be repaired. Whatever the problem is, a good option at this point would be the folks at Mobile Tech Videos repair shop. They have an excellent reputation here in the forum, and can do all sorts of repair.
This is my first post to a forum, so please bear with me...
So a few days ago, a friend of mine got a Verizon Samsung Galaxy S4 from someone, for free. He got it for free because the screen's glass is cracked a bit, and the phone is bricked; the previous owner didn't know what to do with it. I decided I would try to fix it, because if I do, I might be able to buy it off him and give it to my little sister, who currently has a dying iPhone 5C.
When I turn on the phone, it boots, showing the samsung logo, showing the red Verizon screen, and playing the boot tune. Then, just when you'd expect it to go to the OS, it shows a screen which at the top reads "Device memory damaged". Below that, it says "The data partition has been corrupted. You need to reset your phone to factory defaults. This will erase all your data." And below that is a button, which says "RESET PHONE". Tapping on it does nothing.
I have worked with android phones before (rooting, ROMs, locked bootloaders, bricked phones; even all these things on a Galaxy Gear smartwatch), and I know what the data partition is. I remembered that the recovery on samsung phones have an option to wipe the data partition. So I tried to access the recovery menu by holding Power, Home, and Vol+ when the phone is off. It doesn't work either . It shows the Andy robot laying on its back with a door open on its belly, with a warning icon popping out. So the recovery is dead...
I thought I could try to fix the recovery by flashing it with Odin :fingers-crossed:; Didn't work. It is blocked because the phone can't verify version . Then, after a little more research, I realized I might be able to fix the recovery by flashing a whole stock ROM. I don't know what firmware the phone is running, because I can't ask the previous owner. So I tried a few KitKat ones, and they were all rejected by the phone. Then I booted the phone back up, and I realized the RESET PHONE button acted like it was part of a Lollipop UI (There is a darker circle that extends from the part of the button where you tap). So I went back into download mode and tried to flash the 2 OTA versions of Lollipop (OC1 and OF1). The error this time was "SW REV. CHECK FAIL : fused : 8 , Binary : 6". This may or may not be the error I got before with the KitKat ROMs. I don't remember, and I'm not at my desktop to try the old ROMs.
After looking up this error, I found no exact results, but there were ones with a similar error. People said that it means a ROM is being flashed that is too old to pass the downgrade prevention system. I've been trying to flash what seems to be the latest firmware revision for this phone (OF1). Any ideas? Are the OSs I'm trying to flash somehow too new for the phone (even though I've tried all of the stock Lollipop ROMs. Should I give the phone back to my friend and tell him it's dead?
Thanks in advance!
I can't post images because I haven't posted here (or on any forum, for that matter) before.
Well, it seems really bad but you can try Samsung Smart Switch or Verizon Wireless Software Upgrade Assistant to repair the phone, else way JTag it's another option
Fuse 8 is OF1
Matthew M. said:
Fuse 8 is OF1
Click to expand...
Click to collapse
Thanks for the info. I tried flashing that version. Didn't work. I ended up taking my own broken S4 I had laying around, which had a smashed screen but a supposedly good Mainboard, and transferred the mainboard to my friend's bricked S4. Now it boots fully, and I made use of my old phone that was laying around.
BTW, do you know where or how you found out which version Fuse 8 represented? I'd like to learn more about this kind of stuff.
you probably needed to flash a lowship odin tar and repartition
Legitsu said:
you probably needed to flash a lowship odin tar and repartition
Click to expand...
Click to collapse
Sorry, what do you mean by "lowship"? I did use a PIT file to repartition, which didn't work, possibly because the OS being flashed with it wasn't being accepted...
evanzolman said:
Sorry, what do you mean by "lowship"? I did use a PIT file to repartition, which didn't work, possibly because the OS being flashed with it wasn't being accepted...
Click to expand...
Click to collapse
a normal odin tar will not fix a bad partition regardless of the .pit you need a tar that s a _user_Low_ship todo a full format odin was failing because the partitions where screwed and you weren't using the correct image
go to sammobile.com they have all the s4 all variants roms.
evanzolman said:
Thanks for the info. I tried flashing that version. Didn't work. I ended up taking my own broken S4 I had laying around, which had a smashed screen but a supposedly good Mainboard, and transferred the mainboard to my friend's bricked S4. Now it boots fully, and I made use of my old phone that was laying around.
BTW, do you know where or how you found out which version Fuse 8 represented? I'd like to learn more about this kind of stuff.
Click to expand...
Click to collapse
I am not aware of a definitive guide on the fuses. I found it by trial and error
Envoyé de mon SM-G903F en utilisant Tapatalk
So i'm helping a buddy out that was having an issue with several Note 2's that were purchased from a company that restricted their employees access to a lot of things on the phone. My friend handed a couple off to me. The first one was not passcode locked and it was a breeze (Basically just enabled USB Debugging). It is up and running. The other ones are passcode locked and when you try to go into wipe the data/factory reset from recovery it says "MDM does not allow factory reset". The Note 2 I'm having issues with in particular has a locked bootloader on KitKat 4.4.2 through Verizon.
I've spent almost literally every waking moment trying to find a way around this issue. I may have compounded it though. I discovered ODIN, flashed the stock firmware in the hopes that it would clear the phone. It did not (password was still in place). I then decided to flash the stock firmware with the .Pit file for an SCH-I605 and made sure re-partition was checked as well as erase nand. After the process completed successfully and the phone rebooted it will no longer boot beyond the Verizon screen. I still have access to recovery and download mode but in recovery its throwing out a bunch of command lines such as E:failed to mount /data etc. I've tried to reflash the stock firmware with and without the .pit file to no avail.
In the mean time I've tried to unlock the bootloader, attempted auto root, and install custom recoveries to see if I could some how get around the MDM issue. I've also attempted to install or flash from ADB and its still the same deal.
Anyway I'm tired, kind of exhausted, and not really sure what avenues I have left. That's where I'm hoping some of you guys come in. If you have any questions for me let me know and I'll try to shed some more light on it for you. Data DOES NOT matter to me so if you can think of anyway I can get this thing completely wiped out it so I can start from scratch it would be greatly appreciated, Thanks.
Is it just one phone with this problem or several? The mounting issues are becoming more common around here, and seem to be internal memory failure.
http://forum.xda-developers.com/note-2-verizon/help/stuck-boot-file-exists-t3286946
Droid_Nut said:
Is it just one phone with this problem or several? The mounting issues are becoming more common around here, and seem to be internal memory failure.
http://forum.xda-developers.com/note-2-verizon/help/stuck-boot-file-exists-t3286946
Click to expand...
Click to collapse
Well tonight I'll be getting my hands on a couple other test SCH-i605 phones that are in the same situation (Password locked and no ability to wipe from recovery) and I'll put them through the paces to see if I wind up with the same issue and get back with you on it.
The basic issue with this phone is just after trying that repartition with the pit file it doesn't want to boot beyond the verizon logo anymore and thats when it started throwing those errors in recovery. It could be a coincidence I guess.
I've been messing with Heimdall today to see if I could get a custom recovery flashed that way but the phone fails protocol initialization. The only thing I can get to flash to this phone is 4.4.2 and the i605 pit file through ODIN. Nothing else will budge.
I guess the question I really need answered, is there another way to wipe data/factory reset without the option in the stock Samsung recovery and no access beyond the lock screen?
What I have to work with is ODIN mode and whatever is in recovery that is not wipe data/factory reset.
So I did get my hands on a couple other phones with passcode locks that have the MDM lockout within the stock recovery that still fails to flash anything in Odin except the stock 4.4.2 firmware. So I can eliminate the idea its hardware. I have 4 phones here 3 of which have the same issue and the 4th I was lucky enough to not have a passcode. Quick fix to get MDM removed that way.
Again any ideas that are slightly more outside the box would be appreciated. Thanks.
Edit: If this helps the phone that is working that I manage to clean all of that stuff off of also throws the same error in ODIN with or without USB debugging so it leads me to believe there is something I'm actually missing... Time to go read more.
Well, sound like it is more than coincidence. Maybe you should contact Samsung and see if they can help?
Yeah I might do that. I'd just hope they have a one size fits all solution because I have about 600 to 1000 phones to tackle... Hahaha.
The conundrum here is that for the MDM company to release the lock on the phone I have to be able to get beyond the lock screen for the phone to process the request. To get beyond the lock screen I need the psswords that the previous company allowed their employees to put on the phones that for some odd reason they didn't have remove.
Anyway if I get this figured out i'll let you guys know how I got it. Thanks for the suggestion.
((deleted))