Database Info

[Q] Downgrade To 2.3.2

Before the 2.3.3 update the screen on my Nexus S was actually fairly accurate. I did not have any of the blue color tint problems reported by some, with the new update the color temperature is visibly yellow. It seems that a lot of the SuperOMOLED screens are different sadly even when running the Star Field live wallpaper I can see a yellow tint. Is there any way to downgrade back to Gingerbread 2.3.2
Thanks

http://android.clients.google.com/p...9e.signed-soju-GRI40-from-GRH78C.98f3836c.zip Or download a nandroid backup of 2.3.2 or download a ROM thats using 2.3.2 (CM7, GingerS, etc)

so i only have to install this update.zip to downgrade?
is this really working?
thx
bernd

bgrimm said:
so i only have to install this update.zip to downgrade?
is this really working?
thx
bernd
Click to expand...
Click to collapse
yes
10char

zephiK said:
http://android.clients.google.com/p...9e.signed-soju-GRI40-from-GRH78C.98f3836c.zip Or download a nandroid backup of 2.3.2 or download a ROM thats using 2.3.2 (CM7, GingerS, etc)
Click to expand...
Click to collapse
zephiK I downloaded the link and installed the update from the SD Card and everything installed fine. But I rebooted and its still stuck on 2.3.3
Should I follow these instructions?
http://forum.xda-developers.com/showthread.php?t=965686
Thanks

brnagi said:
zephiK I downloaded the link and installed the update from the SD Card and everything installed fine. But I rebooted and its still stuck on 2.3.3
Should I follow these instructions?
http://forum.xda-developers.com/showthread.php?t=965686
Thanks
Click to expand...
Click to collapse
yes that is another way of reverting back to 2.3.2, but that update SHOULD work.
What recovery do you have? If you're using clockwork, MAKE SURE you are flashing
98f3836cef9e.signed-soju-GRI40-from-GRH78C.98f3836c.zip not update.zip.
to do this.. install .zip from sdcard -- just make sure it isnt update.zip
It's very possible that you renamed the 2.3.3 .zip to update.zip and you just simply reflashed update.zip which is 2.3.3
if you're on stock recovery, then mount the USB and delete update.zip and rename 98f3836cef9e.signed-soju-GRI40-from-GRH78C.98f3836c.zip to update.zip then flash

I'm running a stock Nexus S not rooted yet. I did delete the old update.zip and replaced it with your link but I'm still having getting the same results. In recovery the update installs everything and I still reboot back into 2.3.3
Kernal Version is: 2.6.35.7-g1d030a7
Build: GRI40

The other alternative step is to 'fastboot oem unlock' and go through the rooting process. (or do the process of not unlocking and rooting)
- Install Clockwork Recovery
- Download Nandroid backup of 2.3.2
- Restore from the 2.3.2 backup
| OR |
Flash a 2.3.2 based ROM such as CyanogenMod7 RC1 (or Nightlies), GingerS, Bionix, MoDaCo, and so forth.
Stickies in Dev forum will help you get started with tutorials.

zephiK said:
The other alternative step is to 'fastboot oem unlock' and go through the rooting process. (or do the process of not unlocking and rooting)
- Install Clockwork Recovery
- Download Nandroid backup of 2.3.2
- Restore from the 2.3.2 backup
Stickies in Dev forum will help you get started with tutorials.
Click to expand...
Click to collapse
Thanks zephiK I'm going to give this a shot

brnagi said:
Thanks zephiK I'm going to give this a shot
Click to expand...
Click to collapse
no problem. sorry that the 2.3.2 update didnt work out.
I would highly recommend buying Titanium Backup pro or using MyBackUp (Never used this) to backup your apps as you become a flashaholic.
Whenever you flash new ROMs and wipe.. you'll lose your apps but those two apps I mentioned above will save them.
BTW. when you do fastboot oem unlock, your stuff are going to be wiped so make sure you back them up!

zephiK said:
no problem. sorry that the 2.3.2 update didnt work out.
I would highly recommend buying Titanium Backup pro or using MyBackUp (Never used this) to backup your apps as you become a flashaholic.
Whenever you flash new ROMs and wipe.. you'll lose your apps but those two apps I mentioned above will save them.
BTW. when you do fastboot oem unlock, your stuff are going to be wiped so make sure you back them up!
Click to expand...
Click to collapse
I just did a quick Google search on the file you posted and I think its for the 2.3.3 update

zephiK said:
yes that is another way of reverting back to 2.3.2, but that update SHOULD work.
What recovery do you have? If you're using clockwork, MAKE SURE you are flashing
98f3836cef9e.signed-soju-GRI40-from-GRH78C.98f3836c.zip not update.zip.
to do this.. install .zip from sdcard -- just make sure it isnt update.zip
It's very possible that you renamed the 2.3.3 .zip to update.zip and you just simply reflashed update.zip which is 2.3.3
if you're on stock recovery, then mount the USB and delete update.zip and rename 98f3836cef9e.signed-soju-GRI40-from-GRH78C.98f3836c.zip to update.zip then flash
Click to expand...
Click to collapse
Why would the file named "GRI40-from-GRH78C" downgrade you from 2.3.3 to 2.3.2? That's the update file that takes you TO 2.3.3 (aka GRI40) FROM 2.3.2 (aka GRH78C).
Is the one you're recommending modded in some way? If so, it should be renamed to avoid confusion. If not, it's not the right thing to do to accomplish a revert from 2.3.3 to 2.3.2 as requested from the OP.

I don't think it's the right file to downgrade. It is the one upgrade to 2.3.3 from 2.3.2.

kurtlou said:
I don't think it's the right file to downgrade. It is the one upgrade to 2.3.3 from 2.3.2.
Click to expand...
Click to collapse
It's not. He's confused. The "98f3836cef9e.signed-soju-GRI40-from-GRH78C.98f3836c.zip" is definitely the NEW OTA to take you to 2.3.3 from 2.3.3. It has the new bootloader in it and PATCHES from 2.3.2 to 2.3.3. It is 21mb in size and only includes patches.

hmm so how to downgrade to 2.3.2 if I don't have (and hopefully don't have to) unlock bootloader?
i'm planning to downgrade to 2.3.2, then boot into clockwork mode, and use my previous 2.3.2 nandroid backup..
my previous 2.3.2 works fine, no random reboot and at least the colour is pleasant to my eyes..

I'm pretty sure I've devised a method to revert back to 2.3.2 correctly, but I haven't tested it yet and you may or may not need to root your device, depending on what you want backed up.
If you're on 2.3.3 and would like to back everything up as best you can, I advise that you first root, install Titanium Backup, and run.
Next, use the info from this thread to use Odin to revert your Nexus S back to 2.3.1. That thread also includes instructions on how to flash the radio as well to get it truly back to 2.3.1.
After that, you can grab the manual update.zip for 2.3.2 from this link.
From there, if you had previously rooted and backed up your apps and data, you can root again and use Titanium Backup to restore everything.
Hope this helps.

It does sound like the update posted is 2.3.3 from 2.3.2 if you ask me, i guess there may be other revisions too, or will be (from 2.3.1 to 2.3.3 etc..)
For you colour issues (not something i have i guess i jsut have a good LED screen, but i did have the reboots (now fixed) i would suggest:
Keep 2.3.3 (its very smooth)
Install Netarchy cfs 2.3.3 compat kernel
Install Voodoo App from Market
Choose Voodoo's colour profile in the app
I think with that you may be able to keep your update and have the colours you want?
Well i hope so

So I have one of those dreaded 2.51 stock ROMs, what now?

Greetings,
I just bought and legally unlocked a Motorola Defy from Spain, and the carrier was Vodafone.
Checking the ROM in it, it says the following:
System version:
Blur_Version.2.51.1.MB525VF360Blur.Vodafone.en.ES
While the build number says:
JRDNEM_U3_2.51.1
So it's a 2.51.
What exactly does this mean?
I've searched the forum up and down and I still don't quite get it.
The only info I got was:
walter79 said:
!!!!!!!!! Flash only if you come from a 2.21 or 2.34 rom "That is because it has version 2 for CG31 and CG39, if you are on stock 2.51 those versions are 3 and if you flashed leaked froyo those are 4 and you cannot flash any firmware with lower versions. if you are on 2.21 or 2.34 you can flash this, otherwise you will brick your phone. !!!!!!!!!!!!!!!
Click to expand...
Click to collapse
And I don't understand what this means. What's version 2 and 3? What's CG31 and CG39?
There's no official 2.2 Froyo update for my phone, and AFAIK there's no news saying when that may happen.
I don't want Blur (I want to be able to use stock Android widgets), and I don't want the Vodafone or any other operator's stuff.
I know there's no stock ROM without those things so I'll have to do with a modded ROM (I'm very compelled to getting this one).
I'd also like to have the oportunity to reflash the phone to its stock ROM, in case I need to send it to warranty.
I flashed my girlfriend's Milestone with the latest UK official ROM through RSD Lite (after the phone bricked when I used the official update procedure!), and it was a rather simple procedure.
So given that I have one of those "bad" 2.51 ROMs, what additional procedures do I need to make, besides the sbf flashing through RSD Lite?

don't worry mate.. i have 2.51 too.
where to start it..
um.. maybe this.
CMIIW.
SBF is just like RAR and ZIP, it is packaging file.
inside SBF there many files, two of those are CG31.SMG & CG39.SMG.
some newer release SBF (froyo) might have EARLIER "version" of CG31.SMG and CG39.SMG
than CG31.SMG and CG39.SMG on your phone (2.51).
which mean it can't be done to flash it (flash to earlier version).
as long as you not flashing CG31.SMG and CG39.SMG when you apply froyo (leaked or official) update. it's fine..
i think someone here (fritolays) found method to FIX the SBF to exclude CG31.SMG and CG39.SMG. name of that SBF is FIXED SBF.
so if you want to upgrade to froyo, do not flash FULL SBF.
but use clockwork recovery to wipe data and wipe cache, then apply the nandroid backup, then flash the FIXED SBF using RSD Lite 4.9.
----------------------------------------
my advice before you doing anything,
do a factory reset, get root, install custom recovery,
then just create a nandroid backup of your stock 2.51 with custom recovery,
and make sure you have a FULL SBF of 2.51 of your region, and you have FIXED SBF 2.51 of your region.
so if you want to go back to eclair stock:
-install custom recovery, go to custom recovery, wipe data and wipe cache,
-apply restore nandroid backup of your stock
-flash the FIXED SBF 2.51 of your region.
-----------------------------------------

Ok, I now have a nice brick, for the moment.
After rooting, installing the clockwork mod and backing up my original ROM, I flashed a "fixed" SBF from the 3.4.3-11 version.
After the flash, the phone just hangs in the motorola symbol on and off (by about 2 minutes).
I tried both this SBF:
http://forum.xda-developers.com/showpost.php?p=12596803&postcount=845
and this one:
http://forum.xda-developers.com/showpost.php?p=12357943&postcount=62
Both give me the same result: Motorola logo on and off, and no boot.
The bootloader is still accessible.
RSD Lite says to power up the phone manually, but it does so by itself.
Is there some hidden ritual that I don't know of? (like unplugging the USB at a certain time or pressing some buttons?)
Any suggestions?
I've seen this one:
http://forum.xda-developers.com/showpost.php?p=12620475&postcount=7
But I don't even know if it's a fixed ROM or not.. should I try it?

Tried the following ROM with the same result:
3.4.2_155-Fixed.CEE_DEBLUR.sbf
I'm starting to get a bit preocupied here.
Help?

Try restoring a nandroid backup first, then right when you reboot go into stock recovery and flash the fixed sbf for that nandroid backup you installed and it should work fine. It sounds like you may have flashed a fixed sbf before you installed a nandroid backup. Hope this helps.
Sent from my MB525 using XDA App

Dewman4life said:
Try restoring a nandroid backup first, then right when you reboot go into stock recovery and flash the fixed sbf for that nandroid backup you installed and it should work fine. It sounds like you may have flashed a fixed sbf before you installed a nandroid backup. Hope this helps.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
How can I restore the nandroid I did previously?
The clockwork restore boot has been uninstalled, and the restore boot I have right now only has "wipe data", "wipe cache" and "apply update.zip"..

As far I know, you can't enter custom recovery from a boot loop. I don't know if this is correct, but the only way i see to you is flash the full SBF of your stock rom, that you can find here:
http://forum.xda-developers.com/showthread.php?t=966537
Tons of JRDNEM_U3_2.51.1, choose that best fits your phone and go. Next time, BEFORE flashing the fixed SBF, restore nandroid.

ToTTenTranz said:
Ok, I now have a nice brick, for the moment.
After rooting, installing the clockwork mod and backing up my original ROM, I flashed a "fixed" SBF from the 3.4.3-11 version.
After the flash, the phone just hangs in the motorola symbol on and off (by about 2 minutes).
I tried both this SBF:
http://forum.xda-developers.com/showpost.php?p=12596803&postcount=845
and this one:
http://forum.xda-developers.com/showpost.php?p=12357943&postcount=62
Both give me the same result: Motorola logo on and off, and no boot.
The bootloader is still accessible.
RSD Lite says to power up the phone manually, but it does so by itself.
Is there some hidden ritual that I don't know of? (like unplugging the USB at a certain time or pressing some buttons?)
Any suggestions?
I've seen this one:
http://forum.xda-developers.com/showpost.php?p=12620475&postcount=7
But I don't even know if it's a fixed ROM or not.. should I try it?
Click to expand...
Click to collapse
oh damn..
you just bricked your phone right...
the steps are wrong... the steps are:
root>install custom recovery>apply nandroid backup of froyo>reboot but immediately go to bootloader>flash fixed sbf of froyo.
you have to restore nandroid backup of froyo 3.4.3-11 first before you flash the fixed SBF of 3.4.3-11.
from your explanation,
you create backup of your 2.51 then flash the fixed sbf of 3.4.3-11?
if it is true, the ROM is still eclair 2.51 and you install the 3.4.3-11 firmware,
i think that's the problem.
you should restore nandroid backup of froyo 3.4.3-11 first before you flash the fixed sbf of 3.4.3-11.
after that, you follow what pays thread says to do to install his rom.
just because your defy cannot be started,
what you can do now is just flash your phone back to eclair 2.51 first with full SBF, not fixed.
the condition now is you have FIXED firmware of 3.4.3-11, but with 2.51 ROM inside.
just because it is fixed, you still have a chance going back to eclair 2.51
search Full SBF Eclair 2.51 of your region, and flash it with RSD Lite.
hope and make sure your battery is full enough to flash the full SBF, maybe 60-80% is enough.
because with that condition, i think the battery is not charging, even you charge it.
after everything is back to normal (eclair 2.51)
then if you still want to use pays, follow this method
-root
-install custom recovery, reboot to custom recovery
-restore nandroid backup of froyo 3.4.3-11 (if you can't find it pm me)
-immediately flash fixed sbf of froyo 3.4.3-11
-now your phone should froyo 3.4.3-11
-install pays rom with custom recovery

I flashed this sbf and I now have a working phone with a 3.4.2-155 firmware. Phew...
So I should have "restored the nandroid backup of 3.4.3-11" while still having the 2.51 firmware and only then I should have flashed the fixed firmware?
Sorry, this is really confusing for me.
With this 3.4.2-155 firmware, can I still do that procedure to get the pays rom?

ToTTenTranz said:
I flashed this sbf and I now have a working phone with a 3.4.2-155 firmware. Phew...
With this 3.4.2-155 firmware, can I still do that procedure to get the pays rom?
Click to expand...
Click to collapse
oh no...
you flash the FULL SBF of 3.4.2-155??
you should flash FULL SBF of 2.51...
i think you lost your downgradeability now...
but you still can use pays,
just follow like pays thread says.
just because you lost your downgradeability,
you shouldn't even care to flash the full SBF 3.4.3-11 now..
(you don't have to use any nandroid backup now to upgrade to newer build)
ToTTenTranz said:
So I should have "restored the nandroid backup of 3.4.3-11" while still having the 2.51 firmware and only then I should have flashed the fixed firmware?
Sorry, this is really confusing for me.
Click to expand...
Click to collapse
yea, you should do that...
while still having 2.51 firmware,
you should restore the nandroid backup of 3.4.3-11 first,
and then you flash the fixed sbf of 3.4.3-11.

Now you are +1 that can't go back to 2.1 \o/ (like me kkkk)
If you have flashed the full SBF from 2.51.1 you could still have a chance.
And yes, you can go to any ROM that is 2.2 now, test Pays, LiquidArc and BluelessGinger from JBoogie3 and Barebones from Fritolays(my favourite). Don't worry about nandroid backups anymore, just do the full SBF when you install a new ROM (it's what I do).

But as soon as the Spanish Vodafone release a Froyo ROM, I should be able to flash to that and still get the warranty if I need to, right?
Truth be told, I would never want to go back to 2.1, except for warranty procedures.

The problem is that, only if you can find a SBF from Vodafone ES you will have your warranty. And this is just a possibility, since this SBF was not released yet. Good luck for you (and for me, since I'm in the same situation, heheheh)

ToTTenTranz said:
But as soon as the Spanish Vodafone release a Froyo ROM, I should be able to flash to that and still get the warranty if I need to, right?
Truth be told, I would never want to go back to 2.1, except for warranty procedures.
Click to expand...
Click to collapse
as long as the official spanish vodafone SBF have the latest version of CG31.SMG and CG39.SMG inside (newer than CG31.SMG and CG39.SMG inside 3.4.3-11), it should be fine..
otherwise there's workaround though.
if just in case the CG31 and CG39 are in lower version,
you should restore nandroid of official froyo spanish (when it released)
then you flash the fixed sbf of that release.
i am sorry for your lost...
but you can still go back to 2.51 though..
but not in proper "real eclair 2.51"
i will post this method if you ask.

Helps to read all the threads on the process as there are many. Now the problem lies your on froyo and can't get back to eclair if you need to send it in for repair. The main thing tho is your back up and running.
Sent from my MB525 using XDA App

Going to root, am I doing it right?

I am on stock 4.0.4 with a locked bootloader. I want to have root with the stock rom, nothing else just root.
So I am gonna use the tool provided here,
http://forum.xda-developers.com/showthread.php?t=1544940
I have already installed drivers and have the tool downloaded.
Then I would like to flash the stock google 4.0.4 rom that will let me receive OTA updates. Is this the right file?
http://forum.xda-developers.com/showthread.php?t=1569509
Or can I just flash the stock rom from here?
http://forum.xda-developers.com/showthread.php?t=1572307
I heard there are problems flashing stock rom with CWR if the stock recovery isnt removed? Thats why I dont know if I should flash the stock image.
Is the process of flashing rom with CWR recovery the same as with stock recovery?
My phone is the i9023.
Thanks a bunch in advance.

Gambler_3 said:
I am on stock 4.0.4 with a locked bootloader. I want to have root with the stock rom, nothing else just root.
So I am gonna use the tool provided here,
http://forum.xda-developers.com/showthread.php?t=1544940
I have already installed drivers and have the tool downloaded.
Then I would like to flash the stock google 4.0.4 rom that will let me receive OTA updates. Is this the right file?
http://forum.xda-developers.com/showthread.php?t=1569509
Or can I just flash the stock rom from here?
http://forum.xda-developers.com/showthread.php?t=1572307
Is the process of flashing rom with CWM recovery the same as with stock recovery?
Thanks in advance.
Click to expand...
Click to collapse
Baseband version? under about phone

billchen0014 said:
baseband version? Under about phone
Click to expand...
Click to collapse
i9023xxki1.
Sorry should have specified my phone in the OP.

Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).

Harbb said:
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Click to expand...
Click to collapse
You suppose thats better to do manually so I will have latest version of recovery and superuser?
And yes I am aware of the data loss waited sometime to finish all my games now I am ready to lose all my app data.

Harbb said:
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Click to expand...
Click to collapse
Do it this way. The one click is fine but using Android SDK and going through all that will help you in the long run. This way you know the process in case something goes wrong. It may be confusing at first but worth it. It will teach you a lot more than flashing a one click!
I learnt a lot from this and feel much more experienced and capable because of it. I know I will be able to solve any major issues using Android Debug Bridge (adb).

Okay then I am gonna try the manual way and gonna take out time for it. Now I just need to know what do I flash once I have unlocked bootloader and installed CWR?
I just want the stock google rom and receive OTA if nexus S continues to be supported by google.

You won't need to reinstall the ROM if you are currently on 4.0.4. The ROM stays there as-is. Feel free to do your wipes in recovery and reflash stock 4.0.4 through CWM if you must. You flash CWM to your phone and then superuser through CWM.
Steps:
Setup ADB/fastboot
Bootloader --> fastboot oem unlock --> agree
Bootloader --> fastboot flash recovery recovery.img --> this will give you CWM
Recovery --> flash superuser.zip and, if you must, wipe and reflash ICS (flash su AFTER this if done)
Reboot --> bingo
Also note, with stock ROMs it will replace your current recovery with stock recovery on each boot. If you want to keep CWM, delete /system/etc/flash-recovery.sh when you first boot. You'll have to reflash recovery afterward and it will stick.

Oh I was of the impression that unlocking bootloader wipes everything means it wipes the OS as well. That is nice if it's just data and not the OS, dont think I would reflash it if it's not needed.
Can you explain what you mean by will have to reflash recovery? I will have to do that even if I delete that file on first boot? And whats the drawback if I dont delete that file and stick with stock recovery?

As soon as you boot into stock android it will replace the recovery. So if that file is there on first boot, it will replace it while booting and you will be without CWM (stock instead). After first boot you can delete the file (you can reflash a ROM which has this deleted, or delete it yourself from a stock ROM, or even use adb or a recovery-based file manager to delete the file, then you won't have this problem at all) and it will no longer reflash stock recovery, but you would already have the stock one and need to flash CWM one more time to get it to stick. Easiest way is to just flash CWM and delete it within android imo, saves mounting commands and the such.
No downside really. If you need to flash something for one reason or another you'll just have to reflash CWM before you do so. Once rooted, ROM Manager can do this for you within android anyway.

I had already downloaded and installed the drivers from the one click root thread and my computer shows the android adb thing when I connect my phone with USB debugging.
But as you guys suggested I am gonna do the manual way. So do I just skip the installing driver on computer in the part 1 of this guide?
http://forum.xda-developers.com/showthread.php?t=1007782

In my bootloader menu why is it showing my phone as an i9020?? Is it normal?

Gambler_3 said:
In my bootloader menu why is it showing my phone as an i9020?? Is it normal?
Click to expand...
Click to collapse
Because you have a Nexus S with amoled. That's the i9020. The i9023 is SLCD.

DeuXGod said:
Because you have a Nexus S with amoled. That's the i9020. The i9023 is SLCD.
Click to expand...
Click to collapse
He has the i9023 to my knowledge. It is completely normal, though. Bootloader and recovery for i9020 and i9023 series are the same, this can be attributed to the issue with 4.0.3 recovery backlight not turning on.
If fastboot recognises your phone in the bootloader (the fastboot menu), your drivers are installed an working perfectly.

Finally got to the unlock bootloader screen, didnt do it just yet but now I know how to do it.
I must say the guide is a bit outdated, the software has changed quite a bit seems. The most frustrating part was that the fastboot file is actually in the platform tools folder instead of the tools folder which I didnt figure for a while. I will hold off rooting when I have a whole day off because once I lose everything I would be very anxious to get my phone back to normal which will take time.
Thanks for the help harbb, if I have any problem flashing recovery and superuser I will come back for more help.
And yes I have the LCD version i9023.

Btw the guide said the fastboot will be in the tools folder but the tools folder had a read me that "adb has moved to the platform tools folder" this is how I figured to go to that folder and thats where the fastboot file actually was.
Now it says I should put the recovery image in the tools folder so should I do that or put it in the platform tools folder?

In the instructions for the flashing recovery I am not understanding one thing.
6 - Then back on the SNS select Power Off (Reboot also works)
Part 4 - Root
1 - Power ON the SNS
So after flashing recovery I have to reboot? Since I am on stock rom that would bring back the stock recovery so how would I flash superuser then?
If I delete the stock recovery can I still get OTA updates?

fastboot and adb is now in platform tools, that is correct. Easiest way is to put your recovery in there too so you don't have to type in the absolute file path to it, don't put it in tools.
Don't power off or reboot the phone. After you flash recovery go straight into the recovery menu and root, flash custom ROMs, kernels, etc. You can transfer files to flash via the mounts and storage --> mount usb storage menu. After this feel free to reboot.

Harbb said:
fastboot and adb is now in platform tools, that is correct. Easiest way is to put your recovery in there too so you don't have to type in the absolute file path to it, don't put it in tools.
Don't power off or reboot the phone. After you flash recovery go straight into the recovery menu and root, flash custom ROMs, kernels, etc. You can transfer files to flash via the mounts and storage --> mount usb storage menu. After this feel free to reboot.
Click to expand...
Click to collapse
Just wanted to update that I successfully unlocked and rooted. Thanks a bunch mate.

Gambler_3 said:
Just wanted to update that I successfully unlocked and rooted. Thanks a bunch mate.
Click to expand...
Click to collapse
Good work, been wandering what you were up to on this
Hope you enjoy the possibilities.

HOLD ON THIS!!! How To Update TMOUS to 1.84 when Rooted!

HOLD ON UPDATING!!! There are a bunch of people having data and wifi issues with this release. I have not had them but that doesn't mean you won't. Update at your OWN risk. You've been warned.
If you would like to update the software but not the baseband (probable cause for data/wifi issues) then just use my Nandroid linked below and leave your current baseband.
To everyone that keeps trying to relock their phones and flash the RUU to get the update it will NOT work. If you look at your software version you will see that it has added and R2 in it. I don't know why it does this, maybe it's a why for HTC to screw over the hackers yet again. Here is how to get the update.
There are 2 ways to get the update.
First: Use my Stock Rooted 1.84 Nandroid that I posted here. Simple but you will have to flash the radio separate.
Second: More steps but worked for me. NOTE: Only works if your on stock rooted phone. Will not work on custom ROM. Get Stock 1.53 Nandroid here. Credit to Reviewers for posting.
This will NOT wipe your phone nor do you need to wipe your phone if you are on Stock Rooted.
1a - This step only needed if you are on a custom ROM. If your on Stock Rooted then proceed to step 1b.
Download the above linked Nandroid (for 1.53) and restore it in Recovery. Reboot.
1b - Download this tool and use it to flash stock recovery. It will auto reboot your phone into bootloader so just start with your phone normally booted.
Credit goes to hasoon2000 for creating the tool!
2 - Your phone will reboot, once booted back up go to Settings>About Phone>Software Update. It will find the update and download then prompt to install. Select yes and let your phone update and reboot.
3 - Fire up the tool from step 1b again and this time flash CWM Recovery (whichever you prefer).
4 - After reboot is complete reboot again back into recovery and flash this to restore SU permissions (seems the update breaks them, at least for me).
Credit goes to Chainfire for creating this!
5 - Reboot, Done.

Any way to force the update if you have already received it once? I downloaded it yesterday but it failed because I had CWM installed at the time. I've flashed back to stock recovery but when I check for an update it says one isn't available.
I wonder if I could call T-Mobile and have them push it again?

DigitalMonk said:
Any way to force the update if you have already received it once? I downloaded it yesterday but it failed because I had CWM installed at the time. I've flashed back to stock recovery but when I check for an update it says one isn't available.
I wonder if I could call T-Mobile and have them push it again?
Click to expand...
Click to collapse
Did you totally wipe your phone? If not then the update is in your " download" folder
Sent from my HTC One S

Yeah, I know it's in Download, I posted about that in another thread yesterday. But is there some way to flash it now from that file? I thought from reading the other threads there was no flashable version yet, or was that only if you are running CWM?

DigitalMonk said:
Yeah, I know it's in Download, I posted about that in another thread yesterday. But is there some way to flash it now from that file? I thought from reading the other threads there was no flashable version yet, or was that only if you are running CWM?
Click to expand...
Click to collapse
Try deleting that file and checking again. Back it up to your computer first of course.

setzer715 said:
Try deleting that file and checking again. Back it up to your computer first of course.
Click to expand...
Click to collapse
Didn't work for me. I got about 2 downloads out of the servers, and then they aren't sending it anymore. Weak.

No go so far. Copied it to my PC, deleted it from my Download folder, re-booted and then checked for an update 3 different times and nothing so far.

With all of the people having wifi and data issues TMO may have stopped sending it until they figure out what is going on. I do know for a fact that TMO tests any software update the send so something may have gone haywire with it. Maybe got radio mixed up.

DigitalMonk said:
I thought from reading the other threads there was no flashable version yet, or was that only if you are running CWM?
Click to expand...
Click to collapse
Wait.. I didn't know this. You mean even if we "unroot" and flash stock recovery (and using stock ROM of course), we cannot flash this ourselves?
I currently have the CWM touch recovery and root, u/l bootloader, etc., and TMO has sent me 2 updates, both were in the Downloads folder. I didn't notice that it updated (as I never confirmed) but they obviously didn't install.
But I would have done the above if I had known we couldn't just flash it ourselves. WTF T-mobile?? Those of us who know how to flash a file should at least not be prevented from doing so (especially since we need to have the original recovery installed).
Sent from my HTC One-S (rooted), stock ROM

[Q] Problems after flashing ROM-Samsung Tab 3 sm-t311

Hi, I have bought a samsung tab 3 sm-t311 in China and since they everything related to google, I rooted it and installed CWM,
I installed this rom here with CWM: http://forum.xda-developers.com/showthread.php?t=2404877
Installation was successful but I get this messages when launching my device:
- setup wizard isn't responding. Do you want to close it?
I close it, then:
- Unfortunately, the process android.process.media has stopped.
I press ok, then:
Unfortunately, Samsung keyboard has stopped.
I press ok then:
- Process system isn't responding. Do you want to close it?
I press ok
And it keeps coming back over and over...
What should I do?

Backup
anthony239 said:
Hi, I have bought a samsung tab 3 sm-t311 in China and since they everything related to google, I rooted it and installed CWM,
I installed this rom here with CWM: http://forum.xda-developers.com/showthread.php?t=2404877
Installation was successful but I get this messages when launching my device:
- setup wizard isn't responding. Do you want to close it?
I close it, then:
- Unfortunately, the process android.process.media has stopped.
I press ok, then:
Unfortunately, Samsung keyboard has stopped.
I press ok then:
- Process system isn't responding. Do you want to close it?
I press ok
And it keeps coming back over and over...
What should I do?
Click to expand...
Click to collapse
try fixing permissions in cwm/twrp ,if it does not help then restore your nandroid backup or ask the rom developer for the problem..
it might help you

roshan77ss said:
try fixing permissions in cwm/twrp ,if it does not help then restore your nandroid backup or ask the rom developer for the problem..
it might help you
Click to expand...
Click to collapse
Hi, thanks for replying. I cannot post in the topic of the rom because I am new on the forum (what I get when I try to post something overthere).
Could you please explain me how to fix the permissions in CWM?
I am a beginner who been trying to fix his tablet for a week now, but I still dont understand everything since I cant put all my time on it... If its not about following tutorials step by step, i am lost...

I also tried the fast team one, without any success, when the rom is installed and the device is rebooted, this time the screen stay blocked on "samsung galaxy tab3" for years!!!

sorry, i meant the fast dream rom

I just tried to Flash three roms from sammobile.com (one from hong-kong, one from spain and one from germany) through Odin.
Everytime I get I click on AP to load the rom on odin, I get this message:"md5 error! Binary is invalid".
Since I have rooted the tablet using odin to instal CWM, when I boot the tablet in download mode, I can see:
- PRODUCT NAME: SM-T311
- CURRENT BINARY: Cusom
- SYSTEM STATUS: Custom
Is it related? Someone help plz...

The question is do i really have to install a new rom, now that the tablet is rooted with CWM on it, can't do any manipulation to allow the chinese rom to accept google playstore etc...
My biggest problem with the chinese rom that comes with it is that i cant install download google playstore, i installed it but everytime i open it, it closes right away. Not google nor other google apps available neither since it was sold in china...

anthony239 said:
Hi, thanks for replying. I cannot post in the topic of the rom because I am new on the forum (what I get when I try to post something overthere).
Could you please explain me how to fix the permissions in CWM?
I am a beginner who been trying to fix his tablet for a week now, but I still dont understand everything since I cant put all my time on it... If its not about following tutorials step by step, i am lost...
Click to expand...
Click to collapse
You should be able to post on ROM forum now(as you've reached 10 posts.
And the fix permissions option should be in 'advanced' section in CWM(not sure, I use TWRP recovery)

The Dork Knight Rises said:
You should be able to post on ROM forum now(as you've reached 10 posts.
And the fix permissions option should be in 'advanced' section in CWM(not sure, I use TWRP recovery)
Click to expand...
Click to collapse
Yea im able to post over there now, thx

backup
anthony239 said:
The question is do i really have to install a new rom, now that the tablet is rooted with CWM on it, can't do any manipulation to allow the chinese rom to accept google playstore etc...
My biggest problem with the chinese rom that comes with it is that i cant install download google playstore, i installed it but everytime i open it, it closes right away. Not google nor other google apps available neither since it was sold in china...
Click to expand...
Click to collapse
dont you have cwm backup? if not then flash stock firmware ,find proper odin flashable packages for your device.
always make backup before flashing any rom.

anthony239 said:
Yea im able to post over there now, thx
Click to expand...
Click to collapse
So, could the devs help??
(<---And you don't need to say thanks and spam the thread, that what the button's for)

The Dork Knight Rises said:
So, could the devs help??
(<---And you don't need to say thanks and spam the thread, that what the button's for)
Click to expand...
Click to collapse
In the end, I just used a previous version of Odin (3.4 instead of 3.9) to flash an original stock rom.
Now the problem is that I have a new CWM that works with the volume up, volume down button, and this menu:
- reboot system now
- apply update from ADB
- apply update from external storage
- zipe data/factory reset
- wipe cache partition
- apply update from cache
Since the rom is not really good, i wanted to flash another one (one of those we just talked about), but the backup i did with the previous CWM i had (Philz Advanced CWM 6.08.90) is nowhere in the tablet anymore (i dont have any sd card) and i dont know how to make a back up with this CWM...
So now the question is how to make a backup with this version of CWM so I can try to flash other roms, or how to get the version that i had before without takin any risk of brickin the device (so i can make another backup and try to flash another)

anthony239 said:
In the end, I just used a previous version of Odin (3.4 instead of 3.9) to flash an original stock rom.
Now the problem is that I have a new CWM that works with the volume up, volume down button, and this menu:
- reboot system now
- apply update from ADB
- apply update from external storage
- zipe data/factory reset
- wipe cache partition
- apply update from cache
Since the rom is not really good, i wanted to flash another one (one of those we just talked about), but the backup i did with the previous CWM i had (Philz Advanced CWM 6.08.90) is nowhere in the tablet anymore (i dont have any sd card) and i dont know how to make a back up with this CWM...
So now the question is how to make a backup with this version of CWM so I can try to flash other roms, or how to get the version that i had before without takin any risk of brickin the device (so i can make another backup and try to flash another)
Click to expand...
Click to collapse
Are you sure the new recovery is CWM and not stock recovery?? If you flashed stock ROM, it should've given you stock recovery again...
(Does it show the CWM hat logo in the background?)

The Dork Knight Rises said:
Are you sure the new recovery is CWM and not stock recovery?? If you flashed stock ROM, it should've given you stock recovery again...
(Does it show the CWM hat logo in the background?)
Click to expand...
Click to collapse
Actually, yea its the stock recovery, so should i reroot the phone to install CWM, make a backup just in case, flash another stock rom which i find better, and then try to flash this one in recovery mode?

anthony239 said:
Hi, I have bought a samsung tab 3 sm-t311 in China and since they everything related to google, I rooted it and installed CWM,
I installed this rom here with CWM: http://forum.xda-developers.com/showthread.php?t=2404877
Installation was successful but I get this messages when launching my device:
- setup wizard isn't responding. Do you want to close it?
I close it, then:
- Unfortunately, the process android.process.media has stopped.
I press ok, then:
Unfortunately, Samsung keyboard has stopped.
I press ok then:
- Process system isn't responding. Do you want to close it?
I press ok
And it keeps coming back over and over...
What should I do?
Click to expand...
Click to collapse
Try fix or patch.
Or come back to stock rom.

anthony239 said:
Actually, yea its the stock recovery, so should i reroot the phone to install CWM, make a backup just in case, flash another stock rom which i find better, and then try to flash this one in recovery mode?
Click to expand...
Click to collapse
Yup, I think you'd better to start over again. Try take a look at this : http://forum.xda-developers.com/showthread.php?t=2401901
It works well for my SM-T311 :good: Then you can reroot and make a backup from TWRP easily.
I also suggest you to take a look at this too : http://forum.xda-developers.com/showthread.php?t=2522091 From there, you can get PhilZ touch recovery based on CWM v.6.0.4.5

anthony239 said:
Actually, yea its the stock recovery, so should i reroot the phone to install CWM, make a backup just in case, flash another stock rom which i find better, and then try to flash this one in recovery mode?
Click to expand...
Click to collapse
That's right, look at @Ferris Cruiser's post above. Should help.
(<---Remember to thank him and me if this helps.:good

Ok, my problem is resolved now.
- I had to use the previous version of Odin (3.4) to flash a rom from sammobile.com
- Then, I rooted the phone, reinstalling CWM philz version
- I did a backup using CWM
- Finally I flashed the custom rom using CWM
Thank u all for helping

anthony239 said:
Ok, my problem is resolved now.
- I had to use the previous version of Odin (3.4) to flash a rom from sammobile.com
- Then, I rooted the phone, reinstalling CWM philz version
- I did a backup using CWM
- Finally I flashed the custom rom using CWM
Thank u all for helping
Click to expand...
Click to collapse
Glad to help! :good:

HELP
I bought a Samsung Galaxy Tab 3 SM-T311 in Mainland China last month and I cannot install google play can anyone help.