Related
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
The other day I factory reset my Samsung Galaxy Tab 7.0 Plus without backing it up.
F*ck that smilie face.
Anyways, when I first turned it on after the reset I received an error message stating "The process com.android.phone has stopped unexpectadly. Please try again." This message comes up every time I power on my tab. I've tried fixing permissions with ROM Manager but both it and Superuser force close. I can no longer connect to any wifi, I know its the tab and not the router. I've tried open wifi at McDonalds, unlocked the wifi here and tried but still wouldn't connect, however my 360 connects to my home wifi just fine.
Before I reset the tab I know I deleted some stock apps like Browser and Samsung apps that came with it that I wasn't going to use and were taking up space, but that has been months ago and I haven't had any of these problems until I reset it.
When I rooted so I could try using ROM manager I used root.zip, and then downloaded the superuser.zip and installed both from my sd card, but I can't update the superuser binaries or grant superuser rights to any apps.
I'm not really sure what to do, my tablet is a mess. I was thinking just a clean install of 3.2 could fix most if not all issues but I can't find it anywhere online.
Any help is really appreciated.
I would flash a new rom, stock HC or ICS Austria doesn't matter.
Sent from my GT-P6200 using xda app-developers app
shane10588 said:
The other day I factory reset my Samsung Galaxy Tab 7.0 Plus without backing it up.
F*ck that smilie face.
Anyways, when I first turned it on after the reset I received an error message stating "The process com.android.phone has stopped unexpectadly. Please try again." This message comes up every time I power on my tab. I've tried fixing permissions with ROM Manager but both it and Superuser force close. I can no longer connect to any wifi, I know its the tab and not the router. I've tried open wifi at McDonalds, unlocked the wifi here and tried but still wouldn't connect, however my 360 connects to my home wifi just fine.
Before I reset the tab I know I deleted some stock apps like Browser and Samsung apps that came with it that I wasn't going to use and were taking up space, but that has been months ago and I haven't had any of these problems until I reset it.
When I rooted so I could try using ROM manager I used root.zip, and then downloaded the superuser.zip and installed both from my sd card, but I can't update the superuser binaries or grant superuser rights to any apps.
I'm not really sure what to do, my tablet is a mess. I was thinking just a clean install of 3.2 could fix most if not all issues but I can't find it anywhere online.
Any help is really appreciated.
Click to expand...
Click to collapse
ROM Manager will not work properly on the Galaxy Tab 7.0 Plus, 7.7, or any other device.
1_Flash CWM recovery for p6200
2_Full wipe
3_Flash rom stock samsung with odin.
The only way to fix this is to repartition your phone with a .pit file that has been designed not to use the the corrupted sectors of your internal storage.
IMPORTANT NOTE : Remove your SD Card and SIM CARD Please
Run ODIN IN ADMIN Mode
a) Now you have to repartition your tab plus
b) Download the following (Importantly the .pit file)
Pit.file p6200.zip
devid801 said:
ROM Manager will not work properly on the Galaxy Tab 7.0 Plus, 7.7, or any other device.
1_Flash CWM recovery for p6200
2_Full wipe
3_Flash rom stock samsung with odin.
The only way to fix this is to repartition your phone with a .pit file that has been designed not to use the the corrupted sectors of your internal storage.
IMPORTANT NOTE : Remove your SD Card and SIM CARD Please
Run ODIN IN ADMIN Mode
a) Now you have to repartition your tab plus
b) Download the following (Importantly the .pit file)
Pit.file p6200.zip
Click to expand...
Click to collapse
I'm going to try this tonight when I have some more free time, thank you very much for the detailed reply. Does this mean that I will lose some internal storage space if parts are corrupted?
shane10588 said:
I'm going to try this tonight when I have some more free time, thank you very much for the detailed reply. Does this mean that I will lose some internal storage space if parts are corrupted?
Click to expand...
Click to collapse
Yes, is correct. ....
Isn't that edited pit file repartitioning only needed if the tab has been bricked due to the "brick bug"...
I would suggest first just flash some stock firmware file (can be found for example on sammobile.com).
In case that doesn't work, then use the repartitioning.
Sent from my GT-P6210
miksumortti said:
Isn't that edited pit file repartitioning only needed if the tab has been bricked due to the "brick bug"...
I would suggest first just flash some stock firmware file (can be found for example on sammobile.com).
In case that doesn't work, then use the repartitioning.
Sent from my GT-P6210
Click to expand...
Click to collapse
I flashed a factory image of 3.2 with Odin and everything is perfect. I will be more careful from now on. Thanks all for the help.
Solved: stuck at "Firmware upgrade encountered an issue. Please select recovery mode
So you are stuck on the dreaded " Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" screen and there is nothing you can do to get your phone to start normally or even get to the download screen?
Fret not lads & ladies, I've already gone thru the pain and suffering and have come out new man, and I'll tell you how I did it. Also im starting all the way at linux/mac so everyones included.
First things first, you are going to have to get your computer ready with the right software for it to work.
You will need to make sure you get an original stock rom, make sure your source forwhere you download it is credible, this was my first mistake and why evidently I got myself into this mess.
I'm sure other roms might work that are modified for your device, but I suggest stock, and starting fresh just to make sure everything is up and running.
I am not responsible for your device, it may get bricked if done wrong.
Linux & Mac users first.
1. You will need to downloadable a program called Hiemdall, its a program similar to Odin3 (windows program).
2. You will need to extract the stock rom you downloaded earlier, I suggest to a folder in your desktop, wd will call it "folder1".
3. Now open up Hiemdall in root, (sudo Hiemdall-frontend for terminal) and then make sure device is on and stuck on the " Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" screen, plug it in, then press the utilities tab and detect. ($ Heimdall detect)(terminal users). Make sure you do all this fast because the tablets are kinda funny when they stay connected.
4. Now clickthe Utilities tab then the "save as..." button and save the destination for the .pit file in the same location as the extracted stock rom folder (folder1).
5. Next click the Flash tab, and click browse and locate your .pit file, the one you just downloaded. Next click add under Partition (files), and then change the partion name (On the left hand under patition details) to recovery and browse to the extracted folder (folder1) and click and add the recovery.img and press start.
Now if all went well your tablet will have restarted itself and you have seen the logo (Samsung). but the chances are it wont load past that screen, but thats ok because now you can get your device into download mode and re-flash the whole rom. Do this the same way you did the recovery.img, but make sure you add each new one to the correct name in the partitions details section.
Now if this didnt work, then dont worry you can still join the windows crew and do it hat way. Simple download a program called virtualbox and get a windows xp iso, thats up to you to figure out as I deal with open source only O.S
So aftr you do that just load up the virtualbox with windows xp and follow below. I found it a bit easier as well.
Windows users....
I found this way to be pretty simple and straight forward,
1. Download Odin 1.3 (1.85 wasn't working for me)
2. Download the clockworkrecoveryMod
3. Open up Odin and browse in the PDA section for the CWM you downloaded and add it, next plug in your device and the box should turn yellow on the top left.
4. Press start and let it finish and reboot your device and you should now be able to boot into CWM and re flash a rom, or if you were smart just restore from a previous backup and get all the apps and stuff back too.
I dont know why cwm worked but it did so no complaints, just make sure you go into cwm and backup your device and with titanium (google play app) before you start playing with the root.
I did this and it worked for me, so hopefully it did for you. Im sorry if it didnt but dont get down, j6st be patient and ask and someone will help.
The key is getting the recovery.img to flash on I believe and maybe the cwm has it built in the package, im sure someone can shed some light on it.
"Im tired, cranky and hungry, but I got my baby back, no not you hunny, my GT2...":beer:
JLloydMedia said:
So you are stuck on the dreaded " Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" screen and there is nothing you can do to get your phone to start normally or even get to the download screen?
Fret not lads & ladies, I've already gone thru the pain and suffering and have come out new man, and I'll tell you how I did it. Also im starting all the way at linux/mac so everyones included.
First things first, you are going to have to get your computer ready with the right software for it to work.
You will need to make sure you get an original stock rom, make sure your source forwhere you download it is credible, this was my first mistake and why evidently I got myself into this mess.
I'm sure other roms might work that are modified for your device, but I suggest stock, and starting fresh just to make sure everything is up and running.
I am not responsible for your device, it may get bricked if done wrong.
Linux & Mac users first.
1. You will need to downloadable a program called Hiemdall, its a program similar to Odin3 (windows program).
2. You will need to extract the stock rom you downloaded earlier, I suggest to a folder in your desktop, wd will call it "folder1".
3. Now open up Hiemdall in root, (sudo Hiemdall-frontend for terminal) and then make sure device is on and stuck on the " Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" screen, plug it in, then press the utilities tab and detect. ($ Heimdall detect)(terminal users). Make sure you do all this fast because the tablets are kinda funny when they stay connected.
4. Now clickthe Utilities tab then the "save as..." button and save the destination for the .pit file in the same location as the extracted stock rom folder (folder1).
5. Next click the Flash tab, and click browse and locate your .pit file, the one you just downloaded. Next click add under Partition (files), and then change the partion name (On the left hand under patition details) to recovery and browse to the extracted folder (folder1) and click and add the recovery.img and press start.
Now if all went well your tablet will have restarted itself and you have seen the logo (Samsung). but the chances are it wont load past that screen, but thats ok because now you can get your device into download mode and re-flash the whole rom. Do this the same way you did the recovery.img, but make sure you add each new one to the correct name in the partitions details section.
Now if this didnt work, then dont worry you can still join the windows crew and do it hat way. Simple download a program called virtualbox and get a windows xp iso, thats up to you to figure out as I deal with open source only O.S
So aftr you do that just load up the virtualbox with windows xp and follow below. I found it a bit easier as well.
Windows users....
I found this way to be pretty simple and straight forward,
1. Download Odin 1.3 (1.85 wasn't working for me)
2. Download the clockworkrecoveryMod
3. Open up Odin and browse in the PDA section for the CWM you downloaded and add it, next plug in your device and the box should turn yellow on the top left.
4. Press start and let it finish and reboot your device and you should now be able to boot into CWM and re flash a rom, or if you were smart just restore from a previous backup and get all the apps and stuff back too.
I dont know why cwm worked but it did so no complaints, just make sure you go into cwm and backup your device and with titanium (google play app) before you start playing with the root.
I did this and it worked for me, so hopefully it did for you. Im sorry if it didnt but dont get down, j6st be patient and ask and someone will help.
The key is getting the recovery.img to flash on I believe and maybe the cwm has it built in the package, im sure someone can shed some light on it.
"Im tired, cranky and hungry, but I got my baby back, no not you hunny, my GT2...":beer:
Click to expand...
Click to collapse
Hi. Tried your method and it worked on windows. I tried 2 different ODIN softwares before it worked. Thanks for your help and information.
can't enter download mode
thanks for the notes. i tried to update to 4.2.2 from 4.1.2. the upgrade was unsucessfull. now i did whatever u have told. now i got the recovery but i can't enter download mode. now the tab 2(p3100) is just restarting. please help me as soon as possible
JLloydMedia said:
So you are stuck on the dreaded " Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" screen and there is nothing you can do to get your phone to start normally or even get to the download screen?
Fret not lads & ladies, I've already gone thru the pain and suffering and have come out new man, and I'll tell you how I did it. Also im starting all the way at linux/mac so everyones included.
First things first, you are going to have to get your computer ready with the right software for it to work.
You will need to make sure you get an original stock rom, make sure your source forwhere you download it is credible, this was my first mistake and why evidently I got myself into this mess.
I'm sure other roms might work that are modified for your device, but I suggest stock, and starting fresh just to make sure everything is up and running.
I am not responsible for your device, it may get bricked if done wrong.
Linux & Mac users first.
1. You will need to downloadable a program called Hiemdall, its a program similar to Odin3 (windows program).
2. You will need to extract the stock rom you downloaded earlier, I suggest to a folder in your desktop, wd will call it "folder1".
3. Now open up Hiemdall in root, (sudo Hiemdall-frontend for terminal) and then make sure device is on and stuck on the " Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" screen, plug it in, then press the utilities tab and detect. ($ Heimdall detect)(terminal users). Make sure you do all this fast because the tablets are kinda funny when they stay connected.
4. Now clickthe Utilities tab then the "save as..." button and save the destination for the .pit file in the same location as the extracted stock rom folder (folder1).
5. Next click the Flash tab, and click browse and locate your .pit file, the one you just downloaded. Next click add under Partition (files), and then change the partion name (On the left hand under patition details) to recovery and browse to the extracted folder (folder1) and click and add the recovery.img and press start.
Now if all went well your tablet will have restarted itself and you have seen the logo (Samsung). but the chances are it wont load past that screen, but thats ok because now you can get your device into download mode and re-flash the whole rom. Do this the same way you did the recovery.img, but make sure you add each new one to the correct name in the partitions details section.
Now if this didnt work, then dont worry you can still join the windows crew and do it hat way. Simple download a program called virtualbox and get a windows xp iso, thats up to you to figure out as I deal with open source only O.S
So aftr you do that just load up the virtualbox with windows xp and follow below. I found it a bit easier as well.
Windows users....
I found this way to be pretty simple and straight forward,
1. Download Odin 1.3 (1.85 wasn't working for me)
2. Download the clockworkrecoveryMod
3. Open up Odin and browse in the PDA section for the CWM you downloaded and add it, next plug in your device and the box should turn yellow on the top left.
4. Press start and let it finish and reboot your device and you should now be able to boot into CWM and re flash a rom, or if you were smart just restore from a previous backup and get all the apps and stuff back too.
I dont know why cwm worked but it did so no complaints, just make sure you go into cwm and backup your device and with titanium (google play app) before you start playing with the root.
I did this and it worked for me, so hopefully it did for you. Im sorry if it didnt but dont get down, j6st be patient and ask and someone will help.
The key is getting the recovery.img to flash on I believe and maybe the cwm has it built in the package, im sure someone can shed some light on it.
"Im tired, cranky and hungry, but I got my baby back, no not you hunny, my GT2...":beer:
Click to expand...
Click to collapse
pls help..
I m faceting same problem on my galaxy tab 2 7.1 gtp3100..but my tab is not detecting by odin ..n tell me is
kies are necessary or not? pls help me..
shubham.butle said:
I m faceting same problem on my galaxy tab 2 7.1 gtp3100..but my tab is not detecting by odin ..n tell me is
kies are necessary or not? pls help me..
Click to expand...
Click to collapse
kies is not nesccearlly needed we need the usb drivers make sure you installed them and you are using stock samsung usb cable or else IT WON"T WORK !!!
shubham.butle said:
I m faceting same problem on my galaxy tab 2 7.1 gtp3100..but my tab is not detecting by odin ..n tell me is
kies are necessary or not? pls help me..
Click to expand...
Click to collapse
If you can reach to the CWM recovery mode: Download firmware in zip form, you can get it from the below link. if you have a zip file leave it.
After obtaining the firmware copy to your external sdcard using a card reader or any other method
In recovery mode select "Instal zip from sdcard" then select "choose zip from external sdcard" then select the copied firmware zip file from the list and wait for completion
After completion go back and select "wipe data/factory reset" and "wipe cache partition" reboot . it will take some time for reboot atleat 15min. it worked for me. hope it will work for you. good luck
http://forum.xda-developers.com/showthread.php?t=2054901
Thanx...
thanx.. @Jeevan I flashed cwm successfully..(I don't know how..!)n in ur link there are many roms ,when this problem was created my os was ICS..now tell me if I flash 4.2.2 directly..then it will create problem or not..n in 4.2.2 there are two files so which will better..thanx once again u saved me!!pls reply
shubham.butle said:
thanx.. @Jeevan I flashed cwm successfully..(I don't know how..!)n in ur link there are many roms ,when this problem was created my os was ICS..now tell me if I flash 4.2.2 directly..then it will create problem or not..n in 4.2.2 there are two files so which will better..thanx once again u saved me!!pls reply
Click to expand...
Click to collapse
You can choose any of the roms, deodexed will be better. And there won't be any problem flashing 4.2.2
You should install latest kies version
Sent from my GT-P3100 using xda premium
sukkukikku said:
You should install latest kies version
Sent from my GT-P3100 using xda premium
Click to expand...
Click to collapse
Thanx yr..bt today I just install stock rom 4.2.2,so no problem just tell me these stock roms are exactly original or change some thing I mean in future updates can I use normal method ie directly
update from tab?
---------- Post added at 02:05 AM ---------- Previous post was at 02:01 AM ----------
shubham.butle said:
Thanx yr..bt today I just install stock rom 4.2.2,so no problem just tell me these stock roms are exactly original or change some thing I mean in future updates can I use normal method ie directly
update from tab?
Click to expand...
Click to collapse
I update rom by cwm..
would you like to give me clear solution? i have same problem here with P3100, already tried many CWM but none of them fixed it, flashing directly through odin with this file (DBT-P3100XWDMI1-20140113101559) and still no luck. Any link to download correct CWM please... Thanks
Awesome post
Dears
please follow blindly in this post,
because i have tried to install , 4.2.2 Bg to my samsung tab 2, got error firmware upgrade issue, and now i followed the steps here. got installed on 4..2.2
who would required , please go for XDA instruction
realy awesome, life saver, :good:
ragujay said:
Dears
please follow blindly in this post,
because i have tried to install , 4.2.2 Bg to my samsung tab 2, got error firmware upgrade issue, and now i followed the steps here. got installed on 4..2.2
who would required , please go for XDA instruction
realy awesome, life saver, :good:
Click to expand...
Click to collapse
Hi! Do you still having the CWM and Odin 1.3?
Hi.. I was experiencing this problem. Then without even thinking deeply, I try google any solution regarding this matter without referring to this thread first. I found this guys solution as he said it is for all samsung model.
https://www.youtube.com/watch?v=Jfgq6bYfKLg
After done flashing, my tab giving a samsung logo and went off until now. I was unable to enter the recovery and download mode. I try to connect the tab with PC but it kept reconnecting repetitively although universal samsung usb driver has been installed. Any idea how to solve this?
Hi everyone I hope someone can help me resolving this problem I made myself...
I tried to install kitkat 4.4 on one old samsung S1 (the first galaxy model)
first I rooted the phone, and installed clockwork mod, and a *.zip that should contain kitkat 4.4 for the phone.
It all whent well in clockworkmod until I selected to install kitkat. It starts to install, but i get a droid with an red triangle and a exclimation mark, and then it reeboots
Is it somehow possible to reset the install and get it bak to normal? I have also the odin program. can I do something to get the phone working again?
sorry for no pics or video, but the forum didnt allow me before my 10th post..
go to youtube, search on user sixors1 and there is a video who is called cam00376. sorry for the inconvenience
thanks for reading
Haakons said:
Hi everyone I hope someone can help me resolving this problem I made myself...
I tried to install kitkat 4.4 on one old samsung S1 (the first galaxy model)
first I rooted the phone, and installed clockwork mod, and a *.zip that should contain kitkat 4.4 for the phone.
It all whent well in clockworkmod until I selected to install kitkat. It starts to install, but i get a droid with an red triangle and a exclimation mark, and then it reeboots
Is it somehow possible to reset the install and get it bak to normal? I have also the odin program. can I do something to get the phone working again?
sorry for no pics or video, but the forum didnt allow me before my 10th post..
go to youtube, search on user sixors1 and there is a video who is called cam00376. sorry for the inconvenience
thanks for reading
Click to expand...
Click to collapse
okay, listen. the first step is download the stock rom. in the link at the bottom of this post is a list of firmwares for i9000. choose the one from your region, and download it, (or i can give you a link to my firmware, its international, so it will almost certasinly work. you might have to unzip the downloaded file, but only once. inside should be a folder withe the firmware name. go into the folder, you shouild see
a bunch of files.
then go to odin, connect you phone in download mode,navigate to the folder with the firmware folders, then:
Click on “PDA” and select file with “CODE” in its name.
Click on “Phone” and select file with “MODEM” in its name. (Note: Ignore this step if you don’t able to find such file)
Click on “CSC” and select file with “CSC” in its name. (Note: Ignore this step if you don’t able to find such file)
Click on “PIT” and select “.pit” file. (Note: Ignore this step if you don’t able to find such file)
press start, and hopefully your phone will be back working again.
Firmware download link:
http://samsung-updates.com/device/?id=GT-I9000
press thanks if i helped!
Hi and thanks for your reply:good:
I was to download my stock file (region TEN), but i just came to something called rapid gator, and i entered wrong werificatin code, and was told that I have to wait one hour before trying again.. suppose thats a method for getting folks to pay for service. but why do samsung do such a thing?..
anyway, i would highly appreciate if you can send me the stock ROM
Now I was able to get the system up and runing again. I guess it has been changed since you been doing this.
I simply unzipped the package for my region and placed the zip file that was not going to unzip. When I placed this in Odin, at the pda button, it showed a *.md5 file. Set the phone in download mode, and it did the rest itself
But the reason I began doing this was that the phone dont read the sim card, and I was hoping for software malfunction, but I guess I wasnt that lucky.
Anyone who knows how I can get it to read the sim again?
Hi! I have been searching on the web for the Stock ROM to G930F, but the phone only installs the modem.bin file. Everything else throws a error on the phone, and in Odin. So i’ll tell you how this happened, And yes this might be a long story.
I wanted to use Samsung Health to check my puls.
I opened the app and it said that I couldn’t use this app because the phone was rooted. (I had rooted my phone in the past and downloaded a stock ROM to flash my phone with to start off clean)
And so I thought I’ll just fix it now, because I am on computer. So I flashed my device with TWRP and mounted the system and the data. I saved the build.prop file on my computer and changed the Knox Trigger Value to 0. When I flashed the file back after editing it, ADB said it couldn’t read the file. I thought “what the hell?”. I rebooted the device, plugged it off my computer and noticed something was odd. It began to bootloop, the start-up image when you power on the device. I got into Recovery and checked to see what was wrong. It said the Internal Storage was (0 MB) used. I was powering off the device, and it said “No OS installed!”. I tried flashing the stock ROM but it would only accept the modem.bin file. I was worried and didn’t know what I would do. Any help would be great!
Lipticon said:
Hi! I have been searching on the web for the Stock ROM to G930F, but the phone only installs the modem.bin file. Everything else throws a error on the phone, and in Odin. So i’ll tell you how this happened, And yes this might be a long story.
I wanted to use Samsung Health to check my puls.
I opened the app and it said that I couldn’t use this app because the phone was rooted. (I had rooted my phone in the past and downloaded a stock ROM to flash my phone with to start off clean)
And so I thought I’ll just fix it now, because I am on computer. So I flashed my device with TWRP and mounted the system and the data. I saved the build.prop file on my computer and changed the Knox Trigger Value to 0. When I flashed the file back after editing it, ADB said it couldn’t read the file. I thought “what the hell?”. I rebooted the device, plugged it off my computer and noticed something was odd. It began to bootloop, the start-up image when you power on the device. I got into Recovery and checked to see what was wrong. It said the Internal Storage was (0 MB) used. I was powering off the device, and it said “No OS installed!”. I tried flashing the stock ROM but it would only accept the modem.bin file. I was worried and didn’t know what I would do. Any help would be great!
Click to expand...
Click to collapse
Ok so you don't say what firmware you had and which one you want to flash., there are lots of firmware for the G930. You can download them from several places , sammobile, SamFirm Tool and updato.com.
Use the latest version of Odin if you want Oreo, preferably unbranded.
With regard to Samsung health, this app will not work on a rooted device, just like banking apps, network provider apps and any other app which hold personal info.
Lipticon said:
Hi! I have been searching on the web for the Stock ROM to G930F, but the phone only installs the modem.bin file. Everything else throws a error on the phone, and in Odin. So i’ll tell you how this happened, And yes this might be a long story.
I wanted to use Samsung Health to check my puls.
I opened the app and it said that I couldn’t use this app because the phone was rooted. (I had rooted my phone in the past and downloaded a stock ROM to flash my phone with to start off clean)
And so I thought I’ll just fix it now, because I am on computer. So I flashed my device with TWRP and mounted the system and the data. I saved the build.prop file on my computer and changed the Knox Trigger Value to 0. When I flashed the file back after editing it, ADB said it couldn’t read the file. I thought “what the hell?”. I rebooted the device, plugged it off my computer and noticed something was odd. It began to bootloop, the start-up image when you power on the device. I got into Recovery and checked to see what was wrong. It said the Internal Storage was (0 MB) used. I was powering off the device, and it said “No OS installed!”. I tried flashing the stock ROM but it would only accept the modem.bin file. I was worried and didn’t know what I would do. Any help would be great!
Click to expand...
Click to collapse
As @cooltt said use SamFirm tool (search it on google, it's here on xda) and download the latest firmware for your variant (ex. SM-G930F if you own the international S7 flat).
Flash with odin. Make sure you put all the files in the right tabs.
Let the phone boot completly (until the tutorial shows up, if you used the CSC file instead of the HOME_CSC one)
To be able to use SHealth you will need to edit the build.prop. To do so:
1) flash twrp
2) boot to twrp and wipe data (you will loose everything you have in the internal storage so make a backup)
3) Reboot to recovery (twrp menu > reboot > recovery)
4) Flash Magisk 18.1
5) Reboot to system and wait until the phone boots (it may take 5-10minutes)
6) Set up everything and go to play store. Download BuildProp Editor
7) Open BuildProp Editor and make sure you grant it superuser access in Magisk
8) Search for the property: ro.config.tima and set its value to: 0
9) reboot the phone and you should be good to go.
If you want OTAs you will need to 1) uninstall magisk and 2) wait until the next update is released and flash it with odin using the HOME_CSC file.That will revert the kernel to its original state (non-rooted), the recovery to the stock one and the system and binary status to Official (which will allow you to receive OTAs once again)
Sent from my SM-G930F using Tapatalk