Database Develop

Newly Rooted 4.4.2 - Only boots to recovery

Okay guys so I just rooted my att note 3 that was completely up to date using the towelroot.com method found here. Stupidly of me I was trying to follow a thread to change my system language in build.prop but after doing that It ONLY boots to recovery / safestrap. After the safestrap screen I tell it to continue to boot normaly and all i get after that is a black screen.
Any ideas? Is it possible to flash safestrap from odin / heimdall / recovery?
Ive tried factory resetting from safestrap and recovery and that didn't change anything.
I not even sure I have safestrap at this point I can get into recovery, and download mode but it sits at the "Samsung Galaxy NOTE 3 [Unlocked Icon] Custom" screen. It wont actually progress to the safestrap.
Before I tried to edit that build.prop the root / safestrap worked fine all day today, restarted several times for different reasons and still worked afterwards.
I had no encryption enabled.
Via recovery -
"Android system recovery <3e>
KOT49H.N900AUCUCNC2"
**** This Worked ****
Possibly? this as a fix?

Would this be okay to use as a stock Kitkat firmware resource for an Odin flash?

Anyone have a N900AUCUCNC2 ROM or firmware I can flash?

BLMaros said:
Anyone have a N900AUCUCNC2 ROM or firmware I can flash?
Click to expand...
Click to collapse
i have the .zip files for it and odin 3
*it sounds to me like a bootloop or a softbrick, I would recommend using this odin 3 and flash the stock kk rom the one i have is the unofficial and is pre-rooted. but it works when i bricked mine repeatedly trying roms.

farmerj said:
i have the .zip files for it and odin 3
*it sounds to me like a bootloop or a softbrick, I would recommend using this odin 3 and flash the stock kk rom the one i have is the unofficial and is pre-rooted. but it works when i bricked mine repeatedly trying roms.
Click to expand...
Click to collapse
That'd be awesome if you could get that to me some how. I more or less have everything fixed but the wake-up after entering my pattern lock is ungodly slow so I'd like to possibly try a different one.

BLMaros said:
That'd be awesome if you could get that to me some how. I more or less have everything fixed but the wake-up after entering my pattern lock is ungodly slow so I'd like to possibly try a different one.
Click to expand...
Click to collapse
I am assuming you know how to use odin.
https://www.dropbox.com/s/2hl1s7pvf5jatbm/NC2_Bootloader_N900AUCECMLG_VER_2.zip
hope this helps. let me know

farmerj said:
I am assuming you know how to use odin.
https://www.dropbox.com/s/2hl1s7pvf5jatbm/NC2_Bootloader_N900AUCECMLG_VER_2.zip
hope this helps. let me know
Click to expand...
Click to collapse
I do, this is perfect thank you!

Did it work?
Sent from Awesome Note 3 At&t
running Purerom CE.

[Q] AHD won't boot into custom roms

New to me AHD will not boot into any custom roms, I'm confused as to why. But here's what I've done:
Root (motochopper)
Unlock bootloader
Using mythtools, flashed recovery
enter recovery, factory reset, also format /system (CWM Touch 6.0.4.4)
flash CM and Gapps
Afterwards, phone just sits at boot logo. I used mythtools to reflash stock firmware, and that boots and works fine, but when I repeat the process of flashing recovery and flashing a rom, the phone will no longer boot. What am I misssing?

If you're flashing CM, make sure you flash a nightly from BEFORE July 1st, or flash milestone release M8. Then report back results.
Any CM-based ROM from after those dates won't flash because of bootloader issues related to the fact that the Atrix HD hasn't been upgraded to Motorola's latest bootloader yet.

quasihellfish said:
If you're flashing CM, make sure you flash a nightly from BEFORE July 1st, or flash milestone release M8. Then report back results.
Any CM-based ROM from after those dates won't flash because of bootloader issues related to the fact that the Atrix HD hasn't been upgraded to Motorola's latest bootloader yet.
Click to expand...
Click to collapse
Thanks. I was trying to flash M8. Guess I'm going to try and reroot and reunlock boot loader, though it's already done.

mustafu said:
Thanks. I was trying to flash M8. Guess I'm going to try and reroot and reunlock boot loader, though it's already done.
Click to expand...
Click to collapse
M8 should work. It's still JB bootloader compatible.

palmbeach05 said:
M8 should work. It's still JB bootloader compatible.
Click to expand...
Click to collapse
Same goes with validus 6.0

It's like fastboot isn't working...keep trying to flash recovery from it and it doesn't seem to work. Going to check those threads.

Went through the whole process again, still bootloops. rom and gapps flash fine with no errors, the only strangeness I notice is that while flashing rom in recovery, it doesn't seem to take very long (15-20 secs at most). I remember it being considerably longer, the gapps take longer to flash than the rom does. MD5 is good, rom is intact. I'm at a loss of what to do.

mustafu said:
Went through the whole process again, still bootloops. rom and gapps flash fine with no errors, the only strangeness I notice is that while flashing rom in recovery, it doesn't seem to take very long (15-20 secs at most). I remember it being considerably longer, the gapps take longer to flash than the rom does. MD5 is good, rom is intact. I'm at a loss of what to do.
Click to expand...
Click to collapse
Which recovery are you using?

mustafu said:
Went through the whole process again, still bootloops. rom and gapps flash fine with no errors, the only strangeness I notice is that while flashing rom in recovery, it doesn't seem to take very long (15-20 secs at most). I remember it being considerably longer, the gapps take longer to flash than the rom does. MD5 is good, rom is intact. I'm at a loss of what to do.
Click to expand...
Click to collapse
Instead of CWM Touch, try flashing Philz Advanced recovery (I think it's what most users use). Download latest from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/moto_msm8960/
I've never had an issue using Philz. I'm on version 6.43.6 now (which is based on CWM 6.0.4.8)

bylithium said:
Which recovery are you using?
Click to expand...
Click to collapse
CWM Touch 6.0.4.4
quasihellfish said:
Instead of CWM Touch, try flashing Philz Advanced recovery (I think it's what most users use). Download latest from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/moto_msm8960/
I've never had an issue using Philz. I'm on version 6.43.6 now (which is based on CWM 6.0.4.8)
Click to expand...
Click to collapse
Thank you, will give it a try.

mustafu said:
CWM Touch 6.0.4.4
Thank you, will give it a try.
Click to expand...
Click to collapse
I recommend philz. What rom are you flashing?

bylithium said:
I recommend philz. What rom are you flashing?
Click to expand...
Click to collapse
Was trying unified CM M8 still.

mustafu said:
Was trying unified CM M8 still.
Click to expand...
Click to collapse
How did philz go for you? I'm running sokp ?

bylithium said:
How did philz go for you? I'm running sokp ?
Click to expand...
Click to collapse
Was another no-go on PhilZ Back on Stock 4.1 again, unfortunately. Didn't even bootloop this time, just sat at the Moto logo. Strangely, I don't have the Bootloader Unlocked warning screen, just a red Moto logo, not sure how that got changed.

mustafu said:
Was another no-go on PhilZ Back on Stock 4.1 again, unfortunately. Didn't even bootloop this time, just sat at the Moto logo. Strangely, I don't have the Bootloader Unlocked warning screen, just a red Moto logo, not sure how that got changed.
Click to expand...
Click to collapse
Damn, I've messaged you.

So after a little this and that, I've realized that the md5 of the ROM isn't matching anymore, and no matter what browser and how many times I download the ROM, the md5 will now never match. Using the md5 checker on PhilZ latest. The gapps match every time when I check.
I've been using my Kingston SD card to store the ROMs and gapps, will try storing them on the phone and see how it fares.
Sent from my MB886 using Tapatalk

It's working now. Flashed the ROM, phone sat at the boot logo for 20 minutes, then the cm boot animation came on and booted from there. This is the 3rd AHD I've owned but the 1st to have this very strange behavior.

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.

Nexus 6 broken root

Trying to root my Nexus 6 with Marshmallow
I installed the modified boot from Chainfire using fastboot, it succeeded, then restarted bootloader, then installed TWRP 2.8.7.1, it succeeded, then booted to TWRP and installed the 2.52 beta of SuperSU and restarted and the phone is saying the 'device is corrupted', gives me some crap URL (g.co/ABH) and doesn't start, is there any way to fix this?
Edit: sort of fixed by using Despair Kernel, however, isn't there a way to do this without installing a custom kernel?

wrsg said:
Trying to root my Nexus 6 with Marshmallow
I installed the modified boot from Chainfire using fastboot, it succeeded, then restarted bootloader, then installed TWRP 2.8.7.1, it succeeded, then booted to TWRP and installed the 2.52 beta of SuperSU and restarted and the phone is saying the 'device is corrupted', gives me some crap URL (g.co/ABH) and doesn't start, is there any way to fix this?
Edit: sort of fixed by using Despair Kernel, however, isn't there a way to do this without installing a custom kernel?
Click to expand...
Click to collapse
yea, you just ignore the message, press a button, and let it boot. it has NOTHING to do with root being broken. its a message that appears, using the stock kernel, if you have unlocked your bootloader. next time dont freak out, lol :silly:

Well if that had worked I would have not said I already tried doing that...

wrsg said:
Well if that had worked I would have not said I already tried doing that...
Click to expand...
Click to collapse
then you are the only one that it did not boot up afterwards.

simms22 said:
then you are the only one that it did not boot up afterwards.
Click to expand...
Click to collapse
It has happened to someone else. If you touch the system partition at all with the stock kernel you will get the warning. Only way is a modified kernel (or boot?). You can use a stock kernel that has a small mod to remove the message.
I switched to the vortex kernel mm beta and am very happy with it. No problems at all and way more responsive.

johnciaccio said:
It has happened to someone else. If you touch the system partition at all with the stock kernel you will get the warning. Only way is a modified kernel (or boot?). You can use a stock kernel that has a small mod to remove the message.
I switched to the vortex kernel mm beta and am very happy with it. No problems at all and way more responsive.
Click to expand...
Click to collapse
using despair/elementalx myself

johnciaccio said:
It has happened to someone else. If you touch the system partition at all with the stock kernel you will get the warning. Only way is a modified kernel (or boot?). You can use a stock kernel that has a small mod to remove the message.
I switched to the vortex kernel mm beta and am very happy with it. No problems at all and way more responsive.
Click to expand...
Click to collapse
We are talking about two different things: one is the red triangle, and the other is shutting down if rooted.
In this case pressing the power key while showing the triangle is what turns the phone off. It is so if somebody else tampered with your phone to stop it from booting and messing with your stuff.
On the other hand, stopping if rooted can be avoided if you have a custom kernel with all SELinux turned off, or using Chainfires boot.img that dabbles with the security settings so the kernel is satisfied and boots. You will have the red triangle, just let it boot.
And if the red triangle troubles you then by using a modified ramdisk, it can be switched off.

Recovery install help...

I'm rooted and on a custom rom on my Z1 but I've lost all recoverys since I installed it. I've tried using the TWRP app to install and Flashify but I just get a error saying " recovery partition not found " can anyone help me at all get TWRP or some recovery on my Z1?
I've no pc at the moment so I have to try get a recovery installed using just my phone.
Thx & I really hope someone can help I'm not liking the rom I'm on at all, rather stock rooted with xposed probably some kernel too.

RiceydDr0id said:
I'm rooted and on a custom rom on my Z1 but I've lost all recoverys since I installed it. I've tried using the TWRP app to install and Flashify but I just get a error saying " recovery partition not found " can anyone help me at all get TWRP or some recovery on my Z1?
I've no pc at the moment so I have to try get a recovery installed using just my phone.
Thx & I really hope someone can help I'm not liking the rom I'm on at all, rather stock rooted with xposed probably some kernel too.
Click to expand...
Click to collapse
Which rom do you use? Probably you should shut down your phone and then press simultaneously power and volume down. Up to when you hear the second vibrate, now you should only push volume down. Then your recovery should appear

DSTRÍIKER Rom bud and can't get into any recovery at all.... It's really annoying

RiceydDr0id said:
DSTRÍIKER Rom bud and can't get into any recovery at all.... It's really annoying
Click to expand...
Click to collapse
Stil got no pc?

Nope :-/

RiceydDr0id said:
Nope :-/
Click to expand...
Click to collapse
Bootloader locked or unlocked??
Remeber the more info you give less question I have to ask.
Model, rom, bootloader, root status etc

Unlocked bud

Then flash kernel image from Rashr app. Choose any stock based kernel. I like ok kernel. In the zip extract the boot image and then flash it through Rashr app from playstore. There you go kernel and recovery.

IL try now stock kernel only yea?

RiceydDr0id said:
IL try now stock kernel only yea?
Click to expand...
Click to collapse
Stock based kernel. Like ok kryptonian artemesia

I just did it with rashr & ok kernl... now my phone wont turn on!! just black with d red LED flashing on & off. Plzzzz god someone help me

Please tell me i can fix this

RiceydDr0id said:
Please tell me i can fix this
Click to expand...
Click to collapse
I am here don't you worry. First are you sure you are locked bootloader. Second please tell me exactly what you did. You can contact me on Hangouts for quick reply. Check your inbox I have sent you my mail id.

I said its unlocked iv a brick now ;-( im using my navidia shield to contact u..

RiceydDr0id said:
I said its unlocked iv a brick now ;-( im using my navidia shield to contact u..
Click to expand...
Click to collapse
Check your inbox I have sent you my mail id. Contact me there

What was the battery when you flashed it.

I have the problem too. I installed twrp from cmd everything was OK but cannot open the recovery. No led work when booting.

nemes480 said:
I have the problem too. I installed twrp from cmd everything was OK but cannot open the recovery. No led work when booting.
Click to expand...
Click to collapse
Did you ever flash. 236 fw??
If not this is the right time you have to do it once.

I did it maybe 100 times. But I m sorry i did it 101 time .5 miutes before your post and still doesnt work

Not just this type of the install give me error...