Related
Hi guys.
I know that the various aspects of this post are covered in other posts, but I haven't seen anything that acts like a step by step or repository for this info.
Basically, I have a VodafoneAU HTC Magic with 1.5 on it, and I'd like to flash on it one of the Hero roms. I used to have a Diamond and then Diamond Pro, but I know little about Android at this point.
My biggest fear is bricking the phone, followed by not being able to restore my previous rom (and even apps and settings would be awesome too, though not essential) should something go pear shaped.
I know the steps I need to follow are:
1 - Root the phone
2 - Back up ROM (settings/apps too?)
3 - Flash new ROM
4 - ?????
5 - Profit (in the form of enjoying an awesome Hero ROM)
Jokes aside, if someone can point me in the right direction for the first 3 steps, that'd be great. Even if it's as simple as
1 - Root it using this post (link)
2 - Use this App to back it up
3 - etc..
Like I said, I know this info is probably covered elsewhere, but not in one place (that I've found) and I'd hope this post could serve as a guide for anyone else looking to go the same steps as me.
Thanks for any help anyone can give.
Cheers.
First off, you don't need to root your phone, update the SPL, or any of that scary stuff. Which is great, cus that's the riskiest part of it all. Briefly, the procedure is as follows:
1. Boot your phone in fastboot mode (power the phone off, then hold the back button as you power it back on). You'll see a white screen with some text, the word "FASTBOOT" and some androids at the bottom.
2. Note the version numbers you see at the top of the screen - it'll look something like:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.3300.0009 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
3. Download the ROM you want to upgrade to for your phone's version, rename the zip to update.zip and put it on the root of your phone's SD card
4. Boot a recovery ROM using fastboot (from the Android SDK)
5. Use Nandroid Backup to back up your current firmware to the SD card
6. Copy that backup (and the rest of the contents of your SD card) to your PC, just in case. This is the last point at which you can back out!
7. Use the recovery ROM to wipe your phone's existing firmware
8. Use the recovery ROM to apply the update.zip from the SD card
9. Wait for the update to complete
10. Reboot your phone and enjoy your new ROM!
I did this on my Vodafone NZ HTC Magic (PVT32B) running 1.5 yesterday and am enjoying Hero on it right now, barring a few quirks. If you like, I'll put together a detailed step-by-step of the procedure.
KarrdeNZ said:
First off, you don't need to root your phone....
I did this on my Vodafone NZ HTC Magic (PVT32B) running 1.5 yesterday and am enjoying Hero on it right now, barring a few quirks. If you like, I'll put together a detailed step-by-step of the procedure.
Click to expand...
Click to collapse
Awesome, cheers. I'll have a crack at it tonight then.
So Am I correct then in assuming step 5 backs up my phone as it is now? So essentially if I roll back it will be exactly as it was? Installed apps, settings, contacts (although sync sorts that out) and all?
papalazarou said:
So Am I correct then in assuming step 5 backs up my phone as it is now? So essentially if I roll back it will be exactly as it was? Installed apps, settings, contacts (although sync sorts that out) and all?
Click to expand...
Click to collapse
Nope. Nandroid only backs up the existing firmware (and I believe some settings). It doesn't back up texts, contacts (though those should be synced with your Google Account anyway), or apps. For the most part, apps are easy to retrieve from the Market, but if you have any you got from elsewhere you'll need to reacquire them. The app MyBackup Pro seems to be recommended on these forums for more thorough backups, though it isn't free (and I've not used it myself). As my phone was (relatively) new I wasn't too fussed about keeping backups of anything except the firmware.
I've done a couple of Nandroid backups and restores and it restores everything (except SD card), meaning applications, settings, everything is restored.
Also, I highly recommend RAv's recovery (http://forum.xda-developers.com/showthread.php?t=530492). Use it to make your Nandroid backup .
Wysie said:
I've done a couple of Nandroid backups and restores and it restores everything (except SD card), meaning applications, settings, everything is restored.
Click to expand...
Click to collapse
I've heard differing reports on what Nandroid does and doesn't back up, so was erring on the side of caution. But if it backs up everything, awesome.
And yep, that's the recovery ROM I used. I'm writing up the step by step instructions at the moment - will post em when they're done.
KarrdeNZ said:
I've heard differing reports on what Nandroid does and doesn't back up, so was erring on the side of caution. But if it backs up everything, awesome.
And yep, that's the recovery ROM I used. I'm writing up the step by step instructions at the moment - will post em when they're done.
Click to expand...
Click to collapse
depends how you restore it- you can restore system.img only and not get all your data etc (using fastboot) but if you fastboot data.img as well then you get it all..... the new recovery restores it all...
KarrdeNZ said:
First off, you don't need to root your phone, update the SPL, or any of that scary stuff. Which is great, cus that's the riskiest part of it all. Briefly, the procedure is as follows:
1. Boot your phone in fastboot mode (power the phone off, then hold the back button as you power it back on). You'll see a white screen with some text, the word "FASTBOOT" and some androids at the bottom.
2. Note the version numbers you see at the top of the screen - it'll look something like:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.3300.0009 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
3. Download the ROM you want to upgrade to for your phone's version, rename the zip to update.zip and put it on the root of your phone's SD card
4. Boot a recovery ROM using fastboot (from the Android SDK)
5. Use Nandroid Backup to back up your current firmware to the SD card
6. Copy that backup (and the rest of the contents of your SD card) to your PC, just in case. This is the last point at which you can back out!
7. Use the recovery ROM to wipe your phone's existing firmware
8. Use the recovery ROM to apply the update.zip from the SD card
9. Wait for the update to complete
10. Reboot your phone and enjoy your new ROM!
I did this on my Vodafone NZ HTC Magic (PVT32B) running 1.5 yesterday and am enjoying Hero on it right now, barring a few quirks. If you like, I'll put together a detailed step-by-step of the procedure.
Click to expand...
Click to collapse
I am a noob...Why don't need to FLASH SPL and ROOT the phone?? But u can still flash into HERO rom. I would like to have a full flash procedure from you,thanks. My machine is running on PVT32A.
snowhk said:
I am a noob...Why don't need to FLASH SPL and ROOT the phone?? But u can still flash into HERO rom.
Click to expand...
Click to collapse
You can load the Hero ROM without replacing your SPL (in most cases) or rooting, so why replace it if you don't need to? I've done it myself without doing so and it's working fine.
My guide is now ready - check it out at http://www.karrderized.com/romguide/.
KarrdeNZ said:
You can load the Hero ROM without replacing your SPL (in most cases) or rooting, so why replace it if you don't need to? I've done it myself without doing so and it's working fine.
My guide is now ready - check it out at http://www.karrderized.com/romguide/.
Click to expand...
Click to collapse
Just ask for curiosity..But why did others do so?? Thanks. You provided a clear guide.^^
snowhk said:
Just ask for curiosity..But why did others do so?? Thanks. You provided a clear guide.^^
Click to expand...
Click to collapse
I think some SPL versions prevent ROM updates and so need to be replaced with versions that do, but I'm not sure. I'll let someone more knowledgeable take that question.
And thanks, I tried to make the guide as easy as possible
KarrdeNZ said:
I think some SPL versions prevent ROM updates and so need to be replaced with versions that do, but I'm not sure. I'll let someone more knowledgeable take that question.
And thanks, I tried to make the guide as easy as possible
Click to expand...
Click to collapse
My device shows the followings:
Sapphire PVT 32A Ship S-ON H
HBOOT-1.33.0009(SAPP10000)
CPLD-12
RADIO-3.22.20.17
Would my SPL version prevent the update?Coz I afraid of bricking my phone>< I got too many questions. Hope u can have a help. Thanks.
snowhk said:
My device shows the followings:
Sapphire PVT 32A Ship S-ON H
HBOOT-1.33.0009(SAPP10000)
CPLD-12
RADIO-3.22.20.17
Would my SPL version prevent the update?Coz I afraid of bricking my phone>< I got too many questions. Hope u can have a help. Thanks.
Click to expand...
Click to collapse
According to http://forum.xda-developers.com/showthread.php?t=529019 you should be fine. If you're unable to boot the recovery ROM (step 8 in my guide) then stop there, as I believe that's about where problematic SPLs first show signs of trouble. Just make sure you get ROMS for 32A.
KarrdeNZ, thanks for your fantastic guide! Are you OK to put it up as a stick thread within this forum?
i believe you can only do this with signed roms but this is only from what i have read on here, but to be fair its not hard to root anyway and aslong as your not a dumbass its pretty straight forward and can benefit from bluetooth file sharing and apps2sd and tethering so deffo worth it, opens up your phone to numerous possibilities
eva_d said:
KarrdeNZ, thanks for your fantastic guide! Are you OK to put it up as a stick thread within this forum?
Click to expand...
Click to collapse
Sure, not a problem I'd prefer the thread link to the guide so that new versions are easy to find, but whatever works.
KarrdeNZ, mate I followed your guide to the letter. I got all the way down to step 11 and then a problem occurred.
When I clicked 'Apply sdcard:update.zip' it just said cannot find or cannot load update.zip, or something like that, then said operation aborted?
I was trying to install the EXACT same ROM as you, I downloaded it to my laptop, renamed it update.zip and moved it to the root of the SD card.
Yet it didn't work, I can't for the life of me think where it's gone wrong as everything else up to that point had gone smoothly.
Any idea's?
Well I tried downloading the same file again. No luck this time either!
This is what it says when I click the install from sdcard button:
--install from sdcard...
Finding update package...
Opening update package...
E: Can't open /sdcard/update.zip
(no such file or directory)
Installation aborted.
Now I get that it's saying that it can't find the file but I really don't understand why? I mean the file is there, do I have to unzip the file onto my computer 1st and then put it on the sdcard?
I thought i just stuck the zipped file onto the root of the card making sure i renamed it 'update.zip'
Please help me out guys, thanks.
The exact thing happened to me; and I realized I was dumb and had named the file "update.zip", when in fact it should just be "update". The file extension should come naturally since the file is still compressed.
Roy_Drage said:
Well I tried downloading the same file again. No luck this time either!
This is what it says when I click the install from sdcard button:
--install from sdcard...
Finding update package...
Opening update package...
E: Can't open /sdcard/update.zip
(no such file or directory)
Installation aborted.
Now I get that it's saying that it can't find the file but I really don't understand why? I mean the file is there, do I have to unzip the file onto my computer 1st and then put it on the sdcard?
I thought i just stuck the zipped file onto the root of the card making sure i renamed it 'update.zip'
Please help me out guys, thanks.
Click to expand...
Click to collapse
KarredeNZ, THANK YOU for your awesome tutorial!! I looked through so many other pages for instructions and they went totally over my head. Your tutorial was the best and easiest to follow.
I can be contacted here: [email protected]
Anyone able to help with Root ? I picked up a link in a HTC thread on Whirlpool
http://forum.xda-developers.com/show....php?t=1192300
got as far as S Off (Security Off), Updated Clockwork Recovery mod- v4.0.1.4, Now I am stuck on To permanently root your Sensation part 3. When trying to update: When I go to flash clock work/Revolutionary it says: (bad) Can't open Install aborted, though that said some users are having this error and the root is still successful according to XDA however for me I got Root check off the Market and it returns a failed result on Basic and some times a pass on Advanced but some times not. Busybox,Super user,Titanium back up are all saying I'm not rooted to don't have Root permissions.
Have a look at the link below it contains 4 photos of my sensations screen as I went through the process it will no doubt give you a better idea of my problem. It's a link to my blog BTW. Any help would be greatly appreciated. I am not a member of XDA so thought I would try my luck here before having to create yet another account somewhere Thank You.
Best look at the photos from bottom to top as they uploaded back to front, order of process is bottom to top.
http://mathewmurrayharrison.blogspot...sensation.html
Phenomenal MATT writes...
Anyone able to help with Root ? I picked up a link in a HTC thread on Whirlpool
So did you download this http://forum.xda-developers.com/atta...8&d=1311991644 file and flashed it via recovery?
I have S-OFF and I flashed that file I have full root. I then used ROM Manager to flash clockworkmod (CWM) because ROM Manager doesn't see the recovery that came with the S-OFF.
I just backed up my Telstra ROM. It just finished a minute ago.
Yes I did flash that via Recovery inc. the old su-2.3.6.1-ef-signed.zip AND the new su-2.3.6.3-efgh-signed.zip.version I've tried the other couple of suggested methods on that link I posted and nothing seems to be working. Sadly can't see were I have gone wrong.
Here is a link to another two photos with the error message I am getting.
http://mathewmurrayharrison.blogspot...blog-post.html
Phenomenal MATT writes...
Yes I did flash that via Recovery inc. the old su-2.3.6.1-ef-signed.zip
Did you install ROM Manager? I installed ROM Manager and used that to flash CWM and all is working fine here.
EDIT:
My bad. You did say you can't get full root. Don't really know why it won't work for you. Mine worked first go.
Phenomenal MATT
Yeah I have Rom manager but I can't do anything with it everything returns an error.
Phenomenal MATT writes...
Yeah I have Rom manager but I can't do anything with it everything returns an error.
I just figured that out, my bad. I understand that rooting doesn't stick.
Phenomenal MATT
Sounds like you were one of the lucky ones cause if you read the comments after the steps many people are have minor issues. I'm ashamed to say I've being at it all day VERY FRUSTRATING !!!
Yes I put the ZIP file into 'The Root' of the SD card (Main section of SD Card) and yes in recovery I can see that zip file but when I click open it says:
Can't open /sdcrd/su2.3.6.3-efgh-signed.zip
(bad)
Installation aborted.
I've tried over 30 times same thing every single time. HEADACHES !!! lol
Sooo looking forward to a solution. I might have to creat a XDA account and post it in the questions section there, looks as though questions are getting answered pretty quick (Good support) ...WITH ALL THAT SAID IF ANYONE HERE CAN HELP I WOULD BE MOST GRATEFUL.
Phenomenal MATT writes...
Can't open /sdcrd/su2.3.6.3-efgh-signed.zip
(bad)
Installation aborted.
You've probably already tried this, but if not, have you downloaded the su zip again? could it be corrupt?
EDIT: I am really new to Android. Got my phone the day it came to Telstra. You are probably better off on the XDA forums.
Phenomenal MATT
I signed up for XDA but they expect you to make 10 posts elsewhere on their forum before allowing you to comment on the Sensation Dev. one (The comments under the instructions in this link:
http://forum.xda-developers.com/show....php?t=1192300
Yeah I downloaded it on PC, Mac, Mac with Boot camp, Zipped, un Zipped and even tried the old Zip file it says to try in trouble shouting section then followed buy the new Zip file.
Awwwww Well Patients a vertue ... Hopefully it's all worth it.
Seems like the guy already gave you your answer. Just download the zip again. You probably have a corrupted download. And make sure that signature verification is off in recovery. Should work.
I've downloaded over 30 times on 3 different computers + straight to Sensation as a hard Disk tried Zipped, unzipped you name it... PC - Mac Normal sd card, Micro SD card... & Also like to add Sign. verify is off too tried it on and off, I a award the file needs to be zipped and that needs to be off just trying everything here pulling my hair out.
Do You go CWM > Advance . backup ur Rom ?
I'm using rev. And I go to backup and restore click on back up after its complete 10 minutes later I go and try to get the zipped file but it fails every time.
Sent from my HTC Sensation Z710a using XDA App
Finally got it to work. I had to download it from the net with my phone to download folder as opposed to with a pc then moving it to main root folder on SD card. Question is now what ? I want to over clock but I want to keep sense. Do all Roms remove sense ? Leedroid ? What else is recommended now I'm rooted. Btw thanks again everyone for your help.
Sent from my HTC Sensation Z710a using XDA App
Thanks Matt
Thanks for posting this, Phenomenal Matt. I had the EXACT same problem that you posted about. Copying the su zip file to my phone's sdcard while the phone was mounted as a drive did not work at all. I had to download the su zip file on my phone before Clockwork Recovery was able to successfully install it and give me root.
Hi,
I checked through many threads to see if anyone had a similar problem but couldn't find anything unfortunately.
Background :
I was running a Lite'ning ROM on my Samsung Galaxy S2. You're probably familiar with this ROM, but for those who aren't it gets flashed with ODIN and comes rooted and pre-installed with CWM.
I forget which version of Lite'ning ROM it was, but I am fairly certain it was pre-1.5 as the bundled CWM was definitely version 3.x.x.x (later versions I found had 4.x.x.x and 5.x.x.x).
I wanted to try a version of GalnetMIUI for something a bit different and hadn't changed ROMs in quite some time, so I booted into CWM 3.x.x.x (maybe 3.0.0.2?) and did a backup to the internal SD. This came in at around 1.4 GB and comprised of 4 files :
cache.img
data.img
nandroid.md5
system.img
I copied these to my PC too, just in case they somehow got erased from my phone.
Once I'd done this, I then copied the new ROM .zip file (latest version of GalnetMIUI) to the root of the internal SD, booted the phone into CWM, wiped user data and Dalvik cache, then proceeded to install it.
The problem :
I can't get my apps or data back. I was under the false impression that my Google account was automatically backing this up for me, and would restore everything once logged in as it had in the past (factory resets etc.). So once this didn't happen, I tried using CWM to revert back to how things were before installing the new ROM but although the restore appears to work I end up with issues.
I've tried a number of different ROMs and they either get stuck in 'boot loops' or a black screen after running through the restore procedure. I've tried restoring just data via the 'Advanced' option but this doesn't help.
I was under the impression that I'd be able to fully restore the ROM backup if I needed to, and have the phone running exactly how it was prior to messing around. It would seem this is not the case.
In desperation I tried flashing every Lite'ning ROM from version 1.0 to 4.2, restoring my backup each time but as mentioned I always get boot issues.
Have I lost my data? I hope not, as I had 'To Do' lists and all sorts of things that would cause problems if they were not retrievable. I realise this is a lack of knowledge and foresight on my part. I'm thinking now that I should have run Titanium Backup prior to this, and not assumed that CWM was going to provide a complete solution.
Hope all this makes sense and if any of you have the time to read through and offer advice it would be greatly appreciated. I am currently running a very pretty and slick GalnetMIUI without any of my data!
Thanks in advance.
download cwm 2.5.x.x its better
[email protected] said:
download cwm 2.5.x.x its better
Click to expand...
Click to collapse
Thanks for that, I'll give it a go tonight after work. Am I right in thinking that if it doesn't work I can extract the individual files and insert them manually to get my app data back?
OK, so after hours of searching I'm still no wiser as to how to install CWM 2.5.1.2
I found a zip file that was apparently version 2.5.1.2 but when I tried to install it from inside CWM 5.0.2.6 (included with GalnetMIUI) it sometimes gives an error, sometimes it reboots CWM and sometimes it simply says it has successfully installed (it lies). No matter what it says or does, it doesn't seem to actually replace version 5.0.2.6 with the older one and every time I do the three-finger boot it loads up the latest version like nothing changed.
I'm just so lost. All I want to do is restore my old backup, get my data back and move on. Please someone help me before I go insane from all this research!
[EDIT] In case any more information is needed, my exact procedure for installing version 2.5.1.2 of CWM went like this :
Download 2.5.1.2 zip file
Copy zip file to root folder on internal SD
Boot into CWM 5.0.2.6
Select "install zip from sdcard"
Select "choose zip from sdcard"
Navigate to 2.5.1.2 zip file, select and confirm
Can anyone help me at all?
In particular I'd like to know how I can downgrade to CWM 2.5.1.2 or similar in order to give [email protected]'s suggestion a go.
Failing that, if anyone has any suggestions whatsoever about how I can get my backup data restored it would be greatly appreciated. After spending some time with MIUI - in particular the Galnet ICS build - I have nothing but praise, but I really have to get my data back!
You should be able to downgrade through ROM manager. Go to "All Clockwork Mod Recoveries" and just flash one that is not 5.x.x. Any backup not made with version 5 will not work with the new version So if you can flash one that is version 2, 3 or 4 you should be good to go. If that doesn't work you can fastboot flash it. There are guides on how to do that.
Wait.....did you mount /system before installing the CWM zip ?
Sent from my GT-S5830 using XDA App
Sorry for the delayed reply, for some reason I didn't get an email notification that my thread had been updated.
lowandbehold said:
You should be able to downgrade through ROM manager. Go to "All Clockwork Mod Recoveries" and just flash one that is not 5.x.x. Any backup not made with version 5 will not work with the new version So if you can flash one that is version 2, 3 or 4 you should be good to go. If that doesn't work you can fastboot flash it. There are guides on how to do that.
Click to expand...
Click to collapse
For some reason, when I select "All ClockworkMod Recoveries" the only two options are 4.0.1.4 and v4.0.1.4. I'll have to look into "fastboot" flashing as I've never heard of that.
By the way, if I boot into CWM via ROM Manager the version that loads is 4.0.1.5, but if I perform the three-button combo when switching my device on I get version 5.0.2.6.
EmoBoiix3 said:
Wait.....did you mount /system before installing the CWM zip ?
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
I didn't, is that something I should try?
Edit - Just tried this and at first it rebooted CWM and the version number hadn't changed. Doing this again yielded me the following error with no change in version number :
Code:
E:Error in /sdcard/CM V 2.5.1.2_update.zip
(Status 0)
Installation aborted.
I found out that I can extract the contents of my backed up .img files using unyaffs.exe.
Unless I'm doing something wrong, it would appear that my backup is corrupt somehow. When trying to extract data.img, it processes for a while and does bring back a lot of files but I also get the following :
Code:
read image file
: Bad file descriptor
read image file
: Bad file descriptor
data.img is around 1.2GB but the files I extract only amount to around 190MB.
It would appear that I don't have my contacts database in there which is annoying as for some reason there were quite a few that didn't get synced to Google's servers.
Make sure you are using CWM version 6.0.1.0
I am not responsible for whatever happens to your device because everyone else puts this in their threads too! get over it
Be sure to click that Thanks button if this helped you. this also appears in everyone else's thread's! deal with it
1. download the update file for your region from paugustin's thread here:
http://forum.xda-developers.com/showthread.php?t=1720157
2. unzip it inside any folder.
3. open the file called updater-script which is located at:
/META-INF/com/google/android
4. delete the line and the blank space left afterwards then save changes to the file. the line for the US version looks like this:
assert(getprop("ro.product.name") == "a700_pa_cus1");
5. highlight everything that came out of the download from step 1, zip it, and rename it to update.zip
6. place in the root of an SD card, not internal storage!
Note: a few users have recommended placing the update.zip on internal storage. i tried it again from a SD card and it worked just fine. if you're having issues with this try internal.
7. reboot to recovery mode. if you need this guide you've had to do it in the past, nuff said! :silly:
8. select Apply update.zip
9. after you select Reboot System, you will be given two options:
Yes will keep CWM recovery but you wont be able to use recovery mode at all until you unlock the bootloader again!
No will allow the update to restore stock recovery, and you will need to re-flash CWM.
10. if you chose Yes from step 9, unlock your bootloader and do the root process again. DONE!
if you chose No, unlock your bootloader, flash CWM again, and do the root process again. DONE!
there are already guides on how to do that.
BONUS FOR USA TAB OWNERS!
This is ONLY FOR UPDATING FROM the Acer_A700_AV043.RV00RC00_AV043.RV07RC06_PA_CUS1.zip file from the link in Step 1 at the top of the page.
If you are on any other version, and / or from any other country, DO NOT TRY THIS!
This is the latest update with the power option added in settings & touch sensitivity improvements, with the getprop line already deleted from the script!
A. Download this directly to your tab.
B. Reboot to recovery mode.
C. Install.
D. After selecting Reboot System you will be given two options. Refer to Step 9 above.
E. After making your choice, you will be given the option to prevent the update from deleting root :victory:
F. Unlock your bootloader again.
G. If you chose No. from Step 9, re-flash CWM 6.0.1.0
H. If you chose No. from Step E, root again if you wish.
DONE!!
I've try this, but when I do point 8 (select Apply update.zip), the update is aborded.
I'm on SDs_Acer_AV043_A700_RV07RC06_EMEA_FR.zip with the root by patched boot.
I want install Acer_A700_AV043.RV07RC06_AV043.RV23RC04_EMEA_FR.zip.
I don't know why update fail.
imtheyoyo said:
I've try this, but when I do point 8 (select Apply update.zip), the update is aborded.
I'm on SDs_Acer_AV043_A700_RV07RC06_EMEA_FR.zip with the root by patched boot.
I want install Acer_A700_AV043.RV07RC06_AV043.RV23RC04_EMEA_FR.zip.
I don't know why update fail.
Click to expand...
Click to collapse
i think i know why.
i revised step 5, check it out
That's what I had done, zip and rename in update.zip.
imtheyoyo said:
That's what I had done, zip and rename in update.zip.
Click to expand...
Click to collapse
hmm... did you put it on an sd card?
and what error is it giving you?
Sterist said:
hmm... did you put it on an sd card?
and what error is it giving you?
Click to expand...
Click to collapse
Yes, and the message was "Update aborted"
Just a question. I have unlocked my A700 via method 2, so without CWM install.
If I follow this guide, placing the update.zip on the card, and restart with Volume-down+Power, will it execute the update.zip as well?
The update.zip in fact is the altered Acer_A700_AV043.RV07RC04_AV043.RV23RC05_WW_GEN1.zip according to the instructions.
If using Root Explorer, where would I have to place the update.zip file?
---------- Post added at 10:57 PM ---------- Previous post was at 10:52 PM ----------
CheopsChefren said:
Just a question. I have unlocked my A700 via method 2, so without CWM install.
If I follow this guide, placing the update.zip on the card, and restart with Volume-down+Power, will it execute the update.zip as well?
The update.zip in fact is the altered Acer_A700_AV043.RV07RC04_AV043.RV23RC05_WW_GEN1.zip according to the instructions.
If using Root Explorer, where would I have to place the update.zip file?
Click to expand...
Click to collapse
Thanks for any advice.
CheopsChefren said:
Just a question. I have unlocked my A700 via method 2, so without CWM install.
If I follow this guide, placing the update.zip on the card, and restart with Volume-down+Power, will it execute the update.zip as well?
The update.zip in fact is the altered Acer_A700_AV043.RV07RC04_AV043.RV23RC05_WW_GEN1.zip according to the instructions.
If using Root Explorer, where would I have to place the update.zip file?
Click to expand...
Click to collapse
I'm not sure if a modified update script would run on the stock recovery. you can try it, the worst that would happen is it will decline to run the update. i would recommend you always have CWM recovery regardless of any flashing/updating plans you may or may not have.
and the location for the update.zip does not change regardless of what you use to get the file there lol it doesn't matter if you use a Toyota or Lamborghini to get to work. silly question lol..
Thanks for your answer. The problem is, an unmodified update script wont run either on my unlocked A700.
And, I am scared about using CWM, as I hear stories it will possibly brick your A700, and that is something I am not too keen about.
But, with Root Explorer compared to ES File Explorer you have more possibilities. But I agree, it was abit a silly question.
So now, how to update my unlocked A700 with the OTA delivered by Acer? That's the question.....
CheopsChefren said:
Thanks for your answer. The problem is, an unmodified update script wont run either on my unlocked A700.
And, I am scared about using CWM, as I hear stories it will possibly brick your A700, and that is something I am not too keen about.
But, with Root Explorer compared to ES File Explorer you have more possibilities. But I agree, it was abit a silly question.
So now, how to update my unlocked A700 with the OTA delivered by Acer? That's the question.....
Click to expand...
Click to collapse
by my understanding, the CWM versions to avoid are 5.4.0.0 (something like that) and the touch version(s)
unlocking your bootloader and not installing CWM is like alcohol-free-beer... pointless.
When trying the above mentioned procedure, i first got an error 6, which i solved by editing the updater-script the second time with notepad++, so i could keep the unix-like line-ends.
Then when i tried to run the update.zip from within cwm, i got error status 7.
(On both the downloaded update file from the thread mentioned above, and from the original from Acer received OTA update file)
As far as i know, after googling error status 7 has to do with the update zip not for the system trying to update. But i am sure, as i also tried with the Acer received OTA (after deleting the first line in the updater-script), i used the correct update file.
What could cause this?
Hi. Link for U.S. tab owners (www.sendspace.com) is dead. Can you post again?
eman01 said:
Hi. Link for U.S. tab owners (www.sendspace.com) is dead. Can you post again?
Click to expand...
Click to collapse
LOL stupid mistake on my part
the link wasn't really dead, i just screwed up in how i posting it lol thanks for mentioningit
Got it. Thanks.
OK. I finally tried above method to update rooted U.S. A700.
Started with:
Image Acer_AV043_A700_RV07RC06_PA_CUS1
Build Acer_AV043_A700_1.029.00_PA_CUS1
CWM Recovery 6.0.1.1
I tried both methods above- initially using the update.zip specifically provided for U.S. A700 owners in the 2nd part of 1st post of this thread
IN "BONUS FOR USA TAB OWNERS!".
Tried it on 1st external SD, then internal SD.
Both ways I get RED TRIANGLE with exclamation point and message:
"Can't open /sdcard/update.zip
(bad)"
OR
"Can't open /emmc/update.zip
(bad)"
I am, of course, sure I copied the update.zip directly from Downloads to the root of the external and internal cards;
I also made sure to use "Choose zip from SD card" in CWM to find the Update.zip file right where I put it.
Not ready to quit, I tried again using the original Update zip file and modifying updater.script myself, exactly as described in the 1st part of the 1st post. I also tried this update.zip with modified updater.script on both the external and internal SD, without success.
This time I did get further, receiving:
Finding update package...
Opening update package...
Installing update...
Mount Data success
Verifying current system...
assert failed: apply_patch_check_("EMMC:\dev\block\platform\sdhci-tegra.3/by-name/LNX:4065536:95
Then a bunch of letters/numbers
E:Error in sdcard/update.zip
(Status 7)
Installation aborted.
P.S. I verified I have the assert line deleted in the updater.script before I tried this.
I should mention that I have stock ROM, have and have NOT deleted any system apps
(I have inactivated a few like VirusScan within Android).
Luckily I was able to reboot without any problems after all these attempts, but now I am stuck.
Any ideas?
hmmm that's an error i haven't seen before. try deleting the update and downloading it again, or disabling assert check
I'm not a developer, that's the best i can suggest. you'd have to ask someone with a bit more knowledge
it might have something to do with the root method you used originally
Well, I tried yIur modified update.zip multiple times (downloaded it 3 different times, and tried both internal and external SD). As mentioned, I also tried modifying the updater.script myself (used JOTA text editor; maybe that was an issue with respect to how it saves a file, etc.).
How does one disable assert check, as you describe? A link, perhaps?
Interestingly, today I was able to flash the original1.029 update (1st A700 OTA update) after modifying it's updater.script in exactly the same fashion you describe. It put me back to stock 1.029, which I then updated to stock 1.057 (2nd A700 OTA update). I then re-unlocked bootloader, re-rooted and re-installed CWM recovery 6.0.1.1 easily and successfully as described in the threads in A700 development in this forum. Still holding out on CM ROM, as it seems fairly buggy. Thanks for trying. My way definitely took longer; don't know why your direct method would not work on my tab. Thanks.
disable asset check should be one of about 4 or 5 options to choose from, right next to ''choose from internal'' / external
it actually might not be available on this device it's been a while since I've used CWM
i do these modifications right from my tab with ES file explorer.
glad you were able to get it working
[solved] US A700 rooted OTA update
hi all,
after few days of messing about I finally managed to update a rooted US A700. I will try to guide you through what I did.
After initially booting up the A700 I upgraded it OTA to AV043_A700_RV07RC06_PA_CUS1 and after that rooted it using method #2 in the rooting thread (method #1 didn't work for some reason)
Got OTA notification saying that AV043.RV23RC03_PA_CUS1 was available (performance update, 35.72MB in size) but that wouldn't install giving error Status 7.
Installed CWM 6.1.1, still tthe same results, it wouldn't even install any of the other ROM's that are posted in this forum.
I probably should mention that I saved the original OTA update for installation later.
here is the solution (at least in my case)
Downloaded ROM Acer_A700_AV043.RV00RC00_AV043.RV07RC06_PA_CUS1.zi p from http://forum.xda-developers.com/showthread.php?t=1720157
Extracted boot.img and flashed via fastboot flash boot boot.img
Rebooted into CWM recovery and flashed the earlier saved OTA update no problem (was saved on internal memory but external memory card should work as well)
Then all that needed to be done was to root the A700 again (I used method #2 again)
Hope that helps someone.
eman01 said:
OK. I finally tried above method to update rooted U.S. A700.
assert failed: apply_patch_check_("EMMC:\dev\block\platform\sdhci-tegra.3/by-name/LNX:4065536:95
Then a bunch of letters/numbers
E:Error in sdcard/update.zip
(Status 7)
Installation aborted.
Any ideas?
Click to expand...
Click to collapse
You are not using the original bootloader so checking failed.
Simply delete this line to fix it (it happened to me last week when I created my homemade OTA update). Don't forget to unlock your bootloader after that !
Hi
I am trying to install the Jellybean 4.1.1 ROM on my rooted Nexus S.
The history of my attempts so far are here: Rooted Nexus S OTA Upgrade to 4.1 http://forum.xda-developers.com/showthread.php?t=1833420
I have downloaded the "image-soju-jro03e.zip" form the Android open source website, and used the Nexus Root Toolkit to install it.
This failed, and I attempted to install the image using ROM Manager.
This also failed, and produced a lengthy Recovery Log.
I have read through it and it seems to be telling me that certain files or folders are missing from the download.
e.g can't open /dev/tty0: No such file or directory
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
can't find /sd-ext in /etc/fstab
Is that what this means?
How can I correct it?
The full log is here: https://docs.google.com/document/d/1HWeYsXPnppQbgoloz72RH81E8a479LBmvYXIlzYPETo/edit
S
Help with recovery log
Hello?
Can anyone help me to understand this recovery log?
Should I direct my question to the "ROM Manager" people?
I have tried without success to install JB 4.1.1 from the Google Android Images page, and I think it must because something is missing from the file structure of my current ROM.
Am I on the right track?
M S
First of all, what variant of the Nexus S do you have? If you turn off the device and remove the battery, it should be on the sticker showing the device serial number.
Once you find that, you can head over to this link and look for the right image for your device:
http://www.randomphantasmagoria.com/firmware/nexus-s/
I'm assuming that since you're from 4.0.4, you just need to flash the update zip. If you're device is rooted, chances are you have ClockworkMod installed. If so, maybe you should just consider putting in a custom ROM. Flashing it should be much faster. I'd be glad to help you if you can give more info on your variant, current software state (version, rooted/not rooted, etc).
new hope
nightsky87 said:
First of all, what variant of the Nexus S do you have? If you turn off the device and remove the battery, it should be on the sticker showing the device serial number.
Once you find that, you can head over to this link and look for the right image for your device:
http://www.randomphantasmagoria.com/firmware/nexus-s/
I'm assuming that since you're from 4.0.4, you just need to flash the update zip. If you're device is rooted, chances are you have ClockworkMod installed. If so, maybe you should just consider putting in a custom ROM. Flashing it should be much faster. I'd be glad to help you if you can give more info on your variant, current software state (version, rooted/not rooted, etc).
Click to expand...
Click to collapse
Hello nightsky ( is that like, "nice guy",?) thanks for taking a look.
My phone is a Nexus S i9020, no suffix.
It is running Andriod 4.0.4 ICS. It is "rooted" and "unlocked".
I have Clockwork Mod v.6.0.1.0. Superuser v.3.1.3. and ROM Manager v.5.0.2.0.
I have tried over and over again without success to upgrade to JB 4.1.1 and I am getting sick and tired of this stupid game.
I would be happy to just stick with ICS 4.0.4, but every week, the phone tells me that an "update is available", and I have to dismiss the message every time I look at the phone! When I tried to apply the update It used to crash, requiring a battery-pull reset. Now I have CWM it takes over and says "failed to verify file signature", "install untrusted package?"
If I press on and install, it fails and the android is on its back with a red triangle on its belly.
If you look at the posts I have linked to, I have been on a steep learning curve regarding ROM flashing, and I understand the basic idea, its just that when I follow the instructions given on the forum, It doesn't happen that way for me and I suspect that there is something wrong with the file structure on my phone. That is why I have posted the link to my recovery log.
If you can help, please reply.
I have had a look at the "Random Phantasmogoria" site that you recommend, is it offering anything different than the Google developers site https://developers.google.com/android/nexus/images that I have downlooaded my image from?
MS
another version!
PS I have just had a look at the Google Dev. site and there appears to be a new version of 4.1.1 called JRO03L.
My next attempt, I'll try that.
MS
goodnight
Factory images are not to be installed with ROM manager/recovery.
They are factory images that are installed with fastboot.
Your solution is a rather simple but may seem complex to you at first. If that makes sense.
First screw all those one click/ ROM manager crap.
Either download the SDK and get the platform tools add on ( quides are all the over the place). Or use one of those zips people make that include fastboot.exe and a driver or whatnot.
Boot the phone into the bootloader. Connect it to the PC. Open a command prompt in the directory with fastboot.exe and the factory images....
Type in fastboot devices. If your serial comes up just follow the commands in the quide. Re root if you want.
What you where attempting to do reminds me of kids in the arcades just smashing buttons and hoping something works
I am not going to right a guide m. There are stickies and somebody actually made a very noon friendly explanation the other day on here somewhere. Sorry don't know where at the moment.
If there is a specific part or something in particular you don't get let me / us know.
Moral of the story is a once a computer is set up with fastboot properly it is very simple.
jus to add on the post above. the instruction to install the factory images are on the same page where you downloaded the image in question.
and there is something to be wary of : flashing the factory image will WIPE the phone CLEAN (except what's on the usb storage o/c).
albundy2010 said:
Factory images are not to be installed with ROM manager/recovery.
They are factory images that are installed with fastboot.
Your solution is a rather simple but may seem complex to you at first. If that makes sense.
First screw all those one click/ ROM manager crap.
Either download the SDK and get the platform tools add on ( quides are all the over the place). Or use one of those zips people make that include fastboot.exe and a driver or whatnot.
Boot the phone into the bootloader. Connect it to the PC. Open a command prompt in the directory with fastboot.exe and the factory images....
Type in fastboot devices. If your serial comes up just follow the commands in the quide. Re root if you want.
What you where attempting to do reminds me of kids in the arcades just smashing buttons and hoping something works
I am not going to right a guide m. There are stickies and somebody actually made a very noon friendly explanation the other day on here somewhere. Sorry don't know where at the moment.
If there is a specific part or something in particular you don't get let me / us know.
Moral of the story is a once a computer is set up with fastboot properly it is very simple.
Click to expand...
Click to collapse
Smashing buttons and hoping something works?
That's not very nice, or fair!
If you take the trouble to read my post, and the linked previous posts, you will see that I am trying my best to follow the instructions given on this forum, where I hoped to find knowledgeable professionals who contribute their valuable time free of charge to help noobs like me.
So far I have followed the instructions, only to get something other than the result described. This is why I am asking for your help to understand the recovery log, so that I can work out for myself what went wrong, and what I should change next time to get it right.
At this point in the journey I am still unsure about backup. I have "backed up" using the nexus root tool kit, which is a Nandroid back up, and I have "backed up" using ROM manager, but Titanium Back-Up does not recognise the backups and wants me to "back up" some more. After all this is over will I be able to clear out all the dross that my phone memory is accruing? Is there any point backing up Apps like "Google Earth" when I can easily download them from the Play Store after I have my new OS? etc... etc...
Anyway, I am going to try again, this time with the new JRO03L image, and this time I shall do it Command Line style instead of the "one click crap", as you recommend, my friend. I'll let you know how I get on.
MS