Hello guys.. I would be grateful if any of you could help me with your thoughts regarding this matter...
For security reasons I prefer flashing stock recovery and locking down the boot loader after I settle on a custom rom/kernel combo. Been doing this for a while and I dont mind building my phone up from the scratch when I change ROM.
With CM 10.1 stable coming up.. I think I'll finally switch to 4.2 in a few weeks time. I read on the forums that the file system change in 4.2 doesn't play nice with 4.1 recoveries and ends up creating duplicate folders all over the place. Now... I'll surely use latest CWM or TWRP to flash CM 10.1 but later... when I flash the stock recovery (v3e, i think the latest for our device) just to lock down my device- is there any possibility that my system would get messed up? As the latest stock recovery for Nexus S was released with 4.1.2 it isn't supposed to be compatible with 4.2.2 roms technically.
..enlighten me please! with my little knowledge, i'm unable to work it out in my head
Related
Has anyone else had problems trying to install roms like cyanogenmod after the Jellybean update? I used to be able to install CM9 nightlys then eventually stable releases and back to stock with no problems, so i am not a noob to flashing roms. Now after I updated to stock 4.1 I cant install CM10 or any other custom roms. I have tried installing through CWM and TWRP but cant get past the ASUS screen after flashing the usual way. I heard there was a change in partition sizes when the update applied. Is there a way to install custom roms again or am i doing it wrong now?
http://forum.xda-developers.com/showthread.php?t=1883465
Hi All,
I have read the stickies, trolled through dozens of threads and posts, but I can't seem to get a definitive answer to my problem / question.
Current status:
TWRP 2.2.2.0 installed
Unlocked Bootloader
Custom JB Kernel [JB Unsecured I think??] installed
JB Odexed Custom ROM Installed
Hboot 1.14.0002 on device
My question is this:
I want to go back to stock JB or as close to it as possible. The current JB ROM is supposed to be stock, but is a little buggy, in that the stock dialler does not have smart dial, and some other small annoyances [all credit to the dev though, fantastic job!!]
Anyone willing to help me out?
Oh, and for some reason my adb / fastboot drivers are acting up [device not detected, although was working fine a couple of days ago before I started flashing roms!], so I'll need to fix these first somehow!
Tanks
D
What custom ROM are you on? You sure its a custom, and not the stock rooted odexed JB ROM?
If you are really on a custom, just flash a stock rooted JB ROM from Development. I don't see a benefit in installing an official OTA or RUU.
Howdy folks, it appears that I've run into a bit of a hurdle playing with my transformer.
-----------------------------------------
Problem:
Stuck Boot (static "ASUS" logo, with nvidia logo in bottom right and "unlocked" in top left)
-(rebooting into bootloader and recovery is possible)
-----------------------------------------
Background Steps:
1. device got the 4.2.2 OTA from ASUS and is running the 10.6 bootloader
2.performed 4.2 unlock as per ASUS instructions
3.loaded TWRP 2.5 (4.2 version)
4.did a full wipe within TWRP (except SD)
5.installed stable release 10.0.0 =
6. wiped cache and dalvik
7. rebooted
------------------------------------------
I figured this was a problem with the kernel (similar symptoms before on previous devices) so i went into fastboot and loaded the boot.blob from the cm zip. - It had no effect!
I then wiped and tried again with 10.1 (nightly), again updating kernel - It had no effect!
Getting nervous, i flashed a rom based on stock 4.2 (kernel flash was required) -It's working but not what I want to end up with.
-Can you folks help me out?
Any help is appreciated
As far as I know the this [OFFICIAL][4.2.2][TF300T][NIGHTLIES] CyanogenMod 10.1 for TF300T does not work with the 4.2 bootloaders, even though it's 4.2.2 it needs a 4.1 bootloader like 10.4.2.20.
There is an experimental build for the 4.2 bootloaders here [ROM][4.2.2][CyanogenMod 10.1 Unofficial][TF300T(G) with BL 4.2][2013-05-09], if your using twrp 2.5.0.0-4.2 you should have JB 10.6.1.15.3 bootloader as twrp 2.5.0.0-4.2 on JB 10.6.1.8 has a split-screen issue.
As far as I know, the official CM10 and CM10.1 (including nightlies) are still not compatible with the ASUS new 4.2 Boot loader. You have to wait a little while for the official CM10.1 maintainer to catch up.
However, there is an unofficial CM10.1 that can work with your current 4.2 bootloader, look here: http://forum.xda-developers.com/showthread.php?t=2252990
would you recommend downgrading to 4.1 to use the stable release, or should is it safer to just stay with what i got til they decide to make an official cm release that'll work with it?
n00b1c1d3 said:
would you recommend downgrading to 4.1 to use the stable release, or should is it safer to just stay with what i got til they decide to make an official cm release that'll work with it?
Click to expand...
Click to collapse
It is safer to stay. Messing with recovery, fastboot and bootloaders is risky business. Although, it may work, there is also a chance you might brick your tablet when done incorrectly. Not that I doubt your abilities. It's just that we are seeing an alarming rate of bricked TF300T being reported in the forum. Better wait for a much safer version of TWRP recovery.
EDIT: However, if you have NVFlash backup of your tablet, downgrading and bricking won't be much of a problem.
Roger, i'll stay with 4.2, maybe i'll try that experimental 4.2 one.
Hey guyz,
I have an issue with flashing cyanogen mod rom. I hav cwm recovery.Flashed zip.
But after flashing zip and rebooting system a white screen fades,I found fix also for that.
Just placing stock boot.img from backup but after doing that also i have a problem.
The mobile boots,samsung.com logo comes out,then gts7500 comes for 5-10sec and the
mobile reboots.Endless loop.i have done flashing it many times,did wipe data/cache and
dalvik cache but still no difference.
But one thing i observed that i am able to flash roms which have same android version ie.
2.3.6 but im unable to upgrade to higher version like 4.2 or 4.4
Tried flashing even slimbean and speedmod rom but same problem.I have an indian firmware.
Current OS is inspiration rom v_18 by kk9999gada..
So guyz anyone have an idea to get out of this bootloop? I badly want to use cyanogenmod
and upgrade its version
Hi, thank you for using XDA Assist. You are probably going to have to start all over and flash the stock firmware in Odin. Also, the version of cwm may have to updated to flash newer roms. But the best place to get help is in your device's specific forum here, http://forum.xda-developers.com/galaxy-ace-plus They are the experts on your device.
Thread closed.
Hello,
Since it doesn't seem that note pro P900 will get marshmallow, I am thinking of changing to a custom ROM. I have a few questions since I'm pretty new to this. I have a Note PRO 12.2 SM-P900.
1. Will I lose the S-pen function if I change to a custom ROM?
2. Which ROM is the best and it has to be stable? - as I'm using my tablet for school.
3. Is there a guide how to install a custom ROM?
First off I'm not sure what marshmallow has to do with going to a custom rom in your mind but just so you know, in order for a custom ROM that is based upon TouchWiz to exist there must be a stock ROM available for it. That is to say that if you want a marshmallow based custom ROM that has TouchWiz functionality baked into it then a stock marshmallow ROM needs to be released by Samsung. Just figured I'd make that point clear.
Secondly, technically S-Pen function isn't lost with AOSP based ROMS but the standard baked in functions are. Stuff like, the pop-up menu when you pull out the pen, action memo, smart select, image clipping etc. Those things are in TouchWiz so if they are important to you then stay away from AOSP based ROMS and look for TouchWiz based ones instead.
Third, there isn't a ton of development for the SM-P900 so options are limited as is support.
My suggestion is work on getting custom recovery with root first. If you're successful with that then consider going custom ROM after that.
The thing I said regarding marshmallow was more in the way that since Note Pro is not getting it then I have no reason to stay on the stock rom
Is it possible for you to suggest me a TouchWiz rom then? Since I use my S-pen and must be stable.
What happens if I fail getting a custom recovery with root? Will I brick the device?
Well to be honest I believe there's only one custom lollipop touchwiz based ROM for the SM-P900 right now and that's CivZ's ROM.
http://forum.xda-developers.com/gal...-civzp900lollipop-5-0-2-aroma-12-jul-t3155589
As far as where to start, like I said start with the basics which is custom recover (TWRP) and root. The reason root is needed is to retain the custom recovery, otherwise booting into stock system after installing the custom recover can often result in loss of that custom recovery. You need that custom recovery in order to install the custom ROM.
There's a guide to custom recovery and root here: http://forum.xda-developers.com/gal...guide-install-official-lollipop-p900-t3154362
Worst case when trying to do the root and custom recovery is having to restore the device using a factory image and Kies so be prepared for that.
Most common issue with doing the custom recovery and root is missing the buttom combinations or a step in the instructions which can lead to boot loops and getting stuck on the boot splash screen. As long as one can get back into download mode though a custom recovery should still be able to be installed. As long as a custom recovery can be installed a custom ROM can be installed on the device. Of course this all assumes the ROM being downloaded is confirmed to be compatible with the device to begin with . . . try to install a wifi only ROM onto an LTE tablet or vice versa . . all bets are off.