Related
So, there is nothing magical about super wipe scripts, but this one seems to have had some serious thought put into it.
http://forum.xda-developers.com/showthread.php?t=834812
I usually wipe manually but was curious what you guys do...
Sent from my EVO using xda app-developers app
adma84 said:
So, there is nothing magical about super wipe scripts, but this one seems to have had some serious thought put into it.
http://forum.xda-developers.com/showthread.php?t=834812
I usually wipe manually but was curious what you guys do...
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
There is only one superwipe for our phone. There is nothing to compare it to, and no need as it works fine. The link you posted has nothing to do with our device.
http://forum.xda-developers.com/showthread.php?p=27166189
Ta da!
I've never understood super wipes. I just do it manually.
No need for a superwipe. Just Factory Reset and wipe System and you're ready to flash. That's never once given me a problem.
I use superwipe mod all the time after a manual wipe. Reason because TWRP does not have option to wipe/format the BOOT partition.
Sent from my EVO using xda premium
theoner1 said:
I use superwipe mod all the time after a manual wipe. Reason because TWRP does not have option to wipe/format the BOOT partition.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
You shouldn't have to wipe boot.
SoraX64 said:
You shouldn't have to wipe boot.
Click to expand...
Click to collapse
Exactly I never even heard of a Superwipe until the 3d came out. Never had to flash one since I had my g1 and i'm not going g to start now
Sent from my EVO using xda premium
SoraX64 said:
You shouldn't have to wipe boot.
Click to expand...
Click to collapse
Install any aosp rom, example deck cm10 8-31-12. The Rom have force close issue with the phone process at the beginning. Now if you want to go back to latest sense Rom, without wiping boot img, you will continue to have the same phone process force close issue even if you're on sense Rom. It just happen to me a couple nights ago. So wiping boot partition is my way of completely getting rid of previous issue on the last install Rom.
Sent from my EVO using xda premium
theoner1 said:
Install any aosp rom, example deck cm10 8-31-12. The Rom have force close issue with the phone process at the beginning. Now if you want to go back to latest sense Rom, without wiping boot img, you will continue to have the same phone process force close issue even if you're on sense Rom. It just happen to me a couple nights ago. So wiping boot partition is my way of completely getting rid of previous issue on the last install Rom.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I can flash between CM and Sense all I want without the error persisting, maybe you're doing something else wrong?
SoraX64 said:
I can flash between CM and Sense all I want without the error persisting, maybe you're doing something else wrong?
Click to expand...
Click to collapse
I was doing something wrong at the time, I forgot to flash the superwipe. When I first booted into meanrom 3.6 the same phone process force close still there. After realizing I forgot to flash superwipe, went back to recovery, wipe completely manually follow by superwipe then install meanrom 3.6, which booted fine without phone process error. Every time I flash a New Rom I always wipe everything at least twice.
Sent from my EVO using xda premium
theoner1 said:
I was doing something wrong at the time, I forgot to flash the superwipe. When I first booted into meanrom 3.6 the same phone process force close still there. After realizing I forgot to flash superwipe, went back to recovery, wipe completely manually follow by superwipe then install meanrom 3.6, which booted fine without phone process error. Every time I flash a New Rom I always wipe everything at least twice.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Are you by any chance 1.15 S-ON?
Because not a week ago I left CM10 for Viper 4G because I needed the camera to work stably, and I did not receive the force close once.
SoraX64 said:
Are you by any chance 1.15 S-ON?
Because not a week ago I left CM10 for Viper 4G because I needed the camera to work stably, and I did not receive the force close once.
Click to expand...
Click to collapse
Nope orginal hboot 1.12 and s-off
Sent from my EVO using xda premium
theoner1 said:
Nope orginal hboot 1.12 and s-off
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Hmm, interesting because I have gone back and forth between CM10 and MeanRom. I have never had an issue. I love the speed and fluidity of CM10 but the Sense camera is just to good at this point.
I have then same issue...if I don't use sw I have issues bouncing between sense and cmx nands.. can't make calls on sense without it..with it I have no issues
firmbiz94 said:
I have then same issue...if I don't use sw I have issues bouncing between sense and cmx nands.. can't make calls on sense without it..with it I have no issues
Click to expand...
Click to collapse
See what I mean, I'm not the only with this issue. Superwipe work wonders for me too.
Sent from my EVO using xda premium
I think a lot of people got used to using these from the og evo. CWM was thought to have trouble wiping so most would wipe two or three times to make sure it didn't miss anything. I haven't heard of that being an issue for a long, long time though.
One thing that it may help with though is if the ROM doesn't format the system partition. I've spent hours trying to track down bugs only to realize leftover system files were wreaking havoc with the new ROM.
theoner1 said:
See what I mean, I'm not the only with this issue. Superwipe work wonders for me too.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Hmm that's interesting, i remember i flashed tranquility rom and was working great! then tested cmx and at the same time tranquility was updated and that error was still present on the new tranquility rom, but i thought it was the rom so i flashed another sense rom but, this time i used superwipe after manually wiping all and no error anymore, since then i didnt use tranquility thinking it was the new update. now i always use superwipe.
time to go back to tranquility :fingers-crossed::fingers-crossed:
Im currently running Viper4g on my evolte but ive been checking out CM10 and i want to try it out. What would be the usual steps to take when flashing a new rom?
I would do a full NAND backup with whatever recovery you have in case you want to revert back. Then do a full wipe (system, data, cache, dalvik) and flash the new ROM.
Read the guide in my sig lol, explains just about anything you could think of and has a list of basic trouble shooting scenarios that some users are likely to encounter
Come on guys you tell me what a great write up I have and never recommend it?
Edit: I feel like I'm trying to sell myself and I am not a wh***
*runs away in tears*
Of course it's great
However, you said yourself: it's a great reference guide, but not a step-by-step for anything.
The OP asked for steps to take when changing ROMs
Yes but the title of his thread says tips for someone new....ahaaaa.. *cue classic black and white cinema fiend music*
I so wrote it to avoid all these brick and corrupt card threads
Touche...
*bows in defeat*
Make sure you check out om4's AWESOME guide, "DON'T PANIC", here: http://forum.xda-developers.com/showthread.php?t=1869377
*runs off to bed*
bilbo524 said:
Touche...
*bows in defeat*
Make sure you check out om4's AWESOME guide, "DON'T PANIC", here: http://forum.xda-developers.com/showthread.php?t=1869377
*runs off to bed*
Click to expand...
Click to collapse
Suck up
Sent from the depths of hell
Quiet let me have my moment lol
Absolutely not lol
Sent from the depths of hell
Dude, check out the last 2 scenarios, went to the head and the gf added them. I laughed so hard
Well it looks like i did something wrong cause my phone is stuck in a constant boot loop. I followed the instructions on http://forum.xda-developers.com/showthread.php?t=1794867
for
How to flash a boot image if S-ON Dev Unlocked 1.15 HBOOT:
I was trying to install CM10 btw. I did a backup using twrp tried restoring but that didnt work. What can i do now to fix it?
Maybe the cmx was a bad download or bad flash. If you fasboot flashed the aosp boot IMG you might have problems trying to restore a sense backup. I would download cmx again redo all the steps.
I'm not sure if you have to flash a sense boot IMG when restoring a backup , I would try it tho to be safe.
Hey man. The instructions work, so start over and make sure you follow every step including wiping.
Sent from my EVO using xda app-developers app
Did you do a full factory reset and wipe system, data, cache, and dalvik before flashing the ROM?
Sent from my LTEvo powered by CM10 using XDA Premium
bilbo524 said:
Did you do a full factory reset and wipe system, data, cache, and dalvik before flashing the ROM?
Sent from my LTEvo powered by CM10 using XDA Premium
Click to expand...
Click to collapse
No i didnt. Right now i just want to get my phone working again since i have work in an hour. What should i do to get it working again?
Start the process over just make sure you wipe fully before flashing anything. Cache, dalvik, factory reset and system.
Sent from my EVO using xda app-developers app
To restore your existing backup, you will need to reflash your old viper4g kernel (boot.IMG) first with fastboot.
Sent from my LTEvo powered by CM10 using XDA Premium
bilbo524 said:
To restore your existing backup, you will need to reflash your old viper4g kernel (boot.IMG) first with fastboot.
Sent from my LTEvo powered by CM10 using XDA Premium
Click to expand...
Click to collapse
So just follow the steps from the link i posted using the boot.img from the viper4g download?
Yes, follow the same steps you used to flash the CM10 kernel to reflash the viper4g kernel. Your exisiting viper4g backup should then boot OK.
Sent from my LTEVO powered by CM10 using XDA Premium
bilbo524 said:
Yes, follow the same steps you used to flash the CM10 kernel to reflash the viper4g kernel. Your exisiting viper4g backup should then boot OK.
Sent from my LTEVO powered by CM10 using XDA Premium
Click to expand...
Click to collapse
ok im trying to restore again, hopefully it works. i have work in 45 minutes and being without my phone would suck.
It worked! Thanks for the help guys. Im gonna leave CM10 alone until the weekend when im off.
First of all, thank you in advance for any help you can give.
So I made an attempt today of flashing a CyanogenMod Nightlie build using ClockworkMod and now I cannot get passed the spinning Cyanogen logo (I have waited 45 minutes over several different reboot attempts).
The bootloader has been unlocked
I have wiped the data
I have wiped the cache
I have wiped Dalvik Cache
then
I have loaded the nightlie
and then the gapps
then I rebooted and I get nothing but the startup screen.
Can anyone help? Did I miss something? I have been all over the forum looking for insight and havent had any luck.
Again, thank you and I thank everyone for their hard work on these builds.
George
Give us some basic info are you s-off etc
Sent from my HTC_Amaze_4G using xda app-developers app
filthygoat223996 said:
Give us some basic info are you s-off etc
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Yes, I now realize that I forgot the important step of S-Off. Can that be done now that I am forever in the bootloader?
Gkins3 said:
Yes, I now realize that I forgot the important step of S-Off. Can that be done now that I am forever in the bootloader?
Click to expand...
Click to collapse
Can you get into recovery? If you can revert back to your nandroid and enable smart flash if you are using 4ext
Edit: oops I see you are using cwm
I guess you can try to restore and try s-off
Sent from my HTC_Amaze_4G using xda app-developers app
filthygoat223996 said:
Can you get into recovery? If you can revert back to your nandroid and enable smart flash if you are using 4ext
Edit: oops I see you are using cwm
I guess you can try to restore and try s-off
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help. No luck on the restore. I guess I hit full wipe on one of my many re-installs. Gotta work in a few hours... will have to work on it tomorrow more. I thought with my prior Blackberry modding I wouldnt make these stupid mistakes... but I was wrong.
Again - thanks.
Gkins3 said:
Thanks for the help. No luck on the restore. I guess I hit full wipe on one of my many re-installs. Gotta work in a few hours... will have to work on it tomorrow more. I thought with my prior Blackberry modding I wouldnt make these stupid mistakes... but I was wrong.
Again - thanks.
Click to expand...
Click to collapse
No problem its always better to be safe than sorry, I'm sorry I'm not more knowledgeable on cwm. Good luck
Sent from my HTC_Amaze_4G using xda app-developers app
okay, some things have been done wrong.. to flash a rom like cm10 if the rom isn't booting and your S-ON not using 4ext you need to flash the kernel separate, and 4ext is the recommended recovery for any and all S-ON htc phones.. id still recommended for S-OFF also..
---------- Post added at 11:22 PM ---------- Previous post was at 11:19 PM ----------
and to do a clean install your's suppose to
wipe data / factory
format system
wipe cache partition
wipe delvik cache
flash rom
flash gapps
wipe delvik cache again
boot rom let it sit till the screen goes off
(extra)
boot into recovery
wipe delvik cache once again
fix permissions
boot phone and enjoy
install rom agn !!
Hey guys, I recently attempted to root my old phone using the Amaze All in One Kit v5.2. Well, I was able to get the bootloader unlocked and installed TWRP recovery, but was unable to get any roms to load. I was advised I should relock the bootloader and attempt to do a RUU flash since my phone will no longer boot past the HTC screen. Since I relocked the bootloader, I have lost access to TWRP recovery entirely. I also tried the PH85IMG file on my SD card, but it doesn't seem to do anything different after installing and verifying.
My current bootloader screen displays the following:
***RELOCKED***
***Security Warning***
RUBY PVT SHIP S-ON RL
HBOOT-1.93.0003
eMMC-boot
Aug 14 2012, 17:22:50
Any advice or direction would be greatly appreciated.
Michael
Flash 4ext recovery and enable smart flash from settings and then flash any ics rom... (4ext has this smart flash feature so even tho you're S-ON you can still flash a rom and the kernel together in twrp recovery only the rom get Flash not the kernel) reason it didn't work for you in the first place..
https://www.dropbox.com/s/ox16mtk02zoi3qf/PH85IMG.zip
If you have a hard time flashing 4ext recovery from all in one kit use it.. (REMOVE EVERY FILE INSIDE IT EXCEPT FOR THE ONE CALLED "recovery.img" and place it in your ext_sd card and go to bootloader and follow instructions) unlock the bootloader 1st if it's locked ...
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Gotcha. Well, I just got the bootloader unlocked again, but I am unable to flash 4EXT recovery through the all in one software. The only other option I saw involved installing from the phone, but since I can only get to the bootloader and TWRP recovery screen, I'm unsure of how exactly to install it. You will have to excuse my ignorance on this stuff. I'm pretty computer literate, but this rooting stuff has gotten the best of me thus far...
jdmroach said:
Gotcha. Well, I just got the bootloader unlocked again, but I am unable to flash 4EXT recovery through the all in one software. The only other option I saw involved installing from the phone, but since I can only get to the bootloader and TWRP recovery screen, I'm unsure of how exactly to install it. You will have to excuse my ignorance on this stuff. I'm pretty computer literate, but this rooting stuff has gotten the best of me thus far...
Click to expand...
Click to collapse
Just follow the things I told in the 2nd para.. Use that zip and flash it from bootloader.. It'll overwrite and flash 4ext recovery
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
ravike14 said:
Just follow the things I told in the 2nd para.. Use that zip and flash it from bootloader.. It'll overwrite and flash 4ext recovery
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, after installing just that file on my SD card and restarting the phone, it went through a file check and parsing phase then when I clicked on recovery it brought back up TWRP. Obviously I'm misunderstanding something.
jdmroach said:
Well, after installing just that file on my SD card and restarting the phone, it went through a file check and parsing phase then when I clicked on recovery it brought back up TWRP. Obviously I'm misunderstanding something.
Click to expand...
Click to collapse
it didn't install the recovery in the process?
ravike14 said:
it didn't install the recovery in the process?
Click to expand...
Click to collapse
It does not appear so. TWRP opened up once again when I clicked on recovery from within the bootloader.
I'm also getting this error "Unable to mount eMMC" as well.
jdmroach said:
It does not appear so. TWRP opened up once again when I clicked on recovery from within the bootloader.
I'm also getting this error "Unable to mount eMMC" as well.
Click to expand...
Click to collapse
i use the same zip when something goes wrong..it works fine for me..no idea why its not flashing.you unlocked the bootloader? deleted other unnecessary files in that zip?
jdmroach said:
It does not appear so. TWRP opened up once again when I clicked on recovery from within the bootloader.
I'm also getting this error "Unable to mount eMMC" as well.
Click to expand...
Click to collapse
Well, cancel that. Finally got the 4EXT recovery flashed. Thanks again for all your help.
ravike14 said:
i use the same zip when something goes wrong..it works fine for me..no idea why its not flashing.you unlocked the bootloader? deleted other unnecessary files in that zip?
Click to expand...
Click to collapse
I think I was doing something incorrectly. Anyways, I just enabled Smart Flash and went to "install from sdcard". When I select "choose zip from sdcard", I get the error "Can't mount /internal sdcard".
jdmroach said:
I think I was doing something incorrectly. Anyways, I just enabled Smart Flash and went to "install from sdcard". When I select "choose zip from sdcard", I get the error "Can't mount /internal sdcard".
Click to expand...
Click to collapse
looks like you're partitions are corrupted :/ ..go to wipe category and do a full wipe except SD cards and see if it works...
ravike14 said:
looks like you're partitions are corrupted :/ ..go to wipe category and do a full wipe except SD cards and see if it works...
Click to expand...
Click to collapse
In the wipe category, my options are as follows:
wipe data/factory reset
wipe cache
wipe cache + dalvik
wipe dalvik cache
wipe battery stats
format system
format data
format boot
format all partitions (except sd card)
format sdcard
Did you mean do a format all except sdcard?
ravike14 said:
looks like you're partitions are corrupted :/ ..go to wipe category and do a full wipe except SD cards and see if it works...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=27844248&postcount=6
I came across this method and it appears to have fixed my internal sdcard issue. It is installing the rom now. I will let you know once I get done flashing the rom if all goes as planned.
jdmroach said:
http://forum.xda-developers.com/showpost.php?p=27844248&postcount=6
I came across this method and it appears to have fixed my internal sdcard issue. It is installing the rom now. I will let you know once I get done flashing the rom if all goes as planned.
Click to expand...
Click to collapse
Sorry for delay, good luck
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
ravike14 said:
Sorry for delay, good luck
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I ended up just flashing the Cyanogenmod rom for now. Everything seemed to go fine with the install. I rebooted and it sat at the Cyanogenmod splash screen for almost a hour without proceeding. Any clue?
jdmroach said:
I ended up just flashing the Cyanogenmod rom for now. Everything seemed to go fine with the install. I rebooted and it sat at the Cyanogenmod splash screen for almost a hour without proceeding. Any clue?
Click to expand...
Click to collapse
Did you do a full wipe before flashing the rom? If there are data of your previous rom in your system partition all the data get overwrite and crashes ... Full wipe = format all (except sd card)
(the one in wipe/format category..)
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
ravike14 said:
Did you do a full wipe before flashing the rom? If there are data of your previous rom in your system partition all the data get overwrite and crashes ... Full wipe = format all (except sd card)
(the one in wipe/format category..)
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ahh okay. I believe I just did the wipe function and not a full format. I will try that and let you know.
jdmroach said:
Ahh okay. I believe I just did the wipe function and not a full format. I will try that and let you know.
Click to expand...
Click to collapse
It has been at the Cyanogenmod screen for about 20 mins now. Does it normally take this long?
jdmroach said:
It has been at the Cyanogenmod screen for about 20 mins now. Does it normally take this long?
Click to expand...
Click to collapse
I just read carefully your 1st post now.. You're hboot is 1.93.003 it's normally 1.93.002.. It's a nasty issue.. Try to flash a stock htc ics rom (arhd 5) and do the s-off.. It's the only way to recover from that issue as far as I know..
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
ravike14 said:
I just read carefully your 1st post now.. You're hboot is 1.93.003 it's normally 1.93.002.. It's a nasty issue.. Try to flash a stock htc ics rom (arhd 5) and do the s-off.. It's the only way to recover from that issue as far as I know..
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
SUCCESS!!! I was able to flash another rom (T-mobile Stock ICS Debloated) and it booted back up like it should. Seriously, thanks again for all of your help buddy.
Ever since the new partition layout i cant run any kit kat roms. I did throwbacks process and i am s-off so i have had 4.17 on this phone. also running the latest recovery from throwbacks post .8b. I dont know what it is or what im doing wrong but after flashing a 4.4 rom it will stay on the boot screen and the charge light comes on if its plugged it but will not boot. All of the sense 5.5 roms flash and boot up. Any ideas?
First of all make sure you're flashing ROMs compatible with the new partition layout.
Sent from my Nexus 5 using Tapatalk
numel007 said:
First of all make sure you're flashing ROMs compatible with the new partition layout.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have tried flashing slimkat and CM11 both are compatible with the new layout.
theshrimp said:
I have tried flashing slimkat and CM11 both are compatible with the new layout.
Click to expand...
Click to collapse
The commit for the new partitions are not merged into cm repo. If you're flashing stock builds, there is no way it'll work. Are you using SlimKat posted in Android Developemt?
Sent from my Nexus 5 using Tapatalk
numel007 said:
The commit for the new partitions are not merged into cm repo. If you're flashing stock builds, there is no way it'll work. Are you using SlimKat posted in Android Developemt?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I tried a CM11 that somebody had updated, and yes the one by tots
theshrimp said:
I tried a CM11 that somebody had updated, and yes the one by tots
Click to expand...
Click to collapse
Can't think of anything off the top of my head. I'll reply if I come up with anything. My knowledge of updates on this device has dwindled since I got my n5. Sorry 'bout that.
Sent from my Nexus 5 using Tapatalk
numel007 said:
Can't think of anything off the top of my head. I'll reply if I come up with anything. My knowledge of updates on this device has dwindled since I got my n5. Sorry 'bout that.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for the quick reply. I hope i can figure this out! i have been flashing roms since my samsung moment so i dont think its something im doing unless the process changed with the new layout.
theshrimp said:
Thanks for the quick reply. I hope i can figure this out! i have been flashing roms since my samsung moment so i dont think its something im doing unless the process changed with the new layout.
Click to expand...
Click to collapse
Are you using any wipe scripts like superwipe?
Sent from my Nexus 5 using Tapatalk
Check the thread in the link below if you haven't already done so.
http://forum.xda-developers.com/showthread.php?t=2654590
Sent from my HTC device
FinZ28 said:
Check the thread in the link below if you haven't already done so.
http://forum.xda-developers.com/showthread.php?t=2654590
Sent from my HTC device
Click to expand...
Click to collapse
That was the thread i got the CM11 build from.
numel007 said:
Are you using any wipe scripts like superwipe?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I usually wipe cache, dalvik, internal, and system. Then i reboot to bootloader and flash the boot img from the rom, reboot back to recovery and flash the rom with gapps.
theshrimp said:
That was the thread i got the CM11 build from.
I usually wipe cache, dalvik, internal, and system. Then i reboot to bootloader and flash the boot img from the rom, reboot back to recovery and flash the rom with gapps.
Click to expand...
Click to collapse
Maybe I'm out of recent times, but I've personally never flashed boot.IMG separately. I just wipe, flash ROM, flash kernel, wipe caches, reboot. Is this a new thing that updated partitions needs?
Sent from my Nexus 5 using Tapatalk
numel007 said:
Maybe I'm out of recent times, but I've personally never flashed boot.IMG separately. I just wipe, flash ROM, flash kernel, wipe caches, reboot. Is this a new thing that updated partitions needs?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
No change on the new setup. If you're S-on you have to flash the boot.img separately. For S-off, you don't.
Sent from my HTC device
FinZ28 said:
No change on the new setup. If you're S-on you have to flash the boot.img separately. For S-off, you don't.
Sent from my HTC device
Click to expand...
Click to collapse
He is s-off, so technically he shouldn't need to do that. Shouldn't make a difference though.
Sent from my Nexus 5 using Tapatalk
If i remember right people who were S-ON still had to do it that way and i only recently gained S-OFF so i still do it that way. im not sure if there is a different way for S-OFF people?
theshrimp said:
If i remember right people who were S-ON still had to do it that way and i only recently gained S-OFF so i still do it that way. im not sure if there is a different way for S-OFF people?
Click to expand...
Click to collapse
You said in your original post that you're S-off, so you just need to flash the ROM zip. No need to boot to the bootloader and flash the boot.img separately.
Sent from my HTC device
FinZ28 said:
You said in your original post that you're S-off, so you just need to flash the ROM zip. No need to boot to the bootloader and flash the boot.img separately.
Sent from my HTC device
Click to expand...
Click to collapse
So just went and wiped everything and re flashed without going into the bootloader, and still no go. Its stuck on boot screen and the charge light still comes on so its not boot looping right?
theshrimp said:
So just went and wiped everything and re flashed without going into the bootloader, and still no go. Its stuck on boot screen and the charge light still comes on so its not boot looping right?
Click to expand...
Click to collapse
How long are you waiting for it to boot up? Remember it takes several minutes for a ROM to boot after a flash, so give it a bit and see what happens.
Sent from my HTC device
FinZ28 said:
How long are you waiting for it to boot up? Remember it takes several minutes for a ROM to boot after a flash, so give it a bit and see what happens.
Sent from my HTC device
Click to expand...
Click to collapse
Before i re wiped it i let it sit for 30+ minutes. Its been going for about 5 or so minutes.
Maybe ill just have to stick with boring old sense 5 haha. i seriously have no idea why its doing this.
Did you unlock bootloader with htc utility? What did you use to gain s-off?
What version is your H-BOOT?
Some roms I was flashing checked for 2.10.0000 and rejected anything else, so when I upgraded to 2.10.5555, most of the kit kat rooms took a poop on me.
Not sure if this is still an issue though. I would imagine those errors were caused by the person compiling the Roms, but may have been resolved since.