Little over a month ago (I am traveling currently in Quito Ecuador) I had my fanny pack with my Galaxy Note 2 (rooted, custom ROM) and my LG V400 tablet (rooted, deoxed, debloated and running ART rather than dalvic) stolen. Bought as a replacement a Galaxy Note 8 and an SM G530H. Had to have a phone and didn't do any research on the 530 H. BIG mistake.
Rooted the 530H installed the CWM recovery hack and started doing various things I do to an Android device I use daily. First BIG disappointment was in the dev community. No custom ROM's. Anywhere. Fine. In process of all of this I encrypted the phone- who would carry an unencrypted phone anyway, you are begging to be pwned if it goes bye bye. In process of all of this discovered that the CWM hack for the 530H won't deal with the /data partition when the phone is encrypted. That sucks hugely. Today we got news of the second fairly critical Android vulnerability revealed in the last three days (huh? really?) so I figured fine since this second one is with remote management crap code that is not secure (the first one with an SMS vulnerability) and potentially a MUCH more critical problem; since I have locked down as much as possible SMS with a stock rooted ROM...and since to hack remote management to try to kill this vuln-- (you can download the checkpoint scanner from playstore, I strongly recommend doing it and scanning your phone)-its going to take some pretty good surgery with Root Browser and I might break the OS. I figured it might be wise to do a full backup. Scanned the phone with the checkpoint scanner and sure enough its vulnerable. The internet and cell-landia in South America is like the wild west so it probably would be a wise idea to try to fix remote management vulnerability as much as possible. I already know the CWM hack WONT deal with encryption. TWRP on the Note 8 will. It asks for the password when entering recovery and does full painless backups and restores(My Note 8 isn't vulnerable because I am running a custom ROM on it without all the BS code).
So I come over here and find no prob a couple of TWRP threads for the G530. ITs a hack which is OK BUT 1) a number of the links are click bait sites (mods thanks for deleting one and the second in that thread that points to the nz site is click bait AND doesn't work) but finally found a link. Downloaded and flashed. Starts in recovery just fine except that 1) it will NOT mount the external SD card and 2) it reports the /data partition as 0 b. Meaning (like CWM) it can't deal with an encrypted partition. So what good is it?
Its a shame because for a mid priced phone the 530H really is a pretty capable hw platform, quick and stable, not bad for the $$. The follow on in the dev community is sad-. No ROMS. No recoveries using the phone encrypted. Were I not traveling I would try to port CM 12.1 to run on the 530 platform ( I wrote my first code in 1968 when I was 17) but I am not going to attempt it on a laptop and with other things I am involved in at this point no way.
So if you are thinking about the Grand Prime if you can be satisfied with a stock ROM, unencrypted, and don't mind getting your hands dirty then its not bad. However there are a lot better platforms out there as far as after market dev participants custom ROM's and simple things like recoveries that work as advertised. Be advised. Sorry I bought it. That would change in a big way if there was a stable ROM that got rid of all the s*it code that is in stock Android AND at LEAST a recovery that did what it was supposed to do. Lots of people here try to help posting links but before doing so understand please how the original program (TWRP) actually works on other platforms with all the bells and whistles and try to verify that the hack you link to actually performs like the original.
Related
Hi everyone,
I got a live demo unit Galaxy S5 (g900x) from work, and I've never used a Samsung for rooting / flashing purpose before. I was wondering if I could in fact flash a stock rom, and root the device, in order to use it as a full multimedia device ?
Thanks
If Samsung continued the demo unit path as per the Galaxy S4 then the S5 demo units will be missing important hardware components, a physical connection between the Sim port and the system board being one of them. It was impossible to use an S4 demo unit as a phone for example. It was also impossible to flash a standard stock rom without the device refusing to boot, the partition table was also different.
Of course, this all might not be the case with the S5 demo units and they might simply be stock units with a modified firmware. But, if not, you have little more than a small tablet on your hands.
Thank you for your answer, I knew I couldn't use as a phone, but at least I wanted it as, like you said, a small tablet. The problem is the retail mode app that keeps launching itself and wiping the device, even if I disabled it. That's why I was hoping to flash a stock rom or at least root the device.
dhunzi10 said:
Thank you for your answer, I knew I couldn't use as a phone, but at least I wanted it as, like you said, a small tablet. The problem is the retail mode app that keeps launching itself and wiping the device, even if I disabled it. That's why I was hoping to flash a stock rom or at least root the device.
Click to expand...
Click to collapse
Definitely sounds like a similar situation to the S4 demo units, I remember they would wipe anything on the data partition on every boot. I'm not sure if the issue was ever overcome.
Check out the following post, not sure if it could be applied to the S5 model.
http://forum.xda-developers.com/showpost.php?p=50393029&postcount=7
dhunzi10 said:
Thank you for your answer, I knew I couldn't use as a phone, but at least I wanted it as, like you said, a small tablet. The problem is the retail mode app that keeps launching itself and wiping the device, even if I disabled it. That's why I was hoping to flash a stock rom or at least root the device.
Click to expand...
Click to collapse
Do not flash a stock rom on it because most probabably you will end up in bootlooping
Try this (PLEASE BACKUP EVERYTHING BEFORE FLASHING)
-root it with CF auto root
-make a nandroid backup (THIS IS ESSENTIAL) of everything
-maintain pit, modem and bootloader files from the demo rom (from your backup) and pick other parts from a stock rom (european open rom will do)
-flash all parts with odin
-now you should have a full working mini tablet without gsm and gps signal
This method is similar to the one used on Galaxy Note 3 and i think it will work, just do the backup before for safety and i'm nor responsible from any damaged caused
Let me know
Are you sure I can root it ? It is SM-G900X, which is not on the list on chainfire's website.
Hello,
as thread title says, I need some advice from professionals here for my new Galaxy S5.
Well it's not quite new (almost 1 year) but never rooted it or flashed it, so I still got OS (original system) by Samsung.
I am a pretty amateur on such stuff. First I need some advice what to do: Rec & Root or flash custom rom?
Followng things are important to me:
The System has to be stable and fast: no lags, no crashes, no errors (I do not expect 100% stability, since not even OS is 100% stable, but it has to be at least stable as OS or even a bit more)
I need features and nice widgets (Rom must also be afordable to other apps and widgets, I 'd prefer Samsung OS widget)
I need good quality on camera (preferred OS cam software and features)
Good signal and GPS (Good and fast GPS is a MUST!!, as I use often Navigon when I travel with my car)
Good video player and galery app (Preferred Samsung OS Galery App, but video player can also be different than Samsung OS Video Player if its working fine)
What I do not do with my phone:
I do not play games
I do not read e-books
I don't understand the purpose of KNOX! Do I need it really?
Here are some details of my Smartphone:
Model no: SM-G900F
Android version: 5.0
Modem version: G900FXXU1POJ1
Kernel version: 3.4.0-6364590
Build number: LRX21T.G900FXXU1POK5
Securitysoftware version: MDF v1.1 release 4 / VPN v1.4 Release 3
I would be greatful if someone could give an advice if it is worth to flash a custom rom and if yes what rom based in what moden and kernel versions or if a simple root with recovery install is enough?.
Thanks in advance
Regards
Hi @GordonSpace.......
Most of what you said in your post leads me to believe that there are many things about the stock OS that you are happy with. That being the case, the old adage 'if it ain't broke, don't fix it' comes to mind.....meaning (for now) you might as well stay with stock. If you start flashing CM custom roms (for example) you will lose that look and feel.
On to your question about Knox.....
In a nutshell, knox is based around an 'eFuse' which will trip or blow as soon as you modify your device. This eFuse CANNOT be reset. Samsung are, in some cases, denying warranty repairs on devices where knox has been tripped.
So basically, as soon as you flash CF Root or TWRP to gain root, your warranty is void (Samsung normally provide a 2 year warranty on their devices). Tripping knox will also prevent future 'over the air' updates. So even if you unrooted your device you would be stuck with the version of the OS that you have on your device. Finally, tripping knox will prevent your device from connecting to 'business enterprise secure' servers. So if you currently use your phone on your employers network, this will no longer be possible.
If you still want to go ahead and forget about knox, this is the easiest way to gain root......
Follow exactly....
1) deactivate 'Reactivation Lock' (can be found under Security in Settings).
2) copy SuperSU zip to your device.
3) boot into download mode.
4) Odin flash TWRP 2.8.7.0 (specifically this version).
5) DO NOT allow phone to boot, (uncheck auto reboot in odin and if necessary remove the battery as soon as the TWRP flash has completed) then.....
6) boot directly into recovery. (Vol +, Power & Home button combination)
7) flash SuperSU zip.
8) boot device as normal.
TWRP 2.8.7.0 by Dees_Troy
http://forum.xda-developers.com/showthread.php?t=2727406
superSU zip v2.46 by Chainfire
http://forum.xda-developers.com/showthread.php?t=1538053
When you have root access, you can get Titanium Backup from the playstore and freeze/delete the 'bloatware' that comes pre - installed on Samsung firmwares.
That will then give you the stability of the software designed for the phone coupled with the look and feel that you like, but without the resource hogging rubbish that most people with unrooted phones have to put up with......
http://i.imgur.com/rVnFwJM.jpg
thanks
keithross39 said:
Hi @GordonSpace.......
Most of what you said in your post leads me to believe that there are many things about the stock OS that you are happy with. That being the case, the old adage 'if it ain't broke, don't fix it' comes to mind.....meaning (for now) you might as well stay with stock. If you start flashing CM custom roms (for example) you will lose that look and feel.
On to your question about Knox.....
In a nutshell, knox is based around an 'eFuse' which will trip or blow as soon as you modify your device. This eFuse CANNOT be reset. Samsung are, in some cases, denying warranty repairs on devices where knox has been tripped.
So basically, as soon as you flash CF Root or TWRP to gain root, your warranty is void (Samsung normally provide a 2 year warranty on their devices). Tripping knox will also prevent future 'over the air' updates. So even if you unrooted your device you would be stuck with the version of the OS that you have on your device. Finally, tripping knox will prevent your device from connecting to 'business enterprise secure' servers. So if you currently use your phone on your employers network, this will no longer be possible.
If you still want to go ahead and forget about knox, this is the easiest way to gain root......
Follow exactly....
1) deactivate 'Reactivation Lock' (can be found under Security in Settings).
2) copy SuperSU zip to your device.
3) boot into download mode.
4) Odin flash TWRP 2.8.7.0 (specifically this version).
5) DO NOT allow phone to boot, (uncheck auto reboot in odin and if necessary remove the battery as soon as the TWRP flash has completed) then.....
6) boot directly into recovery. (Vol +, Power & Home button combination)
7) flash SuperSU zip.
8) boot device as normal.
TWRP 2.8.7.0 by Dees_Troy
http://forum.xda-developers.com/showthread.php?t=2727406
superSU zip v2.46 by Chainfire
http://forum.xda-developers.com/showthread.php?t=1538053
When you have root access, you can get Titanium Backup from the playstore and freeze/delete the 'bloatware' that comes pre - installed on Samsung firmwares.
That will then give you the stability of the software designed for the phone coupled with the look and feel that you like, but without the resource hogging rubbish that most people with unrooted phones have to put up with......
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Hello keithross and thank you for your response.
I use my smartphone only in private.
However it still has 11 months warranty by Samsung. Another Idea I had was to sell my Galaxy S5 as it is (OS and Knox) and buy another smartphone.
However what would be your recommendation for a new smartphone?
I was thinking about LG or HTC. But I'm not sure about to purchase a "famous" brand device or just a cheap one like Mobistel, Huawai and such.
What is a nice smartphone to have it root / flashed?
Regards
Kiri
I have about 9 months of warranty left on my phone....but I was able to root without tripping knox.....simply because I rooted before I allowed my phone to update to Lollipop (I rooted with Towelroot while running KitKat) then debloated, and customised the stock firmware.....so I have my phone as I want it, and still have knox intact.
The S5 will probably be my final Samsung smartphone, but as of this moment, I haven't given much thought as to what I'll replace it with. I'm half tempted to keep it beyond the end of it's warranty and start trying out custom roms at that point. It does everything I want it to do, so why would I need to replace it?
On the other hand, if i did replace it, I'd probably stay with one of the well known brand names.....The chances are that they'll have more dev support than the less popular makes of device....but I won't waste my money on any more flagship devices, I'll probably look at the 'upper midrange' devices as they'll (by that time) probably have similar specs to my current device (the way technology is currently advancing, they may even be superior to the S5)......
http://i.imgur.com/rVnFwJM.jpg
CyanogenMod
I decided to flash cyanogenmod snapshot
1. However I do not understand the difference between klte and kltedv rom (kltedv = vodafone. does that mean my provider has to be vodafone?)
2. TWRP or Cyanogen Recovery?
3. Do I need to install a diff Kernel version?
4. Anything I should take care about before I flash? (something special about Samsung drivers, kernel, odin etc...?)
Thx for your support.
1....In all honesty I can't answer having never flashed custom to my S5.
2....TWRP recovery over Cyanogen recovery....Every time. Cyanogen recovery is little better (if at all) than stock recovery.
3....flashing a different kernel isn't strictly speaking necessary....unless you want to be able to change processor clock speeds and voltage and apply various other specialist 'tweaks'.....
4....after rooting (but before flashing) make a backup of your EFS folder (critically important) it contains, amongst other things, your IMEI number. If this folder becomes corrupted, you're in a whole world of hurt....
Back up any personal data that you can't afford to lose....things like photos etc.
Make sure you have a copy of your current firmware available....If it all goes pear shaped, you'll possibly need it to recover your phone.
The version of Odin that has most compatibility with the S5 is v3.10.7 though other versions *should* work.
Get hold of and install the Samsung USB drivers on your pc....They come bundled with Kies available on Samsung's website. (If you install Kies, you will need to use task manager on your pc to kill the kies processes prior to flashing anything with Odin).
Use the usb cable that came with your phone when connecting it to your pc.
Make sure you've disabled your firewall and antivirus before attempting to use Odin.
If you need any more help just let me know by commenting below.....
Luck fella
http://i.imgur.com/rVnFwJM.jpg
Hey thanks mate. I rooted my device with CF autoroot via odin. I read that CM13 with Android 6 is as a stable version out now. Probably I am gonna flash it. However, I have a question with my current root of S5. Currently the wifi passwords are being save as an encrypted hex key in the wifi_supplicant.conf file. However I would like to use an app that saves and shows my wifi passwords, but unfortunately due to the encryption of S5 it's not a help for me. Any recommendations what can I do to save the real PW instead of the encrypted key?
Sorry fella....The tech aspects of your question have gone right over my head like an international Jumbo Jet....I have no idea what you're even asking about, let alone how to solve it for you. Your best bet would be to create a thread specifically for this question.....you will probably get more views for that thread than for this one.....sorry mate....
http://i.imgur.com/rVnFwJM.jpg
GordonSpace said:
Hey thanks mate. I rooted my device with CF autoroot via odin. I read that CM13 with Android 6 is as a stable version out now. Probably I am gonna flash it. However, I have a question with my current root of S5. Currently the wifi passwords are being save as an encrypted hex key in the wifi_supplicant.conf file. However I would like to use an app that saves and shows my wifi passwords, but unfortunately due to the encryption of S5 it's not a help for me. Any recommendations what can I do to save the real PW instead of the encrypted key?
Click to expand...
Click to collapse
You should already know the passwords if they are your routers/APs
I don't know my passwords. The thing is, that sometimes we go to some cafés and such where I have saved the PW of the router, but sitting with friends some of them do not have it to connect with wifi. Thats why I am asking if there is a possibility to view the passwords I saved in my wifi connections (not as a hex key but the true passwords). Anyway.. thx for help. I guess thats Samsung OS. Hope it won't be with CM13 like this.
My wife's camera stopped working on her phone. I read flashing back to a previous firmware might fix the issue. I thought it was worth a try (and easier) before physically cracking the phone open and examining the hardware. But boy was I sure wrong about that!
I've read so much crap about this within the past few hours my head could explode. But I think the problem is trying to source the correct firmware.
This is a SM-G935V with a snapdragon processor in it according to spec websites.
The baseband version is: G935VVRSBCTC1
I haven't figured out how to find the current PDA version on the phone yet, but when I was trying to flash it with random firmware with Odin, the phone screen gave me error message: Fused 11 > Binary 4
From what I read, I understand that to mean I'm trying to flash binary 4 over 11 and that won't work. The flash only works if the number is greater....or I'm hoping maybe it will work if the number is the same. I would be happy just to flash Android 8.0 at this point in any form just to see if the camera starts working again. I've already tried a factory reset, clearing camera app data and cache, booting into safe mode, and resetting phone settings to fix the camera - nothing worked.
Could anybody please help me figure out my current PDA version on the phone? Or help me source the correct firmware? I'm starting to think it might be easier just to root the phone and install that ONE UI with android 9 or the Lineage OS with Android 10. But I've never rooted a phone before, this is my first attempt at any of this and to be honest this phone is not giving me the confidence I need to attempt the root and new OS. I can't even get the current firmware to reinstall.
Any help would be very appreciated. Like I said, I've stayed up all night and I'm so freaking tired at this point. But I feel like I'm soooooo close.
I have an SD card with Magisk, no-verity-opt-encrypt, and twrp ready to go. I have Odin ready and installed Samsung USB. Do you guys think I should just try another firmware and root the phone? Any links to firmware that don't take 12 hours to download would be appreciated.
UPDATE!
I found the PDA version with that handy "Phone Info *Samsung*" app in the play store.
The PDA version is G935VVRSBCTC1 5TH DIGIT FROM THE RIGHT GIVES US THE FUSED BINARY "B". I guess when they got past the number 9 the switched to Alpha characters. I found some "A" firmwares on Updato.com. But I didn't see any with a "B". So there's a good chance the one's I'm trying to download over 12 hours right now won't work.
I also scrolled over to the "Hardware" section in the phone and it asked for access to the Camera. I gave it access. But now the field is blank/empty. I didn't populate any info on the Camera. I don't know if that means anything just wanted to point that out. Could still be firmware or hardware as far as I know.
Thanks, Derek
MajinMight said:
My wife's camera stopped working on her phone. I read flashing back to a previous firmware might fix the issue. I thought it was worth a try (and easier) before physically cracking the phone open and examining the hardware. But boy was I sure wrong about that!
I've read so much crap about this within the past few hours my head could explode. But I think the problem is trying to source the correct firmware.
This is a SM-G935V with a snapdragon processor in it according to spec websites.
The baseband version is: G935VVRSBCTC1
I haven't figured out how to find the current PDA version on the phone yet, but when I was trying to flash it with random firmware with Odin, the phone screen gave me error message: Fused 11 > Binary 4
From what I read, I understand that to mean I'm trying to flash binary 4 over 11 and that won't work. The flash only works if the number is greater....or I'm hoping maybe it will work if the number is the same. I would be happy just to flash Android 8.0 at this point in any form just to see if the camera starts working again. I've already tried a factory reset, clearing camera app data and cache, booting into safe mode, and resetting phone settings to fix the camera - nothing worked.
Could anybody please help me figure out my current PDA version on the phone? Or help me source the correct firmware? I'm starting to think it might be easier just to root the phone and install that ONE UI with android 9 or the Lineage OS with Android 10. But I've never rooted a phone before, this is my first attempt at any of this and to be honest this phone is not giving me the confidence I need to attempt the root and new OS. I can't even get the current firmware to reinstall.
Any help would be very appreciated. Like I said, I've stayed up all night and I'm so freaking tired at this point. But I feel like I'm soooooo close.
I have an SD card with Magisk, no-verity-opt-encrypt, and twrp ready to go. I have Odin ready and installed Samsung USB. Do you guys think I should just try another firmware and root the phone? Any links to firmware that don't take 12 hours to download would be appreciated.
Click to expand...
Click to collapse
UPDATE #2
As you can tell I haven't given up yet. I found my current firmware version for download on a different website:
https://samfrew.com/download/Galaxy__S7__edge__/b3kj/VZW/G935VVRSBCTC1/G935VVZWBCTC1/"]https://samfrew.com/download/Galaxy__S7__edge__/b3kj/VZW/G935VVRSBCTC1/G935VVZWBCTC1/
It's another slow download option which really sucks. But I'll be able to test If I can flash the same firmware to the phone (not technically a downgrade and carries the same fused binary). So we shall see. If this doesn't work I'll be looking into the other android 9 or 10 roms and rooting the phone.
Thanks, Derek
MajinMight said:
I found the PDA version with that handy "Phone Info *Samsung*" app in the play store.
The PDA version is G935VVRSBCTC1 5TH DIGIT FROM THE RIGHT GIVES US THE FUSED BINARY "B". I guess when they got past the number 9 the switched to Alpha characters. I found some "A" firmwares on Updato.com. But I didn't see any with a "B". So there's a good chance the one's I'm trying to download over 12 hours right now won't work.
I also scrolled over to the "Hardware" section in the phone and it asked for access to the Camera. I gave it access. But now the field is blank/empty. I didn't populate any info on the Camera. I don't know if that means anything just wanted to point that out. Could still be firmware or hardware as far as I know.
Thanks, Derek
Click to expand...
Click to collapse
TL/DR your full posts but I will cut to the chase on some points. If your phone is SM-G935V (US-Verizon) then you:
1) can NOT root binary B firmware. Binary A (10) yes, B (11) no, at least not until the ENG file becomes available- IF it ever comes. Official S7 support is next to dead.
2) even if you were lucky flashing binary A firmware and successfully rooted, you still would NOT be able to flash ANY custom ROM's such as Lineage. Also, Magisk is useless and will not work on our phones either.
US-spec Snapdragon phones are bootloader locked. There is no workaround. Locked bootloaders prevent flashing custom ROM's, kernels, etc. We are lucky we have root access and it took years just to get that. Bootloader unlocking will never happen for US-spec S7. Much as I love my S7e, if I ever have to replace it I will never get another US "Crapdragon" that you can't do anything with.
I do not know what the issue is with your camera. Maybe other forum members will have ideas. I do wish you luck getting everything back to normal.
Dang! Well thanks for the info! I guess all the videos I've seen with S7's and custom roms have not been done on the US-Verizon phone. What a bummer. Well this was a major learning experience at least.
My only idea now is to crack her open and make sure the camera didn't come unplugged from a drop. I also seen camera replacements were really cheap online. I don't know if it's worth my time....we are due for a phone upgrade anyway.
SkylineDriver said:
TL/DR your full posts but I will cut to the chase on some points. If your phone is SM-G935V (US-Verizon) then you:
1) can NOT root binary B firmware. Binary A (10) yes, B (11) no, at least not until the ENG file becomes available- IF it ever comes. Official S7 support is next to dead.
2) even if you were lucky flashing binary A firmware and successfully rooted, you still would NOT be able to flash ANY custom ROM's such as Lineage. Also, Magisk is useless and will not work on our phones either.
US-spec Snapdragon phones are bootloader locked. There is no workaround. Locked bootloaders prevent flashing custom ROM's, kernels, etc. We are lucky we have root access and it took years just to get that. Bootloader unlocking will never happen for US-spec S7. Much as I love my S7e, if I ever have to replace it I will never get another US "Crapdragon" that you can't do anything with.
I do not know what the issue is with your camera. Maybe other forum members will have ideas. I do wish you luck getting everything back to normal.
Click to expand...
Click to collapse
my first g6 had a broken screen last week. me being abusive to it. from frustration.
bought a used g6 as a backup very quickly but im not liking v9.0
id like to install the first 7.0 version it ever had available H870. I have 3 apps total installed more of a pro privacy advocate so no browser and would like to shut those annoying update popups which are extremely intrusive and come at the worst times. would like to block as much as possible to also have battery life
I dont understand what the roo does, what the bootloader does and I understand I need to flash a kdz rom. if I understand, I need to install 7.0 (not 7.1 or later) then use the root and bootloader to block updates notifications and to remove default apps in the phone.. basically tweak system things...is this correct?
I used to tinker with windows mobile back in the days but after years of fear of bricking and only have one phone, I had to suffer through annoyances in the OS they give. it is time to have a phone that doesnt annoy me and isnt intrusive. I really do need calmness after 18 months of hell with covid.
inevitably I will move to pinephone once it gets mature. for now using this g6. I dont run after the newest models.
any insight or experiences or tips you could throw at me would be appreciated as I think i may be mixing things up
stay afe
i have a used H870 here. Did the root+twrp, up to PIE and tryed/flashed many things, but wasn´t that happy at all. That was a few month ago. A week ago I replaced my battery and tada, sweet runner. So again I wanted more and bricked it to "no sim" after restoring from a kernel here. Since there isnt much for Pie, roms, deadlinks, broken twrp etc. the only tool which worked and helped me was LG bridge to restore to latest stock pie.
I would recommend u to root without recovery via magisk/fastboot method and go for some adaway, acc battery charger, lsposed + gravity, debloat and maybe a kernel manager + etc.
dont forget, when u have sporadic lags, go for the battery.
gl on ur way mate
----
ps just for info
the only working usb drivers where delivered via the LG bridge tool driver update for me, i tryed many..
Could someone please point me in the direction of a custom ROM that will (or even might) work on Samsung j7 sky pro SM-272VL(GP)
Before anyone suggests, I have already read all of the information out there on rooting, ODIN, TWRP, etc for this phone. It sounds like several have tried, but no one has actually been able to gain root, although there may be hope for that due to security flaw https://www.exploit-db.com/exploits/45379 mentioned in this post #21
SM-S727VL Analysis, Partition Table, and Factory
-- UPDATE #1 (11/05/18) added So I've got myself a Tracfone Variant of the Samsung J7, The "Galaxy J7 Sky Pro" [SM-S727VL] CDMA. As far as I can tell, this variant is sold on both the Tracfone and StraightTalk carriers, and it seems to just run...
forum.xda-developers.com
I have also read all of the only other thread out there on this device on the subject of rooting, or anything really:
SM-S727VL Root and Recovery
I cannot for the life of me get this phone rooted or a recovery installed. Odin always fails and ADB doesn't recognize the device. Does anyone have any info on rooting this device? I really just want to at least be able to update this thing to...
forum.xda-developers.com
However not much was accomplished in these peoples attempts other than a bricked phone or 2, and most of the participants seem to have moved onto other devices.
I however do not have any issue with needing to root as I own the device, and as it is I can boot into a recovery ODIN mode that says that FRP Lock is off, and the screen is showing a "download in progress" background to a console, waiting for me to send the updated firmware/custom ROM/whatever from the USB cable. See attached image.
I run Linux and have for the last 20 years have used too many Distros to count, but can work with most any, but prefer debian based although I have much respect for Gentoo, and their compile everything package management, and have spent considerable time on it as well. l have unlocked and installed custom ROM's of of many types on many phones, and am working with the combined experience of myself, and my friend who has done the same, except even more on more different devices than myself. But neither of us has worked on such an obscure model as this one with so little information posted publicly on the internet for anyone to find as this one. But if there is a way to do it, I'm sure between the two of us, we can and will make it happen.
Can anyone be of any help? I would really like to get something out of the phone for the $100 that it cost me. Things I would like to run would be Kali Nethunter, and/or Andrax or Cyanogenmod/LineageOS or really any other AOSP that is not google f***ed. Basically any custom ROM (whichever, whatever type and version has the best chance of working on this phone, since there are none posted publicly that are specifically made for this device that we can find for this obscure, excessively undocumented model of phone. Just getting TWRP will be a good start, and I'm pretty sure we can handle that. However in the mentioned posts even the the TWRP file that is made for this phone, people are having troubles installing in their experiences, and bricking their phones in the process, so I definitelly would prefer not to have a repeat of what happened there.
Thank you in advanced for any and all information, hints, tips, tricks, etc. I would like to not brick this phone as the only other person who attempted to do anything with this phone unfortunately had done.