Hello,
I would like to create a full stock backup, I do not care for applications or settings, the only thing I want is full non-rooter, current Gingerbread with ability to install possible upcoming OTA updates.
The reason for this is simple, I want to try out different ICS roms just for fun and then go back to original, HTC Sense 2.1 powered rom.
The question is: How do I do that? I know I can handle rooting the device and installing various things but how do I get back?
Thanks!
PS A link with instructions on how to do that would be nice, I tried searching the forums and Google but nothing legit came out.
If you have already rooted your phone and installed a recovery such as ClockworkMod or 4EXT, reboot into recovery and go to the "Backup" menu and make a full backup.
In the event of problems, you can do a full wipe or factory reset, and then go to the same backup/restore menu to restore your backup from the SD card.
But if the phone is Gingerbread (it is) I have to downgrade first, correct? To Froyo 2.2. So Basically that leaves me with a copy of 2.2 while my phone came with Gingerbread in the first place.
It basically shows that I've changed (downgraded) the software, doesn't it?
stranded.eu said:
But if the phone is Gingerbread (it is) I have to downgrade first, correct? To Froyo 2.2. So Basically that leaves me with a copy of 2.2 while my phone came with Gingerbread in the first place.
It basically shows that I've changed (downgraded) the software, doesn't it?
Click to expand...
Click to collapse
If you have ALREADY rooted it, then there is no need to be downgrading back to an exploitable firmware when you've already exploited the phone. If all you're doing is installing a custom rom on an already rooted/unlocked phone then you need only flash the roms via recovery.
You would only have to downgrade the firmware if you for some reason decided to flash the original stock firmware, hboot, etc onto the phone.
But that's least as far as the backups go.
In terms of how to get the phone back to non-root/locked state there's a sticky/wiki for that, though I would find it to be a pain in the butt to have the phone rooted and unlocked and then have to go thru the process of locking it back up only to possibly risk bricking it. The more times you mess with the firmware/radio/hboot the more likely you are to brick it.
Just to make it all clear my phone is kinda new, was never rooted, that's why I'm asking. I still can't believe that HTC doesn't have an app like Xperia has, SEUS to be exact, you can fix any phone with one click. By saying fix I mean install the latest, official rom.
That's too bad there is no other way to root Desire Z.
stranded.eu said:
Just to make it all clear my phone is kinda new, was never rooted, that's why I'm asking. I still can't believe that HTC doesn't have an app like Xperia has, SEUS to be exact, you can fix any phone with one click. By saying fix I mean install the latest, official rom.
Click to expand...
Click to collapse
If never rooted there's not much of a way to make a full backup first (since most backup tools like Titanium Backup requires root).
That's too bad there is no other way to root Desire Z.
Click to expand...
Click to collapse
Well there is the HTCDev unlocker from HTC themselves, but you actually have better luck following something like cyanogenmod's wiki entry.
Something like this works quite well : http://wiki.cyanogenmod.com/wiki/HTC_Vision
You just need to make sure to triple-check all the numbers and messages, someone accidentally skipping 2 or 3 steps multiple times is just asking for problems.
But once rooted (like for my G2 I followed the cyanogenmod steps, and then went another step by upgrading my radio to the latest, I just went with a different rom after being rooted) it's usually best to keep it that way even if you decide to just flash the stock rom (i.e.: still rooted and unlocked, but simply using the original software they provide you, which can be rooted simply by having the su binary and superuser app).
The voiding of warranty usually applies to software, i.e.: you bricked the phone as a result of flashing the wrong hboot. Where as if the screen or eMMC dies, it's a hardware failure and shouldn't be voided simply because the phone was rooted (unless of course they determined you fried your CPU by running the phone at 1.9Ghz constantly).
You could just download a full version of the G2 gingerbread rom from shipped-roms.com and flash that if you ever want/need to go back to stock gingerbread.
-Nipqer
Related
this is my second thread about this issue, and PLEASE don't answer if you don't know how i could do this. i DON'T want a rooted/modded whatsoever 2.2, just the update that came today.
i guess my best bet would be flashing a htc europe generic rom and get the OTA, but how do i do that?
If your phone is from a network provider then it will more than likely need rooting even if you just want to flash it with a generic HTC ROM.
If it was purchased SIM free then it should already have a generic ROM and it will just be a matter of time before you get the OTA update.
Have you tried manually chacking for an update on the phone?
maxupp said:
this is my second thread about this issue, and PLEASE don't answer if you don't know how i could do this. i DON'T want a rooted/modded whatsoever 2.2, just the update that came today.
i guess my best bet would be flashing a htc europe generic rom and get the OTA, but how do i do that?
Click to expand...
Click to collapse
Here's how
I'm Rooted and I still want the official update after reading the warning.
1) Make a goldcard using this guide (For Desire too)
2) Download this
3) Double click it and follow the instructions.
4) When the update is ready to be pushed out, you will get a notification.
(taken from the Official foyo update thread....please search or read before making threads like this)
Also consider looking at this
http://android.modaco.com/content/htc-desire-desire-modaco-com/307683/howto-unroot-your-htc-desire/
BTW, if you do this you will not be able to unroot again untill a new root is found which could take weeks, or could never happen. You loose the ability to install custom roms, or non sense roms.
@ shetlander: it IS rooted, but i'm not able to flash generic, it simply doesn't work
@jedipottsy: i don't have a micro SD card available, but as i said, the phone IS rooted, so i there any way to do it without one? maybe a dump of a generic firmware instead of a ruu.exe?
edit: i forgot to mention, i had a leaked 2.2 build flashed before, but then flashed back to t-mobile rom. what doesn't work ist the flash to htc europe generic
maxupp said:
@ shetlander: it IS rooted, but i'm not able to flash generic, it simply doesn't work
@jedipottsy: i don't have a micro SD card available, but as i said, the phone IS rooted, so i there any way to do it without one? maybe a dump of a generic firmware instead of a ruu.exe?
Click to expand...
Click to collapse
nope, need an sdcard, can't flash an official over an unofficial, you need sd to restore to an older official.
Jedipottsy said:
nope, need an sdcard, can't flash an official over an unofficial, you need sd to restore to an older official.
Click to expand...
Click to collapse
well i was able to got to a defrost build and back to stock without goldcard, i don't see why a htc generic can't function (
cant see the advantage of using the official, you loose too much for little gain
http://forum.xda-developers.com/showthread.php?t=741663 or http://forum.xda-developers.com/showthread.php?t=741755
there is full 2.2 with extras, or plain with root, much easier to install and you dont loose root
thx jedi, i am actually flahshing the thingy with busybox(whatever that does), there's no way i'm gonna miss teeter ^^
maxupp said:
this is my second thread about this issue, and PLEASE don't answer if you don't know how i could do this. i DON'T want a rooted/modded whatsoever 2.2, just the update that came today.
i guess my best bet would be flashing a htc europe generic rom and get the OTA, but how do i do that?
Click to expand...
Click to collapse
Download this rom:
http://shipped-roms.com/shipped/Bra...00.28U_4.06.00.02_2_release_126984_signed.zip
change the name to PB99IMG and put it on your gold card, boot into recovery and select fastboot, it will install the generic 1.21 rom, then when you check for updates the froyo update will be there, btw doing this wipes everything on your phone. Worked for me although I didn't install the froyo update as I am scared of the bootloader.
Hi..
I recently rooted my Desire and tried some various ROMs, but chose to stay with the stock 2.1 untill 2.2 was released OTA.
Today I got the message that I could update OTA, but denied, since I thought I might lose my root and my superuser access.
My question is:
Should I update OTA, or find an official ROM here so I don't lose my root - If so, what ROM should I use?
Can I update without getting a wipe, of can I backup or something before I install 2.2 to not wipe everything?
Best regards, and keep up your great work
YOU SHOULD NOT OTA! as you put it. If you update via ota you will loose root and will be unable to root again. Just download one of these "official" rooted roms and flash via recovery/rom manager. No need to wipe. If the rom is as close to the official one you'll never know you changed roms. Everything will look the same. All your widgets and such will be there. No need to wipe. But if you do have problems you should wipe and reflash. Hope this helps. Have fun!
yeah, but the question is only answered half..
WHICH one of all of those "official" roms should one choose?
I am totally blown away of all the posts, everybody seems to have a froyo rom ready for the masses
Which one is the best?
(I would care for deodexed, old-app2sd, the rest as close to official as possible)
EDIT: I just found "Pinky Desire" by pinkolin. Is this the way to go? Am beeing a bit scared of him openly saying that this is his first, but it seems like this is the only deodexed ROM so far and the other facts look juicy too.. ..anyone?
well first I installed the rom posted by ieftm 'cos it's as close to the official one as possible. I'll just wait a few days until things settle down and then I'll look for another rom.
as far as I understood he added VPN and ext4 support to the rom - I don't know if this could cause anything.. but I think you're right with your other statement..
Just wait a few days until everything settles, should be fairly easy to switch to another ROM and maybe even transfer everything with Titanium Backup or so..
that's the reason I went for that rom. Everything he changed is harmless. No wipe no nothing. And I had everything back the same as before flashing so I didn't need titanium backup or any other backup app. Hm leeDroid lookin' pretty good tho'
Hi,
I've had my DHD for 6 months now, and I love it, but after seeing this thread...
http://forum.xda-developers.com/showthread.php?t=1056329
I've finally decided I want to get rid of the Vodafone crap on my phone. It takes way longer to boot than it should, I have stupid apps on there, and I'm generally sick of seeing the Vodafone symbol every time I boot my phone, especially as I bought the phone from them and am not even contracted to them.
Is there an easy way to rid myself of this Vodafone branded ROM? I know next to nothing about rooting or anything, however.
After seeing the link above, I realised that I'll probably be waiting ages for Vodafone to send the update OTA, and I would really like some Gingerbread around about now. Hopefully the process will speed up my phone.
But, is there anyway I can do this without losing everything on my phone? My messages, apps, settings?
A lot of questions there - thanks in advance.
Hi, you will lose everything you don't backup.
Apps will need to be reinstalled, and settings will be lost.
If your firmware version is greater than 1.3x.xxx.x then you will need to downgrade to 1.32
Follow THIS thread to downgrade.
Once downgraded simply download & run the RUU~.exe file and it will take care of the rest.
How could I backup my apps (and settings) and restore them once updated?
My 'software version' is 1.32.178.5
Looking at the link you provided, it says...
System requirements:
Desire HD with build number 1.72 or higher
My DHD's build number is 1.32.xxx.x... Do I...not have to downgrade? Or what?
Also, since I'm running on an Australian network (Virgin), will I need to incorporate that somehow into the software I put onto the phone or something..?
You can root your phone and use clockwork to remove data/cache to go back to factory settings
as for the virgin thing, just make sure your APNs are correct and you should be fine
So I could root it and use Clockwork and my phone would basically be like a standard Desire HD that I bought new, unbranded in a shop?
yeah but you will also lose all your contacts and messages etc
i think you can use titaniumbackup to save those kind of things .. but done quote me because ive never done this, ive only rooted and cleared then flashed a new rom on
actually look up a stock RUU guide
EDIT: Just Root your phone and flash a custom rom imo
I did it .. never going back
Hmm, okay.
What about if I wanted to put something on my phone like the link I posted up top, the 2.3 'release'?
well click the ROOTED link in my sig
and do all the steps with the exception of the flashing of the MIUI.zip ... just replace it with the custom rom of your choice and bobs your uncle
i advice to back up your apps and anything else you want to keep
Hey guys, I was thinking of installing cm7 on my motorola defy but the problem is that its a t-mobile uk version that has been unlocked using an unlock code. Right now I can use any sim with this phone but after installing cm7 will the phone lock itself back to t-mo? I don't have the unlock code for this phone so it would be really disastrous for me if it were to lock itself. should I be worried?
I found a tutorial here that un brands the motorola defy, does that mean the phone would be unlocked? My phone is currently running android 2.2.2 official uk build with baseband epu_93_00.59.02 kernel version 2.6.32.9 and build number jorem_u3_3.4.2_179-6.1.
Any help would be appreciated. Thanks!
Sent from my MB525 using XDA
Yes it should be safe.
I haven't done it myself, but here's why I say so:
1- during the process of updating to a custom rom, everyone should create a full nandroid backup of their current stock rom right after installing 2nd-Init. That way, if things don't work out with custom rom [or for warranty purposes] one can easily return to that original setup with a nand restore [and un-rooting];
2- there is a thread regarding sim unlocking the Defy here: http://forum.xda-developers.com/showthread.php?p=22227859 but I bet you will not even have to deal with it...But if you do, it's there for you and you'll find help from others users I'm sure.
Don't waste anymore time and give a shot at CM7; I'm sure that you'll never go back to stock rom afterwards ;-)
Cheers
Ok one last question. My baseband is greater than the version listed on that thread. It is .02 and I have heard that downgrading your baseband is usually not safe?
Sent from my MB525 using XDA
that shouldn't be a problem either.
In fact, Maniac103 just recently changed the way we set baseband on cm7; no more dedicated apk.. it's now all done through Device Settings.
If you're still worried [and To be on the safe side, in addition the the nand backup before installing a custom rom], also make a copy of this whole folder (current radio files) from your stock rom:
system/etc/motorola/bp_mvn_default
so that you can revert to them (make a flashable zip w them) if needed.
Anyhow, no big risk involved if you do it that way.
Good luck and have fun.
Thank You for your help!
as far as I know unlock is retained no matter what rom u are on...
not 100% sure...
let us know how this works out...
Sent from my MB526 using xda premium
SBFs on Motorola Defy
I read the Motorola Defy beginners guide but I don't understand some stuff. I am already on the latest SBF deployed by T-Mobile UK i.e JOREM_U3_3.4.2_179-6.1 as shown in settings Build Number. When we install Custom ROMs lets say CM7, do these ROMs change the SBF? If yes, then how do I know if it is a Fixed SBF or a Full SBF? If I want to come back to the official build of which I would be making a backup in case I need to get warranty (I still have 6 months of warranty) then do I need to again install the Full SBF taken from the link Zephyrot posted?
If CM7 does not modify or change the SBF then I think I would be pretty much safe in just restoring the official 2.2.2 froyo build without worrying much about SBFs, unroot the phone using SuperOneClick and taking it back to the service center. Right?
And lastly I have the SOC Defy, checked it using CatLog. Does the stable build downloaded from the CynaogenMod website of CM7 work OOB? Zephyrot suggested that sometimes you need to do additional stuff for everything to work correctly.
To go back to stock state, there are two options: 1) you restore a nand backup and like you said, you have to remove SU and unroot. This ain't so easy to do, but is sometimes the only option for people not having their stock sbf available. 2) access STOCK recovery and wipe everything and then flash their stock sbf.
Once rooted and 2nd init installed, I still recommend to create a nand backup of your stock/current state before using a custom rom anyway.
Could be useful if you ever need to go back (outside warranty) to stock rom with all your apps still installed...
Sbf is stock firmware; custom rom replace and build upon that software. I think you meant kernel? But anyhow, I suggest you to first go with ghe latest Maniac103 latest build as it includes boot.img and devtree; no need for anything else and it is rock solid and lightning fast.
Get it here: https://github.com/maniac103/android_device_motorola_jordan/downloads#download_187690
It works superbly
Thanks guys, everything works superbly. The phone didn't lock and it feels like a dead man has been given a life back again!
Hi,
After doing some reading on here I am a little unsure on the best way to back up my HTC One M9 (GSM) stock recovery/system. My software number is 3.50.710.1 (Android 6.0) and it came from Optus (Australia). I cannot seem to find an RUU file for this firmware anywhere online; only earlier versions are available. My understanding of this is that I need an RUU file for my specific firmware as a fail-safe in case I mess something up and need to return to stock?
My questions are:
1) Can I get my phone back to the current complete stock firmware and be able to receive future OTA updates without turning s-off and without copying anything from my phone before I flash TWRP and a custom ROM?
2) If not is there anyway that I can back up my phone it its current stock state that will allow me to go back to this state if I want to go back to my stock Optus firmware or to install OTA updates? (Including the stock radio/recovery)
3) Reading this post as well as others leads me to believe that I may stop my mobile radio working by flashing a custom ROM (especially as the linked post has the exact same firmware as me). How can I avoid this, or fix it if it happens to everyone?
I am ideally looking for a custom ROM which improves over the stock firmware. My priority is maximum battery life, with customisation and HTC 10 system UI/apps a secondary focus. Any recommendations would be great, as well as tweaks and kernels which help give the maximum battery life.
Cheers!
You can't backup your firmware (and that includes your radio). However if you read my google sheet you'll find instructions for backing up your current boot.img, your system and the stock recovery. If you do it correctly those files will suffice for recovering the ability of installing OTAs. No personal data will be backed up so maybe you want to share your backup with us afterwards.
There is a custom kernel for CM/AOSP roms which is said to repair the signal problems. As far as I read some sense rom users reported that flashing the stock boot.img recovered their signal. However this doesn't seem to work for every user. So you'll need to try by yourself.
Flippy498 said:
You can't backup your firmware (and that includes your radio). However if you read my google sheet you'll find instructions for backing up your current boot.img, your system and the stock recovery. If you do it correctly those files will suffice for recovering the ability of installing OTAs. No personal data will be backed up so maybe you want to share your backup with us afterwards.
Click to expand...
Click to collapse
Thank you so much! I have managed to find the guide you mentioned to backup the stock boot image, system image and recovery. By the looks of it the tab to the right is the guide to return my phone to its original state, which is good. I'm more than happy to share the backup once I do it.
Flippy498 said:
There is a custom kernel for CM/AOSP roms which is said to repair the signal problems. As far as I read some sense rom users reported that flashing the stock boot.img recovered their signal. However this doesn't seem to work for every user. So you'll need to try by yourself.
Click to expand...
Click to collapse
Okay, well I am planning on keeping s-on at this stage, so I'm left with Sense based ROMs I believe? I have read that LeeDroid is the best for battery life, does this sound right? If so I am unsure if I can flash it as it says "Please make sure you have the latest HTC Hima 3.35.XXX.XX Marshmallow firmware installed prior to installing this ROM" because my software number is 3.50.710.1?
Thanks again!
Da Doom Lord said:
Okay, well I am planning on keeping s-on at this stage, so I'm left with Sense based ROMs I believe? I have read that LeeDroid is the best for battery life, does this sound right? If so I am unsure if I can flash it as it says "Please make sure you have the latest HTC Hima 3.35.XXX.XX Marshmallow firmware installed prior to installing this ROM" because my software number is 3.50.710.1?
Click to expand...
Click to collapse
I've read that several times in the near past and I actually don't understand it. You never needed S-OFF for flashing none-sense based roms as long as I started using Android/HTC phones and that was back in 2012. Why do so many people think they need S-OFF for AOSP?
I personally prefer the Viper rom. But taste differs and in the end the best advice I can give is try it out by yourself. Everyone has different needs and is using his/her phone in a different way. The best rom for person a might be an awful choice for person b since he/she has completely different needs.
I can't tell you whether you can use Leedroid. Test it and report back. That's how xda works. You might be able to use it after you flashed your stock boot.img but I don't know whether you really are or not. The warning is written so that people don't start flashing that rom with a lower firmware version. On older HTC phones flashing an "older" rom has never been an issue on newer firmware versions whereas flashing a newer rom on an older firmware never goes well (even on the M9). However many things have changed since the M9. There is no hboot anymore, the Download Mode got introduced, google changed the way OTAs are checking whether your system is modified, and so on. (Just to mention a few changes.) Those issues with the lost signal didn't even exist on pre-3.x firmware versions of the M9. Therefore users like you who use a not so common firmware (in comparison to the user numbers of the most common firmware bases: international, taiwanese and the developer firmware) have no other choice but trying out by themselves or getting S-OFF and changing to a more common firmware.
Flippy498 said:
I can't tell you whether you can use Leedroid. Test it and report back. That's how xda works. You might be able to use it after you flashed your stock boot.img but I don't know whether you really are or not. The warning is written so that people don't start flashing that rom with a lower firmware version. On older HTC phones flashing an "older" rom has never been an issue on newer firmware versions whereas flashing a newer rom on an older firmware never goes well (even on the M9).
Click to expand...
Click to collapse
I have followed your guide and now have the latest stable LeeDroid ROM installed and TWRP. Just as I predicted the radio was not originally working. When I restored my stock boot.img from the original backup I performed it began to work. Thanks so much for your help! I'll upload the backup to cloud storage when I get access to a decent internet connection and then I'll share it to help others out.