Develop Bugs

I'm a Beginner, Please Help with installing ICS leak?

Used to be an iphone addict, a pro at it xD Now I love android but I Have no clue on anything.
I found this post in developmental, but I can't post in it due to the "new member".
http://forum.xda-developers.com/showthread.php?t=1668476
It seem fairly easy to install since the files only contain 2 .exe , one for driver and one for install ics leak I guess?
I'm a noobie, I see some installin instruction but it's mainly for people who has already experience with android.
So anyone who has already installed this leak, can you give me the most dumbed down list of step possible? even like stuff how to enter a mode or button to press specifically.
does this need to be rooted to be install? thank you so much.

dustin4vn said:
Used to be an iphone addict, a pro at it xD Now I love android but I Have no clue on anything.
I found this post in developmental, but I can't post in it due to the "new member".
http://forum.xda-developers.com/showthread.php?t=1668476
It seem fairly easy to install since the files only contain 2 .exe , one for driver and one for install ics leak I guess?
I'm a noobie, I see some installin instruction but it's mainly for people who has already experience with android.
So anyone who has already installed this leak, can you give me the most dumbed down list of step possible? even like stuff how to enter a mode or button to press specifically.
does this need to be rooted to be install? thank you so much.
Click to expand...
Click to collapse
If I remember correctly, all you have to do is run the drivers and then put the phone in debugging mode. To do this, you go to applications, then development, then you'll be able to see it and click it. Then run the .exe and that's it.
Sent from my LG-P930 using xda app-developers app

The ICS leak is the easiest to install "ROM" ever. You don't even need root. Just run the exe file.
Now getting back from the leak because the battery only lasts 4 hours and the signal isn't as strong is the HARD part. And unfortunately, there is NO way to get completely stock again with the Nitro.
Even unbricking it leaves you with a rooted ROM that can't be updated through any official method (OTA nor LG Update Tool). Hell, I couldn't even find an unofficial way to update it after I unbricked it and stay stock. Only V10F is rootable, so nobody can get the IMG files off of V10i or V10j, so you get stuck at V10f if you want to stay stock. That's not necessarily a bad thing since I think V10j had issues with the baseband, but it might make it impossible to update to the stock ICS update when it comes out. Your only option at that point will be to either install CyanogenMOD or some other custom ROM. But if the official ICS ROM isn't rootable, you'll never be able to update to it.
---------- Post added at 10:13 AM ---------- Previous post was at 10:12 AM ----------
osmosizzz said:
If I remember correctly, all you have to do is run the drivers and then put the phone in debugging mode. To do this, you go to applications, then development, then you'll be able to see it and click it. Then run the .exe and that's it.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I don't think you even have to put it in debugging mode. Just let Windows install the drivers when you hook it up and run the exe file. It's an official updater so it shouldn't need debugging turned on. You do have to put it in PC Mode though.

And how do you put it in PC mode?
JINXR said:
The ICS leak is the easiest to install "ROM" ever. You don't even need root. Just run the exe file.
Now getting back from the leak because the battery only lasts 4 hours and the signal isn't as strong is the HARD part. And unfortunately, there is NO way to get completely stock again with the Nitro.
Even unbricking it leaves you with a rooted ROM that can't be updated through any official method (OTA nor LG Update Tool). Hell, I couldn't even find an unofficial way to update it after I unbricked it and stay stock. Only V10F is rootable, so nobody can get the IMG files off of V10i or V10j, so you get stuck at V10f if you want to stay stock. That's not necessarily a bad thing since I think V10j had issues with the baseband, but it might make it impossible to update to the stock ICS update when it comes out. Your only option at that point will be to either install CyanogenMOD or some other custom ROM. But if the official ICS ROM isn't rootable, you'll never be able to update to it.
---------- Post added at 10:13 AM ---------- Previous post was at 10:12 AM ----------
I don't think you even have to put it in debugging mode. Just let Windows install the drivers when you hook it up and run the exe file. It's an official updater so it shouldn't need debugging turned on. You do have to put it in PC Mode though.
Click to expand...
Click to collapse

When you plug it into your computer, it will pop up 4 options in your notification bar. PC mode is one of these options. It basically just allows LG software to see your phone.

Be careful. You are better off rooting your stock and installing cwm. Then you have options. With the leak, you are stuck unless you unbrick.
Sent from my LG-P930 using xda app-developers app

dnorthington is right on the money here. It will be a lot more work later if you choose the lazy route and use the 1-click installer right now. The other option is waiting for AT&T, but nobody wants that, right?
Sent from my LG-P930 using Tapatalk 2

[Q] IMEI says 0 on 4.4.1

Hey guys, I think I screwed up. I think that I lost my IMEI through flashing it and I didn't make a back up. It says 0 and only very few of the *# codes work, the *#7285# and #22745927 codes do absolutely nothing and the only one that I know of that works is *#*#4636#*#* which doesn't help me at all. Most programs that I use don't detect the phone correctly or my phones just downright wrecked. Example is DFS says CPS N/A in every section and Samsung MEID Repair says "Unhandled exception has occurred in your application" when I try to connect it to my phone.
I'm running CM11 4.4.1 and I had the problem when I was running a 4.3 ROM. Also I have data and I can make calls. Its just that I cant send MMS and I drop to edge over time and stay on edge until I restart.
Any help would be greatly appreciated. Everyone I call is saying it'll cost $65 - $75 IF they can even fix it.

Try to use nv writer to inject the imei.
http://forum.xda-developers.com/showthread.php?t=1804117

Note that if you reinject IMEI, it might screw up your network

audit13 said:
Try to use nv writer to inject the imei.
http://forum.xda-developers.com/showthread.php?t=1804117
Click to expand...
Click to collapse
I wish I could, When I try to use it, it says "Failed.. phone does not answer". Keep in mind that *#7284# doesnt do anything at all.

Did you know that you need to be completely stock in order to use the code?
Sent from my SAMSUNG-SGH-I747 using Tapatalk

pcshano said:
Did you know that you need to be completely stock in order to use the code?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I did not. That helps a LOT. Thank you so much. I havent tried going back yet, I'm gonna be more cautious about what i do now. Can I go back to stock from CM11 4.4.1 without screwing anything up? I keep seeing that you cant downgrade. Is that the case or is it just the case with official android roms?
Thank you so much, I feel like with your help I may be able to fix this. What im thinking that I have to do (I'll wait for your opinion) is that I should flash to stock, use the nv reader/writer, then ill be able to reroot it? When you say that it could screw up the network, what exactly do you mean?

chasetacos said:
I did not. That helps a LOT. Thank you so much. I havent tried going back yet, I'm gonna be more cautious about what i do now. Can I go back to stock from CM11 4.4.1 without screwing anything up? I keep seeing that you cant downgrade. Is that the case or is it just the case with official android roms?
Thank you so much, I feel like with your help I may be able to fix this. What im thinking that I have to do (I'll wait for your opinion) is that I should flash to stock, use the nv reader/writer, then ill be able to reroot it? When you say that it could screw up the network, what exactly do you mean?
Click to expand...
Click to collapse
I'm not sure what bootloader are you using
but IF your phone is fully unlocked, it doesn't matter, just flash 4.3 Stock and you're good to go
check out this post if you need help getting back to stock http://forum.xda-developers.com/showthread.php?t=2658486
the reason why you see people keep saying you can't "Downgrade" is mostly due to the bootloader you have, and it only apply to if and only if you're downgrading from MJB bootloader to a older version of Touchwiz (ie. Touchwiz 4.3 which will obviously come with MJB, thus you can't downgrade to 4.2 or 4.1 versions of touchwiz), not AOSP. if you're on AOSP in which CM is one, yes you can go from one AOSP to another, but no one does it because most of the time newer > older =D

pcshano said:
I'm not sure what bootloader are you using
but IF your phone is fully unlocked, it doesn't matter, just flash 4.3 Stock and you're good to go
check out this post if you need help getting back to stock http://forum.xda-developers.com/showthread.php?t=2658486
the reason why you see people keep saying you can't "Downgrade" is mostly due to the bootloader you have, and it only apply to if and only if you're downgrading from MJB bootloader to a older version of Touchwiz (ie. Touchwiz 4.3 which will obviously come with MJB, thus you can't downgrade to 4.2 or 4.1 versions of touchwiz), not AOSP. if you're on AOSP in which CM is one, yes you can go from one AOSP to another, but no one does it because most of the time newer > older =D
Click to expand...
Click to collapse
Cool. Im using CWM 6.0.4.3. Youre saying flash back to stock, then use the codes and the NV reader/writer? Also, when using the ZIP. am I using this through CWM "install zip"?

chasetacos said:
Cool. Im using CWM 6.0.4.3. Youre saying flash back to stock, then use the codes and the NV reader/writer? Also, when using the ZIP. am I using this through CWM "install zip"?
Click to expand...
Click to collapse
Yes.
but again you might want to update it to latest version since according to this http://forum.xda-developers.com/showthread.php?t=2658486, he mentioned version 6.0.4.5 and 6.0.4.7 though he didn't say if it's necessary to be but to be safe, you should so that you won't run into any issues.
though again, let me warn you, Reinjecting your IMEI, will work, BUT at the same time, it might screw up with your broadband
I experienced it once with one of my S3 and it stuck on either E or G network.. and I had to fix it by copy my efs folder to that phone in order to fix(and unless you have a good friend with S3 phone with same model, or own more than 1 S3, you won't be able to do it since nobody want to share, apply to me as well)

pcshano said:
Yes.
but again you might want to update it to latest version since according to this http://forum.xda-developers.com/showthread.php?t=2658486, he mentioned version 6.0.4.5 and 6.0.4.7 though he didn't say if it's necessary to be but to be safe, you should so that you won't run into any issues.
Click to expand...
Click to collapse
Cool. I Will do this and I will keep you updated. Itll be just a few moments before I complete the process

pcshano said:
Yes.
but again you might want to update it to latest version since according to this http://forum.xda-developers.com/showthread.php?t=2658486, he mentioned version 6.0.4.5 and 6.0.4.7 though he didn't say if it's necessary to be but to be safe, you should so that you won't run into any issues.
though again, let me warn you, Reinjecting your IMEI, will work, BUT at the same time, it might screw up with your broadband
I experienced it once with one of my S3 and it stuck on either E or G network.. and I had to fix it by copy my efs folder to that phone in order to fix(and unless you have a good friend with S3 phone with same model, or own more than 1 S3, you won't be able to do it since nobody want to share, apply to me as well)
Click to expand...
Click to collapse
So when I try to flash the stock I get an error status 7. Any advice?

chasetacos said:
So when I try to flash the stock I get an error status 7. Any advice?
Click to expand...
Click to collapse
funny a lot of people who use CWM got this error when trying to get back to stock lol
try TWRP.. it should definitely fix it

Cool. It may not be till tonight or tomorrow till I respond, I'm about to have a project m competition. I'll let you know how it goes as soon as I get a chance.

pcshano said:
funny a lot of people who use CWM got this error when trying to get back to stock lol
try TWRP.. it should definitely fix it
Click to expand...
Click to collapse
So now that Ive restored to stock, I have a transparent window with yellow text in it. it reads a bunch of info on the phone. It also said that it was in factory mode?

pcshano said:
funny a lot of people who use CWM got this error when trying to get back to stock lol
try TWRP.. it should definitely fix it
Click to expand...
Click to collapse
So despite being stuck in factory mode I was able to write the NV and luckily I dont have any new network problems as far as I know. However my IMEI now says / 00 and in the phone info it says "unknown"

So this is my progress so far. I have made connection with the NV items reader and I have saved the NV file. when i rewrote it i noticed that my imei is / 00 and it says unknown in the phone info. I have my imei and my converted imei and i was going to insert it into line 00550 but that line says "00550 (0x0226) - Inactive item". Factory mode is still on, I have edited the text files for both factory mode and keystr from ON to OFF and back again rebooting my phone each time and getting no result.
So im stuck in factory mode with / 00 imei. I can however make connection with programs now, I feel like im moving forward.
I feel like it may be worth noting that ive never ever seen a nv_data.bin in my phone....

chasetacos said:
So this is my progress so far. I have made connection with the NV items reader and I have saved the NV file. when i rewrote it i noticed that my imei is / 00 and it says unknown in the phone info. I have my imei and my converted imei and i was going to insert it into line 00550 but that line says "00550 (0x0226) - Inactive item". Factory mode is still on, I have edited the text files for both factory mode and keystr from ON to OFF and back again rebooting my phone each time and getting no result.
So im stuck in factory mode with / 00 imei. I can however make connection with programs now, I feel like im moving forward.
I feel like it may be worth noting that ive never ever seen a nv_data.bin in my phone....
Click to expand...
Click to collapse
make sure that you take your SIM out before injecting imei... then try again
and nv_data.bin is in your efs folder which you can only see it if you have some sort of root explorer

pcshano said:
make sure that you take your SIM out before injecting imei... then try again
and nv_data.bin is in your efs folder which you can only see it if you have some sort of root explorer
Click to expand...
Click to collapse
Still nothing, im getting the same result. This Nv data bin file is not in there. i mean, unless i dont know where to look, but ive checked the whole EFS folder and its not in there...

Hi try flash UCUEMJB 4.3 stock rom via odin .. I have same problem and the stock ROM fix my problem
Sent from my GT-P5113 using XDA Premium 4 mobile app
---------- Post added at 06:24 PM ---------- Previous post was at 06:06 PM ----------
I fix mine with this .....
Ok... I hated to see the posts about the tar file bricking a couple of phones. I had taken it down so not to brick anyone else's phone. But with over 400 downloads and only 2 reports I feel that it was fine, but in either case I have redone it. I have flashed it many many time now and my phone is fine.
Please only use Odin 3.0.7 http://forum.xda-developers.com/showthread.php?t=1722686
Make sure Auto Reboot and Re-Partition are checked. Uncheck F. Reset Time and anything else that might be checked.
Check and load the file in the PDA slot.
Start Flash and wait till it the phone reboots.
I747UCUEMJB 4.3 Odin flashable tar.
http://www.androidfilehost.com/?fid=23329332407590581
Sent from my GT-P5113 using XDA Premium 4 mobile app

elcocolo50 said:
Hi try flash UCUEMJB 4.3 stock rom via odin .. I have same problem and the stock ROM fix my problem
Sent from my GT-P5113 using XDA Premium 4 mobile app
---------- Post added at 06:24 PM ---------- Previous post was at 06:06 PM ----------
I fix mine with this .....
Ok... I hated to see the posts about the tar file bricking a couple of phones. I had taken it down so not to brick anyone else's phone. But with over 400 downloads and only 2 reports I feel that it was fine, but in either case I have redone it. I have flashed it many many time now and my phone is fine.
Please only use Odin 3.0.7 http://forum.xda-developers.com/showthread.php?t=1722686
Make sure Auto Reboot and Re-Partition are checked. Uncheck F. Reset Time and anything else that might be checked.
Check and load the file in the PDA slot.
Start Flash and wait till it the phone reboots.
I747UCUEMJB 4.3 Odin flashable tar.
http://www.androidfilehost.com/?fid=23329332407590581
Sent from my GT-P5113 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunately that did nothing . I might just have to cry about it

Constant crashing

Hi all,
My phone keeps crashing and rebooting. Every time it comes back, it needs to resign on to wifi (retype in WPA), downloads a file calle "how-to" (which I can't find), and have to resign into Google. By the time it accomplishes all this, it crashes and restarts the whole shabang again. Tried recovery mode and clearing, no difference.

It might be worth mentioning it boots into extreme power saving mode too.

Is the phone modified (unlocked bootloader, root, custom ROM, etc.) or is it stock?
On the bootloader screen, what is the OS number?

redpoint73 said:
Is the phone modified (unlocked bootloader, root, custom ROM, etc.) or is it stock?
On the bootloader screen, what is the OS number?
Click to expand...
Click to collapse
It is stock. Tried to root it but it didn't take. Don't know which version as it is stuck in a loop currently. It seems to me this is a hardware problem though.

carljames0603 said:
It is stock. Tried to root it but it didn't take.
Click to expand...
Click to collapse
Need more details on that. How did you try to root, what exact steps did you perform, where did you get stuck and why, etc.
Always provide as many details as possible when asking for help and answering our questions.
carljames0603 said:
Don't know which version as it is stuck in a loop currently.
Click to expand...
Click to collapse
If its stuck in a loop (rebooting) then simply hold volume down, and don't let go. The next time it reboots, it will go to bootloader (then you can let go of vol down).
From there, tell us what OS number it says on the bootloader screen, near the top.
carljames0603 said:
It seems to me this is a hardware problem though.
Click to expand...
Click to collapse
What makes you think that? You haven't provided any details or evidence that would support the statement.
Its possible its a hardware issue. But based on what little you've said, its perfectly possible its a software issue. So be optimistic, unless you have specific evidence to think otherwise.

When it gets stuck in a loop, holding down VOL DOWN does nothing. The only way to get to the boot loader is to go to SETTINGS>POWER OPTIONS and disable fast boot. Then hopefully it shuts down fully and doesn't crash and reboot in the process. Pain in the ass.
The OS is 3.28.605.4

carljames0603 said:
When it gets stuck in a loop, holding down VOL DOWN does nothing. The only way to get to the boot loader is to go to SETTINGS>POWER OPTIONS and disable fast boot. Then hopefully it shuts down fully and doesn't crash and reboot in the process.
Click to expand...
Click to collapse
This is false. That setting only applies when the phone is powered off; since in that condition the phone was not truly powered off (just a deep sleep mode). A reboot is always a reboot.
I know this for fact, because back when I was on KitKat (and on past devices - the "fast boot" power setting was removed after KitKat) I never ever bothered to turn off the "fast boot" feature. I was able to get to bootloader whenever I wanted by rebooting (not power off) and then holding vol down. Worked every time.
Hold down the vol down button during the next reboot cycle, and it will go to bootloader. It may be that some set of conditions is just making you think what you posted is true. But try not to get the "timing" right. Just hold the vol down, and don't let go. It will go to bootloader, if its actually bootlooping.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
Also, you never answered my previous question, how far you got with the rooting, and what steps you performed exactly. Is the bootloader LOCKED, UNLOCKED, or RELOCKED?
When you do go to bootloader, it stays there (doesn't reboot)?

redpoint73 said:
This is false. That setting only applies when the phone is powered off; since in that condition the phone was not truly powered off (just a deep sleep mode). A reboot is always a reboot.
I know this for fact, because back when I was on KitKat (and on past devices - the "fast boot" power setting was removed after KitKat) I never ever bothered to turn off the "fast boot" feature. I was able to get to bootloader whenever I wanted by rebooting (not power off) and then holding vol down. Worked every time.
Hold down the vol down button during the next reboot cycle, and it will go to bootloader. It may be that some set of conditions is just making you think what you posted is true. But try not to get the "timing" right. Just hold the vol down, and don't let go. It will go to bootloader, if its actually bootlooping.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
Also, you never answered my previous question, how far you got with the rooting, and what steps you performed exactly. Is the bootloader LOCKED, UNLOCKED, or RELOCKED?
When you do go to bootloader, it stays there (doesn't reboot)?
Click to expand...
Click to collapse
It's not false, because that's what is happening. I hold down the button the whole time and it will go through the whole process and never go to the bootloader.
Either way, sorry I missed the question. Not very far, it crashes before to long. I tried downloading the SU app as prescribed in the site, but can't get it on the device itself.
The bootloader is locked, and it stays there until I push it to reboot.

carljames0603 said:
Either way, sorry I missed the question. Not very far, it crashes before to long. I tried downloading the SU app as prescribed in the site, but can't get it on the device itself.
The bootloader is locked.
Click to expand...
Click to collapse
Nowhere will you find a guide for this device, that tells you to use an SU app. That isn't the proper way to root this phone. You need to flash SU/SuperSU, and you need custom recovery to do that. And for that, you need an unlocked bootloader, which for your device (Verizon version M8) requires s-off.
Or there is the kingroot method, which has some mixed results.
In any case, locked bootloader is good. Since my recommendation would be to RUU to full stock image, and see if that fixes your reboot problem. If not, then you are probably correct that its a hardware issue.
You can get the RUUs from here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Not only will this get you on a full stock image (which if its a software problem, will fix it) but you can get to a more updated version (yours is really outdated).
You may need to find and flash the Marshmallow 6.21.605.3 firmware (not sure where to find that, offhand), before you can falsh the Marshmallow RUU. But otherwise, you can certainly flash the Lollipop RUU.
---------- Post added at 02:26 PM ---------- Previous post was at 02:22 PM ----------
carljames0603 said:
It's not false, because that's what is happening. I hold down the button the whole time and it will go through the whole process and never go to the bootloader.
Click to expand...
Click to collapse
Maybe its not actually rebooting, then; but doing something like just rebooting the Android shell? But that would be interesting, and not something I've seen before.

redpoint73 said:
Nowhere will you find a guide for this device, that tells you to use an SU app. That isn't the proper way to root this phone. You need to flash SU/SuperSU, and you need custom recovery to do that. And for that, you need an unlocked bootloader, which for your device (Verizon version M8) requires s-off.
Or there is the kingroot method, which has some mixed results.
In any case, locked bootloader is good. Since my recommendation would be to RUU to full stock image, and see if that fixes your reboot problem. If not, then you are probably correct that its a hardware issue.
You can get the RUUs from here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Not only will this get you on a full stock image (which if its a software problem, will fix it) but you can get to a more updated version (yours is really outdated).
You may need to find and flash the Marshmallow 6.21.605.3 firmware (not sure where to find that, offhand), before you can falsh the Marshmallow RUU. But otherwise, you can certainly flash the Lollipop RUU.
---------- Post added at 02:26 PM ---------- Previous post was at 02:22 PM ----------
Maybe its not actually rebooting, then; but doing something like just rebooting the Android shell? But that would be interesting, and not something I've seen before.
Click to expand...
Click to collapse
Sorry, app as the wrong word. I tried several different methods but none was an actual app. I did try using something that came from the HTC website (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4), but the phone would crash every time. It said to use the program while it was on bootloader, but I don't think I did it write because it still couldn't find the phone via USB.

carljames0603 said:
Sorry, app as the wrong word. I tried several different methods but none was an actual app. I did try using something that came from the HTC website (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4), but the phone would crash every time. It said to use the program while it was on bootloader, but I don't think I did it write because it still couldn't find the phone via USB.
Click to expand...
Click to collapse
did you read the post you quoted ?
redpoint73 said clearly what you need and where to find
you used a different RUU and it will not accepted by your device ( in red above )

carljames0603 said:
Sorry, app as the wrong word. I tried several different methods but none was an actual app.
Click to expand...
Click to collapse
Complete lack of correct terminology or any meaningful details, means you haven't provided any actual information on what "methods" you tried to root. You say you tried several different methods, but don't provide any information on what those were. You say an SU app, when you don't mean an SU app (SU zip? SuperSU zip? - which is not the same).
Further, you posted that you "downloading the SU app as prescribed in the site". What website? How are we supposed to have any idea what you are talking about? Please understand, that your posts are vague to the point, that they don't actually provide any real information.
If you want proper help on this website, in general, you need to be specific, provide proper details, and user the right terminology.
carljames0603 said:
(RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4), but the phone would crash every time. It said to use the program while it was on bootloader, but I don't think I did it write because it still couldn't find the phone via USB.
Click to expand...
Click to collapse
As the previous response indicated, this isn't the right RUU for your device. Why would you try to use this? Especially since the proper RUU for your Verizon version M8 was already provided in one of my previous responses? It seems you are just guessing around for solutions (which is a recipe for disaster). You have no reason to think the RUU you listed would work on your device. The version number is all wrong, and it says Brightstar US (which is the US Developer's Edition of the M8). It isn't intended for your device, won't work, and if you flashed it successfully, it would cause your phone's SIM to stop working (radio brick - possibly permanent).

redpoint73 said:
Complete lack of correct terminology or any meaningful details, means you haven't provided any actual information on what "methods" you tried to root. You say you tried several different methods, but don't provide any information on what those were. You say an SU app, when you don't mean an SU app (SU zip? SuperSU zip? - which is not the same).
Further, you posted that you "downloading the SU app as prescribed in the site". What website? How are we supposed to have any idea what you are talking about? Please understand, that your posts are vague to the point, that they don't actually provide any real information.
If you want proper help on this website, in general, you need to be specific, provide proper details, and user the right terminology.
As the previous response indicated, this isn't the right RUU for your device. Why would you try to use this? Especially since the proper RUU for your Verizon version M8 was already provided in one of my previous responses? It seems you are just guessing around for solutions (which is a recipe for disaster). You have no reason to think the RUU you listed would work on your device. The version number is all wrong, and it says Brightstar US (which is the US Developer's Edition of the M8). It isn't intended for your device, won't work, and if you flashed it successfully, it would cause your phone's SIM to stop working (radio brick - possibly permanent).
Click to expand...
Click to collapse
Alright, clearly I'm not knowledgeable in this type of repair. I apologize for using the wrong terminology, I'm scatter brained and names often elude me. Yes, I apparently used the wrong program to flash my ROM, either way it didn't work. In the end it doesn't matter, I'm throwing in the towel and getting a new phone. Go ahead and delete this thread as I won't be using this forum anymore. You're a ****.

carljames0603 said:
Alright, clearly I'm not knowledgeable in this type of repair. I apologize for using the wrong terminology, I'm scatter brained and names often elude me. Yes, I apparently used the wrong program to flash my ROM, either way it didn't work. In the end it doesn't matter, I'm throwing in the towel and getting a new phone. Go ahead and delete this thread as I won't be using this forum anymore. You're a ****.
Click to expand...
Click to collapse
That's unfortunate, as your issue is probably completely fixable. All you need to do is follow the instructions already provided. Myself and others have taken our time, at no benefit to ourselves, in order to try to help you and others.
Any critique given by me was not mean to insult or attack, and if you read my post there is nothing in there that constitutes a personal attack or flaming (I even said "please") - while you on the other hand can't claim such a statement to be true. A constructive criticism of your posts is not the same as attacking a person (which you did). The intent was for us to obtain the proper information so that we can better understand what you did, in order to help; and hopefully to improve the quality of your subsequent posts (but that didn't happen).
You can try to learn from your mistakes and expand your knowledge; or you can complain and continue to be ignorant. Your choice.

Tried rooting today -- soft brick

Edit: The Verizon repair assistant put my phone back to PHE build [100% battery].
Man I knew I shouldn't have tried to root after all this time. I'm not sure which firmware my phone was on [it was the 60% battery update], either PHE or PK1, as it displays in recovery right now. I tried to follow Lrileys modification of freeza's root guide, which neither of them specify a base firmware to go off of, lol.
Anyways, flashing the userdebug sprint firmware with ODIN 3.12.4 failed and my device softbricked. It boots into recovery and download mode.
I have tried factory reset, wiping cache partition, flashing an AP PH1 firmware, and repair through Verizon software/upgrade assistant.
The closest I've gotten to restoring it was with VUA, however when I go to the repair assistant page, it tells me to put phone in download mode [which I do] but the repair button stays greyed out.
Any help would be greatly appreciated.
Edit: The Verizon Upgrade Assistant wasn't starting, saying it was missing mfc90.dll. Well I downloaded the dll, dropped it in the folder, and was able to get UA to recognize phone. Repair assistant is downloading software right now, we'll see how it goes.

IF you would have read there is no root for the PHE.. you also could have checked this via phone settings before you rooted.
You can also use the verizon app to restore your firmware from even the most bricked of phones. Also in in this forum..(looks like you might have tried this?)
I wouldnt even bother at this point, go get your temp phone =]

ars0n said:
IF you would have read there is no root for the PHE.. you also could have checked this via phone settings before you rooted.
You can also use the verizon app to restore your firmware from even the most bricked of phones. Also in in this forum..(looks like you might have tried this?)
I wouldnt even bother at this point, go get your temp phone =]
Click to expand...
Click to collapse
Well the repair assistant seems to be working atm, so hopefully it goes through without any problems. Neither of these threads in the original post mentioned anything about incompatible firmware though [https://forum.xda-developers.com/verizon-note-7/how-to/root-vzw-note-7-t3448711 and https://forum.xda-developers.com/sprint-note-7/how-to/root-super-leaky-bros-sprint-galaxy-t3447202]. I suppose I should have known trying to use a method that dated.

You shouldn't be messing with this stuff if you don't even know how to see what version your on and read.

very helpful
jjayzx said:
You shouldn't be messing with this stuff if you don't even know how to see what version your on and read.
Click to expand...
Click to collapse
Thank you for the gratuitous reply. Despite your sour attitude I was able to return to PHE through VUA. I was running PK1 firmware, however, again, neither root method specified/recommended/listed a base or stock firmware to flash from [or even posted what they were running]. This place used to be helpful.

Has anyone tried this Engineering boot firmware?

This was posted in the all Note 8 forum claiming it is an engineering combo. Has anyone tried it to verify it is actually an engineer boot?
https://firmware.gem-flash.com/index.php?a=browse&b=category&id=12507
The link above requires a paid membership but a file with the same name is available from androidfilehost, can't verify the md5 though.
https://www.androidfilehost.com/?w=files&flid=213338

From what i gather from the firmware this is the us firmware for sprint, which in theory should work for verizon, however not worth bricking to find out.
---------- Post added at 02:09 PM ---------- Previous post was at 02:08 PM ----------
have you checked the sprint note 8 links??

I just ordered my vzw n8 today for tomorrow delivery. However im not smart enough nor brave enough attempt anything on it with a random rouge firmware, but you can bet I will follow this thread. Here's to wishful thinking. : )
~SG

Also being discussed here
https://forum.xda-developers.com/ga...ssion-snapdragon-note-8-models-t3670091/page4

Is it possible to use the mentioned firmware for some carrier switching flashing on note 8, just like what they did to S8 in this thread: https://forum.xda-developers.com/galaxy-s8/how-to/snap-guide-flashing-standard-fw-carrier-t3625817

I can confirm this Combination firmware is legit, or at least the one from the AFH link. You must do a factory reset after flash or the phone will not boot, likely due to encryption.
This kernel is permissive, and it does have ADB enabled by default.

bangbusdriver said:
I can confirm this Combination firmware is legit, or at least the one from the AFH link. You must do a factory reset after flash or the phone will not boot, likely due to encryption.
This kernel is permissive, and it does have ADB enabled by default.
Click to expand...
Click to collapse
When you say likely due to encryption, do you mean encryption already present on the phone or does flashing this encrypt it? I don't believe my phone is encrypted as I haven't enabled any secure unlock system. Or do you mean bootloader encryption. Unless I'm mistaken the phone isn't encrypted until after a secure unlock option is enabled.
I really don't want to go through my phone setup again when root isn't available yet. This just seems like a first step to enable flashing of a rooted firmware.

jellyhead said:
When you say likely due to encryption, do you mean encryption already present on the phone or does flashing this encrypt it? I don't believe my phone is encrypted as I haven't enabled any secure unlock system. Or do you mean bootloader encryption. Unless I'm mistaken the phone isn't encrypted until after a secure unlock option is enabled.
I really don't want to go through my phone setup again when root isn't available yet. This just seems like a first step to enable flashing of a rooted firmware.
Click to expand...
Click to collapse
Since android 6.0, encryption of /userdata is supposed to have been standard. My understanding is that the partition is encrypted at first boot. It's probably encrypted with your personal key after you set a secure lock setting.
Regardless, won't boot without factory reset. You will lose your data if you want to use this firmware, but simply flashing it doesn't format /userdata. I can't say whether or not flashing back to stock triggers automatic factory reset, but sometimes it does.
I did confirm earlier today thought that you can't only flash the kernel. Phone won't boot, regardless of factory reset. Nor will it work with abl.mbn(I assume android boot loader), and xbl ( download mode?) But, the kernel is not fully permissive anyway. /system cannot be remounted rw, and I can't manipulate the files in /dev/block either.
---------- Post added at 10:57 PM ---------- Previous post was at 10:54 PM ----------
lilila said:
Is it possible to use the mentioned firmware for some carrier switching flashing on note 8, just like what they did to S8 in this thread: https://forum.xda-developers.com/galaxy-s8/how-to/snap-guide-flashing-standard-fw-carrier-t3625817
Click to expand...
Click to collapse
I'd like to try that, but insofar I noticed in Download mode it says the carrier is ATT. I think this might be set in the /efs but I could be wrong. If so, root can help. For the record, Verizon is the same model N950U as ATT.

Greetings all,
Been a couple years since I've visited these boards, I just picked up the note a couple days back. Am I reading this correctly that we can actually flash the verizon model with the engineering firmware to a more permissive setup without brick, or am I just exceptionally out of date and reading this wrong?

The.Jericho.Initiative said:
Greetings all,
Been a couple years since I've visited these boards, I just picked up the note a couple days back. Am I reading this correctly that we can actually flash the verizon model with the engineering firmware to a more permissive setup without brick, or am I just exceptionally out of date and reading this wrong?
Click to expand...
Click to collapse
Correct, its safe to flash the engineering firmware

hmm. interesting. now I just need to understand (or make sure I understand correctly) that/what is gained by using this firmware? Is root or bootloader unlocked gained by flashing this firmware? I would think this would be a hot topic and more people to chime in. Is there another thread somewhere where people are dissecting this firmware in more detail (based on what IS known)? Sorry, im just trying to simplify the subject. : )
~SG

I have successfully used this for carrier switching...Carrier Switching Guide coming soon....

SomeGuy2008 said:
hmm. interesting. now I just need to understand (or make sure I understand correctly) that/what is gained by using this firmware? Is root or bootloader unlocked gained by flashing this firmware? I would think this would be a hot topic and more people to chime in. Is there another thread somewhere where people are dissecting this firmware in more detail (based on what IS known)? Sorry, im just trying to simplify the subject. : )
~SG
Click to expand...
Click to collapse
THIS!! ^^
If this is true then I am trading in my Note 4 asap!
Though I have that sinking feeling in my gut that it may be too good to be true. As you've said, I too really feel like this info would have spread like wildfire if this was the case. I hope I am wrong!
Edit: I read a little more into it and it's pretty much just a carrier unlock. Not bootloader... :/

SomeGuy2008 said:
hmm. interesting. now I just need to understand (or make sure I understand correctly) that/what is gained by using this firmware? Is root or bootloader unlocked gained by flashing this firmware? I would think this would be a hot topic and more people to chime in. Is there another thread somewhere where people are dissecting this firmware in more detail (based on what IS known)? Sorry, im just trying to simplify the subject. : )
~SG
Click to expand...
Click to collapse
Root is now live
https://forum.xda-developers.com/galaxy-note-8/development/root-samfail-galaxy-note8-t3685340

jellyhead said:
Root is now live
https://forum.xda-developers.com/galaxy-note-8/development/root-samfail-galaxy-note8-t3685340
Click to expand...
Click to collapse
Thanks for the info. Damit, I have everything working just right in a non rooted fashion. And to be honest I kinda like it that way. But then again I do miss the typical root advantages.
~SG

I'll be waiting to see if the 80% battery issue gets solved.

I read that part. Yuk. That sucks. Ima hold out for a bit while it bakes in the oven a little longer.

I'm stoked that it does not trip knox...