Related
ok so I have done some searching and found nothing that actually resolves my problem.
I have tried time and again to flash a newBoot.img, with different images. I always either get "no such file or directory" or "mtd: read all-zero block at 0x0000000; skipping"
the image will never actually flash. it either boot loops on the "htc" screen or freezes on the "htc" screen. it never gets to the animation.
I used the following commands to flash the newBoot.img:
adb push newBoot.img /sdcard/newBoot.img
adb shell
cat /dev/zero > /dev/mtd/mtd2
flash_image boot /sdcard/newBoot.img
reboot
I did this all in the Recovery console.
am I missing something?!
please help, thanks
gmelchert said:
I did this all in the Recovery console.
am I missing something?!
please help, thanks
Click to expand...
Click to collapse
....What exactly are you trying to flash??
pseudoremora said:
....What exactly are you trying to flash??
Click to expand...
Click to collapse
the "newBoot.img" for DarchDroid 2.1 jit
gmelchert said:
the "newBoot.img" for DarchDroid 2.1 jit
Click to expand...
Click to collapse
You are talking about this thread, right? And if so, you are downloading the STABLE ROM, correct?
yes and no, I'm trying the AOSP jit enabled one
gmelchert said:
yes and no, I'm trying the AOSP jit enabled one
Click to expand...
Click to collapse
Let me check something.
gmelchert said:
the "newBoot.img" for DarchDroid 2.1 jit
Click to expand...
Click to collapse
Wow...for a moment there, I thought you were flashing a Darktremor A01 kernel. I was about to ask you where you got that since I never released it.
gmelchert said:
ok so I have done some searching and found nothing that actually resolves my problem.
I have tried time and again to flash a newBoot.img, with different images. I always either get "no such file or directory" or "mtd: read all-zero block at 0x0000000; skipping"
the image will never actually flash. it either boot loops on the "htc" screen or freezes on the "htc" screen. it never gets to the animation.
I used the following commands to flash the newBoot.img:
adb push newBoot.img /sdcard/newBoot.img
adb shell
cat /dev/zero > /dev/mtd/mtd2
flash_image boot /sdcard/newBoot.img
reboot
I did this all in the Recovery console.
am I missing something?!
please help, thanks
Click to expand...
Click to collapse
Nothing I see is incorrect. Try putting a delay of about 10 seconds between erasing the mtd2 device and flashing the ROM. This is especially true if you are flashing from recovery.
tkirton said:
Wow...for a moment there, I thought you were flashing a Darktremor A01 kernel. I was about to ask you where you got that since I never released it.
Click to expand...
Click to collapse
I thought he was flashing a kernel as well... I'm downloading the AOSP file now and then going to check what it is... its a zip file, so I presume it's just a flashable update, but I'll double check.
it is, but later on in the thread there are a few "newBoot.img" to download. one is clocked @ 710mhz and the other is 787mhz i think
pseudoremora said:
I thought he was flashing a kernel as well... I'm downloading the AOSP file now and then going to check what it is... its a zip file, so I presume it's just a flashable update, but I'll double check.
Click to expand...
Click to collapse
He's flashing a kernel...newBoot.img actually comes from a guide that was posted here sometime back on how to compile your own kernel. What tripped me was that newBoot.img is the name of many iterations of my Darktremor kernel, which I never released but do use for testing (I have it currently on my phone on top of FreshToast to test ext4 patches).
His instructions are the same instructions I use to flash...the difference is that I actually flash while in a working ROM (not smart, but it works). He's doing it from recovery. Last time I did from recovery was a couple of days ago, and I got a bunch of errors unless I waited around 10 seconds between clearing /dev/mtd/mtd2 and flashing the kernel.
If he gets the errors, he can try to flash again...it seems to work when I did it.
gmelchert said:
it is, but later on in the thread there are a few "newBoot.img" to download. one is clocked @ 710mhz and the other is 787mhz i think
Click to expand...
Click to collapse
tkirton said:
He's flashing a kernel...newBoot.img actually comes from a guide that was posted here sometime back on how to compile your own kernel. What tripped me was that newBoot.img is the name of many iterations of my Darktremor kernel, which I never released but do use for testing (I have it currently on my phone on top of FreshToast to test ext4 patches).
His instructions are the same instructions I use to flash...the difference is that I actually flash while in a working ROM (not smart, but it works). He's doing it from recovery. Last time I did from recovery was a couple of days ago, and I got a bunch of errors unless I waited around 10 seconds between clearing /dev/mtd/mtd2 and flashing the kernel.
If he gets the errors, he can try to flash again...it seems to work when I did it.
Click to expand...
Click to collapse
Really? Okay, cause I downloaded the AOSP file and it's definitely a custom ROM... but I'm glad it's sorted out now.
still no luck with the waiting. I tried it on stable when it was booted and I got "could not write file" or something like that where "skipping" was. I'm back to "sticking" now. argh
gmelchert said:
still no luck with the waiting. I tried it on stable when it was booted and I got "could not write file" or something like that where "skipping" was. I'm back to "sticking" now. argh
Click to expand...
Click to collapse
Don't do the step that erases your mtd2 partition. Just ran into the same problem with an automated script. 10 seconds doesn't seem to cut it, but I noticed I can just flash without erasing first.
tkirton said:
Don't do the step that erases your mtd2 partition. Just ran into the same problem with an automated script. 10 seconds doesn't seem to cut it, but I noticed I can just flash without erasing first.
Click to expand...
Click to collapse
I just tried that and all I got was a repeat command line
"# flash_image boot /sdcard/newBoot.img
flash_image boot /sdcard/newBoot.img
#
http://forum.xda-developers.com/showpost.php?p=5447589
Try that post use #9
It's not a flashable zip, needs to be unziped and placed into the sdk tools folder!
Also make sure you are not using the one with file ext.bat I believe if you are you need to change it to .img!
If ya need some help hit me up!
Roman G said:
http://forum.xda-developers.com/showpost.php?p=5447589
Try that post use #9
It's not a flashable zip, needs to be unziped and placed into the sdk tools folder!
Also make sure you are not using the one with file ext.bat I believe if you are you need to change it to .img!
If ya need some help hit me up!
Click to expand...
Click to collapse
I used that post in the first place. Basically what I'm trying to do is get AOSP DarchDroid to actually boot so I want to try one of the kernels darch posted. I have not yet been able to get them to flash (what is the correct outcome in cmd when I type "flash_image boot /sdcard/newBoot.img"?) I know you were on of the people who got the jit working, what did you do to get it to work? the rom I mean...
Good morning,
I have the ICS 404 stock, rooted with CW 6.0.0.7. I downlaoded via ota the JB but the system was not able to install the new JB. How can solve this problem?? Do I have to install manually? Where is the file downloaded?? Someone can help me on the procedure to follow??
thanks
coluichepensa said:
Good morning,
I have the ICS 404 stock, rooted with CW 6.0.0.7. I downlaoded via ota the JB but the system was not able to install the new JB. How can solve this problem?? Do I have to install manually? Where is the file downloaded?? Someone can help me on the procedure to follow??
thanks
Click to expand...
Click to collapse
I have the same exact problem, however it also occurs when I try to install the zip directly from CWM...perusing the other threads it seems as though it's an issue with BusyBox overwriting some files in /system/bin. For the life of me I cannot find how to correct this issue even though the it is repeatedly mentioned in the threads that is has been covered already. Seeing as I'm nearing my wits' end, I'd appreciate someone pointing me in the right direction. Thanks in advance.:crying:
---------- Post added at 10:02 PM ---------- Previous post was at 09:42 PM ----------
Just to clarify this is what I get when I try to install 4.1.1:
Verifying current system...
assert failed: apply_patch_check
('/system/bin/gzip", "afdda757b27b444f525a0f41726d2c1a83012869", "5ba3b3ecd509cf6dcee37b2f27110310a1f55045")
E:Error in /cache/9ZGgDXDi.zip
(Status 7)
Installation aborted.
Even flashing 4.0.4 vias CWM doesn't overwrite the problematic /system/bin files. I got as far as trying to flash a factory image of 4.0.4 but got too frustrated with the fastboot commands in Terminal on OSX.
Again, while not a total neophyte, I could really use some hand holding regarding this mess. Thanks in advance.
Bumping in hope that some kind soul can walk me through replacing the /system/bin files that were overwritten by busybox. Tried factory reset and reflashing the 4.0.4 OTA to no avail. I think that flashing a factory image of 4.0.4 would work but I can't figure that out. I'm on OS X for what it's worth.
I appreciate your time.
Flashing through fastboot is rather simple. Can't remember the exact Mac commands of top of my head. But they are basically the same just fastboot-mac or whatnot.
Anyways if that is really a issue/ don't wanna bother with it. Look for the full stock ROM for your device and flash that with cwm. Make sure you wipe the old rom off first.
albundy2010 said:
Flashing through fastboot is rather simple. Can't remember the exact Mac commands of top of my head. But they are basically the same just fastboot-mac or whatnot.
Anyways if that is really a issue/ don't wanna bother with it. Look for the full stock ROM for your device and flash that with cwm. Make sure you wipe the old rom off first.
Click to expand...
Click to collapse
Thanks for the prompt reply. I dl'ed the factory image for my device (I9020T) from the developers/google site but couldn't get the ./flash-all.sh script to run. I then took the image.zip file from the factory tgz file and tried to flash it via CWM but got installation aborted/ Error 7 as well. Seems to be the only way to overwrite the system/bin filed that BusyBox replaced is to flash a factory image via fastboot.
Is there a way in which I can replace the problematic system/bin files that are preventing me from installing JB without flashing a stock factory image? And if there isn't, could I get some help with the Terminal commands for getting the /.flash-all.sh script to run on Mac?
Thanks again for your help and patience.
Those images are not mean to flashed through any recovery.
You can ignore that script. Extract what you have downloaded until you are left with ALL .img files. You should have system.img boot loader, radio, and userdata.img
Flash them one at a time with fastboot. Can't remember the exact Mac command but its fastboot flash system system.img etc for windows. Just look it for Mac. Think its fastboot-mac then the command but not sure. I hate Macs.
This has Mac fastboot info in it. I hate Macs also
http://forum.xda-developers.com/showthread.php?t=1789216
Edit: this has some info to help you also, I just change to Mac fastboot
http://forum.xda-developers.com/showthread.php?t=1785672
Sent from my Nexus S using xda premium
jayjay3333 said:
This has Mac fastboot info in it. I hate Macs also
http://forum.xda-developers.com/showthread.php?t=1789216
Edit: this has some info to help you also, I just change to Mac fastboot
http://forum.xda-developers.com/showthread.php?t=1785672
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Those two links were extremely helpful, thanks for that. I got as far as having all the requisite factory image files ready to be flashed in the same folder, but when I issue the command to flash the bootloader.img I get
Code:
-bash: ./fastboot-mac: Permission denied
.
Think I may have gotten a little over my head with this whole rooting business
For the record I am rooted and have an unlocked bootloader.
coluichepensa said:
Good morning,
I have the ICS 404 stock, rooted with CW 6.0.0.7. I downlaoded via ota the JB but the system was not able to install the new JB. How can solve this problem?? Do I have to install manually? Where is the file downloaded?? Someone can help me on the procedure to follow??
thanks
Click to expand...
Click to collapse
try latest touch version here http://bit.ly/QHLhXs when the update go to install in cmw there one dailoge box come choose yes and choose reboot and its appear again dailoge box choose yes disable recovery flash.
I solved the problem flashing this stock rom. http://forum.xda-developers.com/showthread.php?t=1784497
Finally sussed it out as well! Thanks to all for the help. Flashing the stock ICS image allowed me to install the JB OTA - will never install the BusyBox from the market again.
Cheers again to all.
I was curious as to any difference between flashing a Kernel via ADB using a boot.img or flashing it as a .zip via recovery. Is there a benefit of one over the other. I've always done it via ADB, but I recently tried via a zip file through TWRP but didn't notice any difference, but wasn't sure if I was just being oblivious or not lol
I heard someone mention that when flashing it via ADB you don't get the Modules that come with the Kernel. Which I don't know if that was BS or not, cause as I stated, after trying it both ways, I didn't notice any features taken away i.e. flashed bricked kernel via ADB and then restored stock kernel and then flashed bricked via TWRP, and I was able to activate DT2W/S2W regardless of the method of flashing, as well as OC capabilities, Fast Charge, etc etc.
Just been curious about this for awhile, and there doesn't seem to be much discussion about it, so was unable to find an answer. Dev's always seem to give you the option to download a boot.img or .zip file, and wasn't sure if htat was just due to giving peopel the choice of preferred flashing method, or because of inherit benefits between the two.
Its simply 2 different options of installation. The final result is the same: a boot.img gets extracted and written onto the appropriate partition of your device.
When you use fastboot to flash the img. the executable on your computer does this directly.
When you use a recovery to flash the zip (which also contains the boot.img), the edify script within the zip gives instructions to the recovery on how and where to write the image to.
There isnt really any advantage to doing one over the other.
Silicon Knight said:
I was curious as to any difference between flashing a Kernel via ADB using a boot.img or flashing it as a .zip via recovery. Is there a benefit of one over the other. I've always done it via ADB, but I recently tried via a zip file through TWRP but didn't notice any difference, but wasn't sure if I was just being oblivious or not lol
I heard someone mention that when flashing it via ADB you don't get the Modules that come with the Kernel. Which I don't know if that was BS or not, cause as I stated, after trying it both ways, I didn't notice any features taken away i.e. flashed bricked kernel via ADB and then restored stock kernel and then flashed bricked via TWRP, and I was able to activate DT2W/S2W regardless of the method of flashing, as well as OC capabilities, Fast Charge, etc etc.
Just been curious about this for awhile, and there doesn't seem to be much discussion about it, so was unable to find an answer. Dev's always seem to give you the option to download a boot.img or .zip file, and wasn't sure if htat was just due to giving peopel the choice of preferred flashing method, or because of inherit benefits between the two.
Click to expand...
Click to collapse
Fastboot is the tool to which you are referring to, not ADB. You use fastboot to flash image files to partitions directly through the bootloader. That being said, there's no difference which method you use, the end result is the same. Using fastboot requires an unlocked bootloader, flashing through the recovery does not. When you flash a zip through the recovery, the proper destination partition is automatically overwritten whereas when you flash an image in fastboot, you have to specify the proper partition. That's the only real difference.
Excuse me, Fastboot is what I meant yes. My bad lol.
Thanks for the info, I figured as much. Im experienced with both methods and understand how they work. Just wasn't sure if there was a benefit over one or the other when it comes to flashing custom kernels. Thanks bro I appreciate the help. I will stick to flashing via fastboot then. I just prefer to do it that way.
I also use flashify sometimes as well. Seems to work pretty good.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Chromium_ said:
Its simply 2 different options of installation. The final result is the same: a boot.img gets extracted and written onto the appropriate partition of your device.
When you use fastboot to flash the img. the executable on your computer does this directly.
When you use a recovery to flash the zip (which also contains the boot.img), the edify script within the zip gives instructions to the recovery on how and where to write the image to.
There isnt really any advantage to doing one over the other.
Click to expand...
Click to collapse
i have a locked bootloader but i have root, can i "flash" throught root explorer overwriting boot.img file?
and reboot?
AXD96 said:
i have a locked bootloader but i have root, can i "flash" throught root explorer overwriting boot.img file?
and reboot?
Click to expand...
Click to collapse
Root explorer is not a flashing tool and no, it cannot modify the kernel
Sent from my Nexus 5 using Tapatalk
rootSU said:
Root explorer is not a flashing tool and no, it cannot modify the kernel
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
maybe a stupid question, but the kernel is all saved in boot.img?
AXD96 said:
maybe a stupid question, but the kernel is all saved in boot.img?
Click to expand...
Click to collapse
Yep Indeed. What you can browse is /sys, which are the "files" the kernel manipulates to do what it wants...
..but browsing here is of no benefit to changing a kernel
Sent from my Nexus 5 using Tapatalk
Unlock your device and just use the a custom recovery.
Sent from my Nexus 5 using Tapatalk
can we change kernel alone
i am using SENSONIC with stock kernel can i change kernel alone.
I want to change to franco kernel . Is it enough installing zip using recovery or i have to do fresh install of the ROM.........
Thanks in advance.
I successfully rooted and achieved an unlocked bootloader with S-OFF on my Verizon HTC One M8 and also flashed TWRP 2.7.0.2. I downloaded a rom (without an SD card). I booted into recovery and i made a backup (not noticing that one of the lines read "unable to mount '/system". I then wiped and attempted to flash the rom only to find out that i can't find it in my file system. So i put the rom on an SD card and mounted it and tried to flash it, i get this message:
E: Unable to mount '/system'
E: Unable to open zip file.
Error Flashing zip '/external_sd/Roms?ViperOneM*_1.2.0.zip'
Updating partition details...
E: Unable to mount '/system'
So i'm stuck with a boot loader, an unmountable file system, and unable to flash a rom.
I've tried Fix permissions, I've tried mounting the "system" but all that mounts is 'cache' 'data' and 'micro SDcard'.
I hope my nerves are getting the best of me and i can't see something that's right in front of me!
Edit: Flashed CWM Recovery. Trying to install ROM from SD Card results in "Installation Aborted". When i try to side load it hangs at 81%.
Did you flash TWRP using terminal emulator mode as described on the official website for 2.7.0.2? If so you overwrote the system partition. Try flashing the recovery using the fastboot method as this will put the recovery in the right place. Then boot into the bootloader, choose recovery. I think this will get you TWRP in the recovery partition. Once there try flashing a ROM (although o would suggest something closer to stock like Skyfall).
I think what is happening is since the instructions for flashing TWRP via terminal emulator list the wrong partition, when you boot up to system it seems like you are booting to recovery because TWRP shows up. But you're actually on the system partition so when you try to flash a ROM you get an error because you can't mount the partition you're in.
I'm far from an expert in any of this so anyone who is please correct me.
dsEVOlve said:
Did you flash TWRP using terminal emulator mode as described on the official website for 2.7.0.2? If so you overwrote the system partition. Try flashing the recovery using the fastboot method as this will put the recovery in the right place. Then boot into the bootloader, choose recovery. I think this will get you TWRP in the recovery partition. Once there try flashing a ROM (although o would suggest something closer to stock like Skyfall).
I think what is happening is since the instructions for flashing TWRP via terminal emulator list the wrong partition, when you boot up to system it seems like you are booting to recovery because TWRP shows up. But you're actually on the system partition so when you try to flash a ROM you get an error because you can't mount the partition you're in.
I'm far from an expert in any of this so anyone who is please correct me.
Click to expand...
Click to collapse
I did flash TWRP as described. I used Terminal from my Macbook. I did some researching and i did try flashing using the fast boot method. I'm just so stumped!
First of all you aren't bricked. Have you tried using side load to flash the ROM? Try flashing another recovery too.
Sent from my HTC6525LVW using Tapatalk
SimplyNando said:
I did flash TWRP as described. I used Terminal from my Macbook. I did some researching and i did try flashing using the fast boot method. I'm just so stumped!
Click to expand...
Click to collapse
The above suggestion to try and Sideload the ROM install is a good idea. Basically, put the ROM zip file in your platform-tools folder of adb. Then boot to TWRP recovery, choose "sideload" and then issue the command "adb sideload [filename.zip]" (Instructions are found HERE.)
If that doesn't work, have you tried flashing Clockwork Recovery? You may have better luck with that in regards to mounts and/or flashing the ROM...
There's always USB OTG as well
Sent from my HTC6525LVW using Tapatalk
I found THIS thread (for ASUS Transformer though).
What may have happened (if I'm reading the above thread correctly) is that your /system doesn't exist.
Taking a complete stab at a fix, you may be able to use fastboot to flash a working "system.img" file. (Anyone with more expertise, please confirm or refute this...)
EDIT: Found THIS post in the "Official" TWRP release 2.7.0.0 thread I wonder if perhaps this is what happened to you?
WorldOfJohnboy said:
I found THIS thread (for ASUS Transformer though).
What may have happened (if I'm reading the above thread correctly) is that your /system doesn't exist.
Taking a complete stab at a fix, you may be able to use fastboot to flash a working "system.img" file. (Anyone with more expertise, please confirm or refute this...)
EDIT: Found THIS post in the "Official" TWRP release 2.7.0.0 thread I wonder if perhaps this is what happened to you?
Click to expand...
Click to collapse
That does seem like it could be the problem. I just flashed CWM recovery instead but it's still the sam problem. Still can't flash a rom, i also tried using sideboot.
SimplyNando said:
That does seem like it could be the problem. I just flashed CWM recovery instead but it's still the sam problem. Still can't flash a rom, i also tried using sideboot.
Click to expand...
Click to collapse
You might have to find a factory image, an RUU I am not sure if one exists but it will write the partitions. I think somehow your actual system partition was erased which is why it cannot be mounted. Pretty much, your only hope is an RUU or a zipped factory image.
123421342 said:
You might have to find a factory image, an RUU I am not sure if one exists but it will write the partitions. I think somehow your actual system partition was erased which is why it cannot be mounted. Pretty much, your only hope is an RUU or a zipped factory image.
Click to expand...
Click to collapse
I wouldn't be able to get that from the system dump located http://forum.xda-developers.com/showthread.php?t=2695171 ? Is there any other possible explanation??
SimplyNando said:
I wouldn't be able to get that from the system dump located http://forum.xda-developers.com/showthread.php?t=2695171 ? Is there any other possible explanation??
Click to expand...
Click to collapse
no because it is not a flashable zip. Factory image or RUU means the bootloader will literally write the partition. Recovery will mount the partition and write information to it. It cannot create the partition itself which I think is your issue.
Assuming your recovery is fine..this is what I did to fix my self inflicted "soft brick" on Saturday...I mistakenly hit format system instead of just data and cache while trying to start over.
I am running cwm 6047..and for whatever reason the sideload failed with an error trying to sideload flash sky fall.
So I did an adb push skyfall.zip /sdcard/0 and was then able to flash the zip from internal storage.
Hope that helps with your situation.
bakemcbride21 said:
Assuming your recovery is fine..this is what I did to fix my self inflicted "soft brick" on Saturday...I mistakenly hit format system instead of just data and cache while trying to start over.
I am running cwm 6047..and for whatever reason the sideload failed with an error trying to sideload flash sky fall.
So I did an adb push skyfall.zip /sdcard/0 and was then able to flash the zip from internal storage.
Hope that helps with your situation.
Click to expand...
Click to collapse
Yep. You have a bad download. Download a new ROM on your computer...boot to recovery and do a adb sideload or push
Sent from my HTC One M8
Just had a thought... did you flash the insecure Kernel (found HERE) ever? You may not have a writeable /system?
Flash the Kernel, then reflash the official TWRP (both in Fastboot) and see if that works...
WorldOfJohnboy said:
Just had a thought... did you flash the insecure Kernel (found HERE) ever? You may not have a writeable /system?
Flash the Kernel, then reflash the official TWRP (both in Fastboot) and see if that works...
Click to expand...
Click to collapse
Kernel runs inside the rom and the system becomes writeable in the ROM so that won't do anything. I'm pretty convinced he is missing the partition.
Sent from my HTC6525LVW using Tapatalk
Hi did you manage to sort this issue out as i'm having the same issue. it won't install backups or open zip files of the rom's. no matter what i do it won't flash the rom's. i've tried side loading on both cwm and TWRP - as i just said swapped from both recoveries. Managed to mount the sd card and put a new rom on it but won't flash from there and I've tried to move it to internal but fails.
I can't find my stock recovery an a nandroid back up either. Any help would be great
thanks
---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------
Oh it does let me flash a Kernal zip tho?
jerico9 said:
Hi did you manage to sort this issue out as i'm having the same issue. it won't install backups or open zip files of the rom's. no matter what i do it won't flash the rom's. i've tried side loading on both cwm and TWRP - as i just said swapped from both recoveries. Managed to mount the sd card and put a new rom on it but won't flash from there and I've tried to move it to internal but fails.
I can't find my stock recovery an a nandroid back up either. Any help would be great
thanks
---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------
Oh it does let me flash a Kernal zip tho?
Click to expand...
Click to collapse
did you try formatting internal yet?
Just for anyone withthe same issue. It ended up being not dnough memory to flash the recovery or the new rom....deerrrrrrr!!!
Haha, cant believe it had me stumped for 5 days trying everything and anything. Formatting would have helped aswell So thanks for the suggestion
jerico9 said:
Just for anyone withthe same issue. It ended up being not dnough memory to flash the recovery or the new rom....deerrrrrrr!!!
Haha, cant believe it had me stumped for 5 days trying everything and anything. Formatting would have helped aswell So thanks for the suggestion
Click to expand...
Click to collapse
I have an HTC version of fastboot/adb that will work on a low memory pc. It's posted in my ruu thread.
dottat said:
I have an HTC version of fastboot/adb that will work on a low memory pc. It's posted in my ruu thread.
Click to expand...
Click to collapse
I mean the device memory was low, so couldn't flash as no room on the device
Moto G7 river xt1962-1 firmware 29.114-16-5
firmware_moto-g7_river_xt1962-1_29.114-16-5_copyparts
will be needed for custom roms
firmware_moto-g7_river_xt1962-1_29.114-16-5_full
is all partitions, not required for custom roms, just for curious developers
windows users will need to make their own .bat files I don't use windows
two things:
1. working on twrp for river
2. working on lineageos 16 for river based on payton... errors with some vendor files
actually errors all over
please help I have two newborns and only get a few minutes to myself each night
good luck on building lineage, the g6 never had any development so i dont anticipate the g7 will get much either. if i was you id concentrate on twrp so we can at least flash gsi based roms.
Is this the original factory signed rom? (I.e. is it possible to fully flash and relock bootloader?)
Also wondering if anyone has the latest full rom (29.114-16-7).
Thanks in advance!
ptn107 said:
Moto G7 river xt1962-1 firmware 29.114-16-5
firmware_moto-g7_river_xt1962-1_29.114-16-5_copyparts
will be needed for custom roms
firmware_moto-g7_river_xt1962-1_29.114-16-5_full
is all partitions, not required for custom roms, just for curious developers
windows users will need to make their own .bat files I don't use windows
two things:
1. working on twrp for river
2. working on lineageos 16 for river based on payton... errors with some vendor files
actually errors all over
please help I have two newborns and only get a few minutes to myself each night
Click to expand...
Click to collapse
Confirmed that at least boot.img is correctly signed. You rock ptn107!! However I did confirm (from the version number displayed in recovery) that this is 29.114.16 and not 29.114.16-5.
How were you able to extract the partitions? Specifically boot.img. If I can learn that, then it would be easy to unroot, take OTA updates, copy and save boot.img, and patch with Magisk. Thanks in advance!!!
smokinu said:
Confirmed that at least boot.img is correctly signed. You rock ptn107!! However I did confirm (from the version number displayed in recovery) that this is 29.114.16 and not 29.114.16-5.
How were you able to extract the partitions? Specifically boot.img. If I can learn that, then it would be easy to unroot, take OTA updates, copy and save boot.img, and patch with Magisk. Thanks in advance!!!
Click to expand...
Click to collapse
The boot image version does not change with every little update. For every version of 29.114.16-* released it will be the same boot.img. 29.114.16-7 is getting around and most likely uses the exact same boot.img as ours.
As for extracting the .img files I use a linux shell script I wrote here. Makes doing this quick with each new firmware image.
It needs to be placed in /sdcard on your device (root is required to work):
Code:
adb push mkimg.sh /sdcard/
adb shell
cd /sdcard/
su -c sh ./mkimg.sh
I do this in Linux. Not much of a Windows user anymore.
Output files go into /sdcard/firmware-images but you can change that with the 'outfolder' variable if you wish.
Long story short it takes the list of partitions from /dev/block/bootdevice/by-name/ and uses 'dd' to create the .img.
If you are looking to just get a boot.img from our device and nothing else the command would be as follows (needs root):
Code:
su dd if=/dev/block/mmcblk0p41 of=/sdcard/boot.img > /dev/null 2>&1
ptn107,
Thanks for the write-up. I'm familiar with a similar approach using TWRP (booted, but not installed) and dd copying the individual partitions. I will give your script a try. Should save a lot of time!
Is there a way to copy partitions without root? My biggest concern is taking on an OTA update (currently 16-7), without having the original signed images to revert back to stock and relock the bootloader. Motorola has historically been bad at providing factory roms. If there is a clever way to unroot, take an OTA, save original, and re-root....I'd be a happy camper!
/dev is user root and group root so root is necessary.
Is there a clever way to take an OTA update and get a copy of the new boot.img? From what i understand, you have to unroot to take an OTA update.
BTW...good luck with the newborns!! Mine is now 3 and is still as much of a handful as when he was a newborn.
ptn107 said:
The boot image version does not change with every little update. For every version of 29.114.16-* released it will be the same boot.img. 29.114.16-7 is getting around and most likely uses the exact same boot.img as ours.
As for extracting the .img files I use a linux shell script I wrote here. Makes doing this quick with each new firmware image.
It needs to be placed in /sdcard on your device (root is required to work):
Code:
adb push mkimg.sh /sdcard/
adb shell
cd /sdcard/
su -c sh ./mkimg.sh
I do this in Linux. Not much of a Windows user anymore.
Output files go into /sdcard/firmware-images but you can change that with the 'outfolder' variable if you wish.
Long story short it takes the list of partitions from /dev/block/bootdevice/by-name/ and uses 'dd' to create the .img.
If you are looking to just get a boot.img from our device and nothing else the command would be as follows (needs root):
Code:
su dd if=/dev/block/mmcblk0p41 of=/sdcard/boot.img > /dev/null 2>&1
Click to expand...
Click to collapse
Boot img sometimes changes, you never know. I bricked a g6 by flashing a boot img that the last number in the version was 2 instead of 4. Flashed, and got stuck in a bootloop. Had to completely reflash stock firmware, then took an OTA that bricked it.
clcombs262 said:
Boot img sometimes changes, you never know. I bricked a g6 by flashing a boot img that the last number in the version was 2 instead of 4. Flashed, and got stuck in a bootloop. Had to completely reflash stock firmware, then took an OTA that bricked it.
Click to expand...
Click to collapse
I did confirm that the boot.img between 16 and 16-5 is different. The recovery mode displays the correct version for each of the boot.imgs, and MD5 checksums are different, although same file size.
That being said, flashing a 16 boot.img on a 16-5 device will mearly result in bootloop until the correct version is flashed. People should keep track of which slot they loaded the boot.img into (A/B).
smokinu said:
I did confirm that the boot.img between 16 and 16-5 is different. The recovery mode displays the correct version for each of the boot.imgs, and MD5 checksums are different, although same file size.
That being said, flashing a 16 boot.img on a 16-5 device will mearly result in bootloop until the correct version is flashed. People should keep track of which slot they loaded the boot.img into (A/B).
Click to expand...
Click to collapse
Code:
fastboot oem lock
doesn't work with PPO29.114-16-5
says boot.img is not signed
update: same for PPO29.114-16 and PPO29.80-61
ptn107 said:
Code:
fastboot oem lock
doesn't work with PPO29.114-16-5
says boot.img is not signed
update: same for PPO29.114-16 and PPO29.80-61
Click to expand...
Click to collapse
I saw the same thing on my end at first. Found this to work repeatedly....
fastboot oem lock (enter this a few times until i says something to the effect of...."you still need to flash a signed boot.img")
fastboot flash boot boot.img (this will now flash fine without saying the image is not signed)
fastboot oem lock (if you prefer to re-lock. You'll need the unlock key again if you plan to unlock).
smokinu said:
I saw the same thing on my end at first. Found this to work repeatedly....
fastboot oem lock (enter this a few times until i says something to the effect of...."you still need to flash a signed boot.img")
fastboot flash boot boot.img (this will now flash fine without saying the image is not signed)
fastboot oem lock (if you prefer to re-lock. You'll need the unlock key again if you plan to unlock).
Click to expand...
Click to collapse
Wow. That actually worked. I had to do both commands like 6 times one after the other but it worked.
Thank you!
No problem! Glad I could help. Found that one by accident.
smokinu said:
No problem! Glad I could help. Found that one by accident.
Click to expand...
Click to collapse
I would have never found that out.
fastboot without root
I have been foolish and used twrp to wipe my G7. I am trying to use twrp to flash or fastboot update provided in this thread but neither approach works.
error is invalid zip file.
I was running -7 not -5
as in my title, there is no root. and because of my stupidity, no OS either! I am happy to give any details
Any help would be amazing. Thanks in advance!
Mr_navillus said:
I have been foolish and used twrp to wipe my G7. I am trying to use twrp to flash or fastboot update provided in this thread but neither approach works.
error is invalid zip file.
I was running -7 not -5
as in my title, there is no root. and because of my stupidity, no OS either! I am happy to give any details
Any help would be amazing. Thanks in advance!
Click to expand...
Click to collapse
The zip file itself cannot be flashed as it's not in proper update format. You'll have to extract and flash the contents via fastboot. To get to fastboot, power off the device then hold power and volume down until you see the bootloader screen, and then connect it via USB to a pc
Follow the instructions here to get back to stock
Mr_navillus said:
I have been foolish and used twrp to wipe my G7. I am trying to use twrp to flash or fastboot update provided in this thread but neither approach works.
error is invalid zip file.
I was running -7 not -5
as in my title, there is no root. and because of my stupidity, no OS either! I am happy to give any details
Any help would be amazing. Thanks in advance!
Click to expand...
Click to collapse
Sounds like you wiped the system partition then tried to flash the unflashable zip file (hence, no system)
First, always make backups.
Second, you can still get into fastboot and manually update/restore
You can also use the moto software to recover the device.
Get it into fastboot, start from there. It is 100% an easy recovery process
warBeard_actual said:
You can also use the moto software to recover the device.
Click to expand...
Click to collapse
This fixed it in a jiffy. Making backups from now on!
Question to the experts:
Unlocking the bootloader and rooting a phone is stressful times for those of us who (like me) only do this once every few years when we buy a new phone. On some phones, after attempts at routing, I've been stuck for days without a phone till some distant helpful person helped me back to a working rooted phone. Other times it was very simple. But the experience leaves you scared.
Yes I know it's my own (and similar other uneducated) fault because we did something wrong that would be obvious to any expert. But it happens to the rest of us no matter how many threads we read.
So my question is, if the phone becomes non functional following erroneous commands or files (my own unintentional error), will this same 'moto recovery' restore things?
Where do I find out more 'how' to use this Moto software and where this 'Moto software recovery' is to be found?
Thank you.
Edit
Just to clarify things, this is my first Moto phone which is why I don't know what the Moto software recovery is. Is it what you get by pressing Power-volume down?