[question] Working method to pull boot.img from the phone? - Moto G7 Questions & Answers

Currently I don't see any fulll ROM for G7. I tried to use several methods found in G6 forum and I got either "file not found" or "permission denied".
Can anybody tell me working method to pull boot.img from the phone?
This is the only step I need to be done to achieve root.

https://mirrors.lolinet.com/firmware/moto/river/official/
Check carefully your build number to match the ROM or "sorry"
Root is just few hours away

Related

Moto-Fastboot ROM's ?

Just followed Ken's instruction how to install the non OTA Gingerbread ROM and am happy with that process.
OK the touchscreen has managed to reverse itself but I will figure that out after my Atrix is fully charged.
Anyway I was wondering if it was possible to load other ROM's via this method ?
Do you simply load the contents of the zip file item by item or is there a faster method that I just haven't read or found yet ?

Sideload issue in stock recovery (ls980)

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.

[Q] Read the Sticky, still can't flash stock or lollipop kernels

I wonder whether there is help for someone who thought he knew how to flash a kernel but apparently is deluded. I have the original nexus seven Wi-Fi tablet android version 4.3 build number JWR66V. The system still wants to update me to 4.3 because I ripped some files out of the cache directory to prevent OTA updates. I have both fastboot and adb. I have read the stickies about flashing.
The phone is rooted and the bootloader is unlocked. I use TWRP custom recovery, and it's a good thing, because I solidly bricked myself up just trying to get my lollipop. I know there are tools to root a nexus seven even with stock lollipop, so I thought I'd upgrade my phone to stock lollipop and then use one of those methods. I tried both the stock lollipop kernel and the one provided by chain fire, which I understand is rooted already. (I'm assuming upgrading to lollipop will lose me my root, unless I want to recover back to 4.3.)
I tried to do these things a couple of different ways. When I tried fast boot, I got the message "error: neither -p product specified nor ANDROID_PRODUCT_OUT set". There was a YouTube video suggesting how to deal with this error message. I'm pretty sure I followed the instructions but no go. (I was using the "flash all" command.) This was after I had put the file containing lollipop in the directory, both zipped and unzipped (so that I had an .img file instead of a zip file). I tried using both the zip file with all of the lollipop partitions and the system image file individually. No go. I also had a message that android-info.txt could not be found, even though it was in the same, working directory.
I could be wrong but I don't think you can install a complete updated kernel from a file on the device. I think that works only with update.zip.
I'm still thinking fastboot is my best bet, but there are dependencies apparently and I don't know what files to include in its directory. Then, am I wise to go to stock and then root, or should I simply flash the stock kernel already rooted? I assume that's what chainfire is providing, correct?
I notice the lollipop official ROM nor Chainfire’s supposedly-rooted image have any file named nakasi. I have only .img files, no .zip files.
I found a dozen sets of instructions on how to flash a kernel but something I need is missing from all of them. Does anyone know what it is or can anyone offer some helpful advice?
Thank you,
Leon M.

Difference in root methods

What is the difference between these two root methods? The first says to install ADB (what is ADB?), to type adb wait-for-device, then to use ODIN to flash what it calls an "engineer-rooted boot image," and finally to flash the SuperSU file (not sure how).
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
The second says to flash the TWRP file through a Windows computer using ODIN, to copy the SuperSU file to the phone (in addition to a no-verify-opt-encrypt file), and to then flash both using the phone while it is in TWRP mode (not through the computer).
https://www.youtube.com/watch?v=nlj76YvxGYo
What's happening behind the scenes in each method? There are a lot of guides on how to root one's phone on the internet, but at least I haven't been able to find one that explains what each step actually does. I would really appreciate it if you could explain both methods to me like I was five.
Many thanks in advance,
scndts

need help restoring to stock

been trying to restore my moto x pure to stock and i keep getting this error.
Preflash Validation Error indicating such when you attempt to flash the partition table (gpt.bin).
i tried all the firmwares possible and i cant seem to get it working. any suggestions or work arounds to fix
I was on 7.1.1 custom rom and tried to restore to 6.0 and thats when it failed. i also treid 5.0 still same issue.
So essentially i am following directions and i get stuck with that error. anyone know of a work around or a way to find out which one i need to use to lock the bootloader?
https://forum.xda-developers.com/showthread.php?t=3489110
Read the entire first post.

Categories

Resources