I just switched over to HTC TB last week. I rooted it and put in Tesla Coil 1.7.1., which runs magnificently.
But I feel I should update it to Gingerbread.
Would that be possible by just flashing a GB rom?
Or do I have to do a manual update first?
Thanks for the help
Everything is new to me now since I switched over from Droid X.
If you have a custom recovery, which you should...then you just flash the ROM (from recovery) and its recommended radio (from bootloader). Oh, and wipe data/cache obviously.
Absolute_Zero said:
If you have a custom recovery, which you should...then you just flash the ROM (from recovery) and it's recommended radio (from bootloader).
Click to expand...
Click to collapse
Yeah, I'm using Rom Manager to reboot to recovery.
So if I just flash the ROM and the recommended radio, my system will update itself to 2.3.4?
Would you happen to know how to REVERT back from 2.3.4 to 2.2.1 also?
Just in case things don't go well.
johnnysyeah said:
Yeah, I'm using Rom Manager to reboot to recovery.
So if I just flash the ROM and the recommended radio, my system will update itself to 2.3.4?
Would you happen to know how to REVERT back from 2.3.4 to 2.2.1 also?
Just in case things don't go well.
Click to expand...
Click to collapse
Just make a nandroid backup. Then if you don't like GB, you can restore your nandroid backup and flash the old radio back.
Absolute_Zero said:
Just make a nandroid backup. Then if you don't like GB, you can restore your nandroid backup and flash the old radio back.
Click to expand...
Click to collapse
Oh wow, much simpler than Droid X.
For Droid X. I'd have to SBF back to Froyo from Gingerbread and only then am I able to reflash my Nandroid backup of a Froyo ROM.
Thanks for the advices!
Time to go ROM hunting
Related
I am trying to restore to one of the nandroid back ups that I did before. I face with the following messages on recovery:
Checking md5 sums...
Erasing boot before restore...
Restoring boot image...
Error while flashing boot image!
What is my problem?
Thanks in advance
What rom are you currently on and which one are you trying to restore?
Abu-7abash said:
What rom are you currently on and which one are you trying to restore?
Click to expand...
Click to collapse
I am on this one:
CyanogenMod 7 for Vibrant (Gingerbread 2.3.4)
and trying to restore to this one:
[2.2.1] Middle Eastern Support Thread [EDT][JVJPJ - JPJPM] - Updated 4/11/2011
barribow said:
I am on this one:
CyanogenMod 7 for Vibrant (Gingerbread 2.3.4)
and trying to restore to this one:
[2.2.1] Middle Eastern Support Thread [EDT][JVJPJ - JPJPM] - Updated 4/11/2011
Click to expand...
Click to collapse
Bingo. You can't restore a 2.2.1 backup while on 2.3. You're gonna have to Odin then flash that rom as per first time Im afraid.
Abu-7abash said:
Bingo. You can't restore a 2.2.1 backup while on 2.3. You're gonna have to Odin then flash that rom as per first time Im afraid.
Click to expand...
Click to collapse
Good catch! I didn't know that. I just Odin'ed, can I restore after Odin?
Whenever you leave cm7, you need to odin to jfd.
I have a guide, if needed.
barribow said:
Good catch! I didn't know that. I just Odin'ed, can I restore after Odin?
Click to expand...
Click to collapse
Not sure, But I guess not since you either odined to 2.2 or 2.1 while Heathen's rom is 2.2.1 so try flashing it again then restore if you've THAT much data you don't want to lose and haven't backed up in any other way.
s15274n said:
Whenever you leave cm7, you need to odin to jfd.
I have a guide, if needed.
Click to expand...
Click to collapse
I read yours, probably had missed it. Lots of info
Thanks though
Abu-7abash said:
Not sure, But I guess not since you either odined to 2.2 or 2.1 while Heathen's rom is 2.2.1 so try flashing it again then restore if you've THAT much data you don't want to lose and haven't backed up in any other way.
Click to expand...
Click to collapse
Am trying to restore now. The reason I went back is because I noticed Ti backup this time didn't bring my SMS stuff to CM7. So now I want to install SMS back up and then back them up then go back to CM7... oh boy long way...frustrating
I unlocked the bootloader and rooted it okay... then I flashed a ROM, that also worked fine. I tried to flash a kernel and now it just gets stuck on the HTC screen. I tried restoring my back up, still the same issue. Tried reflashing the ROM, same issue. Not sure how to get it back to normal at this point.
It sounds like the kernel you flashed is either a 2.3.3 kernel that doesn't work on 2.3.4, or it was a bad flash. You should be able to fix this by holding volume down when booting up (opens HBOOT) then choose Recovery and from the recovery you can then either enable USB Mass Storage device and transfer a stock kernel over USB to your SD card then flash the stock kernel, or if you already have a stock kernel on your SD card, you can just select it from the install from zip menu and flash.
This Kernel should work fine (it's stock with CIQ spyware removed):
http://forum.xda-developers.com/showthread.php?t=1224659
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Coriolis3ffect said:
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Click to expand...
Click to collapse
ROMs usually have kernels. You could just wipe Dalvick cache and cache and flash your original rom (which has it's original kernel). and that should work.
There's a sea of roms. You could try posting on a rom's thread whether a particular kernel is compatible. Just follow the spin of things. Saves from just going round in circles.
Coriolis3ffect said:
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Click to expand...
Click to collapse
Here's a scenario: If you installed a rooted stock 2.3.4 rom then decided to install Silverneedle kernel, your phone will get stuck in this boot-loop because the silverneedle kernel is not compatible with 2.3.4 yet. So by flashing a stock kernel over what is already on there, it should fix the problem. Before you flash the stock kernel clear cache and dalvik. After that flash the kernel and reboot the phone. Chances are it will boot normally. I doubt you will have to reflash a ROM to fix this.
Just cleared the dalvik and the cache, reflashed the ROM hoping to start completely fresh and its still getting stuck...
Coriolis3ffect said:
Just cleared the dalvik and the cache, reflashed the ROM hoping to start completely fresh and its still getting stuck...
Click to expand...
Click to collapse
Then flash a stock kernel. I have had the same problem before. I flashed a ROM, installed a kernel and stuck at HTC boot screen. The fix is to either install a stock kernel through bootloader or flash another ROM in recovery. If you want the best chance of it working the first time, then flash the stock rooted 2.3.4 ROM by xhausx. If you want to try other ROMs and kernels, make sure that your ROM and kernel are compatible. Also use the synergy wipe zip file before flashing to make sure everything is formatted properly. Also, did you flash the extra firmwares that came with the 2.3.4 update? If not, make sure you flash those along with the new radio that just came out.
Sent from my PG86100 using Tapatalk
Take it you didn't do a nandroid before flashing?
Sent from my PG86100 using xda premium
Tried to get my nandroid and it still got stuck..
Perhaps I should've also mentioned that my bootloader still says S-ON and I unlocked it using the HTC unlock method.
sn0b0ard said:
Then flash a stock kernel. I have had the same problem before. I flashed a ROM, installed a kernel and stuck at HTC boot screen. The fix is to either install a stock kernel through bootloader or flash another ROM in recovery. If you want the best chance of it working the first time, then flash the stock rooted 2.3.4 ROM by xhausx. If you want to try other ROMs and kernels, make sure that your ROM and kernel are compatible. Also use the synergy wipe zip file before flashing to make sure everything is formatted properly. Also, did you flash the extra firmwares that came with the 2.3.4 update? If not, make sure you flash those along with the new radio that just came out.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Not sure about any extra firmwares actually.... currently going to try flashing xhaus' ROM and hope that works...
Flashed the superwipe before flashing the ROM, then flashed the ROM... it went to the HTC screen for a second then just vibrated and then turned black.
When I go into the bootloader when it is loading up the images.... it kept saying "No Image!" for all of them. I'm not having any luck with this at all.
Coriolis3ffect said:
When I go into the bootloader when it is loading up the images.... it kept saying "No Image!" for all of them. I'm not having any luck with this at all.
Click to expand...
Click to collapse
Do you have it named exactly PG86IMG.ZIP?
Sent from my PG86100 using xda premium
Okay... you mentioned something about firmwares to flash... which ones are they?
I'm kinda lost at this point because I'm not sure about the specific order in which you are supposed to do things.
Which version of hboot do you have?
Sent from my PG86100 using xda premium
1.50.000 or whatever
Just follow this guide easy. Easy step by step.
http://forum.xda-developers.com/showthread.php?t=1231249
jayharper08 said:
Just follow this guide easy. Easy step by step.
http://forum.xda-developers.com/showthread.php?t=1231249
Click to expand...
Click to collapse
+1 on this. RUU method should be bullet proof
Coriolis3ffect said:
Okay... you mentioned something about firmwares to flash... which ones are they?
I'm kinda lost at this point because I'm not sure about the specific order in which you are supposed to do things.
Click to expand...
Click to collapse
It's in the post that xhausx made for the stock rooted 2.08.651.2 ROM.
URL: http://forum.xda-developers.com/showthread.php?t=1223979
List of new firmwares for the 2.08.651.2 update:
(If you do the RUU method, you should have all the firmwares installed automatically btw...)
Radio & PRI Updates Radio 0.97.10.0808 PRI 1.24_003
PG86IMG_radio_pri.zip (MD5: E28414AAC6F91CE9D7B3615B2999AD3A)
RPM Possible fix for Black SOD
PG86IMG_rpm.zip (MD5: DE69396C8922FAD3AC82E5F836EE95FB)
SBL Secure Bootloader?
PG86IMG_sbl.zip (MD5: 5604349AD611241CF1AC152FD3B0DE45)
TZ Trusted Zone - Not sure of it's purpose
PG86IMG_tz.zip (MD5: 75749FBCCE1331A5A85D2A154E15B276)
PG2F2_SPCUSTOM - No idea what it is
PG86IMG_pg2f2_spcustom.zip (MD5: 7A7DE8659A0771919A14B0C299CA18CC)
Click to expand...
Click to collapse
The link posted is for the GSM Evo 3D... will it work on CDMA?
Quick question. Can I do a nandroid restore after wiping data, cache and dalvik?
If you chose to put it in your external SD card when you made it, yes. wiping the big 3 doesn't wipe the SD card
Sent from my MB870 using XDA App
IDMA.DROID.X2 said:
If you chose to put it in your external SD card when you made it, yes. wiping the big 3 doesn't wipe the SD card
Sent from my MB870 using XDA App
Click to expand...
Click to collapse
So i will be able to go back to my original ROM just as I left it even after wiping the big 3?
Yup! I've got a back ulbof every ROM except MIUI, haven't flashed it yet! Haha
Sent from my MB870 using XDA App
EDIT: Make sure its on the external SD card though. Not sure weather it will be there on the SD card if you put it there then wiped the big 3
IDMA.DROID.X2 said:
Yup! I've got a back ulbof every ROM except MIUI, haven't flashed it yet! Haha
Sent from my MB870 using XDA App
EDIT: Make sure its on the external SD card though. Not sure weather it will be there on the SD card if you put it there then wiped the big 3
Click to expand...
Click to collapse
I have a nandroid on my internal that has endured several data wipes and sbf's. It is a backup of my stock phone before flashing anything. I backed it up in both places just in case.
Sent from my cm7dx2 using XDA App
litetaker said:
So i will be able to go back to my original ROM just as I left it even after wiping the big 3?
Click to expand...
Click to collapse
Well, that depends. If you upgraded to say, Android 2.3.5, then you have a different kernel and the kernel is NOT backed up via Nandroid. So unless you are still on the same android version, then you should SBF back to the base OS version you were on. This was tested extensively about a month or so back and it was determined that a nandroid restore doesn't restore the kernel.
Otherwise, nandroiding back should get you where you were before.
iBolski said:
Well, that depends. If you upgraded to say, Android 2.3.5, then you have a different kernel and the kernel is NOT backed up via Nandroid. So unless you are still on the same android version, then you should SBF back to the base OS version you were on. This was tested extensively about a month or so back and it was determined that a nandroid restore doesn't restore the kernel.
Otherwise, nandroiding back should get you where you were before.
Click to expand...
Click to collapse
Good to know! I missed the tests done, I thought it backed up everything.
Sent from my MB870 using XDA App
iBolski said:
Well, that depends. If you upgraded to say, Android 2.3.5, then you have a different kernel and the kernel is NOT backed up via Nandroid. So unless you are still on the same android version, then you should SBF back to the base OS version you were on. This was tested extensively about a month or so back and it was determined that a nandroid restore doesn't restore the kernel.
Otherwise, nandroiding back should get you where you were before.
Click to expand...
Click to collapse
So if MIUI is saying that it is running Android 4.0.3, and CM7 is Android 2.3.7, then is it not ok to nandroid back to CM7 from MIUI?
jsgraphicart said:
So if MIUI is saying that it is running Android 4.0.3, and CM7 is Android 2.3.7, then is it not ok to nandroid back to CM7 from MIUI?
Click to expand...
Click to collapse
No, it should be fine. 4.0.3 is STILL using the same kernel. 4.0.3 is the OS version, not necessarily the kernel version.
Since the bootloader is still locked, flashing the DX2 MIUI still keeps the 2.3.4 kernel. All that gets replaced are the system files. So, nandroiding back to CM7 (which is what I did) is fine because you are still running the same kernel.
At least, that's how I read it when I researched a little on this and with some other people posting their explanations as well.
The reason you shouldn't flash 2.3.4-based ROMs over 2.3.5 is because the kernel version was changed. Remember, the kernel can ONLY be updated via a Verizon-approved OTA. The 2.3.5 update is not an official release, but it DID come from Motorola servers, so it has the signature in it that the X2 is looking for when the kernel is attempted to be upgraded. Hence, that is why flashing a 2.3.4-based ROM over a 2.3.5 image is not a good thing. Same goes with flashing a 2.3.5 ROM over a 2.3.4 image. It's just not a good idea and could pose problems down the road.
iBolski said:
No, it should be fine. 4.0.3 is STILL using the same kernel. 4.0.3 is the OS version, not necessarily the kernel version.
Since the bootloader is still locked, flashing the DX2 MIUI still keeps the 2.3.4 kernel. All that gets replaced are the system files. So, nandroiding back to CM7 (which is what I did) is fine because you are still running the same kernel.
At least, that's how I read it when I researched a little on this and with some other people posting their explanations as well.
The reason you shouldn't flash 2.3.4-based ROMs over 2.3.5 is because the kernel version was changed. Remember, the kernel can ONLY be updated via a Verizon-approved OTA. The 2.3.5 update is not an official release, but it DID come from Motorola servers, so it has the signature in it that the X2 is looking for when the kernel is attempted to be upgraded. Hence, that is why flashing a 2.3.4-based ROM over a 2.3.5 image is not a good thing. Same goes with flashing a 2.3.5 ROM over a 2.3.4 image. It's just not a good idea and could pose problems down the road.
Click to expand...
Click to collapse
Ok, that makes sense. I figured it would be fine but didnt know the technical details.
I've flashed my 2.3.4 backups over 2.3.5 quite a bit since my cheesecake backup is 2.3.5 and I've never had any issues. Do we really know if the kernel changed? I never really looked at the kernel version on 2.3.5.
Sent from my MB870 using XDA App
T3HBR1AN said:
I've flashed my 2.3.4 backups over 2.3.5 quite a bit since my cheesecake backup is 2.3.5 and I've never had any issues. Do we really know if the kernel changed? I never really looked at the kernel version on 2.3.5.
Sent from my MB870 using XDA App
Click to expand...
Click to collapse
Back in December, I asked the question about nandroiding and if it replaced the kernel. Motcher (and ashclepdia) helped out with this one. Motcher SBF'd to 2.3.4 and then nandroided back to Eclipse 2.0.3 (which is 2.3.5) based and the kernel version came up as 00005 which is the 2.3.4 kernel. So, Nandroiding does NOT replace the kernel.
Here's the posted that he posted about this:
http://forum.xda-developers.com/showpost.php?p=20808392&postcount=20
It may be that the differences are minor enough that it won't cause issues, but if the official 2.3.5 ever comes out, it might be best to always SBF back to 2.3.4 if you have to just to be on the safe side. I guess the moral of the story is, do this at your own risk.
Ok I tried to nandroid back to cm7 from Miui and I got a md5-sum mismatch message, and I wasn't able to go back. Do I need to wiped the big 3 every time I nandroid ?
Sent from my DROID X2 using XDA App
bandit1224 said:
Ok I tried to nandroid back to cm7 from Miui and I got a md5-sum mismatch message, and I wasn't able to go back. Do I need to wiped the big 3 every time I nandroid ?
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
No. That means the md5-sum hash key that was generated after the backup was created isn't matching with your nandroid backup. It means possibly your backup is corrupted.
Wiping the big three has nothing to do with nandroiding.
Uninstall bsr -either cm7 or orig. Then reinstall cm7 bsr. It worked for me On cm7. BTW Be sure not to use any spaces when renaming.
failed restore
So im trying to reload my backup from my sd card. I have made 2 thus far and neither work.
I am on the Rogers network on a i747 with the dlk4 baseband. CWM, rooted, stock rom. When i try to restore it loads a few things (ie. system), and starts loading the DATA portion. Which at this point i get an error message. I reboot it, and my phone gets hung up at the samsung loading screen.
I have tried wiping the big 3 and also under mount and unmount i formated system before restoring as well with no success.
Could it be that my version of CWM is 5.5.0.4.. And, from my understanding I dont think it would be the cause, but maybe because i made the backup after being rooted and flashing cwm
Sykotyk said:
So im trying to reload my backup from my sd card. I have made 2 thus far and neither work.
I am on the Rogers network on a i747 with the dlk4 baseband. CWM, rooted, stock rom. When i try to restore it loads a few things (ie. system), and starts loading the DATA portion. Which at this point i get an error message. I reboot it, and my phone gets hung up at the samsung loading screen.
I have tried wiping the big 3 and also under mount and unmount i formated system before restoring as well with no success.
Could it be that my version of CWM is 5.5.0.4.. And, from my understanding I dont think it would be the cause, but maybe because i made the backup after being rooted and flashing cwm
Click to expand...
Click to collapse
this is a thread for the motorola droid x2.
oops
Lorenzo VonMatterhorn said:
this is a thread for the motorola droid x2.
Click to expand...
Click to collapse
i've been searching threads with search tool....guess i wasn't paying attention.
Cheers
I'm happy with my current setup on Eclipse, but of course I'm curious about CM7 and CM9. I was wondering, would it be possible to:
-nandroid backup my current eclipse setup
-follow install instructions for CM7/9 or even getting back to stock rooted or any other ROM.
Then, if I choose I prefer Eclipse over CM7/9 whatever, just simply restore my nandroid backup of Eclipse to get back to my current setup? or would I have to go through all the procedures again?
I guess my question boils down to: Does the nandroid backup backup everything as is? Or can I restore between different nandroids on different ROMs without worry?
flanker1743 said:
I'm happy with my current setup on Eclipse, but of course I'm curious about CM7 and CM9. I was wondering, would it be possible to:
-nandroid backup my current eclipse setup
-follow install instructions for CM7/9 or even getting back to stock rooted or any other ROM.
Then, if I choose I prefer Eclipse over CM7/9 whatever, just simply restore my nandroid backup of Eclipse to get back to my current setup? or would I have to go through all the procedures again?
I guess my question boils down to: Does the nandroid backup backup everything as is? Or can I restore between different nandroids on different ROMs without worry?
Click to expand...
Click to collapse
It will not back up your kernel therefore, make your nandroid. SBF back then root install Cm9. If you want to go back you will have to use ota root keeper take the ota then restore your nandroid to be back on eclipse
Sent from my MB870 using xda premium
flanker1743 said:
I'm happy with my current setup on Eclipse, but of course I'm curious about CM7 and CM9. I was wondering, would it be possible to:
-nandroid backup my current eclipse setup
-follow install instructions for CM7/9 or even getting back to stock rooted or any other ROM.
Then, if I choose I prefer Eclipse over CM7/9 whatever, just simply restore my nandroid backup of Eclipse to get back to my current setup? or would I have to go through all the procedures again?
I guess my question boils down to: Does the nandroid backup backup everything as is? Or can I restore between different nandroids on different ROMs without worry?
Click to expand...
Click to collapse
trafalger888 said:
It will not back up your kernel therefore, make your nandroid. SBF back then root install Cm9. If you want to go back you will have to use ota root keeper take the ota then restore your nandroid to be back on eclipse
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
if you have any trouble following the instructions given here, let us know.
Ah. Because CM7 and 9 are based on 2.3.4, whereas Eclipse is 2.3.5 based, correct?
flanker1743 said:
Ah. Because CM7 and 9 are based on 2.3.4, whereas Eclipse is 2.3.5 based, correct?
Click to expand...
Click to collapse
Correct
Sent from my MB870 using xda premium
I try and keep two NANDroid by...
One is stock untouched 2.3.4
The other is stock untouched 2.3.5...
Flashing is quick and easy, so all I have to do is wipe and install...
DROID DOES, Apple did...like I forgot when
Pixelation said:
I try and keep two NANDroid by...
One is stock untouched 2.3.4
The other is stock untouched 2.3.5...
Flashing is quick and easy, so all I have to do is wipe and install...
DROID DOES, Apple did...like I forgot when
Click to expand...
Click to collapse
Here, Here!
i have updated to jellybean and its not all that great right now and i really love TeamVenow Viper4g 2.0.2 rom. Is it possible to restore my viper4g backup now that im on the new firmware that came with the jellybean update?
wmarshall said:
i have updated to jellybean and its not all that great right now and i really love TeamVenow Viper4g 2.0.2 rom. Is it possible to restore my viper4g backup now that im on the new firmware that came with the jellybean update?
Click to expand...
Click to collapse
I believe folks in the Viper ROM thread have updated their firmware and are still using ViperROM with no issues.
wmarshall said:
i have updated to jellybean and its not all that great right now and i really love TeamVenow Viper4g 2.0.2 rom. Is it possible to restore my viper4g backup now that im on the new firmware that came with the jellybean update?
Click to expand...
Click to collapse
im running viper and updated firmware and have to issues
josh030181 said:
im running viper and updated firmware and have to issues
Click to expand...
Click to collapse
Your running viper with problems? My backup won't restore. Maybe I should do a fresh installed to get back to the viper Rom
I can't say anything for viper rom. But one thing i noticed when i switch from jb to ics is that my DATA backup in twrp (from jb) did not transfer back to ics. I had to restore a previous ics DATA backup for my phone to boot correctly.
See if a fresh ics install works first, then restore data.
Shad Stang said:
I can't say anything for viper rom. But one thing i noticed when i switch from jb to ics is that my DATA backup in twrp (from jb) did not transfer back to ics. I had to restore a previous ics DATA backup for my phone to boot correctly.
See if a fresh ics install works first, then restore data.
Click to expand...
Click to collapse
My ics backups from twrp wont restore either. i tried a fresh install of viperrom and it wont boot up. Which fresh ics rom did you use?
wmarshall;35736875Which fresh ics rom did you use?[/QUOTE said:
First I wiped cache, dalvic cache, factory reset, then wiped system. after that I installed stock with goodies 2.16 (being s-off) and it booted to ics no problem. I then restored my jb backup data and my phone didnt load the os. It finally loaded when i restored it with my ics backup data i made earlier before i upgraded to jb.
If your s-on i cant be certain that ics will load up. but you can try fastboot flashing the boot.img file inside the rom zip.
Click to expand...
Click to collapse
Shad Stang said:
First I wiped cache, dalvic cache, factory reset, then wiped system. after that I installed stock with goodies 2.16 (being s-off) and it booted to ics no problem. I then restored my jb backup data and my phone didnt load the os. It finally loaded when i restored it with my ics backup data i made earlier before i upgraded to jb.
If your s-on i cant be certain that ics will load up. but you can try fastboot flashing the boot.img file inside the rom zip.
Click to expand...
Click to collapse
I am s-on. I'll try to flash the boot.img hopefully that will work. I'm really not liking this jb update.
wmarshall said:
I am s-on. I'll try to flash the boot.img hopefully that will work. I'm really not liking this jb update.
Click to expand...
Click to collapse
flashed the boot.img in fastboot then restored my backup and now im back to viperrom
It's the kernel. I couldn't go back either until I flashed a different kernel