On my Nexus 6, there are several ROMs derived from stock images. In fact, I am running one right now. So I was surprised to find out there don't seem to be any for the Nexus 9. There doesn't even seem to be a recovery flashable .zip of an unmodified stock ROM. Why is this? Is there simply not enough developer interest?
I think lack of developer interest is part of the problem. Even with the N6, there's not much in the way of "stock, rooted" ROMs with no other modifications. It probably stems from how easy it is to flash factory images and root, etc.
On the one hand, I'm fine flashing factory images, but I may not have my PC handy to flash (e.g. I was on vacation when a security update came out a while back). It would be nice if there were a tool like Flashify or a way in recovery to flash factory images without a PC. I, too, miss flashable stock ROMs, but I also don't feel comfortable asking a dev to take time out of their life to create one.
Sent from my Nexus 9 using Tapatalk
Related
Up until recently, I've been a fan of CWM, but now that I am playing with 4.4 custom ROMs and various kernels (particularly Apolo), I am getting some experience with TWRP as well. I like TWRP. It seems more flexible than the 4.4. compatible CWM, but I'd like to know which is really the preferable recovery to use, i.e, what the typical shortcomings or problems are with each with 4.4.
corvus.corax said:
Up until recently, I've been a fan of CWM, but now that I am playing with 4.4 custom ROMs and various kernels (particularly Apolo), I am getting some experience with TWRP as well. I like TWRP. It seems more flexible than the 4.4. compatible CWM, but I'd like to know which is really the preferable recovery to use, i.e, what the typical shortcomings or problems are with each with 4.4.
Click to expand...
Click to collapse
It comes down to which you prefer. One isn't technically 'better' than the other. However on i9100 with a combined kernel/recovery, you'll likely end up using whatever comes bundled with your kernel of choice. Bear in mind you can't 'mix' backups between the two... I.e. if you make a backup in TWRP, you need to restore it in TWRP, same goes for CWM.
Sent from a galaxy far, far away
I was using CWM with the stock rooted roms until about the end of last year, when I switched to Omnirom which uses TWRP.
I think TWRP is more easy to use it, with a better UI.
I used CWM until i upgraded to KK, now im with TWRP, other that the fact im still a bit lost on menus at times, i havent really felt much of a difference (im not much of a power user, just the usual wipe/new rom kind of person)
I'm trying really hard to do this without being dopey. I want to get my Galaxy Tab 10.1 P7510 to slim down and speed up, so I want to root and apply a new ROM. This much I'm pretty sure of. I understand that I need to replace the recovery code, which will allow me to replace the stock ROM with a modded ROM. (How am I doing?). I think I need Odin running on my PC to load the new recovery. I understand booting into recovery mode (I think). I've read about putting the new ROM on my device and rebooting into it. I believe I then need to install google apps to get some of the basic stuff (like Play store) back on the device. I assume that is because they are not part of the modded ROMs? But... how the heck does one decide WHICH recovery, WHICH ROM, WHICH gapps and the right versions of each? I'm going around and around. I'm willing to do the research, but I'm not even clear on the high-level process and steps, let alone the details, finer points. I'm a retired app developer (client server, Oracle, Powerbuilder) so I have some idea of what I'm doing. Just some. Thanks in advance if anyone cares to help.
jberthoty said:
I'm trying really hard to do this without being dopey. I want to get my Galaxy Tab 10.1 P7510 to slim down and speed up, so I want to root and apply a new ROM. This much I'm pretty sure of. I understand that I need to replace the recovery code, which will allow me to replace the stock ROM with a modded ROM. (How am I doing?). I think I need Odin running on my PC to load the new recovery. I understand booting into recovery mode (I think). I've read about putting the new ROM on my device and rebooting into it. I believe I then need to install google apps to get some of the basic stuff (like Play store) back on the device. I assume that is because they are not part of the modded ROMs? But... how the heck does one decide WHICH recovery, WHICH ROM, WHICH gapps and the right versions of each? I'm going around and around. I'm willing to do the research, but I'm not even clear on the high-level process and steps, let alone the details, finer points. I'm a retired app developer (client server, Oracle, Powerbuilder) so I have some idea of what I'm doing. Just some. Thanks in advance if anyone cares to help.
Click to expand...
Click to collapse
A custom ROM can be installed via custom recovery or Odin, so you don't really need a custom recovery before installing it, however it is higly advised.
To say it all, you don't even need root to flash a custom recovery. Some custom recovery like CM also come already rooted.
It is because they are not part of the custom ROM, since including gapps source code would take up more space and some other issues. Regarding the fact about which recovery and ROM to choose... the fact that there is a lot of them doesn't mean that they are very different. Some are based on the source code of another and just add little features that one must be looking for in order to be interested. Generally, TWRP and CWM are the ones most documented. With a simple google comparision research you should be able to decide. Custom ROMs are also based on two vastly documentet projrcts: CM and AOSP. Start with the regular ones, try them both, stock with one if you don't need anything else or start looking around among the forks.
However, I started using custom ROMs with an objective: build source code. For this scope, I decided to use CM for it's huge documentation, since I was looking for a kernel that did one particolar thing, but there wasn't one so I did it on my own. Just to say, I don't know how it feels like to be in decisive about what ROM to pick up.
Ciuffy's SM-G900F CM 12.1 spirit hath marked this way.
Hi All... help...
I have a Note3 SM-N9005 which is rooted. I have been trying to get CWM installed.
I started by using ROM Manager and this just didnt work at all - the recovery partition stayed stock.
So I downloaded the Samsung Note 3 (International) recovery image (6.0.4.6) (non-touch) from https://www.clockworkmod.com/rommanager.
I used Cygwin to convert to a .tar file and then flashed to PDA using Odin.
All looked OK and Odin passed the install - however when I tried to reboot into recovery my Note3 just gets stuck in a boot loop - the only way I could get it working again was to re-flash using Odin and when it reboots it starts and works normally - but if I reboot into recovery mode it just keeps re-booting!!
Any thoughts on how to fix this or whether the best option is to flash a whole ROM with CWM already packed? Alternatively - any ideas on where I can get a CWM file which will work on my Note3?
Also - now this has started getting messy, any advice on backing up EFS (just in case )
Thanks in advance
So you reflashed the whole stock firmware via Odin and recovery still isn't working? Very strange. Rom Manager sucks and has for years now. Why didn't you just grab either CWM or TWRP (which I find way better for most phones) from the subforum for your phone here on Xda?
es0tericcha0s said:
So you reflashed the whole stock firmware via Odin and recovery still isn't working? Very strange. Rom Manager sucks and has for years now. Why didn't you just grab either CWM or TWRP (which I find way better for most phones) from the subforum for your phone here on Xda?
Click to expand...
Click to collapse
Hi es0tericcha0s
Thanks - TBH I have only just replaced my S4 with the Note3 and just set everything up - so didnt want to reflash with a custom ROM so followed the instructions for installing CWM... and failed I did install TWRP a while ago and couldnt really get on with it - if you think it is better I might reflash the whole phone with a new ROM and give it a go.
I think I did download a CWM img file from here and when I flashed it to PDA the phone wouldnt boot at all - from memory I am sure it came up saying it couldnt boot and enetered "Odin mode"... I will have to back up my important stuff and try again tonight.
Any recommendations on a good ROM to play with? Need a stable product ideally as I dont get much time to play
Thanks
I would just restore the entire phone with the stock firmware file and start fresh. TWRP here: http://forum.xda-developers.com/showthread.php?t=2494245 As far as roms, I haven't played with the international Note 3 in awhile, but I typically recommend stock based roms for less potential issues (I personally prefer CM based roms, but I have more time and experience with dealing with possible problems than most). I would take a look at AllianceRom if you want to customize a lot on stock based http://forum.xda-developers.com/showthread.php?t=2571255 or Omega http://forum.xda-developers.com/showthread.php?t=2470441
As always, you should read through some of the stuff other active users are saying about it to make sure it fits your needs, but those development teams support a lot of Samsung devices and usually provide solid updates.
es0tericcha0s said:
I would just restore the entire phone with the stock firmware file and start fresh. TWRP here: http://forum.xda-developers.com/showthread.php?t=2494245 As far as roms, I haven't played with the international Note 3 in awhile, but I typically recommend stock based roms for less potential issues (I personally prefer CM based roms, but I have more time and experience with dealing with possible problems than most). I would take a look at AllianceRom if you want to customize a lot on stock based http://forum.xda-developers.com/showthread.php?t=2571255 or Omega http://forum.xda-developers.com/showthread.php?t=2470441
As always, you should read through some of the stuff other active users are saying about it to make sure it fits your needs, but those development teams support a lot of Samsung devices and usually provide solid updates.
Click to expand...
Click to collapse
Thanks es0tericcha0s - I downloaded the TWRP tar and flashed to PDA - all worked first time... I will give it a go and see how I get on, when I get more time I will do a clean flash too!
Good deal. Lemme know if you need anything else.
So I've been rooting all my devices for a while now. I've been able to figure out many issues, including times where I've accidentally soft bricked my device. I've always loved Nexus devices, and have rooted nearly every one I've had. I've had the 7 (2012), 5, 6, and 9, so I'm not new to this. However, the issue I'm having now is something I've never had before...
I rooted my 9 just a couple of days after getting it, and I was successful. I used the nexus root toolkit, which has always been my go to (and yes, I've made sure to configure my drivers and they all function just fine.) I was running CM12 and 12.1. After some time, I decided to try and go back to stock, due to things beginning to slow down on my tablet. I used a stock image from Google (and ensured it was the right one too) and flashed it with the nexus root toolkit. However, just before doing this, I messed up and instead of doing a normal wipe, I also did a full wipe, taking everything off. I figured reverting to stock could undo my error. After flashing stock through my PC, I became shocked to see the CM boot logo and the build being a CM one. I noticed that gapps were installed already (not sure if they were from the factory image, or from a failed wipe) and they crash any time I attempt to log in with my Google account. TWRP is still installed, so I've tried to do a clean install of CM with fresh gapps and continues to be the same issue. It's like it's constantly being dirty flashed. At this point, I'm probably just gonna revert to stock, but have no idea how. Someone please help!
Sent from my Nexus 6 using XDA Free mobile app
Download a stock image, and flash it manually with fastboot. Toolkits are cool for their ease, but honestly, if you're flashing things, you need to know how to do them manually first, so you actually know what's being done.
Sent from my Nexus 9 using Tapatalk
dictionary said:
Download a stock image, and flash it manually with fastboot. Toolkits are cool for their ease, but honestly, if you're flashing things, you need to know how to do them manually first, so you actually know what's being done.
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
So even if the tool kit uses fast boot and stuff to flash back, manual flashing will be more successful?
I won't say that that'll solve your problems for sure, but you'll know exactly where your problem is.
dictionary said:
I won't say that that'll solve your problems for sure, but you'll know exactly where your problem is.
Click to expand...
Click to collapse
I appreciate it! I'm waiting for an OTG cable to arrive in the mail because the only Windows machine I have is a tablet.. I like Linux and Hackintosh a tad too much on my daily driver, but don't feel comfortable enough using terminal to try and flash through Linux.. But I'll be sure to report my findings when possible!
So just to update, I used the nexus root toolkit and disabled any checks when reverted to stock. It worked, and it seems to have been related to the boot issue CM originally had. Planning on going to CM again soon
I love my KF HD 6 and use it daily, but after almost two years I've grown tired of the UI and was thinking about switching over to a custom ROM. That, and the fact that Amazon seems to have abandoned development for my device since it's a couple generations behind so it's not likely to get updated past its current 5.1.1 lollipop.
I did some digging, but the only official ROM I could find for my device is CM11. A bit disappointing since it's not only an incomplete port (not all features work), but it would be a downgrade to 4.X KitKat. Not really what i'm looking for. I did find a video showing how to put CM13 Marshmallow onto a KF 7. https://www.youtube.com/watch?v=W0GwGthOfh8 and I thought this may work for the 6 as well. I know they're not the same device, but I've seen it mentioned several places that the HD 6 and HD 7 that were released in 2014 are identical under the hood with the only difference being the screen size.
Anyway, I have a working TWRP recovery for my device, along with properly installed ADB and fastboot drivers. So if I use ADB to pull my partitions and copy them to my PC just in case, then make a Nandriod backup in TWRP and transfer it to my PC (again, just in case) then do a cache wipe and a system wipe, then flash CM13 along with the appropriate Gapps, then another cache wipe to avoid bootloops, then reboot I should be good right?
Either it will work, or it won't. In case it doesn't work I should be able to boot back into TWRP and restore from my Nandroid. If for some reason I can't get back into TWRP, I do have a fastboot cable that can at least get me access to fastboot mode where I can push all my partitions back manually. Either way I should be good in the event that it all goes pear shaped?
Sorry if these are basic questions, but I am still new to all this and I just want to make sure I have all my bases covered before I start anything. I feel it's better to ask for clarification and advice first, than to jump the gun and come here afterward with a bricked device asking for help trying to fix it because of my own stupidity.
For all you who are pros at this sort of thing, did I miss anything or should I be good to go? Thanks.
Necro bump - so what did you end up doing? I have a KF 6HD gathering dust and I'm getting an itch to ROM