Help! The phone dropped to the ground once and had a crack on the digitizer and LCD screen. I replaced both of them and now, it is stuck in a boot loop (turns on, stays on splash screen) I've tried flashing the latest firmware thru Odin, but the same thing happens. All I can do on the phone is just getting to the download mode. I can't get to recovery, too.
Did you wiped cache and dalvick before reboot?
Before the first bootloop what did you do(Install an apk? Flash a zip?)? Were you rooted? A custom rom? A stock one?
During Odin did you wait for pass and blue color?
have you seen This? Is that similar for you?
Mukiai said:
Did you wiped cache and dalvick before reboot?
Before the first bootloop what did you do(Install an apk? Flash a zip?)? Were you rooted? A custom rom? A stock one?
During Odin did you wait for pass and blue color?
have you seen This? Is that similar for you?
Click to expand...
Click to collapse
Yes, I did wipe both, I didn't do anything weird except a reboot, not rooted, stock ROM, pass on Odin, not similar to the hard brick problem. I can get to download and recovery mode.
You can go now to recovery mode? Have you retry to flash a rom?
Do you remember last version before and the last you install? Couldn't it be you had try to flash an older version?
Mukiai said:
You can go now to recovery mode? Have you retry to flash a rom?
Do you remember last version before and the last you install? Couldn't it be you had try to flash an older version?
Click to expand...
Click to collapse
I'm going to flash a new one.
Acerpeng229 said:
I'm going to flash a new one.
Click to expand...
Click to collapse
Any news? Do you enjoy again your Mega? Hope that yes.
No news ?
got same problem
Mukiai said:
No news ?
Click to expand...
Click to collapse
hello fellas..this my first post here..im using samsung mega lte,and have a problem after root my phones..cant go recovery mode.couse there have a red text warranty bit kernel and 3more text avove in my screen..just stuck at samsung logo..dont know how to do..there any friend here know how to do?its been a month my phone stuckat the same problem
It seems this issue is a difference in screen compatibility. To fix this, you can turn the device on and let it boot into the Android OS, then (while still on), unplug the old LCD and plug in the new LCD. Hit the power button to ensure the new LCD is working properly, then turn the device on, and finish assembling your phone.
same issue
R960 stuck in loop after replacing screen and cant access recovery or odin mode
need help desperately
I just got a galaxy mega from someone an got ripped off because it's running 4.4 kit Kat and had the screen replaced right before I got it, so it doesn't work. Bootloops. Due to not an OEM screen and I don't really have the cash to risk ordering a screen claiming to be oem.
So how can I just downgrade to a version before the need for OEM screen??
Please any help would be greatly appreciated!!
-d.block- said:
I just got a galaxy mega from someone an got ripped off because it's running 4.4 kit Kat and had the screen replaced right before I got it, so it doesn't work. Bootloops. Due to not an OEM screen and I don't really have the cash to risk ordering a screen claiming to be oem.
So how can I just downgrade to a version before the need for OEM screen??
Please any help would be greatly appreciated!!
Click to expand...
Click to collapse
You can not in normal way (i.e flashing stock 4.2). But there is hope for you... look there:
http://forum.xda-developers.com/showthread.php?t=2608110
trurl3 said:
You can not in normal way (i.e flashing stock 4.2). But there is hope for you... look there:
http://forum.xda-developers.com/showthread.php?t=2608110
Click to expand...
Click to collapse
I'm still a bit confused as to what exactly I should do.. there's alot in that thread.. I really can't afford to buy another screen. This really sucks that the update requires OEM screen in order to function.. if I could find a way to fix the issue without buying a screen I'd be extremely grateful!
But I don't have much experience at all with rooting and flashing custom ROMs, and I'm kind of afraid to brick the phone..
Any help to get the touch screen up and running would be highly appreciated!!
Thank you!
I am the only one who only a part of upper screen works? (I can see status bar, and rotating enter to wifi settings and try to get out of welcome screen of att)
Mukiai said:
No news ?
Click to expand...
Click to collapse
OMG! Sorry for the very late reply. It works fine already. Went to download mode and flashed using Odin. Thanks!
Related
Hi All,
Hope you are well. I just flashed the CWM recovery to a locked tab using ODIN, and upon doing POWER + VOL(-) and getting into the recovery, for some reason the screen with all the menu to do wipes/install just seems to be scrolling all over the place.
When I re-flash the stock recovery back using ODIN, the screen is fine again. Tried both 4.0.0.4 and also the 3.2.0.1 versions, with not much luck.
Has anyone had a similar incident? Is there anything I can do? I wanted to try and flash my custom boot.img.
Thanks heaps in advance!!!.
Hi Folks,
Hope you are well - wasn't sure if anyone has come across this - but anyone seen the Recovery mode flickering / scrolling when flashed on a locked Galaxy Tab 10.1?
Thanks again!
I'm using CWM 4.0.0.4 on my locked P7510, works as intended.
http://forum.xda-developers.com/showthread.php?t=1171089
Thanks yqed,
For some reason when I have CWM 4.0.0.4, and when I reboot into the recovery mode - CWM shows up - but the screen keeps on flickering / scrolling / refreshing all over the place.
I'm wondering if there is something different in my Retail Galaxy Tab 10.1 WIFI vs. the others - I bought mine from Korea (retail). Appears that I have kernel version 2.6.36.3 instead of .4 and the build is EH14.
Thanks.
I to get some lag while using the cmw...
Sent from my Galaxy Tab!
+1
I have a Korean 32Gb wifi Galaxy Tab 10.1, and my CWM Recovery also starts having a seizure when I boot into it. It still seems to be working fine, but it is nearly impossible to use.
I would really like to know what causes this issue.
Thanks limenless,
Anyone seen this before? Anyone know if CWM 5 might potentially fix this - seens some thread with regards to this.
I was going to try and wipe the dalvik cache, and others, but seeing the screen is almost impossible to use in recovery mode, having a bit of difficulty there.
Any advice is much appreciated - if you need dumps and others, happy to provide - as long as I get some instructions...
Thanks.
frankus0512 said:
Thanks limenless,
Anyone seen this before? Anyone know if CWM 5 might potentially fix this - seens some thread with regards to this.
I was going to try and wipe the dalvik cache, and others, but seeing the screen is almost impossible to use in recovery mode, having a bit of difficulty there.
Any advice is much appreciated - if you need dumps and others, happy to provide - as long as I get some instructions...
Thanks.
Click to expand...
Click to collapse
Any luck bro? having same problem here..
Please help.. i realy want to root my tab 10.1
castiel19 said:
Any luck bro? having same problem here..
Please help.. i realy want to root my tab 10.1
Click to expand...
Click to collapse
Are you using the cwm5?
I'M just curious if so and you still get issues.
Sorry I can't really help.
If you can read this it was sent using my GT-P7510.
HOPING solution
frankus0512 said:
Hi All,
Hope you are well. I just flashed the CWM recovery to a locked tab using ODIN, and upon doing POWER + VOL(-) and getting into the recovery, for some reason the screen with all the menu to do wipes/install just seems to be scrolling all over the place.
When I re-flash the stock recovery back using ODIN, the screen is fine again. Tried both 4.0.0.4 and also the 3.2.0.1 versions, with not much luck.
Has anyone had a similar incident? Is there anything I can do? I wanted to try and flash my custom boot.img.
Thanks heaps in advance!!!.
Click to expand...
Click to collapse
Did you try CMW 5? Preshoot has a tutorial in the development section, its pretty simple just follow it and I think and hope that your issue would be solved!
Why dont you try taking a picture/screenshot of it, best would be using ddms.bat in the android development kit to take screenshot's , or just a picture would do great. Hard to guess what's going on, when someone mentioned seizure, I pictured Dr.House
Misledz said:
Why dont you try taking a picture/screenshot of it, best would be using ddms.bat in the android development kit to take screenshot's , or just a picture would do great. Hard to guess what's going on, when someone mentioned seizure, I pictured Dr.House
Click to expand...
Click to collapse
Thank you for showing interest to help me.. btw am also big fan of house
Let me explain my situation from the start..
i tried to flash recovery-cwm_4.0.0.4-sam-tab-10.1.tar.md5 following the instruction from the tutorial.. but after i boot into recovery the screen flash.. I will attach you tube video later..
took whole night to fix it with no success, finally decided to re-flash stock rom from firmware P7510ZSKK1_P7510ZZHKK1_TGY.. boot into stock recovery and worked fine..
as i don't want to give up and want my tab 10.1 to be rooted tried again to flash CWM5027 from preshoot.. but same screen flicker happened..
Please help me fix the problem.. or do you know other way to root my tab??
---------- Post added at 12:49 PM ---------- Previous post was at 12:40 PM ----------
castiel19 said:
Thank you for showing interest to help me.. btw am also big fan of house
Let me explain my situation from the start..
i tried to flash recovery-cwm_4.0.0.4-sam-tab-10.1.tar.md5 following the instruction from the tutorial.. but after i boot into recovery the screen flash.. I will attach you tube video later..
took whole night to fix it with no success, finally decided to re-flash stock rom from firmware P7510ZSKK1_P7510ZZHKK1_TGY.. boot into stock recovery and worked fine..
as i don't want to give up and want my tab 10.1 to be rooted tried again to flash CWM5027 from preshoot.. but same screen flicker happened..
Please help me fix the problem.. or do you know other way to root my tab??
Click to expand...
Click to collapse
how can i copy link of youtube here?? i want to show my screen flicker
Just link it here,
HTML:
[media=youtube] bracket [/media]
Where "bracket" is the ID of your video, those letters at the end. EG: FL7yD-0pqZg
Have you tried Overcome's CWM? I'm using that and it's perfectly fine. PS it's the ver 5 release.
PS; For being an epic House fan I shall see to it that you get it worked out
And to top that off, an offlink to the CWM of Overcome http://www.mediafire.com/?6c5tdmds927npdv
PS: Here's your video, Embedded anyways.
I'm on the same page. My screen flicker after entering CWM recovery mode. Very annoying.
In the development section for 10.1 I was just reading in a thread about a Korean ROM, Pershoot stated something about someones device not being compatible with his kernel. I don't know if either one has to do with the other but I think I read in the same thread of someone having "this problem"
Honestly don't know if anything between this thread and that thread are relevant to each other.
Just thought I'd mention it to see if it helps. sorry if it doesn't apply to anything here.
I somehow fixed it by flashing the tab with an non-HK 3.1 stock ROM using Odlin. then then cwm recovery works fine.
Not really a fix but
You could always just find a pre rooted rom to flash with odin, then once u have the pre rooted rom installed get rom manager and u will no longer have to worry about cwm. Plus u could then flash to whatever rom u need to using rom manager.
My method allows me to have a clear screen in CWM RECOVERY but after I flashed Galaxy Task 14 I get all blurred screen whenever my Tab is resumed from standby. I must set my screen to never turn off to prevent it flickering again.
May I ask which pre rooted ODLIN ROM do you guys recommend? If possible can you please provide the URL to it? I suspect the flickering problem has relation to the harmony between bootloader, kernel etc so I want to use the exact combination you guys are using.
Sent from my GT-I9100 using Tapatalk
Still not working
appreciate your help Misledz, 002001-Overcome_CWM_Recovery_v5.1.2.6 got same result.. my screen still flicker..
I think I will give up on CWM too complicated for me
Can you just give me tips on how to root my tab 10.1 without CWM (if that is possible)
sunnymui said:
My method allows me to have a clear screen in CWM RECOVERY but after I flashed Galaxy Task 14 I get all blurred screen whenever my Tab is resumed from standby. I must set my screen to never turn off to prevent it flickering again.
May I ask which pre rooted ODLIN ROM do you guys recommend? If possible can you please provide the URL to it? I suspect the flickering problem has relation to the harmony between bootloader, kernel etc so I want to use the exact combination you guys are using.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
What Stock Rom did you use? a, planning to download stock rom
P7510ZCLA1 ## 2012 February P7510OZHLA1 China Download
From samfirmware and flash... hope I can use CWM and instal ROM
for the past 3 hours I tried to search pre rooted ROM that can be flash using Odin with no avail
Forgive if there are similar threads about this topic.
I suffered from scrolling cwm so i tried this fix: http://forum.xda-developers.com/showpost.php?p=27830023&postcount=41
It worked excellent but when i lock my screen and unlock it again it starts flickering like shown in this video: http://youtu.be/P6fMxjFdpJE
I have tried to do factory resets both from recovery and flash an original firmware. Nothing works.
Is it possible to get this fixed or am i screwed?
Hi!
I've the same trouble like you!
Try this http://forum.xda-developers.com/showthread.php?t=1680738
For me it works well both the CWM recovery that hc 3.2 (no more flickering!)
brusarp said:
Hi!
I've the same trouble like you!
Try this http://forum.xda-developers.com/showthread.php?t=1680738
For me it works well both the CWM recovery that hc 3.2 (no more flickering!)
Click to expand...
Click to collapse
I just wanted to say the same. Flash the kernel from pershoot website, it should fix it.
brusarp said:
Hi!
I've the same trouble like you!
Try this http://forum.xda-developers.com/showthread.php?t=1680738
For me it works well both the CWM recovery that hc 3.2 (no more flickering!)
Click to expand...
Click to collapse
isimobile said:
I just wanted to say the same. Flash the kernel from pershoot website, it should fix it.
Click to expand...
Click to collapse
Thank you very much. I will try this when i get home from work.
It doesn´t work for me.
But I dont use 3G anyway so can I just go with P7510 firmware which works?
nicktaken said:
It doesn´t work for me.
But I dont use 3G anyway so can I just go with P7510 firmware which works?
Click to expand...
Click to collapse
Oh... i don't know that... mine is P7500... and works well both CWM and HC3.2 (with 3G and wifi connection)
brusarp said:
Oh... i don't know that... mine is P7500... and works well both CWM and HC3.2 (with 3G and wifi connection)
Click to expand...
Click to collapse
Alright I got it to work! I didn´t get it that I should flash the kernel in cwm so I flashed it in Samsungs recovery
nicktaken said:
Alright I got it to work! I didn´t get it that I should flash the kernel in cwm so I flashed it in Samsungs recovery
Click to expand...
Click to collapse
:highfive: :good:
brusarp said:
Hi!
I've the same trouble like you!
Try this http://forum.xda-developers.com/showthread.php?t=1680738
For me it works well both the CWM recovery that hc 3.2 (no more flickering!)
Click to expand...
Click to collapse
Got the same issue today after installing Task's ROM. The fix worked for me.. Thanks man.. :good:
nicktaken said:
Forgive if there are similar threads about this topic.
I suffered from scrolling cwm so i tried this fix: http://forum.xda-developers.com/showpost.php?p=27830023&postcount=41
It worked excellent but when i lock my screen and unlock it again it starts flickering like shown in this video: http://youtu.be/P6fMxjFdpJE
I have tried to do factory resets both from recovery and flash an original firmware. Nothing works.
Is it possible to get this fixed or am i screwed?
Click to expand...
Click to collapse
When you tried the fix noted above, I assume the screen didn't roll when you rebooted then into CWM recovery. At that point did you flash a ROM and THEN reboot to find the flicker after locking the screen, or did you do a reboot back into the same stock HC after flashing the bootloader and experience the problem?
I'm contemplating flashing this same bootloader because I have a rolling CWM5.5.0.4 right now and I want to stabilize it - but just so that I can root...not thinking about a ROM just yet...
Just to inform you all, i also had to flash a different bootloader after installing cm9 on my p7511, wich is in fact a 7510. For the records, pershoot made the new bootloader for exactly that issue, not backwards. But seems to work also.
What i deal now with, is that after flashing the uk ics for p7510 to my tab, the stock recovery doesn't recognize my sdcard. Can't mount sdcard...
Could be that a repartitioning with pit file will be necessary afterwards for us all.
Edit: thanks to the wise help of msedek, i know by now that my hind was totaly wrong. My mentioned point has to do with the Changes within stock recovery of ics, which have been made to prevent changes from there.
Getting more confident..
OK so it is sounding like this is definitely better. One more question:
I'm following the stickied root guide in General and that method uses CWM 4.0.0.4...I had reflashed that version. If I want to flash this boot loader should I flash 5.5.0.4 first? Or does it matter if I'm just trying to root right now?
EDIT: Flashed the bootloader which straightened out the recovery!! Successfully rooted after that. Downloaded root apps (ROM manager/Titanium/etc). Then turned off my screen - FLICKER CITY!
http://forum.xda-developers.com/showthread.php?t=1680738 <<< THIS fixed it. Load this kernel into the root of your tablet and flash it with CWM. Seems to have done the trick nicely and I'm exploring my newly rooted tab! My wife no longer wants to kill me either.
brusarp said:
Hi!
I've the same trouble like you!
Try this http://forum.xda-developers.com/showthread.php?t=1680738
For me it works well both the CWM recovery that hc 3.2 (no more flickering!)
Click to expand...
Click to collapse
This method don't work with new ICS firmware. I need a new kernel to work with new ICS firmware . I like the new firmware but i stuck with flickerscreen issue. Can sum 1 help ? Thanks.
I have the same Problem here.
Nothing is working for me, i have tried 2 diferent kernels and still flickering screen after tourning the screen off and on.
Please can anyone help me?
KeyF said:
I have the same Problem here.
Nothing is working for me, i have tried 2 diferent kernels and still flickering screen after tourning the screen off and on.
Please can anyone help me?
Click to expand...
Click to collapse
What ROM or firmware are you running? What exactly have you done with the device up to this point? Are you 3G or WiFi? Need more detail...
Flicker screen after screen lock\timeout
djmatt604 said:
What ROM or firmware are you running? What exactly have you done with the device up to this point? Are you 3G or WiFi? Need more detail...
Click to expand...
Click to collapse
I have the same problem on my P7500 3G and the minute i load the bootloader to fix CWM recovery rolling i get the screen flickering after lock screen.
Rom: ICS 4.0.4
Build Number: IMM76D.XXLQ8
BaseBand7500XXlQ8
Kernel: 3.1.10
Still stuck.
Hi guys,
Gtab 10.1 Wifi here. Fix didn't worked, somehow...
After installing official ics from Samsung and rooted, i had the same insane flicker issue. I followed this thread - http://forum.xda-developers.com/showthread.php?t=1680738 - , flashed new kernel, and now i cant pass Samsung Galaxy Tab logo for some reason, not even past half an hour.
Im in a dead end, even tried installing back CM9 but it also wont pass the splashing blue screen.
Any ideas?
cheers!
EDIT : After some reboots, finally managed to boot into ICS (CM9) but now i was pushed back to the step 1, where I don't have a working camera, but I have root access and non official ICS from Cyanogen. I am afraid re-doing all my work and get stuck again in the scrambled screen after it updates the kernel..
I'm I missing something, guys?
Hi there!
Are you still having problems?does this guide here work for you?:
http://forum.xda-developers.com/showthread.php?t=1555984
I've found something,the kernel flash package changes our devices' WiFi driver,that's why it doesn't work.
sorry for not giving a fix until tomorrow,it's sleep time here,I know my excuse will be accepted because you all care for basic human needs...
But please inform me if that guide(Pershoot's) has fixed your problem,thanks for that
brusarp said:
Hi!
I've the same trouble like you!
Try this http://forum.xda-developers.com/showthread.php?t=1680738
For me it works well both the CWM recovery that hc 3.2 (no more flickering!)
Click to expand...
Click to collapse
No it does not work for me.
I have a GT-P7500 with ICS with Build # IMM76D.XWLP6
Please direct me to the correct forum.
thanX
reXbeer said:
No it does not work for me.
I have a GT-P7500 with ICS with Build # IMM76D.XWLP6
Please direct me to the correct forum.
thanX
Click to expand...
Click to collapse
Hey guys i solve my problem today i desided to solve it anyway and now i am free from this **** ....
i just go to http://droidbasement.com/galaxy/roms/cm10/p4/ and download
bootloader.tar.md5
latest recovery.tar.md5
cm-10-20121112-EXPERIMENTAL-p4.zip
but before start anything first i format my tab memory then restart in download mode install bootloader.tar.md5 and recovery.tar.md5 ... volla ... reboot in recovery mode volla thats it all is now working perfect .... then i install cm-10-20121112-EXPERIMENTAL-p4.zip now my tab is free on madness ...
must try but first fully clean your tab ...
iff its really work then click on thanks button ...
i was running two roms with dual boot. first was a supernexus jb rom and other mystic glory. i had some hicups with supernexus so i flashed a dream kernel over it. for the first time it booted upto dream logo (even asked for loading 2nd rom) and then went black; phone turned off. second time happened the same thing. then i tried to go to cwm recovery mode, but no luck. so booted with mystic glory rom and from the restart menu tried to go to cwm recovery. the phone turned off and now the phone wont boot beyond samsung galaxy s2 logo.
i searched through this forum and couldnt find any solution.
any help would be greatly appreciated. pls provide any links to any threads if you want me to download something.
Thanks
poooolbachhan said:
i was running two roms with dual boot. first was a supernexus jb rom and other mystic glory. i had some hicups with supernexus so i flashed a dream kernel over it. for the first time it booted upto dream logo (even asked for loading 2nd rom) and then went black; phone turned off. second time happened the same thing. then i tried to go to cwm recovery mode, but no luck. so booted with mystic glory rom and from the restart menu tried to go to cwm recovery. the phone turned off and now the phone wont boot beyond samsung galaxy s2 logo.
i searched through this forum and couldnt find any solution.
any help would be greatly appreciated. pls provide any links to any threads if you want me to download something.
Thanks
Click to expand...
Click to collapse
Dual booting has always been unstable and the only way out is to start from scratch. I would not advice dual booting unless you are able to spend time redoing it.
zelendel said:
Dual booting has always been unstable and the only way out is to start from scratch. I would not advice dual booting unless you are able to spend time redoing it.
Click to expand...
Click to collapse
thks mate for the reply.........any suggestions to get out of this mess.....
poooolbachhan said:
thks mate for the reply.........any suggestions to get out of this mess.....
Click to expand...
Click to collapse
Did u use the rom manager app?
Go to the development section and check out the stickies for going back to stock. That should be your first step.
Sent from my SGH-I777 using xda premium
Phalanx7621 said:
Did u use the rom manager app?
Click to expand...
Click to collapse
i m not sure wt u r suggesting.............but it was on my phone.......and now i cant get anyplace except for download mode using usb cable......
Red_81 said:
Go to the development section and check out the stickies for going back to stock. That should be your first step.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
i have tried going back to stock........odin runs completely and passes.......phones starts reboot......once past samsung logo, it shows cwm recovery pic for a sec from previous flash (which is wierd, since the phone must be back to stock)..........and goes black.......still able to go to download mode.......
i have also tried bootloader i777uckh7sbl.tar from one the posts here.........still no luck....
i think i have seriously messed up the phone........but since i can manage to get to download mode, its not a hard brick????
poooolbachhan said:
i have tried going back to stock........odin runs completely and passes.......phones starts reboot......once past samsung logo, it shows cwm recovery pic for a sec from previous flash (which is wierd, since the phone must be back to stock)..........and goes black.......still able to go to download mode.......
i have also tried bootloader i777uckh7sbl.tar from one the posts here.........still no luck....
i think i have seriously messed up the phone........but since i can manage to get to download mode, its not a hard brick????
Click to expand...
Click to collapse
The only think that can hardbrick was that bootloader you flashed... Don't do that when it's completely unnecessary.
korockinout13 said:
The only think that can hardbrick was that bootloader you flashed... Don't do that when it's completely unnecessary.
Click to expand...
Click to collapse
does that mean my phone is hardbricked........if not pls show me a way...........still can get into download mode...........
poooolbachhan said:
does that mean my phone is hardbricked........if not pls show me a way...........still can get into download mode...........
Click to expand...
Click to collapse
Brick means no sign of life. Stop using that word.
122ninjas said:
Brick means no sign of life. Stop using that word.
Click to expand...
Click to collapse
thanks mate........that is a gre8 relief .........any suggestions to get me out of this mess?........i could have get the jtag done on it but i live in India and shipping the phone to mobiletechvideos and getting it fixed will cost me nearly a brand new phone..........since it is US version of s2, i cant get it fixed in India through samsung........
i need some definitive actions.....because everything i have been doing until now through research made it worse.......only life signs its showing right now is getting in to download mode with a pc connection......also smetimes i see a flicker in the bottom four keys......pls help
poooolbachhan said:
thanks mate........that is a gre8 relief .........any suggestions to get me out of this mess?........i could have get the jtag done on it but i live in India and shipping the phone to mobiletechvideos and getting it fixed will cost me nearly a brand new phone..........since it is US version of s2, i cant get it fixed in India through samsung........
i need some definitive actions.....because everything i have been doing until now through research made it worse.......only life signs its showing right now is getting in to download mode with a pc connection......also smetimes i see a flicker in the bottom four keys......pls help
Click to expand...
Click to collapse
I suggest you continue trying to get to stock. Use a different stock package than the one that didn't work.
Sent from my SGH-I777 using xda premium
Hey guys, basically, i'm new-ish to flashing, but i was able to do it following all instructions. Yesterday i installed an s5 theme from this site that caused my phone to have problems such as the wifi not working. I was reading that flashing a custom kernel might help, it didn't.
So i woke up, entered my TWRP custom recovery and stupidly factory wiped everything, now my phone wont get past the 'Samsung galaxy s III' screen, it just stays there. I have no idea what to do, i'm dumb enough not to make a recovery file before i started all this so i've ****ed up there.
If anyone can help me get my phone back i'll be extremely happy, i just want it working again! I have work in a few hours and really hope to fix it before then! Any help is appreciated.
Download a stock rom from sammobile.com and flash it the way you flashed TWRP.
adamldn said:
Hey guys, basically, i'm new-ish to flashing, but i was able to do it following all instructions. Yesterday i installed an s5 theme from this site that caused my phone to have problems such as the wifi not working. I was reading that flashing a custom kernel might help, it didn't.
So i woke up, entered my TWRP custom recovery and stupidly factory wiped everything, now my phone wont get past the 'Samsung galaxy s III' screen, it just stays there. I have no idea what to do, i'm dumb enough not to make a recovery file before i started all this so i've ****ed up there.
If anyone can help me get my phone back i'll be extremely happy, i just want it working again! I have work in a few hours and really hope to fix it before then! Any help is appreciated.
Click to expand...
Click to collapse
It sounds like you might need to flash a ROM before it will boot. Your contacts, texts etc are gone if you wiped /data though.
thefunnyone said:
Download a stock rom from sammobile.com and flash it the way you flashed TWRP.
Click to expand...
Click to collapse
Appreciate the help guys, i thought as much, i just downloaded 'http://forum.xda-developers.com/galaxy-s3/development-i9305/stock-rom-4-4-4-gt-i9305n-i9305nxxufni4-t2886807/page10' as i was typing this and am installing it now. Lets see what happens?
EDIT- IT WORKED! PHONES BACK!!!
adamldn said:
Appreciate the help guys, i thought as much, i just downloaded 'http://forum.xda-developers.com/galaxy-s3/development-i9305/stock-rom-4-4-4-gt-i9305n-i9305nxxufni4-t2886807/page10' as i was typing this and am installing it now. Lets see what happens?
Click to expand...
Click to collapse
Wait stop, what kind of s3 do you have?
ArkThompson said:
Wait stop, what kind of s3 do you have?
Click to expand...
Click to collapse
GT-I9305, LTE version.
adamldn said:
GT-I9305, LTE version.
Click to expand...
Click to collapse
Ah ok, it's good that it worked. I was just worried since you posted this on the i9300 forum and said you were flashing an i9305 ROM.
A good day to all!
I have had an issue with my S6 edge (SM-G925F, Philippines Globe Carrier Version) for months now wherein it keeps restarting/crashing. The problem persists so randomly, sometimes multiple times a day or sometimes a day or two without it. I've already tried everything I could find in the internet, such as; deleting the cache in recovery, factory wiping the phone, and flashing the newest firmware i found for it on sammobile. Noting seemed to work. This is my last attempt in fixing the phone before I give up. I hope someone can give me good advice about this.
So nobody knows how to fix this? I don't care if it's a hardware problem i just wanna know
yh man,same problem...i cant even boot to the system..is your led flashing blue?
buzzsaw345 said:
So nobody knows how to fix this? I don't care if it's a hardware problem i just wanna know
Click to expand...
Click to collapse
Is the phone currently working?
It sounds like it could be the hardware failing, could be the emmc failing.
The only thing to suggest at this point is to wipe data/cache in recovery and flash a new firmware.
Or try a custom ROM. If it happens on the custom ROM also then it's possibly hardware.
pexluka said:
yh man,same problem...i cant even boot to the system..is your led flashing blue?
Click to expand...
Click to collapse
Mine can actually boot to the system but it always crashes after some time of use.
callumbr1 said:
Is the phone currently working?
It sounds like it could be the hardware failing, could be the emmc failing.
The only thing to suggest at this point is to wipe data/cache in recovery and flash a new firmware.
Or try a custom ROM. If it happens on the custom ROM also then it's possibly hardware.
Click to expand...
Click to collapse
That's EXACTLY what i was thinking although i did not know that was the name of the part. I was just thinking the memory module was maybe defective already. Dang it so the logic board should be replaced right? Because as far as I know the memory is soldered to the board and hard to remove by itself let alone replacing it.
I've already tried the wiping of data/cache and flashed the newest firmware using Odin but the problem still persists.
Also tried the custom ROM and I've tried a lot of them non actually boots to the system. Only flashing the official firmware allows me to boot to the system.
Thank you for the reply I will now just give up on this and just buy a OnePlus 3T.
buzzsaw345 said:
That's EXACTLY what i was thinking although i did not know that was the name of the part. I was just thinking the memory module was maybe defective already. Dang it so the logic board should be replaced right? Because as far as I know the memory is soldered to the board and hard to remove by itself let alone replacing it.
I've already tried the wiping of data/cache and flashed the newest firmware using Odin but the problem still persists.
Also tried the custom ROM and I've tried a lot of them non actually boots to the system. Only flashing the official firmware allows me to boot to the system.
Thank you for the reply I will now just give up on this and just buy a OnePlus 3T.
Click to expand...
Click to collapse
If it's the emmc then only way to fix is to replace the full motherboard, which isn't cheap.
It's a known problem on note 4. Emmc chip fails and eventually completely packs in.
Which custom Roms did you try? Carhd rom is a good one to try very reliable. Also when flashing a custom ROM it can take 20-30 minutes to boot into the system.
callumbr1 said:
If it's the emmc then only way to fix is to replace the full motherboard, which isn't cheap.
It's a known problem on note 4. Emmc chip fails and eventually completely packs in.
Which custom Roms did you try? Carhd rom is a good one to try very reliable. Also when flashing a custom ROM it can take 20-30 minutes to boot into the system.
Click to expand...
Click to collapse
True they are very expensive that's why I'd rather just buy a new phone. I just didn't want to give up such good hardware until I've tried everything.
Oh really? I wonder why that's the case
I actually forgot which ones already but I'm sure I tried Carhd and it didn't boot for more than an hour. But I'll go and check again just to be thorough.
buzzsaw345 said:
True they are very expensive that's why I'd rather just buy a new phone. I just didn't want to give up such good hardware until I've tried everything.
Oh really? I wonder why that's the case
I actually forgot which ones already but I'm sure I tried Carhd and it didn't boot for more than an hour. But I'll go and check again just to be thorough.
Click to expand...
Click to collapse
Yeah it's a shame really. I could be wrong that might not occur on yours. Normally when you get emmc failure, the phone will reboot to download mode and give you an error along the lines of emmc Write fail. And then keep repeating this.
3T is a good choice to go for if that's what you decide
callumbr1 said:
Yeah it's a shame really. I could be wrong that might not occur on yours. Normally when you get emmc failure, the phone will reboot to download mode and give you an error along the lines of emmc Write fail. And then keep repeating this.
3T is a good choice to go for if that's what you decide
Click to expand...
Click to collapse
It's alright I feel like whatever the hardware issue is it'll require the motherboard to be swapped out anyways. I can finally let the phone rest in peace haha thank you very much.
Yeah it's perfect for an android enthusiast. Already ordered one. Good bye and thanks again!
buzzsaw345 said:
It's alright I feel like whatever the hardware issue is it'll require the motherboard to be swapped out anyways. I can finally let the phone rest in peace haha thank you very much.
Yeah it's perfect for an android enthusiast. Already ordered one. Good bye and thanks again!
Click to expand...
Click to collapse
No problem buddy enjoy your one plus 3
thanks guys,i get the same problem,no rom wants to boot,i can install twrp and custom roms ut cant boot the rom..i once managed to oot to i think it was custom rom,but apps still kept crashing and i couldnt finish the welcoming screen
i got it with android m and apps were crashing all the time,and phone was restarting..
so motheroard it is?
pexluka said:
thanks guys,i get the same problem,no rom wants to boot,i can install twrp and custom roms ut cant boot the rom..i once managed to oot to i think it was custom rom,but apps still kept crashing and i couldnt finish the welcoming screen
i got it with android m and apps were crashing all the time,and phone was restarting..
so motheroard it is?
Click to expand...
Click to collapse
Wouldn't say it was motherboard yet. After you flash your rom you need to boot to recovery and wipe data/cache. This will fix the apps crashing
done,cant boot the system.
gave a visit to a few services,they sad around 50e would be reparation,but im student and now dont have cash for that ****..you have any other suggestions? i tried custom roms,at first magisk would always faild,last time it was ok but still couldnt boot
pexluka said:
done,cant boot the system.
gave a visit to a few services,they sad around 50e would be reparation,but im student and now dont have cash for that ****..you have any other suggestions? i tried custom roms,at first magisk would always faild,last time it was ok but still couldnt boot
Click to expand...
Click to collapse
Do not pay for it. Chances are if you can't fix it they can't either.
So have you tried flashing stock firmware?
What Android version do you have and what region? What's full model number g925?
Reduce the cpu frequencies to 1200-800mhz for big and little and userspace governor. This the only fix.
ok,so one more thing,on the glass back of the phone sits one imei that is not correct,and on the battery is another,which reports 64g version,while next to that number is printed 32gb and phone actually has 32gb lool
it is supposed to be g925f,but after i installed some custom rom,pc showed it as g925s? i think it is due to rom signing the wrong model number
the last thing i have done was yesterday,and it was flashing firmware through kies again.
and this is what i get :
s6 edge powered by android,followed by blue screen 'installing system update',and then recovery
in the recovery,i get this :
android recovery
samsung/zeroltexx/zerolte
7.0/NRD90M/G925FXXU5EQBG
user/release-keys
*recovery options*
No suppoer SINGLE-SKU
Supported API: 3
dm-verity error...
i realy dont know what else to try,and i am open to all suggestions..i have read that emmc storage is broken so this kind of problems can occur,so maybe service would do that?
thank you,i know this is confusing and boring problem
i tried with odin once more,and it failed at 25% instaing system update,then i restarted it and it got up to 32% and started erasing and it turned off..tf with this phone?? i guess its broken...
pexluka said:
i tried with odin once more,and it failed at 25% instaing system update,then i restarted it and it got up to 32% and started erasing and it turned off..tf with this phone?? i guess its broken...
Click to expand...
Click to collapse
https://www.sammobile.com/firmwares/galaxy-s6-edge/SM-G925F/VOD/download/G925FXXU5EQBG/125195/
Download and flash that firmwsre through odin before you try anything else. Let me know what happens.
I can tell you it's likely not emmc failure. For this you would get random reboots and it would reboot to download mode. There you would have an error emmc_write_error.
wowo thanks,i just gave up on that phone,i will try again,i will report back!
just one question,why vodafone?
oh,and i did have random reboots on android m,but it would reboot to optimizing android and boot