Hey guys, I have always jumped from ROM to ROM and its been great. I use alot of CWM backups, and usually don't have too many snags. Well I recently wanted to try the Jellybean port. I did a CWM backup, and then wiped everything and flashed. Jellybean was fun for 5 minutes obviously because it is quite glitchy. Now i cannot revert to my original backup.
I had a backup image if CyanogenMod 9 which bootloops and I had a backup image of MIUIv4 by 360 Productions which also bootloops.
Before i restored from backup i made sure to wipe everything (/data, /system, /cache dalvik and everything else). I even installed Cyanogenmod 9, let it boot into the ROM, then rebooted into recovery and tried to restore on that. I tried multiple combinations of flashing kernels on-top of the backup, and nothing fixes the bootloop issue.
What am I doing wrong? Should I scrap these backups and just start fresh ?
That's odd, you may give Odin a shot then install and boot fresh ICS. Then give your backups another try.
Vibrant MiuiV4 360° Productions
jrongi1 said:
That's odd, you may give Odin a shot then install and boot fresh ICS. Then give your backups another try.
Vibrant MiuiV4 360° Productions
Click to expand...
Click to collapse
I tried that - I ended up just pulling my accounts.db, apps and data, and other stuff out of my backup image - faster than starting from scratch...
imilleson said:
I tried that - I ended up just pulling my accounts.db, apps and data, and other stuff out of my backup image - faster than starting from scratch...
Click to expand...
Click to collapse
Glad you got going again.
Vibrant MiuiV4 360° Productions
Related
Hello guys!
Today i installed ClockworkMod Touch recovery and installed SuperNexus 2.0 Build 4 Rom , the whole process took less than 5 minutes. But before i installed SuperNexus i did a "Nandroid?" backup which went fine and took lots of space xD Anyway i proceeded with SuperNexus and it installed fine and played with the rom for a few hours ... i decided to restore the backup so my whatsapp and all that stuff comes back .. i didnt know that it'll restore system too! Ofcourse the phone went on a bootloop so i went to CWM and wiped data/factory reset and the phone booted with Stock 4.1.2 and the phone is kinda slow at the first boot ... now i dont really know what to do :/ The nandroid backup is large and im afraid the SuperNexus rom wont fit and it'll cause errors n all xD Im really stuck at this point , should i repeat installing SuperNexus?
EDIT: I cleared 4.6GB of space , what to do next?
the backup restore shouldn't have caused a bootloop, that's weird.
it restores everything - system and data. so if you want to keep the data when switching ROMs, use Titanium backup or something if the sort. try restoring again. if it fails, try a custom restore of /data
Glebun said:
the backup restore shouldn't have caused a bootloop, that's weird.
it restores everything - system and data. so if you want to keep the data when switching ROMs, use Titanium backup or something if the sort. try restoring again. if it fails, try a custom restore of /data
Click to expand...
Click to collapse
Im not sure if its a bootloop , it keeps restarting boot animation after 1min , i fixed it anyway by wipe data/factory reset option thru recovery and its on stock now booting fine , Shall i flash SuperNexus again normally ? Other than wipe data/factory reset is there anything else to do ?
I mean, if you don't care about your data being lost - then sure
Yeah no probs , contacts on sim and pic's and movies on sd card , Ill just have to redownload my games and all Ill charge my phone then proceed , thanks One more question. Since I installed SuperNexus before does it have system files that I need to delete? Or wipe data/factory reset will cover it?
Sent from my GT-I9300 using xda app-developers app
no, a data wipe will do.
Success Thanks for the help xD I learned a lesson Ill use titanium backup from now on
Hello, I use Rootbox 4.2 with Dorimanx 9.43 (october). After a reboot i had a crazy issue i never had before : first the rom didn't boot, i was stuck on kernel logo. Since wiping caches didn't help, first thing to do is to backup, so i did and it ended (successfully) but in only 30sec..!
So i plugged USB and checked the backup folder and saw there was barely any data there..! So i thought it's wiped.. I tried reinstalling the rom (which means stock kernel instead dorimanx) without wiping, still no boot but trying backup again, it's doing the backup fully!!
However since space was missing, it failed.. So i had to reinstall Dorimanx, mount USB, make space, reinstall rom, reboot recovery and do back up again (currently on process). I'm wondering if there's an issue with the internal memory, if so i shoud delete all and send back.I would NEVER send back an Android for warranty if my data wasn't wiped before, your life's inside of it!
--STILL EDITING/ADDING INFO//PRESS F5 AND SOMETHING NEW MAY APPEAR---
LOOKING AT THE BACKUP FOLDER, I SEE BOOT.IMG IS 0MB! What does it means..?!
goja said:
Hello, I use Rootbox 4.2 with Dorimanx 9.43 (october). After a reboot i had a crazy issue i never had before : first the rom didn't boot, i was stuck on kernel logo. Since wiping caches didn't help, first thing to do is to backup, so i did and it ended (successfully) but in only 30sec..!
So i plugged USB and checked the backup folder and saw there was barely any data there..! So i thought it's wiped.. I tried reinstalling the rom (which means stock kernel instead dorimanx) without wiping, still no boot but trying backup again, it's doing the backup fully!!
However since space was missing, it failed.. So i had to reinstall Dorimanx, mount USB, make space, reinstall rom, reboot recovery and do back up again (currently on process). I'm wondering if there's an issue with the internal memory, if so i shoud delete all and send back.I would NEVER send back an Android for warranty if my data wasn't wiped before, your life's inside of it!
--STILL EDITING/ADDING INFO//PRESS F5 AND SOMETHING NEW MAY APPEAR---
LOOKING AT THE BACKUP FOLDER, I SEE BOOT.IMG IS 0MB! What does it means..?!
Click to expand...
Click to collapse
Wipe EVERYTHING from your phone, delete all folders and stuff, then install an Oficial Rom and after that put your Rom again. Can be a Rom, kernel or flash error...
I took a backup of android policy and services jar file before flashing. When I tried to flash the backup after bot loop I'm still stuck. Tried to flash crt off effect on MIUI. Now my device is ruined
It seems the backup applied but it's not working
Falenone said:
I took a backup of android policy and services jar file before flashing. When I tried to flash the backup after bot loop I'm still stuck. Tried to flash crt off effect on MIUI. Now my device is ruined
It seems the backup applied but it's not working
Click to expand...
Click to collapse
Have you wiped cache and dalvik-cache?
Christiaan91 said:
Have you wiped cache and dalvik-cache?
Click to expand...
Click to collapse
Yeah I did. I gave up. Took a full backup of my system to get app settings n stuff back and re-installed ROM.
Moral of the story. Take a FULL freakin' backup before flashing those nasty jar files.
you said device is ruined. is it had bricked?
What exactly is going on? that what i understand you have bootloop even after flashing new rom
i had similar problem before when i had boot stuck after flash new android it was the same
boot stuck new JB boot stuck new JB boot stuck all over again. I flashed ISC and worked out
it was long boot up first time but started up. Maybe you need different rom to start up and later you
can flash that what you like
I know it is confusing but may this help you
Would there be a reason I can't restore CM12.1 - d2vzw? I can restore my previous non-CM roms. I'm using CWM 6.0.4.5 and I've tried wiping data, cache and dalvik, then restoring my backup. I tried to restore the 1st nightly, but it rebooted into recovery.I reinstalled the zip from scratch and have updated till today.Today I booted up into official nightly from May 17th, 1st install went fine like before but when I tried to check if I could restore with the new nightly. Still no go. The Samsung logo comes on, stays on 30 sec. then reboots into CWM Recovery again. I can restore back to a former rom of a different maker. Any suggestions?
Thanks, Tom
tshuford said:
Would there be a reason I can't restore CM12.1 - d2vzw? I can restore my previous non-CM roms. I'm using CWM 6.0.4.5 and I've tried wiping data, cache and dalvik, then restoring my backup. I tried to restore the 1st nightly, but it rebooted into recovery.I reinstalled the zip from scratch and have updated till today.Today I booted up into official nightly from May 17th, 1st install went fine like before but when I tried to check if I could restore with the new nightly. Still no go. The Samsung logo comes on, stays on 30 sec. then reboots into CWM Recovery again. I can restore back to a former rom of a different maker. Any suggestions?
Thanks, Tom
Click to expand...
Click to collapse
I've had some issues before regarding actions within the CWM on my d2vzw. I got rid of CWM and installed TWRP 3.0.2-0. I was then able to do much more.
I had also read somewhere that CWM is an abandoned project and TWRP is kept current and is also recommended by Cyanogenmod for all their ROM's and other flashable files.
The link for the d2vzw TWRP is https://dl.twrp.me/d2vzw/
Good luck!
I seem to have shot myself in the foot recently. I've been on CM 13 for nearly a year now and I wanted to try out LineageOS for the hell of it since I am planning to get a new phone and I wanted to put LineageOS on that as well. So I downloaded an unofficial build of LineageOS for the G850W and followed some basic instructions: backup with TWRP, wipe with TWRP, and flash both the ROM and OpenGApps with TWRP. All three of these went well and I was able to install LineageOS. Now the problem: I tried restoring my backup (a CM 13 based backup) thinking I could restore some things from that backup and when I went to restart the CM boot screen popped up and I immediately knew I must have messed up. Checking my backup it contained boot, cache, system, EFS, modem, and a couple other folders/partitions that I can't remember off the top of my head. I then simply tried to redo everything again: backup, wipe, flash. While I am able to backup, wipe, and flash, and I am able to proceed past my device's boot screen, the Lineage OS boot screen seems to either be stuck or it is taking a long time. I've waited for 30 minutes with no change and I am sure that shouldn't be the case at all. Stock ROM was the same way, sitting on the Samsung logo with the sparkles forever. I managed to reinstall CM 13 but it's a very buggy install as sometimes it restarts randomly and goes through the "preparing applications" thing upon restart. Furthermore data doesn't seem to work and IMEI info is not found and sometimes in the stock recovery mode it shows that the EFS partition could not be found. Same thing happens when I poke around in ADB, I do not see any EFS partition when I type in the mount command. Clearly I've really messed things up. So would there be some way to fix things considering I do have a backup of things before I messed things up? How would I use my backup to fix everything? Would there be other tools I should be trying? Any help would be appreciated.
Flash original firmware
echo124 said:
Flash original firmware
Click to expand...
Click to collapse
I did: "Stock ROM was the same way, sitting on the Samsung logo with the sparkles forever".
Erase everything on your phone (aftet backup) and flash stock again.
echo124 said:
Erase everything on your phone (aftet backup) and flash stock again.
Click to expand...
Click to collapse
I've done that as well already, still the same issue.
:fingers-crossed:Flash stock, flash same version twrp used to backup, flash same version of cm 13 used on backup, try restore.