Database Users

[Guide] Return to Stock from Original CWM Nandroid Backup

This guide is for those that require to return COMPLETLEY to stock (out of the box) and your firmware version is not yet available for download.
You must be; rooted, CWM Recovery and have an original nandroid backup (made after first root, and before flashing any custom ROM or non-regional firmware other than recovery or modem)
Australian Optus Nandroid :
* [email protected] has been kind enough to upload here
* You will need to Triangle Away, so begin at step #1
* I have not personally tested this nandroid, only my own
Australian Vodafone Nandroid :
* [email protected] has been kind enough to upload here
* You may need to Triangle Away, so begin at step #1
* Again, I have not personally tested this nandroid, only my own
Modem & Stock Recovery
* Not backup by CWM, thus you may need to restore your original
Modem Collection :
* [REF] Galaxy S3 Modem / Radio Collection (I9300 & I9300T ONLY) CWM & Odin Flashable
Android System Recovery 3e :
* CWM_Stock_I9300_Recovery.zip attached
* Stock recovery is the SAME between I9300 or I9300T versions
[Guide] Return to Stock from Original CWM Backup - No firmware released for download
Requirements:
1. Have a nandroid backup of your original stock firmware
2. Root & CWM Recovery
3. Triangle Away app
4. SU-BusyBox-CWM_Manager-Uninstaller.zip (wipes SU binary, SuperUser, BusyBox and CWM Manager v3.50/3.55/3.60)
5. CWM_I9300_Stock_Recovery.zip
6. CheckFus Downloader app to check Product Code (SGS2 dialer code *2767*4387264636# does not work)
7. CWM flashable modem.zip (if not original baseband version)
METHOD:
1. Use Triangle Away app to reset binary download counter
2. Boot into CWM Recovery
3. Restore "original" nandroid backup (ensure the name has not been modified or you may experience md5 mismatch)
4. Reboot & check for and uninstall any remaining User apps that require SU
5. Boot in CWM Recovery
6. Flash modem.zip (only if baseband is not original)
If you did not Triangle Away before making the original backup, your binary flash counter may not be restored as zero, so reboot and reset before proceeding to step#7
Click to expand...
Click to collapse
7. Flash SU-BusyBox-CWM_Manager-Uninstaller.zip
8. Flash CWM_I9300_Stock_Recovery.zip
9. Factory reset
10. Reboot system
11. Check settings > about device > status > device status > scanning............... Normal (This may take a few minutes)
12. Sign into Google Play & install CheckFus app. Product code should be correct
If returning for warranty:
13. Delete all contents of internal sdcard "phone"
14. Factory reset again and power off
All tested on my own device
Hope this helps some Hit THANKS if it has
Added Disclaimer: All your own risk. I am not responsible for anything you may try here. I didn't make you do it, blah blah blah

Thanks for this, really appreciate it!
I found a typo in one of your sentences:
Baseband I9300DTULE6 can be found here:
Click to expand...
Click to collapse
I really think you meant I9300TDULE6

kelvinyap9 said:
Thanks for this, really appreciate it!
I found a type in one of you sentences:
I really think you meant I9300TDULE6
Click to expand...
Click to collapse
Correcting...
Cheers
Sent from my GT-I9300T using xda premium

Anyway, I'm at the process of getting ready to do a NANDROID backup (already put an SD card in the phone).
As I'm aware, the stock recovery doesn't do NANDROID backups. Would I need to flash CWM (Chainfire one) via ODIN before doing so?
UPDATE: Never mind, NANDROID is a CWM feature x)

kelvinyap9 said:
Anyway, I'm at the process of getting ready to do a NANDROID backup (already put an SD card in the phone).
As I'm aware, the stock recovery doesn't do NANDROID backups. Would I need to flash CWM (Chainfire one) via ODIN before doing so?
Click to expand...
Click to collapse
Recommend it. Just follow Chainfire guide exactly.
Copy the backup found in clockworkmod folder to PC for safe keeping.
Once rooted, search for EFS Backup Pro and copy the backup to PC too. CWM will not back this up either. If this every becomes corrupted (and no backup) = iPod (no cellular network)
Sent from my GT-I9300T using xda premium

Thanks man, that's what I was heading towards but you beat me to it.
Sent from my GT-I9300T using xda premium

Lonski said:
Thanks man, that's what I was heading towards but you beat me to it.
Sent from my GT-I9300T using xda premium
Click to expand...
Click to collapse
Yeah, took a "little" bit of flashing just to prove the method works. Anyone following the steps and links to the appropriate guides shouldn't have any trouble.
Had other ideas such as how to dump your firmware and re-package into Odin flashable .tar file . This took a while, so maybe I'll add the other method in future. Wife is on my case
Sent from my GT-I9300T using xda premium

Rooted my phone,made a nandroid backup,flashed cm9,restored using original nandoid backup then used triangleaway to reset counter which shows 0,flashed a custom kernel on stock rom.Baseband has reverted to normal but device status showing modified.How to change it to normal?
Sent from my G-I9300 using Tapatalk 2

rock2702 said:
........flashed a custom kernel on stock rom.Baseband has reverted to normal but device status showing modified.How to change it to normal?
Click to expand...
Click to collapse
You didn't follow the guide did you?
Your firmware is now "modified" from the original (out of the box) having flashed a custom kernel. Also, depending on the flash method (Odin?), your counter most likely increased again
If you want completely back to original (out of the box state) firmware, follow the guide in FULL >> Redo steps 1-9 (or 1-11)
Obviously, if your official firmware is available for download somewhere, this guide becomes redundant. Flashing a complete official firmware will remove the modified status, but yours isn't completely official/stock now is it?
But, if this is want you want
This guide is for those that require to return COMPLETLEY to stock (out of the box) and your firmware version is not yet available for download.
Click to expand...
Click to collapse
, follow the guide step-by-step and it will work!
To avoid any further confusion I've added to the OP......... COMPLETLEY to stock (out of the box).......

Actually i did all this before you posted this thread.I used triangle away and the official counter is showing 0.My firmware is not up for download still but i made the nandroid backup before flashing cm9.
I rooted my phone using cf root by chainfire and then flashed cm9 using cwm.But then i returned to stock using my backup,then flashed a custom kernel using mobile odin pro.If i flash my stock kernel will my device status be normal again?
Also wanted to ask if the efs backup pro is an android app?I dloaded the zip on my cell as i dont have pc now,should i flash the zip using cwm to get efs pro app?
Sent from my GT-I9300 using Tapatalk 2

rock2702 said:
Actually i did all this before you posted this thread.I used triangle away and the official counter is showing 0.My firmware is not up for download still but i made the nandroid backup before flashing cm9.
I rooted my phone using cf root by chainfire and then flashed cm9 using cwm.But then i returned to stock using my backup,then flashed a custom kernel using mobile odin pro.If i flash my stock kernel will my device status be normal again?
Also wanted to ask if the efs backup pro is an android app?I dloaded the zip on my cell as i dont have pc now,should i flash the zip using cwm to get efs pro app?
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I haven't tested any other method, as I was more concerned with getting the stock recovery.zip and proofed.
No counter + unroot + complete official firmware package => status = "normal".
If you flash an official kernel that is a different version to that of your official package, this would most likely "corrupt" the product code, so its not recognized = "modified".
These mix and match official firmware are referred as "Frankenstein".
EFS Backup Pro
http://forum.xda-developers.com/showthread.php?t=1308546
There are other methods, have a search...
Sent from my GT-I9300T using xda premium

I have a question, i followed the steps my phone shows normal for the device status but i still have cwm in my app drawer.

gadget069 said:
I have a question, i followed the steps my phone shows normal for the device status but i still have cwm in my app drawer.
Click to expand...
Click to collapse
CWM Manager app was installed when you first installed Chainfire CWM Recovery, and was back upped with your original nandroid.
You have not followed all the steps.....
Check steps #10 and #11
Sent from my GT-I9300T using xda premium

Thanks heaps for this.. I was trying to unroot & remove cwm recovery from my Optus Galaxy SIII all day yesterday with no luck since I couldn't find the stock Optus Australia firmware.. I skipped step 3 & 4 since all I did was flashing the CF-Root kernel . Now I can send this back without worrying
I did all those yesterday except I couldn't get back the stock recovery. Flashing the stock kernel didn't work. All good now

kamalmawa said:
Thanks heaps for this.. I was trying to unroot & remove cwm recovery from my Optus Galaxy SIII all day yesterday with no luck since I couldn't find the stock Optus Australia firmware.. I skipped step 3 & 4 since all I did was flashing the CF-Root kernel . Now I can send this back without worrying
I did all those yesterday except I couldn't get back the stock recovery. Flashing the stock kernel didn't work. All good now
Click to expand...
Click to collapse
Nice to hear success and was useful for you. Hope you get it back soon.
Hit thanks if you have the time
Sent from my GT-I9300 using xda premium

I only have a backup made before rooting, made with stock recovery.
This method will work for me?
But, my FW version is available. If I flashed through Odin I'll increase the counter. I'm a little bit lost here.

Yusei said:
I only have a backup made before rooting, made with stock recovery.
This method will work for me?
But, my FW version is available. If I flashed through Odin I'll increase the counter. I'm a little bit lost here.
Click to expand...
Click to collapse
I don't see how nandroid can be made without CWM recovery or various tools using ADB commands.
A nandroid backup is typically made up of:
1. boot.img
2. cache.ext4.tar
3. data.ext4.tar
4. nandroid.MD5 checksum
5. recovery.img
6. system.ext4.tar
Flashing any official firmware with Odin does not increase any counter.
++ This guide is not for you ++
For your case;
1. Use Triangle Away app to reset any counter
2. Flash official firmware with Odin (this will also remove root)
3. Wipe any evidence of SU apps and delete contents of internal sdcard
4. Maybe Factory reset before sending the phone off
Sent from my GT-I9300 using xda premium

With stock recovery I've made a backup xD
In that day I don't even bother with warranty, my wish was enter again in flashmaniac mode xD
I'm on my phone so I can't see if you have PayPal account, but if you have I'll buy you a beer.
Thanks dude, really thanks.

Yusei said:
With stock recovery I've made a backup xD
In that day I don't even bother with warranty, my wish was enter again in flashmaniac mode xD
I'm on my phone so I can't see if you have PayPal account, but if you have I'll buy you a beer.
Thanks dude, really thanks.
Click to expand...
Click to collapse
No problem. Happy my guide was of use.
Have Paypal, but happy to help out fellow XDA members and you hitting the "thanks" is enough.
Cheers
Sent from my GT-I9300 using xda premium

If I have not done any modifications than rooted can I triangle away then boot to cwm then install su unistaller and after that stock recovery and I'm done?
E: I read a guide where first triangle away then cwm and full wipe then odin flash and after that factory reset and I don't want to lose all data. Is the su app that is the reason for modified status as it's easy to remove in cwm before odin flash to stock?
Sent from my GT-I9300 using xda app-developers app

You don't need to be fully stock to get and install a OTA

I have seen misinformation regarding the ota process on the nexus s repeated so many times and its driving me nuts so I made this thread.
1. You CAN be rooted. Yes you can. Anybody that says otherwise is wrong
2. You can have a custom recovery and you SHOULD! Unless you're going to be running a logcat and trying to grab the ota URL when it first starts rolling out there is no need for stock recovery. In fact. You WON'T be able to install it manually on stock recovery. Yes you WON'T. If you're on stock recovery you either have to wait for it to be pushed to your device or flash custom recovery and flash the update zip manually. You CAN'T manually do it with stock anymore. Anybody that says otherwise is wrong.
3. Bootloader unlocked has no.effect.
4. I am not going into what rom you need on the phone or what else the updater script checks for. Since I don't see people constantly misinformed about it.
Lastly. If you're not unlocked (bootloader) now and not rooted with custom recovery you will NOT be able to flash jelly bean as soon as the ota update zip is posted. You will have to wait for it be pushed to your device or unlock and flash custom recovery..

"Real ota(?)" Is pushed by google and installs automatically, IMO.
Sent from my Nexus S using xda app-developers app

albundy2010 said:
I have seen misinformation regarding the ota process on the nexus s repeated so many times and its driving me nuts so I made this thread.
1. You CAN be rooted. Yes you can. Anybody that says otherwise is wrong
2. You can have a custom recovery and you SHOULD! Unless you're going to be running a logcat and trying to grab the ota URL when it first starts rolling out there is no need for stock recovery. In fact. You WON'T be able to install it manually on stock recovery. Yes you WON'T. If you're on stock recovery you either have to wait for it to be pushed to your device or flash custom recovery and flash the update zip manually. You CAN'T manually do it with stock anymore. Anybody that says otherwise is wrong.
3. Bootloader unlocked has no.effect.
4. I am not going into what rom you need on the phone or what else the updater script checks for. Since I don't see people constantly misinformed about it.
Lastly. If you're not unlocked (bootloader) now and not rooted with custom recovery you will NOT be able to flash jelly bean as soon as the ota update zip is posted. You will have to wait for it be pushed to your device or unlock and flash custom recovery..
Click to expand...
Click to collapse
1. Spot on, reading the update script it doesn't look for additional files. I said otherwise previously, my bad.
2. Also true. Updater script does no hash check on the two recovery files either, so even if you deleted /system/etc/install-recovery.sh it will still be fine. My bad also.
3. Spot on.
Thanks for this writeup albundy :good:

So I was running ics roms well before they came to my ns4g... I didn't bother with ota since there was already a port available almost immediately... that fixed most of the bugs we experienced with pre-ota ports...
My question is, I'm running RemICS UX v1.3... what would I need to do to get PTA when its available for our phones?
I'm sure they'll have a flashable rom almost immediately so this question might be null anyways... but it is good to know these things...
Sent from my Nexus S 4G using Tapatalk 2

ioplkj13 said:
"Real ota(?)" Is pushed by google and installs automatically, IMO.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Yes, but the question is when that will happen. Google pushes updates in waves, it could take weeks before it gets pushed to your phone.
And all those people already getting anxious now how to prepare their phone for ota-push don't strike me as the waiting kind... in fact, it's really silly making all that fuzz now, still another 2 weeks before 4.1 gets released.

the1dynasty said:
My question is, I'm running RemICS UX v1.3... what would I need to do to get PTA when its available for our phones?
I'm sure they'll have a flashable rom almost immediately so this question might be null anyways... but it is good to know these things...
Click to expand...
Click to collapse
So far the NS4G always had to wait to get an official update, Sprint taking it's time. The first OTA's will probably be for 9020T/9023 again, different radio. So unless you are willing to wait, you need a custom-zip anyway, don't use the dl-link from Google that will be floating around in 2 weeks.
But to answer your question:
First OTA's have always been incremental updates, so one needed to be on prior stock-rom to apply it. (In this case: 4.0.4 stock -> 4.1 update)
Of course they could change it this time and release everything at once (full rom, factory images, all models), but I heavily doubt it.

I'm on stock 4.0.4 rooted with no custom recovery. The way i see it i have 2 options:
1. Make an OTA update. I will not lose any app or data, but what about the root? It will be lost?
2. Flash CWM and the flash the update zip. In this case the root is surely gonna be in the zip file, but what about the apps and data. Will i lose them?

grigri444 said:
I'm on stock 4.0.4 rooted with no custom recovery. The way i see it i have 2 options:
1. Make an OTA update. I will not lose any app or data, but what about the root? It will be lost?
2. Flash CWM and the flash the update zip. In this case the root is surely gonna be in the zip file, but what about the apps and data. Will i lose them?
Click to expand...
Click to collapse
Re #1: Yep, root will be lost. You shouldn't loose and app / data.
RE #2: You only loose data when you do 'wipe data' in CWM, which you should do when installing a new ROM.
If you install 'Titanuim Backup' you can back up and then later restore all your APPs. After you back up APPs, you will need to transfer these to a PC, and wipe the phone, install new ROM, and then transfer APP backups back to SD Card on phone, install them using Titanium Backup. The PRO version allows you to do this in batch mode (much quicker).

ac17 said:
Re #1: Yep, root will be lost. You shouldn't loose and app / data.
RE #2: You only loose data when you do 'wipe data' in CWM, which you should do when installing a new ROM.
If you install 'Titanuim Backup' you can back up and then later restore all your APPs. After you back up APPs, you will need to transfer these to a PC, and wipe the phone, install new ROM, and then transfer APP backups back to SD Card on phone, install them using Titanium Backup. The PRO version allows you to do this in batch mode (much quicker).
Click to expand...
Click to collapse
I have Titanium backup pro. But which method is the wiser?
OTA and reroot or update zip and re-install all apps?

@ re #2: why the transfer of backups to PC?! They're saved on sdcard, it never gets wiped automatically (except when unlocking boot loader). And there's no need to do it manually.

caliban2 said:
@ re #2: why the transfer of backups to PC?! They're saved on sdcard, it never gets wiped automatically (except when unlocking boot loader). And there's no need to do it manually.
Click to expand...
Click to collapse
Because, i will make a wipe data in order to get a clean install of the new ROM. In our case the 4.1 stock.

you don't have to wipe sdcard to get a clean install... but go ahead, it won't do any harm.

will I get the OTA?
So I've got cyanogen mod 9 on my nexus s with Clockwork mod bootloader will I get the OTA update? if not what changes do I have change back? ps I would rather not format the Internal USB drive.

Ah you people complicated it for me, this is what I was thinking of doing
I'm on CyanogenMod 9 RC1, when Jelly Bean starts going OTA, there should be a flashable ZIP available, right? I know when I was on GB, and waiting for OTA for my country is never gonna happen, I just downloaded update.zip and flashed it.
1. Download ZIP, put it on SD Card, along with full stock 4.0.4 flashable ZIP, and Superuser.zip
2. Make Titanium Backup of apps
3. Go to CWM
4. Wipe data
5. Flash stock 4.0.4
6. Flash update to make it Jelly Bean
7. Flash Superuser
8. Boot to Jelly Bean
9. Explore around, download ROM Manager, install CWM again through it, because it will probably be gone once I boot into JB for the first time
10. Done
Correct me if I'm wrong.

JavaJunkay said:
Ah you people complicated it for me, this is what I was thinking of doing
I'm on CyanogenMod 9 RC1, when Jelly Bean starts going OTA, there should be a flashable ZIP available, right? I know when I was on GB, and waiting for OTA for my country is never gonna happen, I just downloaded update.zip and flashed it.
1. Download ZIP, put it on SD Card, along with full stock 4.0.4 flashable ZIP, and Superuser.zip
2. Make Titanium Backup of apps
3. Go to CWM
4. Wipe data
5. Flash stock 4.0.4
6. Flash update to make it Jelly Bean
7. Flash Superuser
8. Boot to Jelly Bean
9. Explore around, download ROM Manager, install CWM again through it, because it will probably be gone once I boot into JB for the first time
10. Done
Correct me if I'm wrong.
Click to expand...
Click to collapse
Too many steps. From what i have learned, download the JB flashable zip (probably it will be available the same day when ota is pushed) put to sdcard, make a wipe data and flash through cwm. The ics zip was releashed the same day, was root, busybox and superuser.

On stock 4.0.4 official with custom recovery...
Download ota zip
Boot to custom recovery
Flash ota zip
Directly after ota zip finishes, flash latest Superuser.zip (In same recovery session)
Wipe cache
Reboot----> Now you have latest ota JellyBean with Root.
Change permissions of recovery-from-boot & install-recovery.sh to 000 (so you will keep custom recovery upon reboot)
Re-flash custom recovery with JoeyKrim's Flash_Image GUI
Hungry Hungry Hippo Time

Can you have a custom kernel ??
Sent from my Nexus S using xda app-developers app

snandlal said:
On stock 4.0.4 official with custom recovery...
Download ota zip
Boot to custom recovery
Flash ota zip
Directly after ota zip finishes, flash latest Superuser.zip (In same recovery session)
Wipe cache
Reboot----> Now you have latest ota JellyBean with Root.
Change permissions of recovery-from-boot & install-recovery.sh to 000 (so you will keep custom recovery upon reboot)
Re-flash custom recovery with JoeyKrim's Flash_Image GUI
Hungry Hungry Hippo Time
Click to expand...
Click to collapse
Every stock zip contains a directory called "recovery". Delete it before flashing and you don't have to care about cwm getting overwritten.

btw are really needed only stock rom and stock kernel???
what about the 'ota survival' option present in superuser?

albundy2010 said:
I have seen misinformation regarding the ota process on the nexus s repeated so many times and its driving me nuts so I made this thread.
1. You CAN be rooted. Yes you can. Anybody that says otherwise is wrong
2. You can have a custom recovery and you SHOULD! Unless you're going to be running a logcat and trying to grab the ota URL when it first starts rolling out there is no need for stock recovery. In fact. You WON'T be able to install it manually on stock recovery. Yes you WON'T. If you're on stock recovery you either have to wait for it to be pushed to your device or flash custom recovery and flash the update zip manually. You CAN'T manually do it with stock anymore. Anybody that says otherwise is wrong.
3. Bootloader unlocked has no.effect.
4. I am not going into what rom you need on the phone or what else the updater script checks for. Since I don't see people constantly misinformed about it.
Lastly. If you're not unlocked (bootloader) now and not rooted with custom recovery you will NOT be able to flash jelly bean as soon as the ota update zip is posted. You will have to wait for it be pushed to your device or unlock and flash custom recovery..
Click to expand...
Click to collapse
I suspect in some of the "misinformation" you have missed the distinction between preparing the phone for automatically receiving and automatically installing properly an actual Over the Air update from Google, vs. preparing for you actually installing an OTA file, or some form of new Jelly Bean. You don't explicitly make this distinction or don't really clearly say which you are discussing. The title of your post points one direction, but the contents the other. Or maybe the "rant" style of writing just confuses people more, including me.

How to flash and root new 4.0.4 ICS stock rom

NOT MY CREDITS
Perhaps scryshark should made this post
(This applies both 7500 7510 and was writen when we didn't had the wifi only version, so for 7510 ignore the mention steps)
On step 1, you can use also:
--------------------------------
ODIN->PDA->SELECT FIRMWARE AND AFTER PUT TAB IN FLASH MODE CLICK START
--------------------------------
scaryshark said:
Here's a definitive guide for P7510 owners on how to install stock ICS on their tabs with root. How do I know it's definitive? Well, I'm running it right now with no problems!
NOTE: Obviously I shouln't have to say this but... WiFi only guys may run into a bug of some sort if trying to apply this. I haven't had any prblems yet. Everything works: WiFi, GPS, Camera, Auto-brightness, G-Sensor etc. If something wrong happens, then it's not my fault!
That said there are a few things going on because of running a P7500 ROM on a P7510. Like there is a signal indicator in the status bar showing no signal. There are mobile data options in the settings menu. The device is recognised as a P7510, i think you get the point.
Now to the actual instructions.
Step 1: Putting ICS on
- Create a Nandroid backup!
- Download & install Mobile Odin by Chainfire. [Redistrubution is not allowed so I've linked to his thread] <- Read that properly before you go onto the next step so it's istalled properly!
- Download the firmware and unzip
- Move the file P7500XXLQ8_P7500OXALQ8_P7500XXLQ8_HOME.tar.md5 to the root of your Tab.
- Open Mobile Odin
- Select the .md5 firmware you just put onto your Tab
- *IMPORTANT FOR WIFI TABS* Select Modem and press Clear
(there's no need to select the option of auto root or odin insall 'cos it wont work! )
- Select the 2 wipe options
- Plug your tab into the power supply
- Press the fflash firmware button
---------------------------------------------------
LET IT DO IT'S OWN THING. LEAVE IT AND WAIT FOR IT TO RESTART TO THE SETUP SCREEN
---------------------------------------------------
Done now your running ICS, but wait - you don't have root! or CWM recovery for that matter! :crying: Don't worry, keep reading!
CWM Recovery and Rooting:
- Download this update.zip for rooting your tab and move it to the root of your tab
- Put your tab into download mode
- Plug it into the computer
- Let the computer install the drivers (Automatic on Win 7 - unsure about other OS's)
- Download and unzip Odin 1.85
- Download CWM Touch Recovery & save to same folder as Odin 1.85
- Open up odin
- Click PDA and select the file named recovery.tar.md5
- Click start
-------------------------------------------------------------------------------
LET ODIN DO IT'S THING & WAIT FOR TAB TO RESTART
-------------------------------------------------------------------------------
- Put the tab into recovery mode.
- Select install from sd card and select Samsung_Galaxy_Tab_10.1_root.zip
---------------------------------------------------------------------------------
LET RECOVERY DO IT'S THING
-----------------------------------------------------------------------------------
- Tap go back and then reboot now
There you have it stock ICS for P7500 & P7510 rooted.
Click to expand...
Click to collapse

It works for me. I restored my apps + data using Mybackup Pro. Thanks for your work!

jpl69 said:
NOT MY CREDITS
Perhaps scryshark should made this post
(This applies both 7500 7510 and was writen when we didn't had the wifi only version, so for 7510 ignore the mention steps)
On step 1, you can use also:
--------------------------------
ODIN->PDA->SELECT FIRMWARE AND AFTER PUT TAB IN FLASH MODE CLICK START
--------------------------------
Click to expand...
Click to collapse
Cool! It may be possible to install the CWM recovery during the ROM install by downloading it from the Cwm website and using that recovery . I'm under the recovery option in mobile odin and skipping straight from initial reboot to putting it into recovery mode and installing the root update.zip. However I forgot to do that so I'm not sure if it'll work or not!
Sent from my GT-P7510 using XDA Premium HD app

So the firmware is for the UK. What happens if I flash this on my US tab?

9xnine said:
So the firmware is for the UK. What happens if I flash this on my US tab?
Click to expand...
Click to collapse
nothing. just flash it it will be OK

real77055 said:
nothing. just flash it it will be OK
Click to expand...
Click to collapse
If anyone has the issue where it just sits at the Samsung logo just reboot into recovery and do a data/cache wipe.

I assume the camera works?

awwilson21 said:
I assume the camera works?
Click to expand...
Click to collapse
Everything works.

After pressing flash firmware, I have the odin logo on my tab for 10 mins now.
Is this normal?
If not, what should I do now?

Thanks for bringing this nice guide.
So do I get this right that there is no way to flash the rom without wiping?

Im a little nervous here. Did I just brick my device?
Why is the odin logo still on my tab? Wasnt there supposed to be a restart?

tomerstern said:
After pressing flash firmware, I have the odin logo on my tab for 10 mins now.
Is this normal?
If not, what should I do now?
Click to expand...
Click to collapse
I used Normal ODIN on my PC. When it finished it rebooted and hung at the Samsung logo. I rebooted into recovery and wiped data/cache and it fixed it. You could attempt to reboot into recovery. If Mobile ODIN did it's thing you will be back to stock recovery. If that's the case then wipe data/cache and reboot.
---------- Post added at 12:58 PM ---------- Previous post was at 12:57 PM ----------
tomerstern said:
Im a little nervous here. Did I just brick my device?
Why is the odin logo still on my tab? Wasnt there supposed to be a restart?
Click to expand...
Click to collapse
I doubt you bricked it. Hold power and volume down to reboot into recovery or download mode again. If you can get to recovery and download mode you are fine.

OK, I rebooted, I have the following options:
1. reboot system now
2. apply update from external storage
3. wipe data / factory reset
3. wipe cache partition
4. apply update from cache.
Which one should I choose?

tomerstern said:
OK, I rebooted, I have the following options:
1. reboot system now
2. apply update from external storage
3. wipe data / factory reset
3. wipe cache partition
4. apply update from cache.
Which one should I choose?
Click to expand...
Click to collapse
OK so you have the stock recovery. Thats good. first wipe data/factory reset. Then wipe cache partition, then reboot.

Thanks so much!
I now have ICS running!!
That was a tough 30 mins

tomerstern said:
Thanks so much!
I now have ICS running!!
That was a tough 30 mins
Click to expand...
Click to collapse
We've all been there. Just remember before you start flashing make sure you know which buttons will get you into recovery and Download mode. If you can get to recovery or download mode there is no reason to freak out. Also, ODIN is your friend. I recommend having a copy of the PC version installed on your PC just in case something goes wrong with a flash or Mobile ODIN. Glad it's up and running for you!

I can get the Rom running alright. My problem is that I get the rolling recovery issue. With the a 5.0.... recovery I get rolling recovery, but the Rom runs fine. If I install the recovery from Pershoots page which is 5.5.0.4, then I get no Rolling recovery, but I get a rolling Rom instead! Frustrating!
Edit: Installed Pershoots recovery v6.0.1.0, didn't solve the issue, but flashing the bootloader method from here: http://forum.xda-developers.com/showthread.php?t=1555984 fixed things. The bootloader change didn't work for me on the older recovery's.
Edit 2: Scrap that, I hadn't turned the screen off yet, that's when it happens lol.

9xnine said:
Everything works.
Click to expand...
Click to collapse
Awesome! So CM10 should be fully functional soon!

Yeah, I tried the bootloader thing as well with the rolling recovery here. Wasn't a great idea anyhow, I guess we need to flash the bootloader from the 4.0.4 ROM, I just don't know how or how to make such a tar on Windows...
Sent from my GT-P7510 using XDA Premium HD app

Yeh I'm not sure either. I managed to get the recovery and rom working for honeycomb and then on to ICS AOSP, but not sure what to do to get this rooted etc!
Sent from my GT-P7510 using xda app-developers app

Any Guide available For Flashing 4.2.2 on Custom kernel without Loosing Data

As the Topic Suggest is there any guide someone made for noobs like me
who wanna upgrade there NEXUS 7 to 4.2.2 having Custom kernel without loosing data ?

You don't need a guide in your case.
Click here:
http://forum.xda-developers.com/showthread.php?t=2148337
There are two STOCK 4.2.2 roms in this thread. One is DEODEXED and the other is ODEXED.
I recommend downloading the DEODEXED STOCK 4.2.2 rom.
Here's the link to the DEODEXED STOCK ROM:
http://goo.im/devs/teshxx/Nexus7Wifi/Grouper-JDQ39_4.2.2-Deodex_Rooted-02-14-13-teshxx.zip
Download it, put it in your N7 and flash it via recovery. You won't lose any data and you don't have to wipe anything. Just flash and go!

scream4cheese said:
You don't need a guide in your case.
Click here:
http://forum.xda-developers.com/showthread.php?t=2148337
There are two STOCK 4.2.2 roms in this thread. One is DEODEXED and the other is ODEXED.
I recommend downloading the DEODEXED STOCK 4.2.2 rom.
Here's the link to the DEODEXED STOCK ROM:
http://goo.im/devs/teshxx/Nexus7Wifi/Grouper-JDQ39_4.2.2-Deodex_Rooted-02-14-13-teshxx.zip
Download it, put it in your N7 and flash it via recovery. You won't lose any data and you won't have to wipe anything. Just flash and go!
Click to expand...
Click to collapse
I won't get error 7 ?
For installing this ?
And its not ota update how come it wont wipe data?
Sent from my Nexus 7 using Tapatalk HD

1) make a full nandroid (cwm/twrp) backup
2) flash a 4.2.2 stock-derived ROM on top of existing ROM - no wipe
2.5) flash a minimal root kit (SuperSU or Superuser) if not in ROM in step 2 - no wipe
3) flash the same kernel you used previously - no wipe
4) profit!
No workie? Restore backup from step # 1 and try something else.

pleasant said:
I won't get error 7 ?
For installing this ?
And its not ota update how come it wont wipe data?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
1. Have you read the thread?
2. No it won't give you an error. Why would it?
3. It's from the official OTA update. You just don't need to wipe anything. Trust me on this.
4. How come? I did this last night on my Nexus 7 and everything is just fine.
5. You won't get a bootloop or an error if you do exactly what I just told you.
Sent from my Nexus 4 using Tapatalk 2

scream4cheese said:
1. Have you read the thread?
2. No it won't give you an error. Why would it?
3. It's from the official OTA update. You just don't need to wipe anything. Trust me on this.
4. How come? I did this last night on my Nexus 7 and everything is just fine.
5. You won't get a bootloop or an error if you do exactly what I just told you.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
For safety I made a full online nandroid backup as above suggested now the issue is I am trying to copy the backup on PC
But when I plug nexus 7 on PC
In clockworkmod folder the backup folder doesn't show up but in
File manager at tablet shows it :/
Sent from my Nexus 7 using Tapatalk HD

pleasant said:
For safety I made a full online nandroid backup as above suggested now the issue is I am trying to copy the backup on PC
But when I plug nexus 7 on PC
In clockworkmod folder the backup folder doesn't show up but in
File manager at tablet shows it :/
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
There's no need to do that. But in spite of it, I can tell you that you can just create the nandroid backup and leave it in your device. Don't pull it out. Just flash the download in my previous post and if anything goes wrong. Enter recovery mode and restore your system. Even if you did pull the nandriod backup file from the N7 and the device fails to boot up, you cant just put the file back in to restore it that way. It won't mount so you can access the internal storage system.
P.S i don't know how to make the backup show up but i think there are a few thread here that some people have found a solution to it.

scream4cheese said:
1. Have you read the thread?
2. No it won't give you an error. Why would it?
3. It's from the official OTA update. You just don't need to wipe anything. Trust me on this.
4. How come? I did this last night on my Nexus 7 and everything is just fine.
5. You won't get a bootloop or an error if you do exactly what I just told you.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
DA FAAK this thing worked :good:
i am finally upgraded to 4.2.2
tell me why this one didnt gave "7" error ?
Where this Guide was Hiding i have been looking for easiest method and this is what it is

pleasant said:
For safety I made a full online nandroid backup as above suggested now the issue is I am trying to copy the backup on PC
But when I plug nexus 7 on PC
In clockworkmod folder the backup folder doesn't show up but in
File manager at tablet shows it :/
Click to expand...
Click to collapse
I have had TWRP behave the same way - sometimes it will put backups in
/data/media/TWRP/...
and sometimes in
/data/media/0/TWRP/...
It is a bit of a mystery what causes this to happen. Strangely, when there is a folder in the first location, TWRP (2.4.1.0) will not find the second one. But, if I manually move the files from the first location (/data/media/TWRP) to the second location (/data/media/0/TWRP) using a file manager, then TWRP will find the backups no problem.
well, the "sdcard" mount point ( == /data/media/0/ ) is the thing that shows up on the PC via MTP mode, so I would just move the files to the second location. I'm not sure if CWM behaves the same way, but you will certainly be able to copy them from the N7 to the PC at that point.
good luck.

pleasant said:
DA FAAK this thing worked :good:
i am finally upgraded to 4.2.2
tell me why this one didnt gave "7" error ?
Where this Guide was Hiding i have been looking for easiest method and this is what it is
Click to expand...
Click to collapse
LOL. I told you it works.
There's one thing that you're missing from that update. And that is the bootloader version, the bootloader version that you're currently using is 4.13. The newest version is 4.18. You don't have to update it if you don't want to.
I'll include this link for you to flash the latest bootloader via command prompt.
http://forum.xda-developers.com/showthread.php?t=2150251
I hope you know how to use adb/fastboot.

scream4cheese said:
LOL. I told you it works.
There's one thing that you're missing from that update. And that is the bootloader version, the bootloader version that you're currently using is 4.13. The newest version is 4.18. You don't have to update it if you don't want to.
I'll include this link for you to flash the latest bootloader via command prompt.
http://forum.xda-developers.com/showthread.php?t=2150251
I hope you know how to use adb/fastboot.
Click to expand...
Click to collapse
first tell me does updating bootloader wipes data ?
and secondly what does bootloader do and advantage of updating bootloader ?
u mean to say sideload command ?

pleasant said:
first tell me does updating bootloader wipes data ?
and secondly what does bootloader do and advantage of updating bootloader ?
u mean to say sideload command ?
Click to expand...
Click to collapse
Updating bootloader does not wipe anything. It simply replaces and updates the one you already have on.
Definition of a bootloader:
http://m.androidcentral.com/what-is-android-bootloader
Sideload? I think so.

boot(basically kernel) and system are usually what people mean 'custom ROM'. So if you just manually flash these two things(and usually need to be done together), none of your 'data' would be lost.
So just find these two images (usually .img) in whatever custom ROM you want and flash it.
This is the unix convention for a long long while and android is just linux

scream4cheese said:
Updating bootloader does not wipe anything. It simply replaces and updates the one you already have on.
Definition of a bootloader:
http://m.androidcentral.com/what-is-android-bootloader
Sideload? I think so.
Click to expand...
Click to collapse
So if there is a flashable zip available that would be great
Sent from my Nexus 7 using Tapatalk HD

you don't really need to flash bootloader

chimpanzeexda said:
you don't really need to flash bootloader
Click to expand...
Click to collapse
Yeah, I told him that.
Sent from my Nexus 7 using Tapatalk HD

scream4cheese said:
1. Have you read the thread?
2. No it won't give you an error. Why would it?
3. It's from the official OTA update. You just don't need to wipe anything. Trust me on this.
4. How come? I did this last night on my Nexus 7 and everything is just fine.
5. You won't get a bootloop or an error if you do exactly what I just told you.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Hi bro can you provide me the similar flashable zip for android 4.3 for nexus 7 wifi
Sent from my Nexus 7 using Tapatalk HD

[Q] Problems with KitKat Cook Roms?

Dear friends,
First all, I tried to search, found some threads (Titanium Backup problem) but it did not work for me.
I just bought a N9005 (after 1 year stick with i9500). With i9500 everything very simple with 4.3, I haven't upgraded to KitKat.
With N9005 I stuck with some problem for days: Tried to install some Custom Rom: Crash, Echoe, X-Note ... same problems:
- Dropbox: can not export file, can not save.
- Titanium Backup: FC
- Some apps can not download file.
-----------------------------------------------------------
I tried
"su
Restorecon -R -v /data/data/
But still didnot work. I think the problem is can not write on the storage. But it's weird, in Browser i'm still able to download files.
-----------------------------------------------------------
Later I went back to stock rom, with root flashed. Everything go smooth. But I still want to go with custom rom (as I always did with my i9500). Is this custom rom problem?
-----------------------------------------------------------
Thank you all.
Best regards.
Ryan.

Alan_Hill said:
Dear friends,
First all, I tried to search, found some threads (Titanium Backup problem) but it did not work for me.
I just bought a N9005 (after 1 year stick with i9500). With i9500 everything very simple with 4.3, I haven't upgraded to KitKat.
With N9005 I stuck with some problem for days: Tried to install some Custom Rom: Crash, Echoe, X-Note ... same problems:
- Dropbox: can not export file, can not save.
- Titanium Backup: FC
- Some "black market" can not download file.
-----------------------------------------------------------
I tried
"su
Restorecon -R -v /data/data/
But still didnot work. I think the problem is can not write on the storage. But it's weird, in Browser i'm still able to download files.
-----------------------------------------------------------
Later I went back to stock rom, with root flashed. Everything go smooth. But I still want to go with custom rom (as I always did with my i9500). Is this custom rom problem?
-----------------------------------------------------------
Thank you all.
Best regards.
Ryan.
Click to expand...
Click to collapse
To be clear, what rom are you using now? JB or KK?

fadhil3536 said:
To be clear, what rom are you using now? JB or KK?
Click to expand...
Click to collapse
KitKat my friend

Alan_Hill said:
- Some "black market" can not download file
Click to expand...
Click to collapse
No warez or discussion thereof allowed here, forum rules. That may be your problem - corrupted or virus-ridden warez apks. Good luck....

B3311 said:
No warez or discussion thereof allowed here, forum rules. That may be your problem - corrupted or virus-ridden warez apks. Good luck....
Click to expand...
Click to collapse
Ok sorry my bad, may I edit my post?
Might not be crrupted or virus, I tried many times with different roms, with full wipe, format ...

Still not entirely clear - did you have a working KK ROM and now you're trying to install a KK custom ROM, or did you have JB 4.3 before trying to upgrade?

Alan_Hill said:
Ok sorry my bad, may I edit my post?
Might not be crrupted or virus, I tried many times with different roms, with full wipe, format ...
Click to expand...
Click to collapse
Before installing custom rom, did you wipe your rom manually using recovery (CWM)? wipe cache, systems, dalvik and data partitions?
Titanium backup have a problem when restoring data in KK, but there is a fix for it in the playstore. When finished restore (batch restore) don't run the app yet, run the TB fix and restart.phone.
All downloaded file using any browser will go to phone memory.
I am using stock root NC2. to bypass this SD Card issue copy this file to system/etc/permissions and set permission. Restart phone. hope it help.
https://www.dropbox.com/s/5yxb1kqv8lc6ycp/platform.xml

fadhil3536 said:
Before installing custom rom, did you wipe your rom manually using recovery (CWM)? wipe cache, systems, dalvik and data partitions?
Titanium backup have a problem when restoring data in KK, but there is a fix for it in the playstore. When finished restore (batch restore) don't run the app yet, run the TB fix and restart.phone.
All downloaded file using any browser will go to phone memory.
I am using stock root NC2. to bypass this SD Card issue copy this file to system/etc/permissions and set permission. Restart phone. hope it help.
https://www.dropbox.com/s/5yxb1kqv8lc6ycp/platform.xml
Click to expand...
Click to collapse
To be clearer, I have stock root NC2, wanna try other custom roms (Crash, Echoe, Xnote).
I tried them all but still have the same issue.
I always do full wipe in CWM when switch to another custom rom.
I tried to edit the permission as you mentioned (both manually and copy file) but got error message all the time, seem like I couldn't write or edit file.
I installed the TB fix on Play Store, but It say no issues with the phone (weird), so can not run.
Stock rom everything seem ok but custom roms always have same issues T_T

Its mean your phone doesnt fully root?

fadhil3536 said:
Its mean your phone doesnt fully root?
Click to expand...
Click to collapse
I double checked that. Tried to flash root again. Superuser ok, but still stuck .

Alan_Hill said:
I double checked that. Tried to flash root again. Superuser ok, but still stuck .
Click to expand...
Click to collapse
Can i know which method you are using to root the phone?

fadhil3536 said:
Can i know which method you are using to root the phone?
Click to expand...
Click to collapse
I flash the auto root in team win recovery mode .

Did you remove the file explorer from supersu app then give root permissions again afterwads?
This fixed ES for me...

I'm using this:
https://plus.google.com/app/basic/stream/z12fsrl4jujntr24h04cjl1aoor5ezninhc