First off, this will not let you convert a 16GB phone to a 32GB phone. If you try this on a phone that really is a 16GB device, you run a large change of bricking the device and requiring a jtag. These instructions and the files linked are only intended to be used on a Sprint SGS3.
I recently received a Sprint SGS3 32GB that was flashed as if it was a 16GB SGS3. The sticker under the battery said it was a 32GB model and I confirmed that it really did have a 32GB emmc chip inside by using cat /proc/partitions which showed:
Code:
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
A 16GB model will look like this:
Code:
179 0 15388672 mmcblk0
However, because mine was flashed wrong, I only had 12GB of storage instead of 26GB. To correct this problem, you will need a few files:
32 GB pit file and linked just in case someone needs it: 16GB pit file
A full copy of the stock firmware. The one I used is here.
Odin 3.07
USB drivers
You'll also want to back up everything to your removable sdcard. This process will require you to format your entire /data partition which includes all your apps and anything on your "internal sdcard" which includes pictures, backups, etc.
Make sure that you have all of the above files downloaded and have installed the USB drivers. You'll need to extract Odin and the .tar file from inside the firmware zip to known locations on your computer. Make sure your battery has a good charge. Lastly, I take no responsibility if something goes wrong. Also this will *not* trip the flash counter. You're flashing signed Samsung images that do not count towards your flash counter.
Power off your phone.
Hold down volume down and the home button then press and hold power until a screen shows up on your phone.
Release the buttons and press volume up to put your phone in download mode.
Open Odin on your PC
Connect your phone to your computer.
A COM box should light up and Odin should say something like "Attached" after your phone is detected.
Click on the PIT button and browse to and select the 32GB pit file.
Click the PDA button and brose to and select the firmware file. After you select the firmware file, Odin may verify the md5 which may take a few moments.
Click on start and go grab a soda. It will take upwards of 10 minutes to fully flash your device.
Cross your fingers and knock on wood and hope that the phone reboots successfully. On first boot it may boot to stock recovery to wipe cache.
When it boots to Android you probably still only have 12GB of storage, but that's (probably) ok. We'll fix it now.
Go into Settings -> Backup & Reset -> Factory Reset and choose to reset your phone.
Your phone will reboot to stock recovery and perform a full format of all of your data then reboot.
When finished rebooting, you should now have ~26GB of internal storage. Congrats.
Note, if you have trouble getting your phone to be detected by Odin, try a different USB cable and USB port.
I've confirmed that everything works on my phone after doing this. I've been able to activate, do PRL and profile updates, get 3G, 4G LTE, SMS, wifi, bluetooth, NFC, front and rear cameras, etc are all still working.
Dees_Troy said:
First off, this will not let you convert a 16GB phone to a 32GB phone. If you try this on a phone that really is a 16GB device, you run a large change of bricking the device and requiring a jtag. These instructions and the files linked are only intended to be used on a Sprint SGS3.
I recently received a Sprint SGS3 32GB that was flashed as if it was a 16GB SGS3. The sticker under the battery said it was a 32GB model and I confirmed that it really did have a 32GB emmc chip inside by using cat /proc/partitions which showed:
Code:
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
A 16GB model will look like this:
Code:
179 0 15388672 mmcblk0
However, because mine was flashed wrong, I only had 12GB of storage instead of 26GB. To correct this problem, you will need a few files:
32 GB pit file and linked just in case someone needs it: 16GB pit file
A full copy of the stock firmware. The one I used is here.
Odin 3.07
USB drivers
You'll also want to back up everything to your removable sdcard. This process will require you to format your entire /data partition which includes all your apps and anything on your "internal sdcard" which includes pictures, backups, etc.
Make sure that you have all of the above files downloaded and have installed the USB drivers. You'll need to extract Odin and the .tar file from inside the firmware zip to known locations on your computer. Make sure your battery has a good charge. Lastly, I take no responsibility if something goes wrong. Also this will *not* trip the flash counter. You're flashing signed Samsung images that do not count towards your flash counter.
Power off your phone.
Hold down volume down and the home button then press and hold power until a screen shows up on your phone.
Release the buttons and press volume up to put your phone in download mode.
Open Odin on your PC
Connect your phone to your computer.
A COM box should light up and Odin should say something like "Attached" after your phone is detected.
Click on the PIT button and browse to and select the 32GB pit file.
Click the PDA button and brose to and select the firmware file. After you select the firmware file, Odin may verify the md5 which may take a few moments.
Click on start and go grab a soda. It will take upwards of 10 minutes to fully flash your device.
Cross your fingers and knock on wood and hope that the phone reboots successfully. On first boot it may boot to stock recovery to wipe cache.
When it boots to Android you probably still only have 12GB of storage, but that's (probably) ok. We'll fix it now.
Go into Settings -> Backup & Reset -> Factory Reset and choose to reset your phone.
Your phone will reboot to stock recovery and perform a full format of all of your data then reboot.
When finished rebooting, you should now have ~26GB of internal storage. Congrats.
Note, if you have trouble getting your phone to be detected by Odin, try a different USB cable and USB port.
I've confirmed that everything works on my phone after doing this. I've been able to activate, do PRL and profile updates, get 3G, 4G LTE, SMS, wifi, bluetooth, NFC, front and rear cameras, etc are all still working.
Click to expand...
Click to collapse
Fantastic!! Just a few things. I got me and my wife the 32GB S3 the same way you did :angel:, akmzero put me on to your thread. With mine, I followed the instructions to the letter, and there was no second factory reset needed. On my wife's, I flashed the only the 32GB pit and it worked. I got the idea from just flashing .pit's on my s1 years ago.
Thanks for this, you saved my brain.
Is that 16gb pit file the one for the 16gb phone? So I could re flash mine if I needed too?
Sent from my SPH-L710 using xda app-developers app
dav3wash said:
Fantastic!! Just a few things. I got me and my wife the 32GB S3 the same way you did :angel:, akmzero put me on to your thread. With mine, I followed the instructions to the letter, and there was no second factory reset needed. On my wife's, I flashed the only the 32GB pit and it worked. I got the idea from just flashing .pit's on my s1 years ago.
Thanks for this, you saved my brain.
Click to expand...
Click to collapse
The same way he did?
Awesome. Just had this happens to a friend and can fix it.
Worked perfectly thank you again
Sent from my SPH-L710 using xda app-developers app
freeza said:
The same way he did?
Click to expand...
Click to collapse
Hit me up on google talk: [email protected]
dav3wash said:
Hit me up on google talk: [email protected]
Click to expand...
Click to collapse
Sorry to kick a dead post, but would the 16gb pit work for the cricket s3? If not, could it be modded to work?
do you have a pit to v 4.1.2 ?
Isn't it possible there was a reason your phone was factory formatted from a 32 to a 16? Perhaps mem beyond the 16 mark was bad and they just repackaged as a 16 when they formatted it as such?
Would re-opening this other bank of memory potentially expose the phone to errors when a bad block is hit?
edufur said:
Isn't it possible there was a reason your phone was factory formatted from a 32 to a 16? Perhaps mem beyond the 16 mark was bad and they just repackaged as a 16 when they formatted it as such?
Would re-opening this other bank of memory potentially expose the phone to errors when a bad block is hit?
Click to expand...
Click to collapse
Yes, but most people mess up with Odin and just flash anything without research. Most likely the case.
Hello...I'm using cwm v5.8.4.7...and when in recovery it only gives me the option to install from my phone and not my SD card...so I facorty reset and all and I have no roms or back ups on my phone one my SD...so now my phone won't boot up cause there is no operation system...what can I do...can I put my phone in download mode and flash a stock ROM and then re root my phone..or will it still be rooted...and can someone PLEASE...PLEASE give that file cause I'm gonna have to go to someone's house cause my PC isn't working...please helpe...I'm scared I just ruined a $600 dollar phone...Thanks in advance...
P.s... or could i use odin to flash a differert recovery ...so that way i can get my files off my external sd card...? And while in recovery I even tried to mount and unmount my SD card to try to get out to hpok up to the PC and it wouldn't work .
Sent from my SGH-T999 using xda premium
You can do a couple of things:
1 - in download mode, flash a different recovery, like TWRP. It may be able to read your SD card if it already contains the ROM you want to flash. Search the forums for the file you need to flash with Odin. If you choose to go with this method, your flash counter will increase, in which case, search for Triangle Away in these forums to reset it back to 0.
2 - also in download mode, you can flash this image, which is already rooted. Make sure you download the right image for your phone. Also, as the name of the thread states, this method will NOT increase your flash counter.
Flash the latest CWM v6.0.1.2 via this site http://www.clockworkmod.com/rommanager
Make sure you choose the correct phone since there are multiple S3s.
The file will be in .img format and you need a .tar
Download the toolkit from the developer forum and install it.
Rename the file to recovery.img and place it in the INPUT folder of the toolkit
Use the toolkit to covert the file into a .tar (its gonna have a long name but that's OK)
Use odin flash the .tar file to update your recovery.
Then flash a rom
Next time please make a NAND backup before wiping......
you could also mount usb in cwm, and then transfer the file to your sd card via usb, then flash as usual. make sure your sd card is mounted though. that could be your whole problem.
---------- Post added at 04:25 PM ---------- Previous post was at 04:25 PM ----------
xXxShAmRoCkxXx said:
you could also mount usb in cwm, and then transfer the file to your sd card via usb, then flash as usual. make sure your sd card is mounted though. that could be your whole problem.
Click to expand...
Click to collapse
oh you already tried that. my bad.
Wow...I thought there was a tar file already that I could use with Odin...I flashes my sgs3 with that cf- root thing...I would like to skip all that renaming stuff I don't want yo meas up my phone I did a 3 backups and it said that there was no Giles in there...weird ..but...after I do that...will I have to root again...?
P.s... those files aren't .IMG files they are zip files...
Oh and while I have the phone off the charing light came on once for like 2 mins. But even when the phone is off and plugged in it does this thing where it will do a short vibrate like every 5 seconds...and the light isn't on...and I can't tell if its charging while its in recovery cause its an older version and it doesn't show it like 6.0.1.2 does......so where I can I get this tar file for the original rom
Sent from my SGH-T999 using xda premium
Rogers S3 i747 need some serious help and advice
Ive spent the last 9 hours trying to find a solution to this issue and I cant seem to wrap my head around it, so I am kindly asking for some help.
I was attempting to flash the CM 10.1 12/18/2012 yesterday but every time I flashed it...the data was not working. I tried 12/17, 12/16 files but still the same issue.
So finally I gave up hope and I tried to flash back to the CM M2 experimental. I was using this before and other than the occasional force closes and once a week reboots at least it was useable.
So after I flashed everything again, of course with wiping the data and what not for the proper procedures, I was trying to load up my apps again from Google. About 15 apps in I get the message that there is not enough room? Puzzled I went to see why this was....
My internal memory of 12gigs only has available 678megs... WTF???????
Ive tried to locate how this was possible, but no programs I use can seem to see why the space is taken up. The funny thing is...all the movies and songs and pictures from the internal SD are still there. They can be seen on the phone play lists and picture lists. BUT I cant access the internal SD card!!!!
I am at a loss for solutions. I dont know what I did wrong here.
Ive reflashed Odin. Ive reflashed all the roms. I was able to finally mount the SD from Clockword MOD, but still no sign of these files.
Any and all help would be greatly appreciated at this point as Im about to give up.
ps..has anyone gotten CM10.1 to work with data? cause everytime I used it... it kept saying No Internet Connection
PLEASE HELP.... :silly::crying::crying::crying:
Delete unused backup data in CWM.
Sent from my SAMSUNG-SGH-I747 using xda premium
try format sdcard via cwm
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
lyrad12 said:
try format sdcard via cwm
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
tried formatting sd card via cwm but its not able to because its not mounted
so ive been trying to flash stock Samsung ROM back on my phone with ODIN...
twice its failed.
this is what its saying so far:
<ID:0/019> NAND Write Start!!
<ID:0/019> recovery.img
<ID:0/019> system.img.ext4
<ID:0/019> amss.bin
<ID:0/019> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
im using this TAR file
Odin3_v3.07_SGSIII\I727RUXLF3_I727RRWCLF3_I727RUXLF3_HOME.tar.md5
after careful examination i see that it might be the wrong version...
so now im using this TAR file
Odin3_v3.07_SGSIII\root66_RWC_I747MVLDLK4.tar.md5
wasabiGT said:
Odin3_v3.07_SGSIII\I727RUXLF3_I727RRWCLF3_I727RUXLF3_HOME.tar.md5
Click to expand...
Click to collapse
If I'm reading that correctly, that isn't even an image for any sort of S III, being instead for a variant of the S II.
wasabiGT said:
Odin3_v3.07_SGSIII\root66_RWC_I747MVLDLK4.tar.md5
Click to expand...
Click to collapse
This, on the other hand, should be the right (pre-rooted) image for your device.
Well, its the right i747image for a Canadian variety.
Verify these folders.
Verify in your internal SD Card if you have these directories:
/storage/emulated/0
and
storage/emulated/legacy
And by /storage I believe it means just the internal SD Card root directory.
According to a post, CM10.1 for some reason makes a copy of the entire contents of your internal sd card to these folders after installing it... not exactly sure why. Take a look at the link below for more information:
http://forum.xda-developers.com/showthread.php?p=35646339&highlight=emulated#post35646339
I simply formatted the SD Card through CWM Recovery after flashing back to stock ROM and the space was recovered, you will however lose data unless you try and take the contents out from these folders to your PC first.
thus far this method will not work for any of your 4.4.2 ota bricks if you flashed the 4.4.2 modem on the mjb bootloader, the only way to fix those bricks is with a new emmc, motherboard or a new phone. Jtag won't save you this time the phone is now a glorious paperweight.
On 4.3 it will not work if you flashed a bootloader for the wrong model(E.G. AT&T I747 bootloader on a Bell I747M)
Read ALL of the first 2 posts,there is useful information and files in post 2.
This works for BOTH AT&T I747 and the I747M The files are located at the bottom of this post in the quote there are also more instructions and files/tools to download in the 2nd post of this thread.
First and foremost I take no credit for any of the work here, other people did most of the leg work. This is a DIRECT copy of -Mr.X-'s post from here namely page 17 that is being used with his permission, I have added to it after having to actually Unbrick my phone lastnight.
Thank you to all who contributed to the things that made this thread possible. -Mr.X-, Loserskater, upndwn4par, enewman17 and all who may have contributed to their work.
So what you have done is hard bricked your I747 AT&T or your I747M by whatever means. Most likely flashing something with a bootloader. Your phone won't do anything at all. You can't get to download mode or recovery mode. Perhaps this method will fix your phone? Give it a try what else do you have to loose? You might save some money on a Jtag?
I take no responsibility for anything that comes of you using this information.
IF YOU BRICKED YOUR PHONE BY FLASHING A DIFFERENT MODELS BOOTLOADER ON IT THIS METHOD WILL NOT WORK FOR YOU. ] YOU WILL NEED A JTAG.(THAT ALSO INCLUDES WHILE TRYING TO UNBRICK USING THIS METHOD.)
Be sure to get all the way to the bottom of the first 2 posts and PLEASE read everything before doing anything.
The Debrick Files are all the way at the bottom in the qoute below by -Mr. X- The Links Are Active.
Be sure to read the second post too. If you need clarification on anything please send me a PM
Here Is The Information You Came Here For HOW TO DEBRICK - Mr. X-'s post from This Is The Thread That The Below Quote Is From
Click below for the quote from where I got most of my information, do not just start doing things after you read the below quote, read the second post too.
-Mr. X- said:
How to UNBRICK:
Credit goes to these guys in this thread, I thought i was onto something origional, however after doign some searching i found others have figured this out for a different Variant of the S3
What you did:
Bricked downgrading the bootloader after upgrading to the 4.3 bootloader. The 4.3 bootloader appears to blow efuses that stop previous boot loaders from booting. Now your EMMC has non booting garbage on/in it. YAY! not...
What we are doing:
What we will be doing is writing the Partition layout (Partition.mbn) among other things to the SD so the phone will boot from it after it fails to boot from the EMMC. According to my research the CPU is designed to cascaded from one storage device to the other in the event of failure on the first device. This also means if your EMMC is smoked, you could technically run the whole rom and everything from the sd card, or that's my assumption.
What you need:
- A Micro SD card 16GB or larger. this will no work on smaller cards, i tried a 2GB 4 GB and 8GB for the sake of testing and it fails.
- A working Dump that includes the SBL1, SBL2, SBL3, aboot, TZ and RPM from a working device that matches your DEVICE MODLE ie: I747U or I747M If you wanto t create your own dump from a friends device the command in a rooted adb shell would be as follows but not exact depending where you want the dump file to end up being on your sd cards. "dd if=/dev/block/mmcblk0 of=/storage/sdcard1/debrick.bin bs=1024 count=81920" That is what I used my my co-workers CM 10.2 rom to get the 4.3 bootloader/debrick dump. NOTE: the device has to be rooted with a working busybox that supports the dd command.
- The ability to write the dump image to the micro sdcard.
What to do:
First:
I used "Win32DiskImage" Located here But you can also use dd to write the image to your sd card in Linux.
On Windows:
Open Win32DiskImage. Brows to the Debrick dump you have for your device. Select the drive letter if your micro sd in the drop-down, click write. Bam done.
On Linux:
For ease of example, and method. Open Gparted on your Linux install or live cd, check the dev your sd card is in the drop down menu. For example mine was /dev/sdb/ then use "dd if=/path/to/debrick/dump.img of=/dev/sdb/" This method also works. Be careful you are selecting the right dev or you will overwrite another disk on your system. YOU HAVE BEEN WARNED.
Second:
Put that SD card in your device insert the battery and if the SD card is written correctly with a proper debrick file. You can put a jig in the device and it will boot straight to download mode. If you dont have a jig hold Vol Down + Home + Power the device will boot to download. If it does not, either the image didn't write to the card properly ( I had to write it a few times with Win32DiskImager, DD worked fine the first try), the debrick dump is no good. Or your trying to debrink your 4.3 bootloader downgrade brick with a dump from 4.1.2 compatible bootloaders. this will not work the blown efuse will still prevent the bootloader from booting from the SD card as well as the EMMC. You will know pretty fast if it worked, as the device will vibe with the jig or it will vibe with the button combo almost immediately after being pressed and held.
Third:
Odin that thing back to the 4.3 stock rom. Yes you have to. You ain't getting 4.1.2 bootloaders back so dont think about odining that thing either. it wont boot, with out the SD with the 4.3 bootloader on it installed. Odining back is the best thing to do, it will get the right boot loader on your EMMC. If you are feeling adventurous and you had a custom recovery installed. You can boot to recover instead of download from the debricking SD boot, and install a 4.3 flashable zip bootloader there, if all goes well, you wont lose your data and the bootloader will be functional on the EMMC. Either method you choose after its done "flashing" what ever method. remove the sd and verify it boots on its own.
Note: a user stated that he flashed a bootloader via recovery and flashable zip, and he stated it appeared to flash the bootloadeerr to the micro sd. if this happens, ODIN back to the proper rom to get the internal EMMC rebuilt and booting.
If it does, do a dance or something.
Here is a flashable Bootloader for the i747M 4.3
Here is a debrick Dump from a I747M from the UEMK5 4.3 that works
Broken link I will update IF/AFTER it is fixed is an untested debrick dump for I747M from the DMF1 4.1.2 (WOuld be used to debrick a device that was bricked before or that has not updated to 4.3 bootloader only)
This one is for AT&T phones.
Here is a debrick file from the I747U on 4.3 thanks to theramsey3 I cannot test it obviously but it looks good in a hex editor. Should work for any one who has bricked the I747U by downgrading the boot loader.
Click to expand...
Click to collapse
The 16GB SD card is going to get formatted and partitioned if you have valuable data on it do a back up of it... You have been warned.MAKE SURE YOU USE THE CORRECT FILES FOR YOUR PHONE FAILURE TO DO SO WILL RESULT IN YOUR PHONE NEEDING TO BE JTAG'ED
YOU HAVE BEEN WARNED REPEATEDLY DO NOT FLASH THE WRONG BOOTLOADERS
Requirements(carrier specific)
For The AT&T SGH-I747
you will need two micro SD cards one 16GB (I read in a similar thread that the SD card must be 16GB no smaller and no larger if you get one bigger to work please let me know) and one 1GB or larger. You will need Odin v3.09(what I used), Samsung kies3 (you need the USB drivers it installs, a working custom recovery either CWM or TWRP(I prefer TWRP) and some patients.
For The SGH-I747M
you will need a 16GB micro SD card to put the debrick files on, Odin v3.09, Samsung kies3, the correct firmware TAR file for your phone and some patients.
If you need some of the things mentioned in the requirements please click under "Tools You May Need And File Downloads For AT&T and the SGH-I747M" .
You Need to Identify Your Phone Model Correctly and download the appropriate debrick file From the quote by -Mr. X- in the post above to place on your 16GB Micro SD Card with the Win32DiskImager (available for download below).
How to put the Debrick file on your SD card
Flash this Debrick file to your 16GB Micro SD card with Win32DiskImager (available below) by
*Insert your Micro SD card into your computer (backup any information you may have on it we are going to ERASE, FORMAT and PARTITION it.)
*Open win32DiskImager
*Navigate to the location where you downloaded the correct Debrick file
*Select your Debrick file by double clicking on it
*In the upper right corner of Win32DiskImager you should make sure that the drive letter assigned to your sd card is selected.
***Which ever drive that is listed will be erased, formatted, partitioned and have a small amount of data written to it***
*Click write in the bottom right hand side
You now have your debrick card
For the SGH-I747M
You need to put the Debrick SD card in the Phone, Pull and Replace the Battery, Put the Phone in download mode and flash your carrier specific 4.3 firmware (instructions and downloads Below) Via ODIN. Reboot the phone allow it to boot up, get in the phone, reboot without the debrick sd card in it, if it won't boot on its own see the link below.
If you are on AT&T
You will need to copy all of the files you are going to flash (you can download them below) onto your 1GB or larger SD card. You then Need Put your Debrick SD card in the Phone, Remove and reinstall the battery,Put the Phone in Recovery Mode (Must Be Either TWRP or CWM Instructions and TWRP Download Below), Dismount the Debrick SD card, Insert your SD card with your Bootloaders, ROM, kernel, and Modem into the Phone, Mount the SD card, Flash your files one at a time, wipe the cache and dalvik between each file, Once you are done reboot the system, You Might have to put the debrick SD back in and do another battery pull, boot up the phone, after you get in the phone reboot it without the Debrick SD card in. If it will not Boot on its own see the link below.
AFTER YOU FLASH IT MAY APPEAR THAT THE PHONE FREEZES ON THE BOOT SCREEN BE PATIENT 4.3 TAKES A LONG TIME TO BOOT THE FIRST TIME A ROM IS INSTALLED.
Tools You May Need And File Downloads For AT&T and the SGH-I747M
Here is a flashable Bootloader for the i747M 4.3
Here is a debrick Dump from a I747M from the UEMK5 4.3 that works
Broken link I will update IF/AFTER it is fixed is an untested debrick dump for I747M from the DMF1 4.1.2 (WOuld be used to debrick a device that was bricked before or that has not updated to 4.3 bootloader only)
Here is a debrick file from the I747U on 4.3 thanks to theramsey3 I cannot test it obviously but it looks good in a hex editor. Should work for any one who has bricked the I747U by downgrading the boot loader.
Debrick file mirrors use only if the links ^^^above don't work please.
AT&T debrick file Use this ONLY if you are on AT&T and after you have been on the 4.3 bootloaders
SGH - I747M debrick fileUse this ONLY if you have an SGH-I747M that was on the 4.3 bootloaders.
Win32 Disk Imager (used to write the debrick file to the sd)
Samsunk Kies
Go Here For Odin Pick Whichever One You Want To Use I Used 3.09
Do Not worry about downloading or installing root or KnoxRemover or SuperSU from the thread below yet focus on the task at hand you need to get your phone booting first then concern yourself with other goodies. You need TWRP and possibly ODIN if you want to take it from there. There are instructions in that thread on the installation of TWRP Skip the rest for now.
Go Here For TWRP Custom Recovery There Is Also A Link To ODIN There
Partition Wizard Free (There is a link with instructions below)
With AT&T you will have to download 4.3 bootloaders, a 4.3 rom, a 4.3 kernel and a 4.3 modem. I will post links to Threads where I retreived mine at and possibly a mirror download link with appropriate permissions.
AT&T info and link to roms, bootloader, kernel and modem I used to recover. Click below.
I got everything I flashed from here
Lately I have been running Looserskaters S3Rx, it is very stable and very functional Here is a link to it, I highly recommend it http://forum.xda-developers.com/showthread.php?t=2252932 I am not going to intentionally brick my phone again to test if you can flash this directly from a hardbrick so if anyone is successful or unsuccessful please let me know so I can update this thread.
Use this bootloader for the AT&T i747 ONLY https://www.dropbox.com/s/vbyeorrxapwrots/d2att_I747UCUEMJB_bootloader.zip the one in the tread where I got mine hasn't been working so use this bootloader it is the same one just hosted by a different person.
DO not use these files if you are not on AT&T you will simply be wasting your time by bricking your phone again. AND requiring a Jtag.
For the kernel I flashed the one in the middle d2att_Kernel_Stock_init.d_4.3_MJB_v1.0.zip which belongs to upndwn4par. I used loserskater's rom, bootloader and modem everything I used was linked in that thread. With proper permissions I would like to mirror those links as I know they work well.
This will have you rooted from jump Street. You might have to download supersu from the play store. I didn't have to. But YMMV.
Firmware downloadsFOR SGH-I747M USERS ONLY make sure you download the correct file. These are the TAR files that the I747M users can flash via the PDA button in ODIN
By clicking the button below to reveal links you acknowledge you are going to download the correct file.
WWW.Sammobile.COM (when I was still able to this was the site I downloaded my firmwares from)
If You Need Instructions For Download Mode, Recovery Mode or How to Flash TWRP Click Below
If You Need To Install TWRP Click Below For Instructions
If you don't already have a custom recovery installed on the phone.
* You will need to write your debrick file to your 16GB SD card and insert it into the phone,
* Perform a battery pull
*Reinsert the battery
*Access download mode
*Flash the TWRP file with ODIN
***Click Below For Instructions***
*First to access download mode (you should already have your Debrick SD card in your phone.)
*hold vol down, the home button and the power button for 4 seconds.
*The phone should vibrate.
*Release the power button followed by the remaining two.
*You may or may not have to have the USB cable plugged into your computer to do this? If it wont work with the cable plugged in unplug it and vise versa.
*When the warning screen pops up you need to press the correct button to continue.
***Follow the remaining Instructions EXACTLY***
*Now (if you havent done so yet) open ODIN on your pc (Kies MUST BE CLOSED)
*Click the PDA button, (In ODIN 3.09 it says AP)
*Navigate to where you downloaded the TWRP file,
*Select that file, Double Click To Select
### MAKE SURE that you do NOT have anything besides auto reboot checked ###
*** Once you are sure you have followed the direction ***EXACTLY*** click below to reveal the rest
Now That you are 100% Certain you have nothing more than auto reboot checked,
go to the bottom and click start.
it should write some files and say PASS and all threads finished (1 succeeded/ 0 failed).
you now have TWRP installed you can follow the rest of the guide.
If You Need Instructions To Access Download Mode Click Below.
*First to access download mode (you should already have your Debrick SD card in your phone and your battery removed.)
*Reinsert the battery
*Hold vol down, the home button and the power button for 4 seconds.
*The phone should vibrate.
*Release the power button followed by the remaining two.
*You may or may not have to have the USB cable plugged into your computer to do this? If it wont work with the cable plugged in unplug it and vise versa.
*When the warning screen pops up you need to press the correct button to continue.
If You Need Instructions To Access Recovery Mode Click Below
*First to access recovery mode (you should already have your Debrick SD card in your phone and the battery out.)
*Reinsert the battery
*Hold vol up, the home button and the power button for 4 seconds.
*The phone should vibrate.
*Release the power button followed by the remaining two.
*You may or may not have to have the USB cable plugged into your computer to do this? If it wont work with the cable plugged in unplug it and vise versa.
Your phone won't boot without the debrick SD card? Click below.
If you are on AT&T
When I first got mine booting again it would only boot with the micro SD card that has the .IMG file on it in the phone and only after a battery pull. What I did was boot back to recovery, remove my SD card and I had a spare SD card I used to flash the files with, I inserted it told TWRP to mount the new SD card, flashed the bootloader again and it seems to have cured my phones malfunctions. It now boots on its own like nothing ever happened. It may not happen like this for you???]
For the SGH-I747M
You have Two choices either flash the bootloader only via the 2 sd card method outlined for AT&T which requires flashing Custom recovery and VOIDING YOUR WARRANTYor you can reflash with odin and possibly try a factory reset in the samsung stock 3e recovery.
If your phone is booting now don't play with the bootloaders any more.
Make a nandroid backup of your phone if you are going to follow the instructions below.
You assume all risk associated with such...
Do you want to be able to use wifi, bluetooth or USB tethering? Click below. But read everything carefully before you do anything.
I contacted enewman17 and inquired about the link below \/ \/ \/ he advised me that it should be flashable via custom recovery to any AT&T I747 on 4.3 regardless of rom or kernel and possibly without root. He also said he thinks it may work on the I747M also.
If any I747M users flash it and are successful or unsuccessful please let me know so I can post whether this is effective for that as well.
http://forum.xda-developers.com/showpost.php?p=46804681&postcount=5 I flashed enewman17's tether hack with bluetooth enabled from there ^^^which allows wifi tethering through the roms native tethering app without the carrier getting their hands in your pocket.
Do you need instructions to install the above file? Click below
To install this you need to
*download this file^^^
*move it to your SD card
*put the SD card by k into the phone
*turn the phone off
*boot into recovery
*select install
*navigate to the location of the file ^^^
*select the correct file
*write the file to the phone
*clear the cache and wipe the dalvik
*reboot and enjoy, make sure you thank enewman17 for his fantastic work.
It works flawlessly for me buy your results may vary?
DO you want to get your 16GB micro SD card back to a use able state so you can store data on it again? Click below for details.
If you want to restore your sd card to a useable state after you get everything running again I used http://www.partitionwizard.com/free-partition-manager.html, After you install it and open it Insert your SD card into your computer and select the drive letter assigned to your SD card tell the partition wizard to delete all partitions then in the top left corner click apply. You now have a completly blank unformatted SD card. Now Insert it into your phone the phone will give you a notification that the sd card is unformatted and give you an option to format it. you now have a blank formatted SD card you can use again.
More to come in the near future.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Amazing! Thanks you!
This worked perfectly! I almost lost hope, but this has restored my faith in Android. So, does this mean that this is the end of Custom Roms that run versions <Android 4.3? That would be a shame...Is it the Android 4.3 update that caused all of this, or just Samsung's update?(Google or Samsung) I really loved custom roms of 4.1.2 and there were some things that I was able to do there that were ruined because of the update. It wasn't quite nice for Samsung to do this to those great devs.
theramsey3 said:
Put that SD card in your device insert the battery and if the SD card is written correctly with a proper debrick file. You can put a jig in the device and it will boot straight to download mode. If you dont have a jig hold Vol Down + Home + Power the device will boot to download. If it does not, either the image didn't write to the card properly ( I had to write it a few times with Win32DiskImager, DD worked fine the first try), the debrick dump is no good. Or your trying to debrink your 4.3 bootloader downgrade brick with a dump from 4.1.2 compatible bootloaders. this will not work the blown efuse will still prevent the bootloader from booting from the SD card as well as the EMMC. You will know pretty fast if it worked, as the device will vibe with the jig or it will vibe with the button combo almost immediately after being pressed and held.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This is interesting. If the other poster is correct, the phone's CPU will try to boot like the computer CPU, from boot device #1, to #2, #3, etc. In this case, the internal ROM is #1 device and the SD would be #2 root device.
If this is the case, then why do we need the SD card to hold the same bootloader? If the phone is totally hard-bricked, then it should just by-pass the internal ROM completely and boot through the SD directly. Then the phone should be able to boot from 4.1.2 or any older ROM.
So if the SD card has to have the same bootloader as the internal ROM, it means the phone still boots off the ROM bootloader, then continue to boot off the SD card since the internal ROM does not have the valid ROM to continue.
In my case, I have a really hard-bricked phone. I do not even know the original ROM version. I do not think its bootloader is locked. But the previous owner flashed with a wrong ROM from a different phone.
So I'd like to know from the folks who successfully fixed the hard-bricked phones with this method: Do you have to use the debrick.img from the existing bootloader, or you can use any generic debrick.img?
BaSingSe said:
This is interesting. If the other poster is correct, the phone's CPU will try to boot like the computer CPU, from boot device #1, to #2, #3, etc. In this case, the internal ROM is #1 device and the SD would be #2 root device.
If this is the case, then why do we need the SD card to hold the same bootloader? If the phone is totally hard-bricked, then it should just by-pass the internal ROM completely and boot through the SD directly. Then the phone should be able to boot from 4.1.2 or any older ROM.
So if the SD card has to have the same bootloader as the internal ROM, it means the phone still boots off the ROM bootloader, then continue to boot off the SD card since the internal ROM does not have the valid ROM to continue.
In my case, I have a really hard-bricked phone. I do not even know the original ROM version. I do not think its bootloader is locked. But the previous owner flashed with a wrong ROM from a different phone.
So I'd like to know from the folks who successfully fixed the hard-bricked phones with this method: Do you have to use the debrick.img from the existing bootloader, or you can use any generic debrick.img?
Click to expand...
Click to collapse
To be quite honest I have no clue if that would work? I am pretty sure if you left your debrick sd card in the phone you could do it like that but then you loose the ability to have expandable storage. Or atleast have to keep your boot.img sd card with you all the time incase you need to reboot the phone.
How this works is that: the phone can not boot from the internal bootloader/ROM. So it tries to boot off the SD card. The SD should not have to have the same 4.3 bootloader (technically). From the old/original thread (Sprint), even very old generic ROM should do it. But after you get to download mode, you'll have to flash the same 4.3 ROM (or whatever your last bootloader-locked ROM is). Or you get the same hard-bricked phone since the 4.3 bootloader can't be written over.
But again, I have a hard bricked phone someone flashed with a wrong S3 ROM, something like a GTI9300 ROM onto a Verison S3 phone. And I still can't get the phone to make any move, even after the following the exact instruction many times.
I really hope if someone DOES get this work with a really hard-bricked phone, provide some details, so we can understand this better.
A hard-bricked phone means, if you remove the battery and connect AC, the red light would turn on. Other than that, no boot, no sound, no vibrate, no download mode, no recovery. The phone would be totally dead, other than the red light.
theramsey3 said:
To be quite honest I have no clue if that would work? I am pretty sure if you left your debrick sd card in the phone you could do it like that but then you loose the ability to have expandable storage. Or atleast have to keep your boot.img sd card with you all the time incase you need to reboot the phone.
Click to expand...
Click to collapse
BaSingSe said:
How this works is that: the phone can not boot from the internal bootloader/ROM. So it tries to boot off the SD card. The SD should not have to have the same 4.3 bootloader (technically). From the old/original thread (Sprint), even very old generic ROM should do it. But after you get to download mode, you'll have to flash the same 4.3 ROM (or whatever your last bootloader-locked ROM is). Or you get the same hard-bricked phone since the 4.3 bootloader can't be written over.
But again, I have a hard bricked phone someone flashed with a wrong S3 ROM, something like a GTI9300 ROM onto a Verison S3 phone. And I still can't get the phone to make any move, even after the following the exact instruction many times.
I really hope if someone DOES get this work with a really hard-bricked phone, provide some details, so we can understand this better.
A hard-bricked phone means, if you remove the battery and connect AC, the red light would turn on. Other than that, no boot, no sound, no vibrate, no download mode, no recovery. The phone would be totally dead, other than the red light.
Click to expand...
Click to collapse
Mine was truley Hard Bricked The only response it would give is The red light with the charger plugged in and battery removed. also the QHUSB_DL message on the computer when connected. I recovered from it and created this How To Guide to try to help others.
Mine was recovered from the Debrick file that actually came off of my phone with the help of -Mr.X- to tell me the command lines to type to get the file extracted from my phone the day prior to me bricking my phone(which did not happen on purpose).
Never thought I would need it then 18 hours later I bricked my phone, and found out this is a Viable way to recover from it.
Perhaps your phone needs to be JTAG'ed?
theramsey3 said:
- A working Dump that includes the SBL1, SBL2, SBL3, aboot, TZ and RPM from a working device that matches your DEVICE MODLE ie: I747U or I747M If you wanto t create your own dump from a friends device the command in a rooted adb shell would be as follows but not exact depending where you want the dump file to end up being on your sd cards. "dd if=/dev/block/mmcblk0 of=/storage/sdcard1/debrick.bin bs=1024 count=81920" That is what I used my my co-workers CM 10.2 rom to get the 4.3 bootloader/debrick dump. NOTE: the device has to be rooted with a working busybox that supports the dd command.
Click to expand...
Click to collapse
What did you mean by stating that? So your phone was running CM 10.2?
BaSingSe said:
What did you mean by stating that? So your phone was running CM 10.2?
Click to expand...
Click to collapse
You're Qouting -Mr.X-'s post from a different thread. I didn't write that part of it. and explained such in the very begining of this thread.
Everything that is grayed out was written by him everything in white was written by me.
Hey man, how big are the Img files usually...do you mind uploading it? i am on i747m , accidentally flashed the AT&T 4.3 Bootloader (yea it was super late and i mis selected that file)
Can probably wait in a few weeks when i get a chance to meet a friend on 4.3 to get that dump
but if its not too big...would you mind uploading it?
---------- Post added at 06:12 AM ---------- Previous post was at 06:11 AM ----------
Hey man, how big are the Img files usually...do you mind uploading it? i am on i747m , accidentally flashed the AT&T 4.3 Bootloader (yea it was super late and i mis selected that file)
Can probably wait in a few weeks when i get a chance to meet a friend on 4.3 to get that dump
but if its not too big...would you mind uploading it?
FULLTIMEIT said:
Hey man, how big are the Img files usually...do you mind uploading it? i am on i747m , accidentally flashed the AT&T 4.3 Bootloader (yea it was super late and i mis selected that file)
Can probably wait in a few weeks when i get a chance to meet a friend on 4.3 to get that dump
but if its not too big...would you mind uploading it?
---------- Post added at 06:12 AM ---------- Previous post was at 06:11 AM ----------
Hey man, how big are the Img files usually...do you mind uploading it? i am on i747m , accidentally flashed the AT&T 4.3 Bootloader (yea it was super late and i mis selected that file)
Can probably wait in a few weeks when i get a chance to meet a friend on 4.3 to get that dump
but if its not too big...would you mind uploading it?
Click to expand...
Click to collapse
DO you mean these Debrick.img files that are in the first post?
-Mr. X- said:
Here is a debrick Dump from a I747M from the UEMK5 4.3 that works
Here is an untested debrick dump for I747M from the DMF1 4.1.2 (WOuld be used to debrick a device that was bricked before or that has not updated to 4.3 bootloader only)
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
theramsey3 said:
DO you mean these Debrick.img files that are in the first post?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
o man my bad lol tired pretty hard to look for the link too...thanks!
Followed instructions still can not get phone into download mode.
I only have a 64 GB SD card could that be the problem?
Also I get no red light and no vibe.
When phone is plugged in Linux sees it as qhsusb_dload
Sent from my GT-N8013 using Tapatalk 4
dragonslayer73 said:
Followed instructions still can not get phone into download mode.
I only have a 64 GB SD card could that be the problem?
Also I get no red light and no vibe.
When phone is plugged in Linux sees it as qhsusb_dload
Sent from my GT-N8013 using Tapatalk 4
Click to expand...
Click to collapse
I could only get my phone to respond to button inputs to get into recovery if; I pulled the battery out with the USB cable unplugged, put the battery back in, plug the USB cable back in, then used the button combination. Otherwise it was a dead phone that did nothing.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Hi Op, tried to 4.3 file, didnt work for me , I can have red light on when plug in PC with no battery. using a 32 GB class 10 card , wrote the image a few times stil not getting the download mode...also tried to pull battery before combo thing...
Wanna try the 4.1.2 img..but the link is broken?
theramsey3 said:
I could only get my phone to respond to button inputs to get into recovery if I pulled the battery out with the USB cable unplugged put the battery back in then used the button combination. Otherwise it was a dead phone that did nothing.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Tried button combos still nothing plugged into PC and not plugged in
Sent from my GT-N8013 using Tapatalk 4
Read some of this thread which is where -Mr.X- gave credit to in his post. The op of that thread says you may have to try writing the file to the SD card several times and try booting to recovery or download mode several times to be successful.
There is also a post near the end of it that says the SD card must be exactly 16GB. Is that a fact? I don't know? The one I used was and the process worked for me.
If you guys are on AT&T make sure you are using the correct files.
If you guys have the Canadian I747M make sure you use the right file.
That link is messed up its not mine I will contact the rightful owner of it and request that he fix it if possible.
I did not create any part of this process I simply used some information that helped me Unbrick my phone with permission to write a how to guide. Perhaps the size of your SD cards are making a difference here??? I did observe when I was repartitioning my SD card to be able to use it for storage again that when you write the .IMG file to it, it creates several partitions on the SD card to look just like the internal storage of the phone. So if you're using a larger card than the phones internal storage perhaps that is conflicting with the process?
I was using my daily driver 16GB card that I normally keep in my phone for storage.
I am no developer just a concerned SGH-I747 owner. I became really concerned after I bricked my phone the night before last night at about 11pm I finally got it to boot again at about 8am.
This method has been proven to work on many different variants of the galaxy s3. Sprint, T mobile, the Canadian I747M, my phone (AT&T I747) and maybe others as well?
I personally debricked my phone with this method. The author of the post I quoted in the op who wrote all the files says he debricked an I747M with this method.
As with all things though perhaps it doesn't work in all situations?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I have the i747 not i747m what debrick image should I use?
Sent from my GT-N8013 using Tapatalk 4
Unbricked and now hard bricked again
I used the debrick-SGH-I747U-CUEMJB3.img on my hard bricked (no signs of life except for red charging light when plugged into charger) At&T i747 that had the ota 4.3 update and was able to get into download mode ! from there I flashed TWRP through Odin and from there I flashed the I747UCUEMJ2 rom and it booted right up and was happy ! but then I went back into TWRP and decided to flash boot_CWM_I747MVLUEMK5 and when it was done flashing it said succeeded so I hit reboot then after that my phone was dead again and the sdcard debrick imgae no longer works..........any ideas?
dragonslayer73 said:
I have the i747 not i747m what debrick image should I use?
Sent from my GT-N8013 using Tapatalk 4
Click to expand...
Click to collapse
This is the one you should be using for an AT&T phone
-Mr. X- said:
Here is a debrick file from the I747U on 4.3 thanks to theramsey3 I cannot test it obviously but it looks good in a hex editor. Should work for any one who has bricked the I747U by downgrading the boot loader.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Team,
I have been researching for hours and am quite confused on which avenue to take to recover my soft brick. Information overload:crying:
Here is what happened and I will provide as much info as I can so please bare with me. After OTA upgrading to 4.3 and rooting successfully using the CF Auto Root. I was attempting to get my wifi hotspot working again using the Wifi mod and mucked around and installed the wrong mod (Odexed MK4). This rendered me stuck at the glowing samsung screen and it goes no further. Ive tried to factory reset, wiped cache and rebooted several times. Boots fine into recovery and download mode.
So after hours of searching, reading (its 3:50am est) and testing solutions I am no closer to a fix than I was when I started. I am currently waiting on a stock rooted rom to download in an attempt to flash back to stock but its taking hours to download.
However I just noticed, as I am typing this thread, that I can no longer
1. Mount as an usb external drive in recovery (TWRP v 2.3.1.0) I have Samsung drivers installed (1.5.14.0) so I get the indicator sound from windows that I sees the phone.
2. If I attempt to manually browse through my files using the recovery there are no files inside my internal sdcard directories.
/sdcard There are three directories there
/0 /obb /TWRP and the only folder that has files inside is the TWRP folder.
Im floundering here. I cannot even mount and install files on the phone to even attempt to flash back to stock. Can I get some fresh angles ladies and gents? I am at a loss.
signalsoldier said:
Team,
I have been researching for hours and am quite confused on which avenue to take to recover my soft brick. Information overload:crying:
Here is what happened and I will provide as much info as I can so please bare with me. After OTA upgrading to 4.3 and rooting successfully using the CF Auto Root. I was attempting to get my wifi hotspot working again using the Wifi mod and mucked around and installed the wrong mod (Odexed MK4). This rendered me stuck at the glowing samsung screen and it goes no further. Ive tried to factory reset, wiped cache and rebooted several times. Boots fine into recovery and download mode.
So after hours of searching, reading (its 3:50am est) and testing solutions I am no closer to a fix than I was when I started. I am currently waiting on a stock rooted rom to download in an attempt to flash back to stock but its taking hours to download.
However I just noticed, as I am typing this thread, that I can no longer
1. Mount as an usb external drive in recovery (TWRP v 2.3.1.0) I have Samsung drivers installed (1.5.14.0) so I get the indicator sound from windows that I sees the phone.
2. If I attempt to manually browse through my files using the recovery there are no files inside my internal sdcard directories.
/sdcard There are three directories there
/0 /obb /TWRP and the only folder that has files inside is the TWRP folder.
Im floundering here. I cannot even mount and install files on the phone to even attempt to flash back to stock. Can I get some fresh angles ladies and gents? I am at a loss.
Click to expand...
Click to collapse
Good morning (not really, I assume, sorry). So where are you at? Not sure what you mean that you cannot install files on the phone... Can you get into download mode and your computer recognizes the phone? If yes, can you do what you started to say - odin stock rooted? Or... if you can get into a custom recovery but your internal sd card has been wiped, can you put a stock rooted ROM in zip format on an external sd card, put that sd card into your phone, and flash in custom recovery?
erikalin said:
Good morning (not really, I assume, sorry). So where are you at? Not sure what you mean that you cannot install files on the phone... Can you get into download mode and your computer recognizes the phone? If yes, can you do what you started to say - odin stock rooted? Or... if you can get into a custom recovery but your internal sd card has been wiped, can you put a stock rooted ROM in zip format on an external sd card, put that sd card into your phone, and flash in custom recovery?
Click to expand...
Click to collapse
Here is the problem...the ROM I have is in zip format and based on what I have been reading I cannot install via Odin. Due to the fact that the phone refuses to mount as an external storage device I have no way of placing data on the the internal or external card. The only recourse I have now it to attempt to find an adapter to be able to mount this microsd card to my PC. I am out of town and have no idea where I could find one.....uggggh. Ill keep you posted.
signalsoldier said:
Here is the problem...the ROM I have is in zip format and based on what I have been reading I cannot install via Odin. Due to the fact that the phone refuses to mount as an external storage device I have no way of placing data on the the internal or external card. The only recourse I have now it to attempt to find an adapter to be able to mount this microsd card to my PC. I am out of town and have no idea where I could find one.....uggggh. Ill keep you posted.
Click to expand...
Click to collapse
Walmart. .. target. ... and most any office store you should be able to find one. http://forum.xda-developers.com/showthread.php?t=2538543 ... This thread gives you the stock unrooted rom in a flashable zip. To my knowledge no one has put out a stock rooted zip, but I will check around.
http://i.imgur.com/qrByUGN.jpg
signalsoldier said:
Team,
I have been researching for hours and am quite confused on which avenue to take to recover my soft brick. Information overload:crying:
Here is what happened and I will provide as much info as I can so please bare with me. After OTA upgrading to 4.3 and rooting successfully using the CF Auto Root. I was attempting to get my wifi hotspot working again using the Wifi mod and mucked around and installed the wrong mod (Odexed MK4). This rendered me stuck at the glowing samsung screen and it goes no further. Ive tried to factory reset, wiped cache and rebooted several times. Boots fine into recovery and download mode.
So after hours of searching, reading (its 3:50am est) and testing solutions I am no closer to a fix than I was when I started. I am currently waiting on a stock rooted rom to download in an attempt to flash back to stock but its taking hours to download.
However I just noticed, as I am typing this thread, that I can no longer
1. Mount as an usb external drive in recovery (TWRP v 2.3.1.0) I have Samsung drivers installed (1.5.14.0) so I get the indicator sound from windows that I sees the phone.
2. If I attempt to manually browse through my files using the recovery there are no files inside my internal sdcard directories.
/sdcard There are three directories there
/0 /obb /TWRP and the only folder that has files inside is the TWRP folder.
Im floundering here. I cannot even mount and install files on the phone to even attempt to flash back to stock. Can I get some fresh angles ladies and gents? I am at a loss.
Click to expand...
Click to collapse
You always have the Factory Reset/Wipe Data option inside your Recovery. But if that doesnt work use your downoad mode and Reset in KIES. but whatever you do, now that you have upgraded to 4.3 DO NOT try and dowgrade. it will cause a hard brick.
You did the ota update which put KNOX on your phone which is bad especially if you have a warranty. There is currently no way to get rid of it. I read a while ago the peoples phones has been getting bricked because they were trying stuff.
Anyway the only option I guess you have is to use your computer and reset your phone using kies. It will flash your phone back to stock in download mode.
Sent from my GT-N5110 using xda app-developers app
Ok team here is the latest
I was able to grab an adapter for my micro and I attempted to install the stock rom posted above located here
http://forum.xda-developers.com/showthread.php?t=2538543
That was a no-go and gave me the following error during installation.
assert failed: apply_rename_check("/system/app/ALLSHAREPLAY.apk","/system/app/ALLSHARECASTPLYER.apk","f90c86cf5423131dcd04f9a5b169df5f83ab9170" "81dbc5115c7c1121f70ada147f7297e192af4d38")
E: Error in /external_sd/cffb350e111c431bcd19eea86e0d0e6816950053.USER_L710_SPR_MD4_to_MK3_Update_FWD.zip
Click to expand...
Click to collapse
I attempted to connect to Kies 2.6.1 via download mode. Kies will timeout attempting to connect after about 8 to 10 mins.
"Device does not respond. Reboot to Resolved the Issue."
Click to expand...
Click to collapse
at this point I am still able to get into Recovery and Download. I really hosed this **** up
Here is the stock tar thread....You can use this to Odin back to stock. http://forum.xda-developers.com/showthread.php?t=2565972
Good luck!
http://i.imgur.com/qrByUGN.jpg
Thanks bro.....Ill download it and give it a try. I have nothing to lose at this point. Ill be back with praise or tears.
Problem resolved I was able to go back to stock using the link posted above by Bigpappa!!!
Thank you all so much for you help!
Congratulations
I am glad you were able to get use of your phone back. I wish I had seen this thread sooner. I was in exactly the same boat a couple of weeks ago, only mine lasted 3 days. I even bought a new GS4 when I thought my phone was dead. Took it back when someone finally helped me do what you did. It's a helpless feeling when you have been rooting and Romming for years safely. Sure seems like a sticky thread is in order for this specific issue. As you can see, I haven't got enough history for credibility on this forum since I rarely post. Oh well.