Greetings,
This phone will not let me RUU it, it constantly is rebooting even during the RUU process. Then it always ends in some error. It goes thru startup, installs some apk's (always), goes into android OS and after like two minutes, restarts by itself.
Bootloader stays on, though. Can't format it from there. Factory reset does nothing.
anyone???
ruu should work as long as you relock your bootloader. try this file out in this thread
http://forum.xda-developers.com/showthread.php?t=2013122
Related
Hello all,
as the title says, one of my touch diamond's is stuck in bootloader screen.
I didnt do anything in between it working and not working, it was on my desk, put it there working, got it 5mins later, and it was in bootloader screen (tricolor screen).
What i've already done to try and fix it:
flash it with the original HTC rom, flash completes succesfully, phone reboots to tricolor screen, so no solution there.
install mtty and format the phone, this completes, reboot the phone, again goes to the bootloader.
reflash the phone with original rom after cleaning it with mtty, flash again completes succesfully but when it reboots after flashing it just goes to bootloader again.
Tried to flash a Hardspl: stuck at 0% and stays there. so that doesnt work.
BUT! when in mtty i give the "boot" command, it DOES start to boot WM. but then again, when i turn the phone of, and on again, or it reboots because of first start after flash, it goes to bootloader again. The VOLDOWN button is NOT stuck, cause when it boots i can use the vol buttons perfectly fine.
Anyone got an suggestion in how to unbrick it? i have a second, perfectly working diamond here too, if that helps in any way.
Some more info ive just seen in mtty, when i told it to boot, it said ONE BAD BLOCK IN CE, remove block ---- to ---- (dont know the exact numbers anymore)
hi..i had something like that...
just download this.
"RUU_Signed_1_93OliNex_HSPL_UnsignedEdition"
it's only 1.7MB and it's will make it work.. atleast it did the job for me...
Hi,
My T mobile touch diamond stuck in bootloader screen? Any experties to help me please.
Thanks in advance.
Hey guys,
I rooted and unlocked my HTC One a few weeks ago, then I tried to gain S-OFF on my phone (HBOOT 1.54) with the rumrunner tool. But after a few tries (it wouldn't work) it gave another error. I then unplugged my phone and put it on, but after 5-7 seconds it suddenly rebooted. It just kept rebooting ever since, it stays on for 5-7 seconds and then turns off again. Also I noticed the 'Quietly Brilliant' line isn't showing anymore when it reboots itself. I can still get into recovery mode.
The weird part is: I utilised a factory reset and then i rebooted it and the bootloop stopped, but if I turn it off it just starts again and I need to utilise a factory reset again.
Please help me, I'm tired of worrying my phone will turn off by accident.
Thanks.
My out of the box Nexus 6 is now stuck looping on and off at the Google boot screen after it tried to install the system update.
I've used the toolkit 1.9.8 to go back to stock. It goes thru the steps appearing to show OKAY and finished at each step. It never reboots the phone at the end. I try to force reboot after waiting for several minutes and it still boot loops. I try again the process again and sometimes it loops and a few times it actually starts up to the welcome screen. However, if I try to root or update recovery (using the toolkit), I get the boot looping again.
Did google bork my phone during a failed update? Is there anything else I can do to completely restore the phone? I've also downloaded the images on google and flashed---same boot loop.
Ultimately, my phone is now booting up to the welcome screen as expected and shows LRX21O. BUT, if I try to do anything (root or recovery), boot loop results again.
(I was able to unlock the phone and know about the usb debug and OEM unlock settings in dev menu, fyi).
Here's the deal, I have a sprout8 device (the Indonesian Nexian Journey One) running stock 6.0 with some xposed mods installed on it. Suddenly the device shuts down and when I try to boot it up it only goes halfway through the bootanimation when it shuts down again. I wasn't too worried as I thought it was just a conflicting system issue and I also thought it was time to re-flash fresh stock 6.0 to freshen up my phone anyway. So I went ahead and did it.
Here's where the problems start to show up, I had a hard time booting to recovery through the power + volume up combination. The phone suddenly shuts down on its own as it boots up. I tried it a few times and finally got to recovery. After that, as I flashed stock 6.0 the phone shut down again. I thought it was an issue with my recovery so I tried wiping everything through fastboot and re-flashed recovery through fastboot aswell. From there I tried again to flash stock 6.0 through recovery and again, the phone shut down. I tried a different ROM thinking it was a ROM issue but still got the same results.
After hours of trying to flash a ROM through recovery (retrying over and over as it suddenly shut down while flashing), I finally got a ROM installed. Then I rebooted my phone, but again it freezes halfway through the bootanimation (literally freezing the bootanimation) and refused to do anything. I took off the battery and booted up the phone countless tries trying to get it to boot up. When it finally booted up, I filled in all the Google startup credentials and finally got started on a fresh stock 6.0. However, I tried to restore my previous application data through Android's application recovery on startup but everytime the device installs a new application it would freeze up and shut down. This happened countless times. Then the phone, once again, shut down and could not start the ROM. It would freeze up on the bootanimation.
Then things started to get weird, when the phone turns on it should show the "Nexian" logo in all its glory before going to bootanimation. But here the screen gets all distorted and shows these weird horizontal (and sometimes vertical) lines. Nothing's wrong with my phone screen so I assume it is a system error. From here on, the phone refused to boot. It just shows the Nexian logo and restarts over and over. The same thing happens even after I re-flashed both my recovery and ROM. I even tried using SP Flash Tool to re-flash stock but still the same results.
Now, the device wouldn't even turn on. But when I connect it using USB to a Windows computer, it still gets detected through device manager as an ordinary MediaTek device.
I'm assuming now that it may be a problem with the /system parition where we install our ROMs in. The partition may be (partially) corrupt. Seeing as the device could still boot the ROM a few hours ago but freezing upon updates to the stated partition.
If you guys have any other ideas/solutions I'm all ears.
Hi, I have an unrooted, unmodified RP2. Out of nowhere, while browsing twitter, the phone shut down and attempted to reboot, but got stuck on the animation right after the Razer logo for hours. I tried shutting it down and starting it up again, letting it run out of battery, and starting again, but nothing seemed to work.
I decided to just factory reset it from the Android Recovery menu, but booting it up again after that gave me a "Your device is corrupt. It can't be trusted and may not work properly" warning. After pressing power to get past that menu, it tries to reboot over and over again with no success. Has anyone else had this problem?
I have had this problem too, it just booted recycle endless. At that time my RP2 is stock Pie MR2 with Trinitykernel, rooted by Magisk.
I turned off it for minutes(10~30 guessed), It can boot successfully.
Now I switched to arter97 kernel, it only happened one time. Wonder it's kernel or system or device problem?
StarHelel said:
Hi, I have an unrooted, unmodified RP2. Out of nowhere, while browsing twitter, the phone shut down and attempted to reboot, but got stuck on the animation right after the Razer logo for hours. I tried shutting it down and starting it up again, letting it run out of battery, and starting again, but nothing seemed to work.
I decided to just factory reset it from the Android Recovery menu, but booting it up again after that gave me a "Your device is corrupt. It can't be trusted and may not work properly" warning. After pressing power to get past that menu, it tries to reboot over and over again with no success. Has anyone else had this problem?
Click to expand...
Click to collapse
Is this resolved?
Can you get to bootloader?