Related
I'm new to Xoom but gave unlocking and rooting a go. That was todays mistake! I flashed a 3g version of boot.img. Then I tried to flash back to stock img-file. Found out that it also was a 3g img-file. Flashed once more. Now it was a wifi-only boot.img. Now I'm stuck at the Motorola Dual Core logo with Starting RSD mode 3 written in top left corner. I can't shut this thing off or anything else but rebooting back to same screen. I really don't know what to do. I bought it yesterday from a man that bought it in the US a week ago so I can't go to the shop and I don't think there are any shop that can flash it for me because it's not available here in Sweden yet. Please help. I have RSD Lite installed and the correct drivers for the Xoom installed. I'm used to ADB but it can't find the device and fastboot doesn't see it either.
Edit. I can't go into fastboot mode.
Grab the wifi's boot.img off of here:
http://forum.xda-developers.com/showthread.php?t=1017398
http://forum.xda-developers.com/showthread.php?t=973355
This might be helpful. Not sure.
Don't worry you are in good company, even BRD had the same problem. Here's how he fixed it:
While I was in "RSD Mode 3" I did
Code:
fastboot flash boot boot.img
Even though there was no response from the device, I pressed Vol Down + power until the screen went black. I then quickly pressed and held Vol Up + power. The device then went into the bootloader, received the queued command from fastboot, and flashed the boot.img. Finally, I did
Code:
fastboot reboot
and was back in the game.
Guys, I think the moral of the story is to slow down and be careful with fastboot. You can bet i'll be a little more careful
Click to expand...
Click to collapse
Edit: Same advice as linked above by milehighclubAV8R
That doesn't do it. Propably it's some stupid misstake from me but I cannot do this because of " I pressed Vol Down + power until the screen went black". It wont get black. When I press Power + Vol down nothing happens. Am I doing something wrong. I have tried holding the buttons for about 30 seconds and nothing happens.
Did you just press the buttons or did you also enter the fastboot code as suggested?
First cmd command then pressing the buttons. When I reboot using power + vol up it starts into RSD mode 3. When rebooting it with power + vol up then vol down when black it starts into the logo screen without any text in the upper left corner. Can't even shut it down with long press on power button
Can I pull the battery? On my Galaxy S that's the way out if I get in a boot loop or need to redo a failed flash.
Not AFAIK, the unit is sealed and can't access the battery to pull it.
Perhaps ask in this thread - http://forum.xda-developers.com/showthread.php?t=973355, there may be more technical people seeing it there than in the general section.
OK. I will do that. Thank you for trying to help.
Press power+volume up. Hold it til it restarts. Let go of both buttons once you see the motorola logo then just press volume down once, and you should be then able to cycle through 3 different modes. Press volume down to cycle to different modes, volume up to select. Hope that helps.
Sent from my Xoom using XDA Premium App
Sorry but I can't cycle through anything. There are two modes. Either "Starting RSD mode 3" or nothing and RSDLite can't communicate with it so I belive that my xoom is dead. Sending it in for repair tomorrow. I'm giving up.
mine is stuck in the rsd mode 2. if i push and power and the up it will boot cycle if i the down button it says it is the the flashboot protocol mode, but i cannot get it to respond from the cmd window. my computer doesnt think its connected. i have the correct mot drivers. any help or is it bricked
Some people have been getting lucky with ADB commands however others have not been so luck. I myself am in the others category with one of my XOOMS.
Sucks, but some people have been able to get back. I however have not been so lucky with one of the WiFi XOOM's I have and did this purposely to see if maybe something can be done with it. Looks like we have to wait for all the files to be released......
Any day now Moto, util then people will continue to send these devices in and con the stores . For this, I applaud them.
This might work or it might not.
I had a bricked xoom too. no matter what fastboot i entered it wouldnt recognise it. all it would say is "waiting for device"
This is what i did.
Turn the xoom off
Do not connect you USB cable yet
Fastboot reboot-bootloader
It should say "waiting for devices"
Now plug your xoom
Turn on the xoom.
When you see the Motorola logo press volume down till you see "fastboot protocol"
Press volume up.
It recognise my xoom that way
couldnt turn mine off. let the battery run down. plugged it into power booted it up. no help. bricked
stevenege said:
Some people have been getting lucky with ADB commands however others have not been so luck. I myself am in the others category with one of my XOOMS.
Sucks, but some people have been able to get back. I however have not been so lucky with one of the WiFi XOOM's I have and did this purposely to see if maybe something can be done with it. Looks like we have to wait for all the files to be released......
Any day now Moto, util then people will continue to send these devices in and con the stores . For this, I applaud them.
Click to expand...
Click to collapse
I have to admit, I'm one of them. Sure is a nice way to tell Moto to hurry the F up. I can't say I felt great about it but I wasn't about to lose $600 either.
me to one of them
shipped mine back to the factory today. not sure what they can do to it. is there such a thing as a force flash or will they have to replace the firmare chip to make it work? unstable combo tegra and honeycomb, aint messin with mine anymore.
i just recovered mine from this. i flashed recovery with clockwork mod:
at the rsd 3 screen with the usb attached
fastboot flash recovery recovery.img
held the volume down while pressing the power off on until fastboot started flashing the recovery
fastboot reboot
xoom started in clockwork mod, did a restart and it worked
****This happened after attempting to load recovery from rom manager without flashing new recovery image.***
Did you happen to mention in your explanation about what went wrong with your xoom anything about unlocking or relocking?
i have a Galaxy Tab 2 7.0 p3113.
i used heimdall to flash CWM into the tablet.
after what seemed like a succesful flash, my tablet rebooted. but for some reason, it would only go as far as showing the galaxy tab logo. it seems stuck there. i could not turn the unit off. i would hold the power button to force shutdown, but it always starts right back up. it seemed like i could only shut it down if it was connected to my mac while holding down the power button. i can however, boot into download mode.
after consulting google, it seems like the appropriate step was to restore the unit to stock. problem is, i can't seem to boot into recovery. i'm being told by the internet that to boot into recovery, i need to hold [power] and [volume down] until it turns on and then release [power] but keep on holding [volume down] and CWM will load. but nothing happens.
i know this is a total noob post, but i've been scouring the web for two days. i'm at my wits end. any help would be greatly appreciated.
I think recovery mode accessed via volume up+power if you could not so use download mode to flash stock or so to return to normal operation
Sent from my GT-I9100 using xda app-developers app
I press the power and UP ( button next to the power button) I normally hold BOTH buttons down at once and let the boot cycle process twice just to make sure i am going into recovery .....so i see the white samsung text twice i mean. It may take around 10 seconds to complete the process. Then release BOTH keys at once.
The battery needs a good charge for it to work.. Try charging over night before you try it via the mains supply.
Holding the power button and down will bring you into download mode and thats what you use for an odin/heimdall flash.
Hope that works for you
Let us know how you get on .....
Thanks. The battery of the gtab2 drained overnight, so i've got it charging back up now. Will definitely post my results when i have something.
Thank you guys. I'm able to boot into recovery now.
But unfortunately, i still need a little guidance on my original problem. And that problem being that my gtab2 will not startup. After rebooting, it gets stuck on the logo screen. It also plays a startup audio clip. But after that, it just displays the startup logo screen. It does not go into the animation screen and start.
I should also mention that when i plug my gtab2 into my computer, no drives show up.
My question now is, if i were to select [wipe data/factory reset] in CWM, would this restore my gtab2 to it's original factory state? Or would I need to flash a ROM for this? And if i need to flash a ROM, could i place a ROM on a microsd card and flash from there?
*********UPDATE*************
Everything is fine (so far).
I went poking around CWM and realized that I had put a cyanogenmod 9 update.zip in the root of the internal sd card before all this happened. So i went back to cyanogenmods wiki on how to install it on my gtab2 and followed the rest of the instructions on flashing it and VOILA!! I have my gtab2 back.
you should use ODIN instead CWM.
CWM is not designed specifically for Gtab2.
Hoping someone here may have some ideas. ..
Picked up a couple Global's the other day on eBay. Two of the three work great. Was able to get them unlocked, rooted, and band unlocked. They are working great on T-mobile! The issue I'm having is with the third one. When I enter the bootloader, I get nothing but a black backlit screen with no writing. When I attempt to use RSD Lite, I can't get it to recognize the phone at all.
So next I tried booting the phone normally, and then hooking it to the PC. RSD Lite does recognize it that way. When I begin the flash process, the phone attempts to reboot into flash mode, screen goes black, same backlit screen with no writing. I would like to point out that I am doing all this with a 5-wire factory cable, so none of the usual button combo mistakes, undercharged battery issues, etc. apply here. If you have on of these, you don't need a battery in the phone at all. With and without battery, with and without factory cable...hasn't mattered, no bootloader no matter what. The issue is that the bootloader acts as if it just isn't even on the phone. I know there are several ways to reload that consumer replacement to a droid 1, but I haven't found anything for a 2. The other thing limiting what I am able to do is that the phone is running .629, which means no root or CWM, so those couple tricks are out the window at this point also, and because of the bootloader issue I am unable to downgrade using RSD Lite or any of the bootable CD options that usually work for phone stuck on .629.
So at this point I'm figuring the phone is just stuck the way it is, but I thought I'd throw it out there and see if any of you guys had any similar experiences. Thanks
strabo231 said:
Hoping someone here may have some ideas. ..
Picked up a couple Global's the other day on eBay. Two of the three work great. Was able to get them unlocked, rooted, and band unlocked. They are working great on T-mobile! The issue I'm having is with the third one. When I enter the bootloader, I get nothing but a black backlit screen with no writing. When I attempt to use RSD Lite, I can't get it to recognize the phone at all.
So next I tried booting the phone normally, and then hooking it to the PC. RSD Lite does recognize it that way. When I begin the flash process, the phone attempts to reboot into flash mode, screen goes black, same backlit screen with no writing. I would like to point out that I am doing all this with a 5-wire factory cable, so none of the usual button combo mistakes, undercharged battery issues, etc. apply here. If you have on of these, you don't need a battery in the phone at all. With and without battery, with and without factory cable...hasn't mattered, no bootloader no matter what. The issue is that the bootloader acts as if it just isn't even on the phone. I know there are several ways to reload that consumer replacement to a droid 1, but I haven't found anything for a 2.
Click to expand...
Click to collapse
maybe bricked, could try manually installing update.zip from android recovery, if you can get to that
How to enter Android system recovery
Power down the phone.
Slide out the keyboard.
Press and hold the X button on the physical keyboard.
Press the power button.
Once you see a warning sign with an android robot appear, press the Search button on your physical keyboard if you're running froyo/2.4.x firmware. For gingerbread/4.5.x firmware, press Volume Up and Down buttons.
and be sure you are using
How to Enter Bootloader: (used to flash .sbf recovery images)
Power down the phone.
Slide the keyboard out.
Press and hold the up arrow (↑) key.
Press the lock/power button.
Once the SBF loader screen pops up, release the up arrow key.
The other thing limiting what I am able to do is that the phone is running .629, which means no root or CWM, so those couple tricks are out the window at this point also, and because of the bootloader issue I am unable to downgrade using RSD Lite or any of the bootable CD options that usually work for phone stuck on .629.
Click to expand...
Click to collapse
.629 has been rootable since 16 April 2012
just use ezSBF & Root 2.3.4/ 4.5.629
So at this point I'm figuring the phone is just stuck the way it is, but I thought I'd throw it out there and see if any of you guys had any similar experiences. Thanks
Click to expand...
Click to collapse
sd_shadow said:
maybe bricked, could try manually installing update.zip from android recovery, if you can get to that
How to enter Android system recovery
Power down the phone.
Slide out the keyboard.
Press and hold the X button on the physical keyboard.
Press the power button.
Once you see a warning sign with an android robot appear, press the Search button on your physical keyboard if you're running froyo/2.4.x firmware. For gingerbread/4.5.x firmware, press Volume Up and Down buttons.
and be sure you are using
How to Enter Bootloader: (used to flash .sbf recovery images)
Power down the phone.
Slide the keyboard out.
Press and hold the up arrow (↑) key.
Press the lock/power button.
Once the SBF loader screen pops up, release the up arrow key.
.629 has been rootable since 16 April 2012
just use ezSBF & Root 2.3.4/ 4.5.629
Click to expand...
Click to collapse
Ah Shadow! I was hoping you'd see this. Let me clarify a little bit.
1. I am able to get phone to boot into OS. I did try to install the update.zip already but I'm still having the same problem with the boot loader.
2. I know about the easy sbf, and tried that with this particular phone, but because of the problem with the boot loader when easy sbf or RSD Lite switch the phone, or attempt to switch into flash mode, the computer no longer recognizes the phone.
3. I did think about rooting the phone to try to open up a few other options to at least get around the problem. Since it's on .629 already though I'm limited to rooting using easy sbf as far as I've understood, but again since I'm having the issue with the boot loader that hasn't been an option I have been able to successfully use.
4. The power button on the phone isn't working, so I'm unable to use the key combo to access the boot loader; however, I have a factory cable...now I say factory cable not meaning the stock charging cable...but the 5-wire factory cable. Typically with Motorola phones using this cable you simply remove the battery, and then with no battery in the phone hold down both volume buttons and plug the factory cable in and it automatically reverts to the boot loader.
I know that there is a consumer replacement boot loader for the droid 1 to fix issues like this, but I haven't seen one for the two. The other issue is that the replacement is an sbf file which ill be unable to use, and didn't know if that was something that would exist as an update.zip that could be flashed through the stock recovery
don't need power button
with phone off, hold up arrow and connect usb cable
should boot directly to bootloader
sd_shadow said:
don't need power button
with phone off, hold up arrow and connect usb cable
should boot directly to bootloader
Click to expand...
Click to collapse
yeah we're on the same page there. When I do that, instead of getting the bootloader like I normally would, I'm just getting a blank black backlit screen, like the boot loader isn't there. Instead of getting bootlader D0.11 ect, It's just a blank screen. It doesn't matter which method I use to access it, both volume buttons and usb, up arrow and usb, whether there is a battery in the phone or not, I'm still getting the same result. If I boot the phone normally, and then try to let RSD switch it for me, it does it, and then I get the same black screen and the flash mode failure error. Like I said there is a consumer replacement bootloader for the 1 that I've been able to use to fix this problem in the past, but if one exists for the two I haven't been able to locate it. So at this point I have a working OS, a working stock recovery, and no boot loader
think there was a 608 bootloader file, can't remember where i saw it
but it didnt work on 629 anyways
you might be able to root with http://forum.xda-developers.com/showthread.php?p=37438602
Root Droid 2 on Gingerbread 2.3.4 [WINDOWS]
i havent got it to work, but it only takes a few mins to download and run
Sent from my XT862 using xda premium
sd_shadow said:
think there was a 608 bootloader file, can't remember where i saw it
but it didnt work on 629 anyways
you might be able to root with http://forum.xda-developers.com/showthread.php?p=37438602
Root Droid 2 on Gingerbread 2.3.4 [WINDOWS]
i havent got it to work, but it only takes a few mins to download and run
Sent from my XT862 using xda premium
Click to expand...
Click to collapse
Yeah I tried that last night. I saw where you were having problems with it too. I had seen where a few months back there was someone else that was having this issue that you were trying to help walk them through, but the thread kinda died off, so I wasn't sure if there was ever a resolution to it. Ok well thanks for your time. I'll be sure to post an update for people coming behind me if I manage to get anywhere with it.
strabo231 said:
yeah we're on the same page there. When I do that, instead of getting the bootloader like I normally would, I'm just getting a blank black backlit screen, like the boot loader isn't there. Instead of getting bootlader D0.11 ect, It's just a blank screen. It doesn't matter which method I use to access it, both volume buttons and usb, up arrow and usb, whether there is a battery in the phone or not, I'm still getting the same result. If I boot the phone normally, and then try to let RSD switch it for me, it does it, and then I get the same black screen and the flash mode failure error. Like I said there is a consumer replacement bootloader for the 1 that I've been able to use to fix this problem in the past, but if one exists for the two I haven't been able to locate it. So at this point I have a working OS, a working stock recovery, and no boot loader
Click to expand...
Click to collapse
if you are still working on this a Bootloader Only
HS_S_signed_AP_BL_D11_cdma_droid2we_Consumer_replacer.zip
has been posted here http://sbf.droid-developers.org/cdma_droid2/list.php
If you're still looking to root, try Framaroot from here. It worked for me on .629. No idea about the bootloader however . Good luck though!
This Vizio XR6M came with the M65-D0 display I bought. It was running their unmodified version of whatever software was preinstalled. It worked fine all the way up until they pushed an OTA to it, which is causing it to bootloop. I cannot get into any usable recovery because the screen that appears where recovery options should be is the Android on its back with an exclamation point I believe. Can anyone help me get this thing working again? Thanks.
I was really hoping that someone would have a clue. This really sucks. I'll keep waiting
Had the same thing happen to me. When on the screen with the android on his back, hold the power button and quickly press volume up. This should give a menu with a handful of options. Scroll up and down with volume up and down and press power to select. One of the options is to wipe the device. Do this and then select reboot. (There is also a wipe cache option, but this didn't do anything for me.) This is what I was told to do by Vizio support. Unfortunately I've had to do this wipe 3 times now. This tablet is very unstable in my opinion. (Once after an OTA update, once after I rebooted it, and once it just rebooted itself and got stuck in the loop.) I came across your post while looking for info on rooting the tablet or at least getting a backup like TWRP on it so I don't have to spend an hour downloading apps and getting my settings back like I had them every time the tablet decides to lose its **** and go haywire. Best of luck.
Gah... I spent about an hour trying different key combinations to get into recovery... I thought I tried all the key combinations at that Android screen too... But I guess not. Thanks!! Trying a wipe of cache with no expectations that it'll work... full data wipe incoming....
Getting to the Factory menu
1. Hold pwr button down to turn the tablet off
2. Hold the vol dwn button and press the pwr button
3. Anddroid logo with an ! should appear
4. Hold the pwr button and press the vol up button
5. The factory menu should appear
I just picked up two of these TVs and wall-mounted them and they are pretty fantastic, one of the remotes updated just fine but the other one keeps giving me a signature validation failed when it tries to update. I've wiped the cash down a factory reset from recovery and factory reset from inside Android. Anyone have any ideas? I've downloaded it on 3 different WiFi networks and tried to install it probably 10 times now.
Vizio's online chat support to the rescue. I told them what the issue was, what all I tried, she had me verify that I had already done what they suggest (basically get into recovery and such), and told me to send them a copy of my receipt and I'd get a free brand new one, or they could send me a refurbished one without it.
Here's the instructions she gave me.
Please try the following steps:
1. Power the tablet off. While the tablet is off press and hold the Volume Down and Power keys at the same time.
2. The tablet will vibrate and the V logo screen will pop up. Let go of the POWER and VOL DOWN key when the tablet VIBRATES.
3. The tablet will show a picture of the Android mascot laying on the ground with the text 'No Command'.
4. Press and hold the Power key and tap Volume Up key. (One you've tapped the volume up key you can release the power key).
5. Use the Volume Up and Down keys to navigate the options, and the Power Key as an 'OK' button to select options.
6. Navigate down to Wipe Data/ Factory Reset, and press the Power key.
7. Text will appear in the bottom the screen indicating the tablet is resetting.
8. The Android Recovery options will appear again. Use the Vol Keys to navigate to 'Reboot System Now' and press the power button to confirm.
Note: After the reset it may hang on the V logo screen for 5+ minutes before initiating the rest process.
RED ZMAN said:
Vizio's online chat support to the rescue. I told them what the issue was, what all I tried, she had me verify that I had already done what they suggest (basically get into recovery and such), and told me to send them a copy of my receipt and I'd get a free brand new one, or they could send me a refurbished one without it.
Here's the instructions she gave me.
Please try the following steps:
1. Power the tablet off. While the tablet is off press and hold the Volume Down and Power keys at the same time.
2. The tablet will vibrate and the V logo screen will pop up. Let go of the POWER and VOL DOWN key when the tablet VIBRATES.
3. The tablet will show a picture of the Android mascot laying on the ground with the text 'No Command'.
4. Press and hold the Power key and tap Volume Up key. (One you've tapped the volume up key you can release the power key).
5. Use the Volume Up and Down keys to navigate the options, and the Power Key as an 'OK' button to select options.
6. Navigate down to Wipe Data/ Factory Reset, and press the Power key.
7. Text will appear in the bottom the screen indicating the tablet is resetting.
8. The Android Recovery options will appear again. Use the Vol Keys to navigate to 'Reboot System Now' and press the power button to confirm.
Note: After the reset it may hang on the V logo screen for 5+ minutes before initiating the rest process.
Click to expand...
Click to collapse
And after the hair and saliva samples to verify you're really a human and not something from Nibiru, you were able to get into recovery and get it working right?!
Crazy, ive had at least 15 different android devices, and never ever needed to go through a military-style agility course to get into recovery.
Sent from my SM-N920P using Tapatalk
jerry43812 said:
And after the hair and saliva samples to verify you're really a human and not something from Nibiru, you were able to get into recovery and get it working right?!
Crazy, ive had at least 15 different android devices, and never ever needed to go through a military-style agility course to get into recovery.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
It took like 2.5 weeks to get the replacement too, but it was brand new. Now I've got 2 tablets, 3 wireless chargers, and I don't want to use them at all. LOL
Does anyone know if anyone has a factory image that can be flashed? I think mine has bad firmware so resets don't do anything to fix it.
This device have made by Chinese/Indian company Borqs. The code name Bennu-M. Platform is Qualcomm APQ8016 (MSM8916 w/o modem). There should work standard method to bring EDL mode. Hold Vol+ and Vol- at power on (press power). Then connect to the PC. Thus device will stay look dead, however should be detected as Qualcomm QDLoader 9008 on the PC side. This is the factory described method.
You can flash factory firmware from this mode using external bootloader (programmer) for MSM8916 firehose protocol. This procedure is described in the thousands of manuals around the net. Qualcomm tools like QPST or QFIL can be used as good as many 3rd party utils to flash and manage any another available way. Many professional 'box' tools should support this device too but only as 'generic' msm8916 (if applicable).
However I can't find the firmware package for this device anywhere. You should ask and require the manufacturer/distributor to publish firmware, the source code and all the corresponding matherials to be able to flash and rebuild firmware from sources in any manner you want without any limitations as required by GNU/GPL free open source software licenses this firmware is obligated to.
Everyone who have the device working or software dead, can try to dump the current firmware and data, stored on the internal eMMC memory module in part(s) or in whole image using free QTools project utilities and suitable external bootloader with ability to dump eMMC, not only to flash as many factory supplied programmers do. There are programmer(s) for MSM8916 available in the project repo. Read and understand manuals carefully before trying anything!
There is definitely another ways to root, dump, flash, manage the device in any manner YOU WANT, not only the way you are "allowed" to use your own device by manufacturer/distributor. FTA!
You can root the device then dump all the multiple partition images manually (dd if=/dev/block/mmbblk0...... of=/sdcard/......) or using built custom recovery like CWM/TWRP for your device. Please note, kernel sources are important but not mandatory to build e.g. CWM. You can build one using CWM image from the similar device and the kernel (boot/recovery) image binaries from your device. There are good manuals and image repacking utils available around like e.g. AndImgTool.
There are the way to produce factory image from the eMMC/partitions dump(s). Use utils like R-Studio to dump particular partition images from the eMMC dump (it's like whole HDD or UFD image with all the sectors raw, one by one, w/o any modifications/compression/etc) Manuals / utils are avavailable to make e.g. sparse and xml scripts set which is flashable by the programmer in the EDL mode (i.e. from any damaged state, because EDL is built in to the PBL and masked to the internal CPU ROM, thus can not be damaged in any manner, except firing the CPU up).
You can also flash partition images from the more common Fastboot mode, unless eMMC GPT and bootloaders (SBL/RPM/TZ/ABoot) stay intact (logo showed). You can't dump from fastboot, which is common due to the (foolish) 'safety' requirements. It's security by obscurity and is definitely not for your favor, but for the corps control over you and force to send valuable private data to foreign clouds.
Please share eMMC full and/or partitions dumps using reliable 'neverending' file cloud/hosting since there is no factory firmware available yet (ever). I do not own this device and never seen being overseas, so I can't share. Help each other and f... the mfrs and matrix!
Hey guys - I hope you're doing well.
I recently got an HTC U12+, but wanted to try using a custom ROM due to all of the bloatware . Unfortunately I think I've ended up bricking my device. Here are some things I've since tried:
- Restoring to the backup I made beforehand in TWRP - restore works without any errors, but then just hangs at the boot screen
- Method 1 from this thread (https://forum.xda-developers.com/u12-plus/how-to/collection-htcu-u12-ruu-firmware-t3794664) - TWRP always says the zip files are corrupted for some reason
- Method 3 from that same thread - this actually worked before, but I tried installing a custom ROM again, somehow messed up again, and now this method no longer works as it just hangs at the "HTC" boot screen for eternity
- Both methods in this thread (https://www.theandroidsoul.com/how-to-install-htc-firmware-ruu-and-zip/) - the first one leads to a "failed remote 99 ru unknown fail terrible mishap" error, and for some reason my PC doesn't see my phone when I try the second despite being able to see it in file manager
- Probably many other methods that I've now forgotten
I know this is a whole lot of information, but I'm in desperate need of some help. I typically like to troubleshoot things myself, but I've been trying to fix this for quite some time now and could definitely use another set of (much more experienced) eyes. I greatly appreciate any help you guys can provide.
Thanks.
Flash RUU with SD card method
Download RUU from here(important:check your CID): https://docs.google.com/spreadsheets/d/1wIRrVQawd5rD-t9VKPQ-SdRK20RcJVZhwD7lhmPIK8w/edit#gid=0
1. rename RUU to 2Q55IMG.zip
2. copy zip in the root of your sd card. - external card / not internal - it will not work
3. reboot to download mode,
4. your device will pick up the zip file and flash it.
5.follow on screen instructions and enjoy your RUU(this method erase all your data)
I'm having an issue with my u12+ where it just continually reboots to a message saying "The boot loader is unlocked and the software integrity cannot be guaranteed. Any data stored on the device maybe available to attackers, do not store sensitive data on this device" and then it shows the white HTC logo that says Powered by Android down the bottom of the screen, it stays like that for about 5 minutes and then reboots and does the same thing over again.
Holding the power down button does nothing, it will not turn off the phone. Holding power and volume down does nothing either. The phone just does this every 6 minutes and reboots and cycle and that's it.
I've tried putting the file 2Q55IMG_IMAGINE_DUGL_O80_SENSE10GP_hTC_Asia_TW_1.53.709.1_Radio_sdm845-000201b-1807311356_release_531499_signed_2_4.zip (renamed to 2Q55IMG.zip) on the root of a 8gb Fat32 formatted SD card, but I just can't get into recovery or download mode.
I've tried holding down all 3 side buttons for minutes, or just the power button, or combination of buttons, they all do nothing to the phone. (it's as tho they are disabled, but sometimes holding a combination of the 3 will make the phone vibrate a little bit, but in no particular time or order)
When the phone is in either state (locked bootloader message or white HTC logo) my Windows 10 PC sees the phone plugged in as a "USB Input Device", not an Android Phone or Android Device. So using ADB or Fastboot commands do not work to it. I've tried to force the driver to the HTC driver but that does not work.
I also tried using the RUU_IMAGINE_UHL_O80_SENSE10GP_NA_Gen_Unlock_1.30.617.2.exe file, but once again it doesn't detect my phone.
Any help would be kindly appreciated.
Cheers!
EDIT: So I was finally able to get into download mode by waiting until the phone done its 6 minute reboot and then holding power down until it vibrated once, then held volume up until it vibrated again, then let go of the power button, I was then able to choose recovery, download etc.
So I managed to get the file 2Q55IMG.zip to install, it said it installed 100% okay. The phone rebooted and now I'm stuck again just at the white HTC logo and Power by Android down the bottom of the screen.
This time the phone is not automatically rebooting itself and no key combinations will make it reboot. I've tried holding them all in certain combinations for periods of time, the phone will not reboot or turn off.
EDIT 2: So maybe I didn't wait long enough after installing the 2Q55IMG.zip file, I finally got the phone to reboot and now I've got a working phone again. happy days :laugh:
whowhatwhen said:
I'm having an issue with my u12+ where it just continually reboots to a message saying "The boot loader is unlocked and the software integrity cannot be guaranteed. Any data stored on the device maybe available to attackers, do not store sensitive data on this device" and then it shows the white HTC logo that says Powered by Android down the bottom of the screen, it stays like that for about 5 minutes and then reboots and does the same thing over again.
Holding the power down button does nothing, it will not turn off the phone. Holding power and volume down does nothing either. The phone just does this every 6 minutes and reboots and cycle and that's it.
I've tried putting the file 2Q55IMG_IMAGINE_DUGL_O80_SENSE10GP_hTC_Asia_TW_1.53.709.1_Radio_sdm845-000201b-1807311356_release_531499_signed_2_4.zip (renamed to 2Q55IMG.zip) on the root of a 8gb Fat32 formatted SD card, but I just can't get into recovery or download mode.
I've tried holding down all 3 side buttons for minutes, or just the power button, or combination of buttons, they all do nothing to the phone. (it's as tho they are disabled, but sometimes holding a combination of the 3 will make the phone vibrate a little bit, but in no particular time or order)
When the phone is in either state (locked bootloader message or white HTC logo) my Windows 10 PC sees the phone plugged in as a "USB Input Device", not an Android Phone or Android Device. So using ADB or Fastboot commands do not work to it. I've tried to force the driver to the HTC driver but that does not work.
I also tried using the RUU_IMAGINE_UHL_O80_SENSE10GP_NA_Gen_Unlock_1.30.617.2.exe file, but once again it doesn't detect my phone.
Any help would be kindly appreciated.
Cheers!
Click to expand...
Click to collapse
with the phone off, turn it on,when you feel first vibration
quick release power key and keep push volume down.
Smartphone should boot in bootloader mode.
can you get into this mode with this guide?
fabrizio b92 said:
with the phone off, turn it on,when you feel first vibration
quick release power key and keep push volume down.
Smartphone should boot in bootloader mode.
can you get into this mode with this guide?
Click to expand...
Click to collapse
Cheer mates, issue sorted. I just updated my comment in my post.
Not sure if I'm game enough again now to try and put LeeDrOiD and Magisk on it.