Database Users

[GUIDE] Galaxy Tab 2 10.1 OR 7.0 Rooting/CWM/Restoring To Stock

WARNING: Using sections A, B or E will increase your flash counter and thus void your warranty.
NOTE: This device is almost unbrickable so long as you don't mess around with bootloaders, so if something goes wrong post in the Q&A section and we'll help you fix it.
MODEL NUMBER KEY:before you use this guide, you must find your model number.
First digit: 5 for tab 10.1, 3 for tab 7.0
Final three digits: 100 for 3g, 110 for wifi international, 113 for wifi American
SECTIONS:
A. Root stock ICS or JB
B. Install a JB-based ROM
C. Install a ICS-based ROM
D. Install a kernel
E. Restore to stock
F. Flash a file with Mobile ODIN
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
A. Root stock ICS or JB
This should root any gtab2 10.1 or 7.0 model running ICS or JB. It will not wipe any data.
1. Download and install if you don't already have them:
SAMSUNG KIES
Odin v1.83
2. Download the correct ClockworkMod Recovery (CWM) for your device according to model number:
CWM6 for p5100
CWM6 for p5110
CWM6 for p5113
CWM6 for p3100
CWM6 for p3110 and p3113
3. Put the SuperSU installer zip on your MicroSD card or internal storage.
4. Turn off the tablet
5. Hold volume UP (away from power button) for a few seconds
6. Volume DOWN (towards the power button) to confirm that you want to enter download mode
7. Open ODIN
8. Plug in your tablet. A box in ODIN should turn yellow.
9. Click PDA and browse to the recovery file you downloaded in step two.
10. Uncheck Auto Reboot In ODIN
11. Click Start.
12. Hold power until the screen goes black to get out of download mode. Hold power and volume down until you see the "Galaxy Tab 2" screen. If you mess up and the tablet boots normally, start over from step four. If your recovery says "stock recovery <3e>", then you missed a button combo when booting and Clockworkmod was overwritten by your ROM. No harm done, just start over from step 4.
13. Use the volume buttons to navigate to install zip from sdcard, then choose zip from sdcard (or internal storage)
14. Select the zip file you downloaded in step 3 and install it.
15. Click "reboot system now"
16. If you're on 4.0.4 or 4.1.1, you will see a message asking you if you want to delete the OEM/stock recovey. Say yes.
16. You should be rooted!
NOTE: CWM recovery can deleted if you perform a normal boot when your tab is on the 4.0.4 or 4.1 stock ROM. If your recovery is deleted, perform steps 4-12 again to get it back.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
B. Install a JB-based (4.2 , 4.3 or 4.1 ) ROM
THIS WILL WIPE YOUR DATA
JB 4.1 ROM's for the tab 10.1:
CyanogenMax CM10 (p5100 only)
Teamhacksung CM10
AOKP JB
AOSP 4.1.1
ParanoidAndroid
Deodexed Stock JB
Zap Blaster
JB 4.2 ROM's for the tab 10.1:
CM10.1 Nightlies
JB 4.1 ROM's for the tab 7.0:
AOKP JB
Teamhacksung CM10
ButterNutz
Tab2Lite Resurrection (p3113 only)
ParanoidAndroid
TabNex 7 (p3113 only)
Sungsonic
Tsunami X
JB 4.2 ROM's for the tab 7.0:
CM10.1 Nightlies
JB 4.3 ROM's for the tab 10.1:
CM10.2 Nightlies
JB 4.3 ROM's for the tab 7.0:
CM10.2 Nightlies
1. Download the ROM to your tablet's MicroSD card or internal storage
2. Download Google Apps and put it on your tab.
3. Turn off the tablet
4. Hold volume UP (away from power button) for a few seconds
5. Volume DOWN to confirm that you want to enter download mode
6. Open ODIN
7. Plug in your tablet. A box in ODIN should turn yellow.
8. Click PDA and browse to the recovery file that you should have downloaded in section A step 3.
9. Click Start.
10. There should be a green box in the upper left corner saying "PASS". Unplug your device.
11. Reboot into recovery (see above)
12. Go to Backup/Restore and hit backup to external storage (it may take a while)
13. Click wipe data/factory reset
14. Go to install zip from sdcard>choose zip from sdcard or internal storage
15. Find your ROM and hit install.
16. Go to install zip from sdcard>choose zip from sdcard or internal storage
17. Find gapps-jb-20120726-signed.zip and hit install.
18. After it's finished, hit reboot system now.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
C. Install an ICS-based ROM
THIS WILL WIPE YOUR DATA
ICS TW/Stock-based ROM's for Tab 10.1:
4.0.3:
Fry ROM (p5100)
CleanROM (p5113 & p5110)
InfectedROM (p5113 & p5110)
4.0.4:
SRD (Stock Rooted Deoxed) ICS (p5113)
ASERG RUS (p5100) (does not require wipe when coming from stock)
ICS TW/Stock-based ROM's for Tab 7.0:
SRD Base (p3113)
Tab2Lite (p3113)
BAMF Galaxy Cubed
kwbr
ICS AOSP-based ROM's for 10.1: (all are 4.0.4)
Cherry Picked CM9 (p5110) (needs gapps)
Teamhacksung CM9 (all versions of Gtab 2 10.1) (needs gapps)
ICS AOSP-based ROM's for 7.0:
Codename Lungo CM9 AOKP
BlackIce AOKP
AOKP M6
RomsWell
NOTE: If you are on CM9 and want to move to a TW-based ROM, you MUST flash the ADB fix kernel (10.1) or after step 9 in this section.
1. Download the ROM to your tablet's MicroSD card or internal storage
2. (OPTIONAL) If your ROM needs gapps (marked in green), download http://goo.im/gapps/gapps-ics-20120429-signed.zip and put it on your tab.
3. Reboot into recovery (see above)
4. Go to Backup/Restore and hit backup (it may take a while)
NOTE: You can skip the next step if coming from stock and flashing Aserg RUS or RomsWell
5. Click wipe data/factory reset
7. Go to install zip from sdcard>choose zip from sdcard/internal storage
8. Find your ROM (or gapps) and hit install.
9. (OPTIONAL) If your ROM needs gapps, repeat steps 7-8 but with the gapps file.
10. After it's finished, hit reboot system now.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
D. Install a kernel
10.1 kernels (compatible with all models)
TW kernel (for stock and stock-based ROM's):
ADB fix kernel NOTE: This kernel fixes a bug in the stock kernel that prevents ADB from running as root. Otherwise, it is exactly like stock. If you aren't using ADB, you don't need this. (use subsection 1)
CM9 kernel (only for official CM9):
MetalliKernel (use subsection 2)
CM10OC kernel (for CM10 ROM's):
CM10OC Kernel (use subsection 2)
AOKP kernel (for AOKP JB):
AOKP Official OC Kernel (use subsection 2)
CM10.1 kernel (for CM10.1, PAC-ROM, Baked Blackbean):
DhollmenCM (use subsection 2)
CM10.2 kernel (for CM10.2 based ROM's):
NEXT (use subsection 2)
7.0 kernels:
ICS Kernel (for stock and CM9 ICS):
Stock/AOSP OC Kernel (p3113 only) (use subsection 2)
CM9 kernel (only for official CM9):
MetalliKernel (all versions of gtab 7.0) (use subsection 2)
CM10OC kernel(for codeworkxx's CM10):
CM10OC Kernel (all versions of gtab 7.0) (use subsection 2)
AOKP kernels (for AOKP JB):
AOKP Official OC Kernel (all versions of gtab 7.0) (use subsection 2)
CM10.1 kernel (for CM10.1, PAC-ROM, Baked Blackbean):
DhollmenCM (use subsection 2)
Subsection 1: Install an odinable kernel (.tar or .tar.md5 file)
1. Power off, then hold power and volume UP (towards power button) . Then click volume DOWN to get into download mode.
2. Open ODIN. One of the boxes should be yellow.
3. Use the PDA button to select the kernel.
4. Hit Start
5. Enjoy!
Subsection 2: Install a CWM flashable kernel (.zip file)
1. Put the kernel file on your SD card.
2. Reboot into recovery (power + volume DOWN).
3. OPTIONAL: go to backup & restore and click backup.
4. Click install zip from sdcard>choose zip from sdcard
5. Select the kernel file and confirm the install.
6. Go back to the main menu and click reboot system.
7. Enjoy!
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
E. Restore to stock
THIS WILL WIPE YOUR DATA! IT MAY ALSO WIPE YOUR INTERNAL SDCARD, SO BACK ANY DATA ON IT UP!
p5100: http://www.sammobile.com/firmwares/database/GT-P5100/
p5110: http://www.sammobile.com/firmwares/database/GT-P5110/
p5113: http://www.sammobile.com/firmwares/database/GT-P5113/
p3100: http://www.sammobile.com/firmwares/database/GT-P3100/ (PIT files: 16Gb p3100, 8GB p3100
p3113: http://www.sammobile.com/firmwares/database/GT-P3110/
p3110: http://www.sammobile.com/firmwares/database/GT-P3113/
Note: for more language options and versions of stock ROM's for the tab 10, go here.
1. Download the stock firmware matching your carrier/region for your device from the correct link above. This will take a long time. When it's finished, unzip or unrar it.
2. If and only if your device is currently bricked and hasn't been fixed by other stock restore attempts, AND your ROM includes a .pit file, click PIT and open the .pit file you downloaded, and check Re-Partition in ODIN. Skip to step 4.
3. Reboot into recovery and select wipe data/factory reset.
4. Reboot into Download Mode.
5. click PDA and find the stock file (PDA/PLATFORM file, the largest one).
6. OPTIONAL: if you want to flash the bootloader and/or csc, you can select them as well. If you don't know what that means, you don't need to do it.
7. Click Start.
8. Try to boot the tablet. If it hangs, do not panic, just repeat step 2.
9. Enjoy!
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
F. Flash a file with Mobile ODIN
Using Mobile ODIN is recommended for advanced users only. You must have root.
Using Mobile ODIN will NOT increase your flash counter, and therefore your warranty will remain intact.
1. Extract or copy the file you want to flash to your tablet. If you're flashing a ROM, you only want the PLATFORM/PDA file (.tar.md5) (almost always the largest file)
NOTE: There are no .pit files in Mobile ODIN. They are installed along with your flashkernel.
2. Download either Mobile ODIN pro ($5) OR Mobile ODIN lite (does not include EverRoot, so you will need to re-root using ODIN) and the p51xx FlashKernel from here.
3. Click on Open File... in Mobile ODIN and find the file you want to flash.
4. If you're flashing a ROM, click Recovery and click clear on the window that pops up.
5. If applicable, enable EverRoot.
6. Select both Wipe data and cache and Wipe Dalvik cache
7. Click flash firmware.
THANKS: weltwon and Chainfire for root & unroot method, codeworkx for the newer versions of CWM, count dooku for discovering than TW ROM's don't include a kernel the hard way, invisiblek for testing stock ROM on p5113, and all you devs who make custom ROM's and kernels.
If this guide has helped you, please hit the thanks button.

Great work!! Thank you!

New Recovery
There is a new one from here without double image from here and is a bit faster link here:- http://forum.xda-developers.com/showthread.php?t=1722063

@jamesclinton: How did you install the new recovery?
i have the old one with the double image. But when I want to confirm to proceed to odin my tab restart. Odin does not recognize my tab until it starts up
btw: do you know if i can flash de new ROM with the old recovery?
greez
edit: i have to put UP to confirm. NOT DOWN

tanks
GT-P5100_XEO_P5100XWALD7_P5100XXLD7_P5100OXXALD9.rar
this link is unable

If you mean the stock ROM's, both of those links work!

Well, crap
I just bought a GT-P5113 from Fry's yesterday and followed your instructions down to the letter. I was only able to get CM9 working but it is having wifi issues (many apps give `fail to download` errors when they download something on the internet - like swiftkey getting language packs)
CleanROM (1.0 and 1.1) and InfectedROM both don't get past the "Galaxy Tab 2 10.1" screen. I even let it sit for an hour to see if something would resolve but it doesn't. I've cleared data, cache, dalvik, etc before each install. I reflashed CWM like 4 times, I've formatted everything except the kitchen sink, I've repaired permissions, nothing.
I wish wish WISH I had a backup of the stock rom to go to as it was a better option than what Im stuck with now (the experimental nightly of CM9)
Is anyone having the same problem and figured it out or am I just going to have to wait until better ROMs come out? :-/

You're going to have to be the tester for the restore to stock procedure above.

CM9 nightly bug list and changelog
andrewortman said:
I just bought a GT-P5113
[.......]
I wish wish WISH I had a backup of the stock rom to go to as it was a better option than what Im stuck with now (the experimental nightly of CM9)
Is anyone having the same problem and figured it out or am I just going to have to wait until better ROMs come out? :-/
Click to expand...
Click to collapse
I feel your pain. I'm in the same predicament. CleanRom hangs, CM9 is buggy. Peel cannot detect the IR blaster. Pulse and galary are not showing images.
I wonder is there is a page were I can check what bugs have been found and what changes have been made in CM9 nightly?
Thanks.

You can try InfectedROM. I used it and had zero issues.

Thanks MultipleMonomials for the suggestion. Just tried it, but this infectedRom is freezing on the SamsungGalaxyTab2 10.1 boot screen as well. I've waited for 5minutes for something to happen. So I guess I'll hop back to my CM9 backup.
(If only I had a stock backup... well a lesson learned.)

Oh. That's what you meant when you said Cleanrom hung. You might try reflashing a TW kernel (i.e. ADB fix) after flashing InfectedROM. And I don't believe any custom ROM's have support for the IR blaster (I might be wrong).

If i wanted to return to the stock rom on the 7.0 (GT-P3113) which one should I download?

This guide isn't for the tab 7.0.

So to return to stock i have to install (p5110 taiwan android, the link that is in the first page in 4th point *Return TO stock*) even if i am italian because why it is called *Taiwan android p5110* ??!

thx
thanks for your share

Internal SD privilege issue
MultipleMonomials said:
Oh. That's what you meant when you said Cleanrom hung. You might try reflashing a TW kernel (i.e. ADB fix) after flashing InfectedROM. And I don't believe any custom ROM's have support for the IR blaster (I might be wrong).
Click to expand...
Click to collapse
Your suggestion worked and most of the stuff is back to normal. Even Peel is starting up again. Just one other item I hope you have a good suggestion for. My Gallery app is not stating up, I complains about not enough memory. I suspect this is due to some privilege issue. I had created a tmp folder on the internal SD to hold the CM9 zip. I cannot delete the folder. If I access the DCIM folder I can't delete any of the image files. Thus I suspect an issue with the privileges.
I ran the fix permissions option in the Clockwork menu, and also ran some other permission fixer of google play. But they did not fix the privileges with which I had issues. I searched the forum for a similar issue & solution, but was unable to find it.
Do you have a suggestion? Thanks in advance!

Hi i am italian and i have P5110 what i have to download and install to return to stock with polaris office, music read hub and simliar ????

count dooku, it looks like your sdcard is corrupted. Get a USB MicroSD reader (you really should have one anyway) and copy your sdcard to your computer. (now's a good time to delete that folder) Then, reformat the card using Windows. Lastly, copy the files back to your sdcard.

Andrew1998, just flash the p5110 stock package.

[HOW TO] Install CM9/CM10 on GB 2.3.6 LATAM (R01 and R02 firmwares)

DISCLAIMER!!!
THIS TUTORIAL IS INTENDED FOR THOSE WHO HAVE FLASHED THE LATAM GINGERBREAD 2.3.6 VERSION WHICH ARE R01 AND R02, SUCH AS RETAIL LATAM, PERSONAL, CLARO, MOVISTAR AND VIVO
If you come from a different firmware this tutorial may not be entirely useful because the root method may vary and if you come from froyo you may need to use CH version for CM9, and flash a GB kernel for CM10... but that's not the point of this thread, go to the ROM's thread and READ the OP before asking dumb questions!
Click to expand...
Click to collapse
ROOT your phone (Check nicofff's method: http://forum.xda-developers.com/showthread.php?t=1750277)
Download and install Droid2Bootstrap (see attachments or http://www.mediafire.com/?rbie0acs53rdfwc)
Download bootmenu1.1.0 and put it on your SD Card (see attachments or http://www.mediafire.com/?lh61gvslph4x4sv)
For CM9 download latest European GB Kernel version this thread: http://forum.xda-developers.com/showthread.php?t=1623385 and latest ICS gapps from http://goo.im/gapps/ and put both zips on your SD Card
For CM10 download latest version from this thread: http://forum.xda-developers.com/showthread.php?t=1827801 and latest JB gapps from http://goo.im/gapps/ and put both zips on your SD Card
Open Droid2Bootstrap and grant it root permission
Hit "Bootstrap Recovery" You'll see a pop-up telling you "SUCCESS!"
Hit "Reboot Recovery" and your phone will reboot and enter on custom recovery
Select "Install zip from sd card" and then choose the bootmenu1.1.0.zip (use slider keyboard arrow keys to move, and "OK" button to select)
Reboot
When booting, the led will turn blue, press both volume buttons to enter bootmenu
In the bootmenu, go to "Recovery" > "Custom Recovery" (use volume buttons to move, power button to select)
In the custom recovery, select "Wipe data/factory reset" and "Wipe cache partition"
Go to "Advanced"
Select "Wipe Dalvik Cache" and "Wipe Battery Stats"
Go back and select "Install zip from sd card" and then choose the CyanogenMod zip file (CM9 or CM10)
Do the same for gapps: Choose gapps-ics-xxxxx.zip for CM9 and gapps-jb-xxxxx.zip for CM10
Reboot
Be happy
You should be booting into CyanogenMod now!
If your signal is not working try installing the MS2Toolbox (see attachments or http://www.mediafire.com/?k3h8vpcj6b2it0e) and then go to Baseband Switcher and choose your right band and then reboot, you might need to try more than once, but this tool will get your signal up
ALL CREDITS TO nicofff FOR THE ROOT METHOD, TO sfc3001 FOR THE CM9 ROM, AND TO tezet FOR THE CM10 ROM

Caesarivs said:
Well, now that it's possible to root this firmwares (check this thread: http://forum.xda-developers.com/showthread.php?t=1750277) it's possible to try some custom roms on our MS2, in this particular case I'll make a little guide on how to install sfc3001's CM9:
ROOT your phone (Check nicofff's method: http://forum.xda-developers.com/showthread.php?t=1750277)
Download and install Droid2Bootstrap (see attachments or http://www.mediafire.com/?rbie0acs53rdfwc)
Download bootmenu1.1.0 and put it on your SD Card (see attachments or http://www.mediafire.com/?lh61gvslph4x4sv)
Download CM9 and put it on your SD Card (download the latest version from this thread: http://forum.xda-developers.com/showthread.php?t=1623385)
Download Google Apps and put them on your SD Card (download the latest version from http://goo.im/gapps/)
Open Droid2Bootstrap and grant it root permission
Hit "Bootstrap Recovery" You'll see a pop-up telling you "SUCCESS!"
Hit "Reboot Recovery" and your phone will reboot and enter on custom recovery
Select "Install zip from sd card" and then choose the bootmenu1.1.0.zip (use slider keyboard arrow keys to move, and "OK" button to select)
Reboot
When booting, the led will turn blue, press both volume buttons to enter bootmenu
In the bootmenu, go to "Recovery" > "Custom Recovery" (use volume buttons to move, power button to select)
In the custom recovery, select "Install zip from sd card" and then choose the CM9 zip file
Do the same for gapps: "Install zip from sd card" > gapps.zip
Select "Wipe data/factory reset" and "Wipe cache partition"
Go to "Advanced"
Select "Wipe Dalvik Cache" and "Wipe Battery Stats"
Go back and reboot
You should be booting into ICS now!
If your signal is not working try installing the MS2Toolbox (see attachments or http://www.mediafire.com/?k3h8vpcj6b2it0e) and then go to Baseband Switcher and choose your right band and then reboot, you might need to try more than once, but this tool will get your signal up
ALL CREDITS TO nicofff FOR THE ROOT METHOD AND TO sfc3001 FOR THE CM9 ROM
Click to expand...
Click to collapse
:good::good: good, and now, i am on cm9:good::good:

THANKS! It was really helpful as I find it a bit difficult to install a custom ROM after getting root following nicofff procedure. Don't know why, but installing a zip the usual way didn't work. Then I followed your instructions and it worked like a charm.

Thanks that was almost too easy
I was already rooted before but did not dare the Cyanomod mainly to their alpha (still?) status, but when I heard about the feature that volume rocking allows skipping to the next song, I knew that I was doomed !
EDIT: BTW found it very stable after 1 day of extensive trial. I am really impressed !

Love this :good::good::good:

Hi,
first of all, thanks for this howto!
I am however getting problems. Coming from Brazilian VIVO 2.3.6. I succesfully completed all steps, until I get to rebooting after installing the bootmenu file. When I do a normal reboot, my phone's just rebooting into VIVO. When I choose to reboot recovery then I get an triangle image. When I push both volume rockers, I'm getting in another recovery menu. When I apply CM9 update, it will not verify.. That is where I'm stuck. Am I doing something wrong here?
SOLVED:
When you've installed bootmenu 1.1.0, it is possible that it does not load the first reboot. Just let it reboot normally, than reboot again! Now it worked!
thanks!

This is great! :good:
Few days ago I was looking for something like this but just can't find.
I experimented myself and got CM9 working on my phone.
(Took quite a lot of time waiting booting)
Thank god i did not brick my phone.
This will be great helpful to those who would like to try CM9.

Quick question - does this work with UK stock kernel?
Or does this require a specific kernel.
(How do I check?)

regiment said:
Quick question - does this work with UK stock kernel?
Or does this require a specific kernel.
(How do I check?)
Click to expand...
Click to collapse
This works for european GB kernels, and specifically for latinamerican R01 and R02 GBkernels (which are based on the european GB kernel)
When you go to settings -> About phone, what does it say in Android Version?

Nice Tutorial
Nice Tutorial! Really easy to follow.

:good: Great posts, thanks to you and the makers of "PreInstalameEsta" I've my phone working with this rom , for new updates of the rom do you know if it's necessary to wipe dalvik and cache or factory reset, I just don't want to sync all my accounts again ..
Thanks.

kainlite said:
:good: Great posts, thanks to you and the makers of "PreInstalameEsta" I've my phone working with this rom , for new updates of the rom do you know if it's necessary to wipe dalvik and cache or factory reset, I just don't want to sync all my accounts again ..
Thanks.
Click to expand...
Click to collapse
To update CMx roms from another version of the same branch (ie : a 7 to a 7, a 9 to a 9 and so on) you only need to :
- wipe cache partition
- wipe dalvik cache
- wipe battery stats (optional, it's just to get more accurate battery duration)

Ashareth said:
To update CMx roms from another version of the same branch (ie : a 7 to a 7, a 9 to a 9 and so on) you only need to :
- wipe cache partition
- wipe dalvik cache
- wipe battery stats (optional, it's just to get more accurate battery duration)
Click to expand...
Click to collapse
K, great, thanks

it works! thx a lot !
wait.....where is market ??
EDIT 3: done, i have just reflashed the file (gapp ) in recovery mode

hi all....new problems here
when i open play store it says me: server error
i avoided the problem flashing the gapp file from april instead the last one, now i would ask...what is the differences between the two files ? have i less features or a less fluidity ?
i have another question: where is swype keyboard ? i cant find it in settings !

sminatore said:
hi all....new problems here
when i open play store it says me: server error
i avoided the problem flashing the gapp file from april instead the last one, now i would ask...what is the differences between the two files ? have i less features or a less fluidity ?
i have another question: where is swype keyboard ? i cant find it in settings !
Click to expand...
Click to collapse
I haven't had any problems with latest ICS gapps, are you sure you flashed ICS gapps? Anyway you should always do at least wipe cache and dalvik cache, it's best if you do full wipes AFTER flashing gapps
Swype keyboard is not included in CM9... you can get it from beta.swype.com

Caesarivs said:
I haven't had any problems with latest ICS gapps, are you sure you flashed ICS gapps? Anyway you should always do at least wipe cache and dalvik cache, it's best if you do full wipes AFTER flashing gapps
Swype keyboard is not included in CM9... you can get it from beta.swype.com
Click to expand...
Click to collapse
yes yes im sure ....
ok thx for infos :good:

Caesarivs said:
This works for european GB kernels, and specifically for latinamerican R01 and R02 GBkernels (which are based on the european GB kernel)
When you go to settings -> About phone, what does it say in Android Version?
Click to expand...
Click to collapse
I am currently running Tezet's CM7 ROM 120221-1901-NIGHTLY (Android 2.3.7).
Still not sure what kernel is running!

regiment said:
I am currently running Tezet's CM7 ROM 120221-1901-NIGHTLY (Android 2.3.7).
Still not sure what kernel is running!
Click to expand...
Click to collapse
You must be on Froyo... because tezet's CM7 doesn't work on gingerbread, so if you want to try CM9 you must use Chinese version

In this case, can I follow the 1st post tuto ?
Caesarivs said:
You must be on Froyo... because tezet's CM7 doesn't work on gingerbread, so if you want to try CM9 you must use Chinese version
Click to expand...
Click to collapse
Sent from my MotoA953 using xda premium

[Q] roms

hi can anyone help me I have a Packard bell liberty tab to which I have been told it is an a500 in a different case PB will not update the system to ICS so is there any way I can do this myself using an ICS rom and if there is where can I download this from
thanks in anticipation

[GUIDE]
kevings178 said:
hi can anyone help me I have a Packard bell liberty tab to which I have been told it is an a500 in a different case PB will not update the system to ICS so is there any way I can do this myself using an ICS rom and if there is where can I download this from
thanks in anticipation
Click to expand...
Click to collapse
I got you covered ;p
First of all, you need root. I assume you're on 3.2.1.
To get a rooted stock ROM, download this:
http://depositfiles.com/files/c6pr69ri6
Follow Instructions in PDF...
After you've done that, confirm that you have the superuser app installed now....
Download the latest stable 4.2 or 4.3 ROMS...
(There are many options...CHOOSE !!!ONE!!! (DOWNLOAD GAPPS TOO)
Randomblame's 4.3 : http://forum.xda-developers.com/showthread.php?t=2376662
Randomblame's 4.2: http://forum.xda-developers.com/showthread.php?t=1990136
Pjsports's 4.3: http://forum.xda-developers.com/showthread.php?t=2426942
Pjsports's 4.2: http://forum.xda-developers.com/showthread.php?t=2049874
Thor2002ro's 4.3: (For this one you need a tegraowner's account) http://forum.tegraowners.com/viewtopic.php?f=9&t=1312
)
Thor2002ro's 4.2: http://forum.tegraowners.com/viewtopic.php?f=9&t=1046
(Recommend Thor 4.2 because it is the most stable and updated)
Also download the latest recovery (Using Acer Recovery Installer (Google Play Store) or from here http://forum.tegraowners.com/viewtopic.php?f=8&t=1281 (Also need a tegraowners account).
Put your ROM, Gapps and Recovery files on the root folder of your External SD card. (don't extract anything)
Now power off your tablet.
Now press the power button and volume - (or volume + if you're holding in portrait) key until you boot into recovery. Then navigate to the wipe menu.
Go into the Wipe menu, and do a Data Wipe.
Go into the Install Zip from SD Card menu, and install/upgrade to the latest version of Touch Recovery.
Reboot the A500, and once again go into Recovery (hold VOL-).
Go into the Install Zip from SD Card menu, and install the ROM.
Go into the Wipe menu, and do a Data Wipe. (yes a 2nd data wipe)
Go into the Install Zip from SD Card menu, and install GApps.
Reboot the device (Don't hold VOL- this time).
Enjoy...credits to Dime for this Guide...

Help to install ics on my phone

i have one mytouch 4g with s-off and android 2.2.1 with root and CWM recovery.
i want to install ICS on this but not sure how to proceed as i am really confused by reading all threads . so DEVs kindly help me to install ICS step by step.
thanks

Put a ICS rom onto your sd card. Then flash it.

Broken down version:
1) download an ICS ROM zip file (I recommend SteppNasty Aospx - link in the 'resource bible')
2) put that zip file (don't extract) on the root of your sd card (i.e. not in any folders)
3) reboot your phone into recovery (either adb reboot recovery or power off > battery pull > battery insert > hold volume down button + power > select 'recovery', press power button
4) using CWM recovery, do a factory reset/wipe data, then I think under advanced select 'wipe cache' and 'wipe dalvik' (I don't have CWM anymore). If you like, you can also wipe battery stats, but I'm not sure it does anything.
5) select 'install from zip', and choose your ROM zip file
6) either flash a gapps (google apps) zip file if the ROM thread says it needs it, or reboot if it already includes google apps (most don't). Sometimes (like I think with Stepp Aospx), its actually better to reboot after flashing the rom, then go back to recovery and wipe dalvik & cache and flash gapps after getting through an initial boot. Most rom threads will have a link to the gapps they recommend for their rom. You just need one that matches the android version (i.e ICS gapps for ICS roms)
That's the usual method. Most ROM threads will have instructions on them. Seems like a lot of steps, but it usually only takes a couple of minutes.

How to Use FlashFire App with Ford/KFFOWI (Root Required)

22 May 2016
version 0.32 is considered more stable than 0.33
default settings should be fine for both new installs and updates
Root Junky Video
Amazon Fire 5th gen 7in Slim Rom install on Fire OS 5 1 1 with FlashFire App
https://youtu.be/NaCBSuUuhRE
Official Chainfire FlashFire thread
http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Google+
https://plus.google.com/u/0/communities/116661625291346007584
Alt downloads
https://www.chainfire.eu/
https://download.chainfire.eu/956/FlashFire/FlashFire-v0.31-20160405175326.apk
http://www.apkmirror.com/apk/chainfire/flashfire/
- Fresh Installation from FlashFire 0.27
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Cyanogenmod Zip
- Ensure Auto-mount and Mount /system read/write are UNCHECKED
- Click the Red + button again and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Open Gapps Zip.
- Ensure Auto-mount is UNCHECKED
- Ensure Mount /system read/write is CHECKED
- Move "Wipe" to the Top of the order
- Press the big FLASH button.
Upgrading from FlashFire 0.27
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Cyanogenmod Zip
- Click the Red + button again and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Open Gapps Zip.
- Ensure Auto-mount is UNCHECKED
- Ensure Mount /system read/write is CHECKED
- Click the Red + again and choose 'Wipe'
- ONLY tick Dalvik and Cache.
- Press the big FLASH button.
Installing gapps on Stock Rom Root Required
Wiping should not be necessary.
[url]http://opengapps.org/[/URL] Arm | 5.1.1 | Micro, Nano or Pico
Instructions
Install the app
Download gapps
Open FlashFire app
Allow root access
tap red circle with + in it (bottom right)
Select Flash ZIP or OTA
browse to Gaaps.zip
I didn't check Auto-mount
Tap Check make (top right)
tap red circle with + in it (bottom right)
browse to Gapps.zip
Shouldn't need to check Auto-mount
Select Flash
Ok
Screen will go black for second or so.
Then a lot of code will run through screen
Then you will see normal scripts for gapps install
Device will reboot

Changelog
29 April 2016
Added link to
http://www.apkmirror.com/apk/chainfire/flashfire/
13 May 2016: Current Version is 0.33
Unless otherwise noted, use newest version.
Files may need to be on internal storage, rather SD card.
16 April 2016
Added links to ChainFire's Blog...
Cleaned up post abit
Added instructions from CM12.1
20 March 2016
Due to so many brick devices, I recommend that those with 5.1.X bootloaders
do not install cm12.1
nexus and slim roms have caused far fewer issues
20 Feb 2016
Note:There is some risk if using on 5.1.X Bootlader
Some have reported bricking, when trying to install a rom, unclear what the cause is.
I'm still on 5.0.1 bootloader, and I am not going to update to 5.1.1
I have not seen a clear reason as to why Flashfire is bricking some and not others.
With the locked bootloader, Flashfire should not effect the stock recovery, but yet that seems to be the result in some cases.
There is not failsafe way to install any rom with Flashfire.
Davey126 said:
Fully concur. Additional thoughts:
- leaving wipe at the bottom is just asking for trouble
- dirty flashes are not a great idea when switching roms
- recent FlashFire versions (0.26+) have several changes targeted at CM
- the most serious issues seem to occur with older versions of FlashFire
- wipe options make a difference; consult the rom OP for best selections
- stick to recommended zip options (see rom OP for guidance)
I also believe (but have no decisive evidence to prove) that evironmental complexity plays a role. Suggestions:
- make sure current rom is stable before updating or flashing a new rom
- minimize the number of background tasks before launching FlashFire
- when switching roms skip GAaps on the first pass. A package of choice (preferably nano) can be flashed later with individual apps added from the Play Store as needed. This does complicate the process as FlashFire will need to be sideloaded on the new rom for the initial GAaps flash. Best leave a copy of the FlashFire apk and GAaps zip in a location that won't get overwritten.
Click to expand...
Click to collapse
6 Jan 2016: Be sure that wipe option is listed first,
FlashFire places it as last task,
which will wipe system, and rom will no longer be usable.
and likely the cause of the bricking of fires with the 5.1.1 bootloader.
23 Jan 2016
Don't try to install a custom rom with a low battery
Original post #1
I was able to update SlimLP with just Flashfire
You need to accept being a tester
Install the app
Download rom, gapps...
Root Required
Open FlashFire app
Allow root access
Wipe
tap red circle with + in it (bottom right)
System Data: optional
3rd party apps like a Factory reset
Dalvik Cache: Recommended
Cache partition: Optional
Tap Check make (top right)
(continue for installing Rom)
tap red circle with + in it (bottom right)
Select Flash ZIP or OTA
browse to rom.zip
I didn't check Auto-mount
Tap Check make (top right)
tap red circle with + in it (bottom right)
browse to Gapps.zip
I didn't check Auto-mount
Tap Check-mark (top right)
Select EverRoot
Check Inject SuperSU
Tap Check-mark (Top Right)
scroll down to bottom
Select Flash
Ok
Screen will go black for second or so.
Then a lot of code will run through screen
Then you will normal scripts for rom install (gapps)
Device will reboot
When I tried to install CM12.1 over SlimLP
FlashFire got stuck installing
Maybe possible, just need to select correct settings

next

sd_shadow said:
I was able to update SlimLP with just Flashfire
You need to accept being a tester
Install the app
Download rom, gapps...
Root Required
Open FlashFire app
Allow root access
Wipe
tap red circle with + in it (bottom right)
System Data: optional
3rd party apps like a Factory reset
Dalvik Cache: Recommended
Cache partition: Optional
Tap Check make (top right)
(continue for installing Rom)
tap red circle with + in it (bottom right)
Select Flash ZIP or OTA
browse to rom.zip
I didn't check Auto-mount
Tap Check make (top right)
tap red circle with + in it (bottom right)
browse to Gapps.zip
I didn't check Auto-mount
Tap Check-mark (top right)
Select EverRoot
Check Inject SuperSU
Tap Check-mark (Top Right)
scroll down to bottom
Select Flash
Ok
Screen will go black for second or so.
Then a lot of code will run through screen
Then you will normal scripts for rom install (gapps)
Device will reboot
When I tried to install CM12.1 over SlimLP
FlashFire got stuck installing
Maybe possible, just need to select correct settings
Click to expand...
Click to collapse
When it got stuck installing CM what happened..? Were you able to just reboot? Or did it corrupt the install and you had to reflash via TWRP/CM?

Wonder if it will work from within FireOS 5.0.1.

4t701 said:
When it got stuck installing CM what happened..? Were you able to just reboot? Or did it corrupt the install and you had to reflash via TWRP/CM?
Click to expand...
Click to collapse
I just forced power off, and then I booted it into fastboot mode.
Sent from my KFFOWI using Tapatalk

Failed to install stock over SlimLP, just reboots to SlimLP
Could just need a different install script for stock.

blueberry.sky said:
Wonder if it will work from within FireOS 5.0.1.
Click to expand...
Click to collapse
I haven't tried installing a rom in stock yet.
In Stock 5.0.1, restore SlimLP worked, but it took a while, I thought it was stuck, ,but just left it, came back later and it was running SlimLP just as I backed up
backup was created with FlashFire, haven't tested Twrp created backup with FlashFire, but don't think it will be compatible.

4t701 said:
When it got stuck installing CM what happened..? Were you able to just reboot? Or did it corrupt the install and you had to reflash via TWRP/CM?
Click to expand...
Click to collapse
i wonder if I just didn't wait long enough? Didn't time it, thought it was about 10 mins?
Edit: in reference to the install

I tried to use flash fire to create a backup of my modified stock from, and it ran some script, then went to a blank screen with flash fire on the top. It stayed like that for about 30 minutes before it rebooted, and there was no backup file. I thought I would try it. I would like to see if I can flash cm12.1 on stock. It was a $35 tablet, I don't mind trying stupid stuff with it.
Sent from my SPH-L710T using Tapatalk

pbailey212 said:
I tried to use flash fire to create a backup of my modified stock from, and it ran some script, then went to a blank screen with flash fire on the top. It stayed like that for about 30 minutes before it rebooted, and there was no backup file. I thought I would try it. I would like to see if I can flash cm12.1 on stock. It was a $35 tablet, I don't mind trying stupid stuff with it.
Sent from my SPH-L710T using Tapatalk
Click to expand...
Click to collapse
Blimey that's a long wait. Totally sure it didn't back it up anywhere, seems odd given how long it took?

Pond-life said:
Blimey that's a long wait. Totally sure it didn't back it up anywhere, seems odd given how long it took?
Click to expand...
Click to collapse
I got it to back up and restore on stock, now to try to install cm12, worst case scenario, I have to hook it up to my computer and install it through adb and twrp
Sent from my SPH-L710T using Tapatalk

I dirty flashed CM latest build, gapps.zip, and superSU.zip yesterday. Everything worked perfectly. It only took like a minute to flash all 3 of those zips. No frozen screen or unresponsiveness. No issues with the new CM install or gapps.
Only things I did different from you @sd_shadow was I only wiped dalvik cache and cache partition, I did check 'automount' feature on all 3 of my .zips, and I didn't use the EverRoot to inject superSU into system (as I preferred to just flash the superSU.zip)
sd_shadow said:
I was able to update SlimLP with just Flashfire
You need to accept being a tester
Install the app
Download rom, gapps...
Root Required
Open FlashFire app
Allow root access
Wipe
tap red circle with + in it (bottom right)
System Data: optional
3rd party apps like a Factory reset
Dalvik Cache: Recommended
Cache partition: Optional
Tap Check make (top right)
(continue for installing Rom)
tap red circle with + in it (bottom right)
Select Flash ZIP or OTA
browse to rom.zip
I didn't check Auto-mount
Tap Check make (top right)
tap red circle with + in it (bottom right)
browse to Gapps.zip
I didn't check Auto-mount
Tap Check-mark (top right)
Select EverRoot
Check Inject SuperSU
Tap Check-mark (Top Right)
scroll down to bottom
Select Flash
Ok
Screen will go black for second or so.
Then a lot of code will run through screen
Then you will normal scripts for rom install (gapps)
Device will reboot
When I tried to install CM12.1 over SlimLP
FlashFire got stuck installing
Maybe possible, just need to select correct settings
Click to expand...
Click to collapse

Installing cm12 on stock didn't work. It stuck on the blank flas fire screen for over an hour, so I turned it off a d on and got stuck on the Cm boot screen. Oh weel. It was worth a shot
Sent from my SPH-L710T using Tapatalk

pbailey212 said:
Installing cm12 on stock didn't work. It stuck on the blank flas fire screen for over an hour, so I turned it off a d on and got stuck on the Cm boot screen. Oh weel. It was worth a shot
Sent from my SPH-L710T using Tapatalk
Click to expand...
Click to collapse
sd_shadow said:
When I tried to install CM12.1 over SlimLP
FlashFire got stuck installing
Maybe possible, just need to select correct settings
Click to expand...
Click to collapse
Did you guys use the 'automount' feature or no?

So I tried to flash SlimLP over my CM install...
-I wiped dalvik and cache partition.
-flashed SlimLP, checked 'automount'
-flashed my gapps.zip, checked 'automount'
-flashed SuperSU.zip, checked 'automount'
-FLASHED
-system reboots but hangs at boot animation forever like @pbailey212
So it appears FlashFire is only really useful if you are just using it to update your current CM or SlipLP install (or to flash xposed.zip or your gapps). Doesn't look like it can be used to flash a different ROM from what you are already on. Oh well, it's still pretty useful. Just wish it woulda worked for flashing a different ROM. That or our BL get unlocked so TWRP could be installed. If that ever happens this would be the perfect budget tablet. [emoji41]

4t701 said:
So I tried to flash SlimLP over my CM install...
-I wiped dalvik and cache partition.
-flashed SlimLP, checked 'automount'
-flashed my gapps.zip, checked 'automount'
-flashed SuperSU.zip, checked 'automount'
-FLASHED
-system reboots but hangs at boot animation forever like @pbailey212
So it appears FlashFire is only really useful if you are just using it to update your current CM or SlipLP install (or to flash xposed.zip or your gapps). Doesn't look like it can be used to flash a different ROM from what you are already on. Oh well, it's still pretty useful. Just wish it woulda worked for flashing a different ROM. That or our BL get unlocked so TWRP could be installed. If that ever happens this would be the perfect budget tablet. [emoji41]
Click to expand...
Click to collapse
Well sd-shadow did get it to flash from CM to Slim in the second post on the thread, maybe you needed to wipe more as he did.
---------- Post added at 06:04 PM ---------- Previous post was at 06:00 PM ----------
pbailey212 said:
Installing cm12 on stock didn't work. It stuck on the blank flash fire screen for over an hour, so I turned it off a d on and got stuck on the Cm boot screen. Oh well. It was worth a shot
Sent from my SPH-L710T using Tapatalk
Click to expand...
Click to collapse
Installing slim on stock did work. And restoring my stock back up after realising I really didn't like slim gapps.

Pond-life said:
Well sd-shadow did get it to flash from CM to Slim in the second post on the thread, maybe you needed to wipe more as he did.
Click to expand...
Click to collapse
Oh, yeah...I completely missed @sd_shadows' post (#2) And yeah I didn't wipe system apps so I guess that's probably why it didn't work for me. Was gonna try that later after I had made a proper backup.

I think my problem was I installed open gapps normal, I should have done pico. The normal is too large to fit in the system partition. I bet that's why it hung up on the flash fire screen. Its the same thing that happened when I tried to create a backup in the eternal storage
Sent from my KFFOWI using Tapatalk

Pond-life said:
Installing slim on stock did work. And restoring my stock back up after realising I really didn't like slim gapps.
Click to expand...
Click to collapse
So with FlashFire it is possible to flash custom roms without access to the fastboot boot command. If we can get root in 5.1.1 then we are back in business! Safestrap of course would be much better, safer.