Database Info

From 4.4.4 to patched 5.1.1

The stagefright threat, etc. is forcing me to finally move to 5.1.1. Because one misstep could mess things up, I'm looking for "reassurance" that below is the correct procedure. (I've only upgraded android versions once before and am nervous ....)
Starting point:
- Rooted nexus 5, kitkat 4.4.4,
- Xposed framework installed
- twrp 2.8.6.0 recovery installed
- adb and fastboot on Windows pc
Need to: (please correct if wrong steps)
1. Make nandroid and Titanium backups
2. Download 5.1.1 (LMY48I) from
https://developers.google.com/android/nexus/images#hammerhead
3. Uninstall xposed framework?
4. Flash downloaded 5.1.1 (LMY48I) from within twrp recovery
Questions:
A. Is 5.1.1 (LMY48I) the correct stagefright patched image for nexus 5?
I'm a T-Mobile subscriber but bought my nexus 5 from Google not T-Mobile. So is this the correct image or the T-Mobile specific 5.1.1 one?
I'm currently KTU84P
B. Will I lose root?
C. Will I lose data?
Please let me know if I have it wrong.
Thank you!

Going from Android 4.x to 5.x you'll need to end up wiping your device. Make a nandroid and store it off your device. Also make sure you have Google backing up your device, it'll make things easier.
Download the latest factory image, Google nexus factory image. Extract the .tgz file using 7-zip or winrar. In there is another zip file extract it too. Then follow method 2, long method, of this, http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
You'll need to re-root and you will lose data.
Sent from my Nexus 9 using XDA Free mobile app

Darn!
Thanks for replying. I really don't want to reroot and lose data. Is there no other way?
I don't sync with Google or the cloud, so that's not an option for me.
Isn't there a way to do it via adb or fastboot?

I thought it was unlocking the bootloader that wiped the system. But my bootloader is already unlocked.

Anderson2 said:
I thought it was unlocking the bootloader that wiped the system. But my bootloader is already unlocked.
Click to expand...
Click to collapse
The issue is you will have to flash userdata.img or you'll boot loop and not get your device to boot. Flashing userdata.img will wipe your device.
Sent from my Nexus 9 using XDA Free mobile app

Maybe I'll gear up my courage and do it. Thanks for the advice. Wish you lived next door!

If you have a nandroid you can simply restore data after the upgrade. That is after you reflash twrp (or not if you fastboot partitions one by one skipping recovery) and push your nandroid back to the device. Gives you back all of your calls, sms's, contacts, apks (except system, but the old data will come back), etc. If you have kept your apks up to date, even when on 4.4.4 they should work fine on lollipop.
I just did this on Slim. Was on SlimKat for ages, used multirom and flashed latest SlimLP build by Robbie. I swapped the new one LP to primary in modified twrp. I updated kernel to elementalx, restored data from previous nandroid, fixed up xposed for a few tweaks I use (don't do too much with a custom rom (I use greenify, bootmanager, and secure settings). I ran the new primary for a few days, the LP one with all the restored stuff. A few things needed to update through play (pain in the butt as I live in China and have to do it through a VPN). Everything was working fine, so I did one more nandroid, then deleted kitkat. I don't think this would be suggested in most guides, but it worked. If it hadn't, well, go back to my nandroid. If there are things you are really scared of losing you could go farther, export all contacts, use sms/call log backups, then titanium for all apks and data. Titanium also has an option for a selective recovery from a nandroid of the data partition. This means you can flash a new lp rom, install titanium, then restore in bulk from a nandroid. No need to back them all up individually.
Remember, once you start you have the nandroid to fall back on anyway. Nothing should be able to go wrong. If it all gets messy just get into bootloader and fastboot boot recovery (twrp image) and restore your device to where you started. Softbrick is nothing when you have a nandroid and recovery.

Thank you so much. That is very helpful to learn.
wangdaning said:
If you have a nandroid you can simply restore data after the upgrade. That is after you reflash twrp (or not if you fastboot partitions one by one skipping recovery) and push your nandroid back to the device.
Click to expand...
Click to collapse
That's what I've never done. Can I just restore "data" from a nandroid after updating to lp? (after refreshing twrp and putting my nandroid back; fastbooting partition by partition is beyond my current abilities)
wangdaning said:
Titanium also has an option for a selective recovery from a nandroid of the data partition.
Click to expand...
Click to collapse
That I will explore. Sounds like the easiest and fastest option if it works.

If you want to keep your recovery (save you from having to reinstall it):
1) open the factory image you have downloaded
2) open the image-hammerhead-(whatever version).zip
3) delete recovery.img
4) run the flash-all file
I can confirm that you can selectively restore from a nandroid in titanium backup. I opened it on my phone to check before I said you could.

OK. I decided to put aside bad memories of the pc not recognizing the phone and the like and decided to go ahead.
Did a lot of reading, took notes, did my backups (nandroid and tibu), moved them to the pc, downloaded the necessary files and moved them to where I had adb and fastboot installed and with trepidation went ahead.
First command from the adb folder
"Fastboot devices"
found the nexus 5 and gave the correct response!
So, I said "I was worried about nothing. This is going to be a breeze"!
Next command, as administrator, from the subfolder in the adb folder, with N5 attached, was the unmodified
flash-all.bat
Response:" waiting for device"
I tried again with phone in recovery: Response:" waiting for device"
I tried again with phone in bootloader mode and got:
........
error: cannot load 'bootloader-hammerhead-hhz12h.img'
rebooting into bootloader...
OKAY [ 0.065s]
finished. total time: 0.066s
error: cannot load 'radio-hammerhead-m8974a-2.0.50.2.26.img'
rebooting into bootloader...
OKAY [ 0.071s]
finished. total time: 0.072s
error: failed to load 'image-hammerhead-lmy48i.zip': No such file or*
directory
Press any key to exit...
........
What should I do? Everything is unzipped. Windows 8.1
Thank you.
*
*

Here is the folder contents from which I ran flash-all.
So the files are there.

Anderson2 said:
Here is the folder contents from which I ran flash-all.
So the files are there.
Click to expand...
Click to collapse
Try method 2 from here:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
As mentioned before you can skip the fastboot flash recovery thing, or at the end "fastboot flash recovery (twrp image)" to install custom.
Also, it is not as complicated as it seems. When you enter the command "fastboot flash bootloader" for example, you can just drag the bootloader file into the command prompt instead of typing everything out.

Did you follow the instructions from here?
https://developers.google.com/android/nexus/images?hl=en
Sent from my Nexus 5 using Tapatalk

OK, Now I am in trouble!
I followed the instructions in method 2 of http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Everything went smoothly and I finished. When the instructions at the end said to go into recovery, I found myself in the TWRP recovery. But I am now in a boot loop. I can't boot into system. It keeps returning to the TWRP recovery.
Really need help. My PC does not see where in the Nexus 7 I can recopy the nandroid I made back to the phone so I can restore kitkat.
HELP!

Put the phone back into fastboot mode and reflash the factory images. Do you need a custom recovery? If not don't install twrp for now. Just want to get up and running first.
Sent from my Nexus 5 using Tapatalk

Am now in twrp's file manager and after rebooting my pc am transfering my nandroid back to the phone. So I feel better....
But I would like to try to boot into 5.1.1 before restoring.

ldubs said:
Put the phone back into fastboot mode and reflash the factory images. Do you need a custom recovery? If not don't install twrp for now. Just want to get up and running first.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I tried restoring my nandroid kitkat backup so I can get some work done. But that failed when restoring data with "e:extractTarFork( ) process ended with ERROR=255
Will try to restore kitkat without the data restore.

that didn't work either. It's rebooting but the little balls just keep turning..

Anderson2 said:
OK, Now I am in trouble!
I followed the instructions in method 2 of http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Everything went smoothly and I finished. When the instructions at the end said to go into recovery, I found myself in the TWRP recovery. But I am now in a boot loop. I can't boot into system. It keeps returning to the TWRP recovery.
Really need help. My PC does not see where in the Nexus 7 I can recopy the nandroid I made back to the phone so I can restore kitkat.
HELP!
Click to expand...
Click to collapse
I out the phone back into fastboot and followed all the instructions of method 2 up to
Type the following commands, in this order (If you have a different folder, change the path)
Code:
fastboot flash bootloader C:\image-hammerhead-krt16m\bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:\image-hammerhead-krt16m\radio.img
fastboot reboot-bootloader
fastboot flash system C:\image-hammerhead-krt16m\system.img
fastboot flash userdata C:\image-hammerhead-krt16m\userdata.img
(Note: this command will wipe your device (including \sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:\image-hammerhead-krt16m\boot.img
fastboot flash recovery C:\image-hammerhead-krt16m\recovery.img
fastboot erase cache
fastboot flash cache C:\androidimage\cache.img
★After everything finished, select "Recovery" using the volume buttons.
★When a small Android appears, press Power Button + Volume UP
.................................................
At this point again TWRP appeared instead of the android recovery.
Just like the first time.

The problem might be at the end of the method 2 sequence. When finished with method 2 flashing I get 2 screens:
1. a screen from twrp saying it noticed an unmodified partition and asking whether I should keep it read only or modified. I tried both with the same result, boot loop into TWRP
2. a second screen offering to install supersu. I refused. same result boot loop.
maybe they are the problems? Twrp remains in place.

How to Downgrade bootloader 41.1A to 41.18 or 41.19

please..
i have problem with bootloader version 41.1A
i want to Downgrade to version 41.18 or 41.19
anyone know ..??
please share it
thank you

Up
Me too
My bootloader v 41.1A I downgrade 41.18 Help

Why do you need to downgrade? Messing with Bootloaders can destroy your phone.

even i want to downgrade... I cant flash custom recovery on 41.1A

poran123 said:
even i want to downgrade... I cant flash custom recovery on 41.1A
Click to expand...
Click to collapse
Bootloader cannot be downgraded. You're stuck on w/e version you have currently installed.

Okay so I'm stuck on 41.1A and my phone will continue to restart itself and then stuck in bootloop till the battery dies... and then when I connect it to the charger boot's up normally...

@lost101
Can you please let me know how to check bootloader version?
I am using Moto G XT1033 model(Asia).
It was updated to Lollipop 5.0.2 by Motorola Stock Lollipop update.
Later on I had unlocked bootloader and downgraded it to Kitkat 4.4.4 using this thread.
I don't have any clue about current version of bootloader in my Moto G.
I want to try Lollipop 5.1 Optimized stock rom link here, so just wanted to ensure compatibility of bootloader so that my phone works after flashing it.

kalpesh.fulpagare said:
@lost101
Can you please let me know how to check bootloader version?
Click to expand...
Click to collapse
Enter bootloader (hold volume-down while turning it on), read text on screen (second line).

I too want to know if there is a way to downgrade or at least reflash my damaged bootloader which is causing weird behaviour.
Sent from my Nexus 6P using Tapatalk

I have the exact same problem.
Stuck on 41.1A
Was on a slim6 rom before. Tried to return to STOCK_ASIA_RETAIL. All fastboot commands successfully executed but no apparent change. I have the exact same wallpaper, the same layers RRO navbars, everything. I would not need to go to STOCK but since the slim installation is unstable and everything force closes, the phone is unusable.
Additional note: Somehow even TWRP is stuck in the splash screen, so cant flash any other ROM. Even tried to access TWRP using adb, but the TWRP service fails to start.
I fastboot flashed phillz recovery, stock recovery & newer TWRP versions, but nothing happens. Phone still stuck in TWRP screen.
To my surprise I was able to pull my personal files from the internal SD using ADB (which still works btw).
But I'm left with a phone in a zombie unusable condition, it just doesn't react to anything.
Any help from the XDA community would be greatly appreciated. I am still keeping my fingers crossed, so that one day a guide comes up to brick my device (STOCK 5.1 bootloader) and unbrick it using some sort of unbrick tool.

Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too

SLATE21&MOTOG said:
Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too
Click to expand...
Click to collapse
Creating such a zip is possible, but flashing it may either not work or hard brick your phone.

How to install working recovery on 41.1A bootloader
I had the situation on my Moto G XT1039 where I had formatted the partitions on my phone (using my old CWM recovery), then flashed the 41.1A bootloader, but 41.1A would not allow me to flash any recovery.
So I had a working bootloader, but no recovery and no OS. And apparently no way to install a recovery, to install an OS...
I got the phone back like this:
- Flashed 4.4.4 stock manually using the bootloader (if you do this, DO NOT flash the 4.4.4 motoboot.img, according to everything on here that will permanently brick your phone; I am not sure about partition gpt.bin - I flashed this, but I was already on the 4.4.4 partition layout anyway). Do flash boot.img, that is the OS boot.
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
From there I now had the correct recovery in place to flash the 5.1 Optimized distro (which I would definitely recommend - clean, stable, excellent battery life!).
Yay!

Bmju said:
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
Click to expand...
Click to collapse
Why didn't you simply fastboot flash a TWRP image?

_that said:
Why didn't you simply fastboot flash a TWRP image?
Click to expand...
Click to collapse
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.

Bmju said:
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.
Click to expand...
Click to collapse
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.

_that said:
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.
Click to expand...
Click to collapse
Thanks! I definitely tried that first! Maybe this bit I didn't make clear in my post, but actually:
- fastboot boot was only working for me with older recovery ROMS, i.e. the older CWM recovery which I mentioned, which I had lying around from when I first rooted my phone on 4.4.4, and also - not that it's much use - with the recovery in the 4.4.4 image, which just brings up the dead Android logo
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.

Bmju said:
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
Click to expand...
Click to collapse
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Bmju said:
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
Click to expand...
Click to collapse
That doesn't make any sense. Not that I don't believe you, I just can't explain how fastboot could fail writing recovery but succeed in writing a different partition.
Bmju said:
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.
Click to expand...
Click to collapse
Thanks for sharing your experience though, maybe it will help someone who has the same weird issue.

_that said:
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Click to expand...
Click to collapse
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)

Bmju said:
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)
Click to expand...
Click to collapse
Yes, I've got that one too, but my flashed recovery then worked fine. However I upgraded my bootloader by installing the complete 5.1 stock ROM, maybe your bootloader update was somehow incomplete.

I'm stuck on the nvidia boot screen.

hey guys! I've been lurking for a while now, but I think I may have broken something, but was wondering what to do now.
I unlocked the bootloader in fastboot, installed TWRP, factory reset, and then flashed cyanogenmod nightly via twrp.
.... and it just stayed on the NVidia logo for over an hour when I tried to boot.
so at this point I wanted to make sure I didn't break something, so I wiped every partition via twrp (except recovery) and then used fastboot to reinstall the stock image..... and nothing. I can't get the tablet to boot anything.
... what do I do next? I can reliably get into TWRP and fastboot.

Did you wipe system before flashing?

Natebluehooves said:
... what do I do next? I can reliably get into TWRP and fastboot.
Click to expand...
Click to collapse
If you still have twrp - you didn't flash stock.
Downloads and instructions:
https://developer.nvidia.com/shield-open-source
Download, unpack, install adb & drivers, copy imgs and blob to /program files/minmalAdb...
Open flash all.bat(as txt) and retype commands from keyboard.
"fastboot devices
fastboot flash recovery recovery.img"...etc.

dzidexx said:
If you still have twrp - you didn't flash stock.
Downloads and instructions:
https://developer.nvidia.com/shield-open-source
Download, unpack, install adb & drivers, copy imgs and blob to /program files/minmalAdb...
Open flash all.bat(as txt) and retype commands from keyboard.
"fastboot devices
fastboot flash recovery recovery.img"...etc.
Click to expand...
Click to collapse
I re flashed twrp after it failed to boot. think of it like a safety blanket. I did actually flash over recovery/system/staging/etc, but it wouldn't boot. it just sits there.
it's worth mentioning this is the k1 tablet. not sure what that changes.

With twrp you can restore only backup.
Stock - fastboot & pc.

dzidexx said:
With twrp you can restore only backup.
Stock - fastboot & pc.
Click to expand...
Click to collapse
okay perhaps I was not clear....
IN THIS ORDER:
I was on stock update 4.4 on the K1 shield tablet
I decided I wanted to run cyanogenmod, so I unlocked the bootloader (fastboot oem unlock), and then flashed CWM (fastboot flash recovery "insert file name for cwm here".img
I couldn't boot into recovery for some reason. it just hangs on the nvidia screen forever when I choose recovery from fastboot
I now install TWRP (fastboot flash recovery etc etc), this works, and I use twrp to install cyanogenmod. won't boot.
I try a few other roms like AICP, still won't boot. just gets stuck forever.
At this point, I figure i'm doing something wrong and i need my tablet to work for this coming week (i use it at work), so I "fastboot flash system/staging/recovery/etc" from the nvidia package. THIS DOES NOT WORK. AT THIS POINT I NO LONGER HAVE TWRP, AND CAN NOT BOOT.
I can install TWRP to get that functionality back, but at this point I can't get the tablet to boot into anything but bootloader or TWRP if i install it. anything else leaves me stuck on the nvidia logo forever.
this is a brand new nvidia tablet K1 as of about a week ago. no issues until i unlocked the bootloader.
Also, I really need to know, and nobody anywhere is answering this for some reason: are roms for the original shield compatible with the K1? As i understand it, the k1 is nearly identical in hardware (missing the stylus sensor, but not much else), but I seem to be the only person having these problems.

edisso10018 said:
Did you wipe system before flashing?
Click to expand...
Click to collapse
yes. am i not supposed to do this? is a dirty flash recommended for some reason?

Natebluehooves said:
yes. am i not supposed to do this? is a dirty flash recommended for some reason?
Click to expand...
Click to collapse
Nvidia shield k1 tablet had 1.4 & 1.5 updates(november).
You flashed wrong firmware.
You have to download and flash 1.4 firmware(recovery image) from:
https://developer.nvidia.com/gameworksdownload#?search=SHIELD%20Tablet%20K1&tx=$additional,shield

dzidexx said:
Nvidia shield k1 tablet had 1.4 & 1.5 updates(november).
You flashed wrong firmware.
You have to download and flash 1.4 firmware(recovery image) from:
https://developer.nvidia.com/gameworksdownload#?search=SHIELD%20Tablet%20K1&tx=$additional,shield
Click to expand...
Click to collapse
ok. grabbed it, flashed everything including recovery, aaand.... it's just frozen on the bootloader screen saying cold booting Linux. it's been here for a while. same issue as previously.
edit: looked at the old file I was flashing, it was 1.3.
my previous tablet I worked with was an original shield, so that's why I had the 4.4 update in my head.

I think that you flashed(yesterday) twrp with multiboot option.
Reflah it, uncheck multiboot and try "optimized stock".

dzidexx said:
I think that you flashed(yesterday) twrp with multiboot option.
Reflah it, uncheck multiboot and try "optimized stock".
Click to expand...
Click to collapse
I can't find any multi boot option in twrp...

I have the same problem with the cold booting linux, did you solved it?

Natebluehooves said:
I can't find any multi boot option in twrp...
Click to expand...
Click to collapse
I have this same issue lol can't boot into anything!

Installed TWRP to Boot, want to boot myself in the a**.

Own the OPP6; Rooted, on OxygenOS 5.18.
Went to install the newest TWRP (was going to install XXX no limits), when asked where to install it to, accidentally, without thinking, hit install to Boot.
Problems.
I can get into fastboot, the PC sees the phone in fastboot.
Have tried to flash a recovery image and similar, got an error saying: FAILED (remote: (recovery_b) No such partition).
Just want to get the phone booting again, wipe the whole thing start over, from fastboot.
Any help appreciated.

https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892

Thank you, the tool worked like a charm.
BTW: I did search and find other "methods" but none of them worked

noncomjd said:
Own the OPP6; Rooted, on OxygenOS 5.18.
Went to install the newest TWRP (was going to install XXX no limits), when asked where to install it to, accidentally, without thinking, hit install to Boot.
Problems.
I can get into fastboot, the PC sees the phone in fastboot.
Have tried to flash a recovery image and similar, got an error saying: FAILED (remote: (recovery_b) No such partition).
Just want to get the phone booting again, wipe the whole thing start over, from fastboot.
Any help appreciated.
Click to expand...
Click to collapse
What you should have done was fastboot boot twrp.img. which would start twrp, then you could have used the installer in to install twrp on phone. After that you would have to installed stock or custom kernel.

MrSteelX said:
What you should have done was fastboot boot twrp.img. which would start twrp, then you could have used the installer in to install twrp on phone. After that you would have to installed stock or custom kernel.
Click to expand...
Click to collapse
That is exactly what I wanted to do.
I could get into TWRP, but I couldn't see the phone on the PC and couldn't move files (ROM) to the phone (although fastboot was working and I could see the device using adb) but I couldn't figure out how to have TWRP look for or find the ROM on the PC.

There's no recovery partition on A/B phones remember.

RusherDude said:
There's no recovery partition on A/B phones remember.
Click to expand...
Click to collapse
Thanks for that. and that explains a few things and explains why when I installed TWRP, I didn't see the recovery option. Doesn't pardon my hitting install to Boot.
Just thought of another Q, if there is no recovery partition, where is the OEM recovery stored? (I figured the lack of a recovery partition is why TWRP gets overwritten if installed without a custom ROM)
I did a quick read on that, it seems really interesting and may be of some use as soon as I learn more.
I've got so much to learn about this. I keep meaning to take time to begin, but stuff comes up and boom more changes.
I've got to do more reading to take advantage of that.
@MrSteelX mentioned that I could have used TWRP to install a ROM from the PC.
Is this what is referred to as "sideloading". I've been looking for some info on this and haven't really come across much that is any good.
Are there any available guides that anyone can point to so I can learn about using TWRP that way?

noncomjd said:
Thanks for that. and that explains a few things and explains why when I installed TWRP, I didn't see the recovery option. Doesn't pardon my hitting install to Boot.
Just thought of another Q, if there is no recovery partition, where is the OEM recovery stored? (I figured the lack of a recovery partition is why TWRP gets overwritten if installed without a custom ROM)
I did a quick read on that, it seems really interesting and may be of some use as soon as I learn more.
I've got so much to learn about this. I keep meaning to take time to begin, but stuff comes up and boom more changes.
I've got to do more reading to take advantage of that.
@MrSteelX mentioned that I could have used TWRP to install a ROM from the PC.
Is this what is referred to as "sideloading". I've been looking for some info on this and haven't really come across much that is any good.
Are there any available guides that anyone can point to so I can learn about using TWRP that way?
Click to expand...
Click to collapse
In twrp, you go to advance/sideload. Twrp then waits for adb sideload to push file to phone then auto flashes file.
In your case, you would sideload rom to flash and have been go to go.

noncomjd said:
Own the OPP6; Rooted, on OxygenOS 5.18.
Went to install the newest TWRP (was going to install XXX no limits), when asked where to install it to, accidentally, without thinking, hit install to Boot.
Problems.
I can get into fastboot, the PC sees the phone in fastboot.
Have tried to flash a recovery image and similar, got an error saying: FAILED (remote: (recovery_b) No such partition).
Just want to get the phone booting again, wipe the whole thing start over, from fastboot.
Any help appreciated.
Click to expand...
Click to collapse
If you have working fastboot mode and getting detected via fastboot then
fastboot flashable stock rom via fastboot mode.
U don't have to do anything just downloaded zip file unzip it any folder u want. Connect u r phone to. Computer in fastboot mode
Then go to that folder and just click flash all bat waut for 10to 15 min and then phone boots in working oos.
(all data will be get wipes after this)
Link
https://www.google.co.in/amp/s/foru...m-stock-fastboot-roms-oneplus-6-t3796665/amp/

MrSteelX said:
In twrp, you go to advance/sideload. Twrp then waits for adb sideload to push file to phone then auto flashes file.
In your case, you would sideload rom to flash and have been go to go.
Click to expand...
Click to collapse
Thanks.
I will give this a try. After I learn a little more about the A/B partitions & recovery on this phone, I want to try one on the custom ROMs.

pankspoo said:
If you have working fastboot mode and getting detected via fastboot then
fastboot flashable stock rom via fastboot mode.
U don't have to do anything just downloaded zip file unzip it any folder u want. Connect u r phone to. Computer in fastboot mode
Then go to that folder and just click flash all bat waut for 10to 15 min and then phone boots in working oos.
(all data will be get wipes after this)
Link
https://www.google.co.in/amp/s/foru...m-stock-fastboot-roms-oneplus-6-t3796665/amp/
Click to expand...
Click to collapse
Thanks for the link/guide. I had been trying an iteration of this (and the guide) but after reading your link, it too explains some things. I was trying to restore a Stock ROM from fastboot according to your link:
Things are changing with the advent of project treble. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlcoked. This will erase all your data and will wipe
I download and was trying to use the stock ROMs, I didn't see any bats, and now I know why.
Lots more reading to do. I love doing playing with this stuff, but trying to learn & keep up with things burns time, which most days I don't have.
This is the longest I've ever been on a stock OS (6 weeks? got the phone right after its release) although it's rooted (can never leave things completely alone).

noncomjd said:
Thanks for the link/guide. I had been trying an iteration of this (and the guide) but after reading your link, it too explains some things. I was trying to restore a Stock ROM from fastboot according to your link:
Things are changing with the advent of project treble. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlcoked. This will erase all your data and will wipe
I download and was trying to use the stock ROMs, I didn't see any bats, and now I know why.
Lots more reading to do. I love doing playing with this stuff, but trying to learn & keep up with things burns time, which most days I don't have.
This is the longest I've ever been on a stock OS (6 weeks? got the phone right after its release) although it's rooted (can never leave things completely alone).
Click to expand...
Click to collapse
I have to unzip the downloaded fastboot ROM at any folder on computer and open that folder u will see named [flash all bat]
Now connect phone in fastboot mode to computer and just click [flash all bat] file

noncomjd said:
Thanks for that. and that explains a few things and explains why when I installed TWRP, I didn't see the recovery option. Doesn't pardon my hitting install to Boot.
Just thought of another Q, if there is no recovery partition, where is the OEM recovery stored? (I figured the lack of a recovery partition is why TWRP gets overwritten if installed without a custom ROM)
I did a quick read on that, it seems really interesting and may be of some use as soon as I learn more.
I've got so much to learn about this. I keep meaning to take time to begin, but stuff comes up and boom more changes.
I've got to do more reading to take advantage of that.
@MrSteelX mentioned that I could have used TWRP to install a ROM from the PC.
Is this what is referred to as "sideloading". I've been looking for some info on this and haven't really come across much that is any good.
Are there any available guides that anyone can point to so I can learn about using TWRP that way?
Click to expand...
Click to collapse
"recovery" (what's left of it... wipe and mostly nothing else) is inside the boot partition. TWRP on those devices is installed into the boot partition (NOT overwriting the boot partition, but into the "ramdisk", a part of the kernel where OEM recovery resides and where TWRP, Magisk, Xposed and all the mods do their stuff on the kernel. On a phone with A/B partitions, you have to fastboot BOOT twrp, and then you have to flash the installer zip, you should never ever flash the image to any partition since there isn't any.

RusherDude said:
"recovery" (what's left of it... wipe and mostly nothing else) is inside the boot partition. TWRP on those devices is installed into the boot partition (NOT overwriting the boot partition, but into the "ramdisk", a part of the kernel where OEM recovery resides and where TWRP, Magisk, Xposed and all the mods do their stuff on the kernel. On a phone with A/B partitions, you have to fastboot BOOT twrp, and then you have to flash the installer zip, you should never ever flash the image to any partition since there isn't any.
Click to expand...
Click to collapse
Thanks for the information.
and this is what I did, originally I thought I had accidentally selected the wrong partition, but it seems since there is no recovery partition, I did it wrong from the start.
Q: I'm guessing this is why when you do load TWRP (the correct way, which I did once, following a guide) without a custom ROM (still using Oxygen OS) that the OEM recovery overwrites TWRP or the OEM recovery is called up at the next reboot into recovery?
Q: I understand, at least in theory the benefit of the A/B partitions, what is the benefit of eliminating the recovery partition other than giving more control of the phone to the OEM and OS? Is this setup limited to the stock kernel or mandated to be copied by any potential replacement kernels (this information is new to me, I haven't yet read up on kernels).

[Solved][PX5 GS] Can not use custom recovery

I would like to flash custom recovery -> in order to use custom ROM -> in order to gain split screen in my 7" device (ehhh)
I have root, adb, access to bootloader (everything what I need..) but it does not work in default way.. - I mean flashing just by fastboot flash recovery TWRP.img
I have checked those TWRP builds
https://twrpbuilder.github.io/downloads/twrp/ (type px5)
Flashing worked fine (no error, success message)
But after rebooting to recovery I still have original recovery. Note: I have to reboot to system, and then to recovery by adb command. There is no reset button on my device, I can only enter bootloader by long pressing volume button while booting.
I saw `backup` partition in my device. Is it possible that system is reverting recovery partition? How to fix that so I can use TWRP

SZAMAN92 said:
I would like to flash custom recovery -> in order to use custom ROM -> in order to gain split screen in my 7" device (ehhh)
I have root, adb, access to bootloader (everything what I need..) but it does not work in default way.. - I mean flashing just by fastboot flash recovery TWRP.img
I have checked those TWRP builds
https://twrpbuilder.github.io/downloads/twrp/ (type px5)
Flashing worked fine (no error, success message)
But after rebooting to recovery I still have original recovery. Note: I have to reboot to system, and then to recovery by adb command. There is no reset button on my device, I can only enter bootloader by long pressing volume button while booting.
I saw `backup` partition in my device. Is it possible that system is reverting recovery partition? How to fix that so I can use TWRP
Click to expand...
Click to collapse
That TWRP don't work in PX5. I'm trying to get it work

Good luck!
Please inform me if you will succeed.

Have you first tried to boot TWRP without flashing? I'd most certianly want to try that before flashing something.
Did that work?
This might sound super silly, but did you also unlock the bootloader first? (Sorry, I'm not familiar with your specific device so this may or may not apply in your situation)

stokedcrf said:
Have you first tried to boot TWRP without flashing? I'd most certianly want to try that before flashing something.
Did that work?
This might sound super silly, but did you also unlock the bootloader first? (Sorry, I'm not familiar with your specific device so this may or may not apply in your situation)
Click to expand...
Click to collapse
Any advice is welcome thanks
But without unlocking bootloader I would not be able to go to bootloader and use fastboot tool right? So I concluded it is already unlocked.
I tried
fastboot boot TWRP.img
Image was downloaded and booted (success message was printed in console), I lost connection with device so it went in some other mode then bootloader, but after 30 seconds of black screen I have switch power off and back on to restart.

SZAMAN92 said:
Any advice is welcome thanks
But without unlocking bootloader I would not be able to go to bootloader and use fastboot tool right? So I concluded it is already unlocked.
I tried
fastboot boot TWRP.img
Image was downloaded and booted (success message was printed in console), I lost connection with device so it went in some other mode then bootloader, but after 30 seconds of black screen I have switch power off and back on to restart.
Click to expand...
Click to collapse
What android version you have ? 8 ?

tuga_z said:
What android version you have ? 8 ?
Click to expand...
Click to collapse
9
Build nr: rk3368-userdebug 9 PQ2A 190305
Kernel v: 4.4.167
MCU: MTCE_GS_V3.07_3
It is that build:
https://yadi.sk/d/umCvHqCDzHccr/RockChip PX5 Android 9/HA/HA_px5_9.0_ota(20190528)升级包.7z
I tried using A8 roms but I can not flash it with original recovery.. It requires device name be PX5 (I have rk3368). If I remove checking from rom updater script, signature verification fails.

I have tried recovery from Malaysk pack (extracted from update.zip), tried RecoveryInstaller from malaysk, lot of TWRP which I have found in web.
Nothing worked.
However as a last chance I used bootable SD from Malaysk - recovery (for android 8) successfully installed, Malyask rom installed. Im happy now
BTW. If you want you system to not revert recovery - you need to remove "/system/recovery-from-boot.p"

SZAMAN92 said:
I have tried recovery from Malaysk pack (extracted from update.zip), tried RecoveryInstaller from malaysk, lot of TWRP which I have found in web.
Nothing worked.
However as a last chance I used bootable SD from Malaysk - recovery (for android 8) successfully installed, Malyask rom installed. Im happy now
BTW. If you want you system to not revert recovery - you need to remove "/system/recovery-from-boot.p"
Click to expand...
Click to collapse
By this you mean that you no longer need TWRP for android 8 ?

tuga_z said:
By this you mean that you no longer need TWRP for android 8 ?
Click to expand...
Click to collapse
I mean I already have Recovery v8. So I was been able to flash custom A8 ROM.
However if you would implement TWRP please message me It is always better.

SZAMAN92 said:
I mean I already have
However if you would implement TWRP please message me It is always better.
Click to expand...
Click to collapse
Except if you ever want to update your unit or MCU, then it's pretty much useless.

marchnz said:
Except if you ever want to update your unit or MCU, then it's pretty much useless.
Click to expand...
Click to collapse
Maybe you are right. But at least it is easier to backup / restore whole device with TWRP.