Database Info

[Q] My rom Wont flash

So i made a rom and when i type fastboot flashall is works fine but when i try to boot it just gets stuck on google screen i know how to unbrick and all that i just want to know how to fix the problem were i cant boot into my rom

How can we help you fix your rom without any source of your code... It's problem in the ROM source, upload it on github and post it here, maybe someone who is experienced in making roms will help.

Isus <3 said:
How can we help you fix your rom without any source of your code... It's problem in the ROM source, upload it on github and post it here, maybe someone who is experienced in making roms will help.
Click to expand...
Click to collapse
how do i upload it

poptarticus456 said:
how do i upload it
Click to expand...
Click to collapse
I never used github.com, use your brain I'm sure it's not hard.

Here is another questions how do i change the name of my rom

Why am I skeptical that you made a ROM?

Wakamatsu said:
Why am I skeptical that you made a ROM?
Click to expand...
Click to collapse
I'm betting built would be a better choice of word here. I'm also betting he built aosp if he's flashing with fastboot. I'm betting he's missing some binaries that are causing the bootloop.

yes its an aosp i could try re installing the binaries

OP, what branch or release tag are you building? Also, we're talking about hammerhead, right?
In any case, I think you should be wiping userdata partition when running `fastboot flashall`, I believe there's a fastboot argument for that (I believe aosp's flash scripts take `-w`).
That said, "unbricking" - as you called it - is as easy as using factory images to flash back to factory state. When running custom builds, you should be able to debug and learn from it. Tbh, if you did, you probably wouldn't be here asking this, at least not without sharing some meaningful logs.
a maguro wrote this.

android 5.0.2 and yes hammerhead

So here is every thing i know ok i am pulling a log right know with logcat then i will post it here i use both fastboot flashall and fastboot -w flashall is there a better pull the dump file

here it is
https://github.com/poptarticus456/help/blob/master/README.md

poptarticus456 said:
here it is
https://github.com/poptarticus456/help/blob/master/README.md
Click to expand...
Click to collapse
It seems there are some missing packages, issue/missing data.layout_version and QComKeymaster. No idea how to fix it but those we`re some of the E(rrors) in the log.

Haven't looked at the log yet (I will when I get back home), but, OP, you got all the binaries from Google right? And extracted them? You should have several folders under /vendor.
Edit: Yeah, stuff is missing alright.

where do i extract the binaries

Wwhat do i Do then ive ran the binaries it still wont work ive ran lunch aosp_hammerhead-userdebug let me know

Seriously?
Just read everything on the following link:
https://source.android.com/source/building.html
a maguro wrote this.

[Recovery] TWRP 3.1.1 for Xperia X Compact

Greetings!
I'd like to present a TWRP recovery for the Xperia X Compact. This release should work on Xperia X single and dual-SIM variant of the device. I am an owner of Xperia X, but some users reported that my recovery works just fine on its smaller brother.
DISCLAIMER:
I'm not responsible for any damage done to your device. You have been warned.
REQUIREMENTS
Unlocked bootloader
Working ADB and Fastboot (You can get the latest version through Android Studio or by visiting this site)
FEATURES
MTP support
ADB Sideload
Backups and restores almost every partition
Full SELinux support
Working encryption. You can access /data within recovery
USB-OTG
DOWNLOADS
INSTALLATION
Unlock the bootloader
Download the file
Put the following code in CMD/Terminal:
Code:
fastboot flash recovery twrp-3.1.1-kugo-*.img
//Replace * with the version you want to flash
Unplug the cable
Press Volume Down + Power to activate the recovery. When installed properly, the device should vibrate funnily, purple LED should appear and after a couple of seconds, you should see the TWRP screen.
Enjoy!
BUILD
You need to sync the OmniROM and vendor blobs from DonkeyCoyote. You can find my sources on GitHub.
android_device_sony_loire_common
https://github.com/omnirom/android_bootable_recovery/commits/android-7.1
Thanks:
@grayleshy - for initial TWRP
@AndroPlus for some of his flags
OmniROM team for sources
If you find my work useful, consider buying me a cup of coffee

it works perfectly! well can't say I tried all functions yet, but it certainly seems so.
thank you so much. finally a proper lastest version of twrp for XC that supports encryption on nougat.
btw. you have to flash it over fotakernel as described in OP. (hotbooting did not work. blank screen.)
I did try other regular X twrp versions with the same result in the past in hopes of finding something better, so the issue was likely the same since I hotbooted them too for a fast test. I guess that's what you get for being lazy. doh.
thanks again for posting it here.
/tuxen

Thank you for sharing.

thanks
Thanks for sharing brother
Working ⚒ perfectly on stock 7.0
no problem

Perfect, thanks. Only annoyance is that I can only reboot the system or power off now.

XperienceD said:
Perfect, thanks. Only annoyance is that I can only reboot the system or power off now.
Click to expand...
Click to collapse
That shouldn't work anyway. I can enable these flags if you want.

eagleeyetom said:
That shouldn't work anyway. I can enable these flags if you want.
Click to expand...
Click to collapse
For all I use the other options there's no need to go out of your way, but if you do make another for whatever reason having the options would be nice.

XperienceD said:
For all I use the other options there's no need to go out of your way, but if you do make another for whatever reason having the options would be nice.
Click to expand...
Click to collapse
It didn't work for me on X. I can enable them in the next version.

realtuxen said:
it works perfectly! well can't say I tried all functions yet, but it certainly seems so.
thank you so much. finally a proper lastest version of twrp for XC that supports encryption on nougat.
btw. you have to flash it over fotakernel as described in OP. (hotbooting did not work. blank screen.)
I did try other regular X twrp versions with the same result in the past in hopes of finding something better, so the issue was likely the same since I hotbooted them too for a fast test. I guess that's what you get for being lazy. doh.
thanks again for posting it here.
/tuxen
Click to expand...
Click to collapse
What do you mean by hot booting? I did this to boot to twrp without installing and have no problem
Code:
fastboot boot twrp.img
Thanks for the twrp, with this I can make full backup before trying to update to 7.1 or 8.0 later :good:

MTP is not working in this version. Everything else is top notch, will test backup/restore a bit later and report back.

trewelu said:
What do you mean by hot booting? I did this to boot to twrp without installing and have no problem
Code:
fastboot boot twrp.img
Thanks for the twrp, with this I can make full backup before trying to update to 7.1 or 8.0 later :good:
Click to expand...
Click to collapse
Exactly. I know hotbooting is not the best description, but you understood anyway.
Strange, I am not a flashophile so I usually just booted twrp this way after a upgrade with flashtool. When the phone was connected to the pc anyway.
But it only works for me with the androplus version, oshmoun's version won't boot that way either. It's not the first time I have talked odd twrp behaviour though, as another guy could not get the androplus one to work at all. I have no reason to doubt him, as this is pretty casual stuff.
I see you are still on MM, I have been on N since it came out and if I remember correctly I backed up ta just before N came out (exploit and N came out very close to each other), took the ota, and unlocked BL. So I performed all the 'fastboots' (better word? heh) on that and 7.1.1. Perhaps the bootloader changed someway? I have no idea.
Edit: if I learned to read properly the first time, you are NOT on MM (doh) but 7.0. Sorry and even more strange. Does MTP work for you? (see below)
---------- Post added at 20:00 ---------- Previous post was at 19:58 ----------
kekistaneerefugee said:
MTP is not working in this version. Everything else is top notch, will test backup/restore a bit later and report back.
Click to expand...
Click to collapse
MTP works absolutely fine here..

This version uses Sony init, so you can see the Sony screen and led indicator while entering the recovery mode. I'm not planning to change it before creating an official TWRP.

eagleeyetom said:
This version uses Sony init, so you can see the Sony screen and led indicator while entering the recovery mode. I'm not planning to change it before creating an official TWRP.
Click to expand...
Click to collapse
Is this in response to something functional, or just general cosmetics info? Doesn't the sony screen origin from the bootloader? How should a official twrp look while booting it? I get the sony boot and led then the TWRP boot image, isn't that normal when booting fotakernel replaced by TWRP? ie. the bootloader handles it when turning the phone on while holding vol down.
An official version would sure be nice. I more than appreciate what you already done. So just take your time.

realtuxen said:
But it only works for me with the androplus version, oshmoun's version won't boot that way either. It's not the first time I have talked odd twrp behaviour though, as another guy could not get the androplus one to work at all. I have no reason to doubt him, as this is pretty casual stuff.
Edit: if I learned to read properly the first time, you are NOT on MM (doh) but 7.0. Sorry and even more strange. Does MTP work for you? (see below)
Click to expand...
Click to collapse
Strange, I don't have problem booting twrp without installing for either of twrp.
I'm on 7.0. I tried to update to 7.1, but I don't get signal if I do the ta_poc + tobias drm fix method, and the drm is still marked as broken.
I really hate mtp and avoid it. I don't think I even have mtp working properly on my pc. I can't help you test that one. Sorry.

trewelu said:
Strange, I don't have problem booting twrp without installing for either of twrp.
I'm on 7.0. I tried to update to 7.1, but I don't get signal if I do the ta_poc + tobias drm fix method, and the drm is still marked as broken.
Click to expand...
Click to collapse
Why are you running it through both ta_poc and Tobias rootkernel with drm fix?
Either you use ta_poc to mount your ta backup from before the bootloader was unlocked thereby bringing the whole trim area back including drm.
Or you use Tobias rootkernel to fix or 'emulate" drm.
Both tools can disable dm verity, sony ric, etc. there is no reason (other than likely creating trouble) to run the kernel image though both tools?!
If you for example run a boot.img with drm fix through ta_poc it will remove the drm fix first. So I imagine things could go wrong of you apply drm fix again (if that is what you're doing) after using ta_poc.
I really hate mtp and avoid it. I don't think I even have mtp working properly on my pc. I can't help you test that one. Sorry.
Click to expand...
Click to collapse
Lol I hate it general too, it can come in handy when only twrp is booted though. I am not sure I have any drivers installed either. Regardless I can access a drive resembling my phone labeled 'mtp device' in 'my computer' when I boot twrp.
Edit: sorry for sidetracking the thread a bit.

eagleeyetom said:
NEEDS TESTING
USB-OTG
Click to expand...
Click to collapse
Thanks! and i can confirm that USB OTG works well.

Working on Sony Nougat
This is the only TWRP I can decrypt my data with on Sony Nougat Stock ROM, Thanks !

realtuxen said:
Both tools can disable dm verity, sony ric, etc. there is no reason (other than likely creating trouble) to run the kernel image though both tools?!
Click to expand...
Click to collapse
Using both tools stems from users reporting they had to to get Magisk to work.

XperienceD said:
Using both tools stems from users reporting they had to to get Magisk to work.
Click to expand...
Click to collapse
There was an info in one of threads, that you should get the stock kernel first through TA_POC and then through kernel repack tool. If you did not, it would work, but occassionally reboots. I am now on 7.1.1 build 206 with Genesis Kernel 1.05 (no_DRM patch version) and it works ok.
As for TWRP, thanks for this! It works ok. Can not fastboot it, must be flashed in recovery parition, but no deal for me. Only thing that I wonder, there are options to backup system, data etc, but not Internal SD (/data/data). Why?

Hi I have a question, I have N 7.1.1, and i want to root it, so i need the twrp, if I flash this twrp, its okay? Ty!

twrp for pixel 3a

The website below shows instructions on how to install twrp on the 3a. But when i go to the twrp website, they only have a recovery image for the xl. Are those recovery images interchangable?
MOD Edit:- Links Removed

Lol not even close. Don't try it. Or read ****ty articles like that, for that matter.

When the TWRP website has the builds up for the 3a (Sargo), that is when you download it and use it.

bigw34 said:
When the TWRP website has the builds up for the 3a (Sargo), that is when you download it and use it.
Click to expand...
Click to collapse
Or when I get it working lol. I've already booted TWRP on sargo but stuff won't mount. Close tho.

ZVNexus said:
Or when I get it working lol. I've already booted TWRP on sargo but stuff won't mount. Close tho.
Click to expand...
Click to collapse
Is it just /data that wont mount or everything?
I'm mulling rebuilding my env from scratch to simply build twrp without encryption support (low hanging fruit and all), if it's just due to the fact that /data is encrypted, I'd appreciate a copy as I'm only building twrp to be able to nandroid without encryption.

I know its too soon but I def miss having a custom recovery esp in cases when things do not flash correct and you have to undo them lol.

Trust me when TWRP is up for 3a you will definitely get a article on XDA/thread on 3a section. don't follow these spammy sites/blogs which does nothing but more of a click bait.

SacredDeviL666 said:
Trust me when TWRP is up for 3a you will definitely get a article on XDA/thread on 3a section. don't follow these spammy sites/blogs which does nothing but more of a click bait.
Click to expand...
Click to collapse
Sorry. I didn't really know. Thank you for the advice.

TheManii said:
Is it just /data that wont mount or everything?
I'm mulling rebuilding my env from scratch to simply build twrp without encryption support (low hanging fruit and all), if it's just due to the fact that /data is encrypted, I'd appreciate a copy as I'm only building twrp to be able to nandroid without encryption.
Click to expand...
Click to collapse
Literally everything besides the vendor image lol. At least that means I can load the kernel modules from touch as they are in the vendor image, but that's about it so for.
I decided to re base my trees and redo everything but this attempt doesn't even boot, or even get to the splash screen. Sad.

Heres hoping for some good news lol

Android 11.

Has anyone tried the Android 11 dp1 gsi on there Google pixel? I'm going to try later but thought would ask here 1st.

ttocs99 said:
Has anyone tried the Android 11 dp1 gsi on there Google pixel? I'm going to try later but thought would ask here 1st.
Click to expand...
Click to collapse
Yeah, I have. System partition isn't big enough for it, we'd need to resize it with like fdisk or something.

Voltz100999 said:
Yeah, I have. System partition isn't big enough for it, we'd need to resize it with like fdisk or something.
Click to expand...
Click to collapse
Besides partition resizing and flashing GSI (as described on official developer website), is there any other steps required for it to boot successfully?
I've tried flashing the smaller official GSI without GMS, but it is not booting at all. Can't figure out the cause yet.

I even repartioned my phone and can't get any GSI working. Someone did open a ticket with phhusson here however:
github.com/phhusson/treble_experimentations/issues/1161

oasisfeng said:
Besides partition resizing and flashing GSI (as described on official developer website), is there any other steps required for it to boot successfully?
I've tried flashing the smaller official GSI without GMS, but it is not booting at all. Can't figure out the cause yet.
Click to expand...
Click to collapse
Yeah no, it doesn't boot for me either, I think it might be an AVB issue but i'm not certain of that.

Voltz100999 said:
Yeah no, it doesn't boot for me either, I think it might be an AVB issue but i'm not certain of that.
Click to expand...
Click to collapse
AVB should not bother on Pixel 1 if bootloader is unlocked, especially if any custom ROM can be flashed without problem. I think it's probably SELinux-related issue, maybe set to permissive could help. (I've not tried)

oasisfeng said:
AVB should not bother on Pixel 1 if bootloader is unlocked, especially if any custom ROM can be flashed without problem. I think it's probably SELinux-related issue, maybe set to permissive could help. (I've not tried)
Click to expand...
Click to collapse
Interesting, though I don't know how we would set SELinux to permissive without booting first, maybe we'd need a kernel to set it for us? I dunno, this whole thing is really confusing.

Yeah so much for Google phones and universal treble support LOL
Pathetic

Flipz77 said:
Yeah so much for Google phones and universal treble support LOL
Pathetic
Click to expand...
Click to collapse
Can't argue with that, but it wont help us figure out how to get this working.

Clue
Here's a clue:
According to this certain audio libraries are needed to boot the quack GSI so maybe its the same for 11?
github.com/phhusson/treble_experimentations/issues/1196

xtremeed2705 said:
Here's a clue:
According to this certain audio libraries are needed to boot the quack GSI so maybe its the same for 11?
github.com/phhusson/treble_experimentations/issues/1196
Click to expand...
Click to collapse
I gave that a look and even tried it, its missing the libeffectsconfig.so file, yet I couldn't add it because /system is not mountable in twrp. We need another way.

Google has released the final build for android 11, will there be a port for the Pixel?

Deleted.

Development [KERNEL]Despair Kernel

Mission:
The purpose of this project is to increase efficiency of the Pixel 7 series devices by merging functional patches with minimal bloat.
If you submit bug reports without a log, you may be prosecuted...or executed.
Disclaimer:
If your device fails to comply with your standards of what you consider functioning, I am not liable. This is provided free of charge and does not come with a warranty. Although, if you provide a log, I can provide some sort of assurance that I will look into your issue.
You must have verity and verification disable to flash this for the time being!
To do so you will need to flash vbmeta.img using the command below followed by wiping the device.
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
Installation:
-Download ZIP for kernel and extract
-Use the below commands to flash from bootloader/fastboot
-fastboot reboot bootloader
-fastboot flash dtbo dtbo.img
-fastboot flash boot boot.img
-fastboot flash vendor_kernel_boot vendor__kernel_boot.img
-fastboot reboot fastboot
-fastboot flash vendor_dlkm vendor_dlkm.img
Links:
Downloads:
Kernels - Google Drive
drive.google.com
Telegram:
Despair
You can view and join @despairchat right away.
t.me
Source:
https://github.com/DespairFactor/pantah
Credits:
Google

A question, for curiosity sake...
*because it is coming from a very ignorant, noob place
With the change of Magisk now needing to patch the boot_init instead of the usual boot.img, would your kernel need to make the same adjustments? I was just looking at your directions and saw the command line for fastboot flashing boot, and I've been obsessively on the How To guide and there is a certain need of a sensitivity to flashing to the boot instead of the boot_init right now while the initial word gets out of the change...
I also mention this because it seems that this was developed under the Pixel 6 and all your documentation still seem to point to that device still....so....
i have absolutely no experience in kernel building and only dabbled in employing using custom kernels in the past, so I may have no idea what I'm talking about....i was just wondering if it's a possibility or eventuality...

You're source is nill if you didn't notice. And just a bit of an edit needed dude.

SeanHacker said:
You're source is nill if you didn't notice. And just a bit of an edit needed dude.
Click to expand...
Click to collapse
it's uploading still and yeah, I need to update that

simplepinoi177 said:
A question, for curiosity sake...
*because it is coming from a very ignorant, noob place
With the change of Magisk now needing to patch the boot_init instead of the usual boot.img, would your kernel need to make the same adjustments? I was just looking at your directions and saw the command line for fastboot flashing boot, and I've been obsessively on the How To guide and there is a certain need of a sensitivity to flashing to the boot instead of the boot_init right now while the initial word gets out of the change...
I also mention this because it seems that this was developed under the Pixel 6 and all your documentation still seem to point to that device still....so....
i have absolutely no experience in kernel building and only dabbled in employing using custom kernels in the past, so I may have no idea what I'm talking about....i was just wondering if it's a possibility or eventuality...
Click to expand...
Click to collapse
the init_boot is not touched with this so that magisk image that you flashed is untouched! I am hoping to get AnyKernel working soon enough or maybe another dev will hop on it and beat me to it. There is a bit of a problem with how our images are made for this device and how AnyKernel works from the stuff I have tested today.

Nice to see you here.

DespairFactor said:
I am hoping to get AnyKernel working soon enough or maybe another dev will hop on it and beat me to it. There is a bit of a problem with how our images are made for this device and how AnyKernel works from the stuff I have tested today.
Click to expand...
Click to collapse
Would you mind elaborating on that? I'm working on an update to Kernel Flasher, and I'm considering taking a stab at wrapping this kernel in AK3 for testing purposes.
I suppose with init_boot being untouched, one obvious change would be preventing it from patching boot. Would that and adding vendor_kernel_boot into the mix be enough, you think?
Edit: I managed to get it to flash and work with AK3 with verity disabled, but simply patching the hashtree descriptor for vendor_dlkm in vbmeta wasn't enough to get it to work with verity enabled.

your the man @DespairFactor

capntrips said:
Would you mind elaborating on that? I'm working on an update to Kernel Flasher, and I'm considering taking a stab at wrapping this kernel in AK3 for testing purposes.
I suppose with init_boot being untouched, one obvious change would be preventing it from patching boot. Would that and adding vendor_kernel_boot into the mix be enough, you think?
Edit: I managed to get it to flash and work with AK3 with verity disabled, but simply patching the hashtree descriptor for vendor_dlkm in vbmeta wasn't enough to get it to work with verity enabled.
Click to expand...
Click to collapse
So you've packed this kernel on AK3 , flashed through your flasher app and it boots?..( i have also verity disabled )

capntrips said:
Would you mind elaborating on that? I'm working on an update to Kernel Flasher, and I'm considering taking a stab at wrapping this kernel in AK3 for testing purposes.
I suppose with init_boot being untouched, one obvious change would be preventing it from patching boot. Would that and adding vendor_kernel_boot into the mix be enough, you think?
Edit: I managed to get it to flash and work with AK3 with verity disabled, but simply patching the hashtree descriptor for vendor_dlkm in vbmeta wasn't enough to get it to work with verity enabled.
Click to expand...
Click to collapse
init_boot and vendor_boot go untouched, think of vendor_kernel_boot as more or less the replacement for vendor_boot. How did you manage to get this to work? I think AVB is now tied to init_boot and vendor_boot only for now based on what I saw in the fstab.

Just uploaded a 1.02 build to fix a couple issues. This is using the manual flashing method until I can get confirmation on what is needed for AK3 to work. After I have this information I will make it into an AK3 zip.

DespairFactor said:
Just uploaded a 1.02 build to fix a couple issues. This is using the manual flashing method until I can get confirmation on what is needed for AK3 to work. After I have this information I will make it into an AK3 zip.
Click to expand...
Click to collapse
Will we always have to disable verity on this phone for custom kernels to work or will you eventually figure out a way around it?
I really don't feel like wiping my phone.

Gordietm said:
Will we always have to disable verity on this phone for custom kernels to work or will you eventually figure out a way around it?
I really don't feel like wiping my phone.
Click to expand...
Click to collapse
There may be a way around it, we rely on capntrips to help us on this journey. He helped us do it on the Pixel 6 devices. For now, I will keep mine disabled and probably will going forward to avoid any issues.

Like this so far!
Will revisit this once i dont need to Wipe my Device anymore and theres a Flasher for this!

Larakali said:
Like this so far!
Will revisit this once i dont need to Wipe my Device anymore and theres a Flasher for this!
Click to expand...
Click to collapse
You would only need to wipe once when you disable verification, you can update using factory images or flash tool and keep it disabled after the first time and not wipe.

It's great to see a custom kernel for the P7P. Is there a description of the changes in the kernel? I'm coming from the P6P and the Kiri kernel.
After spending 2 days setting up my device, I'm hesitant about wiping. Hopefully there will be a way to flash this kernel with out changing verification.

Does it still hold true that a wipe isn't needed when disabling only verity? I think capntrips mentioned only disabling verity and not verification as well.
Regardless, I disabled both of them on my 1st flash when getting this phone and will keep them that way going forward like I did with Raven, because things ...

swieder711 said:
It's great to see a custom kernel for the P7P. Is there a description of the changes in the kernel? I'm coming from the P6P and the Kiri kernel.
After spending 2 days setting up my device, I'm hesitant about wiping. Hopefully there will be a way to flash this kernel with out changing verification.
Click to expand...
Click to collapse
They are on GitHub, it's pretty close to the stuff I added on my 6 kernels. I have added SSG IOSCHED as well. I cannot list all the changes at the moment. Feel free to check GitHub commit history for the time being.
EDIT: One thing to note, because of the complaints of display being heavy on battery usage, I undervolted the display a little bit, we will have to see how this fares for battery usage. I didn't go crazy with it because we need to maintain stability of the device especially when there can be different binnings.
Lughnasadh said:
Does it still hold true that a wipe isn't needed when disabling only verity? I think capntrips mentioned only disabling verity and not verification as well.
Regardless, I disabled both of them on my 1st flash when getting this phone and will keep them that way going forward like I did with Raven, because things ...
Click to expand...
Click to collapse
I had to disable verification cause I manually flashed. We would need him to confirm or have someone with that setup test.

thanks for the quick release!
I did not disable verity when I did my bootloader unlock and root and dont feel like starting from scatch again so will wait to see if it gets fixed with AK3. if not then will wait until I have time to do a full wipe

Nekromantik said:
thanks for the quick release!
I did not disable verity when I did my bootloader unlock and root and dont feel like starting from scatch again so will wait to see if it gets fixed with AK3. if not then will wait until I have time to do a full wipe
Click to expand...
Click to collapse
I think capntrips will be looking into this over the coming week. You can disable Verity without wiping, but not verification. If he managed to get it to work with just Verity disabled that is good enough for me as it's rather simple to disable even if you forget to after an update.