Database Develop

[NEED HELP] I need help. and will deletehis asap

i have a symphony roar a50 (Bangladesh). it was running everything stock and updated with twrp 2.8.7.0 without root. bootloader was unlocked.
i was trying to root the device with the AIO from this thread:
http://forum.xda-developers.com/cro.../android-one-toolkit-unlocks-relocks-t3294448
the phone suddenly rebooted in the middle of the process and was stuck in a bootloop. i tried to factory reset it but it still didn't work. was still on boot loop.
then i tried to flash the appropriate stock firmware but that didn't help it wont boot. stuck on the boot logo for 1.5 hrs. then tried CM13 nightlies and the cyanpop roms. still nothing.
i am currently in a state of shock as this is a fairly a new phone and i am to travel to Chittagong in ~11 hours.
please help

don't you take a backup ?
and don't you wipe every thing before flashing the cm13 ?

mithun mpk said:
don't you take a backup ?
and don't you wipe every thing before flashing the cm13 ?
Click to expand...
Click to collapse
yes i had a nandroid backup. but twrp says it is corrupt or some reason. and yes i wiped everything before cm13

downgrade twrp2.8.7 to 2.8.4.... 2.8.7 has problem with backup and recovery

https://www.androidfilehost.com/?fid=24389512218018336 twrp 2.8.8.x beta 3
btw this thread is wrong section

I too Had the same Problem once as I Tried Rooting My Android One through the same method as u did, So for fixing it I prefer that U FLASH The Stock MM ROM for Ur Device through STOCK Recovery ( Remember to Wipe Cache and Data b4 Flashing ) AND then ur Device mst be Fixed ( This method worked for me ) And Dude if u want to root Ur Device Follow This Method : -
1) FLASH TWRP RECOVERY
2) Reboot into Recovery and FLASH Thunderzap 5.1 Kernel through Recovery
3) Then FLASH SUPERSU ZIP from Recovery
4) Reboot And Done ! Ur Device is Rooted ! ?

@RoxAndroid how did you fallback to stock recovery from twrp? I'm stuck.

Tanzim Abir said:
@RoxAndroid how did you fallback to stock recovery from twrp? I'm stuck.
Click to expand...
Click to collapse
So......to do that Follow these Steps :-
Download Stock Recovery from here http://forum.xda-developers.com/crossdevice-dev/android-one-general/stockrecoveryandroid-one-t2917457
1) Make sure u have Installed ADB drivers ( If Already did, Skip Step 2)
2) To install ADB drivers first Unable USB debugging From the developer Options in the Setting ( If there is No Developer Options Goto-Setting-About Phone-Tap Build Number 7 Times and go back to settings and Open Developer Options and Unable USB debugging) And then Connect Your Phone to PC and Open ADB DRIVER executable File And Install Drivers.
3) Once Drivers are installed Download ADB AND FASTBOOT from here http://drive.google.com/file/d/0B1nu6Ydzrmi-dWdmS00tWjE1WHM
4)Extract the zip and open the folder and then HOLD SHIFT+Right Click and then click on Open Command Window here
5)And then boot your phone to Fastboot Mode, To do that Power Off the Device and HOLD POWER AND VOLUME UP key at the same time and then navigate to the Fastboot Mode by Volume UP button and and Click Volume Down button to select. Once you are in Fastboot Mode connect your Device to PC and go back to PC
6)Once Command Window is opened type following Command :-
Code:
fastboot devices
Code:
fastboot oem unlock
Code:
fastboot format userdata
Code:
fastboot flash recovery <Name of the Recovery in ur PC>
Code:
fastboot boot <Name of the Recovery in ur PC>
6) DONE ! STOCK RECOVERY IS FLASHED and Remember to keep Stock Recovery img file in the ADB AND FASTBOOT FOLDER

Thanks I'll try this asap currently on a train..

Okay.. I've shipped it to the customer care. They said I'll have to wait 3 days for it to get back. I'll report back then.
Thank you everyone for your input.

Closed as this has run its course.

brick ...

Hello, sorry advanced my English is not good I have a problem with my L-10 ... its brick .. I don't have access recovery and I have wiped the room . thanks you . (I am french).

Enter fastboot mode by holding "Volume down" & " Power" buttons while your cable is connected to the computer.
Make sure that the USB drivers for P7 L-10 are installed by installing HiSuite from official Huawei website.
Now download ADB and fastboot here https://www.androidfilehost.com/?fid=24521665358595410
Now you'll need 2 more things - Official P7-L10 ROM & Huawei update extractor which you can download here http://forum.xda-developers.com/attachment.php?attachmentid=3262545
Once you have all of those we can start the fun with the command line
Once you're in fastboot mode you'll have either green LOCKED screen or red UNLOCKED screen. You need to have a red screen in order to send commands to your phone from fastboot.
Open ADB & Fastboot and type "fastboot devices" (without quotes, always without quotes) - this will tell you if your device is properly detected, if it is, you'll see bunch of numbers and letters.
Now you'll need to extract a couple of .IMG files from your official ROM. This is how you do it. Your official ROM has 1 single file that's called UPDATE.APP. Open Huawei Update Extractor and open UPDATE.APP in it.
You should see a whole list with different .IMG files. You'll need to extract only a couple. BOOT.IMG - RECOVERY.IMG - CUST.IMG - SYSTEM.IMG
Now that you've extracted them all you'll need to start flashing them 1 by 1. This is how we do it
fastboot flash recovery RECOVERY.IMG
fastboot flash boot BOOT.IMG
fastboot flash cust CUST.IMG
fastboot flash system SYSTEM.IMG
You can drag and drop the IMG file into fastboot for your conveniance.
Now you need to place the actual ROM in the root of your SDcard.
On your SDcard make a folder called dload and put UPDATE.APP in it.
Now force update by turning off your phone and then power it back on while holding all 3 buttons pressed in. When screen comes on release Power button, but keep holding the other 2 buttons down.
Now your recovery should start wiping and installing the ROM and you should be saved
Let me know if you need more help

Milan-XDA said:
Enter fastboot mode by holding "Volume down" & " Power" buttons while your cable is connected to the computer.
Make sure that the USB drivers for P7 L-10 are installed by installing HiSuite from official Huawei website.
Now download ADB and fastboot here https://www.androidfilehost.com/?fid=24521665358595410
Now you'll need 2 more things - Official P7-L10 ROM & Huawei update extractor which you can download here http://forum.xda-developers.com/attachment.php?attachmentid=3262545
Once you have all of those we can start the fun with the command line
Once you're in fastboot mode you'll have either green LOCKED screen or red UNLOCKED screen. You need to have a red screen in order to send commands to your phone from fastboot.
Open ADB & Fastboot and type "fastboot devices" (without quotes, always without quotes) - this will tell you if your device is properly detected, if it is, you'll see bunch of numbers and letters.
Now you'll need to extract a couple of .IMG files from your official ROM. This is how you do it. Your official ROM has 1 single file that's called UPDATE.APP. Open Huawei Update Extractor and open UPDATE.APP in it.
You should see a whole list with different .IMG files. You'll need to extract only a couple. BOOT.IMG - RECOVERY.IMG - CUST.IMG - SYSTEM.IMG
Now that you've extracted them all you'll need to start flashing them 1 by 1. This is how we do it
fastboot flash recovery RECOVERY.IMG
fastboot flash boot BOOT.IMG
fastboot flash cust CUST.IMG
fastboot flash system SYSTEM.IMG
You can drag and drop the IMG file into fastboot for your conveniance.
Now you need to place the actual ROM in the root of your SDcard.
On your SDcard make a folder called dload and put UPDATE.APP in it.
Now force update by turning off your phone and then power it back on while holding all 3 buttons pressed in. When screen comes on release Power button, but keep holding the other 2 buttons down.
Now your recovery should start wiping and installing the ROM and you should be saved
Let me know if you need more help
Click to expand...
Click to collapse
I flashed all the images you named, and after that I can't enter in recovery. Tried flashing twrp, still can't enter. Tried with power + vol+, nothing, tried with stock power + vol+vol-, still nothing. And access bootloader I can only with usb connected. Tried from another update.app, same result. Phone unlocked.

RocketDoge said:
I flashed all the images you named, and after that I can't enter in recovery. Tried flashing twrp, still can't enter. Tried with power + vol+, nothing, tried with stock power + vol+vol-, still nothing. And access bootloader I can only with usb connected. Tried from another update.app, same result. Phone unlocked.
Click to expand...
Click to collapse
Just yesterday i bricked my phone too and i've spend 18 hours unbricking it, until i realised that the version of TWRP is directly related to the version of EMUI that's on your phone. As i was trying to install the old B126 with EMUI 2.3 i had to use TWRP 2.8.1.0. Once i installed it, i was able to enter into recovery and erase all data in orded to start over. Maybe you have the same problem.
EMUI 2.3 - TWRP 2.8.1.0
EMUI 3.0 - TWRP 2.8.7.0
EMUI 3.1 - TWRP 3.0.0.0
Try using TWRP that matches your EMUI version and let me know if it works for you

Milan-XDA said:
Just yesterday i bricked my phone too and i've spend 18 hours unbricking it, until i realised that the version of TWRP is directly related to the version of EMUI that's on your phone. As i was trying to install the old B126 with EMUI 2.3 i had to use TWRP 2.8.1.0. Once i installed it, i was able to enter into recovery and erase all data in orded to start over. Maybe you have the same problem.
EMUI 2.3 - TWRP 2.8.1.0
EMUI 3.0 - TWRP 2.8.7.0
EMUI 3.1 - TWRP 3.0.0.0
Try using TWRP that matches your EMUI version and let me know if it works for you
Click to expand...
Click to collapse
Well, somehow after posting I got working TWRP and got back to X-Rom, because for some reason, I can't install other custom ROM's, because of infinite bootloop. So I wanted to get back to stock firmware. So I tried all you steps and got bricked. For some reason, when I tried to install stock rom I got, "verifying install package" and after few seconds "FAIL". So I kinda stuck to one ROM

RocketDoge said:
Well, somehow after posting I got working TWRP and got back to X-Rom, because for some reason, I can't install other custom ROM's, because of infinite bootloop. So I wanted to get back to stock firmware. So I tried all you steps and got bricked. For some reason, when I tried to install stock rom I got, "verifying install package" and after few seconds "FAIL". So I kinda stuck to one ROM
Click to expand...
Click to collapse
I see that X-Rom is based on B125. Did you try flashing .IMG files from the same ROM or did you use some other?

Milan-XDA said:
I see that X-Rom is based on B125. Did you try flashing .IMG files from the same ROM or did you use some other?
Click to expand...
Click to collapse
I finnaly did it, week ago. I downloaded stock rom (don't remember which, but recovery started working). Then I just "forced update" with latest full rom. and now I have B852. :fingers-crossed:
My main problem was that stock recovery would not work, but I managed somehow to get it done and after that point it was all nice and clean. Thanks for helping out!

RocketDoge said:
I finnaly did it, week ago. I downloaded stock rom (don't remember which, but recovery started working). Then I just "forced update" with latest full rom. and now I have B852. :fingers-crossed:
My main problem was that stock recovery would not work, but I managed somehow to get it done and after that point it was all nice and clean. Thanks for helping out!
Click to expand...
Click to collapse
That's great news, I'm glad I could help. I'm rocking B852 too with TWRP 3.0.0.0 like a boss :highfive:

[Q] How to reflash a Stock Rom back after a soft brick?

Hi to everyone! Can anyone explain me how to reflash a Stock Rom (6.0.1 or 7.0) back after a soft brick? I mean, once I accidentially installed an OTA update over rooted Android 7 with TWRP recovery, so after restarting the phone got TWRP bootloop and did not enter in the fastboot mode. Tried to reflash a nandroid backup (ResurrectionRemix-M-v5.7.4-20160920-seed) and clean installation of the following Roms:
[TWRP] General Mobile 4G Android 6.0.1 MOB30Q Stock ROM
[TWRP]General Mobile 4G Android N 7.0 NRD90R Stock ROM
cm-13.0-20160930-UNOFFICIAL-seed
ResurrectionRemix-M-v5.7.4-20160920-seed
cm-14.0-20161003-UNOFFICIAL-seed
omni-7.0-20161017-seed-HOMEMADE
but none of them helped. Is there a workaround on making the phone enter in the fastboot mode? Or can I reflash Stock Recovery 6.0.1 MOB30Q or Stock Recovery 7.0 NRD90R via TWRP to get clean installation of the Android 6.01. or 7?

If you want to keep twrp in your phone i don't know how i can help you, but otherwise you could search the stock bootloader etc and then flash it via adb/fastboot in the commandprompt on your computer. After that reboot to bootloader and then flash the rest of the files.

snrfie said:
If you want to keep twrp in your phone i don't know how i can help you, but otherwise you could search the stock bootloader etc and then flash it via adb/fastboot in the commandprompt on your computer. After that reboot to bootloader and then flash the rest of the files.
Click to expand...
Click to collapse
The problem was - I could not enter into the adb/fastboot mode due to TWRP bootloop. That was a result of the OTA flashing over custom root and recovery. So I could neither recover my backup nor flash any custom or stock roms (flashing of custom or stock roms goes ok but restart results in TWRP bootloop).

I'm sorry, but i don't think i could help you with that. However with my huawei honor holly it was able to flash things if i removed the battery and disconnected it from the usb cable, then pressed volume down and power and put sptool in flashmode. When i connected it it would immediately start in fastboot mode but kind of basic. I don't know how to achieve immediate flashing after connecting to computer with adb/fastboot commands. Hope this helps.

snrfie said:
I'm sorry, but i don't think i could help you with that. However with my huawei honor holly it was able to flash things if i removed the battery and disconnected it from the usb cable, then pressed volume down and power and put sptool in flashmode. When i connected it it would immediately start in fastboot mode but kind of basic. I don't know how to achieve immediate flashing after connecting to computer with adb/fastboot commands. Hope this helps.
Click to expand...
Click to collapse
So, my experience in solving this problem was like this: I started Install MOB30Q.bat from images folder (starting INSTALL_Android N 7.0 September Update.exe could not help), got a message waiting for device and gave a reboot on the phone already connected to PC (in TWRP mode). Flashing process started with some errors, but the main thing - phone got flashed with a Stock Rom over the exisitng Custom one.
There is a workaround on a Russian forum but that's a quite complicated method requiring a modified USB cable.
The other way is to flash 5.1.1 Stock Rom as it is adviced on the same forum but that's a Swift stock rom so I did not risk.

you did not mention what your device is! am i correct to assume that it is a gm 4g android one? if it is, then search and download for a stock rom that is flashable via fastboot.
with your device, remove the battery to force it to switch off, assuming you still have a bootloop as you said. refit the battery and then switch the phone to fastboot mode by pressing vol-down+power on. the rest is already a standard process to flash the stock rom via fastboot. this procedure guarantees that everything in your phone is erased to be replaced by the stock rom you just flashed.

Hard Brick L-19

Hello guys
Need your help or ideas
So i Hard Bricked my P9 i can only enter fastboot.
Phone was on Android N first build,flashed it with TWRP,but i dint have stock app likes camera calculator e.t.c
Phone was working OK but i whanted to get original camera.
So there was made TWRP for android N, i flashed it TWRP worked system was booting, but TWRP not mounting /data, so there was tuto for fix that.
Need to flash zip -> repair /data -> resize ( thats was begining of problem )
zip was success, but format and repair was with error 4
system not booting anymore stuck on bootloop, with twrp.
Tried re-flash N with TWRP dint helped . Only lost TWRP
So i flashed L19C432B136 with dload. update was success, but I don't know why system wast booting, there was no orginal recovery i can't enter it or update with dload.
Stuck in screen "Phone is unlocked and can't be trusted"
Flashing TWRP for MM or N is success but phone don't enter IT
Flashing stock recovery from B136 dint helped ( i tried stock recovery from B322 ; no success)
Tried flashing SYSTEM.img BOOT.img RECOVERY.img from 322, all is sucess but phone not skipping screen ( Phone is unlocked and can't be trusted )
Any idea how to get phone back from dead?
I can only enter fastboot.
Is i possible to flash something true fastboot?
I have full updates of L19C432B182 and L19C432B161.

richish said:
Hello guys
Need your help or ideas
So i Hard Bricked my P9 i can only enter fastboot.
Phone was on Android N first build,flashed it with TWRP,but i dint have stock app likes camera calculator e.t.c
Phone was working OK but i whanted to get original camera.
So there was made TWRP for android N, i flashed it TWRP worked system was booting, but TWRP not mounting /data, so there was tuto for fix that.
Need to flash zip -> repair /data -> resize ( thats was begining of problem )
zip was success, but format and repair was with error 4
system not booting anymore stuck on bootloop, with twrp.
Tried re-flash N with TWRP dint helped . Only lost TWRP
So i flashed L19C432B136 with dload. update was success, but I don't know why system wast booting, there was no orginal recovery i can't enter it or update with dload.
Stuck in screen "Phone is unlocked and can't be trusted"
Flashing TWRP for MM or N is success but phone don't enter IT
Flashing stock recovery from B136 dint helped ( i tried stock recovery from B322 ; no success)
Tried flashing SYSTEM.img BOOT.img RECOVERY.img from 322, all is sucess but phone not skipping screen ( Phone is unlocked and can't be trusted )
Any idea how to get phone back from dead?
I can only enter fastboot.
Is i possible to flash something true fastboot?
I have full updates of L19C432B182 and L19C432B161.
Click to expand...
Click to collapse
You have 2 choices with this.
If you can still boot into TWRP,
1. Flash the Beta Update.zip
2. Power off phone.
3. Press up button whilst powering up phone.
4. You will now be in stock recovery and you can perform a factory reset.
5. the device will now boot in to N beta but will be missing the vendor apps.
There is another way to fix if this doesn't work. Tell me if this method works first.
Edit: I just read in the op that you flashed the update and had stock recovery.
The reason it won't boot is because you need to have b322 flashed and you have to factory reset to repair the corrupt file system. To do this follow these instructions.
1. You need to flash the Boot, Recovery and System images from b322 in fastboot.
2. Then enter stock recovery (Vol + and Power)
3. Then factory reset (this is essential as it repairs the file system and enables boot)
4. The device will then boot.
5. (Optional )If you want to go back from the beta you have to flash the rollback.app to b300 through th dload method first then you can flash a Android 6.0 through the dload method.
Regards
Lee

thel2dab said:
You have 2 choices with this.
If you can still boot into TWRP,
1. Flash the Beta Update.zip
2. Power off phone.
3. Press up button whilst powering up phone.
4. You will now be in stock recovery and you can perform a factory reset.
5. the device will now boot in to N beta but will be missing the vendor apps.
There is another way to fix if this doesn't work. Tell me if this method works first.
Regards
Lee
Click to expand...
Click to collapse
Cant Enter TWRP
noone of recoverys work

richish said:
Cant Enter TWRP
noone of recoverys work
Click to expand...
Click to collapse
Edited my previous post with another method.

thel2dab said:
Edited my previous post with another method.
Click to expand...
Click to collapse
fast qestion
there is 2 recoverys, does both need to be flashed?

@richish
If you get really stuck I can teamviewer your pc and help.
Or you can facebook message me direct.
I had exactly the same issue when I first tried to flash the properdatafix with TWRP for N
Regards
---------- Post added at 10:26 PM ---------- Previous post was at 10:24 PM ----------
richish said:
fast qestion
there is 2 recoverys, does both need to be flashed?
Click to expand...
Click to collapse
You can flash both.
fastboot flash recovery recovery.img
fastboot flash recovery2 recovery2.img
I don't think it is essential but it won't hurt to do it anyway.
---------- Post added at 10:35 PM ---------- Previous post was at 10:26 PM ----------
[/COLOR @richish
I seen you PM. I am not sure it will wok by flashing B182. I think you have to flash B322 first.
Regards

fist you have to flash stock recovery from emui 5(android N) through fastboot.
second , download the rollback package,extract it and put it on dload folder of external storage.
third, turn off the phone , and press vol up + vol down + power button together to enter forced update mode.
if it is successful system will boot and you should flash android M firmware using dload method then u should unlock bootloader,install twrp,wipe /system /cache /data and then flash update.zip(android N) and hw_data of your firmware one after another.
i hope this help you.

still phone is not booting
I redownload b322, extracted Boot.img System.img Recovery.img Recovery2.img and Cust.img with
http://forum.xda-developers.com/showthread.php?t=2433454 Update Extractor
Flashed all .img true fastboot
But still nothing
Stuck on bootloader screen "Your device is unlocked, and can't be trusted"
Maybe i need flash some more images from b322.
Its look like phone cant pass bootloader.
Any sugestions?
P.S. Phone still have warranty, but booloader is unlocked
and fastboot oem relock ************** ends with failed.
"Failed - root cant trusted"
Sugestions how to lock it?

I had my phone bricked from testing cm, and going back to stock. My solution was to flash dload and recovery from the 182, followed by dload flash of 182.

@richish
caution : these commands will format the partition
can u use these command ?
"fastboot format /system"
"fastboot format /data"
or "fastboot erase /system"=> this will erase system partition

Phone is live now.
I downloaded DC-Phoenix and bought 15 credits
flashed stock B182 via DC-phoenix and phone booted.
I recomand this apllication for everybody who have similar problems.
THX for everybody who helpped.

richish said:
Phone is live now.
I downloaded DC-Phoenix and bought 15 credits
flashed stock B182 via DC-phoenix and phone booted.
I recomand this apllication for everybody who have similar problems.
THX for everybody who helpped.
Click to expand...
Click to collapse
How can i sign up for an account, it alway said wrong username or password !:crying:

DC-Phoenix is not cheap but it also cured my phone after bricking it with flashfire where all other methods did not work.
if you use it follow the instructions carefully and do the 2 step flashing although it will work after the first one. if you don`t do the second flash the partition sizes are wrong and a dload update will fail.

smartmobee said:
How can i sign up for an account, it alway said wrong username or password !:crying:
Click to expand...
Click to collapse
First u must buy credits, activate your account in email and then login in aplication.

Hi everyone
I would like to share the problem that i am having with my p9 , so maybe i can get your help.
Firstly i had L19C185 version and i changed Oeminfo in order to install c636 Beta 7.0 Nougat.
I installed the nougat but then realized that i dont have stock apps in my phone, so by mistakely tried to install TWRP for 6.0 Marshmallow and my problem started here.
Now my phone can not boot. its stuck in Phone is booting now ( the screen when you unlock bootloader after huawei logo) , and its never booting. it stays like that.
I tried to flash rboot.img , recovery.img and System.Img from fast boot. but whenever im trying to flash system.img after boot and recovery.img, a get an error and never succeeded to flash system.img. Im trying to flash these .img files from L19C636b180.
Can you please help me or give me some advice because none of mobile services couldnt fix and flash new software. maybe because they dont know exactly what should they do. and in my country i couldnt find anyofficial huawei service provider.
Please help me how to fix my phone.

I also had serious problems with flashing the thing back to stock.
TWRP was broken too for me.
I've done that to fix it all
The ONLY way that worked for me was
1. Download EVA-L19C636B168 from here http://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586
2. Download that SRK tool http://forum.xda-developers.com/p9/development/tool-srk-tool-huawei-bootloader-root-t3374068
3. Flash the recovery from the SRK tool, you can do that with the tool or directly via fastboot (i don't know other proper source for the correct recovery img)
4. Put the image EVA-L19C636B168 (UPDATE.app) in the "dload" folder of your sd card
5. Start phone in dload mode (Hold all 3 buttons at start) and let the update do it's job

What about recovery??? Does 3 button combination works? Whats heppens if u hold volup and power button when turning phone on!
Situation looks similar what i had.
Only solution for me was dc-phoenix.
U have tu buy 15 points to flash phone (15eur) But it works.
I'm 99% sure that there are bootloader comands what is same as for dc-phoenix,but i dont know them.
Sent from my EVA-L19 using XDA-Developers mobile app

please help
i had bricked my p9 L09 twrp not working noting working only fastboot mode is working plzzz help me in finding boot.img recovery.img system.img

TWRP and slots - I'm really confused now

I'm a long time user of custom roms. I've bricked and subsequently rescued more android phones than I can remember and I always managed to get myself out of trouble before. But, I've been away from them for a while and I never had a phone with this dual slot setup before, and I'm stumped with this one
Before I start with the real issue, can I ask what the purpose of two slots is? Is it for dual booting, or something to do with the dual sims??
So, I'm on Lineageos. When I first flashed it I used the lineageos recovery. Now I would like TWRP permanently installed but can't get it to stick.
I've flashed the rom, and TWRP, so many times now. It's been a mess. My rom is working so no panic but if I go into recovery I'm back on the lineageos recovery and the text is too tiny to read (it wasn't like that when I used it before - the text was big).
Anyway, about half an hour ago I flashed the TWRP image in fastboot mode.
Then started twrp and copied the twrp zip over to the phone.
Then I flashed the zip and it flashed to both slots.
Then I couldn't get into my rom. It seemed to overwrite the boot.
So then I reflashed lineage and my rom is back and working fine, but I have the lineageos recovery again.
I thought that with TWRP in both slots, and me then flashing the rom, that the rom would only use one slot and TWRP would remain in the other and would be accessed when I boot to recovery.
Another thing. In fastboot mode (or the bootloader I should say) I have a black screen. The only feedback I get is from the terminal window on my linux computer. I can't see **** on the phone.

buachaille said:
I'm a long time user of custom roms. I've bricked and subsequently rescued more android phones than I can remember and I always managed to get myself out of trouble before. But, I've been away from them for a while and I never had a phone with this dual slot setup before, and I'm stumped with this one
Before I start with the real issue, can I ask what the purpose of two slots is? Is it for dual booting, or something to do with the dual sims??
So, I'm on Lineageos. When I first flashed it I used the lineageos recovery. Now I would like TWRP permanently installed but can't get it to stick.
I've flashed the rom, and TWRP, so many times now. It's been a mess. My rom is working so no panic but if I go into recovery I'm back on the lineageos recovery and the text is too tiny to read (it wasn't like that when I used it before - the text was big).
Anyway, about half an hour ago I flashed the TWRP image in fastboot mode.
Then started twrp and copied the twrp zip over to the phone.
Then I flashed the zip and it flashed to both slots.
Then I couldn't get into my rom. It seemed to overwrite the boot.
So then I reflashed lineage and my rom is back and working fine, but I have the lineageos recovery again.
I thought that with TWRP in both slots, and me then flashing the rom, that the rom would only use one slot and TWRP would remain in the other and would be accessed when I boot to recovery.
Another thing. In fastboot mode (or the bootloader I should say) I have a black screen. The only feedback I get is from the terminal window on my linux computer. I can't see **** on the phone.
Click to expand...
Click to collapse
1. Don't use lineage official because many users have had different problems. Use the unofficial one from the Telegram chat
2. The reason for the two slots is for updating your stock ROM without any risk of bricking
*When you get a stock update the system flashes it to the dormant slot ..if it bricks it boots back to active slot ...if it boots fine you switch slots and your dormant becomes your active .So you have a duplicate of all partitions but only one data partition ..so regardless of which slot you're using your data is there ..(+ and importantly doesn't get wiped ) so the concept is/was that you can flash stuff without bricking nor losing any data
3.The concept is simple : *usually because not always* your recovery flashes a rom or update to the slot you are not using ... But be careful .. ANYTHING ELSE like magisk or gapps or whatever gets flashed to the active slot ..so after flashing your ROM you need to change to the other slot in recovery then continue flashing gapps and magisk there ...so
SLOT A - flash ROM zip to B
*Reboot to slot B RECOVERY
SLOT B - flash gapps & magisk
___BOOT TO NEW ROM
*YOU ARE NOW USING SLOT B
#your old rom is still sleeping in slot A
In emergency you could go back there
4. Recovery ...this and other A/B devices and even other devices dont have a recovery partition ..so the recovery is inside the boot partition or recovery_ramdisk partition...which yes gets overwritten when flashing a new ROM or kernel etc
_the solution is easy_
Flash recovery back in recovery after flashing a custom ROM
*Some have twrp included and it gets flashed automatically
5. The not booting with recovery must have something to do with either bugs in the rom you are using or an old or bugged recovery or encryption/secure boot data problem ...either way you need to try different roms and recoveries and kernels - magisk combos
#see 7 # maybe you can't boot cos ARB 4 needs custom kernel on pie roms to boot
6. The black screen in fastboot is not a good sign ...sounds like your device got converted from Android 1 to MIUI and it triggered ARB 4
fastboot getvar anti
7. YOU CAN READ UP ON THAT ..all this info is available for our device in this forum and this is very lazy of you and I shouldn't be spoon feeding you .
***You can always sideload or backup sideways
fastboot boot recovery.img
*Go to advanced tab activate adb sideload
adb sideload "filename"
*File must be in adb folder

KevMetal said:
1. Don't use lineage official because many users have had different problems. Use the unofficial one from the Telegram chat
2. The reason for the two slots is for updating your stock ROM without any risk of bricking
*When you get a stock update the system flashes it to the dormant slot ..if it bricks it boots back to active slot ...if it boots fine you switch slots and your dormant becomes your active .So you have a duplicate of all partitions but only one data partition ..so regardless of which slot you're using your data is there ..(+ and importantly doesn't get wiped ) so the concept is/was that you can flash stuff without bricking nor losing any data
3.The concept is simple : *usually because not always* your recovery flashes a rom or update to the slot you are not using ... But be careful .. ANYTHING ELSE like magisk or gapps or whatever gets flashed to the active slot ..so after flashing your ROM you need to change to the other slot in recovery then continue flashing gapps and magisk there ...so
SLOT A - flash ROM zip to B
*Reboot to slot B RECOVERY
SLOT B - flash gapps & magisk
___BOOT TO NEW ROM
*YOU ARE NOW USING SLOT B
#your old rom is still sleeping in slot A
In emergency you could go back there
4. Recovery ...this and other A/B devices and even other devices dont have a recovery partition ..so the recovery is inside the boot partition or recovery_ramdisk partition...which yes gets overwritten when flashing a new ROM or kernel etc
_the solution is easy_
Flash recovery back in recovery after flashing a custom ROM
*Some have twrp included and it gets flashed automatically
5. The not booting with recovery must have something to do with either bugs in the rom you are using or an old or bugged recovery or encryption/secure boot data problem ...either way you need to try different roms and recoveries and kernels - magisk combos
#see 7 # maybe you can't boot cos ARB 4 needs custom kernel on pie roms to boot
6. The black screen in fastboot is not a good sign ...sounds like your device got converted from Android 1 to MIUI and it triggered ARB 4
fastboot getvar anti
7. YOU CAN READ UP ON THAT ..all this info is available for our device in this forum and this is very lazy of you and I shouldn't be spoon feeding you .
***You can always sideload or backup sideways
fastboot boot recovery.img
*Go to advanced tab activate adb sideload
adb sideload "filename"
*File must be in adb folder
Click to expand...
Click to collapse
Thanks. I really appreciate your detailed reply. Sorry I didn't answer sooner. I've been unbelievably busy with work and other things and only just logged into XDA again 10 minute ago.
Yes I know it's lazy of me, BUT, a problem I always have with information on roms is that there is so much contradictory information. One post contradicts another a lot of the time, often because methods change over time. Anyway, this leads to me doing the wrong thing and bricking my phones
Thanks again :good:

I got to this link from telegram chat after searching it up. Is this where you are saying I should get Lineageos?
https://github.com/LineageOS

buachaille said:
I got to this link from telegram chat after searching it up. Is this where you are saying I should get Lineageos?
https://github.com/LineageOS
Click to expand...
Click to collapse
https://sourceforge.net/projects/shoukolate-los17-1-builds/files/jasmine_sprout/

KevMetal said:
https://sourceforge.net/projects/shoukolate-los17-1-builds/files/jasmine_sprout/
Click to expand...
Click to collapse
Thanks. Once I get TWRP to stick I will flash this.

buachaille said:
Thanks. Once I get TWRP to stick I will flash this.
Click to expand...
Click to collapse
Sure . It will be easy . Put magisk and twrp.zip and gapps on your PC .
Put recovery.img in the adb folder
1. Connect phone to pc in normal mode and enable adb
2. Open adb and authorize device
3. Adb reboot bootloader
4. Fastboot boot recovery.img
5. Transfer recovery.zip to phone internal
6. Wipe - flash zip - format data - reboot recovery - transfer lineage ROM to phone - flash - flash recovery.zip - format data - reboot to the INACTIVE slot in reboot section ..then choose reboot recovery - flash gapps and magisk - reboot to lineage ...then recovery should be stuck
*If you wanna keep data back it up when you boot recovery first time
**Restore it after all the steps
***Recovery will only stick if you do the data formatting
Use this recovery:
https://drive.google.com/drive/mobile/folders/1NRlv58EiQ_YlMjrpLYKzOqIob2Vq3kYE

I'm on linux but I don't think that makes any difference here.
I've got the fastboot screen fixed. I downloaded and flashed the stock MI image. So I'm pleased with that.
I've flashed 3 different versions of TWRP. 3.4.0.0 and a couple of older ones. 3.4.0.0 gives me the TWRP screen but doesn't actually load into TWRP. With the other I get a black screen. Trying as we speak to fix.
I believe I have the command correct - sudo fastboot boot twrp-3.4.0-0-jasmine_sprout.img
<<edit>> This one worked ------ twrp-3.3.0-0-jasmine_sprout.img
In TWRP now and following your instructions. Would be done by now but rom taking ages to download. Anyway, thanks. I'll post back once I'm done and let you know what happened.

I owe you a post to let you know what happened. It took me hours and hours but it's finally done. I now have the following:
Bootloader image showing as it should (fixed this by using the MI flash tool and restoring a stock rom.
TWRP is installed and hasn't disappeared. I had a hard time with TWRP. The older version, that was the only one I could get to boot up initially, refused to flash a rom. I tried the Lineageos unofficial and the official, but no way. So I used TWRP, to flash the newest version of TWRP, and then it worked.
Lineageos unofficial is installed and rooted with Magisk.
Your list of instructions (quoted below) was extremely useful and I wouldn't have managed with it. Many thanks :good:
Put recovery.img in the adb folder
1. Connect phone to pc in normal mode and enable adb
2. Open adb and authorize device
3. Adb reboot bootloader
4. Fastboot boot recovery.img
5. Transfer recovery.zip to phone internal
6. Wipe - flash zip - format data - reboot recovery - transfer lineage ROM to phone - flash - flash recovery.zip - format data - reboot to the INACTIVE slot in reboot section ..then choose reboot recovery - flash gapps and magisk - reboot to lineage ...then recovery should be stuck
*If you wanna keep data back it up when you boot recovery first time
**Restore it after all the steps
***Recovery will only stick if you do the data formatting
Click to expand...
Click to collapse
I would say that flashing roms has become more complicated during the time I've been away. I think the last phone I used a custom rom on was my Galaxy S5. I can't believe how hard a time I had getting this to work.

buachaille said:
I owe you a post to let you know what happened. It took me hours and hours but it's finally done. I now have the following:
Bootloader image showing as it should (fixed this by using the MI flash tool and restoring a stock rom.
TWRP is installed and hasn't disappeared. I had a hard time with TWRP. The older version, that was the only one I could get to boot up initially, refused to flash a rom. I tried the Lineageos unofficial and the official, but no way. So I used TWRP, to flash the newest version of TWRP, and then it worked.
Lineageos unofficial is installed and rooted with Magisk.
Your list of instructions (quoted below) was extremely useful and I wouldn't have managed with it. Many thanks :good:
I would say that flashing roms has become more complicated during the time I've been away. I think the last phone I used a custom rom on was my Galaxy S5. I can't believe how hard a time I had getting this to work.
Click to expand...
Click to collapse
No yes I understand I had to pick up all what was discussed by trial and error.
Therr are two big changes ..more security measures ...more complicated workarounds.
But the A/B thing is a mission. I converted my phone completely and repartitioned it to A only . Now it has a dedicated recovery partition. And I have an extra 4GB of space .
By the way .Please remember you will need to reflash the twrp zip after every ROM if you don't want to lose it.

KevMetal said:
No yes I understand I had to pick up all what was discussed by trial and error.
Therr are two big changes ..more security measures ...more complicated workarounds.
But the A/B thing is a mission. I converted my phone completely and repartitioned it to A only . Now it has a dedicated recovery partition. And I have an extra 4GB of space .
By the way .Please remember you will need to reflash the twrp zip after every ROM if you don't want to lose it.
Click to expand...
Click to collapse
Thanks for the reminder about reflashing TWRP. I will keep that in mind. I shouldn't be reflashing much now though. I hope I got that out my system last time. I was always changing roms - constantly.
I mainly wanted TWRP installed as I remember sometimes my roms would just go into a bootloop for no reason that I could discover, and I'd need my TWRP backups.
How do you re-partition a Xiaomi. With the MI flash tool? I'm guessing that as I remember I had to do that once with Odin (I always had Samsung phones back then). I was forced to do it as I had bricked my phone much MUCH more seriously than usual. Got it fixed though
I still am quite confused with the A/B thing, but I'll pick it up as I go along I'm sure. For now I'm happy. Rom working fine so I can get on with other things in life.
And thanks again - you totally got me out of the **** :good::good: