Database Info

Codename Android 2.0 stuck in win recovery

I used the CWM to install CNA b4.zip, the Codename Android package.
Now all my phone does is boot into a menu that says:
install wipe
backup restore
mount settings
advanced reboot
How do I get into ICS?

frogcity said:
I used the CWM to install CNA b4.zip, the Codename Android package.
Now all my phone does is boot into a menu that says:
install wipe
backup restore
mount settings
advanced reboot
How do I get into ICS?
Click to expand...
Click to collapse
I think u didnt follow what I wrore in instruction: YOU MUST BE ON ICS TO FLASH THIS ROM...anw, just heimdall back to stock, then flash CM9 and then any ICS rom else u like...remember to stick to instructions next time man...there must be a reason that we (OPs) put it there but not for fun lmao...
Sent from my SGH-T959V using xda premium

daothanhduy1996 said:
I think u didnt follow what I wrore in instruction: YOU MUST BE ON ICS TO FLASH THIS ROM...anw, just heimdall back to stock, then flash CM9 and then any ICS rom else u like...remember to stick to instructions next time man...there must be a reason that we (OPs) put it there but not for fun lmao...
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
I was on ICS (Cyanogenmod9) when I tried to flash it.

frogcity said:
I was on ICS (Cyanogenmod9) when I tried to flash it.
Click to expand...
Click to collapse
Oh so sr, my mistake (inform more info next time bro ^^) so, just try to redownload or recopy and reflash cause I flashed it normally from CM9
Sent from my SGH-T959V using xda premium

sounds like he lost root. You will probably need to use heimdall one click to get back to kj6. Use the one I packaged that can be found here.
http://forum.xda-developers.com/showthread.php?t=1822626
Then flash to ICS and then to the rom you want.

I had this happen to me when I tried to flash CNA b4. No matter what I did I could not get out of recovery when trying to flash. I thought for sure I would have to go back to stock but I just fully wiped and reinstalled AOKP with no problems. It may have been a bad download or something but I had that issue as well.

[Q] Q flash with stock CWM

Hey all , hope u rocking with your tabs.
anyway, I decided to move on and divorce my stock rom forever
I just would like to ask about a few little things before i get starting flashing.
1 - can i flash Panaroid(Cauz it's awesome and very fast software cycle) with the stock CWM?
2 - if i decided to return back to stock ICS, i will have to wipe data then and would that make me vulnerable to the famous brick bug?
3 - how to backup my stock rom just in case?
4 - what's the biggest sacrifices i will make due to this migration?

well, 2 days now and no one answers these questions :S

Well I have Paranoid installed and its perfect. I backed up my stock ICS and I have a backup. That's all.
Sent from my GT-P6800 using xda premium

samomamo said:
Well I have Paranoid installed and its perfect. I backed up my stock ICS and I have a backup. That's all.
Sent from my GT-P6800 using xda premium
Click to expand...
Click to collapse
okay, the question is: did you installed it with the stock cwm?
and should i back it up with stock cwm also?

bassem.mohsen said:
okay, the question is: did you installed it with the stock cwm?
and should i back it up with stock cwm also?
Click to expand...
Click to collapse
No I have TWRP recovery, I backed up with that and installed the PA.
Sent from my GT-P6800 using xda premium

Hi I am newbie as well. Still see and learn from this great helpful website. I would like to share my experience to play around with custom ROM. and so far still safe. These steps are from what I have done although I have not used the wonderful [ROM][JB : 4.1.2][CM10 Hybrid][P6800\P6810\i815] Paranoid Android v2.22 [17/10][WIP], I am still waiting for the nearly perfect of this rom. .
I am still satisfied with [ROM] Singha ROM Version 1.1.1 (SEP 26 2012). http://forum.xda-developers.com/showthread.php?t=1886370
bassem.mohsen said:
Hey all , hope u rocking with your tabs.
anyway, I decided to move on and divorce my stock rom forever
I just would like to ask about a few little things before i get starting flashing.
1 - can i flash Panaroid(Cauz it's awesome and very fast software cycle) with the stock CWM? It is better using CWM instead of Stock recovery. I am using old version Locerra's recovery at this http://forum.xda-developers.com/showthread.php?t=1542897&page=13. Works perfect so far.
2 - if i decided to return back to stock ICS, i will have to wipe data then and would that make me vulnerable to the famous brick bug? if you have downloaded stock ICS thenI would suggest using CWM when you are installing from zip file. So far I did the bellow steps if using CWM :
1) place on internal SD
2) reboot to CWM
3) wipe data/factory reset in CWM
4) wipe cache
5) advanced > wipe dalvik, wipe battery stats
6) install .zip from INTERNAL SD
7) reboot
Another method is using mobile odin or PC Odin to flash with Stock ICS. You can see at this http://forum.xda-developers.com/showthread.php?t=1469635
3 - how to backup my stock rom just in case? You have to install CWM Recoverry. TWRP http://forum.xda-developers.com/showthread.php?t=1809295 or Locerras' recoverry
4 - what's the biggest sacrifices i will make due to this migration? see The OP updated log. It is nearly perfect and there is still bug. But it depends on individual's opinion.
Click to expand...
Click to collapse

oh, thanks very much, cakrabayu.
much appreciate your help.

ok i have another quick question for people who tried PA roms.
did you tried intensive hd games .. does the performance is better?

Mobile Odin Pro: Should wipe data/cache?

Sorry for the noob question, but I intend to update my 8013 to JB and wonder whether it's needed to wipe data/cache? Thank you!

I moved forward without doing so and no issues yet...
Sent from my GT-N8013 using xda app-developers app

l think it depends what you're flashing.
Going from ICS to JB then no, don't wipe
Going from JB to ICS then yes otherwise it gets into a boot loop
Sent from my GT-N8000 using XDA Premium HD app

Yes like the member above said.
But also what rom are you on if you are on custom or customized stock rom and losing data is not a big issue then I would suggest a clean wipe and then install as that would clean you systems

I think a wipe always suggested but I had this same concern about data wipe.
I went from the stock German N8010 4.1.1 rom to the stock US N8013 4.1.2 rom using Mobile Odin, and I only wiped Dalvik (did NOT wipe data). I still have root, and all my data, and so far, I don't seem to have any issues with anything.
But of course, I had titanium back ups, and dropbox data back ups just in case..

hard brick?
Bulbous said:
l think it depends what you're flashing.
Going from ICS to JB then no, don't wipe
Going from JB to ICS then yes otherwise it gets into a boot loop
Sent from my GT-N8000 using XDA Premium HD app
Click to expand...
Click to collapse
isnt it unsafe to do any wipe on a stock rom be it ICS or JB?wont it get hard brick by doing so?just wondering....

I haven't, not on my note 10.1... I used this method to get rid of the "Custom" status in my bootloader and about Settings. I also have a "0" flash count... I did run triangle away first though....

[Q] After Flushing PA Jelly Bean Rom It Keep showing PA boot screen

Hi,
I have AT&T Motorola Atrix 2 MB-865 , i was on official ICS after root unlock I flushed pa_edison-3.69-20130729-nokex.zip rom to my atrix 2, using http://forum.xda-developers.com/showthread.php?t=2050705
i did factory reset, data format system, format cache and etc before flushing that ROM after successful flush , I rebooted , after reboot it keep stuck (does't not hang just stuck) on paranoid boot screen, i tried to flush again but same result in addition i want to say i flushed only rom , no gapps, , now i am again on ics_edison using RDS Lite ,Please any one tell me where i am wrong
Thanks in advance.

cheeta123 said:
Hi,
I have AT&T Motorola Atrix 2 MB-865 , i was on official ICS after root unlock I flushed pa_edison-3.69-20130729-nokex.zip rom to my atrix 2, using http://forum.xda-developers.com/showthread.php?t=2050705
i did factory reset, data format system, format cache and etc before flushing that ROM after successful flush , I rebooted , after reboot it keep stuck (does't not hang just stuck) on paranoid boot screen, i tried to flush again but same result in addition i want to say i flushed only rom , no gapps, , now i am again on ics_edison using RDS Lite ,Please any one tell me where i am wrong
Thanks in advance.
Click to expand...
Click to collapse
Firstly its FLASH not FLUSH.!! On which system did you flash the ROM.. If you have flashed on 2nd system you should not wipe data... It will wipe out your other partitions... And did you flash via bmm or cwm??
Sent from my MB865 using XDA Premium HD app

nikhJ said:
Firstly its FLASH not FLUSH.!! On which system did you flash the ROM.. If you have flashed on 2nd system you should not wipe data... It will wipe out your other partitions... And did you flash via bmm or cwm??
Sent from my MB865 using XDA Premium HD app
Click to expand...
Click to collapse
he's is in a habit of writing 'flush' in place of 'flash' (see his other posts)
sent from my A2 running ÑÜMÅ3.0
$ÇÏÊÑÇÈ is the only TRUTH

Re
nikhJ said:
Firstly its FLASH not FLUSH.!! On which system did you flash the ROM.. If you have flashed on 2nd system you should not wipe data... It will wipe out your other partitions... And did you flash via bmm or cwm??
Sent from my MB865 using XDA Premium HD app
Click to expand...
Click to collapse
I used Atrix2BootStrap.apk which seem like CWM based, there was no option 1st system or second system, it was like standard flashing(means normally we flash using Clock world recovery so no 1s or seccond system option appeared).

cheeta123 said:
I used Atrix2BootStrap.apk which seem like CWM based, there was no option 1st system or second system, it was like standard flashing(means normally we flash using Clock world recovery so no 1s or seccond system option appeared).
Click to expand...
Click to collapse
i think this rom can be install via BMM only... my friend has do like what you do before..... the only you can do is FXZ to stock,root,and then go to play store, install BMM 0.3..... dont install bootstrap.apk again after installing BMM and you will be fine...

I seem to have a similar issue.
First of all although this is my first post on XDA I'm not new to flashing and using Custom Roms infact I have been using CM 10.1 versions switching back and forth between 4.1.2 when I run into trouble.
I decided to give PA a shot and seem to have run into a wall. I flashed PA nokex on system 3 (which previously had CM10.1 - JBX 0.8.1(kernel)).
Before flashing PA on it I destroyed and recreated system, data and cache partitions so I didn't see the need to do wipes on them again. Nevertheless I did dod wipes. Flashed PA nokex, Gapps, wiped dlavik cache and rebooted. (Using BMM ofcourse)
I am stuck at a black screen with the red LED. I would really like to sample PA so any help would be really appreciated.

blazebud350 said:
I seem to have a similar issue.
First of all although this is my first post on XDA I'm not new to flashing and using Custom Roms infact I have been using CM 10.1 versions switching back and forth between 4.1.2 when I run into trouble.
I decided to give PA a shot and seem to have run into a wall. I flashed PA nokex on system 3 (which previously had CM10.1 - JBX 0.8.1(kernel)).
Before flashing PA on it I destroyed and recreated system, data and cache partitions so I didn't see the need to do wipes on them again. Nevertheless I did dod wipes. Flashed PA nokex, Gapps, wiped dlavik cache and rebooted. (Using BMM ofcourse)
I am stuck at a black screen with the red LED. I would really like to sample PA so any help would be really appreciated.
Click to expand...
Click to collapse
i think PA non kexec is for ICS base only!
¢@®bøÑ///JBX

Super_Commando said:
i think PA non kexec is for ICS base only!
¢@®bøÑ///JBX
Click to expand...
Click to collapse
Yeah. I flashed the kexec version and it booted up fine... Thank you.

[Q] Can not read SlimOTA properties!!

Hi There,
My Atrix 2 is running on Slimkat 4.4.3.build.5.9, while trying to update the same via OTA getting error as Can not read SlimOTA properties.
Pls help!!!!!!
Thanks in advance!

Atrix2dBeast said:
Hi There,
My Atrix 2 is running on Slimkat 4.4.3.build.5.9, while trying to update the same via OTA getting error as Can not read SlimOTA properties.
Pls help!!!!!!
Thanks in advance!
Click to expand...
Click to collapse
No one can help you. Because atrix 2 is not officially supported by slim team.
Sent from my MB865 using XDA Premium 4 mobile app

Can not read SlimOTA properties!!
noranora said:
No one can help you. Because atrix 2 is not officially supported by slim team.
Sent from my MB865 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Okay......thanks for the reply. But then how can I update it to 4.4.4 Build 6.0 without Format/Wiping data?
Pls help @alteredlikeness

Atrix2dBeast said:
Okay......thanks for the reply. But then how can I update it to 4.4.4 Build 6.0 without Format/Wiping data?
Click to expand...
Click to collapse
Ideally you should wipe everything and then clean install the ROM. To retain your data and apps, you can take backup using titanium backup or take backup of data partition using BMM then restore (though I am not too sure about BMM method if it really works perfectly).
If you don't want to wipe then you can try to dirty flash the 6.0 ROM on the existing version. Just don't perform format or wipe, just flash the ROM+Gapps. see If it goes well.

Can not read SlimOTA properties!!
Jack Sparrow xda said:
Ideally you should wipe everything and then clean install the ROM. To retain your data and apps, you can take backup using titanium backup or take backup of data partition using BMM then restore (though I am not too sure about BMM method if it really works perfectly).
If you don't want to wipe then you can try to dirty flash the 6.0 ROM on the existing version. Just don't perform format or wipe, just flash the ROM+Gapps. see If it goes well.
Click to expand...
Click to collapse
Okay...that means there is no way to get OTA update:crying:.........anyways...thanks a lot for replying!

Atrix2dBeast said:
Okay...that means there is no way to get OTA update:crying:.........anyways...thanks a lot for replying!
Click to expand...
Click to collapse
Even if there is OTA support in the ROM then also it doesn't mean that the phone will be updated automatically like how it happens in case of official firmware updates. The OTA in most of the custom ROMs just downloads the ROM file on your phone, thats it. Rest you will have to manually install/flash the ROM using that downloaded file like how you maybe doing it now. OTA just cuts the step of finding and downloading the ROM file from internet. So IMO its not a feature which matters much.

Ok bro...thanks a lot for sharing the info and for the timely response...
Sent from my MB865 using XDA Free mobile app

Can not read SlimOTA properties!!
Jack Sparrow xda said:
Ideally you should wipe everything and then clean install the ROM. To retain your data and apps, you can take backup using titanium backup or take backup of data partition using BMM then restore (though I am not too sure about BMM method if it really works perfectly).
If you don't want to wipe then you can try to dirty flash the 6.0 ROM on the existing version. Just don't perform format or wipe, just flash the ROM+Gapps. see If it goes well.
Click to expand...
Click to collapse
Tried dirty flashing...it worked...post booting found that gapps were not working....so flashed latest gapps again...now its rebooting again n again....what to do??

Atrix2dBeast said:
Tried dirty flashing...it worked...post booting found that gapps were not working....so flashed latest gapps again...now its rebooting again n again....what to do??
Click to expand...
Click to collapse
Perhaps it's time for you to clean flash? Idk. Sounds like it's bootlooping. 5.9 gapps was 4.4.3. Meanwhile version 6 is 4.4.4. Sometimes its best for you to start afresh to avoid any issue.
Sent from my MB865 using XDA Premium 4 mobile app

Atrix2dBeast said:
....so flashed latest gapps again...now its rebooting again n again....what to do??
Click to expand...
Click to collapse
No option other than clean install. That type of issue why its always recommended to clean flash the newer versions.
To have little bit of hope, backup the data partition using BMM then later try to restore the data partition using that backup once you successfully flash the ROM. If it works then all is good and if it doesn't then....

Can not read SlimOTA properties!!
Jack Sparrow xda said:
No option other than clean install. That type of issue why its always recommended to clean flash the newer versions.
To have little bit of hope, backup the data partition using BMM then later try to restore the data partition using that backup once you successfully flash the ROM. If it works then all is good and if it doesn't then....
Click to expand...
Click to collapse
Okay....flashed 4.4.4 built 6 again(clean install)...rebooted...and then flashed gapps for the same build....but again its rebooting....had to fxz again...what i am doing wrong here???

Atrix2dBeast said:
Okay....flashed 4.4.4 built 6 again(clean install)...rebooted...and then flashed gapps for the same build....but again its rebooting....had to fxz again...what i am doing wrong here???
Click to expand...
Click to collapse
What are the steps you are following? Are you flashing using BMM? Which system? What GApps version? Try not to reboot between ROM and GApps flashing. Flash only minimal GApps.
I haven't faced any such issue with any of the ROMs so far. I just follow the BMM guide word to word.
Right now I am having 5.10 build and its pretty much stable and almost bug-free for me on System 1. There are few experiments going on in the builds after 5.10 so I would recommend you should also flash the 5.10 build.

Can not read SlimOTA properties!!
Jack Sparrow xda said:
What are the steps you are following? Are you flashing using BMM? Which system? What GApps version? Try not to reboot between ROM and GApps flashing. Flash only minimal GApps.
I haven't faced any such issue with any of the ROMs so far. I just follow the BMM guide word to word.
Right now I am having 5.10 build and its pretty much stable and almost bug-free for me on System 1. There are few experiments going on in the builds after 5.10 so I would recommend you should also flash the 5.10 build.
Click to expand...
Click to collapse
I am using BMM only....on system 1...made a mistake of rebooting between ROM and GApps flashing.:silly: