yashsingh1/xdaforums huggingface dataset:
[Sprint Galaxy S 5 Themes and Apps] BfunnY6t9:
MUST BE DEODEXED AND ROOTED. WORKING ON ODEX HOPEFULLY SOON ILL CRACK IT.

I managed to get full theme store access on stock deodexed 6.0.1 mm. I figured I would share with everyone.

1. I changed my build prop value of the ro.product.model from G900p to N930P. I have sprint so my model is P. Should work for all models just change only the numbers.

2. Need to have a new launcher I'm using a TouchWizHome_zero myself. Any from S6|N5 should work.

3. I found that I need 2 theme stores the first ThemeStore_3xh and a N7 GalaxyThemes. I'm using the older S6 theme Center because they don't show up with the newer N7 theme center.

4. To download I set the correct permissions for the new galaxy themes to 0755 for the folder and 0644 for the apk. (In the 3xh theme Center just rename the apk to ThemeCenter_3xh.bak and vice versa. You can only have 1 installed at a time. So after downloading your themes go in to data\overlays\json files\temp json and move them to user json. Then go in priv apps and change GalaxyThemes.apk to GalaxyThemes.bak and then go into the Themestore_3xh and change the apk back to Themestore_3xh.apk. then reboot.

Basically one app to download and the other to apply.

5. In the zip I included a TouchWiz_Zero launcher with small icons and up to 7 I believe in the hotseat, Both theme stores, theme center and an add toggles app that seems to work on mm too to add all toggles.

6. All folder permissions are 0755 and all app permissions are 0644 and the go into system\priv-apps. Just remember to toggle the 2 theme stores with 1 apk changed to .bak and one .apk.

7. Do not update theme store or it won't show your themes.. OR IF YOU WANT S6 THEME STORE KEEP A COPY OF THE ORIGINAL AND THEN DO THE UPDATE. YOU WILL HAVE TO KEEP ORIGINAL TO APPLY THEMES. IF YOU LIKE YOU CAN KEEP ALL 3 TO HAVE ACCESS TO S6,N7, AND ORIGINAL TO APPLY. JUST REMEMBER TO SET CORRECT PERMISSIONS AND RENAME THE APK NOT BEING USED TO .BAK AS THIS WILL UNINSTALL AFTER RESET. MUST RESET EACH TIME YOU SWITCH TO A DIFFERENT STORE AND ORIGINAL THEME STORE APPLY APP. IF YOU WANT S6 STORE BUILD PROP NEEDS TO BE G920P. YOU WILL HAVE TO CHANGE MODEL FOR EACH STORE

Themestore+toggles

https://drive.google.com/folderview?id=0B5AfudcH1XDQRXJoWUY0Tjdhd3c

Good luck and happy theming. Only works on icons and wallpaper so far feel free to advance farther I'm kind of a noob but I didn't see this up here so I'm sharing. As always to be safe make a backup first
[Sprint Galaxy S 5 Themes and Apps] Saahil Shaikh:
Will try it Sir t.y
[Sprint Galaxy S 5 Themes and Apps] philiptibbs:
Any way of making a flashable ZIP I'm not very good at changing permissions.
[Sprint Galaxy S 5 Themes and Apps] zfk110:
HI, I did it but only app drawer icon and wallpaper is changing, rest of icons on the home screen wont change I'm using on 910V with Marshmallow
[Android Q&A, Help & Troubleshooting] illquo:
I have a Huawei Ascend Y300-0151 and it’s quite impossible for me to unlock the bootloader on this phone because I have to request a bootloader unlock code from the official website and the only way to do that is to request it from the Chinese variant. Even though I fill out a form on their website, it still comes up with errors that I have not filled out the form correctly when every part IS in fact, filled out correctly.

I’ve e-mailed them about the error but I don’t expect a reply back, this has led me to believe I won’t ever get my Huawei Ascend Y300’s bootloader unlocked. I have, in fact, rooted the phone already, but my goal is to flash a custom ROM onto the phone but I need the bootloader unlocked for that.

My question is, what’s the easiest phone to unlock the bootloader with, because it sure isn’t the Huawei type Android phones. I’m looking into getting another phone to unlock the bootloader with, so which is yours guys favourites?
[Note 7 Questions & Answers] votum:
Tmo customer here in USA. I'm heading to Dubai next month for business, is the international Note 7 better than the US version?
[Note 7 Questions & Answers] NIKKOTUASON:
International version. I dont know about the newer Snapdragons but I read a lot of peoples in here have so many complaints about them being slow and sluggish, typing lag, poor battery, over heating...etc.
[Note 7 Questions & Answers] Moeinjeddah:
Dual sim

They have them in dual sims
[Note 7 Questions & Answers] B3501:
The Exynos international version has less lag and stutter than the US Snapdragon.
[Note 7 Questions & Answers] DuffmasterFresh:
There are already a lot of threads on this topic in this forum, please search for them, they are not hard to find.

In summary, the Exynos version of the phone is, for the most part, better. It isn't as powerful for gaming because it has a different GPU for that, but everything else is better. No bloatware from the carriers really speeds things up, no locked bootloader, no BS.
[Note 7 Questions & Answers] votum:
OK coolio. I know there are plenty of threads about it, just wanted an updated ideaafter the recall jazz
[P3300, MDA Compact III ROM Development] Synablade:
Hi all,

my TMO-MDAIIIc stopped syncing over usb cable!

I do not have any clue why!

Last thing i remember i installed the OpenVPN-Client!

I did this before on Windows Mobile 5 without problem.. So i presume it's not caused by OpenVPN!

Nevertheless i wonder if anyone has experienced this as well? I tried to connect the device to several computers without even ActiveSync recognizing it. But loading the battery over USB still works!

I also do not get a "Network Interface" if i connect the cable.

I searched several forums and find out there were similar problems, but unfortunately no solution for me...

It seems not to have something to do with the "Notification deleted" problem..

As i can see several replog.exe notifications. Also the one about RS232 Connections... Is there any other Notification missing maybe?

I also tried to play with the USB-to PC option in the settings menu. No effect.

Im totaly clueless i can sync via bluetooth, and irda, and of course wireless (gprs).

Any help would be much appreciated!

Cheers!

Syn
[P3300, MDA Compact III ROM Development] mugglesquop:
My phone stopped working the same as yours about 6 months ago. I recently found out that it was because i charge my phone in my car, which can damage the USB Interface Board in the phone. (usually when you have the phone on charge, and then start the car, causes a spike in the current).

As far as i know, the only way to fix it is to send the phone back to the supplier, who will replace the board under warrenty.

Assuming you have the same problem :)
[P3300, MDA Compact III ROM Development] Synablade:
Hi, thanks for reply!

could be true! I also charge it in the car frequently... I didn't payd a lot attention to if i plug it beofre starting the car or after...

So my last try now seems to be a "hard-reset".

I'll let you know if it fixes the problem.... If not....

I may need to "downgrade" the phone b4 sending it right?

Cheers!

Syn
[P3300, MDA Compact III ROM Development] mugglesquop:
yeh, its probably a good idea to put the original ROM back on :p
[P3300, MDA Compact III ROM Development] Synablade:
What's really bugging me is:

Why is it still "loading" the battery after damage to the USB-Circuit??

Anyway.. i did the hardreset, and guess what...

no effect... my problem now is.. if usb stopped working.. how do i flash back to original rom? :->

bluetooth? *shudder*

Cheers!

Syn
[P3300, MDA Compact III ROM Development] zaza68:
hi,

I always clear the option usb to pc.I think this wil solve you problem

settings>connections>usb to pc

Cheers,

zaza
[P3300, MDA Compact III ROM Development] mugglesquop:
yeh, same as me :) i havent been able to flash a cooked ROM to mine at all. You can change the ROM by using the MicroSD, as long as you are USPL unlocked. There is a section in the Wiki about how to do it.

You cant change the ROM using bluetooth, caus half way thru flashing, whats gonna control the bluetooth??! :D

The Battery still charges caus the battery charging circuit is seperate to the USB control circuit :)
[P3300, MDA Compact III ROM Development] patterns:
Are you guys running XP on your comp/laptop? have you turned off your firewalls? i had problems syncing on my laptop with xp, now i use my comp, but i found if i removed firewalls all was ok. if you have tried reflashing, or if you havent flashed any new software if you have tried re-sinstalling active sync, try the above, im sure its somethign simple
[P3300, MDA Compact III ROM Development] mugglesquop:
I've tried everything... WinXP, WinXPx64, Win2000, Win Vista, active sync V.3-4.5... :confused: the only answer is to send the phone back to T-Mobile, they will fix it under warrenty tho, so it aint so bad.
[P3300, MDA Compact III ROM Development] Synablade:
hi thank you all for your replies!

unfortunately i think mugglesquop is right,

the device died from power overflow from car adapter...

funny thing here is: i use a motorola car adapter all the time! no problems.. then i changed to a tmobile provided adapter! And now it seems that tis one is vulnerable to power highs! Great!

You know what ? I love t-mobile for providing "cheap" "crappy" hardware!

actually im downloading the original rom i found and i will try to flash it back via sdcard. Then i will send it in!

Cheers!

Syn
[P3300, MDA Compact III ROM Development] hutchy007:
What rom are you using ?

I had the same problem & i was using B&B4.3. It took me a couple of days of trying before i could get an activesync connection. I then flashed O2's mobile 6 Rom & hey presto everythings working again (now trying different rom). Not sure it was the Rom as only a few people seem to have experienced the problem. So it could have just been a coincidence. Also i would assume that the problem should be instant rather than after a few days of having the rom flashed. Have you tryed jiggling the usb cable about in the phone to try & get a connection ?
[P3300, MDA Compact III ROM Development] mugglesquop:
lol, gotta love T-Mobile... No WM6 update as well :mad:

Good luck getting ur MDA sorted! :cool:
[T-Mobile Samsung Galaxy Note5] F9zSlavik:
I went ahead and exchanged my Note 5 under warranty. I got my new phone, flashed TWRP, flashed TEKHD, phone worked great until the battery died. I turned it back on and it was stuck on the Start Up screen with an error. I did not record the error code but it was on the top left hand corner in Red. Something about not being able to verify something. So I weant ahead and flashed stock rom and the unit keeps restarting into stock recovery. I've wiped data and cache and continues to be stuck. I flashed G1 firmware again and same thing. Any ideas what the problem might be? After restarting the phone in stock recovery, it reboots into recovery but with an error at the bottom in red. It reads:

Support APU: 3 <--------This is in white

dm-verity verification failed... <------This is in red

Need to check DRK first... <----------Also in red.

ANy ideas? Flashing back to stock, clearing data does not seem to help.
[T-Mobile Samsung Galaxy Note5] scrappy610:
First thing, You are flashing the correct firmware version correct? i had the dm verity issue with my wifes note 5. I fixed it by extracting the boot.img and system.img from the odin file and flashing system.img then boot.img and it booted. Supposedly if you do this and take an update or factory reset, you will have to perform these steps again. I just flashed twrp and rooted and she has been happily flashing away again without issue.
[T-Mobile Samsung Galaxy Note5] F9zSlavik:
Yes, I believe it is the correct. I was running G1. It was working fine as I said it just suddenly stop working after the battery drained.

How do you flash the system and boot? Same way? Odin -> AP flash?
[T-Mobile Samsung Galaxy Note5] F9zSlavik:
Does anyone have a solution for this? Can't use my Note 5 ;/ I tried doing as suggested but Odin will not see either the boot or img. Also, I can not flash TWRP. Which does not make sense as I was able to before. Something about FAP Lock.

Took a picture of it.
[T-Mobile Samsung Galaxy Note5] F9zSlavik:
So I did some more google searching and was lead to this thread

http://xdaforums.com/note5/help/how-to-solve-dm-verity-verification-t3293306

Says extract original firmware and delete cache and repackage it. Which I went ahead and deleted but when I try to repackage it, it gives me an error saying it is missing the cache.rfs. The tutorial uses a difference version of TAR.MD5 PACKAGER. The latest version I have has different options. It will not let me create a full rom unless the cache.rfs is there.

I am confuse and I need help.
[T-Mobile Samsung Galaxy Note5] F9zSlavik:
These are the options I am presented with

https://scontent.fsan1-2.fna.fbcdn.net/t31.0-8/14444752_10209691582821769_8183071702963249499_o.jpg

and these are the options that are present in the tutorial.

They are different.
[T-Mobile Samsung Galaxy Note5] scrappy610:
Sorry, I didn't get any notification for this thread. I actually took the boot img and system img and using 7zip added them to a new archive with the .tar extension and it worked. Thought it would be more difficult then that but it wasnt. Then I flashed them individually through Odin the same way you flash any Odin using the ap slot.

---------- Post added at 08:39 PM ---------- Previous post was at 08:38 PM ----------

Also, fap lock happened to me also, flashing the Odin files like I stated previously worked to boot up stock, then go to settings make sure all unlocking options are checked and your good. Some reason it reset everything on her and we still don't know why or what.
[T-Mobile Samsung Galaxy Note5] F9zSlavik:
I downloaded 7zip, added the boot and system into a new archive file, removed the 7 zip extention and replaced it with .TAR. I started Odin, loaded it under AP, and it does nothing. It loads but either sits and does nothing or it crashes. Phone simply stays in download mode. I don't understand why this phone refuses to return back to stock!!!

Any other ideas? I tried the latest firmware with the latest Odin and still nothing.
[T-Mobile Samsung Galaxy Note5] F9zSlavik:
This is @#$%*!@ BS!!! I received my replacement phone and I restored my TWRP back up I had made and the moment I restarted the phone I has the same bull**** error!!!! Boots into Recovery mode (stock) with the same god damm error! WTF!!!!

I went through the proper steps of installing twrp and then restored from a back up. I had to restart the phone and got an error code saying FRP blocked something, went into Recovery, and is now stuck on there again. How the hell am I getting the same error code on 2 different phones! I'm so pist!

I tried, like before, to restore G1 firmware, goes through everything fine in Odin, then it restarts, you see the little android in the back saying it is updating, then erasing, then abruptly restarts before it reaches 100 percent, restarts to the same android screen and errors out with the following message "no command", then boots into Recovery.

Does anyone have any idea wtf is going on and how to fix this god forsaken issue? I was really hoping to use this phone tonight. Otherwise I have to order another phone -_-
[T-Mobile Samsung Galaxy Note5] F9zSlavik:
Were you trying to write something?

I made a video of me trying to install stock firmware and what happens as a result.

https://www.youtube.com/watch?v=QBYdsJWqFw8
[T-Mobile Samsung Galaxy Note5] javierduran:
I had never seen this case, I saw your video and in the same YouTube saw some videos explaining the solution with a program. check out these tutorials can be the solution or see where some expert if you are unsure ...
[T-Mobile Samsung Galaxy Note5] scrappy610:
So your not getting the red text with the error anymore? That lock happened to me but i also had the dm-verity and drk errors. I flashed the systme.img and boot.img like I stated ealrier, except you have to do them individually. First the system then the boot. Then it will let you in. That FAP lock is in settings and has to be turned off before flashing twrp.

I got my solution from the same thread except I followed post #18. Not sure if it would help you. Do you know what firmware it was on when you got it? If i'm not mistaken you may have to go backto the exact firmware you had before you tried twrp and all.
[T-Mobile Samsung Galaxy Note5] F9zSlavik:
Hey thanks for responding back. I am still getting the red text error. I did as you mentioned, I did the system followed by the boot. Still the same error. I did the system and allowed it to boot. Same error. Went into download mode and loaded boot in AP. Same thing. So then I went and did System again, but did not allow to to boot, restarted phone and instantly went into Download Mode, loaded the Boot, restarted the phone, same error.

I don't understand this error.

At first I thought this happened because I did not enable ‘OEM Unlock’. So when I got my new phone, I made sure of turning that on. Then I installed TWRP with no problems. Restarted the phone and bam, red text error. The one thing I did not enable, was ‘USB debugging’. Could this have cause the red text error this time around?

I don't know what else to do
[T-Mobile Samsung Galaxy Note5] scrappy610:
Its possible, but i doubt it seeing as how your going into download mode.

I never got the red text to go away. It was there every time i did a factory reset or ota upgrade. But i always got it to boot using the system and boot. So, you have fap turned off now? If so, you should be able to flash twrp. That was the only thing keeping me from flashing twrp. After i got it to boot, then turned on oem unlock, i rebooted to download mode, flashed twrp and then custom rom and kernel and never saw the text or had an issue with it again.
[T-Mobile Samsung Galaxy Note5] F9zSlavik:
I can't flash TWRP so I am assuming it is on. The way its turned off is via debug mode off and oem off right? But I was able to flash it before this problem happened. That is what confuses me
[T-Mobile Samsung Galaxy Note5] scrappy610:
Yeah. If its on it should tell you when your in download mode. And if it is only way to get it off is flash bone stock.
[T-Mobile Samsung Galaxy Note5] F9zSlavik:
I've done stock flash. I don't know where I went wrong. I just got my 3rd replacement. I am going to try and install TWRP, nothing else. Debugging mode on and OEM Unlock on.
[T-Mobile Samsung Galaxy Note5] mryanmarkryan:
Have you tried going back to stock com and then reset from within the rom ? Worked for me once after I did an at from flash on my Sprint phone
[T-Mobile Samsung Galaxy Note5] Nathan.7118391:
Hav you tried full wipe? once you ODIN back to stock then you should be fine. if you are still having trouble you should do a full wipe and restart.
[Upgrading, Modifying and Unlocking] lyriquidperfection:
Hi I was wondering if some kind soul could provide me with a QPST QCN backup of their ZTE MF112 so I can try repair my corrupt EFS as the SPC is no longer accepted.

I use this device for testing purposes as I am the developer of EFS Professional and I am currently updating Qualcomm NV Tools and adding new features as part of an upcoming update.

Any help would be greatly appreciated. :)
[Sprint HTC EVO 4G LTE] CarpeDiemTim:
My rooted Evo 4G LTE is running HBOOT 2.09, Android 4.1.1, and radio 1.12.11.1210. And I've been trying for days now to get this thing running on Cyanogenmod 12.

For one thing, most of the tutorials I'm finding have dead links, so I'm having to piece together information.

Plus, I even downloaded a couple RUUs that were specifically for the Jewel, and yet when I ran them, it said I had the wrong one (so my device is now wiped, without an OS).

Most notably, any time I try to get S-Off, I get as far as the "unlock token check successful" message, but then I'm not seeing a prompt on the phone itself that apparently I should be able to press Volume-Up to confirm the S-Off.

I know that part of my difficulty is needing to update HBOOT because several times over, I've seen a message stating that the installer package was made for 2.10 and up.

I've been spinning my wheels quite a bit here, and I'm just lost and could use your help. Any helpful advice would be greatly appreciated :good:

UPDATE: Following the trail of others who have been stuck in S-On, I found this thread:

http://xdaforums.com/showthread.php?t=2492469&page=2

...which led me to try sending a lock command before unlocking, and in that case, I actually got the prompt on the phone's display like I'm supposed to get, BUT if I select 'Yes', it reboots, and gets stuck at the HTC logo (since the OS was wiped with a failed RUU update), and if I power off the phone (by holding the power button for quite a while since the battery isn't removable in this lovely model of phone) and go back to fastboot, I'm still S-On and the CID is SPCS_001.

Here's the output:
[Sprint HTC EVO 4G LTE] dangle79:
Okay, so ultimately where you'd like to get is the latest CM for the jewel, right?

I'm a little confused regarding your current status about s-on/off because the process you're describing is around unlocking your bootloader.

Since you're on 2.09 you've got to do s-off the way i did it way back when using dirtyracun http://unlimited.io/jewel.htm

i honestly don't remember doing this all through linux/ubuntu, (read, i probably went the long way 'round the barn to do it using Windows) but just follow the directions. there are links to the stock RRU's to the right of the page if you want to see the device boot normally before proceeding. This will get you to s-off

next you wan to get to current firmware, I still have a copy of the most recent RUU for the jewel, the one Sprint released and then pulled. You can find it and instructions here https://www.dropbox.com/sh/hl5zaxvdjjokrhm/AAAR5iEqCvTQ09vHhDA0MWODa?dl=0

this will bring your SPCS_001 to HBOOT 2.10 and the 1.13 radio etc. on stock Jellybean 4.3 (as i recall), you will still be s-off and there's no need to unlock your bootloader again; i never did.

once that's all done you can fastboot flash the latest TWRP from here https://dl.twrp.me/jewel/

and then there's the last cm 12.1 build i did (as far as i know it was the last one built and shared) https://www.dropbox.com/sh/r11bcdephdslkvh/AAC8mSKwOkdbug4VGUROlUaYa?dl=0

good luck. i see it was over two weeks ago that you posted this, i just happened to bop over to see if anyone else had been tinkering with cm13 still. hopefully it's still helpful