Related
I recently bought a nexus one from vodafone, which came with vodafone's version of froyo FRF91 pre-installed. I wanted to get future OTA updates direct from google so I unlocked the bootloader, and downgraded to ERD79 using this guide:
(can't post links, but if you copy 'how to upgrade your nexus one today' into google, it's the first result - this is the guide i followed)
This all worked fine and i'm now on ERD79, but I cannot upgrade any further than ERD79. When I search for OTA updates using the "check in" command, it finds none and still says my system is up to date.
I also cannot update from the sd card using the update.zip method, as I get the following error:
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
I have done this before on another vodafone nexus one using exactly the same method and it worked fine. On the first phone, after downgrading to ERD79, the froyo OTA update began immediately. The only difference was that in that case, the phone did not have froyo to begin with, this time vodafones version of froyo was already installed.
If anybody has any clue as to why the phone will not download an OTA update, I'd be really really grateful if you could let me know!
Thanks
If you unlocked your bootloader - why wouldn't you just flash a custom ROM?
Jack_R1 said:
If you unlocked your bootloader - why wouldn't you just flash a custom ROM?
Click to expand...
Click to collapse
I unlocked it in order to get install stock froyo, so I would immediate future updates from google, rather than having to wait for vodafone to release their own version.
Why don't you instal Geo411m's rom? It's almost stock...(I really like it)
And as soon as the new OTA update is available you will find it here (and most likely it will be rooted asap)
What file did you use when you renamed to update.zip? From what i did. I downgraded to EPE76 then downloaded signed FRF85B. from EPE76 it said my system was up to date. but when i manually updated to FRF85B and checked the system updates it auto downloaded FRF91.
I used "PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_release_signed.zip" with fast boot to get ERD79 and then attempted to use "signed-passion-ERE27-from-ERD79.a487b405.zip" on the sd card to update. Then i get the error.
Appreciate the help guys,
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=717870&highlight=FRF91+downgrade
Second post. is the PASSIMG.zip. place in sdcard and boot into bootloader.
This takes you to EPE76.
then download FRF85B
http://www.mediafire.com/?j5zejudgngm
rename to update.zip. boot into stock recovery (triangle with android) then hold power and hit volume up, select update.zip
Ok I tried that and I got an error 'main version is older'.
I am downloading "PASSIMG_Passion_Google_WWE_1.11.1700.1_EPE76_release_signed.zip" now to try and do the same with that, or is that the same file that was called PASSIMG.zip in the thread you linked?
Have you looked into this thread?
http://android.modaco.com/content/g...-online-kitchen-optional-root-insecure-himem/
Yes i have that thread bookmarked but it's not helping me much right now unfortunately
I managed to get onto EPE76 by flashing the boot, recovery and system .img files using fastboot. But when i try to update to frf85b with the sdcard method i get the same error:
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Ok, I tried updating with the sd card method using RA custom recovery - it gives the error:
E: No signature (575files)
E: Verification failed
Installation aborted
Solved this now. In case anyone else has had this problem, it is related to the vodafone froyo versions having HBOOT 0.35.0017. Follow this guide http://forum.xda-developers.com/showthread.php?t=726258 to change that and go back to a version that allows updating
Anyone got it or know where I can find it? Would like to have it so I can flash official updates. Been searching for it with no luck. Tried using among RA 2.0.0 but still failed.
take the version that suits you from the ones that say (completely stock)
http://android.modaco.com/content/g...build-info-and-repacks-stock-rooted-deodexed/
I suggest the last one if you really want COMPLETELY stock, others are just with root/radio update mixes...although I doubt you need the radio
Is the recovery image from FRG33 the same? Have you tried flashing that one with fastboot? If it doesn't work you can always flash a different one.
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Roms
(The FRG33 package has recovery.img in there)
I don't see any reason to flash a new radio...
ahorriblemess said:
Is the recovery image from FRG33 the same? Have you tried flashing that one with fastboot? If it doesn't work you can always flash a different one.
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Roms
(The FRG33 package has recovery.img in there)
I don't see any reason to flash a new radio...
Click to expand...
Click to collapse
waaahhh sorry I misread the topic XD I thought he wanted a whole rom...
Forget my links then, they don't have a stock recovery in them
Just as a note, you don't need to have a stock recovery to get OTA updates...as long as your recovery does NOT check for signatures...else you can simply install the update manually.
But anyways, if you REALLY want a stock recovery, just find any official update and flash the recovery.img that's included with it.
I tried using among RA 2.0.0 and toggle the signature off so it wouldn't check, but it still failed. I'm trying the frg83 to frg83d from the modaco site.
dls5375 said:
I tried using among RA 2.0.0 and toggle the signature off so it wouldn't check, but it still failed. I'm trying the frg83 to frg83d from the modaco site.
Click to expand...
Click to collapse
If you have RA 2 working, you can grab the update here and flash as zip
http://www.shipped-roms.com/shipped...signed-passion-FRG83D-from-FRG83.ecb21b75.zip
That's the same one I already tried, wont flash even with RA working. The rom I use is stock frg83 but with root. It always seems to fail to update as it trys to verify what I'm currently running.
dls5375 said:
That's the same one I already tried, wont flash even with RA working. The rom I use is stock frg83 but with root. It always seems to fail to update as it trys to verify what I'm currently running.
Click to expand...
Click to collapse
As of my small experience so far i can tell that it is very hard to trace where the error is, when using cooked stuff, just like all of a sudded i got this bloody red trackball all the time, when ever the screen is on.
Ok, if you got some little time, here's how i would go for that: (assuming you want pure stock with root)
- Wipe
- Either fastboot the few images contained in the latest modaco stock rom, or say rather as he described there, alternatively just install the 2 files from shipped rom, one will be named PASSIMG.zip, the other update.zip and proceed as the popular threads describe
- If all is "original" you'll be prompted by google to download the update, once you got the frg83D, you can then use Super Once Click rooting 1.5.1, it still works for the updated thing.
I'm convinced there are a lot of similar threads and solutions to your problem, but you may deliver a bit more description to let the community see you did some research.
I returned completely to stock using the info from another thread on here and it worked perfectly. Also returned to stock recovery. As soon as it booted back up I got the ota for frg83d. I then used super one click root. It was really easy to setup and use. Bring on 2.3!
Disclaimer: You may brick your phone. NOT for AT&T
Reminder: Make sure your phone has enough battery charge to flash this, it's larger than normal.Hi,
Here is a huge CWM zip that restores your Bell phone to stock 2.2.2. I have tested it on my phone several times and it worked perfectly, there is still the chance that something may go wrong, but I am feeling confident in it.
What this does is similar to my app or scripts, it puts my backup of Bell's 2.2.2 partitions on your phone, but instead of using dd, it uses tenfar's CWM and flash_image. Some partitions are HUGE, and take a while, your phone is not locked up.
This has been updated to include the Bell bootloader for 2.2.2 and the radio for 2.2.2.
EDIT: This has been updated again to ram fix the boot and recovery partitions if there is a ram problem.
It writes to partitions 1, 2, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 17. 3 is left out because it's your pds partition, and data and cache have no relevant content. You must factory reset after using this to clear those. So, that's your boot, recovery, system, webtop, cdrom, preinstall, and several other partitions. This is to get back to stock Bell 2.2.2, it's not just a boot/system replacement, if that is a fruitcake, this is a gobstopper.
Please note: This restores your Bell phone to stock condition, that means you won't be unlocked, CWM will be overwritten with the stock recovery. It will be just like you bought it. If you want to keep flashing things in CWM with the unlocked bootloader, then immediately after flashing the stock zip, flash the unlock and fix zip. If you don't then you will have to reflash an unlocked bootloader, and reflash CWM recovery, which is time consuming any annoying, it doesn't mean you will be permanently locked again. I had to spell that out to the folks that don't really understand this stuff. At all.
If you want root after installing this, just install Superuser.apk from the market.
Bell_FR_2.2.2.zip (Froyo not France)
(md5 e431b4cc3ba7e3a27b6aad6982a31066)
Cheers!Oh, I forgot to mention, this is not quite stock, there are su and sudo binaries in /system/bin. Just install Superuser.apk to be rooted. they haven't been a problem for doing an OTA yet, but they are easy enough to remove if it comes up.
unlocked-fixed-Bell-2.2.2.zip
Mirror: unlocked-fixed-Bell-2.2.2.zip
Damn, nice work as always, man! This should come in handy for lots of us Bell Atrix users that feel left out. Lots will appreciate this!
When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?
So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?
Will you eventually be able to compile a zip for Bell gingerbread?
IrshaadH said:
Will you eventually be able to compile a zip for Bell gingerbread?
Click to expand...
Click to collapse
the problem would be hosting it, not sure how he would be able to do that.
akurit said:
When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?
So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?
Click to expand...
Click to collapse
keeping in mind that this is only for the recovery with unlocked devices, what he means is that the CWM recovery that tenfar put out has a problem with int'l phones (pretty sure it's all int'l) where IN recovery (not just the normal ROM, like the problem we had before) only 300 and some mb of RAM is available. since this zip is over 300mb, it can't all load into your RAM properly with normal recovery.
NFH found this bug, and patched recovery for us so as to fix the RAM problem. the two files attached are fixed recoveries for the two separate MBR versions of int'l devices.
to find what version you should use, connect to phone via ADB and then
Code:
adb shell
su
cat /proc/cmdline
and then search for the part of the output where it says "tegrapart=mbr:" and read that. it should have either "1100" or "d00" somewhere in it, use the CWM zip attached that has your respective output.
hope that clears up your question, if you have any further ask them in here.
IrshaadH said:
Will you eventually be able to compile a zip for Bell gingerbread?
Click to expand...
Click to collapse
Hi,
I believe y2whisper may be working on something like that. The point of getting back to stock 2.2.2 is to be able to apply the final OTA for Bell GB. Certainly something similar can be done for any firmware you want to flash.
Cheers!
i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.
tried it again and it work
but seems like i have to fastboot flash it each time i want to use recovery
akurit said:
i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.
tried it again and it work
but seems like i have to fastboot flash it each time i want to use recovery
Click to expand...
Click to collapse
I know what you are talking about, but I got that with a stock bootloader.
If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.
Cheers!
Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.
CWM_INT_Recovery.zip
(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)
NFHimself said:
I know what you are talking about, but I got that with a stock bootloader.
If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.
Cheers!
Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.
CWM_INT_Recovery.zip
(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)
Click to expand...
Click to collapse
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.
raybond25 said:
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.
Click to expand...
Click to collapse
Hi,
Sure, it's just replacing the word recovery with boot and having the right boot images in the file.
Cheers!
yes its zipping now. off to bed but tomorrow I will back up my stuff and attempt to flash to see if it works.
@akurit
I forget off the top of my head but there is a file that you just have to delete to prevent that. the file just flashes the old recovery on every reboot. get rid of that and you will be fine.
Awesome work! This makes it much easier to get back to 2.2.2
Its installing now!
now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.
ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.
This is why hehee
tenfar said:
......
Please Remove install_recovery.sh located in your /system/etc/ ,so that the recovery will not be overwrite to stock one.........
Click to expand...
Click to collapse
now it remains unlocked and I have recovery even if i reboot... but the ram issue still exists
y2whisper said:
Its installing now!
now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.
ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.
Click to expand...
Click to collapse
i could test it for you, i should be able to tell if it works alright or not, since i'm starting from an AT&T build of 2.3.4. would i have to head back to stock Bell using Gobstopper before i use your package too? i got a whole buncha time on my hands this week, so i should be able to test it however you want.
anyone try flashing the bootloader and radio?
kevnb said:
anyone try flashing the bootloader and radio?
Click to expand...
Click to collapse
Hi,
I have tested it, no problems, but went back to IHOP and the ram-fixed bootloader for 2.2.2 in the OP so recovery will work.
Also, the file install_recovery.sh located in your /system/etc/ doesn't exist in the Gobstopper, so that isn't causing recovery to be generated by patching boot.
Cheers!
So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.
I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome
y2whisper said:
So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.
I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome
Click to expand...
Click to collapse
Hi,
What recovery are you using, if it's not ram fixed you are going to run into situations where you don't have enough space to flash it.
Cheers!
ahhhh.
you know i was wondering if that was it. I even repackaged the recovery thinking it would be the cause.
I don't believe I was ram fixed at the time of the backup. So I am thinking either, have custom recovery flashed in that spot, or change the order to where recovery gets flashed after.
Just a quick background, I purchased my DS7 at staples and rooted it and installed CWM using the info found on the forums so I could connect to my ad-hoc tether. Last week I attempted to install the HC upgrade and got the mis-match message. I booted into CWM and started looping. In an effort to correct this I mistakenly wiped the memory (big mistake!). I found the instructions on flashing the stock ROM (turned out that it was TMO) and got the unit running again. I called Dell (I have posted in another thread on this) and they are to send a pickup. In the meantime I have found instructions on flashing the OEM stock wfi ROM and have done so. I, like many others, noticed that the service tag was wrong and edited PG23/line220 to reflect my correct tag ( note to posters of ROMs and those who would flash: before doing so write down all the information about your unit so you can make changes later if needed). I now have most everything back to pre-upgrade status, but Gingerbreak v1.2 will not root. When I attempt it the program runs but I get a message “Not sure what happened her. Either the exploit failed or the reboot failed. Please reboot manually and see if you have Superuser!” I reboot and nothing, no Superuser and no root access. Also, before I attempt the “unroot’ option is greyed out so I take it that the unit is not rooted nor can I see root files in file manager One thing I have not tried is the CWM un-install that was included in the stock ROM flash thread. Since I don’t see it and I boot into fastboot I am guessing that it is gone. Any suggestions or has anyone had this issue as well?
Another note, I too have the 338 version and no auto update yet. I am not real sure I want to update now. To those that have updated, can you connect to ad-hoc networks with out changing the WPA?
Big wall of text, if you're on 2.2.x reflash CWM 3.0 and flash Superuser.zip as a update.zip though it.
If you're on HC, flash CWM 4.0 and flash Superuser7.zip on it.
Superuser.zip will always work on 2.x roms.
Superuser7.zip will always work on 3.x roms.
If you try and run the wrong one it will just 'run' and give no error, it will simply not do anything, but it wont damage anything.
Thanks, you think cwm is still lurking and giving problems? So I need to reinstall cwm and use it to install the zip? Won't CWM interfere with the HC update?
alchrisr01 said:
Thanks, you think cwm is still lurking and giving problems? So I need to reinstall cwm and use it to install the zip? Won't CWM interfere with the HC update?
Click to expand...
Click to collapse
If you have CWM installed you won't get the update automatically no matter if you have a matching ROM or not... you must be FULLY stock... but I see no sense in waiting, TheManii has already posted the releases that are coming out... why not just flash the zip
Hi everyone,
im a newbie android user, have my device for barely 2 weeks.
i have a couple of questions on my mind, questions i tried googeling answers to for days now,
as i didnt find clear cut answers, im asking for your help.
i know i can flash a the stock 4.3 rom using custom recovery (i use TWRP) but that will result in wiping my data.
im interested in updating my AT&T HTC One to 4.3 without losing my data.
note that i currently have an unlocked bootloader, root (supersu) and im S-OFF (used Revone)
i already figured that i need to unroot my device and re-lock the bootloader in order to receive the OTA update properly.
my questions are as follows:
1) do i need to flash back to stock recovery in order to update or is unrooting and relocking bootloader good enough?
2) since im S-OFF, updating to 4.3 will update my hboot but will keep me S-OFF? or will it turn it on? or maybe it wont even update and stay on 1.44?
3) after i update to 4.3, re-unlocking my bootloader will once again wipe all data?
4) after updating to 4.3, in order to re-root my device i follow the same procedure i did on 4.1.2?
5) since im not using an AT&T sim card, i had to flash some wifi files in order to bypass carrier check and turn on wifi tethering, i imagine im gonna have to do that again on 4.3, will the same files work or will i need to wait for a new hack\workaround to come out? (i used: http://forum.xda-developers.com/showthread.php?t=2285047)
i have a few more questions that i cant recall right now, too much google digging for info got me confused.
will add them if\when i remember.
Thanks in Advance.
You don't need to relock bootloader or remove root, you do need stock recovery and stock ROM. Hboot will be updated, S-Off will remain. Your data will not be lost. Follow same procedure for root.
BenPope said:
You don't need to relock bootloader or remove root, you do need stock recovery and stock ROM. Hboot will be updated, S-Off will remain. Your data will not be lost. Follow same procedure for root.
Click to expand...
Click to collapse
Thank you for the quick reply.
a few followup questions if u dont mind.
1) where do i get the stock recovery files?
2) how can i identify the correct ROM associated with htc one 4.3? i know i need to use Cingular as my HTC is an AT&T one, but the roms versions are listed by AT&T firmware.
3) do i flash stock recovery and then do a regular OTA update?
Nexaddo88 said:
Hi everyone,
im a newbie android user, have my device for barely 2 weeks.
i have a couple of questions on my mind, questions i tried googeling answers to for days now,
as i didnt find clear cut answers, im asking for your help.
i know i can flash a the stock 4.3 rom using custom recovery (i use TWRP) but that will result in wiping my data.
im interested in updating my AT&T HTC One to 4.3 without losing my data.
note that i currently have an unlocked bootloader, root (supersu) and im S-OFF (used Revone)
i already figured that i need to unroot my device and re-lock the bootloader in order to receive the OTA update properly.
my questions are as follows:
1) do i need to flash back to stock recovery in order to update or is unrooting and relocking bootloader good enough?
2) since im S-OFF, updating to 4.3 will update my hboot but will keep me S-OFF? or will it turn it on? or maybe it wont even update and stay on 1.44?
3) after i update to 4.3, re-unlocking my bootloader will once again wipe all data?
4) after updating to 4.3, in order to re-root my device i follow the same procedure i did on 4.1.2?
5) since im not using an AT&T sim card, i had to flash some wifi files in order to bypass carrier check and turn on wifi tethering, i imagine im gonna have to do that again on 4.3, will the same files work or will i need to wait for a new hack\workaround to come out? (i used: http://forum.xda-developers.com/showthread.php?t=2285047)
i have a few more questions that i cant recall right now, too much google digging for info got me confused.
will add them if\when i remember.
Thanks in Advance.
Click to expand...
Click to collapse
Just a quick question: why do you want to go through all that hassle to receive the OTA? Since you're S-Off you're able to flash unsigned firmware. The only reason I can think of using OTA, is if someone is S-On and therefore cannot update firmware; an unlocked bootloader allows you to flash ROM, kernel, and radio, but not firmware. with S-Off you CAN do that.
One piece of advice, in either case, DO NOT GO S-ON EVER!
Or did I misunderstand you?
nkk71 said:
Just a quick question: why do you want to go through all that hassle to receive the OTA? Since you're S-Off you're able to flash unsigned firmware. The only reason I can think of using OTA, is if someone is S-On and therefore cannot update firmware; an unlocked bootloader allows you to flash ROM, kernel, and radio, but not firmware. with S-Off you CAN do that.
One piece of advice, in either case, DO NOT GO S-ON EVER!
Or did I misunderstand you?
Click to expand...
Click to collapse
i thought that flashing the new ROM will wipe my data, where an OTA update wont, or did i misunderstood?
also got an answer to the question about the wifi tether?
Nexaddo88 said:
i thought that flashing the new ROM will wipe my data, or did i misunderstood?
Click to expand...
Click to collapse
There are files in the firmware.zip that wipe the phone, removing those files means it won't wipe. Often boot.img and recovery.img are also removed from the firmware you download from here.
Nexaddo88 said:
i thought that flashing the new ROM will wipe my data, or did i misunderstood?
Click to expand...
Click to collapse
What do you mean by data? your internal storage/sdcard with pictures, music, etc. or your apps?
When flashing a new ROM with different base (eg 4.2.2 to 4.3) a wipe is recommended (that would wipe your apps and their data, not sdcard), but you could use Titanium Backup, Helium, etc. to back those up and restore.
You can do a dirty flash, which would not wipe your apps, but could lead to some potential problems with some apps; in which case you would need to reflash with wipe.
Anyhow, be careful with going back to stock first, because when you flash the stock recovery, it will/could wipe your phone completely including sdcard. Happened to me while I was testing a few things, and just flashing stock recovery and accessing it, wiped my apps and sdcard.
Hit us with some more details, what ROM (etc.) are you on now, and where do you want to go.
This is where I am now (attached pics)
I would simply like to upgrade my HTC to 4.3
I would like to do that without the hassle of wiping my phone and restoring apps data.
But if it's necessary I'm willing to backup and restore the apps data.
As u said, my SD CARD contents will no be deleted? ie photos, music etc.
From what u guys told me, I gather that doing an OTA is not as simple as I thought.
Can u please tell me the easiest way to upgrade?
or even better, what my options are?
2nd pic attached, for some reason it let me attach only 1 pic.
Thanks in Advance!
Nexaddo88 said:
2nd pic attached, for some reason it let me attach only 1 pic.
Thanks in Advance!
Click to expand...
Click to collapse
In my humble opinion, you should do a full back up of everything (nandroid, apps+data AND sdcard) and copy all that to your PC.
Whichever way you proceed, you're going to be moving from Android 4.1.2 to 4.2.2+, that will change the file structure on your phone: in 4.1.2 sdcard points to /data/media/ but as of 4.2.2+ it now points to /data/media/0/ (this is due to multiuser support in 4.2.2+).
For some, whether OTA or flashing a custom ROM, three things have happened:
1- the sdcard (pictures, music, etc) files were moved correctly to /data/media/0
2- the files were duplicated in /data/media AND /data/media/0, so they had to manually delete the duplicates (root enabled file explorer needed)
3- the files were not moved at all, and had to be manually moved from /data/media/ to /data/media/0/ (root enabled file explorer needed)
Note: that once you're on 4.2.2+ /data/media/ will no longer show up when you connect to your PC, only /data/media/0, hence why you need a root enabled file explorer to access /data/media/
If it was me (and I like a clean phone ), I would flash the new custom ROM in recovery, then while still in recovery format the /data/media/ (/sdcard/), boot up and let the ROM setup the sdcard as brand new.
And then setup the device from scratch. Copying all pictures, music, etc. back using your PC.
For backup/restore of USER apps & data, I would take a look at these:
* Titanium Backup
* Helium
* SMS Backup & Restore
* Call Log Backup & Restore
and possibly the built in HTC Backup.
Titanium can back up the data of system apps, but it's not recommended to restore these especially between the large gap from 4.1.2 to 4.3; usually you could restore WiFi, Bluetooth and a few more settings, but there have been reports that due to the changes in all of these, the restore of system data could/was causing problems.
Finally, if you want to upgrade your firmware, use vomer's guide here: http://forum.xda-developers.com/showthread.php?t=2365506. The firmwares there have boot.img (so no need to reflash RIM), recovery.img (so no need to reflash custom recovery) removed as well as the files that would wipe the sdcard. So you can flash the firmware without any negative effects.
Of course you could just do all the backups, and try dirty flashing (without wipe), and see how that works out for you. In case you run into problems (eg apps force closing, missing widgets, bad Wifi, bluetooth, or mobile data), you can then reflash with full wipe.
This is all my personal opinion, so don't know if anybody disagrees with my thoughts.
EDIT: if you use CWM recovery, you should also take a look at this after upgrading: http://forum.xda-developers.com/showthread.php?t=1991657
Hit the thanks button if I helped
Sounds good. Tyvm!!!
I'd like a clean phone as well.
So lets me know if I get it straight:
1) flash Rom in recovery (after backing up media and/or non-system apps)
2) wiping SD CARD clean
3) flash firmware in recovery
4) flash radio in recovery
Did I get it right?
Again thanks on advance
Nexaddo88 said:
Sounds good. Tyvm!!!
I'd like a clean phone as well.
So lets me know if I get it straight:
1) flash Rom in recovery (after backing up media and/or non-system apps)
2) wiping SD CARD clean
3) flash firmware in recovery
4) flash radio in recovery
Did I get it right?
Again thanks on advance
Click to expand...
Click to collapse
Yes pretty much, the most important part is the backup, I would do:
1- a nandroid backup in recovery (just in case you want to come back to that)
2- perform a Titanium Backup/Helium of everything (you don't need to restore system apps/data, but it's good to have them anyway)
3- perform HTC Backup (I do it, but have never restored from it yet)
4- copy everything from the sdcard (which would include above) to PC
firmware (modified versions by vomer) and/or radio can be flashed at any time without any risk of loosing apps or sdcard.
You should be good to go.
PS: In case you format sdcard and /system/ and find yourself without an OS (by accident), you will have to use 1 of 3 methods to get the ROM you want to flash on the phone:
1- adb sideload
2- adb push
3- OTG cable
Which firmware and radio version I need?
Whats the modification done in vomer's firmwares? Just removed files to prevent data wipe?
Nexaddo88 said:
Which firmware and radio version I need?
Whats the modification done in vomer's firmwares? Just removed files to prevent data wipe?
Click to expand...
Click to collapse
Firmware and radio are pretty much up to you; especially radio, where newer doesn't always mean better, it's very user specific, but you can flash them so easily in recovery back and forth. (I have them on my phone all the time and experiment depending on my location)
Also, just remember once you go to 2.x firmware or above the touchscreen drivers will no longer work with a 4.1.2 ROM, but then again why would you want to go back
The files in vomer's firmware that are removed are:
1- stock kernel (boot.img), otherwise you'd have to reflash ROM.zip after updating firmware
2- stock recovery (recovery.img), otherwise you'd have to reflash custom recovery after updating firmware
3- I don't recall, but some firmware package had a files in them that would wipe the sdcard (but haven't seen those for a while)
Firmware and radios are all available in vomer's guide: http://forum.xda-developers.com/showthread.php?t=2365506
about wiping the /data/media/ folder after flashing the ROM,
will i be prompted to do it or i'll do it manually?
sorry for all the questions, i know i can see for myself when i actually do it, but im scared since its my first android device ever
ty.
Nexaddo88 said:
about wiping the /data/media/ folder after flashing the ROM,
will i be prompted to do it or i'll do it manually?
sorry for all the questions, i know i can see for myself when i actually do it, but im scared since its my first android device ever
ty.
Click to expand...
Click to collapse
you'll have to do it manually, I'm using CWM, so I have to go to "mounts and storage" and then "format /data and /data/media (/sdcard)"
hmm, on that thought after formatting and booting up your ROM, check if all the apps are there, some get installed to /data/app, and I wonder if the above would delete those.
Wouldn't be a big deal, you would just copy the ROM back to your sdcard using your PC and reflash it. (Maybe do that anyway)
At least you know you'll have a clean sdcard without any possibility of duplicates or other files you no longer need (eg temporary files from some apps)
Alright, I've done it!!!
Upgraded to 4.3 stock Rom, which came with 3.17 firmware.
(used: http://forum.xda-developers.com/showthread.php?t=2476204)
Flashed AT&T OTA radio.
Even found a new tether hack for 4.3 that will allow me to activate tethering while not on AT&T network
Thanks a lot for all the help,
Much appreciated.
One more question tho if that's ok,
Are there any downsides to upgrading my firmware from 3.17 to the latest 3.62?
Nexaddo88 said:
Alright, I've done it!!!
Upgraded to 4.3 stock Rom, which came with 3.17 firmware.
(used: http://forum.xda-developers.com/showthread.php?t=2476204)
Flashed AT&T OTA radio.
Even found a new tether hack for 4.3 that will allow me to activate tethering while not on AT&T network
Thanks a lot for all the help,
Much appreciated.
One more question tho if that's ok,
Are there any downsides to upgrading my firmware from 3.17 to the latest 3.62?
Click to expand...
Click to collapse
Congratz.
As for firmware, I can't think of any downsides to upgrading it. Since you're S-Off you can always downgrade it back to 3.17 if you find any incompatibilities, though I dont think there will be any.
Alright ty.
The current firmware I have is 3.17.502...
Which came with the Rom.zip I flashed
I only found 3.17.402... on xda
Would u happen to know where I could get 3.17.502... ??
As I wouldn't want any problems or incompatibilities with the 402 one.
Also should I bother updating my hboot (if it's even possible)??
Thanks again.
Nexaddo88 said:
Alright ty.
The current firmware I have is 3.17.502...
Which came with the Rom.zip I flashed
I only found 3.17.402... on xda
Would u happen to know where I could get 3.17.502... ??
As I wouldn't want any problems or incompatibilities with the 402 one.
Also should I bother updating my hboot (if it's even possible)??
Thanks again.
Click to expand...
Click to collapse
Are you sure the ROM.ZIP contained firmware?? Usually, ROM.ZIP only contains the ROM and firmware is separate; also because the two have different flashing methods:
1- custom ROM is flashed using custom recovery
2- firmware is flashed in fastboot RUU mode
can you post a "fastboot getvar all" (remove IMEI and s/n before posting) to see the details.