Database Users

BLack screen after installing any rom

On my note3 (n900t), after I install any rom, which I've tried CM11, CM13, ResurrectionRemix v5.6.0 and 5.6.5, and the latest version for lollipop. Every time, it will install successfully via twrp, get to the welcome/language select screen, then the screen will go black, i.e. off. Pressing buttons or tapping the screen still turns the haptic motor, but does nothing, and the back/menu lights come on for a split second at a time, and sometimes spaz out turning on and off on their own.
these are the guides I followed, if it helps:
CM13: androiding.how/download-note-3-cm13-rom-marshmallow/
CM11: Just the wiki
RR: galaxynote3root.com/sm-n9005-galaxy-note-3-roms/resurrection-remix-rom-w-android-6-0-1-for-galaxy-note-3-marshmallow/The video in this one shows it working on a n900t, so it isnt a model compatibility thing
Is there something I've done wrong here? How can I fix this and install one of these?
(sorry about the links, I made an account to try and find help)

zxsq said:
On my note3 (n900t), after I install any rom, which I've tried CM11, CM13, ResurrectionRemix v5.6.0 and 5.6.5, and the latest version for lollipop. Every time, it will install successfully via twrp, get to the welcome/language select screen, then the screen will go black, i.e. off. Pressing buttons or tapping the screen still turns the haptic motor, but does nothing, and the back/menu lights come on for a split second at a time, and sometimes spaz out turning on and off on their own.
these are the guides I followed, if it helps:
CM13: androiding.how/download-note-3-cm13-rom-marshmallow/
CM11: Just the wiki
RR: galaxynote3root.com/sm-n9005-galaxy-note-3-roms/resurrection-remix-rom-w-android-6-0-1-for-galaxy-note-3-marshmallow/The video in this one shows it working on a n900t, so it isnt a model compatibility thing
Is there something I've done wrong here? How can I fix this and install one of these?
(sorry about the links, I made an account to try and find help)
Click to expand...
Click to collapse
Did you do all the wipes? On TWRP I always press advanced(I don't use factorey reset), then select everything but internal storage and SD, then I flash and it boots just fine.

robertofelce said:
Did you do all the wipes? On TWRP I always press advanced(I don't use factorey reset), then select everything but internal storage and SD, then I flash and it boots just fine.
Click to expand...
Click to collapse
Yep, I'm downloading the stock rom so i can get it working again, but I really want to try the rr marshmallow releases.. :|

zxsq said:
Yep, I'm downloading the stock rom so i can get it working again, but I really want to try the rr marshmallow releases.. :|
Click to expand...
Click to collapse
Remember that rr marshmallow releases don't work for SM N900. I guess that your phone is sm N9005. Right?
If it is, is awkward that you can't flash a rr marshmallow ROM

You should be in the T-Mobile note 3 forum?
Cm12.1 for the hltetmo: https://download.cyanogenmod.org/?device=hltetmo

zxsq said:
Yep, I'm downloading the stock rom so i can get it working again, but I really want to try the rr marshmallow releases.. :|
Click to expand...
Click to collapse
got exactly the same problem....Tried to flash repair stock rom with pit, with success, but doesn't change anything
can flash 5.0 stock or 5.1 port rom but not CM or AOSP..
if you find what happen....

Hi, I've had the same issue on my Note 3 N9005. I thought it was a problem caused by Knox, so I opened the original bootloader and I deleted every Knox file; then I flashed it and it works. I tried this solution with the Resurrection Remix Rom v5.6.5, but when I updated to v5.6.7 it gave me the same problem. After a sleepless night I realized that, being the problem related to hardware components (the screen), and being impossible that such components were broken, I thought that the real problem was the kernel, so I tried to flash a compatible kernel with the Marshmallow 6 version of Android and it finally works. The kernel in question was the NetHunter one (Kali Linux), that I flashed even when I flashed the bootloader, without noticing.

rikymatteo97 said:
Hi, I've had the same issue on my Note 3 N9005. I thought it was a problem caused by Knox, so I opened the original bootloader and I deleted every Knox file; then I flashed it and it works. I tried this solution with the Resurrection Remix Rom v5.6.5, but when I updated to v5.6.7 it gave me the same problem. After a sleepless night I realized that, being the problem related to hardware components (the screen), and being impossible that such components were broken, I thought that the real problem was the kernel, so I tried to flash a compatible kernel with the Marshmallow 6 version of Android and it finally works. The kernel in question was the NetHunter one (Kali Linux), that I flashed even when I flashed the bootloader, without noticing.
Click to expand...
Click to collapse
My note 3 smnN900t is doing that same thing and it sucks because I know I did everything perfectly!! What Kernel were you able to flash for it and where did you download it from? By the way thanks in advance for any help and info you can give!!!

Wrong forum
forum links .
http://forum.xda-developers.com/showthread.php?t=2574886

Please help I am having the same issue. Did anyone find a solution for this ?

New User - CyanogenMod Questions

Hello,
I received my Nexus 6P yesterday and got my SIM card activated without any issues at Verizon. I immediately took it home, unlocked the bootloader, installed TWRP, and then flashed CyanogenMod's latest nightly. After booting in, wireless networks weren't detected, and I only had 3G (no 4G LTE as I should). I restored my backup of the stock ROM that I made in TWRP and it hung at the Google logo. I'm not sure why. I then flashed all the latest factory restore images (MTC19X) to get it working again and determined that the issues I had in CyanogenMod might have happened due to the vendor.img I had on my phone at the time not being compatible with that build of CM13.
My questions are:
1) What are the known issues that would likely occur due to vendor.img being a different version than what CM13 was based on? The concept of vendor.img is new to me. I haven't had this, as far as I know, on any of my other phones (granted I'm coming from a locked Samsung Galaxy S5 that I've had for almost 2 years)
2) How can you easily tell which vendor.img CM was based on so you know which one to flash?
3) Is there anything else I should be made aware of before attempting to flash CM13 again?
4) While using CM13, do most people recommend a custom kernel? If so, which one and how stable is it? What are the benefits of switching from the stock kernel, and how simple is it to go back if there's a problem?
Thanks!!

dude...I just got the N6P and ran CM13 within hours. This is what I did...
unlocked the bootloader
downloaded the lastest (MTC19X) image off of https://developers.google.com/android/nexus/images and unpacked it into the C:\Program Files (x86)\Android\android-sdk\platform-tools folder
ran the flash-all.bat
fastbooted TWRP
installed CM13. (didn't wipe internal storage)
installed arm64 open Gapps pico
BAM!!!
right now running stock kernel. it's cool. I'm PrivacyGuard-ing the hell out of all my apps (turned off START AT BOOT and KEEP AWAKE for almost every downloaded app), though, so battery is OK
also using Kernel Adiutor but underclocking values for the CPUs doesn't seem to stick

So it likely worked for you since you had flashed the newest vendor.img first. Apparently there are compatibility issues with certain features that cause them not to work (such as WiFi) if you're using an older one.

chaoticyeshua said:
Hello,
I received my Nexus 6P yesterday and got my SIM card activated without any issues at Verizon. I immediately took it home, unlocked the bootloader, installed TWRP, and then flashed CyanogenMod's latest nightly. After booting in, wireless networks weren't detected, and I only had 3G (no 4G LTE as I should). I restored my backup of the stock ROM that I made in TWRP and it hung at the Google logo. I'm not sure why. I then flashed all the latest factory restore images (MTC19X) to get it working again and determined that the issues I had in CyanogenMod might have happened due to the vendor.img I had on my phone at the time not being compatible with that build of CM13.
My questions are:
1) What are the known issues that would likely occur due to vendor.img being a different version than what CM13 was based on? The concept of vendor.img is new to me. I haven't had this, as far as I know, on any of my other phones (granted I'm coming from a locked Samsung Galaxy S5 that I've had for almost 2 years)
2) How can you easily tell which vendor.img CM was based on so you know which one to flash?
3) Is there anything else I should be made aware of before attempting to flash CM13 again?
4) While using CM13, do most people recommend a custom kernel? If so, which one and how stable is it? What are the benefits of switching from the stock kernel, and how simple is it to go back if there's a problem?
Thanks!!
Click to expand...
Click to collapse
1) Depends on ROM /VENDOR, sometimes nothings happens then an error message, sometimes things doesnt work
2) Just download fresh the latest snapshot, release or nightly (they are much more stable then for a few years!) and vendor image (use these ones which are recommended!)
https://wiki.cyanogenmod.org/w/Install_CM_for_angler (there is a link for the vendor)
3) If you stay close on the tutorials, i dont know what should happen (flashing a rom is normally not critical, installing a recovery can be!)
4) Custom kernels can be great, but its not a must-have. Which kernel you should use depends on your wishes: better battery, more power etc.
Hope i could have help you a little bit!

kaufikauf said:
1) Depends on ROM /VENDOR, sometimes nothings happens then an error message, sometimes things doesnt work
2) Just download fresh the latest snapshot, release or nightly (they are much more stable then for a few years!) and vendor image (use these ones which are recommended!)
https://wiki.cyanogenmod.org/w/Install_CM_for_angler (there is a link for the vendor)
3) If you stay close on the tutorials, i dont know what should happen (flashing a rom is normally not critical, installing a recovery can be!)
4) Custom kernels can be great, but its not a must-have. Which kernel you should use depends on your wishes: better battery, more power etc.
Hope i could have help you a little bit!
Click to expand...
Click to collapse
Very much so. I appreciate it!

Has anyone encountered the constant popup of the Select Sim Card message? I'm using project fi and I am still unable to find a solution to this issue.

Experience : successful Resurrection Remix NEM-L51 - Meticulus's ROM v5.8.5-20171214

Hi all XDA's members and Meticulus's RR ROM contributors,
I would like to share my experience with Meticulus's RR ROM for Honor 5C.
First I tried Elite V6 with no success : bootloop, F2FS or EXT4 nothing to do ; the Elite V7 is available from Christmas but I see that there are bugs to fix for Hassan, so I gave up and restored a backup of my STOCK system.
The restore was not good as my camera and audio no longer worked...
Before I get back to the STOCK update NEM-L51C432B357, I decided to try Meticulus's RR. It was a very good idea as I now have a renamed Honor 5c to hi6250 (...) working with no bug up to now.
LTE OK, SMS OK, GPS OK, SDCARD OK, AUDIO OK, VIDEO OK, GAPPS OK, MTP OK, etc
Adaway OK, Afwall+ OK, Magisk v14 OK
+ Bonus : Evie Launcher working as it was not using with STOCK ROM (icon size issue) !
Many thanks to Meticulus and contributors for sharing this very good work.
---
To be more precise for Honor 5C owners :
DEVICE : HONOR 5C
ROM STOCK BUILD : NEM-L51C432B350
MODDED RECOVERY .. : TWRP-3.1.1-0-hi6250-v5.2.zip
ROM INSTALLED .... : RR-N-v5.8.5-20171214-hi6250-Meticulus.zip
GAPPS INSTALLED .. : open_gapps-arm64-7.1-pico-20171225.zip
---
Steps of my successful installation with SDCARD and no SIM CARD :
1- FASTBOOT the TWRP then reboot to the TWRP RECOVERY
2- Wipe all except external SDCARD
3- Install the ROM
4- Reboot to TWRP RECOVERY
5- Install the GAPPS
6- Reboot to system (RR)
7- During RR Android setup, when asked insert the SIM CARD.
It would perhaps also have been successful with the SIM CARD inserted from the beginning...
---
Questions/feature requests :
- On Resurrection Remix site, I have not found your great ROM why ?
- On XDA Dev, there is no thread "Resurrection Remix For The Honor 5C [METICULUS]" but a "[ROM][7.1.2] Resurrection Remix For The Honor 6x [METICULUS]" one, this is why I put my comments here and in the Elite thread for those like me unable to get Elite V6 or V7 working with their Honor 5C.
- One thing is really missing to me (not found in settings) : the scheduled start/stop that worked very well with the STOCK ROM.
Do you think that this useful feature could be added on a future version ?
- The double TAP for screen wake up, would be a great bonus feature (was not provided in the STOCK ROM).
- Not tested the OTG, I will tell it in this thread.
Thanks again.
---
Meticulus's replies :
1. It is unlikely that any device with a kirin processor will get "official support" for LineagOS and therefore Resurrection Remix. There just isn't enough source.
2. Just because there is no "Honor 5c" thread doesn't mean you should come here and confuse information. It makes the water muddy. There is nothing stopping you from creating a thread in the "Honor 5c General" and post your experienced there.
3. Scheduled device start and sleep is not something I will work on.
4. DoubleTap 2 Wake only works on some P9 Lite's. Other devices with different touchscreens simply do not have the hardware capability.
5. I'm glad you like the ROM but please re-post your experiences in the Honor 5c section. I intend to delete these posts...

Is working dual sim and volte
Is works dual sim and volte

Sim working fine??

What do you think solved the audio issue?
Reverting to Stock Rom backup could have helped somehow.
Renaming it maybe ? And how did you rename it? After installing this rom mine became hi6250.
I own a nmo-l31 and ever since installing EliteRom v7 i could not get the audio working. Installed EliteRom v6 , applied l-31 patch,nothing.
Trying to switch to stock rom with dload gave error
Directly flashing boot,system,cust,recovery from firmware packages didnt change anything on the userspace ,literally.My files,homescreen etc. remained the same and only recovery changed. I think i made a mistake there but who knows.
Now installed this ResurrectionRemix twrp and rom after seeing this thread.Audio still refuses to work .

thatwasmyfakeacc said:
What do you think solved the audio issue?
Click to expand...
Click to collapse
I had the same problem on my NEM-L51. The problem is (or at least i think it is), that the vendor partition is somehow corrupted.
Short explaination, the vendor partition holds some drivers which are not open source (therefore not in the android kernel) and also aren't shipped in the custom roms (because of copyright stuff). So you always need to have them, if the custom rom depends on them (and most/all of the honor 5c custom roms do so). That's also the reason why you always have to flash the custom rom over your emui5.x and if you screwed your whole system, you first need to flash a backup or get back to emui on a different way before you can flash a working custom rom again.
So that's the explaination part. I installed twrp on my device, took a complete backup, flashed aosp from meticulus, everything worked except of Audio/Videos. Flashed LineageOS from Hassan, everything worked except of audio/video playback. Flashed backup, everything worked except audio/video. WTF. I don't know why, but i believe that the backups made with TWRP were somehow not complete, because flashing all partitions (the backup was over all partitions, triple checked, made new backups from stock) didn't solve audio issues, not even on the stock backup. What I now did was getting back to stock with the dload method, and flashed again directly the lineageos from hassan, which then worked. I had a try before where i first accidentially flashed aosp again, and same problems occured again. Also the now stock backup again didn't work. That's why i think that the TWRP backups for Honor 5c NEM-L51 are somehow not right.
Tl;dr if you have audio/video playback issues, try to get back to stock (make sure those features work on your stock rom) and flash again. If it still doesn't work, custom rom is maybe not compatible with nem-l51 (only experienced that with meticulus roms, hassans work great).
thatwasmyfakeacc said:
I own a nmo-l31 and ever since installing EliteRom v7 i could not get the audio working. Installed EliteRom v6 , applied l-31 patch,nothing.
Trying to switch to stock rom with dload gave error
Directly flashing boot,system,cust,recovery from firmware packages didnt change anything on the userspace ,literally.My files,homescreen etc. remained the same and only recovery changed. I think i made a mistake there but who knows.
Click to expand...
Click to collapse
Try again with the dload method, maybe use another UPDATE.zip. I had to try it several times, device booted sometimes for ever, and suddenly it worked. No idea why, but maybe try it again.

Custom Roms is good but overal it lacks supports for long terms and quality of pictures taken are not as nice as stock ones

stevedat said:
Custom Roms is good but overal it lacks supports for long terms and quality of pictures taken are not as nice as stock ones
Click to expand...
Click to collapse
also system collect trash files that slows you down. i used to be all in for custom roms but now i dont use them because they will break in time and standby batterydrain will increase rapidly.

thelous said:
also system collect trash files that slows you down. i used to be all in for custom roms but now i dont use them because they will break in time and standby batterydrain will increase rapidly.
Click to expand...
Click to collapse
Rite, it's just for fun.

shankarjdhv125 said:
Is works dual sim and volte
Click to expand...
Click to collapse
Hi,
Dual SIM not tested, Volte I don't know if it works using my ISP (free.fr) and don't know how to check this.
An advice, don't update Magisk, I have done it on several rr (honor 5c, idol3 5.5), the result was bootloop.

Screen problem

Hi everyone,
To flash the last rom (nightly ) of LineageOS ( in Oreo,from the 2 february), i had to put the firmware 5.1.7. After flash this firmware i was able to flash the ROM but it makes my phone extremely slow and with screen issues (i can still use the tactile but the screen doesnt follow).
I restored but the problem stills then i put le last stable ROM from Oneplus on android pie (9.0.3). It is a bit better (still really slow) and after a moment i get now like a white noise (same as on TV but with color moreover) by wink ( was more and more often on Google Maps), I had to reboot cause i couldnt use more my phone.
Thanks you in advance !
Ps : I've got TWRP from siankatabg and i'm not rooted , if you want me to send log tell me how pls.

Up :good:

When you were flashing did you used this instructions?
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Flash codework's TWRP for Pie. After that reboot into recovery, wipe everything down and use clean flash instructions for your OTA. It should be able to fix any issue you were having. If not let me know.

Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.

Raidenne said:
Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.
Click to expand...
Click to collapse
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.

Ebeninyo said:
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.
Click to expand...
Click to collapse
My issues seem gone since few weeks with the last OTA (it very rarely happens now). I don't know what caused that even if i use my backup.
Thanks for your support !

Popup camera not working on xiaomi mi 9t with custom ROM

After smashing my head against the limits of the MIUI again, i decided to say goodbye to my warranty and flash a custom rom. Via TWRP I flashed the latest (stable) version of Arrow OS based on android 10Q. Everything works perfectly aside from the popup camera, that appears to be firmly locked in place feeding live feed from inside the chassis. Thinking it was an error of that release, i tried other ROMs, both Android 9 and 10, ResurrectionRemix, Lineage. With RR the problem is the same, while with Lineage, the camera asks for a calibration: it actually pops out fully does two or three pops and then it says calibration failed. The servos are working, I've opened the chassis and found no dust at all, so I've looked for a fix online. The most common one is a flash of the stock 'persist.img' image, I've tried several times via TWRP, tried a few clean flashes (ROM+image) of different versions and nothing. Am I missing something? I don't want to get back to MIUI...

Did u backup your persist partition before ? if no u can flash any other one that comes in the fastboot stock rom but u will loose L1 (netflix in HD)

The problem persists.
Badis st said:
Did u backup your persist partition before ? if no u can flash any other one that comes in the fastboot stock rom but u will loose L1 (netflix in HD)
Click to expand...
Click to collapse
I did, but even when I tried flashing different versions of persist.img ranging from fastboot stock firmware 10 to 12, with and without backup, (clean wipe, fresh recovery) the problem was still present. I'm no expert but I'd guess the OS doesn't know how to: either tell the servos to pop the camera out (Arrow OS) or recognizing the camera working when calibrating (Lineage OS). I'm trying to dig my way to the cam app in the MIUI release and to install it in the custom ROM, but I don't think it works.