Please note that this is only a thread on HOW-TO and not a central place on where you can get your firmwares. There's several websites like SamMobile that can help you getting them.
All the Heimdall's instructions will be at the second post.
1. Q/A's (Introduction)
" I'm afraid I'll break my phone/tablet... "
1. What is download mode?
It's a special mode where the partitions are flashed into your phone. It's functionning is simillar to how fastboot works with other devices. (Nexus/HTC) It's normaly accessible by pressing the three-way button combinaison (Power + Home + Vol-) at the same time when turning on your device.
Click to expand...
Click to collapse
2. What's Odin then?
Odin, in this case, (not the mythologic one) is a windows program, a proprietary software from Samsung to flash numerous partitions. (/system, /cache, kernel etc) It is generally only used when in download mode.
Click to expand...
Click to collapse
3. If we have Odin, then why we do need Heimdall?
Heimdall is a cross-platform open source program that uses the same type of communication protocol that Odin uses to communicate with Samsung devices. It's very useful if for example you're using something like Mac OS or Linux. (in which Odin can't work natively without using some sort of Windows implementation)
Click to expand...
Click to collapse
4. Why sometimes I need to have a PIT file when I flash with either of these programs?
A PIT (Partition information table) which it's name indicates, is a file where regroups all your device's partition information. (such as name, size, offset, etc) It is possible to modify it but NOT RECOMMENDED unless you know what you're doing.
Click to expand...
Click to collapse
2. Odin Instructions for Original Samsung Galaxy S and Samsung Galaxy S II "based" devices
" Considered once before the best of Android... "
Device examples:
Samsung Galaxy S (I9000)
Samsung Galaxy S II (I9100)
Samsung Galaxy Note (N7000)
Samsung Galaxy Player/S Wifi (All)
2.1 Odin Prerequistes:
When you need to flash using either Odin or Heimdall (with Windows), you need the USB drivers. You can use either kies or the standalone USB drivers. (I prefer the USB drivers because Kies is not what I would take for a first choice...)
- A working brain
- A working computer
- Samsung USB Drivers
- Odin3 v1.7
- A "pit" file (Only need for when you re-partition. It can be found in your device's respective forum)
- A stock samsung USB cable if possible (it seems to give better result than other USB cable bought on third party sellers.)
Note: It is recommended to plug the device in download mode before executing Odin so the computer will recognize it and do the final preparation for the first time you'll want to flash something.
2.2 Little Glossary:
Left side:
Re-Partition: Actually means what it means, it re-partitions your device according to the pit file you've given. It's only necessary when flashing back to fresh STOCK and doing it without any further objective will BRICK your device.
Auto-Reboot: Self-explanatory
F. Reset time: Don't know really what it is. (It looks like it can reset some counter)
Note: those 2 last boxes should always be checked
Dump: Not necessary..
Phone EFS Clear: You do not want to make this..
Phone Bootloader update: Not necessary unless you want to flash only the bootloaders. (you probably won't EVER touch this)
Right side:
PIT: Self explanatory once again, the file should normally come with a .pit extension.
PDA: Normally this is where your firmware (ROM along with kernel) will be flashed. It contains the "PDA" name in it as well as the .tar or the .tar.md5 extension.
PHONE: This is where the Modem (Baseband) will go. It will normally contain "MODEM" in it's name. Once again, it will come with the .tar.md5 extension.
CSC: File that contains information from a specific network operator. (to use some special feature) You won't probably use this case if you're locked into a particular network... It does contain "CSC" in it's name and it comes with the .tar.md5 extension.
2.3 Flashing Time:
When you have finished with installing your drivers and your device has been recognized in both "normal" mode and "download" mode, you can proceed with the flashing. Here you can find a picture of Odin actually running. (Can be useful if you want a landmark on what to expect)
1. Extract the Odin3 v1.7.exe file from the zip
2. Execute Odin3 v1.7.exe
3. Put your device in download mode. To do so, press vol- while pressing the power button. The result of this combination should be this.
Note: The image is a result for the OG SGS based devices, The SGS II based ones should come with this instead after you bypassed the warning there.
4. You should see a yellow rectangle with COM:xx and saying ready. It means that your device is ready to be flashed
5. Depending on what you're flashing, take it to the corresponding box (PDA: Roms/Firmwares, Kernels, Bootloaders) (Modem: Radio/Baseband) (CSC: Csc file)
6. When you're clear with this, be sure to check throughously that the files selected were intended for your device
7. If a .pit file was selected when trying to flash, ensure that re-partition at the left is UNCHECKED!!
Note: If you're flashing Stock (Original) Samsung firmware, you MUST check the box. Failing to do so will likely brick the device...
8. Press the flash button
9. It should go through the flashing, you should see the partitions that's being flashed into device during this time.
Note: DO NOT EVER unplug the cable as the result will probably be a pricey plastic brick in your hands now.
10. When everything is finished, the program should ouput that it's done with a green box and your device should reboot automatically.
2.4 Misc. Section:
While the Original Galaxy S isn't related, the Galaxy S II based devices have a flash counter regarding on how much time you flash while in download mode. It's count goes up everytime you flash something in this particular mode. When the number is higher than 0, you LOSE your waranty. Be Warned!!
That said, there are ways to fix those problem by either buying a USB jig, or using an app like Triangle Away made by Chainfire.
3. Odin Instructions for the Samsung Galaxy S III "based" devices
" Designed for humans is the new way to go... "
Device examples:
Samsung Galaxy S III (I9300)
Samsung Galaxy Note II (N7100)
Samsung Galaxy Note 10.1 (N8000)
Samsung Galaxy S III Mini (I8190)
Samsung Galaxy Camera (EK-GC100)
3.1 Odin Prerequistes:
When you need to flash using either Odin or Heimdall (with Windows), you need the USB drivers. You can use either kies or the standalone USB drivers. (I prefer the USB drivers because Kies is not what I would take for a first choice...)
- A working brain
- A working computer
- Samsung USB Drivers
- Odin V3.07
- The files you'll want to flash
- A "pit" file (Only need for when you re-partition. It can be found in your device's respective forum)
- A stock samsung USB cable if possible (it seems to give better result than other USB cable bought on third party sellers.)
Note: It is recommended to plug the device in download mode before executing Odin so the computer will recognize it and do the final preparation for the first time you'll want to flash something.
3.2 Little Glossary:
Left side:
Re-Partition: Actually means what it means, it re-partitions your device according to the pit file you've given. It's only necessary when flashing back to fresh STOCK and doing it without any further objective will BRICK your device.
Auto-Reboot: Self-explanatory
F. Reset time: Don't know really what it is. (It looks like it can reset a counter in older device...)
Note: those 2 last boxes should always be checked
Flash Lock: Not sure what this does
LED Control: This as well
Nand Erase All: You do not want to touch this...
Right side:
PIT: Self explanatory once again, the file should normally come with a .pit extension.
PDA: Normally this is where your firmware (ROM along with kernel) will be flashed. It contains the "PDA" name in it as well as the .tar or the .tar.md5 extension.
PHONE: This is where the Modem (Baseband) will go. It will normally contain "MODEM" in it's name. Once again, it will come with the .tar.md5 extension.
CSC: File that contains information from a specific network operator. (to use some special feature) You won't probably use this case if you're locked into a particular network... It does contain "CSC" in it's name and it comes with the .tar.md5 extension.
UMS: I'm not sure as what this section does, it is greyed out by defaut so it must have some sort of specific usage. (but not for us anyway..)
Bottom side:
Start: Self explanatory...
Reset: Reset all the values to Odin's default.
Exit: Self explanatory again...
3.3 Flashing Time:
When you have finished with installing your drivers and your device has been recognized in both "normal" mode and "download" mode, you can proceed with the flashing. Here you can find a picture of Odin actually running. (Can be useful if you want a landmark on what to expect)
1. Extract all the files from the from the Odin307.zip
2. Execute Odin3 v3.07.exe
3. Put your device into download mode. The result should be like this after you bypassed the warning there.
4. You should see a yellow rectangle with COM:xx and saying ready. It means that your device is ready to be flashed!
5. Depending on what you're flashing, take it to the corresponding box (PDA: Roms, Kernels, Bootloaders) (Modem: Radio/Baseband) (CSC: Csc file)
6. When you're clear with this, be sure to check throughously that the file is intended for your device
7. If a .pit file was selected when trying to flash, ensure that re-partition at the left is UNCHECKED!! (Unless if it's going back to the stock Samsung firmware)
8. Press the flash button
9. It should go through the flashing, you should see the partitions that's being flashed into device during this time.
Note: DO NOT EVER unplug the cable as the result will probably be a pricey plastic brick in your hands now.
10. When everything is finished, the program should ouput that it's done with a green box and your device should reboot automatically.
3.4 Misc. Section:
All the Galaxy S III based devices have a flash counter regarding on how much time you flash while in download mode. It's count goes up everytime you flash something in this particular mode. When the number is higher than 0, you LOSE your waranty. Be Warned!!
That said, there are ways to fix those problem by either buying a USB jig, or using an app like Triangle Away made by Chainfire.
However be careful with the newer Knox bootloaders that came with the newer 4.3 Touchwiz updates as there's NO way of resetting the counter AND/OR downgrading it.
4. Odin Instructions for the Samsung Galaxy S4 "based" devices
" With the increasing popularity comes more restrictions... "
Device examples:
Samsung Galaxy S4 (I9500)
Samsung Galaxy Note II (N9000)
Samsung Galaxy Note 10.1 2014 Edition (SM-P600)
Samsung Galaxy S4 Mini (I9190)
4.1 Odin Prerequistes:
When you need to flash using either Odin or Heimdall (with Windows), you need the USB drivers. You can use either kies or the standalone USB drivers. (I prefer the USB drivers because Kies is not what I would take for a first choice...)
- A working brain
- A working computer
- Samsung USB Drivers
- Odin V3.07
- The files you'll want to flash
- A "pit" file (Only need for when you re-partition. It can be found in your device's respective forum)
- A stock samsung USB cable if possible (it seems to give better result than other USB cable bought on third party sellers.)
Note: It is recommended to plug the device in download mode before executing Odin so the computer will recognize it and do the final preparation for the first time you'll want to flash something.
4.2 Little Glossary:
Left side:
Re-Partition: Actually means what it means, it re-partitions your device according to the pit file you've given. It's only necessary when flashing back to fresh STOCK and doing it without any further objective will BRICK your device.
Auto-Reboot: Self-explanatory
F. Reset time: Don't know really what it is. (It looks like it can reset a counter in older device...)
Note: those 2 last boxes should always be checked
Flash Lock: Not sure what this does
LED Control: This as well
Nand Erase All: You do not want to touch this...
Right side:
PIT: Self explanatory once again, the file should normally come with a .pit extension.
PDA: Normally this is where your firmware (ROM along with kernel) will be flashed. It contains the "PDA" name in it as well as the .tar or the .tar.md5 extension.
PHONE: This is where the Modem (Baseband) will go. It will normally contain "MODEM" in it's name. Once again, it will come with the .tar.md5 extension.
CSC: File that contains information from a specific network operator. (to use some special feature) You won't probably use this case if you're locked into a particular network... It does contain "CSC" in it's name and it comes with the .tar.md5 extension.
UMS: I'm not sure as what this section does, it is greyed out by defaut so it must have some sort of specific usage. (but not for us anyway..)
Bottom side:
Start: Self explanatory...
Reset: Reset all the values to Odin's default.
Exit: Self explanatory again...
4.3 Flashing Time:
When you have finished with installing your drivers and your device has been recognized in both "normal" mode and "download" mode, you can proceed with the flashing. Here you can find a picture of Odin actually running. (Can be useful if you want a landmark on what to expect)
1. Extract all the files from the from the Odin307.zip
2. Execute Odin3 v3.07.exe
3. Put your device into download mode. The result should be like this after you bypassed the warning there.
4. You should see a yellow rectangle with COM:xx and saying ready. It means that your device is ready to be flashed!
5. Depending on what you're flashing, take it to the corresponding box (PDA: Roms, Kernels, Bootloaders) (Modem: Radio/Baseband) (CSC: Csc file)
6. When you're clear with this, be sure to check throughously that the file is intended for your device
7. If a .pit file was selected when trying to flash, ensure that re-partition at the left is UNCHECKED!! (Unless if it's going back to the stock Samsung firmware)
8. Press the flash button
9. It should go through the flashing, you should see the partitions that's being flashed into device during this time.
Note: DO NOT EVER unplug the cable as the result will probably be a pricey plastic brick in your hands now.
10. When everything is finished, the program should ouput that it's done with a green box and your device should reboot automatically.
4.4 Misc. Section:
All the Galaxy S4 based devices have the Knox flash counter which is MORE PROACTIVE than the flash counter inside the GSII/GSIII based devices. Upon flashing something that has not been signed numerically by Samsung, the eFuse is burned off and there's NO possible way of reverting the counter back to 0. (because of an HARDWARE failure)
PROCEED AT YOUR OWN RISK!
5. Odin Instructions for the Samsung Galaxy ARMv6 "based" devices
" Underpowered, they're still fighting through the end... "
Device examples:
Samsung Galaxy Ace (S5830)
Samsung Galaxy Gio (S5660)
Samsung Galaxy Mini (S5570)
Samsung Galaxy Fit (S5670)
5.1 Odin Prerequistes:
When you need to flash using either Odin or Heimdall (with Windows), you need the USB drivers. You can use either kies or the standalone USB drivers. (I prefer the USB drivers because Kies is not what I would take for a first choice...)
- A working brain
- A working computer
- Samsung USB Drivers
- Odin Multi Downloader v4.42
- The files you'll want to flash
- An "ops" file (Only need for when you re-partition. It can be found in your device's respective forum)
- A stock samsung USB cable if possible (it seems to give better result than other USB cable bought on third party sellers.)
Note: It is recommended to plug the device in download mode before executing Odin so the computer will recognize it and do the final preparation for the first time you'll want to flash something.
5.2 Little Glossary:
Left side:
One Package: If you have a one package firmware, (one that has every partition regrouped into one) you may check this box and take your one package file from your computer.
Auto-Reboot: Self-explanatory
Protect OPS: Need further info on that one but looks like it protects the internal OPS file from inside the device if you use a OPS while while flashing something.
Reset time: Don't know really what it is. (it looks like it can restart odin after a set number of time after having initially pressed "start")
Note: those 3 last boxes should always be checked
DEBUG ONLY: Well it is what it says. There's no option you'll really use in this part so I won't describe it as it's not necessary.
Right side:
OPS: This serves as the equivalent of PIT for some devices, it has information for the partitions from your device. it comes with a .ops extension.
BOOT: Not sure what this box is. From what I see, this box isn't even used...
Phone: This is where the Modem (Baseband) will go. It will normally contain "MODEM" in it's name. Once again, it will come with the .tar.md5 extension.
PDA: Normally this is where your firmware (ROM along with kernel) will be flashed. It contains the "PDA" name in it as well as the .tar or the .tar.md5 extension.
CSC: File that contains information from a specific network operator. (to use some special feature) You won't probably use this case if you're locked into a particular network... It does contain "CSC" in it's name and it comes with the .tar.md5 extension.
EFS: This is the file that contains the most sensible information of your phone (IMEI, S/N, MAC addresses, etc...) it comes also with the .tar or .tar.md5 extension.
One Package: If you do happen to have a "One Package" file, you can use it to flash all it's contents into your device.
5.3 Flashing Time:
When you have finished with installing your drivers and your device has been recognized in both "normal" mode and "download" mode, you can proceed with the flashing. Here you can find a picture of Odin actually running. (Can be useful if you want a landmark on what to expect)
1. Extract all the files from the from the OdinMultiDownloaderv4.42.zip
2. Execute Odin Multi Downloader v4.42.exe
3. Put your device into download mode. The result should be something similar to this after you maybe had this beforehand.
4. You should see a yellow rectangle with COM:xx and saying ready. It means that your device is ready to be flashed!
5. Depending on what you're flashing, take it to the corresponding box (PDA: Roms, Kernels) (Modem: Radio/Baseband) (CSC: Csc file) (EFS: EFS file)
6. When you're clear with this, be sure to check throughously that the file is intended for your device
7. If a .opt file was selected when trying to flash, ensure that "Protect OPS" at the left is CHECKED!!
8. Press the flash button
9. It should go through the flashing, you should see the partitions that's being flashed into device during this time.
Note: DO NOT EVER unplug the cable as the result will probably be a pricey plastic brick in your hands now.
10. When everything is finished, the program should ouput that it's done with a green box and your device should reboot automatically.
5.4 Misc. Section:
I would need more information. If you could send some, it would be appreciated!
6. Heimdall Instructions
" At last, an alternative has been found... "
Heimdall should work at least with the following devices (I'll add more if necessary)
Samsung Galaxy S (I9000)
Samsung Galaxy S II (I9100)
Samsung Galaxy S III (I9300)
Samsung Galaxy S4 (I9505)
Samsung Galaxy Player (All)
6.1 Heimdall Prerequistes:
When you need to flash using either Odin or Heimdall (with Windows), you need the USB drivers. You can use either kies or the standalone USB drivers. (I prefer the USB drivers because Kies is not what I would take for a first choice...)
- A working brain
- A working computer
- Samsung USB Drivers (for Windows only)
- WinUSB drivers installed (From zadig.exe, once again Windows only)
- Udev rules set-up for your Samsung device (for Linux only)
- Heimdall's Official Webpage
- The files you'll want to flash
- An "pit" file (needed for Heimdall to actually flash on your device)
- A stock samsung USB cable if possible (it seems to give better result than other USB cable bought on third party sellers.)
6.2 Little Glossary:
Load Package Tab:
We won't really use it... Unless you have an Heimdall package but you should already know how to use it...
Flash Tab:
PIT: Self explanatory once again, the file should normally come with a .pit extension. Also you have to select it in order to be able to flash (unless you're using the terminal)
Re-Partition: Actually means what it means, it re-partitions your device according to the pit file you've given. It's only necessary to check it when flashing back to fresh STOCK and doing it without any further objective will BRICK your device.
Add: Pretty simple, Adding the partition you wanted to be flashed according to the "pit" file you've selected
Remove: Pretty simple once again, this time it's to remove the partition you've selected.
No reboot: Won't reboot after all the flashing has been done.
Resume: (use after "No reboot") This is only to continue the session of "flash" as of after you've flashed something with Heimdall and you decided to press "No reboot", Heimdall stops communication with your device and you would need then to reboot it back into "download" mode to get it back working again
Create Package Tab:
Won't really explain because it's not that "much" used so it won't be useful for the purpose of this thread
Utilities Tab:
Detect Device: Obvious but for debugging purposes it can be useful.
Close Pc Screen: This affects more older Samsung devices (like the original Galaxy S) that when something went wrong with a flashing this picture would get in when you turned on your device. This button fixes it.
Download Pit: Here you can grab the .pit file from your device and save it through your computer. (Useful if you do need one but can't find it anywhere or for specific debugging purposes)
Print Pit: Here you can see the content of the .pit file from either two places: From your device or from a pit file you have on your computer. The result will be displayed on the "Output" window.
Partitions:
IBL+PBL: Primary bootloader, you mess with it, your device is a plastic brick... (Normally it should be a file named boot.bin)
SBL: Same thing as IBL+PBL. (It should be a file named sbl.bin)
SBL2: Acts as a backup of the original SBL partition. I don't really know if this could boot up when the first SBL is borked up.
PARAM: It's a file that "controls" the bootloaders on the initial device's boot. (param.lfs)
CACHE: It's actually your cache partition (The older Samsung models would have a file named cache.rfs, newer Samsung models though should be something like cache.img)
EFS: This partition is very important because all the "sensitive" data of your device is there: S/N, IMEI, MAC addresses. (Older models: efs.rfs, Newer models: efs.img)
RECOVERY: That's the recovery partition, where your recovery will be at. It serves as a unused kernel partition for the original Galaxy S. (It should be something like recovery.img for newer devices)
FACTORYFS: This is where your OS (/system) is. (Older models: factoryfs.rfs, Newer models: factoryfs.img)
KERNEL: It is what it is basically. It's where your kernel will be flashed. (Older models would be zImage/boot.img/normalboot.img where's the newer models comes more with boot.img)
6.3 Flashing Time:
When you have finished with installing your drivers and your device has been recognized in both "normal" mode and "download" mode, you can proceed with the flashing. Here you can find a picture of Heimdall on the "Flash" tab actually running. (Can be useful if you want a landmark on what to expect)
1. Extract all the files from the from the Heimdall zip you download
2. Execute Heimdall-frontend.exe on Windows, the Heimdall executable on Mac OS or on your Linux terminal, type "heimdall-frontend"
3. Put your device into download mode.
4. Plug your device into your computer. If you go to the "Utilities" tab and press the "Detect Device" Button. If it has been detected, you can continue on.
5. Go on the "Flash" tab. From then, you need to take up a .pit file that has been saved into your computer.
6. After taking your .pit file, you'll need to add a partition. Then selecting the partition you'll need to flash from the dropdown menu.
7. Be sure to check carefully each partition so you know that each partition equals their file counterparts.
8. When that is done, depending on if you're going to stock or not, check the "Repartition" box.
9. After you've been SURE that ALL those check-ups have been made, press the "Start" button.
10. Let the program do it's things. Then when it's done, your device should reboot automatically and it's a SUCCESS!!
Note: DO NOT EVER unplug the cable as the result will probably be a pricey plastic brick in your hands now.
6.4 Misc. Section:
- Heimdall CAN'T possibly work with every device. You mostly have to test for yourself if Heimdall works for you.
- When you install your drivers from zadig.exe, it "overwrites" Odin drivers which will make your device unusable with Odin. It's kinda like a trade. If you want to use Odin, you can't use Heimdall and vice-versa.
- If you happen you have an "Odin" flashable package and you want to flash using Heimdall, you can remove the ".md5" extension from your file and then extract the ".tar" file contents, you should get each of the partitions that can be flashable via Heimdall.
7. Thanks
" The roots provided by them grew into this tree... "
Google
Samsung
@SamHaLeKe
@Benjamin Dobell
@Perseus71
@LuigiBull23
Reserved...
wow great tutorial iknow how hard to be a newbie coz i experienced of hard time flashing when i newly purchased sgs 4 .
btw ur the man, great effort! i know someday we will be crowded here because of this tutorial
keep up the good heart sir
Gonna subscribe and hit 5star.
it should be sticky thread too
Sent from my YP-G1 using xda premium
rockerblood said:
wow great tutorial iknow how hard to be a newbie coz i experienced of hard time flashing when i newly purchased sgs 4 .
btw ur the man, great effort! i know someday we will be crowded here because of this tutorial
keep up the good heart sir
Gonna subscribe and hit 5star.
it should be sticky thread too
Sent from my YP-G1 using xda premium
Click to expand...
Click to collapse
Well I think it should have been better to add it before but it's better now than never. Also I'll put all the pit files here tomorrow so if you want them when you'll flash, they will be there and you wont have to search around and around.
i think thats a good idea
keep up the good heart and work sir
Thanks for posting. I flashed TerraSilent kernel.
However, I still don't have root access. As I posted before, I cannot find a root method for 2.3.6 on the US Player 4, and this seems to still be the case (for whatever reason after flashing, About Phone now reports Android 2.3.5, but I know this is impossible, as I did not flash any ROM).
(Also, right before the TerraSilent boot logo comes up, the upper half of the display shows some lines for a split second. This is not an issue, just wondering why it is there.)
TheTehk17 said:
Thanks for posting. I flashed TerraSilent kernel.
However, I still don't have root access. As I posted before, I cannot find a root method for 2.3.6 on the US Player 4, and this seems to still be the case (for whatever reason after flashing, About Phone now reports Android 2.3.5, but I know this is impossible, as I did not flash any ROM).
(Also, right before the TerraSilent boot logo comes up, the upper half of the display shows some lines for a split second. This is not an issue, just wondering why it is there.)
Click to expand...
Click to collapse
But AFAIK, I never knew that the US player had 2.3.6. Anyway you can root with which ever GB root you can find as this kernel is insecure which means that you have a root shell by default.
zaclimon said:
But AFAIK, I never knew that the US player had 2.3.6. Anyway you can root with which ever GB root you can find as this kernel is insecure which means that you have a root shell by default.
Click to expand...
Click to collapse
Got mine rooted now, thanks. I'm used to rooting and contributing for/with devices like the Samsung Moment and other s3c6410-based devices so this stuff is all new to me.
Yep, mine shipped with 2.3.6. I might make a guide so that others in the same boat as me know what to do.
Hey I said earlier this week I would put some pit files, well it better now than never. Sorry for the delay. With school and ICS porting, I don't have really the time to do it. Anyway the pit are here now.
Posting this in a few places but I recommend you note in the OP that this will always be best accomplished using a STOCK Samsung usb cable. Depending on how close to "bricked" the device is it is very possible the device will not be recognized by the pc unless the stock cable is used. I think this little bit of information will be very helpful and may save a lot of heartache for some in the future.
Jiggity Janx said:
Posting this in a few places but I recommend you note in the OP that this will always be best accomplished using a STOCK Samsung usb cable. Depending on how close to "bricked" the device is it is very possible the device will not be recognized by the pc unless the stock cable is used. I think this little bit of information will be very helpful and may save a lot of heartache for some in the future.
Click to expand...
Click to collapse
Alright it's taking into note. Thanks!
Alright I was given the 4.0 with it running an ICS ROM. I was not familiar with Samsung devices and rooting, and in thinking it was like my DINC2, I put it into recovery and since then I have tried to read all the forums to get it to work and to put it back to a stock ROM....... I haven't found a solution, and I am not sure if I missed a step in a forum, but I can get the device into a different recovery with blue lettering and only a few select options, but as far as getting it to boot up with the actual ROM I have had 0 success on any of it.... Any help?????? P.M. me or I can give my email if it would help at all, or any help what so ever would be great. Thanks.
P.S. It is the US version if that was a question.
Brennon19968 said:
Alright I was given the 4.0 with it running an ICS ROM. I was not familiar with Samsung devices and rooting, and in thinking it was like my DINC2, I put it into recovery and since then I have tried to read all the forums to get it to work and to put it back to a stock ROM....... I haven't found a solution, and I am not sure if I missed a step in a forum, but I can get the device into a different recovery with blue lettering and only a few select options, but as far as getting it to boot up with the actual ROM I have had 0 success on any of it.... Any help?????? P.M. me or I can give my email if it would help at all, or any help what so ever would be great. Thanks.
P.S. It is the US version if that was a question.
Click to expand...
Click to collapse
Sorry for the late reply but try this:
http://forum.xda-developers.com/showthread.php?t=1531850
zaclimon said:
Sorry for the late reply but try this:
http://forum.xda-developers.com/showthread.php?t=1531850
Click to expand...
Click to collapse
Alright thank you. I will have to try it when I get home from the hospital visit.
Sent from my Incredible 2 using xda app-developers app
SGP YP-G70 International Heimdall Froyo Stock Rom with bootloaders
zaclimon said:
Heimdall Instructions
I generally prefer flashing with heimdall because it's better than odin (but less simple) and it's cross platform.
More information on Heimdall: http://forum.xda-developers.com/showthread.php?t=755265
3.1 Heimdall Prerequistes
- Samsung USB Drivers
- Heimdall
3.2 Flashing With Heimdall
3.2.1 Drivers installation (Windows)
These are a FIRST time installation only for the libusb drivers.
1. Extract the heimdall folder somewhere in your computer.
2. Go in the heimdall folder and then drivers. You should see a file named zadig.exe
3. Execute zadig.exe and then check list all devices
4. You should see a samsung device listed.
5. Install the drivers, you should have an error concerning certificate (It's NORMAL, install them anyway). You must do this in home screen and in download mode.
3.2.2 Flashing
6. When this is done, Open heimdall-frontend.exe,
7. Go in the flash section and take your .pit file according to your device.
8. Select the partitions you want to flash and take the file according to it.
9. Ensure that all the partitions you've selected are good.
10. Flash!!
11. Your device should reboot by itself and it should work!:good:
If you have more questions/suggestions, ask them in the thread and I will answer it as soon as I can.
4. Pit Files
Here's the pit files needed if you need to re-partition
4.0 Intl: 4.0 Intl Download
4.0 Us: 4.0 Us Download
4.0 Kor: 4.0 Kor Download
5.0 Intl: 5.0 Intl Download
5.0 Us: 5.0 Us Download
5.0 Kor: 5.0 Kor Download
Thanks:
Google: For such a good OS
Samsung: For making such good devices (and Odin )
Benjamin Dobell: For Heimdall
SamHaLeKe: For the USB drivers
All the uploaders of the pit files
Click to expand...
Click to collapse
Can anyone share the right file or files to flash SGP YP-G70 International (with physical home button) with Stock Froyo (or other ROM) wich inclues the bootloaders?
How should I proceed to flash it?
Despite all information we find here there is always some details we don't know how to handle. I followed the instructions with Odin and the result was: PASS (green) but SGP wont reboot or turn on. I always think there is some missed detail.
Please help me to have it working again so I will right a full restoring procedure from the begining (hard brick) until the end to help our brothers to recover their devices as well.
I thank you very much in advance
mrlightman said:
Can anyone share the right file or files to flash SGP YP-G70 International (with physical home button) with Stock Froyo (or other ROM) wich inclues the bootloaders?
How should I proceed to flash it?
Despite all information we find here there is always some details we don't know how to handle. I followed the instructions with Odin and the result was: PASS (green) but SGP wont reboot or turn on. I always think there is some missed detail.
Please help me to have it working again so I will right a full restoring procedure from the begining (hard brick) until the end to help our brothers to recover their devices as well.
I thank you very much in advance
Click to expand...
Click to collapse
Seems that you never tried with heimdall as I told you right? Also because your case is very rare, (you're the 1st or the 2nd with this particular hard brick case), I never really took the time to write down. Well first of all, is your device recognized by your computer outside of the download mode?
SGP 5.0 YP-G70 wont turn on
zaclimon said:
Seems that you never tried with heimdall as I told you right? Also because your case is very rare, (you're the 1st or the 2nd with this particular hard brick case), I never really took the time to write down. Well first of all, is your device recognized by your computer outside of the download mode?
Click to expand...
Click to collapse
I haven't tried yet cause I'm not sure how to do it. I was searching for ROMs to use in Heimdall and I found just the PIT file.
Can I use the exact same ROM I used to flash with Odin?
The device is recognized by PC just when I have it into download mode using Adam Outlers method (Unbrickable Resurrector)
mrlightman said:
I haven't tried yet cause I'm not sure how to do it. I was searching for ROMs to use in Heimdall and I found just the PIT file.
Can I use the exact same ROM I used to flash with Odin?
The device is recognized by PC just when I have it into download mode using Adam Outlers method (Unbrickable Resurrector)
Click to expand...
Click to collapse
Yeah you can use the same rom as what you used with odin. You can follow this thread instruction on how to. You may need to flash the bootloaders so here's the name of them
IPL+PBL: boot.bin
SBL: sbl.bin
PARAM: param.lfs
SGP 5.0 YP-G70 wont turn on
zaclimon said:
Yeah you can use the same rom as what you used with odin. You can follow this thread instruction on how to. You may need to flash the bootloaders so here's the name of them
IPL+PBL: boot.bin
SBL: sbl.bin
PARAM: param.lfs
Click to expand...
Click to collapse
Well I'm trying to do that. Heimdall requires a Pack and I'm trying to use the ROM (tar) files I used to flash with Odin. The matter is that Heimdall always says firmware.xls is missing from the package and maybe that the exact point wich drove me flaw (I dont know).
Can you please share with me the right package including the firmware to make me able to flash it?
I already have the PIT file and I remember that the SGP was using Froyo before all my mass (having it bricked). My SGP is 5.0 YP-G70 International with physical home button.
Related
=========================================================================================
=== Device: GT-P5100 (Galaxy Tab 2, 10.1", 3G model)
=== Description: Safe stock ODIN image, recovery and root
=== Packaged by: cheatman ( xda - http://forum.xda-developers.com/member.php?u=490310 )
=== Stock ROM version: P5100XWALD7
=== Build date: 07 June 2012
=========================================================================================
Disclaimer: I am not responsible and assume no liability on how this information is used. This package is provided "as is" without any warranty and does not guarantee any fitness for any purpose.
ONLY FOR GT-P5100 (3G model)!!! Do not flash on any other Galaxy Tab 2!!!
Download the ZIP (large, about 600MB) from here:
=> DOWNLOAD FROM HERE (HotFile)
How to use: Read the readme.txt file or this post here.
On to the safe stock restore process:
1. Make sure you have the Samsung device drivers installed before you begin. If you don't, install them from here:
- 64bit: http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x64.shtml
- 32bit: http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml
2. Make sure your tablet's battery is at least 30% charged up before you begin.
3. Make sure you have an external microSD inserted in the device, if you also plan on rooting afterwards. Nothing will be erased from the microSD, there is no need to worry about that.
4. Run procedure to flash back the stock ROM from Samsung (Ice Cream Sandwitch 4.0.3 - P5100XWALD7) from the folder "Step1-Stock". STOP HERE FOR PURE STOCK!!!
5. Run procedure to enable ClockworkMod recovery from the folder "Step2-Recovery". This step is OPTIONAL (only if you want a custom recovery). STOP HERE IF YOU DON'T WANT ROOT!!!
6. Run procedure to enable "root" access from the folder "Step3-Root".
7. Done! Enjoy! Profit!
===============================================================
========== Step 1 - Flashing Stock P5100XWALD7 ================
===============================================================
1. Download the file from the link above.
2. Shut down your tab.
3. Disconnect tab from USB and/or power cables.
4. Hold "Power+Volume UP" physical buttons on your tablet to initiate download mode.
5. Press "Volume DOWN" physical button on your tablet to confirm and enter ODIN mode.
6. On your PC, open "Odin3 v1.85.exe"
7. Press "PDA" button in ODIN and select the "PLATFORM_P5100XWALD7_482645_REV02_user_low_ship.tar.md5" file.
8. Press "PHONE" button and select the "MODEM_P5100XXLD7_REV_01_CL1128355.tar.md5" file.
9. Connect your tablet using a USB cable. In ODIN you should see the device "<added>" message appear. If you do not, there is a problem with the Samsung drivers installation.
10. Confirm that only the following options are checked in ODIN: "Auto Reboot", "F. Reset Time", "PDA", "PHONE". DO NOT CHECK RE-PARTITION!!! NEVER!!!
11. Click the big "Start" button and WAIT. Be patient!!! The process takes about 3-4 minutes but can take longer.
12. Do not power down the tablet while this takes place. Do not shut down your PC. Do not touch anything! Just wait! Get a coffee or something...
13. After full flash the tablet will reset automatically.
14. Congratulations you are now safely back to stock P5100XXALD6.
15. There is no need to flash the bootloader and CSC. Do so at your own risk.
===================================================================
========== Step 2 - Flashing ClockworkMod Recovery ================
===================================================================
1. Download the attached recovery file "p5100-recovery.tar.md5.zip" and extract it.
2. Shut down your tab.
3. Disconnect tab from USB and/or power cables.
4. Hold "Power+Volume UP" physical buttons on your tablet to initiate download mode.
5. Press "Volume DOWN" physical button on your tablet to confirm and enter ODIN mode.
6. On your PC, open "Odin3 v1.85.exe"
7. Press "PDA" button in ODIN and select the "p5100-recovery.tar.md5" file.
8. Connect your tablet using a USB cable. In ODIN you should see the device "<added>" message appear. If you do not, there is a problem with the Samsung drivers installation.
9. Confirm that only the following options are checked in ODIN: "Auto Reboot", "F. Reset Time", "PDA". DO NOT CHECK RE-PARTITION!!! NEVER!!!
10. Click the big "Start" button and wait a few seconds. Flashing recovery.img is super-fast!
11. After recovery flash, the tablet will reset automatically.
12. Congratulations you are now running recovery for your tablet.
13. Note: Internal SD is not working with this recovery, you must use external microSD cards to load up ZIPs.
14. You can also download and extract the kernel and flash it also on "PDA" if you want a rooted Kernel
=========================================================
========== Step 3 - Enabling root access ================
=========================================================
1. Download the attached file "CWM-root-P5100-v1.zip".
2. Copy the "CWM-root-P5100-v1.zip" file to the external microSD card.
3. Shut down your tab.
4. Insert the microSD in the tablet.
5. Hold "Power+Volume DOWN" physical buttons on your tablet to initiate recovery mode. It takes a while to start up recovery (10-15 seconds) so be patient. Try not to press too hard on the buttons as it does not help at all (takes same amount of time :-D)
6. Use the "Volume UP" and "Volume DOWN" buttons to navigate (select options) and the "Power" button to select. Don't HOLD the buttons, just press them (like a click or something).
7. Select the option to install ZIP from sdcard.
8. Navigate to where you copied the "CWM-root-P5100-v1.zip" file and select it.
9. Wait for the operation to complete.
10. Navigate back and select option to "Reboot system"
11. Congratulations you have a fresh stock ROM with CWM and root ready to go!
12. Enjoy
=======================================================================================
Thanks and greetings go to:
- Galaxian-Soup
- nycbjr
- All others who help and bring value to the XDA comunity!
Peace and have fun!
C.
Reserved!
Looking for mirrors. This is a very large file!
Thanks.
Ah damnit lol this was almost what i was looking for. I need the one for the wifi version.
Do you think the recovery would be the same? Thats the only part i really need lol.
Nvmind i see its all in one file lol
Recovery is in an independent folder, you don't flash the initial zip lol.
Anyway, the recovery and root steps should apply to p5110 as well.
Cheers,
C.
Thank you for all the hard work. I'm sure my Willy nilly ways will require me to use this
Sent from a note on fire in the middle of the sea
Hi,
I see that in your instructions for flashin stock do not use file "BOOTLOADER_P5100XXALD6_365113_REV02_user_low_ship. tar.md5" which is otherwise included in the package, does that mean that it did not necessarily use one?
When it is necessary to use that file?
Thanks.
Updating the bootloader is not required.
Playing with bootloaders is very risky and dangerous in general (can permanently brick tab).
Bootloader is responsible for the download mode. If you can access it and flash using odin, there is no need to mess with it. Upgrading it may result in a locked boot mode, meaning you can't flash custom stuff anymore.
I included only the required files and steps so you guys don't have to look for the right combination.
Peace,
C.
Thank you for the file sir oh sir.
Rapidshare mirror
Sized at 492.65MB, i recompressed the file using 7-zip to cut off the size a bit. It is below 500MB, meaning it's Dev Host friendly.
Code:
stock-safe-p5100-4.0.3-v1.zip 2E5566F2311BAD666A8CFD9674AEE0A5
stock-safe-p5100-4.0.3-v1.7z 946AAC1EDE408FFCA48BAF592AC3F92C
Step1-Stock
MODEM_P5100XXLD6_REV_01_CL1128355.tar.md5 07EFC235DC6989D50C9321076EDCDFC1
PLATFORM_P5100XXALD6_365113_REV02_user_low_ship.tar.md5 8186B1660ED2D4C1752336014ED047FD
Step2-Recovery
recovery.tar.md5 16AFDD2FEDBD8476521D9C144C823023
Step3-Root
CWM-root-P5100-v1 4D2E472F0C0A640F4170B9500F39FCAC
Can someone please confirm the hashs?
I rooted my Galaxy Tab 2 10.1 WiFi GT-P5110 using the manual and it works fine!
Thanks for the manual
Sent from my r00t3d GT- P5110 using XDA Premium App
Updated new version of the stock image.
Thanks for this find go to our friend "zi0m3k" (cheers, mate!)
C.
How did you capture the stock recovery from the device? I would like to do the same from my GT-P5113, but (of course) one has to flash CWM first to get access, and that overwrites the recovery.
Stock recovery comes with the stock ROM, so you need to overwrite it, not capture it.
But, to clarify the issue, you can root your device without a custom recovery. After you root, you can dump system images using the "dd" command.
Rooting using CWM zips is just more convenient and easier for everyone, it's not the only option, though. There was root before recovery...
C.
cheatman said:
Stock recovery comes with the stock ROM, so you need to overwrite it, not capture it.
But, to clarify the issue, you can root your device without a custom recovery. After you root, you can dump system images using the "dd" command.
Rooting using CWM zips is just more convenient and easier for everyone, it's not the only option, though. There was root before recovery...
C.
Click to expand...
Click to collapse
I know that the final goal is to overwrite the recovery to get the benefits of CWM (e.g.). But if you want to save the *stock* recovery first, you need to capture/dump it from the device somehow before flashing (correct me if my logic here is incorrect).
Also, yes, I know a good way to dump it is with "dd", but one needs root to do that (I tried for the hell of it, to see if there was non-root read access, but alas, no).
I think you have hit upon my question regarding root: did you root the tab without flashing CWM? If so that will allow "dd" to capture the stock recovery, yes. If you used CWM, that you overwrote the recovery, and you would not have been able to save the stock recovery in that case.
I have not found a rooting method for the GT-P5113 that does not involve flashing CWM, so I cannot figure out how to same my stock recovery, which I would like to do before flashing CWM (and thereby losing the stock recovery forever).
I obviously dumped the recovery before I flashed CWM, otherwise it wouldn't be stock.
If I get you right, you want to know the root exploit I used to root my p5100 to get suid and be able to copy the "su" binary. In fact, getting elevated rights on a linux system if you have direct access to it is not rocket science. However, because that's a lot to write, here is a more simple solution you can apply to get a stock recovery that I didn't have at the time:
1. Go to samfirmware.com and download a stock rom for your device.
2. Extract the .tar.md5 files and get the "recovery.img" out of them. Usually the "boot" and "platform" files have one inside.
I reckon all p51xx devices have the same recovery anyway, but it might not be the case.
C.
cheatman said:
I obviously dumped the recovery before I flashed CWM, otherwise it wouldn't be stock.
If I get you right, you want to know the root exploit I used to root my p5100 to get suid and be able to copy the "su" binary. In fact, getting elevated rights on a linux system if you have direct access to it is not rocket science. However, because that's a lot to write, here is a more simple solution you can apply to get a stock recovery that I didn't have at the time:
1. Go to samfirmware.com and download a stock rom for your device.
2. Extract the .tar.md5 files and get the "recovery.img" out of them. Usually the "boot" and "platform" files have one inside.
I reckon all p51xx devices have the same recovery anyway, but it might not be the case.
C.
Click to expand...
Click to collapse
Hi, yes, that's exactly right - I wanted to know how you got elevated rights in order to use dd for this.
I really want the recovery image from *my* stock tablet - not one off the net.
Could you private message me, if you are uncomfortable talking about it here. I am well-versed in Linux (I've done kernel development, I'm part of the Gentoo Linux dev team, etc.), so I am no stranger to Linux. I know there are exploits now and then, but they are not usually trivial. If you found a new one for the current kernel, then I'm impressed, and please do tell. If you found the exploit somewhere on the net, can you send me a link?
Thanks, Joe
Well, I must admit I actually took my time thinking whether I should actually write a reply :-D
However, my main concern is having to write a lot to explain stuff, but considering you are a kernel dev, this should be easy peasy. In short, I didn't force my way in, I just *convinced* the system to let me in. It's an inherent problem of Android, in fact:
1. Extracted the boot.img and unpacked it.
2. Replaced the adbd binary in the ramdisk with an unsecure one.
3. Repackaged and flashed using ODIN.
4. Used adb root to get into the system, the *regular* way. Once adbd lets
5. Installed su and superuser.apk.
There is no need to exploit the kernel if the system is inherently flawed when it comes to direct access (adb root exists). Any and all Android devices that use this layout (boot.img) can be rooted this way. Sorry to disappoint you about the exploit, but I am no *real* dev. I just know my way around :-D
PS: You can get the latest boot.img I did for this purpose here
Hope it helps with your recovery dump,
C.
cheatman said:
There is no need to exploit the kernel if the system is inherently flawed when it comes to direct access (adb root exists).
Click to expand...
Click to collapse
Very interesting - that was my missing piece of the puzzle - I had not realized one could replace the adbd. Makes sense. I will certainly give this all a try! I may be experienced with Linux, but I have a lot less background in android internals; learning quickly, though. In fact, my next project (when I get some time) is to try building the GT-P5113 ROM from source (and also some delving into AOSP). Being able to customize at the source level would be very cool.
LavaJoe said:
Very interesting - that was my missing piece of the puzzle - I had not realized one could replace the adbd. Makes sense. I will certainly give this all a try! I may be experienced with Linux, but I have a lot less background in android internals; learning quickly, though. In fact, my next project (when I get some time) is to try building the GT-P5113 ROM from source (and also some delving into AOSP). Being able to customize at the source level would be very cool.
Click to expand...
Click to collapse
I would be eternally grateful if you could post the stock rom for the 5113 (including stock recovery) if you can. I would settle for just the stock recovery in flashable form via odin etc.
A read through Samsung's kernel source reveals that the governors are already coded into the kernel (install voltage control and you can switch between governors and schedulers at will).
It looks like the set stock speed on the 10.1 5113 is 1008MHz.
Does anyone know how/where in the kernel overclocking is programmed?
The source also looks pretty comprehensive for the tablet and apparently is very similar to that of the 7" tab. I imagine it wouldn't be too hard for a veteran coder to fix this up for the 10" users.
I haven't coded in years and I'm not familiar enough with Android to do anything but attempt to compile the source from Samsung.
Hi,
Does this work on P5100XXLD6 ?
Android version 4.0.3
Thanks
Odin is the saviour tool for all Samsung devices. The method for flashing by Odin differs from device to device.
This thread will give step by step instructions on how to flash a stock rom from Odin on the GT-I8262/I8260 :
A. Download Odin tools from here Mod edit: Link removed.-Dev-Host links are no longer allowed on XDA.
B. Download the stock rom from*www.samfirmware.com
Setting up Odin :
1. Make sure you have installed the necessary drivers for this device.
The drivers can be installed from within KIES or seperately .
2. Run Odin as administrator.
*3. Setting up the files is divided in two types depending on the firmware type :
a. If the firmware is a multi package file, put the files in the corresponding sections.ie. CSC file in CSC section, PDA file in PDA section.
b. If the firmware is a single package, add the single file in the*PDA section.
4. Now that Odin is setup, put the phone in download mode.
To do that, power off the phone and press 'home+power+volume down' buttons together.
Keep the buttons pressed till Download mide appears.
5. Now that Odin and the phone are setup, connect the phone to the device. Odin will detect the device and show something like 'com port (1)'
6. Flash the device.
7. The flash will take 5 minutes for a full flash on average
8. When the flashing is complete, DO NOT remove the device until Odin shows ' PASS '.
9. The device will reboot. Remove the device, go to recovery mode and do a factory/data reset.
That's it. Happy flashing ..!!
The title of this thread should be
HOW TO FLASH STOCK FIRMWARE
Click to expand...
Click to collapse
Use odin GT-I8262 / I8260
tnx...bro..
qstar.inc said:
The title of this thread should be
Click to expand...
Click to collapse
Yeah ur right xD
Win 7 x86 in Mac OSX Virtual Box VM
Hi, I'm trying to run the Odin with a Windows 7 x86 VM over Mac OSX. The VM has 2GB of RAM and still given to be the message "Program too big to fit in memory.".
I got this message due I'm trying to execute the EXE file by CMD because when I tryed by double clicking a CMD window opened and closed without any action.
Is there a Mac OSX software like Odin?
Thanks.
thanks bro
Hi, i have some doubts about this process:
1) Does flashing stock fw removes TWRP custom recovery? I wannt to put I8260 completely in factory condition...
2) does flashing stock fw increments flash counter?
Thaxnx a lot friends!
vvaibhavv said:
Odin is the saviour tool for all Samsung devices. The method for flashing by Odin differs from device to device.
This thread will give step by step instructions on how to flash a stock rom from Odin on the GT-I8262/I8260 :
A. Download Odin tools from here :* http://d-h.st/hSj
B. Download the stock rom from*www.samfirmware.com
Setting up Odin :
1. Make sure you have installed the necessary drivers for this device.
The drivers can be installed from within KIES or seperately .
2. Run Odin as administrator.
*3. Setting up the files is divided in two types depending on the firmware type :
a. If the firmware is a multi package file, put the files in the corresponding sections.ie. CSC file in CSC section, PDA file in PDA section.
b. If the firmware is a single package, add the single file in the*PDA section.
4. Now that Odin is setup, put the phone in download mode.
To do that, power off the phone and press 'home+power+volume down' buttons together.
Keep the buttons pressed till Download mide appears.
5. Now that Odin and the phone are setup, connect the phone to the device. Odin will detect the device and show something like 'com port (1)'
6. Flash the device.
7. The flash will take 5 minutes for a full flash on average
8. When the flashing is complete, DO NOT remove the device until Odin shows ' PASS '.
9. The device will reboot. Remove the device, go to recovery mode and do a factory/data reset.
That's it. Happy flashing ..!!
Click to expand...
Click to collapse
Hey douche, got a link that doesn't go Str8 to porn?!
I have some questions regarding installing COSMIC ROM on galaxy core duos GT-I8262.
Is it necessary to flash Gapps.zip along with COSMIC. zip?
If Yes, which Gapps should I prefer?
I have Gapps.zip for Marshmallow version, shall I go with it? or else...
Sent from my Sparkle V using Tapatalk
My Samsung Galaxy Note Pro 12.2 WiFi (SM-P900) got soft bricked after following a rooting tutorial i found by googling How to root SM-P900. I think the problem was that i used a too old (or wrong) version of Odin, but im not sure. While i was flashing the auto-root through Odin the screen turn of. After that it showed the "firmware upgrade encountered an issue. please select recovery mode in kies and try again" standard Samsung Message. I tried to reinstall the firmware through kies but with no luck.
[SOLUTION]
1. First I downloaded the correct firmware, from Sammobile. In my case it was Nordic Contries, cause i live in Denmark. Pick the one that suite you!!
2. Then i booted my first NotePro to download mode. It took my some tries, to get it working. First hold the power button. When the "Firmware Upgrade Encountered An Issue..." message turns off, in the same second, release the power button, and now select all three (Power + Volume Down + HomeKey). (You have to release the power button and press it again to make it work (At least for me)
3. Now install the stock firmware and your tablet is now working again.
4. (Optional) If you want to root your device and it didn't work the first time. Make sure you use the same Odin as showed in the tutorial.
invalid ext4 image
madsthines said:
My Samsung Galaxy Note Pro 12.2 WiFi (SM-P900) got soft bricked after following a rooting tutorial i found by googling How to root SM-P900. I think the problem was that i used a too old (or wrong) version of Odin, but im not sure. While i was flashing the auto-root through Odin the screen turn of. After that it showed the "firmware upgrade encountered an issue. please select recovery mode in kies and try again" standard Samsung Message. I tried to reinstall the firmware through kies but with no luck.
[SOLUTION]
1. First I downloaded the correct firmware, from Sammobile. In my case it was Nordic Contries, cause i live in Denmark. Pick the one that suite you!!
2. Then i booted my first NotePro to download mode. It took my some tries, to get it working. First hold the power button. When the "Firmware Upgrade Encountered An Issue..." message turns off, in the same second, release the power button, and now select all three (Power + Volume Down + HomeKey). (You have to release the power button and press it again to make it work (At least for me)
3. Now install the stock firmware and your tablet is now working again.
4. (Optional) If you want to root your device and it didn't work the first time. Make sure you use the same Odin as showed in the tutorial.
Click to expand...
Click to collapse
i AM FACING A PROBLEM HERE, PLEASE HEALP!
First I have download "P905XXUANAE_P905OXXANA7_P905XXUANA7_HOME.tar. md5" for my Galaxy Note Pro 12.2 SM-P905. But unfortunately the file did not work for me and after all the long installation process odin says failed. and the last line on my device is
"ODIN : Invalid ext4 image"
so, after seeing that I thought the downloaded file ("P905XXUANAE_P905OXXANA7_P905XXUANA7_HOME.tar.md5 ") may be corrupted. then I download again another file from sammobile website for my note pro SM-P905 and that is "P905XXUANC3_P905BTUAND2_P905XXUANA7_HOME.tar. md5" but when tried to install by odin after long time same condition happen again. Odin says failed, and my device last line was Invalid ext4 image.
what is the problem?
how to flash SM-P905?
where is the exact proper flash file for my SM-P905?
Please Healp!!!
ornobohornish said:
i AM FACING A PROBLEM HERE, PLEASE HEALP!
First I have download "P905XXUANAE_P905OXXANA7_P905XXUANA7_HOME.tar. md5" for my Galaxy Note Pro 12.2 SM-P905. But unfortunately the file did not work for me and after all the long installation process odin says failed. and the last line on my device is
"ODIN : Invalid ext4 image"
so, after seeing that I thought the downloaded file ("P905XXUANAE_P905OXXANA7_P905XXUANA7_HOME.tar.md5 ") may be corrupted. then I download again another file from sammobile website for my note pro SM-P905 and that is "P905XXUANC3_P905BTUAND2_P905XXUANA7_HOME.tar. md5" but when tried to install by odin after long time same condition happen again. Odin says failed, and my device last line was Invalid ext4 image.
what is the problem?
how to flash SM-P905?
where is the exact proper flash file for my SM-P905?
Please Healp!!!
Click to expand...
Click to collapse
1. You may want to try using:
http://samsung-updates.com/
instead of samfirmware, if you're experiencing corrupted downloads from the latter (but it's not very probable... see pt 3)
2. At the moment I am testing new firmware revision, downloaded from samsung-updates: P905XXUAND1 for NEE region. It flashed fine. Also, for most of the time I have used P905XXUANC3 firmware for DBT region (Germany - even if I am not a German, I do not really care about csc stuff, and I got used to the fact that the newest firmwares were always released for DBT region first on my old "standard" Note 10.1). It was flashing fine, too.
3. The problem seems, however, lie not in the firmware, but in your hardware - or at least in the way it is handled by Odin or drivers. Note that *.tar.md5 archive contain md5 checksum concatenated to the very end of archive. When you're selected firmware file in Odin (in a PDA section), it probably took a longer while before the file appeared as selected - this is because meanwhile Odin is checking the checksum (and for that purpose, he has to read whole 1.5Gig file...). So: If Odin allowed you to flash the tar.md5 file - then it was NOT corrupted, otherwise it won't even be possible to start the process as of file wrong checksum!
4. THere is another possibility - that something bad happened to your pit section (it has been overwritten in result of flashing firmware for a wrong device) and your nand partition table is corrupted, which may probably result in an impossibility of flashing files or impossibility of mounting filesystems... I cannot help then, I have never faced such a problem in practice myself.
5. Pt 4, however, seems to be less possible than pt 3.
- Have you ever flashed any firmware with success?
- what do you mean by "long installation process"? A 10 minutes? An hour? Half-a-day?
- Have you been observing Odin while flashing? It's indicating which partition is being flashed atm - can you tell on which firmware part (system? hidden? cache?) did it fail?
- Try using different version of Odin (an older one, guess 3.07? not sure however - the one which has "PDA" section instead of a single-letter names)
- Try flashing from different PC
- use usb 2.0 port instead of 3.0 ones.
- try using different usb cable (I guess it'll may be the hardest thing to check because the cable seem to be quite unique )
Grateful to you...
esgie said:
1. You may want to try using:
http://samsung-updates.com/
instead of samfirmware, if you're experiencing corrupted downloads from the latter (but it's not very probable... see pt 3)
2. At the moment I am testing new firmware revision, downloaded from samsung-updates: P905XXUAND1 for NEE region. It flashed fine. Also, for most of the time I have used P905XXUANC3 firmware for DBT region (Germany - even if I am not a German, I do not really care about csc stuff, and I got used to the fact that the newest firmwares were always released for DBT region first on my old "standard" Note 10.1). It was flashing fine, too.
3. The problem seems, however, lie not in the firmware, but in your hardware - or at least in the way it is handled by Odin or drivers. Note that *.tar.md5 archive contain md5 checksum concatenated to the very end of archive. When you're selected firmware file in Odin (in a PDA section), it probably took a longer while before the file appeared as selected - this is because meanwhile Odin is checking the checksum (and for that purpose, he has to read whole 1.5Gig file...). So: If Odin allowed you to flash the tar.md5 file - then it was NOT corrupted, otherwise it won't even be possible to start the process as of file wrong checksum!
4. THere is another possibility - that something bad happened to your pit section (it has been overwritten in result of flashing firmware for a wrong device) and your nand partition table is corrupted, which may probably result in an impossibility of flashing files or impossibility of mounting filesystems... I cannot help then, I have never faced such a problem in practice myself.
5. Pt 4, however, seems to be less possible than pt 3.
- Have you ever flashed any firmware with success?
- what do you mean by "long installation process"? A 10 minutes? An hour? Half-a-day?
- Have you been observing Odin while flashing? It's indicating which partition is being flashed atm - can you tell on which firmware part (system? hidden? cache?) did it fail?
- Try using different version of Odin (an older one, guess 3.07? not sure however - the one which has "PDA" section instead of a single-letter names)
- Try flashing from different PC
- use usb 2.0 port instead of 3.0 ones.
- try using different usb cable (I guess it'll may be the hardest thing to check because the cable seem to be quite unique )
Click to expand...
Click to collapse
Dear Sir,
I am so surprised to see that somebody response me for the core of his heart! I am so pleased to realize that some body look at my problem very attentively! sir, thank you!
so,
** I have tried using different usb cable to flash
** I have tried both 3.9 or 3.7 odin
** I have tried different pc to flash
** I have used 2.0 or 3.0 both usb cable
** I have tried both kies3 or previous kies
** I am giving here the whole odin texts which
was shown
"<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P905XXUANC3_P905BTUAND2_P905XXUANA7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> sbl1.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> aboot.mbn
<ID:0/008> rpm.mbn
<ID:0/008> tz.mbn
<ID:0/008> sdi.mbn
<ID:0/008> NON-HLOS.bin
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img.ext4
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
<ID:0/008> Added!!"
** Long installation process means 5-7 minutes! (I think it is normal, sorry)
** yes, I have used all high end android devices and all was rooted, installed cwm recovery, custom room, so I have experience well on android I am not new to play with android operating system. even now I am also using Note 3 with Omega custom rom and working great.
** I am thinking may be the problem is about pit. and I don't know where I will find a .pit file for SM-P905. some how may be the pit of my note pro is corrupted. i don't know actually I am not a developer!
Here all you wanted to know!
Dear Sir please help me to make alive my Galaxy Note Pro!
Please!!!
screen shot!
after the failed flashing operation all the time my devices shows, i am giving a screen shot!
Downloaded 3 Firmware
Already I have downloaded 3 rom, (because I thought the firmware file was corrupted) but by studying your post I know now when ever odin accept any firmware that means the rom file is not corrupted! thanks!
P905XXUANAE_P905DBTANA6_DBT.zip
P905XXUANAE_P905OXXANA7_BTU.zip
P905XXUANC3_P905BTUAND2_BTU.zip
i have download this 3 files!
Ok, we shall try to flash firmware otherwise, using more advanced method.
Note that if ur knox isn't yet tripped - it WILL trip it, breaking your warranty (in this case it's better to send the device to service center - i suppose something's broken...). If it is tripped, you have nothing to lose...
1. Download:
http://www67.zippyshare.com/v/25492738/file.html
do not rename the file, it should be named recovery.img
2. Using this tool
http://forum.xda-developers.com/showthread.php?t=2446269
convert provided recovery.img to tar.md5 format
3. Flash it with odin (it should take a few sec to finish and it should succeed as recovery seems to flash ok on your device)
4. Enter recovery mode by holding power+home+vol up. Warning should appear about warranty and then custom recovery should appear on screen..
5. Using touch menu seek thru options and thru wipe menu format the system partition, as well as wipe/format data and cache (any errors?). Leave the device for a moment...
6. Simultanously, open one of 2+ gig tar.md5 firmwares (i recommend to choose one which you tried to flash with odin in your last trial) downloaded from sammobile with winrar or 7zip (if error about bad end of file appears ignore it) and extract system.img.ext4 somewhere...
7. Download simg2img from post #19
http://forum.xda-developers.com/showthread.php?t=2191930&page=2
and use it to convert sparse image extracted from firmware tar.md5 (system.img.ext4) to raw image (let's say output file is called system.img)
8. Copy system.img to root of empty micro sd card (fat32 or exfat formatted). Check if it has been copied correctly. Put the micro sd card into device. Reboot recovery once again
9. Advanced -> terminal/console -> use default directory ( / ), console window should open. Using simple onscreen keyboard input:
dd if=/external_sd/system.img of=/dev/block/mmcblk0p23
Be careful - if ur on P905 the last number should be "23", inputting otherwise may result in unrecoverable hard brick!!! Also, process may take a LONGER while, like 10 mins, its ok, even if there is no progress indicator. Youll know it finished when keyboard will show back again (any errors here??)
10. Reboot AGAIN to recovery, go to Mounts menu, tick system, data and cache (does tick within system work?)
11. Go to terminal as in pt 9, but this time enter:
restorecon -R /cache
restorecon -R /data
restorecon -R /system
(errors?)
12. Reboot into system and cross yer fingers
mismatch
esgie said:
Ok, we shall try to flash firmware otherwise, using more advanced method.
Note that if ur knox isn't yet tripped - it WILL trip it, breaking your warranty (in this case it's better to send the device to service center - i suppose something's broken...). If it is tripped, you have nothing to lose...
1. Download:
http://www67.zippyshare.com/v/25492738/file.html
do not rename the file, it should be named recovery.img
2. Using this tool
http://forum.xda-developers.com/showthread.php?t=2446269
convert provided recovery.img to tar.md5 format
3. Flash it with odin (it should take a few sec to finish and it should succeed as recovery seems to flash ok on your device)
4. Enter recovery mode by holding power+home+vol up. Warning should appear about warranty and then custom recovery should appear on screen..
5. Using touch menu seek thru options and thru wipe menu format the system partition, as well as wipe/format data and cache (any errors?). Leave the device for a moment...
6. Simultanously, open one of 2+ gig tar.md5 firmwares (i recommend to choose one which you tried to flash with odin in your last trial) downloaded from sammobile with winrar or 7zip (if error about bad end of file appears ignore it) and extract system.img.ext4 somewhere...
7. Download simg2img from post #19
http://forum.xda-developers.com/showthread.php?t=2191930&page=2
and use it to convert sparse image extracted from firmware tar.md5 (system.img.ext4) to raw image (let's say output file is called system.img)
8. Copy system.img to root of empty micro sd card (fat32 or exfat formatted). Check if it has been copied correctly. Put the micro sd card into device. Reboot recovery once again
9. Advanced -> terminal/console -> use default directory ( / ), console window should open. Using simple onscreen keyboard input:
dd if=/external_sd/system.img of=/dev/block/mmcblk0p23
Be careful - if ur on P905 the last number should be "23", inputting otherwise may result in unrecoverable hard brick!!! Also, process may take a LONGER while, like 10 mins, its ok, even if there is no progress indicator. Youll know it finished when keyboard will show back again (any errors here??)
10. Reboot AGAIN to recovery, go to Mounts menu, tick system, data and cache (does tick within system work?)
11. Go to terminal as in pt 9, but this time enter:
restorecon -R /cache
restorecon -R /data
restorecon -R /system
(errors?)
12. Reboot into system and cross yer fingers
Click to expand...
Click to collapse
according to your link there is no file, named "recovery.img" but the file name is "libwfdsm.so"
DAAAAMN wrong link copied.
Wait a sec, I'll upload it in a while. Until then, you may start doing steps 6-8.
EDIT:
Here u go
http://www47.zippyshare.com/v/40021725/file.html
PS: using above method (a similiar one, to be exact...), figured out on my own to be exact, I have managed to unroot and revert to fully-stock state my old Note10.1, which I was not able to flash straight via Odin at all because the port's been broken, so I was able to send it to service center without any worries (at least related to the possibility of detecting the customization by the service) The difference is that you are able to flash files via Odin - except the system - but also that my device was booting at the very beginning, and yours not. Neverthless, with appropriate modifications, it should work on P905 too - or at least explain what's the reason of your issues.
Don't want to worry you, but as of now i am considering physical NAND damage as the most possible cause of the issue... But that's a theory only. Good luck.
problem solved!
esgie said:
DAAAAMN wrong link copied.
Wait a sec, I'll upload it in a while. Until then, you may start doing steps 6-8.
EDIT:
Here u go
http://www47.zippyshare.com/v/40021725/file.html
PS: using above method (a similiar one, to be exact...), I managed to unroot and revert to fully-stock state my old Note10.1, which I was not really able to flash straight via Odin because the port's been broken. The difference is that you are able to flash files via Odin - except the system - but also that my device was booting at the very beginning, and yours not. Neverthless, with appropriate modifications, it should work on P905 too - or at least explain what's the reason of your issues.
Don't want to worry you, but as of now i am considering physical NAND damage as the most possible cause of the issue... But that's a theory only. Good luck.
Click to expand...
Click to collapse
my dear sir, don't know how but my note pro start up automatically. before some minutes on my display "unauthorized operation occur, please restart you device" was showing. so after pressing ok, device tried to restart but it was stuck on recovery mode. so i started my device manually. when I pressed reboot from recovery everything was fine and still now it is working properly!
I don't know is going gone on my device. but is a mystery for me!
one thing, after trying to fix my devices long time my note pro battery was empty and i could not able to charge because it was stuck on download mode. after searching i got a boot image.tar.md5 for SM-P905. and install that Samsung logo appear, and device started charging. and after charge a few, It was start up!
now when I am connecting it with my pc, kies says I need to update my device. but previously my device was updated the latest software. I am giving the screen shot!
what will I do now? just update via kies and star to operate my device normally?
ornobohornish said:
my dear sir, don't know how but my note pro start up automatically. before some minutes on my display "unauthorized operation occur, please restart you device" was showing. so after pressing ok, device tried to restart but it was stuck on recovery mode. so i started my device manually. when I pressed reboot from recovery everything was fine and still now it is working properly!
I don't know is going gone on my device. but is a mystery for me!
one thing, after trying to fix my devices long time my note pro battery was empty and i could not able to charge because it was stuck on download mode. after searching i got a boot image.tar.md5 for SM-P905. and install that Samsung logo appear, and device started charging. and after charge a few, It was start up!
now when I am connecting it with my pc, kies says I need to update my device. but previously my device was updated the latest software. I am giving the screen shot!
what will I do now? just update via kies and star to operate my device normally?
Click to expand...
Click to collapse
Did I understood well that after emptying the battery of the non-working device out and recharging it back again at least a little, the device started to work again? Seems like... eeee...? some voltage circulating through the mainboard was the cause?
Well, I bet it was faulty or somehow corrupted boot.img (as it was the only partition you have flashed between the time the device seemed damaged and time the device started to work again), but I am not sure what really happened.
As to the firmware update question: from the screenshot attached I can see that you are now running XXUNAE firmware. Proposed XXUNC3 is a newer one so in general it is recommended to do the update. However, we cannot be sure anyhow if your device will not react in a same way as before. However, current updates seems to be minor ones (they concentrate on security policies and not on features...) so my recommendation is to leave it alone, at least until some more important update...
ohh nooo! befor reading you reply I was tried to update my device by kies. but same thing happen here. stuck on Invalid ext4 image!
i am so tired
esgie said:
Did I understood well that after emptying the battery of the non-working device out and recharging it back again at least a little, the device started to work again? Seems like... eeee...? some voltage circulating through the mainboard was the cause?
Well, I bet it was faulty or somehow corrupted boot.img (as it was the only partition you have flashed between the time the device seemed damaged and time the device started to work again), but I am not sure what really happened.
As to the firmware update question: from the screenshot attached I can see that you are now running XXUNAE firmware. Proposed XXUNC3 is a newer one so in general it is recommended to do the update. However, we cannot be sure anyhow if your device will not react in a same way as before. However, current updates seems to be minor ones (they concentrate on security policies and not on features...) so my recommendation is to leave it alone, at least until some more important update...
Click to expand...
Click to collapse
emergency firmware recovery start on kies but also stuck on "invalid ext4 image" and my my pc says to go service center! giving two screen shot!
ornobohornish said:
emergency firmware recovery start on kies but also stuck on "invalid ext4 image" and my my pc says to go service center! giving two screen shot!
Click to expand...
Click to collapse
My recommendation: repeat the procedure Ive posted earlier. Well se what happens
It looks like some part of your nand may be physically corrupted... and unwriteable.
before closing my notebook I am just hit the "CF-Auto-Root-viennalte-viennaltexx-smp905.tar" and surprisingly saw after successfully install the root file by Odin, my device start-up again. but problem is "unfortunately Samsung keyboard stopped" sowing. so I have install google stock keyboard and without Samsung keyboard it is running properly. though it is now working properly without samsung keyboard but I am little bit unhappy with my new Note Pro, I have just purchased this 3-6-14 and to day 5-6-14. I can not even look at thish properly because after purchasing it is disturbing! many thanks dear sir!
now I will try again with your instruction!
can not find "simg2img"
esgie said:
Ok, we shall try to flash firmware otherwise, using more advanced method.
Note that if ur knox isn't yet tripped - it WILL trip it, breaking your warranty (in this case it's better to send the device to service center - i suppose something's broken...). If it is tripped, you have nothing to lose...
1. Download:
http://www67.zippyshare.com/v/25492738/file.html
do not rename the file, it should be named recovery.img
2. Using this tool
http://forum.xda-developers.com/showthread.php?t=2446269
convert provided recovery.img to tar.md5 format
3. Flash it with odin (it should take a few sec to finish and it should succeed as recovery seems to flash ok on your device)
4. Enter recovery mode by holding power+home+vol up. Warning should appear about warranty and then custom recovery should appear on screen..
5. Using touch menu seek thru options and thru wipe menu format the system partition, as well as wipe/format data and cache (any errors?). Leave the device for a moment...
6. Simultanously, open one of 2+ gig tar.md5 firmwares (i recommend to choose one which you tried to flash with odin in your last trial) downloaded from sammobile with winrar or 7zip (if error about bad end of file appears ignore it) and extract system.img.ext4 somewhere...
7. Download simg2img from post #19
http://forum.xda-developers.com/showthread.php?t=2191930&page=2
and use it to convert sparse image extracted from firmware tar.md5 (system.img.ext4) to raw image (let's say output file is called system.img)
8. Copy system.img to root of empty micro sd card (fat32 or exfat formatted). Check if it has been copied correctly. Put the micro sd card into device. Reboot recovery once again
9. Advanced -> terminal/console -> use default directory ( / ), console window should open. Using simple onscreen keyboard input:
dd if=/external_sd/system.img of=/dev/block/mmcblk0p23
Be careful - if ur on P905 the last number should be "23", inputting otherwise may result in unrecoverable hard brick!!! Also, process may take a LONGER while, like 10 mins, its ok, even if there is no progress indicator. Youll know it finished when keyboard will show back again (any errors here??)
10. Reboot AGAIN to recovery, go to Mounts menu, tick system, data and cache (does tick within system work?)
11. Go to terminal as in pt 9, but this time enter:
restorecon -R /cache
restorecon -R /data
restorecon -R /system
(errors?)
12. Reboot into system and cross yer fingers
Click to expand...
Click to collapse
dear sir,
in your link nowhere i found "simg2img"! I searched all the page number 9 but no where I found "simg2img"!!!
help please
---------- Post added at 10:28 AM ---------- Previous post was at 10:01 AM ----------
able to download simg2img from this link: http://web.djodjo.org/?a=download:android:tools:x86_linux:ext4tools
but how to use it to convert sparse image extracted from firmware tar.md5 (system.img.ext4) to raw image (let's say output file is called system.img)?
how to use simg2img?
Will this work with the SM-P900?
esgie said:
9. Advanced -> terminal/console -> use default directory ( / ), console window should open. Using simple onscreen keyboard input:
dd if=/external_sd/system.img of=/dev/block/mmcblk0p23
Be careful - if ur on P905 the last number should be "23", inputting otherwise may result in unrecoverable hard brick!
Click to expand...
Click to collapse
Hi Esgie.
I'm assuming that most of this would work for the SM-P900 (wifi only) version too? What would I use for the dd command in step 9?
Thanks for your help.
Jo Pop
ornobohornish said:
before closing my notebook I am just hit the "CF-Auto-Root-viennalte-viennaltexx-smp905.tar" and surprisingly saw after successfully install the root file by Odin, my device start-up again. but problem is "unfortunately Samsung keyboard stopped" sowing. so I have install google stock keyboard and without Samsung keyboard it is running properly. though it is now working properly without samsung keyboard but I am little bit unhappy with my new Note Pro, I have just purchased this 3-6-14 and to day 5-6-14. I can not even look at thish properly because after purchasing it is disturbing! many thanks dear sir!
now I will try again with your instruction!
Click to expand...
Click to collapse
I had same problem, install rom from greece. Some roms from sammobile and samsung firmware are giving errors, I have tested polish and british giving "odin: invalid ext4 image" error. After installing greece one everything works flawlessly, samsung keyboard also.
Greetings XDA-members !
I'm a total noob in flashing devices under Android..
I already (by the past) flashed many devices but no one under Android..
In fact I haven't the need for doing it..
BUT now, I'm really disturbed with intepestive reboot (due to some I/O errors in Internal Flash Storage)..
I know this can mean my devices is good for garbage throw.. BUT..
I want try something before.
So for that, I want root it !
Well, I want use this (it seems to me) clear tutorial: http://forum.xda-developers.com/showthread.php?t=1957165&highlight=cf+root
I have a Galaxy Tab 2 10.1'', all stock, never rooted, with no custom firmware, with Android JellyBean (not KitKat).
Code:
===Model Number:
GT-P5110
===Android version:
4.1.1
===Kernel version:
3.0.31-523998
[email protected] #1
SMP PREEMPT Thu Nov 22 22:04:16 KST 2012
===Version Number:
JRO03C.P5510XXCLK7
INFORMATIONS:
I must say that I never wiped the data or the cache.
Never format anything.
Never reinstalled the system.
I have already unlocked the USB Debug Mode on my Galaxy Tab 2
I haven't External SD Card (but I can buy one if required!)
Click to expand...
Click to collapse
This is the steps I want to do (please tell me if I'll be on the way to doing wrong steps, I don't want brick my devices..):
Create on my Windows a folder called : C:\SpecialAppDevelopers\AndroidFlasher_GalaxyTab2_ODIN
Downloading the file Odin3-v1.85.zip and store it to the path: C:\SpecialAppDevelopers\AndroidFlasher_GalaxyTab2_ODIN
Downloading the file CF-Auto-Root-espresso10wifi-espresso10wifixx-gtp5110.zip and store it to C:\SpecialAppDevelopers\AndroidFlasher_GalaxyTab2_ODIN
Unzip only 1 time the zip CF-Auto-Root-espresso10wifi-espresso10wifixx-gtp5110.zip, so now I end up with a CF-Auto-Root-*.tar.md5 file in the location: C:\SpecialAppDevelopers\AndroidFlasher_GalaxyTab2_ODIN
Unplug the Galaxy Tab 2 from my PC (if plugged in one USB slot)
Unzip only 1 time the zip Odin3-v1.85.zip, so now I end up with a Odin3-v1.85.exe file in the location: C:\SpecialAppDevelopers\AndroidFlasher_GalaxyTab2_ODIN
Run on my PC the exe file located here: C:\SpecialAppDevelopers\AndroidFlasher_GalaxyTab2_ODIN\Odin3-v1.85.exe
In the Odin3 window, I will click on a button which may think like a PDA, and then, a Window Explorer will occur, letting me choose a file
File I will choose to load is located here: C:\SpecialAppDevelopers\AndroidFlasher_GalaxyTab2_ODIN\CF-Auto-Root-*.tar.md5
Boot my Galaxy Tab 2 in DOWNLOAD Mode (this can do it like Recovery mode BUT this time by holding the Volume Down physical button instead of Volume Up).
When the Galaxy Tab 2 is in DOWNLOAD Mode I can plug it to my PC with USB.
If now I see the "Repartition" ticked, I untick this right now!
Next, on the Odin3 software Window, I click on the "START" button to flash with CF-Root
I wait some seconds (30 per example) and then my Galaxy Tab 2 should reboot Android
End.
Now, If you see one step which can be harmful for my Galaxy Tab 2, please tell me
For running commands as root, Will I be able to make this when in recovery mode (on a CommandLine interface through my PC):
Code:
adb devices
adb shell
su
** at this state, will I be able to acquire the root permissions?? So Will I can run any root command I want run?**
And for finish, three last question...
WILL using Odin + CF-Root cause incapacity to login to an existing Google Play account?
WILL using Odin + CF-Root cause crash or brick or other things like that when I update my Android Versions from Google Play ?
WILL using Odin + CF-Root cause wipe my datas OR NOT ?
THANKS if you answer me ! Really !
Seyokentai said:
Greetings XDA-members !
I'm a total noob in flashing devices under Android..
I already (by the past) flashed many devices but no one under Android..
In fact I haven't the need for doing it..
BUT now, I'm really disturbed with intepestive reboot (due to some I/O errors in Internal Flash Storage)..
I know this can mean my devices is good for garbage throw.. BUT..
I want try something before.
So for that, I want root it !
Well, I want use this (it seems to me) clear tutorial: http://forum.xda-developers.com/showthread.php?t=1957165&highlight=cf+root
I have a Galaxy Tab 2 10.1'', all stock, never rooted, with no custom firmware, with Android JellyBean (not KitKat).
Code:
===Model Number:
GT-P5110
===Android version:
4.1.1
===Kernel version:
3.0.31-523998
[email protected] #1
SMP PREEMPT Thu Nov 22 22:04:16 KST 2012
===Version Number:
JRO03C.P5510XXCLK7
INFORMATIONS:
This is the steps I want to do (please tell me if I'll be on the way to doing wrong steps, I don't want brick my devices..):
Create on my Windows a folder called : C:\SpecialAppDevelopers\AndroidFlasher_GalaxyTab2_ODIN
Downloading the file Odin3-v1.85.zip and store it to the path: C:\SpecialAppDevelopers\AndroidFlasher_GalaxyTab2_ODIN
Downloading the file CF-Auto-Root-espresso10wifi-espresso10wifixx-gtp5110.zip and store it to C:\SpecialAppDevelopers\AndroidFlasher_GalaxyTab2_ODIN
Unzip only 1 time the zip CF-Auto-Root-espresso10wifi-espresso10wifixx-gtp5110.zip, so now I end up with a CF-Auto-Root-*.tar.md5 file in the location: C:\SpecialAppDevelopers\AndroidFlasher_GalaxyTab2_ODIN
Unplug the Galaxy Tab 2 from my PC (if plugged in one USB slot)
Unzip only 1 time the zip Odin3-v1.85.zip, so now I end up with a Odin3-v1.85.exe file in the location: C:\SpecialAppDevelopers\AndroidFlasher_GalaxyTab2_ODIN
Run on my PC the exe file located here: C:\SpecialAppDevelopers\AndroidFlasher_GalaxyTab2_ODIN\Odin3-v1.85.exe
In the Odin3 window, I will click on a button which may think like a PDA, and then, a Window Explorer will occur, letting me choose a file
File I will choose to load is located here: C:\SpecialAppDevelopers\AndroidFlasher_GalaxyTab2_ODIN\CF-Auto-Root-*.tar.md5
Boot my Galaxy Tab 2 in DOWNLOAD Mode (this can do it like Recovery mode BUT this time by holding the Volume Down physical button instead of Volume Up).
When the Galaxy Tab 2 is in DOWNLOAD Mode I can plug it to my PC with USB.
If now I see the "Repartition" ticked, I untick this right now!
Next, on the Odin3 software Window, I click on the "START" button to flash with CF-Root
I wait some seconds (30 per example) and then my Galaxy Tab 2 should reboot Android
End.
Now, If you see one step which can be harmful for my Galaxy Tab 2, please tell me
For running commands as root, Will I be able to make this when in recovery mode (on a CommandLine interface through my PC):
Code:
adb devices
adb shell
su
** at this state, will I be able to acquire the root permissions?? So Will I can run any root command I want run?**
And for finish, three last question...
WILL using Odin + CF-Root cause incapacity to login to an existing Google Play account?
WILL using Odin + CF-Root cause crash or brick or other things like that when I update my Android Versions from Google Play ?
WILL using Odin + CF-Root cause wipe my datas OR NOT ?
THANKS if you answer me ! Really !
Click to expand...
Click to collapse
Your method should work, but you will still have stock recovery. Which won't let you flash anything. Following basically the same steps, use the files here: http://forum.xda-developers.com/showthread.php?t=2535083 and you'll have custom recovery so you can do whatever you want afterwards. I personally prefer TWRP, but this will get you started properly. If you want to try TWRP you can flash the zip after your done, here it is: http://forum.xda-developers.com/showthread.php?t=2548476
wolfclan68 said:
Your method should work, but you will still have stock recovery. Which won't let you flash anything. Following basically the same steps, use the files here: http://forum.xda-developers.com/showthread.php?t=2535083 and you'll have custom recovery so you can do whatever you want afterwards. I personally prefer TWRP, but this will get you started properly. If you want to try TWRP you can flash the zip after your done, here it is: http://forum.xda-developers.com/showthread.php?t=2548476
Click to expand...
Click to collapse
Hey, thanks for answer wolfclan68 !
I don't really understand clearly what are the steps in your given link.
Better explained on the CF-Root page.
You know, I want only be able to run root commands, I'm totally lost in all theses methods...
So... can you answer me in some steps (according to what I wrote on my first thread post) ?
Or at least explain some "points" through a better clearview?
Example:
1) Download "GT-P51XX_XXXX-SuperSU-1.94-BusyBox-1.21.1_universal.tar.zip" and extract it once (you need the *.tar.md5 inside)
> What are the differences betweens each version of recovery?
2) Flash the *.tar.md5 file as PDA
> How? Like the steps [mean: Use ODIN, be in recovery mode on my Galaxy Tab 2, and click on the PDA button in odin window, after selected the right .tar.md5 file ?] I described in my first post?
3) Make sure "Re-Partition" and "F. Reset Time" UNCHECKED,
> I know what is Re-Partition, but, what is F. Reset Time ??
Please answer me:
If I flash my devices in theses steps, will it auto-wipe my data ??? (meaning losing (by formatting) Game saves, Photos, Videos, Screenshots, Game data, Apps, SQLite datas of apps, Games Licenses obtained through third apps like AppGratis, 365 apps ?)
THANKS FOR ANSWERS !
Click to expand...
Click to collapse
There are YouTube videos...Google. .
Sent from my SCH-I545 using Tapatalk
decaturbob said:
There are YouTube videos...Google. .
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
And, this is why you can't simply answer to my questions?
Correct me if I'm wrong but.. We are on a specialized board oriented to flashing, pda, smartphone and development of the technology no?
This is why I prefer ask here instead on Youtube/Google which aren't specialized...
...
Hello!
Please please help me!!!!
My Problem:
After factory reset (even before) without any installation I have only 541MB from 639MB of Phone memory free, when I connect it to the PC.
SD Card memory is OK.
So I had always problems with installing for example Navigon or other programs, because the phone says alwas: Less memory, please add new memory.
So I want to root it, OR MAYBE THERE IS AN OTHER WAY TO EXENT THE MEMORY.
Because inside the phone, when I check the memory via android 5.1.1 there are more GB free.
But I cannot root it, because odin and kies cannot find the J700F Model.
So I trtied different drivers.
Please Please help, or give me some comment what I could try!!!
Best regards
Hook
There android 6.0.1 available for the j700f. If you google search... updato archives, on youre computer or laptop then type in j700f in the firmware search bar and the firmware will show up. Id try a fresh install of the firmware and see that helps. Id post a link but i havent reached 10 posts yet.. id try to update the firmware to 6.0.1 marshmallow and see if that fixes it.
Here you go ....
http://updato.com/firmware-archive-select-model?q=j700f
Thanks!!!
Ifibreakitwillyoufixit said:
There android 6.0.1 available for the j700f. If you google search... updato archives, on youre computer or laptop then type in j700f in the firmware search bar and the firmware will show up. Id try a fresh install of the firmware and see that helps. Id post a link but i havent reached 10 posts yet.. id try to update the firmware to 6.0.1 marshmallow and see if that fixes it.
Click to expand...
Click to collapse
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Many many Thnaks for helping!!!!!!!!
Yes, I read about it, but my Problem is that I also cannot use Odin.
See Post:
I have an really big problem with my phone: "SM-J700F"
I am not able to connect via odin or kies to this one.
But in windowes explorer (Win7 64bit) everything is visible.
In MTP Mode, Usb-Storage and PTP mode.
Also I can acess to the phone via the explorer.
But not with odin and/or Kies.
I tried to installit several times (Kies also Kies3)
Then I tried another win7 computer, but with same result.
The reason is, i wont to root the phone, because of low memory, even after reseting to factory.
I hope really a lot that there is an solution!!!!
--------
And additional Information:
When I connect my Samsung Galaxy S5 Neo, everything is working.
So I compared the used driver for both phone (S5 is OK), (J7 is not) in the device manager of windows.
So below you see the entries when the phone is connected:
S5 Neo - OK:
-Modem: Samsung Mobile USB Modem
-Samsung Android Phone: Samsung Android ADB Interface
-Tragbare Geräte: Galaxy S5 Neo (translated means: carryable device)
-USB Controller: Samsung Mobile USB Composite Device
Same with J700F - Not OK:
- Modem: entity is not existing ---> difference
-Samsung Android Phone: Samsung Android ADB Interface ---> is equal
-Tragbare Geräte: full_tangxun6572_we_I ---> different, is the Name whitch is visible in windows explorer
-USB Controller: USB Verbindungsgerät (translatet: USB Connection Device) ---> different (this Entity is already existing, even when no phone is connected)
So I tried to update exactly this driver with the downloaded one from Samsung. For this I had to use no compactible hardware.
When I select almost all INF driver, the right driver was visible during installation, but it could not start (code 10)
I think this is somehow the problem.
With the driver "USB Verbindungsgerät" on the windows side everything is OK. Copy to phone, explore,...
But I think that Kies and Odin don't find the acces point to the USB samsung device....the bridge to this device.
Maybe there is an possibility go give odin an additional command, where odin connect to the right port (_#0006) and HUB (_#0004) which I see in the USB Verbindungsgerät....
1. Usb debugging on
2. Oem Unlock enabled if its in dev settings,
3. Connect usb to phone and computer
4. Boot into download mode
5. Open odin
6. Select pda
7. Select the firmware file
8. Click start
9. Wait a little bit for the firmware to load
8. Firmware flashes
9. Profit
If the firmware fails to load in odin after 1 minute then you must decompress the zip file and extract the firmwares tar and then flash the tar instead of zip.
Not sure what happened to youre phone but it sounds more like at one time it was rooted and some system modifications have caused it to mess up things.. if you havent done any system modifications then its a strange bug..
In odin it will have a blue box up in the com area up at the top left of odin if its blue then you are connected. If its blue and file fails to load it must be decompressed and extracted so its just the tar file..
Look and see does even a blue box show in odin when youre connected?
Not working --- what is wrong?
Ifibreakitwillyoufixit said:
1. Usb debugging on
2. Oem Unlock enabled if its in dev settings,
3. Connect usb to phone and computer
4. Boot into download mode
5. Open odin
6. Select pda
7. Select the firmware file
8. Click start
9. Wait a little bit for the firmware to load
8. Firmware flashes
9. Profit
If the firmware fails to load in odin after 1 minute then you must decompress the zip file and extract the firmwares tar and then flash the tar instead of zip.
Not sure what happened to youre phone but it sounds more like at one time it was rooted and some system modifications have caused it to mess up things.. if you havent done any system modifications then its a strange bug..
In odin it will have a blue box up in the com area up at the top left of odin if its blue then you are connected. If its blue and file fails to load it must be decompressed and extracted so its just the tar file..
Look and see does even a blue box show in odin when youre connected?
Click to expand...
Click to collapse
Hi!
I tested it again (same prozedure on 2 computers)
1. Usb debugging on -> done!
2. Oem Unlock enabled if its in dev settings, -> done!
3. Connect usb to phone and computer -> done!
4. Boot into download mode -> done!
5. Open odin -> done!
The Problem is, that ODIN cannot find the phone.
There is nothing below "ID:COM" no entity!
So I cannot go forward.
I treid on 2 PCs. Same result.
But interesting ist that from windows I can acces to the phone.
But not via odin and Kies.
Maybe you can give me information whitch driver should be used in the device manager?
Interesting is that Samsung Galaxy S5 Neo is working with this procedure....
I am really sad, and I hope so much that you can help!!!
BR
Hook
ODIN Screenshot - not working
Hello!
Appended there is an screenshot of ODIN.
One of my S5 Neo - called S5 Neo.jpg -> Odin is working
Please Note:
The ID: 0/003 is the phone Samsung Galaxy S5 Neo.
One of my J700F - called J700F.jpg -> Odin is not working (connecting)
On the other computer I tried Odin3 v3.12 also.
I think maybe there is an driver Problem?
Whitch one I need for J700F.
I downloaded more times the Samsung Galaxy USB driver kit...
BR
Robert
Sorry, but in this tread I would like you to ask about the memory points.
Why I have so less memory in the J700F?
Is it normal?
Br
Robert
Can anybody support me
Hello
Is any possibility for helping?
BR
Robert
Some news?!
What I found out:
When I use *#0808#
There is SP selected and RNDIS+ACM+DM+ADB
Bit when I select MTP+ADB the other one is not deselected and I cannot continue?
Means with OK - no function and Reboot - no function (then both are selected....!)
Do you can support me here?
BR
Hook