This is a 4.4.2 rooted android that i just flashed a custom spirit rom. It worked perfect but I go greedy and tried to format the whole phone with intentions of reinstalling spirit again on a fresh device but soon as I formated my phone i got the boot loop....Fail.
Cant access recovery even though the twrp logo pops up when i attempt to enter recovery only to boot loop again.
I tried flashing back to stock rom via odin but no can do cuz you cant downgrade. So I tried reinstalling twrp via odin. Said success but it still won't let me go into recovery mode cuz it still boot loops.
What should i do?
Should I try to use odin to flash to the custom spirit rom that i had on before this happened?
Or download a custom 4.4.2 stock rom and dtry to use that to flash via odin? makes no sense since i had the spirit rom last.
I'm looking at countless threads and am a little bit clouded wtih information. I have a feeling there is something easy to fix this that i dont know about. aNy input? thanks......
Should i try to install the stock recovery with odin? or another custom recovery thats not twrp? then install spirit rom again?
its an att i747 , not canadian one.
I'm not sure but maybe you need to flash a PIT file too?
audit13 said:
I'm not sure but maybe you need to flash a PIT file too?
Click to expand...
Click to collapse
Installed CWM-Recovery-LTE-SGS3-v5.tar_13-40-46.md5 via odin with success. Now I tried to re install the custom spirit rom again but get the error 7 installation aborted error. I know this rom will work since I had it installed last... what gives?
Also it i asks me to install update.zip when installing spirit rom. What update zip ? Should i rename the spirit rom zip to update.zip? or is it asking me to update to 4.4?
Sorry one more thing. I downloaded
I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME stock rom
update412
update4.3
zips ....Should i install stock rom first then the updates? then re root then re stock rom?
I read that if you install stock rom you could brick the phone becuase the bootloader wont let yuou downgrade... so before i potentially brick my phone should i just install the update 4.3 or can i just use the stock one and update?
bamf210 said:
Installed CWM-Recovery-LTE-SGS3-v5.tar_13-40-46.md5 via odin with success. Now I tried to re install the custom spirit rom again but get the error 7 installation aborted error. I know this rom will work since I had it installed last... what gives?
Also it i asks me to install update.zip when installing spirit rom. What update zip ? Should i rename the spirit rom zip to update.zip? or is it asking me to update to 4.4?
Click to expand...
Click to collapse
Status 7 errors can occur when the recovery is out of date.
audit13 said:
Status 7 errors can occur when the recovery is out of date.
Click to expand...
Click to collapse
when i initially formated the internal sd card i deleted 4 partitions via twrp
so when i used odin i notcied it had an option to re-partition
should i click it or will i mess up my phone
wont let me install twrp via odin, only cwm recovery is sticking. then any zip file i try to flash via cwm says the sd card is bad?
i found some guy with the same problem in these forums
Edit: In case others stumble upon this, the solution for me was to scrap the partitions on my SD card and start over. I used the proper sdformatter from the official sdcard site to create a FAT partition using up the entire disk, then used gparted to resize that partition leaving 512mb at the end to fit my ext3 in there. The official sdcard formatter leaves 4mb of unallocated space at the start of the disk, I left this there as I didn't want to mess with it. Once my new partitions were setup, I can again flash ROMS from the sdcard. So although there was a proper FAT32 partition on there previously that seemed to be working fine, for some reason it wasn't.
Last edited by tigris666; 24th January 2011 at 11:13 PM.
Click to expand...
Click to collapse
he appears to be talking about his external sd card but my internal sd card is the one i formated?
hi guys is this forum still active? I think im making this too complicated...
Problem: deleted key partitions via twrp now stuck in bootloop...
things i done.... installed cwm via odin since twrp wont stick. tried to install stock rom via recovery and the previous custom rom i was using "spirit rom" fails with error 7 and says my card is bad when i can read it via card reader still.
What version of cwm are you using?
You can tick repartition but I am not sure if that will help. I have never used that option.
heres cwm log
Starting recovery on Thu Jan 1 00:58:48 1970
framebuffer: fd 4 (720 x 1280)
CWM-based Recovery v5.5.0.4
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p7 (null) 0
2 /system ext4 /dev/block/mmcblk0p14 (null) 0
3 /data ext4 /dev/block/mmcblk0p15 (null) -16384
4 /cache ext4 /dev/block/mmcblk0p17 (null) 0
5 /recovery emmc /dev/block/mmcblk0p18 (null) 0
6 /emmc datamedia /dev/null (null) 0
7 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
ro.build.id=IMM76L
ro.build.display.id=cm_d2spr-userdebug 4.0.4 IMM76L eng.bbelos.20120709.161533 test-keys
ro.build.version.incremental=eng.bbelos.20120709.161533
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Mon Jul 9 16:15:52 EDT 2012
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=bbelos
ro.build.host=EroticBox
ro.build.tags=test-keys
ro.product.model=SPH-L710
ro.product.brand=samsung
ro.product.name=d2spr
ro.product.device=d2spr
ro.product.board=MSM8960
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8960
ro.build.product=d2spr
ro.build.description=samsung/d2spr/d2spr:4.0.4/IMM76D/L710VPALF9:user/release-keys
ro.build.fingerprint=d2spr-user 4.0.4 IMM76D L710VPALF9 release-keys
ro.build.characteristics=default
ro.cm.device=d2spr
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=
ril.subscription.types=NV,RUIM
dev.pm.dyn_samplingrate=1
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-fma2dp=false
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
lpa.decode=false
lpa.use-stagefright=false
ro.use_data_netmgrd=true
persist.data_netmgrd_nint=16
ro.emmc.sdcard.partition=17
persist.timed.enable=true
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
persist.audio.handset.mic=digital
persist.audio.speaker.location=high
ro.opengles.version=131072
ro.ril.transmitpower=true
ro.telephony.call_ring.multiple=0
ro.sf.lcd_density=320
persist.gps.qmienabled=true
ro.telephony.ril_class=SamsungCDMAQualcommRIL
gsm.sim.operator.alpha=sprint
gsm.sim.operator.numeric=310120
gsm.sim.operator.iso-country=us
gsm.operator.alpha=sprint
gsm.operator.numeric=310120
gsm.operator.iso-country=us
ro.cdma.home.operator.numeric=310120
ro.cdma.home.operator.alpha=Sprint
ro.telephony.default_network=4
keyguard.no_require_sim=true
DEVICE_PROVISIONED=1
telephony.lteOnCdmaDevice=1
persist.radio.apm_sim_not_pwdn=1
persist.radio.add_power_save=1
persist.radio.snapshot_disabled=1
debug.enabletr=true
com.qc.hardware=true
ro.sf.compbypass.enable=1
com.qc.hdmi_out=true
ro.hdmi.enable=true
debug.sf.hw=1
debug.composition.type=dyn
ro.cwm.enable_key_repeat=true
ro.com.android.dateformat=MM-dd-yyyy
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.rommanager.developerid=cyanogenmod
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.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dataroaming=false
ro.cm.version=9-20120709-UNOFFICIAL-d2spr
ro.modversion=9-20120709-UNOFFICIAL-d2spr
ro.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
dalvik.vm.lockprof.threshold=500
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.factorytest=0
ro.serialno=90d0a89e
ro.bootmode=unknown
ro.baseband=msm
ro.carrier=unknown
ro.bootloader=I747UCUFNJ1
ro.hardware=qcom
ro.revision=16
ro.emmc=1
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
-- Installing: /sdcard/SpiritRom-4.4.4-v1.7-20141112-d2lte.zip
Finding update package...
I:Update location: /sdcard/SpiritRom-4.4.4-v1.7-20141112-d2lte.zip
Opening update package...
Installing update...
Warning: No file_contexts
about to run program [/tmp/backuptool.sh] with 2 args
/tmp/backuptool.sh: line 50: check_prereq: not found
about to run program [/tmp/otasigcheck.sh] with 1 args
Creating filesystem with parameters:
Size: 1572864000
Block size: 4096
Blocks per group: 32768
Inodes per group: 8000
Inode size: 256
Journal blocks: 6000
Label:
Blocks: 384000
Block groups: 12
Reserved block group size: 95
Created filesystem with 11/96000 inodes and 12609/384000 blocks
is the filesystem being null a reason to be concerned?
audit13 said:
What version of cwm are you using?
You can tick repartition but I am not sure if that will help. I have never used that option.
Click to expand...
Click to collapse
oh hi thanks for replying. its CWM-Recovery-LTE-SGS3-v5.tar_13-40-46.md5
Yes i know im suppose to use an updated version, but i downloaded CWMTouch-recovery_ATT-6.0.3.1 to try to install via recovery but the zip got error status 7.
I'm thinking i messed up the filesystem table.
Lets start fresh. Do you what bootloader version is on your phone? When you boot into download mode, do you see anything on the screen about warranty bit?
audit13 said:
Lets start fresh. Do you what bootloader version is on your phone? When you boot into download mode, do you see anything on the screen about warranty bit?
Click to expand...
Click to collapse
Thanks for the response
product name sgh-i747
current binary: custom
system status: custom
qualcomm secureboot: enable
warranty bit: 1
bootloader ap swrev: 3
Am i screwed?
This tells me that you have at least a 4.3 bootloader on your phone. Do not try to flash a stock rom to your phone until you verify the exact bootloader.
It is best to take things one step at a time. Was your phone ever running a stock kit Kat rom?
audit13 said:
This tells me that you have at least a 4.3 bootloader on your phone. Do not try to flash a stock rom to your phone until you verify the exact bootloader.
It is best to take things one step at a time. Was your phone ever running a stock kit Kat rom?
Click to expand...
Click to collapse
It was 4.4 from what i remember i tried updating and it had no update available. That propably does not mean anything but for sure it was 4.4 and rooted stock rom. I did install a custom rom named "SpiritRom-4.4.4-v1.7-20141112-d2lte" and it ran perfect. It was also the last rom installed.
I messed up and either deleted or formated all my filesytem folders in the phone via twrp hence the boot loop....
Thanks for saying not to install the stock rom. I just downloaded it and the updates as well.
Do not try to flash a stock rom to your phone until you verify the exact bootloader.
Click to expand...
Click to collapse
Not sure how to check, Is the clock mod recovery log reliable? It shows ro.bootloader=I747UCUFNJ1 google search shows it as 4.4.2
Am I going to have to flash a 4.4.2 stock rom? Or can I just install the custom "spirit rom"? via odin? since I get the error 7 when trying from recovery...
The phone is running the latest bootloader so you cannot downgrade it it; otherwise, you run the risk of bricking the phone.
Download the latest tar version of TWRP from here: https://dl.twrp.me/d2att/
Open Odin, uncheck everything in Odin except f.reset time.
Connect the phone and flash TWRP.
When you see the word reset in the window, remove the USB cable, remove the battery, replace the battery, boot into recovery to make sure the phone can enter into and stay in TWRP.
If you get an error when flashing, let us know the error.
Related
So I rebooted into recovery..
Wipe, Cache, Dalvik, Data
Nandroid restore, chose my "sprint lovers" folder and selected the file within that
Then I get this "Oops.. something went wrong! Please check the recovery log!"
This is the log:
Starting recovery on Mon Apr 4 23:39:01 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
Build : RA-supersonic-v2.3 - HAUS MOD rev.A
I:Set boot command "boot-recovery"
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
ro.config.ringtone=Windchimer.mp3
ro.config.notification_sound=Little.mp3
ro.build.id=ERE27
ro.build.display.id=1.32.651.1
ro.build.version.incremental=171253
ro.build.version.sdk=7
ro.build.version.codename=REL
ro.build.version.release=2.1-update1
ro.build.date=Wed Apr 28 21:39:52 CST 2010
ro.build.date.utc=1272461992
ro.build.type=userdebug
ro.build.user=lala-01
ro.build.host=lala-01-desktop
ro.build.tags=test-keys
ro.product.model=PC36100
ro.product.brand=sprint
ro.product.name=htc_supersonic
ro.product.device=supersonic
ro.product.board=supersonic
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=qsd8k
ro.build.product=supersonic
ro.build.description=1.32.651.1 CL171253 test-keys
ro.build.changelist=171253
ro.product.ua=
ro.build.fingerprint=sprint/htc_supersonic/supersonic/supersonic:2.1-update1/ERE27/171253:userdebug/test-keys
ro.product.version=1.32.651.1
keyguard.no_require_sim=1
rild.libpath=/system/lib/libhtc_ril.so
ro.ril.def.preferred.network=4
ro.telephony.default_network=4
wifi.interface=eth0
wifi.supplicant_scan_interval=15
ro.com.android.dataroaming=true
ro.com.google.locationfeatures=1
ro.sf.lcd_density=240
ro.com.google.clientidbase=android-sprint-us
persist.service.mount.playsnd=0
ro.ril.def.agps.mode=2
settings.display.autobacklight=1
settings.display.brightness=143
dalvik.vm.heapsize=24m
ro.media.enc.file.format=3gp,mp4
ro.media.enc.vid.codec=m4v,h263
ro.media.enc.vid.h263.width=176,1280
ro.media.enc.vid.h263.height=144,720
ro.media.enc.vid.h263.bps=64000,6000000
ro.media.enc.vid.h263.fps=1,30
ro.media.enc.vid.m4v.width=176,1280
ro.media.enc.vid.m4v.height=144,720
ro.media.enc.vid.m4v.bps=64000,6000000
ro.media.enc.vid.m4v.fps=1,30
ro.media.dec.jpeg.memcap=20000000
ro.bt.chipset=Broadcom BCM4329-B1
ro.bt.version=Bluetooth 2.1 + EDR
ro.bt.stack=Broadcom BTL-A
ro.bt.stack.version=2.0.47.005
ro.bt.profiles=4270339
ro.cdma.home.operator.numeric=310120
ro.cdma.home.operator.alpha=Sprint
gsm.sim.operator.numeric=0
gsm.sim.operator.alpha=0
gsm.sim.operator.iso-country=0
ro.config.alarm_alert=Light.mp3
ro.config.cal_notification=Vector.mp3
ro.config.msg_notification=Ascend.mp3
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=2.1_r3
media.a1026.nsForVoiceRec=0
htc.audio.alt.enable=1
htc.audio.hac.enable=1
net.bt.name=Android
net.change=net.bt.name
ro.config.sync=yes
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.modversion=RA-supersonic-v2.3 - HAUS MOD rev.A
ro.factorytest=0
ro.serialno=HT12KHL01046
ro.bootmode=recovery
ro.baseband=2.15.00.11.19
ro.carrier=COMMON
ro.bootloader=2.10.0001
ro.hardware=supersonic
ro.revision=3
ro.cid=SPCS_001
init.svc.recovery=running
init.svc.adbd=running
init.svc.extfix=running
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""
Restore BDARS-20110404-0015 ?
Press Power to confirm,
any other key to abort.
Restoring : .
nandroid-mobile v2.2.1
Searching for backup directories, matching BDARS-20110404-0015, to delete or restore
or compress
Looking for the latest backup, will display other choices!
Error: no backups found
Oops... something went wrong!
Please check the recovery log!
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""
Move recovery.log to SD
Press Power to confirm,
any other key to abort.
Moving : .unmounting /sdcard
Click to expand...
Click to collapse
Now, if I power off the phone, then power on, I see the White HTC splash screen then it immediately goes to the bootloader..
it looks like you never made a backup with amon-ra. did you backup with clockworkmod? bcuz they aren't compatible. i think you at least need to move folders around. baisically, if you made a backup in cwm, restore in cwm. same goes for amon-ra.
Its saying it cant find the backup. But, why would it then bork everything else from loading?
dkdude36 said:
it looks like you never made a backup with amon-ra. did you backup with clockworkmod? bcuz they aren't compatible. i think you at least need to move folders around. baisically, if you made a backup in cwm, restore in cwm. same goes for amon-ra.
Click to expand...
Click to collapse
I have only made backups via Amon RA.
I made a backup of my Sense ROM then renamed the "top" folder, so I could tell which was Sense and which was AOSP. But, I figure that wouldnt effect anything.
I didnt touch anything within that main folder.
no idea. but did you make the sprintlover's backup with cwm? if you did, just flash to cwm and restore
Could I just flash a new ROM? I have one on my SD card still.
dkdude36 said:
no idea. but did you make the sprintlover's backup with cwm? if you did, just flash to cwm and restore
Click to expand...
Click to collapse
All backups were made with Amon. Amon is the only recovery that has been on my phone.
Mindspin_311 said:
Its saying it cant find the backup. But, why would it then bork everything else from loading?
Click to expand...
Click to collapse
Turn off your device, remove the SD card for a few seconds and then reinsert it. Afterwards, reboot into recovery and try to nandroid restore again. If that does not work, reflash amon RA.
Posting & replying via the XDA Premium app
Mindspin_311 said:
Could I just flash a new ROM? I have one on my SD card still.
Click to expand...
Click to collapse
Yes, you could, but let's make sure your recovery is okay and see if we can get that nandroid restore going. Still, it is your device so if you want to flash a new rom, go for it.
Posting & replying via the XDA Premium app
dougjamal said:
Turn off your device, remove the SD card for a few seconds and then reinsert it. Afterwards, reboot into recovery and try to nandroid restore again. If that does not work, reflash amon RA.
Posting & replying via the XDA Premium app
Click to expand...
Click to collapse
is this a bug with amon-ra? just curious...
dougjamal said:
Turn off your device, remove the SD card for a few seconds and then reinsert it. Afterwards, reboot into recovery and try to nandroid restore again. If that does not work, reflash amon RA.
Posting & replying via the XDA Premium app
Click to expand...
Click to collapse
No luck. Failed again. Here is the log..
Re Starting recovery on Mon Apr 4 23:58:02 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
Build : RA-supersonic-v2.3 - HAUS MOD rev.A
I:Set boot command "boot-recovery"
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
ro.config.ringtone=Windchimer.mp3
ro.config.notification_sound=Little.mp3
ro.build.id=ERE27
ro.build.display.id=1.32.651.1
ro.build.version.incremental=171253
ro.build.version.sdk=7
ro.build.version.codename=REL
ro.build.version.release=2.1-update1
ro.build.date=Wed Apr 28 21:39:52 CST 2010
ro.build.date.utc=1272461992
ro.build.type=userdebug
ro.build.user=lala-01
ro.build.host=lala-01-desktop
ro.build.tags=test-keys
ro.product.model=PC36100
ro.product.brand=sprint
ro.product.name=htc_supersonic
ro.product.device=supersonic
ro.product.board=supersonic
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=qsd8k
ro.build.product=supersonic
ro.build.description=1.32.651.1 CL171253 test-keys
ro.build.changelist=171253
ro.product.ua=
ro.build.fingerprint=sprint/htc_supersonic/supersonic/supersonic:2.1-update1/ERE27/171253:userdebug/test-keys
ro.product.version=1.32.651.1
keyguard.no_require_sim=1
rild.libpath=/system/lib/libhtc_ril.so
ro.ril.def.preferred.network=4
ro.telephony.default_network=4
wifi.interface=eth0
wifi.supplicant_scan_interval=15
ro.com.android.dataroaming=true
ro.com.google.locationfeatures=1
ro.sf.lcd_density=240
ro.com.google.clientidbase=android-sprint-us
persist.service.mount.playsnd=0
ro.ril.def.agps.mode=2
settings.display.autobacklight=1
settings.display.brightness=143
dalvik.vm.heapsize=24m
ro.media.enc.file.format=3gp,mp4
ro.media.enc.vid.codec=m4v,h263
ro.media.enc.vid.h263.width=176,1280
ro.media.enc.vid.h263.height=144,720
ro.media.enc.vid.h263.bps=64000,6000000
ro.media.enc.vid.h263.fps=1,30
ro.media.enc.vid.m4v.width=176,1280
ro.media.enc.vid.m4v.height=144,720
ro.media.enc.vid.m4v.bps=64000,6000000
ro.media.enc.vid.m4v.fps=1,30
ro.media.dec.jpeg.memcap=20000000
ro.bt.chipset=Broadcom BCM4329-B1
ro.bt.version=Bluetooth 2.1 + EDR
ro.bt.stack=Broadcom BTL-A
ro.bt.stack.version=2.0.47.005
ro.bt.profiles=4270339
ro.cdma.home.operator.numeric=310120
ro.cdma.home.operator.alpha=Sprint
gsm.sim.operator.numeric=0
gsm.sim.operator.alpha=0
gsm.sim.operator.iso-country=0
ro.config.alarm_alert=Light.mp3
ro.config.cal_notification=Vector.mp3
ro.config.msg_notification=Ascend.mp3
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=2.1_r3
media.a1026.nsForVoiceRec=0
htc.audio.alt.enable=1
htc.audio.hac.enable=1
net.bt.name=Android
net.change=net.bt.name
ro.config.sync=yes
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.modversion=RA-supersonic-v2.3 - HAUS MOD rev.A
ro.factorytest=0
ro.serialno=HT12KHL01046
ro.bootmode=recovery
ro.baseband=2.15.00.11.19
ro.carrier=COMMON
ro.bootloader=2.10.0001
ro.hardware=supersonic
ro.revision=3
ro.cid=SPCS_001
init.svc.recovery=running
init.svc.adbd=running
init.svc.extfix=running
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""
Restore BDARS-20110403-0429 ?
Press Power to confirm,
any other key to abort.
Restoring : .
nandroid-mobile v2.2.1
Searching for backup directories, matching BDARS-20110403-0429, to delete or restore
or compress
Looking for the latest backup, will display other choices!
Error: no backups found
Oops... something went wrong!
Please check the recovery log!
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""
Move recovery.log to SD
Press Power to confirm,
any other key to abort.
Moving : .unmounting /sdcard
Click to expand...
Click to collapse
dkdude36 said:
is this a bug with amon-ra? just curious...
Click to expand...
Click to collapse
It is possible. It happened to me once and all I did was remove my SD card, reinserted it and booted into recovery and all was well. I wasn't using v2.3 when it happened. At least, I don't recall using it.
Posting & replying via the XDA Premium app
Mindspin_311 said:
No luck. Failed again. Here is the log..
Click to expand...
Click to collapse
ok then try reinstalling amon-ra.
Mindspin_311 said:
No luck. Failed again. Here is the log..
Click to expand...
Click to collapse
Do me a favor if you have the time, boot up to your homescreen and using a file manager, go into your nandroid folder and rename the nandroid you're trying to restore. Make sure there is no spaces or special characters. For instance, rename adbc-20110404-1234 to something like MynsRLS5. Afterwards, go back into recovery and try to restore the nandroid backup you just renamed. If that fails, assume your backup is corrupted and simply flash a new rom like you wanted to do in one of your previous replies. Also, I would reflash amon RA to be on the safe side as stated by dkdude36.
Posting & replying via the XDA Premium app
dougjamal said:
Do me a favor if you have the time, boot up to your homescreen and using a file manager, go into your nandroid folder and rename the nandroid you're trying to restore. Make sure there is no spaces or special characters. For instance, rename adbc-20110404-1234 to something like MynsRLS5. Afterwards, go back into recovery and try to restore the nandroid backup you just renamed. If that fails, assume your backup is corrupted and simply flash a new rom like you wanted to do in one of your previous replies. Also, I would reflash amon RA to be on the safe side as stated by dkdude36.
Posting & replying via the XDA Premium app
Click to expand...
Click to collapse
i dont think he can boot. maybe flash a rom, boot, see if nandroid is there, and then figure out what to do.
I can access all the files on my desktop via the USB-MS feature. I will rename a folder.
Mindspin_311 said:
I can access all the files on my desktop via the USB-MS feature. I will rename a folder.
Click to expand...
Click to collapse
So this is the naming scheme I have...
Folder: Restore
Subfolder: BDARS-20110403-0429
Within the subfolder is a "Android Secure" ZIP, plus boot, data, recovery, wimax, system, nandroid md.5
They are IMG and MD5 files
Retrying restore did not work.
Was wiping cache, dalvik, data then running Calk's format all prior to running the Nand restore a bad idea?
Mindspin_311 said:
Was wiping cache, dalvik, data then running Calk's format all prior to running the Nand restore a bad idea?
Click to expand...
Click to collapse
doesnt sound like one...
Since I just created this account XDA won't let me post this in the appropriate place (which would be http://forum.xda-developers.com/showthread.php?t=1175842).... regardless.
I am trying to flash Nil's Business Gingersense 3.0. I have successfully rooted and flashed multiple ROMs in the past. When trying to flash this ROM CWM comes up saying Error processing ROM Manager Script.
Here is the CWM log.
Starting recovery on Thu Sep 8 19:53:39 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
ClockworkMod Recovery v5.0.2.0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /misc mtd misc (null)
2 /recovery mtd recovery (null)
3 /boot mtd boot (null)
4 /system yaffs2 system (null)
5 /datadata yaffs2 datadata (null)
6 /data ext3 /dev/block/mmcblk0p1 (null)
7 /cache ext3 /dev/block/mmcblk0p2 (null)
8 /emmc vfat /dev/block/mmcblk0p3 (null)
9 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
10 /sd-ext ext3 /dev/block/mmcblk1p2 (null)
I:Completed outputting fstab.
Irocessing arguments.
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=FRF91
ro.build.display.id=GRJ90
ro.build.version.incremental=eng.koush.20110905.104341
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=Mon Sep 5 10:44:06 PDT 2011
ro.build.date.utc=0
ro.build.type=user
ro.build.user=koush
ro.build.host=Koushik-Lion.local
ro.build.tags=release-keys
ro.product.model=ADR6300
ro.product.brand=verizon_wwe
ro.product.name=inc
ro.product.device=inc
ro.product.board=inc
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=qsd8k
ro.build.product=inc
ro.build.description=3.26.605.1 CL264707 release-keys
ro.build.fingerprint=verizon_wwe/inc/inc/inc:2.2/FRF91/264707:user/release-keys
rild.libpath=/system/lib/libhtc_ril.so
ro.ril.def.preferred.network=4
ro.telephony.default_network=4
wifi.interface=eth0
wifi.supplicant_scan_interval=45
mobiledata.interfaces=rmnet0
ro.com.android.dataroaming=true
ro.com.google.locationfeatures=1
ro.sf.lcd_density=240
persist.service.mount.playsnd=0
ro.ril.def.agps.mode=2
settings.display.autobacklight=1
settings.display.brightness=143
ro.phone_storage=1
dalvik.vm.heapsize=32m
ro.cdma.data_retry_config=max_retries=infinite,0,0,60000,120000,480000,900000
ro.cdma.home.operator.numeric=310012
ro.cdma.home.operator.alpha=Verizon
ro.config.htc.nocheckin=1
ro.HorizontalVVM=true
ro.HorizontalBUA=true
ro.ril.enable.prl.recognition=1
ro.additionalmounts=/mnt/emmc
ro.opengles.version=131072
ro.com.android.wifi-watchlist=GoogleGuest
ro.error.receiver.system.apps=com.google.android.feedback
ro.setupwizard.enterprise_mode=1
ro.com.google.clientidbase=android-verizon
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.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
ro.config.vc_call_vol_steps=7
ro.cdma.otaspnumschema=SELC,1,80,99
ro.telephony.call_ring.multiple=false
ro.telephony.call_ring.delay=3000
ro.url.safetylegal=http://www.htc.com/staticfiles/Support/legal/?model=A855
ro.setupwizard.enable_bypass=1
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
ro.media.dec.jpeg.memcap=20000000
ro.media.enc.jpeg.quality=95,85,70
keyguard.no_require_sim=true
ro.rommanager.developerid=cyanogenmod
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Playa.ogg
ro.config.notification_sound=regulus.ogg
ro.config.alarm_alert=Alarm_Beep_03.ogg
ro.product.version=3.26.605.1
ro.modversion=CyanogenMod-7.1.0-RC1-Inc-KANG
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=HT09HHJ18316
ro.bootmode=recovery
ro.baseband=2.15.00.07.28
ro.carrier=COMMON
ro.bootloader=0.92.0000
ro.hardware=inc
ro.revision=0
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
0e32a451006c45b253cb68e516ffb9c2
e32a451006c45b253cb68e516ffb9c2
Error processing ROM Manager script. Please verify you have ROM Manager v4.4.0.0 or higher installed.
Oh, and I have verified I am on v4.4.0.0 or higher (currently 5.0.2.0) I have also verified I am using the correct recovery of 3.0.0.8 (since I am SLCD).
Try reinstall the recovery and redownload the rom
Sent From My Optimized HTC Incredibly Dinc
Kratz17 said:
Try reinstall the recovery and redownload the rom
Sent From My Optimized HTC Incredibly Dinc
Click to expand...
Click to collapse
If the above didn't work you might also want to downgrade from the 5.0.2.0 version. There have been reports here and there of problems with the new version.
Any solutions to this yet?
I've got basically the same problem where I cannot restore my backup. I get the same errors as here.
SOLUTION???
GreatMoloko said:
Since I just created this account XDA won't let me post this in the appropriate place (which would be http://forum.xda-developers.com/showthread.php?t=1175842).... regardless.
I am trying to flash Nil's Business Gingersense 3.0. I have successfully rooted and flashed multiple ROMs in the past. When trying to flash this ROM CWM comes up saying Error processing ROM Manager Script.
Here is the CWM log.
Starting recovery on Thu Sep 8 19:53:39 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
ClockworkMod Recovery v5.0.2.0
Error processing ROM Manager script. Please verify you have ROM Manager v4.4.0.0 or higher installed.
Oh, and I have verified I am on v4.4.0.0 or higher (currently 5.0.2.0) I have also verified I am using the correct recovery of 3.0.0.8 (since I am SLCD).
Click to expand...
Click to collapse
Your ClockworkMod Recovery is version 5.0.2.0. ROM Manager version you need to get from when you open ROM Manager itself, as it'll say at the top. These are two different things. I'm using verison 4.5.0.1. Update ROM Manager in the Market (or uninstall it from your current ROM, then re-install from the Market).
Try performing the following in ROM Manager: Open it, hit Menu - Settings - turn on Advanced Mode - turn on Erase Recovery - hit back arrow - select Flash ClockworkMod Recovery.
Then try flashing the ROM in question.
EDIT: I have had issues with ClockworkMod Recovery verision 5.0.2.0 initially, but after turning on the Erase Recovery feature and re-flashing it, things were fine. Every once in a while it won't backup, so I just reboot and re-flash recovery, do the backup, and it works fine.
[email protected] said:
I've got basically the same problem where I cannot restore my backup. I get the same errors as here.
SOLUTION???
Click to expand...
Click to collapse
I have the same problem... I happen after I flash abyss kernel 4.2 to my galaxy note and now I cannot restore my backup, when I boot to CWM it freeze.
Please if someone can help.
Still a problem- No Erase Recovery found in ROM Manager Premium
RMarkwald said:
Your ClockworkMod Recovery is version 5.0.2.0. ROM Manager version you need to get from when you open ROM Manager itself, as it'll say at the top. These are two different things. I'm using verison 4.5.0.1. Update ROM Manager in the Market (or uninstall it from your current ROM, then re-install from the Market).
Try performing the following in ROM Manager: Open it, hit Menu - Settings - turn on Advanced Mode - turn on Erase Recovery - hit back arrow - select Flash ClockworkMod Recovery.
Then try flashing the ROM in question.
EDIT: I have had issues with ClockworkMod Recovery verision 5.0.2.0 initially, but after turning on the Erase Recovery feature and re-flashing it, things were fine. Every once in a while it won't backup, so I just reboot and re-flash recovery, do the backup, and it works fine.
Click to expand...
Click to collapse
Using ROM Manager ptremium 5.0.2.4. Turned on Advance Features a waring window came OK'd it but no new feature cropped up!!! Don't know where this Erase Recovery" feature is to be found
unknowners said:
Using ROM Manager ptremium 5.0.2.4. Turned on Advance Features a waring window came OK'd it but no new feature cropped up!!! Don't know where this Erase Recovery" feature is to be found
Click to expand...
Click to collapse
Menu - settings, 7th option down. Advanced mode has nothing to do with the erase recovery feature.
Log report
cmlusco said:
Menu - settings, 7th option down. Advanced mode has nothing to do with the erase recovery feature.
Click to expand...
Click to collapse
Log report says this:
Starting recovery on Sat Nov 24 08:00:52 2012
framebuffer: fd 4 (480 x 800)
CWM-based Recovery v5.0.2.7
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /recovery emmc /dev/block/mmcblk0p5 (null)
2 /boot emmc /dev/block/mmcblk0p5 (null)
3 /cache ext3 /dev/block/mmcblk0p2 (null)
4 /data ext3 /dev/block/mmcblk0p7 (null)
5 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
6 /emmc vfat /dev/block/mmcblk0p8 (null)
7 /system ext3 /dev/block/mmcblk0p1 (null)
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Got arguments from /cache/recovery/command
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery" "--update_package=CACHE:update.zip"
(replacing path "CACHE:update.zip" with "/cache/update.zip")
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GRI40
ro.build.display.id=GWK74
ro.build.version.incremental=eng.fitsnugly.20111120.085104
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Sun Nov 20 08:51:42 EST 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=fitsnugly
ro.build.host=ubuntu
ro.build.tags=test-keys
ro.product.model=LG-P999
ro.product.brand=lge
ro.product.name=lge_lge_star
ro.product.device=p999
ro.product.board=p999
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=lge
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=p999
ro.build.description=lge_star-user 2.3.3 GRI40 41fdc8a2 release-keys
ro.build.fingerprint=lge/lge_lge_star/p999:2.3.3/GRI40/lgp999-V21e.41fdc8a2:user/release-keys
rild.libpath=/system/lib/librilswitch.so
rild.libargs=-d /dev/ttyspi0
rilswitch.vendorlibpath=/system/lib/lge-ril.so
rilswitch.ganlibpath=/system/lib/libganril.so
ro.sf.lcd_density=240
mobiledata.interfaces=gannet0,vsnet0,vsnet1,vsnet2,vsnet3
dalvik.vm.heapsize=32m
dalvik.vm.dexopt-flags=m=y,u=n
ro.additionalmounts=/mnt/emmc
ro.vold.switchablepair=/mnt/sdcard,/mnt/emmc
ro.opengles.version=131072
ro.telephony.call_ring.multiple=false
ro.telephony.call_ring.delay=3000
ro.telephony.call_ring.absent=true
ro.telephony.ril_class=lgestar
ro.hardware.respect_als=true
ro.bt.bdaddr_path=/sys/devices/platform/star_bd_address/bdaddr_if
dalvik.vm.dexopt-data-only=1
keyguard.no_require_sim=true
ro.rommanager.developerid=cyanogenmod
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.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.config.ringtone=Playa.ogg
ro.config.notification_sound=regulus.ogg
ro.config.alarm_alert=Alarm_Beep_03.ogg
ro.modversion=CyanogenMod-7.2.0-RC0-G2x-KANG
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=tegra
ro.revision=0
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=running
Finding update package...
I:Update location: /cache/update.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1738 bytes; signature 1720 bytes from end
I:whole-file signature verified
I:verify_file returned 0
Installing update...
Replacing stock recovery with ClockworkMod recovery...
about to run program [/sbin/busybox] with 4 args
rm: /etc: is a directory
about to run program [/sbin/busybox] with 4 args
sh: invalid number 'root'
sh: can't kill pid 3344: No such process
sh: invalid number 'S'
sh: invalid number '/sbin/adbd'
sh: invalid number 'recovery'
sh: can't kill pid 994: No such process
sh: invalid number 'root'
sh: can't kill pid 1764: No such process
sh: invalid number 'S'
sh: invalid number 'grep'
sh: invalid number '/sbin/adbd'
sh: invalid number 'root'
sh: can't kill pid 9420: No such process
sh: invalid number 'S'
sh: invalid number '/sbin/recovery'
sh: can't kill pid 998: No such process
sh: invalid number 'root'
sh: can't kill pid 1764: No such process
sh: invalid number 'S'
sh: invalid number 'grep'
sh: invalid number '/sbin/recovery'
run_program: child exited with status 1
script result was [256]
Starting recovery on Sat Nov 24 08:00:57 2012
framebuffer: fd 4 (480 x 800)
ClockworkMod Recovery v5.0.2.0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /recovery emmc /dev/block/mmcblk0p5 (null)
2 /boot emmc /dev/block/mmcblk0p5 (null)
3 /cache ext3 /dev/block/mmcblk0p2 (null)
4 /data ext3 /dev/block/mmcblk0p7 (null)
5 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
6 /emmc vfat /dev/block/mmcblk0p8 (null)
7 /system ext3 /dev/block/mmcblk0p1 (null)
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GRI40
ro.build.display.id=GWK74
ro.build.version.incremental=eng.fitsnugly.20111120.085104
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Sun Nov 20 08:51:42 EST 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=fitsnugly
ro.build.host=ubuntu
ro.build.tags=test-keys
ro.product.model=LG-P999
ro.product.brand=lge
ro.product.name=lge_lge_star
ro.product.device=p999
ro.product.board=p999
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=lge
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=p999
ro.build.description=lge_star-user 2.3.3 GRI40 41fdc8a2 release-keys
ro.build.fingerprint=lge/lge_lge_star/p999:2.3.3/GRI40/lgp999-V21e.41fdc8a2:user/release-keys
rild.libpath=/system/lib/librilswitch.so
rild.libargs=-d /dev/ttyspi0
rilswitch.vendorlibpath=/system/lib/lge-ril.so
rilswitch.ganlibpath=/system/lib/libganril.so
ro.sf.lcd_density=240
mobiledata.interfaces=gannet0,vsnet0,vsnet1,vsnet2,vsnet3
dalvik.vm.heapsize=32m
dalvik.vm.dexopt-flags=m=y,u=n
ro.additionalmounts=/mnt/emmc
ro.vold.switchablepair=/mnt/sdcard,/mnt/emmc
ro.opengles.version=131072
ro.telephony.call_ring.multiple=false
ro.telephony.call_ring.delay=3000
ro.telephony.call_ring.absent=true
ro.telephony.ril_class=lgestar
ro.hardware.respect_als=true
ro.bt.bdaddr_path=/sys/devices/platform/star_bd_address/bdaddr_if
dalvik.vm.dexopt-data-only=1
keyguard.no_require_sim=true
ro.rommanager.developerid=cyanogenmod
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.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.config.ringtone=Playa.ogg
ro.config.notification_sound=regulus.ogg
ro.config.alarm_alert=Alarm_Beep_03.ogg
ro.modversion=CyanogenMod-7.2.0-RC0-G2x-KANG
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=tegra
ro.revision=0
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
449dfc3bd9a686a32d1b8be35bcdd0d7
e04b109f5e4c6e595fcece40d2b9a984
Error processing ROM Manager script. Please verify you have ROM Manager v4.4.0.0 or higher installed.
Are you s-off, or bootloader unlocked? If so try reflashing cwm thru hboot or fastboot. Also, are you trying to install this rom thru rom manager? Why not just go straight to recovery your self and flash it from there. Rom manager is known to have issues flashing things.
I have a rooted GNexus running AOKP M3 and Franco Kernel #16. Today before updating the kernel I attempted to do a nandroid backup via ROM Manager (newest version: 5.0.0.6). I've done this successfully on a couple occasions but not after I updated ROM Manager. Anyways heres the log:
Starting recovery on Tue Feb 7 02:28:41 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (720 x 1280)
ClockworkMod Recovery v5.5.0.2
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /system ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system (null) 0
2 /cache ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/cache (null) 0
3 /data auto /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata (null) 0
4 /misc emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/misc (null) 0
5 /boot emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/boot (null) 0
6 /recovery emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/recovery (null) 0
7 /sbl emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/sbl (null) 0
8 /xloader emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/xloader (null) 0
9 /radio emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/radio (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sdcard during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:fail
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
ro.build.id=ICS_MR0
ro.build.display.id=full_maguro-userdebug 4.0.1 ICS_MR0 eng.koush.20111123.115422 test-keys
ro.build.version.incremental=eng.koush.20111123.11 5422
ro.build.version.sdk=14
ro.build.version.codename=REL
ro.build.version.release=4.0.1
ro.build.date=Wed Nov 23 11:54:46 PST 2011
ro.build.date.utc=1322078086
ro.build.type=userdebug
ro.build.user=koush
ro.build.host=Koushik-Lion.local
ro.build.tags=test-keys
ro.product.model=Full AOSP on Maguro
ro.product.brand=Android
ro.product.name=full_maguro
ro.product.device=maguro
ro.product.board=tuna
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap4
ro.build.product=maguro
ro.build.description=full_maguro-userdebug 4.0.1 ICS_MR0 eng.koush.20111123.115422 test-keys
ro.build.fingerprint=Android/full_maguro/maguro:4.0.1/ICS_MR0/eng.koush.20111123.115422:userdebug/test-keys
ro.build.characteristics=nosdcard
rild.libpath=/vendor/lib/libsec-ril.so
rild.libargs=-d /dev/ttys0
telephony.lteOnCdmaDevice=0
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.opengles.version=131072
ro.sf.lcd_density=320
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
dalvik.vm.lockprof.threshold=500
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.factorytest=0
ro.serialno=01498FC30D018007
ro.bootmode=unknown
ro.baseband=I9250XXKK6
ro.carrier=unknown
ro.bootloader=PRIMEKK15
ro.hardware=tuna
ro.revision=9
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
I:using /data/media, no /sdcard found.
SD Card mounted...
Verifying SD Card marker...
SD Card marker not found...
de969e6d3606553b5a17eed6b595c2dd
Error processing ROM Manager script. Please verify that you are performing the backup, restore, or ROM installation from ROM Manager v4.4.0.0 or higher.
I:using /data/media, no /sdcard found.
help?
Hmm.. funny. I just successfully did a backup by manually going into recovery and doing it from the menu. I still got a message saying sd card missing or something but it said backup complete and I can see the backup file in ROM Manager.
Hi there, I installed CM9 successfully however when it rebooted, there was no radio. I downloaded the file 403radios_btldr.zip and tried to apply it via CWM recovery and keep getting the following error.. i have also downloaded it twice from different sources. Is that the correct radio? Any ideas?
Code:
Starting recovery on Sat Mar 24 15:43:56 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (720 x 1280)
ClockworkMod Recovery v5.5.0.4
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /system ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system (null) 0
2 /cache ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/cache (null) 0
3 /data auto /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata (null) 0
4 /misc emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/misc (null) 0
5 /boot emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/boot (null) 0
6 /recovery emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/recovery (null) 0
7 /sbl emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/sbl (null) 0
8 /xloader emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/xloader (null) 0
9 /radio emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/radio (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sdcard during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=adb
ro.build.id=ICS_MR0
ro.build.display.id=full_toro-eng 4.0.1 ICS_MR0 eng.koush.20111215.170401 test-keys
ro.build.version.incremental=eng.koush.20111215.170401
ro.build.version.sdk=14
ro.build.version.codename=REL
ro.build.version.release=4.0.1
ro.build.date=Thu Dec 15 17:04:31 PST 2011
ro.build.date.utc=1323997471
ro.build.type=eng
ro.build.user=koush
ro.build.host=Koushik-Lion.local
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_toro
ro.product.device=toro
ro.product.board=toro
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=toro
ro.build.description=full_toro-eng 4.0.1 ICS_MR0 eng.koush.20111215.170401 test-keys
ro.build.fingerprint=Android/full_toro/toro:4.0.1/ICS_MR0/eng.koush.20111215.170401:eng/test-keys
ro.build.characteristics=default
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=0146975B0401F00E
ro.bootmode=unknown
ro.baseband=��������������������
ro.carrier=unknown
ro.bootloader=PRIMEKL01
ro.hardware=tuna
ro.revision=9
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
I:using /data/media, no /sdcard found.
SD Card mounted...
Verifying SD Card marker...
5a8985a48c9f5d61b0f5440da38a35c4
I:Running script:
I:
ui_print("ROM Manager Version 5.0.0.6");
ui_print("March 24, 2012");
ui_print("Preparing to install ROM...");
run_program("/cache/dowipedalvikcache.sh");
assert(install_zip("/sdcard/Download/403radios_btldr.zip"));
parse returned 0; 0 errors encountered
ROM Manager Version 5.0.0.6
March 24, 2012
Preparing to install ROM...
about to run program [/cache/dowipedalvikcache.sh] with 1 args
mount: mounting /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata on /data failed: Device or resource busy
mount: mounting /dev/block/platform/omap/omap_hsmmc.0/by-name/cache on /cache failed: Device or resource busy
mount: can't find /sd-ext in /etc/fstab
umount: can't umount /sd-ext: Invalid argument
run_program: child exited with status 1
-- Installing: /sdcard/Download/403radios_btldr.zip
Finding update package...
I:Update location: /sdcard/Download/403radios_btldr.zip
I:using /data/media, no /sdcard found.
Opening update package...
Installing update...
installing samsung updater extensions
installing samsung updater extensions for toro
Writing bootloader...
Writing LTE radio...
Writing CDMA radio...
Unable to open modem device (No such file or directory)
IOCTL_MODEM_GOTA_START failed: (-1)
script aborted: assert failed: samsung.update_cdma_modem(
package_extract_file("radio-cdma.img"))
assert failed: samsung.update_cdma_modem( package_extract_file("radio-cdma.img"))
E:Error in /sdcard/Download/403radios_btldr.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/Download/403radios_btldr.zip")
I:using /data/media, no /sdcard found.
It looks to me that your baseband is showing up as unknown and the assert failed because of that.
I would try flashing back to stock (starting from scratch) in fastboot with the official images from google. http://code.google.com/android/nexus/images.html
First I will give you the usual response (not trying to be a douche though lol ) : should've put this in Q&A section, should've checked for other threads about this first since I'm sure there are others, look through development section for the appropriate radios thread that will answer your questions, etc. etc...
Now to answer, I'm assuming by "no radio" you mean no functioning signal i.e. no data/sms/calls? if so I'd recommend looking in the development section either here or at Rootzwiki (recommend there first since they have a sticky thread with all current radios/roms) for a flashable zip... if you want to do it a better way I would suggest learning about ADB and Fastboot and doing it through those means, it does require a little bit of computer savvy to set up but is immensely helpful in many ways... also I don't believe the zip you are trying to flash is the correct one, or you may be flashing it wrong... I am on the go on my GNex but can give links if you can't find anything
blazing through on my Nexus Prime via XDA app
seems to me that the cwm zip you're using is not doing it right. attach that cwm zip for us to look at it, or a link to it.
better yet, use fastboot as suggested.
doh sorry for being in the wrong thread.. if a mod can move to Q&A..
thanks for the replies, i was able to get the google roms and update successfully. Here are the versions I was using and commands for anyone else..
fastboot flash bootloader bootloader-maguro-primekj10.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxkk1.img
fastboot reboot-bootloader
fastboot -w update image-yakju-itl41f.zip
nfoman said:
doh sorry for being in the wrong thread.. if a mod can move to Q&A..
thanks for the replies, i was able to get the google roms and update successfully. Here are the versions I was using and commands for anyone else..
fastboot flash bootloader bootloader-maguro-primekj10.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxkk1.img
fastboot reboot-bootloader
fastboot -w update image-yakju-itl41f.zip
Click to expand...
Click to collapse
thx for posting your solution.. i hate it when people find a solution and abandon the thread
nfoman said:
doh sorry for being in the wrong thread.. if a mod can move to Q&A..
thanks for the replies, i was able to get the google roms and update successfully. Here are the versions I was using and commands for anyone else..
fastboot flash bootloader bootloader-maguro-primekj10.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxkk1.img
fastboot reboot-bootloader
fastboot -w update image-yakju-itl41f.zip
Click to expand...
Click to collapse
Those are commands for GSM images.
So... According to your OP you had flashed a CDMA rom on a GSM device. Then were trying to flash CDMA radios?
That is the reason why you had no service and the .zip file wouldn't flash.
Make sure you flash the correct ROM's the future.
Hi everyone,
After about 12 hours of research and no solution here is my question regarding my T999.
For about 2 days I've been unable to flash any roms or recoveries. I currently run CM11 nightlies and was updating fine since the first CM11 nightlies until this problem. I originally thought I had lost root, but that didn't turn out to be the case. I've been unable to boot into recovery and everytime I try to do so I'm taken to what I think is the stock recovery (Android with turning gears on its back) even though I have CWM installed and set up. As a result, CM11 01/01 auto installs and I never see the recovery menu options.
Furthermore, every time I attempt to connect to my PC to flash with ODIN I get an "Samsung Mobile USB MODEM failed" error from Windows 7 (64bit). Here's what I've tried so far,
1- Re-downloaded and installed Samsung drivers (about 3 times). Installed from KIES once and just drivers twice.
2- Tried pushing recovery through ADB but get a "-1" error at the end of the process. (Seems like a permission error)
3- Tried reflashing recovery with ROM and Goo Manager but it takes me back to the aforementioned stock recovery.
4- Tried to flash using Heimdall but also get errors.
At ODIN MODE my T999 reads,
PRODUCT NAME:SGH-T999
CUSTOM BINARY DOWNLOAD: Yes (1 count)
CURRENT BINARY: Custom
SYSTEM STATUS: None
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER AP SWREV: 1
I'm aware of these posts, but find my issue to be different since Windows is not installing appropriate drivers.
http://forum.xda-developers.com/showthread.php?t=2541437
http://forum.xda-developers.com/showthread.php?t=2221279
Any insights would be appreciated,
Cheers
Did you put the phone in download before connecting to Windows ? Download mode drivers for Windows are slightly different from what Kies has. In addition, you have to install those drivers before you start Odin. So best close it before you plug in.
Sometimes you may have to restart windows after installing the Download Mode Drivers.
Perseus71 said:
Did you put the phone in download before connecting to Windows ? Download mode drivers for Windows are slightly different from what Kies has. In addition, you have to install those drivers before you start Odin. So best close it before you plug in.
Sometimes you may have to restart windows after installing the Download Mode Drivers.
Click to expand...
Click to collapse
Hi Perseus,
Sorry I didn't state that. I thought it would be assumed. Yes, definitely put into download mode with debug enabled before connecting it. It tries to install it as a "MSM8960" and Samsung Mobile USB Modem always fails to install... here's a screenshot of my device manager and driver install.
Cheers,
Pictures are huge, so please click on the links!
http://www.image-share.com/upload/2392/209.jpg
http://www.image-share.com/upload/2392/210.jpg
In that case find the original ADB Drivers. They are not from Samsung. Once the errors are resolved, your problem will likely go away.
Perseus71 said:
In that case find the original ADB Drivers. They are not from Samsung. Once the errors are resolved, your problem will likely go away.
Click to expand...
Click to collapse
Thanks Perseus,
I already had the original ADB drivers. I play around with Eclipse quite often so I try to keep my SDK files updated. Here's an update though. I was able to re-flash CWM 6.0.5 recovery in download mode using Heimdall and now Custom Binary reads 2 in ODIN Mode. Though Heimdall frontend recognizes my device and flashes successfully, it never really loads CWM. Just jumps straight into an auto-install of my current rom (CM11 01/01).
Here's the recovery log under /cache/recovery. Thank you for your insight!
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting recovery on Tue Dec 31 19:37:48 2013
framebuffer: fd 4 (720 x 1280)
ClockworkMod Recovery v6.0.4.3
recovery filesystem table
=========================
0 /boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot 0
1 /recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery 0
2 /cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache 0
3 /system ext4 /dev/block/platform/msm_sdcc.1/by-name/system 0
4 /data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata -16384
5 /storage/sdcard1 auto /devices/platform/msm_sdcc.3/mmc_host/mmc1 0
6 /storage/usbdisk0 auto /devices/platform/msm_hsusb_host/usb 0
7 /tmp ramdisk ramdisk 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sdcard during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
W:Unable to get recovery.fstab info for /external_sd during fstab generation!
I:Completed outputting fstab.
I:Connected to Vold..
I:110 0 sdcard /storage/sdcard1 1
I:110 0 sda /storage/usbdisk0 0
I:200 0 Volumes listed.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.boot.hardware=qcom
ro.boot.debug_level=0x4f4c
ro.boot.cp_debug_level=0x55FF
ro.boot.emmc_checksum=3
ro.boot.warranty_bit=1
ro.boot.bootloader=T999UVUEMJC
ro.boot.nvdata_backup=0
ro.boot.boot_recovery=1
ro.boot.batt_check_recovery=1
ro.boot.emmc=true
ro.boot.serialno=761bc55c
ro.boot.baseband=msm
ro.serialno=761bc55c
ro.bootmode=unknown
ro.baseband=msm
ro.bootloader=T999UVUEMJC
ro.hardware=qcom
ro.revision=16
ro.emmc=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
ro.build.id=JLS36G
ro.build.display.id=cm_d2tmo-userdebug 4.3 JLS36G 0c51335b75 test-keys
ro.build.version.incremental=0c51335b75
ro.build.version.sdk=18
ro.build.version.codename=REL
ro.build.version.release=4.3
ro.build.date=Sun Oct 6 04:26:36 PDT 2013
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=hudson
ro.build.host=koushik-lion
ro.build.tags=test-keys
ro.product.model=SGH-T999
ro.product.brand=samsung
ro.product.name=d2uc
ro.product.device=d2tmo
ro.product.board=MSM8960
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8960
ro.build.product=d2tmo
ro.build.description=d2uc-user 4.1.2 JZO54K T999UVDMD5 release-keys
ro.build.fingerprint=samsung/d2uc/d2att:4.1.2/JZO54K/T999UVDMD5:user/release-keys
ro.build.characteristics=default
ro.cm.device=d2tmo
rild.libargs=-d /dev/smd0
telephony.lteOnGsmDevice=1
ro.telephony.default_network=9
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.sf.lcd_density=320
ro.hwui.text_cache_width=2048
ro.vendor.extension_library=/system/lib/libqc-opt.so
ro.ril.hsxpa=1
ro.ril.gprsclass=10
persist.radio.add_power_save=1
persist.radio.snapshot_disabled=1
com.qc.hardware=true
persist.radio.apm_sim_not_pwdn=1
ro.ril.transmitpower=true
ro.opengles.version=131072
persist.audio.vr.enable=false
persist.audio.speaker.location=high
persist.timed.enable=true
ro.emmc.sdcard.partition=17
ro.use_data_netmgrd=true
persist.data_netmgrd_nint=16
lpa.decode=true
rild.libpath=/system/lib/libril-qc-qmi-1.so
ril.subscription.types=NV,RUIM
ro.ril.svdo=true
ro.cdma.subscribe_on_ruim_ready=true
persist.radio.no_wait_for_card=0
media.aac_51_output_enabled=true
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.audio.fluence.mode=endfire
persis
Cheers,
Can you try Odin Mobile and TWRP ?
Hey Perseus,
Thanks for working with me through this. I had forgot to m mentioned that I had tried ODIN Mobile already. Decided to try again and it didn't work. I went back to cache/recovery/ and saw a command for with rw permissions. Here's what it said
boot-recovery
--update_package=/sdcard/0/cmupdater/cm-11-20140101-NIGHTLY-d2tmo.zip
Simply backed up the file and erased the file, rebooted into recovery and voilà, it worked.
Your patience is appreciated!
Cheers
Sent from my SGH-T999 using XDA Premium 4 mobile app
Glad it all worked.