Hello. I Was wondering if someone can help me with a dilemma......... i recently got my mega a month ago. I then decided to root my mega (As i do with all my android devices)The rooting process worked out great. The phone booted.....Everything's all peachy! root was successful! After about 3 weeks i wanted to record my screen. By the way i was running kitkat on my mega. So i installed a screen recording program. i wanted to record the screen so i started the recording..... but it wasnt recording. it kept saying an error message i think it when like gpu is not supported and change to cpu something like that! i thought nothing of it... so i changed the settings to gpu then to cpu (Not knowing what i was doing) after it failed to record again i threw the towel in and quit. i then played one of my mobile games(FNAF2) after i lost the game i went back to the homescreen and the homescreen was acting up... it was in landscape mode when i had the phone upright. it was bugging me to the point where i just rebooted my device. i tried rebooting my device BUT IT WAS IN A BOOTLOOP! i had no idea what was going on. So i tried to restore the backup and it was restored but it was still in a bootloop. at this point i was freaking out! when i went home that day i put the device in download mode and flashed the stock firmware but it failed and didnt work. but when the phone rebooted it booted up and my phone was on activation screen and it was in a different language. then i soon found out that my touchscreen wasnt responding! neither was the home button or back button. i really dont know whats going on. kies does not work i tried emergency firmware initializing and kies didnt read it i tried reinstalling kies and my phones drivers 4 times and it was a no go...... but i finally found a english firmware and i flashed it but it failed and said something like dev_not supported or something so that didnt work either..... i booted up my phone and the language was back to english and my touchscreen wasnt working neither was my home buttons or anything. i also tried installing custom roms but everytime i try to install them it says it completed installing but when i boot up my phone its the same activation screen. i really need help anything that can help will be greatly appreciated. also everytime i boot up it always says set warranty bit:Kernal
Related
About 2 months ago, I got a Samsung Infuse 4g. I was thrilled. At first I was satisfied with the stock rom and its limited functions, but then I got really interested into custom roms. I rooted my phone, installed Clockworkmod recovery and flashed Cyanogen 7 rom. During the reboot process, I pulled out the battery just like the tutorial said and thats where everything went wrong. My infuse got stuck into the bootloop, but I was able to get into recovery. I flashed Cyanogen 7 again and it work. However, my home, back, search and menu buttons all stopped working. I figured it was the customed Rom, so I flashed MiUi. The buttons still did not work. What is worst of all, is that My computer refuses to recognize my phone(yes I installed Samsung Kies)(download mode is unrecognizable too). It only recognize it as a storage device. As a result, Odin does not pick it up. neither does heimdall. I need some serious help. I have tried everything. I am currently running Miui and apparently, now I can't get into recovery mode. Guys, please help.
if you cant access the phone from usb and you cant get into recovery then you re screwed.I had a similar problem and had to return the phone to vodafone to fix it
After screwing around with it, I factory resetted and Tried download mode on a different computer and luckily it worked. Odin was able to pick up my infuse and I used Ultimate Debrick. Thanx a million to those within the Community who are consistently developing and coming up with programs such as Odin. Big thanx to everyelse who shares their thoughts and advice.
Hello fellow XDA members! I am a Noob.
So I believe I have a Bricked Galaxy Note 10.1. Model GT-N8013
I Rooted Stock ROM, and flashed Collective Edition 5 Dark Side.
So heres what happened, everything seemed fine, until I made a mistake, I was Pimping my ROM with the PimpMyRom app. Every change seemed fine and my note worked, but when i saw the double boot screen slide in the app, i did what it said, i have the imf support or something like that. Then after i had the ''support'' needed, i clicked install button on the double boot slide, it seemed to do something and requested nothing, so i went ahead chose a second clip, and clicked set as second boot screen. It said it wont take effect until the 3rd boot, so i rebooted 3x, but at the third time, it was stuck at the boot screen with the galaxy note 10.1 logo ! It did not start or did anything, over time it would turn off and automatically reboot, but it would get stuck again !.
To attempt to fix it, I Booted into recovery (CWM) and did everything i could. I wiped nearly all cache, factory reseted, then out of fear, i flashed the stock firmware ROM from Sammobile website, with ODIN, and to my knowledge, it got worse!! It booted, seemed to do something then in the logo screen it got stuck once again!! Stock recovery says unable to mount /efs, i don't believe EFS is completely corrupted, I left it stuck for awhile and it shut down in like an hour. Help, what can i do to fix this!?!?!?!
Device cannot boot up.
I could boot into recovery and download mode only.
I thought that I too had bricked my 8013 the past weekend. Trying to do something that I shouldn't. It took me a bit of work and a lot of worry (my wife gave me my 8013 for Xmas and if I had to tell her that it was now a doorstop, she would have killed me). I used this method to get back to stock and then was able to work my way back to the ROM I use. I disremember in which order I Odin'd things, but in the end was able to un-brick. All I can say is give it a shot.
jusliloleme said:
I thought that I too had bricked my 8013 the past weekend. Trying to do something that I shouldn't. It took me a bit of work and a lot of worry (my wife gave me my 8013 for Xmas and if I had to tell her that it was now a doorstop, she would have killed me). I used this method to get back to stock and then was able to work my way back to the ROM I use. I disremember in which order I Odin'd things, but in the end was able to un-brick. All I can say is give it a shot.
Click to expand...
Click to collapse
i did what u said...but all i got is i able to get through the logo but without seeing anything only able to hear the sound. any other tip? i got the same problem as above.
Hello I am searching for help. The problem is that my galaxy s2 i9100 stopped working properly. It started like this maybe I took out the battery or something I don't remember and then I turned it on the phone wouldn't boot. I thought maybe my android operation system got bricked so I decided to re flash it but as I can remember the phone wouldn't go in to download mode but some how I managed to reflash the firmware but then phone booted it just froze and then I pressed lock button the phone screen would go black and reboot. After installing cyanogen mode 11 the phone would boot and it could be used again until pressed the lock button it would go black and reboot so I have been reading forums and found problems like boot loop corrupted mmc or something else corrupted and I don't know what the real problem is because the symptoms are like boot loop or corrupted mmc or soft brick. I have already tried other kernels other android versions clock work mode
migimantas said:
Hello I am searching for help. The problem is that my galaxy s2 i9100 stopped working properly. It started like this maybe I took out the battery or something I don't remember and then I turned it on the phone wouldn't boot. I thought maybe my android operation system got bricked so I decided to re flash it but as I can remember the phone wouldn't go in to download mode but some how I managed to reflash the firmware but then phone booted it just froze and then I pressed lock button the phone screen would go black and reboot. After installing cyanogen mode 11 the phone would boot and it could be used again until pressed the lock button it would go black and reboot so I have been reading forums and found problems like boot loop corrupted mmc or something else corrupted and I don't know what the real problem is because the symptoms are like boot loop or corrupted mmc or soft brick. I have already tried other kernels other android versions clock work mode
Click to expand...
Click to collapse
I have found that my emmc has the insane chip bug. The phone boots normally with cyanogen mode 11 but then it goes to sleep mode or I press the power button the screen goes black and the phone restarts. I have tried siyah kernel to try dual boot but then I flash siyah I cant get into recovery.
I think you should flash latest STOCK ROM with Odin, and then follow available custom rom instructions on xda...
Test if the stock rom will work for you, boot your phone etc... Try to use it a few days. If everything is OK, proceed with
further procedures...
twinsen.net said:
I think you should flash latest STOCK ROM with Odin, and then follow available custom rom instructions on xda...
Test if the stock rom will work for you, boot your phone etc... Try to use it a few days. If everything is OK, proceed with
further procedures...
Click to expand...
Click to collapse
I have already tried this but with the stock rom phone boots but at the section where I have to chose language I jus freezes stops working
So I think it is a hardware problem. Phone on stock rom shouldn't freeze on language selection. Something is wrong. If you are on warranty, let them fix it for you, if you are not, try to fix it in some phone repair point. I'm sure you can stop your attempts. It will not be better for now.
twinsen.net said:
So I think it is a hardware problem. Phone on stock rom shouldn't freeze on language selection. Something is wrong. If you are on warranty, let them fix it for you, if you are not, try to fix it in some phone repair point. I'm sure you can stop your attempts. It will not be better for now.
Click to expand...
Click to collapse
Take it straight away to the official service centre
So I have had my S3 rooted for a long while. But the past few weeks it's been running a bit slower. This week it started randomly turning off. I thought it was my battery at first. But then when I tried to turn it back on it got stuck at the Galaxy s3 screen and would not get into the OS.
I tried to get into recovery, it froze on the splash screen. I made sure both were actually frozen by leaving it sitting there for 30 min to an hour.
Tried to flash using this thread: http://forum.xda-developers.com/showthread.php?t=1974114
It kept just sitting at writing NAND.
Now my phone says "Firmare Upgrade encountered an issue, please select recovery mode in kies and try again"
Kies will not connect my device. It sees it but will not complete the connection. I tried using the model and IMEI number to upgrade firmware but it still would not connect to do that.
More searching lead me to this: http://forum.xda-developers.com/showthread.php?t=2581166&page=11
But I can't get into OS or recovery so I don't think this would work.
Any suggestions on what I can do from here? I only really need the phone to work for a few more months. My old Droid incredible just doesn't cut it at this point.
Sorry to bump, but nobody has anything for this? I haven't really found any other options.
Your bootloader is fine so that thread won't help you. What was the last version of touch wiz that was on your phone before you ran into problems?
Let me start by addressing I know this isn't the sprint thread but there's a lot more development here which equals more help. Plus this issue seems to be able to happen to any variant.
Second, this isn't my device I'm trying to see if it can be fixed for a friend. I'm not that familiar with Samsung devices but I have been able to get them working in the past via Odin or kies but this time I need some help.
So this is what's going on, my friend recently rooted his S6(SM-920P) not sure which method he used (don't think it matters at this stage) and was on stock rom (LP5.0.2) with xposed framework installed. He hadn't changed the kernel AFAIK oh but I did install TWRP for him and everything was working. Long story short he woke up a couple days ago to his phone being unable to turn back on. I told him how to get to download mode and I asked him what did it say on the top left corner it said something like "system binary not SEandroid locked" underneath that it said fac lock
So I had him give me the phone thinking somehow it did a OTA update while he was asleep or something either way I was confident using Odin to flash the firmware would solve the issue. Had the firmware finished flashing I'm confident it would have but halfway through Odin simply froze on installing system. I figured its just gonna take a while 45 mins later it was still stuck at the same spot.
Not really thinking about it I figured I will just reboot the phone back into download mode restart the process it should be fine. Not a good idea. Now all I get is a green screen saying to access the smart switch emergency recovery system. But it gets better.
My computer isn't recognizing the device now. I installed smart switch software and it's not recognizing it. I even installed Kies and it's not recognizing either.
Is his phone toast or what? I tried emergency system recovery but I need the S/N of his phone to possibly get this thing working again, but it boot into anything anymore except the screen that says Samsung switch...
PLEASE HELP ME if it's bricked it's bricked I get that but if there's a way to figure out what to do I'm all ears. Thanks in advance