Default [Q] Phone won't boot, enter Recovery Mode, nor connect to PC - what do?
I followed a root-guide a couple of weeks ago and my phone worked perfectly.
I have no memory of what ROM I used, nor do I remember if I flashed a Kernel or not. I'm pretty new at this.
Now, today, my phone sent a notification that a new firmware update was available. Stupid as I am I just press "install" right away. Not much later my phone tried to reboot and suddenly was stuck at the Samsung logo screen. I tried pulling out the battery to reboot and it still wouldn't work. If I connected it to my PC it shows a battery but the spinning arrow-thingy is frozen.
After searching these forums and other places I found several guides on how to fix stuff like this, by either flashing with a new kernel - or rom or w/e I don't know - or going into recovery mode and do something funky. The problem is that I can't reach recovery mode at all, and when I enter download mode it's just frozen at "Downloading..." and I can't get it to connect to my PC at all (tried both with and without Kies). In Odin the ID:COM cells won't update when I connect my phone.
Do you guys have any idea how to resolve this? Do I have to take it to a service centre?
Edit: The phone is out of battery, suddenly, apparently, so I tried to charge it, but that doesn't work either. What the **** has happened to my phone? Please help if you can!
REPLY
zCourge
I've got the same problem as the listed above. I did root my Phone (it's an Galaxy Trend) and then after i wanted to install an custom rom... It was the kitkat 4.1 or something? But then after when i was about to reboot my phone did not start at all. The samsung logo pops-up and it is an yellow triangle on the very bottom. And i've read so many forums and threads and tried various usb modes, adb recovery tools, recovery bootloader's and so on. But none of them does work. And i can't bring my phone to service either. And for a fact i did use Odin and it did work great when i rooted but what should i do? I can boot into download mode and use odin to "transfer" an new rom/zip file but since i can't boot into recovery mode so how can i ever start my phone? I could continue only if my phone would boot into recovery mode.. and i did wipe/reset factory data too before the phone wouldn't start if that's any help for you. And i have all backup for my phone on my pc, all my system data, sd memory, apps and all data i could backup. Please help me, thanks in forward!
Is your phone the Galaxy Ace 2 or the Galaxy Trend?
a.cid said:
Is your phone the Galaxy Ace 2 or the Galaxy Trend?
Click to expand...
Click to collapse
as i did write it is an Galaxy Trend....
hofling96 said:
as i did write it is an Galaxy Trend....
Click to expand...
Click to collapse
So why is is still 'Galaxy Ace 2' in thread title?
Sent from my GT-I8160 using Tapatalk
teddytsen said:
So why is is still 'Galaxy Ace 2' in thread title?
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
well because galaxy ace 2 is the same phone and system as galaxy trend and to root trend you have to follow galaxy ace 2 guide to succed rooting trend. it is simply just the same phone and you dont find any solutions if you search the web for trend because it onlycome solutions for galaxy ace.
No its totally different in hardware. Ace 3 is more like trend but definitely not ace 2...
Sent from my GT-I8160 using Tapatalk
teddytsen said:
No its totally different in hardware. Ace 3 is more like trend but definitely not ace 2...
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
well please notice that it is Trend GT-S7650 and not Trend Duos or Trend Plus or something. well if im wrong i did root my trend successfully using the instructions on how to root galaxy ace 2 so how do you explain that? well anyway if i rooted it using galaxy ace 2 instructions, the solution (if there is) well probably be either of galaxy ace 2 or trend instructions? well i did just ask if anyone knows the answer and if you already did know that there is an big difference between these two phones you would the know how to continue?
hofling96 said:
well please notice that it is Trend GT-S7650 and not Trend Duos or Trend Plus or something. well if im wrong i did root my trend successfully using the instructions on how to root galaxy ace 2 so how do you explain that? well anyway if i rooted it using galaxy ace 2 instructions, the solution (if there is) well probably be either of galaxy ace 2 or trend instructions? well i did just ask if anyone knows the answer and if you already did know that there is an big difference between these two phones you would the know how to continue?
Click to expand...
Click to collapse
If the phones are different, then you are risking a lot. Just because some method worked does not guarantee that all corresponding ones would. Do not complain if your phone gets bricked.
a.cid said:
If the phones are different, then you are risking a lot. Just because some method worked does not guarantee that all corresponding ones would. Do not complain if your phone gets bricked.
Click to expand...
Click to collapse
Yup i did knew that and all the riskes, therefore i did save/backup all system files/data etc. and i do know to that ofc the phones are not precisley simiular but i have read that they are in some way the same too. and as i wrote in the last reply i can be wrong to about they being in any way the same, but still please don't be so sarcastic because i did ask if you/anyone could in any way solve this problem i have.. well now you know that if this is the wrong forum my questions is in can you help me either way? i know what riskes i did take and that maybe there's no so much to do but is there anything at all i can do to start my phone? without any service reparation? and i know so much that if i can start my phone i can then enter recovey mode and fix it... and if there's anything more you'll have to know to help me so ask and i'll say what steps i did take to root and so on... please just help me
Have you tried using a JIT to force boot to recovery?
Sent from my GT-I8160 using Tapatalk
teddytsen said:
Have you tried using a JIT to force boot to recovery?
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
actually not. but i've tried with adb "boot recovery mode" tool but it only works if i could start my phone. that's just my problem, i cant start it so i cant us adb boot recovery tool to boot into recovery mode. but does JIT work in same way as adb or can you force to boot into recovery mode even if phone wont start and is off ?
@up
Search
Sent from my GT-I8160 using Tapatalk
hofling96 said:
Yup i did knew that and all the riskes, therefore i did save/backup all system files/data etc. and i do know to that ofc the phones are not precisley simiular but i have read that they are in some way the same too. and as i wrote in the last reply i can be wrong to about they being in any way the same, but still please don't be so sarcastic because i did ask if you/anyone could in any way solve this problem i have.. well now you know that if this is the wrong forum my questions is in can you help me either way? i know what riskes i did take and that maybe there's no so much to do but is there anything at all i can do to start my phone? without any service reparation? and i know so much that if i can start my phone i can then enter recovey mode and fix it... and if there's anything more you'll have to know to help me so ask and i'll say what steps i did take to root and so on... please just help me
Click to expand...
Click to collapse
Apologies if it sounded sarcastic. It was more out of concern than out of sarcasm. I have seen newbies fumbling around and flashing files of vastly different phones and then lamenting their loss. Just wanted to make sure you knew what you were getting into.
Anyways, I do not possess this phone so I can not help you further in this matter. But it would be prudent if you edited the main post to be more clear about your situation. :good:
a.cid said:
Apologies if it sounded sarcastic. It was more out of concern than out of sarcasm. I have seen newbies fumbling around and flashing files of vastly different phones and then lamenting their loss. Just wanted to make sure you knew what you were getting into.
Anyways, I do not possess this phone so I can not help you further in this matter. But it would be prudent if you edited the main post to be more clear about your situation. :good:
Click to expand...
Click to collapse
The Galaxy Trend GT-S7560 is the same phone with Galaxy Ace 2x S7560m i think that's where he got the rooting package he missed an x ..
Related
hey guys,
( I know that there is another thread here asking that same question, but actually the questioner didn't get the perfect answer , that's why I ask this question again, I really need your help )
please I have a problem in my device,
I have Samsung Galaxy S 2 and the problem is when I switch it off after that
the phone will turn itself ON automatically, in another words, I can't switch it off.
please, can anyone tell me the reason or the solution of this problem ?
( knowing that there is no Samsung Center in my country to fix the phone for me)
thank you so much.
Do you have stock, or a custom rom? if stock, are you rooted?
Sent from my SGH-T989 using xda premium
J.Rawand said:
hey guys,
( I know that there is another thread here asking that same question, but actually the questioner didn't get the perfect answer , that's why I ask this question again, I really need your help )
please I have a problem in my device,
I have Samsung Galaxy S 2 and the problem is when I switch it off after that
the phone will turn itself ON automatically, in another words, I can't switch it off.
please, can anyone tell me the reason or the solution of this problem ?
( knowing that there is no Samsung Center in my country to fix the phone for me)
thank you so much.
Click to expand...
Click to collapse
What happens after you do a battery pull? Try that leave it out for a few seconds and see if it turns itself on again, essentially it shouldn't be able to unless your hardware button is stuck/sticky.
Is your phone insured ?
If you are on a custom rom it could be a bad download. Check the MD5 checksums and verify that your download was legitimate. Other than that. If you ARE NOT rooted, I suggest you read MULTIPLE tutorials and root your phone in addition to adding a custom ROM.
May I suggest Juggernaut V5.0. Or if you like ICS I suggest Blackedition or NexusMod
Best of luck
icepally said:
What happens after you do a battery pull? Try that leave it out for a few seconds and see if it turns itself on again, essentially it shouldn't be able to unless your hardware button is stuck/sticky.
Is your phone insured ?
Click to expand...
Click to collapse
well actually I did that, but it didn't work. no my phone is not insured
but what you meant by saying that '' my hardware button is stuck ? '' sorry for that.
Illuminatiii_X said:
If you are on a custom rom it could be a bad download. Check the MD5 checksums and verify that your download was legitimate. Other than that. If you ARE NOT rooted, I suggest you read MULTIPLE tutorials and root your phone in addition to adding a custom ROM.
May I suggest Juggernaut V5.0. Or if you like ICS I suggest Blackedition or NexusMod
Best of luck
Click to expand...
Click to collapse
well I actually I installed a custom rom before, but for now I am on the original 2.3.4 version. I prefer ICS, I will try Both Blackedition or Nexus mod, I really appreciate your help thank you man.
J.Rawand said:
well actually I did that, but it didn't work. no my phone is not insured
but what you meant by saying that '' my hardware button is stuck ? '' sorry for that.
Click to expand...
Click to collapse
he means that the power button might be stuck. try booting into recovery, and if your phone automatically selects reboot, you know your power button is stuck.
that's somewhere to start.
J.Rawand said:
well actually I did that, but it didn't work. no my phone is not insured
but what you meant by saying that '' my hardware button is stuck ? '' sorry for that.
Click to expand...
Click to collapse
Take the Sim card and external SD card out, too. Have a drink. Put your phone back together
Sent from my SGH-T989 using xda premium
ive had this issue with darksides ROM went away I think after a bit
Sent from my SGH-T989D using XDA
This happened to my mytouch 4g.. Once u press power it turns on automativally right away.. I tried switching multiple roms and even tried unrooting it and putting it back to stock but it still happened... After many complaints tmobile insurance too it back and even gave me a brand new sensation free of charge
Sent from my SGH-T989 using xda premium
Give this a go... Back up your device beforehand.
Download Samsung Kies. Put you phone into download mode. Open Kies, and under "Tools" menu, select "Emergency firmware recovery". This will completely restore your device to stock. If you still have issues afterward, its a hardware problem.
Edit: You WILL lose root with this method. But you'll also get a definitive answer...
Unroot it and install stock
Sent from my SGH-T989 using xda premium
Is your phone plugged in when reboot? What are you charging it with? A usb cable or an actual charger?
Sent from my SGH-T989 using xda premium
I would try flashing a new ROM and especially a new kernel. Try to do it over ADB if you cant get it through recovery.
Hi everyone. I'm new to the forum and I'm looking for a little help today.
I rooted my new Sprint Galaxy S III using Odin3-v3.04, and CWM_SuperUser_v3.0.7. Afterwards I rebooted and all was good.
I then downloaded I9300_Omega_v6.0_XXALF6 ROM and loaded on my phone and rebooted into recovery to install the ROM. I went through the install process, selected remove bloatware and installed. When finished I checked the reboot phone and clicked finish. The phone turned off and didn't ever turn back on.
I have pulled the battery and tried to power on using recovery, download mode and just power but nothing works.
Anyone have any idea what I can do?
Thank you for your time and help.
alexanderd said:
Hi everyone. I'm new to the forum and I'm looking for a little help today.
I rooted my new Sprint Galaxy S III using Odin3-v3.04, and CWM_SuperUser_v3.0.7. Afterwards I rebooted and all was good.
I then downloaded I9300_Omega_v6.0_XXALF6 ROM and loaded on my phone and rebooted into recovery to install the ROM. I went through the install process, selected remove bloatware and installed. When finished I checked the reboot phone and clicked finish. The phone turned off and didn't ever turn back on.
I have pulled the battery and tried to power on using recovery, download mode and just power but nothing works.
Anyone have any idea what I can do?
Thank you for your time and help.
Click to expand...
Click to collapse
development area has a thread for that:
http://forum.xda-developers.com/showthread.php?t=1727171
ONLY use ROMs that you'll find here in these threads not the I9300; that s a different phone from ours.
Thanks I'll check there.
Honestly I was waiting for this to happen gid luck restoring it phone
Sent from my SPH-L710 using XDA
But seriously I hope you learned your lesson and will read and hope you get your phone fixed or replaced
Sent from my Sprint Galaxy Nexus CDMA using Xparent ICS Blue Tapatalk 2
Epix4G said:
But seriously I hope you learned your lesson and will read and hope you get your phone fixed or replaced
Sent from my Sprint Galaxy Nexus CDMA using Xparent ICS Blue Tapatalk 2
Click to expand...
Click to collapse
Hopefully this fail helps us all back from a potential brick. We live, flash and learn.
Sent from my SPH-D700 using xda premium
New phone on the way!
I was able to get a replacement sent from Sprint. Had to go to a corporate store and have a tech look at the phone and they agreed it was toast...
Luckily they didn't know it was due to my failed attempt to load an unsupported ROM.
Lesson learned... new phone should be in by the end of the week.
I'll be waiting for a supported ROM this time.
alexanderd said:
I was able to get a replacement sent from Sprint. Had to go to a corporate store and have a tech look at the phone and they agreed it was toast...
Luckily they didn't know it was due to my failed attempt to load an unsupported ROM.
Lesson learned... new phone should be in by the end of the week.
I'll be waiting for a supported ROM this time.
Click to expand...
Click to collapse
No wonder our insurance deductibles keep going up...
bizdady said:
No wonder our insurance deductibles keep going up...
Click to expand...
Click to collapse
+1
Still sucks for op
Sent from my SPH-L710 using Tapatalk 2
matrixzone5 said:
Honestly I was waiting for this to happen gid luck restoring it phone
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
Oh man tell me about it, I almost stupidly went on to the CM9 nightlies and downloaded the I9300 version before I thought to myself, "well wait a minute, that's not my model number!"
Duh, shoulda had a V8.
I didnt install a GSM rom but still managed to brick somehow. Didnt touch any system files or do anything to where i should be bricked either. Any idea when a full stock Odin package will be made? My phone has been bricked for almost 2 days now
Edit: i started a tread here a few days ago -> http://forum.xda-developers.com/showthread.php?t=1731416 if anyone cares to look or has any advice for me
Thanks
pizzlewizzle said:
I didnt install a GSM rom but still managed to brick somehow. Didnt touch any system files or do anything to where i should be bricked either. Any idea when a full stock Odin package will be made? My phone has been bricked for almost 2 days now
Edit: i started a tread here a few days ago -> http://forum.xda-developers.com/showthread.php?t=1731416 if anyone cares to look or has any advice for me
Thanks
Click to expand...
Click to collapse
What have you tried so far? Have you tried reflashing cwm recovery in Odin?
I did the same thing that the OP said, flashed that omega rom and now my phone wont turn on either.
I was going to try the jig method
taygutta said:
I did the same thing that the OP said, flashed that omega rom and now my phone wont turn on either.
I was going to try the jig method
Click to expand...
Click to collapse
Have you tried mskip's fix??
http://forum.xda-developers.com/showthread.php?t=1727171
bizdady said:
Have you tried mskip's fix??
http://forum.xda-developers.com/showthread.php?t=1727171
Click to expand...
Click to collapse
I want to do this but I somehow need to get the phone on. The buttons dont work.
Any luck?
My phone got stuck booting, so I tried to install the omega rom. The install worked well, and I clicked "reboot." Now the phone won't turn on. I can't get to ODIN or recovery anymore.
Did you guys find any fixes?
brickeds3 said:
My phone got stuck booting, so I tried to install the omega rom. The install worked well, and I clicked "reboot." Now the phone won't turn on. I can't get to ODIN or recovery anymore.
Did you guys find any fixes?
Click to expand...
Click to collapse
What happened is that you flashed a rom that was meant for the international version of the S3 and your on the US version. The only fix I have found is to send it to mobiletechvideos.com. I did and they say they can fix it and maybe save my data I have on it ( I just sent it in)
My fingers are crossed for the data recovery but as far as the phone I am going to send it for a exchange anyway.
Welp, I'm sad to say I just did the same thing too. Should have read. I'm a stinkin noob at this. I installed the I9300 version on a US version phone. Has there been any more development on this? Is the hardware fried, or is there a fix through that mobiletechvideos.com that was mentioned? What was the outcome of that, Taygutta, if you don't mind me re-bringing back up a potentially painful topic?? This thread made me a little sick, since it's my brother's new phone (someone else that knew what they were doing rooted it for him but he didn't like the rom, so I thought I would help him find a few other options to try flashing.)
Anyway, any confirmation that I'm buying my brother a new phone (so I can emotionally prepare for the purchase) or are there some other options?
There's one more thing you can try. There's a little device called a USB Jig. It was made for SGS-2 to clear the yellow triangle and reset flash counts in ODIN mode. It also puts your phone in ODIN mode by simply plugging it into the USB port of a powered down phone. Once in ODIN mode, you can reflash a stock ROM, recovery, etc. You can buy these for around $20 or less on the web.
If this does not work, I'm afraid nothing will.
Good luck.
6uPMAH said:
There's one more thing you can try. There's a little device called a USB Jig. It was made for SGS-2 to clear the yellow triangle and reset flash counts in ODIN mode. It also puts your phone in ODIN mode by simply plugging it into the USB port of a powered down phone. Once in ODIN mode, you can reflash a stock ROM, recovery, etc. You can buy these for around $20 or less on the web.
If this does not work, I'm afraid nothing will.
Good luck.
Click to expand...
Click to collapse
Somewhere in the thread an answer exists. You are not the first to do this.
I think the jig is the best way.
Sent from my SPH-L710 using Tapatalk 2
After installing the rXTREME v6.2 ROM for the i9305, I selected restart from Recovery and it never turned back on. The battery was fully charged before I installed this custom ROM.
- I have removed the battery for an hour and then tried again turn it on - no success. Can't get into Download mode using the 3-buttons.
- When I plug it into my laptop via USB I hear the 'connected sound' and when I remove it I hear the 'disconnected sound', but I do not see any ability to access the phone via Windows Explorer. The driver is found and connected too.
- I tried using Odin and it say's "Added!" when I connect, but the COM:x field is 'yellow', not blue. (Keep in mind I can't get into Download mode on my phone, but I still tried with Odin) I load the right PDA file (I9305XXBMA3_I9305MEOBMA1_I9305XXBLL5_HOME.tar.md5) and have 'Auto Reboot' and 'F. Reset Time' checked. Odin message stays on status "SetupConnection..". I've left it this way many times, one time overnight. But with no success.
Any advice??? Please help :/
Re: Galaxy s3 i9305 won't turn on after installing custom rom (AT&T LTE 4G version)
You are hard bricked. You flashed an international ROM to a us phone (or vice versa, your thread title is a little confusing on what device model you have)
JTAG or send to Samsung.
Sent from my SGH-I747 using xda app-developers app
Re: Galaxy s3 i9305 won't turn on after installing custom rom (AT&T LTE 4G version)
I'm not sure he's hard bricked. Hard brick means no signs of life. Odin can see it, so there's obviously some sign of life. You need to find the proper stock firmware for your phone and try to flash back to stock
Re: Galaxy s3 i9305 won't turn on after installing custom rom (AT&T LTE 4G version)
mrhaley30705 said:
I'm not sure he's hard bricked. Hard brick means no signs of life. Odin can see it, so there's obviously some sign of life. You need to find the proper stock firmware for your phone and try to flash back to stock
Click to expand...
Click to collapse
ODIN also detects hard bricks. It usually shows up as an unknown device with no drivers and can't be flashed. I've been there and done that with my own hard brick.
As his post says his phone won't boot, even after a battery pull and can't get into download or recovery. That would be no signs of life.
I have seen it happen too many times with people flashing international ROMs to their us devices. 95% of the time it is always a hard brick.
Unless he provides us with an update showing that the phone can boot, at all, even a flicker of the screen, its a dead phone. =/
Sent from my SGH-I747 using xda app-developers app
bshend said:
rXTREME v6.2 ROM for the i9305
Click to expand...
Click to collapse
if the phone won't turn on by any mean... you got yourself hard bricked.
people should really read before they actually flash a new rom... what you flashed is an international version.
but that's also weird... if i recall, some people mentioned when they flash international roms, they only got themselves soft bricked..
Re: Galaxy s3 i9305 won't turn on after installing custom rom (AT&T LTE 4G version)
pcshano said:
if the phone won't turn on by any mean... you got yourself hard bricked.
people should really read before they actually flash a new rom... what you flashed is an international version.
but that's also weird... if i recall, some people mentioned when they flash international roms, they only got themselves soft bricked..
Click to expand...
Click to collapse
I concur. Too many people gloss over the thread to flash whatever they feel like it. (even saw people using a vzw app to unlock their att boot loader.. which isn't even locked. also hard bricked. )
The lucky few do get a soft brick. Those lucky few were able to see the Samsung boot logo though. It all depends on the ROM. For instance if you flash the international foxhound ROM its a guaranteed brick. 3 different people in a 2 day span I helped not too long ago. all flashed foxhound all hard bricks.
Sent from my SGH-I747 using xda app-developers app
RPelham said:
I concur. Too many people gloss over the thread to flash whatever they feel like it. (even saw people using a vzw app to unlock their attack boot loader.. which isn't even locked. also hard bricked. )
I really feel XDA should implement a test on reading comp and flashing basics before you are allowed access to dev forums for ROMs.
The lucky few do get a soft brick. Those lucky few were able to see the Samsung boot logo though. It all depends on the ROM. For instance if you flash the international foxhound ROM its a guaranteed brick. 3 different people in a 2 day span I helped not too long ago. all flashed foxhound all hard bricks.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
people should really do research before actually doing it in any way.
Do you get any signs of life on the screen at all? Either Recovery or Download mode? The Galaxy S3 splash screen? Anything at all?
If not, then it's a hard brick and you can get it repaired via a JTAG service (check eBay).
However, if you get ANY signs of life on the screen at all, even if for just a moment, then you might be able to repair things yourself.
innos D9 doesn't switch on properly
CZ Eddie said:
Do you get any signs of life on the screen at all? Either Recovery or Download mode? The Galaxy S3 splash screen? Anything at all?
If not, then it's a hard brick and you can get it repaired via a JTAG service (check eBay).
However, if you get ANY signs of life on the screen at all, even if for just a moment, then you might be able to repair things yourself.
Click to expand...
Click to collapse
I bought the Innos D9 and I replaced the rom with the DNS rom and it was working properly till i decided to install the Cloudfone rom .........
after installed the Cloudfone rom I decided to get back the DNS rom and here my phone die ........
now the only thing I see when I switch on my phone is the Cloudfone logo and some stripe .
any help will be really appreciated.
thepinkpanter said:
I bought the Innos D9 and I replaced the rom with the DNS rom and it was working properly till i decided to install the Cloudfone rom .........
after installed the Cloudfone rom I decided to get back the DNS rom and here my phone die ........
now the only thing I see when I switch on my phone is the Cloudfone logo and some stripe .
any help will be really appreciated.
Click to expand...
Click to collapse
You posted in the AT&T, Rogers, Bell, Telus Samsung Galaxy S III section - not sure how much help you will get for that device here.
kbatman74 said:
You posted in the AT&T, Rogers, Bell, Telus Samsung Galaxy S III section - not sure how much help you will get for that device here.
Click to expand...
Click to collapse
big mistake.......you are right ,
thanks alot
CZ Eddie said:
Do you get any signs of life on the screen at all? Either Recovery or Download mode? The Galaxy S3 splash screen? Anything at all?
If not, then it's a hard brick and you can get it repaired via a JTAG service (check eBay).
However, if you get ANY signs of life on the screen at all, even if for just a moment, then you might be able to repair things yourself.
Click to expand...
Click to collapse
thanks great tip will try that to see if mine works!!!!!!
Help me please
hi everyone
I have a problem or a question you just installed cyanogen mod RC1 4.3 on my samsung sgh i747m s3 but display increased consumption up to 70% wanted to know why and also have another question that does not bring the system settings as limiting processes and overclocking put a little less so that is not forced nor brings battery saving I would like to have those two options in cm7 when handling it but this had not anyone know how to put these two options?
I hope your answer!
Thank you!
Thony18 said:
hi everyone
I have a problem or a question you just installed cyanogen mod RC1 4.3 on my samsung sgh i747m s3 but display increased consumption up to 70% wanted to know why and also have another question that does not bring the system settings as limiting processes and overclocking put a little less so that is not forced nor brings battery saving I would like to have those two options in cm7 when handling it but this had not anyone know how to put these two options?
I hope your answer!
Thank you!
Click to expand...
Click to collapse
Your problem has absolutely no impact or solution to the original problem? Create your own thread or use the search function to find a thread with a similar problem you might find a solution or at least people might help you.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Alright so first off I already already read about 20 threads on this topic. The problem is that the phone is stuck on the Samsung screen when I try to turn it on. I can go into recovery mode (Home+Down+Power), and ODIN recognizes the phone. When I put the phone in my computer ODIN recognizes it. Now one thing I did when I rooted this phone by accident was put the .tar file in the bootloader part of odin and not the PDA part.
Additional information: Sprint version, US
When I use ODIN to try to load the stock recovery it saus there is no PIT partition
Search around the original Dev threads. I believe there is a post in there that contains the pit files needed for odening the phone.
Sent from my SPH-L900 using xda app-developers app
xKrisx said:
Search around the original Dev threads. I believe there is a post in there that contains the pit files needed for odening the phone.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Yeah I found a few but the link was no longer available for download. Trying to download the second one off http://forum.xda-developers.com/showpost.php?p=32273406&postcount=5 hope it works.
That did not do anything I think im going to try and see if Sprint will still accpet it.
Mo_Mann said:
That did not do anything I think im going to try and see if Sprint will still accpet it.
Click to expand...
Click to collapse
Try this... but read it. Then when you are done reading it, read it again before you do anything!!!
I'm experiencing the same problem but my phone has no warranty. I bought it some place else. I googled about the problem but no luck so far. I just find it weird that a lot of people are experiencing the same problem recently.. I found this
http://pomeroy.me/2013/02/solved-samsung-galaxy-note-ii-stuck-on-samsung-logo/
but it didn't really help me as mine is stuck on the Samsung Galaxy note II loading screen, not exactly the samsung logo. It might help you so be sure to try it out.
><
Hello every one! so yesterday while doing nothing but leaving my phone on a markipilers youtube video, I see my screen go off I try to turn it back on and nothing happens. I tried power cycling and its still off, just not responding to anything, no sound no light no nothing. I tried then going to recovery mode but well... nothing happened. The only thing that actually makes any responses is when I connect it using a USB to my laptop, my laptop beeps, its not suposed to beep it is broken so is it bricked?
My device is a rooted Samsung galaxy s4 mini i19192 or so I hope it is.
I really hope that this is the right place to be redirected to assistant if not then Iam really sorry, thank you so much every one and have a fantastic day!
Edit: I forgot to mention two things.
1st: It does not seem to charge the battary, I kniw this because I have another identical one though the battary works fine in the working one
2nd: My PC reads it as (something?)_dload, Sadly I do not have acess to a computer just yet. Thanks again
Any help.. please?
Khaled125 said:
Hello every one! so yesterday while doing nothing but leaving my phone on a markipilers youtube video, I see my screen go off I try to turn it back on and nothing happens. I tried power cycling and its still off, just not responding to anything, no sound no light no nothing. I tried then going to recovery mode but well... nothing happened. The only thing that actually makes any responses is when I connect it using a USB to my laptop, my laptop beeps, its not suposed to beep it is broken so is it bricked?
My device is a rooted Samsung galaxy s4 mini i19192 or so I hope it is.
I really hope that this is the right place to be redirected to assistant if not then Iam really sorry, thank you so much every one and have a fantastic day!
Edit: I forgot to mention two things.
1st: It does not seem to charge the battary, I kniw this because I have another identical one though the battary works fine in the working one
2nd: My PC reads it as (something?)_dload, Sadly I do not have acess to a computer just yet. Thanks again
Click to expand...
Click to collapse
probably QHSUSB_DLOAD, which is a hard brick, you might be able to fix with a debrick image
Sent from my Galaxy S4 Mini using XDA Labs
its in fact qshusb_dload but iam still a bit clueless on the reason or which method to solve. I read its because the cpu is trying to boot from the sd card and has something to do with something called emmac that is terrible in the s4 so I read three methods to solve
1- Just your method
2- Cooling the emmc?
and three, this
http://cellphonetrackers.org/qhsusb_dload-fix-qualcomm-soc.html
so Iam a bit distracted on what to even do or how to do it, any help would be apriciated plus any further notices about how to even avoid the problem
and thank you so much @IronRoo for your noticable contributions to these stuff!
Khaled125 said:
its in fact qshusb_dload but iam still a bit clueless on the reason or which method to solve. I read its because the cpu is trying to boot from the sd card and has something to do with something called emmac that is terrible in the s4 so I read three methods to solve
1- Just your method
2- Cooling the emmc?
and three, this
http://cellphonetrackers.org/qhsusb_dload-fix-qualcomm-soc.html
so Iam a bit distracted on what to even do or how to do it, any help would be apriciated plus any further notices about how to even avoid the problem
and thank you so much @IronRoo for your noticable contributions to these stuff!
Click to expand...
Click to collapse
Yes, the eMMC is prone to fail/corruption on our phones, at least I think. The eMMC is the internal SD memory. Hopefully yours is just corrupt.
The cooling trick is probably only good if there is a bad soldier joint on the chip and will probably only work a few minutes as the board will heat up once turned on
I would try the debrick file as that's probably the easiest. See also Valenti's post on other Samsung device, as better write up on one (Samsung Mega maybe?) as well as by the others who originally come up with the debrick idea to get a better idea of what to do.
I guess (without researching) the method in your link is the same principle as the debrick file but may work even if debrick doesn't work as not dependant on having a matching file from phone with same bootloader (???? I don't know as haven't looked into that method)
Also you can send phone away for jtag if nothing else works
Sent from my Galaxy S4 Mini using XDA Labs
IronRoo said:
Yes, the eMMC is prone to fail/corruption on our phones, at least I think. The eMMC is the internal SD memory. Hopefully yours is just corrupt.
The cooling trick is probably only good if there is a bad soldier joint on the chip and will probably only work a few minutes as the board will heat up once turned on
I would try the debrick file as that's probably the easiest. See also Valenti's post on other Samsung device, as better write up on one (Samsung Mega maybe?) as well as by the others who originally come up with the debrick idea to get a better idea of what to do.
I guess (without researching) the method in your link is the same principle as the debrick file but may work even if debrick doesn't work as not dependant on having a matching file from phone with same bootloader (???? I don't know as haven't looked into that method)
Also you can send phone away for jtag if nothing else works
Click to expand...
Click to collapse
Thats great! thank you. however can you give me a link to download that file / tutorial as iam not sure google would help me in that. second off I have no idea where Valenti's post either so that would just be fantastic if you can, Thanks again for every thing!
Khaled125 said:
Thats great! thank you. however can you give me a link to download that file / tutorial as iam not sure google would help me in that. second off I have no idea where Valenti's post either so that would just be fantastic if you can, Thanks again for every thing!
Click to expand...
Click to collapse
There are some debrick files here for some of the S4 Mini models (some have broken links but some still work, or find others on internet. This is also one of the thread started by @ValenteL
http://forum.xda-developers.com/showthread.php?t=2625628&page=10
Sent from my Galaxy S4 Mini using XDA Labs
IronRoo said:
There are some debrick files here for some of the S4 Mini models (some have broken links but some still work, or find others on internet. This is also one of the thread started by @ValenteL
http://forum.xda-developers.com/showthread.php?t=2625628&page=10
Click to expand...
Click to collapse
Wanderful, Thank you! should I mark this as solved?
IronRoo said:
There are some debrick files here for some of the S4 Mini models (some have broken links but some still work, or find others on internet. This is also one of the thread started by @ValenteL
http://forum.xda-developers.com/showthread.php?t=2625628&page=10
Click to expand...
Click to collapse
I have been searching for ever and still zero luck on finding either a way through the s4 mini nor the actual debrick file... all I could find was for the s3 all over, any help?
Khaled125 said:
I have been searching for ever and still zero luck on finding either a way through the s4 mini nor the actual debrick file... all I could find was for the s3 all over, any help?
Click to expand...
Click to collapse
Did you try the two debrick images in my post dated the 22nd March in the thread I posted above?
Actually I also pulled one from my phone after I read you can generate one from Cyanogenmod phones that will also work, I will post that on the above thread also a bit later.
Sent from my Galaxy S4 Mini using XDA Labs
IronRoo said:
Did you try the two debrick images in my post dated the 22nd March in the thread I posted above?
Actually I also pulled one from my phone after I read you can generate one from Cyanogenmod phones that will also work, I will post that on the above thread also a bit later.
Click to expand...
Click to collapse
Just found it, Though if your link would have directed to page 8 rather than 10 that would have been fantastic! I thought You ment the main post which also helped me alot. How ever do I really have to downoad monster legands to be able to download the foking file?
oh never mind, Just a damn ad
IronRoo said:
Did you try the two debrick images in my post dated the 22nd March in the thread I posted above?
Actually I also pulled one from my phone after I read you can generate one from Cyanogenmod phones that will also work, I will post that on the above thread also a bit later.
Click to expand...
Click to collapse
Oh and how do you flash that thing to recovery, How do you pull that debrick file? is really confusing me
And please pardon me if my questions are spammy or annoying, There are a whole lot of steps through it and neither google nor the forum seem to be answering it so I might just consult you for that.
From what I understand, You flash the debrick file to the sd card using this 32 bit sd flasher thing and then it just works because the booting files are on the sd card but it will not boot without it. So how can you fix the corrupted boot loader AND how can I restore my sd card back to normal, I have seen a video for it but he is using ubuntu and command lines and stuff.
Khaled125 said:
Oh and how do you flash that thing to recovery, How do you pull that debrick file? is really confusing me
Click to expand...
Click to collapse
The original post by @ValenteL was a file to generate a debrick image, but you need a working phone to use that.
People with phones that are already bricked have to get a debrick file from someone else. This debrick image must be put onto an 16Gig (some report success with 32gig) SD card that is formatted (so you will lose everything else on it) and then the phone will boot with it instead of internal mmc to get your phone going (you have to keep the SD in) so you can then recover data and also hopefully flash a new rom later so you don't need to always boot from SD.
Sent from my Galaxy S4 Mini using XDA Labs
IronRoo said:
The original post by @ValenteL was a file to generate a debrick image, but you need a working phone to use that.
People with phones that are already bricked have to get a debrick file from someone else. This debrick image must be put onto an 16Gig (some report success with 32gig) SD card that is formatted (so you will lose everything else on it) and then the phone will boot with it instead of internal mmc to get your phone going (you have to keep the SD in) so you can then recover data and also hopefully flash a new rom later so you don't need to always boot from SD.
Click to expand...
Click to collapse
Yes, that was what I understood already but thank you anyway! My question was How? on both creating the debrick file and restoring both sd card (too make it work as a readable card rather than a booting device if it does not already) and fix the phones internal memory without actually reseting the whole phone and if there are no way else to fix internal memory... to back up the whole thing.
thank you!
IronRoo said:
Did you try the two debrick images in my post dated the 22nd March in the thread I posted above?
Actually I also pulled one from my phone after I read you can generate one from Cyanogenmod phones that will also work, I will post that on the above thread also a bit later.
Sent from my Galaxy S4 Mini using XDA Labs
Click to expand...
Click to collapse
WANDEFUL! My phone actually viperated and showed color!
however.. it gives this on a black screen.
boot recovery
check boot partitions
copy from t flash
boot recovery
write 139008
reboot
and obviously reboots, thoughts?
My last two posts are the most important now, if you or any one else can answer that would be fantastic!
some notes: after searching the thing does not mention emmc nor odin at all like for some others with the same issue... just this plain text.
I had upgraded my android version to 4.4.2 not 4.2.2 so I assume that is important, thanks again and please answer as soon as you can as that would be great! thank you for every thing @IronRoo
Khaled125 said:
My last two posts are the most important now, if you or any one else can answer that would be fantastic!
some notes: after searching the thing does not mention emmc nor odin at all like for some others with the same issue... just this plain text.
I had upgraded my android version to 4.4.2 not 4.2.2 so I assume that is important, thanks again and please answer as soon as you can as that would be great! thank you for every thing @IronRoo
Click to expand...
Click to collapse
I think the important thing is the bootloader (& pit must be the same) that if I recall was updated from the version you mention to ver 2. So you need a debrick with the ver 2 bootloader. (but I am not 100% sure about this, only read some stuff last year) My phone BL is ver 1
a guy on the below Mega thread with an I9195 did get a stop further by repeating multiple times
http://forum.xda-developers.com/showthread.php?t=2600976&page=4
But still didn't fix phone fully
read next few pages, one guy used freeze fix white partial success, might be useful if you want to get data off phone.
Also another link that may offer help
but probably your emmc is bad, is my guess
gotta go now, work calls
Sent from my Galaxy S4 Mini using XDA Labs
IronRoo said:
I think the important thing is the bootloader, that if I recall was updated from the version you mention to ver 2. So you need a debrick with the ver 2 bootloader. (but I am not 100% sure about this, only read some stuff last year) My phone BL is ver 1
a guy on the below Mega thread with an I9195 did get a stop further by repeating multiple times
http://forum.xda-developers.com/showthread.php?t=2600976&page=4
But still didn't fix phone fully
read next few pages, one guy used freeze fix white partial success, might be useful if you want to get data off phone.
Also another link that may offer help
but probably your emmc is bad, is my guess
gotta go now, work calls
Sent from my Galaxy S4 Mini using XDA Labs
Click to expand...
Click to collapse
Thats great! good luck at your work, when you are back though I need to tell you this
I have another device of the exact same model that is kikkat not rooted (kitkat will have bootloader version 2 right?) if only I knew how to get the file out and then do all the stuff again, ill keep searching since you are at work now, will keep you updated. please help about it though if you can*
so if someone say for example has android 5 on an s4 mini, he will never get his phone back to work unless some one made a debrick file for it? if the previous statments were true?
My questions are:
Extract that file from the other phone, if I managed to answer it ill tell you.
To get my SD card back to work and fix my emmc
Iam not giving up on my emmc yet though, iam sure there is a way to solve it, if not then how to fix that failed emmc?
thanks again!