Database Info

Updating Android 4.1

Hey there, guys. I've been around XDA a while & have messed around with different ROMS. I had found one that I liked (decent battery life is the most important for me) & stuck with ParanoidAndroid 3.60 (4.2 based ROM) for Android 4.1 (I believe the firmware version is 10.4.2.20). TWRP is 2.5.0.0. This was around 1-2 years ago, and I finally decided it was time to upgrade it.
Can anyone point me the direction on where to start? I would like to update to the latest (or most stable) android version, if possible. I have a basic knowledge of fastboot & how it works.:fingers-crossed:

First, you will have to upgrade your bootloader to the latest version to run the latest recovery. I don't know if there's an easier way of doing this, but I'd suggest installing a stock ROM and then unlocking/rooting/installing recovery again.
You can download the latest official firmware from here (assuming you have a TF300T model): http://www.asus.com/Tablets_Mobile/ASUS_Transformer_Pad_TF300T/HelpDesk_Download/
Make sure to select the one with the correct SKU.
Then, follow this guide: http://forum.xda-developers.com/showthread.php?t=1757077
This will wipe all your data so make sure to backup all the files you need.
The bootloader will most likely remain unlocked, so what you need now is root and recovery. There are plenty of guides for those, so find the right one for you. You can download the latest TWRP from here: http://teamw.in/project/twrp2/97
An installation guide is on the same page, but make sure to download the one ending with 4.2 since you will be on the latest firmware version (here's the name of the file you'll probably need if you have a TF300T model: openrecovery-twrp-2.6.3.0-tf300t-4.2.blob).
Hope this will help

Duchman said:
First, you will have to upgrade your bootloader to the latest version to run the latest recovery. I don't know if there's an easier way of doing this, but I'd suggest installing a stock ROM and then unlocking/rooting/installing recovery again.
You can download the latest official firmware from here (assuming you have a TF300T model): http://www.asus.com/Tablets_Mobile/ASUS_Transformer_Pad_TF300T/HelpDesk_Download/
Make sure to select the one with the correct SKU.
Then, follow this guide: http://forum.xda-developers.com/showthread.php?t=1757077
This will wipe all your data so make sure to backup all the files you need.
The bootloader will most likely remain unlocked, so what you need now is root and recovery. There are plenty of guides for those, so find the right one for you. You can download the latest TWRP from here: http://teamw.in/project/twrp2/97
An installation guide is on the same page, but make sure to download the one ending with 4.2 since you will be on the latest firmware version (here's the name of the file you'll probably need if you have a TF300T model: openrecovery-twrp-2.6.3.0-tf300t-4.2.blob).
Hope this will help
Click to expand...
Click to collapse
Thanks for replying! I got it to boot, but it stays stuck on the Asus logo with the loading circle. I installed the correct TWRP recovery. I tried rebooting, but it says no OS installed. Furthermore, it does not mount the External storage. I can browse the files through the file Manager in TWRP.
EDIT: It rebooted & I have everything back. It just took forever to reboot. Thanks for your help!!

boxer3310 said:
Thanks for replying! I got it to boot, but it stays stuck on the Asus logo with the loading circle. I installed the correct TWRP recovery. I tried rebooting, but it says no OS installed. Furthermore, it does not mount the External storage. I can browse the files through the file Manager in TWRP.
EDIT: It rebooted & I have everything back. It just took forever to reboot. Thanks for your help!!
Click to expand...
Click to collapse
I'm glad I was able to help. Could you tell me the order of your actions and what happened after what? I'm a bit confused as to why it'd get stuck like this.
Also, you might need a newer recovery for more recent ROMs. There are both 2.7.0.1 and 2.7.1.0 versions available in the development section.

Duchman said:
I'm glad I was able to help. Could you tell me the order of your actions and what happened after what? I'm a bit confused as to why it'd get stuck like this.
Also, you might need a newer recovery for more recent ROMs. There are both 2.7.0.1 and 2.7.1.0 versions available in the development section.
Click to expand...
Click to collapse
I did everything as you posted:
1. Downloaded the most current firmware for the TF300T from the Asus site.
2. Pushed it to my device using fastboot
3. Installed custom recovery for my version of Android
4. Rebooted.
The Installation bar completed after I pushed the firmware & recovery. It just took long to reboot. I read that you have to let the ROM "stabilize," so I suspect it might have been the cause of the hang. Everything went pretty smooth after the reboot, though. I installed TWRP 2.7.1.0 (as you posted above) and installed a new ROM. Thank you very much for taking the time to reply. I love this update! :victory:

[Q] recovery partition not found

Hello,
First off, I am a total noob and probably should not have been messing with my phone before knowing exactly what I was doing. I have a Nexus 5 that I rooted with towelroot. I had xposed framework installed with some other cool tweaks. I should have stopped there. I followed the tutorial on PhoneArena yesterday titled How to download and install the Android L beta update on your Nexus 5. I downloaded and flashed the modified kernel, the SuperSU mode, and the new radio.
I had a backup kernal and recovery set up through Flashify/TWRP. The flash and installation worked. When I tried to flash the N5_L_PREV_LPV79.zip to the newer N5_L_PREV_LPV81C.zip my phone said "your recovery partition couldn't be found. You won't be able to flash recovery images. You can still flash images. It said the same thing about my boot partition. Is there anything I can do to get these partitions back? I know I shouldn't have been jacking with everything without proper knowledge. I appreciate any help you can give me.
Thank you,
Patrick

[Q&A] [MOD][OCT 21] MultiROM v29

Q&A for [MOD][OCT 21] MultiROM v29
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 [MOD][OCT 21] MultiROM v29. 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!

recovery issue!
I'm facing a weird issue! When i try to flash an android l preview based rom as a primary rom,it gets stuck at formatting systems!...its fine with kitkat roms! i can't solve this! please help me !

Hi, I have android l preview has secondary rom and I would like to know how to root it or flash a .zip for it. Thank you!

If I flash any .zip file by recovery. In which rom it will be installed? is it primary rom or secondary?

Riyad Pradhan said:
If I flash any .zip file by recovery. In which rom it will be installed? is it primary rom or secondary?
Click to expand...
Click to collapse
If you use the Install, Backup or Wipe options when you first get to recovery are your internal (primary) rom.
All secondary roms are located in Multirom/manage roms/

Please help me.
I installed multirom from the appstore, (rooted my phone before) - then pressed install there - phone rebooted into twrp and then rebooted again. and then it was stuck into the booting screen or how you call it (1+1 logo without any animation). what should i do now? how do i get this fixed? i need my phone back!

memylo said:
I installed multirom from the appstore, (rooted my phone before) - then pressed install there - phone rebooted into twrp and then rebooted again. and then it was stuck into the booting screen or how you call it (1+1 logo without any animation). what should i do now? how do i get this fixed? i need my phone back!
Click to expand...
Click to collapse
Strange, I would try restoring your nandroid and flashing a patched kernel and MultiRom in recovery.

thereal_bigjake said:
Strange, I would try restoring your nandroid and flashing a patched kernel and MultiRom in recovery.
Click to expand...
Click to collapse
Can you explain me how to do this stuff? I installed a uninstall zip for multirom and did a factory reset and was able to install paranoid android, but i want to go back to the stock cm11s. The rom provided by Cynogenmod gives me a error with invladid meta inf.

memylo said:
Can you explain me how to do this stuff? I installed a uninstall zip for multirom and did a factory reset and was able to install paranoid android, but i want to go back to the stock cm11s. The rom provided by Cynogenmod gives me a error with invladid meta inf.
Click to expand...
Click to collapse
First make sure your bootloader and radio are up to date.

Regarding Tassadr's recovery flashable zips, I have one question: what will happen with google OTA updates? Since the recovery is not overwritten, I assume they wouldn't exactly work as usual. Any insight or precautions I should take?

So, these factory image zips don't have a recovery? And won't wipe my data/sdcard correct? So I 'should' be able to dirty flash over the dev preview. Or if not, I will at least still have my custom recovery to restore a nandroid?

So I flashed the lollipop stock rom, threw on super su and francos kernel as secondary rom, but I cannot connect to wifi. Any idea how to fix wifi?

The problem seems to be related to DHCP. I clicked on the advanced option and entered a static IP instead of DHCP and I was able to connect.

Why I can't see multirom boot menu? I press and hold volume up or down but nothing, why?

TWRP Splash
I'm trying to replace the curtain on team win. ive done it before on a different device (no multirom) by unpacking it with (http://www.techknow.me/forum/index.php?topic=6816.0) replacing the curtain.jpg with my custom one, repacking with the same program, and then flashing through flashify. (twrp manager didnt work. no idea why. and the phone couldnt fastboot flash so i couldnt test that, but flashify worked and it replaced the curtain perfectly). my nexus 5 w/ multirom recovery doesnt work though. unpack works. changing curtain works. repack works. but no method of flashing it works. no matter how i flash it, i dont seem to have a recovery. (booting to recovery sticks me at the google screen with the padlock) does anyone have success replacing the curtain or have any clue what im doing wrong? or if its possible?

MistaEast said:
I'm trying to replace the curtain on team win. ive done it before on a different device (no multirom) by unpacking it with (http://www.techknow.me/forum/index.php?topic=6816.0) replacing the curtain.jpg with my custom one, repacking with the same program, and then flashing through flashify. (twrp manager didnt work. no idea why. and the phone couldnt fastboot flash so i couldnt test that, but flashify worked and it replaced the curtain perfectly). my nexus 5 w/ multirom recovery doesnt work though. unpack works. changing curtain works. repack works. but no method of flashing it works. no matter how i flash it, i dont seem to have a recovery. (booting to recovery sticks me at the google screen with the padlock) does anyone have success replacing the curtain or have any clue what im doing wrong? or if its possible?
Click to expand...
Click to collapse
I followed this guide and everything worked the first try. I've repacked quite a few now with no problems.
http://goo.gl/EWw71q
Bonus: you can flash recovery with the Material twrp theme.

I couldnt get android kitchen working this way. Idk what i did wrong but it wasnt unpacking the file at all. So i found a work around with the program i linked to. You just unpacked, replaced, repacked, and flashed the multirom recovery and it worked?

MistaEast said:
I couldnt get android kitchen working this way. Idk what i did wrong but it wasnt unpacking the file at all. So i found a work around with the program i linked to. You just unpacked, replaced, repacked, and flashed the multirom recovery and it worked?
Click to expand...
Click to collapse
Yep works no problem. I was able to use that method on Linux Mint and right on my Nexus 5.

Last question, Did u do it on a windows machine as well? I know Kitchen is a lot easier to install/works better on linux.

MistaEast said:
Last question, Did u do it on a windows machine as well? I know Kitchen is a lot easier to install/works better on linux.
Click to expand...
Click to collapse
No, I don't use Windows at all.

Custom ROM Issue... Stuck Booting...

Hey androids, I submitted this question as a reply to the guide thread already earlier... just thought it might get noticed in this forum alittle quicker... any help would be appreciated
I'm working on a recalled tablet that I rooted to keep using, and up until recently the ROM i had installed on it worked famously (bliss pop with android 5.1.1). Now, I was having some issues with it and thought "Well, i'll try out a different rom!"
So, I already had root (obviously) and I had already successfully installed a rom to this tablet... Using TWRP (both the 2.8.x.x I used previously and the newest one available for the shield) I have backed up, wiped, and flashed the images to 3 different roms + gapps for the appropriate versions...
first, I was going an issue with it mounting the \data partition so it wouldn't flash anything... then I repaired and rewiped the partitions, and got (what appeared to me in the logs) a clean and successful install of the roms. Each time I successfully flashed a ROM and GAPPs zips I would go to boot the ROM and my table would sit on the "NVIDIA" boot screen forever, never advancing to boot the ROMs.
I was worried that I had made a mistake and bricked the thing (though, it's been on borrowed time anyways being a recalled tablet). But I was able to force shutdown the tablet and reboot it into TWRP for another try. Each time I cleared the previous flash, wiped the cache and system partitions, and would get another clean install... but each time, it would get stuck on that same boot screen....
Anyone have any suggestions? thoughts? ideas? fixes? answers?.... anything? lol
Thanks folks!

Assuming you are trying to flash MM custom roms: You need the MM bootloader.

edisso10018 said:
Assuming you are trying to flash MM custom roms: You need the MM bootloader.
Click to expand...
Click to collapse
Is the newest TWRP *not* a MM bootloader?

TWRP is a recovery. A bootloader is a bootloader.

This is covered in every rom thread that updated from L to M.

lafester said:
This is covered in every rom thread that updated from L to M.
Click to expand...
Click to collapse
I'll re-look, the guides i've read have only covered flashing TWRP, then using them to flash the ROM and GAPPs... Which is what I did the first time I rooted it and put on a custom ROM... though maybe I didn't delete the original bootloader the first time and did so accidentally this time?

Thanks for the heads up though people, we'll see if I can straighten it out now that I know what I'm looking for

edisso10018 said:
Assuming you are trying to flash MM custom roms: You need the MM bootloader.
Click to expand...
Click to collapse
Ok, so I've downloaded the shield recovery zip, flashed the boot.img to the boot... nothing, then I read on one of the guides here that the "blob.img" is the bootloader... but the zip has a blob, without the .img
So I then attempted to add .img, and flash it to "boot" in TWRP, and there was an error, saying the file is too large...
do you (or someone else) know where to find a guide on where to find/how to flash a MM bootloader?
thanks

Ok, so I found guide with links to the latest firmware update; I flashed it, rebooted, and now I've gotta past the "Nvidia" boot screen into the Bliss boot screen... It's been here for a couple minutes now, gonna give it alittle bit and then try to install the other ROM I had tried.

MilesD37 said:
Ok, so I found guide with links to the latest firmware update; I flashed it, rebooted, and now I've gotta past the "Nvidia" boot screen into the Bliss boot screen... It's been here for a couple minutes now, gonna give it alittle bit and then try to install the other ROM I had tried.
Click to expand...
Click to collapse
Im stuk with the same probem, can you sendme the Link to the gide please

Latest TWRP not working

Hello guys,
I have a p5113 tablet that i have been having trouble with. I have tried flashing like 5 different roms and they all boot loop. I think its because I am using an old recovery (Device Specific TWRP 3.0.0-0) the problem is only the old recoveries are working for me. When i flash the latest common TWRP (3.0.3-0) Wiping gets stuck at updating partition details, it wont install any roms it stays at "detected filesystem ext4", and if I try to reset the tablet through TWRP menu it wont do anything. When I use the old recoveries it flashes and wipes fine. When i flash stock rom through odin, the system works fine. I have tried different versions of the latest twrp but to no avail. Thank you in advance for your help.
EDIT: I finally have a custom rom working on this tablet, it is Dhollmen stock 4.2.2 with GT-P5110_PhilZ-Touch-Recovery_6.59.2. recovery, device specific TWRP 3.0.0-0 would give me error 7. Im very happy but I would like to get Marshmallow on this tablet if anyone can help with that.

Install the 3.0.3-0 common TWRP, then try to format data (Wipe ->Format Data-> type yes). Reboot recovery once and then perform a wipe of all partitions (Wipe->Advanced Wipe-> select everything). If you get stuck at "updating partition details..." just wait. It could take as long as five minutes some times to get unstuck.
This is the link for the thread of Slim6, the mm rom I recommend by Andi:
https://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified/rom-slim6-t3414798/page1
And this is an aosp mm rom also by Andi, try it if above fails
http://builds.unlegacy-android.org/aosp-6.0
Flash both with TWRP 3.0.3-0
If problems continue, post the recovery log (you can find it after reboot at /cache/recovery/ )

landetta said:
Hello guys,
I have a p5113 tablet that i have been having trouble with. I have tried flashing like 5 different roms and they all boot loop. I think its because I am using an old recovery (Device Specific TWRP 3.0.0-0) the problem is only the old recoveries are working for me. When i flash the latest common TWRP (3.0.3-0) Wiping gets stuck at updating partition details, it wont install any roms it stays at "detected filesystem ext4", and if I try to reset the tablet through TWRP menu it wont do anything. When I use the old recoveries it flashes and wipes fine. When i flash stock rom through odin, the system works fine. I have tried different versions of the latest twrp but to no avail. Thank you in advance for your help.
EDIT: I finally have a custom rom working on this tablet, it is Dhollmen stock 4.2.2 with GT-P5110_PhilZ-Touch-Recovery_6.59.2. recovery, device specific TWRP 3.0.0-0 would give me error 7. Im very happy but I would like to get Marshmallow on this tablet if anyone can help with that.
Click to expand...
Click to collapse
have you used the twrp on the http://andi34.github.io/ website? and roms compiled before 3/22/16 dont flash with common twrp when I updated twrp I had downloaded the zip and went into twrp to flash it I havent used a pc at all to install twrp and root . so I just put the zip on my sd card and it updated it did you update twrp with odin?

Thank you for your reply,
Yes I used the recoveries from Android Andi, and yes I have installed recoveries in zip form through recovery and Odin. Unfortunately neither have worked. I did use the latest recoveries when I tried to install the newer roms but it just gets stuck, I can't even make nandroid backups it also gets stuck with the newer recoveries.
Edit:
@ john99ap Sorry i just got home, I tried what you said but it just got stuck at both wipes, I waited 10 mins but a no-go. I found the logs, I couldn't paste them in here because it exceeded character length so I put it in pastebin. I didn't know which log to use so I am giving you the ones that I think are more relevant
Log:
pastebin/gpWgBEm7
Last_log:
pastebin/12uLYgwS
Last_log.10
pastebin/asePpLBa
Thank you guys again for your help!

landetta said:
Log:
pastebin/gpWgBEm7
Last_log:
pastebin/12uLYgwS
Last_log.10
pastebin/asePpLBa
Thank you guys again for your help!
Click to expand...
Click to collapse
I can't find anything in these logs
I need the log in which you try to install the zip file.
Try this:
-Install TWRP 3.0.3-0 (if it's not already there)
-Reboot and delete all recovery logs you can find
-Install the zip without doing anything else before or after so that the log is as clean as possible
-Post any log you find
PS: you could upload logs in your reply by hitting the button with a stapler on the bottom left corner

Thanks for your reply, sorry about the old logs, here are the new ones like you requested. Hopefully you find something in these new ones. Thanks again for all your help BTW I don't have any staples in my advanced reply so I had to use Pastebin again sorry. I think its because of my low post count.
pastebin/UcntGLTZ
pastebin/Fq8V7WUf
PS: Not even the reboot button works on 3.0.3-0.

Sorry but I can't find anything in these logs either. Maybe it's my fault since I 'm not an expert
At your first post you said device specific twrp gives you error 7. This is caused by a safety check in which your recovery checks if your device is compatible with the rom. In your case, it must be a mistake of the recovery (I had the same issue with my p3110 device specific twrp). So you could just remove the safety check.
Here's how to do it:
- Go to the zip you want to install and find the file /META-INF/com/google/android/updater-script
-Edit it with a text editor and remove the first line (it begins with asserts and ends at the first semicolon)
-Install the zip
Good luck!

john99ap said:
Sorry but I can't find anything in these logs either. Maybe it's my fault since I 'm not an expert
At your first post you said device specific twrp gives you error 7. This is caused by a safety check in which your recovery checks if your device is compatible with the rom. In your case, it must be a mistake of the recovery (I had the same issue with my p3110 device specific twrp). So you could just remove the safety check.
Here's how to do it:
- Go to the zip you want to install and find the file /META-INF/com/google/android/updater-script
-Edit it with a text editor and remove the first line (it begins with asserts and ends at the first semicolon)
-Install the zip
Good luck!
Click to expand...
Click to collapse
Awe thanks anyways dude, I really appreciate you trying. One last thing, on Andi's website he say that device specific 3.0.0-0 recovery should work to flash the latest roms. If anyone can confirm this maybe I can get the new roms working on it. Thanks again for all your help john99ap :good: