I want to upgrade my ROM, especially the Radio ROM. But I am a little nervous, as I feel that this is an operation into the deep and decisive structures of my Jasjar.
I am using the excellent backup program Spb backup.
My question is:
If anything goes wrong when I try to update the ROM, will I still be able to retrieve the old version with Spb backup? Or will the new ROM be so deeply entrenched in the Jasjar that I will be unable to return to the old version?
Thankful for answer from someone who knows.
i saved the same software to sd card and found after ROM change i was able to roll back
I haven't actually tried it my self but sprite backup has little tool that you can use to recover a backup across a ROM upgrade. You do the backup as normal, hardreset the phone and run the program to let spritebackup know what the clean OS looks like, then do your upgrade and restore the backup, but point it at the file produced upgrade tool. When I upgraded there were a few things I didn't want to carry across into the upgraded phone, so I just backed up my contacts and reinstalled any programs I wanted after the upgrade.
just started and upgrde, the unit died, i tried to install the old O2 Rom but the exec stays in boot mode with a funny screen, any help please?
lion
I know there is similars topics, but I want to describe my problem as somebody may have an answer for me.
I have tried many times installing WP7. WM (official) was working well, some WM custom roms bugged sometime.
I tried to install WP7, first flashing the ROM, there everything is OK.
If I have a SDcard, and if I reboot the phone, the phone starts, then when it gets to the start screen it freezes after 1 second (and the contact tile is still working for few seconds)
If I don't have a SDCard, the phone works well. But I can't use it with Zune, because it says it is a test phone or it is not well connected.
So as I saw there may be driver issues with the SDcard, I have tried the CAB method update.
I can install the 7403 version without problem, but I can't install the 7661 version without plugging the SDcard, because it says I don't have enough storage.
* 1st question: How do I know if the 500M storage capacity is unlocked?
Ok, so I have put the SDCard, done a hard reset from settings and launched the 2nd set of update to 7661 (why? just to be sure everything goes well... As it does not work all the time, I prefer to go step by step instead of going straight to 7720).
The update is OK, but now I can't go to 7720 anymore, because it says my storage is full (the card is recognized in settings, so I have 7Go available)
Ok, I restart the phone... Frozen again after booting.
It is really strange because the system is still working (some animations, the battery hiding, ...) but it becomes unresponsive.
Sometimes when I restart it doesn't freeze, but I don't know why or when it does.
Do you have any idea about what can I do?
I have tried 2 sdcards sandisk 8 and 16GB, it is EXACTLY the same. So it is probably more a problem coming either from the phone (card reader??) or the way I install (I cannot format the SD anymore because it is undetected under win, I don't have any nokia with sdcard phones, and don't have any linux installed, nor CD reader, so I haven't tried killdisk
I bought my phone in december 2009, 1 or 2 months after its release, so it is getting old, but I would prefer to keep it for at least 4 more months!
The last 2 months have been a real pain so I am really looking for a solution!
Hehe, after many many many tries, I finally got my fresh Mango!!
Everything is working well, with the same hardware, same sdcard, don't understand why but it works!
I have set all accounts possibles to be sure this time it won't bug. It seems to work!
I just have to send 1Gig of MP3 to be sure, take few more picture, and it should be ok!
So gooooooood
Anyway, Mango is much much better than initial WP7! Almost everything missing in WP7 is in 7.5!
What did I do? hum... Nothing special, just many times the same thing:
flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing, flashing
then...
flashing WM6.5 ROM (with SD)
flashing magldr
flashing Radio (or maybe not??)
flashing WP7 (with SD)
flashing deviceprovisioning
setting time
flashing to 7392
RESET because lack of space? or maybe it was the time before?
flashing to 7720
reset
playing with the phone
being happy and relaxed
I am playing alone here, but if someone comes:
Everything works, everything BUT zune...
I cannot connect my device to Zune, it is not recognized I don't know why, it has never been (maybe once, but long time ago, many flashes since!)
So if somebody knows what could be wrong... (my device time is set right, same as my computer)
"Can't connect to your phone. Disconnect it, restart it, then try connecting again"... always.
I got a "your phone is synced, disconnect to see the content" because i was on the marketplace, but nothing on the computer!
If I can't get it working, is there a way to send MP3s to it without Zune?
Well I see you got the problem solved, but just I case others come across the same issue, you remove the SD card before going to WP7 and update as far as U can with Zune, then update as far as U can with cabs. I think update 7463 requires an SD card so format it using windows and insert it and continue updating. From my understanding, it is something to do with the way WP7 treats SD cards and locks them and at some point its like the SD card gets forgotten so when U try to update, the card is locked so cannot be used. Look at xboxmod/yuki updatable wp7 v2 and there is also a cab to unlock the SD card as well as update cabs and some other useful stuff. There is a very good install guide. Oh and FYI, there is also a 1 shot update to go from 7004 to 7720 mango RTM. Takes about an hour to do but much easier.
Thanks, but... Being able to use mango, I won't flash anymore, it has been too painful to reach that!!
I have never been able to update with Zune, because it has never been recognized well. I have been able to update with cabs, hoping that would resolve itself with updates, but still have the same pb, can't connect to Zune...
My plan is to upload photos using skydrive, and put MP3 via... another way, I just have to find it!
Hi,
i want to install Android in NAND. But at the Moment i have WP7.5... And after i tested the Android ROMs i want my WP7.5 back- with als my Data. But how can I make a Backup thats works? Last time i tried this, I wasn´t able to restore it (after reinstalling WP7.5), it Wanted to reboot and nothing... I think it was because of the aMagloader...
Will a Backup with the WP7 Update Cab Sender work? Or is it possible to make a complete NAND image?
no...
use WPDM for backup...
Doesn´t work.. Allway say an Error occoured .
I have the same issue, not sure how to backup for testing other ROM and not having to set everything up again. I tried using Windows Phone Connector for Mac, it makes a backup but the 3 times I have tried it throws an error and does not restore...
Hey guys I flashed my Omnia 7 to the latest 7.8 ROM that just came out, but had some stability issues and decided to go back to Tango, so I flashed it back to a factory Optus (my carrier) ROM and updated accordingly back to Tango.
I made a backup using WP7 easy backup before I did all of this and was wondering if there's a way to restore the phone to it. I've tried doing it via Zune but it just fails giving me error 801812E0.
Cheers
Problem I am trying to solve: As soon as the device boots I get the notification "preparing network" and when I try to dial a number on the stock ROM and get "Mobile Network not available"
A Nandroid restore CM11 appears to connect to the mobile network (I can dial a number but get "your account could not be validated" because the device has not been successfully activated on the network yet)
Here is how I arrived at such a dilemma.
okay, I am gonna try to format this in a way where you can skip some sections that might be a little "ranty" while still making it informational while still requesting some assistance.
A little background (feel free to skip this part) I have been rooting and ROMing phones for a few years to support my Cyanogenmod fix. I buy my phones on eBay or Craigslist, and verify I can setup a recovery, then backup the rooted Stock ROM (to activate the device and update PRL, etc.) then install the CM version of my desire and transfer over all my settings and backup files and restore them so I have had the same look and feel for the operating system of my phone for the last few years. I am on TIng (a Sprint MVNO) and have had zero problems performing these hardware upgrades from my droid, to my galaxy nexus to my second galaxy nexus, to my galaxy S3 to my second Galaxy S3 on a regular basis using their website.
Last Friday, I picked up a Galaxy S4 (running NAE) at the local Sprint store and once verified by the Sprint employee as being a clean ESN, I was set to start my process of rooting, installing recovery (I chose TWRP), then Nandroid backup of the stock ROM, then install CM 11 M6 and copy over my backup files (Titanium Backup) from my S3 and restore them, then Nandroid backup of the CM 11 install, then restore of Stock NAE ROM to activate the phone. Here is where things get a little fishy.
For awhile now, I had been always used Clockwork in the past but several comparisons score TWRP a little higher for features and functionality so I decided to use that for my recovery. It installed CM just fine and it seemed to perform Nandroid backups without any problems (or so I thought). I attempted to restore my Nandroid Stock ROM to activate the device and upon boot I saw the familiar Cyanogenmod screen. I tried it again, but same thing. No big deal, I'll find a stock rooted NAE ROM, copy it to the SD card, install using TWRP, activate, Nandroid backup, then restore my CM Nandroid backup and be up and running. I installed the Stock Rooted NAE ROM using Odin and lose my TWRP recovery so I reinstall TWRP and make a Nandroid backup of the Stock Rooted NAE ROM using TWRP. I make sure my TWRP restore can restore my CM11 Nandroid backup and it does. Okay, I should be all set. I have a nandroid backup of stock and CM11. All I need to do is restore stock, activate and I am up. I attempted to restore my Nandroid Stock ROM backup to activate the device and upon boot I saw the familiar Cyanogenmod screen for the second time. At this point, I am a little frazzled as logically this has never happened in the history of all the devices I have worked with.
I start checking the forums to see if anyone has experienced this and see nothing. I see many "how-to" guides that cover all kinds of things for the Spring GS4 that include wiping the data and cache multiple times over and over using a recovery called PHILZ.
I abandon TWRP, restore Stock Rooted NAE ROM and as far as I can tell, I am ready to begin from scratch using PHILZ. Install PHILZ recovery, install CM 11 M6 and copy over my backup files (Titanium Backup) from my S3 and restore them, then Nandroid backup of the CM 11 install, then restore of Stock NAE ROM to activate the phone. This time I am able to successfully restore a Nandroid backup of Stock rooted ROM but I am seeing a little red x and zero bars for the mobile network connectivity.
I start checking the forums to see if anyone has experienced this and see a few people that have lost mobile network connectivity and claim loading a modem using Odin is the fix. I try NAE-Modem-Only.tar using Odin and that does not improve anything. I also try loading TriForceROM5.4 having read that any TW ROM can be used to access the menu to activate a device
Now I am stuck.
There is nothing I can do to get mobile network to work on a stock ROM. As soon as the device boots I get the notification "preparing network" and when I try to dial a number on the stock ROM and get "Mobile Network not available"
A Nandroid restore CM11 appears to connect to the mobile network (I can dial a number but get "your account could not be validated" because the device has not been successfully activated on the network yet).
this issue is resolved.
I followed the steps to "unroot / unbrick" my phone using multiple stock ROMS and finally, the stock ROM L720VPUFNAE_L720SPTFNAE_SPR performed a full reset on my device (all partitions). I wish I remembered the page that linked me to the download of that ROM but googling that name should provide you a few places to get it.
not sure if that helps anyone else but my appreciation to QBKING77 for his multiple "How-To" videos.