yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] H4X0R46:
My favorites are Elite and ElementalX personally. Give those a shot and lemme know if any of em work for you :)
[Nexus 6  Original Android Development] sliverboi:
Off Topic: why does my custom recovery(TWRP) keep getting overwrite by stock recovery?
[Nexus 6  Original Android Development] H4X0R46:
That's a good question! This happened to me last week and had me thinking "huh, this phone never did this before." But after flashing TWRP a second time, it stuck. I'm not sure of the cause, but try reflashing it, and maybe using the fastboot boot [TWRP IMG] after flashing. I know some phones need this command to stick somehow.
[Nexus 6  Original Android Development] sliverboi:
I reflash 3x using nexus rootkit it still happens
[Nexus 6  Original Android Development] H4X0R46:
Try it manually with fastboot, that's my best guess.
[Nexus 6  Original Android Development] sliverboi:
IDK how?
[Nexus 6  Original Android Development] rignfool:
Recovery-from-boot.p... I think

Will overwrite your recovery after every reboot...

Flashing any SU solution should keep that from happening...
[Nexus 6  Original Android Development] H4X0R46:
Is this a new thing with the Nexus 6? Never had this happen until recent lol it's fixed now, just found it weird.
[Nexus 6  Original Android Development] sliverboi:
i still rather kick stock unrooted while with Multirom but thing is STOCK REcovery keep overwriting my TWRP custom recovery
[Nexus 6  Original Android Development] rignfool:
Try deleting

/system/recovery-from-boot.p
[Nexus 6  Original Android Development] sliverboi:
so i delete recovery from /system after i flashed TWRP?
[Nexus 6  Original Android Development] jbaumert:
I have stock 7.1.1 as primary w/ Franco Kernel. When I have MultiROM installed, I lose some of the kernel options (i.e. Double Tap to Wake). Reverting to official TWRP and running the MR uninstaller brings these options back. I'm thinking it has something to do with MR "injecting boot.img". Anyone else have this problem and find a work-around?
[Nexus 6  Original Android Development] rignfool:
I think so... I've always been rooted... So make sure you make a backup first
[Nexus 6  Original Android Development] BitOBSessiOn:
TWRP 3.0.3 (NO_KEXEC) + MultiROM (20170112)

Latest TWRP available for testing here.

Latest MultiROM available here.
[Nexus 6  Original Android Development] jbaumert:
What are the changes?
[Nexus 6  Original Android Development] BitOBSessiOn:
As you know, it's a blind build. Latest code from MultiROM and device tree and TWRP parameters reworked to try to fix slow data wiping.
[Nexus 6  Original Android Development] glockman4519:
Thank you sir, testing now.
[Nexus 6  Original Android Development] Sakiwinkie:
Whenever I test your version of Multirom it always asks me to Decrypt the data partition to continue. I am not sure what the password would be to decrypt it. So I end up going back to the unofficial 3.0.2 version which still works for my needs.

Do you have any ideas as to what I might be doing wrong?
[Nexus 6  Original Android Development] BitOBSessiOn:
Do you have your /data partition encrypted...? Remember that you can't use multirom if /data encrypted.

If I have time I will try to revise official TWRP code to see if I can fix the password issue (it should be able to apply default one).
[Nexus 6  Original Android Development] vsot13:
My phone is encrypted by default, I never mess with it. I'm using MR, like forever, never asked me for password. Every of your builds do ask for a password. I fastboot official and flashing back old version of MR allows me to using my phone again. Weird.

I hope you can figure out how to fix it. Thanks
[Nexus 6  Original Android Development] forgottenhacker:
Stock or custom rom?
[Nexus 6  Original Android Development] vsot13:
Custom
[Nexus 6  Original Android Development] dannycellestio:
Same, been using MR since forever with encrypted data, and with a boot password sometimes, but I've never been asked for a password when I didn't set one previously/have a boot password and being asked and denied when I write it, on any other builds beside of yours. The only one that matches my needs, the 10/18 build, boots M on primary and N on secondary succesfully, but I need your latest needs to access dev options on the secondary, and I cannot use any build from 006 (and matching MR) to the latest (tested). I don't know if this is a issue prone to being fixed.. but it'd worth trying. :D
[Nexus 6  Original Android Development] Captain_Throwback:
MultiROM should work fine on encrypted devices. You just have to include the necessary vendor files to support it. Do you have those included in your build?

EDIT: See here. That's the path where the device files expect to find them, so they properly get copied into the build. You can just grab the files I have there and copy them to your vendor/qcom/shamu/proprietary folder and it should fix your problem (unless your already have those there, in which case I have no idea).
[Nexus 6  Original Android Development] deeplyyoung:
Thanks to intervene here...really appreciated...Need your little help, if possible. So that we can get perfect build. As On OP3, if device is encrypted we can't use MR. cuz BitO earlier owning OP3 and now I think OP3T (correct me if I'm wrong).

Edited: you already helped above ..Huge thanks
[Nexus 6  Original Android Development] BitOBSessiOn:
Thx a lot for your help. Those files are included in current build (010). It's more difficult because this is a blind build... I don't have the device to test it.

Revising params, I see in BoardConfig.mk TARGET_HW_DISK_ENCRYPTION as false... I'm building with this set to true...

I will upload 011 as soon as it finishes to compile...

Thx again.

PS: Current DT to build this modded TWRP here.

---------- Post added at 18:29 ---------- Previous post was at 18:22 ----------

Latest 011 build available here for testing.

If it doesn't fix encryption stuff I would need more time to try to see why it doesn't work... but I can't guarantee this is possible, sorry.

As you know, this is a blind build... not tested... I've changed HW encryption switch to "true" and used standard OmniROM kernel source. (default config)
[Nexus 6  Original Android Development] vsot13:
No go for me. Thanks for your effort
[Nexus 6  Original Android Development] Captain_Throwback:
I'm assuming you're using [MENTION=3418703]Tasssadar[/MENTION]'s device files, right? Here's my BoardConfig.mk, and my device files are in the same location (though I only changed BoardConfig I believe). But compare to yours and see if it helps.
[Nexus 6  Original Android Development] Captain_Throwback:
[MENTION=6411851]BitOBSessiOn[/MENTION] [MENTION=5149175]deeplyyoung[/MENTION]

I was able to get my build box back up and manually kick off some shamu builds. If someone wants to test these builds (MultiROM zip & recovery) and see if decryption is working, it would be appreciated. If they work, those files can be used for future builds by BitOBSessiOn.

AndroidFileHost

Basketbuild
[Nexus 6  Original Android Development] deeplyyoung:
Welcome back Capt. ... You won't believe how much I'm happy seeing pop-up of this post... Buddy I will happily gonna try this build but main thing encryption which I can't check as I never ever use device as encrypted... But here plenty of active users who facing encryption password bugs, so they will going to report ASAP.

Guys whoever using MR and encrypted, just give a spin and get back with reviews.

Thanks Capt. Thank you very much for your support.

Edit: flashed and wiped/deleted two secondary ROMS within few seconds...So those who complaining about long time while factory resetting or wiping can give a try ..I'm sure that bug you not gonna face in Capt. Build.
[Nexus 6  Original Android Development] jimbomodder:
Well I was silly enough to run encrypted ( new to Nexus) so I'll happily test and report back.

Edit:.... No encryption problem for me [emoji3] [emoji3] [emoji3]
[Nexus 6  Original Android Development] BitOBSessiOn:
Thx, [MENTION=1162986]Captain_Throwback[/MENTION] , your build works. I suspect I'm missing some binary because my stripped down DT.

I will use your files as base for a new build... Is your branch uploaded to github or similar ? I would like to check that algo multirom no-kexec also works with encrypted /data partition.

Big thx.
[Nexus 6  Original Android Development] vsot13:
Finally it's working! Thank you [MENTION=6093703]Captain T[/MENTION]hrowback
[Nexus 6  Original Android Development] Captain_Throwback:
My branch of what? The device files? Those are just Tasssadar's files with the updates for NO_KEXEC. Or are you looking for something else. I gave you a direct link to my modified BoardConfig already, but I haven't uploaded that stuff to github as I only made minor changes and I didn't plan on doing this long-term. If you're looking for the MultiROM stuff, that's on github.com/multirom-htc.
[Nexus 6  Original Android Development] crosschris:
Thnk you [MENTION=6411851]BitOBSessiOn[/MENTION] for your work.. you stepped in to build for device you dont have and done well and to everyone else who made this multirom possible
[Nexus 6  Original Android Development] BitOBSessiOn:
Well, finally...

https://www.androidfilehost.com/?fid=745425885120701006

I guess this is basically the same that [MENTION=1162986]Captain_Throwback[/MENTION] 's but I've built kernel from sources, no_kexec set as default... I needed to build it... [emoji14]

Thx for shedding more light, Capt.
[Nexus 6  Original Android Development] H4X0R46:
Is this for use with captain throwback's multirom zip? Thanks again for taking this project up, both of you guys! :D
[Nexus 6  Original Android Development] BitOBSessiOn:
It should work, because he's also included no_kexec support, afaik.

You can also use my latest uploaded multirom.

TWRP code has been updated, to improve encryption and other minor fixes, so probably I'll build at least one more version to include these changes.
[Nexus 6  Original Android Development] garywojdan81:
I can report your last works fine with the Captain's multirom.zip
[Nexus 6  Original Android Development] deeplyyoung:
Thanks alot for giving us latest and greatest builds. Even without owning Shamu...
[Nexus 6  Original Android Development] forgottenhacker:
After you flash back to stock first thing you need to do is to let it run through the first boot and encrypt the storage then reboot back to bootloader then flash recovery, then boot into recovery then wipe everything. You can do format data partition in twrp itself but I found that to be buggy. Reboot to bootloader then run "fastboot format userdata". This will reformat the /data and /internal and remove any existing encryption lock on the storage. Wuala, encryption is gone...after that feel free to flash whatever you want. You will not need to do these steps again unless you end up encrypted again. TBH I

USED TO LIKE

encryption for the extra security, but after getting a taste of the non-encrypted butter smooth performance, I can never encrypt it again. Oh, and if you are flashing a boot image or kernel that forces encryption there is a thread somewhere on this device for FED Patcher which removes the forced encryption flags from the boot. Good Luck....Try it once and see for yourself...it's definitely worth the time and effort.
[Nexus 6  Original Android Development] vsot13:
Nah,not worth it. Thanks tho
[Nexus 6  Original Android Development] greeneyez15o:
Will this update force encrypt ?
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] zaidam:
I just reflash my lovely HIMALAYA to latest c_shekhar ROM. If I not mistaken, somewhere here have a patch to display name & tel number on SMS received instead of tel number only. Anyone can help me?
[NFC Hacking] Phurkus:
I just bought my fist pack of NFC chips with 888 bytes of writable memory. I'm wondering if there are any cool tricks to do with NFC other than just programing task.

I also have a keychain, any tips on what to carry on it?

I know the one of turning your computer on with tapping on NFC, any other ones?
[NFC Hacking] jacksepticeye:
Yeah, Google them
[Samsung Galaxy Pocket Neo S5310] QA Bot:
Q&A for AOSB-ROM unofficail port for s531x

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for AOSB-ROM unofficail port for s531x. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Samsung Galaxy Pocket Neo S5310] nv_vijaykumar:
THank you...

Please update cm 12 man.........
[Samsung Galaxy Pocket Neo S5310] Karthick Chandran:
im trying my level best :cowboy:
[Android Software Development] hellowasif:
Its final hope :P
[Android Software Development] osm0sis:
Did [MENTION=2777334]TKruzze[/MENTION] give you his Windows shell extensions to make the build process simple? If not, you should talk to him about it. :good:

Edit: Guess not.. looks like you've only updated the apks themselves; the library lists, etc. that the script uses are out-of-date. Use this at your own risk, people. :(
[Android Software Development] hellowasif:
Well I tried to contact Tkruzze but he has blocked the PM option same on G+ etc so i couldn't find any medium to contact him. I shall be very thankful to you if you could contact him for me :)
[Android Software Development] intrepid24:
[MENTION=4344925]hellowasif[/MENTION] thanks for bringing back PA GAPPS. I appreciate your hard work

I am using HTC Sensation 4G wit CM 11 and have been using PA GApps for a long time without any issues.

The most recent update from April 2015 causes Google Hangouts to crash continuously. I even tried a clean install - wiped system/data/cache
[Android Software Development] d.casper.b:
Thank you for helping out.

I assume you have kept everything as it was so that I can use my config file.

I like being able to flash more apps onto the system partition and that's why I'm so glad to see this.
[Android Software Development] Sandivisi:
big Thank :D
[Android Software Development] hellowasif:
Update

April 10, 2015 - 20150410

Google Calendar updated to v5.2-90091543 [Stock/Full/Mini/Micro]

Google Play Store updated to v5.4.11 [Stock/Full/Mini/Micro/Nano/Pico]

Google Play Movies & TV updated to v3.7.20 [Stock/Full]

Google (Search) updated to v4.4.9.16 [Stock/Full/Mini/Micro/Nano]

YouTube updated to v10.13.54 [Stock/Full/Mini]
[Android Software Development] GuestK00268:
Thank You.
[Android Software Development] hulicow:
[MENTION=4344925]hellowasif[/MENTION]

Hi I found a major bug in Mini GApps Package:

1. Hangouts - Opening Hangouts on device only force closes, the only workaround is to delete system app file and then download Hangout from Play Store.

2. Google Calendar does not replace stock AOSP Calendar. No Google Calendar found on application drawer/list when trying to find.

I didn't experienced those on official PA GApps made by Tkruzze. I hope you will fix this issues. Thanks for the packages. :)
[Android Software Development] rogers11:
Micro-Gapps flashed fine on my Galaxy S2 with CM11. Thanks a lot.
[Android Software Development] intrepid24:
yes, I can confirm as well. Just tried a clean install and I had the same 2 issues with the Stock GApps. I restored my previous installation
[Android Software Development] ltodorov:
I'm trying to install pa_gapps-modular-pico-4.4.4-20150410-signed.zip but its signature can't be verified. Could you help me, please?
[Android Software Development] Ok_Kaleidoscope5109:
[MENTION=4344925]hellowasif[/MENTION] I just found this thread, but this is wonderful work you are doing!
[Android Software Development] mark manning:
Closed per OP request
[General Questions and Answers] hossam55:
hi

i want to know what makes custom rom compatible with my device is it the processes or what ?

so i have huawei ascend y 320 u30 and it has mt5672 and i can't find any rom for it

can i use any rom for mt5672 or it might be incompatible with it ?

what is your recommendations ??!

thanks
[General Questions and Answers] LS.xD:
A custom rom must be created / ported specilly for your specific device. It must be compatible / fitted for with ALL of your phone's components.
[General Questions and Answers] hossam55:
so rom like this one here

mt6572roms.blogspot .com/2014/09/rom-afterlife-60-for-mt6572-features.html

won't be compatible with my phone ?
[General Questions and Answers] LS.xD:
You can't install it without further modifications I suppose. I haven't found any confirmed to work custom roms for your phone :( Have you already rooted your device and installed a custom recovery?
[General Questions and Answers] hossam55:
what further modification are we talking about here?

i didn't rooted nether installed any thing
[General Questions and Answers] LS.xD:
I found this link for the Afterlife 6.0 rom --> CLICK ME

Your phone is listed as "needs to be ported". The point is that there are just some poor informations from different blogs but not a single thread in a forum which provides any reliable informations.
[General Questions and Answers] zelendel:
There are many tuts on XDA on how to port a rom. One of the main issues is that cheap chipset that these devices use. They never release the kernel source for the device so porting at best is what you get and most of the time there are issues that cant be fixed
[General Questions and Answers] hossam55:
any easy tutorial on how to port a rom

and porting a rom will that Ensures that dual sim will work and the 3G ?
[ONE Q&A, Help & Troubleshooting] ryaneu:
I have a serious issue after upgrading to lollipop. After flashing the CM12 nightlies and a custom lollipop rom. I could not get LTE signal and my data connection will keep switching between H and H+ with frequent disconnections and loss of signal (exclamation mark).

However when I flashed the O5Q kitkat modem + proximity sensor fix, my LTE signal came back stable with no more disconnections or loss of signal.

Weird issue I must say. It seems like the network I'm using isn't compatible with the CM12 nightlies modems.

Anyone else encounter this issue?
[Samsung Galaxy Mini] celtol:
Hello,

i'm using CM11 M12 From midzian21, today i saw the Port Sound Mod Dolby by D2Y aka E. When i flash it according to the instruction, i restart it and then my phone get bootloop(boot animation repeat for about 30 minutes) i flash the stock rom first the latest for my country, then few from other forums and this not help bootloop stuck. So i try find out how to fix it, then i found Rescue PDA Final and this had not even start. Please can you help me? (Sorry, for my english)
[Samsung Galaxy Mini] midzan21:
1) try to get in recovery and make factory reset (hint: go to download mode, then reset device and as quickly as possible press vol up + vol down + home to enter recovery)

2) I'm not responsible for any mods which I didn't tested on my build, so that D2Y Indonesian guy maybe didn't tried it out properly or you had some other mod which maybe make problems

3) I was testing back in days some mods but barely oworks just because it had older base for ROM (builds prior August 2014 most of time) and if I made it to work on latest CM11 then I had some problems with SystemUI and FC's

Sent from xda free using Mini 2 with Stock ROM (reverted so my mom can use it)
[Samsung Galaxy Mini] celtol:
Thanks for fast answer,

I do not have access to recovery tried at least 10 times and nothing.
[Samsung Galaxy Mini] midzan21:
hint: try to flash cwm any 6.0.x version with Odin and then try to get in recovery...

also note: if you get in bootloop after flashing mods - do a factory reset from recovery.... it helps a lot.

sent from some crappy old laptop
[Samsung Galaxy Mini] celtol:
I tried this solution before, still i have no access to recovery.
[Samsung Galaxy Mini] celtol:
I had bring my phone to GSM service in my city, and they repair it. Thread to close
[Samsung Galaxy Mini] med darkman:
i have a problem like that , i tried to enter the recovery mode but could not ,and i tried to enter the download mod but it keep crushing ,i wonder if someone could hep me
[Nexus 5 Q&A, Help & Troubleshooting] Pranjal53:
I flashed cm12 nightly and its working great but i miss the stock android and want to revert back to android 5.1 build number LMY47I.

so i just have to flash the factory image and wipe all the data?

while installing cm12 i had to downgrade my boot loader from hhz12f to hhz12d so do i need to flash the bootloader image first or just straight away flash the factory image??
[Nexus 5 Q&A, Help & Troubleshooting] beekay201:
You could use a flashable stock rom put together by someone here at XDA, but I would advise you to back up your userdata and flash factory images. You can afterwards push your userdata back to /sdcard/.
[Nexus 5 Q&A, Help & Troubleshooting] upndwn4par:
Search is your friend.

http://xdaforums.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
[Moto G Q&A, Help & Troubleshooting] Xaenir:
Hello guys, I have a problem on my Moto G 2013 XT1032 which is that I've did the CM12 nightly on my phone and when I switch on, the screen was on and after few minutes he switch off with no reason. The phone is on (I can see the led and the sound) and the touch command work. I flashed the ROM with TWRP 2.6.3.0 (installed by the Flashify app) and I run this custom recovery by using Flashify (doesn't work on fastboot mode), flashed the GAPPS after it but I forget to flash the SU (Doesn't know if it's needed).

Thanks for future help and sory for my bad english (I'm French).

I'm gonna try this : http://xdaforums.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
[Moto G Q&A, Help & Troubleshooting] Xaenir:
Okay I think the problem is solved it's a bug with the lumonistiy screen
[JAMin, XDA Neo, S200 ROM Development] cesardeluxe:
There is a release coming from Vietnam (thnks John-Wu!)

It is said to be stable and fast.

Gets everything working and consuption is moderated. It is a clean version.

If you want to try it, just get it from HERE

Don't forget to post your opinions about it.

A fine release adviced in http://todopocketpc.com by tiggerbcn

Respect!:rolleyes:

PASSWORD is

PDAVIET
[JAMin, XDA Neo, S200 ROM Development] Eladio.Linares:
Password? Must wait again?

Thanks, Eladio
[JAMin, XDA Neo, S200 ROM Development] llvll:
password??!

password plz?
[JAMin, XDA Neo, S200 ROM Development] cesardeluxe:
Yeah sorry i am waiting too for the password. I 'll post it ASAP
[JAMin, XDA Neo, S200 ROM Development] John-Wu:
sorry but this release is not from Thailand. As you can see in the word "PDAViet", it comes from Vietnam :-)

The password is PDAVIET

but there ist an better release which called: PDAVIET 1.0. With this Rom, you can cook your own EXTROM

Download at: http://rapidshare.com/files/32493040/WM6_Prophet_PDAViet_v1.0.zip

version 1.1:

http://rapidshare.com/files/32493762/WM6_Prophet_PDAViet_v1.1.zip

version 4.0.0.0.1

http://rapidshare.com/files/32714434/WM6_Prophet_PDAViet_v4.0.0.1.zip

password is the same.

all ROMs:

- over 31MB free memory

- fast

- stable

- Wifi, IR, BT works

V.1.1:

- PIM Backup 1.9

- MIDlet Manager 11.1.7.1023

- BatteryStatus 4.02 build 203

- CommManager 1.6 (9 icons + skin CrossBow)

- Macromedia Flash ActiveX 6

- remove Voice Command

- remove Market Place and Windows Update

--> but as far as i can see: the best ROMs at the moment (date 22.05.07)

have fun with it!

John
[JAMin, XDA Neo, S200 ROM Development] ts3010:
the 2nd one is great
[JAMin, XDA Neo, S200 ROM Development] elDoctor:
G3 or G4

Hi, can you said me if this version is form G3 or G4? after burn into my S200, it's stay on the first splash screen.

thanks.
[JAMin, XDA Neo, S200 ROM Development] Carty:
Will give a try and let you guys posted..

Regards,

Carty..
[JAMin, XDA Neo, S200 ROM Development] cesardeluxe:
Both. HAve you made a hard reset after flashing? HAve you flashed from a no vendor WM5?

CIao