Related
Sorry i cant work on this anymore because i lost defy. Sorry guys
Hello guys,
first of all, i am no where near a developers level, but being somehow geeky at linux and android stuff, i am trying to port MiUi ROM for motorola milestone to motorola defy. I havent succeeded till now, but i will try my best to bring MiUi goodness to Defy phone users. I worked all night last night, trying to do different stuff every time hoping it works, but everytime i do anything, all i get is the big a$$ motorola logo. I need some developer's help on doing this.
The main problem has been motorola's locked bootloader, which does not let me flash updated zip files, unless i flash the original sbf, log into motoblur, root it, install recovery, boot into recovery and finally install. And trust me, i did all of that like 10-15 times last night. Even my phone must be pissed off at me right now cuz of that If there is an easier way,please, please please let me know.
I have tried everything from replacing apps, extracting boot.img, replacing framework files, installing directly, using kitchen for htc to automatically replace and almost eveything i could think of, and still no success. I really need help from someone who can debug kernels and sneak into bytecodes.
You are really welcome to help me if you think that you could help in any ways. Please shoot me an email at zed [at] wireshock.com (i will usually reply asap), or add me in gtalk admin [at] wireshock.com so that we can talk about it. Lets all hope that we can see miui in defy some day. Wish me luck
Edit: Here is the final thing i came up with, if anyone wants to examine, here is the link -> Click Here
PLEASE NOTE THAT THIS WILL NOT WORK! IT WILL NOT BOOT! THIS IS FOR DEV'S ONLY!
March 29
Update (9:40 AM): Another night without success. I am trying my best to make it work. Few people have contacted me about this, and some have helped a lot. Thanks to them. I contacted eugene_373 about this, lets hope he replies fast.
Update (11:48 AM): @KSubediTweet My Defy no longer works... So, not much help I can give. <- Eugene's defy doesnt work, need some devs who work for defy.
Update (5:54 PM): Me and Landroid from xda worked for almost the whole day trying to make it work. No success till now, but i think we are closer than before. If anyone finds a way to run recovery without booting somehow, please let me know, that will help a lot. And be sure to say thanks to Landroid for helping me out a lot.
April 6
Update (10:53 AM): Spent the last week trying to figure out a way to run recovery without booting which would help me save 80% time. Need some more Dev's help. I have tried contacting some chinese miui developers so that they could help me on porting the rom. Waiting for reply.
April 7
Update (8:35 PM): I think i finally found something that can help! Check this out -> http://forum.xda-developers.com/showthread.php?t=1026853
April 13
Update (8:14 PM): After few days of being idle, i am back to the track. Now as i have 2nd init, pre boot menu and everything i need to work, i will try as fast as i can. And racca pointed out some stuff i didnt know before, so i am kind of positive about getting it to work this time.
P.S. All times are MST (GMT -7)
I don't have much technological knowhow to add, but good luck and its great that someones finally making the effort, so don't give up!
Sent from my HTC Vision using Tapatalk
tbman1996 said:
I don't have much technological knowhow to add, but good luck and its great that someones finally making the effort, so don't give up!
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
Thanks, ill try my best.
Eugene made some adaptations on system recovery to apply update.zip. I don't know exactly how that works but maybe help you.
link: http://forum.xda-developers.com/showthread.php?t=995131
Thanks a lot for the link, if i can get the keyfile, i think i can make an update.zip for the recovery and can open clockworkmod from default recovery. Ill try it
Edit: or i can sign the zip file so that i can flash it from default recovery.
Dexter_nbl did the port of sense for us. In his rom he used a file on sdcard to boot on recovery. Like, if the file called recovery_mode exist on sdcard execute the script to boot up on recovery....this helped a lot!
psicodelico said:
Dexter_nbl did the port of sense for us. In his rom he used a file on sdcard to boot on recovery. Like, if the file called recovery_mode exist on sdcard execute the script to boot up on recovery....this helped a lot!
Click to expand...
Click to collapse
That might have worked if the room booted at all, the problem here seems to be with some hardware driver that is preventing the phone from booting. Only if someone who knows what is preventing it from booting could help me out, i would work on fixing it somehow.
good to see a new project coming up.
got a bit quiet here in the past week, devs probably waiting for motos official froyo release.
anyways, kepp us updated on your progress and good luck!
ksubedi said:
That might have worked if the room booted at all, the problem here seems to be with some hardware driver that is preventing the phone from booting. Only if someone who knows what is preventing it from booting could help me out, i would work on fixing it somehow.
Click to expand...
Click to collapse
That ideia is for you access your system recovery to restore your system without flash a sbf, get root, install system recovery (that take a long time). This way you can try more things. Dexter call the script to verify the file on sdcard in beginning of the process of boot, i dont know how but if you want see take a look the first version of his ROM.
i dont think you can sign the update packages. maybe you should try to ask eugene how this whole cookie cutter thing works
http://twitter.com/eugene_373
http://eb-productions.proboards.com/
would be awesome to get miui on defy...
Sent from my MB525 using XDA Premium App
psicodelico said:
That ideia is for you access your system recovery to restore your system without flash a sbf, get root, install system recovery (that take a long time). This way you can try more things. Dexter call the script to verify the file on sdcard in beginning of the process of boot, i dont know how but if you want see take a look the first version of his ROM.
Click to expand...
Click to collapse
That is exactly what i have been trying to do since my first day. I have asked eugene_373 for help on this. Thanks anyways.
drsouly said:
i dont think you can sign the update packages. maybe you should try to ask eugene how this whole cookie cutter thing works
http://twitter.com/eugene_373
http://eb-productions.proboards.com/
would be awesome to get miui on defy...
Click to expand...
Click to collapse
Thanks for the link I just contacted eugene_373 about this. Ill update once i get a reply.
Keep it up!!
One closer day i will buy the defy
Thank you for your efforts. Look forward to your success
any news?!
Any news ???
I have contacted miui developers to help me out. Waiting for reply now. Lets hope that we can bring miui to defy as soon as possible. Need help from some devs.
What do you mean go to recovery without booting? Without booting to Android you cannot use any other means to write to the Filesystem, so how would you do that? You can't replace the recovery that's installed with the phone, so I don't really see how that would be possible.
Recovery without booting is possible through charge-only-mode, but no one is capable to do it for Defy. And probably it is possible in Defy Sense ROM, if you read the thread. But I did not tried.
an option would be to look for an exploit in the recovery, that allows us to make something like open recovery on the milestone... i would ask the devs from openrecovery
There is the way using the second boot used on milestone (2nd-init) and the way used by Dexter in Sense ROM;
- included ClockWorkRecovery custom edition for this rom
• - Do NOT install the apk release, or it will ruin bootup of sense.
• - activate Recovery by putting an empty file in the root of your sdcard called "recovery_mode"
• content can be anything or empty, just make sure filename is correct.
• - reboot, and it will load into recovery.
Click to expand...
Click to collapse
Sense ROM: http://forum.xda-developers.com/showthread.php?t=933710 (get the first version to see the magic)
2nd-init: http://forum.xda-developers.com/showthread.php?t=1003449
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.
I believe this section is dead for the most part...
As many of you should know, those of us who took the OTA update have no way of rooting if towel root does not work... (Futex patched)
However there is hope!
I am not very knowledgable about exploits or reverse engineering...
There are two exploits that may be able to get us root when combined.
CVE-2014-7911(gets us system uid)
Cve-2014-4322(goes from system to root)
There is public poc code to do this...
However we need something...
I am working on getting the kernel symbols
When you get started please consider creating a thread in the Developers ONLY area which is heavily moderated. Good luck in this endeavor!!!
KennyG123 said:
When you get started please consider creating a thread in the Developers ONLY area which is heavily moderated. Good luck in this endeavor!!!
Click to expand...
Click to collapse
I figured that this may get more attention here....
I really do hope we can get root ASAP
I dunno if 4.3 kernel will work, I don't see why the addresses would of been changed but I am not a devloper nor an experienced hacker. (After some research this is probably incorrect)
Just need someone with stock kernel and root so we can get the addresses for cve 4322 and gg
Can you move this post or should I just create another thread in the developers section?
I'm rooted with Towelroot, on the Superliterom developed by mohammad.afaneh
http://forum.xda-developers.com/galaxy-s3-verizon/development/rom-superliterom-v1-0-i535vrudne1-t2805797
Not sure if that qualifies as stock kernel. I'd love to help as long as you can give me detailed instructions. If necessary I'm willing to go back to true stock if it helps unlock the bootloader so I can find a rom that's easier on the battery.
What do the commands yoh postes do, and what do you mean by "drop a link"? You can see I don't have much experience "under the hood".
IWellHeThanks said:
I'm rooted with Towelroot, on the Superliterom developed by mohammad.afaneh
http://forum.xda-developers.com/galaxy-s3-verizon/development/rom-superliterom-v1-0-i535vrudne1-t2805797
Not sure if that qualifies as stock kernel. I'd love to help as long as you can give me detailed instructions. If necessary I'm willing to go back to true stock if it helps unlock the bootloader so I can find a rom that's easier on the battery.
What do the commands yoh postes do, and what do you mean by "drop a link"? You can see I don't have much experience "under the hood".
Click to expand...
Click to collapse
If you're able to be on 4.4.2 that is rootable via towel root, it's not the exact kernel that I and others are on because futex is patched on the latest OTA. If you're able to boot into the stock rom (don't update if possible, may lose root?) and those commands (from my understanding) get us the addresses we need for the root on latest OTA. I remeber reading that they get randomized after every time it's compiled so it may not help. If someone more knowledgeable about this can help that would be great. No hurt in trying though. Just need you to do those commands then upload kallsyms and leave a link. Open it with a text editor and make sure it's not all 0's then words ect. Needs to be numbers then text, which is why root is required to do that... If we can get those adresses for the updated kernel we can get root on latest. I doubt we're getting lollipop....
Ok guys I have the boot.img for my device, the prepaid on nf5
I will get kernel from it when I can and then we are close...
Today I upgraded to an S5, so I can now afford to get locked into a stock rom on the S3. So if someone more knowledgeable can help me get this phone to the point wherr it gets you the data you need, I'll do it. In fact, I may be willing to send you this phone in a few weeks and you can borrow it for development if you promise to eventually return it with Cyanogenmod 10.x or another AOSP rom on it If it needs to be connected to get the latest OTA "up"grades then I'll get those going. My plan for the S3 is now to keep it as a backup. Saves me from paying for insurance on the new one.
Just to clarify on the commands; each line is a separate command, right? Right now kallsyms is 000000 textetc. . . I inputted the commands assuming each line was a separate command, hit the "enter" key after each line. It definitely accessed SU to do it as well.
I don't have a file upload account but if it's possible to upload it here or e-mail it I'm happy to do so.
What firmware build.are you on and whata your model? If you're not on a locked bl yet then don't lock it...
To clarify I am on nf5 on the I535PP. I think that after each tike tge kernel is compiled the adresses aee randomized... I have the compressed kernel binary from an update.tar.md5... I need to figure out how to decompress it... could I load in in qemu and do a ram dump? We basiclly just need the kernel symbols for the exploit to modify poc to work for our devices. The build date on mine is jul 22, futex(towelroot) is a nogo. I don't know if I535 and I535PP use the same kernel, I'll test when I get a chance.... If a mod could move this to devlopment and change the title to "NF5 root progress" or something like thay, woupd be great.
Ok guys, I am working on extracting.the kernel.then the kernel.adresses ahould.be easily obtainable, then I can build.the binary for 7911 to run as system and GG
When I get home I will begin I really hope I dont run into any issues...
Btw, I am not wanting/expencting donations/bountys nor am I promising anything other than mabey a "thanks". I am not a devloper and using publiC exploits and poc makes me nothing .special
OpenSourcererSweg said:
What firmware build.are you on and whata your model? If you're not on a locked bl yet then don't lock it...
To clarify I am on nf5 on the I535PP. I think that after each tike tge kernel is compiled the adresses aee randomized... I have the compressed kernel binary from an update.tar.md5... I need to figure out how to decompress it... could I load in in qemu and do a ram dump? We basiclly just need the kernel symbols for the exploit to modify poc to work for our devices. The build date on mine is jul 22, futex(towelroot) is a nogo. I don't know if I535 and I535PP use the same kernel, I'll test when I get a chance.... If a mod could move this to devlopment and change the title to "NF5 root progress" or something like thay, woupd be great.
Click to expand...
Click to collapse
I'm pretty sure the bootloader is locked; that's why I'm interested in what you're doing I was very disappointed to learn that I couldn't install an AOSP ROM after I repaired my phone.
When I replaced the motherboard and booted up, it was running 4.4.2 (and everything was in Spanish lol). The SKU on the sticker of the phone I got the motherboard from is SCHI535ZKB so does that make it the I535ZK? The concept of hardware version is new to me (and causing me frustration with my new S5).
I think the firmware is NE1, but as I said I've got the Superliterom, so under build number it says
SUPERLITEROM! V2.0
KOT49H.I535VRUDNE1
But as I said, if it helps you (and therefore helps me) I can flash it back to stock and take the OTA upgrades til it's at the NF5 firmware. But as you said I expect I would lose root, and then be unable to get the info you wanted. Seems like a real catch-22, at least at the skill level I'm at.
Glad you're making progress and let me know if you think there's anything I can do to help.
Don't risk losing root in a case I fail. You should be able to flash ne1 but don't flash nf5 or whatever. I don't think I will need someone who's already rooted since I am taking a diffrent approach to getting the symbols. I hate using hex editors... Especially ones from market and not on a pc....
I seem to have hit a brick wall... Great....
I don't seem to be able to decompress the kernel :/
I thought that most kernels on android used gzip but binwalk says its LOZ and some stuff about encryption... My device storage is encrypted and I did copy the update from it.....
I'm going to decrypt my phone tonight and try again tomarrow....
When you hit a brick wall, use a sledgehammer.
My phone is encrypted, too, so I guess it would have given you the same issue had you tried with it.
Well, I am taking a diffrent approach completely from what I originally thought I needed someone for.
I am trying to get the symbols from the kernel itself, I have gotten boot.img from the firmware, I have gotten zImage from boot.img. I am currently trying to get the goodies from zImage but having trouble getting at them. I am very confused because the gzip magic headers are there... When I use dd to get that saved and try to gunzip it I get an error about corruption... I need an uncompressed kernel to get the symbols for the qcom cve...
Once I get those I just plug those symbol values into poc code I found on GitHub, build the binary with ndk, then take that binary and put it In a folder from the other part of the poc, build the app using android studio, test it, then boom. Everyone with the same kernel *SHOULD* have root
If any of you devs with reverse engineering know how could point me in the direct for getting the uncompressed kernel binary, please point me in the right direction.
Google simply isn't helping at this point.
Basically, fire off cve 7911.
With system privileges, execute the binary and GG
I created a thread asking for help in the dev section, hope I get this going.
https://github.com/android-rooting-tools/libmsm_vfe_read_exploit
...
This is probably useful, going to try it later.
When did NF5 come out?
Is there a new radio I can flash?
LLStarks said:
When did NF5 come out?
Is there a new radio I can flash?
Click to expand...
Click to collapse
He's speaking of the prepaid VZW S3 not the contract version
Sent from my Nexus 5
Reversing the kernel doesn't seem possible to me at all at this point with my limited knowledge of this....However I have been digging and it may be possible to get root by taking the Odin flash able OTA, extracting the files, deleting the bootloader and recovery files, unpacking or mounting system.img and adding an SU binary (and setting permissions?), Repack, put it all together and then flashing it via Odin. If I can obtain root this way, I'll be able to get what I need to try to make a 1 click root for others on mf5(only the i535pp phones I believe) and then I can die happily.
I'm not much of a "developer" but I am determined to get this.
I have successfully built a flash able tar.md5 with a modified system.img.ext4 containing a su binary that I chowne as root under linux & chmoded
Also have supersu.apk chmoded and I'm the apps.
I am currently moving the tar.md5 to my sdcard from my pc and I am about to boot windows to see if I can no flash via Odin
If all goes well, I will be very happy indeed.
Well, I managed to soft bring my device.
I'm not entirely sure how I managed to do that...
I am about to flash stock again via odin, i should have backed up some files xD
Just saw the following article from XDA regarding TWRP v3.5 being released. I'm hopeful that this means that for devices that ship with Android 10 that TWRP will be able to decrypt the data partition in order to facilitate a complete backup.
That said, does anyone know how long it typically takes for TWRP to be supported on a new device (i.e. G-Stylus 2021)? Just curious what the norm is. Thanks!
That's a good question. I don't know how long it should take, but after reading the article you linked it seems that successfully porting TWRP to these newer phones will take a lot longer than on the older ones. Hopefully someone's already started working on TWRP 3.5 for the 2021 models, but I haven't heard any actual news on that yet.
I would love to be able to get a full backup of my device in case I really screw something up later on. If I had any level of programming skills I would certainly make an attempt at it myself.
DM.IDOL said:
That's a good question. I don't know how long it should take, but after reading the article you linked it seems that successfully porting TWRP to these newer phones will take a lot longer than on the older ones. Hopefully someone's already started working on TWRP 3.5 for the 2021 models, but I haven't heard any actual news on that yet.
I would love to be able to get a full backup of my device in case I really screw something up later on. If I had any level of programming skills I would certainly make an attempt at it myself.
Click to expand...
Click to collapse
I'd look around on github
THIS is a TEST build for the Moto G stylus XT2115-1 minsk_t
(please mind that i have never done this before and i am at least trying to figure out how to create custom recoveries. i just need a good teacher with a little time. .)
*Touch Screen does not work. OTG mouse necessary.*
(not too sure how to fix this error)
*Mount points were for testing*
(modied fstab files in ramdisk to fix mount points)
*modified ramdisk and split_image from Moto G 9 plus unofficial 3.5.1 twrp*
https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-g9-plus-odessa.4195729/
i tried to put a recovery together for this device but im not sure where i went wrong or what to do next. booting into this recovery works but /vendor and /system_root have denied permissions. when it is flashed within twrp and rebooted to recovery or system the screen says no OS installed press power to power off. If anyone can help me figure this one out i would be greatly appreciative. If you need anything i can pull from my device just let me know. Anyone willing to help work on this recovery and figure out what needed to be fixed i would greatly appreciate it!
*EDIT*
i got /data to back without digest verification. Was not able to try to restore the backup as i got NO OS error when i rebooted to restore.
*EDIT*
i was able to figure out pretty much everything except the touch part of the recovery. it has a novatek_ts (NVT-ts)
not sure what to do to enable the drivers for twrp. any feed back would be great.
*EDIT*
Found the driver. I'll post it here and see what you can do. I'll also work on it as I'm still learning where stuff should go in the recovery. And also seems to b that i cannot access external sd from twrp either.
*EDIT*
resolved sd card issues. mountpoint was incorrect. only thing left to get working is touchscreen and not have to use otg mouse.
updated twrp for minsk_t is in files now.
*EDIT*
I found the proper elements to configure the recovery's touchscreen capabilities. Will be recompiling later on today. After I have tested it I will post the new working TWRP recovery. Thanks everybody.
*deleted*
sosthenisRR said:
*deleted*
Click to expand...
Click to collapse
So this is fully functioning now right? Is there any reason to use this over the OrangeFox recovery that has been posted?
Also, if I did install OrangeFox, and decided I wanted to install this later, would it be as simple as flashing using fastboot from ADB, overtop of OrangeFox? Or would the procedure be a little more complex?
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.