Hi devs, this question is especially for you guys! So I tried to build AOSP 6.0 for my D6603 and the build itself was succesful but after flashing the boot, system and userdata IMGs, the device takes about 2sec before the Sony screen shows up and after 1sec the device reboots. I have followed the instructions on developer.sonymobile.com for the m-preview and changed the repo to the final 6.0_r1 branch, this is the only step I've made differently. First I used the blobs for the m-preview and after that, bc the build showed the mentioned symptoms, the ones for lollipop just to try it. For both the same result. So my question is, is it because of an bug in the aosp branch, was it a noob fault because I'm new to building roms or is it because I didn't use blobs for the final release (which aren't released yet)? Is there any way to resolve the problem by myself?
Info: I also tried using the boot.img from cm and other roms
bye
Related
I have been flashing this afternoon trying to find a ROM that meets the following needs (without going into too much detail), but have not been able to find one that will will work without bootloops.
Basically, I am looking for a CM12 5.0 ROM that supports the AK kernel with working encryption. BlissPop has been badly buggy for me since late February, and I just tried with Temaseks 8.8 (last android 5.0.X version, still supports exposed) twice. First time tried to encrypt after flashing latest AK kernel and UKM zip, but my OPO would just reboot without encrypting. Then I tried flashing on a new clean install after encryrpting, and got a bootloop. I have also tried this on some other ROMs, even some F2FS ones but it didn't work (I don't think encryption works with F2FS).
Any help would be greatly appreciated. I can give more details as necessary. I never post on XDA, but I am by no means a novice to Android or flashing.
OK,
I have posted this within another thread but have decided to start anew as other threads seem to be resolved after Rom has flashed because of changes made in the update script dealing with bootloader version. My issue is after the Rom has flashed and apologize if I missed it but have not at least seen another thread with the same issue or complaint so will once again apologize if I am not correct but my issue is or do not beleive is related to the update.
e script bootloader insertion.
Also a bit lazy in that although I will do research have come to trust advice from xda members who may reply so all and all like knowing that whatever I may find may be backed up here as opposed to spending and wasting limited time searching down the wrong rabbit hole looking for resolutions so with that said below is what I wrote on another thread whose creators issue seemed resolved after moving past the errors received in the process of flashing.
I have had a few issues with latest versions of CM.
First was errors received during the flash process. Was able to get past this a number of ways.
Change bootloader version in update script.
removed bootloader version check line altogether from the script .
Edit line in source for my current bootloader and compiling myself.
This was all find and dandy but with every one of the above mentioned changes to either flash an official nightly or one compiled myself after flashing has gone through without error I am stuck on the "Google" logo after rebooting into system. Have done a quick search and have seen a number of posts like the one mentioned above that after getting past flash errors by modifying update script or in the above case had probably worked because older script was from an update.zip created before the bootloader check had been added by CM after the flash was successful no additional issues had been experienced.
So far I have tried a number of different update.zip's from flashing a number of official nightly zips to compiling my own nightly and even going back and flashing older CM-12 versions either still on SD card or PC that I have flashed in the past without issue and depending on age flash currently without any bootloader version edits as had been created or downloaded before the check had been added and still nothing will go past the "Google" logo.
"
Have also changed versions of TWRP and at one point had seen two versions with one for caf that I do not see as I no longer see any versions on the TWRP website just link to install the TWRP Manager app but in my quick reads had seen that it had only addressed the bootloader issue but now not sure as it had disappeared once I returned for more info and to download.
I do not have any problems installing AOSP Roms as compiled, flashed and running 5.1.0 "LMY47I" for a few days now and have no issue in restoring cm12 created nandroids even though flashing the zip from which the nandroid was created results in a permanent stop on the "Google" logo the nandroid restores and boots up just fine. Also had yesterday gave cm another try as had seen a commit in hammerhead device listing my current bootloader and "LMY41I" Build Number but still "Google" logo.
Should also probably mention I fastboot flashed the image for first "LMY47D" image and then later the "LMY47I" images. After each image flash would first thing fastboot flash twrp and create a nandroid backup before doing anything but would then flash supersu reboot system and set up everything before creating a second nandroid of each. Not sure how this would effect my current cm issue but thought worth noting because am obviously confused so what I think may be related in any way can be thrown out the window . Otherwise have not seen anything helpful in researching and have even considered flashing the bootloader taken from the 5.0.1 factory image as problems began after flashing 5.1.0 "LMY47D" factory image.
One last tidbit is I have tried booting into cm after flashing both with gapps and without in the case maybe something in the gapps packages I have is screwing with things preventing from booting past the "Google" Logo
Hi, XDA. I tried to build a zImage for nexus 5 and I did everything as usual, git cloned kerenel/msm.git, git checkouted hammerhead marshmallow-mr1, got gcc 4.8 eabi, make hammerhead_defconfig, did one change in config (the only thing I need is TTL target support), make, got no compilation errors, repacked boot.img, tried to fastboot boot and my smartpone simply stuck on Google logo. I tried to compile without any changes in config and again, the smartphone got stuck at Google logo. Unluckily, I don't have UART adapter to see boot logs. What am I doing wrong? How big guys actually build kernels for n5 marshmallow?
lipol said:
Hi, XDA. I tried to build a zImage for nexus 5 and I did everything as usual, git cloned kerenel/msm.git, git checkouted hammerhead marshmallow-mr1, got gcc 4.8 eabi, make hammerhead_defconfig, did one change in config (the only thing I need is TTL target support), make, got no compilation errors, repacked boot.img, tried to fastboot boot and my smartpone simply stuck on Google logo. I tried to compile without any changes in config and again, the smartphone got stuck at Google logo. Unluckily, I don't have UART adapter to see boot logs. What am I doing wrong? How big guys actually build kernels for n5 marshmallow?
Click to expand...
Click to collapse
It depends what your building for, if your using googles source, then it won't boot on cm based ROMs, since cm is CAF based, so if your using a cm based ROM, try switching to an aosp ROM and see if it boots that
Sent from my XT1526 using Tapatalk
Hello and thank you for viewing my thread!
To start, my device is the OnePlus One, and i am running the latest Release of CyanogenMod 13 with the Latest Lightning Kernel for it's kexec/hardboot patch
I have tried multiple times, installing the multirom files, as well as flashing a factory image and flashing from a fresh install. Nothing seems to work.
The exact problem would be, even after performing the inject boot sector action, multiboot or the boot menu fails to appear.
I have no idea how to view kernel logs or anything of the sort. However i will gladly provide any logs or files if needed! Ill just have to figure them out is all.
Any help is greatly appreciated. Thank you in advance!
Edit:
1. I think i have the kernel ruled out as the problem as i have already tried a modified stock kernel, as well as bouffla's kernel.
2. The rom also doesnt seem to be the problem as i have tried both COS 12.1 and CM 13
3. The recovery seems to be ruled out as well. I rolled back to a previous version of TWRP and still have the same issue, no multiboot menu after proper installation.
4. This is really confusing. I even tried using the files built into the multirom manager application and that fails as well.
P.S. (on a semi-unrelated note)
I currently have a strong feeling it is a very low level issue (at least for my experience) due to the fact that kali nethunter is also failing to install and causing my device to brick every time i attempt an install.
Seems like there are quite a few oreo builds out. I am currently on RR Nougat and tried the one RR Oreo build and was faced with the com.android.phone has stopped on boot up. So I guess my question is do any of the other Oreo ROMs support the CDMA phone? Is there a way to fix the RR build? I was in the process of setting up my laptop to build from source but got a little confused about device tree, kernel, and propitiatory drivers. Was not sure if that was all supplied with the RR git repo or if there was something else I needed to do. Thanks.
Update: Just tried 3 other ROMS (AEX, Cosmic OS, and Lineage OS) all gave me the same error on boot up. All clean installs with wiping everything but SD card.
toasterboy1 said:
Seems like there are quite a few oreo builds out. I am currently on RR Nougat and tried the one RR Oreo build and was faced with the com.android.phone has stopped on boot up. So I guess my question is do any of the other Oreo ROMs support the CDMA phone? Is there a way to fix the RR build? I was in the process of setting up my laptop to build from source but got a little confused about device tree, kernel, and propitiatory drivers. Was not sure if that was all supplied with the RR git repo or if there was something else I needed to do. Thanks.
Update: Just tried 3 other ROMS (AEX, Cosmic OS, and Lineage OS) all gave me the same error on boot up. All clean installs with wiping everything but SD card.
Click to expand...
Click to collapse
I have the same issue with every rom I've tried.
Also im willing to brick my moto g, just to test out it works, mine is busted to crap lol.