[HOWTO] Update to 2.3.3 Baseband (I9020XXKB1) without 2.3.3 OTA - Nexus S Android Development

Hello all.
I know I, among others are delaying updating to 2.3.3 due to many issues with the update, but would like to have the improvements brought by the new radio image, which will hopefully reduce reboots during phone calls, reception dropping issues, etc. So I went on a quest looking for a way to update just the radio image without having to go through updating to 2.3.3 and reverting back to my CM7 nandroid, etc.
This requires just one thing: fastboot working properly on your Windows/Linux/OS X machine. If you don't know how to set up fastboot, there are plenty of guides on how to do so here on XDA
Step 1: Confirm that you have the original 2.3.2 baseband.
You can check this information by going to settings, about phone, and looking in the baseband version. The original baseband is I9020XXJK8
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If your baseband is I9020XXKB1, then you are already on the latest radio, which came with 2.3.3​
Step 2: Procure the 2.3.3 radio.img file. I have uploaded this file here:
radio.img
MD5 (radio.img) = 942c7f6339e6ada5a58cf656c3f1fd4a
Or, if you'd rather not trust a random stranger , you can extract the radio.img file from the official full update file from Google, which can be found here:
http://android.clients.google.com/packages/ota/google_crespo/f182cf141e6a.signed-soju-ota-102588.f182cf14.zip
Once you have this file, place it on your computer in the directory from where you'll be running fastboot (oftentimes in your sdk/tools directory, but if you have that directory in your PATH, just your working directory from where you'll run your command prompt).​
Step 3: flash the radio.img using fastboot.
You need to put your phone into fastboot mode. Power it down. Then, press and hold power and volume up for a few seconds to enter fastboot mode. Once your phone is connected to your computer in fastboot mode, you can run the following command:
Code:
fastboot flash radio radio.img
On my Windows machine, this was the output. You will see something similar:
Code:
C:\Users\Andrew\Desktop>fastboot flash radio radio.img
sending 'radio' (12288 KB)... OKAY [ 1.918s]
writing 'radio'... OKAY [ 1.694s]
finished. total time: 3.612s
Once that's done, just reboot the phone from the fastboot menu.​
Step 4: Confirm that your baseband has been updated.
Once again, go to settings, about phone, and confirm that you have the new baseband I9020XXKB1
Congratulations! You've updated the baseband on your Nexus S to the latest version.​
Please let me know where I can find the original 2.3.2 radio.img for those who follow this guide and wish to revert. The procedure is exactly the same, but with a different .img file

thanks, flashed it and got no problem

thank you

bigxie said:
Please let me know where I can find the original 2.3.2 radio.img for those who follow this guide and wish to revert. The procedure is exactly the same, but with a different .img file
Click to expand...
Click to collapse
Is it possible to extract the radio image from the phone?
I'm already updated, so too late for me. I have a copy of the I9020XXJK1 radio, though.

I'm almost certain that you can, but I overlooked that :/
Now it's too late for me too

It might be possible to do a reverse patch of I9020XXKB1 with the radio.img.p file in the GRI40-from-GRH78x zip.
If you can patch from I9020XXJK8 to I9020XXKB1, then you should be able to the reverse as well.

shrivelfig said:
It might be possible to do a reverse patch of I9020XXKB1 with the radio.img.p file in the GRI40-from-GRH78x zip.
If you can patch from I9020XXJK8 to I9020XXKB1, then you should be able to the reverse as well.
Click to expand...
Click to collapse
No radio in that update.

People install new radio! !! And try to call

Heres the GB 2.3.3 Radio update that can be flashed through recovery:
http://forum.xda-developers.com/showthread.php?t=971272

frank707 said:
No radio in that update.
Click to expand...
Click to collapse
There's a radio patch file. Radio on phone + patch file = new radio.
Anyway, the radio is apparently in /proc/mtd/mtd5, so a dd command might do the trick.
Code:
dev: size erasesize name
mtd0: 00200000 00040000 "bootloader"
mtd1: 00140000 00040000 "misc"
mtd2: 00800000 00040000 "boot"
mtd3: 00800000 00040000 "recovery"
mtd4: 1d580000 00040000 "cache"
mtd5: 00d80000 00040000 "radio"
mtd6: 006c0000 00040000 "efs"
Code:
dd if=/dev/mtd/mtd5 of=/sdcard/radio.img bs=4096
or possibly
Code:
dd if=/dev/mtd/mtd5 of=/sdcard/radio.img count=14155776
Any volunteers?
Edit:
OK, this actually worked:
Code:
dd if=/dev/mtd/mtd5 of=/sdcard/radio.img count=14155776
I ended up with a file that was byte-by-byte identical to the radio.img in the original update zip. Except it was too large, the original radio.img is only 12583040 bytes long. I don't know the size of I9020XXJK8, but both I9020XXJK1 and I9020XXKB1 are 12583040 bytes.

Can anyone upload the 2.3.2 radio.
The phone now has no reception and android.phone FC's

2.3.2 Baseband
Hi!
For those who might be interested I posted the 2.3.2 Baseband here in a Clockwork Recovery flashable file
http://forum.xda-developers.com/showthread.php?p=11681261&posted=1#post11681261

mazodude said:
Can anyone upload the 2.3.2 radio.
The phone now has no reception and android.phone FC's
Click to expand...
Click to collapse
I fixed it.
Just had to reflash CM7

Here's my collection of Nexus S baseband files:
I9020XXJK1 (GRH35): http://www.mediafire.com/?k7z99q74x84nwsp
(old, don't use, included for research purposes)
I9020XXJK8 (GRH78): http://www.mediafire.com/?kwk5oi05uyh0a8l
SHA1: 02ac1c1b37bff7e41d0249cd13f91f9f35ff9e04 (matches the official value)
Thanks to sdelmont!
I9020XXKB1 (GRI40): http://www.mediafire.com/?44ol19b39o4cjpm
SHA1: 01a21ee05d8143c015499f50be6944347d70dfd0 (matches the official value)
I9023XXKB3 (GRI54): http://www.mediafire.com/?a5etgvk2tbsxtwy
Thanks to www.SamFirmware.com!
From the official GRI40-from-GRH78 update zip:
Code:
assert(apply_patch_check("MTD:radio:12583040:02ac1c1b37bff7e41d0249cd13f91f9f35ff9e04:12583040:01a21ee05d8143c015499f50be6944347d70dfd0"));
As you can see, the SHA1 from I9020XXJK8 and I9020XXKB1 matches the values in the official assert check statement.

shrivelfig said:
here's my collection of nexus s baseband files:
I9020xxjk1 (grh35): http://www.mediafire.com/?k7z99q74x84nwsp
(old, don't use, included for research purposes)
i9020xxjk8 (grh78): http://www.mediafire.com/?kwk5oi05uyh0a8l
sha1: 02ac1c1b37bff7e41d0249cd13f91f9f35ff9e04 (matches the official value)
i9020xxkb1 (gri40): http://www.mediafire.com/?44ol19b39o4cjpm
sha1: 01a21ee05d8143c015499f50be6944347d70dfd0 (matches the official value)
i9023xxkb3 (gri54): http://www.mediafire.com/?a5etgvk2tbsxtwy
thanks to www.samfirmware.com!
From the official gri40-from-grh78 update zip:
Code:
assert(apply_patch_check("mtd:radio:12583040:02ac1c1b37bff7e41d0249cd13f91f9f35ff9e04:12583040:01a21ee05d8143c015499f50be6944347d70dfd0"));
as you can see, the sha1 from i9020xxjk8 and i9020xxkb1 matches the values in the official assert check statement. :d
Click to expand...
Click to collapse
thank you so much!

thanks, I flashed the i9023xxkb3 radio on my i9020 Nexus S, and it shows i9020xxkb3...

Thanks! Works great on CM7.

Does it matter what ROM you are on? i.e., CM7 nightly with this baseband?

There is already a post about this that comes with a zip that you flash in clockworkmod.
Sent from my Nexus S using XDA App

but this is old rooom
where the official to Nexus s Ics i 9020?
please help

Related

[SPLASH] A few splash screens

Just knocked together this splash screen for all your s-off phones to make it look a bit diff
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
splashnew.img
splashCM.img
Hope u all like
[To install]
What you need
-- Fastboot set up
-- the attached spashnew.zip
1) extract the .img from the zip file
2) reboot into fastboot mode
3) run
fastboot flash splash1 splash.img
Click to expand...
Click to collapse
(Replace splash.img with the .img u want
4) run
fastboot reboot
Click to expand...
Click to collapse
Have Fun
Thanks for these, the first one looks brilliant on my device!
Thanks for the instructions, if anyone wants some more really nice ones for Cyanogen look here:
http://forum.xda-developers.com/showthread.php?t=807130
I'm using #4, looks great on DHD!
Awesome, this is something I've wanted to do for a long time. many thanks
Cheers Apache.
Can someone please post the original DesireHD splash?
Thanks
I used another Cyanogen spalsh screen......who wants the crappy green HTC anyways hahaha..
Is there a way to flash this without using a PC and fastboot?
I've read in other forums and tried to rename the zip PD98IMO.ZIP and flash in automatically from HBOOT but I get an error because android-info.txt isn't correct for this phone.
Can anyone help please?
Sent from my CyanogenMod Desire HD
timstanley1985 said:
Is there a way to flash this without using a PC and fastboot?
I've read in other forums and tried to rename the zip PD98IMO.ZIP and flash in automatically from HBOOT but I get an error because android-info.txt isn't correct for this phone.
Can anyone help please?
Sent from my CyanogenMod Desire HD
Click to expand...
Click to collapse
THIS IS NOT RECOMMENDED AND YOU MIGHT BRICK YOUR DEVICE, but you can save the .img file in your SD-Card and using a terminal application type:
Code:
dd if=/sdcard/splash.img of=/dev/block/mmcblk0p19
it should work, but I take no responsibility, you've been warned.
Anyway, here's my contribution (you can find it attached, unzip first) :
View attachment hungry.7z
phunkycow said:
THIS IS NOT RECOMMENDED AND YOU MIGHT BRICK YOUR DEVICE, but you can save the .img file in your SD-Card and using a terminal application type:
Code:
dd if=/sdcard/splash.img of=/dev/block/mmcblk0p19
it should work, but I take no responsibility, you've been warned.
Anyway, here's my contribution (you can find it attached, unzip first) :
View attachment 462548
Click to expand...
Click to collapse
Haha, the picture is cute. Definitely using it.
So cuuuute ! I use it thanks
phunkycow said:
THIS IS NOT RECOMMENDED AND YOU MIGHT BRICK YOUR DEVICE, but you can save the .img file in your SD-Card and using a terminal application type:
Code:
dd if=/sdcard/splash.img of=/dev/block/mmcblk0p19
it should work, but I take no responsibility, you've been warned.
Anyway, here's my contribution (you can find it attached, unzip first) :
View attachment 462548
Click to expand...
Click to collapse
nice one. currently on my dhd now
nailmind said:
nice one. currently on my dhd now
Click to expand...
Click to collapse
On mine too Very nice one!
Hi Appache,
I'm pretty new in the Android platform so I do apologize for the silly question
I could not flash the image. I'm getting this:
Code:
C:\Program Files (x86)\Android\android-sdk-windows\tools>fastboot.exe flash spla
sh1 splash.img
sending 'splash1' (750 KB)... OKAY [ 0.186s]
writing 'splash1'... FAILED (remote: not allowed)
finished. total time: 0.187s
I have rebooted the phone (screenshot attached) - is that OK?
... and run the command as you adviced in the 1st post.
I have S-OFF (as you can see from the screenshot). I've rooted, unlocked the phone according you guide here: http://forum.xda-developers.com/showthread.php?t=857444
Another question would be: Can I somehow replace the carrier logo in the phone? Is that splash2 or I'm completely wrong?
Thanks for all your effort man!
snooffy said:
Hi Appache,
I'm pretty new in the Android platform so I do apologize for the silly question
I could not flash the image. I'm getting this:
Code:
C:\Program Files (x86)\Android\android-sdk-windows\tools>fastboot.exe flash spla
sh1 splash.img
sending 'splash1' (750 KB)... OKAY [ 0.186s]
writing 'splash1'... FAILED (remote: not allowed)
finished. total time: 0.187s
I have rebooted the phone (screenshot attached) - is that OK?
... and run the command as you adviced in the 1st post.
I have S-OFF (as you can see from the screenshot). I've rooted, unlocked the phone according you guide here: http://forum.xda-developers.com/showthread.php?t=857444
Another question would be: Can I somehow replace the carrier logo in the phone? Is that splash2 or I'm completely wrong?
Thanks for all your effort man!
Click to expand...
Click to collapse
You need ENG-OFF to use ADB. You can put ENG-OFF over S-OFF.
You were absolutely right mate. Done eng s-off and it went like a charm. Nice one, thanks. Oh and about the orange logo I winged about in my question - that's sorted by a different ROM
Apache14 said:
Just knocked together this splash screen for all your s-off phones to make it look a bit diff
Click to expand...
Click to collapse
Thank you, dude!
Just a little contribution...
Something sexy...
splash1.img attached
Here is mine
http://db.tt/70oe5ZU
Sent from my LeeDrOiD loaded HTC Desire HD using my thumb....
How to edit the image file? What apps to use? Photoshop ?

[INFO] Flash AOSP 2.3 GRH55

Using moto-fastboot (thanks, eval- and _unknown), we can flash any developer build unlocked images in Fastboot mode. Thanks to Team Black Hat, we were given a very early developer build with AOSP Gingerbread (mostly). That build was based on GRH55.
This build is pretty dang buggy, but its AOSP applications and such can certainly be harvested for use by devs. If you're just playing around, you'll want to move back to HKTW or stock within 10 minutes. If you want to farm the apps and libs, just mount the system image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
Basic Information
Code:
Android 2.3
Build number: olympus-eng 2.3 GRH55 eng. w30562.20110119.152615 test-keys
Date: January 19, 2011
System version: 0.0.1.MB680.ATT.en.US
Working
Data and cellular network
All applications (for the most part)
Buggy, weird, or broken
Phone application
Extremely slow!
WiFi broken
GPS
Often reboots
Some elements reflect Blur style, most are AOSP
Installation
Prerequisites
Linux [until moto fastboot is recompiled for Windows]
moto-fastboot (64-bit, 32-bit)
GRH55 boot image
GRH55 system image [[URL="http://www.filesonic.com/file/1297604021/system-grh55.zip"]Mirror]
[/URL]
Unlocked bootloader
Instructions
Commands are the same as the HKTW build flash. Thank _unknown and eval- for making it easy for everyone.
Boot the device into Fastboot mode
Power off device
Press and hold downward volume and power buttons until "Fastboot" appears
Press the upward volume button
Open a terminal window and issue the following commands
Code:
sudo ./moto-fastboot flash boot boot-grh55.smg
sudo ./moto-fastboot flash system system-grh55.smg
sudo ./moto-fastboot -w
sudo ./moto-fastboot reboot
Replace "moto-fastboot" with "moto-fastboot32" if you're on a 32-bit or VMWare system.
Reboot and enjoy!
My brain is gonna explode from all the kickass stuff being posted today!! LOL I hope this day never ends!! Thanks Kenneth!!
Im a newb running linux. I have linux in a virtual box. I downloaded moto-fastboot and the two image files. Now where do I extract these files too in linux? When I run the commands it just says command not found? I have the files on my desktop in linux, how do I direct linux to flash the files too the phone via fastboot through the terminal since it cant find the file?
JayRolla said:
Im a newb running linux. I have linux in a virtual box. I downloaded moto-fastboot and the two image files. Now where do I extract these files too in linux? When I run the commands it just says command not found? I have the files on my desktop in linux, how do I direct linux to flash the files too the phone via fastboot through the terminal since it cant find the file?
Click to expand...
Click to collapse
Make sure to check out eval-'s thread in General. Read up there.
To answer your questions...
1.) Extract the files to your home folder (for me it was my username, Kenneth)
2.) Right click the moto-fastboot32 (you need 32-bit) and click Properties... change permissions to read/write
Now give it a go.
kennethpenn said:
Make sure to check out eval-'s thread in General. Read up there.
To answer your questions...
1.) Extract the files to your home folder (for me it was my username, Kenneth)
2.) Right click the moto-fastboot32 (you need 32-bit) and click Properties... change permissions to read/write
Now give it a go.
Click to expand...
Click to collapse
So I extracted both img files for the GB build too my User name folder along with the moto-fasboot32 and changed permissions. When I run the commands exactly how they are I get ./moto-fastboot command not found. I know Im missing something easy.
JayRolla said:
So I extracted both img files for the GB build too my User name folder along with the moto-fasboot32 and changed permissions. When I run the commands exactly how they are I get ./moto-fastboot command not found. I know Im missing something easy.
Click to expand...
Click to collapse
You need to use ./moto-fastboot32 not ./moto-fastboot.
kennethpenn said:
You need to use ./moto-fastboot32 not ./moto-fastboot.
Click to expand...
Click to collapse
OMG, thank you. I knew it was something easy, LOL.
JayRolla said:
OMG, thank you. I knew it was something easy, LOL.
Click to expand...
Click to collapse
No problem. I edited the instructions for clarity.
So this is why you aren't responding to me...shame Kenneth smh
Gutterball said:
My brain is gonna explode from all the kickass stuff being posted today!! LOL I hope this day never ends!! Thanks Kenneth!!
Click to expand...
Click to collapse
It's like an early Christmas, then in a few days we get fireworks, what next, overclocking xD imagine running a rom optimized for dual core at even 1.4GHz a core, sure your battery will die faster than road kill, but hey, imagine the games that would be possible, IMAGINE THE WEBTOP THAT WOULD BE POSSIBLE!!! Excuse me while I go dance like a little girl from all this happy news lol
Korey_Nicholson said:
So this is why you aren't responding to me...shame Kenneth smh
Click to expand...
Click to collapse
Lol, he's calling in sick tomorrow
Sent from my MB860 using XDA App
so this is native? no moto influences or accents??
when can we expect cwm version or this ?
kennethpenn said:
Using moto-fastboot (thanks, eval- and _unknown), we can flash any developer build unlocked images in Fastboot mode. Thanks to Team Black Hat, we were given a very early developer build with AOSP Gingerbread (mostly). That build was based on GRH55.
This build is pretty dang buggy, but its AOSP applications and such can certainly be harvested for use by devs. If you're just playing around, you'll want to move back to HKTW or stock within 10 minutes. If you want to farm the apps and libs, just mount the system image.
​
Basic Information
Code:
Android 2.3
Build number: olympus-eng 2.3 GRH55 eng. w30562.20110119.152615 test-keys
Date: January 19, 2011
System version: 0.0.1.MB680.ATT.en.US
Working
Data and cellular network
All applications (for the most part)
Buggy, weird, or broken
Phone application
Extremely slow!
WiFi broken
GPS
Often reboots
Some elements reflect Blur style, most are AOSP
Installation
Prerequisites
Linux [until moto fastboot is recompiled for Windows]
moto-fastboot (64-bit, 32-bit)
GRH55 boot image
GRH55 system image [[URL="http://www.filesonic.com/file/1297604021/system-grh55.zip"]Mirror]
[/URL]
Unlocked bootloader
Instructions
Commands are the same as the HKTW build flash. Thank _unknown and eval- for making it easy for everyone.
Boot the device into Fastboot mode
Power off device
Press and hold downward volume and power buttons until "Fastboot" appears
Press the upward volume button
Open a terminal window and issue the following commands
Code:
sudo ./moto-fastboot flash boot boot-grh55.smg
sudo ./moto-fastboot flash system system-grh55.smg
sudo ./moto-fastboot -w
sudo ./moto-fastboot reboot
Replace "moto-fastboot" with "moto-fastboot32" if you're on a 32-bit or VMWare system.
Reboot and enjoy!
Click to expand...
Click to collapse
It says "System version: 0.0.1.*MB680*.ATT.en.US", which should be "System version: 0.0.1.*MB860*.ATT.en.US", had to point that out lol
jahizen said:
so this is native? no moto influences or accents??
Click to expand...
Click to collapse
There are a few. Simple edits can take them out. Mostly AOSP, though. This is clearly their first (or one of the first) engineering build.
has fastboot been recompiled for windows?
Dubee24 said:
has fastboot been recompiled for windows?
Click to expand...
Click to collapse
No. Someone needs to do it using Cygwin. Best info: http://groups.google.com/group/android-porting/browse_thread/thread/4990ffe551844860?pli=1&fwc=1
anyone know what is the code group CGXX.smg for this boot-grh55.smg??
I'm getting the following,
Code:
sending 'system' (327680 KB)...
(bootloader) Image is too big, use 0x10000000 bytes chunks
FAILED (remote: (00000006))
finished. total time: 0.003s
phone displays
Failed to process command download :14000000 error(0x6)
is there a solution to this?
you need to flash it on linux

[Recovery] ClockworkMod - TF701T Proxy Thread

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
THIS IS A PROXY THREAD Creator and Maintainer is pershoot
This is CWM for the ASUS Transformer Pad (TF701T – Macallan).
-You must be unlocked (use ASUS’s unlock tool to perform this)
-You must be on 10.26.1.18 bootloader (updating to ASUS’s latest 4.3 release will install this)
For complete Info and Download: VISIT HERE
***Once there, check out the Recent Entries on the right side of the page for latest updates***
-Unlock your device using the ASUS Unlock tool.
-Boot in once and execute: adb reboot bootloader
Fastboot:
To boot the recovery:
fastboot boot recovery.img
To permanently flash the recovery:
fastboot flash recovery recovery.img
Source:
https://github.com/pershoot/android_device_asus_tf701t
https://github.com/pershoot/android_kernel_asus_tf701t
https://github.com/CyanogenMod/android_bootable_recovery
Creator and Maintainer:
@pershoot
Video Tutorial
Video Tutorial Thanks @wwjoshdew
Ah just saw screenies. Nice job pershoot.
Why is the version still 6.0.4.6?
CWM 6.0.4.7
OP Updated
Feb/2 OP updated
Small question: my device is on 10.26.1.17. Updating to the latest official 4.3 will definitely wipe the CWM recovery, and probably will make some of the apps not running any more (not mentioning loosing root, etc..)
Is it possible to install the CWM on such a ROM version (10.26.1.17) ? I've just tested booting it and booting (and using it as a backup) works.
I was on 6.0.4.6 and i used flashify to update. Worked fine.
hetzbh said:
Small question: my device is on 10.26.1.17. Updating to the latest official 4.3 will definitely wipe the CWM recovery, and probably will make some of the apps not running any more (not mentioning loosing root, etc..)
Is it possible to install the CWM on such a ROM version (10.26.1.17) ? I've just tested booting it and booting (and using it as a backup) works.
Click to expand...
Click to collapse
Both cromix and cm11 will require the latest bootloader to eliminate compatibility issues it is recommended to flash to the latest asus firmware
Sent from my SGH-T889 using XDA Premium 4 mobile app
@AngryDinosaur - I made a video on how to install Custom Recovery on your Transformer Pad TF701T!
http://www.youtube.com/watch?v=3IBN1YkBp3g
wwjoshdew said:
@AngryDinosaur - I made a video on how to install Custom Recovery on your Transformer Pad TF701T!
http://www.youtube.com/watch?v=3IBN1YkBp3g
Click to expand...
Click to collapse
included in the post alongside the screenshots. Thanks a lot!!!
OP updated 2/16, installation video tutorial included. Thanks to @wwjoshdew
recovery updated with baseline build and sorted dock sd card functionality and usbdisk functionality.
@pershoot I'd love for this recovery to include touch screen drivers. That way at least aroma could use the touch screen. Any ideas how to compile with the standard drivers included?
sbdags said:
@pershoot I'd love for this recovery to include touch screen drivers. That way at least aroma could use the touch screen. Any ideas how to compile with the standard drivers included?
Click to expand...
Click to collapse
i'll look in to it...
I'm getting a weird error I've never seen before trying to flash something with fastboot. :
fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
error: cannot load 'recovery.img' : No error
Any ideas?
lortay78 said:
I'm getting a weird error I've never seen before trying to flash something with fastboot. :
fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
error: cannot load 'recovery.img' : No error
Any ideas?
Click to expand...
Click to collapse
Make sure recovery.img is in the same folder as fastboot and you are running the cmd prompt from that folder.
sbdags said:
Make sure recovery.img is in the same folder as fastboot and you are running the cmd prompt from that folder.
Click to expand...
Click to collapse
Duh, I have platform-tools in my path so I can run them from anywhere. I forgot to cd to the directory. Thanks for airing out my brain fart.
lortay78 said:
Duh, I have platform-tools in my path so I can run them from anywhere. I forgot to cd to the directory. Thanks for airing out my brain fart.
Click to expand...
Click to collapse
Very common mistake that happens to the best of us
updated.
Hi,
I spent hours trying to get this to work before discovering there are two missing steps in the OP's instructions.
There's a shell script that calls an application that restores the stock boot loader on every boot.
You have to delete it.
Steps:
1. Root.
2. Install Root Explorer.
3. Go into /etc
4. Delete install_recovery.sh
5. Go into /system
6. Delete recovery-from-boot.p
You have to delete the files. You can't just rename them or change the extension because the system actually searches the filesystem for a file whose contents matches an MD5 hash and will find it if you rename it.
After you do this, THEN follow OP's instructions.

[Boot Logo][Flashable] Android 6.0 Marshmallow

Hii guys .. here am created boot logo of android marshmallow for Moto X Style ​
Instructions:
1.Download the flashable zip file from the link
2.copy that into sdcard/internal storage
3.reboot to recovery
4.flash the zip file
5.Reboot your device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Downloads: http://d-h.st/bjXA
Sweet! Any chance for one with a Black background?
Shouldn't this be about 1440px high?
When I tried flashing this I had errors and it failed in twrp. Redownload and same issue.
Sent from my XT1575 using Tapatalk
BlackHoleSlam said:
When I tried flashing this I had errors and it failed in twrp. Redownload and same issue.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I am having the same problem
It no work...
For those who can't flash the zip, you could try extracting the logo.bin and flash via fastboot:
Code:
fastboot flash logo /path/to/logo.bin
Disclaimer: The fastboot command works, but I haven't tested it with the logo.bin file provided from the zip in this thread.
Stryder5 said:
For those who can't flash the zip, you could try extracting the logo.bin and flash via fastboot:
Code:
fastboot flash logo /path/to/logo.bin
Disclaimer: The fastboot command works, but I haven't tested it with the logo.bin file provided from the zip in this thread.
Click to expand...
Click to collapse
I will attempt to flash later in the evening to test.
Update: flashed successfully with fast boot. Looks great
flash logo.bin via cmd
mfastboot flash logo logo.bin
[email protected] said:
flash logo.bin via cmd
mfastboot flash logo logo.bin
Click to expand...
Click to collapse
Did you test the file you posted?
You shared a flashable zip file so is it working?
@[email protected] ... It's a sorry thing to see when a member of your apparent experience on XDA resorts to plagiarism to open a new thread. The reason your flashable zip doesn't work is because you have copied the "Meta-Inf" file word for word and comma for comma from the original by @caitsith2 who pioneered flashable zips for boot logos. Not only have you failed to give him/her due credit for the work but you have also been ignorant enough to copy/leave in the three "dummy commented out" lines from his original. If you had an ounce of original thought in your being you would have seen that there was no way this "updater-script" was going to work.
Unlike you I have taken note of the requests by posters to this thread and have incorporated your "image" into a new flashable zip which works. As usual flash through custom recovery.
Oh looks awesome...thanks.
metpolds said:
@[email protected] ... It's a sorry thing to see when a member of your apparent experience on XDA resorts to plagiarism to open a new thread. The reason your flashable zip doesn't work is because you have copied the "Meta-Inf" file word for word and comma for comma from the original by @caitsith2 who pioneered flashable zips for boot logos. Not only have you failed to give him/her due credit for the work but you have also been ignorant enough to copy/leave in the three "dummy commented out" lines from his original. If you had an ounce of original thought in your being you would have seen that there was no way this "updater-script" was going to work.
Unlike you I have taken note of the requests by posters to this thread and have incorporated your "image" into a new flashable zip which works. As usual flash through custom recovery.
Click to expand...
Click to collapse
No. i made this bootlogo just using bootlogo maker tool. And ik flashable zip is not working and I am busy with mokee anyways thanks for fixing.
I did the procedure but it was upside down
eduluzamba said:
I did the procedure but it was upside down
Click to expand...
Click to collapse
@eduluzamba ... I don't wish to bang you on the head about this but I must point out that 268 people have downloaded this logo and you are the first to state that this particular problem exists.
Might I suggest that you delete the logo and re-instate the original, I presume you backed it up before installing this one, then re-download this logo just in case it was corrupted in the download and flash it again through recovery.
You might also look back at the post by @Stryder5 on page 1, he suggests the alternative method of flashing using ADB Fastboot.
I hate to state the obvious but presumably your device is the MXPE.
Sorry is that after I saw that the logo is for the bike x style and the bike x force

Convert TWRP .img to .tar (for ODIN)[Easy]

Sometimes the latest version of TWRP is in ".img", so some people use an older version instead, which is in .tar, so they can flash it with ODIN. The thing is that the ".tar" version is just the ".img" compressed XD, so I'm going to show you how to "convert" .img to .tar.
// TUTORIAL
1 - Download and install 7-zip
2 - Download the latest TWRP .img
3 - Open a file explorer, rename the downloaded file to: recovery.img
4 - Right click on the file > 7-zip > Add to archive...
5 - In this screen you can change the file name and, most important, in "Archive format" choose "tar"
6 - Open ODIN and flash the new file as always
Note: maybe other .img files (I mean other than the TWRP recovery) works too.
// SCREENSHOT
This is how the final file should look:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
// Other stuff
[MOD] Centered clock in status bar [6.0.1][.ZIP][SM-N910C]
You can try this too to convert the .img to a "tar.md5": http://forum.xda-developers.com/showthread.php?t=2446269
is this method for MM build? (N910C)
Edited.
genova88 said:
is this method for MM build? (N910C)
Click to expand...
Click to collapse
It doesn't matter the version I guess.
The TWRP that I show in the screenshot is the one I'm using right now on MM (SM-N910C).
Thanks
Zawnaiminn said:
Thanks
Click to expand...
Click to collapse
Is there a way to do the opposite direction, convert odin flashable tar to twrp flashable zip? Like to flash Samsung stock rom with twrp..
joe535 said:
Is there a way to do the opposite direction, convert odin flashable tar to twrp flashable zip? Like to flash Samsung stock rom with twrp..
Click to expand...
Click to collapse
I have the same query. But seems that none exists!
Sorry for the resurrection but I wasted time trying to use this and wanted to say something.
I tried to use 7zip to create a .tar file for Odin and it didn't work for me personally. SeaFargo also says that 7zip .tars are not compatible with Odin.
SeaFargo's response is over at "[Script][Tool] how to create a tar.md5 file from img For Odin" by mkh.mourad. First page. New user here so I cannot post external links.
what about covert odin flashable files to twrp flashable files ?
joe535 said:
Is there a way to do the opposite direction, convert odin flashable tar to twrp flashable zip? Like to flash Samsung stock rom with twrp..
Click to expand...
Click to collapse
1st Extract Images from twrp
2nd Add Image files to this zip:
https://mega.nz/file/R4AggZjK#mVwpFp9lFtctNA51NubD1hr-Wm-zMREdJVLI3LXY4Yc
A S Ovin said:
I have the same query. But seems that none exists!
Click to expand...
Click to collapse
No need flashable zip, just extract by 7zip and flash images in twrp.
jjgvv said:
No need flashable zip, just extract by 7zip and flash images in twrp.
Click to expand...
Click to collapse
Can someone confirm this? It almost sounds too easy.
prkfsz said:
Can someone confirm this? It almost sounds too easy.
Click to expand...
Click to collapse
Sorry I mean:
1.Extract tar by 7zip or winrar
2. fastboot flash recovery C://recovery.img for recovery image and fastboot flash system C://system.img for system image which C:// recovery.img and C:// system.img should be replaced by the directory of the image
3.reboot and enjoy!
Remember delete meta inf folder
joe535 said:
Is there a way to do the opposite direction, convert odin flashable tar to twrp flashable zip? Like to flash Samsung stock rom with twrp..
Click to expand...
Click to collapse
just decompress it.

Categories

Resources