Need HELP!! with HTC Desire 816 - Desire 816 Q&A, Help & Troubleshooting

Hello Everyone,
I need help with my HTC Desire 816 Here is my issue :
I rooted my device using this tutoriol : http://forum.xda-developers.com/showthread.php?t=2775801
everything went smooth but when i open SuperSU it says Binary needs to be updated but i'm unable to update it in anyway.
After root the phone restarts randomly.
I even tried to unroot using SuperSU and other ways but nothing seems to work.
I also tried to Disable Write Permission and that's when it all went wrong.
Now my phone keeps rebooting and i can't even use it
N.B: I always had an iphone, it's my first android phone so i'm a Newbie in rooting.
Any help is REALLY appreciated.
Thanks.

the link doesn't work, if you mean v_superuser guide the post was for kitkat
for lollipop you need to flash supersu v 2.46 I guess, atleast that what I did
the write protection post indicated in his guide also was for kitkat
try flashing stock if you took a backup b4 rooting to stop the random restarts, flash supersu and disable write protection for lollipop http://forum.xda-developers.com/des...-disable-writeprotection-sense-stock-t3091456

[/COLOR]
MaE_sTrO said:
Hello Everyone,
I need help with my HTC Desire 816 Here is my issue :
I rooted my device using this tutoriol http://forum.xda-developers.com/show....php?t=2775801
everything went smooth but when i open SuperSU it says Binary needs to be updated but i'm unable to update it in anyway.
After root the phone restarts randomly.
I even tried to unroot using SuperSU and other ways but nothing seems to work.
I also tried to Disable Write Permission and that's when it all went wrong.
Now my phone keeps rebooting and i can't even use it
N.B: I always had an iphone, it's my first android phone so i'm a Newbie in rooting.
Any help is REALLY appreciated.
Thanks.
Click to expand...
Click to collapse
Sorry your having these problems but as long as you can get into your boatloader they should be fixable. Hopefully you did a full nandroid backup of your phone after rooting before attempting any other flashes or mods but if you didn't then that's just friendly advice for any future flashes for everybody , me included. It's an easy step to skip(I've forgotten to do one myself) but it's the most important step to being able to easily restore from any problems.
Try to get into your boatloader by holding power button then volume down and hold. That should reboot into your bootloader and from there you can enter recovery and do a factory reset then wipe cache and dalvik cache then reboot system and see if that stops the bootloops. If not then you might need to find and reflash your stock recovery and relock your bootloader then find a flashable zip or executable RUU (rom utility update) and flash back to completely stock. If your in the U.S. HTC has the RUU executable files on their website in the downloads section(RUU not kernel). These you can either run from a P.C. as an executable program with your phone in fastboot or rename to your model specific firmware image and install to and flash from your phone's external SD card from your bootloader. The only issue would be if your system has been modified by the write permission mod you flashed then that would need to be removed before any signed stock update could work. What's your specific phone model( a5_"what") and are you in the U.S. or overseas?
EDIT: it's volume down not volume up. Volume up reboots the phone. Sorry, I use an app to do all of that now not my keys.

thoctor said:
[/COLOR]
Sorry your having these problems but as long as you can get into your boatloader they should be fixable. Hopefully you did a full nandroid backup of your phone after rooting before attempting any other flashes or mods but if you didn't then that's just friendly advice for any future flashes for everybody , me included. It's an easy step to skip(I've forgotten to do one myself) but it's the most important step to being able to easily restore from any problems.
Try to get into your boatloader by holding power button then volume down and hold. That should reboot into your bootloader and from there you can enter recovery and do a factory reset then wipe cache and dalvik cache then reboot system and see if that stops the bootloops. If not then you might need to find and reflash your stock recovery and relock your bootloader then find a flashable zip or executable RUU (rom utility update) and flash back to completely stock. If your in the U.S. HTC has the RUU executable files on their website in the downloads section(RUU not kernel). These you can either run from a P.C. as an executable program with your phone in fastboot or rename to your model specific firmware image and install to and flash from your phone's external SD card from your bootloader. The only issue would be if your system has been modified by the write permission mod you flashed then that would need to be removed before any signed stock update could work. What's your specific phone model( a5_"what") and are you in the U.S. or overseas?
EDIT: it's volume down not volume up. Volume up reboots the phone. Sorry, I use an app to do all of that now not my keys.
Click to expand...
Click to collapse
Thank you thoctor , as i said i'm a newbie in rooting so i didn't make full nandroid backup but thanks to you and after doing a factory reset the bootloops stopped, i'm able to use the phone now, but i think the write protection is still disabled, as i'm trying to use apps2sd and creating a new partition in the SD is not working, one more thing i'm unable to update SuperSu's binary too, thanks to your help and i would appreciate if you can help me further.
my model number : A5_ul and cidnum: HTC__E11 , and i'm in europe.

Roberto Nigel said:
the link doesn't work, if you mean v_superuser guide the post was for kitkat
for lollipop you need to flash supersu v 2.46 I guess, atleast that what I did
the write protection post indicated in his guide also was for kitkat
try flashing stock if you took a backup b4 rooting to stop the random restarts, flash supersu and disable write protection for lollipop http://forum.xda-developers.com/des...-disable-writeprotection-sense-stock-t3091456
Click to expand...
Click to collapse
Thanks Roberto
that's the exact way i tried to disable write protection, and that's when it all went wrong, but i retried it now it went smooth, but i think it didn't work , is there anyway to make sure if it's enabled or not ?

MaE_sTrO said:
Thank you thoctor , as i said i'm a newbie in rooting so i didn't make full nandroid backup but thanks to you and after doing a factory reset the bootloops stopped, i'm able to use the phone now, but i think the write protection is still disabled, as i'm trying to use apps2sd and creating a new partition in the SD is not working, one more thing i'm unable to update SuperSu's binary too, thanks to your help and i would appreciate if you can help me further.
my model number : A5_ul and cidnum: HTC__E11 , and i'm in europe.
Click to expand...
Click to collapse
No problem buddy. We've all been there trust me on that. You can update the binaries from within the SuperSU apps settings or in custom recovery. Check to verify you have the most current version from the play store and if not download it. Also you might try to wipe your cache and dalvik cache from within your custom recovery then reboot system and see if that fixes it. As for the WP mod there are some that get it to work right off the bat and others who have to add or remove a line in the lib files using a terminal emulator app but I've never personally used this mod as I have true S off on my 816 a5_chl. I use Link2SD not the one your talking about but the partitioning for the app I use is done on a P.C. using EaseUS partition manager. Is yours the same process?

thoctor said:
No problem buddy. We've all been there trust me on that. You can update the binaries from within the SuperSU apps settings or in custom recovery. Check to verify you have the most current version from the play store and if not download it. Also you might try to wipe your cache and dalvik cache from within your custom recovery then reboot system and see if that fixes it. As for the WP mod there are some that get it to work right off the bat and others who have to add or remove a line in the lib files using a terminal emulator app but I've never personally used this mod as I have true S off on my 816 a5_chl. I use Link2SD not the one your talking about but the partitioning for the app I use is done on a P.C. using EaseUS partition manager. Is yours the same process?
Click to expand...
Click to collapse
Yup i have the latest supersu, About the Link2SD i have it also installed, and i've done the partitions on pc , tried EXT2 , EXT4 amd fat32 nothing worked, after so many tries the last error i get is something like that ( bad magic number in superblock ). that's why i thought it has something to do with the WP.
so i should wipe the cache and dalvik cache and it will do no harm right ?(coz i'm really glad now since i got rid of the rebootloop and i can use my phone .

MaE_sTrO said:
Yup i have the latest supersu, About the Link2SD i have it also installed, and i've done the partitions on pc , tried EXT2 , EXT4 amd fat32 nothing worked, after so many tries the last error i get is something like that ( bad magic number in superblock ). that's why i thought it has something to do with the WP.
so i should wipe the cache and dalvik cache and it will do no harm right ?(coz i'm really glad now since i got rid of the rebootloop and i can use my phone .
Click to expand...
Click to collapse
Lol. I know how you feel. You can wipe those two all day long and nothing bad will happen. It's just a cache cleaner that clears out our any leftover files in the firmwares cache folders. System restore wipes the whole phone except for the external SD card and your personal downloads or data files. Custom delete can add those personal data files so be careful there but otherwise your good. Check settings to see in about phone if your SElinux permissions are set to enforcing or permissive. The mod is supposed to change them to permissive for it to work properly.
Also on link2SD set the new data partition to ext2 if your on a stock rom and set as primary then set the remaining partition for your normal storage(not app data) to fat32 (as that's the format the phone will let you view in your SD card) and also as primary. It was the write permissions that wasn't letting it work not the format because I've been down that road many times before I got mine right.

thoctor said:
Lol. I know how you feel. You can wipe those two all day long and nothing bad will happen. It's just a cache cleaner that clears out our any leftover files in the firmwares cache folders. System restore wipes the whole phone except for the external SD card and your personal downloads or data files. Custom delete can add those personal data files so be careful there but otherwise your good. Check settings to see in about phone if your SElinux permissions are set to enforcing or permissive. The mod is supposed to change them to permissive for it to work properly.
Also on link2SD set the new data partition to ext2 if your on a stock rom and set as primary then set the remaining partition for your normal storage(not app data) to fat32 (as that's the format the phone will let you view in your SD card) and also as primary. It was the write permissions that wasn't letting it work not the format because I've been down that road many times before I got mine right.
Click to expand...
Click to collapse
thanks for the fast response , i wiped the cache and i still can't update the binary i get this msg
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if i press normal the phone reboots, if i press TWRp/CWM ( since i rooted with cwm recovery) it reboots enters recovery starts loading then reboots and i get the same msg about the update again.
Also about the SElinux i can't find it in about :S.

MaE_sTrO said:
thanks for the fast response , i wiped the cache and i still can't update the binary i get this msg
if i press normal the phone reboots, if i press TWRp/CWM ( since i rooted with cwm recovery) it reboots enters recovery starts loading then reboots and i get the same msg about the update again.
Also about the SElinux i can't find it in about :S.
Click to expand...
Click to collapse
Find official TWRP recovery flashable zip for the a5 on their website and download and flash over CWM from your P.C. using ADB/fastboot.Just put the file in your ADB folder and rename it twrp.img and enter fastboot flash recovery"recovery name".img and either enter the name after typing recovery or just drag it down into your command prompt after typing recovery and it should flash automatically with your phone's USB debugging activated and the phone in fastboot. I use TWRP and you might be having an issue with the CWM exe recovery.Can't hurt to flash and you could always go back if you didn't like it but most everybody loves TWRP custom touch recovery. I know I do. It's on all my rooted devices.
As for the SElinux it's at the very bottom of my settings in about phone but I'm on a custom rom CM12.1 but you should be able to see it somewhat in your phone's settings on stock. I just can't remember where it is but it's there
EDIT: try to reflash in recovery the most current flashable zip for SuperSU found on chainfires website for SuperSU. I believe it's 2.4.6 but don't quote me on that just make sure it's the most current one which it will be on his site. That may help the binary issue. Even if the one you flashed is the most current flashable zip flash it again.

thoctor said:
Find official TWRP recovery flashable zip for the a5 on their website and download and flash over CWM from your P.C. using ADB/fastboot.Just put the file in your ADB folder and rename it twrp.img and enter fastboot flash recovery"recovery name".img and either enter the name after typing recovery or just drag it down into your command prompt after typing recovery and it should flash automatically with your phone's USB debugging activated and the phone in fastboot. I use TWRP and you might be having an issue with the CWM exe recovery.Can't hurt to flash and you could always go back if you didn't like it but most everybody loves TWRP custom touch recovery. I know I do. It's on all my rooted devices.
As for the SElinux it's at the very bottom of my settings in about phone but I'm on a custom rom CM12.1 but you should be able to see it somewhat in your phone's settings on stock. I just can't remember where it is but it's there
Click to expand...
Click to collapse
Just flashed TWRP.
tried to update binary same thing happend but now i see in TWRP when it tries to update it says no MD5

thoctor said:
Find official TWRP recovery flashable zip for the a5 on their website and download and flash over CWM from your P.C. using ADB/fastboot.Just put the file in your ADB folder and rename it twrp.img and enter fastboot flash recovery"recovery name".img and either enter the name after typing recovery or just drag it down into your command prompt after typing recovery and it should flash automatically with your phone's USB debugging activated and the phone in fastboot. I use TWRP and you might be having an issue with the CWM exe recovery.Can't hurt to flash and you could always go back if you didn't like it but most everybody loves TWRP custom touch recovery. I know I do. It's on all my rooted devices.
As for the SElinux it's at the very bottom of my settings in about phone but I'm on a custom rom CM12.1 but you should be able to see it somewhat in your phone's settings on stock. I just can't remember where it is but it's there
EDIT: try to reflash in recovery the most current flashable zip for SuperSU found on chainfires website for SuperSU. I believe it's 2.4.6 but don't quote me on that just make sure it's the most current one which it will be on his site. That may help the binary issue. Even if the one you flashed is the most current flashable zip flash it again.
Click to expand...
Click to collapse
Flashed TWRP reflashed SuperSU from chainfires website , same issue , but now i can see when it tries to update in TWRP it says no MD5!!!
and i assure u i can't find SElinux anywhere in about !!!!

MaE_sTrO said:
Flashed TWRP reflashed SuperSU from chainfires website , same issue , but now i can see when it tries to update in TWRP it says no MD5!!!
and i assure u i can't find SElinux anywhere in about !!!!
Click to expand...
Click to collapse
No problem , Don't worry about the permissions for now. The MD5 is the checksum that verifies the file isn't corrupt but if you got it from the chainfire site your fine. Try to update the binary thru twrp or in the SuperSU app and select your recovery as the way you want to update and see what happens.
Also did you have MD5 check enabled in TWRP? I do in mine for file verification but just wondering what yours was set to when you got that notice. It shouldn't stop SuperSU from flashing either way it's just a file verifier.
---------- Post added at 12:56 AM ---------- Previous post was at 12:18 AM ----------
the binaries are what SuperSU uses to get and maintain root . If they are incomplete or corrupt then they have to be reflashed over with an uncorrupted version. That is usually why people keep getting the notice to update the binaries and when they do they can't because they are not complete or corrupt and need to be totally removed i.e. reflashing, which you did, or unrooting from the SuperSU app itself and redownloading again from the play store. This is what I've read on several help sites for this issue. Just wanted to pass along the why not just the what.

Again thank you for giving me so much information so i can understand the way things work and what i am doing, MD5 check was disabled i tried updating binary thru twrp i also tried enabling the MD5 both gave the same result, but the weird thing that it says done proccessing zip file , but when it reboots the update msg shows again, another thing when updating through twrp i noticed this line " full SElinux is present ".

MaE_sTrO said:
Again thank you for giving me so much information so i can understand the way things work and what i am doing, MD5 check was disabled i tried updating binary thru twrp i also tried enabling the MD5 both gave the same result, but the weird thing that it says done proccessing zip file , but when it reboots the update msg shows again, another thing when updating through twrp i noticed this line " full SElinux is present ".
Click to expand...
Click to collapse
No problem. To me that's the whole point of helping here on XDA is to make these things easier to understand for the person asking for assistance so they don't have to come back for the same thing again.Also because I was here in the same situations just a year or so ago and others helped me understand and I'm not a rocket scientist by any means .
Try to verify root through the root checker app on the play store. Almost positive it will say not rooted but it can't hurt to verify. Then , again, I would try to uninstall SuperSU through the app itself in it's settings as I'm almost positive the binaries are corrupted or incomplete and that's why you keep getting the same "update binaries message". If I sound like a broken record it's because I have learned from multiple Android device issues that sometimes for whatever reason things don't take and some combination of things might happen to alter the reason and trying the same thing again fixed it after coming back to it. I would also download SuperSU again but on a different device(laptop, computer) from chainfires site and reflash it just on the off chance the file is corrupted . Although at this point it's unlikely I know.
Lastly I would do an advanced wipe in TWRP recovery and add system to Data and Dalvik cache and cache from the factory reset. Not internal storage or SD card. Then I would flash the newly downloaded SuperSU and wipe Dalvik and cache then reboot system. Back up your contacts and numbers through Google's own backup in settings and they may already be backed up and use Super Backup app as well to save to external SD card as it can backup the same things.

thoctor said:
No problem. To me that's the whole point of helping here on XDA is to make these things easier to understand for the person asking for assistance so they don't have to come back for the same thing again.Also because I was here in the same situations just a year or so ago and others helped me understand and I'm not a rocket scientist by any means .
Try to verify root through the root checker app on the play store. Almost positive it will say not rooted but it can't hurt to verify. Then , again, I would try to uninstall SuperSU through the app itself in it's settings as I'm almost positive the binaries are corrupted or incomplete and that's why you keep getting the same "update binaries message". If I sound like a broken record it's because I have learned from multiple Android device issues that sometimes for whatever reason things don't take and some combination of things might happen to alter the reason and trying the same thing again fixed it after coming back to it. I would also download SuperSU again but on a different device(laptop, computer) from chainfires site and reflash it just on the off chance the file is corrupted . Although at this point it's unlikely I know.
Lastly I would do an advanced wipe in TWRP recovery and add system to Data and Dalvik cache and cache from the factory reset. Not internal storage or SD card. Then I would flash the newly downloaded SuperSU and wipe Dalvik and cache then reboot system. Back up your contacts and numbers through Google's own backup in settings and they may already be backed up and use Super Backup app as well to save to external SD card as it can backup the same things.
Click to expand...
Click to collapse
i went through your instructions , and after the last steps now i'm stuck on HTC logo
i can't even turn it off or get into recovery!!!!
i managed somehow to get into recovery no it says no OS installed , i guess i F**k it up right ?

MaE_sTrO said:
i went through your instructions , and after the last steps now i'm stuck on HTC logo
i can't even turn it off or get into recovery!!!!
i managed somehow to get into recovery no it says no OS installed , i guess i F**k it up right ?
Click to expand...
Click to collapse
No you didn't f***k it up I f*****d it up. I was thinking of what I do on my custom rom when I can't get something fixed and I brainfarted and forgot for a second your on a stock rom. That's on me not you so be mad at me not yourself. The good thing is it's fixable. I just flash a new custom rom but with stock it's a little bit different. You need to flash back the stock recovery which I will find and link you to and then lock the bootloader and flash back your stock Rom which I will also link you to. I am so sorry. I was in a doctor's office waiting room and my mind was on other things but that's no excuse just an explanation. Below is the link to stock lollipop for the a5_ul European version
Better than what I first linked us this forum page from Nukaru a few posts down in this forum for the stock a5_ul. He had links to both the stock recovery and stock rom file with detailed instructions on how to get the stock rom back on your phone. I know it works because he had a problem and figured all this out himself then wrote a detailed tutorial on how he fixed his. Link below.
http://forum.xda-developers.com/desire-816/help/a5ul-unable-to-flash-ruu-t3294835/page2

thoctor said:
No you didn't f***k it up I f*****d it up. I was thinking of what I do on my custom rom even I can't get something fixed and I brainfarted and forgot for a second your on a stock rom. That's on me not you so be mad at me not yourself. The good thing is it's fixable. I just flash a new custom rom but with stock it's a little bit different. You need to flash back the stock recovery which I will find and link you to and then lock the bootloader and flash back your stock Rom which I will also link you to. I am so sorry. I was in a doctor's office waiting room and my mind was on other things but that's no excuse just an explanation. Below is the link to stock lollipop for the a5_up European version
Link to stock lollipop rom below
https://www.androidfilehost.com/?fid=23991606952595166
Click to expand...
Click to collapse
Never mind i have nothing to loose as long as it's fixable lol, anyway i'll try this rom now
note: when i relock boot loader it says RELOCKED with S-ON does this matters?

MaE_sTrO said:
Never mind i have nothing to loose as long as it's fixable lol, anyway i'll try this rom now
note: when i relock boot loader it says RELOCKED with S-ON does this matters?
Click to expand...
Click to collapse
No, hold off on that first link I have a better one buddy. Just edited it above. No, "relocked S on" is what it's supposed to say so your fine but don't lock it yet or if you already did unlock it using the same unlock token you used on htc developers to unlock it in the first place . Then you flash back your stock recovery. Then relock your bootloader. Then you flash back your stock rom in that order.

thoctor said:
No hold off on that first link I have a better one buddy. Just edited it above. No relocked S on is what it's supposed to say so your fine but don't lock it yet orv I'd your already did unlock it using the same unlock token you used on htc developers to unlock it in the first place .
Click to expand...
Click to collapse
Alright downloading now...

Related

Newbie help with a failed (?) root

Hey guys, first of all I'm a complete n00b to all of this stuff, so please bear with me and consider using layman type language with me. Some of you may think I shouldn't even be messing with this stuff with my limited knowledge, but I'm determined to get the best out of my Galaxy Nexus and generally learn quickly and follow directions well.
Here's the bullet-point run-down of what happened:
- Bought a Galaxy Nexus that was "yakjuux" and wasn't getting updates.
- Read through a thread on here on how to flash to "yakju". Did so successfully.
- I then wanted to root since my device was already wiped from unlocking bootloader or flashing some partition or something
- Followed this thread (http://forum.xda-developers.com/showthread.php?p=19583168#post19583168)
- Rebooted, saw the "Superuser" app and thought I nailed it.
- Saw an update for Jellybean, it requested a reboot before install
- Upon reboot I got a dreaded android on it's back with a red exclamation, nearly wet myself. Took battery out, put back in, phone booted normally. It didn't update to JB anymore and when I check for updates it doesn't show. I figured it'll come around again.
- Went to "superuser" app to update, it said it "Failed!" upon trying to gain root access. Upon reading around, downloaded SU Update Fixer from the store, failed gaining root access. Read some more, downloaded "Root Checker" app and it said my device was not rooted.
So where do I go from here? I'm tempted to just follow the 'flash to yakju' thread again and go back to a clean ROM and forget rooting, but maybe there's something simple I can do from here.
** One side note, in that rooting thread I mentioned above, I did not understand step #7 (7. Using CWM recovery, install su.zip that you downloaded in step 1) too clearly. I didn't understand how my phone could even get the su.zip file. So after reading some other rooting methods, I copy and pasted the .zip into the "Internal Storage" drive under My Computer > Samsung Phone > Internal Storage. Then using CWM Recovery on my phone just selected to install it from sdcard (since the Gnex doesn't have an sdcard) and it seemed to be a success. But I'm not sure if that was right. I assumed it was since I got the Superuser app.
Another thing that felt kind of wrong is that, when I flashed to yakju, it wiped my phone clean. I expected rooting to do the same thing, but it didn't (I think because my bootloader was already unlocked?). So I'm not sure if that has anything to do with it either.
Please help. And remember to please refer to things in dummy form. I only know things that involve the above, like using the cmd and typing fastboot and flashing files from a directory, etc.
Thank you in advance.
BryMerc said:
Hey guys, first of all I'm a complete n00b to all of this stuff, so please bare with me and consider using layman type language with me. Some of you may think I shouldn't even be messing with this stuff with my limited knowledge, but I'm determined to get the best out of my Galaxy Nexus and generally learn quickly and follow directions well.
Here's the bullet-point run-down of what happened:
- Bought a Galaxy Nexus that was "yakjuux" and wasn't getting updates.
- Read through a thread on here on how to flash to "yakju". Did so successfully.
- I then wanted to root since my device was already wiped from unlocking bootloaderor or replace some partition or something
- Followed this thread (http://forum.xda-developers.com/showthread.php?p=19583168#post19583168)
- Rebooted, saw the "Superuser" app and thought I nailed it.
- Saw an update for Jellybean, it requested a reboot before install
- Upon reboot I got a dreaded android on it's back with a red exclamation, nearly wet myself. Took battery out, put back in, phone booted normally. It didn't update to JB anymore and when I check for updates it doesn't show. I figured it'll come around again.
- Went to "superuser" app to update, it said it "Failed!" upon trying to gain root access. Upon reading downloaded SU Update fixed from the store, failed gaining root access. Read some more, downloaded "Root Checker" app and it said my device was not rooted.
So where do I go from here? I'm tempted to just follow the 'flash to yakju' thread again and go back to a clean ROM and forget rooting, but maybe there's something simple I can do from here.
One side note, in that rooting thread I mentioned above, I did not understand step #7 (7. Using CWM recovery, install su.zip that you downloaded in step 1) too clearly. I didn't understand how my phone could even get the su.zip file. So after reading some other rooting methods, I copy and pasted the .zip into the "Internal Storage" drive under My Computer > Samsung Phone > Internal Storage. Then using CWM Recovery just selected to install it from sdcard (since the Gnex doesn't have an sdcard) and it seemed to be a success. But I'm not sure if that was right. I assume it was if I got the Superuser app.
Please help. And remember to please refer to things in dummy form. I only know things that involve the above, like using the cmd and typing fastboot and flashing .img files from a directory, etc.
Thank you in advance.
Click to expand...
Click to collapse
Re-install superuser the same way you did the first time. The OTA failed because you have a custom recovery installed. If you want to update to Jelly Bean, look into installing one of the JB ROMs in the development forums, or if you must have the OTA you'll have to flash the stock recovery and make sure everything else is stock as well. OTAs do not care if you are rooted or have an unlocked bootloader.
you can also install the OTA manually, heres my method
1) grab the link for yakju IMM76i > 4.1.1 from here: http://forum.xda-developers.com/showthread.php?t=1764536 and place that iin your sdcard. ALSO download this version of Superuser (chainfires one): http://download.chainfire.eu/197/SuperSU/CWM-SuperSU-v0.93.zip and place that in your sdcard too.
2) install clockworkmod recovery again the same way you did before, using fastboot flash recovery recovery.img, press vol down twice in the bootloader and go straight into the recovery.
3) install the OTA zip you downloaded and placed in your sdcard
4) clear cache and fix permissions (might not be necessary but you can do it just incase)
5) reboot, you should now have stock jellybean. the ClockworkMod recovery would be removed at this point because stock android has a file in system which replaces the stock recovery after every reboot, unless you delete that file.
6) go back into the bootloader, flash recovery as before and again boot straight into the recovery. this time flash the superuser zip you downloaded.
7) reboot. should be all sorted now
JaiaV said:
Re-install superuser the same way you did the first time. The OTA failed because you have a custom recovery installed. If you want to update to Jelly Bean, look into installing one of the JB ROMs in the development forums, or if you must have the OTA you'll have to flash the stock recovery and make sure everything else is stock as well. OTAs do not care if you are rooted or have an unlocked bootloader.
Click to expand...
Click to collapse
Thanks for the fast response.
So basically, I just copy and paste su.zip again into my Internal Storage on my computer. Put my phone into Recovery Mode, plug it in, find and install that su.zip again, and then reboot?
Also, this is something I didn't know: So if you are rooted, you cannot update "normally"? I will always have to flash over the latest ROM?
Thanks.
BryMerc said:
So basically, I just copy and paste su.zip again into my Internal Storage on my computer. Put my phone into Recovery Mode, plug it in, find and install that su.zip again, and then reboot
Click to expand...
Click to collapse
Yes.
BryMerc said:
Also, this is something I didn't know: So if you are rooted, you cannot update "normally"? I will always have to flash over the latest ROM?
Click to expand...
Click to collapse
JaiaV said:
OTAs do not care if you are rooted or have an unlocked bootloader.
Click to expand...
Click to collapse
They only care that the recovery and /system are stock, and even then (as I said) don't care if you're rooted. Rooting doesn't matter. Having a custom recovery does. They are not the same thing. Also, read through ||Nexus|| response.
IINexusII said:
you can also install the OTA manually, heres my method
1) grab the link for yakju IMM76i > 4.1.1 from here: http://forum.xda-developers.com/showthread.php?t=1764536 and place that iin your sdcard. ALSO download this version of Superuser (chainfires one): http://download.chainfire.eu/197/SuperSU/CWM-SuperSU-v0.93.zip and place that in your sdcard too.
2) install clockworkmod recovery again the same way you did before, using fastboot flash recovery recovery.img, but dont reboot this time, press vol down twice in the bootloader and go straight into the recovery.
3) install the OTA zip you downloaded and placed in your sdcard
4) clear cache and fix permissions (might not be necessary but you can do it just incase)
5) reboot, you should now have stock jellybean. the ClockworkMod recovery would be removed at this point because stock android has a file in system which replaces the stock recovery after every reboot, unless you delete that file.
6) go back into the bootloader, flash recovery as before and again boot straight into the recovery. this time flash the superuser zip you downloaded.
7) reboot. should be all sorted now
Click to expand...
Click to collapse
OK, thank you so much. I'm going to do exactly this. When I "fastboot flash" these over again, will they just replace the old ones? Or do I have to uninstall the ones already on my phone or something. I feel like it may get cluttered or something lol, sorry if that's stupid.
BryMerc said:
OK, thank you so much. I'm going to do exactly this. When I "fastboot flash" these over again, will they just replace the old ones? Or do I have to uninstall the ones already on my phone or something. I feel like it may get cluttered or something lol, sorry if that's stupid.
Click to expand...
Click to collapse
no, youre just reflashing the recovery which wont affect anything else. once you reboot it will revert back to the stock recovery anyway, so youll be able to get future OTA updates just fine.
edit: yes itll just be replacing the recovery, nothing else
IINexusII said:
no, youre just reflashing the recovery which wont affect anything else. once you reboot it will revert back to the stock recovery anyway, so youll be able to get future OTA updates just fine.
edit: yes itll just be replacing the recovery, nothing else
Click to expand...
Click to collapse
Hey, I just installed the Jellybean but how do I do #4? Clear cache and fix permissions?
BryMerc said:
Hey, I just installed the Jellybean but how do I do #4? Clear cache and fix permissions?
Click to expand...
Click to collapse
in clockwork mod recovery there should be a "Wipe Cache" option, and for fixing permissions go to "advanced" and "Fix Permissions"
BryMerc said:
Hey, I just installed the Jellybean but how do I do #4? Clear cache and fix permissions?
Click to expand...
Click to collapse
Wait, actually I don't think the JB installed now that I'm staring at the screen properly.
It went Installing update...
assert failed: file .........blah blah
Installation aborted.
Also, the drivers I thought I had for my phone seem to be messing up and in device manager it says "Full" with an exclamation point. I'm not sure why.
Sorry for the late responses as a n00b I'm stuck with 5 minute intervals here.
which country are you from?
IINexusII said:
which country are you from?
Click to expand...
Click to collapse
Canada.
I just tried reinstalling the drivers and everything and for some reason it's not working. I flash Clockwork Recovery, I see the JB.zip, but when I click to install it it says "assert failed" and has the dead Android. Not sure if it's a driver issue, but I redid the Universal Naked one I had before that worked.
BryMerc said:
Canada.
I just tried reinstalling the drivers and everything and for some reason it's not working. I flash Clockwork Recovery, I see the JB.zip, but when I click to install it it says "assert failed" and has the dead Android. Not sure if it's a driver issue, but I redid the Universal Naked one I had before that worked.
Click to expand...
Click to collapse
After selecting "Install zip from sdcard" I see an option "apply /sdcard/update.zip". Is that anything maybe I need to do or something?
check your PM

Note 4 Marshmellow root not working!

So usually I don't have any issues with rooting my phone and all. For some unknown reason i just cant seem to root my Sprint Note 4 phone!
Information:
Phone: Sprint Note 4
Model: SM-N910P
Android Version: 6.0.1
Software Version: N910PVPU4DPE1
Build Number: MMB29M.N910PVPU4DPE1
TWRP Version: twrp-3.0.2-0-tbltespr (Which i successfully managed to install)
I used CF-Auto-Root-trltespr-trltespr-smn910p.tar
I did notice that when i flash my auto-root it says "Finding boot image.....Boot image not found, Aborting" under the Boot image patch.
Any ideas on what it means? I'm at a total loss so anything would help me at this point.
imsuckk said:
So usually I don't have any issues with rooting my phone and all. For some unknown reason i just cant seem to root my Sprint Note 4 phone!
Information:
Phone: Sprint Note 4
Model: SM-N910P
Android Version: 6.0.1
Software Version: N910PVPU4DPE1
Build Number: MMB29M.N910PVPU4DPE1
TWRP Version: twrp-3.0.2-0-tbltespr (Which i successfully managed to install)
I used CF-Auto-Root-trltespr-trltespr-smn910p.tar
I did notice that when i flash my auto-root it says "Finding boot image.....Boot image not found, Aborting" under the Boot image patch.
Any ideas on what it means? I'm at a total loss so anything would help me at this point.
Click to expand...
Click to collapse
CF-Auto Root was made to flash with odin, to keep your stock recovery in place. I don't think it works with MM roms.
Just download and flash Supersu from within TWRP. Here's the thread for SuperSu Here.
I always use the Latest version 2.74 here. But you can use the Stable version 2.65 here. They're both in the thread above.
Enjoy!
aaron74 said:
CF-Auto Root was made to flash with odin, to keep your stock recovery in place. I don't think it works with MM roms.
Just download and flash Supersu from within TWRP. Here's the thread for SuperSu Here.
I always use the Latest version 2.74 here. But you can use the Stable version 2.65 here. They're both in the thread above.
Enjoy!
Click to expand...
Click to collapse
So basically there is no CF-Root that works for MM and i just have to play the waiting game?
Wouldn't THIS CF-Root work for my ROM? Sorry for all the questions lol. Never dealt with these issues before.
imsuckk said:
So basically there is no CF-Root that works for MM and i just have to play the waiting game?
Wouldn't THIS CF-Root work for my ROM? Sorry for all the questions lol. Never dealt with these issues before.
Click to expand...
Click to collapse
No you don't have to wait. You can root. Cf-auto was made by the same person as supersu. It was just intended to root your phone with odin in one step. What it does is temporary installs a custom recovery that roots your phone, then puts back a stock recovery (At least something like that). But it isn't up to date to work with Marshmallow. So you just have to do it manually. I thought you said you already have Twrp recovery but I'll show you all steps. I'm assuming you have odin and know how to use it.
1. Download and install Twrp from this thread. Follow links in thread to download and install with Odin here.
2. Once you get TWRP installed. I suggest you boot into it and make a Full Backup of your phone.
3. Download onto your phone SuperSu 2.74 here.
5. Boot into Twrp and install the supersu file you downloaded.
You're now rooted.
aaron74 said:
No you don't have to wait. You can root. Cf-auto was made by the same person as supersu. It was just intended to root your phone with odin in one step. What it does is temporary installs a custom recovery that roots your phone, then puts back a stock recovery (At least something like that). But it isn't up to date to work with Marshmallow. So you just have to do it manually. I thought you said you already have Twrp recovery but I'll show you all steps. I'm assuming you have odin and know how to use it.
1. Download and install Twrp from this thread. Follow links in thread to download and install with Odin here.
2. Once you get TWRP installed. I suggest you boot into it and make a Full Backup of your phone.
3. Download onto your phone SuperSu 2.74 here.
5. Boot into Twrp and install the supersu file you downloaded.
You're now rooted.
Click to expand...
Click to collapse
Same issue :/
My Steps:
1. I use a script to convert TWRP IMG file to TAR then flash to my phone. (I used twrp-2.8.7.0-trltespr.img becuause TWRP 3.0.2.0 doesn't flash onto my phone for some reason.)
2. I go onto TWRP and install SuperSu 2.74. (While flashing i see the "Boot Patch" error")
3. Boot up phone and no SU is installed so i install SuperSU from playstore and open up the app. No SU binary installed.
4. After all goes wrong I try latest CF-Root to see if it works. No luck.
5. Try to get into TWRP and receive "Android installing recovery" or something similar. Stock android recovery is installed again.
6. Repeat.
imsuckk said:
Same issue :/
My Steps:
1. I use a script to convert TWRP IMG file to TAR then flash to my phone. (I used twrp-2.8.7.0-trltespr.img becuause TWRP 3.0.2.0 doesn't flash onto my phone for some reason.)
2. I go onto TWRP and install SuperSu 2.74. (While flashing i see the "Boot Patch" error")
3. Boot up phone and no SU is installed so i install SuperSU from playstore and open up the app. No SU binary installed.
4. After all goes wrong I try latest CF-Root to see if it works. No luck.
5. Try to get into TWRP and receive "Android installing recovery" or something similar. Stock android recovery is installed again.
6. Repeat.
Click to expand...
Click to collapse
Oh. That explains it. TWRP ISN'T installed. Let me explain.
1 Download Twrp here.
2 Odin Twrp to phone. Make sure to uncheck auto reboot in odin first. After odin completes it'll say something like all operations done. Just make sure odin is done. It don't take long. Then you have to unplug usb from phone and pull out battery for 10 sec. Put battery back in and hold Vol up + Home + Power button until Twrp boots.
3 now twrp is installed and you can install root.
Also backup your phone.
Sorry I'm busy right now and can't post a good post with pics. If that all makes sense then you should be good to go. If you don't understand what I mean I can message you later with some screenshots
imsuckk said:
Same issue :/
My Steps:
1. I use a script to convert TWRP IMG file to TAR then flash to my phone. (I used twrp-2.8.7.0-trltespr.img becuause TWRP 3.0.2.0 doesn't flash onto my phone for some reason.)
2. I go onto TWRP and install SuperSu 2.74. (While flashing i see the "Boot Patch" error")
3. Boot up phone and no SU is installed so i install SuperSU from playstore and open up the app. No SU binary installed.
4. After all goes wrong I try latest CF-Root to see if it works. No luck.
5. Try to get into TWRP and receive "Android installing recovery" or something similar. Stock android recovery is installed again.
6. Repeat.
Click to expand...
Click to collapse
tar.img is what you should flash in Odin for TWRP. If you are already on TWRP recovery, you can use the .img file to update within TWRP. TWRP makes both these files in flash form; one for Odin flash, the other for TWRP recovery flash. No need to convert. See link below for the Odin flashable TWRP.
Your kernel must already be patched or custom. (Possibly the reason it can't be patched).
When you boot your ROM, check your kernel and bootloader using Galaxy Tools or PhoneInfo for Samsung. If they don't match your last known update, it's possible you've not successfully updated because your reactivation lock is enabled and you didn't notice you failed to update. Nonetheless, check your reactivation lock by going into Settings/Security and uncheck the option.
If failures persist, flash the stock tar in Odin and make sure it flashes.
For the record, latest update for CF AutoRoot for Note 4 does in fact work. But note, you should flash that in Odin over full stock only. Don't try to flash it if you already flashed TWRP. It's intended to back up stock recovery and stock kernel to restore if you full un-root within the SuperSU application. It's been reportedly to be an unknown or dysfunctional but I can confirm it worked for me back on PB5 leaked MM tar. I used the latest update for CF AutoRoot for Note 4 then. Can't imagine anything broke since then but when I realized it was just systemless root, I lost interest. But hey, it has its purpose for those not interested in TWRP recovery and want yo test if OTA is possible with the limited modification. I've yet to test the theory that it may allow OTA update if system ro partition is left untouched. I like sound mods too much to leave system fully stock.
I can recommend an easier way though (if uninterested in systemless root): you don't have to pre-root if flashing a custom ROM. Once you determine your issue or just Odin flash and confirm the stock PE2 tar. Flash the TWRP tar.img file and then factory reset and flash Freeza's Note 4our beta 3.
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
https://androidfilehost.com/?fid=24591023225176402
Note: Thank freeza if the clean flash suggested goes as expected. His thread is in the development forum for Sprint Note 4.
Sent from my SM-N910P using Tapatalk
imsuckk said:
Same issue :/
My Steps:
1. I use a script to convert TWRP IMG file to TAR then flash to my phone. (I used twrp-2.8.7.0-trltespr.img becuause TWRP 3.0.2.0 doesn't flash onto my phone for some reason.)
2. I go onto TWRP and install SuperSu 2.74. (While flashing i see the "Boot Patch" error")
3. Boot up phone and no SU is installed so i install SuperSU from playstore and open up the app. No SU binary installed.
4. After all goes wrong I try latest CF-Root to see if it works. No luck.
5. Try to get into TWRP and receive "Android installing recovery" or something similar. Stock android recovery is installed again.
6. Repeat.
Click to expand...
Click to collapse
Ok now I had a little time. I found an old message I made for someone else with a little better detail. I forwarded it to you. Check your private messages. Plus I'm posting it here for anyone else that it may help.
aaron74 said:
AmmO0702 said:
looking for the best way to root my sprint note 4. can you help me
Click to expand...
Click to collapse
First off some things you should do before ever flashing or rooting your phone.
1. Make sure ReActivation Lock is OFF. (Its in Settings>Security>Reactivation Lock = make sure its unchecked)
2. Turn on Developer options. (Goto Settings>About device and tap Build Number 4 to 5 times; then develepers options will be in settings menu, goto that and turn on USB Debugging)
3. You'll need Official Samsung Drivers HERE! Install this to your PC!
4. Always Backup Phone!!
Now your set to Flash and Root.
IM gonna assume your on a Stock ROM. To root your gonna need to use Odin to flash TWRP, then once thats done we'll root from there.
You'll need these files :
Odin3.11 from Here. , Thanks to @LMMT, Thank him here. You'll install this to your Windows PC.
TWRP 3.0.2.0 from Here. This file is only for the Sprint Note4 SM-N910P, So that better be the phone you have!! Download and save to PC! You can Thank @bigbiff at this Thread.
Lastly you need SuperSU Here! Thanks to @Chainfire at this Thread! Download and save to your Phones SD card or Internal memory.
Now you have the files. Make sure you dont have samsung Kies running while installing or flashing your phone. Actually Dont have any other programs running when Flashing your phone.
1st - Install Samsung Drivers to your PC.
2nd - Install Odin to your PC.
3rd - Copy SuperSU zip file to your phone.
Now unplug your phone and turn it off. And open Odin Program as Admin. Now on your phone hold down the Vol down button + Home button + Power button at same time until a screen shows a Warning.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
then you'll press Volume up to continue to Download Mode.
Once in Download mode plug into usb cord to PC. Your pc should install some drivers then Odin will show your device as connected. Goto options tab in Odin and make sure all the boxes are unchecked except F. Reset Time.
Then click the log tab so we can watch the progress were gonna make. Then click the AP button and load the Twrp file you downloaded into that. If everything looks like my pic then click start. Let it do what it does, dont touch anything until it done. Once down unplug phone and take out battery for 5 seconds.
Put battery back in and press Vol up + Home + Power until phone boots into Twrp Recovery.
Once in Recovery I sugessst to do a Full Backup.
Then you can Hit Install button in Twrp and find the Super SU file you saved on phone and Install and reboot when it says. Your ROOTED!!
Hope this isnt confusing. It really isnt that hard. But Id be able to show you better in person than in writing.
Click to expand...
Click to collapse
Sorry my pics won't send. Also I see @samep mentioned that system less root won't stick on an altered kernel which I didn't know. Thanks.
aaron74 said:
Ok now I had a little time. I found an old message I made for someone else with a little better detail. I forwarded it to you. Check your private messages. Plus I'm posting it here for anyone else that it may help.
Sorry my pics won't send. Also I see @samep mentioned that system less root won't stick on an altered kernel which I didn't know. Thanks.
Click to expand...
Click to collapse
Hooked my phone up to Smart Watch and noticed I had a software update. Gonna update my phone then check back in here and try it out! Thanks!
Sent from my SM-N910P using Tapatalk
aaron74 said:
Ok now I had a little time. I found an old message I made for someone else with a little better detail. I forwarded it to you. Check your private messages. Plus I'm posting it here for anyone else that it may help.
Sorry my pics won't send. Also I see @samep mentioned that system less root won't stick on an altered kernel which I didn't know. Thanks.
Click to expand...
Click to collapse
I meant to use CF AutoRoot, one should start with stock kernel and recovery.
There has been some inexplicable loss of systemless root. I don't claim to know what is causing that but prefer the system based root in freeza's ROM.
Your help has been good. I was posting as you were. Otherwise, I may not have posted that earlier.
Sent from my SM-N910P using Tapatalk
imsuckk said:
So basically there is no CF-Root that works for MM and i just have to play the waiting game?
Wouldn't THIS CF-Root work for my ROM? Sorry for all the questions lol. Never dealt with these issues before.
Click to expand...
Click to collapse
Really do not understand why Cf-autoroot do not work for you. I rooted my device just yesterday with Odin and Cf-autoroot works just fine
Sent from my SM-N910P using XDA-Developers mobile app
aaron74 said:
Ok now I had a little time. I found an old message I made for someone else with a little better detail. I forwarded it to you. Check your private messages. Plus I'm posting it here for anyone else that it may help.
Sorry my pics won't send. Also I see @samep mentioned that system less root won't stick on an altered kernel which I didn't know. Thanks.
Click to expand...
Click to collapse
Man, I am still not rooted when I boot the phone up. Still am getting the same Boot Patch error and everything.
samep said:
I meant to use CF AutoRoot, one should start with stock kernel and recovery.
There has been some inexplicable loss of systemless root. I don't claim to know what is causing that but prefer the system based root in freeza's ROM.
Your help has been good. I was posting as you were. Otherwise, I may not have posted that earlier.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Oh ok, I must have read too fast. My bad.
I often wondered if anyone had lost root cause Yeah I lost root app a couple times with systemless root. Especially Always after I install idones unlock app I lose it. Have to reflash stock kernel and root.
I downloaded @freeza note four Rom last week. Haven't had time to install and play with it yet. I didn't know it had system root. It looks promising. I know he has done a lot for our device. As has a bunch of devs on this site. I know Ive seen your name all through here too. Thanks for all your help.
I don't claim to be a Dev but I like to hack, mod, and figure stuff out. And I've learned most the stuff I know here on XDA. So when I see someone I can help I try to give back to the community.
---------- Post added at 07:39 PM ---------- Previous post was at 07:19 PM ----------
imsuckk said:
Man, I am still not rooted when I boot the phone up. Still am getting the same Boot Patch error and everything.
Click to expand...
Click to collapse
Ok lets get to the bottom of this. Im gonna walk you through getting a fresh stock boot image and then rooting it.
First do you mean when you start your phone it says that?
Or when you go to flash cf autoroot it shows that?
And Can you boot into TWRP recovery?
aaron74 said:
Oh ok, I must have read too fast. My bad.
I often wondered if anyone had lost root cause Yeah I lost root app a couple times with systemless root. Especially Always after I install idones unlock app I lose it. Have to reflash stock kernel and root.
I downloaded @freeza note four Rom last week. Haven't had time to install and play with it yet. I didn't know it had system root. It looks promising. I know he has done a lot for our device. As has a bunch of devs on this site. I know Ive seen your name all through here too. Thanks for all your help.
I don't claim to be a Dev but I like to hack, mod, and figure stuff out. And I've learned most the stuff I know here on XDA. So when I see someone I can help I try to give back to the community.
---------- Post added at 07:39 PM ---------- Previous post was at 07:19 PM ----------
Ok lets get to the bottom of this. Im gonna walk you through getting a fresh stock boot image and then rooting it.
First do you mean when you start your phone it says that?
Or when you go to flash cf autoroot it shows that?
And Can you boot into TWRP recovery?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
When I flash SuperSU it says that, and yes i am able to get into TWRP still.
imsuckk said:
When I flash SuperSU it says that, and yes i am able to get into TWRP still.
Click to expand...
Click to collapse
ok AWEsome. Where gonna see if a copy of your stock kernal is on your phone.
1. Boot into Recovery, Click Advanced, and then File Manager
you should now see the root of your .file system. Click on the Data folder and scroll down do you see a file that start with stock_boot_?
aaron74 said:
ok AWEsome. Where gonna see if a copy of your stock kernal is on your phone.
1. Boot into Recovery, Click Advanced, and then File Manager
you should now see the root of your .file system. Click on the Data folder and scroll down do you see a file that start with stock_boot_?
Click to expand...
Click to collapse
I do not see that. It could be that I just did a fresh update to PE2 and have a totally fresh ROM (with TWRP installed)
imsuckk said:
I do not see that. It could be that I just did a fresh update to PE2 and have a totally fresh ROM (with TWRP installed)
Click to expand...
Click to collapse
Ok Im gonna PM you so not to fill this thread with bunch of mess
aaron74 said:
Ok Im gonna PM you so not to fill this thread with bunch of mess
Click to expand...
Click to collapse
Alright thanks man!
Sent from my SM-N910P using Tapatalk
imsuckk said:
Alright thanks man!
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Besides the stuff we disgust. If that dont work. You could install a pre rooted rom. Or if you really want to figure out why it wasnt working.
I would start with clean slate and download the PE2 tar. Wipe phone and flash it. Reinstall Twrp and Supersu.
Hope it works! Have to get off here for awhile!!
Let me know if you got it!
Will the same method work on pj1 ?

[HELP] I can't get Oxygen OS 3.2.1 to install on my phone

Hello,
I've tried everything that the internet has to offer so far and still can't get the newest version to install on my phone without failing somewhere in the installation process.
I feel like asking for help isn't of much use, because it could be everything.
I tried resetting the phone completely with this guide: http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
After that I wanted to install the update again, and still no success.
Next time you make a thread regarding an issue be kind enough to tell us the state of your phone to the best of your knowledge, whether its working or not? does it show the oneplus logo or not..... these things matter plenty!
judging from the what you have mentioned in your post, your main issues is not being able to install the latest update.
try these steps
1. download this file https://www.androidfilehost.com/?fid=24591000424945019 [thanks to namman bhalla for his thread, http://forum.xda-developers.com/oneplus-3/how-to/mirrors-official-oxygen-os-roms-ota-t3410870]
2. copy and paste it onto your phone.
3. now boot into your phones recovery twrp preferred
4. from there choose the option which says..... click install new zip. and select the zip that you downloaded....
it should work if it doesn't, give us a detailed description of what and all you have done with your phone whether you have unlocked the bootloader, whether there is a custom recovery installer and most importantly whether you have nandroid backup of your device.
ajaysoranam said:
Next time you make a thread regarding an issue be kind enough to tell us the state of your phone to the best of your knowledge, whether its working or not? does it show the oneplus logo or not..... these things matter plenty!
judging from the what you have mentioned in your post, your main issues is not being able to install the latest update.
try these steps
1. download this file https://www.androidfilehost.com/?fid=24591000424945019 [thanks to namman bhalla for his thread, http://forum.xda-developers.com/oneplus-3/how-to/mirrors-official-oxygen-os-roms-ota-t3410870]
2. copy and paste it onto your phone.
3. now boot into your phones recovery twrp preferred
4. from there choose the option which says..... click install new zip. and select the zip that you downloaded....
it should work if it doesn't, give us a detailed description of what and all you have done with your phone whether you have unlocked the bootloader, whether there is a custom recovery installer and most importantly whether you have nandroid backup of your device.
Click to expand...
Click to collapse
I tried using that method and it failed, I can get into recovery just fine and my bootloader is unlocked because I flashed twrp
I have a backup I made in twrp.
I got the official support tool (MsMDownloadTool) and I could restore my phone to 3.1.2 but it still crashes apps and is very unstable.
If I now try to install the update again, or try to flash the full OxygenOS 3.2.1 or 3.1.2 I get the Error 7 ("system partition has unexpected contents").
I dont get this error because the system partition couldnt have been modified, because I didnt even start the phone , I just got into recovery and tried updating it.
I'm losing my mind on this.
Sorry if that was a ramble and isn't understandable
calm down!
boot into twrp, wipe system ,data, cache, dalvik. now try flashing the latest full rom i.e. 3.2.2.
try this and let me know....
if it didn't work give me step by breakdown of what you did.....
DeadlyVirez said:
I tried using that method and it failed, I can get into recovery just fine and my bootloader is unlocked because I flashed twrp
I have a backup I made in twrp.
I got the official support tool (MsMDownloadTool) and I could restore my phone to 3.1.2 but it still crashes apps and is very unstable.
If I now try to install the update again, or try to flash the full OxygenOS 3.2.1 or 3.1.2 I get the Error 7 ("system partition has unexpected contents").
I dont get this error because the system partition couldnt have been modified, because I didnt even start the phone , I just got into recovery and tried updating it.
I'm losing my mind on this.
Sorry if that was a ramble and isn't understandable
Click to expand...
Click to collapse

Stuck at "Patching System Image Unconditionally" when flashing CM12.1 via TWRP

Stuck at "Patching System Image Unconditionally" when flashing CM12.1 via TWRP
Just got a Note 4, proceeding with the usual root and installation CyanogenMod ASAP
Everything was going smoothly until the actual flashing of CyanogenMod, whenever I try to flash it, it just gets stuck on "patching system image unconditionally" and doesn't progress beyond that point
Steps I've taken so far:
1) unboxed phone, was running Android 6.0 (I think, maybe 6.0.1)
2) Rooted with Chainfire's Auto Root
3) Flashed TWRP 3.0.2-0 via Odin 3.09 as per TWRP's instructions
4) Ensured that I could boot both to the stock ROM and TWRP
5) Copied cm12.1 and gapps to Note 4's internal storage (sd card hasn't come in yet, normally I put it onto sd card)
6) Did default factory wipe from TWRP
7) Attempted to flash cm12.1, ran into issue
I didn't make a backup of the stock ROM so now the phone has a recovery but no actual OS, as I had to pull the battery out to get it to do anything beyond being stuck at the patching system image step
I'm redownloading cm12.1 in case maybe there was a problem with the .zip itself, I know it's bad practice but I never check md5 sums
I've found other threads that suggested flashing the stock ROM for some reason, but they were for other phones and I'm not sure if it's related to the Note 4.
I've seen some mention of the bootloader being locked, but I don't know how to tell if the bootloader is locked or not. I see the same exact boot screen that I saw with my Note 3, S4, S3, etc. Could the issue be the bootloader?
I've also found this thread, but I can't get TWRP to mount in Windows, it keeps saying the driver failed to install. MTP transfers worked fine with the stock ROM was still there, but for some reason it doesn't work with the Mount option in TWRP. I'm downloading the Android SDK so I can try using adb
If anyone else has run into this, can you advise me on what to do from here?
EDIT: Nevermind, fixed it. Changed system partition's filesystem to F2FS via TWRP, and this allowed CM and gapps to flash with no issue. Now booted into CM But hopefully this will be helpful if anyone else has this issue
EDIT2: Buuuuut now the WiFi's not working. It just gets stuck at "turn on WiFi" but nothing actually turns on, and the on/off button for WiFi in settings is grayed out. IT NEVER ENDS
CyanogenMod Thread
Reddit Thread
EDIT3:
WiFi and Settings Issue seems to be resolved
I think the problem had something to do with the baseband version
As per Trex's post (http://forum.xda-developers.com/showpost.php?p=69520362&postcount=2), I had to revert back to the OK1 baseband
Now everything seems to work fine
As for TWRP not working and just going to a black screen, I redownloaded it from the TWRP website and it worked fine
So now both TWRP and CM are installed and working, WiFi works, and Settings don't crash.
Now I've encountered an issue where the camera doesn't focus, and I'm wondering if there's still some plastic film on the camera lens, but I've been picking at it and nothing is coming off and I'm afraid of damaging the plastic if I keep trying...
AbuFiraas said:
Just got a Note 4, proceeding with the usual root and installation CyanogenMod ASAP
Everything was going smoothly until the actual flashing of CyanogenMod, whenever I try to flash it, it just gets stuck on "patching system image unconditionally" and doesn't progress beyond that point
Steps I've taken so far:
1) unboxed phone, was running Android 6.0 (I think, maybe 6.0.1)
2) Rooted with Chainfire's Auto Root
3) Flashed TWRP 3.0.2-0 via Odin 3.09 as per TWRP's instructions
4) Ensured that I could boot both to the stock ROM and TWRP
5) Copied cm12.1 and gapps to Note 4's internal storage (sd card hasn't come in yet, normally I put it onto sd card)
6) Did default factory wipe from TWRP
7) Attempted to flash cm12.1, ran into issue
I didn't make a backup of the stock ROM so now the phone has a recovery but no actual OS, as I had to pull the battery out to get it to do anything beyond being stuck at the patching system image step
I'm redownloading cm12.1 in case maybe there was a problem with the .zip itself, I know it's bad practice but I never check md5 sums
I've found other threads that suggested flashing the stock ROM for some reason, but they were for other phones and I'm not sure if it's related to the Note 4.
I've seen some mention of the bootloader being locked, but I don't know how to tell if the bootloader is locked or not. I see the same exact boot screen that I saw with my Note 3, S4, S3, etc. Could the issue be the bootloader?
I've also found this thread, but I can't get TWRP to mount in Windows, it keeps saying the driver failed to install. MTP transfers worked fine with the stock ROM was still there, but for some reason it doesn't work with the Mount option in TWRP. I'm downloading the Android SDK so I can try using adb
If anyone else has run into this, can you advise me on what to do from here?
EDIT: Nevermind, fixed it. Changed system partition's filesystem to F2FS via TWRP, and this allowed CM and gapps to flash with no issue. Now booted into CM But hopefully this will be helpful if anyone else has this issue
EDIT2: Buuuuut now the WiFi's not working. It just gets stuck at "turn on WiFi" but nothing actually turns on, and the on/off button for WiFi in settings is grayed out. IT NEVER ENDS
Click to expand...
Click to collapse
You must flash 5.1.1 ok1 bootloader to get wifi work
I suggest you first flash 5.1.1 firmware in odin
Then flash twrp. Tar file in odin.
Then make full wipe
Flash cm rom + gapps
You will get clean rom install without any errors
Hope this will help
Trex888 said:
You must flash 5.1.1 ok1 bootloader to get wifi work
I suggest you first flash 5.1.1 firmware in odin
Then flash twrp. Tar file in odin.
Then make full wipe
Flash cm rom + gapps
You will get clean rom install without any errors
Hope this will help
Click to expand...
Click to collapse
Okay I'll give that a shot. Are "5.11 ok1 bootloader" and "5.1.1 firmware" the same thing? And do you know where I can find it/them?
Just flashed OK1 via Odin via this thread, but it's just boot looping over and over
EDIT: Did a simple factory wipe and it's working fine now. Currently running unrooted Stock 5.1.1, Baseband N910PVPS4COK1. So I'm basically starting from the beginning, whereas before it was on 6.0 but now it's 5.1.1
Am now rooted but I can't get TWRP installed, I flash it and try to boot to recovery but it just boots to a black screen
Issue seems to be resolved, edited original post
AbuFiraas said:
Okay I'll give that a shot. Are "5.11 ok1 bootloader" and "5.1.1 firmware" the same thing? And do you know where I can find it/them?
Click to expand...
Click to collapse
Go to download mode and check exact model number
Tell me model number and i give you links for bootloader and firmware
Trex888 said:
Go to download mode and check exact model number
Tell me model number and i give you links for bootloader and firmware
Click to expand...
Click to collapse
It's working now, I found another post that had all the various stock firmwares on there. Now the issue I'm having is that my camera doesn't focus at all, but I don't know if it's a hardware or software issue. I never checked the camera before rooting the first time. Gonna try going back to unrooted stock again but if that doesn't change anything, I might have to take it to a Sprint store and get a replacement. Hopefully they don't notice the KNOX trip... lol

Please help me save my phone

FAILED (Do not allow to flash Bootloader image on Unlock device) & TWRP - Failed to mount '/firmware' (invalid argument)
I'm using the Lenovo p2a42 32gb 3gb version (India)
My phone is stuck in fastboot mode. Bootloader is unlocked.
I have the latest twrp - 3.2.2.0 as recovery.
I flashed everything except the modem and bootloader to stock.
Bootloader & modem wont flash - cannot flash unlocked bootloader error.
I have tried everything I can think of:
1. Restore to stock 7.1 (cannot flash bootloader error)
2. Relock Bootloader (not allowed error)
3. Even gave my phone to a repair guy as last resort.
No luck yet.
Its 17000 bucks worth.
And has been laid to waste due to my ****up.
I really want to repair it myself if possible.
Please help me if you can. I'm open to any and all ideas.
Thanks in advance.
Alright mate,
Download this HERE
Extract it.
Boot phone into bootloader/fastboot mode.
Connect it via cable.
Run flashall - stock reco.bat and wait until it is done. Your phone will reboot on its own.
Gimme some details if it doesn't work. Don't worry, it'll be fine.#
Also: NEVER RELOCK THE BOOTLOADER VIA COMMAND, that is a sure-way to **** it up much more.
sm00th4f3 said:
Alright mate,
Download this HERE
Extract it.
Boot phone into bootloader/fastboot mode.
Connect it via cable.
Run flashall - stock reco.bat and wait until it is done. Your phone will reboot on its own.
Gimme some details if it doesn't work. Don't worry, it'll be fine.#
Also: NEVER RELOCK THE BOOTLOADER VIA COMMAND, that is a sure-way to **** it up much more.
Click to expand...
Click to collapse
https://forum.xda-developers.com/lenovo-p2/help/stuck-bootloop-reboots-15-holding-power-t3837278
would it work for me?
LeonDsouza123 said:
https://forum.xda-developers.com/lenovo-p2/help/stuck-bootloop-reboots-15-holding-power-t3837278
would it work for me?
Click to expand...
Click to collapse
Seems like you have a faulty battery or something on your hardware side.
Fun fact: getting into recovery(twrp) is done via Fastboot since the button combo is a ***** and isn't reliable. The timing is too stupid done.
The one team rescue files always work as long as you're in Fastboot/bootloader mode.
It's worth the try
I can't thank you enough @sm00th4f3
You are my saviour. It worked perfectly & my phone is working now.
Thank you sooooo much & keep up the good work.
MadMelman said:
I can't thank you enough @sm00th4f3
You are my saviour. It worked perfectly & my phone is working now.
Thank you sooooo much & keep up the good work.
Click to expand...
Click to collapse
Glad it worked
I restored the stock firmware.
My phone boots to the start screen , after I select the language it's unable to detect or connect to the wifi or to the mobile network.
Therfore I cannot proceed to finish the setup.
TWRP shows a firmware error-
- failed to mount '/firmware' (invalid argument)
Please advice @sm00th4f3
MadMelman said:
I restored the stock firmware.
My phone boots to the start screen , after I select the language it's unable to detect or connect to the wifi or to the mobile network.
Therfore I cannot proceed to finish the setup.
TWRP shows a firmware error-
- failed to mount '/firmware' (invalid argument)
Please advice @sm00th4f3
Click to expand...
Click to collapse
You shouldn't restore stock firmware from backup.
After using rescue tool.
Setup your phone from zero.
Or skip through setup.
Reboot to bootloader.
Flash latest twrp 3.2.3 can be found on official website
Change data system format to ext4 if it's not already.
Wipe system, data, cache and dalvik
Flash custom ROM of your choice
Flash gapps
flash magisk for root if you need it
Wipe dalvik and cache
Reboot.
Setup phone.
sm00th4f3 said:
You shouldn't restore stock firmware from backup.
After using rescue tool.
Setup your phone from zero.
Or skip through setup.
Reboot to bootloader.
Flash latest twrp 3.2.3 can be found on official website
Change data system format to ext4 if it's not already.
Wipe system, data, cache and dalvik
Flash custom ROM of your choice
Flash gapps
flash magisk for root if you need it
Wipe dalvik and cache
Reboot.
Setup phone.
Click to expand...
Click to collapse
I followed your instructions. No luck yet.
After flashing the custom rom, the phone bootlooped.
I changed the data & system to ext4 , I get the failed to mount firmware error.
SCREENSHOT:
https://drive.google.com/file/d/1dhBIadnV-olRsWbQjeL8teoPCJeg2U2L/view?usp=sharing
MadMelman said:
I followed your instructions. No luck yet.
After flashing the custom rom, the phone bootlooped.
I changed the data & system to ext4 , I get the failed to mount firmware error.
SCREENSHOT:
https://drive.google.com/file/d/1dhBIadnV-olRsWbQjeL8teoPCJeg2U2L/view?usp=sharing
Click to expand...
Click to collapse
You really are new to this.
Use the rescue tool.
Let the phone boot.
Skip through setup.
Enable developer options.
Make sure and debugging is enabled.
Connect phone to pc.
Grant always access , which popups on phone.
Open a CMD, in the folder of your adb tools.
Use adb reboot bootloader.
Or use the button combo to get to bootloader /Fastboot mode
Flash twrp.
Boot twrp
Reboot to recovery twrp via reboot menu
Change file system of data to ext4
Reboot to recovery again via reboot menu in twrp.
Now use factory reset, then wipe system partition.
Flash custom ROM
Gapps
Magisk if wanted.
Reboot.
Wait max 10min.
Should work.
sm00th4f3 said:
You really are new to this.
Use the rescue tool.
Let the phone boot.
Skip through setup.
Enable developer options.
Make sure and debugging is enabled.
Connect phone to pc.
Grant always access , which popups on phone.
Open a CMD, in the folder of your adb tools.
Use adb reboot bootloader.
Or use the button combo to get to bootloader /Fastboot mode
Flash twrp.
Boot twrp
Reboot to recovery twrp via reboot menu
Change file system of data to ext4
Reboot to recovery again via reboot menu in twrp.
Now use factory reset, then wipe system partition.
Flash custom ROM
Gapps
Magisk if wanted.
Reboot.
Wait max 10min.
Should work.
Click to expand...
Click to collapse
I 'm new to this & I appreciate your help, but
I followed your instructions again yet the error remains the same.
My phone is not detecting any wifi or cellular data - so I cant proceed /skip the process of setting up my stock phone.
And when i flashed the custom rom, the firmware error shows up.
And believe me I've tried a lot, but it just wont work.
I've come too far to give up now, any suggestions?
Here is the screenshot:
https://drive.google.com/file/d/12VTE6xs1Kozg52DhQP3fgBbNeDptXz2j/view?usp=sharing
MadMelman said:
I 'm new to this & I appreciate your help, but
I followed your instructions again yet the error remains the same.
My phone is not detecting any wifi or cellular data - so I cant proceed /skip the process of setting up my stock phone.
And when i flashed the custom rom, the firmware error shows up.
And believe me I've tried a lot, but it just wont work.
I've come too far to give up now, any suggestions?
Here is the screenshot:
https://drive.google.com/file/d/12VTE6xs1Kozg52DhQP3fgBbNeDptXz2j/view?usp=sharing
Click to expand...
Click to collapse
Before flashing twrp.
Use Fastboot oem unlock
.
Try again without custom ROM this time .
I'm looking into it.
Still stuck at the start screen,
I might be wrong but here is what I think is wrong with the phone:
The modem just won't flash therefore no wifi or cellular data.
The firmware is corrupted.
Thanks for your continued support.
MadMelman said:
Still stuck at the start screen,
I might be wrong but here is what I think is wrong with the phone:
The modem just won't flash therefore no wifi or cellular data.
The firmware is corrupted.
Thanks for your continued support.
Click to expand...
Click to collapse
Hello, well i messed up my phone really bad. deleted the bootloader. Phone wasnt working. But then used blank flash to get things working again. Just that it only charges now when i run it in bootloader mode. Now what i think u can do is delete all partitions using fastboot. I dont know the terms or words to say, but you can try to delete all partitions and then flash them again and check. use the stock files or what you call those emmc, modem and those bin files that is used to flash via fastboot. It may help but can be risky. Well hope this makes any sense
Ryan Robert said:
Hello, well i messed up my phone really bad. deleted the bootloader. Phone wasnt working. But then used blank flash to get things working again. Just that it only charges now when i run it in bootloader mode. Now what i think u can do is delete all partitions using fastboot. I dont know the terms or words to say, but you can try to delete all partitions and then flash them again and check. use the stock files or what you call those emmc, modem and those bin files that is used to flash via fastboot. It may help but can be risky. Well hope this makes any sense
Click to expand...
Click to collapse
there is no need to erase your partitions.. Unless you want to brick your device for real.
But you can try it at your own discretion at risk.
i won't help any further since i don't know that much more concerning this kinda problem.
cheers
Fatal Error
MadMelman said:
I 'm new to this & I appreciate your help, but
I followed your instructions again yet the error remains the same.
My phone is not detecting any wifi or cellular data - so I cant proceed /skip the process of setting up my stock phone.
And when i flashed the custom rom, the firmware error shows up.
And believe me I've tried a lot, but it just wont work.
I've come too far to give up now, any suggestions?
Here is the screenshot:
https://drive.google.com/file/d/12VTE6xs1Kozg52DhQP3fgBbNeDptXz2j/view?usp=sharing
Click to expand...
Click to collapse
Hey buddy, I recently ran into same problem as yours. Have you found any working fix for this issue?
Please reply.

Categories

Resources