Database Info

[Solved] No ADP1.5 Updates work for me

I can't update to 1.5 on any build, I can not figure it out. I wiped before going from Lucid's JFRC33 mod to trying JF ADP1.5 everything installed and booted fine, but as soon as I reboot it gets stuck at the first flash screen. I wiped and tried the update about 3 more times and same thing. I installed JF's RC33 and everything worked, I wiped and tried to update to 1.5 again and same thing, it boots, syncs and once i reboot thats it, it doesnt ever boot. Installed ADP1.1 from JF and everything worked, tried the update and same thing after reboot it doesnt boot. I installed the radio before I ever did anything. I have tried Haykuro's and am getting the same problem. I'd love to be able to update to 1.5
I went into adb and did adb logcat, its looping the same thing. If I wipe it boots, I sign into google, it syncs, one I reboot it never boots it just repeats this over and over in adb:
D/AndroidRuntime( 415):
D/AndroidRuntime( 415): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 415): CheckJNI is OFF
D/AndroidRuntime( 415): --- registering native functions ---
I/Zygote ( 415): Preloading classes...
D/dalvikvm( 415): GC freed 763 objects / 42128 bytes in 7ms
D/dalvikvm( 415): GC freed 278 objects / 17200 bytes in 6ms
D/dalvikvm( 415): GC freed 208 objects / 12664 bytes in 8ms
D/dalvikvm( 415): Trying to load lib /system/lib/libmedia_jni.so 0x0
D/dalvikvm( 415): Added shared lib /system/lib/libmedia_jni.so 0x0
D/dalvikvm( 415): Trying to load lib /system/lib/libmedia_jni.so 0x0
D/dalvikvm( 415): Shared lib '/system/lib/libmedia_jni.so' already loaded in same CL 0x0
D/dalvikvm( 415): Trying to load lib /system/lib/libmedia_jni.so 0x0
D/dalvikvm( 415): Shared lib '/system/lib/libmedia_jni.so' already loaded in same CL 0x0
D/dalvikvm( 415): Trying to load lib /system/lib/libmedia_jni.so 0x0
D/dalvikvm( 415): Shared lib '/system/lib/libmedia_jni.so' already loaded in same CL 0x0
D/dalvikvm( 415): GC freed 462 objects / 29168 bytes in 11ms
D/dalvikvm( 415): GC freed 3579 objects / 171120 bytes in 26ms
D/dalvikvm( 415): GC freed 11306 objects / 400568 bytes in 41ms
D/dalvikvm( 415): GC freed 10462 objects / 438128 bytes in 48ms
D/dalvikvm( 415): GC freed 11013 objects / 460640 bytes in 54ms
D/dalvikvm( 415): GC freed 14354 objects / 505928 bytes in 62ms
D/dalvikvm( 415): GC freed 11294 objects / 480800 bytes in 58ms
D/dalvikvm( 415): GC freed 5966 objects / 250056 bytes in 49ms
D/dalvikvm( 415): GC freed 343 objects / 36704 bytes in 44ms
W/dalvikvm( 415): Exception Ljava/lang/IndexOutOfBoundsException; thrown during Landroid/text/Html$HtmlParser;.<clinit>
D/AndroidRuntime( 415): Shutting down VM
W/dalvikvm( 415): threadid=3: thread exiting with uncaught exception (group=0x4000fe70)
D/dalvikvm( 415): DestroyJavaVM waiting for non-daemon threads to exit
D/dalvikvm( 415): DestroyJavaVM shutting VM down
D/dalvikvm( 415): VM cleaning up
D/dalvikvm( 415): LinearAlloc 0x0 used 1189684 of 4194304 (28%)
D/skia ( 415): purging 6K from font cache [1 entries]
Click to expand...
Click to collapse
Anyone have any ideas?
Update: I'm not sure if this is the real cause cuz I am scared to reboot, but I did notice something new. I reloaded all my apps and crap, and tried to update to 1.5 again. Since I have debian on my SD card, the script that does all the mounting, had a broken link to the /system/sd when I looked did busybox df -h the mounting for the /system/sd was /dev/block/mmcblk0p2 where as LucidREM's mod had it as /dev/mmcblk0p2. Does this seem like a reasonable cause to anyone?
Update: The Apps to SD was the cause. When I would wipe and install ADP1.5 after it booted, the ext2 was mounted /dev/mmcblk0p2, regardless of if I linked or not, the phone would never boot. After doing my backup and getting back al my files form Nandroid and having Lucid's JF RC33 Mod installed, I updated with NO wipe and connected the phone through adb and watched the logcat as it moved everything to /dev/block/mmcblk0p2. I rebooted and everything still works great

This sounds like it might be related to the problem I posted about here:
http://forum.xda-developers.com/showthread.php?t=511454
The "works on first boot but then breaks for subsequent boots" behavior seems similar, and I've also run into looping on "AndroidRuntime START" a couple times - although a battery pull + reboot has always gotten me out of it.
What happens if you go from, say JFv1.43 to JFv1.5 with no intermediate wipe?

-copy jfv1.42_rc33.zip from Jesus Freke to sd card how update.zip
-Turn off
-press home and Red
-wipe and install jfv1.42_rc33
-when wake up
copy jfv1.50_adp1.5 to sd card how update.zip
turn off
press home and red
install jfv1.50_adp1.5
wait and go

satru said:
-copy jfv1.42_rc33.zip from Jesus Freke to sd card how update.zip
-Turn off
-press home and Red
-wipe and install jfv1.42_rc33
-when wake up
copy jfv1.50_adp1.5 to sd card how update.zip
turn off
press home and red
install jfv1.50_adp1.5
wait and go
Click to expand...
Click to collapse
Ive done this, thats the problem, after the update it will boot into adp1.5 but once i reboot again, it just goes into an endless loop with the adb logcat message I posted above.
Now that I loaded the nandroid backup of my RC33 I can try without a wipe and see if it will work, At this point I'm willing to try anything

jairomeo said:
Ive done this, thats the problem, after the update it will boot into adp1.5 but once i reboot again, it just goes into an endless loop with the adb logcat message I posted above.
Now that I loaded the nandroid backup of my RC33 I can try without a wipe and see if it will work, At this point I'm willing to try anything
Click to expand...
Click to collapse
Wipe the SD card after the update. So it doesn't have any update files or recovery.img files in it's base directory.

SOLDIER [X] said:
Wipe the SD card after the update. So it doesn't have any update files or recovery.img files in it's base directory.
Click to expand...
Click to collapse
Unfortunately it has done it with a blank SD card also . Thats why Im hoping maybe someone knows from the logcat what is actually the issue
W/dalvikvm( 415): Exception Ljava/lang/IndexOutOfBoundsException; thrown during Landroid/text/Html$HtmlParser;.<clinit>
D/AndroidRuntime( 415): Shutting down VM
W/dalvikvm( 415): threadid=3: thread exiting with uncaught exception (group=0x4000fe70)
Click to expand...
Click to collapse

Looks like a HTMLParser fails and kill the VM. Not sure where that HTML file is. Have you tried wiping out the cache ?

lacostej said:
Looks like a HTMLParser fails and kill the VM. Not sure where that HTML file is. Have you tried wiping out the cache ?
Click to expand...
Click to collapse
I wiped the phone completely and have had no luck. After I wipe it will boot and I can sign into my account, it will sync and all is well, but whenever I decide to turn off the phone, thats when it no longer boots back up. Ive had adp1.5 running for 5+ hours, but after a reboot it happens. I even texted this by skipping the sign in and just rebooting after the update is complete and it still does the same thing

Anyone know much about Package Manager? (logcat included)

working on getting the IM app instaleld..thought it might be as simple as pulling the apk and doing adb install IM.apk..it fails with a DEXOPT error, here's the logcat. Thoughts?
D/dalvikvm( 338): GC freed 8171 objects / 572600 bytes in 158ms
D/dalvikvm( 338): threadid=17 wakeup: interrupted
D/AndroidRuntime( 793):
D/AndroidRuntime( 793): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 793): CheckJNI is OFF
D/AndroidRuntime( 793): --- registering native functions ---
D/PackageParser( 58): Scanning package: /data/app/vmdl29166.tmp
I/PackageManager( 58): /data/app/vmdl29166.tmp changed; unpacking
D/installd( 36): DexInv: --- BEGIN '/data/app/vmdl29166.tmp' ---
W/dalvikvm( 800): DexOptZ: zip archive '/data/app/vmdl29166.tmp' does not inclu
de classes.dex
W/installd( 36): DexInv: --- END '/data/app/vmdl29166.tmp' --- status=0xff00,
process failed
E/installd( 36): dexopt failed on '/data/dalvik-cache/[email protected]@[email protected]
lasses.dex' res = 65280
W/PackageManager( 58): Package couldn't be installed in /data/app/com.android.
im.apk

Okay scrap that..found that classes.dex had to be there in the apk file - I grabbed the .odex from the IM app and put it in the apk as classes.dex -- right thing to do? wrong thing? now i'm getting this:
E:\>adb install E:\IM.apk
927 KB/s (0 bytes in 326585.000s)
pkg: /data/local/tmp/IM.apk
Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]
adb logcat shows:
D/AndroidRuntime( 827):
D/AndroidRuntime( 827): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 827): CheckJNI is OFF
D/AndroidRuntime( 827): --- registering native functions ---
D/PackageParser( 58): Scanning package: /data/app/vmdl29167.tmp
E/PackageParser( 58): Package com.android.im has no certificates at entry clas
ses.dex; ignoring!
D/AndroidRuntime( 827): Shutting down VM
D/dalvikvm( 827): DestroyJavaVM waiting for non-daemon threads to exit
D/dalvikvm( 827): DestroyJavaVM shutting VM down
D/dalvikvm( 827): HeapWorker thread shutting down
D/dalvikvm( 827): HeapWorker thread has shut down
D/jdwp ( 827): JDWP shutting down net...
D/dalvikvm( 827): VM cleaning up

!
Does anyone have any ideas?

I've been working on getting the IM from CRB34 into 6.0r1. I really want it. But I get stuck, just like you.
Anyone wanna help us?

fwiw the IM app is definitely new. The IM app no longer includes gtalk as the gtalk app is used for that (from the HTC builds)

I'm convincing myself that someone who is online today will know more about package manager than yesterday..gogo!

You can't just rename the odex to dex and dump it into the apk file. Odex is the optimized dex file that is generated specifically for that build of a device. You'd essentially need to get a virgined dex file, or somehow fool the device into thinking its already installed and push the files.
afflaq said:
Okay scrap that..found that classes.dex had to be there in the apk file - I grabbed the .odex from the IM app and put it in the apk as classes.dex -- right thing to do? wrong thing? now i'm getting this:
E:\>adb install E:\IM.apk
927 KB/s (0 bytes in 326585.000s)
pkg: /data/local/tmp/IM.apk
Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]
adb logcat shows:
D/AndroidRuntime( 827):
D/AndroidRuntime( 827): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 827): CheckJNI is OFF
D/AndroidRuntime( 827): --- registering native functions ---
D/PackageParser( 58): Scanning package: /data/app/vmdl29167.tmp
E/PackageParser( 58): Package com.android.im has no certificates at entry clas
ses.dex; ignoring!
D/AndroidRuntime( 827): Shutting down VM
D/dalvikvm( 827): DestroyJavaVM waiting for non-daemon threads to exit
D/dalvikvm( 827): DestroyJavaVM shutting VM down
D/dalvikvm( 827): HeapWorker thread shutting down
D/dalvikvm( 827): HeapWorker thread has shut down
D/jdwp ( 827): JDWP shutting down net...
D/dalvikvm( 827): VM cleaning up
Click to expand...
Click to collapse

strazzere said:
You can't just rename the odex to dex and dump it into the apk file. Odex is the optimized dex file that is generated specifically for that build of a device. You'd essentially need to get a virgined dex file, or somehow fool the device into thinking its already installed and push the files.
Click to expand...
Click to collapse
that was my fear -- any ideas on doing either of those things? dexdumping it perhaps?

afflaq said:
that was my fear -- any ideas on doing either of those things? dexdumping it perhaps?
Click to expand...
Click to collapse
I am not sure, but does it require you to install? Could you try pushing the apk and odex to apps directory and see if it shows up after reboot?

Link2SD problem!! - see Logcat

Hello !!
I installed Link2SD on my Acer liquid E (running LiquidNext 1.9.2).
linked 5 apps.
But after rebooting, Titanium autmoatically crashes, as well as other apps!!
I could not understand what the problem is !
could you please help me ?
Logcat attached

Firstly, I would actually like to thank you on taking the efforts on getting a logcat...
Loads of members nowadays think that their problem is our problem, and hence don't put in efforts in even explaining...
On the other hand, you actually did a good thing :thumbup::good:
Even though I'm not too knowledgeable on such technical stuff, I did go through your logcat (for the simple reason that you took efforts in attaching it in the first place)...
I've (hopefully) identified the problem areas:
Code:
I/Vold ( 284): Vold 2.1 (the revenge) firing up
D/Vold ( 284): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 284): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 284): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
W/Vold ( 284): Ignoring unknown switch 'MSM72K_UDC'
.
.
.
.
I/Installer( 347): connecting...
E/PackageManager( 347): Package com.keramidas.TitaniumBackup has mismatched uid: 0 on disk, 10042 in settings
I/PackageManager( 347): Linking native library dir for /data/app/com.keramidas.TitaniumBackup-1.apk
I/PackageManager( 347): Time to scan packages: 7.069 seconds
W/PackageManager( 347): Unknown permission com.android.vending.permission.UPDATE_MARKET_FAILURE in package com.android.vending.updater
W/PackageManager( 347): Unknown permission android.permission.ADD_SYSTEM_SERVICE in package com.android.phone
W/PackageManager( 347): Unknown permission android.permission.READ_EXTERNAL_STORAGE in package com.cyanogenmod.cmparts
W/PackageManager( 347): Not granting permission android.permission.SEND_DOWNLOAD_COMPLETED_INTENTS to package com.android.browser (protectionLevel=2 flags=0x9be45)
W/PackageManager( 347): Unknown permission com.google.android.gm.permission.READ_GMAIL in package com.google.android.talk
W/PackageManager( 347): Unknown permission android.permission.READ_OWNER_DATA in package com.android.setupwizard
W/PackageManager( 347): Unknown permission android.permission.WRITE_OWNER_DATA in package com.android.setupwizard
W/PackageManager( 347): Unknown permission com.google.android.gm.permission.WRITE_GMAIL in package com.android.settings
W/PackageManager( 347): Unknown permission com.google.android.gm.permission.READ_GMAIL in package com.android.settings
W/PackageManager( 347): Unknown permission com.google.android.gm.permission.READ_GMAIL in package com.google.android.apps.uploader
W/PackageManager( 347): Unknown permission com.google.android.voicesearch.SHORTCUTS_ACCESS in package com.google.android.googlequicksearchbox
W/PackageManager( 347): Unknown permission android.permission.READ_EXTERNAL_STORAGE in package com.android.vending
W/PackageManager( 347): Not granting permission android.permission.SEND_DOWNLOAD_COMPLETED_INTENTS to package com.android.vending (protectionLevel=2 flags=0xabec5)
W/PackageManager( 347): Unknown permission android.permission.SEND_SMS_NO_CONFIRMATION in package com.android.vending
W/PackageManager( 347): Not granting permission android.permission.STATUS_BAR to package com.android.vending (protectionLevel=3 flags=0xabec5)
W/PackageManager( 347): Not granting permission android.permission.PACKAGE_USAGE_STATS to package com.android.vending (protectionLevel=2 flags=0xabec5)
W/PackageManager( 347): Unknown permission android.permission.PACKAGE_VERIFICATION_AGENT in package com.android.vending
W/PackageManager( 347): Unknown permission com.google.android.verifier.permission.UPDATE_VERIFIER in package com.android.vending
W/PackageManager( 347): Not granting permission android.permission.INSTALL_PACKAGES to package com.chelpus.lackypatch (protectionLevel=3 flags=0xbe46)
W/PackageManager( 347): Not granting permission android.permission.DELETE_PACKAGES to package com.chelpus.lackypatch (protectionLevel=3 flags=0xbe46)
W/PackageManager( 347): Not granting permission android.permission.CLEAR_APP_USER_DATA to package com.chelpus.lackypatch (protectionLevel=2 flags=0xbe46)
W/PackageManager( 347): Unknown permission android.permission.READ_OWNER_DATA in package com.android.email
W/PackageManager( 347): Not granting permission android.permission.DEVICE_POWER to package com.android.deskclock (protectionLevel=2 flags=0x8be45)
(I've put in dots .... to just state that there isn't any error there)
From what I've seen, I believe that your partition (since you are using link2sd) isn't formatted properly (or mounted)...and titanium was linked to your partition (am I right?)
Do your system apps also force close?
There's an error with the status bar...
And ya, because of that logcat, I hope we see more of such members in the future :beer:

I agree. I am thinking that your partitions are not set up correctly. IIRC from when I used Link2Sd, you had to have 1-Fat32 for normal stuff and 1-Fat32 for the apps to link too. In older versions it was Fat32, Ext2/3 and the Swap.
When you installed Link2Sd, and it checked for partitions, did it throw any errors? Does your ROM support Link2SD? I'll look around at it some more but A.cid asked for some help.

Thank you both guys for replying in such a kind way: i appreciate!
I am running this MOD: LiquidNext (latest version 1.9.2)
forum thread about the rom here
It seems to be possible to run link2SD on the above ROM.
Other apps crash as well, but I honestly can't recall whether they were system apps or not.
I have now resetted everything:
I have wiped everything, both internal and external memories (8GB SDcard).
I have formatted the sd card from the CWM Recovery (touch): EXT3 1024 MB, Swap: 0 MB, FAT32 remaining space.
I have flashed the same rom again, and haven't yet installed link2sd and Titanium.
so far everything is running smoothly, but I want to understand what's wrong when I install link2sd!
I have been running it smoothly in the past on the same ROM => then something mysterious happened
hope you guys are better than me and can find the culprit !!

Corrupt partition. Removing the link2sd script from init.d will be a temporary fix. You need to reformat your ext partition!
___________XDA Premium__________
Don't be a noob. Be a newbie..!!
Details here.
____________________________________

shaaan said:
Corrupt partition. Removing the link2sd script from init.d will be a temporary fix. You need to reformat your ext partition!
Click to expand...
Click to collapse
already done !!
thanks though

Hey, I know that this isn't your device but there may be somethings in this trhead that will help you troubleshoot, like kernel modules and proper partition setup. This was my first Android device so you might see a post or two in there from me way back when.
[GUIDE] Link2SD on milestone XT 720

Woodrube said:
Hey, I know that this isn't your device but there may be somethings in this trhead that will help you troubleshoot, like kernel modules and proper partition setup. This was my first Android device so you might see a post or two in there from me way back when.
[GUIDE] Link2SD on milestone XT 720
Click to expand...
Click to collapse
Thank you but that was not of much help !!
I still haven't managed to get Link2SD to work correctly!!
help me please

[Q] Installing AOSP ICS launcher

Hi,
I'm trying to modify the AOSP ICS launcher. I've downloaded the ICS source tree and built Launcher2 as is. However, when I try to install it in an Android device(a stock Samsung Galaxy S3 running stock ICS, and a HTC Desire Z running Andromadus mimicry 1.5.0 based on ICS) using "adb install", I get a INSTALL_FAILED_DEXOPT installation error. Logcat output from the Galaxy S3 is as follows:
Code:
D/AndroidRuntime( 5431):
D/AndroidRuntime( 5431): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
D/AndroidRuntime( 5431): CheckJNI is OFF
D/AndroidRuntime( 5431): setted country_code = France
D/AndroidRuntime( 5431): setted countryiso_code = FR
D/AndroidRuntime( 5431): setted sales_code = XEF
D/AndroidRuntime( 5431): readGMSProperty: start
D/AndroidRuntime( 5431): readGMSProperty: already setted!!
D/AndroidRuntime( 5431): readGMSProperty: end
D/LibQmg_native( 5431): register_android_app_LibQmg
D/AndroidRuntime( 5431): Calling main entry com.android.commands.pm.Pm
W/PackageManager( 2093): verifying app can be installed or not
I/ApplicationPolicy( 2093): isApplicationInstallationEnabled
D/dalvikvm( 2093): GC_CONCURRENT freed 7885K, 31% free 32346K/46791K, paused 2ms+6ms
D/dalvikvm( 2093): GC_CONCURRENT freed 1834K, 31% free 32555K/46791K, paused 3ms+5ms
E/PackageManager( 2093): Package XXX.XXXXXXX.XXXXXXXX has mismatched uid: 10130 on disk, 10131 in settings
I/PackageManager( 2093): Running dexopt on: XXX.XXXXXXX.XXXXXXXX
I/PackageManager( 2093): Linking native library dir for |XXXX|XXX|XXXXXXXXXXXXXXXXXXXXXX.XXX
W/dalvikvm( 5442): DexOptZ: zip archive '/data/app/com.android.launcher-1.apk' does not include classes.dex
W/installd( 1907): DexInv: --- END '/data/app/com.android.launcher-1.apk' --- status=0xff00, process failed
E/installd( 1907): dexopt failed on '/data/dalvik-cache/[email protected]@[email protected]' res = 65280
W/PackageManager( 2093): Package couldn't be installed in /data/app/com.android.launcher-1.apk
Does anyone know how to build and install the AOSP launcher on non Nexus devices?
Thanks.

It looks like the apk you built was deodexed but was missing a classes.dex file. And when the installer tried to create an odex file it couldn't because the apk didn't contain instructions on how to.
That's my interpretation of the log for you, although I can't answer you question. Sorry.

Wouldn't this be better in q&a section? Also regarding the launcher I'm pretty sure you can just install the unmodified apk as is by enabling install from unknown sources and placing the apk on your memory card, or just use one of the plethora of stock based home launchers like apex, trebuchet, nova, adw or holo launcher just to name a few.
Sent from my LT30p using xda app-developers app

razz, there's actually a .apk file and a .odex file in the out directory after I build the app. Is the .odex file what it's trying to look for? Is there any way I can include it in the apk, or direct the installer to its location so that it doesn't throw the error? I'm guessing the apk is currently odexed since there's an .odex file, and I need to deodex it? If so, how can I do this?
Galcactus, I'm trying to modify the stock AOSP launcher, hence getting it to install on an Android device unmodified is my first step.
I thought I could install it as is as well, however I keep getting this error. I've tried pushing the apk to my memory card and using a file manager/app installer app to install it but no go as well.

Anyone? Thanks.

[Q] Help needed rooting my Nexus S

Hi,
I want to install Cyanogenmod on my Nexus S. To do this my bootloader needs to be unlocked which wipes the phone. Before I do that, I want to make a backup. For some apps I need root to do a proper backup and there's my problem. I followed half a dozen guides, but they either A) wipe the phone or B) somehow don't work for me. So now I hope you can help me.
My Phone: Nexus S (crespo, I9023XXKI1) with stock Android (4.1.2), no root (obviously)
What I've tried so far:
- Downloaded android-sdk (platform tools and usb drivers)
- Installed USB drivers
- "adb backup -f ... -apk ..." works fine for some apps, but for others the backup is incomplete
- "fastboot devices" works and lists my device
- "fastboot flash recovery ..." doesn't work (says it needs an unlocked bootloader)
- "fastboot oem unlock" will wipe the phone
What can I do to get root and make a proper backup before wiping my phone?
Heres a log of my last try:
Code:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. Alle Rechte vorbehalten.
c:\Users\Sebastian\AppData\Local\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
373......0EC device
c:\Users\Sebastian\AppData\Local\Android\android-sdk\platform-tools>adb reboot bootloader
c:\Users\Sebastian\AppData\Local\Android\android-sdk\platform-tools>fastboot devices
373......0EC fastboot
c:\Users\Sebastian\AppData\Local\Android\android-sdk\platform-tools>fastboot flash recovery recovery-clockwork-6.0.4.3-crespo.img
sending 'recovery' (5388 KB)...
OKAY [ 0.687s]
writing 'recovery'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.716s
c:\Users\Sebastian\AppData\Local\Android\android-sdk\platform-tools>fastboot oem unlock
... // Here I said "no" on the phone
OKAY [ 20.560s]
finished. total time: 20.564s
c:\Users\Sebastian\AppData\Local\Android\android-sdk\platform-tools>

Hyperbo said:
Hi,
I want to install Cyanogenmod on my Nexus S. To do this my bootloader needs to be unlocked which wipes the phone. Before I do that, I want to make a backup. For some apps I need root to do a proper backup and there's my problem. I followed half a dozen guides, but they either A) wipe the phone or B) somehow don't work for me. So now I hope you can help me.
My Phone: Nexus S (crespo, I9023XXKI1) with stock Android (4.1.2), no root (obviously)
What I've tried so far:
- Downloaded android-sdk (platform tools and usb drivers)
- Installed USB drivers
- "adb backup -f ... -apk ..." works fine for some apps, but for others the backup is incomplete
- "fastboot devices" works and lists my device
- "fastboot flash recovery ..." doesn't work (says it needs an unlocked bootloader)
- "fastboot oem unlock" will wipe the phone
What can I do to get root and make a proper backup before wiping my phone?
Heres a log of my last try:
Code:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. Alle Rechte vorbehalten.
c:\Users\Sebastian\AppData\Local\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
373......0EC device
c:\Users\Sebastian\AppData\Local\Android\android-sdk\platform-tools>adb reboot bootloader
c:\Users\Sebastian\AppData\Local\Android\android-sdk\platform-tools>fastboot devices
373......0EC fastboot
c:\Users\Sebastian\AppData\Local\Android\android-sdk\platform-tools>fastboot flash recovery recovery-clockwork-6.0.4.3-crespo.img
sending 'recovery' (5388 KB)...
OKAY [ 0.687s]
writing 'recovery'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.716s
c:\Users\Sebastian\AppData\Local\Android\android-sdk\platform-tools>fastboot oem unlock
... // Here I said "no" on the phone
OKAY [ 20.560s]
finished. total time: 20.564s
c:\Users\Sebastian\AppData\Local\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
Backing up contacts, pictures and other personal data can be done without root using just a simple file manager or mounting your device to your computer, but app data is another story, you are 99% guaranteed to lose it, minus apps like launchers that will make a backup file on the SD card.. I have searched myself for a good resolution, but there hasn't been one yet..

That's what I feared. Even Helium (formerly Carbon) from the ClockworkMod Team doesn't work. When I try to backup any apps it just says: "An error occured while perfoming your app backup. A log of the error has been sent to ClockworkMod. Click Backup to attempt to backup the remaining apps." However, the backup of (only) SMS works fine with Helium.
Is there anything else I could try?

Hyperbo said:
That's what I feared. Even Helium (formerly Carbon) from the ClockworkMod Team doesn't work. When I try to backup any apps it just says: "An error occured while perfoming your app backup. A log of the error has been sent to ClockworkMod. Click Backup to attempt to backup the remaining apps." However, the backup of (only) SMS works fine with Helium.
Is there anything else I could try?
Click to expand...
Click to collapse
As far as I know, Helium can backup app data without root. I wonder why it doesn't work. Can you share the log file if you have?

I was on a business trip and could try it just today. I didn't find a helium log file, so I looked at the link in your signature. I used the adb logcat variant. Here are my results:
Helium Version: 1.1.2.1 (not premium)
After starting the adb log on the console I backuped the SMS and it worked as expected. Then I tried an app for which the backup failed in the past (gnucash), but strangely it went through. I tried it again and it failed. I tried other apps, but couldn't reproduce the success. I chose the gnucash app because with the normal "adb backup -f ..." call it works just fine, so helium shouldn't have any problems.
Here is the log of one of the tries. First the successful SMS backup then the failed gnucash backup:
Code:
I/Carbon (14917): startBackup invoked: file
I/Carbon (14917): com.android.providers.telephony
D/PhoneStatusBar( 354): addNotification score=0
I/Carbon (14917): Releasing locks.
I/Carbon (14917): Acquiring full lock.
I/CarbonNonce(14917): Nonce: 9352e3b8-6553-4b27-a014-96283d88a017
I/Carbon (14917): bu 1 backup
D/SizeAdaptiveLayout( 354): [email protected] view [email protected] measured out of bounds at 95px clamped to 96px
D/dalvikvm(14917): GC_FOR_ALLOC freed 963K, 13% free 13649K/15559K, paused 157ms, total 161ms
I/Carbon (14917): Demux atomic: false
D/dalvikvm(14917): GC_FOR_ALLOC freed 806K, 15% free 13363K/15559K, paused 68ms, total 69ms
I/Carbon (14917): Writing package: com.android.providers.telephony
I/CarbonBackup(14917): Package: com.android.providers.telephony
D/SizeAdaptiveLayout( 354): [email protected] view [email protected] measured out of bounds at 95px clamped to 96px
D/dalvikvm(14917): GC_CONCURRENT freed 1606K, 13% free 13544K/15559K, paused 22ms+12ms, total 115ms
D/dalvikvm(14917): WAIT_FOR_CONCURRENT_GC blocked 44ms
D/dalvikvm(14917): GC_CONCURRENT freed 1849K, 13% free 13544K/15559K, paused 21ms+7ms, total 93ms
D/dalvikvm(14917): WAIT_FOR_CONCURRENT_GC blocked 30ms
D/dalvikvm(14917): GC_CONCURRENT freed 1848K, 13% free 13543K/15559K, paused 20ms+8ms, total 101ms
D/dalvikvm(14917): WAIT_FOR_CONCURRENT_GC blocked 43ms
D/dalvikvm(14917): GC_CONCURRENT freed 1847K, 13% free 13543K/15559K, paused 18ms+10ms, total 109ms
D/dalvikvm(14917): WAIT_FOR_CONCURRENT_GC blocked 55ms
D/dalvikvm(16484): GC_CONCURRENT freed 445K, 6% free 9865K/10439K, paused 12ms+3ms, total 1067ms
I/ActivityManager( 247): Start proc android.process.acore for content provider com.android.providers.contacts/.CallLogProvider: pid=16516 uid=10007 gids={3003, 1015, 1028}
I/ActivityThread(16516): Pub call_log: com.android.providers.contacts.CallLogProvider
I/ActivityThread(16516): Pub com.android.voicemail: com.android.providers.contacts.VoicemailContentProvider
I/ActivityThread(16516): Pub user_dictionary: com.android.providers.userdictionary.UserDictionaryProvider
I/ActivityManager( 247): Process com.android.backupconfirm (pid 16090) has died.
I/ActivityThread(16516): Pub applications: com.android.providers.applications.ApplicationsProvider
I/ActivityThread(16516): Pub contacts;com.android.contacts: com.android.providers.contacts.ContactsProvider2
D/dalvikvm(16516): GC_CONCURRENT freed 233K, 5% free 8230K/8583K, paused 82ms+15ms, total 135ms
D/dalvikvm(14917): GC_CONCURRENT freed 1831K, 13% free 13561K/15559K, paused 15ms+5ms, total 101ms
D/dalvikvm(14917): WAIT_FOR_CONCURRENT_GC blocked 36ms
D/dalvikvm(14917): GC_FOR_ALLOC freed 390K, 14% free 13501K/15559K, paused 53ms, total 54ms
D/dalvikvm(14917): GC_FOR_ALLOC freed 2K, 12% free 13755K/15559K, paused 42ms, total 42ms
I/CarbonParser(14917): Finished demuxing com.android.providers.telephony
I/Carbon (14917): Completed: com.android.providers.telephony
I/Carbon (14917): Releasing locks.
I/Carbon (14917): Stopping.
W/InputMethodManagerService( 247): Window already focused, ignoring focus gain of: [email protected] [email protected]
D/dalvikvm(16516): GC_CONCURRENT freed 51K, 3% free 8593K/8775K, paused 45ms+5ms, total 130ms
D/dalvikvm(16484): GC_CONCURRENT freed 361K, 5% free 10040K/10503K, paused 39ms+49ms, total 566ms
D/dalvikvm(14917): GC_FOR_ALLOC freed 769K, 13% free 13796K/15751K, paused 162ms, total 164ms
I/ExternalStorage(14917): main: /storage/sdcard0
I/ExternalStorage(14917): other main: /storage/sdcard0
I/ExternalStorage(14917): Vol: /storage/sdcard0
I/ExternalStorage(14917): vols in list: 0
I/ActivityManager( 247): Process com.google.android.apps.plus (pid 16214) has died.
D/dalvikvm(16484): GC_CONCURRENT freed 492K, 6% free 10152K/10759K, paused 43ms+15ms, total 152ms
I/Carbon (14917): startBackup invoked: file
I/Carbon (14917): org.gnucash.android
D/PhoneStatusBar( 354): addNotification score=0
I/Carbon (14917): Releasing locks.
I/Carbon (14917): Acquiring full lock.
I/CarbonNonce(14917): Nonce: 36bea2ce-0ba5-4f0e-88d2-650fea91196b
I/Carbon (14917): bu 1 backup org.gnucash.android
W/System.err(14917): java.io.IOException: Connection refused
D/SizeAdaptiveLayout( 354): [email protected] view [email protected] measured out of bounds at 95px clamped to 96px
W/System.err(14917): at android.net.LocalSocketImpl.connectLocal(Native Method)
W/System.err(14917): at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
W/System.err(14917): at android.net.LocalSocket.connect(LocalSocket.java:98)
W/System.err(14917): at com.koushikdutta.shellproxy.ShellProcess2.<init>(ShellProcess2.java:124)
W/System.err(14917): at com.koushikdutta.shellproxy.ShellProcess2.exec(ShellProcess2.java:30)
W/System.err(14917): at com.koushikdutta.backup.BackupServiceHelper$11.onContinue(BackupServiceHelper.java:735)
W/System.err(14917): at com.koushikdutta.async.future.Continuation.next(Continuation.java:119)
W/System.err(14917): at com.koushikdutta.async.future.Continuation.start(Continuation.java:154)
W/System.err(14917): at com.koushikdutta.backup.BackupRestoreService$1$4.run(BackupRestoreService.java:246)
I/Carbon (14917): Releasing locks.
I/Carbon (14917): Stopping.
I/System.out(14917): Connection refused
E/ActivityThread(14917): Service com.koushikdutta.backup.BackupRestoreService has leaked ServiceConnection [email protected] that was originally bound here
E/ActivityThread(14917): android.app.ServiceConnectionLeaked: Service com.koushikdutta.backup.BackupRestoreService has leaked ServiceConnection [email protected] that was originally bound here
E/ActivityThread(14917): at android.app.LoadedApk$ServiceDispatcher.<init>(LoadedApk.java:965)
E/ActivityThread(14917): at android.app.LoadedApk.getServiceDispatcher(LoadedApk.java:859)
E/ActivityThread(14917): at android.app.ContextImpl.bindService(ContextImpl.java:1191)
E/ActivityThread(14917): at android.app.ContextImpl.bindService(ContextImpl.java:1183)
E/ActivityThread(14917): at android.content.ContextWrapper.bindService(ContextWrapper.java:394)
E/ActivityThread(14917): at android.media.MediaScannerConnection.connect(MediaScannerConnection.java:116)
E/ActivityThread(14917): at com.koushikdutta.backup.data.FileBackupPackage.<init>(FileBackupPackage.java:34)
E/ActivityThread(14917): at com.koushikdutta.backup.BackupRestoreService$1.startBackup(BackupRestoreService.java:128)
E/ActivityThread(14917): at com.koushikdutta.backup.BackupFragment$11.onServiceConnected(BackupFragment.java:340)
E/ActivityThread(14917): at android.app.LoadedApk$ServiceDispatcher.doConnected(LoadedApk.java:1097)
E/ActivityThread(14917): at android.app.LoadedApk$ServiceDispatcher$RunConnection.run(LoadedApk.java:1114)
E/ActivityThread(14917): at android.os.Handler.handleCallback(Handler.java:615)
E/ActivityThread(14917): at android.os.Handler.dispatchMessage(Handler.java:92)
E/ActivityThread(14917): at android.os.Looper.loop(Looper.java:137)
E/ActivityThread(14917): at android.app.ActivityThread.main(ActivityThread.java:4745)
E/ActivityThread(14917): at java.lang.reflect.Method.invokeNative(Native Method)
E/ActivityThread(14917): at java.lang.reflect.Method.invoke(Method.java:511)
E/ActivityThread(14917): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
E/ActivityThread(14917): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
E/ActivityThread(14917): at dalvik.system.NativeStart.main(Native Method)
D/dalvikvm(16484): GC_CONCURRENT freed 554K, 7% free 10213K/10887K, paused 22ms+16ms, total 128ms
I/Ads (14917): Ad is not visible. Not refreshing ad.
I/Ads (14917): Scheduling ad refresh 60000 milliseconds from now.
W/InputMethodManagerService( 247): Window already focused, ignoring focus gain of: [email protected] attribute=null
D/dalvikvm( 247): GC_CONCURRENT freed 1764K, 18% free 22183K/26887K, paused 17ms+12ms, total 234ms

Does the log help anyone figuring out whats wrong with my phone?

Hyperbo said:
Does the log help anyone figuring out whats wrong with my phone?
Click to expand...
Click to collapse
Sorry, I didn't get time to reply back. I saw the log and couldn't find much. I'll look at it carefully and get back to you in a day or two.

dont worry bro
here are instructions on how to unlock your Google Nexus S with fast boot and the standard recovery mode.
1.Turn off the phone completely.
2.Now hold down the volume up and power button.
3.You should have now entered Standard Recovery Mode.
4.Connect your phone to your PC/Mac via USB
5.Open command prompt (CMD on Windows) or Terminal (For Mac OSX)
6.Enter ¡®fastboot devices¡¯ without quotes to check whether your phone is connected via USB
7.Type ¡®adb reboot bootloader¡¯
8.Type ¡®fastboot oem unlock¡¯
9.Use volume keys to select ¡®yes, unlock bootloader¡¯
10.Use power button to select option
11.Your new bootloader is unlocked.
NOTE: This unlock performs a factory reset on your Android phone.
You can backup all your data using Go backup app or some other 3rd party app.
For more info you can visit Nexus s Hacks .com

Thanks for your reply. I've already tried what you sugested (see my first post). Step 8 is the problem because it wipes the phone (as you have written). To solve this you suggested the app Go Backup. In the german version of the play store it says that in order to backup your application data, it needs root. This sends me back to square one
Nevertheless I've tried the app. It displays a warning when it starts, that my phone is unrooted. After the backup process it says that it could only backup the app, but not the data, which doesn't help me when doing a factory reset.
Raakib zargar said:
here are instructions on how to unlock your Google Nexus S with fast boot and the standard recovery mode.
1.Turn off the phone completely.
2.Now hold down the volume up and power button.
3.You should have now entered Standard Recovery Mode.
4.Connect your phone to your PC/Mac via USB
5.Open command prompt (CMD on Windows) or Terminal (For Mac OSX)
6.Enter ¡®fastboot devices¡¯ without quotes to check whether your phone is connected via USB
7.Type ¡®adb reboot bootloader¡¯
8.Type ¡®fastboot oem unlock¡¯
9.Use volume keys to select ¡®yes, unlock bootloader¡¯
10.Use power button to select option
11.Your new bootloader is unlocked.
NOTE: This unlock performs a factory reset on your Android phone.
You can backup all your data using Go backup app or some other 3rd party app.
For more info you can visit Nexus s Hacks .com
Click to expand...
Click to collapse

Hyperbo said:
Thanks for your reply. I've already tried what you sugested (see my first post). Step 8 is the problem because it wipes the phone (as you have written). To solve this you suggested the app Go Backup. In the german version of the play store it says that in order to backup your application data, it needs root. This sends me back to square one
Nevertheless I've tried the app. It displays a warning when it starts, that my phone is unrooted. After the backup process it says that it could only backup the app, but not the data, which doesn't help me when doing a factory reset.
Click to expand...
Click to collapse
K Then You will need a pc for this:
*Download MoboRobo for pc
*Connect your device using usb cable and debugging on and backup anything you want even contacts and text messages i,e SMSs.....GoodLuck
---------- Post added at 08:08 AM ---------- Previous post was at 07:52 AM ----------
Hyperbo said:
Thanks for your reply. I've already tried what you sugested (see my first post). Step 8 is the problem because it wipes the phone (as you have written). To solve this you suggested the app Go Backup. In the german version of the play store it says that in order to backup your application data, it needs root. This sends me back to square one
Nevertheless I've tried the app. It displays a warning when it starts, that my phone is unrooted. After the backup process it says that it could only backup the app, but not the data, which doesn't help me when doing a factory reset.
Click to expand...
Click to collapse
K Then You will need a pc for this:
*Download MoboRobo for pc
*Connect your device using usb cable and debugging on and backup anything you want even contacts and text messages i,e SMSs.....GoodLuck

I ended up wiping my phone and losing the app data that couldn't be backed up. It wasn't worth all the hassle.
Thread can be closed.
Raakib zargar said:
K Then You will need a pc for this:
*Download MoboRobo for pc
*Connect your device using usb cable and debugging on and backup anything you want even contacts and text messages i,e SMSs.....GoodLuck
---------- Post added at 08:08 AM ---------- Previous post was at 07:52 AM ----------
K Then You will need a pc for this:
*Download MoboRobo for pc
*Connect your device using usb cable and debugging on and backup anything you want even contacts and text messages i,e SMSs.....GoodLuck
Click to expand...
Click to collapse