Related
This is a guide of how to dualboot KitKat and Android Lollipop on a Nexus 5. This will allow you to test out Lollipop while keeping a stable ROM to run as a daily driver. I am running CM11, but you can do this with any KitKat ROM, even stock.
REQUIREMENTS
Nexus 5
Root
Unlocked bootloader
MultiROM
A brain
At least 1 GB of free space (I recommend 4 GB though)
1. Setting up.
I'm assuming you are already rooted if you are planning on doing this. If not, follow this guide to root and unlock the bootloader. http://forum.xda-developers.com/google-nexus-5/orig-development/nexus-5-cf-auto-root-t2507211
1. After verifying you have root on your phone, download MultiROM Manager off Google Play: https://play.google.com/store/apps/details?id=com.tassadar.multirommgr&hl=en
2. Install and open MultiROM Manager and install MultiROM, Recovery and the patched kernel.
Here is what the following is...
MultiROM: This boots before the system and gives you the option of what system you want to boot. When you select the system, it then hands it off to boot. This will not overwrite your current ROM, but make a backup to be safe
Recovery: This is a custom TWRP recovery with options to install a secondary system
Kernel: This will patch your kernel with kexec-hardboot patch which is requires to dualboot in general.
2. Installing Android Lollipop
1. After you install and verify that MultiROM is installed on your phone, download the Android 5.0 flashable zip from the downloads section at the bottom
2. Reboot into the recovery and go to Advanced> MultiROM> Add ROM
3. When you get there, set ROM type to Android and select "Dont share" for kernel sharing and then press next
4. select ZIP file and install "N5_L_PREV_LPX13D.zip" you downloaded earlier and flash it.
If you wish to not root L, you can go ahead and reboot your phone into Lollipop (The first boot will take several minutes). If you do want to root, go on to the next step. Your primary ROM won't be touched as your primary ROM and its root status won't be affected when using MultiROM.
3. Rooting Android Lollipop (optional)
Rooting is completely optional and is not required for it to run. You need to install root if you do plan on using root apps or busybox on Android 5.0.
As of the LPX13D build, there have been changes made in the bootloader that will prevent SuperSU or root from working. If you want to root on the LPX13D build, you will need to flash this bootloader: http://www.reddit.com/r/Nexus5/comments/2jkx7a/
1. Download the SuperSU zip in the downloads section and save it to your phone.
2. Boot into recovery and go to Advanced> MultiROM> List ROMs and select the L ROM you installed earlier (unless you renamed the zip file or the system name, it should show"N5_L_PREV_LPX13D")
3. Select flash zip and flash the SuperSU zip you downloaded.
4. Reboot and you should now be rooted.
Updating Android Lollipop
As of right now, there are issues if you try to do a dirty flash from DP1 to DP2 (These are issues with Android L and not MultiROM). These issues include home button not working, quick settings pulldown not working, no lockscreen when there is one and data issues (at least with Sprint). If you are coming from LPV79 and updating to LPV81C or LPX13D, it is recommended to do a clean install to avoid these issues. If you are doing a fresh install, you don't have to worry about this issue
Android Lollipop Bugs
These are issues with Android Lollipop and not MultiROM
-The issues stated above when certain things don't work after a dirty flash
-During the inatial setup, the phone may freeze and require reboot when trying to connect to wifi (seems like a new bug with LPV81C). The phone will say Connecting and show a white box before it freezes
-Some apps will crash or be buggy (this is to be expected though with the transition to ART)
-More bug reports can be found [Here]
-A list of apps that have issues with working with Android L can be found [Here]
Downloads
Android Lollipop flashable zip: http://forum.xda-developers.com/showpost.php?p=56112246&postcount=5498
L Root: http://download.chainfire.eu/578/SuperSU/UPDATE-SuperSU-v2.14.zip
Thanks
Chainfire for CF Autoroot and SuperSU
Tasssadar for MultiROM to make this dualboot possible
davy917 for posting a solution for people having internal storage issues with L
For more information and general use of how MultiROM works, go to its main thread [here]
Also if you do have the issue where your internal storage doesn't mount, follow this solution found [here]
Thanks! First time trying multiROM & working great
In Android L I can't seem to download anything and all the folders in sdcard directory is empty.. Is there something I'm missing?
davy917 said:
In Android L I can't seem to download anything and all the folders in sdcard directory is empty.. Is there something I'm missing?
Click to expand...
Click to collapse
Strange. I didn't have that problem but I will look in to it. I recommend going to advanced> MultiROM> list ROMs and perform a wipe of the cache and dalvik of your L system. I was able to download without problems and the internal storage worked fine. Also, how much space was there on your phone before doing this
Sent from my Nexus 5 using Tapatalk
I can't boot to L. Says I need a kexec-hardboot enabled kernel.
Sent from my Nexus 5
Elisha said:
I can't boot to L. Says I need a kexec-hardboot enabled kernel.
Sent from my Nexus 5
Click to expand...
Click to collapse
Yeah, you need a kernel that has that patch included to be able to use MultiROM. There are a few of them if you look around.
---------- Post added at 01:53 AM ---------- Previous post was at 01:53 AM ----------
davy917 said:
In Android L I can't seem to download anything and all the folders in sdcard directory is empty.. Is there something I'm missing?
Click to expand...
Click to collapse
L does sdcard differently
ThatGuy94 said:
Strange. I didn't have that problem but I will look in to it. I recommend going to advanced> MultiROM> list ROMs and perform a wipe of the cache and dalvik of your L system. I was able to download without problems and the internal storage worked fine. Also, how much space was there on your phone before doing this
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I had about 11gb of space before doing this. I just wiped cache and dalvik but still same issue, no files in sdcard folders and can't seem to download anything
---------- Post added at 12:22 PM ---------- Previous post was at 12:21 PM ----------
Lethargy said:
L does sdcard differently
Click to expand...
Click to collapse
Do you know how I can access the files in my sdcard?
davy917 said:
I had about 11gb of space before doing this. I just wiped cache and dalvik but still same issue, no files in sdcard folders and can't seem to download anything
---------- Post added at 12:22 PM ---------- Previous post was at 12:21 PM ----------
Do you know how I can access the files in my sdcard?
Click to expand...
Click to collapse
You'll have /system/sdcard/0/ and /system/sdcard/
davy917 said:
I had about 11gb of space before doing this. I just wiped cache and dalvik but still same issue, no files in sdcard folders and can't seem to download anything
---------- Post added at 12:22 PM ---------- Previous post was at 12:21 PM ----------
Do you know how I can access the files in my sdcard?
Click to expand...
Click to collapse
Just wondering, what is your baseband version. I'm just thinking if it may be a firmware issue for some reason. Also try ES File Explorer to see if your files show up in it because my files in sdcard appeared with it
Sent from my Nexus 5 using Tapatalk
Lethargy said:
You'll have /system/sdcard/0/ and /system/sdcard/
Click to expand...
Click to collapse
I don't see such directories.. No sdcard folder in system
---------- Post added at 01:50 PM ---------- Previous post was at 01:49 PM ----------
ThatGuy94 said:
Just wondering, what is your baseband version. I'm just thinking if it may be a firmware issue for some reason. Also try ES File Explorer to see if your files show up in it because my files in sdcard appeared with it
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I am using ES Explorer but no luck
My baseband is M8974A-2.0.50.1.13
When I tried to take a screen shot, I got an error saying cannot save screenshot, storage may be in use. Any idea what the deal is?
davy917 said:
I don't see such directories.. No sdcard folder in system
Click to expand...
Click to collapse
In KitKat, try to find /mnt/shell/emulated/0 or /sdcard in L
Sent from my Nexus 5 using Tapatalk
I can find both, but in L the folders in /sdcard are all empty
davy917 said:
I can find both, but in L the folders in /sdcard are all empty
Click to expand...
Click to collapse
Are they empty if you try to open them in KitKat? Also it looks like your baseband is out of date. I have the baseband M8974A-2.0.50.1.16. I recommend updating your baseband to see if it fixes it. Also what is your primary ROM
Sent from my Nexus 5 using Tapatalk
ThatGuy94 said:
Are they empty if you try to open them in KitKat? Also it looks like your baseband is out of date. I have the baseband M8974A-2.0.50.1.16. I recommend updating your baseband to see if it fixes it. Also what is your primary ROM
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It's not empty when I open in KK.. I'm running SlimKat
I'll try updating my baseband and see if it helps. Thanks for all the suggestions!
davy917 said:
It's not empty when I open in KK.. I'm running SlimKat
I'll try updating my baseband and see if it helps. Thanks for all the suggestions!
Click to expand...
Click to collapse
If all else fails, I recommend just trying to reinstall MultiROM and the patched kernel and remove and reinstall L. Also select CM11 when you install the patched kernel since the CM11 kernel should be compatible with slimkat
Sent from my Nexus 5 using Tapatalk
ThatGuy94 said:
If all else fails, I recommend just trying to reinstall MultiROM and the patched kernel and remove and reinstall L. Also select CM11 when you install the patched kernel since the CM11 kernel should be compatible with slimkat
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah I think I'll just try starting over.. Nothing seems to work. I basically don't have any access to storage when on Android L as my secondary. I can't even take photos lol it takes a pic and can't save anywhere
davy917 said:
Yeah I think I'll just try starting over.. Nothing seems to work. I basically don't have any access to storage when on Android L as my secondary. I can't even take photos lol it takes a pic and can't save anywhere
Click to expand...
Click to collapse
There have read people in the Android L thread that have had this same issue. That's why I always thought dual booting with Android L wasn't a good idea.
Got some help from the multirom thread.. Followed the below and it worked fine. Had to reinstall Android L afterwards tho.
1. Install terminal from play store in Android L ROM.
2. In terminal: "su" *enter*
3. In terminal: "restorecon -FR /data/media/0" *enter*
4. Wait.*
5. Reboot.
*If it doesn't boot anymore, delete Android L as ROM, and flash it again trough multirom.
ThatGuy94 said:
If all else fails, I recommend just trying to reinstall MultiROM and the patched kernel and remove and reinstall L. Also select CM11 when you install the patched kernel since the CM11 kernel should be compatible with slimkat
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Slimkat is AOSP/stock kernels.... Not CM11/caf. ?
KJ said:
Slimkat is AOSP/stock kernels.... Not CM11/caf. ?
Click to expand...
Click to collapse
Thanks for the correction. I don't use slimkat so I thought it was using the cm11 kernel.
Sent from my Nexus 5 using Tapatalk
Q&A for [RECOVERY][i9300] TWRP 2.8.0.1 touch recovery [2014-09-12]
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. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
ext sdcard ext4 ?
Hi,
I have a gt-i9300 with official Rom ( Android 4.3 ). Rooted and twrp 2.8.0.1 installed, I buy it for support the team.
I have a ext sdcard 64Gb exFat ( Formatting initialy with the smartphone ).
I can't restore with twrp. It's a problem FS. Can i have a ext4 FS with this Rom ? the card are mount automatically ?
How to format ? with a Linux for example ? or an Apps on playstore ??
Thanks for this Site.
problem with TWRP2 !!
Whenever i boot my device it boots to recovery by default :/
But i can choose to "boot system" from twrp
The Q : how can i change it back to boot system by default ?
I'll be very thankful if someone helped me ^^"
help with backup and restore
Hello, i backup my data from my nexus 5 using twrp recovery backup and restore...when i restored it, music, videos and pdf files were not restored...my download folder also was blank...i backed up data on my otg pendrive...i examined the files on the otg from pc, i find 2 large data files data.ext4.win000 and data.ext.4win001....how do i retrieve data from these 2 files? Help please
strange76 said:
Hi,
How to format ? with a Linux for example ? or an Apps on playstore ??
Thanks for this Site.
Click to expand...
Click to collapse
AParted on the play store will format for you. Backup first!
Not sure about the ROM though... keep googling?
---------- Post added at 02:04 PM ---------- Previous post was at 01:59 PM ----------
Which model is this thread for?
The header is confusing:
Forum Home xda-developers Samsung Galaxy S III I9300, I9305 Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & Troubleshooting [Q&A] [RECOVERY][i9300] TWRP 2.8.0.1 touch recovery [2014-09-12]
Illuvitar said:
AParted on the play store will format for you. Backup first!
Not sure about the ROM though... keep googling?
---------- Post added at 02:04 PM ---------- Previous post was at 01:59 PM ----------
Which model is this thread for?
The header is confusing:
Forum Home xda-developers Samsung Galaxy S III I9300, I9305 Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & Troubleshooting [Q&A] [RECOVERY][i9300] TWRP 2.8.0.1 touch recovery [2014-09-12]
Click to expand...
Click to collapse
Thanks for the reponse.
My solution : Format ext sdcard 64Gb Fat32. I make this with gparted.
Official Rom not suported with ext4.
All works for twrp now.
Now, my Rom is : OmniRom 4.4 i wait for the android 5 ( i hope )
USB OTG Storage
Hello, I currently use Philz recovery on my i9300 and I can mount my USB flash drive through USB OTG, however I cant mount my flash drive in TWRP.
I have tried everything, formating flash drive to fat32, rebooting,using different types of flash drives.
USB OTG works fine,since the mouse works perfectly.
What can I do, because to me it is the most important feature to have in recovery?
Awesome
nice
Twrp 2830 OTG Drive?
Hi I'am new to twpr recovery, I wanted to use a OTG drive to flash roms, but when in recovery there is no option for usb format or mount. My OTG drive is fat32 formatted. The sd card is shown and internal storage but nothing else? can you please help.
plz solve
sorry for bad English
downloading problem downlod after 75% downloading stop why????
TWRP 2.8.3.0 touch recovery
from this site
For Flashable ZIP.
can i ask something?
This flashable zip is working on STOCK RECOVERY of S3 i9300 too?
---------- Post added at 10:57 AM ---------- Previous post was at 10:52 AM ----------
Adeelkamal said:
sorry for bad English
downloading problem downlod after 75% downloading stop why????
TWRP 2.8.3.0 touch recovery
from this site
Click to expand...
Click to collapse
same problem as of mine is 99%
CM12
Does this recovery support CM12? Thank you!
How compatible are backups between cwm and twrp?
Ricky_Karmator said:
Does this recovery support CM12? Thank you!
Click to expand...
Click to collapse
Backup&restore of LP-ROMs are working fine.
_narcolepsy_ said:
How compatible are backups between cwm and twrp?
Click to expand...
Click to collapse
Not. If you want to transfer old CWM-backups to TWRP-format, use Phillz-recovery (restore CWM and backup as TWRP afterwards).
updated from 2.8.5.0 with odin, but has swiped base band details from phone, have been using cm12 rom. how can I get base band back please.
can you tell me how to flash modem have lost data.
Twrp stuck after reset my i9300 (5.1.1. weekly)
Hello! I cannot exit twrp recovery which is stuck, after factory reseting my phone from inside CM12.1.
How can I restore my phone, and exit this twrp loop?
If anybody knows , please help!
Thanks
eurih70 said:
Hello! I cannot exit twrp recovery which is stuck, after factory reseting my phone from inside CM12.1.
How can I restore my phone, and exit this twrp loop?
If anybody knows , please help!
Thanks
Click to expand...
Click to collapse
I'm in the same position. I flashed the Galaxy project ROM using twrp and it keeps booting to TWRP recovery. I tried using the terminal command 'dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota' but it states 'no such directory' Really need help on this one please
TWRP Manager does not work for i9300 (m0).
TWRP Manager did not work when I tried to use it to update TWRP.
I've been told by the developer of TWRP Manager that it does not support the i9300 (M0).
Perhaps then a Zip of the latest version of TWRP should be the preferred way to upgrade from earlier (< v2.8.4.0) versions which cannot self-update using an IMG file?
factory reset on cm12.1 caused twrp bootloop
I am running unofficial cm 12.1 from this thread, together with TWRP 2.8.6.1.
Yesterday I did a factory reset inside cm. Upon reboot, I have a bootloop on twrp. The twrp splash screen pops up, stays on for 2-3 seconds, and the device reboots. This goes on and on.
Unfortunately my device charges fine on usb, but is not reconized on PC. For reference, here is what I see in dmesg output:
Code:
[20871.522790] usb 2-1.1: new full-speed USB device number 93 using ehci-pci
[20871.930703] usb 2-1.1: device not accepting address 93, error -32
[20872.002752] usb 2-1.1: new full-speed USB device number 94 using ehci-pci
[20872.410811] usb 2-1.1: device not accepting address 94, error -32
[20872.410979] usb 2-1-port1: unable to enumerate USB device
So I have not been able to reflash recovery with heimdall.
Does anyone have a suggestion on breaking this bootloop? Is there any way of loading an update or recovery on external sdcard?
Pedro
Q&A for [RECOVERY][golden] TWRP 2.8.1.0
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 [RECOVERY][golden] TWRP 2.8.1.0. 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!
nice
Hi,
Is that version 2.8.3.0 is planned ?
Thanks
There's a version 2.8.3.0 on the Team Win website for S3 Mini, is there a reason to use this one over that?
Micrologos said:
There's a version 2.8.3.0 on the Team Win website for S3 Mini, is there a reason to use this one over that?
Click to expand...
Click to collapse
Sure
What's new in 2.8.3.0:
MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
MTP will now tell the host PC that storage is removed instead of disabling MTP completely
MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
Update and improve fix permissions and make fixing contexts optional
Update SuperSU in TWRP to 2.40 and update install process
Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
Fix kernel panic during MTP start on some devices
Support unicode fonts on devices with True Type Font support
Fix slider value not showing sometimes (vibration settings page)
Toggle MTP off during adb sideload to set correct USB IDs
Reduce library requirements for 5.0 L decrypt
Other minor fixes and improvements
What's new in 2.8.2.0:
MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
Pull in all changes from Android 5.0 lollipop into TWRP
Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
Revert some changes to exFAT that were breaking exFAT support on some devices
Other minor fixes and updates
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
GT-I8190L
Is it compatible with I-8190L?
TWRP 2.8.1.0(Android-Andi) S3 MINI i8190N
I need someone to help me on this.
Updated my TWRP recovery to 2.8.1.0(thanks to Android-Andi) and used it for a while.
Recently i just wondering in recovery mode, under the install option, i cant find any zip
file that have been located in sdcard(accessible -rw). The file is there when i find it using
file explorer, only in recovery mode it isnt there. This never happen when using TWRP 2.7.
Anyone having this problem?
Naimlaaa said:
I need someone to help me on this.
Updated my TWRP recovery to 2.8.1.0(thanks to Android-Andi) and used it for a while.
Recently i just wondering in recovery mode, under the install option, i cant find any zip
file that have been located in sdcard(accessible -rw). The file is there when i find it using
file explorer, only in recovery mode it isnt there. This never happen when using TWRP 2.7.
Anyone having this problem?
Click to expand...
Click to collapse
nevermind me.. Just found it in /data/media
Problem solved
Stuck after flashing recovery
Guys, I am hoping for a little help here. I followed the instructions as detailed, flashed TWRP in Odin, all seemed ok. But whenever I try to boot into recovery, the phone just hangs at "Recovery booting..." (the blue text with the Samsung Galaxy SIII Mini splash screen.) It still boots into the rom ok (still stock, but with super user). I'm stumped. Any ideas?
The phone is a SM-G730W8 (Golden). Thanks so much!
this recovery is only for gt-i1890/l/n
try to flash the last stock rom for your phone and hope that the phone isn't bricked
Gesendet von meinem GT-I8190
Removed - I am completely off-topic for this thread.
supporting S3 Mini 8190(L)??
Flake7100 said:
supporting S3 Mini 8190(L)??
Click to expand...
Click to collapse
Yes it do.
Sent from here to there
Hello.
I registered here just to post a problem where i could not find a solution. With android-andi's recovery (2.8.7.0) it boots in recovery but shows only a black screen. It seems to work because of phone vibrates when touching to screen.
Recovery might boot as visible if you try to boot recovery enough many times. Another funny thing is if you boot it as black screen, put it charger and force boot with power button then it boots straight to recovery and it is visible.
I tried also older andi's recoveries and they booted also as black screen but charger trick not worked with enough old recovery. I havent had any issues with maclaws recoveries and those are worked fine and thats why I am using maclaws recovery atm (the newest version from maclaws site).
Seems to that i can't report this in developers thread because of I am new in xda forums.
One thing, how i can send/attach files in forum? I have recovery log but not managed to send it...
Sorry my english and try to understand .
Anyone else have black screen issues with andis's recoveries? And what is system here to upload logs as txt files here forum becouse can't find option ti upload nothing else than pictures.
NTFS and USB Mass Storage support
Why TWRP didn't recognize NTFS?
In TWRP it shows that the Micro SD is non existent (0MB).
I use this file system because is very fast and stable.
Also,it will be awesome if you add Mass Storage support (it's much more fast than MTP).
Hello All,
Warning: Do not flash these files unless you are on .3.2.4 or Nexus ROM 2.0.x.
Here are rollback images (prerooted) which will enable you to get back to .3.1.0
Instructions:
1. Backup your /data partition in Safestrap if desired and copy it to your computer
2. Flash the appropriate file for you device
3. From Safestrap do a factory reset
4. Reboot to 13.3.2.4 modified stock (the screen will go blank for about 15-20 seconds - no problem)
5. Do not connect to WiFi or register your kindle
6. Select Complete Setup Later
7. Copy the .3.1.0 stock update file to the root of your sdcard
8. Initiate update from device options.
Links
- Apollo Rollback Image
- Thor Rollback Image
Reserved
Thanks @ggow !
Thanks for this man.
What are the benefits to go back to 3.1.0 as 3.2.4 is fully rootable and necessary for Nexus 2.0?
I'm still using 3.1/Nexus 1.4 and planned to update the device to 3.2.4/Nexus2.0. But now I'm wondering if I just should keep the current installation.
Unlocked bootloader!
what steps do i take if i m using nexus 2.02 on stock slot?
i have the original stock image 3.2.4 backed up in TWRP if it helps
Warning
Thanks ggow, but this is a warning to all apollo (HDX 8.9) users - do not use file (with md5 hash: 0f9f3b084500b888fc66415a8539a341) to rollback attempt! If you downloaded file Apollo Rollback Image before and want to use it later, please redownload, @ggow just posted corrected file (with md5 hash: 119b5004e96a41eb073c8b324712fe23)
jeryll said:
Thanks ggow, but this is a warning to all apollo (HDX 8.9) users - do not use this file to rollback attempt!
@ggow you forgot to edit build.prop file, so after anyone boot from this file (md5 hash: 0f9f3b084500b888fc66415a8539a341), kindle will not continue with downgrade to 14.3.1.0 :crying:
No harm done for me, as I backuped everything I can, but beware, if you dont want problems (I found extremely difficult install anything through adb on this installed/running rollback ... you can try edit build.prop file to correct values for downgrade by yourself, but messing with build.prop is highly risky and small mistake and brick is for sure, so you have been warned) WAIT for ggow to upload correct rollback image, or correct edited build.prop for downgrade
Click to expand...
Click to collapse
I have taken the file offline, Sorry about that @jeryll, will correct file and re-upload.
The corrected Apollo rollback image is uploading now. I'll post the new link in the morning.
Sent from my Kindle Fire HDX using Tapatalk
nymica said:
Unlocked bootloader!
Click to expand...
Click to collapse
So the benefit is to install "TWRP Recovery" to be able to install any Custom Rom without Safestrap?
ands2 said:
So the benefit is to install "TWRP Recovery" to be able to install any Custom Rom without Safestrap?
Click to expand...
Click to collapse
Yes full TWRP recovery and yes we can effectively install any ROM we want.
Credit goes to @vortox for making it possible with his signature bypass tool.
Corrected Apollo Image
@jeryll,
The corrected Apollo Rollback Image is up.
Thanks
ggow said:
@jeryll,
The corrected Apollo Rollback Image is up.
Click to expand...
Click to collapse
Thank you sir, successfully rolled back to 14.3.1.0, installed TWRP 2.8.1.0 and now I will play a little with TWRP
ggow said:
Hello All,
1. Backup your /data partition in Safestrap if desired and copy it to your computer
2. Flash the appropriate file for you device
3. From Safestrap do a factory reset
4. Reboot to 13.3.2.4 modified stock (the screen will go blank for about 15-20 seconds - no problem)
5. Do not connect to WiFi or register your kindle
6. Select Complete Setup Later
7. Copy the .3.1.0 stock update file to the root of your sdcard
8. Initiate update from device options.
Click to expand...
Click to collapse
i followed the steps but not sure where it went wrong for me
step 2. that would be the 13.3.2.4_rollback for thor correct? (i have 7 inch fire hdx)
was not sure where to flash this - i used rom slot 2
that installs 13.3.0.9_user into rom slot2 (i dont understand why we still have to update to 13.3.1.0 i guess
13.3.0.9 is not vulnerable?)
following the rest of the steps and rebooting kindle fire system recovery comes up
would be nice to put a link to 13.3.1.0 stock into the OP i found it in the forum)
i did reboot kindle (didnt dare to do reset to factory defaults)
that gets me back to 13.3.0.9
retrying the steps and after reboot rebooting into safestrap i see
openrecovery script installing zip (13.3.1.0)
if i let this continue and reboot i get a flashing screen and then a black screen
what am i doing wrong
p.s. luckily i have safestrap so rom slot 1 and stock still work
2. Flash the appropriate file for you device
Does it mean: Flash the appropriate (rollback) file for you device (in safestrap) (to Stock ROM slot)?
ggow said:
Hello All,
Warning: Do not flash these files unless you are on .3.2.4 or Nexus ROM 2.0.x.
Here are rollback images (prerooted) which will enable you to get back to .3.1.0
Instructions:
1. Backup your /data partition in Safestrap if desired and copy it to your computer
2. Flash the appropriate file for you device
3. From Safestrap do a factory reset
4. Reboot to 13.3.2.4 modified stock (the screen will go blank for about 15-20 seconds - no problem)
5. Do not connect to WiFi or register your kindle
6. Select Complete Setup Later
7. Copy the .3.1.0 stock update file to the root of your sdcard
8. Initiate update from device options.
Links
- Apollo Rollback Image
- Thor Rollback Image
Click to expand...
Click to collapse
@shadowcliffs - yes flash the rollback image to the stock slot...
Guess the file has to be flashed to Stock ROM instead of any other rom slot.
andPS2 said:
i followed the steps but not sure where it went wrong for me
step 2. that would be the 13.3.2.4_rollback for thor correct? (i have 7 inch fire hdx)
was not sure where to flash this - i used rom slot 2
that installs 13.3.0.9_user into rom slot2 (i dont understand why we still have to update to 13.3.1.0 i guess
13.3.0.9 is not vulnerable?)
following the rest of the steps and rebooting kindle fire system recovery comes up
would be nice to put a link to 13.3.1.0 stock into the OP i found it in the forum)
i did reboot kindle (didnt dare to do reset to factory defaults)
that gets me back to 13.3.0.9
retrying the steps and after reboot rebooting into safestrap i see
openrecovery script installing zip (13.3.1.0)
if i let this continue and reboot i get a flashing screen and then a black screen
what am i doing wrong
p.s. luckily i have safestrap so rom slot 1 and stock still work
Click to expand...
Click to collapse
shadowcliffs said:
Guess the file has to be flashed to Stock ROM instead of any other rom slot.
Click to expand...
Click to collapse
Correct
Hi,
Thanks of all your efforts on this. Is it possible to flash the roll back image any other way than installing and using safestrap ?
We all know flashing ROMs got a lot more complicated with the advent of A/B partitions.
This is not my work, the aim here is only to highlight a process which simplifies the task.
Original post on the OnePlus 6 forum can be found here:
https://forum.xda-developers.com/oneplus-6/how-to/script-copy-oxygenos-base-partitions-to-t4097979
It makes use of a script which copies the flashed firmware to both slots without having to reboot recovery and do it a second time. Also by not having to reboot recovery you avoid the issue where internal storage becomes unreadable.
Credit for this goes to:
LineageOS @erfanoabdi @filipepferraz @Prakyy @drpradsms
Download by prakky (hit the thanks button on his post below):
https://androidfilehost.com/?fid=8889791610682890605
The following posts detail it's usage which you follow at your own risk.
Clean Flashing a new ROM
Disable lockscreen security
Boot TWRP 3.4+
1) Flash latest OOS
2) Flash ROM
3) Flash TWRP installer
4) Flash Finalize.zip
5) Format data; type 'yes' (backup as this wipes phone)
6) Boot System
Reboot recovery to flash additional zips.
Updating OOS base whilst on a custom ROM
Boot TWRP 3.4+
1) Flash latest OOS
2) Flash ROM
3) Flash TWRP installer
4) Flash Finalize.zip
5) Boot System
Reboot recovery to flash additional zips.
Updating a custom ROM (nothing fancy here)
Boot TWRP 3.4+
1) Flash ROM
2) Flash TWRP installer
3) Boot System
Reboot recovery to flash additional zips.
Reverting to OOS
WARNING I've yet to test this!
Boot TWRP 3.4+
1) Flash latest OOS
2) Flash Finalize.zip
3) Format data; type 'yes' (backup as this wipes phone)
4) Boot System
Note: this will revert you to stock recovery as well.
Tip:
Chain install the zips by selecting 'Add more Zips' after selecting the first zip.
Only 'Swipe to confirm Flash' once all zips have been queued.
I recommend numbering the zips in the order they need flashed.
Note: this issue is now resolved as of 09/08/20 as per https://forum.xda-developers.com/oneplus-6t/how-to/guide-rom-flashing-easy-t4143701/post83241857
As a side note and given that I show an OmniROM zip in the previous screenshots here's a fix required for flashing OmniROM.
I use Mixplorer to do the following.
1) Open the OmniROM weekly zip
2) Navigate to folder shown
3) Open metadata
4) Edit oneplus6t to OnePlus6T
5) Save metadata
OmniROM will now flash successfully in TWRP.
Nice post! Don't mean to be rude but is kinda redundant as my thread already existed: https://forum.xda-developers.com/oneplus-6/how-to/script-copy-oxygenos-base-partitions-to-t4097979
Prakyy said:
Nice post! Don't mean to be rude but is kinda redundant as my thread already existed: https://forum.xda-developers.com/oneplus-6/how-to/script-copy-oxygenos-base-partitions-to-t4097979
Click to expand...
Click to collapse
Didn't know your post existed. Only learnt about the method on Pixen OS thread which uses it and gives you credit as did I. A lot of people only look in their own phone forum. If you don't mind I'll leave this thread open. However if you aren't happy I'll ask a mod to close it.
Deleted. Think maybe I'm getting altimeters. ?
Prakyy said:
Nice post! Don't mean to be rude but is kinda redundant as my thread already existed: https://forum.xda-developers.com/oneplus-6/how-to/script-copy-oxygenos-base-partitions-to-t4097979
Click to expand...
Click to collapse
Edited first post to make it clearer this is your work.
mitchst2 said:
Didn't know your post existed. Only learnt about the method on Pixen OS thread which uses it and gives you credit as did I. A lot of people only look in their own phone forum. If you don't mind I'll leave this thread open. However if you aren't happy I'll ask a mod to close it.
Click to expand...
Click to collapse
You can keep it open ofc I don't mind.
However, yes, many people only see in their device's forums but since this script will work w/ any A/B device, is there a forum I could post in so that all device owners can see it??
Prakyy said:
You can keep it open ofc I don't mind.
However, yes, many people only see in their device's forums but since this script will work w/ any A/B device, is there a forum I could post in so that all device owners can see it??
Click to expand...
Click to collapse
Good question.
Is 'Android Development and Hacking / General' the right place? There are some all device guides with a lot of views in there.
https://forum.xda-developers.com/android/general
mitchst2 said:
As a side note and given that I show an OmniROM zip in the previous screenshots here's a fix required for flashing OmniROM.
I use Mixplorer to do the following.
1) Open the OmniROM weekly zip
2) Navigate to folder shown
3) Open metadata
4) Edit oneplus6t to OnePlus6T
5) Save metadata
OmniROM will now flash successfully in TWRP.
Click to expand...
Click to collapse
As of 09/08/20 build and this commit all is well with OMNI and TWRP again. No need to edit the ROM zip anymore.
Is there a proper way to switch from one custom rom to another without formatting the data? Encryption and A/B made the custom rom game so crazy and time taking now. Or maybe I lost track of things. I could always take a backup of storage on laptop but the backups are very huge, mostly 80gb+ and takes forever while backing up whatsapp databases with images thumbnails and all.
brajesh.sharma87 said:
Is there a proper way to switch from one custom rom to another without formatting the data? Encryption and A/B made the custom rom game so crazy and time taking now. Or maybe I lost track of things. I could always take a backup of storage on laptop but the backups are very huge, mostly 80gb+ and takes forever while backing up whatsapp databases with images thumbnails and all.
Click to expand...
Click to collapse
No when switching ROM formatting data will be necessary. Not used it myself but others recommend Migrate to restore apps and data.
I was looking for a way to backup current rom using twrp, test a rom and then be back on the original rom with a twrp restore. If anyone finds a way to do this without format data, pls let me know.
brajesh.sharma87 said:
I was looking for a way to backup current rom using twrp, test a rom and then be back on the original rom with a twrp restore. If anyone finds a way to do this without format data, pls let me know.
Click to expand...
Click to collapse
I just restored PiXeN from AOSPA on 6t device and had no issues and I did NOT format my data or do anything but let TWRP do it's restore then rebooted system.. Just backup your system, data and boot partitions and restore them then reboot system. I didn't encrypt my backup using a pw in recovery. I also use magisk canary latest and the themed TWRP recovery 3.4.0-v1 from EvoX rom that acuicultor compiles and morphine1 themes. I've not restored yet using any other TWRP so not sure what works and what doesn't as far as that goes but the themed recovery works for me.
**Formatting data is unavoidable when installing an AOSP custom rom coming from stock OOS rom.
Edit
flash713 said:
I just restored PiXeN from AOSPA on 6t device and had no issues and I did NOT format my data or do anything but let TWRP do it's restore then rebooted system.. Just backup your system, data and boot partitions and restore them then reboot system. I didn't encrypt my backup using a pw in recovery. I also use magisk canary latest and the themed TWRP recovery 3.4.0-v1 from EvoX rom that acuicultor compiles and morphine1 themes. I've not restored yet using any other TWRP so not sure what works and what doesn't as far as that goes but the themed recovery works for me.
**Formatting data is unavoidable when installing an AOSP custom rom coming from stock OOS rom.
Edit
Click to expand...
Click to collapse
I had to mandatory format data when I wanted to move from evolution x to aospa.
brajesh.sharma87 said:
I had to mandatory format data when I wanted to move from evolution x to aospa.
Click to expand...
Click to collapse
And I've also had to format data before as well but not lately. Could it be because I format both slots coming from OOS or because I use Canary Magisk or the recovery I use.. No idea but next time you are on EvoX backup system, data and boot and try and restore it using that recovery that comes with EvoX and see what happens. These last few weeks I've stayed on AOSiP and PixeN and I flashed Omni once I think but restoring from AOSPA to Pixen was flawless for me and also restoring Pixen to Pixen was also fine, which I do because I always mess around with sound mods.... I'm on AOSiP now and soon as I get more charge on my phone I'm going to try and restore to something I have a backup already made on one of my USB drives and I'll edit this post and report what the outcome is...