For those who have been living under a rock, problematic leaked builds of ICS were released for several different Samsung devices a few months ago. Users of those Devices for instance soon discovered that their devices were being ffected by what came to be known as the MMC_CAP_ERASE bug. Shortly after this*occurred, XDA Senior Member hg42 came up with a way to revive downed devices.
Now thanks to some more ingeniuty on his part, hg42 has also developed a companion application known as Partition Scanner to assist in this process.*The application features:
emmc_scan_all_partitions_once.zip
emmc_scan_all_partitions_infinitely.zip
these allow fast scanning of all blocks of all emmc partitions in 1MiB steps.
The main purpose is to access each emmc block to find any bricked block in the partitions after repartitioning.
The “infinitely” variant runs checks infinitely, which may help to find emmc brick effects which only occur sporadically (if such effect really exists). Run this as long as you want. Reboot to finish.
If this freezes the last partition shown may have a bricked block inside.
emmc_find_brick_start.zip
emmc_find_brick_end.zip
these scan the whole emmc device.
emmc_find_brick_start starts scanning from the beginning of the device upward.
emmc_find_brick_end searches the end of the device and then scans downward.
If this runs up to the end or down to zero (showing a message with “completed –> OK”), no bricked block was found.
If it freezes, the block shown last with “…” at end of line is the first bricked block in that direction.
The line before with “-> ok” is the first usable block before/after the brick.
The application has received excellent reviews, so if you’re one of those people currently facing an EMMC issue, or you had the issue previously and gave up on your device, head on over to the companion thread and give this a go.
Click to expand...
Click to collapse
Original xda news: http://www.xda-developers.com/android/partition-scanner-helps-your-emmc-bricked-devices/
Original thread by hg42: http://forum.xda-developers.com/showthread.php?t=1667886
He even provides PITs for our devices, so get a bit into Linux, and fix it by yourself, You can't make it worse I guess..
Anything more to say? Hang onto it, unbrick it and kick Samsungs ass once again!!
Greetings from Australia!
Sent from my GT-P6200 using xda app-developers app
Bad2hold said:
Original xda news: http://www.xda-developers.com/android/partition-scanner-helps-your-emmc-bricked-devices/
Original thread by hg42: http://forum.xda-developers.com/showthread.php?t=1667886
He even provides PITs for our devices, so get a bit into Linux, and fix it by yourself, You can't make it worse I guess..
Anything more to say? Hang onto it, unbrick it and kick Samsungs ass once again!!
Greetings from Australia!
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
@Bad2hold - have you tried this yourself as I am desperate for help in unbricking my device that Samsung refuse to repair as it is the P-6200L (non-UK model).
I can't use ADB as my pc won't recognise the Tab, have tried flashing the .pit file and firmware but no joy, can't use the partition scanner as I can't get it to scan the internal memory (it scans the external SD card instead).
I can install CWM recovery and also get to stock recovery but the Tab will not go past the white Galaxy Tab logo.
Any help is highly appreciated
There is good chance you can recover. try multiple factory resets. flash earlirst odin package, preferrably with a boot.bin, after flash, and stuck on logo, boot to recovery and factory reset. try wiping a few more times if it is still stuck. i usually have to do this when going back to stock. one time i had to wipe from custom recovery, and a combonation of other things..
If you have recovery, youre lucky.
If you give up, you can for JTAG, normally for hard bricks. mobiltechvideos.com saved me from hardbrick.
Id play around a bit before I send to JTAG.
best of luck..
chrisrotolo said:
There is good chance you can recover. try multiple factory resets. flash earlirst odin package, preferrably with a boot.bin, after flash, and stuck on logo, boot to recovery and factory reset. try wiping a few more times if it is still stuck. i usually have to do this when going back to stock. one time i had to wipe from custom recovery, and a combonation of other things..
If you have recovery, youre lucky.
If you give up, you can for JTAG, normally for hard bricks. mobiltechvideos.com saved me from hardbrick.
Id play around a bit before I send to JTAG.
best of luck..
Click to expand...
Click to collapse
Thanks for the advice mate.
Am going to flash it with the honeycomb firmware it came with from Sammobile and try a few factory resets to see if that works.
If not have found a place in the UK that will JTAG it for £38 if all else fails...:good:
UPDATE: Honeycomb doesn't let me access recovery so no way to wipe from there. Recovery is available on an ICS rom but am reluctant wipe in stock recovery as that's how I go in this mess to begin with :crying:
I currently cant help, as iam travelling without a pc... but this guy who developed this scanner, has pit files available for our device. So there is a good chance to get help from him. And iam sure, with some hours off every week, where u get bored, u can actually fix it by yourself as u already figured out that much... i would love to help, its a challange you know? maybe iam gonna buy a laptop... =p
Update: just curious, is it scanning without a external sd inserted? Because internal and sd are swapped in cwm recovery since 3 versions too...
Sent from my GT-P6200 using xda app-developers app
@Bad2hold - Thanks for the reply, have tried flashing the .pit file but no joy.
Can't get the scanner to scan internal card as it's loaded on my external sd and can't push it to the internal which then means I can't remove the external sd.
Have tried flashing various honeycomb and ICS firmwares with a combination of .pit files, the process flashed fine without errors but still no boot past the white Samsung writing
Sent from my GT-I9300 using xda premium
Just one question:
do I use it if my device got bricked (fortunately it s not the case), or do I use it to remove the brick bug risk from my device?
Thanks for your answer...
unclefab said:
Just one question:
do I use it if my device got bricked (fortunately it s not the case), or do I use it to remove the brick bug risk from my device?
Thanks for your answer...
Click to expand...
Click to collapse
I think we cannot remove the brickbug on stock ICS...that pit file just for solving hardbrick issue...
Sent from my GT-P6200 using xda premium
U can actually remove the brick bug issue, this is, what this post is about.
Basically, you just have to find the bad blocks in your sd partition.
After you found them, all is left, is to repartition your sd around the bricked blocks, which you have to delete from your partition.
He mentions several methods to use adb and other tools, helping to do this.
And i really recommend reading a bit through his first post, found the same problem after a minute:
I also had the following problem:
I couldn't format my internal sdcard with the cm9 recovery. I think it's too big for the mkfs.vfat tool of current cm9. So I installed another recovery, formatted the internal sd (I thought).
This erased all my current backups and downloads, because in reality it was my external sd. Fortunately I had a backup of the external sdcard from before rescuing my phone.
So, you may want to create a backup of your external sdcard first.
Then double check which is your internal sdcard (the UMS partition) and which is your external sdcard.
Or you could remove the external sd completely. But think about when to remove it, because you might need it for some files (e.g. to use the emmc partition scanner).
Click to expand...
Click to collapse
Of course, if u r not familiar with linux, u probably wont fix it in an hour.
But you can learn a lot within an hour. First of all, figure out how to connect your device to adb. (Which is still possible, if you didnt smash your tab against the wall or so...) After that, it should be lot easier to follow his instructions.(not just because u have adb working, but because you know what he is actually talking about.)
And he is really willing to help, so figure out as much as possible after connected to adb and just ask in his post if you get stuck.
Dont forget: if its not a issue by malfunctioning/broken hardware, then you actually can fix everything with your pc, you just need to know how.. so dont give up!!!
here his post again: http://forum.xda-developers.com/showthread.php?t=1667886
And @kersey: what pit file did u flash? The pits he provides are to repartition your SD AFTER you located the bricked blocks. But you cant know, if you cant get his scanner running..? You have to format data partition in recovery after flashing one of those, because of missing file system.
Note: Never flash a stock ICS after you fixed it. It will brick your device again. But u r safe with cm9 and others.
Sent from my GT-P6200 using xda app-developers app
Good news all, after much trial and error and more flashing than your average pervert I have revived my tablet from the dead with a big thank you to hg42 for his scanner and extra advice.
Thanks to all those who helped in this post too :good:
Dude, if you dont mind, what exactly have you done to revive your tab?
Not exactly, just a quick guide to avoid the most common mistakes.
Thanx!
Sent from my GT-P6200 using xda app-developers app
Bad2hold said:
Dude, if you dont mind, what exactly have you done to revive your tab?
Not exactly, just a quick guide to avoid the most common mistakes.
Thanx!
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
It was pretty simple to revive it with hg42's help.
The first thing you need to do is ensure you have CWM recovery, as the scanning tools only work with that.
Download hg42 emmc partition scanner from the link on the first page of this topic and copy to all 5 zip files to your external sd card. You will also need to download hg42's patched .pit file for your model of tab.
Boot into CWM recovery and flash emmc_find_brick_start.zip. This will scan you tab and will freeze on a bad block. Make a note of the number it freezes on.
Now flash the emmc_find_brick_end.zip file and once again make a note of the number the tab freezes on.
You now need to select the patched .pit file that falls within the range of brick start and brick end. e.g. my brick_start was 1074 and brick_end was 2147 so the patched .pit file I flashed with Odin was "P6200_tabplus--patched--brick-between-281-and-2160-MB--FACTORYFS-moved-by-1792-MiB"
I once again entered CWM recovery and did a scan using emmc_scan_all_partitions_once.zip. Which verified there were no errors.
I then booted up the Tab and hey presto it was alive again.
Feeling brave I then flashed the latest Austrian 4.0.4 firmware followed by permanent CWM recovery making sure that I can never do a factory reset using stock recovery which cause the brick to begin with.
Hope the above makes sense to those who need it, I'm sure as you go through the processes above it will.
I'd also like to encourage anyone who uses hg42's emmc tools to offer a donation as without him I would have had a very expensive paperweight or would have had to pay to get it JTAG'd
Happy Boy
Hi all
While trying to root and install custom rom I bricked my friends phone. I have been going crazy trying everything I could to get this brick back to life.
ITS ALIVE AGAIN!!!!!!!!
Thank you kersey for your post on how you got your Tab back.
This is what I did.
I installed the 5 files on the SD card.
120824-151927-emmc_find_brick_end
120824-151927-emmc_find_brick_start
120824-151927-emmc_scan_all_partitions_infinitely
120824-151927-emmc_scan_all_partitions_once
120824-220105-emmc_scan_write
I put the phone into recovery mode and ran 120824-151927-emmc_find_brick_start.
The program started scanning the memory and first froze on 2188.
I got back into recovery and ran 120824-151927-emmc_find_brick_end
once again the program started counting down and froze about 3189.
For this phone the correct pit files were in " pits-N7000_16GB "
I unzipped pits-N7000_16GB and looked for the nearest pit file , which was
N7000_16GB_Q1_20110914--patched--brick-between-1174-and-3321-MB--DATAFS-moved-by-2048-MiB.pit
I then put the phone back into download mode and using Odin flashed the patched pit file above.
Disconnecting the phone from computer I went back into recovery and ran120824-151927-emmc_scan_all_partitions_once
For the first time I was able to do a full scan without the program freezing.
Next step was installing Abyss Kernel 4.2. I then did the regular data wipe/cache wipe/dalvik wipe.
And finally I installed Rocketrom 11.
The phone rebooted and then came back to life.
I checked the internal memory and it was down to 9gb, but who cares as long as its ALIVE AGAIN !!!!
hg42 you sir are an absolute legend. Donation coming your way.
This method definitely works . Just be patient. I hope This helps others aswell
EDIT:
Is there any not so hard way to install the original rom with the pit i need? cm10 works, but i dont like it so much.
p6201dbtlpc_p6201xxlpc_p6201xxlp3_home.tar i would like to use
but i only know to flash this in odin, becouse it is no zip, i have no clue how to flash it in cwm
thanks for an answer!
-----------------
Your post should be on first post added =)
And in http://forum.xda-developers.com/showthread.php?t=1807002 !
Thanks for it!
kersey said:
It was pretty simple to revive it with hg42's help.
The first thing you need to do is ensure you have CWM recovery, as the scanning tools only work with that.
Download hg42 emmc partition scanner from the link on the first page of this topic and copy to all 5 zip files to your external sd card. You will also need to download hg42's patched .pit file for your model of tab.
Boot into CWM recovery and flash emmc_find_brick_start.zip. This will scan you tab and will freeze on a bad block. Make a note of the number it freezes on.
Now flash the emmc_find_brick_end.zip file and once again make a note of the number the tab freezes on.
You now need to select the patched .pit file that falls within the range of brick start and brick end. e.g. my brick_start was 1074 and brick_end was 2147 so the patched .pit file I flashed with Odin was "P6200_tabplus--patched--brick-between-281-and-2160-MB--FACTORYFS-moved-by-1792-MiB"
I once again entered CWM recovery and did a scan using emmc_scan_all_partitions_once.zip. Which verified there were no errors.
I then booted up the Tab and hey presto it was alive again.
Feeling brave I then flashed the latest Austrian 4.0.4 firmware followed by permanent CWM recovery making sure that I can never do a factory reset using stock recovery which cause the brick to begin with.
Hope the above makes sense to those who need it, I'm sure as you go through the processes above it will.
I'd also like to encourage anyone who uses hg42's emmc tools to offer a donation as without him I would have had a very expensive paperweight or would have had to pay to get it JTAG'd
Click to expand...
Click to collapse
ICS update and emmc bug
Hi; not sure if right forum, but here goes ,
I updated my tab plus to ics 4.0.4 using alpn and xlpn file from sammobile using odin from pc,
tab was never rooted only used a launcher
so my question is after i have installed ics and will not root or use cwm ,will i still have to worry about the emmc bug and if yes
is it best just to go back to honeycomb
btw all is running well on ics just worried about bricking
thank you in advance
doaft said:
Hi; not sure if right forum, but here goes ,
I updated my tab plus to ics 4.0.4 using alpn and xlpn file from sammobile using odin from pc,
tab was never rooted only used a launcher
so my question is after i have installed ics and will not root or use cwm ,will i still have to worry about the emmc bug and if yes
is it best just to go back to honeycomb
btw all is running well on ics just worried about bricking
thank you in advance
Click to expand...
Click to collapse
If you chose to do a factory restore via stock recovery, which is what you have due to not being rooted and not having CWM installed there is a very big chance you may brick your device. I speak from experience!!!
If you are that worried I would flash back to honeycomb rather than risking having an expensive paperweight
Sent from my GT-I9300 using xda premium
A little of my own experience with superbrick
Bad2hold said:
Dude, if you dont mind, what exactly have you done to revive your tab?
Not exactly, just a quick guide to avoid the most common mistakes.
Thanx!
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
You guys can follow this guide I wrote for the Galaxy Tab 7.7 (which also suffers from mmc_cap_erase) : http://forum.xda-developers.com/showthread.php?t=1862294
Just replace the partition numbers with the ones parted shows you.
The problem is, either way you followed, after being revived your tab will :
- rebrick everytime you flash anything
- Have less than 1gb of internal storage
- Hang everytime you want to download an app or whatever
To fix the last 2 problems, you need to make an ext2sd script to swap your internal-sd and external-sd.
To do so, go to /dev/block/vold : you'll see two files named with numbers (i.e : 22:48 179:48), note the name of those 2 files (one of them is your external-sd mount point)
Then replace the "xxx:xx" in the following script with the name of the first file :
Code:
mount -t vfat -o umask=0000 /dev/block/vold/xxx:xx /storage/sdcard0
mount -o bind /data/media /storage/sdcard1
Save this script in a file called ext2sd1.sh and use Script Manager to run it "as root" and "at boot", now reboot and go to settings/storage : if the first file was your extsd mount point your internal and external storage should now be swapped (i.e : if you have a 64gb external sdcard the settings will show : internal storage : 64gb, and you can actually install 64gb of apps).
If it didn't work, replace the xxx:xx in the script with the name of the second file, then it should work.
Good luck guys, this superbrick is a damn pain in the ass, we can thank sammy for it
P6200
Hello man... I saw your post ''Good news all, after much trial and error and more flashing than your average pervert I have revived my tablet from the dead with a big thank you to hg42 for his scanner and extra advice.
Thanks to all those who helped in this post too'' ... I have the same problem with my P6200. Please give me that scanner to fix it or tell me how to put my tablet back On... Thanks
Androguide.fr said:
You guys can follow this guide I wrote for the Galaxy Tab 7.7 (which also suffers from mmc_cap_erase) : http://forum.xda-developers.com/showthread.php?t=1862294
Just replace the partition numbers with the ones parted shows you.
The problem is, either way you followed, after being revived your tab will :
- rebrick everytime you flash anything
- Have less than 1gb of internal storage
- Hang everytime you want to download an app or whatever
To fix the last 2 problems, you need to make an ext2sd script to swap your internal-sd and external-sd.
To do so, go to /dev/block/vold : you'll see two files named with numbers (i.e : 22:48 179:48), note the name of those 2 files (one of them is your external-sd mount point)
Then replace the "xxx:xx" in the following script with the name of the first file :
Code:
mount -t vfat -o umask=0000 /dev/block/vold/xxx:xx /storage/sdcard0
mount -o bind /data/media /storage/sdcard1
Save this script in a file called ext2sd1.sh and use Script Manager to run it "as root" and "at boot", now reboot and go to settings/storage : if the first file was your extsd mount point your internal and external storage should now be swapped (i.e : if you have a 64gb external sdcard the settings will show : internal storage : 64gb, and you can actually install 64gb of apps).
If it didn't work, replace the xxx:xx in the script with the name of the second file, then it should work.
Good luck guys, this superbrick is a damn pain in the ass, we can thank sammy for it
Click to expand...
Click to collapse
hey dude it's my first post in xda
i've succeded to unbrick my device but my internal memory is shrink a lot into 700+ mb but i don't understand how to use the script so
can u explain step by step ?
one can help me ??
hai everybody.... i'm from indonesia.., my friend just give me samsung galaxy tab 7 plus... ( GT-P6200 ) without any boxes, last day i try to get ICS update from kies , but the application won't update my firmware , so i try the alternative direction.
i try another application - Odin3-v1.85 and download the firmware..., but the fact is after few second running it self , the prosess can't continues get fail after
Note : i;m using : P6200OXALQ1_P6200XXLQ1_P6200XXLQ1_HOME.tar.md5 firmware
<ID:0/017> Firmware update start..
<ID:0/017> cache.img
<ID:0/017> NAND Write Start!!
<ID:0/017> factoryfs.img
<ID:0/017> hidden.img
<ID:0/017> recovery.img
<ID:0/017> Sbl.bin
<ID:0/017>
<ID:0/017> Complete(Write) operation failed. >>> FAIL...
anyone can help me .... please
Related
This has driven me insane. I am close to throwing this tablet out the window. So far I have had nothing but horrible experiences with it. I have a gt3113 and I can't delete several directories on the sdcard. I've tried through file managers, through my pc and through terminal emulator, nothing removes the files.
WTF do I do? I'm rooted, running stock 4.04. Trying to keep it together here.
1-May be through root browser lite and try to long press the files and fix permissions as read and write before delete??
2-or format data in cwm ( be so cautious when doing this)?
3- or as last resort flash a firmware with pit file and repartition ticked in odin? (also be very cautious when doing this)
Sent from my GT-P5100 using xda app-developers app
Mohamedselim said:
1-May be through root browser lite and try to long press the files and fix permissions as read and write before delete??
2-or format data in cwm ( be so cautious when doing this)?
3- or as last resort flash a firmware with pit file and repartition ticked in odin? (also be very cautious when doing this)
Sent from my GT-P5100 using xda app-developers app
Click to expand...
Click to collapse
I tried options 1 and 2, neither worked. 3 may have worked but I found an easier and safer solution.
Not sure if this part helped or not but in terminal I ran:
Code:
su
/system/bin/fsck_msdos -y /dev/block/vold/179:25
reboot
then I was able to delete the files from /mnt/sdcard/ instead of where I was trying to delete them from, which was /sdcard/
and it worked! Thanks a lot for your suggestions! Not sure what caused this in the first place, but if anyone else runs into this problem maybe they'll find this thread.
Bentenrai said:
This has driven me insane. I am close to throwing this tablet out the window. So far I have had nothing but horrible experiences with it. I have a gt3113 and I can't delete several directories on the sdcard. I've tried through file managers, through my pc and through terminal emulator, nothing removes the files.
WTF do I do? I'm rooted, running stock 4.04. Trying to keep it together here.
Click to expand...
Click to collapse
Bentenrai said:
I've had this thing for about a week and haven't even been able to use it yet. It's been in a bootloop or fc loop for the entire time. I finally got it running but the internal SD filled up completely with junk files and directories that couldn't be deleted. I couldn't install any apps since the stock firmware doesn't allow installing to an external card... CM9/10 force close looped because of lack of space I assume. I had narrowed down the problem but couldn't fix it, and of course as soon as you ask for help you figure it out anyway I'll give it a chance now.
Click to expand...
Click to collapse
To whom ever can help out, I have a Galaxy Tab 2 7.0, and cannot seem to get my problem resolved by myself. I have somehow inadvertently managed to install an update.zip that had or had no relations to this particular OS of this particular model of android.
My problem is that I wanted to be able to, migrate my apps to the external SdCard or extSdCard, and I think I used an update.zip designed for the cellphone HTC Evo 4g. Not realizing that I will be later unable to use the restore feature from a previous backup I had made using CWM 6.0.1.0 to recover from my inadvertent mistake (not to comfortable making a backup, and thinking I can restore properly anymore, like I can on my cellphone that I am spoiled with).
Silly of me to think I could use an update.zip designed for another type of device such as the HTC Evo 4g, but… (anyway my bad what was I thinking…?). The update.zip, by the way is "dtapps2sd-2.7.5.2-signed", like I mentioned this is clearly designed for the HTC Evo 4g, and not for the Samsung GT2 7.0.
The problem I experience now is not complete lose of my GT2 7.0 device I can still install and change out OS through the CWM-Recovery and install apps through the Android Market. I do however experience the inability to check my Storage properties under my Settings profile. When I attempt to click on this link it pauses for a second as if it wants to open up and perform its normal function, then reports an error "Unfortunately, Settings has stopped". Now at this point this is where I would have to mention another issue similar to this one, and that is at startup. When I first start the device up and it runs through its process of startup configuration. It will then report a list of programs that are prevented from running properly it as follows;
Unfortunately, the process android.process.media has stopped.
Unfortunately, My Files has stopped.
Unfortunately, Factory Test has stopped.
Unfortunately, MTP has stopped.
Now my question is, how is-it possible to resolve this issue. I have tried to complete a fresh install of the OS, CWM-Recovery, and also attempted to wipe everything possible that the recovery will allow, but I am not expecting much, as I cannot even get the backup and restore feature to work efficiently enough to provide me with what I need it to do…
I have provided this post with a download of the update.zip I used as well as the version of the OS I have provided my Samsung GT2 7.0. If anyone can shine some insight on what direction I should attempt to do to resolve this issue I would be more that interested to take a look at what I could use to correct this error of mine…
-Samsung GT2 7.0 - OS (Use the Download link above the Rosewell signature)
http://forum.xda-developers.com/showthread.php?t=1784318
-dtapps2sd-2.7.5.2-signed
http://www.mediafire.com/?7jpc5oudzt6o76p
I might be comfortable to ADB Shell into my device to make changes, or if one was able provide me an update.zip/script that would be great. Also is there a better recovery out there than the ClockWorkRecovery.
Better recovery so you may try twrp or so
Try install a fresh firmware preferably with a pit file from odin pc
Sent from my GT-I9300 using xda app-developers app
Mohamedselim said:
Better recovery so you may try twrp or so
Try install a fresh firmware preferably with a pit file from odin pc
Click to expand...
Click to collapse
Mohamedselim, Thanks...
Will look into this..., any links by the way in regards to the "fresh firmware with a pit file"...?
Have you tried downloading and flashing a full Odin tar file to restore your device to stock?
imnuts said:
Have you tried downloading and flashing a full Odin tar file to restore your device to stock?
Click to expand...
Click to collapse
Yeap...!, I have tried this already, have had no promising results...
This is the only compatible version of a .pit file...;
http://forum.xda-developers.com/showthread.php?t=1642744
Can anyone provide me another one for the GT-p3113...?
Just checking in..., and wondering if anyone has a solution for this...?
Factory reset in stock recovery. So Odin a stock Rom and before u install anything custom, do a factory reset in recovery after u Odin back to stock. Then flash away.
I imagine you have alrdy tried a factory reset using a custom recovery.
WAIT!!! You don't have to factory reset, just reboot into CWM recovery ang go to mounts and storage>wipe internal storage. Confirm and reboot. You will lose anything on the sdcard but your apps will stay.
RomsWell said:
Factory reset in stock recovery. So Odin a stock Rom and before u install anything custom, do a factory reset in recovery after u Odin back to stock. Then flash away.
I imagine you have alrdy tried a factory reset using a custom recovery.
Click to expand...
Click to collapse
MultipleMonomials said:
WAIT!!! You don't have to factory reset, just reboot into CWM recovery ang go to mounts and storage>wipe internal storage. Confirm and reboot. You will lose anything on the sdcard but your apps will stay.
Click to expand...
Click to collapse
1. I am all over the Factory resets, and wipes.
2. Already tried Stock Rom(s).
3. I believe my problem is a bootloader, or partitioning script. (As this denies me access from inside settings>storage where I can view my allocated size, and Restore to Factory button. In addition in CWM, I am not allowed to mount/sdcard(internal), extSdCard is ok though. Also, I cannot plug Tab via USB to check contains on Internal or External sdcard, but I can remove the External to transfer data from it via sdcard slot on PC...)
Maybe you can recommend a good Stock Rom, so I can give that ago...
I was in the process last night, and could not get a good connection with Heimdall or Odin. I am now looking into driver issues, so...
Ok, so I was successful in taking RomsWell and MultipleMonomials advice, and was able to return my device back to "Normal" state, including "Stock Recovery". But I still have the original problem as in my request I asked in my first post...
I do however experience the inability to check my Storage properties under my Settings profile. When I attempt to click on this link it pauses for a second as if it wants to open up and perform its normal function, then reports an error "Unfortunately, Settings has stopped". Now at this point this is where I would have to mention another issue similar to this one, and that is at startup. When I first start the device up and it runs through its process of startup configuration. It will then report a list of programs that are prevented from running properly it as follows;
Unfortunately, the process android.process.media has stopped.
Unfortunately, My Files has stopped.
Unfortunately, Factory Test has stopped.
Unfortunately, MTP has stopped.
Click to expand...
Click to collapse
I think now, if I cannot get a sizable remedy..., is just to try and send it in Samsung so they can take a look at it...
Any suggestions...?
FYI; I have also tried connecting to Kies, but due to the inability to posses a "MTP" (Media Transfer Protocol), is the reason I cannot connect to my SdCard & extSdCard. I can "PTP" (Picture Transfer Protocol) into it, using "adb shell", but not using "MTP"...
So I do not know how much "MTP" has to do with this relationship of the other three items that I mentioned in my bullet list in my quote, but...
Anyway, I don't know what I am trying to say, but thank you two, for getting me this far...!
grassy-sneakers said:
1. I am all over the Factory resets, and wipes.
2. Already tried Stock Rom(s).
3. I believe my problem is a bootloader, or partitioning script. (As this denies me access from inside settings>storage where I can view my allocated size, and Restore to Factory button. In addition in CWM, I am not allowed to mount/sdcard(internal), extSdCard is ok though. Also, I cannot plug Tab via USB to check contains on Internal or External sdcard, but I can remove the External to transfer data from it via sdcard slot on PC...)
Maybe you can recommend a good Stock Rom, so I can give that ago...
I was in the process last night, and could not get a good connection with Heimdall or Odin. I am now looking into driver issues, so...
Click to expand...
Click to collapse
Did you try formatting internal storage in CWM?
MultipleMonomials said:
Did you try formatting internal storage in CWM?
Click to expand...
Click to collapse
I am not quite confident on how much this will work. As I have tried this multiple times to wipe "Wipe Factory/Data", "Wipe Cache", including all the partitions under the "Advance" section found in CWM Recovery. Even using TWRP Recovery.
Per this post; I just attempted to flash a "Stock Rom", but not before doing a factory/data, cache wipe using "Stock Recovery", including after a successful install...
No luck, the same problem still exist as above...
Ok, this was all just the rudest experience I put my self threw. As I have an HTC Evo 4g - cellphone and have become comfortable with installing ROM's, Kernels, and Updates.zips, as well as, other modification. All threw the Recovery designed for this particular device, and don't get me wrong there has been a couple of times. Maybe more than a couple, more like a few times I have installed incompatible downloads I find in the XDA forums. Which makes this screw up, difficult form me to know that as long as you can get into a Download/Bootloader or a modified Recovery designed for a particular device that was successful flashed correctly. Well the screw up are easily redeemed/recoverable.
So, to make a long story short. After having called Samsung Customer Care (the 1-800-SAMSUNG) number, it seems to have been a External SdCard getting in my way from having been real short from sending my Tab off to the repair department (where ever it is...). I in fact already had it in an envelope, all I needed was an address to send it to. Anyway the nice person on the other side of the phone requested that I remove my External SdCard, and confirm that I was able to get into my "Storage" tab under my settings. Well after success getting this option back, I then made the suggestion that maybe my Eternal SdCard is corrupt or incorrectly formatted. She then agreed maybe this is the case. After ending the phone call. I quickly restarted my Tab, again only to find out that I was no longer receiving the error messages like mentioned above, which is great, because after multiple flashes of "Stock Roms w/Stock Recovery", and forcing myself to believe that it was a system install error. It in fact the External SdCard in place preventing me from throwing my Tab against the wall / in the mail to Samsung Repair Center...
"Man what an ordeal...!!!"
Thanks to all that helped with the suggestions, as to what direction I most defiantly tried.
I am now in the process, since I am living back in Stock mode. To receive an OTA (Over The Air) Update, and am still in the process of seeing if this thing still possess any residual silent errors...
I will keep you posted.
If not, well it off to happy rooting for me...!!!
That is it, my problem is resolved. Damnedest thing this problem of mine, it seems the only thing I screwed up was the micro SdCard. to the point it was the cause of all the error I received when I started up the device, as well as when I attempted to access my storage through me settings options...!!!
Now re-rooted, and a happy camper, Cheers...!
Hi there,
i got a 6800 with stock (but rooted) ICS running and wanted to try the ZETA 4.0 Rom from the development section - what seems to be a minor task turned into disaster ;-/
I followed the instructions from the message in the development forum:
quote:
Do a Nandroid backup!
Copy the Zeta to your SD
(optional) Wipe Data/factory reset
Wipe Dalvik Cache
Install zip from sd
Reboot
I used CWM to backup all information, (which took like 30 mins and ended in an error message)
and when i clicked on "wipe data/factory reset" in recovery things went seriously wrong ...
it seemed to take a very long time (15`+mins) and then rebooted
I am now stuck at the white/blue glowing samsung logo
I can get back into recovery, but when i try to install the "Zeta Rom V4.0.zip" file from the SD card, i just get a
E: signature verification failed in red lettering ... before that, the package is found/opened/verified
also, the cwm.zip is opening, but acting very weired (cant select with the volume keys
The weired thing to me is that I didnt even install the Zeta package when things got ugly!!! - I just did a data wipe
could some good soul pls help me out ...
thx in advance for your time
Al
Hi dude,
Did you try the download mode? (Powerbutton + vol down.) If this still works, your good.
Just get the .Pit file for your device from www.sammobile.com
Now flash this .Pit file with your pc using Odin. If you don't know how to use Odin, please find the thread for this and.read it to the letter! Whatever you do, DON'T set the function for REPARTITION.. that would be THE END dude. Beware!
I had fckd up my tab too, but the Odin solution works fine. After this you can install a new recovery even with Odin and your good M8
After that your good to go and please, of you want to go custom...try the Paranoid Android or Singha light rom . Both are top working, and with the pimp my rom addon (you will find it :good: ), you won't even think about another flash again.
Just don't panic..Good luck!
Regards,
Axelman
Sent from my GT-P6800 using xda app-developers app
Hi there, and thx for responding ...
I can get into download mode (pwr / vol-)
a few extr problems ... I lost the cable to hook up the 7.7 to a computer (3 children household, dont ask ) ... the only form to get files to the tab is pulling the SD card and manually copy files on it and put it back ...
I located 6800.pit files ... so would I just copy those 6800.pit files to the SD and install them in download mode? - could somebody confirm this?
again, thx for answering
Al
sorry, also - could you point me to the 6800.pit file on sammobile ? .... I seem to be unable to locate it ...
thx!
al128 said:
sorry, also - could you point me to the 6800.pit file on sammobile ? .... I seem to be unable to locate it ...
thx!
Click to expand...
Click to collapse
nevermind ... it seems I found it here on xda ...
http://forum.xda-developers.com/showpost.php?p=27636101&postcount=4
(could you confirm that this is the correct one ¿ ... can this be flashed directy via recovery¿
I also leant that I seemed to have superbricked my 6800 by using the "wipe data/factory reset" option in recovery, which supposedly is a bug in the firmware ...
absolutely not amused !
thx for helping
Hi,
Don't use the recovery anymore... as you said, it gave an error anyway. Get a cable and do it the only right way by using Odin.
The super brick means that also the download mode is corrupted...that's the end of the tab for sure, but you still can use the download mode so you are good.
It's your call, but in my opinion your better off with the official download mode (lucky you to still have it) then using a corrupted recovery.
For your info... I would use the Gtp6800 LQ2 .PIT file. If your tab is a 6800 offcorse .
Goodluck m8
Regards,
Axelman
Sent from my GT-P6800 using xda app-developers app
thx axelman, dont worry - I will do it right ... (well, as good as i can do it)
...getting a cable first thing tomorrow ... I cant afford to lose my tab&phone
cheers, Al
Thread moved to Q & A section, post in the relevant section next time.
al128 said:
thx axelman, dont worry - I will do it right ... (well, as good as i can do it)
...getting a cable first thing tomorrow ... I cant afford to lose my tab&phone
cheers, Al
Click to expand...
Click to collapse
He dude,
Use a download from sammobile. Get an account and download the official firmware there. It is the safest way!
I dont know were you are from, but the first ICS build was the open Austria.. P6800XXLQ1
You could use that version, or get the newer version p6800XXLQ2. But you can get any version you like..
GoodLuck
Regards,
Axelman
Axelman8 said:
He dude,
Use a download from sammobile. Get an account and download the official firmware there. It is the safest way!
I dont know were you are from, but the first ICS build was the open Austria.. P6800XXLQ1
You could use that version, or get the newer version p6800XXLQ2. But you can get any version you like..
GoodLuck
Regards,
Axelman
Click to expand...
Click to collapse
I managed to get all things running as per your advice:
I can connect and flash both the stock austrian rom and stock austrian .pit file (I even get a green "pass" in odin!) ... but I am still in a boot trap. I am pretty sure I have those corrupted blocks in the var. partitions ...
I found the following description here on xda ... but it says to TICK the "repartition" ... so I am kind of confused ...
(snip)
What Do You Need To Fix This
1. Odin and Pit get it Here ---> Odin3 v1.85.rar Pit and CWM Include in Odin.
2. Use this Stock Rom P6800XXLQ1_P6800OXALQ1_ATO. This is Open Austria Stock Rom Get it here ==>> Download and Unzip.
3. USB Connector.
3. All You Have and you a ready to Go.
4. Open Odin
5. Tab to Download Mode (( Start + Down Vol ))
6. Connect USB
7. Make Sure the port com detected.
8. Put the Pit file to PIT. Make Sure the PIT is GT-P6800 PIT for P6800XXLQ1_P6800OXALQ1_ATO.pit
9. On Files PDA Make Sure it's XXLQ1_OXALQ1_ATO.md5
10. Make Sure Tick Re-Partition, Auto Reboot and F. Reset Time
11. If you are Ready. Hit the START.
12. If you are successful Com Port box on the Blue and Green in color after the reset and show a pass.
(/snip)
I am confused ... should i tick it or untick it? ... it seems to automatically tick itself on whenever you add a .pit file - so far i UNticked the repartition option
I guess I need to go the whole "adb" route, but it seems to be way over my head ... I cant even get adb to run (a dos window opens and closes immediately) ... pretty frustrating ... there are 70 pages or so to read ... and while I do understand the whole concept, I cannot do it (operationally) ...
well, insult coming to injury ... I am also looking for a job and need my cel desperately
again, thx to all the folks looking into the matter and lending a hand!
cheers, Al
Go back to stock
al128 said:
I managed to get all things running as per your advice:
I can connect and flash both the stock austrian rom and stock austrian .pit file (I even get a green "pass" in odin!) ... but I am still in a boot trap. I am pretty sure I have those corrupted blocks in the var. partitions ...
I found the following description here on xda ... but it says to TICK the "repartition" ... so I am kind of confused ...
(snip)
What Do You Need To Fix This
1. Odin and Pit get it Here ---> Odin3 v1.85.rar Pit and CWM Include in Odin.
2. Use this Stock Rom P6800XXLQ1_P6800OXALQ1_ATO. This is Open Austria Stock Rom Get it here ==>> Download and Unzip.
3. USB Connector.
3. All You Have and you a ready to Go.
4. Open Odin
5. Tab to Download Mode (( Start + Down Vol ))
6. Connect USB
7. Make Sure the port com detected.
8. Put the Pit file to PIT. Make Sure the PIT is GT-P6800 PIT for P6800XXLQ1_P6800OXALQ1_ATO.pit
9. On Files PDA Make Sure it's XXLQ1_OXALQ1_ATO.md5
10. Make Sure Tick Re-Partition, Auto Reboot and F. Reset Time
11. If you are Ready. Hit the START.
12. If you are successful Com Port box on the Blue and Green in color after the reset and show a pass.
(/snip)
I am confused ... should i tick it or untick it? ... it seems to automatically tick itself on whenever you add a .pit file - so far i UNticked the repartition option
I guess I need to go the whole "adb" route, but it seems to be way over my head ... I cant even get adb to run (a dos window opens and closes immediately) ... pretty frustrating ... there are 70 pages or so to read ... and while I do understand the whole concept, I cannot do it (operationally) ...
well, insult coming to injury ... I am also looking for a job and need my cel desperately
again, thx to all the folks looking into the matter and lending a hand!
cheers, Al
Click to expand...
Click to collapse
Dude dd you get through? If not just go to here: http://www.sammobile.com/firmware/?page=3&model=GT-P6800&pcode=0&os=1&type=3#firmware
and download the latest file.
1. It will download as a zip file so make a new folder on your pc and extract it there.
2. Start odin and dont tick anything! leave everything as is. then select pda and choose the extracted file and press start.
3. after you do that just look fror rooting instructions.
BEWARE! DONT WIPE WITH OFFICIAL RECOVERY BECAUSE YOU'LL LOSE EVERYTHING!
dude, thats exactly what I am doing - and it works (all img transfer correctly, i get "PASS" in odin) ... but the tab still is hanging in a boot trap.
I seem to have those dreaded corrupt blocks in the internal SD ...
UPDATE!!!!
UPDATE!!!!
UPDATE!!!! - finally some light at the end of the tunnel ...
I seem to have managed to push HC 3.2 (Hong Kong version, which is where my tab came from) somewhat successfull on to the tablet... but I still get the following error messages
after a reboot, I get to the following screen:
COULD ANYBODY PLS TRANSLATE THIS !!!!!!!... and better yet, suggest what to enter ... I am stuck right there, no idea how to move on (enter doesnt do the trick, nor my google account name ...)
the good news is, other than that the tab behaves pretty normal (volume rockers really increase/decrease volume, keyboard works normal, i can get into a (chinese) shut down menu and it shuts down pretty normally (as opposed to a hard reboot)
would a hongkong 3.2 pit file help with mounting the e: drive?
any thoughts
thx, Al
Enter your password
Sorry, please retry!
word by word translation as you requested.
Sent from my GT-P6800 using xda app-developers app
bruce16878 said:
Enter your password
Sorry, please retry!
word by word translation as you requested.
Sent from my GT-P6800 using xda app-developers app
Click to expand...
Click to collapse
the /data partition is corrupted... you need to repair it for the device to be fully functional.
edan1979 said:
the /data partition is corrupted... you need to repair it for the device to be fully functional.
Click to expand...
Click to collapse
any pointers on HOW ¿¿¿¿
thx, Al
read this guide carefully http://forum.xda-developers.com/showthread.php?t=1862294
ONLY FOLLOW PART 3 to check your /data partition... starting from this point
Code:
Now we are going to use e2fsck to check our new partitions for errors, but not only, it also fixes some erros and it will even for example create lost & found in /data
edan1979 said:
read this guide carefully http://forum.xda-developers.com/showthread.php?t=1862294
ONLY FOLLOW PART 3 to check your /data partition... starting from this point
Code:
Now we are going to use e2fsck to check our new partitions for errors, but not only, it also fixes some erros and it will even for example create lost & found in /data
Click to expand...
Click to collapse
Hi there,
there def. is a problem in the /data directory ... it cannot be mounted and it cannot be formated out of cwm v5.0.2.7
below i have a snip of what I did with e2fsck ... there seem to be some problem
_____________________________
C:\Program Files\Android\android-sdk\platform-tools>adb devices
List of devices attached
46411980122B42BE recovery
C:\Program Files\Android\android-sdk\platform-tools>adb shell
~ # e2fsck -yfDC0 /dev/block/mmcblk0p10
e2fsck -yfDC0 /dev/block/mmcblk0p10
e2fsck 1.41.6 (30-May-2009)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p
10
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # e
C:\Program Files\Android\android-sdk\platform-tools>
_____________________
what is my problem with e2fsck¿
thx,
al
Step by step you will get there.
Regards,
Axelman
Axelman8 said:
Step by step you will get there.
Regards,
Axelman
Click to expand...
Click to collapse
Just to close this chapter ... and for reference to other future folks ...
I managed to get my tab working again, but it was a pita to get there ...:laugh: ... good thing - i learnt a lot in the process
finally i ran a check on the data partition (tool from the superbrick thread) ... and whilst all sectors reported "OK", there was a section where the check took some 10 times longer than normal.
I then used the .pit files provided from the superbrick thread, flashed those with odin, with the option "enable repartition", b/c thats what the .pit files does ... I was quite nervous doing so, though ... I was on the generous side with the "non usable" sectors on the data partition ... so my 7.7 now only has about 8gig of internal SD - I lost about half of it :crying:
then cleared the cache/data/davlic in cmw 6.x ... and flashed the original 3.2 rom over, which booted up - then flashed the shangha ( or so ?) Rom from the developer section a slim version of ICS 4.0.4.... and voilá ... the tab runs like a champ!
cheers,
al
Hey everyone, this is my first thread. I'm really desperate. Here's the thing: yesterday my GF bought a phone (Galaxy SL i9003), previous owner flashed it with custom ROM and boke something, I wasn't sure what till now (in internal memory space it showed UNAVALIBLE), I decided to flash stock ROM to make it work.
I've spent ~10 hours straight but couldn't reach any result.
//I don't use any links or attach photos, because I can't, I insert spaces in them//
1. When I flash it, using ODIN, I use 5-file stock rom (XKPQ), it's ok (odin shows PASS), then the phone reboots and I get this in recovery:
dropbox. com/s/1hnim2sn1dphr6c/IMG_20130617_165950.jpg
As I've come to understand, there is a problem with internal memory, so I googled a little more and found this: androidforums. com/incredible-all-things-root/456898-my-phone-dead-single-tear .html
2. Then I tried to do as described on that forum, installed droid SDK, pushed those 6 files (after applying cf root, so i can access othere options in recovery), applied chmod to them, but I can't seem to do the last point:
Code:
parted /dev/block/mmcblk0 mkfs ext2
This exact command does nothing, only (for some reason) reboots the recovery. And, as you can see on my screenshot, the partition that doesn't work is mmcblk0p3, but when i try to do parted /dev/block/mmcblk0p3 mkfs ext2, it says 'could not stat device - no such file or directory'.
What should I do? Is there a way to fix my problems or is it dead and service center is the only option?
P.S. I'm not experienced with samsungs, so maybe I figured the problm wrong, help me, please!
devcor said:
Hey everyone, this is my first thread. I'm really desperate. Here's the thing: yesterday my GF bought a phone (Galaxy SL i9003), previous owner flashed it with custom ROM and boke something, I wasn't sure what till now (in internal memory space it showed UNAVALIBLE), I decided to flash stock ROM to make it work.
I've spent ~10 hours straight but couldn't reach any result.
//I don't use any links or attach photos, because I can't, I insert spaces in them//
1. When I flash it, using ODIN, I use 5-file stock rom (XKPQ), it's ok (odin shows PASS), then the phone reboots and I get this in recovery:
dropbox. com/s/1hnim2sn1dphr6c/IMG_20130617_165950.jpg
As I've come to understand, there is a problem with internal memory, so I googled a little more and found this: androidforums. com/incredible-all-things-root/456898-my-phone-dead-single-tear .html
2. Then I tried to do as described on that forum, installed droid SDK, pushed those 6 files (after applying cf root, so i can access othere options in recovery), applied chmod to them, but I can't seem to do the last point:
Code:
parted /dev/block/mmcblk0 mkfs ext2
This exact command does nothing, only (for some reason) reboots the recovery. And, as you can see on my screenshot, the partition that doesn't work is mmcblk0p3, but when i try to do parted /dev/block/mmcblk0p3 mkfs ext2, it says 'could not stat device - no such file or directory'.
What should I do? Is there a way to fix my problems or is it dead and service center is the only option?
P.S. I'm not experienced with samsungs, so maybe I figured the problm wrong, help me, please!
Click to expand...
Click to collapse
Idk what the problem is.. but try flashing it AGAIN, but this time select Re-partition.
nbrian2012 said:
Idk what the problem is.. but try flashing it AGAIN, but this time select Re-partition.
Click to expand...
Click to collapse
I did. With, without it. I reflashed different roms hundreds of times.
you should parted mmcblk0 not mmcblk0p3.
and i assumed u have micro sdcard inserted.
Sent from my Galaxy Nexus
chongns said:
you should parted mmcblk0 not mmcblk0p3.
and i assumed u have micro sdcard inserted.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Yeah, I tried, but it only reloads recovery for some reason.
Any ideas?
Hello everyone, I am in need of serious help. I have the Verizon Galaxy S3 4.3 and I have hardbricked the device. The phone is completely unresponsive.
I will attempt to give all the details of how I came to this without boring everyone to death with inane facts. So here goes; I first rooted the phone around November. Used Odin, had ClockworkMod installed and even managed to teach myself (with the help of folks like you all here), how to circumvent Verizon's pesky bootloaders (both unlocked and then relocked). Everything was running smoothly until I had left my phone unattended and plugged into my computer. The Verizon updater forced 4.3 on me leaving me scrambling to figure out to to regain root access. I did manage to gain the root access (although, I'm not 100% sure how so) and once again, everything was fine.
I began using TitaniumBackup to starting removing some bloatware and moving system apps to the SD card. I decided that I had no use for the "Samsung Link" app and I removed it. Once I returned from the reboot, I noticed that the icon for the bootloader was on the screen indicating that it was unlocked. I the did a quick search and app file for the "EZ Unlock" app. I installed the file, ran the program, did and reset and DEAD. Nothing. I've sat at the PC for the better part of the last 24 hours, have read hundreds of posts and tried more methods than I care to count. So far nothing has worked.
I'm desperately hoping that I will be able to find my answers by reaching out to the community as I have no funds to send my phone anywhere and I am past the warranty period. You guys are probably my last hope. Thanks in advance to anyone who helps out. It means a lot.
TwistedPoet said:
Hello everyone, I am in need of serious help. I have the Verizon Galaxy S3 4.3 and I have hardbricked the device. The phone is completely unresponsive.
I will attempt to give all the details of how I came to this without boring everyone to death with inane facts. So here goes; I first rooted the phone around November. Used Odin, had ClockworkMod installed and even managed to teach myself (with the help of folks like you all here), how to circumvent Verizon's pesky bootloaders (both unlocked and then relocked). Everything was running smoothly until I had left my phone unattended and plugged into my computer. The Verizon updater forced 4.3 on me leaving me scrambling to figure out to to regain root access. I did manage to gain the root access (although, I'm not 100% sure how so) and once again, everything was fine.
I began using TitaniumBackup to starting removing some bloatware and moving system apps to the SD card. I decided that I had no use for the "Samsung Link" app and I removed it. Once I returned from the reboot, I noticed that the icon for the bootloader was on the screen indicating that it was unlocked. I the did a quick search and app file for the "EZ Unlock" app. I installed the file, ran the program, did and reset and DEAD. Nothing. I've sat at the PC for the better part of the last 24 hours, have read hundreds of posts and tried more methods than I care to count. So far nothing has worked.
I'm desperately hoping that I will be able to find my answers by reaching out to the community as I have no funds to send my phone anywhere and I am past the warranty period. You guys are probably my last hope. Thanks in advance to anyone who helps out. It means a lot.
Click to expand...
Click to collapse
Ok, Can you boot to Odin mode (dowload mode)?
TwistedPoet said:
Hello everyone, I am in need of serious help. I have the Verizon Galaxy S3 4.3 and I have hardbricked the device. The phone is completely unresponsive.
I will attempt to give all the details of how I came to this without boring everyone to death with inane facts. So here goes; I first rooted the phone around November. Used Odin, had ClockworkMod installed and even managed to teach myself (with the help of folks like you all here), how to circumvent Verizon's pesky bootloaders (both unlocked and then relocked). Everything was running smoothly until I had left my phone unattended and plugged into my computer. The Verizon updater forced 4.3 on me leaving me scrambling to figure out to to regain root access. I did manage to gain the root access (although, I'm not 100% sure how so) and once again, everything was fine.
I began using TitaniumBackup to starting removing some bloatware and moving system apps to the SD card. I decided that I had no use for the "Samsung Link" app and I removed it. Once I returned from the reboot, I noticed that the icon for the bootloader was on the screen indicating that it was unlocked. I the did a quick search and app file for the "EZ Unlock" app. I installed the file, ran the program, did and reset and DEAD. Nothing. I've sat at the PC for the better part of the last 24 hours, have read hundreds of posts and tried more methods than I care to count. So far nothing has worked.
I'm desperately hoping that I will be able to find my answers by reaching out to the community as I have no funds to send my phone anywhere and I am past the warranty period. You guys are probably my last hope. Thanks in advance to anyone who helps out. It means a lot.
Click to expand...
Click to collapse
I doubt you'll bore us here, after all we dwell in the minutiae and tiniest of details for fun. Hmm, from what I see you have a bootloader hard brick since you tried using EZ Unlock. TW 4.3 prevents downgrading the rom to pre-4.3, flashing an unlocked bootloader, and installing a custom recovery using 4.1.2 methods. Your best option will be to try the steps detailed in this bootloader/hardbrick thread by SpyroDazee.
buhohitr said:
Ok, Can you boot to Odin mode (dowload mode)?
Click to expand...
Click to collapse
No. Once I used EZ Unlock, I was bricked.
SlimSnoopOS said:
I doubt you'll bore us here, after all we dwell in the minutiae and tiniest of details for fun. Hmm, from what I see you have a bootloader hard brick since you tried using EZ Unlock. TW 4.3 prevents downgrading the rom to pre-4.3, flashing an unlocked bootloader, and installing a custom recovery using 4.1.2 methods. Your best option will be to try the steps detailed in this bootloader/hardbrick thread by SpyroDazee.
Click to expand...
Click to collapse
I've looked at this particular guide the most. Where I fail there is the post calls to use Win32diskimager with the unzipped debrick.bin. I cant get Win32 to recognize the file and get error code 5: need permission (or something like that) and I run the program in Admin mode.
The only file I've found so far that Win32 does actually write to my SD card is Debrick-i535.img. http://angelfirenetworks.servegame.com/XDA/S3 Debrick IMG_s/
And then I can seem to make that run either.
I also have bricked S3 different circumstances but still hard bricked. Nothing I've tried here on xda or anywhere else has worked. I'm going to try this http://www.ebay.com/itm/281217379767?ssPageName=STRK:MEWAX:IT&_trksid=p3984.m1423.l2649 . It is probably the cheapest and easiest way.
TwistedPoet said:
I've looked at this particular guide the most. Where I fail there is the post calls to use Win32diskimager with the unzipped debrick.bin. I cant get Win32 to recognize the file and get error code 5: need permission (or something like that) and I run the program in Admin mode.
The only file I've found so far that Win32 does actually write to my SD card is Debrick-i535.img. http://angelfirenetworks.servegame.com/XDA/S3 Debrick IMG_s/
And then I can seem to make that run either.
Click to expand...
Click to collapse
It usually takes a few tries to get it to work, but if you really can't then you can always send it in for a jtag repair.
Mobile tech videos will do it, and there's someone on eBay who will do it for $30. Not too expensive.
Sent from my SCH-I535 using Tapatalk 2
TwistedPoet said:
I've looked at this particular guide the most. Where I fail there is the post calls to use Win32diskimager with the unzipped debrick.bin. I cant get Win32 to recognize the file and get error code 5: need permission (or something like that) and I run the program in Admin mode.
The only file I've found so far that Win32 does actually write to my SD card is Debrick-i535.img.
And then I can seem to make that run either.
Click to expand...
Click to collapse
So I just downloaded the debrick.zip and Win32 program from my link onto my laptop. I saved the unzipped debrick folder onto my desktop and found the debrick.bin once I switched the "Files of type" to "." then I just wrote the debrick.bin to a 512 mb sdcard with no problems. I'm not going any further cuz I have no need for this though. Are you saying that Win32 doesn't find the bin file at all?
Edit: I just ran it again and it worked a second time. My backup laptop is a 2006ish (maybe older) with a very outdated version of Windows and my sdcard has been unused since 2008. I don't know what else to tell you but it worked surprisingly well for me.
SlimSnoopOS said:
So I just downloaded the debrick.zip and Win32 program from my link onto my laptop. I saved the unzipped debrick folder onto my desktop and found the debrick.bin once I switched the "Files of type" to "." then I just wrote the debrick.bin to a 512 mb sdcard with no problems. I'm not going any further cuz I have no need for this though. Are you saying that Win32 doesn't find the bin file at all?
Edit: I just ran it again and it worked a second time. My backup laptop is a 2006ish (maybe older) with a very outdated version of Windows and my sdcard has been unused since 2008. I don't know what else to tell you but it worked surprisingly well for me.
Click to expand...
Click to collapse
The Win32 program finds the debrick.bin file when I switch to "." as well. But when I click WRITE, I get an error message and the file doesnt't write to the sd card. I'm using a HP Windows 7 Pro (2009) and I have a 32gb, class 10 sd card. I will run it again to double check.
Follow Up: I figured out what I was doing wrong. I was attempting to pull the "bin" file through Win32 and should have been pulling the "zip" file instead. I was able to write the debrick.zip file onto my SD card but wasn't (on first attempt) able to load my phone. Are there any other steps I may have misunderstood or overlooked?
TwistedPoet said:
The Win32 program finds the debrick.bin file when I switch to "." as well. But when I click WRITE, I get an error message and the file doesnt't write to the sd card. I'm using a HP Windows 7 Pro (2009) and I have a 32gb, class 10 sd card. I will run it again to double check.
Click to expand...
Click to collapse
Have you tried formatting the sdcard and running the program again? Set it to Fat32. I'm thinking it may be the sdcard and not the program itself but I'm not certain.
SlimSnoopOS said:
Have you tried formatting the sdcard and running the program again? Set it to Fat32. I'm thinking it may be the sdcard and not the program itself but I'm not certain.
Click to expand...
Click to collapse
VICTORY!!!!!!! - I made several mistakes in getting to this point but i have successfully retrieved my phone from it's previous HardBrick status. The steps it took me to get to this point were, make sure the sd card is formatted (FAT32) and empty, unzip the debrick.zip file, run the Win32 program, select the unzipped debrick.bin file and upload it to the F drive, then click Write. So, more or less, exactly what the instructions told me to do. Sometimes, it's the simple things that we're most often missing or not understanding.
THANK YOU to everyone and especially SlimSnoopOS for talking me through it and SpyroDazee for making such a comprehensive guide to work with. (although, it's simplicity was too complex for me. ).
TwistedPoet said:
VICTORY!!!!!!! - I made several mistakes in getting to this point but i have successfully retrieved my phone from it's previous HardBrick status. The steps it took me to get to this point were, make sure the sd card is formatted (FAT32) and empty, unzip the debrick.zip file, run the Win32 program, select the unzipped debrick.bin file and upload it to the F drive, then click Write. So, more or less, exactly what the instructions told me to do. Sometimes, it's the simple things that we're most often missing or not understanding.
THANK YOU to everyone and especially SlimSnoopOS for talking me through it and SpyroDazee for making such a comprehensive guide to work with. (although, it's simplicity was too complex for me. ).
Click to expand...
Click to collapse
Haha I love the enthusiasm my friend! Great way to start the weekend! All it took was another perspective, it's all good. You are most definitely welcome.
Edit: and while I'm here, if you have any inquiries about TW 4.3 or want to read up on some info then here's our TW 4.3 discussion thread:
http://forum.xda-developers.com/showthread.php?t=2575661
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
Haha I love the enthusiasm my friend! Great way to start the weekend! All it took was another perspective, it's all good. You are most definitely welcome.
Edit: and while I'm here, if you have any inquiries about TW 4.3 or want to read up on some info then here's our TW 4.3 discussion thread:
http://forum.xda-developers.com/showthread.php?t=2575661
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I'm not turning away knowledge. I'm still very new to this and obviously have a hard time following directions. I was looking at the next steps on that guide and am all ready confused enough to not do anything yet.
What is your phone doing after you inserted your sdcard and what size card and class were they. If you got it to go into download mode or some call it Odin mode by pressing volume down, home button and power button then your off to a great start to bringing your phone back from the dead. If only it worked for mine
Where did you get the debrick.zip file? Every time I download the file it comes as debrick.img not a .zip
Always_Jonezen said:
What is your phone doing after you inserted your sdcard and what size card and class were they. If you got it to go into download mode or some call it Odin mode by pressing volume down, home button and power button then your off to a great start to bringing your phone back from the dead. If only it worked for mine
Where did you get the debrick.zip file? Every time I download the file it comes as debrick.img not a .zip
Click to expand...
Click to collapse
Edit: My SD Card is a 32gb class 10. Once I got Win32 to extract the file properly, I put the SD card back into the phone, put the battery in, and plugged phone into computer. Pushed the power button and the phone came back on.
When you go to download that file with Win32, change the file type to "." - then you'll be able to select the debrick.zip
All files were obtained here - http://forum.xda-developers.com/showthread.php?t=2581166
I hope that helps.
TwistedPoet;49543890. Edit: My SD Card is a 32gb class 10. Once I got Win32 to extract the file properly said:
http://forum.xda-developers.com/showthread.php?t=2581166[/url]
I hope that helps.
Click to expand...
Click to collapse
Thanks I hope it works too. Am I supposed to change the file type of the debrick.img to debrick. and or change the file type in win32
Always_Jonezen said:
Thanks I hope it works too. Am I supposed to change the file type of the debrick.img to debrick. and or change the file type in win32
Click to expand...
Click to collapse
They did exactly what I posted, which was: unzip the debrick.zip, open Win32 and change the file type to ".", find the unzipped debrick folder and select the debrick.bin, and write to the sdcard.
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
They did exactly what I posted, which was: unzip the debrick.zip, open Win32 and change the file type to ".", find the unzipped debrick folder and select the debrick.bin, and write to the sdcard.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
As stated earlier when I download the debrick file it downloads as debrick.img not a zip file am I missing something
Always_Jonezen said:
As stated earlier when I download the debrick file it downloads as debrick.img not a zip file am I missing something
Click to expand...
Click to collapse
Did you brick BEFORE 4.3? I hovered over this link in SpyroDazee's post: "Debrick if you bricked before 4.3 OTA" and that's the only one that would download as an IMG. Press "Debrick if you took the 4.3 OTA" and it will download as a zip.
Or change the browser that you're using. I downloaded it using Chrome on my MBP.
Sent from my SCH-I535 using Tapatalk 4
I did brick on 4.1.2 and I am using chrome as my default browser