I try to install rom using sideload but unfortunately system abort installation after verification! I tried few roms but result is the same in all cases. This is an issue because I recently accidently delete rom on my device, so, only way to recover the system is sideload
Please advice what can I do to improve situation
PS - run_program("/tmp/loki.sh") - Installation aborted I get that message all the time when initiate sideload installation.
Frist i dont believe you can use sideload from stock recovery .
1.will your phone boot?
2.if it can read on everything before doing anything to this phone.
P.s are you rooted
I will watch this thread for your reply i will help you any way i can.
Sent from my LG-LS980 using xda premium
Brick cause of Buil.prop edit
Is there a way to by pass the phone model dll ?
have been trying to revive a friends G2.
after taking the zv8 update, instead of spr my friend for some reason put open, that too not using a build.prop editor,
but he took a copy of the build.prop into windows, does the edit and copies it back to /system/ folder. reboots.
phone stuck on lg boot logo. basically a softbrick.
THE PROBLEM.
because of the edit in build.prop, while trying to flash the stock firmware with the right dll and the right tot file,
it gives a fail saying that the phone model is diff. This error has to be related to the edit done to the build.prop.
now the only way to reboot the phone is to either somehow we are able to replace the build.prop file with a complete stock one.
anybody has any idea as in how to create a flashable build.prop file ? adb sideload works.
i created a build.prop.zip file using zipme in my phone and tried to sideload it, it aborts.
can anybody shed some info on sideload or adb push.
thanks
pvinodnayak said:
Is there a way to by pass the phone model dll ?
have been trying to revive a friends G2.
after taking the zv8 update, instead of spr my friend for some reason put open, that too not using a build.prop editor,
but he took a copy of the build.prop into windows, does the edit and copies it back to /system/ folder. reboots.
phone stuck on lg boot logo. basically a softbrick.
THE PROBLEM.
because of the edit in build.prop, while trying to flash the stock firmware with the right dll and the right tot file,
it gives a fail saying that the phone model is diff. This error has to be related to the edit done to the build.prop.
now the only way to reboot the phone is to either somehow we are able to replace the build.prop file with a complete stock one.
anybody has any idea as in how to create a flashable build.prop file ? adb sideload works.
i created a build.prop.zip file using zipme in my phone and tried to sideload it, it aborts.
can anybody shed some info on sideload or adb push.
thanks
Click to expand...
Click to collapse
I'm stuck in the same boat.
roooted...twrp 2700...then installed CM11/gapps to make it work with "US CARRIERS"
it didnt flash right...although TWRP log says " flash successful
same issue....LG flash tools saying phone model diff (d801) but infact its ls980....go figure
i have a working recovery. how can i download a rom file to the PHONE STORAGE VIA TWRP?
whats my options here guys?
thanks in advance, i hope my noobiness doesnt tickle anyones nerves too much.
Hello devs,
please can somebody discribe how to modify the original update image, that we can install the image with TWRP without overwriting the TWRP recovery , fastboot a.s.o.
That would be great.
You can use a Archive Software like (7zip) to replace files in your update.zip . I didn't try it so no idea if it works.
I know, with 7zip we can open the files, but the point is, how to modify the update script that the recovery will not be overwritten a.s.o.
Frank Bearson said:
I know, with 7zip we can open the files, but the point is, how to modify the update script that the recovery will not be overwritten a.s.o.
Click to expand...
Click to collapse
If all you are worried about is overwriting TWRP then just flash TWRP in TWRP before you reboot
Hi all, I posted this in the 6P bootloop thread, but didn't get a response. As that is a pretty LONG thread, i'm thinking my question may have gotten lost in the jumble.
Quick run down.
A few months back my 6P started the BLOD. I found the fix listed on these pages, applied it, and have been happily using my phone ever since. Phone is bone stock 7.1.2 other than the TWRP recovery and the modified EX kernel for 4 cores.
Since the fix, my phone FINALLY got the OTA update to go to Android 8.0 and i obviously want to get it done. My concern is HOW to do this without causing more headache.
Can anyone point me in the right direction? Should i use the OTA update or download the factory image from Google?
I've got some knowledge as i used to be into the "rooting" scene back in the day, but haven't for a while, so i feel a little lost.
Thanks for any help.
johnnyphive said:
Hi all, I posted this in the 6P bootloop thread, but didn't get a response. As that is a pretty LONG thread, i'm thinking my question may have gotten lost in the jumble.
Quick run down.
A few months back my 6P started the BLOD. I found the fix listed on these pages, applied it, and have been happily using my phone ever since. Phone is bone stock 7.1.2 other than the TWRP recovery and the modified EX kernel for 4 cores.
Since the fix, my phone FINALLY got the OTA update to go to Android 8.0 and i obviously want to get it done. My concern is HOW to do this without causing more headache.
Can anyone point me in the right direction? Should i use the OTA update or download the factory image from Google?
I've got some knowledge as i used to be into the "rooting" scene back in the day, but haven't for a while, so i feel a little lost.
Thanks for any help.
Click to expand...
Click to collapse
Well, for starters do NOT take the OTA. It will either fail or boot loop your phone. Due to the fact you have a modified boot.img you will need to update manually using fastboot with the full image. Re-apply the modified kernel after you finish updating the partitions, but BEFORE booting the first time. You can follow most guides on how to manually update a full image using fastboot, just add the step of flashing the modified kernel before booting.
Thanks for the reply and the help. If i could ask for a little more help, as this is my only phone.
Can you explain the difference between the modified boot.img and the modified kernel?
If i download the factory image from here (https://developers.google.com/android/images) is it ok to the get the latested one (Nov 2017) or do i need to get the original one (Sep 2017 as i'm on Fi)
Once i flash the factory image, is it going to replace the modified boot image as well as the modified kernel?
Follow the OP on this thread (https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279) in the downloads section there appear to be 2 files i would need, the "Boot.img from stock 6.17, 8.0 firmware" and "EX kernel version 5.03". Am i understanding that correctly?
Like i said, this is my only phone, and i'm probably just being overly paranoid about bricking it, but any clarification would be greatly appreciated.
johnnyphive said:
Thanks for the reply and the help. If i could ask for a little more help, as this is my only phone.
Can you explain the difference between the modified boot.img and the modified kernel?
If i download the factory image from here (https://developers.google.com/android/images) is it ok to the get the latested one (Nov 2017) or do i need to get the original one (Sep 2017 as i'm on Fi)
Once i flash the factory image, is it going to replace the modified boot image as well as the modified kernel?
Follow the OP on this thread (https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279) in the downloads section there appear to be 2 files i would need, the "Boot.img from stock 6.17, 8.0 firmware" and "EX kernel version 5.03". Am i understanding that correctly?
Like i said, this is my only phone, and i'm probably just being overly paranoid about bricking it, but any clarification would be greatly appreciated.
Click to expand...
Click to collapse
Use the latest November image. The boot.img contains the kernel and ramdisk, critical files necessary to load the device before the filesystem can be mounted. When you flash the new boot.img contained in the Google image, it will overwrite the patched kernel. You then need to re-patch it by installing EX kernel before booting. EX writes to (modifies) the stock boot.img. There are also pre-modifed boot.img files floating around. You will probably get more detailed help in the dedicated thread. Learning to flash manually (or remember how) is not really a big deal and a necessary skill for modding (and for getting yourself out of trouble). Good luck. :good:
v12xke said:
Use the latest November image. The boot.img contains the kernel and ramdisk, critical files necessary to load the device before the filesystem can be mounted. When you flash the new boot.img contained in the Google image, it will overwrite the patched kernel. You then need to re-patch it by installing EX kernel before booting. EX writes to (modifies) the stock boot.img. There are also pre-modifed boot.img files floating around. You will probably get more detailed help in the dedicated thread. Learning to flash manually (or remember how) is not really a big deal and a necessary skill for modding (and for getting yourself out of trouble). Good luck. :good:
Click to expand...
Click to collapse
Ok, so 1 last time (sorry)
1 - Downloaded the latest 8.0.0 factory image from google (this contains the bootloader, radio, and partitions (.zip).
2 - Get phone to fastboot and apply the above 3 new images
3- before rebooting, flash oreo4core (new, modified boot.img), TWRP recovery.img
4- reboot to recovery (TWRP) and apply the modified EX kernel
5 - reboot and (hopefully) profit
Am i missing anything, or doing anything that isn't needed?
johnnyphive said:
Ok, so 1 last time (sorry)
1 - Downloaded the latest 8.0.0 factory image from google (this contains the bootloader, radio, and partitions (.zip).
2 - Get phone to fastboot and apply the above 3 new images
3- before rebooting, flash oreo4core (new, modified boot.img), TWRP recovery.img
4- reboot to recovery (TWRP) and apply the modified EX kernel
5 - reboot and (hopefully) profit
Am i missing anything, or doing anything that isn't needed?
Click to expand...
Click to collapse
<<Disclaimer: I don't use the 4 core kernel, so I don't know if it comes with installer script or someone has just modified the latest boot.img>> Unzip the "partitions" zip you refer to and extract those image files to the same folder as bootloader and modem. For example, you can keep TWRP recovery if you don't flash the recovery.img. That is how you preserve your custom recovery. So in other words you'll now have a folder (your ADB folder?) with 5 image files.... bootloader, radio, boot, system, and vendor all in one folder. <<Note: it is my understanding you just substitute the latest oreo4core file (should be boot.img?) If this is true, copy that file into your ADB folder and let it overwrite the stock boot.img. Stop. Copy over flash-all.bat, change the *.bat extension to *.txt and open in notepad. You will see (and can copy/paste) the fastboot commands to get you started with bootloader and radio. Then flash the last 3 (boot, system, vendor). At this point you can reboot into the OS. Since you substituted the oreo4core boot.img file for the stock boot.img there is no need to use TWRP to flash anything. That and since you skipped flashing the recovery.img, TWRP is still there.
v12xke said:
<<Disclaimer: I don't use the 4 core kernel, so I don't know if it comes with installer script or someone has just modified the latest boot.img>> Unzip the "partitions" zip you refer to and extract those image files to the same folder as bootloader and modem. For example, you can keep TWRP recovery if you don't flash the recovery.img. That is how you preserve your custom recovery. So in other words you'll now have a folder (your ADB folder?) with 5 image files.... bootloader, radio, boot, system, and vendor all in one folder. <<Note: it is my understanding you just substitute the latest oreo4core file (should be boot.img?) If this is true, copy that file into your ADB folder and let it overwrite the stock boot.img. Stop. Copy over flash-all.bat, change the *.bat extension to *.txt and open in notepad. You will see (and can copy/paste) the fastboot commands to get you started with bootloader and radio. Then flash the last 3 (boot, system, vendor). At this point you can reboot into the OS. Since you substituted the oreo4core boot.img file for the stock boot.img there is no need to use TWRP to flash anything. That and since you skipped flashing the recovery.img, TWRP is still there.
Click to expand...
Click to collapse
Thank for the help! Everything seems to be up and running. I know you said you don't use the "4 cores" (can only assume your either on a different phone or yours isn't affected by the BLOD), but do you know if i still need to apply the EX kernel update, or know of a way to tell if it's already been applied?
Thanks again for all the help. I was pretty much in the right direction, but being as how i'd been away from it for a while, i wanted some backup
johnnyphive said:
Thank for the help! Everything seems to be up and running. I know you said you don't use the "4 cores" (can only assume your either on a different phone or yours isn't affected by the BLOD), but do you know if i still need to apply the EX kernel update, or know of a way to tell if it's already been applied? Thanks again for all the help. I was pretty much in the right direction, but being as how i'd been away from it for a while, i wanted some backup
Click to expand...
Click to collapse
I don't think you can flash EX kernel from now on. I think you have to use a modded boot.img that will contain his kernel/ramdisk. This is my guess. You really should be getting your information in the dedicated thread where everyone is actually installing and using it. Google "oreo 4 core" and you will find the XDA thread is the first hit. Good luck. :good:
Would anyone here have it? I overlooked the "7.1.1" message and used TWRP anyways, THEN used the 7.1.1 boot img which threw me into a bootloop, I can boot into EDL just fine, sideload doesn't work with me, so I see obtaining my original B2017G US boot.img and reflashing it with tulip as the best option to get back on track! Hope someone is able to help
Though, would there be any other methods of flashing the boot.img and removing the bootloop, like updating my firmware to 7.1.1 or something?
https://forum.xda-developers.com/showpost.php?p=73257562&postcount=13
I see something here, downloaded "Axon7mini_Android7(SD card software).zip" but unfortunately I don't know what to do with that update.zip file.
I've posted a few things about this. Trying to pull it together here.
Got phone back to stock F5321 34.3.A.0.252 Customized NOBA 1304-9586 R6D User-live
I still cannot restore via twrp ( 3.2.2 ). I get a missing modem file?
unable to find file system (first period)
Error opening modem_fs1.emmc.win no such file.
I've tried both magisk and supersu flashable. Both do not work. They also break something where I have to reflash with emma to get it to even boot again. If I don't it just sits at the sony screen.
Literally all I need to do is restore a telegam conversation. Can't do this without root. ( need to pull from full twrp backup via titanium). I'd really like to Just restore the whole twrp backup but i cant get that to work.
Can anyone point me to an easy root or getting twrp to actually restore this?
Full story here: https://forum.xda-developers.com/x-compact/help/how-to-7-1-t3824192
j1tters said:
I've posted a few things about this. Trying to pull it together here.
Got phone back to stock F5321 34.3.A.0.252 Customized NOBA 1304-9586 R6D User-live
I still cannot restore via twrp ( 3.2.2 ). I get a missing modem file?
unable to find file system (first period)
Error opening modem_fs1.emmc.win no such file.
I've tried both magisk and supersu flashable. Both do not work. They also break something where I have to reflash with emma to get it to even boot again. If I don't it just sits at the sony screen.
Literally all I need to do is restore a telegam conversation. Can't do this without root. ( need to pull from full twrp backup via titanium). I'd really like to Just restore the whole twrp backup but i cant get that to work.
Can anyone point me to an easy root or getting twrp to actually restore this?
Full story here: https://forum.xda-developers.com/x-compact/help/how-to-7-1-t3824192
Click to expand...
Click to collapse
You won't be able to flash something like SuperSU or Magisk without a cuatom kernel, because of Sony kernel security. Any modification to system will prevent boot. To root, you need to fastboot a custom boot img with security disabled. You can find one here - https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479. Follow instructions in op, and make sure to download the right version for your fw, then flash the same version of TWRP you made the backup with.