Full fresh factory rom! - Galaxy S3 Neo Q&A, Help & Troubleshooting

Hello...
I was on MotionRom v17 and since it has some bugs i decided to go to stock....i wiped everything via Twrp 3.0 including internal storage....
Then i booted to download mode and flashed stock firmware using odin....
I booted stock firmware but i see now that motionrom problems like overheat,,low speaker volume are present now on stock.....
Now i want to ask if is there any hidden partition that needs to be wiped in order to get full fresh factory stock rom ?

Related

Cant figure out how to install custom rom, without loosing root acces

Dear XDA
I have been an android user for many years and rooting has been one of the things I always did to my devices. I am an owner of a Note 3, which I have rooted succesfully and used X-NOTE 13 rom for long time. Last week I wanted to try something new and after that everything seems to be impossible. Before I install any roms I always perfom full wipe of, system, data, cache, dalvik cache etc. (I do it inside the recovery). Afterwards I tried to install CRASH ROM V9 and the progress went fine. When the phone rebooted the strange things started to happened I couldn't find the rom's extra menu and couldnt find any of the functions that the rom contained. I just thought that it was problem with the rom itself therefore I tried to went back to X-NOTE, but without any luck. The X-NOTE installed probably but I couldnt boot into it, it was stucked at the "Samsung Note 3" logo. I tried to wipe cache and dalvik but without any luck and every time I rebooted from the recovery the recovery says "it seems your device doesnt have root access" and the recovery tries to gain root access.
Then I couldnt understand anything of what was happening so I went to stock using ODIN. After installing stock rom I used CF-ROOT and everythings went smooth and I could use SuperSU inside the stock rom. Then I installed a recovery and it didn't mentioned anything about root access, so I was ready to install my custom rom...at least I thought so....I installed X-NOTE again (because I knew that this rom worked before without any problems) and after the progress was done I couldnt boot into the rom again, it was stucked. I wiped the cache and dalvik and as soon I clicked reboot in recovery it tells me that I am not rooted.
Then I did the same thing again, went back to stock, installed CF-ROOT and recovery. This time I installed CRASH ROM instead and I could boot into the system, but the rom still misses the "rooted features" etc.
In other words, what have I done wrong? I cant seem to find the problem and I think that I have tried every possible solution?
Informations:
Model: ​SM-N9005
STOCK ROM: Tried both N9005XXUENB4 (German) and N9005XXUENC2 (Nordic firmware)
Custom Rom: Tried both X-NOTE and CRASH ROM
Recoveries used: TWRP, CWM and Philz CWM
Kernels: Tried with stock one and X-NOTE kernel 1.5
I hope you can help me I cant live with stock roms
Thanks in advance
Regards,
Nepoznati
Nepoznati said:
Dear XDA
I have been an android user for many years and rooting has been one of the things I always did to my devices. I am an owner of a Note 3, which I have rooted succesfully and used X-NOTE 13 rom for long time. Last week I wanted to try something new and after that everything seems to be impossible. Before I install any roms I always perfom full wipe of, system, data, cache, dalvik cache etc. (I do it inside the recovery). Afterwards I tried to install CRASH ROM V9 and the progress went fine. When the phone rebooted the strange things started to happened I couldn't find the rom's extra menu and couldnt find any of the functions that the rom contained. I just thought that it was problem with the rom itself therefore I tried to went back to X-NOTE, but without any luck. The X-NOTE installed probably but I couldnt boot into it, it was stucked at the "Samsung Note 3" logo. I tried to wipe cache and dalvik but without any luck and every time I rebooted from the recovery the recovery says "it seems your device doesnt have root access" and the recovery tries to gain root access.
Then I couldnt understand anything of what was happening so I went to stock using ODIN. After installing stock rom I used CF-ROOT and everythings went smooth and I could use SuperSU inside the stock rom. Then I installed a recovery and it didn't mentioned anything about root access, so I was ready to install my custom rom...at least I thought so....I installed X-NOTE again (because I knew that this rom worked before without any problems) and after the progress was done I couldnt boot into the rom again, it was stucked. I wiped the cache and dalvik and as soon I clicked reboot in recovery it tells me that I am not rooted.
Then I did the same thing again, went back to stock, installed CF-ROOT and recovery. This time I installed CRASH ROM instead and I could boot into the system, but the rom still misses the "rooted features" etc.
In other words, what have I done wrong? I cant seem to find the problem and I think that I have tried every possible solution?
Informations:
Model: ​SM-N9005
STOCK ROM: Tried both N9005XXUENB4 (German) and N9005XXUENC2 (Nordic firmware)
Custom Rom: Tried both X-NOTE and CRASH ROM
Recoveries used: TWRP, CWM and Philz CWM
Kernels: Tried with stock one and X-NOTE kernel 1.5
I hope you can help me I cant live with stock roms
Thanks in advance
Regards,
Nepoznati
Click to expand...
Click to collapse
weird.
all the rom you mentioned xnote & crash come with root access inside.
When you said you used all those 3 recoveries, did you try each rom with each recovery ?
and when you flash those rom, did you follow to do a clean full wipe as mentioned on each OP thread ?
clean full wipe is not only wipe cache and dalvik, but also the data (factory reset).
antique_sonic said:
weird.
all the rom you mentioned xnote & crash come with root access inside.
When you said you used all those 3 recoveries, did you try each rom with each recovery ?
and when you flash those rom, did you follow to do a clean full wipe as mentioned on each OP thread ?
clean full wipe is not only wipe cache and dalvik, but also the data (factory reset).
Click to expand...
Click to collapse
Yes I have and tried several other combinations too. First time I installed X-NOTE I wiped everything and installed X-NOTE without problems.
I cant seem to break the code, I am getting frustrated hour by hour. I have double checked everything, I am on the NC2 bootloader with the NC2 kernel, when trying to install X-NOTE I get stuck at "Samsung Glaxy Note 3" - I cant understand what the problem may be and it is beginning to be personal :/ heheh
But seriously what could I have done wrong?
Nepoznati said:
Yes I have and tried several other combinations too. First time I installed X-NOTE I wiped everything and installed X-NOTE without problems.
I cant seem to break the code, I am getting frustrated hour by hour. I have double checked everything, I am on the NC2 bootloader with the NC2 kernel, when trying to install X-NOTE I get stuck at "Samsung Glaxy Note 3" - I cant understand what the problem may be and it is beginning to be personal :/ heheh
But seriously what could I have done wrong?
Click to expand...
Click to collapse
To be frank... I have no idea. U flash before earlier, means u know how to flash it.
What I could think of, is just the recovery.
I ve been using cwm chenglu all this time (the one reported with less bugs, and most recommended at any rom thread). And jump from rom to rom every 1 week at least with no issue.
I will try tonite use twrp to flash rom. I will let u know if I face any problem.
SOLVED
antique_sonic said:
To be frank... I have no idea. U flash before earlier, means u know how to flash it.
What I could think of, is just the recovery.
I ve been using cwm chenglu all this time (the one reported with less bugs, and most recommended at any rom thread). And jump from rom to rom every 1 week at least with no issue.
I will try tonite use twrp to flash rom. I will let u know if I face any problem.
Click to expand...
Click to collapse
Finally, finally and finally solved!
Well it seems strange but the problem was the official kernel inside the stock roms that made it almost impossible to run any custom rom.
What I did to solve the problem:
1. Went back to stock rom using a rom with the newest baseband NC2, ex. N9005XXUENC2
1a. I did have som problems getting the bootloader updated, which means I was force to install it over ODIN 3.09 - use this bootloader NC2 BOOTLOADER (Thanks soloilmeglio for the bootloader)
2. I used CF-ROOT to gain root access
3. Then I installed CWM 6.0.4.8 recovery as recommended from antique_sonic (Updated few hours ago!)
4. Install the CivZ-SnapKat-Rev3.1-sm_n9005-4.4.2.zip kernel
5. Lets the phone reboot and check that everything works!
7: Boot into recovery and wipe system, data, cache, dalvik cache
8. Install the custom rom
Dont ask me why the kernel wasn't working from beginning and why it was "corrupted" after installing another custom rom - but now everything works as it should!
Thank you very much antique_sonic for helping me!
Nepoznati said:
Finally, finally and finally solved!
Well it seems strange but the problem was the official kernel inside the stock roms that made it almost impossible to run any custom rom.
What I did to solve the problem:
1. Went back to stock rom using a rom with the newest baseband NC2, ex. N9005XXUENC2
1a. I did have som problems getting the bootloader updated, which means I was force to install it over ODIN 3.09 - use this bootloader NC2 BOOTLOADER (Thanks soloilmeglio for the bootloader)
2. I used CF-ROOT to gain root access
3. Then I installed CWM 6.0.4.8 recovery as recommended from antique_sonic (Updated few hours ago!)
4. Install the CivZ-SnapKat-Rev3.1-sm_n9005-4.4.2.zip kernel
5. Lets the phone reboot and check that everything works!
7: Boot into recovery and wipe system, data, cache, dalvik cache
8. Install the custom rom
Dont ask me why the kernel wasn't working from beginning and why it was "corrupted" after installing another custom rom - but now everything works as it should!
Thank you very much antique_sonic for helping me!
Click to expand...
Click to collapse
Good then to know ur phone is okay.
I fully wipe with twrp last nite. And flash xnote. Hang at boot after done.
Fully wipe again, and flash assassins. A lot fc here and there.
I flash back cwm chenglu, full wipe, and flash back xnote. Now it runs nicely.
My phone not suit with twrp.
antique_sonic said:
Good then to know ur phone is okay.
I fully wipe with twrp last nite. And flash xnote. Hang at boot after done.
Fully wipe again, and flash assassins. A lot fc here and there.
I flash back cwm chenglu, full wipe, and flash back xnote. Now it runs nicely.
My phone not suit with twrp.
Click to expand...
Click to collapse
It could probably be a problem with TWRP as you mentioned earlier. After using CWM everything went smooth after updating my kernel. Last night I couldnt hold me back to try one more time, and I flashed X-NOTE with TWRP and I got the same problem as described in #1 post. Then I installed CWM and flashed X-NOTE again and everything got messed up. Then I restored everything, force installed the kernel and bootlaoder. After that installed CWM and then I was able to run X-NOTE without any problem.
I am not a professional developer but I may think that the problem is TWRP when it tries to flash the kernel under the process with may results in some problems. When using CWM from the beginning I do not get any problems but when using TWRP I need to restore everything back.

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.

A500FU problem after moving from cm13 to stock

Hello,
I did have CM13 installed on sm-a500fu and wanted to go back to stock rom. Downloaded right version (TWO-A500FUXXU1BOJ6-20151119145810 - 5.02. )) and flash process was without problem (ODIN) .Then i wanted twrp back and i cant do this no matter which version of twrp i use(twrp2.8.7.0-a5ultexx-19082015.tar,twrp-2.8.7.0-a5ultexx-20082015.tar). Recovery flash goes ok but cannot enter recovery.
Phone is always on Samsung logo
My suggestion is to flash again stock ROM, boot in stock recovery and wipe data/factory reset. Reboot to stock ROM normaly and after that you have to follow the steps to root and install twrp as mentioned in the other thread dedicated to it (I assumed you did that once when you flashed CM13).
In fact that's what I did on my phone...
Flash full stock and once done do a factory reset in stock recovery, do this 3 times, then flash twrp.
From the giver of stock roms

One Plus 2 Recovery Problem

So i was rooting my One Plus 2. While flashing the nee ROM i accidentally cleared the dalvik cache and the Internal storage too. this cleared my old ROM as well as new ROM. The phone went into bootloop. I somehow managed to flash OP2 Stock ROM
But now the problem is I cant reboot my phone into recovery, I tried flashing a new recovery but nothing happens. I lost my Volte update.
PLEASE HELP ?
atharva96 said:
So i was rooting my One Plus 2. While flashing the nee ROM i accidentally cleared the dalvik cache and the Internal storage too. this cleared my old ROM as well as new ROM. The phone went into bootloop. I somehow managed to flash OP2 Stock ROM
But now the problem is I cant reboot my phone into recovery, I tried flashing a new recovery but nothing happens. I lost my Volte update.
PLEASE HELP ?
Click to expand...
Click to collapse
If u have stock recovery then u shud load bootloader (fastboot) Redo the root procedure from scratch ,problem solbed ..
Sent from my ONE A2003 using Tapatalk
Hi. Can you please provide a link for the stock Rom? Did you copy it to your phone by sideload? Will it work on CM Recovery with unlocked bootloader? Mine always boot to CM recovery everytime I power on my phone.
Thank you!

Device bootloop

Hello. My device reboot into TWRP only after reboot (TWRP or System). I tried to reset data into AICP ROM in settings. Install again ROM don't works. Also restore from backup dont works. Help me :/
seems like this one trouble;
https://forum.xda-developers.com/note-4/help/sdcard-empty-installing-rom-t3030736
will try flash the stock one after night. If anybody knows solution, please help me.
After 356 milions of flashing twrp and wiping my phone finally update.zip (stock OS) transfered into phone (earlier still bugs). Then transfered stock.img (image of stock recovery) into phone and flashed it and... My backup worked. I'm embarrased. Will charge my phone and try to update to the lastest version. Then I'll check that my phone have stock or twrp of recovery. Idk what happened last night!
I could install the stock ROM (i had stock recovery and custom ROM). After boot, device runs ~40 sec then rebooting. In recovery i did clean data, then the stock OS works fine.

Categories

Resources