Database Develop

[Q] Jelly Bean Mini Project Noob

Hi all,
First I must point out I'm a bit of a noob at this flashing kernels/roms etc. I want to install Jelly Bean Mini Project | Android 4.1.2 on my xperia x8.
I rooted it ages ago with superoneclick. I got the rom here in the download section of this post and got the kernel here. Not sure how to proceed do i unzip the rom folder called "X8_JBMP-Release4"? I need a tutorial on what programs to use etc. step by step would be handy. I did look did look am continuing to look. Thanks in advance and sorry.

first of all you have installed nAa's jb kernel right?
---------- Post added at 06:27 PM ---------- Previous post was at 06:21 PM ----------
if not, download Flashtool from here
then do the following steps
1. go here and find the "Flashing custom kernel" step
2. Flash the kernel, beforehand, be sure to have the proper drivers installed, go to the flashtool directory, drivers, execute the .exe file then choose drivers for x8, fastboot and flashmode
3. You are ready to flash a kernel, just follow the instructions on the thread I pointed out to you
4. No need to unzip the ROM file as it is a flashable zip, after flashing the kernel power up your device and click the back button a couple of times
5. You are now in the CWM recovery, go to mounts and storage and select: format /system, /data, /cache and then back to the CWM main menu, select Wipe data/factory reset, Wipe cache partition, and to the advanced option, wipe dalvik cache
6. Now you have just performed a full wipe, go to install zip from sd card, find the ROM zip file you just downloaded and install it
7. Then install the GAPPS needed to work with JBMP
8. Reboot and Enjoy

op didn't mention if
a. he already has recovery installed
b. if his bl is unlocked
Just because i don't doesn't mean i can't.

many tairsai
cascabel said:
op didn't mention if
a. he already has recovery installed
b. if his bl is unlocked
Just because i don't doesn't mean i can't.
Click to expand...
Click to collapse
Bootloader is unlocked sorry didn't mention. Titanium back up installed but not sure if that is the backup you are asking about.

Yanisirl said:
Bootloader is unlocked sorry didn't mention. Titanium back up installed but not sure if that is the backup you are asking about.
Click to expand...
Click to collapse
titanium backup is good. :thumbup: you can also enter cwm and make a backup there. otherwise, follow mass's instructions. don't forget to format system cache data in cwm after flashing kernel and before flashing rom. have fun with jb. :thumbup:
Just because i don't doesn't mean i can't.

MassStarvation said:
first of all you have installed nAa's jb kernel right?
---------- Post added at 06:27 PM ---------- Previous post was at 06:21 PM ----------
if not, download Flashtool from here
then do the following steps
1. go here and find the "Flashing custom kernel" step
2. Flash the kernel, beforehand, be sure to have the proper drivers installed, go to the flashtool directory, drivers, execute the .exe file then choose drivers for x8, fastboot and flashmode
3. You are ready to flash a kernel, just follow the instructions on the thread I pointed out to you
4. No need to unzip the ROM file as it is a flashable zip, after flashing the kernel power up your device and click the back button a couple of times
5. You are now in the CWM recovery, go to mounts and storage and select: format /system, /data, /cache and then back to the CWM main menu, select Wipe data/factory reset, Wipe cache partition, and to the advanced option, wipe dalvik cache
6. Now you have just performed a full wipe, go to install zip from sd card, find the ROM zip file you just downloaded and install it
7. Then install the GAPPS needed to work with JBMP
8. Reboot and Enjoy
Click to expand...
Click to collapse
I have correct kernel and the JBMP not sure what GAPPS is.

Yanisirl said:
I have correct kernel and the JBMP not sure what GAPPS is.
Click to expand...
Click to collapse
google apps. i'm not sure about jbmp but naa's minicm10 has a zip file. flash it after flashing the rom.
Just because i don't doesn't mean i can't.

one more noob question
I was wondering about unlocking this phone from the network it is on. Should I get the code and do it first of will I still be able to do it if I wish after the upgrade. Sorry for the noob questions. Thanks for all the other help I have an idea of what to do now.

Sucess!!
Thanks a million guys got it up and running jellybean. First flash of kernel was just sticking on CWM recovery screen no buttons working. flashed back to a stock 2.1 (rom not my original one) and flashed the new kernel again and all went fine. Thank you so much for all this help and thanks to the folks who worked in the release of jellybean. I just need to figure out how to store apps on sd card. time for research.

Option to move apps to sd card is Greyed out in settings/apps section. Any ideas how i might get my apps to move to sd card?

U can odex to get more space..find it in android development, made by TeamMex..
If u're DRAGONFORCE lovers please hit THANKS button,,

Yanisirl said:
Option to move apps to sd card is Greyed out in settings/apps section. Any ideas how i might get my apps to move to sd card?
Click to expand...
Click to collapse
maybe the ROM is missing the 10apps2sd module in the init.d...
you can download App managers from the play store

MassStarvation said:
maybe the ROM is missing the 10apps2sd module in the init.d...
you can download App managers from the play store
Click to expand...
Click to collapse
No, it not missing,

strange...

Looking around on web it seems apps cant be moved after 4.0. Don't know why google did that it was one of the features I most wanted. I guess I could go to something earlier but I like jelly bean :crying:

Yanisirl said:
Looking around on web it seems apps cant be moved after 4.0. Don't know why google did that it was one of the features I most wanted. I guess I could go to something earlier but I like jelly bean :crying:
Click to expand...
Click to collapse
try a clean flash. i'm on 4.1 and i cam move apps fine. though i don't use the native app2sd.
Just because i don't doesn't mean i can't.

Will a reflash do it? do I need to flash back to a stock rom first? Or is there something I need to do to let a2sd work like give it a partition somehow?

Yanisirl said:
Will a reflash do it? do I need to flash back to a stock rom first? Or is there something I need to do to let a2sd work like give it a partition somehow?
Click to expand...
Click to collapse
just format system cache amd data after a full wipe (wipe cache amd dalvik too) and reflash rom.
Just because i don't doesn't mean i can't.

Thanks for the reply. I will try it in a couple of days as I'm busy with work and will post back here with the result.

moving apps
I booted into CWM recovery and used the advanced section to create a 1gb partition left swap size setting at 0 and that fixed the issue. I guess if I wasnt a noob I would have made a partition on the card in the beginning. Apps can now be moved except those that dont allow movement but I am using link2sd for those. Its cool to see jellybean on this phone. I get quite a few hangs/crashes using the browser, bluetooth earpiece connects fine but I cant hear calls on it and the countdown timer is erratic closing by itself quite often. Maybe there are some settings I need to tweak to get the best performance? Thanks again for all the help and replies by the way.

TWRP can't decrypt /data on CM12.1

I just decided to move to CM12.1 on my Droid Turbo (XT1254) after the 1/27 Snapshot (YOG7DAO3J1) was posted. I am running this with TWRP 2.8.7.0, BHB27 Kernel, and OpenGAPPS 5.1. So far, almost everything has been fantastic and the performance of the device is like night and day compared to the Verizon software.
My problem is that the CM12.1 ROM has my device encrypted to begin with, which is nice but giving me trouble. I can't get into TWRP to install Xposed framework or other .zips via ADB. I have tried the following:
Disabling require password on startup
Changing the password in Android
Changing the password from root ADB shell
Using a pin
Trying "default_password"
Can anyone give me a solution or some advice? Any help is greatly appreciated!

Having same issue with TWRP not recognizing any decryption password given... Any ideas out there? Is TWRP incompatible with Droid Turbo HW Encryption, or ?

P_6 said:
Having same issue with TWRP not recognizing any decryption password given... Any ideas out there? Is TWRP incompatible with Droid Turbo HW Encryption, or ?
Click to expand...
Click to collapse
This thread is kinda old and I assumed nobody really knew what was going on with it either. I ended up just not using the encryption. The first time around mine was encrypted without me knowing, which was the issue. I just wiped all partitions and flashed the ROM again...

I am having a similar issue so i thought i would chime in, despite the older thread. I had a stock ROM that was encrypted and I was able to unlock and root with SunShine fine. Flashed on TWRP 2.8.7 and ran into a "Unable to mount storage. Failed to decrypt data" error. Updated to TWRP 3.0.0 and still have the same issue. Still working through a resolution as the phone is still functional if I just boot normally. When you mentioned you wiped all partitions, what process did you use? If i can just get access to the interal storage I can flash a ROM and be good to go.

Asyt said:
I am having a similar issue so i thought i would chime in, despite the older thread. I had a stock ROM that was encrypted and I was able to unlock and root with SunShine fine. Flashed on TWRP 2.8.7 and ran into a "Unable to mount storage. Failed to decrypt data" error. Updated to TWRP 3.0.0 and still have the same issue. Still working through a resolution as the phone is still functional if I just boot normally. When you mentioned you wiped all partitions, what process did you use? If i can just get access to the interal storage I can flash a ROM and be good to go.
Click to expand...
Click to collapse
So far, the only way I have been able to get encryption working with CM12.1 on the Droid Turbo is to do the folllowing (Note: This assumes you have bootloader unlocked and TWRP installed as your recovery):
Part 0: Make sure you have what you need
1. Stock Droid Turbo Firmware SU4TL for your device
2. The version of CyanogenMod 12.1 that you need. I recommend a Snapshot, but it's up to you.
3. TWRP 3.0.0 or later for your Droid Turbo.
Part 1: Final set up (Yes, we do this first)
1. Download CM12.1 & Download OpenGapps arm for 5.1
2. Wipe device (system, data, cache, internal storage), copy CM12 install zip and opengapps install zip via USB to device.
3. Flash CM12 and OpenGapps in TWRP
4. Set up device how you want it to be (install your apps, set up your accounts, etc).
5. Set whatever lock-screen PIN / Password / Pattern you are going to want on your phone in general!
6. Make a Nandroid backup of your 100% set up phone in TWRP
7. Copy your backup TWRP folder to your PC.
Part 2: Encrypt device and put everything back how we want it.
1. Flash stock Verizon firmware (SU4TL) via Fastboot. Do not flash stock Recovery, but put back TWRP if you did somehow (I use a simple bash script I have attached below).
2. Boot device, go through initial set up, don't download apps (we're going to be wiping the device soon).
3. Make sure your battery is 80%+ charged, and your device is plugged in.
4. Set a password or PIN on your phone.
5. Encrypt your device (this will be fairly fast, as /data is empty, but you should be asked for your encryption password on boot.)
6. Reboot to recovery. TWRP will ask you for your password to decrypt. It should work with no problem.
7. Copy your backed-up TWRP folder with your CM12 install to your device via USB. The TWRP folder goes in the Internal Storage root directory.
8. Still in TWRP (Do not reboot), go to Restore, and select the backup you just copied over. This will replace the stock rom with your CM12 backup.
9. Your CM12 install will be restored, but your device will remain Encrypted.
10. Reboot into CM12. Win.
You will need to decrypt your device every boot with the password that you selected when you initially encrypted your device. Your lock-screen password CAN BE DIFFERENT. That is why I do it this way. I have a fairly long password to decrypt my device on boot-up, but a pattern as my lock screen. That way I can quickly get into my phone during daily use without having to constantly type in a fairly complicated password.

Guide MultiBoot 33b [EASY]

Hi everyone, my name is Mirko and I am an italian student and first of all sorry for my bad english, fiddle with ROMS and Kernels is an hobby for me and i really enjoy it.
I would make a tutorial for anyone who can not unencrypt OnePlus3 with any ROM. READ EVERYTHING BEFORE START.
I AM NOT RESPONSIBLE FOR WHAT COULD HAPPEN TO YOUR DEVICE. PAY ATTENTION.
DOWNLOAD
VIRUSTOTAL
Open and extract the zip file where you want.
Install USB drivers
Install ADB drivers by open adb-setup-1.3.exe, Y, Y ,Y and close.
Copy fastboot adb drivers 1.0.36 to C:\adb and overwrite.
Open CMD in the same file folder by pressing Shift+right click and type "adb", if it say nothing match reboot your pc.
Plug your phone to PC and allow adb access, then type "adb devices" and you should see your phone id.
We have to unlock bootloader, THIS ACTION PERFORM A FULL, FULL (EVEN INTERNAL MEMORY) OF YOUR PHONE, BACKUP EVERYTHING. Tick on OEM Unlock in developer option (nothing here will happen). Type "adb reboot fastboot" and your phone will reboot in fastboot mode. Use now "fastboot devices" for recognize your phone and "fastboot oem unlock" for unlock bootloader.
Do not restore backup cause we are gonna wipe again, back into fastboot mode (AFTER OEM UNLOCK FROM DEV OPTIONS) and flash twrp using fastboot flash recovery multiboot....img.
If phone reboot back again into fastboot and type fastboot format userdata. Reboot into recovery.
Now on recovery start MTP and copy OOS/HOS and supersu zips into your phone, flash the ROM, DO NOT REBOOT, flash supersu. Your device is now unencrypted.
Type adb shell chown -R media_rw:media_rw /data/media on CMD for avoid problems after flash.
You can now flash multiboot.zip and you have to inject boot sector every time you will install/update ROMS. OOS/HOS OTA ARE NOT COMPATIBLE WITH TWRP, YOU HAVE TO FLASH THE ENTIRE ZIP FILE FOR UPDATE IT.
You will see a slide menu on top right side of TWRP and from here you can install new roms on INTERNAL MEMORY. In advanced option select "no-kexec workhound" (important).For gapps go to ROM list, select the interested rom, then flash zip, >gapps.zip. NOT ALL ROMS ARE COMPATIBLE WITH MULTIROM.
Every OTA (i think) except (for sure) stock roms will update without problems.
Reboot your phone and it will boot on multiboot menu, here you select rom you want boot.
YOU ARE DONE.
I tested it on my phone and it works really fine, OOS can be installed as secondary rom BUT FLASH SUPERSU BEFORE REBOOT.
Installing secondary ROMS are slower than primary, cause it will create virtual disks.
If you have problems with pattern after reboot, back into twrp, advance, filemanager, /data/system and delete locksettings.db, locksettings.db-shm, locksettings.db-wal and reboot. Pattern will be deleted.
Installing Kernels wich are not compatible with MULTIROM will softbrick the phone, and you have to wipe.
Installing Kernels on virtual ROMS will softbrick the ROM.
I think my guide is done.
If you have problems
FOR ANY PROBLEMS AND DOUBTS WRITE HERE OR PM ME.

Wow, there's a lot of misinformation in this post.
No "virtual disks" are created. Mount points are changed to point to the secondary ROM.
You don't have to use a multi ROM capable kernel, you should read up on the no kexec workaround before you write up a post like this
Also, you can flash kernels to secondary ROMs. I'm not sure what gives you the impression that you can.
You don't have to flash the multi ROM zip Everytime you write to the system partition. Mutirom is on the "SD card" on the data partition
Aside from the incorrect parts, the rest of the tutorial is poorly written and very difficult to follow
Why don't you leave the tutorials to the people who actually know how things work on the back end.
Sent from my Pixel XL using Tapatalk

slothdabski said:
Wow, there's a lot of misinformation in this post.
No "virtual disks" are created. Mount points are changed to point to the secondary ROM.
You don't have to use a multi ROM capable kernel, you should read up on the no kexec workaround before you write up a post like this
Also, you can flash kernels to secondary ROMs. I'm not sure what gives you the impression that you can.
You don't have to flash the multi ROM zip Everytime you write to the system partition. Mutirom is on the "SD card" on the data partition
Aside from the incorrect parts, the rest of the tutorial is poorly written and very difficult to follow
Why don't you leave the tutorials to the people who actually know how things work on the back end.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
First of all thank you for reply, i totally missed to enable no-kexec workhound function...
I want to clarify that it is my first guide I do, I started in make some because I want to help people like me who have had difficulties in carrying out certain passages. I accept ANY advice and I will try to improve with time. I admit I made a mistake forgetting the previously mentioned feature. I can tell you, however, that the multi-boot every time you install a new ROM is removed. Going blind I specified / system because it is the main partition is rewritten during a flash. But I have a doubt. The Kernel for secondary ROM, should not be predisposed to function properly?

mirko8054 said:
First of all thank you for reply, i totally missed to enable no-kexec workhound function...
I want to clarify that it is my first guide I do, I started in make some because I want to help people like me who have had difficulties in carrying out certain passages. I accept ANY advice and I will try to improve with time. I admit I made a mistake forgetting the previously mentioned feature. I can tell you, however, that the multi-boot every time you install a new ROM is removed. Going blind I specified / system because it is the main partition is rewritten during a flash. But I have a doubt. The Kernel for secondary ROM, should not be predisposed to function properly?
Click to expand...
Click to collapse
I assure you, you do not have to reflash the mutirom zip Everytime. I have flashed dozens of times on my phone and have not had to flash mutirom again. The only exception is if you wipe internal storage, BC it wipes your "sdcard"
Mutirom patches the kernel when you flash to to secondary, hence almost any kernel will work
Sent from my Pixel XL using Tapatalk

slothdabski said:
I assure you, you do not have to reflash the mutirom zip Everytime. I have flashed dozens of times on my phone and have not had to flash mutirom again. The only exception is if you wipe internal storage, BC it wipes your "sdcard"
Mutirom patches the kernel when you flash to to secondary, hence almost any kernel will work
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
When my CM13 (Internal rom) installs OTA, after reboot multiboot menu won't appear, and i can't select secondary roms for boot them, i solve by re-flash multiboot.zip...

What you have to do in that case is go into the mutirom menu from twrp , then hit " inject boot sector"
That patches the new kernel from the OTA. You dont need to reflash the entire mutirom zip
Sent from my Pixel XL using Tapatalk

slothdabski said:
What you have to do in that case is go into the mutirom menu from twrp , then hit " inject boot sector"
That patches the new kernel from the OTA. You dont need to reflash the entire mutirom zip
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Ok thank you, i will update the guide.

Problem with installing TWRP and rooting with Magisk

I am trying to install TWRP and root my Mi Mix. I have followed the steps below without encountering any error messages.
1. Go into fastboot
2. Flash TWRP recovery
3. Boot into recovery.
But at the end when I boot into recovery I see Mi Recovery 3.0 instead of TWRP. Am I missing anything? My device is unlocked. I am currently running MiUI 9.6.1 Global stable Android 8.0

sofene said:
I am trying to install TWRPA on my Mi Mix. I have followed the steps below without encountering any error messages.
1. Go into fastboot
2. Flash TWRP recovery
3. Boot into recovery.
But at the end when I boot into recovery I see Mi Recovery 3.0 instead of TWRP. Am I missing anything? My device is unlocked. I am currently running MiUI 9.6.1 Global stable Android 8.0
Click to expand...
Click to collapse
Never mind I solved the problem by booting from the pc. But I have a new problem. Two problems really. First of all I can't seem to get the data partition backed up. I get the error unable to mount *\data *. Secondly I cannot install magisk.zip. I cannot find the file in twrp though it is in main storage in the device. Do I need to copy it to any specific location for the twrp to use it?

Same like your firs post. But i not try instal magisk. I using SU. Now not root and not cusum recovery

sofene said:
Never mind I solved the problem by booting from the pc. But I have a new problem. Two problems really. First of all I can't seem to get the data partition backed up. I get the error unable to mount *\data *. Secondly I cannot install magisk.zip. I cannot find the file in twrp though it is in main storage in the device. Do I need to copy it to any specific location for the twrp to use it?
Click to expand...
Click to collapse
You can install it using a usb stick or via sideload.
You cant backup because the twrp's dont let you enter the password for the encryption on the device thus leaving it encrypted.
If u dont want to delete everything then use sideload for the Magisk installer, if u dont mind then u can go ahead and format data and the encryption will be gone untill you go back to system, then the device will encrypt the data again.

sexlord89 said:
You can install it using a usb stick or via sideload.
You cant backup because the twrp's dont let you enter the password for the encryption on the device thus leaving it encrypted.
If u dont want to delete everything then use sideload for the Magisk installer, if u dont mind then u can go ahead and format data and the encryption will be gone untill you go back to system, then the device will encrypt the data again.
Click to expand...
Click to collapse
I tried to install magisk using sideload enabled but still got error unable to mount storage at the end so I deleted data. And then I was able to install magisk without error. However, when I check root status with root checker it says root was not properly installed. When I went back to twrp I was presented with a screen to enter password to mount I guess the storage or partition. Does this mean that ruth has been installed even though root checker says its not.? Secondly which password is being requested because when I entered my screen unlock password it says password failed. Is it asking for the mi account password or with other password? Thanks for your assistance.

Hi, the only thing that worked for me is to install right after the rom the encryption disabler and you'll be able to use trwp. Just follow the steps in the link below. last thing, when you'll make an update you'll loose again the trwp access.
https://forum.xda-developers.com/mi-mix/development/rom-global-miui9-oreo-mi-mix-t3783869

lnt976 said:
Hi, the only thing that worked for me is to install right after the rom the encryption disabler and you'll be able to use trwp. Just follow the steps in the link below. last thing, when you'll make an update you'll loose again the trwp access.
https://forum.xda-developers.com/mi-mix/development/rom-global-miui9-oreo-mi-mix-t3783869
Click to expand...
Click to collapse
Thanks for your reply. One question, though. Would this then allow you to backup data using twrp?

sofene said:
Thanks for your reply. One question, though. Would this then allow you to backup data using twrp?
Click to expand...
Click to collapse
Yes you can make a backup, but in case of update you'll loose the access on your files in trwp.

A couple things :
1. You can't install magisk if your data partition is encrypted, because magisk needs to put the file in the data partition. so you need to disable the encrypt first, and then you can install magisk.
2. If your data partition is encrypted, don't bother to backup from twrp. Boot to system, connect to pc, and backup using regular way (copy and paste files).
3. Backup your data before you do any encrypt/decrypt process.

Problem updating custom ROM - TWRP won't decrypt data

After trying to update to a newer version of a custom rom, crDroid 6.4, I can no longer boot into the system. The phone only boots into recovery. TWRP no longer asks for a password in order to decrypt the phone, as it has done before. I have tried wiping Data, Cache, and Dalvik, and flashed the rom again, with no luck. Is it a way for me to force decrytion or something?
Any help is much appreciated! I am new to this, and still learning.

Ukulelen said:
After trying to update to a newer version of a custom rom, crDroid 6.4, I can no longer boot into the system. The phone only boots into recovery. TWRP no longer asks for a password in order to decrypt the phone, as it has done before. I have tried wiping Data, Cache, and Dalvik, and flashed the rom again, with no luck. Is it a way for me to force decrytion or something?
Any help is much appreciated! I am new to this, and still learning.
Click to expand...
Click to collapse
I assume that the data partition is actually still encrypted and you see random folder names in TWRP. If so, try formatting data in TWRP (not wipe, but format) then reboot to the ROM.

Robbo.5000 said:
I assume that the data partition is actually still encrypted and you see random folder names in TWRP. If so, try formatting data in TWRP (not wipe, but format) then reboot to the ROM.
Click to expand...
Click to collapse
Will this delete all my files?
Also, I'm not sure if I am flashing the ROM correctly. I have the ROM, magisk and other files on my computer. I use "ADB Sideload" under advanced in TWRP and "adb sideload romname.zip" on my computer.

Ukulelen said:
Will this delete all my files?
Also, I'm not sure if I am flashing the ROM correctly. I have the ROM, magisk and other files on my computer. I use "ADB Sideload" under advanced in TWRP and "adb sideload romname.zip" on my computer.
Click to expand...
Click to collapse
Yes it will delete all your files. If you boot to TWRP and it doesn't ask for the PIN, etc., but you see all your folders have random encrypted names, then everything is lost anyway. There is nothing you can do to recover that data.
In future just copy the ROMs onto the phone and flash them directly off the phone in TWRP, using the install menu.

Robbo.5000 said:
Yes it will delete all your files. If you boot to TWRP and it doesn't ask for the PIN, etc., but you see all your folders have random encrypted names, then everything is lost anyway. There is nothing you can do to recover that data.
In future just copy the ROMs onto the phone and flash them directly off the phone in TWRP, using the install menu.
Click to expand...
Click to collapse
Thanks for your help. Luckily I had backed up all my photos. I am up and running with a new rom. I am testing omni rom as it now comes with microg prebuild.