yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] goose2600:
After updating to v2.0 my phone is stuck on Samsung Galaxy S7 edge logo, instead of asking for the the pin (stock G935FXXU1BPJG rom with full disk encrypion).

The led is breathing very slowly, but never turns completely off.

Reflashing v1.9.0 the phone ask for pin, but fails to decrypt.

Does anyone experienced this issue after upgrading?

Thanks!

EDIT: my issue is definitively related to the data partition encryption and the slow-breathing led, probably, means that the phone is just re-encrypting. I will try to wait until the re-encryption process ends.

EDIT2: Stuck on boot after 3 hours... I had to flash AP via Odin
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] fureedx:
Can you explain what steps you made ?
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] goose2600:
I didn't solved my issue: I had to flash original firmware via Odin.

I also tryed to flash the v2.0.0 starting from the scratch, but it didn't work: stuck on Galasy S7 logo.

Now I am running stock kernel.
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] fureedx:
I've had the slow led /stuck boot logo before flashing the kernel but that was because i took a wrong step... I think what fixed mines was these steps i did .

reflash the firmware . restart and boot back to download mode to flash twrp. Skip booting to device and go straight to twrp. wipe>format data>yes . reboot straight back into twrp again. flash no drm-verity/supersu. Boot to device and config ur first time usage thing (wifi /terms /ect. ) Download synapse and everything else you need . then reboot to twrp and flash prometheus kernel and reboot to device. Sorry for this hard read but it worked for me.
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] goose2600:
Thank you for your effort! But formatting data, of course, you lose the full-disk encryption.

Did you try to encrypt your phone (via settings/security menu) after flashing the kernel? For me did not work (encryption process simply does nothing).
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] fureedx:
Ah i see what you mean . I dont use encryption.
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] DirkStorck:
[MENTION=1148003]lyapota[/MENTION] Hi, how can I flash you latest kernel on top of my ROM without getting phh superuser and magisk reseted?

When I flash your kernel, I have to grant each app again root and all my magisk modules are gone to I have to set up both again! With v1.9 that wasn't a problem at all.

Thank you!
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] Sage:
please delete.
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] lyapota:
v2.0 with option "No root" must be identical to v1.9
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] DirkStorck:
About my problem that magisk and superuser gets removed I found out that you have script inside "clean.sh"

looks like it get always executed.....

#!/sbin/sh
# ========================================
# script Helios ROM
# ========================================
# Created by lyapota

# Remove SU images
cd /data
rm -f magisk.img
rm -f stock_boot.img
rm -f su.img
rm -f stock_boot*.gz

rm -rf /data/app/eu.chainfire.supersu-*
rm -rf /data/data/eu.chainfire.supersu

rm -rf /data/app/com.topjohnwu.magisk-*
rm -rf /data/data/com.topjohnwu.magisk

rm -rf /data/app/me.phh.superuser-*
rm -rf /data/data/me.phh.superuser

rm -f /data/app/Super*.apk
rm -f /data/app/Magisk*.apk

I think /system/xbin/sqlite3 doesn't get always installed but it is needed for Synapse....

Speaking of Synapse. The wakelock tab shows an error because it thinks the wakelocks directories and not files as they are....
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] lyapota:
Ok, yes rooting methods migrated from Helios. Run clean.sh without conditions appropriate for ROM installer, but not for kernel.

I'll look for Synapse wakelock tab again. Last time when i tried, didn't see any error.
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] DirkStorck:
Thank you! really like your kernel a lot!
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] BustedFly:
Thanks, hope you can fix all issues in v2.0.0
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] leboreiro:
Does this kernel support charging control ???

Enviado desde mi SM-G930F mediante Tapatalk
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] DirkStorck:
No, it doesn't.
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] sielhadi:
How to fix cdrom emulator it doesn't work
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] sielhadi:
Can you please add support drivedroid
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] bmonteiro:
I'm trying to use prometheus 1.4 to disable touchboost, but my phone wont boot after flashing it, it stays stuck at ghe Samsung logo screen.

Is there something else that need to be done for it to work?

Using Superman rom 1.7
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] Stoowyguy:
I am trying to rock the Conservativex gov and synapse always changes my settings back to interactive after like reboot I think.
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] luke76bg:
i can't get synapse to works, i switched from super kernel to prometheus and synapse keep loading forever, and after a long time it gives me various error in info about root revoked but it's not true, it have root in super su! i'm using super su system mode sr5 (because of cache and data in f2fs). Any clues ?
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] NonXtreme:
Have you wipe the synapse data?

Just so you know, the synapse data of these two kernel are not interchangeable. You must wipe the synapse data and set it up from scratch.
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] BustedFly:
I have thus problem too.. But on full wipe installation. I think this is a kernel related problem.
[Verizon Galaxy Note 3 General] en11gma:
just wanted to say i had been running my verizon note 3 (non-dev edition) like everyone else here

with the bl unlocked to dev edition and rooted most likely with either kingo or supersu through teamyemin or proyemin and i think there is another one too.

basically if you want to go back 100% original (including your original cid) its not as easy as you might think.

first thing i did was wipe everything that was possible to wipe from within twrp recovery.

next i booted to odin download mode

from there i flashed the OB6 official firmware

then i rooted using the kingo method as this seemed the most likely not to infect my computer and possibly only stole info from my phone. (this used the 2 files 1.tar and 2.tar flashed with odin for pc)

i then verified my root and installed terminal emulator end es file explorer root

i copied samsung_cid to phone sd card and used es file explorer root to move to ./data/local/tmp

changed my cid back to original and rebooted phone

booted to stock recovery and wiped everything i could and booted into odin download mode

flashed OF1 official

there is a very important part that could get alot of ppl phones into brick mode.

when you goto change the cid back to original you better already have the stock BL on and running and >>>NOT<<< the DEV-BL

that is why i chose to flash an official OB6 rom first

if you try to change the cid to original non-dev edition and reboot your phone this could have problems since you would have the dev bl flashed with a non dev bl cid

when the cid for the dev edition became available you could change the cid first and boot into the bl and it would say something like developer mode enabled or someting like that even if you had the stock bl flashed (not the dev bl)

this is fine

only problem is if you change that cid back to stock/original non-dev while you are running the dev bl

i dont know what would happen but i bet it wouldnt be good.

ok next part i think is important is getting rid of kingo root as much as possible and that is why i flashed the OB6 firmware first and then OF1 for my very last step.

ok thanks.

i know alot of ppl are probably gonna say why would you want to go back to stock original cid and my answer is this.

phone is really stable and also if i want to sell it which im thinking about.

hope it helped some ppl.
[Verizon Galaxy Note 3 General] ExpialZLD:
Where do we get our original Cid?
[Verizon Galaxy Note 3 General] bftb0:
The method used to do the unlocking runs the tool in two passes, like this:

pass1: change the CID.

pass2: (create debrick image &) alter the aboot partition sig to the DevEd sig.

There is no reason this can not be reversed (assuming you have root on ANY ROM) e.g. :

pass_negative_2: flash stock aboot to aboot partition.**

pass_negative_1: revert the CID by altering the original code to write your CID (minor code change and recompile).

** must be from the exact same version of boot firmware you have on the phone; you could use "dd" for this.

There's no reports of people trying this explicitly, but OTOH note this: there were owners of DevEd devices that accidentally flashed stock bootloaders. They didn't change their CID, and they didn't brick. They just couldn't go back to an unlocked bootloader any longer, or boot custom kernels: they converted their phones to retail without ever changing their CID.

Anyhow, it appears that you went through a ton of effort, when all you needed to do was flash the stock "aboot" back into place.

It probably isn't even necessary to revert the CID back.

You recorded it - as a precaution - when you went through the unlocking process. Didn't you?

As I mentioned above, it probably doesn't matter anyway.

@OP: did your "Custom" boot logo disappear eventually?

PS even after doing this the phone will still have a blown knox warranty flag and certain TZ/qseecom functionality will no longer work, even with 100% pure stock on the phone.
[Verizon Galaxy Note 3 General] ExpialZLD:
Does by record do you mean by using a tool or like taking a picture of the cid
[Verizon Galaxy Note 3 General] bftb0:
Cut-n-paste to a text file.

The tool spews out onto the screen the device's CID before it goes about changing it.

That assumes you followed the directions in the OP and used ADB. Or, didn't follow those instructions and used a terminal emulator. (I don't know whether or not the app shows you the output from the binary).

As I mentioned, folks that had DevEd devices (that is, "factory unlocked" bootloaders) that made the mistake of flashing stock firmware turned their DevEd phones into retail phones - without ever changing the CID to some other value. So it may not even matter - you end up with a "retail" phone with the same CID that you currently have.

In any event, if you didn't record the previous CID, there's nothing to do about it.

The OP mentions something called "samsung_cid". I presume he is talking about a mod of the original code that allows you to re-write the CID to an arbitrary value.
[Xiaomi Redmi Note 3 Questions & Answers] MOVZX:
You're flashing a custom ROM, you already know the risks. For the sake of humanity, please stop telling lies to the shop/company/manufacturer because it's not good.
[Xiaomi Redmi Note 3 Questions & Answers] MdFaheem:
This should not be an issue of custom rom, I feel this should be an issue of defective battery /charger.
[Xiaomi Redmi Note 3 Questions & Answers] mgolder:
If you voided the warranty by putting a custom ROM on then Xiaomi don't have to fix or replace anything at all. Even if a part was faulty (and almost certainly is to blame of course).

You could try to warranty it and see what they say. Worst case is they say no. Best case is they give you a new phone to keep you quiet.
[Xiaomi Redmi Note 3 Questions & Answers] omegaorgun:
I think you'll get a replacement, say nothing about the rom. Supposedly there was a quality control issue with some batches.

Just wing it get a refund. Post pictures to seller. If you used PayPal your all set.
[Xiaomi Redmi Note 3 Questions & Answers] Wazzim:
Say nothing about the custom ROM and they won't care , good luck mate!
[Xiaomi Redmi Note 3 Questions & Answers] akhil17kr:
Flashing Custom ROM doesn't voids warranty , already confirmed from Mi care here in India
[Xiaomi Redmi Note 3 Questions & Answers] MdFaheem:
Good luck mate
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] Element24:
Please write in the OP the steps on how to install the ROM. Which GAPPS do we need, and what to do with the DATA download... Thanks for the ROM BTW. I will test it and give feedback.
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] amrahmedd:
Screenshots ?
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] Element24:
Download link for the ROM Is not working...
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] Sparco21:
Any screenshots ?
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] GeeekyBoy:
I have updated the download links
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] GeeekyBoy:
You will perform TWRP data restoring using the data folder
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] bleedreader:
How about playstore if we dont flash gapss?
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] Element24:
Trouble while trying to restore the data from the TWRP backup.. It is not showing when i go to the restore section, but if i browse in the file manager it is there.. Any solution? Also tried putting it in the internal storage, but same. It only shows the backups i've made earlier....
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] GeeekyBoy:
You have to have the files with this folders paths:

/sdcard/TWRP/BACKUPS/5a32e610/Turboroid-A-Preview-1-Data/data.ext4.win
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] GeeekyBoy:
It is already included the latest version
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] GeeekyBoy:
Go here: https://1drv.ms/f/s!ArLpZMhtIMDArVNFLTr1pNoXdb0g
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] Shubho20:
If we can't use google play games, we can't play games like clash of clans which uses google play games. Right?
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] Stiliyan:
[MENTION=7166150]GeeekyBoy[/MENTION] for what is the data backup?
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] GeeekyBoy:
To play it you have to install Gapps which will lag your phone as usual
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] Sniperboy1:
Only problem is cannot connect to Google servers. No Play store connection.

Excellent ROM otherwise.

Thanks.

Please make a 64 bit version for Lenovo A6000 plus.
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] Shubho20:
How we will download apps if there is no play store connection?:confused:
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] GeeekyBoy:
Try to checkin in microG settings
[Lenovo A6000/Plus ROMs, Kernels, Recoveries, & Oth] Stiliyan:
You can download apps, the Google play games app not work and you cant login the games.
[Moto G4 Plus Questions & Answers] jogawa:
I just got my xt1644 (G4 Plus, US version) yesterday and was trying to get root.

I got through successfully:

1) Unlocking bootloader.

2) Flashing TWRP.

3) Flashing the boot.img from the Root-motog4-athena-xt1641-xt1643.zip file (maybe a mistake, but read on).

4) Flashing SuperSU.

So then, I HAD root, but no WiFi. Seemingly others had this problem, so I added the ro.securestorage.support=false to the build.prop.

Nope. Still no WiFi. So I tried to change the build.prop BACK by deleting that line. Then, on the next boot, it stays in the "Your bootloader is unlocked" screen and does not boot to system.

I DO have bootloader access, and TWRP still works.

So, if anyone has:

1) A stock build.prop for the xt1644, or

2) New ideas, or

3) Access to the stock rom for the xt1644, which I cannot fiind,

PLEASE let me know.

Thanks!

J
[Moto G4 Plus Questions & Answers] xtermmin:
http://www.filefactory.com/file/3t2...PJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip

Posted this in a bunch of stock ROM topics.

For root, there is no need to flash a new boot.img. Just unlock bootloader, flash or boot TWRP, type in the command to tell SuperSU to flash in systemless mode, flash SuperSU, and reboot.

Guide: http://xdaforums.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
[Moto G4 Plus Questions & Answers] jogawa:
THANK YOU!

I'm d/ling now and will follow your guide!

J
[Moto G4 Plus Questions & Answers] jogawa:
Yay! I got the phone back by flashing the stock ROM, then rooted using the guide, and I'm happy.

Thank you for pointing that stuff out xtermmin! I never thought to look for a ROM file with a name other than one that started with xt1644, and couldn't figure out how to search the directory. :) :(

You saved me.

Thanks again!

J
[Moto G4 Plus Questions & Answers] bleakoutside:
Filefactory link is acting very strangely. Its just loading the basic html, no css.

Could someone give me a mirror? Im as stuck as OP was without it.

EDIT: It took a few minutes but filefactory loaded enough of the css to get the download button. I may reupload somewhere and post a link when I get it downloaded.
[Moto G4 Plus Questions & Answers] Khanov:
http://www.filefactory.com/file/28u...PJ24.139-49_cid50_subsidy-DEFAULT_CFC.xml.zip

Enviado desde mi Moto G (4) mediante Tapatalk
[Moto G4 Plus Questions & Answers] mystx2112:
So i did the same thing as you by flashing the xt143 file, and now my adb will no longer work. The phone will not give me an RSA key prompt. I've deleted the .pub file in data/user/android. Any tips would be appreciated.
[Moto G4 Plus Questions & Answers] acharlest:
I'm getting a "could not find 'meta-inf/com/google/android/update-binary'" error when I try installing zip with TWRP and when I try sideloading. Any idea why?
[Moto G4 Plus Questions & Answers] xtermmin:
Which zip? The stock ROM zip? You can't flash it via TWRP. You have to boot into bootloader mode, connect to a computer, and flash via fastboot or one of those "easy flasher" tools.
[Moto G4 Plus Questions & Answers] Luniz2k1:
Stock roms for the 1644 can be found here https://www.androidfilehost.com/?a=show&w=files&flid=72578
[Moto G4 Plus Questions & Answers] xtermmin:
Read post #2.

Also, "ATHENE_6.0.1_MPJ24.139-13.1_cid50_subsidy-DEFAULT_CFC.xml.zip" is not for the US models. It's for the Indian model.
[Moto G4 Plus Questions & Answers] harsh9987:
guys help me i have moto g4 plus 32 gb(india) and i flashed this firmware but now my fingerprint doesnt work and network also i have to erase the modem1 &2 then i flash modem NON-HLOS.bin after that my network works but no fingerprint ???

\XT1626-XT1640-XT1641_ATHENE_6.0.1_MPJ24.139-23.1_cid50_subsidy-DEFAULT_CFC\

w Folder>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: moto-msm8952-B0.0E(*)

(bootloader) product: athene_16mp

(bootloader) board: athene_16mp

(bootloader) secure: yes

(bootloader) hwrev: P2A

(bootloader) radio: 4

(bootloader) storage-type: emmc

(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007

(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B

(bootloader) cpu: MSM8952

(bootloader) serialno: ZY2238ZFWQ

(bootloader) cid: 0x0032

(bootloader) channelid: 0xc0

(bootloader) uid: 3559230000000000000000000000

(bootloader) securestate: flashing_unlocked

(bootloader) iswarrantyvoid: yes

(bootloader) max-download-size: 536870912

(bootloader) reason: Volume down key pressed

(bootloader) sku: XT1643

(bootloader) battid: SNN5966A

(bootloader) iccid:

(bootloader) cust_md5:

(bootloader) max-sparse-size: 268435456

(bootloader) current-time: "Sun Aug 7 21:45:14 UTC 2016"

(bootloader) ro.build.fingerprint[0]: motorola/athene/athene:6.0.1/MPJ24

(bootloader) ro.build.fingerprint[1]: .139-23.1/1:user/release-keys

(bootloader) ro.build.version.full[0]: Blur_Version.24.24.1.athene.retai

(bootloader) ro.build.version.full[1]: l.en.US

(bootloader) ro.build.version.qcom: LA.BR.1.3.3-02720-8976.0

(bootloader) version-baseband[0]: M8952_70004.04.03.32R ATHENE_INDIA_DSD

(bootloader) version-baseband[1]: S_CUST

(bootloader) kernel.version[0]: Linux version 3.10.84-gcf01273 (hudsoncm

(bootloader) kernel.version[1]: [MENTION=387459]ilc[/MENTION]lbld52) (gcc version 4.9.x-google 20

(bootloader) kernel.version[2]: 140827 (prerelease) (GCC) ) #1 SMP PREEM

(bootloader) kernel.version[3]: PT Thu Apr 28 13:04:48 CDT 2016

(bootloader) sbl1.git: git=MBM-NG-VB0.0E-0-g83950b7

(bootloader) rpm.git: git=1dc910e

(bootloader) tz.git: git=9fa1804

(bootloader) hyp.git: git=9fa1804

(bootloader) keymaster.git: git=9fa1804

(bootloader) cmnlib.git: git=9fa1804

(bootloader) aboot.git: git=MBM-NG-VB0.0E-0-g4986429

(bootloader) qe: qe 1/1

(bootloader) frp-state: no protection (0)

(bootloader) ro.carrier: retin
[Moto G4 Plus Questions & Answers] jerry42570:
Any way of knowing if the file that was just uploaded on Oct 20 is for XT1644?
[Moto G4 Plus Questions & Answers] SoNic67:
Based on the name it seems to be the one that I am using now in my XT1644. But I got my file from the other place...
[Moto G4 Plus Questions & Answers] doctor_evil:
I just bought a XT1644 off ebay for cheap that isn't reading the sim and also isn't able to work with wi-fi either. I am hoping that it's also a case of incorrect firmware having been flashed on it. Keep your fingers crossed for me. LOL
[Moto G4 Plus Questions & Answers] SoNic67:
Hope is not that one that the owner was over here trying every possible solution without success...
[Moto G4 Plus Questions & Answers] pastorbob62:
Did you use PayPal? If the owner didn't warn you about the problem and listed it as a working phone then you can get a refund and return it. If you didn't use PayPal you may be stuck with it.
[Moto G4 Plus Questions & Answers] doctor_evil:
The seller appeared to specialize in used phones, possibly a pawn broker, or a cell phone reseller that does trade-ins. Those are usually the best kind of sellers, as they know enough to see there is a problem and will document it and price it accordingly, but they don't have the time or patience to fool with actually trying to fix the issue.

I will post back with my success or failure. I caused a original Gen Moto G to behave in the exact same fashion when I flashed the wrong firmware on it, and I was able to fix that one with a little trial and error. I learned a valuable lesson on being more careful, and that it was possible to just flash the radio from the firmware zip files instead of flashing everything.

---------- Post added at 10:50 AM ---------- Previous post was at 10:46 AM ----------

The issue was documented in the ebay listing, with photos showing the blank IMEI info. I've had success in fixing this exact issue on a original gen Moto G after I accidentally flashed the wrong version of the firmware on it. I wound up using the UK radio for it to unbrick that one's cell radio.
[Moto G4 Plus Questions & Answers] SoNic67:
Yeah, it needs to be the exact same radio.

Moto has a backup partition for bootloader and radio, and on flashing wrong ones it restores the "correct" one when booting with factory Android firmware. That's why after flashing TWRP, booting all the way into stock Android, it will be reverted to the normal bootloader. That's why we can flash LA.BR (Latin America / Brasil) firmware on our US phones - the baseband is "corrected" at the boot time.

But if you boot with a different that stock firmware, after flashing the wrong radio, than the "backup" capability is lost and subsequent firmwares need to have the exact original radio. And the "repair flash" of the baseband (radio) needs to be done with NON-stock firmware, because that one will "revert" the firmware to the old, wrong, one.

Don't forget, besides the software differences between models, there are also hardware ones.