Related
My phone wont boot now.
It stays stuck at the 2nd Samsung during the boot up.
What happen was I updated today to offical ICS from my rooted gingerbread.
I updated via kias today to get official ICS, got it working and I noticed I didn't have cwm install anymore, so I followed this http://forum.xda-developers.com/showthread.php?t=1504218
It is pass it did it reboot thing, and never got past the 2nd "samsung" loading screen.
Anyone know how to get my phone booting again?
Flash the latest ICS kernel
I am not sure how to do that without cwm.
Before I updated to ICS when I press power + up down, it booted into CWM. Now when I do that I boots into Android System Recovery <3e>
EDIT: Good news.
Got CWM through installed though odin and then I restored to my gingerbread backup I made earlier.
Flash your roms via clockwork recovery mod from now on.
Drop the ROM .zip on sd card and then enter recovery. Wipe everything three times each then flash a uclf6 based ROM. Never touch Odin or kies again. Be happy. Ice cream sandwich is way better than ginger bread
Sent from my SAMSUNG-SGH-I717 using xda premium
Had the same exact problem. I "believe" the problem was that the CWM I flashed was perhaps incompatible with the official ICS?
I used Odin to flash cwm 5.5.0.4 as suggested and the fone was shut down with the hanging Samsung screen as you mentioned. I used the DL screen with Odin to the 600mb Team Objection ROM, which at least got me up and running again. I found out that CWM did in fact flash once the ROM was compatible with it. Updated CWM, then to finally get full stability, I had to do a factory reset after clearing both caches, then install the CM9 official.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Update: I installed official ICS again last night, looks like I lost my root and CWM.
I don't want to mess anything up again, so could you tell me exactly what CWM file you used to flash so it doesn't hang at samsung again?
I was having the same problems but I think I was doing it wrong. How are you flashing the root files? I upgraded from Kies, then used Odin to flash cwm touch (5.5.0.4 I think), make sure to let the reboot and that it's actually turned on and you can see your homescreen. Once you do that, THEN flash the superuser 3.0.7 in cwm. Let the phone reboot properly and it should be okay.
I was doing the same without the reboots and that's what caused me to hang at the logo, but after the above it worked well. Give it a try. For anyone who needs to flash the T-Mobile radios also let the phone reboot and then flash it because I was having issues with that which was fixed by letting the phone reboot.
Make nandroids at every step in case it does hang so you can just restore and try again instead of flashing everything all over again.
Sent from my SGH-I717R using xda app-developers app
I've also tried rooting my AT&T Galaxy Note I717 which had recently upgraded to ICS via AT&T/Kies and my phone is stuck at the Samsung boot screen. While I'm no expert with rooting phones, I had no problem rooting it when it had GB installed so I figured I wouldn't have any problems rooting it again. Is flashing the ICS kernel the best way to fix this? Where do I get the ICS kernel from and how do I flash it?
Details: After my phone upgraded to ICS 4.0.4 kernel 3.0.8 (IMM76D.UCLF6), I followed some instructions to root it using Odin3-v1.85 and PDA->pda.tar. Other instructions used cwm-touch-i717-120414.tar.md5 and odin_n1717_cwm_recovery_b4.tar and I tried those but to no avail. So I have CWM v5.5.0.4 installed but I don't know what to do next.
Any help is greatly appreciated. Thanks!
dcdtrax said:
I've also tried rooting my AT&T Galaxy Note I717 which had recently upgraded to ICS via AT&T/Kies and my phone is stuck at the Samsung boot screen. While I'm no expert with rooting phones, I had no problem rooting it when it had GB installed so I figured I wouldn't have any problems rooting it again. Is flashing the ICS kernel the best way to fix this? Where do I get the ICS kernel from and how do I flash it?
Details: After my phone upgraded to ICS 4.0.4 kernel 3.0.8 (IMM76D.UCLF6), I followed some instructions to root it using Odin3-v1.85 and PDA->pda.tar. Other instructions used cwm-touch-i717-120414.tar.md5 and odin_n1717_cwm_recovery_b4.tar and I tried those but to no avail. So I have CWM v5.5.0.4 installed but I don't know what to do next.
Any help is greatly appreciated. Thanks!
Click to expand...
Click to collapse
Update: I restored my phone back to a non-rooted working Android 4.0.4 by downloading the stock ROM for my phone (I717UCLF6_I717ATTLF6_I717UCLF6_HOME.tar.md5) and uploading it using Odin3-v1.85/PDA. I didn't even lose any of my settings or data. Now I need to figure out how to successfully root it. But at least I'm not worried about getting stuck on the Samsung screen anymore.
Open odin , PDA cwm file, Droid in dl mode, plug in start unplug, reboot, go to cwm recovery mode and backup onto sd card.
Im learning more, as i soft bricked mine last time
dcdtrax said:
Update: I restored my phone back to a non-rooted working Android 4.0.4 by downloading the stock ROM for my phone (I717UCLF6_I717ATTLF6_I717UCLF6_HOME.tar.md5) and uploading it using Odin3-v1.85/PDA. I didn't even lose any of my settings or data. Now I need to figure out how to successfully root it. But at least I'm not worried about getting stuck on the Samsung screen anymore.
Click to expand...
Click to collapse
Odin....to get touch cwm, then download the super user zip and flash it, you will have root....
All can be found in "My links" see it in red...go to GNote page....
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
what about su binaries
Can i put both on my sd card and put it in my phone, cmw recovery and install from there?
liftedzuki said:
what about su binaries
Can i put both on my sd card and put it in my phone, cmw recovery and install from there?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1740367
ok look for the green arrow...and use those threads....to root...k
odin for touch cwm
flash super user
your rooted
You realize the reason you were stuck was because you flashed a GB kernel onto an ICS system? It would never boot. As the second post suggested... all you had to do was flash an ICS kernel to get it to boot.
Sent from my Amazon Kindle Fire using xda premium
Sent from my Amazon Kindle Fire using xda premium
Rooted.
erad1 said:
You realize you the reason you were stuck was because you flashed a GB kernel onto an ICS system? It would never boot. As the second post suggested... all you had to do was flash an ICS kernel to get it to boot.
Sent from my Amazon Kindle Fire using xda premium
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
so correct...you nailed it...so many are trying to root with gb kernal....
I hope they go to the page I made and follow the green arrowed how to root ics...it is very super simple process to root the official ics...but ....
This happened to me after misreading a comment.
If you put your phone into download mode, plug it in, run kies, and do an emergency firmware recovery. You'll need the serial number. My phone is stock ICS again. Works fine.
erad1 said:
You realize the reason you were stuck was because you flashed a GB kernel onto an ICS system? It would never boot. As the second post suggested... all you had to do was flash an ICS kernel to get it to boot.
Sent from my Amazon Kindle Fire using xda premium
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
so cwm 5.5.0.4 touch is a GB kernel? Because that's all I flashed after the KIES update to ICS and I got the hanging Samsung logo.
I believe some people are trying to get ICS rooted with this cwm and are getting stuck. Of course there are ways out of it, but it'll help the learning process if we can find the problem.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
romeojunior said:
so cwm 5.5.0.4 touch is a GB kernel? Because that's all I flashed after the KIES update to ICS and I got the hanging Samsung logo.
I believe some people are trying to get ICS rooted with this cwm and are getting stuck. Of course there are ways out of it, but it'll help the learning process if we can find the problem.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
Wait what??!!??!!
you need to read read read read and PLEASE read
Because CMW is not a kernel
Its a recovery
People wouldn't have these issues if they read.
Please refer to the stickies before you really damage your phone.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
The OP had posted that he flashed Da_g's GB kernel trying to get root...your issue if flashing CWM may be different. Hopefully you use the steps outlined by bigjoe in his post.
Sent from my SAMSUNG-SGH-I717 using xda premium
Sent from my ADR6425LVW using xda app-developers app
I have an s-off'd custom rom with AmonRa recovery... offered update??
I just want to have it ignore the update.
Apparently, the software doesn't know the
recovery system is not stock ... so it tries
and fails. I wonder if there is a way to extract
the new fingerprint to trick the update process
into thinking the updates already applied?
Or is there a way to just suppress it all together?
Well I'm pretty much chicken so I'm basically stock but rooted but the ota update keeps falling. I tried unrooting so the update could work but it still failed. Not sure why...
Sent from my ADR6425LVW using xda app-developers app
Same here
I am having the same issue, as well. Rooted, debloated stock sense. Recovery is Amon-Ra.
So I read another thread that made it seem like I needed to re-lock the bootloader so I did that and now when I try to update it goes into the bootloader menu instead of starting the update. Do I need to unroot or do another step for this to work?
Sent from my ADR6425LVW using xda app-developers app
Did you debloat at all? I was stock+root (no debloating) and the install went fine.
Sent from my ADR6425LVW using xda premium
Well, when the ota update downloads and you press the button to update, the updater immediately begins to check the system utilizing a checksum system for any modification, such as a deodexed system/app folder or binaries that weren't originally present. It wants to make sure all system/apps are still there and untouched and all the binaries are still kosher. If it detects something is "off" it will usually abort. If everything checks out it will boot to bootloader and attempt to install the update in the stock recovery. It will fail here of course if a custom recovery is installed.
You can kill your phone from even attempting to check for any otas by using Root Explorer or something similar, go to system/app and add bak to the end of each of these files:
HtcCOTAClient.apk
HtcCOTAClient.odex
You want them to look like:
HtcCOTAClient.apkbak
HtcCOTAClient.odexbak
You could also remove them.
I have an s-off'd custom rom with AmonRa recovery... offered update??
wildstang83 said:
Well, when the ota update downloads and you press the button to update,
the updater immediately begins to check the system utilizing a checksum system for any modification,
such as a deodexed system/app folder or binaries that weren't originally present. It wants to make sure
all system/apps are still there and untouched and all the binaries are still kosher. If it detects something
is "off" it will usually abort. If everything checks out it will boot to bootloader and attempt to install the
update in the stock recovery. It will fail here of course if a custom recovery is installed.
You can kill your phone from even attempting to check for any otas by using
Root Explorer or something similar, go to system/app and add bak to the en
d of each of these files:
HtcCOTAClient.apk
HtcCOTAClient.odex
You want them to look like:
HtcCOTAClient.apkbak
HtcCOTAClient.odexbak
You could also remove them.
Click to expand...
Click to collapse
I froze that with TiBu but it still shows up
as a pending update.
Experimenting, I tried freezing HtcDM
apk and service and the notices went away.
Is that safe to leave DM frozen, (what else does it do)?
My intent is to just prevent this a future OTA
updates auto-installing while I asleep. i woke
to find myself looking at a failed attempt
and hung in AmonRA, I rebooted to normal
and everything runs as normal.
fuzzynco said:
I froze that with TiBu but it still shows up
as a pending update.
Experimenting, I tried freezing HtcDM
apk and service and the notices went away.
Is that safe to leave DM frozen, (what else does it do)?
My intent is to just prevent this a future OTA
updates auto-installing while I asleep. i woke
to find myself looking at a failed attempt
and hung in AmonRA, I rebooted to normal
and everything runs as normal.
Click to expand...
Click to collapse
Not to be a PIA, but why freeze if you can just add bak to the end of the file name and you will achieve the same thing? If you ever want to go back you just delete the bak?
So for me it sounds like I need to get back to a stock recovery to be able to successfully perform the update?
Sent from my ADR6425LVW using xda app-developers app
Gee thanx for the help people...
Sent from my ADR6425LVW using xda app-developers app
You must be on the stock recovery to take an OTA. The stock recovery performs the update. So flash the stock recovery and then do the update or deal with no update.
Is there a way to flash the stock recovery without it wiping my phone?
Sent from my ADR6425LVW using xda app-developers app
Unless you're running a completely stock rom (with nothing removed), you won't be able to install the update anyway...
If you want to stop it from trying to come down, delete or rename /system/etc/security/otacerts.zip.
As for re-installing the stock recovery, you probably would need to RUU your phone unless it's s-off.
So if I do a back up, then go back to stock recovery which will wipe my phone, then perform the ota update, will a restore revert the ruu back and I'm back to square one, or does the ruu not roll back?
Sent from my ADR6425LVW using xda app-developers app
fivedezs said:
So if I do a back up, then go back to stock recovery which will wipe my phone, then perform the ota update, will a restore revert the ruu back and I'm back to square one, or does the ruu not roll back?
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
If you are on a stock rom you should be able to flash the stock recovery from fastboot without wiping the phone. Just find the recovery.IMG from the 605.12 ruu and flash it in fast boot to your phone. Then take the update and when complete flash your custom recovery in fast boot again and flash su zip.
Sent from my Nexus 7 using Tapatalk HD
fivedezs said:
So if I do a back up, then go back to stock recovery which will wipe my phone, then perform the ota update, will a restore revert the ruu back and I'm back to square one, or does the ruu not roll back?
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
A restore would not overwrite any of the firmware on the phone, just the rom.
As dottat pointed out, you can download the latest RUU, extract the recovery image from it and flash that via fastboot. I'd still back up your rom with your custom recovery first in case the rom pieces in the update bork something...
Can anyone point me in the direction of where I can find the stock ruu?
Sent from my ADR6425LVW using xda app-developers app
fivedezs said:
Can anyone point me in the direction of where I can find the stock ruu?
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Check androidpolice.com, it's over there, should be able to search for it...
Need a copy of the stock recovery
I am S-On and unlocked. I need to reflash the stock recovery to apply the OTA firmware update, right? I cannot find a copy of it anywhere. Anyone know where I can get this? I downloaded the stock RUU and tried to pull it out, but I cannot unzip the file. I would be grateful for any help. Thanks.
I was rooted so I flashed stock ROM and recovery but still the update is failing when trying to install....any Idea of what I would have to do to get completely back to stock and install the update?
I would way +/- with updating at this point. It looks like the new update is blocking the previous rooting exploit.
Overall though, in order to get the update its my understanding you need to be in stock recovery
Flash-oholic on my SCH-I545
Be glad you can't take the update. The ota licks down the bootloader so the Motochopper want give u root.
Sent from my SCH-I545 using xda app-developers app
If you use the kies program from Samsung you can flash it back to the original firmware. In the tools menu there's an emergency recovery option.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Same problem here. Getting error 402 trying to OTA update.
Emergency Firmware Recovery in Kies requires a "recovery code from the previous PC".
I had a custom recovery before flashing the stock image. Should I need to flash the stock recovery in addition to the stock rom?
You would have lost root anyway..
Sent from my SCH-I545 using xda premium
I was able to do it through VZW software, regretting it lol I was hoping more bugs were fixed
Yes, I was only able to update using USB via Kies. Something still seems off, as wiping cache in recovery gives an error and reboots.
I haven't been able to update and have given up for now. I did two factory resets, and used Odin to flash back to stock twice, both without any luck. I went ahead and just set everything back up the way it was for now.
Ok, been away from the note 2 for a min. Anyone want to give me the low down on all this 4.3 stuff? I'm seeing roms say that MJ9 has to be flashed in Odin before a the rom can be flashed? Is this a one time deal or does it have to be done every time I want to flash a tw rom? Do I have to do anything to go back to an aosp rom? I'm sure I could figure all this out on my own but I'm impatient. Lol. TIA
Sent from my SCH-I605 using Tapatalk
KBizzle said:
Ok, been away from the note 2 for a min. Anyone want to give me the low down on all this 4.3 stuff? I'm seeing roms say that MJ9 has to be flashed in Odin before a the rom can be flashed? Is this a one time deal or does it have to be done every time I want to flash a tw rom? Do I have to do anything to go back to an aosp rom? I'm sure I could figure all this out on my own but I'm impatient. Lol. TIA
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
You have to flash MJ9 firmware that has the tz, params and modem in it.. This allows wifi to work.. then flash away! Just do not flash MJ9 official OS KIES bc you'll lock your bootloader..
Once your done flashing the firmware you can flash in between roms no problem doesn't matter what version,4.1.2, 4.3 or aosp 4.4.2:good:
Edit: here's the thread http://forum.xda-developers.com/showthread.php?t=2578458
lacoursiere18 said:
You have to flash MJ9 firmware that has the tz, params and modem in it.. This allows wifi to work.. then flash away! Just do not flash MJ9 official OS KIES bc you'll lock your bootloader..
Once your done flashing the firmware you can flash in between roms no problem doesn't matter what version,4.1.2, 4.3 or aosp 4.4.2:good:
Edit: here's the thread http://forum.xda-developers.com/showthread.php?t=2578458
Click to expand...
Click to collapse
Thank you. It's been a while.
Sent from my SCH-I605 using Tapatalk
Alright, got one more question. So I thought I had bricked my phone last night. Accidentally flashed an S4 stock rom. I know, dumb. Anyway, after 3 hours of trying to Odin multiple stock roms, I finally got one to take and the phone booted. So I immediately went and used casual to root the device. Everything went fine there. I went ahead and updated TWRP to the latest and proceeded to flash aokp. It locked up at the boot animation. So I then tried to flash a 4.1.2 tw rom. This is where it got weird. It flashed fine but then it never booted. Just a black screen after the Samsung splash screen. I then decided to try and Odin a rooted 4.1.3 rom. Still nothing. So last ditch effort I odin'd the pit file. Back in business on an unrooted tw rom. Now when I try to use casual, it won't download the proper driver to root again. Gives a perpetual error and requests the driver be installed over and over until I pull the USB cable. Is there something I'm missing?
Sent from my SCH-I605 using Tapatalk
Try this. With the phone booted, go into device manager on your computer and uninstall the driver. Then boot the phone into download mode and uninstall the driver for it in device manager. Boot phone back up and try casual again. Also make sure your Antivirus is off before you run casual.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Hey Guys
I'm a experienced flasher but I have ran into a issue with flashing roms on my Note 3. I had recently just been running stock rooted rom (basically I rooted my phone the day it came out with Sprint and never have update anything). So when I noticed that ny son's note 3 (note rooted) got an update recently, I decided to look for an updated base and broadband for my phone, which I thought I had found. So after so help with figuring out which update I needed to do, I figured NH7 was the latest. Finally got my phone updated or so it appeared.
So this week I've been trying desperately to update to MOAR S5 PORT (NE5 based I believe) I followed the instructions carefully and tried all 3 versions. All failed. So I restored my phone. Tonight I tried flashing flashing Pac-man rom. Same thing happened. Failed during install.
Can you guys take a look at my setup and tell me what may be wrong? Doing a clean install each time.
Sent from my SM-N900P using XDA Premium 4 mobile app
UPDATED 10/24/2014:
I had to reflash all the Note 3 stock tar's in order. Then root with Chainfire Auto Root. Then install Clockwork MOD Recovery. Now I can flash roms.
shaun0207 said:
Hey Guys
I'm a experienced flasher but I have ran into a issue with flashing roms on my Note 3. I had recently just been running stock rooted rom (basically I rooted my phone the day it came out with Sprint and never have update anything). So when I noticed that ny son's note 3 (note rooted) got an update recently, I decided to look for an updated base and broadband for my phone, which I thought I had found. So after so help with figuring out which update I needed to do, I figured NH7 was the latest. Finally got my phone updated or so it appeared.
So this week I've been trying desperately to update to MOAR S5 PORT (NE5 based I believe) I followed the instructions carefully and tried all 3 versions. All failed. So I restored my phone. Tonight I tried flashing flashing Pac-man rom. Same thing happened. Failed during install.
Can you guys take a look at my setup and tell me what may be wrong? Doing a clean install each time.
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wipe wipe Wipe and when it fails to flash then restart recovery And it will flash then ....
So wipe 3 times. Then when it fails. Reboot to recovery and flash again? Do I need to wipe again before flashing?
Sent from my LGLS990 using XDA Free mobile app
shaun0207 said:
So wipe 3 times. Then when it fails. Reboot to recovery and flash again? Do I need to wipe again before flashing?
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
Any time you wipe the system partition, you MUST restart TWRP recovery before flashing the rom of your choice,.. or it'll fail every time.
Ok. I will try that noq
Sent from my SM-N900P using XDA Premium 4 mobile app
shaun0207 said:
Ok. I will try that now
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my SM-N900P using XDA Premium 4 mobile app
shaun0207 said:
Ok. I will try that noq
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Let us know how it goes. Happy flashing.
So I wiped everything. Tried to install and it failed. So i go to reboot to recovery and it ask me about superuser. But it doesnt install because their is no OS. REBOOT to recovery and it fails again
Do I need to format data?
Actually I dont even see a option in TWRP to format data
I wonder if I should try a dirty flash?
I would odin flash a full stock nh7. To get you all the way to nh7. I see you are still at nab on one. I had problems when they weren't all the same. I could be wrong.... I'm a noob. lol
Then, root with chanfires autoroot. Install your recovery. Then, flash your rom of choice.
NOTE: I said nh7.... but, if the rom you want to use isn't, then odin to nab or whatever the rom you want to run is. I don't know about downgrading, could make a brick.... lol
Research everything I said before you do anything! Or wait for someone to correct what's wrong with what I said! I take no responsibility for what you do to your phone!
one of your issues is you updated wrong! unless you were on nc5 you shouldnt jump right to nh7. you have to update in order to insure no issues. so if oyu were nqb or ever mi3 you need to go in order mi3>nab>nc5>nh7
Chainfires auto root.....http://download.chainfire.eu/362/CF-Root/CF-Auto-Root/CF-Auto-Root-hltespr-hltespr-smn900p.zip
Here is Supersu download.....so when you check to see if you have root.....it will all be good.......http://download.chainfire.eu/578/SuperSU/UPDATE-SuperSU-v2.14.zip
Odin v3.07.......http://forum.xda-developers.com/showthread.php?t=1738841
now you can try to go back to stock and flash whichever you are going to flash........or you can do a reflash of whatever you want....I have notice a losss of root also too.
also make sure to look into all those fixes for security patches xda has for our phone......download and scan with bluebox security and search for any open links that have a fix here on xda........
this happened to me the other weekend and it took an afternoon to dig all resources to figure out why and what i needed to do........I started rooting with a samsung moment......
I am back to stock.....no complaints.....but only did to get home before i go back to a rom.......hope we have helped....
Thanks guys. I will try all of these
shaun0207 said:
Thanks guys. I will try all of these
Click to expand...
Click to collapse
to get updates to stick via odin. remove sd card too. and when you update each version. boot to stock recovery wipe phone. flash again. what i do on each update. never had a single issue.
shaun0207 said:
Do I need to format data?
Click to expand...
Click to collapse
Yes you have to do that.. Also I believe you have to be in twrp 2.8 for kitkat I was having problems too until I installed the new Twrp!
bigkev904 said:
Yes you have to do that.. Also I believe you have to be in twrp 2.8 for kitkat I was having problems too until I installed the new Twrp!
Click to expand...
Click to collapse
I dont see a new TWRP. All I see is version 2,8
I installed all the updates back to back. I have TWRP installed and I'm on NH7 now. But I cant get root. Chainfire Auto took me back to stock recovery and I'm not rooted. So I flashed TWRP via Odin and flashed ChainFire Superuser v.2.14 and I'm still not rooted. All thought it say it worked. So WHen I reboot, what do I need to do then? I have SU installed
Ok guys. After flashing all the Roms in order via ODIN. I finally have NH7 working and rooted.
I just tried wiping system, data,dalvik and cache. Then I immediately rebooted to recovery and tried to flash MOAR V1. and Pac-man rom. Both failed.
One thing Im noticing in recovery is that the system is not mounted in when wiping. So I tried wiping with and without system being mounted and got the same result. One thing Im not sure about with flashing for the note is if the Data should be formatted before installing? However I dont see that option in TWRP.
This is the only phone Ive had this much trouble with when it came to flashing.
Any ideas?
Sent from my SM-N900P using XDA Premium 4 mobile app