Ok so this is what I did. I have an i896 rogers captivate. when I first when to flash a rom I mistakenly put in the i9000 bootloaders. this is what I have on it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
so I guess I have i9000 boot loaders and the captivate teamhacksung ics port for the captivate build 14
my phone is working amazing but I just want to make sure that everything is ok or if I should change something.
I have learned alot here and love the site and all of the developers.
Any help would be appreciated.
Also if I need to include more info on my post about my phone please tell me what so you guys have the info to help me.
Thanks!!
shaker2k said:
Ok so this is what I did. I have an i896 rogers captivate. when I first when to flash a rom I mistakenly put in the i9000 bootloaders. this is what I have on it
View attachment 869121
View attachment 869122
so I guess I have i9000 boot loaders and the captivate teamhacksung ics port for the captivate build 14
my phone is working amazing but I just want to make sure that everything is ok or if I should change something.
I have learned alot here and love the site and all of the developers.
Any help would be appreciated.
Also if I need to include more info on my post about my phone please tell me what so you guys have the info to help me.
Thanks!!
Click to expand...
Click to collapse
The only way to tell if you have the i9000 bootloaders is during the boot sequence. If you see a black screen with "Galaxy S i9000" as your very first boot screen (instead of an AT&T world phone screen) you have the i9000 bootloaders.
And, if your phone boots up and behaves normally, you should be in good shape. I would suggest testing your button combos while everything is functioning normally to make sure they're intact, as well as backing up your /efs folder, but other than that, you should be good to go.
jmtheiss said:
The only way to tell if you have the i9000 bootloaders is during the boot sequence. If you see a black screen with "Galaxy S i9000" as your very first boot screen (instead of an AT&T world phone screen) you have the i9000 bootloaders.
And, if your phone boots up and behaves normally, you should be in good shape. I would suggest testing your button combos while everything is functioning normally to make sure they're intact, as well as backing up your /efs folder, but other than that, you should be good to go.
Click to expand...
Click to collapse
It boots up as a samsung galaxy s gt i9000. and I can get into download and recovery mode. I just have to do it as if it was an i9000 and not the captivate way. power + volume down + home key for download mode
and power + volume up for recovery mode.
You should be in good shape, then.
Just be aware that if you flash any AT&T based roms (i.e. anything that has a 3-letter acronym starting with K, like KK4), you may run into some hiccups. Nothing major, just something to be aware of.
Well I don't forsee that being a problem because I plan to stick with cyanogen ics.
I also want to contribute to xda as much as I can. I won't be a flashing maniac but I'm trying to learn as much as I can so I can help others who had the same hiccups that I have had.
You guys make this so easy to do that even a noob like me can have success and breathe new life into their phones
jmtheiss said:
The only way to tell if you have the i9000 bootloaders is during the boot sequence. If you see a black screen with "Galaxy S i9000" as your very first boot screen (instead of an AT&T world phone screen) you have the i9000 bootloaders.
Click to expand...
Click to collapse
that's not the ONLY way, as mentioned there are specific button combos for each set if bootloaders
shaker2k said:
It boots up as a samsung galaxy s gt i9000. and I can get into download and recovery mode. I just have to do it as if it was an i9000 and not the captivate way. power + volume down + home key for download mode
and power + volume up for recovery mode.
Click to expand...
Click to collapse
You don't need the home button... I9000 uses a different mapping structure as there are less buttons...if you were to flash straight up I9000 firmware the home button wouldn't work at all, when using it while booted is mapped out by the ROM so that pressing it actually goes to the home screen, but the bootloaders detect button presses themselves, before the ROM maps them for Android.
I've been running I9000 boots since pretty much day 1 of their existence in the captivate world. I have never used the home button. Vol down and power, that's all you need
EDIT: F U SWYPE!
that's not the ONLY way
Click to expand...
Click to collapse
Good point.
Vol Doreen
Click to expand...
Click to collapse
Who is this Doreen you speak of? Is she the ghost of kernels yet to come?
I used to have an i9000 bootloader but I switched into our official gingerbread bootloaders as soon as they came out. I would suggest doing the same.
Sent from my SGH-I897 using xda premium
Related
Hi every body
This is a Gingerbread theme for P1000OJPJK2 ME rom
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://www.multiupload.com/7Z7FSKF474
How to install
1- after downloading the attached file copy update.zip in your internal memory
2- go to the original recovery mod
3- apply update.zip from sdcard
fin enjoy ..
will this work on my P1000JXJJ1? also a ME build but changed code to XSG for enabling market
i think yes but idid not test it
Salam Dr
Good job, thank you very much
how do i get my tab into recovery mode?
I tried power on and vol. down button, i'm in downloading mode ! is this the same?
EDIT: I applied it in recovery mode, now all i see is android logo with a orange exclamation mark !
jackie_jagger said:
how do i get my tab into recovery mode?
I tried power on and vol. down button, i'm in downloading mode ! is this the same?
EDIT: I applied it in recovery mode, now all i see is android logo with a orange exclamation mark !
Click to expand...
Click to collapse
the same but power on and vol. up button
So what happened to you unit? Is it back not to normal?
Does it work on JMC
Sent from my GT-P1000 using XDA App
hani1980 said:
the same but power on and vol. up button
Click to expand...
Click to collapse
yea I figured that out, but when I apply I get the android buddy with a yellow exclamation mark ! please advice
Pullback said:
So what happened to you unit? Is it back not to normal?
Click to expand...
Click to collapse
yea I just had to reboot it to get back to normal !
Cant install on ROTO-JMC.
- It failed when i try to apply update.zip ..
jpjm3
dr.akrim;
hi and thanks for this theme.can i use this theme on new arabic rom (JPJM3).
Tab in big problem
Hi everyone.
Im from MExico and i use...used a Galaxy Tab P1000LUMJI with Voicecall capabilities, well, until few minutes ago and i am really new with Galaxy Tab, i installed this them through recovery mode just like the instructions.
Everything went perfect but when it rebooted, it stopped in black screen with "samsung" glowing. Additionaly, its like a cycle because the process is not freezing just making the same glowing screen,.
The tab vibes first one time and after that two times again.
Any solution to remove that update.zip?
Help!!
jae hoon: try to use all clear options in the recovery menu. something similar happened to me and my galaxy s phone and that solved the problem.
dhanjel said:
jae hoon: try to use all clear options in the recovery menu. something similar happened to me and my galaxy s phone and that solved the problem.
Click to expand...
Click to collapse
Thanks for your advice, i tried that, i selected all the options: wipe and clear cache and data to factory through recovery mode....still same.
I think once i applied the update.zip, something like the kernel changed mine. The big problem if it is so, is we are so few members with the Galaxy Tab from Telcel here in Mexico.
I think i will take it to warranty service.
I hope they can do something.
bad news, good news
Hi.
Today i went to my carrier customer office and i they took the tab to check it and reinstall the OS... at least they didnt complain nothing. I have to go back to my office for a while.
I came back from the customer service and the bad new is they cant save the tab. But inmediately they gave me a replacement. ufff! I was being worried.
I will better to help developers in getting more info or development of latin carriers.
can i use it on JMG?
ya, can you help to port this theme to JMG?
nice theme....thanks you.....
It would be great to see this for overcome rom ....
Alright guys, need some help here. I went here:http://forum.xda-developers.com/showthread.php?t=1155623 and followed the step 1 exacly as told. Using Galaxy s 4g..the odin stated a pass..but the phone turned off and it won't power up no more..could somone have any idea on this?
Only flash roms for the SGH-T959V and not any other model
First look up in the bible (http://forum.xda-developers.com/showthread.php?t=1117554) the guide on how to get into download mode. Your phone will hopefully get recognized.
Second, look up raver's KC1 cleanup. Search for raver, you should find it. That should get you back on a clean SGS4G rom.
Third, don't install ROMs that wasn't made for your phone.
Perhaps because it's not made for this phone... From my understanding, you should never use anything that's NOT made specifically for this phone.
Despite the similarities this phone is very different.
Sent from my SGH-T959V using xda premium
So preatty mutch it's dead now right? since it won't power up
Kirthaal said:
So preatty mutch it's dead now right? since it won't power up
Click to expand...
Click to collapse
yeah, flashing roms made for other phones is a good way to kill the Galaxy S 4G. never flash a rom that is made for another phone. it might still be recoverable though.. look up the posts on unbricking your phone using heimdall, maybe you can find something that works.
Kirthaal said:
So preatty mutch it's dead now right? since it won't power up
Click to expand...
Click to collapse
Not necessarily. There is always a chance on getting Odin to recognize it.
Sent from my SGH-T959V using xda premium
Ouch, should've read around the forum more. :T
Does Odin recognize your phone at all when you plug it in? Try the methods to get into download mode and see if Odin recognizes it. If it does, you might be able to restore your phone.
If that doesn't work, try this thread: http://forum.xda-developers.com/showthread.php?t=1220181&highlight=debrick
I haven't really read that thread in detail myself, so maybe others could help you out on that.
Open odin on your computer.
Do a battery pull. Put the battery back in. Hold vol + and -, then plug the usb cable in. If Odin recognizes it, you're in luck.
You should at least be able to get to download mode. When you say it wont power up does it at least show the battery image with the USB plugged in while off? If it does you should be able to hold vol down and power to get to download mode and use ODIN to flash a new ROM.
If it's a blank screen and Odin won't recognize the phone look up raverx3x 's tutorial on how to re-install the correct bootloaders using Heimdall. It worked for me. I can't give you the link because I'm not at the computer now. Once you get the phone to boot you will probably have to flash back to stock using the KC1 cleanup rom and go from there.
Sent from my SGH-T959V using xda premium
nazcalito said:
If it's a blank screen and Odin won't recognize the phone look up raverx3x 's tutorial on how to re-install the correct bootloaders using Heimdall. It worked for me. I can't give you the link because I'm not at the computer now. Once you get the phone to boot you will probably have to flash back to stock using the KC1 cleanup rom and go from there.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Kirthaal, if you haven't seen my post yet, the thread is linked there. Just telling you so you won't have to look everywhere, lol.
http://dl.dropbox.com/u/40595761/1 click bootloader debrick.zip
there that should help u if u dont understand how to use the thread... extract zip run jar file
Ptoblrm is the device won't turn on at all, so it won't be detected by any of the sofware including odin, i got the jig from amazon and that does not do the job either not sure where to go from there
Kirthaal said:
Ptoblrm is the device won't turn on at all, so it won't be detected by any of the sofware including odin, i got the jig from amazon and that does not do the job either not sure where to go from there
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wow I live by a very simple rule when it comes to flashing READ this phone is sooooo hard to hard brick. I feel for u I thought Raver had a post on debricking a hard brick without using jig? U can't even get any back lights or splash screen?
Sent from my SGH-T959V using xda premium
Kirthaal said:
Ptoblrm is the device won't turn on at all, so it won't be detected by any of the sofware including odin, i got the jig from amazon and that does not do the job either not sure where to go from there
Click to expand...
Click to collapse
assumeing he didnt try
I had problems b4 similar to this. Pull the battery, plug in USB, hold down volume up and down at the same time, then put battery back in without letting go and see if that works. If not go to the forum that you flashed the wrong Rom and see if they have a different button combo for dl mode than we do.
Hope this helps
Sent from my SGH-T959V using XDA App
So I'm not sure when this happened, but when I hold my power button for a hard reset, this is the first thing that comes up after the phone shuts down. The sequence goes
1) Hold Power button
2) Screen off
3) This messed up screen
4) SAMSUNG logo
5) ROM bootscreen
Anyone have any idea what this is and how to fix it? This is HUGE nuisance, and if anyone could help, I'll owe you a beer.... or vodka
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I would try flashing a differnt kernel...if that doesnt work, trt flashing a different rom, if that doesnt work try odin back to stock or pre-rooted stock and see if the problem continues
Also it may help to know what rom/kernel you are running
Sent from my SAMSUNG-SGH-I997 using XDA
jgruberman said:
So I'm not sure when this happened, but when I hold my power button for a hard reset, this is the first thing that comes up after the phone shuts down. The sequence goes
1) Hold Power button
2) Screen off
3) This messed up screen
4) SAMSUNG logo
5) ROM bootscreen
Anyone have any idea what this is and how to fix it? This is HUGE nuisance, and if anyone could help, I'll owe you a beer.... or vodka
Click to expand...
Click to collapse
Do u have the right bootloaders?
Sent from my SGH-I997 using xda premium
ODIN to stock using GB ODIN. You'll be good to go
Thanks for the replies, I actually forgot about this thread. I ended up using GTG to flash back to stock to install Zeus and it fixed this problem. I think the original issue happened when I tried to put a custom bootanimation.zip on the phone... now I'm afraid to tweak the bootscreen...
Fear not! At the most you might end up reverting to stock. No big deal, and its worth experimenting.
hi my screen is the same as the guy in the post. but mine is due to the fact im a rogers phone and i installed att gb 2.3.6 and now im stuck as att. is there a way out of this so i can go back to rogers. i tried all the rogers kernels and so on. unless there is a rogers boot somewhere i can download
Display Issue HELP!
Ok my phone has this same problem...anytime upon starting the phone that colorful snowey screen will show for about 5-6 sec right before you see the at&t logo. then it goes away and everything works perfect. I will also occasionally show up when i launch the camera! so I cant see what im taking a picture of but it will still capture the picture just fine...weird. This phone was doing this while NOT ROOTED...any help please!?
chopt said:
Ok my phone has this same problem...anytime upon starting the phone that colorful snowey screen will show for about 5-6 sec right before you see the at&t logo. then it goes away and everything works perfect. I will also occasionally show up when i launch the camera! so I cant see what im taking a picture of but it will still capture the picture just fine...weird. This phone was doing this while NOT ROOTED...any help please!?
Click to expand...
Click to collapse
It sounds like yours may be a hardware issue, but I can't say for sure, I would say take it to AT&T, but your warranty is busted. So my best advice is to use google.com and see if anyone else is having the same issue.
yeah ive googled all day long and this is the only thing I can find on the issue...damn. Thanks
No prob, I wish I knew more so I could help, but I have never heard of that issue
The rainbow screen in the picture is due to using a kernel with the wrong bootloaders. You are most likely running a GB or ICS ROM on froyo bootloaders. Odin back to stock 2.3.6 and flash the BL's.
Sent from my SGH-I997 using XDA
chopt said:
yeah ive googled all day long and this is the only thing I can find on the issue...damn. Thanks
Click to expand...
Click to collapse
I would just run gtg ultimate unbrick it will take your phone back to how it was out of the box
sent on the back of my pink unicorn AOKP
Hey guys,
well i installed clockworkmod rom manager and used that program to upgraded to cyogenmod 7.
It seems that after the backup and install of the new rom, my phone now only boots to the LG logo screen. This is a very big problem for me since I do not have nvflash installed and only CWM.
The main issue is when i boot into CWM, i can can navigate around, however the power button does not work for selecting anything. I can't select reboot, can't do anything. Which brings me to another thing, CWM ONLY has "reboot phone", "wipe cache", "wipe partition", "apply sd card update.zip"(have Cygen mod rom on my sdcard).
What do you guys recommend me doing ot fix this? I'd be happy just bringing the phone back to stock.
Any help ASAP would be great as i need my phone working sooner rather htan later.
First off rom manager doesn't work on this phone. Second go to this thread
http://forum.xda-developers.com/showthread.php?p=33748097 go to nvflash clockworkmod section and use the tools provided on a pc it sounds kinda complicated but its not. Its the only way i know to fix the problem
All the way from mars
monte666 said:
First off rom manager doesn't work on this phone. Second go to this thread
http://forum.xda-developers.com/showthread.php?p=33748097 go to nvflash clockworkmod section and use the tools provided on a pc it sounds kinda complicated but its not. Its the only way i know to fix the problem
All the way from mars
Click to expand...
Click to collapse
Hey, i've got NVflash on my comp. When i try to use any of the buttons, it shows on my phone S/W Upgrade, please wait while upgrading.... and sits on this screen forever.
The cmd prompt that appears goes through its process but says some files filed. Ill attach a screenshot for you to view
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
chowdan said:
Hey, i've got NVflash on my comp. When i try to use any of the buttons, it shows on my phone S/W Upgrade, please wait while upgrading.... and sits on this screen forever.
The cmd prompt that appears goes through its process but says some files filed. Ill attach a screenshot for you to view
Click to expand...
Click to collapse
Red on black, impossible to read. Are you holding down both volume buttons until its done?
also, I would re download the files.
Sent from my LG-P999 using xda premium
justjackyl said:
Red on black, impossible to read. Are you holding down both volume buttons until its done?
also, I would re download the files.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Hey,
Sorry about htat. Ill reupload a photo.
I am holding down both volume buttons. THe funny thing is that when i pull the battery, hold the two buttons down, then plug in the phone, it doesn't go to the "S/W Upgrade" screen. It stays black. Once I initiate one of the NVflashes, the screen then switches over to the "S/W Upgrade screen".
Should it be going to this upgrade screen after a short bit after i plug it in? Is this an issue?
Well guy's.
Following that post worked. For some reason everytime i would do at home, it wouldn't work. I tried running nvflash as admin/non admin, still showed the error.
However coming into work and using my work computer, resolved the issue. I got the experimental touch based CWM up and running and was able to use a coworkers G2x to access my SD card to put Cyanogen 7 on which then allowed me to flash that ROM to my G2x.
All is working well now!!! Thank god for the nearly unbrickable phone
chowdan said:
Well guy's.
Following that post worked. For some reason everytime i would do at home, it wouldn't work. I tried running nvflash as admin/non admin, still showed the error.
However coming into work and using my work computer, resolved the issue. I got the experimental touch based CWM up and running and was able to use a coworkers G2x to access my SD card to put Cyanogen 7 on which then allowed me to flash that ROM to my G2x.
All is working well now!!! Thank god for the nearly unbrickable phone
Click to expand...
Click to collapse
Well, bro sometimes the drivers it aint install right.
Migh be that was the issue, but that was strange you said that you had CWM runnig ont the device how come you werent able to flash a ROM?
I will preface this question by saying that I'm not an expert in Android development, but this is also not my first time flashing a ROM and I am relatively comfortable with basic ADB commands and such. I try not to get involved in anything too complicated, but I like the control custom ROMs give.
I have an AT&T One X that had (has?) TWRP and ViperXL 3.2.5 on it. I wanted to try out the CM10 nightlies ROM. So I download the latest build and the gapps. Do a backup, do a full wipe, then flash the CM10 zip. In TWRP I get confirmation that it has flashed successfully. So I reboot, but I get nothing. A simple power on does nothing. Holding the power button flashes the back, home, settings buttons for ~10 seconds, then I get the white HTC screen with the red warning text, then nothing. Attempting to boot into recovery with the Power and Vol down button does the same.
What's going on here? I'm going to see if ADB will recognize the device, but I'm not sure what my steps should be to get a working phone back. Any help would be greatly appreciated. Thanks.
anothermiler said:
I will preface this question by saying that I'm not an expert in Android development, but this is also not my first time flashing a ROM and I am relatively comfortable with basic ADB commands and such. I try not to get involved in anything too complicated, but I like the control custom ROMs give.
I have an AT&T One X that had (has?) TWRP and ViperXL 3.2.5 on it. I wanted to try out the CM10 nightlies ROM. So I download the latest build and the gapps. Do a backup, do a full wipe, then flash the CM10 zip. In TWRP I get confirmation that it has flashed successfully. So I reboot, but I get nothing. A simple power on does nothing. Holding the power button flashes the back, home, settings buttons for ~10 seconds, then I get the white HTC screen with the red warning text, then nothing. Attempting to boot into recovery with the Power and Vol down button does the same.
What's going on here? I'm going to see if ADB will recognize the device, but I'm not sure what my steps should be to get a working phone back. Any help would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
After the back, home, settings buttons blink and the screen turns off, let go wait 3 seconds then press and hold power and volume down. It will go into bootloader. Also, make sure the phone is not plugged in while doing this.
Make sure you release power after the buttons flash, but hold vol down. That will get you into bootloader.
I suspect you've got the wrong kernel (Sense kernels don't work with asop). Are you s-off? If not, did you flash the CM10 boot.img in fastboot?
Thanks!
iElvis said:
Make sure you release power after the buttons flash, but hold vol down. That will get you into bootloader.
I suspect you've got the wrong kernel (Sense kernels don't work with asop). Are you s-off? If not, did you flash the CM10 boot.img in fastboot?
Click to expand...
Click to collapse
OK I can get into the bootloader. It looks like S-ON unfortunately, and no I didn't flash the CM10 boot.img. I assume that should take care of the kernel incompatibility?
yep
I think that's fixed
anothermiler said:
OK I can get into the bootloader. It looks like S-ON unfortunately, and no I didn't flash the CM10 boot.img. I assume that should take care of the kernel incompatibility?
Click to expand...
Click to collapse
Well I think I have everything fixed - I used a tool to flash the boot.img from fastboot and CM now seems to boot correctly. Thanks a lot for the help!
anothermiler said:
Well I think I have everything fixed - I used a tool to flash the boot.img from fastboot and CM now seems to boot correctly. Thanks a lot for the help!
Click to expand...
Click to collapse
Around here, we don't say thanks, pardner, we click the Thanks button.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just a heads up, on Hboot 1.14 and S-On you'll have to flash a kernel separately each time
Sent from my One X using xda app-developers app
Desertman123 said:
Just a heads up, on Hboot 1.14 and S-On you'll have to flash a kernel separately each time
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Via fastboot no less. Key component.