Hello people,
This is my first post here, so I hope I am putting this in the right place. If not, sorry, please move it.
Anyway, as you all are aware, ICS source code was released a couple days ago, so I decided that I would see if I could begin constructing a ROM based off AOSP for the G2x.
As predicted, it did not go well. I pulled the build makefiles and the like from CyanogenMod (hope that's okay), and tried to use those as device-specific build instructions. I got everything to compile with no errors, and the ROM successfully installed, but does not boot.
Best I can tell, the phone gets through the kernel boot alright, but halts at the "A N D R O I D" screen (no boot animation file is included). The touch panel seems to be responsive.
Does anyone have any suggestions as to what might be wrong? Any help is greatly appreciated.
nerdman said:
Hello people,
This is my first post here, so I hope I am putting this in the right place. If not, sorry, please move it.
Anyway, as you all are aware, ICS source code was released a couple days ago, so I decided that I would see if I could begin constructing a ROM based off AOSP for the G2x.
As predicted, it did not go well. I pulled the build makefiles and the like from CyanogenMod (hope that's okay), and tried to use those as device-specific build instructions. I got everything to compile with no errors, and the ROM successfully installed, but does not boot.
Best I can tell, the phone gets through the kernel boot alright, but halts at the "A N D R O I D" screen (no boot animation file is included). The touch panel seems to be responsive.
Does anyone have any suggestions as to what might be wrong? Any help is greatly appreciated.
Click to expand...
Click to collapse
I think there were two other devs in this thread trying to get ICS up and running as well. They could probably help.
http://forum.xda-developers.com/showthread.php?t=1309620&page=3
Thanks for the link. I am working on changing the init.rc as per one particular post. I'll see if that works.
nerdman said:
Thanks for the link. I am working on changing the init.rc as per one particular post. I'll see if that works.
Click to expand...
Click to collapse
We have 3 people working on it... your assistance would be of great help
Okay, so I tested the idea of changing the bootclasspath in init.rc, and it didn't seem to be helping much. In fact, it may have hindered things. Before the modifications, the phone would finish going through the two lg splash screens. Now, it hangs on the second. Suspect bad merge of ramdisk and kernel. But as for now, sleep is calling. I will work on it more tomorrow.
And I'm glad I can be of help. If you would like, I could throw what I have on megaupload, see if what I have is valuable.
You don't have ICS built device drivers and the kernel needs to be built for ICS. If you do not get it to boot nothing will work except maybe the touchscreen if you are lucky.
Right. Device drivers. But we were able to port Gingerbread to this device with Froyo drivers, yes? What about compiling the ICS kernel source (if it is out) for the G2x. Would that yield any kind of results?
nerdman said:
Right. Device drivers. But we were able to port Gingerbread to this device with Froyo drivers, yes? What about compiling the ICS kernel source (if it is out) for the G2x. Would that yield any kind of results?
Click to expand...
Click to collapse
This is sounding a lot like the Hackintosh driver hacks, which I've done, to get the Mac OS to run on PC hardware of various kinds. In that world, drivers from previous iterations and versions of the Mac OS are merged into the Mac OS to enable various PC hardware which Apple didn't support in the new OS version. One example is the video drivers which Apple supplies for very few video cards but have been hacked to run other, non-supported video cards. As well, Apple is notorious because it orphans perfectly useable and upgradeable Apple Mac hardware by not providing video drivers for it in new releases of the Mac OS. When Mac OS 10.7 was released some people used the Mac OS 10.6 hacked and/or unhacked video drivers and hacked video drivers for OS 10.7 to keep their PC display hardware working. Keep trying.
Got the kernel source. I'll start messing around with it today.
Related
Project Description
This is a project to port the Droid version of CyanogenMod to the milestone. While the Droid and Milestone devices are twins, they are CDMA and GSM respectively. Hacks include not flashing the boot image provided by the CM Droid package and some GSM configurations.
Status
CyanogenMod 6 RC1 (with CoburnROM hacks) will flash successfully, however it will refuse to boot (possibly due to incompatible stock kernel or that the milestone doesn't like unsigned ROMs). So far, flashing works from koush's ClockWorkMod Recovery and Open Recovery 1.14. When rebooted, the device hangs on the M Boot logo.
Downloads
PoC/RC #1: Download from my blog, Geek In The Family - 75MB.
What you can do
Pretty much this ROM is currently a playground, if you want to have a poke around, download a copy of the above versions of the ROM and extract it, and then poke around and see what makes it tick.
Other notes
Space saved for future use.
Cheers!
Reserved for future use
Sent from my Milestone using XDA App
Good luck man, I really hope this happens
You should check with the guys on and-developers.com, and their IRC channel #milestone-modding on Freenode for any progress on the bootloader
Hacking the bootloader is impossibile on our Milestone, the TI OMAP chipset runs in High Security mode and for switching to General Purpose mode you have to desolder and resolder the OMAP chipset on your mainboard, soldering the right pins for enabling the GP mode.
Anyway, 2ndboot can make us able to boot a different kernel (for now GSM modem is unusable, so we can't use the phone with the new?y booted kernel) and this is the way that we'll take on the Milestone for using a custom kernel.
No custom ROMs. Or at least not this way.
We'll NEVER be able to boot this ROM.
Sent from my Milestone using Tapatalk
kholk said:
No custom ROMs. Or at least not this way.
We'll NEVER be able to boot this ROM.
Click to expand...
Click to collapse
My my, that's negative. I do know about the custom kernel via kexec/2ndboot trick.
Nothing is impossible to be hacked, it's a matter of time and blood, sweat and tears. As Paul from MoDaCo stated, nothing is impenetrable.
I'll get this ROM booting, even if I have to wait a year or two before the Boot loader is hacked or a proper method is working.
Good luck to you. I commend you for your efforts.
After 1 year waiting for the bootloader to be hacked...I am slightly skeptical. However, now that the Droid X has been released to the masses with the same locked bootloader, we might get some fresh eyes to look into this matter.
I would be happy enough with a custom kernel running on 2nd boot ;-)
SenseUI Mod
Hello, You might try using the mot_boot_mode file, which is also used with the SenseUI Port for the Milestone, I guess that would make this boot too? If I'm right, this is the boot sequence:
This is what I'm talking about:
"the ramdisk is located in /system/ramdisk.tar folder, it all starts here.
the ramdisk is opened by /system/bin/mot_boot_mode."
You should download the SenseUI Mod and analyse it's way of booting.
Good luck!
Coburn64 said:
My my, that's negative. I do know about the custom kernel via kexec/2ndboot trick.
Nothing is impossible to be hacked, it's a matter of time and blood, sweat and tears. As Paul from MoDaCo stated, nothing is impenetrable.
I'll get this ROM booting, even if I have to wait a year or two before the Boot loader is hacked or a proper method is working.
Click to expand...
Click to collapse
the problem is not about being negative but you are facing it the wrong way .
the problem here is to hack the thing not to port an already existing mod .
Once the bootloader is bypassed they ll be hundreds of real ROMS .
Anybody can pretend at porting there own roms it is completely IRRELEVANT since it wont be possible until its hacked.
you said it 'even if I have to wait ' well there you go do like thousands of others and just wait . BUt please dont pretend at anything else , thank you .
I am actually porting the ROM to the Milestone, in case if you're concerned that I'm lying. Check my twitter for progress reports.
@Mikevhl we may have a hope if we try that! Thanks for the recommendation!
Also, kexec is working. However, instead of rebooting Android with the Droid CM6 Kernel, it just reboots the phone instead. I'm working on a possible fix for that, thank Kiljacken for compiling the kexec module.
So you're not going with that 2ndboot method?
In any case, my eyes are glued to your twitter account
Coburn64 said:
I am actually porting the ROM to the Milestone, in case if you're concerned that I'm lying. Check my twitter for progress reports.
@Mikevhl we may have a hope if we try that! Thanks for the recommendation!
Also, kexec is working. However, instead of rebooting Android with the Droid CM6 Kernel, it just reboots the phone instead. I'm working on a possible fix for that, thank Kiljacken for compiling the kexec module.
Click to expand...
Click to collapse
dude your my hero
It's kinda off-topic, but I just thought, why don't we go 4chan style on Motorola, and, for example, black fax local Motorola offices or something?
Coburn64 said:
My my, that's negative. I do know about the custom kernel via kexec/2ndboot trick.
Nothing is impossible to be hacked, it's a matter of time and blood, sweat and tears. As Paul from MoDaCo stated, nothing is impenetrable.
I'll get this ROM booting, even if I have to wait a year or two before the Boot loader is hacked or a proper method is working.
Click to expand...
Click to collapse
As I said, it IS possible to skip the BL checks, and it's fully hackable...but...I know.... you don't want to resolder your OMAP....
if this mod is "Droid" based, you need to make many modifications to the startup..
the Droid is in no way protected, where Milestone has GSM radio protected, and specific drivers required to open it, which for now only opens when using the original "init" process of a milestone.. the "init" from droid disables radio completely..
but take a look on how i got the senseui port running.. i got the froyo partly running the same way, so im sure my solution used in senseui mod will help you along to make it work...it just requires some debugging and "adb logcat" so you at least can see what happens at startup..
why not work together dexter? i think this may help out in particular cases
Dexter_nlb said:
if this mod is "Droid" based, you need to make many modifications to the startup..
the Droid is in no way protected, where Milestone has GSM radio protected, and specific drivers required to open it, which for now only opens when using the original "init" process of a milestone.. the "init" from droid disables radio completely..
but take a look on how i got the senseui port running.. i got the froyo partly running the same way, so im sure my solution used in senseui mod will help you along to make it work...it just requires some debugging and "adb logcat" so you at least can see what happens at startup..
Click to expand...
Click to collapse
DO YOU HAVE FroYo running!?!?!?!??!?!?!?!?
Coburn64 said:
I am actually porting the ROM to the Milestone, in case if you're concerned that I'm lying. Check my twitter for progress reports.
@Mikevhl we may have a hope if we try that! Thanks for the recommendation!
Also, kexec is working. However, instead of rebooting Android with the Droid CM6 Kernel, it just reboots the phone instead. I'm working on a possible fix for that, thank Kiljacken for compiling the kexec module.
Click to expand...
Click to collapse
I never said you were lying all I said was dont pretend ' about rom ' when even a basic kernel wont run .
if you have a workin kexec would you mind sharing it ?
I'm very interested in your work since it seems that we will never see an official 2.2 from Motorola... I don't know if we are going to have the new update, here in France (2.1 update 2).
Well, I just have a question. On a french forum, someone posted a method to downgrade the ROM of the Milestone by implementing the right version of the bootloader in it, I don't know if I very clear. This member had some major problems with the 2.1 update so he decided to downgrade to 2.0.1. However he wasn't able to do it because his Milestone was using the 90.78 bootloader while the 2.0.1 rom was using the 90.73 bootloader. Eventulally, he managed to install the 2.0.1 rom on his Milestone by putting the 90.78 bootloader in the 2.0.1 rom.
So my question is : will it be possible put a bootloader in a custom rom in order to make it boot on the Milestone ?
(I would give you the link for the topic on the french forum once my account si verified)
kholk said:
Hacking the bootloader is impossibile on our Milestone, the TI OMAP chipset runs in High Security mode and for switching to General Purpose mode you have to desolder and resolder the OMAP chipset on your mainboard, soldering the right pins for enabling the GP mode.
Anyway, 2ndboot can make us able to boot a different kernel (for now GSM modem is unusable, so we can't use the phone with the new?y booted kernel) and this is the way that we'll take on the Milestone for using a custom kernel.
No custom ROMs. Or at least not this way.
We'll NEVER be able to boot this ROM.
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
Actually this is a wrong assumption. HS chip cannot be turned to a Generag purpose.
For those who are interested, here is kexec.
Devs should know the drill, insmod kexec.ko etc etc.
Originally made by Kiljacken (compilation, etc), shared by me.
As for the Android 2.0.1 on Boot Loader 97.73, he may have just made a custom update zip that nukes the system partition and installs 2.0.1 on the device.
Also, I updated my Boot Loader to 90.78ch, which is the XT702 Boot Loader - no bricks. Yet.
I was wondering why we've never seen a TWRP build from TeamWin for the TF101. I remember when the tablet came out that a few team members had the device and there was talk of builds upcoming for our device. Then there was the long break and TWRP2 and everything that happened at TeamWin, finally with 2.1 builds showing up. But there was nothing for our device, while the TF201 and TF301 were getting love.
I pinged dees_troy on twitter and found out some interesting info:
The Recovery Partition is only 5MB on the TF101
The Kernel needs to be less than 3MB to leave enough room for TWRP, meaning a custom recovery kernel.
Without a device in a devs hands, we'll not see TWRP
https://twitter.com/Dees_Troy/status/216631211366424576
https://twitter.com/Dees_Troy/status/216631556863836160
If I didn't rely on mine daily, I'd send it over for some builds, but that is not feasible for me.
Maybe we can get a developer to notice and build this, because I'd love to see a refined touch recovery like TWRP. I mean with the kernel though, how big is it with a stripped down version of it?
Darn shame about the partition sizes, those can be moved around.. but that's not a really great fix. I'd compile it and do a tad of bug-fixing since it should be the same process, but I really don't want to mess with partition sizing being too small and stripping recovery down. X.x
I've asked before and pm'ed about being a tester, and if it happens I'll be on top of it!
See, that's one thing Moto did good with their phones. I would have no issues with partitioning being similar, but I think they did go a little over board on what the system got versus what the consumer should be able to use for storage, IMO.
If there was a guide and I knew I could do it without creating to much headache trying to get it right, then I'd start on a similar project. My biggest problem is, I don't know very much about this at all. The last time I did any programming, I was in highschool and was learning C++ and did some PHP coding, but that doesn't apply here. HaHa.
TWRP has a step by step compile from source linux guide
Just the partitioning, I think it would work straight from source pretty well, but considering that the partition is too small that's where it gets tricky
Thing O Doom said:
TWRP has a step by step compile from source linux guide
Just the partitioning, I think it would work straight from source pretty well, but considering that the partition is too small that's where it gets tricky
Click to expand...
Click to collapse
just build it and see what the size is then we might be able to engage one of the kernel devs to help strip stuff out
Sent from my CM9 Transformer TF101 using Forum Runner
Alright, I'll compile from source and see what I can do. Give me a while though, because I'm upgrading my computer.
Sent from my TF101
Thing O Doom said:
Alright, I'll compile from source and see what I can do. Give me a while though, because I'm upgrading my computer.
Sent from my TF101
Click to expand...
Click to collapse
just checking in, any progress?
Sent from my CM9 Epic 4g Touch using Forum Runner
I'll admit I've been lax so far, it is on my list, but I'm so close to finishing APK peri >.< I just wanna get that done first.
Thing O Doom said:
I'll admit I've been lax so far, it is on my list, but I'm so close to finishing APK peri >.< I just wanna get that done first.
Click to expand...
Click to collapse
no worries, appreciate the effort
Im also eagerly awaiting any news on this... Im stuck on Rogue recovery because all the other versions dont use the MicroSD card, only the internal memory
Can someone post where I can find the partition layout/structure/description? (or PM it to me, that woul work as well)
Thing O Doom said:
I'll admit I've been lax so far, it is on my list, but I'm so close to finishing APK peri >.< I just wanna get that done first.
Click to expand...
Click to collapse
Hammerfest said:
Im also eagerly awaiting any news on this... Im stuck on Rogue recovery because all the other versions dont use the MicroSD card, only the internal memory
Can someone post where I can find the partition layout/structure/description? (or PM it to me, that woul work as well)
Click to expand...
Click to collapse
Looks like rayman has taken the reins on this one. There is a thread in dev for a WIP TWRP recovery
Yep he mentioned it and took over, which is great! Works decently well.
Hi,
I have a very basic question with regards to Android OS. Why can't we easily update the Android OS to newest version; just like we do it for say a Windows PC? I understand that there are hardware limitations for OS updates.. similar to say for example Win7 not supporting older hardware. But if want to update to the newest android version for my phone.. why are there "custom ROMs" posted in forums? What are the contents that go in these Custom ROM? I am interested in the programming part of this.
Also, second question is where do I get the say for example Jelly Bean ROM that I modify to suit for my phone?
Thanks.
--
M
PS:
Note: Please feel free to move this thread to appropriate category, if this does not belong here
MadhaviJ said:
Hi,
I have a very basic question with regards to Android OS. Why can't we easily update the Android OS to newest version; just like we do it for say a Windows PC? I understand that there are hardware limitations for OS updates.. similar to say for example Win7 not supporting older hardware. But if want to update to the newest android version for my phone.. why are there "custom ROMs" posted in forums? What are the contents that go in these Custom ROM? I am interested in the programming part of this.
Also, second question is where do I get the say for example Jelly Bean ROM that I modify to suit for my phone?
Thanks.
--
M
PS:
Note: Please feel free to move this thread to appropriate category, if this does not belong here
Click to expand...
Click to collapse
Well, it depends on a whole lot of things.
1) The bootloader on the atrix2 is locked. This means that you can not actually flash a custom kernel without using something like kexec. This also means that for ANY real android updates, that they MUST come from motorola, or at least be signed by motorola (like the leaked JB asia version we have, that will NOT run on at&t phones, without major and fairly dangerous work). And Motorola abandoned this phone after ICS for the most part.
2) You can flash any "custom" rom be it based on stock or a compiled ROM like cyanogenmod, AOKP, etc. they just can not use the kernel that comes with it, and there are some very special files and trickery to make that happen when compiling the ROM.
3) This phone is locked done at more than just the bootloader, there are other parts of the phone that they have signatures on that do not allow you to go up or down in versions of android, unless you have a special developer version, or one of the MEARET/SEARET versions of the phone, or you made that fairly dangerous mod, I mentioned before.
The Custom ROMs have some nice acceleration tweaks, UI tweaks, and removal of all the crap and bloat apps that come from most providers. These "Custom" Roms are usually all opensource, just like Linux/Android, and you have the chance to customize it even farther with some C code and Java, if you like.
Here is a link to the Cyanogenmod page, and a couple other "custom" ROM pages:
http://www.cyanogenmod.org/
http://en.miui.com/
http://aokp.co/
There are many many more ^^
Now to make a custom ROM you will need a Linux install someplace (a VM at least, but the compile may run way longer), some C++ and java knowledge (even just a small amount will help a little), be good at using google to fix your compile errors, and a whole lot of patience.
I always suggest a new person who would like to learn to dev, start easy and try their hand at a stock rom first using the kitchen it is much easier, and you can do some nice things and learn. Once you get that down, and learn the trouble shooting part of ROM building, you may try your hand at "custom" ROMs, or you can do what some have done and just jump into the "custom" ROM thing, but it is a little harder, and will take more time to get it down.
You can also do as a few other have done, and learn how to port roms from other like phones, but I never could get them to function as they should with ALL parts working, there was almost always something that did not work well enough for me to want to use a ROM I ported. Though others have had huge success with this, and you could PM them to ask their secrets.
Here is my post on where to get the tools needed to start working with your stock ROM, using the kitchen and other tools with Linux:
http://forum.xda-developers.com/showthread.php?t=1404442
jimbridgman said:
Well, it depends on a whole lot of things.
1) The bootloader on the atrix2 is locked. This means that you can not actually flash a custom kernel without using something like kexec. This also means that for ANY real android updates, that they MUST come from motorola, or at least be signed by motorola (like the leaked JB asia version we have, that will NOT run on at&t phones, without major and fairly dangerous work). And Motorola abandoned this phone after ICS for the most part.
2) You can flash any "custom" rom be it based on stock or a compiled ROM like cyanogenmod, AOKP, etc. they just can not use the kernel that comes with it, and there are some very special files and trickery to make that happen when compiling the ROM.
3) This phone is locked done at more than just the bootloader, there are other parts of the phone that they have signatures on that do not allow you to go up or down in versions of android, unless you have a special developer version, or one of the MEARET/SEARET versions of the phone, or you made that fairly dangerous mod, I mentioned before.
The Custom ROMs have some nice acceleration tweaks, UI tweaks, and removal of all the crap and bloat apps that come from most providers. These "Custom" Roms are usually all opensource, just like Linux/Android, and you have the chance to customize it even farther with some C code and Java, if you like.
Here is a link to the Cyanogenmod page, and a couple other "custom" ROM pages:
http://www.cyanogenmod.org/
http://en.miui.com/
http://aokp.co/
There are many many more ^^
Now to make a custom ROM you will need a Linux install someplace (a VM at least, but the compile may run way longer), some C++ and java knowledge (even just a small amount will help a little), be good at using google to fix your compile errors, and a whole lot of patience.
I always suggest a new person who would like to learn to dev, start easy and try their hand at a stock rom first using the kitchen it is much easier, and you can do some nice things and learn. Once you get that down, and learn the trouble shooting part of ROM building, you may try your hand at "custom" ROMs, or you can do what some have done and just jump into the "custom" ROM thing, but it is a little harder, and will take more time to get it down.
You can also do as a few other have done, and learn how to port roms from other like phones, but I never could get them to function as they should with ALL parts working, there was almost always something that did not work well enough for me to want to use a ROM I ported. Though others have had huge success with this, and you could PM them to ask their secrets.
Here is my post on where to get the tools needed to start working with your stock ROM, using the kitchen and other tools with Linux:
http://forum.xda-developers.com/showthread.php?t=1404442
Click to expand...
Click to collapse
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Thanks Jim. That was very helpful. I'm going through the links that you've provided and find them useful.
Any more questions... I'll post them in this thread.
--
M
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..
I've got the Oukitel WP16 which a 64 bit and has an octa-core MediaTek Helio P60 MT6771V on Android 11. Actually a pretty decent rugged phone. Originally tried to root it through fastboot and bricked it about 2 weeks after getting it. For the life of me, I couldn't bring it back to life. Finally after 4 months of it just sitting in a drawer, I went about flashing it to bring it back to life a little differently than I was before and it stuck. Very thankful that it was working again because in those months I had destroyed 3 of your average break if you touch them phones. However me being me, getting it going again wasn't enough. So I gave rooting it a try again. Got it! Rooted with Magisk. Now because I have one of those devices I believe is under rated and under developed, I can't find any kind of development done on it whatsoever and want to build/port TWRP so I'm able to try a GSI ROM. My problem is that every tutorial I read or watch has nothing like what is my stock ROM. Either names of files are different or I find the files in other folders, I've got more folders than what I'm trying to port, and, I would need to double check again, but I wanna say that I've even found them in different partitions. So my question is, what do I do? Like fstab is not in the recovery but in something else. That something else that has fstab in it, my port doesn't have that folder at all. And there are others like that. I've tried several, I repeat SEVERAL different tutorials and cannot figure out what to do. I know it's beyond the capabilities of the tool, but I even tried one of those Hovatek port tools. Obviously didn't work because of the kernel. So to say I'm lost is an understatement. This isn't the first phone I've tried this with. Had another 64 bit with the same chipset that actually had a unofficial TWRP built for it. But when it came to try to port a ROM, I was left with files in different folders and things that weren't in the ROM i was trying to port. I eventually just have up because I kind of had to since scuba diving with the phone here in the Mexican Caribbean finally took it's toll on the phones external hardware. But yeah, back to my only question. What do I do in this situation? I'm mainly concerned about it because this WP16 has a night vision camera on it which I use quite often and don't want to lose that. Recovery has nothing to do with the camera but the ROM I'd like to port will. So figuring out what to do with the recovery could eventually lead me to my answer with the ROM. Anyway, kind of a long winded explanation just to get to what may seem like a simple question to some. Any help would be greatly appreciated.
finnroth69 said:
I've got the Oukitel WP16 which a 64 bit and has an octa-core MediaTek Helio P60 MT6771V on Android 11. Actually a pretty decent rugged phone. Originally tried to root it through fastboot and bricked it about 2 weeks after getting it. For the life of me, I couldn't bring it back to life. Finally after 4 months of it just sitting in a drawer, I went about flashing it to bring it back to life a little differently than I was before and it stuck. Very thankful that it was working again because in those months I had destroyed 3 of your average break if you touch them phones. However me being me, getting it going again wasn't enough. So I gave rooting it a try again. Got it! Rooted with Magisk. Now because I have one of those devices I believe is under rated and under developed, I can't find any kind of development done on it whatsoever and want to build/port TWRP so I'm able to try a GSI ROM. My problem is that every tutorial I read or watch has nothing like what is my stock ROM. Either names of files are different or I find the files in other folders, I've got more folders than what I'm trying to port, and, I would need to double check again, but I wanna say that I've even found them in different partitions. So my question is, what do I do? Like fstab is not in the recovery but in something else. That something else that has fstab in it, my port doesn't have that folder at all. And there are others like that. I've tried several, I repeat SEVERAL different tutorials and cannot figure out what to do. I know it's beyond the capabilities of the tool, but I even tried one of those Hovatek port tools. Obviously didn't work because of the kernel. So to say I'm lost is an understatement. This isn't the first phone I've tried this with. Had another 64 bit with the same chipset that actually had a unofficial TWRP built for it. But when it came to try to port a ROM, I was left with files in different folders and things that weren't in the ROM i was trying to port. I eventually just have up because I kind of had to since scuba diving with the phone here in the Mexican Caribbean finally took it's toll on the phones external hardware. But yeah, back to my only question. What do I do in this situation? I'm mainly concerned about it because this WP16 has a night vision camera on it which I use quite often and don't want to lose that. Recovery has nothing to do with the camera but the ROM I'd like to port will. So figuring out what to do with the recovery could eventually lead me to my answer with the ROM. Anyway, kind of a long winded explanation just to get to what may seem like a simple question to some. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Your device already have TWRP [Firmware version: OUKITEL_WP16_RU_V04_20220621 ] but you not need Custom Recovery for install GSI. Use stock recovery.
About GSI with a night vision camera support so is much expensive solving that. You can try but need very experience and patience of the tests and solutions.
lopestom said:
Seriously? Thank you! I'm guessing the link is gonna be in 4pda being that it's Russian? I've spent a month searching and haven't found anything whatsoever. And since I don't read Russian, I always overlook 4pda even though it's been a great resource in the past. And yes, I'm aware you don't "need" custom recovery for GSI's. It does make things a little easier for me though.
Click to expand...
Click to collapse
The recovery issue will be solved since there is a recovery out there. That still doesn't solve the mystery and problem i have of files being in different places though. In that case what do I do if the files isn't in the same place in the port as it is in the stock, or the other way around? Add the stock file to the same folder it is in for the port? Or should I make a new folder in the port that's name is the same as in the stock? If neither, what do I do?
finnroth69 said:
Seriously? Thank you! I'm guessing the link is gonna be in 4pda being that it's Russian? I've spent a month searching and haven't found anything whatsoever. And since I don't read Russian, I always overlook 4pda even though it's been a great resource in the past. And yes, I'm aware you don't "need" custom recovery for GSI's. It does make things a little easier for me though.
Click to expand...
Click to collapse
No! Search my repository in the github in the release option.
finnroth69 said:
The recovery issue will be solved since there is a recovery out there. That still doesn't solve the mystery and problem i have of files being in different places though. In that case what do I do if the files isn't in the same place in the port as it is in the stock, or the other way around? Add the stock file to the same folder it is in for the port? Or should I make a new folder in the port that's name is the same as in the stock? If neither, what do I do?
Click to expand...
Click to collapse
As I wrote before, it is very difficult to solve issues like the original stock ROM camera. There are even one or two people who managed to get this to work.
Now what you don't understand: If you want a Custom ROM, use GSI and adapt, solve, analyze and test by changing some stock ROM files in GSI. You must understand that you need experience and time. You can even compile a Custom ROM - any GSI - specifically for your device. So you just need to have the source code of your device, have the GSI source code and know how to compile the file so that you can do the tests. Again, you must understand that you need experience and time.
If you haven't researched what is GSI and still think that Custom ROMs portability that happened before until Android 7.1 then look, read and update yourself.
In your questions, be as detailed as possible. You write a lot of parts and you scramble the words.
As for having GSI normally I already wrote where there is an instruction to install and you follow. As for TWRP, look it up on my github.
As for solving something in the GSI, if you managed to install it and still used the phh options to try to fix any bad part, then it is only you who will be able to solve any error/adaptation/bug/extra installations that there.
Trust me when I say I understand what you're saying. I have done some testing I have watched tutorials, I have studied. but everything that I have seen is basically switching a file from a folder on the stock ROM to a folder in the ported ROM with the same name as what's in the stock ROM, and possibly adding a little script to something. What I'm trying to figure out is what I asked. Fstab is not in recovery on my phone's stock ROM. It is in something else. But fstab is in and a part of recovery for TWRP. So even though there might be a TWRP for my phone doesn't help me to know if I should be creating that same folder that's in my stock ROM in the ported one for fstab or other files that are like it. I have downloaded the TWRP from your profile and I've gone to the 4pda and discovered that you're the dev who ported it with and without encryption. Nice work and thank you! I would like to move beyond being a flash baby though. So I'm simply trying asking that one specific question to help me learn because it is something I am lost on. Whether it is to port recovery, port a ROM, or whatever, I don't know what to do when the location of the files I need to port from the stock aren't matching with the with the location of the files in the port itself. Fstab is just one example. I'm gonna send you a friend request. Later when I fire up my laptop, I'll take screenshots to physically show you exactly what I mean. Please be patient and don't get upset at me for trying to learn. As well as please take your time in responding. It's no rush since I've got a business to run and this is something I'm trying to teach myself on the side. It really is something I'm lost on, and if I'm lost on it, how many others has it confused as well?
As for the camera app issue. We can forget I asked that also. I understand completely what you're saying about it being far beyond my reach right now. Thank you for the heads up on that.
Mr. Lopestom can you please help me with your recovery images? I cannot seem to get any of them to boot. I've tried the with script found on 4pda, without that script, I've tried flashing an empty vbmeta, but nothing is getting the images to boot. See attachment for script I'm talking about. Attachment only shows me running it, but I have tried without.
What sense does it make to flash an empty VBMETA ? You typically pull the existing VBMETA and pass this file to Fastboot what rewrites 2 bytes in that file.
finnroth69 said:
Mr. Lopestom can you please help me with your recovery images? I cannot seem to get any of them to boot. I've tried the with script found on 4pda, without that script, I've tried flashing an empty vbmeta, but nothing is getting the images to boot. See attachment for script I'm talking about. Attachment only shows me running it, but I have tried without.
Click to expand...
Click to collapse
The problem is not in the vbmeta file. You can use this one if you can: Post in thread 'Looking for a walkthrough on installing a custom ROM on a BLU G90 PRO' https://forum.xda-developers.com/t/...om-rom-on-a-blu-g90-pro.4253737/post-85180967
The big fact is that the company put a recovery.img stock file inside /vendor/etc/ and you should know how to deal with it. So only removing this recovery.img and repacking modified vendor.img made by u; install that in your device so you can have TWRP.
jwoegerbauer said:
What sense does it make to flash an empty VBMETA ? You typically pull the existing VBMETA and pass this file to Fastboot what rewrites 2 bytes in that file.
Click to expand...
Click to collapse
I'm not sure to be honest with you. Like I told lopestom, I'm just trying to teach myself as I can in my free time. A lot of what I do is imitate what I see or read. While reading post about flashing twrp i had read something about flashing an empty vbmeta file.