Related
Hi,
Right in the middle of use, my ATT Tilt 2 went to a basic, dead screen with red, green, blue, and white bars that says Rhod300 32m SS-BC, etc.
The operating system seems have gone down--it won't respond to anything. Hard reset produces the same results.
Can I flash a cooked or official Rom back onto this? I think activesynch is needed for a normal flash and of course I can't use active synch with the phone in this condition.
I think probably what I need is an original ROM install. Is this possible with a normal Windows 7 PC and a dead phone?
I have so many Windows Mobile programs and peripherals that I am trying to avoid going to Windows Phone at all costs--at least until they have basic stuff like file systems, a way to port over notes, etc. Also need a hard keyboard.
Right now using an older Fuze, which works, but is slower, worse screen, smaller, and lacks some of the features I like.
Thanks for your help.
You sound like you're in the bootloader mode. Tri-color screen.
You can flash from USB or from SD at that screen. I'd recommend trying to flash a stock ROM - as it flashes everything. Assuming that works, hopefully you can flash back whatever ROM you were on.
The phone isn't dead if you're at the tri-color screen. It should say 'serial' at the bottom - when you plug in your USB cable, it should say 'USB' and install some drivers. Then with the RUU software that comes with every ROM, you should be able to flash it.
Phone won't reboot--stuck on tricolored boot screen
Hi,
Thanks so much for replying. I appreciate you pros helping us novices.
Just after I posted the first note, I pulled the battery and hit the power button, it rebooted, and everything was still there in the OS--working fine. But whenever the device had to be rebooted, I would have the same problem of it getting stuck in the boot screen. After that, for the last several days once in awhile, randomly, it would finally reboot from the boot screen after I pulled the battery and hit the power button. The rest of the time (about 5/1) it would just sit there in the boot screen no matter what I did. The "Serial"/"USB" thing would change when I plugged it in, but that's all.
Thought it was the OS, so at a lucky moment where the "pull battery, hit power button" strategy actually worked, I installed the latest official HTC/ATT Rom--it's the next to last one issued that ends in .4.
It was gorgeous and I got all excited--started installing stuff thinking my problem was solved.
Had to reboot to install some programs--now it is stuck again on the boot screen. Tried 30x again--no luck with the "pull battery/hit power button"
strategy. Sometime it would flash a white screen really quickly saying something like "Can't read image!" before going into permanent boot screen. The boot screen will switch from "Serial" to "USB" if you connect it to the computer. So, the problem doesn't seem to be in the OS--rather, in the ability of the device to "read" the OS from the boot screen.
I would be grateful if you or anyone else may know what's going on here, and any ideas on how to fix it. Is there any manual way to get it to read the OS from the boot screen when that's not happening?
I have two guesses (both of which may be wrong):
1. It may be something in the hardware is just worn out and is less and less able to read the Rom--any ROM. I got the phone new off Amazon for a profit of $50 ($.01 cost plus a refund for an older phone) in the summer of 2010 when it was already outdated. and WP was replacing WM. I've certainly gotten my money's worth after 18 months!
Of course we now know that a brand new ROM has the same problem as the older one--which suggests to me it's in the hardware. I'm sure the new OS and the stuff I installed is still there on the phone, but something it appears is not reading something in order to allow the boot up.
2. I have a squirrely free program called Rax Reset (from Windows Mobile Marketplace) that does a software-based hard or soft reboot from inside the OS. The very last time the device went down and didn't come back up, I had used that program to soft reset it. Might have been a big mistake. Could this program be causing the problem? If so, just one reboot would allow me to get rid of it or even hard reset to remove everything but the new OS--but can't get it to boot.
If it turns out the phone is just worn out, I've certainly gotten my money's worth.
I still love WM even with all its problems--and especially the newer Sense version. If this one is shot, I'm thinking about just buying a new Touch Pro2 on Ebay to avoid all of the sacrifices and backwards steps involved with Windows Phone.
Thanks for any help anyone can provide.
Phil Butin
Why are you crossposting? I read this EXACT same post in a thread just below this, in the same section. That's pretty low.. Crossposting across forums isn't welcome, crossposting within forums IN THE SAME SECTION is definitely not welcome.
Don't do it again.
Sorry, just trying to get help
Sorry, just trying to get help, not that familiar with the rules.
I searched on "bootloader" and found a thread (wrote a comment there too), but it's old....
Here is the thread. It doesn't really provide any solution.
HomeArrow
Legacy & Low Activity DevicesArrow
HTC Rhodium: Touch Pro2, Tilt 2Arrow
Touch Pro2, Tilt 2 GeneralArrow
issues with bootloader.
Either way, whether you know the rules or not - why would you think copying and pasting the exact same words in the exact same forum help you any more...
Anyhoo, have you tried the usual? Flash stock? Sometimes I've heard you have to flash several times, I never really understood that logic tho.
I'll try to reinstall the HTC/ATT Sense OS again. I guess you're saying active synch doesn't need to be working in order to do that. I'm at work now--have to wait until i get home. Nothing to lose at this point.
But I'm seriously wondering whether the problem is the OS install or whether there is something in the device that is supposed to read the ROM and start the bootup that is just wearing out.
Thanks.
"No Image File"
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
[email protected] said:
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
Click to expand...
Click to collapse
That error message is 'normal'. Basically the phone checks the SD card for a file labeled "RHODIMG.nbh". If said file exists, it will flash from it. If no file exists, or no SD present - it continues loading bootloader and should say "Serial" at the bottom. This indicates that it's ready to be flashed. If you plug in your USB cable, it will install some drivers and then it should change to "USB" at the bottom instead of "Serial".
Now you should be ready to flash from a normal RUU. I would recommend flashing STOCK, because this flashes everything.
It might also be good to note a lot of people have experienced something similar - the phone getting "stuck" in bootloader mode, and only occasionally making it to WinMo. I'd guess it's failing hardware in some way shape or form, as none of my RHOD's or RAPH's have ever done this.
Good News--at least for now
Good news--I hooked it up to the computer with the USB cable for awhile and the Windows 7 computer did set up some drivers. For some reason after I disconnected it I reset it, and the reboot worked. Then I immediately uninstalled the squirrely reset program and removed it.
Everything I installed yesterday is working fine--I have soft reset it about 5 times now and each time it has rebooted. So I think maybe I'm back in business. Too soon to tell--but we will pray and keep our fingers crossed.
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
[email protected] said:
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
Click to expand...
Click to collapse
You're welcome. Basically if I or someone else posts something helpful, click the "Thanks" button under that post.
15 hours later, Tilt 2 is still working fine on the newly installed Sense OS. I have rebooted freely (using the stylus button on the side) since removing the program "Rax Reset," and everything seems to be going well. I'm keeping my fingers crossed, and will end my contributions to this thread with a warning about using "Rax Reset."
Thanks to all.
I had a bone stock Verizon Samsung Galaxy Nexus which suddenly began to boot loop last week after receiving a text message.
(1 year warranty is 1 month past)
Upon attempting to do do a factory reset via fastboot - clear everything. start from scratch. I am presented with what seems to be a working phone however if you move through the screens too quickly the phone will reboot.
I have since tried putting several different roms on the phone including flashing back to the stock original all present the same results.
When the phone finally comes up. I wait approximately 10 seconds in between each screen tap otherwise the phone will restart.
does anyone have any insight on this. I have been searching since Saturday night for similar issues/fixes but nobody seems to have mentioned this.
Is there a way to do a hardware test on the phone to see if it is in fact hardware related vs software related?
Thanks in advance for your time and help.
-Nick
focusedonsound said:
I had a bone stock Verizon Samsung Galaxy Nexus which suddenly began to boot loop last week after receiving a text message.
(1 year warranty is 1 month past)
Upon attempting to do do a factory reset via fastboot - clear everything. start from scratch. I am presented with what seems to be a working phone however if you move through the screens too quickly the phone will reboot.
I have since tried putting several different roms on the phone including flashing back to the stock original all present the same results.
When the phone finally comes up. I wait approximately 10 seconds in between each screen tap otherwise the phone will restart.
does anyone have any insight on this. I have been searching since Saturday night for similar issues/fixes but nobody seems to have mentioned this.
Is there a way to do a hardware test on the phone to see if it is in fact hardware related vs software related?
Thanks in advance for your time and help.
-Nick
Click to expand...
Click to collapse
Anyone have any ideas.
focusedonsound said:
Anyone have any ideas.
Click to expand...
Click to collapse
I think it's just an hardware problem.
Something happens when a part of code is executed and the hardware does not respond correctly.
Similar problems happen with desktop computers, a faulty memory module, for example may create a reboot due to the error, or making a driver to crash. These smartphones are little computers...
This is what i think IMHO. I'm a computer technician.
PS. Maybe when you scroll faster the cpu goes at an higher frequency an becomes instable, did you overclocked it in the past? Try to lock the frequency as lower as possible with a custom kernel and verify if the issue appears anyway.
Anyway I'll pay a lot of attention flashing a new kernel or recovery on an instable phone, if it reboots during flash you may brick your device!
I hope this helps.
Thanks for the reply,
This is kind of the theory that I had but I didn't want to make any assumptions. With my computer background I am very familiar and understand how to trouble shoot problems with a computer. However phones area whole new cup of tea.
The phone resided in an otterbox which could have led to overheating and ultimately the processor going bad. I am no so quick to flash a new kernal etc to restrict the frequency.
The thing that I find most odd though is that there have been no similar functionality reports.
-Nick
Hey guys, wondering if anyone is able to create a recovery image for me to download of 8.1+update 1.
My surface rt wont boot past the surface logo. I can't find my usb drive that had my restore image but on top of that it was 8.0 anyway. I checked the ms website and they only host an 8.0 image as well.
At this point I am willing to try anything. I did attempt to download and boot to the 8.0 recovery image by inserting the usb drive and holding power and volume down until the logo came up, but so far doesn't seem to do anything. Am I completely hosed?
long version:
About a year ago, my surface started performing really poorly. Basically any swipe gestures would either not work or they would be extremely delayed. The animation would also be delayed. Other things would be really slow for instance, in IE tapping inside an address bar wouldn't load the keyboard for about a minute. PS 90% of my activity is on IE reading news or watching youtube.
Several months back I finally noticed that anytime I would start experience these issues, the disk usage in task manager would be pegged at 99% even though the read might literally show only 14 KB/s and the write might only be 1 MB/s. The biggest flag though was the response time was always in the thousands of ms.
I pretty much lived with the problem and often a restart would seem to make things happy for a while. And I usually leave task manager open so I can peek and see the utilization anything things feel sluggish.
Last night it was behaving worse than before. I managed to navigate through the charms and attempted to restart. But after waiting several minutes of it just saying restarting with that circular loading image decided to force the issue and I held down the power button until it shut off. It only said restarting, not installing updates or anything like that. I waited way longer than it would have reasonably taken and under normal circumstances, if it was installing updates, it is very obvious and the messages are clear. Plus the charms power option was simply restart, not update and restart.
Sadly when I tried to power back on, it just gets stuck at the "Surface" logo and doesn't do anything. I waited 10 minutes and forced the power off and tried again. It was late so I decided to go to bed, but left it running in hopes that it would eventually boot up. I woke up 4 hours later and it still showed the Surface text on a black screen. At that point I decided to shut it off.
I had already installed update 1 last week, BUT just in case it is some kind of failed windows update. Is there anyway to "reinstall" from this state?
Gonna be extremely bummed if my device is permanently bricked.
If memory serves, I'm pretty sure I deleted the recovery partition BUT I have a flash drive that has the backup, although it would be an 8.0 backup not 8.1.
Restore to 8 then update?
drearyworlds said:
Restore to 8 then update?
Click to expand...
Click to collapse
It doesn't boot from the 8.0 image. Not sure if its cause it's completely hosed or because it needs 8.1. I'm not getting the boot record problem as reported by people when 8.1 first came out.
My tablet recently began entering a locked blue screen state devoid of text or icon. It holds there for one to three seconds and then reboots.
Prior to the start of this rebooting sequence trend I downloaded and installed the stock ROM listed on my signature, hoping that it would alleviate some issues with delay in screen tap response, some occasional heating during gaming along with what I perceived to be a little bit of driver related lag.
I haven't figured out when, why, or how it decides to reboot. But as far as I can tell it seems to be related to [behind the scenes machinery of] Google Play (GP). I suspect this because it has happened when I've launched GP or GP tried to do some updates or software installation.
Incidentally, though possibly unrelated, when I try to add an account via settings, at the sign in page, the device returns unable to sign-in message citing connectivity issues. I am in China, so I suspect this could all be related. To get around this issue, I log into a VPN service. This allows me to sign in and add the account to the device. However, in order to play any games, I must log off the VPN. But once the account has been added to the device, it more-or-less is able to access some of the Google services (at least the ones not outright blocked -such as drive and YouTube).
In my troubleshooting attempts, I have thus far done a cache wipe and factory reset from the boot menu. All to no avail.
At this point I need to live in constant fear of a sudden reboot, for I know not when it will strike next.
I would appreciate some suggestions on either what the issue might be, how to determine the cause, or how to solve it.
Thanks
Funny story...
So Kitkat has been released, for the TGY country code.. Yay!
P605ZSUCNE3_P605OZSCNE3_P605ZSUCNE1_HOME.tar
Is the md5 file to be put into the AP slot of Odin 3.09, for my tablet.
I was excited thinking this would address the issue.
Prior to flashing the ROM I factory reset from within the settings, then I went into the recovery boot menu and there I wiped the cache and did a factory reset once more.
Then I proceeded to setup and sign into my Google account, after flashing the ROM.
Naturally the tablet went ahead and started downloading and installing apps and updates from Google Play.
I was happy to see that it was progressing along swimmingly.
The screen dimmed down and then shutdown after period of inactivity (while downloading and installing apps in the background).
Occasionally, I'd click the home button to see tat everything was going as it ought.
I then noticed the screen turned black somewhat suddenly, without dimming first.
I thought little of it.But I went to check by pressing the home button... I figured maybe there's a little lag or the tablet is too busy installing, so I clicked the power button. Nothing; no response.
The tablet is deader than dead.
Now I don't know what to do.
After waiting a while, under the advisement of another user who apparently has also been having issues with his note 10.1 2014, I decided to try to long press the power button. The tablet came back on, and resumed downloading and updating from Google.
But now the tablet is going into this sudden blank blue screen and most of the time rebooting on its own (occasionally it needs a little help, by the pressing and holding of the power button to induce the reboot) ever so randomly. I have found absolutely nor rhyme nor reason for when or how it decides it's going to reboot itself. It tends to happen often if/when I launch some apps that require logging into Google services; but at times it happens without provocation -at all.
Recently it's been boot-looping -without the launching of any app... just from turning on, sitting idle, and then rebooting. But I'm no closer to figuring out how to consistently induce the reboot, either.
My tablet has never been rooted (and for obvious reasons, never will be), no custom ROM, no ROM from another region. Nothing that would give Samsung the excuse to void my warranty (not that it's worth much, here in China).
And yet, it still reboots at random intervals for no immediately apparent reason.
In any event, if anyone has any ideas on how to proceed, any suggestions on what to do with this POS, I'm open to suggestions.
I'm interested in general ideas such as take it to the Samsung shop (something I'm loathe to do because Samsung has terrible service -especially in China- and at best I'm looking at a month or something like that before I get it back), so some ideas on how to discover when/why/how this rebooting sequence is being triggered -and maybe troubleshoot it is slightly preferable.
[Q] LS980-Cloudy G3 ROM- TWRP installed&accessible- [email protected] Android is Updating screen
Hello everyone,
I would like to say first of all to the community, thank you for SHARING KNOWLEDGE. That is the key to everyone's success.
Now down to the gritty. My, now, I guess, mess of a LS980. For starters, the phone was running I would say very well considering my abuse. Big overclocks, gaming hardcore, and pushing the storage space hard. I performed a very easy and simple rooting and recovery program installation. If I remember properly, it all started with an app/.apk that sparked my interest with making the phone mine, was Autorec? (red roundish logo?) In some time I decided to install my first aftermarket ROM. I chose and installed without any issues , Cloudys G3 ROM. I cannot however remember the version number. It is by no means recent. I think I installed it last September so maybe 1.0 or 1.2 (sorry so much bad luck with stuff recently) TWRP version 2.7.0.0 is my recovery, and its functional. Unfortunately I do NOT have my apps backed up. I have no space. (just managed to get about 7GB on this PC to try to back them up but there is not external back up option, UNLESS you are OTG cable equipped I am not )
Now, I think, (this has been the state of the phone for about 3 weeks now) this all started to go south when I saw there was a Dorimanx OTA app in the play store. I used his Kernel for as long as I have had the G3 ROM installed. With no problems. So I figure this would be easier for me than button mashing trying to get into recovery mode without popping my screen out the front. LOL Upon using the app, I was informed of an update, I read the included information, and generally knew the deal. I allowed the app to download what it needed and restart and install like a good little computer. And this is where it gets a little grey for me in terms of order and symptoms. I remember checking the status of the install and it read failed! I looked into the reason why, and I was just plain full of junk. I then uninstalled painfully a bunch of rarely if that, used apps and gained back about 2.2GB of space. I ran Dorimanxs app again and let it do its thing and reboot. And again it reported fail! I looked into it more and noticed there were newer Kernels than available on his inter-web. Alpha versions. I located them on my device and rebooted into TWRP mode and selected , then flashed his 10.4.1 Kernel. Everything went fine. Phone reboots, the LG logo is no longer animated, and takes a bit longer to actually boot into a GUI. But it was, luckily.
So now, the phone would be a usable thing for about 3 minutes tops, before a power off, to a reboot. Which at first I didnt notice to be a boot loop. My battery surprisingly went from full to about 6% in no more than 15-20 minutes. I noticed the battery was getting warm like I was running the CPUs maxed under a serious load for a good half hour. Around the range to make someone pull it out their pocket wondering wth? So after the next reboot, power cycle, I jumped back into TWRP mode, and dug around for what I thought was the culprit, Xposed. I was having the worst time with my phone after a major Xposed framework error. I picked up my phone one day and out of the blue the xda framework was telling me that there were so many errors with it and my apps that ran fine, not being installed or activated. Upon looking into it, it was removed from the phone. I belive the order was , stable, 2.5/ 2.6, then I tried the beta 2.7. and thats the version that eventually , either broke, or uninstalled, I think, during those frequent Crashes! I tried to install the previous versions, even going back to the versions that came out last year like 2.4 . But none would install. And the phone grew more unstable in terms of its cooperation with its software. My normal apps and games worked fine. The phone worked the same, the music player, but there were apps that only can work with xposed that I utilize constantly, that were kaput. So I left the phone off. For a while. I had/have no time and really no resources to research and rescue a sunken ship. I come back about two weeks to it and I take a look around in the phones storage and hunt for any kind of recovery and disabler. I found xposed's disabler and flashed it. Same luck as before. About 3 minutes on, then dump.
I dig some more and found a ccc71 back up folder with some hearty backups that I didn't know were still there (no wonder I was always loosing space) and found another xposed installer.zip . I figured well , it didn't make any sense trying to disable something that wasnt enabled in the first place. (thats why I walk away and come back . fresh mind to tackle what stumps me) So I flashed the installed zip and reboot. Same thing, but now it started to loop around one minute. I power down. Found the recovery.zip that was saved on the beater PC and adb pushed it over the the phone. Im not good enough to adb install it. So TWRP'd it and rebooted, and d'oh! Now we just have the motionless LG ball, but flashing blue and green LED. And after about 2 minutes it would black screen, but be on. Not hung or anything. I connected to the PC, it never finds the right stuff but I used adb to verify state. And it said device. It still could communicate and push. I had it dump its debug, surprise! as it flashes that crap as fast as it can up the screen. But Im a PC guy so it was a fun, pause/break over and over till I found something useful. I saw some things that I could recognize like, failed starts, and longer than normal (for a speedy experience) function or call times, but nothing that slapped me with a red flag.
And that ended that nights attempts to fix thanks to the slowest no ram having box I was using to try to learn how to have the debug save to a .txt file on my PC so I could take a good look at the results.
Upon reading forum after forum, I came to something that looked promising, telling me that, that particular boot issue was due to the wrong radio being installed. So I hunted, and hunted, and laaaaaged my arse off and finally found it. Great I thought. Powered up ten or twenty times, finally get into TWRP, tried to flash it. BBBBBAAAAAANNNNT! nope. Downloaded another copy of the file and tried it again. No luck. ( I must say not until roaming around in these forums tonight did anyone bother to mention that you dont flash that radio. You instead have to inject it via LGFlashTool, which I have used before, and its a pain in the butt.
But before I go any farther, make anymore mistakes. I need some help.. I would really LOVE to be able to flash this , slap that, curse its name then hug it and get her working, without having to ditch my 492 apps. If I would have to say goodbye to happy times, I would like to say good riddance to ugly and annoying G3 ROM. I like not flat UI. My phone was depressing me every time I had to do any navigating around inside it. So I would love to go back to KK Stock LG ROM if push came to shove. But if possible I would just like to "repair, and regain access into the phones GUI system". So I could backup my apps. And eventually labor back to OEM Kitkat.
I apologize for the length of the post. But I just dont see the point of ping ponging with partial exchanges of information. I hope I have made my situation clear, and someone knows of someway, I can get my GUI/phone working again. Thanks to all in advance.
"a non functional smartphone, is an oxymoron"
Upgrade twrp to the blastagator last and dirty flash the same version of cloudy g3. And backup everything on the cloud. Mega give you a lot of free space.
_____________________________________Read more write less and be smart
strangely enough
siggey said:
Upgrade twrp to the blastagator last and dirty flash the same version of cloudy g3. And backup everything on the cloud. Mega give you a lot of free space.
_____________________________________Read more write less and be smart
Click to expand...
Click to collapse
strange thing,
just about 5 minutes ago, the phone, which I left on sitting at the LG screen by accident yesterday after posting the above, changed screens and presented me with the Launcher selection screen.
I immediately noticed that it looked wrong. Like if the resolution was way off. Like an old low res screen, very dull, sort of blurred looking.
I figured what the heck and tapped the screen and it of course did not immediately respond. It took its sweet time , about 30 seconds to show a change. The menu disappeared and a error message along the lines of , android system UI has crashed.
That is not the message verbatim, it was gone to fast for me to take it all in. And now its sitting at the blank powered on and repeating blue/green LED.
I havent done as you suggested yet. I kept getting results from Norway and other places and didnt understand a thing. But I found a TWRP update from Dorimanx, there was a link to it. And now I have to find my version of the OS. And to be clear, were you suggesting doing a re install, basically a file overwrite? And if so, when doing something like that, do you wipe the Dalvik cache ? Or do you just "dirty flash" it?
Thank you ,
I think that your screen is overheated. Never let the phone in bootloop for long time, it can destroy the screen.
About the cache, is better to clean it, but if I remember well the rom installer alredy do this.
_____________________________________Read more write less and be smart