I want to try and flash a single patched .apk from the OTA update everyone else got except T-Mobile (I am looking at the AT&T update specifically). Yes, I could wait until we get ours, but I also want to learn. For what it's worth, I want to try and flash the patched bluetooth.apk to see if it fixed my bluetooth issues.
First off, is it even possible to flash or push a single patch file from an OTA update like that? If not, can I somehow decompile the patch and the original .apk, combine, and flash that?
Second, how can I deodex it for my ROM? Most decompliers I have seen don't recognize the apk.p format, only .apk. Obviously I can change the extension, deodex it with a tool, then change it back, but I don't know if that's "correct".
Any input on this would be great! Thanks in advance!
All,
my sgh-i747 WiFi doesn't appear to work. under settings> WiFi slider (OFF)> slide to on (remains off)
next goto WiFi setup screen: no devices listed, buttons at bottom of screen dim/greyed out.
history:
phone was bricked by a forced ATT update. I finally did a rom update/reinstall to push a working stock kernel kitkat 4.4.2
thx
Rob
ALSO i need working links to Lollipop for sgh-1747 using oden
PS: I do ROM , hardware and software updates on data storage systems with petabytes of storage. BUT THIS PHONE MAKES ME FEEL STUPID....
My Hats Off to All Of You Who Hack, Play, or Make Mods for the Phones.
Boot image not matching firmware on your phone can cause wifi to not work. The kernel doesn't have the what it needs to work with the radio you have installed. It is a fairly typical stock rom problem. Custom roms typically have broader support instead of being targeted at a specific firmware.
First step is to figure out what exactly you have on your phone now. Need to know bootloader, modem, and boot image versions since this phone is finicky. Hard bricks are possible, so don't do anything hasty. There's an app in the Play store called phone info samsung by vndnguyen that helps with that. Install it and see what it says you have for bootloader and modem/baseband. Also check in Settings -> About and see what kernel version you have (the app might tell you that too, it has been a long time). Report that all back here and it will help with how to fix it.
Alternately if you don't want to mess with the app enter this in a terminal app or adb shell:
Code:
getprop ro.bootloader
getprop gsm.version.baseband
You won't find an Odin package for lollipop. Samsung never updated this device past kitkat. Anything lollipop or newer would be a custom rom, and those are all custom recovery flashable zips, not Odin.
jason2678 said:
Boot image not matching firmware on your phone can cause wifi to not work. The kernel doesn't have the what it needs to work with the radio you have installed. It is a fairly typical stock rom problem. Custom roms typically have broader support instead of being targeted at a specific firmware.
First step is to figure out what exactly you have on your phone now. Need to know bootloader, modem, and boot image versions since this phone is finicky. Hard bricks are possible, so don't do anything hasty. There's an app in the Play store called phone info samsung by vndnguyen that helps with that. Install it and see what it says you have for bootloader and modem/baseband. Also check in Settings -> About and see what kernel version you have (the app might tell you that too, it has been a long time). Report that all back here and it will help with how to fix it.
Alternately if you don't want to mess with the app enter this in a terminal app or adb shell:
Code:
getprop ro.bootloader
getprop gsm.version.baseband
You won't find an Odin package for lollipop. Samsung never updated this device past kitkat. Anything lollipop or newer would be a custom rom, and those are all custom recovery flashable zips, not Odin.
Click to expand...
Click to collapse
Thank You
jason2678 what you said makes perfect sense to me. like needing a VIN # for a 2002 Toyota to figure out what water pump or alternator because they used 6 different versions of each, LOL
so i would like to use 5.1 lollipop which is a custom ROM i believe, if you can suggest one i will defer to your judgement
but as a fallback suggest a kitkat ROM as well
bootloader I747UCUFNJ1
BASEBAND I747UCUFNJ1
KERNEL VERSION:
3.4.0-1514807
[email protected] #1
32-bit
modem msm8960
please and thank you
respectfully
123RobH
At NJ1 you're not on the latest bootloader and modem, but you're close enough. And your bootloader and modem match. I wouldn't mess with it. You'll be able to run all the latest custom ROMs on that, no problem.
If you want lollipop, look around the development section here. I'm not sure if you'll be able to track down a lollipop rom download linked to XDA. You might have to poke around old uploads for d2att on androidfilehost.com for 5.1.1 roms. I'm pretty partial to slimkat stable 9 on this phone, and it runs fine on NJ1 firmware too.
Oct-Os is probably the most actively supported rom currently. They've moved on to nougat these days. You'll be able to run it on NJ1 too. You might want to give it a shot.
Track down a rom and matching gapps. Then full wipe and flash them with TWRP recovery. If you run into any trouble or have any questions, just ask. I'm pretty certain once you get a custom rom on your phone your wifi problems will go away. Stick to lollipop, marshmallow, or nougat and you'll be fine. Even newer KitKat ROMs will be OK on NJ1.
Hello everyone, as you all can see freshly new in here as a member, have been following up and using as a resource to get my knowledge improved. I have been on t-mobile devices long time, but finally found a good deal and got an unlocked N920A using with t-mobile. noticed that won't be able to receive OTA updates on an unlocked device when using with another cellular than the device's original one. I don't want to root or superuse just to make sure I do not brick the new baby.
Could you guys help me out how can i update to marshmallow without rooting the device?
odin or adb sideload?(not sure would that require any superuser or rooting)
can I just pick any n920a (att) version/build or does it have to be in the sequence (whichever is the next or after the N920AUCU1AOGG)?
Thanks in advance!
yalch said:
Hello everyone, as you all can see freshly new in here as a member, have been following up and using as a resource to get my knowledge improved. I have been on t-mobile devices long time, but finally found a good deal and got an unlocked N920A using with t-mobile. noticed that won't be able to receive OTA updates on an unlocked device when using with another cellular than the device's original one. I don't want to root or superuse just to make sure I do not brick the new baby.
Could you guys help me out how can i update to marshmallow without rooting the device?
odin or adb sideload?(not sure would that require any superuser or rooting)
can I just pick any n920a (att) version/build or does it have to be in the sequence (whichever is the next or after the N920AUCU1AOGG)?
Thanks in advance!
Click to expand...
Click to collapse
You can just flash in any build...you need to follow the sequence from your current build number...try to look around for the Odin file from lollipop to nougat...if you don't see that, look for the individual builds from lollipop to marshmallow...then Odin to nougat...there's definitely an Odin file from marshmallow to nougat...there should be one from lollipop also...you just have to search for it...
What build are you on?
nedo_iv said:
You can just flash in any build...you need to follow the sequence from your current build number...try to look around for the Odin file from lollipop to nougat...if you don't see that, look for the individual builds from lollipop to marshmallow...then Odin to nougat...there's definitely an Odin file from marshmallow to nougat...there should be one from lollipop also...you just have to search for it...
What build are you on?
Click to expand...
Click to collapse
I am on Build number LMY47X.N920AUCU1AOGG.
So I assume I should go for the next update which is build number LMY47X.N920AUCU1AOH5?
yalch said:
I am on Build number LMY47X.N920AUCU1AOGG.
So I assume I should go for the next update which is build number LMY47X.N920AUCU1AOH5?
Click to expand...
Click to collapse
Yes you should...
GDrive link to my collection (captured using a XT1683 - RETBR channel): https://drive.google.com/drive/folders/1UIfyIox6RMGT6m4YZaNrazryEoFnKGlS?usp=sharing
I cannot guarantee these packages will work on your G5 Plus. Only try using them if you are absolutely sure their are compatible with your phone, as it may be possible your device won't be able to be updated by future OTAs if you sideload the wrong zip. I'm posting these for research purposes - if anyone would like to capture the OTAs from their own G5 Plus we could compare them and maybe find out which variants receive identical firmwares.
My device is the Brazilian variant (XT1683) with 32GB/2GB, NFC, TV, dual sim and no compass. By comparing one of my files to a package from another thread, it seems this variant receives identical OTA packages to ones in the RETIN channel.
Anyone can capture their own OTAs! Just run adb logcat from a command prompt window (assuming you have ADB installed), run the check for updates on your phone and begin downloading the package. Copy the logcat contents to a text editor, search for "handleDownloadServiceRequest:downloadUrl" and access the URL with your browser. You may rename the downloaded file afterwards - look for "fileName" or "Blur_Version" in your logcat to get the correct filename.
I have build NPNS25.137-93-8
I'm trying to get past a soft brick. I had an unlocked bootloader.
Can I fix this with fastboot (I can get to both the bootloader and into TWRP, but my TWRP backup fails to write to the system..
salsolomon said:
I have build NPNS25.137-93-8
I'm trying to get past a soft brick. I had an unlocked bootloader.
Can I fix this with fastboot (I can get to both the bootloader and into TWRP, but my TWRP backup fails to write to the system..
Click to expand...
Click to collapse
You can but you need your actual firmware and I haven't seen any NPNS25.137-93-8 firmware uploaded until now.
There are some users who say they used an older firmware to capture OTA's but imho there's a risk of softbricking.
There's a NPNS25.137-93-4 firmware around, it's up to you to use it: https://drive.google.com/file/d/165BmLRzGiGF_Veo0AuHgUp6jpn01l9UD/view
Sent from my Moto G5 Plus using XDA Labs
Can someone please point me in the direction to Unlock Bootloader and Root the OnePlus 9 Pro T-Mobile Version? I had the Global US Unlocked OnePlus 8 Pro and it was simple. Thank you in advance!
How To: Unlock the T-Mobile Bootloader
Hello all, this is a quick and simple guide to unlocking your T-Mobile locked bootloader. Just a reminder: unlocking the bootloader will wipe your data. The instructions here will apply to all T-Mobile OnePlus devices. Unlock your SIM. Some...
forum.xda-developers.com
Have u received token from tmo
Alright, my bootloader is unlocked now, but I'm not sure how to root at this point. My software version is 11.2.2.2.LE54CB. I can't find that last part (LE54CB) anywhere for download, so I'm not sure where to get my boot.img from. Anybody have some ideas?
Since there's no TWRP for this phone (yet), you have to get the boot.img file and use Magisk to directly patch it. I'm about to embark down this path, I got the T-Mobile version, also on 11.2.2.2 and I just got the bootloader unlocked. Now I need to root it.
glitchsys said:
Since there's no TWRP for this phone (yet), you have to get the boot.img file and use Magisk to directly patch it. I'm about to embark down this path, I got the T-Mobile version, also on 11.2.2.2 and I just got the bootloader unlocked. Now I need to root it.
Click to expand...
Click to collapse
Please let me know if you find a way. I'm super hesitant because of this other thread but I'm not willing to stop using my rooted OP7pro until my 9 is rooted.
I'm about to use https://forum.xda-developers.com/t/...ot-image-and-apply-root-to-the-phone.4263811/ djsubterrain's guide. Seems straight-forward.
1. I downloaded the Payload_Dumper program
2. I grabbed the official ROM from OnePlus's support site (https://www.oneplus.com/support/softwareupgrade/details?code=PM1617074857015) which is the same version my phone is already running.
3. I unzipped the OnePlus9ProOxygen_22.O.05_OTA_0050_all_2103242259_3611e0858f954e7d.zip file I got from OnePlus and there is a payload.bin file
I have to reboot out of linux and into my Windows partition in order to do the next part. But the Payload_Dumper program is supposed to extract a "boot.img" file from the payload.bin; I copy the boot.img file to my phone, into a temporary directory or whatever, and I use the Magisk application on my phone (which can be installed even if not rooted) to patch the boot.img file. I can then use fastboot to flash that image file. (Fastboot Boot rooted_boot.img) and after I reboot, I should, in theory, be rooted.
Since I didn't touch the stock recovery, I should also, in theory, be able to accept OTA updates pushed to my phone. Just normally an OTA update would "unroot" your phone, but guide has a "To retain root access after ROM/OTA update" section that I'm sure to try out next time an update is available. Worst case scenario though, the OTA update unroots me and I have to grab the new version from OnePlus's support site and go through the procedure again to extract the boot.img, patch it on the phone then flash it.
hmm. technically my phone is currently on "11.2.2.2.LE5ACB" and the one on OnePlus's support site is "11.2.2.2.LE15AA"
So there is a slight difference. Meh, should be ok. Worst case scenario I have to flash the entire "11.2.2.2.LE15AA "from OnePlus and I get T-Mobile De-Bloated.
Yeah, I had the exact same hesitation. I'm sorely curious to see how it goes for you. Because I have the OTA for the global rom, and I'm about to use the payload dumper. But if you're a step ahead of me, I'm happy to wait and see if it works for you.
jfsat said:
Yeah, I had the exact same hesitation. I'm sorely curious to see how it goes for you. Because I have the OTA for the global rom, and I'm about to use the payload dumper. But if you're a step ahead of me, I'm happy to wait and see if it works for you.
Click to expand...
Click to collapse
Happy to report it worked just fine. I was able to grab the boot.img from the "11.2.2.2.LE15AA" file on OnePlus's support site. I was able to use Magisk to patch the boot.img file. Then moment of truth..
"fastboot boot 11.2.2.2.LE15AA_patched_boot.img"
And my phone booted just fine. And it was now (temporarily) rooted. I was able to then go back into Magisk and direct-install root. Then reboot.
Magisk confirmed I'm still rooted.
So to all those curious, the boot.img from OnePlus Stock 11.2.2.2.LE15AA works fine on the T-Mobile 11.2.2.2.LE5ACB version.
I may look into using OOM or something to try and force-flash 11.2.2.2.LE5ACB onto my phone and completely De-T-Mobile this phone. I suspect I'll get OTA updates faster from OnePlus than I will from T-Mobile.
so I flashed to global coming from T-Mobile to global 11.2.2.2.
Everything went well. Until I system updated to 11.2.4.4. I realize now it didn't switch to full update and installed the incremental instead. After reboot I no longer have service.sim card is detected but again no service. Don't all the basics, so hopefully someone can help...
ryantf420 said:
so I flashed to global coming from T-Mobile to global 11.2.2.2.
Everything went well. Until I system updated to 11.2.4.4. I realize now it didn't switch to full update and installed the incremental instead. After reboot I no longer have service.sim card is detected but again no service. Don't all the basics, so hopefully someone can help...
Click to expand...
Click to collapse
How did you flash from T-Mobile's 11.2.2.2.LE5ACB over to the Global/USA 11.2.2.2.LE15AA ? The instructions say to put the zip file on the "sdcard" and then go to the update section and do a manual update. However T-Mobile conveniently removed that manual update option. So I was thinking I'd need to use msmtool or something to flash it.
Also you installed the AA version of the ROM, right? That's the U.S (not international) version, but it's generic, not T-Mobile modified. That's the one we should be flashing over our T-Mobile phones, converting them to the U.S Generic version, not the international version. AFAIK the U.S version isn't running 11.2.4.x yet, so not sure why you would get an OTA prompt about 11.2.4.x unless you'd flashed (again, how did you do this?) the international version and not the U.S version.
glitchsys said:
How did you flash from T-Mobile's 11.2.2.2.LE5ACB over to the Global/USA 11.2.2.2.LE15AA ? The instructions say to put the zip file on the "sdcard" and then go to the update section and do a manual update. However T-Mobile conveniently removed that manual update option. So I was thinking I'd need to use msmtool or something to flash it.
Also you installed the AA version of the ROM, right? That's the U.S (not international) version, but it's generic, not T-Mobile modified. That's the one we should be flashing over our T-Mobile phones, converting them to the U.S Generic version, not the international version. AFAIK the U.S version isn't running 11.2.4.x yet, so not sure why you would get an OTA prompt about 11.2.4.x unless you'd flashed (again, how did you do this?) the international version and not the U.S version.
Click to expand...
Click to collapse
flashing like always... unpack payload.bin and flash imgs files... but for some reason I have no service but sim card says tmo.... I've flashed back to stock global and problem still exist.. Also it says unable to find networks manually.. no service. this sucks 7series was so much easier..
ryantf420 said:
flashing like always... unpack payload.bin and flash imgs files... but for some reason I have no service but sim card says tmo.... I've flashed back to stock global and problem still exist.. Also it says unable to find networks manually.. no service. this sucks 7series was so much easier..
Click to expand...
Click to collapse
Using fastboot to flash the img files? There's liike 34 img files. (abl.img, aop.img, bluetooth.img, boot.img, cpucp.img, ..., ..., xbl.img, xbl_config.img). You flashed all 34?
If you're still having problems, I'm rooted and am on the stock 11.2.2.2.LE5ACB from T-Mobile. I can dd up certian partitions and provide them to you if you need. It may help you get back to stock.
glitchsys said:
Using fastboot to flash the img files? There's liike 34 img files. (abl.img, aop.img, bluetooth.img, boot.img, cpucp.img, ..., ..., xbl.img, xbl_config.img). You flashed all 34?
If you're still having problems, I'm rooted and am on the stock 11.2.2.2.LE5ACB from T-Mobile. I can dd up certian partitions and provide them to you if you need. It may help you get back to stock.
Click to expand...
Click to collapse
yes yes please that would help
Rooting is simple. Once your boot loader is unlocked head over to the thread on how to unlock the boot loader. He posted a patched boot IMG for T-Mobile. Flash it in fast boot restart open open magisk manager click direct install it will detect your boot IMG is patched it installs and reboot.
MurphSAN84 said:
How To: Unlock the T-Mobile Bootloader
Hello all, this is a quick and simple guide to unlocking your T-Mobile locked bootloader. Just a reminder: unlocking the bootloader will wipe your data. The instructions here will apply to all T-Mobile OnePlus devices. Unlock your SIM. Some...
forum.xda-developers.com
Click to expand...
Click to collapse
ryantf420 said:
flashing like always... unpack payload.bin and flash imgs files... but for some reason I have no service but sim card says tmo.... I've flashed back to stock global and problem still exist.. Also it says unable to find networks manually.. no service. this sucks 7series was so much easier..
Click to expand...
Click to collapse
Flash your tmobile modem over global.
Where to get tmo modem img?
ryantf420 said:
Where to get tmo modem img?
Click to expand...
Click to collapse
You were supposed to back your's up prior to conversion...