Here's attempt 2 at me trying to make a ROM from source, and just like the first time I tried (back with the R1 HD) I'm running into problems. I am following this guide by the way, but just substituting everything for cm13 where it says cm14.1.
I've decided to try and compile Lineage 13 for the G4 Play, using the device tree for Cyanogenmod 13 provided by squid2. When I tried to add the device tree created specifically for the G4 Play (harpia cm13.0) I get an error running "breakfast harpia" saying there is no msm8916.mk file. I downloaded the other msm8916-common device tree and put it in a separate directory in the device folder, and aftewards I was able to run breakfast for the harpia just fine.
Now, after running croot and "brunch harpia", I am getting more errors during the build process:
/bin/bash: mvn: command not found
make: *** [/home/administrator/android/system/out/target/common/obj/JAVA_LIBRARIES/ambientsdk_intermediates/com.cyngn.ambient.ambientsdk-1.6.0-147069776-39fe2d07.aar] Error 127
Any idea how to clear these up? I am running ubuntu 14.04.5 with openjdk 7 by the way.
The build error is that you're missing Maven (the mvn command line utility)
squid2 said:
The build error is that you're missing Maven (the mvn command line utility)
Click to expand...
Click to collapse
Thanks for the help, the build was running for about 40 minutes so far without stoppage from error. I'll wait and see if anything else comes up.
EDIT: Built successfully. Going to test soon on my own device, but I'll upload to XDA once I can get home and upload the source as well.
After flashing the ROM I built to my device, I get stuck at the boot logo (the BOOTLOADER UNLOCKED warning). I don't think the boot process gets as far as starting ADB because ADB on my computer won't detect my device, so I can't use that to pull logs. Any idea what to do here?
EDIT: Turns out my cable was faulty, and I got some logs. This folder also contains the non-functioning Lineage13 build:
https://drive.google.com/open?id=0BxupjEjigG4tcGNJZmcxMVJidWs
I'm thinking of downloading squid's CM13 and flashing the boot image from there on top of a Lineage13 flash. I can't download it now (mediafire is blocked here) but I should get around to it later tonight
UPDATE: When I replaced the boot.img with the one from squid2's CM13 it still gets stuck on the boot logo, but it vibrates after a couple of seconds of turning it on. After waiting maybe 40-50 seconds the device reboots and repeats the process. This is further than I got with Lineage's boot image, as with that it would just sit on the boot logo with no response or signs of activity whatsoever.
The problem lies in the boot image, but now I have to find what specifically in it is the problem.
jasonmerc said:
After flashing the ROM I built to my device, I get stuck at the boot logo (the BOOTLOADER UNLOCKED warning). I don't think the boot process gets as far as starting ADB because ADB on my computer won't detect my device, so I can't use that to pull logs. Any idea what to do here?
EDIT: Turns out my cable was faulty, and I got some logs. This folder also contains the non-functioning Lineage13 build:
https://drive.google.com/open?id=0BxupjEjigG4tcGNJZmcxMVJidWs
I'm thinking of downloading squid's CM13 and flashing the boot image from there on top of a Lineage13 flash. I can't download it now (mediafire is blocked here) but I should get around to it later tonight
Click to expand...
Click to collapse
Had the same problem with Moto G³ (2015) and I just use squid kernel. People seem to like squid kernel more anyway.
Related
So, I've been banging my head against the wall for a few days now, and though I usually don't post questions (90% of the time I find the answer somewhere on the interwebs) I'm a bit stuck.
So I'm trying to get used to creating my own boot images, and have found the article android-dls article among others very helpful in understanding everything (would post the link, but can't yet)
It was easy enough to find the boot image on the Fire, and I have been using the unpack_bootimg.pl to unpack the boot image, then make the necessary changes, and mkbootfs to pack up the ramdisk. Everything goes swimmingly.
The problem arises when using fastboot to boot the new boot image using the command below:
fastboot boot boot.img-kernel.gz boot.img-ramdisk.cpio.gz
It loads it to the Fire fine, but never boots. My guess is it has something to do with offsets, but to be honest, it's a bit of a blind guess. I have also attempted to repackage the boot image into a testboot.img with the same results. I've even tried just unpacking an re-packing the known good image thats already there, without changes.
Also, not sure if this is relevant information, but mkbootfs and mkbootimg was compiled in OS X (10.6.8 for those that care) directly from the android 4.0.3 source.
Does any one have any suggestions on what to try next? Or even better, any additional articles, threads, etc. that I may have missed. Any help would be appreciated.
Oh, forgot to mention, I also have the firefirefire bootloader installed (1.2) and TWRP. Don't think it matters though.
This may not apply as I do not own a KF...
Have you ever successfully used fastboot in that manner with the KF? Any kernel I mean...
I was never able to use fastboot like that with my inspire 4g... but could use it to flash the very same image quite successfully.
Dont know if that helps or not...
I've found that those scripts do not play nicely with the Fire's boot images for whatever reason, and repacking with them renders all of my images unbootable as well. I've ended up using dsixda's ROM kitchen just for the boot image scripts because those work fine. I'm not entirely sure where the disconnect is on the perl scripts, but I haven't looked at them truly extensively.
Unpacking and re-packing boot images
gumbi2400,
Have you tried loading another boot.img/rom and going back to the one you have edited? I am only asking for my own stupidity. with your post it has my mind going places, well it should not go just yet in the Kindle. I am pretty sure it not much different then myself building GhostBSD. Let me know please!
Thanks,
JohninLex
Changed the Boot Logo and now stuck at boot
I edited the fire_start_000??.png (5 total 43 though 48) to add some text. Re-loaded the zipes into the bootscreen zip file. When I used TWRP to install a factory rom (Gr6-update-modacocustomrom-kindlefire.zip)
It installed fine, and i wiped the cache and the other (Davoric?).
Now when I re-started the Kindle, it shows the "kindle fire" logo, flashes, and then re-displays the logo, but freezes there
I am in fastboot mode according to the Kindle fire utility, and cant change back to normal.
Says no device found.
I have the Android adb device in Device Manager
I can boot and reboot using ADB
But anytime I try to use the fastboot command I get the no device error
If I type in ADB DEVICES, it doesnt show up
If you can help it would be appreciated.
wayoung said:
I edited the fire_start_000??.png (5 total 43 though 48) to add some text. Re-loaded the zipes into the bootscreen zip file. When I used TWRP to install a factory rom (Gr6-update-modacocustomrom-kindlefire.zip)
It installed fine, and i wiped the cache and the other (Davoric?).
Now when I re-started the Kindle, it shows the "kindle fire" logo, flashes, and then re-displays the logo, but freezes there
I am in fastboot mode according to the Kindle fire utility, and cant change back to normal.
Says no device found.
I have the Android adb device in Device Manager
I can boot and reboot using ADB
But anytime I try to use the fastboot command I get the no device error
If I type in ADB DEVICES, it doesnt show up
If you can help it would be appreciated.
Click to expand...
Click to collapse
you could try to get to twrp by issuing:
fastboot oem idme bootmode 5001
fastboot reboot
in the case it says <waiting for device> power off the kf by holding pwr ~20sec
power on again - at some point the command gets finished
power off and on again
once in twrp you have adb available and can copy a good file over the bad one
take care of the permissions !
or just restore a backup or flash a new rom
maybe you have to check your drivers in device manager:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Sorry it took me so long to reply, got distracted by other modding projects.
@JohninLex:
I actually tried simply unpacking and re-packing the stock image that was already on there, just to make sure I was packing it back properly, but got no love.
@eldarerathis:
I think I had stumbled across the ROM Kitchen previously, but wasn't sure if it was what I was looking for. I'm fairly new to this low level of messing with Android, I have a tad bit of experience with Linux proper, but I know things can get pretty murky. I may end up ripping the scripts apart and seeing whats actually in there. Thanks for the tip!
Life is busy right now, and I haven't gotten a chance to mess around with modding my Kindle more, may be time to start again.
Hi all, I'm having problems with my Nexus 4.
I'm on CyanKang & (tried to, it said it had an error & aborted the installation) installed a nightly build which wasn't quite right - must've gotten garbled when downloading or something. Point is, my phone is stuck in a boot loop.
As it's only a 8GB one, I, somewhat stupidly, didn't keep any stable versions of the ROM I was using or backups on the device.
Now I've downloaded a stable version of the ROM but the problem is I have no way of getting the .zip onto the device. It doesn't mount on my computer & according to adb, it's unauthorised & doesn't bring up the authorisation dialogue to let me grant it authorisation. Killing & restarting adb server & unplugging & plugging in the phone again didn't make a difference.
I'm a bit lost as to what I can do to get my phone working again.
Thanks in advance.
Fixed my problem - cleared my personal data on the device which deleted the adb key. Then flashed a working boot.img with fastboot which let me authorise adb & push an update file to my phone which I could flash in recovery
Hi folks,
So, after little usage due to instability caused by the Lollipop upgrade I hadn't used the TN7 in a while. Yesterday I thought I'd have a go at reconditioning it.
Background: The bootloader has been unlocked, recovery was TWRP, I'd flashed and reflashed stock ROMs of KitKat and Lollipop several times previously. The main problem in Lollipop was that whilst the SD card files were showing up fine in FS Explorer, I couldn't see any of my files or folders when looking at local storage. Also, Google Play Services refused to update (or install using an APK).
Yesterday I grabbed the factory ROM from the nVidia site to do a full factory install and reset. I followed the instructions, flashing the recovery, boot, system, userdata, staging blob and dtb in that order. I then rebooted and...nothing. No power (or so it appears), no boot screen, no ability to get back into the bootloader, nada, zilch. When I read back through the flash commands I noticed that the final part of flashing the system image failed, which could well be the cause - I should have paid more attention.
I've searched all over and tried multiple options to get the TN7 to boot or show some signs of life. I don't even get an LED showing when plugged into a wall socket to charge.
The device doesn't show in fastboot or adb on the Mac. I did however get a small sign of life from Windows. If I hold down the power button for around 10 secs and let go, I can hear the Windows chime of a device connecting, immediately followed by a disconnect sound, the Device Manager updates but shows nothing new.
So my question is: have I completely screwed the pooch, or is there something that can be done to resurrect it?
Cheers for reading,
Gray
Evil Penguin said:
Hi folks,
So, after little usage due to instability caused by the Lollipop upgrade I hadn't used the TN7 in a while. Yesterday I thought I'd have a go at reconditioning it.
Background: The bootloader has been unlocked, recovery was TWRP, I'd flashed and reflashed stock ROMs of KitKat and Lollipop several times previously. The main problem in Lollipop was that whilst the SD card files were showing up fine in FS Explorer, I couldn't see any of my files or folders when looking at local storage. Also, Google Play Services refused to update (or install using an APK).
Yesterday I grabbed the factory ROM from the nVidia site to do a full factory install and reset. I followed the instructions, flashing the recovery, boot, system, userdata, staging blob and dtb in that order. I then rebooted and...nothing. No power (or so it appears), no boot screen, no ability to get back into the bootloader, nada, zilch. When I read back through the flash commands I noticed that the final part of flashing the system image failed, which could well be the cause - I should have paid more attention.
I've searched all over and tried multiple options to get the TN7 to boot or show some signs of life. I don't even get an LED showing when plugged into a wall socket to charge.
The device doesn't show in fastboot or adb on the Mac. I did however get a small sign of life from Windows. If I hold down the power button for around 10 secs and let go, I can hear the Windows chime of a device connecting, immediately followed by a disconnect sound, the Device Manager updates but shows nothing new.
So my question is: have I completely screwed the pooch, or is there something that can be done to resurrect it?
Cheers for reading,
Gray
Click to expand...
Click to collapse
Hi,
It can be fixed via apx mode.
Download drivers and switch to apx mode.
Follow instructions http://mobileviandroid.blogspot.in/2015/07/nvidia-tegra-note-7-apx-images.html?m=1
Remember to change your device serial number as mentioned in instructions.
I also faced the same problem as you are facing now. It fixed. If you need any help further just post. God bless. Hope it helps
DJDON1302 said:
Hi,
It can be fixed via apx mode.
Download drivers and switch to apx mode.
Follow instructions http://mobileviandroid.blogspot.in/2015/07/nvidia-tegra-note-7-apx-images.html?m=1
Remember to change your device serial number as mentioned in instructions.
I also faced the same problem as you are facing now. It fixed. If you need any help further just post. God bless. Hope it helps
Click to expand...
Click to collapse
Lol that site ripped my Tutorial! how nice of them, You should of linked the person to https://forum.xda-developers.com/nvidia-tegra-note-7/general/nvidia-tegra-note-7-apx-images-t3149839
Hello everyone,
I'm writing here, because accidentally i turned my zenfone 2 into a brick, following an indian youtuber on this link https://www.youtube.com/watch?v=BJPEc1NG_k8&t=185s&list=FLJXXdfRBIfVwi7iWKHUJJrw&index=1 while trying to update to Nougat 7.1.
The guide is very well done and precise, in fact the fault is totally mine because i accidentally launched by using ADB, the bootloader of the Zenfone 2 ZE550ML then the screen became blank on power up...
So i followed this guide https://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 stopping before point 2) and at least i reached to get out from the permanent blank screen.
Now i'm in trouble because if i use ASUS flash tools (after installing Intel Driver), i am able to see the phone and trying to install on it the .raw file, but at the end of a while, it says "Flash image Failure (Wrong image format).
Then i tried the way "2", installing it by using fastboot, i unzipped the official ROM for ZE551ML and tried to install one per one as the described in the guide, the various parts of the SO, but each time i send a command (checked many times the sintax), the software starts downloading it on the phone and then stops, saying everytime with every file "Failed".
Thinked also to ADB, but by using "adb devices" it doesn't recognize any device...
So... may the bootloader given by the guide be wrong? or an old one version? What can i do?
If i try to get into recovery mode, it just shows an USB cable forever... i'm costricted to repeat the first part of the operation with xFsTK Downloader.
I thank you for any help or suggestion.
Linx91 said:
Hello everyone,
I'm writing here, because accidentally i turned my zenfone 2 into a brick, following an indian youtuber on this link
&t=185s&list=FLJXXdfRBIfVwi7iWKHUJJrw&index=1 while trying to update to Nougat 7.1.
The guide is very well done and precise, in fact the fault is totally mine because i accidentally launched by using ADB, the bootloader of the Zenfone 2 ZE550ML then the screen became blank on power up...
So i followed this guide https://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 stopping before point 2) and at least i reached to get out from the permanent blank screen.
Now i'm in trouble because if i use ASUS flash tools (after installing Intel Driver), i am able to see the phone and trying to install on it the .raw file, but at the end of a while, it says "Flash image Failure (Wrong image format).
Then i tried the way "2", installing it by using fastboot, i unzipped the official ROM for ZE551ML and tried to install one per one as the described in the guide, the various parts of the SO, but each time i send a command (checked many times the sintax), the software starts downloading it on the phone and then stops, saying everytime with every file "Failed".
Thinked also to ADB, but by using "adb devices" it doesn't recognize any device...
So... may the bootloader given by the guide be wrong? or an old one version? What can i do?
If i try to get into recovery mode, it just shows an USB cable forever... i'm costricted to repeat the first part of the operation with xFsTK Downloader.
I thank you for any help or suggestion.
Click to expand...
Click to collapse
same here brother...i am stucked from last night..getting no help nowhere..really upset..plz let me know if you figure out something.
Which raw file version are u using
Hello everyone,
I have a very peculiar problem with getting my Essential Phone to work again. It was lying around for roughly two years as I switched to another phone. Seeing as one of my relatives needs a new phone and has really low requirements I thought I could try to set it up again. I downloaded the official drivers again (Version 1.0.0 I think) as well as the last official release of fastboot images (February 2020).
Before I switched to a new Phone I had the Essential running with Lineage OS and remember wiping it with fastboot -w after I got the new device.
Now when I try to flash anything the device won't respond. It shows up when fastboot devices is used in the bootloader, but all fastboot commands get no answer whatsoever. I then switched from the official fastboot drivers to the latest android drivers which then gave me the sending x to y message when I try to flash anything, but nothing actually happens.
Interestingly enough, I can reboot to bootloader just fine and the Lineage Recovery is still accessible eventhough it shows an:
E: Failed to bind mount /mnt/staging/emulated/media/0 on storage/emulated: No such file or directory
on the bottom which leads me to believe that my device partitions may be corrupted outside of the recovery partition and the phone is bricked. In recovery adb commands can be used and I can reboot to bootloader for example.
When trying to sideload via the "Appy Update" function of the Lineage Recovery, I get an:
Error applying update: 26 (ErrorCode::kDownloadMetadataSignatureMismatch))
everytime. I tried different methods and Roms but nothing worked so far.
Can anyone help me with regards to bypassing signature verification entirely or point me in the direction of another solution?
Thanks for reading, I hope you have a nice day!
McMeth said:
Hello everyone,
I have a very peculiar problem with getting my Essential Phone to work again. It was lying around for roughly two years as I switched to another phone. Seeing as one of my relatives needs a new phone and has really low requirements I thought I could try to set it up again. I downloaded the official drivers again (Version 1.0.0 I think) as well as the last official release of fastboot images (February 2020).
Before I switched to a new Phone I had the Essential running with Lineage OS and remember wiping it with fastboot -w after I got the new device.
Now when I try to flash anything the device won't respond. It shows up when fastboot devices is used in the bootloader, but all fastboot commands get no answer whatsoever. I then switched from the official fastboot drivers to the latest android drivers which then gave me the sending x to y message when I try to flash anything, but nothing actually happens.
Interestingly enough, I can reboot to bootloader just fine and the Lineage Recovery is still accessible eventhough it shows an:
E: Failed to bind mount /mnt/staging/emulated/media/0 on storage/emulated: No such file or directory
on the bottom which leads me to believe that my device partitions may be corrupted outside of the recovery partition and the phone is bricked. In recovery adb commands can be used and I can reboot to bootloader for example.
When trying to sideload via the "Appy Update" function of the Lineage Recovery, I get an:
Error applying update: 26 (ErrorCode::kDownloadMetadataSignatureMismatch))
everytime. I tried different methods and Roms but nothing worked so far.
Can anyone help me with regards to bypassing signature verification entirely or point me in the direction of another solution?
Thanks for reading, I hope you have a nice day!
Click to expand...
Click to collapse
I've been reading around a little, it seems like it could be a recovery issue? try the official lineage recovery if you're not already. If you can get fastboot working at all try to reflash the stock rom and go from there.
I had a similar problem. Use a windows computer with the essential drivers (you can download from reddit) and use the official cable
DO NOT use the cable supplied with the Essential phone for data transfer, it is likely to brick your phone. Use a high quality one from a reputable manufacturer!