Related
My Galaxy S turns off randomly. It wont turn on until I remove the battery and put it back. It is running Android 2.2.1. Has this happened to anyone of you? Is there a solution for this?
Happening to me as well... Froyo Update screwed my phone, Planning to flash a custom ROM now... Lets hope that solves some issues...
Are you using Launcher Pro ?
It was causing the same thing to me on my i9003
ybyb said:
Are you using Launcher Pro ?
It was causing the same thing to me on my i9003
Click to expand...
Click to collapse
I am using the stock ROM with all stock stuffs. Even the launcher is stock.
Backup data and factory reset .
jje
JJEgan said:
Backup data and factory reset .
jje
Click to expand...
Click to collapse
I had done that a few days ago. The problem had stopped, but then started today again.
Are you running stock ROM? If yes I'd try to replace the phone.
Jens
Jens1969 said:
Are you running stock ROM? If yes I'd try to replace the phone.
Jens
Click to expand...
Click to collapse
I got the phone a month ago. I'll try to flash a different ROM.
aakaashjois said:
I got the phone a month ago. I'll try to flash a different ROM.
Click to expand...
Click to collapse
Month old = back to service centre .
Flash rom = no warranty and possible bricked phone .
jje
JJEgan said:
Month old = back to service centre .
Flash rom = no warranty and possible bricked phone .
jje
Click to expand...
Click to collapse
I'll flash a ROM and see if it solves the problem. If it still stays, I'll flash the factory ROM and take it to the service centre.
aakaashjois said:
I'll flash a ROM and see if it solves the problem. If it still stays, I'll flash the factory ROM and take it to the service centre.
Click to expand...
Click to collapse
haha if it's me, I would not even try to flash a custom ROM. If everything is stock and it acted that way, obviously it is problematic. Send it back
I flashed Gingerbread. Problem solved. Its not happening anymore.
Well, I had exactly the same problem when I got the phone originally. I actually called my provider and got an RMA. However I decided to try and install a custom ROM and haven't looked back since.
I started with Darky's ROM and all those problems disappeared. If I were Samsung, I'd be giving Darky a job very fast. Lol!
Sent from my GT-I9000 using XDA App
I just turned on my phone but suddenly my screen doesn't function anymore. I doesn't react on me touching the screen. Anyone familiar with this? I turned it off for a while but after turning it on again, it just doesn't react on me touching the screen. The screen looks normal and so on..... A few minutes ago everything was still working!!! Please help !
Edit: also in recovery the screen doesn't react....
I have a Xperia T, unlocked bootloader(for a long time) and OmniRom 4.4.2 (for a long time as well). Haven't changed anything for a week, no flash or whatsoever.
olafd72 said:
I just turned on my phone but suddenly my screen doesn't function anymore. I doesn't react on me touching the screen. Anyone familiar with this? I turned it off for a while but after turning it on again, it just doesn't react on me touching the screen. The screen looks normal and so on..... A few minutes ago everything was still working!!! Please help !
Edit: also in recovery the screen doesn't react....
I have a Xperia T, unlocked bootloader(for a long time) and OmniRom 4.4.2 (for a long time as well). Haven't changed anything for a week, no flash or whatsoever.
Click to expand...
Click to collapse
im not sure . but just flash the stock rom via flash tool and check whether the screen is functioning or not
romeoofair said:
im not sure . but just flash the stock rom via flash tool and check whether the screen is functioning or not
Click to expand...
Click to collapse
Is that really possible, when I have an unlocked bootloader and a custom rom (4.4.2 Omnirom) ?
olafd72 said:
Is that really possible, when I have an unlocked bootloader and a custom rom (4.4.2 Omnirom) ?
Click to expand...
Click to collapse
tuzmaster_v2 said:
just google the JB 4.1 ftf and flash it, it's the best way for now. :good:
Click to expand...
Click to collapse
Just flashed a 141 ftf but no luck Still no response! The only thing, just to warn you, was the above and set the governor to NOOP in the Performance.... I cannot imagine this caused it, but just in case.
Any other suggestions to solve this? Quite sad here..... Now that I have flashed the original 141 to my phone, I reckon I still have a unlocked bootloader and cannot hand this over to Sony to repair this under warranty? How do I lock the bootloader or even simply said; how do I flash it to stock so Sony can repair it?
Thanks again!
olafd72 said:
Just flashed a 141 ftf but no luck Still no response! The only thing, just to warn you, was the above and set the governor to NOOP in the Performance.... I cannot imagine this caused it, but just in case.
Any other suggestions to solve this? Quite sad here..... Now that I have flashed the original 141 to my phone, I reckon I still have a unlocked bootloader and cannot hand this over to Sony to repair this under warranty? How do I lock the bootloader or even simply said; how do I flash it to stock so Sony can repair it?
Thanks again!
Click to expand...
Click to collapse
no. changing the governor to noop is not responsible for this as i m also using it in noop. i dont know how to relock it. just check the forums. or you may get your problem solved within 24 hr if its just a software issue and some dev refers your problem
---------- Post added at 03:25 PM ---------- Previous post was at 03:25 PM ----------
olafd72 said:
Is that really possible, when I have an unlocked bootloader and a custom rom (4.4.2 Omnirom) ?
Click to expand...
Click to collapse
ya . it is possible to flash
romeoofair said:
no. changing the governor to noop is not responsible for this as i m also using it in noop. i dont know how to relock it. just check the forums. or you may get your problem solved within 24 hr if its just a software issue and some dev refers your problem
---------- Post added at 03:25 PM ---------- Previous post was at 03:25 PM ----------
ya . it is possible to flash
Click to expand...
Click to collapse
Thanks. Well, I just flashed it, as I already mentioned, so I discovered it is possible already
So after flashing this stock 141 ftf, the blootloader is still unlocked?
olafd72 said:
Thanks. Well, I just flashed it, as I already mentioned, so I discovered it is possible already
So after flashing this stock 141 ftf, the blootloader is still unlocked?
Click to expand...
Click to collapse
of course
I've had the same problem twice now on Omnirom 4.4.
The fix is it flash the ftf followed by a kernel elf file with a CWM recovery already eg DooMkernel on flashtool. Then reboot into recovery and flash .141 zip or similar do all wipes.
olafd72 said:
Thanks. Well, I just flashed it, as I already mentioned, so I discovered it is possible already
So after flashing this stock 141 ftf, the blootloader is still unlocked?
Click to expand...
Click to collapse
no bro it has nothing to do with the bootloader. its still unlocked :good:. did you also flash the kernel?
binloud said:
I've had the same problem twice now on Omnirom 4.4.
The fix is it flash the ftf followed by a kernel elf file with a CWM recovery already eg DooMkernel on flashtool. Then reboot into recovery and flash .141 zip or similar do all wipes.
Click to expand...
Click to collapse
Thanks! That sounds nice! Will flash Doom then! I did not flash the kernel.Just the .141 ftf file. It does show me the Sony logo, Xperia, and color splash screen though...
I just locked the bootloader again..... is that a problem?
olafd72 said:
Thanks! That sounds nice! Will flash Doom then! I did not flash the kernel.Just the .141 ftf file. It does show me the Sony logo, Xperia, and color splash screen though...
I just locked the bootloader again..... is that a problem?
Click to expand...
Click to collapse
OK, read that you need an unlocked bootloader so I unlocked it again. Doomkernel says I need .145 as requirement. I have 141. Will that be a problem, since I cannot find a .145 stock that fast.
I unlocked the bootloader, flashed the Doomkernel and then the 141 but still no luck.....:crying:
OK, good news! After leaving it off for like 30 minutes, after doing the above, it worked again after turning it on again! I want to have it all back to stock, kernel and so on. Where do I find the original kernel for 141? By the way; I thought that 145 was the latest?
olafd72 said:
OK, good news! After leaving it off for like 30 minutes, after doing the above, it worked again after turning it on again! I want to have it all back to stock, kernel and so on. Where do I find the original kernel for 141? By the way; I thought that 145 was the latest?
Click to expand...
Click to collapse
****, an hour ago the samen problem..... Again the screen does not respond..... damn! Any ideas left?
I flashed 5.1.1 using via odin 3.10 (no errors etc.) now my phone stuck at Powered by Android screen. I tried to reflash the firmware many times but still the same thing.
Before flashing 5.1.1 my phone was running Looper firmware. I did modify the build.prop (ro.securitystorage = false). Does this cause the issue?
When i get into recovery mode i see this yellow text
"dm-verity verification failed...
Need to check DRK first..."
Please help me to revive this phone. Thank you
aloric said:
I flashed 5.1.1 using via odin 3.10 (no errors etc.) now my phone stuck at Powered by Android screen. I tried to reflash the firmware many times but still the same thing.
Before flashing 5.1.1 my phone was running Looper firmware. I did modify the build.prop (ro.securitystorage = false). Does this cause the issue?
When i get into recovery mode i see this yellow text
"dm-verity verification failed...
Need to check DRK first..."
Please help me to revive this phone. Thank you
Click to expand...
Click to collapse
If you get stuck in a boot loop go into recovery and do a factory reset!
Follow these instructions :
1. press: power/home/vol up keys at the same time.
2. Use vol up/down to get to factory reset
2. press pwr button to select
3. maneuver to erase user data, select using pwr button
4. maneuver to erase cache partition,select using pwr button.
4. Reboot
I did all those steps many times and reflashed the rom like 10 times.. Still the same thing
aloric said:
I did all those steps many times and reflashed the rom like 10 times.. Still the same thing
Click to expand...
Click to collapse
Where did you download the firmware from?
http://forum.xda-developers.com/tmo...nt/rom-g920tuvu2cof6g920ttmb2cof6tmb-t3135673
other S6 edge users got the same issue http://forum.xda-developers.com/tmobile-galaxy-s6-edge/help/stuck-samsung-logo-t3136215
was the imei repaired or your phone unlocked before?
Sunderwear said:
was the imei repaired or your phone unlocked before?
Click to expand...
Click to collapse
yes
aloric said:
yes
Click to expand...
Click to collapse
then thats what caused it.
Sunderwear said:
then thats what caused it.
Click to expand...
Click to collapse
That's sad. Hope someone can find a solution. Now i have a $600 paper weight
aloric said:
That's sad. Hope someone can find a solution. Now i have a $600 paper weight
Click to expand...
Click to collapse
go into your bootloader..see if knox warranty is 0x0
So if the phone was unlocked you can't flash via Odin?
---------- Post added at 07:22 PM ---------- Previous post was at 07:22 PM ----------
I mean officially unlocked with the t-mobile app
TheArtiszan said:
So if the phone was unlocked you can't flash via Odin?
---------- Post added at 07:22 PM ---------- Previous post was at 07:22 PM ----------
I mean officially unlocked with the t-mobile app
Click to expand...
Click to collapse
if you unlocked the offical way..you have nothing to worry about
yay... i fixed the issue. My phone is back to life again
I have same problem.
aloric said:
yay... i fixed the issue. My phone is back to life again
Click to expand...
Click to collapse
How did you fix you phone ? I have same problem need help please.
restore your efs back up (original one) then reflash the rom via odin. If you don't have your original back up then you're out of luck
Wow. That's crazy. Guess it just goes to show how important backing up your efs is. I haven't, but I'm also not a Samsung guy. I will now.
EFS
mikeyinid said:
Wow. That's crazy. Guess it just goes to show how important backing up your efs is. I haven't, but I'm also not a Samsung guy. I will now.
Click to expand...
Click to collapse
WHATS EFS???
mikeyinid said:
Wow. That's crazy. Guess it just goes to show how important backing up your efs is. I haven't, but I'm also not a Samsung guy. I will now.
Click to expand...
Click to collapse
It's extremely important to do it on lg phones also. Well it's important for every phone just in case of worst case scenario, having a working imei is nice
That's it seriously!!!!!!!
aloric said:
restore your efs back up (original one) then reflash the rom via odin. If you don't have your original back up then you're out of luck
Click to expand...
Click to collapse
seriously
I did what you did (restoring EFS)(reflashing stock via odin) with no luck
is there any thing else you've done?
So i purchased a Note 4 SM-N910T about a year ago. It worked fine but last month shortly after the 5.1.1 update I did it started randomly restarting for no reason. First i taught it was Snapchat because I red somewhere that there are camera problems, so I stopped using it. But it kept restarting even after that. From then I have made a factory and a master reset, rooted the phone and even installed CM 12. No mater what i do it keeps on restarting. The only way to get it out of the boot loop is to connect it to a charger that is not a fast charger. Then it starts charging and works normally and you can do everything normally. After you remove it from the charger it works as long as you do not use it. When you start using it and want to do something with it it starts restarting again. I hope somebody can help me fix this issue. I have noticed that connecting it to WIFI makes it 100% sure that it will restart any moment. If you leave it without WIFI as long as you do not do anything big it will not restart. For example I watched series on my phone I downloaded beforehand. I was able to go to the CM 12 file manager and change series for the duration of my bus drive and it has not reset yet and it has not been connected to a charger for around 12 hours already.
My last resort is to wait 3 hours for the stupid free 5.0.1 official firmware and flash it using the TWRP Recovery or Odin. If that does not work I would have t give it to a service. Any help will be greatly appreciated! Also a link to where I can download the 5.0.1 official firmware for free in normal speed will be of greatly appreciated as well!
Merry Christmas!
That's odd, I recommend odin flashing the stock ROM and everything. (Modem + bootloader) the latest one is DOK2 for T-Mobile
MisterCoolBeans said:
That's odd, I recommend odin flashing the stock ROM and everything. (Modem + bootloader) the latest one is DOK2 for T-Mobile
Click to expand...
Click to collapse
Do you have a link to where I could download that because all I found were sites where the free user speeds took 3 hours to download 1.5 GB?:crying:
Let me see if I can find one
---------- Post added at 04:41 PM ---------- Previous post was at 04:40 PM ----------
Here is the full untouched ROM that you can download from Sammobile but it was uploaded to mega instead.
http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858
Make sure you click the first link!
MisterCoolBeans said:
Let me see if I can find one
---------- Post added at 04:41 PM ---------- Previous post was at 04:40 PM ----------
Here is the full untouched ROM that you can download from Sammobile but it was uploaded to mega instead.
http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858
Make sure you click the first link!
Click to expand...
Click to collapse
Thank you very much! I put it for download and it has a reasonable speed. After its done I will try and flash it! I hope the problem does not occur anymore!
Lazarov987 said:
Thank you very much! I put it for download and it has a reasonable speed. After its done I will try and flash it! I hope the problem does not occur anymore!
Click to expand...
Click to collapse
So since the phone restarts when I connect it to the WIFI should i also flash the stock modem or just try first without it?
Lazarov987 said:
So since the phone restarts when I connect it to the WIFI should i also flash the stock modem or just try first without it?
Click to expand...
Click to collapse
If you flash the stock firmware it includes the baseband and modem
ShrekOpher said:
If you flash the stock firmware it includes the baseband and modem
Click to expand...
Click to collapse
To revive the thread I tried flashing the N910TUVU2DOK2_N910TTMB2DOK2_N910TUVU2DOK2_HOME.tar via Odin. It all went fine and after starting the phone it went on to the step where its optimizing apps. It got stuck there and it went back to the boot loop. I had reflash the CM 12 and TWRP Recovery and now I am back at 0. So my question is how should I flash the stock rom. Go to TWRP do a factory reset than turn the phone off and flash the stock rom via Odin? Should I also flash TWRP ans SuperSu after flashing the stock rom?
Thank you for your help!
I've been having the same problem for about a week and a half; it's super annoying. I was running Dynamic Pop on COG2 then yesterday I updated to DOK2 and flashed Maximum Overdrive... no improvement. It rarely even fully boots before freezing or rebooting.
My best guess as to what the problem is that it may be overheating because it tends to actually boot if I put it in the freezer while booting, but then it freezes soon after taking it out. I suppose it could also be internal memory corruption.
Either way, I'm getting ready to do a warranty exchange.
Lazarov987 said:
To revive the thread I tried flashing the N910TUVU2DOK2_N910TTMB2DOK2_N910TUVU2DOK2_HOME.tar via Odin. It all went fine and after starting the phone it went on to the step where its optimizing apps. It got stuck there and it went back to the boot loop. I had reflash the CM 12 and TWRP Recovery and now I am back at 0. So my question is how should I flash the stock rom. Go to TWRP do a factory reset than turn the phone off and flash the stock rom via Odin? Should I also flash TWRP ans SuperSu after flashing the stock rom?
Thank you for your help!
Click to expand...
Click to collapse
First focus on getting a clean stock firmware booted. Do what you mentioned above but don't flash TWRP or superSu until the stock ROM is stable. We need to narrow down the issues so do as few modifications as possible.
---------- Post added at 06:02 AM ---------- Previous post was at 06:01 AM ----------
jazzmachine said:
I've been having the same problem for about a week and a half; it's super annoying. I was running Dynamic Pop on COG2 then yesterday I updated to DOK2 and flashed Maximum Overdrive... no improvement. It rarely even fully boots before freezing or rebooting.
My best guess as to what the problem is that it may be overheating because it tends to actually boot if I put it in the freezer while booting, but then it freezes soon after taking it out. I suppose it could also be internal memory corruption.
Either way, I'm getting ready to do a warranty exchange.
Click to expand...
Click to collapse
You may have messed up the partitions. There is a thread about the pit file you should check out.
ShrekOpher said:
First focus on getting a clean stock firmware booted. Do what you mentioned above but don't flash TWRP or superSu until the stock ROM is stable. We need to narrow down the issues so do as few modifications as possible.
---------- Post added at 06:02 AM ---------- Previous post was at 06:01 AM ----------
You may have messed up the partitions. There is a thread about the pit file you should check out.
Click to expand...
Click to collapse
What thread is that and how do I find it? I mean I always checked that in Odin i never had Re-partition on.
ShrekOpher said:
First focus on getting a clean stock firmware booted. Do what you mentioned above but don't flash TWRP or superSu until the stock ROM is stable. We need to narrow down the issues so do as few modifications as possible.
---------- Post added at 06:02 AM ---------- Previous post was at 06:01 AM ----------
You may have messed up the partitions. There is a thread about the pit file you should check out.
Click to expand...
Click to collapse
I actually downloaded 2 stock roms for my Note 4. One was the COG2 and the other one was the completely stock firmware. I tried flashing them but Odin failed (Auth) whatever that means. The only stock rom I was able to flash was 5.1.1 but it wouldn't boot up so I had to install CM 12 again! I have no idea how to fix the phone. All I want is to return to 5.0.1 and delete any changes. The phone has no apps on it so i have nothing to loose but I do not know how to do it..
Lazarov987 said:
I actually downloaded 2 stock roms for my Note 4. One was the COG2 and the other one was the completely stock firmware. I tried flashing them but Odin failed (Auth) whatever that means. The only stock rom I was able to flash was 5.1.1 but it wouldn't boot up so I had to install CM 12 again! I have no idea how to fix the phone. All I want is to return to 5.0.1 and delete any changes. The phone has no apps on it so i have nothing to loose but I do not know how to do it..
Click to expand...
Click to collapse
You cannot use 5.0.1 ROMs on DOK2 they will never boot and no down grading. You have to use 5.1.1 ROMs for now on.
ShrekOpher said:
You cannot use 5.0.1 ROMs on DOK2 they will never boot and no down grading. You have to use 5.1.1 ROMs for now on.
Click to expand...
Click to collapse
check this out
http://forum.xda-developers.com/not...-solution-to-emmcread-write-problems-t3281179
Ashwin Prabhunerurkar said:
check this out
http://forum.xda-developers.com/not...-solution-to-emmcread-write-problems-t3281179
Click to expand...
Click to collapse
This is exactly what is happening to my T-Mobile Note 4 (SM-N910T) and the thing that you did to your Canadian Note 4 is exactly what I want to do. But can I use the firmware you provided at: http://forum.xda-developers.com/note-4/general/ref-stock-firmware-kernel-modem-recovery-t2920452
or must I use the T-Mobile ones and if I have to use the N910T firmware where can I get it so I can do what you did? A link or a thread would be amazing cause I really miss using my phone as normal!
Lazarov987 said:
This is exactly what is happening to my T-Mobile Note 4 (SM-N910T) and the thing that you did to your Canadian Note 4 is exactly what I want to do. But can I use the firmware you provided at: http://forum.xda-developers.com/note-4/general/ref-stock-firmware-kernel-modem-recovery-t2920452
or must I use the T-Mobile ones and if I have to use the N910T firmware where can I get it so I can do what you did? A link or a thread would be amazing cause I really miss using my phone as normal!
Click to expand...
Click to collapse
Don't flash Canadian tar files
We are searching for the answer
Hope to come back to you with a solution
Try Odin flash back to stock.
@dannygoround
dannygoround said:
Try Odin flash back to stock.
@dannygoround
Click to expand...
Click to collapse
Doesnt work. Wont flash the stock rom. It says Fail(Auth)
A few days ago, all the sensors all just stopped working Please help!
I tried formatting, wipe caching, safe mode and stuff
If you tried all those things you mention, I think it is time to claim warranty
NatalieRath said:
A few days ago, all the sensors all just stopped working Please help!
I tried formatting, wipe caching, safe mode and stuff
Click to expand...
Click to collapse
Have you tried reflashing stock?
sefrcoko said:
Have you tried reflashing stock?
Click to expand...
Click to collapse
Not yet, should I? I am worried about flashing knox XD
NatalieRath said:
Not yet, should I? I am worried about flashing knox XD
Click to expand...
Click to collapse
Someone else can confirm or correct me if I'm wrong, but if you've already tried everything else then I would try flashing stock firmware next. Knox isn't tripped if you download the original firmware for your device (from SamFirm, Sammobile, etc.) and flash it with Odin...just don't flash custom recovery, etc. Something may have become corrupted on your phone, in which case stock fw might fix it (unless it's a hardware issue of course).
knox wont get tripped if you dont flash a custom recovery.
so flashing stock is nit an issue.
you can always use samsung's recovery tool in smart switch app. that way you will be sure to flash the latest and correct build for your phone with out danger.
I will use smart switch instead! I actually use it quite often to back up. Thanks Bober10113!
Smart Switch doesn't support note 8 exynos
ive used it many times. both on N950F and N950N which are exynos.
put your device in download mode via power + vol down + bixby and try again
---------- Post added at 01:04 AM ---------- Previous post was at 01:03 AM ----------
NatalieRath said:
Smart Switch doesn't support note 8 exynos
Click to expand...
Click to collapse
it should be working
Okay I will try again
bober10113 said:
ive used it many times. both on N950F and N950N which are exynos.
put your device in download mode via power + vol down + bixby and try again
---------- Post added at 01:04 AM ---------- Previous post was at 01:03 AM ----------
it should be working
Click to expand...
Click to collapse
It says my Model Number / Phone does not support initializing.
My phone is having the same issues too. Sadly i dont have warranty so samsung wont do anything about it.
I have same issue, let me know if u flashed stock rom via odin/smart switch. Do you have iris scanner issue?
adelistiawan said:
I have same issue, let me know if u flashed stock rom via odin/smart switch. Do you have iris scanner issue?
Click to expand...
Click to collapse
I sent it in for warranty already. I tried everything everyone recommended
NatalieRath said:
I sent it in for warranty already. I tried everything everyone recommended
Click to expand...
Click to collapse
Are u sure that is hardware issue?
Yes it is, Warranty covers it. Something to do with the sensors all not working. It's apart of the motherboard, so they changed the entire thing...
So that means in the future if warranty ends and you still have issues with the sensor you're ****ed since you have to swap the entire motherboard out too. Jesus
But, the good thing is, when you buy legally distributed devices, you can claim warranty!
Hopefully OP tried the *#0*# hardware check first.
Sent from my SM-N950U using Tapatalk
Yeah I did. I got my phone back totally working fine now.
But yeah all the sensors before I sent for warranty was at 0. Crazy.