Hello and thank you for anyone bothering to read this.
I got a CAT S50 and was experiencing a bit of instability lately.
I've run LTE_S0201121.0_S50_0.023.00 without a hitch for a while, then it decided to crash several applications, from google play to any other app open.
That's when I decided to do a factory reset and see if it would help. Performed the rest without a hitch, but the errors kept coming back. At one point, the screen went black. I knew the phone was on because the backlit was working. I hard-reseted it (hold the power button for 30 seconds or more) and rebooted. The phone froze on the CAT splash logo screen and that's when I hard-reset it again. But when I tried to turn it on, the phone simply refused to work. No vibrate, sounds or anything. It's dead.
When I plug it on the computer's USB, the PC makes a sound as if it detected the device, but when I go to the device manager, I get this QHSUSB_BULK with the yellow exclamation mark
I want to know if it is possible to unbrick this phone and if so, if there is a tutorial or if someone can direct me to the correct procedure. I looked everywhere for the ftf file for this phone to attempt this with flashtool, but I simply can't find it.
ANY help of any form is greatly appreciated.
Sadly I had the same thing happen to me, just a black screen. It decided to delete recovery mode or I just cant get to it.
Power Off the Phone,
While pressing Press Vol Down + Cam Button insert a Powersource -- hold down Vol Down + Cam
Recoverymenu should start
Then flash the original rom via ADB Sideload or SD Card.
btw. i have flashed the LTE_S0201121.0_S50_0.023.00 but i want test older ROMs!
can anyone link or upload an older ROM ?
Guy i have the same issue, can you please help me
I got the same problem I search lots place but still nothing then normal update rom anyone can help?
Related
YUP. I "soft bricked" my t-mobile galaxy s (vibrant here in the us) or so I hope. The phone was rooted via z4 on the latest android t959uvji6 from t-mobile.
How did i do it? Brick my phone that is...
The 3d gallery was pissing me off by picking up everything on the phone. I tried clearing the default setting via the manage app but nothing changed so I decided to delete it. First backing up the apk and odex file from the system folder with titanium backup then deleted them from the system folder via root explorer. Rebooted the phone, pulled out the battery, waited for 30 seconds or so, popped in the battery and booted up the phone w/o any issues.
I tried installing the backup 3d gallery apk file and got the "app not installed" error on numerous attempts. Then tried simply copying it over again with ti backup and nothing happens. Gave up and said the heck with and went the factory restore route, got all the relevant apps installed and tried reinstalling the 3d gallery apk but resulting in the same "app not installed" error prompt. So I again copied over the apk and odex file into the system folder. Rebooted and nothing... phone does not boot into the home screen.
At this point here is what the phone is able to do.
It will boot up and display the default galaxy s animation, goes through it's array of colors then comes to a stop at all white letters then the screen goes blank and nothing happens - zip. nadda. i left it on for 12hrs like that - blank screen w/all the hard keys lit up.
What i did notice was win7x64 recognizes the phone after it gets into the blank screen of death as mass storage units.
So far i've tried booting into the recovery screen via the three button method and none of them works.
Did the karma-volume up-home-power twist - nothing
Did the karma-volume down-home-power roll - nothing
Did the karma-volume up and down-power jiggy - nothing
I tried the key combos for about 2hrs without any success then jumped into adb. After reading for a bit I realized that the phone was still rooted and the debug mode was enabled the last time i shutdown the phone (good'ol ti-backup)
For a while there adb did not recognize the phone at all but with an odd power cycling while spamming "adb reboot recovery" it was able to finally nab hold of the phone and jump into the recovery console. At first I thought it was pure luck so unplugged everything and tried it again - works every time if i did the odd out of sequence power cycle while spamming the adb console with "adb reboot recovery".
In the reboot recovery - deleted the user data and did the restore.
Here's where I think I really screwed up - now the phone is no longer in debug mode.
Long story short - is there a way to get into the recovery screen w/o debug mode on?
**quickly pulls on flack jacket**
but seriously any suggestions would be great
Wrong section bro. You probably won't get an answer here.
To answer your question. Yes, Remove Battery, Plug your phone to USB, Press and hold the volume down and the power button Put the batter back on. This should get you into download mode. Use ODIN to restore.
the usb jig trick did the work - now i have two phones!!!! (bought the nexus s yesterday) lol
Time to ODIN.
To access Download mode.
Unplug. press volume up and down togheter, and connect USB. VOILA!
If ODIN does not recognize it, plug and unplug again
chichu_9 said:
To answer your question. Yes, Remove Battery, Plug your phone to USB, Press and hold the volume down and the power button Put the batter back on. This should get you into download mode. Use ODIN to restore.
Click to expand...
Click to collapse
no!
Why the hell are people giving others ideas on how to get into download when their doing it wrong.
its JUST THE VOLUME BUTTONS, NOT THE POWER BUTTON ALONG WITH IT.
volume + power = Recovery, which in this case you probably cant get into
Volume - Power = Download mode, which everyone can get into unless if they somehow hard bricked, if its possible.
Hi, I just bricked my phone while installing the CyanogenMod stable release. Chances are that the zip file i downloaded was corrupted (The filesize was much smaller, must be an internet disconnection that i did not realise) and I am unable to boot into neither download mod nor recovery mode. When holding the volume up and power button, I see the load screen with the yellow triangle (obviously), and it turns black, and the same screen appears again, except that this time, it stays that way.
I tried to see if Odin can detect the phone but because it is not in download mode, it could not detect anything even when kies was switched off. (checked task manager to make sure i killed it) However, the computer was clearly able to detect the phone. (I am using vm ware and when i connect the usb to the phone, i am prompted to choose between connecting it to windows or mac) I then tried to do it in pure windows but odin was still unable to detect the phone. I tried Heimdall to no avail as well. My jigg should arrive in 2 days but from what i seen from the [debunk] Jigg thread, I am not confident that it'll bring me into the download screen.
Is there anything that can be done without sending it for repair? Thank you
Get your battery out the phone, put it back in and hold Volume-down + Home + Powerbutton immediatly pressed, You may have to repeat this several times. When its needed to repeat it more then once let the battery every try some more time out you device.
When You get into downloadMode flash an OdinRom
Hope it will help.
Alright! Thankfully, that worked after a few tries. Tried to flash CM7 again but apparently, it does not work. Think i'll have to ask people in the relevant thread. Thanks again!
Hello all, thanks for helping me out.
I did a very foolish thing. I rooted my phone and deleted a few bloatware apps that were apparently very important to the phone's functionality. I did not install any recovery software like CWM, fastboot, or anything. It was a stock phone that I simply rooted to remove a few apps. When I went to restart my phone, I found out that I bricked it. Now my phone will only enter Download Mode if I hold the up+down volume buttons and plug it in, or it will get stuck on the LG logo screen and a Security Error screen. A factory reset with the volume down + power will work, but does nothing to fix it.
My immediate issue is that when I plug my phone into the computer, the phone will recognize it has been plugged into a power source (it will either go into Download Mode if I was hitting the volume up+volume down buttons, or start trying to boot up but cycle through the LG logo screen and Security Error screen) but the computer will not acknowledge that anything has been plugged in. There is nothing new listed in the Device Manager. I have read other threads and searched around on the internet. The usual solutions are not working for me:
I have tried several other cables and computers to no avail. I have also tested my current computer/cable, and it worked for data transfer with another phone (Nexus 4)
I have tried cleaning out the contacts on the phone. They were not significantly dirty.
I have tried installing the drivers from LG and even the UniversalNakedDriver
I believe that if I could get my computer to see my phone, I could flash the stock rom back and restore it to working order via LGNPST. I know it is simply a software issue, because prior to my rooting the phone it was recognized by the computer.
Does anyone have any other solutions I haven't tried? Or is this something I need to go JTAG on?
How the problem occurred
So a year or two ago I bought a Jiayu G4A/T/Whatever they're calling it and safely got it here. I've used the stock ROM for a bit but I wanted to get rid of the bloatware that was still on it, so I eventually ended up with a properly rooted phone with a ROM from Jiayu.es (Everything worked, have ClockworkMod as recovery, accessible via Mobileuncle Tools), which was essentially a stock Kitkat rom made to work for the phone. Now I got sick of the ROM and recently saw the new EMUI version on Huawei's P8 Lite, so I figured I'd look around for a tailored ROM running that, and ended up at "jiayu-emui-3-0-stable" from Needrom.
What I did
1. I downloaded a ROM from Needrom with identifier "jiayu-emui-3-0-stable" (I can't post external links)
2. Backed up my important files following a guide from androidcentral titled "[Guide] How to Backup and Restore Apps and Data when installing new ROMs" that I can't link,and did a full backup using CWM
3. Placed the ZIP on my internal SD card, went into recovery, wiped data/cache (not dalvik, since it wasn't described in the instructions, I think this might be a probable cause) and installed the new ROM from ZIP
4. Rebooted the phone and now it's stuck in the boot loop I mentioned.
What the problem is
Bootloops aren't that much of a problem usually, except this one is... I can't get into recovery mode. From there on it'd be cake, since I made the right preparations, but I can't get into it. While connected to my PC it keeps powering on, showing a splash screen from Jiayu.es briefly (which shouldn't be present anymore) and powering off after 10 seconds, only to come back to the splash screen.
What I've tried
I've unplugged it, removed the battery, waited to get a full power cycle and tried to hold my buttons in these combinations: [power button + volume up], [power button + volume down] - but neither work. It just keeps going with the boot loop. I can succesfully power it down, and when I plug it in from there it shows the low battery image. At the moment of seeing that I thought I could connect to it using ADB / Fastboot, but no luck there either. It keeps saying no devices found, and with fastboot it keeps on <waiting for device>.
My questions
What exactly can I do if there is no way for me to get into recovery mode? Are there any alternatives? How can I get my device to be recognized by ADB? Is that even possible? Why is this bootloop any different from others?
Update from the massive Q&A thread:
ZipAddict said:
Is it booting up on its own too after being off? This happened to wifes phone and it turned out the power button was stuck. I took a pencil and hit the power button with the eraser a few times and it worked then. Her case mustve dislogded it. I will keep my fingers crossed for u. If not send me a private message and i will look for an answer tomorrow and get back with u
Click to expand...
Click to collapse
Thank you for the reply!
Yes, it does. I took the battery out and let it lay disassembled for a night, after which I cleaned it a little and re-inserted the battery. With the case back on, nothing happened, so the power button wasn't stuck for sure. When I powered it back on with the power button (no USB attached) it showed the emblem for ~8 seconds and powered off. It then buzzes to show it's powered on again and up comes the splash screen again. Could it be that the ROM was just a rebooting falsehood? Why would it disallow me getting into recovery mode? I really hope there is something that can still force the device into recovery mode / interact with it somehow while in this state.
Oh, I also tried to see if the volume down button was broken but all the contacts seem intact, plus, they worked an hour before I started switching roms.
I had recently installed evolution x, everything worked fine, but i stupidly hit the update button today and now im stuck on the twrp splash screen...
When it turns on i get the galaxy s9 plus splash screen then the twrp 3.5.2_9-0 splash screen.
I am not able to turn the phone off with the power button, i have to hold both volume down and power to restart it.
I have also left the phone overnight just incase it needed a bit of time but no luck, still just stuck on the twrp splash screen.
I have tried many hardware button combinations with no luck. I am unable to see the device on adb or fastboot, and i am unable to see the device when plugged in to install drivers for odin.
How do i fix this? (To be clear i dont care about the data on the phone, it is backed up but the phone is currently a paperweight in this state)
Edit [SOLVED]:
After weeks of googling i was able to find one thread for a different phone with a slightly different problem that said letting the phone run out of battery let them boot into download mode and it worked, as soon as i plugged in the phone and held the button combination i was able to get into download mode and install a later twrp version.
Hopefully other people can find this solution faster than i did
I am still looking for information on this if anyone has any.
I have also had to let the phone run out of battery and am hoping that doesnt make things worse.