I've been researching methods to boot another linux kernel from the android bootloader by first booting into the bootloader and then using a command similar to what fastboot uses to boot a temporary zImage.
hxxp://groups.google.com/group/android-kernel/browse_thread/thread/71a7cb1c35933a21
NOTE: replace the xx with tt
From my thread on the android Linux kernel group, it seems I can find more information on the recovery program here.
1. What exactly is the recovery program?
2. How does it function?
3. where do I find modified code for it?
(PS: I had originally posted this on questions and answers but this forum is better suited)
Cheers,
Earlence
anyone have any ideas?
atleast where can I get information on what code is in the recovery partition and how was it replaced to unlock these types of phones?
Honestly it seems to be a one kernel only situation for these devices. I understand what you are referring to. Much like desktop systems where you have a distro of Linux installed and you can choose different kernels to boot with. Unfortunately I don't believe any device right now has a bootloader that is capable of having multiple kernels installed with the option to boot from each one. Unless GRUB or LILO make it on to our devices I don't see this happening anytime in the near future.
Hi Folks,
I already spent some years in customizing Linux kernels and in the last time I was already playing around with Android devices and the possibility they offer to boot customized kernel. Now, thanks to NoThrill, we have a working CWM and my interest rises again. I already compiled the Acer Kernel Sources but I got into trouble booting it. Few months ago, I did the same with a lenovo IdeaPad a1 and it should be possible on the A510 too to boot an outside kernel using the command fastboot boot kernel ramdisk.gz. Problem is, that it does download and boot the kernel - but then it returns to fastboot mode instead of booting android. First I thought, it may be due to kernel errors but it does the same if I am using the stock kernel or the boot.img provided by working ROMs. So my questions are:
Is there any possibility to test an experimental kernel without flashing it first? Do I understand correctly, that it is relatively safe to flash it to the boot partition as long as recovery keeps untouched?
What exactly does the (unexplained) command fastboot continue? I thought it may be used to continue booting process with a downloaded kernel, but unfortunately it seems like it does just the same like a normal reboot ...
Simply pack the kernel into a boot.img and flash it to the /boot partition. If something goes wrong, simply reboot into recovery and flash your original boot.img back. Recovery will always work because it uses its own kernel and therefor is independent of whatever kernel you flash to /boot.
A word of warning though: The Acer kernelsource contains code that could brick your tablet. That needs to be fixed before you experiment any further.
Nevertheless, any work done on the A510 kernel is always encouraged :good:
NoThrills said:
Simply pack the kernel into a boot.img and flash it to the /boot partition. If something goes wrong, simply reboot into recovery and flash your original boot.img back. Recovery will always work because it uses its own kernel and therefor is independent of whatever kernel you flash to /boot.
A word of warning though: The Acer kernelsource contains code that could brick your tablet. That needs to be fixed before you experiment any further.
Nevertheless, any work done on the A510 kernel is always encouraged :good:
Click to expand...
Click to collapse
by the way, nothrills, did you set-up a git or something like that to share kernel mods and stuff like that ?
BENETNATH said:
by the way, nothrills, did you set-up a git or something like that to share kernel mods and stuff like that ?
Click to expand...
Click to collapse
Actually, no, because (call me stupid) I really have no clue how git works. I know how to get stuff from it, and used it alot, but never looked into actually setting something up or submitting patches.
I am very ashamed
NoThrills said:
Actually, no, because (call me stupid) I really have no clue how git works. I know how to get stuff from it, and used it alot, but never looked into actually setting something up or submitting patches.
I am very ashamed
Click to expand...
Click to collapse
THAT is something really easy you know..
but if it's something that you agree, i can upload it to my git if you don't want to use time for that.
i can clearly state about the source and then.. work can be shared and commit done.
otherwise, yu have to set-up a free account and follow this :
https://help.github.com/articles/create-a-repo
it would REALLY help you know
Pretty tricky to find anything for this tablet, but I managed to find a way to get an official image.
What you need:
Alcatel Mobile Upgrade Q 5.1.7 (or newer), get it here.
This will overwrite all your data on the device.
1. Install Mobile Upgrade Q
2. Run "C:\Program Files (x86)\Mobile Upgrade Q\tool\usb_driver\installdriver\DriverInstaller.exe" to install the USB Drivers.
3. Enable USB Debugging
4. adb reboot edl
5. Mobile Upgrade Q and select "VF1400" (note it also lists 9030G and 9030Q, the unbranded variants of this tablet (yet unreleased?), but unfortunately you can't flash these, it will just download the Vodafone branded image)
6. It will download the image files into "C:\Program Files (x86)\Mobile Upgrade Q\bin\download" (note while it's downloading the image files, these are just filled with 0s)
7. After it downloaded the image it starts flashing ("initialisation") and you can copy the files to some place safe (from bin\VF1400-2AVDXXX), it deletes some after it's done
B1BEB0B0CD00.mbn is the boot image, R1BEB0B0CD00.mbn the recovery. Some of the files have partition information, probably can use these to flash with QPST.
Going to have a look into compiling a TWRP, now that I have the kernel
Also, Alcatel seems to have released a *very incomplete* kernel source (build scripts and other things missing) over at https://sourceforge.net/projects/alcatel/files/, see OT_VDF_1400_20160520.tar.xz.
A bummer since the kernel in the official image seems to have all kinds of debugging stuff enabled.
Some more findings. You can coax SUGAR QCT_SP (and maybe Alcatel Mobile Upgrade Q 5.1.7?) into flashing any images.
Before starting SUGAR QCT_SP, copy your backup of the VF1400-2AVDDE1 folder into bin/. It should flash these files.
I flashed a ported recovery, but I couldn't boot it (always boots stock recovery). I guess because of secure boot? Read something about the recovery-from-boot.p file...
Don't worry about bricking, you can get the tab into edl mode with an edl cable. http://xiaomitips.com/guide/miui-deep-flash-engineering-cable-solution-to-non-edl-device/
Some progress, if anyone cares :laugh: (doubt it).
Flashed boot with altered build.pros, selinux is off, but adb root kills the adbd.
Same on recovery, but kind of pointless with zip verification. Now it's either compile a recovery or add a custom key too boot and sign the supersu zip myself.
Also flashed a slimmer system, minus all the google apps I don't use anyway. Stock image carries 1GB of empty space that is being flashed every time
One more interesting thing: You can get into fastboot by flashing a recovery with the wrong kernel and then booting to recovery. Fastboot is crippled though and does nothing useful, can't even flash with it.
Btw to turn off the device if you are stuck in a bootloop to recovery: With usb cable unconnected, hold Power and Volume down. It screen goes black after 5 sec, keep holding the buttons. It should come up again and very shortly after, let go of the buttons screen when the screen goes black a second time.
So, at the moment there is no way to root?
Geeting the device tomrrow
Yes there is. After getting rid of selinux, you can get temporary root using dirty cow, or bake supersu into the boot or system image.
Also I'm working on porting a recovery. It works, more or less already.
I just flashed SuperSU via the recovery I ported. Seems to work
Nice! Is it possible to Upload your Recovery? Simply flash via Fastboot?
gella1992 said:
Nice! Is it possible to Upload your Recovery? Simply flash via Fastboot?
Click to expand...
Click to collapse
I can upload it later.
Fastboot is crippled and you can't boot into it directly, at least on mine. Try booting into it (hold power + vol down). Otherwise see my earlier posts on how to do the initial flash. A little inconvenient, but it's only once
Will post detailed instructions with the recovery.
gella1992 said:
Nice! Is it possible to Upload your Recovery? Simply flash via Fastboot?
Click to expand...
Click to collapse
https://forum.xda-developers.com/android/development/recovery-vodafone-prime-tab-7-t3548560
Working on a frankenkernel with some salvaged parts from the incomplete kernel source from alcatel: https://github.com/852Kerfunkle/android_kernel_vodafone_vfd1400
Works for booting into recovery.
While trying some things with caf android builds, I flashed aboot, thinking I could always get back into download mode with the makeshift EDL cable. Turns out you can't.
Do not mess with aboot unless you are 100% sure (unlike me). The device will only register as HS-USB Diagnostic 900E. Even with an EDL cable.
For anyone who did: your device is not dead, but it's a bit of a mission.
1. Take of the back cover: Remove the screw behind the sim/sd latch and open the device with one of these plastic opener thingies, start at the latch.
2. Bridge the pin marked on the image (take a cable and connect the pin to the ground of the usb connector, i.e. the metal bit).
3. Plug in the usb cable.
4. It should register as HS-USB QDloader 9008 (assuming you have the right drivers).
5. Flash with Sugar.
Hopefully everything is working great again!
Do you think it would be possible to port a Lineage OS to this Tab?
I know how to compile from source, but actually not developing a Rom
gella1992 said:
Hopefully everything is working great again!
Do you think it would be possible to port a Lineage OS to this Tab?
I know how to compile from source, but actually not developing a Rom
Click to expand...
Click to collapse
Yeah it's working alright again, thanks
I tried, no luck yet. Am stuck on a crash in libsdm. Once I had it boot to the point where it was initialising the apps (dexopt or whatever?), but it crashed right after.
For now I am focusing on codeaurora android. If I get that working, maybe the caf parts can be used to make a working LineageOS build.
I also have little to no idea how to do anything android related, so most of the time is spent reading and googling silly errors. Just give it a go, if you get stuck I can help out with what I found so far.
At the moment I am busy. Will give it a try when I have more time :fingers-crossed:
fused#1 said:
Working on a frankenkernel with some salvaged parts from the incomplete kernel source from alcatel:
Works for booting into recovery.
Click to expand...
Click to collapse
Are you still working on this ?
I'm currently considering the option of running a git diff against the CAF msm-3.18 "LA.UM.5.1-03210-8x37.0" TAG/branch, which the released incomplete kernel source appears to be based on.
Then going through the patches and applying them one by one on the newest CAF 8937 TAG/branch.
Although getting LA.UM.5.1-03210-8x37.0 to work with the patches applied would be nice already.
My ultimate goal is OMNI, im not interested in CM/Lineage.
Problem is at the moment i don't have much time for this.
But we'll see :good:
nevexc said:
Are you still working on this ?
I'm currently considering the option of running a git diff against the CAF msm-3.18 "LA.UM.5.1-03210-8x37.0" TAG/branch, which the released incomplete kernel source appears to be based on.
Then going through the patches and applying them one by one on the newest CAF 8937 TAG/branch.
Although getting LA.UM.5.1-03210-8x37.0 to work with the patches applied would be nice already.
My ultimate goal is OMNI, im not interested in CM/Lineage.
Problem is at the moment i don't have much time for this.
But we'll see :good:
Click to expand...
Click to collapse
Hey,
That's pretty much what I was doing before I got caught up in other stuff
Was stuck at trying to figure out how to actually build caf android. Which of the files on the rom belong the the proprietary blobs and how to properly include them in the makefiles so it actually builds...
Hit me up with a PM, maybe we can coordinate our efforts :fingers-crossed:
Thanks for this Guide, but I have a quick question:
I am currently trying to restore my VF-1497 to a stock rom with Mobile Upgrade Q 5.1.7, but the Upgrader always kicks my Tablet out of edl, and throws the error:
'There is no greater version available to upgrade your phone, actual version of your phone is the latest'
Is there any way to restore this device back to stock?
Thank you in advance
ASP
Hi is there a custom "clean" firmware for vdf1400 that can go instead of the latest 6.0.1 150fkg1
Hello, I just got a new phone. It's probably my first actual phone in many years, as I'm mostly a PC kind of guy. I have been having trouble getting it booted for a while now. Someone informed me that it might be an Axia phone from AT&T, but I don't know the validity of that. It says Q-Innovations every time I use it on Google stuff. Does anyone here know of the phone or know how to boot one?
Thanks a lot in advance!
CamShirayuki said:
Hello, I just got a new phone. It's probably my first actual phone in many years, as I'm mostly a PC kind of guy. I have been having trouble getting it booted for a while now. Someone informed me that it might be an Axia phone from AT&T, but I don't know the validity of that. It says Q-Innovations every time I use it on Google stuff. Does anyone here know of the phone or know how to boot one?
Thanks a lot in advance!
Click to expand...
Click to collapse
The model number seems to be the AT&T version of that phone.
When you say that you can't get it booted, what do you mean exactly? What is the device doing when you try to boot it?
Have you tried holding volume up+power(let go when you see the splash screen) to boot into recovery, then factory reset and wipe cache partition?
Some devices have to hold volume down+power, then at the bootloader menu, choose the recovery option.
Sent from my LGL84VL using Tapatalk
What do you mean? I didn't think it was that easy to boot a phone? I wanted to put Linux on my phone instead of the current android version or even put them both on there.
CamShirayuki said:
What do you mean? I didn't think it was that easy to boot a phone? I wanted to put Linux on my phone instead of the current android version or even put them both on there.
Click to expand...
Click to collapse
I think you need to do some research to get familiar with how android devices actually work. Android devices are not like PC, you can't just install whatever OS you want, android devices are not "generic" like that. Operating systems for android devices have to be built specifically based on the hardware in the device, down to the kernel level, the kernel has to be specific to the device. You need to do some reading about how android stock recovery and custom recovery actually work , you also need to research how android stock firmware and custom operating systems are flashed on android devices.
It is "possible" to remove android and install Linux on an android device, but only certain devices can do it, depending on the security built-in to the bootloader that is installed on the device. There isn't a universal way to install Linux on android.
It is also possible to install Linux on top of android in a sort of emulator/VM then use a VNC to .
There are some apps to install linux on top of android, such as:
1) Linux Deploy
2) Complete Linux installer
3) UserLAnd
I installed and tested UserLAnd last night. Try this and see what you think.
https://github.com/CypherpunkArmory/UserLAnd
View the README.md for instuctions to set it up.
Sent from my LGL84VL using Tapatalk
Hello I'm a student here for learning purpose. I've been messing around with custom ROM for over 3 years now and came across GrapheneOS and I liked it on my Pixel 4a due to its secureboot feature and others. So my question is can how can I use a custom boot amination in it? Since its non rooted and everything. Can it be done if so It would be a great help since I would like to use my own logo as I'm a game developer and I would like it very much. I've tried using flashing commands, tried changing it from file manager(not happening since dont have root access), magisk not working, twrp cant flash it. Is there any other way to do it? Thank you in advance.
Changing Android's boot animation always requires phone's Android got rooted.
More info here:
How To Change Boot Logo (Splash Screen) for Android Smartphones - AndroidFist
Splash Screen or Boot Logo on Android smartphone is crucial. But in case you are bored with the same old image, you can change it and here's how to do it.
androidfist.com
jwoegerbauer said:
Changing Android's boot animation always requires phone's Android got rooted.
More info here:
How To Change Boot Logo (Splash Screen) for Android Smartphones - AndroidFist
Splash Screen or Boot Logo on Android smartphone is crucial. But in case you are bored with the same old image, you can change it and here's how to do it.
androidfist.com
Click to expand...
Click to collapse
Yes I gathered that. So is there there a way to root this ROM. I also found a rooted version of GraphOS but the link is no longer supported. Another question... Can I change another Custom rom to secure boot... like LineageOS suppose, after I change the Logo? Revoke all access like similar to graphOS lets say.
jwoegerbauer said:
Changing Android's boot animation always requires phone's Android got rooted.
More info here:
How To Change Boot Logo (Splash Screen) for Android Smartphones - AndroidFist
Splash Screen or Boot Logo on Android smartphone is crucial. But in case you are bored with the same old image, you can change it and here's how to do it.
androidfist.com
Click to expand...
Click to collapse
Hello I found the source code on GitHub:
GitHub - GrapheneOS/device_google_sunfish: Pixel 4a device sources.
Pixel 4a device sources. Contribute to GrapheneOS/device_google_sunfish development by creating an account on GitHub.
github.com
I don't need step by step explanation can just redirect me to the correct thread where I can find how to change the boot image and compile it successfully. Thank you.