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.
Related
Ehi guys, I made a simple app for our transformer, which allow you to reboot directly to the recovery. ROOT IS REQUIRED.
{
"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"
}
Download: http://goo.gl/RbyLo
Devs, feel free to include this app in your room if you want
So what's the difference between using this and using the power button and selecting boot to CWM?
deadman3000 said:
So what's the difference between using this and using the power button and selecting boot to CWM?
Click to expand...
Click to collapse
Not all the ROMs has the recovery button in the power menu
TY. Found I need this with a new ROM
works like acharm thanks man, but mabay you can make it even more usefull by giving it more options like I have on my ARC : http://forum.xda-developers.com/showthread.php?t=1123576
depulle87 said:
works like acharm thanks man, but mabay you can make it even more usefull by giving it more options like I have on my ARC : http://forum.xda-developers.com/showthread.php?t=1123576
Click to expand...
Click to collapse
Will work on that
Added on Android Market. Button in the first post.
Great job....
Thanks for the app, works great
Quickboot free on market does the same and more.
Sent from my GT-I9000 using XDA Premium App
thanks for this !
Boot Loop
I just installed this app. First time using it, it worked perfectly. Rebooted normal and everything was great. Second time I tried getting to recovery, it did not work. Now my tablet is stuck in a bootloop. Only way to get out of it is to Hold Volume Down and Power, cancel the data wipe, then it cold boots into linux. Currently on ASUS Transformer with Prime 1.6
swvines said:
I just installed this app. First time using it, it worked perfectly. Rebooted normal and everything was great. Second time I tried getting to recovery, it did not work. Now my tablet is stuck in a bootloop. Only way to get out of it is to Hold Volume Down and Power, cancel the data wipe, then it cold boots into linux. Currently on ASUS Transformer with Prime 1.6
Click to expand...
Click to collapse
Never happended to me..
Used it many times and have never had a problem. Thanks for this App!!
the multiupload link is dead..can u plss re-upload the file..i cant download it from market..plss sir..
Quickboot doesn't do anything on mine, it just re starts the pad.
BorgCymru said:
Quickboot doesn't do anything on mine, it just re starts the pad.
Click to expand...
Click to collapse
Quickboot is not compatible as with a lot of "booting" apps. They all work to reboot but not reboot into recovery.
https://market.android.com/details?...sMSwxLDEsImNvbS50cmFuc2Zvcm1lci5yZWNvdmVyeSJd
Works
Great little app! Thanks!
Confirmed working AWESOME!
swvines said:
I just installed this app. First time using it, it worked perfectly. Rebooted normal and everything was great. Second time I tried getting to recovery, it did not work. Now my tablet is stuck in a bootloop. Only way to get out of it is to Hold Volume Down and Power, cancel the data wipe, then it cold boots into linux. Currently on ASUS Transformer with Prime 1.6
Click to expand...
Click to collapse
I'm experiencing this as well. After selecting reboot into recovery the tablet reboots then hangs. The only way to boot now is to cancel the data wipe.
edit: I'm on a refurbished RTF201 C20 serial currently running 8.6.4.21.
edit2: Figured it out. It's because I ran CWM which doesn't work on the Transformer. I wiped my device, then installed and ran the recovery installer: http://forum.xda-developers.com/showthread.php?t=1346180
That did the trick.
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
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
Well. I got my phone fell into the wather and now my home and back key doesn't work. :/ Is there any way to flash or get to download mode without keys. Or is there any way to fix it...
modricl said:
Well. I got my phone fell into the wather and now my home and back key doesn't work. :/ Is there any way to flash or get to download mode without keys. Or is there any way to fix it...
Click to expand...
Click to collapse
if you want to flash anything,
switch off ur phone
connect it to pc via usb
fire up odin and fill in the required files
turn on ur phone while it is connected via usb
as soon as odin shows a COM PORT, hit start
done..
Hmm. I'll try that..
modricl said:
Hmm. I'll try that..
Click to expand...
Click to collapse
It works for me
Hey.... don't forget to thank me!!!
If your buttons dont work you can flash CM7 or AOKP.There you can enable on-screen buttons just like on a nexus device...
modricl said:
Hmm. I'll try that..
Click to expand...
Click to collapse
try this one...it saved me because i bricked my touch keys circuit when i was pulling out my amoled screenbut now i have this awesome feature:
{
"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"
}
but this won't hep you to get you in d/l mode in power off state
Sent fom my S-II with CM-10 by mcm811(12/06/2012] powered by [url="http://dorimanx.shine.sk/kernels-jb/Kernel_Dorimanx-V7.29-ICS-JB-22-51--06-12-12-SG2-PWR-CORE.zip]DorimanX kernel v 7.29[/url]
yeah. that's what i wanted guys i just needed help how to root it. but thx very much <3
new problem. I wanted to isntall kyrillos rom. I did everything right in odin. And after it rebooted it entered the cwm recovery now is problem to do anything because my home button isn't working. ((
modricl said:
new problem. I wanted to isntall kyrillos rom. I did everything right in odin. And after it rebooted it entered the cwm recovery now is problem to do anything because my home button isn't working. ((
Click to expand...
Click to collapse
Reflash with odin. Strange...
kyrillos13 said:
Reflash with odin. Strange...
Click to expand...
Click to collapse
is there any way to flash it without using cwm recovery or to get touch recovery?
Well if you could flash g3mod 2.5 you would have touch recovery but since your buttons dont work that couldnt be done.I know when you flash stock froyo it wipes data by itself without going in recovery.And i think that in jelly bean the recocery is touch by deffault.
Click thanks if i helped
artifex21 said:
Well if you could flash g3mod 2.5 you would have touch recovery but since your buttons dont work that couldnt be done.I know when you flash stock froyo it wipes data by itself without going in recovery.And i think that in jelly bean the recocery is touch by deffault.
Click thanks if i helped
Click to expand...
Click to collapse
tnx. i flashed froyo again and i'm using it now. but i want to put some custom rom like kyrillos
Maybe you could try flashing kyrillos and then g3mod 2.5 via odin. But since your buttons aren't working i dont know how could you go in download mode...since you cant boot using terminal emulator isnt possible too. Maybe with ADB...
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?