Related
As title says, all attempts to flash a custom ROM result in error 7, I have checked that my version of TWRP is up to date and the ROM is for TRLTEXX. I have also tried removing the 'assert' section in `updater-script`, which caused another error where the `update-binary` file cannot be found. Can anyone help me figure out why this is happening and how to fix it?
MinkShenanigans said:
As title says, all attempts to flash a custom ROM result in error 7, I have checked that my version of TWRP is up to date and the ROM is for TRLTEXX. I have also tried removing the 'assert' section in `updater-script`, which caused another error where the `update-binary` file cannot be found. Can anyone help me figure out why this is happening and how to fix it?
Click to expand...
Click to collapse
First, if you just bought this phone, what I would do is double check the phone is really 910f. What's it say behind battery? Also boot into download mode, what info does that tell you. When you plug into Odin what model does it say. Reason I say this, I've seen others buy what they thought were F but they were really 910p.
If all the info checks out, I would download twrp again just to make sure you got good file. Downloads can mess up rarely.
Let me know what this tells you.
Had the phone for about a year and a half now, battery cover, behind battery, about page, and download mode all say N910F, the same as the version of TWRP is supposedly for, I have flashed both 3.0.1.0 and 3.0.2.0 of TWRP using Odin with the same result, error 7 on all attempts of installing a ROM. The ROM I'm trying to install is the Resurrection Remix ROM for 6.0.1 TRLTEXX, but others have the same error.
MinkShenanigans said:
As title says, all attempts to flash a custom ROM result in error 7, I have checked that my version of TWRP is up to date and the ROM is for TRLTEXX. I have also tried removing the 'assert' section in `updater-script`, which caused another error where the `update-binary` file cannot be found. Can anyone help me figure out why this is happening and how to fix it?
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/note-4/general/efs-fix-invalid-argument-twrp-fix-t3489294
Trex888 said:
Try this
http://forum.xda-developers.com/note-4/general/efs-fix-invalid-argument-twrp-fix-t3489294
Click to expand...
Click to collapse
I'd rather not experiment considering it still boots into touchwiz fine.
I bricked my note 7 every time I plug in a charger it boots into recovery mode in The bottom it says
"no support SINGLE-SKU
Supported API-3
dm-verity verification failed...
E:Failed setting up dirty target [omc-app-link] fail to mount /system as rwE:Failed setting up dirty target
[hwr_symlink] fail to mount /system as rw"
I tried re installing stock rom but no one has it where it's WITH OUT the 60% battery update I had this happen by trying to root via the SPRINT flashing method I came across on this website I had package disabled pro on when I was rooting now before people tell me oh just return it I work at AT&T im not returning my phone I refuse to belive it's gone for good. I know someone out there has to have a solution I have tried everything search wise on google I'm tired of looking night and day
I tried to delete cache that gives an error as well even wiping the phone while in recovery mode gives an error
Is there a package I am missing that I can re install and it will at least boot up? Odin fails on me it just freezes on initilizing I try different versions of Odin none work
I get passed the initializing but then it says FAILED no other reason nothing nada please help me... I love the Note 7
I will never swap for an s7
note7kevin said:
I bricked my note 7 every time I plug in a charger it boots into recovery mode in The bottom it says
"no support SINGLE-SKU
Supported API-3
dm-verity verification failed...
E:Failed setting up dirty target [omc-app-link] fail to mount /system as rwE:Failed setting up dirty target
[hwr_symlink] fail to mount /system as rw"
I tried re installing stock rom but no one has it where it's WITH OUT the 60% battery update I had this happen by trying to root via the SPRINT flashing method I came across on this website I had package disabled pro on when I was rooting now before people tell me oh just return it I work at AT&T im not returning my phone I refuse to belive it's gone for good. I know someone out there has to have a solution I have tried everything search wise on google I'm tired of looking night and day
I tried to delete cache that gives an error as well even wiping the phone while in recovery mode gives an error
Is there a package I am missing that I can re install and it will at least boot up? Odin fails on me it just freezes on initilizing I try different versions of Odin none work
I get passed the initializing but then it says FAILED no other reason nothing nada please help me... I love the Note 7
I will never swap for an s7
Click to expand...
Click to collapse
We have the firmware and we have an app to block updates.
That page was zero help it was a firmware issue i got resolved a week ago thanks anyway haha ADMINS PLEASE REMOVE THIS OR LOCK IT IT IS NOW SOLVED
brick it too
note7kevin said:
I bricked my note 7 every time I plug in a charger it boots into recovery mode in The bottom it says
"no support SINGLE-SKU
Supported API-3
dm-verity verification failed...
E:Failed setting up dirty target [omc-app-link] fail to mount /system as rwE:Failed setting up dirty target
[hwr_symlink] fail to mount /system as rw"
I tried re installing stock rom but no one has it where it's WITH OUT the 60% battery update I had this happen by trying to root via the SPRINT flashing method I came across on this website I had package disabled pro on when I was rooting now before people tell me oh just return it I work at AT&T im not returning my phone I refuse to belive it's gone for good. I know someone out there has to have a solution I have tried everything search wise on google I'm tired of looking night and day
I tried to delete cache that gives an error as well even wiping the phone while in recovery mode gives an error
Is there a package I am missing that I can re install and it will at least boot up? Odin fails on me it just freezes on initilizing I try different versions of Odin none work
I get passed the initializing but then it says FAILED no other reason nothing nada please help me... I love the Note 7
I will never swap for an s7
Click to expand...
Click to collapse
i brick m too how do i fix it does anyone know
note7kevin said:
That page was zero help it was a firmware issue i got resolved a week ago thanks anyway haha ADMINS PLEASE REMOVE THIS OR LOCK IT IT IS NOW SOLVED
Click to expand...
Click to collapse
Thanx for helping alot by posting what you did to fix it.
Nice participation...
Where's the NO THANKS button when you need it
les_garten said:
Thanx for helping alot by posting what you did to fix it.
Nice participation...
Where's the NO THANKS button when you need it
Click to expand...
Click to collapse
sorry mate here ill do it now ignore my original reply it was an asshole move and I didnt read correctly
gtavio80 said:
i brick m too how do i fix it does anyone know
Click to expand...
Click to collapse
goto this website: https://note7alliance.com/viewtopic.php?f=14&t=4
find your firmware make sure its the CORRECT CARRIER AND FIRMWARE
download a bunch of ODin firmwares I had to try different ones because 2 out of 3 I tried FAILED to flash
I dont have my computer with me as I am replying but I think it was ODIN 11 or something I cant be exact im sorry
any way download it unzip it and then put it in a folder on your desktop try doing the AP file FIRST then do all the other ones. this part is a LAST hope. but most times ODIN Fails because the usb cable could be in the wrong usb spot usually ODIN works best with the back USB ports of computers why I have no clue lol
if odin still fails try to make sure you have the correct firmware and if you can actually get in to recovery mode your not that bad but if you cant even access recovery mode (volume down and power and home I belive is the method) than you have a harder brick to unbrick but note7alliance is a really good site it just takes alittle more time for people to respond to your support tickets but other than that it usually gets help and is strcitly note 7 information. sign up for it i did and I never regretted it and I still use my note 7 back from the dead any questions feel free to reply and ill try and help.. PS I do not really read my emails so its the reason I never got back to ya in the first place cause this site didnt really help me as much and I didnt need it after I got my issue resolved
note7kevin said:
goto this website: https://note7alliance.com/viewtopic.php?f=14&t=4
find your firmware make sure its the CORRECT CARRIER AND FIRMWARE
download a bunch of ODin firmwares I had to try different ones because 2 out of 3 I tried FAILED to flash
I dont have my computer with me as I am replying but I think it was ODIN 11 or something I cant be exact im sorry
any way download it unzip it and then put it in a folder on your desktop try doing the AP file FIRST then do all the other ones. this part is a LAST hope. but most times ODIN Fails because the usb cable could be in the wrong usb spot usually ODIN works best with the back USB ports of computers why I have no clue lol
if odin still fails try to make sure you have the correct firmware and if you can actually get in to recovery mode your not that bad but if you cant even access recovery mode (volume down and power and home I belive is the method) than you have a harder brick to unbrick but note7alliance is a really good site it just takes alittle more time for people to respond to your support tickets but other than that it usually gets help and is strcitly note 7 information. sign up for it i did and I never regretted it and I still use my note 7 back from the dead any questions feel free to reply and ill try and help.. PS I do not really read my emails so its the reason I never got back to ya in the first place cause this site didnt really help me as much and I didnt need it after I got my issue resolved
Click to expand...
Click to collapse
Thanx, I'm sure this may help someone in the Near future the way things are going.
les_garten said:
Thanx, I'm sure this may help someone in the Near future the way things are going.
Click to expand...
Click to collapse
yeah no worries I just barely use this site since I fixed my device and I barely check my emails because of how much spam I have been super busy at my 3 jobs lol
Les_garten did you get it fixed??
Clo292311 said:
Les_garten did you get it fixed??
Click to expand...
Click to collapse
I never had a problem.
Yet...
Clo292311 said:
Les_garten did you get it fixed??
Click to expand...
Click to collapse
Yeah i did
Hi, I bought a Nokia 6 T-1000 and it wound up having an unofficial rom installed. I am desperately trying to get the official firmware installed and I can't find it. Sadly, now my brand new phone just boots straight into recovery mode. Can anyone backup their firmware and provide it to me or point me to where I could get it?
aNorthernSoul said:
Hi, I bought a Nokia 6 T-1000 and it wound up having an unofficial rom installed. I am desperately trying to get the official firmware installed and I can't find it. Sadly, now my brand new phone just boots straight into recovery mode. Can anyone backup their firmware and provide it to me or point me to where I could get it?
Click to expand...
Click to collapse
Try download the file from below. Follow the steps.
http://www.stechguide.com/install-android-7-1-1-nougat-on-nokia-6/
kanakarkku said:
Try download the file from below. Follow the steps.
Click to expand...
Click to collapse
I had tried that. I can only do method 1 though as it won't go out of recovery mode to turn on USB debugging. When doing method 1, it attempts installing, I see it installing three times with a couple reboots then returns to recovery mode and says the following:
Failed to parse build number in post-build-incremental=00CN_3_170
Failed to parse build number in pre-build-incremental=00CN_1_310
E1004: System partition fails to recover
E:Error in <downloaded filename>
(Status 7)
Installation aborted.
aNorthernSoul said:
I had tried that. I can only do method 1 though as it won't go out of recovery mode to turn on USB debugging. When doing method 1, it attempts installing, I see it installing three times with a couple reboots then returns to recovery mode and says the following:
Failed to parse build number in post-build-incremental=00CN_3_170
Failed to parse build number in pre-build-incremental=00CN_1_310
E1004: System partition fails to recover
E:Error in <downloaded filename>
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
It seems it's not the right file. When I check the built number it is 00CN_3_31A_SP. It would be good to know what built be you have as it is failing to increment the 170 .. I will check later what I can do
kanakarkku said:
It seems it's not the right file. When I check the built number it is 00CN_3_31A_SP. It would be good to know what built be you have as it is failing to increment the 170 .. I will check later what I can do
Click to expand...
Click to collapse
Thanks! Before the update, it was saying "00CN_3_170" under Build Number in Settings. I had spoke to Nokia though and they felt that the firmware had been tampered with.
nokia stuck in recovery mode
aNorthernSoul said:
Hi, I bought a Nokia 6 T-1000 and it wound up having an unofficial rom installed. I am desperately trying to get the official firmware installed and I can't find it. Sadly, now my brand new phone just boots straight into recovery mode. Can anyone backup their firmware and provide it to me or point me to where I could get it?
Click to expand...
Click to collapse
aNorthernSoul said:
Thanks! Before the update, it was saying "00CN_3_170" under Build Number in Settings. I had spoke to Nokia though and they felt that the firmware had been tampered with.
Click to expand...
Click to collapse
kindly tell me what to do my new nokia 6 is also stuck on recovery mode plz help me what to do
kafeel3186 said:
kindly tell me what to do my new nokia 6 is also stuck on recovery mode plz help me what to do
Click to expand...
Click to collapse
I am still trying to figure it out. Based on where you live, you might be able to contact Nokia via online chat and they could direct you to a service centre to flash the phone. They don't have any in Canada though.
I am trying to get the legit firmware but I am not sure if it is the one I have or the modified one my phone came with causing me to be able to unsuccessfully install it.
How did yours wind up in that state?
kanakarkku said:
It seems it's not the right file. When I check the built number it is 00CN_3_31A_SP. It would be good to know what built be you have as it is failing to increment the 170 .. I will check later what I can do
Click to expand...
Click to collapse
Just a side note, I am able to sideload the update via the PC. It quits at 54% (failed to read command * no error) after showing those same parse errors on the screen though. Weirdly, then it reboots with a differently styled logo screen and tried (and fails) to update. Then the logo screen is normal again.
Just in case anyone is wondering, I spoke to the seller I purchased from on Amazon. Whether advertised or not, most China suppliers are installing a custom ROM on all China variants of the Nokia 6. When buying from a more local third party, you have no access to this ROM. I just bought this phone last week and knew about the update from Nokia so had confirmed with them that it currently didn't support Google Services. I didn't want a custom rom.
I have asked for either the rom installed or the official firmware that should have came with the phone and a means to install it or I will take action with Amazon tomorrow. I don't really want to return the phone, I'd likely wait for someone to release an official rom but I could barely afford this phone as it was and it is currently useless.
I just wanted to warn anyone else thinking about buying the Chinese model.
kanakarkku said:
It seems it's not the right file. When I check the built number it is 00CN_3_31A_SP. It would be good to know what built be you have as it is failing to increment the 170 .. I will check later what I can do
Click to expand...
Click to collapse
aNorthernSoul said:
I had tried that. I can only do method 1 though as it won't go out of recovery mode to turn on USB debugging. When doing method 1, it attempts installing, I see it installing three times with a couple reboots then returns to recovery mode and says the following:
Failed to parse build number in post-build-incremental=00CN_3_170
Failed to parse build number in pre-build-incremental=00CN_1_310
E1004: System partition fails to recover
E:Error in <downloaded filename>
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
I had the same result after method 1 via sd
Quixote78 said:
I had the same result after method 1 via sd
Click to expand...
Click to collapse
And after method 2 via ADB)))
As result device stuck in bootloop mode.
I've managed to bring it back with MiFlash only.
kanakarkku said:
Try download the file from below. Follow the steps.
http://www.stechguide.com/install-android-7-1-1-nougat-on-nokia-6/
Click to expand...
Click to collapse
IMO the file that you download is to update the existing working ROM and the op has somehow ended up with one that doesn't work. So I think he would need the entire ROM the exact version that he last had to get back into the phone and then update.
[TA-1053] Official OTA 8.1 - Stuck at Recovery with "No command" warning after update
Hey guys,
I received the official update for Android 8.1 on my Nokia 5 TA-1053. I had no root, no Custom Recovery and bootloader locked.
During the update, as usual, the phone rebooted, and I got a error waring "No command". The waring is in recovery mode and I can access recovery options like "updtade from ADB, SD Card. Tried uptading with Android 8.0, but after reboot, still get the same error.
Does anyone have any clue?
Erkyem said:
Hey guys,
I received the official update for Android 8.1 on my Nokia 5 TA-1053. I had no root, no Custom Recovery and bootloader locked.
During the update, as usual, the phone rebooted, and I got a error waring "No command". The waring is in recovery mode and I can access recovery options like "updtade from ADB, SD Card. Tried uptading with Android 8.0, but after reboot, still get the same error.
Does anyone have any clue?
Click to expand...
Click to collapse
That happened to me too, I had to rollback to 7.1 flashing December update and flashing OST before I was able to use my phone again.
If you haven't yet recovered your phone, I uploaded April and May OTAs here:
https://forum.xda-developers.com/showpost.php?p=76513215&postcount=61
If that doesn't work, you will have to do what I did to get my phone up and running
Hi, and thanks.
I spent the night, without any success, trying to downgrade, using this https://forum.xda-developers.com/nokia-5/how-to/guide-how-to-downgrade-official-oreo-to-t3746007.
The OST flashing the nb0 but always fails with error "BATTERY_VOLTAGE_TOO_LOW_FAIL (0xA24B)". I Tried many, many times. If I sideload the OTA through adb (OTA is around 1.7 GB) it will fail at around 47%. Error message on ADB: "adb: failed to read command: No error". Error on phone: "Warning: no" and cannot read anymore. Then it goes to the little android screen with the no command warning, again.
Tried unlock bootloader now, without success. Maybe I need the full OTA for 8.1, but I'm not able to find it.
Erkyem said:
Hi, and thanks.
I spent the night, without any success, trying to downgrade, using this https://forum.xda-developers.com/nokia-5/how-to/guide-how-to-downgrade-official-oreo-to-t3746007.
The OST flashing the nb0 but always fails with error "BATTERY_VOLTAGE_TOO_LOW_FAIL (0xA24B)". I Tried many, many times. If I sideload the OTA through adb (OTA is around 1.7 GB) it will fail at around 47%. Error message on ADB: "adb: failed to read command: No error". Error on phone: "Warning: no" and cannot read anymore. Then it goes to the little android screen with the no command warning, again.
Tried unlock bootloader now, without success. Maybe I need the full OTA for 8.1, but I'm not able to find it.
Click to expand...
Click to collapse
Did you try the OTAs I listed?
If they didn't work, try to flash one of the OTAs here:
https://forum.xda-developers.com/nokia-5/development/ota-nokia-5-ta-1053-monthly-ota-zip-t3655123
They are much smaller. Then you can try flashing OST
BTW I hope you didn't try flashing any of the nb0 files from the mega link in the post you mentioned. None of them are Nokia5 nb0s
If you don't have one, you can try the one in this link:
https://drive.google.com/file/d/0B60NFIDB93wudDNXaG5vMkEyWVE/view
redweaver said:
That happened to me too, I had to rollback to 7.1 flashing December update and flashing OST before I was able to use my phone again.
If you haven't yet recovered your phone, I uploaded April and May OTAs here:
https://forum.xda-developers.com/showpost.php?p=76513215&postcount=61
If that doesn't work, you will have to do what I did to get my phone up and running
Click to expand...
Click to collapse
Please, what did you do? Flashing Dec Update then using an nb0 file with OST, it got stuck at "Connection Failed, 0xc6da" Error; do you have any idea of what I should do?
K1r1k4z3 said:
Please, what did you do? Flashing Dec Update then using an nb0 file with OST, it got stuck at "Connection Failed, 0xc6da" Error; do you have any idea of what I should do?
Click to expand...
Click to collapse
You got this error when flashing the nb0?
redweaver said:
You got this error when flashing the nb0?
Click to expand...
Click to collapse
Yes, I did. I have no idea what it means.
K1r1k4z3 said:
Yes, I did. I have no idea what it means.
Click to expand...
Click to collapse
How many times did you try again?
redweaver said:
How many times did you try again?
Click to expand...
Click to collapse
Severally.
Meanwhile, the OST tool won't run on my Windows 10 PC. I get this error. Is there something I'm missing if you've run this tool on Windows 10 before. Meanwhile I'm at PH.
K1r1k4z3 said:
Severally.
Meanwhile, the OST tool won't run on my Windows 10 PC. I get this error. Is there something I'm missing if you've run this tool on Windows 10 before. Meanwhile I'm at PH.
Click to expand...
Click to collapse
I don't like Windows 10. My lappy comes with Win 8.1. I had to dual boot win 7 just to run OST
redweaver said:
I don't like Windows 10. My lappy comes with Win 8.1. I had to dual boot win 7 just to run OST
Click to expand...
Click to collapse
Could you help me with the specific nb0 file you used in flashing yours.
K1r1k4z3 said:
Could you help me with the specific nb0 file you used in flashing yours.
Click to expand...
Click to collapse
I got it from one of those links
https://mega.nz/#!HoNX1CBT!AORGMLndzcbc5iOBrJlLlLKyncZ5hImJirnPApRGj_s
redweaver said:
I got it from one of those links
https://mega.nz/#!HoNX1CBT!AORGMLndzcbc5iOBrJlLlLKyncZ5hImJirnPApRGj_s
Click to expand...
Click to collapse
I'm kinda confused; what's the difference between "ND1-3320-0-00WW-A02.nb0" and "ND1-3700-0-00WW-B03.nb0"
Cos I'm flashing this "ND1-3320-0-00WW-A02.nb0 with the OST right now and it's still stuck at "Reflash Service Bootloader" for over 20mins now. Is this normal?
K1r1k4z3 said:
I'm kinda confused; what's the difference between "ND1-3320-0-00WW-A02.nb0" and "ND1-3700-0-00WW-B03.nb0"
Cos I'm flashing this "ND1-3320-0-00WW-A02.nb0 with the OST right now and it's still stuck at "Reflash Service Bootloader" for over 20mins now. Is this normal?
Click to expand...
Click to collapse
I honestly have no idea. Wait for it to finish or give an error, otherwise you risk bricking your phone for good. Did you "downgrade" to nougat before flashing?
FINALLY! I got my Nokia 5 working like new.
Thanks @redbeaver! You've got no idea, but you helped alot!
redweaver said:
I honestly have no idea. Wait for it to finish or give an error, otherwise you risk bricking your phone for good. Did you "downgrade" to nougat before flashing?
Click to expand...
Click to collapse
I sent you a PM sir, please attend to it.
I'm trying to use PartCyborgRom on my Galaxy S8 SM-G950U USA version. When I first clicked start in Odin, it said, "complete(write) operation failed". Following that I get a blue screen that says something along the lines of update failed. If I flash part 2 it will let me go back into download mode but the cycle repeats. So far I have used two different computers (with the Samsung drivers installed), at least 2 USB 2 and 3 ports (I know it says not to use 3 but I wanted to see if anything changed), and 2 different cables. I've seen other threads where people say to keep trying while leaving Odin open, etc but none of that has worked either. Does anyone know what the cause could be?
QuantumPie said:
I'm trying to use PartCyborgRom on my Galaxy S8 SM-G950U USA version. When I first clicked start in Odin, it said, "complete(write) operation failed". Following that I get a blue screen that says something along the lines of update failed. If I flash part 2 it will let me go back into download mode but the cycle repeats. So far I have used two different computers (with the Samsung drivers installed), at least 2 USB 2 and 3 ports (I know it says not to use 3 but I wanted to see if anything changed), and 2 different cables. I've seen other threads where people say to keep trying while leaving Odin open, etc but none of that has worked either. Does anyone know what the cause could be?
Click to expand...
Click to collapse
You need to read a bit better and you would see that most of the errors you received are normal
What bootloader revision is your device on. 5th number from end is bootloader revision
Try to read a bit better and search the thread. All is answered there. There will be failures but some are normal and needed for this root method to work
TheMadScientist said:
You need to read a bit better and you would see that most of the errors you received are normal
What bootloader revision is your device on. 5th number from end is bootloader revision
Try to read a bit better and search the thread. All is answered there. There will be failures but some are normal and needed for this root method to work
Click to expand...
Click to collapse
Just realized I could search for keywords in a thread a few minutes ago.
I'm no longer sure but I'm guessing it was past 2. If that is the case, is there any way I can root?
QuantumPie said:
Just realized I could search for keywords in a thread a few minutes ago.
I'm no longer sure but I'm guessing it was past 2. If that is the case, is there any way I can root?
Click to expand...
Click to collapse
I didn't mean to sound like a arse. This root method can be tricky is why I say read read read. A lot of people miss the section of upload mode errors and device software unauthorized screen
What is the current firmware on the device.
If you don't see like a secure check fail. Binary or something you should be good. Which would be displayed in download mode screen. And Odin would fail right off
I'm now back to stock with a v5 bootloader. I'm trying to follow this method but I am getting a "Re-Partition operation failed" error even though I don't have that option ticked. Do I need it ticked or have to use the pit file? I can't get a clear sense of what the pit file does from my googling.
TheMadScientist said:
I didn't mean to sound like a arse. This root method can be tricky is why I say read read read. A lot of people miss the section of upload mode errors and device software unauthorized screen
What is the current firmware on the device.
If you don't see like a secure check fail. Binary or something you should be good. Which would be displayed in download mode screen. And Odin would fail right off
Click to expand...
Click to collapse
I'm now back to stock with a v5 bootloader. I'm trying to follow this method but I am getting a "Re-Partition operation failed" error even though I don't have that option ticked. Do I need it ticked or have to use the pit file? I can't get a clear sense of what the pit file does from my googling.
(Sorry for double posting. I wasn't sure if you get a notification without me replying to you)
QuantumPie said:
I'm now back to stock with a v5 bootloader. I'm trying to follow this method but I am getting a "Re-Partition operation failed" error even though I don't have that option ticked. Do I need it ticked or have to use the pit file? I can't get a clear sense of what the pit file does from my googling.
(Sorry for double posting. I wasn't sure if you get a notification without me replying to you)
Click to expand...
Click to collapse
V5 is unrootsble and no downgrade. You might as well find a new device if you need root