Related
So, yesterday, I decided to finally jump into the abyss and try to root my Evo. Luckily, everything went completely smooth the first time (never had that happen with any other device). I was actually surprised how easy this root was.
Anyway...my question is, if I decide to flash another ROM on my phone, or rather, in 10 minutes WHEN I flash another ROM onto my phone, if I decide I don't like it, how do I reflash my original NANDROID backup back onto the phone?
I was able to navigate on my SD to where the backup was saved, but shouldn't it be a ZIP file or something? I only have individual backup files.
Also, sorry for the noob question.
Thanks in advance for your help
You go into recovery to do a nandroid restore. Its not something you flash. There is an option for backups and restore. You just run those. I like to do a full wipe before a restore though, just in case. Oh, and keep your backups in the original folder, thats where recovery will get them from
I appreciate the quick response! Thanks
No prob, hope it helped
It definitely helped to get back to the stock ROM, but now it appears as though no other ROMs are working for me. I've tried MIUI and MikFroyo, and they both get stuck in boot loops. There's something I'm apparently not doing right. Hmmm.
Did you wipe data/cache/dalvik before flashing the roms?
mosesport said:
It definitely helped to get back to the stock ROM, but now it appears as though no other ROMs are working for me. I've tried MIUI and MikFroyo, and they both get stuck in boot loops. There's something I'm apparently not doing right. Hmmm.
Click to expand...
Click to collapse
Are you updated to the latest Radio and pri? You have to check what version you have and what version you need to flash the rom you want to use. That is most likely the problem. I know older kernels do not like the new radio or pri. You probably have to update them and you should be fine.
Hi guys,
New to xda.. I own a defy with 2.2.2 official SEA. I want to update to CM7 RC0, without losing the downgrade ability. After reading a lot in xda, I've got a fair amount of knowledge to flash my phone. Just have a couple of queries..
6) Can I restore my phone to send it to warranty after flashing CM7?
- You can in these two situations
1 - You have a full SBF of your original ROM (for carriers that already released 2.2 is very easy to find one)
2 - You have a nandroid backup AND a fixed SBF of the version you need.
Click to expand...
Click to collapse
Quick question:
Considering option 1, I have the official ROM (full sbf, 2.2.2 for India) downloaded here. If I flash to CM7, can I re-flash it with the official full sbf to claim warranty? Considering the scenario that I only have contacts and sms to restore and I don't want to restore settings, apps and all. I like to do them anew (even if it takes time).
Technically, that would be like formatting the drive which has the operating system, instead of restoring an image.. Is that possible? Is Nandroid Backup + fixed sbf is the only way to go back to the stock OS to claim warranty?
P.S. - I still don't get what fixed sbf is. Can anyone help?
Just create a backup of your current OS if anything happens restore it.
Sent from my MB525 using XDA Premium App
ATXiceman512 said:
Just create a backup of your current OS if anything happens restore it.
Click to expand...
Click to collapse
You mean Nandroid backup? Can i restore just that file (and not the sbf) in case anything goes wrong?
If your device is rooted download the 1.4.2 version of 2ndinit go into custom recovery and create a backup, then boot back up normally and connect device to the computer and copy the backup to a safe place on your computer, so if you ever need to back it up, you will have the file.
Sent from my MB525 using XDA Premium App
I mean do I always need an sbf file to restore an image?
No you only need sbf. file to flash a image, to restore and image all you need is a copy of a backup.
Hmm.. okay... Consider this scenario:
1. I'm having official 2.2.2 SEA ROM
2. I just want to root, install a custom recovery (take a backup in Nandroid), make changes to the current ROM and I'm NOT flashing a new ROM ie like CM7.
3. Can I just restore the backup from recovery if something goes wrong (without any sbf of course)?
4. Do I still have to install 2nd init in that case?
P.S. - Thanks to your patient replies bro.. Much appreciated
Yes you can downgrade back to sea version using sbf file
Just make a nandroid backup if anything goes wrong restore the nandroid you made plus flash it with the fixed or full sbf file of sea and it will bring everything back the way it was that's what i did anyway and it worked
Let me know how cm7 is on the SEA version if it works stable ill install it
Cheers
WolVish said:
Hmm.. okay... Consider this scenario:
1. I'm having official 2.2.2 SEA ROM
2. I just want to root, install a custom recovery (take a backup in Nandroid), make changes to the current ROM and I'm NOT flashing a new ROM ie like CM7.
3. Can I just restore the backup from recovery if something goes wrong (without any sbf of course)?
4. Do I still have to install 2nd init in that case?
P.S. - Thanks to your patient replies bro.. Much appreciated
Click to expand...
Click to collapse
Yes 2ndinit is a custom recovery program as long as you have that you wont need sbf. Files. Sbf. Files are used with RSD lite in order to install custom roms. You can use any recovery program you want, best I have found to use on the defy is 1.4.2 version of 2ndinit.
Sent from my MB525 using XDA Premium App
Mem check your message please
Sent from my MB525 using XDA Premium App
memz180 said:
Yes you can downgrade back to sea version using sbf file
Just make a nandroid backup if anything goes wrong restore the nandroid you made plus flash it with the fixed or full sbf file of sea and it will bring everything back the way it was that's what i did anyway and it worked
Click to expand...
Click to collapse
Why should i use Nandroid, If I want to flash with full sbf of my SEA official ROM?It'll be factory fresh right?
Let me know how cm7 is on the SEA version if it works stable ill install it
Cheers
Click to expand...
Click to collapse
Sure.. But in Quarx's thread, It was advised to flash Nordic ROM first before installing CM7.
WolVish said:
Why should i use Nandroid, If I want to flash with full sbf of my SEA official ROM?It'll be factory fresh right?
I just restored my old nandroid and flashed with the fixed sbf but i believe if you do a full sbf it will result in the same thing both ways should work
Sure.. But in Quarx's thread, It was advised to flash Nordic ROM first before installing CM7.
Click to expand...
Click to collapse
Yes thats correct some people have installed over the SEA version and its full working im yet to test this i have however tested the NORDIC II version and flashed cm7 beta 6 and that did work nicely but i went back to SEA15 until cm7 releases a more bug free version.
memz180 said:
Yes thats correct some people have installed over the SEA version and its full working im yet to test this i have however tested the NORDIC II version and flashed cm7 beta 6 and that did work nicely but i went back to SEA15 until cm7 releases a more bug free version.
Click to expand...
Click to collapse
What i found in the Official SEA 2.2.2 ROM's thread
ok make sure you do not install CM7 directly on this rom, else boot looping.
Please follow the cyanogenmod7 FAQ point 7. http://forum.xda-developers.com/show....php?t=1065798
i tried and was stuck on boot loop.
Again FLASHED this sea15 sbf via rsd lite back to square1 now need to start the process all again.
Click to expand...
Click to collapse
Nordic is the way to go it seems..
Nice find because i just got my sea15 back i listened to someone from here like a idiot they said they were running SEA15 with cm7 which is a lie because it when i installed cm7 i got a never ending boot loop so id like to say it does not work with sea15 it took me an 1hr to restore all my stuff back to the way it was so yes NORDIC I or II is the way to go thanks for the info
You're welcome mate.. Heard review that RC0 is way better than Beta6..
Finnaly the thread i've been looking for.
I'm currently on official German 2.2.2. I really want to try out CM7 but the tutorials keep telling me I need a sbf (wich is not available at this moment) of my version if I want to downgrade again.
So just to be sure:
Having a sbf is not an absolute must?
And in the case anything goes awry (eg. boot loop) I just have to restore it via my nandroid backup, unroot, deinstall 2ndInit, wipe and I'm practically back were I started, right?
ShiroHouseki said:
I'm currently on official German 2.2.2. I really want to try out CM7 but the tutorials keep telling me I need a sbf (which is not available at this moment) of my version if I want to downgrade again.
Click to expand...
Click to collapse
That's correct. Even if you can't find a full sbf (carrier released version of your OS, usually a large file, 200-300 MB), make sure you have one nandroid backup of your data/settings and a fixed sbf (usually stripped down version, less size <50 MB) of your current OS. This would enable you to re-flash in case you have to claim warranty.
So just to be sure:
Having a sbf is not an absolute must?
Click to expand...
Click to collapse
I don't think so. You MUST have one if you want to claim warranty. Even if you don't need warranty, still you need either Nordic ROM or UK ROM (sbf files, mind you )to be flashed first to install CM7.. Other ROMs are not recommended.
And in the case anything goes awry (eg. boot loop) I just have to restore it via my nandroid backup, unroot, deinstall 2ndInit, wipe and I'm practically back were I started, right?
Click to expand...
Click to collapse
This only works If you flashed with nandroid + fixed sbf of the Nordic/UK ROM.
OR
You have the full sbf of your current ROM, which you can flash from RSD lite.
Hope this helps...
P.S. - Can anyone confirm these answers?
Aww, well i guess i'll be waiting for the sbf files then
Well, thank you anyway for the info.
Who releases this sbf files anyway? Are they somehow extracted out of offical update packages or are they leaked from service contractors?
I am also confused. I thought a nandroid was a complete image of the phone and didn't require an SBF?
Putting it in PC terms I considered a nandroid the equivilent to a ghost image of a HDD? So if I had a PC with XP on it and took a ghost image of that it would be a complete copy of the drive. I could then install Vista on that drive and when / if I wanted to restore the ghost image and it would restore XP onto that system?
I understood an SBF to be a system image as such, but not including the very base level stuff that a nandroid backup would have and hence why you can flash a 2.2.2 rom but need a 2.2 SBF flashed on the phone?
Or am i getting confused?
ShiroHouseki said:
Aww, well i guess i'll be waiting for the sbf files then
Well, thank you anyway for the info.
Who releases this sbf files anyway? Are they somehow extracted out of offical update packages or are they leaked from service contractors?
Click to expand...
Click to collapse
I think your German 2.2.2 ROM has been added only yesterday. Go to www.motorola.com/update, select your region - Select MOTODEFY - Follow instructions.. (Don't forget to do a hard reset after updating )
Full sbf s are released by the Manufacturers/Carriers. It's like untouched windows XP cd. You can directly update via MSU or use RSDlite to flash it..
Fixed sbf s can be made by anyone, maybe you or me, by making some tweaks, just like we do to Windows XP using nlite (which i'm still not that familiar with )
So i installed CM 7.1 i think from rom manager but it wouldn't go past the boot logo with the skating droid. so i took battery out and went to recovery mode and i think i accidentally restored one of my Motorola Droid data and now my phone wont go past the Google CM boot logo i think I'm screwed any suggestions? please help. i guess I'm a noob and sorry if there was something similar to this posted already i just can't find the answer to my problem thank you.
additional info:
us - Tmobile
rooted with gingerbreak
2nd init boot-loader
was running perfect until i accidentally restore the wrong data
oh and yes I've tried data wipe not working
Do you happen to have a nandroid backup of your stock rom you've had before ?
A nandroid backup is what you should have created using CWM recovery. Just restore it with CWM.
You don't have a nandroid backup ?
Flash the full SBF of your original stock rom (the one you had before flashing cm7). This should be a 2.2 Froyo whatever rom. Connect defy to pc, open rsd lite, start the phone and enter the bootloader and flash the sbf using rsd lite.
Have you installed Froyo (2.2) before going to Cm7? If not (you still had Eclair 2.1) then this is the problem.
However, get 2.2 on that phone and flash cm7 again following this guide http://forum.xda-developers.com/showthread.php?t=1054447
Instructions for some of these steps can be found here: http://forum.xda-developers.com/showthread.php?t=1216982
Also, be patient! When the phone boots for the first time after a flash that may take a while!
Try wiping data cache partition and Dalvik cache from the custom recovery..
Sent from my MB525 using Tapatalk
tdlr said:
Do you happen to have a nandroid backup of your stock rom you've had before ?
A nandroid backup is what you should have created using CWM recovery. Just restore it with CWM.
You don't have a nandroid backup ?
Flash the full SBF of your original stock rom (the one you had before flashing cm7). This should be a 2.2 Froyo whatever rom. Connect defy to pc, open rsd lite, start the phone and enter the bootloader and flash the sbf using rsd lite.
Have you installed Froyo (2.2) before going to Cm7? If not (you still had Eclair 2.1) then this is the problem.
However, get 2.2 on that phone and flash cm7 again following this guide http://forum.xda-developers.com/showthread.php?t=1054447
Instructions for some of these steps can be found here: http://forum.xda-developers.com/showthread.php?t=1216982
Also, be patient! When the phone boots for the first time after a flash that may take a while!
Click to expand...
Click to collapse
thanks alot for some reason rsd lite would not detect my phone on windows 7.
this is what my phone say at the time
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x000910
DRM Version: N / A
AP Die ID: 2190001435d15e010000d8ff2100
BP Die ID: 0000000000000000000000000000
AP Public ID: 67fb0d892ad966d841afedffd5eda9e7a1261a1a
BP Public ID: 0000000000000000000000000000000000000000
I'm about to just flash froyo since that's what i had hope it works and thanks for the help i appreciate it.
crlx1906 said:
So i installed CM 7.1 i think from rom manager but it wouldn't go past the boot logo with the skating droid. so i took battery out and went to recovery mode and i think i accidentally restored one of my Motorola Droid data and now my phone wont go past the Google CM boot logo i think I'm screwed any suggestions? please help. i guess I'm a noob and sorry if there was something similar to this posted already i just can't find the answer to my problem thank you.
additional info:
us - Tmobile
rooted with gingerbreak
2nd init boot-loader
was running perfect until i accidentally restore the wrong data
oh and yes I've tried data wipe not working
Click to expand...
Click to collapse
hello sir,
i am facing the same problem with my defy. want to know have you got any solution to that. i am having nandroid backup of my froyo rom. but how to install it with CWR when the phone is not even go beyond bootscreen. i am not much familiar with android. its my first android cell. please help me sir.
waiting for ur reply
are u getting any errors while booting up?
Hi all,
I have a little problem with my Gio that I couldn't solve with googling and searching.
I immediately rooted the phone (I downloaded the rooting kit from here) and everything went right.
Everything started when I installed the wrong CWM from phiexz (from here)
- After flashing CWM ext4-only, it got bricked (*).
- So I flashed the stock recovery (from the same thread) via ODIN, in upload mode: my phone seemed restored, could turn on normally but when I booted into recovery mode it jus stucked on the samsung logo (just like it did when it was "fully"-bricked).
- So, with the phone turned on normally, I typed the "factory reset code", but then it went back fully-bricked (that actually surprised me...)
- Then I flushed CWM ext+rfs and it went back half-bricked
- I again tried factory reset with the same result
- I flushed the stock recovery, making it again half-bricked
(*) I guess I read it mentioned as "soft bricked": when I turn the phone in recovery or nurmally, it just shaws "SAMSUNG www.samsung.com", but download mode worked
Now I'm using it this way, with my original rom (customized by my phoning operator):
Android version: 2.2.1
Base band varsion: S5660XXKB9
Kernel version: 2.6.32.9-perf [email protected] #1
Build number: FROYO.AIKD2
What I wanted (and still want) to do is install CWM, make a back up of the ROM now installed and finally install cyanogen from phiexz (flash cwm and getting it to work, run the backup, run ext4formatter, flash cyanogen).
I could of course go without the backup.
What do you think I should do? Any help would be appreciated
Thanks a lot
Davide
davide_k said:
Hi all,
I have a little problem with my Gio that I couldn't solve with googling and searching.
I immediately rooted the phone (I downloaded the rooting kit from here) and everything went right.
Everything started when I installed the wrong CWM from phiexz (from here)
- After flashing CWM ext4-only, it got bricked (*).
- So I flashed the stock recovery (from the same thread) via ODIN, in upload mode: my phone seemed restored, could turn on normally but when I booted into recovery mode it jus stucked on the samsung logo (just like it did when it was "fully"-bricked).
- So, with the phone turned on normally, I typed the "factory reset code", but then it went back fully-bricked (that actually surprised me...)
- Then I flushed CWM ext+rfs and it went back half-bricked
- I again tried factory reset with the same result
- I flushed the stock recovery, making it again half-bricked
(*) I guess I read it mentioned as "soft bricked": when I turn the phone in recovery or nurmally, it just shaws "SAMSUNG www.samsung.com", but download mode worked
Now I'm using it this way, with my original rom (customized by my phoning operator):
Android version: 2.2.1
Base band varsion: S5660XXKB9
Kernel version: 2.6.32.9-perf [email protected] #1
Build number: FROYO.AIKD2
What I wanted (and still want) to do is install CWM, make a back up of the ROM now installed and finally install cyanogen from phiexz (flash cwm and getting it to work, run the backup, run ext4formatter, flash cyanogen).
I could of course go without the backup.
What do you think I should do? Any help would be appreciated
Thanks a lot
Davide
Click to expand...
Click to collapse
Backup and flash cyanogen
Maybe use an old version of CWM so extformatter isnt needed
Sent from my GT-S5660 using xda premium
dont use cwm & cyanogenMod on froyo baseband
Phiexz: I'm intrigued by the fact a Froyo baseband would cause issues with CWM, which doesn't run the radio... Care to expand a little on that?
Darkshado said:
Phiexz: I'm intrigued by the fact a Froyo baseband would cause issues with CWM, which doesn't run the radio... Care to expand a little on that?
Click to expand...
Click to collapse
i dont know, never tried cwm on froyo
but, i think the problem is bootloader & kernel
someone said gingerbread & froyo using different kernel & method of bootloader
Different bootloader images could explain those issues, I guess.
phiexz said:
dont use cwm & cyanogenMod on froyo baseband
Click to expand...
Click to collapse
What a pity Any suggestions about where to find a recovery image and a rom (the more like cyanogen, the better) that suits my phone?
EDIT: By the way, isn't there a way to upgrade and then install cyanogen, or at least upgrade to stock Gingerbread?
davide_k said:
What a pity Any suggestions about where to find a recovery image and a rom (the more like cyanogen, the better) that suits my phone?
EDIT: By the way, isn't there a way to upgrade and then install cyanogen, or at least upgrade to stock Gingerbread?
Click to expand...
Click to collapse
Have you tried updating your phone with your PC via Kies. If that doesn't work you can update to one of the official firmwares using Odin. Here's a link to the official firmware, and here's a link to instructions on flashing via Odin.
koodiifin said:
Have you tried updating your phone with your PC via Kies. If that doesn't work you can update to one of the official firmwares using Odin. Here's a link to the official firmware, and here's a link to instructions on flashing via Odin.
Click to expand...
Click to collapse
Thanks a lot! Updgrade vie Kies worked well, now everything works, also recovery mode...
Android version: 2.3.6
Base band version: S5660XXKT4
Kernel version: 2.6.35.7-perf-CL843729 [email protected] #1
Build version: GINGERBREAD.AIKT2
Of course, it is still my phone operator's rom... By hte way, it isn't rooted any more, i'll have do to it again...
So, I suppose now I can flush CWM (ext4+rfs), backup the current ROM, run ext4formatter, flush CWM ext4 (is this needed?), and finally flush cyanogenmod , can't I?
Thanks a lot for supporting me
Davide
davide_k said:
Thanks a lot! Updgrade vie Kies worked well, now everything works, also recovery mode...
Android version: 2.3.6
Base band version: S5660XXKT4
Kernel version: 2.6.35.7-perf-CL843729 [email protected] #1
Build version: GINGERBREAD.AIKT2
Of course, it is still my phone operator's rom... By hte way, it isn't rooted any more, i'll have do to it again...
So, I suppose now I can flush CWM (ext4+rfs), backup the current ROM, run ext4formatter, flush CWM ext4 (is this needed?), and finally flush cyanogenmod , can't I?
Thanks a lot for supporting me
Davide
Click to expand...
Click to collapse
No problem. Yes what I would do is:
-Setup everything how you like it on the stock ROM
-Flash CWM(ext4+rfs) from stock recovery
-Make a nandroid backup on CWM(ext4+rfs)
-Then flash CWM(ext4)
-Run ext4formatter
-Flash latest CM7.2 zip
-Flash latest CM7.2 patch zip
-Wipe data/factory reset
-Flash Google apps
-Setup everything how you like on the CM7.2 ROM
-Make a nandroid backup on CWM(ext4)
And then if you need to switch back to stock you will either have to try updating via Kies (from CM7.2 (this should work)) or download an official firmware and flash it via Odin (which will format your phone to RFS), once you have the phone back to a stock gingerbread again you can flash CWM(ext4+rfs) again, then restore your nandroid backup from CWM(ext4+rfs)
Installed cyanogen without problems... Thanks a lot for the support!
Davide
I think i have read it somewhere in xda forum, it said that
latest cwm is only support edify scripting which is used in gingerbread, while froyo are still using amend scripting.
May be that's explain why the latest CWM doesn't work if you ROM are still using Froyo.
sangkelana said:
I think i have read it somewhere in xda forum, it said that
latest cwm is only support edify scripting which is used in gingerbread, while froyo are still using amend scripting.
May be that's explain why the latest CWM doesn't work if you ROM are still using Froyo.
Click to expand...
Click to collapse
I think I'm having the same problem as OP, I have an s5660 rooted, and followed instructions http://forum.xda-developers.com/showpost.php?p=16979859&postcount=549 to install CWM 5.2.7 (cwm-5.0.2.7-ext4+rfs-odin.tar.md5).
Previously I was able to access recovery menu by holding HOME + POWER ON, but now the thing freezes at 1st samsung logo screen. Only now I've come to learn Froyo is not supported. It wasn't mentioned in any article I had read.
I think I will try flash the stock recovery, but I'm scared if it fails I will brick the phone.
Can anyone say, is there an alternative to CWM that will allow me to perform a full system backup that can easily restore the phone in case it's bricked... (and will work on Froyo 2.2.1). I would prefer to backup before attempting any further mods.
The reason I did this in the first place was to overcome "internal memory is low" issue. So far I have been able to move some apps to SD card using Link2SD app but I would like to do nandroid backup before I have a chance to really screw things up. This is my first time doing anything like this and it's my wife's phone, so I have to be extra careful. I tried googling "s5660 froyo nandroid backup", which brought me here.
Any advice is appreciated.
Same problem
Hi!
I have the same problem, did you ever find a solution?
I've installed various ROMs in an attempt to get back to working condition but can't seem to get past the samsung screen.
The problem is, I can't find any stock firmware downloads that still work!! I've been thorough pages and pages of links and keep hitting dead ends. Does anyone have a stock firmware version I can flash with ODIN and at least have a working Gio again!
Many thanks,
orangejuice43 said:
Hi!
I have the same problem, did you ever find a solution?
I've installed various ROMs in an attempt to get back to working condition but can't seem to get past the samsung screen.
The problem is, I can't find any stock firmware downloads that still work!! I've been thorough pages and pages of links and keep hitting dead ends. Does anyone have a stock firmware version I can flash with ODIN and at least have a working Gio again!
Many thanks,
Click to expand...
Click to collapse
download from here:
http://www.sammobile.com/firmwares/database/GT-S5660/
I have a SPH-L710 with a stock ROM and CWM root, I just tried to flash a boot animation and am now stuck in a boot loop. I did not make a backup before I tried this. I have wiped cache,div and did fact reset and can not get out of boot loop...................PLEASE HELP
Runing KK 4.4.2 on VIRGIN MOBILE/SPRINT NETWORK
aanddink said:
I have a SPH-L710 with a stock ROM and CWM root, I just tried to flash a boot animation and am now stuck in a boot loop. I did not make a backup before I tried this. I have wiped cache,div and did fact reset and can not get out of boot loop...................PLEASE HELP
Runing KK 4.4.2 on VIRGIN MOBILE/SPRINT NETWORK
Click to expand...
Click to collapse
You most likely will have to flash a stock rom using Odin on the computer.
The only problem with that is if you had to get your phone flashed to Virgin Mobile like I did with PagePlus, it may or may not erase those critical settings. I could never get a clear answer on that, but it is best to play it safe and assume it will. However, your phone should be functioning once again.You will however have to re-root the phone, and might as well install TWRP. All of this can be done through Odin.
Alternatively, if you have a custom recovery installed and a rom or two on your sdcard, you could try to flash the rom instead of going all the way back to stock. That would help ensure your carrier settings arent wiped related to Virgin, as it could if you were to flash back to stock.
Then for the love of god, devil, or whoever you believe in... make a backup once you are fixed and back up and running!! They are perfect and extremely helpful for situations like this.
Rawb0Ss said:
You most likely will have to flash a stock rom using Odin on the computer.
The only problem with that is if you had to get your phone flashed to Virgin Mobile like I did with PagePlus, it may or may not erase those critical settings. I could never get a clear answer on that, but it is best to play it safe and assume it will. However, your phone should be functioning once
again.You will however have to re-root the phone, and might as well install TWRP. All of this can be done through Odin.
Alternatively, if you have a custom recovery installed and a rom or two on your sdcard, you could try to flash the rom instead of going all the way back to stock. That would help ensure your carrier settings arent wiped related to Virgin, as it could if you were to flash back to stock.
Then for the love of god, devil, or whoever you believe in... make a backup once you are fixed and back up and running!! They are perfect and extremely helpful for situations like this.
Click to expand...
Click to collapse
Thank you for the reply and thank you for the help. i did get it to un-bootloop, i unfortunately did not have a rom backup, now i have a full backup zip using CMW on my sd card which i hope would fix this in the future. nothin worked until i found a good boot animation, i should have look for more firat but.once i re-flashed the 3rd one it booted.
aanddink said:
Thank you for the reply and thank you for the help. i did get it to un-bootloop, i unfortunately did not have a rom backup, now i have a full backup zip using CMW on my sd card which i hope would fix this in the future. nothin worked until i found a good boot animation, i should have look for more firat but.once i re-flashed the 3rd one it booted.
Click to expand...
Click to collapse
You have to have the proper boot animation binaries before you go flashing boot animation. Those zips are for flashing in custom roms that already have the proper binaries.