This Thread Is For Them Who Bricked There Phones
Don't start a new thread for your bricked phone & post here.
We will help you with every possible solutions.
Here are some quick tips :
(Here I'll use the terms like Download-Mode & Recovery-Mode, If you dont know what are they then:
Download mode is for flashing radio firmware/ROM upgrade through official means.
As for Download mode, for example ODIN is commonly used on Samsung devices to flash ROMs, those devices needs to be in download mode prior to flashing. However, ODIN is not the official way to do it, rather Kies, is the official route in upgrading the firmware, this is for Samsung devices for example.
In Android, recovery refers to the dedicated, bootable partition that has the recovery console installed. A combination of key presses (or instructions from a command line) will boot your phone to recovery, where you can find tools to help repair (recover) your installation as well as install official OS updates. Because Android is open and has the recovery source code available, building a customized version with more and different options is relatively easy as well. Let's look at both options.
The stock recovery is pretty limited, but that's by design. Its main purpose is to delete all user data and files, or to perform system updates. Normally, both these operations are started from the running Android system, or you can do things manually and boot right into recovery yourself. When you tell your phone to do a factory reset, recovery is what boots up and erases the files and data. Likewise with updates -- when we restart to install an official OS update, it's done in recovery. Recovery is also where we go to manually install official OS updates we've downloaded from the Internet.
.
A Bricked Phone May Have One or More (Below Problems) :
1. Booting to the ROM(Android) not possible.
2. Booting to the Recovery-Mode not possible.
3. Black screen or Bootloop(Repeated Restarting of Phone at Boot Animation or Samsung Galaxy Y Logo).
Possible Solutions :
(Remember there'll be data loss using these solutions so always try to keep a backup)
1. If you can still enter into Recovery-Mode
(a). Try to clear Data & Cache then check.
(b). Try Installing a Custom ROM using CWM (ClockWorkMod Recovery) & check.
2. If Recovery-Mode didn't helped Enter into Download-Mode & flash an odin supported stock rom.
*You can inform me, if anything left out.
Note :
1. I'll be not held responsible for anything that happens to your phone.
2. Before posting try to search for similar type problems out there & try the solution, if that doesn't solve your problem then post here.
Related
Hi all,
I'm trying to install Cyanogenmod following techbeasts.com tutorial but I'm stuck at the first step : installingTWRP (or CWM).
I followed precisely all the instructions (I allow debugging mode, I installed samsung drivers, I start the phone in download mode, I connect it with OEM cable, I start Odin, it sees the phone, I select the tar.md5 file.), Odin confirms it went well (green box writing "PASS"), but when I try to boot the recovery mode by holding Volume up + Home + Power it seems to boot another recovery software that doesn't offer a backup or a flashing options: "Android system recovery <3e>"
Can't get it to run TWRP or CWM... Can't install the supersu package.
What I'm I doing wrong? Can someone help?
Try to untick Auto Reboot option from odin. I had similiar issues and reason was if you have updated your phone with OTA-updates then it installs some kind of backup script. When your phone boots again after you had installed twrp it installs stock recovery during boot. So untick autoreboot, flash twrp and force boot straight to recovery without letting phone boot to OS. You can also try to pull battery out, put it back and then boot into recovery mode.
Sorry my english and try to understand.
adbhitman said:
Try to untick Auto Reboot option from odin. I had similiar issues and reason was if you have updated your phone with OTA-updates then it installs some kind of backup script. When your phone boots again after you had installed twrp it installs stock recovery during boot. So untick autoreboot, flash twrp and force boot straight to recovery without letting phone boot to OS. You can also try to pull battery out, put it back and then boot into recovery mode.
Sorry my english and try to understand.
Click to expand...
Click to collapse
Great it worked, thanks a lot !
But now I'm stuck on the next step : flashing CM11
I rooted my phone, booted TWRP, chose "install>cm11" (the zip downloaded from nova fusion) but it says "failed" after a few sec...
I would post my TWRP log but the forum prevents me doing so...
Well I get few things that you could check first.
1. Do factory reset for example from twrp. Factory reset is needed/recommended before installing custom rom from offical OS.
2. Sometimes just installing fails almost immediately if you have ticked check zip signature.
After you have installed new rom clear cache and davilk cache just in case. I'll do that every time if I install or update custom roms. Also don't forget to install right gapps package after you have installed rom.
Sorry my english and try to understand.
ok just realized i downloaded the wrong cm image (the odin one, not the recovery)
everything running smooth now
Okay happy to hear that everything is fine now. Happy playing with custom roms
Ever since google rolled out the marshmallow update I have been plagued with battery issues to an extent where it was dropping to half from a full charge within a day even on standby . Having looked at many fixes on this forum which including rooting and replacing the kernel or simply turning core features like wifi off.For some users it may be tedious and it may risk bricking their device . So I decided to go back to stock 5.1.1 until google fixes the battery issues.
Before Proceeding Backup Your Data.
Follow the steps below to roll back to stock 5.1.1 along with stock recovery.
1) Download the Android One Toolkit http://forum.xda-developers.com/cro...oolbox-android-one-toolkit-one-click-t3030165.
2) Download 5.1 OTA update from here : http://forum.xda-developers.com/cro...l/ota-micromax-official-ota-captured-t3058879
3) Download 5.1.1 OTA update from here: http://forum.xda-developers.com/cro...al/ota-canvas-a1-5-1-1-captured-link-t3121543
4) Place both the OTA zips in root of SD CARD.Note the names of both versions.
5) Open Android One Toolkit.Enable USB Debugging . Unlock the Bootloader.
6) Install CWM Recovery from the Toolkit.
7) Reboot to Recovery.
8) Make a full backup of your existing ROM in case something goes wrong.
9) Erase Data , Cache & Dalvik Cache.
10) Select install zip from ext-sd card select the 5.1 OTA zip.
11) After completion reboot your phone. Update will also replace CWM with stock recovery ( No Worries)
12) Keep Wifi Off & Data connection off to prevent marshmallow being downloaded again during Setup . Setup your device Offline.
13) Reboot to stock recovery using key combo Power + Volume Up.If you get "No command" in stock recovery continue pressing Power+Volume Up until menu appears.
14) Select Update from SD Card . Select 5.1.1 OTA zip.
15) Reboot phone and you will now be on 5.1.1. Along with Stock Recovery.
16)Once Data or Wifi is enabled you may get update prompts of Marshmallow in notification. Disable update notification by long pressing on notification and goto settings from there you can disable it.
17) You may Relock Bootloader if You Wish from toolkit
Disclaimer:
I Am Not Responsible For Any Damage Caused To your Phone.
Credits to:
@anil293 for his toolkit
@varun.chitre15 For His Recoveries
@ghpranav & @GokulNC for OTA links.
Draining continues
Can't go to CWM even I unlocked bootloader I flash ed CWM but still on NO COMMAND
ranj9660 said:
Can't go to CWM even I unlocked bootloader I flash ed CWM but still on NO COMMAND
Click to expand...
Click to collapse
FIrst check in android toolkit in list devices if your device is mentioned.
After flashing CWM boot straight to recovery. Booting to OS may cause the recovery to be overwritten by STOCK recovery.
Yeah my device
My device mentioned too . I clicked list devices and I got device id then only I unlocked bootloader and installed custom recovery also but I can't enter to customer recovery ?
ranj9660 said:
My device mentioned too . I clicked list devices and I got device id then only I unlocked bootloader and installed custom recovery also but I can't enter to customer recovery
Click to expand...
Click to collapse
After installing CWM from toolkit don't restart to OS. Press Power+Volume Up until recovery select option appears.
But now
(First i have to thank you to giving me the instruction now its worked) Doesn't show zip files. What to do? I wiped dalvik cache, data and cache partition but doesn't show zip file ? got another problem
Can I use Twrp?
What's wrong using TWRP instead of CWM? I do not have windows. I have Linux(Ubuntu). From linux I can flash anything. But the problem is I don't have the latest recovery image of CWM for Android one devices. (The CWM project has been abandoned anyway).
My only concern is to get back the stock recovery after flashing 5.1.
The process you told to revert back to Lollipop after Marshmallow update, have u done that, are u succeeded.
Please tell me, because after Marshmallow update i got a severe battery drain and over heat in My Spice Dream Uno MI-498.
When my phone is in ideal it is okay but when i started using it then the issue started.
After revert back to Lollipop according to your process is there any IMEI problem.
Is it possible after flashing the ROM in Custom Recovery can it revert back to Stock Recovery.
androidone14 said:
The process you told to revert back to Lollipop after Marshmallow update, have u done that, are u succeeded.
Please tell me, because after Marshmallow update i got a severe battery drain and over heat in My Spice Dream Uno MI-498.
When my phone is in ideal it is okay but when i started using it then the issue started.
After revert back to Lollipop according to your process is there any IMEI problem.
Is it possible after flashing the ROM in Custom Recovery can it revert back to Stock Recovery.
Click to expand...
Click to collapse
Just flash away the STOCK ROM and you'll get everything STOCK
---------- Post added 5th November 2015 at 00:06 ---------- Previous post was 4th November 2015 at 23:57 ----------
ranj9660 said:
(First i have to thank you to giving me the instruction now its worked) Doesn't show zip files. What to do? I wiped dalvik cache, data and cache partition but doesn't show zip file �� got another problem
Click to expand...
Click to collapse
Please give more details or send a pic of what is going wrong for you. You have to put the zip file in your external card and flash from install from external SD card if that's what you are asking for.
wickedspice said:
Ever since google rolled out the marshmallow update I have been plagued with battery issues to an extent where it was dropping to half from a full charge within a day even on standby . Having looked at many fixes on this forum which including rooting and replacing the kernel or simply turning core features like wifi off.For some users it may be tedious and it may risk bricking their device . So I decided to go back to stock 5.1.1 until google fixes the battery issues.
Before Proceeding Backup Your Data.
Follow the steps below to roll back to stock 5.1.1 along with stock recovery.
1) Download the Android One Toolkit http://forum.xda-developers.com/cro...oolbox-android-one-toolkit-one-click-t3030165.
2) Download 5.1 OTA update from here : http://forum.xda-developers.com/cro...l/ota-micromax-official-ota-captured-t3058879
3) Download 5.1.1 OTA update from here: http://forum.xda-developers.com/cro...al/ota-canvas-a1-5-1-1-captured-link-t3121543
4) Place both the OTA zips in root of SD CARD.Note the names of both versions.
5) Open Android One Toolkit.Enable USB Debugging . Unlock the Bootloader.
6) Install CWM Recovery from the Toolkit.
7) Reboot to Recovery.
8) Make a full backup of your existing ROM in case something goes wrong.
9) Erase Data , Cache & Dalvik Cache.
10) Select install zip from ext-sd card select the 5.1 OTA zip.
11) After completion reboot your phone. Update will also replace CWM with stock recovery ( No Worries)
12) Keep Wifi Off & Data connection off to prevent marshmallow being downloaded again during Setup . Setup your device Offline.
13) Reboot to stock recovery using key combo Power + Volume Up.If you get "No command" in stock recovery continue pressing Power+Volume Up until menu appears.
14) Select Update from SD Card . Select 5.1.1 OTA zip.
15) Reboot phone and you will now be on 5.1.1. Along with Stock Recovery.
16)Once Data or Wifi is enabled you may get update prompts of Marshmallow in notification. Disable update notification by long pressing on notification and goto settings from there you can disable it.
17) You may Relock Bootloader if You Wish from toolkit
Disclaimer:
I Am Not Responsible For Any Damage Caused To your Phone.
Credits to:
@anil293 for his toolkit
@varun.chitre15 For His Recoveries
@ghpranav & @GokulNC for OTA links.
Click to expand...
Click to collapse
Thanks!!!
But is there any way to roll back without rooting the phone.
i don't want to my phone now.
anupamdubey said:
Thanks!!!
But is there any way to roll back without rooting the phone.
i don't want to my phone now.
Click to expand...
Click to collapse
Downgrade is possible only through unlocking bootloader and then flashing custom recovery which shall help you flash the LP firmware.
Rooting has nothing to do with this.
wickedspice said:
After installing CWM from toolkit don't restart to OS. Press Power+Volume Up until recovery select option appears.
Click to expand...
Click to collapse
it gets rebooted automatically after flashing cwm recovery but still no command.
stan1996 said:
it gets rebooted automatically after flashing cwm recovery but still no command.
Click to expand...
Click to collapse
Yes , thats the tricky part as os tries to restore stock recovery on boot. Here's what you need to do. On your computer when the toolkit prompt says " completed /finished" prevent rebooting by quickly pressing power+volume up. Once you get the selection prompt select recovery by volume up and confirm selection by volume down.
You have to do this only once , After you successfully boot to cwm it will prevent os from re writing recovery
wickedspice said:
Yes , thats the tricky part as os tries to restore stock recovery on boot. Here's what you need to do. On your computer when the toolkit prompt says " completed /finished" prevent rebooting by quickly pressing power+volume up. Once you get the selection prompt select recovery by volume up and confirm selection by volume down.
You have to do this only once , After you successfully boot to cwm it will prevent os from re writing recovery
Click to expand...
Click to collapse
thank you so much:angel::angel::angel:
I am getting stuck on unlock bootloader, it freezes and does nothing ? any ideas guys ? I really need to get away from marshmallow, hot phone, no 4g etc etc
Hi
The device is Samsung Galaxy Tab S2 8.0 SM-T713.
Following is what happened:
1. Installed TWRP and then Installed Lightning ROM v1.0.
2. Restarted the tablet without turning on OEM Unlock.
3. Did not boot by giving error "custom binary blocked by frp lock"
4. Tried installing stock firmware with odin. Firmware installs successfully but when the tablet reboots, it keep showing the glowing samsung logo.
5. Tried multiple different firmwares and eventually tried the latest firmware for the XAR region. Now only that firmware can be installed and all other older firmwares fail in the installation step giving the error "sw rev check fail aboot fused 2 binary 1"
Would really appreciate if anyone could help.
I assume that flashing pit file with the latest XAR region firmware will help boot the tablet but i cannot find the pit file to use.
Please HELP!
I think your problem is the result of flashing TWRP prior to flashing the stock ROM via Odin. Try this. Do a full wipe via TWRP. Then instead of booting into TWRP and then selecting "download" to use Odin, boot directly into download mode by holding Home, Vol down and power. Then flash the stock ROM. This should not only allow you to boot, but should also replace TWRP with the stock recovery. If it still doesn't boot, you should be able to use the stock recovery to perform a full wipe and again try Odin to install stock. But until you get the stock ROM to boot, trying any other ROM is useless.
lewmur said:
I think your problem is the result of flashing TWRP prior to flashing the stock ROM via Odin. Try this. Do a full wipe via TWRP. Then instead of booting into TWRP and then selecting "download" to use Odin, boot directly into download mode by holding Home, Vol down and power. Then flash the stock ROM. This should not only allow you to boot, but should also replace TWRP with the stock recovery. If it still doesn't boot, you should be able to use the stock recovery to perform a full wipe and again try Odin to install stock. But until you get the stock ROM to boot, trying any other ROM is useless.
Click to expand...
Click to collapse
The problem is that the TWRP recovery is long gone. Its not on the tablet anymore. I cannot flash TWRP because of FRP lock. I can access stock recovery but it also does not allow me to wipe data and factory reset due to FRP lock.
Any other suggestions.
I was able to finally restore the device using the method described in a sammobile forum.
Look at the second post on the thread titled " SmartSwitch: Install & update or replace firmware".
It is a tutorial to reinitialize the device to factory settings using Samsung Smart Switch software.
rafayzq said:
I was able to finally restore the device using the method described in a sammobile forum.
Look at the second post on the thread titled " SmartSwitch: Install & update or replace firmware".
It is a tutorial to reinitialize the device to factory settings using Samsung Smart Switch software.
Click to expand...
Click to collapse
I can't find that thread in the Sammobile forum but just googling "FRP lock" brings up a bunch of You Tube videos on how to remove the lock. Personally, I've never run into the problem.
I didn't realize from the OP that getting the stock ROM back was due to the lock but rather that the tablet was stuck at the Samsung logo rather that where you are asked for the Google login info.
Just so I've got it right and others understand, before you attempted to install a new ROM, was there an option in settings that would have allowed you to turn off using the lock and thereby have avoided the problem?
lewmur said:
I can't find that thread in the Sammobile forum but just googling "FRP lock" brings up a bunch of You Tube videos on how to remove the lock. Personally, I've never run into the problem.
I didn't realize from the OP that getting the stock ROM back was due to the lock but rather that the tablet was stuck at the Samsung logo rather that where you are asked for the Google login info.
Just so I've got it right and others understand, before you attempted to install a new ROM, was there an option in settings that would have allowed you to turn off using the lock and thereby have avoided the problem?
Click to expand...
Click to collapse
All the problems started when i restarted the tablet running a custom rom without enabling the OEM Unlock option in Developer Options in settings.
The lesson i learned the hard way is that you should always keep the OEM Unlock enabled
Hello friends, I've been trying to fix a giant problem with my son's cell phone for three days ... He asked me to rotate it, but I brickee it, I comment on what happens and what I did:
specs:
Glaxy A6 + (SM-A605GN)
1-install TWRP by ODIN (Correct installation)
2-Install TWRP files "force_encryption_disabler, RMM State Bypass and non-verity-opt-encrypt (I think here is my mistake, since I do not know the functions of these files, in my time of Flasheo does not exist) I take it out of this tutorial: androidinfotech.com/root-samsung-galaxy-a6-plus-2018-sm-a605f-fn-gn-pie/[/url])
Error 3-First; I didn't have access to the internal memory in the TWRP, so I followed this tutorial youtube.com/watch?v=bqyVQCGlyqs[/url]) to change the partition system so I could access the internal memory correctly
4- Install the Magisk correctly through the TWRP
5- Restart (And my hell began) ...
a- TWRP informs me that I did not have OS installed on reboot
b- When restarting the screen it tells me: Set guarantee bit: Kernel (in yellow)
c- Try to install the Firmware Stock by Odin, but I can't, it doesn't throw me an error, but it doesn't install anything at all, IT KEEPS ME THE TWRP INTACT
d-Download a Modified ROM, the installation by TWRP and it was installed correctly, but the SIM card does not work (I assume it is because it has a different modem) and I get an error for almost everything L
I want to go back to the Stock ROM but ODIN does nothing ... Please I need your help.
I can access Download and TWRP mode.
discuss the translation ...
Friends, any ideas ?? ... any help is appreciated.
As you already flashed twrp, so i think you know how to go download mode. Just see any youtube video how to flash stock rom on s8/s9. Download your latest firmwere from sammobile or samfrew and flash. Procedure is same as s8 or s9.
tutul2336 said:
As you already flashed twrp, so i think you know how to go download mode. Just see any youtube video how to flash stock rom on s8/s9. Download your latest firmwere from sammobile or samfrew and flash. Procedure is same as s8 or s9.
Click to expand...
Click to collapse
Friend, that's the problem, ODIN doesn't let me install the Stock Rom, at the end of the flash process with Odin, the phone remains intact (with the TWRP intact)
DARKSIDERS_2012 said:
Friend, that's the problem, ODIN doesn't let me install the Stock Rom, at the end of the flash process with Odin, the phone remains intact (with the TWRP intact)
Click to expand...
Click to collapse
What kind of error? or it flashes perfectly? Give us something.. Photo of odin and your phone's download mode screen...
When you first time booted twrp, you needed to click on wipe > format data. This will decrypt your phone (and it wipe your internat storage) then you can flash rmm and no verity. After that, click on reboot > recovery and then reboot > system (or flash magisk). Recommended to flash latest rmm and no verity.
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: