yashsingh1/xdaforums huggingface dataset:
[Moto X Android Development] Nicene Nerd:
Developer pkgmaker.sh Tutorial: Creating an Xposed Framework Package

Say you want to make a package that installs the Xposed framework, since that requires writing to /system. Here's how you would do it with Suicide Flash (assuming you have already rooted the phone):

Open a terminal window to your Suicide Flash root folder. Then sudo su.

Pull a system image. One way to do that:

adb root
adb shell dd if=/dev/block/platform/msm_sdcc.1/by-name/system /sdcard/originalsystem.img bs=1024
adb pull /sdcard/originalsystem.img

Run the pkgmaker script like this, assuming you're using a rooted XT1049 on 4.4.4, but you don't know the offset of the system partition, so you want to pull it via ADB. The script will be placed in output/xposed-flash-package.zip.

./pkgmaker.sh originalsystem.img XT1049 "Stock 4.4.4" ADB xposed-flash-package.zip

The script will pause when originalsystem.img is mounted for writing. As root, copy the Xposed app_process file (which you can extract from the APK if you need it) to "mnt-originalsystem.img/bin/app_process". Then press enter.

The script will continue executing, hopefully without errors.

Voila! Your package xposed-flash-package.zip is ready to upload and/or flash.
[Moto X Android Development] Cindex:
Finally!

The XT1049 has stumped me for a long time, but finally someone found a way!

Just a thought as I'm going into this, there's no mention of drivers for linux. Obviously this isn't to "user" level yet, and I wouldn't put myself too much beyond that, but it's a nice thing to include. I'll be trying it later, but are the drivers for USB/ADB the same as the emergency mode drivers? I'm kind of nervous to try because of the soft brick, and there doesn't appear to be any mention of how the flashed file that bricks it is put back. I'm assuming I can pull the original image before I flash the new one, but I'm not sure yet.

Also, if you have it tested and everything with Republic, I would appreciate a torrent or hosted file somewhere. If there isn't one before I finish, I'll post it.

---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------

Sorry for the double post but I can't edit yet, just realized that the zip file there is all that's needed for Republic. I was going to post the ADB/USB driver setup link for linux, but I'm not allowed yet.
[Moto X Android Development] Nicene Nerd:
You shouldn't need to do anything special for Linux drivers. It works straightforwardly as long as you have fastboot and ADB. The flashed file that creates the softbrick is included by the package maker script in every Suicide Flash package, so it is easy to unbrick. In fact, I can upload another package just for unbricking if you'd like.
[Moto X Android Development] Nicene Nerd:
Added a BusyBox package for XT1049, and added root and Xposed packages for XT1060.

Edit: also added root packages for XT1058 on both KitKat and Lollipop, plus Xposed for XT1058 KitKat.
[Moto X Android Development] Cindex:
That's good to know, I looked around and couldn't find anything on the driver for the Qualcomm Emergency Download mode. I suppose not needing one would be why. Actually some kind of emergency package to unbrick might be good. Now that I see the script in there I don't have a problem, but someone might like it.

So now I'm wondering if I actually have to do a factory reset again, or if I can just flash the SBF file itself and not have to wipe. I'm not sure how big of a difference there is, because I did the factory restore recently and the OTA update was like 6MB or something. I wouldn't think there's be an issue flashing it rather than factory restore. Any ideas?

Also, if anyone knows a good way to do this with Virtualbox it would be a nice addition. I'm personally not going to bother since I already have a bootable Ubuntu USB, but it seems that most people would rather set up a VM with a small linux distro. If it had the tools baked in, it would make it an easy process.
[Moto X Android Development] Nicene Nerd:
Technically, the only reason for the SBF is because when you install OTA updates, files may end up in slightly different positions depending on the circumstances. For this to work, you must start with an identical system partition to the one used for making the package. So all you need to really do is extract the system.img and flash it, if you wish. No data loss necessary.

Also, I'll look into a minimal VM. I thought about actually trying to make a Windows version of Suicide Flash. I'm not sure which I'll end up with.
[Moto X Android Development] Cindex:
So I tried this on my Ubuntu 12.04.5 last night, and it didn't recognize the device in fastboot. I'm going to try on Ubuntu 15.04 soon here. Another question for you though, which sdk do I use for XPosed? I don't seem to be able to figure it out searching all over. I would think 16, but maybe it's for Lollipop?

I think I'm going to get some of these with the OTA, it'll make it easier for the average Republic user once it's gotten going.
[Moto X Android Development] Nicene Nerd:
I can't answer your Xposed Lollipop question. I was wondering the same thing, but I ended up simply pulling the file from an existing Xposed installation. I suppose you could do the same and then diff the files to find out which is correct.

As for the OTA, that's not possible. Every time an OTA is installed, the files can end up in different places on the flash memory, and this utility requires knowing the exact locations for making changes. You'd have to make separate packages for every phone. Otherwise you'll end up with bootloops.
[Moto X Android Development] Nicene Nerd:
Has anyone tried using Suicide Push? It's slow, but I thought it would be the more celebrated part of this since it lets you do basically the same as an ADB push to the system partition. You could even install Xposed that way:

./suicidepush.sh local_app_process_file /system/bin/app_process
[Moto X Android Development] Cindex:
I'm still working on getting it to root. I was going to a few days ago, but my flash drive burned out. I'm going to try Ubuntu 14.04.3.

What linux distro did you use?

---------- Post added 14th August 2015 at 12:41 AM ---------- Previous post was 13th August 2015 at 11:47 PM ----------

Sorry to double post again, but I can't edit yet and have a few more things. I can't seem to be able to find a RW SBF file. I'm thinking restore from factory sounds like a good solution, but I don't know if that's the same thing.

How can I pull a system image if I'm not root? Without an SBF file, I need to package it for myself. Without root, I can't pull the system.img. I'm sure others on networks not covered yet would like to know also. Where did you get your system.img?

Also, if we can get this deep, and you can modify the bootloader, couldn't you just flash the old bootloader image and then the rest of the ROM? Then we could unlock the bootloader using older methods. We might have to flash block by block, but it should work?
[Moto X Android Development] Nicene Nerd:
I used Ubuntu 14.04.

The RW 4.4.4 SBF can be found here or here. It does not appear possible to pull a system image without root. But even without permanent root, KingRoot can get you temp root long enough to pull a system image.

As for the bootloader, there's certainly a chance that this could be done. It's just so risky that I won't try it myself. If there was a single variable missed, it could easily mean hard-brick. But in theory, as far as I understand, it might work. The biggest obstacle might be partition changes. If you got the bootloader to get into fastboot mode, though, you could presumably fix that with an old SBF.
[Moto X Android Development] jahrule:
Flashing the olderer bootloader will not work (I have tried and confirmed it does not work). It is because the efuses verify the bootloader.
[Moto X Android Development] Sabissimo:
Wow! That's hell of a tool you've created here :) Awesome job! I haven't tried it myself yet, but, judging by source code, it should get the work done. More of a developer tool, ofc, but it's more then impressive :) Maaan, I wish there was a normal way to work with ext4 partitions to make it available on Windows))

Since you've made "push" version of it (and that's the most interesting part, longest though), the next step in future development should be doing the same with TWRP flashable zips. Some of them just put apk-s in system folder, some of them have shell scripts inside, I've yet to figure out the pattern :) But that would be awesome next step to this awesome project :)
[Moto X Android Development] CrashXXL:
download link not found )
[Moto X Android Development] hugh a:
theres a tool bar at top crash with download links next to discussions and screenshots
[Moto X Android Development] Nicene Nerd:
I've actually started work on a Windows version, but it's on back burner because school just started. Here's a hint, though: with OSFMount and Ext2Fsd, you can mount Moto system images (pulled from the phone, not SBF ones) as hard drives or removable disks. Suicide Flash for Windows will rely on them.
[Moto X Android Development] lpjunior999:
So what are the chances I could use this to pull a system.img, and actually go in and delete some apps out of my XT1058? I had some success but it pulled the image as a mbn and I'm hesitant to try flashing it.
[Moto X Android Development] Nicene Nerd:
Here's what you'll want to do:

Create the system image on the phone with

dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/oldsystem.img bs=1024

ADB pull or MTP copy the image to your PC.

Run pkgmaker.sh like so:

./pkgmaker.sh oldsystem.img XT1058 "My System" 4B000000 modded-system.zip

When prompted, you can delete apps as root from the mounted system image under mnt-oldsystem.img/app or mnt-oldsystem.img/priv-app

Continue and finish the script.

Flash with

./suicideflash.sh -s output/modded-system.zip
[Moto X Android Development] lpjunior999:
So with much doing, I got it to mount the image of my phone, but the problem is Ubuntu wouldn't actually get root permissions, using any combination of sudo or gksudo. This was a problem, as all those files it created over the course of a few hours were now undeletable; it filled up about 13 gigs trying to get it to actually delete some old apps.

I kind of hate this phone now.
[Moto X Android Development] cyberg0d:
I would happily try it been waiting for this for years.. but; dont wana mess with linux those days are over for me.
[Moto X Android Development] Rohit99:
Download link

http://xdaforums.com/devdb/project/dl/?id=13879

---------- Post added at 11:07 AM ---------- Previous post was at 11:04 AM ----------

Download link

http://xdaforums.com/devdb/project/dl/?id=13879
[Moto X Android Development] s5610:
Nice, but too complicated for newbies, the only ones who need such all-in-one. Win32, pls! )

P.S. Good project's name.
[Moto X Android Development] lpjunior999:
I keep getting an error where it mounts a blank folder, because when it mounts my img, the filetype isn't specified. What needs to be adjusted?
[Moto X Android Development] zadeora420:
Excellent work. Going to give the scripts a try to modify my own system image. Any news for windows version???
[Moto X Android Development] microMXL:
For me this seems easier than CrashXXL method (I'm more used to linux than messing with windows drivers)
[Moto X Android Development] wildblade64:
Anyone able to install xposed on crashxxl's Moto X L!te FW LPA23.12-15.5.EU.ML yet?
[Moto X Android Development] microMXL:
you mean on this one?

_Rus_5_1_0_LPA23_12.XX.7_BL_V30.BE.rar

I tried but could not install xposed, it took like 6hours to install :/

Also had to do it on windows, the script qdloadRoot.py wouldn't work on arch
[Moto X Android Development] Nicene Nerd:
First updates in a long time, from 0.2 to 0.5. Fixed a couple bugs in the package maker script. Added the source to GitHub. And...

A Windows version might show up sometime.
[Moto X Android Development] cyberg0d:
ooooh sometime... cant wait =D
[Moto X Android Development] Salik Iqbal:
Is it possible too just change the build.prop by this method? Rest is all fine :D
[Moto X Android Development] wildblade64:
any one willing to make an image with xposed for the latest ota on xt1058?
[Moto X Android Development] s5610:
I will... to see v0.5 Win32 )
[Moto X Android Development] Nicene Nerd:
There's a much simpler way to change your build.prop. Edit a copy on your PC and then use the Suicide Push script. Usage instructions for it are also in the OP.
[Moto X Android Development] Salik Iqbal:
does this method can be used in droid turbo also xt1254?

---------- Post added at 01:06 AM ---------- Previous post was at 01:06 AM ----------

does this method can be used in droid turbo also xt1254?
[Moto X Android Development] Nicene Nerd:
If it uses the MSM8960 chip, it may work, so long as the Moto X bootloader files were replaced.
[Moto X Android Development] s5610:
No, impossible due to lack of needed loader for this model. Just use Sunshine.
[Moto X Android Development] rczrider:
I've got a Republic Wireless Moto X already running 5.1 (LPA23.12-39-R-15 / 222.21.15.ghost_row.RepublicWireless.en.US.Spring) with a locked bootloader. I'm not using the phone anymore, but want to keep it around as a media player and would love to root it.

Will this tool work? If so, I assume it's still only on Linux, so I would need to run Linux Live or similar (as I only have Windows)?
[Moto X Android Development] bruinsrule:
Further installation for suicideflash.sh to function properly

I've been able to trouble shoot an error that people have been having with your wonderful tool. I'm not sure if you want to update your tutorial or not, but FYI. The suicideflash.sh runs fine until flashing in qualcomm mode. It then kicks an IO error 22 . The problem is that I needed to install pyserial 2.7 manually to get it to work. Now I'm good to go. The install batch file only contains python. I'm not sure if you can install pyserial automatically or need to create a script?? This may be useful for those who thought they had a bricked phone.
[Moto X Android Development] kaivorth:
Would be awesome if we could get this working on 5.1, unless there was a way to downgrade.
[Moto X Android Development] WOrld1:
Stop resurrecting dead thread.

Almost all this section is dying
[Moto X Android Development] rokrmotolovers:
please create video tutorial sir...
[Sprint HTC EVO 4G LTE] ocarinaz64:
[IMG="CarbonLogo"]http://carbonrom.org/wp-content/uploads/2013/12/Black-on-Trans.png[/IMG]

​

I'm super excited to announce Carbon Rom for the Jewel!!! It's been a long time since I've seen this one on this device. I hope you enjoy it, along with the other ROMs I have helped push out for this device. More details to come. For now, clean wipe, flash, and enjoy!!!

NOTE: May not run on first bootup. If not, just restart the phone, and it'll push through fine.

As with all my ROMs, I suggest the latest TWRP for recovery.

I also suggest Slim Gapps for packages.

DOWNLOAD ROM HERE

Special thanks to Carbon team, and CyanogenMod team, both of whose code I used to make this possible.

Kernel Source: https://github.com/cyanogenmod/android_device_htc_jewel/tree/cm-12.1

XDA:DevDB Information

Unofficial Carbon Rom for Jewel, ROM for the Sprint HTC EVO 4G LTE

Contributors

ocarinaz64

Source Code: https://github.com/carbonrom

ROM OS Version: 5.1.x Lollipop

ROM Kernel: Linux 3.4.x

Based On: CyanogenMod

Version Information

Status: Nightly

Created 2015-08-07

Last Updated 2015-08-20
[Sprint HTC EVO 4G LTE] benahlquist:
No. Way. I was a big fan of Carbon way back when, glad to see this back up on LP! Thanks for your work =)

Edit: Install worked great and I'm up and running; all features seem to be functional as far as I can tell. This runs nice and light, very snappy!
[Sprint HTC EVO 4G LTE] ocarinaz64:
I noticed that there have already been several downloads of Carbon. I'm glad to see people at least giving this one a look. I'm not a guy who is too picky on features, so I can switch from one ROM to the next without missing much. For the time being, I'm on Carbon, and I haven't had any hiccups.
[Sprint HTC EVO 4G LTE] ocarinaz64:
One quick note here, be sure to check your ringer volume. For some reason, although my volume was ON, it sounded way soft to where I didn't even know it was ringing. Maybe it's just me, but check to see that you have your ringers working properly by calling your phone.
[Sprint HTC EVO 4G LTE] aptorrent:
First, thank you for your effort in in keeping this device relevant when most others have moved on(which of course is understandable). Much appreciated :)

I haven't seen any issues with the ringer volume. In fact, I find all the audio through the device's speaker much fuller and louder! Very surprised that the device is capable of this volume.

The 2 issues I've seen with this ROM are:

1) Relatively weak battery life compared to 5.1 PAC ROM beta's and Unity ROM 5.1 . Its dropping from fully charged at 10:00 PM to ~60% in the morning without any use. I've used it for 4 days now and will give it a few more days to settle down. It could also be the half-popped kernel with double tap to wake feature.

2) Notifications are not readable due to white text on white background
[Sprint HTC EVO 4G LTE] ocarinaz64:
That's weird, because my notifications are white on a black background... I wonder if its a theme issue.
[Sprint HTC EVO 4G LTE] ocarinaz64:
I did post another update.
[Sprint HTC EVO 4G LTE] 7357:
Anybody using this rom? I'd like to hear some feed back.
[Sprint HTC EVO 4G LTE] mildlydisturbed:
Installed it on my old unit - full wipe, flashed minimal gapps recommended, only issue I see is I'm getting "insert SIM card" whenever mobile data is turned on.

Not that I have mobile data or need to turn it on mind you...
[G4 Q&A, Help & Troubleshooting] dvnguye3:
I've had my Tmobile G4 for almost 2 weeks now and the screen pixelates every single day. The weird thing is it only happens on the bottom left corner of the screen and the size of the pixelation varies. It happens more often when I'm watching videos or playing games. I'd take a screenshot but it's almost impossible to capture because it happens randomly and so fast that I'd have to hold the power and volume down button before it happens in order to capture it.

Is anyone else experiencing these issues? I prefer trying to fix it than bringing it to the Tmobile store where I'd stand for 10-20 minutes waiting for it to happen so they'll believe me.
[AT&T Samsung Galaxy Note II] Drowntecityy:
I am having issues with a Sandisk memory card on my Note 2. For whatever reason, it stopped working- like completely. I can't format it, I can't delete anything off of it, or put anything on it. I haven't write protected it either, which I found odd whenever I went to troubleshoot it on my computer. I have even tried the Command Prompt method of troubleshooting/formatting- but with no results whatsoever. I read online that ALOT of users are having the same problems with their SD Cards out of nowhere, because of an update (my phone is rooted and on 4.1.2 and hasn't been updated).

Might I also add, that when the SD Card stopped working, I noticed that there were extra files put on there that weren't originally there that are from Android (such as google.music and such) and I know I didn't put that on there. I'm just wondering if anyone has found a fix to this? I've tried everything, but I feel as if my SD card is shot (my phone automatically updates apps and such and I'm quite confident it did the same to my External SD Card as it has with other people). I just have alot of things on my phone I need to add for work, and it's super inconvenient that my phone is only 8GB and has a 60GB SD Card with the potential to work again. I would buy another card, but I wouldn't want to spend the money on one, just for something like this to happen again if you know what I mean, lol.
[P3600 General] TriniLix:
i have a Bluespoon AX2 bluetooth ear piece... eveytime i get an incoming text while on a call i lose my bluetooth connection... i then therefor have to continue my call via my phone...has anyone experience this same issue??:confused:

is there any registry tweaks to correct this???:confused:
[XDA Assist] pee_why:
Fail test

Several helpers said me to resolve my mistake when i want to try new recovery+root to reflash with the manufactor ROM. So i come back to the step 1, I download the new S700 ROM from the factory website and flash it with SP Flash tool => by SP__MDT_exe_v3.1504-A2015.03.18-v06 or SPFT v5.1528 it was same : success DL but my S700 doesn't restart.... :( :'(

Instead of firmware upgrade i test also Format All+Download but my S700 doesn't restart :'( So now i don't know what i can do ??? pleassse
[XDA Assist] :
Hi, thanks for using XDA Assist! :)

Please ask for further assistance here:

http://xdaforums.com/general/help

You'll find expert advice there.

Good luck! :)

Thread closed.
[Verizon Samsung Galaxy S 4] Lanky09:
MY S4 allows me to enter debug mode when i plug in the USb although it won't stay in it. I am trying to root which requires debug mode but after 10-20 seconds it switches to media device mtp automatically.

I have tried installing samsung drivers from their website, Kies, i have changed USB cable and port, even tried a different laptop but still the same result.

Help is very much appreciated!

I just got this S4 and cant wait to root it
[7" Kindle Fire HD General] namitutonka:
Most nearly all threads and posts could, would, and should be more helpful, with specific device ID's. So many posts really cement clarity for individuals with model numbers, serial numbers, and device descriptions. When posted with device specifics, many problems could be avoided. I invite any XDA members who have posted here to edit those posts and leave more complete and helpful information.

Include as much specific info as possible with size and internal storage.

If the device is in hand, include the serial number prefix examples:

D01E------Kindle Fire 1st Gen

D026------Kindle Fire 2nd Gen

D025------Kindle Fire HD 7" 16GB

D059------Kindle Fire HD 7" 32GB

B0C9------Kindle Fire HD 8.9" 16GB

B0CA------Kindle Fire HD 8.9" 32GB

B0CB------Kindle Fire HD 8.9" 4G LTE 32GB

B0CC------Kindle Fire HD 8.9" 4G LTE 64GB

Kindle Fire (2011): D01E

Kindle Fire (2012): D026

Kindle Fire HD 7(2012): D025 and D059

Kindle Fire HD 7(2013): 00D3 and 00D2

Kindle Fire HD 8.9: B0C9, B0CA, B0CB, and B0CC

Kindle Fire HDX 7: D0FB, 00FB, 00FC, 0072, 00FD, 00FE, 0073, 006C, 006D, 006E

Kindle Fire HDX 8.9: 0018, 0057, 005E, 00F3, 0019, 0058, 007D, 007E, 007F

[IMG="Kindle Fire Serial #"]http://s1031.photobucket.com/user/thoronodor/media/KindleSerialNumbers_zpsvyylefdy.jpg.html[/IMG]

[IMG="Serial number prefix on device"]http://s1031.photobucket.com/user/thoronodor/media/Kindle-Fire-Device-screen_zpsvla8ysua.png.html?sort=3&o=0[/IMG]

Include Model Numbers, here are some examples:

KINDLE FIRE HD -16GB, Wi-Fi, 7in - Black Model X43Z60

KINDLE FIRE 8.9", 16GB TABLET Model 3HT7G

KINDLE TOUCH 6", 4GB TABLET Model D01200

KINDLE DX 9.7". 4GB TABLET Model D00801

KINDLE FIRE 8.9", 16GB TABLET Model 3HT7G

KINDLE 6", 2GB TABLET (BLACK) Model D01100

KINDLE FIRE HD 7" Model KFTT

KINDLE FIRE WiFi 8.9“HD Model WFJWI

KINDLE FIRE WAN8.9"HD Model WFJWA
[7" Kindle Fire HD General] sd_shadow:
Good info, I will included it in my

Fire Index: Which Amazon Fire Tablet Do I have?

i fixed img tags in quote
[AT&T Samsung Galaxy S 5] Beatty3664:
Is it possible to root a galaxy s5 on att latest firmware if I flash it back to stock firmware and install a pre-rooted 5.0?