Develop Bugs

Unable to flash new roms, recoveries, or PC10IMG

I was attempting to install Cyanogen Mod 9 RC2 on my HTC G2 (Vision - Tmobile Branded) and before I did, I decided to flash a "new" recovery from clockwork. I broke my own rule and used Rom Manager and it seems like the recovery partition is now completely screwed up. Either that or my system is now read only.
I am able to access recovery, bootloader, and even the OS (can still make calls) but if I uninstall an application it will come back on the next boot up such as facebook or even the rom manager. I tried to load PC10IMG from the bootloader, but it only finishes the radio_v2 then it reboots and gets caught in a boot loop. If I go back to try again, it starts over as if no changes were made. Worse still, I've gone as far as to erase the recovery partition only to have it come right back.
I am still showing as S-OFF, but I can't seem to get any changes to stick and I'm not getting any error messages ever. Infact, clockworkmod seems all to eager to say "Install success" when I try to flash another rom or wipe cache & data. Has anyone else been experiencing this issue?
ROM: CM 7.1
Recovery: 5.0.2.7 CWM
I've been at this for a day now and I"m fed up with it, any insight would be a huge help.

ark3typ3 said:
I was attempting to install Cyanogen Mod 9 RC2 on my HTC G2 (Vision - Tmobile Branded) and before I did, I decided to flash a "new" recovery from clockwork. I broke my own rule and used Rom Manager and it seems like the recovery partition is now completely screwed up. Either that or my system is now read only.
I am able to access recovery, bootloader, and even the OS (can still make calls) but if I uninstall an application it will come back on the next boot up such as facebook or even the rom manager. I tried to load PC10IMG from the bootloader, but it only finishes the radio_v2 then it reboots and gets caught in a boot loop. If I go back to try again, it starts over as if no changes were made. Worse still, I've gone as far as to erase the recovery partition only to have it come right back.
I am still showing as S-OFF, but I can't seem to get any changes to stick and I'm not getting any error messages ever. Infact, clockworkmod seems all to eager to say "Install success" when I try to flash another rom or wipe cache & data. Has anyone else been experiencing this issue?
ROM: CM 7.1
Recovery: 5.0.2.7 CWM
I've been at this for a day now and I"m fed up with it, any insight would be a huge help.
Click to expand...
Click to collapse
I would try to reflash recovery thru adb then download fresh rom to install. Not sure if there is any other troubleshooting you could do 1st though.

better yet how about dropping clockwork for 4ext, in mine and many others experience it is far superior on our g2s. and if you insist on clockwork, try to stay away from rom manager. don't flash a pc10img either, if you do the wrong one and there is a radio error you can easily brick your phone (many people with soff seem to think this is a good idea but it can be a terrible one)
then reflash a new rom, if you like cm7 I suggest elitemod cm7, but the choice is yours
never heared of these specific problems with all my years in android but I'm sure you will be happy with the changes I suggested and unless I'm missing something this should also fix your problems
Sent from my HTC Vision using xda premium

demkantor said:
better yet how about dropping clockwork for 4ext, in mine and many others experience it is far superior on our g2s. and if you insist on clockwork, try to stay away from rom manager. don't flash a pc10img either, if you do the wrong one and there is a radio error you can easily brick your phone (many people with soff seem to think this is a good idea but it can be a terrible one)
then reflash a new rom, if you like cm7 I suggest elitemod cm7, but the choice is yours
never heared of these specific problems with all my years in android but I'm sure you will be happy with the changes I suggested and unless I'm missing something this should also fix your problems
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Well you can't exactly flash 4EXT without first having the app to download and install it for you.
But here is the zip file for 4EXT Touch Recovery 1.0.0.5 RC5 specifically for the G2/DZ, which can be renamed to PC10IMG.zip and placed on the SD card to be flashed via fast boot (it contains ONLY the recovery, it won't flash over hboot, radio or any of that).
http://xlu.be/g2/4EXT_Recovery_Touch_v1.0.0.5_RC5.zip
Code:
MD5 (4EXT_Recovery_Touch_v1.0.0.5_RC5.zip) = dfc5dc1e4aee18fdea6268345e3dad22
I never did find a place 'online' to download the recovery images direct, only thru the app was I ever able to download it to my Zip card. (PS: I recommend getting the paid version of the Recovery control from the Google Play market place to support the developer, it'll also let you set options like not backing up the caches).

not @ a comp right now but you can get the image and flash through fastboot, I did this to try it out free, liked it so much right away so I purchased the app through the market just to support the dev. but either way, its all prefrence
Sent from my HTC Vision using xda premium

I tried to flash the recovery img that kbeezie gave me both through PC10IMG.zip (verified MD5) and again through fastboot flash with just the straight img from inside the zip. Neither method worked and now I'm caught in a boot loop until I pull the battery. I've even gone as far as to erase the recovery, do you think formatting the recovery and then flashing again would yield better results?

ark3typ3 said:
I tried to flash the recovery img that kbeezie gave me both through PC10IMG.zip (verified MD5) and again through fastboot flash with just the straight img from inside the zip. Neither method worked and now I'm caught in a boot loop until I pull the battery. I've even gone as far as to erase the recovery, do you think formatting the recovery and then flashing again would yield better results?
Click to expand...
Click to collapse
A boot loop trying to boot normally? or trying to boot into recovery. If you haven't flashed a ROM yet, then naturally you would need to go into the Recovery to do so first.
Are you aware of how to get into Recovery?
PS: NEVER NEVER NEVER NEVER NEVER 'erase' the recovery, you should always have a recovery on there, if you can't get anything going with fast boot then you're probably going to be screwed. Furthermore how did you even 'erase' it ?
You should be able to simply flash the recovery, reboot, hold volume down + power to get into recovery, do a factory reset/wipe, and flash a new rom form SD card.
Play it safe and provide A LOT more information in your next reply.
1) What's your hboot info (the whole boot loader screen, including radio version).
2) What did you do exactly?
---------- Post added at 07:38 PM ---------- Previous post was at 07:29 PM ----------
By the way you might want to hop onto #G2Root on FreeNode IRC for some live assistance, you seem to be doing a lot of unnecessary and potentially bricking stuff with way you're just 'trying everything'.

kbeezie said:
A boot loop trying to boot normally? or trying to boot into recovery. If you haven't flashed a ROM yet, then naturally you would need to go into the Recovery to do so first.
Are you aware of how to get into Recovery?
PS: NEVER NEVER NEVER NEVER NEVER 'erase' the recovery, you should always have a recovery on there, if you can't get anything going with fast boot then you're probably going to be screwed. Furthermore how did you even 'erase' it ?
You should be able to simply flash the recovery, reboot, hold volume down + power to get into recovery, do a factory reset/wipe, and flash a new rom form SD card.
Play it safe and provide A LOT more information in your next reply.
1) What's your hboot info (the whole boot loader screen, including radio version).
2) What did you do exactly?
---------- Post added at 07:38 PM ---------- Previous post was at 07:29 PM ----------
By the way you might want to hop onto #G2Root on FreeNode IRC for some live assistance, you seem to be doing a lot of unnecessary and potentially bricking stuff with way you're just 'trying everything'.
Click to expand...
Click to collapse
A boot loop trying to boot into recovery. I can still pull out the battery for a few seconds and boot into normal.
----------------------------------------------------
HBOOT INFO
----------------------------------------------------
VISION PVT ENG S-OFF
HBOOT-0.76.2000 (PC1010000)
MICROP-0425
RADIO-26.06.02.27_M
eMMC-boot
Aug 20 2010, 16:51:01
----------------------------------------------------
I should also mention that I've been doing this for a while, but this is the first time I haven't been able to just flash a new recovery or rom...it's vexing. I'm aware that what I'm doing is risky and I'm being careful to check steps and MD5s the whole way with a couple of chances taken where appropriate.

ark3typ3 said:
A boot loop trying to boot into recovery. I can still pull out the battery for a few seconds and boot into normal.
Click to expand...
Click to collapse
If you can boot into normal, and you are rooted then try installing a new recovery via either rom manager (if you want clockworkmod) or 4EXT recovery control (which I prefer, note my signature) then reboot into recovery.
Sent from my T-Mobile G2

kbeezie said:
If you can boot into normal, and you are rooted then try installing a new recovery via either rom manager (if you want clockworkmod) or 4EXT recovery control (which I prefer, note my signature) then reboot into recovery.
Sent from my T-Mobile G2
Click to expand...
Click to collapse
I would gladly do that, and believe me I've tried, but it's not working. If I go into Rom Manager and attempt to flash the clockwork recovery it will "succeed" and then do nothing, or it will fail but still act like it succeeded and provide me with a blank confirmation window with a yes button and a no button. 4EXT didn't work either though it definitely looked interesting....

ark3typ3 said:
I would gladly do that, and believe me I've tried, but it's not working. If I go into Rom Manager and attempt to flash the clockwork recovery it will "succeed" and then do nothing, or it will fail but still act like it succeeded and provide me with a blank confirmation window with a yes button and a no button. 4EXT didn't work either though it definitely looked interesting....
Click to expand...
Click to collapse
List out your exact phone specs and included software:
Phone Information
example:
T-Mobile (Carrier)
G2 (or in your case may be HTC Desire-Z)
HBoot information
Example of Mine:
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1010000)
MICROP-0425
RADIO-26.13.04.19_M
eMMC-boot
Sep 8 2012,15:56:38
Rom
Examples:
Cyanogenmod 7
"Stock" (i.e.: same one phone came with), and if Stock what software version?
Methods
What exact methods were used to unlock/root/etc the phone?

Fastboot is the safest method for flashing recoveries (or radio or spls) how did you go about it with fastboot? When in fastboot mode type
fastboot devices
If you see yours continue
fastboot flash recovery recovery.img
fastboot reboot bootloader
Of course you have to point fastboot to the place the recovery image is, and either name it recovery.img or change the command
When you do this do you get an error or is all seemingly well until you try and boot into recovery?
Sent from my GT-I9100 using xda premium

demkantor said:
Fastboot is the safest method for flashing recoveries (or radio or spls) how did you go about it with fastboot? When in fastboot mode type
fastboot devices
If you see yours continue
fastboot flash recovery recovery.img
fastboot reboot bootloader
Of course you have to point fastboot to the place the recovery image is, and either name it recovery.img or change the command
When you do this do you get an error or is all seemingly well until you try and boot into recovery?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
All is seemingly well, it just won't allow any other recoveries but CWM. If I put CWM (5.0.2.7) on it gives me recovery back but when I try to flash a different rom it just stays at Cyanogen 7.1 (Even though it says it succeeded). Trying the 4EXT recovery got rid of CWM, but I can't boot it because it gets stuck in a boot loop until I pull the battery to clear the recovery flag.
I used the exact commands you described and it says it succeeds...

ark3typ3 said:
All is seemingly well, it just won't allow any other recoveries but CWM. If I put CWM (5.0.2.7) on it gives me recovery back but when I try to flash a different rom it just stays at Cyanogen 7.1 (Even though it says it succeeded). Trying the 4EXT recovery got rid of CWM, but I can't boot it because it gets stuck in a boot loop until I pull the battery to clear the recovery flag.
I used the exact commands you described and it says it succeeds...
Click to expand...
Click to collapse
Did you make sure to do a Factory Reset and Wipe (within the Recovery) before applying Cyanogenmod or a different recovery? (flashing a recovery without first wiping will of course sort of 'mix' up whatever you had on there plus new stuff, and as such would break it).

wiping from within recovery will not wipe recovery, the only way to "wipe" recovery is to erase recovery, which isn't a good idea. if you want to ever change recoveries just flash the new one over the old, there will not be a conflict.
as to your continued problem I suggest logging on to freenode #g2root, if there is a chance to fix your phone you'll have the best luck there as testing can be done in real time
Sent from my HTC Vision using xda premium

kbeezie said:
Did you make sure to do a Factory Reset and Wipe (within the Recovery) before applying Cyanogenmod or a different recovery? (flashing a recovery without first wiping will of course sort of 'mix' up whatever you had on there plus new stuff, and as such would break it).
Click to expand...
Click to collapse
Yes I did wipe, I also have tried CM7.2, CM9 RC1 (Build 2), and CM7.1 (current) and they all have the same result. They succeed installation, then they get stuck in a boot loop, then if I pull the battery, it boots up fine with all my settings as if I had never done any of it.
I'm looking for a brute force way to wipe the OS and start completely fresh without harming fastboot or recovery. I'm leaning towards it being a hardware issue, but the issue is a bit confusing because everything is succeeded and I'd have expected an error message of some kind...

demkantor said:
wiping from within recovery will not wipe recovery, the only way to "wipe" recovery is to erase recovery, which isn't a good idea. if you want to ever change recoveries just flash the new one over the old, there will not be a conflict.
as to your continued problem I suggest logging on to freenode #g2root, if there is a chance to fix your phone you'll have the best luck there as testing can be done in real time
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I have gone to the IRC...no answered me.

well of course people aren't always avalible to chat on freenode, try hopping on after work hours, of course this varries depends where you live. I find there are many people around about 6-11pm central time
as for wiping, the cleanest wipe is fastboot -w
your issue is very strange to me and I feel you have a curropt recovery, I would attempt flashing a new one but without your phone in front of me it is hard to troubleshoot these rare problems over xda
try freenode again, good luck!
Sent from my HTC Vision using xda premium

demkantor said:
well of course people aren't always avalible to chat on freenode, try hopping on after work hours, of course this varries depends where you live. I find there are many people around about 6-11pm central time
as for wiping, the cleanest wipe is fastboot -w
your issue is very strange to me and I feel you have a curropt recovery, I would attempt flashing a new one but without your phone in front of me it is hard to troubleshoot these rare problems over xda
try freenode again, good luck!
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I agree, I'll try again later but this is the stuff I got when I ran fastboot -w
Code:
erasing 'userdata'...
OKAY [ 0.410s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
Can't determine partition type.
OKAY [ 0.010s]
erasing 'cache'...
OKAY [ 0.229s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
Can't determine partition type.
OKAY [ 0.009s]
finished. total time: 0.663s
Not sure if that's important, but the Can't determine partition type seems suspicious to me.

ark3typ3 said:
Not sure if that's important, but the Can't determine partition type seems suspicious to me.
Click to expand...
Click to collapse
Probably because when you wiped it previously, it was not "automatically formatted" as such has no partitions (or not formatted).

Screwed up my One X

I tried installing a custom rom today and I think I messed up really bad, because my phone does not get pass the boot screen and I cannot enter the recovery setting. I think I messed up after entering
fastboot flash boot boot.img
in the command prompt and restarting because I forgot to put the rom zip on my phone. Since then I could not get pass the boot screen and even tried running a backup using CWM, but it didn't help. I then managed to mount my phone and put the rom onto it and installed it, but again it didn't help.
Now my phone can only enter the bootloader, I select hboot and fastboot, but nothing else works. Everytime I select recovery or factory reset I get the htc boot screen and it gets stuck. Does anyone have any solutions?
Thanks

did u backup your phone rom???
if you did u can go to recovery and restore it
and never try to change rom again trust me in that
otherwise i can't help bcuz i did the same mistake

I did make a backup, but like I said I can't enter recovery anymore, so I can't load the backup.
Thanks for trying to help anyway though.

fastboot erase cache
Often fixes recovery problems.

BenPope said:
fastboot erase cache
Often fixes recovery problems.
Click to expand...
Click to collapse
Still not working, thanks anyway.

What HBOOT version do you have and what custom ROM are you trying to install?
edit: you didn't need to restart after changing boot.img cause in Recovery you can just go Advanced and then mount USB and copy the ROM or whatever files you want that way.

BlueSingA said:
What HBOOT version do you have and what custom ROM are you trying to install?
edit: you didn't need to restart after changing boot.img cause in Recovery you can just go Advanced and then mount USB and copy the ROM or whatever files you want that way.
Click to expand...
Click to collapse
I have hboot 1.39.0000 and I was trying to install the latest cyanogenmod cm-10-20130106-NIGHTLY-endeavoru.
Yeah I realized this after I restarted and did it get the zip onto the phone. I think I installed it, but the phone is still stuck on the boot screen
UPDATE: Okay I've managed to install CWM recovery, so I think I'm making progress

You had to flash CWM again? Odd..
Anyway, if you happen to encounter the same problem with CM10 I suggest you try some other custom ROM.. Just make sure you "fastboot flash boot boot.img" and then "fastboot erase cache", and if for some reason you decide to format the sdcard or simply forget to add in the ROM zip, you can do it in Recovery when you mount the device as USB under Advanced options. Best of luck!

BlueSingA said:
You had to flash CWM again? Odd..
Anyway, if you happen to encounter the same problem with CM10 I suggest you try some other custom ROM.. Just make sure you "fastboot flash boot boot.img" and then "fastboot erase cache", and if for some reason you decide to format the sdcard or simply forget to add in the ROM zip, you can do it in Recovery when you mount the device as USB under Advanced options. Best of luck!
Click to expand...
Click to collapse
Yeah CWM didn't load up, but I got it working again. Well it seems I'm back to getting the rom to install and being stuck at the boot screen again, so maybe I just need to use a different rom. Thanks for the help though

Okay, I've tried installing a few roms, but unfortunately I'm still on the boot screen, I can sometimes even reach the cyanogenmod boot screen, but get stuck there. I've read that this might be kernel issue, does anyone have any ideas?

CM10 requires a special boot.img for newer hboots. Check post 9308 in CM10 thread.
Sent from my EndeavorU using xda app-developers app

TToivanen said:
CM10 requires a special boot.img for newer hboots. Check post 9308 in CM10 thread.
Sent from my EndeavorU using xda app-developers app
Click to expand...
Click to collapse
You are a goddamn hero! Thanks, this solved everything.

No problem!
Sent from my EndeavorU using xda app-developers app

Stuck on Pink Unicorn bootloader ICJ first time

First time installing custom rom.
Installed lastest one twice both times stuck on this bootoader screen stating "INITIATING SWAGGER" lol
Here is the page
http://forum.xda-developers.com/showthread.php?t=2052610
I did a MD5 checksum on the zip file after transferring to phone, checked out.
I used the One X toolkit v2.2 to unlock bootloader and install TWRP v2.3.3, then I downloaded the ROM and placed it on the phone. I entered recovery and installed and then wiped.
Not sure what the problem is

ps_jw3 said:
Not sure what the problem is
Click to expand...
Click to collapse
Well it could be a couple things. Maybe you don't have enough swagger to start the rom? Didn't follow the installation instructions properly. Or the most likely one is didn't flash the boot.img in fastboot.
The rom works 100% so you must have messed up som where.
Make sure you wipe data, system, dalvic cache and cache under custom recovery. Boot into bootloader and select fastboot and open CMD on your computer.
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
Flash rom
Done.
Easy as pie and hell boot loops like the one your experiencing now happen quite often. Just restart and try again.
Sent from my HTC One X using xda app-developers app

Tw1tchy said:
Well it could be a couple things. Maybe you don't have enough swagger to start the rom? Didn't follow the installation instructions properly. Or the most likely one is didn't flash the boot.img in fastboot.
The rom works 100% so you must have messed up som where.
Make sure you wipe data, system, dalvic cache and cache under custom recovery. Boot into bootloader and select fastboot and open CMD on your computer.
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
Flash rom
Done.
Easy as pie and hell boot loops like the one your experiencing now happen quite often. Just restart and try again.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I thought it was an option to flash via fastboot or use recovery.
Anyway by "Flash rom" I assume use recovery.
BTW do you know of any windows 8 drivers that work with the phone?
Edit: got it working no worries

ps_jw3 said:
I thought it was an option to flash via fastboot or use recovery.
Anyway by "Flash rom" I assume use recovery.
BTW do you know of any windows 8 drivers that work with the phone?
Click to expand...
Click to collapse
You have to flash the boot.img in fastboot if your device is S-ON which in no doubt it probably is. There are some Windows programs and batch files that can do it for you but personally using those 3 commands is the easiest and safest way.
Flash only the rom .zip in recovery.
Install HTC One X driver on Windows 8
I see your quite new to XDA so I recommend you to get familiar with the search button. If you have a problem with your device XDA is probably the #1 place to get help. I wouldnt doubt someone else has had the same problem as you so a quick search in our forums could help you find your way. Also having a look at the forum rules couldn't hurt.
Nice choice choosing ICJ as your first rom! It's one of my favorites too but also check out ViperX and TripNRaVeR's kernels.

ICJ
Hi there good choice in rom as you can see i am new to but been on ICJ since oct and its really good and all the guys there are more than willing to help and are good guys.
Matt

There is a very good tutorial in the op of the thread you can check and follow the easy steps there and you will be good to go.
Great choice mate best rom I used so far.
Sent from my HTC One X using xda premium

[Very serious]Non-booting/non-changing/not working problem

I woke up today to a bootloop. After pulling out the battery, I cant turn it on, it was stuck at the google logo. I thought it was some rom issue or something. When I had the time, in the afternoon, I just boot to recovery, and wiped data+sd card. Turns out sd card was not wiped.
Just now, I found a way to boot it. (AFTER WIPING DATA) I used the gnex toolkit and boot with insecure image, and guess wat? My old rom boots. Everything was the way it was, and then it crashed and stuck on the google logo again.(I made sure i wiped things two to three times, data and sd) I did a few experiments:
1) Flash using ODIN
2) Flash CWM using toolkit--it changed back to twrp after reboot
3) Changing the icon on my homescreen after boot--- everything was the same again after booting
4) Flash stock image using toolkit
5) Wipe data using manual adb
6) Try to lock my bootloader
Everything I tried changing, change back to the original state after reboot. What is the problem?
Device: Galaxy Nexus
ROM: Purity 7 sept release
Kernel: Fancy r42
Logs in twrp are showing updating partition, not FAIL. So I really don't think there is a need to show the recovery log.
HELP ME!

are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.

player911 said:
are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.
Click to expand...
Click to collapse
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.

jacktay94 said:
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.
Click to expand...
Click to collapse
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Yup,I tried it already thru toolkit. Not working either.

Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.

SoHaunted said:
Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.
Click to expand...
Click to collapse
i did adb bro, its the last thing i tried, i learnt and try.
Sent to Samsung centre, they told me its my flash IC thats blown. sobs

[Q] boot problems cm11

im having problems upgrading to cm11 i already know how to wipe data, cahe, dalvik and install the roms the problem is it boots then on the cyanogen logo it freezes then reboots and keeps doing it ive tried factory reset redownload the rom and gapps but nothing seems to work
i am clockwork recovery 6
cm11
gapps 4.4.2 core 1-16

What exact version of cwm do you have, also try flashing the boot.img on the phone. Extract the zip, find the boot.img and place it in the root of your platform tools folder on you're computer, boot into fastboot on your phone, initiate the command: fastboot flash boot boot.img
It will send the boot. If you're on Mac do: ./fastboot flash boot boot.img
If it is a confirmed write of the boot.img, reboot the device.
Sent from my Rezound using xda-developers app. CyanogenMod 11. S-off

my clockworkmod is 6.0.3.2
Sent from my ADR6300 using Tapatalk

S-off or s-on? If s-on I would suggest flashing the boot.img via the command:
fastboot flash boot boot.img
You say you can get past the boot screen of CM 11? Its more than likely you need to flash the boot.img in fastboot.
Sent from my Rezound using xda-developers app. CyanogenMod 11. S-off

javinesteves said:
im having problems upgrading to cm11 i already know how to wipe data, cahe, dalvik and install the roms the problem is it boots then on the cyanogen logo it freezes then reboots and keeps doing it ive tried factory reset redownload the rom and gapps but nothing seems to work
i am clockwork recovery 6
cm11
gapps 4.4.2 core 1-16
Click to expand...
Click to collapse
df /system please, even tho it should be fine
I have a feeling your inc is just not stable with the cpufreq stock speeds

zachf714 said:
df /system please, even tho it should be fine
I have a feeling your inc is just not stable with the cpufreq stock speeds
Click to expand...
Click to collapse
so what do i do i get an error with fastboot that remote not allowed

javinesteves said:
so what do i do i get an error with fastboot that remote not allowed
Click to expand...
Click to collapse
your bootloader is locked, is it not ? if it is not try fastboot erase cache then flash a recovery

zachf714 said:
your bootloader is locked, is it not ? if it is not try fastboot erase cache then flash a recovery
Click to expand...
Click to collapse
my bootloader is unlocked and when i flash the boot.img it still reboots mainly when i use the playstore

javinesteves said:
my bootloader is unlocked and when i flash the boot.img it still reboots mainly when i use the playstore
Click to expand...
Click to collapse
Those things do not correlate, that has to do with the phone ram going to zip and the system not being able to reclaim it
Sent from my SCH-I535 using Tapatalk

zachf714 said:
Those things do not correlate, that has to do with the phone ram going to zip and the system not being able to reclaim it
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
so what do i do? im tired of cm7

javinesteves said:
so what do i do? im tired of cm7
Click to expand...
Click to collapse
Lower the clock speed and deal with the lag
Sent from my SCH-I535 using Tapatalk