Database Info

[SOLVED] Stuck after Recovery i9023

Hello
I have Stock Nexus S i9023
I just followed the guide here: http://forum.xda-developers.com/showthread.php?t=1007782 and ended up with this
I followed the steps, unlocked the phone
But when it came for transfering the SuperUser.zip file.
I rebooted my phone into fastboot and selected "Recovery"
Here is what i get after the Google logo with the UNlock icon.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and after trying to boot it up again, i got the following screen
How should i proceed ?
If i restart the phone, it goes and shows the "Welcome to Nexus S -- Touch the android to begin" screen.
I did not proceed from there and just powered off my phone until i get some help from here.

I had the same problem while I was following a similar guide. Here's the solution:
In Part4, after step 7, instead of booting into "recovery", run the below command:
fastboot flash recovery 3024v3-i9023.img
Then , once you see the recovery flashed confirmation, proceed with Part4 Step 8.
PS: I couldn't see the pics that you posted.

jithinsarath said:
I had the same problem while I was following a similar guide. Here's the solution:
In Part4, after step 7, instead of booting into "recovery", run the below command:
fastboot flash recovery 3024v3-i9023.img
Then , once you see the recovery flashed confirmation, proceed with Part4 Step 8.
PS: I couldn't see the pics that you posted.
Click to expand...
Click to collapse
Here are the images:
1st:
http://static.zooomr.com/images/10110396_806a835e04_o.png
2nd:
http://static.zooomr.com/images/10110398_c733ede677_o.png
I got stuck at Part 4, did not manage to even install Superuser.zip file.
Should i start again from Part 4 ?
I have disconnected the phone from the PC's USB cable. Should i start again at the fastboot screen and insert the usb cable and go to CMS prompt and run fastboot flash recovery 3024v3-i9023.img ?
Here is the fastboot mode screen
http://static.zooomr.com/images/10110423_922e67c1bc_o.png

I tried to go through the Step 4 again.Here is what i got
Code:
C:\nexusroot>adb push su-2.3.6.1-ef-signed.zip /SDCARD/su-2.3.6.1-ef-signed.zip
error: device not found
C:\nexusroot>
What should i do now ?
But my computer is reading the ADB device
http://static.zooomr.com/images/10110424_d2db200065_o.png

Ibn Saeed said:
I tried to go through the Step 4 again.Here is what i got
Code:
C:\nexusroot>adb push su-2.3.6.1-ef-signed.zip /SDCARD/su-2.3.6.4-ef-signed.zip
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\nexusroot>
What should i do now ?
But my computer is reading the ADB device
http://static.zooomr.com/images/10110424_d2db200065_o.png
Click to expand...
Click to collapse
try reinstalling stock rom...
here's the step by step method..
http://caleb1783.tistory.com/13

caleb1783 said:
try reinstalling stock rom...
here's the step by step method..
http://caleb1783.tistory.com/13
Click to expand...
Click to collapse
Ill try that and report back.
Thanks
EDIT: Part of the steps are in Korean ? Or is the english translated part enough ?
Are there supposed to be links to download in your guide ? If yes, i dont see any.
Here is what i see:

Should i go for the STock Rom from here:
http://forum.xda-developers.com/showthread.php?t=731989
Guys, im confused... How should i proceed ?

Ibn Saeed said:
Here are the images:
1st:
http://static.zooomr.com/images/10110396_806a835e04_o.png
2nd:
http://static.zooomr.com/images/10110398_c733ede677_o.png
I got stuck at Part 4, did not manage to even install Superuser.zip file.
Should i start again from Part 4 ?
I have disconnected the phone from the PC's USB cable. Should i start again at the fastboot screen and insert the usb cable and go to CMS prompt and run fastboot flash recovery 3024v3-i9023.img ?
Here is the fastboot mode screen
http://static.zooomr.com/images/10110423_922e67c1bc_o.png
Click to expand...
Click to collapse
From what I understand from those pictures, you haven't flashed the recovery. Try the step 3 again .

Ibn Saeed said:
Should i go for the STock Rom from here:
http://forum.xda-developers.com/showthread.php?t=731989
Guys, im confused... How should i proceed ?
Click to expand...
Click to collapse
Please use the stock rom from below thread:
http://forum.xda-developers.com/showthread.php?t=1063664
copy the zip to root of your sdcard (connect to computer and copy)
get into bootloader mode (Vol-Up + Power)
Flash recovery (refer my earlier post)
choose recovery
in the CWM screen choose install zip from sdcard
choose the zip file in first step
install.

jithinsarath said:
Please use the stock rom from below thread:
http://forum.xda-developers.com/showthread.php?t=1063664
copy the zip to root of your sdcard (connect to computer and copy)
get into bootloader mode (Vol-Up + Power)
Flash recovery (refer my earlier post)
choose recovery
in the CWM screen choose install zip from sdcard
choose the zip file in first step
install.
Click to expand...
Click to collapse
So i should go with installing the Stock Rom or should i proceed with the Rooting guide ?

Ibn Saeed said:
So i should go with installing the Stock Rom or should i proceed with the Rooting guide ?
Click to expand...
Click to collapse
If I were you I would do this:
1. Flash CWM recovery (fastboot flash revovery <image_name>.img)
2. Goto Recovery Mode
3. Choose Install zip from SDCard
4. Select the su....zip that you pushed earlier.
5. Install.
6. Reboot.

jithinsarath said:
If I were you I would do this:
1. Flash CWM recovery (fastboot flash revovery <image_name>.img)
2. Goto Recovery Mode
3. Choose Install zip from SDCard
4. Select the su....zip that you pushed earlier.
5. Install.
6. Reboot.
Click to expand...
Click to collapse
Thanks alot jithin, it worked and the original problem has been solved.
Now i am at the "Welcome to Nexus S" screen with out ant problem.
I flashed it with su--zip file as well.
Got the "Install from SDCARD complete" message and rebooted.
Is that all, now can i start with installing any ROM ? Should i use Rom Manager to isntall new ROMS ? I want to install Bugless Beast ROM.
Should i now go into the Nexus S and setup everything up ?

Ibn Saeed said:
Thanks alot jithin, it worked and the original problem has been solved.
Now i am at the "Welcome to Nexus S" screen with out ant problem.
I flashed it with su--zip file as well.
Got the "Install from SDCARD complete" message and rebooted.
Is that all, now can i start with installing any ROM ?
Should i now go into the Nexus S and setup everything up ?
Click to expand...
Click to collapse
wow! Good to hear that. Welcome to the ROOTED world
You now have a rooted stock Rom. You can install root only apps like Titanium Backup etc..
If you wish to install a custom Rom like CM7, then you will have to follow the above procedure, in this case download the CM7 rom to the root of your sdcard and the follow the steps I gave above. Instead of SU...zip, install the rom.zip.
Let me know how it goes
Edit:
I want to install Bugless Beast ROM.
Click to expand...
Click to collapse
I thought that was Froyo. Why would you want to downgrade from Android 2.x to 1.x?

jithinsarath said:
wow! Good to hear that. Welcome to the ROOTED world
You now have a rooted stock Rom. You can install root only apps like Titanium Backup etc..
If you wish to install a custom Rom like CM7, then you will have to follow the above procedure, in this case download the CM7 rom to the root of your sdcard and the follow the steps I gave above. Instead of SU...zip, install the rom.zip.
Let me know how it goes
Click to expand...
Click to collapse
So i follow the exact method as you have outlined here earlier:
Code:
1. Flash CWM recovery (fastboot flash revovery <image_name>.img)
2. Goto Recovery Mode
3. Choose Install zip from SDCard
4. Select the su....zip that you pushed earlier.
5. Install.
6. Reboot.
Did i understand you correctly ?
I want to try Bugless Beast first.

Did i understand you correctly ?
Click to expand...
Click to collapse
yes instead of su..zip, choose your rom..zip
I want to try Bugless Beast first.
Click to expand...
Click to collapse
Bugless bease, is AFAIK Android 1.x which is known as Froyo. Your Nexus S is by default Android 2.3.X which is called Gingerbird. If you put in Bugless Beast, I believe you will be downgrading the OS version.
A good starting guide will be this link
http://forum.xda-developers.com/showthread.php?t=1067813

jithinsarath said:
yes instead of su..zip, choose your rom..zip
Bugless bease, is AFAIK Android 1.x which is known as Froyo. Your Nexus S is by default Android 2.3.X which is called Gingerbird. If you put in Bugless Beast, I believe you will be downgrading the OS version.
A good starting guide will be this link
http://forum.xda-developers.com/showthread.php?t=1067813
Click to expand...
Click to collapse
Thanks for pointing that out
How about Matrix or NSCollab, would that be compatible?

Ibn Saeed said:
Thanks for pointing that out
How about Matrix or NSCollab, would that be compatible?
Click to expand...
Click to collapse
You would benefit from some reading mate... go through the link
http://forum.xda-developers.com/showthread.php?t=1067813
and read through the whole post. Each one would have their own preferences. For instance, I run stock android 2.3.7 on netarchy kernal. read about each ROM and then decide. Compatibility can be found from the ROM's thread in XDA
Signing off, Jithin

jithinsarath said:
You would benefit from some reading mate... go through the link
http://forum.xda-developers.com/showthread.php?t=1067813
and read through the whole post. Each one would have their own preferences. For instance, I run stock android 2.3.7 on netarchy kernal. read about each ROM and then decide. Compatibility can be found from the ROM's thread in XDA
Signing off, Jithin
Click to expand...
Click to collapse
Thanks ill go through.

Just found out that Bugless Beast is for 2.3.7
GPA v19
http://www.peteralfonso.com/2011/10/download-bugless-beast-v-gpa19-android.html

Just found another way to go around my original problem
Here is a video to solve my original issue through another way.
I thought it might help someone else.

[Guide / Tool][10/15/12] - Update to Official Jellybean Then Root or Custom ROM!

I wrote this guide do to the general lack of information for users about the Jellybean update. This guide is basic in nature and will provide you with all the tools and links you need to update from an ICS based ROM to the official JB ROM then re-root or prepare for custom ROM.
If you already have the Official JB Update simply unlock it and proceed to Section #2. This guide was intially intended for those who cannot update because of Asus stupid lock out program once you unlock.
Warning
I have tested this guide on my device multiple times and never have one single issue. I cannot say it will work perfect for you! I am not responsible for anything that goes wrong including but not limited to; A $500 brick! The economy imploding worse, Nuclear war, End of the world on 12/12/12!
Pre-requisites
Unlocked bootloader
Custom Recovery
Any version of TF700T
Windows 7 or Windows 8 PC
General Overview
Flash Asus JB update
Flash TWRP 2.2.3
Flash SuperSU or Custom ROM
Profit!
Please do not be afraid to ask for help!
This guide was written for people who need help. I didint write it for myself because I already know how to do it, lol
Donations gratefully accepted but never expected!
Please hit Thanks and Rate the thread 5 Stars
Click to expand...
Click to collapse
-Scott

Section 1 - Flash Asus JB update
Obtain the appropriate Jellybean update from the Asus Support Site HERE
Go to Downloads and pick the local / region specific update file for your device. For the intent of this guide I will focus on the US Based variant but all other devices will follow the exact same steps.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After you download the Jellybean update you must extract the zip file in the zip (I dont know why they did this!). The name of the first zip file will be "US_epad_user_10_4_4_16_UpdateLauncher.zip"
The zip file inside of that will be "US_epad-user-10.4.4.16.zip" This is the file we will flash to update to JB!
To do this open the first zip file with your zip [rogram of choice, (as you can see I use 7zip) and pull out the only other zip file in there (US_epad-user-10.4.4.16.zip).
Once you have that file copy it to you internal SD card. Although, untested, external SD should work too.
Now.... Reboot to recovery. To do this power down the device, and then Hold Volume Down and then press power untill you get a menu that says press XX key to boot to recvoery.
Once in recovery you MUST wipe data before you continue!
Now flash the ROM file you just copied like it was a plain old fashioned custom ROM or Root.zip. Just select it and flash!
Once the flash is done reboot. Dont be scared... This will take a LONG time... Maybe in upwards of 3 to 5 minutes. This is normal. Its completely rebuilding the device!
Once the device is all booted up and you are at your desktop we can proceed to Section 2.

Section 2 - Flash TWRP 2.2.2.3
First we need to obtain TWRPREcovery. You are free to use any version you want, including ClockworkMod (although I highly discourage CWM and recomend TWRP).
You can find TWRP HERE. Remember I recommend the 2.2.2.3 version. 2.3.0.0 gave me some issues.
Now that you have the file download you need to rename it to "recovery.blob" for use with my tool!
Now download the attached tool and unzip it. It contains the fastboot and ADB files you will need to flash the recovery.
Next place the recovery.blob in the folder
Turn on USB Degging in the developer menu of the device. This is very important otherwise you will be just sitting there forever, lol
Now initiate the "Recovery Install Tool.bat" file. This will reboot you to bootloader and flash the recovery for you ;c)
Done!

Section 3 - Flash SuperSU or Custom ROM
Needless to say I am partial to custom ROMS ;c) But I know some may be content with just flashing root so I will show you how to obtain the correct root file and or ROM and give a brief over view on how to flash them. This section will be pretty routine and will not contain a lot of new info for most of you!
Obtain my favorite root app, SuperSU, from HERE
Copy to storage
Reboot to recovery
Flash and Be rooted!
Same steps for a custom ROM. The best Custom ROM can be found HERE! ;c)

Section 4 - Thanks!
Thanks to Dess_troy for making TWRP for our devices!
Thanks to Chainfire for the root app!
Thanks to all the Developers on XDA that have taught me (in one way or another) everything I know!
Special Thanks to all the CleanROM users who have inspired me to push CleanROM to be the premier custom ROM for your Android Device!

Please feel free to rebuild this for the Linux or Mac platform and re-distrubute!

So, the very first step is unlocking the bootloader, correct?
Sent from my S2 Skyrocket using XDA app

scrosler said:
Pre-requisites
Unlocked bootloader
Custom Recovery
Any version of TF700T
-Scott
Click to expand...
Click to collapse
A number of people have asked and I have usually replied that it is possible to use the Asus provided UnLock tool - the one on the website that says is only compatible with ICS - with a tablet that has been updated to JB.
In short the Unlock tool works in Jellybean!
You might want to add this as an addendum to your original post.
Cheers,
Eric

i apologize for my beligerant question but if i want to try the new cwm touch recovery, do i just rename it to recovery.blob? when i downloaded it it was the usual iso. when renamed it didnt change anything so i dont wanna brick my tab. figured id ask first. thanks for the awesome walk through tho man. i really apreciate it. loving your roms. have 2.0 downloaded already. also can you pm the link to your tf300 kernel you used? i need to show off some high quadrant numbers lol

Confused...
How do I get a custom recovery on my tablet before this whole process? I've read thru some threads, do I need to be rooted first on ICS before starting this process of updating to JB? I'm not getting the official ASUS JB OTA...I've checked for the update about 500 times, I'm just not getting it.
At this point, I have an unlocked but unrooted, and wiped stock TF700T on ICS. Whats my next step?

BlastTyrantKM said:
So, the very first step is unlocking the bootloader, correct?
Sent from my S2 Skyrocket using XDA app
Click to expand...
Click to collapse
BlastTyrantKM said:
How do I get a custom recovery on my tablet before this whole process? I've read thru some threads, do I need to be rooted first on ICS before starting this process of updating to JB? I'm not getting the official ASUS JB OTA...I've checked for the update about 500 times, I'm just not getting it.
At this point, I have an unlocked but unrooted, and wiped stock TF700T on ICS. Whats my next step?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
This guide is for people who have already unlocked there device any may have had a custom ROM installed pre-JB.
You fall into a unique and rather off situation. I have never heard of some one not getting the OTA.
You could follow these steps but as a pre-step...
Download and unlock with the Asus unlock tool. Its on the same download page.
Download an ICS based recovery and use that in in place of the one noted for now. And then just start at Section 2. Then start back over at Section 1.
Basically we will put a recovery on your device in Section 2. Then start over at step 1 by applying the JB build then put a recovery back on, as it gets wiped off by Asus builds and your all set.

So I got the OTA JB update from Asus. I unlocked the boot loader using the Asus app. I downloaded and extracted US_epad-user-10.4.4.16.zip then threw it on the insternal SD card ( /storage/sdcard0 ). I rebooted with the volume key press and selected recovery. It gave me a message saying "booting recovery kernel". The next thing I see is an android on his back with a red exclamation sign.
What am I doing wrong?

beowolfschaefer said:
So I got the OTA JB update from Asus. I unlocked the boot loader using the Asus app. I downloaded and extracted US_epad-user-10.4.4.16.zip then threw it on the insternal SD card ( /storage/sdcard0 ). I rebooted with the volume key press and selected recovery. It gave me a message saying "booting recovery kernel". The next thing I see is an android on his back with a red exclamation sign.
What am I doing wrong?
Click to expand...
Click to collapse
The stock recovery will only flash firmware zips with a certain name. Rename the zip to EP201_768_SDUPDATE.ZIP and try again.

I upgraded to jb firmware and lost root. My 700T is unlocked. I thought I followed the procedure correctly but I did not get the message correct message when I ran the program. My device is not rooted. Can you tell me what I might be doing wrong.

yes you lose root. this will make your tf700 like the factory jellybean firmware which is not rooted. go back to op and keep reading. each section builds on the previous. first get the jellybean firmware. im still playing with mine stock its so damn smooth. then you flash a custom recovery using his tool. then you flash the zip which gives you root. then i would make a back up so you can always get back to that point. then you can look into custom roms like scotts sweet clean rom for tf700 series
joseph473 said:
I upgraded to jb firmware and lost root. My 700T is unlocked. I thought I followed the procedure correctly but I did not get the message correct message when I ran the program. My device is not rooted. Can you tell me what I might be doing wrong.
Click to expand...
Click to collapse

beowolfschaefer said:
So I got the OTA JB update from Asus. I unlocked the boot loader using the Asus app. I downloaded and extracted US_epad-user-10.4.4.16.zip then threw it on the insternal SD card ( /storage/sdcard0 ). I rebooted with the volume key press and selected recovery. It gave me a message saying "booting recovery kernel". The next thing I see is an android on his back with a red exclamation sign.
What am I doing wrong?
Click to expand...
Click to collapse
If you have the JB Update why ware you trying to install it again? Proceed to section #2. You just need the Recovery and the Root portion. Skip step 1.
joseph473 said:
I upgraded to jb firmware and lost root. My 700T is unlocked. I thought I followed the procedure correctly but I did not get the message correct message when I ran the program. My device is not rooted. Can you tell me what I might be doing wrong.
Click to expand...
Click to collapse
To me it looks like you are trying to run the batch file without extracting the contents.

Thank you for this guide! Although it took me some time to understand it as I was on non-rooted/locked JB stock rom.
---------- Post added at 01:34 PM ---------- Previous post was at 01:29 PM ----------
scrosler said:
If you have the JB Update why ware you trying to install it again? Proceed to section #2. You just need the Recovery and the Root portion. Skip step 1.
Click to expand...
Click to collapse
I actually had similar problem as this guy. I was already on JB and the guide is made for people that are on ICS.

scrosler said:
To me it looks like you are trying to run the batch file without extracting the contents.
Click to expand...
Click to collapse
I am using a borrowed PC. I am a Mac user so forgive my ignorance. But when I look at the folder with Scott's Tool in it it looks like everything is extracted.

scrosler said:
If you have the JB Update why ware you trying to install it again? Proceed to section #2. You just need the Recovery and the Root portion. Skip step 1.
Click to expand...
Click to collapse
I actually tried this last night with no luck. I guess it was something funny with my desktop in that it couldn't connect using fast boot. Anyway I brought it in to work and ran it here and everything is fine. I am going to throw your stock/root rom on it now. Thanks for your help!

CWM-SuperSU-v0.96.zip
Hello,
thanks a lot for the guide, it is really clear and detailed.
My question is something I did not find on the previous question and it is more a double check to be sure I am not doing something I should not.
You say to install SU with the package copied on the internal SD, and you added a link to the SU thread. in this thread, the only SU as a package you can find is CWM-SuperSU-v0.96.zip, as it is CWM, will it work if I install it with TWRP? or there is special settings in this package that will not be recognised by TWRP?
Thanks in advance for your help
Regards

[GUIDE] Unroot / Unbrick, Flash official stock firmware on Galaxy SII Plus GT-I9105/P

Here is a full guide on how to unroot and back to official stock firmware for Galaxy SII Plus GT-I9105/P. It is useful also if you soft brick your phone​
!!!BE SURE THAT YOU ARE FLASHING THE RIGHT FIRMWARE FOR YOUR VARIANT!!!​Do it on your own responsibility! if you follow this guide properly u will be on the safe side ​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Before we proceed, make sure:
1-You have installed your Samsung Galaxy SII Plus GT-I9105/P USB drivers on your PC (the easiest way is to install Kies).
2-You need to enable USB debugging mode (Settings>Developer options) which is deactivated by default.
3-Your SII Plus GT-I9105/P should have 70-80% charge remaining.
4-Your SII Plus GT-I9105/P should be factory unlocked.
5-Backup your important data like Call logs, SMS and other data stored in phone memory in case if anything goes wrong, your data is not hurt.
6-Make sure that kies program is not running & disable antivirus.
This guide is only for Galaxy SII Plus GT-I9105/P. So don’t bother to try it on other devices.
How to do it:
Step 1) Turn OFF your mobile and go to Download Mode by pressing and holding the Volume Down + Home Buttons together for few seconds followed by Power button then proceed with volume up. (For some phones, when you see the construction Android robot and a triangle, press Power again to confirm to enter into Download Mode).
Step 2) Now open ODIN on your PC and connect your Galaxy SII Plus GT-I9105/P to your computer.
Step 3) Once your phone is successfully connected to your PC, the ID:COM box on ODIN will turn blue and will show the COM port number.
Step 4) unzip the downlowded file, u will get a Home.tar file.
Step 5) click on pda in odin (if odin 3.09 choose AP) and choose the file "xxxx.tar.md5"
Step 6) check "Auto Reboot" and "F. Reset Time" options and make sure that "Re-Partition" is unchecked
!!!!DO NOT CHECK "Nand Erase All" IN ANY WAY!!!!
Step 7) Click on Start button in ODIN window to start the installation process. The process will take few minutes to complete.
DO NOT UNPLUG USB CABLE WHILE EXECUTING THE PROCESS, YOU MAY BRICK YOUR PHONE!
Step 8) When the installation is completed, you read a "Pass". your phone will restart (first boot will take a longer time so don't panic) :good:
It is recommended to make hard reset after flashing to have a fresh official firmware ​
NOTE: I prefer to perform data and cache wipe before and after flashing stock firmware.
NOTE 1: If you have a corrupted partition table, (Odin says: "there is no pit partition" or "Re-Partition operation failed"), flash pit file for your device (attached) (put it in pit window) with your firmware, in this case "Re-Partition" must be marked.
NOTE 2: If it happen, and your new csc doesnt stick (the product code), usually a hard reset can solve this issue, or root it again and use third party application like "csc changer".
NOTE 3: For warranty reason, and if you have rooted your SII plus, you must reset the binary counter. Some users report that "Triangle away" application works on SII plus, do it when you still rooted and you have stock kernel and recovery.
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Try another computer.
Download Links:​Odin
For Latest firmwares see second post​​
Don't forget to press THANKS & RATING buttons!

Firmwares links:
I9105 samsung-update.com
I9105P samsung-update.com

Reserved

Thanks for the Contribution brother

Step 5) click on pda in odin (if odin 3.09 choose AP) and choose the file "Home.tar"
Click to expand...
Click to collapse
Instruction is pretty clear, except step 5. I downloaded the correct rom, bit the zip-file doesn't contain a Home.tar at all?
Did I miss something here?

Bart-NL said:
Instruction is pretty clear, except step 5. I downloaded the correct rom, bit the zip-file doesn't contain a Home.tar at all?
Did I miss something here?
Click to expand...
Click to collapse
choose the xxxxxxxx_xxxxxxxx.tar.md5 file

Bart-NL said:
Instruction is pretty clear, except step 5. I downloaded the correct rom, bit the zip-file doesn't contain a Home.tar at all?
Did I miss something here?
Click to expand...
Click to collapse
Just extract the whole zip file and you will get what u need and what it means
Sent from my GT-I9105P using XDA Premium 4 mobile app

thanks but....
why 912 MB?
does it contain stock rom?or another rom?
if it's same stock rom lots of people already have it please give us only home.tar file. it takes me 12 houers to download and host won't let resume downloads and my pc can't maintain that much (but thanks anyway that's my problem)
-please someone tell what that 912MB file in third post contains?
another question about unrooting: i flashed CWM recovery via odin and then two files flashed with recovery(volume up+home+power) to root how can i restore them?(i don't care about triangle or warranty)
another issue:according to this post >> [GUIDE] [4.1] How to root and install CWM by panda00 if someone doesn't care about binary counter unrooting is just about flashing stock frimware with odin, what about that?
what's my problem?:i rooted my phone to use more storage space by deleting unnecessary system apps and moving my apps to system app folder instead(which i failed) but main problem is after rooting and wiping everything 249MB is mising
"sorry for long noob question and bad english and thanks"

vahid8910 said:
why 912 MB?
does it contain stock rom?or another rom?
if it's same stock rom lots of people already have it please give us only home.tar file. it takes me 12 houers to download and host won't let resume downloads and my pc can't maintain that much (but thanks anyway that's my problem)
-please someone tell what that 912MB file in third post contains?
another question about unrooting: i flashed CWM recovery via odin and then two files flashed with recovery(volume up+home+power) to root how can i restore them?(i don't care about triangle or warranty)
another issue:according to this post >> [GUIDE] [4.1] How to root and install CWM by panda00 if someone doesn't care about binary counter unrooting is just about flashing stock frimware with odin, what about that?
what's my problem?:i rooted my phone to use more storage space by deleting unnecessary system apps and moving my apps to system app folder instead(which i failed) but main problem is after rooting and wiping everything 249MB is mising
"sorry for long noob question and bad english and thanks"
Click to expand...
Click to collapse
the 4.2.2 zip is 912 MB, the firmware is arround 1.3 GB (after unzipping, the tar.md5 file)
yes it is a pure stock official rom, it contains, sboot, system, recovery, kernel, cache, param, radio........
you can unroot back to stock by flashing the stock firmware posted in third post!
for other issues, post in rooting thread :good:

Go back to the stock !!
hey there I have I9105XXUBMH4_I9105OXEBMH3_SER.zip file it just contains the pda file so I wanna reflash the stock rom (cuz i'm already running 4.2.2 by flashing this pda) can I just reflash the rom bly flashing this pda file ??
plz answer me as fast as possible.
thx

Bilal.Android said:
hey there I have I9105XXUBMH4_I9105OXEBMH3_SER.zip file it just contains the pda file so I wanna reflash the stock rom (cuz i'm already running 4.2.2 by flashing this pda) can I just reflash the rom bly flashing this pda file ??
plz answer me as fast as possible.
thx
Click to expand...
Click to collapse
Sure you can, but why don't you factory reset?

Raven_Yen said:
Sure you can, but why don't you factory reset?
Click to expand...
Click to collapse
My phone is now slow btw my phone is rooted is it work ??
Sent from my GT-I9105 using XDA Premium 4 mobile app

Bilal.Android said:
My phone is now slow btw my phone is rooted is it work ??
Sent from my GT-I9105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you want to go to clean stock without root, you need to flash through Odin. I am not aware of any unroot method for i9105(P) without using Odin yet.
Or you can factory reset if you still want a rooted status (I think the root still stays if you factory reset, correct me if I'm wrong)
Make sure you backup important datas, files, pictures in your internal storage before factory reset / re-flash firmware.

Raven_Yen said:
If you want to go to clean stock without root, you need to flash through Odin. I am not aware of any unroot method for i9105(P) without using Odin yet.
Or you can factory reset if you still want a rooted status (I think the root still stays if you factory reset, correct me if I'm wrong)
Make sure you backup important datas, files, pictures in your internal storage before factory reset / re-flash firmware.
Click to expand...
Click to collapse
Yes you are right the root even stays if you factory reset the device. Well after formatting everything ,stock rom has to be flashed by using odin after that you will find the binary counter increased. It will be cleared by sing TRIANGLE AWAY app. By this you can easily bring the binary counter to 0. By doing all this you will get the status stock

android.zealot.fervor said:
Yes you are right the root even stays if you factory reset the device. Well after formatting everything ,stock rom has to be flashed by using odin after that you will find the binary counter increased. It will be cleared by sing TRIANGLE AWAY app. By this you can easily bring the binary counter to 0. By doing all this you will get the status stock
Click to expand...
Click to collapse
I never remove binary counter in stock (rooted) ROM before.
Should we Triangle Away first in rooted stock, then flash clean stock ROM using Odin and get official+zero binary after that?
(Or pre-rooted stock ROM )

android.zealot.fervor said:
Yes you are right the root even stays if you factory reset the device. Well after formatting everything ,stock rom has to be flashed by using odin after that you will find the binary counter increased. It will be cleared by sing TRIANGLE AWAY app. By this you can easily bring the binary counter to 0. By doing all this you will get the status stock
Click to expand...
Click to collapse
But the thing is, wouldn't you need to re-root again to use triangle away? Hence, considering you want to return to stock, you would have to flash a stock firmware via odin to unroot. But then again, it would increase the binary counter?

Raven_Yen said:
I never remove binary counter in stock (rooted) ROM before.
Should we Triangle Away first in rooted stock, then flash clean stock ROM using Odin and get official+zero binary after that?
(Or pre-rooted stock ROM )
Click to expand...
Click to collapse
You need root to use triangle away. After using, just flash stock directly. Don't go into cwm or it will trigger the counter again
Sent from my GT-I9105P using XDA Premium 4 mobile app

Brian_SGW_CM9 said:
You need root to use triangle away. After using, just flash stock directly. Don't go into cwm or it will trigger the counter again
Sent from my GT-I9105P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ah, that's my guess and you confirmed for me.
I ended up having binary counter at 5 after upgrading CM11 from stock 4.2.2.
Does the previous binary counter (before re-flashing stock 4.2.2) counted inside?
I don't recall entering recovery mode that much in CM11.

wipe everything and factory reset via recovery
flash stock rom via odin
thats my way without triangle away..

Not sure if my phone is unlocked,,,how can I tell? The *# thing in dialer doesnt work

[SOLVED] Stuck in DOWNLOAD mode after failed ODIN frimware update [SOLVED]

For those in need I have just received another confirmation that my solution works. Here are the details!
Sooo... let me explain before you begin recovery (and it will work, believe me!). 1) worry not!) 2).... the whole wrong comes from Odin. No matter what version of Odin you're using (and I used 3.10.6) and what firmware are you trying to flash (original, not so original, with MD5 or without) Odin will **** up your phone and get you stuck to the bloody "Downloading" screen. For me it happened after having a custom ROM installed and trying to revert to Vodafone UK original rom (namely "G920FXXU1AOCZ_G920FVFG1AOC4_G920FXXU1AOCW_HOME.tar.md5"). DITTO! On some S6s ODIN will ruin your life and you can check that there are other similar horror stories around.
HOW DO I FIX THIS?
Well... pretty simple! Thank God! The idea is that once you reboot you phone and it shows as stuck in "Download" screen you have to flash the "recovery.img" that is actually inside the ".TAR" or ".TAR.MD5" file you have just flashed.
To do so you have to actually put the "recovery.img" you have just extracted from the ".TAR.MD5" (or just ".TAR) into a flashable file that ODIN understands. Yes, your'e right, in a blah-blah.tar.md5 or blah-blah.tar file.
To do so I have downloaded and installed 7Zip (since it's able to mangle .tar files as opposed to WinRAR) and also downloaded a "pristine" .tar file like the TWRP recovery (e.g. twrp-2.8.6.2-zeroflte.img.tar). The TWRP fil actually contains in it a modified "recovery.img" file.
Further on I have created a copy of the TWRP recovery file and named it "my-recovery.img.tar" (or call it whatever it fits you), opened it up in 7Zip and just dragged the "recovery.img" (you have extracted previously from the exact firmware ODIN has ruined at flashing last time) over the existing one in the archive. Click OK when 7Zip will prompt you that you are going to overwrite the existing "recovery.img" and you are done.
Now simply flash the "my-recovery.img.tar" via ODIN to you S6 and once done you'll have a functional phone with the latest firmware!
DON'T FORGET to go into the newly created recovery and factory reset! For your own safety the CSC has to be aligned from one old firmware to the new one.
Here is the recovery image for Italy (Vodafone) 5.0.2 G920FXXU1AODG to get you out of the trouble with the latest firmware (get it here):
my-recovery.img.tar
ATTENTION
While the above described procedure will get you out of trouble caused by ODIN and out of the "Downloading" mode it will not actually solve the whole issue. I just discovered myself that once I tried again the same ODIN firmware re-flashing with a different firmware I got stuck to the same nightmare.
The solution is, once you go through the procedure I have described, to open up Samsung Smart Switch (the new "KIES" for S6 and S6 Edge), go to "MORE" --> "Emergency software recovery and initialization" and perform that task! I will actually re-write the latest firmware you have flashed to your phone BUT will also solve the ODIN issues. On my phone, after doing so, I was able to flash this latest Vodafone Italy I have uploaded here.
The "Emergency software recovery and initialization" procedure has to be completed BEFORE you finish the setup procedure of your S6, you know the "WiFi" / Accounts / blah, blah (after flashing the firmware) and not afterwards. It least so I discover it to work.
Please let me know how this tutorial worked for you.

Will this prosedure trip KNOX?

It will not trip KNOX because it is a signed firmware that you're flashing with Odin.

Everything worked fine but not the Smart switch part. My device doesn't show up here in the list. How do I proceed?

Here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

h3llboy911 said:
Here. View attachment 3321069
Click to expand...
Click to collapse
Select the right tab and fill in there your phone's model after it confirms fill in your s/n number (phone's)... youll find the details on phonr box

This is what it says when I select the right tab. Looks like my device i snot supported. Any alternatives? I want to able to flash roms again.

Just download the rom from sammobile and flash it using odin. Beware that reactivation lock must be off!

AskinSavascisi said:
Just download the rom from sammobile and flash it using odin. Beware that reactivation lock must be off!
Click to expand...
Click to collapse
Why are we facing this flash fail error first of all? Is it because I had reactivation lock tuned on?

If u have it on, u wont be able to use odin... i had the same issue thats why i went with smart switch but it seems u have a problem with your device Model (not supported)... smart switch doesnt care if your reactivation lock is off or on

AskinSavascisi said:
If u have it on, u wont be able to use odin... i had the same issue thats why i went with smart switch but it seems u have a problem with your device Model (not supported)... smart switch doesnt care if your reactivation lock is off or on
Click to expand...
Click to collapse
I don't remember turning reactivation lock on before flashing with odin. I googled about the issue and it seems like it's a partition issue and we need to flash the correct .pit file to fix the issue. Till then every firmware that is flashed is going to fail at hidden.img.
---------- Post added at 07:39 PM ---------- Previous post was at 07:38 PM ----------
and as the OP has stated, Smart Switch fixes this partition issue but sadly my device is not supported by it.
---------- Post added at 07:41 PM ---------- Previous post was at 07:39 PM ----------
This what the OP has stated.
While the above described procedure will get you out of trouble caused by ODIN and out of the "Downloading" mode it will not actually solve the whole issue. I just discovered myself that once I tried again the same ODIN firmware re-flashing with a different firmware I got stuck to the same nightmare.
Click to expand...
Click to collapse

AskinSavascisi said:
Just download the rom from sammobile and flash it using odin. Beware that reactivation lock must be off!
Click to expand...
Click to collapse
Just to confirm, does flashing rom from sammobile using Odin will wipe phone? I know it will not trip knox, but is there any chance to flash official rom without wiping it?

Ollve said:
Just to confirm, does flashing rom from sammobile using Odin will wipe phone? I know it will not trip knox, but is there any chance to flash official rom without wiping it?
Click to expand...
Click to collapse
It doesn't wipe your phone, but it's recommended that you factory reset your phone before flashing.

h3llboy911 said:
It doesn't wipe your phone, but it's recommended that you factory reset your phone before flashing.
Click to expand...
Click to collapse
The point is I'm still on OCV rom (not branded) and I'd like to flash at least OE2-4 with ram fixes and possibly root right after update. Then wipe when we get official 5.1.1.
Waiting for OTA is so pointless in this case...

h3llboy911 said:
It doesn't wipe your phone, but it's recommended that you factory reset your phone before flashing.
Click to expand...
Click to collapse
If its the same pda not really needed

AskinSavascisi said:
If its the same pda not really needed
Click to expand...
Click to collapse
Different, from OCV to OE3/OE4. So probably worth to try without wipe and in case I get FC/bootloops - wipe.

ollve said:
different, from ocv to oe3/oe4. So probably worth to try without wipe and in case i get fc/bootloops - wipe.
Click to expand...
Click to collapse
???

Well, thanks for this

I was trying to install TWRP and my phone got soft bricked. I tried flashing the Trinidad and Tobago firmware that I had and got this "hidden.img fail!" error.The solution to recover the phone is well-explained by the OP and it works like charm.
A lot of people had faced the same issue over the S6 and S6 edge forums
-Some people told that the phones partitions are messed up and I needed to flash the correct PIT file to be able to flash any FW again. Otherwise it will fail every time.
-Some people told that I had "Reactivation lock"(Find my Samsung's feature) enabled and that's why I am facing the error. (In that case, we get a different error while flashing via ODIN or factory reseting, not hidden.img failed error.
The error is because of the FIRMWARE you are flashing is not supported. Yes! I recovered my phone by flashing the latest Indian firmware and it worked like charm. So the lesson here is, EVEN WHEN THE DEVICE MODEL IS SAME(925I), THE FIRMWARES FROM DIFFERENT COUNTRIES ARE NOT COMPATIBLE WHEN FLASHED VIA ODIN. (At least in my case and a few other who confirmed)
PS: The same firmware works if done by FLASHFIRE but ODIN fails.

dehnhaide said:
For those in need I have just received another confirmation that my solution works. Here are the details!
Sooo... let me explain before you begin recovery (and it will work, believe me!). 1) worry not!) 2).... the whole wrong comes from Odin. No matter what version of Odin you're using (and I used 3.10.6) and what firmware are you trying to flash (original, not so original, with MD5 or without) Odin will **** up your phone and get you stuck to the bloody "Downloading" screen. For me it happened after having a custom ROM installed and trying to revert to Vodafone UK original rom (namely "G920FXXU1AOCZ_G920FVFG1AOC4_G920FXXU1AOCW_HOME.tar.md5"). DITTO! On some S6s ODIN will ruin your life and you can check that there are other similar horror stories around.
HOW DO I FIX THIS?
Well... pretty simple! Thank God! The idea is that once you reboot you phone and it shows as stuck in "Download" screen you have to flash the "recovery.img" that is actually inside the ".TAR" or ".TAR.MD5" file you have just flashed.
To do so you have to actually put the "recovery.img" you have just extracted from the ".TAR.MD5" (or just ".TAR) into a flashable file that ODIN understands. Yes, your'e right, in a blah-blah.tar.md5 or blah-blah.tar file.
To do so I have downloaded and installed 7Zip (since it's able to mangle .tar files as opposed to WinRAR) and also downloaded a "pristine" .tar file like the TWRP recovery (e.g. twrp-2.8.6.2-zeroflte.img.tar). The TWRP fil actually contains in it a modified "recovery.img" file.
Further on I have created a copy of the TWRP recovery file and named it "my-recovery.img.tar" (or call it whatever it fits you), opened it up in 7Zip and just dragged the "recovery.img" (you have extracted previously from the exact firmware ODIN has ruined at flashing last time) over the existing one in the archive. Click OK when 7Zip will prompt you that you are going to overwrite the existing "recovery.img" and you are done.
Now simply flash the "my-recovery.img.tar" via ODIN to you S6 and once done you'll have a functional phone with the latest firmware!
DON'T FORGET to go into the newly created recovery and factory reset! For your own safety the CSC has to be aligned from one old firmware to the new one.
Here is the recovery image for Italy (Vodafone) 5.0.2 G920FXXU1AODG to get you out of the trouble with the latest firmware (get it here):
my-recovery.img.tar
ATTENTION
While the above described procedure will get you out of trouble caused by ODIN and out of the "Downloading" mode it will not actually solve the whole issue. I just discovered myself that once I tried again the same ODIN firmware re-flashing with a different firmware I got stuck to the same nightmare.
The solution is, once you go through the procedure I have described, to open up Samsung Smart Switch (the new "KIES" for S6 and S6 Edge), go to "MORE" --> "Emergency software recovery and initialization" and perform that task! I will actually re-write the latest firmware you have flashed to your phone BUT will also solve the ODIN issues. On my phone, after doing so, I was able to flash this latest Vodafone Italy I have uploaded here.
The "Emergency software recovery and initialization" procedure has to be completed BEFORE you finish the setup procedure of your S6, you know the "WiFi" / Accounts / blah, blah (after flashing the firmware) and not afterwards. It least so I discover it to work.
Please let me know how this tutorial worked for you.
Click to expand...
Click to collapse
i simply cant work out this line.. after extracting the firmware file, i only get 1 xxxxxx.tar.md5
how do i actually change the recovery thing?

Starting from stock 4.2.2 UK Tab 2 p5110

Hi guys,
Apologies first of all as I'm sure this has been asked over and over again but I'm still struggling to find a concrete route/guide to running custom roms starting from a stock device (Tab 2 10" P5110 JB 4.2.2).
As far as I understood I should do the following:
1. Install CF-Autoroot - However on CF website I read:
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !
Do I need to worry about the above or can I proceed to install the CF-autoroot via Odin?
2. Install custom recovery as above method leaves with stock recovery - Question here is what is the best way to proceed at this point? Install recovery via rom manager or another method (PC Odin etc) ?
3. Install custom rom and enjoy and improved device
Please if someone could clarify the steps I need to take (exact file versions etc) from a fully stock 10" Tab 2 running 4.2.2 it would be greatly appreciated. Or link me to what I'm after in case I've missed this!
All the best,
GalaxyDude
(Happy Christmas all!)

Galaxydude1 said:
Hi guys,
Apologies first of all as I'm sure this has been asked over and over again but I'm still struggling to find a concrete route/guide to running custom roms starting from a stock device (Tab 2 10" P5110 JB 4.2.2).
As far as I understood I should do the following:
1. Install CF-Autoroot - However on CF website I read:
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !
Do I need to worry about the above or can I proceed to install the CF-autoroot via Odin?
2. Install custom recovery as above method leaves with stock recovery - Question here is what is the best way to proceed at this point? Install recovery via rom manager or another method (PC Odin etc) ?
3. Install custom rom and enjoy and improved device
Click to expand...
Click to collapse
1st, it will only root your mobile, if your purpose is to stay on stock and just delete the bloat wares. and run modded apps. you're good to go
http://forum.xda-developers.com/showthread.php?t=1957165
http://forum.xda-developers.com/showthread.php?t=2203309
just check you're using the file meant for your device only. this thread has a detailed view. and no, its safe as long as you're using the files meant exactly for your device.
2nd installing a custom recovery is the first choice and the best and smartest thing to do, cause if after rooting you did something stupid with the system files, then all your data might be lost, custom recovery helps you keep complete nandroid backup of your device which means almost everything is backed up (except media and external memory card), lets you flash custom rom and in case anything goes wrong, you access the custom recovery and bam, restore your backup, and you're back at the original state. or flash your new custom rom
3. yes install a custom rom after you backup your stock factory rom.
remember taking backup at every step from here on onward is the first rule.
good luck and have fun on xda

Hi Billysam,
Thanks for the speedy reply
I'm aiming to eventually run a nice custom rom but just want to get the rooting and custom firmware down first so as you mention I can do a full nandroid backup before moving on.
I had a look at the link you posted but you're right that leaves you with stock recovery which would be fine if I wasn't going to install a custom rom.
I found http://forum.xda-developers.com/showthread.php?t=1722745
So now I've got:
Odin 3.0.7
philz_touch_5.03.7-p5110.tar.md5
Superuser-3.1.3-arm-signed.zip
Was going to install the above via Odin and then do a full backup, does that sound about right?
Cheers again!
Galaxydude1

Galaxydude1 said:
Hi Billysam,
Thanks for the speedy reply
I'm aiming to eventually run a nice custom rom but just want to get the rooting and custom firmware down first so as you mention I can do a full nandroid backup before moving on.
I had a look at the link you posted but you're right that leaves you with stock recovery which would be fine if I wasn't going to install a custom rom.
I found http://forum.xda-developers.com/showthread.php?t=1722745
So now I've got:
Odin 3.0.7
philz_touch_5.03.7-p5110.tar.md5
Superuser-3.1.3-arm-signed.zip
Was going to install the above via Odin and then do a full backup, does that sound about right?
Cheers again!
Galaxydude1
Click to expand...
Click to collapse
Philz recovery is fine, but some custom roms requires twrp recovery, both are good. check which rom you're going to try and see if it says needs twrp, download that, if not philz is safe too and it's not much hard to switch.
Superuser app, you won't need unless the custom rom you're going to install doesn't have one already. most do. just get custom recovery installed, find a good custom rom, for your device, read instructions and other members who already tried it. don't rush. backup first.
small note- please click reply and then type your msg, it will quote and send me a notification as well. if you don't quote or don't hit thinks, I might not even get notified and see your msg. cheers

billysam said:
Philz recovery is fine, but some custom roms requires twrp recovery, both are good. check which rom you're going to try and see if it says needs twrp, download that, if not philz is safe too and it's not much hard to switch.
Superuser app, you won't need unless the custom rom you're going to install doesn't have one already. most do. just get custom recovery installed, find a good custom rom, for your device, read instructions and other members who already tried it. don't rush. backup first.
small note- please click reply and then type your msg, it will quote and send me a notification as well. if you don't quote or don't hit thinks, I might not even get notified and see your msg. cheers
Click to expand...
Click to collapse
No problem at all, I'd actually deleted the requote to save spam as I assumed you'd be notified auto as you'd contributed
Thanks for the info, on the back of what you've said I think I'll put on PhilsRecovery as I've got it downloaded for my specific model, do a full backup and then can I use Rom manager to install TWRP via the app?
Kind regards,
Galaxydude1

Galaxydude1 said:
Thanks for the info, on the back of what you've said I think I'll put on PhilsRecovery as I've got it downloaded for my specific model, do a full backup and then can I use Rom manager to install TWRP via the app?
Click to expand...
Click to collapse
Yes, go with that. and you can change to twrp with rom manager. but most of the custom rom threads have the recoveries mentioned there and most of the time you will find updated once here on the page. check this page
http://forum.xda-developers.com/galaxy-tab-2/10-inch-development
this is the place you will find all custom roms for your device and updated information. wherever you see P51xx , that rom works for your device as well.

billysam said:
Yes, go with that. and you can change to twrp with rom manager. but most of the custom rom threads have the recoveries mentioned there and most of the time you will find updated once here on the page. check this page
http://forum.xda-developers.com/galaxy-tab-2/10-inch-development
this is the place you will find all custom roms for your device and updated information. wherever you see P51xx , that rom works for your device as well.
Click to expand...
Click to collapse
Thanks for your advice :good:
One thing I just realised though is if you have to be rooted in order to do a full nandroid backup I'll need to flash the recovery with Odin and then install the superuser file zip from recovery before the backup will work.
Am I right in thinking the above?
Cheers again.

Galaxydude1 said:
Thanks for your advice :good:
One thing I just realised though is if you have to be rooted in order to do a full nandroid backup I'll need to flash the recovery with Odin and then install the superuser file zip from recovery before the backup will work.
Am I right in thinking the above?
Cheers again.
Click to expand...
Click to collapse
Get into recovery first and try to backup if it does, you're fine, if it doesn't you can flash superuser zip inside recovery and try then backup.
it's not that risky.

billysam said:
Get into recovery first and try to backup if it does, you're fine, if it doesn't you can flash superuser zip inside recovery and try then backup.
it's not that risky.
Click to expand...
Click to collapse
I just gave it a try but looks like some driver issue going on with PC (Windows 10):
http://imgur.com/5RKLSp6
Just hangs when trying to install drivers (have latest Samsung USB drivers installed) and I've checked and Kies wasn't running, going to try on my Windows 7 PC and see if it's any better. Is there anything else I need installed I'm missing? Should have ADB stuff installed as recently used this laptop to connect to Fire TV.
Will keep thread updated.
Thanks again,
Galaxydude.

Galaxydude1 said:
I just gave it a try but looks like some driver issue going on with PC (Windows 10):
http://imgur.com/5RKLSp6
Just hangs when trying to install drivers (have latest Samsung USB drivers installed) and I've checked and Kies wasn't running, going to try on my Windows 7 PC and see if it's any better. Is there anything else I need installed I'm missing? Should have ADB stuff installed as recently used this laptop to connect to Fire TV.
Will keep thread updated.
Thanks again,
Galaxydude.
Click to expand...
Click to collapse
it shows device connected at com3 in odin. if its blue and shows com3 or any other com, you're connected so the drivers are good, have you enabled usb debugging in settings? if not enable it.
it's getting hanged at installing drivers or is it trying to get update from the internet? might be issue with windows 10. check on windows 7

billysam said:
it shows device connected at com3 in odin. if its blue and shows com3 or any other com, you're connected so the drivers are good, have you enabled usb debugging in settings? if not enable it.
it's getting hanged at installing drivers or is it trying to get update from the internet? might be issue with windows 10. check on windows 7
Click to expand...
Click to collapse
Yeah I managed to get the drivers to install out of download mode but I'm still getting a blue com with it connected and usb debugging enabled.
Going to try on W7 later and post what happens.
All the best.

billysam said:
it shows device connected at com3 in odin. if its blue and shows com3 or any other com, you're connected so the drivers are good, have you enabled usb debugging in settings? if not enable it.
it's getting hanged at installing drivers or is it trying to get update from the internet? might be issue with windows 10. check on windows 7
Click to expand...
Click to collapse
So after reading multiple posts of people saying the blue com status was the same as yellow (different due to software version) I decided to go ahead and try CF-Autoroot with my Tab 2 4.2.2 JB stock and this was SUCCESSFUL:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://imgur.com/VQxjInS
So for those of you wondering if it will work on latest stock firmware it does
Now I'm going to try get a custom recovery installed so I can do a full nandroid backup before I play with any roms.
Thanks all!
Galaxydude1