Related
Do we have nandroid with full backup/restore of all partitions working yet?
If so, some instructions would be greatly appreciated
we wont have nandroid until we have a custom recovery image and possibly full /system access
So... are we seeing any progress in the nandroid department yet?
I distinctly remember seeing a twitpic (from Paul?) of a Desire running custom recovery image so that shouldn't be a problem.
What's holding it back?
You can make nandroid backups from the recovery....
abats said:
You can make nandroid backups from the recovery....
Click to expand...
Click to collapse
That's precisely what I thought.
Golgo said:
So... are we seeing any progress in the nandroid department yet?
I distinctly remember seeing a twitpic (from Paul?) of a Desire running custom recovery image so that shouldn't be a problem.
What's holding it back?
Click to expand...
Click to collapse
I'm sure he said it wasn't a recovery image, but just an app/script. In any case, if we run the recovery script we have the NAND backup/restore options amongst the others (wipe/partition/etc).
alex101uk said:
we wont have nandroid until we have a custom recovery image and possibly full /system access
Click to expand...
Click to collapse
Can you elaborate on this please? You can write /system (and probably any other partition) from within the recovery.
Run the step2.sh from Paul's given files, and you'll see a quick adb shell and mount /system gives full rw to /system.
Really? And it's fully working?
I've been reluctant to try other roms until I knew nandroid was a go.
So just to be crystal clear - I can take a nandroid backup of EVERYTHING, the full stock-rom incl. every partition and restore it later just as easily?
Golgo said:
nandroid backup of EVERYTHING, the full stock-rom
Click to expand...
Click to collapse
Nope (unless you invent/modify the method yourself using the RUU and recovery shell - not 100% sure it's possible). You can only nandroid what's on there past Pauls rootedupdate.zip if you use his instructions.
jayshah said:
Nope (unless you invent/modify the method yourself using the RUU and recovery shell - not 100% sure it's possible). You can only nandroid what's on there past Pauls rootedupdate.zip if you use his instructions.
Click to expand...
Click to collapse
Ok, so you cant make a full backup of /system, /data etc?
Too bad. nandroid is damn handy when you'r messing around with custom roms!
Nandroid make full back as usual. I used it many times without any issues when playing with different desire roms.
Golgo said:
Ok, so you cant make a full backup of /system, /data etc?
Too bad. nandroid is damn handy when you'r messing around with custom roms!
Click to expand...
Click to collapse
Of course you can. I said you can nandoid past Pauls update, and not the stock ROM as you said.
jayshah said:
Of course you can. I said you can nandoid past Pauls update, and not the stock ROM as you said.
Click to expand...
Click to collapse
Ah, alright. Shame
Im new to this so let me get this right, I currently have a rooted stock ROM by Paul using the original linux rooting method. Can I use nandroid to back up this up and then flash a cooked ROM and if I do not like it then I can use the back up to reflash back to where I was?
Nekromantik said:
Im new to this so let me get this right, I currently have a rooted stock ROM by Paul using the original linux rooting method. Can I use nandroid to back up this up and then flash a cooked ROM and if I do not like it then I can use the back up to reflash back to where I was?
Click to expand...
Click to collapse
Yes. If you nandroid restore, it will be as if absolutely nothing has changed (excluding any SD card data changes).
jayshah said:
Yes. If you nandroid restore, it will be as if absolutely nothing has changed (excluding any SD card data changes).
Click to expand...
Click to collapse
thanks
I still need to push the recovery files in order to get into the recovery menu in order to flash etc. Will that mean I cant nandroid my current ROM?
That's something I've wondered for a bit - can you push the recovery files (step 2) without doing step 1? And if so, can you trigger a nandroid backup on it?
I don't THINK you can, but I skipped it entirely, so it might be worth trying. Worst thing that happens is it fails, right? Can you get into recovery without rooting?
The Professor said:
That's something I've wondered for a bit - can you push the recovery files (step 2) without doing step 1? And if so, can you trigger a nandroid backup on it?
I don't THINK you can, but I skipped it entirely, so it might be worth trying. Worst thing that happens is it fails, right? Can you get into recovery without rooting?
Click to expand...
Click to collapse
I cant get into the custom recovery menu without pushing the recovery files so I think we need a custom ROM to be able to get into the recovery menu directly from the phone.
The Professor said:
That's something I've wondered for a bit - can you push the recovery files (step 2) without doing step 1? And if so, can you trigger a nandroid backup on it?
Click to expand...
Click to collapse
Yes, this is exactly what I did. I have a recovery.sh file which is just step2.sh without the push of rootedupdate.zip each time.
Code:
# pwd
/sbin
# ./nandroid-mobile.sh -b
cp: './nandroid-mobile.sh' and '/sbin/nandroid-mobile.sh' are the same file
nandroid-mobile v2.2.1
Using G1 keyboard, enter a prefix substring and then <CR>
or just <CR> to accept default:
Using - prefix to create a backup folder
mounting system and data read-only, sdcard read-write
checking free space on sdcard
Dumping boot to /sdcard/nandroid/HT044PL07434/BCDMRS-20100505-1350/boot.img...done
Dumping recovery to /sdcard/nandroid/HT044PL07434/BCDMRS-20100505-1350/recovery.img...done
Dumping misc to /sdcard/nandroid/HT044PL07434/BCDMRS-20100505-1350/misc.img...done
Dumping system to /sdcard/nandroid/HT044PL07434/BCDMRS-20100505-1350/system.img...done
Dumping data to /sdcard/nandroid/HT044PL07434/BCDMRS-20100505-1350/data.img...done
Dumping cache to /sdcard/nandroid/HT044PL07434/BCDMRS-20100505-1350/cache.img...done
generating md5sum file...done
unmounting system, data and sdcard
Backup successful.
#
Edit: Running a nandroid using the GUI method worked too, the 2nd time. 1st time failed, hence I did it manually above.
-edit- hm, got this
Code:
Using - prefix to create a backup folder
mounting system and data read-only, sdcard read-write
checking free space on sdcard
mtd: MEMGETBADBLOCK returned 1 at 0x00240000 (errno=0)
Dumping boot to /sdcard/nandroid/HT03WPL08829/BCDMRS-20100511-1419/boot.img...mt
d: MEMGETBADBLOCK returned 1 at 0x00240000 (errno=0)
done
.
.
.
.
Backup successful.
#
what does this mean?
Recovery Features:
Updated nandroid and recovery to support newer HTC devices using emmc instead of mtd.
Full support of Amend, Edify, & Busybox Mount Update(r) scripts
Correct auto detection of file system types on sd-ext, system, cache, and data.
Capacitive keys function. V3.0.3
Unlike clockwork you can wipe and not lose your file system type. On clockwork wiping resets your fs to ext3 on /system, /cache, and /data. This one will leave an ext4 file system intact after a wipe.
ADB as root user
USB-MS Toggle :mounts sdcard as mass storage
Backup/Restore:
Nand Backup : Select Items to backup with the [X]
Nand Restore : browse to and select nandroid backup to restore
Nand Restore Clockwork: browse to and restore cwm 3x, 4x, 5x backups
Flash Zip From Sdcard: Update.zip must be in root of sdcard or you can directory browse. Use the "../" to move back a directory
Toggle Signature Verify : Turn of signature checking on flashing zips
Wipe Menu:
Wipe data/factory reset: wipes all (minus full sdcard)
Wipe cache
Wipe Dalvik cache : Wipes Dalvik cache in all possible locations if moved by apps2sd
Wipe SD:ext : Wipes Apps2sd ext partition
Wipe Battery Stats
Wipe rotate settings
Wipe data only
Wipe Sdcard
Wipe .android secure : Wipes .android_secure on sdcard
Partition Sdcard:
Partition SD: Partition's sdcard for apps2sd (this formats card so all non backed-up data is lost)
Repair Sd:ext
SD:ext2 to ext3 : coverts apps2sd ext2 partition to ext3
SD:ext3 to ext4 : same as above but ext3 to ext4
Other:
Fix apk uid mismatches
Move recovery log to SD
Key Test : Output keycodes for debugging recovery
Check battery level
Ext3|4 menu: Formatting and reformating of partitons
Developer menu:
Make and flash boot from zimage : This makes a mkboot folder on sdcard and mounts sdcard as mass storage then you copy a zImage and kernel modules into this folder and it will create a new boot like anykernel and flash it.
Toggle full ext wipe: Toggles full or quick wipe of ext partitions
Install su & superuser: Installs or fixes su & superuser install (removes old if exists)
Install eng (unguarded) su: Installs engineering su that doesn't use superuser (removes old su & superuser if exists)
Reboot to bootloader: reboots to bootloader/hboot
Reboot recovery : reboots phone back into recovery
Trouble Shooting:
1. Use option under Other menu to move recovery log to sd. Mount your sdcard to pc and read that file called recovery.log. It should have detailed cause of error.
Navigation:
Vol-up & Vol-dn = move up & down
Power = select
POWER+VOLUP+VOLDN will auto reboot you out of recovery.
Back = backup or use the -Return menu item
Special Thanks:
Amon_RA for his source code Buy him a redbull
Team Unrevoked & AlphaRev for the s-off
Koush source code
worstenbrood source code for modded desire recovery
Teamwin recovery
jhansche for 3 button navigation on ra recovery.
Github Source
Developer's note: This can easily be ported to any other Emmc HTC's with minimal effort. For mecha, vision, lexikon etc. only change of kernel and default.prop is needed. Recovery binary and scripts will fully work. For devices like shooter the partitions in roots.c will need to be updated as well as fstab.
Changelog: 3.06
Clockwork restore option
Compiled for armv7a-neon so its faster
Added developer menu
Ext3|4 menu using C instead of script now.
Changelog : 3.0.3
Enabled capacitive keys and back now functions to backup one menu.
Re-added Mounts menu
Changelog : 3.04
Signature Checking is off by default
Fixed critcal error in nandroid that caused fail of boot.img restore
Changelog : 3.05
Added ability to restore CWM backups 3x-5x.
Cleaned up some code that could produce an error in the ext3 - ext4 upgrade/downgrade causing script to fail.
Download Section:
fastboot version :
Current recovery-ra-vivow-3.06-gnm.img
MD5= c2e2f9af9607e9334b5e268c7b23e050
old recovery-ra-vivow-3.03.img.zip
MD5 = 2f8ed4661c86f03b7e410c7b0511b2c4 recovery-ra-vivow-3.03.img.zip
old recovery-ra-vivow-3.02.img.zip
MD5 = 47efcf557dc8e233ab9213636f88426b recovery-ra-vivow-3.02.img.zip
Unzip and flash via fastboot with command
Code:
fastboot flash recovery NAMEOFRECOVERY.img
Hboot version : PG32IMG-ra-vivow-3.04.zip
MD5 = c8f95411729ef74fc03bcb679cab857d
old PG32IMG_recovery-ra-3.03.zip
MD5 = d174c23abdf85f99a0233d11c4beda27 PG32IMG_recovery-ra-3.03.zip
old PG32IMG_recovery-ra-vivow-3.02.zip
MD5 = 9f4792175d007bdf151bcce9b21e7f2b PG32IMG_recovery-ra-vivow-3.02.zip
rename above file to PG32IMG.zip and place on root of sdcard and boot to hboot to flash.
Havent tried it yet but flashed it. Would it be possible to make an easier way to go back? Instead of having to select the return or ../ option. Anyways thanks for this.
mbh87 said:
Havent tried it yet but flashed it. Would it be possible to make an easier way to go back? Instead of having to select the return or ../ option. Anyways thanks for this.
Click to expand...
Click to collapse
Not with only 3 mapable keys. If we had a 4th hardware key yes but we don't. Navigation is same as clockwork unfortunatly.
drellisdee said:
Not with only 3 mapable keys. If we had a 4th hardware key yes but we don't. Navigation is same as clockwork unfortunatly.
Click to expand...
Click to collapse
The soft keys work in clockwork though which is nice. Like the layout of this recovery better so I guess I just gotta pick which things bug me less lol.
mbh87 said:
Havent tried it yet but flashed it. Would it be possible to make an easier way to go back? Instead of having to select the return or ../ option. Anyways thanks for this.
Click to expand...
Click to collapse
mbh87 said:
The soft keys work in clockwork though which is nice. Like the layout of this recovery better so I guess I just gotta pick which things bug me less lol.
Click to expand...
Click to collapse
Good suggestion. I added it. Version 3.0.3 has the capacitive keys working and the option to use the menu item -Return or the capacitive back key to backup a menu.
drellisdee said:
Good suggestion. I added it. Version 3.0.3 has the capacitive keys working and the option to use the menu item -Return or the capacitive back key to backup a menu.
Click to expand...
Click to collapse
Awesome, thank you!
Sweet, Amon Ra works great on my old LG Ally.
Welcome to the Dinc2 club Drellisdee. I'm happy you're here.
^^^^^
x2, but used this recovery with my Droid Eris.
Good to see this recovery as another option vs. CWMR...
I LOVE IT!! Anyway to fix permissions ?
Sent from my ROOTED Incredible 2.
phillybizzle said:
I LOVE IT!! Anyway to fix permissions ?
Sent from my ROOTED Incredible 2.
Click to expand...
Click to collapse
Yep thats what this item does
Other:
Fix apk uid mismatches
one more ? how can I keep this as my permanent recovery? clockwork is sneaky and comes back
Sent from my ROOTED Incredible 2.
phillybizzle said:
one more ? how can I keep this as my permanent recovery? clockwork is sneaky and comes back
Sent from my ROOTED Incredible 2.
Click to expand...
Click to collapse
That shouldn't happen on this device. Check if you have a /etc/install-recovery.sh and if so delete it then reflash the recovery.
nope looked everywhere
Sent from my ROOTED Incredible 2.
only way clockwork should come back is if you flash it in ROM Manager or overwriting it elsewhere.
also to the OP, have you thought about porting the Team Win Recovery?
mbh87 said:
only way clockwork should come back is if you flash it in ROM Manager or overwriting it elsewhere.
also to the OP, have you thought about porting the Team Win Recovery?
Click to expand...
Click to collapse
TeamWin's official recovery currently doesn't support the ext3 filesystem, which we (the Inc2) use. Some of the unofficial ports for other devices do, but the ones that have added ext3 support (like the Tbolt port) seem to be dirty hacks at the moment. I was looking at porting it myself, but TeamWin said that they are adding support for a lot of additional devices, including the Inc2, so I'd be duplicating effort that's already ongoing
Will I be able to restore nands created by CWM recovery with this recovery?
Thanks.
slacka-vt said:
Will I be able to restore nands created by CWM recovery with this recovery?
Thanks.
Click to expand...
Click to collapse
no. Cwm and amon ra nandroids are not interchangeable. I'm not going to try to mess with team-win. I like ra recovery and thats what I use. IMO it is the best recovery option out there for all devices. FYI you can use manual flash override option in rom manager to make it not require flashing clockwork to use most of the features of it.
mbh87 said:
only way clockwork should come back is if you flash it in ROM Manager or overwriting it elsewhere.
also to the OP, have you thought about porting the Team Win Recovery?
Click to expand...
Click to collapse
so I.should flash any recovery in clockwork? anyway to flash this recoc
Sent from my ROOTED Incredible 2.
phillybizzle said:
so I.should flash any recovery in clockwork? anyway to flash this recoc
Sent from my ROOTED Incredible 2.
Click to expand...
Click to collapse
Preferred means of flashing are in 2nd post. Flash_image can also be used to flash from android or recovery but hboot zip and fastboot are easiest methods.
At this point there's no way to have full recovery backups through CWM. adb allows us to do almost the same.
Here's how:
Code:
$ adb shell
$ su
# stop
# busybox tar cf /mnt/external_sd/data.ext4.tar --exclude media --exclude dalvik-cache /data
# reboot
To restore:
Code:
$ adb shell
$ su
# stop
# busybox tar xf /mnt/external_sd/data.ext4.tar -C /
# reboot
This will not backup the internal sdcard "/data/media" it's likely too large, so it should be backed up manually.
tar is the same format CWM uses, so it should restore from Titanium Backup.
thanks for this! Every little bit helps.
eww245 said:
At this point there's no way to have full recovery backups through CWM. adb allows us to do almost the same.
Here's how:
Code:
$ adb shell
$ su
# stop
# busybox tar cf /mnt/external_sd/data.ext4.tar --exclude media --exclude dalvik-cache /data
# reboot
To restore:
Code:
$ adb shell
$ su
# stop
# busybox tar xf /mnt/external_sd/data.ext4.tar -C /
# reboot
This will not backup the internal sdcard "/data/media" it's likely too large, so it should be backed up manually.
tar is the same format CWM uses, so it should restore from Titanium Backup.
Click to expand...
Click to collapse
I've not tried this yet, but am wondering what and where the output file would be located. Would you be able to use this as a recovery method from one ROM to the saved ROM similarly to what is done with CWM?
tomlogan1 said:
I've not tried this yet, but am wondering what and where the output file would be located. Would you be able to use this as a recovery method from one ROM to the saved ROM similarly to what is done with CWM?
Click to expand...
Click to collapse
For the instructions posted an external sdcard is needed it would be in the root of the card. You can substitute external_sd with sdcard to save in to the internal memory.
And yes this can work just as CWM when switching ROMs. For example before upgrading to ICS. Then, if possible, flash back to Honeycomb and restore the backup.
eww245 said:
For the instructions posted an external sdcard is needed it would be in the root of the card. You can substitute external_sd with sdcard to save in to the internal memory.
And yes this can work just as CWM when switching ROMs. For example before upgrading to ICS. Then, if possible, flash back to Honeycomb and restore the backup.
Click to expand...
Click to collapse
Just to make sure I have done this, correctly, I have a file on my external sd called data.ext4. Should I wish to try another ROM, I would load the new ROM via the normal recovery method, and then if I wanted to restore from the data.ext4 file, I would use ADB to restore this file. Would this overwrite the existing ROM so I could , for instance, use ICS and then move back to HC? Looking at the data.ext4 file, it appears that all the applications have been backed up as well. Am I correct? Thanks.
tomlogan1 said:
Just to make sure I have done this, correctly, I have a file on my external sd called data.ext4. Should I wish to try another ROM, I would load the new ROM via the normal recovery method, and then if I wanted to restore from the data.ext4 file, I would use Titanium backup to restore this file and then use Titanium to also restore applications and data that I has backed up previously. Am I correct? Thanks.
Click to expand...
Click to collapse
Currently no one has made any roms, I guess because of no CWM which isn't needed, Theres only stock HC and stock ICS. Unfortunately ICS CAN'T be downgraded back to HC, previously I saw no mention of it being possible or not. Titanium backup is capable of restoring apps and data from a nandroid / tar. Which I don't own so I can't test it. Lets say you start getting a bunch of Force Closing apps and you have already made a tar backup. Then just fire up adb and restore it. Or you want to factory reset and start fresh, then install individual apps/data through Titanium from the tar, if even possible.
AppExtractor can also restore app data from a nandroid. Well, it doesn't work with my adb backup on the a100 but if I copy it to my phone AppExtractor has no problem reading the archive. I don't know about Titanium.
[edit]Just want to add to this post because it is actually possible to downgrage to HC. crossix has instructions here forum.xda-developers.com/showpost.php?p=22970185&postcount=147.
Also peporras opened a thread about it forum.xda-developers.com/showthread.php?t=1517286
eww245 said:
Currently no one has made any roms, I guess because of no CWM which isn't needed, Theres only stock HC and stock ICS. Unfortunately ICS CAN'T be downgraded back to HC, previously I saw no mention of it being possible or not. Titanium backup is capable of restoring apps and data from a nandroid / tar. Which I don't own so I can't test it. Lets say you start getting a bunch of Force Closing apps and you have already made a tar backup. Then just fire up adb and restore it. Or you want to factory reset and start fresh, then install individual apps/data through Titanium from the tar, if even possible.
AppExtractor can also restore app data from a nandroid. Well, it doesn't work with my adb backup on the a100 but if I copy it to my phone AppExtractor has no problem reading the archive. I don't know about Titanium.
Click to expand...
Click to collapse
I know there are no custom ROMS. If I wanted to try ICS, there there is no way to flash one of the stock ROMS back? Just wanted to be sure before I do something I would regret.
Thanks.
I am new here so sorry for this newbie question, I have tried the method in post 1 but I get the message tar: empty archive have I missed something? any help will be greatly appreciated. Many thanks in advance.
I have re-typed the commands and all seems ok.
Your not specifying any files to be tarred. The command should end with /data
eww245 said:
Your not specifying any files to be tarred. The command should end with /data
Click to expand...
Click to collapse
many thanks
eww245 said:
At this point there's no way to have full recovery backups through CWM. adb allows us to do almost the same.
Here's how:
Code:
$ adb shell
$ su
# stop
# busybox tar cf /mnt/external_sd/data.ext4.tar --exclude media --exclude dalvik-cache /data
# reboot
To restore:
Code:
$ adb shell
$ su
# stop
# busybox tar xf /mnt/external_sd/data.ext4.tar -C /
# reboot
This will not backup the internal sdcard "/data/media" it's likely too large, so it should be backed up manually.
tar is the same format CWM uses, so it should restore from Titanium Backup.
Click to expand...
Click to collapse
If you changed "data.ext4.tar" to "nameilike.ext4.tar" you would then be able to have a catalog of different setups you made, assuming some other ROMS in the future. The reason for this is the previous generation of CWM on the A500 used the date for the file name and if you had 5 or 6 you didn't know which was which.
[ROM] HTC Euro RUU 2.14.401.1_Radio_47.23e.35.3038M_7.57.39.01M_relea se_246629_signed
RUU_Marvel_S_HTC_Europe_2.14.401.1_Radio_47.23e.35.3038M_7.57.39.01M_release_246629_signed
Fast Mediafire downloaded for those looking for the latest Euro release.
Thanks to rezo for tracking it down.
Have you had any success in rooting this rom?
I can't get root, superuser is installed but apps are always denied.
Any ideas mate?
So this new ruu has problems with gaining root acess?
How to...
intel007 said:
Have you had any success in rooting this rom?
I can't get root, superuser is installed but apps are always denied.
Any ideas mate?
Click to expand...
Click to collapse
No issues.
Here's my install process to the letter:
1/ Backup all my apps using Titanium backup Pro
2/ Make a Nandroid backup
3/ Using ES File Explorer backup all apps to SD card
4/ Place MTD Partition files on SD card along with PG76IMG.zip extracted from RUU file
5/ Reboot to recovery and run recovery portion of MTD partitioning scripts with MTD set to 260 35
Clear Data, Cache, and System
6/ Reboot to recovery
7/ Run boot portion of recovery script
8/ Power down
9/ Run PG76IMG.zip at hboot and update everything
10/ Power down
11/ Remove PG76IMG.zip from SD card and replace it with Alquez's PG76IMG.zip that is clockwork recovery 5.0.2.6
12/ Place root.zip from the rooting section of general on on the SD card
Boot to hboot using power and down volume
12/ Run recovery update
13/ Power down
14/ Reboot to Hboot again and choose recovery
15/ Install zip from SD card and choose root.zip
16/ Reboot into OS and voila. Rooted.
17/ Download and install Rom Manager
18/ Updated Recovery to 5.0.2.8 using ROM manager
19/ Do what you want.
20/ Have fun doing it.
Extracting PG76.img from the RUU:
1/ Clear your user temp directory in windows
2/ Run the RUU update and leave it at the first prompt
3/ Locate rom.zip in your user temp directory
4/ Copy it out to your desktop, etc.
5/ Cancel out of the RUU update.
6/ Delete files from user temp directory
7/ rename rom.zip to PG76IMG.zip and place in root of SD card
8/ Flash that mofo.
aigaming said:
So this new ruu has problems with gaining root acess?
Click to expand...
Click to collapse
No issues at all.
Thanks mate, I'll give this another try when I get a chance.
Ok tnx for clearing this out,i will wait for more people to get this update and update it
I upgraded to RUU_Marvel_S_HTC_Europe_2.13.401.3_Radio_47.23c.35.3037_7.54.39.28M_release_236989
I wonder why do you need to do all that stuff with mtd and all does steps?
I do nandroid backup,install new ru and restore nandroid backup and everything works... (cm 7.2)
Do i miss something?
Any changelog apart from the new radio/hboot ?
comaX13 said:
Any changelog apart from the new radio/hboot ?
Click to expand...
Click to collapse
Off topic, and apologies. But I gotta say it. Your Yamas script for bt4/5 rules dude. Many thanks.
Could someone please help me up and upload the .zip file so that I can flash it through HBOOT?
Added to Index
Thanks I got root and after that I flashed the stock recovery again, so now I have stock recovery and I have root too
Hi there, I have a question. Since I have upgraded both RUU from your post is there a way we can flash latest firmware 2.26 and not lose s-off?
++++++++++++++++++++
All I did is check software update it download about 25mb. Then I click apply from the menu that come after download complete. It took several restart and upgrade my system flawlessly. I had Hboot-1.09.0099 after that. I flashed hboot 1.08.0000 from the previous rom u posted.
I think this two post should be combined.
I started with hboot 0.90.0000 that is the most important thing. hboot 0.90.000o is not compatible to many RUU. I bricked my phone twice now. LOL anyways
Hi,
I'm new here and I'd like to install a new ROM on my Gio but I want to make sure I know what I'm doing before trying something and bricking my phone. :angel:
ClockWorkMod
I installed CWM v5.2.0.6 (followed the instructions here). Is this ok, or do I need to install v5.0.2.7? And if I do need a newer version, is there a way to get an update or do I have to follow the same steps as before?
1.Download the CWM 5.0 v2 and copy to the Root (not in any folder) of your SD card
2. Put your phone in recovery Mode(press: Home button + Power button toghether)
3. In recovery mode, select the downloaded file from SD-card(Use Volume keys to navigate and home button for enter).
4. Search for the root gb updated.zip file on your SD-card
5. Run the update
6. Reboot
Click to expand...
Click to collapse
I tried creating a backup with the CWM version I have, but I get this error: "Can't mount /system".
CWM does create a folder in sdcard/ clockworkmod/ backup/ date, but it only contains the following files:
recovery.img and boot.img.
However, this post says I should actually have more files in the backup folder:
.android_secure.vfat.tar ,boot.img , cache.ext4.tar , data.ext4.tar , nandroid.md5 , recovery.img, system.ext4.tar.
Is this because of my CWM version? Or maybe because I still have the operating system that came with my device (+updates)?
What I really want to know is: can I rely on this backup, will it work?
ROMs
I want to install CM10.1.5 from here, but I have many questions and I don't really know where to look for answers. (Sorry, I really am a complete noob.)
What's the difference between androidarmv6 jenkins build and mardon build? And what's the difference between the 3 versions? Can I just install the Version with CM-Superuser and not worry about it?
Should the updates be installed via CWM - apply update from SDcard? What about the additions - CWM --> install zip from SDcard?
How can I install extras if they are "not CWM flashable"?
What happens to my apps when I install a new ROM? Do I have to install them all again? Is all data lost? Or will they all be restored from my google account and the SD card or something like that?
Finally, how can I use the ext2 partition in my SDcard to install apps? Is this function included in the ROM? Or do I need to install something else? a2sd darktremor? If yes, how (I find the instructions here confusing and overwhelming, and the post is old, so probably outdated)? Or should I use the "Link2SD" addition to the ROM?
I'm sorry for asking so much, but I'm feeling kind of lost.
Thanks in advance.
Anyone?
I've continued trying to figure things out when I have time. I'll post what I find in this thread, in case someone else comes here looking for answers to similar doubts/problems.
In trying to understand what's going on with ClockWorkMod Recovery, I found this very useful link:
wwwDOTtechbiiDOTcom / cwm-recovery-cant-mount-system-error-solution-how-to/
(sorry for the DOTs and spaces, can't post outside links yet)
CWM Recovery – Can’t Mount System Error Solution [How To]
(...)
The error is an expected one and happens generally when you are trying to backup a stock ROM using the clock work mod recovery. Please, note that you can’t do a completed nandroid backup of a stock firmwares. So, just install any custom ROM and then you can backup and restore anytime.
Click to expand...
Click to collapse
If I understood correctly, the best (only?) way to return to stock ROM is to install Odin or similar firmware flashing tool and to get the stock firmware from sites like sammobile.com and sampro.pl. However, it also says that not all firmwares might be available and I haven't looked more into it all of this yet.
Did you root your phone yet?
That should solve the problem from the can't mount system, data, etc
If you need more information, then look at this post http://forum.xda-developers.com/showthread.php?t=1397120
HerroYou said:
Did you root your phone yet?
That should solve the problem from the can't mount system, data, etc
If you need more information, then look at this post http://forum.xda-developers.com/showthread.php?t=1397120
Click to expand...
Click to collapse
Yes, I used the instructions there to root my phone and install CWM (v5.0.2.6), but that thread is 2 years old, so I'm afraid it won't be up to date in relation to certain things. For example, I did create an ext2 partition on my SD card using those instructions, but I found an easier way to move apps from my phone to the SDcard (using the link2SD app, available on Google Play). The information about ROMs is also not up to date.
If you want to install a custom rom just
-wipe data factory reset
-wipe cache partition
-advance>wipe dalvik cache
-install zip from sdcard
-reboot
NOTE: the zip is the rom
HerroYou said:
If you want to install a custom rom just
-wipe data factory reset
-wipe cache partition
-advance>wipe dalvik cache
-install zip from sdcard
-reboot
NOTE: the zip is the rom
Click to expand...
Click to collapse
Thank you.
My main concern at the moment is how to restore my original ROM if something should go wrong, though. I've found some interesting information in this thread but I've been busy this week and I'll need to go back and read it all with more attention before I try something.
Download ODIN 4.42 and GIO ops and a sotckrom MD5 file then put it into the odin and put your phone into recovery mdoe and plug it into your computer. Then click start
you have to put your phone in downloadmode to flash with odin as far as i know,but i have an other question;
can you use heimdall with the samsung galaxy gio
I am trying to flash a new recovery on my samsung galaxy gio with ODIN after it is bricked flashing tass- 6.0.4.5.zip(this cwm seems for the mini!!!) is this possible and if so,which one can?and how to do that...
thanks in advance
Yes it is possible and you need ODIN 4.42, GiPS and a Stock Rom extracted out of the zip.
Here is a video to help you because I am too lazy to explain
http://www.youtube.com/watch?v=euZqtaAMe5c