OTA questions - Galaxy Note 4 Q&A, Help & Troubleshooting

Hi, Ive recently rooted my phone and was just wondering what I need to do to get OTA for marshmallow in the future and I have a few questions about stock rom.
1. Do I lose root when flashing stock rom?
2. Do my apps and data get deleted when I flash stock rom?
3. Do I lose TWRP and revert to stock recovery when I flash stock rom?
Noob here, so thanks in advance

Marshmallow OTA, you are very optimistic mate, might take 3 months if not more.
Anyway, to answer your queries, yes, flashing stock ROM via Odin removes everything, I mean it removes root, it removes any custom recovery and restores stock recovery. But no it won't wipe your internal memory, but here again there are some firmwares where the devices does get wiped out, but I don't know exactly which one are those! But most firmwares don't touch your internal memory. But if you are coming from a custom ROM then it is highly recommended (mandatory actually) to completely wipe the phone using a custom recovery and then only flash stock ROM.
About thanks, hit the metre, saying thanks doesn't mean anything here in XDA

Related

Camera failed warning on 4.4.2

Hi I hope you can help me with this,
I was on a custom 4.3 rom running on old bootloader. I then
updated to 4.4.2 rom but my camera is not working only a black screen and giving
me a warning message " Camera failed" and once that happens
the whole system lags. I've read around that it could be a hardware
problem but when I switched back to the 4.3 rom the camera is working
smoothly again. I have tried 3 different 4.4.2 custom roms but same issue persists.
My question is could this have anything to do with my bootloader? I am planning
on flashing a stock 4.4.2 firmware with the new bootloader to see if that helps but what
worries me is if this doesn't help then I have no way anymore to go back to
a 4.3 firmware where my camera still works. Can you help me point to a solution
to this problem? Or which stock firmware I should flash to test if my camera
will work on that firmware.
Did you fully wipe before flashing?
Lennyz1988 said:
Did you fully wipe before flashing?
Click to expand...
Click to collapse
Yes full wiped in Aroma, Formatted Int/ext card from Philz recovery, restored factory
from rom didn't help either.
What custom rom did you flash? Do you use the correct modem for the old bootloader?
Lennyz1988 said:
What custom rom did you flash? Do you use the correct modem for the old bootloader?
Click to expand...
Click to collapse
I have tried Phoenix ROM, GoldenEYE , ECHO ROM, I am not sure if
I am using the right modem though I just flashed the file suggested on this page.
I'm on the Phoenix rom and it's running stable for me. I am also running on the old bootloader.
I had troubles at first after upgrading to 4.4.2, but after I wiped /system in recovery, everything worked.
You could try it. Make sure to backup /efs to your external sd or pc. Backup your entire internal sdcard, because it will be wiped. I didn't know that, so I lost everything on my sd
Perform a full wipe. Then wipe /system from the recovery (i used clockwork recovery). After that just flash and don't install any tweaks in aroma.

[Q] Method to Out of Bootloop

In according @_alexndr information about immposibility come back to XXUEND3 stock rom if you have XXUFN modem i have a question.
If i have a bootloop I have option to flash stock rom but i don't want beacuse i will loose opportunity to root again with towelroot.
So i can go to stock recovery and wipe data and cache and do factory reset, my question is: will this always help with every bootloops?
Is sometimes happen bootloop that help only flash stock rom?
Gramzz said:
In according @_alexndr information about immposibility come back to XXUEND3 stock rom if you have XXUFN modem i have a question.
If i have a bootloop I have option to flash stock rom but i don't want beacuse i will loose opportunity to root again with towelroot.
So i can go to stock recovery and wipe data and cache and do factory reset, my question is: will this always help with every bootloops?
Is sometimes happen bootloop that help only flash stock rom?
Click to expand...
Click to collapse
not all the times AFAIK.
tried before when testing to downgrade from ND3 to NC2, bootloop, factory reset. go through boot... but all freeze and FC
hehehe.
if you have updated the bootloader, there's no way to go back to any older firmware than your bootloader.
But I didn't upgrade bootloader, only modem and now I don't have come back to old base...

Any way to install stock KK or stock LP via a flash-able file through any recovery?

Hello guys.
This is my first thread on XDA and I am really excited about it.
My query is, can we flash any stock OS via a recovery.
For example I am a N900 user, installed stock KK via Odin, rooted and then installed CWM recovery. Then I installed Nandroid and created a full backup of my ROM(Stock KK with superuser and nothing else)
When I am using any other ROM like Pekaka 6 or Dr. Ketan's L23(with LP bootloader) and when I try to restore my backup via recovery or CWM it's not letting me to restore my backup.
And when I am using any KK based ROM like K14 or alba19986's Ultralite ROM then it's allowing me to restore my backup.
Vishal333 said:
Hello guys.
This is my first thread on XDA and I am really excited about it.
My query is, can we flash any stock OS via a recovery.
For example I am a N900 user, installed stock KK via Odin, rooted and then installed CWM recovery. Then I installed Nandroid and created a full backup of my ROM(Stock KK with superuser and nothing else)
When I am using any other ROM like Pekaka 6 or Dr. Ketan's L23(with LP bootloader) and when I try to restore my backup via recovery or CWM it's not letting me to restore my backup.
And when I am using any KK based ROM like K14 or alba19986's Ultralite ROM then it's allowing me to restore my backup.
Click to expand...
Click to collapse
You replied to your question yourself.
Different bootloaders allow different Android versions. For KK ROM you need KK bootloader, for LP ROM you need LP bootloader. And different modems, as well.
And more importantly, KK and LP need different sizes of the system partition, and to change the size of the system partition, you need a .pit file for that. If you want to play with .pit files, be prepared to read A LOT, because flashing a wrong .pit file (through Odin) may very well brick your device, and naturally, this is not a desired outcome.
And for switching between major Android versions, you need to read even more.
I'm about to pass out, so just read some threads here in the general Note 3 forum, they aren't hard to find.
Thank you so much, obelec for clearing my doubt in a beautiful way.
By the way what if I am on LP based ROMs and I am preforming full wipe, rebooting in download mode, installing KK bootloader and rebooting again in CWM then trying to restore the backup?
Thanks in advance.

[Q] N910G won't boot after TWRP restore?

Hi All,
Just wondering what's going on with my phone - it's a Galaxy Note 4 SM-N910G with Optus Australia.
Here's the situation:
I rooted my phone using Chainfire method from 5.1.1 Optus firmware.
Then, I installed TWRP, backed up all partitions (INCLUDING EFS).
After that, installed Cyanogenmod. Holy damn, I need to go back to stock...
so...
I booted back into TWRP
I reset phone as usually would to restore/install ROM.
I restored firmware backup in TWRP.
Reboot to system
-- BOOTLOOP --
happens every time i try to restore, and the only way I can use my phone right now is to reflash Cyanogenmod 12.1 nightlies onto it - which have problems (such as I cannot reboot with CM12.1 because if I do after installing it, the phone app breaks and I cannot get past anything because of toast message "com.android.phone" has stopped..., so then only way to get it to work again is to reflash CM12.1 again - this happens about twice daily...)
-- -- PLEASE HELP!
What happens to TWRP backups that mean i cannot restore my stock backup without it bootlooping? and why can devs not post a clean stock flashable ZIP copy of stock firmwares? Its great having all these mods, but how about something that doesn't require umpteen thousand bloody applications to reflash your phone with? Whatever happened to a simple ZIP? when I see ZIPs, devs see thanks buttons being pushed!
-- THANKS
MrDhark32 said:
Hi All,
Just wondering what's going on with my phone - it's a Galaxy Note 4 SM-N910G with Optus Australia.
Here's the situation:
I rooted my phone using Chainfire method from 5.1.1 Optus firmware.
Then, I installed TWRP, backed up all partitions (INCLUDING EFS).
After that, installed Cyanogenmod. Holy damn, I need to go back to stock...
so...
I booted back into TWRP
I reset phone as usually would to restore/install ROM.
I restored firmware backup in TWRP.
Reboot to system
-- BOOTLOOP --
happens every time i try to restore, and the only way I can use my phone right now is to reflash Cyanogenmod 12.1 nightlies onto it - which have problems (such as I cannot reboot with CM12.1 because if I do after installing it, the phone app breaks and I cannot get past anything because of toast message "com.android.phone" has stopped..., so then only way to get it to work again is to reflash CM12.1 again - this happens about twice daily...)
-- -- PLEASE HELP!
What happens to TWRP backups that mean i cannot restore my stock backup without it bootlooping? and why can devs not post a clean stock flashable ZIP copy of stock firmwares? Its great having all these mods, but how about something that doesn't require umpteen thousand bloody applications to reflash your phone with? Whatever happened to a simple ZIP? when I see ZIPs, devs see thanks buttons being pushed!
-- THANKS
Click to expand...
Click to collapse
This http://forum.xda-developers.com/note-4/help/n910c-to-stock-rom-cm13-t3321132 :good:
One possible solution is to flash the appropriate stock rom via odin. After booting, install twrp and root your phone. After this you can restore your previously saved stock rom via twrp.
MrDhark32 said:
Hi All,
Just wondering what's going on with my phone - it's a Galaxy Note 4 SM-N910G with Optus Australia.
Here's the situation:
I rooted my phone using Chainfire method from 5.1.1 Optus firmware.
Then, I installed TWRP, backed up all partitions (INCLUDING EFS).
After that, installed Cyanogenmod. Holy damn, I need to go back to stock...
so...
I booted back into TWRP
I reset phone as usually would to restore/install ROM.
I restored firmware backup in TWRP.
Reboot to system
-- BOOTLOOP --
happens every time i try to restore, and the only way I can use my phone right now is to reflash Cyanogenmod 12.1 nightlies onto it - which have problems (such as I cannot reboot with CM12.1 because if I do after installing it, the phone app breaks and I cannot get past anything because of toast message "com.android.phone" has stopped..., so then only way to get it to work again is to reflash CM12.1 again - this happens about twice daily...)
-- -- PLEASE HELP!
What happens to TWRP backups that mean i cannot restore my stock backup without it bootlooping? and why can devs not post a clean stock flashable ZIP copy of stock firmwares? Its great having all these mods, but how about something that doesn't require umpteen thousand bloody applications to reflash your phone with? Whatever happened to a simple ZIP? when I see ZIPs, devs see thanks buttons being pushed!
-- THANKS
Click to expand...
Click to collapse
Sorry no help from me but I have a similar problem. At some point mine quit booting to TWRP and I got a huge OTA update a few days ago and every time I try to boot into recovery it ends up in Stock Recovery only after going to little android saying installing updates(it fails & eventually goes to stock recovery.) I did a reset and still have 5.1.1 installed and still have the same behavior.
I have the professional version of the unified toolkit and it says if it is still booting into stock recovery select options 7, 3 which I did but it didn't fix the problem. I think what's getting me is it thinks there are still system updates to install.

Questions about bootloader and downgrading on s4, help

Okay, please bear with me as i am new to this flashing custom ROM's game.
I got a intl Galaxy s4 (gti9505) a month back. After reading a lot, i flashed TWRP, and installed a custom ROM (Lineage Optimized 14.1) It runs absurdly great, and i dont think i'll need to replace this OS. BUT if i need to downgrade for whatever reason (im sure i will soft-brick the phone soon, because im testing a lot.) I have some questions:
- Some posts says i can flash back to 5.0 and upper, because the bootloader is the same (???)
- Some posts says i cant flash back to anything below my actual OS (android 7.1) (?????)
- Some posts says i cant flash STOCK ROMS because the bootloader is different. (???????)
- Could i HARD BRICK the phone, wrongly installing stuff via TWRP? or is TWRP functional "forever?''
- I did a big ass backup of android 5.0 before, when i installed TWRP. Can i reflash back to this, at any time?
I'd like to avoid any kind of brick, so help is very much appreciated. Thank you very much for helping a fellow android fan :good:
You can always flash the latest stock ROM to the phone using Odin. There is no stock ROM beyond 5.01 as far as I know.
Yes, you can hard brick the phone by flashing files through TWRP.
How did you create the 5.0 backup?
Thank you. +1 :good:
I did the backup via twrp, i think it was nandroid or something.
One last little question. What happens if i flash, say a custom ROM that is android 6.0 on TWRP right now (Doing the correct stuff and wiping what is needed). Will it Softbrick?
if yes, could you tell me why?
neru21 said:
Thank you. +1 :good:
I did the backup via twrp, i think it was nandroid or something.
One last little question. What happens if i flash, say a custom ROM that is android 6.0 on TWRP right now (Doing the correct stuff and wiping what is needed). Will it Softbrick?
if yes, could you tell me why?
Click to expand...
Click to collapse
It should not softbrick if you are flashing a custom ROM that is designed for your phone's model #.
If it does softbrick, there are two major causes: a full wipe of the data and cache partitions is required before installing the ROM or a full wipe of the phone (system, data, cache) using recovery is required before installing the custom ROM.

Categories

Resources