Related
Several days ago I bought Rom Manager from the Play Store on my Nexus 7 (wi-fi). I decided to flash the cyanogen mod, thinking it would be a painless experience I decided not to back up or clear cache. Once the mod had downloaded I rebooted into cyanogen and ended up stuck on the boot screen indefinitely. From there I went into Rom manager's recovery mode and did a factory reset (this time I did make a backup). Finally I was in cyanogen, but I wanted to go back to stock. When I tried flashing it and unrooting my tablet using the Nexus Root Toolkit ([I can't post links) CyanogenMod stayed on my device. I also tried using Rom manager to flash the zip from the Google page, but that didn't work either. I am clueless of what to do and if anybody needs any additional information just say so.
Thanks in Advance!
Edit 1: everytime I try to install a stock ROM it says "installation aborted".
Edit 2: I tried using NRT again to flash stock and it had an interesting error message about losing recovery or something, this could be the root of the problem.
martin234 said:
Several days ago I bought Rom Manager from the Play Store on my Nexus 7 (wi-fi). I decided to flash the cyanogen mod, thinking it would be a painless experience I decided not to back up or clear cache. Once the mod had downloaded I rebooted into cyanogen and ended up stuck on the boot screen indefinitely. From there I went into Rom manager's recovery mode and did a factory reset (this time I did make a backup). Finally I was in cyanogen, but I wanted to go back to stock. When I tried flashing it and unrooting my tablet using the Nexus Root Toolkit ([I can't post links) CyanogenMod stayed on my device. I also tried using Rom manager to flash the zip from the Google page, but that didn't work either. I am clueless of what to do and if anybody needs any additional information just say so.
Thanks in Advance!
Click to expand...
Click to collapse
Read up on rooting and unrooting. These toolkits cause nothing but problems. They have threads dedicated to relocking and returning to stock. But you should know the methods behind toolkits. Just my opinion.
Sent from my Nexus 7 using xda premium
Seconded. For unlocking and rooting maybe, if you already know what you are doing, but there's no way I'd be flashing cyanogen or any other ROM with ROM manager.
Sent from my Nexus 7 using tapatalk 2. (Gone off HD...)
i agree, dont use apps to flash stuff. the apps themselves are what cause the issues. download the rom(or kernel) with the device, boot into your recovery, then flash.
---------- Post added at 06:39 PM ---------- Previous post was at 06:37 PM ----------
martin234 said:
Several days ago I bought Rom Manager from the Play Store on my Nexus 7 (wi-fi). I decided to flash the cyanogen mod, thinking it would be a painless experience I decided not to back up or clear cache. Once the mod had downloaded I rebooted into cyanogen and ended up stuck on the boot screen indefinitely. From there I went into Rom manager's recovery mode and did a factory reset (this time I did make a backup). Finally I was in cyanogen, but I wanted to go back to stock. When I tried flashing it and unrooting my tablet using the Nexus Root Toolkit ([I can't post links) CyanogenMod stayed on my device. I also tried using Rom manager to flash the zip from the Google page, but that didn't work either. I am clueless of what to do and if anybody needs any additional information just say so.
Thanks in Advance!
Click to expand...
Click to collapse
if you are clueless, then you should read and educate yourself first, before doing anything to your device to begin with. you especially dont have any business using a toolkit if you are clueless, you learn nothing using it.
simms22 said:
i agree, dont use apps to flash stuff. the apps themselves are what cause the issues. download the rom(or kernel) with the device, boot into your recovery, then flash.
---------- Post added at 06:39 PM ---------- Previous post was at 06:37 PM ----------
if you are clueless, then you should read and educate yourself first, before doing anything to your device to begin with. you especially dont have any business using a toolkit if you are clueless, you learn nothing using it.
Click to expand...
Click to collapse
I have educated myself around using NRT, but not around flashing ROMs. I tried entering recovery and flashing and that didn't work, instead it still rebooted to cyanogenmod.
Get the Google apps zip for 4.2.1. Go to recovery. Factory reset. Flash cyanogen and then gapps. Factory reset again. Fix permissions. Reboot.
Sent from my Nexus 7 using xda app-developers app
If you want to go back to stock then i have 2 methods for u.
1. If you know fastboot then download 4.2.1 image from google and flash it via fastboot.
2. if you dont know how to do that ten download toolkit andlet it do the magic for u.
I did the 2nd part and i am back to stock with no issues what so ever.
BlackFire27 said:
Get the Google apps zip for 4.2.1. Go to recovery. Factory reset. Flash cyanogen and then gapps. Factory reset again. Fix permissions. Reboot.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
That didn't work i'm still in cyanogen.
martin234 said:
That didn't work i'm still in cyanogen.
Click to expand...
Click to collapse
Well of course you are, that person gave terrible advice and didn't read the OP properly.
If you flash CyanogenMod then obviously you will still be using CyanogenMod.
You need to flash the stock images from Google. Google search is your friend.
Sent from my Galaxy Nexus using xda premium
nodstuff said:
Well of course you are, that person gave terrible advice and didn't read the OP properly.
If you flash CyanogenMod then obviously you will still be using CyanogenMod.
You need to flash the stock images from Google. Google search is your friend.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks, unfortunately every time I try to install the stock image I get an "installation aborted" error after "installing update".
I've tried reformatting everything and even thought it may be a problem with Cyanogen so installed some other ROM but it still doesn't work.
martin234 said:
Thanks, unfortunately every time I try to install the stock image I get an "installation aborted" error after "installing update".
I've tried reformatting everything and even thought it may be a problem with Cyanogen so installed some other ROM but it still doesn't work.
Click to expand...
Click to collapse
You can't install the factory images through recovery, you need to install them through fastboot.
Download the 4.2.1 images for nakasi (assuming you have the wifi only version, tilapia for the 3g version) and flash them via fast boot or the root toolkit if you have to.
That will solve any problems you have.
Sent from my Galaxy Nexus using xda premium
nodstuff said:
You can't install the factory images through recovery, you need to install them through fastboot.
Download the 4.2.1 images for nakasi (assuming you have the wifi only version, tilapia for the 3g version) and flash them via fast boot or the root toolkit if you have to.
That will solve any problems you have.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I cannot thank you enough, this actually fixed the problem.
Many of us are facing this problem where after flashing a 10.2 ROM and rebooting, the device is stuck at boot screen- the Samsung N7000 screen!
This is a strange problem which seems to be affecting only some n7000 handsets as others can keep flashing the ROMs without any issues...wiping, reflashing ROM, etc doesn't work!
I myself faced this problem on almost all custom CM 10.2 Roms and am sharing the solution which worked for me. At the onset, this solution was suggested to me by another member @Super Prince in one of my posts and it worked!!
1. Reboot into recovery
2. Flash the correct gapps once again
3. Reboot
The problem should be gone now and no more stuck-iness for you...
Sent from my GT-N7000 using XDA Premium 4 mobile app
I tried that, and it did not work.
I'm not using the regular Gapps package, but this one:
http://forum.xda-developers.com/showthread.php?t=2012857
What package do you use?
knedge said:
Many of us are facing this problem where after flashing a 10.2 ROM and rebooting, the device is stuck at boot screen- the Samsung N7000 screen!
This is a strange problem which seems to be affecting only some n7000 handsets as others can keep flashing the ROMs without any issues...wiping, reflashing ROM, etc doesn't work!
I myself faced this problem on almost all custom CM 10.2 Roms and am sharing the solution which worked for me. At the onset, this solution was suggested to me by another member @Super Prince in one of my posts and it worked!!
1. Reboot into recovery
2. Flash the correct gapps once again
3. Reboot
The problem should be gone now and no more stuck-iness for you...
Sent from my GT-N7000 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Really? I'll try it next time when I flash some CM based ROM and will get this problem.
I hope it is really the reason.
SirRhor said:
I tried that, and it did not work.
I'm not using the regular Gapps package, but this one:
http://forum.xda-developers.com/showthread.php?t=2012857
What package do you use?
Click to expand...
Click to collapse
Which CM version are you on? This method has worked for me every time on CM 10.2 roms and official CM 10.2 gapps (the one dated 13/08/2013)
I used to get stuck on the GT N7000 screen after every reboot and resorted to all sort of stuff like reflashing, formatting and stuff but to no avail.
The only solution that worked for me was re-flashing the gapps!
Maybe you should try once again with the official gapps..and post your results.
jakuburban said:
Really? I'll try it next time when I flash some CM based ROM and will get this problem.
I hope it is really the reason.
Click to expand...
Click to collapse
The 'Reason', my friend, remains a mystery...
This solution, though worked!
Experienced developers might like to comment on this as to what might be the reason
knedge said:
Which CM version are you on? This method has worked for me every time on CM 10.2 roms and official CM 10.2 gapps (the one dated 13/08/2013)
I used to get stuck on the GT N7000 screen after every reboot and resorted to all sort of stuff like reflashing, formatting and stuff but to no avail.
The only solution that worked for me was re-flashing the gapps!
Maybe you should try once again with the official gapps..and post your results.
Click to expand...
Click to collapse
I'm on Carbon, but I tried another CM based ROM as well and it did not work.
I will try it with the official Gapps and Slim Gapps then report back.
EDIT 1: Well. I tried the lastest Carbon nightly 10/17, with both Slim Gapps and normal regular Gapps and the same result, stuck on boot logo.
Both times I flashed a clean install. I'm out of options now.
EDIT 2: When I'm using a kernel from 4.3 and I'm on CWM trying to format Preload, I always get this message:
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
Error formatting /preload
Could that be a possible reason?, does anyone else have that same message?
No suggestions?
Am I'm stuck on 4.2?
Sent from my GT-N7000
It's the same for all on the new Cwm. Preload cannot be formatted in Cwm 10.2.
What happens when you clean install a rom without gapps. And boot it.?
nokiamodeln91 said:
It's the same for all on the new Cwm. Preload cannot be formatted in Cwm 10.2.
What happens when you clean install a rom without gapps. And boot it.?
Click to expand...
Click to collapse
I tried that last night actually, clean flash and no Gapps and the same result, stuck on boot screen.
What I've tried so far:
- Flashing different 4.3 ROMs with three different Gapps combinations.
- Flashing Carbon with no Gapps.
Thank you in advance for any ideas you can provide.
I have never encountered such an issue after a clean flash ever. So not sure what's going on there.
When a clean install, do you format system, data and cache and then install the new rom?
nokiamodeln91 said:
I have never encountered such an issue after a clean flash ever. So not sure what's going on there.
When a clean install, do you format system, data and cache and then install the new rom?
Click to expand...
Click to collapse
Yeah, what I do is to do a factory reset twice, then clear cache, then preload twice, data once, system twice and dalvik twice, and only then I flash the ROM and then Gapps.
I let it settle for one hour and then I start the configuration.
It is weird, because if I leave it to boot up normally for the first time, without opening any apps or configurations, it reboots normally. And only when I open Settings or an app, and then I reboot the phone, it gets stuck on the boot logo.
I've even tried to format the SD Card and no difference.
tried without the external SD card inserted?
nokiamodeln91 said:
tried without the external SD card inserted?
Click to expand...
Click to collapse
No, gonna try that tonight.
EDIT 1: Tried lastest Carbon nightly with NO Gapps and no External SD Card. Same crap.
EDIT 2: I found this thread and it basically says that I have to flash Stock, then root it and then do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2427569
Sent from my GT-N7000
SirRhor said:
No, gonna try that tonight.
EDIT 1: Tried lastest Carbon nightly with NO Gapps and no External SD Card. Same crap.
EDIT 2: I found this thread and it basically says that I have to flash Stock, then root it and then do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2427569
Sent from my GT-N7000
Click to expand...
Click to collapse
@SirRhor Please try anothjer work-around before you do anything else:
1. Do all the wipes from a safe kernel
2. Flash Rom (only rom and no gapps)
3. Reboot the system without gapps
4. Now, reboot into recovery (I prefer to leave the system for 10-15 minutes to settle down before rebooting)
5. Flash the correct gapps
6. Reboot and set up ur google account etc.Restore apps or whatever u need from the play store. Dabble with rom settings
7. Reboot!
Did it work now?
knedge said:
@SirRhor Please try anothjer work-around before you do anything else:
1. Do all the wipes from a safe kernel
2. Flash Rom (only rom and no gapps)
3. Reboot the system without gapps
4. Now, reboot into recovery (I prefer to leave the system for 10-15 minutes to settle down before rebooting)
5. Flash the correct gapps
6. Reboot and set up ur google account etc.Restore apps or whatever u need from the play store. Dabble with rom settings
7. Reboot!
Did it work now?
Click to expand...
Click to collapse
I haven't tried that yet, I'll do it tomorrow, but I really doubt it's going to work. I think this whole problem it's caused by errors located on some blocks of memory.
Sent from my GT-N7000
SirRhor said:
I haven't tried that yet, I'll do it tomorrow, but I really doubt it's going to work. I think this whole problem it's caused by errors located on some blocks of memory.
Sent from my GT-N7000
Click to expand...
Click to collapse
Well, can be!
Much abused handset...and much loved too!
But do give it a try!
SirRhor said:
No, gonna try that tonight.
EDIT 1: Tried lastest Carbon nightly with NO Gapps and no External SD Card. Same crap.
EDIT 2: I found this thread and it basically says that I have to flash Stock, then root it and then do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2427569
Sent from my GT-N7000
Click to expand...
Click to collapse
maybe your bootloader corrupted already. Reflash the bootloader only or whole stock rom using ODIN may help ..
I'm glad to inform you that I was able to solve my problem following this guide:
http://forum.xda-developers.com/showthread.php?t=2427569
But instead of flashing the Stock Rooted ROM using Odin, I just flashed it within Philz Recovery.
Right now I'm changing settings and restarting on Carbon 4.3, and so far I have not had any problems.
To anyone experiencing this, just read this thread so you will not waste your time trying ALL the bullcrap I did and instead just try the guide above.
Thank you for everyone who helped me out.
EDIT: Maybe the OP can change the title of this thread to "FIXED" or "SOLVED".
So...which Stock Rooted ROM using to flash?...
heihei123 said:
So...which Stock Rooted ROM using to flash?...
Click to expand...
Click to collapse
Actually, I found a better more permanent solution.
Follow this guide to check for errors on the different partitions:
http://forum.xda-developers.com/showthread.php?t=1396366
Let me know if it helps.
And to answer your question, I flashed a stock ROM from Hungary I think, no problems.
EDIT: Forgot to mention, instead of using the switches described on that guide, I used -f and -y at same time.
Sent from my GT-N7000
This is my first time installing a custom ROM. The phone has been rooted for some time now. I downloaded the AOSP ROM and GAPP 2012011, and flashed both packages. I did not use any third-party software to flash, and it appears the process was successful. When the phone reboots, it hangs at the point where the glowing X (like when my Nexus 7 starts up) appears, and nothing else happens.
Where did I go wrong?
Thanks to anyone who has a suggestion.
Maybe it was a corrupted download or you forgot to wipe
DaddyRick said:
This is my first time installing a custom ROM. The phone has been rooted for some time now. I downloaded the AOSP ROM and GAPP 2012011, and flashed both packages. I did not use any third-party software to flash, and it appears the process was successful. When the phone reboots, it hangs at the point where the glowing X (like when my Nexus 7 starts up) appears, and nothing else happens.
Where did I go wrong?
Thanks to anyone who has a suggestion.
Click to expand...
Click to collapse
Did you forget to wipe your data, cache, and dalvik cache before you flashed. Also are you sure your downloads are not corrupted :cyclops:
Assuming you mean this AOSP right http://forum.xda-developers.com/showthread.php?t=2081011&highlight=aosp
I would just use Supernexus 4.2.2 plus AOIP kernel whitescreen fix or if you want 4.1 use camcorys 4.1.2 build
Also what recovery and build are you using?
Sent from my SGH-T679 using XDA Premium 4 mobile app
mwhitt said:
Also what recovery and build are you using?
Sent from my SGH-T679 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't know what you mean by recovery. I used the file AOSP_ancora_tmo_tim1928-4.1.2-Build 6.
And no, I did not wipe the data before I installed the ROM the first time. However I have tried that, and then reinstalled the ROM. Same results.
I feel there is some app or more detailed procedure to installing this ROM, but I don't find specific instructions anyplace.
Thanks for the help I've gotten so far. Any other pointers or suggestions?
DaddyRick said:
I don't know what you mean by recovery. I used the file AOSP_ancora_tmo_tim1928-4.1.2-Build 6.
And no, I did not wipe the data before I installed the ROM the first time. However I have tried that, and then reinstalled the ROM. Same results.
I feel there is some app or more detailed procedure to installing this ROM, but I don't find specific instructions anyplace.
Thanks for the help I've gotten so far. Any other pointers or suggestions?
Click to expand...
Click to collapse
Are you using clockwork mod or twrp to flash the rom
Sent from my SGH-T679 using XDA Premium 4 mobile app
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.
So I tried to root and put on a custom recovery using the nexus root toolkit, since I am not very advanced at this type of stuff. But after pushing the root files to my phone from the TWRP recovery I got the message that the device is corrupt. I press the volume down button and power button to continue boot, but then the screen just goes black, and stays that way. Any advice?
pakman5391 said:
So I tried to root and put on a custom recovery using the nexus root toolkit, since I am not very advanced at this type of stuff. But after pushing the root files to my phone from the TWRP recovery I got the message that the device is corrupt. I press the volume down button and power button to continue boot, but then the screen just goes black, and stays that way. Any advice?
Click to expand...
Click to collapse
I got that message before. I fixed it by going back to stock, (the message will still appear even after going back to stock) then in the stock recovery factory reset the device. Then root as usual. I dont know how you're rooting but I flash the factory reset then install the custom reocery then flash super SU beta with a custom kernel and I havent had that pop up
xxxrichievxxx said:
I got that message before. I fixed it by going back to stock, (the message will still appear even after going back to stock) then in the stock recovery factory reset the device. Then root as usual. I dont know how you're rooting but I flash the factory reset then install the custom reocery then flash super SU beta with a custom kernel and I havent had that pop up
Click to expand...
Click to collapse
I think they key is the custom kernel. I was doing the stock kernel and kept getting the black screen. I will try doing a kernel that is friendly with 6.0.
Thanks for the advice, I will try to flash the stock recovery and factory reset the phone.
pakman5391 said:
I think they key is the custom kernel. I was doing the stock kernel and kept getting the black screen. I will try doing a kernel that is friendly with 6.0.
Thanks for the advice, I will try to flash the stock recovery and factory reset the phone.
Click to expand...
Click to collapse
Maybe i just downloaded it last night and started to tinker with it
Im using Benzocore at the moment, I was using Hells-kernel on Lolipop but it seems like Benzo works 100% with Marsh. I tried another kernel that says thatll work with marshmallow but it ended up in bootloop.
xxxrichievxxx said:
Maybe i just downloaded it last night and started to tinker with it
Im using Benzocore at the moment, I was using Hells-kernel on Lolipop but it seems like Benzo works 100% with Marsh. I tried another kernel that says thatll work with marshmallow but it ended up in bootloop.
Click to expand...
Click to collapse
Hellscore B7 works with MM 100%. Running it right now while rooted and using Layers. So I can vouch for Hells at least.
this fixes that message:
http://forum.xda-developers.com/nexus-6/development/kernel-stock-kernel-root-color-control-t3218958
kronikings said:
this fixes that message:
http://forum.xda-developers.com/nexus-6/development/kernel-stock-kernel-root-color-control-t3218958
Click to expand...
Click to collapse
That did make the message go away, and the black screen too! Thank you so much!
Now to re-try hellscore kernel.
Peylix said:
Hellscore B7 works with MM 100%. Running it right now while rooted and using Layers. So I can vouch for Hells at least.
Click to expand...
Click to collapse
If b7 works, then b8 should work no?
pakman5391 said:
If b7 works, then b8 should work no?
Click to expand...
Click to collapse
It appears so, it was posted just a few hours ago under their Nexus 6 section. I can't comment directly on B8 but I'm downloading to flash now.
Peylix said:
Hellscore B7 works with MM 100%. Running it right now while rooted and using Layers. So I can vouch for Hells at least.
Click to expand...
Click to collapse
Can you link me to the kernel version? I tried the latest one and that one bootlooped lol Thank you
xxxrichievxxx said:
Can you link me to the kernel version? I tried the latest one and that one bootlooped lol Thank you
Click to expand...
Click to collapse
Sure!
b7-m is here
b8-m is here
Also, on the b8. To not get the bootloop. Follow these instructions.
CHeers!