Ok so i backed up my tf using cwm and everything worked perfectly. When i try restoring the back up it first restores the system apps but then there is an error saying the is no .androidsecure file. And my tf wont boot up after. I then have to flash an old tf version for it start working again.
If anyone has a solution that would be great
mafo5000 said:
Ok so i backed up my tf using cwm and everything worked perfectly. When i try restoring the back up it first restores the system apps but then there is an error saying the is no .androidsecure file. And my tf wont boot up after. I then have to flash an old tf version for it start working again.
If anyone has a solution that would be great
Click to expand...
Click to collapse
It might not have anything to do with the 'error' which is maybe not an error, just an informational message from the "Froyo" days. This is all guesswork, but I seem to recall that .android_secure was for apps that were movable and moved to the sdcard. That just doesn't really make sense on the TF101 using Honeycomb, so if you don't have that folder (.android_secure), that that's cool.
Does the restore complete entirely aside from the message about .and* ?
Another thing I wonder about with cwm restores is the kernel. Did you have a working kernel in your tf101 before you got started with this restore? I'm not really seeing how it restores the kernel (boot.img/zImage/whatever) in this version of cwm. All I see saved is system.img, the md5sum, data.img and cache.img. My guess is that you might benefit by picking a kernel, like either the latest stock one or say, Prime's kernel, and burning that in afterward, clearing dalvik and rebooting again.
Note: It might be that everything needed is somehow in system.img and that cwm has the smarts to burn what it needs to the right places, but in every other version of cwm I've seen, there is a boot.img file in the cwm backup that contains the kernel.
If anyone knows how cwm is burning a blob for the kernel, I'd be curious to know how since I'm not looking at the code. Thanks.
Good luck
the restore doesnt completely restore.
It goes something like this....
System apps restore
I think another restore
Then the error
Restore cache
And then its done. It boots me up to an Asus image and wont go past.
These are the files in my cwm restore
Cache.img
Data.img
Nandroid.md5
System.img
Also i have stock kernel
mafo5000 said:
the restore doesnt completely restore.
It goes something like this....
System apps restore
I think another restore
Then the error
Restore cache
And then its done. It boots me up to an Asus image and wont go past.
These are the files in my cwm restore
Cache.img
Data.img
Nandroid.md5
System.img
Also i have stock kernel
Click to expand...
Click to collapse
So it sounds like the restore is completing with the message about the secure folder then dropping dead during the kernel load. If I understand you right, it sounds like you "had" a stock kernel when it was working, but I wonder if you've got any viable kernel right now?
Since your tf101 isn't working and is basically useless, you could try to boot back to cwm and burn some known working current kernel in there. I don't have the links right now to the stock one, but you could try a nearly stock one from the Prime ROM http://roach.qap.la/Roms/Prime_v2.0/OCKernel_Prime_v2.0.6.zip .
I don't know what his zip file looks like but at least it'll force the issue of burning a blob into the boot partition and you can tell if the kernel was the problem.
If that doesn't work, then your backup was possibly corrupted and I don't have a good answer other than to install either a stock image or one of the ROMs people use like Prime or Revolution and see how they do.
I'm also guessing that blowing a new image on there is a last resort because you had stuff setup the way you wanted it, but it's for you to decide that. You could search the forums for something that does some sort of integrity check on the cwm backups, or better yet, get in touch with Solarnz or Daoist via messages and ask their advice. They're experts here in cwm and I'm not.
hachamacha said:
So it sounds like the restore is completing with the message about the secure folder then dropping dead during the kernel load. If I understand you right, it sounds like you "had" a stock kernel when it was working, but I wonder if you've got any viable kernel right now?
Since your tf101 isn't working and is basically useless, you could try to boot back to cwm and burn some known working current kernel in there. I don't have the links right now to the stock one, but you could try a nearly stock one from the Prime ROM http://roach.qap.la/Roms/Prime_v2.0/OCKernel_Prime_v2.0.6.zip .
I don't know what his zip file looks like but at least it'll force the issue of burning a blob into the boot partition and you can tell if the kernel was the problem.
If that doesn't work, then your backup was possibly corrupted and I don't have a good answer other than to install either a stock image or one of the ROMs people use like Prime or Revolution and see how they do.
I'm also guessing that blowing a new image on there is a last resort because you had stuff setup the way you wanted it, but it's for you to decide that. You could search the forums for something that does some sort of integrity check on the cwm backups, or better yet, get in touch with Solarnz or Daoist via messages and ask their advice. They're experts here in cwm and I'm not.
Click to expand...
Click to collapse
I flashed another kernel but I still get the error when trying to restore. I've been searching around and I guess I'm missing the .android_secure file in the data.img. I just dont know how to fix it.
Btw my tf is usable and all I am just not able to restore all my apps and such. So its basically like new..
mafo5000 said:
Btw my tf is usable and all I am just not able to restore all my apps and such. So its basically like new..
Click to expand...
Click to collapse
Couldn't you extract data.img and then make a CWM zip out of that?
Sent from my X10a using The Force
AyDee said:
Couldn't you extract data.img and then make a CWM zip out of that?
Sent from my X10a using The Force
Click to expand...
Click to collapse
I dont know if that would work because, i think, the error is in the data.img.
I could try that though, how would i change it to a cwm zip?
Google "extract data.img android" and "make cwm zip" or search here.
AyDee said:
Google "extract data.img android" and "make cwm zip" or search here.
Click to expand...
Click to collapse
I found this app called app extractor and it can extract apps from old nandroid backups. It works when trying to restore the system apps but when i try to restore user apps it is unable to. If been searching around on how to extract the data.img and what ive found is that i need to use something call unyaffs. If you can point me in a way of a great tutorial that would be great because i can not find one...
Related
So, I just did a backup of my Glorious Overdose setup using the voodoo recovery it comes with and I got MD5 errors while trying to restore...
Anyone else have this issue?
I never restored from a cwm successfully, I think its not fully functional. Red nor orange... luckily I saved my apps & settings using mybackup
I have also had this problem. if anyone knows why, please let us know. I was able to restore data, but a couple funny things happened. when restoring, i get error restoring boot image or md5 sum mismatch. when restoring data, my phone stuck at restoring android_secure. i pulled the battery and rebooted. luckily that didnt brick my phone.
fiveseven808, did you flash cwm through rom manager? if so, i think that might be the problem. i flashed through rom manager and was having problems backing up/restoring. i went to this thread: forum.xda-developers.com/showthread.php?t=1124453 and downloaded the update.zip file in the first post, saved in my download folder. i then went to the root of my sd card and deleted the update.zip file that was there. i moved the other update.zip from my download folder to the root of my sd card. rebooted into cwm and took a backup no problem.
sidekick_fanatic said:
fiveseven808, did you flash cwm through rom manager? if so, i think that might be the problem. i flashed through rom manager and was having problems backing up/restoring. i went to this thread: forum.xda-developers.com/showthread.php?t=1124453 and downloaded the update.zip file in the first post, saved in my download folder. i then went to the root of my sd card and deleted the update.zip file that was there. i moved the other update.zip from my download folder to the root of my sd card. rebooted into cwm and took a backup no problem.
Click to expand...
Click to collapse
I did! But I was unable to use it... or something really strange happened..
Before Glorious Overdose, I could boot into CWM 3 using the recovery boot method. After Glorious Overdose, I realized I could boot into CWM Voodoo with the three button method getting around the stock recovery, and boot into a VERY broken CWM 4 via ROM manager.
Will your advice fix whatever I did wrong?
I have no idea, but you could try it and see. if it doesnt, your no worse off than you were to start with.
Update: I now know for sure that having the right update.zip file will fix the issue. I had to restore my phone today due to issues caused by unknown sources. I tried to fix the issues before doing a restore, but no luck. so I booted into cwm and hit restore. it worked without a single hitch. So the problem (for me at least) was definitely having the wrong update.zip file.
I have never had this issue, with VooDoo or regular CWM... Bad update.zip sounds like it would be the problem, as you said
i believe the issue is in the update.zip file. when flashing cwm through rom manager, i was unable to properly backup and restore. after switching the update.zip with the one found in the dev thread, i can backup and restore to my hearts content. i am very glad to have fully functional cwm on this device, as i had it on my last phone, the tmobile comet. the comet was my first android device. i was not entirely happy with it, but it gave me enough of a taste of android to figure out i wasnt going back to blackberry. prior to android, the best phone i had ever owned was a blackberry pearl. now, the sk4g is the best phone i have ever had, even better than the blackberry pearl. for me, this keyboard has no parallel, and the setup and ui is nowhere near as tough to get used to as people had been saying it was on the forums. but i digress. cwm is the best alternative to the stock recovery, and its good to have it working on this phone.
Hi everyone! I aware that maybe this is a stupid question, but i have to ask...Is there a way to convert a CWM backup to a flash zip to use with the CWM install zip option??? I'm asking this because I have a particular problem and is that I can't do backups or restore with my CWM so i can't install almost any custom rom that is in the developers forum.
I don't know why i have this problem, even I posted a thread asking for help about this, but I guess I'm the only one experiencing this issue and the only rom I successfully installed is the Victory Rom and is a flashing zip.
By the way I installed the CWM with the Atrix Bootstrap and I applied the patch RAZR-CWMOnBoot-Global-J.Y.Daddy.zip to have the CWM on every boot and I don't experience any GPS issue (I guess i don't know exactly what is the issue) and for the record when I'm trying to do a CWM backup i get the "check sum error" when the CWM tried to finish the backup process, and when i'm attemping to restore a backup the CWM starts without problem but then I get the "Error while restoring /system".
I hope you can helpme with this problem.
Thank's in advanced.
jfrank1485 said:
Hi everyone! I aware that maybe this is a stupid question, but i have to ask...Is there a way to convert a CWM backup to a flash zip to use with the CWM install zip option??? I'm asking this because I have a particular problem and is that I can't do backups or restore with my CWM so i can't install almost any custom rom that is in the developers forum.
I don't know why i have this problem, even I posted a thread asking for help about this, but I guess I'm the only one experiencing this issue and the only rom I successfully installed is the Victory Rom and is a flashing zip.
By the way I installed the CWM with the Atrix Bootstrap and I applied the patch RAZR-CWMOnBoot-Global-J.Y.Daddy.zip to have the CWM on every boot and I don't experience any GPS issue (I guess i don't know exactly what is the issue) and for the record when I'm trying to do a CWM backup i get the "check sum error" when the CWM tried to finish the backup process, and when i'm attemping to restore a backup the CWM starts without problem but then I get the "Error while restoring /system".
I hope you can helpme with this problem.
Thank's in advanced.
Click to expand...
Click to collapse
after you apply the atrix bootstrap use rom manager and install the recovery for the droid bionic and you will be able to back up and restore roms. advance restore also works incase you do a wipe, install a rom, and then want your data restored.
jfrank1485 said:
Hi everyone! I aware that maybe this is a stupid question, but i have to ask...Is there a way to convert a CWM backup to a flash zip to use with the CWM install zip option??? I'm asking this because I have a particular problem and is that I can't do backups or restore with my CWM so i can't install almost any custom rom that is in the developers forum.
I don't know why i have this problem, even I posted a thread asking for help about this, but I guess I'm the only one experiencing this issue and the only rom I successfully installed is the Victory Rom and is a flashing zip.
By the way I installed the CWM with the Atrix Bootstrap and I applied the patch RAZR-CWMOnBoot-Global-J.Y.Daddy.zip to have the CWM on every boot and I don't experience any GPS issue (I guess i don't know exactly what is the issue) and for the record when I'm trying to do a CWM backup i get the "check sum error" when the CWM tried to finish the backup process, and when i'm attemping to restore a backup the CWM starts without problem but then I get the "Error while restoring /system".
I hope you can helpme with this problem.
Thank's in advanced.
Click to expand...
Click to collapse
You could convert it... but you would have to write an updater-script, and get an updater-binary (you can basically steal it from any flashable zip.)
rob219 said:
after you apply the atrix bootstrap use rom manager and install the recovery for the droid bionic and you will be able to back up and restore roms. advance restore also works incase you do a wipe, install a rom, and then want your data restored.
Click to expand...
Click to collapse
Should I remove the patch for CWM on every boot? Or i just download the recovery with rom manager ?
farshad525hou said:
You could convert it... but you would have to write an updater-script, and get an updater-binary (you can basically steal it from any flashable zip.)
Click to expand...
Click to collapse
mmmm... interesting, i will try first the rom manager option and then look this. Thankyou all.
rob219 said:
after you apply the atrix bootstrap use rom manager and install the recovery for the droid bionic and you will be able to back up and restore roms. advance restore also works incase you do a wipe, install a rom, and then want your data restored.
Click to expand...
Click to collapse
Well I tried this with no success , I installed the recovery for the droid bionic and then I reboot into recovery with rom manager and make a cwm backup, the result was an error when generating the md5Sum and my battery went from 60% to 3%, that kinda surprise me it's the second time that happens, the first time was when i was updating from stock 2.3.5 to 2.3.6.
Worth the shot i guess but until i can fix this i guess i'm screwed :'( .
jfrank1485 said:
Well I tried this with no success , I installed the recovery for the droid bionic and then I reboot into recovery with rom manager and make a cwm backup, the result was an error when generating the md5Sum and my battery went from 60% to 3%, that kinda surprise me it's the second time that happens, the first time was when i was updating from stock 2.3.5 to 2.3.6.
Worth the shot i guess but until i can fix this i guess i'm screwed :'( .
Click to expand...
Click to collapse
Try flashing the 2.3.5 fkz...
farshad525hou said:
Try flashing the 2.3.5 fkz...
Click to expand...
Click to collapse
That is an interesting point because everything I've done, the rooted, the atrix bootstrap recovery and the CWM on boot patch has been with version stock rom 2.3.6 I never tried do it with the 2.3.5 so i guess i'll be downgrading tonigth to stock 2.3.5.
thank's, when i'm done i will inform of my result.
cheers.
farshad525hou said:
Try flashing the 2.3.5 fkz...
Click to expand...
Click to collapse
Follow what he said and you will be ok. I've messed this phone up more times than i can count trying to mod and theme stuff and the fkz is a life saver.
Sent from my SAMSUNG-SGH-I997 using xda premium
farshad525hou said:
Try flashing the 2.3.5 fkz...
Click to expand...
Click to collapse
It works!!!! it was the stock 2.3.6 update that was stopping me from backup or restore in CWM maybe it changes something in the bootloader that screw the CWM, but now i'm testing the Lithium rom 1.2 . Thank you all for your help and tips.
back to track
Sorry for bringing this up again but I need the answer to the
original question on converting a CWM backup to flashable zip...
my question:
My CWM Backup consistes of 7 files:
boot.img
recovery.img
system.yaffs2.img
data.yaffs2.img
cache.yaffs2.img
nandroid.md5
.android_secure.vfat.tar
my guess is that the first two go directly into the update.zip
then What about the other three yaffs2 files and the .android_secure.vfat.tar file
how are they extracted/combined into the zip file??
ps.about the updater-script and updater-binary, can I take them both from any flashable zip?
hosamn said:
Sorry for bringing this up again but I need the answer to the
original question on converting a CWM backup to flashable zip...
my question:
My CWM Backup consistes of 7 files:
boot.img
recovery.img
system.yaffs2.img
data.yaffs2.img
cache.yaffs2.img
nandroid.md5
.android_secure.vfat.tar
my guess is that the first two go directly into the update.zip
then What about the other three yaffs2 files and the .android_secure.vfat.tar file
how are they extracted/combined into the zip file??
ps.about the updater-script and updater-binary, can I take them both from any flashable zip?
Click to expand...
Click to collapse
Its possible, I have done it, and the only foders you need are system and data...
It will be a pain, tho, your gonna wanna do it through Linux, updater script needs to have the right commands in it to do this, so its def not a drag and drop process, even tho some of it is..
Sent from my MB865 using xda app-developers app
jfrank1485 said:
Hi everyone! I aware that maybe this is a stupid question, but i have to ask...Is there a way to convert a CWM backup to a flash zip to use with the CWM install zip option??? I'm asking this because I have a particular problem and is that I can't do backups or restore with my CWM so i can't install almost any custom rom that is in the developers forum.
I don't know why i have this problem, even I posted a thread asking for help about this, but I guess I'm the only one experiencing this issue and the only rom I successfully installed is the Victory Rom and is a flashing zip.
By the way I installed the CWM with the Atrix Bootstrap and I applied the patch RAZR-CWMOnBoot-Global-J.Y.Daddy.zip to have the CWM on every boot and I don't experience any GPS issue (I guess i don't know exactly what is the issue) and for the record when I'm trying to do a CWM backup i get the "check sum error" when the CWM tried to finish the backup process, and when i'm attemping to restore a backup the CWM starts without problem but then I get the "Error while restoring /system".
I hope you can helpme with this problem.
Thank's in advanced.
Click to expand...
Click to collapse
I had experience this yesterday when restore using PhilZ v3.81 recovery in my Note 2.. Basically the folder name is critical.. It must remain same as per when the backup folder is created. Else u will got md5 checksum error, if bypass md5 check, than error in /system recovery part. After renam the backup folder to the orig name, the restore is running smooth...
machang said:
I had experience this yesterday when restore using PhilZ v3.81 recovery in my Note 2.. Basically the folder name is critical.. It must remain same as per when the backup folder is created. Else u will got md5 checksum error, if bypass md5 check, than error in /system recovery part. After renam the backup folder to the orig name, the restore is running smooth...
Click to expand...
Click to collapse
all you need to do is use unyaffs on the system.img and optionally data.img and if will unarchive them, then back it into a zip with the boot.img and build the updater-script!
Simple question that I can't find an answer to...
What exactly does ROM Manager's flash option do? If it's a fake flash where does it write the recovery program to and how does it get the phone to boot it? I don't see any kind of update zip on either the internal or external SD so it must have written it to one of the partitions on the block device, but which one and what did it replace?
The phone is a Wind Mobile G2X not a T-Mobile and stock recovery is nothing more than factory reset + reboot. As far as I can tell it's still there and I can still get into it with power+volume-down at boot, so that's not what ROM Manager replaced I guess.
yuma80 said:
Simple question that I can't find an answer to...
What exactly does ROM Manager's flash option do? If it's a fake flash where does it write the recovery program to and how does it get the phone to boot it? I don't see any kind of update zip on either the internal or external SD so it must have written it to one of the partitions on the block device, but which one and what did it replace?
The phone is a Wind Mobile G2X not a T-Mobile and stock recovery is nothing more than factory reset + reboot. As far as I can tell it's still there and I can still get into it with power+volume-down at boot, so that's not what ROM Manager replaced I guess.
Click to expand...
Click to collapse
The problem with ROM Manager is that it messes up the files when flashing a ROM or any file. It is more advised to use CMW Recovery.
yuma80 said:
Simple question that I can't find an answer to...
What exactly does ROM Manager's flash option do? If it's a fake flash where does it write the recovery program to and how does it get the phone to boot it? I don't see any kind of update zip on either the internal or external SD so it must have written it to one of the partitions on the block device, but which one and what did it replace?
The phone is a Wind Mobile G2X not a T-Mobile and stock recovery is nothing more than factory reset + reboot. As far as I can tell it's still there and I can still get into it with power+volume-down at boot, so that's not what ROM Manager replaced I guess.
Click to expand...
Click to collapse
Rom Manager should not be used on the G2x. If you flash a rom and something goes wrong and you can not boot you are dead in the water. Use Nvidia CWM instead.
http://forum.xda-developers.com/showthread.php?t=1056847
Yes thanks. I understand that I shouldn't use ROM Manager, but I want to know what it does and why it doesn't work. For starters anybody know where it writes CWM to?
Worse comes to worse I'm just going to dump /dev/block/mmc* and look for strings or disassemble the apk or something...
yuma80 said:
Yes thanks. I understand that I shouldn't use ROM Manager, but I want to know what it does and why it doesn't work. For starters anybody know where it writes CWM to?
Worse comes to worse I'm just going to dump /dev/block/mmc* and look for strings or disassemble the apk or something...
Click to expand...
Click to collapse
I've always been curious about the details of a 'fake flash' too.. please let us know if you figure out any details.
Rom manager has been around since the original Droid from Verizon. The fake flash you refer to isn't actually a fake flash. It actually flashes CWM recovery. It just doesn't work on this particular phone. I may be wrong on the exact details but the G2x partitions and drivers require the use of NVflAsh to install the CWM. However, there are many phones that once they have been rooted, the user can install Rom Manager and use the Flash Recovery option to install their CWM recovery. There are also times when a particular recovery version (ie.. 5.0.5. Or 4.6.3) works better than another on one particular phone. Rom manager allows users an easy way of flashing between those CWM versions by simply pushing the flash button.
So in summary of a long response... it is only called a fake flash because it looks like it worked on our phone , but in fact it does not. We have to use NVflash to flash our recovery.
If it looks like I'm remotely right ( which I think I am..) hit that thanks button. (Shameless request, I know)
From my understanding, the "fake flash" that ROM Manager does is that it doesn't actually flash CWM like NVFlash does (on the recovery partition) but still puts the CWM files on your SD card saying that you do have it installed (sdcard/clockworkmod) so when you try to flash/install a ROM, it can't put it anywhere. I don't think it will flash anything, but people mess up their devices by wiping data/system and such...
OR...
Maybe it does flash CWM to your device but it has the partition tables all messed up?
One or the other lol, it's just a guess for both options but I believe the first one is right.
I've wondered for a while why rom manager is included in roms for the g2x when it's not advised to use it
Sent from this
DorisTheHeavy said:
I've wondered for a while why rom manager is included in roms for the g2x when it's not advised to use it
Sent from this
Click to expand...
Click to collapse
To rename your nandroid backups .
buru898 said:
To rename your nandroid backups .
Click to expand...
Click to collapse
I never thought about that. I was always unsure what flashing CWM with ROM Manager would do when it's already on my phone using NVFlash.
Since our phones have a dual partition in it. I think it flashes to the internal 1 gig memory so then loading another rom writes over it.
Sent from my LG-P999 using xda premium
OK, I finally had some time to do some poking around. Some of this is guess-work since I was too lazy to verify 100% exactly what it does when you specify that you're running a G2X.
Anyway, in it's settings DB it says this phone's recovery partition is read-only, and there's no flash command set, so I guess it doesn't try to flash it directly. It looks like it's relying on the Google stock recovery image to do the flashing instead, so it downloads a recovery-update.zip to the SD card and writes a script to /cache/recovery and reboots the phone into recovery mode. Google stock recovery would execute the script in /cache/recovery, which says to apply recovery-update.zip, but the actual stock recovery on the phone is either not Google stock, or has been modified; it doesn't bother to execute scripts, it just does a factory-reset (clear /cache, /data, etc) so that's why it doesn't work.
Meanwhile, ROM Manager writes to it's DB that it just flashed CWM version X.Y.Z and happily displays that every time it runs, even though that's not true.
I used NVFlash and moved on with my life.
I have a problem with the backup - fails to restore, a backup file looks like this: see attach file
i can't restore this backup,it's tell me "system error".... so i trying open "data.ext4.tar.a" on PC, like you see i try UNYAFFS utility, also fail..
-- note, all "normal" files are empty,i already try change extension to file with data, always the same --- ERROR
any idea?
thanks to all who help
porusski said:
I have a problem with the backup - fails to restore, a backup file looks like this: see attach file
i can't restore this backup,it's tell me "system error".... so i trying open "data.ext4.tar.a" on PC, like you see i try UNYAFFS utility, also fail..
-- note, all "normal" files are empty,i already try change extension to file with data, always the same --- ERROR
any idea?
thanks to all who help
Click to expand...
Click to collapse
please guys, someone? i have vital data on this backup
have you tried replacing these files by a similar backup? maybe this might work if you use the same rom to get it started again
Starship706 said:
have you tried replacing these files by a similar backup? maybe this might work if you use the same rom to get it started again
Click to expand...
Click to collapse
i'm not, i have super brick.... so i just want open those files and get the data
Sorry to hear that...
I guess if you cannot open these files to extract the files you have a big problem. No other backups available like in googlemail?
Unfortunately no
I just saw this. Let me take a good look.
Sent from my SCH-I405 using xda premium
---------- Post added 16th October 2012 at 12:02 AM ---------- Previous post was 15th October 2012 at 11:59 PM ----------
Give me details. What phone and os. Also, why are you restoring from your PC? Can you get your phone into cwm or similar recovery? What started this problem or what was the last thing you did successfully.
Sent from my SCH-I405 using xda premium
Hey, phone was SGS2, i 'm trying restore from PC because i got super brick - my phone is dead, i need replace motherboard.
First i was install stock rom 4.0.4 with Odin, everything worked fine, so i make backup with cwm and install JB 4.1 - non official, also everything worked fine, after this i remembered that i have forgot some files in stock rom,so i make new backup to JB rom and reinstall stock rom from backup that i make before -- until this stage everything fine. Now i wanted return to JB rom and i try flush backup through cwm and i got error - something like "system image error", so i flush it from begining -just clean rom..
After this i remember that i again forgot some files in stock rom, so again, flush stock from backup trough cwm, after i try back to JB rom trough cwm - like in first time,no success, so i try also like in first time - clean install.. in middle of progress phone just shutdown and dead...
Thank for helping
P.S
After first time that i cannot reinstall JB rom trough cwm i thought that backup doesn't performed correctly, so i make new one.. all those file from second backup, the rom was JB 4.1 with Siya kernel
Yeah umm. I think you lost power during your flash at an early state. Could be wrong but how could you flash a Ron and realize you didn't have some files? Was it your own build?
Sent from my SCH-I405 using xda premium
I am looking at one of these 3 ROMS
http://forum.xda-developers.com/showthread.php?t=2408449
http://forum.xda-developers.com/showthread.php?t=2576967
http://forum.xda-developers.com/showthread.php?t=2275529
I installed the top link the SLIM but when I attempt to boot to System_4 where it was installed, my phone just reboots and boots back to System_1 the stock system. What did I do wrong, or what data do I need to provide so that you can help me troube shoot this?
jo15765 said:
I am looking at one of these 3 ROMS
http://forum.xda-developers.com/showthread.php?t=2408449
http://forum.xda-developers.com/showthread.php?t=2576967
http://forum.xda-developers.com/showthread.php?t=2275529
I installed the top link the SLIM but when I attempt to boot to System_4 where it was installed, my phone just reboots and boots back to System_1 the stock system. What did I do wrong, or what data do I need to provide so that you can help me troube shoot this?
Click to expand...
Click to collapse
EDIT --
It looks like for some reason my boot.img, system.img files were being destroyed when the device rebooted, as when I would boot back into BMM and try to open this installed ROM I would get those error messages. How long should BM take to actually open the custom ROM from 1st run? I waited an hour and just assumed it had hung up, is that an accurate assumption?
jo15765 said:
EDIT --
It looks like for some reason my boot.img, system.img files were being destroyed when the device rebooted, as when I would boot back into BMM and try to open this installed ROM I would get those error messages. How long should BM take to actually open the custom ROM from 1st run? I waited an hour and just assumed it had hung up, is that an accurate assumption?
Click to expand...
Click to collapse
Maybe my issue is just SlimKat the top link can not be installed via MBB -- I have succesfully installed both the 2nd and 3rd link via BMM could that be the deal? Only specific ROMS can be installed via MBB and others need CWM or another type recovery?
jo15765 said:
Maybe my issue is just SlimKat the top link can not be installed via MBB -- I have succesfully installed both the 2nd and 3rd link via BMM could that be the deal? Only specific ROMS can be installed via MBB and others need CWM or another type recovery?
Click to expand...
Click to collapse
That ROM installs fine make sure u make enough space for system data and cache partition before flashing it............800 for sys and data
should do the trick....:laugh: and on another note there aren't many ROM's that can be flashed with anyother recovery other than BMM for A2...:laugh:
darth_nihar said:
That ROM installs fine make sure u make enough space for system data and cache partition before flashing it............800 for sys and data
should do the trick....:laugh: and on another note there aren't many ROM's that can be flashed with anyother recovery other than BMM for A2...:laugh:
Click to expand...
Click to collapse
Hey thanks for the note about BMM I have been reading all the docs I can find about it to better understand it. I never realized how between the MB860 & MB865 there was a world of difference.
I destroyed my system.img, data.img, and cache.img partition and rebuilt at 1,000 MB and the SlimKat ROM is still just sitting at a blank screen when I actually try to boot into it?
What is a good basis to follow as far as knowing how large to set those 3 .img files?
EDIT ---
Also if I delete the folders/data located here:
/data/clockworkmod/virtual/
Why when I boot into BMM does the corresponding System folder still show the name of the ROM I attempted to install? I was wanting to clear it all out for a fresh install. I also did the format system, but the name remains.