Related
is it possible to switch to another custom recovery after I already got clockworks?
I tried unrevoked but its stuck in the reboot (I believe its trying to root my aria again)
not sure what youre trying to do.... i believe Clockwork is the only Recovery for rooted phones. if you want to flash a custom ROM, well that is something else altogether. please be specific as to what you want to flash to the phone. include a link to the flash too
I was trying to flash psfreedom recovery rom from here
http://psfreedom.com/wiki/HTC_Aria
I believe the method on that website was for unrooted arias without clockworks
zyo said:
is it possible to switch to another custom recovery after I already got clockworks?
I tried unrevoked but its stuck in the reboot (I believe its trying to root my aria again)
Click to expand...
Click to collapse
To flash a different custom recovery on your Aria, you need to rename the zip file LIBEIMG.ZIP on the SD card and boot in HBOOT (Power on the phone by holding down VOL DOWN and the Power Button). When it boots to the HBOOT screen you should see text stating that it found LIBEIMG.ZIP and is installing it.
awesome. now before I go ahead, is there any clockworkx recovery image I can revert back to?
zyo said:
awesome. now before I go ahead, is there any clockworkx recovery image I can revert back to?
Click to expand...
Click to collapse
I'm curious, what recovery are you talking about?
thanks for including the link. the instructions are clear.... Root IS required, Clockwork recovery is recommended, the Freedom Aria flash appears to be a custom ROM.
once the phone is Rooted, boot into Recovery, make a Nandroid backup, and flash downloaded zip file from SD card.
if you need help Rooting, there is all sorts of good methods available on this site. I use the Unrevoked method myself, but it works best on Linux or Mac OS
zedbra said:
thanks for including the link. the instructions are clear.... Root IS required, Clockwork recovery is recommended, the Freedom Aria flash appears to be a custom ROM.
once the phone is Rooted, boot into Recovery, make a Nandroid backup, and flash downloaded zip file from SD card.
if you need help Rooting, there is all sorts of good methods available on this site. I use the Unrevoked method myself, but it works best on Linux or Mac OS
Click to expand...
Click to collapse
hmm I think you are looking at the old method which is a custom rom
The new one is a custom recovery which brings me to the question as I dont think you can flash a custom recovery in the clockwork custom recovery.
its possible im looking at the wrong thing, but far as i can tell it states "Recovery Custom ROM" which is totally different from Custom Recovery ROM
From link posted above:
"Update can be installed in recovery mode in Psfreedom settings menu via Update (local) or Update (net) if you have configured your wifi connection. Put the file on your SDCARD and install it.
Download Recovery custom rom : http://alephzain.klutsh.com/aria-recovery.tgz "
tpbklake said:
To flash a different custom recovery on your Aria, you need to rename the zip file LIBEIMG.ZIP on the SD card and boot in HBOOT (Power on the phone by holding down VOL DOWN and the Power Button). When it boots to the HBOOT screen you should see text stating that it found LIBEIMG.ZIP and is installing it.
Click to expand...
Click to collapse
I have similar questions. I was trying to update my version of clockwork also using unrevoked again, but couldn't get it to work. I guess my questions are:
1. Is there any benefit in updating to a newer version of clockwork? My current version is 2.0.x.x and I believe the latest one is 2.5.0.4.
2. Will this same method work to do so? Can I rename the latest clockwork .zip file like this and get it updated?
I thought using the flash clockwork option in ROM Manager would do it, but it doesn't. If I reboot from ROM Manager it goes to the newer version, but if I reboot otherwise it goes to my original. The couple times I've used it, there appears to be maybe some different features/options in the newer one and I feel like I might be missing out on something!
What's the difference with this recovery?
Sent from my Liberty using XDA App
zedbra said:
its possible im looking at the wrong thing, but far as i can tell it states "Recovery Custom ROM" which is totally different from Custom Recovery ROM
From link posted above:
"Update can be installed in recovery mode in Psfreedom settings menu via Update (local) or Update (net) if you have configured your wifi connection. Put the file on your SDCARD and install it.
Download Recovery custom rom : http://alephzain.klutsh.com/aria-recovery.tgz "
Click to expand...
Click to collapse
These are probably two different things. once you got the recovery rom flashed you can upgrade it in recovery mode (hence its different from original clockwork recovery)
Ok bro, I didn't see much info about it so I'm gonna take your word for it.
@brswattt, far as I can tell this is " basically" used for jailbreaking the ps3.
@armyengineer;
you can use unrEVOked to flash the new recovery. if youre a Windows user, download the unrEVOked tool and run the .exe as Administrator. also make sure there are no conflicting s/w on the PC such as HTC Sync and you have all the drivers installed(HBoot, ADB drivers, etc.)
for more info about the PSFreedom Recovery, check out THIS Thread HERE
unrevoked keeps giving me
couldnt find misc
error, is there any other way to flash a recovery?
zedbra said:
@armyengineer;
you can use unrEVOked to flash the new recovery. if youre a Windows user, download the unrEVOked tool and run the .exe as Administrator. also make sure there are no conflicting s/w on the PC such as HTC Sync and you have all the drivers installed(HBoot, ADB drivers, etc.)
Click to expand...
Click to collapse
This still isn't working for me. Everything appears to go well at the start, then I get:
Waiting for root...(safe to restart if this doesn't work)
At which point the only way I can restart is to pull my battery. After doing so, it reboots and I get:
This was a triumph
It is not, however, any such thing. After another minute I get this:
Internal error: couldn't find misc.
So I've still got my original version of clockwork, 2.0.1.3, despite the fact that ROM Manager is telling me I have 2.5.0.1. I'm obviously missing something here.
BTW, if it matters I'm running CM 6.1.0
armyengineer51 said:
I have similar questions. I was trying to update my version of clockwork also using unrevoked again, but couldn't get it to work. I guess my questions are:
1. Is there any benefit in updating to a newer version of clockwork? My current version is 2.0.x.x and I believe the latest one is 2.5.0.4.
2. Will this same method work to do so? Can I rename the latest clockwork .zip file like this and get it updated?
I thought using the flash clockwork option in ROM Manager would do it, but it doesn't. If I reboot from ROM Manager it goes to the newer version, but if I reboot otherwise it goes to my original. The couple times I've used it, there appears to be maybe some different features/options in the newer one and I feel like I might be missing out on something!
Click to expand...
Click to collapse
Although there is a ClockworkMod 2.5.0.4 version, I don't think it is for the Aria. According to ClockworkMod ROM Manager, 2.5.0.1 is the most current one for the Aria so I am believing what ROM Manager is telling me since it is written by the same the vendor.
I have tried CM 6.1.0
original HTC Aria 2.1 International Rom
and FR001 RC1
all no go. I think it has something to do with the phone already been rooted and has clockworks installed which makes unrevoked unhappy
zyo said:
I have tried CM 6.1.0
original HTC Aria 2.1 International Rom
and FR001 RC1
all no go. I think it has something to do with the phone already been rooted and has clockworks installed which makes unrevoked unhappy
Click to expand...
Click to collapse
OK, let's start from the beginning. You asked about installing an alternate recovery (PSFreedom recovery), but apparently it has its own installation procedure that needs to be run on an unrooted Aria.
What you need is to find just the PSFreedom recovery and copy it to your SD called in a file called LIBEIMG.ZIP and that is how you need to install it on a root phone that has ClockworkMod. Perhaps you need to go back to the PSFreedom thread and ask if a LIBEIMG.ZIP can be produced that can be flashed from HBOOT to replace ClockworkMod.
Looks like everything you need is located in the PSFreedom wiki:
http://psfreedom.com/wiki/HTC_Aria
I got a recovery.bin which is suppose to be used with unrevoked.
are you talking about the same one if I just compress it into a zip file?
Not applicable
Delete this thread
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.
Let me answer myself.
I don't think the latest rom 2.3.4 is compatible with the clockwork you supplied. So I have to flash my phone back to GRH78. I downloaded the stock ROM from the internet. and then push all the images file into /sdcard/clockworkmod/backup/2010.xxx.
Next, I restore the image in clockwork menu.
after restore, reboot the phone, now I am back in business.
When the phone is boot, i lost the root again, so i went to modaco.com and get Paul's package. run it, restart, I got the root.
Finally, go to market place and get ROM Manager, install the clockwordmod. and I have a 'proper' phone.
although I don't have the least rom, at least i got a working phone that is rooted.
bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
I have the same problem. How did you handle it?
Wow, why risk messing up your phone with flashing a boot.img when you can just rename /etc/install-recovery.sh to something like /etc/install-recovery.bak?
Here's one way to rename (courtesy of Matridom). Another is to use Root Explorer.
Matridom said:
The new update applies the install-recovery.sh script into our phones (not there previously.
Boot into the bootloader
flash CWM
select recovery from the bootloader (DO NOT reboot the phone)
apply the su binary
boot into the OS and test root
make sure busybox is properly installed
run ADB shell
then:
Code:
su
mount -o remount,rw /dev/block/mtdblock3 /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
Boot back into the bootloader and re-flash CWM, should stay permanent now.l had applied the SU binary at the same time as the OTA update, then renamed the installer script and flashed back CWM.
Click to expand...
Click to collapse
andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
same here someone please help ?
This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App
bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
Hi Bante, I am sorry for the inconvenience. I have revert back the CWM Recovery to 3.0.2.4. You can download it at the link above, and try it again
I hope that the problem you mention wont persist anymore
zero383 said:
This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I am sorry but not all people can successfully use Command Prompt to do so.
I cant use command prompt, as it says "Image cant be loaded".
So I had to use this method.
I search around the forum and seen this as a quite common problem,
so I decided to share it
Hope you understand.
Anyway, thanks for your method too Cheers
andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist
16vMK1 said:
same here someone please help ?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist
Wow people like to make things complicated. Why install an entire rom to get ride of a script?
if you can flash cwm, you should have some basic understanding of fastboot, adb and the search options in the forums. the answers are all there already.
Sent from my Nexus S
No disrespect, I agree flashing recoverys should only be done after you understand how to use the tools to do it. there is no reason someone who is going to mod systems on their nexus shouldn't be able to use fastboot and adb properly. all the right drivers are in the sdk.
Sent from my Nexus S 4G using Tapatalk
nxt said:
Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.
Click to expand...
Click to collapse
This is what I did.
I rooted my NS, which had 2.3.3
Used phone with stock 2.3.3 until I figured out which ROM I want to flash.
Before I flashed any ROM, did a Nandroid Backup through CWM.
Used the ROM for a few days, but when I saw that official update is ready for download for i9020A, did do a restore from the Nandroid backup I created.
Updated from 2.3.3 to 2.3.4, phone works fantastic, video chat also works great.
After update when I tried using any of the apps required SU permission, they didn't work. I tried installing a couple of .apk files, couldn't either install it or after installation it didn't work.
Thought let me try wiping my phone clean and start all over again, may be I will use a custom ROM again, downloaded ROM, went to ROM Manager to reboot into recovery, nothing happens.
Tried booting into Recovery option manually by pressing Volume Up and Power button, nothing happens but the Bot with an Arrow appears on screen.
So, I thought I will follow this procedure to reflash CWM to my phone and get it going. I was able to use the command FastBoot once, and suceeded pushing .img file to my phone but now whenever I try using the commands from my computer, this error message appears : "This application has failed to start becasue AdbWinApi.dll was not found. Re-installing the application may fix this problem."
Why this error message if I have the sdk on my computer already through which I was once able to push .img file without any troubles?
Can anyone tell me what would be a possible solution?
Also, how can I fix this problem and get ClockWorkMod Recovery installed on my NS again?
How can I get stock recovery image on my phone if I want start all over again from scratch?
Thx a million.
Edit ::: I found the answer as to how to how to install CWM again. Thx anyways.
Other question still remains a puzzle... why am I not able to install certain programs or if did manage to install, can't run them?
I ran your method and I think I'm stuck at some step...
My phone now default boots into CWM 3.0.2.4
Recovery boots to a newer recovery I flashed.
How do I get my phone to default boot into the OS again?
Edit: nevermind, just downloaded the full 2.3.4 rom, extracted and flashed the original boot.img.
dreamsforgotten said:
All the right drivers are in the sdk.
Click to expand...
Click to collapse
After installing the sdk and a platform, I have adb, but where is fastboot?
I was getting the same error as "Image cant be loaded". after hours of struggling I found that It's only because I was not in the same directory as the img file. silly eh?
hi,did you repaiar your phone,i have try everything but it just keep going in clockwork mode,if i than pres reboot now in clockworkmode it stays on google padlock
i realy need phone if you can help or someone else,than ....
just tried this method of window7 (thanks for the work) with cwm 3.0.2.4, but got the same result like the others in this thread: cant boot the android 2.3.4, the system is always booting into the cwm, no way out.
I don't think this tool works as it should.
:-(
EDIT:
I didn't realize that window7's tool would install the cwm into the boot-partition instead of the recovery-partition.
To get my boot partition back I downloaded the 2.3.4 firmware image from http://forum.xda-developers.com/showthread.php?t=1056062 and extracted the boot.img from the zip.
with "fastboot flash boot boot.img" I restored my orginal boot partition an can boot into android again.
(fastboot is part of the android sdk)
I'm trying to install jelly bean on my kindle fire but using KFU I've only managed firefirefire and clockworkrecovery.
I tried rooting using KFU to root but that doesn't work. Always gets stuck with the twrp.img error saying it's the wrong image (seems to be a common problem)
I've tried getting twrp installed using adb shell but when I get to the command to load the recovery image I get error; couldn't load recovery image. I thought maybe there was a problem so I tried loading the fff bootloader even though I already had it on my kf but it also returned with error: couldn't load image.
Theoretically, if you have clockwork recovery, there is no need for TWRP. But if you must have TWRP instead, use clockwork to flash a rom (and FFF1.4 while you're at it). Boot into the rom and use the Smirkit to install TWRP. It will save you a lot of hassle.
soupmagnet said:
Theoretically, if you have clockwork recovery, there is no need for TWRP. But if you must have TWRP instead, use clockwork to flash a rom (and FFF1.4 while you're at it). Boot into the rom and use the Smirkit to install TWRP. It will save you a lot of hassle.
Click to expand...
Click to collapse
The problem is getting root access. Most of the guides I've tried to follow require twrp installed to get into recovery. Without root I can't flash another rom.
I also already have FFF 1.4.
So I reverted back to stock and went through the manual process again and I was able to get it to work. When I was initially trying to flash twrp with the command line I copied pasted the name of the file without adding the file extension. Fixed that by adding .img and everything went through. Got Jellybean on here now and it's running great.
If you are installing a custom rom (including MoDaCo), there is no need to go through the "rooting" process, hence saving you "a lot of hassle". Recoveries, like CWM and TWRP provide temporary root access.
soupmagnet said:
If you are installing a custom rom (including MoDaCo), there is no need to go through the "rooting" process, hence saving you "a lot of hassle". Recoveries, like CWM and TWRP provide temporary root access.
Click to expand...
Click to collapse
This is odd because I tried installing the JB rom after I got CWM on there. It booted up to a black screen and left it there for 5 minutes and still black screen. I reverted back with the update bin from amazon website after that.
hxu976 said:
This is odd because I tried installing the JB rom after I got CWM on there. It booted up to a black screen and left it there for 5 minutes and still black screen. I reverted back with the update bin from amazon website after that.
Click to expand...
Click to collapse
That has nothing to do with "rooting". Most of the time it's caused by a bad download (always check MD5s) or not "wiping" correctly before installation.
This is a pretty specific question and i'm not sure this is the correct place to ask this but i recently installed the stock rom (Via Zip) on this thread: http://forum.xda-developers.com/showthread.php?t=2527806 . I flashed just the rom NOT including the bootloader (Because i don't know what it does) and the .97 radio because there seems to be some issues with it. Now, everything is working perfectly as it did before. What i'm wondering is after today's random new 4.4 factory image and ota update from Google (I think its krt16s); i know they are probably going to compile a flashable zip, and if they do what exactly do i need to do?
I'm extremely weary when i do these kind of things, the last time i flashed any sort of rom was on my OG RAZR. Would i have to install that new bootloader? (Also what exactly does it do) And would i have to wipe?
I can make the radio judgement on my own but i'm just not entirely sure.
If anyone could answer my questions that would be wonderful, i'm also sorry for posting this here, i'm not allowed to post in that thread because i'm "new" to the site.
Thanks!
you dont have to sorry as you are in the right section for asking questions.
You can either wait for a day or two for someone to post a flashable zip file. If someone do post it; all you have to do is copy it to your phone. Reboot to recovery mode; make sure you have cwm recovery installed. From there choose "install zip" > install zip from sdcard, choose the flashable zip. Once it finishes installing, clear cache partition and reboot. You will not lose anything in the phone.
If you want to install the new krt16s stock update. First, copy all of your files (pictures/music/data etc...) to your computer. This will wipeout everything. Download the image file. Open it with winrar or 7zip. Extract all the files to a folder. Connect your phone to the computer and reboot it to bootloader. Run the "flash-all.bat" file from the extracted files. Wait for it to finish. It will update everything (kernel, bootloader and the new 4.4)
You should know what something is before flashing them wildly, that's the easiest way for people to brick their phone by flashing something incompatible with their devices. Bootloader is the main program that boot first when you turn on to phone to make selftest and boot normally into the operating system kernel, with Nexus you can use it boot into recovery and flash images to partitions as well. It's very recommended to update it along with new Android version or you may run into issues. You should already know this since you had to access the bootloader screen to boot into the CWM recovery.
Stick with using CWM for now and flash the flashable zips. Just make a full backup of your device you can always restore it later. Just know that unless you flash radio separately (aka baseband), roms generally and should not come prepackaged with the baseband, so it is not affected when you flash a different rom, you have to upgrade it manually.
When you flash a new Android version, usually its recommended to do a factory reset in your recovery to avoid issues.
Installing factory image takes a few more steps and required using fastboot, but if you want to check the link in my sig. Also I recommend switching to TWRP recovery, but that's just me.
badboy47 said:
you dont have to sorry as you are in the right section for asking questions.
You can either wait for a day or two for someone to post a flashable zip file. If someone do post it; all you have to do is copy it to your phone. Reboot to recovery mode; make sure you have cwm recovery installed. From there choose "install zip" > install zip from sdcard, choose the flashable zip. Once it finishes installing, clear cache partition and reboot. You will not lose anything in the phone.
If you want to install the new krt16s stock update. First, copy all of your files (pictures/music/data etc...) to your computer. This will wipeout everything. Download the image file. Open it with winrar or 7zip. Extract all the files to a folder. Connect your phone to the computer and reboot it to bootloader. Run the "flash-all.bat" file from the extracted files. Wait for it to finish. It will update everything (kernel, bootloader and the new 4.4)
Click to expand...
Click to collapse
I see, me personally, I'm not very fond of using adb; I haven't used it at all prior to yesterday. I may try this out, but should someone post the new kernel, boot loader, 4.4 and radios would that be the same as flashing the factory image?
This probably seems like a really stupid question but I wouldn't be smart to try to download the ota directly from the phone (via check for updates) would it?
joshvader8 said:
I see, me personally, I'm not very fond of using adb; I haven't used it at all prior to yesterday. I may try this out, but should someone post the new kernel, boot loader, 4.4 and radios would that be the same as flashing the factory image?
This probably seems like a really stupid question but I wouldn't be smart to try to download the ota directly from the phone (via check for updates) would it?
Click to expand...
Click to collapse
You need to learn to use adb and fastboot if you want to be able to do advance things with the phones, or just avoid flashing too much, because once you run into trouble (especially due to using toolkits), you will not know how to recover your device.
If you want your device to be stock and able to receive OTA updates, in addition you also need your stock rom to be an "odexed" version, some roms are "deodexed" which will not receive OTA. You also need to have stock recovery, which CWM isn't.
eksasol said:
You need to learn to use adb and fastboot if you want to be able to do advance things with the phones, or just avoid flashing too much, because once you run into trouble (especially due to using toolkits), you will not know how to recover your device.
If you want your device to be stock and able to receive OTA updates, in addition you also need your stock rom to be an "odexed" version, some roms are "deodexed" which will not receive OTA. You also need to have stock recovery, which CWM isn't.
Click to expand...
Click to collapse
Thank you! One more question, let's say I revert back to my nandroid back up. I backed my ROM up on Android 4.3 rooted and unlocked with CWM. If I flashed the 4.4 factory i image what exactly would happen? Would I boot into 4.4 absolutely stock? Or would I end up with 4.4 unlocked etc...?
Thank you for the help I really appreciate it. ☺
joshvader8 said:
Thank you! One more question, let's say I revert back to my nandroid back up. I backed my ROM up on Android 4.3 rooted and unlocked with CWM. If I flashed the 4.4 factory i image what exactly would happen? Would I boot into 4.4 absolutely stock? Or would I end up with 4.4 unlocked etc...?
Thank you for the help I really appreciate it. ☺
Click to expand...
Click to collapse
When you flash factory image (using fastboot method), it will wipe your entire device and all user data, and you will boot into stock. Except if you do it manually you can prevent datas from wiping, follow these steps and pay attention to the red texts.
Sometimes apps data from older version can cause issues with newer version though, so a clean install is always best.
But if you have custom recovery, you can flashable stock roms, such as this one by fireb33, it's essentially the same as stock. Get the "odexed" version which is required to get OTA updates. Some peolpe say they can get OTA with custom recovery, but I have never tried that. The safest bet is to use fastboot to restore to stock recovery. You could also use custom recovery to flash OTA update packages to update versions that way.
As for backing up, people tends to call the backup "nandroids". After you do backup, if you're doing something that required the device to be wiped, you need to copy the backup to your pc. The CWM nandroids are usually located in 'clockworkmod' folder, but if you don't see it, search in "/data/media". I do not use CWM so I don't know what it allows you to back up, but generally "boot" (which is the kernel), system, and data partitions. It will not restore everything to stock such as your radio (baseband) or recovery.
I highly recommend switching to TWRP recovery, it will make flashing a lot easier.
All,
Thanks in advance for any help you can provide. I have a Nexus 4 that I rooted and installed CWM recovery on, but I never installed any new kernels, ROMs, or radios. I'm currently on 4.4.4 and I want to upgrade to Lollipop. The OTA upgrade failed. So I tried returning to stock recovery and doing both the OTA and adb sideloading the OTA zip. Both fail.
The error message is "Package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or google/occam/mako:5.0/LRX21T/1576899:user/release-keys; this device has google/occam/mako:4.4/KRT160/907817:user/release-keys." (But I definitely have 4.4.4 on my phone, not 4.4.0.)
The extra difficulty is that I really, really do not want to wipe my phone. I have a lot of apps with a lot of configuration and other user data. So is there anything I can do? I guess I should try unrooting somehow? Or is there some other zip I can download that, through some type of recovery, will install the OTA without doing this check and also without wiping me?
Thanks again!
moriarty00 said:
All,
Thanks in advance for any help you can provide. I have a Nexus 4 that I rooted and installed CWM recovery on, but I never installed any new kernels, ROMs, or radios. I'm currently on 4.4.4 and I want to upgrade to Lollipop. The OTA upgrade failed. So I tried returning to stock recovery and doing both the OTA and adb sideloading the OTA zip. Both fail.
The error message is "Package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or google/occam/mako:5.0/LRX21T/1576899:user/release-keys; this device has google/occam/mako:4.4/KRT160/907817:user/release-keys." (But I definitely have 4.4.4 on my phone, not 4.4.0.)
The extra difficulty is that I really, really do not want to wipe my phone. I have a lot of apps with a lot of configuration and other user data. So is there anything I can do? I guess I should try unrooting somehow? Or is there some other zip I can download that, through some type of recovery, will install the OTA without doing this check and also without wiping me?
Thanks again!
Click to expand...
Click to collapse
OTA wants complete stock and obviously it doesn't think so about your phone. One option could be to back up to the cloud or some place outside the phone with TiBu (or whatever backup app you trust), then flash lollipop and try restore from TiBu. Another option would be to unroot (Supersu has an option to completely unroot), then retry.
Actually, I figured out what works! This was on a stock rooted device with stock recovery, but I bet it would work with custom recovery too. Instructions modified from https://pay.reddit.com/r/nexus4/comments/1qny3f/howto_update_your_stock_w_lte_nexus_4_without/ .
1. Download the image you want from https://developers.google.com/android/nexus/images . Extract it, extract the .zip file inside it too, and collect all of the .img files into one folder.
2. adb reboot bootloader (and wait until the bootloader comes up)
3. fastboot flash bootloader bootloader-mako-makoz30f.img (or whatever file has a similar name, if you got a different image than I did)
4. fastboot reboot-bootloader (and wait until the bootloader comes back up)
5. fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.04.img (or whatever file has a similar name, if you got a different image than I did)
6. fastboot reboot-bootloader (and wait until the bootloader comes back up)
7. fastboot flash boot boot.img
8. fastboot flash recovery recovery.img
9. fastboot flash system system.img
10. fastboot format cache
11. fastboot reboot
12. Don't panic unless you've seen the startup animation for at least 15 minutes without anything else happening.
I lost root, but I imagine re-custom-recoverying and re-rooting won't be any harder than the first time around.
Hi moriarty00,
I'm going to try the same procedure, thank you for posting this.
Can you confirm that your data and app are safe after the upgrade?
moriarty00 said:
Actually, I figured out what works! This was on a stock rooted device with stock recovery, but I bet it would work with custom recovery too. Instructions modified from https://pay.reddit.com/r/nexus4/comments/1qny3f/howto_update_your_stock_w_lte_nexus_4_without/ .
1. Download the image you want from https://developers.google.com/android/nexus/images . Extract it, extract the .zip file inside it too, and collect all of the .img files into one folder.
2. adb reboot bootloader (and wait until the bootloader comes up)
3. fastboot flash bootloader bootloader-mako-makoz30f.img (or whatever file has a similar name, if you got a different image than I did)
4. fastboot reboot-bootloader (and wait until the bootloader comes back up)
5. fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.04.img (or whatever file has a similar name, if you got a different image than I did)
6. fastboot reboot-bootloader (and wait until the bootloader comes back up)
7. fastboot flash boot boot.img
8. fastboot flash recovery recovery.img
9. fastboot flash system system.img
10. fastboot format cache
11. fastboot reboot
12. Don't panic unless you've seen the startup animation for at least 15 minutes without anything else happening.
I lost root, but I imagine re-custom-recoverying and re-rooting won't be any harder than the first time around.
Click to expand...
Click to collapse
Wow, a 12-step program
I simply rolled back my changes, and applying the OTA was as simple as pressing the "restart and install" button Here are some steps:
I used the app Flashify from Play Store to flash stock 4.4.4 recovery. I downloaded the stock factory image from google's own site (this one), used 7zip to extract the archives (tgz and tar), found "recovery.img" and transfered that to my phone. Then chose that file in Flashify.
Uninstalled all apps that made system changes, like Xposed framework and mods, BetterBatteryStats etc.
Removed Root with SuperSU cleanup function
Rebooted for good measure and apply OTA from notification - wait an hour or two for it to complete
Profit (do we still say that on the internet? Getting old here...)
I don't know if certain ways to get root will break the OTA. I used towel-root, and apparently SuperSU was able to undo that completely.
DrDruge said:
Hi moriarty00,
I'm going to try the same procedure, thank you for posting this.
Can you confirm that your data and app are safe after the upgrade?
Click to expand...
Click to collapse
Yup, perfectly safe! Just make sure not to flash other images, like userdata.img.
venu123 said:
OTA wants complete stock and obviously it doesn't think so about your phone. One option could be to back up to the cloud or some place outside the phone with TiBu (or whatever backup app you trust), then flash lollipop and try restore from TiBu. Another option would be to unroot (Supersu has an option to completely unroot), then retry.
Click to expand...
Click to collapse
If I unroot with Supersu how do I get root back?
moriarty00 said:
Yup, perfectly safe! Just make sure not to flash other images, like userdata.img.
Click to expand...
Click to collapse
Thank you!
Unfortunately the steps did not work for me, maybe I had some irreversible modifications or I had followed a different rooting procedure.
Or maybe I made a mistake in the upgrading steps.
Anyway, I had to flash the whole ROM and now everything is working fine.
Hey!
Basically I have similar problem with upgrading from 4.4.4 to 5.0 using OTA. Log from TWRP says:
Package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or google/occam/mako:5.0/LRX21T/1576899:user/release-keys; this device has google/occam/mako:4.3/JWR66V/737497:user/release-keys.
Click to expand...
Click to collapse
Phone has been rooted using Nexus Root Toolkit. And as long as there wouldn't be a problem with flashing using adb and wiping all data, there is one setback... My nexus is somehow broken. Communication via USB does not work, at all. Neither phone nor PC sees other device. Certified LG service centre nearby said that it is problem with main board, so generally repair is unprofitable.
So question is: How do I update to 5.0 and then root, without USB connection to my PC?