For Both Flo/Deb
https://developers.google.com/android/nexus/images#razorkrt16o
It looks like they are currently uploading the Flo version at this time of posting, but both Stock 4.4 Images are up..
I looked around to see if anyone who have already posted this.. if so please feel free to merge or delete this Post
Finally! I'm going to flash this on both my flo and mako. Then, along with my hammerhead, I'll have KitKats everywhere!
Was going to post this too. Just my luck that they release it the day that I'll be out all night and won't be able to update until the weekend. Maybe I'll get the OTA before then.
Looks like the file for flo is corrupt. It is always only 835 bytes. MD5 hash seems to be taken from the version on the server... So don't even waste time in x-checking them just yet.
The update for mako seems to be fine, though.
Zaphodspeaks said:
For Both Flo/Deb
https://developers.google.com/android/nexus/images#razorkrt16o
It looks like they are currently uploading the Flo version at this time of posting, but both Stock 4.4 Images are up..
I looked around to see if anyone who have already posted this.. if so please feel free to merge or delete this Post
Click to expand...
Click to collapse
The Wifi version doesnt look like its been fully uploaded..
Deb however looks like its all there.. Check in an hour to see if the upload is complete..
The F5 key on my keyboard has taken a turn for the worst! lol
Blockberd said:
Looks like the file for flo is corrupt. It is always only 835 bytes. MD5 hash seems to be taken from the version on the server... So don't even waste time in x-checking them just yet.
The update for mako seems to be fine, though.
Click to expand...
Click to collapse
Maybe not completed the upload yet?
ElGato65 said:
Maybe not completed the upload yet?
Click to expand...
Click to collapse
Hm. Would be interesting. I can open the file without any problem. It contains flash-all.bat, flash-all.sh and flash-base.sh.
ElGato65 said:
Maybe not completed the upload yet?
Click to expand...
Click to collapse
It isn't a problem with the upload.
It is a problem with WHAT was uploaded.
The file that was uploaded matches the sha1 hash code.
It unpacks fine.
Unfortunately it has nothing except the flash batch files/shell scripts.
Also the batch file tries to flash bootloader 3.14, which is wrong. The bootloader should be 4.01. It does however try to flash the krt16o rom, which means someone edited the file, just didn't do a good job.
Noticed this as well -- no image.
Blockberd said:
Hm. Would be interesting. I can open the file without any problem. It contains flash-all.bat, flash-all.sh and flash-base.sh.
Click to expand...
Click to collapse
It is a complete file, with no image, just the install scripts.
Seems like it's almost a place holder -- could just be a flat-out mistake.
Can someone tell me if these images are complete resets? Or do they work just like the OTA update would?
Thanks.
jbwray said:
It is a complete file, with no image, just the install scripts.
Seems like it's almost a place holder -- could just be a flat-out mistake.
Can someone tell me if these images are complete resets? Or do they work just like the OTA update would?
Thanks.
Click to expand...
Click to collapse
By default, they are complete resets but they can be modified to keep your user data with minimal effort by removing the -w flag.
They don't work like OTAs because they don't patch the file you have in place, but rather replace the /system partition with the new one. The difference being if you installed some extra files into /system, they would be preserved during an OTA update, but would be gone after a factory image.
jbwray said:
It is a complete file, with no image, just the install scripts.
Seems like it's almost a place holder -- could just be a flat-out mistake.
Can someone tell me if these images are complete resets? Or do they work just like the OTA update would?
Thanks.
Click to expand...
Click to collapse
Those factory images will reset your device to factory is flashed as told by Google. There are, however, ways to avoid that if you have a stock Android prior to the version you want to flash.
---------- Post added at 10:41 PM ---------- Previous post was at 10:40 PM ----------
sfhub said:
It isn't a problem with the upload.
It is a problem with WHAT was uploaded.
The file that was uploaded matches the sha1 hash code.
It unpacks fine.
Unfortunately it has nothing except the flash batch files/shell scripts.
Also the batch file tries to flash bootloader 3.14, which is wrong. The bootloader should be 4.01. It does however try to flash the krt16o rom, which means someone edited the file, just didn't do a good job.
Click to expand...
Click to collapse
The question is if someone has closer contact to someone at Google to inform them about that...
Great tip, thanks.
sfhub said:
By default, they are complete resets but they can be modified to keep your user data with minimal effort by removing the -w flag.
Click to expand...
Click to collapse
Awesome tip, thanks! Now that I have looked at the file, I think I have seen that before, but it really didn't register as I wasn't concentrating on doing an update like this... too antsy for 4.4
jbwray said:
Awesome tip, thanks! Now that I have looked at the file, I think I have seen that before, but it really didn't register as I wasn't concentrating on doing an update like this... too antsy for 4.4
Click to expand...
Click to collapse
You could also go ahead and flash each .img file (except userdata) in bootload with fastboot to the device. That will be my way once the damn factory image is properly uploaded. ;D
sfhub said:
It isn't a problem with the upload.
It is a problem with WHAT was uploaded.
The file that was uploaded matches the sha1 hash code.
It unpacks fine.
Unfortunately it has nothing except the flash batch files/shell scripts.
Also the batch file tries to flash bootloader 3.14, which is wrong. The bootloader should be 4.01. It does however try to flash the krt16o rom, which means someone edited the file, just didn't do a good job.
Click to expand...
Click to collapse
Well atleast the Binaries are up..
So it wont be long until we will be seeing new Custom Roms, and Kernels..
Those of us that were lucky to get the OTA dont need to worry about the factory images..
I created a TWRP clean stock backup of KRT16O if I need to go back to factory settings
This is NOT, I repeat NOT a flashable zip. Its a Zip of my TWRP backup, minus the Data partition..
Just unzip into your TWRP backup folder.. It will bring your Nexus 7 Flo directly to stock 4.4..(ROOTED) It is not an OTA.
Your SD Card will remain untouched
https://www.dropbox.com/s/mqczh3q59lydga9/2013-11-13--06-14-08 KRT16O.TWRP.zip
If any of you want to flash just the update to 4.4, HERE is a link, with directions HERE
sfhub said:
Also the batch file tries to flash bootloader 3.14, which is wrong. The bootloader should be 4.01. It does however try to flash the krt16o rom, which means someone edited the file, just didn't do a good job.
Click to expand...
Click to collapse
Apparently calling all bootloaders 3.14 is a mistake they have chosen to propagate from JSS15R when they called the 3.15 bootloader 3.14.
So basically the 4.01 bootloader is named bootloader 3.14 in the archive.
With the stock rom, can I just flash it using a custom recovery?
yanksrock1000 said:
With the stock rom, can I just flash it using a custom recovery?
Click to expand...
Click to collapse
You can flash the OTA (the OTA requires stock JSS15R to be installed) or the update.zip that scrosler put together using custom recovery.
You can't flash the factory image from google in this thread using custom recovery. It was meant to be flashed using fastboot and with your tablet in bootloader.
Update images now available.
EDIT ** I looked at the wrong image... nothing has changed ** please delete.
jbwray said:
EDIT ** I looked at the wrong image... nothing has changed ** please delete.
Click to expand...
Click to collapse
I was in the middle of replying saying I must be blind (or some cache is getting in the way) because I couldn't find the alternate link/download
Related
OTA2 US was released today. Here is the update.
Would it be possible to make a version that can be flashed in CWM that keeps root and doesn't do the system verification?
Would you provide the full name of the update, please? I'm trying to save it properly for future reference. Thanks.
toenail_flicker said:
Would you provide the full name of the update, please? I'm trying to save it properly for future reference. Thanks.
Click to expand...
Click to collapse
I don't know the full name, it downloaded as update.zip on my TpT.
Okay, usually it sits in the download folder with its full name as the file name. Thanks anyway.
agree CWR removal
or, at least a way to restore the factory recovery partition, because following the steps in the CWM thread doesn't work....hitting vol+ or even adb reboot recovery, will not take you to the recovery area after you use the dd if=/recovery-from-boot.p
it places a VERY tiny file in the recovery partition and in no way restores it to the factory functionality.
Seems to be this one from here:
http://download.lenovo.com/slates/think/tablet1
ThinkPadTablet_A310_02_0039_0086_US.zip
Thanks, but I'm not finding any US files there, only WE. If your post is only for the file name, thanks, that does help.
toenail_flicker said:
Thanks, but I'm not finding any US files there, only WE. If your post is only for the file name, thanks, that does help.
Click to expand...
Click to collapse
http://download.lenovo.com/slates/think/tablet1/ThinkPadTablet_A310_02_0039_0086_US.zip
That does work
Has anyone updated using ClockworkMod Recovery or is it necessary to flash the original recovery? Also has anyone who updated and used OTA Rootkeeper tried flashing ClockworkMod Recovery after the update? Does it still work?
Perfect. Thanks.
I've captured the OTA zip for XT1052 India 4.4.4 update.
Instructions (You should be on android 4.4.2)
For both locked and unlocked bootloaders
1. Place the downloaded file in sdcard
2. Don't rename the file, it should be exactly as it is
3. Rooted users make sure you're as close to stock as possible
4. Go to settings-> about-> system updates
5. It will prompt to install the update
Download XT1052 India 4.4.4 OTA
Could you post the stock recovery image of the 4.4.2 ROM, please?
ron_gangte said:
Could you post the stock recovery image of the 4.4.2 ROM, please?
Click to expand...
Click to collapse
Sorry, I don't have that right now.
Thanks anyway. It'd be awesome if someone who has it posted. Anyone?
Yep, the update just popped up. How do you capture it by the way? What's the path?
devilsdouble said:
Yep, the update just popped up. How do you capture it by the way? What's the path?
Click to expand...
Click to collapse
/cache - find it w/Root Explorer, or similar.
samwathegreat said:
/cache - find it w/Root Explorer, or similar.
Click to expand...
Click to collapse
There are three folders under cache, backup, lost+found and recovery, none of them contain the update.
devilsdouble said:
There are three folders under cache, backup, lost+found and recovery, none of them contain the update.
Click to expand...
Click to collapse
You already installed it? Once you install it, the file is erased - forever. All OTAs are this way. You MUST extract it before you install it.
Confirm: Did you install it or not? Also, if not - has it downloaded completely?
EDIT: I'll take your lack of response as you confirming that you did install it...
I am downloading ota update my phone is rooted so should i unroot it first and remove xposed framework.. reply??
Hitesh1802 said:
I am downloading ota update my phone is rooted so should i unroot it first and remove xposed framework.. reply??
Click to expand...
Click to collapse
Yes, un-root, and remove all traces of having rooted. That includes any changes done to your System Files which Xposed might have done. You will have to flash the stock recovery too.
ron_gangte said:
Yes, un-root, and remove all traces of having rooted. That includes any changes done to your System Files which Xposed might have done. You will have to flash the stock recovery too.
Click to expand...
Click to collapse
thanks for the reply mate i have removed su by app option full unroot yes i am on stock recovery and uninstalled all modules and xposed framework..
after update i have to done that again..
Due to this i miss my old Samsung device just flash and you are on...
samwathegreat said:
You already installed it? Once you install it, the file is erased - forever. All OTAs are this way. You MUST extract it before you install it.
Confirm: Did you install it or not? Also, if not - has it downloaded completely?
EDIT: I'll take your lack of response as you confirming that you did install it...
Click to expand...
Click to collapse
No, my lack of response was because of the reading I was doing here on XDA as why I wasn't seeing the OTA zip file under cache. Then I realized that I did not download the OTA, I thought that it was downloaded already as I had data on and it was just asking me to whether it should install or not.
Now I downloaded the OTA, and it's there under cache folder, and now at a safe place on my desktop.
I would never install it on my phone without flashing back stock ROM again anyway. I like to do things fresh.
devilsdouble said:
No, my lack of response was because of the reading I was doing here on XDA as why I wasn't seeing the OTA zip file under cache. Then I realized that I did not download the OTA, I thought that it was downloaded already as I had data on and it was just asking me to whether it should install or not.
Now I downloaded the OTA, and it's there under cache folder, and now at a safe place on my desktop.
I would never install it on my phone without flashing back stock ROM again anyway. I like to do things fresh.
Click to expand...
Click to collapse
Good Deal. Thanks for clarifying, and glad you were able to extract it. :good:
I can relate -- I also prefer to always "do things fresh"
samwathegreat said:
Good Deal. Thanks for clarifying, and glad you were able to extract it. :good:
I can relate -- I also prefer to always "do things fresh"
Click to expand...
Click to collapse
Thanks. It's always nice to have the latest of Android. The new dialer is meaningless for me, again, it just changed it's viewing type, nothing else has been changed! Need to install ExDialer as usual. Will see if there's really something done with the camera, can't take any meaningful photos at 3:30 in the morning :laugh:
Just one thing, as I have taken the OTA after a fresh install of stock ROM, now I don't need to format it again from recovery right?
There is already a thread for the 4.4.4 rollout here, please use it instead of having two similar discussions going on in 2 separate threads. Thanks
Thread closed
It's out guys!
https://developers.google.com/android/nexus/images
jarjar124 said:
It's out guys!
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Thanks for the heads up!
if anyone is going to flash this, could you please benchmark it encrypted?
i saw a bench today where someone had fullspeed even encrypted. is this on 5.0.1?
Interesting that it is the exact same build as the other 5.0.1 updates. No major Shamu specific changes? Hopefully the new binaries provide significant improvements at least.
So I wondering, do we need to unroot the device in order to update using factory images, I had read sometime back how updates in Lolipop now checks all system files and if they are patched/altered the update will fail, but have not ready any issues updating the nexus 7 to 5.0.1 or the nexus 10 when they are root.
wolfnumba1 said:
So I wondering, do we need to unroot the device in order to update using factory images, I had read sometime back how updates in Lolipop now checks all system files and if they are patched/altered the update will fail, but have not ready any issues updating the nexus 7 to 5.0.1 or the nexus 10 when they are root.
Click to expand...
Click to collapse
No need to unroot to flash the new images..
Sent from my Nexus 4 using Tapatalk
ohhdavid said:
Interesting that it is the exact same build as the other 5.0.1 updates. No major Shamu specific changes? Hopefully the new binaries provide significant improvements at least.
Click to expand...
Click to collapse
There might be as there are new binaries I believe. I'll need to check when I'm home.
BRKotucs said:
No need to unroot to flash the new images..
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Right that was only for flashing OTA update files right? Doing it through fastboot should just work, taking nandroid and then flashing after will post status
Flashed it, but manually disabled force encryption in kernel.
Interesting that I'm not getting 200+/60+ as before, it is 160/140 with no encryption, will check other benchmarks and may be some background load in progress as I just first booted after flash.
Can someone tell me how to flash this right?
im on stock, decrypted and rooted+TRWP on it.
do i need to start all over after flashing?
XorZone said:
Flashed it, but manually disabled force encryption in kernel.
Interesting that I'm not getting 200+/60+ as before, it is 160/140 with no encryption, will check other benchmarks and may be some background load in progress as I just first booted after flash.
Click to expand...
Click to collapse
How did you disable the encryption in kernel, before I remember just using a modified boot image, dont know if that one will work for the new 5.0.1 factory image though, did you use the same boot image from this link to do this before updating?
http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
---------- Post added at 06:59 AM ---------- Previous post was at 06:57 AM ----------
Silentsoul said:
Can someone tell me how to flash this right?
im on stock, decrypted and rooted+TRWP on it.
do i need to start all over after flashing?
Click to expand...
Click to collapse
So I was same, root with decrypted kernel and TWRP. I updated manually but forgot I had it decrypted, its encrypting right now, good thing I took a nandroid before so I am going to restore back to that image and try again with that modified boot image like I did before when I decrypted it and will let you know.
Silentsoul said:
Can someone tell me how to flash this right?
im on stock, decrypted and rooted+TRWP on it.
do i need to start all over after flashing?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2954008
Sent from my Nexus 4 using Tapatalk
wolfnumba1 said:
How did you disable the encryption in kernel, before I remember just using a modified boot image, dont know if that one will work for the new 5.0.1 factory image though, did you use the same boot image from this link to do this before updating?
http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
Click to expand...
Click to collapse
Nope, I took 5.0.1 kernel, unpacked it, changed from force encrypt to encryptable and repacked. Will post it in that thread as soon as I'll get back to PC.
XorZone said:
Flashed it, but manually disabled force encryption in kernel.
Interesting that I'm not getting 200+/60+ as before, it is 160/140 with no encryption, will check other benchmarks and may be some background load in progress as I just first booted after flash.
Click to expand...
Click to collapse
I have noticed the same thing on 5.0
I got the amazing speeds upon first boot after flashing then never again. 160/140 is similar to what i'm getting now. was that the same as encrypted?
Maybe it was all a placebo.
No force encryption boot img here:
http://forum.xda-developers.com/showpost.php?p=57406510&postcount=360
XorZone said:
No force encryption boot img here:
http://forum.xda-developers.com/showpost.php?p=57406510&postcount=360
Click to expand...
Click to collapse
Thanks!
wolfnumba1 said:
So I was same, root with decrypted kernel and TWRP. I updated manually but forgot I had it decrypted, its encrypting right now, good thing I took a nandroid before so I am going to restore back to that image and try again with that modified boot image like I did before when I decrypted it and will let you know.
Click to expand...
Click to collapse
Curious to see if root will still work? I am not sure if we will need an updated img to fastboot flash boot to get root again.
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
XorZone said:
Flashed it, but manually disabled force encryption in kernel.
Interesting that I'm not getting 200+/60+ as before, it is 160/140 with no encryption, will check other benchmarks and may be some background load in progress as I just first booted after flash.
Click to expand...
Click to collapse
What app are you using to measure?
joderme said:
Curious to see if root will still work? I am not sure if we will need an updated img to fastboot flash boot to get root again.
Ill let you know, its updating now after flashing however I am going to reflash like I said before, I will check root status first though, I am sure the root is gone now.
Click to expand...
Click to collapse
joderme said:
Curious to see if root will still work? I am not sure if we will need an updated img to fastboot flash boot to get root again.
What app are you using to measure?
Click to expand...
Click to collapse
1. cf-autoroot after flashing and 1 time booting works fine
2. androbench
Is the kernel the same? I'm curious if they changed it.
Searched all over XDA, could not find one. The only one which is there is of an October build. Anyone has the flashable of the latest build including the January security fixes?
rajarshi10 said:
Searched all over XDA, could not find one. The only one which is there is of an October build. Anyone has the flashable of the latest build including the January security fixes?
Click to expand...
Click to collapse
Just download the factory image and use fastboot to flash the update.
Shockz said:
Just download the factory image and use fastboot to flash the update.
Click to expand...
Click to collapse
That is one thing that can be done, but I like keeping a backup zip in case something goes wrong. So you have it? Or know anyone who has it?
rajarshi10 said:
That is one thing that can be done, but I like keeping a backup zip in case something goes wrong. So you have it? Or know anyone who has it?
Click to expand...
Click to collapse
The image you download is yours to keep.
https://developers.google.com/android/nexus/images?hl=en#angler
Shockz said:
Just download the factory image and use fastboot to flash the update.
Click to expand...
Click to collapse
XxMORPHEOUSxX said:
The image you download is yours to keep.
https://developers.google.com/android/nexus/images?hl=en#angler
Click to expand...
Click to collapse
And doesn't this wipe the internal storage as well?
rajarshi10 said:
And doesn't this wipe the internal storage as well?
Click to expand...
Click to collapse
If you use the flash all script. Otherwise you can pick and choose what images you want to use.
I read that you can use the flash-all script without it deleting all your data. Just open the script with a text editor and remove "-w" from the last line. I personally did NOT do that, its just something I've read here on XDA. I followed Heisenberg's guide, step 10, to a T and everything went well. Remember you will have to reflash recovery and SuperSU again if you want those back.
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