Related
I flashed midnight ROM. put the AOSP theme over it. Flashed the newest MAC Kernel, and that's when it started happening.
I decided to factory reset and flash the ROM again, tried to restart. same thing.
restored a backup (after factory restting), no dice.
Wiped boot/data/system, factory resetted, wiped both caches and reflashed midnight ROM. Still nothing.
Tried to flash CM9 (after factory resetting and stuff) and it still won't go past the HTC screen no matter how long I wait.
What's wrong? Am I half bricked?
I'm using the Evo V with S OFF on downgraded HBOOT.
You need to downgrade your radios as well to flash aosp roms. Run an older RUU, which will set you back to stock, flash your recovery and then flash midnight again
Sent from my PG86100 using xda app-developers app
beneath-a-burning-turtle said:
You need to downgrade your radios as well to flash aosp roms. Run an older RUU, which will set you back to stock, flash your recovery and then flash midnight again
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
I've flashed all these ROMs with no problems before. I already have my radios upgraded (I basically turned my phone into a Evo 3D).
RedDeadDorito said:
I've flashed all these ROMs with no problems before. I already have my radios upgraded (I basically turned my phone into a Evo 3D).
Click to expand...
Click to collapse
Gotta go in the opposite direction with radios, downgrade. It'll make older roms compatible again.
Sent from my PG86100 using xda app-developers app
beneath-a-burning-turtle said:
Gotta go in the opposite direction with radios, downgrade. It'll make older roms compatible again.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
So basically, upgrade my HBOOT (since stock is on a upgraded one) again and flash a stock ROM then downgrade again?
I was thinking of doing this, but why did this problem come up in the first place?
I can't do it because I don't have an extra SD card around. If I put the hboot upgrade on my SD card, the bootloader won't start up because it gives you the option to install it or not install and either way, it turns the phone off.
Got it figured out. When I flashed a different kernel, it broke the other kernel or something. I had to flash the ROM's kernel separately. I don't know why.
I'm not sure why, but it did. Anyways, it seems to be working now!
RedDeadDorito said:
Got it figured out. When I flashed a different kernel, it broke the other kernel or something. I had to flash the ROM's kernel separately. I don't know why.
I'm not sure why, but it did. Anyways, it seems to be working now!
Click to expand...
Click to collapse
Glad that you got a solution and that you were also detailed in your response. Perhaps someone in the future that sets aside the time to research and read will be able to either get themselves out of a mess - or - possible avoid one. Cheers!
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:
Hi,
For 2 days my Wifi is giving an error. It says turning on but never does. I have not installed anything or changed a thing. It stopped working for some strange reason. I am on stock mobility with stock kernel, never changed it and I have s-on.
Please help,
Thanks
Try a hard reset
Sent from my HTC_Amaze_4G using xda app-developers app
Is there any way besides a hard reset?
Sent from my HTC Amaze 4G using xda premium
Are you rooted!
Sent from my HTC_Amaze_4G using xda app-developers app
Unlocked bootloader & rooted.
Sent from my HTC Amaze 4G using xda premium
Try clearing Dalvik-Cache in recovery then Fix Permissions. It should help it.
Wipe and reflash stock via hasoon's zip files.
I reset and its still the same. When I try to flash a different kernel it restarts without changing but starts with an error message to contact HTC. I'm fully rooted, unlocked bootloader and s-on and I tried flash.bat and the kernel flasher app but none can change my kernel. Does anyone have any suggestions?
Just noticed bt is not working too
Sent from my HTC Amaze 4G using xda premium
pokey77 said:
I reset and its still the same. When I try to flash a different kernel it restarts without changing but starts with an error message to contact HTC. I'm fully rooted, unlocked bootloader and s-on and I tried flash.bat and the kernel flasher app but none can change my kernel. Does anyone have any suggestions?
Sent from my HTC Amaze 4G using xda premium
Click to expand...
Click to collapse
Well if you are using 4ext recovery (which i highly recommend, best recovery ever made)then there is an option that asks if you are are s-on and you click yes because you are s-on which then allows the recovery to flash any kernel (given its compatible of course) as if you were s-off. That should work, if for some odd reason (for me 4ext never failed even when i was s-on while flashing kernels) it doesnt work then i would suggest attempt to s-off your device via wire trick but be sure to read up thoroughly before you attempt that as some people have bricked their device doing so.
Edit: also i would suggest wipe all partitions except sd card then flash rom and then flash kernel right after to avoid issues.
Could I try to flash a kernel first before flashing. I tried looking for a kernel all day and can't seem to find 1. I used the mobility ota Kernel which does not seem to work.
Sent from my HTC Amaze 4G using xda premium
pokey77 said:
Could I try to flash a kernel first before flashing. I tried looking for a kernel all day and can't seem to find 1. I used the mobility ota Kernel which does not seem to work.
Sent from my HTC Amaze 4G using xda premium
Click to expand...
Click to collapse
Hmm I haven't heard of that kernel before and there aren't many to choose from on this device. First off do you have the ICS ruu? If so just flash faux's kernel with any of theroms that are based off of sense 3.6. Here is the link that is also under the development section of the forums http://faux.androidro.ms/ruby-faux123-kernel-v017.zip for the ICS version ROMs (most of them are) I would suggest speedrom 7.5 as I found it pretty decent for a sense based rom. But you have to flash the ROM first then the kernel but if I recall 4ext recovery with the feature of s-off automatically flashes the kernel that is packaged with the rom it just ends up having to boot twice. So first just flash one of the new sense 3.6 ROMs via 4ext recovery - settings-recovery-check smartflash on and then flash the ROM kernel should automatically flash
Edit: stumbled across this in faux kernel thread might help if 4ext still doesn't work
http://forum.xda-developers.com/showthread.php?t=1359951&page=181
I also had the wifi error problem for some reason when I tried to flash Speedrom 6.5 and 7.0 coming from Supersaiyan 3. Kinda fixed itself after installing Speedrom 7.5/7.6 so maybe try these two steps and it might work for you:
1 ) Of course make a backup
2) When flashing a new or old rom I always Wipe/Factory Reset from 4ext and then just clear dalvik cache, then install whatever rom you like. Never had any probs with this method such as the wifi error you're encountering. Just never got bt error.... weird...
Btw what rom are you currently on?
+1 if this helped anyone!
Sent from my HTC Ruby using xda premium
I'm on mobility stock rom
Sent from my HTC Amaze 4G using xda premium
I switched to speed Rom and bt works but not WiFi.
Sent from my HTC_Amaze_4G using xda premium
I've tried a few roms all day and still no luck.
1. After installing a rom, it always does 1 final step before a restart. It uses a previously saved boot.img which i think is causing my issue but i could be wrong.
1. One thing i noticed is when a rom boots up, the 1st thing it does is turn on WIFI followed by an error.
Has this happened or does any of this makes sense to anyone?
Once again, please help & thanks.
pokey77 said:
I switched to speed Rom and bt works but not WiFi.
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Bro its most likely a kernel issue you are facing WiFi issues usually are due to the incorrect kernel flashed or the kernel not flashed at all with the ROM however I would suggest that you flash the stock ruu file (however you will lose both root and recovery but those are easy to reinstall using hasoons tool or various other methods) I say this because this way you will know for sure if you have a hardware or software problem for sure. WiFi should work with stock ruu from your carrier (make sure to download your carrier specific ruu).if you feel you can do s-off via wire trick and then super cid your amaze you will be able to flash any and every ROM for the amaze. I have a suspicion that the ROMs that are out are based off of T-Mobile ruu and people with mobilicity have their amaze super cid to work with any carrier.however did you try flashing cm10 via 4ext maybe since that has an aosp kernel and if flashed with smart flash option in 4ext it may work.
1. After installing a rom, it always does 1 final step before a restart. It uses a previously saved boot.img which i think is causing my issue but i could be wrong.
1. One thing i noticed is when a rom boots up, the 1st thing it does is turn on WIFI followed by an error.
Click to expand...
Click to collapse
Yea it could be the kernel because the thing you said about the 4ext recovery telling you that its loading the saved boot.img is what I always get and whenever i do get it, the rom always works perfectly. Also which version of speedrom did u try because I had the problem when I was using both 6.5 and 7.0. Try flashing the Supersaiyan 3 rom and then choose faux kernel from the AROMA INSTALLER. Then wipe as I told you in the posts before and then flash speedrom. It worked like that for me. Sorry if you still dont have luck!
What would happen if i deleted the boot.img file and flash a kernel?
Sent from my HTC_Amaze_4G using xda premium
pokey77 said:
What would happen if i deleted the boot.img file and flash a kernel?
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Well OK I really want this to work for you after you mentioned the boot.IMG issue it may be that you need to flash an insecure boot image first. Here is the link http://forum.xda-developers.com/attachment.php?attachmentid=1223086&d=1343307912 for s-on people this usually needs to be flashed via fastboot and not recovery. However since 4ext recovery seems to be an exception to almost every rule regarding recoveries it may be able to flash it. If not just flash via fastboot I posted the forum topic link that this issue has been discussed on in one of my previous posts in this thread. I'm positive this is your problem now.
---------- Post added at 12:44 AM ---------- Previous post was at 12:36 AM ----------
Read through the issue on this page http://forum.xda-developers.com/showthread.php?t=1359951&page=181 seems like this is exactly the issue you are facing. I suggest after flashing which ever ROM flash fauxs kernel it's the best for the amaze anyway hope you get this to work I have exhausted the last bit of knowledge I have regarding this issue. Hence I s-off my device to avoid stupid issues such as these once and for all.
Should I try s-off before installing the GB ruu?
Sent from my HTC Amaze 4G using xda premium
I have a MoPho with unlocked bootloader running 2.3.4 and everytime I try to flash back to my saved stock backup from any custom rom I keep getting an "error while flashing boot image" I tried to do an advanced restore and picked the files one at a time but I keep getting the same result. Can someone please help, thank you in advance...
Sent from my MB855 using xda app-developers app
Are you restoring using the same utility you did the nandroid backup with? Joker recovery vs twrp vs cwm recovery
Sent from my MB855 using Tapatalk 2
I created the back up using cwm and trying to restore through cwm...
Sent from my MB855 using xda app-developers app
Stray2thaB said:
I created the back up using cwm and trying to restore through cwm...
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Are you using a working recovery? Jokers? Twrp? Photon3? Or the ROM manager one? ROM manager version does not work.
Sent from my MB853 using XDA
As far as I know, I am using Clockworkmod Recovery v5.0.2.8. I've tried Rom Manager but I usually get an error while trying to perform a NANDroid backup...
Sent from my MB855 using xda app-developers app
Stray2thaB said:
As far as I know, I am using Clockworkmod Recovery v5.0.2.8. I've tried Rom Manager but I usually get an error while trying to perform a NANDroid backup...
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
as mentioned previously the ROM Manager one DOES NOT WORK. 5.0.2.8 DOES NOT WORK! you NEED to user Jokers, TWRP or the 5.0.2.7-photon3 recoveries ONLY. you can find the working recoveries on my site. choose which one suits you best! don't use Jokers V4 because it won't flash google apps properly.
http://www.motosunfire.com/clockworkmod-recovery/
Ok thanks a lot, I will try the two you just recommended...
Sent from my MB855 using xda app-developers app
OK I downloaded the TWRP recovery you had suggested, I backed up my current from but when I tried to restore a different from I keep getting an error "the process com.android.phone has stopped working" and I have no service now...
Sent from my MB855 using xda app-developers app
Stray2thaB said:
OK I downloaded the TWRP recovery you had suggested, I backed up my current from but when I tried to restore a different from I keep getting an error "the process com.android.phone has stopped working" and I have no service now...
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
alright? well that doesn't say alot? as you could be using any one of 20 different ROMs. which are you using?
na7q said:
alright? well that doesn't say alot? as you could be using any one of 20 different ROMs. which are you using?
Click to expand...
Click to collapse
I am running cm7, or rather was running cm7 coz now my phone is stuck in the boot loop limbo. Kept getting the error "com.android.phone stopped working" and I was unable to make or receive calls all day. So I thought relocking and unlocking the bootloader would do the trick but now I'm stuck on a rock and a hard place. Sssoooooo, do you have any tricks up your sleeves I could use, I would really appreciate it...
I've been able to run a hand full of fastboot commands to bring my phone back out of limbo, I am past the boot image and able to activate with the sprint network. Thank you all who took the liberty of viewing my post, I appreciate the help...
Stray2thaB said:
I am running cm7, or rather was running cm7 coz now my phone is stuck in the boot loop limbo. Kept getting the error "com.android.phone stopped working" and I was unable to make or receive calls all day. So I thought relocking and unlocking the bootloader would do the trick but now I'm stuck on a rock and a hard place. Sssoooooo, do you have any tricks up your sleeves I could use, I would really appreciate it...
Click to expand...
Click to collapse
Stray2thaB said:
I've been able to run a hand full of fastboot commands to bring my phone back out of limbo, I am past the boot image and able to activate with the sprint network. Thank you all who took the liberty of viewing my post, I appreciate the help...
Click to expand...
Click to collapse
hmmm... CDMA user? or GSM? i remember that bug being around in the very early builds of CM7. are you on the latest nightly or stable release?
i might also recommend changing some build prop info (which could be causing this?) to make sure it tells the radio to operate in the correct mode. gsm or cdma. if you look for ro.telophony.default_network=? the ? should be a 4 for CDMA or a 7 for GSM. change to your liking. then reboot. this was an issue in CM9 for the longest time and this is how it was resolved. it's possible it could be the same for CM7.
another option is to of course start over. wipe the cache,data,system partitions, possibly even twice. flash cm7. twice to be safe. then gapps. twice to be safe. then give it another shot.
other than that it might be a bad download or a bad build. so try another if it doesn't work. hope this helps you!
CDMA user, for now I am able to have my phone back on, but I will probably steer away from CM7 AND perhaps try CM10. All I keep finding is an unofficial release, is this the only one there is?
Sent from my MB855 using xda app-developers app
Stray2thaB said:
CDMA user, for now I am able to have my phone back on, but I will probably steer away from CM7 AND perhaps try CM10. All I keep finding is an unofficial release, is this the only one there is?
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
there will never be any officials releases unless somehow Motorola decides they want to give us drivers/source for ICS or JB. which is never. unless we get a leak.
the other day i tried restoring a back up via TWRP but it didnt work until i fastboot flashed boot.img...Alright so i updated my TWRP via goomanager app to the latest version (whatever is on there via goomanager) as in the TWRP forum discussions it was stated that previous versions were not working properly wihen restoring. So today i flashed a new ROM (NOS ROM) but that didnt work so i decided what better time than now to try restoring again, no dice didnt work and i had to fastboot flash the boot img for the restore file to take and boot up just fine again...ok peeps what am doing wrong??? again im fairly new at this flashing ROMS scene but i thought witht he TWRP update i would be good to go. Am i missing some settings ticks/options/checks? i saw a check box that said "recovery" i think in the restore or back up process dont remember which process. i tried going onto the TWRP discussion but it is locked down and states that there will no longer be any support for it...should i just switch to CWM?? thanks in advance to whom ever replies
twrp recovery..
kenohki88 said:
the other day i tried restoring a back up via TWRP but it didnt work until i fastboot flashed boot.img...Alright so i updated my TWRP via goomanager app to the latest version (whatever is on there via goomanager) as in the TWRP forum discussions it was stated that previous versions were not working properly wihen restoring. So today i flashed a new ROM (NOS ROM) but that didnt work so i decided what better time than now to try restoring again, no dice didnt work and i had to fastboot flash the boot img for the restore file to take and boot up just fine again...ok peeps what am doing wrong??? again im fairly new at this flashing ROMS scene but i thought witht he TWRP update i would be good to go. Am i missing some settings ticks/options/checks? i saw a check box that said "recovery" i think in the restore or back up process dont remember which process. i tried going onto the TWRP discussion but it is locked down and states that there will no longer be any support for it...should i just switch to CWM?? thanks in advance to whom ever replies
Click to expand...
Click to collapse
What did you have checked while making the backup? data? recovery? cache? system? and did you rename the back up?
System, data and boot are checked...I didn't mess with the options just hit restore and let it do it's thing...should I change something or check the other 2 boxes (one of them being "recovery" forgot what the other option was)?
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
System, data and boot are checked...I didn't mess with the options just hit restore and let it do it's thing...should I change something or check the other 2 boxes (one of them being "recovery" forgot what the other option was)?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I would check recovery as well and try again.....also make sure to wipe everything before flashing anything
---------- Post added at 12:42 PM ---------- Previous post was at 12:34 PM ----------
canemaxx said:
I would check recovery as well and try again.....also make sure to wipe everything before flashing anything
Click to expand...
Click to collapse
also some roms are picky about which recovery is used to install/backup. I can say I have had no issues backing up stock or custom roms with twrp on my DNA
Alright sounds good maybe later on tonight when I'm at my computer just in case thank you for the tips I as well haven't had much trouble flashing ROMS with TWRP, albeit I've only tried flashing 2 or 3 been very happy with ViperDNA just wanted to check out different ones and easily restore back to viper
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
Alright sounds good maybe later on tonight when I'm at my computer just in case thank you for the tips I as well haven't had much trouble flashing ROMS with TWRP, albeit I've only tried flashing 2 or 3 been very happy with ViperDNA just wanted to check out different ones and easily restore back to viper
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Check out NOS its a great rom
canemaxx said:
Check out NOS its a great rom
Click to expand...
Click to collapse
That's exactly what I was trying when all this happened...I flashed it via flash gui app like I've been doing but for some reason it didn't work...when I went to unlock screen it would pull up HTC splash screen and just stay stuck there... I'm not S-off yet so would that have something to do with NOS ROM not functioning?
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
That's exactly what I was trying when all this happened...I flashed it via flash gui app like I've been doing but for some reason it didn't work...when I went to unlock screen it would pull up HTC splash screen and just stay stuck there... I'm not S-off yet so would that have something to do with NOS ROM not functioning?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
no thats how that rom boots....leave it alone for about 5-10 minutes youlll see the notificatiion light come on and your =e good to go
Let me rephrase that...it boots up, screen comes on silver background from butterfly then I go pull ring to unlock and it pulls up the HTC splash screen once I unlock and will not move from there...so that's when I reset and went back to viper...???
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
Let me rephrase that...it boots up, screen comes on silver background from butterfly then I go pull ring to unlock and it pulls up the HTC splash screen once I unlock and will not move from there...so that's when I reset and went back to viper...???
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Flash the new Nos build, and flash cpalmers kernel after the Rom install and then reboot.
Sent from my ADR6425LVW using Xparent Red Tapatalk 2
Haven't tried it since I posted this, but ok I'll give it another spin/attempt this weekend thanks for the tip
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
Haven't tried it since I posted this, but ok I'll give it another spin/attempt this weekend thanks for the tip
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I may have misread but did you wipe everything before loading nos? I saw what was checked for backup but not about wiping. You should wipe everything-system, then cache, then delvik cache-not exactly in that order (make SURE there IS a backup just in case). Load the rom AND flash the correct image file with adb. Also, many roms when FIRST loading up sit a long time before they start up, not sure if nos does this or not-I have been jumpy about the time sitting with a few roms when waiting was all I needed to do. I have had different Viper versions on a few times and moving to another rom was quirky each time I did so, not sure why.
NOS did that to me too. Just wait....it will load into the setup wizard. I think being s-on, which I still am...twrp isn't able to back up and restore your roms boot.img. just a guess but I to failed to restore a backup when an install went awry. Makes sense to be being that you can't install a kernel from recovery either.
Sent from my HTC6435LVW using xda app-developers app
Ajj915 said:
NOS did that to me too. Just wait....it will load into the setup wizard. I think being s-on, which I still am...twrp isn't able to back up and restore your roms boot.img. just a guess but I to failed to restore a backup when an install went awry. Makes sense to be being that you can't install a kernel from recovery either.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I looked at the install instructions for nos, if you are s-on you need to do one extra step. You have to extract the rom into a folder somewhere to get the image file, copy the image file from it. Flash that image file using adb on your pc and THEN install the rom from your phone with goomanager. Without the image file loaded, I don't think it would work. If you are s-off this step is not needed.
rootntootn said:
I looked at the install instructions for nos, if you are s-on you need to do one extra step. You have to extract the rom into a folder somewhere to get the image file, copy the image file from it. Flash that image file using adb on your pc and THEN install the rom from your phone with goomanager. Without the image file loaded, I don't think it would work. If you are s-off this step is not needed.
Click to expand...
Click to collapse
I get that. I'm purely talking about after a full while that I'm not sure if twrp will restore the boot.img from a nandroid. S-On of course.
Sent from my HTC6435LVW using xda app-developers app
Ajj915 said:
I get that. I'm purely talking about after a full while that I'm not sure if twrp will restore the boot.img from a nandroid. S-On of course.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I believe it will, if it had the image from the get go. I believe that the back up has everything it needs. At least my back ups have never needed an image file. I decided I should try NOS myself and must say it would not go for me (S-off) it kept rebooting into recovery. I was going to try and also flash the boot image but have not done so yet.
---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------
rootntootn said:
I believe it will, if it had the image from the get go. I believe that the back up has everything it needs. At least my back ups have never needed an image file. I decided I should try NOS myself and must say it would not go for me (S-off) it kept rebooting into recovery. I was going to try and also flash the boot image but have not done so yet.
Click to expand...
Click to collapse
Oh yeah, and I restored my back up and that works just fine
rootntootn said:
I believe it will, if it had the image from the get go. I believe that the back up has everything it needs. At least my back ups have never needed an image file. I decided I should try NOS myself and must say it would not go for me (S-off) it kept rebooting into recovery. I was going to try and also flash the boot image but have not done so yet.
---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------
Oh yeah, and I restored my back up and that works just fine
Click to expand...
Click to collapse
Its the kernel in NOS. Flash NOS and then flash cpalmers kernel. Then reboot and do the setup and if you want to change to the zarboz kernel you need to delete system/bin/thermald or rename it to thermald_old.bak
Sent from my HTC6435LVW using Xparent Red Tapatalk 2
Hmmm well I did everything via my cell (been the way I've been flashing ROMS unless something goes wrong then I use ADB on computer) and everything when properly done works fine using Flash GUI APP love that app! I've flashed super charged hatka 320 (used that for a couple weeks) then switched over to viper...both using Flash GUI I tried using NOS but yes no dice loaded up but when I pull the unlock ring for whatever reason the splash screen comes up and it won't budge from there....and as for my original question haha TWRP did not work for me when restoring it tripped out like if it was missing the boot image (done that before so I'm familiar with that behavior haha)
Oh and I'm still S-on
Sent from my HTC6435LVW using xda app-developers app
CharliesTheMan said:
Flash the new Nos build, and flash cpalmers kernel after the Rom install and then reboot.
Sent from my ADR6425LVW using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
That's what mine does too......just wait til the notification light turns orange and you will be all set......be patient.
canemaxx said:
That's what mine does too......just wait til the notification light turns orange and you will be all set......be patient.
Click to expand...
Click to collapse
Really? After it boots up? That's odd but ok I'll give it a shot again but probably tomorrow will post here again if it doesn't work....thanks everyone for responding. I'm out at the moment and need cell to be functioning hahaha just in case
Sent from my HTC6435LVW using xda app-developers app