[Q] SGH-I527M flashing issues - Samsung Galaxy Mega

Hi all, long time browser of XDA, first time poster. Up until now, every phone I've had, I've found the answers on this forum. I recently picked up a Samsung Galaxy Mega (SGH-I527M) which was non functional due to what I believe was an interrupted OTA update. When I first turned it on it said ']image size too large!! w:1080 h:1920 display image fail secure fail: kernel' I downloaded stock 4.4.2 from the sammobile website, and flashed it through odin, this got rid of the message, but sent the phone into a bootloop, I couldnt enter recovery, couldn't boot, just download mode. I then tried to use the Kies software to recover it, which brought back the image size error again. Anything stock i try to flash from sammobile results in a bootloop, the only rom that boots is a pre rooted stock 4.2.2. However, with this rom I have no wifi, bluetooth, sound, or USB. In an attempt to fix this I flashed the modem file from a 4.4.2 pre rooted stock rom. This returned my sound and bluetooth, but i still cant enable wifi, and no computer ive tried can connect to the phone via usb. As of now, I still have no wifi or usb. The hardware is completely fine, according to the previous owner, it worked right up until the failed flash. I've been trying to figure this out for 2 days straight now, and I'm at a loss. Does anybody have any ideas what might be causing this? I very much appreciate any help with this situation

Hi..try flashing this rooted rom by @krazykipa with odin 3.09 and it is a 4.4.2 kitkat rom NE5 ..download the rom with the link that is at the bottom of that post.
Link: http://forum.xda-developers.com/showthread.php?p=56268871
Sent from my SGH-I527M using XDA Free mobile app

Thank you for your reply. I had already tried the ROM from that thread to no avail. However, I did manage to restore this phone to working order. It turns out that all of my issues stemmed from an aftermarket screen replacement. Upon searching various forums, I cam! e across one that said to unplug the screen, boot the phone, and plug it back in once the screen would have normally timed out. Lo and behold, the LED turned blue and it didnt bootloop. Upon plugging the screen back in I was presented with my lockscreen, with no touch response. That confirmed my suspicions of an aftermarket screen. Browsing the web with new leads, I came across a video explaining how to fix, flashed megafire v16 as suggested, and the phone lives again! Seems samsung doesnt like when they cant take you for more money on OEM parts
Thanks again for the reply, and may I say just how lost I'd be without XDA?

Related

[Q] YABSGP - Another bricked SGP 5.0

It seems that I have bricked my SGP 5.0 (US). It started with a bootloop problem, and after trying various methods discovered in the forums, I am now left with a SGP that refuses to show anything other than the yellow "Downloading" screen.
I've tried flashing it with Eryigit's ROM (as well as a supposedly stock ROM) using Odin. I get a PASS from Odin, but when it resets it just goes back to the download screen.
I've found similar threads, but so far they either 1) haven't worked or 2) have broken links for one or more of the files to be downloaded. If I'm missing one that would fix my situation, please point me in the right direction.
Is there anything I can do to make my player usable again?
Problem fixed!
Apparently I needed to reflash the bootloader, and it booted into recovery mode. After that, I chose the wipe/factory reset, rebooted, and voila!
Even though no one responded to this thread, thanks to all those who posted before, as I wouldn't have been able to revive it without those posts. (I'll thank your posts when I have a chance--busy setting up my SGP at the moment. )
U need flash "low" firmware, try this : http://narod.ru/disk/39324223001/CODE_G70XEKP2_CL642455_REV01_user_low_ship_HOME.tar.md5.html

[Q] Samsung Galaxy Tab 10.1 Verizon LTE (sch-i905) bricked, no recovery

Verizon Galaxy Tab 10.1 4G LTE (sch-i905)
So I got this tablet from a friend who said it was bricked, said I could have it if I got it working. So I plug it in and it turns on no problem, strange. wiped tablet and added a couple apps. Got busy at work and the tablet drain power. That's when I got to see it bricked, but still not sure why it booted for a bit for me.
Symptoms:
Boots to Samsung Galaxy Tab 10.1 splash screen (not the animated one after), sits there for ever.
Boots to Odin update mode
When booting to recovery I get a blank, back lit screen and nothing ever.
I've tried:
-Pushing clockwork mode to fix recovery
-I've had a hell of a time finding stock firmware for some reason (it isn't on sammobile), but I did find one eventually. I pushed it to the tablet via Odin, and it was successful, but rebooted to blank black back-lit screen. Have to hard boot and hold power buttun until I see the splash screen to get that far. I followed the guide on rootzwiki reposted on icsforums - www icsforums com/forum/showthread / 13525 (sorry new member can't post links)
-Followed another guide that involved draining battery completely, no go.
I don't care what firmware I end up on, or if I can use LTE (I won't anyway)
I'm a network engineer so I'm tech savy, but not heavy on Android OS. I'm looking for anything else I can try. I saw another method involving heimdall suite, but can't find the files for my model.
Any help or guidance is greatly appreciated.
@Juicebox4242
I had this problem on my gt-p7510...
What I ended up doing was wiping my sdcard..I must have had something corrupt in my file system or a kernel issue( still not sure which )..
Since you have no recovery..I think you can use odin to repartition ( I CAN NOT STRESS ENOUGH THAT THIS IS JUST A GUESS )..I have not tried it..but i will search after this post to confirm..I also believe there is a way using ADB..again not sure..
I just wanted to post this so you would know somebody was looking and to maybe give you a couple ideas to follow up on...I'll search around and see what I find
Edit...I believe ADB will only work with usb debugging checked...But you can flash a stock rom in odin with re-partition checked..you need a .pit file....I think...
Edit...Here is a link to a stock rom thread for you're device..It seems to have helped a couple people with their soft-bricked devices..just follow directions in OP..no repartition checked. I cant even find a .pit file to do a re-partition with for you're device..
http://forum.xda-developers.com/showthread.php?t=1342995 Let me know if this works for you..
Thanks for the post!! Really appreciate it.
That firmware is the one I found in the end and tried. Odin pushes it ok, but then still doesn't boot. In fact after pushing that firmware it boots to backlit blank screen, but when hard reset boots to splash screen.
I tried a pit file I found that I thought was the right one, but it failed when I used that so it must have been wrong.
Juicebox4242 said:
Thanks for the post!! Really appreciate it.
That firmware is the one I found in the end and tried. Odin pushes it ok, but then still doesn't boot. In fact after pushing that firmware it boots to backlit blank screen, but when hard reset boots to splash screen.
I tried a pit file I found that I thought was the right one, but it failed when I used that so it must have been wrong.
Click to expand...
Click to collapse
I have the exact same problem as you, except sometimes I can't my tablet to boot. I know it is a software problem because before I was messing with recovery yesterday, everything was working just fine. All I wanted to do was restore to factory settings and instead ended up bricking the device... If you find / know the answer, please do share.
Juicebox4242 said:
Verizon Galaxy Tab 10.1 4G LTE (sch-i905)
So I got this tablet from a friend who said it was bricked, said I could have it if I got it working. So I plug it in and it turns on no problem, strange. wiped tablet and added a couple apps. Got busy at work and the tablet drain power. That's when I got to see it bricked, but still not sure why it booted for a bit for me.
Symptoms:
Boots to Samsung Galaxy Tab 10.1 splash screen (not the animated one after), sits there for ever.
Boots to Odin update mode
When booting to recovery I get a blank, back lit screen and nothing ever.
I've tried:
-Pushing clockwork mode to fix recovery
-I've had a hell of a time finding stock firmware for some reason (it isn't on sammobile), but I did find one eventually. I pushed it to the tablet via Odin, and it was successful, but rebooted to blank black back-lit screen. Have to hard boot and hold power buttun until I see the splash screen to get that far. I followed the guide on rootzwiki reposted on icsforums - www icsforums com/forum/showthread / 13525 (sorry new member can't post links)
-Followed another guide that involved draining battery completely, no go.
I don't care what firmware I end up on, or if I can use LTE (I won't anyway)
I'm a network engineer so I'm tech savy, but not heavy on Android OS. I'm looking for anything else I can try. I saw another method involving heimdall suite, but can't find the files for my model.
Any help or guidance is greatly appreciated.
Click to expand...
Click to collapse
Did you ever get this fixed? I've had the same problem for months. I just gave up and put it away. I recently fixed a Galaxy Tab 2 and now I want to see if anyone else was able to fix this i905 not booting issue.
did anyone know the solution of this question

GT-I8160 stuck in startsplash

Hi,
the long story:
bought a used Samsung GT-I8160 (Galaxy Ace II) on Tuesday. It is without simlock and not branded. Originally it had Gingergread installed. I tried my SIM and after some fundling it in the slot it finally worked, I got connection, could recieve and send messages and use the Internet via the browser.
After that I tried to get it rooted via Odin v3.07, I8160XXLL2_CWM_5.0.2.6_ANT.tar.zip and UPDATE-SuperSU-1.65.zip wich worked. So I went on and tried CM 10.1 and 10.2 and Vanilla RootBox Build 4m which all worked extremely well. Just a single glitch: I could not get it to recognize my SIM any more. Even with holding it in place for better connection to the contacts to the chip. Remembering, that it once worked I thougt to flash the stock rom (via sammobile.com) back on and tried I8160XXLL2_I8160ATOMA1_ATO.zip which succeeded in Odin but brought me to my final problem.
The Problem:
Right now while booting or booting to recovery it gets stuck on the first screen, which is a Samsung Startsplash or a black screen or a frozen loading circle. Therefore I can not enter any codes or wipe any data through recovery.
I can start the phone in Odin Mode and flash custom roms, stock roms, kernels and whatever, what gets a succeed and a PASS! in Odin, but changes nothing for re-booting while flashing or booting manually into the other modes.
Searching the Internet I have not found a solution and even the problem seems to be rare. As last resort I tried to flash the GT-I8160_EUR_XX_4G.pit as mentioned in one post while Re-Partition through Odin, what did not change a thing. I guess I did something awefully wrong on the way but would like to get it undone. If there is no solution to do it myself I will have to go to a store next week.
Thanks for reading.
PS: Same Posting goes to the Forum on sammobile.com
I had the same problem and I found a solution here: (3w)taringa.net/comunidades/galaxyace/6526325/Aporte-Desbrickear-Samsung-Galaxy-Ace-S5830-M.html

[Q] Cellphone is looping at splash screen after kernel update

Hi everyone,
First of all, thanks for all the help/development done here, it is really awesome. I am new to rooting/rom so, I've spent a lot of time reading forum threads and looking at people's issues and it's been really helpful.
Yesterday, I spent all day trying to update my Bell Mobility Samsung Galaxy S Vibrant GT-I9000M from Froyo 2.2 to 4.2+
I sucessfully rooted the device, installed SpeedMod kernel(with Odin 3.04) and got CWM Recovery working when I restart the cellphone.
Afterward, I tried to update with different ROM(CyanFox, CM11, Mackay OmniROM...) but always got Status 7 error at CWM. So I figured I'd try to upate to a recent Kernel and installed GearKernel_JBPlus_Vibrant_1.0.3v.tar trought Odin. The phone got in an installation loop. Here is a poor webcam photo of the error(sry couldn't get better) : http://i.imgur.com/L3b0RmF.png. It says something like Estimating(?) volume for path [grep], Can't mount grep, Installation Aborted. Restart, splash screen, installation aborted, loop.
I had this loop at other occasions trying to update Kernel. The solution had been to put the cellphone in Download mode and reinstall Speedmod Kernel with Odin. This is what I did again.
It allowed me to get in Recovery mode but I couldn't go passed it. Attempt at restoring backup didn't worked. So I decided I'd go back to everything stock and followed this thread http://forum.xda-developers.com/showthread.php?t=1047087 and used Odin with the PIT and TAR files.
This got me in my worst position so far. If the cellphone is plugged, it loops between dark screen and the little "loading thingy" before the battery, but nothing more, no battery charge. If I try to open it without the plug, it display the GALAXY S GT-I9000 splash screen(which is weird cause I'm using I9000m) for a couple second then goes dark.. Then splash screen.. then dark... pretty quickly.
I can go in Download mode but I haven't succeeded to get in Recovery mode. I have adb on my computer but I haven't been able to call anything from it at the point I am.
I have found different threads showing different solution for various problems but I feel like I tried enough and I'd like to avoid bricking my cellphone so I decided I'd make my own post detailing the steps I took.
What should be my next step to get out of this loop? It seems like I only have Odin/Download mode to help me.
Thanks again.
If you have the gt-i9000m that is not the vibrant. The vibrant is the sgh-t959. Thats probably your problem
Sent from my Nexus 4 using xda app-developers app

Need assistance with Odin Soft or Hard Brick?

Hey guys,
I flashed Cyanide L on Friday morning with a clean install etc.. and my phone seems to have bricked itself while on the charger from Friday night into Saturday morning. I used it most of the day Friday and it seemed fine other than 1 random reboot. My phone will not boot past the Galaxy Note II screen when the phone first turns on, I can boot into recovery (Philz) but I don't see anything on the screen when I do (I get haptic feedback when I touch anywhere on the screen but I can't do anything.)
I tried for about 5 hours to use Odin in download mode and return to either 4.1.1 stock or 4.1.2 (I know using Odin to restore 4.3 will lock my bootloader which I am not interested in doing). However, Odin keeps failing when trying to write the recovery image to the phone. Does anyone have any tips or suggestions for what I could do next?
ozo012 said:
Hey guys,
I flashed Cyanide L on Friday morning with a clean install etc.. and my phone seems to have bricked itself while on the charger from Friday night into Saturday morning. I used it most of the day Friday and it seemed fine other than 1 random reboot. My phone will not boot past the Galaxy Note II screen when the phone first turns on, I can boot into recovery (Philz) but I don't see anything on the screen when I do (I get haptic feedback when I touch anywhere on the screen but I can't do anything.)
I tried for about 5 hours to use Odin in download mode and return to either 4.1.1 stock or 4.1.2 (I know using Odin to restore 4.3 will lock my bootloader which I am not interested in doing). However, Odin keeps failing when trying to write the recovery image to the phone. Does anyone have any tips or suggestions for what I could do next?
Click to expand...
Click to collapse
Here's an older post with links that might be helpful ( http://forum.xda-developers.com/showthread.php?p=57944591 ).
Make sure you're using the pit file when flashing the appropriate firmware in Odin.
Some common issues with Odin also are to make sure you're using a USB 2.0 port on your computer and use the phone's original USB cable or a good quality one if you don't have the original any longer. Also run Odin with Administrative privileges, make sure that Kies is not running in the background because it interferes with ODIN, and disable antivirus programs when running Odin.
Yeah something went wrong in Odin when I flashed the stock recovery the last time and I corrupted my EMMC as Product Name: (Blank) is showing up now.
RIP Note II it was nice knowing you.
ozo012 said:
Yeah something went wrong in Odin when I flashed the stock recovery the last time and I corrupted my EMMC as Product Name: (Blank) is showing up now.
RIP Note II it was nice knowing you.
Click to expand...
Click to collapse
Man... that sucks! I wonder if it was actually Odin, or if the EMMC chip just died. Either way, it doesn't really matter now. RIP Note 2.

Categories

Resources