Hi guys, my Galaxy tab 7.7 is still completely stock: Honeycomb and Touchwiz...... :crying: High time to move on!
Ultimately, I'd like to be able to try a few ROMs, using a ROM manager. When I want to install CWM from Google Play, it indicates that I need to manually install a recovery. I found found daniel_hk's tar files for the P6800 (CWM recovery)
I'm using a Linux PC, and I want to use Heimdall to flash. There is nothing on the Tab that needs to be preserved. (for the record: I've spent quite some time reading lots of threads on this, Googling stuff; and I I have experience with Linux arch & gentoo, so I am very used to doing my homework, but now I really need some help THANKS
My questions
1. Are these the correct steps I need to take? If not please correct me.
- flash CWM recovery
- reboot the Tab
- install CWM (as an app, from Google Play)
- then get Root? Using what app / method?
- flash the wanted ROM, using Heimdall, installing it using the ROM manager
2. it is enough to flash the recovery image, don't I need a cache.img as well? It's not in Daniel's .tar....
3. how will I flash? I don't really understand the heimdall GUI.... So , if i simply use the terminal, would I use
heimdall flash --no-reboot --RECOVERY recovery.img or is it better to leave the --no-reboot out ?
4. Will the recovery image (there is one for cwm 6.0.3.0 and cwm 6.0.4.3) only work with the corresponding cwm? Or will any image do?
Thank you all very much! [off topic ]Although the Linux kernel is in Android, for some reason it is hard to really understand it, maybe because words like 'firmware' or 'ROM' and 'kernel' seem to have a different meaning in Android/Phones compared to Linux/x86 PCs. That, plus you can 'brick' your PC - unless your flashing a BIOS or something : [/off topic ] Again, thanks in advance !
Never mind, i could not wait. I flashed with --no-boot, but then had to reboot manually. I will post a manual when I'm ready. So far: CWM installed, Root obtained, KitKat installed.
Related
Seems like there are more and more people coming out having trouble geting into cwm on their device - I'm one of them...but there's a thread in the general QA that I think would get more attention and feedback here.
http://forum.xda-developers.com/showthread.php?p=27585693#post27585693
No idea how to move it...but in a nutshell I and others are odining the cwm package but still only get the factory recovery when we try to boot into cwm.
Any ideas?
Take a look here.
http://rootzwiki.com/topic/24762-stopping-recovery-overwrite/
I'm familiar with Heimdall - but I thought the bootloader had to be a bin file?
If someone had or could write a quick step-by-step on that, what version Heimdall, etc...I'd give it a go. I've been in Heimdall (newest version) connected to the unit and wasn't exactly sure which options to use...I hate to guess when messing with bootloaders.
Thanks Stranxk - it was the locked bootloader.
Steps I took that worked:
1. Download and launched Heimdall 1.85
2. Downloaded the appropriate unlocked bootloader from the links in the above post
3. Using Heimdall I exported my PIT directly from my device and used that in the flash tab
4. Select "add" and "Kernel" - and flashed the unlocked bootloader
5. Re-flashed CWM using ODIN
Went right into clockworkmod - running Tab2Lite beta3 right now...
Works great - Thanks!
Hi!:laugh:
I've rooted my Samsung Galaxy S 4G, and now want to flash it with CM10
This is the guide I've been following but I've never succeeded:
w w w . android. gs /update-galaxy-s-4g-cm10-android-4-1-jelly-bean/
Every time I go into CWM and chose the zip file, it says that it can't mount my SD card.
I've wiped the cache and deleted all user data (factory reset), though it still won;t flash.
I've used programs like Android Commander, and it still won't flash.
Will someone please explain to me why I can't flash the rom?
Welcome to the forum,
You need recent CWM (the blue one) to be able to flash mtd roms.
You have two choices:
1) Flash using heimdall one-click (found in the stickies section) then CM10 using CWM. <=- (you do need to follow the instructions carefully)
2) Download Samsung Galaxy Kernel Flasher from play store, and download AntonX kernel (Search the forums), then flash CM10.
Edit:
I checked the link you provided, I would say please DO NOT flash any ROM from unknown sources. In quick glance they provide false
information. Specifically you cannot return to STOCK with CWM once you are using MTD rom (you need heimdall or Odin).
Please read before you flash anything.
PS: despite flashing using CWM is somewhat safe for this device (SGS4G), but don't take this safety for granted for other devices,
ALWAYS be careful, and learn from other people mistakes (I recently hard bricked S2 Hercules by flashing wrong kernel using CWM).
Rebel_X said:
Welcome to the forum,
You need recent CWM (the blue one) to be able to flash mtd roms.
You have two choices:
1) Flash using heimdall one-click (found in the stickies section) then CM10 using CWM. <=- (you do need to follow the instructions carefully)
2) Download Samsung Galaxy Kernel Flasher from play store, and download AntonX kernel (Search the forums), then flash CM10.
Edit:
I checked the link you provided, I would say please DO NOT flash any ROM from unknown sources. In quick glance they provide false
information. Specifically you cannot return to STOCK with CWM once you are using MTD rom (you need heimdall or Odin).
Please read before you flash anything.
PS: despite flashing using CWM is somewhat safe for this device (SGS4G), but don't take this safety for granted for other devices,
ALWAYS be careful, and learn from other people mistakes (I recently hard bricked S2 Hercules by flashing wrong kernel using CWM).
Click to expand...
Click to collapse
How would I get the new (blue one) CWM?
And what could I do about my sd card mounting in CWM?
Thanks again though for the advice, it had too many bugs!
mxoaper said:
How would I get the new (blue one) CWM?
And what could I do about my sd card mounting in CWM?
Thanks again though for the advice, it had too many bugs!
Click to expand...
Click to collapse
Read the links in my signature.
lumin30 said:
Read the links in my signature.
Click to expand...
Click to collapse
I've already upgraded my phone via kies mini to GB 2.3.6, then rooted it with this turtorial...
w w w .youtube. com /watch?v=qsJc2lM4OXo
How will I get the blue CWM though?
Please help me! I'm not a noob but definitely not a master at this
You should read more
http://forum.xda-developers.com/showthread.php?t=2376048
Make sure to check out the wiki at the bottom.
Hey Guys,
Im streamlining a deployment process for my employer. They use Tab 2's and have made a ROM that is set up perfect. I pull a system dump of the system, boot, and recovery partitions (mmcblk0p9, mmcblk0p5, & mmcblk0p6). They are names system.img, boot.img, and recovery.img. I am using CWM 10.1 for more versatile customization over the touchwiz framework.
I use Ubuntu 13.04 for tarball and md5sum, the md5 checks out with Odin. However the flashing process fails when it gets to the system.img.
boot and recovery flash, but system cant.... Any ideas here guys? There are hundreds of these being deployed, currently it takes about an hour to initialize one for use. I really want to streamline this process. Maybe you cant use odin to flash non-touchwiz distros? I could increase complexity of the deployment and use CW recovery to flash, but I want to make this as simple as possible.
Any input/thoughts will be appreciated.
-FlemDroid
flemdroid said:
Hey Guys,
Im streamlining a deployment process for my employer. They use Tab 2's and have made a ROM that is set up perfect. I pull a system dump of the system, boot, and recovery partitions (mmcblk0p9, mmcblk0p5, & mmcblk0p6). They are names system.img, boot.img, and recovery.img. I am using CWM 10.1 for more versatile customization over the touchwiz framework.
I use Ubuntu 13.04 for tarball and md5sum, the md5 checks out with Odin. However the flashing process fails when it gets to the system.img.
boot and recovery flash, but system cant.... Any ideas here guys? There are hundreds of these being deployed, currently it takes about an hour to initialize one for use. I really want to streamline this process. Maybe you cant use odin to flash non-touchwiz distros? I could increase complexity of the deployment and use CW recovery to flash, but I want to make this as simple as possible.
Any input/thoughts will be appreciated.
-FlemDroid
Click to expand...
Click to collapse
Ever figure this one out? I am essentially in the same boat as you but am sticking with stock. Also running into the same issue with you when it gets to system.img
I have no idea why it fails. Im guessing it has to do with a signature of the .tar.md5 file. Theres articles to do this yourself for other samsung devices. Im stumped but will explore ODIN again. Currently restore from backup. But from a systems administrator standpoint its not ideal.
Please let me know if you have developments. Ill update the thread if I do.
Sent from my SCH-I545 using xda app-developers app
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
I rooted using the on-board iroot app. I now have root access and SU on my N8013.
Can I now simply
- use ODIN to load the Gnabo 7 ROM.
- Flash Gnabo, remove phone stuff, and wifi fix.
- Can I use the stock kernel or must I flash a different kernel?
Will this give me the update to KitKat?
mangurian said:
I rooted using the on-board iroot app. I now have root access and SU on my N8013.
Can I now simply
- use ODIN to load the Gnabo 7 ROM.
- Flash Gnabo, remove phone stuff, and wifi fix.
- Can I use the stock kernel or must I flash a different kernel?
Will this give me the update to KitKat?
Click to expand...
Click to collapse
Try rashr inline flash tool from Google play store and flash twrp recovery image from the app this way you have a modern recovery tool and will be able to flash what ever ROM you want.
Just download all the necessary parts to your tablet, reboot into recovery and flash in the given sequence via twrp. Good luck.
tsukaza said:
Just download all the necessary parts to your tablet, reboot into recovery and flash in the given sequence via twrp. Good luck.
Click to expand...
Click to collapse
I would be grateful if you could provide just a bit more info.
- what are the necessary parts?
- where on my table should I put them?
- "given sequence" = Gnabo 7 ROM, then remove phone stuff, then wifi fix??
Sorry to seem so dull. I am just timid about doing this whole ROM bit.
Thanks,
mangurian said:
I would be grateful if you could provide just a bit more info.
- what are the necessary parts?
- where on my table should I put them?
- "given sequence" = Gnabo 7 ROM, then remove phone stuff, then wifi fix??
Sorry to seem so dull. I am just timid about doing this whole ROM bit.
Thanks,
Click to expand...
Click to collapse
Download the ROM, SuperSu, Kernel for N801X, WiFi Fix for N801X and Remove phone stuff for N801x
- Install rashr from Google play store and grant root when asked.
- from rashr install the latest twrp recovery image.
- reboot into twrp recovery to be sure it is working.
- boot back normal.
- down from gnabo v8 post and put zips in the internal/external sdcard, put them in one directory after you downloaded all 5 needed zip files. ROM, su, kernel, fix phone stuff and fix WiFi.
- boot into twrp recovery image.
- Full wipe (cache, dalvik, data, system)
- Flash the ROM, SuperSu, Kernel and Remove phone stuff for N801x ********
- Reboot and do the setup
- Reboot in recovery
- Flash WiFi Fix for N801X ******
- Reboot
well
mangurian said:
I rooted using the on-board iroot app. I now have root access and SU on my N8013.
Can I now simply
- use ODIN to load the Gnabo 7 ROM.
- Flash Gnabo, remove phone stuff, and wifi fix.
- Can I use the stock kernel or must I flash a different kernel?
Will this give me the update to KitKat?
Click to expand...
Click to collapse
posting in the correct section this is not the Q & A..
I don't even believe anybody should respond with any other answer then, please read the forum rules. before posting or beginning a thread. And direct you to the right place.