Database Users

Help! Can't boot / cant get into recovery. ..

I was unlocked and rooted and ready to install CM7. I followed all the instructions in the Official Atrix CM7 OP to the T, but when it rebooted, I got stuck on the boot screen with "unlocked" and the red M logo.
I tried to repeat the process several times and ended kind of giving up, factory wiping, and then trying to restore my backup. It appeared to restore successfully, but when I rebooted the phone now wont boot at all. I can't even get it into recovery. No combination or order of button presses or battery pulls / usb plugins will turn it on. I just have a green light like it's charging but nothing is working.
Is it possible to brick your phone even after you have been successfully unlocked and rooted just while you are trying to install CM7?
Please help. I am really desperate here. . .

jimjenkins said:
I was unlocked and rooted and ready to install CM7. I followed all the instructions in the Official Atrix CM7 OP to the T, but when it rebooted, I got stuck on the boot screen with "unlocked" and the red M logo.
I tried to repeat the process several times and ended kind of giving up, factory wiping, and then trying to restore my backup. It appeared to restore successfully, but when I rebooted the phone now wont boot at all. I can't even get it into recovery. No combination or order of button presses or battery pulls / usb plugins will turn it on. I just have a green light like it's charging but nothing is working.
Is it possible to brick your phone even after you have been successfully unlocked and rooted just while you are trying to install CM7?
Please help. I am really desperate here. . .
Click to expand...
Click to collapse
are you using the right recovery? romracer or rom manager!

i am using the tenfar CWM included in the Atrix 4G Automatic Unlock script package. will this not work?
if not, how do I replace it with the right recovery if I cant even get into the phone?

jimjenkins said:
i am using the tenfar CWM included in the Atrix 4G Automatic Unlock script package. will this not work?
if not, how do I replace it with the right recovery if I cant even get into the phone?
Click to expand...
Click to collapse
no, that the old recovery you can use the rom manager if you have , or romracer latest recovery you can find that in the development section, also ther was instruction in the cm7 thread.

you should have left it alone at the M boot screen because it takes about 5-10min to boot after unlock and flash...
everything you do now will have to be through fastboot DO NOT SBF FLASH ANYTHING!!!
Go here to use Fastboot
then download the system.img and boot.img from here
use fastboot to push the boot.img and system.img to your phone
if it gets stuck at the M boot screen let it sit for at least 10min
EDIT: get Romracer recovery from here and push that through to your phone through fastboot

Yeah youre going to have to fastboot wipe recovery then fastboot flash recovery recovery.img
Just download rom racers and rename it..recovery.img
Sent from my GT-I9100 using xda premium

Great. Sorry to be such a noob, but do I decompress the CWM-recovery-atrix5.zip file and push the recovery.img file that's inside it? or push the CWM-recovery-atrix5.zip itself?
Also - every time I am able to get my phone into fastboot mode, it says my battery is too weak to flash anything. I cant seem to get the battery to charge enough to execute any fastboot commands. Any way around this? a powered usb hub?

jimjenkins said:
Great. Sorry to be such a noob, but do I decompress the CWM-recovery-atrix5.zip file and push the recovery.img file that's inside it? or push the CWM-recovery-atrix5.zip itself?
Also - every time I am able to get my phone into fastboot mode, it says my battery is too weak to flash anything. I cant seem to get the battery to charge enough to execute any fastboot commands. Any way around this? a powered usb hub?
Click to expand...
Click to collapse
If you can borrow another Atrix user's battery, or take yours to an AT&T store and see if they can charge it for you.
If you're able to get back into recovery then you can just flash the zip.
If not, you'll need to extract the recovery.img to use it with fastboot, or just download it directly from the OP in romracer's thread. (The left hand link is just the .img, the right hand side is the CWM .zip) Then place it in the same directory as fastboot.

So I can literally flash a different recovery from within another?

jimjenkins said:
So I can literally flash a different recovery from within another?
Click to expand...
Click to collapse
yes but it MUST be working proper first ! its ok to use rom managers cwm but i just prefer the otherone alawys have but n e way there are only 2 that are current (uptodate )
thoughs 2 and with romracers you can. chose
a color that you like not just blue
Sent from my MB860 using xda premium

Its the recovery from tenfar CWM. When I can get it into recovery it seems to be working - with the obvious exception of successfully installing CM7
So I can flash romracer recovery from inside tenfar recovery?
sorry if im being redundant - just dont want to screw it up!
thanks

Just download rom racers cwm. Img, head into fastboot and then fastboot flash recovery recovery-****** (whatever yer recovery image color u chose is)
Sent from my MB860 using Tapatalk

I was able after a full day of leaving the phone plugged in, to charge it up. Then I flashed the rom racer recovery, rebooted into recovery (new version), installed CM7, installed gapps, and voila! A working CM7 Atrix. thank you soo soo much guys.

Can't boot android/recovery
ClearFire said:
you should have left it alone at the M boot screen because it takes about 5-10min to boot after unlock and flash...
everything you do now will have to be through fastboot DO NOT SBF FLASH ANYTHING!!!
Go here to use Fastboot
then download the system.img and boot.img from here
use fastboot to push the boot.img and system.img to your phone
if it gets stuck at the M boot screen let it sit for at least 10min
EDIT: get Romracer recovery from here and push that through to your phone through fastboot
Click to expand...
Click to collapse
Please help!!!
The phone stuck in boot screen and overheat, then restart.
In recovery mode is just black screen.
Phone has Neutrino 2.6GT+ ROM whit Clemsyn's OC kernel 1.6GHz and it has unlocked bootloader.
Can I change the kernel without booting in os or recovery?
This problem show after I was extracting very big zip file and phone overheat.

firecode95 said:
Please help!!!
The phone stuck in boot screen and overheat, then restart.
In recovery mode is just black screen.
Phone has Neutrino 2.6GT+ ROM whit Clemsyn's OC kernel 1.6GHz and it has unlocked bootloader.
Can I change the kernel without booting in os or recovery?
This problem show after I was extracting very big zip file and phone overheat.
Click to expand...
Click to collapse
I am actually having this same problem.

My warranty-replacement (unrelated ear-piece failure) had 2.3.6 pre-installed. Thinking little of it, I unlocked the BL and rooted the phone as usual. After this, I tried to install a couple of the ROM's (Neutrino and Morrisoft) which I was most happy with on my previous Atrix.
After flashing either Neutrino or Morrislee's ROM, the phone hung on the M screen. Waiting approximately 30 minutes with no change, I pulled the battery.
When trying to enter recovery mode, the phone would state, "entering recovery mode..." Then go black.
I ended up using RSDLite and sbf flashing the stock 2.3.6 sbf file back to the phone. Then, I had to re-unlock the bootloader and re-root.
This never happened up to, and including 2.3.4, but did twice last night on these ROM's using 2.3.6, and I've flashed many ROM's and Kernels.
It happened to a lesser extent when trying to flash Clemsyn's stock enhanced kernel to the stock ROM, as I was able to enter recovery mode. Entering recovery mode, it would give errors: mounting cache, mounting system errors, and errors to accessing recovery and recovery log files.
Restore recovery would fail in this state, giving me the above errors as well.
Trying to mount the cache and system in recovery would fail. Trying to format cache and system then mounting these could occur temporarily, but would revert back to unmounted when a restore was attempted.
For these problems I pushed a recovery through fastboot.

Just one word: Fastboot. See if Fastboot works and flash everything from there. Or, as Alterna suggested, flash through RSDLite, but that a little dangerous and can brick your phone if you don't know what you are doing. Hope it helps.

Problem sloved!!!
Alterna said:
My warranty-replacement (unrelated ear-piece failure) had 2.3.6 pre-installed. Thinking little of it, I unlocked the BL and rooted the phone as usual. After this, I tried to install a couple of the ROM's (Neutrino and Morrisoft) which I was most happy with on my previous Atrix.
After flashing either Neutrino or Morrislee's ROM, the phone hung on the M screen. Waiting approximately 30 minutes with no change, I pulled the battery.
When trying to enter recovery mode, the phone would state, "entering recovery mode..." Then go black.
I ended up using RSDLite and sbf flashing the stock 2.3.6 sbf file back to the phone. Then, I had to re-unlock the bootloader and re-root.
This never happened up to, and including 2.3.4, but did twice last night on these ROM's using 2.3.6, and I've flashed many ROM's and Kernels.
It happened to a lesser extent when trying to flash Clemsyn's stock enhanced kernel to the stock ROM, as I was able to enter recovery mode. Entering recovery mode, it would give errors: mounting cache, mounting system errors, and errors to accessing recovery and recovery log files.
Restore recovery would fail in this state, giving me the above errors as well.
Trying to mount the cache and system in recovery would fail. Trying to format cache and system then mounting these could occur temporarily, but would revert back to unmounted when a restore was attempted.
For these problems I pushed a recovery through fastboot.
Click to expand...
Click to collapse
My problem like that and I use automated unlock tool to recover recovery, this recovery show some errors but I successfully flash cwm touch and reinstall Nutrition 2.6GT+

[Q] CM7 and Stock SBF Soft Brick

You're all going to have to forgive my idiocy, but I have a problem. I installed SM7 in my Atrix on an unlocked bootloader. I decided to go back to stock today and downloaded and flashed the SBF through RSLite. Reading now, you're not suppose to flash a previous sbf version if your bootloader is unlocked, but I didn't know that, at least that's what I'm assuming happenned. Now, the phone goes into a loop on the Motorola animation and does nothing. I can get into fastboot, recovery, RsLite mode and all of that, but the phone itself is in a loop. My questions is, what (If anything) can I do (eg. flash, fastboot etc) to go back and fix my problem? That battery already died once and I found a way to charge it so I can get back in those menus, but any tidbits would be majorly helpful.

madetoservehim said:
You're all going to have to forgive my idiocy, but I have a problem. I installed SM7 in my Atrix on an unlocked bootloader. I decided to go back to stock today and downloaded and flashed the SBF through RSLite. Reading now, you're not suppose to flash a previous sbf version if your bootloader is unlocked, but I didn't know that, at least that's what I'm assuming happenned. Now, the phone goes into a loop on the Motorola animation and does nothing. I can get into fastboot, recovery, RsLite mode and all of that, but the phone itself is in a loop. My questions is, what (If anything) can I do (eg. flash, fastboot etc) to go back and fix my problem? That battery already died once and I found a way to charge it so I can get back in those menus, but any tidbits would be majorly helpful.
Click to expand...
Click to collapse
If you can get into recovery, flash a fruitcake.
Make sure to data wipe & cache wipe beforehand.

Swiftks said:
If you can get into recovery, flash a fruitcake.
Make sure to data wipe & cache wipe beforehand.
Click to expand...
Click to collapse
I tried going into recovery mode; no dice. Droid error icon showed up. What's this I'm reading about flashing using fastboot? Can I download and flash a fastboot file so as to fix my phone?

Tried full wipe using fastboot? That pulled me out of boot loop once.
There are instructions and batch files to automate it somewhere in development forum.

if ur ATnT then screwed for very long time(till there is a fix)
if ur international/bell user (i am bell user and i messed up mine big time) then download the bootloader unlock SBF (IHOP_Bell) and flash it via rdslite and this will give u back the bootloader unlocked logo on ur boot screen.
if yes then ur lucky connect ur phone in fastboot mode and remove every **** out of it
fastboot erase boot
fastboot erase system
fastboot erase webtop
fastboot erase userdata
fastboot erase cache
then flash latest recovery via fastboot (do a search in forum ull find it)
boot into recovery and mount ur memory card as a usb mass storage device and copy the fruitcake or any other rom's zip file into it and flash it via recovery and u should be good to go.
since i am bell user i was able to flash back 2.2.2 french rom via SBF and RSD but after flashing cm7 i am not touching rsd or any sbf for that matter.
Press thanks if i helped you, and if i didnt then press it anyways

i would say do what swiftks says
flash a fruitcake use fastboot its your
only hope now also swiftks has guides
in his signature

Yer not hard bricked. You'll be fine. PM swift or myself if you can't figure it out.
Sent from my SAMSUNG-SGH-I777 using Tapatalk

[Q] Nexus 7 gets stuck booting. Tried reflashing stock OS multiple times.

I seem to have got myself into a bit of a pickle here.
I had a rooted N7 on 4.2.2. Tried to unroot (in lieu of going up to 4.3). Disaster struck! It wouldn't boot. It would just get stuck at the bootloader and go "Booting failed" or something similar.
So bother, I could get into the bootloader. So I tried to fastboot flash a stock image using this (http://forum.xda-developers.com/showthread.php?t=1907796) guide.
I got a bit further now, it would get the X loading screen but then no amount of waiting would have it boot.
So I tried factory reset from the recovery menu (the one with the Android and the red triangle).
No good, still did the same thing.
So I tried using Nexus Root Toolkit to flash stock + unroot from a soft-bricked/bootloop state. Nope! No good. Still does the same thing.
I've been through every combination of flashing, clearing, resetting but to no avail!
I've tried flashing CWM and TWRP but when I try to get into recovery mode, I just get the Google logo forever. This is a nightmare!
What's going on Have I managed to brick this thing...

evenstevens said:
I seem to have got myself into a bit of a pickle here.
I had a rooted N7 on 4.2.2. Tried to unroot (in lieu of going up to 4.3). Disaster struck! It wouldn't boot. It would just get stuck at the bootloader and go "Booting failed" or something similar.
So bother, I could get into the bootloader. So I tried to fastboot flash a stock image using this (http://forum.xda-developers.com/showthread.php?t=1907796) guide.
I got a bit further now, it would get the X loading screen but then no amount of waiting would have it boot.
So I tried factory reset from the recovery menu (the one with the Android and the red triangle).
No good, still did the same thing.
So I tried using Nexus Root Toolkit to flash stock + unroot from a soft-bricked/bootloop state. Nope! No good. Still does the same thing.
I've been through every combination of flashing, clearing, resetting but to no avail!
I've tried flashing CWM and TWRP but when I try to get into recovery mode, I just get the Google logo forever. This is a nightmare!
What's going on Have I managed to brick this thing...
Click to expand...
Click to collapse
Hey,
did you try doing all these manually :
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot -w update image.zip
PS : Edit these according to images you are trying to flash.
You mentioned you tried the guide but try this once again.
Unlock your bootloader / keep your bootloader unlocked while doing this.
If you want to you can even try running the .bat files and / or .sh files while in the bootloader.
If it still doesnt work , download the latest custom recovery and just try flashing it through
Code:
fastboot flash recovery recovery.img
Please mention the errors you have a bit more in detail during these steps !

Red Devil said:
Hey,
did you try doing all these manually :
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot -w update image.zip
PS : Edit these according to images you are trying to flash.
You mentioned you tried the guide but try this once again.
Unlock your bootloader / keep your bootloader unlocked while doing this.
If you want to you can even try running the .bat files and / or .sh files while in the bootloader.
If it still doesnt work , download the latest custom recovery and just try flashing it through
Code:
fastboot flash recovery recovery.img
Please mention the errors you have a bit more in detail during these steps !
Click to expand...
Click to collapse
Okay, I've managed to get TWRP up and running.
Now... how do I get a ROM onto there to try to flash? >_<
PS. I did all those commands manually many many times. It's got to a stage now where the X logo never actually comes up... Just the Google logo and the little padlock

evenstevens said:
Okay, I've managed to get TWRP up and running.
Now... how do I get a ROM onto there to try to flash? >_<
PS. I did all those commands manually many many times. It's got to a stage now where the X logo never actually comes up... Just the Google logo and the little padlock
Click to expand...
Click to collapse
Code:
adb sideload ROM.zip
in advance options > adb sideload
And about the ROM getting stuck at the Nexus boot animation , try getting a logcat.. maybe that will help. !

Red Devil said:
Code:
adb sideload ROM.zip
in advance options > adb sideload
And about the ROM getting stuck at the Nexus boot animation , try getting a logcat.. maybe that will help. !
Click to expand...
Click to collapse
Amazing. I actually managed to flash a copy of Cyanogen on there and it all booted perfectly.
Now I wonder if I can get it back to stock from here easily..
Thanks

evenstevens said:
Amazing. I actually managed to flash a copy of Cyanogen on there and it all booted perfectly.
Now I wonder if I can get it back to stock from here easily..
Thanks
Click to expand...
Click to collapse
You can ... just make sure you have downloaded the right factory images and flash the use the .bat / .sh to flash the images .. keep in mind that you will lose all your data including that on the internal sd. All the best

Red Devil said:
You can ... just make sure you have downloaded the right factory images and flash the use the .bat / .sh to flash the images .. keep in mind that you will lose all your data including that on the internal sd. All the best
Click to expand...
Click to collapse
So I tried to reflash a stock image... same issue again! Just freezing at the Google logo screen :/
Properly stumped as to why it's doing that. Maybe I'm stuck with Cyanogen...

evenstevens said:
So I tried to reflash a stock image... same issue again! Just freezing at the Google logo screen :/
Properly stumped as to why it's doing that. Maybe I'm stuck with Cyanogen...
Click to expand...
Click to collapse
So close...
Downloaded the new SDKs from Google and managed to actually flash and get into a stock version of Android... but it's constantly saying "Google keyboard has stopped working! Launcher has stopped working! etc" and it's practically useless
Gaaaaaaaaah

evenstevens said:
So close...
Downloaded the new SDKs from Google and managed to actually flash and get into a stock version of Android... but it's constantly saying "Google keyboard has stopped working! Launcher has stopped working! etc" and it's practically useless
Gaaaaaaaaah
Click to expand...
Click to collapse
Okay my solution to this:
Just keep flashing it with the flash-all.bat command until it just... worked.
Must've done it about 15 times.
Well that's that ordeal over.

[SOLVED]A500 Stuck on OS Load

Tired, Frustrated and Helpless I am at the moment.
My A500 was running OK with a Jelly Bean Rom( I forgot which one) with Skrilax_CZ's bootloader V8 and CWM v5.5.0.4.
I decided to try a different Jelly Bean Rom. Forgot to keep a CWM backup and my misery started.
Any rom and gaps will install fine. But after reboot it will be stuck on Cyogenmod or Android LOGO. I have tried several ROM. Exact same result.
This happened a few months back and after trying numerous times I gave up for that time.
But I need to get the tablet back to working.
So, since yesterday I have been trying my best to get this one to work.
Started with "[A500 & A501] Android 4.4.4 (OmniROM unofficial)".
According the installation note for that rom, I installed CWM 6.0.4.5 on secboot following the "[Recovery]CWM 6.0.4.5[UPDATED WITH INSTRUCTIONS][25/12/2013]" process.
Same exact situation. ROM will install then after reboot it will be stuck on OS load.
Tried with a few other older rom such as CM10-FLEX_V6Supercharged_Rev3.4. Same issue.
I even, Installed TWRP recovery openrecovery-twrp-2.6.3.0-a500 on secboot. Same Issue.
Then, Updated Skrilax_CZ's bootloader V8 to Skrilax_CZ's bootloader V9. Same Issue.
Weird thing is now when I go to "CWM 6.0.4.5" from "Skrilax_CZ's bootloader V9", CWM doesn't really let me do any task. Any menu I enter on CWM 6.0.4.5 it freezes and then reboots the tablet. But initially when I first installed CWM 6.0.4.5 on secboot it worked for the first few times.
I am a noob in this. I do not want to try anything else myself as I think I will eventually brick the device and there will be no coming back.
I have searched on XDA for this issue. Many other people have similar issue with a500 but I couldn't find any situation same as mine.
Need help from you awesome people.
I do not want to give up on this tablet. But without your HELP I am lost.
Please HELP.

Need help on this please.

iamtapu said:
Need help on this please.
Click to expand...
Click to collapse
Have you tried wiping the device in fastboot mode? If not, try that!
The partitions to wipe are system, data and cache. The command is "fastboot erase cache".

HenrikE said:
Have you tried wiping the device in fastboot mode? If not, try that!
The partitions to wipe are system, data and cache. The command is "fastboot erase cache".
Click to expand...
Click to collapse
tried that. same issue.
it keeps circling on cyanogenMOD logo.
Apologies for reply late. I was not well and could not attend to you reply.

anything else i can try?
Please help.

Hey Bro,
I had exactly the same issue. What I did to solve it, was to delete all folders manually. Boot to recovery and choose "mounts and storage". Unmount everything and then format every folder. Then Wipe everything again. Reboot and flash the image with recovery. Then everything should work fine.

Same here
I have had exactly the same issue and haven't yet found a decent solution.
Mine was stuck on the Acer logo with the stock ICS ROM.
I found my CPUID and SBK, the linux way.
I tried everything you tried, managed to have bootloader V9 installed, TWRP as a recovery (Thor's version), CWM as secboot.
I was able to wipe and flash with no errors, but it would always stuck on the Acer logo. No custom ROM would ever boot.
I will definitely try Unimatrix-zero's solution and tell you guys if it worked for me.
So far, the only thing that worked for me was to use an EUUs package (GEN1) to get back to stock HC 3.01.
As you may guess, there are no more OTA updates via wifi in 2014.
So I downloaded several update packages and so far I only managed to update to HC 3.2. I haven't yet found a working package for stock ICS.
Anyway, if Unimatrix-zero's workaround actually works, a custom ICS ROM will do the trick for me.

Unimatrix-zero said:
Hey Bro,
I had exactly the same issue. What I did to solve it, was to delete all folders manually. Boot to recovery and choose "mounts and storage". Unmount everything and then format every folder. Then Wipe everything again. Reboot and flash the image with recovery. Then everything should work fine.
Click to expand...
Click to collapse
Significant result but did not resolve the issue.
As you have mentioned, I have wiped off everything that i can find in the recovery menu.
rebooted after that to recovery and for the first time I could go to TWRP 2.7.
tried to install a custom rom. but same issue. Either it reboots when I tried omni rom 4.4.4 on the "booting from primary" menu or the CM blue circle going on forever, when I tried with a CM 10.1 rom.
and just now after trying the cm 10.1 rom it went back to the way it was before. now the TWRP 2.7 will just keep on blinking on the screen .
Help bro...help....

You can try the following fastboot commands to wipe your device:
fastboot erase boot
fastboot erase system
fastboot erase data
fastboot erase userdata
fastboot erase cache
And then flash the rom.

Unimatrix-zero said:
You can try the following fastboot commands to wipe your device:
fastboot erase boot
fastboot erase system
fastboot erase data
fastboot erase userdata
fastboot erase cache
And then flash the rom.
Click to expand...
Click to collapse
you are a GOD SEND for me.:highfive::highfive::highfive::victory::victory::victory::victory::victory:
Did the following as you mentioned.
Code:
fastboot erase boot
fastboot erase system
fastboot erase data
fastboot erase userdata
fastboot erase cache
boot recovery TWRP 2.7.
Installed OMNI 4.4 rom.
Installed GAPS.
NOW its booting to OMNI rom...
awesomeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee

Help help help with a hard bricked 6P

Hello guys,
I had my phone rooted with latest twrp. I flashed stock+ rom with Franco Kernel 25r and the A.R.I.S.E file for better sound. I've done the same set up minus the ARISE file and never had an issue.
well to my luck it kept bootlooping and I wasn't able to get back into my custom recovery. When I got home and got my hands on a pc I did a factory reset by manually flashing stock google img . I even used a couple tools since I ran out of ideas and still no luck.
I'm able to do anything through fastboot but I can't seem to get into my recovery at all.
Any ideas or tips of where I should go next?

Not a Hardbrick
As long as you can get to the bootloader mode, you haven't hard bricked your device. Hardbricking is a point where you cant boot your device and in to bootloader so there is no way to flash your device to a useable state.
Now as you can boot to the bootloader, just fastboot boot twrp.img and if you have a factory image zip, copy it in your device internal storage and flash it. Its that simple, provided you are already using an unencrypted boot.img in your current setup. Or else the next step is to flash an decrypted boot.img(you will loose all your userdata and internal storage data.). There are ways to mount the the encrypted filesystem if you are using a pin or password combo with your fingerprint. But without it its a bit more trickier so just for ease and if you dont have any inseparable data in your device now just flash a decrypted boot.img and then you can easily mount your internal storage to your pc and copy the factory image and the rest you already know..

At this point, I'd recommend a full reset.
Flash all the images in the latest Android M factory image (don't flash DP5 or similar N based ROMs): Recovery, Boot, System, Bootloader, Radio, everything.
Once you get stabilized and back into a working phone, then start rooting and messing around with kernels and what not.
To be completely honest, I've flashed nearly every ROM for the 6p, as well as my other Nexus devices, Galaxy phones, Sony phones, and no-name brands and none of those ultra modified kernels did any noticeable change. I tried the F2FS, NTFS, etc file system changes, tweaks to the governors and IO's, all of that, and found the stock kernel was the best. If a kernel with a different IO Scheduler worked even 10% better than the current implementation, and was just as stable, don't you think the Google/Android Engineers would've pushed that to live?
Currently running Pure Nexus July 23rd Update, everything stock that comes with it, Systemless Root/XPosed, and Viper4Android and have never had a performance or stability issue. I'd recommend you do the same.

leninmon said:
As long as you can get to the bootloader mode, you haven't hard bricked your device. Hardbricking is a point where you cant boot your device and in to bootloader so there is no way to flash your device to a useable state.
Now as you can boot to the bootloader, just fastboot boot twrp.img and if you have a factory image zip, copy it in your device internal storage and flash it. Its that simple, provided you are already using an unencrypted boot.img in your current setup. Or else the next step is to flash an decrypted boot.img(you will loose all your userdata and internal storage data.). There are ways to mount the the encrypted filesystem if you are using a pin or password combo with your fingerprint. But without it its a bit more trickier so just for ease and if you dont have any inseparable data in your device now just flash a decrypted boot.img and then you can easily mount your internal storage to your pc and copy the factory image and the rest you already know..
Click to expand...
Click to collapse
First of all thank you for the response.
I've tried flashing the most current twrp and it seems to go through fine on fast boot but when I actually try to get into recovery from the device it will boot loop and just keep doing that.
How can I get into the phones storage through fastboot?
Where can I get the factory zip?
it feels as if everything seems to go good through fastboot but when I actually try to boot the phone nothing seems to work.

Wiltron said:
At this point, I'd recommend a full reset.
Flash all the images in the latest Android M factory image (don't flash DP5 or similar N based ROMs): Recovery, Boot, System, Bootloader, Radio, everything.
Once you get stabilized and back into a working phone, then start rooting and messing around with kernels and what not.
To be completely honest, I've flashed nearly every ROM for the 6p, as well as my other Nexus devices, Galaxy phones, Sony phones, and no-name brands and none of those ultra modified kernels did any noticeable change. I tried the F2FS, NTFS, etc file system changes, tweaks to the governors and IO's, all of that, and found the stock kernel was the best. If a kernel with a different IO Scheduler worked even 10% better than the current implementation, and was just as stable, don't you think the Google/Android Engineers would've pushed that to live?
Currently running Pure Nexus July 23rd Update, everything stock that comes with it, Systemless Root/XPosed, and Viper4Android and have never had a performance or stability issue. I'd recommend you do the same.
Click to expand...
Click to collapse
Thanks for the reply.
I've done the manual flashing already and flashed everything single item the most current factory image. Everything seemed to have gone through okay but when I rebooted the phone it was back to 0.
I'm actually considering getting rid of the phone now since it is my daily =/

Format each partition before flashing.
fastboot format <partition>
wait until it's done, then
fastboot flash <partition> <image>
Some partitions can't be formatted, which there are ways around, but try this first.

Just get to bootloader mode and try booting the twrp.img
fastboot boot twrp.img
From the twrp ui, go to advanced wipe and format your storage.
To mount the internal storage on your PC, enable mtp from twrp screen.
If U are using a decrypted boot.img, it will easily mount ur internal storage. Or try flashing a decrypted boot.img
fastboot flash boot boot.img
Then try the above again..

leninmon said:
Just get to bootloader mode and try booting the twrp.img
fastboot boot twrp.img
From the twrp ui, go to advanced wipe and format your storage.
To mount the internal storage on your PC, enable mtp from twrp screen.
If U are using a decrypted boot.img, it will easily mount ur internal storage. Or try flashing a decrypted boot.img
fastboot flash boot boot.img
Then try the above again..
Click to expand...
Click to collapse
I flashed the twrp.img and it went through successfully at least on the computer it did but when the phone actually tries to get into recovery (twrp) it will start to boot loop and keep on doing that. I tried both an encrypted and decrypted boot img but it still made no difference.
I'm really going crazy over this

Wiltron said:
Format each partition before flashing.
fastboot format <partition>
wait until it's done, then
fastboot flash <partition> <image>
Some partitions can't be formatted, which there are ways around, but try this first.
Click to expand...
Click to collapse
I just tried this and had no luck =/....the phone wont get past the google boot screen

You need to explain more on what you actually tried here.
Just download the latest factory image and try to flash the latest bootloader using fastboot.
Then boot to the bootloader and try formating the device. Not wiping
Then you have to
fastboot boot twrp.img
I believe you have only tried wiping not formating. I faced similar issue before. But once I flashed a decrypted boot.img, it cleared the user data and then I was able to get to twrp.
Maybe your twrp img is corrupted if this didn't work.

leninmon said:
You need to explain more on what you actually tried here.
Just download the latest factory image and try to flash the latest bootloader using fastboot.
Then boot to the bootloader and try formating the device. Not wiping
Then you have to
fastboot boot twrp.img
I believe you have only tried wiping not formating. I faced similar issue before. But once I flashed a decrypted boot.img, it cleared the user data and then I was able to get to twrp.
Maybe your twrp img is corrupted if this didn't work.
Click to expand...
Click to collapse
i just flashed the latest bootloader from the most recent factory image and i did the command format user data and then tried the fastboot boot twrp and the phone will then try to get into recovery, the google logo comes up lasts a couple seconds and boot loops all over to where is says my phone cant be check for corruption
By now i should have been able to get into recovery and it wont go through

edgarted said:
i just flashed the latest bootloader from the most recent factory image and i did the command format user data and then tried the fastboot boot twrp and the phone will then try to get into recovery, the google logo comes up lasts a couple seconds and boot loops all over to where is says my phone cant be check for corruption
By now i should have been able to get into recovery and it wont go through
Click to expand...
Click to collapse
download a factory image and run the flash all file...... it should reboot your phone after 5 minutes and the issue should be resolved.. a hard brick would be a device that does nothing.... in this case i believe that you just didnt do something right.

Then download the latest factory image and extract it
fastboot flash radio.img
fastboot flash bootloader.img
& do a fastboot update the rest archive file as it is
This will flash the rom via fastboot& U don't have to rely on TWRP or CWM

i42o said:
download a factory image and run the flash all file...... it should reboot your phone after 5 minutes and the issue should be resolved.. a hard brick would be a device that does nothing.... in this case i believe that you just didnt do something right.
Click to expand...
Click to collapse
I was really really hoping this would help. I erase/formated everything before flashing anything. I then ran the flash-all file and it took a couple of minutes and it said finished on the command box and my phone restarted and went into the white google logo and rebooted again with a bootloop. I waited around 15 minutes hoping it would start but it didn't.
It honestly feels as if the phone is not processing the full commands but on the pc it seems to go through successfully
is there a way to force an install of a rom and see if maybe a dirty flash over the stock one will allow it to start up?

leninmon said:
Then download the latest factory image and extract it
fastboot flash radio.img
fastboot flash bootloader.img
& do a fastboot update the rest archive file as it is
This will flash the rom via fastboot& U don't have to rely on TWRP or CWM
Click to expand...
Click to collapse
i know how to flash the radio and bootloader but how do i do a fastboot update?

edgarted said:
i know how to flash the radio and bootloader but how do i do a fastboot update?
Click to expand...
Click to collapse
Just unzip the factory image and there U can see the flash shell script files too. Open them in a text editor & U could see the exact command. In a factory img, they also do the same thing via script files. Flashing the radio & bootloader & updating the rest archive

so this is what I've done
I've manually flashed every file needed for the factory image from google.
I also tried wugfresh tool kit which is great but didn't help me much. I flashed stock recovery and treid to boot into to and nothing. I flashed a customer recovery and nothing.
It always does the same thing
the screen that says my phone can't be checked for corruption and then the google sign comes up stays on for a couple seconds and then it bootloops to the can't be checked for corruption.
I try to get into recovery using fastboot commands and the phone does the same exact thing.
I was even able to lock and relock the bootloader and I was able to successfully flash everything at least that is what it showed on the computer
so ive read almost every thread that had to do with bricking and I feel like an expert now but im starting to think it is done =/

edgarted said:
so this is what I've done
I've manually flashed every file needed for the factory image from google.
I also tried wugfresh tool kit which is great but didn't help me much. I flashed stock recovery and treid to boot into to and nothing. I flashed a customer recovery and nothing.
It always does the same thing
the screen that says my phone can't be checked for corruption and then the google sign comes up stays on for a couple seconds and then it bootloops to the can't be checked for corruption.
I try to get into recovery using fastboot commands and the phone does the same exact thing.
I was even able to lock and relock the bootloader and I was able to successfully flash everything at least that is what it showed on the computer
so ive read almost every thread that had to do with bricking and I feel like an expert now but im starting to think it is done =/
Click to expand...
Click to collapse
Hey there. First off make sure to unlock again your bootloader. Then you may follow post # 10 of @Heisenberg 's flashing guide for our device.
First images to flash would be bootloader and radio. First flash bootloader, then make sure to issue the command adb reboot-bootloader. Then afterwards once the phone has rebooted back to bootloader, flash radio, then again do the adb reboot-bootloader again.
Once the phone is again back to bootloader flash the rest of the images except userdata. For the boot.img and recovery.img, flash the stock ones-don't use the decrypted boot.img and don't flash the twrp.img yet. Once all necessary images have been flashed issue the reboot-booloater command one more time, then on the bootloader screen choose the reboot option. Wait anywhere from 3-10 minutes for the phone to load. Let us know how it goes for you.

blitzkriegger said:
Hey there. First off make sure to unlock again your bootloader. Then you may follow post # 10 of @Heisenberg 's flashing guide for our device.
First images to flash would be bootloader and radio. First flash bootloader, then make sure to issue the command adb reboot-bootloader. Then afterwards once the phone has rebooted back to bootloader, flash radio, then again do the adb reboot-bootloader again.
Once the phone is again back to bootloader flash the rest of the images except userdata. For the boot.img and recovery.img, flash the stock ones-don't use the decrypted boot.img and don't flash the twrp.img yet. Once all necessary images have been flashed issue the reboot-booloater command one more time, then on the bootloader screen choose the reboot option. Wait anywhere from 3-10 minutes for the phone to load. Let us know how it goes for you.
Click to expand...
Click to collapse
Hello and thank you for helping.
I tried this method a couple of minutes ago. I flashed them this same way
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
It does the same exact thing it will try and restart the phone, the message that says it can't be checked for corruption the google logo comes up and it repeats it self non stop.
This is what doesn't make sense to me.
This is the file that I had flashed through twrp when it was working fine
Leviticus 1.3 - http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709

edgarted said:
Hello and thank you for helping.
I tried this method a couple of minutes ago. I flashed them this same way
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
It does the same exact thing it will try and restart the phone, the message that says it can't be checked for corruption the google logo comes up and it repeats it self non stop.
This is what doesn't make sense to me.
This is the file that I had flashed through twrp when it was working fine
Leviticus 1.3 - http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
Click to expand...
Click to collapse
This is weird. What version of the stock factory images did you flash? I've been using leviticus 1.3 since it came out and when i was still on stock rom. I switched over to cm builds and have been flashing every nightly since the 7/24th build, and in the process repeatesly reflashing the aound mod along, and i've had zero issues with the phone booting afterwards.