Try the boot.img shared here, you can patch it yourself. (I did it) don't get boot.img from payload dumper go (somehow for me it's only 68MB way less then 196MB as should be for boot.img)Im getting bootloops after fastoot boot patchedimage
I patch my own file, then I try the one shared here
My device is IN2111 india, OOS13F.16
I uninstall magisk before try, dont know what more to do, someone has tried to root
Even I was uninstalled magisk, there was still on my phone, but I could get over the bootloop by uninstalling lucky patcher and hide my applistTry the boot.img shared here, you can patch it yourself. (I did it) don't get boot.img from payload dumper go (somehow for me it's only 68MB way less then 196MB as should be for boot.img)
Even I was uninstalled magisk, there was still on my phone, but I could get over the bootloop by uninstalling lucky patcher and hide my applist
Idk. Haven't used lucky patcher for a long time. Magisk present as an app regardless of you are rooted or not. You check root status by open the magisk app, see if install says the version of magisk. Otherwise just patch boot.imgEven I was uninstalled magisk, there was still on my phone, but I could get over the bootloop by uninstalling lucky patcher and hide my applist
Yes, it was as an app, I uninstall, but now when I install it again after successfuly fastboot boot all my magisk data was intact, even modules was still installed x'D... actually I counldt install magisk at first because trying different things I got magisk canary version.. so installling normal magisk throw me the error than an updated version of magisk was already installed... but there was no magisk at sight to open, install the canary version again do the trickIdk. Haven't used lucky patcher for a long time. Magisk present as an app regardless of you are rooted or not. You check root status by open the magisk app, see if install says the version of magisk. Otherwise just patch boot.img
Interesting. Call me paranoid but I always prefer to extract the boot.img file directly from the file I will be updating with. I used Payload Dumper GO and patched it without an issue.Try the boot.img shared here, you can patch it yourself. (I did it) don't get boot.img from payload dumper go (somehow for me it's only 68MB way less then 196MB as should be for boot.img)
I always do that to. But Payload Dumper Go somehow got the file size real small so I was skeptical to use the file with usual size. I didn't try to boot the patched boot.img from payload dumper go even though I did patched it with magisk. I kept it as a backup in case the one shared here didn't work but it worked so I didn't try the one from my payload dumper go. What works works, right.Interesting. Call me paranoid but I always prefer to extract the boot.img file directly from the file I will be updating with. I used Payload Dumper GO and patched it without an issue.
what version are u using? i got that error on older versionsI always do that to. But Payload Dumper Go somehow got the file size real small so I was skeptical to use the file with usual size. I didn't try to boot the patched boot.img from payload dumper go even though I did patched it with magisk. I kept it as a backup in case the one shared here didn't work but it worked so I didn't try the one from my payload dumper go. What works works, right.
I was talking about f16
I was asking what version of dumper go ahaha im using payload-dumper-go_1.2.2 without problems
I don't really know ehat version but the file I attracted was fine as well. I just didn't check it at the time I wrote the response. Until now, I used it more than thrice and worked every time. Though payload-dumper-go f17 got me boot.img of 0MBI was asking what version of dumper go ahaha im using payload-dumper-go_1.2.2 without problems
I could exctract without problem the boot.img search for the latest version of payload-dumer-goI don't really know ehat version but the file I attracted was fine as well. I just didn't check it at the time I wrote the response. Until now, I used it more than thrice and worked every time. Though payload-dumper-go f17 got me boot.img of 0MB
what errors? what version of dumper are you using?Anybody has the F17 boot image? I tried to dump it myself but encountered errors...
We're you able to get it? If yes please share thxAnybody has the F17 boot image? I tried to dump it myself but encountered errors...
Anyone has LE2115 Global F.18 boot.img? I want to try doing the MSM readback but want a copy of F.18 boot.img just in case I stuff up.
LE2115 Global F.18 stock boot.img attached....and @Z-Blade, there's no way to stuff up, the only thing that can happen is missing the EDL window which you can totally avoid just by tapping on ReadBack Mode before pluggin in the phone in EDL mode. Enjoy.
Sweet, thanks for the tip. I will give it a shot.LE2115 Global F.18 stock boot.img attached....and @Z-Blade, there's no way to stuff up, the only thing that can happen is missing the EDL window which you can totally avoid just by tapping on ReadBack Mode before pluggin in the phone in EDL mode. Enjoy.
You can only use payload dumber for full OTA, the incremental OTA does not contain the boot.img file and the only way to get a copy is to update the phone first and then extract the boot.img file using MSM readback via EDL.
F.17 is the latest. Look at post #140 on page 7 for the stock LE2115.F.17 boot.img.Thanks for sharing.
My op 9 currently still runs non root stock oos11 , about to upgrade to 13by ota, then unlock bootloader and flash patch. I noticed ota carries F17, your share drive use F16, will that be a problem?
View attachment 5796595
Post #147 in this thread. Scroll up.