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
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.
The following post is just a TESTED collection of tools and procedures that were found over at XDA forum or elsewhere on the Internet.
I do not take any credit for all those nice scripts and manuals - I just put them together for the young community of IdeaPad A2107A owners.
Below you will find methods of getting root and Clockwork Mod Recovery v 6.0.1.5 on IdeaPad A2107A (I own the -H version with dual SIM and ca. 4 GB of internal memory).
All processes were tested by me and are working well but obviously you are responsible for your actions.
My device runs on ICS 4.0.3, compilation A2107A-H_S341 and has a couple of European languages (tablet bought in Poland).
What you need is installed ADB drivers so the PC can "talk" to you tablet. You will find a lot of guides on the net - just make sure Windows device manager shows Android Device - Android ADB Interface or something close to that.
I also advise to enable USB debugging and allow installing applications from unknown sources - all in your tablet's settings.
Once you make sure you have done the above you're good to go.
So let's go!
Download this: http://www.mediafire.com/download.php?5o7dm16d430lwal (un7zip) and read as follows:
1 - Root
The method I chose is for patient people - the device will reboot 3 times during this process.
a) connect your tablet to the PC, open "1 - 4.03root" folder and run "root.bat"
b) just after you run the .bat the device will reboot and in the command prompt you will see "Press any key to continue . . ." - WAIT until the tablet boots up completely. When you see the lockcreen THEN hit a key in the command prompt.
c) the above will happen 2 more times - always WAIT for the tablet to boot completely.
This process will install Superuser and RootExplorer so find those apps and see if the root works.
2 - Backup the whole ROM that is on your device - will be useful with making the CWM recovery.img file.
For this you will need ca. 2GB of memory so I advise at least 4GB sdcard.
I also advise to go to the settings and in the memory tab set the "Default write disk" to "SD storage" - this makes the microSD the primary "sdcard" - makes things easier with backups etc.
ALSO in the settings set the screen to stay on for at least 10 minutes - this is how long it will take to do the full ROM dump - important to keep the script alive.
To avoid any issues turn the flight mode on so no new "data" is received by the device.
Once you're done open "2 - Backup" folder from my 7zip and copy the "gscript" folder to the root of your sdcard. Now install "GScriptLite.apk" and run it (needs root access!).
In the app hit the menu button and pick "Add Script" ->"Need SU?" must be checked -> "Load file" -> select "back_mt6575_a4_v2c.sh" -> save and click the script.
As I said - wait ca 10 minutes for the scrip to finish. Now you will have a nice backup in the SD - look for "backup_v2" folder - copy it to your PC.
3 -Mobileuncle - it's in the Google Play Store but you won't find it with our tablet - supposedly incompatible. Bull*hit!
Open "3 - Mobileuncle" folder, copy the apk to your device and install. We will come back to this later.
4 - How about the CWM? Yes!
Open "4 - CWM 6015" - you will find a PDF there - read the instructions. The subfolder "michfood" contanis all the scripts you need so you don't have to download anything else.
ATTENTION - the "recovery.img" used in this process is YOUR "recovery.img" that you dumped in step 2. So find your backup from step 2 and the original "recovery.img" from your ROM.
ATTENTION - our device is MT6575 so you pick nr 1 in the command prompt.
5 - Once you have the new "recovery.img" with CWM (it is actually smaller than the original file) copy it to the root of your sdcard.
Now open the Mobileuncle Tools you installed in step 3 and hit "Recovery Update".
There, at the very top of the screen you will see your new CWM recovery file - hit it and then confirm the update. It takes a second!
Now you will be asked to boot into recovery mode - go ahead, try it
If the tablet booted in CWM then you are all set!
REMEMBER - to go into the recovery mode while the device is OFF you need to:
1 - hold the power button for ca 3 seconds
2 - let it go and in the same moment press BOTH Vol + and Vol - buttons.
REMEMBER 2 - the CWM 6.0.1.5 makes backups in a bit different way than the old CWM - read here :http://forum.xda-developers.com/showthread.php?t=1846446
It also appears that the key to modding our tablet is the MT6575 processor - a lot of tools just need to support this processor, the device itself is not so important.
All the best.
Mike.
P.S.
A little film how it looks: http://www.youtube.com/watch?v=tM3Sdwf2i4M
------------------------------------------------- UPDATE 1 ---------------------------------------------------------
For those who are running the same compilation as I am (A2107A-H_S341):
- you can download my recovery file from here: http://www.mediafire.com/download.php?um372gh6ayf6t6w
To use it you need to do:
1 - Root
(optional backup with GScriptLite.apk)
2 - flash the recovery file with Mobileuncle
Be careful and make sure you have a backup if you want to try this file with another compilation.
Cheers.
------------------------------------------------- UPDATE 2 ---------------------------------------------------------
Tested (by user: manwithmanypiercings) USB drivers are in this post: http://forum.xda-developers.com/showpost.php?p=34651039&postcount=51
------------------------------------------------- UPDATE 3 ---------------------------------------------------------
I think there is even easier way than the one I originally posted above.
BUT I cannot be sure that it will work with all of you - the reason is that I made so many changes to my A2107A-H that I do not know whether this method works "just because it's universal" or because my tablet was tweaked far enough.
On the other hand when you consider it reasonably it looks like it's quite simple and there is no particular reason why it shouldn't work with a stock A2107A.
So...
What you need:
1 - this package: http://www.mediafire.com/download.php?fbuzi5xjofs7vgf
2 - PC running Windows 7 would be the best (7 gave me no problems at all - takes 1 minute to do it). I made it on Windows 8 as well but there is a lot more fuss to install the proper driver.
What you do:
1 - turn on USB Debugging on your tablet
2 - connect the tablet to your PC (if it's the 1st, some default drivers will install - that's ok)
3 - tap on the notifications area in the "Connect as" change to "MTP" - this is quite important !
4 - from the downloaded package run the "Flash_tool.exe"
- click "Scatter-loading" on the right and find "MT6575_Android_scatter_emmc.txt"
- in the list in the lower part of the window you MUST have the "PRELOADER" (super important) and "RECOVERY" ticked and leading to the correct files. The PRELOADER = "preloader_lenovo75_a2_ics.bin" (in the package) and the RECOVERY is the recovery file of your choice -> there are 3 in the package - pick the one you want. You can flash them over and over so if you don't like one then try the other.
5 - click "Download" above - you will see a prompt saying that not all images were loaded - that is fine - we only want to flash the RECOVERY - so click "Yes"
6 - now the Flash tool is waiting for the tablet - press "reset" on the back - Windows will recognize a new device (and WILL NOT find the driver unless you have done it before) - no worries, you have the correct driver.
7 - open Windows "Device manager" and locate the MT65..... unrecognised device -> update / install driver -> point Windows to "USB VCOM Driver" folder from the package and pick your system. My Windows 7 found the driver on the spot but asked to confirm the install - "insecure" driver - I obviously clicked "install anyway" and so should you.
8 - once the driver is loaded the Flash tool will flash the new recovery file - you will see some colour progress bars in the program - at the end you should see a green circle.
That is it. Unplug the tablet, press reset on the back and you can now enter the recovery mode.
FUN FACT: the "reset" button on the back is not really a reset button, it's more like physical cut off button to temporarily disconnect the battery.
I have the Lenovo A2107A under Vodafone's brand Vodafone Smart Tab II 7
It has Android version 4.0.4 and compilation: A2107A_A404_010_002_120913_VODA
Imanaged to root it and install CWM using this thread. But somehow I was not able to create the CWM modded recovery.img
I used the one provided here and it worked fine.
Thanks for this.
I can't connect tablet to PC
csns said:
The following post is just a TESTED collection of tools and procedures that were found over at XDA forum or elsewhere on the Internet.
I do not take any credit for all those nice scripts and manuals - I just put them together for the young community of IdeaPad A2107A owners.
Below you will find methods of getting root and Clockwork Mod Recovery v 6.0.1.5 on IdeaPad A2107A (I own the -H version with dual SIM and ca. 4 GB of internal memory).
All processes were tested by me and are working well but obviously you are responsible for you actions.
My device runs on ICS 4.0.3, compilation A2107A-H_S341 and has a couple of European languages (tablet bought in Poland).
What you need is installed ADB drivers so the PC can "talk" to you tablet. You will find a lot of guides on the net - just make sure Window device manager shows Android Device - Android ADB Interface or something close to that.
I also advise to enable USB debugging and allow installing applications from unknown sources - all in your tablet's settings.
Once you make sure you have done the above you're good to go.
So let's go!
Download this: http://www.mediafire.com/download.php?5o7dm16d430lwal (un7zip) and read as follows:
1 - Root
The method I chose is for patient people - the device will reboot 3 times during this process.
a) connect your tablet to the PC, open "1 - 4.03root" folder and run "root.bat"
b) just after you run the .bat the device will reboot and in the command prompt you will see "Press any key to continue . . ." - WAIT until the tablet boots up completely. When you see the lockcreen THEN hit a key in the command prompt.
c) the above will happen 2 more times - always WAIT for the tablet to boot completely.
This process will install Superuser and RootExplorer so find those apps and see if the root works.
2 - Backup the whole ROM that is on your device - will be useful with making the CWM recovery.img file.
For this you will need ca. 2GB of memory so I advise at least 4GB sdcard.
I also advise to go to the settings and in the memory tab set the "Default write disk" to "SD storage" - this makes the microSD the primary "sdcard" - makes things easier with backups etc.
ALSO in the settings set the screen to stay on for at least 10 minutes - this is how long it will take to do the full ROM dump - important to keep the script alive.
Once you're done open "2 - Backup" folder from my 7zip and copy the "gscript" folder to the root of your sdcard. Now install "GScriptLite.apk" and run it (needs root access!).
In the app hit the menu button and pick "Add Script" ->"Need SU?" must be checked -> "Load file" -> select "back_mt6575_a4_v2c.sh" -> save and click the script.
As I said - wait ca 10 minutes for the scrip to finish. Now you will have a nice backup in the SD - look for "backup_v2" folder - copy it to your PC.
3 -Mobileuncle - it's in the Google Play Store but you won't find it with our tablet - supposedly incompatible. Bull*hit!
Open "3 - Mobileuncle" folder, copy the apk to your device and install. We will come back to this later.
4 - How about the CWM? Yes!
Open "4 - CWM 6015" - you will find a PDF there - read the instructions. The subfolder "michfood" contanis all the scripts you need so you don't have to download anything else.
ATTENTION - the "recovery.img" used in this process is YOUR "recovery.img" that you dumped in step 2. So find your backup from step 2 and the original "recovery.img" from your ROM.
ATTENTION - our device is MT6575 so you pick nr 1 in the command prompt.
5 - Once you have the new "recovery.img" with CWM (it is actually smaller than the original file) copy it to the root of your sdcard.
Now open the Mobileuncle Tools you installed in step 3 and hit "Recovery Update".
There, at the very top of the screen you will see your new CWM recovery file - hit it and then confirm the update. It takes a second!
Now you will be asked to boot into recovery mode - go ahead, try it
If the tablet booted in CWM then you are all set!
REMEMBER - to go into the recovery mode while the device is OFF you need to:
1 - hold the power button for ca 3 seconds
2 - let it go and in the same moment press BOTH Vol + and Vol - buttons.
REMEMBER 2 - the CWM 6.0.1.5 makes backups in a bit different way than the old CWM - read here :http://forum.xda-developers.com/showthread.php?t=1846446
It also appears that the key to modding our tablet is the MT6575 processor - a lot of tools just need to support this processor, the device itself is not so important.
All the best.
Mike.
P.S.
A little film how it looks: http://www.youtube.com/watch?v=tM3Sdwf2i4M
------------------------------------------------- UPDATE 1 ---------------------------------------------------------
For those who are running the same compilation as I am (A2107A-H_S341):
- you can download my recovery file from here: http://www.mediafire.com/download.php?um372gh6ayf6t6w
To use it you need to do:
1 - Root
(optional backup with GScriptLite.apk)
2 - flash the recovery file with Mobileuncle
Be careful and make sure you have a backup if you want to try this file with another compilation.
Cheers.
Click to expand...
Click to collapse
csns thanks for your guide
Unfortunately I can't connect my tablet to pc in USB debbuging mode. I tried a lot of drivers from net but without success.. Pls let me know the right way to root my tablet.
optical99 said:
csns thanks for your guide
Unfortunately I can't connect my tablet to pc in USB debbuging mode. I tried a lot of drivers from net but without success.. Pls let me know the right way to root my tablet.
Click to expand...
Click to collapse
Hi there,
Try those drivers: http://www.mediafire.com/?vx2hyv7dpwlmeyy
They come from the current Android SDK but I am running a 64 bit system and I'm not sure if those drivers will work with 32 bit systems.
Fingers crossed!
I tried with yor recommend dirvers and with a lot of others and doesn't work. I have to unrecognised denices in Device Manager - A2107A-H and MTP.
I am very upset about Lenovo because their support doesn't exist.
optical99 said:
I tried with yor recommend dirvers and with a lot of others and doesn't work. I have to unrecognised denices in Device Manager - A2107A-H and MTP.
I am very upset about Lenovo because their support doesn't exist.
Click to expand...
Click to collapse
I had to use the PDANET from this link.
http://forum.xda-developers.com/showthread.php?t=1982334&page=6
Should be the first post.
Sent from my Samsung Galaxy Note running JellyBeer using Xparent ICS Blue Tapatalk 2
First of all, a ton of thanx to csns for posting this detailed procedure along with all required scripts and tools...
I have just one question...Which Modified ROM did you install as I see you have unlocked calling feature in the video you posted???
I asked because the MOD ROM by pemergency in the other thread is for the 16 GB and creates some issues in the device...But your's is 4 GB, as is mine...
Thanx in advance
makbro said:
First of all, a ton of thanx to csns for posting this detailed procedure along with all required scripts and tools...
I have just one question...Which Modified ROM did you install as I see you have unlocked calling feature in the video you posted???
I asked because the MOD ROM by pemergency in the other thread is for the 16 GB and creates some issues in the device...But your's is 4 GB, as is mine...
Thanx in advance
Click to expand...
Click to collapse
I'm glad you find my post useful.
As for the calling feature - it's not actually working
You see, to have the calling app (in other words "the phone" app) in the app drawer all you need to do is change one tiny value in framework-res.apk.
This value is telling the system weather the whole device is supposed to handle voice calls or not. I just tricked the system to make the Phone.apk visible but there is a lot more do be done in order to make a real call over the cellular network.
I've just had this tablet for a week and I didn't have much time to dig into this topic. Let's see what the weekend brings
Be patient, I think it's just a matter of time when someone posts a user friendly guide... Or search yourself and share what you find with the community.
Take care.
works fine
manwithmanypiercings
I have gained acces to tabled with PDAnet drivers...thanks a lot
csns
I followed all steps and installed CWM 6015. Very nice tutorial...I thought it's simpliest way...respect for your job
optical99 said:
manwithmanypiercings
I have gained acces to tabled with PDAnet drivers...thanks a lot
csns
I followed all steps and installed CWM 6015. Very nice tutorial...I thought it's simpliest way...respect for your job
Click to expand...
Click to collapse
Glad I could help by showing the link. Glad you got everything else taken care of.
This is an awesome post! Thak you very much.
Need help at step 4
csns said:
The following post is just a TESTED collection of tools and procedures that were found over at XDA forum or elsewhere on the Internet.
I do not take any credit for all those nice scripts and manuals - I just put them together for the young community of IdeaPad A2107A owners.
Below you will find methods of getting root and Clockwork Mod Recovery v 6.0.1.5 on IdeaPad A2107A (I own the -H version with dual SIM and ca. 4 GB of internal memory).
All processes were tested by me and are working well but obviously you are responsible for your actions.
My device runs on ICS 4.0.3, compilation A2107A-H_S341 and has a couple of European languages (tablet bought in Poland).
What you need is installed ADB drivers so the PC can "talk" to you tablet. You will find a lot of guides on the net - just make sure Windows device manager shows Android Device - Android ADB Interface or something close to that.
I also advise to enable USB debugging and allow installing applications from unknown sources - all in your tablet's settings.
Once you make sure you have done the above you're good to go.
So let's go!
Download this: http://www.mediafire.com/download.php?5o7dm16d430lwal (un7zip) and read as follows:
1 - Root
The method I chose is for patient people - the device will reboot 3 times during this process.
a) connect your tablet to the PC, open "1 - 4.03root" folder and run "root.bat"
b) just after you run the .bat the device will reboot and in the command prompt you will see "Press any key to continue . . ." - WAIT until the tablet boots up completely. When you see the lockcreen THEN hit a key in the command prompt.
c) the above will happen 2 more times - always WAIT for the tablet to boot completely.
This process will install Superuser and RootExplorer so find those apps and see if the root works.
2 - Backup the whole ROM that is on your device - will be useful with making the CWM recovery.img file.
For this you will need ca. 2GB of memory so I advise at least 4GB sdcard.
I also advise to go to the settings and in the memory tab set the "Default write disk" to "SD storage" - this makes the microSD the primary "sdcard" - makes things easier with backups etc.
ALSO in the settings set the screen to stay on for at least 10 minutes - this is how long it will take to do the full ROM dump - important to keep the script alive.
To avoid any issues turn the flight mode on so no new "data" is received by the device.
Once you're done open "2 - Backup" folder from my 7zip and copy the "gscript" folder to the root of your sdcard. Now install "GScriptLite.apk" and run it (needs root access!).
In the app hit the menu button and pick "Add Script" ->"Need SU?" must be checked -> "Load file" -> select "back_mt6575_a4_v2c.sh" -> save and click the script.
As I said - wait ca 10 minutes for the scrip to finish. Now you will have a nice backup in the SD - look for "backup_v2" folder - copy it to your PC.
3 -Mobileuncle - it's in the Google Play Store but you won't find it with our tablet - supposedly incompatible. Bull*hit!
Open "3 - Mobileuncle" folder, copy the apk to your device and install. We will come back to this later.
4 - How about the CWM? Yes!
Open "4 - CWM 6015" - you will find a PDF there - read the instructions. The subfolder "michfood" contanis all the scripts you need so you don't have to download anything else.
ATTENTION - the "recovery.img" used in this process is YOUR "recovery.img" that you dumped in step 2. So find your backup from step 2 and the original "recovery.img" from your ROM.
ATTENTION - our device is MT6575 so you pick nr 1 in the command prompt.
5 - Once you have the new "recovery.img" with CWM (it is actually smaller than the original file) copy it to the root of your sdcard.
Now open the Mobileuncle Tools you installed in step 3 and hit "Recovery Update".
There, at the very top of the screen you will see your new CWM recovery file - hit it and then confirm the update. It takes a second!
Now you will be asked to boot into recovery mode - go ahead, try it
If the tablet booted in CWM then you are all set!
REMEMBER - to go into the recovery mode while the device is OFF you need to:
1 - hold the power button for ca 3 seconds
2 - let it go and in the same moment press BOTH Vol + and Vol - buttons.
REMEMBER 2 - the CWM 6.0.1.5 makes backups in a bit different way than the old CWM - read here :http://forum.xda-developers.com/showthread.php?t=1846446
It also appears that the key to modding our tablet is the MT6575 processor - a lot of tools just need to support this processor, the device itself is not so important.
All the best.
Mike.
P.S.
A little film how it looks: http://www.youtube.com/watch?v=tM3Sdwf2i4M
------------------------------------------------- UPDATE 1 ---------------------------------------------------------
For those who are running the same compilation as I am (A2107A-H_S341):
- you can download my recovery file from here: http://www.mediafire.com/download.php?um372gh6ayf6t6w
To use it you need to do:
1 - Root
(optional backup with GScriptLite.apk)
2 - flash the recovery file with Mobileuncle
Be careful and make sure you have a backup if you want to try this file with another compilation.
Cheers.
------------------------------------------------- UPDATE 2 ---------------------------------------------------------
Tested (by user: manwithmanypiercings) USB drivers are in this post: http://forum.xda-developers.com/showpost.php?p=34651039&postcount=51
Click to expand...
Click to collapse
Hi csns,
Sorry to bother you but when I try drag and drop my original "recovery.img" to "cwmr 6015.bat" in the "michfood" folder, I get a warning message "System cannot find the specified file "C:\users\....\recovery.img" "recovery" and the bat script exits...I have tried the following:-
1. Copy the folder and file "michfood" and my original "recovery.img" file in all possible alternate locations of my PC including desktop as shown in the pdf tutorial in "michfood" folder.
2. The permissions for both folders is "Full Control" for all users.
3. Files not hdden or protected.
4. Also turned off my antivirus and firewall.
No luck....Please help !!! Thanx in advance
makbro said:
Hi csns,
Sorry to bother you but when I try drag and drop my original "recovery.img" to "cwmr 6015.bat" in the "michfood" folder, I get a warning message "System cannot find the specified file "C:\users\....\recovery.img" "recovery" and the bat script exits...I have tried the following:-
1. Copy the folder and file "michfood" and my original "recovery.img" file in all possible alternate locations of my PC including desktop as shown in the pdf tutorial in "michfood" folder.
2. The permissions for both folders is "Full Control" for all users.
3. Files not hdden or protected.
4. Also turned off my antivirus and firewall.
No luck....Please help !!! Thanx in advance
Click to expand...
Click to collapse
Well, this happened to me once and I think the reason was that the path was too long - I guess it may have something to do with the fact that the .bat is a simple "program" and can have some problems with handling long paths.. specially with "national" character in them.
Try finding a location as close to the root of the drive as possible, and make sure you have full R/W access. Or try with a pendrive for example.
Since you made a backup of your ROM I think you are quite safe with using the recovery I uploaded - first post -> UPDATE 1.
They seem to fit all 2107A devices. If not I will tell you how to restore the original recovery from your backup.
You can also read UPDATE 3 I just made - your choice.
Thanx
Hello csns,
Thanx to your help, I have also got CWM recovery working on my device.
BTW I saw these two posts on a forum in Russian (I guess)...I used google translate and am pretty sure these two posts that I provide links for below have two modified ROMs with everything working, including phone and radio !!! The only draw back is that once you flash these ROMs you'll get Russian language, which can be changed to English from the language menu
I plan to fo it myself as well tomorrow,would let you know the outcome
http://4pda.ru/forum/index.php?showtopic=286687&st=920 (go down to the post labelled "A2107_Foxtrot_v100")
and
http://4pda.ru/forum/index.php?showtopic=286687&st=440 (go down to the post labelled "Прошивка Tasemart
MOD 1.1")
and of course you can also try the "Angeleas_Final" modified ROM also that I'll upload and provide links to tomorrow
Thanx again for all your help !!!
I also had many trouble getting the cwm bat file to work. It is very picky about its path and arguments on Win7.
I moved the michfood folder to C: and moved my own recovery.img to C:\michfood\recovery.old
cd C:\michfood
cwmr\ 6015.bat recovery.old
That worked - otherwise it wouldnt finish the cpio stuff.
Reworking that horrible script to work on linux would have probably taken less time -_-
Anyway - thanks!
Permissions problems on Windows7
Hi,
I Had the same problem.
makbro said:
Hi csns,
Sorry to bother you but when I try drag and drop my original "recovery.img" to "cwmr 6015.bat" in the "michfood" folder, I get a warning message "System cannot find the specified file "C:\users\....\recovery.img" "recovery" and the bat script exits...I have tried the following:-
1. Copy the folder and file "michfood" and my original "recovery.img" file in all possible alternate locations of my PC including desktop as shown in the pdf tutorial in "michfood" folder.
2. The permissions for both folders is "Full Control" for all users.
Click to expand...
Click to collapse
My solution:
It was required to use a directory not to deep in folder structures, so the best is as short as possible like "C:\michfood".
I had to add "Full Control" permissions for "everyone" to the "michfood"-directory and enable the "replicate permissions to subfolders"-option (I don't know the exact designation because I use it in german ... )
I had to delete an existing "Recovery" folder inside the "michfood"-directory from earlier attempts to create the new file and for this I had to take over the ownership of the "Recovery" folder before I was able to delete it.
The original Recovery.img must be in a different folder than "michfood". This can be on the desktop but for a shorter path it could be in the root directory.
I had success after copying "cwmr 6015.bat" to "go.bat" (it's shorter and does not contain any space in it) and calling it from command line from its directory( C:\>cd C:\michfood ) with: "go C:\Recovery.img" ( I had Recovery.img on C:\ ).
makbro said:
3. Files not hdden or protected.
4. Also turned off my antivirus and firewall.
No luck....Please help !!! Thanx in advance
Click to expand...
Click to collapse
I hope this helps ...
Thanx
Thanx for the suggestions everyone, appreciate it...I got it working in the mean time on a WinXP desktop without any problem
makbro said:
Thanx for the suggestions everyone, appreciate it...I got it working in the mean time on a WinXP desktop without any problem
Click to expand...
Click to collapse
HOW?
Tell me what you did...
Cristian.Ene said:
HOW?
Tell me what you did...
Click to expand...
Click to collapse
I copied the folder as "C:\michfoods" and recovery image file as "C:\recovery.img" and gave the command "cwmr6015 C:\recovery.img"...Before that, I removed the space from the file name "cwmr 6015.bat" and saved it as "cwmr6015.bat".
Hi, i rooted succesfuly my a2107a device and installed backup Gscript ...loading "back_mt6575_a4_v2c.sh and saving it , but when it comes to run...nothing...only the counter saying how many sec's till stop.Any ideeas why?
. I don't even want a custom ROM. I just want to be rooted and run stock with rooted google play store apps. Am I there?
I just want to run rooted apps with no ROM flashing...oh god why...where is the guide to root and only root?
You'd think this http://forum.xda-developers.com/show....php?t=1652398 would be where to go to do that, but evidently it's sending me down the road to custom ROM flashing. AGHGHGhjkdashbdas. Do not want.
Ok, so here's where I am, I have finished step 8:
1. Download Odin 1.85 .
2. Download(USE FIREFOX!) ClockworkMod TOUCH 5.5.0.4 OR TWRP 2.2.2.0, they are both named "recovery.tar.md5" and will be downloaded as "recovery.tar.md5", DO NOT CHANGE the filename or else it wont install.
3. Extract the contents of odin-185.zip to a folder.
4. Run Odin 1.85.exe from the folder you extracted it to.
5. Prepare Odin: Check "auto-reboot" and UNCHECK ALL OTHER OPTIONS. SEE COMPUTER SREEN PICS BELOW.
6. Only Click "PDA" and select the recovery.tar.md5 file you downloaded. SEE COMPUTER SREEN PICS BELOW.
7. How To Put your device into Download Mode: DO NOT TOUCH THE POWER BUTTON FOR THIS PROCEDURE. - download mode is NOT the same as recovery mode
a. Connect the USB cable to your PC, but NOT to your phone.
b. Remove the battery.
c. Reinsert the battery.
d. ATT PHONES - Press and keep down both Volume Up and Volume Down keys simultaneously.
ROGERS PHONES - Press and keep down only the Volume Down key.
DO NOT RELEASE THE VOLUME KEY(S) UNTIL INSTRUCTED TO DO SO IN STEP (f)
e. Insert the USB cable into your device. The phone will turn itself on when usb cable is inserted - DO NOT TOUCH THE POWER BUTTON.
f. You will now see a screen w/a yellow triangle warning you about installing a rom . Now release the volume key(s) - SEE PHONE PICS BELOW
g. Press and release the "Volume Up" key to enter into download mode - SEE PHONE PICS BELOW
h. You should now be at the Download Mode screen w/odin recognizing your phone. SEE COMPUTER SREEN PICS BELOW.
8. Click Start in Odin. It will flash the new recovery and will reboot the phone when completed. Your device will autoreboot into android. You are done using ODIN.
9. UPDATING CWM OR TWRP:
Now you need to udate CWM, download and copy cwm6027touch_v14.4.6_skyrocket.zip file to your sdcard, boot into recovery and choose "INSTALL FROM SDCARD" from recovery, install the file and reboot back into recovery to see if it installed correctly.
sk8erwitskil's CWM thread is here HERE , check to see if above file is the latest or dl the "Flashable zip" CWM file from there.
If upgrading TWRP go here HERE and follow the dev's instructions on using goo app, or you can use the flashable TWRP 2.4.1.0 file HERE and copy that file to your sdcard, boot into recovery and pick "INSTALL" from recovery, install the file and reboot back into recovery to see if it installed correctly.
How to enter recovery read section #2 below.
How to use cwm read THIS, also read Q&A on recoveries
You can upgrade to either CWM OR TWRP from which ever recovery TAR file you used in ODIN in step #2 from above.
10. You're done newbie and soon to be a power user, read and educate yourself as much as you can before flashing, happy flashing.
Click to expand...
Click to collapse
I don't know how to do step 9. Do I even need it? I have no desire to run a custom ROM.
yargdpirate said:
OK so here's the list of instructions I'm using to root my Skyrocket:
I have completed everything through step 4. I completely do not understand what to do after that. So, like I'm a 40 year old soccer mom, can you explain what I'm supposed to do to fulfill step 5? Is it through the odin app on my pc? Is this completed on my phone? The link provided that ostensibly explains to noobs how to do this (http://forum.xda-developers.com/showthread.php?t=1777970) doesn't adequately explain to me what I'm doing and where.
Help, please!
Click to expand...
Click to collapse
Assuming that you have successfully installed your custom recovery you then need to know which recovery you installed before you update it. If you used CWM you can get the updated version from the Skyrocket development thread. Put the updated CWM file on your SD card and flash that zip while in recovery. If you used TWRP you can update it through the app that it installed if it did install one. GooManager (someone correct me if I am wrong on the name) I think GooManager needs suoeruser privileges. So which recovery did you flash?
CodeNameRedNeck said:
Assuming that you have successfully installed your custom recovery you then need to know which recovery you installed before you update it. If you used CWM you can get the updated version from the Skyrocket development thread. Put the updated CWM file on your SD card and flash that zip while in recovery. If you used TWRP you can update it through the app that it installed if it did install one. GooManager (someone correct me if I am wrong on the name) I think GooManager needs suoeruser privileges. So which recovery did you flash?
Click to expand...
Click to collapse
Put the updated CWM file on your SD card and flash that zip while in recovery?
Click to expand...
Click to collapse
It's CWM. How do I
A. Put the updated CWM file on my SD card and
B. Flash that zip while in recovery? Is that through Odin, or what?
Thanks
yargdpirate said:
It's CWM. How do I
A. Put the updated CWM file on my SD card and
B. Flash that zip while in recovery? Is that through Odin, or what?
Thanks
Click to expand...
Click to collapse
i think you should stay on stock, read more b4 you brick your phone, no sense in rooting/installing custom roms when you dont know how to install a file on your scard, im not putting you down but trying to give you friendly advice
Vincom has a point. I taught myself through these forums and Google how to do it back in October of 2011. I flashed many a ROM and many files since then until I bricked mine Thursday. Now I have to pay 60 dollars to get it fixed. But on the upside I now have a Note II to play with.
Edit: She is asking for help though and she did ask in the right thread. Some people need more help than others.
vincom said:
i think you should stay on stock, read more b4 you brick your phone, no sense in rooting/installing custom roms when you dont know how to install a file on your scard, im not putting you down but trying to give you friendly advice
Click to expand...
Click to collapse
Oh. ****. I don't even want a custom ROM. I just want to be rooted and run stock with rooted google play store apps. Am I there?
I just want to run rooted apps with no ROM flashing...oh god why...where is the guide to root and only root?
You'd think this http://forum.xda-developers.com/showthread.php?t=1652398 would be where to go to do that, but evidently it's sending me down the road to custom ROM flashing. AGHGHGhjkdashbdas. Do not want.
Ok, so here's where I am, I have finished step 8:
1. Download Odin 1.85 .
2. Download(USE FIREFOX!) ClockworkMod TOUCH 5.5.0.4 OR TWRP 2.2.2.0, they are both named "recovery.tar.md5" and will be downloaded as "recovery.tar.md5", DO NOT CHANGE the filename or else it wont install.
3. Extract the contents of odin-185.zip to a folder.
4. Run Odin 1.85.exe from the folder you extracted it to.
5. Prepare Odin: Check "auto-reboot" and UNCHECK ALL OTHER OPTIONS. SEE COMPUTER SREEN PICS BELOW.
6. Only Click "PDA" and select the recovery.tar.md5 file you downloaded. SEE COMPUTER SREEN PICS BELOW.
7. How To Put your device into Download Mode: DO NOT TOUCH THE POWER BUTTON FOR THIS PROCEDURE. - download mode is NOT the same as recovery mode
a. Connect the USB cable to your PC, but NOT to your phone.
b. Remove the battery.
c. Reinsert the battery.
d. ATT PHONES - Press and keep down both Volume Up and Volume Down keys simultaneously.
ROGERS PHONES - Press and keep down only the Volume Down key.
DO NOT RELEASE THE VOLUME KEY(S) UNTIL INSTRUCTED TO DO SO IN STEP (f)
e. Insert the USB cable into your device. The phone will turn itself on when usb cable is inserted - DO NOT TOUCH THE POWER BUTTON.
f. You will now see a screen w/a yellow triangle warning you about installing a rom . Now release the volume key(s) - SEE PHONE PICS BELOW
g. Press and release the "Volume Up" key to enter into download mode - SEE PHONE PICS BELOW
h. You should now be at the Download Mode screen w/odin recognizing your phone. SEE COMPUTER SREEN PICS BELOW.
8. Click Start in Odin. It will flash the new recovery and will reboot the phone when completed. Your device will autoreboot into android. You are done using ODIN.
9. UPDATING CWM OR TWRP:
Now you need to udate CWM, download and copy cwm6027touch_v14.4.6_skyrocket.zip file to your sdcard, boot into recovery and choose "INSTALL FROM SDCARD" from recovery, install the file and reboot back into recovery to see if it installed correctly.
sk8erwitskil's CWM thread is here HERE , check to see if above file is the latest or dl the "Flashable zip" CWM file from there.
If upgrading TWRP go here HERE and follow the dev's instructions on using goo app, or you can use the flashable TWRP 2.4.1.0 file HERE and copy that file to your sdcard, boot into recovery and pick "INSTALL" from recovery, install the file and reboot back into recovery to see if it installed correctly.
How to enter recovery read section #2 below.
How to use cwm read THIS, also read Q&A on recoveries
You can upgrade to either CWM OR TWRP from which ever recovery TAR file you used in ODIN in step #2 from above.
10. You're done newbie and soon to be a power user, read and educate yourself as much as you can before flashing, happy flashing.
Click to expand...
Click to collapse
I don't know how to do step 9. Do I even need it? I have no desire to run a custom ROM.
For just rooting u have to run the superuser zip through your recovery
Oh and if you are not understanding what the stickies are saying to do then look it up on youtube because there are a lot of step by step instructions there.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
a. put updated file in your micro sd card.... plug ur micro sd card to pc... drag file and drop it in your micro sd card. put the micro sd card back in phone.
b. to go to recovery press power button + vol+ + vol- all at once and hold.
why do u need to unlock play store app? playstore is accessible completely even without root. you can also sideload Amazon appstore and other apps without root. no need to get all bricked up just to run playstore. i'm confused what are you trying to do again?
droidbabyxda said:
a. put updated file in your micro sd card.... plug ur micro sd card to pc... drag file and drop it in your micro sd card. put the micro sd card back in phone.
b. to go to recovery press power button + vol+ + vol- all at once and hold.
why do u need to unlock play store app? playstore is accessible completely even without root. you can also sideload Amazon appstore and other apps without root. no need to get all bricked up just to run playstore. i'm confused what are you trying to do again?
Click to expand...
Click to collapse
im guessing he wants to run apps from play that require root, eg titanuim backup, but he doesnt know how to put a file on his sdcard, but then he has to learn how to install zips from recovery which someones got to teach him since he doesnt want to read/learn/search for the answers. he seems to be impatient and wants it done "now", its a brick waiting to happen, my advice to him was to slowdown and learn
vincom said:
im guessing he wants to run apps from play that require root, eg titanuim backup, but he doesnt know how to put a file on his sdcard, but then he has to learn how to install zips from recovery which someones got to teach him since he doesnt want to read/learn/search for the answers. he seems to be impatient and wants it done "now", its a brick waiting to happen, my advice to him was to slowdown and learn
Click to expand...
Click to collapse
agree and such bad attituted too. i wouldn't want to help anybody who cusses in every conversation geez little respect goes a long way
It you just want to root and not want to flash any custom ROMs or anything related to it,I will tell you how to from total beginning
ALL DATA WILL BE LOST , BACKUP EVERYTHING
In order to root Android 4.2 the following three requirements must be satisfied beforehand:
The Android SDK, which you can download from Google Developers
A custom recovery like ClockworkMod (CWM) or Team Win Recovery Project (TWRP)
SuperSU, which you can download from CF-Root
There are no major differences between the two, but TWRP is more touch-oriented thanks to larger buttons. CWM is also available in a touch-compatible variant, but it has much smaller buttons. It's a matter of personal preference between the two though, but you have to choose one.
Before starting the process I urge you to perform a backup, as all data might be lost afterwards. You can copy the contents of the SD card to a safe external location such as cloud storage service or computer hard drive.
The first step that needs to be performed after all the files are downloaded is to install the Android SDK. Afterwards open the Android SDK Manager and select the following two items:
Android SDK Platform-tools -- it contains the required programs to install Android 4.2 Jelly Bean
Google USB Driver -- it contains the necessary drivers for the Nexus device
Then you should create a folder in an easily accessible location within the command line. In this example I will use a folder named "Root" in my C:\ drive in Windows. The path name will therefore be: "C:\Root".
From the folder where Android SDK Platform-tools is installed (in my case it is "C:\Program Files x86)\Android\android-sdk\platform-tools" copy the following files to the previously created "Root" folder:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
The following files must also be copied to the "Root" folder:
CWM-SuperSU-v0.97.zip -- SuperSU file
The custom recovery that you previously downloaded for your specific device (please see below)
For my 8 GB nexus 7 wifi(codename "grouper" I will use TWRP with the name "openrecovery-twrp-2.3.1.0-grouper.img".
You can easily find the codename for your devoice by looking into Google
The custom recovery file differs for each device, please make sure you download the correct file
In order to make the process smoother for instance the SuperSU file can be renamed to "root.zip" and the custom recovery to "customrecovery.zip". It's a matter of convenience, but for accuracy I will stick to the original naming for this guide.
If the previous steps are completed you must have the following six files in your "Root" folder:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
CWM-SuperSU-v0.97.zip -- SuperSU file
The custom recovery. In my case it is "openrecovery-twrp-2.3.1.0-grouper.img"
From there, you can proceed to install the drivers for "fastboot mode". To install them, follow these steps:
Power off your Nexus device.
Press and hold Volume Up and Volume Down then press and hold the Power button; the device will now enter "fastboot mode".
Go to Device Manager (Computer -> Properties -> Device Manager in Windows 7/8) and identify the device; for me it shows up as Android 1.0.
Right click Android 1.0 and select "Update Driver Software," then select "Browse my computer for driver software".
Select "Let me pick from a list of device drivers on my computer," then click "Next".
From "Have Disk..." option go to the folder where you have Google USB Driver installed (for me it's "C:\Program Files .(x86)\Android\android-sdk\extras\google\usb_driver" and select "android_winusb.inf".
Out of the three options select "Android ADB Interface" and validate any future warning window to install the driver.
Final preparations
Everything is prepared in order to start the installation process, but in order to do so a command window must be opened. Windows Key + R opens "Run"; type in "cmd" and the command window appears. Typing "cd C:\Root" and pressing Enter sets the "Root" folder as the working directory. Pressing the Shift key and right clicking inside the "Root" folder will also deliver the same result.
The device must be turned on in "fastboot mode" which I have explained at step no.2 during the driver installation process, and obviously plugged-in to the computer. You then have to type in the following commands while in "fastboot mode":
fastboot devices -- this is just for verification purposes; if there is no listed device then the drivers have been improperly installed and steps 1 through 7 must be redone.
fastboot oem unlock -> you have to accept the prompt in order to continue -- this command will unlock the bootloader, but it will also erase the data on the device which is why a backup is necessary.
fastboot reboot-bootloader -- this will reboot the bootloader.
fastboot flash recovery openrecovery-twrp-2.3.1.0-grouper.img -- this will flash the custom recovery --please use the specific file and name for your particular Nexus device!
fastboot erase cache -- this will erase the cache -- might not be necessary but it's just as a precaution.
fastboot reboot -- this will reboot the device.
After Android 4.2 is loaded and running the SuperSU file must be copied from the "Root" folder to the internal storage (shows up in Windows Explorer as a Nexus device). A simple copy and paste will do the trick here.
Then you have to power off the Nexus device and enter "fastboot mode" again. Use the Volume Up and Volume Down keys to navigate until you can select "Recovery Mode". After the power button is pressed the device will reboot in the new custom recovery.
Rooting your Nexus device
If you have ClockworkMod installed, you have to perform the following steps:
Select "install zip from sdcard"
Select "choose zip from sdcard"
Select "0" (zero) folder
Select "CWM-SuperSU-v0.97.zip"
Select "Yes - Install CWM-SuperSU-v0.97.zip"
Select "Go Back"
Select "reboot system now"
If you have Team Win Recovery Project installed, you have to perform the following steps:
Press "Install".\
Select "CWM-SuperSU-v0.97.zip" -- for me it's in the "0" (zero) folder
Swipe to confirm flash
Press "Wipe cache/dalvik" (just as a precaution)
Swipe to wipe
Press "Reboot System"
After Android 4.2 loads your device can run apps with elevated privileges (meaning it's rooted). A SuperSU app is installed in order to allow root requests, so please use your judgement on which apps you grant access.
If you experiences any problem, please reply and I will look into it.
Sent from my Nexus 7 using xda app-developers app
Sent from my Nexus 7 using xda app-developers app
^^you want him todo that, lmao, he doesnt even know how to put a file on his sdcard to flash it in recovery, theres no way a computer newb is going to be able to follow what you posted
That's why I have not used the word flash anywhere, I know that he does not know how to flash , I have posted the right thing for a total noob,( at least if he knows how to use command in windows or install drivers)
I helped him in the way I could and what he requested
Sent from my Nexus 7 using xda app-developers app
You think that helped. LOL. Your telling him to do things that aren't even required to gain root with this device. Not everything is a nexus bro. Next time you wanna help study up on the phone your giving advice about. lol
Well , thanks for telling me that every android isn't rooted in same manner, I was thinking that all devices are rooted in same ways like for my nexus
Sent from my Nexus 7 using xda app-developers app
naman14, im not putting you down, your step by step howto is admirable, good work, but the problem is that the op is clueless on tech stuff, its not the word "flash" he has a problem with, i could of said "install" and it would lead to same conclusion, he doesnt know how to copy a file to his sdcard, if he cant do that he has no business in modding his phone until he learns more. anyhow the op is long gone by now
I upgraded my samsung skyrocket s2 version 2.3.6 to 4.0.4 through the Kies. Then I tried to install TWRP 2.2.0 and Odin 1.85. I saw COM 14 ; COM 17 when I hit start button .It said
FAILED. Now it showed a yellow triangle in the middle of phone & monitor pictures. ( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again). Please help . Thank you very much.
I just tried other laptop . I saw COM 3 but it said it couldn't open the serial (COM )port . All thread completed (success 0/ failed 1)
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