I have a very glitchy Rogers Dream with EB1 radio. I rooted it before the mandatory update and have since updated the radio. My wife had been using the phone and claimed it was unstable and had lots of problems. I swapped phones with her and am trying to figure out what's wrong and how to fix it.
We did have a bulging battery issue before and replaced it.
FASTBOOT says:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA21000)
CPLD-4
RADIO-3.22.26.17
Apr 20 2009,15:30:43
I have the Amon Ra 1.7.0R Recovery flashed.
I have tried to wipe cache, dalvik, ext partition, and factory wipe from recovery. Then I flashed CM 5.0.8, then EB1 patch, and GApps. I have tried switching around EB1 patch and GApps order, but the same problems arise.
It's not the SD Card because we swapped that and the SIM and I have mine in the phone.
When the phone starts up, there are numerous FC's even without installing any apps. The FC's include acore, media, and sometimes the geniewidget.apk.
On its own, it will reboot after pressing a few buttons sometimes. It doesn't always reboot by itself. If I turn it off, most of the time it will reboot instead usually when plugged into the wall charger, but happens even without.
Can anyone shed some light and help me out? Do I have a bad phone? I was thinking maybe trying to reroot the device to see if that fixes anything, but I don't even know where to begin anymore.
My G1 is older than her Dream and it doesn't even have any of these issues aside from no 3G on Rogers network.
For radio issues:
Turn off 3g it will be stable with the new radio as well..
From what I can tell its bad HSPA handoffs between towers and usually happens when you are in an area with multiple towers with similar signal quality.. for me this seems to only be at work.
This isn't to say the radio firmware is or is not at fault.. but if it is reverting to the original 3.22.20.17 ought to solve it (battles with rogers call center aside if the wavier fails for you)
Note I find cyanogen has less issues than the stock HTC firmware with the radio..
------
As for the force closes. . Usual clean install rules:
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot erase boot
And remove all files in /sd-ext
(I believe ra-recovery has a wipe option for that)
Then install.
I've not had system stability issue. . Just radio stability fixed by airplane mode.
thanks.. this seems to have solved the problems so far. her phone hasn't fc'ed once since i started the phone after i erased in fastboot and reflashed everything. I turned of 3g just in case and maybe i'll try to turn it back on later.
Exact Same Issue
Hi Guys,
Had EXACT same issue, EXACT same versions, some other symptoms to note...
-The EXT partition seemed to get bigger with every reflash
-Restarting sometimes resulted in freeze, requiring reflash
SO FAR, the fastboot steps, wipe, reflash seems to be stable. Will update this thread as time goes on with my findings. A note, though, about the radio. It was stable in CM4x, with the 1.4 +JF recovery, showing only occasional glitches s/a missed calls. Don't think there should be any change with 5x?
At any rate, thanks for the fresh install fix.
Dylan
her phone did have 1 issue after the fastboot wipe. it turned itself off once out of the blue and was unable to be charged or turned on until i pulled the battery. i don't believe this has reoccurred which is why i never mentioned it.
Related
Hi all, this might be a n00bish question, ive searched and ive noticed some people having a similar problem but i havent read a solution.
My G1 and specs are in the signature. I am on Radio 1.22.14.11 and im trying to update to the 26I from HTC's site but everytime i flash it and I hold Power+Camera it still says im on the 11 radio...why wont it let me upgrade? I didnt use the trackball btw, if that has anything to do with it...i renamed it update.zip and everything. idk why it wont upgrade. Any help would be greatly appreciated! Thanks!
Hello, I had issues like this, I noticed it the first time with a jf rom and onne other time with the recovery, somethings not being saved right on ur end. I wouldn't know the exact answer to this question, however, my fix was a complete start from scratch, back to dreaimg.nbh and formating.partioning of the sd. Srry for weak suggestion, I'm sure there's a reason and an answer but if all else fails a fresh start never hurts! Hope u fix it!
Try to use cyan 1.4 recovery.
The reason I say this is because I think there is a bug with amon_ra's new boot image where it will select an option by pressing the home button, thus doing the same thing as using the trackball to press the reboot option.
Thanks guys. it seems like theres no simple fix for it. i tried flashing in cyans recovery a few weeks ago and it still didnt work. I wonder if any of the others who had this problem solved it. Ill admit if it wasnt for the Recovery Flasher app that came out a while ago, i would never have been able to root. Im still a n00b, but im learning a lil more as i read along here. Thanks guys ill keep looking for info.
flash the radio through fastboot.
fastboot flash radio radio.img
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery
doing all that, you can also flash the recovery image that you tried to before, but could not.
sorry for the extremely late response.
Ive installed the sdk successfully but each time i install the drivers and connect my phone itll sense it for like 30 seconds and then the phone wont be sensed anymore, this happens on my win 7 64 bit laptop and on my windows xp desktop. I updated to RA's 1.5 recovery image and gave it another shot but it still shows up as the old radio in the phone settings.
i just realized you said fastboot. idk if i can use that since i have stock spl. forgive me if im wrong like i said im still new to this
No you can't, you have to use the hard/enginering spl
Hm....I don't think I can upgrade my spl if I can't upgrade my radio, is that right? I don't know why it doesn't flash through recovery. It writes the image and boot, then shows a picture of the htc logo and reboots into recover and says clearing cache. I don't know what could be causing the problem, I even tried formatting my memory card and wiping everything but still it remains on the 11 radio....
I am running Cyanogenmod, latest update, and ever since I rooted my G1 and replaced the ROM, I have encountered a large amount of problems, such as my phone rebooting itself constantly and android.process.acore constantly force-closing, and I would like to revert back to stock firmware. Now, I know how to revert to stock firmware, that's all easy enough, but here's my problem:
I am not fully aware of what a splash2 image is and in reverting to stock firmware, if it was modified, I will brick my phone without erasing it. I need to erase it using Fastboot; however, I cannot boot into Fastboot mode, I have tried constantly.
I power off my device, connect it via USB to my computer, then power it on by holding Back+Power. I then repeatedly press Back but can never enter Fastboot mode, it only displays Serial01.
These problems severely frustrate me on a daily basis and I would like nothing more than to revert back to stock firmware, any help in moving me toward that goal would be greatly appreciated. Thank you.
firstly, wrong section
secondly, fastboot it camera+power, not back+power
unless you consciously added a custom splash2 then you wont have one
Sent Move Request
you could easily just wipe and reflash the 1.6 adp image from the htc website - that would fix it and there is no risk of brick
Sorry, I wasn't aware of where to post this.
When I flashed the Cyanogenmod ROM it changed the screen where it displays the "android" image when booting up my phone. Is that not a changed splash2 image?
Also, when I try to boot it using Camera+Power, it quickly displays "No img found!" then I end up on the multicolored screen with Serial01 displayed. I press Back and Serial01 disappears, but Fastboot does not appear.
I apologize if these questions are absurdly unintelligent but these are the areas I've been most confused about for quite a while. Except for ADB shells, but I did manage to get that working.
EDIT:
If this would help at all, what I do have displayed at this screen is:
DREA100 PVT 32B
HBOOT-O.95.0000
CPLD-4
RADIO-2.22.19.261
Sep 2 2008
Also, I have never seen a screen with three Android avatars skateboarding nor am I able to access it.
Why don't you just put an .img onto an sd card and fastboot? When you go into fastboot is an img there waiting to get loaded?
Hey guys, I think I've soft bricked my device all the way to hell and back.
So I was running Nocturnals GPE ROM and something screwed up and I was left with no service for the whole day. I came home to find that it was an issue which happened on the latest version of the ROM where if you flash anything it screws with the radio (even though I'm pretty sure I didn't flash anything in between my sending a text before getting in my car and getting out, but... whatever). So I went home and tried flashing all different radios- 1180, 0155 (or whatever it is) on TWRP 2.6, 2.7, and 2.8. No dice- same thing every time (no baseband, phone basically knows nothing about itself except its serial number). I then tried flashing ViperOne after wiping the phone (which TWRP didn't even do, I still had my SD Card items, but it said it did it so I trusted it). That booted up to an HTC Logo and a status bar with still no service. So I did a factory reset and wiped again, flashed the GPE ROM (because it actually booted to a usable interface) and went to bed, figuring I'd deal with it tomorrow afternoon and deal with another day without service and school wifi restrictions.
So I came home today and tried to flash an RUU. I'm now on 0904 radios with no recovery and nothing to boot into. Booting normally or rebooting through fastboot gets me into a bootloop with just an HTC Screen. Flashing a recovery via fastboot will say it flashed, but trying to get into recovery will again bootloop it, but this time, on the first loop of the bootloop, it will have the "Entering recovery..." message at the top. I then tried to flash clockwork to try to install anything, and to my surprise, it booted! I then did a full wipe to try to install a new ROM, but then after wiping and rebooting to try to push something via fastboot, I could not get into clockwork again.
At this point I tried to use the RUU.exe for the phone. After freezing my computer and taking 10 minutes to load, it said there was an error and that the phone wasn't connected. I'm assuming this is because I was in the bootloader, not in an OS. So I've now been sitting here trying to get anything to flash and boot, but I keep getting bootlooped.
I'm now just sitting in the bootloader trying to think of a solution, but I'm out of ideas. Anyone got anything?
Bootloader looks as follows:
*** UNLOCKED ***
M7_WLS PVT SIP S-OFF RH
CID-SPCS_001
HBOOT-1.57.0000
RADIO-1.01.20.0904_2
OpenDSP-v31.120.274.0617
OS-1.11.651.2
eMMC-boot 2048MB
Sep 24 2014, 16:58:42.0
I'm probably going to take it to Sprint tomorrow and see if they can do anything, and if not, let me place a hold on a Nexus 6 since it's going to be less money on contract allegedly. But until then, I'm hoping I can get this figured out.
Thanks for any help you guys can provide!
EDIT: I got TWRP to run on the phone! I guess it must have been a bad download that I was using or something. Now downloading stock and I'm going to Xposed the balls out of it to make it near stock, since I want to have as close to GPE as possible.
EDIT 2: So I got into TWRP- The adb sideload didn't work. Actually- it worked once, but once it got to 100%, it said the file was corrupt then deleted it. So I went back into TWRP and after several tries, could not get it to work again. So I go to try my OTG cable. I tried flashing a completely stock ROM and it got almost all the way, then said "could not find /data, could not find /system, could not find /cache, could not find internal memory". This makes me believe that the phone has literally no other files on it other than TWRP. So I tried to find some way to get those files, and that managed to lead me to flash the boot.img for the phone. Now it booted up and has been stuck at the HTC boot screen with the "powered by Android" logo at the bottom and the red text. I've held down volume down + power for 5 minutes and it did nothing; the lights just kept flashing. I'm going to take it to Sprint tomorrow and say I was trying to get it back to stock and the RUU screwed it up. Sprint is supposedly pretty cool about mods and rooting, so hopefully they can help me out.
Bseagull said:
Hey guys, I think I've soft bricked my device all the way to hell and back.
So I was running Nocturnals GPE ROM and something screwed up and I was left with no service for the whole day. I came home to find that it was an issue which happened on the latest version of the ROM where if you flash anything it screws with the radio (even though I'm pretty sure I didn't flash anything in between my sending a text before getting in my car and getting out, but... whatever). So I went home and tried flashing all different radios- 1180, 0155 (or whatever it is) on TWRP 2.6, 2.7, and 2.8. No dice- same thing every time (no baseband, phone basically knows nothing about itself except its serial number). I then tried flashing ViperOne after wiping the phone (which TWRP didn't even do, I still had my SD Card items, but it said it did it so I trusted it). That booted up to an HTC Logo and a status bar with still no service. So I did a factory reset and wiped again, flashed the GPE ROM (because it actually booted to a usable interface) and went to bed, figuring I'd deal with it tomorrow afternoon and deal with another day without service and school wifi restrictions.
So I came home today and tried to flash an RUU. I'm now on 0904 radios with no recovery and nothing to boot into. Booting normally or rebooting through fastboot gets me into a bootloop with just an HTC Screen. Flashing a recovery via fastboot will say it flashed, but trying to get into recovery will again bootloop it, but this time, on the first loop of the bootloop, it will have the "Entering recovery..." message at the top. I then tried to flash clockwork to try to install anything, and to my surprise, it booted! I then did a full wipe to try to install a new ROM, but then after wiping and rebooting to try to push something via fastboot, I could not get into clockwork again.
At this point I tried to use the RUU.exe for the phone. After freezing my computer and taking 10 minutes to load, it said there was an error and that the phone wasn't connected. I'm assuming this is because I was in the bootloader, not in an OS. So I've now been sitting here trying to get anything to flash and boot, but I keep getting bootlooped.
I'm now just sitting in the bootloader trying to think of a solution, but I'm out of ideas. Anyone got anything?
Bootloader looks as follows:
*** UNLOCKED ***
M7_WLS PVT SIP S-OFF RH
CID-SPCS_001
HBOOT-1.57.0000
RADIO-1.01.20.0904_2
OpenDSP-v31.120.274.0617
OS-1.11.651.2
eMMC-boot 2048MB
Sep 24 2014, 16:58:42.0
I'm probably going to take it to Sprint tomorrow and see if they can do anything, and if not, let me place a hold on a Nexus 6 since it's going to be less money on contract allegedly. But until then, I'm hoping I can get this figured out.
Thanks for any help you guys can provide!
EDIT: I got TWRP to run on the phone! I guess it must have been a bad download that I was using or something. Now downloading stock and I'm going to Xposed the balls out of it to make it near stock, since I want to have as close to GPE as possible.
EDIT 2: So I got into TWRP- The adb sideload didn't work. Actually- it worked once, but once it got to 100%, it said the file was corrupt then deleted it. So I went back into TWRP and after several tries, could not get it to work again. So I go to try my OTG cable. I tried flashing a completely stock ROM and it got almost all the way, then said "could not find /data, could not find /system, could not find /cache, could not find internal memory". This makes me believe that the phone has literally no other files on it other than TWRP. So I tried to find some way to get those files, and that managed to lead me to flash the boot.img for the phone. Now it booted up and has been stuck at the HTC boot screen with the "powered by Android" logo at the bottom and the red text. I've held down volume down + power for 5 minutes and it did nothing; the lights just kept flashing. I'm going to take it to Sprint tomorrow and say I was trying to get it back to stock and the RUU screwed it up. Sprint is supposedly pretty cool about mods and rooting, so hopefully they can help me out.
Click to expand...
Click to collapse
Try the command fastboot erase cache then reboot into twrp and reflash rom
Sent from my HTCONE using Tapatalk
thicklizard said:
Try the command fastboot erase cache then reboot into twrp and reflash rom
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Oh man, I can't tell you how many times I did that. I also ended up flashing a stock ROM. Then, it would boot, but after booting, be stuck on an uninteractive HTC logo screen. In order to do anything, I had to unplug it to get the critical better warning, then click more info, allowing me into the settings app. That really got me no information, so I ended up just giving up and trying to get it back to as close to stock as possible. I was able to get rid of the tampered notification and the red warning text, but I couldn't get the Superuser to work, so I had to live with it not being fully locked and settle for it saying "relocked". The I went back to S-ON, factory reset, then brought it back to Sprint.
They said it was water damage.
***** please.
However, that meant I could take to to geek squad with that excuse because we have their insurance plan (which covers water damage!) and they didn't even bother checking. So now I'm using my old Galaxy Epic 4G running 2.3.6 until a new phone ships in.
The worst part of it all is that my dbrands aren't sticky anymore, so I'll have to use the phone naked until February when I get a Nexus 6. I bonded with those dBrands for over a year. They were the life of my phone!
At least I'll get a new set of headphones, which I conveniently broke the same day I lost service.
Hi everyone, let me lay out my issue.
I was running the latest Temasek CM 12 on my unlocked & rooted XT1096 and starting about 2 days ago I could no longer get any 4G connectivity, only 3G. I fiddled around with the mobile network settings and even went into the *#*#4636#*#* radio settings but could not get 4G back for the life of me. I tried restoring a nandroid of the stock rooted image I had, and it worked for about a minute. It would show a 4G connection and would let me browse the play store and whatnot, then after a minute or less it would disconnect and show no service (not even 3G). I tried flashing a clean install of the stock rooted image and flashing a clean install of Temasek CM 12, but neither would get any connection at all.
I even took out my SIM card and popped it into my old Galaxy Nexus and it works fine connecting to 4G.
It seems like my phone was dropped from the Verizon network or something. What should I try next? Revert back to stock?
Thanks!
here are some screenshots that show exactly what I'm seeing
So it looks like it might be a hardware issue with the radios. I went to the Verizon store and got a new SIM card, but it still only connects for about 20-30 seconds after inserting the card before disconnecting all service (data & voice). The new SIM card still works perfectly in my old Galaxy Nexus. I am at a loss...I guess I'll have to get a new phone
EDIT: I somehow fixed it! In a desperation attempt, I booted into the bootloader and re-flashed the radios
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
then I booted into a clean flash of CM12, but no luck. So I tried restoring my nandroid of a working stock rooted image and that seemed to do the trick. I received a message from Verizon saying: "An update has been made to your device to improve network performance, please power cycle your device at your earliest convenience." I rebooted and 4G LTE data seems to be back in action!
Hopefully now I can clean flash CM12 again and keep data working.
amd_h4x0r said:
So it looks like it might be a hardware issue with the radios. I went to the Verizon store and got a new SIM card, but it still only connects for about 20-30 seconds after inserting the card before disconnecting all service (data & voice). The new SIM card still works perfectly in my old Galaxy Nexus. I am at a loss...I guess I'll have to get a new phone
EDIT: I somehow fixed it! In a desperation attempt, I booted into the bootloader and re-flashed the radios
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
then I booted into a clean flash of CM12, but no luck. So I tried restoring my nandroid of a working stock rooted image and that seemed to do the trick. I received a message from Verizon saying: "An update has been made to your device to improve network performance, please power cycle your device at your earliest convenience." I rebooted and 4G LTE data seems to be back in action!
Hopefully now I can clean flash CM12 again and keep data working.
Click to expand...
Click to collapse
I think I am having the same issue as you. At some point in time between flashing different roms, including using Sunshine to unlock my bootloader. my phone started receiving only 3G--never 4G. I tried reflashing different roms multiple times, factory reset, flashing different modems, delete modemst1, modemst2, DDR, flash fsg but nothing would work.
I tried an app called Radio Switcher, and using that I was able to get it to get 4G signal, but only for 10-15 seconds. After 10-15 seconds, all signal is lost, no bars/voice, absolutely nothing. If I toggled airplane mode, it would then give me 4g again but it would lose everything again after 10-15 seconds. I reflashed a 5.1 radio and was able to get 3G back, but now I'm back to 3G only and never any 4G. I tried swapping in my brothers known working 4G LTE SIM card, but no dice--same exact result.
Cliffs notes:
1. Phone would only receive 3G signal.
2. Was able to get 4G for 10-15 second intervals but then all signal is lost (no voice etc)
3. Was able to get 3G back (step 1 status) but no 4G at all.
If this sounds like your issue, can you link me to the NON-HLOS.bin modem and fsg files that you flashed?
Thank you
RyanBRZ said:
I think I am having the same issue as you. At some point in time between flashing different roms, including using Sunshine to unlock my bootloader. my phone started receiving only 3G--never 4G. I tried reflashing different roms multiple times, factory reset, flashing different modems, delete modemst1, modemst2, DDR, flash fsg but nothing would work.
I tried an app called Radio Switcher, and using that I was able to get it to get 4G signal, but only for 10-15 seconds. After 10-15 seconds, all signal is lost, no bars/voice, absolutely nothing. If I toggled airplane mode, it would then give me 4g again but it would lose everything again after 10-15 seconds. I reflashed a 5.1 radio and was able to get 3G back, but now I'm back to 3G only and never any 4G. I tried swapping in my brothers known working 4G LTE SIM card, but no dice--same exact result.
Cliffs notes:
1. Phone would only receive 3G signal.
2. Was able to get 4G for 10-15 second intervals but then all signal is lost (no voice etc)
3. Was able to get 3G back (step 1 status) but no 4G at all.
If this sounds like your issue, can you link me to the NON-HLOS.bin modem and fsg files that you flashed?
Thank you
Click to expand...
Click to collapse
try using the latest 5.1 files found here http://motofirmware.center/files/file/253-victara_verizon_51_lpe2332-25-3_cid2_cfcxmlzip/
Not working for me. Have to decide if I want to live with 3G or upgrade to a nexus 6p.
Phone: Mi 5 64gb
This is crazy guys, after I flashed LOS, I wasn't able to connect to the wifi and whenever I do, the phone causes to reset and ruin the Internet for every temporarily. I thought it was just this phone so I went to shop and switched for a new one. And as soon as I flashed RR, guess what? Same thing happens. I'm so lost, what did I do wrong? These are the steps I took to flash custom ROMs. First, I unlocked bootloader and flash TWRP 3.0xx recovery. Next, I factory reset, wipe cache system data everything and flashed firmware, then ROM, finally the Gapps. I tried to flash back to official ROMs, the problem remained. I'm so screwed, don't know if the shop gonna let me switch to a new one, again.
P.S. on the bright side, I can mess with other's Wifi, make them unusable.
P.S. 2 during zip installing in TWRP, I saw two red lines like this "E:unknown command [log], detected filesystem ext4 for /dev/block/bootdevice/by-name/system, script succeeded: result was [1.000000]..." but it said done regardless