Related
So in my attempts to undo unbrick my bionic i was able to get back on the path and got into a rooted 901 version YEAH.
Problem is my webtop version is WT 1.3.0-105_DBN-1 which is not the current version. Does anyone have a way to get an updated grfs version onto the phone or a process that works coming from 901?
The problem as I see it, is that you aren't really on 5.9.901 because you couldnt have updated with the leaked update.zip without having all of the signed components from 5.5.893 including the webtop partition. You must be using a ROM that updated only your system and nothing else.
The solution is to use the full 5.5.893 xml.zip released recently and flash it with RSD Lite and it will put you back on the path with all the stock images.
If you wanted to only flash the grfs.img from that file then you need to use the moto-fastboot.exe instead of the fastboot.exe because it is modified to handle larger than 256MB images.
It is difficult to tell where you really are with all of your firmware components and whether just flashing the webtop will do you any good. That is why i recommend the full xml.zip and RSD Lite.
This is the method that a technician would use to fix a returned device to stock and is what the file is designed to do. Its like an SBF file but uses the fastboot interface instead of the old flash interface.
We have all the tools we need to recover virtually all problem flashes at this point, and its up to everyone who is modding these devices to understand the options before you flash any ROMs so you dont find yourself returning a device that you destroyed to VZW for warranty replacement, a practice all to common unfortunately.
according to this
http://mobilesyrup.com/2012/08/29/b...shes-galaxy-tab-8-9-ics-upgrade-to-september/
it says"south of us in the States users are reporting that the upgrade has hit their Tab, brining a new version of TouchWiz."
so who got the update??
damn it .... sorry ppl ..... wrong info
it is talking the wifi not the lte .....
http://www.androidpolice.com/2012/0...-wi-fi-ics-update-now-rolling-out-in-the-u-s/
my bad ....
lets keep waiting..........
I don't even know why I got the LTE version, I thought that maybe ATT can be trusted to provide me with a data plan while on vacation, but they're just a bunch of thieves I've never found a plan I didn't feel cheated with.
Should've got the wifi.
http://story537.tistory.com/category/갤럭시 시리즈 펌웨어/갤럭시탭 8.9 LTE
check out this site
i am not sure this is the rom or not
maybe it is ... maybe not ... cuz its in korean... and i dont understand it
It's definitely firmware, but who has the balls to odin it?
http://story537.tistory.com/93
It's not letting me donload the complete file. I can get the boot and recovery img, but the system.img doesn't seem to be complete in the archive.
apparently on the sammobile firmware page, there's an ota update for the telus and bell variations dated august 2012. Might wanna check into them
KitF said:
It's not letting me donload the complete file. I can get the boot and recovery img, but the system.img doesn't seem to be complete in the archive.
Click to expand...
Click to collapse
this is what i got after i use 7zip
amss.bin
boot img
mdm.bin
recovery img
system.img.ext4
and i have no idea how to flash it
madsatan said:
this is what i got after i use 7zip
amss.bin
boot img
mdm.bin
recovery img
system.img.ext4
and i have no idea how to flash it
Click to expand...
Click to collapse
I did flash and it stuck at Samsung Galaxy Tab 8.9 LTE logo and doesnt boot further. it's about an hour and nothing changed. Going to flash stock firmware now.
Update : Do not flash this firmware. Tab does't boot even after flashing stock firmware. Stuck at Samsung logo. Can anyone help ??
kunals.shah said:
I did flash and it stuck at Samsung Galaxy Tab 8.9 LTE logo and doesnt boot further. it's about an hour and nothing changed. Going to flash stock firmware now.
Update : Do not flash this firmware. Tab does't boot even after flashing stock firmware. Stuck at Samsung logo. Can anyone help ??
Click to expand...
Click to collapse
Hmm, not good. I'd focus on getting a working rooted (ie: not stock) recovery image first. Are you stuck at the boot loader logo (the first samsung logo with sharp text) or the initlogo in the ramdisk (second samsung logo, sort of looks like it's fuzzy and/or glowing) ? And can you get into it via ADB ? logcat might tell you where you're stuck at if you're lucky and have working ADB even though it doesn't fully boot...
twrp recovery:
http://forum.xda-developers.com/showthread.php?t=1697610
you'll probably need to install this via ODIN, since if you can't boot and don't have a proper recovery already, there's really no other way. See post #9.
If that works, try installing dannorom http://forum.xda-developers.com/showthread.php?t=1701865
Also, good catch on the Telus/Rogers OTA images!! They are smaller than the full image, which I assume means they only contain the updated files, and not the full package? Downloading now, it's a .bin file, 260mb, quite a bit smaller than the ~400mb complete HC image.
Don't know much about the OTA packages, but I'm guessing step #1 is to apply the stock HC image for the respective carrier.. how is the .bin flashed, ODIN?
The rogers, bell and telus HC images, as is, DO work on the ATT i957. I suspect the ICS images would too, but... never know without trying.
Suspecting your problem is mostly related to improperly applying the OTA image... anyone know the details of OTA?
nrvate said:
Hmm, not good. I'd focus on getting a working rooted (ie: not stock) recovery image first. Are you stuck at the boot loader logo (the first samsung logo with sharp text) or the initlogo in the ramdisk (second samsung logo, sort of looks like it's fuzzy and/or glowing) ? And can you get into it via ADB ? logcat might tell you where you're stuck at if you're lucky and have working ADB even though it doesn't fully boot...
twrp recovery:
http://forum.xda-developers.com/showthread.php?t=1697610
you'll probably need to install this via ODIN, since if you can't boot and don't have a proper recovery already, there's really no other way. See post #9.
If that works, try installing dannorom http://forum.xda-developers.com/showthread.php?t=1701865
Click to expand...
Click to collapse
I am stuck at second samsung logo. Tried installing TWRP and CWM recovery but no success. I tried restoring TWRP backup but still stuck at second samsung logo.
nrvate said:
Also, good catch on the Telus/Rogers OTA images!! They are smaller than the full image, which I assume means they only contain the updated files, and not the full package? Downloading now, it's a .bin file, 260mb, quite a bit smaller than the ~400mb complete HC image.
Don't know much about the OTA packages, but I'm guessing step #1 is to apply the stock HC image for the respective carrier.. how is the .bin flashed, ODIN?
The rogers, bell and telus HC images, as is, DO work on the ATT i957. I suspect the ICS images would too, but... never know without trying.
Suspecting your problem is mostly related to improperly applying the OTA image... anyone know the details of OTA?
Click to expand...
Click to collapse
No clue. As far as what I can figure out, they have to be applied via software update on a stock telus/bell image. If the update isn't on samsung's servers, it's back to the waiting game.
kunals.shah said:
I am stuck at second samsung logo. Tried installing TWRP and CWM recovery but no success. I tried restoring TWRP backup but still stuck at second samsung logo.
Click to expand...
Click to collapse
Well, atleast you have a working recovery and are attempting to boot. That's a start!
I assume your TWRP backup included the boot image?
Also, is adb available with the device hung at the second logo?
And also... did you do a wipe in TWRP? try the factory reset, which wipes data/cache, then wipe system as well.
I noticed the SHV-E140 ODIN package has a 806mb system.img.ext4, significantly bigger than the I957 honeycomb system.img.. and also bigger than the actual system partition! (mmcblk0p24, 687mb on my ATT 957). Did ODIN complete successfully? I have no idea what the behavior of ODIN-flashing a larger than expected system.img.ext4 is.
You might want to be sure you can even mount /system, /data and /cache within the recovery shell (adb to the device while in TWRP, you'll get a root shell).. and also check the sizes of these partitions in /proc/partitions to be sure the SHV140 ODIN image didn't alter that, although unless you checked the re-partition box (DO NOT DO THIS!!! under ANY circumstances!) in ODIN, it shouldn't have touched the partition allocations.. just in case, I got:
179 24 714752 mmcblk0p24
179 25 430080 mmcblk0p25
179 26 13512704 mmcblk0p26
---------- Post added at 12:06 PM ---------- Previous post was at 12:00 PM ----------
ubufugu said:
No clue. As far as what I can figure out, they have to be applied via software update on a stock telus/bell image. If the update isn't on samsung's servers, it's back to the waiting game.
Click to expand...
Click to collapse
Yea, thats about what I came to after it finally downloaded. The .bin appears to be a completely proprietary format and from what I can find via google, it's a delta (differences only) package... sort of like a patch. doh!
I'm guessing we'll see the full package via checkfus2 soon, as well as the source release. not sure how sammobile got the OTA package first, but that's encouraging
Ok, I DID flash the before mentioned ROM to my ATT Galaxy Tab 8.9. It ended up doing exactly what the other poster mentioned. It boots to the second boot logo, and then quits. I knew the possiblity of a Brick was there, but I did it anyways. It boots into the attached Boot Screen, then hangs.
Also, when I did the ODIN flash, it failed on Modem. I'm going to remove the Modem portion and try again. In the mean time, I rebooted into ODIN mode and flashed the Stock ROM, and it boots normal again, NO BRICK!!! :victory:
I will update this when I'm done trying different things on the ICS ROM...
So if I load the Rogers stock ROM and then this update from Sam, I should have ICS on my i957?
dmunjal said:
So if I load the Rogers stock ROM and then this update from Sam, I should have ICS on my i957?
Click to expand...
Click to collapse
most likely no. This is a pre-release ota, so it may not even be available for rogers/telus/bell users yet. e also don't know if it's just an updated version of hc
UPDATE: I've tried everything I can think of to get this ICS update on our Tab. Unfortunately, it plain does not fit. I don't want to mess with the Partions, so will leave it be. Next, I'm going to try the Rogers one and see if I can get anywhere...
EDIT: No success with Rogers ROM either. I cannot get it to flash at all. Fails immediately. Not giving up, just taking a break for now.
nrvate said:
The rogers, bell and telus HC images, as is, DO work on the ATT i957. I suspect the ICS images would too, but... never know without trying.
Click to expand...
Click to collapse
Have you flashed them to the ATT variant? I cannot get them to flash successfully.
ubufugu said:
most likely no. This is a pre-release ota, so it may not even be available for rogers/telus/bell users yet. e also don't know if it's just an updated version of hc
Click to expand...
Click to collapse
It's almost certainly not an update to HC, especially given it's size -- way too big for that. Besides, the test cycle for an OTA update is significant enough they'd just roll forward the ICS update if they needed to fix something critical -- after all, that test cycle is mostly complete now.
I really wouldn't touch this OTA at all.. Even if you convince the software update service to do the delta against whatever you're running, we have NO idea what else it updates -- It may touch the modem, boot image, recovery image, or other pieces that are even more touchy (ie: efs, bootloader, etc).
nrvate said:
It's almost certainly not an update to HC, especially given it's size -- way too big for that. Besides, the test cycle for an OTA update is significant enough they'd just roll forward the ICS update if they needed to fix something critical -- after all, that test cycle is mostly complete now.
I really wouldn't touch this OTA at all.. Even if you convince the software update service to do the delta against whatever you're running, we have NO idea what else it updates -- It may touch the modem, boot image, recovery image, or other pieces that are even more touchy (ie: efs, bootloader, etc).
Click to expand...
Click to collapse
Thanks for clarifying about the OTA, my knowledge of them is little to none. Hopefully the OTA update will roll out to bell/rogers/telus users soon and we can get a system/boot/etc dump that's a little more useful.
So, I have a nook color and I installed roms in it, rooted and other basic things. But recently my girlfriend got a dell streak from his brother and from two weeks of use, today it bootloops every single time. I have no experience on how to install the recovery or roms in it. My girlfriends brother never rooted it or changed the stock firmware. This is the device information I copied when I first took the device:
OS:
HC 3.2
Base band:
11.810.09.06.00
Core (kernel?) version:
2.6.36.3
OEM version:
GLUNB1A151130
Build:
19921
Service tag:
BH2L2P1
So, can I just factory reset (user data and internal tablet storage) the device and flash (software upgrade via update.pkg on sd card) the 21700 build on this page (http://forum.xda-developers.com/wiki/Dell_Streak_7#Official), or I have to do something else first?
Thank you very much in advance.
Update:
The factory reset solved the bootloop, now I am reading the posts to see which costume rom to install. Do you recommend one for battery life, performance and/or stability? Stock Froyo, Costume Froyo, Stock HC (version 511), update to version 514 of Stock HC, Costume HC (HoneyStreak R8 or other), CM10 nightlies?
Also, I know that the tab haves a sim slot, but I don't know which tab version is (4g, 3g or other). The original owner threw the box away long time ago and doesn't remember anything about the tab specifications. Is there a way to know which version is the tab with an app or a terminal command?
Thanks.
Well, you're the 1st person that I've seen have 511 firsthand.
Would you be willing to make a dump of it before updating?
As you're the 1st, you'll likely be the last with it.
As far as boot loops are concerned, if you have not rooted and modified system files: a fac reset should fix it.
If you/someone did modify files, that's likely the reason.
It's possible it's the rom itself that's the issue (or the hardware, we'll assume it's not a hardware issue unless otherwise), but noone else can comment as it's not a common version.
TheManii said:
Well, you're the 1st person that I've seen have 511 firsthand.
Would you be willing to make a dump of it before updating?
As you're the 1st, you'll likely be the last with it.
As far as boot loops are concerned, if you have not rooted and modified system files: a fac reset should fix it.
If you/someone did modify files, that's likely the reason.
It's possible it's the rom itself that's the issue (or the hardware, we'll assume it's not a hardware issue unless otherwise), but noone else can comment as it's not a common version.
Click to expand...
Click to collapse
I am not that tech savy, but I am guessing you want a "copy" of the rom for future references or development. Sure, no problem.
How do I do that? I have found this link (http://www.freaktab.com/showthread.php?401-Dumping-ROM-using-ADB-guide). Is it a complete guide or do you have a best guide/link to do it with this device?
Also, I updated the first post, managed to get out of the boot loops with the factory reset now that I am at my own home with this baby. XD
Wanted to update it tomorrow at first hour but first I would do the dump.
Thanks.
[Q] Dell S10 Pro - Need help in Updating
Read that and repeat the steps, it's essentially the same thing.
Requires that you understand the command line (just basic commands)
The major differences: (on the S7 instead of the S10)
APX mode is Vol up + vol down + power
Use this bootloader: bootloader.bin
Files of interest: P4, P5, P9, P10, P11
Any needed files are listed in stickies on the dev subforum, if you need more specific instructions, just ask.
(except for basic "how to use the command line", there are many tutorials on the web)
Beyond that, to update, just download the 514-30 version from the wiki, the one with a baseband version indicated.
As you seem to have a US4g model, that would be the one to use.
(assuming you wish to use a stock rom)
Since you have a DS10, Honeystreak nor CM10 will work on it.
As I don't have one, I haven't made a ROM for it.
He has a S7, I merely linked to that thread as I just helped someone do the exact same thing on a S10.
Steps are more or less identical as it uses APX mode, with the differences already mentioned.
Ah gotcha.
Sent from my Nexus 7 using Tapatalk 2
Are the partition image files available somewhere for download ?
TheManii, I've sent you the dropbox link in your inbox, please check if everything is alright.
Sorry for the extended delay... :s
Assuming that dump you gave me is a good image: I would recommend updating to 514 first regardless of what you're ultimately going to flash.
You'll have a good baseline to compare incase you wish to flash a custom rom afterwards.
As you have a stock recovery (assuming you didnt overwrite it with a custom one), just download the 514-30 us4g pkg and update.
I dont know if a manual update will wipe data, so you would be recommended to make a backup beforehand
Edit: the dump seems to be good (in that it doesnt look corrupt offhand) thanks
To backup I have to install the costume recovery of one of your threads ([Recovery]Clockwork Mod 6.0.1.2: http://forum.xda-developers.com/showthread.php?t=1334487) or is it a better way to do it (NVflash or other recovery)?
I would normally only update, but since this 511 version is uncommon, who knows if somebody else needs it in the future for something in particular.
If you're backing up userdata, use a custom recovery.
You can use "fastboot boot <image name>" instead of "fastboot flash recovery <image name>" to only run it instead of permenently installing it.
511 is only important because I collect roms, beyond that it's not terribly interesting.
I have a bionic on stock JB. I have FXZ many times and do not get any errors with FXZ, but it seems that the radio never gets written.
I belive the radio files only get written after the 1st reboot after FXZ process. During that time, I see the robot with the chest open. It appears to be doing some file updates, and I don't get any errors. However, after flashing, I always get "baseband version: unknown" when I check the phone info.
I have attempted to do stock recovery using update_zip. The update zip contains bp.img and lte.imp. When I tried to flashe those file in recovery mode, I see that it goes though some package verification process, then it aborts. So the files never get flashed.
Is there some other way I can flash these radio files? I tried some custom roms like blurry, carbon. None of them include radio files, so the custom roms still run off the corrupt radio files that I have.
Since fxz and stock recovery doesn't flash the radio files, is there any other way to update these file? My phone is rooted, so can safestrap update do it? Or can I do it through adb? Or copy the files in through root explorer?
I heard that the radio files reside on the /radio partition, but I have not seen that directory when I use root explorer. Many it's not normally mounted. Does any know how mount that partition for edit?
The FXZ file has radio.img, but the stock recovery has bp.img/lte.img does anyone know what's the difference?
bobdole said:
I have a bionic on stock JB. I have FXZ many times and do not get any errors with FXZ, but it seems that the radio never gets written.
I belive the radio files only get written after the 1st reboot after FXZ process. During that time, I see the robot with the chest open. It appears to be doing some file updates, and I don't get any errors. However, after flashing, I always get "baseband version: unknown" when I check the phone info.
I have attempted to do stock recovery using update_zip. The update zip contains bp.img and lte.imp. When I tried to flashe those file in recovery mode, I see that it goes though some package verification process, then it aborts. So the files never get flashed.
Is there some other way I can flash these radio files? I tried some custom roms like blurry, carbon. None of them include radio files, so the custom roms still run off the corrupt radio files that I have.
Since fxz and stock recovery doesn't flash the radio files, is there any other way to update these file? My phone is rooted, so can safestrap update do it? Or can I do it through adb? Or copy the files in through root explorer?
I heard that the radio files reside on the /radio partition, but I have not seen that directory when I use root explorer. Many it's not normally mounted. Does any know how mount that partition for edit?
The FXZ file has radio.img, but the stock recovery has bp.img/lte.img does anyone know what's the difference?
Click to expand...
Click to collapse
Dumb question, but have you verfied MD5 on your fxz to make sure your download wasn't corrupt?
useltonm said:
Dumb question, but have you verfied MD5 on your fxz to make sure your download wasn't corrupt?
Click to expand...
Click to collapse
Yes, the MD5 does match up. This brings up the question if I got the file from the right place.
I have not being able to find any other place to down load the JB stock rom other than this place:
http://sbf.droid-developers.org/cdma_targa/list.php
Did I get it from the right place?
bobdole said:
Yes, the MD5 does match up. This brings up the question if I got the file from the right place.
I have not being able to find any other place to down load the JB stock rom other than this place:
http://sbf.droid-developers.org/cdma_targa/list.php
Did I get it from the right place?
Click to expand...
Click to collapse
The bottom one is definitely the correct one for jb on the bionic.
Let me check something and I'll get back to you.
Sent from my XT875 using Tapatalk 4
---------- Post added at 01:32 AM ---------- Previous post was at 01:26 AM ----------
I was going to suggest trying the house of bionic, but it looks like you already went there.
Sent from my XT875 using Tapatalk 4
Can anyone help?
I'm trying to do an experiment to flash just the latest JB bp.img and lte.img (radio files) in stock recovery.
When I do it it fails on package validation.
I found some older 902 and older radio files, those do not fail package validation, but fail to flash.
I assume they fail because of security(no going back to older version).
I need some to help package the bp, lte.img files into a zip. I tried the signapk tool. It seems to generate all the manifest files, but somehow the files do not pass package validation.
I tried taking the 902 radio files that pass package validation and run them through signapk, and sure enough they would fail package validation after signapk.
Can anyone help, please!
https://dl.dropboxusercontent.com/u/7632904/targa_jb_update_radio.zip
This is the radio only update.zip that contains the bp.img and lte.img that are digitally signed by Motorola and is pulled from the radio.img of the Bionic JB release from the XML.zip.
System Version
98.72.22.XT875.Verizon.en.US
Baseband Version
CDMA_N_05.22.00 LTEDC_U_09.1D.00
These are the only files you can flash the radio with on any MDM6600 Motorola device. They must be the signed images in the original file flashed in stock recovery.
If you flash these and still have Baseband Unknown errors then you may have a corrupt amss.mbn and we don't have files to fix that for any recent releases.
That is extremely rare and if you flash the properly signed baseband images it should restore normal function in almost all cases.
cellzealot said:
https://dl.dropboxusercontent.com/u/7632904/targa_jb_update_radio.zip
This is the radio only update.zip that contains the bp.img and lte.img that are digitally signed by Motorola and is pulled from the radio.img of the Bionic JB release from the XML.zip.
System Version
98.72.22.XT875.Verizon.en.US
Baseband Version
CDMA_N_05.22.00 LTEDC_U_09.1D.00
These are the only files you can flash the radio with on any MDM6600 Motorola device. They must be the signed images in the original file flashed in stock recovery.
If you flash these and still have Baseband Unknown errors then you may have a corrupt amss.mbn and we don't have files to fix that for any recent releases.
That is extremely rare and if you flash the properly signed baseband images it should restore normal function in almost all cases.
Click to expand...
Click to collapse
Hi cellzealot,
I really appreciate your help. I tried flashing your file, but I get the same error as when I flash for full JB update file, which is:
assert failed: motorola.motoflash("/tmp/bp.img")
I was wondering if you could do one more thing to help..
Since it's failing assert, what if we modify the script to no do a assert check, but just run the command?
This is the update-script:
assert(show_progress(0.2, 2),
do_format_cache(true);
package_extract_file("bp.img", "/tmp/bp.img"),
package_extract_file("lte.img", "/tmp/lte.img"),
show_progress(0.8, 35),
motorola.motoflash("/tmp/bp.img"),
motorola.motoflash("/tmp/lte.img"),
delete("/tmp/bp.img", "/tmp/lte.img"));
What if we make it like this:
show_progress(0.2, 2),
do_format_cache(true);
package_extract_file("bp.img", "/tmp/bp.img"),
package_extract_file("lte.img", "/tmp/lte.img"),
show_progress(0.8, 35),
motorola.motoflash("/tmp/bp.img"),
motorola.motoflash("/tmp/lte.img"),
delete("/tmp/bp.img", "/tmp/lte.img");
I'm hoping that this might work.
BTW, how did you package the zip file and sign the files?
The original zip file had lots other system/boot files.
Thanks!
I didn't sign or edit the files at all. The update.zip is pulled from the radio.img using a hex editor.
Te radio image is an ext3 partition that just contains the update.zip which itself contains the signed bp.img and lte.img that are flashed in recovery after the device reboots from AP fastboot bootloader.
This is because the MDM6600 Motorola devices are all hybrid chipset boards and the OMAP AP chipset is separate from the Qualcomm MDM6600 CDMA/EVDO/GSM/WCDMA radio and the Motorola TI Wrigley LTE radio.
The radio chips are setup on a BP passthrough only device interface that cannot be flashed in AP Fastboot mode.
This is why you can't see the radio partitions in the file system of the device and the kernel layer only has access to the radio via the RIL.
Regarding the persistent errors, it sounds like it is failing due to the recovery because there is no reason it would fail asserts with the signed files in stock recovery.
cellzealot said:
I didn't sign or edit the files at all. The update.zip is pulled from the radio.img using a hex editor.
Te radio image is an ext3 partition that just contains the update.zip which itself contains the signed bp.img and lte.img that are flashed in recovery after the device reboots from AP fastboot bootloader.
This is because the MDM6600 Motorola devices are all hybrid chipset boards and the OMAP AP chipset is separate from the Qualcomm MDM6600 CDMA/EVDO/GSM/WCDMA radio and the Motorola TI Wrigley LTE radio.
The radio chips are setup on a BP passthrough only device interface that cannot be flashed in AP Fastboot mode.
This is why you can't see the radio partitions in the file system of the device and the kernel layer only has access to the radio via the RIL.
Regarding the persistent errors, it sounds like it is failing due to the recovery because there is no reason it would fail asserts with the signed files in stock recovery.
Click to expand...
Click to collapse
Thank you for your explanation.
I was able to find the radio.img file from the OTA xml.zip for fxz.
Indeed, if I open the radio.img I find the update_radio.zip that you have provided.
What I don't quite understand is why we are able to flash various custom roms that are not signed by motorola through CWM, TWRP.
Would there be a way to run a modified update_radio.zip through CWM, TWRP?
"Now to" needed
cellzealot said:
....... link removed because it won't let me post with it in here.......
This is the radio only update.zip that contains the bp.img and lte.img that are digitally signed by Motorola and is pulled from the radio.img of the Bionic JB release from the XML.zip.
System Version
98.72.22.XT875.Verizon.en.US
Baseband Version
CDMA_N_05.22.00 LTEDC_U_09.1D.00
Click to expand...
Click to collapse
I have found a lot of information about needing to flash the Bionic radios, and that its not included in the custom ROM (I have a current Cyanogen nightly & baseband CDMA_n_05.13.01R LTEDC_U_09.14.00). I downloaded the file you listed above, but now the question that I can't seem to find the answer to.... "Now What"... when I installed safestrap and the custom rom i found some very helpful step by step instructions... I can't not seem to locate the same for flashing in new radio files.... so if someone could point me in the direction of some that would be most helpful...
BTW.... Typing "upgrade bionic radio files" into forums and Google returns everything BUT what I am looking for
RichT1 said:
I have found a lot of information about needing to flash the Bionic radios, and that its not included in the custom ROM (I have a current Cyanogen nightly & baseband CDMA_n_05.13.01R LTEDC_U_09.14.00). I downloaded the file you listed above, but now the question that I can't seem to find the answer to.... "Now What"... when I installed safestrap and the custom rom i found some very helpful step by step instructions... I can't not seem to locate the same for flashing in new radio files.... so if someone could point me in the direction of some that would be most helpful...
BTW.... Typing "upgrade bionic radio files" into forums and Google returns everything BUT what I am looking for
Click to expand...
Click to collapse
Put the radio file on a SD card(leave it as .zip, don't unzip it) put the sd card in in your phone.
The follow these instructions to flash in recovery mode:
http://www.droid-life.com/2011/09/2...boot-menu-for-recovery-sbf-flashing-and-more/
In recovery mood, select update zip from ext-sdcard
Then pick the radio file..
That's it.
bobdole said:
Put the radio file on a SD card(leave it as .zip, don't unzip it) put the sd card in in your phone.
The follow these instructions to flash in recovery mode:
.... link removed .....
In recovery mood, select update zip from ext-sdcard
Then pick the radio file..
That's it.
Click to expand...
Click to collapse
Thank you.... worked like a charm....:victory:
I'm literally a real noob when it comes to this stuff.. But when I tried to flash the radio files from above via recovery, I got this error.
assert failed: motorola.motoflash("/tmp/lte.img")
I've lost my lte baseband way before trying this, I've actually lost it, running a Carbon nightly rom.
EDIT
I've changed the updater script and now I'm having a problem with it aborting the installation alltogether. Any help would be greatly appreciated. I just want to get my LTE radio working :|
cellzealot said:
https://dl.dropboxusercontent.com/u/7632904/targa_jb_update_radio.zip
This is the radio only update.zip that contains the bp.img and lte.img that are digitally signed by Motorola and is pulled from the radio.img of the Bionic JB release from the XML.zip.
System Version
98.72.22.XT875.Verizon.en.US
Baseband Version
CDMA_N_05.22.00 LTEDC_U_09.1D.00
These are the only files you can flash the radio with on any MDM6600 Motorola device. They must be the signed images in the original file flashed in stock recovery.
If you flash these and still have Baseband Unknown errors then you may have a corrupt amss.mbn and we don't have files to fix that for any recent releases.
That is extremely rare and if you flash the properly signed baseband images it should restore normal function in almost all cases.
Click to expand...
Click to collapse
Hi CellZealot,
Do you have radio.zip file(s) from GB versions by any chance? I'm on ICS and want to try GB radio(s) hoping to get better signal strength and possibly enable 900/1800mhz band if it's disabled in ICS radio. I'm still experimenting to get my Bionic (Hw A, 08/12) to work on 900/1800mhz.
Is Droid Razr also MDM6600 Motorola device? If yes, can I try and get its radio and flash on Bionic? Please advise.
Thanks.
https://www.dropbox.com/s/vnob615mwf17xxk/Bionic_Radio.zip
I believe that zip has most or all of the older radios. Posting from phone at work.
cellzealot said:
https://www.dropbox.com/s/vnob615mwf17xxk/Bionic_Radio.zip
I believe that zip has most or all of the older radios. Posting from phone at work.
Click to expand...
Click to collapse
Thanks a lot CellZealot. You're a gem!!
cellzealot said:
https://www.dropbox.com/s/vnob615mwf17xxk/Bionic_Radio.zip
I believe that zip has most or all of the older radios. Posting from phone at work.
Click to expand...
Click to collapse
I tried flashing a couple of radios from that zip file via recovery and the update was successful each time. I did NV edits, buildprop changes and the factory data reset each time. But when I checked the Baseband version info, the LTE component was missing e.g..it only shows CDMA_N_04.07.02R. I suspect somehow LTE part was not flashed via recovery even though no error was shown. Also IMEI and SV show up unknown as well. Did I miss some step or did I do something incorrectly? Please advise.
Thanks in advance.
P.S. I didn't rename the radio zip file to update.zip. Just used the files as is from the above zip. I'm trying to use them on ICS, These GB radios aren't fully compatible with the ICS version kernel or something?
This post helped me fix my bionic... the same process applies to the baseband unknown issue that i had and i found a lot of bionic owners have the issue also. the simplest fix is actually not to put the radios on the sd card but instead to make a copy of the xml doc that is in the fastboot files and delete every step but the radio install (the last step) then use rsd lite and change the xml file to the one with the radio
I have been working on my bionic for months.
Casey Walt said:
This post helped me fix my bionic... the same process applies to the baseband unknown issue that i had and i found a lot of bionic owners have the issue also. the simplest fix is actually not to put the radios on the sd card but instead to make a copy of the xml doc that is in the fastboot files and delete every step but the radio install (the last step) then use rsd lite and change the xml file to the one with the radio
Click to expand...
Click to collapse
This all started back in december 2013. a buddy gave me a bricked bionic.. i was able to "unbrick". and install the 98.72.22 fxz. i only get service half of the day and 3g like maybe 30min...i also have the error where the lte.img will not install. Thus please explain more as to how you were able to fix it. Do you have 4g? i haven't been able to restore it. i had to splice a usb cord and attach the pos and neg to the battery and connect a charging cord from the phone to my desktop to get a led response from the phone during the unbricking process. basically if i install a new rom daily i have steady service all day.. 3g even. but then it just craps out on me. believe me, im not giving up on this phone until i see a 4g icon on my status bar.
I have an S3 now but i can still glady help you.... what i did was put a shim in my sim card holster. then put the .905 radio in the fxz folder and flash it again... you wait like 5-10 min till you have service ( if you did it right there should be no lte in the baseband yet) then put the zip file for the 4.1.2 radio on your sd card and flash it through stock recovery. when you boot your phone up you wait 5-10 min again and you should have both 3g and lte in your baseband
Sent from my SCH-I535 using xda app-developers app
Hello everybody,
I got new R1 HD which came with 6.1 firmware and tries to download 7.4.2.
Can you please tell where zip file with firmware is located?
I checked /Android/com.fota.adups folders during download but file is not there.
Right now download is at ~50% completed.
Should I wait for download to complete?
I already checked this thread https://forum.xda-developers.com/r1-hd/help/folder-update-downloaded-to-t3511204
It refers to another thread with URL link with zip file but it is for OEM variant and I have Prime version.
ivarme said:
Hello everybody,
I got new R1 HD which came with 6.1 firmware and tries to download 7.4.2.
Can you please tell where zip file with firmware is located?
I checked /Android/com.fota.adups folders during download but file is not there.
Right now download is at ~50% completed.
Should I wait for download to complete?
I already checked this thread https://forum.xda-developers.com/r1-hd/help/folder-update-downloaded-to-t3511204
It refers to another thread with URL link with zip file but it is for OEM variant and I have Prime version.
Click to expand...
Click to collapse
I know I saw a link in the forum for both sock oem and prime versions posted. Look in the guides section, then in the index thread. But if you want to stay stock, just wait for the download.
Oem can be installed on prime. If this is what you want to do, it is easier to do it before updating, that way you can do it without messing up the preloader and lk
Never apply the downloaded update if you want to be able to do things like get root and flash roms. Install the SAFE versions of the updates that have been modified instead.
I suggest you read all the way through this thread: https://forum.xda-developers.com/r1-hd/development/prime-stock-rom-6-5-flashed-via-twrp-t3455532 You can flash either the prime or non-prime version depending on whether you want to have the prime apps or not.
I found this link but not on forums and it is for 8GB model:
http://hwfotadown.mayitek.com/ota/r....2_GENERIC_6.0_20161109-13431478711915353.zip
I tired to modify it for 16GB model but modified link does not work.
Actually all links posted in forums are for 8GB model and looks like people use them for 16GB R0030UU model. Is this right?
Also all these links are OTA not OOB firmwares.
In case I put modified firmware on this device it would be nice to have OOB firmware if needed to restore to original factory state.
Found only one thread https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499 with OOB firmwares but these are not original factory OOBs, they have only 3 partitions to restore, these are probably pulled from device.
So I guess once I complete above thread to mod device there is no way to OEM relock device or full factory restore of all partitions?
ivarme said:
I found this link but not on forums and it is for 8GB model:
http://hwfotadown.mayitek.com/ota/r....2_GENERIC_6.0_20161109-13431478711915353.zip
I tired to modify it for 16GB model but modified link does not work.
Actually all links posted in forums are for 8GB model and looks like people use them for 16GB R0030UU model. Is this right?
Also all these links are OTA not OOB firmwares.
In case I put modified firmware on this device it would be nice to have OOB firmware if needed to restore to original factory state.
Found only one thread https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499 with OOB firmwares but these are not original factory OOBs, they have only 3 partitions to restore, these are probably pulled from device.
So I guess once I complete above thread to mod device there is no way to OEM relock device or full factory restore of all partitions?
Click to expand...
Click to collapse
well , yes you can return to factory (out of box) condition. But only with pulled from device images. I made backups of my phone on day one, when i opened the box. If you want to be able to return to "clean slate" you can use some ones pulled images or make your own.
manually enter scatter information into sp flash tool on read back tab
or
use miricle box (little difficult to set up drivers)
or
if rooted and ok with a rooted backup use dd in adb shell
Thank you Mrmazak.
Would be possible to mount 6.1 system.img on Linux PC, modify it, remove Amazon apps and flash it back with spft?
I would rather go my own way to mod device and upgrade to my own modified 7.4.2. For example both BLU firmwares and modded zip ROMs found on forums have Baidu_Location.apk which I presume sends location data to China?