Database Develop

[q] cannot install cm 11!! :(

Hi guys I downloaded CM 11 from cyanogenmod.org for the Atrix HD and when I try to download it I get the error ''Status 7'' with CWM Recovery. Have you guys been able to install it with the file from the web site?? Please help :crying:

Are you running the latest recovery?

Phil recovery iss more up to date then the cwm itself

audit13 said:
Are you running the latest recovery?
Click to expand...
Click to collapse
Yes I am running cwm recovery 6.04.4e

SVLAN said:
Phil recovery iss more up to date then the cwm itself
Click to expand...
Click to collapse
How do I replace CWM recovery for Phil recovery?? Any guide??

Download and flash in recovery
Sent from my MB886 using XDA Premium 4 mobile app

Not sure if this will help: http://forum.xda-developers.com/showthread.php?t=2302599

penser
audit13 said:
Not sure if this will help: http://forum.xda-developers.com/showthread.php?t=2302599
Click to expand...
Click to collapse
Like I mention in every one of these threads, Status 7 is, at least 99% of the time, a bad download. Redownload and verify the MD5 checksum.
The MD5 for the official nightly is "513639551c586888db38bc9b17c7dab2". Use this program to verify the MD5 checksum.

helldogg75 said:
Download and flash in recovery
Sent from my MB886 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you. I just flashed that recovery and it worked.

I'm having the same problem with every single 4.4 and 4.4.x rom. I've tried removing the lines of code method already, running 6.0.2.8 cwm

ph3dia said:
I'm having the same problem with every single 4.4 and 4.4.x rom. I've tried removing the lines of code method already, running 6.0.2.8 cwm
Click to expand...
Click to collapse
4.4 needs the latest CWM to install. Try using Philz Touch Recovery or install the latest img from the Clockwork website.

I don't know if any of you guys solved your issues but you need to download cm11 onto external SD card then download philz touch version of cwm also on ESD card. Flash philz touch in your already existing cwm whatever version that may be. I forgot if it will boot back into recovery automatically but get back into recovery. If you are soft bricked get back in recovery by holding the power and vol up button I think and just flash rom as normal wipe data/cache/dalvik etc. That's how fixed my status 7 and flashed OSE 4.4.2 and loving it. Hope I helped.

Black_halo said:
I don't know if any of you guys solved your issues but you need to download cm11 onto external SD card then download philz touch version of cwm also on ESD card. Flash philz touch in your already existing cwm whatever version that may be. I forgot if it will boot back into recovery automatically but get back into recovery. If you are soft bricked get back in recovery by holding the power and vol up button I think and just flash rom as normal wipe data/cache/dalvik etc. That's how fixed my status 7 and flashed OSE 4.4.2 and loving it. Hope I helped.
Click to expand...
Click to collapse
So I was able to update my recovery but now every single rom that I try to flash ends up stuck at the motorola logo. I don't know what to do. I can still get into recovery but no rom works.

ph3dia said:
So I was able to update my recovery but now every single rom that I try to flash ends up stuck at the motorola logo. I don't know what to do. I can still get into recovery but no rom works.
Click to expand...
Click to collapse
Moto logo? Are you trying to go back to stock?

Black_halo said:
Moto logo? Are you trying to go back to stock?
Click to expand...
Click to collapse
Nah, it's the dual core technology right before the animation for the startup. I posted a thread about the problem.

ph3dia said:
I'm having the same problem with every single 4.4 and 4.4.x rom. I've tried removing the lines of code method already, running 6.0.2.8 cwm
Click to expand...
Click to collapse
Try flashing Phil's Recovery, it should be version 6.0.4.5. Once I flashed Phil's I have not had a failed flash of any 4.4 Rom.
Here is the link in case you need it.
http://forum.xda-developers.com/showthread.php?t=2552622

PeteSeiler2010 said:
Try flashing Phil's Recovery, it should be version 6.0.4.5. Once I flashed Phil's I have not had a failed flash of any 4.4 Rom.
Here is the link in case you need it.
http://forum.xda-developers.com/showthread.php?t=2552622
Click to expand...
Click to collapse
That's what I've been running

ph3dia said:
That's what I've been running
Click to expand...
Click to collapse
Maybe try going back to stock and starting over. Whenever I have strange problems like this and everything checks out, I revert to stock and start over.

PeteSeiler2010 said:
Maybe try going back to stock and starting over. Whenever I have strange problems like this and everything checks out, I revert to stock and start over.
Click to expand...
Click to collapse
That was the first thing I tried, I just get a black screen once the phone tries to boot up.

ph3dia said:
That was the first thing I tried, I just get a black screen once the phone tries to boot up.
Click to expand...
Click to collapse
Did you use fastboot commands or the RUU?
Sent from my Atrix HD using XDA Premium 4 mobile app

[Q] Xperia Z1 is recognized as "togari", Z Ultra

As the title suggests, I rooted my phone, unlocked BL and was about to flash CM for Honami, which is Z1, but the flashing of the ROM was stopped because it recognizes my device, a Z1, as a "togari", a Z Ultra. I find this quite odd as I have practically no idea why it does that.
I also tried flashing "togari" CM ROM, but that also fails.
Any fixes for this?

Sari95 said:
As the title suggests, I rooted my phone, unlocked BL and was about to flash CM for Honami, which is Z1, but the flashing of the ROM was stopped because it recognizes my device, a Z1, as a "togari", a Z Ultra. I find this quite odd as I have practically no idea why it does that.
I also tried flashing "togari" CM ROM, but that also fails.
Any fixes for this?
Click to expand...
Click to collapse
if you are sure that you have an z1... then just remove the device check in the updater script (within the zip...) it is in the beginning... cant really remember how it looks but ... search google perhaps.. then it will flash weird enough ... my s also identifies as an sl... but that is from the build prop

HellRoot said:
if you are sure that you have an z1... then just remove the device check in the updater script (within the zip...) it is in the beginning... cant really remember how it looks but ... search google perhaps.. then it will flash weird enough ... my s also identifies as an sl... but that is from the build prop
Click to expand...
Click to collapse
Haha, yes. I google for it and tried to simply delete the device check in update-script, but it didn't work for me. I believe the issue is in my recovery, which is not a 4.4 kitkat recovery. The CWM-recovery I have at the moment is 6.0.3.6 and I believe that is the reason for my issues. I have had no luck trying to find a 4.4 kitkat recovery... any tips here?

Sari95 said:
Haha, yes. I google for it and tried to simply delete the device check in update-script, but it didn't work for me. I believe the issue is in my recovery, which is not a 4.4 kitkat recovery. The CWM-recovery I have at the moment is 6.0.3.6 and I believe that is the reason for my issues. I have had no luck trying to find a 4.4 kitkat recovery... any tips here?
Click to expand...
Click to collapse
well..i have never had problems with it being the recovery... what error does it make now?

HellRoot said:
well..i have never had problems with it being the recovery... what error does it make now?
Click to expand...
Click to collapse
I tried this recovery too, without any luck: http://forum.xda-developers.com/showthread.php?p=49966299
To begin with I got Status 7 error, which is now gone.. I found a tutorial to flash SlimRom for Z1, which is android 4.4.2: http://www.ibtimes.co.uk/android-4-4-2-kitkat-sony-xperia-z1-available-via-slimkat-rom-1432702
However, I was only able to make emergency calls, no cellular at all. I flashed CM through the same method and everything I tried worked, except cellular. Thus, I had to wipe it and install stock Sony firmware.
After that I tried flashing CM the "normal" way through recovery and everything installed as usual, but when I push reboot to reboot the system, the phone simply shuts off. Even if I press the powerbutton to turn it on, it only vibrates and nothing else happens. Again, I flashed stock firmware to be able to use the phone again...
I am very confused about this, because it does not give any errors. It simply does not work :l

[/COLOR]
Sari95 said:
I tried this recovery too, without any luck: http://forum.xda-developers.com/showthread.php?p=49966299
To begin with I got Status 7 error, which is now gone.. I found a tutorial to flash SlimRom for Z1, which is android 4.4.2: http://www.ibtimes.co.uk/android-4-4-2-kitkat-sony-xperia-z1-available-via-slimkat-rom-1432702
However, I was only able to make emergency calls, no cellular at all. I flashed CM through the same method and everything I tried worked, except cellular. Thus, I had to wipe it and install stock Sony firmware.
After that I tried flashing CM the "normal" way through recovery and everything installed as usual, but when I push reboot to reboot the system, the phone simply shuts off. Even if I press the powerbutton to turn it on, it only vibrates and nothing else happens. Again, I flashed stock firmware to be able to use the phone again...
I am very confused about this, because it does not give any errors. It simply does not work :l
Click to expand...
Click to collapse
just copied from the CM11 dev fora...
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm10 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.

HellRoot said:
[/COLOR]
just copied from the CM11 dev fora...
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm10 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
Click to expand...
Click to collapse
Hmm... seems reasonable. Could you give me the link to the fora, so I can try this method out too ?

Sari95 said:
Hmm... seems reasonable. Could you give me the link to the fora, so I can try this method out too ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2540650
there it is.... hope you figure it out.

Sari95 said:
As the title suggests, I rooted my phone, unlocked BL and was about to flash CM for Honami, which is Z1, but the flashing of the ROM was stopped because it recognizes my device, a Z1, as a "togari", a Z Ultra. I find this quite odd as I have practically no idea why it does that.
I also tried flashing "togari" CM ROM, but that also fails.
Any fixes for this?
Click to expand...
Click to collapse
I had this problem when I try to flash with LB.

HellRoot said:
http://forum.xda-developers.com/showthread.php?t=2540650
there it is.... hope you figure it out.
Click to expand...
Click to collapse
Thank you I kind of figured it out... but I am not sure why/ how xD I wiped everything, flashed stock firmware "a.136", rooted, installed recovery and flashed CM. After that, it worked as it is supposed to, so problem solved
Thanks for your help

Sari95 said:
Thank you I kind of figured it out... but I am not sure why/ how xD I wiped everything, flashed stock firmware "a.136", rooted, installed recovery and flashed CM. After that, it worked as it is supposed to, so problem solved
Thanks for your help
Click to expand...
Click to collapse
good to hear hope you enjoy the CM.... if you want then please tell me how it is running.. performance, battery, camera etc
have a good day

cant flash any rom

atrid hd rooted unlocked and custom recovery ,but i still cant falsh anyrom just goes to black screen and if i wait long enough it goes to a green screen, wtf right was running carbon kitkat but bricked on accident and rsd back to stock 4.1.1 and now can flash at all please help...................

So, you are on Stock right now? Did you flashed with RSD? Which recovery are you using?

mauchito said:
So, you are on Stock right now? Did you flashed with RSD? Which recovery are you using?
Click to expand...
Click to collapse
yes i am stock using phil touch recovery and did flash with RSD

Try flashing the bell stock ROM, then Philz, then a custom rom. I assume your phone boots with the stock ROM properly and you receive no errors when flashing a custom ROM.

audit13 said:
Try flashing the bell stock ROM, then Philz, then a custom rom. I assume your phone boots with the stock ROM properly and you receive no errors when flashing a custom ROM.
Click to expand...
Click to collapse
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml that is the one i used and then rerooted with myth tool and then installed philz from fastboot ...still gett a black screen when i flash new rom , and yes did wipe multiple times factory , cache , and dalvik

Try flashing the Mexico Retail or Bell Retail using RSD Lite instead of Myth.

audit13 said:
Try flashing the Mexico Retail or Bell Retail using RSD Lite instead of Myth.
Click to expand...
Click to collapse
wouldnt happen to have a bell retail link lying around would ya and i did flash with rsd only rooted with myth

Look under the development threads. I believe skeevy posted a link.

audit13 said:
Look under the development threads. I believe skeevy posted a link.
Click to expand...
Click to collapse
found it downloading now thnks ill let u no wht happens

dgross1123 said:
found it downloading now thnks ill let u no wht happens
Click to expand...
Click to collapse
To clear something up -- does your phone boot after flashing a fastboot? If no, you need to format the internal sd and change it's mount point to /data/media (use Philz CWM to do all that) -- that's a common error after downgrading from a 4.2+ rom to a 4.1.2- rom.

skeevydude said:
To clear something up -- does your phone boot after flashing a fastboot? If no, you need to format the internal sd and change it's mount point to /data/media (use Philz CWM to do all that) -- that's a common error after downgrading from a 4.2+ rom to a 4.1.2- rom.
Click to expand...
Click to collapse
ok link is a croupt file i will try the internal thing and is it ok to flash the mexico one even though im in us

dgross1123 said:
ok link is a croupt file i will try the internal thing and is it ok to flash the mexico one even though im in us
Click to expand...
Click to collapse
Just skip the gpt partition and you'll be fine.

skeevydude said:
Just skip the gpt partition and you'll be fine.
Click to expand...
Click to collapse
noob question wht is gtp partition .thts a term i havent heard with android

dgross1123 said:
noob question wht is gtp partition .thts a term i havent heard with android
Click to expand...
Click to collapse
Partition table. Our equivalent to a PC's mbr or gpt (newer more advanced mbr). Its unable to be downgraded.

ok well im now back fully stock, rooted and, runnin philz recovery i couldnt get either bell or mexico one to work should i try to flash now

dgross1123 said:
ok well im now back fully stock, rooted and, runnin philz recovery i couldnt get either bell or mexico one to work should i try to flash now
Click to expand...
Click to collapse
Yep, just boot into recovery and make nandroid backup saved to the external sd before you flash anything (you risk wiping it accidentally if stored to the internal sd). That way if anything goes wrong all you have to do is boot into recovery and restore your backup.

skeevydude said:
Yep, just boot into recovery and make nandroid backup saved to the external sd before you flash anything (you risk wiping it accidentally if stored to the internal sd). That way if anything goes wrong all you have to do is boot into recovery and restore your backup.
Click to expand...
Click to collapse
ok so i still get noting tried to flash cm10 after full wipe and still only get to unlocked bootloader screen then the screen goes black does anyone have the jb ota update that works

dgross1123 said:
ok so i still get noting tried to flash cm10 after full wipe and still only get to unlocked bootloader screen then the screen goes black does anyone have the jb ota update that works
Click to expand...
Click to collapse
Try flashing a CM11 ROM. I use Validus 5.1 on mine and it's great.

audit13 said:
Try flashing a CM11 ROM. I use Validus 5.1 on mine and it's great.
Click to expand...
Click to collapse
ok so valdius worked wtf havent been able to flash for weeks thk u guys

dgross1123 said:
ok so valdius worked wtf havent been able to flash for weeks thk u guys
Click to expand...
Click to collapse
Glad you got it to work. There are other great ROMs out there to use while we wait for the official KK ROM, if it ever comes.

update software atrix hd

i recieved several times a message saying that i have to install a security update (at&t), after some time i decided to install it but when i try to i get a status 7, another thing what do i need to install a custom rom on my arix hd, it has android 4.1 from at&t, unlocked bootloader, cwm, and carrier unlocked (i dont want to loose this), in my touchpad i just have to download the rom + gapss and install them from a custom recover, so i dont know if this is the same for the atrix hd, thanks in advance.

You need to be running stock recovery and stock ROM to install the update.
The update includes security patches and some modem updates. This update may be necessary for taking the OTA KK update.

audit13 said:
You need to be running stock recovery and stock ROM to install the update.
The update includes security patches and some modem updates. This update may be necessary for taking the OTA KK update.
Click to expand...
Click to collapse
ok thanks for answering, i have stock rom so, but unlocked bootloader can i install it then just by installing the stock recovery?

You may need to be unrooted in addition to having stock recovery.
If you removed too many of the att apps, that may cause the update to fail as well.

audit13 said:
You may need to be unrooted in addition to having stock recovery.
If you removed too many of the att apps, that may cause the update to fail as well.
Click to expand...
Click to collapse
where can i find stock recovery?, because when i turn the phone on it takes about 40 secs to reboot into recovery to update, so i cant do anything with it now :S

maur1c10 said:
where can i find stock recovery?, because when i turn the phone on it takes about 40 secs to reboot into recovery to update, so i cant do anything with it now :S
Click to expand...
Click to collapse
Did you phone take the update or is it automatically booting into recovery?
The best way to get the update is to flash back to stock ATT 4.1.1, take the OTA update, re-install CWM, and carry on using a custom ROM. This is exactly what I did with a Bell Canada Atrix HD.
You can try re-installing stock recovery in fastboot.

audit13 said:
Did you phone take the update or is it automatically booting into recovery?
The best way to get the update is to flash back to stock ATT 4.1.1, take the OTA update, re-install CWM, and carry on using a custom ROM. This is exactly what I did with a Bell Canada Atrix HD.
You can try re-installing stock recovery in fastboot.
Click to expand...
Click to collapse
Yeah. The quickest, sure-fire way to get in a position to take the OTA update is to flash back to stock (stock files available here). You can use RSD or MythTools, whatever works for you. Doing this will also put you back on stock recovery.
I had to do this, too, before I could take the OTA. But in my case I had modified/removed too many AT&T stock apps...

thanks to both of you, yes the phone rebooted itself like about 40 secs from turning on i was able to fix this part by formatting cache from cwm, now im gonna try to flash stock recovery

quasihellfish said:
Yeah. The quickest, sure-fire way to get in a position to take the OTA update is to flash back to stock (stock files available here). You can use RSD or MythTools, whatever works for you. Doing this will also put you back on stock recovery.
I had to do this, too, before I could take the OTA. But in my case I had modified/removed too many AT&T stock apps...
Click to expand...
Click to collapse
so i flashed the stock recovery from the stock rom, but when i go into recovery the android is down with a red exclamation sign and i cant get into the recovery menu :S, did this happen to you by any chance?

maur1c10 said:
so i flashed the stock recovery from the stock rom, but when i go into recovery the android is down with a red exclamation sign and i cant get into the recovery menu :S, did this happen to you by any chance?
Click to expand...
Click to collapse
When the dead Android dude is on the screen, tap the bottom right hand side of screen. Hopefully, a menu will appear.

audit13 said:
When the dead Android dude is on the screen, tap the bottom right hand side of screen. Hopefully, a menu will appear.
Click to expand...
Click to collapse
well i flashed the stock firmware, and the phone works fine but still the same with recovery, nothing happens if i touch on the screen or if i press volume or power button, tried to install the update anyway but it fails, hope i can somehow install KK when it comes

maur1c10 said:
well i flashed the stock firmware, and the phone works fine but still the same with recovery, nothing happens if i touch on the screen or if i press volume or power button, tried to install the update anyway but it fails, hope i can somehow install KK when it comes
Click to expand...
Click to collapse
Which stock ROM did you install? There are 2 versions of 4.1.1.

audit13 said:
Which stock ROM did you install? There are 2 versions of 4.1.1.
Click to expand...
Click to collapse
Blur_Version.98.4.20.MB886.ATT.en.US is the one that my phone already had

I think that is the ROM before the update.
I see another ROM named Blur_Version.98.5.38.MB886.ATT.en.US too.

audit13 said:
I think that is the ROM before the update.
I see another ROM named Blur_Version.98.5.38.MB886.ATT.en.US too.
Click to expand...
Click to collapse
flashed it and works fine except recovery the same issue but its updated so i can go to cwm now, thanks man

maur1c10 said:
flashed it and works fine except recovery the same issue but its updated so i can go to cwm now, thanks man
Click to expand...
Click to collapse
Did you flash 98.4.20 or 98.5.38?

audit13 said:
Did you flash 98.4.20 or 98.5.38?
Click to expand...
Click to collapse
the first time i flashed 98.4.20 the second time 98.5.38 and i have the same problem with recovery in both cases

maur1c10 said:
the first time i flashed 98.4.20 the second time 98.5.38 and i have the same problem with recovery in both cases
Click to expand...
Click to collapse
Strange. Did you flash both ROMs using RSD Lite or Myth? I had to use RSD Lite without Myth to flash 98.4.20.

audit13 said:
Strange. Did you flash both ROMs using RSD Lite or Myth? I had to use RSD Lite without Myth to flash 98.4.20.
Click to expand...
Click to collapse
i used myth (easier to use), could that make any difference?

maur1c10 said:
i used myth (easier to use), could that make any difference?
Click to expand...
Click to collapse
I got a Bell Canada Atrix HD from a co-worker. When I used Myth to flash from stock Bell to stock ATT, it would not work properly. When I used RSD with 98.4.20 without going through Myth, the ATT ROM flashed without any errors. I was able to take the OTA update, flash CWM, and revert to a custom ROM.

Stuck at reboot after flashed the new version of twrp

I have flashed the 3.2.1.0 version of twrp recovery but it stucks at reboot when i reboot the system well i don't know what to do if i flash the old versin 3.1.1.0 is it would be problem. Now i am on stock rom and recovery. Open for suggestions.

It may be a kernel problem. I had the same thing happen on stock. I fixed it by downloading a ROM then installing TWRP. After install go right into recovery after you disconnect from Odin and clean flash the new ROM. No problems after that.

Any errors on screen as it boots?

phuhcue said:
Any errors on screen as it boots?
Click to expand...
Click to collapse
İt's just shows note 5 logo and repeating that after and after.

sparkeymat said:
It may be a kernel problem. I had the same thing happen on stock. I fixed it by downloading a ROM then installing TWRP. After install go right into recovery after you disconnect from Odin and clean flash the new ROM. No problems after that.
Click to expand...
Click to collapse
Can you provide any more details and specifics on which files and procedures worked for you? Thank you.

[email protected] said:
Can you provide any more details and specifics on which files and procedures worked for you? Thank you.
Click to expand...
Click to collapse
I used the latest TWRP and immediately flashed the Teleteam s8n8 ROM after installing TWRP. You can find the ROM on here with a quick search.