Develop Bugs

Soft Brick, couldn't flash anything, now can't mount anything

When I boot to twrp in recovery, I am unable to accomplish anything -- wipe or install. When I try to do either I get an error about "unable to mount sdcard". I have seen this thread, but cannot find the zip mentioned anywhere. I am able to run "adb push" to /sdcard and then to actually see the file pushed there in twrp recovery. I'm just not able to do anything with the pushed file in the install function.
Tried mounting with adb shell, but kept getting error of "Invalid argument". Did discover that /sdcard is /dev/block/mmcblk0p36, and using fdisk in adb shell found that it "doesn't contain a valid partition table". I'm not concerned about losing data. Everything was backed up, but anybody know how to create the correct partition table so I can install a ROM?
Original post:
So I screwed up. I rooted my phone according to this post. Unfortunately I then did something stupid when trying to flash a new recovery and get actual SU privileges to remove bloatware. Instead of going back to the first page in that thread and seeing the links to use there, I followed this guide. Unfortunately, when I ran the script, install-insecure-linux.sh, it flashed the boot.insecure.img and then spit out errors related to incompatibility with the ncurses version on my laptop. It seems difficult if not impossible to downgrade the ncurses without causing a ton of other headaches. It went to reboot and just stayed dead.
Thought I was hosed, but then after charging for a while I got signs of life. Managed to boot to fastboot. Connected back up to the laptop and decided to follow the cyanogenmod guide for installing CM11. Flashed the CM recovery img file successfully but after rebooting I can't do anything.
I still occasionally get into the fastboot on the phone. Running fastboot devices on the laptop lists the phone. Running adb devices does not. Running any other fastboot command sticks at either nothing or <waiting for device>. Running any adb command gives "error: Device not found". I added a udev rule and adb_usb.ini with the device id "0bb4" and mode 0666, but no joy.
I only have a linux machine available at the moment, so I'd prefer suggestions for working in linux. If someone knows of a good Windows solution, I can probably try that in a few days. Thanks in advance.
EDIT: Progress
Noticed that for a second when I first connect to the laptop USB the fastboot menu showed in red FASTBOOT USB before going back to just FASTBOOT. Managed to tee up the command for flashing the twrp recovery img and ran it immediately upon plugging in. Was then able to boot to recovery. Not sure what my next step to getting a working phone is though. Help still appreciated.

My last post got swallowed by the ether I guess. I was able to fix it by formatting the sdcard using mkdosfs -F 32 -n INT_SD -s 64 /dev/block/mmcblk0p36. Then rebooting, wiping, and installing CM11. All is good again.

Can't install rom on moto z play (verizon)

I have a Motorola Z play which was running 7.1.1. It is a Verizon version, so it is said to be unrootable. But I tried it anyway.
I flashed twrp-3.2.1-addison first. After I did some thing (data wiping, etc), it does not reboot to normal os anymore. At one point, I noticed it says "no OS to boot into”. I searched online and found that the only solution is to install new rom. So I downloaded oreo zip and ran adb to sideload it to my phone. However it failed due to the following error:
Code:
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
Then I tried another option which is to save the zip to my phone and install it in recovery mode ( installed twrp this way). When I opened my phone with PC, it is empty. I tried to drag the zip file to the root dir of my phone, I got the following error:
Code:
Cannot copy item
The device has either stopped responding or has been disconnected.
I think it probably had to do with the data wiping. "adb devices" still shows the device is connected with the ID though.
How do fix this?

jiddy0001 said:
I have a Motorola Z play which was running 7.1.1. It is a Verizon version, so it is said to be unrootable. But I tried it anyway.
I flashed twrp-3.2.1-addison first. After I did some thing (data wiping, etc), it does not reboot to normal os anymore. At one point, I noticed it says "no OS to boot into”. I searched online and found that the only solution is to install new rom. So I downloaded oreo zip and ran adb to sideload it to my phone. However it failed due to the following error:
Code:
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
Then I tried another option which is to save the zip to my phone and install it in recovery mode ( installed twrp this way). When I opened my phone with PC, it is empty. I tried to drag the zip file to the root dir of my phone, I got the following error:
Code:
Cannot copy item
The device has either stopped responding or has been disconnected.
I think it probably had to do with the data wiping. "adb devices" still shows the device is connected with the ID though.
How do fix this?
Click to expand...
Click to collapse
Uhhh.......yeah I have the same phone as u and I'm pretty sure u just bricked your phone as the Droid version DOES NOT have a unlockable bootloader which u would need to be able to install the stock firmware/rom that came from the phone from the fact....
Sent from my XT1635-01 using Tapatalk

Yeah dude, you just bricked your phone probably. Take it to Verizon and hopefully they will help reset it to stock but since you put twrp on, they might not. Always unlock your bootloader unless following a guide that is SAFE for locked bootloader

so no way flash custom rom to verizon moto z play?

Pixel XL boot loop (sort of) help, might have bricked my phone, not sure

Before I begin, just know I am aware I am an idiot for this.
I decided I was going to install LineageOS onto my Pixel XL today, something I have done many times before with different phones. In my haste, I ended up on the wrong install guide (my own stupid fault for not double checking, I know) and I accidentally installed TWRP on the boot partition. When I boot my phone, it just goes right into TWRP, regardless of whether I pick Start or Recovery Mode from the bootloader. I tried sideloading Lineage from TWRP, but it got to 47% done according to adb before abruptly stopping. My phone was then stuck in a boot loop where I couldn't even get into TWRP. The furthest I could get was the bootloader. After restarting my phone a number of times, I was finally able to get back into recovery mode with TWRP. I can reboot into Bootloader or Recovery (TWRP) from TWRP. If I try to reboot into System, I get the warning about my bootloader being unlocked, the Google splash screen, and then I get booted back into TWRP. If I try booting into Slot A or Slot B I get the following:
Code:
Could not mount /data and unable to find crypto footer.
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
More details:
Phone is not rooted
The original command I ran that started this whole mess was
Code:
fastboot flash boot /path/to/twrp.img
As long as I am in TWRP, I can see my phone from my computer if I run "adb devices"
My original thought was to try to flash the stock .img file (or the Lineage one if I could find it), but any time I run any fastboot commands, my terminal just says "< waiting for any device >" and hangs until I kill the process. I assume this is because my device isn't actually booted. I'm not sure if there is a way to accomplish the same thing using adb.
All adb commands seem to still work fine. I can still sideload with TWRP (sort of, see above paragraph), and I can use the push and pull commands to add and remove things from the phones memory
Have I bricked this phone or is there a way to fix this?

RyanDMC said:
Before I begin, just know I am aware I am an idiot for this.
I decided I was going to install LineageOS onto my Pixel XL today, something I have done many times before with different phones. In my haste, I ended up on the wrong install guide (my own stupid fault for not double checking, I know) and I accidentally installed TWRP on the boot partition. When I boot my phone, it just goes right into TWRP, regardless of whether I pick Start or Recovery Mode from the bootloader. I tried sideloading Lineage from TWRP, but it got to 47% done according to adb before abruptly stopping. My phone was then stuck in a boot loop where I couldn't even get into TWRP. The furthest I could get was the bootloader. After restarting my phone a number of times, I was finally able to get back into recovery mode with TWRP, which is where I am now, as I am terrified to touch anything else.
More details:
Phone is not rooted
As long as I am in TWRP, I can see my phone from my computer if I run "adb devices"
All adb commands seem to still work fine. I can still sideload with TWRP (sort of, see above paragraph), and I can use the push and pull commands to add and remove things from the phones memory
Have I bricked this phone or is there a way to fix this?
Click to expand...
Click to collapse
If you can get to fastboot mode. Use the flash-all to install the March 2019 factory image.

Ignore this, I lied. Trying the above now.

Homeboy76 said:
If you can get to fastboot mode. Use the flash-all to install the March 2019 factory image.
Click to expand...
Click to collapse
That worked. Had to fidget with it a bit because fastboot kept complaining about ANDROID_PRODUCT_OUT not being set but I got it to work.
In case anyone happens upon this in the future, if you get that error, you need to create an environment variable on your machine called ANDROID_PRODUCT_OUT and set it to the path to a very specific folder in the image .zip you download from Google. When you extract that .zip, you should get a folder, that contains another folder, that contains two image files (a bootloader one and a radio one), three "flash-all" script files, and yet another .zip file. Extract that .zip and the folder that it creates is the one you need to set the environment variable to.

RyanDMC said:
That worked. Had to fidget with it a bit because fastboot kept complaining about ANDROID_PRODUCT_OUT not being set but I got it to work.
In case anyone happens upon this in the future, if you get that error, you need to create an environment variable on your machine called ANDROID_PRODUCT_OUT and set it to the path to a very specific folder in the image .zip you download from Google. When you extract that .zip, you should get a folder, that contains another folder, that contains two image files (a bootloader one and a radio one), three "flash-all" script files, and yet another .zip file. Extract that .zip and the folder that it creates is the one you need to set the environment variable to.
Click to expand...
Click to collapse
Glad you got it fixed :good:
Another solution is use this guide and do #4 'keep data':
[Guide] Pixel XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + by Homeboy76

Update magisk failed, now can't boot anymore

Hey guys I have an unlocked google pixel 2 XL running TWRP 3.3.0.0, Resurection Remix V7.0.2. and for root I was using Magisk.
I updated Magisk using the recommended installation method. The installation failed, I don't fully remember the error, but it was something along the lines, "partition not found" . After that the magisk updater recommended that I reboot. I did so but now there is the error message "Your device is corrupt. It can't be trusted and may not work properly. Visit link on another device: g.co/ABH ". You can skip the message by hitting the power button. After that You get the normal unlock warning and then the phone got stuck in the google boot screen.
After that I tried entering the recovery but that also didn't work. The phone got stuck on the TWRP boot screen.
So next I tried to reflash the recovery but I got the following error:
Sending 'recovery' (40960 KB) OKAY [ 0.975s]
Writing 'recovery' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Now I still can't get into my recovery and if I select "Start" or "Restart bootloader" in the fastboot menu the phone will just return to the fastboot mode.
Any suggestion.

schpongo said:
Now I still can't get into my recovery and if I select "Start" or "Restart bootloader" in the fastboot menu the phone will just return to the fastboot mode.
Any suggestion.
Click to expand...
Click to collapse
First order of business is getting your OS working. Fastboot the factory image without the -w to see if that gets you going. Hopefully you made a backup of sorts before you started.

Badger50 said:
First order of business is getting your OS working. Fastboot the factory image without the -w to see if that gets you going. Hopefully you made a backup of sorts before you started.
Click to expand...
Click to collapse
I don't think I have a backup of the original firmware but I have a full nandroid backup from when I last successfully flashed the current OS. Would that also work and how would I go about that?

schpongo said:
I don't think I have a backup of the original firmware but I have a full nandroid backup from when I last successfully flashed the current OS. Would that also work and how would I go about that?
Click to expand...
Click to collapse
If you can get into twrp, which you stated you can't, it might work. However, I would first flash the magisk uninstaller zip if you can get into TWRP. If none of that works, then you'll have to fastboot the factory image without the -w so as to not wipe data. You may also try flashing the stock boot.img to see if it'll boot up as well before having to get too drastic with anything else :good:

schpongo said:
I don't think I have a backup of the original firmware but I have a full nandroid backup from when I last successfully flashed the current OS. Would that also work and how would I go about that?
Click to expand...
Click to collapse
I couldn't get in TWRP and uninstall Magisk. So I flashed the stock boot.img from the factory firmware. Sadly that also didn't help. Then I tried "fastboot flashall" but got the following error. Now I'm completely out of ideas. Is there any way to recovery my data and maybe also bring my phone back from the dead?
Daniels-MacBook-Pro:taimen-qq1a.191205.008 danielkurth$ fastboot flashall
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
--------------------------------------------
Bootloader Version...: TMZ20k
Baseband Version.....: g8998-00253-1805232234
Serial Number........: XXX
------------------------------------------
If you so kind to make any suggestions, please describe them in detail, I only play around with android from time to time and thus I'm not very familier with many things.
Thanks for the help.

schpongo said:
I couldn't get in TWRP and uninstall Magisk. So I flashed the stock boot.img from the factory firmware. Sadly that also didn't help. Then I tried "fastboot flashall" but got the following error. Now I'm completely out of ideas. Is there any way to recovery my data and maybe also bring my phone back from the dead?
Daniels-MacBook-Pro:taimen-qq1a.191205.008 danielkurth$ fastboot flashall
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
--------------------------------------------
Bootloader Version...: TMZ20k
Baseband Version.....: g8998-00253-1805232234
Serial Number........: XXX
------------------------------------------
If you so kind to make any suggestions, please describe them in detail, I only play around with android from time to time and thus I'm not very familier with many things.
Thanks for the help.
Click to expand...
Click to collapse
Ouch! Bummer man. What type of USB cable are you using? Hopefully not a USB C to USB C. You, unfortunately, may have to factory reset if nothing else works. Are your platform-tools up to date as well?

Badger50 said:
Ouch! Bummer man. What type of USB cable are you using? Hopefully not a USB C to USB C. You, unfortunately, may have to factory reset if nothing else works. Are your platform-tools up to date as well?
Click to expand...
Click to collapse
I wanted to try and get at my data so I:
1. Extracted the boot.img from the rom I was using. I did this with the payload extractor
2. Reflashed that boot.img
3. Set TWRP to boot via "fastboot boot twrp_XXX_img"
I got into the loading screen of TWRP and I have adb access but my sdcard folder seems empty. Is there any other place my data could be or is it maybe hidden or did I just lose it in the process?
Yes I'm using a usb-c to usb-c connection. Why does this matter?
How would I go about restoring my phone back to a factory state?

schpongo said:
I wanted to try and get at my data so I:
1. Extracted the boot.img from the rom I was using. I did this with the payload extractor
2. Reflashed that boot.img
3. Set TWRP to boot via "fastboot boot twrp_XXX_img"
I got into the loading screen of TWRP and I have adb access but my sdcard folder seems empty. Is there any other place my data could be or is it maybe hidden or did I just lose it in the process?
Yes I'm using a usb-c to usb-c connection. Why does this matter?
How would I go about restoring my phone back to a factory state?
Click to expand...
Click to collapse
USB-C to USB-C have been notorious for being rather "finicky" and not necessarily working in all cases. What does is USB-A to USB-C cables/cords -- seem to work in all cases.
I'm unsure as to why your data is not showing; whether it's not decrypting or not reading it... question;did you employ a screenlock/fingerprint lock before while the device was working? Because if you did, and it’s not asking for it to “decrypt”, then something more critical is going on and not being able to read your /data and/or /system
In any case, the main reason I wanted to chime in was to bring up something that you might be aware of already, but I wanted to confirm; when using Linux or macOS, you address the flash-all.sh file, and not attempt to launch the “flash-all.bat”.
However, it’s best if you could start from step 1 and download/re-download the Full Factory image, extract the .zip so it shows the 6 files within. Then, at this point and to make sure to cause no further issues, you should get rid of the flash-all.bat file – therefore only keeping the flash-all.sh and the flash-base.sh. Also, to retain any data, supposedly you would remove the “-w” from flash-all, but that’s how it goes for Windows and the flash-all.bat batch file; I’m unsure how to go about the same for Mac or Linux. After making sure you have the 5 correct files, move them on over to the platform-tools folder that contain the adb & fastboot .exe files – also, this would be a good time to make sure you have the most up-to-date platform-tools because, more often than not, not having the most up to date version is what usually causes most hiccups; latest version is “r29.0.5-darwin”.
And, after all of that, if you are still having issues, if you could post your output logs (if you remove the “exit” from the flash-all.bat file, it would keep the output window, but then again, that’s how to to it in a Windows environment…), it would be most helpful as to figuring out where/how things are going wrong. Usually/most likely it’s either platform-tools aren’t up-to-date or using different cords and/or on a different computer seems to be the resolutions at that point.
Hopefully this ends up being helpful…good luck!

Don't try to install twrp. Fastboot boot it

Question PocoF3 bricked. Please help.

I've googled and read posts for hours but nothing I tried works.
I was on Miui.eu V12.5.4.0 and decided to update to V12.5.5.0 using Twrp. It updated fine. However, I was not able to get my phone to root with magisk. So I dirty flashed back to V12.5.4.0 but for some reason when I tried to reboot to system, it prompted that no os is installed and I accidentally tapped reboot.
So now my phone is stuck on a boot loop on fastboot.
I tried Miflash tool. It ran for a few minutes but eventually got an error:Sending sparse 'userdata' 1/*3 (741188 KB) FAILED (Error reading sparse file).
I tried to use OTG on twrp but it seems like I can't access internal storage anymore. It shows up empty.
I tried to use adb sideload to push V12.5.4.0 rom into the phone but it says
loading: 'xiaomi.eu_multi_HMK40_POCOF3_V12.5.4.0.RKHCNXM_v12-11.zip'
* cannot read 'xiaomi.eu_multi_HMK40_POCOF3_V12.5.4.0.RKHCNXM_v12-11.zip' *
I did more digging and found this https://forum.xda-developers.com/t/q-adb-cant-read-sideload.1990405/page-3#post-69648733.
I tried to allow large address aware on adb and got this error instead
adb: failed to read command: No error
And the final method I tried was to use adb push to /sdcard/.
From the guides I saw online, after you typed in the command and press enter, a text stating the progress of the transfer should appear but mine did not. After a few minutes, this error appeared
"failed to copy 'xiaomi.eu_multi_HMK40_POCOF3_V12.5.4.0.RKHCNXM_v12-11.zip' to '/sdcard//xiaomi.eu_multi_HMK40_POCOF3_V12.5.4.0.RKHCNXM_v12-11.zip': write failed: No space left on device"
Any advice will really help. Thanks.

Zythol said:
I've googled and read posts for hours but nothing I tried works.
I was on Miui.eu V12.5.4.0 and decided to update to V12.5.5.0 using Twrp. It updated fine. However, I was not able to get my phone to root with magisk. So I dirty flashed back to V12.5.4.0 but for some reason when I tried to reboot to system, it prompted that no os is installed and I accidentally tapped reboot.
So now my phone is stuck on a boot loop on fastboot.
I tried Miflash tool. It ran for a few minutes but eventually got an error:Sending sparse 'userdata' 1/*3 (741188 KB) FAILED (Error reading sparse file).
I tried to use OTG on twrp but it seems like I can't access internal storage anymore. It shows up empty.
I tried to use adb sideload to push V12.5.4.0 rom into the phone but it says
loading: 'xiaomi.eu_multi_HMK40_POCOF3_V12.5.4.0.RKHCNXM_v12-11.zip'
* cannot read 'xiaomi.eu_multi_HMK40_POCOF3_V12.5.4.0.RKHCNXM_v12-11.zip' *
I did more digging and found this https://forum.xda-developers.com/t/q-adb-cant-read-sideload.1990405/page-3#post-69648733.
I tried to allow large address aware on adb and got this error instead
adb: failed to read command: No error
And the final method I tried was to use adb push to /sdcard/.
From the guides I saw online, after you typed in the command and press enter, a text stating the progress of the transfer should appear but mine did not. After a few minutes, this error appeared
"failed to copy 'xiaomi.eu_multi_HMK40_POCOF3_V12.5.4.0.RKHCNXM_v12-11.zip' to '/sdcard//xiaomi.eu_multi_HMK40_POCOF3_V12.5.4.0.RKHCNXM_v12-11.zip': write failed: No space left on device"
Any advice will really help. Thanks.
Click to expand...
Click to collapse
Press Power+Volume Down and go to fastboot and flash a fastboot rom. Should work

did you try fastboot format userdata ?

soneji said:
Press Power+Volume Down and go to fastboot and flash a fastboot rom. Should work
Click to expand...
Click to collapse
Do this to avoid actual bricking of your phone.
Safer ways always better

Thanks for the responses. I managed to fixed it with MiFlash Tool. The issue I had was that the Tool was using an older version of fastboot somewhere in my computer and not the latest that it came with. And that caused the flashing to fail because some commands didn't exist. I deleted the older version and it works. Thanks again!