So recently I unlocked the boot loader of my Moto G 2nd generation and installed a custom rom so that I can get the google assistant to work on it by changing the build.prop. This was a test before I moved onto my Nexus.
So I got the Moto g 2nd Generation to work so I decided to move to the Nexus device.
I unlocked my bootloader "fastboot flashing unlock", Flash factory images, setup my device, Flashed TWRP using the Android Development Bridge and fastboot with the command "fastboot flash recovery twrp-3.0.2-2-bullhead.img" and then booted into recovery. I then extracted my build.prop using ADB "adb pull /system/build.prop" and edited it by changing ro.product.model=Nexus 5X to ro.product.model=Pixel and added the line ro.opa.eligible_device=true. I then pushed it back to my device and changed the permission "adb push build.prop /system/build.prop" "adb shell" "chmod 644 /system/build.prop". I then rebooted my device and checked my device information and it still has the model name of Nexus 5X. I then rebooted into recovery again and check to see if the build.prop had saved and it still had the changes applied but android doesn't seem to notice the changes so I wiped the cache and dalvik cache and it didn't help.
So I was wondering what can I do to fix this and can I edit the build.prop without root I am running android NBD90W and thank you in advance.
This is the start of original Build.prop of my device (parts that will be changed are underlined
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=NBD90W
ro.build.display.id=NBD90W
ro.build.version.incremental=3239497
ro.build.version.sdk=24
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=7.0
ro.build.version.security_patch=2016-10-05
ro.build.version.base_os=
ro.build.date=Thu Sep 1 06:03:08 UTC 2016
ro.build.date.utc=1472709788
ro.build.type=user
ro.build.user=android-build
ro.build.host=kpfj12.cbf.corp.google.com
ro.build.tags=release-keys
ro.build.flavor=bullhead-user
ro.product.model=Nexus 5X
ro.product.brand=google
ro.product.name=bullhead
ro.product.device=bullhead
ro.product.board=bullhead
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=LGE
ro.product.locale=en-US
ro.wifi.channels=
ro.board.platform=msm8992
# ro.build.product is obsolete; use ro.product.device
ro.build.product=bullhead
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=bullhead-user 7.0 NBD90W 3239497 release-keys
ro.build.fingerprint=google/bullhead/bullhead:7.0/NBD90W/3239497:user/release-keys
ro.build.characteristics=nosdcard
# end build properties
And this is the start of the edited build.prop (changes are underlined)
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=NBD90W
ro.build.display.id=NBD90W
ro.build.version.incremental=3239497
ro.build.version.sdk=24
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=7.0
ro.build.version.security_patch=2016-10-05
ro.build.version.base_os=
ro.build.date=Thu Sep 1 06:03:08 UTC 2016
ro.build.date.utc=1472709788
ro.build.type=user
ro.build.user=android-build
ro.build.host=kpfj12.cbf.corp.google.com
ro.build.tags=release-keys
ro.build.flavor=bullhead-user
ro.product.model=Pixel
ro.product.brand=google
ro.product.name=bullhead
ro.product.device=bullhead
ro.product.board=bullhead
ro.opa.eligible_device=true
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=LGE
ro.product.locale=en-US
ro.wifi.channels=
ro.board.platform=msm8992
# ro.build.product is obsolete; use ro.product.device
ro.build.product=bullhead
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=bullhead-user 7.0 NBD90W 3239497 release-keys
ro.build.fingerprint=google/bullhead/bullhead:7.0/NBD90W/3239497:user/release-keys
ro.build.characteristics=nosdcard
# end build properties
And this is the start of the build.prop of my Moto G 2nd Generation running cyanogenmod 14 beta with the google assistant (changed parts will be underlined)
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=NBD90Z
ro.build.display.id=cm_titan-userdebug 7.0 NBD90Z 9d1048a4a0 test-keys
ro.build.version.incremental=9d1048a4a0
ro.build.version.sdk=24
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=7.0
ro.build.version.security_patch=2016-10-05
ro.build.version.base_os=
ro.build.date=Tue Oct 11 03:38:56 CEST 2016
ro.build.date.utc=1476149936
ro.build.type=userdebug
ro.build.user=luk1337
ro.build.host=build2.dev.xda-developers.com
ro.build.tags=test-keys
ro.build.flavor=cm_titan-userdebug
ro.product.brand=motorola
ro.product.name=cm_titan
ro.product.board=MSM8226
ro.product.model=Pixel
ro.opa.eligible_device=true
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=motorola
ro.product.locale=en-US
ro.wifi.channels=
ro.board.platform=msm8226
ro.build.characteristics=default
ro.cm.device=titan
# end build properties
I know that it looks like there is no _ in ro.opa.eligible_device=true but there is.
Here are some links to the guides that I have followed
https://verdictforu.com/2016/10/11/google-assistant-on-android-nougat-devices/
http://forum.xda-developers.com/android/software/guide-how-to-enable-google-assistant-t3477879
Ok I have found the problem. Apparently it's not just me, dratsablive is experiencing that same problem
What's bizarre is if I flash TWRP then check build.prop through terminal it has the changes. But when I reboot phone and check through adb shell then cat /system/build.prop changes gone.
But changes are there any time I check through TWRP
Click to expand...
Click to collapse
And david279 has stated that you do need root to get changes in the build.prop to load
Gotta root for the changes to take effect
Click to expand...
Click to collapse
If anyone knows if this is true then please tell me but from my experience this is true because my Moto G 2nd generation with root can load build.prop changes but my Nexus 5X running stock android can't.
Hmm. Worked fine on my G 2015. Once my bootloader is unlocked and I'm all flashed on my new 5X, I'll give it a go.
JaredTamana said:
Hmm. Worked fine on my G 2015. Once my bootloader is unlocked and I'm all flashed on my new 5X, I'll give it a go.
Click to expand...
Click to collapse
I know editing the build.prop on my Moto G 2014 works just fine but it doesn't seem to work on my Nexus 5X. All thou my Moto G 2014 is running a rooted cyanogenmod and my Nexus 5X is running stock android with an unlocked bootloader. I'm just wondering if this is related to my devices root access.
I will try to take a look into editing the build.prop using TWRP directly instead of pushing the file onto the device.
Tools needed
(Optional)Google Factory images : https://developers.google.com/android/nexus/images
Android Development Bridge/Fastboot (I think this is the link): https://developer.android.com/studio/index.html
TWRP for Nexus 5X : https://twrp.me/devices/lgnexus5x.html
Super Su : https://download.chainfire.eu/1003/SuperSU/SR1-SuperSU-v2.78-SR1-20160915123031.zip
(Optional)Notepad++ : https://notepad-plus-plus.org/download/v7.html
Click to expand...
Click to collapse
Before we get started
Anything you do to your device is your responsibility and I am not resposible for what you do with it. If you brick your device it is not my fault. This also my void your devices Warrenty. Unlocking your bootloader will also factory reset your device
Click to expand...
Click to collapse
To get the google assistant to work on my Nexus 5X I needed to unlock my boot loader
1. fastboot flashing unlock (confirm this action on your device)
2. (Optional) Apply Nexus 5X factory images
3. Boot device
4. Restart device into bootloader by holding down my power button and volume down button
5. Flash TWRP recovery "fastboot flash recovery twrp-3.0.2-2-bullhead.img"
6. Boot into my new recovery using the volume keys and power button on my phone
7. Transfer SuperSu (SR1-SuperSU-v2.78-SR1-20160915123031.zip) onto my phone by using a file manager
8. Installed SuperSu using TWRP
9. Edit my build prop to include the new lines for it to activate the Google Assistant. This can be done in many different ways I will run you through each of them.
Method 1.
1. In TWRP mount the system
2. Use "adb pull /system/builb.prop"
3. Edit the build.prop using a program like notepad++
4. Change "ro.product.model=Nexus 5X" to "ro.product.model=Pixel"
5. Add a new line somewhere and type in "ro.opa.eligible_device=true"
6. Push the file back onto the device "adb push build.prop /system/build.prop"
7. Now fix the permissions using "adb shell" "chmod 644 /system/build.prop and reboot device.
Method 2.
1. In TWRP mount the system
2. Open the TWRP terminal and type in "vi /system/build.prop"
Use this guide to learn how to use the vi command https://www.washington.edu/computing/unix/vi.html
3. Scroll through the build.prop using the arrows until you find ro.product.model=Nexus 5X
4. Change "ro.product.model=Nexus 5X" to ro.product.model=Pixel (Press "i" to edit)
5. Press escape and add a new line by pressing "o"
6. Type in "ro.opa.eligible_device=true"
7. Press escape and type in ":w" and press enter
8. Now tap "w" a few times to exit
9. Reboot device
10. Now you can wipe your cache and dalvik cache and reboot your device
I'm sorry if this is a horrible tutorial but I just need to let people that came to this tread how to set up the google assistant. You will need root for the build.prop changes to apply.
Related
Just curious on how to unroot my evo after rooting w/ unrevoked3. The S-On shows in the reboot mode, im not even sure that i downloaded the (2) required downloads. i tried to download the PC36IMG and its saying that its not valid. i have no idea what im doing, i tried to install the new update 3.7 and my phone showed the android, w/ a triangle w/ a yellow exclamation point in the center....i had to take the battery out because it just froze up. i really want this phone back to the way it was when i bought it, im not good at things like this, im desperate for some help. i just want to go to sprint and see if maybe there might be someone to help me but im afraid to go that far just yet... another thing, there is this that shows up on my sd card:
Starting recovery on Mon Dec 13 22:33:54 2010
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
ClockworkMod Recovery v2.5.0.1
Fixing execute permissions for /cache
I:Set boot command "boot-recovery"
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=ECLAIR
ro.build.display.id=koush_supersonic-eng 2.1-update1 ECLAIR eng.koush.20100714.213746 test-keys
ro.build.version.incremental=eng.koush.20100714.213746
ro.build.version.sdk=7
ro.build.version.codename=REL
ro.build.version.release=2.1-update1
ro.build.date=Wed Jul 14 21:38:26 PDT 2010
ro.build.date.utc=1279168706
ro.build.type=eng
ro.build.user=koush
ro.build.host=Koushik-OSx86.local
ro.build.tags=test-keys
ro.product.model=HTC Evo (US)
ro.product.brand=generic
ro.product.name=koush_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=mdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=qsd8k
ro.build.product=supersonic
ro.build.description=koush_supersonic-eng 2.1-update1 ECLAIR eng.koush.20100714.213746 test-keys
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
ro.config.sync=yes
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=HT072HL00439
ro.bootmode=recovery
ro.baseband=2.15.00.09.01
ro.carrier=COMMON
ro.bootloader=0.97.0000
ro.hardware=supersonic
ro.revision=3
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:Set boot command ""
Starting recovery on Mon Dec 13 22:34:00 2010
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
ClockworkMod Recovery v2.5.0.1
I:Set boot command "boot-recovery"
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=ECLAIR
ro.build.display.id=koush_supersonic-eng 2.1-update1 ECLAIR eng.koush.20100714.213746 test-keys
ro.build.version.incremental=eng.koush.20100714.213746
ro.build.version.sdk=7
ro.build.version.codename=REL
ro.build.version.release=2.1-update1
ro.build.date=Wed Jul 14 21:38:26 PDT 2010
ro.build.date.utc=1279168706
ro.build.type=eng
ro.build.user=koush
ro.build.host=Koushik-OSx86.local
ro.build.tags=test-keys
ro.product.model=HTC Evo (US)
ro.product.brand=generic
ro.product.name=koush_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=mdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=qsd8k
ro.build.product=supersonic
ro.build.description=koush_supersonic-eng 2.1-update1 ECLAIR eng.koush.20100714.213746 test-keys
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
ro.config.sync=yes
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=HT072HL00439
ro.bootmode=recovery
ro.baseband=2.15.00.09.01
ro.carrier=COMMON
ro.bootloader=0.97.0000
ro.hardware=supersonic
ro.revision=3
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...
I:Running script:
I:
install_zip DATA:local/unrevoked-forever.zip
print "Rebooting in 10 seconds..."
sleep 10
Parsed /tmp/extendedcommand
calling command install_zip
-- Installing: DATA:local/unrevoked-forever.zip
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: DATA:local/unrevoked-forever.zip
Opening update package...
I:Update file path: /data/local/unrevoked-forever.zip
Installing update...
I:Trying update-binary.
unrEVOked forever S-OFF patch v1.1
Verifying system type...
E:unsupported radio version
E:Update failed. Check /sdcard/soff.log.
E:Error in /data/local/unrevoked-forever.zip
(Status 42)
Installation aborted.
Failure at line 1:
install_zip DATA:local/unrevoked-forever.zip
SOOOOOOOOO, AFTER LOOKING THIS OVER I SEE THE TERM (UNREVOKED FOREVER BEING USED MULTIPLE TIMES, IM PRETTY SURE I DIDNT USE THAT METHOD, I DONT THINK I FLASHED ANYTHING, IF ANYONE COULD HELP ME I WOULD REALLY APPRECIATE IT........I NEEEEEEEED HELP!!!!
I have read that some people lose root and go back to stock applying this update. Good Luck.
http://forum.xda-developers.com/showthread.php?t=874091
You may also try this link:
http://forum.xda-developers.com/showthread.php?t=780141&highlight=unrevoked
Since you mentioned your phone shows S-ON, all you could do is place the PC36IMG on the root of the SD and then boot in the bootloader. Power + Vol Down and then apply the update. Try to relax and take time to read thoroughly. As long as you can boot into your bootloader, your phone should still work.
i hope this works...like i said im not good at this, and if this helps i will thank you alot.....
yeah, that didnt do anything but show me a bunch of blank pages where nothing would load and one link actually opened and it was all in a foreign language, anymore ideas??
am i supposed to upload the rapidshare file?? and if im supposed to what are the next steps in regards to unrooting my phone. i need step by step instructions if you will please, i cant afford to ruin my phone...
steveno131 said:
am i supposed to upload the rapidshare file?? and if im supposed to what are the next steps in regards to unrooting my phone. i need step by step instructions if you will please, i cant afford to ruin my phone...
Click to expand...
Click to collapse
Can you log onto Gtalk? I will send PM you my screen name.
Just sent you a PM. Check it out.
the pc36img.zip is invalid.....i wonder why?? how can i download the pc36img w it being fully functional, and if that worked i dont understand where this root is on my sd card, ive searched high and low and come up empty handed.....is root a folder or sub folder, if so i cant find it, i didnt mention this before but i attempted to root my phone using unrevoked3 and the 1st attempt failed and then i got excited, i think i extracted the 2 necessary files they asked me to and so the i tried to root the second time and it said it was a triumph.....and then magically my phone was rooted.....please dont give up on me.
dont get mad at me, but what is G talk?? i have a gmail account is that kind of related?? im at work im about to be off, i can be available in like 30 min to be free from everything if you still want to help me...
steveno131 said:
dont get mad at me, but what is G talk?? i have a gmail account is that kind of related?? im at work im about to be off, i can be available in like 30 min to be free from everything if you still want to help me...
Click to expand...
Click to collapse
I have no reason to get mad man. Just log onto your GMail account on the left side you will see a window that says Chat. Just add me up I sent you a PM with my username. I will be around for a while just let me know and I will try to help as best I can.
i checked my hotmail acct and i didnt see any user name whats a pm?? im going to log on to my gmail right now
PM is a private message. Scroll to the very top of the XDA forums, you will see 'Welcome, steveno131.' Under that you will see 'You last visited on....' and 'Private Messages' under that. Click on Private Messages to check your PMs.
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...
So since I bought my Galaxy Nexus, I was not able to update my device over the air. I used to receive the update, download it, then reboot to install. I always get the android mascot laying on his back with his internals open stuck.
After updating manually from 4.0.1 to 4.0.2 everything seemed to work perfectly, until 4.0.4 came out. The same problem happened again.
I tried to update it manually like the last time. but I got ths message:
Code:
-- Installing: /sdcard/7f97fbc19417.signed-yakju-IMM76D-from-ICL53F.7f97fbc1.zip
Finding update package...
I:Update location: /sdcard/7f97fbc19417.signed-yakju-IMM76D-from-ICL53F.7f97fbc1.zip
I:using /data/media, no /sdcard found.
Opening update package...
Installing update...
installing samsung updater extensions
Verifying current system...
file "/system/build.prop" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/build.prop", "c47a6508986e87bdd807aabc2418c1399735e34e", "4bf6dfef298bc3a61bb9613cb814f2ee0a806d14")
assert failed: apply_patch_check("/system/build.prop", "c47a6508986e87bdd807aabc2418c1399735e34e", "4bf6dfef298bc3a61bb9613cb814f2ee0a806d14")
E:Error in /sdcard/7f97fbc19417.signed-yakju-IMM76D-from-ICL53F.7f97fbc1.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/7f97fbc19417.signed-yakju-IMM76D-from-ICL53F.7f97fbc1.zip")
I:using /data/media, no /sdcard found.
I think my problem relies on build.prop file. Here is mine:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=ICL53F
ro.build.display.id=ICL53F
ro.build.version.incremental=235179
ro.build.version.sdk=14
ro.build.version.codename=REL
ro.build.version.release=4.0.2
ro.build.date=Thu Dec 8 01:24:15 UTC 2011
ro.build.date.utc=1323307455
ro.build.type=user
ro.build.user=android-build
ro.build.host=vpbs3.mtv.corp.google.com
ro.build.tags=release-keys
ro.product.model=Galaxy Nexus
ro.product.brand=google
ro.product.name=yakju
ro.product.device=maguro
ro.product.board=tuna
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=omap4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=maguro
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=yakju-user 4.0.2 ICL53F 235179 release-keys
ro.build.fingerprint=google/yakju/maguro:4.0.2/ICL53F/235179:user/release-keys
ro.build.characteristics=nosdcard
# end build properties
#
# system.prop for maguro
#
rild.libpath=/vendor/lib/libsec-ril.so
rild.libargs=-d /dev/ttys0
telephony.lteOnCdmaDevice=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
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
ro.config.ringtone=Girtab.ogg
ro.config.notification_sound=Proxima.ogg
ro.config.alarm_alert=Cesium.ogg
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.url.legal=***/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=***/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.error.receiver.system.apps=com.google.android.feedback
ro.setupwizard.enterprise_mode=1
keyguard.no_require_sim=true
drm.service.enabled=true
camera.flash_off=0
ro.com.google.mcc_fallback=262
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.config.vc_call_vol_steps=100
Could you guys help me fix this?
It looks like your trying to apply the zip while it's on the SDCARD. Are you rooted? Try flashing the img not zip file.
Try re downloading and store on your computer and flash remotely via adb. Let us know how you get on.
Sent from my Galaxy Nexus using Tapatalk
shonas said:
So since I bought my Galaxy Nexus, I was not able to update my device over the air. I used to receive the update, download it, then reboot to install. I always get the android mascot laying on his back with his internals open stuck.
After updating manually from 4.0.1 to 4.0.2 everything seemed to work perfectly, until 4.0.4 came out. The same problem happened again.
I tried to update it manually like the last time. but I got ths message:
Code:
-- Installing: /sdcard/7f97fbc19417.signed-yakju-IMM76D-from-ICL53F.7f97fbc1.zip
Finding update package...
I:Update location: /sdcard/7f97fbc19417.signed-yakju-IMM76D-from-ICL53F.7f97fbc1.zip
I:using /data/media, no /sdcard found.
Opening update package...
Installing update...
installing samsung updater extensions
Verifying current system...
file "/system/build.prop" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/build.prop", "c47a6508986e87bdd807aabc2418c1399735e34e", "4bf6dfef298bc3a61bb9613cb814f2ee0a806d14")
assert failed: apply_patch_check("/system/build.prop", "c47a6508986e87bdd807aabc2418c1399735e34e", "4bf6dfef298bc3a61bb9613cb814f2ee0a806d14")
E:Error in /sdcard/7f97fbc19417.signed-yakju-IMM76D-from-ICL53F.7f97fbc1.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/7f97fbc19417.signed-yakju-IMM76D-from-ICL53F.7f97fbc1.zip")
I:using /data/media, no /sdcard found.
Click to expand...
Click to collapse
You do not have a stock build.prop file. I've posted a stock ICL53F one before, but can't remember where. Regardless, the "update" link in my signature explains how to extract it yourself from the stock image.
Additionally, it seems like you have other issues as well. You shouldn't be getting sdcard errors...
Sent from my Galaxy Nexus using Tapatalk 2
what kind of issues? I really appreciate any help I can get.
Sent from my Galaxy Nexus using XDA
shonas said:
what kind of issues? I really appreciate any help I can get.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
It you want it to install automatically, you need to have the recovery that came with 4.0.4 installed. Otherwise you need CWM installed. A recovery from a different build version won't work.
As well, all the files in /system have to be original -- if you've made changes, you will have to undo them.
Stock Recovery
efrant said:
It you want it to install automatically, you need to have the recovery that came with 4.0.4 installed. Otherwise you need CWM installed. A recovery from a different build version won't work.
As well, all the files in /system have to be original -- if you've made changes, you will have to undo them.
Click to expand...
Click to collapse
I went to the post you have in the signature. Downloaded the Stock ICL53 and extracted the build.prop file. I cannot implement it to my device to replace the old file.
I have CWM Touch recovery installed. It seems my device have so many problems that I have to do a full wipe and a fresh installation of version 4.0.4 to fix all issues.
Thanks for your help. I did not want to bother you more. Starting fresh this time. Bye Bye data.
Hi,
I have a nexus one running PA-3.99rc2 with the following superuser modifications:
* replaced stock superuser app with SuperSU (system app)
* installed adbtoggle (system app)
* I do have the exposed framework and xprivacy installed, with no restrictions on the settings app, the adbtoggle app and the supersu app.
In the developer options, I have
* "Root Access" set to disabled.
* USB debugging" unchecked
* "select debug app" -> no debug app selected
However, what happens is that whenever I connect a USB cable, I can just run 'adb shell' and get a root prompt.
C:\> adb shell
[email protected]:/
Click to expand...
Click to collapse
This is possible irrespective of the adb toggle setting or the root access setting or the USB debugging setting.
I am simply handed a shell even when USB debugging is turned off, whether I asked for it or not.
I haven't tried it over wifi but I have reason to believe that it would be accessible all the same.
When I toggle ADB using the app or the settings panel, I do see the notification that usb debugging was turned on or off - but in reality it has no effect on the actual state of the debug bridge (which is permanently on.)
I did notice:
[email protected]:/ # cd /
cd /
[email protected]:/ # grep -e 'start adbd' init*
grep -e 'start adbd' init*
init.mahimahi.usb.rc: start adbd
init.mahimahi.usb.rc: start adbd
init.mahimahi.usb.rc: start adbd
init.mahimahi.usb.rc: start adbd
init.mahimahi.usb.rc: start adbd
init.rc: start adbd
init.usb.rc: start adbd
init.usb.rc: start adbd
init.usb.rc: start adbd
init.usb.rc: start adbd
Click to expand...
Click to collapse
All the init scripts in "/" have exec, and are owned by root: "-rwxr-x--- root root", unmodified since the ROM's installation.
Are the init scripts starting up adbd irrespective of my settings? Or am I having/doing something wrong?
Has anyone else observed this behaviour?
Is there any way to fix this behaviour and have adbd run only when asked to?
Thanks in advance,
fruit-salad
===================
[email protected]:/ # uname -a
uname -a
Linux localhost 2.6.38.8-evervolv-02117-g69a13bd #1 PREEMPT Sat Sep 28 03:33:41
PDT 2013 armv7l GNU/Linux
I'm running Paranoid Android 3.99.1-RC2- Release 2 from (d-h.st/BuG)
gApps not installed yet.
boot, system and cache were wiped before install, however I did retain my sd-ext partition.
I don't have any old odex files on the sd-ext, a2sd re-optimized the apps on my sd-ext when enabled.
UPDATE:
========
my default.prop has:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
persist.sys.usb.config=mass_storage,adb
persist.service.adb.enable=1
persist.sys.strictmode.disable=true
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
Click to expand...
Click to collapse
but trying to change
persist.service.adb.enable=1 to persist.service.adb.enable=0
and
persist.sys.usb.config=mass_storage,adb to persist.sys.usb.config=mass_storage
isn't helping. Changes are lost after an update.
According to ?t=2209401 build.prop isn't editable -- is default.prop also not editable?
I did remount / "rw" before editing.
Help?
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.