Hello XDA,
(First of all, my knowledge about the inner working of a android os is equelevent to a cave-mans knowledge, so please explain your advise to me like explaining to a brain-dead person. Thank you)
I found my first smartphone back from 2011 inside my house while doing a cleanup, and it appears to be broken
Phone does not boot into the OS, it just hangs at the second HTC screen (the one screen with the HTC text and their motto at the bottom)
I tried to factory reset the phone from bootloader but it failed. It just showed a progress bar for a few seconds and back to the boot logo (which hangs at there again)
I tried to install the Cyanogenmod but the "Recovery" mode in the bootloader is also broken too. I pressed the 3 button configuration (power+vol up+vol down) at the same time but it just hangs at the boot screen like before.
(New Update on this below)
Do you guys know how can i fix this phone? I have PC and I dont care about the personal files in it. I just want it to work again and I am taking any kind of risk to accomplish this task.
Some information on the bootloader:
"PICO PVT SHIP S-ON RL
HBOOT-1.02.0000
RADIO-1.11.82.17
Oct 31 2011,16:44:09"
UPDATE: After I woke up just now I've decided to try my luck on recovery again. I left the phone to charge overnight and when I woke up the battery was %60. And This time It worked!... Well, not really. At first I was only seeing these 2 screens: one was a green recycling-type-of-stuff logo switching to a red exclamation mark, and the other being just stuck at htc logo. This time It did showed the red exclamation mark AGAIN but afterwards It booted up to Recovery mode, but something is genuinely wrong here.
Instead of 6 different options there is only 4 options which is being:
-Reboot system now
-Apply update from sdcard
-Wipe data/factory reset
-Wipe cache partition
With the a yellow text at the very bottom saying:
"E:Can't open /cache/recovery/command"
The situation here is worse than I thought... I was wondering If i could install a new os on this only using PC if it is possible.
UPDATE 2: I've tried all the 3 settings except reboot.
"Wipe cache partition" was working fine, at least, I think...
"Wipe data/factory reset" just MISERABLY failed. There was bunch of errors on the screen saying "Couldn't find this_important_file.zip" "Couldn't find that_important_file.zip"
"Apply update from sdcard" I thought it could install the Cyanogen mod but it just rebooted to the never ending boot screen
I believe that both the Operating System AND the worst of all, the BIOS is corrupted too... (wow no $h!t sherlock!)
I am still holding hope but I don't think anybody can fix this phone.
Related
Hey folks,
I could desperately use some help here...
I rooted my Droid Incredible using UnRevoked, which was painless and easy. After that, I downloaded Rom Manager, then backed up my current Rom.
Then I downloaded Titanium, and backed up all apps and system data.
Using Rom Manager, I downloaded Cyanogen mod 7.0.2, checked google apps, DID NOT check wipe data or cache, and then clicked OK to let it work it's magic.
The system turned on and off a bit, and then the CyanogenMod boot screen came on, ran the arrow around the droidbot a few times, then the droidbot dissapeared, came back across the screen, and the arrow resumed circling. This happened about 20 times, before I gave up and powered off by removing the battery.
Then I loaded Hboot, and attempted to access items in Clockworkmod, but even though I could click on an item, it would show the top hat with no change in status for many minutes. I eventually tried almost all options.
My Hboot screen shows:
HBOOT - 0.92.0000
Radio- 2.15.00.07.28
I am unable to click on Fastboot, Recovery leads me to busted Clockwork menu, Clear Storage causes restart into looped Cyanogen Mod screen, haven't tried Simlock, and Factory Reset also goes to broken Clockwork Menu.
I downloaded the RUU file from Doug, changed the title as directed, and put it on the SD Card. It gave me the option to Update, which when restarted afterwards continued to loop in Cyanogen Mod screen. Or, if I went to Clockwork Mod screen, the font was now Green instead of Orange. Also, when I click an item in the Clockwork Mod menu, it simply goes to a black screen until I hit the power button to bring me back to the menu,
I'd love to just get the phone to a factory state, so I can possibly use it for it's purpose of calling and sexting (just kidding.)
Please help, any advice would be greatly appreciated.
Oftentimes, ClockworkMod Recovery has an error at the bottom stating:
E:Invalid command argument
I have to go to bed for a bit, but will be back on around 10:30am EST. Thanks for any and all help!
In ClockworkMod, I can now access and start an operation by selecting it with the volume buttons, and then hitting the joystick button. This wasn't working previously. So, I've tried some of the obvious options such as Factory Reset but it's not doing anything. I've tried multiple solutions, which means I've probably messed it up on many levels. Is there any way I can just start from scratch or get a system restore done?
After utilizing that update from Doug, and then going into Clockwork Mod, clearing all caches and system data, and then trying to restore to a previous flash for the 7th time... I think it might be working!
Thanks to anyone who looked at this.
Hello everyone. I am an old member, seeing as I registered almost four years ago, but I guess either your database was refreshed and it lost my username, or I only lurked. So, as the title suggests I have one of those lowly, inexpensive, down right cheap Kyocera phones. Here is what I have figured out so far. I was able to root it using Kingroot. That went splendidly, though because of my over adventurousness I decided to swap some apps out. I added a new launcher to the /system/app folder and wanted to upgrade the com.android.settings.apk with one from a newer build. This phone (was) running Android 4.0.4 Kyocera release r77 build date 2013. Apparently Kyocera loves to lock the bootloader so if I was able to spin a custom system rom I wouldn't be able to flash it. Another thing which discovered was upon boot up the system checks the integrity of app the system apps. If one of them fails the check it will not boot the system fully. I was able to recover the stock boot/recovery/system roms from a thread on here, but I seem to be stuck in a soft brick loop. One thing that another thread said, the thread that had the rom images, it said that you could used ADB to flash the roms to the phone. Thing is, when I boot the phone it restarts, and if I put it into recovery mode (press and hold volume down plus power for ten to fifteen seconds) the only options I have are "reboot system now", "wipe data/factory reset", "wipe cache partition." There is no "flash update from sd card" or wipe dalvik cache option. As I have said before, I could try to flash the rom to it using adb but I believe that wiping the system partition unset the USB debugging setting. When I connect it to my computer windows device manager notices the kyocera removable device for a second then as the phone reboots it goes away. Setting it into recovery mode does not make it show up in windows. Is there any way I can flash the stock rom onto it? Any android sdk or adb trick I can use that can boot it into some recovery mode? I was trying to see if I can get it to boot into download mode but seeing as it has soft keys and not a physical home button I do not know if I can manage that. I was thinking that maybe they tied one of the physical keyboard buttons to the home button but I have yet to uncover that one. Any help would be appreciated.
Zestypanda said:
Hello everyone. I am an old member, seeing as I registered almost four years ago, but I guess either your database was refreshed and it lost my username, or I only lurked. So, as the title suggests I have one of those lowly, inexpensive, down right cheap Kyocera phones. Here is what I have figured out so far. I was able to root it using Kingroot. That went splendidly, though because of my over adventurousness I decided to swap some apps out. I added a new launcher to the /system/app folder and wanted to upgrade the com.android.settings.apk with one from a newer build. This phone (was) running Android 4.0.4 Kyocera release r77 build date 2013. Apparently Kyocera loves to lock the bootloader so if I was able to spin a custom system rom I wouldn't be able to flash it. Another thing which discovered was upon boot up the system checks the integrity of app the system apps. If one of them fails the check it will not boot the system fully. I was able to recover the stock boot/recovery/system roms from a thread on here, but I seem to be stuck in a soft brick loop. One thing that another thread said, the thread that had the rom images, it said that you could used ADB to flash the roms to the phone. Thing is, when I boot the phone it restarts, and if I put it into recovery mode (press and hold volume down plus power for ten to fifteen seconds) the only options I have are "reboot system now", "wipe data/factory reset", "wipe cache partition." There is no "flash update from sd card" or wipe dalvik cache option. As I have said before, I could try to flash the rom to it using adb but I believe that wiping the system partition unset the USB debugging setting. When I connect it to my computer windows device manager notices the kyocera removable device for a second then as the phone reboots it goes away. Setting it into recovery mode does not make it show up in windows. Is there any way I can flash the stock rom onto it? Any android sdk or adb trick I can use that can boot it into some recovery mode? I was trying to see if I can get it to boot into download mode but seeing as it has soft keys and not a physical home button I do not know if I can manage that. I was thinking that maybe they tied one of the physical keyboard buttons to the home button but I have yet to uncover that one. Any help would be appreciated.
Click to expand...
Click to collapse
Hi and thank you for using XDA Assist
If you can access your recovery it is already a good thing, try first to wipe data and see how it goes.
nilac said:
Hi and thank you for using XDA Assist
If you can access your recovery it is already a good thing, try first to wipe data and see how it goes.
Click to expand...
Click to collapse
So, I boot into recovery and I do the wipe data/factory reset then the wipe cache partition for good measure and it still halts on boot. Same thing. Boot, kyocera logo, virgin mobile boot splash, then it halts where it would normally go into android. Then it reboots. Rinse repeat.
Any suggestions? I sorta need the information off the phone.
Hi,
I just bought a second hand Nexus 5 and when I turned it on it was in "FastBoot Mode" with the product name Hammerhead and bootloader HHz12k showing as the bootloader version.
Anyway, I set the phone up and started a system software update and now it's stuck in a loop where it states "Installing System Update" with the progress bar 1/5th of the way up, restarting and repeating that process, Statement, Progress Bar, Restart.
Has this phone been tampered with and is there any way I (a layman) can get it running.
I've searched the forum but must admit the volume of threads is confusing. Can anyone help?
You can just flash the latest stock from from Google.
ROM images are here: https://developers.google.com/android/nexus/images#hammerhead
Good info here: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
CHEWBAZZA said:
Hi,
I just bought a second hand Nexus 5 and when I turned it on it was in "FastBoot Mode" with the product name Hammerhead and bootloader HHz12k showing as the bootloader version.
Anyway, I set the phone up and started a system software update and now it's stuck in a loop where it states "Installing System Update" with the progress bar 1/5th of the way up, restarting and repeating that process, Statement, Progress Bar, Restart.
Has this phone been tampered with and is there any way I (a layman) can get it running.
I've searched the forum but must admit the volume of threads is confusing. Can anyone help?
Click to expand...
Click to collapse
You first need to find out what state the bootloader is in. Is it locked, unlocked? If unlocked, is there a custom recovery installed, such as TWRP? First of all, turn the phone completely off ... and then boot into recovery, by holding the volume down button and the start button simultaneously. Toggle the volume button to show recovery, and select with the power button. If it boots into TWRP, do a wipe (cache, dalvik cache, reset), and then reboot the system. You should be at the welcome screen of what software is currently on the phone. Set up enough so that you can get back to XDA, and download a stock custom rom, such as xTraFactory and the updated bootloader/radio zip that was released a couple of weeks ago. Back into recovery ... wipe, then flash the rom zip and the bl/radio zip. Reboot and setup.
Hi all. Hoping someone can finally help me get my Galaxy Tab 2 working again.
A few years ago I decided to root it and install CyanoGenMod. It worked much faster after that and everything was fine. Then one day out of the blue I turned the tablet on and it eventually loaded to the home screen but it was messed up. A few seconds later the Tab 2 reboots itself and this just repeats over and over.
If I go into recovery mode I get the message "installing system update" for less than a second and then it changes to "no command" and eventually a message loads:-
# MANUAL MODE #
-- Appling Multi-CSC ...
Applied the CSC-code : BTU
did not match sized '/system/csc/common/system/csc/others.xml (No Data Available)"
If I try selecting the wipe cache partition option, it will try for a second or two and then shows error and reboots.
If I try the wipe data/factory reset option, it says the data has been wiped but the Android logo in the background changes to say 'error' underneath it. It then powers itself off. Turning it on brings up the boot loop as before with the messed up home screen appearing for a few seconds before it reboots. So it doesn't appear to be wiping any data at all.
Can anyone offer any assistance on how to get this working again please? I would be forever grateful.
PFMC84 said:
Hi all. Hoping someone can finally help me get my Galaxy Tab 2 working again.
A few years ago I decided to root it and install CyanoGenMod. It worked much faster after that and everything was fine. Then one day out of the blue I turned the tablet on and it eventually loaded to the home screen but it was messed up. A few seconds later the Tab 2 reboots itself and this just repeats over and over.
If I go into recovery mode I get the message "installing system update" for less than a second and then it changes to "no command" and eventually a message loads:-
If I try selecting the wipe cache partition option, it will try for a second or two and then shows error and reboots.
If I try the wipe data/factory reset option, it says the data has been wiped but the Android logo in the background changes to say 'error' underneath it. It then powers itself off. Turning it on brings up the boot loop as before with the messed up home screen appearing for a few seconds before it reboots. So it doesn't appear to be wiping any data at all.
Can anyone offer any assistance on how to get this working again please? I would be forever grateful.
Click to expand...
Click to collapse
See the best way to get out of this is to install the stock Samsung firmware using the ODIN tool.
Then if you ever wish to install a custom rom again you can do as you like. Hope this helps. If you are require assistance, feel free to reply to this conversation.
I have tried a few times to flash the stock firmware with ODIN but it would either install the whole thing but it actually didn't work, or the install would crash part way through.
Unless there is some error with the stock firmware I've found online, is there a link to the proper one that I can download from somewhere? Or a specific version of ODIN that is needed for it to work?
Hi, here's a description of what happened, what I did to solve my problem, and where I am now...
I left my Google Pixel and 2 hours later found it stuck into a booting loop (Google logo displayed > black screen > Google logo displayed > blackscreen...).
I first entered fastboot and tried to power off, restart, etc a few times, but it stayed stuck into the booting loop.
So I downloaded latest OTA from Google for my phone (my phone was already updated to the latest version via the phone update manager, which goes back to december 2019 I think).
I first verified that my linux pc could correctly see the devices, and then from fastboot I entered recovery mode and chose "Apply update from ADB".
I used the adb command to load the OTA I had downloaded.
The update progressed until it finished with the following error message :
Code:
install from ADB completed with status 1
Installation aborted
E:Failed to clear BCB messages: failed to write /dev/block/platform/soc/62400.ufshc/by-name/misc: I/O error
I was back on the recovery menu screen, and this is where I think I did something stupid : I selected "Reboot system now".
The phone did not reboot, the screen just went black and stays black. The phone is cold so I guess not running anything. And it does not respond to any button, so not starting up, no fastboot, etc. No more when I connect it to a PC or plug it in a power plug.
I don't really care about the phone, I was just trying to get back my picture/videos from the last 6 months.
I don't have much hope but I will appreciate any help, even if its just to confirm that there is nothing to do
rraphrr said:
Hi, here's a description of what happened, what I did to solve my problem, and where I am now...
I left my Google Pixel and 2 hours later found it stuck into a booting loop (Google logo displayed > black screen > Google logo displayed > blackscreen...).
I first entered fastboot and tried to power off, restart, etc a few times, but it stayed stuck into the booting loop.
So I downloaded latest OTA from Google for my phone (my phone was already updated to the latest version via the phone update manager, which goes back to december 2019 I think).
I first verified that my linux pc could correctly see the devices, and then from fastboot I entered recovery mode and chose "Apply update from ADB".
I used the adb command to load the OTA I had downloaded.
The update progressed until it finished with the following error message :
Code:
install from ADB completed with status 1
Installation aborted
E:Failed to clear BCB messages: failed to write /dev/block/platform/soc/62400.ufshc/by-name/misc: I/O error
I was back on the recovery menu screen, and this is where I think I did something stupid : I selected "Reboot system now".
The phone did not reboot, the screen just went black and stays black. The phone is cold so I guess not running anything. And it does not respond to any button, so not starting up, no fastboot, etc. No more when I connect it to a PC or plug it in a power plug.
I don't really care about the phone, I was just trying to get back my picture/videos from the last 6 months.
I don't have much hope but I will appreciate any help, even if its just to confirm that there is nothing to do
Click to expand...
Click to collapse
Well you could try and see if the phone is in deep flash mode, if it is flash system, boot and other sensitive partitions but make sure that the versions are the same. If you don't have the firmware you can pull user data partition from phone and get your data back that way
muhammad42620 said:
Well you could try and see if the phone is in deep flash mode, if it is flash system, boot and other sensitive partitions but make sure that the versions are the same. If you don't have the firmware you can pull user data partition from phone and get your data back that way
Click to expand...
Click to collapse
Thanks for your help. This is probably beyond my capabilities. I don't know how to check if it's in deep flash mode. Pulling the data out is what I'm interested in most.
Maybe this is something that a phone repair shop is able to do...
rraphrr said:
Thanks for your help. This is probably beyond my capabilities. I don't know how to check if it's in deep flash mode. Pulling the data out is what I'm interested in most.
Maybe this is something that a phone repair shop is able to do...
Click to expand...
Click to collapse
These phones get emmc errors. Common issue with this device