I'm about at my wits end trying to figure out this problem of mine.
Here's a quick overview of my situation, so I don't have to go through it again:
http://forum.xda-developers.com/showthread.php?t=1301091
Anyways, I decided to take another shot late at night to see if I could get this working. I'm running on 3.2.2 right now, build HLK75D, with no 3G/4G connectivity. I looked at a screen shot of a stock updated 4G Xoom's settings and I noticed that my baseband is the only thing different.
Is there some way to change the baseband from what it is now (CDMA_N_03.1A.54P) to "CDMA_N_03.1A.52P ltedc_u_05.15.00"?
I'm having the same problem. Downgraded, took updates, overwrote the radio image. Oops. No LTE. Gone. You can re-activate it on 3G, but that's about it.
Jewremy said:
I'm having the same problem. Downgraded, took updates, overwrote the radio image. Oops. No LTE. Gone. You can re-activate it on 3G, but that's about it.
Click to expand...
Click to collapse
Yeah, well, I don't have either 3G or 4G. My Xoom says activation successful over Wi-Fi, and I have full signal with the Verizon towers, but it just doesn't connect.
I still haven't heard anything back from Motorola regarding any way to get the baseband back to the LTE version.
Guys use Motorola stock imgs, but remove your sim card after you flash it. See if it connects to 3g then. If not look for the hlk75c stock root on here flash that with your sim in.
Sent from my Xoom using xda premium
HLK75C is the Verizon one. Try to flash this.
http://forum.xda-developers.com/showthread.php?t=1294824
Sent from my Xoom using xda premium
hammer4203 said:
HLK75C is the Verizon one. Try to flash this.
http://forum.xda-developers.com/showthread.php?t=1294824
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
We've tried that. No dice. I think it may be the bootloader that turns the radio on/off. HTJ85B or whatever it was overwrites the bootloader. If you power down, then power up BP (hold vol up + vol down on boot), it says LTE Radio OFF Cold booting linux. We need to turn that LTE radio on.
Did you flash hri66? What kernels have you tried? Oh and are you in a 4g area, cuz that can cause an issue if your not.
Sent from my Xoom using xda premium
http://forum.xda-developers.com/showthread.php?p=18224270
AceXMachine's post has a 7z file that should put you back. He did the same thing as you and he is back up.
Sent from my Xoom using xda premium
hammer4203 said:
http://forum.xda-developers.com/showthread.php?p=18224270
AceXMachine's post has a 7z file that should put you back. He did the same thing as you and he is back up.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
I've tried AceXMachine's solution. Still no deal.
No matter what image I've used, I still have no option for LTE in my mobile network settings. My baseband still has never changed back to LTE.
I live in the dead center of a strong 4G area. My 4G was working fine prior to making the stupid mistake of flashing over what Motorola sent back.
Jewremy said:
We've tried that. No dice. I think it may be the bootloader that turns the radio on/off. HTJ85B or whatever it was overwrites the bootloader. If you power down, then power up BP (hold vol up + vol down on boot), it says LTE Radio OFF Cold booting linux. We need to turn that LTE radio on.
Click to expand...
Click to collapse
And that is exactly what mine says when I power up BP.
I just received a total generic e-mail response from Motorola telling me to make sure to check for updates, etc.
I replied to them and told them that my baseband is the wrong version and that my LTE radio is turned off. Lets see if they can provide anything to help out.
Anyone know how I can get you the baseband from my xoom? I am rooted on hlk75d. Just give me some directions and I will pull it for ya.
Sent from my ADR6400L using xda premium
hammer4203 said:
Anyone know how I can get you the baseband from my xoom? I am rooted on hlk75d. Just give me some directions and I will pull it for ya.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
I think it involves pulling your build.prop?
http://android.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
dethrok said:
I think it involves pulling your build.prop?
http://android.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
Click to expand...
Click to collapse
No. This is lower-level software. It's part of the bootloader, governs the radio. The build.prop files are the same between 3.2.2 back from moto and 3.2.2 upgraded from stock.
I am not find anything on how I can extract the file it files you need! Makes no sense. I know there has got to be a way to just pull the radio and make an update zip.
Sent from my Xoom using xda premium
I actually think it is a kernel or kernel module issue. I started another post in this direction. http://forum.xda-developers.com/showthread.php?t=1305039
Basically I can see the "wrigley" LTE modem in /system/build.prop and dmesg but I don't see the device in /sys/bus/usb/devices so the system can't use it. I thought the kernel lived in boot so I am surprised that flashing a new boot.img doesn't fix it, but for me at least it doesn't.
hammer4203 said:
I am not find anything on how I can extract the file it files you need! Makes no sense. I know there has got to be a way to just pull the radio and make an update zip.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
It is not. I'm about 90% sure that this is a bootloader issue. If you boot up in BP tools mode, it says LTE radio is off.
It can't be the radio (aka baseband) 'cuz none of the updates change the baseband. Always the same one even on HRI39 and HRI66. EDIT: Nevermind. Don't bother.
zarkuu said:
I actually think it is a kernel or kernel module issue. I started another post in this direction. http://forum.xda-developers.com/showthread.php?t=1305039
Basically I can see the "wrigley" LTE modem in /system/build.prop and dmesg but I don't see the device in /sys/bus/usb/devices so the system can't use it. I thought the kernel lived in boot so I am surprised that flashing a new boot.img doesn't fix it, but for me at least it doesn't.
Click to expand...
Click to collapse
See above in this same post.
Well, this is all hurting my head. Motorola e-mailed me back and said they were bumping my case up to their repair escalation team and I'll be getting a call in 1-2 days.
Hopefully they'll still help me out when it was my own stupid fault that I screwed up my connection. Maybe they'll be able to give me a solution to turn the radio back on.
Jewremy said:
It is not. I'm about 90% sure that this is a bootloader issue. If you boot up in BP tools mode, it says LTE radio is off.
It can't be the radio (aka baseband) 'cuz none of the updates change the baseband. Always the same one even on HRI39 and HRI66. I'm thinking the baseband is contained in the ebb partition, also known as the bootloader. Reflashing the bootloader is extremely risky. You really don't want to do that. It's at /dev/block/mmcblk1p1. Controls the whole boot sequence. The HTJ85B update overwrites/updates the bootloader, which is what could cause our issue.
Click to expand...
Click to collapse
OK, this makes sense to me since I have flashed back to HRI66 and did OTA updates to HTL85B and nothing else would presumably have changed it back. My mistake was probably allowing the device to boot under HTJ85B. If I had just done it through recovery and then flashed back to HLK75C it wouldn't have touched the bootloader. I bet some people didn't do that and so they work when flashing various restores. I understand it is risky to flash the bootloader (because if it goes wrong you won't be able to even go to fastboot) but what other option is there other than RMA back to Moto? Do we think Moto will be releasing stock images for this new bootloader anytime soon? That's really more of a rhetorical question I think.
I guess if someone wants to try making a backup I might try flashing it.
From http://forum.xda-developers.com/showthread.php?t=1294824
Pulling your own images
1. Flash a custom recovery
2. Boot straight into recovery.
Code:
adb shell
mount /data
mkdir -p /data/media/images
dd if=/dev/block/platform/sdhci-tegra.3/by-name/ebb of=/data/media/images/bootloader322.img
sync
Then reboot back into android and pull it off your device.
See if you can use this.
http://forum.xda-developers.com/showthread.php?t=1270848
Sent from my Xoom using xda premium
I'm in the same boat: http://forum.xda-developers.com/showthread.php?t=1299485
Hopefully we'll find an answer soon.
hammer4203 said:
See if you can use this.
http://forum.xda-developers.com/showthread.php?t=1270848
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
No dice. I've checked all the OTA updates I know about:
19dea2ba1ae5.signed-trygon-HTJ85B-from-HMJ37.19dea2ba.zip
7a15c95f18ba.signed-trygon-HLK75-from-HLK42B.7a15c95f.zip
7ac6aeb09117.signed-trygon-HLK75D-from-HLK75C.7ac6aeb0.zip
a5de99b3e437.signed-trygon-HMJ37-from-HRI66.a5de99b3.zip
In HMJ37 from HRI66 (3.0.1 to 3.1) I see a bootloader.bin along with this in the updater-script
Code:
assert(package_extract_file("bootloader.bin", "/tmp/bootloader.bin"),
moto.set_mbm_update("/tmp/bootloader.bin"),
delete("/tmp/bootloader.bin"));
There is nothing else that does an "set_mbm_update" in any of the other updates.
On the upside the md5sum of this bootloader.bin matches my own dd dump of the ebb partition.
Code:
c3a74df4a356c0e4158fd592cc8be693 bootloader.img
c3a74df4a356c0e4158fd592cc8be693 /tmp/updates/bootloader.bin
I'd be interested to see if someone can take a dump of their ebb partition as I documented earlier and see if the md5sum matches. if it does, then we will know the bootloader is not the problem. If not, then this is something new to try. Basically we need the dump and then an update.zip to flash it. If someone can provide the dd dump then I can make the update.zip. That should be safe enough to flash I think.
Related
[MegaUpload][Not signed] http://www.megaupload.com/?d=KZMXFFKN
Be still unsigned, you can`t flash it to a productions phone. only engineering phones are allowed.
[MegaUpload][Signed] http://forum.xda-developers.com/showpost.php?p=15954239&postcount=174
This one can still not be flashed to productions phone.
without signature...so still could not flash it right now?
WongJames said:
without signature...so still could not flash it right now?
Click to expand...
Click to collapse
yes, can only be flashed to engineering devices.
Thank you for your contribution to Milestone2.
I don't see any "[2.3 Leak] complete .sbf of Official GB ROM"
ARE YOU KIDDING OR WHAT?!!!!
not kidding,please be reading my post carefully.
Thank you for bringing it here,uploading it to international file host service is too troubling for me. What I want to point out is that even it's unsigned, we can depack anyway,maybe we can repack a system.img and boot.img.
Or you can try to force flashing or fake your phone as a prototype,neither way is in my reach.
Sent from my ME722 using XDA App
I am sorry, but although I am happy that 2.3 is finally leaking I only see China Retail instead of UK something in the filename. Additionally, what can be achieved with this sbf? Can it be signed afterwards, will it be flashable somehow? Thanks.
In China GB is just short for GuoBiao,mean's national standard for character not the Great Britain.
Sent from my ME722 using XDA App
JunHou said:
In China GB is just short for GuoBiao,mean's national standard for character not the Great Britain.
Sent from my ME722 using XDA App
Click to expand...
Click to collapse
I mean GingerBread here......
can it flash by sbf_flash in Linux? I see the sbf_flash can flash boot.img by "sbf_flash -r -d --boot boot.img"... Is it true?
PS. sorry for my English.
It's time about time MS2 got GB!! Can't wait for the official version.
Will my phone be functional once I flash it since the leak is based in China (I think?) and I'm from US? Functional meaning phone data and calls/texts (phone service). I want to know before I flash!
Thanks.
SedaG said:
Will my phone be functional once I flash it since the leak is based in China (I think?) and I'm from US? Functional meaning phone data and calls/texts (phone service). I want to know before I flash!
Thanks.
Click to expand...
Click to collapse
This ROM is unsigned. And because of that fact, RSD Lite won't let you flash it onto the phone.
frenetico said:
This ROM is unsigned. And because of that fact, RSD Lite won't let you flash it onto the phone.
Click to expand...
Click to collapse
so how do I get it on my phone?
EDIT: It says "cannot be flashed to production phones." If mine is not a production phone can I then flash it? (Is my understanding)
SedaG said:
EDIT: It says "cannot be flashed to production phones." If mine is not a production phone can I then flash it? (Is my understanding)
Click to expand...
Click to collapse
Well, if you got a developer phone you can flash it.
Some others managed to flash another .sbf of the 2.3 leak onto their phones which refused to boot properly.
I have a developers phone, except I think my phone is in a boot loop anyways I just flashed it and I'm not sure if it's just supposed to take this long the first time booting up, bc it took a while in the past. My boot-up image is the same as before and it keeps repeating. I'm gonna wait a little more, pull the battery ( ) if no results and do a hard factory reset with the new .sbf
Did you erase the cache through android recovery?
frenetico said:
Did you erase the cache through android recovery?
Click to expand...
Click to collapse
dammit no. I forgot! ughhh. What can I do? The hard factory reset isn't working. Should I flash my old sbf?
EDIT:
Took forever, pressing the search key doesn't open the android recovery menu anymore.. i basically hit all the keys like an idiot until it popped up. I think it was both volume keys at the same time that did it. I wiped cache and then did a factory reset and it works beautifully.
ONE PROBLEM.
Forgot China had issues with Facebook and Google, so you can't hook up those two accounts.. which is very important to me.. so no Gmail unless you use a 3rd party app from market which I'm looking up now. Don't know if I really like that.
Oh, long story short. I got it
How come you have a developer phone? Yes, try to flash last or working sbf and then wipe cache before updating
Sent from my MotoA953 using XDA App
All workt realy good with Tiamat 2.2
Then I got the less awesome ide of trying the new 3.2.2 update.
Now the crazy thing happend I lost all my 3G.
So I figured if I flash back to Tiamat it might solve the problem, but nope
and I tryed flashing back to stock and still no 3g.
Anyone have an ide of what I mest up and how to fix this.
Did you flash the stock rooted 3.2.2 that tells you that you will lose 3G if you do???
flash back to 3.2, and it should come back, but 3.2.2 is for the ones with the 4g chip installed.
yea I must have mist that, but when flashing back or to stock I dident get my 3g back, Gonna trye flashing some more (Got all day)
---------- Post added at 03:32 PM ---------- Previous post was at 03:19 PM ----------
yeay, ok after some flashing and some tvshow waching I finally got my 3g back
Now my Xoom feels compleete tnx all
Nandroids are your friend.
Sent from my Xoom using xda premium
I have no 3G now either.
I received my Xoom back fro the 4G upgrade yesterday, unlocked and right before pushing su and superuser files I started bootlooping.
I re-locked with instructions on Motorola's website which got me back to 3.0 but I cannot connect to 3G now (I'm not in a 4G area).
I've tried flashing nand backup after rooting 2nd time but got bootlooped again so re-locked again.
I did all the OTA upgrades and am at 3.2 now, but still have no connectivity. WiFi works fine...
Anyone have suggestions?
raw33 said:
I have no 3G now either.
I received my Xoom back fro the 4G upgrade yesterday, unlocked and right before pushing su and superuser files I started bootlooping.
I re-locked with instructions on Motorola's website which got me back to 3.0 but I cannot connect to 3G now (I'm not in a 4G area).
I've tried flashing nand backup after rooting 2nd time but got bootlooped again so re-locked again.
I did all the OTA upgrades and am at 3.2 now, but still have no connectivity. WiFi works fine...
Anyone have suggestions?
Click to expand...
Click to collapse
let me know if you ever get this resolved... exact same situation as you.
http://dl.dropbox.com/u/22648028/HLK75Csystemboot.7z password is "AceXMachine" without the quotes
Flash via fastboot same as stock images.
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
May need to wipe data, don't forget to erase cache. 4G and WiFi working on my xoom with these images and it should already be rooted. Let me know if it works.
AceXMachine said:
http://dl.dropbox.com/u/22648028/HLK75Csystemboot.7z password is "AceXMachine" without the quotes
Flash via fastboot same as stock images.
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
May need to wipe data, don't forget to erase cache. 4G and WiFi working on my xoom with these images and it should already be rooted. Let me know if it works.
Click to expand...
Click to collapse
i guess i should ask which rom did you flash from? did you go from the stock and rooted 3.2.2 rom from the dev thread? or from a complete stock factory image?
Does it have the lte/cdma with in networks? And do we need to have a custom recovery? If it is rooted can I go straight from stock 3.2.2?
Sent from my Xoom using xda premium
I just applied this and no LTE/CDMA option.
So under mobile networks there is no setting for you to switch? Then this is not the most up to date version.
Sent from my Xoom using xda premium
There is some version that the LTE devices ship back with labeled 3.2.2, but it does not look like what others have posted all over the net saying 3.2.2. Not sure what the deal is but I just got Verizon to do a warranty replacement on my Xoom LTE. If someone can explain to me how to export that Rom when I get the replacement device I will post that for everyone to have a look.
I'm too stuck in this boat as well.
I received my Xoom after the LTE Upgrade and flashed the 'Stock 3.2.2' Rom and started having all the wifi issues. I thought I remembered my 3g working with this ROM but I honestly don't know if I'm remembering right.
Anyway, I tried going back to stock but obviously, no one has the actual latest build. When I received my Xoom back, I absolutely had the option of choosing LTE/CDMA and none of the images and ROMs floating around right now have that.
The problem I'm having now is my 3g doesn't work with ANY ROM or or image I've tried. This includes stock 3.0 and all the updates, the Stock 3.2.2 ROM, Tiamat, the image in this thread of the nandroid and the Pilot 3.2.2 image going around.
gordon12393 said:
I just applied this and no LTE/CDMA option.
Click to expand...
Click to collapse
I flashed this same file myself and I have it so I do not know what is going on with yours. We have to be missing something simple here.
gordon12393 said:
There is some version that the LTE devices ship back with labeled 3.2.2, but it does not look like what others have posted all over the net saying 3.2.2. Not sure what the deal is but I just got Verizon to do a warranty replacement on my Xoom LTE. If someone can explain to me how to export that Rom when I get the replacement device I will post that for everyone to have a look.
Click to expand...
Click to collapse
As far as I know there are 2 versions. HLK42B and HLK75C. Both for the same 3G/4G VZW Xoom's, one is just an earlier build from the pilot group from what I can tell. I do not know what other differences there are between them.
aldouse said:
i guess i should ask which rom did you flash from? did you go from the stock and rooted 3.2.2 rom from the dev thread? or from a complete stock factory image?
Click to expand...
Click to collapse
What ROM I flashed from is irrelevant, but it was the earlier HLK42B biuld I mentioned before which was infact stock/rooted 3.2.2 to these HLK75C 3.2.2 images.
hammer4203 said:
Does it have the lte/cdma with in networks? And do we need to have a custom recovery? If it is rooted can I go straight from stock 3.2.2?
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
It does on mine. Although after a factory reset it is having trouble connecting to 4G, I am working on that now, but it does still have the LTE/CDMA option.
Hey I just got updated to HLK75D. I am unrooted and locked, but if you want the files tell me how to get em and I will.
Sent from my Xoom using xda premium
I agree with AceXMachine's post above. I do believe that there is something wrong with my Xoom. The whole reason I'm having this ordeal is because I lost my 3G/4G connection all of a sudden and during troubleshooting with Verizon and Motorola things have gone down hill over the last 24 hours.
One question for AceXMachine I have is can you connect to 3G? I saw you posted you are having problems with 4G.
Same Problem with Connectivity as many
I sent my Xoom off for 4G upgrade and received it. Moto in its infinite wisdom sent me a new Xoom. So naturally, I started my Xoom and 3G/4G failed because I had a new MEID. Motor provided this new Xoom without syncing up with Verizon. So Verizon didn't have my MEID synced to my new 4G card. This explains the connectivity issues I had OOB.
I wish I new that before I went about a variety of flashing that failed in one way or the other. I did eventually get things to run with 3g/4g, and here s what I did.
1. Flash HRI66
2. Do a hard reset from Settings/Privacy
3. Reboot and fastboot flash recovery-Tiamat-R4c-100611-1150-cwm.img
4. Reboot into CWM and flash Android-HC-3.2.2-Stock+Rooted-1.1-SOLARNZ.zip
5. Flash HLK75C from this thread above as directed
Upon reboot both my WIFI and 3G/4G were restored.
When you reboot you should get prompted for HLK75D which is the market.
Peace & Joy
gordon12393 said:
I agree with AceXMachine's post above. I do believe that there is something wrong with my Xoom. The whole reason I'm having this ordeal is because I lost my 3G/4G connection all of a sudden and during troubleshooting with Verizon and Motorola things have gone down hill over the last 24 hours.
One question for AceXMachine I have is can you connect to 3G? I saw you posted you are having problems with 4G.
Click to expand...
Click to collapse
Sorry I missed your question. I lost 4G and 3G but it turns out it was because of a kernel I had installed and didn't realize it til later because I was using WiFi. Reflashed and I was good again until I tried installing that same kernel I was testing out...forget the name...Rogue/Arcturus or something.
AceXMachine said:
Sorry I missed your question. I lost 4G and 3G but it turns out it was because of a kernel I had installed and didn't realize it til later because I was using WiFi. Reflashed and I was good again until I tried installing that same kernel I was testing out...forget the name...Rogue/Arcturus or something.
Click to expand...
Click to collapse
I can confirm I had this same problem(Also flashed Rogue's Kernel and lost 3G/4G)! Thanks AceXMachine, you Images saves my bacon.
I just received my US 3G model Xoom back after having the LTE upgrade done and like an idiot, flashed the ROM below instead of just rooting the already installed 3.2.2 ROM
[ROM/UPDATE] Android Honeycomb 3.2.2 - Stock & Rooted
I'm experiencing the same Wifi issue a lot of other users are reporting so I've reverted back to the Stock image. My problem is I didn't root and nandroid before installing the ROM above so I can't get to 3.2.2. I can only get as far as 3.2 and then Android reports it's up to date.
Any ideas of how to get to 3.2.2 other than the ROM above? I'll buy a USB Host cable if I can find the proper .zip files to upgrade from 3.2.
mmayhew said:
I just received my US 3G model Xoom back after having the LTE upgrade done and like an idiot, flashed the ROM below instead of just rooting the already installed 3.2.2 ROM
[ROM/UPDATE] Android Honeycomb 3.2.2 - Stock & Rooted
I'm experiencing the same Wifi issue a lot of other users are reporting so I've reverted back to the Stock image. My problem is I didn't root and nandroid before installing the ROM above so I can't get to 3.2.2. I can only get as far as 3.2 and then Android reports it's up to date.
Any ideas of how to get to 3.2.2 other than the ROM above? I'll buy a USB Host cable if I can find the proper .zip files to upgrade from 3.2.
Click to expand...
Click to collapse
http://dl.dropbox.com/u/22648028/HLK42Bsystemboot4g.7z
That will get you to HLK42B which is 3.2.2. These are the boot and system images which you can flash thru fastboot, something you should be familiar with if you flashed back to stock images...works the same way. However, this the earlier version from the Pilot group which I was part of. Apparently the ones being sent out now are HLK75C or something like that. I am trying to find anyone with one of the recently updated Xooms that can dump the System/Boot images for me. Until then, these are better than nothing and will get you back up on 4G
AceXMachine said:
http://dl.dropbox.com/u/22648028/HLK42Bsystemboot4g.7z
That will get you to HLK42B which is 3.2.2. These are the boot and system images which you can flash thru fastboot, something you should be familiar with if you flashed back to stock images...works the same way. However, this the earlier version from the Pilot group which I was part of. Apparently the ones being sent out now are HLK75C or something like that. I am trying to find anyone with one of the recently updated Xooms that can dump the System/Boot images for me. Until then, these are better than nothing and will get you back up on 4G
Click to expand...
Click to collapse
Perfect, thanks a ton man. Is there a better place than the 'Xoom Android Development' XDA forums to look for the most recently dumped images?
mmayhew said:
Perfect, thanks a ton man. Is there a better place than the 'Xoom Android Development' XDA forums to look for the most recently dumped images?
Click to expand...
Click to collapse
Not that I know of at the moment. Trying to get someone to dump the new images for me. Also, forgot to mention, password for that 7zip is "solarnz"
AceXMachine said:
Not that I know of at the moment. Trying to get someone to dump the new images for me. Also, forgot to mention, password for that 7zip is "solarnz"
Click to expand...
Click to collapse
Thanks again. Up and running on the 3.2.2 build with no problems.
I took a nandroid after I unlocked the bootloader (which also does at least a factory reset). Can you use that?
Sent from my Xoom using Tapatalk
Unfortunately this did not work on my verizon xoom. I am still getting no internet connection even though it says 3.2.2 Initially it said the sim card was unknown, so I took it out and put it back in and did a reboot. It no longer gives that error, but I still don't get 3g or 4g.
Switch your network to cdma only and power down and back up. That will let it activate.
Sent from my Xoom using xda premium
I don't have the option for cdma only. Mine says home only and automatic. I don't have the LTE/CDMA option at all. I am on 3.2.2
Sent from my PG86100 using xda premium
short/y said:
I took a nandroid after I unlocked the bootloader (which also does at least a factory reset). Can you use that?
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Yes, that would be great.
Sent from my Xoom using XDA App
bathanr said:
I don't have the option for cdma only. Mine says home only and automatic. I don't have the LTE/CDMA option at all. I am on 3.2.2
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
I have this problem too. I can't get 3g/4g to work on any pre-3.2.2 image including this 'pilot' 3.2.2 image uploaded here. I can get 3g working with the ROM mentioned in my original post but wifi doesn't work.
Sent from my Xoom using XDA App
If you can create a link or pm me the backup as well that would be great
mmayhew said:
Yes, that would be great.
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
I've uploaded a Rogue Recovery backup to MEGAUPLOAD -- http://www.multiupload.com/BTA7S2DMPZ. Unzip everything and put the files in clockworkmod/backup/<some-name> either on your microSD card or your internal memory and then boot into recovery (again, I took it with Rogue Recovery V1.2) and do a restore.
I've verified that this is the stock 3.2.2 by inspecting system/build.prop in the system backup -- it says the version is HLK75C.
Sorry, guys, but today's an exceptionally busy day for me so I don't have the time to monitor this board and answer questions as to how to flash Rogue or whether it'll work with the standard CWM or any of that. Hopefully someone else can step up and help with those questions.
How do I dump the system? I will post it if I new how.
Sent from my Xoom using xda premium
short/y said:
I've uploaded a Rogue Recovery backup to MEGAUPLOAD -- http://www.multiupload.com/BTA7S2DMPZ. Unzip everything and put the files in clockworkmod/backup/<some-name> either on your microSD card or your internal memory and then boot into recovery (again, I took it with Rogue Recovery V1.2) and do a restore.
I've verified that this is the stock 3.2.2 by inspecting system/build.prop in the system backup -- it says the version is HLK75C.
Sorry, guys, but today's an exceptionally busy day for me so I don't have the time to monitor this board and answer questions as to how to flash Rogue or whether it'll work with the standard CWM or any of that. Hopefully someone else can step up and help with those questions.
Click to expand...
Click to collapse
Thanks again for the files. I updated to rogue recovery. I created a CWM folder on my SD card and did the restore. It restored fine. I boot up and it shows 3.2.2 and it also shows build version HLK75C. It still does not show 4G nor does it have the option under mobile network settings to choose LTE/CDMA. I have been on the phone with verizon and they have no clue. Motorola said tech level 3 will call me within 24-48 hours.
You need stock files to get that back. It should show lte/CD a in network settings. You could drive to a 4g area and it should activate.
Sent from my Xoom using xda premium
hammer4203 said:
How do I dump the system? I will post it if I new how.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
You need to flash the modded recovery, then in adb shell, run
mount /data
mkdir /data/media/Stock
dd if=/dev/block/platform/sdhci-tegra.3/by-name/system of=/data/media/Stock/system.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/boot of=/data/media/Stock/boot.img
sync
Then reboot and pull the files, should be in a "Stock" folder on the internal storage.
*Thanks to solarnz for these instructions
---------- Post added at 04:05 PM ---------- Previous post was at 04:00 PM ----------
bathanr said:
Thanks again for the files. I updated to rogue recovery. I created a CWM folder on my SD card and did the restore. It restored fine. I boot up and it shows 3.2.2 and it also shows build version HLK75C. It still does not show 4G nor does it have the option under mobile network settings to choose LTE/CDMA. I have been on the phone with verizon and they have no clue. Motorola said tech level 3 will call me within 24-48 hours.
Click to expand...
Click to collapse
You guys are wiping the cache and davlik after flashing right?
Is there a way to dump the img files without modding anything? I just sent my xoom out and will be receiving it completely void of any user information so I can do it at that time, but I really don't want to modify the recovery.
nubsors said:
Is there a way to dump the img files without modding anything? I just sent my xoom out and will be receiving it completely void of any user information so I can do it at that time, but I really don't want to modify the recovery.
Click to expand...
Click to collapse
I doubt it. Instructions I received specifically stated that the modded recovery would be needed. You can try unlocking it and running the commands to see but I doubt it will work. You could also try backing up the stock recovery using:
dd if=/dev/block/platform/sdhci-tegra.3/by-name/recovery of=/data/media/Stock/recovery.img
But I believe the modded recovery is what allows the device to be mounted. Wonder if this could be done via fastboot. I have to go to work or I would test it on my own Xoom. Will try later unless someone has already posted images by then.
Ok, I have pulled HLK75C images which should be flashable through fastboot thanks to short/y's Rogue CWM nandroid backup. Usual disclaimers apply here, don't try this unless you know what your doing, not my fault if something messes up. That being said, download images here: http://dl.dropbox.com/u/22648028/HLK75Csystemboot.7z zip password is "AceXMachine" without the quotes. After unpacking files go to the command prompt
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
It goes without saying that you need your xoom unlocked for this, need adb setup/working and may need to wipe data. I would do a nandroid backup of your current config before doing this. I was able to restore the "data" backup from a previous backup after restoring the "system" and "boot" from short/y's backup. Only problem I had was my market shortcut on the home screen had to be replaced since my "data" backup had the link to the older market. I rooted this before pulling these images so you should already have root when you flash this. I tested and have working WiFi and 4G with this setup. Feel free to ask questions or PM me if needed. Thanks again to short/y for his nandroid backup...even if he did make me load the Rogue recovery just so I could use it ;P
Hey all.
On the Verizon i815 tab we seem to have a modem and a separate LTE modem. In the OTA files the scripts always do a
write_firmware_image("/tmp/modem.bin")
and the LTE file gets pushed to /dev/block/mmcblk0p8.
Now the question is, WHERE does the write_firmware_image call flash the bin file and how can I extract it from a running and updated device?
Background: We have one user who by some weird coincidence got the ICS OTA update pushed from Verizon. Everyone else's update always fails (whole debacle can be found in different threads). We now managed to have this one user pull a clone copy of all of his partitions via dd if=/dev/block/mmcblk0pxx of=/sdcard/file_xx commands and pushing those into another tablet yields a working ICS with updated LTE modem but the "regular" baseband still shows the old version!!!
I need to know how this one successfully updated user can dump his modem.bin and where we need to flash this dd or using this proprietary write_firmware_image function, so that in the end everything is updated as if the OTA had worked in the first place ...
THANKS
Pershoot is the king with the 10.1 tab variants, maybe he he can shed some light.
Sent from my SCH-I815 using xda premium
Most devices will store the CDMA modem.bin in the nvram so it unfortunately cannot be dumped like a normal partition.
Perhaps the kernel drivers could be modified to extract it, though I've never looked into such things very far.
Sent from my SCH-I500 using xda app-developers app
jt1134 said:
Most devices will store the CDMA modem.bin in the nvram so it unfortunately cannot be dumped like a normal partition.
Perhaps the kernel drivers could be modified to extract it, though I've never looked into such things very far.
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
DAMN I kinda thought it would be something like this. Luckily I found a way to trick Verizon/Samsung's server to push the latest OTA to my tab where I was able to extract the needed modem.bin file. It's just a total pain in the behind, also because CWM can not flash the cdma part. For that we always need stock recovery and the latest stock recovery is of course locked, doesn't accept unsigned update files. *bastards* !!
electron73 said:
DAMN I kinda thought it would be something like this. Luckily I found a way to trick Verizon/Samsung's server to push the latest OTA to my tab where I was able to extract the needed modem.bin file. It's just a total pain in the behind, also because CWM can not flash the cdma part. For that we always need stock recovery and the latest stock recovery is of course locked, doesn't accept unsigned update files. *bastards* !!
Click to expand...
Click to collapse
This may be the first instance where Honeycomb is actually useful (the recovery part LOL)
electron73 said:
DAMN I kinda thought it would be something like this. Luckily I found a way to trick Verizon/Samsung's server to push the latest OTA to my tab where I was able to extract the needed modem.bin file. It's just a total pain in the behind, also because CWM can not flash the cdma part. For that we always need stock recovery and the latest stock recovery is of course locked, doesn't accept unsigned update files. *bastards* !!
Click to expand...
Click to collapse
Is the bootloader locked?
Sent from my SCH-I500 using xda app-developers app
jt1134 said:
Is the bootloader locked?
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
Yes of course. It's Verizon
electron73 said:
Yes of course. It's Verizon
Click to expand...
Click to collapse
Lame.
How were you guys using cwm then?
I may know of a solution even if the bootloaders are locked.
Sent from my SCH-I500 using xda app-developers app
jt1134 said:
Lame.
How were you guys using cwm then?
I may know of a solution even if the bootloaders are locked.
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
Well it seems like it's "half locked" then. The tab allows you to flash any recovery but nothing else. No kernel, no system fs. And they are locking it down further with every update. New ICS recovery won't flash unsigned zips anymore.
What solution do you have? Always interested in learning more about this stuff.
OK. I can probably help then. I'll post more details when I get home in a little bit.
Sent from my SCH-I500 using xda app-developers app
electron73 said:
New ICS recovery won't flash unsigned zips anymore.
Click to expand...
Click to collapse
Whoa...really? If we ever deliberately unroot, how would it ever be possible to restore it post-ICS? (I'm only aware of the recovery-injection method.)
Rodney
Oh Samsung....you never change...
Seems they're still using the same type of bootstrap initramfs as they have been for years. This allows unpacking and repacking of a kernel image
Linked below is a copy of the ICS recovery.img that has been repacked with the following changes:
* start adbd as root by default
* recovery keys replaced with 'test' keys
If this boots it should allow access to stock recovery with adbd, and should allow the stock recovery to flash unsigned zip packages. If so, you may create a zip package that can flash modem deltas (or tits).
DISCLAIMER: I don't even have this device, so I haven't tested anything. I came by this forum for other reasons. If it doesn't work or breaks something, then well, have a beer or something (though I see no reason it will break things even if it does not work as intended).
http://www.mediafire.com/?wnbr1v846yldl94
Flash with Odin or Heimdall, or whatever you folks are using for such things.
rhester72 said:
Whoa...really? If we ever deliberately unroot, how would it ever be possible to restore it post-ICS? (I'm only aware of the recovery-injection method.)
Rodney
Click to expand...
Click to collapse
It seems you can simply ODIN your CWM back on and then take it from there. As long as they don't close that hole at some point... Right now with the latest ICS version, even with stock recovery installed, this is still possible.
jt1134 said:
Oh Samsung....you never change...
Seems they're still using the same type of bootstrap initramfs as they have been for years. This allows unpacking and repacking of a kernel image
Linked below is a copy of the ICS recovery.img that has been repacked with the following changes:
* start adbd as root by default
* recovery keys replaced with 'test' keys
If this boots it should allow access to stock recovery with adbd, and should allow the stock recovery to flash unsigned zip packages. If so, you may create a zip package that can flash modem deltas (or tits).
DISCLAIMER: I don't even have this device, so I haven't tested anything. I came by this forum for other reasons. If it doesn't work or breaks something, then well, have a beer or something (though I see no reason it will break things even if it does not work as intended).
http://www.mediafire.com/?wnbr1v846yldl94
Flash with Odin or Heimdall, or whatever you folks are using for such things.
Click to expand...
Click to collapse
Awesome! Thanks for your help. Now of course I have a few questions and hope you can give me a quick rundown.
how do I unpack this img. I have linux and good knowledge of linux and unix tools. You say it's an initramfs? Is there a tutorial somewhere that explains how to unpack, modify and repack such a thing? And where do I make the changes if I were to do it myself with *our* ICS recovery?
I believe I can't just flash this one as there are big differences between the international versions and our LTE version of the Tab 7.7
The partition table is different etc. I don't want to use this and end up screwing my stuff up. I'd rather take the original one that came with our ROM and modify it myself.
You don't happen to also know how to unlock the bootloader so that we could just flash a rom with ODIN ?
The recovery I posted is a modified version of the one that asenduk posted in the other ICS thread. When I get to a PC later I'll post a link to the tools that I used to modify it. Its pretty straightforward.
As far as unlocking the bootloader, that's above my pay grade. Perhaps kexec would be a useful thing to look into?
Sent from my SCH-I500 using xda app-developers app
I think maybe we could start a donation for Mr JT to get the i815?
If he's interested yeah?
He's done many marvelous things!!
repack scripts : https://github.com/project-voodoo/kernel_repack_utils
toolchain : http://www.codesourcery.com/public/...-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
use extracter.sh to unpack the image into a folder, edit to taste, then use repacker.sh to put it back together.
make sure to use gzip compression when repacking.
jt1134 said:
The recovery I posted is a modified version of the one that asenduk posted in the other ICS thread. When I get to a PC later I'll post a link to the tools that I used to modify it. Its pretty straightforward.
As far as unlocking the bootloader, that's above my pay grade. Perhaps kexec would be a useful thing to look into?
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
You say it has a locked bootloader, but we have CM10 which uses a custom kernel...
okashira said:
You say it has a locked bootloader, but we have CM10 which uses a custom kernel...
Click to expand...
Click to collapse
Well... Bootloaders I have never really looked into.. I am still unable to flash a kernel or a factory fs with ODIN. Odin only lets me flash the recovery. So something is locked there. Maybe not crazy-locked like the motorola razr phones but also not completely open like the AT&T Galaxy Note was... Maybe someone with a little more experience in this stuff can shed some light
jt1134 said:
repack scripts : https://github.com/project-voodoo/kernel_repack_utils
toolchain : http://www.codesourcery.com/public/...-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
use extracter.sh to unpack the image into a folder, edit to taste, then use repacker.sh to put it back together.
make sure to use gzip compression when repacking.
Click to expand...
Click to collapse
Cool! Thanks for the links. Will look at the stuff and see if I can figure it out
i have the VZW G2 (VS-980) and its stuck in fastboot mode. ive tried all the different methods listed in these forums and nothing has worked. i cant get into download mode as everytime i try, download mode shows for a second then goes into fastboot mode again. PLEASE HELP!!
simon_lefisch said:
i have the VZW G2 (VS-980) and its stuck in fastboot mode. ive tried all the different methods listed in these forums and nothing has worked. i cant get into download mode as everytime i try, download mode shows for a second then goes into fastboot mode again. PLEASE HELP!!
Click to expand...
Click to collapse
How the hell did you brick it? Give us some more background on what tweaks, root methods, flashing recovery methods did you use or else its hard to diagnose the issue.
ericdabbs said:
How the hell did you brick it? Give us some more background on what tweaks, root methods, flashing recovery methods did you use or else its hard to diagnose the issue.
Click to expand...
Click to collapse
ok. i was on stock. rooted with the IO method. wanted to flash a ROM (clean rom). downloaded ROM, wipe dalvik/cache/data. after reboot, phone booted into recovery mode. tried going into download mode to revert back to stock and LG FlashTool failed. said phone was the wrong model number (D802). the ROM i Downloaded said it was for VZW G2. obviously it wasnt. so i finally ended up using fastboot to push boot image and it booted, but in about phone, it says it D802 model (i just got it to boot, where as before i was stuck in fastboot mode). now i need to return to stock, but dont know how. any ideas?
Check out this thread:
http://forum.xda-developers.com/showthread.php?t=2517649&highlight=bricked
Gnarfsan said:
Check out this thread:
http://forum.xda-developers.com/showthread.php?t=2517649&highlight=bricked
Click to expand...
Click to collapse
well, i actually was able to restore a backup i had of my stock rom and that fixed the model number prob, however now i cant get into download mode so i can do a reflash :/
simon_lefisch said:
well, i actually was able to restore a backup i had of my stock rom and that fixed the model number prob, however now i cant get into download mode so i can do a reflash :/
Click to expand...
Click to collapse
Even following the steps posted in that thread?
Gnarfsan said:
Even following the steps posted in that thread?
Click to expand...
Click to collapse
yes. not sure why its doing that. is there any way that download mode can be deleted from the phone? also, how do you get into fastboot mode?
EDIT: nevermind. i finally got it into download mode!! (thank god!!) flashing right now. damn that was a pain in the ass. i was starting to freak out that i messed up my phone. this is my first LG phone so this process is a little new to me (been on moto for the last few years) thanks for trying to help me out. this was def a learning experience.
Phew, I'm glad to hear that. Some day I will be in the same situation
Sent from my LG-D802 using XDA Premium 4 mobile app
Just a quick question. Why would you even need to go into download mode to flash a Rom? Never once have I done that. Really, just curious.
Thanks Devs. From my VZW G2.
trickster2369 said:
Just a quick question. Why would you even need to go into download mode to flash a Rom? Never once have I done that. Really, just curious.
Thanks Devs. From my VZW G2.
Click to expand...
Click to collapse
I was thinking the same thing. It's best to stay out of those modes. Get a recovery installed ASAP and do everything that you need to do from there. I recommend TWRP Recovery.
Sent from my LG-D802 using XDA Premium 4 mobile app
Maybe because when flashing stock rom download mode is needed (atleast in my old sammy phone, maybe same in moto phones)
What's wrong with restoring the backup of the stock rom that should have been made before wiping and flashing a different rom? Not sure what I'm missing here.
Sent from my Nexus 10 using XDA Premium HD app
Download mode is useful to flash the entire phone back to stock using the OEM tools. It's not just for the stock ROM. It's everything. It's useful if you get a bit carried away in TWRP and wipe partitions you really shouldn't be touching. Or if you somehow manage to bork your recovery, or at least can't get into it. It's also good if you want your phone to be completely stock to sell it or to send it in on warranty. I'm sure someone could come up with other scenarios where it's useful.
But yes, it is a good idea to keep a backup of your stock ROM. And as always, know what you're flashing, make sure it's for your phone and check md5s. And be mindful of what you're doing in recovery. You should be able to avoid most issues. Download mode is indeed something you shouldn't be using often but as I said above there are situations where it is useful or necessary. It's actually something I suggest you know how to use. I say it's always a good idea to know how to get back to complete stock for warranty stuff, selling, or if something just goes majorly wrong.
The Rom I was trying to flash was apparently for a different model number, yet it was under the Verizon thread. There was no md5 to cross reference. In the end I ended up finding the proper boot image/twrp files and pushed them via fastboot (since I was unable to use adb) which then allowed more to restore a backup of the original Rom. Just took me all night to finally get back to stock. Then I decided to restore to out-of-the-box stock just to make sure all files weren't corrupted our anything.
Sent from my VS980 4G using Tapatalk
Not for nothing, but I ran the LG flash tool without putting the phone in download mode and it worked fine.
Semantics said:
Not for nothing, but I ran the LG flash tool without putting the phone in download mode and it worked fine.
Click to expand...
Click to collapse
Hmm.....interesting. I may try that next time I have to flash to stock.
Sent from my VS980 4G using Tapatalk
Same Problem
simon_lefisch said:
The Rom I was trying to flash was apparently for a different model number, yet it was under the Verizon thread. There was no md5 to cross reference. In the end I ended up finding the proper boot image/twrp files and pushed them via fastboot (since I was unable to use adb) which then allowed more to restore a backup of the original Rom. Just took me all night to finally get back to stock. Then I decided to restore to out-of-the-box stock just to make sure all files weren't corrupted our anything.
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Can you fill me in on how you used fastboot to install twrp? I am in the same boat right now...
i'm stuck as well in Fastboot and can't figure it out
emmur0 said:
i'm stuck as well in Fastboot and can't figure it out
Click to expand...
Click to collapse
I sent you a pm
You can you adb side load which is the same for flashing rom, pushing, or pulling file from the phone which is the first thing to learn before flashing anything to the new device that you got and know nothing about.
Sent from my LG-LS980 using xda premium