Related
I've been thinking about bricks recently.
The common brick is caused by a failure to boot the recovery system in conjunction with having the command field of the MISC partition set to "boot-recovery".
When the command field is set to boot-recovery, the SPL will ***IGNORE*** the boot-time signals for altering the boot mode, such as the BACK or CAMERA buttons to go into FASTBOOT.
When a recovery fails to boot, it will NOT clear the command field as a successful boot will, hence it will always try to boot into the broken recovery, and nothing you do will break it out.... bricked.
In general, it is my belief that having the recovery fail to boot ***FOR ANY REASON*** will have the same effect.
Yes, a REALLY broken recovery will convince the SPL to skip straight to fastboot. Unfortunately, a PARTLY working recovery will NOT, i.e. it just needs to be good enough that the SPL can recognize a recovery image.
There are many reasons why a recovery partition can fail to boot!
A recent observation by FIRERAT is that the CM5.0.8 kernel WILL NOT successfully boot a phone with 0.95.3000 *when flashed*. It *will* boot it using "fastboot boot"... which adds to the danger since the typical testing procedure IS to "fastboot boot". The second observation is that it works perfectly with 1.33.2003, which actually uses the SAME PARTITION TABLE as 0.95.3000.
So if someone builds a recovery using the CM5.0.8 kernel, you could have a brick factory.
The process that would brick a phone is this:
From the SYSTEM, flash the recovery image, then "reboot recovery". You are now bricked. And this, of course, is a very common process.
This is my WARNING about building custom recovery images:
1) Testing the image using "fastboot boot" is ***NOT ADEQUATE***. It MUST be tested by being FLASHED.
2) You can safely test it by NOT doing ANYTHING that will set the command field to "boot-recovery".... i.e. flash the image, and do a NORMAL reboot holding the HOME button.
3) Recovery image MUST be EXTENSIVELY TESTED... 0.95.x000, 1.33.2003, 1.33.2005. I suggest that YOU THE USER test your recovery image when you install it!
Further thought: It is seeming more and more that the simple presence of a recovery image is the cause of bricks. Since a BLANK recovery image will convince the SPL to jump into fastboot, I suggest that it might just be a really good idea to keep your recovery blank. As long as you have FASTBOOT, you can always "fastboot boot recovery.img" with no chance of bricking.
So... in rooting, the first step is to install SOME SPL with fastboot... i.e. 1.33.2003 or 0.95.3000. The second step for added security is to wipe out your recovery partition.
Note: This is by no means to be taken as a negative with respect to the CM image or kernel. There is nothing particularly wrong with it or dangerous about it since it was never *INTENDED* that that kernel be used for a recovery. Breaking your boot partition is never a problem since you have fastboot waiting to save the day.
Is it possible to build an spl that always allows access to fastboot?
jtroye32 said:
Is it possible to build an spl that always allows access to fastboot?
Click to expand...
Click to collapse
Possible? Certainly.
The problem is in convincing EVERYONE to actually INSTALL it.
Keep in mind that there are a LOT of people who still use the 0.95.0000 SPL (stock dream no fastboot), despite all the information everywhere saying that they should have *SOME* kind of engineering SPL.
The RECOVERY is a much easier place to play, for several reasons;
1) flashing the recovery feels "safer".
2) everybody's doing it
3) SOURCE CODE!!! (rather than decompile/reverse engineer/hack).
If the recovery was made to be SAFE (which includes being GONE), then a severe oversight in the SPL design loses its teeth.
You could always get devs to recommend a hacked SPL with that functionality. I mean, there's so many people with Danger now, when it used to be only people playing with ports.
Tony_SpaZ said:
You could always get devs to recommend a hacked SPL with that functionality. I mean, there's so many people with Danger now, when it used to be only people playing with ports.
Click to expand...
Click to collapse
You can recommend whatever you want. There is NOTHING you can do to make people use it.
Recovery on the other hand... well that's fairly easy.... you can enforce a custom recovery with a custom update-script much more completely than you can enforce a particular SPL.... and people are MUCH more comfortable with flashing a custom recovery than a custom SPL since they figure that the SPL is still there to protect them! For that matter, there are VERY FEW recoveries that would need to be modified in order to cover EVERYBODY -- most importantly, amon-ra and clockwork. The old recoveries (jf, cm) don't matter much since nobody is pushing them.... even CM recommends amon-ra and clockwork over his recovery.
And then to force everybody to use a single SPL? Well *right now* there are TONS of SPLs in use! You want to shut the door on all of them?
Fact is simple. I am NOT suggesting that you don't go hack up a custom "safe" SPL. In fact I ENCOURAGE it. I don't think you CAN though -- otherwise you wouldn't be asking for it. Find somebody who CAN -- hint: not too many around, ezterry is one of those few, he even mentioned that he WANTED to, but it is FAR from trivial.
Hint 2: 1.33.2003 is probably your best starting point... it seems to have the greatest universal compatibility of ALL the available SPLs.... it boots kernels incompatible with 0.95 and its compatible with radios incompatible with 1.33.2005.
But this does NOT eliminate the need for a safe RECOVERY, because FACE IT -- the RECOVERY is where the bricking ACTUALLY OCCURS.
Ok, this caught my attention.
I like your idea of working without recovery. Rom updates could force either the install of a "safe" recovery (I assume that that's why AOSP and official builds include recovery images and force-flash them), or just format the recovery partition entirely without writing anything back.
It would also force people to use an engineering SPL since any work that you might have to do through recovery would have to be done through fastboot boot recovery.
I see one problem, though. Say you're a person who has 0.95 SPL, you pick up a rom that force-removes recovery, and you finish flashing the rom. Now you're sans recovery and with an SPL that can't fastboot boot. Your only option at this point is to flash recovery through system, and that has a chance (if the "dev" who packed the forced recovery is an idiot) of bricking your phone.
A better choice would be to force-flash an SPL that's safe to use (1.33+), but I don't know if that can be done from an OTA package.
Let's face it. If a person bricks a phone, it's usually because they're dumb, so we can't realistically expect a person to learn to use fastboot boot recovery any time they have to flash a new rom.
I believe the force-flash SPL is a better option.
whenever I switch from 0.95.xxxx to 1.33.xxxx I
fastboot erase system -w
fastboot erase recovery
fastboot boot recovery.img
flash spl-1.33.xxxx.zip
fastboot boot recovery.img
seems the safest way
good to know! thanks for the warning i really love how much you guys care about the community and this kind of.... obsolete? phone
jubeh said:
Ok, this caught my attention.
I like your idea of working without recovery. Rom updates could force either the install of a "safe" recovery (I assume that that's why AOSP and official builds include recovery images and force-flash them), or just format the recovery partition entirely without writing anything back.
It would also force people to use an engineering SPL since any work that you might have to do through recovery would have to be done through fastboot boot recovery.
I see one problem, though. Say you're a person who has 0.95 SPL, you pick up a rom that force-removes recovery, and you finish flashing the rom. Now you're sans recovery and with an SPL that can't fastboot boot. Your only option at this point is to flash recovery through system, and that has a chance (if the "dev" who packed the forced recovery is an idiot) of bricking your phone.
A better choice would be to force-flash an SPL that's safe to use (1.33+), but I don't know if that can be done from an OTA package.
Let's face it. If a person bricks a phone, it's usually because they're dumb, so we can't realistically expect a person to learn to use fastboot boot recovery any time they have to flash a new rom.
I believe the force-flash SPL is a better option.
Click to expand...
Click to collapse
I wouldn't want to FORCE erase the recovery when installing a system image... that would be silly since the recovery failure is related to the radio and spl and NOT the system image.
You are also missing one option for a 0.95.0000 SPL (note that 0.95.3000 is also a 0.95 SPL, but has fastboot, so blank recovery OK there) is NBH files.
Best way to erase a recovery is through fastboot. This has the added benefit of ensuring that you HAVE fastboot.
the_fish said:
good to know! thanks for the warning i really love how much you guys care about the community and this kind of.... obsolete? phone
Click to expand...
Click to collapse
Obsolete? Nope. Not even close. The defining characteristic of obsolete is that it is not able to perform the required function. This hardware still works great and 2.2 is supposed to be even better on it.
Firerat said:
whenever I switch from 0.95.xxxx to 1.33.xxxx I
fastboot erase system -w
fastboot erase recovery
fastboot boot recovery.img
flash spl-1.33.xxxx.zip
fastboot boot recovery.img
seems the safest way
Click to expand...
Click to collapse
That appears to be quite safe
It should even withstand a radio/spl mismatch (1.x radio + 1.33.2005 SPL or 3.x radio + SPL < 1.33.2005)
been thinking, I'm not sure it is quite as dangerous
Clockwork ROM Manager reboots to recovery
and we know that we don't get bricks when it fails to flash recovery via cm5.0.7test5+ based ROM
does that set the boot flag in the same way?
Firerat said:
been thinking, I'm not sure it is quite as dangerous
Clockwork ROM Manager reboots to recovery
and we know that we don't get bricks when it fails to flash recovery via cm5.0.7test5+ based ROM
does that set the boot flag in the same way?
Click to expand...
Click to collapse
When it fails to flash recovery, it must be leaving it in the OLD state, or in a so-dead-the-SPL-can-see-it state.
what about suggesting that you should *never* use the reboot recovery command from shell? its easier than suggesting a new spl, and its a guarantee against stupidly bricking your phone.
$.02, and im gone.
relevent81 said:
what about suggesting that you should *never* use the reboot recovery command from shell? its easier than suggesting a new spl, and its a guarantee against stupidly bricking your phone.
$.02, and im gone.
Click to expand...
Click to collapse
Because reboot-recovery can also be set from update-radio and update-hboot. This is where the REAL danger comes in -- if it didn't do that, then there wouldn't be nearly as many deathspl bricks -- it would look nice and bricked, but still respond perfectly to back/camera, which would bring up fastboot and offer the cure -- especially since 1.33.2005 is actually a strong SPL that can fastboot flash both radio and SPL.
Firerat said:
been thinking, I'm not sure it is quite as dangerous
Clockwork ROM Manager reboots to recovery
and we know that we don't get bricks when it fails to flash recovery via cm5.0.7test5+ based ROM
does that set the boot flag in the same way?
Click to expand...
Click to collapse
My thoughts exactly. I had Clockwork running fine installed from a test4 rom. I wiped and upgraded to a 5.0.8 rom (via clockwork), and then on the new install Clockwork forced me to re-install the recovery again in order to use it. I did that and rebooted in to it and almost had a heart attack when it was stuck on G1. After a battery pull it started up fine again. I flashed clockwork yet again through the app, rebooted, and all is normal again. Whew.
Now this thread is saying that the first time clockwork flashed its recovery it messed it up so bad even the header that tells SPL it is a recovery was broken, but it it had that header correct I would have been bricked? ...and sorry for OT, but why did the recovery flash fine the second time through ROM manager? How are you supposed to flash a recovery in a 5.0.8cm branch?
rpmccormick said:
My thoughts exactly. I had Clockwork running fine installed from a test4 rom. I wiped and upgraded to a 5.0.8 rom (via clockwork), and then on the new install Clockwork forced me to re-install the recovery again in order to use it. I did that and rebooted in to it and almost had a heart attack when it was stuck on G1. After a battery pull it started up fine again. I flashed clockwork yet again through the app, rebooted, and all is normal again. Whew.
Now this thread is saying that the first time clockwork flashed its recovery it messed it up so bad even the header that tells SPL it is a recovery was broken, but it it had that header correct I would have been bricked? ...and sorry for OT, but why did the recovery flash fine the second time through ROM manager? How are you supposed to flash a recovery in a 5.0.8cm branch?
Click to expand...
Click to collapse
flash recovery via fastboot or recovery
@Firerat
not sure it belongs to this thread but am trying to use MTD 70 2 on LeFeuDeDieu v2.5.1 which uses CM 5.0.8 and I haven't been able to make it boot (on previous version 2.4) I am about to try v2.5.1, any help will be appreciated as always
juangil said:
@Firerat
not sure it belongs to this thread but am trying to use MTD 70 2 on LeFeuDeDieu v2.5.1 which uses CM 5.0.8 and I haven't been able to make it boot (on previous version 2.4) I am about to try v2.5.1, any help will be appreciated as always
Click to expand...
Click to collapse
For me i must do this if I want it to boot! I have clockwork now, not amon_ra
-Goto rec, Flash 1-1 recovery of MTD.zip thing
-wipe everything(exc batt stats)
-reboot recovery
-flash rom, then any xtras
-flash the boot MTD file.zip(version 1)
My Partition is, 3-cache, 90-sys, rest-data
Ace42 said:
For me i must do this if I want it to boot! I have clockwork now, not amon_ra
-Goto rec, Flash 1-1 recovery of MTD.zip thing
-wipe everything(exc batt stats)
-reboot recovery
-flash rom, then any xtras
-flash the boot MTD file.zip(version 1)
My Partition is, 3-cache, 90-sys, rest-data
Click to expand...
Click to collapse
thanks, I'll try that
1 more Question (I know am on the wrong thread sorry)
how about no wipe updates? will that affect the new partition or should I flash the boot MTD again?
thx
So, I posted earlier about looking for a Stock Android 2e recovery image, to no avail.
I have pulled the recovery from a stock build and being that I don't have an EVO, I respectfully would like to ask a couple people to test this.
The goal is, that after flashing the zip via HBOOT, that entering recovery will yield the stock HTC Recovery that came with the phone. I believe this is necessary to have to successfully install ota updates from Sprint in the future.
Of course, your S-OFF will allow you to revert back to Clockwork or Amon_Ra.
It's attached at the bottom of the post. Appreciate the feedback.
I think it is possible to flash this recovery via fastboot. Take out the recovery.img and go into fastboot and simply use:
Code:
fastboot flash recovery recovery.img
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.
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).
So a while back I unlocked and rooted my phone. I did something wrong the first time around and it bricked, so I started from scratch and flashed a stock firmware image, then installed Magisk. I used TWRP, but did not install it. No problems, except the OTA updates don't work, and the phone constantly nags me about it. I had a similar problem on a prior phone (Moto G4+) when the recovery partition was modified, and flashing back to stock fixed it on that phone. I finally get around to trying to fix this, figured Magisk did something to either boot or bootloader, so I re-flash boot.img and bootloader.img using the same images and instructions I originally used to flash my phone. boot.img fails claming bad signature, but bootloader.img succeeds. Now my phone will not successfully boot and claims it needs a factory reset. If I boot to TWRP, I can decrypt and see my data is intact (I explicitly chose not to encrypt my phone for this exact reason but *shrug*). If I install TWRP, it only boots to a TWRP screen and will not accept touch input. Booting TWRP from fastboot functions normally.
So basically, my data is intact. I want it to remain intact. My bootloader is mad at me. What do I do?
I have tried flashing the bootloader.img from multiple versions of the stock ROM and all of them have the same result. Using 'fastboot flash bootloader bootloader.img'
My only theory is that the key was written to the bootloader and flashing stock it doesn't have that key, but that doesn't make sense because what's the point of encryption then (see: I explicitly did not want my phone encrypted).
Update: I was able to fix it and retain all my data by using LMSA to recover it, but I edited the flashfile.xml to remove the step where it wipes userdata.