Related
Phone worked fine with lagfix... but consumed too much battery and I decided to uninstall the lagfix with the mcr script...
Then applications stopped working and it gave errors, so the best thing to do is to reboot I thought NOT
Now it will not boot annymore and it's stuck after the nice Samsung intro after that my screen stays black and the only response is the illuminated keys..
Tried 3-button recovery but that didn't work.. no recovery no download mode..
I have one from The Netherlands, Europe/International version.
PLEASE HELP ??
you can try to flash a stock Euro ROM back into your phone with Odin and repartition enabled
if that doesn't work, then the next best thing is to send the SGS back to repair
How can Odin see my phone? The only thing I can see are 2 external sd card that I can't access.
use the 3 button Download Mode to get into the connection with Odin
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series
instructions on Wiki
How long have you waited for the samsung galaxy s intro to pass ? I had quite a shock myself when I rooted my phone. I just had to be patient and the phone went on to operate as usual after a long initial wait during the time the logo was shown... After that, every subsequent reboot was faster.
I haven't flashed my phone because Odin can't recognize my phone. It just hangs in the boot screen and there isn't happening anything. The phone just gets warm and does nothing... Looks like that lagfix f*cked up my root
Guess I must head back to the store ... and wait ... 2 weeks or more so...
Have you tried the heat fix to get the 3 button working?
Sent from my GT-I9000M using XDA App
Which lagfix were you using?
The One Click Lagfix takes awhile to boot up at first
KaliKot said:
Which lagfix were you using?
The One Click Lagfix takes awhile to boot up at first
Click to expand...
Click to collapse
he's un-installing/removing/deleting the lag fix out of the phone,
not installing it for the first time
AllGamer said:
he's un-installing/removing/deleting the lag fix out of the phone,
not installing it for the first time
Click to expand...
Click to collapse
You're right. After I heard it consumed very much energy I decided to UN-install the lagfix which messed up my root by partitioning it wrong...
Brought it back to the store today so I hope to have it back soon!
Then after delivery I will make sure I can access the 3-button combo!
same here. damn it, my JF5 don't have 3BR
already sent to SGS last friday. hope that I will get it back on this week.
We should tell others that who installed LagFix
DONT TRY TO UNINSTALL IT Unless you got your time to wait.
NXJeff said:
same here. damn it, my JF5 don't have 3BR
already sent to SGS last friday. hope that I will get it back on this week.
We should tell others that who installed LagFix
DONT TRY TO UNINSTALL IT Unless you got your time to wait.
Click to expand...
Click to collapse
Yeah that will be a very smart thing to do!
The main guideline will be: Don't do anything stupid before you can access the recovery and download mode
Got my phone back, but still hecitating to do the 3-button flash since there are more people that have bricked their phone with it.
Hopefully the Froyo update comes soon! (in one of these days )
Sorry for the long read, this is half rant and half question.
Alright, I got a captivate a long time ago (about a year and 3 months ago), loved it, rooted it and installed cyanogenmod as soon as I got home, changed roms and kernals constantly, did whatever I wanted to do.
About 3 months ago my screen stopped working.. So I take it in and they give me a refurb captivate, looked brand new so I didn't mind. However, when I tried to get into recovery it didn't work, the 3-button-method just wouldn't work at all, period, so I try to get it to work, gets stuck in bootloop.. pretty much every time I try to flash a rom something goes wrong and I get stuck in a bootloop but I can usually get into recovery or download mode because I had CWM.
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
I guess my only option is to usb jig it, but honestly now I'm convinced that the phone is just faulty, I want to run the thing over.
-Pirate said:
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
Click to expand...
Click to collapse
If you would have actually searched you would have known it was a bug in the glitch. There are atleast 40 pages about that.
-Pirate said:
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Click to expand...
Click to collapse
If you flashed ICS you should know it takes 2 flashes for it to work first time. Having a jig around is always a good idea as well.
-Pirate said:
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
Click to expand...
Click to collapse
Stuff doesn't work as intended. Keep in mind everything is still in dev and not all devices are the same. But you should have searched a little more and it would have ran =/
U def don't need a jig. If it's booting it's not bricked. Try removing battery, start Odin, hold down power and down, plug in and put battery in. This should bring u to download mode.
prbassplayer said:
If you would have actually searched you would have known it was a bug in the glitch. There are atleast 40 pages about that.
Click to expand...
Click to collapse
I did start to see a few people with the problem, however many people do not follow up with what fixes their problem, and I did what a few people had said to do.
prbassplayer said:
If you flashed ICS you should know it takes 2 flashes for it to work first time. Having a jig around is always a good idea as well.
Click to expand...
Click to collapse
I should of mentioned that I did flash a few times, 3 total I think, it was getting stuck at boot.
prbassplayer said:
Stuff doesn't work as intended. Keep in mind everything is still in dev and not all devices are the same. But you should have searched a little more and it would have ran =/
Click to expand...
Click to collapse
I understand that **** happens but honestly my old captivate could always get into recover mode and download mode no matter what, it's extremely frustrating that something changed with the newer models. One of my questions was what caused the brick? I did nothing wrong from what I see and it was running perfectly until I tried to restart/boot into recovery.
Oh and mbc663, thanks but download mode doesn't work at all, nor does recovery obviously.
I can't say exactly what you are doing. Best advice I can do Re download your .zips Flash back to stock GB and try again.
-Pirate said:
About 3 months ago my screen stopped working.. So I take it in and they give me a refurb captivate, looked brand new so I didn't mind. However, when I tried to get into recovery it didn't work, the 3-button-method just wouldn't work at all, period, so I try to get it to work, gets stuck in bootloop.. pretty much every time I try to flash a rom something goes wrong and I get stuck in a bootloop but I can usually get into recovery or download mode because I had CWM.
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
I guess my only option is to usb jig it, but honestly now I'm convinced that the phone is just faulty, I want to run the thing over.
Click to expand...
Click to collapse
Last year, I had issues with my original Cap, and got a "new" one. I learned that the bulk of the Caps going out as replacements are referbs. The one I got was a 1008 build, and does not have 3 button recovery. There are minor differences with each and every Cap that's out there. That's why some have issues with ROM's and some don't, some can over clock like crazy, and some can't at all. My guess is you have a 1008 as well, but that really doesn't matter. You just have a different device and as you seem to already have learned.
It sounds like there is more research you need to do. Even though the devices are a bit different, if you are having issues with ROM's loading, then I would say it's more of a procedure issue, than one with your device.
My procedure, is,
Remove SD/Micro SD
Odin1 Click to Stock JF6, and Master Clear(This will erase EVERYTHING)
Root with One-Click Root
Use Sideload Wonder Machine to install ROM Manager, copy update.zip and 3buttonFix to my SD, then reboot into recovery
Once in recovery I install the 3buttonFix, and install my new ROM
For me this has proven to be a very good method versus going from one ROM to another. The Master Clear cleans EVERYTHING off of your SD, so there is no chance for anything to corrupt your new install. Anytime I read a post of a install gone FUBAR, USUALLY a Flash To Stock/Master Clear (FTS/MC) fixes it
Before using Odin 1 Click, check your devices build number!! If it is higher than 1012, I would NOT recommend using 1 click, there is a higher chance of hard brick on the newer devices
Kangi...if you flash a firmware package without bootloaders, you won't have to do the 3 button fix every time. And if you keep a copy of the update.zip on your pc you don't have to even root, let alone bother with side loading ROM manager.
Cezar has a no boots jf6 and after you run that, you can still use master clear in one click.
Sounds like you got one of the refurbs that is missing the SBL. Have you looked at this thread? http://forum.xda-developers.com/showthread.php?t=1129821
I've not had this problem myself but it sounds like that might help. If I remember reading correctly, once this is flashed it should stick as long as you don't flash any other bootloaders on top of it.
Its not missing the sbl. The sbl it has doesn't respond to key combos. Derpa sherpa moment for samsung I guess?
Rofl yeah...if it was missing the sbl it would be fuggin bricked!
studacris said:
Kangi...if you flash a firmware package without bootloaders, you won't have to do the 3 button fix every time. And if you keep a copy of the update.zip on your pc you don't have to even root, let alone bother with side loading ROM manager.
Cezar has a no boots jf6 and after you run that, you can still use master clear in one click.
Click to expand...
Click to collapse
I know, thanks. I'm such a creature of habit, I started doing it like this a bit over a year ago, and has worked flawlessly for me(just jinxed myself!) so I never saw a reason to "fix what aint broke".
I'll take a look at Cezar's thanks!
Yeah, missing SBL was a poor choice of words. My bad.
kangi26 said:
Last year, I had issues with my original Cap, and got a "new" one. I learned that the bulk of the Caps going out as replacements are referbs. The one I got was a 1008 build, and does not have 3 button recovery. There are minor differences with each and every Cap that's out there. That's why some have issues with ROM's and some don't, some can over clock like crazy, and some can't at all. My guess is you have a 1008 as well, but that really doesn't matter. You just have a different device and as you seem to already have learned.
It sounds like there is more research you need to do. Even though the devices are a bit different, if you are having issues with ROM's loading, then I would say it's more of a procedure issue, than one with your device.
My procedure, is,
Remove SD/Micro SD
Odin1 Click to Stock JF6, and Master Clear(This will erase EVERYTHING)
Root with One-Click Root
Use Sideload Wonder Machine to install ROM Manager, copy update.zip and 3buttonFix to my SD, then reboot into recovery
Once in recovery I install the 3buttonFix, and install my new ROM
For me this has proven to be a very good method versus going from one ROM to another. The Master Clear cleans EVERYTHING off of your SD, so there is no chance for anything to corrupt your new install. Anytime I read a post of a install gone FUBAR, USUALLY a Flash To Stock/Master Clear (FTS/MC) fixes it
Before using Odin 1 Click, check your devices build number!! If it is higher than 1012, I would NOT recommend using 1 click, there is a higher chance of hard brick on the newer devices
Click to expand...
Click to collapse
I didn't think anyone else was going to reply to this thread, whoops.
Thank you for helping me, but I'm still having trouble.
Rom manager doesn't show up in Market, Sideload wonder machine tells me [INSTALL FAILED OLDER SDK] with any apk of Rom manager I find.
kangi26 said:
3buttonFix to my SD, then reboot into recovery
Click to expand...
Click to collapse
How do you reboot into recovery when 3buttonfix hasn't been applied yet?
This sucks and is extremely frustrating, I feel like my captivate is just trolling me.
-Pirate said:
I didn't think anyone else was going to reply to this thread, whoops.
Thank you for helping me, but I'm still having trouble.
Rom manager doesn't show up in Market, Sideload wonder machine tells me [INSTALL FAILED OLDER SDK] with any apk of Rom manager I find.
How do you reboot into recovery when 3buttonfix hasn't been applied yet?
This sucks and is extremely frustrating, I feel like my captivate is just trolling me.
Click to expand...
Click to collapse
When I get home later tonight I'll link you everything you'll need. Again, VERY important, what is your build number? If it's 1012 or higher, don't use Odin 1 click
Sent from a autonomous device
kangi26 said:
When I get home later tonight I'll link you everything you'll need. Again, VERY important, what is your build number? If it's 1012 or higher, don't use Odin 1 click
Sent from a autonomous device
Click to expand...
Click to collapse
Ok, finally got it working, I did exactly what you said, I found the rom manager 3.00.002 or whatever and that worked with sideloader, it took some messing around with but I'm running ICS now, thank you so much man, you've helped me so much, and now I can change roms and keep up to date without worrying about constantly soft-bricking.
As for my build number, I'm not sure, the only thing I see under build number in settings is: "IML74k"
-Pirate said:
Ok, finally got it working, I did exactly what you said, I found the rom manager 3.00.002 or whatever and that worked with sideloader, it took some messing around with but I'm running ICS now, thank you so much man, you've helped me so much, and now I can change roms and keep up to date without worrying about constantly soft-bricking.
As for my build number, I'm not sure, the only thing I see under build number in settings is: "IML74k"
Click to expand...
Click to collapse
The build number is actually under your battery, and looks like 10.06, 10.07, 10.08 and so on. It is the production date
Edit** And as a side note, do NOT try to use the 3buttonFix with a GB ROM, it WILL brick your phone in a really bad way. ONLY use it with 2.1 or 2.2
kangi26 said:
The build number is actually under your battery, and looks like 10.06, 10.07, 10.08 and so on. It is the production date
Edit** And as a side note, do NOT try to use the 3buttonFix with a GB ROM, it WILL brick your phone in a really bad way. ONLY use it with 2.1 or 2.2
Click to expand...
Click to collapse
Is it weird that I don't have a build number? It seems I can't post pictures without a few more posts, maybe this will work: deleted
And thanks for the warning on the 3buttonfix, I'm going to have to read more about bootloaders though, I don't understand what you and studacris were talking about earlier in the thread, haha.
-Pirate said:
Is it weird that I don't have a build number? It seems I can't post pictures without a few more posts, maybe this will work: imgurDOTcom/26sXGl.jpg
And thanks for the warning on the 3buttonfix, I'm going to have to read more about bootloaders though, I don't understand what you and studacris were talking about earlier in the thread, haha.
Click to expand...
Click to collapse
I havent seen that before, there doesnt seem to be a build#
Might want to pull that photo, it's not too good having your IMEI number publicly displayed
kangi26 said:
I havent seen that before, there doesnt seem to be a build#
Might want to pull that photo, it's not too good having your IMEI number publicly displayed
Click to expand...
Click to collapse
Maybe because it's a refurb? and whoops didn't think about that.
-Pirate said:
Maybe because it's a refurb? and whoops didn't think about that.
Click to expand...
Click to collapse
I'm not sure why, mine is a referb, and I have a sticker with mine on it. Ooh well, it is what it is
Sent from a autonomous device
I made a wipe data/factory reset while on CWM Touch (I didn't know about the issues yet) and, of course, it didn't work. So now, everytime I try and flash an Odin ROM (because it doesn't work with the recovery), it gets stuck at data.img/datafs so there's no way I can boot my phone although it does have recovery, download and it gets to the Samsung bootscreen (I flashed a stock ROM).
Has anyone got any ideas on how to fix this? Thanks
Tried clearing cache and data while on recovery? Which rom/kernel are you on?
Sent from my GT-N7000 using XDA
praetorius said:
Tried clearing cache and data while on recovery? Which rom/kernel are you on?
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
I was on AOSP ICS v04 with the infamous AbyssNote 1.2 kernel (but I don't have the same factoryfs problem as the others) with Touch CWM (that's where the problem comes from I believe) and the only problem is that neither Odin nor CWM can access the /data partition. So a wipe doesn't work.
I fear the nearest Samsung service is the way to go for you, mate. Your data partition is corrupted beyond repair.
Believe me, the guys affected with Angelom 1.2 had tried everything, including jigging, jtagging and nothing helped unbrick their phones. It looks like replacing the motherboard is the only solution.
Sorry to have to tell you this.
chasmodo said:
I fear the nearest Samsung service is the way to go for you, mate. Your data partition is corrupted beyond repair.
Believe me, the guys affected with Angelom 1.2 had tried everything, including jigging, jtagging and nothing helped unbrick their phones. It looks like replacing the motherboard is the only solution.
Sorry to have to tell you this.
Click to expand...
Click to collapse
Are you sure? Even though it's never stuck at factoryfs and it only bootloops? Because the problem is I have no service center I can go to so sending it via La Poste (in France) isn't exactly what I'd call safe... Or is there a way to send iut directly to Samsung and get a new one?
Up.............
Since it looks like a partition problem - have you tried using stock .pit file and repartition with ODIN ?
Akiainavas said:
Since it looks like a partition problem - have you tried using stock .pit file and repartition with ODIN ?
Click to expand...
Click to collapse
Yes I did. Well I think imma have to send it to a samsung repair center. How long does it take to get a new Note?
Hi, I had a similar problem and here's what I did. I flashed a stock rom (doesn't have datafs so it worked fine) then it rebooted into recovery which complained about /data partition. So I did wipe data and rebooted.
Hope this helps.
nico53laval said:
Yes I did. Well I think imma have to send it to a samsung repair center. How long does it take to get a new Note?
Click to expand...
Click to collapse
According to warranty agreement:
"Repairs are done as fast as possible, but within 14 days time."
no id agree with what the guys have told you, looks like a service center job, did you just flash this recently or were you one of the users who flashed it weeks back, and youve only just attempted a wipe now??
Just out of curiosity, if people have this kernel installed, can they flash to a diff kernel b4 trying a wipe, or will that not work.
graemeg said:
Just out of curiosity, if people have this kernel installed, can they flash to a diff kernel b4 trying a wipe, or will that not work.
Click to expand...
Click to collapse
You're fine if you don't do any wipes prior to flashing another kernel. However, wipe anything and it's curtains.
chasmodo said:
You're fine if you don't do any wipes prior to flashing another kernel. However, wipe anything and it's curtains.
Click to expand...
Click to collapse
Exactly :/ I was fine for weeks then I wiped before installign another ROM and boom...
dirk271 said:
Hi, I had a similar problem and here's what I did. I flashed a stock rom (doesn't have datafs so it worked fine) then it rebooted into recovery which complained about /data partition. So I did wipe data and rebooted.
Hope this helps.
Click to expand...
Click to collapse
Too late ^^ I sent it to a repair center.. But I don't think it would have worked. I already did a wipe on a tock rom with stock recovery and it worked but the phone still couldn't boot.
Akiainavas said:
According to warranty agreement:
"Repairs are done as fast as possible, but within 14 days time."
Click to expand...
Click to collapse
The problem is that in France the repair centers have an agreement with Samsung but they're not directly related to Samsung so do you think it'll only be 14 days (even though I might neeed a new mobo or a new phone)?
Not sure how youre postal system works there but make sure you get recorded delivery or france similar so you have proof of posting etc.
Also considering the issue ive read most times lads have had a quick turn around, but who knows, depends how fast samsung receive it, i would suggest UP TO 2 weeks, more likely a week, but then it me be 2 week, depends what they have to do to repair it.
I recently took a phone to the o2 shop to be repaired, i received it back via post 4 days later, that was really fast, and im quite lucky here that theres an abundance of walk in repair centres around the uk, it just made me wonder if there one close to you and would it be economical to take it in person, samsung repair shop where i live if ya take your phone in by hand theyll usually say come back in a couple of hours and then they fix it there and then, that would be better for you because you arent messing around with posting then, i know a lot of countries guys dont have that option but i would have thought france and germany would be similar to the uk as they are both quite large mobile manufacturing countries so my fingers are crossed for you that you can find a quick solution.
No idea mate, but you shouldn't wait more than 2 weeks. The repair will take one hour probably, the rest is testing, posting, filling papers etc.
You'll probably have it back after 1 week or so. So let's hope you'll received it fixed as soon as possible.
nico53laval said:
Exactly :/ I was fine for weeks then I wiped before installign another ROM and boom...
Click to expand...
Click to collapse
Oh, I see. Should've read angelom 1.2 thread first.... sorry
Good luck with service.
dirk271 said:
Hi, I had a similar problem and here's what I did. I flashed a stock rom (doesn't have datafs so it worked fine) then it rebooted into recovery which complained about /data partition. So I did wipe data and rebooted.
Hope this helps.
Click to expand...
Click to collapse
what stock rom? which version you used?
Hi all,
The day before yesterday I decided to move from my GNex to the new N4, but my time with it was short, because I have managed to accomplish an incredible feat: brick a N4 just 12hours after purchase :laugh:.
Now, I'm not creating this topic to moan about it, I'm fully aware that bricking is a possibility for every flash, and the phone is already sent back to LG. I just want to tell you all what I did, so we can, possibly, find what I did wrong and help other people to avoid it :highfive:. And a little bit of background, I got Gnex for a year, before that is a G1, with flashing almost become a daily job (not so with the Gnex, as I prefer the stock experience, but still a lot of rom switching and kernel flashing every few months).
My N4, right of the bat, I put it into fastboot unlock, root (the usual thingies). It's still working as normal, but the battery life is not so stellar, so I decided to try franco's kernel. I flashed r53 to my phone, it boot up normally, I feel the performance is too slow compare to stock, so I flashed the latest test version r61, too. It's still working without a hitch, abeit not as smooth as stock.
So I decided to get back to stock. I'm too lazy to do fastboot with stock image, so I download the stock kernel CWM package from this topic, and just to be safe, I flashed faux's kernel reset from here before that. The flashing was succeed, no error, but when I reboot, the phone failed to boot up, just black screen. If I plug it into my computer, it show up as qhsusb_dload, which is a telltale sign of a corrupt internal memory aka definite brick.
To put it short, the sequel is: stock -> unlock -> root -> franco r53 -> franco r61 -> faux reset -> stock kernel flash -> brick.
I guess I did something wrong between the faux reset and stock kernel flashing. can anyone tell me what I did wrong? I did happen to flash wrong kernel build on my Gnex before but the worst I got is a boot loop, not straight up brick like this. And I'm very surprised that a core part of the phone (fastboot) can be corrupted that easy.
And, flash safely :good:
interesting, ive been having problems with my kernel, and used faux reset plenty of times. hopefully someone can chime in for you. Mine is still up and running with faux kernel too
I swear this phone is getting bricked a lot more than a y other nexus
Sent from my Nexus 4 using Tapatalk 2
italia0101 said:
I swear this phone is getting bricked a lot more than a y other nexus
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I swear you are a complete moron.
As for the OP's problem download nexus tool kit , Put the phone in bootloader mode and flash stock factory image.
italia0101 said:
I swear this phone is getting bricked a lot more than a y other nexus
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Are u serious Every phone has a chance of that alot of times
Soon To Be A Nexie
berz said:
I swear you are a complete moron.
As for the OP's problem download nexus tool kit , Put the phone in bootloader mode and flash stock factory image.
Click to expand...
Click to collapse
Yea ... im a complete moron.. iv not seen this " red light " problem with any other Nexus device, have you? of course i know theres a chance of bricking with anything , but iv never seen a nexus device die so easily just by running a benchmark ?!? thats all im saying
i know this isnt the problem the op is having , but its just strange..
either way , maybe chill out a bit before you start pulling out the names yea...
I want to chime in ^_^
I think the kernel reset screwed everything up IMO. I think there was maybe some left over files on the ram disk that didn't get wiped out 100% (I'm assuming you didn't wipe completely, regardless of a kernel reset) and when you flashed stock kernel it couldn't rearrange them correctly and you ended up with a bricked device.
Just my thoughts.
Sent from my Nexus 4 using xda app-developers app
when going back to stock just flash the factory image. it is very easy once you have the files and learn how to do it and always work,
juliano_q said:
when going back to stock just flash the factory image. it is very easy once you have the files and learn how to do it and always work,
Click to expand...
Click to collapse
Bricking Nexus? lol? this is a joke? just reinstall the stock firmware and you're done.
as long as u didnt fscked up the bootloader or the partition scheme then you shall be not affraid and its fairly easy to recover.
Adam
Any chance you flashed N7 kernel? Read somewhere that the kernel partition of N7 has same id as bootloader partition of N4. So what happens is kernel overwrites the bootloader resulting in brick.
Sent from LG Google Nexus 4 using XDA Premium
AdamLange said:
Bricking Nexus? lol? this is a joke? just reinstall the stock firmware and you're done.
as long as u didnt fscked up the bootloader or the partition scheme then you shall be not affraid and its fairly easy to recover.
Adam
Click to expand...
Click to collapse
I still dont have my N4 but I always thought this. Coming from previous devices the only reason Ive seen a true brick is someone screwing up flashing radios or dicking with the boot-loader. I didn't think you could actually brick a device with ROMS/Kernels.
linh1987 said:
Hi all,
The day before yesterday I decided to move from my GNex to the new N4, but my time with it was short, because I have managed to accomplish an incredible feat: brick a N4 just 12hours after purchase :laugh:.
Click to expand...
Click to collapse
Power off. Hold "volume down" and press power button. This should get you to the bootloader. If it does, your phone is not bricked and there's loads of info on here to put it right again (stock factory image would be my first call here). If it doesn't work, I'd be tempted to remove the battery (IIRC, quite easy once you remove the screws at the bottom) and repeat the above instructions. (if you can get to the bootloader one way or another, your phone is most certainly not bricked!)
If this doesn't work, it's probably dead and you'll need to send back.
Daern
---------- Post added at 01:34 PM ---------- Previous post was at 01:27 PM ----------
berz said:
I swear you are a complete moron.
Click to expand...
Click to collapse
Didn't your mother ever teach you - "If you can't say anything nice, say nothing at all"?
This is not a site for trolling. Please go away.
I flashed different kernels many many times.
Never a problem.
OP should check for human error instead of blaming the device.
Sent from my Nexus 4 using xda premium
atulalvenkar said:
Any chance you flashed N7 kernel? Read somewhere that the kernel partition of N7 has same id as bootloader partition of N4. So what happens is kernel overwrites the bootloader resulting in brick.
Sent from LG Google Nexus 4 using XDA Premium
Click to expand...
Click to collapse
Sorry but i don't know what are you talking about ? what the same ID as bootloader? erm?
partition name in case of bootloader is bootloader, for case of kernel is boot
Adam
linh1987 said:
Hi all,
The day before yesterday I decided to move from my GNex to the new N4, but my time with it was short, because I have managed to accomplish an incredible feat: brick a N4 just 12hours after purchase :laugh:.
Now, I'm not creating this topic to moan about it, I'm fully aware that bricking is a possibility for every flash, and the phone is already sent back to LG. I just want to tell you all what I did, so we can, possibly, find what I did wrong and help other people to avoid it :highfive:. And a little bit of background, I got Gnex for a year, before that is a G1, with flashing almost become a daily job (not so with the Gnex, as I prefer the stock experience, but still a lot of rom switching and kernel flashing every few months).
My N4, right of the bat, I put it into fastboot unlock, root (the usual thingies). It's still working as normal, but the battery life is not so stellar, so I decided to try franco's kernel. I flashed r53 to my phone, it boot up normally, I feel the performance is too slow compare to stock, so I flashed the latest test version r61, too. It's still working without a hitch, abeit not as smooth as stock.
So I decided to get back to stock. I'm too lazy to do fastboot with stock image, so I download the stock kernel CWM package from this topic, and just to be safe, I flashed faux's kernel reset from here before that. The flashing was succeed, no error, but when I reboot, the phone failed to boot up, just black screen. If I plug it into my computer, it show up as qhsusb_dload, which is a telltale sign of a corrupt internal memory aka definite brick.
To put it short, the sequel is: stock -> unlock -> root -> franco r53 -> franco r61 -> faux reset -> stock kernel flash -> brick.
I guess I did something wrong between the faux reset and stock kernel flashing. can anyone tell me what I did wrong? I did happen to flash wrong kernel build on my Gnex before but the worst I got is a boot loop, not straight up brick like this. And I'm very surprised that a core part of the phone (fastboot) can be corrupted that easy.
And, flash safely :good:
Click to expand...
Click to collapse
If you took the same amount of time to search that you took to write this terrible OP you would have already fixed your phone....
tweaked said:
If you took the same amount of time to search that you took to write this terrible OP you would have already fixed your phone....
Click to expand...
Click to collapse
Hey tweaked, thanks for your contribution, but if you take 5 secs to search for a black screen issue with qhsusb_dload show up in windows, you will know that I went to a dead end.
@all: yes it's 100% my fault, I just double check and I DID flash grouper (aka N7) kernel to my N4, but I just feel it's so much easier to flash N7 kernel to N4 without any error. And again, I just want to repeat that I'm not moaning about it, it's totally my fault. I just want to help other people to avoid it :highfive:
atulalvenkar said:
Any chance you flashed N7 kernel? Read somewhere that the kernel partition of N7 has same id as bootloader partition of N4. So what happens is kernel overwrites the bootloader resulting in brick.
Sent from LG Google Nexus 4 using XDA Premium
Click to expand...
Click to collapse
Hey atulalvenkar, yes, I just did what you say. How stupid I'm. Guess we learn new thing every day
linh1987 said:
Hey atulalvenkar, yes, I just did what you say. How stupid I'm. Guess we learn new thing every day
Click to expand...
Click to collapse
You are the first person I heard that flashed a wrong KERNEL.
Congratz.
Sent from my Nexus 4 using xda premium
linh1987 said:
Hey atulalvenkar, yes, I just did what you say. How stupid I'm. Guess we learn new thing every day
Click to expand...
Click to collapse
Saw couple of posts on reddit where many people did the same thing. The problem is franco develops for both N7 and N4 and his XDA thread subject doesn't have any indication of the device. Because of this it's easy to get pointed to the wrong thread and download wrong kernel.
My phone bricked spontaneously. I had installed CM 10.1, with the stock kernel, about 12 hours earlier and was actually browsing facebook when the phone spontaneously rebooted. I could get into fastboot, but no matter what I tried, I couldn't flash a stable recovery or full image. Constant boot loops with the occasional successful system boot, only to reboot within a few seconds.. starting the whole process over again.
Flashed and formatted every accessible partition, followed every "how to" I could find. Absolutely no success. Luckily Google sent me a replacement and I had a new phone in 2 days. Running the same CM 10.1/stock kernel now, no issues.
My first phone (a Rev_11) always ran somewhat hot, and the battery wouldn't last a day. The replacement phone (also a Rev_11) runs much cooler and the battery lasts for 2 days easy, with the exact same software. I'm thinking the old phone just somehow toasted itself. Just speculation. Oh, the old phone was also a "slow" binned CPU.
Anyway, the point of my story is that is ISN'T entirely true that the ability to boot into bootloader/fastboot will guarantee you success when trying to resurrect a dead phone.
Hello everyone, thanks for taking your time and reading this.
I've owned a Samsung Galaxy S GT-i9000 for about two years now. This phone is not my primary phone, as I just use it as a secondary phone for different apps/backup, most of the times the phone is turned off.
But a few days ago, I turned the phone on, and once the homescreen had loaded, around 20-30 seconds later, the phone will freeze, and there's nothing else you can do other than take the battery out to turn it off.
A few details about the phone: the phone has never been flashed, and the OS has never been touched. It's basically at stock, but the only thing I remember is updating the official firmware through the Samsung link in the settings. The phone has never been modded, and that's what bugs me the most. (I've never had experience with 'modding' phones with custom ROMS and such)
So, after sitting at home all day looking for a fix, I couldn't find anyone else in my situation. There are a few similar situations, but I am yet to find something that replicates my problem exactly.
I've also tried rebooting the phone in many different ways, for example, taking out the memory card, then taking out the sim card, then taking them both out completely.
That's when I found a link which gave me information on how to factory reset the device. Since nothing else was working, I decided to go for it.
I held the VOLUME UP button + the HOME button, and hit the power button and got the menu up.
The menu works fine, I was flicking through the options for 10 whole minutes just to check if it freezes or not, and it works perfectly fine.
So then I factory reset the phone, wiped the system cache, and I also formatted the internal SD card.
Still, the problem persists. This time, the phone will reboot for a little while longer, since I expect the system files are getting set up, then it asks for the language, and before I can hit English, it freezes, and the screen stays like that until the battery is dead. All the hardware buttons don't do anything, it's basically fully dead with the screen still on the OS menu.
I was wondering if anyone knows what I should do?
I can provide more information if needed, and I can even upload a video to YouTube if you want a better aspect of the problem.
Any help is appreciated, thanks.
is it i9000 or 9100?
Sent from my GT-I9000 using xda premium
compacity said:
is it i9000 or 9100?
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Ah, sorry, got the title completely messed up there.
Yes it's the GT-i9000 and I think it had Froyo 2.2.1, forgot to include that in the main text.
Could try Rooting the phone and wiping all options in Recovery and Reboot
or
Could be that something maybe corrupted which is halting the system
Upload a video so that we can offer better advice
Which Rom / Firmware are you using?
Last option.
Would Recommend Downloading Rom (whichever you choose) and go from there....
Major UPDATE:
Okay, so after sticking at it the whole day and trying to get a better understanding of this situation, I've managed to work around the problem slightly. It's not fixed yet, though.
So after the screen had frozen for the (insert number here)th time, the battery was starting to go empty, so I stuck it on charge, but I forgot that I had left the frozen screen on (currently frozen on the 'Language Select' set up menu).
After about 20 minutes, the phone vibrated and a little message popped up, and it said that 'the process Soundhound.com.xxx.xxx was force closed', or something along the lines. I can't remember fully because it popped up for only around 4 seconds and disappeared.
As soon as I saw that, I quickly went to the application settings and deleted all of the soundhound cache/data and then removed the app completely. After that I thought it was fixed for sure, so I was messing around with the phone and using different apps to see if it freezes again, and it didn't.
But I had to restart the phone to see if the freeze issues happened again, and yep, it was there again, this time the same as the first issue, where it used to freeze up in the home screen. AND, I let it sit on the frozen screen for 15 minutes and it was that SAME soundhound app that got force closed, so once it got out of the frozen state, I quickly went to the application settings and the app was still there, it was like I didn't even delete it?
This leads to my new problem, the so called 'hard factory wipe/reset' doesn't actually reset EVERYTHING. As seen in my other post: http://forum.xda-developers.com/showthread.php?t=2305825
Now I'm completely confused as to what I should do.
I've pretty much tried everything, and i'm sure a FULL hard reset where EVERYTHING gets wiped out might just fix it? The thing is though, I don't know how? I've been trying to fix this phone for about 7 hours straight now.
My opinion Flash a Stock Rom or what ever you wish and then Root it...
If selling it just dont bother with Rooting it.
As you say you have been at it for Several hours and flashing takes less than an hour even for a newbie if following the procedure correctly
As going by what you say it seems that files are messed up on the phone and better to start fresh
ywasaf acquitted
EwOkie said:
My opinion Flash a Stock Rom or what ever you wish and then Root it...
If selling it just dont bother with Rooting it.
As you say you have been at it for Several hours and flashing takes less than an hour even for a newbie if following the procedure correctly
As going by what you say it seems that files are messed up on the phone and better to start fresh
Click to expand...
Click to collapse
Is there a legit way to flash it, maybe through Samsungs website? I don't want to mess around with custom files, as I would like to keep everything clean.
Oh, and also, I just went through the media files and found some of my old pictures too. So for some reason, the 'format internal SD' option in the recovery menu isn't working.
If I flash it, will I have to flash it to Froyo 2.2.1 which it is currently in right now?
Here's information I found on the 'About phone' menu:
Kernel version:
2.6.32.9
[email protected] # 1
Build number:
FROYO.XXJPY
Baseband version:
i9000XXJPY
Thanks for all the help so far.
Legit way your on XDA!
Flash a Stock 2.3.6 (Clean) which is the same as Samsung Site its in my How to Guide if you wish to follow it
Its the exact same Rom just not on there Site
EwOkie said:
Legit way your on XDA!
Flash a Stock 2.3.6 (Clean) which is the same as Samsung Site its in my How to Guide if you wish to follow it
Its the exact same Rom just not on there Site
Click to expand...
Click to collapse
Thanks.
Briefly read your guide, and it's all mind boggling to a newbie like me :silly: lol
I might just have to flash it, because this problem is getting a little bit annoying now.
Which parts of your guide should I follow exactly? And shouldn't I be sticking Froyo 2.2.1 back in? Won't a newer firmware (such as the 2.3.6) make the phone slower/drain more battery than usual?
Oh and one last thing, what's the difference between rooting and flashing a phone? Cheers.
Rooting briefly means :
Giving yourself root access to system files and the ability to change things that normally are marked read only
This allows you to change all kinds of things that normally you wouldn't be able to
Flashing : Erm.. Flashing a new Rom on your Phone or the process of over-writing your internal memory
2.3.6 will be ok for you if you wish to stay just Stock on your phone.
Plus the fact if you wish to move to another Rom later on its just a matter of Rooting the Phone and installing the Custom Rom
Just follow guide from the : HOW TO GUIDE : TUTORIAL TO FLASH 2.3.6 JVU + ROOT BEFORE INSTALLING CUSTOM ROM
and you will be ok.
EwOkie said:
Rooting briefly means :
Giving yourself root access to system files and the ability to change things that normally are marked read only
This allows you to change all kinds of things that normally you wouldn't be able to
Flashing : Erm.. Flashing a new Rom on your Phone or the process of over-writing your internal memory
2.3.6 will be ok for you if you wish to stay just Stock on your phone.
Plus the fact if you wish to move to another Rom later on its just a matter of Rooting the Phone and installing the Custom Rom
Just follow guide from the : HOW TO GUIDE : TUTORIAL TO FLASH 2.3.6 JVU + ROOT BEFORE INSTALLING CUSTOM ROM
and you will be ok.
Click to expand...
Click to collapse
So the 2.3.6 Firmware you provide, is that known a 'custom firmware'?
I've been searching for YouTube videos with people explaining how to flash, but all the videos sound like they're speaking about some rocket science sh** lol
Now I'm super confused, some guy on YouTube is flashing to 2.3.6 JVT while you're doing JVU, I don't even know what that means haha
I just don't want to brick the phone and make it completely dead, that's why I'm just making sure I understand the basics before I go ahead with it, sorry if I'm starting to sound annoying lol
You wont brick it if you follow it correctly...
2.3.6 JVU is the basis for all custom roms been flashed unless stated otherwise by Rom Developers.
As its basically a stock 2.3.6 then when you want to flash another Rom its just a matter of Rooting the 2.3.6
EwOkie said:
You wont brick it if you follow it correctly...
2.3.6 JVU is the basis for all custom roms been flashed unless stated otherwise by Rom Developers.
As its basically a stock 2.3.6 then when you want to flash another Rom its just a matter of Rooting the 2.3.6
Click to expand...
Click to collapse
Ah, okay.
Well, I'm in the process of downloading your files, THANKS for ALL the help you've given so far, sir!
I'll flash once all the files are downloaded. By the way, does 2.3.6 have Google Play store, and not the old Andropid Market?
I hope I can get this done before I head off to sleep in a few hours, been a very long day haha
I'll let you know of the results, cheers and have a good day sir.
No problem hope it all works out for you :good:
Not sure if Google Play is on it as its 2.3.6 Stock ...just upgrade it if possible
EwOkie said:
No problem hope it all works out for you :good:
Not sure if Google Play is on it as its 2.3.6 Stock ...just upgrade it if possible
Click to expand...
Click to collapse
why is it i cant see ur online status? is my app ...... nevermind that.
Sent from my GT-I9000 using xda premium
---------- Post added at 05:14 AM ---------- Previous post was at 05:13 AM ----------
f2k8 said:
Ah, okay.
Well, I'm in the process of downloading your files, THANKS for ALL the help you've given so far, sir!
I'll flash once all the files are downloaded. By the way, does 2.3.6 have Google Play store, and not the old Andropid Market?
I hope I can get this done before I head off to sleep in a few hours, been a very long day haha
I'll let you know of the results, cheers and have a good day sir.
Click to expand...
Click to collapse
GOOD LUCK N MAY LADY LUCK ON UR SIDE WHILE FLASHING
Sent from my GT-I9000 using xda premium
EwOkie said:
No problem hope it all works out for you :good:
Not sure if Google Play is on it as its 2.3.6 Stock ...just upgrade it if possible
Click to expand...
Click to collapse
Back again, haha.
I was just wondering, did you say I should root or not? As rooting it seems like a bit of a hassle? Plus, it says that I should install a custom rom zip file if I decide to root it, but I don't have one? I am using your 2.3.6 which was in your Odin Files download link, right?
So if I root, what do I do exactly?
compacity said:
why is it i cant see ur online status? is my app ...... nevermind that.
Click to expand...
Click to collapse
Hiding from the Tax Man :laugh:
Rooting takes 15 seconds to do
EwOkie said:
Hiding from the Tax Man :laugh:
Rooting takes 15 seconds to do
Click to expand...
Click to collapse
Okay, so I've rooted it also now, and unplugged the USB.
Now it's restarted, and the language set-up page is there, and guess what? .. It froze again :|
Exactly the same way before I flashed it :crying: :crying: lol
I actually feel like crying right now haha, I think the phone may be completely dead? Something is seriously corrupt with it I'm guessing?
I've never dropped it, or accidentally dropped liquid on it or anything like that.
I have absolutely no idea what to do now. Sigh.
Thanks for your help either way though.
can you upload a video on whats happening?
EwOkie said:
can you upload a video on whats happening?
Click to expand...
Click to collapse
how bout activate repartition?
Sent from my GT-I9000 using xda premium
---------- Post added at 05:49 AM ---------- Previous post was at 05:48 AM ----------
EwOkie said:
Hiding from the Tax Man :laugh:
Rooting takes 15 seconds to do
Click to expand...
Click to collapse
so thats why, i thought my app got error.
Sent from my GT-I9000 using xda premium