Related
I am currently on rooted 8.4.4.5 rooted with CWM and netflix fix. I want to upgrade to rooted HC 3.2 with CWM and netflix. What is the best course of action?
Do i need to flash to 8.4.4.11 via CWM first?
Then after that there is the brk method or the roach method. Which would cause me less hassle ?
Also can i use the brk method without doing the 8.4.4.11 flash?
I'm not going to do the 8.4.4.11 rooted stock ROM search for you, since that thread is seemingly buried, but I was in the same boat as you (rooted stock 8.4.4.5).
I went ahead and flashed the rooted stock 8.4.4.11 over 8.4.4.5 (going straight to 8.6.5.7 will NOT work - I tried it), then booted. Rebooted back into recovery, then flashed this: http://forum.xda-developers.com/showthread.php?t=1198066
After that, I flashed this custom ROM over stock (optional, of course): http://forum.xda-developers.com/showthread.php?t=1154939
All of that I did with simple cache wipe and dalvik wipe. No data wiping and I retained my apps all through it. Oh, and all of it with CWM, of course.
I did find the 8.4.4.11 thread with the patch .zip not the full rom though which should be just fine. http://forum.xda-developers.com/showthread.php?t=1178607
I also remembered that i have the OC Kernel v16 from Clemsyn-Blades: http://forum.xda-developers.com/showthread.php?t=1202884
Will this kernel be a problem when i upgrade to 3.2 or will it just be wiped with flash to HC 3.2?
I also have the US version and have read that the upgrade to 8.6.5.7 killed their CWM. Im curious if that has been fixed, because i only saw that it was fixed in the WW version. I could probably just use brk's script to install cwm again, if someone can verify that that works...? I forget how i even got cwm on there originally...
Finky said:
I did find the 8.4.4.11 thread with the patch .zip not the full rom though which should be just fine. http://forum.xda-developers.com/showthread.php?t=1178607
I also remembered that i have the OC Kernel v16 from Clemsyn-Blades: http://forum.xda-developers.com/showthread.php?t=1202884
Will this kernel be a problem when i upgrade to 3.2 or will it just be wiped with flash to HC 3.2?
I also have the US version and have read that the upgrade to 8.6.5.7 killed their CWM. Im curious if that has been fixed, because i only saw that it was fixed in the WW version. I could probably just use brk's script to install cwm again, if someone can verify that that works...? I forget how i even got cwm on there originally...
Click to expand...
Click to collapse
I did all the flashing using CWM and it didn't affect CWM at all. Also, don't be surprised if you find your bluetooth isn't working after all this. See here: http://forum.xda-developers.com/showthread.php?t=1192805
^ The exact same issue happened with my TF. That's when I flashed the custom ROM I linked to over stock rooted 3.2, and got BT working again. That ROM already has the Clemsyn kernel included, so I didn't worry about installing the kernel separately.
hey guys,
I'm trying to do a backup through CWM before I flash CleanROM and start tinkering with some stuff. The issue I'm having is when I try to backup it gives me an error saying "error backing up boot image!!"
I've done plenty of backups through CWM in the past and never has this issue, anyone have a solution? I have no problem wiping out/re-flashing if necessary but I want a backup before I do all that!
I have CWM version 5.5.0.4 on my TF300T running CM9 at the moment. Could this issue have been caused by when I reverted back to stock about a week ago, and broke something?
That necessitates another question then: if I copy/paste the structure of my internal memory card manually to my computer, and then do whatever I want on the tablet, can I just restore that backup and pick up where I left off? Or will it break dependencies and whatnot?
My other question is how do I get started with custom kernels? ROM's seem to be a dime a dozen but I can't find very many kernels, and I don't have the slightest clue where to start with them.
Last question is, since CWM is giving me issues can I just flash over the existing CWM install with the new CWM touch version, or will that break something/make me lose my backups/etc?
Any help is appreciated
-Opethfan89
Realization: I'm actually running CWM 5.8.3.4 and I just realized that when I installed ROM Toolbox it let me update CWM and after that update is when I started running into these issues. So the same question then remains, if I just flash the older CWM over my current install, will that wipe out everything or will it retain whats there and just overwrite my CWM install?
dump CWM altogether and use TWRS!
Sent from my ASUS Transformer Pad TF300T using Xparent Red Tapatalk 2
I might try TWRS but I want to try the CWM touch version first before I change. As it turns out, I just flashed the v5.5.0.4 over my current install and it worked fine and I'm backing up my install at the moment. Seems it might have been an error in the 5.8 version of CWM that was causing my grief. So that resolves two of my issues, my question about the kernels still remains if anyone can shed some light.
i havent tried the touch CWM. i just wish the keyboard worked in recovery, that would be awesome!
Sent from my ASUS Transformer Pad TF300T using Xparent Red Tapatalk 2
Which recovery? TWRS? or CWM?
Ok so i've finally decided im ready to unlock and flash. My question is this: whats the deal with returning to stock and redoing everything on certain roms? Can anyone explain to me the variables here?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
once you have your device rooted and have a recovery installed, make a nandroid back up your stock rom, flash whatever rom you want, then if you need to go back to stock rom, just flash the nandroid back up you made. If you want to go 100%, then you will have to find the stock recovery image, and flash that over your custom recovery as well, then just use OTA Rootkeeper... and temp unroot your phone... and viola, your 100% stock again.... but if you plan to go back to 100% stock then DO NOT UNLOCK YOUR BOOTLOADER!! there is no way to lock it again once you unlock it.
I think it's worth while to note
currently the only custom recovery that is able to flash stock is CWM
TWRP is not able to flash a stock rom
KAD79 said:
I think it's worth while to note
currently the only custom recovery that is able to flash stock is CWM
TWRP is not able to flash a stock rom
Click to expand...
Click to collapse
If you flash a stock ROM using CWM you will lose all data on your device, including any backups you made using CWM. So be sure to backup those files to your PC (they're located in the clockworkmod/backup folder of your internal storage) before flashing the stock Asus ROM.
I've been changing my ROM's throughout the day and have basically memorized the process of flashing CWM, root, and ROM's by now
KAD79 said:
I think it's worth while to note
currently the only custom recovery that is able to flash stock is CWM
TWRP is not able to flash a stock rom
Click to expand...
Click to collapse
TWRP can flash stock. I've done it.
Sent from my SGH-I897 using xda premium
Ive read about problems reflashing ROMs when youre on the CM or AOKP. Need to return to stock, then flash other ROMs, dunno why exactly. So is it enough just to restore my stock nand backup or do I need to do something differently? :good:
This is exactly what im talking about. What are the rules when coming from cyan to a stock flavor?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
So lets say right now im ready to unlock and root. I would want to unlock the device, then root, then flash CWM (not twrp) so i could still retrain (and boot in to without reinstalling) my original rom? Because i still want to titanium my apps.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
not sure if I understand your question right, but yeah you can use your stock rom when you root or flash cwm. Untill you wont wipe anything within CWM, theres no reason you coulndt use it. But dont forget to do backup of your stock mate.
I think part of the confusion is defining what "stock" means, and I've got two different views on it over the past few days:
COMPLETE STOCK means flashing ASUS' original stock firmware, which completely wipes out everything on your tablet (including your nandroid backups) and CWM and takes you back to a fully stock tablet (except it will still have unlocked bootloader). From here, if you want to install ROM's like CleanROM or Hydro you have to re-flash CWM each time, then flash the appropriate ROM.
MODIFIED STOCK would be making a nandroid backup of your stock settings as soon as you flash the stock ROM, install CWM, then back it up and you can revert to it accordingly. I don't know if this would break things when you tried to flash Clean/Hydro and so maybe someone can clarify.
I wanted to try both hydro and cleanrom so I spent many hours yesterday flashing between stock/modified stock. Its kind of a pain, but all part of the learning process.
And one thing I want to note both for myself and for anyone else: if you flash stock without removing CWM it'll give you the broken bootloader logo (android on his back w/ exclamation point), and my solution has just been to do a 'wipe data' from the fastboot menu and the stock will work fine. What I mean by this is I've done this at least three times, where I flash STOCK from within CWM and when I try to boot into recovery, I'll get that android. That's because STOCK completely erases everything including CWM so in order to restore the normal operating procedure, you just need to 'wipe data' from within the tablet.
Hope my understanding of these situations is correct, if not anyone can feel free to correct me
People like to experiment with their tablet, they get easily bored with the same thing.
So they go back to stock and flash another rom like Hydro which is stock based because when you flash CM or AOKP it won't let you just flash to Hydro.
KAD79 said:
I think it's worth while to note
currently the only custom recovery that is able to flash stock is CWM
TWRP is not able to flash a stock rom
Click to expand...
Click to collapse
NOT TRUE!
It should be noted that TWRP is now more functional than CWM. TWRP can now flash stock ROMs just fine. It can now restore complete nandroids, including /boot, and it can now flash from and store to the external SD card. It was just recently updated for this, which is why all the information until now has said to use CWM to flash the stock ROM. So, go ahead and use TWRP. It's perfect now.
Hi!
I just bought Nexus S i9023 and don't know how to start flashing roms, kernels etc. I was reading about that I must unlock bootloader first, flash cwm recovery and then i can finally flashing roms. Is it right? I have few questions about this device, here they are:
1. How are kernels flash? Is it flashing by recovery like update.zip?
2. I have Gingerbread currently, but I want to update to JB, can I first off apply the update in recovery or I have to update to ICS first? Can you provide me a link to updates?
3. http://android.clients.google.com/packages/ota/google_crespo/9ZGgDXDi.zip this is JellyBean for i9023, right?
4. What are the kernel and rom combo most stable and fast?
5. Internal memory is working like a SD card, so if I will make a nandroid backup, it will not erase my data while doing full wipe ... ?
6. I'm currently using my private MIUI GB on my Xperia X8, which was ported from SGS. Is there any multilanguage MIUI GB rom anywhere?
7. Which is the flashing order? Kernels first? Or roms?
Thanks for replies, guys!
:cyclops:
Yes, you must unlock the bootloader, which will wipe EVERYTHING on your phone before you can flash your desired recovery and root. Kernels are flashed through recovery, after a ROM is flashed, otherwise it will generally be overwritten if a new ROM is flashed. No need to go to ICS to get to jb if you are flashing a full ROM. The memory referred to as internal is not what is used as an SD card. The SD/USB memory is the external memory. A nandroid doesn't back this up.
Sent from my ns4g using Tapatalk 2
p1gp3n said:
Yes, you must unlock the bootloader, which will wipe EVERYTHING on your phone before you can flash your desired recovery and root. Kernels are flashed through recovery, after a ROM is flashed, otherwise it will generally be overwritten if a new ROM is flashed. No need to go to ICS to get to jb if you are flashing a full ROM. The memory referred to as internal is not what is used as an SD card. The SD/USB memory is the external memory. A nandroid doesn't back this up.
Sent from my ns4g using Tapatalk 2
Click to expand...
Click to collapse
I just picked up a secondhand i9020T. It's running stock jelly bean, but it looks like the previous owner had some custom ROMs installed. The bootloader is unlocked and clockwork mod recovery is installed. I don't seem to have root access. Can I just flush a full ROM, like CM10 through clockwork even though I don't have root access? Will doing that provide root in CM10, or is that going to cause a problem. Thanks.
naguziew said:
I just picked up a secondhand i9020T. It's running stock jelly bean, but it looks like the previous owner had some custom ROMs installed. The bootloader is unlocked and clockwork mod recovery is installed. I don't seem to have root access. Can I just flush a full ROM, like CM10 through clockwork even though I don't have root access? Will doing that provide root in CM10, or is that going to cause a problem. Thanks.
Click to expand...
Click to collapse
You might could get by just flashing cm10 and gapps, but I would start by flashing superuser, or super su for jb.
Sent from my ns4g using Tapatalk 2
Yo, thanks, I successfully unlocked my bootloader and flashed cwm, then installed fresh miui jb and gapps. I searching for good kernel for daily usage, with good performance, can you recommend me any?
cheers
p1gp3n said:
You might could get by just flashing cm10 and gapps, but I would start by flashing superuser, or super su for jb.
Sent from my ns4g using Tapatalk 2
Click to expand...
Click to collapse
So i'm a little confused. The stock rom as of now has the superuser app, but when I open something that tried to pull root access (titanium backup or root checker for example) the superuser app does not come up, and root access is not available. Thoughts? When I flashed ROMs on my old transform, root seemed to travel with the kernel - but I just want to make sure I can flash a rooted ROM+kernel through recovery without having root access. Sorry if these questions are a bit naive - I'm trying to work through the other guides and Q+A to try to figure this out, but I'm still not clear. Also, sorry for sort of hijacking your thread, but the topic seemed like a good fit. Thanks in advance for all help.
*Edit - Fixed root access in stock rom by flashing new SU app through CWM from link posted in second post of this thread: http://forum.xda-developers.com/showthread.php?t=1918490&highlight=have+clockworkmod+but+no+root
Last question, if I flashed JellyBean based rom, can I flash Gingerbread based by following the steps like formatting system etc. in recovery previously?
The su app from the play store is just an app. as you found, flashing the su zip is the only way to actually get the su access.
Anytime you flash a new rom, it is highly recommended that you perform a full wipe, after making a nandroid, of course. The steps I follow are factory reset/data wipe (this will also take care of cache & dalvic cache since they are on the data partition) then go to mind and storage to format /system & /boot.
If you haven't already I suggest using titanium backup & the pro key if you can. I have it set to automatically backup everything every 2 days, and I also make a new one each time I get ready to flash anything. Don't restore any system apps per data off you change roms though. The only reason I backup the system stuff is so I can restore my texts & call log with the proper time stamps.
Sent from my ns4g using Tapatalk 2
I was on locked on stock OTA JB.
I unlocked a few days ago, then last night flashed TWRP. Created a nandroid, then rooted.
Today I've spent several hours downloading ROMs, doing Titanium backups, surfing forums, backing up my personal files etc. i.e. using my tablet normally without problems.
I decided it was time to flash a ROM so booted in TWRP to create a fresh nandroid. Then when it finished I rebooted the system with the plan to copy the nandroid to my pc.
The tablet booted, but then after 30s or so rebooted. It's now stuck in this boot loop. So I tried a cold boot, and then restoring the latest nandroid and the problem persists. I'm currently trying to restore the pre root nandroid I made.
To recap - I am on stock OTA JB, with TWRP v2.3.1.0 recovery. Any thoughts?
Ok just to update - the pre root nandroid seems to be stable at the moment. So... What to do?
Should I reflash the recovery? Try a different recovery?
Any ideas why the nandroid would be borked when the system seemed stable when I created it?
Sent from my Galaxy Nexus using Tapatalk 2
Question: Does TWRP actually root the TF300? Mine is unlocked but I am looking for the easiest way to root the device.
No it doesn't, it just replaces stock recovery and allows you to gain root.
You could start your own thread. Or, you could read the thread in Android Development that gives clear instructions for noobs to gain root and install TWRP or CWM.
Sent from my Galaxy Nexus using Tapatalk 2
which ROM were you trying to flash? was it a JB rom?
bshpmark said:
Question: Does TWRP actually root the TF300? Mine is unlocked but I am looking for the easiest way to root the device.
Click to expand...
Click to collapse
After you install TWRP, you just need to flash a root zip file with TWRP to gain root..
bshpmark said:
Question: Does TWRP actually root the TF300? Mine is unlocked but I am looking for the easiest way to root the device.
Click to expand...
Click to collapse
Flash a rooted custom rom. ull gain root + rom easily
mike-y said:
which ROM were you trying to flash? was it a JB rom?
Click to expand...
Click to collapse
Since this thread got immediately hijacked i'm not sure but I'm going to assume this part of your post was aimed at me...
I wasn't trying to flash a ROM at all. I hadn't even got that far. All I'd done was flash the recovery, root it and then create a nandroid. It was creating the nandroid that seemed to trigger the boot loop, even though that makes zero sense.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
can you get back into fastboot connected to your PC?
I'd try to re-flash TWRP. Also make sure you are using the JB version, not the ICS version.
http://teamw.in/project/twrp2/97
I just unlocked and flashed TWRP on my tf300 (with the OTA JB update) this morning, and everything is working fine. I also flashed a root file without any issue.
I reflashed TWRP and re-rooted it seems to be OK.
Then I found I couldn't get any ROMs to work - they all froze at the boot screen. The solution to that problem lies in flashing the US update of JB rather that the WW. Now I'm running Hydro with Untermensch's kernel.
One thing I did notice with TWRP 2.3 is I get the error "can't mount /storage" in the log whenever I do anything. A bit of research suggests this might be an issue with TWRP 2.3, not present in 2.2. I wonder if that is what was causing the boot loop issue I had previously.
I can't seem to find a blob of 2.2 to downgrade to so I'm living with it for now and hope it's not going to cause problems down the line.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Good that TWRP always using the same names for a DL Link. So here is the 2.2 for JB Bootloader
If you are looking for ICS just edit the dl link .
http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.2.2.0-tf300tg-JB.blob