Compiled ROM not booting - any Dev pls help!! - Nexus 5 Q&A, Help & Troubleshooting

Hey there,
I've compiled CM13 without any problems. Flashing my build in recovery also went without errors but after reboot I get stuck at Google logo and nothing more.
My question is how to fix this bootloop to make that ROM usable? Maybe I have to do something with source code.. I don't really know.
I would be thankful if any Dev would like to help me with this.
Thank you in advance,
Cheers

Did you put the blobs in there?

Related

Building Omnirom

hey guys.
i've been trying to build omnirom for our device for a month and still havent been able to get it boot without a bootloop.
anyone tried to give omnirom some love?
pinkflozd said:
hey guys.
i've been trying to build omnirom for our device for a month and still havent been able to get it boot without a bootloop.
anyone tried to give omnirom some love?
Click to expand...
Click to collapse
Does this help you in any way coz entropy mentioned about modem initialization problem causing reboot
http://forum.xda-developers.com/showpost.php?p=50071782&postcount=11

[Q] Personal CM 12 build gets stuck on boot

** Was not sure where to post this.
Today I was successful in building CM 12 for the first time using Docker on Ubuntu 14. The build went fine but when I try to flash my phone with the cm-12-2015-02-01.zip file the flashing goes fine without any errors but when I reboot the device it gets stuck on the Google boot screen and doesn't process to the CM boot screen. I have tried doing a full clean flash, as well as wiping cache(s).
This does not happen if I try flashing an official build from the CM site. This has something to do with my build but I cant figure out what because the build goes fine when I run it.
Thanks for the help in advance
Did you make sure you're building for hammerhead?
Lethargy said:
Did you make sure you're building for hammerhead?
Click to expand...
Click to collapse
Yes I definitely built for hammerhead.
waleed_k said:
Yes I definitely built for hammerhead.
Click to expand...
Click to collapse
Try running a repo sync and rebuild
Hi,
Did you figure it out? We are running into the same issue, build in plain Ubuntu is fine, but if we build in Docker container, then the phone stuck on boot screen.
waleed_k said:
** Was not sure where to post this.
Today I was successful in building CM 12 for the first time using Docker on Ubuntu 14. The build went fine but when I try to flash my phone with the cm-12-2015-02-01.zip file the flashing goes fine without any errors but when I reboot the device it gets stuck on the Google boot screen and doesn't process to the CM boot screen. I have tried doing a full clean flash, as well as wiping cache(s).
This does not happen if I try flashing an official build from the CM site. This has something to do with my build but I cant figure out what because the build goes fine when I run it.
Thanks for the help in advance
Click to expand...
Click to collapse
Still have not figured this out.
I think this is a generic issue about building Android in Virtual Environment (chroot, lxc, docker).
I know that someone else says that Android can be built in VE without any problems, in our company, we do have some Android projects which can be built in VE without any problems too, but somehow, some projects cannot, hope that someone knows Android and VE better can help on this.
waleed_k said:
Still have not figured this out.
Click to expand...
Click to collapse

[Completed] All i need is a working custom rom for mt6572

I have recently written a post explaining my situation, but i have not got a solution as at now. http://http://forum.xda-developers.com/android/help/custom-stock-rom-mt6572-phone-viwa-max-t3044543.
I have tried countless roms but most of them stuck at the boot logo although they install successfully. I recently learned iot would be possible if i ported the rom, but i dont know if there is a way of porting if i don't have a copy of my stock rom. The latest rom i tried was the PROJECT PURE XPERIAUI FINAL (MT6572) which also froze at the boot logo. ALL i need is a rom that will boot my phone . I need help.
Hi there,
Please give us more details about your device/firmware because that link is broken.
Thanks

Phone powers off after flashing CAF based ROMS no boot.

Hi guy,
I have been trying to figure this out for a while now and can't seam to figure it out. Everytime I flash a CAF based ROM after clicking reboot the phone turns off. During this time it is very hard to get the phone to turn back on. Holding the power button does not seam to do anything. I have to hold the power+volup+voldown for around 30 seconds let go and do it again in order to get back into recovery. I am not getting any errors at all when flashing. I really have no clue what it could be. I have tried every CAF based ROM I have come across here and they all do it. The only thing I can come up with is my phone has had the screen, camera, and battery replaced. Could one of these parts or another part be causing a problem that doesn't allow CAF based ROMS to work? I know its a long shot but thats all I can think of at the moment.
Right now I am working on trying to flash CyanogenMod from this thread. I have tried both version 13 and version 14 both have the same problem. This is what I have tried.
Flash HammerheadCAF reboot back into recovery
Flash bootloader&radio_HHZ20h+2.30.zip reboot to recovery
Flash cm-13.0-20161029-UNOFFICIAL-hammerheadcaf.zip
Flash opengapps
Flash SuperSu
Reboot
Black screen of death
What is wrong with this process? I have also tried the same process with cm-14.0-20161029-UNOFFICIAL-hammerheadcaf.zip. I am now going to try this same process with cm-14.1-20161029-UNOFFICIAL-hammerheadcaf.zip. I don't expect any difference though. Anyone have any suggestions?
Thanks,
Rocky
*****Update*****
I have tracked the problem down to CAF TWRP. I have formatted the phone which has removed everything except CAF TWRP and I am still getting the black screen of death situation. When the phone reboots it completely turns off. It will not respond unless I hold down power+volup+voldown for around 30 or 40 seconds. Then the phone will finally enter the bootloader. Are there any other recoveries that will flash CAF based ROMs? I don't know what else to do =(
Maybe don't flash supersu? Cm comes prerooted?
audit13 said:
Maybe don't flash supersu? Cm comes prerooted?
Click to expand...
Click to collapse
Thanks for your reply and time. I also tried flashing without SuperSU and it did the same thing. When I tapped reboot the phone would not turn on. I also tried just flashing the ROM and rebooting. The problem is with TWRP CAF because I have even formatted the phone so there was no ROM just TRWP CAF and when I tapped on reboot to recovery the phone just turned off. The power button wouldn't do anything. It would not even turn the phone on. The only thing I could do was hold the power+voldown+volup for 30 sec let go and press them again and go into bootloader.
Hey guys anyone else have any suggestions? I have tried sending a support ticket to twrp over a week ago. I haven't heard a word from them. I really want to use CAF ROMs
Hi!
I'm facing the same problem. I've been trying everything I can think of, and everything ended with a black screen when trying to boot:
Flashing stock again and then TWRP and CAF.
Flashing a lower version of TWRP (2.8.7.0) and then flashing CAF.
Flashing an AOSP version of CM, then TWRP for CAF and finally CAF.
Fixing permissions.
Changing filesystems to F2FS.
I tried to logcat, but adb logcat keeps waiting for the phone and it doesnt find anything.
Anybody has another idea of what could be happening or how to solve it?
Thanks!
I can flash caf, aswell as noncaf roms on my N5 just fine.
I used the CM14 darkrom CAF. Excellent performance, great battery life
i wiped the device in TWRP caf (Latest) (system,data,cache,dalvik0
Then i flashed the rom and the Darkrom gapps (use only those, as rom comes withouth a launcher. Pixwl launcher embeded into gapps package)
Wipe cahce/dalvik & reboot
It looped like: GOOGLElogo ,bootanimation ,self restart and it works perfectly fine since then
---------- Post added at 18:54 ---------- Previous post was at 18:53 ----------
I should also mention, that i use the european D821 model
I was beginning to wonder if it was just me. I felt like an ass for posting for help because I felt like it was my fault. I still have not gotten any response at all from twrp support. I really want to use car based Roms. I use to be able to when I first got the phone. Now I don't have a clue what the problem is. I am using the 820 USA model.
After doing a Google search for CAF TWRP no boot black screen and other combinations I have found posts around the web from people with the same issue. The only resolution was to revert to stock. I have sent TWRP support another email linking to this topic as well as contacted them on g+ hopefully we can get a resolution.
since i dont own the device.... no logs= we cant help you
Funny thing is twrp caf and non-caf are identical, the ONLY difference is that they are looking for a different device name when flashing. So I'd suggest to use the non-caf one, download any caf rom, edit the updater-script and replace every "hammerheadcaf" with "hammerhead" and it will flash just fine. If it really is just a twrp issue that will work. But I don't know why, I feel it's bound to be more than that...
I'm having this problem too, I can flash any non-CAF ROM and it will bootup fine, but any CAF rom will leave me in a black screen. Did you found any solution yet?
I have not been able to find a solution to the problem. TWERP tech support seams to be non existent. I have emailed them numerous times. They don't even take the time to say they will look into it =(
Dark_Eyes_ said:
Funny thing is twrp caf and non-caf are identical, the ONLY difference is that they are looking for a different device name when flashing. So I'd suggest to use the non-caf one, download any caf rom, edit the updater-script and replace every "hammerheadcaf" with "hammerhead" and it will flash just fine. If it really is just a twrp issue that will work. But I don't know why, I feel it's bound to be more than that...
Click to expand...
Click to collapse
What else could it be if we are able to flash absolutely anything else we want to flash except for a CAFE ROM?
I have never tried editting the updater script. Could you please explain how to do the things you described?
Ok I got an update. Today just for ****s and giggles I tried to flash the latest TWRP twrp-3.0.2-0-hammerhead.img on top of itself from inside TWRP using the image flashing process. I got the black screen I been getting that we are discussing here. Therefore, that tells me that the problem is not with TWRP CAF but with flash recovery's in TWRP. For some reason TWRP does not like that. Therefore, I am manually flashing the fallowing files the old fashion way by hand using the android sdk and adb.
1.) TWRP CAF
2.) The latest bootloader directly from the latest google factory image
3.) The latest radio directly from the latest google factory image
4.) Install the latest build of Dark ROM
I will report back with my findings.
Findings are epic fail. No boot, black screen of death.:crying: After holding down volup+voldown+power I am able to get back into recovery just like with flashing all the files through recovery when I first started. However, I can't get the damn thing to boot the ROM. I don't know what to think anymore. I think we just have to come to the conclusion that CAF based ROMs are out of the question for us :crying: :crying: :crying: When my son gets home and can hold the tablet while I operate the Nexus 5 maybe I will try to make a video of the problem. Hopefully this will help lead to a resolution.
Let me guess. All your phones have been repaired or are second-hand devices, aren't they?
experience7 said:
Let me guess. All your phones have been repaired or are second-hand devices, aren't they?
Click to expand...
Click to collapse
will a repaired device not work, mine has had the screen replaced. Nothing else just the screen.
experience7 said:
Let me guess. All your phones have been repaired or are second-hand devices, aren't they?
Click to expand...
Click to collapse
Yup, I have replaced the screen, why is that? Is it too much different than the original, shouldn't it work normally?
Not sure what's wrong with the hardware. No CAF for you guys, I'm sorry.
experience7 said:
Not sure what's wrong with the hardware. No CAF for you guys, I'm sorry.
Click to expand...
Click to collapse
Wait seriously? because i fixed my screen i am not able to use a caf rom on my device? That seems ridiculous, what would cause that to even be a thing? is there some sort of security flag it checks for?
Yeah I replaced the screen on mine too. Not sure how that plays a role. The only thing I can think of is unless there is a missing driver or something like that because our screens are different.
There's gotta be a way to fix this problem. I wish I knew how to build ROMs, kernels, and recoveries. I don't think anyone will go out of their way to fix a problem that doesn't directly affect them. So for me it is stock, rooted, with ElementalX till this pos croaks.
Not sure what the problem is. Fact is that your screen somehow differs from the 'original' one which causes CAF ROMs to blackscreen.
If you really, really want your phone to run CAF you have to provide a lot more information. You could try to get a running system and fetch some hardware information. Pretty sure there are apps on the Play Store that print hardware brands/model names, etc. Report your results and I'll use the same method to get mine. We should compare. Furthermore we'll need logs. Try to boot CAF. Of course it will blackscreen again but you can reboot to recovery and pull some logs. Maybe last_kmsg and dmesg where the latter one should be even more interesting.
And last but not least I'd like to tag @myfluxi here. Perhaps that's interesting for you...

A750F GSI Using Tree UI 0.9.5. Is it Possible?

Hi There I just wanted to ask as I keep seeing conflicted information on this and everytime I try i end up with a bootloop or endless loading. I use the TreeUI 0.9.5 rom for the vendor and my recovery is PBRP. My phone model is a A750F. Could anyone help as I am genuinely lost on how to install GSI's on this device. Any help would be greatly appreciated.
What gsi you tried?
I have tried many gsi's and him work very good
But there are a battery drain issue

Categories

Resources