yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dracinn:
I'm going to try the update after I do a backup to see what happens.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Just flashed NJ2 BL & MDM zip & all is good ? LTE signal seems to have improved a bit. Wife's d2att is still on NJ1 do I did a speed test with devices side by side & mine is 8mbs faster after several tests. Gonna let it settle in a bit & test again to be sure I'm not getting a placebo effect. [MENTION=2972841]enewman17[/MENTION] thanks a lot bro! You da man? ? ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thonyromes:
Random Reboots

sorry this isn't related to thread but its the only place i could ask for help.

my samsung galaxy s3 at&t with 4.4.2 UCUFNE4 keeps rebooting randomly. i have made different experiments and noticed that it usually reboots once my ram goes a little over 700mb. but sometimes it reboots even when am only just browsing through the phone. i have tried various fix such as removing the battery, sim card, sd card, going airplane mode, disabling location, formating, updating to UCUNJ1 rom and bootloaders+modem but the problem still persists. pls could anyone offer their assistances thanks in adance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
[MENTION=6799464]thonyromes[/MENTION] if you've flashed or updated to a new ROM bootloader & modem & its still persistent, sounds like a hardware issue which can't be resolved by changing firmware or software/OS. it'll need to be repaired internally if that's the case. I had a friend who had a d2spr (sprint s3) & he had exact the same issue. He tried everything, including updating to the latest stock firmware & eventually had to get it replaced.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dracinn:
I would recommend making a backup then factory reset with stock recovery and see if your problem persists, then you should be able to know if it's hardware or not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thonyromes:
thanks for the reply. i will do just that. but before then i just installed cm12.1 on the phone. it rebooted when my location was on so i turned it off. am still testing it. the problem now is that i can't connect to a wifi. i can turn it on and search but can't connect. i could do this on the previous UCUNJ2 stock rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sritej20:
Rooted SGH-i747 on NJ1 softbricked after accidental OTA update to NJ2

Hey guys,

My phone got softbricked when my rooted NJ1 tried to update itself to NJ2. Can someone confirm if the below process is what i should follow ?

1. install custom recovery twrp by putting my phone in download mode using odin.

2. copy Flashable NJ1 Bootloaders and modem. MD5: 3f508608848313313c3af3b3229dab69 into sd card

3.start phone in recovery mode and install the .zip file

Queries

. should i extract the zip file and select boot.img and system.img separately?

. should i instead pick nj1 stock upgrade to nj2 stock and then rooted nj2?

.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
Your on the right track

Install the custom recovery

Flash the the NJ2 firmware since it messed up on the OTA there is a chance going to NJ1 could make things worse.

So flash the NJ2 firmware then the NJ2 rom... you don't have to reboot in between

Don't extract the zips just place on the root of you ext sd card and flash in recovery
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sritej20:
Do i have to format the entire internal sdcard? in case if i do can i make a nandroid backup and restore after flashing the firmware and rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sritej20:
Also which one do you exactly mean by firmware and rom?

Flashable Rooted NJ2 system.img and boot.img = ROM ?

Flashable NJ2 Bootloaders and modem = firmware ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dracinn:
I had that problem when I just updated bootloader/modem then installed NJ2 system backup and all was working so I guess CyanogenMod may not yet be compatible.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
You shouldn't have to format the internal sd. Making and restoring a nandroid won't restore the data that was on the internal sd. It only backs up the system, boot, and app data. So you might want to backup the contents before formatting.

Correct
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dracinn:
No you do not have to wipe storage but if your still running stock I would wipe davlik/cache, system. I assume you flashed bootloader/modem so you no longer need that so just install NJ2 rooted .zip.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
Guys, can someone confirm if this is the same result you are getting when running the Zimperium Stagefright detector app on this new build..? Not all security holes are patched? I'm running a slightly modified ROM with this fix included.. Just needed to rule out if its the ROM or the patch. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Are you running one of enewman17's NJ2 roms, or someone else's ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
Someone else's.. Thats why I was asking. If u are running enewman17's stock, can you check? Cheers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeadlyByNite:
What rom exactly is it if you don't mind sharing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
S3 R3ARMED | TOUCHWIZ | 4.4.2 | AROMA

Its not based off the NJ2 Rom yet, but the Dev included the stagefright patch ATT released.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeadlyByNite:
It's stated here that there's one thing that isn't patched. Pretty sure that it will be shortly. Here is the link: http://xdaforums.com/showthread.php?p=62458654
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
Yes, I did read that. Just wanted to make sure; u know.. If someone was running latest pure stock..cos the other ROM isn't based off NJ2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
NJ2 shows the same vulnerability...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeadlyByNite:
I haven't updated to NJ2 myself yet, but from what I have heard (remember you can't believe everything you hear on the Internet) it's only been patched for the NJ2 stock rom. But devs are definitely starting to build roms based on NJ2. Sorry I couldn't help more. I think lollipop roms are a bit safer also, but I can't confirm that, so it's still a hit and miss. If you want I can point you in the right direction to for ways to stay protected until fully patched.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
Thanks for the confirmation. Cheers ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rsborn:
Thank you so much for this. AT&T tried to send this to me OTA and it broke the phone and corrupted the EFS and my IMEI was null, installing this bootloader and semi-stock rom fixed it. I don't know if it was supposed to but it did and I'm grateful.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
Hi enewman17 I have a question...is safely go back from nj2 to nj1 bootloader/modem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
No, you can't downgrade the bootloader & modem. What's your reason for wanting to go back?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
Hi.. Is for heavy battery drain. But thanks for your answer.. I have cm12.1 nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Is flashing NJ2 the only thing you've changed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
Yes ...that is the only thing I have change.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikek753:
NE4 to NJ2?

hi,

can I flash directly my NE4 to NJ2 boot_modem zip?

do I have to flash NJ1 in between?

thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
I don't think you can skip one. I wouldn't try it. Its too easy to just flash the bootloader/modem anyway.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
From NE4 flash NJ1 bootloader & modem combo zip, then NJ2 bootloader & modem combo zip. You should reboot in between & check your baseband in settings/about phone to make sure you got a good install, then flash the next combo. DO NOT SKIP you'll end up with trouble!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikek753:
did you upgrade to NJ2 to address security (media) vulnerability issue?

I try to understand if I should or must upgrade from NE4 to NJ2?

thanks for the education.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
You dont have too, but yes I'd recommend it. NJ2 was a patch for stagefright vulnerability. If you're on stock & plan to stay on stock, you'll need to update bootloader & modem & the ROM too. Again, be sure to do it incrementally. NJ1 bootloader & modem + ROM, then NJ2 bootloader &modem + ROM. If you're on a custom AOSP or CM based ROM you can just update the bootloader & modem only. Either way you CAN'T SKIP NJ1. Also, once you update don't ever try to downgrade. If you do, you'll BRICK! & Your welcome bud ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] logoster:
how long should it take to actually finish booting? my phone seems to get as far as the AT&T logo then after a bit my phone vibrates, screen brightness go's down, then my capacitive touch keys light up, but then after the set time they shut off and my phone screen appears to be stuck on the AT&T logo
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
If you get stuck on the at&t boot screen then you most likely didn't wipe data media (your internal sdcard) . When going from AOSP back to TW you'll need to format "everything" except external SD card. Put the ROM on your ext SD & wipe data/factory reset. Wipe system, cache, dalvik, sdcard0 (data media) then reflash. Make sure you backup your internal & any important files in data media b4 you do this. Be sure not to wipe external SD. I recommend TWRP 2.8.7.0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vtails:
I d/l update but it said it was interrupted check 24hrs. I had debloated with Ashland so I must have taken some files out. So I d/l update.zip from the other thread, I also tried to restore kit Kat from an old backup but it had some com files that had stopped, I made backups with Philz and tried to install withh trwp and I guess thats why it had the com files missing. I did so fast tapping and got to factory restore and update finaly took. It has better signal but its still Kitkat.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] btygielski:
Hi, I want to clarify the steps as I once did a wipe on the internal storage and had a heck of a time getting the phone working again. Do I install the recovery on the external SD card (TWRP) and pull down the flashable img file for the rom to the ext SD and flash from there? I am on the correct bootloaders and modem but want to return to stock. I'm thinking this is the right step but want to confirm before I proceed.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
I am basing my reply on your comment and on the post you quoted:

It appears you are on a custom ROM with a custom recovery. If your custom recovery is fairly current you can place the files you are flashing on your external sdcard for flashing. If your recovery is not fairly recent you may need to update it before beginning.

Stating the obvious, make backups and nandroids before proceeding.

If you are not on the current bootloader and modem, NJ2, and you are wanting to be on stock NJ2, flash bootloaders and modems in sequence until you are on NJ2 from your current custom recovery. Do not flash anything that would downgrade bootloader or modem. Do your factory reset, wipes, and formats from the custom recovery already on your phone. Flash the stock NJ2 you procured from the OP and placed on the external sdcard.

If you have trouble booting after doing the above you may need to flash the stock recovery, found in OP, and do a factory reset from within it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] btygielski:
Thanks.... You are right on with the assumptions. I am on cm11 with twrp. I'll give it a go and hope everything turns out OK. Thanks for your help and understanding.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tank Weston:
If I'm on NJ1 on cyanide's newest 5.1.1. build, can I just dl the bootloaders and modem and flash them in twrp. WIll it affect anything? I don't want to wipe anything because I have a ton on my phone and it takes some time to back it all up. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
That should work fine. There is no need to go back to the stock ROM if you are simply wanting the newest bootloader and modem. I guess if you have connection issues you could wipe cache after flashing, but only if necessary.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tank Weston:
No issues buddy, thanks! I wipe cache & dalvik after flashing anything anyways. Good looks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] btygielski:
Thanks dawgdoc, enewman17 and candroid. I did the wipe and flash as directed and it worked flawlessly. Thanks very much for the great instructions and the patience.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Glad to hear you have it working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] logoster:
i do have TWRP, i did a "full wipe" with it (advanecd wipe, selected everything except microsdcard and usb-otg) and then did a flash with your file, i still only get as far as the AT&T logo (i get the sound and the logo does spin for the duration of the sound, then it locks up other then my notification light pulsing)

i've also tried flashing the stock recovery with it as well, still locks up at the AT&T logo
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chowming:
I have had this exact problem going from ASOP to TW.

Using TWRP it just had problems. either it was the version I was using or my being new to twrp. Flashing a version of Phil's recovery did not do it either. I had to Oden stock on a pc.

That tool me a couple tries but when it worked it fixed all issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
How can you Odin back to stock if you on are a bootloader newer than MJ2?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
I have read several times that reverting to the stock recovery, doing a factory reset from there will fix the boot issues. enewman17 has a flashable zip of the stock recovery in the OP of this thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
I've never heard of that as a solution. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] StoneyJSG:
So is there a flashable odin tar file for NJ1/NJ2? I'm still on NE4 and don't want to flash TWRP to upgrade or take at&t's OTA.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Not that I have ever heard of.

The last official flashable tar by AT&T was 4.1.1. Everything since has been OTA releases with no accompanying tar files. I vaguely recall one of devs (probably enewman17 or maybe loserskater) creating a tar of either MJB or NE4, but nothing since.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] insaneghost17:
Hi I am running Android 5.1.1 Dirty Unicorns on AT&T Galaxy S3 I747 Lollipop Custom ROM but i am wondering if I can go back to stock ROM. Its band base says its UCUFNJ1 and I'm wondering If I can I go back to stock ROM. I also created a back up before but every time i install it I get a bunch ""such and such" function stopped working" Help would be very much appreciated thanks.
[ONE General] aooga:
Hey, do you still have any left? Thanks :good:
[ONE General] Sunil_k:
Hey Aooga still interested with the invites?
[LG G Watch R] mattcoz:
Love this watch but this one issue is driving me crazy. Very often I'll swipe away notifications from the Gmail app(yahoo mail account, not gmail) and they just come right back, or I'll get them multiple times. I don't have any problems dismissing these notifications on my phone, just on my watch. Anyone else having issues like this? Any ideas?
[HTC One Mini] AndroGeek974:
CyanogenMod is a free, community built distribution of Android 5.1 (Lollipop) which greatly extends the capabilities of your phone.

Here is unofficials builds of CyanogenMod 12.1 for HTC One Mini (m4).​

How to get this ?

You need the last .zip package (15/12/11) : https://www.damien-boyer.com/downloads.html

And the 5.1 gapps : https://www.androidfilehost.com/?fid=95916177934550851

Progress of the Project:

26 Dec 2014: Initial Release

19 Jan 2015: Fix Camera and lot of other things.

27 Jan 2015: Sources updated. New CM bootanimation.

06 Apr 2015: CyanogenMod 12.1 - Android-5.1.0_r3

15 Apr 2015: Updated.

08 Jun 2015: Updated by [MENTION=6749826]Wingman2K[/MENTION]

11 Jun 2015: Updated by [MENTION=6749826]Wingman2K[/MENTION]

15 Jun 2015: Updated by [MENTION=6749826]Wingman2K[/MENTION]

21 Jun 2015: Updated by [MENTION=6749826]Wingman2K[/MENTION]. Check the changelog.

27 Jun 2015: Re-sync + CM12.1's MSM8960

16 Jul 2015: Re-sync + TeamEOS kernel source

13 Oct 2015: Re-sync by [MENTION=6749826]Wingman2K[/MENTION].

11 Dec 2015: Last CM12.1 Build

Issues

Memory leaks and other lags.

How can I install it ?

1. Copy the ROM and the Gapps in your device

2. Reboot in recovery (TWRP or CWM)

3. Wipe

4. Flash the ROM

5. Flash the Gapps

6. Reboot

7. Enjoy the ROM

Don't forget to contribute

Donate with Paypal

XDA DevDB Information

CyanogenMod 12.1 for HTC One Mini - m4, ROM for the HTC One Mini.

Source Code: https://github.com/CyanogenMod/android/tree/cm-12.1

Kernel Source: github.com/TeamEOS

Blobs: https://github.com/TheMuppets

ROM OS Version: 5.1.1 Lollipop

ROM Kernel: Linux 3.4.x

Version Information

Status: Beta

Created 2014-12-26

Last Update 2015-12-11

Special thanks to [MENTION=2858383]mattplo[/MENTION] & [MENTION=6749826]Wingman2K[/MENTION]
[HTC One Mini] malikou:
first

another LP rom for our beloved M4 , nice i'll try this right now
[HTC One Mini] mattplo:
;)

Trying to patch in D2W/S2W for the kernel from CM11 patch. Its fighting me.
[HTC One Mini] malikou:
After a day of use, the rom run flawlessly apart somes lag on intensive use, i have got redraw and 2 cases of reboot ... I will try to reproduce that and bring catlog ... However the rom is very stable for first release, keep up the good work ;)
[HTC One Mini] AndroGeek974:
Thanks for you report [MENTION=662367]malikou[/MENTION]
[HTC One Mini] dvb127:
Very Good Rom

This Rom is realy great and fast, I'm not a heavy user of my mini but I didn't have an issue since yesterday only Camera - do you have a fix already? Thanks.
[HTC One Mini] AndroGeek974:
[MENTION=950746]dvb127[/MENTION] : Thanks for your report. I have others projects so no fixes for the moment
[HTC One Mini] malikou:
The proximity sensor dont work ... Apart this i didnt got redraw or reboot since 2 days, every think seems to be good i ll continue reporting if i found another issues ...
[HTC One Mini] mattplo:
I actually have this fixed but at the cost of a major crash that leads to a reboot after the screen attempt to come back on when a call has ended. As soon as I get back to the mainland (I'm on vacation in the Caribbean) where bandwidth is plentiful I'll get in contact with the OP if he has time.
[HTC One Mini] htc_one_mini_m4:
Sorry for this, but since the CM11 and the sudden death of One Mini's issue, I'm concerned.

Has it been solved ?

Is CM12 having similar issues, or not ?

I've lost quite a few episodes, so I don't know if it been fixed since CM11 latest updates, etc.
[HTC One Mini] pure.by:
There has been no official statement on this issue.

An updated thermald config was implemented in CM-code somewhere last summer/fall, presumably solving the overheating issue.

It is not 100% clear whether issue is solved, though, because there has been at least 1 report of overheated & bricked M4 under the patched thermald config right after it was first posted as a separate patch.

I must say the above applies only to the official CM11 M7 snapshop and nightlies thereafter. I have no experience or knowledge about later snapshots or this, unofficial CM12 port.

Can only say there have been no reports on XDA about bricked devices somehwere since summer/fall.
[HTC One Mini] htc_one_mini_m4:
Thank you very much mate!

You're always around helping people ;)
[HTC One Mini] AndroGeek974:
New build out.

Check first page, new build fix camera and a lot of others things.
[HTC One Mini] rsiddall3130:
Nice job! Like the CM12 Themer...although there are some issues with lockscreen wallpaper, I understand that is across the board.

Has the bluetooth audio problem that I'm experiencing in the Candy Rom as well. Currently using your rom as my daily driver because that's really all the issues I'm having.

Very peppy and happy to see another version of Lollipop for our device!
[HTC One Mini] AndroGeek974:
Thanks for your report man !

I think these types of issues gonna be fix in future builds, in fact it depends of the blobs and cm updates.

I'll try to make weekly builds of this ROM.
[HTC One Mini] gazleyp:
Thanks for a great ROM dude I am also using as my daily driver, got same issue with Bluetooth Audio and seem to have slight connectivity issues nothing major (might not be ROM related) but is first time have experienced this. Looking forward to your future builds.
[HTC One Mini] AndroGeek974:
27/01 build
[HTC One Mini] mattplo:
Update: Finally got around to flashing this. Glad to say everything works as expected. However, I didn't test its Bluetooth. It comes on just not sure how solid it is. But aside from that. Great build.

All of the new features CM guys incorporated are pretty snazzy too.

Waiting for my SO to get home and I'll flash this.
[HTC One Mini] EdiBese:
hi/mic issue

flashed this rom.

everything is working finde. BUT still there is for me an issue with the microphone. i had it on cm11 too

during calls, the other one cant hear me good, i think the mic volume is too low. is there a way to boost it?

PS: On my S1 Galaxy there is a app called "voodoo sound". with this app i could boost mic volume and the other one could hear me better.

But after long searches i couldnt find similar apps for the one mini.

With the insert coin rom the problem is still there, but i think with cm its worse. i need this mic fix, otherwise i cant use this phone any longer -.-
[HTC One Mini] stoffel010170:
official CM release?

Hi,

is a official cyanogenmod 12 release planed for M4?

thx
[HTC One Mini] Nous16:
Ram use is quite nice :)

WhatsApp and Threema about 290-310 Free Ram

The system use is about 300 MB Ram
[HTC One Mini] i859:
rom works good, but gotta install gapps separately
[HTC One Mini] Nous16:
So it is my last try to port android 6 for our device. . .

My problem is still the SELinux denial.

type=1400 audit(1456345610.720:4): avc: denied { write } for pid=149 comm="kworker/0:4" name="/" dev="tmpfs" ino=5145 scontext=u:r:kernel:s0 tcontext=u:object_r:device:s0 tclass=dir permissive=0

If somebody have an idea to fix it, it would be great :)

So I am not able to fix :/

It seems although nobody wants the rom :/

Here is the last ksmg log.
[HTC One Mini] jame02:
[MENTION=6934193]Nous16[/MENTION]

Sry, I cant help you. I first have to look at building Android. Until then, I only can test your builds. I will install RR 5.1 - maybe its more stable than the one from androgeek. Wish you luck fixing the bug.?

PS: Whats with you [MENTION=5365082]AndroGeek974[/MENTION]? Stoped supporting this thread?
[HTC One Mini] Nous16:
Would be great if you can give me feedback about the rom (RR 5.1)
[HTC One Mini] gfsLuc:
I am actually using RR Rom. Can't say yet how stable for daily use. But everything seems to work at the moment.

Thank you for the Rom. Can't wait for marshmallow.

[edit]

ram usage seems to be a lot better than with cyanogenmod rom. until now it was very reliable.
[HTC One Mini] AndroGeek974:
Thanks for your help man. I have some problems now about my internet connexion so I can't really work in proper conditions but the developement for this device (and M7) continue.
[HTC One Mini] Nous16:
For information: You can use the msm8960 Kernel from CyanogenMod (CM13.0) https://github.com/CyanogenMod/android_kernel_htc_msm8960