Related
I updated the Cyanogen Mod to 4.2.6, which worked fine. However, I then went into the Cyanogen Updater to get the Dark Dream 1.5 theme (not realizing that it is a theme for CM 4.2.5).
Now when I go to restart my phone, it gets hung up on the G1 screen. I can still get into the recovery screen, but it aborts everything I try, so I cannot wipe and re-install a ROM. I can get into the console, but I'm not sure what I'm looking for there. I can also get into the boot-loader screen, but am unable to do anything. HBoot Mode shows that there are a bunch of missing images and then pops me back to FastBoot screen. I am wondering if anyone can offer a suggestion on how to get my phone working again.
greatheight said:
I updated the Cyanogen Mod to 4.2.6, which worked fine. However, I then went into the Cyanogen Updater to get the Dark Dream 1.5 theme (not realizing that it is a theme for CM 4.2.5).
Now when I go to restart my phone, it gets hung up on the G1 screen. I can still get into the recovery screen, but it aborts everything I try, so I cannot wipe and re-install a ROM. I can get into the console, but I'm not sure what I'm looking for there. I can also get into the boot-loader screen, but am unable to do anything. HBoot Mode shows that there are a bunch of missing images and then pops me back to FastBoot screen. I am wondering if anyone can offer a suggestion on how to get my phone working again.
Click to expand...
Click to collapse
Use fastboot. You say you have it, this is what its for.
greatheight said:
I updated the Cyanogen Mod to 4.2.6, which worked fine. However, I then went into the Cyanogen Updater to get the Dark Dream 1.5 theme (not realizing that it is a theme for CM 4.2.5).
Now when I go to restart my phone, it gets hung up on the G1 screen. I can still get into the recovery screen, but it aborts everything I try, so I cannot wipe and re-install a ROM. I can get into the console, but I'm not sure what I'm looking for there. I can also get into the boot-loader screen, but am unable to do anything. HBoot Mode shows that there are a bunch of missing images and then pops me back to FastBoot screen. I am wondering if anyone can offer a suggestion on how to get my phone working again.
Click to expand...
Click to collapse
If you can into recovery you should be able to fix it by applying the cyanogen update again, if not use fastboot to restore a nandroid backup
jackslim said:
If you can into recovery you should be able to fix it by applying the cyanogen update again, if not use fastboot to restore a nandroid backup
Click to expand...
Click to collapse
While I can boot into the recovery mode, nothing seems to work. I try a wipe; comes up "Wipe Aborted." Same thing happens when I try to apply the update again.
I am going to see if I can re-install the cyanogen update from the console, as it seems like that is the only the working in the recovery mode. Unfortunately I don't have a nandroid backup to use. Thanks for the suggestion.
Which recovery image are you using?
jackslim said:
If you can into recovery you should be able to fix it by applying the cyanogen update again, if not use fastboot to restore a nandroid backup
Click to expand...
Click to collapse
greatheight said:
Unfortunately I don't have a nandroid backup to use.
Click to expand...
Click to collapse
You can download a nandroid image to fastboot of the official rom directly from HTC for the ADP1 phone. Download the Android 1.6 "System Image" from http://developer.htc.com/adp.html You may have to reinstall a custom recovery image afterwords. Then you can upgrade to any rom you want.
If you need to, you can download the latest recovery image here http://forum.xda-developers.com/showthread.php?t=566669 and install using the fastboot method.
testing567 said:
If you need to, you can download the latest recovery image here http://forum.xda-developers.com/showthread.php?t=566669 and install using the fastboot method.
Click to expand...
Click to collapse
It is likely this is the way I'll need to go. Thanks for all the help.
battery
the wipe could have been aborted b/c your battery is too low thats happened to me before just plug it in
My phone won't get passed the t-mobile mytouch 4g screen. This happened after I backed up my stock rom using rom manager and did a full wipe to start clean ut no after I went back and restored my backup, my phone is stuck on the mytouch screen and won't get pass that. Is my phone bricked? or can it be saved? can someone pls help me? I just got this phone yesterday and rooted it with no problem. All I did after the root was add a custom kernel. Everything was going great until I restored my backup. Pls help. Thanks in advance.
try going into the bootloader. press power& the volume down button at the same time. then let it load, select the option to boot into recovery. once u do that wipe all cache, data, and restore the backup u made. but if it doesn't boot up again then it might be a defective backup. might have to start fresh with flashing a new rom. but keep trying once u boot into the phone tho. goodluck!
I tried that and still not working. Is there away I can get a stock rom to flash?
Jaylito. said:
try going into the bootloader. press power& the volume down button at the same time. then let it load, select the option to boot into recovery. once u do that wipe all cache, data, and restore the backup u made. but if it doesn't boot up again then it might be a defective backup. might have to start fresh with flashing a new rom. but keep trying once u boot into the phone tho. goodluck!
Click to expand...
Click to collapse
Now I can't even boot into clockworkmod recovery. Now it boots me to the stock recovery. How can I get clockworkmod recovery back? I can't flash a rom without it.
ImABoss said:
Now I can't even boot into clockworkmod recovery. Now it boots me to the stock recovery. How can I get clockworkmod recovery back? I can't flash a rom without it.
Click to expand...
Click to collapse
The phone still says s-off so I don't know what is wrong and since I bought the phone yesterday I can take it back to t-mobile to get a new one but won't they notice the s-off and not exchange it?
Use Fastboot. It is like adb, but only uses the bootloader on the phone. If you don't have the SDK installed, you can get adb and Fastboot from TrueBlue_Drew's thread in the dev subforum.
HTC Glacier run ning CM7 #33
jggimi said:
Use Fastboot. It is like adb, but only uses the bootloader on the phone. If you don't have the SDK installed, you can get adb and Fastboot from TrueBlue_Drew's thread in the dev subforum.
HTC Glacier run ning CM7 #33
Click to expand...
Click to collapse
I'm using fastboot but nothing happens. AM I screwed? I'm sorry for all the questions but this has never happened before.
ImABoss said:
I'm using fastboot but nothing happens. May I screwed? I'm sorry for all the questions but this has never happened before.
Click to expand...
Click to collapse
Is there an official update.zip I can probably apply through the stock recovery?
Thanks Jaylito and Jggimi for your help, was able to get into cwm recovery and flash a new rom. It looks like I had a bad backup. Thanks again to you both.
Hi guys, i have cwm 3.0.0.5 which is really a cwm 3.0.0.6 mod i downloaded from here. anyway,i cant get back too 2.5.1.2. when i go into rom manager the lowest it says is 2.5.1.3 and none of the 2.x work for me except my old one. i tried rebooting it, and flashing the original 3.0.0.5 and it still doesnt show up and i have the paid version by the way. so my question is how do i get it back?
second problem is i flashed a splash screen and its stuck on there with a staticky looking bar covering the top of the screen when i reboot. i have deleted the custom.img on the sdcard, wiped the phone, flashed another custom.img, factory reset the phone, and it still is there and i pushed the files through terminal emulator, i do everything from my phone because my computer is very laggy. can anyone help with the above problems?
TamiaSky said:
Hi guys, i have cwm 3.0.0.5 which is really a cwm 3.0.0.6 mod i downloaded from here. anyway,i cant get back too 2.5.1.2. when i go into rom manager the lowest it says is 2.5.1.3 and none of the 2.x work for me except my old one. i tried rebooting it, and flashing the original 3.0.0.5 and it still doesnt show up and i have the paid version by the way. so my question is how do i get it back?
Click to expand...
Click to collapse
you can always find just the recovery image and flash it via the ADB commands.
TamiaSky said:
second problem is i flashed a splash screen and its stuck on there with a staticky looking bar covering the top of the screen when i reboot. i have deleted the custom.img on the sdcard, wiped the phone, flashed another custom.img, factory reset the phone, and it still is there and i pushed the files through terminal emulator, i do everything from my phone because my computer is very laggy. can anyone help with the above problems?
Click to expand...
Click to collapse
you need to flash a new image, that is the only way to fix it.
neidlinger said:
you can always find just the recovery image and flash it via the ADB commands.
you need to flash a new image, that is the only way to fix it.
Click to expand...
Click to collapse
and where would i find the recovery image? and can it be done using terminal emulator, becuase my computer has a virus and it takes days to load stuff or do anything, thats why i do it straight from my phone
and i have flashed a new image just like u quoted me i deleted the stuck one, wiped the phone, then i flashed another one, then factory reset the phone and its still there!
TamiaSky said:
and where would i find the recovery image? and can it be done using terminal emulator, becuase my computer has a virus and it takes days to load stuff or do anything, thats why i do it straight from my phone
and i have flashed a new image just like u quoted me i deleted the stuck one, wiped the phone, then i flashed another one, then factory reset the phone and its still there!
Click to expand...
Click to collapse
i'm sure google has something on the recovery image. I only have 3.0.0.6 stored in a .zip.
you CAN flash the recovery image via the terminal but not the boot image.
TamiaSky said:
and where would i find the recovery image? and can it be done using terminal emulator, becuase my computer has a virus and it takes days to load stuff or do anything, thats why i do it straight from my phone
and i have flashed a new image just like u quoted me i deleted the stuck one, wiped the phone, then i flashed another one, then factory reset the phone and its still there!
Click to expand...
Click to collapse
Download a fresh cope of the latest version here: http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-3.0.2.4-glacier.img and flash it via terminal emulator. It automatically overwrites the previous installation.
I'm having a big problem with my Nexus 4 here lately. I tried to root it about 2 days ago, and it did not work. So i downloaded TWRP and my computer read it the same as the Nexus 4 root toolkit by WugFresh. I opened TWRP and it asked me to flash or boot (it was on flash), and i think i clicked "Recovery" and it made my Nexus not boot up, it was just at the logo screen. Then i tried to flash TWRP to the bootloader and System and it flashed TWRP, now it won't go into android. It just takes me into the TWRP interface. In the TRWP interface there are 8 options( Install, Wipe, Backup, Restore, Mount, Settings, Advanced, and Reboot). I pressed "Reboot" and i when press System, Recovery, or Bootloader it tells me that the is no OS installed, I've looked up how to install OS back via WugFresh's toolkit, but it's still not working (maybe because I'm on a old computer). So I'm kinda panicking, is there anyone i can call,or take my phone to, or can you guys help PLEASE!?!
1. Calm down, dont panic. Its an easy fix. You need to push a rom onto your phone using adb, then flash it using twrp.
2. Setup adb.
3. Download ROM: here or here.
4. Use this command to copy the rom to the phone:
Code:
adb push nameofROM.zip /sdcard
5. In TWRP go to Install, look for the rom you pushed, select it, and finally swipe to flash it.
Okay, i'll try that right now..
chromium96 said:
1. Calm down, dont panic. Its an easy fix. You need to push a rom onto your phone using adb, then flash it using twrp.
2. Setup adb.
3. Download ROM: here or here.
4. Use this command to copy the rom to the phone:
Code:
adb push nameofROM.zip /sdcard
5. In TWRP go to Install, look for the rom you pushed, select it, and finally swipe to flash it.
Click to expand...
Click to collapse
I'm having a problem with the ADB setup, i followed all the directions carfully, and that last step were i had to type in "adb devices" in did not work... is there anyway i can open adb??
Yiddish said:
I'm having a problem with the ADB setup, i followed all the directions carfully, and that last step were i had to type in "adb devices" in did not work... is there anyway i can open adb??
Click to expand...
Click to collapse
Try install these drivers: http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi
chromium96 said:
Try install these drivers
Click to expand...
Click to collapse
Nice, that worked. Okay i'm back on track. Also, does it matter what ROM i download?? I don't have to be rooted to push them huh?
Yiddish said:
Nice, that worked. Okay i'm back on track. Also, does it matter what ROM i download?? I don't have to be rooted to push them huh?
Click to expand...
Click to collapse
Nope. Just make sure u put the phone in recovery mode (twrp) before you use the push command.
Sent using xda-developers app
chromium96 said:
Nope. Just make sure u put the phone in recovery mode (twrp) before you use the push command.
Sent using xda-developers app
Click to expand...
Click to collapse
Recovery mode is when the Android is on it's back with a red exclamation over it right??
Yiddish said:
Recovery mode is when the Android is on it's back with a red exclamation over it right??
Click to expand...
Click to collapse
Thats the stock recovery, but since you have TWRP installed that is your current recovery. So go into TWRP and use the command from there.
chromium96 said:
Thats the stock recovery, but since you have TWRP installed that is your current recovery. So go into TWRP and use the command from there.
Click to expand...
Click to collapse
Oh, i see. Okay here i go
chromium96 said:
1. Calm down, dont panic. Its an easy fix. You need to push a rom onto your phone using adb, then flash it using twrp.
2. Setup adb.
3. Download ROM: here or here.
4. Use this command to copy the rom to the phone:
Code:
adb push nameofROM.zip /sdcard
5. In TWRP go to Install, look for the rom you pushed, select it, and finally swipe to flash it.
Click to expand...
Click to collapse
Okay, it got past the Google screen, now it's been on the multicolored X for about 10 minutes+ not doing anything
chromium96 said:
Thats the stock recovery, but since you have TWRP installed that is your current recovery. So go into TWRP and use the command from there.
Click to expand...
Click to collapse
How long will i be on the X loading screen??
Yiddish said:
How long will i be on the X loading screen??
Click to expand...
Click to collapse
On the first boot after flashing a new ROM the Nexus should start up within 5 to 10 minutes. If the phone is still displaying the boot animation, reboot into the phone into TWRP recovery, select Wipe, select Factory Reset, wipe Cache and Dalvik cache, and reboot the phone.
BobWalker said:
On the first boot after flashing a new ROM the Nexus should start up within 5 to 10 minutes. If the phone is still displaying the boot animation, reboot into the phone into TWRP recovery, select Wipe, select Factory Reset, wipe Cache and Dalvik cache, and reboot the phone.
Click to expand...
Click to collapse
Thanks! I think it was just the ROM i chose. I just downloaded Slim Bean, this seems to be working( the startup screen looks cool ) I'm on the "Android is upgrading..." screen and it says "Starting apps." at the moment.
Okay, SlimBean took more than 10 minutes, so i factory reset and tried again, and it's still not booting up. ):
BobWalker said:
On the first boot after flashing a new ROM the Nexus should start up within 5 to 10 minutes. If the phone is still displaying the boot animation, reboot into the phone into TWRP recovery, select Wipe, select Factory Reset, wipe Cache and Dalvik cache, and reboot the phone.
Click to expand...
Click to collapse
Any ideas why it's still not working??
Yiddish said:
Any ideas why it's still not working??
Click to expand...
Click to collapse
I have not used Slim Bean. It sounds as though you got past the boot animation screen to Slim Bean updating apps (Android upgrading). Normally ROMs that update apps on startup display a count as they update. Does Slim Bean display such an update counter? Does the count progress or does it hang at some point? Note that the system update on startup will take additional time depending on the quality of your phone's network connection. If you are still experiencing issues with Slim Bean, I recommend that you post on the developers forum where you downloaded the ROM.
BobWalker said:
I have not used Slim Bean. It sounds as though you got past the boot animation screen to Slim Bean updating apps (Android upgrading). Normally ROMs that update apps on startup display a count as they update. Does Slim Bean display such an update counter? Does the count progress or does it hang at some point? Note that the system update on startup will take additional time depending on the quality of your phone's network connection. If you are still experiencing issues with Slim Bean, I recommend that you post on the developers forum where you downloaded the ROM.
Click to expand...
Click to collapse
I got passed the boot animation, and it was taking too long to update my apps so i turned my phone off, and back on, after that my phone would not go past the boot animation. Are you guys sure that all i need to do is pus a ROM file?? Because it doesn't seem like it's working. Also, does it matter were i flash TWRP too??
Yiddish said:
I got passed the boot animation, and it was taking too long to update my apps so i turned my phone off, and back on, after that my phone would not go past the boot animation. Are you guys sure that all i need to do is pus a ROM file?? Because it doesn't seem like it's working. Also, does it matter were i flash TWRP too??
Click to expand...
Click to collapse
It is certainly more convenient to replace the stock recovery with TWRP permanently since this gives you more freedom when installing ROMs and performing nandroid backups.
I would try booting into TWRP again, install the Slim Bean ROM one more time, install Gapps, wipe Cache and Dalvik cache, and reboot your phone. If the Nexus gets past the boot animation to "Android upgrading" allow the upgrade to complete. If you are still having problems with Slim Bean, I suggest posting your question in the Slim Bean thread in the developers forum.
BobWalker said:
It is certainly more convenient to replace the stock recovery with TWRP permanently since this gives you more freedom when installing ROMs and performing nandroid backups.
I would try booting into TWRP again, install the Slim Bean ROM one more time, install Gapps, wipe Cache and Dalvik cache, and reboot your phone. If the Nexus gets past the boot animation to "Android upgrading" allow the upgrade to complete. If you are still having problems with Slim Bean, I suggest posting your question in the Slim Bean thread in the developers forum.
Click to expand...
Click to collapse
Where do i get Gapps??
Long story short a custom kernel completely screwed up the graphics on my N4 CM11 so I'm trying to flash the original kernel from the ROM which is NOWHERE to be found in the cyanogen site.
Anyone got a link?
MGREX said:
Long story short a custom kernel completely screwed up the graphics on my N4 CM11 so I'm trying to flash the original kernel from the ROM which is NOWHERE to be found in the cyanogen site.
Anyone got a link?
Click to expand...
Click to collapse
Just reflash the rom.
If you don't want to, tell me what version of cm11 your'e running and i'll make a flashable kernel zip :good:
or pull the boot.img out of the rom zip and use the flashify app to flash it. the boot.img is the kernel. but honestly, it sounds like you have absolutely no idea what you are doing. if you have any questions, please ask, im willing to help. can you explain what happened?
Yeah I screwed up, didn't notice it wasn't CAF
22sl22 said:
If you don't want to, tell me what version of cm11 your'e running and i'll make a flashable kernel zip :good:
Click to expand...
Click to collapse
It's 11.0-InstallerXNPQ08Q
Thanks!
So after a reboot to enter recovery my N4 is stuck in the splash screen with the white google logo.
This is getting worse by the minute...
MGREX said:
So after a reboot to enter recovery my N4 is stuck in the splash screen with the white google logo.
This is getting worse by the minute...
Click to expand...
Click to collapse
just fastboot flash a recovery, this shouldnt an issue. did you flash a recovery before, or just boot one? it makes a difference if it sticks around or not.
simms22 said:
just fastboot flash a recovery, this shouldnt an issue. did you flash a recovery before, or just boot one? it makes a difference if it sticks around or not.
Click to expand...
Click to collapse
I'm able to force-access recovery and CWM but that's it, once it boots it gets stuck on the splash screen, and thanks to the lack of a SD port I'm unable to easily load a kernel or ROM, and despite having the android SDK I'm unable to sideload the file through adb on Windows.
Any ideas? besides trying the adb through Linux (I'm doing that now)
Here's the flashable kernel zip taken from Snapshot M7 build :good:
Okay now it gets stuck in the cyanogenmod boot animation
Any ideas? that don't involve wiping everything I mean
simms22 said:
or pull the boot.img out of the rom zip and use the flashify app to flash it
Click to expand...
Click to collapse
Can't do since it no longer boots into android, but I tried to do what you say and sideload the zip but I get a "installation aborted" error on CWM
MGREX said:
Can't do since it no longer boots into android, but I tried to do what you say and sideload the zip but I get a "installation aborted" error on CWM
Click to expand...
Click to collapse
What about TWRP?
Sent from my Nexus 4 using Tapatalk
22sl22 said:
What about TWRP?
Click to expand...
Click to collapse
You mean installing TWRP?
BTW that problem is with the kernel I assembled using a CM11 ROM, your zip actually does boot into cyanogenmod but it gets stuck in the CM boot animation
Okay I'm not sure why or how, but this time it booted alright:laugh::highfive::good:
Thank you guys for the assistance, I'll do a full backup in case it decides to crash again so I can do a total wipe and flash a new ROM from scratch
MGREX said:
Okay I'm not sure why or how, but this time it booted alright:laugh::highfive::good:
Thank you guys for the assistance, I'll do a full backup in case it decides to crash again so I can do a total wipe and flash a new ROM from scratch
Click to expand...
Click to collapse
No problem
Do a titanium backup that backs up all your apps with data. Always have a backup so if things do go wrong you can just wipe and restore apps afterwards :good:
Sent from my Nexus 4 using Tapatalk