Related
Hello. Sorry if I sound like a COMPLETE noob here and if I posted in the incorrect place.
I am going to start from the very beginning so I can explain myself.
I am currently on a mission to be able to play Pokemon GO on my tablet and spoof my GPS without getting banned. Ill be running it on an account that I wouldn't care if it was banned so please do not just tell me to not do it.
First of all I had manually installed an update to lollipop (5.1.1) when first receiving the tablet. This was still Samsung official OS. In order to obtain my goal I had to root it. So after trial and error I managed to get my device rooted using KingRoot. Couldn't understand a damn thing because it was in Chinese but it was still successful.
This allowed me to install my GPS spoofer hider (supposed to hide GPS spoof from GO). Now it seemed promising until it told me I needed Xposed framework installed. Went to go install it however now I need a custom recovery manager to install that. I have checked with both ROM Manger and TWRP but I cant find my device. I assume its not supported by either.
Is there any decent custom recoveries that will work for my device or have I hit a complete dead end? Maybe someone might even have a COMPLETELY different approach to accomplish my goal. I don't know if you need this to answer my questions but here is everything that seems relevant in about my device.
----------------------------------------------------------------------------------
Model Number: SAMSUNG-SM-T337A
Android Version: 5.1.1
Baseband version: T337AUCU2BOH44
Kernel Version:
3.4.0-5608828
[email protected]#1
Thu Aug 13 17:01:34 KST 2015
Build Number: LMY47X.T337AUCU2BOH4
-----------------------------------------------------------------------------------
I would also like to say thank you. Not just for helping me directly in my situation but for everything. MANY of times I have wanted to do something on my phones and other android devices and I would always end up in these forums and get everything I needed. You guys are the best!
Update.
I have been reading deep in the threads. This tablet seems to be one of THE MOST frustrating android devices to try and work on.
This is what I have tried to this point.
Doing a little more research I found that I could use flashfire to get Xposed working. Thats when I ran into another problem. flashfire will not work with kingroot and will with SU.
Despite all the warnings, I tried to use SuperSUme and install superuser over the kingroot to remove it.
Softbrick..
Put it into download mode and reinstalled 5.1.1 which fixed it, buuuut now I have no root.
This led me to look into kingroot a little more and much like others, I have found kingroot to be a little too shady for me. I will not be using the kingroot path again.
1 step forward, 10 steps back.
I am currently working with someone else on the forums here to see if we can work on a way to get TWRP to work on the tablet. If we are successful then chances are I will be able to downgrade the OS back to 4.2.2 KitKat. My understanding is that OS is rootable for this tablet. After that I am going to look into a way to unlock it so I could possibly use it for cricket. I don't exactly have high hopes for it but it is worth a shot.
Custom recovery may be achievable but please do not kid yourself, you will end up with a brick if you try to downgrade the os
Hi guys. I very narrowly (somehow) managed to recover from almost bricking my phone.
I successfully S-Off'd my phone, and previously successfully installed TWRP. I tried to install this ROM:
https://forum.xda-developers.com/ve...m-perfumewl-m60-dev-edition-unlocked-t3442969
When I tried the to flash the ZIP for firmware and for the ROM, the firmware wouldn't install. I tried some other stuff and basically almost bricked my phone. Some how got it to suddenly start being able to use the htc_fastboot commands (????????) and was able to start installing the zip for stock... but it ran an error, I ran it again and it froze... then I forced my phone to reboot and somehow I'm back to having a stock system. No clue what I did.
My question is, can I take a software update on my phone normally (to 7.0) , and then install just that ROM? Or so I need to flash the firmware separately with a command line command? I just don't want to give myself another heart attack tonight. Current firmware version is 1.82.605.6, not rooted, don't believe my recovery is TWRP right now (but I know how to install that one).
I'm just looking for root access and the ability to remove pre-installed Verizon crap (VZW Messager, My Verizon, etc). Thanks guys.
CritKlepka said:
Hi guys. I very narrowly (somehow) managed to recover from almost bricking my phone.
I successfully S-Off'd my phone, and previously successfully installed TWRP. I tried to install this ROM:
https://forum.xda-developers.com/ve...m-perfumewl-m60-dev-edition-unlocked-t3442969
When I tried the to flash the ZIP for firmware and for the ROM, the firmware wouldn't install. I tried some other stuff and basically almost bricked my phone. Some how got it to suddenly start being able to use the htc_fastboot commands (????????) and was able to start installing the zip for stock... but it ran an error, I ran it again and it froze... then I forced my phone to reboot and somehow I'm back to having a stock system. No clue what I did.
My question is, can I take a software update on my phone normally (to 7.0) , and then install just that ROM? Or so I need to flash the firmware separately with a command line command? I just don't want to give myself another heart attack tonight. Current firmware version is 1.82.605.6, not rooted, don't believe my recovery is TWRP right now (but I know how to install that one).
I'm just looking for root access and the ability to remove pre-installed Verizon crap (VZW Messager, My Verizon, etc). Thanks guys.
Click to expand...
Click to collapse
I recommend you install this one instead:
https://forum.xda-developers.com/ve...m-1-85-605-9-aroma-root-root-debloat-t3529732
Follow instructions in OP...or:
1)fastboot flash FW w/o Boot w/ TWRP (htc_fastboot oem rebootRUU, fastboot flash zip...)
2)htc_fastboot reboot-bootloader
3) Finally, go into recovery-- backup and flash ROM (choose root w/ Magisk and debloat)
Thanks, I figured out why it wasn't working before. Used official TWRP, thats why it wasn't working. Wouldn't have thought that'd made that much of a difference.
New problem though; something I really would like to use the Google versions of contacts and dialers. Trying to flash those just made my phone app unusable. So I turned to LineageOS but it REFUSES to boot. Hangs on their little vertical line with a moving circle. Found out AOSP roms don't like VZW firmware? Flashed global firmware, updated through WiFi as much as possible, and then ran into issues with radio, even though I flashed the VZW one. So I reverted those changes, am going through with what you said above to have a working phone (after not having one all day), but any advice on getting Google dialer and contacts? I'd like to use LineageOS but I couldn't get it work at all.
CritKlepka said:
Thanks, I figured out why it wasn't working before. Used official TWRP, thats why it wasn't working. Wouldn't have thought that'd made that much of a difference.
New problem though; something I really would like to use the Google versions of contacts and dialers. Trying to flash those just made my phone app unusable. So I turned to LineageOS but it REFUSES to boot. Hangs on their little vertical line with a moving circle. Found out AOSP roms don't like VZW firmware? Flashed global firmware, updated through WiFi as much as possible, and then ran into issues with radio, even though I flashed the VZW one. So I reverted those changes, am going through with what you said above to have a working phone (after not having one all day), but any advice on getting Google dialer and contacts? I'd like to use LineageOS but I couldn't get it work at all.
Click to expand...
Click to collapse
You've got to read OPs, search threads, etc. Some ROMs work w/ our phone, and some do not. Check out the latest versions of ice and leedroid. Your most likely want to grab the SVN versions is the official versions may not yet support Verizon N firmware
Antny6 said:
You've got to read OPs, search threads, etc. Some ROMs work w/ our phone, and some do not. Check out the latest versions of ice and leedroid. Your most likely want to grab the SVN versions is the official versions may not yet support Verizon N firmware
Click to expand...
Click to collapse
I have been doing a lot of searching, but I've found so many different, conflicting sources of information. For example, one website told me to install LineageOS, was to be on latest Verizon OTA and just normally flash it; that obviously didn't work.
So from what I can see, our choices are Viper, Ice, LeeDroid, NuSense and the one you linked. I'm going to try out LeeDroid... out of curiousity, is there any reason, for example, LeeDroid or Ice haven't posted in this Verizon section with links to their ROMs?
*Edit Two* Dialer wouldn't work out of the "box" so to speak, so I had to go to Phone settings at the bottom, there is a menu called Calling Accounts. Had to go there and tap Receive Incoming Calls... why is that disabled in the first place..? But that seems to be an issue going even as far back as the Nexus 5. But that's how you find the option in the HTC 10 for anyone who comes across this issue too...
Not sure why your having issues with the flashing. Are you doing a full wipe? Not just factory reset. Going from stock to lineage requires a complete format of internal SD card. On the stock roms, most will ask if you are still on marshmallow firmware & are working fine. Again, we need more info on what firmware version your on, version of twrp& how your wiping your device. Most AOSP roms work, but no advanced calling
LOS ROMs will work without issue IF you have flashed the US unlocked firmware at some point in time. This is the only information that we have found from a VzW device with LOS booting and VzW device without. We started a thread awhile ago and is the only known method we currently know of to get LOS booting. Also works for Sprint users.
https://forum.xda-developers.com/verizon-htc-10/how-to/how-to-cm-booting-vzw-vzw-firmware-t3500900
Is anyone having problems with Bluetooth on their device? Just need to enable it on mine because I used 2FA with my Google account, & have a security token.
Model Number: BTV-W09
Build Number: NRD90M test-keys
EMUI Version: 5.0
Android Version: 7.0
Everything else seems to be working, at least so far. Still only seeing 2.4 GHz frequency with WiFi, but getting 5.0 GHz working is something I can work on later.
My Bluetooth seems to be working fine. I am on EMUI 5 / Android 7.
the second update file likely did not install correctly when attempting the dload method correct? the solution is to install the second update file as a zip from twrp. that fixes the problem, and updates your system version to the correct btv-w09c128b350 (if your using us version) if you don't have the second update file you can download it using firmware finder app, be sure its the full ota version, as the others do not work with this method.
tomchism said:
the second update file likely did not install correctly when attempting the dload method correct? the solution is to install the second update file as a zip from twrp. that fixes the problem, and updates your system version to the correct btv-w09c128b350 (if your using us version) if you don't have the second update file you can download it using firmware finder app, be sure its the full ota version, as the others do not work with this method.
Click to expand...
Click to collapse
I love how people here use abbreviations so frivilously. TWRP?? I googled that and it seems to be a root method. Rooting the tablet isn't a solution to this and we need bluetooth and 5ghz working for US. I had an EU update installed before this, then I hear the US update is out and I hoped it fixed the bluetooth issue. But now I have a USA version with a disabled bluetooth and no 5ghz wifi radio. This tablet is becoming more of a pain than anything....
When it comes to Android, your best solution is not a Google search but a search of the forums here at XDA, TWRP, is a recovery system that can be installed on the device. Once installed it can be used to perform system backups and restores, install firmware install root, wipe a device, do all sorts of nifty things.
To install TWRP you need to unlock your device, the instructions for doing that are in a different forum. Once unlocked you will need to set up adb which instructions can be found in the install TWRP forum, each version of TWRP is device specific, so you have to get the right one. If you really want to dig into figuring out how to do this, you will need to spend several hours reading the forums about this device, or find a friend who knows how to do this that you can trust not to brick your device.
tomchism said:
When it comes to Android, your best solution is not a Google search but a search of the forums here at XDA, TWRP, is a recovery system that can be installed on the device. Once installed it can be used to perform system backups and restores, install firmware install root, wipe a device, do all sorts of nifty things.
To install TWRP you need to unlock your device, the instructions for doing that are in a different forum. Once unlocked you will need to set up adb which instructions can be found in the install TWRP forum, each version of TWRP is device specific, so you have to get the right one. If you really want to dig into figuring out how to do this, you will need to spend several hours reading the forums about this device, or find a friend who knows how to do this that you can trust not to brick your device.
Click to expand...
Click to collapse
does the above mentioned operation void my guarantee for the tablet ?
That's a difficult question to answer. The device comes with two recovery systems built in. There are not many scenarios where you can hard brick the device and are unable to restore it back to factory settings, locked unrooted and like new. Any warranty issue are likely to be hardware not software.
Hmm. I am in the process of using the dc-unlocker client to unlock my bootloader. When the client reads my phone, it shows the build number as NRD90M test-keys, but when I look at device info on the phone, it shows a normal build number. Does anybody know what this means?
Hi. Been waiting a while to post this, and playing around based on what I see, but I the last change I made to my phone hasn't worked out too well and I don't think I have enough of a grip on the process. I am an ex-computer 3rd level tech support so I have reasonable skills around computers etc.
I bought an Axon 7 (A2017G) in Germany but it got flooded one day when it went down the toilet pan, literally. So I replaced it with a 128 Gb model from China, not really thinking about the software versions. Of course it came with A2017, and more importantly, no ability got OTA upgrades from Android 6.
So recently I've been having some battery life issues so I've changed the battery.
Following guides here, I've managed to get it onto a newer A2017 version and it has taken an OTA upgrade to Android 7. The build number is B13. The boot loader is still unlocked. But it's not very stable and Google Play service has now stopped, and I can't be doing with the unreliability. And tbh although it worked, I can't remember exactly which guide or what steps I followed to do it.
So I want to put it onto a stock G version, which I think seems to be possible, based on stuff I've read here. I don't think I need root going forwards (once this is done) and I'm looking for the simplest method. Unfortunately, due to the length of time it's been live, this forum really is information-overload and I've been reading for two days now and made loads of notes but I'm not really very clear about what I need to do.
I'm quite happy to find and read the right guides but would be really grateful if someone could take a few minutes to just tell me exactly which bits are essential to be upgraded and what steps I do need to follow. If I am confused I can come back with any queries.
I'd be happy to root the phone if it's felt that is a really useful thing but I'm not really a "power user" and I'm OK with standard.
Also I'm assuming any upgrade would receive any future Android releases OTA (if there are any for this phone), but if not that's not too vital.
Thanks in advance...
Geoff
But regarding your situation: You have an A2017 with A2017G firmware, right? Can you tell us your firmware version?
Would you be fine with Chinese firmware (MiFavor 5.2, B17) or prefer stock+ (G B01/B02, U B12)?
Thanks for the quick response, really appreciated.
The firmware is still A2017 version AFAIK, but I don't know where to check. If I go to the boot loader screen it says ZTE/P996A03_N/ailsa_ii and on the next line 7.1.1/NMF26V/20170912.013327
I'm thinking I'd do the change from A2017 to A2017G to get round the annoying junk which came with the Chinese version, and also avoid the Google Play Services problem I came across. It may not be do-able but I thought I'd read it was.
I guess in addition to telling me the steps, telling me exactly which file versions to use would help a lot. I promise to keep notes!
I don't mind which firmware, so long as it works reliably and so long as I can preferably put a G version on it.
of course it's doable, the thing is that you'll need to unlock the bootloader in order to.
If you had trouble with Play Services then it's most probably on chinese firmware, finding out would be as easy as going to Settings, then About phone
The boot loader is still unlocked from when I managed to do the previous upgrade. That took me quite some hours, and it was more by luck than judgement that I got a result. This time I want to better understand what I'm doing.
Not sure what I'm looking at for the firmware, isn't it the versions I quoted above? But the menus (mostly) are in Chinese at start up, and I had to load Google Play and Play Services from the ZTEYR store so I'm pretty sure it is on Chinese firmware.
So if it is, do I just need to upgrade the firmware then the ROM (is that the terminology?). If so which versions would I use?
Ta
Geoff
EDIT I missed the kernel version - which is 3.18.31
OK so I've spent more time reading. I'm coming to the conclusion that I don't need TWRP and I don't need to update my Chinese bootloader, does that sound about right?
Is it right that all I need to do is
- find a G firmware zip file <<< may have incorrect terminology here, would appreciate a pointer to a valid download as I have many but not sure they are the right type of file
- put it on an SD card named as update.zip
- boot into recovery mode
- choose "apply update from SD card"
And, assuming I have used a stock version, will it then update to the latest version (hopefully Oreo) once it's started?
Do I need to do any formats or wipes anywhere in the process? I already have a backup of my stuff, done with AXON7Toolkit.
And can you recommend a version of firmware to go to, or does it not really matter as it'll update itself anyway?
UPDATE: MiFavor UI is v5.0
OK, so there is no real short easy answer to this.
I've used the updates from ZTE since I've had the phone until I soft bricked it.
Zte offer updates similar to this.
Eg: B06 to B08 or B08 to B09 and B09 to B12
The update has to be done in stages.
Some updates you can copy to the internal SD card then go settings > system > update, your phone should detect the updates and tap install.
Some Zip files can be done the same way after changing the file name to update.zip or Ota.zip depending on the instructions.
Some zip files have the update within the Zip so it needs to be extracted.
Make sure you have the correct version software and correct version for your phone.
After the update is done all the data etc will be still in place unless you reset your phone.
All I can say is research, research, research.
Btw if your bootloader is unlocked some updates will fail.
I hope this helps
PS: you can use the method you described as well, just follow the instructions carefully.
In most cases there is no need to wipe or format unless you are using a custom ROM etc.
Excellent, thanks.
Going back a post or two - I re-installed Google Play services but still have problems. Before a reboot it appears in the list of apps, and Play opens, but the sidebar comes straight in and behind there is a message "Error while retrieving information from server [RH-01]" . After a reboot it is no longer in the list of Apps (even when expanded to include System apps), and Play just opens and closes real quick.
So I found a thread which led me look in Settings in Play Store at the Play Protect Certification, which says the device is not certified. So I downloaded the related app and ran it, which gave me a code which I put in web page then entered the stuff into my phone but still no joy. I suspect this is causing the Play problem and I think it'd be due to trying to use Google product on a Chinese firmware (again I'm not sure my terminology is right - I mean whatever the software is which throws up the initial boot screen).
So I think I need to get off the Chinese firmware at the same time as going to a G version, and I'm even less clear on how to replace the firmware than the rest of the process - what files and how it's done.
Going back to the more recent post (Syberclone), as I have already wiped my phone I'm not concerned about keeping data. I understand about doing this is steps - I hadn't thought of doing it that way but it seems very sensible.
I found a post by Raystef66 with loads of links to software - including A2017X_B15_Universal_Bootloader.zip. Does this replace the Chinese firmware and would it work with all zipfiles? How would I apply it? (I was using Axon7ToolKit the other day and that looks quite impressive).
I am still confused over the different types of files and the naming conventions but it's slowly making more sense. Appreciate all advice.
Thanks
Geoff
Personally I use Edl packages much easier imo.
I use Miflash or Edl tool by @djkuz
I have a bad flash help page that explains the process.
The bootstacks etc are mainly for custom ROMs, if you are just looking a factory firmware, Edl's are much easier to install without worrying about bootstacks, twrp etc.
My last Edl update was from Nougat (Chinese Rom)
To Oreo A2017G I had to factory reset after the install though.
Thatnks. Today I've done a fwe more hours reading, literally. This is taking all my time!!
Anyway I decided to follow your advice and found a full EDL of Oreo, which I applied. (ZTE_A2017V3.0.0B17) and the phone is still working, and I've not lost my apps.
However I still have the problem that Play Services won't run. I've upgraded it, followed a few troubleshooting guides, used different versions ( - should I be using the 64 bit one??) but still no joy. If I could only get that going I'd stick with the Chinese firmware. It is looking to me like it can't sync, though whether that's a cause or an outcome I'm not sure. Not unexpectedly, a number of apps will not run as a result.
I haven't done a factory reset yet, I thought I'd ask here first to see if that is likely to fix it or whether anyone has any better ideas.
Despite the time this is taking I'm enjoying learning and am grateful to you all for the responses.
The play store link "device not certified" will happen when you change a ROM from its original.
So I have an A2017G, when I run any other ROM it will show "device not certified" because the link between the phone and the software isnt in sync.
When I was running the beta Oreo from the Chinese my device always had this issue and NFC does not either usually.
There is a play store app version which will work as it should however the certified is still a problem without a work around.
When I installed the G version Oreo to my device the certification is back.
I'm miss some of the Chinese ROM animations tho.
Anyway I hope this helps
I am using an A2017 ROM on an A2017. I've not changed anything else. Maybe I need to update the boot stuff (firmware?).
What I'm seeing is that Play Services always needs to be manually enabled, and seems to drop out and require re-installation sometimes. So I have an apk on my internal memory for quick access.
I'm not sure that the "device not certified" is a cause or effect really.
So I have an apk on my internal memory for quick access. It's the latest non-beta 64bit version for Android 8 - should I try a specific one, e.g. is there likely to be a specific one which matches the ROM? (An older non 64 bit one seemed to give much the same problem)
I'd put up with the problem except I can't run some Google stuff at all (Play Store for instance), and some other stuff is compromised (e.g. I can't get into Waze on my usual ID, I'm guessing Play Services plays a part in authorizing). And I can't install some stuff I'd like.
And I'd still be interested to know which bits require upgrade to go to a G version, if it is do-able and would run trouble free.
There was a play store app that worked on most ROMs.
You are on Oreo now yes?
There was a link on one of the Android pie ROMs that I used, it worked fine.
If you are still having issues you can use an app called Yalp that works like the play store.
I've used it on custom ROMs when the play store app refuses to work.
Yes, Oreo now.
I've put YALP on and that looks pretty good. I now seem to have most things working, and those that aren't I can probably live without.
I use a network tool called FING which reports my phone details, and I think it's incorrect but it's saying in one place it's a A2017U which I don't think is right. But now I am more comfortable with EDL and stuff I'm going to continue to fix this properly but the urgency is now not there. I was thinking if I couldn't fix this I might have to buy a new phone on black Friday!! So thanks for your help.
I'm still not really quite sure why I get Chinese characters at start up and what files I need to change to out a G firmware on, if that is what is wrong, and if it's do-able. I think if I knew how to do that then I could put on a G firmware and matching ROM and I'd be in business!!
The same page offered me F-DROID which seems to offer a whole load of different free apps. Maybe they don't have ads? Anyway I'll have a look.
Anyway, again - thanks!!
Geoff
Geoff I'm glad I could help
I was running the Chinese Oreo on my phone and after selecting English in setting some parts of the ROM were still in Chinese, even some notifications.
I converted to the A2017G Oreo update when it was released.
I miss some of the features in the Chinese ROM tho.
So... without wishing to prolong this... your phone was Chinese (as mine was) and you are now running a Global version and all you upgraded was the ROM? And are you able to use the Play Store and you don't have any issues running apps I - and can you run, say, Google Maps?). Is your bootloader still unlocked and if so is the menu at boot time still in Chinese?
Or have you upgraded something other than the ROM?
I actually have an Axon 7 A2017G here in Australia.
I soft bricked it when I accidentally made a mistake flashing a ROM.
I searched for a suitable stock firmware but I could only flash the Chinese Oreo Beta. It had to be modified to run on my device until the Oreo package for my A2017G had been uploaded.
I've now running the proper software for this phone.
Thanks.
Another couple of hours and I have made a Major breakthrough! I went back over all my notes and checked what i'd done and one thing I hadn't remembered doing was setting the Pay Store to Autorun. So using the Mi-Assistant I have done this, and most of the stuff which wasn't working now is. I am still working on why OK Google won't work, but the list of things I might have to live without is now quite short!! The one major benefit is that my battery life seems to be greatly increased. Boot time is also much quicker which is a bonus but not critical.
Nice, yes battery life is improved, actually the Chinese Oreo Beta has a better battery life than my current Oreo.
I could get up to 4 days out of the Chinese ROM, my current ROM can manage just over 3 days at best.
I have battery saver mode on but not ultra battery saver.
I hope this has been a good learning experience for you?
"I hope this has been a good learning experience for you?"
For sure it has. Back in the days when I was 3rd level computer techie, the best learning came from other experts and from being thrown in the deep end, rather than what they taught you in the classroom!
I have been an XDA member/ reader for over 10 years but this is the first time I think I have ever asked a question.
I have a Tab A 510 WiFi that I rooted back in Dec 2019. Since then I have done no other updates except to my installed apps. I want to basically unroot it and install updates that are desperately needed. I then want to reroot it correctly. Plus install a Android ROM that is a much newer version. When I originally rooted, I am pretty sure I didn't get the process correctly done. I have been running it with TWRP, and MAGISK, installed but I am pretty sure I didn't use the correct kernel or build. The tablet has been slowly loosing app compatibility with newer apps. I really just want to start fresh. I also want to remove system apps that are unneeded.
Is the best way to just reset the device, then let it update to the most current security and Android version then reroot it? I have rooted multiple devices in the past but for some reason on this tab A, I have been intimidated by kernel versions and build numbers so I have just ignored any OS updates and have kept the option in settings to automatically update turned off. And have really done nothing with TWRP. I am pretty sure the version is way out of date on my tablet.
Will resetting, updating to correct build and kernel and then rerooting following the directions posted work still? I just want to make sure that what I end up with is an updated and easier to manage tablet. I know how to unlock bootloader, and how to use Odin. And can follow the instructions for in the forum for rerooting. But, I have not been able to find this question answered anywhere in the Tab A forums.
Any advice would be appreciated.
Thank you
The build numbers I have is *** treble_a64_bvS-userdebug 10 QQ2A.200305.003 200314 test-keys**** my kernel is ****4.4.111# 2 Sun Mar 1 15:16:12 PST 2020 and my security patch level is from November 1, 2019. And serial number is *** R52MA0ZH01R****hope that is enough information to at least show how out of date the system is.