As i do not want to flash a .tot and start over rooting
I need them to make Zv9 themes for B.o 1.1 and newer roms
Lost my backups (Hard drive Fail) and the ones i have wont compile due to the swiss cheesey like nature of em.
Related
how do i unroot from cynanogen 4.2.17 back to 1.6 without haveing to resign in? i dont have data on my phone and and how do i do this with doing a full wipe. thanks
The only way to completely unroot is to flash NBH wich will wipe your phone and you will have to resign. Non-rooted users don't have the luxury of running the phone without signing in. May I ask, what are you trying to accomplish?
im having some texting problems with cyan, so i have to go back to rc29 and sign in with the hack and then to 1.5 and 1.6?
any easier way?
my question is where did you get 4.2.17 considering development on CM-4 stopped at 4.2.15.1? my recommendation would be to get off of a version that doesnt exist and upgrade to CM-5.
my bad wrote the wrong version, is cm-5 still haveing problems?
nahanee20 said:
im having some texting problems with cyan, so i have to go back to rc29 and sign in with the hack and then to 1.5 and 1.6?
Click to expand...
Click to collapse
Also what are the texting problems? Maybe there is a fix.. or just wiping + erasing your ext partition.
Otherwise I think (but have never tried) you can install rc29 + manually apply the two ota updates and be at a version of android where you can skip the login and login when using wifi. If you do this for non warentee reasons however I strongly recommend never rooting your phone again.
(OK I also give exceptions to developers that require to test something in a particular android build.. but they probably want to use and keep a engineering spl)
Have you considered going to stock adp1 firmwares they have the img file that if you unzip and flash userdata/cache/system/boot images via fastboot will put you on that rom without loosing your current bootloader or custom recovery? requires an engineering spl. (I support using custom Tom's after this process as well)
Hey guys -
I'm a recent convert to Milestone (owned horrible WM devices over the years before just recently switching to Android). Love this community and hope it continues to grow!
A couple of quick questions:
1.) I have a rooted Telus Milestone but want to apply the latest Telus update (I believe it was released Aug. 10th). Now, I've tried doing this OTA but no luck because I'm rooted apparently (I believe I can sill do it via cable)... but if I CAN do this successfully, will I lose root?
2.) If I can't apply the update without un-rooting my phone first, I suppose that this would be my process. Can you tell me if this will work?
1. Make a nandroid backup
2. Un-root the phone
3. Apply the firmware update
4. Root the phone
5. Restore my nandroid backup.
... BUT here's my fear: I'll be restoring my nandroid backup overtop of a different OS / build... and isn't that a recipe for disaster? (I could never do this with WM devices, anyway).
Can anyone tell me if this process will work? Having a hard time finding answers here.
Really appreciate it. Thanks!
-Trevor : )
Trevor_g said:
Hey guys -
I'm a recent convert to Milestone (owned horrible WM devices over the years before just recently switching to Android). Love this community and hope it continues to grow!
A couple of quick questions:
1.) I have a rooted Telus Milestone but want to apply the latest Telus update (I believe it was released Aug. 10th). Now, I've tried doing this OTA but no luck because I'm rooted apparently (I believe I can sill do it via cable)... but if I CAN do this successfully, will I lose root?
2.) If I can't apply the update without un-rooting my phone first, I suppose that this would be my process. Can you tell me if this will work?
1. Make a nandroid backup
2. Un-root the phone
3. Apply the firmware update
4. Root the phone
5. Restore my nandroid backup.
... BUT here's my fear: I'll be restoring my nandroid backup overtop of a different OS / build... and isn't that a recipe for disaster? (I could never do this with WM devices, anyway).
Can anyone tell me if this process will work? Having a hard time finding answers here.
Really appreciate it. Thanks!
-Trevor : )
Click to expand...
Click to collapse
When you restore the nandroid backup you'll be back where you were before on the old version of 2.1.
You can get the update by flashing the newest Telus service SBF from here:
http://and-developers.com/sbf:milestone
(scroll way down to the end)
If you need to then root again you'll want to reflash the vulnerable recovery SBF from:
http://android.doshaska.net/rootable
and then apply any of the various update.zip methods for root.
Also you could go for the G.O.T. leaked version of the exact same firmware update:
http://groupoften.wordpress.com/2010/07/07/update-for-france-and-telus-released/
which skips the need to reflash the vulnerable recovery SBF. Then proceed again with a root update.zip.
I might also recommend taking a full Titanium backup before the upgrade in addition to nandroid. If any of the root mods you've made are incompatible with flashing the update via SBF, it'll give you another way to restore your data on the new OS update.
I've never installed a theme on my Nexus yet but I have on my older Motorola Cliq, and I can't exactly remember the process of reverting back to stock without a nandroid...
so 2 questions
If I go the MetaMorph way, how do I go back to stock?
same thing goes for flashing an update.zip btw.
I'm on CM6 stable
Stock morph that pushes the stock files.
Same goes for update.zip.
Since both have a high likelihood of not being in existence, you'll be better off with nandroid.
Thank you. Can I somehow back up those files before the flash?
If you know exactly what files you're morphing (by looking at the morph and checking which files it modifies) - yes, you can back them up using ADB.
So in my attempts to undo unbrick my bionic i was able to get back on the path and got into a rooted 901 version YEAH.
Problem is my webtop version is WT 1.3.0-105_DBN-1 which is not the current version. Does anyone have a way to get an updated grfs version onto the phone or a process that works coming from 901?
The problem as I see it, is that you aren't really on 5.9.901 because you couldnt have updated with the leaked update.zip without having all of the signed components from 5.5.893 including the webtop partition. You must be using a ROM that updated only your system and nothing else.
The solution is to use the full 5.5.893 xml.zip released recently and flash it with RSD Lite and it will put you back on the path with all the stock images.
If you wanted to only flash the grfs.img from that file then you need to use the moto-fastboot.exe instead of the fastboot.exe because it is modified to handle larger than 256MB images.
It is difficult to tell where you really are with all of your firmware components and whether just flashing the webtop will do you any good. That is why i recommend the full xml.zip and RSD Lite.
This is the method that a technician would use to fix a returned device to stock and is what the file is designed to do. Its like an SBF file but uses the fastboot interface instead of the old flash interface.
We have all the tools we need to recover virtually all problem flashes at this point, and its up to everyone who is modding these devices to understand the options before you flash any ROMs so you dont find yourself returning a device that you destroyed to VZW for warranty replacement, a practice all to common unfortunately.
I recently rooted my LG Thrill (US AT&T) and installed CM7 on it. I didn't backup the original image. The CM7 image had major issues with echo, and not receiving calls. I managed to get back to the stock image after a lot of varied attempts - documenting my experience here in case someone else is facing the same problem.
1. Install the stock, rooted gingerbread image from acidhazard's site. Cannot post links - our firewall doesn't allow access to the site. This image cannot be used because the fonts are totally messed up, though the calls seem to be fine.
2. Follow AT&T and LG's instructions on upgrading to ICS using LG's support tool (this did not work unless the phone had a stock image). Make sure you remove the external SD card.
That's about it. Since the support tool was able to talk to the process on the stock, rooted image the upgrade succeeded. I won't document the various attempts I made to directly flash the kdz file directly - suffice to say, they didn't work.
I lost root after upgrading to the stock ICS - I might try to regain that just to remove AT&T's default installed apps which are just a waste of space and memory. But I'll do a lot more research before that