Develop Bugs

Going to AOSP from TW 4.3

Hello friends,
I'm a happy touchwiz user running DN3 v3 with mj5 bootloader (knox free). All is well.
But i want to try new AOSP 4.4 builds like PARANOIDANDROID, PAC, omni etc. Is it possible to do that like from latest knox free bootloader and tw4.3 TO aosp?
Has anybody tried this? please suggest what procedure should i follow.
thanks

mani16985 said:
Hello friends,
I'm a happy touchwiz user running DN3 v3 with mj5 bootloader (knox free). All is well.
But i want to try new AOSP 4.4 builds like PARANOIDANDROID, PAC, omni etc. Is it possible to do that like from latest knox free bootloader and tw4.3 TO aosp?
Has anybody tried this? please suggest what procedure should i follow.
thanks
Click to expand...
Click to collapse
Hey,
You will love AOSP! I have tried CM11 and OMNI, and both were smooth and stable. You will have a much faster phone but you will use all the Samsung apps, including the S-Pen tricks. Your S-pen will still work though.
My advice? Well:
1. Make a Nandroid Backup (using your custom recovery). You might wanna get back to your current ROM if anything goes south or you just don't like AOSP.
2. Update your custom recovery. Actually I would suggest you do this even if you don't flash any AOSP 4.4 ROMs. I recommend TWRP 2.6.3.x.
3. Make a full wipe before installing anything. Full wipe means everything but your SD cards (internal and external). Though, I would recommend to also wipe your internal SD card, after you back up your stuff (watch out not to lose your nandroid backups that might be on your internal SD).
4. Flash the ROM you choose and be very careful to read the flashing instructions. You'll feel like an a$$hole if you ask for help on the ROMs thread and find out that you missed some step because you didn't read the OP carefully.
5. Usually you'll have to flash other fixes/addons for everything to work. Look for them in the OP, if it's needed or recommended, it will be listed there.
I hope that helps! Come back if you have trouble.

flash AOSP
Just flash as usual but remember you need to read the instruction carefully for each aosp rom forum.
1. you need to use cwm 6.0.3.7 version onward or TWRP 2.6.1.0 ( can search through xda forum)
2. Do full wipe including System, Data, Cache, Dalvik, Android Secure, and Preload.
3. Flash the aosp rom you prefer
4. Flash the gapps
5. reboots (It might take some time for first time)

Ok thanks guys, I'll try it today.
Sent from my BE(a)ST.. Samsung Galaxy Note2

cant using other custom room on my note4 sprint

I have note 4 sprint from my cousin and already using custom rom xnote kitkat 4.4.4 and its great working but i just want to try other custom rom i can flash all that litle rom like cynogen its work find but when i try other rom like hybrid or other big file rom (i mean 1 gb over rom ) i cant flash it on twrp its just boot loop or just not on like i flash hybrid custom room i flash it and just bot loop or not turn on so i had an idea to download an standart room kitkat and try flash it on odin but it didnt work too its fail i just want to upgrade this phone to lolipop but consider iam in asia region now and i cant flash all lolipop custom rom and still cant use the 4g conection so my question is any there custom room just work like the xnote but its lollipop ??

emalqu86 said:
I have note 4 sprint from my cousin and already using custom rom xnote kitkat 4.4.4 and its great working but i just want to try other custom rom i can flash all that litle rom like cynogen its work find but when i try other rom like hybrid or other big file rom (i mean 1 gb over rom ) i cant flash it on twrp its just boot loop or just not on like i flash hybrid custom room i flash it and just bot loop or not turn on so i had an idea to download an standart room kitkat and try flash it on odin but it didnt work too its fail i just want to upgrade this phone to lolipop but consider iam in asia region now and i cant flash all lolipop custom rom and still cant use the 4g conection so my question is any there custom room just work like the xnote but its lollipop ??
Click to expand...
Click to collapse
Just a theory but did you flash a CM12 ROM? Do you have a TWRP nandroid (backup) of any ROM you knew worked before?
Can you see the Settings/About phone to see build, modem or firmware? That's basically asking if it boots at all.
I ask because I'm wondering if CM12 put you on the OE1 bootloader preventing you from going back to older builds? Hopefully not. Did you try restoring the original backup? What happened?
If you're stuck without a functional TWRP backup, going back to CM12 or Lollipop Noterized Stable 2 may be an option.
If data continues to be an issue, there are some fixes for certain issues in the OP of some CM ROMs. There was a TWRP backup for OE1 but I wouldn't recommend that unless you can confirm your actual build is in fact OE1.
Otherwise, the usual backup internal memory of wanted files, TWRP backups and media to sdcard and thorough wipe of system, internal, cache and dalvik-cache and a few factory resets and nandroid restore or flash a TW build OB7 or lower build should do it.
Be careful because the next move you make could be critical without a PC. The recommended wipes plus Odin OF5 would best option if you don't mind giving up KitKat or passing on custom ROMs briefly. If my theory is right, going back to OB7 or KitKat is already not an option.
Sent from my SM-N910P using Tapatalk

[Rom] Stock, Semi-debloated, Rooted, Xposed Installed. N910TUVU2DOK2.

Your warranty is now void.
I take no responsibly for your phone rolling over and dying, cursing you out, or starting WW3. You shouldn't have any problems flashing this ROM.This was made for the individuals that prefer a non touched stock ROM. If you flash this you take full responsibly. Having said that, Enjoy.
ROM BASE
Quote:
N910TUVU2DOK2 TW 5.1.1 for T-Mobile Note 4
WHAT'S NEEDED TO FLASH THIS?
SM-N910T
DOK2 BOOTLOADER
TWRP RECOVERY
(Optional) Odin 3.09 to install stock rom
INSTALLATION GUIDE
Backup your current ROM
(Optional) Wipe Data/Factory Reset
(Optional :good install stock rom N910TUVU2DOK2 to get best results
Wipe system/data/cache/dalvid cache.
Restore Downloaded Backup
Reboot
All DOWNLOADS
Stock Rom N910TUVU2DOK2
https://www.dropbox.com/s/yz5ntf8kbnzcxnn/N910TUVU2DOK2 (Lollipop 5.1.1).tar?dl=0
TWRP Backup
https://www.dropbox.com/s/vkmjt8s16bubato/N910TUVU2DOK2 TWRP.rar?dl=0
Custom Kernel
https://www.dropbox.com/s/gc16tdqae44oli3/Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910T kernel.zip?dl=0
If you want the stock, deodexed only get from here. its where i get it. Thanks to Diarrhea Slushie.
http://forum.xda-developers.com/not...k2-pure-stock-deodexed-n910tuvu2dok2-t3263361
ENJOY AND HAPPY DEVELOPING!

Great thank you one question is it stock kernel or custom kernel?

Custom Kernel
Rollablunt420 said:
Great thank you one question is it stock kernel or custom kernel?
Click to expand...
Click to collapse
Forget To say that it need a custom kernel but because its a backup, i think it will be in the rom backup, but if is not with the rom backup have edit the post so you can download the kernel from there.

İce Rom home button not working

Hi, I am install ice rom but not working home button.
How fix it this?

MM or Android N firmware?
Powered by HTC 10

2WildFirE said:
MM or Android N firmware?
Powered by HTC 10
Click to expand...
Click to collapse
N
3.1.0
Stock and elemental kernel not working

kallardo said:
N
3.1.0
Stock and elemental kernel not working
Click to expand...
Click to collapse
Please Kids, learn to read, before you flash something!!!
You must flash the rom on MM Firmware and homebutton will work.

kallardo said:
N
3.1.0
Stock and elemental kernel not working
Click to expand...
Click to collapse
You know 3.10 is just rom version and doesn't say anything about firmware? Are you sure you flashed correct firmware too?
Corrupt homebutton is usually the case when running N rom on M firmware.
@BladeOne1
Think you're misunderstanding. When first N roms came out, the custom recoveries couldn't yet work on N kernel. To workaround this problem, u could flash rom first from M environment and flash firmware afterwards.
Anyway, since the hero's behind TWRP already have a working version there's no need for this workaround anymore.
Best way now is to flash firmware (including twrp) first and then boot to recovery to flash rom. There's absolutely no reason to flash N-based roms while on Marshmellow firmware.

@Switcherd
!:
Backup your data, including internal sdcard
The ROM boots on old firmware and dirty flash of the ROM on top of Android M 3.5.0 works!
On the last screen on the installation, choose the firmware you plan to use. If you pick the wrong one your fingerprintscanner and home button won’t work!
After flashing the Android N ROM, TWRP won’t be able to decrypt your data, so you won’t be able to backup/restore etc. It is recommended to run the rom on unencrypted data, so TWRP is fully functionial.
Flashing the new firmware will break TWRP, you will only have a black screen. Therefore you would need to downgrade the firmware to have access to TWRP again.
A TWRP working on new firmware got released: twrp-3.0.2-7-pme-DEBUG.img
If you decide to flash the new firmware, do it AFTER the ROM, you should know why, since you read the above text.
Downgrading firmware should be safe on that base, it has been done by one of our devs several times. On earlier bases it caused a brick. Do it at your own risk, downgrading is always dangerous
When you downgrade, use a full firmware from Sneakyghosts thread. If you use a partial one, you will brick your device!
If the rom does not boot: Only ways that work are: Changing to Dev ED MID and CID and flash the Dev ED RUU/Firmware or following that instructions
Installation Instructions:
Dirty flashing, to keep your data from Android M
Stick with the old 1.9x firmware to have access to TWRP
Backup your Android M rom, best would be Viper10 3.5.0..other roms should work too though
Backup your internal sdcard
format data in TWRP to get rid of encryption
restore your Android M backup
DON’T reboot, else your device will get encrypted again
Flash the 4.x.x rom
Ensure you pick the correct firmware you want to use on the last screen on the setup, else your fingerprint scanner won’t work
Now you got an unenrypted Android N rom, with fully working TWRP
---------- Post added at 12:08 AM ---------- Previous post was at 12:07 AM ----------
BladeOne1 said:
@Switcherd
!:
Backup your data, including internal sdcard
The ROM boots on old firmware and dirty flash of the ROM on top of Android M 3.5.0 works!
On the last screen on the installation, choose the firmware you plan to use. If you pick the wrong one your fingerprintscanner and home button won’t work!
After flashing the Android N ROM, TWRP won’t be able to decrypt your data, so you won’t be able to backup/restore etc. It is recommended to run the rom on unencrypted data, so TWRP is fully functionial.
Flashing the new firmware will break TWRP, you will only have a black screen. Therefore you would need to downgrade the firmware to have access to TWRP again.
A TWRP working on new firmware got released: twrp-3.0.2-7-pme-DEBUG.img
If you decide to flash the new firmware, do it AFTER the ROM, you should know why, since you read the above text.
Downgrading firmware should be safe on that base, it has been done by one of our devs several times. On earlier bases it caused a brick. Do it at your own risk, downgrading is always dangerous
When you downgrade, use a full firmware from Sneakyghosts thread. If you use a partial one, you will brick your device!
If the rom does not boot: Only ways that work are: Changing to Dev ED MID and CID and flash the Dev ED RUU/Firmware or following that instructions
Installation Instructions:
Dirty flashing, to keep your data from Android M
Stick with the old 1.9x firmware to have access to TWRP
Backup your Android M rom, best would be Viper10 3.5.0..other roms should work too though
Backup your internal sdcard
format data in TWRP to get rid of encryption
restore your Android M backup
DON’T reboot, else your device will get encrypted again
Flash the 4.x.x rom
Ensure you pick the correct firmware you want to use on the last screen on the setup, else your fingerprint scanner won’t work
Now you got an unenrypted Android N rom, with fully working TWRP
Click to expand...
Click to collapse
Its from Viper Rom, but its the same

Switch to another custom rom

Hi,
I have a Pixel 3xl rooted and running with Havoc Rom.
if I want to switch from a custom rom to another custom rom, how can I do that?
Do I have to install stock rom and erase data before the new custom rom or can I just install the new custom rom above to previous one?
Thank you.

oceliome said:
Hi,
I have a Pixel 3xl rooted and running with Havoc Rom.
if I want to switch from a custom rom to another custom rom, how can I do that?
Do I have to install stock rom and erase data before the new custom rom or can I just install the new custom rom above to previous one?
Thank you.
Click to expand...
Click to collapse
Install stock factory image to both slots with -w intact in the flash-all batch, and then start with the instructions of the ROM you want to install.

sliding_billy said:
Install stock factory image to both slots with -w intact in the flash-all batch, and then start with the instructions of the ROM you want to install.
Click to expand...
Click to collapse
I would personally back up anything I wanted then flash the new rom boot.img and try to dirty flash it. If it got messed up then I would do as above. I am still crazy though and 9/10 you need a wipe when switching.

wangdaning said:
I would personally back up anything I wanted then flash the new rom boot.img and try to dirty flash it. If it got messed up then I would do as above. I am still crazy though and 9/10 you need a wipe when switching.
Click to expand...
Click to collapse
I get it. I hate clean flashing more than anything, but pretty much no custom ROMs allow for dirty installs except for over the same ROM these days. Even over the same doesn't always work well especially if the build was dirty. Not worth the extra effort trying to figure out and fix what broke on a cross-rom dirty flash, IMO.

sliding_billy said:
I get it. I hate clean flashing more than anything, but pretty much no custom ROMs allow for dirty installs except for over the same ROM these days. Even over the same doesn't always work well especially if the build was dirty. Not worth the extra effort trying to figure out and fix what broke on a cross-rom dirty flash, IMO.
Click to expand...
Click to collapse
True, but lots of people have extra time nowadays. I would say just always make sure you back up somehow before any switch. Be ready to wipe your device clean.

Thank you for your replys.
I'm not an english speaking personn, so if i understand:
The normal way to switch two customs roms is to "transit" by the stock rom and clear all data and then install rhe new custom rom.
The other way, would be dirty flash the new custom rom above the previous custom rom (with loss data possible so a bachup is needed).