yashsingh1/xdaforums huggingface dataset:
[General Topics] GeTex:
So I've got a discussion thats bugged me for ages. I've always wondered about bad IMEI's/ESN's. Phones that cannot be used because they are reported stolen

It has a great purpose, It's like if someone stole your car, the car nolonger can start(bad analogy, don't laugh). But it leaves me with something that really really bugs me

Now what happens to people who legitimately buy devices second hand from original owners and such and then the original owner decides to be a you know what and blacklist the device? Or worse, what happens then to all of these devices in their after life? We now have a pile of useless phones that there seems to be no procedure to ever unblacklist these devices... thats the part that sickens me. We literally are rendering useless perfectly good phones that have the ability to be reused, be it the device is sent to the manufacturer first for refurbishing, the original owner gets the device back into their possession. I just feel there so many phones out there that are rendered useless when they are really expensive pieces of equipment... I Know there's always "changing the IMEI" but we aren't going the illegal route here.

Anyone else have feedback, Idk why it just gives me this feeling of being very wasteful.
[General Topics] Planterz:
XDA simply doesn't want to dabble in any "grey" areas. There may be legitimate/legal reasons for changing an IMEI. Most (or at least many) cases, the reasons aren't legitimate or legal. So, to avoid any confusion (or liability), discussion is prohibited. Similarly, certain "patcher" apps. Lots of legitimate uses, like back-ups/restores, root app removal, etc. But also lots of illegitimate uses. So XDA takes the blanket stance of not discussing such apps. It saves them from any hassle of legal/ethical issues, and alleviates the moderating staff from sorting out the fraction of legitimate questions from the dubious questions, lies, damned lies, and flat-out admissions of nefariousness.

If you buy a phone without doing your research into its IMEI or its unlock status, then I think it's your own damn fault for getting burned. Just my opinion. If you're asking about changing IMEI, then either you screwed up in that regard, or you've knowingly purchased a phone with a bad IMEI (buying a "parts" phone off eBay or craigslist), or are the cause of it having a bad IMEI itself (failing to fulfill a contract agreement). Regardless of the reason, even if it's innocently/ignorantly getting burned by an unscrupulous seller, such discussion is barred from XDA because of those other concerns.
[General Topics] GeTex:
My exact question is at the end more than anything, I see this being wasteful of phones? If a device is blacklisted for being "stolen" but is later found by the original owner? Then what? Still a dead device? I just think there's hundreds of good phones out there that could still be used even if they are found or returned or by who knows what means end up on the service providers desk cause someone found it and sent it to the police or something and it's reunited with it's owner...

You get where I'm going with this?

I SPECIFICALLY STATED CHANING IMEI's, HOW-TO's, and such are NOT to be discussed here. I even said this was a discussion, not a Help me thread... Sorry I feel just like you didn't read my op :/

to make it more basic, I think the current system is super inefficent and wasteful and there must be better solutions out there or some future legal way to deal with unblacklisting phones(i.e. original owner finds phone, goes to carrier, proves their identity with an ID and clearly the carrier can look up the account and devices)
[Miscellaneous Android Development] BadGuy:
Hello everybody!!!

My name is Raphael (kyleve on xda) I have 14 years and have a trend lite (kyleveub) but as we all know there aren't many ROMs for this device:

But with everyone's help we can include this device on xda and motivate more developers to create ROMs for this device (lolipoop, KitKat between and others) because it has several people that have this device and they would like to have multiple ROM options for that device to help get that damn lag.

Because I know that all together we can do what the Samsung among other brands failed to do.

Basically, and all I have to say ....

First I and some developers we need to talk about it and form a group to begin developing ROMs for this device and so to create a category for the device.

I ask everyone who want to participate in the project, send me a message in the hangouts:

olocogameplays552@gmail.com

Enviado de meu GT-S7392 usando Tapatalk
[Non-Touchscreen Windows Mobile Other] ol2:
Using HTC Cavalier with WM6, trying to get my mail stored on the storage card.

The registry edits work to direct the mail onto the storage card, but when the phone boots up, the storage card does not start soon enough and the mail program creates a "Storage Card" directory in main memory. Then when the "real" storage card starts, the phone renames it to "Storage Card2" which messes everything up big time.

Anyone got any ideas on how to fix this? Please help.

I have tried renaming the in-memory storage card directory to "Storage Card.bak" and rebooting, but then I get yet another "Storage Card" created in main memory in addition to the "Storage Card.bak" and "Storage Card2".
[Networking] flamery:
Hi guys,

I'm working on an app at the moment but I can't get it to work.

I am trying to load a webpage by its IP address, usually this will not work because the server doesn't know what site you want to access in the case of a shared hosting etc. So I am injecting the "host domain.com" header into the request. However the page will still not load.

Anyone got an idea of how I can do this. I know I can use the host file but I'm trying to achieve it without admin privileges. on the pc.

Using wireshark the only difference I found in the packet were GET string in the HTTP header so not sure if I'm missing something..
[Networking] 0ptr:
There is no way to help you if you don't provide any sort of source code or dump of the packages you're sending.
[Nexus 6P Android Development] npjohnson:
[MOD] MultiROM v33 -- Beta 4

Reserved
[Nexus 6P Android Development] npjohnson:
Reserved.
[Nexus 6P Android Development] npjohnson:
Reserved
[Nexus 6P Android Development] 500 Internal Server Error:
Downloads

Reserved.
[Nexus 6P Android Development] 500 Internal Server Error:
changelog

Reserved.
[Nexus 6P Android Development] 500 Internal Server Error:
Extra information

Unlike some of the other 64-bit MultiROM ports, this port does have kexec-hardboot enabled, which is less risky and speeds up boot into secondary ROM. Anyone porting MultiROM to a Snapdragon 810 device may find the source to be useful.
[Nexus 6P Android Development] nathanchance:
Just a heads up, your

Spoiler content hidden.
[Nexus 6P Android Development] keaheng:
thanks that works
[Nexus 6P Android Development] davidwilson83:
Oh awesome! Subscribed and will install as soon as I get off work. Thank you for your hard work [MENTION=5924703]500 Internal Server Error[/MENTION]

#whiteuimustdie #themesmatter
[Nexus 6P Android Development] tacosrdelicioso:
Yeahhhhhhhhhhhhh!! Finally. Very happy to see this
[Nexus 6P Android Development] Wohee:
Nice work! Can't wait to try it out.
[Nexus 6P Android Development] galaxys:
Definitely needed! Super!!
[Nexus 6P Android Development] npjohnson:
Congrats on this man! The Hardboot Patch will be indefinitely helpful for ARM64 users in the future!

No noticable bugs so far. I'm going to build MR with USB support sometime this weekend, will test, and get back to you.

Something we are going to have to deal with that other devices won't is the /vendor partition on the 6P. For example, user install Layers Overlay on stock ROM, now CM based secondary won't boot due to conflicting Layers/CM theme. Th8s wasn't a problem on the Nexus 6 because it didn't have a /vendor, but simply had a /system/vendor for each ROM.

A simple way we could bypass this is to set up a virtual /vendor (like we already have for /boot) and give the option when making the ROM to use a virtual /vendor, and then if the user opts to do so, they could base it off a vendor.IMG, or their current /vendor. If this doesn't sound like something you'd want to do, we could also tell the secondary ROMs to look at /system/vendor, and not ever mount /vendor (though this'd require that MR inject the current /vendor partition contents into /system/vendor on Secondary ROM flash.

Could you make a separate thread in the Original-Development about the HardBoot patch, and irlts inner workings? Tasssdar made a thread like that for the Nexus 6, and it helped a lot of kernel devs get up to speed quickly. It also contained example commands, etc. and was a great place for Kexec newcomers to learn.

Again, Congrats!
[Nexus 6P Android Development] DJBhardwaj:
And finally its here! Glad you dealt with kexec-hardboot :)
[Nexus 6P Android Development] 500 Internal Server Error:
This should be doable - I can look at how MultiROM mounts the system partition and try to do the same for vendor. However, I'm not sure if there is a need for that since CyanogenMod didn't ship with any custom vendor binaries. I'll look into it when a ROM actually needs it.

Sure: I'll post a guide on porting it to other devices. The TLDR version:

- It's based on Geoff Levand's arm64 kexec patch as adapted by webgeek1234 to build on Android

- the hardboot part works by:

kexec call is made to load kernel, ramdisk, and device tree at specified addresses

kernel makes a temporary copy of this data in RAM that won't be overwritten at reboot, along with some code to copy it to the final positions

kernel reboots

Hardboot kernel checks that a hardboot is required, and jumps to the copier code

Copier code copies the new kernel to the final address and jumps to it

New kernel boots.

The extra copying code is needed since on 32-bit ARM the kernel can copy itself to the desired position; on arm64 it can't and extra code is needed. In addition, on 32-bit ARM the position of the ramdisk and device tree doesn't seem to matter; on the Nexus 6P however they have to be placed at the same location that the real bootloader uses.
[Nexus 6P Android Development] Tylog:
Omg. Amazing. The only thing i am missing on the 6P. You are the men! Thank you so much.
[Nexus 6P Android Development] akhilnarang:
Great work!
[Nexus 6P Android Development] npjohnson:
Thank you! :highfive:
[Nexus 6P Android Development] steviemch:
Excellent work, fingerprint authentication working without a hitch on my secondary ROM.
[Nexus 6P Android Development] jamescable:
So, I've been doing my best to read up before I install, I have used multirom on my hammerhead, shamu, and Flo and want to on angler, but....I have read about the device lockout.....what causes this and has it been fixed?
[Nexus 6P Android Development] nadiros:
You obviously know the risks of this software to begin with. The lockout has been fixed apparently with this latest release. There is a discussion in the General threads regarding TWRP and lock screen security which may be helpful.
[Nexus 6P Android Development] opz187:
I restored a backup as a secondary rom last night, no lock out, finger print works, great work dev. seriously, you kick a$$ man thank you for work I cant believe how well it's running. hats off to you!
[Nexus 6P Android Development] ncsuwolfs:
flashed the new stable recovery and installer. when i try to boot into secondary rom it goes to black screen then reboots asks for pin again then proceeds to reboot to recovery. primary works fine. im sure its something i did or didn't do. any ideas? (i tried to re inject boot again but didn't fix it) if it helps, im running pure nexus with elementalx kernel for primary, and resurrection remix and dirty unicorns as secondary.

edit: reflashed recovery and multi rom with same result
[Nexus 6P Android Development] kingoddball:
This is brilliant!

Everything is working brilliantly!

No idea how you managed it but it's great!
[Nexus 6P Android Development] npjohnson:
Delete and reflash the ROMs.
[Nexus 6P Android Development] ncsuwolfs:
seems to have fixed it, Dirty Unicorns just booted. was holding off trying that because i just got Resurrection remix the way i wanted it but it is what it is lol. Thanks for all your hard work!
[Nexus 6P Android Development] subhjvlz:
Faced the same issue as [MENTION=5621213]ncsuwolfs[/MENTION] . Device was rebooting when I tried to unlock the screen. A delete and reinstall of secondary fixed the problem. Now I am successfully using stock MMB29Q as primary and CM nightlies as secondary. The two different concepts of theming layers and CMTE live in the same device peacefully. Fingerprint and everything else is working as expected, Just loving it. Thanks for the awesome work.

Just a small question how to update the CM nightlies via delta updates ?
[Nexus 6P Android Development] npjohnson:
Good to hear. I'll add a note about the passcode/recovery loop to the OP tomorrow.

The CM Delta updates question is not for this thread. But, the only CM Delta Updater I have ever seen is CyanDelta (in the Play Store), but I am insure of this works with MultiROM (or even Marshmallow for that matter, as it uses block updates instead of the old manual extraction/permission KitKat style of update).

Make a backup of your Primary, Secondaries, and Internal Storage, then try it I guess, its uncharted territory. But you run 0 risk of a hard brick, just a TWRP solvable soft brick.
[Nexus 6P Android Development] subhjvlz:
I 'ed surely want to give it a go. But all my previous attempts to install/recover/restore from backup have not yielded desired results.
[Nexus 6P Android Development] DJBhardwaj:
Download delta updates, don't yet flash them. Boot into TWRP and manually flash them via multirom menu :good:
[Nexus 6P Android Development] subhjvlz:
How can I flash Delta updates of CM Nightlies in the multirom scenario. CM is my secondary ROM stock being primary. I am using CM downloader app to download Delta updates, the app gives me a 1gb zip after applying the 35 MB Delta update.

http://xdaforums.com/showthread.php?p=65646485
[Nexus 6P Android Development] DJBhardwaj:
Just like you flash gapps on secondary ROM ;)

Of course, you will have to grab hold of the delta zip. It located in CM Downloader folder in storage.
[Nexus 6P Android Development] subhjvlz:
The 35 MB Delta zip doesn't show up for flashing in recovery. :what:
[Nexus 6P Android Development] DJBhardwaj:
Weird. Just move the zip to another location, like the root of the internal storage.
[Nexus 6P Android Development] galza:
just updated mr from beta 4 to stable,installed secondary rom and when i boot up it boots into internal rom and i dont get the menu to choose from which rom to bootup.any ideas?

thanks for an awsome job dev
[Nexus 6P Android Development] DJBhardwaj:
I presume you haven't flashed the Stable 1 MultiROM Installer zip - https://multirom-nexus6p.github.io/multirom-20160302-v33-UNOFFICIAL-angler-STABLE1.zip

A little advice - Make sure to update MR Recovery and Installer zip files, every time when you update.
[Nexus 6P Android Development] galza:
i did flash both the installer and the twrp recovery and yet i cant choose the rom to boot when the phone starts...
[Nexus 6P Android Development] ncsuwolfs:
reinject boot sector from recovery
[Nexus 6P Android Development] galza:
sorry for the noob question but how do i do that? step by step please....:eek:
[Nexus 6P Android Development] ncsuwolfs:
from recovery click multirom then click 3 dots in upper right hand corner, click inject multi then swipe to confirm
[Nexus 6P Android Development] DJBhardwaj:
Is your storage encrypted? Cross check it.
[Nexus 6P Android Development] galza:
thanks dude that solved the issue :D
[Nexus 6P Android Development] gqukyo:
I can't seem to get MR to work anymore. It worked before but now I can't get the auto boot option to show me list of roms and I've injected the MR thing multiple times, tried different supported kernels including the modified stock one. I've tried uninstalling it via the uninstall zip. Starting from scratch, still doesn't work. In fact, now I can't even select my internal rom. Using PureNexus 2/18 build as my main rom. Something similar happened to me on my Shield Tablet and I gave up on that since it's just a tab I use at home but I would love to try different roms out especially with the fingerprint authentication fixed. What should I try now to fix it?
[Nexus 6P Android Development] AmyClaraRose:
I was wondering if you were planning to push this to official multirom all github so I can use play store version to install
[Nexus 6P Android Development] 500 Internal Server Error:
We did open a pull request https://github.com/Tasssadar/MultiROMMgr/pull/100 but Tassadar hasn't accepted it yet.
[Nexus 6P Android Development] emam damon:
sorry guys for noob question

how can i decrypte my nexus6p?
[Nexus 6P Android Development] Aztriltus:
Format data including internal storage. So back up your files first to a computer or something and wipe everything.

Then load the ROM and kernel files into your phone and flash them. Note that the kernel must not force encryption and also need to support multirom.

Then once you're booted to your new ROM, your device will show you that it's unencrypted.
[Nexus 6P Android Development] Eru Ilúvatar:
Tasssadar has just replied!

:highfive:
[Nexus 6P Android Development] akshaysalunke13:
Even I am unable to boot multi rom.I don't get any selection screen.First ROM boots by default.ANyone else with such an issue?
[Nexus 6P Android Development] ncsuwolfs:
look a page or two back
[Nexus 6P Android Development] steviemch:
It may be prudent to add a small section about injecting boot after an update to the op, I used MultiRom on mako so already knew. It'll save the repetitive questions from people who don't tend to use the search function.
[Nexus 6P Android Development] akshaysalunke13:
Instead some people tend to try all the options( including injecting) and maybe then only post such questions !
[Nexus 6P Android Development] gqukyo:
If you guys are referring to just injecting the boot sector, I already did that multiple times to no avail. Also did notice that on the MR manager apk posted in the OP states that there's an update to the recovery which I selected to download and update and does say it flashed successfully but still can't see internal rom and won't show list at boot.
[Nexus 6P Android Development] ncsuwolfs:
recovery, multirom, click 3 dots in upper right Hand corner, inject multi, swipe to confirm, or you already did that?
[Nexus 6P Android Development] gqukyo:
Yup, multiple times via that method as well as after flashing anything
[Nexus 6P Android Development] Swamphound:
When I've had trouble flashing EX kernel linked in OP on the ROM I'm trying to boot fixed it.
[Nexus 6P Android Development] Swamphound:
FYI Multirom app from the playstore now let's you edit icons. Pointless I know but cool.:)
[Nexus 6P Android Development] dirtyreturn:
Is there anyone having any trouble swapping primary with secondary ROM?
[Nexus 6P Android Development] 500 Internal Server Error:
We haven't tested this and it's likely that bad things will happen. Do you have any logs that can help us diagnose the error? (dmesg, logcat, TWRP log)?

Can you:

1) Flash the latest MultiROM zip

2) inject the boot sector

3) boot into your primary.

4) get a dmesg

The dmesg contains MultiROM's logs and will help us diagnose the issue.
[Nexus 6P Android Development] dirtyreturn:
Here is a dmesg log. http://pastebin.com/WksnFDb0 edit - this was taken directly after trying to swap primary and secondary roms. Hope it helps.
[Nexus 6P Android Development] 500 Internal Server Error:
The recovery dmesg doesn't seem to show anything weird: when does swapping ROMs fail? Can you grab the TWRP recovery log (it's on /cache, I think) if it fails in the recovery, or /sys/fs/pstore/console-ramoops after a reboot if it fails on bootup?
[Nexus 6P Android Development] dirtyreturn:
here is the console-ramoops https://drive.google.com/file/d/0BwP1hSe-Z6szZ1hOSUFoN25RR2c/view?usp=sharing here is the log https://drive.google.com/file/d/0BwP1hSe-Z6szYTktdm1HZXNmOTg/view?usp=sharing here is the last_log https://drive.google.com/file/d/0BwP1hSe-Z6szM0l2aU56Wk5tSkE/view?usp=sharing The funny thing, that since upgrading multirom and recovery to stable from beta4 i believe this was the fourth try for me to swap roms. I can say that this time it worked. Logs anyway, in case they mean anything.. thanks.
[Nexus 6P Android Development] starscream86:
I'm new to multirom so forgive my ignorance, I used the market app to install multirom the recovery and the kernel. But it's showing that recovery is not installed however I do boot into multirom/twrp recovery when I boot recovery.. Should I worry about the installer app not showing as installed?
[Nexus 6P Android Development] dirtyreturn:
Same thing happens here
[Nexus 6P Android Development] sketron13:
Same here. Then when I choose the secondary ROM in the app, it gets to the Google screen and appears to reboot into the primary ROM without any other options during startup. Tried a few different ROMS, gapps, kernels as both primary and secondary. :/
[Nexus 6P Android Development] metalcated:
Same here as well.
[Nexus 6P Android Development] Swamphound:
I would manually install beta 4 as in the OP and just use the app to switch ROMs for now. It shows recovery not installed for me too but it's working just fine.
[Nexus 6P Android Development] metalcated:
I've done the manual process as well but don't get the boot menu to choose which Slot to boot. I have tried both Franco and stock both kexec patched. Same result.
[Nexus 6P Android Development] Swamphound:
Flash the installer zip in recovery and download the app from the Playstore. Also try EX kernel.
[Nexus 6P Android Development] metalcated:
Done, done and done. Same result, no boot menu.
[Nexus 6P Android Development] TWong1200:
Glad I'm not alone. Same here. I haven't given up yet!!
[Nexus 6P Android Development] Swamphound:
Sorry I'm not more help. Only other thing I can think of is that I had the debug app installed and the beta 4 zips then installed the updated app from the Playstore over that. I've got 10 ROMs installed including a stock unrooted and two CM builds.
[Nexus 6P Android Development] steviemch:
Anyone else running DU as secondary with latest elementalx kernel (1.11)? After flashing the kernel to secondary, the ROM refused to boot, instead rebooting straight back to recovery. Definitely a kernel problem as flashing 1.10 returned everything to normal. Just checking I'm not the only one.
[Nexus 6P Android Development] subhjvlz:
Check the SElinux status of ROM and kernel, they must be compatible
[Nexus 6P Android Development] steviemch:
Yeah I did, including switching between enforcing and permissive just to double check. I'll give it another try at some point, not that big of a deal.
[Nexus 6P Android Development] FuMMoD:
I wish I had that kind of time to test all those! I miss the icon feature a lot though.
[Nexus 6P Android Development] Swamphound:
Well you didn't get to be a RC by not testing! Up to 10 now lol.
[Nexus 6P Android Development] Pheoxy:
Is your SELinux set to Enforcing? Same issue with twrp app a while ago.

It couldn't read recovery due the SELinux policy in Enforcing. I think Permissive was needed.
[Nexus 6P Android Development] metalcated:
Is stock unrooted your primary?

---------- Post added at 09:06 AM ---------- Previous post was at 08:41 AM ----------

As a follow up, I removed xposed and tried to see if that made a difference, but no change. Not too sure what else to try at this point beyond going back to stock unrooted and starting this all over again. I'm open to suggestions.
[Nexus 6P Android Development] akshaysalunke13:
[MENTION=5848265]npjohnson[/MENTION] [MENTION=5924703]500 Internal Server Error[/MENTION] Please help me.! I am unable to use multirom . I don't get the menu to select which ROM to boot into.Primary ROM boots automatically . I have flashed MRtwrp,MR,Modified kernel and injected boot sector several times.Also I have reported this issue on github