Related
Got myself in a bind. Bought a new Note 5 today to upgrade to 64GB. Forgot to OEM unlock, and the phone is bricked for the moment. The new image N920TUVU3DPG1 isn't available to download yet. Any suggestions, or does anyone know where the new image can be found yet? What a rookie mistake! Smart Switch in emergency recovery tries to flash N920TUVU2DPD1 and fails. Downgrading doesn't work either.
same here. where can we get it from?
rmarinella said:
Got myself in a bind. Bought a new Note 5 today to upgrade to 64GB. Forgot to OEM unlock, and the phone is bricked for the moment. The new image N920TUVU3DPG1 isn't available to download yet. Any suggestions, or does anyone know where the new image can be found yet? What a rookie mistake! Smart Switch in emergency recovery tries to flash N920TUVU2DPD1 and fails. Downgrading doesn't work either.
Click to expand...
Click to collapse
Just downgrade to an older version via Odin if possible. It can be done on Verizon so I don't see why not on yours.
MrMike2182 said:
Just downgrade to an older version via Odin if possible. It can be done on Verizon so I don't see why not on yours.
Click to expand...
Click to collapse
I tried the previous version while in download mode using Odin. Loaded the stock rom in the AP slot and started it then it failed pretty quick. The com shows connected before I hit start but it still fails.
mistaedster said:
I tried the previous version while in download mode using Odin. Loaded the stock rom in the AP slot and started it then it failed pretty quick. The com shows connected before I hit start but it still fails.
Click to expand...
Click to collapse
You have to make sure you have the correct firmware! You should be able to see which one is already on the phone while in recovery mode.
MrMike2182 said:
You have to make sure you have the correct firmware! You should be able to see which one is already on the phone while in recovery mode.
Click to expand...
Click to collapse
That's the problem. I can't find the right firmware
mistaedster said:
That's the problem. I can't find the right firmware
Click to expand...
Click to collapse
I think we're stuck with a very expensive paperweight until Samsung releases full firmware for the N920TUVU3DPG1 update.
rmarinella said:
I think we're stuck with a very expensive paperweight until Samsung releases full firmware for the N920TUVU3DPG1 update.
Click to expand...
Click to collapse
I actually got darthstalker rom working on mine then moved to sick ass rom. I flashed the stock deodexed kernel from original android development then the rom via twrp
mistaedster said:
I actually got darthstalker rom working on mine then moved to sick ass rom. I flashed the stock deodexed kernel from original android development then the rom via twrp
Click to expand...
Click to collapse
Stock Kernel from where?
rmarinella said:
Stock Kernel from where?
Click to expand...
Click to collapse
http://forum.xda-developers.com/tmo...ernel-stock-modified-kernel-touchwiz-t3194148
mistaedster said:
http://forum.xda-developers.com/tmo...ernel-stock-modified-kernel-touchwiz-t3194148
Click to expand...
Click to collapse
OK, thanks. Looks like we aren't in the same situation though. I can't get into, or flash TWRP.
Stock N920TUVU3DPG1 Firmware now available here: https://www.androidfilehost.com/?fid=24588232905721433
rmarinella said:
Stock N920TUVU3DPG1 Firmware now available here: https://www.androidfilehost.com/?fid=24588232905721433
Click to expand...
Click to collapse
Hope u fixed ur problem, I'm still on Note 4, was waiting for u to fix the new firmware for us last month, and now we just got another one, so shocked Samsung is actually taking care of the Note 4 N910T,
My rom boots up, but can't see sim card, external storage, wifi doesn't connect and so forth, I guess they did something with the new MM that @dsixda kitchen doesn't work correctly somewhere anymore,
need to learn Ubuntu, not easy with no help,,, I made an external drive with 16.04 but need to java development and figure the rest out, not easy with 2 kids.. and wifey..
and u r also in FL, by the way thanks for the updater script for the past v5.1.1 roms we had...
Samsung keeps raising prices on these phones, ridiculous no reason the new Note 7 will be $849 cause they r only making egde style phones.
I'm glad they pushed me to my limits, first it was HTC, I had all the HTC phone till M7, for when they had the first tmobile dash windows phone.. haha..
don't know whats next, maybe crapple... no rush since the note 4 is still rocking good,
but the Note 7, water resistence is awesome is the only kool thing I guess.
Seems like I'm having the same problem frp lock and drk has anyone found a solution yet. I can't seem to find any way to fix this yet. Appreciate any help in advance
I could help with this issue, just let me know if you need my assistant I would have to remotely do this to accomplish this thanks..
I had been reading up on the Dirty Cow exploit/root method, and it seemed to be compatible with all Android devices, so I took a little chance with my v10, and it worked perfectly! I was on the stock unrooted 20l update, and followed all the steps here: https://github.com/jcadduono/android_external_dirtycow#running
Notes:
-I put our TWRP image and SuperSu zip on the root of my sdcard
-For the very last command, replace 'twrp.img' with the name of your TWRP image file(or change the name of your TWRP fiile to twrp.img ).
-Like it says in the instructions, the phone did look like maybe it bricked at one point, with a strange backlighting on the Tmobile boot screen. It worked out tho!
-My boot loader was unlocked prior to doing these steps
Info thread, v20: http://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Got all the files here: https://build.nethunter.com/android-tools/dirtycow/arm64/
YrrchSebor said:
I had been reading up on the Dirty Cow exploit/root method, and it seemed to be compatible with all Android devices, so I took a little chance with my v10, and it worked perfectly! I was on the stock unrooted 20l update, and followed all the steps here: https://github.com/jcadduono/android_external_dirtycow#running
Notes:
-I put our TWRP image and SuperSu zip on the root of my sdcard
-For the very last command, replace 'twrp.img' with the name of your TWRP image file(or change the name of your TWRP fiile to twrp.img ).
-Like it says in the instructions, the phone did look like maybe it bricked at one point, with a strange backlighting on the Tmobile boot screen. It worked out tho!
Info thread, v20: http://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Got all the files here: https://build.nethunter.com/android-tools/dirtycow/arm64/
Click to expand...
Click to collapse
Great job. You know technically these same instructions should work for ANY of the v10 variants ..verizon...at&t etc....including the ones that up till now didn't have root at all.
Thanks. Doesn't it require an unlocked boot loader tho, or no?
Sent from my LG-H901 using XDA-Developers mobile app
YrrchSebor said:
Thanks. Doesn't it require an unlocked boot loader tho, or no?
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
It requires an unlocked boot loader.
YrrchSebor said:
Thanks. Doesn't it require an unlocked boot loader tho, or no?
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes but for example verizon's comes with an unlocked bootloader...they just only had root for the 5.x rom's and none for the 6.0.
famewolf said:
Yes but for example verizon's comes with an unlocked bootloader...they just only had root for the 5.x rom's and none for the 6.0.
Click to expand...
Click to collapse
Gotcha yeah, it seems like good news for all phones with unlockable bootloaders until Google, and then the OEMs, patch the exploit.
Sent from my LG-H901 using XDA-Developers mobile app
will this factory reset my phone?
CrimsonSaber5G said:
will this factory reset my phone?
Click to expand...
Click to collapse
Nope. Unlocking your bootloader will but this won't in itself.
Sent from my LG-H901 using XDA-Developers mobile app
thank you, and i have the tmobile variant, that means my bootloader is already unlocked??
CrimsonSaber5G said:
thank you, and i have the tmobile variant, that means my bootloader is already unlocked??
Click to expand...
Click to collapse
No, it means it's unlockable, but you have to actively unlock it. There should be a thread here somewhere if you haven't done that yet, but it's just boot into bootloader and then 'fastboot oem unlock'
Edit: in case you need it there are great instructions in the v20 thread that I linked in the first post.
Sent from my LG-H901 using XDA-Developers mobile app
YrrchSebor said:
Gotcha yeah, it seems like good news for all phones with unlockable bootloaders until Google, and then the OEMs, patch the exploit.
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
The cow method means copy on write...
This means as anything is written it is copied (or flashed or burned; whatever you want to call your desired definition)
You could in theory copy dummy files to a temp location and actually write to a permanent location...
Or am I thinking wrong about it?
If this is a viable option to ALL phones I don't think Google or manufactures could (or would for that matter) actually patch this kind of exploit as it would be super time consuming.
just confirming that Root 20l w/Dirty Cow does work.
Finally got my replacement V10 back, and all is a go again. Stock rooted,
Not sure the novice should try this, as its pretty nerve racking. If you follow the directions correctly it does work great.
Surprised they have closed this backdoor yet,
thanks for being the first to try this on a V10.
je2854 said:
The cow method means copy on write...
This means as anything is written it is copied (or flashed or burned; whatever you want to call your desired definition)
You could in theory copy dummy files to a temp location and actually write to a permanent location...
Or am I thinking wrong about it?
If this is a viable option to ALL phones I don't think Google or manufactures could (or would for that matter) actually patch this kind of exploit as it would be super time consuming.
Click to expand...
Click to collapse
I think it's considered a very serious vulnerability that must and will be patched soon. They can't have root access so easily obtained on any device.
Amd4life said:
just confirming that Root 20l w/Dirty Cow does work.
Finally got my replacement V10 back, and all is a go again. Stock rooted,
Not sure the novice should try this, as its pretty nerve racking. If you follow the directions correctly it does work great.
Surprised they have closed this backdoor yet,
thanks for being the first to try this on a V10.
Click to expand...
Click to collapse
You're welcome, and thanks for confirming. That one step where the screen goes weirdly backlit with the Tmo splash screen is a bit nerve-wracking, and so is writing recovery this way, but I was comforted by the fact that you can just tell it to to write to the recovery partition rather than having to know the more technical name/location(not sure if this was possible a few years back?)
Anyway, if I did brick I was gonna go straight to the store and buy a ZTE Zmax Pro for $180 haha.
Which reminds me, does anyone know if there is a way to simply push su into /system once you have the root shell, instead of writing recovery to flash SuperSu? Just curious. I sorta wanted to do that but then I just went with TWRP.
YrrchSebor said:
Which reminds me, does anyone know if there is a way to simply push su into /system once you have the root shell, instead of writing recovery to flash SuperSu? Just curious. I sorta wanted to do that but then I just went with TWRP.
Click to expand...
Click to collapse
No. The shell has limited access...it has just enough permissions to write recovery and access some things on boot...you need to get it a recovery where you can then flash a zip to install superuser.
Thanks so much for this info, I was actually about to post a new thread to see if root for 20L had been achieved.
But a few questions:
Is there a KDZ/TOT available for 20L? Or is it delivered in update.zip format via OTA?
Is there a way to root 20L without touching system partition? Like, you know, systemless root? I was thinking that maybe it might be possible to flash Magisk from TWRP then install systemless phh Superuser or (less preferable for me) SuperSU. This way I can still take the official Nougat OTA when it hits, without losing root. But the catch is, TWRP needs to be accessible first.
Well, time to sleep for now, it's been a long 3 days, subsisting on Monster and cigs. I'll tackle this when I eventually wake up.
Like the last guy, I've got a million questions on this. I need to find the changelog on 20L to begin with, because if they didn't fix the VoLTE silence on calling, then it's useless to me. I wonder where the OP was with his existing V10.. because I'm currently on 20J rooted with twrp. Seems with the instructions posted, I would have to use LG bridge to go back to 100% stock, then upgrade to 20L then hope this works. Again, the radios are probably modified so there's probably some kind of anti-rollback involved as well.
Great post though! Great work discovering this! Definitely in the right direction!
AnonVendetta said:
Thanks so much for this info, I was actually about to post a new thread to see if root for 20L had been achieved.
But a few questions:
Is there a KDZ/TOT available for 20L? Or is it delivered in update.zip format via OTA?
Is there a way to root 20L without touching system partition? Like, you know, systemless root? I was thinking that maybe it might be possible to flash Magisk from TWRP then install systemless phh Superuser or (less preferable for me) SuperSU. This way I can still take the official Nougat OTA when it hits, without losing root. But the catch is, TWRP needs to be accessible first.
Well, time to sleep for now, it's been a long 3 days, subsisting on Monster and cigs. I'll tackle this when I eventually wake up.
Click to expand...
Click to collapse
There is a 20l KDZ floating around in some other threads. Not sure if there is or will be a systemless root, never even done it myself [emoji4]
Sent from my LG-H901 using XDA-Developers mobile app
joesee said:
Like the last guy, I've got a million questions on this. I need to find the changelog on 20L to begin with, because if they didn't fix the VoLTE silence on calling, then it's useless to me. I wonder where the OP was with his existing V10.. because I'm currently on 20J rooted with twrp. Seems with the instructions posted, I would have to use LG bridge to go back to 100% stock, then upgrade to 20L then hope this works. Again, the radios are probably modified so there's probably some kind of anti-rollback involved as well.
Great post though! Great work discovering this! Definitely in the right direction!
Click to expand...
Click to collapse
The Volte silence bug is fixed in 20l, as many have reported. I had updated officially to 20l and was stock unrooted prior to this. But for people who are rooted on 20j or earlier, I believe Eliminator has released a pre-rooted update, so maybe you'd wanna do that instead.
Sent from my LG-H901 using XDA-Developers mobile app
I've looked everywhere and haven't found anything on rooting for the 930az. Found an xda rep that said his root or the root he got if from was for all s7 . Followed the instructions step by step till I reached flashing ,then my phone got stuck in a bootloop .luckily I found a post on the inputs of Oden to return to stock but I'm still persistent on finding a root for it please help!!!
Jay351 said:
I've looked everywhere and haven't found anything on rooting for the 930az. Found an xda rep that said his root or the root he got if from was for all s7 . Followed the instructions step by step till I reached flashing ,then my phone got stuck in a bootloop .luckily I found a post on the inputs of Oden to return to stock but I'm still persistent on finding a root for it please help!!!
Click to expand...
Click to collapse
When you say flashing, fhalsing what exactly got you the bootloop? Was it flashing the engineering Boot.img through Odin or the fix S7 zip through Flashfire... Or something else?
I don't have a Cricket branded S7, but always offering to help you research.
Sent from my SM-G930P using Tapatalk
POWerSUrgeSW3 said:
When you say flashing, fhalsing what exactly got you the bootloop? Was it flashing the engineering Boot.img through Odin or the fix S7 zip through Flashfire... Or something else?
I don't have a Cricket branded S7, but always offering to help you research.
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
Thanks for the help it was https://youtu.be/KawiIZ4bAV8
As soon as I got to the boot.img and downloaded it to my phone that when it started.
Jay351 said:
Thanks for the help it was https://youtu.be/KawiIZ4bAV8
As soon as I got to the boot.img and downloaded it to my phone that when it started.
Click to expand...
Click to collapse
Only a few things I can think to ask:
1) You are using the Odin version by PrinceComsy... not the original version of Odin?
2) When you download the engineering boot image, you're downloading it for your phone model (S7 for S7, S7 Edge for the S7 Edge)? Maybe you accidentally downloaded the wrong one?
3) When uploading the boot image through Odin, the boot image TAR file is in the AP slot of Odin?
4) Last thing I can think is easy, is the boot image is still a TAR file correct? Its not a ZIP or any other file extension?
Have you tried downloading the image again? I invite you to check out a thread I'm part of if you want another location to download the S7 engineering boot image, that thread located here and the boot image file can be downloaded directly from here
POWerSUrgeSW3 said:
Only a few things I can think to ask:
1) You are using the Odin version by PrinceComsy... not the original version of Odin?
Yes and I tried the original also
2) When you download the engineering boot image, you're downloading it for your phone model (S7 for S7, S7 Edge for the S7 Edge)? Maybe you accidentally downloaded the wrong one?
Correct s7 for s7
3) When uploading the boot image through Odin, the boot image TAR file is in the AP slot of Odin?
Yes
4) Last thing I can think is easy, is the boot image is still a TAR file correct? Its not a ZIP or any other file extension?
I made sure it was still a tar file.
Thanks for your help I'll check it out
Click to expand...
Click to collapse
Jay351 said:
POWerSUrgeSW3 said:
Only a few things I can think to ask:
1) You are using the Odin version by PrinceComsy... not the original version of Odin?
Yes and I tried the original also
2) When you download the engineering boot image, you're downloading it for your phone model (S7 for S7, S7 Edge for the S7 Edge)? Maybe you accidentally downloaded the wrong one?
Correct s7 for s7
3) When uploading the boot image through Odin, the boot image TAR file is in the AP slot of Odin?
Yes
4) Last thing I can think is easy, is the boot image is still a TAR file correct? Its not a ZIP or any other file extension?
I made sure it was still a tar file.
Thanks for your help I'll check it out
Click to expand...
Click to collapse
You're welcome, just trying to figure it out. Though I see this is a common thing, so I wonder what is different with the Cricket version?
And you're rooting the Nougat version of the phone? This seems to be a topic floating around with no one explaining it. I've tried looking to see if maybe the processor might be somehow a "reduced" version of the 820 compared to the others... but everything makes it look like it should work.
Only other thing I would say is go back through all the steps, and make sure you're not accidentally skipping one. I did that a bunch of times when I first started off. I ended up printing off instructions and making note edits. Took me a few different sets of instructions until I found a formula that worked for my G930P
Click to expand...
Click to collapse
POWerSUrgeSW3 said:
Jay351 said:
You're welcome, just trying to figure it out. Though I see this is a common thing, so I wonder what is different with the Cricket version?
And you're rooting the Nougat version of the phone? This seems to be a topic floating around with no one explaining it. I've tried looking to see if maybe the processor might be somehow a "reduced" version of the 820 compared to the others... but everything makes it look like it should work.
Only other thing I would say is go back through all the steps, and make sure you're not accidentally skipping one. I did that a bunch of times when I first started off. I ended up printing off instructions and making note edits. Took me a few different sets of instructions until I found a formula that worked for my G930P
Click to expand...
Click to collapse
I'm sorry no we haven't received the update yet I'm still on 6.0.1. Do you mean like mixing up the steps and finding which worked with your phone?
Click to expand...
Click to collapse
Jay351 said:
POWerSUrgeSW3 said:
I'm sorry no we haven't received the update yet I'm still on 6.0.1. Do you mean like mixing up the steps and finding which worked with your phone?
Click to expand...
Click to collapse
Oh I'll have to go back and do some rereading then, because I thought I saw some websites saying that phone was already on Nougat. If you're still on MM this should be easier I would think... hmmm
For me, it took me about 4 or 5 different threads of talking about how they rooted their Sprint S7 phone, for me to find the right instructions for myself to root my phone. But I know along the way I would miss a step, then my phone wouldn't boot or bootloop like yours. That's why I went back and printed out instructions and checked off to make sure I didn't skip anything. After awhile I could wrap my head around it.
Just saying we are all human, so it's easy to skip a step. Though it doesn't seem like you're the only one having this problem. But if all the branded US phones are pretty much rooted one way or another, I don't see why yours would be any different.
Click to expand...
Click to collapse
POWerSUrgeSW3 said:
Jay351 said:
Oh I'll have to go back and do some rereading then, because I thought I saw some websites saying that phone was already on Nougat. If you're still on MM this should be easier I would think... hmmm
For me, it took me about 4 or 5 different threads of talking about how they rooted their Sprint S7 phone, for me to find the right instructions for myself to root my phone. But I know along the way I would miss a step, then my phone wouldn't boot or bootloop like yours. That's why I went back and printed out instructions and checked off to make sure I didn't skip anything. After awhile I could wrap my head around it.
Just saying we are all human, so it's easy to skip a step. Though it doesn't seem like you're the only one having this problem. But if all the branded US phones are pretty much rooted one way or another, I don't see why yours would be any different.
Click to expand...
Click to collapse
Your probably right I'll try those steps again and see if anything changes. The only model I see that's close to g930az would be the at&t which is g930a. I know I got lucky with the last attempt to try with it in soft brick. I just don't want to try to many and it be completely screwed. Because on cricket you have to buy all of you phones up front well at least I had to with mine. I'll try it again and let you know if it worked or I have a paper weight haha. Thanks again
Click to expand...
Click to collapse
Jay351 said:
POWerSUrgeSW3 said:
Your probably right I'll try those steps again and see if anything changes. The only model I see that's close to g930az would be the at&t which is g930a. I know I got lucky with the last attempt to try with it in soft brick. I just don't want to try to many and it be completely screwed. Because on cricket you have to buy all of you phones up front well at least I had to with mine. I'll try it again and let you know if it worked or I have a paper weight haha. Thanks again
Click to expand...
Click to collapse
With following the steps you are and what you have happening, you should be OK with being able Odin back to factory firmware.
Yeah Cricket is kind of the double edge sword, you have to buy the phone up front, but they have CHEAP prices for good service. I had them when I first moved to Arizona and would have kept them, if I didn't travel so much.
Report back if anything changes.
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
Jay351 said:
I've looked everywhere and haven't found anything on rooting for the 930az. Found an xda rep that said his root or the root he got if from was for all s7 . Followed the instructions step by step till I reached flashing ,then my phone got stuck in a bootloop .luckily I found a post on the inputs of Oden to return to stock but I'm still persistent on finding a root for it please help!!!
Click to expand...
Click to collapse
hey can you help get my s7 g930az back to stock. i also happen to be stuck in a bootloop and i've searched everywhere and nothing
leonardo879 said:
hey can you help get my s7 g930az back to stock. i also happen to be stuck in a bootloop and i've searched everywhere and nothing
Click to expand...
Click to collapse
Do you have the stock firmware and Odin? Flash that will get you back to stock and functional. Does take awhile to flash the full imagine, but can pretty much fix any software brick issues.
Sent from my SM-G930P using Tapatalk
POWerSUrgeSW3 said:
Do you have the stock firmware and Odin? Flash that will get you back to stock and functional. Does take awhile to flash the full imagine, but can pretty much fix any software brick issues.
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
Yes i have the stock firmware and Odin but it always fails. is there any other way to fix it? i tried smart switch and it stops at 69% and it says error so idk what else to try.
leonardo879 said:
Yes i have the stock firmware and Odin but it always fails. is there any other way to fix it? i tried smart switch and it stops at 69% and it says error so idk what else to try.
Click to expand...
Click to collapse
What's the failure error? OEM Unlock in Android was turned on correct?
Sent from my SM-G930P using Tapatalk
POWerSUrgeSW3 said:
What's the failure error? OEM Unlock in Android was turned on correct?
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
It says "Encrypt Error" in smart switch. What does OEM Unlock mean?
leonardo879 said:
It says "Encrypt Error" in smart switch. What does OEM Unlock mean?
Click to expand...
Click to collapse
By default the phones are locked so someone can't steal your phone and Reimage it. If you boot your phone up after trying to flash do you get an FPR or some sort of error like that?
Sent from my SM-G930P using Tapatalk
POWerSUrgeSW3 said:
By default the phones are locked so someone can't steal your phone and Reimage it. If you boot your phone up after trying to flash do you get an FPR or some sort of error like that?
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
No it doesn't. The phone is just stuck in a boot loop after i tried installing a .tar file in Odin that i got from a youtube video showing how to root it but it doesn't work so now i'm stuck on he boot loop.
leonardo879 said:
No it doesn't. The phone is just stuck in a boot loop after i tried installing a .tar file in Odin that i got from a youtube video showing how to root it but it doesn't work so now i'm stuck on he boot loop.
Click to expand...
Click to collapse
Yes but if you try to Odin back to the stock firmware what happens then?
Sent from my SM-G930P using Tapatalk
POWerSUrgeSW3 said:
Yes but if you try to Odin back to the stock firmware what happens then?
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
It says "Fail. Model Mismatch fail" something a long that
leonardo879 said:
It says "Fail. Model Mismatch fail" something a long that
Click to expand...
Click to collapse
I would recommend going to sammobile or updato to get the firmware for your phone. Sounds like you have the wrong model. If you need help I can help in an hour or so when I get home.
Sent from my SM-G930P using Tapatalk
These UFirm Carrier Roms are so big I chose to use the flash system.img.ext4 first method in Flashfire followed by a partial rom zip so I could get all the multicarrier stuff to fit. This way also insures that all symlinks and permissions are correct.
Download N8 Firmware HERE
Download NOTE8_DEODEX_ROM_AQI5_V1.zip
Directions
You must be rooted
Extract AP file from the firmware zip and copy AP file to your phone internal storage
Copy NOTE8_DEODEX_ROM_AGI5_V1.zip to your phone
Open Flashfire and choose add zip and choose NOTE8_DEODEX_ROM_AQI5_V1.zip mount system when it ask
In Flashfire choose add firmware and choose AP file. Select system.img.ext4 and persit.img.ext4 DO NOT select boot and recovery images
Add wipe and move wipe to top of flash order
Make sure inject supersu IS NOT SELECTED
Flash order should be wipe; firmware; rom
Click Flash
Faetures
Fully Stock All Carriers
Deodexed
Rooted
Volte Icon Fixed
Extras: These are already included in the rom but may come in handy
NOTE8_VOLTE_ICON_FIX_ALL_VARIANTS.zip
NOTE8_ADD_WIFICALLING_VOLTE_ICON_FIX_VZW.zip
....This is for getting WifiCalling and Visual Voicemail working on U1 Firmware (Unlocked firmware) For Verizon Only
Keyser~soz3 said:
Will you make this for tmobile note 8 please
Click to expand...
Click to collapse
What Does the title say?
@jkruse, good to see you here man!!! Just got the note from my s7 edge loved your rom on the edge.
Are you planning something similar here? Either way good to know you are here.?
Sent from my SM-N950U using Tapatalk
lahegry said:
@jkruse, good to see you here man!!! Just got the note from my s7 edge loved your rom on the edge.
Are you planning something similar here? Either way good to know you are here.?
Click to expand...
Click to collapse
I don't have the Note8 I just made this per requests for some people that want to run xposed. So I won't be doing much here
jrkruse said:
I don't have the Note8 I just made this per requests for some people that want to run xposed. So I won't be doing much here
Click to expand...
Click to collapse
Well, darn it! Good to see you none the less.
Sent from my SM-N950U using Tapatalk
This rom runs great!! To be expected being from jrkruse. Played with it this weekend and used it all day today at work. Super fast and smooth. Battery lasts much better than i figured it would. Brought my charger to work to be safe, and actually used less battery than stock setup. Thanks jrkruse for this and whatever you end up doing here.
Bsober said:
This rom runs great!! To be expected being from jrkruse. Played with it this weekend and used it all day today at work. Super fast and smooth. Battery lasts much better than i figured it would. Brought my charger to work to be safe, and actually used less battery than stock setup. Thanks jrkruse for this and whatever you end up doing here.
Click to expand...
Click to collapse
People need to thank you as it was partly your request that encouraged me to make this. Thanks for all the times you tried my new stuff on s7
jrkruse said:
People need to thank you as it was partly your request that encouraged me to make this. Thanks for all the times you tried my new stuff on s7
Click to expand...
Click to collapse
Yeah, that s7 edge stuff was fun i'd have to say. Quite the trip start to finish. I figure S8+ cant be too far off from this phone. Hope you pop in with some cool stuff for this phone. I'm open to play with any of it.
jrkruse said:
Download N8 Firmware HERE
Download NOTE8_DEODEX_ROM_AGI5_V1.zip
Directions
You must be rooted
Extract AP file from the firmware zip and copy AP file to your phone internal storage
Copy NOTE8_DEODEX_ROM_AGI5_V1.zip to your phone
Open Flashfire and choose add zip and choose NOTE8_DEODEX_ROM_AGI5_V1.zip mount system when it ask
In Flashfire choose add firmware and choose AP file. Select system.img.ext4 and persit.img.ext4 DO NOT select boot and recovery images
Add wipe and move wipe to top of flash order
Make sure inject supersu IS NOT SELECTED
Flash order should be wipe; firmware; rom
Click Flash
Faetures
Fully Stock All Carriers
Deodexed
Rooted
Volte Icon Fixed
Click to expand...
Click to collapse
You should post a link in the base note 8 Development Forums
https://forum.xda-developers.com/galaxy-note-8/development
Thanks for working on this, I have been waiting for this to root
b3y0ndd34th said:
You should post a link in the base note 8 Development Forums
https://forum.xda-developers.com/galaxy-note-8/development
Thanks for working on this, I have been waiting for this to root
Click to expand...
Click to collapse
I'm not looking to maintain more threads If someone wants to post have at it
Missing all the fun while I get my Swappa business sorted out Can barely contain the excitement to try it out!
Thank you very much!! The best stuff in the phone world is right here on xda
?
Wow thanks @jrkruse
Has anyone tried this with AT&T? Main question is does the phone still make and receive calls if Enhanced LTE Services is enabled?
I need someones help: Can someone that istalled this rom and has the ability to follow directions and upload big files pm me
was able to get this to work on T-Mobile no fuss, running great. THANK YOU..
JustinCasehegone said:
was able to get this to work on T-Mobile no fuss, running great. THANK YOU..
Click to expand...
Click to collapse
Stupid question, for Tmo you used the AP file provided in the OP?
vazquezcmp said:
Stupid question, for Tmo you used the AP file provided in the OP?
Click to expand...
Click to collapse
All the carriers firmware are the same as far as ap bl and cp files and home csc files. Only difference is userdata images
vazquezcmp said:
Stupid question, for Tmo you used the AP file provided in the OP?
Click to expand...
Click to collapse
Yes, those exact steps.
One thing that was confusing was how to get "Wipe" to top, but once all files are selected you can re-arrange the ROM, Firmware, Wipe pretty easily.
@jrkruse Hey man what do you need?
Much appreciated kind Sir. jrkruse, glad to see you here.
I just had this thought... Since Samsung is basically on lockdown now.... I wonder what would happen if you install a custom ROM, in order to make the phone not care which android version or security version you currently have, and then tried to flash the downgraded stock rom that you wanted in the first place? Anyone ever tried this?
Sent from my [device_name] using XDA-Developers Legacy app
Try This
Pawprints1986 said:
I just had this thought... Since Samsung is basically on lockdown now.... I wonder what would happen if you install a custom ROM, in order to make the phone not care which android version or security version you currently have, and then tried to flash the downgraded stock rom that you wanted in the first place? Anyone ever tried this?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Hi there,
Well I have tried downgrade from firmware 6.0 to 5.0.2 and it did work so it might work for you
You can try and use this website as I Prefer this website than Sam mobile
The website is www.updato.com
Pawprints1986 said:
I just had this thought... Since Samsung is basically on lockdown now.... I wonder what would happen if you install a custom ROM, in order to make the phone not care which android version or security version you currently have, and then tried to flash the downgraded stock rom that you wanted in the first place? Anyone ever tried this?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
First of all, if the bootloader is locked, you can't flash a custom ROM, so that shoots that idea in the head.
Second, a custom ROM is basically only a system.img and kernel. Even if you were able to flash a custom ROM, your stock bootloader is still there. Flashing a custom ROM will not change whether or not you can downgrade the bootloader, the part of your device where bootloader is located is unaffected by any custom ROM or system.img.
Sent from my LGL84VL using Tapatalk
KIBS2173 said:
Hi there,
Well I have tried downgrade from firmware 6.0 to 5.0.2 and it did work so it might work for you
You can try and use this website as I Prefer this website than Sam mobile
The website is www.updato.com
Click to expand...
Click to collapse
What was your software versions before and after the downgrade? Im just curious if you were still on the first bootloader version and thats maybe why it worked?
Ive been doing a little reading on combination roms... but im not sure where a reliable source would be, or if i can make my own combining 2 different firmwares
Try This
Pawprints1986 said:
What was your software versions before and after the downgrade? Im just curious if you were still on the first bootloader version and thats maybe why it worked?
Ive been doing a little reading on combination roms... but im not sure where a reliable source would be, or if i can make my own combining 2 different firmwares
Click to expand...
Click to collapse
Hi there,
well I was using a Samsung A5000 which was the original version of the A5 series and it was the Chinese version of the phone, so therefore it had the HONGKONG VERSION on it in order to get Google PlayStore because playstore is banned in China. However, the HongKong Samsung service only updated the phone up to version 5.0.2 and China had the latest firmware update which was android 6.0
I was however able to update the phone from version 5.0.2 to 6.0 using ODIN
and the phone rebooted with new boot loader, recovery, and even it has a new downloader.
The phone was working alright but it didn't had any playstore.
I tried numerous ways to install playstore which resulted the phone to lag and heat up for some reason
So I had to downgrade it from 6.0 to 5.0.2 and I used ODIN again.
And it was flashed successfully.
And no when I flashed it from 5.0.2 to 6.0 it had the new boot loader and I didn't have to unlock the boot loader at all.
And I think by 2017 THE SAMSUNG KNOX service was discontinued so i don't see a reason why there would not to downgrade your phone.
Combining two roms with different coding can brick your phone. As most custom roms are built by building over the existing rom.
So by concluding you can try to downgrade the firmware or you can change the firmware to another region or you can wait till samsung to release another software update which might fix your problem or just re-install the whole OS with the same version as there might be a missing file when it was updated to that version
KIBS2173 said:
Hi there,
well I was using a Samsung A5000 which was the original version of the A5 series and it was the Chinese version of the phone, so therefore it had the HONGKONG VERSION on it in order to get Google PlayStore because playstore is banned in China. However, the HongKong Samsung service only updated the phone up to version 5.0.2 and China had the latest firmware update which was android 6.0
I was however able to update the phone from version 5.0.2 to 6.0 using ODIN
and the phone rebooted with new boot loader, recovery, and even it has a new downloader.
The phone was working alright but it didn't had any playstore.
I tried numerous ways to install playstore which resulted the phone to lag and heat up for some reason
So I had to downgrade it from 6.0 to 5.0.2 and I used ODIN again.
And it was flashed successfully.
And no when I flashed it from 5.0.2 to 6.0 it had the new boot loader and I didn't have to unlock the boot loader at all.
And I think by 2017 THE SAMSUNG KNOX service was discontinued so i don't see a reason why there would not to downgrade your phone.
Combining two roms with different coding can brick your phone. As most custom roms are built by building over the existing rom.
So by concluding you can try to downgrade the firmware or you can change the firmware to another region or you can wait till samsung to release another software update which might fix your problem or just re-install the whole OS with the same version as there might be a missing file when it was updated to that version
Click to expand...
Click to collapse
Combining 2 firmwares that were made for the exact same model number, does not cause a brick unless it wasn't done correctly. For example, a 5.0 firmware can be mixed and matched with a 6.0 firmware if they are for the same device.
Sent from my LGL84VL using Tapatalk
Try this
Droidriven said:
Combining 2 firmwares that were made for the exact same model number, does not cause a brick unless it wasn't done correctly. For example, a 5.0 firmware can be mixed and matched with a 6.0 firmware if they are for the same device.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Hi there,
Well I have tried to combine 2 firmwares together which ended up bricking one of my android devices. since it was a mediatek device I just gave up on the SPFLASH TOOL as it just gave out error codes. However if you have tried it and became successful well think i have done something wrong
BUT I THINK IT WILL BE ALRIGHT FOR YOU TO DOWNGRADE THE DEVICE
KIBS2173 said:
Hi there,
Well I have tried to combine 2 firmwares together which ended up bricking one of my android devices. since it was a mediatek device I just gave up on the SPFLASH TOOL as it just gave out error codes. However if you have tried it and became successful well think i have done something wrong
BUT I THINK IT WILL BE ALRIGHT FOR YOU TO DOWNGRADE THE DEVICE
Click to expand...
Click to collapse
Were the two firmwares that you tried to combine for the exact same model number device? Or were they for a different device? That makes a difference.
What I described is basically the same as porting a Samsung firmware from a US variant of a device to work on an international model of the same device(i.e. port stock lollipop for a US variant of Samsung Galaxy S6 to work on an international variant of Samsung Galaxy S6). It's a common procedure.
Sent from my LGL84VL using Tapatalk
TRY THIS
Droidriven said:
Were the two firmwares that you tried to combine for the exact same model number device? Or were they for a different device? That makes a difference.
What I described is basically the same as porting a Samsung firmware from a US variant of a device to work on an international model of the same device(i.e. port stock lollipop for a US variant of Samsung Galaxy S6 to work on an international variant of Samsung Galaxy S6). It's a common procedure.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Hi there,
Yeah they were for the exact phone and model. For some reason SpFlash Tool bricks Mediatek Devices. I think someone should create another version of spflash tool just like ODIN. Odin is actually a great software to flash all Samsung devices I Had no problems with it.
But Spflash tools are still in Beta mode. The software is not reliable.
I had to get a new motherboard for my device because of the hard brick however my pc is still able to detect the device but it won't install the firmware. Keeps on giving me error 4032 something like that.
Droidriven said:
Combining 2 firmwares that were made for the exact same model number, does not cause a brick unless it wasn't done correctly. For example, a 5.0 firmware can be mixed and matched with a 6.0 firmware if they are for the same device.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Can you lead me to anywhere explaining how to do this in detail?
I'm still researching. I saw somewhere that Oreo had a not as strict security downgrade and there was possibility that upgrading to Oreo and then downgrading to marshmallow might work.... But I tried to no avail. So there goes that theory...
I wasn't concerned about the upgrading as nougat and Oreo are basically the same, I'm not really losing or gaining by varying between those 2.
Still would love to have the best of both worlds though... Appearance of lollipop/marshmallow in all areas but with version either 7 or 8. The leaks of samsungs spin on 9 look a little promising.... A little.
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
Can you lead me to anywhere explaining how to do this in detail?
I'm still researching. I saw somewhere that Oreo had a not as strict security downgrade and there was possibility that upgrading to Oreo and then downgrading to marshmallow might work.... But I tried to no avail. So there goes that theory...
I wasn't concerned about the upgrading as nougat and Oreo are basically the same, I'm not really losing or gaining by varying between those 2.
Still would love to have the best of both worlds though... Appearance of lollipop/marshmallow in all areas but with version either 7 or 8. The leaks of samsungs spin on 9 look a little promising.... A little.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Here is a guide to extract the two firmware files.
Extract one firmware in a folder of its own and extract the other in its own folder.
https://www.rwilco12.com/forum/showthread.php?tid=74
You basically only need to switch the system.img from the older firmware, in other words, remove the system.img from the firmware that won't allow downgrading, then, extract the system.img from the older firmware that you want to downgrade to, then put the older system.img into the firmware that won't allow downgrading. Then repackage the file into an Odin flashable .tar.md5 following this guide.
https://forum.xda-developers.com/showthread.php?t=2446269
Or this guide
https://www.rwilco12.com/forum/showthread.php?tid=92
***NOTE***
Some things may have changed since those guides were written. You might need to switch more than just the system.img files from the two firmware files. Do some researching and reading to find out and understand exactly which parts you need to swap around in order for the finished file to flash correctly.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Here is a guide to extract the two firmware files.
Extract one firmware in a folder of its own and extract the other in its own folder.
https://www.rwilco12.com/forum/showthread.php?tid=74
You basically only need to switch the system.img from the older firmware, in other words, remove the system.img from the firmware that won't allow downgrading, then, extract the system.img from the older firmware that you want to downgrade to, then put the older system.img into the firmware that won't allow downgrading. Then repackage the file into an Odin flashable .tar.md5 following this guide.
https://forum.xda-developers.com/showthread.php?t=2446269
Or this guide
https://www.rwilco12.com/forum/showthread.php?tid=92
***NOTE***
Some things may have changed since those guides were written. You might need to switch more than just the system.img files from the two firmware files. Do some researching and reading to find out and understand exactly which parts you need to swap around in order for the finished file to flash correctly.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks! My brain is kinda pooped for tonight, but I will definitely dig into these tomorrow night
I had read a bit about removing the sboot.bin file from the firmware i want to use, but it feels risky to remove it entirely. I like the idea of using it but allowing that other system image to flash, much like youve described! it sounds safer than just leaving components out completely
Pawprints1986 said:
Thanks! My brain is kinda pooped for tonight, but I will definitely dig into these tomorrow night
I had read a bit about removing the sboot.bin file from the firmware i want to use, but it feels risky to remove it entirely. I like the idea of using it but allowing that other system image to flash, much like youve described! it sounds safer than just leaving components out completely
Click to expand...
Click to collapse
Also, do some Google searches for:
"How to port Samsung stock firmware"
Or similarly worded searches to understand what is involved when modifying Samsung stock firmware.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Also, do some Google searches for:
"How to port Samsung stock firmware"
Or similarly worded searches to understand what is involved when modifying Samsung stock firmware.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
So, if I try this, and it doesn't work.... Is the worst case still that I may need to reflash twrp and the official firmware that does work? I had that happen when just regularly trying to flash the marshmallow official firmware, I think it's called "soft brick" cuz it wiped the nougat/oreo but couldn't install anything in its place, but I found my way out of it with no issues. And since I have no personal things on there yet I wasn't worried about wiping and losing anything. I have a twrp backup I also made of nougat after rooting but before messing with anything, so I've got that to fall back on too.
Still reading but just wanted to be sure, that the worst case is just needing to reflash proper working firmware/recovery if needed.
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
So, if I try this, and it doesn't work.... Is the worst case still that I may need to reflash twrp and the official firmware that does work? I had that happen when just regularly trying to flash the marshmallow official firmware, I think it's called "soft brick" cuz it wiped the nougat/oreo but couldn't install anything in its place, but I found my way out of it with no issues. And since I have no personal things on there yet I wasn't worried about wiping and losing anything. I have a twrp backup I also made of nougat after rooting but before messing with anything, so I've got that to fall back on too.
Still reading but just wanted to be sure, that the worst case is just needing to reflash proper working firmware/recovery if needed.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
As long as the two firmware are for the same device and as long as you read carefully about what you're doing and you don't do something completely wrong, the worst you should expect is a soft brick or a bootloop, in which case, you'd flash the original stock firmware or you'd flash TWRP then restore the nandroid backup that you created from stock nougat.
Sent from my LGL84VL using Tapatalk
Droidriven said:
As long as the two firmware are for the same device and as long as you read carefully about what you're doing and you don't do something completely wrong, the worst you should expect is a soft brick or a bootloop, in which case, you'd flash the original stock firmware or you'd flash TWRP then restore the nandroid backup that you created from stock nougat.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
New little snag. Oreo uses lz4 compression while Marshmallow uses regular .img disk image compression. I wonder if I'm better off converting the marshmallow one to lz4 or converting the other Oreo files I'll be using into regular img files. Hmm.
I did start to Google that and people have converted the Oreo files to img before Odin could read the lz4 ones. But I wonder if the other way around could work too. Or, do they even need to be the same? Hmm.... Will need to do a bit more reading than expected
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
New little snag. Oreo uses lz4 compression while Marshmallow uses regular .img disk image compression. I wonder if I'm better off converting the marshmallow one to lz4 or converting the other Oreo files I'll be using into regular img files. Hmm.
I did start to Google that and people have converted the Oreo files to img before Odin could read the lz4 ones. But I wonder if the other way around could work too. Or, do they even need to be the same? Hmm.... Will need to do a bit more reading than expected
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Exactly, this isn't the kind of thing that has a clear cut, everything you want to know guide. It's the kind of thing you'll have to figure out and piece together from different sources.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Exactly, this isn't the kind of thing that has a clear cut, everything you want to know guide. It's the kind of thing you'll have to figure out and piece together from different sources.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Okay, so upon some more research, and finding a couple of tools here on xda, heres what ive been able to do.
Before I did anything I made copies of both roms in a separate new folder, so that I wasnt modifying my original downloads.
I decided that since I had read about people doing this successfully before Odin could read lz4 compression, here on xda I found a tool and removed that compression. Since marshmallow uses img but oreo uses bin files, I then found another thread that states that you can simply rename the file with extensions visible to convert them from .bin to a regular .img, like marshmallow uses. I did this for all the oreo files, replacing only the system.img with the marshmallow one, removing the oreo one to another folder for now. (The only thing im still debating is if i should have gone the other way, and renamed the marshmallow system.img into a .bin file instead. If I try and it fails, that may be my next attempt.) I was then able to use another tool I found here on xda to take the new tar files I made and replace the .md5 extension and recompressed my new editions. There were a few folders within these tar files originally (Meta data was one) that I simply left alone but included in the same tar file that they were in before.
The only thing ive yet to do is actually try to flash them. But, if Ive read everything properly, they are ready to flash. Im only nervous to find out if the absolute worst case if it doesnt work is it will give me some kind of error. the only one i didnt bother with was home_CSC since that 1 is only for restoring with your files present, and im looking to start from scratch, so ill keep those removed from the mix.
so basically the only thing i changed was bin files to img files, and removed the oreo system.img and put the marshmallow system.img in its place. Im wondering now if i should go back and change those files back to .bin extensions. Then that way nothing crutial can screw up? hmm.... but im *almost* there.
ETA: So I just decided to go through everything once more, and decided to keep certain files as bin files like original, and the other files as img, as they were originally within the oreo rom. I was mistakenly thinking that all files had to be either img or bin, but upon another check through i did notice that the file type within the same rom can vary. I feel better about that now Still just working on the courage to flash it. I didnt truly edit any of the files. I only either renamed the extension thereby converting types of files. otherwise i only decompressed and then recompressed things. I didnt do any true open notepad and edit type stuff. Just sticking with the basics here
Pawprints1986 said:
Okay, so upon some more research, and finding a couple of tools here on xda, heres what ive been able to do.
Before I did anything I made copies of both roms in a separate new folder, so that I wasnt modifying my original downloads.
I decided that since I had read about people doing this successfully before Odin could read lz4 compression, here on xda I found a tool and removed that compression. Since marshmallow uses img but oreo uses bin files, I then found another thread that states that you can simply rename the file with extensions visible to convert them from .bin to a regular .img, like marshmallow uses. I did this for all the oreo files, replacing only the system.img with the marshmallow one, removing the oreo one to another folder for now. (The only thing im still debating is if i should have gone the other way, and renamed the marshmallow system.img into a .bin file instead. If I try and it fails, that may be my next attempt.) I was then able to use another tool I found here on xda to take the new tar files I made and replace the .md5 extension and recompressed my new editions. There were a few folders within these tar files originally (Meta data was one) that I simply left alone but included in the same tar file that they were in before.
The only thing ive yet to do is actually try to flash them. But, if Ive read everything properly, they are ready to flash. Im only nervous to find out if the absolute worst case if it doesnt work is it will give me some kind of error. the only one i didnt bother with was home_CSC since that 1 is only for restoring with your files present, and im looking to start from scratch, so ill keep those removed from the mix.
so basically the only thing i changed was bin files to img files, and removed the oreo system.img and put the marshmallow system.img in its place. Im wondering now if i should go back and change those files back to .bin extensions. Then that way nothing crutial can screw up? hmm.... but im *almost* there
Click to expand...
Click to collapse
I'm not sure about changing back to bin files or not. You could always make a copy that is not converted and a copy that is converted.
I can't say that I'm 100% certain about this, but..
As long as you are working with stock files and followed instructions, you shouldn't cause any real permanent damage but you might get errors of some kind, those might be correctable. You might cause a soft brick or have to restore the device by some complex processes but it should be restorable, sometimes its tough to restore but can be done.
I would look for information about whether the question about bin vs img is a valid question and what potential problems it can cause.
Sent from my LGL84VL using Tapatalk
Droidriven said:
I'm not sure about changing back to bin files or not. You could always make a copy that is not converted and a copy that is converted.
I can't say that I'm 100% certain about this, but..
As long as you are working with stock files and followed instructions, you shouldn't cause any real permanent damage but you might get errors of some kind, those might be correctable. You might cause a soft brick or have to restore the device by some complex processes but it should be restorable, sometimes its tough to restore but can be done.
I would look for information about whether the question about bin vs img is a valid question and what potential problems it can cause.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
This is becoming so beyond frustrating... I went though tonight, deleted my previously modified files... I wanted to go through and only undo the lz4, without all that renaming I had done. Did that just fine.
Gather up the guts to finally try it in odin though? Well, i dont even know what the error is. In odin 3.13, it gets to "file analysis" and just sits there. I unplugged and was still even able to restart the device back in to the oreo that was still on it, it did nothing at all. So i did a little bit of searching and it seems that an older version of odin fixes this. So i downloaded the recommended 3.09... Odin gets to the same point and then the program straight up shuts down! Ive even tried compatibility mode for windows 7 thinking maybe. I had ran it as administrator each time.
so the phone is fine.... but i cant get the program to even try it let alone give me any kind of error to work with....
ive given up for tonight!
The other idea i had was to check "phone bootloader update" in odin and just try to flash the straight up marshmallow rom, but googling that gets mixed results.