If I root my galaxy tab 10.1 then I install a new rom wiping the data first will I loose the root? Or has the custom rom got root built in?
I'm using galxytask 13.1 but my tab doesn't charge through the USB to my pc, any ideas since the description to galaxytask rom says USB charging?
1. it has root
2. it doesn't work for some reason.
1. You will still have root access
2. This is a Kernel option, Task was using pershoots Kernel for previous builds , but switched to the stock kernel cause there was a problem updating from pershoots kernel to pershoots kernel if you were 2-3 updates behind I believe , the safest way was to to be on the stock kernel then flash pershoots Kernel over the stock. So if you want that option back you will have to flash pershoots latest kernel then enable it . All that info is in Tasks thread and pershoots , try there first next time
Related
Ok, according to MobileTechVideos (who does ROM reveiws on youtube) the MIUI rom is to be installed the same way he installs CyanogenMod 7 in one of his videos (as seen here)...
In his method he states to after flashing to stock with Odin to flash the overstock kernel v1.5.2 UV, but I'm curious to know if in replacement of this could I use overstock v2.4.1 kernel instead or if after flashing MIUI using the overstock kernel v1.5.2 UV I could then flash the overstock v2.4.1 kernel over the 1.5.2 version?
Sorry if this question is confusing!
I use the revamped and or LE versions depending on which i like better for the new weekly update and flash the glitch kernel which was designed for miui and is extremely fast,and i flash the KB5 modem inwhich works best for me.
Generally i stick with the LE version wich is bloat free and add the apps i want and set the build.prop settings to my preference.
Ok i see in the stock miui.us they dont actually specify how this should be installed...so here it goes as i know it to work. You must be on froyo bootloaders!!!
Odin back to stock....for me its eclair (2.1).....then flash a 2.2 rom and make sure you have cwm....from there reset/wipe data,wipe cache,wipe dalvic...then go mounts and storage and format/ system.
Now flash miui,when its done go to advance and fix permissions,then reboot system wait 5 minutes and reboot....all done.
From this point on when installing a miui update you do not have to wipe data and reset but follow the rest of the steps and you wont loose all your apps and settings.
Pm me if you have further questions and ill be glad to walk you thru it.
Edit: i found that you can flash this from stock eclair but you have to root and get cwm,i find its just easier to flash a 2.2 custom rom that has root and cwm already on it and go from there
Im thinking about change my rom to Cyanogenmod, but Im afraid it will crash and brick my phone.
Can i just flash it directly? or should i wipe out all stuff first?
Speedmod is a kernel, Cyanogenmod is a ROM.
CyanogenMod 7 (w/ Gingerbread 2.3.7) for Galaxy SII Q&A.
No, ist very very unlikely to brick your phone just because you go from stock (or modded stock) or whatever to Cyanogen,
If something goues wrong, you can (nearly) always flash a stock Firmware via ODIN.
As far as I know its almost impossible to brick a modern Android Phone. Except you do do some really "deep" stuff.
But you should wipe your phone when you go from Stock (or modded Stock) to Cyanogen.
And you should flash the Cyanogenmod Rom twice because its using a new or modded version of clockworkmod.
There is a step by step discription in the Cyanogenmod Wiki.
I hope that Information helps a bit.
How to
normalife said:
Im thinking about change my rom to Cyanogenmod, but Im afraid it will crash and brick my phone.
Can i just flash it directly? or should i wipe out all stuff first?
Click to expand...
Click to collapse
1.just download latest nightly of cyanogemod and put it on SDcard...Link for latest nightly here: (http://download.cyanogenmod.com/get/cm_galaxys2_full-94.zip)
2.enter CWM recovery and do a wipe data/factory reset,,, wipe cache,, wipe dalvik cache(it is in Advanced option in CWM main menu)...so yes wipe out all stuff first
3. install nightly .zip file from sdcard
4. install nightly .zip file from sdcard AGAIN...REALLY DO IT OR IT WILL NOT BOOT
5. reboot phone from recovery and you will be in CyanogenMod 7 ROM
PS: do not be afraid about SpeedMod kernel....flashing cyanogenmod nightly .zip also flashes CM7 Stock kernel for you
PS: You can try Siyah kernel 2.1 beta 14 (http://www.gokhanmoral.com/public/files/siyahkernel/test/Siyah-v2.1b14-CWM.zip) info here: (http://forum.xda-developers.com/showthread.php?t=1263838)
I am using this kernel since beta 12 and no problems
PS: Speedmod is name of kernel = core of android system...Cyanogenmod is a ROM = phone firmware
You can ask me again if needed..or send me a PM
Should he not at least make a nandroid backup first
Dude, do some research.
If you managed to get Speedmod onto the phone, then you shouldn't have any other problems.
Kinda new to i9100, most of my experience is with HTC.
First rooted using CFroot (KG2) 4.1
Current rom: CM9 kang
Current kernel: Siyah 3.3.2
What I did to cause it:
- I compiled Siyah kernel from source with some minor modifications.
- After I flashed it, the i9100m stuck on boot screen, probably something I messed up in kernel build.
What I tried to do to fix:
- Used Odin and flashed CF-root KG2 4.1 odin > doesn't boot rom, but can use recovery
- Flash Siyah 3.3.2 CWM in CFroot recovery > doesn't get root back
- Used Odin and flashed Siyah 3.3.2 odin > doesn't get root back
- run extweaks > misc > Install root, remove root, auto-install root > all don't get root back
I'm stuck here, what can I do to restore root?
-----------------
Edit: Solved, just downloaded SuperOneClick:
http://shortfuse.org/?page_id=2
Clicked on Root, it said Root was already detected. Overrode it and it works now.
I'm planning to use Custom ROM for my JB using Custom Kernels from my Rooted ICS, and I have questions and doubts. Here's the steps and the Q's they have:
So, here's the steps I planned based on my S2 Guide Surfing:
1. Root my ICS (Done)
2. Flash Stock JB Official Firmware via Odin XWMS1? XWMS2? or XWLSW?
Questions Regarding This Step:
A. Do I have to backup my /efs folder from ICS here?
B. Do I have to Wipe Data/Factory Reset + Wipe Cache BEFORE/AFTER flashing the JB Firmware?
3. Flash Siyah? or DorimanX? Kernel via Odin
Questions Regarding This Step:
A. Can I run these kernels on my Stock JB ROM (if succeededly flashed)?
B. If I do a backup on Siyah via its CWM, and changed to DorimanX, then noticed that the kernel's not my type, can I restore my backup from Siyah's to DorimanX's CWM? Or does the both kernel have the same CWM?
4. Flashing Custom ROM via Custom CWM
Questions Regarding This Step:
A. If I flashed a Custom ROM which has a Cusrom Kernel inside (like NeatROM, I suppose), will it be overwritten my Siyah/DorimanX kernel? Or they will still be there?
Thanks for Noticing My Questions! And Very Thanks for Answering Them!
1) Yes, I'd backup up EFS immediately after you root your phone (and even before you do a nandroid backup with CWM). Use Hellcat's kTool from Google Play (and buy Hellcat a beer after you download it).
2) No. No need to wipe when flashing stock firmware (you can if you want though if you like a really clean install) because you're going to be wiping before you do a custom rom install anyway.
3) Yes. You should be able to run Siyah or Dorimanx just fine on stock JB (make sure you choose the right build though; read the threads devoted to these kernels to work out which build you need).
4) Yes, if you do a nandroid backup with CWM while running Siyah, and you switch to Dorimanx & decide you don't like it, you can restore your backup & go back to Siyah.
Though you could just easily re-flash Siyah with CWM to achieve the same result. That will probably be quicker than restoring a backup (say, 2 minutes Vs 10 minutes). If you re-flash a kernel, just the kernel changes, none of your settings/apps/anything else does, so restoring a nandroid just to go back to a particular kernel is overkill.
5) Yes. If you flash a custom rom, the kernel bundled with that rom will overwrite/replace your current kernel. If you don't like the kernel bundled with the rom, you should be able to use any other kernel you want with it provided the kernel you want to use works with the base of the rom (I.E the kernel you want to use works with TW roms if you're running a TW rom, or AOSP if you're running an AOSP rom) & the Android version of the rom you're running. Again, read the thread devoted to the kernel to determine compatibility before you flash it (worse thing that can happen if it isn't compatible is the phone will bootloop though; unlikely to brick your phone outright).
Would the following work as a way to try out, for example Cyanogenmod 10. I am currently running a 4.1.2 install (pretty much stock just rooted/cwm via Philz as per the tutorial). I have a complete backup made via Philz recovery of this rom along with the kernel (which I believe is still stock from that) and efs.
1) Install a custom kernel (eg. dorimanx 9.x?) via the Philz recovery.
2) Install cm-10.2-20140102-NIGHTLY-i9100.zip.
3) To return to the original rom, reflash the original kernel (with whatever CWM is included in dorimanx) - then reflash the backed up rom via the same recovery?
I hope this is clear enough a question.
I believe you have to flash a stock rom through Odin, to return to complete stock. Just flashing a stock kernel isn't enough, and is surely not going to work (so don't do it).There are also tutorials how to remove the yellow triangle afterwards.
Please correct me if I'm wrong
Donnie Sins said:
I believe you have to flash a stock rom through Odin, to return to complete stock. Just flashing a stock kernel isn't enough, and is surely not going to work (so don't do it).There are also tutorials how to remove the yellow triangle afterwards.
Please correct me if I'm wrong
Click to expand...
Click to collapse
This is the part I'm most unsure of. Ideally I'm trying to figure out the process that lets me go from CM10.2 (and whatever recovery) to the point I am running the backed up rom rooted with PhilZ-cwm6-XWLSW-XEU-5.06.1-signed.zip again. Very confused on how to do so.
TopherBrink said:
This is the part I'm most unsure of. Ideally I'm trying to figure out the process that lets me go from CM10.2 (and whatever recovery) to the point I am running the backed up rom rooted with PhilZ-cwm6-XWLSW-XEU-5.06.1-signed.zip again. Very confused on how to do so.
Click to expand...
Click to collapse
Topher,
If you have rooted and cwm via philz, you already have a modified kernel installed. I believe the philz-cwm6 should be as close to stock kernel with the CWM incorporated. You don't need to add another kernel, because it will be replaced when you install the custom ROM. You should just be able to flash the cm10.2 via philz or via odin. You can then flash the dormanix kernel if you want - can't comment on that kernel - or if it has cwm included.
I would also suggest that you consider backing up you /efs folder (one with you imei information etc) prior to flashing any custom roms. People have been using hcKtool to do the backups and also an actual copy as well.
Depending on the custom rom, you may have connection problems with your network. So you may want to consider keeping a copy of your modem.bin file from your stock rom handy in case you need to flash onto the custom rom.
If you want to go back to stock, then you just need to flash the stock rom - you can check sammobile website for your stock rom or use the backup that you made.
I should point out that I have yet to do any of the above - I gathered this from reading the forums. Some more experienced forum users can add corrections. I rooted my phone a couple of months ago and now considering installing custom rom in the next couple of months.
Thanks.
if u flash a custom rom (cm10.2 for example), it already included kernel as well. so if u want to try out other custom kernel, i can flash it after you are done flashing a custom rom but make sure it is compatible with your android version. (u cant use custom kernel that not support android 4.3 with a custom rom running android 4.3)