Note 910C UK N910CXXU2COL2_N910COLB2COL1_THL ROM = can't install any other ROM - HELP
I'm in the UK and recently had some problems with bootlooping N910C, I then installed N910CXXU2COL2_N910COLB2COL1_THL to get the phone working.
I now want to install a different ROM - probably CM13 or Sixperience - I'm very open to suggestions of a low bloat mature ROM - if any exist....
Is there any obvious reason why my attempts at installing different ROMS all fail ?
Thanks for reading....
Is anyone out there ?
How are you trying to install roms? I think you have flashed a locked bootloader so won't be able to to odin any earlier base but custom roms should still flash through custom recovery. What errors are you getting?
Sent from my SM-N920C using Tapatalk
sawdoctor said:
How are you trying to install roms? I think you have flashed a locked bootloader so won't be able to to odin any earlier base but custom roms should still flash through custom recovery. What errors are you getting?
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Hi sawdoctor,
I followed these instructions:
1) Put the zip file in your SD Card
2) Reboot in Recovery Mode (use Twrp or Philz Recovery)
3) Wipe Data, Cache, Dalvik Cache and format /System (If running Philz Recovery use the "Clean before install a new rom" option)
4) Install the ROM
5) Reboot.
From Philz and got a bootloop, 3 times so far.
I then have to install THL 5.1.1 from Odin as nothing else seems to work - also I can't get a nandroid backup from current ROM or back up EFS - so experimenting is a bit risky....
Which rom are you trying to install? Also are you sure it's bootloop, if you flash a deodexed rom through recovery then first boot can take 15 mins
Sent from my SM-N920C using Tapatalk
sawdoctor said:
Which rom are you trying to install? Also are you sure it's bootloop, if you flash a deodexed rom through recovery then first boot can take 15 mins
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
After a fresh install of a custom rom it could take as much as 20+ minutes, I know because it took my note 4 910c that long to boot into erobot v12
Related
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.
Hi,
I have a SM-N900 Exoyns device. Whenever I flash any rom on it using a recovery (I have tried both CWM and TWRP) post flashing the phone doesn't turn on. I have tried CM12.1, Resurrection and Pekaka roms. Here are the steps I have tried.
1. Use Odin to first get Stock ROM
2. Boot phone up and transfer rom to the device
3. Install recover using Odin
4. Go to reocvery (CWM or TWRP) and install the zip (After formating /system and /data)
5. Reboot phone
I tried this with 3 custom roms and none seem to then boot up the phone. When the above process finishes and phone reboots I get the SM-N900 text and then when boot animation should come, nothing happens. The display is blank and stays that way.
I can however flash stock android using Odin as many times I want.
Any idea why the phone is behaving this way? Thanks
Blasphy62 said:
Hi,
I have a SM-N900 Exoyns device. Whenever I flash any rom on it using a recovery (I have tried both CWM and TWRP) post flashing the phone doesn't turn on. I have tried CM12.1, Resurrection and Pekaka roms. Here are the steps I have tried.
1. Use Odin to first get Stock ROM
2. Boot phone up and transfer rom to the device
3. Install recover using Odin
4. Go to reocvery (CWM or TWRP) and install the zip (After formating /system and /data)
5. Reboot phone
I tried this with 3 custom roms and none seem to then boot up the phone. When the above process finishes and phone reboots I get the SM-N900 text and then when boot animation should come, nothing happens. The display is blank and stays that way.
I can however flash stock android using Odin as many times I want.
Any idea why the phone is behaving this way? Thanks
Click to expand...
Click to collapse
Same problem here
What do you mean by stock? Are you trying to flash stock samsung firmware in odin but it has a problem?
Well it sounds to me that you are not even rooted dude. Flash the SuperSU zip from recovery, then you will be rooted. I don't know exactly which file to flash for Exynos models, but Google should be able to tell you.
My note 4 N910f is running the kyubi rom V7.1
I've noticed that it has changed my model number to N910c. I've checked the build prop and it says the same. Whenever I try to install an AOSP rom in recovery it aborts saying this rom is for trltexx phone is trltecan. I've tried reverting back to my stock backup flashing the original C0I3 bootloader and modem but all I get is a bootloop. Any ideas?
When installing an AOSP ROM, are you wiping system, data, cache and dalvik?
my rom is kitkat can i install lolipop custom rom ?
speedyjay said:
When installing an AOSP ROM, are you wiping system, data, cache and dalvik?
Click to expand...
Click to collapse
Yeah and I've also done a full wipe and format of internal SD card. I'm totally baffled.
Sent from my SM-N920C using Tapatalk
@SAMAN_SAM
Yes if you update your bootloader, modem and recovery @chrisbrew
Flash the latest trltexx twrp recovery
chrisbrew said:
My note 4 N910f is running the kyubi rom V7.1
I've noticed that it has changed my model number to N910c. I've checked the build prop and it says the same. Whenever I try to install an AOSP rom in recovery it aborts saying this rom is for trltexx phone is trltecan. I've tried reverting back to my stock backup flashing the original C0I3 bootloader and modem but all I get is a bootloop. Any ideas?
Click to expand...
Click to collapse
You are using the wrong TWRP recovery, the latest one can be downloaded from here:
https://dl.twrp.me/trltexx/
Hello everyone,
yes i tried the search, but i really could not find anything matching my problem
I want so gift my S4 to a friend for christmas and wanna do a full wipe + new custom rom (currently sitting on Ressurection Remix Remix 5.5.5)
When i try to enter TWRP i get stuck at the teamwin screen
I've tried the following:
- flash older TWRP again via Odin
- install newest TWRP again via TWRP Manager App
- flashing Stock Recovery (could not even get into anything, bootloop)
Any suggetions how to solve this problem?
Sorry for any grammar/vocabulary mistakes. English is not my first language
Try flashing stock rom. That also includes the stock recovery. Then reflash twrp.
GDReaper said:
Try flashing stock rom. That also includes the stock recovery. Then reflash twrp.
Click to expand...
Click to collapse
Thanks :3
do i need to root again now?
der Blonde said:
Thanks :3
do i need to root again now?
Click to expand...
Click to collapse
Unless you want to stay on the stock rom, or want to backup some apps, then no. Rooting will not be necessary if you plan on changing to a custom rom again.
rooted my s4 again,
twrp is finally working
but i cant flash the rom
Error executing updater binary in zip
anyone has an idea?
i allready downloaded the rom again but the zip is not broken
Are you using the latest version of twrp?
Yes 2.8.7.0
der Blonde said:
Yes 2.8.7.0
Click to expand...
Click to collapse
That error is caused because the recovery thinks the rom is not compatible with your phone.
Make sure your phone is compatible with the rom.
Or try these steps I found online:
1. Advance Wipe > Wipe cache, data, system, dalvik partitions.
2. Select ZIP file of your ROM and flash it.
3. You will get E:Error executing updater binary in zip (Don’t panic!)
4. Go to Reboot menu > Select Reboot to recovery.
5. After rebooting in recovery, flash the ZIP file of the ROM again WITHOUT WIPING.
Then it should work, according to the site I found it on.
The execution error indicates that the phone may not be supported by the ROM you're trying to flash..
I really need some advice here, I haven't been able to use my note 3 for a few days now.. Every time I reboot, about 3-4 mins into using I get "system ui has stopped" fc - I am using Resurrection Remix 5.6.8 MM Rom w/openGapps6stock - I have tried everything it seems.. even reflashing the stock firmware and starting from 0 again, and this system ui fc happens everytime.
Bug Report Attached.
Thanks in advance for having a look, any help would be appreciated.
R,
Jordan
Device: Samsung Note 3 Intl Qualcomm SM-N9005
PreFlash Build: LRX21V-BOK4 Stock SM LP5.0 Firmware w/cf auto rooted
Recovery: TWRP 3.0.2.
Via recovery mounts and storage .
Format system data cache .
Flash your chosen rom .
JJEgan said:
Via recovery mounts and storage .
Format system data cache .
Flash your chosen rom .
Click to expand...
Click to collapse
what do I select in twrp's mount?
Are you performing a factory wipe immediately after flashing a stock ROM?
audit13 said:
Are you performing a factory wipe immediately after flashing a stock ROM?
Click to expand...
Click to collapse
Yes, if I dont do so, the flash will suspend and give a message saying to factory reset first.
I have never seen that message when flashing any Samsung phone via Odin.
audit13 said:
I have never seen that message when flashing any Samsung phone via Odin.
Click to expand...
Click to collapse
This is flashing via TWRP 3.0.2.0
You're using twrp to flash a stock rom? I recommend using Odin or heimdall for flash a stock rom from sammobile.com.
sorry for the confusion mate. When I flash stock I use Odin only.. after all completed.. I will then factory reset again and wipe on twrp.. If I forget to wipe steps, the flash suspends with a message advising me to wipe first. I am going to update to Resurrection Remix 5.6.9 and see how it goes for stability fixes with the UI.
Possible its TWRP try Philz Recovery .
Sent from my SM-N920C using XDA-Developers mobile app