• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root AmonRa issues!

WA_Bob

WA_Bob

Android Expert
Okay, I know it's gotta be some sort of operator error. Lately, I've been doing AmonRa Nandroid backups, but when I try to restore my system with them I always get an error and it never works. I go with the default settings on my backups so can someone tell me what I'm doing wrong that prevents me from restoring my system from them? I'm very confused and rather annoyed! :confused:

Thanks for any insight!
 
the main thing is that you want to launch amon from fastboot:

fastboot boot <recoveryname>.img

if you are booting to amon that is permanently installed on your phone,your nandroids are NOT getting their boot images restored,as the recovery partition cannot write to the boot partition.

boot is writeable from fastboot,hence,launching recovery from fastboot makes it possible for the boot image to be properly restored. (recovery is now inside fastboot. sorta. ;))

sounds hokey,but it works,i promise ;) i have checked and verified that the kernels are changing when you restore from amon launched from fastboot.

your nandroid restore shoould automatically erase things first,but for some peace of mind:
-wipe data/factory reset
-wipe cache
-wipe dalvik cache
-wipe boot
-wipe system
*then restore

if you had amon back up the recovery image,you can uncheck that box,as amon is not able to restore a recovery.

hope that helps :)
 
Yes it does help. I'm so used to Clockwork Recovery and how that works that this is just different enough to confuse me. I'll give it another shot today like this and see what happens.
 
Epic Fail - no nandroid restore. AmonRa can move me forward to a new ROM, but I just can't make it give me back a nandroid. The best I can do is wipe, re-install the previous ROM, and at least get my apps back via Titanium. And here I thought I was doing pretty good navigating various Motorola Droids and the Thunderbolt. But the Rezound is just kicking my a** in the restoring my backups. CWM won't function for me on it and even using your method Scotty (Which I have read over and over again on multiple posts - you're a very patient guy!) and going back to XDA, I'm lost with this one. :confused:

I'm missing some connection here. And I know it's between my ears is the worst part! :eek:

I need a beer and a long afternoon to do some more reading........
 
maybe try and describe in as much detail as possible your procedure,and what happens after.

ive done it,and it does work... i havent done anything special to restore the backups(that i know of,anyway)

when you wiped "boot" was that successful?

do you have Xs by boot and system to restore?

im sure we can figure this out :)

edit: if youre using adb for anything,copy and paste the contents of your cmd box between
Code: 
 tags... that typically helps alot
 
WA_Bob said:
Epic Fail - no nandroid restore. AmonRa can move me forward to a new ROM, but I just can't make it give me back a nandroid. The best I can do is wipe, re-install the previous ROM, and at least get my apps back via Titanium. And here I thought I was doing pretty good navigating various Motorola Droids and the Thunderbolt. But the Rezound is just kicking my a** in the restoring my backups. CWM won't function for me on it and even using your method Scotty (Which I have read over and over again on multiple posts - you're a very patient guy!) and going back to XDA, I'm lost with this one. :confused:

I'm missing some connection here. And I know it's between my ears is the worst part! :eek:

I need a beer and a long afternoon to do some more reading........
Click to expand...

I feel ya there.

Before getting this Rez I was a flashaholic then screeeech.:eek:
 
Okay - here goes:

Code: 
C:\Android\android-sdk-windows\platform-tools>fastboot boot recovery-ra-vigor-3.
14-gnm.img
downloading 'boot.img'...
OKAY [  1.393s]
booting...
OKAY [  0.002s]
finished. total time: 1.396s

C:\Android\android-sdk-windows\platform-tools>

That puts me into RA-VIGOR. Next I go to "Wipe" and
-Wipe data/factory reset
-Wipe cache
-Wipe dalvik cache
-Wipe boot
-Wipe system

Ok - now to Restore>Nand Restore> my backupfile and the default checks are by:
- boot
- system
- data
- cache
- .android_secure

Then "Perform Restore" and "Restore backup?"

And then.......

"Restoring : .

Oops... something went wrong!
Please check the recovery log"

once again - fail.

So, any guess?
 
does your sd card have enuff room for another GB of backup? if youve got a rom on your sd card,some other pics,videos,and media,you can only fit a few nandroids on an sd card :eek:

also low battery charge can cause a similar message.

failing those 2 things,there should be an option to move the recovery log to SD. do that,then look on the SD for the log. post its contents here,or in a pastebin and post the link. :)
 
I checked before I started the process - 16 GB+ available on my external SD card and 65% on the battery before I got going. I've got the recovery file so here ya go:

Code: 
Starting recovery on Wed Feb 29 11:28:03 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (720 x 1280)
RA Revamped
Build : RA-VIGOR-v3.13-getitnowmarketing
Command: "/sbin/recovery"

ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
ro.ril.oem.ecclist=911,*911,#911
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.def.agps.mode=6
ro.ril.disable.fd.plmn.prefix=23402,23410,23411,23420
ro.ril.enable.sdr=0
ro.ril.oem.show.act=0
ro.ril.enable.gea3=1
ro.com.google.clientidbase=android-htc
ro.com.google.clientidbase.yt=android-htc
ro.com.google.clientidbase.am=android-verizon
ro.com.google.clientidbase.vs=android-verizon
ro.com.google.clientidbase.gmm=android-verizon
ro.com.google.clientidbase.ms=android-verizon
ro.product.model=ADR6425LVW
ro.aa.rid=224
ro.aa.skulist=605
ro.aa.customizationid=249206
ro.aa.taskid=221384
ro.aa.project=Vigor
ro.aa.mainsku=605
ro.aa.modelid=PH9810000
ro.aa.romver=1.02.605.6
ro.aa.maincid=VZW__001
ro.aa.cidlist=VZW__001
ro.build.id=GRJ22
ro.build.display.id=GRJ22
ro.build.version.incremental=183296.6
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.4
ro.build.date=&#26085; 10&#26376; 16 18:07:00 CST 2011
ro.build.date.utc=1318759620
ro.build.type=user
ro.build.user=root
ro.build.host=ABM019
ro.build.tags=release-keys
ro.product.brand=verizon_wwe
ro.product.name=htc_vigor
ro.product.device=vigor
ro.product.board=vigor
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=xhdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=msm8660
ro.build.product=vigor
ro.build.description=1.02.605.6 CL183296 release-keys
ro.build.changelist=183296
ro.product.ua=
ro.build.fingerprint=verizon_wwe/htc_vigor/vigor:2.3.4/GRJ22/183296.6:user/release-keys
ro.build.project=<CupcakeSKU.SKUInfo instance at 0xfa01b8>:221384
ro.product.version=1.02.605.6
ro.build.languageremove=0
ro.build.sense.version=3.5
keyguard.no_require_sim=1
ro.sf.lcd_density=320
debug.fb.rgb565=0
debug.composition.type=c2d
rild.libpath=/system/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
persist.rild.ril.ltedr=0
persist.rild.ril.ltedrtable=max_retries=infinite,10000
DEVICE_PROVISIONED=1
persist.cne.UseCne=false
persist.cne.bat.range.low.med=30
persist.cne.bat.range.med.high=60
persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist.cne.bwbased.rat.sel=false
persist.cne.snsr.based.rat.mgt=false
persist.cne.bat.based.rat.mgt=false
persist.cne.be.ge.sqi.min=0
persist.cne.be.ge.sqi.max=100
persist.cne.be.umts.sqi.min=0
persist.cne.be.umts.sqi.max=100
persist.cne.be.hspa.sqi.min=0
persist.cne.be.hspa.sqi.max=100
persist.cne.be.1x.sqi.min=0
persist.cne.be.1x.sqi.max=100
persist.cne.be.do.sqi.min=0
persist.cne.be.do.sqi.max=100
persist.cne.be.wlan.sqi.min=0
persist.cne.be.wlan.sqi.max=100
ro.use_data_netmgrd=true
persist.data_netmgrd_nint=16
persist.data_netmgrd_mtu=1428
ro.config.lte=true
ro.config.svlte1x=true
persist.radio.adb_log_on=1
ro.cdma.data_retry_config=max_retries=infinite,0,0,60000,120000,480000,900000
ro.gsm.2nd_data_retry_config=max_retries=3, 2000, 2000, 2000
ro.ril.enable.dtm=0
ro.ril.gprsclass=12
ro.ril.hsdpa.category=10
ro.ril.hsupa.category=6
ro.ril.hsxpa=3
ro.telephony.default_network=8
wifi.interface=eth0
wifi.supplicant_scan_interval=30
ro.opengles.version=131072
dalvik.vm.heapsize=48m
ro.ril.disable.power.collapse=1
ro.ril.enable.prl.recognition=1
ro.baseband.arch=svlte2a
ro.phone_storage=0
ro.ext4fs=1
ro.htc.checkin.url=http://andchin.htc.com/android/checkin
ro.htc.checkin.crashurl=http://andchin.htc.com/android/crash
ro.htc.checkin.url_CN=http://andchin.htccomm.com.cn/android/checkin
ro.htc.checkin.crashurl_CN=http://andchin.htccomm.com.cn/android/crash
ro.htc.checkin.exmsg.url=http://fotamsg.htc.com/android/extra/
ro.htc.checkin.exmsg.url_CN=http://fotamsg.htccomm.com.cn/android/extra/
ro.htc.appupdate.url=http://apu-chin.htc.com/check-in/rws/and-app/update
ro.htc.appupdate.url_CN=http://apu-chin.htccomm.com.cn/check-in/rws/and-app/update
ro.htc.appupdate.exmsg.url=http://apu-msg.htc.com/extra-msg/rws/and-app/msg
ro.htc.appupdate.exmsg.url_CN=http://apu-msg.htccomm.com.cn/extra-msg/rws/and-app/msg
ro.config.htc.nocheckin=1
ro.bt.chipset=Broadcom BCM4329-B1
ro.bt.stack=Broadcom BTL-A
ro.bt.stack.version=2.0.50.032
ro.bt.profiles=4270339
service.brcm.bt.activation=0
service.brcm.bt.srv_active=0
service.brcm.bt.hcid_active=0
service.brcm.bt.btld=0
service.brcm.bt.btld_pid=0
service.brcm.bt.avrcp_pass_thru=0
service.brcm.bt.avrcp_toggle=1
service.brcm.bt.local_name=
persist.sys.shutdown.mode=hibernate
ro.htc.common.version=2.0.0.0
ro.product.processor=1.5 GHz dualcore
ro.product.ram=1GB
ro.product.display_resolution=4.3 inch 720p resolution
ro.product.main_camera=8M
ro.product.front_camera=2M
ro.product.bluetooth=3.0
ro.product.wifi=802.11 b/g/n
ro.cdma.home.operator.numeric=310012
ro.cdma.home.operator.alpha=Verizon
ro.htc.device.slot1=RUIM
ro.htc.framework.screencapture=true
ro.HorizontalVVM=true
ro.HorizontalBUA=true
ro.modem.load.release_key=true
profiler.anr_dump_native_uid=9999
ro.sdcard2=1
keydispatchtimeout=15000
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.networklocation=1
ro.setupwizard.mode=DISABLED
ro.config.ringtone=QuietlyBrilliant.mp3
ro.config.notification_sound=Zeta.mp3
ro.config.alarm_alert=NewDay.mp3
ro.config.cal_notification=Epsilon.mp3
ro.config.msg_notification=Gamma.mp3
ro.com.google.gmsversion=2.3_r7
media.a1026.nsForVoiceRec=0
htc.audio.alt.enable=1
htc.audio.fluence.enable=1
htc.audio.hac.enable=1
lpa.decode=false
ro.setupwizard.enterprise_mode=1
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.modversion=RA-VIGOR-v3.13-getitnowmarketing
ro.factorytest=0
dev.silent_reboot=0
ro.serialno=HT19XS219057
ro.bootmode=normal
ro.baseband=0.95.00.1118r/0.95.00.1223r
ro.carrier=COMMON
ro.bootloader=2.11.0000
dev.bootreason=
ro.hardware=vigor
ro.revision=2
ro.devicerev=2
ro.engineerid=2
ro.lb=1
ro.cid=VZW__001
ro.mid=PH9810000
ro.emmc=1
ro.pagesize=2048
init.svc.choice_fn=stopped
init.svc.htcbatt=running
init.svc.adbd=running
init.svc.rmt_storage=running
ro.9kramdump=0
init.svc.recovery=running
ro.boot.block=/dev/block/mmcblk0p22
ro.recovery.block=/dev/block/mmcblk0p23
ro.misc.block=/dev/block/mmcblk0p24
ro.sdcard.block=/dev/block/mmcblk1p1
ro.sd-ext.block=/dev/block/mmcblk1p2
ro.internal_sdcard.block=/dev/block/mmcblk0p37
ro.ums.path=/sys/devices/platform/usb_mass_storage/lun0/file
ro.htcmodelid=PH9810000

Now I confess it's all Greek to me, and I'm not sure if it includes when I had to re-install a ROM after my attempt at recovery failed last night, but I can always fail a recovery again and post the log in the interest of figuring this one out. I know for sure I can do that much! ;)

Anyway, enjoy and hopefully this can help me and anyone else in my shoes in the long run.
 
one difference i see is that im using the newest amon-3.14.
another difference is that i do not attempt to backup or restore android_secure. just boot/system/data/cache

that log is from after flashing the new rom. heres what id do:

-download newest amon from here: [Recovery] Amon Ra style vigor - xda-developers
-install it on your phone if you currently have 3.13 installed(it shouldnt matter,i have the stock recovery on my phone :eek: but just in case,install 3.14 if you like to keep a recovery)
-open cmd,boot phone to fastboot,launch 3.14. make a new backup.
-do wipes,and try and restore an old backup,unchecking android_secure. if you get the error,immediately move the recovery log to the sd. toggle usb storage and move the log to your pc
-if it works,then reboot :)
-if it doesnt work,do wipes again and try and restore the backup you just made with 3.14. if it fails again,move the log to the sd and retrieve it again.


if it fails in both scenarios,i will PM drellis for some advice... he will want to be aware of issues and troubleshoot. :)
 
no prollem :) skimming thru the thread,i did see some references to issues with .android_secure,so hopefully using the newer version and not restoring that fixes it for you
 
I use Amon 3.14 and always backup and restore android_secure (because I read it somewhere). I've done this with different CleanROMs and RezRoms and Incredikernel. Just adding information for you guys to consider.
 
thanks for the info. it could be an issue with 3.13 backing up and/or restoring the .android_secure that is fixed in 3.14.

if he can restore without it checked, then he could try it with.

do either of you keep apps on your sd card? i do not,hence ive not ever bothered to back up .android_secure. that could have something to do with it also :)
 
I keep as much as possible on my SD card. It's a 32GB class 10 card. I wish I could keep all my user and system data on the SD card, but some data is kept elsewhere such that when I wipe and restore, I don't get a lot of the system settings and some app data.

Oh.. and I backed up and restored .android_secure when I was using AmonRa 3.13 too.
 
Well, it worked this time - with android secure and 3.14! Danged if I know how, but it did! VERY odd. :confused:

Don't worry - I'm sure it'll fail again, but it seems to at least work for me now. Maybe all it took was enough talking behind it's back....... :eek:

I'll just have to wait for it to fail again and see what happens. In the mean time - I'm back in the saddle and thanks for helping! :D
 
awsome! :cool:

how bout you? do you keep alot on your sd card?

did it work with android_secure checked or unchecked?
 
Yes - I also sprung for a class 10 32 GD card so I keep as much as I can on it. It's a holdover from my Droid X when I'd run out of memory if I didn't keep some stuff on my SD card so I could run multiple things.

And it worked with "android secure" checked. I just did a backup of my current setup with the intent of trying both. Turns out I didn't have to. And, I didn't wipe before my restore just because I didn't want to have to re-set up everything on my phone again since I seemed to be bombing out restore on a regular basis.

When I get more time this weekend I'll play some more to see if I can figure out exactly what I was doing wrong. In the meantime, I'm just glad to be back! :D
 
You must log in or register to reply here.
Back
Top Bottom