Database Users

Having Problems in flashing roms

On flashing a Custom Rom, my phone gets stucked with continous FC ("Unfortunately Phone Crashed","Press OK") just after the phone boots.
I had faced the same problem earlier so someone on XDA suggested to use twrp recovery. Then i flashed the purity rom and it worked fine, but then as you may know now, as PA is out, so flashed it and again i'm getting continuous fc error....
currently i'm using purity rom, stock kernel and twrp recovery (2.6.3.3)

I would flash back to a stock 4.2.2 and start over. I find that this is the only way I can install certain roms.

audit13 said:
I would flash back to a stock 4.2.2 and start over. I find that this is the only way I can install certain roms.
Click to expand...
Click to collapse
I already did this and again i'm facing the same problem

htrapy said:
I already did this and again i'm facing the same problem
Click to expand...
Click to collapse
Strange. Are you updating the bootloader and radio before flashing a 4.4 rom?

Are you doing a factory reset???? And flashing a proper gapps after ROM? You should always do this when going from one ROM to another. Sometimes a manual format of /system is necessary also.

no i am not updating my bootloader and radio before flashing (rather didn't know if i had to update them,fyi i bought my nexus 4 this september)....and yes i'm doing a factory reset (using the wipe option in twrp recovery which warns clearing of data, cache and dalvik memory)

[Q] Yellow Brick?

Just recently rooted my s4, was working fine or so I thought, went to flash NamelessROM, I don't think the rom is the issue, I had my s2 rooted and flashed on a weekly basis so I know about wiping, data cache, and dalvik, I flashed Rom then Gapps, and it was stuck on boot up, of course I made a nandroid and restored, but now I'm stuck on the yellow sprint screen, did my research and found it it's called a Yellow Brick, or referred to as. Found out a possible fix was downloading the kernel so I've chosen the Rooted NoData kernel to download and flash via odin. Is this what I should do or is there a better fix out there?

Sounds like you wiped everything. Can you boot into recovery?

Beezer80 said:
Sounds like you wiped everything. Can you boot into recovery?
Click to expand...
Click to collapse
Yes I can, and I tried to restore back from my nandroid which is how I'm stuck on yellow sprint screen now versus stuck on the boot for NamelessROM.

Do a factory reset in recovery and see if it boots.
That will wipe your accounts and what not but you can't boot anyway.
If it won't boot then you'll need to flash a ROM to get running. Do you still have the ROM you wish to flash on your SD card or internal storage?

Beezer80 said:
Do a factory reset in recovery and see if it boots.
That will wipe your accounts and what not but you can't boot anyway.
If it won't boot then you'll need to flash a ROM to get running. Do you still have the ROM you wish to flash on your SD card or internal storage?
Click to expand...
Click to collapse
Just got me stuck on NamelessROM boot up so I'm restoring off nandroid again. I think that flashing the kernel will fix it.

I'd get the ROM booting then play with the kernel. That's just me though.

Beezer80 said:
I'd get the ROM booting then play with the kernel. That's just me though.
Click to expand...
Click to collapse
trying that right now

JosephBallin said:
trying that right now
Click to expand...
Click to collapse
I'm trying to push a kernel through odin, I could possible try to find a way to put a kernel on my extsd and try and flash it through twrp? Would I just have to wipe cache and dalvik and flash? because when I try through odin it fails.
EDIT: I found a fix it involves unrooting most likely, but if I do I'll be back at VPUAMDC (Android 4.2.2) so could I still root with SafeRoot? Or what would be the way to root from that version?

Which firmware version did you root from? If it was MJA or MK2 you have to use one of those, you can't downgrade to MDC easily.

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" After Restoring in TWRP

I restored a backup from a few weeks ago after trying out a marshmallow based ROM (I was on lollipop prior) and after the restore process, my old phone interface came up and it was as if I never flashed the newer rom at all as expected, however, now my camera does not work at all and I could use a hand figuring out how to resolve this issue.
Things I've tried:
- Rebooting (obviously)
- Clearing cache/dalvik from recovery
- Clearing the camera app's data and cache
When I restored my backup, I chose not to restore 'boot' and 'recovery' because while I was on the marshmallow rom, I unlocked my phone's bootloader and installed TWRP (as opposed to using SafeStrap) and I didn't want to lose it.
Samsung Galaxy S5 GM-900V
Android 5.0
Baseband: G900VVRU2BOG5
Build: OptimalRom 15-5
Marshmallow rom I referenced: Norma_Note5Port_V3.4_VZW
Any advice?

So I've formatted dalvik/cache/data/internal storage and installed the older rom (OptimalRom 15-2 ) again. Did the initial setup and the camera still didn't work. I tried reflashing a known-good kernel that's compatible with this rom and that didn't seem to help.
Can anyone point me in the right direction on how to resolve this? Something must have been flashed when I installed the Note 5 rom that wasn't when I went back to OptimalRom. I just don't know what. I'll keep searching and experimenting. Thankfully I have a real recovery menu now so softbricking isn't as big of a deal.

GoTeamScotch said:
So I've formatted dalvik/cache/data/internal storage and installed the older rom (OptimalRom 15-2 ) again. Did the initial setup and the camera still didn't work. I tried reflashing a known-good kernel that's compatible with this rom and that didn't seem to help.
Can anyone point me in the right direction on how to resolve this? Something must have been flashed when I installed the Note 5 rom that wasn't when I went back to OptimalRom. I just don't know what. I'll keep searching and experimenting. Thankfully I have a real recovery menu now so softbricking isn't as big of a deal.
Click to expand...
Click to collapse
Since you have TWRP now, try doing a complete and clean wipe. Go into recovery, Wipe, Advance Wipe and select Cache, Dalvik cache, Data and Internal and swipe. Then back out to Wipe and swipe twice on the slider and install the OptimalRom of choice. then install the PB1 firmware NO Bootloader. If you still have an issue then try with the ROM kernal and flash it which I think it'sthe OG5 Kernal No Bootloader. The reason for doing this particular wipe is to get anything that may be left over from a previous ROM. This is my preference and habit from when I started running ROM's on my S3. Beanstown103 and others had recommended doing this in TWRP and haven't had any issues or problems by doing this since. Hope this may help

Thanks al50. I will give that a shot. Sorry but I'm not familiar with "PB1 firmware". what are you referencing there?

GoTeamScotch said:
Thanks al50. I will give that a shot. Sorry but I'm not familiar with "PB1 firmware". what are you referencing there?
Click to expand...
Click to collapse
It's the version that your phone is on. Look in About Phone in settings. Anyways, that’s the Zip file you install after you install the ROM. But if you're already on PB1 then you don't have to worry about that. If you have issues with the camera then try flashing the No bootloader kernal that was made for that ROM, which I believe it was OG5 but check the OP to be for sure

All sensors stopped after flash rom

I need some help, I really don't know what to do anymore..
I've installed the optimized cyanogenmod 13 and now my sensors don't work. It works randomly for about 10-20 minutes then stops. The only sensor that works without any problem is the light one..
I don't know what can I do. Can this be from hardware, even working sometimes?
All the sensors are recognized by phone, they just don't work.
I've already jumped into a lot of ROMs and nothing. I've already done a full wipe (system, data, caches, internal) and installed official stock ROM and nothing.
Now I'm on lollipop 9.0 and I can't get this to work even for 10 minutes, but I know that on other rom it will work for about 10 minutes.
What can I do?

Did you install the latest official stock or just any stock rom with Odin?

audit13 said:
Did you install the latest official stock or just any stock rom with Odin?
Click to expand...
Click to collapse
I installed the latest stock rom right from sammobile.

audit13 said:
Did you install the latest official stock or just any stock rom with Odin?
Click to expand...
Click to collapse
I don't know if has anything to do, but if you have a s4 with root, can you please verify if in your folder "persist" have anything? It stays right in the root.
Thanks!

Weird that stock didn't fix the issue. You also performed a factory wipe from stock recovery before booting the newly-flashed ROM for the first time?
Sorry, I don't have an s4 with me at the moment. I can check later today.

audit13 said:
Weird that stock didn't fix the issue. You also performed a factory wipe from stock recovery before booting the newly-flashed ROM for the first time?
Sorry, I don't have an s4 with me at the moment. I can check later today.
Click to expand...
Click to collapse
Do you mean the recovery that comes with stock rom? I never used him. My wipes I always do from TWRP

I really don't know what else I can do. I don't want to change de motherboard :/.. I still think that is from software

You should try wiping with stock recovery.

audit13 said:
You should try wiping with stock recovery.
Click to expand...
Click to collapse
Install the stock rom again, then turn off phone, power+volume up+home and do a wipe data/cache factory reset? Is this different from the TWRP wipe?
Maybe I can do this wipe via settings on the system?
On lollirom 9.0 I can't get them working even for 10 minutes

Sometimes, a wipe using stock recovery works better than a wipe using a custom recovery.
Flash with Odin and use stock recovery to wipe before booting the stock ROM for the first time.

audit13 said:
Sometimes, a wipe using stock recovery works better than a wipe using a custom recovery.
Flash with Odin and use stock recovery to wipe before booting the stock ROM for the first time.
Click to expand...
Click to collapse
Ok.. I'll try to do this and I post the result here. This not working, there's anything else I can do?

Not sure what else to try as flashing stock and wiping with stock recovery usually fixes software glitches.

audit13 said:
Sometimes, a wipe using stock recovery works better than a wipe using a custom recovery.
Flash with Odin and use stock recovery to wipe before booting the stock ROM for the first time.
Click to expand...
Click to collapse
Again, only light sensor working.. anything else?
The sensorhub test gives me PASS.

Everything was working before flashing cm13?

audit13 said:
Everything was working before flashing cm13?
Click to expand...
Click to collapse
Yes, perfectly. Never had this issues before optimized cyanogenmod 13 :/. That's why I think its from software, but I have no idea what to do anymore..

I am at a loss too. The phone shows the correct imei, baseband, and bootloader?

audit13 said:
I am at a loss too. The phone shows the correct imei, baseband, and bootloader?
Click to expand...
Click to collapse
Yes. The phone is 100% ok, just the sensors not working.. Now even for 10 minutes is working :/, just the light sensor

Anything else I can do? :/

Dont know if a logcat can help, but..
I just started the phone and searched for "gyro"
As you can see, gyro_sensor was not found.. Maybe we got something here?????
--edit--------
Searching now I found that this is something about .idc files, right in /system/usr/idc. I just don't know what file.. @audit13

How about flashing a custom rom that is based on the original stock rom?