TL;DR; version on the bottom.
Hi everyone. I'm long time user of xda, though I rarely post, because I've always found the solution for my android problems until today.
I've bricked many phones in the past and always managed to get them back up working, including my Galaxy Nexus that has been bricked easly over 10 times... possibly over 15.
Anyway, yesterday I was testing some Kitkat 4.4 stuff on my phone. my daily ROM as been paranoid android for a long time. since they were on 2.8 or something.
First I installed nexus 5 launcher on my gnexus because I really wanted to test the new google experience thing.
Then I thought it was a bit slow, and decided to install a full 4.4 ROM. ended up deciding I couldn't miss some of the paranoid android features and flashed my paranoid android rom back (3.99 RC2), installed the GEL (google experience launcher) installed xposed framework and put my device the way it was pretty much.
To make GEL a bit more faster and fluid I decided to overclock a bit (I've overclocked alot in the past up to 1900+ Mhz and never had problems though I know it's not healthy for the phone.)
I've overclocked it to about 1500... I just wanted to see how it would work and then turn it back to normal again.
I got distracted for some reason and forgot to turn it off (and I think it might have been that... something burned inside or something...)
At night I was checking something on the browser, and then the phone suddenly reboots, which happened in the past several times (people that flash alot should know).
the phone started boot looping on google logo and from my previous bricks I knew it was bricked and I did what I usually do.
Went to recovery mode, wiped everything expect internal storage, dalvik cashe, system, cashe and data.
tried flashing paranoid android and gapps, didn't work. Then proceeded to flashing stock rom, didn't work either.
From that point and from my previous bricks, I knew it was something more serious than just rom.
So then I did a odin flash, and I thought it would be fine after because odin never failed me before. I did odin flash, it did the google logo boot, and then started the boot animation from the stock rom and after 3 seconds looped google logo again followed by the stock nexus bootanimation (before it only looped the google logo boot).
I searched a bit on xda, and found this thing called OMAP (I used this post http://forum.xda-developers.com/showthread.php?t=2146790), which apparently is something you do when your phone has no software at all (for people that somehow mess their bootloaders and/or downloading modes )from what I understood.
I tried it out, it kind of worked I believe though I found odd that my device kept reconnecting to my pc as "omap4460 usb device" every 3 seconds.
After that I did a odin flash again and didn't work.
After all this I'm thinking that the problem is not software but hardware because of that little overclock I did and forgot to undo.
Any help would be appreciated.
TL;DR; Version:
Was running paranoid android 3.99 RC2, installed the new GEL (google experience launcher);
Overclocked a bit to make GEL faster but intended to put the clock speeds to normal after;
Forgot to set the clock speeds to normal (though I'm not 100% sure that's what messed my device);
At night while using the browser the device rebooted and got stuck in google logo bootloop.
wiped everything except internal storage and flashed paranoid android, didn't work, flashed stock rom, didn't work either;
Did a odin flash, device appeared to boot, at least got over google logo boot, and started the stock bootanimation, but kept looping that.
Did OMAP (I don't know the right term for this... OMAP flashing? I don't think that's correct)thing to see if would fix the phone, then odin flash again but didn't work.
Any help would be appreciated
How do you did the OMAP Flash works? My problem is little same, but i cant enter to download, recovery or fastboot mode, and I read the OMAP can help me, but when I star the process of OMAP my GN don't change anything, and in the OMAP says the process is finish :C!
Do you know something about this? :C
make sure your pc can detect ur device.. as omap ( if not try plugged off your battery)
1. run the omap4460_tuna.bat
2. plug in ur phone without battery..
3. when, the mapflash detect a device, plug-in the battery.
4. your gnex will go to bootloader page..
5. then can restore anything thru odin or nexus toolkit
try this step first..
sorry for my bad english
galaxy nexus i9250
How did u get into 1.9Ghz+ clock, the Ezekeel's Glados for 4.2.2 only had that much of clock speed step (though Np could'nt handle that), and Trinity had only till 1.8Ghz max !
did u try the original fastboot google stock JWR66Y image flashing by erasing all partitions and then re-flashing ??
Though this one looks like a very serious issue....
Bl4ckB1rd7 said:
How do you did the OMAP Flash works? My problem is little same, but i cant enter to download, recovery or fastboot mode, and I read the OMAP can help me, but when I star the process of OMAP my GN don't change anything, and in the OMAP says the process is finish :C!
Do you know something about this? :C
Click to expand...
Click to collapse
The omap only use is to get the bootloader back in case you mess it up somehow (which was stupid in my case since mine was working to begin with but I did it anyway).
Follow exactly what is in that link and after that you should have your bootloader back..
After you do it you should be able to get into fastboot and download mode and then, odin flash your phone and get it back operational.
Ashtrix said:
How did u get into 1.9Ghz+ clock, the Ezekeel's Glados for 4.2.2 only had that much of clock speed step (though Np could'nt handle that), and Trinity had only till 1.8Ghz max !
did u try the original fastboot google stock JWR66Y image flashing by erasing all partitions and then re-flashing ??
Though this one looks like a very serious issue....
Click to expand...
Click to collapse
it was a long time ago, about 6 months, maybe more, with one of Experimental Ak kernels... it was called ak pirate or something I believe.
It couldn't handle that speed for too long though. I never tested it to the limit because whenver I thought the phone was getting way too hot I put it back on normal values inb4 it became a toaster powered by android lol.
Anyway, imo gnex clock speed won't afftect too much your performance... what I needed on it was more ram, not really speed.
Related
This boot looping issue is not like the normal ones (I have googled,as well as checked here...I am a noob,but know how to search)
I am running CWM v3.0.0.5
Energy ROM
And Aggressive Freedom (Was running More freedom prior,but still the same issue occured)
It does not matter which rom i am running ( have tried about 5 now)...after a few days my phone will lock up no matter what i am doing and then reboot,except it gets stuck in a boot loop...If I do a battery pull and fire it back up...no problem it boots up like nothing ever happened...and after a few days it will do it again so on and so forth. This has not always happened, it started occurring around 3 months ago. Can anyone help me as to rectify this issue?
Also when i flash a new rom i do a factory wipe/reset,run gruesome format all 3 times,clear cache,as well as dalvik cache..and THEN i will flash the rom over.
Any help would be GREATLY appreciated. its not a GIANT pain but it just wants to happen at odd times which sucks lol
Kernel
Have you tried installing a different kernel trough Recovery?
Edit: Sorry, didn't read your post carefully enough. Have you tried a stock kernel?
No i have not tried a stock kernel. Figured with aggressive/more freedom it would be a little more lenient on the battery life.
Look in this post: http://forum.xda-developers.com/showthread.php?t=708502
Since I don't own an EVO, I'm not sure if this is a good one. Try it at your own risk.
Do a search in the development section for a stock kernel also maybe download set CPU to try one of the governors sounds like phone does not like over clocking they all run a little different.
Rammv said:
Do a search in the development section for a stock kernel also maybe download set CPU to try one of the governors sounds like phone does not like over clocking they all run a little different.
Click to expand...
Click to collapse
Thats the problem i was having also,my phone could'nt be overclocked over 113600 MHz or it would start locking up and giving me random reboots,try dropping your level.Ondemand profile works great with my phone,others seem to give me problems.
busted GPS receiver
My wife's Evo did the same thing and we spent a total of 6 hours at the [carrier] store trying to get them to replace it. The store is cement and cinder blocks so there is no GPS signal inside. The phone easily passes their "complete" diagnostic.
Finally, I became irate and pleaded the store manager to get in my car with me. Before we got out of the parking lot, the phone began rebooting.
Turns out, their "complete" diagnostic doesn't test the GPS receiver in any way. He knew this, but I had to point it out to him.
My phone is underclocked with the kernel i am running UNLESS the roms i use some how over clock them, SetCPU does not work for me. And my GPS is always turned off because i try to conserve the battery life.
I will go ahead and see if i run the stock kernel...or one that comes with the rom instead of using Aggressive or More freedom kernel and see how that one fairs out.
htc evo boot loop
i was using my htc evo fine today, it was on 2.3 ota when i rooted it with revolution, it was half way flashed to boost, it already had the NV items and the Nam files, on the front said boost mobile, after i rooted i put a Speedy Shift rom, to make it have the internet pass through like the shift, so today i decided to finish flashing it to boost, after i put the nv and nam files again, i restated the phone, and from there it just keep doin a endless reboot, i could only go in the hboot, i tryed the pc36img, Amon ra, Ruu, and rerooting with revolution but it doesnt read the phone on fastboot, any help?
S- Off
HBoot - 6.16.1002
Radio - 2.15.00.0000
So here's the situation and this is literally the 3RD time this phone has done this. I'll be on a ROM on my rooted unlocked galaxy nexus, and randomly I'll be opening my texts or contacts or something and my phone will reboot. No big deal right? But then it just boot loops. Endlessly. If I try to restore a nandroid from a different ROM, it'll get almost done then won't be able to restore /data. I know it's not a bad nandroid backup cuz I switch back and forth between them all the time. I can't flash any rom, it'll be a boot loop, can't restore a nandroid,so I always have to end up flashing a stock image and start from scratch again.
I've seen this problem before after it happened the first time and found that flashing stock img fix. I have two questions: Why does it do this randomly every month? It's like my bootloader goes MIA or something for no reason. What would cause it to do this and literally, almost once every 30 days?
Second question: Is this a stable phone? I'm coming from the nearly unbrickable Captivate and I've done some crazy stuff to that phone and always managed to recover it, a couple times when it shouldn't have even worked at all. But yet this thing breaks down almost every month. Didn't flash anything new, didn't flash anything incompatible, nothing. Everything was running smooth. Then all of a sudden reboot, boot loop, backups dead, roms on SD card are useless.
Can someone please fill me in on what's going on with this? lol this is my 5th rooted android phone, not a developer or a themer or anything, but I know quite a bit about what would cause a phone to do whatever. Any insight would be great. Thanks guys!
Wich roms are you trying? Wich rooting methods? Wich flashing method? Are you using adb and fastboot?
Edit: does the issue happens on stock?
So far my phone its rock solid stable and buttery smooth fast after 3/4 months
Galaxy Nexus AOKP m5 Franco kernel m3
It first happened on liquid rom. I rooted via Samsung gnex toolkit. It happened again on gummy 1.2.0 honestly I wasn't on stock long enough to see how stock ran lol I don't use adb or fastboot often. Just to root and recently, to flash a stock image every time this happens
Sent from my Galaxy Nexus using XDA
I'd try rooting properly by using fast boot and flashing a superuser.zip. It may be that the toolkit is not working properly and you have a bad recovery. Something is wrong if this is happening. Its not too hard...
Sent From My Sprint Galaxy Nexus via XDA Premium
Hello,
I'm running into a very strange issue. I've had Note 2 for a while now (since Nov 2012 -ish) and up until a few days ago it's performed magnificently. I have not load any custom ROM/mod or anything like that - simply because I use Note for work and Good For Enterprise freak whenever there's a custom ROM mod (I didn't even attempt it with Note 2, due to my experience with GFE crapping out on my Galaxy Nexus every time I try to load a custom ROM). But, no complaints so far.
A few days ago (Mar 1st? give or take a day), I got a prompt for a system software update. Ever since then, I have had nothing but trouble with my Note 2. It would boot up fine, but in a few minutes, whether I'm in email, or browsing the net, or running WeChat, or Viber, Pulse, or any of the other apps that I normally use, the screen would freeze up. Power button would turn the screen off, but then once you turn on the screen again, you can't swipe to unlock the screen. Home button doesn't work. The only thing that I could do "to reset the phone" is hold down power and home button and force it to reboot.
Edit: I forgot to mention something, I remember many of the times when I am experiencing the freeze issue, I can still drag down the notification settings, but can't click on anything though. If this helps any one to help me troubleshoot my issue.
Now, I've tried to reload 4.1.1 stock kernel (there are a couple of them), 4.1.2 stock kernel via Odin (I downloaded them from http://samsung-updates.com/). with 4.1.1, the device would be stuck in a bootloop, 4.1.2 works, but after a while, screen freeze problem comes back. I've tried a bunch of things, such as:
1) Just flashing the kernel
2) factory reset via the VolUp+Power+Home, then flash kernel
3) removed my MicroSD, repeat 1 or 2.
I'm totally out of ideas.. can someone help?? Please! I'm stuck with my old iPhone 4s and let me tell ya.. Once you get used to Note 2, iPhone 4s seems positively TINY!!!
any help is appreciated.. but can someone please enlighten me??
PS. Adding insult to injury, my SO who is a hardcore apple fan, now chants "see how stable Apple is?" every time I'm *****ing about this damn Note 2.. heh..
mobilebuddha said:
Hello,
I'm running into a very strange issue. I've had Note 2 for a while now (since Nov 2012 -ish) and up until a few days ago it's performed magnificently. I have not load any custom ROM/mod or anything like that - simply because I use Note for work and Good For Enterprise freak whenever there's a custom ROM mod (I didn't even attempt it with Note 2, due to my experience with GFE crapping out on my Galaxy Nexus every time I try to load a custom ROM). But, no complaints so far.
A few days ago (Mar 1st? give or take a day), I got a prompt for a system software update. Ever since then, I have had nothing but trouble with my Note 2. It would boot up fine, but in a few minutes, whether I'm in email, or browsing the net, or running WeChat, or Viber, Pulse, or any of the other apps that I normally use, the screen would freeze up. Power button would turn the screen off, but then once you turn on the screen again, you can't swipe to unlock the screen. Home button doesn't work. The only thing that I could do "to reset the phone" is hold down power and home button and force it to reboot.
Edit: I forgot to mention something, I remember many of the times when I am experiencing the freeze issue, I can still drag down the notification settings, but can't click on anything though. If this helps any one to help me troubleshoot my issue.
Now, I've tried to reload 4.1.1 stock kernel (there are a couple of them), 4.1.2 stock kernel via Odin (I downloaded them from http://samsung-updates.com/). with 4.1.1, the device would be stuck in a bootloop, 4.1.2 works, but after a while, screen freeze problem comes back. I've tried a bunch of things, such as:
1) Just flashing the kernel
2) factory reset via the VolUp+Power+Home, then flash kernel
3) removed my MicroSD, repeat 1 or 2.
I'm totally out of ideas.. can someone help?? Please! I'm stuck with my old iPhone 4s and let me tell ya.. Once you get used to Note 2, iPhone 4s seems positively TINY!!!
any help is appreciated.. but can someone please enlighten me??
PS. Adding insult to injury, my SO who is a hardcore apple fan, now chants "see how stable Apple is?" every time I'm *****ing about this damn Note 2.. heh..
Click to expand...
Click to collapse
Um, you mentioned Odin. I say go back to the site you got the "kernel" from and download a full stock firmware. Try to find the original one that came with your phone model. Flash via odin. Should fix if a software issue. If after wipe and stock reinstall issue still occurs you may want to consult whom you purchased it from. Could be a hardware failure.
You are right, I actually meant to say full firmware images (they are about 1.5GB uncompressed "md5" files).
aswethinkweiz said:
Um, you mentioned Odin. I say go back to the site you got the "kernel" from and download a full stock firmware. Try to find the original one that came with your phone model. Flash via odin. Should fix if a software issue. If after wipe and stock reinstall issue still occurs you may want to consult whom you purchased it from. Could be a hardware failure.
Click to expand...
Click to collapse
Do a mega wipe via zoot's script. Then from recovery reboot into download mode. Then flash the latest stock rom for your country. (If latest is 4.1.1 then flash latest france rom)
After this procedure every bit of information would be deleted from your phone. So backup accordingly.
Sent from my GT-N7100
I have the same problem. Wiping and resetting didn't help. I sent mine for repair but Samsung is ignoring the issue and they sent it back to me unrepaired. I'll probably have to send it in again or try to get a replacement.
Many people here in the forum seem to think these are symptoms of imminent sudden death syndrome so no fu Good luck and let us know how it goes for you.
install "eMMC Check" from google play and run it.
If your eMMC chip is;
Type: VTU00M
FwRev: 0xf1
read this thread, Note 2 SDS (sudden death syndrome) and worry!!
I have 0xf1 insane chip and am experiencing your exact same symptoms.
Hey Honestly ,
I am not a big Fan of APPLE but i should say that the Apple Os is Very stable , Now the reason of it being stable is because the Apple is not an Open Source Os , Where in Android is an Open Source so there are huge number of Developers who are giving you so many apps for free,u've got lot of Mods and tweaks that can be done on Android where as not on Apple , So Please stop comparing that Apple is stable , not Android , Where there is always a fix for all the problems , I would suggest you to try a Clean install of Stock Firmware by Formatting your Sd and Resetting your Phone and Flash the Stock with Odin.
It is not a sign of sds. It is like fever.
When you have a disease you get fever.
Fever means that your body is fighting against the disease.
Freezing is the fever here. To prevent sds the phone freezes. There is no correct explanation but it seems it only happens after upgrading to sds fixed roms.
this is XXXDDDAAA
Had 5 freezes and/or resets between 07:00 and 08:00, same story for the past few weeks since firmware upgrade XXDMB2.
Now with latest XXDMB6 firmware downloaded this morning its been to rock steady for the last 6 hours
I am 0xf1.
Hi
Guys i need your help. Pleas can someone tell me for now what mods is much better for I927R (Also withe very stability and with much less bugs) ?!
I found Liquid Smooth but it have some problem so i need your guide about other mods.
Thank you
ICS Roms are the best and most stable... Stock ICS from AT&T UCLJ3 or any roms based off of it ... Dman's daily driver, Ice Pop Rom by RawRaw, LiteRom by TheGreaterGood...
Unfortunately none of those are being maintained but I had been running Dman's for the last couple months, great battery life when paired w/ JuiceDefender (20+hours of heavy use when I'm not sleeping).
Now the newest CM10.1 by Spyke seems pretty solid ... Just a couple of issues.
ICS is the only one you'll get bug free, though. Stock is hard to compete with when we're pairing up roms without a true Devdeloper.
On this subject, I've just reverted back to using IcePop ROM after (unhappily) downgrading from Spyke's latest 10.1 ROM - just mainly because of the Bluetooth headset issue, which I really need working for work purposes.
I'm just wondering if there are any ICS builds that have GPS working correctly? I tried flashing the Rogers modem (since my phone was originally a Rogers import, flashed to AT&T ICS, then played with ICS from there) and first time I ran GPS status it took 771 seconds... I'm going to keep trying just in case that was the first time only, but 12 minutes is still a very long time for an initial fix .
Also - I've found that I'm getting more and more bootloop problems even with clean installs - so wiping cache, data, dalvic, etc. Is there some way to do a *thorough* wipe without bricking the phone? I can back all my data up no worries, but next time I move to JB (in the optimism that the BT issues will be fixed soon, judging by the positive progress being made by Spyke ) I would like to do a clean build from scratch and not have to gamble being able to start the phone up again
David - I always go into mount options of CWM and format /system prior to a new flash .. I'm not sure if flashing with Odin will get rid of any previous settings, its something to attempt though.
I, also, had reverted to using JB Because GPS wouldn't work ... There's a thread in here (search for it) that shows the solution to the GPS fix, its editing sirgps.conf and gps.conf ... I was getting a fix on GPS in under 30 seconds.... GPS was a huge let down in the stock ICS rom, Even when using TheGreaterGoods LiteRom w/ GPS fix I found after a couple of days my gps didn't hold....
Thanks for the reply.
I was considering formatting /system this morning when I was getting stuck in a boot loop from trying to get M3 running, but decided it was a risk I'd have to check up on first . Next time I do a build from scratch (I'm going to resist until the BT stuff is working - fingers crossed!) I'll do that.
I remember having a look at the gps.conf fix but don't recall anything about sirgps.conf - so I will look it up, thanks!
As an aside, I've been checking the GPS fix a couple of times since my last post and it is coming up in under 30 seconds each time... I'm wondering if my attempt to flash the Rogers modem did in fact fix the issue... I'd do a reboot but I'm too scared I won't get the phone up again XD
EDIT:
Found the fix, I did a few of the changes (rather than all of them), and it's now picking up 8 satellites instead of 3-5, and getting a stronger signal from each... and all I did was point it to the AU ntp server, and tell it I'm not on the ATT network . I'll save the suggested settings to a text file on my SD card so next time I'm out and about and if it plays up I'll have access to the details.
yohan4ws said:
David - I always go into mount options of CWM and format /system prior to a new flash .. I'm not sure if flashing with Odin will get rid of any previous settings, its something to attempt though.
Click to expand...
Click to collapse
Had to restart my phone tonight and got caught in a boot loop again... after trying a few things I flashed Lite Kernel (I'm still using ICS again at the moment) and that seems to have solved the boot loop issues. I'm thinking that with all the ROM flashing I've been doing the fact that I actually had the phone running without flashing an ICS specific kernel (after running JB) was screwing things up.
Interestingly though, I tried installing Spyke's M3 ROM from a complete user wipe, system format, everything gone - and I still got a boot loop so next time I try it I'll grab a copy of LiteKernel and do that separately.
davidpartay said:
Interestingly though, I tried installing Spyke's M3 ROM from a complete user wipe, system format, everything gone - and I still got a boot loop so next time I try it I'll grab a copy of LiteKernel and do that separately.
Click to expand...
Click to collapse
That has to be very concerning to you, I've never had an issue booting any ROM. And very strange flashing the Kernel separately would resolve your booting issues...
Did you try to flash any of the stock roms w/ Odin ? I have read that we can only flash back to stock Gingerbread from JellyBean if we flash a GB or ICS CWM ROM and then go back with Odin otherwise there will be boot issues.
If I were in your position I would try and do a full revert back to the earliest version of gingerbread I could find on samfirmware and then use Kies to udpate - THEN I would retry flashing to a newer JB or ICS Rom.
Pretty time consuming but that is the price we pay to mod
davidpartay said:
Had to restart my phone tonight and got caught in a boot loop again... after trying a few things I flashed Lite Kernel (I'm still using ICS again at the moment) and that seems to have solved the boot loop issues. I'm thinking that with all the ROM flashing I've been doing the fact that I actually had the phone running without flashing an ICS specific kernel (after running JB) was screwing things up.
Interestingly though, I tried installing Spyke's M3 ROM from a complete user wipe, system format, everything gone - and I still got a boot loop so next time I try it I'll grab a copy of LiteKernel and do that separately.
Click to expand...
Click to collapse
My phone has an issue, simple I couldnt reboot it, I must power off and wait a little. You can try it when you flash something, just remove battery and usb cable, and wait 2 minutes, before you turn on.
yohan4ws said:
Did you try to flash any of the stock roms w/ Odin ? I have read that we can only flash back to stock Gingerbread from JellyBean if we flash a GB or ICS CWM ROM and then go back with Odin otherwise there will be boot issues.
Click to expand...
Click to collapse
Not yet. I'll have to check which ones I have - I'm certain I have the AT&T ICS rom from November but then I'd have to go digging through my email for the unlock code again, so I'm trying to avoid doing that at this point . If i can find the stock GB Rogers rom at some point I might flash that one back on before I do any more upgrades. The phone is up and running at this point though, so I'm not too fussed. I've also noticed that it's a little quicker than before so I think the version of LiteKernel I installed was a good idea anyway.
bubor said:
My phone has an issue, simple I couldnt reboot it, I must power off and wait a little. You can try it when you flash something, just remove battery and usb cable, and wait 2 minutes, before you turn on.
Click to expand...
Click to collapse
I've tried pulling the battery a few times, but probably no longer than 30 seconds. Next time I'll give it a couple of minutes. I tend to do this late at night when I'm not expecting any calls (except fire brigade but I have a pager for that too) so time without a phone is no issue to me
Yesssss
After much irritation at continually getting stuck in boot loops again, I've 'Oneclicked' the phone twice, got fed up with the AT&T ICS ROM within about 5 minutes, gave up on IcePop because of buggy GAPPS...
And thought, bugger it. Format /system. Factory reset. Clear cache + Dalvik. Installed in this order:
Jellybean 4.2 ROM from 0217
Spyke's M3 update
PAC rom
GAPPS dated 0427
"Kick-ass Kernel"
and it BOOTED FIRST GO
I am pleased
Does JB need already to be installed before putting the M3 revisions on? Maybe that's where I've been going wrong all along, because my attempts at running both the standard M3 and PAC ROM (even immediately after OneClicking) resulted in boot loops or eternal boot loading.
Uhh... what do you mean by "One Clicking" ??
I know there's a "superoneclick" that will flash and root the rom all at once, but I never personally found it to work for our glides.
Using CWM and installing the ROM through the CWM boot menu is severaly key presses so ... not too sure what you're referring to.
Also, I've always downloaded to a hardwired computer then copied over USB to my phone and flashed ... sometimes the download will have errors if I grab it from my phone.
I'm assuming it's a variant of SuperOneClick... The title is 'Odin3Excution v1.85' and then underneath it says 'I927UCLG9_OneClick'.
And it worked just fine, I did have a stock rom that I tried to flash with Odin but it kept giving me errors, the OneClick method worked.
davidpartay said:
I'm assuming it's a variant of SuperOneClick... The title is 'Odin3Excution v1.85' and then underneath it says 'I927UCLG9_OneClick'.
And it worked just fine, I did have a stock rom that I tried to flash with Odin but it kept giving me errors, the OneClick method worked.
Click to expand...
Click to collapse
Interesting... for future reference, www.samfirmware.com has the stock firmwares, then there's the superUser file floating around the forums that allows you to root by flashing it. Passed that, remove bloat.
Glad you got it working! Welcome to JB
[Q] "Udpated" my XPlay without flashing boot.img and all went to sh*t. Any clues?
So I had this custom ROM based on a CyanogenMod 9 (I think, cannot be sure, It was a Jelly Bean ROM) working awfully on my phone, even "Trebuchet font" was force closing. Can't remember the name, so if any of you knows how I can guess, like from some registred data on my SD card or something, I'd be a great help.
Well, I tried factory resetting and It didn't fix anything, so I tried to "update" my phone with the internal function built in the Cyanogen Roms to the Stock Cyanogenmod 9.
And from then, the phone is working even more like **** (literally the screen is sliced in half and going like left to right continously), to the point that I can't flash any rom because the Flashtool doesn't recognize my phone (debug mode and unknown sources activated) anymore in any of the 3 computers I tried. I feel like I'm in a dead end.
I don't hava any backups, so the only thing I think it can fix my phone is flashing the same ROM that worked like **** but less like **** as the one I have know, and from there flashing another ROM properly.
Any way to find my old ROM? Another way to fix my phone?
Functionality of flash mode/fastboot is not related to installed ROM, unless you damage bootloader. You're doing something wrong, or just did not installed needed drivers.