yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] Darkussj:
Hi everyone, I am new to this forum so excuse me if this isn't the right section to post my problem.

so I tried to change the theme of my Samsung Galaxy Ace S5830 after I install a custom ROM in it, so I installed ROM toolbox Lite and I tried to change the phone's theme from there but it didn't work, after that I searched for some apps (I thought that my phone needed those apps to apply the themes from ROM Toolbox Lite) apps like : Theme chooser ,Theme changer, Theme manager and I kept rebooting each time I installed a theme thinking that what must be done so my phone can load it. but nothing changed, so after some searching on google I found a topic in this forum that has some APK files to choose from to change the phone's theme and it must replace Touchwiz30.apk in the System/app directory and give it the permission to write , read and read but I didn't find it with that exact name ,in my case it was called TouchSpaceWiz50.apk so I deleted it and went and tried to replace it with the one I've downloaded except I couldn't give it the permission and I got an error message that says I can't change some system files permissions.

so I ended up without the file TouchSpaceWiz50.apk in my System/app directory not to mention that I wasn't able to go to the home screen.

so I turned off the phone and on again only to find out that the phone is frozen on the boot animation screen, it doesn't keep rebooting just stuck at the boot animation that keeps playing.

I was able to fix this problem by re-installing the custom ROM from my SD-Card. but the main questions is why I wasn't able to change the theme via ROM Toolbox Lite when I have a custom Rom that includes ThemeChooser? and why the other apps didn't work as well? and is there another way to install themes? because I wasn't able to find any. and thanks in advance. :)

I am sorry if my post is so long I just wanted to explain what happened in details.
[T-Mobile Note 7  Guides, News, & Discussion] RoidDroidVoid:
I've opened this thread so that there can be a

CLEAN

thread for devs to discuss the development of a kernel mod to the Sprint userdebug firmware to allow a hybrid T-mo/Sprint ROM to be built that preserves T-Mo features such a Wi-Fi Calling and VoLTE.

If you are not a dev currently contributing to this particular effort, please refrain from posting in this thread and use the "ALL THINGS ROOT..." thread here for all other root related discussion.

See Post #2 for ORDER OF EVENTS, CURRENT STATUS AND REQUEST FOR HELP.

See Post #3 for a compiled summary of everything we know and have tried as of this moment.

Let me know if there is anything that you think I should add to this post that might help keep this process on track.

I believe this goal to be attainable but it will likely require some teamwork and collective imagination.
[T-Mobile Note 7  Guides, News, & Discussion] RoidDroidVoid:
ORDER OF EVENTS, CURRENT STATUS AND REQUEST FOR HELP:

​

1. T-Mo Note 7 ships with locked bootloader.

2. freeza manages to supply Sprint Note 7 users with a userdebug firmware that allows root access to be gained on the N930P

3. ethanscooter posts the following info in which he shares his experience that the N930P userdebug flashes normally to the N930T, allows boot and root:

5. The loss of WI-Fi Calling and VoLTE as well as other T-Mo specific customizations (Visual Voicemail?) is identified as a major drawback of using the Sprint fw.

Edit: Other issues as reported so far: Samsung Apps cannot be updated, any Bluetooth pairings that are made must be re-paired after every reboot
​

6. A T-Mobile engineering build is being sought to no avail as of yet. This would resolve the primary issue by allowing us to use a T-Mobile FW with the appropriate T-Mobile modifications for WiFi Calling and VoLTE. (Not sure yet what might be causing the issues with Samsung apps and Bluetooth)

7. In the absence of a Tmo eng boot, several devs are organizing to find a solution. The current idea is to dd a modded kernel after flashing the Sprint fw which would (hypothetically) remove the validation checks that prevent flashing modified images. Then build a deodexed T-Mobile build with the modded kernel and su included.
​

Progress has been somewhat limited up until now. Partially because most devs have been working quietly in their own silos and communicating ideas and knowledge has been a challenge with the previous threads becoming dominated by chatter rather than the facts as they have and are being discovered.

The other hindrance has been that many devs who are keen to work on this issue are without a device such as Rx8Driver and Chainfire.

ATTENTION:

ANYONE THAT IS NOT A DEVELOPER BUT IS LOOKING TO CONTRIBUTE TO THIS EFFORT, PLEASE DONATE TO THE TWO DEVS MENTIONED ABOVE SO THAT THEY CAN HAVE A DEVICE WITH WHICH TO WORK. ALSO, SINCE I KNOW YOU ARE ALL EAGERLY POURING OVER THESE THREADS, KEEP AN EYE OUT FOR OTHER DEVS INTERESTED IN HELPING THAT MAY NEED A DEVICE AND TRY TO HELP THEM GET THEIR HANDS ON ONE.

ANOTHER OTHER WAY TO CONTRIBUTE WOULD, OF COURSE, BE TESTING. BE WARNED THAT NO ONE HERE AT XDA ASSUMES ANY RESPONSIBILITY FOR ANY CODE THAT IS PROVIDED TO TESTERS OR USERS AND BRICKING YOUR DEVICE IS A VERY REAL POSSIBILITY.

THOSE INTERESTED IN TESTING, PLEASE START A SEPARATE THREAD IN DEV SO THAT GUINEA PIGS CAN ADD THEIR NAME TO THE LIST OF WILLING TESTERS. (PLEASE KEEP THAT THREAD SIMPLE AND TO THE POINT)

In Post #3, I will do my best to provide a straight-forward compilation of all we know and have tried as of this moment.
[T-Mobile Note 7  Guides, News, & Discussion] RoidDroidVoid:
WHAT WE KNOW (OR AT LEAST THINK WE KNOW):

The following is the list of details that we currently know regarding the T-Mobile Samsung Galaxy Note 7 (SM-N930T) and its locked bootloader including concepts, ideas and loosely confirmed information:

FROM CHAINFIRE ON G+ (regarding SU challenges and some work-arounds):

FROM

STILL WORKING ON THIS - NEED TO TAKE A BREAK - FEEL FREE TO BEGIN USING THIS THREAD FOR DEV RELATED DISCUSSION ONLY

REMINDER: See above link to "ALLTHINGS

ROOT

..." thread for open discussion that is not directly related to solving this issue. Thanks!

​
[T-Mobile Note 7  Guides, News, & Discussion] RoidDroidVoid:
Post #4

RESERVED
[T-Mobile Note 7  Guides, News, & Discussion] Rx8Driver:
This is a spectacular thread with solid information and an accurate description of our intentions....i want to state that although i appreciate any efforts made that contribute to obtaining a development device I CANNOT IN GOOD FAITH MAKE ANY PROMISES OF RESULTS NOR CAN I SUPPLY A TIME FRAME SHOULD A DEVICE BECOME AVAILABLE. That said, in time I'll have the device no matter what (assuming i don't just buy an Intl F variant- although that's unlikely since $150 on the barrel head is much more palatable than $900 when i literally just had a baby 4 days ago... plus i work 50hrs a week at my regular job) so i don't want folks to think if they don't contribute I'll never get the device- in fact, honestly if I buy it myself there's even MORE likelihood it'll be a T variant- because i will...

Also, be aware the Chinese model is said to be sd820 as well, and has it's own chances of being unlocked, so when everyone's pitched in to buy myself or Chainfire a device then Samsung releases a Chinese Bootloader we can use that's unlocked and solve all our problems, i don't want a bunch of butt hurt fellow members angry with me because the necessity dried up before i could produce the intended Results. I think [MENTION=309990]freeza[/MENTION] and a few other members who have known me around the forums these past few years will vouch that I'm a Stand Up Dude and truly intend to go as far as reverse engineering the T Bootloader to unlock it. Can I? Idk. Am i knowledgeable enough at this very moment to do it? Probably not. Can i still figure it out? I hope so. Will i brick the device? Good chance. Will i try my best and promise to research and learn whatever is necessary to make it happen? Absolutely.

Those are my terms. If you as an individual reading this don't 100% agree then keep your money in your wallet and wait until i can buy the device myself. That's as straight up as i can be. I'll make another promise. Should anyone donate but the total come up short of obtaining a device before i can on my own, i will leave all the donations in my PayPal and refund everyone's money. Only if enough is gained to buy a device will the money move from PayPal, and then it'll be one transaction to purchase the device using the account. If not enough is collected I'll refund everything that was donated...I'll also agree to prove with screenshots...

So again if you're uncomfortable then DO NOT SEND MONEY.

Thanks to all and i look forward to busting this whole Bootloader open! Or giving it one heck of a try if not!
[T-Mobile Note 7  Guides, News, & Discussion] DutchDogg54:
Thread moved to General

Thanks for starting something like this gentleman, but as with the bootloader thread, this is not actual development so it belongs in general. Carry on.
[Moto X Q&A] neo.dcm:
My Moto X 1st Gen (XT1052, Locked bootloader, default Lollipop 5.1.1) went dead out of nowhere. I noticed that my WhatsApp was FCing every few minutes. I ignored it, but the phone just went dead. When i pressed and held the power button, the phone went into a boot loop. I can access the recovery menu but it does not go into any of the options, just goes back to bootloop after selecting any option.

Also, i notice that the screen flashes for about half a second, every 20 secs and i can see the Android bot lying on its back with the Red exclamation and 'No command' text below it.

What's the solution to this?
[Moto X Q&A] sd_shadow:
what options are available?
[Moto X Q&A] YedanyXD:
recovery stock? Or TWRP
[ZTE Axon 7 Guides, News, & Discussion] jkuczera:
Hoping to use this thread to help members who are having bootloops/wifi/etc. issues after flashing different kernels/system images.

If wi-fi is not working (A2017U B20):

You also need the crossed out boot.img from Here

If you're using an SD card, reboot your phone to TWRP. Make sure external SD is mounted in TWRP. On your PC, in the folder where your downloaded and extracted the boot.img, type:

Code:

adb push boot.img /external_sd/b20b_boot.img

adb shell if=/dev/block/sde12 of=/external_sd/boot_backup.img

adb shell if=/external_sd/b20b_boot.img of=/dev/block/sde12

adb reboot

Please post the steps you took to end up with bootloops/wifi issues, what exact issues you are having (wifi/bluetooth/cell/boot logo) as well as which recovery (stock/twrp) you currently have installed.
[ZTE Axon 7 Guides, News, & Discussion] DrakenFX:
You and me both my friend, I created a thread like a week ago to gather info about what you are saying here, but seems like they don't want to participate for a fix.

http://xdaforums.com/axon-7/help/post-current-boot-issues-read-posting-t3447987
[ZTE Axon 7 Guides, News, & Discussion] jkuczera:
Well, we got two sub-forums covered now. Let's see if anyone bites.
[ZTE Axon 7 Guides, News, & Discussion] thjoca3:
Well I did Draken's B20_Boot TWRP Backup Xposed+Root Edition Provided by DrakenFX , which cause a no boot situation, with no access to recovery. used tenfar's root without bootloader unlock to flash boot and recovery, then Draken's software image booted but no wifi. Still haven't fixed that one yet.
[ZTE Axon 7 Guides, News, & Discussion] jkuczera:
[MENTION=1900557]thjoca3[/MENTION] do you know what system.img file you used? Is it a b20_boot system.img?
[ZTE Axon 7 Guides, News, & Discussion] thjoca3:
That I'm not sure, it's whatever system is packaged with Draken's backup
[ZTE Axon 7 Guides, News, & Discussion] jkuczera:
[MENTION=1900557]thjoca3[/MENTION] here are my current boot and system files. They are both b20_boot.

https://drive.google.com/folderview?id=0Bx04wovXfQGeYlpqSHhvS3Noc28
[ZTE Axon 7 Guides, News, & Discussion] Pollito788:
Exactly what this thread says to do...http://xdaforums.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895

I downloaded the TWRP backup from that thread, and then downloaded Tenfar's tool from his own thread. I used his thread(Tenfar's) for the acquiring of the tool, as well as downloading a2017U B20 (since B20_boot unlocked is crossed out?). I then flashed the boot and recovery .img(using Tenfar's tool), then restored to the TWRP backup in TWRP provided by rcriderz. Afterwords, my phone booted up, but did not have Wifi access. That seems to bethe only feature missing... At this point I think I'd just rather wait for the first cyanogenmod release, but this is how I got to this point. I did this in the first place because I bricked my device by using GravityBox and rebooting so the settings would kick in. Device info: US Variant, unlocked bootloader via ZTE request form, TWRP installed
[ZTE Axon 7 Guides, News, & Discussion] thjoca3:
maybe not totally sure how to use this, but I can't seem to get anything bigger than 5gb or so to load on to my sd card, or extract anything that size onto the sd card.
[ZTE Axon 7 Guides, News, & Discussion] DrakenFX:
I know this is not my thread but having it little more info in the following form will help a lot lIssue

- Model :

- Previuos Version :

- Current Version :

- Issue / Problem :

- How happen :

That will help a lot figure things out.
[ZTE Axon 7 Guides, News, & Discussion] thjoca3:
zz
[ZTE Axon 7 Guides, News, & Discussion] jkuczera:
The problem is likely the format of your SD card. It needs to be in a format that accepts files > 4GB. I believe exFAT or ext4 should work.

http://kb.sandisk.com/app/answers/d...rger-file-to-a-usb-flash-drive-or-memory-card
[ZTE Axon 7 Guides, News, & Discussion] thjoca3:
Well found an sdcard reader and was able to get files to the sdcard. Restored with warofhero's system image, and my stock boot and recovery, no change with wifi. Also loaded the b20_boot with stock recovery and no wifi.
[ZTE Axon 7 Guides, News, & Discussion] jkuczera:
Recovery should have zero effect on the outcome of Wi-Fi functioning during normal boot. I believe the issue with wi-fi is a mismatch of boot.img and system.img.

Do you know if warofhero's system image a b20 or a b20_boot?
[ZTE Axon 7 Guides, News, & Discussion] thjoca3:
I tried both on his, neither worked for me. Then I did this

Download rczrider's TWRP System backup, restored in twrp with the boot from tenfar's post - a2017u B20 http://d-h.st/LqR5 (modified from [MENTION=6699128]rczrider[/MENTION]‘s backup real stock b20 boot.img) and my wifi is back.
[ZTE Axon 7 Guides, News, & Discussion] DrakenFX:
That's awesome, glad you got it fix.

So you have a full operational device now? Hope this solution help others.
[ZTE Axon 7 Guides, News, & Discussion] thjoca3:
Yes, appears everything is working now, with the modified boot.
[ZTE Axon 7 Guides, News, & Discussion] peramikic:
I posted this somewhere else as well but here it goes again.

The booti.img and system have to match and be from the same set. So if you use stock B20 (not _Boot) boot.img then you have to use the same /system. In this case this would be

For locked bootloader use rcrider's boot(no root) + system or tenfar's boot(root) + rcrider's /system

For unlocked bootloader you would use B20_Boot boot+system like one jkuczera posted upthread

Do not mix and match files form different region's either, these are both from US A2017U model.

When bootlooping, there are multiple reasons why this could be:

- wrong modle boot.img

- unrotted boot.img and modded recovery or system while BL is locked

- /system flashed with unsuported SU or Xposed

- boot.img flashed with unsupported kernel/ramdisk patch

- junk in cache/dalvik

- junk in /data

- /data encrypted with key which cannot be decrypted due to altered cryptochain

The way to fix it most of the time is to flash proper boot and system and wipe all user partitions. tenfar's tools can restore boot and recoveries very painlessly. TWRP can take care of the /system and wipes. The only unknown at this point is if the system image can be flashed in TWRP in a OTA consistent state on the B20 version. This should be doable by running TWRP in read only mode but i do not know if that will still let you restore system. It also has to be "System Image" backup (6GB one) from TWRP and not just the /system partition for block consistency. Hope this helps sort out the problems. I might try all this out once i am certain I'll keep the phone, it is currently in trial mode for few more weeks. The full "System Image" for B20_boot was posted here http://xdaforums.com/showpost.php?p=68248798&postcount=53 , (edit: jkuczera's is also System Image and same size). maybe rcrider can put up one for B20 Stock on his MEGA
[ZTE Axon 7 Guides, News, & Discussion] jkuczera:
Thanks for clarifying [MENTION=1340661]peramikic[/MENTION].

For the quote above, I don't understand what you mean by OTA consistent state. Do you mean a state in which OTA would still occur even after bootloader unlock?
[ZTE Axon 7 Guides, News, & Discussion] peramikic:
This probably goes more for the B20 folks, since i doubt we will see an OTA from ZTE that will work on B2-_Boot. But in essence the System Image backups are supposed to produce bit level mirror image of the /system partition so that OTA update will properly hash it. Chances are very high that when you restore regular ext4 backups, while the files are the same they will not be laid out on the partition the same way. That's why /system is strictly read-only now. Even just enabling that RW access in TWRP can alter it. For instance the image you and swehes have posted differs slightly in first 4MB of the files (his has some stuff while your is all 0s) and then again in offset 69bd000 or so where one file is missing from your's i think it's the recovery-from-boot file. It is likely TWRP removed it so it would not get flashed over after reboot with stock recovery, if you allowed RW access to system.
[ZTE Axon 7 Guides, News, & Discussion] TeutonJon78:
Deleted
[ZTE Axon 7 Guides, News, & Discussion] Flapjack:
[MENTION=1340661]peramikic[/MENTION]:

Thanks for posting this very scientific breakdown as to why this is happening. I'm curious as to what your theory is regarding wifi/radio not working. The common referenced explanation is that it's a mismatch between the boot and system partitions, but I have flashed all four combinations of those with no luck (stuck at ZTE logo, or boot with no wifi).

Your post has given me some hope. I'm glad I didn't send off my RMA. I think I will try again to see if I can recover the phone before returning it.
[ZTE Axon 7 Guides, News, & Discussion] jkuczera:
[MENTION=574279]Flapjack[/MENTION], do you have the US version A2017U?
[ZTE Axon 7 Guides, News, & Discussion] tabletalker7:
anyone tried using QPST to solve this problem?
[ZTE Axon 7 Guides, News, & Discussion] peramikic:
Basically the reason for WiFi not working is that WiFi modules that are compiled with the kernel are not stored in the boot.img but in the /system partition. That pairs them so when kernel looks for the modules on system, it will not load them if the modules have been compiled with a different kernel version. if you are rooted and run dmesg, you should see the errors about mismatch in the log. So for WiFi to work boot and /system have to be from same release. So B20 US boot needs B20 US /system.

Now for the black screen, this could be several things so In case you were B20 BL locked you will want to use rooted B20 U boot.img and rcriders system for instance. flash boot and rec via tenfar's tool.

In TWRP make sure to wipe cache, dalvik, data and to format them as well as /system. Then restore /system and wipe /data /cache /dalvik one more time. This should get you to bootable with WiFi.

Going back to stock with with non-rooted is a little trickier probably and i m not sure if it would work. What you need is the "System Image" type TWRP backup from vanilla B20. Problem with switching back to stock boot.img is that dm-verity kicks in and checks signatures of partitions. If they don't match, no boot. The "System Image" is supposed to backups system in a way that restoring it preserves the signature. It's supposed to include boot and recovery as well, but those should be restored via tenfars tool with supposedly same signature (there is actually some file padding in dumps, but lets assume that they get ignored on flash back or don't affect the signature). In this case you would do the wipes like above, then get TWRP to mount system as read-only (you might need to flash stock recvery and the back to TWRP to get the prompt). This is needed to avoid TWRP modding the /system in any way upon exit. The restoring of "System Image" should (BIG IF here) still work since it's a dd copy and doesn't care. So after restoring system, flash the stock boot and recovery to the phone with tenfar's tool. Immediately after that reboot into stock recovery (do not boot the phone normally) and do factory wipe. If it all worked as expected you should be able to boot into all stock unrooted with working WiFi.
[ZTE Axon 7 Guides, News, & Discussion] Flapjack:
Yup. :)

Thanks for the advice. Currently, the phone has the stock /system, stock boot, and stock recovery, but does not have wifi working. I have even relocked the bootloader (since I was going to return it).

What exactly is not stock, at this point? Is installing P996A01B20Fastboot_ssl.zip via the SDcard (jkuczera's guide) simply not reversible? If not, what has been permanently altered? Doesn't that zip just patch the kernel (which is on /boot, right?)?
[ZTE Axon 7 Guides, News, & Discussion] peramikic:
The process of unlocking the BL itslef might alter some partitions on the phone permanently and not reverse them after re-locking, but it should not have anything to do with WiFi. You mentioned that you have wifi with rooted B20, but not with stock. Is the stock boot.img you are running B20 or B20_Boot? If the /system is B20 (not _Boot) then boot.img has to be B20 as well. Mind you both B20 and B20_Boot are stock but different versions.
[ZTE Axon 7 Guides, News, & Discussion] Flapjack:
I'm trying to get the phone back to where the system is modified, the B20_Boot is installed, TWRP is installed, and is rooted. No luck. The only thing that affects any visible change is unlocking/relocking the bootloader, and changing between stock and TWRP recoveries. I've tried flashing P996A01B20Fastboot_ssl.zip (from both TWRP and stock recovery.... from internal and external sdcards), but I get the error 8, file "has unexpected contents".

I'm having a hard time keeping track of who's boot files and system images are which. What exact files TWRP and root? If I can get it back to where TWRP is installed, and wifi works, then I will NOT be installing SuperSU 2.67, lol.
[ZTE Axon 7 Guides, News, & Discussion] DrakenFX:
ok,

1- what was your problem????? sorry is hard to keep track some of the user current issues

2- as far as i know base on you post YOU ARE B20_Boot Right?

3- with or without TWRP?

if you are B20_Boot and looking for boot+system

i have uploaded this http://xdaforums.com/showpost.php?p=68206051&postcount=4

but i really don't know what your problem is.