Related
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 am on stock 4.0.4 with a locked bootloader. I want to have root with the stock rom, nothing else just root.
So I am gonna use the tool provided here,
http://forum.xda-developers.com/showthread.php?t=1544940
I have already installed drivers and have the tool downloaded.
Then I would like to flash the stock google 4.0.4 rom that will let me receive OTA updates. Is this the right file?
http://forum.xda-developers.com/showthread.php?t=1569509
Or can I just flash the stock rom from here?
http://forum.xda-developers.com/showthread.php?t=1572307
I heard there are problems flashing stock rom with CWR if the stock recovery isnt removed? Thats why I dont know if I should flash the stock image.
Is the process of flashing rom with CWR recovery the same as with stock recovery?
My phone is the i9023.
Thanks a bunch in advance.
Gambler_3 said:
I am on stock 4.0.4 with a locked bootloader. I want to have root with the stock rom, nothing else just root.
So I am gonna use the tool provided here,
http://forum.xda-developers.com/showthread.php?t=1544940
I have already installed drivers and have the tool downloaded.
Then I would like to flash the stock google 4.0.4 rom that will let me receive OTA updates. Is this the right file?
http://forum.xda-developers.com/showthread.php?t=1569509
Or can I just flash the stock rom from here?
http://forum.xda-developers.com/showthread.php?t=1572307
Is the process of flashing rom with CWM recovery the same as with stock recovery?
Thanks in advance.
Click to expand...
Click to collapse
Baseband version? under about phone
billchen0014 said:
baseband version? Under about phone
Click to expand...
Click to collapse
i9023xxki1.
Sorry should have specified my phone in the OP.
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Harbb said:
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Click to expand...
Click to collapse
You suppose thats better to do manually so I will have latest version of recovery and superuser?
And yes I am aware of the data loss waited sometime to finish all my games now I am ready to lose all my app data.
Harbb said:
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Click to expand...
Click to collapse
Do it this way. The one click is fine but using Android SDK and going through all that will help you in the long run. This way you know the process in case something goes wrong. It may be confusing at first but worth it. It will teach you a lot more than flashing a one click!
I learnt a lot from this and feel much more experienced and capable because of it. I know I will be able to solve any major issues using Android Debug Bridge (adb).
Okay then I am gonna try the manual way and gonna take out time for it. Now I just need to know what do I flash once I have unlocked bootloader and installed CWR?
I just want the stock google rom and receive OTA if nexus S continues to be supported by google.
You won't need to reinstall the ROM if you are currently on 4.0.4. The ROM stays there as-is. Feel free to do your wipes in recovery and reflash stock 4.0.4 through CWM if you must. You flash CWM to your phone and then superuser through CWM.
Steps:
Setup ADB/fastboot
Bootloader --> fastboot oem unlock --> agree
Bootloader --> fastboot flash recovery recovery.img --> this will give you CWM
Recovery --> flash superuser.zip and, if you must, wipe and reflash ICS (flash su AFTER this if done)
Reboot --> bingo
Also note, with stock ROMs it will replace your current recovery with stock recovery on each boot. If you want to keep CWM, delete /system/etc/flash-recovery.sh when you first boot. You'll have to reflash recovery afterward and it will stick.
Oh I was of the impression that unlocking bootloader wipes everything means it wipes the OS as well. That is nice if it's just data and not the OS, dont think I would reflash it if it's not needed.
Can you explain what you mean by will have to reflash recovery? I will have to do that even if I delete that file on first boot? And whats the drawback if I dont delete that file and stick with stock recovery?
As soon as you boot into stock android it will replace the recovery. So if that file is there on first boot, it will replace it while booting and you will be without CWM (stock instead). After first boot you can delete the file (you can reflash a ROM which has this deleted, or delete it yourself from a stock ROM, or even use adb or a recovery-based file manager to delete the file, then you won't have this problem at all) and it will no longer reflash stock recovery, but you would already have the stock one and need to flash CWM one more time to get it to stick. Easiest way is to just flash CWM and delete it within android imo, saves mounting commands and the such.
No downside really. If you need to flash something for one reason or another you'll just have to reflash CWM before you do so. Once rooted, ROM Manager can do this for you within android anyway.
I had already downloaded and installed the drivers from the one click root thread and my computer shows the android adb thing when I connect my phone with USB debugging.
But as you guys suggested I am gonna do the manual way. So do I just skip the installing driver on computer in the part 1 of this guide?
http://forum.xda-developers.com/showthread.php?t=1007782
In my bootloader menu why is it showing my phone as an i9020?? Is it normal?
Gambler_3 said:
In my bootloader menu why is it showing my phone as an i9020?? Is it normal?
Click to expand...
Click to collapse
Because you have a Nexus S with amoled. That's the i9020. The i9023 is SLCD.
DeuXGod said:
Because you have a Nexus S with amoled. That's the i9020. The i9023 is SLCD.
Click to expand...
Click to collapse
He has the i9023 to my knowledge. It is completely normal, though. Bootloader and recovery for i9020 and i9023 series are the same, this can be attributed to the issue with 4.0.3 recovery backlight not turning on.
If fastboot recognises your phone in the bootloader (the fastboot menu), your drivers are installed an working perfectly.
Finally got to the unlock bootloader screen, didnt do it just yet but now I know how to do it.
I must say the guide is a bit outdated, the software has changed quite a bit seems. The most frustrating part was that the fastboot file is actually in the platform tools folder instead of the tools folder which I didnt figure for a while. I will hold off rooting when I have a whole day off because once I lose everything I would be very anxious to get my phone back to normal which will take time.
Thanks for the help harbb, if I have any problem flashing recovery and superuser I will come back for more help.
And yes I have the LCD version i9023.
Btw the guide said the fastboot will be in the tools folder but the tools folder had a read me that "adb has moved to the platform tools folder" this is how I figured to go to that folder and thats where the fastboot file actually was.
Now it says I should put the recovery image in the tools folder so should I do that or put it in the platform tools folder?
In the instructions for the flashing recovery I am not understanding one thing.
6 - Then back on the SNS select Power Off (Reboot also works)
Part 4 - Root
1 - Power ON the SNS
So after flashing recovery I have to reboot? Since I am on stock rom that would bring back the stock recovery so how would I flash superuser then?
If I delete the stock recovery can I still get OTA updates?
fastboot and adb is now in platform tools, that is correct. Easiest way is to put your recovery in there too so you don't have to type in the absolute file path to it, don't put it in tools.
Don't power off or reboot the phone. After you flash recovery go straight into the recovery menu and root, flash custom ROMs, kernels, etc. You can transfer files to flash via the mounts and storage --> mount usb storage menu. After this feel free to reboot.
Harbb said:
fastboot and adb is now in platform tools, that is correct. Easiest way is to put your recovery in there too so you don't have to type in the absolute file path to it, don't put it in tools.
Don't power off or reboot the phone. After you flash recovery go straight into the recovery menu and root, flash custom ROMs, kernels, etc. You can transfer files to flash via the mounts and storage --> mount usb storage menu. After this feel free to reboot.
Click to expand...
Click to collapse
Just wanted to update that I successfully unlocked and rooted. Thanks a bunch mate.
Gambler_3 said:
Just wanted to update that I successfully unlocked and rooted. Thanks a bunch mate.
Click to expand...
Click to collapse
Good work, been wandering what you were up to on this
Hope you enjoy the possibilities.
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.
hi,i am using stock rom running 4.0.4,i had it rooted too and now i had two queries
1)Is rom manager compatible with Atrix 2??
im asking this because when i open it, it shows u need to install CWM recovery...but no option in that responds...not even intall cwm (1st option in menu)....so i installed CWM using atrix boot strapper app and now still rom manager is not detecting CWM..please help
2)after installing CWM, i had backup my present stock rom..so if i flash a new rom now will that CWM and back up still exist??(because we will wipe data which will remove everyhting right??)
for suppose if i flash jelly bean rom and if i dont like it...can i restore my previous stock rom without bricking my device??
thanks for u r help
vdpraneeth said:
hi,i am using stock rom running 4.0.4,i had it rooted too and now i had two queries
1)Is rom manager compatible with Atrix 2??
im asking this because when i open it, it shows u need to install CWM recovery...but no option in that responds...not even intall cwm (1st option in menu)....so i installed CWM using atrix boot strapper app and now still rom manager is not detecting CWM..please help
2)after installing CWM, i had backup my present stock rom..so if i flash a new rom now will that CWM and back up still exist??(because we will wipe data which will remove everyhting right??)
for suppose if i flash jelly bean rom and if i dont like it...can i restore my previous stock rom without bricking my device??
thanks for u r help
Click to expand...
Click to collapse
1) Rom manager is not compatible with Atrix 2. I would not use it. Why do you need it anyway??
You can use Atrix Bootstrapper to go into CWM recovery . Rest can be done there. Or you can use Boot Menu Manager.
2)Of course! it will still be there! the backup is saved on your SD Card. So as long as you don't format your SD Card. It will be there.
NHS2008 said:
1) Rom manager is not compatible with Atrix 2. I would not use it. Why do you need it anyway??
You can use Atrix Bootstrapper to go into CWM recovery . Rest can be done there. Or you can use Boot Menu Manager.
2)Of course! it will still be there! the backup is saved on your SD Card. So as long as you don't format your SD Card. It will be there.
Click to expand...
Click to collapse
Rom Manager does work with Atrix2. If you're on Stock ICS, you can install CWM on every boot, then flash the Bionic recovery through Rom Manager. That will allow you to use the 1 touch backup in RM, just hit backup rom and everything does what it's supposed to.
Here is the CWM on every boot for Stock ICS.
NHS2008 said:
1) Rom manager is not compatible with Atrix 2. I would not use it. Why do you need it anyway??
You can use Atrix Bootstrapper to go into CWM recovery . Rest can be done there. Or you can use Boot Menu Manager.
2)Of course! it will still be there! the backup is saved on your SD Card. So as long as you don't format your SD Card. It will be there.
Click to expand...
Click to collapse
2)will the CWM recovery exist after flashing new rom or i need to install it again??
when i restore to stock fom JB, it means downgrading the firmware right??
so will there be a chance of bricking or is it same to restore anytime from any version??
vdpraneeth said:
2)will the CWM recovery exist after flashing new rom or i need to install it again??
when i restore to stock fom JB, it means downgrading the firmware right??
so will there be a chance of bricking or is it same to restore anytime from any version??
Click to expand...
Click to collapse
No, your Recovery will be wiped after you flash a new rom, but you can install it again and restore your ROM.
But when restoring a rom, make sure you ARE ON THE ROM you are restoring.
E.g. If you flash JB and want Stock ICS back with your backup. First flash the Stock ICS from RSD and then restore your backup from CWM on it.
Or Vice-Versa.
@41rw4lk, Thanks for rectifying that. I did not bother with Rom Manager much.
NHS2008 said:
No, your Recovery will be wiped after you flash a new rom, but you can install it again and restore your ROM.
But when restoring a rom, make sure you ARE ON THE ROM you are restoring.
E.g. If you flash JB and want Stock ICS back with your backup. First flash the Stock ICS from RSD and then restore your backup from CWM on it.
Or Vice-Versa.
@41rw4lk, Thanks for rectifying that. I did not bother with Rom Manager much.
Click to expand...
Click to collapse
but downgrading to stock ICS from JB will brick my mobile right??
is there any problem if im not on the rom im restoring??
(im a newbie and i dont know much..even not found these after searching a lot..thats the reason im asking all these)
41rw4lk said:
Rom Manager does work with Atrix2. If you're on Stock ICS, you can install CWM on every boot, then flash the Bionic recovery through Rom Manager. That will allow you to use the 1 touch backup in RM, just hit backup rom and everything does what it's supposed to.
Here is the CWM on every boot for Stock ICS.
Click to expand...
Click to collapse
how is it possible to flash bionic recovery through RM...all the menu options are disabled for me there even after CWM installed through bootstrap
vdpraneeth said:
2)will the CWM recovery exist after flashing new rom or i need to install it again??
when i restore to stock fom JB, it means downgrading the firmware right??
so will there be a chance of bricking or is it same to restore anytime from any version??
Click to expand...
Click to collapse
I don't think any recovery exist after flashing a new rom. We have a locked bootloader, so we can't replace the stock recovery.img, all of our recoveries hijack the boot process to work. CM10 and PA I believe have a built in recovery, and that's about as close as you'll get to having a recovery exist after flashing a rom.
As far as restoring from JB, I believe you can downgrade to ICS, but you'll have to look at the JB thread to be certain. I'm on AT&T so I haven't had an opportunity to try JB (officially). CM10 is based on JB, but for our phone with the locked bootloader, it's more of a pseudo experience and is based on our ICS framework.
As for bricking, there is always a chance to brick, that's part of the mod game, but if you read and pay attention to what you have and what you're doing, you'll be alright.
vdpraneeth said:
but downgrading to stock ICS from JB will brick my mobile right??
is there any problem if im not on the rom im restoring??
(im a newbie and i dont know much..even not found these after searching a lot..thats the reason im asking all these)
Click to expand...
Click to collapse
UNLESS you have AT&T phone you should be just fine with ref lashing the ICS.
YES. there is a big problem if you are not on a ROM you are restoring.
Its like you are trying to comlete your jigsaw puzzle by putting pieces from some another jigsaw puzzle.
vdpraneeth said:
how is it possible to flash bionic recovery through RM...all the menu options are disabled for me there even after CWM installed through bootstrap
Click to expand...
Click to collapse
You need to use the CWM on every boot setup, the Atrix2Bootstrap alone won't do.
41rw4lk said:
You need to use the CWM on every boot setup, the Atrix2Bootstrap alone won't do.
Click to expand...
Click to collapse
yes...my phone is an AT&T version...though im using it with IDEA.....
so if i install CWM on every boot,then rom manager will detect it and work right??
vdpraneeth said:
yes...my phone is an AT&T version...though im using it with IDEA.....
so if i install CWM on every boot,then rom manager will detect it and work right??
Click to expand...
Click to collapse
Yes. I will say though, if you're on an AT&T branded phone with AT&T firmware, do NOT try to flash the new JB FXZ. It doesn't matter who your carrier is, it matters what firmware your phone is using. So, if you're on AT&T then you need to make sure that the things you flash are for AT&T, or else you will brick and that will be then end of that.
41rw4lk said:
Yes. I will say though, if you're on an AT&T branded phone with AT&T firmware, do NOT try to flash the new JB FXZ. It doesn't matter who your carrier is, it matters what firmware your phone is using. So, if you're on AT&T then you need to make sure that the things you flash are for AT&T, or else you will brick and that will be then end of that.
Click to expand...
Click to collapse
thanks a lot...
what are the ROMS avaialble for us???
can i reflash stock ICS from any of those ROMS safely??
thank you
vdpraneeth said:
thanks a lot...
what are the ROMS avaialble for us???
can i reflash stock ICS from any of those ROMS safely??
thank you
Click to expand...
Click to collapse
CM10
PA
Numa
MIUI (had battery issues, but I think they got it all worked out)
there's a few, you'll just have to look. Most of the time, if something is not meant for AT&T, the devs will post in the description that it isn't compatible. If you want stock ICS back at anytime, you can do yourself a favor and make a backup of your stock ICS all setup the way you like it, so you can restore if needed. If all else fails, there is an Official ICS FXZ that will get you back to stock ICS.
41rw4lk said:
CM10
PA
Numa
MIUI (had battery issues, but I think they got it all worked out)
there's a few, you'll just have to look. Most of the time, if something is not meant for AT&T, the devs will post in the description that it isn't compatible. If you want stock ICS back at anytime, you can do yourself a favor and make a backup of your stock ICS all setup the way you like it, so you can restore if needed. If all else fails, there is an Official ICS FXZ that will get you back to stock ICS.
Click to expand...
Click to collapse
my main question is :
will downgrade to ICS cause brick??
how do i create my own backup for stock ICS??
vdpraneeth said:
my main question is :
will downgrade to ICS cause brick??
how do i create my own backup for stock ICS??
Click to expand...
Click to collapse
You're killing me smalls. You're on ICS already, you're not downgrading anything, nor can you downgrade ie. Gingerbread. There is no Official JB for AT&T, so that's not an issue. CM10 is a JB based rom built on an ICS frame, (for our phone at least), and again, you're not downgrading.
To make a back up, boot in to CWM or whatever recovery you're using (not stock), and click backup. You might hit up the noob thread to get an idea of the terminology and basics for our device. Not trying to be rude, but you're running yourself in circles. You got to walk before you can run.
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.