Related
I recently figured out how to use Odin with my vibrant. I bricked my phone using Eugene's fro yo rom that doesn't brick your phone. I flash stock witch fixed had issues with my phone and tried flashing a new rom using odin. I stumbled upon cognition 2.2 beta rom. Not to my knowing it is a captivate rom. Now when i boot it has the captivate boot on my vibrant. I tried to flash the stock vibrant rom doesnt works i need csc.tar and phone.tar to have a completely fixed phone please help
Bump! I am have the same problem. Any help would be greatly appreciated. Thanks everyone!
bump same as well
the same problem
ask for help
http://forum.xda-developers.com/showthread.php?t=734475
movieaddict said:
http://forum.xda-developers.com/showthread.php?t=734475
Click to expand...
Click to collapse
Thank u for your post，but that dosen't work.
Exactly our problem is the boot logo has been changed.We need the CSC.TAR for vibrant not a firmware.
I've spent the last 2 days trying to fix my mistake. I have the GS2 ATT version, and I didn't realise there was a difference between that and the GTI9100 S2.
I wanted to give some tips I learned on how to recover your phone if you make this mistake.
First, here are some posts you'll want to look at:
http://forum.xda-developers.com/showthread.php?t=1286432 - Stock firwmware
http://forum.xda-developers.com/showthread.php?t=1285823 - Clockworkmod for the ATT
http://forum.xda-developers.com/showthread.php?t=1286192 - Cyanogenmod for our phones.
Using Odin and the stock firmware, you can recover your phone to a 95% working state. Once I got my stock firmware on there, I found that while making calls my phone made no sound, and the mic didn't work. The mic did work when I wasn't making calls though.
I reflashed the modem.bin file found on the stock firmware, not sure if its required but that is what I did first. Then, I unpacked the rooted stock firmware, and flashed JUST THE zImage file. After doing this, I rebooted, and my calls were working again.
After that, I installed the correct version of Clockworkmod, and then CM7 nightly. Now everything seems to be running great on my phone.
Hope this helps someone out there,
-Orbital
Good job thanx man.
Sent from my SAMSUNG-SGH-I777 using XDA App
Been awhile since I messed w/ android. I forgot about the different models myself until I realized I was spending half my day in the wrong section
Could you please explain the flashing of the CM Nightlies process to me? I can flash the signed base build but can't flash any of the added on nightlies...
Alucardis666 said:
Could you please explain the flashing of the CM Nightlies process to me? I can flash the signed base build but can't flash any of the added on nightlies...
Click to expand...
Click to collapse
In other words I can't flash the nightly builds like the latest 77 or any others for that matter.
Alucardis666 said:
In other words I can't flash the nightly builds like the latest 77 or any others for that matter.
Click to expand...
Click to collapse
Those are NOT for our version of the GS2, International only. Our version is here in the development forum.
Sent from my SGH-I777 using xda premium
Yes, it will return a status error 7 which means it's unmatched. Ask me how I know. I flashed international roms last night and used this fix to get me good again.
I flashed a KE7 I9100 build to my I777 and saw no ill effects other than incorrect capacitive button mapping. Which build did you flash? Did you make sure to wipe data factory reset afterwards.
So you are saying that you wre able to flash Euro ROMS and your phone booted just fine? Mine didnt boot at all. Did you flash the KERNEL for ATT on top of it ?
connexion2005 said:
I flashed a KE7 I9100 build to my I777 and saw no ill effects other than incorrect capacitive button mapping. Which build did you flash? Did you make sure to wipe data factory reset afterwards.
Click to expand...
Click to collapse
The simple thing would be to change out the sec_touchkey.kl with rootexplorer and take the sec_touchkey from system/usr/keylayout should fix the i9100 rom to work with the i777. Seeing as how this worked for the Captivate *i897* for jvr, jvs, and jvt darkyrom releases and I would assume that it would work.
daraj said:
So you are saying that you wre able to flash Euro ROMS and your phone booted just fine? Mine didnt boot at all. Did you flash the KERNEL for ATT on top of it ?
Click to expand...
Click to collapse
Personally I would think that you had a bad flash? Did you flash through Odin or CWM? From what I have been reading the gb bootloaders between the i777 and i9100 are different and I can see if you used a custom i9100 rom flashing via cwm could cause that. Since I am not too sure on the sgs2 if the differences between the euro models versus the carrier locked, the Kernel will not fix the button mapping, I learned this with the captivate when I switched over to using DarkyRom jvr and jvs builds since they were the most stable of GB for the i897 captivate. Plus if you are going to run a i9100 rom, I am sure the modem will not work with the att kernel. Especially if the situation with the cappy is any indication that att kernel needs att modem and i9000 kernel needs i9000 modem. I will be able to know more as soon as I get my i777 tomorrow.
HTH,
Charlie
Does anyone know how to remove the i9100 splash screen?
Google Talk Video does not work after updating to CyanogenMod 7 and back to stock rom. Any suggestion ?
spbluffmaster said:
Google Talk Video does not work after updating to CyanogenMod 7 and back to stock rom. Any suggestion ?
Click to expand...
Click to collapse
wipe data/factory reset
tried that three times... didnt help..
Did the same thing and made it back to ATT version and running CM7 for now. Still have an I9100 boot screen with a yellow logo. How do I get rid of that?
SO why do you say this flashes you back to 95%? Is there no 100% return to stock fix?
DiscipleDOC said:
Does anyone know how to remove the i9100 splash screen?
Click to expand...
Click to collapse
Speedy350z said:
Did the same thing and made it back to ATT version and running CM7 for now. Still have an I9100 boot screen with a yellow logo. How do I get rid of that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1311975
re: get rid of i9100 boot logo
Speedy350z said:
Did the same thing and made it back to ATT version and running CM7 for now. Still have an I9100 boot screen with a yellow logo. How do I get rid of that?
Click to expand...
Click to collapse
Use a download mode jig or flash entropy 512's stock TAR kernel with Odin from the link below.
http://forum.xda-developers.com/show....php?t=1286432
Good luck!
highaltitude said:
SO why do you say this flashes you back to 95%? Is there no 100% return to stock fix?
Click to expand...
Click to collapse
Some people need to wipe or also flash the modem for 100%.
Also, people who managed to flash a bootloader without hardbricking can't get back to stock with any confirmed method.
I have posted bootloader dumps, but no one has flashed them and I'm not messing with trying to flash them. They are dumps from my device and that is the ONLY guarantee I provide for them.
Entropy512 said:
Some people need to wipe or also flash the modem for 100%.
Also, people who managed to flash a bootloader without hardbricking can't get back to stock with any confirmed method.
I have posted bootloader dumps, but no one has flashed them and I'm not messing with trying to flash them. They are dumps from my device and that is the ONLY guarantee I provide for them.
Click to expand...
Click to collapse
i messed up and flashed an i9100 rom and am having the call prob u described. can i just flash the modem or stock rooted kernel and be back to 100%? if so do i use odin and do i need to check the box for repartition or anything like that? thx in advance!!!
My Galaxy Player bricked since I flashed "CF-ROOT for GT-I9000"(Because I selected the wrong file)
The screen touch response is reversed and the touch button doesn't work!
Please help me what to do!!!
The problem was solved!! Thanks Samwes's help
error01671 said:
My Galaxy Player bricked since I flashed "CF-ROOT for GT-I9000"(Because I selected the wrong file)
The screen touch response is reversed and the touch button doesn't work!
Please help me what to do!!!
Click to expand...
Click to collapse
Wait...so you flashed an I9000 kernel and it still booted? Maybe I will try investigating if we could just port kernels from the galaxy s phones.
But anyway..just boot into download mode and reflash one of the custom kernels for the 4.0.
Sent using Tapatalk
klin1344 said:
Wait...so you flashed an I9000 kernel and it still booted? Maybe I will try investigating if we could just port kernels from the galaxy s phones.
But anyway..just boot into download mode and reflash one of the custom kernels for the 4.0.
Sent using Tapatalk
Click to expand...
Click to collapse
I flashed STeVEs-3.0-EU kernel but it didn't fix my problem!!
I will post video and you can see the problem on my device.
I think a dev should make a sticky to bricks. They are coming up too often now.
Also if it booted, it's not bricked.
Chris4evernoob said:
I think a dev should make a sticky to bricks. They are coming up too often now.
Also if it booted, it's not bricked.
Click to expand...
Click to collapse
But I flash any stock rom or custom rom,even any custom kernel,can't fix my device.
Why would you flash a i9000 kernel on a YP-G1 ? What kernel did you flash, we're going to need that kernel to see what happened!
pmdisawesome said:
Why would you flash a i9000 kernel on a YP-G1 ? What kernel did you flash, we're going to need that kernel to see what happened!
Click to expand...
Click to collapse
I downloaded "CF-Root-JP6-v1.2-Busybox-1.17.1.zip"from http://forum.xda-developers.com/showthread.php?t=788108
The file which I prepared for my i9000,but when I' m going to flash my YP-G1 kernel,I selected the wrong file.
get odin, stock firmware, and flash the stock firmware with odin
I have the same problem since I've flashed a kernel for the Galaxy S.
My Galaxy player has not booted.
I have flashed Steves ROM and since that I have the same problems.
I've found so far no solution.
The flash of the stock firmware did not help.
I have also tested other ROMS.
Did you're player run 2.3 or 2.2 stock, because that would make a difference. If it ran 2.2 then therea you're problem isolated.
Infact I just noticed you said touch button, so are you sure its not US?
Sent from my YP-G70
Seresta said:
get odin, stock firmware, and flash the stock firmware with odin
Click to expand...
Click to collapse
I tried,but it doesn't work.
Samwes said:
Did you're player run 2.3 or 2.2 stock, because that would make a difference. If it ran 2.2 then therea you're problem isolated.
Infact I just noticed you said touch button, so are you sure its not US?
Sent from my YP-G70
Click to expand...
Click to collapse
The touch buttons that I mean is menu button and back button,not home button.
And I will try 2.2 stock,thanks.(I already ran 2.3 stock.)
error01671 said:
The touch buttons that I mean is menu button and back button,not home button.
And I will try 2.2 stock,thanks.(I already ran 2.3 stock.)
Click to expand...
Click to collapse
Which stock rom did you try?
zaclimon said:
Which stock rom did you try?
Click to expand...
Click to collapse
2.3.6 stock rom
Samwes said:
Did you're player run 2.3 or 2.2 stock, because that would make a difference. If it ran 2.2 then therea you're problem isolated.
Infact I just noticed you said touch button, so are you sure its not US?
Sent from my YP-G70
Click to expand...
Click to collapse
I just flash 2.2.1 stock rom and it fix my device!!! Thank you very much!
Without your advice,I won't flash into 2.2!(Because 2.3 is much better!)
Can you send me the link?
Gigadroid said:
Can you send me the link?
Click to expand...
Click to collapse
Here is the 2.2.1(INTL)stock rom download link : http://dl.dropbox.com/u/60441441/G1ZSKC5-REV01-PDA-low-CL976041.tar.zip
The link is from http://forum.xda-developers.com/showthread.php?t=1531850
Thank you.
I'll try it.
EDIT: Hooray, it worked.
Yes in this case when flashing with odin 2.2.1 rom is better at resolving problems then 2.3.6.
I have been trying to flash NX-Kernel_v1.1.0 to my phone which is running Rootbox-JB-i9300-v3.9.1.
I have noticed that the file I am trying to flash is not a .tar, which is what I am use to, but a .zip.
When i use TWRP to attempt to flash it boots into download mode and does nothing.
I have also tried using odin and mobile odin but i think because its a .zip odin cannot even see it.
The thread is linked below. I have searched it and people seem to be saying that it is possible to flash with a recovery and odin/mobile odin, all of these i have tried.
Can someone please tell me what i am doing wrong!?!?
http://forum.xda-developers.com/showthread.php?t=2192893
just flash it from recovery like a rom
is the rom based on CM10.1?
Tried
Glebun said:
just flash it from recovery like a rom
is the rom based on CM10.1?
Click to expand...
Click to collapse
I have tried flashing from tw recovery it does not boot into system from there.
The rom is a AOKP base.
guspop said:
I have tried flashing from tw recovery it does not boot into system from there.
The rom is a AOKP base.
Click to expand...
Click to collapse
Why would a kernel made for galaxy note or note 2 work on a galaxy s3?
There are sure to be differences which will make it not boot.
Sent from my GT-I9300 using xda premium
oops, didn't see that. Of course it won't boot, you're lucky if you didn't kill it
First off, kernels cannot kill phones. Only corrupted or mismatched or blank boot loaders can.
ficti0n851 said:
Why would a kernel made for galaxy note or note 2 work on a galaxy s3?
There are sure to be differences which will make it not boot.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
b-eock said:
First off, kernels cannot kill phones. Only corrupted or mismatched or blank boot loaders can.
Click to expand...
Click to collapse
Wow thank you I cannot believe I didn't realise it was for the note.
b-eock said:
First off, kernels cannot kill phones. Only corrupted or mismatched or blank boot loaders can.
Click to expand...
Click to collapse
Hate to tell you it can. I bricked an S3 by accidently flashing an S2 kernel to it which bricked the device to the point that a jig would not even revive it.
That makes no sense if you think of the booting process... I mean crazy things happen. But a kernel should never fully brick a device...
guspop said:
I have been trying to flash NX-Kernel_v1.1.0 to my phone which is running Rootbox-JB-i9300-v3.9.1.
I have noticed that the file I am trying to flash is not a .tar, which is what I am use to, but a .zip.
When i use TWRP to attempt to flash it boots into download mode and does nothing.
I have also tried using odin and mobile odin but i think because its a .zip odin cannot even see it.
The thread is linked below. I have searched it and people seem to be saying that it is possible to flash with a recovery and odin/mobile odin, all of these i have tried.
Can someone please tell me what i am doing wrong!?!?
http://forum.xda-developers.com/showthread.php?t=2192893
Click to expand...
Click to collapse
Flash it w CWM. Should work
Sent from my SPH-L710 using xda app-developers app
b-eock said:
That makes no sense if you think of the booting process... I mean crazy things happen. But a kernel should never fully brick a device...
Click to expand...
Click to collapse
It does if the kernel is not for the proper chip set. Like a kernel for a qualcom chip flashed on an eyxnos chip.
jorv976 said:
Flash it w CWM. Should work
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
the issue has already been found. The kernel is for a different device.
It should only result in a soft brick... Bootloaders are the first to come (primary then secondary. Secondary passing the booting process off to the kernel. Recovery is in the kernel while DL mode is in the boot loaders.) Oh well. I make sure I don't do stuff like that. I'm really OCD and paranoid about stuff being just right.
b-eock said:
It should only result in a soft brick... Bootloaders are the first to come (primary then secondary. Secondary passing the booting process off to the kernel. Recovery is in the kernel while DL mode is in the boot loaders.) Oh well. I make sure I don't do stuff like that. I'm really OCD and paranoid about stuff being just right.
Click to expand...
Click to collapse
\Yeah thats what I thought as well. I was just rushing far more then I normally do and downloaded the same rom for both the S2 for my brother and my S3 and flashed the wrong one to mine. Boy was I not happy. Spent 3 days with some of the most talented developers here and we all agreed that jtag was the only hope.
Okay so here's the low down. I recently rooted my sprint note 3 via CF auto root method. Shortly after I experienced random reboots. I found out through system tuner app that only one core was online. So I ticked "Force all cores online on boot complete", which seemed to fix the problem. Now, whenever I play games I set cpu governor to performance and OC to like 2.7something.. But halfway through my gamei realize the cpu gets set back down to a lower frequency. Also experiencing lag in games (which IMHO should not be there.). Does anyone have any ideas as to what may be causing this problem?Any help is greatly appreciated.
-Matthew
I would try going back to stock, that's usually what I start with.
Sent from my SM-N900P using XDA Premium 4 mobile app
How would I go about that. I'm new to rooting so I apologize. But I have one backup from when I was freshly stock but rooted. Or do I need to do a full unroot/ factory reset? If so how?
To go back to stock rom easiest way would be via odin. U will need
1.odin software.
2.usb driver
3.stock rom files (modem, pda, csc files)
Do say if you need more detailed instructions.
I would appreciate it. I have Odin and the USB drivers already.
Ok so u just need stock files to flash..
. And the problem is?
Is that mj4.tar? I need a step by step. Odin tar then what?
mscooksey21 said:
I would appreciate it. I have Odin and the USB drivers already.
Click to expand...
Click to collapse
What kernal are u using?
Sent from Sprint Galaxy Note 3 using Tapatalk
I was using beastmode. Do I need to flash stock mj4 kernel as well?
insane209 said:
What kernal are u using?
Sent from Sprint Galaxy Note 3 using Tapatalk
Click to expand...
Click to collapse
Also... I tried flashing the stock mj4 firmware and reboooted and was stuck in a boot loop.. to make things worse, I wiped system and data.. so I think I messed up big time.
mscooksey21 said:
I was using beastmode. Do I need to flash stock mj4 kernel as well?
Click to expand...
Click to collapse
mscooksey21 said:
Also... I tried flashing the stock mj4 firmware and reboooted and was stuck in a boot loop.. to make things worse, I wiped system and data.. so I think I messed up big time.
Click to expand...
Click to collapse
Beast kernal is unstable at oc at times, i used lean kernal believe me its more stable at 2.7, and how did u flash the stock firmware using odin?
Sent from Sprint Galaxy Note 3 using Tapatalk
insane209 said:
Beast kernal is unstable at oc at times, i used lean kernal believe me its more stable at 2.7, and how did u flash the stock firmware using odin?
Sent from Sprint Galaxy Note 3 using Tapatalk
Click to expand...
Click to collapse
yes I did it through odin amd I will flash lean kernel after the mj4 then. Wish me luck!
mscooksey21 said:
yes I did it through odin amd I will flash lean kernel after the mj4 then. Wish me luck!
Click to expand...
Click to collapse
Do steps 4-6: http://forum.xda-developers.com/showthread.php?t=2514434
Lean kernal direct link 1.3 most stable on oc 2.7ghz:
http://androtransfer.com/get.php?p=imoseyon/hlte-others/lk_hltespr-v1.3.zip
insane209 said:
Do steps 4-6: http://forum.xda-developers.com/showthread.php?t=2514434
Lean kernal direct link 1.3 most stable on oc 2.7ghz:
http://androtransfer.com/get.php?p=imoseyon/hlte-others/lk_hltespr-v1.3.zip
Click to expand...
Click to collapse
okay I did that but im still in a boot loop. I think I might need to recover my rom? Because the baseband has nothing to do with the rom correct?
mscooksey21 said:
okay I did that but im still in a boot loop. I think I might need to recover my rom? Because the baseband has nothing to do with the rom correct?
Click to expand...
Click to collapse
Why dnt u flash the jellybomb rom?..its a great rom with alot of features...flash that and flash the lean kernal
Sent from Sprint Galaxy Note 3 using Tapatalk
insane209 said:
Why dnt u flash the jellybomb rom?..its a great rom with alot of features...flash that and flash the lean kernal
Sent from Sprint Galaxy Note 3 using Tapatalk
Click to expand...
Click to collapse
Ok I just flashed it in stock recovery but im still getting a loop. Is my phone unrooted? Did I need to wipe before I know I should know these things by now but I feel like theres a lot to it that I just dont. So. I could flash twrp in odin then try the flash again? Or do I need to root it again?
mscooksey21 said:
Ok I just flashed it in stock recovery but im still getting a loop. Is my phone unrooted? Did I need to wipe before I know I should know these things by now but I feel like theres a lot to it that I just dont. So. I could flash twrp in odin then try the flash again? Or do I need to root it again?
Click to expand...
Click to collapse
Yea odin twarp, pull out mem card, wipe everything on twarp except internal, and reinstall the rom, then reinsert mem card
Sent from Sprint Galaxy Note 3 using Tapatalk
mscooksey21 said:
Ok I just flashed it in stock recovery but im still getting a loop. Is my phone unrooted? Did I need to wipe before I know I should know these things by now but I feel like theres a lot to it that I just dont. So. I could flash twrp in odin then try the flash again? Or do I need to root it again?
Click to expand...
Click to collapse
oops I mean I flashed jellybomb..
..It's been one of those days man.
mscooksey21 said:
oops I mean I flashed jellybomb..
..It's been one of those days man.
Click to expand...
Click to collapse
Still got a boot loop. Wiped cache and dalvik like 3 times. Wiped everything except internal. Flashed rom and kernel. Also on boot loop it says
kernel is not Seandroid enforcing.
and set warranty bit: kernel. And every once in a while I get a very frightening orange bar flash on screen then fade out.
insane209 said:
Yea odin twarp, pull out mem card, wipe everything on twarp except internal, and reinstall the rom, then reinsert mem card
Sent from Sprint Galaxy Note 3 using Tapatalk
Click to expand...
Click to collapse
...Any ideas?