I am looking for a tutorial or some instructions on how to build a recovery with fastbootD apart of it. I come here cause I have the A52S and there was a fastbootD recovery available to install some firmwards and gsi's What I want is to build one for my S6 Lite tablet with doesn;t have fastboot in the recovery. Hope there is some good information that someone has that can be shared on how to make the recovery with fastbootD in it.... thanks in advance.
You can find the instructions in the repo:
GitHub - ShaDisNX255/Patch-Recovery: CI service that patches recovery.img of Dynamic Samsung devices launched with Android 10 and above to enable fastbootd.
CI service that patches recovery.img of Dynamic Samsung devices launched with Android 10 and above to enable fastbootd. - GitHub - ShaDisNX255/Patch-Recovery: CI service that patches recovery.img o...
github.com
ShaDisNX255 said:
You can find the instructions in the repo:
GitHub - ShaDisNX255/Patch-Recovery: CI service that patches recovery.img of Dynamic Samsung devices launched with Android 10 and above to enable fastbootd.
CI service that patches recovery.img of Dynamic Samsung devices launched with Android 10 and above to enable fastbootd. - GitHub - ShaDisNX255/Patch-Recovery: CI service that patches recovery.img o...
github.com
Click to expand...
Click to collapse
Thanks, will look at today!
Edit: was able to fumble around and got the recovery built yay. Never used github for that kind of thing before, just to download other peoples works.... will play around as I am sure I'll need to make another recovery when there is an update to firmware for the tablet. thanks again for the link...
@ShaDisNX255 this method is great once I got it figured out. Would be nice if there was a script to build twrp.... but I'm sure it's a bit more complicated after all. At least from what I've seen on a couple of github trees for twrp builds...
bobfrantic said:
@ShaDisNX255 this method is great once I got it figured out. Would be nice if there was a script to build twrp.... but I'm sure it's a bit more complicated after all. At least from what I've seen on a couple of github trees for twrp builds...
Click to expand...
Click to collapse
TWRP build instructions are in the device tree README.
BlackMesa123 said:
TWRP build instructions are in the device tree README.
Click to expand...
Click to collapse
thanks but after looking at that information, It's a bit over my head for now... LOL
bobfrantic said:
thanks but after looking at that information, It's a bit over my head for now... LOL
Click to expand...
Click to collapse
There's a GitHub Actions workflow you can try (https://github.com/azwhikaru/Action-Recovery-builder), I didn't test it but it looks promising
BlackMesa123 said:
There's a GitHub Actions workflow you can try (https://github.com/azwhikaru/Action-Recovery-builder), I didn't test it but it looks promising
Click to expand...
Click to collapse
looks interesting indeed, thanks...
bobfrantic said:
looks interesting indeed, thanks...
Click to expand...
Click to collapse
Is there something specific you need built? I'm more than happy to fire up my compilation enviroment and build something (assuming that it isn't something like a whole rom )
screen said:
Is there something specific you need built? I'm more than happy to fire up my compilation enviroment and build something (assuming that it isn't something like a whole rom )
Click to expand...
Click to collapse
i was wanting to build a twrp recovery for my S6 Lite 2022 SM-P916, but a bit over my ability LOL
bobfrantic said:
i was wanting to build a twrp recovery for my S6 Lite 2022 SM-P916, but a bit over my ability LOL
Click to expand...
Click to collapse
SM-P916 doesn't give me the model you said when typed into google (no models at all even), are you sure that that's the correct model number?
Edit: I found the correct model number. I think you meant either SM-P613 (wifi) or SM-P619 (wifi/lte)
Edit2: are you sure that Fastbootd (or regular old fastboot) is not working like on the A52s? Try enabeling adb in Developer Options and issue the command 'adb reboot fastboot' and if that doesn't work try 'adb reboot recovery' to see if that one does work.
also: https://www.howtoreset.org/samsung-galaxy-tab-s6-lite-2022-fastboot-mode/
screen said:
SM-P916 doesn't give me the model you said when typed into google (no models at all even), are you sure that that's the correct model number?
Edit: I found the correct model number. I think you meant either SM-P613 (wifi) or SM-P619 (wifi/lte)
Edit2: are you sure that Fastbootd (or regular old fastboot) is not working like on the A52s? Try enabeling adb in Developer Options and issue the command 'adb reboot fastboot' and if that doesn't work try 'adb reboot recovery' to see if that one does work.
also: https://www.howtoreset.org/samsung-galaxy-tab-s6-lite-2022-fastboot-mode/
Click to expand...
Click to collapse
i have fastbootD in recovery. I followed the instructions from this post:
FastbootD recovery tutorial please
I am looking for a tutorial or some instructions on how to build a recovery with fastbootD apart of it. I come here cause I have the A52S and there was a fastbootD recovery available to install some firmwards and gsi's What I want is to build...
forum.xda-developers.com
and my mistake, SM-P619
bobfrantic said:
i have fastbootD in recovery. I followed the instructions from this post:
FastbootD recovery tutorial please
I am looking for a tutorial or some instructions on how to build a recovery with fastbootD apart of it. I come here cause I have the A52S and there was a fastbootD recovery available to install some firmwards and gsi's What I want is to build...
forum.xda-developers.com
and my mistake, SM-P619
Click to expand...
Click to collapse
Oh, after looking through the git repo mentioned in that post I think I am starting to connect the dots. You currently have the sammy default recovery patched and installed, and now you want to modify and 'build' twrp to include the fastbootd daemon for this device? Cuz that is completely unnecessary, fastbootd has been implemented into twrp since oct 21 2020 (according to the git enviroment of the developers).
All you would need to do to enable fastbootd is reboot to the bootloader/fastboot from within twrp (at least I think, I cannot test this currently as my daily driver (A52s) is still vanilla OneUI with untripped knox fuse, and will stay like this untill it's out of warranty and I don't have any of my old devices with twrp installed on me )
If I am completely wrong about what you are trying to accomplish, please elaborate d;
screen said:
Oh, after looking through the git repo mentioned in that post I think I am starting to connect the dots. You currently have the sammy default recovery patched and installed, and now you want to modify and 'build' twrp to include the fastbootd daemon for this device? Cuz that is completely unnecessary, fastbootd has been implemented into twrp since oct 21 2020 (according to the git enviroment of the developers).
All you would need to do to enable fastbootd is reboot to the bootloader/fastboot from within twrp (at least I think, I cannot test this currently as my daily driver (A52s) is still vanilla OneUI with untripped knox fuse, and will stay like this untill it's out of warranty and I don't have any of my old devices with twrp installed on me )
If I am completely wrong about what you are trying to accomplish, please elaborate d;
Click to expand...
Click to collapse
I would like to build a TWRP from scratch actually. Not just for the fastboot aspect but also to be able to install modules and magisk without having to patch the boot.img mainly... and all other things possible with TWRP.
Related
Okay here we go,
Thanks @pikeylfc for testing. :good:
Rootable Permissive Verity/RIC disabled.
Marvelous Super-Huge Thanks to
@AndroPlus for his kernel source
and helping me out with the kernel.elf situation.
This is in line with AndroPlus's sources at the time I cloned and compiled originally 9th March 2016 for the Z5 premium.
The kernel souce is the same for this device, the kernel was compiled last night.
Download
sxz3plus_ivy_MM_Rootable_Permissive_boot.img
It seems the dsds model may not be unlockable at least in one instance so far.
I'm going to leave this image in place however.
sxz3plus_ivy_dsds_MM_Rootable_Permissive_boot.img
This is for Marshsmellow, it's not rocket-science.
flash by normal means
This image is setup with the bootrec scenario. That information is covered in AndroPlus work and threads.
My defconfigs are attached.
Use @Chainfire 's latest SuperSU, this version will apply root to the boot.img (system-less root).
I do not intend any further effort outside of this.
ATTENTION: I don't have a recovery build for ivy. I don't own the device. The only reason i sorted the kernel for root is because the kernel source is the same from the z3+/z4 to the z5.
Someone who owns the device will have to start picking up proper development. Sorry.
I am still looking for confirmation as to whether or not the bootloader for the dsds model is unlockable, or if there is
some sort of country restriction that applies.
m
The size is like almost 50% of the previous boot-251. Is it correct, wondering why size shrink so much.
30920704 Sep 12 2015 boot-251.img
16293888 Mar 14 14:20 sxz3plus_ivy_MM_Rootable_Permissive_boot.img
Can you confirm the steps?
# Get into flastboot download mode
fastboot flash boot sxz3plus_ivy_MM_Rootable_Permissive_boot.img
fastboot boot recovery.twrp.2.8.7.0.img
in TWRP, flash SuperSU-v2.66.zip
reboot system
krusir said:
The size is like almost 50% of the previous boot-251. Is it correct, wondering why size shrink so much.
30920704 Sep 12 2015 boot-251.img
16293888 Mar 14 14:20 sxz3plus_ivy_MM_Rootable_Permissive_boot.img
Can you confirm the steps?
# Get into flastboot download mode
fastboot flash boot sxz3plus_ivy_MM_Rootable_Permissive_boot.img
fastboot boot recovery.twrp.2.8.7.0.img
in TWRP, flash SuperSU-v2.66.zip
reboot system
Click to expand...
Click to collapse
Yes that's what I did
krusir said:
The size is like almost 50% of the previous boot-251. Is it correct, wondering why size shrink so much.
Click to expand...
Click to collapse
k,
hi, instead of the "usual" kernel binary + dtb image
this package uses a compressed and concatenated kernel-dtb.
So where the "usual" setup results in a 20+mb kernel binary and a 700+kb - 2mb dt.img [depending]
the resulting image-dtb.gz generated during kernel compilation comes down to roughly 8.3mb total.
And since the ramdisk itself is largely text files with few small compiled binaries in sbin, the ramdisk itself
can be compressed from 13.1mb, uncompressed in this case, down to 6.9mb with gzip compression.
With lzma compression the ramdisk would be 2.8mb
m
Super. Install went perfect. Works as expected. Also flashed -arm64-custom-build-by-wanam-20160211.zip
Gravity works fine. I only tried few mods I used regularly.
Thanks for getting is available. I've been keep searching for past few days since upgrade.
Sent from my E6553 using Tapatalk
krusir said:
The size is like almost 50% of the previous boot-251. Is it correct, wondering why size shrink so much.
30920704 Sep 12 2015 boot-251.img
16293888 Mar 14 14:20 sxz3plus_ivy_MM_Rootable_Permissive_boot.img
Can you confirm the steps?
# Get into flastboot download mode
fastboot flash boot sxz3plus_ivy_MM_Rootable_Permissive_boot.img
fastboot boot recovery.twrp.2.8.7.0.img
in TWRP, flash SuperSU-v2.66.zip
reboot system
Click to expand...
Click to collapse
Hi, I'm a noob regarding root on the Z3+ so I would be very grateful if someone could explain a bit more detailed who this installation should be carried out?
I never rooted my device on lollipop, but I guess that in order to be able to flash this kernel, the bootloader must first be unlocked?
I assume that the procedure has not changed because of the update to MM, so i guess I could find the steps somewhere here in the Z3+/Z4 forum (of course if you want to explain those steps as well I wont protest )
Thanks in advance,
Andreas
Thank you so much! Now I finally got the iOS emojis ♥
Install was easy, boot time was same as normal!
bobboviking said:
Hi, I'm a noob regarding root on the Z3+ so I would be very grateful if someone could explain a bit more detailed who this installation should be carried out?
I never rooted my device on lollipop, but I guess that in order to be able to flash this kernel, the bootloader must first be unlocked?
I assume that the procedure has not changed because of the update to MM, so i guess I could find the steps somewhere here in the Z3+/Z4 forum (of course if you want to explain those steps as well I wont protest )
Thanks in advance,
Andreas
Click to expand...
Click to collapse
Andreas,
provided your device is single sim, just flash the img as normal using fastboot. As per OP this is for the MM firmware release.
If your device is dual sim [dsds] let me know and i will post a dsds version AFTER you post the kernel.sin image from the ftf firmware archive for your device.
NO MEGA! DIE CLOUD DIE !!
m
Its not that complicated, but yes, your bootloader must be unlocked. Once you have that sorted, just use flashtool to flash the firmware (you can download the one you want from within flashtool using xperifirm) by installing fastboot and flashmode drivers (those are in the folder you installed flashtool; on anything above Win8 youll need to turn off driver verification to install these drivers, just google that if you dont know how it works), then choosing flashmode, selecting the firmware and falshing it. If you want to do a clean install, just check all the Wipe settings. Two questions will come up while flashing, just click yes on both.
Then you put the phone into fastboot mode (oh and have supersu on the SD card helps) and once again using flashtool, flash the img file from this thread. Then hotboot into the bootable TWRP, found in some other thread here. The phone will restart into TWRP and there you choose install and install the superSU.zip you copied to your SD card before.
If you dont understand parts of what I said, reconsider if youre really so much into gaining root OR ask
Oh gosh. Do I need to unlock my phone first? Mine is dual sim, I'll post the kernel tomorrow, it's 2 a m here, sorry.
alexander43c said:
Oh gosh. Do I need to unlock my phone first? Mine is dual sim, I'll post the kernel tomorrow, it's 2 a m here, sorry.
Click to expand...
Click to collapse
Good deal :good:
I was waiting for someone with a dsds model to respond.
Again, post it to where i can get it.
NO MEGA! DIE CLOUD DIE !!
m
And yes, always now and forever, you will need to unlock your bootloader.
works perfect here! finally marshmallow, root and xposed! thank you very much !!!
oh and drmrestore.zip also works great! much better camera pictures, x-reality works etc! i'm really excited
Anyone else with system storage being shown as 16 GB?
moonbutt74 said:
Good deal :good:
I was waiting for someone with a dsds model to respond.
Again, post it to where i can get it.
NO MEGA! DIE CLOUD DIE !!
m
And yes, always now and forever, you will need to unlock your bootloader.
Click to expand...
Click to collapse
Here you go.
is gg driver ok by the way?
https://drive.google.com/open?id=0B80b07NYd46FYU5HWEdtaXoydm8
You need to set the sharing option!!!
moonbutt74 said:
You need to set the sharing option!!!
Click to expand...
Click to collapse
I've done that after you tried to get the link. Sorry for the inconvenience. I'll check it again
Sent from my E6533 using Tapatalk
And now you need to post the correct link!!!
alexander43c said:
I've done that after you tried to get the link. Sorry for the inconvenience. I'll check it again
Sent from my E6533 using Tapatalk
Click to expand...
Click to collapse
Okay good :good:
What is the device codename and model number?
derp nevermind , i have too much going on at once xD
moonbutt74 said:
Okay good :good:
Click to expand...
Click to collapse
https://drive.google.com/open?id=0B80b07NYd46FYU5HWEdtaXoydm8
here you are
Here are the binaries for fastboot you can use on your device. The reason I'm posting them here is because they can really useful if you happen to flash something wrong while on the go. You need another device to connect to via USB to use them.
I cant really post source because I didn't keep it, since I compiled in aosp env, but I can explain how to compile them if anyone really wants. I did made these a while ago but I never tested them until I had to today, because I flashed a kernel while waiting in line behind the 4 slowest human beings in existence at Walmart. To my surprise, it worked I figured I'd have to add a USB library like I had to for adb, but apparently not.
Normally I wouldn't bother posting these, but our device is so finicky that I figure someone else might need them at some point. I didn't change any of the source code of fastboot from the 8.1 branch.
Download : https://androidfilehost.com/?fid=673791459329068348
Reshare or do whatever you want with them.
Make sure pixel 2 is the device that gets the direct USB-C connection.
Finally, don't be dumb with them, act like an adult, and if you get errors there's a good chance I'm not going to go back to fix them so post the relevant line in code that leads to whatever error you get if you want me to help or look at it.
Very cool!
You people flashing things on-the-go which can potentially render your device inoperable until you get fastboot access confuse me haha. But I guess that's JustXDAThings.
Just watch what you flash and use anykernels, not boot images. The Pixel 2 bootchain isn't as fragile as you think once you flash TWRP into the ramdisk. Protect TWRP and you'll hopefully never need to fastboot from a companion device.
MishaalRahman said:
You people flashing things on-the-go which can potentially render your device inoperable until you get fastboot access confuse me haha. But I guess that's JustXDAThings.
Click to expand...
Click to collapse
YOLO.
The way I see it, there are two kinds of developers, the kind that need testers because they have no idea what they're doing, and the kind that test themselves, because they are the only ones that know what they're doing.
I'm about to yolo flash a taimen build I just made, it will most likely fail, but that log and debug info I get from it will be valuable lol.
Good on you to carry around 2 phones though. I ain't got that luxury. Haha so I'm still screwed.
jlee08517 said:
Good on you to carry around 2 phones though. I ain't got that luxury. Haha so I'm still screwed.
Click to expand...
Click to collapse
Well anything that has an arm arm64 arch, like tablets and chromebooks would work too. So it's just convenient, ironically there's code for tcp connections in fastboot, so that's interesting...
Surge1223 said:
Well anything that has an arm arm64 arch, like tablets and chromebooks would work too. So it's just convenient, ironically there's code for tcp connections in fastboot, so that's interesting...
Click to expand...
Click to collapse
I had a device that made use of that fastboot over tcp protocol ;p
Moto G3 Prototype. Comically, it was actually a boot mode with an extended LK (as in when I used a non-proto boot image, the feature was not operable).
The ARM version doesn't seem to work. I get "illegal instruction" no matter what command I try to use.
TheSt33v said:
The ARM version doesn't seem to work. I get "illegal instruction" no matter what command I try to use.
Click to expand...
Click to collapse
@TheSt33v
I've got an older armeabi build that should work for you. Check my Odds and Ends thread, or grab it from the Magisk Modules repo.
osm0sis said:
@TheSt33v
I've got an older armeabi build that should work for you. Check my Odds and Ends thread, or grab it from the Magisk Modules repo.
Click to expand...
Click to collapse
Is it new enough that it will flash the Pixel 2 XL? It doesn't work with older versions.
TheSt33v said:
Is it new enough that it will flash the Pixel 2 XL? It doesn't work with older versions.
Click to expand...
Click to collapse
Well you can try, but probably not then. You'll just need to use a newer device as the host device to flash from.
@Surge1223 I realize this is an older thread but I'm going to ask anyways because after searching around, most I can find are x64 files. I've ordered an arm based Chromebook, am I correct in that this is what's needed to get fastboot and adb working? Thanks
@Surge1223
Just wondering if there's any chance of getting this updated?
The current version is broken, at least, on the Pixel 3. Just tried to use my old Nexus 5X to Update my Pixel with the January update. Going to be computer-less for a while starting next week and was hoping I could use the Nexus for updates.
I bypassed the version check in the flash-all.sh file and tried to run it. Bootloader and radio updated fine. But system (along with product and vendor) were a complete no go. Boot image also updates just fine.
Basically I suspect any simple flashes will work, other than that - nope.
At least it didn't brick the device in any way. I ended up with a December system, vendor, and product along with an updated modem, bootloader, and Magisk patched kernel which all booted fine. Normal update via computer worked so at least I'm good for this month.
Not expecting anything, just hoping maybe you'll update this sometime in the near future.
Thanks for your consideration.
jcmm11 said:
@Surge1223
Just wondering if there's any chance of getting this updated?
The current version is broken, at least, on the Pixel 3. Just tried to use my old Nexus 5X to Update my Pixel with the January update. Going to be computer-less for a while starting next week and was hoping I could use the Nexus for updates.
I bypassed the version check in the flash-all.sh file and tried to run it. Bootloader and radio updated fine. But system (along with product and vendor) were a complete no go. Boot image also updates just fine.
Basically I suspect any simple flashes will work, other than that - nope.
At least it didn't brick the device in any way. I ended up with a December system, vendor, and product along with an updated modem, bootloader, and Magisk patched kernel which all booted fine. Normal update via computer worked so at least I'm good for this month.
Not expecting anything, just hoping maybe you'll update this sometime in the near future.
Thanks for your consideration.
Click to expand...
Click to collapse
Yeah new devices use fastbootd to update vendor system product vbmeta and dtbo, I'll try to update it soon, I'll try to hook it up before next week for ya though.
Surge1223 said:
Yeah new devices use fastbootd to update vendor system product vbmeta and dtbo, I'll try to update it soon, I'll try to hook it up before next week for ya though.
Click to expand...
Click to collapse
I normally wouldn't ask, and if you can't (for whatever reason) that's fine. But you did say you'd try to get this updated. New security patches are due out Monday and it would be real nice if I could apply them ?
If not, I'll live. Thanks, no matter what.
Surge1223 said:
Here are the binaries for fastboot you can use on your device. The reason I'm posting them here is because they can really useful if you happen to flash something wrong while on the go. You need another device to connect to via USB to use them.
I cant really post source because I didn't keep it, since I compiled in aosp env, but I can explain how to compile them if anyone really wants. I did made these a while ago but I never tested them until I had to today, because I flashed a kernel while waiting in line behind the 4 slowest human beings in existence at Walmart. To my surprise, it worked I figured I'd have to add a USB library like I had to for adb, but apparently not.
Normally I wouldn't bother posting these, but our device is so finicky that I figure someone else might need them at some point. I didn't change any of the source code of fastboot from the 8.1 branch.
Download : https://androidfilehost.com/?fid=673791459329068348
Reshare or do whatever you want with them.
Make sure pixel 2 is the device that gets the direct USB-C connection.
Finally, don't be dumb with them, act like an adult, and if you get errors there's a good chance I'm not going to go back to fix them so post the relevant line in code that leads to whatever error you get if you want me to help or look at it.
Click to expand...
Click to collapse
Sorry for bumping an old thread but would you be willing to explain how to compile or upload the fastboot and adb binaries of the latest platform tools? I have a PineBookPro that's running arm64 architecture and was looking for them in the repos but the ones I could find were for api23 and would very much like api30 so I could revive my old p2xl. Thank you for your contribution.
Fe Mike said:
Sorry for bumping all old thread but would you be willing to explain how to compile or upload the fastboot and adb binaries of the latest platform tools? I have a PineBookPro that's running arm64 architecture and was looking for them in the repos but the ones I could find were for api23 and would very much like api30 so I could revive my old p2xl. Thank you for your contribution.
Click to expand...
Click to collapse
Not sure if this helps...I'm on the newest version of Platform tools, I have a pixel 2 xl and have no issues.
cubzfan68 said:
Not sure if this helps...I'm on the newest version of Platform tools, I have a pixel 2 xl and have no issues.
Click to expand...
Click to collapse
It may, are you using fastboot from op on the phone from another arm device or a PC?
Fe Mike said:
It may, are you using fastboot from op on the phone from another arm device or a PC?
Click to expand...
Click to collapse
I use it from a pc
DisclaimerThis software comes wth no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device.
Note: Currently Oreo 8.1 custom roms are not supported,only stock EMUI 8.x .
Download and Installation
* Download twrp recovery
* Start your device in fastboot mode
* Install the recovery using the following command:
Code:
fastboot flash recovery_ramdisk [filename].img --> ex: fastboot flash recovery_ramdisk twrp_honor9_lite_0.1.img
* Restart with this command:
Code:
fastboot reboot
* As soon as you execute the restart command,remove the USB cable and keep pressing Volume UP,so the device will boot to TWRP.This is to avoid that the device boot to OS,overwritting TWRP recovery.
Features
Internal storage decryption = working
MTP and OTG connection = working
Backup&Restore = working
Note: There are no sources for this yet,because is based on the work of @zxz0O0 ,from Honor 9.
Contributors
**** Pretoriano80
**** zxz0O0 - This wouldn't be possible without this guy,so big big thank to him.I used his base to make this recovery work.Thank again buddy!
**** TeamWin project ,obviously.
**** @Blackball
**** @JamesBott - for testing on Honor 9 Lite
**** Team OpenKirin - thanks for the "Oem Path wipe esclusion" code
**** Anyone that somehow contributed to this project
Download links
twrp_honor9_lite_0.1.img - initial release
twrp_honor9_lite_0.2_test.img - test build ,possible fix for unencrypted devices (stock or custom roms).
thanks
would u add link for stock recovery for LLD-AL10 8.0.0.160(C675)
thanks for the twrp recovery. I used Honor 7x recovery it worked well in my 9 Lite. i will try this.
kdark said:
thanks
would u add link for stock recovery for LLD-AL10 8.0.0.160(C675)
Click to expand...
Click to collapse
Already its here https://forum.xda-developers.com/showpost.php?p=76186952&postcount=2
@kdark can u please pull your system.img from ur phone and give it to me. Because i messed with my phone. No i didnt receive that AR Lens update.(I received it , when i install it failed becoz of root. Now after unrooting completely . my device shows no update :crying: )
VigneshS007 said:
thanks for the twrp recovery. I used Honor 7x recovery it worked well in my 9 Lite. i will try this.
Already its here https://forum.xda-developers.com/showpost.php?p=76186952&postcount=2
@kdark can u please pull your system.img from ur phone and give it to me. Because i messed with my phone. No i didnt receive that AR Lens update.(I received it , when i install it failed becoz of root. Now after unrooting completely . my device shows no update :crying: )
Click to expand...
Click to collapse
tell me how to do it.
i will try
kdark said:
tell me how to do it.
i will try
Click to expand...
Click to collapse
take twrp system.img backup and plz upload. i will try to restore in my phone..
@Pretoriano80 thanks a lot, this is the first thing i'll try after i get my bootloader unlocked. I contacted Huawei for the unlock code as the page where to get it is down.
VigneshS007 said:
@kdark can u please pull your system.img from ur phone and give it to me. Because i messed with my phone. No i didnt receive that AR Lens update.(I received it , when i install it failed becoz of root. Now after unrooting completely . my device shows no update :crying: )
Click to expand...
Click to collapse
Maybe this could help you, stock firmwares for the Honor 9 Lite. Be carrefull i haven't tried them myself and i don't know how to flash them (just found out yesterday).
http://huawei-firmware.com/?load_page=search&q=LLD-L31&page=1
ROO3VER said:
@Pretoriano80 thanks a lot, this is the first thing i'll try after i get my bootloader unlocked. I contacted Huawei for the unlock code as the page where to get it is down.
Maybe this could help you, stock firmwares for the Honor 9 Lite. Be carrefull i haven't tried them myself and i don't know how to flash them (just found out yesterday).
http://huawei-firmware.com/?load_page=search&q=LLD-L31&page=1
Click to expand...
Click to collapse
my device is LLD-AL10 C675 (Indian Version). So i need that only.
VigneshS007 said:
my device is LLD-AL10 C675 (Indian Version). So i need that only.
Click to expand...
Click to collapse
Somehow i posted the link for LLD-L31, here is the link to other types aswell:
http://huawei-firmware.com/?load_page=search&q=Honor+9+lite+&page=1
I can see only one package for your version and it's only 110 mb so i don't know it has any use for you.
ROO3VER said:
Somehow i posted the link for LLD-L31, here is the link to other types aswell:
http://huawei-firmware.com/?load_page=search&q=Honor+9+lite+&page=1
I can see only one package for your version and it's only 110 mb so i don't know it has any use for you.
Click to expand...
Click to collapse
yes, its OTA. i need Latest OTA which has AR Lens feature and May Security Patch.
VigneshS007 said:
yes, its OTA. i need Latest OTA which has AR Lens feature and May Security Patch.
Click to expand...
Click to collapse
I'm afraid these are the only ones there, maybe it's still to come ?
ROO3VER said:
@Pretoriano80 thanks a lot, this is the first thing i'll try after i get my bootloader unlocked. I contacted Huawei for the unlock code as the page where to get it is down.
Click to expand...
Click to collapse
where can i contact them to get the unlock code?
if the honor homepage for bootloader unlock code down - you can use dc-unlocker
i pay for my last bootloader unlock code 4€, for my last FRP unlock 15€
daxter19 said:
where can i contact them to get the unlock code?
Click to expand...
Click to collapse
Search for your local service center email
JamesBott said:
if the honor homepage for bootloader unlock code down - you can use dc-unlocker
i pay for my last bootloader unlock code 4€, for my last FRP unlock 15€
Click to expand...
Click to collapse
Why pay for it when you can get it for free?
@vayavalla
hi,
if i need bootloader unlock code : first use huawei/honor homepage "bootloader unlock". if i can not connect this page (wait-time 1..2 days) i pay dc-unlocker.
this work all time ! that's all.
if in the future from huawei/honor NO bootloader unlock code available - i go with my money to another factory.
daxter19 said:
where can i contact them to get the unlock code?
Click to expand...
Click to collapse
I just tapped the e-mail link on their website and asked for it.
Today i recived a e-mail in witch they asked for info they need to get the code like device-ID, IMEI,... and why i need the code.
Now i'm waiting for it, hopefully i get it tomorrow.
Pretoriano80 said:
Download links
twrp_honor9_lite_0.1.img - initial release
twrp_honor9_lite_0.2_test.img - test build ,possible fix for unencrypted devices (stock or custom roms).
Click to expand...
Click to collapse
Good afternoon. I have a device Huawei p Smart analog Honor 9 Lite. this TWRP does not work. But Your another version: the Only problem is to decrypt DATA at each input. If this TWRP to finish cutting-it will be fine. Thank you for your work.
twrp_p_smart_10.img
ROO3VER said:
I just tapped the e-mail link on their website and asked for it.
Today i recived a e-mail in witch they asked for info they need to get the code like device-ID, IMEI,... and why i need the code.
Now i'm waiting for it, hopefully i get it tomorrow.
Click to expand...
Click to collapse
@daxter19, maybe this is not the fastest or easiest way to get the code but bootloader is unlocked.
Thank you for the recovery! So I tested both v0.1 and v0.2 TWRP builds. V0.1 is stuck at the teamwin boot logo. V0.2 works fine but shows internal /sdcard as encrypted. By the way: is there a way that the recovery is not getting overwritten all the time?
kaiomatico said:
Thank you for the recovery! So I tested both v0.1 and v0.2 TWRP builds. V0.1 is stuck at the teamwin boot logo. V0.2 works fine but shows internal /sdcard as encrypted. By the way: is there a way that the recovery is not getting overwritten all the time?
Click to expand...
Click to collapse
* As soon as you execute the restart command,remove the USB cable and keep pressing Volume UP,so the device will boot to TWRP.This is to avoid that the device boot to OS,overwritting TWRP recovery.
kaiomatico said:
Thank you for the recovery! So I tested both v0.1 and v0.2 TWRP builds. V0.1 is stuck at the teamwin boot logo. V0.2 works fine but shows internal /sdcard as encrypted. By the way: is there a way that the recovery is not getting overwritten all the time?
Click to expand...
Click to collapse
version 0.1 worked fine for me. LLD-AL10 . havent tested 0.2
TWRP DIRTY PORT FOR G7 PLAY
My friend was looking to get a G7 Play, so I wanted to whip something up for him really quick. I managed to make a dirty port of TWRP for the G7 Play, taken from the G7 TWRP image since they're the same SDM632 chipset. Until you guys get a real, proper build of TWRP done with the proper source code, consider this a stop gap to at least be able to flash things! It's not perfect obviously but hopefully it's good enough for now!
AS ALWAYS, I DO NOT TAKE RESPONSIBILITY IF FLASHING THIS BRICKS YOUR PHONE. WHAT YOU CHOOSE TO DO TO YOUR PHONE IS ON YOU!!!
WHAT WORKS:
It boots! As you can see here, the G7 Play is in fact running this recovery image just fine
Not sure, don't have the phone to test for myself
WHAT DOESNT WORK:
Because this is a dirty port, the recovery will think this is a G7, when as we all know this is in fact a G7 Play. There is nothing I can really do about this, this is the nature of dirty ports
Not sure, don't have the phone to test for myself
DOWNLOAD:
DOWNLOAD LINK HERE
I cannot provide any source code since this was a dirty port, so no actual source was used. The only things I used to make this were a G7 TWRP image, a G7 Play boot image, and carliv's image kitchen
HOW TO USE:
Reboot to fastboot
Flash the dtbo with fastboot flash dtbo dtbo.img
After that boot from the recovery with fastboot boot recoveryname.img
THANKS TO:
@Alberto97 for the G7 TWRP image I dirty ported from
The G7 Play Telegram group for testing out the image I made, since I don't have a G7 Play to test this on myself. Specifically @noslen7 for testing the image and figuring out how to get it to run (need to flash the dtbo first) and for sending me the image I used above to show it's working and bootable
Carliv for that Carliv Image Kitchen he made, that tool rocks!
I can't test it anymore but if it's uses the same things as the one I built which was inspired by Alberto, do not try to install the TWRP unless you have already flashed the second bank.
fastboot boot recovery.img indeed won't harm so you can try that.
Any idea what works more then the one I built?
Which dtbo.img are we supposed to flash - the one from the stock ROM, or something else?
Great work!
First of all thanks for your hard work. I was really happy to see your post. I have followed the instructions exactly and I got "Failed (too many links)" when it attempted to boot my phone into recovery.
I am using XT1952-4_CHANNEL_RETCA_9.0_PPY29.105-5
Any ideas why it might have failed?
Thanks
jwreidmoto said:
First of all thanks for your hard work. I was really happy to see your post. I have followed the instructions exactly and I got "Failed (too many links)" when it attempted to boot my phone into recovery.
I am using XT1952-4_CHANNEL_RETCA_9.0_PPY29.105-5
Any ideas why it might have failed?
Thanks
Click to expand...
Click to collapse
That's the same one I'm trying to use, tried the dtbo from the same firmware got the same results. Possible EU/Canada firmware as the screenshot of the phone that was shared is in celcius
This is how i boot this recovery successfully
daftshanks said:
That's the same one I'm trying to use, tried the dtbo from the same firmware got the same results. Possible EU/Canada firmware as the screenshot of the phone that was shared is in celcius
Click to expand...
Click to collapse
step 1 fastboot flash dtbo dtbo.img
s000.tinyupload. com/download.php?file_id=26286860633744490329&t=2628686063374449032989765
step 2
fastboot boot "recovery above"
s000.tinyupload. com/download.php?file_id=24332259722784445351&t=2433225972278444535138860
noslen7 said:
step 1 fastboot flash dtbo dtbo.img
s000.tinyupload. com/download.php?file_id=26286860633744490329&t=2628686063374449032989765
step 2
fastboot boot "recovery above"
s000.tinyupload. com/download.php?file_id=24332259722784445351&t=2433225972278444535138860
Click to expand...
Click to collapse
I appreciate your reply on this. However the dtbo filebyou provided is about 3/5ths of the dtbo from my stock firmware, normally they would be at least close to the same file size. Can I ask you what firmware you are on? And were you able to permanently install TWRP? Possible root?
Downloaded dbto.img got same result
I downloaded the above dbto.img and flashed it instead of my own stock dbto.img and got the same result when I tried to boot from recovery - Failed ( too many links). I think the recovery IMG is not working for our Canadian ROM edition.
anybody with XT1952-1 RETEU reading this here, you can help!
https://forum.xda-developers.com/showpost.php?p=79655902&postcount=5
Which dtbo.img to use? In the download area you only have the image of recovery
HOW TO USE:
Reboot to fastboot
Flash the dtbo with fastboot flash dtbo dtbo.img
After that boot from the recovery with fastboot boot recoveryname.img
dbto.img
That was in response to another query. I used my own dbto.img from my stock ROM. That part flashes fine it's the recovery.img that comes back with " failed( too many links) I have a Canadian phone.
Flashing dtbo.img will erase the smartphone data? Will I lose app data?
thank you
it worked for me fine it did give me some problems when i tried booting direct so i flashed to boot then went to recovery mode thru bootloader menu and it worked once in twrp i installed the original boot.img and im good.
Yo I'm coming from the g6 play forum with a quick question. Does this by chance work with the same current root method for the g6 play which is booting in twrp and formatting data to decrypt it then flashing twrp and flashing through twrp the encryption disabler zip then flashing magisk. If someone is able to confirm that I can possibly try to make a decent guide for you guys. We don't have a offical twrp that decrypts on its own and the twrp we have ain't a dirty port so I know there may be some differences when it comes to twrp related issues but it's better than nothing lol
ninjakira said:
Yo I'm coming from the g6 play forum with a quick question. Does this by chance work with the same current root method for the g6 play which is booting in twrp and formatting data to decrypt it then flashing twrp and flashing through twrp the encryption disabler zip then flashing magisk. If someone is able to confirm that I can possibly try to make a decent guide for you guys. We don't have a offical twrp that decrypts on its own and the twrp we have ain't a dirty port so I know there may be some differences when it comes to twrp related issues but it's better than nothing lol
Click to expand...
Click to collapse
There is one significant difference (as it regards rooting) between the Moto G6 Play and the Moto G7 Play. The G7 Play uses the A/B partition index while the G6 Play uses a standard GPT index. The current dilemma with root for the G7 Play involves the A/B partition config. Developer topjohnwu has been notified of this issue on the Magisk support thread, and has stated that he is working on a resolution at present.
Viva La Android said:
There is one significant difference (as it regards rooting) between the Moto G6 Play and the Moto G7 Play. The G7 Play uses the A/B partition index while the G6 Play uses a standard GPT index. The current dilemma with root for the G7 Play involves the A/B partition config. Developer topjohnwu has been notified of this issue on the Magisk support thread, and has stated that he is working on a resolution at present.
Click to expand...
Click to collapse
There has to be more to it than this. There are plenty of devices using A/B partitioning that can be rooted with Magisk. As far as I know, Magisk has supported A/B since version 17.1. Reading through the threads it sounds like more a TWRP problem than a Magisk one.
Has anyone tried patching boot_a and boot_b with Magisk and flashing both at once?
Spaceminer said:
There has to be more to it than this. There are plenty of devices using A/B partitioning that can be rooted with Magisk. As far as I know, Magisk has supported A/B since version 17.1. Reading through the threads it sounds like more a TWRP problem than a Magisk one.
Has anyone tried patching boot_a and boot_b with Magisk and flashing both at once?
Click to expand...
Click to collapse
You try and let's us know
Fdraco10 said:
You try and let's us know
Click to expand...
Click to collapse
I don't have the device otherwise I would. That's why I'm asking if anyone has tried it yet.
Spaceminer said:
I don't have the device otherwise I would. That's why I'm asking if anyone has tried it yet.
Click to expand...
Click to collapse
Yes. I patched both boot_a and boot_b with Magisk v19.3. My device booted into the OS with no problems at all, yet Magisk Manager indicates that root is not installed. Topjohnwu has been notified of the root issue with the Moto G7 Play, and has stated on the Magisk support thread that he is looking into a resolution. It's not a TWRP issue at this point because there is no unofficial or official TWRP for the G7 Play as of yet. Like you, I fully agree this is a bizarre issue. Root strategies which are working on the Moto G7, G7 Power & G7 Plus are not working on the G7 Play. Although Magisk has certainly supported A/B devices for some time now, no universal root method is completely infallible. There are many devices -- both A/B and standard GPT -- that encounter problems with Magisk from time to time. Luckily for the Android community, topjohnwu works hard on resolving any known issues like the one at hand.
Viva La Android said:
Yes. I patched both boot_a and boot_b with Magisk v19.3. My device booted into the OS with no problems at all, yet Magisk Manager indicates that root is not installed. Topjohnwu has been notified of the root issue with the Moto G7 Play, and has stated on the Magisk support thread that he is looking into a resolution. It's not a TWRP issue at this point because there is no unofficial or official TWRP for the G7 Play as of yet. Like you, I fully agree this is a bizarre issue. Root strategies which are working on the Moto G7, G7 Power & G7 Plus are not working on the G7 Play. Although Magisk has certainly supported A/B devices for some time now, no universal root method is completely infallible. There are many devices -- both A/B and standard GPT -- that encounter problems with Magisk from time to time. Luckily for the Android community, topjohnwu works hard on resolving any known issues like the one at hand.
Click to expand...
Click to collapse
I read the responses in his thread about that, and it seems like you guys aren't getting root without a working TWRP. The problem that was laid out, is that fastboot can't patch existing files, it can only overwrite them. Without a custom bootloader, Magisk would never be able to patch existing files through fastboot.
Personally, I think that's a very sh*tty position to be in, and I want to help you guys out. If you or anyone else wants to upload your most recent boot.img, it'll save me some time. I'm not too familiar with the A/B partition setup, but I am very familiar with TWRP. I think that I can get it working for you folks. I will make this happen or break my brain trying. No phone with an unlockable bootloader should go unrooted! Thank you for answering my question by the way. That's one less thing to troubleshoot.
I just want to confirm a few things before I get to work.
Is your base model number xt1952?
Is your code name Channel?
Where is the current TWRP hacked from? (Moto G7, G7 Power, G7 Plus?) - Moto G7. I found it in the OP.
And are you guys arm32 or arm64?
Hello,
I have a device that I obtained through beta testing that has not been released yet. I am allowed to keep the device now that testing is over. I am not happy with the stock rom and some of the apps it forces you to keep. I cannot remove them through ABD either. There is no stock ROM image available yet. Therefore, I cannot port TWRp or root.
I stumbled on project treble. I ran treble check and it says my phone is supported as it came with android 11. It supports systemless updates and has A/B system partition. I really like stock android ASOP. Is there anyway I can flash a generic image? What's the odds of it working correctly? Since there is no image available yet and I cannot port TWRP I have to worrying about not being able to recover the device if things go wrong. I know you can flash without TWRP which is why I decided to ask about this. Would I have a better chance flashing roms for supported devices with similar hardware? How should I proceed?
Thanks,
Rocky
as long as you have a compatible custom recovery AND the stock rom in case something go wrong, you can flash any GSI according to your device's architecture
Roizoulou said:
as long as you have a compatible custom recovery AND the stock rom in case something go wrong, you can flash any GSI according to your device's architecture
Click to expand...
Click to collapse
Since it is a beta unit I have neither as it has not been officially released. I have never flashed one of these roms so I do not know how well they work after flashing. I know the device has a pretty popular SOC which is a snapdragon 750g so I would assume if a gai runs good on another device using the 750g then it should work.
bigroc2223 said:
Since it is a beta unit I have neither as it has not been officially released. I have never flashed one of these roms so I do not know how well they work after flashing. I know the device has a pretty popular SOC which is a snapdragon 750g so I would assume if a gai runs good on another device using the 750g then it should work.
Click to expand...
Click to collapse
best you can do is dump the whole rom, make a backup before going any further
Roizoulou said:
best you can do is dump the whole rom, make a backup before going any further
Click to expand...
Click to collapse
I don't think I can dump it without root right?
bigroc2223 said:
I don't think I can dump it without root right?
Click to expand...
Click to collapse
an unlocked bootloader first and just search for how to dump system on google. it usually just need a pc and ADB
bigroc2223 said:
I don't think I can dump it without root right?
Click to expand...
Click to collapse
[GUIDE] Making Dump Files Out of Android Device Partitions
Use: The main purpose is to make a file that contains all data in android specific partition. This is really handy in case of dumping leak firmwares. Pr-requirement: - Rooted device. - Knowledge of how to use adb or Terminal Emulator. The...
forum.xda-developers.com
Roizoulou said:
[GUIDE] Making Dump Files Out of Android Device Partitions
Use: The main purpose is to make a file that contains all data in android specific partition. This is really handy in case of dumping leak firmwares. Pr-requirement: - Rooted device. - Knowledge of how to use adb or Terminal Emulator. The...
forum.xda-developers.com
Click to expand...
Click to collapse
I tried this before it requires root. I just double checked and the prereqs say root required too. This sucks because the device has decent specs. It's just the ROM and software on it are crappy. After doing some reading the biggest thing I'm worried about is flashing and not having mobile data since it is a 5g phone. I read about someone else flashing and not being able to get their mobile data to work.
bigroc2223 said:
I tried this before it requires root. I just double checked and the prereqs say root required too. This sucks because the device has decent specs. It's just the ROM and software on it are crappy. After doing some reading the biggest thing I'm worried about is flashing and not having mobile data since it is a 5g phone. I read about someone else flashing and not being able to get their mobile data to work.
Click to expand...
Click to collapse
what is the device?
Roizoulou said:
what is the device?
Click to expand...
Click to collapse
It's a beta device from TCL. It has not been released yet. I read that phh GSI should be compatible with all android phones with treble support. Therefore, I think I might just go for it. The only thing is if I end up with a bug I more than likely will probably have to figure it out on my own.
bigroc2223 said:
It's a beta device from TCL. It has not been released yet. I read that phh GSI should be compatible with all android phones with treble support. Therefore, I think I might just go for it. The only thing is if I end up with a bug I more than likely will probably have to figure it out on my own.
Click to expand...
Click to collapse
just try phh's first and if you encounter issues, try other custom roms
Roizoulou said:
just try phh's first and if you encounter issues, try other custom roms
Click to expand...
Click to collapse
I think I might of found a solution. I am pretty sure there is a way to boot a ROM before flashing it. I could of sworn I read this somewhere. It was an adb command. It allowed you too boot the ROM instead of flashing it. This would allow me to preview the ROM before officially flashing it to the device. I just cannot remember where I saw this at or the command.
My goal is to get a working gsi installed. From there I would like to get TWRP flashed on the device so it can be rooted. If I would need to port TWRP I think I could figure it out. This way when the device is officially released it will have TWRP ready to go for it. Also, since it will have TWRP I will be able to start porting roms as soon as they release the system image.
bigroc2223 said:
I think I might of found a solution. I am pretty sure there is a way to boot a ROM before flashing it. I could of sworn I read this somewhere. It was an adb command. It allowed you too boot the ROM instead of flashing it. This would allow me to preview the ROM before officially flashing it to the device. I just cannot remember where I saw this at or the command.
My goal is to get a working gsi installed. From there I would like to get TWRP flashed on the device so it can be rooted. If I would need to port TWRP I think I could figure it out. This way when the device is officially released it will have TWRP ready to go for it. Also, since it will have TWRP I will be able to start porting roms as soon as they release the system image.
Click to expand...
Click to collapse
like DSU loader?
Roizoulou said:
like DSU loader?
Click to expand...
Click to collapse
Never heard of that this was just an adb command.
I just downloaded ASOP 11.0 v309. Treble info says my device requires system-arm64-ab.img.xz. So I downloaded system-roar-arm64-ab-gapps.img.xz and system-roar-arm64-ab-vanilla.ikg.gz so hopefully those are the right ones. One has Gapps and one does not. Was going to flash the Gapps version first and see how things go. Then if need be flash vanilla.
I got a problem with phone calls. When I dial out I get call ended. Incoming calls I can hear them ring but get no way to answer. Also I am not getting text messages.
Roizoulou said:
like DSU loader?
Click to expand...
Click to collapse
I got it all working bro thanks for your help
bigroc2223 said:
I got it all working bro thanks for your help
Click to expand...
Click to collapse
gapps or vanilla?
Roizoulou said:
gapps or vanilla?
Click to expand...
Click to collapse
I was able to get them both to work. However, I am trying to use the gapps version, but I am getting an error that the device is not google certified. I cannot find a workaround unless I unroot which I do not want to do =(
bigroc2223 said:
I was able to get them both to work. However, I am trying to use the gapps version, but I am getting an error that the device is not google certified. I cannot find a workaround unless I unroot which I do not want to do =(
Click to expand...
Click to collapse
rooted with magisk?
Roizoulou said:
rooted with magisk
Click to expand...
Click to collapse
It comes rooted with phh superuser. I'm trying to find a way to pull my boot.img from the device so I can use it to flash magisk since it has a workaround for non Google certified devices.