Develop Bugs

ATT Tilt 2 went to red, green, blue, white screen; how can I flash a cooked Rom to it

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.

Weird bricked GT-I9195 stuck on black screen after Samsung logo

So, unluckily today i find myself here lookin' for help with my phone. I had already took a look on other brick threads, but i can't find an appropriate answer to my problem.
I'm (i was) running lineage-14.1-20170602-nightly, i had ne0zone75's TWRP 3.1.0.0-0, and that's how the brick came in a strange way; i was simply on XDA Labs app browsing the forum, when i received a call. I've answered, and when i shut off the call the phone shut off immediately after. I thought it was a reboot, but keeping pressed the power button didn't switched on the phone anymore. So i've tried to remove the battery and re insert it after some minutes, but the only thing i can get is the screen with the samsung logo that goes all black after 5 seconds. I already had other bricks due some errors of mine in the past, but this time it's really difficult.
1: I can't access recovery mode. Ow, how i wish i could.
2: I can access download mode, but after that i reach the ODIN MODE screen with the details of product binary, KNOX, ecc. the phone shuts off again.
3: If i keep the power button pressed, the phone doesn't starts. It only starts if i replug the battery in, but after some seconds it shuts off again.
4: How could a call as another mess up the whole phone?
5: I didn't installed nothing new from at least a week... yesterday an automatic update of the Play Store took place, but except that nothing has been changed. Nothing of nothing! No settings, no apps...
What could i do? Installing Kies with Samsung drivers could help me flashing a stock rom for example? Because at the moment, there isn't too much that i can do with the phone in this state... I hope this little jewel won't have to become a stone to be thrown away. Any help would be great, and really appreciated. Thanks in advance...

Things has got worse. Now my device doesn't starts at all; no vibrations, no signs of life, nothing. I've tried even to put it for 6 hours in my refrigerator, because i've read that the cold temperature could be helpful to fix some broken contacts on some component, but i'm losing hope 'bout it. I supposed that at this point is something hardware-based and not software, because it's just impossible that a call like an other one could be the cause of this hard brick... The only thing is that if connected to my PC, it is being showed as QHSUSB_LOAD. I'll try some methods that i've seen in other forums, like softwares that tries to fix this, but i think that i'll be forced to buy a new device. Neither an usb-jig could help me to force the download mode if the phone is dead in every aspect... the only thing that i still didn't understood, is if a debrick.img on my SD card (sadly i've read that a microSD class 10 with at least 16 GB is required, and i don't have one) could help somehow on a situation like this one of not. Still no one could advice me with some tip, guys
Edit - feel free to close this thread, I have another phone now

Samsung Galaxy S7 Software Issue

Hi,
So a few months ago I regrettably decided to try and root my Samsung Galaxy s7. It did not go well, and from the feedback from the firm I sent it for software repairs, apparently a second partition was created which caused start-up issues. They said they fixed it and for a few months the phone worked well. Until now.
The phone refuses to startup. It is currently plugged into the mains and showing a steady 51% (which I know from previous experience will be the maximum it reaches) If I press the power button it goes through the loading screen (the animated Samsung logo) then shuts off, then tries again and again never making it past this point.
The things I've tried:
Tried every kind of reset
Run the restart process with every combination of sim card, sd card and lackthereof
I remember that the guy that fixed my phone offhandedly commented that he could see the issue on his PC, presumably via a software of some-sorts. Anybody know what this could be?
So, nothing seems to work and in a last bid of desperation I googled the issue and came across this website.
Perhaps a kind Samaritan here might know how to fix my issue? Any help would be greatly appreciated.

CorrinRoth said:
Hi,
So a few months ago I regrettably decided to try and root my Samsung Galaxy s7. It did not go well, and from the feedback from the firm I sent it for software repairs, apparently a second partition was created which caused start-up issues. They said they fixed it and for a few months the phone worked well. Until now.
The phone refuses to startup. It is currently plugged into the mains and showing a steady 51% (which I know from previous experience will be the maximum it reaches) If I press the power button it goes through the loading screen (the animated Samsung logo) then shuts off, then tries again and again never making it past this point.
The things I've tried:
Tried every kind of reset
Run the restart process with every combination of sim card, sd card and lackthereof
I remember that the guy that fixed my phone offhandedly commented that he could see the issue on his PC, presumably via a software of some-sorts. Anybody know what this could be?
So, nothing seems to work and in a last bid of desperation I googled the issue and came across this website.
Perhaps a kind Samaritan here might know how to fix my issue? Any help would be greatly appreciated.
Click to expand...
Click to collapse
You are at wrong forum. If you are new to XDA, then let me tell you, XDA has device specific forums, means we are discussing only one device here, help for other devices will not be provided on different device forum.
Click the following link, it's Galaxy S7 (see guide section, it will have flashing guide of Stock ROM) : https://forum.xda-developers.com/galaxy-s7

I need a software can be used to manager all the data of my Android phone ,

Note 10 Plus Qualcomm D2Q in sporadic boot loop..

I've been running the latest update on the d2q Note 10 welcome it's a n975u1, and I've been running ice box as my device owner as well as revenant and also use a box to keep my apps under control, very conscientiously I must add.
Ever since the last update was ready to be installed I was trying to put it off because I was hoping to get off on one of those new routing techniques that keep telling me that I can't update my system Os or I won't be able to get it done, so I kept putting it off, but with each day my system kept getting more and more strained and suddenly just begin going into a straight boot loop going from the startup screen with the Android name printed across the screen and then saying it was booted and has been reset and then immediately going straight back to that Opening screen with the Android logo on it and repeatedly doing it until I catch it at the right time to Power It Off. My question is is there any way that I am going to be able to get around having to do a factory reset on this device or does anybody have any other suggestions that may circumvent this tedious measure at this point? I've been routinely wiping system cache, make sure I got all my backups ready to go during the periods of time that it doesn't go into bootloop,(which seems to be usually once a day for a few hours it will operate just perfectly until just suddenly shuts off with no warning signs). I was also able to get onto the Verizon update app via ADB download mode and they ran a scan on it and determined that they could fix my device if I were to leave it plugged in and allow them to do it. Theresa in the process of the repair that they said needs to be done. They didn't say what this repair would consist of, so I have no idea what is the real issue here. I've been trying to get as many system debugging reports as I can pick up along the way from various apps that record crashes and such but not sure really how to process that information to be able to determine what exactly the issue is. I'm at my wit's end and just about to point to just go for it the factory reset as much as I hate to do that! I think that I have Extreme Complex post-traumatic factory reset disorder and would do just about anything to avoid having to go through this again! If anybody has any advice I would very much appreciate it and I hope I'm posting in the right for him because all these Note 10 forms get kind of confusing when you got all the various processors and countries and all the other factors that you have to where to figure out where you're supposed to be asking a question here! LOL sorry, thanks!

Power management apps and launchers can boot loop you fast... so I learned
I get good run times with no power management on my stock N10+, but it's heavily optimized and I am using a package disabler.
To fix it you'll need to edit the offending apk(s) out of the boot sequence. I haven't a clue how to do that. The power management app is the most likely suspect though.

Need Help, Bootloop issue...

Hello,
New to the forum, at least posting have been lurking and reading for years, but this will be my first post.
Mi 10T Pro, stuck in bootloop. I have been trying to get it going again and have been having no luck, so I decided it is time to turn to the pros for some help.
Symptoms:
Bootloops 1 or 2 times to the MIUI logo, then boots to the recovery menu
Not possible to turn of completely, bootloops until battery drains completely
Able to get to the fastboot menu
What I have tried:
I had a suspicion that it was a problem with the power button, so i replaced the ribbon but no improvement (Unless new one is bad also?)
Replaced Battery, no improvements
Tried all the button press combinations to try and do hard reboot and so on
About Device:
Software version: Unknown as the phone broke a long time ago, got a replacement and the phone has been sitting in the drawer...
Phone was never rooted or unlocked in any other way
The phone is open and I could unplug battery or try a new ribbon for the power button (I have a new one on hand)
What I would like to achieve:
Save the data that is on the phone.... This is the main thing I would like to do as there is precious pictures of my young kids and so on....
Get the phone working and use it as an emergency device
Options I think are still available in order of how I would like to attempt them:
Do a software recovery, by installing a stock rom, example: (
)
I don't know what version of rom to download as I don't know what version the phone was on
I don't know if this will work since the bootloader has never been unlocked
Anything else possible before next step?
Reset through the reset menu. and cry over all the lost data (
All suggestions are welcome.
Thank you!

this phone is notorious for needing to be reballed after a few years of use. its a trash phone. join any mi 10T groups in facebook and youll see countless users who had to pay specialist technicians to reball their CPU and Memory chips and even then, they still fail after a few weeks/months.

Thank you for your answer ongkal. So you don't think its worth to try to overwrite the loader? I don't want to have to reball if its a software issue, but will if it comes down to it.
Mainly just want to get the files out, went back to samsung after first phone with xiaomi...

I was just looking at the reball videos on youtube and most of the phones are completely dead, mine still turns on but straight into bootloop. Besides they say it might be due to gaming, which that phone has not seen