Develop Bugs

Wildfire ROM update - backup questions

Hi everyone,
I'm using a HTC Wildfire and am considering changing from stock (HTC non-branded) to CyanogenMod for a number of minor reasons. Could anyone just confirm that I got a few points right before I get started:
- Recovery is totally independent from the ROM itself, right? So I can flash ClockWorkMod Recovery only, continue to use the stock ROM, but have the additional features of ClockWorkMod available, such as backup, with which I can create a complete backup of the stock ROM. In case I don't like CyanogenMod, I can restore the stock image and be exactly where I left it, Apps, Settings and everything (of course the new Recovery will still be installed.) Is this correct?
- I'm planning to do the following steps (I read about the details, just want to confirm the basics):
x use the Revolutionary way to S-OFF and install new Recovery
x create full image backup of the stock ROM using the new Recovery
x install new ROM (ClockWorkMod)
x if I don't like CM: restore image created before to return to stock
-> This should work, shouldn't it?
- One more: What will happen if the the phone is S-OFF, an alternative Recovery is installed, and a HTC Firmware-Update is attempted? Will this work at all, will it update just the ROM, or will it update the Recovery, too? S-OFF will not be changed back to S-ON, right?
Thanks for your help.
Regards

1. Yes, the recovery is in it's own partition and is independent from the ROM
2. The recovery creates a "snapshot" of your current ROM. So when you restore, it'll be just the way you left it.
3. There's no need to do any HTC Firmware updates after installing a custom ROM (infact, I'm almost 100% sure that it won't work)

As a basic answer yes you go ahead with what you posted.just make sure your hboot version is compatible with revolutionary 1st etc etc.
As for HTC firmware update question,if your talking about the over the air updates I'm not sure but I think it would update your hboot thus reverting back to s-on status again so best not accept it if you do get one (turn off in settings)
Edit : ninja'd lol
Sent from my HTC Wildfire using XDA App

slymobi said:
As a basic answer yes you go ahead with what you posted.just make sure your hboot version is compatible with revolutionary 1st etc etc.
Click to expand...
Click to collapse
Yes, of course.
As for HTC firmware update question,if your talking about the over the air updates [...]
Click to expand...
Click to collapse
No, the manual ones you can download directly from HTC and install via USB. My understanding was that this would kill everything flashable, including radio and recovery. It would be reassuring to have a worst-case way to go back to stock in case the image-restore fails for whatever reason.

150d said:
Yes, of course.
No, the manual ones you can download directly from HTC and install via USB. My understanding was that this would kill everything flashable, including radio and recovery. It would be reassuring to have a worst-case way to go back to stock in case the image-restore fails for whatever reason.
Click to expand...
Click to collapse
Ah sorry never dealt with any firmware updates. There are ruu.exe to help get back to stock if something goes wrong I think.
Sent from my HTC Wildfire using XDA App

You can go completely back to stock, s-on and all but believe me once you have cwm installed there really is no point unless its for warranty reasons, backup fails are rare with the latest recoveries + if it does fail with your first backup you can always post here and we will explain how to extract a stock Rom from an ruu to put things back to how they where before or you can flash a custom sense Rom and modify it to your liking.
Sent from my HTC Wildfire using xda premium

Scratch0805 said:
You can go completely back to stock, s-on and all
Click to expand...
Click to collapse
That's great.
[...] but believe me once you have cwm installed there really is no point unless its for warranty reasons[...]
Click to expand...
Click to collapse
Yea, exactly. I'm a little on the paranoid side, I know... ;-)
Ok, I'm on my way now. I've performed the "Revolutionary" S-OFF and am now running "Revolutionary CWM v4.0.1.4". Is this an out-of-date version?
I've read about ROM-Manager being able to auto-check for and flash a new Clockworks Recovery, but I've also read that ROM-Manager needs root. I have not yet flashed a new ROM, so I assume that I'm not yet rooted, am I? Can I find a ZIP of CWM that I can directly flash from the SD-card?
Does the CWM-version I'm running have any effect on the "quality" of the image backup? In other words, if I create a backup now, will I be able to restore it later running a different version of CWM?

The "different version backup restore" is a bit wonky and won't always work.
To flash a different recovery from the SD card do this:
1. Place this file on your SD card (Not in any folders!): http://www.multiupload.com/74EW2VPNHL
2. Boot into the bootloader
3. Wait a bit and then it should prompt you to update
4. Click the volume+ key to update
5. Remove SD card
6. Boot into the new recovery and insert the SD card
7. Go under mounts and select Mount USB storage
8. Delete the PCIMG file from your computer

nejc121 said:
1. Place this file on your SD card (Not in any folders!): http://www.multiupload.com/74EW2VPNHL
Click to expand...
Click to collapse
I tried to, but I couldn't use the link. The whole domain seems to be down - maybe another holy crusade of Big Content, who knows. They sure leave fans in their wake, don't they.
Since you indicated that updating would be ok for the wildfire I went to http://www.clockworkmod.com/rommanager and downloaded the file recovery-clockwork-5.0.2.0-buzz.zip.
However, I'm not sure how to handle it: If I put it on the card under this name, nothing happens on bootloader-start. In recovery, I can select the file and install it, and then I immidiatly get a newly colored menu with the new CWM version 5.something. However, once I restart, the old CWM (v4.x) is there again.
I assume I need to use a magic filename so that the bootloader performs the update, not the (already running) recovery. Right?
**EDIT: Ah, disregard. I believe I found the answer myself.

Do you have fastboot?
If you do I can give you the recovery.img I'm using, which you can flash via fastboot.

Yes, fastboot is available.
Thank you.

Okay, here's how you flash a recovery via fastboot.
1. Extract the .zip I attached to the location where you fastboot is
2. Reboot phone in the bootloader
3. Select fastboot and attach USB cable
4. Open up the command prompt and type in "cd [location of fastboot]
5. Type in "fastboot flash recovery recovery.img"
6. You're done
Oh and by [location of fastboot] I mean that you type in the location of fastboot.

Wow - this was fun. There was something really curious going on with my device: Whatever I tried, no "official" way worked to modify CWM v4 to v5. In every case, the menu of the new version showed up and was usable, but was gone again after restart. After the file-on-card method got me nowhere (file was not recognized), I tried the high road and installed ROM-Manager. This complained about missing su. So I installed su. After that ROM-Manager downloaded CWM v5 and put it onto the card (into a file named update.zip - ahh... ) On restart, the CWM-install-screen came up, then the v5 menu.
And after restart, it was gone again. Even ROM-Manager was confused: He showed v5 as "installed", when in fact it was still v4. ;-)
So finally I downloaded the Android SDK (to get fastboot.exe) and performed the flash as you suggested in the first place. And it worked. First try, without hitch, permanently.
Thank you very much for your help!
Regards

The problem with ROM Manager's version is that it's only temporary and can only be accessed from the ROM Manager itself

[Q] Installing Jelly Bean on my HOX

Hello all,
I've got an unbranded international (taiwan) HOX.
Today I was notified that I got an update availabe for my device - finally JB!
So I let it download and install, but when it turns off to install (in CWM) it automatically I've got an error that says
PHP:
"E: unknown volume for path [file path]"
"E: Can't mount [file path]"
"Installation aborted."
So I tried to install the file from the zip manually (in CWM) but I got these errors:
PHP:
"E: failed to verify whole-file signature"
"E: signature verification failed"
"Installation aborted."
Also tried to put it in another folder and install manually, but no luck, and even re-download it. (Delete, let it download the update again and install).
Another friend who's got the same phone as mine (we bought it at the same store) did get to install the update successfully.
Any thoughts? I'll go ahead and say that my phone has CWM and is rooted. my friend's phone is clean in that matter, no modifications.

noodlez04 said:
Hello all,
I've got an unbranded international (taiwan) HOX.
Today I was notified that I got an update availabe for my device - finally JB!
So I let it download and install, but when it turns off to install (in CWM) it automatically I've got an error that says
PHP:
"E: unknown volume for path [file path]"
"E: Can't mount [file path]"
"Installation aborted."
So I tried to install the file from the zip manually (in CWM) but I got these errors:
PHP:
"E: failed to verify whole-file signature"
"E: signature verification failed"
"Installation aborted."
Also tried to put it in another folder and install manually, but no luck, and even re-download it. (Delete, let it download the update again and install).
Another friend who's got the same phone as mine (we bought it at the same store) did get to install the update successfully.
Any thoughts? I'll go ahead and say that my phone has CWM and is rooted. my friend's phone is clean in that matter, no modifications.
Click to expand...
Click to collapse
You need to go back to stock in everything to get that update ... It needs stock recovery and locked bootloader ...

chaun1308 said:
You need to go back to stock in everything to get that update ... It needs stock recovery and locked bootloader ...
Click to expand...
Click to collapse
Could you please refer me to a guide that will help me do that?
and from my understanding, If I'll go back to stock, and update, I'll have to unlock the bootloader again. Last time I did that I had to delete everything on my phone (I guess this will happen when I revert the root and bootloader unlocking too), so got any good way to backup all the app data and everything I need?
Thanks.

noodlez04 said:
Could you please refer me to a guide that will help me do that?
and from my understanding, If I'll go back to stock, and update, I'll have to unlock the bootloader again. Last time I did that I had to delete everything on my phone (I guess this will happen when I revert the root and bootloader unlocking too), so got any good way to backup all the app data and everything I need?
Thanks.
Click to expand...
Click to collapse
Correction . You will have to relock the bootloader again . And since you've rootedd your phone , use Titanium Backup or MyBackup .
This video will guide you to complete stock .

Relocking bootloader is not necessary for OTA updates, but you need stock recovery.
You have to find a stock recovery and then flash it via Fastboot.
Tutorials over here: http://forum.xda-developers.com/showthread.php?t=1832891

Agree with webpatrick
you only need stock recovery to install OTA updates, just find your original rom(or extract from ruu) and flash it in bootloader fastboot flash recovery path_to_recovery_signed.img
not sure if it requires locking the bootloader or not, after that you can reinstall CWM the way you did before and make a backup.

There are 2 options
1:
Flash the non-rooted stock rom with stock boot.img and stock recovery. Bootloader can stay UNLOCKED.
2:
Flash the right RUU, only LOCKING the bootloader is needed. The ruu will flash the stock recovery and boot.img.
Just to be clear
Verstuurd van mijn HTC One X

Need some clearing up here:
1. Can my phone stay rooted? if not - how do I remove SuperSU? tried to remove it from ES by removing the SU file and the app from system/app but that didn't work. - EDIT: Managed to remove root from my device using HTC Quick Root, though it says I need to install secure boot.img to entirely remove root.
2. I tried to flash a recovery file I found in a guide, but the recovery doesn't really work...when I try to access the recovery I got the error screen (the one with the red triangle and exclamation mark), so can someone refer me to a working recovery? attached my software information.
3. Do I need to relock my bootloader or not?
Thanks alot guys, I'm pretty much of a newbie in this whole business

Okay let me lay it down for you.. Pretty simple.. This process doesn't need you to relock the bootloader. (Even if you had to using the other process you would be adding a couple of minutes more in unlocking bootloader)
method1:
1- First things first get your RUU depending upon the version you are at. I haven't had a look at your picture. but just make sure that your region is correct and that the version you possess is either the same version or higher.
2- You need to flash the recovery as that is what will update the recovery and the ROM. so as mentioned above you can just go into fastboot and then flash recovery using the RUU.
method 2:
just relock te bootloader by going into fastboot and typing "fastboot oem lock".
Once that is done you can just run RUU and it will update everything for you. Once complete just unlock bootloader and then flash CWM.. thats it

zainalabididn.syed said:
Okay let me lay it down for you.. Pretty simple.. This process doesn't need you to relock the bootloader. (Even if you had to using the other process you would be adding a couple of minutes more in unlocking bootloader)
method1:
1- First things first get your RUU depending upon the version you are at. I haven't had a look at your picture. but just make sure that your region is correct and that the version you possess is either the same version or higher.
2- You need to flash the recovery as that is what will update the recovery and the ROM. so as mentioned above you can just go into fastboot and then flash recovery using the RUU.
method 2:
just relock te bootloader by going into fastboot and typing "fastboot oem lock".
Once that is done you can just run RUU and it will update everything for you. Once complete just unlock bootloader and then flash CWM.. thats it
Click to expand...
Click to collapse
now I've got a few problems with that:
first of all, my version is 2.18 and there is no RUU for that version for my HTC (which is TWM-TW) yet. and I don't wanna go back to stock ROM, it is the one I have. I just want to set my phone straight so it can get the OTA JB update.
The problem I think I've got now is that my recovery is malfunctioning. I think I don't have the right recovery, since when I try to go into recovery mode I get the red triangle and exclamation mark.
When I tried to install the update, it downloaded it, went into recovery, started doing the process (the green bar was progressing) and then out of the blue - error screen (red triangle and exclamation mark)...
Any ideas?

I always have this problem when i try to update even if i go back to the stock recovery.The problem is that you installed something that modified you'r system (in my case i've installed using CWM the Google Now and some other stuff on it) and now the phone can't update because something is "messed up" in the system.You now have to restore and old backup in CWM,preferably one that doesn't have any mods in it.The recovery is good,otherwise it wouldn't work at all.

jeyml said:
I always have this problem when i try to update even if i go back to the stock recovery.The problem is that you installed something that modified you'r system (in my case i've installed using CWM the Google Now and some other stuff on it) and now the phone can't update because something is "messed up" in the system.You now have to restore and old backup in CWM,preferably one that doesn't have any mods in it.The recovery is good,otherwise it wouldn't work at all.
Click to expand...
Click to collapse
Well, I rooted my phone and installed CWM. so I did the unroot (as far as I know) and got the stock recovery, so what else could it be? :S

No,you didn't understand,this is not about the stock recovery.This is about the fact that you probably installed something (using CWM) that rewrited some files in the /system or other folders that this update depend on.Because those folders are modified the update doesn't recognize those apps and can't continue.That is what i am saying.Install the CWM again,search for any nandroid backups that you have on it and install the oldest one.I usualy make a nandroid backup everytime i update my phone because until the next update i keep installing stuff that messes up my ROM and in cases like yours i just apply the backup i've taken and voila,the update works.Also there is one app that messes up you'r system,it is called BusyBox,and if you install that app and want to make an update,the update will fail (red triangle) because of that app.
If you don't have any nandroid backups the only solution is to install the RUU.

jeyml said:
No,you didn't understand,this is not about the stock recovery.This is about the fact that you probably installed something (using CWM) that rewrited some files in the /system or other folders that this update depend on.Because those folders are modified the update doesn't recognize those apps and can't continue.That is what i am saying.Install the CWM again,search for any nandroid backups that you have on it and install the oldest one.I usualy make a nandroid backup everytime i update my phone because until the next update i keep installing stuff that messes up my ROM and in cases like yours i just apply the backup i've taken and voila,the update works.Also there is one app that messes up you'r system,it is called BusyBox,and if you install that app and want to make an update,the update will fail (red triangle) because of that app.
If you don't have any nandroid backups the only solution is to install the RUU.
Click to expand...
Click to collapse
Thanks for making it all clear I'll check if I've got a backup from when I formatted my phone (does root affect this process?)
And from what I understand, I can only install RUU that is the same as my phone's version or higher. right now I got 2.18, the TWM-TW version of the phone. know by any chance if there is an RUU for it?

The root should not affect the backup/restore proces as far as i know.Yes,the RUU must be the same as phone version or higher.Honestly i don't know any RUU for that,try searching for the new JB RUU.
EDIT:
Check you'r CID and download one of the stock nandroid backups here:
http://forum.xda-developers.com/showthread.php?t=1975140

Thanks for the nandroid, It will be my last resort if restoring a clean image won't help
and about the root - I meant if it's supposed to interfere with the update.
Thanks.

So let me get this straight. You don't have the RUU for your version at all?? and what recovery is installed right now???

No problem,if there are any other problems just ask.

@zainalabididn - I made a recovery image when i first rooted the phone (not when I first got it), but it still won't let me update over it - maybe because of the root. the recovery I'm using right now is CWM 5.8.4
@jeyml - I tried to install the nandroid in the link you gave me, but it wouldn't let me flash the hboot on my device, so after flashing the boot and nandroid it just went into loops of trying to start up, getting stuck and rebooting. got any idea why that happens? (notice: I don't have S-off, if that's what causing the problem)

Both CM9/CM10 hangs at boot.

My procedure in chronological order:
Flashed recovery TWRP 2.3
Wiped everything possible in the wipe-tab
Installed CM9/10 from zip on SD-card (zip contains META-INF, system and boot.img)
Flashed boot.img from the zip file CM9/10
Issued the command fastboot erase cache
Unplugged cable and reboot
What happens is that I am stuck at the HTC booting screen. I have been here for about 30-40 minutes. If I try any adb shell command I receive this error: - exec '/system/bin/sh' failed: No such file or directory (2) -. Clearly, something is not right here. I will not speculate because I lack the knowledge to do so. Any help is appreciated because I have been phone-less for a day now and it is getting irritating. Thanks!

Seems you did everything correctly.
Try to flash via ClockWorkMod recovery.
Sent from my HTC One X

TToivanen said:
Seems you did everything correctly.
Try to flash via ClockWorkMod recovery.
Click to expand...
Click to collapse
I just did the same procedure as before but with clockworkmod instead. Still hung at booting screen. I get the same error as before. Is root access a must? I have not done any exploit, only thing I have done is unlocked my boot loader at HTCDev.

zettez said:
I just did the same procedure as before but with clockworkmod instead. Still hung at booting screen. I get the same error as before. Is root access a must? I have not done any exploit, only thing I have done is unlocked my boot loader at HTCDev.
Click to expand...
Click to collapse
Root should not be needed since most roms are rooted by default.
Did you flash gapps?

TToivanen said:
Root should not be needed since most roms are rooted by default.
Did you flash gapps?
Click to expand...
Click to collapse
No, I have not. Maybe I should give it a try? Or is it not required? Should I not be able to start the phone without any gapps?
Do you by chance have any ROM you can recommend that works so I could try it out and exclude problems? Would very like to know if it is my phone or ROM that is buggy.

It should boot without them, but better to give it a try.
Ironically, I've been using CM10 for more than a month now and never had any problems booting.
Sent from my HTC One X

If you have an hboot newer than 1.12 you need a different boot.img, check the bottom if the ROM OP.

TToivanen said:
It should boot without them, but better to give it a try.
Ironically, I've been using CM10 for more than a month now and never had any problems booting.
Click to expand...
Click to collapse
Would you mind telling me which CM10 build you are using and which boot.img you flashed?

BenPope said:
If you have an hboot newer than 1.12 you need a different boot.img, check the bottom if the ROM OP.
Click to expand...
Click to collapse
I have hboot 1.3 or something I think. I downloaded the different builds at get.cm. Where can I get the boot.img if not the one in the zip file? Do you mean whichever thread that CM have posted themselves here on xda? Would you mind sending a link to where I can find the boot.img?

zettez said:
I have hboot 1.3 or something I think. I downloaded the different builds at get.cm. Where can I get the boot.img if not the one in the zip file? Do you mean whichever thread that CM have posted themselves here on xda? Would you mind sending a link to where I can find the boot.img?
Click to expand...
Click to collapse
Normally it would be found in the bottom of CM10 threads OP but the link is down.
Here you go:
http://forum.xda-developers.com/showpost.php?p=34829297&postcount=9173
Remember to repack it with the one found in zip. Repack tool stickied on android development forum.
Sent from my HTC One X

TToivanen said:
Normally it would be found in the bottom of CM10 threads OP but the link is down.
Here you go:
http://forum.xda-developers.com/showpost.php?p=34829297&postcount=9173
Remember to repack it with the one found in zip. Repack tool stickied on android development forum.
Click to expand...
Click to collapse
Thanks, but still a no go. What I did was take the modified boot from your link and the boot.img from the zip file, do the online converter as stickied on the forum, then did the procedure all again but this time I flashed the new boot.img I got from combining the old and the new boot.img. Still hangs at boot. Very annoying. I am currently using a modified stock ROM and I dislike it very much.

Hey,
I have exactly the same issue. I've unlocked my bootloader using the method as specified by htcdev.com. Then I flashed the newest CWM recovery. But if I flash any ROM, I'm stuck at its boot animation. However if I then unzip the boot.img from the ROM, and flash that (fastboot flash boot boot.img), my phone won't boot past HTC screen. Even erasing the cache didn't help (fastboot erase cache).
I've restored the stock ROM using the RUU, however during the process something went wrong and it formatted my sd-card. So I'm stuck with the stock ROM, without any applications or data.
Can anybody help me flash CM10?
My Hboot version is 1.36.0000
And I'm trying to flash the cm-10-20121210-NIGHTLY-endeavoru.zip ROM.
Thanks in advance
Han

irundaia said:
Hey,
I have exactly the same issue. I've unlocked my bootloader using the method as specified by htcdev.com. Then I flashed the newest CWM recovery. But if I flash any ROM, I'm stuck at its boot animation. However if I then unzip the boot.img from the ROM, and flash that (fastboot flash boot boot.img), my phone won't boot past HTC screen. Even erasing the cache didn't help (fastboot erase cache).
I've restored the stock ROM using the RUU, however during the process something went wrong and it formatted my sd-card. So I'm stuck with the stock ROM, without any applications or data.
Can anybody help me flash CM10?
My Hboot version is 1.36.0000
And I'm trying to flash the cm-10-20121210-NIGHTLY-endeavoru.zip ROM.
Thanks in advance
Han
Click to expand...
Click to collapse
You cannot use the boot.img that comes with the zip out of the box if you have Hboot 1.36. What you have to do is repack it, taking the boot.img from the zip file and then a modified boot.img here http://forum.xda-developers.com/show...postcount=9173 (thanks TToivanen), then as I understood it, repack it for instance here http://forum.xda-developers.com/showthread.php?t=1815607, download the repacked boot.img and flash that.
With that said, I could not get it running but it might be something wrong with my phone. Please try this out and tell me if it works or not so I may start to conclude where the error lies.

zettez said:
Thanks, but still a no go. What I did was take the modified boot from your link and the boot.img from the zip file, do the online converter as stickied on the forum, then did the procedure all again but this time I flashed the new boot.img I got from combining the old and the new boot.img. Still hangs at boot. Very annoying. I am currently using a modified stock ROM and I dislike it very much.
Click to expand...
Click to collapse
Sorry, but all I can say is that you did a mistake at some point.
Try installing again with full wipe and remember to wipe cache and dalvik.
You are referring to the official CM10 and not Trip's or any other builds right?

TToivanen said:
Sorry, but all I can say is that you did a mistake at some point.
Try installing again with full wipe and remember to wipe cache and dalvik.
You are referring to the official CM10 and not Trip's or any other builds right?
Click to expand...
Click to collapse
Will try again. I got the latest build from http://get.cm/?device=endeavoru. Will try cm-10-20121213-NIGHTLY-endeavoru.zip as it came out today.

zettez said:
You cannot use the boot.img that comes with the zip out of the box if you have Hboot 1.36. What you have to do is repack it, taking the boot.img from the zip file and then a modified boot.img here http://forum.xda-developers.com/show...postcount=9173 (thanks TToivanen), then as I understood it, repack it for instance here http://forum.xda-developers.com/showthread.php?t=1815607, download the repacked boot.img and flash that.
With that said, I could not get it running but it might be something wrong with my phone. Please try this out and tell me if it works or not so I may start to conclude where the error lies.
Click to expand...
Click to collapse
I did that and now my phone is still stuck on the HTC screen. Trying to restore my backup of the stock ROM atm.
---------- Post added at 04:35 PM ---------- Previous post was at 04:30 PM ----------
hmm the backup was useless... Off to the RUU it is....

irundaia said:
[/COLOR]hmm the backup was useless... Off to the RUU it is....
Click to expand...
Click to collapse
You flashed the stock boot.img before restoring?

irundaia said:
I did that and now my phone is still stuck on the HTC screen. Trying to restore my backup of the stock ROM atm.
Click to expand...
Click to collapse
I see, then it is not only I who have this problem.
And a heads up, if the backup would go wrong, I currently use this ROM and it works pretty good if you want stock or cannot be arsed to get a root exploit for the stock ROM. http://forum.xda-developers.com/showthread.php?t=2035203.
Would be great if anyone has any ideas why irundaia and I cannot make CM10 work?

TToivanen said:
You flashed the stock boot.img before restoring?
Click to expand...
Click to collapse
You're right, I forgot to do that. I does boot now, still at a loss though. Can't we downgrade our Hboot to a version in which we know that CM can be flashed?

Kinda out of ideas here...
Can you confirm that the boot.img flashes ok? (should say OKAY)
Also confirm that you have endeavoru and not evita.

HTC Desire Hd won't start after updating Jellytime

Hay guys,
for my Desire HD i use the custom rom Jellytime. I used the r6.2, then i flashed an update.zip to r7.
But then i realized, bluetooth is not working and i'm not connected to my google account. So i decided to downgrade to r6.2, so i flashed the .zip as an update.zip. now my phone freezed after the jellytime bootlogo :/
I tried to get to the recovery but when i press power+ volume down, it vibrates 3 times and nothing happens.
does anybody knows what to do? I have a backup, so are there any possibilities, to restore the backup?
slixx

Ouch, did you flash the ROM as an update.zip or the backup?? And what recovery do you got?

hay,
i flashed the r7 as an update.zip, to update my custom rom from r6.2 to r7. and i also flashed the r6.2 as an update.zip to downgrade
I think this was my fault.
i have the lastes version i think - something like 5.0.1.20.

okay,
i used the adb to boot into the bootloader. with the bootloader i booted into the recovery, know i try to restore my backup.
hope it works!

Report back with your progress.
EDIT: and save yourself some trouble next time by using recovery instead of bootloader for installing ROMs

It worked!
i restored the backup, after this i installed an older version of jellytime, flashed gapps, and restored my personal stuff with google
i didn't flashed the rom with the bootloader. i just forgot to flash gapps, after installing the jellytime update ._.
this was the reason why i was not connected to my google account. and the bluetooth function...hmm i dont care cause i don't use it.
but now everything is okay again.

BTW, if you feel like getting back to jelly time, I recommend using v30, or the last 4.1.2 version of jelly time. I think it was only until v9 that jellytime started getting stable, and v30 should be almost bug free.
Sent from my Inspire 4G using xda app-developers app

black screen after update of Jellytime was installed
I flashed in recovery , formatted and all that and picked up the zip of jellytime all installation steps worked fine and once finsihed and the phone was going to finally reboot it just turned black and didn't continue.
HOw do I resolve this? How can I do my backup ? Right now my phone is useless so appreciate a fast answer
Regards
Toby

ektob said:
I flashed in recovery , formatted and all that and picked up the zip of jellytime all installation steps worked fine and once finsihed and the phone was going to finally reboot it just turned black and didn't continue.
HOw do I resolve this? How can I do my backup ? Right now my phone is useless so appreciate a fast answer
Regards
Toby
Click to expand...
Click to collapse
Do you have an unlock bootloader? If so, have you flashed the boot.img in fastboot?

glevitan said:
Do you have an unlock bootloader? If so, have you flashed the boot.img in fastboot?
Click to expand...
Click to collapse
If you mean I am rooted - yes I am. I had the IceColdSandwich before I tried to flash this CM10 JellyTime. I'm not sure I did the fastboot. I did a clean wipe and selected the update rom zip and then followed the steps, inlcuding selecting Desire S and flash (normal?) . It ran through all the installation steps without problems, but when finsihed and during the reboot it hanged (black screen).

ektob said:
If you mean I am rooted - yes I am. I had the IceColdSandwich before I tried to flash this CM10 JellyTime. I'm not sure I did the fastboot. I did a clean wipe and selected the update rom zip and then followed the steps, inlcuding selecting Desire S and flash (normal?) . It ran through all the installation steps without problems, but when finsihed and during the reboot it hanged (black screen).
Click to expand...
Click to collapse
I didn't ask about root, did I? I made 2 simple questions that have not been answered

glevitan said:
I didn't ask about root, did I? I made 2 simple questions that have not been answered
Click to expand...
Click to collapse
So responding a bit more politely;
Do you have an unlock bootloader? To unlock a bootloader is mlostly resolved by doing a root. That I have done so yes in that case I do have a unlocked bootloader. Please correct me if I am wrong in conclusion.
If so, have you flashed the boot.img in fastboot? I am not sure in this. I think I was give two choices - fast boot and normal boot. I selected normal boot.

ektob said:
So responding a bit more politely;
Do you have an unlock bootloader? To unlock a bootloader is mlostly resolved by doing a root. That I have done so yes in that case I do have a unlocked bootloader. Please correct me if I am wrong in conclusion.
Click to expand...
Click to collapse
You are wrong in your conclusion.

bananagranola said:
You are wrong in your conclusion.
Click to expand...
Click to collapse
OK..fine. Still I'm sure I'm unlocked. Now I acctally got the bootloader working - ACE PVT ENG S-OFF RL . So I read your link - thanks it seemed valuable but I didn't get why I needed to open a terminal window (dos window I assume) secondly it didn't work at all since the usb connection didn't connect properly.. I'm sorry for being such a hassle.. . I did before though un zip the folders so if needed - where should the boot image be in order for it to load from the sd card ?
Thanks for the patience
EDIT: I tried to follow the flashboot steps as best I could, but failed to load the image.

ektob said:
ACE PVT ENG S-OFF RL
Click to expand...
Click to collapse
Then you are not unlocked!! I give up.

bananagranola said:
Then you are not unlocked!! I give up.
Click to expand...
Click to collapse
Whatever - I didn't stop me from installing other ROMs. This case is now closed - I changed ROM to CodefireX - worked fine. But sure I will look into it if its necessary - for sure for Jellytime..
I must say you guys really tried to help but any reasons to why I have to unlock bootloader - is that something that have become necessary over time? Maybe its also bad instructions on the ROMS main pages? Why do I need to search 50 different forums to get a simple answer?
Anyway you can give up on me now because I resolved it on my own. Thanks

Because there are additional steps if you are unlocked...

Stuck in TWRP and unable to load recoveries

OK, I have a major problem/possibly problems.
I was running Stock on 1.80.something and flashed the latest LeeDroid ROM, not mentally registering that Lee is on 1.92. Naturally there were some quirks, so I wanted to restore the 1.80 untouched Stock so that I could download and install the 1.92 OTA and move to Lee and other custom ROMs. I understand to do that I have to flash back to Stock Recovery so that I can get the 1.92 OTA since otherwise it fails to install on my phone (I have an unlocked bootloader, root and TWRP). I have yet to successfully do that, though.
I booted into TWRP and wiped Lee since I didn't need it and since I had recoveries. I then flashed the 1.80.709.1 Stock Recovery image from topjohnwu's Stock Backups/Recovery/OTA/RUU repository and booted to it, however, it didn't like any of the 1.80 Untouched System Images I tried to flash from that repository. So, I reflashed TWRP with the adb console thinking I would restore a backup and deal with this another day when I'm not so tired.
For some reason the TWRP Restore menu now only lets me select one item ("DATE"_MMB29M_release-keys), even though I have two other backups. I'm missing the "Up a level" button that lets me pick a different folder, so I can't pick a different backup. Flashing this only available backup gives me the error "Cannot restore system -- mounted read only." Trying to install one of the 1.80 zips from the repository gives me errors saying that it "Could not find 'META-INF/com/google/android/update-binary' " in the zip file. I can only install LeeDroid on a firmware that's too high for my phone.
Any suggestions about what to do? I currently have no OS on my phone and download mode tells me the OS is 1.80.617.1. I apologize for my profuse stupidity on this. I used TWRP fairly frequently with my LG G3, but having to flash Stock Recovery for OTAs on the HTC 10 after a long day adds a whole new layer of complication.
Thanks in advance!

Are you S-off? if yes you can flash 1.9X firmware in DL mode to be able to boot LeeDroid.

macschwag14 said:
OK, I have a major problem/possibly problems.
I was running Stock on 1.80.something and flashed the latest LeeDroid ROM, not mentally registering that Lee is on 1.92. Naturally there were some quirks, so I wanted to restore the 1.80 untouched Stock so that I could download and install the 1.92 OTA and move to Lee and other custom ROMs. I understand to do that I have to flash back to Stock Recovery so that I can get the 1.92 OTA since otherwise it fails to install on my phone (I have an unlocked bootloader, root and TWRP). I have yet to successfully do that, though.
I booted into TWRP and wiped Lee since I didn't need it and since I had recoveries. I then flashed the 1.80.709.1 Stock Recovery image from topjohnwu's Stock Backups/Recovery/OTA/RUU repository and booted to it, however, it didn't like any of the 1.80 Untouched System Images I tried to flash from that repository. So, I reflashed TWRP with the adb console thinking I would restore a backup and deal with this another day when I'm not so tired.
For some reason the TWRP Restore menu now only lets me select one item ("DATE"_MMB29M_release-keys), even though I have two other backups. I'm missing the "Up a level" button that lets me pick a different folder, so I can't pick a different backup. Flashing this only available backup gives me the error "Cannot restore system -- mounted read only." Trying to install one of the 1.80 zips from the repository gives me errors saying that it "Could not find 'META-INF/com/google/android/update-binary' " in the zip file. I can only install LeeDroid on a firmware that's too high for my phone.
Any suggestions about what to do? I currently have no OS on my phone and download mode tells me the OS is 1.80.617.1. I apologize for my profuse stupidity on this. I used TWRP fairly frequently with my LG G3, but having to flash Stock Recovery for OTAs on the HTC 10 after a long day adds a whole new layer of complication.
Thanks in advance!
Click to expand...
Click to collapse
You are flashing wrong files for your phone. What is you cid and mid? It says your os is 1.80.617 but yoy are trying to flash 1.80.709 recover. The 3rd numbers are important that is a region code. Also Leedoid is based on. WWE 1.95.401. If i was you i would flash the RUU that is for your cid and mid and start over.
It seems that you are on US unlocked. If you search you will find an ruu zip for 1.91.617.1

Thanks for the replies. I'm unable to find my CID and MID. Download mode doesn't show either, and the using the adb console commands to show them only gives me the message "waiting for a device" in the console window.
I don't have S-OFF (yet). Should I install the 1.91.617.1 RUU via PC or should I first buy S-OFF and then install the RUU?

macschwag14 said:
Thanks for the replies. I'm unable to find my CID and MID. Download mode doesn't show either, and the using the adb console commands to show them only gives me the message "waiting for a device" in the console window.
I don't have S-OFF (yet). Should I install the 1.91.617.1 RUU via PC or should I first buy S-OFF and then install the RUU?
Click to expand...
Click to collapse
Install the RUU via pc or find the ruu zip and flash in download mode by renaming the zip to 2PS6IMG.zip you dont need SOFF to flash RUU.also remember it will erase your internal storage.

Thanks everyone! I installed RUU 1.91.617.1 and seem to be running smoothly now. I still can't see any other backups on in the TWRP Restore menu and don't have the Up a level button that lets me pick a different directory on my SD card. Any ideas about that?