Hi eveyone, I updated my stock from 4.0 to 4.1 through odin and it was really painless. Sorry if this sounds lazy but can you install cm the same way? Doing the whole CW etc. seems a lot of steps - i'd rather upload one file only if possible. Thanks!
Guiyoforward said:
Hi eveyone, I updated my stock from 4.0 to 4.1 through odin and it was really painless. Sorry if this sounds lazy but can you install cm the same way? Doing the whole CW etc. seems a lot of steps - i'd rather upload one file only if possible. Thanks!
Click to expand...
Click to collapse
i do not think you can install zip with odin
LitD said:
i do not think you can install zip with odin
Click to expand...
Click to collapse
Thanks. You cannot - what I mean is: is CM ever realeased as a TAR-compatible ODIN file?
That can certainly be done. But it's not the norm.
Sent from my SGH-T699 using Tapatalk
James chdset
Nardholio said:
That can certainly be done. But it's not the norm.
Sent from my SGH-T699 using Tapatalk
Click to expand...
Click to collapse
Thanks Nardholio. I'm obviously missing some important feature CWM offers thatthe "odin process" does not. Is it seamless backup amd restore? Or is it the possibility of adding patches and new stuff - say, gapps on top of CM?
Thanks again!
G.
Deleted because I reposted in the intended thread
Guiyoforward said:
Thanks Nardholio. I'm obviously missing some important feature CWM offers thatthe "odin process" does not. Is it seamless backup amd restore? Or is it the possibility of adding patches and new stuff - say, gapps on top of CM?
Thanks again!
G.
Click to expand...
Click to collapse
CWM offers both of those things as an advantage, yes. You also can use CWM with the Stock image to gain the backup and restore features, amongst others.
And really, if you're already running Stock JB, the process is as simple as:
Place The cm-10.2-XXXXXXXX-NIGHTLY-apexqtmo.zip and gapps zip files on your phone, either on the 'internal' or external SD Card. (This even is optional, as they can be sideloaded if you have adb)
Flash CWM with Odin or Heimdall.
Reboot into recovery
Flash the cm nightly.zip
Flash the gapps.zip
wipe /cache with CWM.
Issue a factory reset with CWM.
Reboot to system.
If you're still on ICS, then you just need to add the steps of flashing the JB-stock-modem.zip and JB-stock-bootloader.zip before flashing the cm-nightly.zip (Turn GPS OFF before flashing these, specifically the modem, just to be on the safe side)
If you perform a backup with CWM before flashing anything, you can restore your stock system as you please.
If you simply want to root your relay, flash an appropriate recovery flashable zip copy of Superuser or SuperSU instead of flashing anything else.
kilr00y, along with providing the JB-stock-modem and JB-stock-bootloader recovery-flashable zip files, also provided a JB-stock-image.zip that can be used to go back to a stock-like system.
CWM allows you for a much greater amount of control over your phone, even when still running a stock image, due to the flexibility of being able to flash new applications directly to the system directories (such as Superuser/SuperSU) without having to have everything be signed by Samsung.
Magamo said:
CWM offers both of those things as an advantage, yes. You also can use CWM with the Stock image to gain the backup and restore features, amongst others.
And really, if you're already running Stock JB, the process is as simple as:
Place The cm-10.2-XXXXXXXX-NIGHTLY-apexqtmo.zip and gapps zip files on your phone, either on the 'internal' or external SD Card. (This even is optional, as they can be sideloaded if you have adb)
Flash CWM with Odin or Heimdall.
Reboot into recovery
Flash the cm nightly.zip
Flash the gapps.zip
wipe /cache with CWM.
Issue a factory reset with CWM.
Reboot to system.
Click to expand...
Click to collapse
THANKS! This is by far the easiest step by step instructions I've seen, and gladly I'm on stock JB already.
Will give this a try
thanks again!
just booted into apex CM 347 nightly after the... ehem... peculiar apex logo thanks a lot for your effort.
now, I am a noob but can find my way around. I still think the whole process (CM and co, not the relay 4g per se) is a bit convoluted and underdocumented. just an example: I downloaded the IMG file from CWM but it took me a while to figure out that I had to transform it into md5 for it to play nice with odin, etc.
buy hey. I'm going to setup my system.
thanks everyone!!
Guiyoforward said:
just booted into apex CM 347 nightly after the... ehem... peculiar apex logo thanks a lot for your effort.
now, I am a noob but can find my way around. I still think the whole process (CM and co, not the relay 4g per se) is a bit convoluted and underdocumented. just an example: I downloaded the IMG file from CWM but it took me a while to figure out that I had to transform it into md5 for it to play nice with odin, etc.
buy hey. I'm going to setup my system.
thanks everyone!!
Click to expand...
Click to collapse
In all honesty, ODIN itself is an underdocumented POS, the recovery.img file (or in this case, the renamed apexq_recovery-10.2.img file if you were following along with the wiki) comes right from the build process, it can be flashed directly without much tooling about with it using heimdal, which is an open source replacement for ODIN, that works very well. Heimdall can be used optionally with a GUI, but I personally use it from the command line, to get it to flash a recovery image to the recovery partition of a Relay, it's simply:
heimdall flash --recovery apexq_recovery-10.2.img
Guiyoforward said:
just booted into apex CM 347 nightly after the... ehem... peculiar apex logo thanks a lot for your effort.
now, I am a noob but can find my way around. I still think the whole process (CM and co, not the relay 4g per se) is a bit convoluted and underdocumented. just an example: I downloaded the IMG file from CWM but it took me a while to figure out that I had to transform it into md5 for it to play nice with odin, etc.
buy hey. I'm going to setup my system.
thanks everyone!!
Click to expand...
Click to collapse
How did you transform the img to md5 (I can also take the cwm in md5 format from the root thread, am I right?) ?
So I can flash anything without root using this method (even recovery) ? I couldn't do this with my desire Z, it's confusing me !
Which recovery should I flash to use cm10.2 (the cwm or the apexq_recovery-10.2.img ?) ?
=> If I use an older recovery I can't flash any jelly been rom's ?
robuser007 said:
(I can also take the cwm in md5 format from the root thread, am I right?)
Click to expand...
Click to collapse
yes, you can
robuser007 said:
So I can flash anything without root using this method (even recovery) ? I couldn't do this with my desire Z, it's confusing me !
Click to expand...
Click to collapse
there are several differences. you can flash recovery via odin to a not rooted device
robuser007 said:
Which recovery should I flash to use cm10.2 (the cwm or the apexq_recovery-10.2.img ?) ?
Click to expand...
Click to collapse
google 'install cyanogenmod samsung relay' and follow 'how to install cyanogenmod for samsung relay' wiki. 'installing cyanogenmod from recovery' is the same as for desire z
Related
Hi. My name is Shaun, and yes this is my first post here ... I would like to say this is an awesome forum full of information. Thanks for being here.
I'll start off with where I am at with my phone, and ultimately, what I want to do, then I will roll with a few questions (actually a lot of questions).
I will give you my phone stats and info to start off with. Some of it may not be pertinent. (All of this is what came out of the box, and I haven't done anything to this phone besides gain su access to it through superoneclick)
-Samsung Galaxy S (Mesmerize through US Cellular)
-Hardware v I500.04
-Firmware v 2.2.1
-Kernel v 2.6.32.9
I have read through the glossary, the stickies, and a few other threads as well. I'm looking to flash a new ROM, of course.
Now with the questions and calls for layman's explanations...
1. My friend, Adam, told me that the next step for me is to "Download ROM Manager and run a back up". I read in a thread this is a no-no, and that I need to get CVM Red Recovery (I saw it in both zip and tar formats). Once I download it, what is the next step? Do I put the zip file on my SD card and boot into the factory recovery and get it there? Do I download "odin" and load it that way? What is the advantage or disadvantage of either method? It seems a bit unclear to me.
2. With the particular ROMs, I read that these packages will sometimes include the kernels. Are these in separate files and need to be flashed separately? If so, how do I know which kernel package matches a particular ROM, if I am even making any sense right now?
3. After putting CVM on my phone, how would one get back to stock?
Conceptually, I think I am missing a bit on how all of this works and the inner workings of a droid, and I'm one that tends to learn these things through diving in it. The fear of "bricking" my precious lifeline to the world is keeping my butthole clinched and myself afraid to make the next move.
First off, welcome. You will find the answers to almost all of your questions in the following stickied threads. Doing your own research and reading a LOT is the best way to get yourself comfortable and ready for rooting. Keep in mind, the only person that can correct anything you screw up is you so make sure you have a good understanding of what you're doing BEFORE you do it. Oh, and don't use ROM Manager. It doesn't work correctly for our phone (yet). Kernels included in Rom's don't need installed separately
Glossary
Step by Step Guide
Info on Kernels
new questions about CVM for mesmerize
In my search for CVM for my mesmerize... I came across this sticky thread in reference to all SCH-I500 models..
http://forum.xda-developers.com/showthread.php?t=1026893
In this thread is a working modified Clockworkmod recovery that is also built to work with all three phones. To flash it, you would either need a recovery that allows you to flash a zip file, or you can flash the tar file in Odin.
Click to expand...
Click to collapse
Where is this said "recovery that allows you to flash a zip file"? Is this the same recovery that I can access when I hold the power and volume buttons to boot the phone? The wording sounds as if I need a "previous recovery" from another source somewhere to do this.
Also, in that same thread there is a link to the CVM needed for these phones. I see CVM3-voodoo, CVM3-voodoo blue, and CVM-voodoo purple... is the first in the list the "red recovery" I am looking for?
LazerOrca said:
In my search for CVM for my mesmerize... I came across this sticky thread in reference to all SCH-I500 models..
http://forum.xda-developers.com/showthread.php?t=1026893
Where is this said "recovery that allows you to flash a zip file"? Is this the same recovery that I can access when I hold the power and volume buttons to boot the phone? The wording sounds as if I need a "previous recovery" from another source somewhere to do this.
Also, in that same thread there is a link to the CVM needed for these phones. I see CVM3-voodoo, CVM3-voodoo blue, and CVM-voodoo purple... is the first in the list the "red recovery" I am looking for?
Click to expand...
Click to collapse
There's a lot of different versions of CWM (W not V btw, stands for ClockWork Mod). I believe the colored ones are the same just different colors. The first one named should work fine though. And you will flash the zips in CWM when you reboot using the "3 finger method" which I believe is what you were describing.
akellar said:
There's a lot of different versions of CWM (W not V btw, stands for ClockWork Mod). I believe the colored ones are the same just different colors. The first one named should work fine though. And you will flash the zips in CWM when you reboot using the "3 finger method" which I believe is what you were describing.
Click to expand...
Click to collapse
Using the three-finger method with the factory recovery and scroll to where it says "apply sdcard:update.zip", find the zip file in the sdcard and hit ok?
LazerOrca said:
Using the three-finger method with the factory recovery and scroll to where it says "apply sdcard:update.zip", find the zip file in the sdcard and hit ok?
Click to expand...
Click to collapse
No that's an old method. Use the CWM.tar file and flash it in PDA in Odin. 3-finger method will then take you to CWM and not stock recovery.
it worked!!!
sweet it worked!!! thanks akellar...
how do you like MIUI? I see that you are running that on your phone. I gotta look through some of these roms and look at the features and screenshots.
LazerOrca said:
sweet it worked!!! thanks akellar...
how do you like MIUI? I see that you are running that on your phone. I gotta look through some of these roms and look at the features and screenshots.
Click to expand...
Click to collapse
No problem.
MIUI is awesome (I'm actually using CM7 btw, just haven't updated my sig). It is VERY different from stock though. Keep in mind there are bugs in both it and CM7 so if that's an issue for you then stick with TouchWiz based Roms (H57 would be my suggestion or PnP if you just want stripped down stock). You can find instructions and info on those Roms in their specific threads.
When trying to back up in CWM, I get an "Error while backing up boot image!" I am using CwM Voodoo Lagfix Recovery v3.0.2.8x.ti
Is there a newer version and is this a known issue?
LazerOrca said:
When trying to back up in CWM, I get an "Error while backing up boot image!" I am using CwM Voodoo Lagfix Recovery v3.0.2.8x.ti
Is there a newer version and is this a known issue?
Click to expand...
Click to collapse
Honestly there are so many different versions of nearly identical CWM's the version number and names no longer mean anything to me.
Download this link, unzip, pick one of the colors (all the same just different colors), install in the CWM you currently have, go to reboot recovery, it will then reboot into the update recovery and you should be good to do a backup from there.
http://www.megaupload.com/?d=R7V0INE0
put it on my SD card, then select "install zip from sdcard" or "apply update from sdcard"?
LazerOrca said:
put it on my SD card, then select "install zip from sdcard" or "apply update from sdcard"?
Click to expand...
Click to collapse
Install - update will look for an update.zip and install that, which won't do you any good.
akellar said:
Install - update will look for an update.zip and install that, which won't do you any good.
Click to expand...
Click to collapse
this what it is saying now
Finding update package...
Opening update package...
Installing update...
Installation aborted.
I reboot and it is still the same version of CWM I'm running now. Should I repair permissions?
Does it matter that the lagfix conversion says yes? I know this changes the file system from what I have read?
LazerOrca said:
this what it is saying now
Finding update package...
Opening update package...
Installing update...
Installation aborted.
I reboot and it is still the same version of CWM I'm running now. Should I repair permissions?
Does it matter that the lagfix conversion says yes? I know this changes the file system from what I have read?
Click to expand...
Click to collapse
First off, did you unzip the file I linked and pull out one of the individual files? It sounds like your trying to install the original zip which won't work. THere are 3 zip files inside the original zip.
Did you already install a Rom or Kernel? Where are you seeing lagfix coversion saying "yes?" It should only say enabled or disabled in CWM.
I saw that in the CwM recovery screen.
It is working now. I am backing up as we speak. this backup can be recovered at anytime if I can make it back to the CwM recovery screen, correct? should I download the factory rom and kernel and keep it around on my SD card?
and btw... thank you sooooo much for helping me out.
LazerOrca said:
I saw that in the CwM recovery screen.
It is working now. I am backing up as we speak. this backup can be recovered at anytime if I can make it back to the CwM recovery screen, correct? should I download the factory rom and kernel and keep it around on my SD card?
and btw... thank you sooooo much for helping me out.
Click to expand...
Click to collapse
As long as your on the same file format (i.e. not on CM7, MIUI) you will be able to restore that file, yes. The stock rom/kernel are not flashable in CWM, you have to use ODIN so having them on the SD card would not do you any good.
Not a problem. We were all new once. Like I said before, just make sure to do your own homework before jumping in head first. Many of us spend days/weeks reading before we ever did anything.
cm7
And do you have any tips for flashing cryanogen 7...
looked at this thread http://forum.xda-developers.com/show....php?t=1142872 saying I need to flash two files separately... do I flash cm7 then gapps? both from CWM?
90 some odd MB seems fairly small for something running your entire phone. is this just an update?
In the process of flashing, does this change the file format, or does this occur when it reboots and installs?
LazerOrca said:
And do you have any tips for flashing cryanogen 7...
looked at this thread http://forum.xda-developers.com/show....php?t=1142872 saying I need to flash two files separately... do I flash cm7 then gapps? both from CWM?
90 some odd MB seems fairly small for something running your entire phone. is this just an update?
Click to expand...
Click to collapse
Your link is broke so I am not sure what you are referring to but the CM7 thread has the instructions in it. Gapps installs the Google apps (gmail, market, etc).
correction... here is the link http://forum.xda-developers.com/showthread.php?t=1142872
and in the process of flashing this rom, is the file format converted then or when the installation occurs after reboot?
LazerOrca said:
correction... here is the link http://forum.xda-developers.com/showthread.php?t=1142872
and in the process of flashing this rom, is the file format converted then or when the installation occurs after reboot?
Click to expand...
Click to collapse
Converts, then reboots to recovery, then flashes rom. Should do this all on its own. FYI, this is in the OP of that link. Make sure to read everything carefully!
I have ported this recovery from Motorola Defy.
Big thanks to Epsylon3 and TWRP team.
WARNING: Use it at your own risk !!!
It has been tested on my MIUI v4 (ICS) ROM.
BUGs:
- restoring system from nandroid doesn't work
- not working with GB ROMS
Download
Only recovery.
Recovery and ICS bootmenu.
You can use Only recovery package if you don't have ICS ROM installed.
This recovery only replaces recovery in bootmenu.
Anyone tested the bootmenu version with CM9?
It should be working, because I have used bootmenu in MIUI v4 from CM9.
You can also flash only recovery package. It won't delete your bootmenu, it will only replace recovery. Only recovery package won't work, if you don't have bootmenu already.
With bootmenu package replace the whole bootmenu also with recovery.
doubt: why change to this recovery?
Look into Defy thread about it or on the official site: www.teamw.in/project/twrp2
---UFO--- said:
Look into Defy thread about it or on the official site: www.teamw.in/project/twrp2
Click to expand...
Click to collapse
yeah, now I can see the reason...
but I think you should explain how to install it. Can we install via CWM (?), before or later install the ICS ROM (?), can we install it with a GB ROM (?), etc
I installed the recovery only version as i already have bootmenu and i dont have ics. It says it is conpleted and i just need to reboot recovery but i dont see the option from my recovery menu so i just rebooted the phone. I reentered recovery but i still have the same recovery. Choosing latest, stable or stock does not show me the twrp recovery. I then tried to install again but the same thing happens no twrp. Did i miss something?
lucasdeeiroz said:
yeah, now I can see the reason...
but I think you should explain how to install it. Can we install via CWM (?), before or later install the ICS ROM (?), can we install it with a GB ROM (?), etc
Click to expand...
Click to collapse
Yeah, will both the recovery and bootmenu work with GB ROMS? I'd like it on will5's MIUI 2.5.25 GB 2.3.7. Thanks in advance!
evilmtv said:
Yeah, will both the recovery and bootmenu work with GB ROMS? I'd like it on will5's MIUI 2.5.25 GB 2.3.7. Thanks in advance!
Click to expand...
Click to collapse
I have only tried it with ICS. When I will have some spare time, I will try it with GB roms.
I agree that some more detailed description and "how-to" guide would be useful.
To be honest, I'm not sure what exactly is better on TWRP recovery and why would I prefer it over CWM (what's its functions?), what can it do? How it looks (some screens would be nice)?
How to install it?
I appreciate all your work, so don't take it as (rude) criticism, but as an idea for an improvement of this topic
I bet, it would be way more interesting and more people would use it, if there will be informations, I mentioned above.
Anonymous_ said:
I agree that some more detailed description and "how-to" guide would be useful.
To be honest, I'm not sure what exactly is better on TWRP recovery and why would I prefer it over CWM (what's its functions?), what can it do? How it looks (some screens would be nice)?
How to install it?
I appreciate all your work, so don't take it as (rude) criticism, but as an idea for an improvement of this topic
I bet, it would be way more interesting and more people would use it, if there will be informations, I mentioned above.
Click to expand...
Click to collapse
Since it doesn't have specified the requirements I pushed the files with right permissions over bootmenu 0.8.6(yes old, but i didn't know about requirements), so adding missing files, patching one script I got it running, touch UI, everything nice, but but but, I fixed the backup, backed up system, then tried to restore and oh surprise, rm -rf /system and then nothing happened. The result? the recovery deleted the whole system folder. so, my progress is on a .tar nandroid that i can't restore(the usual way)...So be CAREFUL.
Sorry about that, I have tested it only with MIUIv4 (ICS) with lastest bootmenu from CM9.
I have never try to restore system from nandroid, I'm always using update.zip for restoring system.
Thanks for your feedback.
Hello,
Does anyone experienced problems to mount sdcard ?
Kind reagrds,
So i did something stupid right after rooting my Relay. I deleted basic stock files that are necessary for the phone to function properly. I was able to copy them from my current phone (rooted T-Mobile G2/Desire Z) onto an SD card and in turn push them back onto my Relay. My problem is that I still get error messages constantly after boot up and the simplest tasks can take hours (not to mention I can't use phone, contacts, messaging). I have seen all over the web (and XDA) about unrooting the phone and retuning it to stock. I was thinking that I could unroot, then reroot my Relay and that will solve my problem.
I was all set to unroot when I encountered yet another issue. Samsung-updates.com and sammobile both direct you to download the firmware files from hotfile. Hotfile has been shut down due to copyright infringement. Where I can find the stock firmware files now that hotfile has been shut down?
Please help me as I anxiously await using my new phone without the extra bloatware!
Thank you,
RockinRita
RockinRita said:
I was all set to unroot when I encountered yet another issue. Samsung-updates.com and sammobile both direct you to download the firmware files from hotfile. Hotfile has been shut down due to copyright infringement. Where I can find the stock firmware files now that hotfile has been shut down?
Click to expand...
Click to collapse
Would Samsung's Kies software be able to restore it to stock, or is it too far gone for Kies to work?
Bobby Tables said:
Would Samsung's Kies software be able to restore it to stock, or is it too far gone for Kies to work?
Click to expand...
Click to collapse
Without the stock files wouldn't Kies be pointless?
The easiest way I've found to completely revert to stock, is to get a CWM flashable version of the unmodified stock rom (From the straight system image, not an update.zip reformated image) and a CWM flashable version of the stock recovery. Flash those in. If you want to reset your flash counter, make certain to also flash a su binary of some form (I personally prefer SuperSU, since it's so easy to clear out, run triangle away, then uninstall your su app properly.
http://forum.xda-developers.com/showpost.php?p=48581775&postcount=6
I've just put up recovery and system flashables of Stock JB.
Pushing on a Relay
RockinRita said:
So i did something stupid right after rooting my Relay. I deleted basic stock files that are necessary for the phone to function properly. I was able to copy them from my current phone (rooted T-Mobile G2/Desire Z) onto an SD card and in turn push them back onto my Relay.
Click to expand...
Click to collapse
I did a very similar thing to my Relay and I can only get it boot off of the SD card. I am curious how you performed the push. I assumed that you
used adb push, but how?
Thanks,
Lou
scopedial said:
I did a very similar thing to my Relay and I can only get it boot off of the SD card. I am curious how you performed the push. I assumed that you used adb push, but how?
Thanks,
Lou
Click to expand...
Click to collapse
I copied the files from my rooted HTC Desire Z/ T-Mobile G2 to a spare SD card I have and then I inserted that card into my Relay and started it up. It took me a few hours to get passed all the error messages that constantly pop up. And then I went into my files, external SD and moved the files over to the system folder on the Relay. After several reboots, the error messages still are coming up which I why I need to unroot it and reroot it.
Magamo said:
The easiest way I've found to completely revert to stock, is to get a CWM flashable version of the unmodified stock rom (From the straight system image, not an update.zip reformated image) and a CWM flashable version of the stock recovery. Flash those in. If you want to reset your flash counter, make certain to also flash a su binary of some form (I personally prefer SuperSU, since it's so easy to clear out, run triangle away, then uninstall your su app properly.
http://forum.xda-developers.com/showpost.php?p=48581775&postcount=6
I've just put up recovery and system flashables of Stock JB.
Click to expand...
Click to collapse
You may have just saved me, Magamo! Thank you for saving them to Drive! Once I get on my old slow Dell laptop (i'm on my Chromebook now- which unfortunately doesn't support most things) I'll try to flash your files and update you here since I cannot comment on your post as I have not posted enough myself.
Stock ROM Restore Method I Used
Magamo said:
The easiest way I've found to completely revert to stock, is to get a CWM flashable version of the unmodified stock rom (From the straight system image, not an update.zip reformated image) and a CWM flashable version of the stock recovery. Flash those in. If you want to reset your flash counter, make certain to also flash a su binary of some form (I personally prefer SuperSU, since it's so easy to clear out, run triangle away, then uninstall your su app properly.
http://forum.xda-developers.com/showpost.php?p=48581775&postcount=6
I've just put up recovery and system flashables of Stock JB.
Click to expand...
Click to collapse
You could also use Odin to flash a md5 sum of T699UVBMC5_HOME using the download mode of the Relay. Place in PDA, and tick off the Auto Reboot and F. Reset Time and hit start. Make sure you have the drivers required to do this. I think they're included with Kies. In my case, I used CWM to format /system, then I used download mode. However, I had to reset my device. AND CWM (plus root access) was erased after the stock restore. I didn't miss an important detail, did I?
furboom1240 said:
You could also use Odin to flash a md5 sum of T699UVBMC5_HOME using the download mode of the Relay. Place in PDA, and tick off the Auto Reboot and F. Reset Time and hit start. Make sure you have the drivers required to do this. I think they're included with Kies. In my case, I used CWM to format /system, then I used download mode. However, I had to reset my device. AND CWM (plus root access) was erased after the stock restore. I didn't miss an important detail, did I?
Click to expand...
Click to collapse
I'll be honest, you've got me on this one. I've never used ODIN, and am not well versed in its use. But yes, this is sounds like a more technical way of doing it without the CWM flashables I've mentioned. -- Impossible in some situations. For example, my fiancee's phone's USB port has died for all purposes other than charging, So if I'm to send it in for a warranty repair, I'll have to use the method I posted.
Confused here
Magamo said:
The easiest way I've found to completely revert to stock, is to get a CWM flashable version of the unmodified stock rom (From the straight system image, not an update.zip reformated image) and a CWM flashable version of the stock recovery. Flash those in. If you want to reset your flash counter, make certain to also flash a su binary of some form (I personally prefer SuperSU, since it's so easy to clear out, run triangle away, then uninstall your su app properly.
http://forum.xda-developers.com/showpost.php?p=48581775&postcount=6
I've just put up recovery and system flashables of Stock JB.
Click to expand...
Click to collapse
Magamo,
I'm sorry, but I'm still totally confused here. Not sure how to flash the files in. I downloaded Kies and both of the zip files from your post. Successfully updated the firmware and my error messages are gone, but I don't have CWM on it. I extracted your files, but now what? I'm not very technologically inclined so this is all Greek to me.
furboom1240 said:
You could also use Odin to flash a md5 sum of T699UVBMC5_HOME using the download mode of the Relay. Place in PDA, and tick off the Auto Reboot and F. Reset Time and hit start. Make sure you have the drivers required to do this. I think they're included with Kies. In my case, I used CWM to format /system, then I used download mode. However, I had to reset my device. AND CWM (plus root access) was erased after the stock restore. I didn't miss an important detail, did I?
Click to expand...
Click to collapse
furboom,
What is T699UVBMC5_HOME? How do I get the md5 sum of it? How do I use CWM to format /system? How do I get to stock restore? Again, I'm sorry for asking so many questions, i just have no clue what I'm doing here.
Thanks,
Rockin Rita
RockinRita said:
Magamo,
I'm sorry, but I'm still totally confused here. Not sure how to flash the files in. I downloaded Kies and both of the zip files from your post. Successfully updated the firmware and my error messages are gone, but I don't have CWM on it. I extracted your files, but now what? I'm not very technologically inclined so this is all Greek to me.
furboom,
What is T699UVBMC5_HOME? How do I get the md5 sum of it? How do I use CWM to format /system? How do I get to stock restore? Again, I'm sorry for asking so many questions, i just have no clue what I'm doing here.
Thanks,
Rockin Rita
Click to expand...
Click to collapse
If you don't have CWM, or some other custom recovery running on this, how did you get root in the first place? The easiest way to get root is to use heimdall or ODIN to flash CWM or another custom recovery, then flash Superuser or SuperSU using your new custom recovery.
The .zip files I linked are only meant to be flashed through recovery. Not Kies, not ODIN, not any other method.
Got it!!
With the help of this site (http://www.celldekho.com/how-to-unroot-samsung-galaxy-s-relay-4g/) and the file it linked to on rapidshare, along with your tip Magamo, I was able to unroot my Relay successfully. I'll reroot it later when I have the time and make sure not to delete important files LOL Thanks so much for the help!
I have a Galaxy Tab 2 7.0 gt3113. It is rooted,and I want to install a rom. The factory rom/kernel lags...get stuck ....and with all I have read the roms out there make a big difference. But I'm having a problem....I'm using rom manager and rom toolbox and I cant seem to install a rom. It load the rom whether from the computer or the download option but when it boot into recovery I get an error saying that the sd card is not found and I just end up manually re-booting the device....Ive tried this a few times choosing different things at the screen...a(abd....cashe....external storage....) it all ends up the same.....anyone have any idea what this means? I'm learning as I go....and was thinking about un-rooting my device then rooting it again.....maybe I did something wrong?
Complety bewildered....
Speedy8311 said:
I have a Galaxy Tab 2 7.0 gt3113. It is rooted,and I want to install a rom. The factory rom/kernel lags...get stuck ....and with all I have read the roms out there make a big difference. But I'm having a problem....I'm using rom manager and rom toolbox and I cant seem to install a rom. It load the rom whether from the computer or the download option but when it boot into recovery I get an error saying that the sd card is not found and I just end up manually re-booting the device....Ive tried this a few times choosing different things at the screen...a(abd....cashe....external storage....) it all ends up the same.....anyone have any idea what this means? I'm learning as I go....and was thinking about un-rooting my device then rooting it again.....maybe I did something wrong?
Complety bewildered....
Click to expand...
Click to collapse
if you are able to boot into recovery then please wipe cache partition and do a factory reset and then try to revert to stock rom
Speedy8311 said:
But I'm having a problem....I'm using rom manager and rom toolbox
Click to expand...
Click to collapse
For starters, stay away from ROM Manager! It's known to cause different sorts of problems on different devices while installing CWM and ROMs. I have only good things to say about ROM Toolbox in terms of tweaks and utilities, but never used it for ROM installation, and would suggest not to. Just download the ROM you want from its original source, put it on internal or external storage, and flash using your recovery (my personal all-time favourite is PhilZ Touch CWM, not sure what you are using). Do the proper wipes before flashing (full wipe is always recommended, especially between stock and CM/AOSP ROMs. Make sure you also flash other possibly applicable components (depends on the ROM and your preferences) -- gapps, kernel, etc. See if it works that way. I just don't see any reason to use 3rd-party apps for "ROM management" -- the simpler the process, the better.
I'm going to try to put a new rom on the tab tonight without using a program,i have a question though...I have to press power and the up volume or power and the down volume when i flash the new rom
Speedy8311 said:
I'm going to try to put a new rom on the tab tonight without using a program,i have a question though...I have to press power and the up volume or power and the down volume when i flash the new rom
Click to expand...
Click to collapse
Power+Volume up
This is the screen I get....what do I press? I know its a silly question but this IS where I was at and getting the could not find sd card error
Speedy8311 said:
i have a question though...I have to press power and the up volume or power and the down volume when i flash the new rom
Click to expand...
Click to collapse
Speedy8311 said:
This is the screen I get....what do I press? I know its a silly question but this IS where I was at and getting the could not find sd card error
Click to expand...
Click to collapse
You are in recovery... To get to download mode on P31xx for using Odin you need to press and hold Volume DOWN + Power.
ok.....so I need to be in the download mode to download anything including roms and kernels....so I have to use odin to download stuff then?
Speedy8311 said:
ok.....so I need to be in the download mode to download anything including roms and kernels....so I have to use odin to download stuff then?
Click to expand...
Click to collapse
I think you need to do some research.
http://forum.xda-developers.com/showthread.php?t=1900055
Speedy8311 said:
ok.....so I need to be in the download mode to download anything including roms and kernels....so I have to use odin to download stuff then?
Click to expand...
Click to collapse
Man, that sounds scary! You really need to do some reading on the basics, before you screw something up.
You can flash ZIP files from recovery, including ROMs, kernels, recoveries, and apps. However, you need Odin, a PC connection, and a download mode on your tab in order to flash things like official ROM packages (typically in tar.md5 format).
If you want to flash the ROM in zip format, you can do that in recovery. In general, if you have problems doing that, your other option is Odin and a stock ROM; then you can start over.
Looking closely at your photo, you have a stock recovery. You can only flash signed zips from it, which means you won't be able to flash custom ROMs or kernels. I would suggest to start with flashing a custom recovery (look up PhilZ Touch CWM, it's the best). This will make things easier for you.
P.S.: Sorry, didn't mean to sound harsh... It seems things got a bit confusing in the process, so questions and answers didn't really line up...
well ....I have been doin a lot of research,maybe too much lol....but the only thing I can get outta all of it is that to flash a kernel or rom or both I need to go into recovery(power and up volume) and do a wipe of the cashe and install.....then it seems to trail off there with a ok now your done go enjoy....
I cant seem to find any kinda description of what happens in between the wiping of the cashe/devlick and the install...I keep ending up in the recovey section wheather I use rom manager rom toolbox or just me following directions. I will say this though.....I do not see the cwm logo in the recovery....I stiil have the android and he lays there dead then does a quick flash to an error message then I get the menu....but there is no "mount and storage" and "backup and restore" option for me to choose from I put the tab into recovery mode and took a picture....its in the previous post.
I am still using the stock rom and kernel btw....Im not sure if I have mentioned that. I havnt been able to flash anything.
Speedy8311 said:
I am still using the stock rom and kernel btw....Im not sure if I have mentioned that. I havnt been able to flash anything.
Click to expand...
Click to collapse
Yeah, I got that. Sorry for the confusion! I updated my previous post, take a look. Stock recovery seems to be your problem here.
No harm done lol I appreciate all the help.....I'm a bit new at this,but I learn quick. Ok....I may be putting CWM or pfilze wrong way on my tab I loaded it from the play store,along but when I rooted tab I'm 99% positive that I installed CWM also . when I plug it into the computer I can see a clockwork folder.do I neeed to use odin to install philz?
is there a specific PhilZ Touch for the tab 2? or can I just download it to the computer and send it to my tab via odin?
Speedy8311 said:
when I rooted tab I'm 99% positive that I installed CWM also . when I plug it into the computer I can see a clockwork folder.do I neeed to use odin to install philz?
Click to expand...
Click to collapse
Not sure exactly what and how you did previously, but the fact is that you've got a stock recovery now. You need a custom recovery - it doesn't have to be PhilZ, even though I strongly recommend it. You can install standard CWM, too, no problem with that. To install PhilZ, you either need CWM to be already installed, or you need to use Odin.
For details and install instructions on PhilZ CWM, look here:
http://forum.xda-developers.com/showthread.php?t=2202667
Oh, BTW, as an alternative to Odin, look up the Mobile Odin by Chainfire on Play Store. It allows you to flash Odin packages from your device directly. Very useful tool! Free version will do, but the paid one has more features.
Speedy8311 said:
is there a specific PhilZ Touch for the tab 2? or can I just download it to the computer and send it to my tab via odin?
Click to expand...
Click to collapse
Yes, there is. Look in the thread I linked above.
Yep.....i got it stuck in forever boot using mobile odin.... Uugggh....I'm gonna return everything to stock and re-root it.....what ever I did the first time rooting and installing cwm I must a missed a step or something. I'll repost my progress when I'm back to stock and rooted properly
MERRY CHRISTMAS EVERYONE!!!!
YAY!!! Merry Christmas to me!!! I unrooted and repaired my tab 2 7.0 . I also re-rooted it and installed philztouch and everything is installed properly this time. Funny thing though.....after I got the tab working and before I re-rooted it...I tried to do the factory update to 4.2.2 ,since now I'm only on 4.1.1,it said that I had the latest updates available and my apps and phone list didn't auto load like when I first got my tab....hhhmmmm...anyways it works now and all root stuff and twrp is properly :highfive::highfive: only one more question...now that TWRP is working....when I want to download a kernel or rom do I leave it in Zipped form when I put it on the tab and the tab unzips it and flashs it or do I unzip it? .....sorry for all the basic questions but ya cant learn unless you ask questions
Thanks for every ones help with my Tab 2!!!
Speedy8311 said:
YAY!!! Merry Christmas to me!!! I unrooted and repaired my tab 2 7.0 .
Click to expand...
Click to collapse
Well, congrats, and merry Christmas! A bit confused - are you using PhilZ CWM, or TWRP?
As for zip files, leave them as they are, don't unzip - the recovery will install them. Just a suggestion - whenever possible, especially for large files like complete ROMs, verify the MD5 checksum to make sure your file is not corrupt during download.
just went into recovery and it says Philz touch 6
I have a Shield Tablet (post battery fire exchange) and I would like to update it to the newest firmware/os... It is currently rooted, running BitO-Kernel, and stock nvidia rom. I did all the rooting and flashing on this tablet originally, but I never kept it up to date with newer updates. I heard on this forum awhile back that it's not just as simple as flashing a new rom, something about having to flash some other system stuff first or some partition or something. Basically I'm looking for a guide on how to update a Shield Tablet from rooted 5.1.1 to the newest OS version avalible. I tried sreaching the forum, but I couldn't find what I was looking for (maybe I'm not using the right search keyworks).
Agreed, that it is typically best to keep devices updated with the whole OTA update, which include firmware, modems, and whatever other partitions (not always flashed with custom ROMs). Although I'm not sure if there is much changed in those partitions between 5.1.s and 5.2.
That is the original Shield tablet (not the K1) right?
If so, I think you can just download the full OTA zip, and flash in TWRP: https://forum.xda-developers.com/showpost.php?p=72501806&postcount=35
Then root (flash Magisk or SuperSU) right away before rebooting, if you want to keep TWRP. If you don't root, the update will cause TWRP to be replaced with stock recovery.
Another option, if you made a backup of the stock ROM before installing custom ROM (I suggest always doing that) you can restore it, and should get the OTA notification. Then you should be able to just download and update that way. Again, root before rebooting, if you want to retain TWRP.
If all the above fail, you can download the recovery OS, and flash all the components using fastboot, as described in the supplied instructions:
https://developer.nvidia.com/gameworksdownload#?search=SHIELD%20Tablet%20wifi&tx=$additional,shield
redpoint73 said:
Agreed, that it is typically best to keep devices updated with the whole OTA update, which include firmware, modems, and whatever other partitions (not always flashed with custom ROMs). Although I'm not sure if there is much changed in those partitions between 5.1.s and 5.2.
That is the original Shield tablet (not the K1) right?
If so, I think you can just download the full OTA zip, and flash in TWRP: https://forum.xda-developers.com/showpost.php?p=72501806&postcount=35
Then root (flash Magisk or SuperSU) right away before rebooting, if you want to keep TWRP. If you don't root, the update will cause TWRP to be replaced with stock recovery.
Another option, if you made a backup of the stock ROM before installing custom ROM (I suggest always doing that) you can restore it, and should get the OTA notification. Then you should be able to just download and update that way. Again, root before rebooting, if you want to retain TWRP.
If all the above fail, you can download the recovery OS, and flash all the components using fastboot, as described in the supplied instructions:
https://developer.nvidia.com/gameworksdownload#?search=SHIELD Tablet wifi&tx=$additional,shield
Click to expand...
Click to collapse
Thanks I appreciate the help! Yes it's an original tablet (not the k1). It's currently rooted with the Bit-O kernel running over the stock Nvidia 5.1.1 os (also has twrp on it as well). I'd like to keep root. I'll have to do some more search to see if I can find the old thread where I was told it's more difficult the a simple flash, I remember it was explained fairly clearly, I just can remember exactly what that was lol.
EDIT: found the original post where I was asking about this from last year, the issue revolves around the Staging Blob which I've never worked with before and know nothing about it (usually just ROMs and kernel flashes and occasionally radio images).
https://forum.xda-developers.com/shield-tablet/help/how-update-rooted-shield-tablet-to-t3355436
bluegizmo83 said:
It's currently rooted with the Bit-O kernel running over the stock Nvidia 5.1.1 os (also has twrp on it as well). I'd like to keep root.
Click to expand...
Click to collapse
You won't be able to update the OS and keep root. Which is pretty typical when updating most Android devices (root will be lost). But for the 1st and 2nd options I gave (flashing the OTA zips in TWRP), it's easy to just root the device again. Just have your preferred root zip (Magisk or SuperSU) on the phone when you update. Then after the update (before rebooting to OS) while still in TWRP, just flash the root zip. Then you will be rooted, and TWRP will not be wiped (replaced by stock recovery).
3rd option (flash Recoveyr OS in fastboot), getting root again is a few more steps, but still not that hard. After flashing all the components, reboot and verify everything is working. Then go to fastboot again, flash TWRP. Then boot into TWRP, and flash the root file (Magisk or SuperSU).
For any of the options 1-3, if you want to then flash your custom kernel again after rooting, you are free to do so. I'd probably verify the stock OS is working. Then boot to TWRP, make a backup of the stock kernel & ROM, then flash your desired kernel.
bluegizmo83 said:
I'll have to do some more search to see if I can find the old thread where I was told it's more difficult the a simple flash, I remember it was explained fairly clearly, I just can remember exactly what that was lol.
EDIT: found the original post where I was asking about this from last year, the issue revolves around the Staging Blob which I've never worked with before and know nothing about it (usually just ROMs and kernel flashes and occasionally radio images).
Click to expand...
Click to collapse
On the 3rd option (flash Recovery OS in fastboot), if you go to the link then click the desired version 5.2, it will expand, and you will see Downloads for the Windows or Linux files, and instructions below that. Click on "instructions" and you will see there are steps to extraxt various components, than flash each one individually using fastboot:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
If you do the other methods (flash OTA zip with TWRP) I believe all these components are included, and just flash automatically.
redpoint73 said:
You won't be able to update the OS and keep root. Which is pretty typical when updating most Android devices (root will be lost). But for the 1st and 2nd options I gave (flashing the OTA zips in TWRP), it's easy to just root the device again. Just have your preferred root zip (Magisk or SuperSU) on the phone when you update. Then after the update (before rebooting to OS) while still in TWRP, just flash the root zip. Then you will be rooted, and TWRP will not be wiped (replaced by stock recovery).
3rd option (flash Recoveyr OS in fastboot), getting root again is a few more steps, but still not that hard. After flashing all the components, reboot and verify everything is working. Then go to fastboot again, flash TWRP. Then boot into TWRP, and flash the root file (Magisk or SuperSU).
For any of the options 1-3, if you want to then flash your custom kernel again after rooting, you are free to do so. I'd probably verify the stock OS is working. Then boot to TWRP, make a backup of the stock kernel & ROM, then flash your desired kernel.
On the 3rd option (flash Recovery OS in fastboot), if you go to the link then click the desired version 5.2, it will expand, and you will see Downloads for the Windows or Linux files, and instructions below that. Click on "instructions" and you will see there are steps to extraxt various components, than flash each one individually using fastboot:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
If you do the other methods (flash OTA zip with TWRP) I believe all these components are included, and just flash automatically.
Click to expand...
Click to collapse
Oh ok thanks! I'll definitely try to flash that 5.2 OTA zip from twrp and see if that works. After that, I should be able to flash any current update (like 6.0) also, correct? And I assume I need to flash 5.2 first before flashing 6.0 (or whatever the most current shield tablet OTA is), correct?
bluegizmo83 said:
Oh ok thanks! I'll definitely try to flash that 5.2 OTA zip from twrp and see if that works.
Click to expand...
Click to collapse
Pretty sure it's how I updated to 5.2 (then rooted), and probably the easiest of the options. It's been a busy last couple months, so it's all a little blurry!
bluegizmo83 said:
After that, I should be able to flash any current update (like 6.0) also, correct?
Click to expand...
Click to collapse
Correct.
bluegizmo83 said:
And I assume I need to flash 5.2 first before flashing 6.0 (or whatever the most current shield tablet OTA is), correct?
Click to expand...
Click to collapse
Not 100% sure. It's a full OTA zip, not an incremental update. So in those cases (full OTA) it may not need the preceding update installed. But again, I'm not sure.
redpoint73 said:
Pretty sure it's how I updated to 5.2 (then rooted), and probably the easiest of the options. It's been a busy last couple months, so it's all a little blurry!.
Click to expand...
Click to collapse
Ok thanks again, I appreciate all the help! One last question I promise lol. Do I need to wipe anything in twrp before I flash an OTA zip? In the past I've been told wipes are not required for incremental updates (like 5.0 to 5.1 to 5.2) but they are usually recommended for larger os revisions like 5.0 to 6.0, does that still hold true?
bluegizmo83 said:
One last question I promise lol. Do I need to wipe anything in twrp before I flash an OTA zip? In the past I've been told wipes are not required for incremental updates (like 5.0 to 5.1 to 5.2) but they are usually recommended for larger os revisions like 5.0 to 6.0, does that still hold true?
Click to expand...
Click to collapse
I would say that is still true. Don't think you need to wipe anything (except cache and Dalvik - which I usually wipe when flashing anything), and I don't think I did either. Make a TWRP backup, in case anything goes wrong, as well as any other backups of apps, data, etc. (such as Titanium)..
Ask all the questions you like. It's fun to help, although I may not necessarily always know the answer!
redpoint73 said:
I would say that is still true. Don't think you need to wipe anything (except cache and Dalvik - which I usually wipe when flashing anything), and I don't think I did either. Make a TWRP backup, in case anything goes wrong, as well as any other backups of apps, data, etc. (such as Titanium)..
Ask all the questions you like. It's fun to help, although I may not necessarily always know the answer!
Click to expand...
Click to collapse
Ok thanks. I did just think of one more question, its not 100% related to flashing though... On my shield tablet, I have a 128gb SDcard in it, and I use Folder Mount to move all my large apps and games to the SDcard. Do these backup through TWRP if I check every box (I don't think it does cause there isn't a check box to backup the sdcard)? Would titanium backup work better to backup and restore these large apps & games that were moved with Folder Mount?
bluegizmo83 said:
Ok thanks. I did just think of one more question, its not 100% related to flashing though... On my shield tablet, I have a 128gb SDcard in it, and I use Folder Mount to move all my large apps and games to the SDcard. Do these backup through TWRP if I check every box (I don't think it does cause there isn't a check box to backup the sdcard)? Would titanium backup work better to backup and restore these large apps & games that were moved with Folder Mount?
Click to expand...
Click to collapse
You can't backup internal storage or SD card in TWRP.
I don't personally use anything like Folder Mount. I would think as long as the folders are where they are supposed to be, and the data for Folder Mount is preserved/migrated properly, then it will all still work as it did before the update. If you are really paranoid, you can make a copy of the folders on your SD card to your computer as a "backup".
redpoint73 said:
You can't backup internal storage or SD card in TWRP.
I don't personally use anything like Folder Mount. I would think as long as the folders are where they are supposed to be, and the data for Folder Mount is preserved/migrated properly, then it will all still work as it did before the update. If you are really paranoid, you can make a copy of the folders on your SD card to your computer as a "backup".
Click to expand...
Click to collapse
I just noticed on that download link you posted earlier, that Nvidia lists the newest update as 5.2.0, but that is actually Android os version 7.0. Earlier when I said on was on 5.1.1 I meant Android os 5.1.1 (as in Lollipop), not shield os version 5.1 (which is Nougat). Sorry if that wasn't clear in the beginning. Does that effect any of your original advise? Just thought I should double-check that.
bluegizmo83 said:
I just noticed on that download link you posted earlier, that Nvidia lists the newest update as 5.2.0, but that is actually Android os version 7.0. Earlier when I said on was on 5.1.1 I meant Android os 5.1.1 (as in Lollipop), not shield os version 5.1 (which is Nougat). Sorry if that wasn't clear in the beginning. Does that effect any of your original advise? Just thought I should double-check that.
Click to expand...
Click to collapse
I'm not sure if it matters with the OTA. My feeling is, that it won't matter, and it will still install.
My guess is that in the worst case, the OTA fails, and you have to resort to flashing the recovery OS version.