Help with booting problems? - Sprint Galaxy Note 4 Q&A, Help & Troubleshooting

Hello,
I just noticed something the other day and I do not know if this has any effect on my problem with the phone getting a usb not recognized error so I wanted inquire!
So I did a completely clean install of the [ROM] [Touchwiz-PC1,PD1] [100% Stock, Root, No KNOX, No Itson] [4/5/2016] deodox rom and have noticed that my boot screen no longer shows multiple lines while booting. The only thing I get now is:
Set Warranty Bit : Kernel
Before I would get that and several other lines including one about Knox. I also do not get the Sprint logo as one of the bootup screens. My question is, is this rom suppose to do this or did I do something wrong? I followed the directions 100%. I also notice that I also now get an error that it cannot do a fingerprint unlock on boot and I have to enter my emergency password.
Last but not least, if there is a problem. Is there anyway to put a OG5 rom on my micro sd card (I have a card reader I can put the micro sd card into to transfer files, I cannot odin) and restore it to then?
Thanks for any help!

Most of what you describe is not abnormal.
Your fingerprint may be data left over from Lollipop. Try deleting your fingerprints and add them back.
Be aware, if you factory reset, you'll need to flash systemless root again. Google search SuperSU zip if you need it; it's also linked in the ROM thread. If you factory reset for any reason, make sure you don't keep our have a folder in root folder named /carrier/ItsOn. The apk in that folder could activate causing numerous reboot prompts to complete activation.
Eventually, you're going to need access to a PC to do what you want. You might be stuck and unable to update; modified partitions can cause the failure to update on OTA and KIES. Custom stockish ROMs are coming but they won't be for PD1; it's already outdated.
You can't go back to Lollipop without a PC because you need to revert your bootloader to Android 5.1 to run that ROM. Without a TWRP backup to restore, you should also Odin the full stock tar rather than just the bootloader.
Sent from my SM-N910P using Tapatalk

samep said:
Most of what you describe is not abnormal.
Your fingerprint may be data left over from Lollipop. Try deleting your fingerprints and add them back.
Be aware, if you factory reset, you'll need to flash systemless root again. Google search SuperSU zip if you need it; it's also linked in the ROM thread. If you factory reset for any reason, make sure you don't keep our have a folder in root folder named /carrier/ItsOn. The apk in that folder could activate causing numerous reboot prompts to complete activation.
Eventually, you're going to need access to a PC to do what you want. You might be stuck and unable to update; modified partitions can cause the failure to update on OTA and KIES. Custom stockish ROMs are coming but they won't be for PD1; it's already outdated.
You can't go back to Lollipop without a PC because you need to revert your bootloader to Android 5.1 to run that ROM. Without a TWRP backup to restore, you should also Odin the full stock tar rather than just the bootloader.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I have a PC, the problem is that it will no longer recognize my phone by USB. It always gives the USB not recognized error. I do have a folder in root called carrier but when I try to go into it with root it tells me my phone is not rooted. This does not make sense as my phone is rooted , per the installtion of the rom and I have other apps I have given root access too.
Arrg! Thanks for the info, any more will help greatly!

h4kudoshi said:
I have a PC, the problem is that it will no longer recognize my phone by USB. It always gives the USB not recognized error. I do have a folder in root called carrier but when I try to go into it with root it tells me my phone is not rooted. This does not make sense as my phone is rooted , per the installtion of the rom and I have other apps I have given root access too.
Arrg! Thanks for the info, any more will help greatly!
Click to expand...
Click to collapse
Did you enable developer options (tap build # in Settings/About device 7 times or more until enabled) and enable USB debugging in developer options?
Yes you should be able to detect device when you plug in to PC but you may not see COM connected in Odin without USB debugging.
If it's always not detecting, could be bad USB cable (broken out missing data lines) or bad PC USB port. Try others first, if that's the case. Hardware failure is rare but has been reported as suspect. Hopefully, it's simple rather than that.
Sent from my SM-N910P using Tapatalk

Related

Factory Restore an Encrypted Galaxy S3

Model: Samsung Galaxy S3 AT&T i747
Hi!
I was forced to encrypt my galaxy s3 in order to receive corporate emails on my phone using the stock email app. However I never imagined that encrypting the phone would literally lock the memory and options to customize the phone.
I tried to root the phone to benefit from more flexibility and also debloat the phone. However during the rooting process, I could not mount /emmc/ when using ClockWorkRecovery in the startup menu. Based on what I found on the web, I figured it was due to the encryption.
I then tried to factory reset the phone to get rid of the encryption but I simply can't hard reset the phone from the OS or the startup menu. When doing the reset from the startup menu, the errors are "Can't mount /sdcard/". The reset continues but when the phone reboots, all my applications and personal data are there and the phone is still encrypted.
I read a lot about flashing a custom recovery via flashboot or ADB but I am reluctant to do it without guidance from the experts (you guys).
I deleted my corporate email account (It is my personal phone, I am not required to install exchange on it).
I tried to use an external sd card but as soon as the phone recoginizes it, I have to encrypt the card as well as a result from the corporate policies. I ejected the card and did not encrypt it.
I am new to android (long time iPhone user) and I would really appreciate your guidance on the methods to factory reset my phone or a different technique to get rid of the encryption because I am really stuck right now.
I have never encrypted an Android phone before. But maybe your response to these questions will serve as a "bump" to this thread.
1) What method did you use to encrypt the phone? Stock or 3rd party encryption?
2) Doesn't that same method also offer you the offer to unencrypt the phone?
3) If you used a stock method of encrypting the phone, then I'd assume your provider (AT&T?) tech support should be able to help you unencrypt it.
Eddie,
Thanks for your response.
1) I used stock method for encryption
2) Decrypt the phone is not possible apparently,only way is to factory restore the phone apparently
3) I went to the AT&T store and they were unable to factory restore (using the standard methods). They offered an exchange but since I purchase over the phone at a discounted price, I have to do the exchange using that method. Before shipping back the phone, I was wondering if I could fix it myself with the help of knowledgeable people.
CZ Eddie said:
I have never encrypted an Android phone before. But maybe your response to these questions will serve as a "bump" to this thread.
1) What method did you use to encrypt the phone? Stock or 3rd party encryption?
2) Doesn't that same method also offer you the offer to unencrypt the phone?
3) If you used a stock method of encrypting the phone, then I'd assume your provider (AT&T?) tech support should be able to help you unencrypt it.
Click to expand...
Click to collapse
I have never used the encryption but if the phone can turn on and is usable, cant you go into the encryption settings and turn encryption off? then you should be able to do anything (may be best to start with a factory restore first just so you have a fresh slate to work with)
1ofAKind said:
Model: Samsung Galaxy S3 AT&T i747
Hi!
I was forced to encrypt my galaxy s3 in order to receive corporate emails on my phone using the stock email app. However I never imagined that encrypting the phone would literally lock the memory and options to customize the phone.
I tried to root the phone to benefit from more flexibility and also debloat the phone. However during the rooting process, I could not mount /emmc/ when using ClockWorkRecovery in the startup menu. Based on what I found on the web, I figured it was due to the encryption.
I then tried to factory reset the phone to get rid of the encryption but I simply can't hard reset the phone from the OS or the startup menu. When doing the reset from the startup menu, the errors are "Can't mount /sdcard/". The reset continues but when the phone reboots, all my applications and personal data are there and the phone is still encrypted.
I read a lot about flashing a custom recovery via flashboot or ADB but I am reluctant to do it without guidance from the experts (you guys).
I deleted my corporate email account (It is my personal phone, I am not required to install exchange on it).
I tried to use an external sd card but as soon as the phone recoginizes it, I have to encrypt the card as well as a result from the corporate policies. I ejected the card and did not encrypt it.
I am new to android (long time iPhone user) and I would really appreciate your guidance on the methods to factory reset my phone or a different technique to get rid of the encryption because I am really stuck right now.
Click to expand...
Click to collapse
1ofaKind,
Had EXACTLY the same thing happen to me. Encrypted my S3 in order to access work exchange server. Tried CWM but cannot mount /emmc/ problem after booting into recovery. Have not tried to factory reset yet as I am wanting to learn more before I go that route. But basically I am in the same boat as you. The only difference is I was not required to encrypt an external SD card when I put it in my phone. Read about flashboot as well...maybe the only way to actually factory reset after encryption??
Sorry I cannot offer any solutions at the moment...but I will keep scouring the forums looking for a way.
If I learn something valuable, I will try to post it here to help ya out.
EDIT: Maybe you have read these threads, but there is some decent info in them. http://forum.xda-developers.com/showthread.php?t=1451655 & http://forum.xda-developers.com/showthread.php?t=1392037
good luck
Look into using Odin to restore a factory image.
Sent from my SAMSUNG-SGH-I747 using xda premium
I'm in the same boat here - had to encrypt my GS3 in order to receive corporate (Exchange Server) emails. Now can't update the OS on the phone which is more important to me than receiving corporate emails on the device.
Can someone tell me how to decrypt (UN-encrypt) the phone? Everything I've read says that a factory reset won't do it.
Please help!
CZ Eddie said:
Look into using Odin to restore a factory image.
Click to expand...
Click to collapse
Has anyone tried this? If so, did it work?
I clicked install rom from sd card in cwm selected f/w which i had copied into internal memory. Did factory reset in recovery.
Odin it back to stock.
This might be too late to help you guys, but here's what worked for me. I odined it back to stock. Then I went into recovery (volume down, power and home button) and selected wipe data/factory reset. This does of course erase all your data, so try to copy whatever you can onto a computer or something before doing this. You should end up with an unencrypted storage.
sid9102 said:
This might be too late to help you guys, but here's what worked for me. I odined it back to stock. Then I went into recovery (volume down, power and home button) and selected wipe data/factory reset. This does of course erase all your data, so try to copy whatever you can onto a computer or something before doing this. You should end up with an unencrypted storage.
Click to expand...
Click to collapse
ODIN will not recognize my phone when it is in download mode ...
tamon77 said:
ODIN will not recognize my phone when it is in download mode ...
Click to expand...
Click to collapse
After you hit start, unplug then replug the usb from the computer. I had some issues with it not recognizing it either to flash stock, but when i messed with the cord, it made the noise that i unplugged and it started working. Same thing with the root injected, only this time i fully unplugged it when the fiddling with it didnt work. Make sure you replace it into the same com port.
so, i seem to be having the same problem as all of you, only i encrypted to protect my data from agents. So, right now, i am *hopefully* :fingers-crossed: installing the root injected JB now. I had many issues. TWRP and CWM were no help, couldnt see phone to add new roms to it. ODIN was the only hope. I booted into recovery after going back to stock, did a new factory reset and am installing the stock with root. When i let it boot, it didnt go to encryption this time, but the first time i flashed the stock, it did. This is a mess to say the least.
EDIT: YEAH! done. No encryption and i got root. i used the image from here: http://forum.xda-developers.com/showthread.php?t=1968625 DLK3 worked for me. Good luck. i hope this helps. Ill be happy to explain more if you want.
tamon77 said:
ODIN will not recognize my phone when it is in download mode ...
Click to expand...
Click to collapse
ODIN (for me at least) wont see anything since im using Windows 8. On Windows 7, however, it works just fine.
Factory reset encrypted phone
hi,
I'm using CM11 as a rom.
I didn't want to reinstall stock rom, just to root it again later.
Installing updated version from external SD didn't work (updated the ROM but no decryption)
Tried to factory reset from recovery - didn't work, as the internal storage is encrypted it can't mount /sdcard/
however, from within settings menu, in backup&restore there's an option to do a factory reset - this is formatting internal memory altogether.
worked like a charm.
oxidase said:
After you hit start, unplug then replug the usb from the computer. I had some issues with it not recognizing it either to flash stock, but when i messed with the cord, it made the noise that i unplugged and it started working. Same thing with the root injected, only this time i fully unplugged it when the fiddling with it didnt work. Make sure you replace it into the same com port.
so, i seem to be having the same problem as all of you, only i encrypted to protect my data from agents. So, right now, i am *hopefully* :fingers-crossed: installing the root injected JB now. I had many issues. TWRP and CWM were no help, couldnt see phone to add new roms to it. ODIN was the only hope. I booted into recovery after going back to stock, did a new factory reset and am installing the stock with root. When i let it boot, it didnt go to encryption this time, but the first time i flashed the stock, it did. This is a mess to say the least.
EDIT: YEAH! done. No encryption and i got root. i used the image from here: http://forum.xda-developers.com/showthread.php?t=1968625 DLK3 worked for me. Good luck. i hope this helps. Ill be happy to explain more if you want.
Click to expand...
Click to collapse
I understand this is very old but I am going to make a note here in case anyone else gets into this problem. When you go back to stock, do the factory reset using the STOCK recovery. Don't install TWRP or anything else until you have cleared the encryption. At least, that's what worked for me.

Stuck in recovery loop after failed 5.1 update

Hello –
I have an HTC One M9 (AT&T) which is stock and unrooted. Apparently a failed 5.1 update while traveling abroad has caused my phone to get stuck in recovery mode. Rebooting the phone or powering down simply brings the phone back to recovery. I am hoping there might be a way to update a stock ROM or force an OTA update without losing any of the internal data on the phone. Alternatively I was hoping I could pull the photos from the phone before wiping or returning the phone.
My only options on this screen are to:
reboot system now; apply update from ADB; wipe data/factory reset; wipe cache partition; reboot to bootloader; power down; view recovery logs; apply from phone storage; apply from sd card
I have tried all options multiple times, but I have not tried a factory reset because all of my pictures from my trip are still on the internal memory of the phone.
Unfortunately I never enabled USB debugging before the device failure, so I believe my options with ADB and “pulling” the files are limited. Nonetheless, my phone won’t communicate effectively with my PC or laptop while in recovery mode, my PC and laptop only recognize that an Android device is connected while in bootloader or download mode.
I have been told by HTC that my only option is to download and update the ROM that is available on their website to the phone, but this will erase all data on my phone.
Is there any other possible option for me that can kick my phone out of recovery mode, or extract the photos from the internal storage? Is there a different ROM or OTA update I can use that will retain my data once installed?
Thanks!
awhaley3 said:
Hello –
I have an HTC One M9 (AT&T) which is stock and unrooted. Apparently a failed 5.1 update while traveling abroad has caused my phone to get stuck in recovery mode. Rebooting the phone or powering down simply brings the phone back to recovery. I am hoping there might be a way to update a stock ROM or force an OTA update without losing any of the internal data on the phone. Alternatively I was hoping I could pull the photos from the phone before wiping or returning the phone.
My only options on this screen are to:
reboot system now; apply update from ADB; wipe data/factory reset; wipe cache partition; reboot to bootloader; power down; view recovery logs; apply from phone storage; apply from sd card
I have tried all options multiple times, but I have not tried a factory reset because all of my pictures from my trip are still on the internal memory of the phone.
Unfortunately I never enabled USB debugging before the device failure, so I believe my options with ADB and “pulling” the files are limited. Nonetheless, my phone won’t communicate effectively with my PC or laptop while in recovery mode, my PC and laptop only recognize that an Android device is connected while in bootloader or download mode.
I have been told by HTC that my only option is to download and update the ROM that is available on their website to the phone, but this will erase all data on my phone.
Is there any other possible option for me that can kick my phone out of recovery mode, or extract the photos from the internal storage? Is there a different ROM or OTA update I can use that will retain my data once installed?
Thanks!
Click to expand...
Click to collapse
You could unlock through HTCdev and flash twrp recovery. Once booted into TWRP you should be able to see your phone from your computer, the same as you would if it was booted into the OS. Steps 1-5 here will walk you through what i'm talking about (see post #3).
http://forum.xda-developers.com/one-m9/help/m9-5-1-os-rootable-t3159710
BUT...You probably need to weigh how important the stuff you'll lose is to you because unlocking *could* cause issues if you need to send for repair or warranty swap.
jollywhitefoot said:
You could unlock through HTCdev and flash twrp recovery. Once booted into TWRP you should be able to see your phone from your computer, the same as you would if it was booted into the OS. Steps 1-5 here will walk you through what i'm talking about (see post #3).
http://forum.xda-developers.com/one-m9/help/m9-5-1-os-rootable-t3159710
BUT...You probably need to weigh how important the stuff you'll lose is to you because unlocking *could* cause issues if you need to send for repair or warranty swap.
Click to expand...
Click to collapse
Thank you very much for the instructions. I believe I may try to go this route, but to be sure, step #1 (unlocking the bootloader) in your link says that the unlocking process will wipe the internal storage? Is this correct, or am I missing something?
And ultimately, the goal is to get into TWRP so that my PC recognizes the phone and sees the storage device? Many thanks for your time and effort.
awhaley3 said:
Thank you very much for the instructions. I believe I may try to go this route, but to be sure, step #1 (unlocking the bootloader) in your link says that the unlocking process will wipe the internal storage? Is this correct, or am I missing something?
And ultimately, the goal is to get into TWRP so that my PC recognizes the phone and sees the storage device? Many thanks for your time and effort.
Click to expand...
Click to collapse
Lol. Yeah. It definitely does wipe storage. I wasn't thinking clearly. Thanks for reading for yourself and asking that. Sorry for the misinformation.
jollywhitefoot said:
Lol. Yeah. It definitely does wipe storage. I wasn't thinking clearly. Thanks for reading for yourself and asking that. Sorry for the misinformation.
Click to expand...
Click to collapse
Don't worry about it, I've accepted that I am pretty much out of options and will most likely have to wipe the phone for whatever solution I choose. Thanks again for the information and such a detailed response; it is greatly appreciated since I'm so new to all of this.
awhaley3 said:
Don't worry about it, I've accepted that I am pretty much out of options and will most likely have to wipe the phone for whatever solution I choose. Thanks again for the information and such a detailed response; it is greatly appreciated since I'm so new to all of this.
Click to expand...
Click to collapse
Well, the last thing you could try would be to download and place the update file (renamed to 0PJAIMG.zip) on an external SD card (32gb or less, formatted FAT32) and boot to download mode. I've never flashed a file this way but many people around here have. For more information, just search 0PJAIMG.
I can upload the package to my drive, but it will take a while. In the meantime, I'll do a quick search to see if anyone else has uploaded it.
awhaley3 said:
Don't worry about it, I've accepted that I am pretty much out of options and will most likely have to wipe the phone for whatever solution I choose. Thanks again for the information and such a detailed response; it is greatly appreciated since I'm so new to all of this.
Click to expand...
Click to collapse
Here's a link to the OTA pkg I uploaded.
https://drive.google.com/file/d/0B8OH6sFjVE1lb0xEazA2c0RwRUE/view?usp=sharing
jollywhitefoot said:
Well, the last thing you could try would be to download and place the update file (renamed to 0PJAIMG.zip) on an external SD card (32gb or less, formatted FAT32) and boot to download mode. I've never flashed a file this way but many people around here have. For more information, just search 0PJAIMG.
I can upload the package to my drive, but it will take a while. In the meantime, I'll do a quick search to see if anyone else has uploaded it.
Click to expand...
Click to collapse
I'm getting the following error when trying to flash via the 0PJAIMG.zip method:
Failed -2, 14: fail to flash via downloadzip
I cannot find anyone else with this particular error, and I'm not sure what would be causing it. I'm going to do a bit more digging after work tomorrow. Maybe this error means that any update file will fail to flash, but would it be worth trying to flash the March 23, 2015 update? In Download mode it shows that I have the new OS number but the date shows March 23 2015, the date of the prior update.
The thing is I cannot locate a .zip for the March 2015 update, I'm only able to find non-US versions online, do you have any recommendations for where to find one?
awhaley3 said:
I'm getting the following error when trying to flash via the 0PJAIMG.zip method:
Failed -2, 14: fail to flash via downloadzip
I cannot find anyone else with this particular error, and I'm not sure what would be causing it. I'm going to do a bit more digging after work tomorrow. Maybe this error means that any update file will fail to flash, but would it be worth trying to flash the March 23, 2015 update? In Download mode it shows that I have the new OS number but the date shows March 23 2015, the date of the prior update.
The thing is I cannot locate a .zip for the March 2015 update, I'm only able to find non-US versions online, do you have any recommendations for where to find one?
Click to expand...
Click to collapse
Sorry that didn't work for you. I figured it was a hail mary. I'm pretty much out of ideas now, too.
I don't know about the March 15 OTA files.
jollywhitefoot said:
Sorry that didn't work for you. I figured it was a hail mary. I'm pretty much out of ideas now, too.
I don't know about the March 15 OTA files.
Click to expand...
Click to collapse
Yeah, I was thinking it was a long shot too anyway. Many thanks for trying to help and giving me ideas! Unfortunately I exhausted all my options without any luck. I resorted to a factory reset and flashing of the stock OTA and the phone was still unresponsive, so I had to send it in for a replacement.

HTC M9 Help! No fastboot. Have had it rooted for a while

Hi! I have been reading some write ups, but im not sure what to do.
I have a M9 Sprint version that has been unlocked for a while now, like a year, I downloaded an app this morning to delete sprint junk apps and deleted them. Well the app failed and when i reset the phone, the sprint apps just reinstalled. Shortly after, on my drive to work, I felt my phone vibrating, and noticed it was stuck in a reset loop.
I tried loading in fastboot, to re lock boot loaded and attempt to go back to stock image. I used TWRP to root it, and i have formatted my computer since then and dont have any of the associated files, including any backups.
My goal at this point is to return to a working phone, oem image or not, i really dont care. What do I need to do?
I downloaded the adb/fastboot tool to my pc, but no devices are being found, and fastboot is not an option when i go to the boot loader.
THANKS!
thehoss said:
Hi! I have been reading some write ups, but im not sure what to do.
I have a M9 Sprint version that has been unlocked for a while now, like a year, I downloaded an app this morning to delete sprint junk apps and deleted them. Well the app failed and when i reset the phone, the sprint apps just reinstalled. Shortly after, on my drive to work, I felt my phone vibrating, and noticed it was stuck in a reset loop.
I tried loading in fastboot, to re lock boot loaded and attempt to go back to stock image. I used TWRP to root it, and i have formatted my computer since then and dont have any of the associated files, including any backups.
My goal at this point is to return to a working phone, oem image or not, i really dont care. What do I need to do?
I downloaded the adb/fastboot tool to my pc, but no devices are being found, and fastboot is not an option when i go to the boot loader.
THANKS!
Click to expand...
Click to collapse
There is a dedicated thread for sprint versions, you would have better luck posting in there, but check out this thread.
https://forum.xda-developers.com/sp...print-htc-one-m9-1-32-651-17-t3073355/page106
You might want to use an ruu via SD card method.
Rogue apps.. A perfect example of why rooted phones aren't for laymen.
As long as you have download mode and the original cable the fastboot issue will be driver related. You might have to force the physical address into the drivers. Google that!. It's about a 6 on the pc illiteracy skill scale (piss, for short, thats what it makes you scream at the screen).
Beamed in by telepathy.
squ89r97 said:
There is a dedicated thread for sprint versions, you would have better luck posting in there, but check out this thread.
https://forum.xda-developers.com/sp...print-htc-one-m9-1-32-651-17-t3073355/page106
You might want to use an ruu via SD card method.
Click to expand...
Click to collapse
Thank you,
I dont use the forums much. I will check it out.

[root] [ZS570KL] Asus Zenfone 3 Deluxe fast rooting method. Despite TWRP

Not tested on nougat.
I use adb and fastboot , twrp, supersu.
Files We need:
TWRP: It's bogus, in my phone the screen flips upsidedown: Connect a mouse thru female usb or try to figure out how to tap in a rotated screen with a non rotated touch panel.
TWRP Download -> https://drive.google.com/file/d/0B0XMYw0cbs_cdm5FZW1DQXl4MFU/view
SuperSU file - > https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip?retrieve_file=1
For ADB access thru MAC:
1.- First of all we have to get open USB debug mode to get adb acces to the phone by going to Settings -> About -> Software Information -> Tap 7 times over Build number.
2.- After we get Developer options available we have to put the phone on usb debugging by goig to "Settings-> Developer Options" Activate USB Debugging.
3.- Install android platform-tools on your PC/Linux/MAC , in my case had work on MAC and no devices acces thru ADB on PC :silly: .
platform-tools -> http://www.androidpolice.com/2017/0...ble-without-full-sdk-android-studio-download/
Here you have the 3 options to download ADB and FASTBOOT
4.- Connect your phone to the PC (USB) and copy SuperSu to the root of your phone, a place that its easy too acces, cause TWRP, for the moment flips the screen.
5.- Copy TWRP3.0.XXX.zip to the folder where you have platform-tools installed.
6.- Reboot your phone to bootloader and in Linux could work too:
./adb reboot bootloader [./ is placed cause I don't put platform-tools on the my PATH]
After the boot, then we have to boot on TWRP
./fastboot boot twrp-3.0xxxx.zip (you don't flash anything) If you want to flash TWRP, at your awn risk, ./fastboot flash recovery twrp-3.0xxxx.zip".
Well, now you have to see TRWP on your phone screen.
My recomendation is to play a little bit with the flipped screen if you don't have a female USB to plug a mouse.
7.- Trying to make a complete backup of the phone could be a good practice to move on TWRP with the flipped screen . Tap backup option and make a Backup. Always recomended!
8.- After Backup, you can go to INSTALL SuperSU.zip file. "Install -> look for your SuperSU.zip file "
9.- Go to Playstore and install supersu app.
Now you can test your root, after reboot for example tryin to install some APP that requires root. Fast move:
./adb shell
su root
It has to appear a screen to grant root access to the phone.
10. Done!
Well I think thats my second post at all, hope can help someone to root the phone.
I placed In Questions and Answers cause XDA says want to protect us from SPAM.
Feel free to correct me anything.
Kronen_75
Your links do not work.
jnmacd said:
Your links do not work.
Click to expand...
Click to collapse
Links are corrected. Thanks!
You can also substitute Magisk instead of Supersu if you need to use any of the pay apps or have root sensitive apps...
Without the right Twrp, many benefits to rooting are missing such as removing stock rom applications. Seems without being able to boot to a recovery, even Titanium cannot remove apps because it needs to clean the dalvic.. Can't do it without a recovery
Sent from my ASUS_Z016D using XDA-Developers Legacy app
Download the right twrp here: https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
You should change your title !!
Tested on nougat.
The variant ZS550KL can be rooted with same method on latest firmware with nougat
Very nice guide, Thank you. Could you please provide updated links to both TWRP and SuperSU. I am currently using TWRP 3.1.1-0 and it functions properly after hanging for approximately 45 seconds on boot. This may be due to the fact my phone is encrypted. I initially rooted without installing TWRP (fastboot boot twrp.img) but have since flashed it. Both ways work well. The posted version of SuperSU did result in root but caused me to lose cell service! The phone could "see" the sim card but not use it. Updating to SuperSU 2.82 solved that issue. This was all done on my finally rooted ZenFone 3 Deluxe Special Edition (Z016D)!!!
I unfortunately figured something out the other day. Using TWRP 3.1.1-0 I am able to install zip files, complete wipes, make & restore backups. The issues only arise after you restore your nandroid image. Everything works except for two things.
1. The ability to hear audio during phone calls. The phone is actually able to place calls but you are unable to hear or record any phone audio. Oddly enough I was able to play music and use voice dictation. It was only in-call audio that seemed to be affected.
2. If you have a pin set when you create your nandroid image your pin will no longer work once restored. You will be locked out of your own phone!!
Fortunately both are fairly easily resolved and keep TWRP relatively useful, although a bit bothersome!
To resolve the pin issue it is necessary to use the TWRP file manager or ADB to delete 5 files (listed below) and regain entrance to your phone. Once deleted simply reboot the phone and reset your pin. If you remove your pin before creating a backup this issue is averted completely.
/data/system/gatekeeper.pattern.key
/data/system/gatekeeper.password.key
/data/system/locksettings.db
/data/system/locksettings.db-wal
/data/system/locksettings.db-shm
To re-enable call audio use TWRP (install zip) to reflash the same version firmware from the Asus website over your current install without wiping. This will restore any system apps you may have removed but you should still have root and can easily remove them again. There will be two errors when performing the flash, which is why I believe root is retained but the system image will be reflashed. Reboot and enjoy
I sincerely hope I have not caused anyone any issues! Or that someone else finds this information useful. I have tested everything in this post at least three times. All testing was done on the most recent Android 7 firmware on my ZenFone 3 Deluxe Special Edition (SnapDragon 821/6/256).
Sandman45654 said:
I unfortunately figured something out the other day. Using TWRP 3.1.1-0 I am able to install zip files, complete wipes, make & restore backups. The issues only arise after you restore your nandroid image. Everything works except for two things.
1. The ability to hear audio during phone calls. The phone is actually able to place calls but you are unable to hear or record any phone audio. Oddly enough I was able to play music and use voice dictation. It was only in-call audio that seemed to be affected.
2. If you have a pin set when you create your nandroid image your pin will no longer work once restored. You will be locked out of your own phone!!
Fortunately both are fairly easily resolved and keep TWRP relatively useful, although a bit bothersome!
To resolve the pin issue it is necessary to use the TWRP file manager or ADB to delete 5 files (listed below) and regain entrance to your phone. Once deleted simply reboot the phone and reset your pin. If you remove your pin before creating a backup this issue is averted completely.
/data/system/gatekeeper.pattern.key
/data/system/gatekeeper.password.key
/data/system/locksettings.db
/data/system/locksettings.db-wal
/data/system/locksettings.db-shm
To re-enable call audio use TWRP (install zip) to reflash the same version firmware from the Asus website over your current install without wiping. This will restore any system apps you may have removed but you should still have root and can easily remove them again. There will be two errors when performing the flash, which is why I believe root is retained but the system image will be reflashed. Reboot and enjoy
I sincerely hope I have not caused anyone any issues! Or that someone else finds this information useful. I have tested everything in this post at least three times. All testing was done on the most recent Android 7 firmware on my ZenFone 3 Deluxe Special Edition (SnapDragon 821/6/256).
Click to expand...
Click to collapse
The second issue happens in all the phones/twrp.
It's possible to install the firmware from asus website with twrp?? To update i flash the stock recovery, install the firmware, then reflash twrp and supersu. Didn't know that! It updates successfully with twrp??
Thank you Ryder for confirming my suspicion that the pin issue may have been a more common one with TWRP. This is the first phone I actually cared enough about to use a pin. I was thrown for a loop when I first booted my fresh nandroid restore and the pin I know I've been using was incorrect!
As for installing firmware, with the two errors that occurred during I don't know that you would be able to do full scale upgrade to a higher version. To reinstall the system partition however it does seem to work quite well. I tested this part four times. To do so download the correct device/version firmware to the phones storage, click install, and select that file. After it completes I like to wipe both the cache and the dalvik cache before restarting the phone. The audio issue was unfortunately easily reproduced on my phone, but thankfully equally easy to resolve. This worked for me each time without fail.
Sandman45654 said:
Thank you Ryder for confirming my suspicion that the pin issue may have been a more common one with TWRP. This is the first phone I actually cared enough about to use a pin. I was thrown for a loop when I first booted my fresh nandroid restore and the pin I know I've been using was incorrect!
As for installing firmware, with the two errors that occurred during I don't know that you would be able to do full scale upgrade to a higher version. To reinstall the system partition however it does seem to work quite well. I tested this part four times. To do so download the correct device/version firmware to the phones storage, click install, and select that file. After it completes I like to wipe both the cache and the dalvik cache before restarting the phone. The audio issue was unfortunately easily reproduced on my phone, but thankfully equally easy to resolve. This worked for me each time without fail.
Click to expand...
Click to collapse
You said that the two issues occurred when you restored the nandroid backup and to fix one of them by installing the zip firmware from asus website with twrp... I don't understand. I can install zip firmware with twrp or i have to flash the stock recovery and install with it? Errors may occur using the twrp? Sorry
Everything done in my post so far has been in TWRP. Honestly I didn't even back up the recovery image. TWRP seemed to work flawlessly so I bit bullet and flashed it.
On a sidenote I am currently testing the usability of FlahFire on this device. It appears to create a very nice fastboot installable recovery image! I have yet to restore the image however. I will post my findings here once I have thoroughly tested it.
Sandman45654 said:
Everything done in my post so far has been in TWRP. Honestly I didn't even back up the recovery image. TWRP seemed to work flawlessly so I bit bullet and flashed it.
On a sidenote I am currently testing the usability of FlahFire on this device. It appears to create a very nice fastboot installable recovery image! I have yet to restore the image however. I will post my findings here once I have thoroughly tested it.
Click to expand...
Click to collapse
Ok. I'm interested in flashing zip firmware to update. Never tried that. I thought that firmware can be installed only with stock recovery. The stock recovery can be downloaded in an asus forum website
This is the first time I have flashed anything in almost a year. I got to thinking and this is the most success I have had was flashing a stock image with TWRP! I doubt it will perform a full flash. I believe the errors are most likely for the boot and recovery partitions. As a save my butt reflash the system partition it does work. It sounds like it's time to find some TWRP changelogs!
Sandman45654 said:
This is the first time I have flashed anything in almost a year. I got to thinking and this is the most success I have had was flashing a stock image with TWRP! I doubt it will perform a full flash. I believe the errors are most likely for the boot and recovery partitions. As a save my butt reflash the system partition it does work. It sounds like it's time to find some TWRP changelogs!
Click to expand...
Click to collapse
I don't care about stock images... If i can't flash the zip with twrp to update successfully then i reflash the stock recovery and after the update root again with twrp and supersu. By the way, the zip firmare contains factory images? I thought it contains different kind of files
Ryder. said:
By the way, the zip firmare contains factory images? I thought it contains different kind of files
Click to expand...
Click to collapse
I lack the knowledge to answer that with enough certainty to even call it an answer! This is my foray into the insides of this phone and I don't want to start posting my hunches.
What I do know is you can flash the system partition using TWRP. I have done it several times. Asus's zips run as a script based zip install. You are offered no options during install. When the script runs you will see two errors quickly scroll past.
Ryder. said:
Download the right twrp here: https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
Click to expand...
Click to collapse
Are you creating these TWRP builds? If so thank you very much! TWRP-3.1.1-0-Z016-20170826 seems to work flawlessly! No lag on boot and no known issues after restoring a backup unlike before.
I wanted to post my finding about FlashFire by Chainfire. I have had great success with the fastboot backup! It is the only option I have tested extensively however. I have been running the same fastboot restored phone since soon after my last post on this topic with no issues discovered.
Sandman45654 said:
Are you creating these TWRP builds? If so thank you very much! TWRP-3.1.1-0-Z016-20170826 seems to work flawlessly! No lag on boot and no known issues after restoring a backup unlike before.
I wanted to post my finding about FlashFire by Chainfire. I have had great success with the fastboot backup! It is the only option I have tested extensively however. I have been running the same fastboot restored phone since soon after my last post on this topic with no issues discovered.
Click to expand...
Click to collapse
No. It's not me. It's another user which i don't remember the nickname
Ryder. said:
No. It's not me. It's another user which i don't remember the nickname
Click to expand...
Click to collapse
Okay thank you. If you happen to find out/remember please let me know. I would like to give credit with my project and thank them for their hard work.

No wifi after flashing, either on BPA1 or CPD1 firmwares

I was trying to get rooted, I've downgraded and am on 5.1.1 on the CPD firmware currently, but I can't get wifi back. I had the boot loader unlocked but somehow lost it after flashing to the CPD firmware. I was using this guide: https://forum.xda-developers.com/no...guide-step-step-stock-n910v-6-0-1-to-t3426905
I've made it to step 35 from there, but I can't get Kingroot to work on this current firmware because of no wifi, I guess. It tries but it keeps failing.
Any ideas or suggestions? At this point I don't care if I have root or not, I just need a workable phone with wifi
At that point, you need a SIM card because you are on the updated bootloader (CPD1) for 6.01 and will not have WiFi. You have upgraded the bootloader, but you're still on the older 5.11 baseband. Pop a SIM card into the phone and root it once again. Then follow the rest of the instructions. It works. I've done it on multiple devices.
BeckPC said:
At that point, you need a SIM card because you are on the updated bootloader (CPD1) for 6.01 and will not have WiFi. You have upgraded the bootloader, but you're still on the older 5.11 baseband. Pop a SIM card into the phone and root it once again. Then follow the rest of the instructions. It works. I've done it on multiple devices.
Click to expand...
Click to collapse
Unfortunately, I've pulled the sim from my working phone and put it into this one, and despite running KingRoot about a dozen times now, I can't ever get it to go through. I don't know if I don't have enough data bandwidth here in the area for it to work entirely correct, or what, but I can't seem to get past this stage or get any wifi up and going again.
hondaatc said:
Unfortunately, I've pulled the sim from my working phone and put it into this one, and despite running KingRoot about a dozen times now, I can't ever get it to go through. I don't know if I don't have enough data bandwidth here in the area for it to work entirely correct, or what, but I can't seem to get past this stage or get any wifi up and going again.
Click to expand...
Click to collapse
It sounds like you're stuck on a 6.01 ROM with a 5.11 bootloader. You have a few more steps to complete before you're ready to flash to your hearts content. King Root doesn't download much.
I had the same problem once. Go to setting and do a hard reset on the device, wiping all data and let it boot up for the first time (with the same ROM installed. Don't sign into Google, just skip all the setup routines. Install King Root and try again. It should work. It might take a few times. It's extremely unstable. As soon as you get root, run the ADB routine quickly and unlock the bootloader. Now you can use ODIN to flash the final file N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar. That will update you to the new firmware and restore your wifi. Don't let the phone reboot automatically. Once it's done, pull the battery. Leave it out for a minute at least. Then start up the phone in bootloader mode (vol down, home and power). Immediately after that, you want to use ODIN to install the twrp 3.0.20 file as well.
Now boot up the phone and enter TWRP. Do a standard wipe (cache/dalvic/data) but not System. Do it twice. Now reboot. You should be unlocked (open padlock on the screen) and booting into 6.0.1. You can check for root. At this point, you should be good. Now you can flash any ROM that requires the CPD1 firmware. You can always update the modem, but your firmware will remain at that version. Personally, I recommend Modest Rom 8. It's as close to stock as you can get, with a few nice tweaks and addons that makes life a bit better. From there, you can experiment all you want.
Two more bits of advice ... once you have it rooted and fixed up, you need to do two things.
1. Use Root Explorer to completely delete all files from /systems/efs folder. Why you ask, this folder will contain chinese junk that will slow down your phone. Trust me. It works and hurts nothing. Do this especially after rooting.
2.Use TWRP to make a backup of the complete system to your memory card. It's so much easier to go back and restore, than it is to redo all the work you just did.
BeckPC said:
It sounds like you're stuck on a 6.01 ROM with a 5.11 bootloader. You have a few more steps to complete before you're ready to flash to your hearts content. King Root doesn't download much.
I had the same problem once. Go to setting and do a hard reset on the device, wiping all data and let it boot up for the first time (with the same ROM installed. Don't sign into Google, just skip all the setup routines. Install King Root and try again. It should work. It might take a few times. It's extremely unstable. As soon as you get root, run the ADB routine quickly and unlock the bootloader. Now you can use ODIN to flash the final file N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar. That will update you to the new firmware and restore your wifi. Don't let the phone reboot automatically. Once it's done, pull the battery. Leave it out for a minute at least. Then start up the phone in bootloader mode (vol down, home and power). Immediately after that, you want to use ODIN to install the twrp 3.0.20 file as well.
Now boot up the phone and enter TWRP. Do a standard wipe (cache/dalvic/data) but not System. Do it twice. Now reboot. You should be unlocked (open padlock on the screen) and booting into 6.0.1. You can check for root. At this point, you should be good. Now you can flash any ROM that requires the CPD1 firmware. You can always update the modem, but your firmware will remain at that version. Personally, I recommend Modest Rom 8. It's as close to stock as you can get, with a few nice tweaks and addons that makes life a bit better. From there, you can experiment all you want.
Two more bits of advice ... once you have it rooted and fixed up, you need to do two things.
1. Use Root Explorer to completely delete all files from /systems/efs folder. Why you ask, this folder will contain chinese junk that will slow down your phone. Trust me. It works and hurts nothing. Do this especially after rooting.
2.Use TWRP to make a backup of the complete system to your memory card. It's so much easier to go back and restore, than it is to redo all the work you just did.
Click to expand...
Click to collapse
Well that gives me some hope I'm on the right track, I guess I'll keep trying. I've done much of that, and the thing is every time I do a factory reset (Like before an odin flash), I get stuck in a boot loop again until it seemingly randomly comes out of it and starts up normal again, so its kinda spooky doing that. All the steps and finagling makes me yearn for my old Samsung Moment that was a simple drop a rom onto the SD card...lol
If you have the SD card installed, remove it. It may need to be cleaned for the phone to boot properly.
Just do the wipe and reboot normally. See if it will continue. You'll need the SD card later, but it needs to be formatted if it was used during the bootloader backup. It looks like you are almost finished. Just one more round with the ADB command and you'll be complete.
BeckPC said:
If you have the SD card installed, remove it. It may need to be cleaned for the phone to boot properly.
Just do the wipe and reboot normally. See if it will continue. You'll need the SD card later, but it needs to be formatted if it was used during the bootloader backup. It looks like you are almost finished. Just one more round with the ADB command and you'll be complete.
Click to expand...
Click to collapse
Okay, so I went back and did factory reset from recovery console to retry Kingroot. I noticed though, it set me back to BPA, and not CPD1. So now I'm trying to use odin to back back up to CPD1.
Was this normal, for a factory reset to go back to BPA, or should it have kept me on CPD1?
It sounds like you missed a step unlocking the bootloader. You have to do it three times, with each firmware update you do. A factory reset should not have rolled back to BPA1. Why don't you take a look at the other thread on rooting and use it. When I got to the bottom of the one you're using, I knew I didn't want to do the Jasmine ROM, so I followed this one: https://forum.xda-developers.com/no...asy-guide-how-to-root-verizon-galaxy-t3454593
Just take it slowly and it will take a couple of hours, but once it's done, you'll be rooted.
hondaatc said:
Okay, so I went back and did factory reset from recovery console to retry Kingroot. I noticed though, it set me back to BPA, and not CPD1. So now I'm trying to use odin to back back up to CPD1.
Was this normal, for a factory reset to go back to BPA, or should it have kept me on CPD1?
Click to expand...
Click to collapse
If you have rooting issues try inputting the proper APN manually before attempting to root. That was my issue. Even tho it recognized my sim it wouldn't root until I put in my actual APN settings for Koodo.
Try an older version of the root apps also.

Categories

Resources