Database Info

Need 3.1 boot.img

I need someone with the xoom 3G with 3.1 to run this command in an adb shell and post it. I flashed an older boot.img before making a backup
cat /dev/block/platform/sdhci-tegra.3/by-name/boot > /sdcard/boot.img
Thanks in advance.

I think it's in the update.zip package, as bootloader.bin

Bauxite said:
I think it's in the update.zip package, as bootloader.bin
Click to expand...
Click to collapse
NO, that's the bootloader. The boot.img is the kernel.

Bauxite said:
I think it's in the update.zip package, as bootloader.bin
Click to expand...
Click to collapse
I saw that in there but I decided to flash back to 3.0.1 without wiping my data (the apps really don't like that) and I'm reupdating to 3.1 now. I'll post the boot file when I'm back up and running in case someone else needs it.
Well I forgot I lost root in the manual update so I can't extract it yet. At least you can revert to 3.0.1 if you make the mistake I did and reflash 3.1.

One problem
I get Permission Denied, since I lost root when I applied the 3.1 update.
I was curious, about to try flashing koush's rootboot.img and getting root back; however I wanted a backup of the 3.1 boot.img as well, and only found the boot.img.p in the update and I'm not quite sure if that will do me any good.
At any rate, hope someone can run that command for you (and me)

tekuru said:
I get Permission Denied, since I lost root when I applied the 3.1 update.
I was curious, about to try flashing koush's rootboot.img and getting root back; however I wanted a backup of the 3.1 boot.img as well, and only found the boot.img.p in the update and I'm not quite sure if that will do me any good.
At any rate, hope someone can run that command for you (and me)
Click to expand...
Click to collapse
The boot.img.p is a binary patch that's applied to the original boot. There's an applypatch tool in the Android sources that can apply binary patches, so if you have the stock boot from the previous version and can apply the patch, you have a 3.1 boot.img without doing anything.

tekuru said:
I get Permission Denied, since I lost root when I applied the 3.1 update.
I was curious, about to try flashing koush's rootboot.img and getting root back; however I wanted a backup of the 3.1 boot.img as well, and only found the boot.img.p in the update and I'm not quite sure if that will do me any good.
At any rate, hope someone can run that command for you (and me)
Click to expand...
Click to collapse
Don't flash rootboot, that is what I did that screwed me up. We'll have to wait for another root img to flash that is updated for 3.1.

Excellent, thanks. Going to be on my way doing that, will return if successful.. assuming applypatch can be run in windows, if not I will have to dust off an older ubuntu notebook and get started.

Aaannd thank you, too, glad I came here before taking the plunge. I will do my best to get you the patched boot.img

tekuru said:
Excellent, thanks. Going to be on my way doing that, will return if successful.. assuming applypatch can be run in windows, if not I will have to dust off an older ubuntu notebook and get started.
Click to expand...
Click to collapse
As the android sources only build on 'nix, it's a 'nix executable.

We have both the 3g and the wifi stock images in the irc channel

bwcorvus said:
We have both the 3g and the wifi stock images in the irc channel
Click to expand...
Click to collapse
Mind putting them on multiupload or such for those of us not in the channel?

boot image
*EDIT: Thought I should point out that this is from the Verizon 3G Xoom*
Okay so here is the boot.img that is the result of the patch.
http://www.multiupload.com/LFUP6NY7A7
Since applypatch needs the SHA1 values of the source/target files, I took them from the updater script:
Code:
apply_patch("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/boot:8388608:17c91cba04ae40ebdc28cd7a5cbd9eb5e9bb33fd:8388608:e95341ff1b5f5cb2e246f028cc127083f14e0a40",
"-", e95341ff1b5f5cb2e246f028cc127083f14e0a40, 8388608,
17c91cba04ae40ebdc28cd7a5cbd9eb5e9bb33fd, package_extract_file("patch/boot.img.p"));
Then I wound up with this command, which I ended up running on my evo with the applypatch from the cyanogenmod update package, since my linux notebook wasn't happy being unused for so long.
Code:
# applypatch boot.img boot31.img e95341ff1b5f5cb2e246f028cc127083f14e0a40 8388608 17C91CBA04AE40EBDC28CD7A5CBD9EB5E9BB33FD:boot.img.p
And that resulted in the file I have uploaded, boot31.img. it matches the CRC from the install script, so we should be good to go.

tekuru said:
Mind putting them on multiupload or such for those of us not in the channel?
Click to expand...
Click to collapse
http://www.mediafire.com/?fzet7g9u770v286
Wifi stock 3.1 boot.img

tekuru said:
Then I wound up with this command, which I ended up running on my evo with the applypatch from the cyanogenmod update package, since my linux notebook wasn't happy being unused for so long.
Click to expand...
Click to collapse
Yeah, I'm a doofus, the android sources build a native binary, not a host binary. (You don't even need CM, because it's part of the standard Android tool suite).
But I'm glad you got that working.

ydaraishy said:
Yeah, I'm a doofus, the android sources build a native binary, not a host binary. (You don't even need CM, because it's part of the standard Android tool suite).
But I'm glad you got that working.
Click to expand...
Click to collapse
Guess it kind of worked out then -- I never even got to try on my computer, just thought about using the CM version since thats what was on the handset and I didn't know if I would have issues with an official build or whatnot.. and it just sort of worked. I can luck out occasionally it seems.. now back to OP's original thought, how to get root back

tekuru said:
Guess it kind of worked out then -- I never even got to try on my computer, just thought about using the CM version since thats what was on the handset and I didn't know if I would have issues with an official build or whatnot.. and it just sort of worked. I can luck out occasionally it seems.. now back to OP's original thought, how to get root back
Click to expand...
Click to collapse
Easy. Split the new boot image into kernel and ramdisk, and change ro.secure back, then wrap it all back together.
(Given that your 'nix machine is out of commission, I'm trying to do this for you now.)

Here, I hope this works for rootz, usual disclaimers apply. I can't test it myself because I don't have a device, though, sorry
(But you should have a stock image to work with, though, and if all else fails, flash HRI66 and reapply the update.)

ydaraishy said:
Here, I hope this works for rootz, usual disclaimers apply. I can't test it myself because I don't have a device, though, sorry
(But you should have a stock image to work with, though, and if all else fails, flash HRI66 and reapply the update.)
Click to expand...
Click to collapse
Just flashed it and booting now will let you know if this works
Thanks
Edit: That works. Once I rebooted I just was able to adb remount and push su to /system/bin and chmod it. Now have root on 3.1 Xoom.
Great job

Worked for me as well, thanks

[REQ] Need MZ601 Euro 3G users. READ NOW!

Ok, so after the announcement of the 3.1 update at IO yesterday, were all eagle awaiting the 3.1 update.
For those of us in europe, with 3G xooms we need a different update so don't try flash anything that is currently available.
Second and most important. There are NO Stock boot images for 3G europe, we need someone who has stock recovery to dump it and get in touch with me. WE CANNOT UPDATE IF WE INSTALLED CLOCKWORK MOD.
Once we have a stock recovery image I can post all the stock images for us to flash back to stock for the update.
Use these commands to dump the recovery image (you need to be rooted and/or have a custom kernel like Tiamat (or the one in my thread) installed so you can remount, you may also need to install busybox (use Busybo installer by Stericson from the Android Market, don't forget to open and run it after you install it):
Code:
adb remount
adb shell dd if="/dev/block/platform/sdhci-tegra.3/by-name/recovery" of="/sdcard/recovery.img"
adb pull /sdcard/recovery.img
That's it, the image will be on your sdcard and copied to your computer, please upload or PM me a link.
Thanks
Macbots drool as I XOOM through the Galaxy to my hearts Desire.

I had to add "platform" to the path:
adb shell dd if="/dev/block/platform/sdhci-tegra.3/by-name/recovery" of="/sdcard/recovery.img"
Click to expand...
Click to collapse
Hope I did it all right after rooting the device (by your manual - thanks in advance for this!).

Riffer said:
I had to add "platform" to the path:
Click to expand...
Click to collapse
You're right, sorry I typed it from memory, will update it now!

That's... odd...
The kernels from the boot image that you circulated a while back, plus the kernel from this recovery image, are different.
They should be the same.
(The recovery ramdisk ro.build.version.release says 3.0.1, maybe the boot image is from 3.0? Has the MZ601 got 3.0.1 yet?)

ydaraishy said:
That's... odd...
The kernels from the boot image that you circulated a while back, plus the kernel from this recovery image, are different.
They should be the same.
Click to expand...
Click to collapse
That's normal ... a recovery image would probably have a light weight stripped down kernel, since it doesn't need to boot and run the full OS, just hte recovery OS.
It's also possible that the recovery might be the same as the US one, and the US one runs a differnet kernel to the euro one, so it's not necessarily a problem that it's different.
Oh, and any chance of a link to the recovery image you've dumped? Please.

alias_neo said:
That's normal ... a recovery image would probably have a light weight stripped down kernel, since it doesn't need to boot and run the full OS, just hte recovery OS.
Oh, and any chance of a link to the recovery image you've dumped? Please.
Click to expand...
Click to collapse
No, they should have the same kernel. It's designed that way. (Remember, when you get an OTA, you get a recovery-from-boot.p patch that runs on startup to repatch your recovery image back to stock -- it's deliberately based on the boot image, so the patch is as small as possible)
I didn't dump the recovery image -- look a few posts up (I _still_ don't have a device yet )
ed. And I don't think a US MZ601 is out yet...The above dump looks like it's from a German Xoom, based on ro.product.locale.region.

ydaraishy said:
Has the MZ601 got 3.0.1 yet?)
Click to expand...
Click to collapse
Yes. Mine does have it. Got it without any branding from www.sparhandy.de yesterday.
Should I mention I am german?
alias_neo said:
Oh, and any chance of a link to the recovery image you've dumped? Please.
Click to expand...
Click to collapse
Mine is attached above? Or do you say that to ydaraishy?

Riffer said:
Mine is attached above? Or do you say that to ydaraishy?
Click to expand...
Click to collapse
Sorry, didn't see your edit.
EDIT: @ydaraishy: Interesting, I wasn't aware of this as I have never ran an OTA before in my life, and my XOOM was at 3.0.1 when it was released.
So, I wonder what the deal is here, will the euro OTA come with a full kernel? Maybe the method I used to split the kernel and ramdisk I posted (in order to root it) caused some change? How are you comparing them?

alias_neo said:
Sorry, didn't see your edit.
EDIT: @ydaraishy: Interesting, I wasn't aware of this as I have never ran an OTA before in my life, and my XOOM was at 3.0.1 when it was released.
So, I wonder what the deal is here, will the euro OTA come with a full kernel? Maybe the method I used to split the kernel and ramdisk I posted (in order to root it) caused some change? How are you comparing them?
Click to expand...
Click to collapse
No, they'll binary patch it like usual.
I split the kernel and ramdisk of the recovery image, then the boot image that you had posted a while back for root, then md5'd both kernel images.

Got my T-Mobile Xoom 3G (3.0.1; MZ601; H.6.1-38-5) today and dumped the recovery.img just after flashing rooted boot.img.
Hope this helps.

Thanks guys, hopefully i can use these to sort something out for us when we get 3.1 update finally.

I also have a T-Mobile Xoom and I've used Clockworkmod Recovery to make a dump via dd of system and boot.
All togheter we should now have a complete set of the MZ601 H.6.1-38-5 Firmware.
I put it togheter into one rar-file and uploaded it. But I am not allowed to post links here because of not enough posts.
I will send it to you via PM, hopefully someone of you can post it.
Hope this helps.

MediumO said:
I also have a T-Mobile Xoom and I've used Clockworkmod Recovery to make a dump via dd of system and boot.
All togheter we should now have a complete set of the MZ601 H.6.1-38-5 Firmware.
I put it togheter into one rar-file and uploaded it. But I am not allowed to post links here because of not enough posts.
I will send it to you via PM, hopefully someone of you can post it.
Hope this helps.
Click to expand...
Click to collapse
Your zip you PMd me says boot, recovery and system, surely all 3 can't be stock if you installed clockwork mod to dump it, so which two are stock?

Ok, this one is exactly identical to mine - says Winmerge.

Riffer said:
Ok, this one is exactly identical to mine - says Winmerge.
Click to expand...
Click to collapse
Which one?

I used the recovery of Riffer. System and boot are stock from my device.
I just put them togheter in one archive to get a full set.

MediumO said:
I used the recovery of Riffer. System and boot are stock from my device.
I just put them togheter in one archive to get a full set.
Click to expand...
Click to collapse
That's great. Now we just gotta wait for 3.1 in Europe!

I have been fallowing this forum for a long time and also I got my Xoom from CPW couple of weeks ago and I have to say that I'm really waiting for this update so bad, just because many people has been reviewing it and they say is really a change in performance, sometimes I find that my Xoom is quite heavy, more when I'm trying to surf the web, and sometimes when I come to the forum from it, and I will like to be an active member of this forum as well, I will try to help with anything I can and I just rooted my Xoom with neo guide.
sorry if my english is not so good.
I'm in London at the moment
and Galaxy SII owner as well

Hopefully 3.1 will show up in Europe soon. I read somewhere that T-Mobile Germany had also planned to release the update on 5/11. But no evidence for that until now.
Otherwise we have to port the CDMA Rom ;-)

MediumO said:
Hopefully 3.1 will show up in Europe soon. I read somewhere that T-Mobile Germany had also planned to release the update on 5/11. But no evidence for that until now.
Otherwise we have to port the CDMA Rom ;-)
Click to expand...
Click to collapse
There will be non of that frankenfrak here sonny. We get our own 3.1 or we all go down swinging. :-D
Macbots drool as I XOOM through the Galaxy to my hearts Desire.

[fixed] WiFi unable to connect after S-OFF on Sensation

Hi!
I just unlocked (S-OFF) and rooted my Sensation according to the tutorial pinned in the development section. Unfortunately, now I am unable to connect to any WiFi-networks. My phone is an unlocked, SIM-free european HTC Sensation.
Restoring the phone backup I created before rooting (with ClockworkMod Recovery) to the unrooted stock ROM didn't work, still no wireles lan.
Does anybody know how to resolve this issue? Any pointers would be greatly appreciated.
Edit: If you flashed an unsafe boot image, page two has the solution.

Maybe try to ask in the IRC channel from #revolutionary on irc.freenode.net (but please recheck this on their website ), joined there today because of a minor problem and they seem very helpful.

PartyMango said:
Hi!
I just unlocked (S-OFF) and rooted my Sensation according to the tutorial pinned in the development section. Unfortunately, now I am unable to connect to any WiFi-networks. My phone is an unlocked, SIM-free european HTC Sensation.
Restoring the phone backup I created before rooting (with ClockworkMod Recovery) to the unrooted stock ROM didn't work, still no wireles lan.
Does anybody know how to resolve this issue? Any pointers would be greatly appreciated.
Click to expand...
Click to collapse
u installed boot.img from cwm? I`m figuring out how to restore the old one..

I did some further investigation, and possibly was to quick on the draw:
While trying to find a solution, I noticed that I was able to connect to some other networks without problems. So I tried changing channels & power-cycling my WiFi access point. Et voilà: Magically, my wireless lan-problems did disappear.
I guess the problem was with the router all along, no fault of unrevoked & AlphaRev which I both want to praise for their excellent work in unlocking this phone.
Next time, I'll try turning it off and on again, first

Glad you fixed it Mr Mango, can you change the Title of your Thread to Fixed then

nicoaraalex said:
u installed boot.img from cwm? I`m figuring out how to restore the old one..
Click to expand...
Click to collapse
I used the boot.img for CWM provided with the tutorial here (Step 2): http://forum.xda-developers.com/showthread.php?t=1192300
ikhzter said:
Glad you fixed it Mr Mango, can you change the Title of your Thread to Fixed then
Click to expand...
Click to collapse
Done.

PartyMango said:
I used the boot.img for CWM provided with the tutorial here (Step 2): http://forum.xda-developers.com/showthread.php?t=1192300
Done.
Click to expand...
Click to collapse
Thanks Mr Flirty Magno

well not working for me.. on Wi-Fi, it says Error... doesn't turn on or off...

nicoaraalex said:
well not working for me.. on Wi-Fi, it says Error... doesn't turn on or off...
Click to expand...
Click to collapse
Exactly the same problem here, nothing to connect to because the wifi won't initiate. Really need help with this too.

dladz said:
Exactly the same problem here, nothing to connect to because the wifi won't initiate. Really need help with this too.
Click to expand...
Click to collapse
Same here! Sensation with Vodaphone branded ROM, no wifi anymore. Says "Error" in wireless menu.
I'm not sure if this was caused by S-OFF itself or by the installation of the "Unsafe" boot image to get root in adb by default.
So far I haven't found a way to make the wifi work again!

I have the exact same "Error" problem with my T-mobile branded sensation
joel.bourquard said:
Same here! Sensation with Vodaphone branded ROM, no wifi anymore. Says "Error" in wireless menu.
I'm not sure if this was caused by S-OFF itself or by the installation of the "Unsafe" boot image to get root in adb by default.
So far I haven't found a way to make the wifi work again!
Click to expand...
Click to collapse

Ok, I think I really found the cause: it happens when I install the "Unsecured Boot.img - Europe" from there:
http://forum.xda-developers.com/showthread.php?t=1122053
Edit: Same problem with the Unsecured boot img (Asia) !
But here's good news: just install a RUU and the Wi-Fi problem will be gone!

joel.bourquard said:
Same here! Sensation with Vodaphone branded ROM, no wifi anymore. Says "Error" in wireless menu.
I'm not sure if this was caused by S-OFF itself or by the installation of the "Unsafe" boot image to get root in adb by default.
So far I haven't found a way to make the wifi work again!
Click to expand...
Click to collapse
UNSAFE boot image was the cause. so i scrapped it
AS Joel said, just reinstall stock rom. and its gone.
for more information visit the guide to S-off, bottom of post 1 will tell you how to debrand or reinstall

Yes, everything works fine now with the un-branded ROM.
So there's no way to get direct root adb access without breaking wi-fi functionality at the moment?

joel.bourquard said:
Yes, everything works fine now with the un-branded ROM.
So there's no way to get direct root adb access without breaking wi-fi functionality at the moment?
Click to expand...
Click to collapse
When users had the wifi break, the rooting file in step 3 was outdated. it was for froyo and eclair only. whcih is why users flashed unsecured boot.img causing the WIFI loss.
NOW!
Read the Guide. If you follow step 3. you WILL get root and YOU WILL NOT LOSE WIFI.
initially Step 3. had a su file called su-ef2.3.6.1.zip which didnt work causing people to use the unsecured boot from binary
but the new one is called su-efgh2.3.6.3zip which is working
the difference, the new supports Gingerbread and Honeycomb
i followed step 3 and hundreds of others have, we are all rooted on stock or custom roms without wifi problems!

ikhzter said:
When users had the wifi break, the rooting file in step 3 was outdated. it was for froyo and eclair only. whcih is why users flashed unsecured boot.img causing the WIFI loss.
NOW!
Read the Guide. If you follow step 3. you WILL get root and YOU WILL NOT LOSE WIFI.
initially Step 3. had a su file called su-ef2.3.6.1.zip which didnt work causing people to use the unsecured boot from binary
but the new one is called su-efgh2.3.6.3zip which is working
the difference, the new supports Gingerbread and Honeycomb
i followed step 3 and hundreds of others have, we are all rooted on stock or custom roms without wifi problems!
Click to expand...
Click to collapse
Sorry, maybe I wasn't being totally clear.
Yes, I flashed ClockworkMod and then "su-2.3.6.3-efgh-signed.zip" and it works great. I'm rooted, no problem with that.
The only thing I'm missing here, is that when I connect with "adb shell" I get the "$" prompt (not root). So I need to type "su" first. Then I'm root.
With the "unsecured boot" I get connected as root right away with "adb shell", but then the Wi-Fi doesn't work.
Therefore I was wondering if some way exists, to enable direct root for "adb shell" without breaking the Wi-Fi.

joel.bourquard said:
Ok, I think I really found the cause: it happens when I install the "Unsecured Boot.img - Europe" from there:
http://forum.xda-developers.com/showthread.php?t=1122053
Edit: Same problem with the Unsecured boot img (Asia) !
But here's good news: just install a RUU and the Wi-Fi problem will be gone!
Click to expand...
Click to collapse
Any recommendation on which RUU to flash? I have a Tmo Sensation. I don't wanna flash anything that will brick my phone now that I finally got S-OFF on this bad boy

joel.bourquard said:
Sorry, maybe I wasn't being totally clear.
Yes, I flashed ClockworkMod and then "su-2.3.6.3-efgh-signed.zip" and it works great. I'm rooted, no problem with that.
The only thing I'm missing here, is that when I connect with "adb shell" I get the "$" prompt (not root). So I need to type "su" first. Then I'm root.
With the "unsecured boot" I get connected as root right away with "adb shell", but then the Wi-Fi doesn't work.
Therefore I was wondering if some way exists, to enable direct root for "adb shell" without breaking the Wi-Fi.
Click to expand...
Click to collapse
I dont think there is a way yet, im not sure if it works directly or not, as i am currently using a custom rom

Beast84 said:
Any recommendation on which RUU to flash? I have a Tmo Sensation. I don't wanna flash anything that will brick my phone now that I finally got S-OFF on this bad boy
Click to expand...
Click to collapse
Check your Build number under the software information in Settings.
it should start with 1.27.531.2 or 1.29.531.2
You can download the exact same one below according to your build number
RUU_Pyramid_TMOUS_1.27.531.2_Radio_10.42.9007.00P_ 10.11.9007.15_M_release_192098_signed
http://www.filefactory.com/file/cb5d...098_signed.exe
RUU_Pyramid_TMOUS_1.29.531.2_Radio_10.42.9007.00P_ 10.11.9007.15_M_release_193714_signed
http://www.filefactory.com/file/cb7a...714_signed.exe

Ahhh, does this mean we naughty WIFI guys can try to re-root now? I was one of the ones that had WIFI go crap out after the root, and I flashed back to a stock ROM for TMOUS. Does this mean I can try to root again and plan on it working this time?
Matt

ICS Modem Files - WORKING UCAL4 Modem

EDIT
See post #5 for CWM Zip
Be sure to thank LeeC for the zip and Carrett for giving us the files.
For those that have ICS installed, would you be able to pull the modem files out. Figured I'd test some theories out with getting this on a rogers version. Shot in the dark, but figured I would make the leap.
For those of you that are wondering how to; You will need to do this:
adb shell dd if=/dev/block/mmcblk0p13 of=/sdcard/amss.bin
adb shell dd if=/dev/block/mmcblk0p17 of=/sdcard/mdm.bin
adb pull /sdcard/amss.bin
adb pull /sdcard/mdm.bin
Then just throw that into a zip for me.
Appreciate any help you can provide.

Here are mine. Hopefully devs find this useful! What's weird is that mdm.bin and amss.bin end up being EXACTLY the same size (down to the byte). I double-checked and did it twice to be sure.
Let me know if I can adb anything else for y'all.
http://db.tt/JLhX67BT

putting this into a zip and flashing now

Looking forward to your result.

Hi y2whisper, I made a flashable zip with some library files together.
http://dl.dropbox.com/u/4333782/ICSradio.zip
Just for test since I have not tested if it's work or not. I need my phone working now.

LeeC said:
Hi y2whisper, I made a flashable zip with some library files together.
http://dl.dropbox.com/u/4333782/ICSradio.zip
Just for test since I have not tested if it's work or not. I need my phone working now.
Click to expand...
Click to collapse
YAYYY it works

Killadude said:
YAYYY it works
Click to expand...
Click to collapse
On what ROM you flashed? y2whisper mentioned in another post that he got boot loop so I guess he missed those library files.

Yeah I figured I would have had the lib files already in there so I skipped it. I will flash and confirm as well.
EDIT
Not only does this work but the baseband version shows up as well. Will let the people with the Odin tar know.

LeeC said:
Hi y2whisper, I made a flashable zip with some library files together.
http://dl.dropbox.com/u/4333782/ICSradio.zip
Just for test since I have not tested if it's work or not. I need my phone working now.
Click to expand...
Click to collapse
AWESOME! Thanks for this - works great on my I727R.

Great, thanks for the confirmation. One step a time guess we are getting our perfect rogers ICS soon

LeeC said:
Great, thanks for the confirmation. One step a time guess we are getting our perfect rogers ICS soon
Click to expand...
Click to collapse
Perfect would be ASOP but this is pretty damn near good enough!

Thanks LeeC, worked great on my phone flashed with the nandroid ICS.
Edit: Only problem with this radio right now for me is that I can't get a solid LTE signal. I've always had a strong solid LTE signal in the same location but now it keeps fluctuating. Anyone else has this problem?

yvrRome said:
Thanks LeeC, worked great on my phone flashed with the nandroid ICS.
Edit: Only problem with this radio right now for me is that I can't get a solid LTE signal. I've always had a strong solid LTE signal in the same location but now it keeps fluctuating. Anyone else has this problem?
Click to expand...
Click to collapse
Same issue

try *#2263# and setting LTE prefrences to all

Killadude said:
try *#2263# and setting LTE prefrences to all
Click to expand...
Click to collapse
Yeah, I've tried that already but I just end up with no network. So you don't have issues after flashing this radio?

Havent noticed any issues with the radio....
But if i try any of the leaked flashable zips (NON rogers/nandroid one) it still lags like it used to when i had the KJ7 radio =S

I installed the nandroid deodexed backup - up and running pretty sweet!
For this - do I simply put the zip file on root of my sdcard and install from cwm?

dogblood said:
For this - do I simply put the zip file on root of my sdcard and install from cwm?
Click to expand...
Click to collapse
That is correct.

LeeC said:
Hi y2whisper, I made a flashable zip with some library files together.
http://dl.dropbox.com/u/4333782/ICSradio.zip
Just for test since I have not tested if it's work or not. I need my phone working now.
Click to expand...
Click to collapse
That updater-script won't install the RIL properly. It's looking for "system" in the zip, but its "lib". If you change it to this I think it should:
Code:
package_extract_dir("lib", "/system/lib");
unmount("/system");

Thanks romracer. I updated and the libs are now updated properly. Unfortunately I was hoping this would stabilize LTE for me but it didn't. Although it has improved.

no signal in bhundven's cm7

i installed the fourth release of bhundven's cyanogenmod and now as stated rom is stable and works pretty fast only that i am not getting any signal i messed with some options in mobile networks like international roaming,national roaming,network selection type etc.. but nothing seems to be working,then i installed both kd1 and kj2 modems of sidekick which they say has very good reception even then no luck please help me fix it

Your flashing an alpha build. You have to expect things like that. For now just flash back to something else. Or better yet fix it yourself than let Bryan know about it.

in his post he mentioned that modem(ril) is working fine and can access gsm,3g,4g so i was compromised for bluetooth and gps to just give this rom a try.i dint know this is gonna happen anyway i will wait for his final update till then will use beautifulsgs4g.
thanx for the reply buddy

You flashed modem files that haven't been padded.
See my reply here:
http://forum.xda-developers.com/showthread.php?p=24889243#post24889243
You're going to need to reinstall the ROM. Don't try to flash another modem this time, the one that bhundven included with the ROM was specially packaged for CM7

FBis251 said:
You flashed modem files that haven't been padded.
See my reply here:
http://forum.xda-developers.com/showthread.php?p=24889243#post24889243
You're going to need to reinstall the ROM. Don't try to flash another modem this time, the one that bhundven included with the ROM was specially packaged for CM7
Click to expand...
Click to collapse
is there a padded modem that I could flash because the one built in is not working for me?

ChadBFlores said:
is there a padded modem that I could flash because the one built in is not working for me?
Click to expand...
Click to collapse
While your phone is booted to android:
Code:
adb shell ls -l /radio/
there should be a file in there named modem.bin that is about 15M.
If that is not the case, heimdall the latest boot.img, then reinstall the update.zip from the freshly rebooted recovery.

thanks for the reply and absolutely sorry for this post
now the signal is working fine i should have checked it twice before posting
sorry again