Database Users

Cellular South Hero problems after 2.1 update

Hi all! I'm new to the forum AND somewhat new to Android
anyway.. I recently updated my Cellular South CDMA Hero (1.5) to 2.1 via the RUU on the Cellular South website, following all instructions carefully.
Now, after the update, my phone will reboot almost like clockwork whenever it is left in sleep mode for more than ~30 seconds. This happens ONLY when it's unplugged or plugged into a car charger.
I've restored to factory settings, re-flashed the stock RUU, rooted and applied hexskrew's new CS-only ROM... each of the aforementioned steps were taken, multiple times.. I even reformatted my sd card ...
I don't know what to do.. I'm planning to take it to the shop soon in hopes of getting it replaced (I doubt they have troubleshooting steps for THIS problem). I've tried everything. What gives? Please help! Thanks in advance (reply if you have had similar problems)

self-bump! lol sorry... but I'm desperate at this point..
Anyway.... also, does it matter that I'm using Win7 for all this? I know that with Vista, for example, certain compatibility issues arise. Could it be that adb is not connected just right because of such incompatibility? would I have more luck with Terminal or something?

OB1canOB said:
self-bump! lol sorry... but I'm desperate at this point..
Anyway.... also, does it matter that I'm using Win7 for all this? I know that with Vista, for example, certain compatibility issues arise. Could it be that adb is not connected just right because of such incompatibility? would I have more luck with Terminal or something?
Click to expand...
Click to collapse
I used 7 to update mine and it went fine. Not sure what could be wrong with yours. Were you already rooted when you upgraded or still on stock 1.5?

it was stock 1.5

Yeah. I flashed DangerRom, and now it works just fine. Thanks, MrDanger!

[Q] OTA 2.2.1 update manually

I am looking to download and installed 2.2.1 on my MT4G but I can't find a download link anywhere. I can only find 2.2. It tried to do a OTA but when it rebooted it never installed and when I pulled the battery an hour later it deleted the update on boot. I've performed *#*#checkin#*#* and it said succeeded but I still haven't had an update since. I don't want a custom ROM on this phone for a while since it's under warranty. I have a MT3G for that...
BTW, I did use the search feature for who ever was going to say use it, I even used this thing call Google. It was quite fascinating!

remijenkins said:
I am looking to download and installed 2.2.1 on my MT4G but I can't find a download link anywhere. I can only find 2.2. It tried to do a OTA but when it rebooted it never installed and when I pulled the battery an hour later it deleted the update on boot. I've performed *#*#checkin#*#* and it said succeeded but I still haven't had an update since. I don't want a custom ROM on this phone for a while since it's under warranty. I have a MT3G for that...
BTW, I did use the search feature for who ever was going to say use it, I even used this thing call Google. It was quite fascinating!
Click to expand...
Click to collapse
Call T-Mobile customer service and verify with them that the IMEI number they have in your account is the correct one. This is the number one reason for not getting the update. I had a phone for over a month and they never changed the IMIE # until I called. The IMEI is on your box or under your battery.

Please post questions in the Q&A section.

remijenkins said:
I am looking to download and installed 2.2.1 on my MT4G but I can't find a download link anywhere. I can only find 2.2. It tried to do a OTA but when it rebooted it never installed and when I pulled the battery an hour later it deleted the update on boot. I've performed *#*#checkin#*#* and it said succeeded but I still haven't had an update since. I don't want a custom ROM on this phone for a while since it's under warranty. I have a MT3G for that...
BTW, I did use the search feature for who ever was going to say use it, I even used this thing call Google. It was quite fascinating!
Click to expand...
Click to collapse
[GUIDE] Forcing update 2.2.1 and re-rooting after downgrading This was on the same page you posted.... have you by chance read it?

I'd recomend using the force method...I spent almost three weeks waiting on it after being put on a "push list", verifying IMEI, and other things. Some phones "won't update" for whatever reason and they will eventually tell you to swap it. I did the manual update from the thread linked above without issue after T-Mo was unable to resolve my issue and I wasn't willing to swap for a potential refurb after having to pay full $450 retail price on the phone.

I actually did read the post about forcing the update about I don't want to have to root my phone or turn S off. I'm wanting to leave it 100% stock. The forcing the update post mentions that wifi stops working when you update and that you have to do some stuff to get it working. I actually spent almost 2 hours on the phone with CS for Tmobile and at the very end they told me that they can't push an update, that I can only do the checkin option which has been done. Most of my time was spent on hold. That's why I'm just looking for someone who happens to have a copy of the update that I can copy to what ever folder is needed to get my phone to update. They did mention it can be at the end of the push out by Google before I get another chance to update which is several months of bugs to deal with.

remijenkins said:
I actually did read the post about forcing the update about I don't want to have to root my phone or turn S off. I'm wanting to leave it 100% stock. The forcing the update post mentions that wifi stops working when you update and that you have to do some stuff to get it working. I actually spent almost 2 hours on the phone with CS for Tmobile and at the very end they told me that they can't push an update, that I can only do the checkin option which has been done. Most of my time was spent on hold. That's why I'm just looking for someone who happens to have a copy of the update that I can copy to what ever folder is needed to get my phone to update. They did mention it can be at the end of the push out by Google before I get another chance to update which is several months of bugs to deal with.
Click to expand...
Click to collapse
THE update is in the post... if you want to try and copy it to every folder on your phone fine... try it... but it is in that post
and if you want you could turn s-off to flash it then turn s-on when you're done... and you won't be rooted after the update applies so you won't have to unroot

If that is the update then why does wifi stop working when you flash it? And how are you suppose to get it working again after it stops?

remijenkins said:
If that is the update then why does wifi stop working when you flash it? And how are you suppose to get it working again after it stops?
Click to expand...
Click to collapse
there is more than one file posted there... The one named "PD15IMG.zip" is part of the update. It replaces the kernel and some other system files, but does not include the patches from the update, which is why wifi breaks. The one labeled The OTA is the full OTA pulled from a phone and the filename is "update.zip" I could not get the full update to flash with S-ON because it has to do some commands on the system to let it know it's going to flash becuase the phone temporarily disables the write through in place... (not sure if i explained that right). My solution is to flash the partial update which gets your kernel up to date then patch the kernel (turning s-off) and then flashing the entire update. If you're really against root you can undo all the root stuff and S-Off after the update hits... but what's wrong with root? You should still get new updates if you're still running stock, but are rooted. BUT, if you uninstall programs the updates will most likely not take (I recommend a nandroid be made before removing things so you can flash back to it get the update, make a new nandroid, then reremove software.)

Well I was actually concidering rooting updating and unrooting when my phone goes, "downloading new firmware"... It's amazing how you ***** and moan to Tmobile and things just happen. :: shrugs :: I'm happy, now I wish they would let me remove bloatware without rooting.

remijenkins said:
Well I was actually concidering rooting updating and unrooting when my phone goes, "downloading new firmware"... It's amazing how you ***** and moan to Tmobile and things just happen. :: shrugs :: I'm happy, now I wish they would let me remove bloatware without rooting.
Click to expand...
Click to collapse
Why the aversion to rooting? it's really not that hard and there are at least 4 or 5 of us in irc that will walk you through it

Rooting is nasty
The problem with the description of the method for manual install of 2.2.1 is that it is misleading; the author said HIS WiFi stopped working after installing PD15IMG but should have said from the start that PD15IMG is only part of the OTA; that EVERYBODY's WiFi would stop working after installing PD15IMG; and that the entire following process is required to get to 2.2.1 if all you want is an unrooted phone with 2.2.1:
Flash PD15IMG-->temporary root-->permanent root (lot of jibberish)-->flash rest of update-->unroot
This is an intimidating process which is nowhere given in simple and complete steps but yet is often described as "simple" or "took minutes." Maybe for some, but the "simple" suckers in a lot of people who stumble along the way.
As I did; all I wanted was an unrooted phone with 2.2.1 and I had given TMo a couple of weeks to do it. A few hours into the process and a few steps beyond trashing WiFi I realized I didn't want a rooted phone and decided either to pay somebody who knows a lot more about this subject than I do to fix it or, preferably to convince TMo to give me a new one. So I went to sleep.
And guess what? At 6AM TMo said they wanted to do a firmware update, to which I agreed, and the legit OTA over-rode that damned PD15IMG and cajoled my WiFi back to life. And as far as I know Tmo doesn't have my IMEI either, because they say on their site they don't know what kind of phone I have.
And none of that snarky "if you don't know what we're talking about you shouldn't be here," either. If she didn't know she could get pregnant from it she shouldn't have done it. The whole rooting business is nasty: there are no simple comprehensive directions, there are too many ROMs and there is too little honest description of where they fail.
It would be nice also if Google would save up its incremental improvements and let them loose at longer intervals, as Apple does, to reduce the frustration of those interested in Being First. It would also be nice if the Google open system had required carriers to be able to absorb the latest updates within a fixed time, regardless of whatever crud they lay over the basic Android. The software may be "open" as far as Google and Tmo are concerned, but between TMo and me the relationship is different.

ecdy said:
The problem with the description of the method for manual install of 2.2.1 is that it is misleading; the author said HIS WiFi stopped working after installing PD15IMG but should have said from the start that PD15IMG is only part of the OTA; that EVERYBODY's WiFi would stop working after installing PD15IMG; and that the entire following process is required to get to 2.2.1 if all you want is an unrooted phone with 2.2.1:
Click to expand...
Click to collapse
I'm sorry you had problems, but when doing anything that has a set of instructions it is wise to read the entire thing before starting. This will ensure you are fully prepared instead of lost in the sauce halfway through... Piss Poor Planning leads to Piss Poor Performance.

To almost bricked and back on US Cellular version

Thought I'd share my experience in case it would help anyone.
Got a good deal on a new used US Cellular version tab. Hadn't come here yet to check things figuring all tabs would be the same.... wrong obviously.
First, because not everyone necessarily clearly mentions the difference between the GSM and CDMA versions, I almost went down the wrong path and tried to load a GSM rom. Caught that luckily in time. Rooting sucked as Kies would not, with 6 different computers and just as many different versions of Kies, recognize my device. Luckily I stumbled on the Z4root app which worked great.
All is good, but of course, no one mentions the us cellular version at all when it comes to roms. Studied up and noticed the model numbers and specs between us cellular version and verizon version matched. Great. Loaded beta clockwork mod for verizon, but only the stock recovery would come up when I tried to get into recovery.
Decided to load the voodoo kernal for cdma verizon. This is where it got ugly. Wouldn't convert partition to ext4 and just sat there. Took creators advice and booted into recovery. Suprisingly, it now went to the clockwork mod recovery, but nothing I did there helped, so I rebooted into recovery from clockwork mod recovery as per the instructions so I could do a data wipe and factory reset. Not all I had was a boot loop and it would no longer even go into recovery. Pretty sure I was screwed at this point. Only thing I had going for me was that I could still get into download mode. Got lucky and found the files necessary to go to bone stock verizon vie heimdall. Loaded them up and rebooted. A little hairy, but then I had a running system again. Since I knew I could always redo that, I decided to load the voodoo kernal again and this time it worked (maybe because my system was now basically verizon???).
Anyways, if anyone needs the files to go back to stock, I do have them and would be more than willing to share. I know one thing, if it wasn't for the wealth of information here I would have a bricked tab right now.

So I just bought a used US Cellular tab and wish I'd understood there would be issues.
I just rooted via z4Root as well and now don't know what to do. Were you able to flash any ROMs after getting into recovery? I'd imagine Verizon Roms might work?
I don't care about cellular data as I'm using it as wifi only.

Would you be kind enough to share the stock rom you mentioned? I've run into problems restoring my US Cellular GT. Thanks!

This is the exact same thing that happened to me as well except that I have a vzw tab.
I used sgs kernal to flash which went successful then tried to load a rom through cwm and got stuck in the boot screen.
I was able to go into download mode but had no idea how to use heimdall nor did I know what files I needed.
Luckly I bought through vzw 13 days ago so I just went in and exhanged it.
Wanna try again but would like to have the stock files needed to restore my tab in case I soft brick it again.
Can you please email me the files to [email protected]???

Yes please share the stock files

I would also like to request stock file as well. Thanks!!!!

Can anyone share the 4G LTE system/boot dump?

I tried to use the rooted 3.2.2 rom that was listed under development, but I could never get my wifi to connect. Now I am unable to get my 4G to work. I used to have the option to choose preferred network mode LTE/CDMA, but now that no longer shows. I am on 3.2.2 using build HLK42B.
I was wondering if someone who received their xoom back from the upgrade has the latest image I can try.

Tell me how to dump it. Never done it before. I am n stock 3.2.2 fresh back from the upgrade.
Sent from my Xoom using xda premium

I wish I knew.. I will have to research that.
Sent from my PG86100 using xda premium

I just posted an upload link over at http://forum.xda-developers.com/showpost.php?p=18204881&postcount=13

hammer4203 said:
Tell me how to dump it. Never done it before. I am n stock 3.2.2 fresh back from the upgrade.
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

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

4G LTE
I got my Xoom back some time ago. I've been waiting to root it until it came back. (Really didn't want to go through it, and have to undo it just to figure out how to do it again)
I'm trying to find the official file from Moto for the HLK42B build that came back on my 4G Xoom. I'm on the Moto Dev site, but they only have up through the 3G upgrade listed. Anybody know where I can get the official file in case anything goes wrong? I want to make sure I have it, before I start.
Thanks

Thanks Ace, it worked for me. It wasn't rooted because I imediately got and updated to HLK57D

AceXMachine said:
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
Click to expand...
Click to collapse
Thanks for the img files. They will save many headaches for a lot of people.
It is a damn shame that Motorola will not post the updated img files though...

I've tried both Ace and Shorty's backups. They seem to work restore fine but I still can't get any 3G/4G data. I've tried both HLK75C and D. I've done many factory resets and cache wipes. I had VZW send me a new SIM card which they manually activated while I was on the phone with them and according to their end they can see my Xoom contacting the tower but there is no activity beyond that. I really never believed that was the problem since I was able to swap SIMs with my Bionic and the Bionic worked great with the Xoom's SIM (but not the other way around of course).
I'm still suspicious about the radio Baseband version. I am missing the second "ltedc_u_05.19.00" that I've seen in HLK75C screen shots and I don't have the option to select a network mode under Mobile network settings that I know needs to be checked. This makes me think my Xoom's hardware is ok since it is able to talk with the tower over the 4G modem for activation, however the OS software is not able to select the 4G radio for actual system use. Are the radio files built into the system or boot images? Where do the baseband versions listed in About tablet come from and how might these be backed up/restored? I've never really bothered flashing radios before so this part of the process is new to me. I'm really hoping this can be solved without having to return the device to Moto.

zarkuu said:
I've tried both Ace and Shorty's backups. They seem to work restore fine but I still can't get any 3G/4G data. I've tried both HLK75C and D. I've done many factory resets and cache wipes. I had VZW send me a new SIM card which they manually activated while I was on the phone with them and according to their end they can see my Xoom contacting the tower but there is no activity beyond that. I really never believed that was the problem since I was able to swap SIMs with my Bionic and the Bionic worked great with the Xoom's SIM (but not the other way around of course).
I'm still suspicious about the radio Baseband version. I am missing the second "ltedc_u_05.19.00" that I've seen in HLK75C screen shots and I don't have the option to select a network mode under Mobile network settings that I know needs to be checked. This makes me think my Xoom's hardware is ok since it is able to talk with the tower over the 4G modem for activation, however the OS software is not able to select the 4G radio for actual system use. Are the radio files built into the system or boot images? Where do the baseband versions listed in About tablet come from and how might these be backed up/restored? I've never really bothered flashing radios before so this part of the process is new to me. I'm really hoping this can be solved without having to return the device to Moto.
Click to expand...
Click to collapse
This is my same exact problem. Can't seem to figure out the baseband problem.
I wonder if anyone has contacted Motorola regarding a way to flash the baseband to the LTE 4G version?

Hey guys. Been going through the same ****. The MEID/ESN changes with LTE upgrade. Adds a 01 or 02 to the end of the ESN. If you downgraded and took updates, it modified your baseband, taking out the LTE part of it. If you go back to HRI66 and do the CDMA activation thingy, you should be able to re-activate on 3G. Yeah, it sucks, but what else can we do? We need that OTA to re-flash the LTE baseband.

You can get the hlk75c which is rooted then take the hlk75d update and reroot using the universal root method. That will put you back.
Sent from my ADR6400L using xda premium

Jewremy said:
Hey guys. Been going through the same ****. The MEID/ESN changes with LTE upgrade. Adds a 01 or 02 to the end of the ESN. If you downgraded and took updates, it modified your baseband, taking out the LTE part of it. If you go back to HRI66 and do the CDMA activation thingy, you should be able to re-activate on 3G. Yeah, it sucks, but what else can we do? We need that OTA to re-flash the LTE baseband.
Click to expand...
Click to collapse
Oh, duh, it's so simple. I'll definitely be trying this when I get home from work today.
If it works - you will be my savior.
Scratch that - it didn't even reactivate my 3G.

Jewremy said:
Hey guys. Been going through the same ****. The MEID/ESN changes with LTE upgrade. Adds a 01 or 02 to the end of the ESN. If you downgraded and took updates, it modified your baseband, taking out the LTE part of it. If you go back to HRI66 and do the CDMA activation thingy, you should be able to re-activate on 3G. Yeah, it sucks, but what else can we do? We need that OTA to re-flash the LTE baseband.
Click to expand...
Click to collapse
I don't think that will work unless you open it up and physically remove the LTE modem. my understanding is once the LTE modem was installed the internal 3g modem is deactivated. Even if this did work it would deactivate your SIM card so you wouldn't be able to use LTE in the future without getting a new one. I had the idea to switch my currently useless Xoom data plan over to my old OG Droid and then wifi tether. I asked VZW about switching and found I *could* do this but going from a 4g device back to 3g would deactivate the SIM card and I won't be able to switch without getting a new one. Too much trouble in my opinion.
I spent about 2 hours in a Verizon store yesterday after 2 hours on the phone the previous night and eventually ended up with an RMA with Motorola. I'll be returning it to them and hopefully it will come back correct in about a week. Such a hassle when I could probably flash this myself if I had the right files but at this point I don't know what else to try.

Can you repost link please. I am trying to get this on a Mac running OSX and I cant seem to unzip the file. Any suggestions?! PLease HELP!!!
---------- Post added at 09:22 PM ---------- Previous post was at 09:09 PM ----------
how do you unzip HLK75Csystemboot.7z on Mac OSX??? Please Help!!!

download 7zip or use winrar

Jewremy said:
Hey guys. Been going through the same ****. The MEID/ESN changes with LTE upgrade. Adds a 01 or 02 to the end of the ESN. If you downgraded and took updates, it modified your baseband, taking out the LTE part of it. If you go back to HRI66 and do the CDMA activation thingy, you should be able to re-activate on 3G. Yeah, it sucks, but what else can we do? We need that OTA to re-flash the LTE baseband.
Click to expand...
Click to collapse
This does not work I've tried it a bunch of times in different fashions. I even flashed 3.2.2 then flashed the official recovery took the next update and nothing. Actually its been said that HRI66 over rights stuff that we need. Take that with a grain of salt.

zone23 said:
This does not work I've tried it a bunch of times in different fashions. I even flashed 3.2.2 then flashed the official recovery took the next update and nothing. Actually its been said that HRI66 over rights stuff that we need. Take that with a grain of salt.
Click to expand...
Click to collapse
Yeah, it does. The radios are in the bootloader, aka mmcblk1p1, aka the ebb partition.
Theoretically, we should be able to get a dump of the post-upgrade bootloader, dd it over our borked bootloaders and have it working. Problem is, getting that dump and figuring out how to do the flash. We definitely don't want to do it in a powered up system...that leaves recovery or fastboot.

Jewremy said:
Yeah, it does. The radios are in the bootloader, aka mmcblk1p1, aka the ebb partition.
Theoretically, we should be able to get a dump of the post-upgrade bootloader, dd it over our borked bootloaders and have it working. Problem is, getting that dump and figuring out how to do the flash. We definitely don't want to do it in a powered up system...that leaves recovery or fastboot.
Click to expand...
Click to collapse
It restores your device but it will not bring back 3G/4G. If it does please tell me how because I've flashed it a few times and it did not bring back 3G.
Actually in reading your post a few times you say it yourself that its a borked bootloader. Flashing HRI66 will not fix this. If it did we would be finished and we could close this thread.

[Q] 3G absolutely unattainable?

So, I have done everything in my power to get 3G to work with the GBretail sbf.
I have tried the update zips using clockwork. I have tried using baseband switcher. I have swapped the bp_nvm_default files manually via adb. The last method seems to be most effective, only because it makes the phone unable to boot. The other methods simply do nothing.
i would really like data on this phone,without using the crap (and I mean crap) stock US tmo build.
help??
my struggle with swapping the ~/bp_... files can be seen at this thread. http://forum.xda-developers.com/showthread.php?t=1977819
Thanks.

Where are you? Maybe you have a US Defy, which has different freqs than the euro version? that could by why you don't have 3g?