Related
Hey guys,
I have a problem with a bricked xiaomi redmi 2 prime.
After a bootloop i tried to fix the problem with a system reset. But this does not work
After i booted into recovery and wiped all data, the phone reboot but than nothing happend. So i tried to flash the rom with the mi flash tool, but there i get the error "remote: failed to write partition".
So i went over to the adb and fastboot programms, with fastboot i erased system, userdata, recovery, boot and then i flashed the images of this elements back on the phone (fastboot flash sayed that flashing went successfully)
Then the phone reboot, nothing happend and i can´t get into recovery mode, also adb doesn´t recognoze the phone anymore
Have you any idea what i can do to fix the phone, or can i put it into the trash?
Thanks for your help
Stop experimenting.
Does fastboot work? Do a full flash with miflash(erasing all storage)(firmware should be of your model itself)
If fastboot doesnt work,try putting in the charger with battery in,if there is any vibration,you have a chance of reviving your r2
#fingerscrossed
Ezio95 said:
Hey guys,
I have a problem with a bricked xiaomi redmi 2 prime.
After a bootloop i tried to fix the problem with a system reset. But this does not work
After i booted into recovery and wiped all data, the phone reboot but than nothing happend. So i tried to flash the rom with the mi flash tool, but there i get the error "remote: failed to write partition".
So i went over to the adb and fastboot programms, with fastboot i erased system, userdata, recovery, boot and then i flashed the images of this elements back on the phone (fastboot flash sayed that flashing went successfully)
Then the phone reboot, nothing happend and i can´t get into recovery mode, also adb doesn´t recognoze the phone anymore
Have you any idea what i can do to fix the phone, or can i put it into the trash?
Thanks for your help
Click to expand...
Click to collapse
Yup actually download the latest version of miui fastboot files..paste them in the fastboot folder... Dont bother erasing you phn again(as it does erase at the time of writing new files...)And most importantly flashing only 3 files is more than enough. Flash them in the order boot.img, system.img, recovery.img and thats it. If your problem is actually not booting into fastboot then....press the volume down button and insert your usb while keeping it pressed.
Hey guys,
thanks for the answers. I tryed to flash only thees 3 files but it doesn´t change anything. fastboot works without trouble so far.
I tried multiple times the xiaomi flashing tool but this only throws errors -.-'
I will try again and keep you by the actual progress ^^
Ezio95 said:
Hey guys,
thanks for the answers. I tryed to flash only thees 3 files but it doesn´t change anything. fastboot works without trouble so far.
I tried multiple times the xiaomi flashing tool but this only throws errors -.-'
I will try again and keep you by the actual progress ^^
Click to expand...
Click to collapse
If you can get the fastboot to work, you can flash recovery on your phone for good or temporarily to flash zips.
How to do it?
1.Get into fastboot on phone
2.Install minimal adb and fastboot in your computer
3.Run adb and install drivers
4.Connect your phone which should be in fastboot to computer
5.Check for devices by using "fastboot devices", if a device is listed, proceed
6.Download a custom recovery, rename the recovery img to something easy than using the full name and copy the img into the folder where minimal adb and fastboot is installed
7.Type in "fastboot flash recovery <name you gave to recovery img>.img" (img for the image format) to flash recovery permanently
OR
7.Type in "fastboot boot <recovery name>.img" to use it temporarily, this method will erase the recovery on reboot so flash whatever you want before rebooting if you're following this method.
8.Flash in your ROM zip, try stock and custom ROMs, see if you can get your phone to work
GOOD LUCK
Same error with my yureka plus (error "remote: failed to write partition"). I'm planning to buy redmi 2 prime.. . Scared if this will happen to redmi 2 prime
Hi all!
Fairly new to rooting & flashing on Android - but I've done so successfully in the past on an older device.
Not fully happy with OxygenOS (wanted to flash a Cyanagen ROM) - but I'm having some trouble getting everything to work.
Here are the steps I followed and results:
Put OP2 into Developer Mode & enabled USB debugging
Connected OP2 to MacBookPro via USB
Opened Terminal on Mac & ran "adb reboot bootloader" to reboot the device into fastboot mode
One in Fastboot Mode, ran "fastboot devices" via Terminal to ensure it was readying my OP2 (everything is fine here)
In Terminal, ran "fastboot flash recovery recovery.img" (I had previously downloaded a copy of TWRP into the same folder as ADB & Fastboot & renamed the TWRP image to "recovery.img")
In Terminal, next ran "fastboot boot recovery.img"
Once it booted into TWRP, I navigated to the SuperSu .ZIP file saved on my OP2 and ran through the install process...and rebooted the device.
This is where it hangs on the boot screen - It's a red dot with 2 white dots circling around it.
(I tried to add an image of the screen to this post, but it says I'm too much of a newb to be able to post images
It's been on this screen for at least 30 minutes now - and I'm thinking it shouldn't take this long at this point (but I could be wrong).
Can anyone please help me?
Thank you much in advance!
just one more step
here you go:
http://forum.xda-developers.com/oneplus-2/help/oneplus-2-bootloop-flashing-supersu-t3424834
I'm a noob but a respectful one. I'm embarrassed to have to post in this forum asking for help on what should be such a simple problem but I'm three days and 500 google searches closer to insanity.
I just want to install TWRP on my Essential Android which I bought from Best Buy but activated on T-Mobile.:
Product - Mata
Variant - Openus
Bootloader Version - mata-84f7cce
Baseband Version - 2.0.c4.M2.0.3
Secure Boot - yes
Device State - unlocked
I've installed ADB and fastboot on my computer and made it system wide using the PATH variable in Windows 10 Pro System Properties "Environment Variables"
I have all the proper Windows usb drivers from the Essential website and I have activated Developer Options, OEM unlocking and USB Debugging on my phone. I've removed the pin so the device doesn't lock.
I'm using the original USB C cable from Essential plugged directly into my new HP all n one USB C slot.
I've copied the twrp image and pasted it into C:\ADB\ along with my minimum adb\fastboot install. I then opened a powershell there. Both the "adb devices" and "fastboot devices" commands show my phone is being recognized and that I am indeed in FastBoot Mode.
I originally left the twrp image name as downloaded: "twrp-mata_2" but when "fastboot flash recovery C:\ADB\twrp-mata_2" resulted in "error: cannot load 'C:\ADB\recovery.img': No such file or directory"
I renamed it and ran the command:
"fastboot flash recovery C:\ADB\recovery.img"
Same error.
Please help
There is no recovery partition on the device.
To flash TWRP, you'll need to fastboot flash boot, then boot to recovery from fastboot on your device. Once in TWRP, you'll need to flash a boot image before restart. TWRP isn't persistent, so you'll have to do this every time.
Unless you're looking for a custom ROM, the easiest way to root is just to patch a stock boot image with magisk and flash it from fastboot.
MackHoncho said:
I'm a noob but a respectful one. I'm embarrassed to have to post in this forum asking for help on what should be such a simple problem but I'm three days and 500 google searches closer to insanity.
I just want to install TWRP on my Essential Android which I bought from Best Buy but activated on T-Mobile.:
Product - Mata
Variant - Openus
Bootloader Version - mata-84f7cce
Baseband Version - 2.0.c4.M2.0.3
Secure Boot - yes
Device State - unlocked
I've installed ADB and fastboot on my computer and made it system wide using the PATH variable in Windows 10 Pro System Properties "Environment Variables"
I have all the proper Windows usb drivers from the Essential website and I have activated Developer Options, OEM unlocking and USB Debugging on my phone. I've removed the pin so the device doesn't lock.
I'm using the original USB C cable from Essential plugged directly into my new HP all n one USB C slot.
I've copied the twrp image and pasted it into C:\ADB\ along with my minimum adb\fastboot install. I then opened a powershell there. Both the "adb devices" and "fastboot devices" commands show my phone is being recognized and that I am indeed in FastBoot Mode.
I originally left the twrp image name as downloaded: "twrp-mata_2" but when "fastboot flash recovery C:\ADB\twrp-mata_2" resulted in "error: cannot load 'C:\ADB\recovery.img': No such file or directory"
I renamed it and ran the command:
"fastboot flash recovery C:\ADB\recovery.img"
Same error.
Please help
Click to expand...
Click to collapse
You should try using a Type-C to USB cable, I ran into the same issue trying to flash mine using supplied cable, once I tried the USB to Type-C it worked. :good:
MackHoncho said:
I'm a noob but a respectful one. I'm embarrassed to have to post in this forum asking for help on what should be such a simple problem but I'm three days and 500 google searches closer to insanity.
I just want to install TWRP on my Essential Android which I bought from Best Buy but activated on T-Mobile.:
Product - Mata
Variant - Openus
Bootloader Version - mata-84f7cce
Baseband Version - 2.0.c4.M2.0.3
Secure Boot - yes
Device State - unlocked
I've installed ADB and fastboot on my computer and made it system wide using the PATH variable in Windows 10 Pro System Properties "Environment Variables"
I have all the proper Windows usb drivers from the Essential website and I have activated Developer Options, OEM unlocking and USB Debugging on my phone. I've removed the pin so the device doesn't lock.
I'm using the original USB C cable from Essential plugged directly into my new HP all n one USB C slot.
I've copied the twrp image and pasted it into C:\ADB\ along with my minimum adb\fastboot install. I then opened a powershell there. Both the "adb devices" and "fastboot devices" commands show my phone is being recognized and that I am indeed in FastBoot Mode.
I originally left the twrp image name as downloaded: "twrp-mata_2" but when "fastboot flash recovery C:\ADB\twrp-mata_2" resulted in "error: cannot load 'C:\ADB\recovery.img': No such file or directory"
I renamed it and ran the command:
"fastboot flash recovery C:\ADB\recovery.img"
Same error.
Please help
Click to expand...
Click to collapse
@barteringram is right, no recovery partition.
Your command needed is this.
Fastboot flash boot whateveryounamedtwrp.img.
fastboot flash boot_a/boot_b yourTWRP.img
The above command worked for me. Use boot_a or boot_b depending on what you have. In addition use a separate type C cable to your PC instead of stock type C cable and remove all USB accessories plugged in the PC. I know its crazy but working with this phone may require you to do some unexplainable stuff.
MackHoncho said:
I'm a noob but a respectful one. I'm embarrassed to have to post in this forum asking for help on what should be such a simple problem but I'm three days and 500 google searches closer to insanity.
I just want to install TWRP on my Essential Android which I bought from Best Buy but activated on T-Mobile.:
Product - Mata
Variant - Openus
Bootloader Version - mata-84f7cce
Baseband Version - 2.0.c4.M2.0.3
Secure Boot - yes
Device State - unlocked
I've installed ADB and fastboot on my computer and made it system wide using the PATH variable in Windows 10 Pro System Properties "Environment Variables"
I have all the proper Windows usb drivers from the Essential website and I have activated Developer Options, OEM unlocking and USB Debugging on my phone. I've removed the pin so the device doesn't lock.
I'm using the original USB C cable from Essential plugged directly into my new HP all n one USB C slot.
I've copied the twrp image and pasted it into C:\ADB\ along with my minimum adb\fastboot install. I then opened a powershell there. Both the "adb devices" and "fastboot devices" commands show my phone is being recognized and that I am indeed in FastBoot Mode.
I originally left the twrp image name as downloaded: "twrp-mata_2" but when "fastboot flash recovery C:\ADB\twrp-mata_2" resulted in "error: cannot load 'C:\ADB\recovery.img': No such file or directory"
I renamed it and ran the command:
"fastboot flash recovery C:\ADB\recovery.img"
Same error.
Please help
Click to expand...
Click to collapse
Stop the presses!
Please do not use that old ass version of TWRP...
Many many fixes since then...
Please read and familiarize yourself with
http://mata.readthedocs.io/en/latest/
And also realize that you will not ever have persistent TWRP
TWRP-Mata_11.img is what you should be flashing and you have to flash it via fastboot Everytime you want to enter twrp. Then you have to flash a stock boot.img Everytime you reboot the system from twrp.
droidstyle said:
TWRP-Mata_11.img is what you should be flashing and you have to flash it via fastboot Everytime you want to enter twrp. Then you have to flash a stock boot.img Everytime you reboot the system from twrp.
Click to expand...
Click to collapse
I am semi new to this community, so I am unsure if it's doing this because I am rooted or not but I've got twrp permanently installed... So from my understanding Slot a can hold your os and slot b basically hold your twrp you just need to remember when you need to switch back.... How I installed was fast booted twrp to slot a, then in twrc switched to slot b to install rom, then switch back to slot a and did a reboot to recovery... Boots into twrp, I switched back to slot b to flash gapps, then restart system... Once inside os and everything is set up if you are rooting reboot to bootloader and flash the patched boot. Img with fastboot on pc... Then reboot system... Now when you want to use twrp all you have to do is reboot bootloader, fastboot to switch to slot a, and then boot recovery... Then Twrp will load then switch to slot b and you are good to go!
barteringram said:
There is no recovery partition on the device.
To flash TWRP, you'll need to fastboot flash boot, then boot to recovery from fastboot on your device. Once in TWRP, you'll need to flash a boot image before restart. TWRP isn't persistent, so you'll have to do this every time.
Unless you're looking for a custom ROM, the easiest way to root is just to patch a stock boot image with magisk and flash it from fastboot.
Click to expand...
Click to collapse
Thank you in advance for answering about three questions as of yet forthcoming... done this b4? lol
BTW, yes, I intend to install magisk, root and AOSip 8.1.
Anyway, I got past the original problem, kinda.
My problem arose from having too many adb installations in too many places on my windows machine.
I deleted everything, installed a single instance, put everything in a single folder on my desktop, opened a windows powershell there and then adb/powershell was able to find the twrp file.
Next problem was a "no such partition" error which was solved by a google search and specifying the slot location in the flash command.
NOW I have twrp recovery installed but the touchscreen doesn't work so its useless. AAAAAARRRRGHH!
Should I post a new thread or is this still OP?
I'm still in the same boat as my goal is a working TWRP recovery....
please advise
A_Pac1 said:
You should try using a Type-C to USB cable, I ran into the same issue trying to flash mine using supplied cable, once I tried the USB to Type-C it worked. :good:
Click to expand...
Click to collapse
Worth a try I guess but I am maintaining a solid connect to my PC and all other commands seem flawless. My problem has evolved now. I have installed twrp but now the touchscreen wont work.
rignfool said:
Stop the presses!
Please do not use that old ass version of TWRP...
Many many fixes since then...
Please read and familiarize yourself with
http://mata.readthedocs.io/en/latest/
And also realize that you will not ever have persistent TWRP
Click to expand...
Click to collapse
You might have just solved my newly evolved issue (got twrp installed but now touchscreen doesn't work)
Will get on it and let you know.
Quick question; What do you mean twrp is not persistent? Does that mean I have to install it and install magisk and whatever rom from twrp on the first shot before rebooting? At what point does twrp disappear?
What other pitfall, tips or tricks should I be aware of?
MackHoncho said:
You might have just solved my newly evolved issue (got twrp installed but now touchscreen doesn't work)
Will get on it and let you know.
Quick question; What do you mean twrp is not persistent? Does that mean I have to install it and install magisk and whatever rom from twrp on the first shot before rebooting? At what point does twrp disappear?
What other pitfall, tips or tricks should I be aware of?
Click to expand...
Click to collapse
It's not persistent as in it won't survive the flashing of the stock boot.img.
MackHoncho said:
Thank you in advance for answering about three questions as of yet forthcoming... done this b4? lol
BTW, yes, I intend to install magisk, root and AOSip 8.1.
Anyway, I got past the original problem, kinda.
My problem arose from having too many adb installations in too many places on my windows machine.
I deleted everything, installed a single instance, put everything in a single folder on my desktop, opened a windows powershell there and then adb/powershell was able to find the twrp file.
Next problem was a "no such partition" error which was solved by a google search and specifying the slot location in the flash command.
NOW I have twrp recovery installed but the touchscreen doesn't work so its useless. AAAAAARRRRGHH!
Should I post a new thread or is this still OP?
I'm still in the same boat as my goal is a working TWRP recovery....
please advise
Click to expand...
Click to collapse
I had the same issue with using an older version of Mata TWRP... You need to install TWRP-MATA_11
Solved
My Windows 10 machine isnt set to show file extensions.
was trying to fastboot twrp-11 as I named it; recovery.img
fastboot wanted recovery.img.img
please laugh hardily
aer0zer0 said:
@barteringram is right, no recovery partition.
Your command needed is this.
Fastboot flash boot whateveryounamedtwrp.img.
Click to expand...
Click to collapse
Thank you, thank you, THANK YOU!! You would not believe how long I've been trying to solve this problem! Now I can get on with tweaking and personalizing my Oneplus 6T!
vonstarr said:
Thank you, thank you, THANK YOU!! You would not believe how long I've been trying to solve this problem! Now I can get on with tweaking and personalizing my Oneplus 6T!
Click to expand...
Click to collapse
So op6t is easier (I just bought one)
Fastboot boot nameoftwrp.img
It'll boot twrp without flashing it to the phone. Makes life easier. Mata doesn't have this option.
I've seen alot of guys here who are encountering problems while flashing custom roms.Make sure you have backed up all your data before starting the procedure.
This method is also valid for those who are coming straight from the Stock rom.
Prerequisites :
•Unlocked Bootloader
•ADB and Fastboot Files
•Desired Custom Rom
•Copypartitions file
•TWRP image
•TWRP installer - Download and move it to Internal Storage
•A USB C-Type Cable and some Brain.
•Magisk [Optional]
•Fresh Gapps ARM64 (I'd recommend Mini)
Installation :
#1. Back up all your data or simply move everything to your PC.
#2.Boot your phone into Bootloader Mode [Power button + Volume Down] or Enable Debugging mode,And run this Command ''adb devices''- To ensure that the device is connected,then ''adb reboot bootloader''.
#3.Move the ''twrp.img'' file to the ''adb" folder of your PC.
#4.You'll see 3-4 files along with twrp.img file you just copied there[adb folder], Simply Click Shift+Right Click anywhere in that blank space,then click on Open Powershell Window here or Open Command Prompt Window.
#5.Attach your phone to the PC,you'll hear a sound,yet run this Command "fastboot devices" to ensure that the device is connected properly [Device ID will appear]
#6.Now you're supposed to temporarily boot TWRP in order to permanently flash the Custom Recovery.So to do this ,Run this Command while the device is connected to the PC in fastboot mode > "fastboot boot twrp.img '' [After Typing fastboot boot, simply drag twrp.img file into the PowerShell or Command prompt window to Complete the Command ''fastboot boot twrp.img'',it may look like ''fastboot boot C://adb/twrp.img''.
#7.After Booting Temporarily into TWRP,Swipe for Modifications,Locate and install TWRPinstaller.zip,this will permanently install TWRP as your Recovery.
#8.After installing TWRP,Return to the home screen of TWRP and Reboot into Recovery from there.[Permanently Flashing incase you don't need hassles with computer flashing]
#9.After booting again into TWRP,Click on Wipe>Format User Data>Type Yes>Go to Home screen Reboot into Recovery.
#10.After booting again into TWRP,Click on Wipe>Advanced Wipe> [Tick on Dalvik/Art Cache,Cache, System,Data] > Wipe it off.
#11.Go back to the Home Screen of the TWRP,Reboot into Recovery.
#12.Now Push copypartitions.zip file to your phone from your PC,then flash it via TWRP,then again,Reboot your phone to Recovery.
#13.Now Push the Desired Custom rom you would want to install on your G7 river from the PC> Install it> After the Installation Finishes,Reboot your phone to the Bootloader mode from TWRP [As the the Recovery will be replaced by the Custom Rom's Recovery,hence, TWRP will be removed].
#14.Once in the Fastboot Mode,run the command in PowerShell or CMD, "fastboot boot twrp.img"
#15.After booting again into TWRP,Push Gapps File into your phone and install it Accordingly,After the installation Finishes,Wipe Dalvik Cache,Come back to the Home screen of TWRP,Reboot > Power Off in TWRP,then manually Power it On,After powering it On,the rom may prompt you for a factory reset,that's it. You've successfully installed Custom Rom along with the Google Apps without Messing with the partitions.
#16.Now, Finally Boot your phone into Bootloader mode, run the command "fastboot boot twrp.img" and install TWRPinstaller.zip,this will again permanently install TWRP as your recovery.
#17.You may root your phone by installing Magisk or Flash any other zip without the need of temporarily booting TWRP,as you've flashed it permanently. Simply Reboot to Bootloader then Boot into Recovery.
Errors and Fixes:
#1.If you encounter any problem while flashing zips from the internal storage, simply move all the zips to the MicroSD or USB OTG and flash it from there.
#2.If your TWRP isn't reading the internal storage properly or isn't responding well,simply reboot your phone again to the Bootloader mode,again boot twrp.img and try again,this should do the thing.
#1.copy-partitions-AB.zip
#2.twrp-3.3.1-0-river.img
#3.twrp-installer-3.3.1-2-river.zip
Find these files on the internet or XDA forums as I can't Post links yet,Happy to help!
Simplify and Clarify
Thanks @deathcruizer for the your procedure. It rescued me in a jam. The critical items for me that you noted were that the Custom ROM replaced TWRP with its own Recovery and that a Factory Reset was required.
I wanted to simplify and clarify your key points for those already setup with fastboot and familiar with TWRP. Generic filenames mentioned should be replaced by the actual full name; eg, twrp-3.3.1-2-river.img.
1. Backup partitions in TWRP just in case for a restore. And Data will be needed later.
2. Move all zip files needed (ROM, Gapps, copy-partitions, twrp-installer, Magisk, etc.) to internal storage or USB OTG. Move twrp.img on PC to a convenient location for fastboot.
3. Enter fastboot boot twrp.img to temporarily use TWRP.
4. Flash copy-partitions.zip, reboot, and flash custom ROM.zip.
5. In TWRP, choose Reboot to the Bootloader mode, not Recovery. TWRP has been removed and replaced by the custom ROM's Recovery.
6. Enter fastboot boot twrp.img to temporarily use TWRP again. Install Gapps.zip, wipe caches, and then Power Off.
7. Manually Power On to the Custom ROM. Accept its Factory Data Reset option.
8. Boot into Bootloader Mode, enter fastboot boot twrp.img again, and use this temporary TWRP to install TWRP permanently using twrp-installer.zip.
9. Reboot and begin a minimum setup of the Custom ROM.
10. Reboot to TWRP and restore the Data partition.
11. G7 River is back with its apps, desktop layout, settings, icons, etc., on the new Custom ROM.
Hey guys, your tutorial is great and very informative. I do however have a recurring problem with installing any custom rom. No matter which one I choose, I have no LTE and occasionally the phone randomly reboot if I unplug my phone. Has anyone encountered this? I've followed all applicable steps for properly installing a custom rom, and am pretty use to it as I've always flashed roms on as many phones as I could. Any help or guidance would be appreciated. Thanks in advance
What model phone, to be clear?
Moto g7, xt19621. I tried to flash lineage again today to no avail. Twrp then copy. Zip. Reboot. Lineage. Wipe dalvic. Reboot. Previously tried wiping system and starting from scratch. Copy. Zip and start from scratch. Clean flash. Dirty flash. I've been able to get it to work properly maybe 2 or three times since having the phone and trying different roms. Basically always having to revert back to stock after a multitude of attempts. I've never had this much trouble flashing with a phone.
---------- Post added at 12:45 AM ---------- Previous post was at 12:27 AM ----------
Do I need to flash stock to the 9eiginal firmware or something? I tried the stock room from August 2019, and kind 9f same issues. Device kinda bugged out.
If you're going to do a full article, always be sure to check and double check your process before sharing. The A/B slots on this device CAN cause mucho mucho errors if the user is unfamiliar or does not alternate correctly (TWRP can select boot slot, yes, but doesnt always work the right way), they can end up with a bricked device. I am excited to see a full guide be posted but for other people's sake, I recommend maybe clarifying the A/B details. I, personally, have yet to find a good A/B tutorial, and how they work during installs, online but if there is one and someone wants to share the link I'd sure appreciate it! Thanks and goodluck!
---------- Post added at 02:02 AM ---------- Previous post was at 01:49 AM ----------
trentag1988 said:
Moto g7, xt19621. I tried to flash lineage again today to no avail. Twrp then copy. Zip. Reboot. Lineage. Wipe dalvic. Reboot. Previously tried wiping system and starting from scratch. Copy. Zip and start from scratch. Clean flash. Dirty flash. I've been able to get it to work properly maybe 2 or three times since having the phone and trying different roms. Basically always having to revert back to stock after a multitude of attempts. I've never had this much trouble flashing with a phone.
---------- Post added at 12:45 AM ---------- Previous post was at 12:27 AM ----------
Do I need to flash stock to the 9eiginal firmware or something? I tried the stock room from August 2019, and kind 9f same issues. Device kinda bugged out.
Click to expand...
Click to collapse
back up phone if you have third party backup application
(not absolutely necessary BUT, I always remove my security and google account before going into fastboot)
reboot to fastboot or power off phone and boot to fastboot by holding down the volume down+power
"fastboot set_active b"
"fastboot boot (drag your twrp img file from it's location to the command window) so that it reads sort of like "fastboot boot c:\path-to-twrp.img"
1. now install copy-partitions.zip
2. "Format, Advanced", type "yes" then back to TWRP main screen
3. install ROM of your choice (if installing Lineage, skip step 4)
4. install twrp-installer.zip (make sure you're using the zip format, not img)
5. "adb reboot bootloader"
"fastboot set_active a" (because when you installed the ROM, the device installed it to the inactive slot, in this instance that slot would be "a"
ADV: you may get a message indicating you're already on slot a, which is fine. 9 out of 10 times the device changes slot automatically after you reboot
post-ROM-install
6. from TWRP home choose "Advanced, ADB Sideload", check the two boxes and"adb sideload c:\path-to-gapps" (you'll need ARM64 gapps for this device)
7. IF you want magisk, from TWRP home choose "Advanced, ADB Sideload", check the two boxes and "adb sideload c:\path-to-magisk.zip"
8. "adb reboot bootloader"
9. "fastboot -w"
10. For whatever reason, magisk never stays on my device but I just install the apk and install it from the app.
Hope this doesn't annoy anyone and proves helpful.
@clinton I am definitely going to try this particular method. Setting B as active first is the one thing I have not done. I would like to point out that I am about to do fastboot boot twrp.img , however when installing the provided zip, my phone makes a weird noise on every screen tap. Like odd feedback from the speaker. If I use just lineage recovery that installs from the rom, it doesn't do that. Another thing that happens now - every lineage install goes fine until first boot. As soon as I sign on to WiFi and it tries to activate the radio, device just shuts down. Has anyone had this happen to them?
I am still experiencing the same issues. flashed back to original firmware and had no LTE. didn't resolve when flashing a custom rom. Flashed to latest stock rom and everything went through properly (LTE, no random reboot after unplugging), attempted rigmarole for flashing custom rom, same issues. x over signal bar and reboot as soon as I unplug the device. I have basically given up at this point, going to have a go at it again when stock android 10 update happens Thank you, guys, for all the help and tutorials. Big hugs, take care
Weird: I was just using it normally, it switched off and now it stays stuck on the Google logo; when entering recovery mode, I get TWRP"s splash screen and it stays there, so I cannot even recover.
Suggestions please??
Note 1: I'm pretty bad with this kind of stuff, need step-by-step instructions.
Note 2: rom is AOSP 7.1.2 but I guess is irrelevant, as even TWRP does not load.
Thanks in advance!!
Can you fastboot boot the TWRP recovery?
Hmmm dont know exactly what that means sorry; I mean I havent tried connecting it to the laptop and using thr ADB toolkit, but I can reset via Power+VolDown to the bootloader menu (? the android layind down and giving the option to StartSystem/ SwitchOff/ Restart/ RecoveryMode), and choosing RecoveyMode it tries to launch TWRP (it even shows the logo) but stays there on the splashscreen, doesn't quite manage to give me the TWRP menus
Someone?
AndDiSa said:
Can you fastboot boot the TWRP recovery?
Click to expand...
Click to collapse
let's see... I set in recovery mode, connect to the PC (does not recognise it), and with "fastboot boot twrp.img" it just sends/writes the file, the tab shows the Google logo with open lock, and then tries to launch Twrp, but as before, it just get stuck in the splashscreen "TeamWin Recovery Project 3.3.1.0" , so just the same.
Command "fastboot flash boot twrp.img" the same
Command "fastboot flash recovery twrp.img" the same
Command "adb devices" returns the list empty
Command "adb reboot recovery" returns "error: no devices / emulators found"
Command "fastboot oem unlock" returns "(bootloader) bootloader is already unlocked"
I tried running a tool called FirstAid (https://forum.xda-developers.com/devdb/project/dl/?id=16684) but does nothing for me
I'm lost, please help
Video and photos of the issue (device, not adb)
video: https://photos.app.goo.gl/GrFrmQhbyQeHVFZN7
Well, looking at your video it seems that there is no bootable ROM installed and also the recovery (for what ever reason) has some issues to start.
The fact, that you are able to boot into bootloader shows that at least it's not completely bricked ... but there's still the chance that the flash memory has some issues.
I would connect the device via usb with a PC and try to do a
fastboot boot <twrp-3.3.1-grouper.img>
to whether in that case the recovery is booting.
If this is successful, the next step would be re-flashing the recovery into the recovery partition and booing into recovery mode from the bootloader.
If this is successful, too, wiping and flashing a new ROM would be the last step.