Database Info

[Q] Vanilla kernel on Galaxy Tab 7+ (P6201)

Hi,
I've got a noob question. Is it possible to install a vanilla kernel on the P6201? I've tried to flash a cross-compiled kernel (3.8-rc1) via heimdall, but the device seems to get stuck at the very first boot screen (black screen with white "SAMSUNG Galaxy Tab 7 plus" written on it). I've succeeded to boot the device with a cross-compiled samsung-kernel-p6200 by alanorth (at least somewhat, it boots, but then it fails to run the full android environment). To make a long story short: Is it even possible to boot a vanilla kernel? Are there premade kernel configurations? And if so, do I need to tamper with the boot loader?
Many thanks

hossen0 said:
Hi,
I've got a noob question. Is it possible to install a vanilla kernel on the P6201? I've tried to flash a cross-compiled kernel (3.8-rc1) via heimdall, but the device seems to get stuck at the very first boot screen (black screen with white "SAMSUNG Galaxy Tab 7 plus" written on it). I've succeeded to boot the device with a cross-compiled samsung-kernel-p6200 by alanorth (at least somewhat, it boots, but then it fails to run the full android environment). To make a long story short: Is it even possible to boot a vanilla kernel? Are there premade kernel configurations? And if so, do I need to tamper with the boot loader?
Many thanks
Click to expand...
Click to collapse
There is no such thing as a vanilla kernel for any device. The kernel must be built with the specific device / board dependencies and OS target version There is no generic.
All you are seeing is the boot loader starting.

DigitalMD said:
There is no such thing as a vanilla kernel for any device. The kernel must be built with the specific device / board dependencies and OS target version There is no generic.
All you are seeing is the boot loader starting.
Click to expand...
Click to collapse
By vanilla kernel I meant the sources from kernel.org, as opposed to linaro/aonorth/garyd9 etc sources. I am well aware that I need to configure the sources according to the device I want the kernel to run on. As mentioned I sucessfully built aonorth's sources (samsung-kernel-p6200, run make gt_p6200_defconfig), however, carrying over the configuration is impossible. E.g., when looking at /proc/cpuinfo in the original system, the board type is said to be SDMKC210. However, in the samsung-kernel-p6200 configuration, the board chosen is "C1 board", an option that doesn't exist in the linux-3.8-rc1 sources.
I know that I got stuck at the boot loader, or maybe not, because if you don't have any output from the kernel, you don't know for sure. The kernel could have been booted, and then got stuck. Or would the screen go blank then?
I have gotten a blank screen now, w/o the boot image (white "SAMSUNG" etc written ona black screen) by setting CONFIG_S3C_LOWLEVEL_UART_PORT to 0. I'll keep looking into this. If anyone could give me a hint on how to put the console output on the screen, I'd be very grateful.
Also, could it be that the tablet only charges when a functioning kernel is flashed into it? It seem not to charge with a nonfunctioning kernel on it, even when turned off and plugged into the wall.
Happy new year

If its not charging, you may be crashing the bootlaoder which controls charging
you should do more research here
http://bootloader.wikidot.com/android:kgdb
and here
http://elinux.org/Kernel_Debugging_Tips
Also note, the android kernel is not identical to the Linux kernel

Lenovo tb3 7 essentials custom logo

Hi,
I have lenovo tb3 7 essentials tablet and I want to change the boot logo and animation with custom one. Do I need to flash a custom ROM to accomplish that or I can do that without custom ROM ? I've been told by an android developer that "this tablet is a mediatek device. Devices who have an mediatek soc usually have a logo partition. " and advised me to post here to get help to know what exactly I need to do to accomplish this task.
I really appreciate input or article about this.
Thanks,
Ahmad

Ok I did more research and found that we have bootanimation.zip and shutanimation.zip files that have the images for the boot/shutdown animation, and it can be easily updated by replacing the zip files with the new animation with proper animations. Seems does not require flashing a custom ROM.
But how to update the logo (static image) when that appears before the animation ? can I also change this logo without a full custom ROM ? I appreciate any guidance here.

I am new to this community, I appreciate any input from you. If I did something wrong, or if I should follow specific protocol to get help from others please let me know. I really appreciate that

Black boot logo and animation

Can anyone develop a boot logo (without the Unlock and signature verification warning) and boot animation without the use of TWRP? I'd love it if someone could point me to a how-to if they can't produce such a thing, please and thank you!

This would be awesome. Hopefully someone can figure it out. This was possible on the Nexus 5X but not the 6P, for some reason.

I fear with the latest SafetyNET update triggering with as little as an unlocked bootloader that this won't be possible for some time. However if there is a developer willing to tackle this, I'm willing to donate to the cause, as I'm sure others would be too. I know that many other people would love have black boot logo and the error gone as well.

Kalveitt said:
I fear with the latest SafetyNET update triggering with as little as an unlocked bootloader that this won't be possible for some time. However if there is a developer willing to tackle this, I'm willing to donate to the cause, as I'm sure others would be too. I know that many other people would love have black boot logo and the error gone as well.
Click to expand...
Click to collapse
How do we create a bounty? I have no clue. I'd throw in a dollar or two.

Well I tried changing the hex code in system\media\bootanimation.zip from white to black but that didn't do the trick. It basically just "removed" any animation whatsoever and booted up with a static white background and Google logo.
I would love someone to look into this more.

Anyone have any ideas on this?

Happened to me once. I rechecked the permissions 644 after I placed the files once again in solid explorer and there it was- not correct. Changed permissions, rechecked, permissions stood there, rebooted and it worked.

I wonder if the developer of the Weta ROM @Mentalmuso can assist. One of the main reasons I use this great ROM is to get the black boot logo (just the boot image, not the starting BL unlock warning). This way, I have a visual indicator of which slot I'm booting into. If it's black, it's slot A.

Here's one.
[BootAnimation] Darkish & Black Stock

mrZoSo said:
Here's one.
[BootAnimation] Darkish & Black Stock
Click to expand...
Click to collapse
You know, thanks for this. Actually, this thread points to another link and I used it to create my own flashable zip.

I'm stuck trying to flash a GSI, I can't figure what I'm doing wrong

Hi!
I'd like to get rid of the HTC original firmware on my U12+.
I just tried to flash GSIs of LineageOS 17 by AndyYan then AOSP 10.0 by phhusson, without luck.
I have a factory unlocked HTC U12+ (fastboot mode showing Secure Boot : Development, Secure State : S-Off, Device State : Unlocked(U)) so I went straight to the "flash GSI without TWRP" part of the official XDA tutorial: I factory reset the phone, rebooted in bootloader, then erased system and successfully flashed lineage-17.0-20191117-UNOFFICIAL-treble_arm64_avN.img.
But after reboot, I got a bootloop.
I've wanted to try the TWRP method, but upon launch it asked my password for decryption. While I'm sure of the code I've used and typed, decryption doesn't work, so TWRP didn't help.
Then I've flashed the AOSP GSI via fastboot, but then I got a "This device is corrupt. It can't be trusted and will not boot" error message.
So as suggested on another thread I've used the SD card method to flash a RUU, specifically 2Q55IMG_IMAGINE_DUGL_O80_SENSE10GP_HTC_Europe_1.30.401.2_Radio_sdm845-000201b-1807311356_release_528103_signed_2_4.zip. It flashed successfully, but then it booted to the static white HTC logo on black background and stayed there for 20 min.
I can still boot to fastboot mode/download mode, but I don't know what to do.
I can't figure what I'm doing wrong, can you help me, please?

After another attempt I've managed to go back full stock using the microSD card method.
Then I've been able to boot TWRP, which first showed a "Mount" "Decrypt data" screen, asking for a password. The 6 digits code I've used previously doesn't work. So TWRP "failed to decrypt data", also was "unable to mount storage" and "failed to unmount /system_root (device or resource busy)". As suggested, I formatted/wiped data to remove encryption.
Then I performed a factory reset, adb pushed system-quack-arm64-ab-vanilla.img to /data, then flashed it successfully to the system partition, as requested in the afore mentioned official tutorial. On reboot I get another bootloop. Bootscreens shows the HTC and Powered by Android wordmarks and also "** ORANGE **" on the top left corner of the screen.
What am I missing?! :-/

After first boot of flashed RUU at the HTC logo reboot the device. Got there myself, rebooted(using power button) and the OS booted up perfectly.
TWRP doesn't decrypt latest Pie with July Patch. So you will not decrypt it. (Wiping does not decrypt).
I used temporary TWRP, flashed permanent (with touchscreen patch), installed Magisk, Rooted, installed LeeDroid from Magisk for example.
Make sure you have a correct RUU for your CID version.
I am not sure how a project treble ROM will work on this device. You still need signed HTC drivers. I don't think we are ready now for 10 on this device for daily use. HTC did quite awful with the Pie update and many bugs are still not fixed after 6 months.

GSI tutorials advise against rooting before flashing. They advise to keep the phone full stock. What do you think about this?
I was unable to determine CID and MID yesterday from fastboot mode or TWRP, so I've downloaded the latest RUU for dual SIM and EMEA model, as my U12+ is dual SIM and I live in Europe.
Now that the phone is back to full stock, I just installed a terminal app right on the phone and executed the following:
getprop ro.cid : 11111111
getprop ro.boot.mid : empty
I understand that the phone is "SuperCID", but I don't really understand what that implies.
Regarding Treble, Treble Info by Hackintosh Five reports (translated from French by me): "Your device supports the old Project Treble version, using VNDK version 26.0."
But the U12+ is listed as supported on phhusson's wiki. A few issues are listed, but I'm fine with them.
I've read a tutorial that asks to "extract the GSI and vendor+boot zips", but then doesn't what to do with the vendor+boot zips. Do you know?
Lastly, do you know what the **GREEN** or **ORANGE** overlay means on the boot screen?
Thank you for your help!

Romano2K said:
GSI tutorials advise against rooting before flashing. They advise to keep the phone full stock. What do you think about this?
Thank you for your help!
Click to expand...
Click to collapse
SuperCID implies you can install any RUU (not specific CID). So you can "transform" your US version into european or asian... for a specific reason. No need to do that. Usually there was a specific base that was needed to install a custom ROM or Custom Recovery or people just wanted a different version because they lived in a different part of the world from where the phone was purposed.
I am guessing the **GREEN*** overlay has smth to do with the RUU (if it's embedded in the Boot animation zip (basically pictures+ sound)) or has smth to do with the nature of your tempering (S-OFF/SuperCid etc.)
with this device and serves as a warning for users/devs/internal testing.
You should find your answers on a different section. More active. I see no activity here. And it's HTC's fault for dying" on us. I myself bought the U12 just to own (probably) the last flaghsip device they make. Here's to the comeback.... but I am not sure it will be real. HTC was one of the fastest to update, for example.. until 2019. We are still with bugs and on the July patch. Right not, in reality I am just hoping for one last Pie update to fix bugs and that's it. Will give this device a 1 year run and buy something better.
So go to the Android general section where you can ask how can you compile your ROM on this device. They should help. I can not offer sufficient knowhow on this topic.

Thank you for these clarifications
The **GREEN** or **ORANGE** overlay is shown for a few seconds on the vendor logo, before boot animation. It wasn't showing before I started messing with firmwares, but nevermind
Yes unfortunately HTC is kind of dead on the smartphone front. They deserved it at the end, U12 Plus' firmware is badly translated and full of bloatware. I've been a long fan, I've had four Orange branded Windows Mobile phones and PDA phones from 2002 (17 years ago!) to 2007, then a few Android smartphones (HTC Desire <3), so I think it's sad.
Anyway I've been able to flash AOSP 10.0 GSI by phhusson with his help.
So I've just shared a quick tutorial:
https://forum.xda-developers.com/u12-plus/how-to/guide-how-to-install-generic-image-gsi-t4019151
Thank you for your help Deonix!

Romano2K said:
Thank you for these clarifications
The **GREEN** or **ORANGE** overlay is shown for a few seconds on the vendor logo, before boot animation. It wasn't showing before I started messing with firmwares, but nevermind
Yes unfortunately HTC is kind of dead on the smartphone front. They deserved it at the end, U12 Plus' firmware is badly translated and full of bloatware. I've been a long fan, I've had four Orange branded Windows Mobile phones and PDA phones from 2002 (17 years ago!) to 2007, then a few Android smartphones (HTC Desire <3), so I think it's sad.
Anyway I've been able to flash AOSP 10.0 GSI by phhusson with his help.
So I've just shared a quick tutorial:
https://forum.xda-developers.com/u12-plus/how-to/guide-how-to-install-generic-image-gsi-t4019151
Thank you for your help Deonix!
Click to expand...
Click to collapse
Interesting. Will look into your tutorial. So thank you. If the boot animation.zip was modified you will find in in root/system/[search for it] -you can lookup up each image that forms the animation to check. I myself modified the ZIP to not include the annoying audio, so i deleted it. )
So is the GSI good for daily use? I would mess around with it until i sell my HTC U11. Still using the U11 as a daily driver for the past 2 weeks. And by selling it i mean practically giving a perfectly good phone away for scrap... because it's old.

Deonix said:
I myself modified the ZIP to not include the annoying audio, so i deleted it.
Click to expand...
Click to collapse
That's clever! The HTC boot sound was annoying when I had trouble booting the bootloader, because of the tactile buttons.
Deonix said:
So is the GSI good for daily use?
Click to expand...
Click to collapse
At this point I have a big problem with AOSP 10.0: brightness is blocked at 100%. There's a workaround involving adb, but for some reason adb isn't working with this firmware, even though I've activated developer options and USB debugging. I haven't had the time to tinker yet, I'll give it a try asap and I'll report back!
Thank you again for your help

Romano2K said:
Thank you for these clarifications
The **GREEN** or **ORANGE** overlay is shown for a few seconds on the vendor logo, before boot animation. It wasn't showing before I started messing with firmwares, but nevermind
Yes unfortunately HTC is kind of dead on the smartphone front. They deserved it at the end, U12 Plus' firmware is badly translated and full of bloatware. I've been a long fan, I've had four Orange branded Windows Mobile phones and PDA phones from 2002 (17 years ago!) to 2007, then a few Android smartphones (HTC Desire <3), so I think it's sad.
Anyway I've been able to flash AOSP 10.0 GSI by phhusson with his help.
So I've just shared a quick tutorial:
https://forum.xda-developers.com/u12-plus/how-to/guide-how-to-install-generic-image-gsi-t4019151
Thank you for your help Deonix!
Click to expand...
Click to collapse
Did Bluetooth work for you on AOSP? Tried to install a few GSIs over the last couple of days but I cannot get Bluetooth working for calls or media. Apparently it's a known issue but none of the fixes I can find here on the forums seem to work for me. Just wondered what your experience was on another U12. I even tried your guide but still no Bluetooth for me.

Useful post about the GREEN message.

Several Questions

I'm interested in building an updated, de-googled, de-bloated, ROM for a TCL A30 , model TCL5102D, mt6762/6765. First off was whether to post in tha Alcatel Section. My understanding is that Alcaltel is no more and those phones are now marketed as TCL. Prior Alcaltel posts may be helpful - perhaps the moderators could rename the section "Alcaltel/TCL" rather than adding a New TCL section.
I fouund mtkclient in the forum and it works on my device. I have not TWRP rooted it yet but have pulled boot.img, vbmeta.img and the entire system image. I have also found the TCL source code site, downloaded an earlier device with Mediatek Helio 22P chips and adb pulled /proc/config.gz. GPL source for my specific device has yet to be published by TCL.
I've yet to pull the vendor blobs and have only found guides in the Lineagos documentaion. It's pulling from a zip'd image rather than a device and TCL does not have images for any of their current phone. Also could not find a dump for this particular phone.
My first challenge is trying to build the kernel. The TCL source code, kernel 4.19.127, is not structured like the AOSP kernel source and aarch64, gcc builds hang up on the lcdscreen driver. The screen driver was backported in later 4.19.x versions which built with the config.gz and upstream kernel.org source.
What I'd like to do is to do is update the TCL source to the latest stable 4.19 code base but my web searches have not come up with any examples on how to do this. Could also build with the AOSP 4.19-stable source with the pulled config.gz - chances that it would work?
If I can prebuild the kernel, then make a decision in regards to a LineageOS build vs a GSI build. Maybe even build within GrapheneOS (uses prebuild kernels).
Where, in the forum, should I start the line of questions? Can anybody point me to a guide on howto build an kernel with an up-to-date source?

hi, your best place to go would be here and here

I have a TCL a30 android 11. I'm looking for any possible way to unlock the bootloader and install custom recovery. This all started with trying to use a visible sim card in the phone and me not being able to change the APN settings. I've been working on a way for a while now and have gotten absolutely nowhere. If anyone has any insight, it would be greatly appreciated.

danvep5014 said:
I have a TCL a30 android 11. I'm looking for any possible way to unlock the bootloader and install custom recovery. This all started with trying to use a visible sim card in the phone and me not being able to change the APN settings. I've been working on a way for a while now and have gotten absolutely nowhere. If anyone has any insight, it would be greatly appreciated.
Click to expand...
Click to collapse
TCL A509DL NO FASTBOOT-ABILITY??
Hey there guys and girls. I just bought a cheap TCL A509DL to experiment with and immediately hit a roadblock of megalithic proportions...no fastboot mode available on this cracker-jack prize equivalent phone. Seriously...no way to boot into...
forum.xda-developers.com

971shep said:
TCL A509DL NO FASTBOOT-ABILITY??
Hey there guys and girls. I just bought a cheap TCL A509DL to experiment with and immediately hit a roadblock of megalithic proportions...no fastboot mode available on this cracker-jack prize equivalent phone. Seriously...no way to boot into...
forum.xda-developers.com
Click to expand...
Click to collapse
I'm working on how to get the device to be recognized in mtkclient. Regardless of what button combination I use, the device fails to be recognized. Any specific way it needs to be done on the TCL A30?

I took the phone apart to look for some test points and I can't find any. Did anyone have success in getting this device to work with mtkclient? I've tried every button combination possible. If anyone has any insight it would be greatly appreciated. This is getting extremely frustrating. Been trying for the past week. Once I get passed that point we will be good to go but I'm at a wall right now.

danvep5014 said:
I took the phone apart to look for some test points and I can't find any. Did anyone have success in getting this device to work with mtkclient? I've tried every button combination possible. If anyone has any insight it would be greatly appreciated. This is getting extremely frustrating. Been trying for the past week. Once I get passed that point we will be good to go but I'm at a wall right now.
Click to expand...
Click to collapse
I start mtkclient with the phone connected via usb but powered off. Mtkclient messages that it is trying to establish a connection. Then just power up with the power key only. You should get messages that you connected in brom mode.

I was finally able to get it. Had to use adb reboot edl. Did the trick. Now I'm trying to build a rom with oxygen os but i keep getting stuck in a boot loop.

Boot loops can have many causes.. In the case of a custom rom, it is often that boot verification of the file systems fails, ie a file system checksum is different. In the thread I linked above, the way around this was to overwrite the three different vbmeta.* files with a blank file..