Related
THIS SOURCE WILL WORK ON ALL CURRENT HTC EVO'S!!!
i found the board files for the EVO a while back but wanted to wait til we at least had the release RUU to release it. now the actual kernel itself isnt a EVO kernel. its actually an Incredible kernel source with the EVO board files in it. that said i had to mod the board files a little to get it to compile. anyhow link below and remember to fork as it helps github and everyone. thanx
GoDmOdE-EVO
Commit log:
Sat May 22, 2010 - First-commit-0_o = first commit
Sat Jun 19, 2010 - Fix the wimax LED, capella prox sensor. Add epson panel support for supersonic
(panel_type=0), which is present on
hardware revision 3. Implement 9bit spi. - by Joe Hansche (maejrep)
Sun Jun 20, 2010 - Add some more epson vs novatec fixes - by Joe Hansche (maejrep)
Mon Jun 21, 2010 - Fix proximity sensor and Implement wimax LED control. These commits also fixed issues with all other sensors, and enabling them to all work!!! - by Joe Hansche (maejrep)
THIS IS A UPDATE.ZIP THAT CAN BE USED WITH FRESH ROM, TO BOOT THIS KERNEL WITHOUT WIPING. PLEEEEEESE DO A NANDROID BACKUP BEFORE FLASHING THIS UPDATE.ZIP. SO U CAN JUST NANDROID RESTORE UR DEVICE BACK TO NORMAL AFTER UR DONE PLAYING . ANYHOW CAMERA IS NOT WORKING AND THERE SEEM TO BE WHATS THOUGHT TO BE VSYNC ISSUES. ANYHOW ENJOY!!!
http://link.geekfor.me/godmodefreshhh
of course dont turn this thread into a this is broke can u please fix it thread.
IF U WOULD LIKE TO HELP OUT OR BUILD UR OWN KERNEL FROM THIS SOURCE, PLEASE FORK. THIS IS ADVISED BY GITHUB AND ALSO BY ME. AS IT MAKE PULLING CHANGES TO AND FROM BRANCHES MUCH EASIER. THIS IS A GOOD THING FOR U AND ME. IF I MAKE A COMMIT U WANNA ADD U CAN EASILY SYNC UP WITH ME AND VICE VERSA. WORKS OUT GREAT FOR EVERYONE AND KEEPS US COMPLETELY OPEN, AFTER ALL WERE ALL ON THE SAME TEAM.
ToAsTcFh For MOD!!!! This is genius
Im a little too buzzed atm. What exactly is this and what does it mean for us? explain and ill understand it in the A.M.
Trying to take over the Evo forums already Toast? ha ha Good to know we are going to have good devs on this board. Still running your kernel on my Hero. That is until my Evo arrives today and I start trying to root it
chuckhriczko said:
Trying to take over the Evo forums already Toast? ha ha Good to know we are going to have good devs on this board. Still running your kernel on my Hero. That is until my Evo arrives today and I start trying to root it
Click to expand...
Click to collapse
how're you getting your evo today??
so far i know a lot of good devs coming over. im pre-ordered so as soon as it shows up at best buy ill be struggling for root again.
justinisyoung said:
how're you getting your evo today??
Click to expand...
Click to collapse
Ebay? Craglist?
ppl from the google i/o event selling them
YoungAceAtlanta said:
Ebay? Craglist?
ppl from the google i/o event selling them
Click to expand...
Click to collapse
Yep. eBay. It's a Google I/O device. Paid a HEFTY premium for it but it's worth it to get it two weeks early for me.
toastcfh said:
so far i know a lot of good devs coming over. im pre-ordered so as soon as it shows up at best buy ill be struggling for root again.
Click to expand...
Click to collapse
Awesome. Who else that you know of? I know I stopped devving for the Hero but I can't wait to start devving for this thing. This community is going to be epic!
Right on toast, this is awesome.
fantastic toast
can this kernel be loaded onto one of the google I/O event EVOs to test?
The device isn't root yet
toastcfh said:
The device isn't root yet
Click to expand...
Click to collapse
now i see the catch 22...sorry im new to all this and dont have an EVO to experiment with...
could this kernel be combined with the standard ramdisk into a boot.img, packaged into a signed update.zip and installed through the stock recovery?
joeykrim said:
now i see the catch 22...sorry im new to all this and dont have an EVO to experiment with...
could this kernel be combined with the standard ramdisk into a boot.img, packaged into a signed update.zip and installed through the stock recovery?
Click to expand...
Click to collapse
No. You can't flash anything worthwhile until the phone is rooted. Once this happens expect this forum to explode.
No we need root and the ability. To flash a custom recovery. Basically. The catch 22 is we need root before we can do anything custom
By flashing an updated NBH, doesn't that overwrite both the Kernel and the OS on the NAND? If so, couldn't we replace the Kernel with one with root, and also provide for our own (AOSP, etc.) builds of Android?
Essentially, I'm wondering what the breakdown process is for recovery. The bootloader (Power + Volume on boot) is stored on the ROM, so regardless of "bricking" your device, you should always be able to get back to the bootloader to recover, correct?
If that's the case, what stops us from simply building an NBH with the current (locked) Kernel, but with modified system files for our own ROM?
Shidell said:
By flashing an updated NBH, doesn't that overwrite both the Kernel and the OS on the NAND? If so, couldn't we replace the Kernel with one with root, and also provide for our own (AOSP, etc.) builds of Android?
Essentially, I'm wondering what the breakdown process is for recovery. The bootloader (Power + Volume on boot) is stored on the ROM, so regardless of "bricking" your device, you should always be able to get back to the bootloader to recover, correct?
If that's the case, what stops us from simply building an NBH with the current (locked) Kernel, but with modified system files for our own ROM?
Click to expand...
Click to collapse
we're thinking alike here. some of this terminology is new to me and some isnt. hopefully this makes sense. im gonna reword but ask the same question as above (at least i think same question) plus another question. im doing a lot of research and tryin to word things correctly...
this might be the same question as above, are we able to trick the supersonic RUU released here into loading our own rom.zip file (NBH)? (we were able to do this with the samsung moment)
if not, are we able to use the fastboot-bootloader mode (samsung moment doesnt have this) to install a custom recovery? if so, we are then waiting on a custom recovery to be developed?
I think we are heading down the same path.
My understanding is that flashing a new "ROM" via NBH will replace both the Kernel and the OS (Android) files on the NAND, as both live there. The only item that lives in the ROM itself is the bootloader, which should always persist. With this understanding, even if you totally destroy your Kernel and/or Android OS, you should always be able to power the device to bootloader mode (Power + Volume) to flash (and therefore replace/restore) a new Kernel/OS to your phone.
If that's the case, then root access isn't necessary. All root access will allow us to do is some fancy side operations, like running a ROM (OS) manager inside Android--and who really wants to do that? Most of us want to be able to load a single custom build of Android, optimized and designed the way we want, right?
My thought process is this:
HTC should be releasing the EVO Kernel source on developer.htc.com by the official launch. With that, we can compile the Kernel ourselves (if we can't otherwise find it compiled) and theoretically bundle that with our own OS compilation of Android into a .NBH. This .NBH could then be flashed via the bootloader, replacing both the stock OS and the Kernel with what we've bundled.
This would seem to mean we wouldn't have root access, but we wouldn't need it, as we could simply update the OS files, build an .NBH, and provide it to users to flash. This could mean that custom distros would be a single contained file--one file to flash and that's it, you're updated.
Thoughts? Is this accurate?
If this is the case, we should start looking at the Kernel and the .NBH format rather than obtaining root, because once we understand the .NBH, we can load whatever we want (including a Kernel with root access, if desired.)
Shidell said:
I think we are heading down the same path.
My understanding is that flashing a new "ROM" via NBH will replace both the Kernel and the OS (Android) files on the NAND, as both live there. The only item that lives in the ROM itself is the bootloader, which should always persist. With this understanding, even if you totally destroy your Kernel and/or Android OS, you should always be able to power the device to bootloader mode (Power + Volume) to flash (and therefore replace/restore) a new Kernel/OS to your phone.
If that's the case, then root access isn't necessary. All root access will allow us to do is some fancy side operations, like running a ROM (OS) manager inside Android--and who really wants to do that? Most of us want to be able to load a single custom build of Android, optimized and designed the way we want, right?
My thought process is this:
HTC should be releasing the EVO Kernel source on developer.htc.com by the official launch. With that, we can compile the Kernel ourselves (if we can't otherwise find it compiled) and theoretically bundle that with our own OS compilation of Android into a .NBH. This .NBH could then be flashed via the bootloader, replacing both the stock OS and the Kernel with what we've bundled.
This would seem to mean we wouldn't have root access, but we wouldn't need it, as we could simply update the OS files, build an .NBH, and provide it to users to flash. This could mean that custom distros would be a single contained file--one file to flash and that's it, you're updated.
Thoughts? Is this accurate?
If this is the case, we should start looking at the Kernel and the .NBH format rather than obtaining root, because once we understand the .NBH, we can load whatever we want (including a Kernel with root access, if desired.)
Click to expand...
Click to collapse
ok.. the bootloader isnt gonna let us flash anything that isnt for the phone that ive heard of at least. the bootloader is only gonna let us flash rom.zips signed by htc unless we have a engineering spl. if we had that we could fastboot whatever we want. but it is also my understanding that the new engineering spls will not let us flash to certain major partitions (ie rocovery, and boot) anyhow this i think was an issue for the desire that modaco rooted and he found a way around it. we need a recovery for sure. as starting a new with no backups and such would be nothing more then a pain. we should focus i think on obtaining a engineering SPL from someone nice who wants to hook us up or a exploit of some sort. we need to gain read/write access to system, boot and recovery partitions. we do that and we can do what we want with the device. were not gonna be able to just flash a kernel, boot.img, system, or update.zip thats not official without the ability to gain access to the recovery partition.
in an exploit we would have root user status and we would have write perms on system at that point we could possible add flash_image to bin, chmod it and use that to flash a new recovery. write access is all we need. if ur idea was possible all we would need to do is flash a distro with root access and then flash the recovery partition with a custom recovery. a custome recovery will give us the ability to flash, backup and restore whatever we want. so long story short we need root user status in any event so we can gain access to recovery partition.
NOTICE: Sorry Guys, As i lost my defy, i will not be able to work for defy anymore So i will not be able to maintain this thread as well. Racca is maintaining another thread with updates for this bootmenu here which can now be called the official thread.
Hello XDA,
[Notice: You might have checked my signature and already figured out that i lost my Motorola Defy So i will be no longer able to develop anything for defy. I will not be able to edit the boot menu and optimize it, but i will still post all the updates i get from Korean Developers. I am sorry to say that i will not be able to work on porting MiUi to Defy anymore. I hope some other developer will handle the work and port MiUi to Defy. Just reply to this thread if you have anything. Thank You]
This is a pre-boot menu that loads just before the android system starts, which allows you to enter recovery, start adb daemon, run 2nd init script, run 2nd boot and few more. I recently changed the format of this post so that i can easily add updates, and i hope you guys don't mind it, and if you want to check the old post, here is the link. I have also added an unofficial changelog. This MOD was developed by Korean Developers at http://cafe.naver.com/androiders, so big thanks goes to them.
Status: Beta
Latest Version: v0.5.1
Last Update: 4/16/2011
Usage:
Load second init.rc file which enables you to do a lot of things that were not possible before.
Load custom recovery before booting os, which makes it possible to restore your nandroid backup or flash a new rom even if your system is not booting.
Run ADB Daemon to debug system boot using logcat or similar tools, very useful for developers.
Change the default boot to 2nd init, so you can load the 2nd init on default boot.
And much more....
Download:
Version 0.5.1 (Latest)
Version 0.5.0
Version 0.4.5
Version 0.3.1
Version 0.2.0
XDA-Developer Forum Members, Download Latest Attached File, Non-Members, Click Here.
Upgrading:
Simply follow the installation instructions, it will overwrite the old version and install the new one.
Installation:
Download the latest zip file.
Create a folder “bootmenu” on your sd card and extract all the files inside the zip file there.
Turn on usb debugging on your phone. And use the following commands in adb:
C:/> adb shell
$ su
# cp -R /sdcard/bootmenu /data/bootmenu
# cd /data/bootmenu
# chmod 755 *
# ./install.sh
# rm -R /data/bootmenu
Click to expand...
Click to collapse
The bootmenu will be installed.
Turn off USB Debugging.
Restart your device once.
Check the Using "Pre Boot Menu" section for instructions on how to use.
Using Pre Boot Menu:
Turn your phone off.
Press the Power Button.
After 1-10 seconds, the blue led on your phone will light up for just 1.5 seconds (Still while the Motorola logo is being displayed).
Exactly when the led lights up, press the volume down button.
You will see the BootMenu, use the Volume Button to navigate up and down, and the power button to select an item.
Changelog:
Version 0.5.1
Bug Fixes
Minor Internal Script Changes
Version 0.5.0
Bug Fixes
Few Changes In UI (Background)
Updated All Scripts, Better Compatibility With Most ROMS
Changed Directory Structure
Version 0.4.5
Bug Fixes
Changed Name Of OpenRecovery To Custom Recovery
ADB Daemon Works Now
Few Minor Changes...
Version 0.3.1
Replaced Tenfar's Recovery With OpenRecovery
Added 2nd Init Script
Bug Fixes
Minor UI Enhancements
Version 0.2.0
Initial Release
Added BootMenu
Added Tenfar's Recovery
What Works:
BootMeu
ADB Daemon
2nd Init
Custom Recovery
Default Recovery
Setting 2nd Init As Default
Reboot
Normal Boot
What Doesn't Work:
2nd Boot (Can Be Done Via 2nd Init Though)
Credits:
Korean Developer "ohnholic" and Other Korean Developers for creating this
Korean Forum User "intohim" for providing me this file and helping me translate Korean things to English.
Korean Forum User "고봉현" for mailing me about the updates as soon as they are released, and also for providing some files.
XDA Developer "tenfar" for his ClockWorkMod Port To Defy.
Developer "Koushik Dutta" for ClockWorkMod.
XDA User "pedrodh" for creating an easy installer.
And everyone i forgot to mention....
Related Projects:
Easy Installer (APK) for this MOD.
Cyanogenmod 7 Port Based On 2nd Init Using This MOD (Under Developement)
MiUi Port Based On 2nd Init Using This MOD (Under Developement)
P.S. I do not take any responsibilities for the damages caused by this tool. If you brick your device, the most i can do is *help* you recover your system. So use it on your own. Works on my phone.
This will be impressive when 2nd-init works.
Thanks for everyone working in things like that!!
P.S. It's working here!
does this mean custom kernels? once it gets figured out?
mussio said:
does this mean custom kernels? once it gets figured out?
Click to expand...
Click to collapse
Well, not right now, but once the korean developers figure out a way to bypass the recovery signature verification, which is of course, not easy, we will be able to do that too. And according to what i kknow, the korean devs are working really hard on that. But this definitely means that we are one step closer.
So for now this makes flashing Roms easier? safer? sorry if i seem confused i'm not getting my Defy till Monday just want to clarify if i should flash Roms this way or follow directions dor each rom, all this sbf files and being able to downgrade is kinda confusing I never had a android phone with a locked bootloader so all this is new to me.
hope that makes sense.
mussio said:
So for now this makes flashing Roms easier? safer? sorry if i seem confused i'm not getting my Defy till Monday just want to clarify if i should flash Roms this way or follow directions dor each rom, all this sbf files and being able to downgrade is kinda confusing I never had a android phone with a locked bootloader so all this is new to me.
hope that makes sense.
Click to expand...
Click to collapse
Well, this doesnt really make flashing roms easier (its same recovery), but it definitely makes it safer as you can always restore your nandroid or flash another rom even if your phone stops booting. And i can totally understand you, the way motorola works is a bit different than HTC and other phones, sbfs and stuff like that, but dont worry, if you read the guides here -> http://forum.xda-developers.com/showthread.php?t=919334 , you will understand everything. Enjoy
That are very great news!!
Does I have to install this after every new firmware-flash or only after a bootloader up/downgrade?
wow... great news..
now we don't have to boot up the phone, and install custom recovery.
saving time
Can't wait to see custom kernels
"intohim" what a great nick... hahahahahaha!
sorry, great news & big props to the korean devs!
That sounds pretty awesome, will try later. I would have saved a lot of hours with that... anyway, I'll save them by now
Sent from my Defy running adlxmod using Tapatalk
Oh, now disabling USB debugging is not required! Bravo!
I have not disabled USB debugging and I have M boot loop. Now reflashing to try again.
For everyone - do not forget to turn off usb debugging. Now it´s working and I am going to try it some more.
Edit: Finally the true, fully working recovery. With Tenfar´s recovery, this is the best developed thing for Defy, since Defy´s release
and it´s worth the donation. About only 5 minutes to recover bricked system.
I only hope some day adb will be working too, but this is great enough for now.
How can I get root-access after starting adb via the bootmenu?
Currently, it's not working for me:
$ su
[1] Segmentation fault su
Click to expand...
Click to collapse
Does this mod mean that Cyanogen is coming to Defy???
hirano said:
Does this mod mean that Cyanogen is coming to Defy???
Click to expand...
Click to collapse
Not yet. We need the 2nd-init working to do that.
antony.ps said:
Can't wait to see custom kernels
Click to expand...
Click to collapse
not possible unless someone can crack/get the lock
it's a great improvement but no where near custom kernels
afaik, this is another "bootstrap" executed on boot except it resumes normal boot after 2 seconds or so.
if we can get 2nd-init to work with it, we might finally be close to getting what milestone already have.
peetr_ said:
I have not disabled USB debugging and I have M boot loop. Now reflashing to try again.
For everyone - do not forget to turn off usb debugging. Now it´s working and I am going to try it some more.
Edit: Finally the true, fully working recovery. With Tenfar´s recovery, this is the best developed thing for Defy, since Defy´s release
and it´s worth the donation. About only 5 minutes to recover bricked system.
I only hope some day adb will be working too, but this is great enough for now.
Click to expand...
Click to collapse
Curious, just in case anyone has already tried and can give an answer: when installed, is outer persistent after you flash a sbf? Or is it overwritten by the sbf? Does anyone know? (i mean, afaik /pds isn't restored with sbf, mess with it and you get a brick! )
Sent from my Defy running adlxmod using Tapatalk
Any news from the Koreans who develop this recovery?
Sent from my MOTO Defy
demolition23 said:
Any news from the Koreans who develop this recovery?
Sent from my MOTO Defy
Click to expand...
Click to collapse
Nope, i have just emailed "intohim" and asked him to come online, as he is the only one who can read korean, and the korean page doesnt work here for some reason. I will update as soon as i get a reply
adlx.xda said:
Curious, just in case anyone has already tried and can give an answer: when installed, is outer persistent after you flash a sbf? Or is it overwritten by the sbf? Does anyone know? (i mean, afaik /pds isn't restored with sbf, mess with it and you get a brick! )
Sent from my Defy running adlxmod using Tapatalk
Click to expand...
Click to collapse
Sorry to say, but nope, this is not hardcoded in to rom or is not replaced in place of original recovery as the bootloader is still locked. And installing a sbf update is like replacing everything on the phone with the contents from sbf. So it wont work if you reflash the sbf, unless it is included in the mod or rom you installed. Some developers have just contacted me and said that they are going to include this on their rom. So future defy roms are going to be more safe
I hope there are some devs looking through this part of the forum.
This is NOT a request thread, I merely need some pointers as to questions I have about development so I can experiment on my own and hopefully attain results which are to some degree helpful to the community.
1) The sony stock firmwares come in these weird .sin formats, does this mean the device partitions work differently on Xperias than they do on other devices or does this stand in the way when reading general guides on e.g. cyanogenmod about flashing a certain partition?
2) The bootloader on this device acts differently than the one on my nexus 7, as in, in a weird way. I gather this is because sony made it themselves and to their liking to add flashmode.
2a) Is it normal that I can use fastboot to flash a kernel, but not use "fastboot boot boot.img" to boot e.g. extended stock temporarily? My device then hangs on the black-screen-blue-light standard fastboot look, but it doesn't power off when removing the USB cable and I have to pull out the battery. Flashing works though.
2b) Is "Flashmode" necessary for anything? Does it do anything else then allow for ftf's to be flashed, thus not having much to do with custom rom development?
2c) also, on original stock kernel, is it normal that the only way to get into recovery I have found up until now is using the Quickboot app? Using a recovery keycombo or trying from fastboot or adb does nothing, sometimes even hanging the device, so taking out the battery is necessary again...
3) How do you guys make booting images out of a compiled kernel? I can compile a kernel just fine, but I don't really figure what to do with the zImage file other than "packing it somehow". Been searching around on google for this, but I can't find any working ways to pack anything, and I don't even know where to get a ramdisk or how to make one.
4) On that note, I have been trying to figure out compiling CM, by forking some repos of taoshan and sony common, but I don't really know how for these are in correctness. Are there specific repos with the taoshan board configuration that are being worked on right now that I should/could fork to figure stuff out myself? I don't know how this forking is looked upon, if it is regarded as stealing someone's code or something, any insights about that might also be helpful.
That's what I can form off of the top of my head. I hope I get some insights from you guys at least. I have been trying and breaking my device for a week now, wishing to get something working of my own, but to no real avail
All the best.
MajorMonodon
MajorMonodon said:
I hope there are some devs looking through this part of the forum.
This is NOT a request thread, I merely need some pointers as to questions I have about development so I can experiment on my own and hopefully attain results which are to some degree helpful to the community.
1) The sony stock firmwares come in these weird .sin formats, does this mean the device partitions work differently on Xperias than they do on other devices or does this stand in the way when reading general guides on e.g. cyanogenmod about flashing a certain partition?
2) The bootloader on this device acts differently than the one on my nexus 7, as in, in a weird way. I gather this is because sony made it themselves and to their liking to add flashmode.
2a) Is it normal that I can use fastboot to flash a kernel, but not use "fastboot boot boot.img" to boot e.g. extended stock temporarily? My device then hangs on the black-screen-blue-light standard fastboot look, but it doesn't power off when removing the USB cable and I have to pull out the battery. Flashing works though.
2b) Is "Flashmode" necessary for anything? Does it do anything else then allow for ftf's to be flashed, thus not having much to do with custom rom development?
2c) also, on original stock kernel, is it normal that the only way to get into recovery I have found up until now is using the Quickboot app? Using a recovery keycombo or trying from fastboot or adb does nothing, sometimes even hanging the device, so taking out the battery is necessary again...
3) How do you guys make booting images out of a compiled kernel? I can compile a kernel just fine, but I don't really figure what to do with the zImage file other than "packing it somehow". Been searching around on google for this, but I can't find any working ways to pack anything, and I don't even know where to get a ramdisk or how to make one.
4) On that note, I have been trying to figure out compiling CM, by forking some repos of taoshan and sony common, but I don't really know how for these are in correctness. Are there specific repos with the taoshan board configuration that are being worked on right now that I should/could fork to figure stuff out myself? I don't know how this forking is looked upon, if it is regarded as stealing someone's code or something, any insights about that might also be helpful.
That's what I can form off of the top of my head. I hope I get some insights from you guys at least. I have been trying and breaking my device for a week now, wishing to get something working of my own, but to no real avail
All the best.
MajorMonodon
Click to expand...
Click to collapse
1) Not at all. Just extract .sin using flashtool and then mount the dumped .ext4 as a regular filesystem.
Xperia devices have all partitions except /recovery.
2) I can't answer your question because I didn't have any non Sony android device before.
2a) Sony bootloader doesn't allow hotbooting kernels.
2b) You can cherrypick components of firmware like baseband, kernel, system etc and flash through flashmode. Really handy!
2c) As I mentioned before, Xperia devices don't have /recovery. So any attempt to boot recovery partition is futile.
Another way round, is to load recovery.cpio as an initrd during boot by keymaps.
3) use mkbootimg. Check my git for more info.
Randisk can be obtained by extracting stock kernel.
4) maybe a cm developer can help you regarding this.
Rachit Rawat said:
1) Not at all. Just extract .sin using flashtool and then mount the dumped .ext4 as a regular filesystem.
Xperia devices have all partitions except /recovery.
2) I can't answer your question because I didn't have any non Sony android device before.
2a) Sony bootloader doesn't allow hotbooting kernels.
2b) You can cherrypick components of firmware like baseband, kernel, system etc and flash through flashmode. Really handy!
2c) As I mentioned before, Xperia devices don't have /recovery. So any attempt to boot recovery partition is futile.
Another way round, is to load recovery.cpio as an initrd during boot by keymaps.
3) use mkbootimg. Check my git for more info.
Randisk can be obtained by extracting stock kernel.
4) maybe a cm developer can help you regarding this.
Click to expand...
Click to collapse
Rachit,
Thanks a lot for the answers! This really gives me a boost, because sometimes when stuff doesn't work I'm ready to just give up!
I'll take a look at and fork your kernel repo if that is okay with you, to take a look at how you do things.
If I have an occasional question later on, would you mind me contacting you in some way, like pm?
Thanks again
(a very happy) MajorMonodon
MajorMonodon said:
Rachit,
Thanks a lot for the answers! This really gives me a boost, because sometimes when stuff doesn't work I'm ready to just give up!
I'll take a look at and fork your kernel repo if that is okay with you, to take a look at how you do things.
If I have an occasional question later on, would you mind me contacting you in some way, like pm?
Thanks again
(a very happy) MajorMonodon
Click to expand...
Click to collapse
Sure. You can do whatever you want with my sources.
Atm I think one is broken because I kinda messed it up while patching wcnss.
Better you start with stock and patch it with commits I've done. If you don't understand what the patch is all about, hit me anytime via pm. I don't browse forums frequently.
:thumbup:
Rachit Rawat said:
Sure. You can do whatever you want with my sources.
Atm I think one is broken because I kinda messed it up while patching wcnss.
Better you start with stock and patch it with commits I've done. If you don't understand what the patch is all about, hit me anytime via pm. I don't browse forums frequently.
:thumbup:
Click to expand...
Click to collapse
Thanks Rachit, I'll do that!
All the best
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
URGENT! I accidentally typed:
fastboot flash boot (recovery.img)
instead of:
flashboot flash recovery (recovery.img)
Help!
quick
I need a response
getting impatient now...
Still need a response. And if you are reading this, I may just need a system folder. But if it is included in the rom, then I'll have that.
Angry
for god's sake, this forum is dead. I can't rely on support because they are charging me, and no one on here is helpful nor willing to help out. No one hs even replied to this in ages and I am getting very impatient. XDA is dying.
bump
bump
mossy boy said:
URGENT! I accidentally typed:
fastboot flash boot (recovery.img)
instead of:
flashboot flash recovery (recovery.img)
Help!
Click to expand...
Click to collapse
Sorry to hear that no one replied to you.
Unfortunately, the rom development of the Kogan Agora 6 plus is all but dead. There is just not enough backing or public interest of custom ROMs in this device. I would suggest a to replace your device, this device is getting old anyway.
I can give you the Kerbal sources if you have the know-how to make your own recovery image.
Best wishes
Imlex
mossy boy said:
URGENT! I accidentally typed:
fastboot flash boot (recovery.img)
instead of:
flashboot flash recovery (recovery.img)
Help!
Click to expand...
Click to collapse
sorry for late response but this thread bumped up so i saw it...
anyway, you are in a tricky situation. I heard that you mfgr is resisting to release kernel sources so compiling won't work.
You can ask for a downloadable firmware update via email, this is option one.
You can ask another user of the identical phone to send you a backup of his boot partition (using dd command) but that requires root. This is option two.
And the third option is to force Kogan to comply to GPL and release kernel sources but i guess no one will care.
If you fail to do the above, then you're screwed.
On the other hand, you can act dumb and say that "it was updating and than this happened bla bla". Sometimes it works.
Bye
sorry for late response but this thread bumped up so i saw it...
anyway, you are in a tricky situation. I heard that you mfgr is resisting to release kernel sources so compiling won't work.
You can ask for a downloadable firmware update via email, this is option one.
You can ask another user of the identical phone to send you a backup of his boot partition (using dd command) but that requires root. This is option two.
And the third option is to force Kogan to comply to GPL and release kernel sources but i guess no one will care.
If you fail to do the above, then you're screwed.
On the other hand, you can act dumb and say that "it was updating and than this happened bla bla". Sometimes it works.
Bye
Click to expand...
Click to collapse
I have the link for the kernel source. I don;t knwo how to compile boot partitionas and al lthatt tho.
mossy boy said:
I have the link for the kernel source. I don;t knwo how to compile boot partitionas and al lthatt tho.
Click to expand...
Click to collapse
https://forum.xda-developers.com/an...erence-how-to-compile-android-kernel-t3627297
Here is the link for a tutorial. I would suggest installing ubuntu in a virtual machine. Search for the how-to.
i ave ubuntu on my machine. thank you for the info. however, i have one question. will this compile the boot partition?
mossy boy said:
i ave ubuntu on my machine. thank you for the info. however, i have one question. will this compile the boot partition?
Click to expand...
Click to collapse
Most tutorials will tell you how to prepare for compiling.
okay well i didnt get too far with compiling. does anyone HAVE a kogan agora 6 plus?