Dear members, Like always i first of all would like to thank you all for the great effort and hard work all of you have put into this wonderful site.
I am a noob with a rooted nexus one. ( i was begining to think of myself a step above noob recently but trying to update my phone to froyo made me realize i still am a noob.
I so want to update to froyo NOW without waiting for the OTA update but i just cant figure out how to. i downloaded the FR50 ( with and without radio ) but both failed. SO i figured it must be due to stock recovery. So i went to Amon Ra's thread to flash the new recovery image using terminal but after placing the image on the sdcard when i enter the flash image command , it says " image not found " when its most definitely there on the sdcard and i checked the spellings over and over again but it just wont flash and as a result i still cant enjoy froyo
I am sooooo sorry if i posted this thread in the wrong section but i really could use some guidance from the most intelligent Android people i know .
Regards,
Nadeem
It's basically a 4 step process, but make sure you did all of them.
1) Unlock Bootloader
2) Apply Root. I used this method, quick and painless: http://android.modaco.com/content/g...-erd79-frf50-superboot-rooting-the-nexus-one/
3) Flash Recovery using ADB.
3a) Recommended: Do a Nandroid backup image of your Stock 2.1u1, just in case something wierd happens during your flash.
4) Flash FRF50 ROM w/Radio. You want the version with the new Radio, as I believe 2.2 won't work with the 2.1 radio without tinkering.
ATnTdude said:
as I believe 2.2 won't work with the 2.1 radio without tinkering.
Click to expand...
Click to collapse
It works for the most part, but you'll get a crash if you try to record video without updating the radio.
Wait...you put the Recovery image on your SDCard? It should be on your harddrive. You push the the image from the HDD to the phone. Unless there's some other way I don't yet know about.
caliwolv said:
It works for the most part, but you'll get a crash if you try to record video without updating the radio.
Click to expand...
Click to collapse
Well, I'm glad I at least the gist of the material is sticking. I browse this place just about every day trying to keep myself from bricking my phone. If I do, it's back to my Nokia E71, and being forced to use Symbian after Android 2.2...not pleasant at all.
I highly appreciate the super quick response ATnTDUde
The first two steps in your method describe how to get root i presume....
Actually i already rooted my Nexus 1 and i am fairly certain the bootloader is unlocked too ( i see a small padlock unlocked every time i turn my N1 on)
Oh so i am going to have to flash the AMon Ra recovery image using ADB. actually on Amon's thread there was another method of flashing the image using terminal which i tried and failed at. I'll most definitely try ADB method once i get back home.
Just wanted to ask you a quick question Sir.
Once i flash Amon Ra's recovery image i assume i wont be getting any OTA updates from google ???? right ....
Also if i want to go to the stock recovery image ( is there a way to do so ? ) will i start getting OTA updates
Please some one help with the two questions above coz i cant start the process without knowing.
nadeemhasnaat said:
......
Once i flash Amon Ra's recovery image i assume i wont be getting any OTA updates from google ???? right ....
Also if i want to go to the stock recovery image ( is there a way to do so ? ) will i start getting OTA updates
Click to expand...
Click to collapse
1) right
2) yes
ATnTdude said:
Wait...you put the Recovery image on your SDCard? It should be on your harddrive. You push the the image from the HDD to the phone. Unless there's some other way I don't yet know about.
Click to expand...
Click to collapse
Yeah, its very easy.
adb shell flash recovery /sdcard/Amon-Ra.img
or whatever the thing is.
or you can
fastboot flash recovery C:\android\tools\wha\tev\er\Amon-Ra.img
The path just has to be correct wheter o
Related
I followed the steps in this guide http://forum.xda-developers.com/showthread.php?t=544654 for unrooting my rogers dream right down to the letter but somehow managed to screw up. I want to get my phone back to its original state, but am unsure of two things, so im going to ask them here before I screw up second time (and brick for good :S)
Code:
fastboot flash radio rogersradio.img
fastboot flash recovery rogersrecovery.img
fastboot erase system -w
and flash the update.zip found somewhere on this forum ;P
Click to expand...
Click to collapse
1) Where is this update.zip? There are so many, im not even sure where to begin looking
2) I cant access my sd card anymore (can only boot into fast boot mode and recovery mode). Is there still a way to write the update.zip to the card, or do I need to find another phone to give me access to the card.
Thanks!
martin_secretary said:
I followed the steps in this guide http://forum.xda-developers.com/showthread.php?t=544654 for unrooting my rogers dream right down to the letter but somehow managed to screw up. I want to get my phone back to its original state, but am unsure of two things, so im going to ask them here before I screw up second time (and brick for good :S)
1) Where is this update.zip? There are so many, im not even sure where to begin looking
2) I cant access my sd card anymore (can only boot into fast boot mode and recovery mode). Is there still a way to write the update.zip to the card, or do I need to find another phone to give me access to the card.
Thanks!
Click to expand...
Click to collapse
can't you just flash the official rogers update?
martin_secretary said:
I followed the steps in this guide http://forum.xda-developers.com/showthread.php?t=544654 for unrooting my rogers dream right down to the letter but somehow managed to screw up. I want to get my phone back to its original state, but am unsure of two things, so im going to ask them here before I screw up second time (and brick for good :S)
1) Where is this update.zip? There are so many, im not even sure where to begin looking
2) I cant access my sd card anymore (can only boot into fast boot mode and recovery mode). Is there still a way to write the update.zip to the card, or do I need to find another phone to give me access to the card.
Thanks!
Click to expand...
Click to collapse
you can put the files on your sdcard by mounting it in your recovery and using adb push
if you have cyanogens recovery, go to console on it and type
Code:
ums_enable
and it will show up on your computer
when your done
Code:
ums_disable
correct me if im wrong, but my phone needs to be rooted in order to use cyanogens recovery right?
Something tells me that my phone didnt root when I was following those instructions (maybe I have that perfect SPL everyone is talking about?)
Anyway so far Ive spent half a day on this, and no luck, and I feel like Im getting ever closer to bricking my phone. It doesnt help that almost all guides here are for the G1 and very little for rogers.
Anyway, is anyone interested in $25 that Ill pay them via paypay/online banking to talk to me through recovery? Private msg me
hjlow said:
can't you just flash the official rogers update?
Click to expand...
Click to collapse
there is no official rogers update
martin_secretary said:
there is no official rogers update
Click to expand...
Click to collapse
It's posted on rogers website.
I bought my phone used and I used the universal androot app to root it without locking the bootloader. I want to take it back to just the way it was when it came out of the box. Are there easy to follow step by step directions anywhere? I've searched but everything says it assumes you know how to use adb and fastboot. I don't. Do directions exist for dummies? It sure was a piece of cake to restore my old iPhone.
Yeah, I had the same problem a few weeks ago. My suggestion is look at some tutorials for installing custom ROMs and then reverse engineer those once you've learned how to use adb and fastboot.
You mean something like this -->
http://androidspin.com/2010/05/06/guide-unrooting-your-nexus-one-its-like-it-never-happened-almost/
cymru said:
You mean something like this -->
http://androidspin.com/2010/05/06/guide-unrooting-your-nexus-one-its-like-it-never-happened-almost/
Click to expand...
Click to collapse
Kind of like that, but this part confused me.
"Once you have this installed, add a folder path for the ADB utility to your System Environment Variables “path” variable."
Ok, when I get to step 7, the command prompt says "FAILED (remote: not allowed)"
What's up with that? HELLLLLLP!
I did a manual erase user data, but now when I go to Type 'fastboot flash userdata userdata.img'
the command prompt tells me FAILED (remote: signature verify fail)
Help?
Okay, sounds like you're panicking.
There's kinda like a fix everything button, and that's a passimg.
Grab it here: (remove the spaces, I'm not allowed to post links)
w w w . megaupload . com/?d=7JQU3MV0
All you gotta do is put that on the root of your SD card. Boot into bootloader mode (hold down trackball when powering) and select recovery. That's all. It'll detect passimg, and fix everything.
The caveat here, is that you'll be on EPE76 - which was super duper annoying to actually upgrade from (but I eventually found a FRF91 rom that worked - I'll see if I can find it and post it for you).
But yeah. Download that. Fix everything. Enjoy
From EPE76 can't you just do an OTA update to upgrade to Froyo? And what exactly does this passimg do and how does it work? I got adb and fastboot working and everything, I just get errors when I try to flash. Do you have to have an unlocked bootloader to do this stuff? I just used the universal androot app to gain root, so the bootloader wasn't actually unlocked.
No. the passimg will just automatically flash radio, recovery, etc. so you don't have to. If you've got it working manually now, no need to use it.
The passimg does pretty much what you were asking about. The Nexus One has the code name "Passion", so "pass/img" is the original factory shipping image for the Nexus One. The OTA should then** come to your phone, maybe in a few hours, but maybe not for a while.
And if I do the passimg it shouldn't screw up the phone since I'm already running froyo and this will kick me back to 2.1?
Read - Nexus One Wiki, "Unroot / Restore your Nexus", PASSIMG.ZIP method.
Written especially to avoid threads like this one.
Well it worked perfectly and now I'm running 2.1 EPE76. Is there a way to force it to update to Froyo?
you should be able to open up your dialer and type
*#*#CHECKIN#*#*
or
*#*#2432546#*#*
scgolfer7 said:
you should be able to open up your dialer and type
*#*#CHECKIN#*#*
or
*#*#2432546#*#*
Click to expand...
Click to collapse
That's a negative. It just says checkin result success, but doesn't download any update. When I go to about phone and system updae it says my system is up to date.
If I was reading correctly I should upgrade from EPE76 to FRF85B and then I should get the FRF91 OTA? Can anyone confirm this?
I got everything working and I'm back to completely stock Froyo FRF91 and I just wanted to thank everyone who contributed to this thread for guiding my annoying newbie ass through the process and teaching me a wealth of knowledge about the Android OS along the way. Thanks again!
For future reference, if you want to restore your phone while having no issues accessing it, just get Rom Manager. Use it to download and install a stock unrooted Froyo rom (just make sure to select wipe data and do not select the rooting options).
Very easy to restore. The passimg method comes in very handy if you cannot even boot into the OS.
so my friend recently gave me his old G1, and i did some searching around and discovered that HTC made a dev version. now, being new to android, i have absolutely no clue what the differences are. i want to update my adp1 to froyo, but i get lost when i look up stuff about rooting or whatever. can anyone dumb it down for me or link me to an easy to follow walkthrough? i'm not sure whether or not guides for the g1/dream can be applied to the dev version. please help a noob in need
ADP1 shipped with bootloader 0.95.3000 whereas non-ADP shipped with 0.95.0000. 3000 let you flash unsigned images. That is the difference.
Note that all 0.95 SPLs are obsolete now.
dhkr123 said:
ADP1 shipped with bootloader 0.95.3000 whereas non-ADP shipped with 0.95.0000. 3000 let you flash unsigned images. That is the difference.
Note that all 0.95 SPLs are obsolete now.
Click to expand...
Click to collapse
so how would i go about putting 2.2 on it?
http://forum.xda-developers.com/showthread.php?t=831139
http://forum.xda-developers.com/showthread.php?t=717874
http://forum.xda-developers.com/showthread.php?t=811620
dhkr123 said:
http://forum.xda-developers.com/showthread.php?t=831139
http://forum.xda-developers.com/showthread.php?t=717874
http://forum.xda-developers.com/showthread.php?t=811620
Click to expand...
Click to collapse
x_x wow thanks
going to try and decipher these forum posts now
http://wiki.cyanogenmod.com/index.php?title=Dream:Rooting
^
That is the way that most of us rooted our phones. It's reasonable simple, downgrade, type teldnetd, open telnet app, install a recovery, update radio, set boot partitions(if using customMTD)/install danger SPL, and flash CM. If you would like to get as much performance as possible from your phone, I suggest using ezterry's rom, but for that you will need to update the radio and spl through adb and fastboot, which is a little bit more advanced. If you need anything don't be afraid to ask.
mejorguille said:
http://wiki.cyanogenmod.com/index.php?title=Dream:Rooting
^
That is the way that most of us rooted our phones. It's reasonable simple, downgrade, type teldnetd, open telnet app, install a recovery, update radio, set boot partitions(if using customMTD)/install danger SPL, and flash CM. If you would like to get as much performance as possible from your phone, I suggest using ezterry's rom, but for that you will need to update the radio and spl through adb and fastboot, which is a little bit more advanced. If you need anything don't be afraid to ask.
Click to expand...
Click to collapse
hm so i'm looking at the instructions on the link you gave me; i won't be able to login to my google account without a 3g plan huh? i guess i'll have to get that before i do anything?
and it doesn't matter that i have the ADP1 instead of just a regular G1?
pandapus said:
hm so i'm looking at the instructions on the link you gave me; i won't be able to login to my google account without a 3g plan huh? i guess i'll have to get that before i do anything?
and it doesn't matter that i have the ADP1 instead of just a regular G1?
Click to expand...
Click to collapse
Well in that case use this link, since your bootloader is already factory unlocked, you can use the fastboot commands to flash a recovery image. You will need to have adb and fastboot from the android sdk installed on your computer. There are guides in the rom bible on the development forum to help you with that.
EDIT: and try this trick for skipping the initial login so that you can use wifi to sign in if you have to.
mejorguille said:
Well in that case use this link, since your bootloader is already factory unlocked, you can use the fastboot commands to flash a recovery image. You will need to have adb and fastboot from the android sdk installed on your computer. There are guides in the rom bible on the development forum to help you with that.
EDIT: and try this trick for skipping the initial login so that you can use wifi to sign in if you have to.
Click to expand...
Click to collapse
unfortunately that trick does not work with the ADP1 =(
i flashed with DREAIMG.nbh and cannot bypass the setup thing; then i discovered this article: http://forum.xda-developers.com/showthread.php?t=532719
which i completed up until the "installing drivers" step that i don't know how to complete because the computer doesn't even recognize that a device is plugged in, so now my phone thinks it's a G1 and i cannot get past the login screen and i cannot complete the ADB setup with my phone. what do i do?
---------------
EDIT: alright so i bypassed the login by swapping SIMs with a friend who has a 3G plan, but anyhow, when i plug it into my comp, i don't get an option to "Install drivers from my pc" according to the guide i referenced earlier in this post....
After waiting for the official AT&T froyo release with the captivate, I decided to just go ahead and flash a froyo ROM. I've decided to flash the axura ROM first since i heard good things about it.
So while I'm finishing charging my phone before the flashing, is there anything I need to keep note of before flashing so that I can prevent bricking my phone? I've read up on the forums and watched the video from connexion2005 from the post: http://forum.xda-developers.com/showthread.php?t=867153.
Its pretty scary since I'm not much of a tech savy guy and this is my first android phone. Any help and suggestions will be appreciated.
agegsg said:
After waiting for the official AT&T froyo release with the captivate, I decided to just go ahead and flash a froyo ROM. I've decided to flash the axura ROM first since i heard good things about it.
So while I'm finishing charging my phone before the flashing, is there anything I need to keep note of before flashing so that I can prevent bricking my phone? I've read up on the forums and watched the video from connexion2005 from the post: http://forum.xda-developers.com/showthread.php?t=867153.
Its pretty scary since I'm not much of a tech savy guy and this is my first android phone. Any help and suggestions will be appreciated.
Click to expand...
Click to collapse
Backup all your apps and data with Titanium Backup. Make sure your battery is fully charged, and removing your sim and SD cards are good practice.
Have fun! You won't go back.
- Backup all your files and make a nandroid backup!
- Get Odin3 One-Click and drivers to get your phone back to stock in case you brick it: http://forum.xda-developers.com/showthread.php?t=731989
- There may be additional precautions you can take, so read through related threads on xda.
agegsg said:
After waiting for the official AT&T froyo release with the captivate, I decided to just go ahead and flash a froyo ROM. I've decided to flash the axura ROM first since i heard good things about it.
So while I'm finishing charging my phone before the flashing, is there anything I need to keep note of before flashing so that I can prevent bricking my phone? I've read up on the forums and watched the video from connexion2005 from the post: http://forum.xda-developers.com/showthread.php?t=867153.
Its pretty scary since I'm not much of a tech savy guy and this is my first android phone. Any help and suggestions will be appreciated.
Click to expand...
Click to collapse
If you've read as much as you claim to have read, then you're probably in good shape. It's really not an unsafe process as long as you have some idea of what you're doing. I was very nervous about it myself the first time, but since then I've probably flashed 20 roms without a problem.
A couple of things that I would tell you, if you aren't already aware:
1. MAKE SURE that BEFORE you flash, you can get into download mode from the phone being off using one of the methods. I'm sure you've seen the one-click flash back to JF6 (stock) that was posted - download that if you haven't. For me, removing the battery, sim, and ext sd, replacing the battery, and holding down both volume buttons while plugging in the USB works really well - just make sure Odin is running before you do that. If you do manage to brick it, you will want to be able to get to download mode and flash back to stock.
2. After moving to a custom rom, it is best to always flash back to stock before flashing a different rom; you can avoid a lot of potential problems this way.
3. After rooting your phone, backup the update.zip in /sdcard/ on your computer. Any time you flash back to stock, you can reinstall CWM really easily by just putting that update.zip back in /sdcard/ and choosing "reinstall packages" from the recovery menu again. Sometimes you may have to do it twice before it enters CWM.
4. OCLF in the market is, to me, the easiest and quickest way to root your phone, but the one click root method isn't much worse. Just a matter of preference, I guess.
Good luck! Come back if you have any problems.
EDIT: apparently two people replied while I was typing my response lol! But what they said is very good as well.
Thank you for all your help. One quick question though, do I need the android ID changer?
the biggest mistake people make is not making sure they have the button combinations to enter recovery or download. (download = hold both volume buttons own and plugging usb cable in; recovery = hold volume buttons down, then holding power until AT&T screen pops up, letting go of power but still holding both volume buttons) if either of these don't work, you must, before doing ANYTHING else, flash the stock odin one click with the button fixes; it is posted somewhere in the development forum. and no you shouldn't need the android id changer unless you want to keep the android id that your phone came with. then open the changer and click save id and flash your rom of choice. most custom roms have a script to automatically load a saved id or randomly generate one if there wasn't a saved one. good luck in all your flashing endeavors!
edit: also as bodaciousdrake mentioned previously about cwm recovery, you should always keep the update.zip that contains cwm recovery on your sd card and you'll never need to change that to something else because using cwm recovery you can flash any .zip file that you want and it does not need to be named update.zip.
Take out the external SD card before you accidently delete 10 GB of music you had just perfected the selection of. (not that I accidently did that... lol)
mindbullet said:
Take out the external SD card before you accidently delete 10 GB of music you had just perfected the selection of. (not that I accidently did that... lol)
Click to expand...
Click to collapse
lol oops! Did that happen with a master clear, or when you flashed the rom? I have forgotten to take out the sim/ext sd once or twice but I have never had a problem...yet.
agegsg said:
Thank you for all your help. One quick question though, do I need the android ID changer?
Click to expand...
Click to collapse
Yes, you need it. Download it from the market, while on 2.1, and save your id onto your sd card. After you are on 2.2, choose Load id and it will automatically reboot.
majinzen said:
Yes, you need it. Download it from the market, while on 2.1, and save your id onto your sd card. After you are on 2.2, choose Load id and it will automatically reboot.
Click to expand...
Click to collapse
What exactly is the point in saving the phone id? Sorry I'm kinda a noobie at this and looking up things about phone id, it seems like it just is an identifier for the phone but doesn't really provide anything.
Also, how do I get out of download mode? I've put it in download mode to make sure it works and it seem I can't get out of it... I've done the 2 volume bottons with the usb cord.
there's another thread in this forum that answers that question perfectly. also to exit download mode you need to pull the battery out.
slifer315 said:
there's another thread in this forum that answers that question perfectly. also to exit download mode you need to pull the battery out.
Click to expand...
Click to collapse
Really? just take the battery out?
agegsg said:
What exactly is the point in saving the phone id? Sorry I'm kinda a noobie at this and looking up things about phone id, it seems like it just is an identifier for the phone but doesn't really provide anything.
Click to expand...
Click to collapse
Basically, a lot of 2.2 Roms come with the same android id, 977blah... If you don't want market issues later I would suggest that you put in your original 2.1 android id. You can always search more if that answer isn't sufficient. And yes, do a battery pull to get out of download mode.
I've master cleared but can't seem to root. Every time I try with the one click root, and I go to recovery, it said it can't find the update.zip from the /sdcard/
yep, just pull the battery. also you don't need to root to flash roms. just grab the update.zip containing clockwordmod recovery from the thread in the development forum, put it on your sd card, boot to recovery and select reinstall pacakges. after that, reboot the phone (you might have to reinstall packages again) then you'll be ib clockwordmod recovery and you'll be able to flash any rom you want without having to change the filename.
agegsg said:
I've master cleared but can't seem to root. Every time I try with the one click root, and I go to recovery, it said it can't find the update.zip from the /sdcard/
Click to expand...
Click to collapse
For some reason I got this too the first few times I tried to root. I then noticed that in the cmd prompt, for a split second it said failed to push update.zip or something due to privileges.
How I fixed it was ran the one-click root on windows in admin mode. It worked after that.
Thanks guys for all your help. I got it to flash the ROM and it seems I haven't bricked my phone
Thanks again
I people!
I wanted to install the official update on my ICS 4 Incredible S that has the ClockworkMod recovery with the superuser and is S-ON.
I made an official OTA update but when I rebooted the phone it locks and stays with the symbol android with a triangle with an exclamation .The phone is unlocked by HTCDev.com. I am back to putting everything as it was with the ClockworkMod recovery. Can you help me to perform the update? Thank you for your attention.
The reference in HBOOT will attach.
View attachment 1201873
Figas said:
I people!
I wanted to install the official update on my ICS 4 Incredible S that has the ClockworkMod recovery with the superuser and is S-ON.
I made an official OTA update but when I rebooted the phone it locks and stays with the symbol android with a triangle with an exclamation .The phone is unlocked by HTCDev.com. I am back to putting everything as it was with the ClockworkMod recovery. Can you help me to perform the update? Thank you for your attention.
The reference in HBOOT will attach.
View attachment 1201873
Click to expand...
Click to collapse
subscribed to your thread as i am in the same situation as you are,
unrooting and relocking bootloader did not help.
Figas said:
I people!
I wanted to install the official update on my ICS 4 Incredible S that has the ClockworkMod recovery with the superuser and is S-ON.
I made an official OTA update but when I rebooted the phone it locks and stays with the symbol android with a triangle with an exclamation .The phone is unlocked by HTCDev.com. I am back to putting everything as it was with the ClockworkMod recovery. Can you help me to perform the update? Thank you for your attention.
The reference in HBOOT will attach.
View attachment 1201873
Click to expand...
Click to collapse
In order to apply the OTA you will need to return to a fully stock state. Locked bootloader and replace ClockworkMod with the stock HTC Recovery.
tpbklake said:
In order to apply the OTA you will need to return to a fully stock state. Locked bootloader and replace ClockworkMod with the stock HTC Recovery.
Click to expand...
Click to collapse
Thanks I'll try and see what happens, then I say anything.
Thank you
I have just been through this too.
Firstly I'd say be careful, ICS for me was not good - bluetooth connections were very fragile (sometimes did not auto-connect when the other device was turned on, and then when it did connect, the phone did not disconnect when the other device turned off. At this point trying to go into the phone bluetooth menu to cycle bluetooth off or manually disconnect caused the phone to crash. I even performed a factory re-set and it was the same)
But if you want to go ahead anyway, it's possible you may also need to have a standard system (un-rooted). Before I performed my update I flashed a standard system.img with fastboot. I'm not saying you will have to do this for sure, but for me since I was already flashing standard recovery.img with fastboot it was no bother to also restore the system.img - so it's just something you can try if your update doesn't work.
dingers01 said:
I have just been through this too.
Firstly I'd say be careful, ICS for me was not good - bluetooth connections were very fragile (sometimes did not auto-connect when the other device was turned on, and then when it did connect, the phone did not disconnect when the other device turned off. At this point trying to go into the phone bluetooth menu to cycle bluetooth off or manually disconnect caused the phone to crash. I even performed a factory re-set and it was the same)
But if you want to go ahead anyway, it's possible you may also need to have a standard system (un-rooted). When I did the update I flashed a standard system.img with fastboot. I'm not saying you will have to do this for sure, but for me since i was already flashing standard recovery.img with fastboot it was no bother to also restore the system.img - so it's just something you can try if your update doesn't work.
Click to expand...
Click to collapse
Along with the system.img file, you should have also flashed the lib.img file. That may be the cause of the flaky issues you are having with BT connections.
tpbklake said:
Along with the system.img file, you should have also flashed the lib.img file. That may be the cause of the flaky issues you are having with BT connections.
Click to expand...
Click to collapse
Thanks for the info. I am interseted in your comment both to learn a little more about the software structure and also because it opens up an avenue where I may re-attempt the ICS upgrade. So for these reasons, please allow me to ask:
- Do you mean I should have flashed lib.img before the update? I suppose I must ask what exactly is the lib.img?
The reason I didn't was, as I was running from a standard HTC rom as a base, I was under the impression that I'd only need to revert the parts that I had changed..... which (I thought) were the system (because I rooted) and the recovery (because I'd flashed 4ext)... to bring the phone back to standard trim.
- Are you saying that I might still have ended up with a 'non-standard' lib.img prior to the ICS upgrade? and if so which process (the rooting, installing recovery, or the boot unlocking) causes that?
- Also for this to be the potential cause of problems after the ICS upgrade, that supposes that the ICS upgrade would not have included a 'fresh' lib.img. Without knowing what img.lib is I don't know if this is this likely.. anyone?
dingers01 said:
Thanks for the info. I am interseted in your comment both to learn a little more about the software structure and also because it opens up an avenue where I may re-attempt the ICS upgrade. So for these reasons, please allow me to ask:
- Do you mean I should have flashed lib.img before the update? I suppose I must ask what exactly is the lib.img?
The reason I didn't was, as I was running from a standard HTC rom as a base, I was under the impression that I'd only need to revert the parts that I had changed..... which (I thought) were the system (because I rooted) and the recovery (because I'd flashed 4ext)... to bring the phone back to standard trim.
- Are you saying that I might still have ended up with a 'non-standard' lib.img prior to the ICS upgrade? and if so which process (the rooting, installing recovery, or the boot unlocking) causes that?
- Also for this to be the potential cause of problems after the ICS upgrade, that supposes that the ICS upgrade would not have included a 'fresh' lib.img. Without knowing what img.lib is I don't know if this is this likely.. anyone?
Click to expand...
Click to collapse
OK, I think I misunderstood at which point you flashed the system.img. I thought you had flashed the ICS system.img manually to force the OTA, not that you had flashed the system.img from the RUU/ROM you were currently running. My mistake.
Anyway, since you are eager to learn, hopefully this will give you some answers to your questions. Please reference this diagram from the BlackRose 2.02.0002 thread and perhaps my comments will make more sense.
http://forum.xda-developers.com/showpost.php?p=22789898&postcount=2
If you look at the contents of a RUU/ROM.zip file, you will notice that it contains various img files such as system.img, radio.img, recovery.img, boot.img, etc.
These represent partition of Android. Beginning with GB 2.3.5/Sense 3.0 ROMs, HTC decided to split the system.img into 2 parts, system.img and lib.img.
From the diagram, you can see that lib.img file actually gets mounted as the /system/lib directory, therefore if you flashed the system.img manually as part of trying to get the OTA going, you should also flash the corresponding lib.img so that you have a complete /system structure.
SOLVED
20545ZR16 said:
subscribed to your thread as i am in the same situation as you are,
unrooting and relocking bootloader did not help.
Click to expand...
Click to collapse
tpbklake said:
In order to apply the OTA you will need to return to a fully stock state. Locked bootloader and replace ClockworkMod with the stock HTC Recovery.
Click to expand...
Click to collapse
Figas said:
Thanks I'll try and see what happens, then I say anything.
Thank you
Click to expand...
Click to collapse
Is solved, I installed the stock HTC Recovery, locked bootloader and installed RUU_VIVO_ICS_35_S_HTC_WWE_4.10.405.1_Radio_20.74.30.0833U_3831.18.00.11_M
Everything worked perfectly.
Thank you for your help.
Hugs to you all