I have a htc one x and i currently have no network reception. i took it to the o2 shop and the o2 guru said that it is caused by the missing imei and baseband.
He sugggested installing a custom ROM to try fixing this (my phone is out of warranty anyway).
Having looked online i have managed to root my phone, backup my stock android ROM and installed CyanogenMod-10.2.1-endeavoru using clockwork mod recovery.
However, just after installing cyanogenmod when i tried to boot into this i am seeing the blue preloader icon going round in circles. I have waited for 30mins and its still loading.
I have wiped cache, factory reset and wiped dalvik cache but that didnt work either.
Does anyone have any suggestions on what to do next?
I simply want reception back on the phone so i can use it, not really fussed about the ROM.
Thanks!
Related
Just got Desire S, locked to Ireland O2 network.
The first time I booted it, fresh from the box, it bootlooped on me a couple of times. It was strange, but I didn't worry too much - I said to myself "doesn't matter, I'll overwrite /system anyway".
Ran Alpharev, everything worked, got into recovery, backed up stock ROM, tried to flash ROM. Didn't work - stopped almost immediately. Checked /system, almost nothing there, only /app and several apps inside it.
Reflashed recovery to different ones, tried flashing ROMs again, didn't help. Tried to return to stock ROM backup - and only then noticed that system.img has size of 0.
Then I got worried, reflashed O2 RUU. Everything was back to stock, booted, started setting up the stock ROM - voila, bootloop again.
Is this anything known, are Ireland O2 Desire S versions special in any way (why was I unable to flash /system properly?), or did I just get a bad phone?
Thanks.
Jack_R1 said:
Just got Desire S, locked to Ireland O2 network.
The first time I booted it, fresh from the box, it bootlooped on me a couple of times. It was strange, but I didn't worry too much - I said to myself "doesn't matter, I'll overwrite /system anyway".
Ran Alpharev, everything worked, got into recovery, backed up stock ROM, tried to flash ROM. Didn't work - stopped almost immediately. Checked /system, almost nothing there, only /app and several apps inside it.
Reflashed recovery to different ones, tried flashing ROMs again, didn't help. Tried to return to stock ROM backup - and only then noticed that system.img has size of 0.
Then I got worried, reflashed O2 RUU. Everything was back to stock, booted, started setting up the stock ROM - voila, bootloop again.
Is this anything known, are Ireland O2 Desire S versions special in any way, or did I just get a bad phone?
Thanks.
Click to expand...
Click to collapse
i dont think there is any area specific problem
i think you just got a bad device or something went wrong when flashing
Since it bootlooped both out of the box and right after RUU, I don't think there's any chance that none of the many flashes worked correctly.
Oh well, I guess warranty repair it is.
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
Hey there folks, I've got a sensation 4g (bell). I recently followed the htc released steps to unlock my bootloader, all went well, as far as i can tell, when accessing the bootloader, it says that it is unlocked.
Here comes the issues. I was trying to flash cm7. I did all the necessary steps, wiped the cache and data, did a backup. The whole nine yards. Then I flashed the rom. Rom wouldn't load. No trouble, I made a backup. When I reverted to my backup, I had lost all radio functionality. No mobile network, no wifi. Nothing.
SO I tried flashing MIUI through rom manager. Still nothing.
I'm stuck folks, any suggestions?
I flashed the ROM and baseband per instructions in this thread: http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523
I had 4.4.2 and he said it had to be stock, and it was with the exception of potentially having some system files modified due to other apps, like Android Tuner. I wiped Dalvik cache and regular cache, installed both files as mentioned through TWRP, and yet upon starting I get a notice to update to 4.4.3 despite already being on 4.4.3, and it can't connect to T-Mobile which is my service provider. Am I doing something wrong here? I figured by "stock" ROM he meant the original and not CyanogenMod or anything like it. Was that supposed to mean stock Android with zero modifications to the system files?
I didn't want to do a factory reset and have to redo all my data and applications, but if I must then I will.
There is a rough thunderstorm going on so maybe that knocked out T-Mobile service, but I find it rather coincidental.
]UPDATE] Turns out that the storm coincidentally disabled the towers at around the exact time I updated my phone. The phone was flashed fine. T-Mobile is the problem. Thanks for the help!
It doesn't matter what ROM you're coming from but if it's not stock you need to wipe. But whatever mods you have on stock is irrelevant.
If you're having issues connecting,, wiping cache is often the cause. Check. Our imei etc is correct. Maybe fastboot flash a stock cache image or Nandroid restore
Sent from my Nexus 5 using Tapatalk
rootSU said:
It doesn't matter what ROM you're coming from but if it's not stock you need to wipe. But whatever mods you have on stock is irrelevant.
If you're having issues connecting,, wiping cache is often the cause. Check. Our imei etc is correct. Maybe fastboot flash a stock cache image or Nandroid restore
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It was the original stock that shipped with the phone, with potentially some files modified from an application. Strangely when searching for networks to connect to, Sprint and AT&T show up as normal but not T-Mobile, although their APN's show up as if I am connected but can't get access to their service.
The IMEI within the phone appears to match the worn off label. Either way, I cleared the Dalvik and regular cache again so I'll see what happens when the phone finishes booting.
Surely it's booted by now?
Sent from my Nexus 5 using Tapatalk
rootSU said:
Surely it's booted by now?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It finished updating the apps and didn't get a connection, however when I traveled outside of my home zone to work, after I reach the spot outside of the city at which there is no LTE support and it drops to EDGE the connection picked up and remained. After I returned from work and got back in the city near my home where it switches back to LTE the connection dropped again and remained that way even after wiping the caches again.
Does this still sound like a software problem or maybe it's on T-Mobile's end?
Fixed
Turns out that the storm coincidentally disabled the towers at around the exact time I updated my phone. The phone was flashed fine. T-Mobile is the problem. Thanks for the help!
Couple days ago I flashed my first rom, a nightly kltespr Cyanogenmod 12 through Clockworkmod custom recovery. When it booted up the cell network kept turning on and off but everything else was working (not due to bills or location, it did not acknowledge my SIM). I attempted a clean install several times, but to no avail. Went to boost mobile (my provider) and asked if I could get some help with my phone. I told them I installed a custom OS and they thought it was a virus when they saw the booting animation, lmao. He did a full ****ing system wipe.. So it booted up with CMOD 12 again because I didnt have a backup and didnt install another rom. He asked me if I could connect to their wifi. Then this dumbass wouldnt give me the password to it because he thought I can hack into his PC and **** and threatened to call the cops.. He didnt even give me a new SIM to try. Then I went home and tried downloading the latest version in klte and installing it (still CMOD 12).. Unfortunately, I confused it with kltespr, the correct rom for my SM-G9OOP (keep in mind, before this I installed the correct version, but i had cell service issues). Before I noticed, everything was working fine, then my cell network turned off. I noticed the problem when I went to settings and checked my model number and it was changed to SM-G9OOF, so I downloaded the kltespr version and appropriate gapps package, and prior to installing in Clockworkmod I wiped davlik cache, system, and everything. It boots up fine, but cell network is still not working, and more recently the phone turned off, then got stuck in bootloop. I took out the battery and reinstalled everything in CWM, after wiping again. Booted up fine again, but I still dont have cell service and the phone uncontrollably restarts over and over, forcing me to take the battery out. Is there anything I can do?
Btw this is my first post excuse the length.
Also, **** you Boost, get some competent employees. I highly suggest anyone considering them to stay away.
If I cant fix this im going to get a new iPhone6+ or Note 4 from Verizon.
Try this fix posted in this thread. Has nothing to do with Boost Mobile.
http://forum.xda-developers.com/sprint-galaxy-s5/help/help-t3006806