first, sorry if this is the wrong section.
my phone right now is stuck booting to the white htc evo screen, sitting for a second, then rebooting back the the white screen, and just looping like that.
before it started doing that, i was on my phone, with bootmanager, i installed jared's ics rom to a slot, and then i booted to it. the install of the gapps wasnt quite working correctly, so i was gonna install it to the phone then nadroid, then put it in a slot. so i when straight from my slot 1 rom, to recovery, flashed the phonerom update.zip then did a backup of my phonerom before installing the ics rom. after doing the backup, i installed the new rom, and gapps, hit reboot, and now im looping.
thats the best description of my situation, i really hope someone can help out, if any more information is needed, let me know
thanks in advance
-Alex
I would best do a full wipe and restore a backup if possible, then try to reconfigure bootmanager. Did you check that 'flash large boot.img' option?
i cannot get into recovery, i forgot to mention that. is there a way to do that over adb? i have nands and roms on my computer
thanks for quick reply
aadcrasher said:
i cannot get into recovery, i forgot to mention that. is there a way to do that over adb? i have nands and roms on my computer
thanks for quick reply
Click to expand...
Click to collapse
As an it just keeps rebooting when you try to go to the bootloader?
And well the only way is if you were to extract the boot image of a working rom, and flashed it using fastboot; and no problem.
i can get into bootloader, but not recovery. and i dont think i have any .img's
aadcrasher said:
i can get into bootloader, but not recovery. and i dont think i have any .img's
Click to expand...
Click to collapse
What happened when you choose recovery? Have to tried re-flashing a recovery?
Also, extract a rom zip, then copy the boot.img from that rom into your adb tools folder. From the bootloader, select fastboot, connect to pc, from adb run:
fastboot flash boot boot.img
fastboot reboot
i was thinking i should try flashing a recovery, but i didnt know if that would mess it up. when i select recovery, it does the same bootloop. im gonna try that with fastboot
tried that with fastboot, and no dice. gonna find a recovery and flash it, see what happens
actually, i pushed the boot.img, now its booting the ics rom, which is not the boot.img that i pushed
aadcrasher said:
i was thinking i should try flashing a recovery, but i didnt know if that would mess it up. when i select recovery, it does the same bootloop. im gonna try that with fastboot
tried that with fastboot, and no dice. gonna find a recovery and flash it, see what happens
actually, i pushed the boot.img, now its booting the ics rom, which is not the boot.img that i pushed
Click to expand...
Click to collapse
The boot may have been corrupted and went with the old rom.
Well see if you can get into recovery, do a full wipe > new rom > re-try bootmananger.
it didnt boot successfully, but now i can get into recovery. its still acting a little strange. like i just did a wipe and factory reset, and it still tried to boot into the ics rom? maybe its messing up cause of bootmanager. idk.
im gonna flash a new recovery. i try to boot into the recovery, and it goes to white screen, then reboots, and goes into the rom
i cant get anything to work/stick, i flashed a recovery (cwm) and it looked like it was gonna work, then i couldnt flash something on my sd, it said it couldnt find it. so confused
i cant get anything to work/stick, i flashed a recovery (cwm) and it looked like it was gonna work, then i couldnt flash something on my sd, it said it couldnt find it. so confused
aadcrasher said:
i cant get anything to work/stick, i flashed a recovery (cwm) and it looked like it was gonna work, then i couldnt flash something on my sd, it said it couldnt find it. so confused
Click to expand...
Click to collapse
I would try amon ra recovery; CWM has caused known problems for some users.
any chance of a link?
nvm, its just under the cwm links on the page i found earlier
ya, it still doesnt see my sd. and using fastboot to install the boot.img doesnt seem to be working either
aadcrasher said:
ya, it still doesnt see my sd. and using fastboot to install the boot.img doesnt seem to be working either
Click to expand...
Click to collapse
For the sd card, try this > http://forum.xda-developers.com/showthread.php?t=695243
I'm heading out now; hopefully someone else can take over.
okay, thanks for the help
that did the trick to make it recognize my sd, but still cant get it to boot
aadcrasher said:
okay, thanks for the help
Click to expand...
Click to collapse
No problem man.
i cant get cache to unmount in recovery, and i cant get the phone to hold a recovery, i have to keep flashing via fastboot
Related
Hey, I got a soft brick so I'm going to use the unroot method here but I just wanted to make sure it would work.
S-OFF, Hboot 2.1
Also, I'll still be able to root and go back to an old nandroid if this all works out, correct?
It should work. Yes, you will be able to re-root and restore a nandroid once you have completed everything again.
Might throw out your issue first, to see if someone can help you fix without having to go through all that work of unrooting and re-rooting again.
Let's hope so. I'm knocking on wood that I won't have to throw my EVO down some stairs and go get a new one.
Firstly, it is unclear (at least to me) what you mean by "soft brick". Secondly, the link you posted is to a thread that is outdated and was retired by the OP. Or did you mean this thread?
http://forum.xda-developers.com/showthread.php?t=838448
To answer your second question, with S-off you can just go into recovery, do a wipe and then restore your NAND back-up from there. Try just wiping the cache and dalvik cache before restoring. If your phone still gives you problems, you may need to do a full wipe and do a fresh install of your favorite rom.
Ok things are more complicated than I had originally implied.
I can't boot into recovery--still SOFF but when I try to get into recovery I'm getting the red triangle.
Should I try the fix broken recovery option?
tubazeppelin said:
Ok things are more complicated than I had originally implied.
I can't boot into recovery--still SOFF but when I try to get into recovery I'm getting the red triangle.
Should I try the fix broken recovery option?
Click to expand...
Click to collapse
Now we're getting somewhere. Yes, if you can get the recovery to work, it will make the process less difficult for you. Can you boot normally? If so, use ROM Manager to flash the recovery on it. If it doesn't boot into clockwork, try using ROM Manager to flash an alternate recovery (Amon RA) and then try booting into recovery.
If your phone doesn't boot at all, you're going to have to push the recovery image onto the phone via fastboot adb. Worse case scenario would be to run the RUU and start over.
rugedraw said:
Now we're getting somewhere. Yes, if you can get the recovery to work, it will make the process less difficult for you. Can you boot normally? If so, use ROM Manager to flash the recovery on it. If it doesn't boot into clockwork, try using ROM Manager to flash an alternate recovery (Amon RA) and then try booting into recovery.
If your phone doesn't boot at all, you're going to have to push the recovery image onto the phone via fastboot adb.
Click to expand...
Click to collapse
Yeah, no dice on getting it to boot. Stick on the HTC EVO 4G white screen and goes nowhere. I got into this mess trying to apply the GPS fix for CM7 and when i tried to nandroid back I got loopy loops.
So should I just use the recovery fix listed there or can I just download CM 3.0.0.5 and push that via fastboot? All my nandroids are via CM.
tubazeppelin said:
Yeah, no dice on getting it to boot. Stick on the HTC EVO 4G white screen and goes nowhere. I got into this mess trying to apply the GPS fix for CM7 and when i tried to nandroid back I got loopy loops.
So should I just use the recovery fix listed there or can I just download CM 3.0.0.5 and push that via fastboot? All my nandroids are via CM.
Click to expand...
Click to collapse
I would download Amon recovery and flash that via adb; I recommend staying away from clockwork - read about too many users running into issues with it, especially that 3.0.0.5 version.
tubazeppelin said:
Yeah, no dice on getting it to boot. Stick on the HTC EVO 4G white screen and goes nowhere. I got into this mess trying to apply the GPS fix for CM7 and when i tried to nandroid back I got loopy loops.
So should I just use the recovery fix listed there or can I just download CM 3.0.0.5 and push that via fastboot? All my nandroids are via CM.
Click to expand...
Click to collapse
I would suggest using Amon Ra recovery. I like it better, and personally have had far less issues with it. Attatched is a PC36IMG of Amon Ra 2.3. Put it on the main directory of your SD card, name it exactly PC36IMG, and boot to bootloader, and select yes to update. That should flash Amon Ra's V2.3 recovery for you. If it's successful, see if it works. The only problem with this, that I see, is you wouldn't be able to restore your previous clockwork backups. However, if that did go successful, and you were able to boot into a rom, you could use ROM manager to flash clockwork back, then you could restore your backups. Hope you get it booted up.
EDIT: If you do end up needing to unroot, just remember that if you initially used unrevoked to root, or used unrevoked forever at any time, you're not going to be able to turn S on without having a custom recovery. Becase as far as I know, you need to flash the Unrevoked S on tool in recovery if you used unrevoked to begin with. Otherwise S is permanently off.
tubazeppelin said:
Yeah, no dice on getting it to boot. Stick on the HTC EVO 4G white screen and goes nowhere. I got into this mess trying to apply the GPS fix for CM7 and when i tried to nandroid back I got loopy loops.
So should I just use the recovery fix listed there or can I just download CM 3.0.0.5 and push that via fastboot? All my nandroids are via CM.
Click to expand...
Click to collapse
Yea, try the recovery fix. If unsuccessful getting CW to flash, remember you can always try to flash Amor RA recovery just to be able to wipe and flash a working rom. Once you get the phone to boot, you can download ROM manager, flash clockwork and then restore to your CW NAND that is stored on your SD card. I've had to do this in the past.
Thanks EVERYONE! Come to the DC area and the beer is on me (or if you're a mobile dev and want a job, hit me up)
Worked like a charm.
PS I copied down the error message I got when it was trying to install, wondering if I should be worried about this:
Microp OK
Radio_v2 FAIL pu
everything else OK
Bootloader FAIL ic
I renamed my recovery file and everything loaded up fine, just wondering if I should be worried about any of that
tubazeppelin said:
Thanks EVERYONE! Come to the DC area and the beer is on me (or if you're a mobile dev and want a job, hit me up)
Worked like a charm.
PS I copied down the error message I got when it was trying to install, wondering if I should be worried about this:
Microp OK
Radio_v2 FAIL pu
everything else OK
Bootloader FAIL ic
I renamed my recovery file and everything loaded up fine, just wondering if I should be worried about any of that
Click to expand...
Click to collapse
Really not sure. That goes beyond my scope of trial and error knowledge.
Well thanks anyway.
Looks like booting back into CWM is no longer an option for me--everything defaults to Amon_RA (even when trying to switch through ROM manager). Guess I can't load my old nandroids so I'm stuck rebuilding.
Oh well...worse things could have happened.
tubazeppelin said:
Well thanks anyway.
Looks like booting back into CWM is no longer an option for me--everything defaults to Amon_RA (even when trying to switch through ROM manager). Guess I can't load my old nandroids so I'm stuck rebuilding.
Oh well...worse things could have happened.
Click to expand...
Click to collapse
So choosing 'flash clockworkmod recovery' from rom manager doesnt work for you? weird. Try letting it flash, and then instead of rebooting to recovery from within rom manager, boot to recovery manually, from teh bootloader. see if that works.
k2buckley said:
So choosing 'flash clockworkmod recovery' from rom manager doesnt work for you? weird. Try letting it flash, and then instead of rebooting to recovery from within rom manager, boot to recovery manually, from teh bootloader. see if that works.
Click to expand...
Click to collapse
Well I tried that the first time and nothing really worked out--got the same loops and had to do the whole dance again.
Tried it again after your post and it worked. Hot damn.
Getting rid of CWM as we speak and going back to RA, which was my first and only recovery for so long.
tubazeppelin said:
Well I tried that the first time and nothing really worked out--got the same loops and had to do the whole dance again.
Tried it again after your post and it worked. Hot damn.
Getting rid of CWM as we speak and going back to RA, which was my first and only recovery for so long.
Click to expand...
Click to collapse
So strange, but glad it worked for you. And yea, staying on RA will be your best bet.
k2buckley said:
So strange, but glad it worked for you. And yea, staying on RA will be your best bet.
Click to expand...
Click to collapse
Seemed to be an issue with ROM Manager. So weird--I'm so used to everyone over in Heroland swearing by CWM. I'm glad I'm back to a spot where RA is king.
Anyway I uninstalled ROM manager and am just not going to screw with it anymore. GB has a "reboot to recovery" option for a reason.
tubazeppelin said:
Seemed to be an issue with ROM Manager. So weird--I'm so used to everyone over in Heroland swearing by CWM. I'm glad I'm back to a spot where RA is king.
Anyway I uninstalled ROM manager and am just not going to screw with it anymore. GB has a "reboot to recovery" option for a reason.
Click to expand...
Click to collapse
Awesome. Thats the way to go, just manually flash everything using RA and you'll be good to go.
hey i just tried to change my recovery bc cwm got messed up with the whole cache not being able to wipe. so i went through goo manager and tried to install twrp it looked like it install right and when i go into recovery it get stuck on teamwin boot img and doesnt do anything. what should i do?
mightymike889 said:
hey i just tried to change my recovery bc cwm got messed up with the whole cache not being able to wipe. so i went through goo manager and tried to install twrp it looked like it install right and when i go into recovery it get stuck on teamwin boot img and doesnt do anything. what should i do?
Click to expand...
Click to collapse
Cwm 5.0.2.7 all day.
Sent from my SGH-T989 using xda app-developers app
I have exactly the same issue. I had problems trying to wipe cache on CWM 5 so I installed through Goo, now when I boot into recovery, it gets stuck on TEAMWIN screen.
files- images
make sure you have the file in the right place wwhen you know you do get the switcher and then down ld. the file again i had to trial and error it a few times :victory:
The newest twrp gets stuck for me too. I just flashed back to a cwm
noodles2224 said:
The newest twrp gets stuck for me too. I just flashed back to a cwm
Click to expand...
Click to collapse
Same issue here on the Telus T989D. Any solutions without using cwm?
You can always try the manual method if your brave and familiar with the terminal. Go to Team Win's for our phone here: http://teamw.in/project/twrp2/101. Download the .IMG file and follow the instructions under Download - Recovery Image Method (using dd): Not hard but doublecheck your typing before hitting enter or you'll brick your phone.
I'm not responsible for any actions taken because of this post. Good Luck, its worth it in the long run.
Sent from my SAMSUNG-SGH-T989 using xda premium
One small problem with that.....
Hi guys. I'm having a somewhat similar issue, but it's a little more problematic than that. I was in mid-flash when I unfortunately learned that any attempt to work with the cache resulted in an immediate freeze-up. From what little of the log I've seen, it's trying to tell me that the cache partition is read-only. Any attempt to unmount, wipe, or work with the cache in any way will result in an immediate lock up. This is *after* wiping the system and data partitions. I have been able to get TWRP to start correctly twice in the last 40 times I've tried to boot up the phone.
Question: I noticed that TWRP has a button where you can enter a terminal command. I don't have adb set up yet on this machine, since reloading it. I would imagine the answer would be 'no', but is it possible to put a different recovery image on the sd card, then use TWRP's terminal button to issue the command to flash it, or would that make matters worse? Or am I going to have to set up adb and odin again on another machine and use that? Any feedback would be greatly appreciated.
Side note: I should've stayed with CWM non-touch. :crying:
This worked for me:
reflash CWM, flash superwipe, install TWRP through goomanager.
i had the same problem on my t989 and this odin flashed version posted here worked fine
http://forum.xda-developers.com/showthread.php?t=1852753
dailo23 said:
i had the same problem on my t989 and this odin flashed version posted here worked fine
http://forum.xda-developers.com/showthread.php?t=1852753
Click to expand...
Click to collapse
I flashed that version through Odin and it seems to be running just fine. I wiped caches and now TWRP appears to be working normally :fingers-crossed:
mightymike889 said:
hey i just tried to change my recovery bc cwm got messed up with the whole cache not being able to wipe. so i went through goo manager and tried to install twrp it looked like it install right and when i go into recovery it get stuck on teamwin boot img and doesnt do anything. what should i do?
Click to expand...
Click to collapse
EDIT: Wow I guess I didnt read the critical part where your stuck on the recovery boot screen so the attachment below wont help.... JUMP DOWN TO POST #21 AND FOLLOW IT TO RECTIFY THE GETTING STUCK ISSUE
Here, try this file guys. Someone over in the Jedi threads made a CWM flashable TWRP zip. You can thank me for bringing it to your attention if you want, but I did not create this ( I just clicked on the attachment paperclip for the thread and browsed through all the attachments because I knew I saw it somewhere in the development section...)
I also checked TWRP's own website and for the Hercules, v.2.3.1.1 is the latest version supported for our device so far but I only found 2.3.0.0 packed in a recovery flashable form.
Just flash it via CWM like any other zip and once its done it'll reboot your device automatically to system, so just reboot it back to recovery to make sure it worked. It did for me when I did awhile back with v.2.2.2.0 and I just used the below file to flash and update it in TWRP to v.2.3.0.0
Hope it helps
incgnito said:
Hi guys. I'm having a somewhat similar issue, but it's a little more problematic than that. I was in mid-flash when I unfortunately learned that any attempt to work with the cache resulted in an immediate freeze-up. From what little of the log I've seen, it's trying to tell me that the cache partition is read-only. Any attempt to unmount, wipe, or work with the cache in any way will result in an immediate lock up. This is *after* wiping the system and data partitions. I have been able to get TWRP to start correctly twice in the last 40 times I've tried to boot up the phone.
Question: I noticed that TWRP has a button where you can enter a terminal command. I don't have adb set up yet on this machine, since reloading it. I would imagine the answer would be 'no', but is it possible to put a different recovery image on the sd card, then use TWRP's terminal button to issue the command to flash it, or would that make matters worse? Or am I going to have to set up adb and odin again on another machine and use that? Any feedback would be greatly appreciated.
Side note: I should've stayed with CWM non-touch. :crying:
Click to expand...
Click to collapse
i just started having this exact problem with the cache partition. it will freeze on me whenever i try to reformat it, i can't unmount it, etc. i also get stuck on the twrp "teamwin" blue start up screen. have you figured out a solution?
edit- got it working again.. ended up odin flashing twrp 2.2 and i was able to wipe everything and install the new rom stuff.
noodles2224 said:
The newest twrp gets stuck for me too. I just flashed back to a cwm
Click to expand...
Click to collapse
Will you kindly explain how you did this?
y0urm0msname said:
Will you kindly explain how you did this?
Click to expand...
Click to collapse
What exactly is your issue?
Eks Dee Aye said:
What exactly is your issue?
Click to expand...
Click to collapse
Same as OP. I have never re-flashed CWM. This was my first time trying TWRP. I am looking for instructions to either...
Re-flash CWM
Re-install a version to TWRP that works
Thanks!
y0urm0msname said:
Same as OP. I have never re-flashed CWM. This was my first time trying TWRP. I am looking for instructions to either...
Re-flash CWM
Re-install a version to TWRP that works
Thanks!
Click to expand...
Click to collapse
Do you currently have CWM or TWRP as your recovery?
Eks Dee Aye said:
Do you currently have CWM or TWRP as your recovery?
Click to expand...
Click to collapse
Currently the non-functioning TWRP. I tried flashing CWM from the Rom Manager app, but that froze too. Looking for a reliable fix. I do not have a preference for recovery.
Eks Dee Aye said:
Do you currently have CWM or TWRP as your recovery?
Click to expand...
Click to collapse
If you have either I guess it doesn't really matter. Just install/flash the attached file below just like you would any other rom via your recovery.
After it installs reboot back into recovery and you will see the old recovery replaced with the latest TWRP for the T989.
Lemme know if this works for ya.
Eks Dee Aye said:
Just install/flash the attached file below just like you would any other rom via your recovery.
Click to expand...
Click to collapse
This is the part I don't understand. If my TWRP is stuck, how do I install/flash via my recovery?
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
Ok, so..my Girlfriend tried to root the phone herself and i think something went wrong...actually i know something went wrong..when i load up the Bootloader it gives me a few NO IMAGE found things on the SD card....but the real issue arises when i try to load a ROM onto the phone it will function for like 5 maybe 6 mintues then restart.
I tried to restore the phone to before roms were attempted to be installed on it, and the phone just hangs on the HTC screen and doesn't move.
I've tried installing Different Kernels using the whole fastboot flash boot boot.img method and none of the kernels i install seem to help..
I'm not 100% familiar with this phone since i myself use a S2 Skyrocket..
So my real question is..is there any way to get this phone back to square one so i can reinstall HBoot or whatever its called, or is there a way from where i'm at to stop this phone from constantly rebooting itself?
i don't think because there is no way to reinstall Hboot , only it can be done by HTC service centre but i will advice you to root it again from beginning , if your bootloader is already unlocked then try to root HOV , and after rooting i will suggest you to use PA rom with cm10 hellboy kernel
The no image thing is normal.not to worry.
Which Rom did you try to install?
Edit:is the phone gsm or cdma?
mihirengg19 said:
The no image thing is normal.not to worry.
Which Rom did you try to install?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1948034
I was trying to install that one "Pacman"
It gets about to the point where she would enter her information for account sync and then it would just reboot.
and the phone is CDMA through Virgin Mobile
And about the CM10 thing, i was reading that CM10 doesn't work with the camera, and she needs the camera for work to send pics to her other managers
Ok,your phone is completely normal.
Now,do this in order
Put Rom and gapps in sdcard
Put the kernel in fastboot/platform-tools folder
Boot into bootloader and select fastboot.
flash kernel using the command you described in OP
Enter recovery.do a full wipe,i.e,factory reset,wipe cache,wipe.dalvik cache.also,go into mounts and storage and format every partition,except sdcard.
Then flash the Rom.zip,boot into Rom and then again into recovery and flash gapps.
mihirengg19 said:
Ok,your phone is completely normal.
Now,do this in order
Put Rom in sdcard
Put the kernel in fastboot/platform-tools folder
Boot into recovery
Select fastboot.flash kernel using the command you described in OP
Enter recovery.do a full wipe,i.e,factory reset,wipe cache,wipe.dalvik cache.also,go into mounts and storage and format every partition,except sdcard.
Then flash the Rom.zip,boot into Rom and then again into recovery and flash gapps.
Click to expand...
Click to collapse
Ok doing that now, Do i format the/sd-ext? or just leave that alone with the sdcard
sd-ext format isn't supported so you may as well leave it.and,use the boot.img inside the zip,that is the supersick kernel.
mihirengg19 said:
sd-ext format isn't supported so you may as well leave it.and,use the boot.img inside the zip,that is the supersick kernel.
Click to expand...
Click to collapse
ok rom flashed...do i want to install Gapps now? or let the phone boot all the way first into the rom before restarting it and going back into recovery?
Boot into Rom,wait for 5mins and then flash gapps.
Nekrophilia said:
ok rom flashed...do i want to install Gapps now? or let the phone boot all the way first into the rom before restarting it and going back into recovery?
Click to expand...
Click to collapse
Ok, I'll just try Booting first before i go back and install the GAPPS...just to make sure the phone won't reboot on me
mihirengg19 said:
Boot into Rom,wait for 5mins and then flash gapps.
Click to expand...
Click to collapse
Ok..so an update... upon the initial boot..it still rebooted ... i went back and installed GApps anyways...and it's installing it now...i have no idea why this is happening with this phone :\
Did you download and flash the gsm rom by mistake?
Are you using the proper command to flash the boot.img?i.e,
fastboot flash boot boot.img
mihirengg19 said:
Did you download and flash the gsm rom by mistake?
Are you using the proper command to flash the boot.img?i.e,
fastboot flash boot boot.img
Click to expand...
Click to collapse
i grabbed it right off that link i posted earlier..I'll try Redownloading the ROM and then starting over again..maybe something happened in the download process or the transfer process..heh i'm not going to bed till i fix this issue lol since the phone for her right now is virtually unusable
You said in OP that you have a backup right?restore it first.and flash the boot.img found inside the backup.
Let's see what happens.it should boot normal.
mihirengg19 said:
You said in OP that you have a backup right?restore it first.and flash the boot.img found inside the backup.
Let's see what happens.it should boot normal.
Click to expand...
Click to collapse
That was an issue, i tried to restore the backup but it hangs at the HTC screen shortly after the Virgin Mobile and doesn't move..ever i let it sit for a long while and nothing happend
You have to flash the kernel first!only then will it boot.
Go into fastboot,flash the kernel found inside the backup and then restore it.
mihirengg19 said:
You have to flash the kernel first!only then will it boot.
Go into fastboot,flash the kernel found inside the backup and then restore it.
Click to expand...
Click to collapse
oh! ok, I'll try that
Nekrophilia said:
oh! ok, I'll try that
Click to expand...
Click to collapse
i don't have to do that format stuff before restoring right?
No need.
mihirengg19 said:
No need.
Click to expand...
Click to collapse
Ok, and is it normal for the screen to stay black after i restored and hit restart?..because that's what it's doing lol
Hi guys I am trying to get my phone in some sort of working order. I have CWM Recovery 6.0.5.1 for some reason no matter what I do to change the recovery it stays the same. I've tried installing lower CWM and also tried installing TWRP which again it says it was installed but when i go to recovery it still shows the CWM recovery. I installed CM11 and it worked fine, when I installed gapps is when the problems started. I've tried install multiple roms now, and it just doesn't want to take anything
thetinyjesus said:
Hi guys I am trying to get my phone in some sort of working order. I have CWM Recovery 6.0.5.1 for some reason no matter what I do to change the recovery it stays the same. I've tried installing lower CWM and also tried installing TWRP which again it says it was installed but when i go to recovery it still shows the CWM recovery. I installed CM11 and it worked fine, when I installed gapps is when the problems started. I've tried install multiple roms now, and it just doesn't want to take anything
Click to expand...
Click to collapse
try restoring a stock nandroid backup. if you dont have one then download one from general thread. and also make a nandroid backup of your current rom. not so sure what your problem is but maybe returning to pure stock will help.
I am trying to load the nandroid but I cannot get this recovery to work right. I've tried installing openrecovery-twrp to install the nandroid but i cant get the CWM to remove. I really dont mind what bootloader is on there but anything just to install any rom
thetinyjesus said:
I am trying to load the nandroid but I cannot get this recovery to work right. I've tried installing openrecovery-twrp to install the nandroid but i cant get the CWM to remove. I really dont mind what bootloader is on there but anything just to install any rom
Click to expand...
Click to collapse
Install/flash via fastboot the official cwm 6.0.51 that you had. then try again. if your lucky then it might work.
thetinyjesus said:
I am trying to load the nandroid but I cannot get this recovery to work right. I've tried installing openrecovery-twrp to install the nandroid but i cant get the CWM to remove. I really dont mind what bootloader is on there but anything just to install any rom
Click to expand...
Click to collapse
Get TWRP Manager from the play store. Hit the three line menu thingy on the top left of the app, and pick install TWRP. Super easy.
Ok guys ive tried reinstalling the same CWM version and reinstalling CM11 with no luck. I cannot change the bootloader to TWRP because it appears to be stuck on the CWM. The problem started for me when I installed the gapps through CWM, as soon as I did that when the phone went to boot it now says please enter the password for android, then says it was the right password but data is corrupt and cant use phone.
Is there a way to attempt to just format the entire phone including partition size and start from scratch again?
thetinyjesus said:
Ok guys ive tried reinstalling the same CWM version and reinstalling CM11 with no luck. I cannot change the bootloader to TWRP because it appears to be stuck on the CWM. The problem started for me when I installed the gapps through CWM, as soon as I did that when the phone went to boot it now says please enter the password for android, then says it was the right password but data is corrupt and cant use phone.
Is there a way to attempt to just format the entire phone including partition size and start from scratch again?
Click to expand...
Click to collapse
How are you trying to flash these recoveries (they're not called bootloaders, that is something totally separate)?
Have you tried using TWRP Manager as I suggested earlier, or are you using ADB? And If you are using ADB and trying to flash it that way, what fastboot commands are you giving?
There is no way that your should be "stuck" with CWM.
Okay what i have to do is fastboot its the only thing i can get to work. Not at my computer but yeah i fastboot the recovery img via cmd in windows. Fastboot flash recovey i use ane it successfully does. Doesnt matter what img or recovery i use when i boot into recovery it still uses cwm. Also only way i can put a rom on is adb sideload but now thats even failing with status 7 error
Also when i try the command fastboot oemRUU or whatever the command is it reboots the phone shows CM logo and boots till asking for android pw
thetinyjesus said:
Okay what i have to do is fastboot its the only thing i can get to work. Not at my computer but yeah i fastboot the recovery img via cmd in windows. Fastboot flash recovey i use ane it successfully does. Doesnt matter what img or recovery i use when i boot into recovery it still uses cwm. Also only way i can put a rom on is adb sideload but now thats even failing with status 7 error
Click to expand...
Click to collapse
The status 7 error is because of an outdated recovery. Not much help, I know.
It's strange that the TWRP Manager doesn't work. I've helped others with problems flashing recovery, and it has worked for them.
You could also try ROM Toolbox to update your CWM, or ROM Manager, but ROM Toolbox is better/more complete. It has everything ROM Manager has plus some.
The other option that you may not want to take is to do a COMPLETE wipe of your phone. That always sucks.
Going to try those programs. Thank you btw and how do i perform the full wipe i was about to throw the phone out lol.
@thetinyjesus You could also try this app. No PC necessary.
Thanks but cannot use the app i cannot get the phone to boot. Do you have directions for a full wipe
thetinyjesus said:
Going to try those programs. Thank you btw and how do i perform the full wipe i was about to throw the phone out lol.
Click to expand...
Click to collapse
Actually, you full wipe in recovery. lol
If you haven't tried TWRP Manager yet, that would be my first choice.
Damn that didnt work than i tried all those format options in the bunked recovery with no luck it sucks
If you're using the command prompt to flash the recovery, provide a screenshot of your desktop so that we can see what you're doing and what "it's" doing.
Starting to think that it's more of an "operator" fault and not anything to do with the device that doesn't want to play along.
Okay once im back home ill show the output
Here is the output from flashing the recovery. Once again when I went to recovery it loaded with CWM.
Also here is the output from sideloading the cm file again (same error no matter what rom I try)
Windows CMD: C:\Users\Jimmy\Desktop\platform-tool>adb sideload cm.zip
sending: 'cm.zip' 100%
Phone: Installing update...
set_perm_recursive: "/system" not a valid uid
E: Error in /tmp/update.zip
(Status 7)
Installation aborted
Anyone?