Hi folks,
I tried updating the Radio to a new release coming from this forum (1.64.08.21).
The process stopped with no progress at about 98%. After waiting for more than 10 minutes I reset the device.
From that moment it is up only to the 4 colors screen with no luck doing any updates!!! Nothing I do or try is working, the device is just no working.
If I try updating to any ROM what so ever (including other Radio releases) the indicator bar is not moving from 0%..... and after resetting it is back to the colored screen.
WHAT CAN I DO PLS????
Many tnx,
JB
Related
I'm testing different page pools on my rom, basically my "Naked" with this being the only change.
I'm most interested in:
Storage / Program numbers after a hard reset and a couple power cycles...
General feel for operation - does the phone work?
Do the applications work?
Just a summary - I just want to be sure the pagepool is getting set properly.
Please IM me and I'll send the link....
hey
decided to post here as your more likely to see it!
been using the pandora 1.05 for a week and a bit and reboot times are really long.were talking up to and over a minute.
I downloaded your latest release thinking it was my customisations tht were causing it to slow down as such,bt its still taking long to boot.it tends to hang at the green splash sreen.
although,earlier today,I received a txt message whilst it was booting.wht I mean is,the phone vibrated but was still on the green boot screen.
wondering if you could help?
thanx.
duke_stix said:
hey
decided to post here as your more likely to see it!
been using the pandora 1.05 for a week and a bit and reboot times are really long.were talking up to and over a minute.
I downloaded your latest release thinking it was my customisations tht were causing it to slow down as such,bt its still taking long to boot.it tends to hang at the green splash sreen.
although,earlier today,I received a txt message whilst it was booting.wht I mean is,the phone vibrated but was still on the green boot screen.
wondering if you could help?
thanx.
Click to expand...
Click to collapse
I'm not sure if I had asked you before, but have you tried flashing an empty extended ROM, or reloading your carriers ROM before flashing a Pandora?
I ask that, becuase I haven't gotten (or experienced) this issue myself. I've heard of this issue causing long bootups, but not seen it personally.
I just flashed a "naked" with an 8 meg pagepool, and it took about 20 seconds.
My phone worked perfectly for a few days with ADP1.5H r3 on it, but now it refuses to boot, it seems to be looping forever. The blue android logo comes up, but the "shining" animation stops moving after usually 1-2 seconds, then the screen flashes back and the same thing repeats over and over again. I have already tried a wipe earlier, but now I'm having the same problem again. Any clues on what causes this or (better) how to fix this?
bsander said:
My phone worked perfectly for a few days with ADP1.5H r3 on it, but now it refuses to boot, it seems to be looping forever. The blue android logo comes up, but the "shining" animation stops moving after usually 1-2 seconds, then the screen flashes back and the same thing repeats over and over again. I have already tried a wipe earlier, but now I'm having the same problem again. Any clues on what causes this or (better) how to fix this?
Click to expand...
Click to collapse
Are you doing Apps to SD? It could be your card.
Did you move any caches?
Do you have any nandroid backups? (just fastboot flash if so)
Did you recently try to update to anything and fail?
Try to use the update.zip again. If that doesn't work then start over from scrap.
bsander said:
My phone worked perfectly for a few days with ADP1.5H r3 on it, but now it refuses to boot, it seems to be looping forever. The blue android logo comes up, but the "shining" animation stops moving after usually 1-2 seconds, then the screen flashes back and the same thing repeats over and over again. I have already tried a wipe earlier, but now I'm having the same problem again. Any clues on what causes this or (better) how to fix this?
Click to expand...
Click to collapse
Wipe worked for me. It was sticking on the Android flash screen, but worked after the wipe.
Yeah, a wipe fixes it. Later today I stumbled upon a thread which suggested the problem is the "Contact Owner" app that doesn't play nice. Can anyone confirm that?
In answer to binary: yeah I do apps on SD but I've been doing that since ADP1.1, so I doubt the card is the problem. Didn't move any caches. Yeah I have a nandroid backup, and all the updates I did went smoothly. I had the whole system working for about 2 days until this happened (probably, because this was the first time I rebooted since installing Contact Owner, though I can't really remember that 100%)
bsander said:
Yeah, a wipe fixes it. Later today I stumbled upon a thread which suggested the problem is the "Contact Owner" app that doesn't play nice. Can anyone confirm that?
Click to expand...
Click to collapse
Contact Owner caused my phone to go into a reboot loop, but that was on the 5.02H build. I haven't had the guts to try it on JF1.5 or 1.5Hr3. If you look through the market comments for Contact Owner you'll see quite a few complaints of the same issue.
Hi there,
And sorry for reviving this old thread. I am the developer of Contact Owner an I kinda need your help in debugging this issue. I got a small number of messages from users of custom builds a while ago (about a month or two) but thought it was an issue with those builds.
Now it came back to bite me in the ass, as it seems the HTC builds in various countries (Canada, Sweden, South Africa) have the same issue: the phone goes into a reboot loop. I've tried (and failed) to install a custom build on my dev phone (almost bricked it) so I'm going to ask nicely if someone is willing to debug the issue for me. Please, please, please!
All that's needed is to install and run Contact Owner and if the device goes into a reboot loop, simply attach it to USB, run 'adb logcat' and then post the output. To recover from the reboot loop, simply start in 'safe mode' (hold Menu down while booting) and then uninstall Contact Owner.
I suspect the problem lies in SQLite, because I've seen similar complaints from Klaxon users and that app also sets the alarm message (which then ends up in a SQLite db, I guess). The Alarm Clock app that comes with Android also does that but I imagine it's because the message set by Alarm Clock is always short and has no newlines. I also don't think the issue is in Dalvik code, because the device should not crash if managed code causes an error.
TIA,
Paranoid Android.
I recently forced the updates to get to Mango using the http://www.wpcentral.com/force-mango-update-early-through-zune-software method. I'm on step 8 of 10 on the Mango installation and it appears to have frozen. The small gray bar appears to be at 100 percent but it still depicts the do not disconnect from computer screen. I'm wondering if anyone else has encountered this problem and what I should do. Thanks.
It's possible it just froze and a restart would work.
EDIT: Well I waited for the little gray status bar to get as far as it will go. ie: let it sit there for an hour or two to make sure everything was set. The Zune software said something about a failed update or whatever so I disconnected it. Anyways took two restarts and bam I have Mango working perfectly fine on my phone. Sat a little while on the new Windows Phone logo page.
I have a HTC 7 Trophy and I managed to update succesfully, but I'm dissapointed that there's no difference from the leaked one. No IM integration from yahoo, no skype. Very little customisation
chioreanul said:
I have a HTC 7 Trophy and I managed to update succesfully, but I'm dissapointed that there's no difference from the leaked one. No IM integration from yahoo, no skype. Very little customisation
Click to expand...
Click to collapse
That was 100% unhlepful.
I have the same problem as you. I cancelled the update and disconnected my phone but now my phone will not boot properly. It vibrates 7 times and stays on the HTC start up screen.
Can anyone help us?
using an omni a 7 here, been stuck on step 6 of the process "rebooting your handset" for about an hour now. Handset rebooted a couple of times as I expected before this step but just hangs on this screen. Loading bar stick ticking on and the do nt disconnect screen on the handset but that's it.
hightower1 said:
using an omni a 7 here, been stuck on step 6 of the process "rebooting your handset" for about an hour now. Handset rebooted a couple of times as I expected before this step but just hangs on this screen. Loading bar stick ticking on and the do nt disconnect screen on the handset but that's it.
Click to expand...
Click to collapse
My Omnia did the same. Just unplug the USB cable from your phone, and then plug it back in again. Worked for me!!!
this is just from my experience.
I did have freeze the first time I updated to mango beta few weeks back on part where I had to restarted the phone. I disconnected the usb, and seemed everything was good.
but I connected the phone again, try to look for new update, and zune gave me error. the only way I fixed is by restoring to previous NODO build.
the 2 things I would make sure I have before doing any updates for wp7:
1. battery power is > 50%
2. I would make sure that screen time out is set to NEVER
since then, I never had issue with updates
I hope this helps
Edited because I found the 'fix' or work about. Everything is fine.
While on the Home screen of the Relay, I got a notification from Facebook. I pressed the Notification which would normally launch Facebook and where that post/comment which notified me was and as it opens, my whole phone screen turns blue. The color of the blue seems like the blue you would get when you have the "Blue Screen of Death" on Windows. I waited to see if it'll go away but after 5 minutes of still the in the blue screen, I took out the battery and put it back in. My phone started up normally and it said "My T-Mobile Account stopped working" so I just pressed ok. I wonder though what caused that to happen or if it will happen again.
Phone Information:
- Samsung Galaxy S Relay
- T-Mobile
-Running 4.1.2 (Jelly Bean) Stock ROM
-Rooted
-Clockworkmod Recovery
I'm planning on unrooting now because I'm kind of scared of what other problems my Relay might soon experience.
Every time i turn on my Relay it says, "Unfortunately, T-Mobile My Account has stopped working." Its getting annoying.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Ok, so I just factory reset my phone and the error message isn't popping up anymore. My phone is still rooted and I'm not experiencing any problems so far. It's probably because of an application I had or something. Hopefully no other problems will persist.
Chrizuki said:
The color of the blue seems like the blue you would get when you have the "Blue Screen of Death" on Windows. I waited to see if it'll go away but after 5 minutes of still the in the blue screen, I took out the battery and put it back in.
Click to expand...
Click to collapse
I had this same problem from time to time after the update to 4.1.2 Jelly Bean (not rooted). After suffering with it for a little while, I did a factory reset on the phone and haven't had the problem since.
So hey folks,
This is the most strange issue i've experienced with my OPO so far.. Already had many random reboots since i manually flashed 38R, but this night Bacon screwed things up.
I woke up, seeing my OPO in a boot loop, it was super hot aswell and has drained the whole battery. So i connected my charger, did a reboot.
'Android is upgrading. Optimizing apps.' - OK so far, but only a total of 106 apps (With my last runtime change to ART, it showed 188 apps..). W/e.
Now it comes. Phone boots up - language defaulted. Whole settings reverted to stock. Apps are still there, but data is lost. :crying: Media on phone is untouched.
Suddenly i see these super strange buttons - they are NOT in their usual CM11S-Design!! And i did not change any visual stuff. [Attached Screenshot of notification screen]
Top right button to switch to quick actions does not work anymore, no reaction.
Home button completely not working aswell.
Also if i shut down and charge, the charging animation is completely different and colored instead oft OPO's normal one.
Restart menu back one low-level functionality aswell..only restart and shutdown possible [Attached Screen]
It's like my phone reverted itself to half generic android.
Guys, what the Heck happened?!
I mean, i will prolly just hard reset and reflash my phone later this day, but really.. WTH is this?? Any similar experiences so far? Or any Problem solutions?
Thanks for your time and replies..
Wasnt able to post in OPO Forums so far (server error >.>) but will update this thread if i get more info.
Attached screen shows that Rom status seems normal..