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

Help restore hangs in Android logo screen

S

shanyel

Newbie
I did restore from lastest nandroid backup and now the galaxy won't turn on. it stuck in the logo screen (android) all the time - like in loops.
Is there any connection to the fact that I did ODIN to II5 before and the backup is from older build?
can someone help?
 
shanyel said:
I did restore from lastest nandroid backup and now the galaxy won't turn on. it stuck in the logo screen (android) all the time - like in loops.
Is there any connection to the fact that I did ODIN to II5 before and the backup is from older build?
can someone help?
Click to expand...
yes its likely to be that, you are restoring an image of an earlier version over the top of a new one.

if i was you i would flash ii5 back with odin but wipe from recovery first
 
Odin flash works fine.
I flashed with Odin - the phone finished, restarted and went up.
after that i did fastboot and install the recovery img.
Once done i did recover latest nandroid backup

the restore completed OK - but when the OS was up i got a lot of "force close" messages....
 
shanyel said:
Odin flash works fine.
I flashed with Odin - the phone finished, restarted and went up.
after that i did fastboot and install the recovery img.
Once done i did recover latest nandroid backup

the restore completed OK - but when the OS was up i got a lot of "force close" messages....
Click to expand...
as stated the nandroid backup is from an earlier version of os there for it will break.
what is the reason for restoring it?
 
getting back pre-installed apps by my operator. I had moxier (exchange email) pre-installed. now after upgrading to II5 i lost the app....
 
Odin to the old firmware, restore, then copy the apk off and keep it on you sdcard.

Then with whatever new firmware you use, just install astro file manager, browse to it and install it.
 
understood that already - my problem is quiet simple - don't have the prev build...
my carrier is Orange IL
I was counting on nandroid to back me up - seems some gaps are here when involving different builds
 
Do you remember what firmware version it was? What i mean is the CSC is not important. Just the last 2 letters i.e. G8, H2, H4, H7, H8, I4, I5

Alternatively you can find the backup on your sd card and extract the image.

Mount your internal sd card and go to the backup. It will be in here:

\nandroid\mem=109M\CBDMRS12-<date>-<time>

copy the system.img to the root of your sdcard to make it easier. Now boot into recovery (because it has unyaffs command).

type:

cd /sdcard
mkdir temp
cd temp
unyaffs /sdcard/system.img

Now you can mount the internal SD in recovery, and browse /sdcard/temp for the apk's you need. Copy them onto the root of your sdcard for safe keeping, and you can delete /sdcard/temp if you feel like it.
 
You need the custom recovery, and to boot into it. Then adb shell into that. I use the 4.1 or 4.2 recovery from hdblog.it

Standard firmware won't have unyaffs.
 
Now seems I got a new issue. seems the APK I'm trying to install is workable only on specific Model number (looking for sting 'Galaxy'). Anyway to change the Model number string to something it will work out?
many thanks again!!
 
Its probably looking in the build.prop.

adb pull /system/buildprop build.prop

That will grab the file into the adb directory on your PC. Have a look at it and compare it with the one from your backup (it should be
in /sdcard/temp/system/build.prop) if you didnt delete the unyaffs extracted folder :)

You can edit the build.prop on your PC (be carefull not mess up the CR/LF's - i use ultraedit to do it). Then boot to recovery. Type

adb remount
adb pull build.prop /system/buildprop

Also if you want to check what your old firmware/CSC was you can check in CSCVersion.txt in your extracted backup. So /temp/system/CSCVersion.txt on your sdcard
 
You must log in or register to reply here.
Back
Top Bottom