Develop Bugs

[Q] Help needed with failed Rooting and Custom ROM installation.

Hi all,
Happy new owner of European model HTC One M9. Now stuck with white HTC boot screen and problems to turn it off and random strange things... I'm lost and need help desperately...
Followed all guides in unlocking through htc-dev, installing TWRP 2.8.6.4 (beta).
Made a copy of Stock ROM through nandroid backup.
Flashed SuperSU (UPDATE-SuperSU-v2.46).
Advanced wipe (did I by any means delete internal system?)
When flashing Android_Revolution_HD-One_M9_4.1_eda061 everything went haywire. Got message at end stating that not all processes were finished. Something with regard to E:mount -0 bind '/data/media/'sdcard' process errored with error=255. Now lots of issues...
1) I couldn't get passed the white boot HTC One screen. Had to keep my finger on the power off for ages.
2) Bootloader shows software status: modifed. unlocked. s-on. I assume this is correct?
3) Going into recovery I get a strange HTC message: This build is for development purposes only (+ disclaimer not to distribute outside HTC bla bla bla). Is this normal?
4) when I try to restore my Stock ROM through fastboot I get to the setup of the device, but then FC of different programs. Back, home and settings button are non-responsive. Even entered a strange HTC error check. Upon rebooting, clearing cache and Dalvik, I am stuck at white boot screen. Now I can't even get into android OS setup anymore.
I have tried nr 4 above several times without success. I do get a strange "Invalid sparse file format at header magi
erasing 'system'..." is this normal? I get OK at end - but then still back to white boot screen.
Is my system totally buggered? What have I done wrong? I've flashed HTCs and Samsungs several years as an amateur but I feel like a total noob... Help? Anyone?

robned said:
Hi all,
Happy new owner of European model HTC One M9. Now stuck with white HTC boot screen and problems to turn it off and random strange things... I'm lost and need help desperately...
Followed all guides in unlocking through htc-dev, installing TWRP 2.8.6.4 (beta).
Made a copy of Stock ROM through nandroid backup.
Flashed SuperSU (UPDATE-SuperSU-v2.46).
Advanced wipe (did I by any means delete internal system?)
When flashing Android_Revolution_HD-One_M9_4.1_eda061 everything went haywire. Got message at end stating that not all processes were finished. Something with regard to E:mount -0 bind '/data/media/'sdcard' process errored with error=255. Now lots of issues...
1) I couldn't get passed the white boot HTC One screen. Had to keep my finger on the power off for ages.
2) Bootloader shows software status: modifed. unlocked. s-on. I assume this is correct?
3) Going into recovery I get a strange HTC message: This build is for development purposes only (+ disclaimer not to distribute outside HTC bla bla bla). Is this normal?
4) when I try to restore my Stock ROM through fastboot I get to the setup of the device, but then FC of different programs. Back, home and settings button are non-responsive. Even entered a strange HTC error check. Upon rebooting, clearing cache and Dalvik, I am stuck at white boot screen. Now I can't even get into android OS setup anymore.
I have tried nr 4 above several times without success. I do get a strange "Invalid sparse file format at header magi
erasing 'system'..." is this normal? I get OK at end - but then still back to white boot screen.
Is my system totally buggered? What have I done wrong? I've flashed HTCs and Samsungs several years as an amateur but I feel like a total noob... Help? Anyone?
Click to expand...
Click to collapse
the disclaimer is normal, and all that other stuff. before the fastboot restore did you flash stock recovery, I'm not sure but I think you have to, someone correct me if I'm wrong. pn advanced wipe you wipe cache-dalvic cache-system and data. nothing else before flashing a rom, if it has aroma installer select full wipe.

Aldo101t said:
the disclaimer is normal, and all that other stuff. before the fastboot restore did you flash stock recovery, I'm not sure but I think you have to, someone correct me if I'm wrong. pn advanced wipe you wipe cache-dalvic cache-system and data. nothing else before flashing a rom, if it has aroma installer select full wipe.
Click to expand...
Click to collapse
Hi,
Many thanks for your input. I tried to do a fastboot restore stock recovery (OTA 401.15) and afterwards a fastboot of my Stock ROM nandroid backup. It all seemed to work well (took longer than before - so I guess things got written to system) but I get foreclosures on several programs - most importantly Sense UI (even EasyAccessService and others less important as well). The SenseUI means I dont have any working buttons for apps, back and home. I wanted to see if I could delete the cache for SenseUI - but as soon as I try to go to apps, I get FC on App Helper. Same if I want to install anything.
- so I'm lost again... Any ideas?

robned said:
Hi,
Many thanks for your input. I tried to do a fastboot restore stock recovery (OTA 401.15) and afterwards a fastboot of my Stock ROM nandroid backup. It all seemed to work well (took longer than before - so I guess things got written to system) but I get foreclosures on several programs - most importantly Sense UI (even EasyAccessService and others less important as well). The SenseUI means I dont have any working buttons for apps, back and home. I wanted to see if I could delete the cache for SenseUI - but as soon as I try to go to apps, I get FC on App Helper. Same if I want to install anything.
- so I'm lost again... Any ideas?
Click to expand...
Click to collapse
I don't know. maybe your backup image was corrupted/

Aldo101t said:
I don't know. maybe your backup image was corrupted/
Click to expand...
Click to collapse
I actually made two backups and I tried the second one. I realized I didn't wipe cache and dalvik after installing stock recovery. I've flashed so many times tonight i'm going mad. Went in to stock recovery and wiped it, and upon reset and a lot of sweating it all works back to square 1.
Maybe I'll stick to stock... :silly:
Many thanks for the headsup on stock recovery. That's probably the only thing I hadn't tried and I wouldn't have thought of. :good::good::good:

http://forum.xda-developers.com/showthread.php?p=59896551
HTC ONE (M9) RUUs, OTAs, Stock TWRP Backups, Firmware & More Collection
---------- Post added at 01:13 PM ---------- Previous post was at 01:12 PM ----------
Rename it into 0PJAIMG.ZIP, put it on the ext sd card, reboot into 'download_mode', agree..

jauhien said:
http://forum.xda-developers.com/showthread.php?p=59896551
HTC ONE (M9) RUUs, OTAs, Stock TWRP Backups, Firmware & More Collection
---------- Post added at 01:13 PM ---------- Previous post was at 01:12 PM ----------
Rename it into 0PJAIMG.ZIP, put it on the ext sd card, reboot into 'download_mode', agree..
Click to expand...
Click to collapse
I have exactly the same issue, but can't get past the htc splash screen; any suggestions?

hellejoep said:
I have exactly the same issue, but can't get past the htc splash screen; any suggestions?
Click to expand...
Click to collapse
if you rename it OPJAIMG.zip before moving it to sdcard it will have two zips on it there(OPJAIMG.zip.zip)this will fail.

[Q] Help with downgrade and/or re-unlock, possible flash new OS

Hi, total noob to Android hacking and rooting here...
I'm in the US and have the HTC Desire 816 (710c) on Virgin Mobile. Really wishing I'd done better research about the Desire 816 and VM before buying this phone. It's a great phone except for the small HD. I didn't realize just how many headaches that small HD--and Virgin's tight-fisted grip regarding their unlock policy--would cause me!
Forgive the length of this, but I'm hoping more detail as to what I've done/tried will help find the right solution...
I was doing fine on KitKat and for some reason decided I wanted to upgrade to Lollipop--mistake number 1! I first installed the update over KitKat but had some issues. Nothing major, but I figured something was definitely wonky when I noticed the basic stock web browser was gone--not that I really use it, just wanted to test something with it. (I was having an issue in Habit Browser, didn't realize 'til later that it was because I had my download folder setting on external SD card. While that worked in KK, it didn't in LP.) So, I did a backup...or THOUGHT I did. HTC Backup app was supposed to have been backing up my phone every day to Drive...turns out, it wasn't, despite notifications that it was working. So, anyway... I went ahead and factory reset the phone and reinstalled Lollipop. UGH! An even bigger mistake. Over 6 GB of the HD gone, just from stock LP!
Then I thought maybe if I unlocked the phone, I could delete most of the junk, even still using the stock OS. I followed the directions on HTCDev and although the proper screen appeared on the phone and asked me if I wanted to unlock, and I replied yes, it didn't work at first. The phone rebooted and everything was the same. Reboot checker confirmed failure.
So, as I was ready to try to narrow down my list of previously installed apps to absolute essentials due to the reduced disk space, I thought to see if there was a a way to revert to KitKat. I followed the instructions here http://forum.xda-developers.com/desire-816/general/ruu-t2952058. I tried the RUU .exe first. It failed, telling me I needed to get the correct RUU and try again. However, HTC's website does NOT show any KK downloads for Virgin Mobile USA for this device. More on that in a moment...
I also tried the flashing via SD card method. It also failed. I thought, what the heck, I'll try steps 3 and 4 of the SD card method, flashing the stock recovery and lock the bootloader, even though I thought my device was locked. Well, I guess I didn't notice when I went into fastboot that the device indeed HAD at some point unlocked, after all.
After those steps, I now had the following show up:
*** Software Status: Modified ***
*** RELOCKED ***
SECURITY ALERT!
I tried flashing the ROM.zip from SD card method again. It failed spectacularly, saying something about about a large file (some of the text was beyond the edges of the screen, so I couldn't read all of it. There was also an instruction to press power to reboot. The phone went back into fast boot screen with red highlighted "!! Image Update FAIL !!" Mind you, this was with the SD card now removed. I did manage to get the phone to boot normally again, back to stock Lollipop.
Now I thought I would try flashing the WWE KK download from HTCDev. Well, I didn't get the large image fail message, but it did fail saying that it was not the right image.
I tried unlocking the phone again, via the instructions at HTCDev. Didn't work. Thought I would try the ROM.zip file from the thread here at XDA one more time. Same fail message as before, same behavior of phone getting stuck on flashboot screen with red error message on initial attempt to reboot the device. I do notice now that although phone status is still modified and relocked, the security alert message is gone.
Can anyone help? I just want KitKat back so I can reload all my previous apps! (or possibly a good KK equivalent non-stock ROM, once I get the phone unlocked again? I have no idea which one though, being a noob :/ )
Thanks!

witchywoman said:
So, as I was ready to try to narrow down my list of previously installed apps to absolute essentials due to the reduced disk space, I thought to see if there was a a way to revert to KitKat. I followed the instructions here http://forum.xda-developers.com/desire-816/general/ruu-t2952058. I tried the RUU .exe first. It failed, telling me I needed to get the correct RUU and try again. However, HTC's website does NOT show any KK downloads for Virgin Mobile USA for this device. More on that in a moment...
Click to expand...
Click to collapse
That ruu file should work it's the vm usa last kitkat version. You need to follow the directions unroot and relock phone. But depending on what you did to the phone that was non standard you might also need to wipe or format internal data before running the ruu.
I think you can:
1) unroot then boot into recovery(twrp)
2) wipe phone/format data.
3) Boot directly from twrp to bootloader so you can get to fastboot usb.
4) Flash stock recovery from your PC.
5) Relock bootloader then run the ruu.exe.
All the other stuff you did afterwards should not be necessary.

pcjunky: The phone is currently relocked. I'm not 100% sure about unrooted, but I think it is. Like I said, when it was unlocked before I didn't even realize it, and I didn't really do anything unusual with it. The phone still had stock Lollipop on it and I just changed some stock settings and preferences.
Also, as I said, I am a total noob. I don't know what you mean about twrp and booting into that to wipe the drive and then from that. I'm sure there is info about that on this site somewhere, but it might be quicker if you (or someone) could explain it briefly, or point me in the right direction.
Updating to answer my own question in this reply. You're telling me to use a custom recovery but I never installed one. So.... currently searching to see how to do that.

I don't know if it's worth you time to learn how to go back to Kitkat. There should be howto's in the general forum for most everything you need. But I think the free memory difference between Kitkat and Lollipop is almost 1GB. 4.04GB free versus 3.14GB free. If you make sure all your apps that support being moved to SD card are moved and your storage settings for supported items uses the SD card you might be able to save enough space to get by until you decide to switch phones.
Twrp is a custom recovery and backup/restore tool you can do a search to learn about it, but you might not need it. The HTC backup is OS specific and it only saves apps and data not system files. So your HTC backup under Kitkat won't restore over Lollipop. If you had installed Twrp and and made a backup of Kitkat before you installed Lollipop you could restore your kitkat backup over Lollipop.
If you still want to try to get back to kitkat you can try to reset your phone(In theory relocking your phone should do that but it wont hurt) before you run the ruu file.

pcjunky said:
I don't know if it's worth you time to learn how to go back to Kitkat. There should be howto's in the general forum for most everything you need. But I think the free memory difference between Kitkat and Lollipop is almost 1GB. 4.04GB free versus 3.14GB free.
Click to expand...
Click to collapse
Well, it's interesting to note that my phone used ~ 4.8 GB when it was new with KK installed. After the Lollipop upgrade, it was using well over 6 GB with just the stock OS, HTC apps and Virgin apps on it. Obviously, that was unacceptable, and it's what got me started on this whole quest. :silly: However, after flashing a custom recover image, rather than the stock recovery I used previously, the stock installation is using 4.97 GB, so I think I should be good to go with that.
If you make sure all your apps that support being moved to SD card are moved and your storage settings for supported items uses the SD card you might be able to save enough space to get by until you decide to switch phones.
Click to expand...
Click to collapse
I always have used the SD card as much as was supported. Switching phones is not an option for me as I have a rather limited income and the Desire was an investment. Thus another reason I embarked on trying to make these changes.
Twrp is a custom recovery and backup/restore tool you can do a search to learn about it, but you might not need it. The HTC backup is OS specific and it only saves apps and data not system files. So your HTC backup under Kitkat won't restore over Lollipop. If you had installed Twrp and and made a backup of Kitkat before you installed Lollipop you could restore your kitkat backup over Lollipop.
If you still want to try to get back to kitkat you can try to reset your phone(In theory relocking your phone should do that but it wont hurt) before you run the ruu file.
Click to expand...
Click to collapse
Well, as I said above, the stock/OME installation now, before uninstalling whatever junk it will let me, is using only 4.97 GB, so I should be fine with that.
Thanks for your efforts to help me out with this. :good:

I'm glad you got it to a workable point. It's possible to go back to Kitkat, but I personally wouldn't do it because it gives you better battery life.
From time to time you should check apps under settings and swipe left to see the apps on sd card. Sometimes new app updates will support being moved to sd card or an updated version of an app will need to be moved over to the sd card.

n00b here, Google isn't helping [SOLVED]

So I think I just bricked my phone... I tried to update my phone by reinstalling the stock recovery as per this video:
https://www.youtube.com/watch?v=PPPT5J8xG6w
After updating, the phone got stuck on the error screen. I was able to go back into recovery and go back to the home screen. After some googling, I found this:
http://forum.xda-developers.com/htc-one-m8/help/ota-lollipop-update-fails-red-triangle-t3015597
So I followed the steps and unrooted my phone and tried again. After the update, my phone won't go past the splash screen. I tried going into recovery and wiping the phone and rebooting, but it never gets past the splash screen. Help please!

CID-ROGER001
HBOOT-3.19.0.0000
RADIO-1.25.21331147A1.06G
OpenSDP-v48.2.2-00564-M8974_FO.1211
OS-4.20.631.3
eMMC-boot 2048MB

If you can flash an ruu then I would suggest flashing a stock latest Rogers ruu and starting from there

danial.aw said:
If you can flash an ruu then I would suggest flashing a stock latest Rogers ruu and starting from there
Click to expand...
Click to collapse
How would I flash and RUU? And where can I find a Rogers RUU? I can only find US/Europe RUUs. Please bear with me, I'm new to all this, but I'm trying to read as much as I can.

Bump
I'm trying method 2 as per SneakyGhost's FUU guide, but my computer is not detecting my phone despite it showing up in the "Safety Remove Hardware and Eject Media" tab (Android 1.0). In addition, the phone is showing FASTBOOT USB when connected. Stuck at a standstill right now.

Just an update on the situation, maybe this will help someone in the future - Progress so far - I was able to flash TWRP 2.8.7.0 as instructed a guide on the Android forums (I wish I could post links!).
Working on getting a rom to flash onto it now... I think I'm getting close...

ChickenOmelette said:
Just an update on the situation, maybe this will help someone in the future - Progress so far - I was able to flash TWRP 2.8.7.0 as instructed a guide on the Android forums (I wish I could post links!).
Working on getting a rom to flash onto it now... I think I'm getting close...
Click to expand...
Click to collapse
Same issue as you right now. Attempting to download a nandroid backup and then push it to my phone via fastboot and restore using TWRP and see if that works. Let me know how you make out.

essteekay said:
Same issue as you right now. Attempting to download a nandroid backup and then push it to my phone via fastboot and restore using TWRP and see if that works. Let me know how you make out.
Click to expand...
Click to collapse
Unfortunately, I didn't even have a backup - I'm having enough trouble getting the damn thing to boot!

ChickenOmelette said:
Unfortunately, I didn't even have a backup - I'm having enough trouble getting the damn thing to boot!
Click to expand...
Click to collapse
I managed to get a nandroid 4.4 backup onto my device and restored it. Worked and now my phone is back up and running and going through the rigmarole of updating apps and restoring my media/data backups.

essteekay said:
I managed to get a nandroid 4.4 backup onto my device and restored it. Worked and now my phone is back up and running and going through the rigmarole of updating apps and restoring my media/data backups.
Click to expand...
Click to collapse
Who is your carrier? And where did you get this Nandroid backup?

ChickenOmelette said:
Who is your carrier? And where did you get this Nandroid backup?
Click to expand...
Click to collapse
Fido, but my CID is Rogers001 (same network, probably that's why).
I used this thread as reference.
Downloaded the 3.34.631.4 - TWRP Recovery Nandroid from the CID Rogers001 part. Here's a direct link to the Nandroid backup.
From there, I unzipped the file and then transferred it to my M8 using my SD card (you can also push it straight to the device if using fastboot). I used the file manager in TWRP to move it into my backup folder (TWRP > Backup > Serial Number) in TWRP and then restored it.
Let me know if you've got any other questions. Seems to be working for me right now.

essteekay said:
Fido, but my CID is Rogers001 (same network, probably that's why).
I used this thread as reference.
Downloaded the 3.34.631.4 - TWRP Recovery Nandroid from the CID Rogers001 part. Here's a direct link to the Nandroid backup.
From there, I unzipped the file and then transferred it to my M8 using my SD card (you can also push it straight to the device if using fastboot). I used the file manager in TWRP to move it into my backup folder (TWRP > Backup > Serial Number) in TWRP and then restored it.
Let me know if you've got any other questions. Seems to be working for me right now.
Click to expand...
Click to collapse
Seems like amazing news. Hopefully this works. Apparently after this is done the OTA has to be applied? Is that your next step? Will you be flashing a rom after your firmware is updated?

ChickenOmelette said:
Seems like amazing news. Hopefully this works. Apparently after this is done the OTA has to be applied? Is that your next step? Will you be flashing a rom after your firmware is updated?
Click to expand...
Click to collapse
Right now, just going to keep things as is. I'm in a location with pretty spotty internet, so downloading 1+ GB ROMs isn't that easy. Probably just keep it so that I can use my device and then tinker on it when I'm back at home. I was notified that the Android 5.0.1 update is available for download, but right now I'm holding off doing anything else.
I'm just glad I got it back to working order now.

Here's what I got told to do:
If you want to properly update your firmware via FUU, you have to get to a stock rooted rom, stock recovery, s-off using Sunshine, apply the SuperCID mod, and then update your firmware. After that, reinstall TWRP and whatever modern rom.
Click to expand...
Click to collapse
After doing all this, I tried updating the phone from the Rogers pushed update. Unfortunately, that pushed me back to step 1, where the phone wouldn't boot up, so I had to start from scratch. Now that I have SuperCID, I'm going to try to apply a stock OTA from another carrier. Wish me luck!

So I started from scratch and the Rogers update just doesn't want to work. Every time it updates, it would show the red HTC error icon. I ended up taking the update off the phone's internal memory, as it could still boot, and pushing it via Method 2 seen in this guide as a reference. After pushing flashing (it took two times), the update finally installed, BUT it STILL GOT STUCK AT THE DAMN BOOT SCREEN.
At this point, I got frustrated and went straight to flashing a custom ROM as per the instructions given here. After long moments of waiting, it finally started installing. Very important to note, but I got stuck at the AROMA installer at the "Please Wait" screen. After pressing the power button and vol up, the got out of that screen and continued to install. Now I have a custom ROM, updated firmware and SENSE 7.0! Amazing. I hope that this post helps you in what you'll have to do next!
I blame Rogers for pushing out s***ty updates. But consider this problem SOLVED.

sd card and gapps6 problem on cm13

i was running cm12 with no probs on htc one m9
then by mistake i installed the new update and it was cm13.
after the phone rebooted i got google play error saying i need to update google play.
downloaded the latest gapps6 but when trying to install in recovery mode from internal phone memory (as sd card for some reason is not mounted anymore) it gives an error E: FAILED TO MAP
is there a way to go back to cm12 or fix these faults on cm13?

Linx78 said:
i was running cm12 with no probs on htc one m9
then by mistake i installed the new update and it was cm13.
after the phone rebooted i got google play error saying i need to update google play.
downloaded the latest gapps6 but when trying to install in recovery mode from internal phone memory (as sd card for some reason is not mounted anymore) it gives an error E: FAILED TO MAP
is there a way to go back to cm12 or fix these faults on cm13?
Click to expand...
Click to collapse
Install gapps immediately after rom installation, do not allow a full boot..
There is also an issue with the SD and the way it's read, this is an android M issue.

dladz said:
Install gapps immediately after rom installation, do not allow a full boot..
There is also an issue with the SD and the way it's read, this is an android M issue.
Click to expand...
Click to collapse
that's the problem, i didn't realize it's cm13 (thought it's another cm12 nightly) till rebooted the phone...
now it won't allow me to install anything at all giving that e: map... error.

Linx78 said:
that's the problem, i didn't realize it's cm13 (thought it's another cm12 nightly) till rebooted the phone...
now it won't allow me to install anything at all giving that e: map... error.
Click to expand...
Click to collapse
Ask in the forum mate, where u got the rom from.

dladz said:
Ask in the forum mate, where u got the rom from.
Click to expand...
Click to collapse
i'm really sorry if i posted in wrong place... (please direct me in the wright way)
the rom itself was downloaded automaticaly on the phone as an update and i pressed the option update, so the phone rebooted itself into recovery installed it and then i rebooted the phone myself not even looking what was installed... the rest you already know...

Linx78 said:
i'm really sorry if i posted in wrong place... (please direct me in the wright way)
the rom itself was downloaded automaticaly on the phone as an update and i pressed the option update, so the phone rebooted itself into recovery installed it and then i rebooted the phone myself not even looking what was installed... the rest you already know...
Click to expand...
Click to collapse
You will have to have downloaded the rom from xda surely? The Rom you downloaded initially I assume was cm 12.1, then you updated to cm 13, that thread is in the original android development section, I'm sure you can find your way there as you've been there before. The thread is now called cm13 I believe..
Also make sure you're on the latest TWRP recovery, I'm guessing you are but it'd be nice to be sure.
Might also be worth downloading G apps from the cm13 thread then rebooting to recovery, flashing the rom again and installing gapps whilst once complete, don't allow a reboot.
Wiping cache and dalvic will be fine, don't perform a full wipe just incase you can't install the rom again.
If you get stuck, you can push files to your phone using recovery and the push command..
Not 100% but I think storage works via TWRP, could be wrong about that and I've not tested it with cm13.
Either way you have a way back..
---------- Post added at 06:55 PM ---------- Previous post was at 06:55 PM ----------
Install from your internal memory not your SD card. Get the necessary files on your internal memory instead.

thank you very much, will try there.
yes, you are right, got rom from xda and i'm on latest recovery, but no matter what i do, even after wiping cashe still getting the bloody
E: failed to map file
Installation aborted

Linx78 said:
thank you very much, will try there.
yes, you are right, got rom from xda and i'm on latest recovery, but no matter what i do, even after wiping cashe still getting the bloody
E: failed to map file
Installation aborted
Click to expand...
Click to collapse
i can't post anything there... not enough posts...
did i brick my phone now? or is there a way to clean install? recovery mode won't work...

Linx78 said:
i can't post anything there... not enough posts...
did i brick my phone now? or is there a way to clean install? recovery mode won't work...
Click to expand...
Click to collapse
No it'a not bricked..
Are you installing from internal or external memory?
Connect your phone to your computer and go to recovery, then mount storage in recovery, copy G apps to internal memory.
Make more posts in here, i think you need ten

I tried it and found Android 6.0 is having issues with my PC, not recognizing my SD Card, not even the Internal SD !!! :S I know it is pure Super fast but i cant live without connecting my phone to PC.
Also I tried to flas Gapps just after installing MM (not reboot and with Aroma) and the installation freezes, so im stuck with pure Android no Google Apps, so I did return to Lollipop VipeOne 3.5.0 with a full backup made with TWRP.

Sorted. Avoid it til it'a fixed like me unless you want to be a Guinea pig.

dladz said:
Sorted. Avoid it til it'a fixed like me unless you want to be a Guinea pig.
Click to expand...
Click to collapse
sorry, i did copy everything onto internall memory, still no luck...
also the cm13 updated the recovery aswell, and i can't even do a factory reset...
please is there a way to go back to cm12.1?
once again i can't install anything in recovery mode.

Hang on you just said you reverted back to viper?
You should be able to install things now?
At this point I'm not too sure mate.. Sorry, perhaps install recovery again, might not be the right thing to do though, ask in the viper thread, you might have enough posts now.

dladz said:
Hang on you just said you reverted back to viper?
You should be able to install things now?
At this point I'm not too sure mate.. Sorry, perhaps install recovery again, might not be the right thing to do though, ask in the viper thread, you might have enough posts now.
Click to expand...
Click to collapse
that wasn't my post, some else posted here too...
i'm stuck, adb won't install anything too

LLegion said:
I tried it and found Android 6.0 is having issues with my PC, not recognizing my SD Card, not even the Internal SD !!! :S I know it is pure Super fast but i cant live without connecting my phone to PC.
Also I tried to flas Gapps just after installing MM (not reboot and with Aroma) and the installation freezes, so im stuck with pure Android no Google Apps, so I did return to Lollipop VipeOne 3.5.0 with a full backup made with TWRP.
Click to expand...
Click to collapse
i wanted to ask how to go back to cm12.1 from cm13?
i don't have any backups, nor my recovery is allowing to install anything as per post above...
adb method is not working either, just says waiting for the device when rebooted to download and nothing else.
also my firmware is 2.10..... is that an issue?

dladz said:
Hang on you just said you reverted back to viper?
You should be able to install things now?
At this point I'm not too sure mate.. Sorry, perhaps install recovery again, might not be the right thing to do though, ask in the viper thread, you might have enough posts now.
Click to expand...
Click to collapse
i also tried install recovery through adb, didn't work, just says waiting for the device and nothing happens

Linx78 said:
i also tried install recovery through adb, didn't work, just says waiting for the device and nothing happens
Click to expand...
Click to collapse
Nah i'm on 2.10 that's fine.
At this point it appear to be an issue with CM13 rather than anything else, I'm not up to speed with Android 6.0 so I think it would be best if you asked in the thread, you've made over 10 posts now so i'm assuming you can post there.
See what they say, let them know what you've done so far, someone will have either been through it or will know what to do.
Sorry i can't be of more help mate.
PS: Just thought of something, if you have connectivity to your computer / laptop, update your recovery if you haven't already, chances are it's an issue with cm13 but might be worth a try.

I had similar problem - Google Services crashing after unintentional update to CM13.
I realized that I need to install new GApps to fix the issue but GApps installation in recovery was constantly failing.
I used to have some recovery there, I even don't know which one, but during update to CM13 the recovery has been changed to some kind of CM recovery.
After installing TPRW recovery (ir forked for me from the TPRW Manager App from play store) I was able to install Nano GApps.
It solved the issue with Google Services crashing, now I got some Wizard crashing. The issue with crashing wizard is solved by going to privacy setting and allowing the wizard all rights. Later I realized that many other applications were crashing on start as well. I solved it for each of them by uninstalling and installing from Play Store again.

Boot loop at the final stap in rooting/unlocking bootloader

I have followed the instructions from Max at galaxynote4root http://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/5/. I got all the way through to the final step which is go into TWRP recovery, install the Oscar kernel and SuperSU zip files. I did not extract these files. Once I did that I got into a boot loop. I get by the Verizon logo to the UI and then it starts rebooting. Since there is not much discussion activity at Max's site, I thought if anyone here could help me.
After the UI comes up and before it goes in the boot loop, I get messages saying "Unfortunately xxxx has stopped." It varies about sometimes it is Knox. S Pen, Google Play, etc.

Try a factory reset by going into recovery and wiping delvik, cache, and data

MonstaSaleens said:
Try a factory reset by going into recovery and wiping delvik, cache, and data
Click to expand...
Click to collapse
That improved the situation. It is no longer in a constant boot loop, but it will still reboot when I manually start it or reboot it. When it starts it says "unfortunately KNOX has stopped running." It was doing that before, too.
I have confirmed I have root and and unlocked bootloader.

Redownload the rom.
Wipe data, cache, dalvic cache and system.
Install rom
Then kernel
And supersu.
Reboot and you should be fine
---------- Post added at 06:32 AM ---------- Previous post was at 06:30 AM ----------
If it continues I'd get a Odin flushable and use the pit file for repatriationing of the system. Maybe something went wrong..... Idk

Just a quick question: Did you use a micro SD card as part of the process? Did you remove this card after you were done unlocking the bootloader?
I know the process has you reformat the card, but I am asking if you have tried booting with the card removed.

codydixon said:
Redownload the rom.
Wipe data, cache, dalvic cache and system.
Install rom
Then kernel
And supersu.
Reboot and you should be fine
---------- Post added at 06:32 AM ---------- Previous post was at 06:30 AM ----------
If it continues I'd get a Odin flushable and use the pit file for repatriationing of the system. Maybe something went wrong..... Idk
Click to expand...
Click to collapse
Just followed your instructions. Everything was fine until I installed the kernel and supersu. I hate to be stuck when I'm so close.

ssj4gogeta2003 said:
Just a quick question: Did you use a micro SD card as part of the process? Did you remove this card after you were done unlocking the bootloader?
I know the process has you reformat the card, but I am asking if you have tried booting with the card removed.[/QUOTE
OK, tried that, and it worked--once. When I reboot with the SD card out, it either won't start or goes back into a boot loop.
Click to expand...
Click to collapse

Although it didn't seem very warm to me, I pulled the battery and let it sit for an hour. When I started it back up, everything was fine.
However, how do I re-enable the use of the SD card. I am afraid if I put in back in, I'll go back into the boot loop?

MrNetwork said:
Although it didn't seem very warm to me, I pulled the battery and let it sit for an hour. When I started it back up, everything was fine.
However, how do I re-enable the use of the SD card. I am afraid if I put in back in, I'll go back into the boot loop?
Click to expand...
Click to collapse
You'll need to connect the micro sd card itself to the computer and format it there. I have used Rufus (https://rufus.akeo.ie/) in the past to do this, but you may use any formatting program that you are familiar with. I recommend FAT32 as your format unless you move files over 4 GB to and from the card.

Thanks. I've rebooted it a couple of times after doing this, and it still is working! Now, should I install a 6.0 ROM or leave well enough alone?

MrNetwork said:
Thanks. I've rebooted it a couple of times after doing this, and it still is working! Now, should I install a 6.0 ROM or leave well enough alone?
Click to expand...
Click to collapse
It will depend on what version of firmware you are currently running. Most 6.0 ROMs require that you are using N910VVRU2CPD1 or N910VVRU2CPF3 for proper use. Please go into About Phone in Settings and check the Baseband Version field to make sure that you have one of those two in there. Flashing a 6.0 ROM with 5.1.1 firmware will cause issues with mobile signal and can make it impossible to use wifi.
If you find that you are running 5.1.1 firmware, then you have two choices: Flash a 5.1.1 ROM and call it a day or go through the process of unlocking the bootloader for 6.0.1 firmware. It's important to note that this will be a different process than the one you just went through. Be sure to research it thoroughly before attempting it. Hsbadr is a great developer and I believe he has a process for that, but it's been a while since I did it myself.

Back in a boot loop again. Once I've loaded the system image, I can reboot several times and everything is stable. As soon as I obtain root by installing the Oscar kernel and BetaSU, the phone becomes unstable. It might boot properly at first, but I still get "XXX has failed to start" where XXX can be any of a number of apps. If I let that go on without first shutting it down, it will go into a boot loop. However, if I do shut it down and restart it will also eventually go into a boot loop. Obviously this phone can't be my daily driver until I get it stable.
Before I install the rom each time, I wipe data, cache, dalvic cache and system.
I wonder if the kernel is the issue?

MrNetwork said:
Back in a boot loop again. Once I've loaded the system image, I can reboot several times and everything is stable. As soon as I obtain root by installing the Oscar kernel and BetaSU, the phone becomes unstable. It might boot properly at first, but I still get "XXX has failed to start" where XXX can be any of a number of apps. If I let that go on without first shutting it down, it will go into a boot loop. However, if I do shut it down and restart it will also eventually go into a boot loop. Obviously this phone can't be my daily driver until I get it stable.
Before I install the rom each time, I wipe data, cache, dalvic cache and system.
I wonder if the kernel is the issue?
Click to expand...
Click to collapse
I need more information to help you out. Please answer the following:
What baseband is your phone at right now? (Refer to my post above for where to find it.)
What ROM have you installed? (Be sure to include Android version as well as name)
Oscar Kernel is specifically for use with 6.0.1 Touchwiz ROMs. If you aren't on 6.0.1 and you haven't installed a Touchwiz-based ROM, then there will be issues.

ssj4gogeta2003 said:
I need more information to help you out. Please answer the following:
What baseband is your phone at right now? (Refer to my post above for where to find it.)
What ROM have you installed? (Be sure to include Android version as well as name)
Oscar Kernel is specifically for use with 6.0.1 Touchwiz ROMs. If you aren't on 6.0.1 and you haven't installed a Touchwiz-based ROM, then there will be issues.
Click to expand...
Click to collapse
Thank you. I finally figured it out. The problem was with oscar_kernel_v0.2. Instead I am using Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P. I'm going to stay with 5.1.1. The only trouble I am having now is with My Tracks not showing the map. I know it's been deprecated by Google, but it still is working on my LG G4. However, I'm not trying to hijack this thread. I'll start a new thread for this issue.
This is now the fastest phone I've used after deleting bloatware and running Nova Launcher.

Good to hear. Enjoy the phone.