So this happened:
http://forum.xda-developers.com/lg-g2/help/vs980-twrp-bootloop-botched-lollipop-t3072133
and once that was "fixed" i was able to use the phone, but it was acting funky. like dialing numbers was oddly laggy and while i can successfully call someone, it disconnects almost immediately and the cell network appears to be ... cycling itself for lack of a better term. i went looking at the various versions/info etc in About Phone and see the following
Baseband "Unknown"
Software Status "Modified"
Warranty date code "Unavailable"
The IMEI looks fine, unlike many of the threads i saw in a search.
any advice?
ok, so after doing like 11 things that didnt work, or at least not completely, including losing my twrp access at one point early on (scaring the piss outta me) i have fixed it with a KDZ using:
this guide:
http://www.cellrabta.pk/2013/10/how-to-flash-big-kdz-files-optimus-g-gk-g-pro-g2-and-others/
and this KDZ:
http://forum.xda-developers.com/verizon-g2/development/stock-vs98039a05-kdz-lollipop-t3069041
it wasn't flawless, and some stuff didnt seem to work right, like at :
"Now click at ‘Normal web upgrade test’." the support tool opened but the option to "start upgrade" was greyed out so i went to "options > upgrade recovery" and let it download and install it on its own. oddly enough it looked (on the phone) like it listed both what the assistant downloaded and the one i chose within the flash tool but it seemed to work fine. i just spent about 1/2 hour on the phone with someone without losing connection so thats a bonus, and the baseband is listed now, the Software Status is "Official", and the Warranty date code is missing, or at least i cant find it again anyway. i lost my root, but i dont care at this point. no more taking chances for me, at least not till upgrade time anyway.
hope someone out there finds any of this useful, if for no other reason than to see why one should never tinker with something they cant afford to lose, especially when one is a novice at best.
Deviouz1 said:
ok, so after doing like 11 things that didnt work, or at least not completely, including losing my twrp access at one point early on (scaring the piss outta me) i have fixed it with a KDZ using:
this guide:
http://www.cellrabta.pk/2013/10/how-to-flash-big-kdz-files-optimus-g-gk-g-pro-g2-and-others/
and this KDZ:
http://forum.xda-developers.com/verizon-g2/development/stock-vs98039a05-kdz-lollipop-t3069041
it wasn't flawless, and some stuff didnt seem to work right, like at :
"Now click at ‘Normal web upgrade test’." the support tool opened but the option to "start upgrade" was greyed out so i went to "options > upgrade recovery" and let it download and install it on its own. oddly enough it looked (on the phone) like it listed both what the assistant downloaded and the one i chose within the flash tool but it seemed to work fine. i just spent about 1/2 hour on the phone with someone without losing connection so thats a bonus, and the baseband is listed now, the Software Status is "Official", and the Warranty date code is missing, or at least i cant find it again anyway. i lost my root, but i dont care at this point. no more taking chances for me, at least not till upgrade time anyway.
hope someone out there finds any of this useful, if for no other reason than to see why one should never tinker with something they cant afford to lose, especially when one is a novice at best.
Click to expand...
Click to collapse
Amen, Preach it
I'm trying the above right now- hopefully getting to a working phone by tomorrow. Thanks for sharing.
EDIT- Still no download mode for me so I guess this is another dead end.
damn, sorry youre having even more trouble than i did, which is saying something to be sure. good luck man, hope it all works out for ya. if i had a clue i'd give it to ya.
edit: actually, can you still get into the phone normally? if so try using autorec. thats how i got my twrp back and i think it fixed my download mode too which is how i was able to finally fix mine.
Deviouz1 said:
So this happened:
http://forum.xda-developers.com/lg-g2/help/vs980-twrp-bootloop-botched-lollipop-t3072133
and once that was "fixed" i was able to use the phone, but it was acting funky. like dialing numbers was oddly laggy and while i can successfully call someone, it disconnects almost immediately and the cell network appears to be ... cycling itself for lack of a better term. i went looking at the various versions/info etc in About Phone and see the following
Baseband "Unknown"
Software Status "Modified"
Warranty date code "Unavailable"
The IMEI looks fine, unlike many of the threads i saw in a search.
any advice?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3076993
Sent from My LG G Flex LG-F340K Stock KitKat V20D on LTE Network using XDA Free Mobile app
I got mine from Amazon yesterday, I already bricked it a few hours ago by messing with the recovery. It should be an easy fix once I get hold of the stock firmware. I got another one coming tomorrow, so I'll focus on just extracting the rom from that one
Bricking aside, I got 20/10mbs down/up on speedtest using my T-mobile US SIM, and the signal indicator showed LTE. Forcing it off LTE I got 10/5mbs down/up.
Battery life is awesome, I used it constantly for 8hrs and only got down to 50%, my note4 would have been dead after that much use with the screen on. The overall feel of Android 6.0 was smooth, no stuttering. There is no bloatware, just a few utilities for fancy wallpapers.
The phone charges faster than any other phone I have. The included TPE case doesnt increase the thickness of the phone too much and I like that It keeps the camera lens off the desk when I set the phone down.
Dual SIM functionality works nice. It was one of the main features I was looking for, though I will miss T-Mobile wifi calling.
Some notes:
I used adb & fastboot in my attempts to root. After running
Code:
fastboot oem unlock
fastboot reboot
the display now showed
Code:
Orange state
Your device has been unlocked and can't be trusted
Your device will reboot in 5 seconds
So it appears that it is best to oem relock it when you're done updating, as the message goes away if you relock.
Backing up the ROM
I found SP Flash Tool v5.1632 for Linux and I've been practicing saving chunks of ROM from my bricked phone. I should be able to grab the recovery portion of the new phones' ROM tomorrow.
Based on the scatter.txt file I've found for the Gionee S8 AmigOS Marshmallow ROM, recovery starts at 0x8000 and is no more that 16Mb is size. So, in theory, I should be able to grab that range of the ROM and flash it using fastboot back to my bricked unit. I'm using the word "bricked", but its far from that, I should just say "unbootable" to be more clear.
Earlier today I was trying to get MTK droid tools to detect my Blu Pure XR so I could extract the scatter file, but It never was detected. All the drivers installed ok, so maybe its not compatible, I'm not sure yet. I'll get back onto that after my first unit is back up and working, hopefully tomorrow.
Edit: I just found a modified MTK Droid Tools for 64bit cpu phones, I'll give this a try too.
Edit next day: I got the second phone this morning. I used SP Flash Tool to grab the recovery.img portion of the new phone, then I used fastboot to flash it to the damaged phone, and it worked fine. The bootloader unlock/relock caused the phone to wipe itself and then re-encrypt the file system, so I lost a few test photos, no big deal. FWIW, I could have flashed the recovery back to the damaged phone using SP Flash Tool, but I wanted to make sure it worked with fastboot, which it did.
Heres the recovery.img for those that may need it and don't have two phones
View attachment xr-recovery.zip
Monday or so my mom gets her phone, so I'll be able to test LTE on AT&T with her SIM card. I just got 34Mbs download on a speed test (T-Mobile), which is is fine, considering all the naysayers reviewing on Amazon who didn't have the guts to buy the phone, saying LTE wouldn't work at all.
I just heard of this device today. I wonder how quick Android 7.x can be flashed over to this, but for $299 it's a good looking phone.
It may be a while since there's not much activity happening on this device yet.
I'm focusing on creating a rooted boot.img right now, as I'll be happy with 6.0 and root. I plan on having this done today. I've never created a custom twrp recovery, but I may try that next.
I need to figure out how to prevent the full wipe after oem unlocking/relocking, that's a real pain having all my setup deleted after every test, as it makes it hard to use the phone while developing.
Got root
Firstly, I'm still learning about Mediatek based devices, so I feel like a noob again. I haven't edited a ROM in several years and there's a lot of crap info on the internet. Most articles that write up "how to root a phone" basically say "Install twrp, then supersu", yeah, thanks
After struggling with all the selinux controls in 6.0, I switched to hack mode. As per phhusson's super-bootimg script, I used his sed technique to force the init in boot.img to not enforce security policy and added his bits to init.rc to load su. I put su and in system.img along with a suid root shell just in case. Its working, I have SuperSu installed, and it pops up to ask me to grant permissions. It won't update its su binary, I've got some permission problem there, but it's not a show stopper. Also,I found its easiest to just leave the bootloader unlocked while testing, I just have to get used to the annoying boot message and 5 second delay.
This week I'll start from scratch and document the procedure I used and hopefully make it repeatable for anyone else who may want to try it. Maybe someone will just port twrp and save me the time of learning how to do it
Some notes on the software I used:
Windows:
* SP Flash Tool with a bogus scatter file to grab the stock ROM sections of my phone as the Linux version would timeout reading large ranged of flash.
Linux:
* mktool to unpack/repack the boot.img
* loopback mounted the system.img to add su to it.
* used img2simg to convert system.img to a sparse image
* fastboot to flash the boot & system images to the phone.
AT&T Speed Tests
No good, ~500kbs up/down, even though signal strength showed 4 bars on 4G. No LTE at all. Changing the band set to 3g/4g had no real effect either way. Don't buy this phone I you plan on using it with AT&T, although my mother hasn't noticed the ****ty 4G in actual use yet (I'll switch her to T-mobile soon).
Update: After using the phone for 1 week, I am extremely pleased with it. I chuckle when I read the negative reviews on all the big phone web sites. Reviewers hate the wiggly button, LOL, but it doesn't bother me as I'm used to it on my Samsungs. Other than the wiggly home button, its a solid phone. I prefer the metal back as opposed to glass. By the way, who's brilliant idea was it who thought an all glass phone was a good idea?
It's not AOSP, but I find it's AmigOS Carefree launcher very pleasant to use, and I've used countless launchers over the years. It's got way better specs than the Nexus 5X and after struggling with the security in 6.0, I'm not in any rush to find out what security bull**** awaits me in 7.0 (for my benefit of course).
On the flip side, I don't use NFC payments, Google Pay, Google Play, no Google anything. All Google stuff disabled. I run my own calendar/contacts/tasks sync server, use oandbackup to save/restore all my apps and settings, the majority of my apps come from f-droid. I don't play games. So I'm not an average user. I've been using Android devices since the Nexus One and I have a pile of phones in front of me. Blu (or Gionee) has shown it can make quite a competitive device that I enjoy using all day, (though I wouldn't be using it at all unless it was rooted, so luckily for both of us that is the case).
Rant: Things that are actually more annoying than a wiggly button:
* Dozens of phone review websites that all publish a review of this phone within 2 days of each other after the phone was released on Aug 29th ,with all the same content. It's like they are all run by the same hack, just to get advertising dollars.
* Websites like rootoreviews.com that use a template on how to root this particular phone using twrp, when twrp doesn't exist yet for the device. WTF is that? Why would someone think this is a great idea? They have the same instruction set for every phone on the site with the make/model info swapped out. Are they just hoping twrp becomes available soon so they have the first post on the topic by default? Lame!
rotohammer said:
No good, ~500kbs up/down, even though signal strength showed 4 bars on 4G. No LTE at all. Changing the band set to 3g/4g had no real effect either way. Don't buy this phone I you plan on using it with AT&T, although my mother hasn't noticed the ****ty 4G in actual use yet (I'll switch her to T-mobile soon).
Update: After using the phone for 1 week, I am extremely pleased with it. I chuckle when I read the negative reviews on all the big phone web sites. Reviewers hate the wiggly button, LOL, but it doesn't bother me as I'm used to it on my Samsungs. Other than the wiggly home button, its a solid phone. I prefer the metal back as opposed to glass. By the way, who's brilliant idea was it who thought an all glass phone was a good idea?
It's not AOSP, but I find it's AmigOS Carefree launcher very pleasant to use, and I've used countless launchers over the years. It's got way better specs than the Nexus 5X and after struggling with the security in 6.0, I'm not in any rush to find out what security bull**** awaits me in 7.0 (for my benefit of course).
On the flip side, I don't use NFC payments, Google Pay, Google Play, no Google anything. All Google stuff disabled. I run my own calendar/contacts/tasks sync server, use oandbackup to save/restore all my apps and settings, the majority of my apps come from f-droid. I don't play games. So I'm not an average user. I've been using Android devices since the Nexus One and I have a pile of phones in front of me. Blu (or Gionee) has shown it can make quite a competitive device that I enjoy using all day, (though I wouldn't be using it at all unless it was rooted, so luckily for both of us that is the case).
Rant: Things that are actually more annoying than a wiggly button:
* Dozens of phone review websites that all publish a review of this phone within 2 days of each other after the phone was released on Aug 29th ,with all the same content. It's like they are all run by the same hack, just to get advertising dollars.
* Websites like rootoreviews.com that use a template on how to root this particular phone using twrp, when twrp doesn't exist yet for the device. WTF is that? Why would someone think this is a great idea? They have the same instruction set for every phone on the site with the make/model info swapped out. Are they just hoping twrp becomes available soon so they have the first post on the topic by default? Lame!
Click to expand...
Click to collapse
Hi theer just curious on how you get it to root then??
Thanks for potentially inspiring some activity here regarding this phone. It looks like an impressive device, but I won't pull the trigger until there're some solid rom options.
Hey brother hope you r doing well. Glad to see this thread with the smartphone similar to mine. My phone is symphony helio s20, mtk6755 helio p10 processors, 4gb ram 64gb rom with the similar system.img and boot.img of gionee s8 & blu pur xr.
I was desperately looking for a pre rooted rom or a custom, custom recovery and rooting tool for almost 2 months, requested so many times all around this site, but unfortunately didn't get any respons (really frustated). I just badly need to root my device but I'm just a noob on modding and tweaking with Roms. I got my stock rom from Service Center, when I bricked my phone flashing a custom recovery. Later I tried all the method found all over the website but non of them are working only misleading. Bricked my phone several times but luckily I managed to reflash the stock rom by sp flash tool. Please keep this good work up and help us root our devices without any hassle. You are doing a really great work so keep it up bro!
Here is the link of my stock firmware with sn write tool if you need it for anything bro.
Best regards
https://drive.google.com/open?id=0BywTv6KKZO4jX3BMMGRGVUFRa28
http://www.mediafire.com/download/7...N_Writer_tool_exe_v1.0_1604.00_All_In_One.rar
http://www.mediafire.com/download/pa2f3wqpf24t0db/Helio_S20_flashtool.zip
thanks in advance
Hey guys, thanks a lot for all your info and everything you posted Could you be so kind to describe how did you root your Pure XR devices??? Big hug from Cuba
I'm going to guess something with KingRoot. This is a rebranded Gionee S8, so China is already no stranger to this phone.
Not surprised about AT&T performance considering I've never seen an unlocked phone support so few LTE bands (2, 4, 7). Ridiculous. It supports less than half of all the LTE bands AT&T uses. Unless your area uses primarily band 2 or 4 you're screwed if you're on AT&T. Even worse if you're on T-Mobile. It only supports ONE band on T-Mobile. Does Blu even realize it's 2016?
bailsafe said:
I'm going to guess something with KingRoot. This is a rebranded Gionee S8, so China is already no stranger to this phone.
Click to expand...
Click to collapse
I tried every rooting tool, including KingRoot, none worked. There's an OTA update for the stock firmware, but I wont be able to install it until after I un-root. I probably retrace the steps I did the first time: backup all my apps, flash the stock firmware, do the OTA, then save/edit it to have root, then flash the result. The phone works so good right now that I'd hate to mess it up.
Tikerz said:
Not surprised about AT&T performance considering I've never seen an unlocked phone support so few LTE bands (2, 4, 7). Ridiculous. It supports less than half of all the LTE bands AT&T uses. Unless your area uses primarily band 2 or 4 you're screwed if you're on AT&T. Even worse if you're on T-Mobile. It only supports ONE band on T-Mobile. Does Blu even realize it's 2016?
Click to expand...
Click to collapse
This was a Gionee S8 originally, which only supported FDD-LTE bands not in use in the USA. It's a miracle they got FDD-LTE in here at all, I guess, but if you're gonna sell in the US market... they really need more bands.
Rotohammer said:
I tried every rooting tool, including KingRoot, none worked. There's an OTA update for the stock firmware, but I wont be able to install it until after I un-root. I probably retrace the steps I did the first time: backup all my apps, flash the stock firmware, do the OTA, then save/edit it to have root, then flash the result. The phone works so good right now that I'd hate to mess it up.
Click to expand...
Click to collapse
That's probably your best bet. I'm surprised KingRoot wouldn't work, even on the newer updates...
hey I was wondering for some reason my blu pure xr does not receive notifications at all except for certain apps and it keeps on disconnecting from messenger and such is there any remedy for this?
orlandotisk said:
hey I was wondering for some reason my blu pure xr does not receive notifications at all except for certain apps and it keeps on disconnecting from messenger and such is there any remedy for this?
Click to expand...
Click to collapse
Press left button to bring up the running apps list, long press the button with 3 rectangles in it, then press "Clean white list". Here, you press"Add into white list" and choose "messenger" and any other apps you don't want "auto cleaned".
For example, my white list includes Alarm Klock, K-9 mail, CSipSimple, Silence (all apps that I want running all the time)
rotohammer said:
I got mine from Amazon yesterday, I already bricked it a few hours ago by messing with the recovery. It should be an easy fix once I get hold of the stock firmware. I got another one coming tomorrow, so I'll focus on just extracting the rom from that one
Bricking aside, I got 20/10mbs down/up on speedtest using my T-mobile US SIM, and the signal indicator showed LTE. Forcing it off LTE I got 10/5mbs down/up.
Battery life is awesome, I used it constantly for 8hrs and only got down to 50%, my note4 would have been dead after that much use with the screen on. The overall feel of Android 6.0 was smooth, no stuttering. There is no bloatware, just a few utilities for fancy wallpapers.
The phone charges faster than any other phone I have. The included TPE case doesnt increase the thickness of the phone too much and I like that It keeps the camera lens off the desk when I set the phone down.
Dual SIM functionality works nice. It was one of the main features I was looking for, though I will miss T-Mobile wifi calling.
Some notes:
I used adb & fastboot in my attempts to root. After running
Code:
fastboot oem unlock
fastboot reboot
the display now showed
Code:
Orange state
Your device has been unlocked and can't be trusted
Your device will reboot in 5 seconds
So it appears that it is best to oem relock it when you're done updating, as the message goes away if you relock.
Click to expand...
Click to collapse
Hey bro how are you? How's family? I hope that everything is well for you and yours. Basically I just wanted to say thanks for sharing such great info. And I'm really glad that there's someone who's onto something like einstein. I just hope that you can figure out a way to get root with your own custom build of twrp recovery using chainfire's supersu to work with this smartphone. Cos that'll be super-awesome right? But I'm just a noob so all I can do is just wish you the best of luck. So best of luck until you crack the code. And I have complete faith in you. You will achieve it I know that for sure. Wish you and yours all the best. And thanks again in advance. Peace!
Does anybody succeed rooting ?
Please share the method!!
so no one knows how to root?
rotohammer was able to achieve root and said he would get back to us with the method on how it was done, but he hasn't posted it yet...
I just tried to use my banking apps for the first time on my brand new OnePlus 5. It's completely stock still, not rooted or anything. I have 2 banks and both of their banking apps fail to load. Also Android pay fails to work, tells me I need a network connection when I already have one. I confirmed my banking apps are still working on my HTC one m9 but I no longer have the s8 or s6 I use to use Android pay with. I tried searching on here and didn't see anyone else having these issues. Any ideas?
Is your bootloader perhaps unlocked?
Unless oneplus sends them out that way from the factory, no. But I haven't actually checked.
Did you give the apps the correct permissions?
I had the same issue with one of my Banking apps, fully stock with locked bootloader, and when opening the app it sent me to a website page stating that my software was modified.
My solution was to unlock bootloader, install TWRP, root and use banking on my laptop :angel:
Sent from my OnePlus 5 using XDA Labs
I guess my solution is going to be to carry my old HTC around and tether off the OnePlus when I need to check my account balance. I sure hope they fix this soon.
Have you tried Magisk hide? Every app i've tried has been spot on with that, work email, snapchat, everything really, don't use banking apps on my phone so couldn't say for sure.
I got an update last night, plus I went into app permissions and gave them every permission possible. Still no go. It says the app has encountered an unexpected problem after it tries for maybe 15 seconds to load.
Snapchat works fine. I haven't tried magisk. I wasn't going to bother rooting this phone because I like it as is.
Android Pay and my bank apps work fine on my stock, locked bootloader OP5. I'm in the US.
Seems peculiar Android Pay fails. Have you tried hard resetting?
I cleared data and uninstalled all 3 apps and I got both banking apps to work on the second try. Android pay kept telling me I needed a data connection which I already had. I realized NFC wasn't turned on so I turned that on and then it seemed to get past that part but it tells me my card isn't supported so I need to look into that with my bank.
Not sure why it didn't work the first time. It seems like I've had to reboot this phone for weird glitches a lot more than I did on my old s6. Hopefully that doesn't continue.
Update: they stopped working again. They seem to work once and then the next time you to try to log in it fails every time. Glad I still have an old HTC one m8 I can bank with. Lol. I'm not doing Android pay on a phone without a finger print sensor though.
350Rocket said:
Snapchat works fine. I haven't tried magisk. I wasn't going to bother rooting this phone because I like it as is.
Click to expand...
Click to collapse
You're stock and they're not working? Weird.
Do you have to de-authorise the banking apps to use them on another phone? My back accounts app requires that
I don't believe so. I traded the s6 on the s8 and they worked fine right away on both of those ones when I first got them. Plus I've used them interchangeably on my main phone and my backup HTC m9 quite a bit. I reinstalled them on the m9 when the OnePlus failed to work and that's how I've been getting by.
I have been having an issue with Venmo. It won't let me verify the device, this has been happening since I got the device. Now I am unlocked/rooted with Magisk hiding, and it's still not letting me verify. So strange.
shrtysskat8 said:
I have been having an issue with Venmo. It won't let me verify the device, this has been happening since I got the device. Now I am unlocked/rooted with Magisk hiding, and it's still not letting me verify. So strange.
Click to expand...
Click to collapse
Figured out my issue. I had an adblock enabled and it wouldn't let it send the code because of that. Disabled and all is well.:good::good:
I am in the UK. My OP5 is completely stock. I have Lloyds, Nationwide and Barclaycard banking apps installed and working plus Android Pay. So, it should work OK.
I am running version .8 of the OS
Alan
I believe I was on 4.5.10 before the update and now it's 4.5.11. So maybe they broke it with the .10 update? I really don't see anything else I could have done to make it not work. I've never had a problem before even on rooted phones.
OP curious what does your android pay do that it doesn't work?
Does it open or when you pay it doesn't work
I haven't tried it at a terminal yet, but I believe it's ready to work. I switched banks and my new debit card isn't compatible with Android pay even though I was lead to believe it did.
I added my one credit card and my old debit card and they seem to be ready to go now.
So my issue now is only with the banking apps, not Android pay.
My snapchat (lest safetynet) won't work at all. Tried different roms.....
My brother passed away and was using this phone until a couple of weeks ago. I don't have the lockscreen pattern but I'm trying to do a little detective work regarding my brothers last activity. I reached out to law enforcement, but they don't have an active investigation and they suggested that I reach out to his cell provider [Tracfone] which I might try. Of specific interest to me is his text message activity on the day of his death.
Anyhow I scoured the net and tried to beat the lockscreen via emergency dialer, and also tried to connect via adb shell and MTP. I also don't think the device was registered via the samsung tools. I'm at the point where the device told me I have 9 unlock attempts left and it will erase the device after. The lockscreen seems to appear at device power and I think that it might not have booted android completely at this point.
Is anybody aware of a method to bypass the lockscreen which would work on this device so I can look into the details surrounding his death?
Sort of desperate here. There seems to be some software called Dr Fone that claims to have a lockscreen removal. However not sure that it works and on this device.
I may have a solution for this if you are wanting to preserve data if not check around on youtube for a video on FRP resetting this. I might have wrote a tutorial on this somewhere but I cant remember atm. Basically if you don't want to preserve the devices data (your brothers as you say) then you will simply factory reset it and then follow an FRP Removal tutorial you can find on here and or youtube.
btw nice leet username =]
phonecapone said:
I may have a solution for this if you are wanting to preserve data if not check around on youtube for a video on FRP resetting this. I might have wrote a tutorial on this somewhere but I cant remember atm. Basically if you don't want to preserve the devices data (your brothers as you say) then you will simply factory reset it and then follow an FRP Removal tutorial you can find on here and or youtube.
btw nice leet username =
Click to expand...
Click to collapse
Speaking of nice usernames
If you're still around, I have an old J327t1 that I had dropped and broke the screen on a few years ago. I recently fixed it, but can't remember PIN. I would like to preserve the data and am interested in what you have
veryspecialagent said:
Speaking of nice usernames
If you're still around, I have an old J327t1 that I had dropped and broke the screen on a few years ago. I recently fixed it, but can't remember PIN. I would like to preserve the data and am interested in what you have
Click to expand...
Click to collapse
All you need to do is find a recovery for that and flash it then go into the lock files and remove those. You can find some guides here on XDA or on youtube.
This was before I got into development, so adb isn't enabled, bootloader is still locked, and the phone is not rooted, so I'm skeptical I'd be able to flash. It's also running (I believe) Marshmallow, and most of those "find and delete lock settings" methods were for 4.x Kit-Kat and below. I could be wrong though.
If you have a particular thread in your watch list, I'd be grateful for the link.
I've been all over looking for a solution, hence me posting in here as opposed to creating a thread. Didn't want to reinvent the wheel if I didn't have to.
Despite the above limitations, the device has not received any updates since June 2017, it DOES go into MTP mode when I hook it to my laptop, and I have verified that it is vulnerable to the Mtpwn exploit.
noidodroid said:
All you need to do is find a recovery for that and flash it then go into the lock files and remove those. You can find some guides here on XDA or on youtube.
Click to expand...
Click to collapse
Also, I turned a moto g7 Play into a Nethunter device and had tried Android PIN Bruteforce, but after entering in so many PINs it would make me wait 30 seconds to try again and I couldn't figure out how to get my g7 to keep the screen of the J3 on. Or wake it back up, since it requires you to hit power then swipe the screen.
I ended up wiping it because it had Pie and no workaround for the wifi throttling, and installed Q. It's rooted, but I haven't set up nethunter back up on it yet. I do have an S5 that I has Nethunter, but haven't set it up with HID support yet. Plus, the battery on that would drain too quickly to use for this process.