Hello,
I have searched multiple forums for hours today and have figured out what is going on with my HTC Vivid. (It has been upgraded to AT&T Official ICS.)
It was working fine up until yesterday where it was not receiving a signal from the mobile network and the signal icon has an X through it. The SIM card is properly inserted and another SIM card has been tried as well. Looking through other threads it seems like the Radio RIL files may be missing or corrupt. The IMEI number and *#06# code does not show an IMEI number either. The baseband version says unknown. I am not sure what happened as I have never loaded any other ROM on it.
I downloaded the Official RUU ICS upgrade ROM today and tried reflashing it, with no luck.
What is interesting (and the other person who had the radio problem) is that when I left the phone sit off overnight and then turned it on in the morning, the phone connected to the mobile network and I had a signal. When I restarted the phone, hours later, the phone lost connection to the mobile network and that is when I started digging and found the problem with the baseband version being unknown.
Is there anything anyone can suggest? Can I reflash the baseband files or copy them from someone somehow using ADB? It seems like there is where my problem lays. I've searched for ways on how to downgrade from ICS to the official GB stock rom, but it doesn't seem like it can be accomplished.
(I tried downloading the Holiday Cingular version of the GB stock rom but the update failed. I read about the ICS HBOOT version being different and not allowing it.)
Thank you in advance for helping and any suggestions.
Have you gotten a new sim card yet? That needs to be your first step. My captivate did the same thing and turned out the sim went bad
Sent from my HTC PH39100 using Tapatalk 2
Cor-master said:
Have you gotten a new sim card yet? That needs to be your first step. My captivate did the same thing and turned out the sim went bad
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Yes I have tried a different sim card. I don't believe thats the issue though being that it worked with the same sim after I let the phone sit overnight. From reading about others experience, it doesn't seem that the sim is the issue but more the baseband version and imei information missing.
centro7710 said:
Hello,
I have searched multiple forums for hours today and have figured out what is going on with my HTC Vivid. (It has been upgraded to AT&T Official ICS.)
It was working fine up until yesterday where it was not receiving a signal from the mobile network and the signal icon has an X through it. The SIM card is properly inserted and another SIM card has been tried as well. Looking through other threads it seems like the Radio RIL files may be missing or corrupt. The IMEI number and *#06# code does not show an IMEI number either. The baseband version says unknown. I am not sure what happened as I have never loaded any other ROM on it.
I downloaded the Official RUU ICS upgrade ROM today and tried reflashing it, with no luck.
What is interesting (and the other person who had the radio problem) is that when I left the phone sit off overnight and then turned it on in the morning, the phone connected to the mobile network and I had a signal. When I restarted the phone, hours later, the phone lost connection to the mobile network and that is when I started digging and found the problem with the baseband version being unknown.
Is there anything anyone can suggest? Can I reflash the baseband files or copy them from someone somehow using ADB? It seems like there is where my problem lays. I've searched for ways on how to downgrade from ICS to the official GB stock rom, but it doesn't seem like it can be accomplished.
(I tried downloading the Holiday Cingular version of the GB stock rom but the update failed. I read about the ICS HBOOT version being different and not allowing it.)
Thank you in advance for helping and any suggestions.
Click to expand...
Click to collapse
I had a similar problem and thought I solved it, but I later realised all my "solutions" didn't bring back the network but coincided with its reappearing cos no same "solution" worked more than once.
It's a very weird problem as the network shows up once in a while and when I'm using Mobile Network for Data, my phone hangs again and the IMEI, Network, baseband disappears on reboot...till further notice. I gave up trying and concluded it's either a bad modem (hardware) or something AT&T knows about!
You can get HBOOTS for both GB and ICS via Hasoons AIO kit
Flash the HBOOT, Flash the Image from Cingular GB RUU and I wish you luck!!!
ayulatins said:
I had a similar problem and thought I solved it, but I later realised all my "solutions" didn't bring back the network but coincided with its reappearing cos no same "solution" worked more than once.
It's a very weird problem as the network shows up once in a while and when I'm using Mobile Network for Data, my phone hangs again and the IMEI, Network, baseband disappears on reboot...till further notice. I gave up trying and concluded it's either a bad modem (hardware) or something AT&T knows about!
You can get HBOOTS for both GB and ICS via Hasoons AIO kit
Flash the HBOOT, Flash the Image from Cingular GB RUU and I wish you luck!!!
Click to expand...
Click to collapse
I found the download link, but the website says they're updating their drives, so who knows how much longer that will take.
Also, are you saying I should just use the tools within the kit to flash the HBOOT back to the previous version compatible with GB and then flash the RUU GB image after? Can I do that with the phone connected via USB or does it have to be flashed from the SD card? If it has to be flashed from the SD card, how do I go about doing that? If it can be done from the phone via USB, does the phone have to be in recovery mode?
I have tried reflashing the ICS RUU multiple times w/ version 3.26.502.52 and 3.26.502.56, both do not fix the issue. Do the baseband and or radio files NOT get flashed within these updates?
Thanks for the response!
centro7710 said:
I tried finding a download link for the AIO kit on the link provided, but I must be blind?
Also, are you saying I should just use the tools within the kit to flash the HBOOT back to the previous version compatible with GB and then flash the RUU GB image after? Can I do that with the phone connected via USB or does it have to be flashed from the SD card? If it has to be flashed from the SD card, how do I go about doing that? If it can be done from the phone via USB, does the phone have to be in recovery mode?
I have tried reflashing the ICS RUU multiple times w/ version 3.26.502.52 and 3.26.502.56, both do not fix the issue. Do the baseband and or radio files NOT get flashed within these updates?
Thanks for the response!
Click to expand...
Click to collapse
For any issues downloading Hasoon AIO tool, please use his thread (earlier provided).
Yes, use the AIO tool to flash GB HBOOT or read the SUPERGUIDE
and obtain rom.zip from the Cingular RUU
I don't know how to flash RUU via Recovery [email protected]@@!!!
I'd advice you follow my first solution here!!!
ayulatins said:
For any issues downloading Hasoon AIO tool, please use his thread (earlier provided).
Yes, use the AIO tool to flash GB HBOOT or read the SUPERGUIDE
and obtain rom.zip from the Cingular RUU
I don't know how to flash RUU via Recovery [email protected]@@!!!
I'd advice you follow my first solution here!!!
Click to expand...
Click to collapse
Thanks for the quick reply.
Your thread was the one I saw earlier with the simliar problem that I am having, only I have not loaded any custom ROMS. The phone just stopped receiving the signal the other day. I am still waiting for the download website to become available to use the tool to perform the flash of HBOOT, however, once I do that, will that erase the ICS rom from my phone? If so, what steps do I have to perform to get it in a "download mode" to accept the AT&T GB RUU? I'm a little confused on that part.
I read your first thread and I am a bit confused on exactly how you were able to correct the baseband/RIL issue (which I am assuming is the root of my issue). Do I have to extract some files from the RUU executable? Are the commands you provided to be used in ADB? I am confused as to what to do with [setprop ro.baseband 3.26.5XXX (<--- mainver: in android-info.txt in RUU.zip)] from your post. If that command is copying a file or just setting information (almost like as a registry setting within Windows) to point to the file or set a version number. Also if the XXX needs to have a certain number.
I thank you for your time and am trying my hardest to understand what to do to accomplish these steps.
centro7710 said:
Thanks for the quick reply.
Your thread was the one I saw earlier with the simliar problem that I am having, only I have not loaded any custom ROMS. The phone just stopped receiving the signal the other day. I am still waiting for the download website to become available to use the tool to perform the flash of HBOOT, however, once I do that, will that erase the ICS rom from my phone? If so, what steps do I have to perform to get it in a "download mode" to accept the AT&T GB RUU? I'm a little confused on that part.
I read your first thread and I am a bit confused on exactly how you were able to correct the baseband/RIL issue (which I am assuming is the root of my issue). Do I have to extract some files from the RUU executable? Are the commands you provided to be used in ADB? I am confused as to what to do with [setprop ro.baseband 3.26.5XXX (<--- mainver: in android-info.txt in RUU.zip)] from your post. If that command is copying a file or just setting information (almost like as a registry setting within Windows) to point to the file or set a version number. Also if the XXX needs to have a certain number.
I thank you for your time and am trying my hardest to understand what to do to accomplish these steps.
Click to expand...
Click to collapse
I did find the extracted files within the RUU executable and found the rom.zip which included the .img files among other files I assume needed as sources to flash the phone. I see a radio.img file would I be able to do anything with that?
Thank you.
centro7710 said:
I did find the extracted files within the RUU executable and found the rom.zip which included the .img files among other files I assume needed as sources to flash the phone. I see a radio.img file would I be able to do anything with that?
Thank you.
Click to expand...
Click to collapse
And I have a question, if the radio/baseband files are included in the RUU flash, what is happening as to why it is not being reflashed, or if it is being reflashed, why it is disabling the mobile network and providing an Unknown version to Baseband and clearing the IMEI number?
ayulatins said:
For any issues downloading Hasoon AIO tool, please use his thread (earlier provided).
Yes, use the AIO tool to flash GB HBOOT or read the SUPERGUIDE
and obtain rom.zip from the Cingular RUU
I don't know how to flash RUU via Recovery [email protected]@@!!!
I'd advice you follow my first solution here!!!
Click to expand...
Click to collapse
Here's where I am:
I successfully unlocked my bootloader, downgraded to GB, rooted. Tried to gain root access through adb terminal but it was not working properly.
I relocked my bootloader. Installed the ICS RUU AT&T ROM update. Unlocked my bootloader, rooted.
I see the commands you ran in your previous post. I am also receiving the same message of N/A when running the getprop ro.baseband
I tried the second command setprop ro.baseband 3.26.5XXX and then restarted the phone. I have tried it as posted, and also with swapping out the version that is located in my android-info.txt file: 3.26.502.56
Still no luck with setting the baseband version. IMEI still is cleared out.
Am I doing something wrong?
ayulatins said:
I had a similar problem and thought I solved it, but I later realised all my "solutions" didn't bring back the network but coincided with its reappearing cos no same "solution" worked more than once.
It's a very weird problem as the network shows up once in a while and when I'm using Mobile Network for Data, my phone hangs again and the IMEI, Network, baseband disappears on reboot...till further notice. I gave up trying and concluded it's either a bad modem (hardware) or something AT&T knows about!
Click to expand...
Click to collapse
Please see my initial quotes above...
All the previous steps I took were only a coincidence (not proven to work)!!!
We may need to contact AT&T to be sure its not a lock IMEI (and I'm wondering why it would be) or an experienced Dev
ayulatins said:
Please see my initial quotes above...
All the previous steps I took were only a coincidence (not proven to work)!!!
We may need to contact AT&T to be sure its not a lock IMEI (and I'm wondering why it would be) or an experienced Dev
Click to expand...
Click to collapse
Hey thanks for all of your suggestions. I contacted AT&T the day everything happened to see if it was on the block list. They said no. I tried multiple things including trying to re-flash the radio, but I was getting a signature failed error that I could not get around. I really think that's what the problem is. I gave up and ended up selling it.
centro7710 said:
Hey thanks for all of your suggestions. I contacted AT&T the day everything happened to see if it was on the block list. They said no. I tried multiple things including trying to re-flash the radio, but I was getting a signature failed error that I could not get around. I really think that's what the problem is. I gave up and ended up selling it, as is, on ebay instead to get a few bucks out of it and getting a new phone.
Click to expand...
Click to collapse
I really wouldn't mind selling mine too if I get a buyer. I'm just tired of all the troubles and no dev is willing to help.
ayulatins said:
I really wouldn't mind selling mine too if I get a buyer. I'm just tired of all the troubles and no dev is willing to help.
Click to expand...
Click to collapse
Exactly. It was my sister's phone. The sh*tty thing is we bought two off of ebay at the same time, 1 for me, 1 for her. Well, her phone was not in the box (either never shipped or stolen) so I had to file a claim through eBay which took 3 weeks to get the money back. Meanwhile, I gave her my phone (which is the phone in reference) to use instead. I bought her an iPhone instead now, along with purchasing one myself. I loved Android, but the bugs and fragmentation is getting too much for me to handle.
Dude, if you don't have an IMEI showing up, something is WAY wrong. That goes beyone the RIL not working... The RIL is probably fine. If your phone doesn't have an IMEI somehow, the cell towers are NOT, NO WAY, NEVER EVER going to register your phone on their network. You can put a billion SIM cards in there, or flash a billion stock ROMS, and if you don't have an IMEI, you will never be able to connect.
Something is probably corrupt or broken in your firmware or the hardware itself. I think your device is probably screwed.
My advice, is follow the steps to put your phone back to stock (including changing the bootloader message back to **LOCKED** and S-ON), and get it back to the phone company. They will be able to tell something is boned on the phone right away since it isn't displaying an IMEI.
Sorry to be the bearer of bad news and for your many wasted hours... But on the plus side, you now know a LOT about flashing and how your phone works now
Good luck with everything man! Hope they get you up and running soon!
I have the same problem as the OP but I have a IMEI showing up and a Basehand But won't connect to AT&T or anything they resent me a Signal & everything it shows a X with no bars it happened after I did a Factory Reset
anyone got the Radio.img?
inick73376 said:
I have the same problem as the OP but I have a IMEI showing up and a Basehand But won't connect to AT&T or anything they resent me a Signal & everything it shows a X with no bars it happened after I did a Factory Reset
Click to expand...
Click to collapse
That's weird..you try creating the apns again? I don't see how a factory reset would do that. Try toggling airplane mode too
Sent from my De-Sensed HTC Vivid using xda premium
I am currently having the same issues right now, it works if i leave the phone off for 1 hr it will work until i reboot then its down again, tried every thing possible, airplane mode will crash, reflashing the radios from gb and ics does nothing, setprop does nothing really. from this point it feels like a hardware issue.
sorry to revive an old thread, i just wanted to know if anyone came across this issue and had it fixed
i will get a log to see if there is errors showing up
Return it.
Sent from my HTC Holiday using Tapatalk 2
Immediately after the release of the Sprint update, I tried flashing Insertcoin's ROM which asked for activation of the phone. I am in India intend to use my phone on GSM so, the process could not complete. I switched to Renovate 7.0. The problem is, now I am unable to flash any Sprint specific ROM on the phone as the phone keeps trying to activate and would not go past that screen. I am able to flash international ROMs with Sprint support like Elegancia, Renovate or Viper but not Sprint ROMs. Please let me out of this problem. I am desperate to try the Rage One ROM and other ROM variants.
shantanil said:
Immediately after the release of the Sprint update, I tried flashing Insertcoin's ROM which asked for activation of the phone. I am in India intend to use my phone on GSM so, the process could not complete. I switched to Renovate 7.0. The problem is, now I am unable to flash any Sprint specific ROM on the phone as the phone keeps trying to activate and would not go past that screen. I am able to flash international ROMs with Sprint support like Elegancia, Renovate or Viper but not Sprint ROMs. Please let me out of this problem. I am desperate to try the Rage One ROM and other ROM variants.
Click to expand...
Click to collapse
After downloading the rom.zip open it and go to /system/costumize/AAC/default.xml and find the line(near the bottom) sku_id 10
Change that value to 42, save update archive and flash the ROM. I think it's a base bug, cause that activation screen should pop up, but after a few min it should go away daying unable to activate. Anyway after changing sku_id you should not have problems
Sent from my HTC One using Tapatalk
Thanks. Will try this and report.
No joy for me. Still stuck at the activation setup in Badboyz ROM.
Hi,
I've already been through the thread
[30.03.2012][CF-Root 4.4] J-P/S/Q-*,JV-1KBHIOPQRSTAUV,JVU,JW4 - su+bb+2e/CWM-rfs+ext4
which has links to all the ROM files to be used with CWM in recovery mode (and explanations about their names).
I don't have a standard production phone. Mine has a build name of: FROYO.eng.eunju81.hong.201000831.205407 therefore I can't go by the names of the ROM files which are based on build names like FROYO.xxJP (P obviously referring to "Production"). Does the date of that build have any significance to you experts (Aug 31, 2010)? Does this narrow down what ROM file I can download?
Also, my phone is a pretty standard 512MB, ARM processor phone for that era (I'm guessing, since it was given to a journalist for review who gave it to me when she was done reviewing it).Will I have to use ODIN to flash it? I WAS able to root it (the Chinese made Eroot succeeded where all else failed) and install ROM Manager AND CWM but I then downloaded all three ROM types for my phone (the phone part isn't active I only use the WIFI so I tried the Galaxy Tab ATT, T-Mobile and Verizon but they all gave errors when I tried installing them). I read that it's imperative to have the right file, but with my funky build number, that doesn't seem possible. Am I going to be able to do with this without "doorstopping" my phone? (sorry. I like "doorstop" better than "brick" .
Wrong forum, this is S2/I9100 Q&A, not Tab Q&A which is here (we have device specific fora).
I've asked mods to move your thread, sit tight until they do.
One other thing;
I forgot to mention: Kies updated the firmware to the latest version if that helps you "axe spurts" figure this puzzle out. Thanks in advance!!! :fingers-crossed:
>>my phone is a pretty standard 512MB, ARM processor phone for that era (I'm guessing, since it was given to a journalist for review who gave it >>to me when she was done reviewing it).Will I have to use ODIN to flash it? I WAS able to root it (the Chinese made Eroot succeeded where all >>else failed) and install ROM Manager AND CWM but I then downloaded all three ROM types for my phone (the phone part isn't active I only use >>the WIFI so I tried the Galaxy Tab ATT, T-Mobile and Verizon but they all gave errors when I tried installing them). I read that it's imperative to >>have the right file, but with my funky build number, that doesn't seem possible. Am I going to be able to do with this without "doorstopping" my >>phone? (sorry. I like "doorstop" better than "brick" .[/QUOTE]
Hello All,
Today i tried flashing a new rom on my 3T. But failed with the message:
E3004, This package is for device OnePlus3T, oneplus3t; this device is .
Updater process ended with error: 7
Clearly the model name has somehow been removed from my device.
I've tried removing the asserts lines in the update script of the rom, but then my phone throws error 4 or error 6 codes.
Is there a way to rewrite the model name in my phone?
jaccotjuhhh said:
Hello All,
Today i tried flashing a new rom on my 3T. But failed with the message:
E3004, This package is for device OnePlus3T, oneplus3t; this device is .
Updater process ended with error: 7
Clearly the model name has somehow been removed from my device.
I've tried removing the asserts lines in the update script of the rom, but then my phone throws error 4 or error 6 codes.
Is there a way to rewrite the model name in my phone?
Click to expand...
Click to collapse
Discuss this issue with the ROMs Devs.
Also.. What version of TWRP recovery are you using? If not running the latest Official 3.2.1-0, or equivalent if suggested up-to-date UnOfficial TWRP build, I suggest updating your recovery and try again.
Sent from my OnePlus 3T using XDA Labs
I cross-flashed my v405ua (ATT) to the V405EBW30b_00_OPEN_EU_DS_OP_0806.kdz in an effort to get rid of the start-up error (current version) but the error still remains. Now I'm unable to flash back or to any other Kdz file, I get this notice Not support cross model download. It's not the start up error that concerns me, it's that I can not flash any other variant. I got the start up error after flashing from pie to Android Q (error: Current version not available for user. can't find matched carrier)
What can I do to fix this not being able to flash another Kdz file? Any ideas?
Gabriel51 said:
I cross-flashed my v405ua (ATT) to the V405EBW30b_00_OPEN_EU_DS_OP_0806.kdz in an effort to get rid of the start-up error (current version) but the error still remains. Now I'm unable to flash back or to any other Kdz file, I get this notice Not support cross model download. It's not the start up error that concerns me, it's that I can not flash any other variant. I got the start up error after flashing from pie to Android Q (error: Current version not available for user. can't find matched carrier)
What can I do to fix this not being able to flash another Kdz file? Any ideas?
Click to expand...
Click to collapse
Yes, to do a crossflash, u need the 1.14 dll version of patched lgup. U probably have that as you've already done a crossflash. To flash back, u need the patched lgup with dll 1.16. It's newer and recognizes the newer rom u crossflashed to.
The other issue u mention, the error on startup. I've found that if I crossflash (partition dl) to the rom I want, let it finish (which means it reboots), then shut it off and use lgup to do a 'refurbish' with the exact same rom u crossflashed to, then u won't get the message.
It sounds kind of convoluted, I know. But it seems the 'refurbish' propagates some of the values from partition to partition, where the part dl does not.
cheers
Yes I have been using patched 1.14, I'm looking for patched 1.16 now. Thanks
The EBW30b works well, I will try the method you mentioned to get rid of the start up error. (If I understand it correctly)
I cannot find patched lgup with dll 1.16. anywhere?
I did fine the patched 1.16 however I still get the cross flash error "CrossDL"
Gabriel51 said:
I did fine the patched 1.16 however I still get the cross flash error "CrossDL"
Click to expand...
Click to collapse
hmmmm, try doing it with the 1.14 version, choose part D/L and select everything but the ftm partition. Then do a refurbish with same kdz. See if that works.
I tried every option with the patched 1.14 version as well however I selected all items with the D/L option. Will omitting ftm be that much different?...
It seems no matter what I do with any lgup file it gets to 4% and then gives me the crossDL error. I wish it would just ignore what ever version I'm using. Thanks
Gabriel51 said:
I tried every option with the patched 1.14 version as well however I selected all items with the D/L option. Will omitting ftm be that much different?...
It seems no matter what I do with any lgup file it gets to 4% and then gives me the crossDL error. I wish it would just ignore what ever version I'm using. Thanks
Click to expand...
Click to collapse
Here's a thread, and another one to look in for a version of 1.14 that should work. In this thread there's talk about the start up error.
Should have mentioned earlier, the startup error doesn't hurt anything, and you only see it briefly after rebooting the phone. Others have just lived with it.
But, as said, it's the part d/l and then do a refurbish that gets rid of it, so check the other threads to find a version that will work. The ftm exclusion isn't necessarily critical, but some have lost their imei / and or serial due to cross flash and excluding ftm usually avoids that.
hopefully you've read the threads about doing this prior, as they do suggest to backup your boot, abl, laf, ftm, fsg, modem, modemst1 and modemst2 partitions first.
cheers
One of those options I had already tried but no success until about an hour ago.
https://mylgphones.com/how-to-flash-stock-pie-kdz-firmware-on-lg-v40-thinq-with-lgup.html?amp
These instructions got me where I needed to be with ease. It seems that some KDZ files cross flash easy but cross flashing from them is difficult as I have tried everything from everywhere.
I appreciate you effort to help.
====================================================
Attachment contains process