Hello guys
I messed up with my Nexus 5: I've applied the 'Stock White Holo Build v7' originally created for N4 XDA Thread link and I'm on a boot loop right now.. I was stupid, I wasn't aware that this could put me down.
The .zip has these lines in updater-script:
Code:
run_program("/sbin/busybox", "mount", "/system");
delete("/system/priv-app/Settings.odex");
delete("/system/priv-app/Mms.odex");
delete("/system/priv-app/SystemUI.odex");
delete("/system/priv-app/GoogleCamera.apk");
delete("/system/app/GoogleCamera.apk");
delete("/system/app/GoogleCamera.odex");
delete("/system/app/CalendarGoogle.odex");
package_extract_dir("system", "/system");
unmount("/system");
Inside .zip, has a system folder with these folders and files:
Code:
\system\app\CalendarGoogle.apk
\system\app\DeskClockGoogle.apk
\system\app\GalleryGoogle.apk
\system\app\GoogleCamera.apk
\system\framework\framework-res.apk
\system\priv-app\GoogleDialer.apk
\system\priv-app\KeyGuard.apk
\system\priv-app\Mms.apk
\system\priv-app\Settings.apk
\system\priv-app\SystemUI.apk
\system\priv-app\TeleService.apk
After flashing this .zip listed above, my android got screwed up and got stuck in a bootloop. Looking for a solution, I found this thread: Another XDA Thread - now for N5 and found 'White UI for KOT49H (deodex) v1.zip' available for download there.
This file .zip replaces the following files:
Code:
\system\app\DeskClockGoogle.apk
\system\app\GalleryGoogle.apk
\system\framework\framework-res.apk
\system\priv-app\GoogleDialer.apk
\system\priv-app\Settings.apk
\system\priv-app\SystemUI.apk
\system\priv-app\TeleService.apk
After flashing it, Android booted, but 'com.android.systemui' keeps crashing and I can't do anything else but force boot it.
Question: If I sideload a default 'SystemUI.apk', am I be good again? If so, can anyone please share this apk with me please?
If this won't work, how would you guys solve this? I know tat re-flashing my ROM would do the trick, but I would like to know if there's a simpler solution and with any loss.
Thanks!
How would you be at a loss by flashing your current ROM? It's the simplest way! There won't be any data loss. If you are on a custom rom, then just flash the rom.zip via recovery and you will be good to go! If you're on stock, then download the stock factory image and only flash system.img
vin4yak said:
How would you be at a loss by flashing your current ROM? It's the simplest way! There won't be any data loss. If you are on a custom rom, then just flash the rom.zip via recovery and you will be good to go! If you're on stock, then download the stock factory image and only flash system.img
Click to expand...
Click to collapse
Thank you man, this did the trick. With this, I was able to boot into Android again but somethings are still messed. But once Android booted, I was able to backup some things and now I'm reflashing stock ROM again.
Update: I've finished flashing stock ROM again, leaving userdata intact. When ROM flash was complete I've flashed SuperSU to have root again, re-installed Xposed and everything went back as it was before I screwed everything. Problem 100% solved, thank you again @vin4yak!
This thread may be closed, if this is what happens when the problem mentioned is solved.
Aah! Good to hear
Related
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...
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!
Just a quick question to double check.. I rooted my atrix 2 and installed CWM and took backup of my phone thru it. So two questions:
1.} Now to install custom rom, what should i do? directly now download and install thru cwm or need to flash any other thing?
2.} I accedently changed my stock battery icon thru rom toolbox pro and when i restore my stock rom thru cwm it says md5 check failed.. What should i do?
To install a Custom Rom only need access to CWM Recovery, and follow the installation steps of the Rom you choose, as there are two forms, one is restored and the other is flashing, so you should read the instructions.
thanks buddy!
I did not use rsd or did not flash fast bootfiles, are these necessary for installing custom rom? I guess not i am trying custom roms now..
And what abt the second question?
Sedariya11 said:
thanks buddy!
I did not use rsd or did not flash fast bootfiles, are these necessary for installing custom rom? I guess not i am trying custom roms now..
And what abt the second question?
Click to expand...
Click to collapse
No rsd and fastboot files are for flashing back to stock in the case of u messing up your phone (soft brick or bootloop)
Sedariya11 said:
thanks buddy!
I did not use rsd or did not flash fast bootfiles, are these necessary for installing custom rom? I guess not i am trying custom roms now..
And what abt the second question?
Click to expand...
Click to collapse
for restoring. do a few things. first, make a backup right now and try to restore it right away. If that works, something went wrong with your old one. you can open up the nandroid.md5 file within the backup folder and delete everything, that will make it restore, but it could cause some issues if it really was broken. Or it could not even boot, but that is what the fxz is for.
If it also fails, most likely there is something wrong with your sdcard. that happened to me. try formatting it WITH THE PHONE (backup anything that you need to since it will be wiped). if it fails both times the backups are most likely fine, so just delete everything in the nandroid.md5 file and do it. Keep in mind it may still have issues so be familiar with the stock restoring process just in case.
As always, i don't take responsibility for anything that happens.
Thanks for your help and time in advance. I am trying to flash a ROM to my At&T HTC One X. It is HBOOT 1.14 running ics 2.20. I am specifically trying to flash ViperXL and have failed about 3 times so far. I keep getting my phone stuck in a boot loop. It is no longer in a boot loop because I have flashed the factory ROM. My phone is rooted and I have TWRP as my recovery. I have some specific questions to ask:
1) What version of ViperXL should I use? I think I might be trying to flash the wrong version.
2) Do I leave the entire file zipped when I put it on my sd card or do I specifically extract the boot.img file and keep that file separate from the zip file?
3) If I have Flash Image GUI from the playstore should I use that to flash it? If so do I still follow step 2 above?
This is what I have been doing so far:
1) Downloading this file: ViperXL 3.2.1 - Android File Host (685MB) from http://forum.xda-developers.com/showthread.php?t=1868236
2) Using WInRar to extract its contents and move it to my sd card.
3) Using Flash Image GUI to select boot.img and then pressing flash.
4) Rebooting my phone and then wa-la, boot loop. I have actually been following a youtube video on how to do it but I'm not getting no luck.
If there is an easier way please inform me. I am a noob but love this stuff. Please be specific with instructions so I can enjoy an awesome custom ROM.
Again, thank you for your time and have a great day.
dirty2k9 said:
Thanks for your help and time in advance. I am trying to flash a ROM to my At&T HTC One X. It is HBOOT 1.14 running ics 2.20. I am specifically trying to flash ViperXL and have failed about 3 times so far. I keep getting my phone stuck in a boot loop. It is no longer in a boot loop because I have flashed the factory ROM. My phone is rooted and I have TWRP as my recovery. I have some specific questions to ask:
1) What version of ViperXL should I use? I think I might be trying to flash the wrong version.
2) Do I leave the entire file zipped when I put it on my sd card or do I specifically extract the boot.img file and keep that file separate from the zip file?
3) If I have Flash Image GUI from the playstore should I use that to flash it? If so do I still follow step 2 above?
This is what I have been doing so far:
1) Downloading this file: ViperXL 3.2.1 - Android File Host (685MB) from http://forum.xda-developers.com/showthread.php?t=1868236
2) Using WInRar to extract its contents and move it to my sd card.
3) Using Flash Image GUI to select boot.img and then pressing flash.
4) Rebooting my phone and then wa-la, boot loop. I have actually been following a youtube video on how to do it but I'm not getting no luck.
If there is an easier way please inform me. I am a noob but love this stuff. Please be specific with instructions so I can enjoy an awesome custom ROM.
Again, thank you for your time and have a great day.
Click to expand...
Click to collapse
wipe cache dalvik system and factory reset in recovery
fastboot flash boot boot.img or use the gui to flash the boot.img extracted from the viper rom
install the viper rom within recovery.
read more before you end up with a brick.
it says all this right in the second post of the viper thread
"Download the ViperXL 3.0.0 from the download section
Confirm the md5 checksum is correct on both files (it will be noted on the dl page)
Place the file somewhere on your phone storage
Reboot to TWRP recovery
Backup current ROM
Install ROM using twrp and select wipe during aroma install if coming from another base
If you have 1.14 hboot you will need to flash the boot.img in fastboot. You will need to extract this from the ROM zip. I have found the following tool useful: [TOOL] HTC Auto Boot.img Installer (One Click Tool)
Reboot and Enjoy"
All Flash Image GUI does is flash the boot.img, which is a small part of the overall ROM. You also need to have the entire ROM zip on your SD card. Boot into bootloader, then go into TWRP recovery. Once in TWRP, go to Wipe, do a factory reset (do not factory reset in bootloader, as it will corrupt your SD memory), wipe Dalvik, wipe cache. Then select Install, and navigate to the ROM zip. The ROM will begin to install. AROMA will then launch, giving you a variety of install options specific to ViperXL. Go through the AROMA options. Then when the ROM install is complete, TWRP will give you the option to reboot. Reboot and enjoy.
Do not extract rom lol. Flash it as is!
Sent from my One X using Tapatalk 2
flash successful
Thank you everyone for your replies. I got the ROM flashed and it's working great.
redpoint73 said:
(do not factory reset in bootloader, as it will corrupt your SD memory
Click to expand...
Click to collapse
Wow how did you figure this out? I now know why my sd corrupted on me once. I did click that once in my life. In fact it put me i have the "soft brick and gonna cry" category, complete with post in q&a.
There needs to be a sticky for things like this.. Little nuggets of knowledge.
The sticky should also contain the factory recovery.
And then the sticky should be mandatory before you are allowed to download roms, recoveries, etc. It would save headache for many.
wdkingery said:
Wow how did you figure this out? I now know why my sd corrupted on me once. I did click that once in my life. In fact it put me i have the "soft brick and gonna cry" category, complete with post in q&a.
There needs to be a sticky for things like this.. Little nuggets of knowledge.
The sticky should also contain the factory recovery.
And then the sticky should be mandatory before you are allowed to download roms, recoveries, etc. It would save headache for many.
Click to expand...
Click to collapse
Agreed. I too fall into the category of accidently bootloader factory resetting and almost dieing lol
it has been stated not to factory reset in bootloader, i have posted it probably almost 100 times. i'm glad this thread is finally over it was making me itch and twitch.
wdkingery said:
Wow how did you figure this out? I now know why my sd corrupted on me once.
Click to expand...
Click to collapse
Its a fairly common mistake, and as DvineLord stated, it been discussed quite a bit in various places.
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.