hello, im in need of some help
i had/have cwm recovery (touch) on my one x, after flashing TripNdroids AOKP rom and can no longer boot to recovery.
i can boot to bootloader, but when i select 'recovery' it begins to load (for a split second) then the htc splash appears and boot into the rom.
i have cwm rom manager on the phone, and have the same outcome when i try 'boot to recovery' from there, and when i try a 'restore' i get the same outcome.
to make matters worse, i have no gapps as i needed to flash them after rom install.
im not to worried at this point, i think its fixable, i just dont have the knowledge, hopefully i will by the time its sorted.
sgb101 said:
hello, im in need of some help
i had/have cwm recovery (touch) on my one x, after flashing TripNdroids AOKP rom and can no longer boot to recovery.
i can boot to bootloader, but when i select 'recovery' it begins to load (for a split second) then the htc splash appears and boot into the rom.
i have cwm rom manager on the phone, and have the same outcome when i try 'boot to recovery' from there, and when i try a 'restore' i get the same outcome.
to make matters worse, i have no gapps as i needed to flash them after rom install.
im not to worried at this point, i think its fixable, i just dont have the knowledge, hopefully i will by the time its sorted.
Click to expand...
Click to collapse
You really should have posted this in the right section. Either way, "fastboot erase cache" from the fastboot menu.
sorry, hopefully a mod will place it correctly.
so my cwm recovery has gone? do i just need to re-install? as i tried this lastnight and i failed.
could you/someone point me in the correct direction please
edit~ lol read wrong, i should be good now, will update later
Can't you try to reflash recovery if you have problems with it?...
Cheers, R
hi,
go to fastboot and try this:
"fastboot erase cache"
il try that later when i get home, to lappy, thanks
Wiping cache doesn't make sense to me, we are trying to boot in the recovery remember? Could you two elaborate?
Cheers, R
fastboot flash recovery recoveryxxxxx.img
Download recovery here: http://forum.xda-developers.com/showthread.php?t=1594819
Follow this:
1. Hold power button down, so that you device wil reboot, at the same time hold volume down button pressed.
2. Now you in the bootloader.
3. Press power button, so that you device go in Fasboot mode.
4. Flash with fastboot the stock recoverie.
5. Re-lock you device again.
6. Boot again into the bootloader, choose fastboot, en choose power down (without usb cable connected).
If you device is powered down, you can plugin the usb cable again.
Let you device charche.
If the led collors green, you can flash a stock rom.
If you not can handle with this, READ THE WIKI http://forum.xda-developers.com/showthread.php?t=1603905
Have pfun Rongogo
There's some terrible advice being thrown around here. Relock the bootloader? Flash a RUU?! Seriously?
Yes, he just needs to erase the cache from fastboot. Yes it's a known issue which has been covered in Trip's thread about a hundred times. Yes he probably should have searched and would have found the answer. No, he doesn't need to reflash his recovery or return to stock or any other ridiculous suggestion.
Honestly, stop and think before you post, and if you're not sure of what you're saying don't say anything. Better no advice than the wrong advice.
Come on. I've been using it. just go to fastboot and in then "fastboot erase cache" then reboot the bootloader and open recovery! You have to do it every time u need to open recovery.
the first answer is the correct answer
sgb101 said:
hello, im in need of some help
i had/have cwm recovery (touch) on my one x, after flashing TripNdroids AOKP rom and can no longer boot to recovery.
i can boot to bootloader, but when i select 'recovery' it begins to load (for a split second) then the htc splash appears and boot into the rom.
i have cwm rom manager on the phone, and have the same outcome when i try 'boot to recovery' from there, and when i try a 'restore' i get the same outcome.
to make matters worse, i have no gapps as i needed to flash them after rom install.
im not to worried at this point, i think its fixable, i just dont have the knowledge, hopefully i will by the time its sorted.
Click to expand...
Click to collapse
I had the exact same issue after installing tripndroids CM9. I freaked out as flashing the recovery again did not solve the issue for me. after about half an hour of trying everything, I tried erasing cache from fastboot and it worked for me.
tkm89 said:
You really should have posted this in the right section. Either way, "fastboot erase cache" from the fastboot menu.
Click to expand...
Click to collapse
^^This is exactly what fixed my problem ^^
Sent from my HTC One X on Leedroid's ROM v5.1.0.
hopscotchjunkie said:
There's some terrible advice being thrown around here. Relock the bootloader? Flash a RUU?! Seriously?
Yes, he just needs to erase the cache from fastboot. Yes it's a known issue which has been covered in Trip's thread about a hundred times. Yes he probably should have searched and would have found the answer. No, he doesn't need to reflash his recovery or return to stock or any other ridiculous suggestion.
Honestly, stop and think before you post, and if you're not sure of what you're saying don't say anything. Better no advice than the wrong advice.
Click to expand...
Click to collapse
My advice is correct, and i think verry much before i post.
I'm not a rookie, I travel a long time around different forums.
Ps: here is the source for the solution
http://forum.xda-developers.com/showthread.php?t=1609190
Regards Rongogo
Rongogo said:
My advice is correct, and i think verry much before i post.
Click to expand...
Click to collapse
All he needs to do to get into recovery is wipe his cache, I hardly think advising him to wipe everything and reinstall the stock operating system is appropriate (or 'correct'). Especially as he'd then need to reinstall his cm9 ROM, and would then still need to wipe his cache to be able to get into recovery.
The thread you linked to is a guide on how to recover a phone which won't boot, which is an entirely different scenario.
It's equivalent to telling a PC user that they need to format their hard drive and reinstall Windows because they've deleted their browser. Yes it will work, in that they'll have their browser back, but it's completely the wrong advice for that particular situation. Which is why I said think before you post, to be sure the advice you're offering is the best advice for the question being asked.
Solving this problem with a RUU is like killing a fly by firing a nuke at it. Although a nuke is fun fun time, while a RUU ain't
It ain't right the recovery reboots over an unknown-state cache though.
Cheers, R
abhimar1128 said:
Come on. I've been using it. just go to fastboot and in then "fastboot erase cache" then reboot the bootloader and open recovery! You have to do it every time u need to open recovery.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=26045096&postcount=8
fastboot erase cache isn't solving my problem, and I still can't get into recovery.
Thanks
sorry it took me a while to get back to you, only just got time to try the the 'clear cache' n fastboot, and it worked a treat. THANK YOU ALL
having spent 5 days without most apps, i dont know how i survived before. also, the AOKP rom, is a little to buggy so im going to look for another to try out.
any one have any decent suggestions.
again thak you all, you guys never fail to come up trumps
Had the same issue, fastboot erase cache solves the problem.
Thanks!
H-Cim said:
Had the same issue, fastboot erase cache solves the problem.
Thanks!
Click to expand...
Click to collapse
Where do you guys dig up a thread like this ? Its almost a year old LOL !
Related
i have a strange problem
my one x seems got bricked.. the phone is continuosly keeps restarting not booting only the part of the venom bootanim. and again restarting
and the problem is sdcard i think
i cant format it. when i'm formatting it after rebooting and getting to CWM all my files are there
also i am not able to relock or run stock ruu to recover my device. the fastboot flash system system.img didn't work,
please help me becouse in repair centere no one been able to repare my device...
tiom7 said:
i have a strange problem
my one x seems got bricked.. the phone is continuosly keeps restarting not booting only the part of the venom bootanim. and again restarting
and the problem is sdcard i think
i cant format it. when i'm formatting it after rebooting and getting to CWM all my files are there
also i am not able to relock or run stock ruu to recover my device. the fastboot flash system system.img didn't work,
please help me becouse in repair centere no one been able to repare my device...
Click to expand...
Click to collapse
if you can get into your bootloader try flashing a boot.img and then try and flash the modules of the kernel you choose... and before that fastboot erase cache and then flash boot.img
Goku80 said:
if you can get into your bootloader try flashing a boot.img and then try and flash the modules of the kernel you choose... and before that fastboot erase cache and then flash boot.img
Click to expand...
Click to collapse
and i have that problem. no one helpd me!
real77055 said:
and i have that problem. no one helpd me!
Click to expand...
Click to collapse
the problem is that. that my fastboot commands don't work properly.. yesterday i delited all my usb drivers and adb sdk htc sync and installed again. to be sure that the problem is not that.
when i'm giving the command fastboot erase cache seems it erased(it's said ok erased inished). but when i'm trying to relock my bootloader its said ok relocked but in bootloader nothing changed . when i'm trying to flash stock recovery in fastboot its said ok finished but the recovery is the same CWM... after that i noticed that i cant change the sd card. even if i formated sd card through recovery or pc seems its formatted but after first reboot to recovery sdcard recovers by itself... in the same condition...and yes. i can't add nothing more to sdcard. in the windows when i mount sdcard it shows that i added. but after first reboot to recovery the ile dissapeard...
tiom7 said:
the problem is that. that my fastboot commands don't work properly.. yesterday i delited all my usb drivers and adb sdk htc sync and installed again. to be sure that the problem is not that.
when i'm giving the command fastboot erase cache seems it erased(it's said ok erased inished). but when i'm trying to relock my bootloader its said ok relocked but in bootloader nothing changed . when i'm trying to flash stock recovery in fastboot its said ok finished but the recovery is the same CWM... after that i noticed that i cant change the sd card. even if i formated sd card through recovery or pc seems its formatted but after first reboot to recovery sdcard recovers by itself... in the same condition...and yes. i can't add nothing more to sdcard. in the windows when i mount sdcard it shows that i added. but after first reboot to recovery the ile dissapeard...
Click to expand...
Click to collapse
why are you relocking your phone...if you do what i said your phone will be up and running again..once that is done then do whatever you want with it and flash an ruu..here is a wiki for you as well
http://forum.xda-developers.com/wiki/HTC_One_X
Goku80 said:
why are you relocking your phone...if you do what i said your phone will be up and running again..once that is done then do whatever you want with it and flash an ruu..here is a wiki for you as well
http://forum.xda-developers.com/wiki/HTC_One_X
Click to expand...
Click to collapse
thank you for trying to help. but i've already explained that my fastboot commands dont work. i cant add anything to my sdcard(mount sdcard in recovery) and delete from sdcard i cant change my recovery i cant adb push files to my sdcard//
when i type fastboot devices its shows my devices code(and i can be sure that fastboot is working properly on my pc and drivers are all ok)
but when i try to change to stock recovery or to another recovery (fastboot flash recovery recovery.img) nothing changed . also can't run the ruu from fastboot. when the ruu tryes to boot my phone to bootloader device began rebooting again.. i see you'r very experienced user please help me....
tiom7 said:
when i type fastboot devices its shows my devices code(and i can be sure that fastboot is working properly on my pc and drivers are all ok)
but when i try to change to stock recovery or to another recovery (fastboot flash recovery recovery.img) nothing changed . also can't run the ruu from fastboot. when the ruu tryes to boot my phone to bootloader device began rebooting again.. i see you'r very experienced user please help me....
Click to expand...
Click to collapse
are you flashing the correct recovery for the firmware version you are on...so if you are on firmware 1.26 you flashing that stock recovery correct?
i can try to help you as much as i can my friend but not that experienced on my One X cause i did not had anything like this happen to me...i can try and help as much as i can...have you read the wiki link i gave you..few options there
Goku80 said:
are you flashing the correct recovery for the firmware version you are on...so if you are on firmware 1.26 you flashing that stock recovery correct?
Click to expand...
Click to collapse
yepp. i cant change my recovery i cant flash even TWRP. in fastboot its said that all flashed OK but the recovery doesnt changed. seems my sdcard is become unwritable??
tiom7 said:
yepp. i cant change my recovery i cant flash even TWRP. in fastboot its said that all flashed OK but the recovery doesnt changed. seems my sdcard is become unwritable??
Click to expand...
Click to collapse
weird man very weird.....not sure then my friend
ok help me out here again cause i just woke up....does the actual phone boot up in bootloader? can you use fastboot commands and what stock recovery are you using? and do not flash TWP recovery cause that is not stock...have you updated the latest clockwork mod recovery
Goku80 said:
are you flashing the correct recovery for the firmware version you are on...so if you are on firmware 1.26 you flashing that stock recovery correct?
i can try to help you as much as i can my friend but not that experienced on my One X cause i did not had anything like this happen to me...i can try and help as much as i can...have you read the wiki link i gave you..few options there
Click to expand...
Click to collapse
yes i did.. i already read the disaster forum searched alot. and tryed almost everything. at first i thought that the problem is in me, but than realized that the problem is in my sdcard. becouse when i tryed to format it through pc or recovery after first reboot all my files resored automatically..
can we open a thread in dev section for devs look on my problem.. i'll buy alot of BEER)) if soemone help me))))
tiom7 said:
yes i did.. i already read the disaster forum searched alot. and tryed almost everything. at first i thought that the problem is in me, but than realized that the problem is in my sdcard. becouse when i tryed to format it through pc or recovery after first reboot all my files resored automatically..
can we open a thread in dev section for devs look on my problem.. i'll buy alot of BEER)) if soemone help me))))
Click to expand...
Click to collapse
no do not open a thread there cause you will get flamed for opening in the wrong section....so the problem is the sdcard then..so you can go into the main homescreens then your phone is not bricked..
to be honest mate you are kinda confusing me now with what is your problem...one minute you say your phone keeps rebooting and now you are saying you are all restored and you have your apps running but y ou can not format.....very confused
Goku80 said:
no do not open a thread there cause you will get flamed for opening in the wrong section....so the problem is the sdcard then..so you can go into the main homescreens then your phone is not bricked..
to be honest mate you are kinda confusing me now with what is your problem...one minute you say your phone keeps rebooting and now you are saying you are all restored and you have your apps running but y ou can not format.....:S very confused
Click to expand...
Click to collapse
but i cant boot my device. it continuosly rebootin and cant go away from bootanimation. in our repair service thay didint help me cos my phon is rooted.. is here anyone who can help me. i don't want to lose my device after 2 weeks of use...
Goku80 said:
no do not open a thread there cause you will get flamed for opening in the wrong section....so the problem is the sdcard then..so you can go into the main homescreens then your phone is not bricked..
to be honest mate you are kinda confusing me now with what is your problem...one minute you say your phone keeps rebooting and now you are saying you are all restored and you have your apps running but y ou can not format.....very confused
Click to expand...
Click to collapse
noo my friend)i can boot only to fastboot and recovery. i have nothing restored. and i have nothing installed. i have tryed everything here. to boot my device but couldnt do that. onle fastboot and recovery. and fastboot commands not working on my device(but fastboot devices shows my devices)
tiom7 said:
but i cant boot my device. it continuosly rebootin and cant go away from bootanimation. in our repair service thay didint help me cos my phon is rooted.. is here anyone who can help me. i don't want to lose my device after 2 weeks of use...
Click to expand...
Click to collapse
like i said the only steps i could think off and you already tried are:
fastboot erase cache in bootloader if you can go in there
flash a boot.img and then flash the modules in recovery
and that is it really....
your saying your fastboot commands do not work so i am confused how to sort this out...strange...are you sure they are not working fine?
did you try flashing a kernel when you was viper x
there is another person(tadeausz,real77055) with such a problem but his problem is not solved and i cant finde him to know what he did...
yes i tried. a flash insertcoin. coredroid ARHD vyper and all the kernels befor. than tryed vypers rom used it for 8 days and in a moment i noticed that my phone is rebooting by itself.
tryed to wipe dalvik flash boot.im erase cache but didn't helped me. the phone is continuously rebooting. can turn of only via fastboot.
tiom7 said:
there is another person(tadeausz,real77055) with such a problem but his problem is not solved and i cant finde him to know what he did...
yes i tried. a flash insertcoin. coredroid ARHD vyper and all the kernels befor. than tryed vypers rom used it for 8 days and in a moment i noticed that my phone is rebooting by itself.
tryed to wipe dalvik flash boot.im erase cache but didn't helped me. the phone is continuously rebooting. can turn of only via fastboot.
Click to expand...
Click to collapse
did you flash modules though
Goku80 said:
did you flash modules though
Click to expand...
Click to collapse
ah M8... but there is no moduls with stock kernel. and also i have no moduls on my sdcard and cant push or add through mount usb
really thank you very very much... but i see my phone is bricked really and i'm the only person with such a stupid brick...((
maybe you know someone who are very experienced in android developmend. i'll pay for helping me(cos in our repair center noone could help me) or i have to buy another phone absurd..
Goku80 is more than capable to help you. Just do exacly what he says and give him correct information about what happends at your end and he'll get you through. Just be precise.
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).
Hi guys,
I rooted my HOX using this guide http://forum.xda-developers.com/showthread.php?t=1843585 . It went ok.
Then I flashed the jb rom, also went perfect. Because i really like sense i wanted to flash the viper rom, then everything went terribly wrong.
I flashed it and when it finished the device began bootlooping. I pressed the on/off button and volume down to boot into recovery, when i select recovery it tries to open but then the device shuts down and begins bootlooping again. So i cannot get in to recovery. I tried to reset recovery using the hox disaster recovery tread, but when i type the commands in cmd it keeps saying failed.
Is my phone ruined now? can this be fixed? can someone please help me or tell me where i can get help?
I tried using the search function but i didn't find anything, i actually don't really know what to search for... :crying:
I really hope someone has a anwser for me .
Thanks in advance.
Caos
If your recover doesn't work, have you tried reflashing clockworkmod recovery via fastboot?
Also, did you wipe data/factory reset before you changed ROMs?
your phone phone is ok since he is unlocked. the bootloop is caused by wrong boot, have you made a back up for the .
Here what you will do:
1-hold power+ vol down until you get the bootloader menu.
2-go to hboot and hit power to access fastboot.
3-connect your phone via USB (you should get fastboot usb).
4-get the boot.img file from the ROM viper copy it and paste in a folder name it for ex fastboot.
5-Enter to this folder, Hold alt+shift and click right click and chose open command window here.
6-type "fastboot erase cache", should write ok.
7-type "fastboot flash boot boot.img", should write ok
8-reflash your rom again via recovery choose fullwipe in aroma installation.
9-reboot your phone.
open command prompt. type c:\whereveryourfastbootis\fastboot erase cache
as long as you can boot into bootloader(and its unlocked), and you didnt flash stuff for a different phone you're OK
Vcek said:
as long as you can boot into bootloader(and its unlocked), and you didnt flash stuff for a different phone you're OK
Click to expand...
Click to collapse
No i'm sure i did not flash anything for another phone:angel:, and i can still get into bootloader.
I will try everything when i get home, i'm at work now, then i will post if it worked.:victory:
Thanks so much!
tomascus said:
If your recover doesn't work, have you tried reflashing clockworkmod recovery via fastboot?
Also, did you wipe data/factory reset before you changed ROMs?
Click to expand...
Click to collapse
I think i tried, but i will try again, probably did something wrong.
Yes i did a factory reset. I think it went wrong because i had a custom kernel and did a full wipe.
Don't worry, when recovery tries to load and the phone reboots it means you need to fastboot erase cache. i had the same problem when switching to a jelly bean rom and kernel. the factory reset wont help this.
~Jeej~
Noobzter said:
your phone phone is ok since he is unlocked. the bootloop is caused by wrong boot, have you made a back up for the .
Here what you will do:
1-hold power+ vol down until you get the bootloader menu.
2-go to hboot and hit power to access fastboot.
3-connect your phone via USB (you should get fastboot usb).
4-get the boot.img file from the ROM viper copy it and paste in a folder name it for ex fastboot.
5-Enter to this folder, Hold alt+shift and click right click and chose open command window here.
6-type "fastboot erase cache", should write ok.
7-type "fastboot flash boot boot.img", should write ok
8-reflash your rom again via recovery choose fullwipe in aroma installation.
9-reboot your phone.
Click to expand...
Click to collapse
I did exactly as you said, and it worked hura! i'm so happy with my viper sense rom !!! EDIT/ I'm totaly going to make a pink theme for myself EDIT/
Thank you, thank you, thank you, thank you so much !
jam256 said:
Don't worry, when recovery tries to load and the phone reboots it means you need to fastboot erase cache. i had the same problem when switching to a jelly bean rom and kernel. the factory reset wont help this.
Click to expand...
Click to collapse
Thank you for comferting me , obviously i don't know much about flasing roms (and i'm a girl so i have the forces of nature against me) fist time i tried to root and flash a custom rom on my desire hd it took me over one week , because i didn't understand anything and had to google every single word in the guide. I just try to follow the guides step by step and then it goes ok, but if something unexpected happens i'm really lost . I'm so glad i could get help here .
Thank you guys so much for helping me out, i wish there is something i could do in return.
Hi, after attempting to flash a custom ROM to my phone I'm experiencing a big problem, the phone will not boot past the HTC screen. This is obviously very frustrating as the phone is pretty much rendered useless.
I am able to get into the HBOOT menu by holding the Power button and Volume Down and from there am able to select Recovery and enter the ClockWork Mod recovery screens. As you can tell I'm a 100% noob and I really just want to revert my phone to a working state. My network is Vodafone UK. I can't find an RUU above version 3.13 which is apparently what I have (so it tries updating 3.13 to 3.13 and obviously fails).
Any help on getting my phone to work again would be very very appreciated, thanks.
VBQ24 said:
Hi, after attempting to flash a custom ROM to my phone I'm experiencing a big problem, the phone will not boot past the HTC screen. This is obviously very frustrating as the phone is pretty much rendered useless.
I am able to get into the HBOOT menu by holding the Power button and Volume Down and from there am able to select Recovery and enter the ClockWork Mod recovery screens. As you can tell I'm a 100% noob and I really just want to revert my phone to a working state. My network is Vodafone UK. I can't find an RUU above version 3.13 which is apparently what I have (so it tries updating 3.13 to 3.13 and obviously fails).
Any help on getting my phone to work again would be very very appreciated, thanks.
Click to expand...
Click to collapse
Download a ROM onto your computer, connect to your phone in recovery, mount the sdcard, move the ROM from your computer onto your phone's sdcard, and flash from recovery. No need for RUU.
Dont forget to wipe.
wipe data/factory reset and format all partitions (except sd card) from recovery.
Go to bananagranolas link in her signature, you'll find everything you need there.
Thanks a lot for your help! I was attempting to flash the JellyTime ROM which I understand must have failed to result in my phone not booting properly. Should I flash a stock ROM or will any ROM suffice?
VBQ24 said:
Thanks a lot for your help! I was attempting to flash the JellyTime ROM which I understand must have failed to result in my phone not booting properly. Should I flash a stock ROM or will any ROM suffice?
Click to expand...
Click to collapse
As long as you are S-OFF and have a custom recovery (CMW or 4EXT) you are able to flash any custom rom you like. Just make sure that you make a full wipe before the flashing (wipe data/factory reset, wipe cache partition, format system or in 4ext recovery just choose format all partitions except sdcard).
That should leave you up and running again.
Okay great!
I used the HTCDev tools to unlock my boot loader which I understand is different to S-OFF? Could that be while the ROM flashing failed originally?
EDIT: Upon trying to flash the JellyTime AKOP Rom I get a message saying install from SD card complete but it's still stuck at the HTC screen...
VBQ24 said:
Okay great!
I used the HTCDev tools to unlock my boot loader which I understand is different to S-OFF? Could that be while the ROM flashing failed originally?
Click to expand...
Click to collapse
If you have an unlocked bootloder, then you have to flash the rom (previous full wipe of course) then reboot bootloader (from advanced options in CWM) and then in fastboot (you should see fastboot usb in red in the phone when plugged to the pc) you have to flash the boot.img inside the rom zip folder.
Extract that file only (not the whole rom) and from a cmd session or terminal as root (located where the boot.img file is) type:
fastboot flash boot boot.img
Once that is done (you will get OKAY. finished near the bottom) you can reboot normally by typing in cmd fastboot reboot or choosing reboot from hboot.
My bootloader now says RELOCKED, how can I unlock it again? (I'm really sorry about this)
VBQ24 said:
My bootloader now says RELOCKED, how can I unlock it again? (I'm really sorry about this)
Click to expand...
Click to collapse
Use the token HTC sent you when u unlocked it. and typing in cmd the fastboot unlock command.
Okay done that, thanks a lot!
I'm now looking in the advanced options of CWM, I can see the option "Reboot Recovery" but no "Reboot Bootloader"?
VBQ24 said:
Okay done that, thanks a lot!
I'm now looking in the advanced options of CWM, I can see the option "Reboot Recovery" but no "Reboot Bootloader"?
Click to expand...
Click to collapse
then just turn the phone off (power off option) and then boot with power + volume down
glevitan said:
then just turn the phone off (power off option) and then boot with power + volume down
Click to expand...
Click to collapse
Okay, I wiped all partitions, installed JellyTime AOKP, restarted, went into fastboot, extracted/flash boot file and the rebooted phone.
The phone will now progress from the HTC screen but is now stuck on a black screen, Windows tried to install drivers but failed....
VBQ24 said:
Okay, I wiped all partitions, installed JellyTime AOKP, restarted, went into fastboot, extracted/flash boot file and the rebooted phone.
The phone will now progress from the HTC screen but is now stuck on a black screen, Windows tried to install drivers but failed....
Click to expand...
Click to collapse
Was the boot.img file flashed successfully?
Yes it said so...
EDIT: Not sure if this is an issue with the ROM of if I'm doing something wrong? I went to the "mounts and storage" section of CWM and clicked all the format options accept sdcard. I then installed ROM, went into fastboot and flashed boot.img, it said OKAY twice then finished. Still stuck at black, backlit screen after HTC screen. ROM is JellyTime by randomblame.
VBQ24 said:
Yes it said so...
Click to expand...
Click to collapse
that is weird. Try flashing a different rom then and see what happens. flash the boot image first and then the the rom in recovery.
glevitan said:
that is weird. Try flashing a different rom then and see what happens. flash the boot image first and then the the rom in recovery.
Click to expand...
Click to collapse
I've just tried flashing the boot image first and then installing JellyTime AOKP, same black screen. Maybe I should try a Gingerbread ROM? That's the Operating system I had before, is there a known working ROM?
VBQ24 said:
I've just tried flashing the boot image first and then installing JellyTime AOKP, same black screen. Maybe I should try a Gingerbread ROM? That's the Operating system I had before, is there a known working ROM?
Click to expand...
Click to collapse
Sorry, have You checked the md5sum of the file? Maybe You have a bad download...if that it Is ok, then try flashing a totally different rom and see what happens.
glevitan said:
Sorry, have You checked the md5sum of the file? Maybe You have a bad download...if that it Is ok, then try flashing a totally different rom and see what happens.
Click to expand...
Click to collapse
No I haven't checked the md5sum of the file, how should I go about doing that?
VBQ24 said:
No I haven't checked the md5sum of the file, how should I go about doing that?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.fab.md5
EDIT: well, don't I feel stupid. I knew full well from reading that your phone wasn't working, but posted a link to an app. Just not paying attention. Sorry about that.
VBQ24,
You can go back to stock by flashing a stock RUU from your PC.
(Edit: You should relock your bootloader first. you can do so from Hboot. There's an option that says relock bootloader or something like that)
The version of the RUU should be equal or greater to the version that came with your phone. Try this v3.13
However, if you want to flash a custom ROM:
You need to downgrade your device first, get s-off and root, then flash a custom ROM
You need to use the Advanced Ace Hack Kit (AAHK), get it from here.
Make sure to read the manual (called 'effin manual) word by word. There are instructions on how to downgrade.
Follow the instructions, and if you have any questions, ask here.
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