I have done everything I can think of and I can't get the system partition to accept a script from a flash zip. I have tried different formats, templates everything.
I can't get anything related to assert lines to not error out. Flash fire says 'set_metadata' or 'set_metadata_recursive' isn't recognized so I can't set the permissions. I can flash the system directory and it's folders and files for the most part, but nothing in the by-name directory.
I have been able to successfully deodex the system image for the LVY48F source code, from the device 'shamu'. As a result, I've been able to port over a significant portion of that AOSP build without actually having to build anything yet. A lot of the stuff has ported without any modifications.
Unfortunately I can't get too much further if I can't get the system partition to accept any of the updater scripts. That will be a problem and actually getting a ROM off the ground. so any advice or assistance anyone can provide would be absolutely awesome and very much appreciated.
DragonFire1024 said:
I have done everything I can think of and I can't get the system partition to accept a script from a flash zip. I have tried different formats, templates everything.
I can't get anything related to assert lines to not error out. Flash fire says 'set_metadata' or 'set_metadata_recursive' isn't recognized so I can't set the permissions. I can flash the system directory and it's folders and files for the most part, but nothing in the by-name directory.
I have been able to successfully deodex the system image for the LVY48F source code, from the device 'shamu'. As a result, I've been able to port over a significant portion of that AOSP build without actually having to build anything yet. A lot of the stuff has ported without any modifications.
Unfortunately I can't get too much further if I can't get the system partition to accept any of the updater scripts. That will be a problem and actually getting a ROM off the ground. so any advice or assistance anyone can provide would be absolutely awesome and very much appreciated.
Click to expand...
Click to collapse
It is not normal, on my devices I have tried flashfire and I have installed a ROM it detects the set_metadata command and sets the permissions correctly. Have you checked the updater-script of the ROM? Can you post the updater-script?
Rortiz2 said:
It is not normal, on my devices I have tried flashfire and I have installed a ROM it detects the set_metadata command and sets the permissions correctly. Have you checked the updater-script of the ROM? Can you post the updater-script?
Click to expand...
Click to collapse
Well I just noticed this. And now I'm pretty passed off. I don't think we'll be able to flash a ROM...at all maybe. I hope this line from the last amazon update.bin doesn't mean what it says
Code:
block_image_update("/dev/block/platform/mtk-msdc.0/by-name/system"
Script one is the update.bin script and script 2 is the one I made. Going by the fire nexus ROM script. It shouldn't need to change much.
I believe HD 10's bootloader doesn't support such commands properly. Maybe you should look at how it was implemented in prerooted image for FlashFire.
Btw, block_image_update is a function implemented in android 5 and above for ota updates - it's just update system image block by block, that's where it got its name from. There is also a tool to modify such updates, you can read more here and the tool is called "Tool Unpack Repack DAT IMG", there are 3 versions of it already.
Though you shouldn't be able to flash such modified updates via official amazon recovery as it is checking updates somehow.
Maksfrai said:
I believe HD 10's bootloader doesn't support such commands properly. Maybe you should look at how it was implemented in prerooted image for FlashFire.
Btw, block_image_update is a function implemented in android 5 and above for ota updates - it's just update system image block by block, that's where it got its name from. There is also a tool to modify such updates, you can read more here and the tool is called "Tool Unpack Repack DAT IMG", there are 3 versions of it already.
Though you shouldn't be able to flash such modified updates via official amazon recovery as it is checking updates somehow.
Click to expand...
Click to collapse
So does flash fire support the flashing of a .dat? Couldn't we make a .dat, sign it or whatnot, turn it into a system.img and flash it in flash fire? This will be hard or impossible without the use of it. Not unless someone can modify or build an app like fireflash.apk (used to flash TWRP to the HD 8.9).
Just to be aware, I tried to use my trick to install the SystemUI. I can modify it like my framework, it installs and then I adb push the one from the factory image to over write it. Works with Settings APK, but not the SystemUI. Strange.
DragonFire1024 said:
So does flash fire support the flashing of a .dat? Couldn't we make a .dat, sign it or whatnot, turn it into a system.img and flash it in flash fire?
Click to expand...
Click to collapse
Not sure about .dat only, unless you'll pack it back with system.transfer.list, file_contexts and so on (FlashFire actually supports block-based OTAs, it would be strange if it couldn't flash typical OTA update), but I never tried that. Besides, the previously mentioned tool supports repacking system.img as well starting from v2. I took system.img from prerooted 5.6.2.0 firmware by retyre and successfully repacked it with some modified files - though I didn't flash it (don't want to mess with my HD 10 yet). Can't guarantee it will work as it should though, but I suppose you will not hard-brick device by flashing system partition only.
Maksfrai said:
Not sure about .dat only, unless you'll pack it back with system.transfer.list, file_contexts and so on (FlashFire actually supports block-based OTAs, it would be strange if it couldn't flash typical OTA update), but I never tried that. Besides, the previously mentioned tool supports repacking system.img as well starting from v2. I took system.img from prerooted 5.6.2.0 firmware by retyre and successfully repacked it with some modified files - though I didn't flash it (don't want to mess with my HD 10 yet). Can't guarantee it will work as it should though, but I suppose you will not hard-brick device by flashing system partition only.
Click to expand...
Click to collapse
The stock script from the amazon update.bin has set_metadata in it, after the boot.omg is unpacked. Would it matter to put the set_metadata after that?
I don't think it will change anything. It seems FlashFire is using stock features like recovery/bootloader commands to flash something, so maybe set_metadata which changes permissions is not supported properly on the step or somehow blocked or something else. And I've noticed FlashFire is using update-binary rather than update-script in some cases.
Did you try to modify and flash system image only?
Maksfrai said:
I don't think it will change anything. It seems FlashFire is using stock features like recovery/bootloader commands to flash something, so maybe set_metadata which changes permissions is not supported properly on the step or somehow blocked or something else. And I've noticed FlashFire is using update-binary rather than update-script in some cases.
Did you try to modify and flash system image only?
Click to expand...
Click to collapse
Not yet. Going to be doing that today. The stock script are the same for the Fire7 and HD 10. So not sure how this is the case with flash fire unless the version of flash fire matters. It could be the version(s) we are stuck with won't work for set_metadata. @ggow what version of flash fire is the fire 7 using for your rom?
DragonFire1024 said:
Not yet. Going to be doing that today. The stock script are the same for the Fire7 and HD 10. So not sure how this is the case with flash fire unless the version of flash fire matters. It could be the version(s) we are stuck with won't work for set_metadata. @ggow what version of flash fire is the fire 7 using for your rom?
Click to expand...
Click to collapse
In the instructions to install fire nexus rom you have to use it using flashfire 0.73
Rortiz2 said:
In the instructions to install fire nexus rom you have to use it using flashfire 0.73
Click to expand...
Click to collapse
Correct. Well I still haven't been able to successfully flash anything to the partition. I tried one of the unpacking tools (UR_Tool) and still nothing. Should I flash the boot.img with a system.img assuming I can properly build one?
DragonFire1024 said:
Correct. Well I still haven't been able to successfully flash anything to the partition. I tried one of the unpacking tools (UR_Tool) and still nothing. Should I flash the boot.img with a system.img assuming I can properly build one?
Click to expand...
Click to collapse
Test what you said, to flash the system.img and boot.img
Rortiz2 said:
Test what you said, to flash the system.img and boot.img
Click to expand...
Click to collapse
Have been.it's in the nexus script to unpack boot. It's also in the stock script. Sigh.
If you're changing system partition to the extent it affects boot partition then yes, you obviously will need to modify and flash it too. I was talking about small changes to system partition like changing default build-in launcher or system ui and such. Also, if you'll need a tool to modify boot image, try this one, it's simple and working fine for amazon devices.
Maksfrai said:
If you're changing system partition to the extent it affects boot partition then yes, you obviously will need to modify and flash it too. I was talking about small changes to system partition like changing default build-in launcher or system ui and such. Also, if you'll need a tool to modify boot image, try this one, it's simple and working fine for amazon devices.
Click to expand...
Click to collapse
I'll try it later when I get home. I've only tried flashing a whole room. Didn't occur to me to flash just a package or two.
Sent from my Galaxy S4 using XDA Labs
Any updates?
Rortiz2 said:
Any updates?
Click to expand...
Click to collapse
I tried once yesterday with the linked tool a few posts ago to modify boot.img and it didn't work. Well everything worked up to flashing. I flash and not surprisingly, hangs at the white boot logo or reboots when that logo disappears. I will try again today.
Sent from my Galaxy S4 using XDA Labs
DragonFire1024 said:
I tried once yesterday with the linked tool a few posts ago to modify boot.img and it didn't work. Well everything worked up to flashing. I flash and not surprisingly, hangs at the white boot logo or reboots when that logo disappears. I will try again today.
Sent from my Galaxy S4 using XDA Labs
Click to expand...
Click to collapse
Oh I'm sorry. It stays in the bootanimation or in the boot logo? Try again as you say
Rortiz2 said:
Oh I'm sorry. It stays in the bootanimation or in the boot logo? Try again as you say
Click to expand...
Click to collapse
The white Amazon logo appears. Not long passes before it disappears and the tablet reboots to it. The white amazon logo disappears around the same amount of time as it would if booting normally.
@ggow this maybe a dumb thing to ask, but have you ever successfully modified the ram disk on the fire 7 or any other amazon device? Has anyone?
I finally figured out how to create a system image from the update bin. The tool I use is nice, but I am having trouble getting it to size properly. It always seems to be just over the partition size of 1614(ish) mb or 1.6 gb. The image builds as 1.8gb and I can't get it down to the right size. If I rebuild the .dat files, it creates a system.img with them that I can open as an archive in 7zip and if I just build the image, I have to run it through an unpacker. Which one should I be using to flash or does it even matter? What tool should I use for this? I lost the link to a recommended one.
Sent from my MotoG3 using XDA Labs
Related
I'll start by saying here that I fully understand that what I'm saying may not apply to the international (non-GED) Xoom devices.
Maybe someone can shed some light on this. Why is it that every rooting method I see here seems to involve flashing some ZIP file that has a modified kernel or boot image? Seems pointless considering that, as with any other Google Experience Device, you can simply unlock your bootloader, flash Clockwork, and then flash the official Superuser.zip from androidsu.com and you're done. There's no unsecuring of the boot image, or anything. It just installs Superuser.apk, the su binary and changes the permissions on the binary.
Am I missing something here? Is there some advantage I'm not thinking of to using a custom boot image to obtain root on a Xoom?
No. Before when I first bought my xoom I just rooted it, no custom kernel or rom. Now I've used both and benefits alot. As for example some games people complain laggs, with custom kernel ya can over clock and fix some of this. Then custom roms allow ya to use features not enabled by Google on default. For example the wifi xoom can not connect ad-hoc networks like mobile hotspots. Roms include this unless you wanna do it the hard way. Another nifty feature is the USB OTG to attach hard drives which Google allows ya to do like mice and keyboards but not external drives.
oldblue910 said:
Seems pointless considering that, as with any other Google Experience Device, you can simply unlock your bootloader, flash Clockwork, and then flash the official Superuser.zip from androidsu.com and you're done. There's no unsecuring of the boot image, or anything. It just installs Superuser.apk, the su binary and changes the permissions on the binary.
Am I missing something here? Is there some advantage I'm not thinking of to using a custom boot image to obtain root on a Xoom?
Click to expand...
Click to collapse
I think you ARE missing something. The process you outlined with other GED devices is identical to the Motorola XOOM root process as well.
1. You use "fastboot oem unlock" to unlock the bootloader. (This only unlocks the bootloader so you can flash custom ones, recoveries, etc. but does NOT modify the current bootloader in any way.)
2. Flash clockwork with fastboot as well.
3. Install the Universal XOOM rooting ZIP through clockwork.
4. Done.
How is this any different?
The Universal XOOM root ZIP can be found @ http://forum.xda-developers.com/showthread.php?t=1242241 and does NOT contain any sort of modified Kernel or Boot image.
I don't know where you got your information from.
Sure it does. Take a look at the zip file (all those files in the kernel folder). Plus once it's done, stock recovery no longer auto flashes because something was changed in the boot image and the checksums don't match anymore.
Sent from my Xoom using Tapatalk
Well, I stand corrected! Yeah, I don't know why it modifies the boot image either then. I'd have just thought flashing clockwork and installing the binary should be fine.
I guess you need to talk to solarnz or one of the other more experienced XOOM devs...
sodaboy581 said:
Well, I stand corrected! Yeah, I don't know why it modifies the boot image either then. I'd have just thought flashing clockwork and installing the binary should be fine.
I guess you need to talk to solarnz or one of the other more experienced XOOM devs...
Click to expand...
Click to collapse
And that's the thing...flashing just the binaries DOES work fine, at least on my Xoom. I wonder if it has something to do with the international non-GED Xooms...
Sent from my Xoom using Tapatalk
You do need a modified initramfs to root properly.
an insecure boot.img is the most useful part of being rooted.
And with one of those you don't even need clockworkmod.
flash it with fastboot / reboot / adb remount and then just push su and superuser set suid on su (10 seconds total - far less hassle than messing with clockworkmod).
I am a little surprised no one figured out how to root before unlocking. Would sure be handy to do a titanium backup before unlocking ( which wipes everything !! ) That said, it is just a minor inconvenience. Copy some stuff to the PC and I am good to go.
oldblue910 said:
I'll start by saying here that I fully understand that what I'm saying may not apply to the international (non-GED) Xoom devices.
Maybe someone can shed some light on this. Why is it that every rooting method I see here seems to involve flashing some ZIP file that has a modified kernel or boot image? Seems pointless considering that, as with any other Google Experience Device, you can simply unlock your bootloader, flash Clockwork, and then flash the official Superuser.zip from androidsu.com and you're done. There's no unsecuring of the boot image, or anything. It just installs Superuser.apk, the su binary and changes the permissions on the binary.
Am I missing something here? Is there some advantage I'm not thinking of to using a custom boot image to obtain root on a Xoom?
Click to expand...
Click to collapse
You don't _need_ to flash an insecure kernel image; there's multiple paths to root. If you don't have a version of CWM for the device, then running the system insecure may be the only way to do it. Running the system in insecure mode does give you the ability to run adb as root amongst other things, however (so you can do things like adb remount).
Yeah I can see needing the insecure image in the case of not having ClockworkMod or if you need those extra commands in ADB. I was more just curious if running an insecure image was somehow a better practice than just flashing the androidsu.com zip. I guess it's 6 of one or a half dozen of the other in the end.
Thanks for the explanation!
Sent from my Xoom using Tapatalk
unrandomsam said:
an insecure boot.img is the most useful part of being rooted.
Click to expand...
Click to collapse
I suppose that depends on what you use root for, really. For instance, the ability to run adb as root means nothing to me really. I can count the number of times I've used adb on one hand. I more use root so I can take screenshots without hooking up to USB, and I also like having root access to the filesystem.
Plus, it seems that the insecure image is the reason why everyone says not to accept OTAs if you're running a rooted stock ROM. I've read horror stories of people accepting OTAs on a rooted stock ROM and ending up with bootloops and all kinds of other craptastic stuff. If you root with the boot image secure, you can accept OTAs and just re-root when it's done flashing.
Different strokes for different folks, right?
Sent from my Xoom using Tapatalk
mobileweasel said:
I am a little surprised no one figured out how to root before unlocking. Would sure be handy to do a titanium backup before unlocking ( which wipes everything !! ) That said, it is just a minor inconvenience. Copy some stuff to the PC and I am good to go.
Click to expand...
Click to collapse
This.
Most devices have temp root so you're able to run rooted app to fully backup before unlocking it. I've been holding off rooting on my wife's xoom because I don't want to wipe her saved data, but im really itching to mess with it, hehe. I heard with ICS you can do a full backup with adb, I believe you use the " adb backup" method.
The insecure boot image is need for two reasons.
1) without it you would not be able to adb mount the partitions while inside the Android os.
2) every time you boot into Android, a script it's ran to check for stock recovery and overwrite it, insecure boot images disable this (you can also disable by deleting the script files)
Sent from my Nexus S 4G
Hey I have an unlocked boot loader, stock 4.2.1 ROM but running ktoonz kernel. In order to get the next update will I have to re flash the stock kernel, recovery, and re-lock my bootloader? I'm really only familiar with Samsung galaxy devices where you can just ODIN everything
Sent from my SGH-T999 using xda premium
Jms122589 said:
Hey I have an unlocked boot loader, stock 4.2.1 ROM but running ktoonz kernel. In order to get the next update will I have to re flash the stock kernel, recovery, and re-lock my bootloader? I'm really only familiar with Samsung galaxy devices where you can just ODIN everything
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
You will need the stock kernel and your /system partition must be completely unmodified. Bootloader state and recovery don't matter. After accepting an update you will lose your custom recovery and root, so you will have to reflash but that's no big deal.
Sent from my Nexus 7 using Tapatalk HD
Awesome thanks a lot, is there a link for a flashable stock kernel? I don't ry feel like restoring from my old recovery
Sent from my SGH-T999 using xda premium
Jms122589 said:
Awesome thanks a lot, is there a link for a flashable stock kernel? I don't ry feel like restoring from my old recovery
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Download the latest factory images at http:// developers.google.com/android/nexus/images. Open the package, and flash boot.img.
Sent from my Galaxy Nexus using Tapatalk 2
oldblue910 said:
Download the latest factory images at http:// developers.google.com/android/nexus/images. Open the package, and flash boot.img.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hey can u also help me
I was running CM10.1 then I flashed back the stock image of 4.2 and now I am not able to update it to 4.2.1 it shows me an error when installing.
Please help!!!
udimars30 said:
Hey can u also help me
I was running CM10.1 then I flashed back the stock image of 4.2 and now I am not able to update it to 4.2.1 it shows me an error when installing.
Please help!!!
Click to expand...
Click to collapse
You have to flash both system and boot, plus do a full data and cache wipe. As long as you do that and you don't let root apps modify files on your /system partition, the update should install fine. Also, keep in mind that when you get the OTA notification on your phone, you cannot just select "Restart and Install" if you have ClockworkMod recovery. OTAs will only auto flash if you have stock recovery. If you're using ClockworkMod recovery, you'll have to pull the OTA file out of your /cache folder and put it on internal storage somewhere, then flash it manually in ClockworkMod.
OK so am I flashing the boot image and system image through fastboot? If so how do I do that? If not...how do I flash them?
Sent from my SGH-T999 using xda premium
Jms122589 said:
OK so am I flashing the boot image and system image through fastboot? If so how do I do that? If not...how do I flash them?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Correct. Just extract system.img and boot.img from the package you download, then plug your tablet into USB, boot it into the bootloader, and do the following two commands:
fastboot flash boot boot.img
fastboot flash system system.img
If you want to wipe data, also do:
fastboot erase cache
fastboot erase userdata
That'll get you back to complete stock.
OK so were am I extracting these files to? Root of mysd card, desktop, etc? Thanks a bunch for your help btw I'm just not experienced at all with flashing outside of recovery or odin
Sent from my Nexus 10 using xda premium
Jms122589 said:
OK so were am I extracting these files to? Root of mysd card, desktop, etc? Thanks a bunch for your help btw I'm just not experienced at all with flashing outside of recovery or odin
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
Extract them to your desktop somewhere, then do fastboot from the command prompt.
oldblue910 said:
You have to flash both system and boot, plus do a full data and cache wipe. As long as you do that and you don't let root apps modify files on your /system partition, the update should install fine. Also, keep in mind that when you get the OTA notification on your phone, you cannot just select "Restart and Install" if you have ClockworkMod recovery. OTAs will only auto flash if you have stock recovery. If you're using ClockworkMod recovery, you'll have to pull the OTA file out of your /cache folder and put it on internal storage somewhere, then flash it manually in ClockworkMod.
Click to expand...
Click to collapse
sorry but i didn't get this part 'As long as you do that and you don't let root apps modify files on your /system partition' and to flash all that i need unlock bootloader??
oldblue910 said:
You have to flash both system and boot, plus do a full data and cache wipe. As long as you do that and you don't let root apps modify files on your /system partition, the update should install fine. Also, keep in mind that when you get the OTA notification on your phone, you cannot just select "Restart and Install" if you have ClockworkMod recovery. OTAs will only auto flash if you have stock recovery. If you're using ClockworkMod recovery, you'll have to pull the OTA file out of your /cache folder and put it on internal storage somewhere, then flash it manually in ClockworkMod.
Click to expand...
Click to collapse
I did all that you said but didn't understand this 'As long as you do that and you don't let root apps modify files on your /system partition' then i tried to update manually and it did again showed me an error like this:
udimars30 said:
I did all that you said but didn't understand this 'As long as you do that and you don't let root apps modify files on your /system partition' then i tried to update manually and it did again showed me an error like this:
Click to expand...
Click to collapse
Did you use the JOP40C factory images downloaded from the Google website somewhat recently? That error is caused when you flash the original set of JOP40C images released when the Nexus 10 first came out. There was a bug in them that Google fixed. They posted new images. You can download them at http://developers.google.com/android/nexus/images or http://www.randomphantasmagoria.com/firmware/nexus-10/mantaray.
Also, what I mean about root apps modifying /system files...so there are a lot of root apps out there that make tweaks to your system...stuff like making changes to your GPS config files for quicker lock-on, you yourself going in and deleting unwanted apps out of /system/app, you or an app making changes to build.prop, installing busybox in the wrong place and having it overwrite system commands with its own...things like that. If you or any app make any change whatsoever to any file anywhere on /system, an OTA will fail every time. It checks the hash of each and every file before applying the update and if a single one of them doesn't match what it expects, the OTA will fail. So just keep that in mind.
But that error you're getting about set_perm is most definitely caused by using the original, bad set of images that Google put out there. Download them again, try again and you should be in business.
oldblue910 said:
Did you use the JOP40C factory images downloaded from the Google website somewhat recently? That error is caused when you flash the original set of JOP40C images released when the Nexus 10 first came out. There was a bug in them that Google fixed. They posted new images. You can download them at http://developers.google.com/android/nexus/images or http://www.randomphantasmagoria.com/firmware/nexus-10/mantaray.
Also, what I mean about root apps modifying /system files...so there are a lot of root apps out there that make tweaks to your system...stuff like making changes to your GPS config files for quicker lock-on, you yourself going in and deleting unwanted apps out of /system/app, you or an app making changes to build.prop, installing busybox in the wrong place and having it overwrite system commands with its own...things like that. If you or any app make any change whatsoever to any file anywhere on /system, an OTA will fail every time. It checks the hash of each and every file before applying the update and if a single one of them doesn't match what it expects, the OTA will fail. So just keep that in mind.
But that error you're getting about set_perm is most definitely caused by using the original, bad set of images that Google put out there. Download them again, try again and you should be in business.
Click to expand...
Click to collapse
Thanks a ton dude but any place where i can talk to you??
like facebook or Google+??
udimars30 said:
Thanks a ton dude but any place where i can talk to you??
like facebook or Google+??
Click to expand...
Click to collapse
I'm on Twitter and G+. Just click on my name over on the left of this post and you can find links to my profiles.
So I want to update to 4.2.2 using the Nexus Toolkit (I have the latest one) but have been running into problems. Every time I try to update it fails: assert failed: apply_patch_check ("/system/lib/libSR_AudioIn.so", bcc09f67f497c66aedece202942bc4c45f712f62", "85eeeb97d102a3f6656e58cb25ad97bbe29ec613")
After reading around I found out that the Beats Audio drivers I had installed (and thought I removed) modified that .so file. I'd like to be able to just replace that single file with the stock version to save me the hassle of flashing the whole stock image.
Does anyone know where I can find a copy of that file, or a work around that I can use?
Thanks!
http://forum.xda-developers.com/showthread.php?t=2144330
use 'search thread', people have similar issues, you'll find a solution there.
Yeah, I read through about 10 different threads about this but none of them actually had a solution... Just a bunch of "This is happening UPDATE: Fixed it" type posts. No one has actually posted their solution in any of the threads I've looked through (including the one you linked). Thanks for the link though.
issak42 said:
http://forum.xda-developers.com/showthread.php?t=2144330
use 'search thread', people have similar issues, you'll find a solution there.
Click to expand...
Click to collapse
i am also looking for SiMILAR Method like how we installed BEATS AUDIO so the method should be the same if someone can provide stock audio driver ZIP so we can reflash it back to get old drivers
I had this same exact problem.
I had beats audio installed and even with the script uninstaller and uninstalling the APP my LIB file was missing. i copied it from N4 and still it kept failing on that LIB file every time i applied the OTA zip
the BEST way to resolve this is to
extract the SYSTEM.IMG and BOOT.IMG file from the 4.2.1 stock image
FASTBOOT FLASH SYSTEM.IMG to your device
FASTBOOT FLASH BOOT.IMG to your device
this will flash the stock system files AND kernal to your device.
reboot your device and try to flash the OTA again and it should work.
Thanks. That's exactly what I did... I decided to use the Nexus 7 Toolkit to just restore to stock (I was getting frustrated so I didn't care if it removed all my apps, etc). It turns out the toolkit lets you restore the stock image without wiping all of your apps/sd data so I was able to update and everything was great. Not rooted anymore, but I'll deal with that later .
nextelbuddy said:
I had this same exact problem.
I had beats audio installed and even with the script uninstaller and uninstalling the APP my LIB file was missing. i copied it from N4 and still it kept failing on that LIB file every time i applied the OTA zip
the BEST way to resolve this is to
extract the SYSTEM.IMG and BOOT.IMG file from the 4.2.1 stock image
FASTBOOT FLASH SYSTEM.IMG to your device
FASTBOOT FLASH BOOT.IMG to your device
this will flash the stock system files AND kernal to your device.
reboot your device and try to flash the OTA again and it should work.
Click to expand...
Click to collapse
i had the same deal. flashed system.img, updated, flashed su. i didn't flash boot though
?need to flash boot.img
Thanks for above. I have solved the beats audio problem as per above. I only flashed the system.img and not the boot.img. Does this matter? Or should I do so to get the latest kernel? or is my kernel 3.1.10-g05b777c the latest?
Cheers,
Sam
yuo need to be on stock everything so to be safe and retain all user data and apps, just flash system.img and boot.img
it wont hurt anything and saves you headaches
I am currently in the same boat. I can't seem to find the stock image for 4.2.1. On Google's site they only have 4.1.2 and 4.2.2. Does any one know where I can get it or at least the system.img and boot.img from it?? Thanks for the help.
Leif
Leifrn said:
I am currently in the same boat. I can't seem to find the stock image for 4.2.1. On Google's site they only have 4.1.2 and 4.2.2. Does any one know where I can get it or at least the system.img and boot.img from it?? Thanks for the help.
Leif
Click to expand...
Click to collapse
http://goo.im/devs/WugFresh/stock/nakasi
burnitdown said:
i had the same deal. flashed system.img, updated, flashed su. i didn't flash boot though
Click to expand...
Click to collapse
same here. Now on 4.2.2 rooted.
I tried flashing boot.img but I cant seem to fastboot to device because of an unknown partition error. What to do??
swidnik0
You sir, are a gentleman. Thanks for you help.
Leif
Try this command to resolve partition issue
Leonhan said:
I tried flashing boot.img but I cant seem to fastboot to device because of an unknown partition error. What to do??
Click to expand...
Click to collapse
> fastboot flash system system.img
[email protected] said:
> fastboot flash system system.img
Click to expand...
Click to collapse
Oh there, spot on! Thanks man!
nextelbuddy said:
I had this same exact problem.
I had beats audio installed and even with the script uninstaller and uninstalling the APP my LIB file was missing. i copied it from N4 and still it kept failing on that LIB file every time i applied the OTA zip
the BEST way to resolve this is to
extract the SYSTEM.IMG and BOOT.IMG file from the 4.2.1 stock image
FASTBOOT FLASH SYSTEM.IMG to your device
FASTBOOT FLASH BOOT.IMG to your device
this will flash the stock system files AND kernal to your device.
reboot your device and try to flash the OTA again and it should work.
Click to expand...
Click to collapse
Sorry for noon question
Any link for the guide ?
For flashing boot.IMG system.IMG
Sorry I have never done these things before
Sent from my Nexus 7 using Tapatalk HD
How/where to extract system.img and boot.img ??
rm79 said:
Thanks. That's exactly what I did... I decided to use the Nexus 7 Toolkit to just restore to stock (I was getting frustrated so I didn't care if it removed all my apps, etc). It turns out the toolkit lets you restore the stock image without wiping all of your apps/sd data so I was able to update and everything was great. Not rooted anymore, but I'll deal with that later .
Click to expand...
Click to collapse
How/where to extract system.img and boot.img ??
after I flashed 4.2.1 system and boot images
so after flashed system.img and boot.img i was able to upgrage 4.2.2 OTA but now my nexus is not rooted. so if im gonna root it again will i lose all my data and apps?
ashok_jeev said:
so after flashed system.img and boot.img i was able to upgrage 4.2.2 OTA but now my nexus is not rooted. so if im gonna root it again will i lose all my data and apps?
Click to expand...
Click to collapse
If your bootloader is already unlocked, then rooting it won't wipe your data.
Unlocked Bootloader.
CWM.
Root.
Fail in updating, with message something like assert fail apply_update_check status 7.
Revert to Stock Recovery and Unroot (bootloader is still unlock), update again, result in error with the android robot and red exclamation.
Happen to my Nexus 7 and Galaxy Nexus as well (same unlock bootloader cwm root, same revert method, same error).
Has anyone face this and any solution to make OTA works?
Get back to stock, then try again
Sent from my Nexus 4 using xda premium
Had the same problem. This will answer all your questions
http://forum.xda-developers.com/showthread.php?t=2145848
thanks for the link. it did not directly make my device can be updated, but incase others have this problem and looking for solution, here are the things I did and fix it:
flash boot.img and flash system.img
these 2 files are needed to be at STOCK, I extract from the factory image, and flash through fastboot.
flashing these 2 files WILL NOT CAUSE application to be formatted (like what I thought at the first time).
It will simply remove any tweak done to system such as ads blocking (adaway, etc), battery icon mod, etc.
Then, you can update just fine.
Again, BIG THANKS to xda community.
raijinshou said:
thanks for the link. it did not directly make my device can be updated, but incase others have this problem and looking for solution, here are the things I did and fix it:
flash boot.img and flash system.img
these 2 files are needed to be at STOCK, I extract from the factory image, and flash through fastboot.
flashing these 2 files WILL NOT CAUSE application to be formatted (like what I thought at the first time).
It will simply remove any tweak done to system such as ads blocking (adaway, etc), battery icon mod, etc.
Then, you can update just fine.
Again, BIG THANKS to xda community.
Click to expand...
Click to collapse
Sorry, but I searched and searched but I still don't understand. I removed all my mods.
I wanted to update to 4.2.2 but it says apply_patch_check error about Currents.
How do I flash that boot.img and system.img? Trough custom recovery or stock? And where can I find those files? Thanks.
Guzanni said:
Sorry, but I searched and searched but I still don't understand. I removed all my mods.
I wanted to update to 4.2.2 but it says apply_patch_check error about Currents.
How do I flash that boot.img and system.img? Trough custom recovery or stock? And where can I find those files? Thanks.
Click to expand...
Click to collapse
boot.img and system.img can be founded in the STOCK ROM, here is the link for STOCK 4.2.1 for Nexus 4:
https://docs.google.com/open?id=0B_zuNWpIf1ujNlFDVnZ3dzg2WEU
(Source: http://www.randomphantasmagoria.com/firmware/nexus-4/occam/ )
Extract the file, you can find boot.img and system.img inside it.
To flash these 2 files, since I am not familiar with fastboot, I am using Nexus 4 Toolkit to help with it.
You can download Nexus 4 Toolkit: http://goo.im/devs/mskip/toolkit/google_nexus4/Google_Nexus_4_ToolKit_v1.3.0.exe
(Source: http://forum.xda-developers.com/showthread.php?t=1995688 )
Copy boot.img and system.img to Nexus 4 Toolkit folder of "put_img_files_to_flash_here"
then using "11. Boot or Flash .img Files to Device option", flash the file to the correct partition
(when flashing boot.img, to boot partition | when flashing system.img, to system partition).
this is a thread for brainstorming and testing an upgrade path from 4.4.4 stock to 5.1 stock that retains root (that is all).
i'm assuming trying to flash a pre-rooted 5.1 system .img (if ever becomes available) using mofo is not going to work unless something changes [ie, how would you get the new modem, kernel, etc?]
idea 1:
a. use mofo to flash xt1254.system.21.44.12.quark_verizon.rooted.ext4.img (stock 4.4.4 with root baked in, no other system modifications).
b. next, manually flash the android 5.1 OTA patch .zip (whenever its public, or if any soak members are willing to test now)
c. question for a willing tester (realize once you go 5.1 you cant go back and might not ever see root again), does root remain or is it lost during the upgrade?
idea 2:
a. if the above system upgrade from 4.4.4 to 5.1 does work but root is lost (and there is no "OTA Keeper" type app in the image), could we bake in a 'backup' of root and a 'restore' app into the xt1254.system.21.44.12.quark_verizon.rooted.ext4.img and then could we again upgrade to 5.1 and 'restore' root on a temporary basis (better than never having root).
b. of course this is not ideal, but if that does work, then maybe someone could also bake into the base 4.4.4 image an app that auto-restores root quickly on every boot, for a virtual perm temporary root solution.
idea 3:
put your thinking cap on and please provide.
Idea 1 is a no go
PILLMUZIK3600 said:
Idea 1 is a no go
Click to expand...
Click to collapse
well, bummer, thanks. sounds like we'll have to skip to idea 3.
but to confirm, does the 5.1 OTA patch not manually flash over a clean xt1254.system.21.44.12.quark_verizon.rooted.ext4.img ? OR it does, but root lost?
Doesn't flash at all
Has someone tried using Mofo that has taken the new update? I saw that the 2nd gen Moto X works with Mofo & 5.0 Lollipop, but not sure about 5.1.
I'm kind of confused. Can't we just modify the stock 5.1 image to have root? Or does mofo refuse to flash it?
PILLMUZIK3600 said:
Idea 1 is a no go
Click to expand...
Click to collapse
yep also just tested option 1 fails on recovery-from-boot.sh or something like that basically one of the files that supersu changes to get root working.
Can you install the update on a rooted phone? Or do I need to go back to stock?
janitorjohnson said:
Can you install the update on a rooted phone? Or do I need to go back to stock?
Click to expand...
Click to collapse
back to stock. it will fail if rooted
Does anyone have a completely stock system image ?
Anyone tried kingroot?
Can't get back to stock for some reason ..rooted .. Can some one help me
One option that might work is to take a rooted system img and "copy" the contents of the ota into it - overwriting anything that was updated - this should leave the root files in the image and mofo should flash it - but the new kernel may not like the old bootloader. Or old radios. Or just being there in the first place. It may brick the phone or cause your microwave to explode.
hotrodwinston said:
One option that might work is to take a rooted system img and "copy" the contents of the ota into it - overwriting anything that was updated - this should leave the root files in the image and mofo should flash it - but the new kernel may not like the old bootloader. Or old radios. Or just being there in the first place. It may brick the phone or cause your microwave to explode.
Click to expand...
Click to collapse
I have been trying to figure out this how do we keep root thing. so in the image is also the kernel? that part has been perplexing me and no one has yet tell me exactly that. if the kernal is in the image. because i know lollipop new kernal is needed. so i figured no matter what we would have ot get the OTA to receive the kernel then it would all depend on if mofo was still able to access whatever it access to overwrite the stock image.
but from what you say it seems. the kernel is included in the image so we flash a new image we flash a new kernel?
johnbravado said:
I have been trying to figure out this how do we keep root thing. so in the image is also the kernel? that part has been perplexing me and no one has yet tell me exactly that. if the kernal is in the image. because i know lollipop new kernal is needed. so i figured no matter what we would have ot get the OTA to receive the kernel then it would all depend on if mofo was still able to access whatever it access to overwrite the stock image.
but from what you say it seems. the kernel is included in the image so we flash a new image we flash a new kernel?
Click to expand...
Click to collapse
As far as I know, the system image is just the /system directory. At least that's what I can see when I mount the file in Linux.
So I think if we had a Lollipop image, we could just copy the Superuser.apk to /system/app, then that's all we need to get root... I hope.
neozen21 said:
As far as I know, the system image is just the /system directory. At least that's what I can see when I mount the file in Linux.
So I think if we had a Lollipop image, we could just copy the Superuser.apk to /system/app, then that's all we need to get root... I hope.
Click to expand...
Click to collapse
I would think you would just look at the SuperSU.zip script file and then insert all required files as described in the script.
https://su.chainfire.eu
Tomsgt said:
yep also just tested option 1 fails on recovery-from-boot.sh or something like that basically one of the files that supersu changes to get root working.
Click to expand...
Click to collapse
ok, so do we need to pull from non-modified stock 4.4.4, and try file by file, putting the file back into that .img, flash with mofo, then try manually applying the ota.zip.. until we have a working stock 4.4.4 .img that contains some way to restore root, that can be manually updated with the OTA.zip... or does using mofo automatically flag the system is modified and only path would be to revert fastboot a stock verizon img. questions...
PILLMUZIK3600 said:
Does anyone have a completely stock system image ?
Click to expand...
Click to collapse
great question. can someone post a link to a completely stock 4.4.4 system image for Verizon Droid Turbo? if one doesn't exist, how is everyone reverting to stock to continue with OTA updates that has used mofo and/or CF's modified roms?
neozen21 said:
As far as I know, the system image is just the /system directory. At least that's what I can see when I mount the file in Linux.
So I think if we had a Lollipop image, we could just copy the Superuser.apk to /system/app, then that's all we need to get root... I hope.
Click to expand...
Click to collapse
does mofo flash the modem/kernel, data, etc ? or is it only going to flash the system partition?
chip! said:
ok, so do we need to pull from non-modified stock 4.4.4, and try file by file, putting the file back into that .img, flash with mofo, then try manually applying the ota.zip.. until we have a working stock 4.4.4 .img that contains some way to restore root, that can be manually updated with the OTA.zip... or does using mofo automatically flag the system is modified and only path would be to revert fastboot a stock verizon img. questions...
great question. can someone post a link to a completely stock 4.4.4 system image for Verizon Droid Turbo? if one doesn't exist, how is everyone reverting to stock to continue with OTA updates that has used mofo and/or CF's modified roms?
mofo already said its not going to work on 5.1.. so we know you can only use mofo with droid turbo when the phone is still on 4.4.4. and i dont see how you can go 4.4.4 -> 5.1 from a 'system' partition .img alone. someone feel free to set the record straight, but it would be surprised if modem, kernel, etc are embedded on system partition.
Click to expand...
Click to collapse
All i can say to all of these questions right now is "PROCESSING". if you know me you will understand
Tomsgt said:
All i can say to all of these questions right now is "PROCESSING". if you know me you will understand
Click to expand...
Click to collapse
Faith age, boys.
Tomsgt said:
All i can say to all of these questions right now is "PROCESSING". if you know me you will understand
Click to expand...
Click to collapse
Sweet can't wait