Database Info

Question about CWM before ICS update

I just rooted my TF101 using ViperMod but now I'm not sure whether I should install CWM recovery or not if I want to install further OTAs. I have read some threads but couldn't come up with a clear answer. I read somewhere that only stock recovery can receive OTA updates but also read that CWM can receive them too. If I can't install CWM then what ROMs can I install with stock recovery? What's the best way to go if I want to be ready for the ICS? Thanks!!

theremix said:
I just rooted my TF101 using ViperMod but now I'm not sure whether I should install CWM recovery or not if I want to install further OTAs. I have read some threads but couldn't come up with a clear answer. I read somewhere that only stock recovery can receive OTA updates but also read that CWM can receive them too. If I can't install CWM then what ROMs can I install with stock recovery? What's the best way to go if I want to be ready for the ICS? Thanks!!
Click to expand...
Click to collapse
Technically you'll still receive the OTA update you just can't apply it if you have CWM or a custom ROM installed.
You can't install custom ROM without CWM (if you have an older SBK tablet you can use NVFlash with a compatible ROM).

So I shouldn't install cwm until the ICS drops right?
Sent from my Transformer TF101 using Tapatalk

If you want to update to ICS via OTA don't instal CWM.
As you have been told, you will get the OTA message but the update will fail.
So you have two choices (or three):
* Keep stock recovery and update to ICS when the OTA update is available
* Install CWM and update to ICS as soon as a DEV publishes an ICS ROM
* Install CWM and remove it as soon as you know the OTA is due (pretty lame, but you could do it).
Regards.

CalvinH said:
If you want to update to ICS via OTA don't instal CWM.
As you have been told, you will get the OTA message but the update will fail.
So you have two choices (or three):
* Keep stock recovery and update to ICS when the OTA update is available
* Install CWM and update to ICS as soon as a DEV publishes an ICS ROM
* Install CWM and remove it as soon as you know the OTA is due (pretty lame, but you could do it).
Regards.
Click to expand...
Click to collapse
Thanks, I think I'll just wait for the OTA as I want to update as soon as ICS drops in.
Sent from my PC36100 using Tapatalk

I have a question about removing CWR. Actually 2.
1. Can't we just uninstall and wipe data with Titanium since it was installed as an .apk- from Gnufabio? (pretty sure this won't work but thought I would throw it out there anyways). Where is the recovery located on a tablet (what folders) Same as in phones?
2. Can we just flash the stock recovery by itself and not reset back to .13 or younger? If I am running stock ROM, it seems that I should be able to just reflash the stock recovery and replace it w/o changing the ROM or factory reset.
I have no problem doing it the long way but if it doesn't need to be done and we can replace the CWR with stock and not tamper with the ROM, it seems logical.
Clearly I just got the tab recently and have been reading and reading but they seem so much different than the way phones work. I am very comfortable flashing ROMs/Kernels/Mods on phones, but just a little intimidated with the tablet (for now).

Woodrube said:
I have a question about removing CWR. Actually 2.
1. Can't we just uninstall and wipe data with Titanium since it was installed as an .apk- from Gnufabio? (pretty sure this won't work but thought I would throw it out there anyways). Where is the recovery located on a tablet (what folders) Same as in phones?
2. Can we just flash the stock recovery by itself and not reset back to .13 or younger? If I am running stock ROM, it seems that I should be able to just reflash the stock recovery and replace it w/o changing the ROM or factory reset.
I have no problem doing it the long way but if it doesn't need to be done and we can replace the CWR with stock and not tamper with the ROM, it seems logical.
Clearly I just got the tab recently and have been reading and reading but they seem so much different than the way phones work. I am very comfortable flashing ROMs/Kernels/Mods on phones, but just a little intimidated with the tablet (for now).
Click to expand...
Click to collapse
1- The RecoveryInstaller app only help to flash the recovery image so no you can just delete it.
2- You can flash a stock recovery image via CWM. You can get a repacked version here.
http://forum.xda-developers.com/showthread.php?t=1154947&highlight=unroot

baseballfanz said:
2- You can flash a stock recovery image via CWM. You can get a repacked version here.
http://forum.xda-developers.com/showthread.php?t=1154947&highlight=unroot
Click to expand...
Click to collapse
I figured that would be the case with the executable part of the apk.
I read that thread but wasn't sure if only the stock recovery by itself could be flashed w/o the prepacked ROM.

[Q] Revert to stock ICS after JB OTA?

I was running ICS on my One S (S3). Installed TrickDroid v5 (JB), but there were a couple of issues with it. So I decided to go back to ICS. I just ran the 2.15 RUU. And I was back on ICS. A day later I got the JB OTA. Installed that, everything was working great, until I tried doing something stupid, and managed to wipe the entire phone.
Long story short, I got the phone working again, by putting in TrickDroid v5 again. Thing is, I want the official JB OTA. How do I do this? There aren't any RUU's for JB. I tried downloading this: http://forum.xda-developers.com/showpost.php?p=37398225&postcount=41 for my CID (J15).
I don't know how to install it though. I just put it on my sdcard, and tried to install it with TWRP. It just give me a bunch of errors. I also tried running the older ICS 2.15 RUU. It doesn't work either. Just says older hboot.
What I want to do is to revert back to stock ICS, so that I can get the JB update again? Is this possible? Or anything else I can do?
Any ideas, anyone?

firefiber said:
I was running ICS on my One S (S3). Installed TrickDroid v5 (JB), but there were a couple of issues with it. So I decided to go back to ICS. I just ran the 2.15 RUU. And I was back on ICS. A day later I got the JB OTA. Installed that, everything was working great, until I tried doing something stupid, and managed to wipe the entire phone.
Long story short, I got the phone working again, by putting in TrickDroid v5 again. Thing is, I want the official JB OTA. How do I do this? There aren't any RUU's for JB. I tried downloading this: http://forum.xda-developers.com/showpost.php?p=37398225&postcount=41 for my CID (J15).
I don't know how to install it though. I just put it on my sdcard, and tried to install it with TWRP. It just give me a bunch of errors. I also tried running the older ICS 2.15 RUU. It doesn't work either. Just says older hboot.
What I want to do is to revert back to stock ICS, so that I can get the JB update again? Is this possible? Or anything else I can do?
Any ideas, anyone?
Click to expand...
Click to collapse
In order to load an RUU from rooted device. First you have to relock your boot loader. Then all you have to do is connect the phone in fastboot usb to computer and run the RUU file on the PC.
One thing to note is that this only works if you are loading an RUU which is the same version you currently have or updated version. Can't get a previous version from one you have already. So I am guessing you have to downgrade your hboot or change your CID which is much more complicated and risky.
Sent from my One S using Xparent Skyblue Tapatalk 2

LikeaG2root said:
In order to load an RUU from rooted device. First you have to relock your boot loader. Then all you have to do is connect the phone in fastboot usb to computer and run the RUU file on the PC.
One thing to note is that this only works if you are loading an RUU which is the same version you currently have or updated version. Can't get a previous version from one you have already. So I am guessing you have to downgrade your hboot or change your CID which is much more complicated and risky.
Sent from my One S using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Mate that link wasn't an executable RUU. There aren't any executable JB RUU's. It's a zip file. I don't know how to install it. I tried to flash it in TWRP, and like I said, it just gives me a bunch of errors.
So is there any way to downgrade my HBOOT? I already tried installing an older ROM (Trickdroid with ICS). And then from there, trying to update. Doesn't work. So basically, I need to downgrade my hboot. If ANYONE can tell me if there's a way to do that, that would be awesome.

firefiber said:
Mate that link wasn't an executable RUU. There aren't any executable JB RUU's. It's a zip file. I don't know how to install it. I tried to flash it in TWRP, and like I said, it just gives me a bunch of errors.
So is there any way to downgrade my HBOOT? I already tried installing an older ROM (Trickdroid with ICS). And then from there, trying to update. Doesn't work. So basically, I need to downgrade my hboot. If ANYONE can tell me if there's a way to do that, that would be awesome.
Click to expand...
Click to collapse
Its very risky and you need Ubuntu to do this...http://forum.xda-developers.com/showthread.php?p=34076562
Sent from my One S using Xparent Skyblue Tapatalk 2

Yeah I was thinking of trying that, but the thing is, it says I shouldn't try it if I took the JB OTA. Which I did. So now I'm not sure how to proceed.

firefiber said:
Yeah I was thinking of trying that, but the thing is, it says I shouldn't try it if I took the JB OTA. Which I did. So now I'm not sure how to proceed.
Click to expand...
Click to collapse
You need a 4.0.4 customrom which is based one the official release/close to stock.
Like zenRom for the S4 Version.
Maybe there is a similar one for the S3.
If you find one, do a clean install off the rom, boot full. Flash stock recovery. (You dont have to relock your bootloader, its only for RUUs)
Do a factory reset. Boot your phone and you will receive the official jb ota.
After receiving and installing the ota i recommend you to do a factory reset again.
If everything works fine, you should have a clean official jellybean Rom.
This procedure worked with the s4 Version, i can confirm it twice

[SOLVED] Need To Fuly Revert To Stock

Hello, my HTC One S was fine on the stock things, but I decided to root it and add a custom ROM.
Bad idea.
I can't install Linux, so I can't downgrade the bootloader, and I can't find any ROMs where wifi will work without doing so. How can I revert to full stock, or is there a ROM where wifi works on hboot version 1.14?
Click to expand...
Click to collapse
I no longer need to downgrade to get the WiFi thanks to this great post here: WiFi Fix
I hope this helps people in the future.

All roms wifi works fine for me on hboot 1.14...

Vuciz said:
Hello, my HTC One S was fine on the stock things, but I decided to root it and add a custom ROM.
Bad idea.
I can't install Linux, so I can't downgrade the bootloader, and I can't find any ROMs where wifi will work without doing so. How can I revert to full stock, or is there a ROM where wifi works on hboot version 1.14?
Click to expand...
Click to collapse
i regret rooting my phone.. i cant sell it because they dont want a rooted phone

Re: Need To Fuly Revert To Stock
There's a guide somewhere in here how to revert to stock. I used it and worked perfectly. You should be able to find it using the search .
Basically the procedure goes like this:
1. Install zenROM (it's in the dev section).
2. Install stock recovery (also posted here in several threads)
3. Boot the phone into zenROM and look for OTA updates. ZenROM can find and install official updates.
4. Once updates are ready, you should be running stock JB rom.
5. Relock bootloader, or root or whatever. Now you are on the stock rom.
Of course this requires that there is a JB update available for your CID.
Sent from my HTC One S using xda app-developers app

zaak00 said:
There's a guide somewhere in here how to revert to stock. I used it and worked perfectly. You should be able to find it using the search .
Basically the procedure goes like this:
1. Install zenROM (it's in the dev section).
2. Install stock recovery (also posted here in several threads)
3. Boot the phone into zenROM and look for OTA updates. ZenROM can find and install official updates.
4. Once updates are ready, you should be running stock JB rom.
5. Relock bootloader, or root or whatever. Now you are on the stock rom.
Of course this requires that there is a JB update available for your CID.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
so let me post it the fourth time ..
http://forum.xda-developers.com/showpost.php?p=37942416&postcount=2

Usually you'll find answers to your problems in the according rom section as you're not the only one with it.
But as you are pretty new here:
1. You can use Linux livecd for downgrading. More here. The process isn't that easy so and you'll need to be patient and careful. (I did that couple of times on my device. The first time it was really worse also I was/am not new to Linux).
2. 1.14 means you have been on ICS only so far. So any ICS rom should work for you. If there is still trouble with wifi, search for answers in that rom section. I remember some guys editing a file for enabling/boosting wifi. As I'm not concerned by this, I have no links.
3. If you'd like to move to JB roms search for 'flashing wifi partitions' as long as you want to keep 1.14. If flashing the OTA update for JB your bootloader version will be 2.15 and the according wifi partitions will be working as well. For both, ICS and JB.
Substantially there will be no real differences for you between 1.14 and 2.15 as only with 1.06 and 1.09 you don't need to flash kernels via fastboot mode.
Hope you got the point as my answer is very short.

[Q] Rooted ICS to JB - check my sanity please :)

After two weeks of forum crawling and surviving 2 soft-bricking incidents, I've finally decided to reach out for help from the experts :crying:
Currently I have an ATT HOX, unlocked/rooted/SuperCID - running stock ICS (4.0.4).
My goal is to get JB on it and then flash to Blade ROM (I tried flashing to Blade with ICS - OOPS!)
Even though the info is on the forums - it's not all together in a streamlined format for me to follow - I feel I could get lost and screw it up (again)
From what I gathered from reading - here is what I "think" I need to do from my current phone state:
1. Facepalm S-Off
2. Install OTA Rootkeeper then backup root
3. Flash stock recovery
4. Re-Lock Bootloader
5. Flash OTA ATT JB.zip using stock recovery
6. Unlock Bootloader
7. Flash TWRP
8. Restore backup root with OTA RK
9. Flash Blade ROM
Can someone please check my thinking and make sure I'm not missing something?
Or any recommendation of an easier process? I feel I'm going to get lost somewhere in those steps and end up in Oz.
Or maybe a recommendation on an awesome ICS Rom? (so I can avoid confusing myself)
I'm terrified of another 3AM morning and a bricked-out HOX.
Thanks in advance!

Do you mean this rom: http://forum.xda-developers.com/showthread.php?t=2134328?
Because that's a rom for the quad-core Tegra One X. If you've been doing that, it's no wonder you got bricked.
You don't need OTA Rootkeeper. You can just flash a rooted rom.

2 major points:
1) As already mentioned, Blade is not for our phone, its for the quad core One X. Stay within this forum section. If you are looking at any XDA thread that just says "HTC One X" (no mention of "AT&T, Rogers" etc.) near the top of the screen, you are in the wrong section. Stick to the forum section that mentions AT&T. Flashing a ROM for the quad core version won't work, and might also hard brick your phone.
2) Aside from S-Off which is a good idea) you don't need to mess with any of the stuff you mentioned (Rootkeeper, stock recovery, OTA zip) in order to flash a JB based custom ROM if you are already bootloader unlocked and have TWRP. With S-off, just flash the ROM. If S-on, just flash the ROM, then flash the boot.img with fastboot (if hboot 1.14 or higher).
I'm not sure how you got the notion that you need to do all these other steps (maybe some process for the quad core forum?).

redpoint73 said:
I'm not sure how you got the notion that you need to do all these other steps (maybe some process for the quad core forum?).
Click to expand...
Click to collapse
<---- desperate noob
...and I also came from the original Samsung Vibrant. With that phone, I also had the idea that I could only use a ROM based of the current android version. Hence the carry over of thought from that side.
I can't believe I lost sleep over the simplicity of it all.
But.... just to make sure I understand this correctly - Even if I have ICS currently installed, I can flash a JB based ROM without issues?
Thanks a ton guys!

razorc03 said:
But.... just to make sure I understand this correctly - Even if I have ICS currently installed, I can flash a JB based ROM without issues?
Click to expand...
Click to collapse
Correct you can flash it.
But some people have been having issues on JB coming from older firmware. If you have problems later, then ruu'ing and updating is warranted. Right now it's overkill.

iElvis said:
Correct you can flash it.
But some people have been having issues on JB coming from older firmware. If you have problems later, then ruu'ing and updating is warranted. Right now it's overkill.
Click to expand...
Click to collapse
Would I be able to RUU to a stock JB? Or would I have to start from stock ICS again?

razorc03 said:
Would I be able to RUU to a stock JB? Or would I have to start from stock ICS again?
Click to expand...
Click to collapse
There are no JB ruu's as far as I know. But you can run the 2.20 ruu and then flash the 3.18 ota, then unlock again and reflash everything. That's what I did. Whole process took about half an hour and wasn't complicated. Just be sure you're s-off.

iElvis said:
There are no JB ruu's as far as I know. But you can run the 2.20 ruu and then flash the 3.18 ota, then unlock again and reflash everything. That's what I did. Whole process took about half an hour and wasn't complicated. Just be sure you're s-off.
Click to expand...
Click to collapse
Thanks for the info. But I need to bug you again.:angel:
A few questions about the ruu method. After you ruu, does that remove root, lock bootloader, and goes back to s-on?
And since I love numbered steps, here is how I am viewing it with my inexperienced understanding with question marks:
1. Check for S-off
2. Lock bootloader? (I guess not with S-off)
3. Run ruu 2.20 exe
4. Flash 3.18 ota
5. Rerun superCID (X-Factor xploit)?
6. Unlock bootloader
7. Flash TWRP
8. Flash ROM (Assuming S-off wasn't changed during the ruu)
I would love to be at your confidence level to run it it 30 minutes. One day I guess....

Before you run a ruu, you have to relock. When you run it, it wipes your entire phone and returns it to stock-out-of-the-box (except for s-off). So you need to back up anything you want to keep.
Here's a corrected list:
1. S-off
2. Relock in fastboot
3. Run ruu
4. Copy OTA update.zip to internal storage
5. Flash in stock recovery
6. Unlock
7. Flash custom recovery
8. Flash rooted rom
None of this affects s-off. AFAIK, the only way to be s-on again is manually change it in fastboot.
I wouldn't do all this unless you have a reason to, as there are spots in here where you can get tripped up if you're a complete noob.

iElvis said:
Before you run a ruu, you have to relock. When you run it, it wipes your entire phone and returns it to stock-out-of-the-box (except for s-off). So you need to back up anything you want to keep.
Here's a corrected list:
1. S-off
2. Relock in fastboot
3. Run ruu
4. Copy OTA update.zip to internal storage
5. Flash in stock recovery
6. Unlock
7. Flash custom recovery
8. Flash rooted rom
None of this affects s-off. AFAIK, the only way to be s-on again is manually change it in fastboot.
I wouldn't do all this unless you have a reason to, as there are spots in here where you can get tripped up if you're a complete noob.
Click to expand...
Click to collapse
Thanks for the checklist! It makes me feel safer to know an exit strategy so I don't panic if/when stuff goes bad.
I noticed you didn't list a step to re-root through custom recovery after step 7. Is the previous root still in place?

razorc03 said:
...and I also came from the original Samsung Vibrant. With that phone, I also had the idea that I could only use a ROM based of the current android version. Hence the carry over of thought from that side.
Click to expand...
Click to collapse
This varies completely by device, and firmware versions. Never assume that something you learned on another Android device applies to a different device.

razorc03 said:
I noticed you didn't list a step to re-root through custom recovery after step 7. Is the previous root still in place?
Click to expand...
Click to collapse
No, it's that once you're unlocked, you can re-root just by flashing a rooted rom.

Jelly Bean OTA

FOTA ripped for your enjoyment.
https://mega.co.nz/#!xoZigSqS!YHUa5Umv-8qjyFV1dtHs4lDQXMIn1q7plTz3zWeYSwY
That's completely unmodified. (I tried just installing it in CWM. Think I probably bricked doing something silly...)

I pulled this as well, but I'm curious if you had to flash back to stock firmware and recovery to get it. I tried using a rooted stock rom and the software update screen would give me a "modified devices don't get updates" message. I actually had to have stock recovery and system installed so that it would download. Did you have to do the same thing?

gee one said:
I pulled this as well, but I'm curious if you had to flash back to stock firmware and recovery to get it. I tried using a rooted stock rom and the software update screen would give me a "modified devices don't get updates" message. I actually had to have stock recovery and system installed so that it would download. Did you have to do the same thing?
Click to expand...
Click to collapse
Interestingly enough, it downloaded perfectly fine for me, even though my device was "modified"...

bigleague4040 said:
Interestingly enough, it downloaded perfectly fine for me, even though my device was "modified"...
Click to expand...
Click to collapse
I have a modified boot.img- perhaps that blocks the ota?

My device is rooted.
It is on 4.2.1 genuine T-mobile software.
When I want to update OverTheAir this message pop out.
See attachement (I don't know how to put image here).
What can I do to update OTA?

I played around with this a while ago (my flash counter is at 29 last time I checked).
I think you have a few options:
1) maybe unroot and that might remove the modified status
2) use heimdall or odin to flash back to unrooted stock, including stock recovery and boot.img
3) flash one of the rooted JB roms, either stock, cyanogen, or our very own Teamapexq rom
4) download the OTA or the JB rom from the web and repackage it yourself to a flashable zip.
Option 1 might not work. Option 2-4 will work, 4 would be the most fun.
sent while running with scissors

gee one said:
I played around with this a while ago (my flash counter is at 29 last time I checked).
I think you have a few options:
1) maybe unroot and that might remove the modified status
2) use heimdall or odin to flash back to unrooted stock, including stock recovery and boot.img
3) flash one of the rooted JB roms, either stock, cyanogen, or our very own Teamapexq rom
4) download the OTA or the JB rom from the web and repackage it yourself to a flashable zip.
Option 1 might not work. Option 2-4 will work, 4 would be the most fun.
sent while running with scissors
Click to expand...
Click to collapse
OMG, I would like to do it with no hassle.
I just want something to work ... grrr.

Option 2 would probably be the most straightforward. Essentially, you are unrooting. I just remembered, Samsung has Kies which might restore it to stock. You can download it from their website.
sent while running with scissors

mazak23 said:
My device is rooted.
It is on 4.2.1 genuine T-mobile software.
When I want to update OverTheAir this message pop out.
See attachement (I don't know how to put image here).
What can I do to update OTA?
Click to expand...
Click to collapse
the update in this thread is only about JB 4.1.2 that is officially the latest and the last one for our mobile. your message box is normal, there is no need for the usage of the OTA anymore since then. if u want to update to JB 4.3 follow this unofficial image:
http://forum.xda-developers.com/showthread.php?t=2463661

Holy thread resurrection Batman!!!
Oh boy. Here we go. Having troubles here.
I am trying to re-flash my phone to stock so I can return it under the protection plan. I firmly believe my radio might be on the fritz.
Anyway, I used the directions here:
http://theunlockr.com/2013/04/25/how-to-unroot-the-samsung-galaxy-s-relay-4g-sgh-t699/
Now it all completed successfully, and the phone is chilling at the SAMSUNG screen trying to boot. Not sure what to do at this point. Its been sitting there for a good 5 minutes.
Please help!!
UPDATE: Went into stock recovery, cleared Cache and Data, then rebooted it again, and it booted!

Which JelyBean Version...!!!
After installing this update what will be my os (JB 4.X.X) version???

saurabhsaurabhrai said:
After installing this update what will be my os (JB 4.X.X) version???
Click to expand...
Click to collapse
it is just from stock, will be updated to JB 4.1.2