Database Info

[Q] Paranoid Android ROM

1. Download ROM
2. Download Gapps
3. Do a full wipe in recovery
4. Flash in TWRP or CWM recovery
5. Extract the boot.img and flash it with fastboot
Re the above installation instructions:
Do I have to download the ROM and Gapps on a pc then transfer to my phone or can I download using my phone?
Flashing in TWRP - I presume I have to flash both the ROM and Gapps, does it matter in which order this is done?
Thanks for any advice with this.

Paranoid Android 2.18
I'm experimenting with getting Paranoid Android up and running on my One S as well, and so far I've found that downloading the files on either handset or pc works fine. You are going to need that boot.img file on your pc to flash with fastboot eventually, though you can mount the device to USB within TWRP and extract it the same as any other compressed file. I typically flash the ROM first then Gapps, and have managed to get Paranoid Android up and running in this manner.
However, I have an ulterior motive posting because I am having an issue with PA 2.18, in that the Paranoid Settings module/apk/app (whatever it would be called) crashes or force closes immediately upon tapping it within settings. I have tried first flashing(w/TWRP 2.2.2.0) PA 2.17 as a fresh install/flashing the boot.img with fast boot, then upgrade installing to 2.18/again flashing the new boot.img with fast boot, and unfortunately I still have the Paranoid Settings module crashing upon launch. Any help from other PA users or anyone on xda with this issue would be greatly appreciated.

Sigh. If you read you would see that you need to install it as a separate APK file. It's in the OP.

Thanks for the reminder!
invasion2 said:
Sigh. If you read you would see that you need to install it as a separate APK file. It's in the OP.
Click to expand...
Click to collapse
Thanks for reminding me, I totally did read the OP and tried installing that ParanoidPreferences.apk both through adb and a simple file manager with root of course. It provided a couple unexpected results. Appreciate the effort though, simple things like that do get overlooked.
edit: The root access was set to apps only, enabling there then adb'ing to install seemed to solve the problem.

ADB push it to /data/app, not data/local . Or put it on your SD and move it manually.

[Q&A] BigPart Repartition Upgrade and Resource Center

Q&A for BigPart Repartition Upgrade and Resource Center
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 BigPart Repartition Upgrade and Resource Center. 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!

Exe files?
When I try to download the zips for BigPart Twrp and the wingray BigPart boot image, it downloads executable files? Why does it not just download the zip files as promised?

Exes
I tried downloading one and instead of downloading the zip file I wanted it downloaded EZ Downloader, and broke my Chrome browser. Why can we not just download the zip files required to change over to the BigPart repartition for xoom?

I made a huge mistake. I installed TWRP 2.6.3.0 fine. Unfortunately I got distracted and forgot to flash twrp bigpart. Instead I skipped to the step where you wipe everything but the sdcard, and when I rebooted to recovery, the screen hung on the teamwin splash screen. When I did a hard reset and tried to reboot manually into recovery I get the motorola dual core screen with a message saying "starting fastboot protocol support", and it just hangs there. Any help from you guys would be greatly appreciated.
Disregard, I finally got it to boot back into recovery manually and went on from there.

Guide
9) Go into install. Recovery should show your microsd storage by default. If not, using the navigation panel, navigate to root then go into "sdcard". Flash your rom, BigPart boot image package, and any other resources as you normally would.
Click to expand...
Click to collapse
But I don't see the files on the memory card
from FAQ
Q: Followed the instructions for the re-partitioning. Everything worked except the Xoom cannot see the external sd card in recovery. I have re-formated it as fat32 and tried another card. When I view the files in the PC they are there. Any ideas?
A: Something something went wrong... Copy the data from the SD to your PC, format SD and put back data. Let's see if that works...
Click to expand...
Click to collapse
it doesn't work
upd:
another card is working correctly!
upd2:
no need to flash BigPart boot image package!

Motorola Xoom bigpart repartition touch recovery
Hello, never rooted xoom but want to so I can have KitKat. When I try to download original TWRP 2.6.3.0 touch recovery it takes me to a smut video. Do you have a link to the real file. Also since I have never rooted this device, do I have to do something else before I follow the big part repartition upgrade. Sorry very green about this.
Thanks!

Trouble with flashing BigPart to WingRay unable to wipe or mount data
I have tried a lot of ways of flashing the BigPart partition (TWRP 2.8.6.0 for BigPart) but it seems that every way I do it is wrong. I think I followed the directions correctly but every time I do it I either get a password request to login to TWRP or it starts up but says that the data partitions is not able to be wiped or mounted. Most times I can not select the data check box. Please help me figure out what I am doing wrong or tell me were to go. I really want to flash the 5.1.1 but I am getting no where.

Accidentally deleted /system partition, PC doesn't recognize the phone anymore

Hello there.
My phone is in a state which is widely being reffered to as "bricked". After hours of reading through hundreds of forums and trying out everything possible/impossible, I came to this - I'm posting here, and desperately asking you guys for help.
I have Moto G XT1032. I converted it to GPE, to install a 5.0.1 ROM few months ago. I used it without any problems. However, today I decided to try out the stock 5.0.2 ROM. But I read that I'll have to change my Data partition to F2FS (from EXT4). I did that (using TWRP v2.8.5.0), and then I did this terrible mistake: I decided to do a clean install, so I wiped everything. I wiped System, and Internal storage as well. Yes, I know that I'm stupid.
Now my phone is stuck at my custom recovery (TWRP) or at bootloader. I can switch between these two, but I can't boot to the system, because I don't have any system installed (because I wiped the /system partition - what an Einstein I am -_-). I thought that it would be easy - I just have to somehow push the zip file of the new ROM to my phone, and then install it from TWRP. The thing is - I can't transfer any files to the phone. I'm probably missing some drivers, but the problem is, that the phone doesn't have any operating system installed (besides bootloader, I guess) - so I can't get any drivers working. My PC is running Windows 7 64bit.
I tried installing Motorola Device Manager, I tried using the drivers from android-sdk, but nothing helped. When I type a command "adb devices" to a command line, it says: "List of devices attached >emtpy line<". When I connect the phone to the PC, it doesn't even try to look for drivers anymore. I tried deleting them (drivers), placing there some new, but again - nothing helped. If anyone can provide any help, I'd be very, very, very glad.
Thanks in advance.
//edit: Nevermind, I made my phone alive again. I just had to use mfastboot tools. Moderators can close or delete this thread, please. I'm sorry for creating it, since it was kinda useless.

temme how to recover the system folder. i have a system folder on my desktop. help me. my phone isnt turing on

If you can get into fastboot and recover you can restore your phone. You just need a complete ROM, and restore it with mfastboot method.
It doesn't matter if you wiped system, you can do that in TWRP, if you reboot it won't boot into the OS (obviously) but go into fastboot mode.
Download mfastboot, a ROM image, and go through the command lines. There is a FAQ on how to restore.

felmaster said:
Hello there.
My phone is in a state which is widely being reffered to as "bricked". After hours of reading through hundreds of forums and trying out everything possible/impossible, I came to this - I'm posting here, and desperately asking you guys for help.
I have Moto G XT1032. I converted it to GPE, to install a 5.0.1 ROM few months ago. I used it without any problems. However, today I decided to try out the stock 5.0.2 ROM. But I read that I'll have to change my Data partition to F2FS (from EXT4). I did that (using TWRP v2.8.5.0), and then I did this terrible mistake: I decided to do a clean install, so I wiped everything. I wiped System, and Internal storage as well. Yes, I know that I'm stupid.
Now my phone is stuck at my custom recovery (TWRP) or at bootloader. I can switch between these two, but I can't boot to the system, because I don't have any system installed (because I wiped the /system partition - what an Einstein I am -_-). I thought that it would be easy - I just have to somehow push the zip file of the new ROM to my phone, and then install it from TWRP. The thing is - I can't transfer any files to the phone. I'm probably missing some drivers, but the problem is, that the phone doesn't have any operating system installed (besides bootloader, I guess) - so I can't get any drivers working. My PC is running Windows 7 64bit.
I tried installing Motorola Device Manager, I tried using the drivers from android-sdk, but nothing helped. When I type a command "adb devices" to a command line, it says: "List of devices attached >emtpy line<". When I connect the phone to the PC, it doesn't even try to look for drivers anymore. I tried deleting them (drivers), placing there some new, but again - nothing helped. If anyone can provide any help, I'd be very, very, very glad.
Thanks in advance.
//edit: Nevermind, I made my phone alive again. I just had to use mfastboot tools. Moderators can close or delete this thread, please. I'm sorry for creating it, since it was kinda useless.
Click to expand...
Click to collapse
Also TWRP/CWM has support for adb, u just need to install the drivers manually. Then you can push whatever you want.
Of course you can try restoring stock as suggested above.

How did u fixed it? :/

As a last resort there is always OTG (this thing has OTG support right?). Life was so much simpler when you could just put your sd card into a card reader and put your zip on there. A quick google search makes me think its got support, but who knows

TF300T Terminal Emulator TWRP.blob HELP!

Hey guys, I need a little help getting the Custom Recovery TWRP to work with terminal emulator.
I have the Asus Transformer Pad TF300T(WIFI Only)
Android Version: 4.2.1
Build Number: 10.6.1.27.5
Bootloader: Unlocked with Asus Unlock Tool(Restart with small print in top left corner "This device is unlocked")
Root: Rooted with KingoRoot
My problem is everytime I open up the Terminal Emulator(The reason for using this method is because I dont have a USB cable to connect to the computer) I type in
SU (a little popup shows it granted superuser access)
I then type in
dd if=/removeable/microsd/twrp.blob of=/dev/block/mmcblk0p4
It then tells me
/removeable/microsd/twrp.blob: cannot open for read: No such file or directory
Full Terminal Emulator DOS screen:
[email protected]: / $ SU
[email protected]: / # dd if=/removeable/microsd/twrp.blob of=/dev/block/mmcblk0p4
/removeable/microsd/twrp.blob: cannot open for read: No such file or directory
I have the file renamed to TWRP.blob. I also have a TWRP.img that I've tried and its in the root of my sd card. I've even tried formatting my sd card for android because before this i never used it for anything.
Any help would be appreciated.

Bamablood94 said:
a little popup shows it granted superuser access
Click to expand...
Click to collapse
Download the SuperSU (Chainfire) from Playstore. Then you will get access to the Terminal Emulator.
PS: Please download Kang TWRP 2.8.7.2 here: https://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479. This is the right TWRP version you need for both KatKiss Rom N7.1.1 and MM 6.0.1. There is also an install instruction for using Terminal.

ebonit said:
Download the SuperSU (Chainfire) from Playstore. Then you will get access to the Terminal Emulator.
PS: Please download Kang TWRP 2.8.7.2 here: https://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479. This is the right TWRP version you need for both KatKiss Rom N7.1.1 and MM 6.0.1. There is also an install instruction for using Terminal.
Click to expand...
Click to collapse
Trying it now will update in a second
I already had SuperSU access to the terminal emulator and Ive already tried with that TWRP but i still get the same thing No such file or directory

I used TWRP Manager app and installed twrp 3.0.2.0 recovery now all i need to do is download a custom rom and i should be set right?

Bamablood94 said:
I've even tried formatting my sd card for android
Click to expand...
Click to collapse
I think the communication problem might be your SD card. The format must be FAT 32. Either reformat it on your PC or use a new one.
The terminal code is "dd if=/sdcard/foo.img of=/dev/block/mmcblk0p4", "foo" stands for "twrp_tf300t_kang_2.8.7.2_signed."
This command also expects the file "twrp_tf300t_kang_2.8.7.2_signed.image" to be on /sdcard.
Take care that the terminal can communicate with your SD card. That means the command has to be written very very correctly. No capital letters for instant.
---------- Post added at 09:13 PM ---------- Previous post was at 09:03 PM ----------
Bamablood94 said:
I used TWRP Manager app and installed twrp 3.0.2.0 recovery now all i need to do is download a custom rom and i should be set right?
Click to expand...
Click to collapse
To avoid issues you need Kang TWRP 2.8.7.2. This is the right TWRP version recommended by the developer Timduru for both KatKiss Rom N7.1.1 and MM 6.0.1.

ebonit said:
I think the communication problem might be your SD card. The format must be FAT 32. Either reformat it on your PC or use a new one.
The terminal code is "dd if=/sdcard/foo.img of=/dev/block/mmcblk0p4", "foo" stands for "twrp_tf300t_kang_2.8.7.2_signed."
This command also expects the file "twrp_tf300t_kang_2.8.7.2_signed.image" to be on /sdcard.
Take care that the terminal can communicate with your SD card. That means the command has to be written very very correctly. No capital letters for instant.
I'll have to try that cause if I'm not mistaken it formatted to NTFS.
---------- Post added at 09:13 PM ---------- Previous post was at 09:03 PM ----------
To avoid issues you need Kang TWRP 2.8.7.2. This is the right TWRP version recommended by the developer Timduru for both KatKiss Rom N7.1.1 and MM 6.0.1.
Click to expand...
Click to collapse
Can I use the recovery to install it or TWRP manager app or am I gonna have to do the terminal emulator
It successfully installed katkis mm6.0.1

ok so i downloaded the twrp and the file it downloaded is "twrp_tf300t_kang_2.8.7.2.img" do i leave it like it is and in the terminal type foo.img or can i rename it to twrp.img and then twrp.img in the terminal?

Bamablood94 said:
ok so i downloaded the twrp and the file it downloaded is "twrp_tf300t_kang_2.8.7.2.img" do i leave it like it is and in the terminal type foo.img or can i rename it to twrp.img and then twrp.img in the terminal?
Click to expand...
Click to collapse
NO!!! Just stay on 3.0.2. You are fine with that version. It's the latest released for this tablet and sooner or later those still on lj's kang version will have to update anyway. ..
If amazing master wizard Tim still keeps cranking out roms this tablet was never supposed to see.
You're good, you did good, but get the heck yourself a USB cable so that you have fastboot access. I hate to watch trapeze artists working without a net!!!
It's $7 on Amazon - no excuses accepted!
https://www.amazon.com/Charging-Sync-Cable-TF101-TF201-TF300/dp/B007QUBYDY

berndblb said:
Just stay on 3.0.2. You are fine with that version. It's the latest released for this tablet and sooner or later those still on lj's kang version will have to update anyway. ..
If amazing master wizard Tim still keeps cranking out roms this tablet was never supposed to see.
Click to expand...
Click to collapse
It is known that I belong to those user who swear on Tim's install instruction. This includes the advise in the first line there "You need Kang TWRP". Following that advise I have never had any TWRP issues. Are you really sure that an update on the latest TWRP won't cause any issues?
There is still the old wisdom in my mind "Never change a running system". Anyhow your advise is greatly appreciated.

ebonit said:
It is known that I belong to those user who swear on Tim's install instruction. This includes the advise in the first line there "You need Kang TWRP". Following that advise I have never had any TWRP issues. Are you really sure that an update on the latest TWRP won't cause any issues?
There is still the old wisdom in my mind "Never change a running system". Anyhow your advise is greatly appreciated.
Click to expand...
Click to collapse
I am sure.
There is nothing magically different or better about the Kang TWRP. It supports the dock SD which the official TWRP never did, but that's a feature I have used maybe twice in all that time I used it. Other than that there are some additional reboot options and GUI changes if I remember correctly, but the core is just TWRP. I think at the time lj made the recovery the offical TWRP had a bug with the f2fs conversion - can't quite remember - but for a while it was the go-to recovery for both the TF300 and TF700.
Don't get me wrong - it's a perfectly fine recovery and for all I know still supports even Nougat roms. There is no reason for you to change it if you stay on the same rom. But there's also no reason for somebody who flashed a 3.+ version already to downgrade to 2.8. Documented by the fact that Bamablood94 flashed Katkiss successfully.

berndblb said:
I am sure.
Don't get me wrong - it's a perfectly fine recovery and for all I know still supports even Nougat roms. There is no reason for you to change it if you stay on the same rom. But there's also no reason for somebody who flashed a 3.+ version already to downgrade to 2.8. Documented by the fact that Bamablood94 flashed Katkiss successfully.
Click to expand...
Click to collapse
Thanks a lot for your very instructive reply. I'm gonna to stay on Josh's TWRP until I change the rom.

berndblb said:
I am sure.
There is nothing magically different or better about the Kang TWRP. It supports the dock SD which the official TWRP never did, but that's a feature I have used maybe twice in all that time I used it. Other than that there are some additional reboot options and GUI changes if I remember correctly, but the core is just TWRP. I think at the time lj made the recovery the offical TWRP had a bug with the f2fs conversion - can't quite remember - but for a while it was the go-to recovery for both the TF300 and TF700.
Don't get me wrong - it's a perfectly fine recovery and for all I know still supports even Nougaamt roms. There is no reason for you to change it if you stay on the same rom. But there's also no reason for somebody who flashed a 3.+ version already to downgrade to 2.8. Documented by the fact that Bamablood94 flashed Katkiss successfully.
Click to expand...
Click to collapse
I am now running nougat 7.1.1 from katkiss using the twrp 3.0.2.0 using the TWRP Manager app and also downloaded the mini GApps. I didnt realize that was something I also had to install until i realized there was no play stor or any other google related apps but I have invested in a 5 dollar usb data cable from ebay which should come in sometime this week. My other problem now seems to be that this thing dont like running too many apps in the background and when you first start up a program it likes to lag it a tad bit untill it runs a little smoother. I appreciate the help guys.

Welcome to the wonderful world of the Transformer, my friend. If you expect this tablet to run anywhere close to the performance of any current device, you will be disappointed.
Asus thought up a genius form factor and then ruined it by crippling it by not giving it enough ram and a cheap, slow memory chip on top of it.
You have to go easy on this baby.
Turn off automatic updates in the Play Store.
Turn off automatic updates and syncing for as many apps as you can stand.
If you don't use an app, get rid of it.
Do NOT use the Facebook app. It's a piece of cra** anyway and really hard on resources
In the 700 forum Tim posted some fine tuning tips a while back. If I find it, I'll add the link later
Develop a good backup/restore routine (e.g Titanium Backup) and then format data every 3 months or so - depending on how much you use the tablet.
If you haven't, convert /data to f2fs. That really helps on this tablet let.
Enjoy
https://forum.xda-developers.com/showpost.php?p=71095273&postcount=362
There you go! Helps to organize your bookmarks. [emoji6]
The tips are in a TF700 thread, but the two tablets are almost identical. They should work for your tablet as well

berndblb said:
https://forum.xda-developers.com/showpost.php?p=71095273&postcount=362
There you go! Helps to organize your bookmarks. [emoji6]
The tips are in a TF700 thread, but the two tablets are almost identical. They should work for your tablet as well
Click to expand...
Click to collapse
BTW, the same tips put Tim in a TF300T thread as well:
https://forum.xda-developers.com/showpost.php?p=71094836&postcount=615
To my opinion the best performance with KatKiss N7 on the TF300T will be reached with a RAM use of around 65%. That means to keep the amount of apps as low as possible. In my case up to 45 apps, but mostly less. Always have an eye on piggy apps.

I appreciate the help guys I don't use the tablet much since I have an Asus phone but I install the zenui launcher and to my surprise it seemed to help the "lag" just a bit. Again I appreciate the help I don't get on xda often but when I need help this is my go to place.

Sideload twrp backup?

So ive searched for an answer to this but couldnt find it with google/xda.
I tried to install a custom rom.
My first rom install attempt ever on android
It failed with a signal 11 error
So after lots of trouble shooting trying any "fix" I could find suggested.
I read wiping before a rom install was required.
So I made a twrp backup, placed it on my pc, this is where I messed up and nobody in the countless threads I read said
I deleted the twrp backup on device
Then wiped with twrp, following the era proper directions for device allegedly.
Which was wipe everything but internal storage, also read to format in the many topics I perused.
Then found everything was wiped, including /sdcard, and system/OS
WELL I STILL GOT SIGNAL 11 on rom flash attempt via sideload, since the zip got erased on sd.
I did manage to flash a rom, but wouldnt you know it, its a rom that cant connect to pc through usb.
If I try to push the twrp backup folder, it just says error in cmd while in sideload
Anybody know the proper way to do that? Or is it just a case of murphys law getting a right good laugh at my devices expense.
I did read I could use a micro usb to external storage to mount, but I lack that.
I need to restore twrp because I think I need to pull the vendor directory off device to try to overcome the signal 11 error.
Anyway any advice is appreciated and hopefully can serve others in the future.
Thanks and cheers

Re-flash Stock ROM.

Well I dont think the device in question has a stock rom. Or I cant find one at first glance.
I had to roll back the version to unlock bootloader and root.
But that .bin wouldnt help I think.. hmm
Back to the drawing board I guess.
Perks of a decade old device.

Apparently androidmtk.com has stock roms available, but is that site safe to use?
Sorry for my noobiness.
Edit: actually that bin is the stock firmware apparently. I hope at least.
Will try and report back.
Thanks jwoegerbauer
Edit2: that worked flashing the bin. Was able to mount on pc and add the backup back up.
Did have a stumble as without making a backup there wasnt a backups folder. I tried to manually create one, but twrp couldnt see the folder I made.
Not sure if it was the naming. I tried "Backups" but twrp created "BACKUPS"
I just backed up efs since it was smallest to get twrp to make it.
Cool. Now I can backup vendor for rom comparison. Was overstressed for half the day about it, but the solution was simple and right there in front of me.
Thanks again Jwoegerbauer

what do you mean "it's a rom that can't connect to pc through usb"?
what do you mean "was able to mount on pc"?
you have backup of old ROM on pc. what do you want to do with?

No worries alecxs
Yeah I was able to sideload a custom rom but that rom had broken/missing usb drivers so mtp on pc failed.
That was before I knew I had the stock rom.
I needed stock rom to be able to restore with twrp in order to pull vendor folder off original device.
(I need vendor folder to try to fix that broken custom rom)
Just me being a noob. Sorry again.

you're welcome. just asking for clarity.
you have answered one question, so let me give you hint on guesswork.
you can connect device with usb-debugging from developer options. adb is the recommended way to transfer files. MTP is a faulty implemented Microsoft protocol I wouldn't use for large amount of data (for small files is okay).
Android devices cannot mounted since Android 5.0.1 Lollipop as UMS has been dropped in favour of MTP. /sdcard is no longer separate FAT partition but emulated storage in /data/media.
Bear in mind TWRP backup does not include /data/media so one have to backup pictures manually. this can be done from adb.
Code:
adb pull -a /sdcard
For the same reason you will lose /sdcard every time you format /data.
If you're interested to restore backup to different ROM, you cannot use TWRP. backup of /data can only restored to the exact same ROM.
For restoring backup to different ROM use Migrate.
[APP][ROOT][5.0+][1st Nov 2020] Migrate - custom ROM migration tool
Jumping from one custom ROM to another can be a challenging task. So I decided to make an app to simplify the process. Introducing Migrate! Migrate-GPE (v4.0) is on Google Play It was temporarily suspended. Read more here...
forum.xda-developers.com