Related
Not sure if it's a soft or hard brick, because the darn thing does not turn on at all.
When plugged into the computer, my computer makes the sound when a new device is plugged in and then continuously makes the sound when a device is removed.
Can't turn on phone, so can't get into bootloader or recovery.
Here is what I did:
Ran trickdroid TMOUS 4.0 for about a week no problems.
Just now installed MDJ's new kernel(plus the necessary script and modules), and updated radio(yes, the US radio).
Everything went well, I disabled smokin1337's scripts, and instead enabled setcpu with fairly conservative settings (only maxed at 1.5 Ghz, a screen off profile and a battery percentage profile).
Decided to reboot to ensure changes would stick and BAM! Brick.
I am going to call warranty and get a new one soon. In the meantime, I am going to leave the phone completely off charger and when the weekend is over, try to plug it in and boot into recovery and start from scratch. If anybody has any ideas to try, let's hear them.
Also, I've rooted many many many phones before. I'm not a noob to android modding, and I'm 100% positive I didn't eff something up. I've rooted and installed trickdroid on my sister and my dad's phone too, no problems. They do not have the kernel or the radio.
Must have installed wrong radio which could be perminant brick don't take my word for it though wait for a developer
Sent from my HTC One S using xda premium
k1llacanon said:
Must have installed wrong radio which could be perminant brick don't take my word for it though wait for a developer
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I guess so. I just checked the radio files, and they are the same name. I don't have an md5 to check it against though. Bummer
Sent from my HTC VLE_U using Tapatalk 2
Try holding the power button for 10 seconds, you will see the capacative lights flash, let go and quickly hold vol down, while holding vol down press the power button. If that boots into the bootloader, we can bring you back.
Is adb working when pluged in?
Gesendet von meinem HTC One S mit Tapatalk 2
Can not boot
I have the same problem.
My phone stop booting when the HTC logo is on display.
I ´ve flashed the mui rom and because it doesn´t works well i made a factory reset. And now i can´t boot and i can´t flash another rom because I can´t mount sdcard.
edition-driver said:
I have the same problem.
My phone stop booting when the HTC logo is on display.
I ´ve flashed the mui rom and because it doesn´t works well i made a factory reset. And now i can´t boot and i can´t flash another rom because I can´t mount sdcard.
Click to expand...
Click to collapse
Dude don't steal his post make ur own and if ur logo comes up means u should be able to get into bootloader then force a zip to sd card I'm guessing u must have installed wrong image or something else
Sent from my HTC One S using xda premium
edition-driver said:
I have the same problem.
My phone stop booting when the HTC logo is on display.
I ´ve flashed the mui rom and because it doesn´t works well i made a factory reset. And now i can´t boot and i can´t flash another rom because I can´t mount sdcard.
Click to expand...
Click to collapse
There's a guide in the dev section on how to adb push a Rom to the sdcard
Sent from my HTC One S using Tapatalk 2
To format the sdcard flash the stock recovery via fastboot and format the sdcard in the bootloader menu then flash a custom recovery and mount the sdcard via usb or push a zip via adb.
Gesendet von meinem HTC One S mit Tapatalk 2
Thanks for the replies, folks, but let me reiterate again that I CANNOT get into boot loader. It does not power on, no splash screen, no boot up, nothing. I'm assuming the worst, that I either somehow screwed the radio flash or got a bad download of the radio or something. Seems highly unlikely to me, especially since I was able to boot and go through normal operations for a little bit before deciding to reboot. That's the way it is I suppose.
Also, to answer another user's question, the phone does not respond to adb. If anyone else has an idea, I'm willing to try anything. But to repeat, I cannot get to boot loader.
Sent from my HTC VLE_U using Tapatalk 2
How much charge Did the phone have?
Sent from my HTC One S using xda premium
But if the computer recognizes the phone it must be turned on. What happens if you press and hold the powerbutton?
Gesendet von meinem HTC One S mit Tapatalk 2
hansthegeek said:
But if the computer recognizes the phone it must be turned on. What happens if you press and hold the powerbutton?
Gesendet von meinem HTC One S mit Tapatalk 2
Click to expand...
Click to collapse
Yeah that's true
Sent from my HTC One S using xda premium
Does fastboot reboot or fastboot reboot bootloader do anything? Also if you need a real hard reset find the youtube videos that show how to replace the display and disconnect the battery.
Can u get out of a full brick ?
Sent from my HTC One S using xda premium
Okay, finally some good news. I took the phone to the t-mobile store with intention of getting it replaced. While there, the phone magically turned on, but couldn't get past the lock screen. I was a little worried he would say something because of the custom splash screen, but he didn't notice that or the bootloader screen saying "tampered". And didn't say anything when he got to the TWRP screen. I immediately grabbed it and said "I cant take it from here". Now, the phone is working, but the SD card can't be mounted. So I plugged it into my computer and reformatted the SD card. Going to try flashing now.
To answer a couple questions, the phone had about a 90% charge.
Fastboot is a no go, because the phone *did* not turn on and did not answer to adb.
long story short, I believe I had some kind of data corruption on the SD card. Not sure how/why or what fixed it. I've just gotten done adding another ROM to the SD card, and i'm going to reflash and report back. Thank you all for your help.
Any update?
I'm experiencing a similar problem. I didn't fully brick my phone. Just went into a soft brick. Flashed MIUI, but decided I wanted to go back to stock, so I tried to factory reset. Now my SD card cannot be mounted and none of the ROMs I try to flash via Fastboot are going through. I'm stuck on MIUI with no SD card mount.
hansthegeek said:
To format the sdcard flash the stock recovery via fastboot and format the sdcard in the bootloader menu then flash a custom recovery and mount the sdcard via usb or push a zip via adb.
Gesendet von meinem HTC One S mit Tapatalk 2
Click to expand...
Click to collapse
Gesendet von meinem HTC One S mit Tapatalk 2
dung8604 said:
Okay, finally some good news. I took the phone to the t-mobile store with intention of getting it replaced. While there, the phone magically turned on, but couldn't get past the lock screen. I was a little worried he would say something because of the custom splash screen, but he didn't notice that or the bootloader screen saying "tampered". And didn't say anything when he got to the TWRP screen. I immediately grabbed it and said "I cant take it from here". Now, the phone is working, but the SD card can't be mounted. So I plugged it into my computer and reformatted the SD card. Going to try flashing now.
To answer a couple questions, the phone had about a 90% charge.
Fastboot is a no go, because the phone *did* not turn on and did not answer to adb.
long story short, I believe I had some kind of data corruption on the SD card. Not sure how/why or what fixed it. I've just gotten done adding another ROM to the SD card, and i'm going to reflash and report back. Thank you all for your help.
Click to expand...
Click to collapse
A friend of mine had this happen to her S2. I turned on magically the next day by itself.
Gregree said:
Any update?
I'm experiencing a similar problem. I didn't fully brick my phone. Just went into a soft brick. Flashed MIUI, but decided I wanted to go back to stock, so I tried to factory reset. Now my SD card cannot be mounted and none of the ROMs I try to flash via Fastboot are going through. I'm stuck on MIUI with no SD card mount.
Click to expand...
Click to collapse
Don't steal his thread
Sent from my HTC One S using xda premium
So i was running cm10 and i wanted to install a kernel. I when to install and kernel via rom manager.. When i tried to install in the screen went black and i havent been able to get the phone to turn on since,,,, i noticed when i try to put the phone into dload mode nothing happens... When i plug the phone into the wall charger the led light turns on as if it was charging but i dont have the battery in.. If i put the battery in and i push the volume down home and power nothing happens...can someone please help??? Please!!!!!!!!! I think the kernel was something like k74 something like that...
If you arent able to get into download mode, or even get a vibrate out of the phone, then sadly it may be hard bricked. I don't understand how flashing a kernel could hard brick the phone, though. At any rate, worst case scenario is you will have to send the unit in for a JTAG repair if you are unable to get it to boot in any way.
bakerboy81 said:
So i was running cm10 and i wanted to install a kernel. I when to install and kernel via rom manager.. When i tried to install in the screen went black and i havent been able to get the phone to turn on since,,,, i noticed when i try to put the phone into dload mode nothing happens... When i plug the phone into the wall charger the led light turns on as if it was charging but i dont have the battery in.. If i put the battery in and i push the volume down home and power nothing happens...can someone please help??? Please!!!!!!!!! I think the kernel was something like k74 something like that...
Click to expand...
Click to collapse
Welcome to AOKP/CM. lol Wouldn't use rom manager myself but hold on a few and Droidstyle or Annoying duck should chime in soon. I don't remember how bricked that means. Maybe able to leave battery out awhile and get it back.
apacseven said:
If you arent able to get into download mode, or even get a vibrate out of the phone, then sadly it may be hard bricked. I don't understand how flashing a kernel could hard brick the phone, though. At any rate, worst case scenario is you will have to send the unit in for a JTAG repair if you are unable to get it to boot in any way.
Click to expand...
Click to collapse
i have never heard of jtag... can you give me more info just in case
JTAG is the only way to recover from a hard brick. It is a service that is performed by only one (or maybe a few) companies in the world for the S3 (and many many other devices). Heres a link to the service, which starts at $60, and a link to the video of the S3 being unbricked.
https://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
https://www.youtube.com/watch?v=XnA8Djs55Ds&feature=player_embedded
Try leaving the device plugged into the charger for a hour or so then try to get into odin mode...if still nothing then it sounds like you flashed a kernel that was for the international s3.
bakerboy81 said:
So i was running cm10 and i wanted to install a kernel. I when to install and kernel via rom manager.. When i tried to install in the screen went black and i havent been able to get the phone to turn on since,,,, i noticed when i try to put the phone into dload mode nothing happens... When i plug the phone into the wall charger the led light turns on as if it was charging but i dont have the battery in.. If i put the battery in and i push the volume down home and power nothing happens...can someone please help??? Please!!!!!!!!! I think the kernel was something like k74 something like that...
Click to expand...
Click to collapse
Did you install the 10/14 nightly? I noticed that when I installed the 10/14 nightly and then installed leankernel over that my phone would no longer boot. A simple flash back to M2 and leankernel fixed the issue. 10/14 had a lot of kernel updates so I think that's the problem.
VolUp+Home+Power to boot back into recovery I believe.
Do all of your flashing manually in the future. ROM Manager = no.
Sent from my SCH-I535 using Tapatalk 2
Anayalata said:
Did you install the 10/14 nightly? I noticed that when I installed the 10/14 nightly and then installed leankernel over that my phone would no longer boot. A simple flash back to M2 and leankernel fixed the issue. 10/14 had a lot of kernel updates so I think that's the problem.
VolUp+Home+Power to boot back into recovery I believe.
Click to expand...
Click to collapse
Since his phone wont even power on it will be impossible to flash another ROM.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thanks
FNM
bakerboy81 said:
So i was running cm10 and i wanted to install a kernel. I when to install and kernel via rom manager.. When i tried to install in the screen went black and i havent been able to get the phone to turn on since,,,, i noticed when i try to put the phone into dload mode nothing happens... When i plug the phone into the wall charger the led light turns on as if it was charging but i dont have the battery in.. If i put the battery in and i push the volume down home and power nothing happens...can someone please help??? Please!!!!!!!!! I think the kernel was something like k74 something like that...
Click to expand...
Click to collapse
Delete please
Sent from my PC36100 using Tapatalk 2
I have the cricket model. Sometime last night my phone started rebooting on every ROM and kernel. Nothing I do will get it to stop. It doesn't happen in TWRP and that's it. I thought maybe it was a battery issue as I haven't been able to fully charge it because of this issue but that's not helping either. I've been trying to use the upgrade tool but in this state the computer never even recognizes the phone and I can't even get that far, plus it reboots even when in download mode. I'm about to call cricket and see if they can just send me a new one since I've only had it a week but is there anything I can do? Does anyone have a boot IMG for complete stock 60450 ?!? EDIT: Got the tool to recognize phone and start process but what do ya know phone reboots even deep into download mode. It just always wants to restart to the system for some reason, except for when on twrp. UPDATE:EDIT: Turns out the reason the upgrade app wasn't working is because i didn't have enough space for the update to download on the PC . I didn't realize because the app never stated why it was restarting my phone or disconnecting so I just assumed it was related to why my phone kept restarting on all ROMs. Wow lol I feel so damn stupid for not thinking of this 2 days ago. Its installing now and hopefully this fixes my reboot issues. Thanks to everybody here for helping and answering my 1000 question's on every post. Really appreciate it.
it looks like motherboard is gone. I hope you can return it when you have custom rom installed.
DallasCZ said:
it looks like motherboard is gone. I hope you can return it when you have custom rom installed.
Click to expand...
Click to collapse
I've had the phone for one week lol. Motherboard is gone? Could something be messed up in build prop somewhere? I did try to use a DPI changer app on stock rom once or maybe xposed? I've done a lot of flashing since I got it trying to find the perfect setup. I just noticed that the USB cable it came with is crap so now that I'm using a different one I'm hoping that low discalobrated battery was the issue. Charging it up proper and gonna see what happens after. Also for some strange reason the Flyme OS ROM is the only one that doesent seem to want to restart as often. It still does but it lasts a lot longer before doing so , why idk lol.
turn off the phone, charge it fully and then run the upgrade tool to go back to stock.
Odesláno z mého 6045X pomocí Tapatalk
DallasCZ said:
turn off the phone, charge it fully and then run the upgrade tool to go back to stock.
Odesláno z mého 6045X pomocí Tapatalk
Click to expand...
Click to collapse
I wasnt previously able to corectly charge becauss when i would turn the phone off to charge it wpuld power up instead of gking to the charging acreen. I think the USB cable that came with the phone might have been faulty and I just didn't notice it somehow. Now that I've charged the phone to 50% Flyme is up and running without a reboot, although running quite hot....which could also be the issue. Maybe the metal on the USB tip got toasted. That would explain my reboots in download mode but it doesent explain why the phone never once rebooted on me while in twrp and why it would reboot even while not being charged and had like 30%. Gonna charge it up to 100 and try the tool again.
carnivalrejectq said:
I wasnt previously able to corectly charge becauss when i would turn the phone off to charge it wpuld power up instead of gking to the charging acreen. I think the USB cable that came with the phone might have been faulty and I just didn't notice it somehow. Now that I've charged the phone to 50% Flyme is up and running without a reboot, although running quite hot....which could also be the issue. Maybe the metal on the USB tip got toasted. That would explain my reboots in download mode but it doesent explain why the phone never once rebooted on me while in twrp and why it would reboot even while not being charged and had like 30%. Gonna charge it up to 100 and try the tool again.
Click to expand...
Click to collapse
if you can boot to flyme, and got no reboots in TWRP i suggest you flash from TWRP your previously mad ebackup..if you dont have any, just flash stock kernel or look here in threads, there was a thread and it contains TWRP backup of stock rom..if you find TWRP backup of your STOCK 6045O then flash it from TWRP, and if you dont observe nay reboots, it was due to the kernel. IF it still reboots send it to warranty repair.
DallasCZ said:
if you can boot to flyme, and got no reboots in TWRP i suggest you flash from TWRP your previously mad ebackup..if you dont have any, just flash stock kernel or look here in threads, there was a thread and it contains TWRP backup of stock rom..if you find TWRP backup of your STOCK 6045O then flash it from TWRP, and if you dont observe nay reboots, it was due to the kernel. IF it still reboots send it to warranty repair.
Click to expand...
Click to collapse
Well I'm back on CM now with no reboots. I guess my USB cable just sucked and my battery calibration was off so the battery was showing more than it actually had and probably causing instability. However, I still can't get the tool to work. It just reboots at around 22% exiting me out of download mode. BTW I've searched and scowled almost every thread and I can't find a stock kernel. There's the arde one but I thought that was just his custom kernel for stock. And the twrp back up I definitely can't find. I seen the thread but there was no link.
carnivalrejectq said:
Well I'm back on CM now with no reboots. I guess my USB cable just sucked and my battery calibration was off so the battery was showing more than it actually had and probably causing instability. However, I still can't get the tool to work. It just reboots at around 22% exiting me out of download mode. BTW I've searched and scowled almost every thread and I can't find a stock kernel. There's the arde one but I thought that was just his custom kernel for stock. And the twrp back up I definitely can't find. I seen the thread but there was no link.
Click to expand...
Click to collapse
If it was the USB cable why is mobile upgrade tool rebooting the device at 22%? It makes no sense. It could be the pins on the usb socket on the phone or i dont know.
You should ask someone with the 6045O device to send you the boot.img (aka kernel) of stock 6045O.
DallasCZ said:
If it was the USB cable why is mobile upgrade tool rebooting the device at 22%? It makes no sense. It could be the pins on the usb socket on the phone or i dont know.
You should ask someone with the 6045O device to send you the boot.img (aka kernel) of stock 6045O.
Click to expand...
Click to collapse
Well I first noticed my cable was funky when I loaded up Flyme it kept making an unplug sound and I thought it was just the ROM glitching out but I changed the cable and it stopped. About the tool......I have a Windows tablet that it's only USB connection is one of those mini USB to full adapters and it's a little loose. I have zero problems with it plugging my phone into it for file transfer or for adb, it's all fine there so idk why it would be causing an issue with the tool, last time I tried it k specifically made sure all connections were sturdy and didn't move the whole time and it still rebooted. I noticed somebody in one of the threads said his device did the same thing though and that's why he couldn't use the tool as well......nobody ever replied to him lol
Ahh I spoke to soon. Restored my stock, because that's what I prefer for even at OC it still doesent make the phone nearly as hot as CM ROMs and the restarts came right back even with a decent charged battery. I'm back on CM again though and its not happening. Doesent make much sense because before the restarts were happening across all ROMs. It can't be the kernel in my stock restore as I had used it a bunch of times before with no issues...... Though it is saved on my external SD..... But so is the cm build I'm using. Idk whats going on here. Just wanna return the phone to full stock and call it a day lol. Edit: spoke to soon again lol. There goes CM rebooting, although it took way longer than stock to do so.
After my phone bricked I installed latest Chinese Stable ROM in EDL mode. I chose EDL mode for two reasons (1. I suspected that the phone only works while plugged in to charge and 2. the EDL mode turns off the phone after flashing so I can plug in the charger before booting). Turns out I was right. After the flash was over I tried to boot it without charging it first and it didn't work. After I connected it to the charger it booted normally and the ROM installed successfully.
I tried it again this morning after it fully charged. Few seconds after Ii disconnected it, it turned off. When I tried to turn it back on it was just rebooting to the MI logo screen. I plugged it in the charger and it rebooted 2 times (both times it got to those three dots at the bottom of the screen) and the third time it booted normally.
I also just noticed that the phone is curved a bit (maybe less than 1mm difference between upper left edge and rest of them), maybe from wearing it in tight pockets or something like that.
I think your battery might be dead. Try checking the voltage or the quality.
Replaceable batteries are pretty cheap.
Trimis de pe al meu Mi-4c folosind Tapatalk
Might be faulty battery, might be bad kernel, might be anything. Best way to check is to try to flash latest dev china rom via fastboot, if it still doesn't work try flashing stable 5.1.1 rom, again, via fastboot. If none of the solutions above doesnt work might be bad battery or worse, the controller on mobo died.
timipisoboy said:
Might be faulty battery, might be bad kernel, might be anything. Best way to check is to try to flash latest dev china rom via fastboot, if it still doesn't work try flashing stable 5.1.1 rom, again, via fastboot. If none of the solutions above doesnt work might be bad battery or worse, the controller on mobo died.
Click to expand...
Click to collapse
Well I hope it's a battery, because I just bought one to replace it. What is that mobo controller? Is it replaceable?
I have the same issue,
Battery replacement and stock rom of android 7 didn't help
I'm afraid is another hardware issue /:
I do have a similar problem, flashed xiaomi.eu and something have been broken.
I dont know how and why but its very strange.
Unplugged from supply i can boot up the phone, can see the miui logo and boot into fastboot but NOT into recovery and not boot up os.
As soon as i plug in supply it works quit normally, can boot up everything seems to be working, booting into twrp and flashing rom. No problem at all.
If i unplug while running os it imediately shut down.
The battery bar inside twrp show strange jumps.
What happens did somehting break ? Id like to gift the phone my mother for christmas.
Danny94 said:
I do have a similar problem, flashed xiaomi.eu and something have been broken.
I dont know how and why but its very strange.
Unplugged from supply i can boot up the phone, can see the miui logo and boot into fastboot but NOT into recovery and not boot up os.
As soon as i plug in supply it works quit normally, can boot up everything seems to be working, booting into twrp and flashing rom. No problem at all.
If i unplug while running os it imediately shut down.
The battery bar inside twrp show strange jumps.
What happens did somehting break ? Id like to gift the phone my mother for christmas.
Click to expand...
Click to collapse
Hi how did you resolved this. Facing same problem. Will replacing battery solve this.
visharagp said:
Hi how did you resolved this. Facing same problem. Will replacing battery solve this.
Click to expand...
Click to collapse
I purchased a new battery and it was working normally again and still working.
Danny94 said:
I purchased a new battery and it was working normally again and still working.
Click to expand...
Click to collapse
Great then I have to purchase a new battery ss well
Hi, 2 days ago my OPO just keeps turning off after a few seconds even when I'm in twrp screen. Even with the wall charger connected, but if I connect it to a computer or any other system it just works fine and normal.
I have lineage 14.1 and I already try factory reset, OS clean installation again and with previous versions. With gapps or without gapps still turning off. Very strange. Can anybody help? I don't know what to do.
JFPT said:
Hi, 2 days ago my OPO just keeps turning off after a few seconds even when I'm in twrp screen. Even with the wall charger connected, but if I connect it to a computer or any other system it just works fine and normal.
I have lineage 14.1 and I already try factory reset, OS clean installation again and with previous versions. With gapps or without gapps still turning off. Very strange. Can anybody help? I don't know what to do.
Click to expand...
Click to collapse
Replace battery.
Mr.Ak said:
Replace battery.
Click to expand...
Click to collapse
When I do factory reset, reinstall os, do the initial configuration the phone just works normally... Which is very strange...
But thanks for help
JFPT said:
When I do factory reset, reinstall os, do the initial configuration the phone just works normally... Which is very strange...
But thanks for help
Click to expand...
Click to collapse
It'll bootloop if you don't connect the device to charger.That's the sign of dying battery.
Mr.Ak said:
It'll bootloop if you don't connect the device to charger.That's the sign of dying battery.
Click to expand...
Click to collapse
Thanks a lot. I will try that. But isn't strange if i connect to the wall charger still turning off? And sometimes it reboots and stucks in Android is starting screen. Is there a way to test the battery? Last week the phone works just fine and the battery lasts the entire day. I just trying to understand what happened. Thanks again,and sorry for my bad english.
JFPT said:
Thanks a lot. I will try that. But isn't strange if i connect to the wall charger still turning off? And sometimes it reboots and stucks in Android is starting screen. Is there a way to test the battery? Last week the phone works just fine and the battery lasts the entire day. I just trying to understand what happened. Thanks again,and sorry for my bad english.
Click to expand...
Click to collapse
Yes,you can order Usb tester and try it,but instead of wasting time over this,just buy a new battery(look up battery thread in accessories for suggestions).
I think this just happen to me.
If not connecting to charger :
-Rebooting itself when flashing rom
-Bootloop after a few second when using the phone (All rom, even after revert back to COS 13)
-Somehow, it not bootlooping if on fastboot.
If connected to charger :
-Phone working as normally.
-