I've managed to get myself so confused and flustered I don't even know where to go at this point.
A couple months ago I got tired of waiting for Samsung to send out the 4.1.2 Android update so I grabbed the Odin version and updated it myself.
I like it well enough but I want to try putting CyanogenMod 10.1 on my P6210. I tried everything last night and it's turned into a long chain of things that won't work.
The bottom line seems to be that I can't change the recovery mode - I've tried installing goo.im; no joy. I have tried several versions of CWM - no luck. Every time I get the "signature verification" error if I try from stock Android Recovery; if I try from Odin I just get a big "FAIL" message; I've tried with Heimdall and I just get partition errors.
I've reached a point where I don't know what to do - I'd really like to strip it down to basics but I've definitely reached a point where I'm over my head.
Any help would be hugely appreciated...
Related
Hey,
I've tried searching similar threads for this issue but haven't found a solution that works quite yet.
I have Samsung S Vibrant GT-I9000M on which I tried to originally flash CyanogenMod. At first I tried using Clockworkmod and discovered I couldn't actually get into it because of the Samsung 3e recovery utils. So I tried flashing to a different firmware (I've tried a lot now) to get to 2e but I am unable to get past the loading screen, which is flashing the samsung galaxy s logo. I've followed a lot of guides to try to get back to stock firmware but I haven't had any success at all.
I can't get into recovery mode anymore but I can get into download mode, and I've been trying to get back to stock firmware but whatever I try it just reboots and starts flashing a loading icon (if the usb is still plugged in, without it just flashes the samsung s galaxy screen). I've also noticed that the model number changed from GT-I9000M to GT-I9000.
I'm new to all of this, so if anyone can lend a helping hand I'd really appreciate it. So to summarize, I can get back into download mode but I cant' get into recovery. I've tried at least 5 or 6 times to reflash stock firmware (following the guides in this forum, I can link if needed) but its the same result each time. A cycling loading screen.
this guy is having the same problem.. see my posts in his thread.. do all the things i have told him to do..
http://forum.xda-developers.com/showthread.php?t=1022688
Hi guys, reasonable newbie here. My Galaxy S2 has stopped displaying anything after the initial logo. In fact it seems to turn the phone off as you can make repeated attempts to boot it within a few seconds.
I started by flashing an insecure sgs2 kernel from this site with odin, then used s2root.
I then played around with rom managed but found it wouldn't boot into clockworkmod (orange exclamation mark in a white triangle every time) I booted into it manually and started trying to flash cm7 which I had downloaded earlier.
I wiped the data etc and flashed the cm7 zip (plus the google apps zip). Rebooted and got into cm7 with everything seeming fine.
Next I thought I should probably flash back to the stock version of the insecure kernel. I rebooted the phone but got distracted and didn't start it up in download mode, I looked just in time to see the normal logo (with the yellow insecure triangle) and then nothing....just blank.
I tried rebooting afew times and nothing, even after yanking the battery. Then I tried getting back into clockworkmod to reflash cm7. Nope, same thing happens.
I can still get back into download mode but nothing I flash makes the slighest difference. Tried reflashing clockworkmod, insecure and stock kernels of various versions but I'm stuck.
This is almost a new phone and I can't believe I've already killed it I would be so grateful for any tips, I've included as much info as I can think of from the top of my head but I will do my best to answer anything you gurus might need.
Again, very grateful for any help...I don't want to have to explain to Orange how I've managed to brick this after 4 days
Ok after trying over and over again to get into recovery mode, it booted into the original (3e) recovery. I've just flash cwmod to it again and have just flash cm7.
After reading some posts about cyanogenmod sometimes not flashing correctly first time, I did it twice (and it did indeed take longer the second time) and twice for google apps.
Next I'll try to get back to the stock kernel. This is where it went wrong before but i'll cross my fingers.
Edit: Well, multiple reboots didn't cause a problem but flashing the stock kernel back does kill the handset again. I'm sure this stuff is all obvious to those with experience I guess I'll have to sit with an insecure kernel and the yellow triangle for the forseeable future. On a side note, s2root doesn't see the phone connected with cm7 (yes usb debugging was turned on). I'm hoping that it is pre-rooted but I haven't tested that yet.
Hey everyone I am very green to roms and modding .I have a Samsung galaxy GT-P5113 it had 4.2.2 prior to my messing it up I was attempting to remove many of the stock apps from it and attempted to root it. In the process of do that I must have neglected to do a step. because now it boots only to the samsung logo with the blue glow and no further sometimes I get it to the point where I can enter my user information. but just before it reboots after I have entered the user info I get a message that "unfortunately the set up wizard has stopped working . then it goes back to booting only to the samsung glowing logo.
I have tried to down load other roms to try to see if tey may work but no luck I used odin 1.85, 3.07 but no joy tried;CF-Auto-Root-espresso10wifi-espresso10wifibby-gtp5113.tar no luck;Slim-p5110-4.4.2.build.3-OFFICIAL-3079.tar no joy;checked the tar file with MD5 summer and found error in every .tar i downloaded. I even went into recovery mode trying to install a rom from the sd card but got the error E:sdcard failed to mount. I am at my wits end can anyone shed some light on what I can do, or what files I need to fix it a step by step guide would be helpful as all those I followed didn't help.you can email me any help to my email:[email protected] I am very desperate about now its been three days working on this.:crying::crying::crying::crying:
Thanks guys
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
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