Database Info

Can't get past Google Screen

I just restored from the official google 4.4.2 images and my phone cant get past the Google screen. Please help!

bobyum said:
I just restored from the official google 4.4.2 images and my phone cant get past the Google screen. Please help!
Click to expand...
Click to collapse
You flashed the factory images?

bobyum said:
I just restored from the official google 4.4.2 images and my phone cant get past the Google screen. Please help!
Click to expand...
Click to collapse
Do a data factory reset and wipe the cache both in recovery and reboot bro.

gee2012 said:
Do a data factory reset and wipe the cache both in recovery and reboot bro.
Click to expand...
Click to collapse
Thinking the same thing. But.. I can admit getting in a hurry and flashing the wrong image! :laugh:

I made sure that I was using the right image and it still wont go past the Google screen. Any other ideas?
edit: okay the phone can't even write the recovery to the phone through fastboot! Any other thoughts?

bobyum said:
I made sure that I was using the right image and it still wont go past the Google screen. Any other ideas?
Click to expand...
Click to collapse
Long press the power button force it to reboot. As soon as the screen goes black hold down the volume down button. That will boot you into the bootloader, from there you can get to recovery. Factory reset, wipe cache.
You flashed stock recovery?
If you have stock recovery go to the bootloader like I said earlier. Choose recovery. Then you will see android laying down. Press volume up and power button at the same time. Do a factory reset.

bobyum said:
I made sure that I was using the right image and it still wont go past the Google screen. Any other ideas?
edit: okay the phone can't even write the recovery to the phone through fastboot! Any other thoughts?
Click to expand...
Click to collapse
If you flashed the whole image inclusing userdata.img it should boot usualy, never xperienced it did not personaly. So besides a wipe have no idea bro, you might try to reflash the rom again. Are you using a Toolkit?

gee2012 said:
If you flashed the whole image inclusing userdata.img it should boot usualy, never xperienced it did not personaly. So besides a wipe have no idea bro, you might try to reflash the rom again. Are you using a Toolkit?
Click to expand...
Click to collapse
I did this with the flashh-all.bat provided by the official image. I can't even do that anymore because it just gets stuck when writing the bootloader. Totally out of ideas right now. Is there any way I can reformat the partition through fastboot? Would that help?

bobyum said:
I did this with the flashh-all.bat provided by the official image. I can't even do that anymore because it just gets stuck when writing the bootloader. Totally out of ideas right now. Is there any way I can reformat the partition through fastboot? Would that help?
Click to expand...
Click to collapse
Try this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
After that flash the rom again with flash.all.batt

maybe flash each part individually (not using flashall)
Sent from my Nexus 5 using Tapatalk

gee2012 said:
Try this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
After that flash the rom again with flash.all.batt
Click to expand...
Click to collapse
Unfortunately, it didnt help Still stuck at writing bootloader...

beaver2233 said:
maybe flash each part individually (not using flashall)
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yup, that might work better maybe

hmm so in which order should i flash them in?
edit: I honestly think the flash storage failed. Ill just apply for RMA then. Do you guys know if I bought my phone in early December, will I still be eligible?

bobyum said:
hmm so in which order should i flash them in?
edit: I honestly think the flash storage failed. Ill just apply for RMA then. Do you guys know if I bought my phone in early December, will I still be eligible?
Click to expand...
Click to collapse
How to flash a factory image. Erasing everything in fastboot should have done the trick. Erase everything then do method 2. You have to reboot the bootloader after flashing the bootloader and again after flashing the radio. One year to RMA. .
---------- Post added at 02:14 AM ---------- Previous post was at 01:57 AM ----------
These are the commands I would use. The name of the images for the bootloader and radio are for 4.4.2.
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot

Thanks all for the help! Will try it tomorrow. Hopefully it works

wantabe said:
How to flash a factory image. Erasing everything in fastboot should have done the trick. Erase everything then do method 2. You have to reboot the bootloader after flashing the bootloader and again after flashing the radio. One year to RMA. .
---------- Post added at 02:14 AM ---------- Previous post was at 01:57 AM ----------
These are the commands I would use. The name of the images for the bootloader and radio are for 4.4.2.
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Click to expand...
Click to collapse
I'd go one better and look to do a COMPLETE reflash - userdata and all! I'd also rename bootloader-hammerhead-hhz11k.img to bootloader.img and radio-hammerhead-m8974a-1.0.25.0.23.img to radio.img as it means there's less to get wrong! SO, to recap:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot format cache
I'd then boot into the stock recovery and perform a factory reset to make sure everything is in order and then reboot. I've done this exact method a number of times on my Nexus 5 and it works every time

EddyOS said:
I'd go one better and rename bootloader-hammerhead-hhz11k.img and radio-hammerhead-m8974a-1.0.25.0.23.img to just bootloader.img and radio.img to make it easier - less to type out and get wrong!
Click to expand...
Click to collapse
I usually do the same thing too but I left the names as a hint to verify that he had the correct images.
I almost never flash userdata and recovery unless I'm selling a device. I've also never rebooted the bootloader between every image Except after the bootloader and radio images but I agree that your method is covering all the bases!

wantabe said:
I usually do the same thing too but I left the names as a hint to verify that he had the correct images.
I almost never flash userdata and recovery unless I'm selling a device. I've also never rebooted the bootloader between every image Except after the bootloader and radio images but I agree that your method is covering all the bases!
Click to expand...
Click to collapse
As I hardly have any data to backup bar some custom ring tones I always reflash the userdata partition to be thorough. As for the reboots, I've just done it from habit, again just to be thorough. If it still doesn't work after that then it's goosed!

Try using the backup bootloader. Press and hold both volume buttons with the power button. That will take you into the backup bootloader.

Thanks to everyone for helping but I could not even get past writing the bootloader to the phone. I honestly think the flash storage and failed so will be RMAing. Hopefully they will accept it...

Stuck at boot up failed!

Hey guys,
I wanted to have the Android 5.1 update so I looked up how I can do this.
I ended up at a youtube video called ''How to Install OFFICIAL Android 5.1 Lollipop GPe on Moto G [XT1033 & XT1032]'' by Samanyou Garg.
I did the first thing he said with the file called 5.x to 4.4.4 gpe. after I did this my phone didn't boot up. Now i'm stuck at th bootloader menu and if i try anything it says ''boot up failed''
Please help me with this problem, im stuck for 4 days right now! and I really need my phone tommorow.

poolta321 said:
Hey guys,
I wanted to have the Android 5.1 update so I looked up how I can do this.
I ended up at a youtube video called ''How to Install OFFICIAL Android 5.1 Lollipop GPe on Moto G [XT1033 & XT1032]'' by Samanyou Garg.
I did the first thing he said with the file called 5.x to 4.4.4 gpe. after I did this my phone didn't boot up. Now i'm stuck at th bootloader menu and if i try anything it says ''boot up failed''
Please help me with this problem, im stuck for 4 days right now! and I really need my phone tommorow.
Click to expand...
Click to collapse
Flash a custom recovery and wipe system ,data,dalvik and cache then flash cm 12.1 nightly

sjandroiddeveloper said:
Flash a custom recovery and wipe system ,data,dalvik and cache then flash cm 12.1 nightly
Click to expand...
Click to collapse
I tried to flash TWRP but when I put ''adb devices'' in cmd it doesn't come up with my device
update: wait It does work now with fastboot devices

poolta321 said:
I tried to flash TWRP but when I put ''adb devices'' in cmd it doesn't come up with my device
update: wait It does work now with fastboot devices
Click to expand...
Click to collapse
Okay I flashed TWRP but when I do recovery It still says Boot up failed

poolta321 said:
Okay I flashed TWRP but when I do recovery It still says Boot up failed
Click to expand...
Click to collapse
First if all don't do things you don't know about, just watching a random YouTube videos and following is a stupid thing
Now try this
In fastboot mode enter following commands
fastboot erase recovery
fastboot flash recovery recovery.img
---------- Post added at 12:24 PM ---------- Previous post was at 12:23 PM ----------
And why did you make 4 threads for the same thing
Dont spam please

sjandroiddeveloper said:
First if all don't do things you don't know about, just watching a random YouTube videos and following is a stupid thing
Now try this
In fastboot mode enter following commands
fastboot erase recovery
fastboot flash recovery recovery.img
---------- Post added at 12:24 PM ---------- Previous post was at 12:23 PM ----------
And why did you make 4 threads for the same thing
Dont spam please
Click to expand...
Click to collapse
sorry for the many threads.
I did what you said and reflashed TWRP but it still says Boot up failed when I go to recovery

poolta321 said:
sorry for the many threads.
I did what you said and reflashed TWRP but it still says Boot up failed when I go to recovery
Click to expand...
Click to collapse
When you flash recovery what does it say on phone's fastboot screen

sjandroiddeveloper said:
When you flash recovery what does it say on phone's fastboot screen
Click to expand...
Click to collapse
cmd: getvarartition-type:recovery
cmd: erase:recovery
cmd: getvarartition-type recovery
cmd: getvar:max-download-size
cmd: download:007b1800
cmd: flash: recovery
Mismatched partition size (recovery)
Boot up failed

poolta321 said:
cmd: getvarartition-type:recovery
cmd: erase:recovery
cmd: getvarartition-type recovery
cmd: getvar:max-download-size
cmd: download:007b1800
cmd: flash: recovery
Mismatched partition size (recovery)
Boot up failed
Click to expand...
Click to collapse
lol didn't mean to put the smileys there

poolta321 said:
lol didn't mean to put the smileys there
Click to expand...
Click to collapse
Try to flash Philz
And if that doesnt work out then flash the stock 5.0.2 Asian firmware for xt1033
That's the only thing you can do

sjandroiddeveloper said:
Try to flash Philz
And if that doesnt work out then flash the stock 5.0.2 Asian firmware for xt1033
That's the only thing you can do
Click to expand...
Click to collapse
tried Philz and it still says Mismatching partition and boot up failed
Tried stock 5.0.2 Asian firmware for xt1033 but it didn't do anything. on cmd I typed the code but nothing came up

poolta321 said:
tried Philz and it still says Mismatching partition and boot up failed
Tried stock 5.0.2 Asian firmware for xt1033 but it didn't do anything. on cmd I typed the code but nothing came up
Click to expand...
Click to collapse
Mismatch partition size will always occur while flashing a custom recovery, no need to worry about it
And what do you mean nothing came up when you typed commands
Some output must have come

sjandroiddeveloper said:
Mismatch partition size will always occur while flashing a custom recovery, no need to worry about it
And what do you mean nothing came up when you typed commands
Some output must have come
Click to expand...
Click to collapse
image is in attachments.
this happens for all the codes i type via mfastboot.exe

poolta321 said:
image is in attachments.
this happens for all the codes i type via mfastboot.exe
Click to expand...
Click to collapse
Wait it works right now.
I didn't knew I needed to paste the mfasboot in the SDK folder

poolta321 said:
Wait it works right now.
I didn't knew I needed to paste the mfasboot in the SDK folder
Click to expand...
Click to collapse
Okay it finished. but still doesn't do anything.....
It still says Boot up failed an when I try to turn it on it says Fastboot Reason: Fall-trough from normal boot mode

poolta321 said:
Okay it finished. but still doesn't do anything.....
It still says Boot up failed an when I try to turn it on it says Fastboot Reason: Fall-trough from normal boot mode
Click to expand...
Click to collapse
I think your bootloader is corrupted or something like that

sjandroiddeveloper said:
I think your bootloader is corrupted or something like that
Click to expand...
Click to collapse
Is there a way to fix it?

poolta321 said:
Is there a way to fix it?
Click to expand...
Click to collapse
There are plenty of people who have killed their phones by doing something the result of which was corrupt bootloader
And sadly there is no way to fix it

sjandroiddeveloper said:
There are plenty of people who have killed their phones by doing something the result of which was corrupt bootloader
And sadly there is no way to fix it
Click to expand...
Click to collapse
So my phone is broke?

poolta321 said:
So my phone is broke?
Click to expand...
Click to collapse
Technically its called hardbricked

Cant flash any updated Recovery; Rom is Bricked

Hey, so I went to install Android 6.0 on my OPO, but there seemed to be some driver issue with the Wifi.
So I wanted to go back to my original OS, that I had backuped. I had the same Problems on this one too - as soon as I would enable WiFi, It would just crash and reboot after a few seconds.
Then I thought, perhaps with a updated Recovery it would work. So i tried to install a newer version of TWRP.
This is what happens:http://forum.xda-developers.com/attachment.php?attachmentid=3627932&stc=1&d=1454171784
Any help would be much appreciated - thanks!

Check to see if ur bootloader is still unlocked

Bradl79 said:
Check to see if ur bootloader is still unlocked
Click to expand...
Click to collapse
How exactly do you mean that?
I issued the command "fastboot oem unlock" prior to trying to flash.

LennartFuchs said:
How exactly do you mean that?
I issued the command "fastboot oem unlock" prior to trying to flash.
Click to expand...
Click to collapse
Try this: fastboot oem device-info, and show us what it says.

fastboot flash recovery xxxx.img
Don't need to erase recovery it will overwrite existing recovery

deziguy420 said:
fastboot flash recovery xxxx.img
Don't need to erase recovery it will overwrite existing recovery
Click to expand...
Click to collapse
He can't, his OPO doesn't seem to be unlocked. Look in the screenshot please...

fastboot oem device-info
Post ur screenshot here

Honor 6 bricked.Is there any hope?

HI all, i own a Honor 6 L02 and i have the following brick problems.
1. in normal boot i get RESCUE MODE error! func no9 func_boot_kernel
2.when i try to boot in recovery i get RESCUE MODE error no 10 func_boot_recovery
3when i try 3 buttons i get the same as no2
4.when i try fastboot(my phone is unlocked) i cannot flash ANYTHING from pc because i get failed remote command not allowed.
which i think is the major problem
I think it all initiated when i was in 532 lollipop and flashed wrong recovery(recovery for L04) in order to flash superuser which i did and everything was okay indeed.Until i wanted to move back to 316 stable kitkat, but i couldnot flash stock recovery because of the fail command not alowed,so i Installed Flashify ,flashed TWRP and then tried to flash image through twrp.
After rebooting i got bricked.ANY solutions?

Nobody can suggest a solution ? smth to begin from?

pudup said:
Is your bootloader unlocked? If so then the fastboot commands should work. Does your phone show up when you type "fastboot devices"?
If all fastboot still doesn't work, try updating the drivers. Download the latest multi tool and use that. Just flash a stock rom with multi tool or flash all the individual img files with fastboot manually.
Click to expand...
Click to collapse
Thanks for the reply.My bootloader says phone unlocked ,so i supposse it is.My phone shows up when i type fastboot devices.
Im using the latest multitool (and also tried different versions) and have installed the drivers on a fresh formatted windows 8.1 laptop!
the disaster problem is that i cannot flash ANYTHING with fastboot flash commands.For example:
sending recovery okay
writing recovery Failed error remote command not allowed.im getting this error with every single image file(boot,cust , system,recovery stock or custom)

pudup said:
Can you try locking your bootloader? Lock your bootloader and then switch off. Then unlock it and try flashing a recovery.
Also try this command after placing, let's say the twrp.img file for kitkat, in the fastboot folder.
"fastboot boot twrp.img"
That boots directly into twrp without flashing it. See if that works.
Click to expand...
Click to collapse
This is what i get when i try to relock bootloader
* daemon not runnig.starting it now on port 5037
daemon started successfully
T2FDU1482900...... fastboot
...
Failed (remote:stat not match)
finished total time 0.003
If i try to unlock it (although it s written phone unlocked) i get
FAILED ( remoteassword wrong)
shouldnt i get smth like bootloader already unlocked?
The weird thing is im 100% sure that im using the correct bootloader password because i have gotten
it from 3 different sources(local huawei,chinese site huawei a year ago, and the tool a guy has posted here on xda)
Last i have copied twrp.img in the folder and tried the command
fastboot boot twrp.img
downloading 'boot.img'
OKAY [1.047s]
booting...
FAILED(remote:command not allowed)
Thank you for your help,i appreciate it

Using fastboot flash your rom recovery again and your rom recovery
---------- Post added at 07:59 PM ---------- Previous post was at 07:55 PM ----------
dimikon said:
This is what i get when i try to relock bootloader
* daemon not runnig.starting it now on port 5037
daemon started successfully
T2FDU1482900...... fastboot
...
Failed (remote:stat not match)
finished total time 0.003
If i try to unlock it (although it s written phone unlocked) i get
FAILED ( remoteassword wrong)
shouldnt i get smth like bootloader already unlocked?
The weird thing is im 100% sure that im using the correct bootloader password because i have gotten
it from 3 different sources(local huawei,chinese site huawei a year ago, and the tool a guy has posted here on xda)
Last i have copied twrp.img in the folder and tried the command
fastboot boot twrp.img
downloading 'boot.img'
OKAY [1.047s]
booting...
FAILED(remote:command not allowed)
Thank you for your help,i appreciate it
Click to expand...
Click to collapse
you flash TWRP RECOVERY in your BOOT partition it is Wrong
in fast boot do that
for Boot.img (your rom num)
fastboot flash boot boot.img
for recovery (your rom num)
fastboot flash recovery recovery.img

adhamamar said:
Using fastboot flash your rom recovery again and your rom recovery
---------- Post added at 07:59 PM ---------- Previous post was at 07:55 PM ----------
you flash TWRP RECOVERY in your BOOT partition it is Wrong
in fast boot do that
for Boot.img (your rom num)
fastboot flash boot boot.img
for recovery (your rom num)
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
My friend,,, every image i try to flash via fastboot (recovery,boot,system,cust) gives me FAILED error:remote command not allowed
what i did with the twrp.img was the thing that the other guy advised to see if it would work

do you have a TWRP backup of your rom? if yes try restore it ....
if not
Search on this site for TWRP backup for your build num and Change the serial number for the backup copy with your phone serial number (folder name and change inside recovery.log file) (http://4pda.ru/forum/index.php?showtopic=671958&st=920)

adhamamar said:
do you have a TWRP backup of your rom? if yes try restore it ....
if not
Search on this site for TWRP backup for your build num and Change the serial number for the backup copy with your phone serial number (folder name and change inside recovery.log file) (http://4pda.ru/forum/index.php?showtopic=671958&st=920)
Click to expand...
Click to collapse
Thank you very much , but how will i be able to restore it ??? i cannot boot into recovery ,i get error no FUNC_BOOT_RECOVERY

read this http://forum.xda-developers.com/showpost.php?p=56662843&postcount=2945

adhamamar said:
read this http://forum.xda-developers.com/showpost.php?p=56662843&postcount=2945
Click to expand...
Click to collapse
No luck,what this tool does is similar to the multitool unbrick,just tries to flash the images in an automated way,and gives me the
FAILED error remote command not allowed

pudup said:
Sorry but it seems your phone is hard bricked. Take it to a service center.
The "command not allowed" error usually comes up for locked bootloaders or in some cases when usb debugging is not switched on. There is nothing i can think of right now for you to do.
I suggest you lie to the people at the service center and tell them this happened while you were doing a normal update that was given to you OTA.
Click to expand...
Click to collapse
what do you think would be the cost for repairing? i have asked at the local Huawei but they wont repair it because it is not bought from E.U. ,is there any chance that somebody would repair it without sending it back to china(after all guarantee is lost ,i own it for 1,5 years)

screwed up when flashing twrp

Alright so I screwed Up. I got in a rush and followed some guys advice in a thread for a different phone and not sure how to get back on track. Can someone help?
Heres what I did.....
G:\Downloads\oneplus 6 root\android p>fastboot flash recovery twrp-3.2.3-0-enchilada.img
target reported max download size of 536870912 bytes
sending 'recovery' (26744 KB)...
OKAY [ 0.569s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.577s
Click to expand...
Click to collapse
Nothing..... SO I googled and then typed this:
>>fastboot flash boot_b twrp-3.2.3-0-enchilada.img
Phone rebooted and showed twrp, cool. I restarted from there then, sh1t! Now I can't get back to twrp nor the os to follow the correct guide.
I tried holding power for 7 seconds - reboots and shows the red dot with white dots circling eternally
I tried holding volume down + power for 7 seconds - reboots and does the same thing
I tried holding volume up + power for 7 seconds - it goes into this all black recovery mode or something
no recovery mode is seen again yet since my mistake

As far as I know the only TWRP that works for Android p on the OnePlus 6 is bluspark. Try this unbrick thread or try fastboot bluspark.img
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
---------- Post added at 04:45 AM ---------- Previous post was at 04:36 AM ----------
Bluspark
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965
Fastboot commands
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965/page44

dgunn said:
As far as I know the only TWRP that works for Android p on the OnePlus 6 is bluspark. Try this unbrick thread or try fastboot bluspark.img
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
---------- Post added at 04:45 AM ---------- Previous post was at 04:36 AM ----------
Bluspark
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965
Fastboot commands
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965/page44
Click to expand...
Click to collapse
Hey thanks for trying to help me. I somehow just got it into fastboot mode....... Not really sure how, but I tried to follow the guide here to get in to it.
Anyway. I was running android oreo not android p before I tried to flash twrp.. does that make a difference?

So just to be clear you were trying to update TWRP on Oreo and not Android p?
Reason I ask is it says Android p in your original post

dgunn said:
So just to be clear you were trying to update TWRP on Oreo and not Android p?
Reason I ask is it says Android p in your original post
Click to expand...
Click to collapse
Hey! sorry, I made the folder called "Android P" because i will be upgrading to android p lineage os 16. Before I made this mistake, I was running the latest version of android oreo.
GOOD NEWS THOUGH. I somehow got into twrp through fastboot (using bootloader? option). now it keeps booting into twrp. How can I restore stock recovery from here and have a do-over? Thank you!

If you want to restore stock recovery you have to flash the stock image that you are currently on. If you are on the latest Oreo it would be 5.1.11
And I believe you will have to delete the TWRP folder. Not exactly sure when you do that but I read about it somewhere

dgunn said:
If you want to restore stock recovery you have to flash the stock image that you are currently on. If you are on the latest Oreo it would be 5.1.11
And I believe you will have to delete the TWRP folder. Not exactly sure when you do that but I read about it somewhere
Click to expand...
Click to collapse
Ok this is weird..........
I boot into twrp, then I choose; reboot, slot a (instead of default slot b), then the phone boots and it's running android P. what the heck!?
Not sure what happened....... here's the history
1- Android 8
2- Installed Android P dev preview
3- Rolled back to Android 8
4- Installed TWRP, screwed it up
5- Got back to TWRP, chose slot B, now it's booted
6- How is it running Android P

I really just want to get it back to full stock and start over since i screwed up. or even better... just want to fix my screw up the way it's meant to be done right......

Once it screwed up the TWRP it automatically switch slots.
Installed Android p (slot a)
Rolled back (slot b)
TWRP screw up (switched to slot a)
Every time you update it Flags the current slot
---------- Post added at 05:16 AM ---------- Previous post was at 05:15 AM ----------
Boot into recovery and Flash a full stock ROM Oreo

dgunn said:
Once it screwed up the TWRP it automatically switch slots.
Installed Android p (slot a)
Rolled back (slot b)
TWRP screw up (switched to slot a)
Every time you update it Flags the current slot
---------- Post added at 05:16 AM ---------- Previous post was at 05:15 AM ----------
Boot into recovery and Flash a full stock ROM Oreo
Click to expand...
Click to collapse
So is slot A and B only for ROMS and not for recovery?
When I downgraded to 8 from 9, technically 9 was still installed:silly:?

R0ttenB4ndit said:
hey @ajsmsg78. when i do adb devices through usb, it doesn't find it. it will keep booting to the red dot and spinning white dots around it. no recovery option appears on the phone. what mode do I have to be in for the pc to see it at this point?
Click to expand...
Click to collapse
1. Shut off device
2. Unplug any cables or otg connectwd to it.
3. Hold volup while holding power, you should be greeted with fastboot mode and a oneplus logo
4. When you get into the menu do
Code:
fastboot flash boot_x boot.img
Replace _x with _a then _b, to flash it to both slots.
5. By now you should be up and running, to flash twrp you have to
Code:
fastboot boot twrp.img
6. Flash the twrp zip to make it stay.
Reason being that twrp has to be patched to your current boot image, new phones with ab partition tables doesnt have a recovery partition. Thats why we have to boot the twrp img from our pc initially, then use the zip to patch it in permanently.
If you dont have a boot for your oos there is a thread with stock and prepatched twrp boot img's in discussion subforum
I posted this in the other thread before i saw any replies here, if you want to reset to full stock just use the fastboot unbrick bat

I can't boot back into TWRP lol. I also tried changing the slots while in fastboot with PC using
a) fastboot --set-active=a
b) fastboot set_active [a,b]
c) fastboot set_active other
none of them worked. how do you recommend I get back to how twrp and the rom is supposed to be installed? Thank again for the help, big help.
UPDATE: OK I see your previous response, I'll try and report back.

R0ttenB4ndit said:
I can't boot back into TWRP lol. I also tried changing the slots while in fastboot with PC using
a) fastboot --set-active=a
b) fastboot set_active [a,b]
c) fastboot set_active other
none of them worked. how do you recommend I get back to how twrp and the rom is supposed to be installed? Thank again for the help, big help.
Click to expand...
Click to collapse
Well, easiest way is the last mentioned one, its a real simple procedure. Hook up to fastboot, then click the corresponding bat and wait, heres the thread. Then to get twrp running follow my previous posted steps
forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665/page57

After installing the zip... should I wipe the cache/dalvik?
Update: the answer is yes, I'm reading. will update soon.

efinityy said:
1. Shut off device
2. Unplug any cables or otg connectwd to it.
3. Hold volup while holding power, you should be greeted with fastboot mode and a oneplus logo
4. When you get into the menu do
Code:
fastboot flash boot_x boot.img
Replace _x with _a then _b, to flash it to both slots.
5. By now you should be up and running, to flash twrp you have to
Code:
fastboot boot twrp.img
6. Flash the twrp zip to make it stay.
Reason being that twrp has to be patched to your current boot image, new phones with ab partition tables doesnt have a recovery partition. Thats why we have to boot the twrp img from our pc initially, then use the zip to patch it in permanently.
If you dont have a boot for your oos there is a thread with stock and prepatched twrp boot img's in discussion subforum
I posted this in the other thread before i saw any replies here, if you want to reset to full stock just use the fastboot unbrick bat
Click to expand...
Click to collapse
Alright, thought I had it............ but no, now it just keeps rebooting into fast mode. Maybe I'm getting ahead of myself here. Sorry....
Here's what I did:
cmd
>>fastboot flash boot_a twrp-3.2.3-0-enchilada.img
>>fastboot flash boot_b twrp-3.2.3-0-enchilada.img
all ok
>>fastboot boot twrp-3.2.3-0-enchilada.img
the phone boots into twrp, cool
cmd again
>>adb push twrp-installer-enchilada-3.2.3-0.zip /sdcard/
then installed twrp-installer-enchilada-3.2.3-0.zip to make it stay
wiped dalvik/cache and it rebooted to twrp again
think I am now in the clear yay (not).
>>adb push lineage-16.0-20180916_111137-UNOFFICIAL-enchilada.zip /sdcard/
then installed lineage-16.0-20180916_111137-UNOFFICIAL-enchilada.zip
success
I reboot but it still goes to twrp
i change slot to b (it was set to A) hoping maybe it'd boot to lineage
phone reboots and now I can't make it go back to twrp. It keep rebooting into fastboot no matter what I do (hard keys reset/options to choose)
stuck again.

When try to mount the twrp image just to boot into it, I get this now:
>>fastboot boot twrp-3.2.3-0-enchilada.img
downloading 'boot.img'...
OKAY [ 0.568s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.584s

so @efinityy what's this fastboot unbrick bat you speak of? Is it this one I need: flash-all-partitions-fastboot.bat ?
Thanks again.
Which zip is it that I need?

R0ttenB4ndit said:
so @efinityy what's this fastboot unbrick bat you speak of? Is it this one I need: flash-all-partitions-fastboot.bat ?
Thanks again.
Which zip is it that I need?
Click to expand...
Click to collapse
Exactly, but i dont think its the all partitions one, it says in the thread which one almost always is the necessary one, using the wrong one can make it worse... and the twrp zip you need can be gotten from blu_spark kernel threads download section, you want the twrp v2 for pie, v1 for Oreo.. Scratch that, v2 works for all.
Dont flash the twrp img in boot partition yo ? you want the stock boot image/ kernel there... Twrp will later be merged with your current boot, flashing twrp to boot a or b will make you have no kernel, having no kernel equals having no instructions to get android running, and instead of calling the kernel to boot android it will just call twrp over and over
Why we are installing the zip is because previously we had recovery partition, a dedicated partition made for the recovery, now we don't, the recovery is part of the kernel, and we don't ever wanna lose our kernel because that means the phone doesn't know how to boot itself to a usable state, so that's why we only fastboot BOOT twrpimghere... Then install the twrp zip to to patch out the old recovery, like removing a tumor from a body, then patch that empty place with a bandaid that is twrp, so you have your old kernel, the one that can boot the system, and a fresh bandaid on top of it that is twrp... Sorry for the weird metaphoring, I trying to put a/b partitions and it's functions in condensed text is a challenge, but as soon as you grasp the concept you will understand how to do it flawlessly every time

efinityy said:
Exactly, but i dont think its the all partitions one, it says in the thread which one almost always is the necessary one, using the wrong one can make it worse... and the twrp zip you need can be gotten from blu_spark kernel threads download section, you want the twrp v2 for pie, v1 for oreo
Click to expand...
Click to collapse
In the OP it says:
Now usually the one needed is only the first "flash-all-partitions-fastboot.bat" but if you are badly bricked i recommend to use flash-all-partitions.bat .
Click to expand...
Click to collapse
When you say I want the twrp..... is this something else I need before I run the Stock Fastboot ROM bat file?

which step did I go wrong?
I did Replace _x with _a then _b, to flash it to both slots
I thought it was meaning to flash it to both A and B? What did that mean? Thank you!