Develop Bugs

Help restoring my DEV note 4 please!!

Hey I have a problem here.I have a dev edition Note 4. I have been running EMSpoilt's first ROM ([Rom][N910VOYU1ANI1][4.4.4] Stock Root Deodex/Knox-Free Updated 11/24/2014) for about 2 weeks now. It was running great smooth as butter until now. I tried flashing his new [Rom][N910VVRU1ANJ5][4.4.4] Stock Root Odex/Knox-Free) but my phone wouldn't boot up, it wouldn't get past the first Samsung screen just keeps restarting. I made sure to follow step by step instructions. Wiped everything but my SD card. Tried it 2 more times and nothing. Tried to wipe cache and all that. Nothing helped. So I decided to restore back to my backed up ROM. Once restored it started to act weird. My finger print scanner doesn't work and I can't download anything another than apps from app store...the phone is very glitchy and almost unusable.. almost like it has a virus. It did get pretty hot when I was flashing the ROM I hope I didn't fry anything. I tried and tried to reset things but no luck. I don't have a backup of stock Dev ROM unfortunately...is there a way to reset back to stock(out of the box state)? I still have root and TWRP recovery works fine.
Anyone help please?
Sent from my SM-N910V using XDA Free mobile app

Sent from my SM-N910V using XDA Free mobile app

shpotik said:
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
If you want to get the NJ5 ROM up and running without issues I would suggest flashing the NJ5 stock restore tar file in Odin, then flash TWRP recovery in Odin. Once that is done boot into TWRP and flash SU, then flash the ROM. I was having the same issue yesterday and this fixed things for me.

+1 on what airmaxx23 has recommended. Caution: Make damn sure you ODIN the stock restore file intended for the DE, not the retail. If you just want to get back to a fully functional DE without the ROM then ODIN the stock restore file, ODIN TWRP and flash SUPERSU in recovery. You don't have to flash the ROM.

jpcalhoun said:
+1 on what airmaxx23 has recommended. Caution: Make damn sure you ODIN the stock restore file intended for the DE, not the retail. If you just want to get back to a fully functional DE without the ROM then ODIN the stock restore file, ODIN TWRP and flash SUPERSU in recovery. You don't have to flash the ROM.
Click to expand...
Click to collapse
Can you point me into direction of stock restore file? Thanks
Sent from my SM-N910V using XDA Free mobile app

shpotik said:
Can you point me into direction of stock restore file? Thanks
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
I linked all the files you need for the DE in my original response.

shpotik said:
Can you point me into direction of stock restore file? Thanks
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
Here you go: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937. Make sure you go to post #2 and select the stock restore file for the DE.

I am having problems with mine, too
After getting into trouble yesterday with a phone that stuck in Verizon logo screen, I was able to restore from backup.
Then I started noticing weird things that I believe were working a day ago.
I cannot download any email attachments, cannot create folders on sdcard, cannot install xposed or even install Fora offline dictionary files I downloaded from PlayStore. I never flashed custom ROMs on my DE, just flashed TWRP and then rooted it. I am still running original SW N910VOYU1ANI1. Screenshots and photos are saved just fine (burst shots on sdcard and regular photos on extsdcard).
Any Ideas? I've tried to restore from pre-root backup, then restored my image that has root and some applications but cannot move from there.

inseek said:
After getting into trouble yesterday with a phone that stuck in Verizon logo screen, I was able to restore from backup.
Then I started noticing weird things that I believe were working a day ago.
I cannot download any email attachments, cannot create folders on sdcard, cannot install xposed or even install Fora offline dictionary files I downloaded from PlayStore. I never flashed custom ROMs on my DE, just flashed TWRP and then rooted it. I am still running original SW N910VOYU1ANI1. Screenshots and photos are saved just fine (burst shots on sdcard and regular photos on extsdcard).
Any Ideas? I've tried to restore from pre-root backup, then restored my image that has root and some applications but cannot move from there.
Click to expand...
Click to collapse
Here is what I would do if I were you:
1. Go into TWRP Recovery and do a complete wipe (system, data, cache, delvik). Do not select recovery.
2. While in TWRP do a factory reset
3. In TWRP, RESTORE the backup you mentioned.
4. While in TWRP clear cache and delvik again
5. Power off the phone and remove the battery
6. Replace the battery and boot
7. If the phone boots normally then power off the phone, boot into recovery and flash SuperSU (Do not try to restore any "image", just flash SuperSU.zip)
8. Reboot the phone

jpcalhoun said:
Here is what I would do if I were you:
1. Go into TWRP Recovery and do a complete wipe (system, data, cache, delvik). Do not select recovery.
2. While in TWRP do a factory reset
3. In TWRP, RESTORE the backup you mentioned.
4. While in TWRP clear cache and delvik again
5. Power off the phone and remove the battery
6. Replace the battery and boot
7. If the phone boots normally then power off the phone, boot into recovery and flash SuperSU (Do not try to restore any "image", just flash SuperSU.zip)
8. Reboot the phone
Click to expand...
Click to collapse
Although I did it already almost the same way multiple times since yesterday, I'll try it again.
How do I do #2 in your list from TWRP?
Thanks.

inseek said:
Although I did it already almost the same way multiple times since yesterday, I'll try it again.
How do I do #2 in your list from TWRP?
Thanks.
Click to expand...
Click to collapse
Go to "Wipe" then "Format Data" then type "yes" and hit "go". This will completely remove all data. Under "Advanced Wipe" check "dalvik", "system", "data", and "cache" and wipe those as well.
If that doesn't work you're going to have to start fresh.

inseek said:
Although I did it already almost the same way multiple times since yesterday, I'll try it again.
How do I do #2 in your list from TWRP?
Thanks.
Click to expand...
Click to collapse
When you're in TWRP and select Wipe, there will appear a "swipe bar" that when swiped will perform a Factory Reset. It is the first screen you see when you select Wipe on the home screen. Do the Factory Reset and then clear cache, delvik, system and data. You can do the Factory Reset before clearing cache etc or after clearing cache etc. It really doesn't make a difference in what order you do the Factory Reset, just do it.
If this process doesn't get you back to normal then another option is to flash the stock restore file for NJ5 availble in the Android Development Section. But, lets do the process I've outlined first.

jpcalhoun said:
Here is what I would do if I were you:
1. Go into TWRP Recovery and do a complete wipe (system, data, cache, delvik). Do not select recovery.
2. While in TWRP do a factory reset
3. In TWRP, RESTORE the backup you mentioned.
4. While in TWRP clear cache and delvik again
5. Power off the phone and remove the battery
6. Replace the battery and boot
7. If the phone boots normally then power off the phone, boot into recovery and flash SuperSU (Do not try to restore any "image", just flash SuperSU.zip)
8. Reboot the phone
Click to expand...
Click to collapse
I did everything up to the #7, then powered the phone. I am getting all bunch of errors like "com.sec.phone has stopped" and other I don't remember. It shouldn't be this way, right?
Then I powered the phone off and on again, this time I got the setup wizard without error messages and flashed SU and then installed Xposed. So far, so good. Will install couple apps to see how it goes.
Thanks, jpcalhoun!

airmaxx23 said:
If you want to get the NJ5 ROM up and running without issues I would suggest flashing the NJ5 stock restore tar file in Odin, then flash TWRP recovery in Odin. Once that is done boot into TWRP and flash SU, then flash the ROM. I was having the same issue yesterday and this fixed things for me.
Click to expand...
Click to collapse
do i have to extract the file with 7zip ?

inseek said:
I did everything up to the #7, then powered the phone. I am getting all bunch of errors like "com.sec.phone has stopped" and other I don't remember. It shouldn't be this way, right?
Then I powered the phone off and on again, this time I got the setup wizard without error messages and flashed SU and then installed Xposed. So far, so good. Will install couple apps to see how it goes.
Thanks, jpcalhoun!
Click to expand...
Click to collapse
Glad you got it working. I'd have to see the error messages to try, I emphasize try, to determine what might be causing them. Often after flashing or using ODIN to install software you'll get an error message until the system has been rebooted. You should probably power off you phone, again, pull the battery, replace the battery and reboot to see if you continue to get error messages. You shouldn't be getting error messages during boot unless you have installed something that has turned a service off or has altered a service that the system is asking for (that's not technically well stated, but I think you get the point). Exposed Framework is great and enables users to customize many things in Android. But, not all the modules work the same on every device, and in fact some modules will not work at all on the Note 4. If you're trying to run a module that does not work as advertised then you should uninstall that module or not select that particular customization. A misbehaving module can cause problems that manifest themselves in funny ways.

shpotik said:
do i have to extract the file with 7zip ?
Click to expand...
Click to collapse
Yes, extract it with 7zip.

Rooted OTA?

Hi, is is possible after rooting to replace TWRP with the stock recovery, stay rooted and enjoy OTA updates.
Rooting is out of question, but besides the fact that 3.2.0 is still not available from the Oneplus website and it is hard to judge which unofficial source is trustworthy, I would prefer not to have to reroot and install xposed each time I flash a full image.

I am also interested in this.
Is this possible without wipe?
I guess root and xposed should be reinstalled even after OTA:

ErzlordCaron said:
Hi, is is possible after rooting to replace TWRP with the stock recovery, stay rooted and enjoy OTA updates.
Rooting is out of question, but besides the fact that 3.2.0 is still not available from the Oneplus website and it is hard to judge which unofficial source is trustworthy, I would prefer not to have to reroot and install xposed each time I flash a full image.
Click to expand...
Click to collapse
Download complete ROM from here: https://www.androidfilehost.com/?fid=24591020540823780
1. Booted into TWRP wiped Cache & Dalvik
2. Flashed Full ROM 3.2.0
3. Wiped Cache & Dalvik
4. Flashed systemless SU and systemless Xposed v85.7
5. Wiped Cache & Dalvik
6. Reboot
You will not lose data and be updated at the same time.

nidhish91 said:
Download complete ROM from here: https://www.androidfilehost.com/?fid=24591020540823780
1. Booted into TWRP wiped Cache & Dalvik
2. Flashed Full ROM 3.2.0
3. Wiped Cache & Dalvik
4. Flashed systemless SU and systemless Xposed v85.7
5. Wiped Cache & Dalvik
6. Reboot
You will not lose data and be updated at the same time.
Click to expand...
Click to collapse
Thanks, but I know how to do that - aside from the fact that I would like to get my ROM from Oneplus or at least a dedicated XDA-dev thread, instead of some link in some forum. The question was if I can flash the original recovery to be able to receive OTA updates.

TWRP installed; Do I need anything else to flash CM13?

Title basically says it all.
I have been able to install TWRP on a S4 Mini. Do I need anything else to flash CM13?

riahc3 said:
Title basically says it all.
I have been able to install TWRP on a S4 Mini. Do I need anything else to flash CM13?
Click to expand...
Click to collapse
No, but most people would flash gapps 6 too, else you will miss a lot (must be done at the same time as the ROM the first time to set permissions)

IronRoo said:
No, but most people would flash gapps 6 too, else you will miss a lot (must be done at the same time as the ROM the first time to set permissions)
Click to expand...
Click to collapse
What I ment is before flashing it....Afterwards/during of couse Ill flash gapps

riahc3 said:
Title basically says it all.
I have been able to install TWRP on a S4 Mini. Do I need anything else to flash CM13?
Click to expand...
Click to collapse
Copy CM13 rom and gapp in your sd card.
Backup your old firmware through twrp.
Do a factory Reset from Wipe.
And install CM13 and gapp respectively.
And enjoy ^_^

syednawaz said:
Copy CM13 rom and gapp in your sd card.
Backup your old firmware through twrp.
Do a factory Reset from Wipe.
And install CM13 and gapp respectively.
And enjoy ^_^
Click to expand...
Click to collapse
checked every file hash matches, did exactly as written, done all of above and it doesn't work
TWRP went on in less than 10 second does that sound normal ? and how do you know if its actually on there?

Nope. Installation take atleast 2 or 3 minutes.
and if its installed properly you would have seen different rom from the stock.
Here is what i use for s4 mini(i9192). Also used it on i9190 model as well.
http://forum.xda-developers.com/galaxy-s4-mini/development/rom-aokp-rom-25-apr-2016-t3366314
and these steps mentioned in the website.
A. Initial install
1. Copy ROM and Gapps to your external SD Card or internal memory
2. Boot into recovery
3. Wipe
4. Install ROM and Gapps
5. Reboot
Its simple. Should have worked.
I hope you have installed your model rom.

A question the system format is required to install the rom ??

juanpabloml said:
A question the system format is required to install the rom ??
Click to expand...
Click to collapse
In TWRP Swipe for factory reset will do the job. you can also do dalvik /art cache in advance wipe. System or other wipe never did it for changing roms.

syednawaz said:
In TWRP Swipe for factory reset will do the job. you can also do dalvik /art cache in advance wipe. System or other wipe never did it for changing roms.
Click to expand...
Click to collapse
Ie that enough only to make WIPE FACTORY RESET AND WIPE DALVIK CACHE is not necessary to the FORMAT SYSTEM, DATA AND CACHE ??

sorry i do not understand.
to install a rom just do a factory reset. nothing else is necessary.
If you do not do factory reset, sometimes you will not be able to install a new version of rom(for example, from kitkat to lollipop).
if you do not do factory reset its called dirty flash.
for example
you are using custom rom cm13. and it has a new update released, you go in twrp recovery and install the updated rom without doing factory reset. this way you can keep all the application and data you have.
i hope i am making some sense. it is hard for me to explain.
well do some flashing and you will understand but always make a backup.

Downgrading Oreo to Nougat OnePlus 3

I'm running Android Oreo on the Beta line. I've felt that Camera quality used to be better in Nougat, and occassionally phone heats up with Oreo. So I'd like to switch back to Nougat. But I've seen a couple of threads mentioning about a potential data loss(whole internal storage getting wiped) and needing to install a rollback build before installing a stable Nougat ROM. Could someone shed some light into this? Is flashing the rollback build really necessary if I can flash the stable OOS 4.5.1 via TWRP? And, would I lose data in internal storage during the procedure? Thanks in advance.

wHiTeWoLf007 said:
I'm running Android Oreo on the Beta line. I've felt that Camera quality used to be better in Nougat, and occassionally phone heats up with Oreo. So I'd like to switch back to Nougat. But I've seen a couple of threads mentioning about a potential data loss(whole internal storage getting wiped) and needing to install a rollback build before installing a stable Nougat ROM. Could someone shed some light into this? Is flashing the rollback build really necessary if I can flash the stable OOS 4.5.1 via TWRP? And, would I lose data in internal storage during the procedure? Thanks in advance.
Click to expand...
Click to collapse
The info you asked for and the steps with links everything is available here: https://forums.oneplus.com/threads/guide-how-to-go-from-oreo-to-stock-nougat.661713/

tnsmani said:
The info you asked for and the steps with links everything is available here: https://forums.oneplus.com/threads/guide-how-to-go-from-oreo-to-stock-nougat.661713/
Click to expand...
Click to collapse
I checked the thread and noticed that it's all about installing via the stock recovery. My phone's bootloader is unlocked and I have TWRP installed. So my question is, do I really need to install the rollback build? Can I not directly flash the 4.5.1 zip file via TWRP and be done with it? Or is there a purpose to installing the rollback version? I mean I read in that thread that after installing the rollback version via stock recovery, a factory reset should be done(which would erase the whole internal storage I assume?) and then the 4.5.1 zip file should be flashed. If I could use the advanced wipe option in TWRP to wipe the cache, data and system partitions and install the 4.5.1 zip file, do I need to go through the tedious procedure of installing via stock recovery, which would potentially erase my whole internal storage?

wHiTeWoLf007 said:
I checked the thread and noticed that it's all about installing via the stock recovery. My phone's bootloader is unlocked and I have TWRP installed. So my question is, do I really need to install the rollback build? Can I not directly flash the 4.5.1 zip file via TWRP and be done with it? Or is there a purpose to installing the rollback version? I mean I read in that thread that after installing the rollback version via stock recovery, a factory reset should be done(which would erase the whole internal storage I assume?) and then the 4.5.1 zip file should be flashed. If I could use the advanced wipe option in TWRP to wipe the cache, data and system partitions and install the 4.5.1 zip file, do I need to go through the tedious procedure of installing via stock recovery, which would potentially erase my whole internal storage?
Click to expand...
Click to collapse
Why would OnePlus provide the rollback build if there are other reliable methods of downgrading?

I think rollback version is for stock recovery users and data loss + . And if you decrypted your data already downgrading is just flash zip in twrp and no data loss but you keep decrypt.

drmuruga said:
I think rollback version is for stock recovery users and data loss + . And if you decrypted your data already downgrading is just flash zip in twrp and no data loss but you keep decrypt.
Click to expand...
Click to collapse
You mean the dm-verity thing? So it will be fine if I flash the Nougat zip file and install SuperSU binaries via TWRP to fix the dm-verity issue? That's what I've been waiting for as an answer. Thanks.

Can I stay encrypted when making a clean upgrade to OOS 5.0.8?

I am currently on the last open beta OOS, rooted with supersu and twrp-3.2.3-0. I know that i need to make a clean install of 5.0.8, so i shall wipe data/system/cache/dalvik, flash the latest 5.0.8 full zip, then reboot to recovery to flash magisk and then finally reboot to system.
My concern is - my phone is currently encrypted. Can i simply update as planned above, or do i need to take any additional steps to remain encrypted or go to decrypted state.
What could be the advantages of remaining encrypted or going decrypted?

msafiri said:
I am currently on the last open beta OOS, rooted with supersu and twrp-3.2.3-0. I know that i need to make a clean install of 5.0.8, so i shall wipe data/system/cache/dalvik, flash the latest 5.0.8 full zip, then reboot to recovery to flash magisk and then finally reboot to system.
My concern is - my phone is currently encrypted. Can i simply update as planned above, or do i need to take any additional steps to remain encrypted or go to decrypted state.
What could be the advantages of remaining encrypted or going decrypted?
Click to expand...
Click to collapse
Since you are on OOS (though beta), flashing 5.0.8 should not affect your encryption status. Your plan is ok.
Encryption is related to security. Decrypted means lesser security though I have no idea by how much. It is your call.

Yup, switching betweeb Beta to stable OOS will not affect encryption in anyway. Encryption will only be removed IF you manually format your data partition or the recovery does it for you.

abhibnl said:
Yup, switching betweeb Beta to stable OOS will not affect encryption in anyway. Encryption will only be removed IF you manually format your data partition or the recovery does it for you.
Click to expand...
Click to collapse
Thank you. That was helpful. So in my case, i would have to erase data partition using TWRP to update from open beta to OOS 5.0.8, so the partition would get decrypted. But then i believe clean flashing the 5.0.8 zip would re-encrypt the data partition. Is my understanding correct?

msafiri said:
Thank you. That was helpful. So in my case, i would have to erase data partition using TWRP to update from open beta to OOS 5.0.8, so the partition would get decrypted. But then i believe clean flashing the 5.0.8 zip would re-encrypt the data partition. Is my understanding correct?
Click to expand...
Click to collapse
No, when you "wipe data", it doesn't remove encryption. When you "format data", it removes encryption. I hope the difference is clear enough for you to grasp easily.
all you need to do is, if you have twrp, make sure you have OOS 5.0.8 zip, Magisk zip, working TWRP image - available in internal memory.
Then you need to Wipe System, Cache, Data - Do not check Internal Storage/Memory. or simply Factory reset from within TWRP. Then flash OOS 5.0.8 zip. Once it's done, flash TWRP recovery image from within TWRP. At this step, make sure you "reboot" back to recovery. If you will reboot directly to system, it will replace twrp with stock recovery.
Once you reboot to TWRP, flash magisk and you are all set!

abhibnl said:
No, when you "wipe data", it doesn't remove encryption. When you "format data", it removes encryption. I hope the difference is clear enough for you to grasp easily.
all you need to do is, if you have twrp, make sure you have OOS 5.0.8 zip, Magisk zip, working TWRP image - available in internal memory.
Then you need to Wipe System, Cache, Data - Do not check Internal Storage/Memory. or simply Factory reset from within TWRP. Then flash OOS 5.0.8 zip. Once it's done, flash TWRP recovery image from within TWRP. At this step, make sure you "reboot" back to recovery. If you will reboot directly to system, it will replace twrp with stock recovery.
Once you reboot to TWRP, flash magisk and you are all set!
Click to expand...
Click to collapse
Yep, i understand the difference in the operations on the data partition now. Thank you once again for the clarification.

abhibnl said:
No, when you "wipe data", it doesn't remove encryption. When you "format data", it removes encryption. I hope the difference is clear enough for you to grasp easily.
all you need to do is, if you have twrp, make sure you have OOS 5.0.8 zip, Magisk zip, working TWRP image - available in internal memory.
Then you need to Wipe System, Cache, Data - Do not check Internal Storage/Memory. or simply Factory reset from within TWRP. Then flash OOS 5.0.8 zip. Once it's done, flash TWRP recovery image from within TWRP. At this step, make sure you "reboot" back to recovery. If you will reboot directly to system, it will replace twrp with stock recovery.
Once you reboot to TWRP, flash magisk and you are all set!
Click to expand...
Click to collapse
One small addl. info. After flashing TWRP, there is no need to reboot to recovery. Simply flash Magisk right after TWRP and then boot to system. Flashing Magisk at that stage prevents TWRP being overwritten by stock recovery.
EDIT: or you can skip flashing TWRP and boot back to recovery after flashing the ROM and then flash Magisk alone before booting into system. Either way, you save one step.

abhibnl said:
No, when you "wipe data", it doesn't remove encryption. When you "format data", it removes encryption. I hope the difference is clear enough for you to grasp easily.
all you need to do is, if you have twrp, make sure you have OOS 5.0.8 zip, Magisk zip, working TWRP image - available in internal memory.
Then you need to Wipe System, Cache, Data - Do not check Internal Storage/Memory. or simply Factory reset from within TWRP. Then flash OOS 5.0.8 zip. Once it's done, flash TWRP recovery image from within TWRP. At this step, make sure you "reboot" back to recovery. If you will reboot directly to system, it will replace twrp with stock recovery.
Once you reboot to TWRP, flash magisk and you are all set!
Click to expand...
Click to collapse
I successfully completed the clean flash from last open beta to 5.0.8 and have magisk 18.0/twrp 3.2.3-0. Going forward, can i accept a new OTA update say 5.0.9 directly, or should i have to flash the full zip again? also would the process change when going to Pie later on?

msafiri said:
I successfully completed the clean flash from last open beta to 5.0.8 and have magisk 18.0/twrp 3.2.3-0. Going forward, can i accept a new OTA update say 5.0.9 directly, or should i have to flash the full zip again? also would the process change when going to Pie later on?
Click to expand...
Click to collapse
I always download the full OTA zip and flash it manually wiping only system and cache/dalvik partitions, and I never had any issues whatsoever. Sure you will need to reflash magisk since your kernel and firmware will be flashed again.

msafiri said:
I successfully completed the clean flash from last open beta to 5.0.8 and have magisk 18.0/twrp 3.2.3-0. Going forward, can i accept a new OTA update say 5.0.9 directly, or should i have to flash the full zip again? also would the process change when going to Pie later on?
Click to expand...
Click to collapse
Since you have Magisk and TWRP, the OTA either will not download or if it downloads, it will not flash. So you need to download the full zip (usually, the full zip will be automatically downloaded when the update detects changes to your system ie. root) and flash it. So long as you use the same above mentioned method to flash the full zip, Magisk will automatically flash going forward and your TWRP and Magisk will be intact. When going to Pie, since it is a different version ie. from Android 8 to 9, you should wipe system, data, Dalvik and cache before flashing Pie.

tnsmani said:
Since you have Magisk and TWRP, the OTA either will not download or if it downloads, it will not flash. So you need to download the full zip (usually, the full zip will be automatically downloaded when the update detects changes to your system ie. root) and flash it. So long as you use the same above mentioned method to flash the full zip, Magisk will automatically flash going forward and your TWRP and Magisk will be intact. When going to Pie, since it is a different version ie. from Android 8 to 9, you should wipe system, data, Dalvik and cache before flashing Pie.
Click to expand...
Click to collapse
Thanks. That clears my doubts.