Related
I'm sorry that I post the thread in wrong sub-forum, i don't have enough permission to post thread in development forum.
I've a ship s-off Incredible S, couple of days ago, I download Incredible S 2.6.35 kernel source code,
and successfully compiled the kernel.
I get a tun.ko kernel module, insmod it in adb shell, and it works fine ^_^
And now, i changed some kernel configurations, get a new kernel zImage file, but i don't know how to repack IS's boot image, seems HTC add 256 bytes of signature in front of boot.img file.
I've tried reboot into fastboot mode, and use fastboot to flash zImage directly, but it reports "not allowed" ...
Is there some instructions i can follow to repack the kernel boot image so i can update IS's kernel?
Thanks ^_^
Is the instructions of flashing IS's boot image similar to Desire HD ?
Ok, I need a few extra kernel modules... So I figure I'll just rebuild the kernel, like I've done a billion times before on other devices.
Well, I must be missing something, because the kernel will NOT boot. My xt1060 just sits at the bootloader unlocked screen and eventually reboots (I'm assuming some kind of watchdog timeout?).
So what am I missing?
I've tried unpacking and repacking the original CM11 kernel boot.img (using the info from the unpack) and that doesn't boot either, it's also about 1mb smaller than the original as well.
After some reading I caught something on DTB images, so I'm guessing that's why the repack was smaller, but is that why it won't boot?
My mkbootimg came out of the CM11 sources and my XT1060 is running whatever the last nightly of CM11 (which is really old).
I'm not building the full CM11 source, just the kernel... I don't have the time for the full build (and shouldn't have to!)
Can anyone help?
Thanks!
I just tried again with some boot img tools that support DTBs and same result, no boot.
I tried using mkboot to unpack and repack and it puts out a file close to the original image, but still no boot.
What am I missing, is there a checksum that the moto bootloader needs?
What is CyanogenMod or TWRP doing to their boot.img that I'm not?
Hi seishuku,
I am also getting same issues while flasing with custom boot.img . I unpacked and packed using mkboot unable to boot my MotoX(XT1052).
If you got solution how to boot with custom zImage and devicetree please help????
Thanks
Ram
Thanks goes to @nilezon for giving me the rundown, as it is all from his repos, save for a couple of things to make it work for the Z5 instead.
(Yes, your bootloader has to be unlocked)
Kernel is based on firmware version 32.0.A.6.152
There is two versions of the kernel: one with a recovery script, and one without.
The one with the recovery script will allow you to boot into recovery during your phone's startup process.
To enter recovery:
Boot up your phone like normal. Wait for the LED status light to turn amber. Once that happens, start pressing the volume buttons a few times. This will take you into the recovery menu.
The one without the recovery script does not have this option. This means that your phone will boot up a few seconds faster than the one with it.
Xposed: The Camera 2.0.apk plays nicely with Xposed now. No need to deoxed it manually!
Anyways:
TWRP
https://goo.gl/k9PiFV - TWRP 2.8.7.0
KERNELS
https://goo.gl/wzUAv4 - With recovery script, flashable zip file
https://goo.gl/8LTc9l - No recovery script, .img file that must be flashed through fastboot
For the recovery:
Code:
fastboot boot recovery.img
to just boot into it to flash a zip
OR
Code:
fastboot flash recovery.img
to flash it (although, you will need to do fastboot boot recovery the first time to get into it)
Kernel:
Code:
fastboot flash boot z5_stock_fixed_fixed.img
- For the .img file
The blues are oranges instead, like his, but it is kinda cute.
Have fun.
For unlocked bootloaders?
Sent from my Sony Xperia Z5
Snaqejack said:
For unlocked bootloaders?
Sent from my Sony Xperia Z5
Click to expand...
Click to collapse
Yes.
Technically you can flash the boot.img in the recovery ?
bazhip said:
This isn't flashable, only bootable:
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
It's fairly easy to make it bootable.
Modify your boot.img ramdisk using this code and instructions:
https://github.com/jackfagner/twrp-sony-recovery-boot-script
Then just flash the recovery with fastboot.
nilezon said:
It's fairly easy to make it bootable.
Modify your boot.img ramdisk using this code and instructions:
https://github.com/jackfagner/twrp-sony-recovery-boot-script
Then just flash the recovery with fastboot.
Click to expand...
Click to collapse
I saw that at the bottom of your post right afterwards I'll modify it in a bit here, but I wanted to make sure it was going first. Thanks for making that script!
Thanks, bazhip.
Can you provide the modified source and a quick run through on how to compile it on github?
yannik~ said:
Thanks, bazhip.
Can you provide the modified source and a quick run through on how to compile it on github?
Click to expand...
Click to collapse
The kernel or TWRP? I'm kinda busy though so I'm not sure when I'll get around to it. If you want, look at the dirty ROOT thread for nizelion and my posts. I was pretty vocal about the process and what I was doing, as it was my first time ever doing it. You should be able to follow it, I think.
Were the only changes you made disabling SONY_SECURITY_RIC and DM_VERITY in the defconfig?
zwliew said:
Were the only changes you made disabling SONY_SECURITY_RIC and DM_VERITY in the defconfig?
Click to expand...
Click to collapse
That, and ro.secure disabled and ro.debuggable enabled. As close to stock as possible.
bazhip said:
Thanks goes to @nilezon for giving me the rundown, as it is all from his repos, save for a couple of things to make it work for the Z5 instead.
(Yes, your bootloader has to be unlocked)
Anyways:
https://goo.gl/k9PiFV - TWRP 2.8.7.0
https://goo.gl/8LTc9l - Kernel that I compiled that allows root
This isn't flashable, only bootable:
Code:
fastboot boot recovery.img
Kernel:
Code:
fastboot flash boot z5_stock_fixed_fixed.img
The blues are oranges instead, like his, but it is kinda cute.
Have fun.
Click to expand...
Click to collapse
Can it be use on E6683
Build no - 32.0.A.6.152
winkhant said:
Can it be use on E6683
Build no - 32.0.A.6.152
Click to expand...
Click to collapse
It's built for the 6653, but I think it should work for the 6683. Give it a shot. If it doesn't, just flash back the stock kernel.sin from the ftf.
winkhant said:
Can it be use on E6683
Build no - 32.0.A.6.152
Click to expand...
Click to collapse
I've applied this on my E6683. All looks good :good:
magadaner said:
I've applied this on my E6683. All looks good :good:
Click to expand...
Click to collapse
Awesome! That's what I figured, but good to have confirmation. I'll edit accordingly.
nilezon said:
It's fairly easy to make it bootable.
Modify your boot.img ramdisk using this code and instructions:
https://github.com/jackfagner/twrp-sony-recovery-boot-script
Then just flash the recovery with fastboot.
Click to expand...
Click to collapse
Is there anything that needs to be changed with the recovery script to work on the Z5? I threw it into my kernel and followed the directions to a tee and I get a bootloop. I saw @AndroPlus made a kernel too using your script, so I flashed it to see if it worked and it was fine. I unpacked his boot.img and looked at it and the structure was the exact same. After hitting my head against a wall for a while, I tried repacking his just to make sure I wasn't crazy. The file size between his initial boot.img and the repacked one was a few KB different, and when I repack his, it bootloops too. So then I made sure mkboot tools were working fine and I unpacked/repacked my initial kernel, and it boots just fine.
Then I tried breaking it down:
I took my kernel, unpacked/repacked and it was fine. Then I copied over the bootrec folder, repacked, and it was fine. Then I made sure the symlink was working, so I:
Code:
mv init init.real
ln -s init.real init
and it booted just fine.
Then I did the final
Code:
rm init
ln -s /bootrec/init.sh init
and repacked, and it bootloops forever Any ideas about what is happening?
The only thing I can think of is that I messed up the symlink some how, but I dont know why AndroPlus's works before repacking and not after. Bleh :/
EDIT: **** everything. I ended up using SuperRs kitchen instead. That worked just fine. Noooo idea why mkbootimg_tools failed me.
External SD card is not detected on E6683.
Masa. T said:
External SD card is not detected on E6683.
Click to expand...
Click to collapse
Once I get my Z5 dual (E6683) in I may try to build a kernel specifically for the E6683's. I need to figure out how much I'll lose from losing the DRM keys.
Masa. T said:
External SD card is not detected on E6683.
Click to expand...
Click to collapse
In the kernel or TWRP?
EDIT: My bad, I spaced on the variants. I thought the 6683 was the baseband variant, not the dual sim. Yeah, I wouldn't roll with this on there.
And this is confirmed as working on the Z5 ?. because I have waited for root for this for some time now, and if it works I will be a happy man.
MeX_DK said:
And this is confirmed as working on the Z5 ?. because I have waited for root for this for some time now, and if it works I will be a happy man.
Click to expand...
Click to collapse
This is not an exploit, if that is what you are asking. As stated in OP, you need to unlock your bootloader first. The kernel is merely the stock kernel with the security features disabled, which allows you to be able to flash SuperSU. But yes, it works.
I have a rare phone running Android 6.0 on a MT6750 with an unlocked bootloader (might be MT6750T since it is 1920x1080, but the only things I have found say MT6750)
I have been unable to get TWRP working on this phone after trying several porting guides and TWRP images. Almost all port attempts result in the boot image (logo.bin - android logo), followed by a black screen for a few seconds, then it reboots into Android.
Is it possible to manually patch the boot.img to gain root? If so, can someone point me to a guide for it? I found https://forum.xda-developers.com/android/software-hacking/systemless-root-mediatek-t3309909 but PATH doesnt seem to be set anywhere in my boot image (grep -nrw 'boot.img-ramdisk' -e "PATH"). I tried adding "export PATH $PATH:/data/bin" or "export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin::/data/bin" to init.environ.rc with other exports, but I get a boot loop
try recompile the decompiled boot.img without doing any changes and flash the compiled boot.img to see that there is no problem with respect to compilation of boot.img
shankar_vl said:
try recompile the decompiled boot.img without doing any changes and flash the compiled boot.img to see that there is no problem with respect to compilation of boot.img
Click to expand...
Click to collapse
i decompiled and recompiled without any changes using kitchen tools and flashed back ... but its showing error.
same with recovery.img also
btw im using oppo f3 mt6750t
rajeshca911 said:
i decompiled and recompiled without any changes using kitchen tools and flashed back ... but its showing error.
same with recovery.img also
btw im using oppo f3 mt6750t
Click to expand...
Click to collapse
Then its a compilation error. Its not being compiled correctly.
Btw, systemless root by supersu and magisk do a lot things like starting sudaemon, injecting supolicy changes, mounting su.img, etc. Its better to port a custom recovery and let supersu or magisk zip do all the required things to root your device.
Or if you want to be ambitious, dirty your hands with hackings, unzip these zip files and try to implement manually what is programmed there.
My suggestion is go for porting recovery from devices matching your device specs ( need not be 100%). There are several threads on this forum helping you out on this. I think chances of porting a workable custom recovery are brighter than manually compiling su compatible boot.img.
There's the problem..
I did port custom recovery.
But when I flash it back to device it's showin error.
I understand that I need to dirt my hands more to get root my device
So I decided to compile revovery.. But oppO f3 source files r not available. I tried with omni Tom source. But it failed
rajeshca911 said:
i decompiled and recompiled without any changes using kitchen tools and flashed back ... but its showing error.
same with recovery.img also
btw im using oppo f3 mt6750t
Click to expand...
Click to collapse
rajeshca911 said:
There's the problem..
I did port custom recovery.
But when I flash it back to device it's showin error.
I understand that I need to dirt my hands more to get root my device
So I decided to compile revovery.. But oppO f3 source files r not available. I tried with omni Tom source. But it failed
Click to expand...
Click to collapse
You said that even the imgs just compiled without any changes made to decompiled files are not able to boot. Then there must be something wrong with compiling. Your tools for compiling may not be correctly working.
There are carlive image kitchen tools. get them here https://forum.xda-developers.com/android/development/tool-cika-carliv-image-kitchen-android-t3013658. They are known for flawless working.
What is more important now is that you have right tools for compiling imgs. Then you can think of further.
shankar_vl said:
You said that even the imgs just compiled without any changes made to decompiled files are not able to boot. Then there must be something wrong with compiling. Your tools for compiling may not be correctly working.
There are carlive image kitchen tools. get them here https://forum.xda-developers.com/android/development/tool-cika-carliv-image-kitchen-android-t3013658. They are known for flawless working.
What is more important now is that you have right tools for compiling imgs. Then you can think of further.
Click to expand...
Click to collapse
Thanks bro. But im using carliv kitchen tools only.
I didn't tried with other kitchen tools yet.. So i give a try other tools
rajeshca911 said:
Thanks bro. But im using carliv kitchen tools only.
I didn't tried with other kitchen tools yet.. So i give a try other tools
Click to expand...
Click to collapse
no need. carliv tools are perfect. stick with them.
are you able to successfully flash imgs with sp flash tools? no matter whether you are able to boot with them.
as for porting, use twrp or any other custom recovery of SoC as yours, mt6750t and of OS version similar to yours as well.
shankar_vl said:
no need. carliv tools are perfect. stick with them.
are you able to successfully flash imgs with sp flash tools? no matter whether you are able to boot with them.
as for porting, use twrp or any other custom recovery of SoC as yours, mt6750t.
Click to expand...
Click to collapse
Ok.. I stick with carliv as u suggested. And... Yes... Im able to flash img files to phone but not with sp flash tools. Im using professional tools ( uni tools from volcano) and also flashing using a cracked download tool meant for oppo devices. ( the download tool was created on base of sp flash tools only)
Then...
I just tried twrp porting only ( same soc mt6750t quitel k6000 plus i think.. Which chipset is mt6750t)
Also tried with oppo f1s twrp which chipset is mt6750.. ( not 6750t.. ) both went wrong..
seniors and xda developrs ( zackie& a guy from Indonesia unfortunately i forgot his name) also tried to. Port twrp for me. I also tried flashing their img files ..everything went not well.. There i have understood that either compiling or flashing causing error in my device
Thats y im trying to find other wayz.. There i found ur thread .& fetching useful checklist:good:
rajeshca911 said:
Ok.. I stick with carliv as u suggested. And... Yes... Im able to flash img files to phone but not with sp flash tools. Im using professional tools ( uni tools from volcano) and also flashing using a cracked download tool meant for oppo devices. ( the download tool was created on base of sp flash tools only)
Then...
I just tried twrp porting only ( same soc mt6750t quitel k6000 plus i think.. Which chipset is mt6750t)
Also tried with oppo f1s twrp which chipset is mt6750.. ( not 6750t.. ) both went wrong..
seniors and xda developrs ( zackie& a guy from Indonesia unfortunately i forgot his name) also tried to. Port twrp for me. I also tried flashing their img files ..everything went not well.. There i have understood that either compiling or flashing causing error in my device
Thats y im trying to find other wayz.. There i found ur thread .& fetching useful checklist:good:
Click to expand...
Click to collapse
As you tried various flashing methods, you might have already known all the related intricasies of flashing. still I just want to mention that I presume you might have then known vcom drivers, creating scatter file with mtkdroid tools, loading scatter file and, most importantly switching off phone and plugging phone to PC just after clicking on flash button in sp flash tool.
And about the other tools of flashing you mentioned, sorry I will not be helpful.
A thing to mention regarding porting is taking care of mount points in fstab file and a similar file if any at /etc folder in ramdisk of decompiled port recovery. mount points should be same as fstab of your boot.img.
Besides, ensure kernel (Imaze) of port recovery is replaced with that of boot.img.
shankar_vl said:
As you tried various flashing methods, you might have already known all the related intricasies of flashing. still I just want to mention that I presume you might have then known vcom drivers, creating scatter file with mtkdroid tools, loading scatter file and, most importantly switching off phone and plugging phone to PC just after clicking on flash button in sp flash tool.
And about the other tools of flashing you mentioned, sorry I will not be helpful.
A thing to mention regarding porting is taking care of mount points in fstab file and a similar file if any at /etc folder in ramdisk of decompiled port recovery. mount points should be same as fstab of your boot.img.
Besides, ensure kernel (Imaze) of port recovery is replaced with that of boot.img.
Click to expand...
Click to collapse
Your not helpfull??.. I don't agree with that. May be im Not in the position to catch your mind.
However.. Im not going to miss single chance to upgrade myself ( yes ofcourse from devs n seniors like u)
As you said
1) i have installed vcom drivers & fetched scatter file. ( again not from mtk droid tools) . I heard mtkdroid tools nOt fully supporting mt67xx Series. Even i tried modified mtkdroid tools developed by dev havoc.. And droid tool showed some info like cpu info.. Etc. But right hand side there was an error which saying that its usable to fetch info. . I presume the error may b causing by oppo. Own OS ( Color OS based on android 6.0).. And my last try was 2 months ago. So i dont know if there is any improvements in droid tools or not. Please privide me links if they updated/ supported 67xx series
2)yes i agree with mount points you mentioned. I was just replacing fstab file from stock to. Port. I didnt edit any. . I will check again and update u.
3) Actually im in dilemma to blame on cimpiling or flashing.. The device is not booting even i didn't modify any item after repack. I need solution for that. If that resolved... Automatically everything will b set up by themselves.. Pls share any views regarding this..
I know its difficult to u to guide until u have hands on it or personally seen d procedures & results
I may upload videos / pictures/ share Team viewer etc.. if u want to see it personally.. So.. U can better understand my problem , my flaws where i need to b improved ( onlynif u wish) however i need a mentor to guide n judge methods im following
rajeshca911 said:
Your not helpfull??.. I don't agree with that. May be im Not in the position to catch your mind.
However.. Im not going to miss single chance to upgrade myself ( yes ofcourse from devs n seniors like u)
As you said
1) i have installed vcom drivers & fetched scatter file. ( again not from mtk droid tools) . I heard mtkdroid tools nOt fully supporting mt67xx Series. Even i tried modified mtkdroid tools developed by dev havoc.. And droid tool showed some info like cpu info.. Etc. But right hand side there was an error which saying that its usable to fetch info. . I presume the error may b causing by oppo. Own OS ( Color OS based on android 6.0).. And my last try was 2 months ago. So i dont know if there is any improvements in droid tools or not. Please privide me links if they updated/ supported 67xx series
2)yes i agree with mount points you mentioned. I was just replacing fstab file from stock to. Port. I didnt edit any. . I will check again and update u.
3) Actually im in dilemma to blame on cimpiling or flashing.. The device is not booting even i didn't modify any item after repack. I need solution for that. If that resolved... Automatically everything will b set up by themselves.. Pls share any views regarding this..
I know its difficult to u to guide until u have hands on it or personally seen d procedures & results
I may upload videos / pictures/ share Team viewer etc.. if u want to see it personally.. So.. U can better understand my problem , my flaws where i need to b improved ( onlynif u wish) however i need a mentor to guide n judge methods im following
Click to expand...
Click to collapse
I empathize with your frustration.
Truth is that with the devices which have not caught the fancy of developers, not having proven root methods, custom recovery, etc only, we take initiatives ourselves and learn the things the hard way which is essentially a true way learning. With popular devices having already so many developments, there is no scope for adventurism and fun as well.
Just see back what are all you gained in doing the things you did with your device for gaining root. Could it have been possible with the so called popular devices?
Now let's come to the issue. In all times of failed booting on compiled imgs, how did you restore them? flashing again stock boot and recovery imgs? and with tools you mentioned?
If you could flash stock boot and recovery with the tools you mentioned, then there is no problem with those flashing tools. Then it comes to the decompiling and recompiling of imgs.
If it could be possible, can you share here stock boot.img, and custom recovery you have selected for porting (also mention the device name, recovery pertained). Let me try.
Yup.. Bro.
What have you said all true.. during this journey i have learned so manythings like porting custom recovery , read back firmware etc and i cant forget what i have learned.. so many trail and errors
below link is the stock and custom recovery i tried to port
https://drive.google.com/file/d/0B6wWbhnrRZ_-V2RZQXByYjc4QVU/view?usp=drive_web
and a developer also tried to to port recovery for me .. below is the link which he modified for me
https://www.androidfilehost.com/?fid=745425885120760137
Im also enclosing stock boot.img
https://mega.nz/#!MF1ySQ4D!ku6RWfOP8QTkm75sNq_1_n-_Af0y843J0I0tiCHRa8k
My Device Details are
Manufacture : Oppo
Device name : Oppo f3
Model No : CPH1609
chipset : MT6750T , 4gb Ram , 64 Gb storage
[ I Really praying Inside ....:angel: god may give result for our endless efforts }
@rajeshca911 can you give details for the custom recovery you have given links, like name of the device, its os ( lollipop, marshmallow, like), and chipset if possible, it pertained to.
shankar_vl said:
@rajeshca911 can you give details for the custom recovery you have given links, like name of the device, its os ( lollipop, marshmallow, like), and chipset if possible, it pertained to.
Click to expand...
Click to collapse
Aquired custom recovery from
Device : qukitel K6000 plus, chipset MT6750T
android version 6.0 (from below)
https://www.google.co.in/amp/s/foru...al/oukitel-k6000-plus-twrp-root-t3620241/amp/
rajeshca911 said:
Aquired custom recovery from
Device : qukitel K6000 plus, chipset MT6750T
android version 6.0 (from below)
https://www.google.co.in/amp/s/foru...al/oukitel-k6000-plus-twrp-root-t3620241/amp/
Click to expand...
Click to collapse
I think the signature of the boot.img gets changed. Try to sign it after decompiling and recompiling by AVB patcher from here: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
anandverma458 said:
I think the signature of the boot.img gets changed. Try to sign it after decompiling and recompiling by AVB patcher from here: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Click to expand...
Click to collapse
Shall i sign both boot.img and recovery.img as well?? or is it enough to sign compiled recovery.img ?
---------- Post added at 07:57 AM ---------- Previous post was at 07:44 AM ----------
i generated public and private keys also signed and generated
boot_signed.img
recovery_signed.img
first i flashed both the images... result was soft brick and i had to flash original boot.img
second i flashed only signed recovery.img and same was repeated.
rajeshca911 said:
Shall i sign both boot.img and recovery.img as well?? or is it enough to sign compiled recovery.img ?
---------- Post added at 07:57 AM ---------- Previous post was at 07:44 AM ----------
i generated public and private keys also signed and generated
boot_signed.img
recovery_signed.img
first i flashed both the images... result was soft brick and i had to flash original boot.img
second i flashed only signed recovery.img and same was repeated.
Click to expand...
Click to collapse
Actually, I had the same problem (I have vivo 1603). When I flashed boot.img after decompiling and recompiling,it bootlooped. I had twrp installed, so I first restored the backup of stock boot.img, and then installed the recompiled boot.img without rebooting. That worked for me
As you don't have custom recovery, I suggest that you first flash stock boot.img, and after the process completes, flash the recompiled boot.img without rebooting your device.
Hey bro, I decompiled the stock boot.img to see that if 'verify' flag was preventing booting the system with other than stock recovery. Dm-verity is a recent security control for preventing booting with changed/modified kernel/system. But I could not find any such flags, but found verity_key, so I just deleted it and decompiled the boot.img. I am not sure whether it can solve your booting problem. Let's see will this now allow to boot with custom kernel. Here is the modified stock boot.img. http://www.mediafire.com/file/tc1k1ghmy76nfqd/modified_oppo_boot.img
Flash first this boot.img and then flash the custom recovery.imgs (you can try your recoveries also)
I have also ported two recovery.imgs. Both are ported from the twrps for the same device, K6000 plus. However, what I found for this k6000 plus was different in size. So I ported two twrp recovery imgs. Here are two twrp ported recoveries, one is from you have given links to and another is from what I found on this forum.
http://www.mediafire.com/file/4als7qmpwdz1iv4/oppo_port_twrpv1.img
http://www.mediafire.com/file/5xz7387at6rr0dy/oppo_port_twrpv2.img
Once again, I reiterate that first flash the modified boot.img and then try flashing the recoveries.
Best of luck
anandverma458 said:
Actually, I had the same problem (I have vivo 1603). When I flashed boot.img after decompiling and recompiling,it bootlooped. I had twrp installed, so I first restored the backup of stock boot.img, and then installed the recompiled boot.img without rebooting. That worked for me
As you don't have custom recovery, I suggest that you first flash stock boot.img, and after the process completes, flash the recompiled boot.img without rebooting your device.
Click to expand...
Click to collapse
Bro thanks for your advice.. and i did same what you have said.. i flashed stock boot.img with out rebooting flashed recompiled boot.img the device didnt boot up.. i think culprit is something else .. that prevets booting custom images
I'm thinking of getting a 30 Ultra the next week, as I'm very disappointed with my OnePlus 10 Pro and the way OnePlus is heading.
I've been an OnePlus user since the 6 and never had a Motorola before, but the 30 Ultra really fascinates me.
Before I buy it I only wanted to ask how the modding community for motorola is.
Is Magisk easily installable with Motorola devices? Anything I should keep in mind with unlocking the bootloader / rooting of a motorola?
Thank's in advance
I didn't have any problems rooting my edge 30 ultra. I had to wait about 2-3 days for the OEM unlocking option to be activated in the developer options, but other than that it was smooth sailing.
Unlock bootloader, obtain stock boot image by for example using the Lenovo Rescue and Smart Assistant, patch the boot image in the magisk app, and then flash it.
You should keep in mind that it's extremely dangerous if not impossible to relock the bootloader again. In theory you have to flash the stock firmware and thoroughly delete all data and custom settings but a lot of people end up with bricked devices.
Killuminati91 said:
You should keep in mind that it's extremely dangerous if not impossible to relock the bootloader again. In theory you have to flash the stock firmware and thoroughly delete all data and custom settings but a lot of people end up with bricked devices.
Click to expand...
Click to collapse
Yes, it's true.
But i big problem in poland, because customer write to unlock bootlader code = warranty is out.
I this method broken my Moto G82
Killuminati91 said:
You should keep in mind that it's extremely dangerous if not impossible to relock the bootloader again. In theory you have to flash the stock firmware and thoroughly delete all data and custom settings but a lot of people end up with bricked devices.
Click to expand...
Click to collapse
Ok so once I root my Motorola, I can't go back to unrooted, right? Surely not ideal but I rarely unroot my devices once I rooted. But thanks for mentioning!
I'm guessing custom rom/kernel support for this device isn't really a thing right?
No, you can unroot at any time if you uninstall magisk and flash the stock boot.img. But you can't / shouldn't relock the bootloader. I think times are over when a lot of people developed kernels / Roms / TWRP for specific phones. We need more people to take matters into their own hands, the market is flooded with too many different models.
@Killuminati91 any news on twrp for this phone yet?
_Hinnie_ said:
I didn't have any problems rooting my edge 30 ultra. I had to wait about 2-3 days for the OEM unlocking option to be activated in the developer options, but other than that it was smooth sailing.
Unlock bootloader, obtain stock boot image by for example using the Lenovo Rescue and Smart Assistant, patch the boot image in the magisk app, and then flash it.
Click to expand...
Click to collapse
I'd be very thankful if you could share a guide for this
memocatcher said:
Ok so once I root my Motorola, I can't go back to unrooted, right? Surely not ideal but I rarely unroot my devices once I rooted. But thanks for mentioning!
I'm guessing custom rom/kernel support for this device isn't really a thing right?
Click to expand...
Click to collapse
Custom roms / kernels isn't a thing at the moment. It is confirmed however that Motorola will soon release the kernel source code of the Edge 30 Ultra, which can help with custom rom and kernel development (https://github.com/MotorolaMobilityLLC/kernel-msm/issues/445).
memocatcher said:
I'd be very thankful if you could share a guide for this
Click to expand...
Click to collapse
1. Go to Settings -> Developer Options -> Enable OEM Unlocking
2. Reboot the phone to the bootloader, for example using adb reboot bootloader
3. Follow the steps from here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
To root your phone:
1. Install the Magisk app from here: https://github.com/topjohnwu/Magisk/releases
2. Download the boot image from the official firmware, make sure the firmware corresponds with your device (or grab your own using the Lenovo Rescue and Assist tool) https://forum.xda-developers.com/t/...cn-to-edge-30-ultra-eu.4491699/#post-87424851
3. In Magisk: Home -> Install -> Select and Patch a File ->Select the boot.img -> Click LET'S GO
4. Copy the patched boot image from /storage/emulated/0/Downloaded/magisk_patched-xxxx.img to your computer
5. Boot the phone to the bootloader
6. Flash the patched boot image with fastboot flash boot magisk_patched-xxxx.img, or alternatively, if you want to be sure that the boot image boots before flashing it, use fastboot boot magisk_patched-xxxx.img and if it works fine, repeat from step 5.
7. Reboot
_Hinnie_ said:
Custom roms / kernels isn't a thing at the moment. It is confirmed however that Motorola will soon release the kernel source code of the Edge 30 Ultra, which can help with custom rom and kernel development (https://github.com/MotorolaMobilityLLC/kernel-msm/issues/445).
1. Go to Settings -> Developer Options -> Enable OEM Unlocking
2. Reboot the phone to the bootloader, for example using adb reboot bootloader
3. Follow the steps from here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
To root your phone:
1. Install the Magisk app from here: https://github.com/topjohnwu/Magisk/releases
2. Download the boot image from the official firmware, make sure the firmware corresponds with your device (or grab your own using the Lenovo Rescue and Assist tool) https://forum.xda-developers.com/t/...cn-to-edge-30-ultra-eu.4491699/#post-87424851
3. In Magisk: Home -> Install -> Select and Patch a File ->Select the boot.img -> Click LET'S GO
4. Copy the patched boot image from /storage/emulated/0/Downloaded/magisk_patched-xxxx.img to your computer
5. Boot the phone to the bootloader
6. Flash the patched boot image with fastboot flash boot magisk_patched-xxxx.img, or alternatively, if you want to be sure that the boot image boots before flashing it, use fastboot boot magisk_patched-xxxx.img and if it works fine, repeat from step 5.
7. Reboot
Click to expand...
Click to collapse
Thanks a lot!!
TF1920 said:
@Killuminati91 any news on twrp for this phone yet?
Click to expand...
Click to collapse
No success yet and I currently don't have the time to try, sadly. Device tree can be generated with helpers but the whole Linux compiling part is still gibberish to me.
TF1920 said:
@Killuminati91 any news on twrp for this phone yet?
Click to expand...
Click to collapse
I did a tentative build, here are the results: img / zip
This was built with OrangeFox, using my device tree. Feel free to contribute to the repo, I can rebuilt if it doesn't work out of the box.
A disclaimer: I am a noob, and I don't have the device yet to test it, it is quite unlikely that this recovery works on the first attempt.
The prebuilt kernel I am especially unsure about.
arellewen said:
I did a tentative build, here are the results: img / zip
This was built with OrangeFox, using my device tree. Feel free to contribute to the repo, I can rebuilt if it doesn't work out of the box.
A disclaimer: I am a noob, and I don't have the device yet to test it, it is quite unlikely that this recovery works on the first attempt.
The prebuilt kernel I am especially unsure about.
Click to expand...
Click to collapse
I also tried myself to setup a device tree, but haven't been able to extract the prebuilt kernel. That's also why I asked for the kernel source on their github that will hopefully soon be published.
I'll try in a bit and edit this post to see if the recovery boots.
EDIT: Nope, it doesn't boot. After the usual motorola animation the screen goes black, and afterwards boots into system.
logandavid said:
sorry for an off-topic question: What did you hate about Oneplus 10 Pro in particular?
Click to expand...
Click to collapse
I just don't like the way OnePlus is heading, like many users with the 10 Pro. It feels like using an Oppo device honestly and they made it impossible to unbrick your device by encrypting the popular MSM Tool.
After 5 years with OnePlus it's time for me to try something different
_Hinnie_ said:
I also tried myself to setup a device tree, but haven't been able to extract the prebuilt kernel. That's also why I asked for the kernel source on their github that will hopefully soon be published.
I'll try in a bit and edit this post to see if the recovery boots.
EDIT: Nope, it doesn't boot. After the usual motorola animation the screen goes black, and afterwards boots into system.
Click to expand...
Click to collapse
Yes it didn't work for me either
Nope !! , stay where you are, I had One Plus 9 Pro before, the Edge 30 Pro is much better in all aspects, One plus = Oppo, very bad phone.
A few questions;
Do you need to have a sim card installed in the phone during the 7 day wait period until the oem unlock button is available? Can I just connect the phone to wifi and let it sit for a week?,
Do you need some sort of unlock code from Motorola? I read the unlock directions, but to go any further it's asking for an email address and the need to register and account.,
Also what is the main difference between the pro and the ultra? Is it only the 200MP camera?
_Hinnie_ said:
Custom roms / kernels isn't a thing at the moment. It is confirmed however that Motorola will soon release the kernel source code of the Edge 30 Ultra, which can help with custom rom and kernel development (https://github.com/MotorolaMobilityLLC/kernel-msm/issues/445).
1. Go to Settings -> Developer Options -> Enable OEM Unlocking
2. Reboot the phone to the bootloader, for example using adb reboot bootloader
3. Follow the steps from here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
To root your phone:
1. Install the Magisk app from here: https://github.com/topjohnwu/Magisk/releases
2. Download the boot image from the official firmware, make sure the firmware corresponds with your device (or grab your own using the Lenovo Rescue and Assist tool) https://forum.xda-developers.com/t/...cn-to-edge-30-ultra-eu.4491699/#post-87424851
3. In Magisk: Home -> Install -> Select and Patch a File ->Select the boot.img -> Click LET'S GO
4. Copy the patched boot image from /storage/emulated/0/Downloaded/magisk_patched-xxxx.img to your computer
5. Boot the phone to the bootloader
6. Flash the patched boot image with fastboot flash boot magisk_patched-xxxx.img, or alternatively, if you want to be sure that the boot image boots before flashing it, use fastboot boot magisk_patched-xxxx.img and if it works fine, repeat from step 5.
7. Reboot
Click to expand...
Click to collapse
It works for me, thanks~
And is there any way to remount /system or /vendor directory with r/w permission?
solsolhh said:
It works for me, thanks~
And is there any way to remount /system or /vendor directory with r/w permission?
Click to expand...
Click to collapse
This but for me dosn't work if write something there is 0 bytes, if you make it work let us know
Tools:
- Universal Mount System RW (Guide)
-> Fix for Android 12
arellewen said:
I did a tentative build, here are the results: img / zip
This was built with OrangeFox, using my device tree. Feel free to contribute to the repo, I can rebuilt if it doesn't work out of the box.
A disclaimer: I am a noob, and I don't have the device yet to test it, it is quite unlikely that this recovery works on the first attempt.
The prebuilt kernel I am especially unsure about.
Click to expand...
Click to collapse
Kernel Sources now available, if you got the time:
Release MMI-S3SQ32.16-16-28 ยท MotorolaMobilityLLC/kernel-msm
eqs-g push for android 12
github.com