Related
I'm new to rooting and android in general. I'm currently running 4.4 rooted with stock I believe. Says ponury kernal in my settings.
I'm trying to flash the update for 4.4.2 via the TWRP install. I get a failed error: error executing updater binary in zip.
I've made sure my zip is the 4.4 to 4.4.2 but still no luck. Any ideas what I can do? Do I need to wipe something before I can put it on there?
On a first thought, you need to get back to the original kernel.
Update from 4.4.1 to .4.4.2. has no problems with different kernels installed, however this won't work from 4.4. to 4.4.2.
The exact error message would be also helpful
tom1807 said:
On a first thought, you need to get back to the original kernel.
Update from 4.4.1 to .4.4.2. has no problems with different kernels installed, however this won't work from 4.4. to 4.4.2.
The exact error message would be also helpful
Click to expand...
Click to collapse
The error was : error executing updater binary in zip. I will look into getting back to stock.
matthewordie said:
The error was : error executing updater binary in zip. I will look into getting back to stock.
Click to expand...
Click to collapse
You need to fastboot flash the system and boot image from 4.4 if you have a custom kernel. Then flash the update
jd1639 said:
You need to fastboot flash the system and boot image from 4.4 if you have a custom kernel. Then flash the update
Click to expand...
Click to collapse
How do I fastboot flash the system and boot image? Can I do that from TWRP or do I need to use the command line with the fastboot? I have fastboot installed on my mac already. I was playing with that as well.
matthewordie said:
How do I fastboot flash the system and boot image? Can I do that from TWRP or do I need to use the command line with the fastboot? I have fastboot installed on my mac already. I was playing with that as well.
Click to expand...
Click to collapse
You'll need to get the factory image and extract the files. Inside there is another zip file which you'll need to extract. That's where you'll find the images. Use fastboot flash system system.img The Mac command is slightly different, I don't remember exactly what it is. To fastboot boot its the similar format
jd1639 said:
You'll need to get the factory image and extract the files. Inside there is another zip file which you'll need to extract. That's where you'll find the images. Use fastboot flash system system.img The Mac command is slightly different, I don't remember exactly what it is. To fastboot boot its the similar format
Click to expand...
Click to collapse
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
matthewordie said:
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
Click to expand...
Click to collapse
then stop modding your phone if you want OTAs.
its really that simple.
just flash the 4.4.2 factory images.
matthewordie said:
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
Click to expand...
Click to collapse
Flashing the system image won't wipe anything
http://forum.xda-developers.com/showthread.php?p=14
Sent from my Nexus 5 using Tapatalk
Zepius said:
then stop modding your phone if you want OTAs.
its really that simple.
just flash the 4.4.2 factory images.
Click to expand...
Click to collapse
Well I really don't know the exact steps involved in "flashing the image". That's what I'm asking.
jd1639 said:
Flashing the system image won't wipe anything
Click to expand...
Click to collapse
Then I guess I had the wrong impression of what flashing the image is. Is there a guide available?
matthewordie said:
Then I guess I had the wrong impression of what flashing the image is. Is there a guide available?
Click to expand...
Click to collapse
Follow method#2. But only flash the system.img and boot.img. http://forum.xda-developers.com/showthread.php?p=47156064
Edit, your bootloader is unlocked, right? If not then you will lose all you data unlocking it
jd1639 said:
Follow method#2. But only flash the system.img and boot.img. http://forum.xda-developers.com/showthread.php?p=47156064
Edit, your bootloader is unlocked, right? If not then you will lose all you data unlocking it
Click to expand...
Click to collapse
Ah, I was close I actually did method 1. Yeah I did leave it unlocked since i'm going to root again right away. Thanks
I know this is the wrong place to post this, but everywhere else tells I can't. So here goes:
I've a T300 with AndroidBlue 3.0 and JB 4.1.1 on nit. Web browsing is typically slow.
I need to up TWRP from 2.2 to the latest and greatest, and would like some input as to whether or not going with CM 10.1 would help my "Browsing Experience"?
It seems that Rom Toolbox would take care of installing CM (or from TWRP), and TWRP Manager (with the right file - it dl's the ICS version) would take care of that.
Correct?
I'm sure this has been discussed before, but searching has yielded pages and pages that do not help.
All help have my thanks in advance.
RBraverman said:
I know this is the wrong place to post this, but everywhere else tells I can't. So here goes:
I've a T300 with AndroidBlue 3.0 and JB 4.1.1 on nit. Web browsing is typically slow.
I need to up TWRP from 2.2 to the latest and greatest, and would like some input as to whether or not going with CM 10.1 would help my "Browsing Experience"?
It seems that Rom Toolbox would take care of installing CM (or from TWRP), and TWRP Manager (with the right file - it dl's the ICS version) would take care of that.
Correct?
I'm sure this has been discussed before, but searching has yielded pages and pages that do not help.
All help have my thanks in advance.
Click to expand...
Click to collapse
OK so first you have to update that ancient bootloader of yours to use KitKat. Do that by flashing the latest Stock ROM via fastboot.
cmendonc2 said:
OK so first you have to update that ancient bootloader of yours to use KitKat. Do that by flashing the latest Stock ROM via fastboot.
Click to expand...
Click to collapse
Thank you for answering - I've been ill since I wrote that, so I'm finally getting back to you. I'm looking at ASUS's site, as I can not find my build number (AndroidBlue over-wrote that in status) - but this is a US version, so I'm assuming 10.6.1.27.1 US SKU?
Can I not flash this via TRWP - I'm assuming Fastboot, just as when I flashed TWRP.
When I flash this will everything be back to stock: no root, no TWRP?
RBraverman said:
Thank you for answering - I've been ill since I wrote that, so I'm finally getting back to you. I'm looking at ASUS's site, as I can not find my build number (AndroidBlue over-wrote that in status) - but this is a US version, so I'm assuming 10.6.1.27.1 US SKU?
Can I not flash this via TRWP - I'm assuming Fastboot, just as when I flashed TWRP.
When I flash this will everything be back to stock: no root, no TWRP?
Click to expand...
Click to collapse
Hope you get getter
10.6.1.27.1 Will work, and I suggest flashing with fastboot so you can confirm that fastboot works so you can reflash TWRP later. When you do flash the 10.6.1.27.1 stock, everything will be erased, including TWRP, so you will have to flash a newer version of TWRP. That can be the stable branch here: http://forum.xda-developers.com/showthread.php?t=2772093
cmendonc2 said:
Hope you get getter
Click to expand...
Click to collapse
Thank you, slowly on the mend.
cmendonc2 said:
10.6.1.27.1 Will work, and I suggest flashing with fastboot so you can confirm that fastboot works so you can reflash TWRP later. When you do flash the 10.6.1.27.1 stock, everything will be erased, including TWRP, so you will have to flash a newer version of TWRP. That can be the stable branch here: http://forum.xda-developers.com/showthread.php?t=2772093
Click to expand...
Click to collapse
I don't see the "THANKS" button.......
Ok, so if I do this I LITERALLY start over, and should ASUS up another F/W version, I do this all over - correct?
Here's the REAL crux of the matter; I like the unit as it is EXCEPT that half the day the wifi sucks, either via 3g phone or RV park WiFi which I built! I'm getting closer to the reason for this, close my Dell 6400 down and the WiFi gets better, so interference.
OVERALL, would upping this one (I have 2) make any perceptible difference on the WiFi? I mean all else is fine.
So I need 3 things: newest F/W (have), Latest TWRP(don't have - yet but looking, 2.7 I believe), latest way to root(don't know) - Correct?
Again where is that thanks button!!!!!
RBraverman said:
I don't see the "THANKS" button.......
Ok, so if I do this I LITERALLY start over, and should ASUS up another F/W version, I do this all over - correct?
Here's the REAL crux of the matter; I like the unit as it is EXCEPT that half the day the wifi sucks, either via 3g phone or RV park WiFi which I built! I'm getting closer to the reason for this, close my Dell 6400 down and the WiFi gets better, so interference.
OVERALL, would upping this one (I have 2) make any perceptible difference on the WiFi? I mean all else is fine.
Again where is that thanks button!!!!!
Click to expand...
Click to collapse
Thanks button is below the username at the end of the post
Upping the tf300 would make the pages load faster on the tablet after they have downloaded, and would make Chrome or whatever other browser you are using load the page much faster. It would unlikely change the download speed to the tablet.
It's also unlikely that Asus will release another FW version because the tf300 is already 2 or 3 years old and they tend to cut support after that time. Then again, they could release an update tomorrow for no reason, but that doesn't mean the bootloader has to change requiring you to flash stock again. I updated my stock FW a more than a year ago and there has been 2 or 3 updates since that, but the bootloader hasn't changed so I haven't done any of those updates.
cmendonc2 said:
Thanks button is below the username at the end of the post
Upping the tf300 would make the pages load faster on the tablet after they have downloaded, and would make Chrome or whatever other browser you are using load the page much faster. It would unlikely change the download speed to the tablet.
It's also unlikely that Asus will release another FW version because the tf300 is already 2 or 3 years old and they tend to cut support after that time. Then again, they could release an update tomorrow for no reason, but that doesn't mean the bootloader has to change requiring you to flash stock again. I updated my stock FW a more than a year ago and there has been 2 or 3 updates since that, but the bootloader hasn't changed so I haven't done any of those updates.
Click to expand...
Click to collapse
NOW it's there!
Okay upping to stock F/W, looking for TWRP (openrecovery-twrp-2.6.3.0-tf300tg-JB.img) then how do I root this
RBraverman said:
NOW it's there!
Okay upping to stock F/W, looking for TWRP - how do I root this
Click to expand...
Click to collapse
Flash the Android 4.2 update via fastboot: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.1: http://forum.xda-developers.com/showthread.php?t=1949758
Then Flash the TWRP: http://forum.xda-developers.com/showthread.php?t=2772093
Then flash the KK rom you want in the Android Dev section, such as CM or CROM or PAC or KatKiss, etc.
cmendonc2 said:
Flash the Android 4.2 update via fastboot: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.1: http://forum.xda-developers.com/showthread.php?t=1949758
Then Flash the TWRP: http://forum.xda-developers.com/showthread.php?t=2772093
Then flash the KK rom you want in the Android Dev section, such as CM or CROM or PAC or KatKiss, etc.
Click to expand...
Click to collapse
Ya know I documented the WHOLE business when I did all this the 1st and 2nd and 3rd time, especially when the system can't find the device. Now I can't find it - I have the drivers, but no docs.
************************************** edit *********************************
I need to be able to translate this so I can understand. These are the steps:
fastboot -i 0x0b05 flash blob.blob (extracted from TF300T-US_epad-10_6_1_27_1-UpdateLauncher )
fastboot -i 0x0b05 flash openrecovery-twrp-2.6.3.0-tf300tg-JB
{then root by installing root-signed.zip}?
fastboot -i 0x0b0g flash {custom ROM is desired} - Does KitKat root it?
RBraverman said:
Ya know I documented the WHOLE business when I did all this the 1st and 2nd and 3rd time, especially when the system can't find the device. Now I can't find it - I have the drivers, but no docs.
************************************** edit *********************************
I need to be able to translate this so I can understand. These are the steps:
fastboot -i 0x0b05 flash blob.blob (extracted from TF300T-US_epad-10_6_1_27_1-UpdateLauncher )
fastboot -i 0x0b05 flash openrecovery-twrp-2.6.3.0-tf300tg-JB
{then root by installing root-signed.zip}?
fastboot -i 0x0b0g flash {custom ROM is desired} - Does KitKat root it?
Click to expand...
Click to collapse
Code:
fastboot -i 0x0b05 flash blob.blob
(extracted from TF300T-US_epad-10_6_1_27_1-UpdateLauncher )
Reboot tablet.
Use this TWRP: http://d-h.st/e9H. The one you selected would have bricked the tablet.
Code:
fastboot -i 0x0b05 flash recovery [TWRP file]
Reboot Tablet.
(The custom ROM is already rooted for you with the exception of Omni ROM)
Copy ROM to SDcard, flash in TWRP to confirm it works.
I would strongly recommend using KitKat over CM10.1 because KitKat is much mroe optimized for older devices, and you should see a performance upgrade.
cmendonc2 said:
Code:
fastboot -i 0x0b05 flash blob.blob
(extracted from TF300T-US_epad-10_6_1_27_1-UpdateLauncher )
Reboot tablet.
Use this TWRP: http://d-h.st/e9H. The one you selected would have bricked the tablet.
Click to expand...
Click to collapse
That was the one I wasn't sure about - I dl'd another that I was more confident in and it turned out to be this ine - THANKS AGAIN.
cmendonc2 said:
Code:
fastboot -i 0x0b05 flash recovery [TWRP file]
Reboot Tablet.
(The custom ROM is already rooted for you with the exception of Omni ROM)
Copy ROM to SDcard, flash in TWRP to confirm it works.
I would strongly recommend using KitKat over CM10.1 because KitKat is much more optimized for older devices, and you should see a performance upgrade.
Click to expand...
Click to collapse
Which version of KitKat would the most stable?
AGAIN MANY THANKS! (as he begins to flash the stock rom)
********************************* oops ****************************
This is what I get:
C:\adb>fastboot devices
015d2994ca10140f fastboot
C:\adb>fastboot -i 0x0b05 flash blob.blob
unknown partition 'blob.blob'
error: cannot determine image filename for 'blob.blob'
C:adb>\
This with the unit ready to go, in "starting fastboot USB download protocol"
I have tried to change the name with the same result.
Am re-downloading as "I" speak.
RBraverman said:
That was the one I wasn't sure about - I dl'd another that I was more confident in and it turned out to be this ine - THANKS AGAIN.
Which version of KitKat would the most stable?
AGAIN MANY THANKS! (as he begins to flash the stock rom)
********************************* oops ****************************
This is what I get:
C:\adb>fastboot devices
015d2994ca10140f fastboot
C:\adb>fastboot -i 0x0b05 flash blob.blob
unknown partition 'blob.blob'
error: cannot determine image filename for 'blob.blob'
C:adb>\
This with the unit ready to go, in "starting fastboot USB download protocol"
I have tried to change the name with the same result.
Am re-downloading as "I" speak.
Click to expand...
Click to collapse
Use the extracted stock blob with this command:
Code:
fastboot -i 0x0b05 flash system blob.blob
cmendonc2 said:
Use the extracted stock blob with this command:
Code:
fastboot -i 0x0b05 flash system blob.blob
Click to expand...
Click to collapse
Found my notes and kept reading system blob.blob, as renaming it to system.blob - gotta get new glasses.
Waiting for the media databases to upgrade.
Flash extract img from "CUSTOM_TWRP_JB_KK_v2.7_STABLE_TF300T"? to be sure
Just rebooted, and it's 4.2.1, but everything I had - most of what I had, is still there!?! And the run?
RBraverman said:
Found my notes and kept reading system blob.blob, as renaming it to system.blob - gotta get new glasses.
Waiting for the media databases to upgrade.
Flash extract img from "CUSTOM_TWRP_JB_KK_v2.7_STABLE_TF300T"? to be sure
Click to expand...
Click to collapse
Yes the img from "CUSTOM_TWRP_JB_KK_v2.7_STABLE_TF300T" like this:
Code:
fastboot -i 0x0b05 flash recovery twrp.img
Dont forget to reboot after flashing the stock ROM and reboot after flashing twrp.
cmendonc2 said:
Yes the img from "CUSTOM_TWRP_JB_KK_v2.7_STABLE_TF300T" like this:
Code:
fastboot -i 0x0b05 flash recovery twrp.img
Dont forget to reboot after flashing the stock ROM and reboot after flashing twrp.
Click to expand...
Click to collapse
This should be the last question as the latest everything is on - no sweat really - bugged the hell out of your patience because I couldn't find my bloody notes till now.
So, the which KitKat (after a wipe) is the most stable - I've read through http://forum.xda-developers.com/showthread.php?t=2686228 and it would seem that the only obvious choice would be http://forum.xda-developers.com/showthread.php?t=2686228, but I can't/don't see the file!
RBraverman said:
This should be the last question as the latest everything is on - no sweat really - bugged the hell out of your patience because I couldn't find my bloody notes till now.
So, the which KitKat (after a wipe) is the most stable - I've read through http://forum.xda-developers.com/showthread.php?t=2686228 and it would seem that the only obvious choice would be http://forum.xda-developers.com/showthread.php?t=2686228, but I can't/don't see the file!
Click to expand...
Click to collapse
Thats the ROM I keep my tablet on during the school year, the download for the latest build is here: http://forum.xda-developers.com/devdb/project/dl/?id=7893.
cmendonc2 said:
Thats the ROM I keep my tablet on during the school year, the download for the latest build is here: http://forum.xda-developers.com/devdb/project/dl/?id=7893.
Click to expand...
Click to collapse
That's the problem - WAY too many links ... I'm downloading the one in you response but that would be the latest CM nightly - correct?
I would rather have the most stable KitKat, as you've stated that works the best with my older devices. But which is the file for the T300?
SO, CROMi-X_DEODEX_5.4_Signed.zip as DEOdexed is a bit better. Now I assume as I can't do a nanobackup I can skip that , just do a Wipe Factory from TWRP.
I can't believe how easy this was when I did 4 different tablets and 2 phones and now ... maybe I was sicker than I thought.
RBraverman said:
That's the problem - WAY too many links ... I'm downloading the one in you response but that would be the latest CM nightly - correct?
I would rather have the most stable KitKat, as you've stated that works the best with my older devices. But which is the file for the T300?
SO, CROMi-X_DEODEX_5.4_Signed.zip as DEOdexed is a bit better. Now I assume as I can't do a nanobackup I can skip that , just do a Wipe Factory from TWRP.
I can't believe how easy this was when I did 4 different tablets and 2 phones and now ... maybe I was sicker than I thought.
Click to expand...
Click to collapse
I linked you to the latest build of CROMBi-kk, the updated version of CROMi. From the ROMs I have tested, it is the most stable KitKat ROM, assuming you don't want those cutting edge features.
cmendonc2 said:
I linked you to the latest build of CROMBi-kk, the updated version of CROMi. From the ROMs I have tested, it is the most stable KitKat ROM, assuming you don't want those cutting edge features.
Click to expand...
Click to collapse
Sorry misunderstood. While I've been waiting for the ROM to dl, I noticed that my notes have fastboot xxxxxxx boot recovery.img, yet mostly what I see is fastboot xxxxxx recovery recovery.img. I also noticed that when I do a Vol/Dn/Pwr I get the 3 icons and have to select RCK to get to TWRP - I haven't noticed that mentioned anywhere - did I screw up?
To be clear - I want wipe / and "swipe to factory reset) then flash KK.
I going to try VERY hard to leave you alone now - I have taken way too much advantage of your kindness in helping me.
RBraverman said:
Sorry misunderstood. While I've been waiting for the ROM to dl, I noticed that my notes have fastboot xxxxxxx boot recovery.img, yet mostly what I see is fastboot xxxxxx recovery recovery.img. I also noticed that when I do a Vol/Dn/Pwr I get the 3 icons and have to select RCK to get to TWRP - I haven't noticed that mentioned anywhere - did I screw up?
To be clear - I want wipe / and "swipe to factory reset) then flash KK.
I going to try VERY hard to leave you alone now - I have taken way too much advantage of your kindness in helping me.
Click to expand...
Click to collapse
I'm not sure what you are talking about with "fastboot xxxxxxx boot recovery.img, yet mostly what I see is fastboot xxxxxx recovery recovery.img". As long as TWRP is working you shouldn't have to use fastboot anymore.
The new bootloader that you upgraded to only has 3 icons when you press vol-down and power. Fastboot now connects automatically if you turn on your tablet with the USB plugged in and pressing the key combo. To access TWRP, selecting RCK is the correct choice. As always, never select the Wipe Data in the bootloader menu or you will brick.
Before flashing new ROMs, you should only have to do the "swipe to factory reset" option in the TWRP recovery. If you update your ROM with a newer version of that specific ROM, you only have to Wipe Cache and Dalvik Cache.
Is there a place where I can download (old) bootloaders?
Or do I just have to download a full ROM image, and extract the bootloader from there?
I want to flash a different bootloader without flashing anything else.
Which one are you looking for? And why flash an old bootloader???
Upgrade/downgrade of the BL is usually done through flashing the official firmware. You can do it in fastboot, but that's risky stuff... Why would you?
berndblb said:
Which one are you looking for? And why flash an old bootloader???
Click to expand...
Click to collapse
I have ICS installed on my /system partition, and the 10.6.1.14.40 bootloader I recently installed fails to boot the ICS kernel that I usually use. (It does boot Ubuntu however)
berndblb said:
Upgrade/downgrade of the BL is usually done through flashing the official firmware. You can do it in fastboot, but that's risky stuff... Why would you?
Click to expand...
Click to collapse
I have nvflash keys, so I like to live dangerously.
bsammon said:
I have ICS installed on my /system partition, and the 10.6.1.14.40 bootloader I recently installed fails to boot the ICS kernel that I usually use. (It does boot Ubuntu however)
I have nvflash keys, so I like to live dangerously.
Click to expand...
Click to collapse
I'll say....
I don't know of anyone collecting old bootloaders so you'll have to flash the system blob in fastboot I think.
Praetoriano had a collection of those: http://forum.xda-developers.com/showthread.php?t=1946456
AFAIK you cannot downgrade to anything earlier than 9.4.5.30. That was the last ICS version
berndblb said:
I'll say....
I don't know of anyone collecting old bootloaders
Click to expand...
Click to collapse
Now you do...
Code:
[email protected] ~/android/tf700/bootloaders $ ls blob.EBT*
blob.EBT.10.4.4.16 blob.EBT.10.4.4.23 blob.EBT.10.6.1.14.4-US blob.EBT.9.4.5.26
blob.EBT.10.4.4.18 blob.EBT.10.4.4.25-US blob.EBT.10.6.1.14.4-WW blob.EBT.9.4.5.30
blob.EBT.10.4.4.20 blob.EBT.10.6.1.14.10-WW blob.EBT.10.6.1.14.8-US
@bsammon: which one do you want?
_that said:
Now you do...
Code:
[email protected] ~/android/tf700/bootloaders $ ls blob.EBT*
blob.EBT.10.4.4.16 blob.EBT.10.4.4.23 blob.EBT.10.6.1.14.4-US blob.EBT.9.4.5.26
blob.EBT.10.4.4.18 blob.EBT.10.4.4.25-US blob.EBT.10.6.1.14.4-WW blob.EBT.9.4.5.30
blob.EBT.10.4.4.20 blob.EBT.10.6.1.14.10-WW blob.EBT.10.6.1.14.8-US
@bsammon: which one do you want?
Click to expand...
Click to collapse
Well.. I think I'd start with 9.4.5.30 -- in hopes that that is close enough to load my 9.4.5.26 kernel
And if that doesn't work, or if I'm feeling adventurous, I'd try the 9.4.5.26 image, and see if I can install it from the Flatline bootloader.
Or, you could send me all of them, and I'll find a website to host them on.
_that said:
Now you do...
Click to expand...
Click to collapse
LOL
Why am I not surprised? [emoji38]
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?
Hello guys, a brief introduction; All the Xiaomi devices running Miui roms out of the box have a dedicated firmware but I didn´t find for those based on Android One or atleast for Daisy.
Every rom requires a specific Firmware to work well so I´ll share the most used here.
This is intended to flash it as a base to avoid the tedious process to flash the whole rom through MiFlash tool.
But be advised although that some times could be required to do a clean flash through MiFlash tool, for some roms or to fix missed partitions being the case as happen too with all the rest of Xiaomi devices and some times flashing the firmware and the vendor from the same version through fastboot will be enough.
I hope that it´ll be useful, please hit thanks if it works, test it, report and share with others the results.
Download Link:
https://drive.google.com/open?id=1Bbt_aTOHABMYQQlVNTy7X0MVJBJoHqgJ
Dont work on daisy (android one)?:crying:
heyimvitor2 said:
Dont work on daisy (android one)?:crying:
Click to expand...
Click to collapse
They´re for Daisy, stock rom is Android One.
Are these just a repack of the fastboot ROMs available from xiaomi?
They are already listed here. And are .tar.gz rather than .zip
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
How to use it? Flash via twrp?
fastboot with miflash
a1291762 said:
Are these just a repack of the fastboot ROMs available from xiaomi?
They are already listed here. And are .tar.gz rather than .zip
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Click to expand...
Click to collapse
Fastboot rom is the whole rom including system, userdata, and more as you know to be flashed through fastboot directly or using a tool like MiFlash but these are not a repack but a flashable zip the way that all the update process to switch to other rom can be done while in TWRP.
Cause all my previous devices were running Miui they had available firmwares and never need to flash all the rom as a base for custom roms and since I bought this device I missed this feature.
Here you have a reference what I´m talking about https://xiaomifirmwareupdater.com
prodang2509 said:
How to use it? Flash via twrp?
Click to expand...
Click to collapse
Yes, as any flashable zip, recommendable as first step (as a base) after to make the wipes and before the other required steps.
dochdoc said:
fastboot with miflash
Click to expand...
Click to collapse
Nope, zips can´t be flashed through fastboot.
https://docs.google.com/spreadsheets/d/1Uy6qouIV0WbVouK4X5PhmUz2quxfLguHDqSf6LYDBO8/edit#gid=0
here you have all flashable stock trough miflash/fastboot
SubwayChamp said:
these are a flashable zip the way that all the update process to switch to other rom can be done while in TWRP.
Click to expand...
Click to collapse
I'm used to the fastboot ROMs but these may prove useful... Is there a process for converting a fastboot ROM into a twrp-flashable ROM?
a1291762 said:
I'm used to the fastboot ROMs but these may prove useful... Is there a process for converting a fastboot ROM into a twrp-flashable ROM?
Click to expand...
Click to collapse
If you refer to the whole rom yes, it does. Other Xiaomi devices have a fastboot (tar) and also a recovery (zip) but TWRP must be adapted to work with.
Thank you for this, it is really helpful.
Last night I played with offains TWRP 3.3.1-0 and restored a firmware backup, but it only got deleted and restoring failed.
Then I flashed your 10.3.0 file and all is good. You also put a custom dark splash.img in it, which I really like (was too lazy to create my own). :good:
Firmware 10.0.15
SubwayChamp said:
Hello guys, a brief introduction; All the Xiaomi devices running Miui roms out of the box have a dedicated firmware but I didn´t find for those based on Android One or atleast for Daisy.
Every rom requires a specific Firmware to work well so I´ll share the most used here.
This is intended to flash it as a base to avoid the tedious process to flash the whole rom through MiFlash tool.
But be advised although that some times could be required to do a clean flash through MiFlash tool, for some roms or to fix missed partitions being the case as happen too with all the rest of Xiaomi devices and some times flashing the firmware and the vendor from the same version through fastboot will be enough.
I hope that it´ll be useful, please hit thanks if it works, test it, report and share with others the results.
Download Link:
https://drive.google.com/open?id=1Bbt_aTOHABMYQQlVNTy7X0MVJBJoHqgJ
Click to expand...
Click to collapse
Do you have also the newest firmware 10.0.15? I have a bug with screen rotation (not longer works after a few hours), i hope firmware 10.0.15 is the solution because because I read that a screen rotation error is known.
counti said:
Do you have also the newest firmware 10.0.15? I have a bug with screen rotation (not longer works after a few hours), i hope firmware 10.0.15 is the solution because because I read that a screen rotation error is known.
Click to expand...
Click to collapse
Firmware is based on major updates i.e. on fastboot global images (full rom) when all partitions are modified but is not included in OTA updates (incremental rom) when mostly only system and vendor (sometimes also kernel) receive modifications but all the other partitions remain untouched.
To better understanding the three next OTA updates (v10.0.14.0, v10.0.15.0 and v10.0.16.0) are using as base v10.0.13.0 firmware.
Just appear the next full rom I will upload it but hopefully it is 10.
Great Job !
SubwayChamp said:
Hello guys, a brief introduction; All the Xiaomi devices running Miui roms out of the box have a dedicated firmware but I didn´t find for those based on Android One or atleast for Daisy.
Every rom requires a specific Firmware to work well so I´ll share the most used here.
This is intended to flash it as a base to avoid the tedious process to flash the whole rom through MiFlash tool.
But be advised although that some times could be required to do a clean flash through MiFlash tool, for some roms or to fix missed partitions being the case as happen too with all the rest of Xiaomi devices and some times flashing the firmware and the vendor from the same version through fastboot will be enough.
I hope that it´ll be useful, please hit thanks if it works, test it, report and share with others the results.
Download Link:
https://drive.google.com/open?id=1Bbt_aTOHABMYQQlVNTy7X0MVJBJoHqgJ
Click to expand...
Click to collapse
Hello Dear SubwayChamp,
It Will Be Very Helpful For US. Thank You Once Again...
Thanks for updating this to 10.0.13.
I wanted to create my own file and have some questions about the file emmc_appsboot.mbn
1. The updater script flashes the above file as an img file. Is it ok to just rename the mbn file or is a program like HxD Hex Editor needed?
2. In your 10.0.13 version there is only the mbn file but not the img file, is that ok? In your 10.0.3 file there is only the img file and in 10.0.9 there are both, so I'm a little confused.
I am seeing a few custom Android 10 roms out there, with the Android 9 base firmware, is not better wait for the android 10 base firmware? and the source code for the kernel.
Pat750 said:
Thanks for updating this to 10.0.13.
I wanted to create my own file and have some questions about the file emmc_appsboot.mbn
1. The updater script flashes the above file as an img file. Is it ok to just rename the mbn file or is a program like HxD Hex Editor needed?
2. In your 10.0.13 version there is only the mbn file but not the img file, is that ok? In your 10.0.3 file there is only the img file and in 10.0.9 there are both, so I'm a little confused.
Click to expand...
Click to collapse
Hi, I switched to other devices since I uploaded these files, anyway thanks for notice that, there was an error on the typo in versions 9, 12 and 13.
Xiaomi fastboot ROMs are mirrored on a lot of sites and I don´t remember now from where I downloaded it and I duplicated from inside the version 10.0.9, it wasn´t right, now all the files were re-uploaded and corrected.
As per mbn files can´t be simply renamed as image, you can look inside and change some values with a HEX editor but is not a good idea to make this without a solid knowledge so it may get corrupted and flashing a corrupted bootloader can seriously brick your device anyway don´t worry about so no need to change nothing, TWRP will place the images in the right places/partitions as they´re originally inside the fastboot ROMs.
SubwayChamp said:
Hi, I switched to other devices since I uploaded these files, anyway thanks for notice that, there was an error on the typo in versions 9, 12 and 13.
Xiaomi fastboot ROMs are mirrored on a lot of sites and I don´t remember now from where I downloaded it and I duplicated from inside the version 10.0.9, it wasn´t right, now all the files were re-uploaded and corrected.
As per mbn files can´t be simply renamed as image, you can look inside and change some values with a HEX editor but is not a good idea to make this without a solid knowledge so it may get corrupted and flashing a corrupted bootloader can seriously brick your device anyway don´t worry about so no need to change nothing, TWRP will place the images in the right places/partitions as they´re originally inside the fastboot ROMs.
Click to expand...
Click to collapse
Thank you. I see the changes.
Good luck with your new device. You did some good things here and helped people a lot.