Related
I upgraded to the leaked Gingerbread ROM, but wanted to downgrade due to the bugs. When I downgraded to ED1 in Odin, it worked, but I got the "baseband unknown" problem. I tried everything: using PST to flash ED1, ED2 and even EG2, but it wouldn't work. Here's the problem:
When flashing, everything runs OK in both Odin and PST until it's time to flash cp_modem.bin. At that point the phone displays the following:
Wait, VIA Booting ..
VIA rest done. ..
Downloading to VIA...
That's where it stops. Nothing happens at all. I even tried a system restore to before I installed the VIA drivers, tried it, installed the VIA drivers and tried it again...it didn't help.
Can anyone please help me?
This post has all the info and links to flash back to a factory stock state. It worked for me.
http://www.mydroidworld.com/forums/...harge-full-factory-tar-flashing-software.html
apascual89 said:
This post has all the info and links to flash back to a factory stock state. It worked for me.
http://www.mydroidworld.com/forums/...harge-full-factory-tar-flashing-software.html
Click to expand...
Click to collapse
Thanks, but I tried that exhaustively. It keeps hanging at the end where it tries to flash t modem. Did you have any trouble there?
No I had some issues getting pst going, but once it started, it went thru. Are you flashing with the battery in?
Did you remove the Sim card?
apascual89 said:
No I had some issues getting pst going, but once it started, it went thru. Are you flashing with the battery in?
Did you remove the Sim card?
Click to expand...
Click to collapse
Yes, battery in and SIM card out. I put the battery back in after putting it in download mode because it will fail otherwise.
Any word? I seem to be having the same probelm.
Hi,
The release of the stable CM7.1 really encouraged me to finally S-OFF my phone and install it. I used Revolutionary 0.4pre4, and installed CWM 5.0.20. I wiped everything (data, system, cache, dalvik, you name it), and installed the CM7.1 update zip and right afterwards the new Google apps zip. Eventually, I used Fix Permissions, and rebooted.
I was quite happy, until I saw the com.android.phone FC message. It just showed the same message over and over. I updated my radio to the latest version, to no avail. I tried reformatting, re-wiping, reinstalling quite a few times, and I even tried 3 different sim cards. I finally decided to go back to RUU (kept S-OFF), and didn't get any FCs.
I'm really frustrated, since it is my first Android phone, and I really believe I tried everything already.
Thanks in advance.
I got no problem at all until now.
Another thing I've discovered is when I get these FCs, sometimes if I enable the bluetooth, the phone suddenly discovers the network and the FCs stop. That's just very odd, to me.
I really hope that's not a problem with my phone (especially since it does work properly with RUU).
foouser said:
Hi,
The release of the stable CM7.1 really encouraged me to finally S-OFF my phone and install it. I used Revolutionary 0.4pre4, and installed CWM 5.0.20. I wiped everything (data, system, cache, dalvik, you name it), and installed the CM7.1 update zip and right afterwards the new Google apps zip. Eventually, I used Fix Permissions, and rebooted.
I was quite happy, until I saw the com.android.phone FC message. It just showed the same message over and over. I updated my radio to the latest version, to no avail. I tried reformatting, re-wiping, reinstalling quite a few times, and I even tried 3 different sim cards. I finally decided to go back to RUU (kept S-OFF), and didn't get any FCs.
I'm really frustrated, since it is my first Android phone, and I really believe I tried everything already.
Thanks in advance.
Click to expand...
Click to collapse
Nothing has ever broken my phone quite as much as when I have done the 'fix permissions' thing. Totally screwed my phone and was FC city. I've never done it since, and never had any problems since. Try going back over your steps and leave out the fix permissions part!
I recently had a quick go with CM7 nightlies and had no issues. This included the last nightly before it became stable which was very close to the stable version.
wnp_79 said:
Nothing has ever broken my phone quite as much as when I have done the 'fix permissions' thing. Totally screwed my phone and was FC city. I've never done it since, and never had any problems since. Try going back over your steps and leave out the fix permissions part!
I recently had a quick go with CM7 nightlies and had no issues. This included the last nightly before it became stable which was very close to the stable version.
Click to expand...
Click to collapse
Tried doing the same process without fixing permissions, twice already, and I still get the same problem.
have you tried this?
http://forum.xda-developers.com/showpost.php?p=18309360&postcount=9
Helped with the market issue, but not yet with the com.android.phone FC...
foouser said:
Helped with the market issue, but not yet with the com.android.phone FC...
Click to expand...
Click to collapse
Odd. Here is how I did mine, step-by-step. (Do a NANDroid backup before this, and copy it to your PC/Mac.)
1. Install latest 4EXTRecovery from here: http://forum.xda-developers.com/showthread.php?t=1130004
2. Use this to format all partitions to EXT4. (Not sure if you are using EXT3, not sure if it matters, just saying I'm on EXT4 formatting with no issues.)
3. Do the full wipe & manual format routine (including boot) again just in case!
4. Flashed CM7.
5. Flashed Gapps.
6. Flashed Tiamat kernel (1.1.4)
7. Reboot.
I'm used the same radio as in my sig but also doubt that matters. Not sure what else to suggest. Try downloading the ROM again, and compare the MD5 of your two downloads.
Wow, I believe I'm in some big trouble now. I decided to try and get my phone replaced in the store since I just recently bought it. I used this guide: http://forum.xda-developers.com/showpost.php?p=17481836&postcount=2 to get back to S-ON, but when I tried to flash back the RUU, I get a CUSTOMER ID ERROR and the flash fails.
I've tried two RUUs: RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed
RUU_Saga_hTC_Asia_WWE_1.48.707.1_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199476_signed
But they both end up the same way. I'm now stuck on the HBOOT screen with S-ON and a big purple security warning (I guess since CM7 is still on the /system partition).
Any help?
Try solution 2 of this guide http://forum.xda-developers.com/showthread.php?t=1284196
but replace the mmc....
With
mmcblk0p25
this will format your system partition,
maybe also data could be formatted by replacing mmc... with mmcblk0p26,
after that run the ruu again.
Swyped from my Desire S
Tectas said:
Try solution 2 of this guide http://forum.xda-developers.com/showthread.php?t=1284196
but replace the mmc....
With
mmcblk0p25
this will format your system partition,
maybe also data could be formatted by replacing mmc... with mmcblk0p26,
after that run the ruu again.
Swyped from my Desire S
Click to expand...
Click to collapse
I don't really have access to recovery (it just gets me back to fastboot), let alone Android, so I don't see how I can follow this guide (maybe I misunderstood)...
I have FC with Market. Everytime i try to acces it.
foouser said:
I don't really have access to recovery (it just gets me back to fastboot), let alone Android, so I don't see how I can follow this guide (maybe I misunderstood)...
Click to expand...
Click to collapse
Don't mind the recovery step, just do the commands within adb shell
Swyped from my Desire S
mihaibuda said:
I have FC with Market. Everytime i try to acces it.
Click to expand...
Click to collapse
Have you tried wiping cache and
dalvik cache?
I also had fc after an update, this solved it for me.
If you're using cyanogen, try changing the language to English us, this solved it for some users.
Swyped from my Desire S
Never mind, I actually created a goldcard in order to bypass the CUSTOMER ID error and flashed my phone back to original and S-ON. Thanks anyways.
Just as a note to everyone, you should really go about getting back to S-ON via this way: Flash any RUU, get the original HBOOT image from that RUU (you can find it in your temp folder while flashing the RUU), and then just downgrade the HBOOT using fastboot. Easier than going through ENG HBOOT, and allows you to avoid these kind of problems (CID errors).
The problem is that you restored "DIALER STORAGE" via titanium backup. Reflash ROM, and don't restore this. It'll work, FOR SURE.
foouser said:
Never mind, I actually created a goldcard in order to bypass the CUSTOMER ID error and flashed my phone back to original and S-ON. Thanks anyways.
Just as a note to everyone, you should really go about getting back to S-ON via this way: Flash any RUU, get the original HBOOT image from that RUU (you can find it in your temp folder while flashing the RUU), and then just downgrade the HBOOT using fastboot. Easier than going through ENG HBOOT, and allows you to avoid these kind of problems (CID errors).
Click to expand...
Click to collapse
Can you please post the thread that contains the Gold Card creation process (if there was one) so that I can add it to the INDEX.
As no doubt this will be useful to others...
ty
ben_pyett said:
Can you please post the thread that contains the Gold Card creation process (if there was one) so that I can add it to the INDEX.
As no doubt this will be useful to others...
ty
Click to expand...
Click to collapse
Sure, it's really the same process for all HTC phones and works even on the newest models (Sensation generation). Thanks a lot to EFI from AlphaRev who actually pointed me in the right direction.
I used this guide: http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
I'm using Windows 7 x64 and when I inserted the card after modifying it, Windows required me to format it (as opposed to what's written in the above guide), but it still worked. Also, since my phone was stuck on HBOOT I had to use another Android phone to get the SD's CID (I used a friend's SGS, and the SD slot to query is mmc2 on it).
shrome99 said:
The problem is that you restored "DIALER STORAGE" via titanium backup. Reflash ROM, and don't restore this. It'll work, FOR SURE.
Click to expand...
Click to collapse
Well, I actually didn't use Titanium Backup at all, so nope.
Hi,
I'va had CM7 a10 flashed on my Sensation for a few days. A couple of days ago I've decided to get back to Stock ROM, and then the problems started. Before installing CM7 everything was fine. After restoring my backup from before flashing CM7 weird things started to happen (apps dissapearing, settings changing on their own, hangs, and other stuff). So I've done a SuperWipe a few times, and flashed a completely new Stock ROM via USB using: RUU_Pyramid_HTC_Europe_1.50.401.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223042_signed file. Then I've done a few factory resets, just in case. But still weird things are happening (eg. now I have a clean phone - once again - and trying to setup the sync options and the options app hangs everytime. and installing something from market is like praying for a miracle). I've tried doing factory reset, clear cache/dalvik (but with dalvik CWM recovery says that the partition or files wasn't found). Don't know what to do. Does anyone have any ideas ?? Please help. Phone worked fine before, and after CM7 everything is f*cked up
Wierd, looks like you've tried everything I could think of while reading the post.
Do you still have a nandroid backup of CM7, if so does that work if you restore ?
Can you use ADB to get to the phone ? If so you could check some things from there.
When you installed the RUU from the PC, did it install without errors ? Presumably you had to re-install CWM after that.
CM7 nand backup works fine after restore.
I can use ADB to comunicate with the phone.
No errors while updating RUU.exe / CWM recovery flashed without problems also after that.
I think that there's something screwed up with the file permissions.
I've downloaded and installed about 20 apps since the last HR, and now I have about 40 apps more queued in Market, and as before the downloads are stuck every 1-2 apps. Then I have to restart to CWM recovery and run fix permissions. After that another 1-2 apps will download and get stuck again, and so on...
Anyone has any ideas what the hell is going on ? Because my I'm getting more then irritated by this, and beggining to think that the best solution will be to send my phone flying through the window.
A few questions first.
What country are you in?
Who is your carrier?
What version did your phone originally come with? I believe 1.5xxxxx RUU was released recently, but I could be wrong.
Did you ever change your CID?
Have you ever flashed a new radio and RIL?
Did you copy all of the data from your SD card to your computer, then format your SD card using the phone?
Answer these questions and try the SD card thing, then report back. I may be able to help.
Poland.
T-Mobile (Sensation) / Play Mobile (Gio)
Don't remeber what version my Sensation originally came with - I have a 1.50.401.1 RUU that I'm flashing with currently.
Yes, I've changed CID to 11111111 some time ago, but I'm back to original HTC__001 now.
No I haven't changed my radio or RIL.
I've tried formatting the SD card using the phone, my laptop, my linux NAS, my other phones.
The weird thing is that yesterday all of this was progressing. It came to a point that after a factory reset or even a whole ROM reflash nothing would install (not even Market update). And this also started to happen on my Samsung Gio. So after very very very frustrating evening, and part of the night I gave up. And in the morning it was still the same (on both my android phones). But now things are starting to work (updates/installs). So I think I'm going to blame the whole thing on Google and Market. I'll see what happens while I'll install all my apps in the next few hours.
Still have to restart the phone every 1-3 apps installed. This is driving me crazy
All,
See that the new AT&T update for the 850 G3 came out...I'm currently rooted via towelroot and nothing else. Tried downloading the update, rebooted, installing process and failed. Said I was rooted. Booted me back to normal. Anyway to unroot myself without wiping everything?
Nope, you pretty much have to flash back to stock via the top file which will wipe EVERYTHING including the internal storage. The better question is why do you want the att update. If you are absolutely desperate you can try the root cloak xposed module, that may or may not trick the updater into attempts to flash but may also brick your phone.
I just tried this and it didn't work. I the below method last night but the LG Flash Tool keeps failing and giving me the error "cannot change to download mode". I saw there were some issues when using Windows 8 so I"m going to try and put Windows 7 on my old laptop and try again. If not I will try another computer with Windows 7 already installed.
http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827
I have had nothing but issues with this phone upgrading. Every time it bricks, the first time I got it working by reformatting DATA partition. The other times basically gave up and 2-3 days later I come back and it magically starts working again. The day that 5.0.1 came out I downloaded the FUU, well everything looked good the it gets stuck at the Android is upgrading starting apps. Since then I have redownloaded all 5.0.1 files I could find on XDA, and the same results. I tried different roms, using TWRP to wipe and rewipe and format and do it again and again. I have tried to downgrade to 4.4.2 and 4.4.4 but i get the process system isn't responding when it boots up. I am unsure what to do now, anything will help.
You flashed this RUU???
http://forum.xda-developers.com/showthread.php?t=3047103
After flashing that do a factory reset from hboot. That should get you back to a healthy stock system
berndblb said:
You flashed this RUU???
http://forum.xda-developers.com/showthread.php?t=3047103
After flashing that do a factory reset from hboot. That should get you back to a healthy stock system
Click to expand...
Click to collapse
Yes, that was the first thing I tried, but I just downloaded it again twice and did factory reset both times and I still get stuck on the "Android is upgrading... Starting apps."
dab1414 said:
Yes, that was the first thing I tried, but I just downloaded it again twice and did factory reset both times and I still get stuck on the "Android is upgrading... Starting apps."
Click to expand...
Click to collapse
So after it upgrades all apps its just sits on starting apps?
Can't hurt to run RUU again. Perhaps even4.4.4 then take the OTA for 5.0.1
andybones said:
So after it upgrades all apps its just sits on starting apps?
Can't hurt to run RUU again. Perhaps even4.4.4 then take the OTA for 5.0.1
Click to expand...
Click to collapse
Yes It gets stuck there everytime. Seems like no matter what I do for 5.0.1. When I tried to downgrade ( I did both 4.4.2 and 4.4.4) it gets the process system isn't responding error.
dab1414 said:
Yes It gets stuck there everytime. Seems like no matter what I do for 5.0.1. When I tried to downgrade ( I did both 4.4.2 and 4.4.4) it gets the process system isn't responding error.
Click to expand...
Click to collapse
that's very strange. What method are you going about with the RUU?
using adb?
perhaps maybe try going through hboot with the sdcard?
not sure it will make any difference what-so-ever, just brainstorming.
andybones said:
that's very strange. What method are you going about with the RUU?
using adb?
perhaps maybe try going through hboot with the sdcard?
not sure it will make any difference what-so-ever, just brainstorming.
Click to expand...
Click to collapse
Yes, it is very strange. OK so I have done nothing with adb for the upgrade. I have tried the FUU.exe, and the RUU through fastboot, fastboot flash all files separately, and put on an external drive that is fat32 to use HBOOT method. and I just downloaded the firmware and did the HBOOT again twice, doing a factory reset after each one. But in bootloader screen all firmware numbers match up and I never get any errors, just gets stuck on starting apps.
dab1414 said:
Yes, it is very strange. OK so I have done nothing with adb for the upgrade. I have tried the FUU.exe, and the RUU through fastboot, fastboot flash all files separately, and put on an external drive that is fat32 to use HBOOT method. and I just downloaded the firmware and did the HBOOT again twice, doing a factory reset after each one. But in bootloader screen all firmware numbers match up and I never get any errors, just gets stuck on starting apps.
Click to expand...
Click to collapse
Are you S-OFF?
If so are you wanting to run a ROM or just be on stock + rooted?
andybones said:
Are you S-OFF?
If so are you wanting to run a ROM or just be on stock + rooted?
Click to expand...
Click to collapse
Yes I am S-OFF since the day I got the phone. And I have been using RKND roms, but I downloaded and tried all the 5.0.1 roms to see if anything would help. At this point I just want my phone working again, but preferably with the ability to change roms when i want to which is about once a month or two.
So I had tried everything I knew how to do again with no luck. Then I just let my phone sit for the last week. Then I decided to turn it on last night and it works fine. Is there any reason why I had to let the phone stay powered down for days for it to start working? This is the second time I had to do that when upgrading the firmware.
Thanks for bringing this up and I'm glad to hear it worked out for you even tho it took some time. My bro just ran the vzw update while on viper 4.1.0 and now he says his screen is unresponsive. He said it ran through all the normal start up procedures but the welcome screen is shaded (like it's in the background) and he says it won't respond to any touches whatsoever. I won't get a chance to see it until I return to work on Wednesday but if it does the same as yours maybe it'll fix itself by then. :fingers-crossed:
Edit: I just realized that you ran the FUU. He went and said yes to the stupid OTA! Hopefully I'll be able to do something with it when I get back but I'm thinking that running the OTA while rooted and S-Off'd might've screwed it up.
Update: I'm a moron! :silly: It didn't do anything to his phone. I just had to reinstall the recovery and viper 4.3.0 and it's working fine again. I think actually it might've been a good thing he did cause now the phone had the right firmware on it for LP so it all worked out. Sorry for cluttering up your thread.