Related
Hey all, Team Black Hat have released a series of update.zip’s that will allow you to easily flash the newest kernel, radio, system, and bootloader. Thought some might wanna download ASAP in case they get pulled.
Article About it here:
http://www.gizmoninja.com/2010/12/1...date-your-kernel-system-radio-and-bootloader/
Direct link To Team Black Hat Thread and Downloads:
http://www.mydroidworld.com/forums/...ystem-baseband-2-3-340-kernel-bootloader.html
Cheers! And all credit and thanks foes to Team Black Hat!
If I flash the system.zip from recovery will it take me from Tranquility 3.6 back to stock? What's the best way to go from Tranq back to stock? Thanks.
Flashing the kernel and radio as I type.
aaaaand SBF time lol.
Sorry.. just trying to understand...
I have downloaded these 4 files. Now I go to Bootstrap/Recovery and use the Update.zip option for these files one at a time? (in a particular order?) OR do I re-name them update.zip one at a time?
Secondly, I have ApeX 1.2.1 installed... it's working with .320 and I wonder if it will work with the new files?
Any advice on these 2 things. (please)
Thanks.
romanvail said:
Sorry.. just trying to understand...
I have downloaded these 4 files. Now I go to Bootstrap/Recovery and use the Update.zip option for these files one at a time? (in a particular order?) OR do I re-name them update.zip one at a time?
Secondly, I have ApeX 1.2.1 installed... it's working with .320 and I wonder if it will work with the new files?
Any advice on these 2 things. (please)
Thanks.
Click to expand...
Click to collapse
To answer your first question, we don't need to rename them. We can got o bootstrap and update them one by one. I don't think there's a particular order, however, I do think that we can only do one at a time (install one and then reboot)
I'm not sure about coming from Apex, i'm personally coming from Fission 2.3.1, and I am a little scared to do these....
zeavott said:
To answer your first question, we don't need to rename them. We can got o bootstrap and update them one by one. I don't think there's a particular order, however, I do think that we can only do one at a time (install one and then reboot)
I'm not sure about coming from Apex, i'm personally coming from Fission 2.3.1, and I am a little scared to do these....
Click to expand...
Click to collapse
Yeah no renaming is needed.
I am on fission 2.3.1 as well, flashed the Kernel, Bootloader, and Radio Image all one after another while in clockworkmod recovery, and had 0 issues.
U will have to *228 again after radio, but other than that u its fine.
So I just got a question..is this the file that is downloaded ota or put together by these guys? I only ask cause trying to understand why we can't just throw in our own stuff in this update.zip and resign it..but I am sure there is some kind of keys we will be missing
Did the 2.3.340 SBF also update the radio or should I use the .zip to update that?
mdhaliwal said:
So I just got a question..is this the file that is downloaded ota or put together by these guys? I only ask cause trying to understand why we can't just throw in our own stuff in this update.zip and resign it..but I am sure there is some kind of keys we will be missing
Click to expand...
Click to collapse
Lol, if only it were that simple, unfortunately we can't because of the bootloader being locked, it wont pass security, so we can only modify or use their kernels.
Sunblood said:
Did the 2.3.340 SBF also update the radio or should I use the .zip to update that?
Click to expand...
Click to collapse
If u did the .340 sbf u should be all up to date, this is more for .320 users and such. U can double check ur kernel, radio version in about phone though as well.
ive recently upgraded from my Eris to an X so im having a hard time understanding all of what i need to do, ive downloaded these files and saved them cuz im sure ill need them as soon as i learn everything can anyone point me to a cut and dry tutorial or some kind of explanation? thanks!!!!! loving the x already
edit: i am searching while im waiting for an answer, my bootloader says 30.04 but i dont understand the whole sbf stuff and i can get into clockworkmod recovery im not completely helpless just a little lost after playing with my eris so much.
Confused
I downloaded each file then rebooted into recovery. I installed each file one by one. I reboot system out of recovery and I get a black screen that says:
Bootloader
30.04
Err: A5, 70, 39, 00, 27
Battery OK
OK to Program
Transfer Mode:
USB
btw as far as i can see by the numbers my version is the .340 and the 1.09.07P baseband....i updated mine yesterday
acidbath5546 said:
If u did the .340 sbf u should be all up to date, this is more for .320 users and such. U can double check ur kernel, radio version in about phone though as well.
Click to expand...
Click to collapse
The .340 sbf is system only so no he wouldn't be up to date. His system would but not anything else. Still have to apply the patches if you want to be 100% up to date with everything.
mob87 said:
The .340 sbf is system only so no he wouldn't be up to date. His system would but not anything else. Still have to apply the patches if you want to be 100% up to date with everything.
Click to expand...
Click to collapse
k thanks guys updating now
mob87 said:
The .340 sbf is system only so no he wouldn't be up to date. His system would but not anything else. Still have to apply the patches if you want to be 100% up to date with everything.
Click to expand...
Click to collapse
Oh yeah ur right...forgot .340 is system only...haven't had to SBF in a long time...lol
Thanks for catching that.
I am on Fission 2.2.2 (FRG83), would these updates work for me?
So I am somewhat familiar and want to make sure. I can not get my 2.3. 340 update to go will these files let me do this
Sent from my DROIDX
im at the same screen what to do??
Here is the update that the test phones(4.0.19915 to 4.1.26) received right before the launch of the retail unit. You might think this is useless, but it paints a very clear picture of how Moto updates work on the Atrix.
For each file that is being updated it hash checks and then applies the binary patch. This means changing the file permissions, mounting the system as rw will not cause this to fail as someone else had mentioned before. When it comes time to update, we can extract it and run the patch against the retail dump to create an updated dump.
This also tells us we can use recovery to flash update.zip files, we just need to figure it out. This would be very helpful when creating an updated dump.
This file is downloaded to /cache/tmp. A simple script was used to capture it before it was deleted.
Download the file here:
http://www.ponack.net/designgears/atrix/update.7z
This is very good news.
does this also mean that an OTA can be packaged as a zip and "flashed" to a phone?
verrry nice
Thanks DG!
and please stay
we will miss you
GSeeker said:
Thanks DG!
and please stay
we will miss you
Click to expand...
Click to collapse
I will still be around doing things here and there
Anyway to unbrick my atrix with this?
hassanjanjua2002 said:
Anyway to unbrick my atrix with this?
Click to expand...
Click to collapse
What kind of brick do you have on your hands?
Also, thanks dg
Very informative!
Hmmm, tried to flash it as an update.zip through recovery and signature check failed. I'm guessing since this was prior to release it was test signed? Had to try since I need something via RSD, Recovery, or Fastboot to get my phone up and running again.
navalynt said:
Hmmm, tried to flash it as an update.zip through recovery and signature check failed. I'm guessing since this was prior to release it was test signed? Had to try since I need something via RSD, Recovery, or Fastboot to get my phone up and running again.
Click to expand...
Click to collapse
If you look in there you can see that it updates recovery, I am assuming it signs it and requires a signature now.
might want to try one with a test signature and see if that works.
Im on my tablet no computer. . . Is there a boot.bin in therr if so id like to run it through my keyfind program see if i can find the same aes key in it
t0dbld said:
Im on my tablet no computer. . . Is there a boot.bin in therr if so id like to run it through my keyfind program see if i can find the same aes key in it
Click to expand...
Click to collapse
baseband_ota.img and mbm_combo.bin
I want Update.zip signed for this orginal files from /system/lib
libskia.so
libskiagl.so
libwebcore.so
Because I changed these files to make the device read Arabic, but the device stops working and Restart
Now I want to push this and return the original files
designgears said:
baseband_ota.img and mbm_combo.bin
Click to expand...
Click to collapse
Lol damnit lying in bed so tired , but so tempted by what ever mbm_combo.bin is but linux machine and keyfind back at my store only cr-48 and mac air here not enough processing power :-( anyhow thanks so much for post i cant wait to check it out. On side note you sure you going to leave dg ? I mean ever sense we got dock hack figured out im more leaning twoards keeping it . . Also because this is first cheep device i have bought $150 small invesment payed $500 or more for most my devices and cause i think we will get bootloader now and something seems weird abiut that dev dump of gb being vanilla. Maybe an option they will offer to quiet the devs anyhow at least keep posting us the leaks if you wont stay
designgears said:
If you look in there you can see that it updates recovery, I am assuming it signs it and requires a signature now.
might want to try one with a test signature and see if that works.
Same situation here, as you already know. is there a forum for one with a test signature?
Click to expand...
Click to collapse
Im not a dev far from one but from what i am reading this sounds like some pretty good information has been gathered just from this old update.....Also you dont have to stay just keep the leaks and any others a coming....Thanks
it seems as they signed all of the partitions... have you guys looked at the odexed version.... under recoveryand overall... what are they trying to patch... BZIP2 is attached and renamed "updater"??? Also traces of BSDIFF just like in other moto images... .
Also this is from the radio_baseband image...
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_mc.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_error_handler.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_flash.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_configure.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_partition.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_loader.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_auth.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_target_accessor.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/shared/src/dbl_parser.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/target/qsc6695/src/dbl_target.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/target/qsc6695/src/dbl_flash_nand.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/target/qsc6695/src/dbl_flash_onenand.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/target/qsc6695/src/dbl_flash_shared.c
/localrepo/wxnk36/oly16101P/mdm6600/core/boot/secboot2/dbl/target/qsc6695/src/dbl_clk.c
OLYMPUSBP_N_01.61.01P.dbl
hassanjanjua2002 said:
designgears said:
If you look in there you can see that it updates recovery, I am assuming it signs it and requires a signature now.
might want to try one with a test signature and see if that works.
Same situation here, as you already know. is there a forum for one with a test signature?
Click to expand...
Click to collapse
are you brave enough to flash the engineering bootloader from the other tread.... ?
It might circumvent the signature checks...
Click to expand...
Click to collapse
zambezy said:
are you brave enough to flash the engineering bootloader from the other tread.... ?
It might circumvent the signature checks...
Click to expand...
Click to collapse
Not saying that I will do it, but; How would we flash those *.bin files to the phone?
mp2ning said:
Not saying that I will do it, but; How would we flash those *.bin files to the phone?
Click to expand...
Click to collapse
I'm guessing with NVFlasher
Hi guys,
Found the official package for 513
http://mobileupdate.dell.com/PackageProductionLocations/LG7-820W_513_20588_00.pkg
one more problem, I still dont know how to extract or prepare the recovery image from pkg files
Can anybody please guide me how?Please.. I think this is my last resort so I can get back to stock recovery.
thanks...
Hmm, seems like only the version available is the EU 3g one, I know for a fact that the EU wifi one also exists and assume the US 4g/wifi ones should too.
Will have it decrypted and uploaded in a few hours
513 is decrypted and uploaded now, you can find the recovery link on the wiki,
no patch notes, 514 is nearly identical to 506/7 and 513 should be just about the same
TheManii said:
513 is decrypted and uploaded now, you can find the recovery link on the wiki,
no patch notes, 514 is nearly identical to 506/7 and 513 should be just about the same
Click to expand...
Click to collapse
thanks TheManii..for decrypting the files (and sorry for bugging you in PM), unfortunately it did'nt resolved my problem about flashing a new recovery.
The read-only issue is my most probably my problem that is why I cannot overwrite the recovery on my DS7 and why everytime I put a new file on sdcard it disappear after rebooting.
Guess I have to call dell / retailer for return and fix it. Its a known issue as per what I read on the forums and hopefully they will acknowledge that fault.
thanks much bro!
I had that happen before I just pin hole off and apx mode and do a nvflash. I also manipulated the .img
So it had my service tag and serial number. I'm doubt changing the service tag fixed anything but I did that just in case nvflash didn't work and I'd have to send it in
Sent from my Nexus S 4G using xda premium
Subject says it all. No luck with Google. Don't want to update until I know what's being updated.
Sent from my HTC first using xda app-developers app
not sure but...
jonslice said:
Subject says it all. No luck with Google. Don't want to update until I know what's being updated.
Sent from my HTC first using xda app-developers app
Click to expand...
Click to collapse
I installed the update last night. I honestly don't know what all the changes are, but I'm pretty sure it is a bugfix release. Still android 4.1.2. The only thing that I have noticed is that after the update my led will actually flash green for a text message or email. Before the update, my led only worked for charging, so I would have no idea whether I had email or messages without turning my screen on.
I have not noticed any other changes. No noticable speedups or slowdowns. Haven't discovered any issues. None of my apps have ever forced closed on this phone, and that has not changed after the update.
So...not a bad upgrade, although it might be pointless if you don't have any issues.
19.8MB update. Can't be too much going on in there, but I'd also think it's more than a few lines of code being updated...
Ooh, fun. Looks like I can't install the OTA with CWM or TWRP. Jonslice, are you rooted?
EDIT:
Weird. Now my phone says the software is up to date. What's the Build info under About Phone for you guys? Wondering if it did actually update even though it said it failed...
The OTA zip is on my dropbox in case anyone is curious to look at it. [1] Looks to me like it's updating a handful of system files, as well as the boot and recovery images. With clockworkmod installed, I was prompted to confirm installing the update because its signature wasn't verified, but I haven't yet attempted to let it install it. This should definitely give us an "official" image for the boot and recovery partitions though, which never hurts.
1: https://dl.dropboxusercontent.com/u/7859496/Android/mystul/OTAPkg.zip
nuclear_eclipse said:
The OTA zip is on my dropbox in case anyone is curious to look at it. [1] Looks to me like it's updating a handful of system files, as well as the boot and recovery images. With clockworkmod installed, I was prompted to confirm installing the update because its signature wasn't verified, but I haven't yet attempted to let it install it. This should definitely give us an "official" image for the boot and recovery partitions though, which never hurts.
1: https://dl.dropboxusercontent.com/u/7859496/Android/mystul/OTAPkg.zip
Click to expand...
Click to collapse
It'll fail if you try to install it. I'm thinking it needs the official bootloader to work. Someone will need to make this flashable. I was trying to extract it from my phone, but you beat me to it. Thanks!
chrisliphart said:
It'll fail if you try to install it. I'm thinking it needs the official bootloader to work. Someone will need to make this flashable. I was trying to extract it from my phone, but you beat me to it. Thanks!
Click to expand...
Click to collapse
I pulled this recovery.img from the firmware.zip that's included inside OTAPkg.zip: https://dl.dropboxusercontent.com/u/7859496/Android/mystul/recovery.img
I would assume that a simple `fastboot flash recovery recovery.img` should suffice.
nuclear_eclipse said:
I pulled this recovery.img from the firmware.zip that's included inside OTAPkg.zip: https://dl.dropboxusercontent.com/u/7859496/Android/mystul/recovery.img
I would assume that a simple `fastboot flash recovery recovery.img` should suffice.
Click to expand...
Click to collapse
Huh. I couldn't get the Firmware.zip to open on my system. Thanks for doing that. Now I'm gonna go be an idiot and possibly brick my device by pushing this recovery to my phone to try and install the OTA. lol
I did also manage to snag the recovery.log from clockwork recovery when the update first tried to run, just in case that actually proves useful to anyone... https://dl.dropboxusercontent.com/u/7859496/Android/mystul/recovery.log
nuclear_eclipse said:
I did also manage to snag the recovery.log from clockwork recovery when the update first tried to run, just in case that actually proves useful to anyone... https://dl.dropboxusercontent.com/u/7859496/Android/mystul/recovery.log
Click to expand...
Click to collapse
Thanks. I posted both the update and your log to the development forum to see if someone with more knowledge can do anything with them.
For the record, pushing that recovery doesn't work. Well, pushing it works, but you can't get into it on the phone. I repushed TWRP to my phone in the interim.
chrisliphart said:
19.8MB update. Can't be too much going on in there, but I'd also think it's more than a few lines of code being updated...
Ooh, fun. Looks like I can't install the OTA with CWM or TWRP. Jonslice, are you rooted?
EDIT:
Weird. Now my phone says the software is up to date. What's the Build info under About Phone for you guys? Wondering if it did actually update even though it said it failed...
Click to expand...
Click to collapse
I got failed update with CWM also. I'll try to post a build info screen shot once I'm on my desktop when my work week is over. Manual check for update says I still need update.
Note: unlocked boot loader, CWM and rooted.
Sent from my HTC first using xda app-developers app
As long as this doesn't remove the ability to disable Facebook Home, I'll probably update it. Can anyone confirm that this is the case?
Daman09 said:
As long as this doesn't remove the ability to disable Facebook Home, I'll probably update it. Can anyone confirm that this is the case?
Click to expand...
Click to collapse
That's a feature of Home, not the firmware. So yeah, you can still disable it. I don't ever see even Facebook changing that.
My gear live was rooted had twrp on it and i was trying to update it to the newest android wear os i couldn't update it with twrp on it and i tried adb sideload with no luck restarted it restarted my phone no luck so i tried the stock recovery no luck with adb sideload i factory reset my watch everything was fine it downloaded an update which was KNX01Q so i reset the device again and it did the download again but this time it failed in recovery so i flashed the stock img from the gear live restore tool v3 now my watch is on KGW42N and i can't get it to connect to my phone it doesn't show up at all in android wear the weirdest part i used to have an option to search for Bluetooth devices in the watch settings but now there's no option and since i can't connect it to my phone i can't even connect it to my pc says adb device unauthorized.. i can get into recovery the bootloader of the watch it even starts up but it stays at the screen saying to install android wear on your phone but i can't recognize the watch it's like the Bluetooth is off or not working on the watch? Anyone have any ideas or workarounds for an unauthorized adb device?? Any help would be appreciated.
I'm having the same issue. I tried to go back to 100% stock so I could download the newest update, but now my phone doesn't recognize the watch via Bluetooth at all..
Edit: Fixed it, fastboot flashed the stock KMV78Y located here: http://forum.xda-developers.com/gear-live/development/rom-octamodwear-stock-root-busybox-t2834620
For people using the Samsung Gear Live Restore Tool, if that stock image worked for you, I would recommend replacing your 42Nboot.img and 42Nsystem.img with the ones in the above for future endeavors.
Also, that zip file needs a lot more attention in these forums.
YES!!!!
bkid001 said:
i'm having the same issue. I tried to go back to 100% stock so i could download the newest update, but now my phone doesn't recognize the watch via bluetooth at all..
Edit: Fixed it, fastboot flashed the stock kmv78y located here: http://forum.xda-developers.com/gear-live/development/rom-octamodwear-stock-root-busybox-t2834620
for people using the samsung gear live restore tool, if that stock image worked for you, i would recommend replacing your 42nboot.img and 42nsystem.img with the ones in the above for future endeavors.
Also, that zip file needs a lot more attention in these forums.
Click to expand...
Click to collapse
thank you so much you are the best!!
Bkid001 said:
I'm having the same issue. I tried to go back to 100% stock so I could download the newest update, but now my phone doesn't recognize the watch via Bluetooth at all..
Edit: Fixed it, fastboot flashed the stock KMV78Y located here: http://forum.xda-developers.com/gear-live/development/rom-octamodwear-stock-root-busybox-t2834620
For people using the Samsung Gear Live Restore Tool, if that stock image worked for you, I would recommend replacing your 42Nboot.img and 42Nsystem.img with the ones in the above for future endeavors.
Also, that zip file needs a lot more attention in these forums.
Click to expand...
Click to collapse
DUDE!! You totally fixed all the problems I was having with my gear live. I am a late adopter and had so much trouble with it. After flashing that firmware, the watch upgraded to 6.0.1. All my syncing issues, updating issues, every issue I had fixed. Thanks soo much. This is my second one. Had to return the other. Just another thanks. You the man.
No problem guys! I didn't even remember this post, and the only way I knew about it was an email I got because I was quoted
Bkid001 said:
No problem guys! I didn't even remember this post, and the only way I knew about it was an email I got because I was quoted
Click to expand...
Click to collapse
You still the man!! May not seem like a lot for some people but I just wanted a cheap fitness/smartwatch tracker. This was the thing to get. Got it off Amazon and first one was sh!t. Wouldn't sync, update, or anything. Second one was dead. Tried your method on the first one and it revived it! Now it's the smart watch I had imagined it to be. Cheap, good specs, and a fitness tracker. Can't thank you enough.
quantump8 said:
DUDE!! You totally fixed all the problems I was having with my gear live. I am a late adopter and had so much trouble with it. After flashing that firmware, the watch upgraded to 6.0.1. All my syncing issues, updating issues, every issue I had fixed. Thanks soo much. This is my second one. Had to return the other. Just another thanks. You the man.
Click to expand...
Click to collapse
When you say flashed, do you mean that you took the files fro the stock rom he listed in his post, and replaced the "78Y" files with the ones from the post?
Deathscreton said:
When you say flashed, do you mean that you took the files fro the stock rom he listed in his post, and replaced the "78Y" files with the ones from the post?
Click to expand...
Click to collapse
I took the boot.img and system.img from the "78Y" file and replaced the boot.img and system.img from the Samsung Gear Live Restore tool files. But you have to make sure you rename them "42Nboot.img and 42Nsystem.img" before the tool will recognize them. Hope this helps.
quantump8 said:
I took the boot.img and system.img from the "78Y" file and replaced the boot.img and system.img from the Samsung Gear Live Restore tool files. But you have to make sure you rename them "42Nboot.img and 42Nsystem.img" before the tool will recognize them. Hope this helps.
Click to expand...
Click to collapse
I'm not sure I understand. Maybe I confused myself, so let me ask again. xD
I have the original Samsung Gear Live Restore Tool v2 folder on my desktop. Inside, I have the 78Y files, (boot, recovery and system in that order) that are located in that folder. These are the files that need to be replaced by the originals linked above (kmv78y)that solved the issues, correct? I don't have any "42Nboot.img" or "42Nsystem.img" files. Just the ones I listed.
When I downloaded the link to the original stock ROM from the post above, all that was there was a system and boot img, which I assume is what needs to be renamed "42xxxx.img" according to your post, do I correct? And even if that is correct, the Samsung Restore Tool is scripted to look for the 78Y files, not any type of 42N files.
Deathscreton said:
I'm not sure I understand. Maybe I confused myself, so let me ask again. xD
I have the original Samsung Gear Live Restore Tool v2 folder on my desktop. Inside, I have the 78Y files, (boot, recovery and system in that order) that are located in that folder. These are the files that need to be replaced by the originals linked above (kmv78y)that solved the issues, correct? I don't have any "42Nboot.img" or "42Nsystem.img" files. Just the ones I listed.
When I downloaded the link to the original stock ROM from the post above, all that was there was a system and boot img, which I assume is what needs to be renamed "42xxxx.img" according to your post, do I correct? And even if that is correct, the Samsung Restore Tool is scripted to look for the 78Y files, not any type of 42N files.
Click to expand...
Click to collapse
Whatever the files names are, just replace them with the ones from 78Y file. For me, the files from the original tool had "42N" before the system.img name and the tool wouldnt work until I changed the file names. If they are just system.img and boot.img, then just replace without renaming. But all img files must be the same name. Like I said, at least for me, this was the way it worked.
quantump8 said:
Whatever the files names are, just replace them with the ones from 78Y file. For me, the files from the original tool had "42N" before the system.img name and the tool wouldnt work until I changed the file names. If they are just system.img and boot.img, then just replace without renaming. But all img files must be the same name. Like I said, at least for me, this was the way it worked.
Click to expand...
Click to collapse
I ended up trying this and I still have a few problems regarding Contacts (Try again on your phone) and Play Music (Your phone is not nearby...). Maybe app specific issues. I appreciate the help though. :c