Database Develop

[Q] Can only access bootloader. Soft brick?

Hey guys,
Today I attempted to root my HTC One. I successfully unlocked it and successfully flashed twrp 2.5 onto my phone. Without creating a backup and after flashing superuser and arhd 11.0 my phone would only boot into bootloader. Then I found I had trouble going back into recovery. I tried reflashing twrp and it worked and led me back into recovery. I was unable to find any of the ROMs I put into the internal memory and I get an error that says I am unable to mount data. I've tried flashing cwm recovery, which only lead to booting into bootloader, and then back to twrp which worked at first, but now I can't get either to work. I've been at this for hours. Hope any of you guys could help me out. Thanks in advance!
Also, I think my problem began by trying to flash arhd 11.0 from stock without doing a full wipe.
Update: Was able to get twrp to work again by clearing cache, but still unable to mount data.
This is an error i see inside twrp.
E : Unable to mount '/data'
E : Unable to recreate /data/media folder.
Updating partition details...
E : Unable to mount '/cache'
E : Unable to mount '/data'
E : Unable to mount internal storage.
E : Unable to mount /data/media during GUI startup
E : Unable to mount '/cache'
E: TWFunc : : Copy_Log -- Can't open destination
etc...
Click to expand...
Click to collapse
Update: SOLVED. Tried flashing Viper Rom and it worked great.

I believe that you install ARHD 11 from a 4.1 based rom, right? If that's the case, moving from 4.1 to 4.2 will mess up your data structure a bit. Because you have flashed arhd 11, all the rom files you had put earlier on 4.1 will be at other folder. My advice is you boot into twrp, open adb sideload (advance menu). On your computer use "adb sideload rom.zip" (rom.zip is the name of the rom you wanna flash). After it loaded the rom to the sd card, reboot to bootloader and you should see a file named sideloaded.zip. flash it. After finish, clear cache and reboot system.
or you can search in media/0
hope it helps

ryryzz said:
I believe that you install ARHD 11 from a 4.1 based rom, right? If that's the case, moving from 4.1 to 4.2 will mess up your data structure a bit. Because you have flashed arhd 11, all the rom files you had put earlier on 4.1 will be at other folder. My advice is you boot into twrp, open adb sideload (advance menu). On your computer use "adb sideload rom.zip" (rom.zip is the name of the rom you wanna flash). After it loaded the rom to the sd card, reboot to bootloader and you should see a file named sideloaded.zip. flash it. After finish, clear cache and reboot system.
or you can search in media/0
hope it helps
Click to expand...
Click to collapse
So I should sideload and flash a 4.1 based rom or a 4.2?
I've tried sideloading ARHD 11 and it brings me into the same bootloader loop. Could you send me a link to a ROM that may work?
Here's the steps I am taking if it helps;
1. fastboot erase cache
2. fastboot flash recovery twrp.img
3. go into recovery
4. adb sideload arhd11
5. reboot into recovery
6. flash sideload
7. reboot system
8. gives me a message saying my phone is not rooted would I like to install SuperSU now?
9. regardless of if i put 'do not install' or 'swipe to install' phone reboots into bootloader and I start over with the same problem
Click to expand...
Click to collapse

zasuncion said:
So I should sideload and flash a 4.1 based rom or a 4.2?
I've tried sideloading ARHD 11 and it brings me into the same bootloader loop. Could you send me a link to a ROM that may work?
Here's the steps I am taking if it helps;
Click to expand...
Click to collapse
Can you access recovery?
If yes, adb push name_of_rom.zip /sdcard/
rom will now be on your sdcard after the transfer. install it.
all roms using aroma installer crash sometimes, just keep trying.
edit: IF you can't find it, select install zip from sideload in recovery and command
adb sideload name_of_rom.zip
after the transfer it will begin to install automatically - you shouldn't need to reboot after a sideload.

redbull123 said:
Can you access recovery?
If yes, adb push name_of_rom.zip /sdcard/
rom will now be on your sdcard after the transfer. install it.
all roms using aroma installer crash sometimes, just keep trying.
Click to expand...
Click to collapse
Yes, I can access recovery. Just tried this. After flashing ARHD11 again I am still rebooting into bootloader.
Maybe it's just the ROM itself that I'm having trouble with? Could anyone direct me to one that will work for sure in my case?
Also after every flash, when I choose to reboot, twrp gives me a message saying my phone is not rooted and if I should install SuperSU. Should I say yes or not install? or is there a problem with flashing the ROM?

zasuncion said:
Yes, I can access recovery. Just tried this. After flashing ARHD11 again I am still rebooting into bootloader.
Maybe it's just the ROM itself that I'm having trouble with? Could anyone direct me to one that will work for sure in my case?
Also after every flash, when I choose to reboot, twrp gives me a message saying my phone is not rooted and if I should install SuperSU. Should I say yes or not install? or is there a problem with flashing the ROM?
Click to expand...
Click to collapse
So ARHD goes through and installs (as in gets to 100% in aroma) then reboots to bootloader?
Sent from my HTC One using xda premium

redbull123 said:
So ARHD goes through and installs (as in gets to 100% in aroma) then reboots to bootloader?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Yes. And the only way to get back into recovery from there is to reflash. I also can't use cwm, I can only use twrp. If that means anything.

HTC One Soft bricked many problems leading to more problems!

Ok So I have an HTC One m7. and I had CyanogenMod installed. Then jsut today I decided I would go back to Sense 6. So I download Android Revolution HD 71.1 for m7 install it on my phoen. Then CWM(Which I hate btw and can't uninstall no matter what I do) says your phone is not rooted would you like to root it when I click reboot phone. No matter which I click I get stuck on the HTC logo boot logo. I don't care if I lose my data or anything so I click factory reset, then wipe cache, then wipe dalvik cache. Then I get the error were it constantly says cant mount /cache or whatever. So to fix it i wipe Dalvik Cache again. Then I try sideloading ViperOne Rom. Guess what It give me *failed to write 'protocol fault <no status> *
Then I tried formatting my data with CWM which took 2 hours and still didn't complete so I rebooted(which led to more problems) Now I cant say install from sdcard because it gives me the error E: Can't Mount /sdcard. So that means I cant adb push Viper /sdcard. I have no Idea what to do. Help me please!

radsherwin said:
Ok So I have an HTC One m7. and I had CyanogenMod installed. Then jsut today I decided I would go back to Sense 6. So I download Android Revolution HD 71.1 for m7 install it on my phoen. Then CWM(Which I hate btw and can't uninstall no matter what I do) says your phone is not rooted would you like to root it when I click reboot phone. No matter which I click I get stuck on the HTC logo boot logo. I don't care if I lose my data or anything so I click factory reset, then wipe cache, then wipe dalvik cache. Then I get the error were it constantly says cant mount /cache or whatever. So to fix it i wipe Dalvik Cache again. Then I try sideloading ViperOne Rom. Guess what It give me *failed to write 'protocol fault <no status> *
Then I tried formatting my data with CWM which took 2 hours and still didn't complete so I rebooted(which led to more problems) Now I cant say install from sdcard because it gives me the error E: Can't Mount /sdcard. So that means I cant adb push Viper /sdcard. I have no Idea what to do. Help me please!
Click to expand...
Click to collapse
its simple to fix, your problem is simply cwm recovery, you need to use twrp to flash either of those rom's, so start there, recommended is 2.6.3.3, its the most problem free.
Code:
fastboot flash recovery recovery_name.img
fastboot erase cache
fastboot reboot-bootloader
then enter recovery, select wipe then format data, push or sideload a rom then flash it.
ViperOne Install Instructions
1. Download the the latest ViperOne full ROM zip from the download section
2. Place the file somewhere on your phone storage. Alternatively, if you have a USB OTG cable (I have this exact one), you can place the rom on a USB key (FAT32, NTFS are all supported).
3. Confirm the MD5 on the download page matches the MD5 of the file on your phone (ES File Explorer will show the MD5 of the file)
4. Reboot to TWRP Recovery
5. Backup current ROM if desired
6. Install ROM using TWRP and select wipe during aroma install if coming from another base
7. Reboot and Enjoy

Seanie280672 said:
its simple to fix, your problem is simply cwm recovery, you need to use twrp to flash either of those rom's, so start there, recommended is 2.6.3.3, its the most problem free.
Code:
fastboot flash recovery recovery_name.img
fastboot erase cache
fastboot reboot-bootloader
then enter recovery, select wipe then format data, push or sideload a rom then flash it.
ViperOne Install Instructions
1. Download the the latest ViperOne full ROM zip from the download section
2. Place the file somewhere on your phone storage. Alternatively, if you have a USB OTG cable (I have this exact one), you can place the rom on a USB key (FAT32, NTFS are all supported).
3. Confirm the MD5 on the download page matches the MD5 of the file on your phone (ES File Explorer will show the MD5 of the file)
4. Reboot to TWRP Recovery
5. Backup current ROM if desired
6. Install ROM using TWRP and select wipe during aroma install if coming from another base
7. Reboot and Enjoy
Click to expand...
Click to collapse
Ok I'm currently sideloading ViperRom but at first it was stuck at 2% so I cancelled it now it's stuck at 26% for like 30 min

radsherwin said:
Ok I'm currently sideloading ViperRom but at first it was stuck at 2% so I cancelled it now it's stuck at 26% for like 30 min
Click to expand...
Click to collapse
did you format data first ? any unable to mount messages, you could also try advanced wip and select everything in the list.
try pushing it instead
with the phone in twrp main screen only, no sub menu's and the rom in the same folder as adb and fastboot on your computer type:
Code:
adb push (name_of_rom).zip /sdcard/
takes a while and will look unresponsive, but the cmd window will let you know when its done. Make sure you unplug your phone before flashing.

Seanie280672 said:
did you format data first ? any unable to mount messages, you could also try advanced wip and select everything in the list.
try pushing it instead
with the phone in twrp main screen only, no sub menu's and the rom in the same folder as adb and fastboot on your computer type:
Code:
adb push (name_of_rom).zip /sdcard/
takes a while and will look unresponsive, but the cmd window will let you know when its done. Make sure you unplug your phone before flashing.
Click to expand...
Click to collapse
ok I 've been sitting here for a while and the cmd prompt just shows a blinking line under my command. The file is in my sdcard but is it complete?

Seanie280672 said:
did you format data first ? any unable to mount messages, you could also try advanced wip and select everything in the list.
try pushing it instead
with the phone in twrp main screen only, no sub menu's and the rom in the same folder as adb and fastboot on your computer type:
Code:
adb push (name_of_rom).zip /sdcard/
takes a while and will look unresponsive, but the cmd window will let you know when its done. Make sure you unplug your phone before flashing.
Click to expand...
Click to collapse
also it doesnt let me format data wipe. It gives me error like E: Unable to mount '/cache/

radsherwin said:
also it doesnt let me format data wipe. It gives me error like E: Unable to mount '/cache/
Click to expand...
Click to collapse
with your phone in fastboot, type fastboot format cache

Seanie280672 said:
with your phone in fastboot, type fastboot format cache
Click to expand...
Click to collapse
doesn't work either.. I tried everything nothing is working. I can't even get ViperOne Rom on my phone.

anyone? I need help! I'm looking all over the internet for solutions and apparently every has solved their problem but me. HELP!

Seanie280672 said:
with your phone in fastboot, type fastboot format cache
Click to expand...
Click to collapse
anymore help? When ever I try to ADB sideload It gets stuck on 1% forever. Whenever I try to adv push it does nothing and doesnt tell me anything. everytime I try to format It says successful but it still gives me error saying E: / cant mount cache. PLEASE HELP ME

radsherwin said:
anyone? I need help! I'm looking all over the internet for solutions and apparently every has solved their problem but me. HELP!
Click to expand...
Click to collapse
I recommend you start from scratch
from the bootloader / power down
wait a couple min and boot back to fastboot
plug the phone into the PC
from your command prompt type
fastboot devices
see your device serial number
type
fastboot erase cache
type
fastboot reboot-bootloader
now try sideload your rom from TWRP 2.6.3.3 /advanced/sideload

clsA said:
I recommend you start from scratch
from the bootloader / power down
wait a couple min and boot back to fastboot
plug the phone into the PC
from your command prompt type
fastboot devices
see your device serial number
type
fastboot erase cache
type
fastboot reboot-bootloader
now try sideload your rom from TWRP 2.6.3.3 /advanced/sideload
Click to expand...
Click to collapse
when I try fastboot erase cache it says
"******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (status read failed (Too many links))
finished. total time: 0.293s

So you have CWM / TWRP installed? Try copying a ROM to the external SD card, and install it that way. Clear everything in recovery first, cache, dalvik, etc... I had the same problem with the M8 and it drove me nuts until I did it all from the SD. If not, I would suggest trying the full RUU, it has saved me many a time.

hack14u said:
So you have CWM / TWRP installed? Try copying a ROM to the external SD card, and install it that way. Clear everything in recovery first, cache, dalvik, etc... I had the same problem with the M8 and it drove me nuts until I did it all from the SD. If not, I would suggest trying the full RUU, it has saved me many a time.
Click to expand...
Click to collapse
I have the m7 not the m8. So I have no sd card. What is the RUU method? I have TWRP installed right now.

This is getting on my nerves. Ive been sitting here for 6 hours and I posted 4 times and I still have not fixed this problem!!!!!!!! No one can explain clearly or respond to me even. Half my problems are being ignored. and half the things I say are being ignored.

radsherwin said:
I have the m7 not the m8. So I have no sd card. What is the RUU method? I have TWRP installed right now.
Click to expand...
Click to collapse
Oh that's right dang it. When I had my M7 I converted it to a Dev Edition by changing the CID and then using a file like this:
http://dl4.htc.com/RomCode/Source_and_Binaries/m7ul-3.4.10-g77e9ea0.zip
Mine was an ATT version so MID matched.
---------- Post added at 07:28 PM ---------- Previous post was at 07:27 PM ----------
radsherwin said:
This is getting on my nerves. Ive been sitting here for 6 hours and I posted 4 times and I still have not fixed this problem!!!!!!!! No one can explain clearly or respond to me even. Half my problems are being ignored. and half the things I say are being ignored.
Click to expand...
Click to collapse
Hey, hey, hey, patience my friend, we are here to help, ALL of us, we are trying.
Scratch that link, it doesn't like direct posts, find the Brighstar WWE RUU by searching at: http://www.htcdev.com/devcenter/downloads, or find the ATT, or TMobile. Not sure what your carrier is, but the Dev Edition is the way to go.

hack14u said:
Oh that's right dang it. When I had my M7 I converted it to a Dev Edition by changing the CID and then using a file like this:
http://dl4.htc.com/RomCode/Source_and_Binaries/m7ul-3.4.10-g77e9ea0.zip
Mine was an ATT version so MID matched.
---------- Post added at 07:28 PM ---------- Previous post was at 07:27 PM ----------
Hey, hey, hey, patience my friend, we are here to help, ALL of us, we are trying.
Click to expand...
Click to collapse
The link just sends me to the htc website. Also what does converting my m7 to dev edition do exactly? Will it help with the Sideload problem or the cant mount cache problem?
And I know you guys are trying to help me. Im just mad because everything I do is not working. Im searching all over the internet and nothing is helping. Errors lead to more errors. Reminds me of the time I tried learning progrramming and I made a simple program but It wouldnt work. I posted it on 3 websites and no one could help me. So I'm sorry for going off like that.

radsherwin said:
The link just sends me to the htc website.
And I know you guys are trying to help me. Im just mad because everything I do is not working. Im searching all over the internet and nothing is helping. Errors lead to more errors. Reminds me of the time I tried learning progrramming and I made a simple program but It wouldnt work. I posted it on 3 websites and no one could help me. So I'm sorry for going off like that.
Click to expand...
Click to collapse
I know it can be frustrating, but nothing you can do to the M7 can hurt it. Try the link above HTC doesn't like direct links.

hack14u said:
I know it can be frustrating, but nothing you can do to the M7 can hurt it. Try the link above HTC doesn't like direct links.
Click to expand...
Click to collapse
ok im doing it right now. Im AT&T btw.
I seem to have fixed the E: Can't mount cache problem. All i did was go to advance and click only on cache. Now all I need is to sideload or pus my ViperOne rom over to my HTC. Then hopefully nothing goes wrong. What do I do once the zip file is done downloading?

That might not be the right one, it should be an exe around 1 GB in size, sorry. Look around for it, if it's not still posted at the HTC Dev site, then it is around here somewhere. There are also some nandroids I have seen that should help you restore to stock. Nonetheless, once you have that Viper Rom on there, you should be able to flash anything you want. A full RUU will restore your phone to the state in which you bought it in, just like brand new.

htc1 m7 keeps rebooting and won't detect network

Last week after software update using auto update Option , after installing the softare , the phone will keep rebooting and won't detect the network. I guess that my phone battery was low at the time of installation(10%) however it was connected to a charger. The problem is after turning on the phone, the phone will reboot after aprox. 1minute 50 seconds and the htc1 won't show network. The settings option in network setting would appear greyed out.
After this problem, I tried factory reset, no avail. Tried recovery from bootloader option but no avail.
Tried Using RUU- RUU_M7_U_JB_50_HTC_Europe_1.29.401.2_R_Radio_4A.14.3250.13_10.33.1150.01_release_311663_signed_2_4
Gives me error 155 in Update Utility.
After searching the threads, I decided to unlock and unroot the phone so that I could install any custom ROMs, did unlocking and unrooting.
My htc1 m7 with following specs now
Tampered
Unlocked
M7_U S-On
Hboot- 1.57.0000
Radio0- 4T.28.3218.04
OS-6.15.599.101
Android version 4.4.3 and Sense 6

Some guys recommended me to post my query on xda and I came here with lots of hopes. Unfortunately after couple of days no one from expert community has responded to this query.

htc1resetting said:
Some guys recommended me to post my query on xda and I came here with lots of hopes. Unfortunately after couple of days no one from expert community has responded to this query.
Click to expand...
Click to collapse
you not being ignored, their is no real answer to your problem
you can flash stock recovery for 6.15.599.101 if you can find it
and try the factory reset from stock recovery (not bootloader)
If you have TWRP 2.6.3.3 or higher on the phone now you can choose to format data and then push / sideload a 6.xx.xxx.x rom to the phone. Their are no 6.xx RUU so that's not an option. If the phone died during the update theirs no telling what partitions are damaged so the format data option is your first step

clsA said:
you not being ignored, their is no real answer to your problem
you can flash stock recovery for 6.15.599.101 if you can find it
and try the factory reset from stock recovery (not bootloader)
If you have TWRP 2.6.3.3 or higher on the phone now you can choose to format data and then push / sideload a 6.xx.xxx.x rom to the phone. Their are no 6.xx RUU so that's not an option. If the phone died during the update theirs no telling what partitions are damaged so the format data option is your first step
Click to expand...
Click to collapse
Firstly loads of thanks.
I have tried hard to find 6.15.599.101 RUU but no success.
I should use the second option to push 6.xx.xx.x rom, can you advice where can I find it. I get confused between kernel & OTA, which one is a ROM or neither one?

htc1resetting said:
Firstly loads of thanks.
I have tried hard to find 6.15.599.101 RUU but no success.
I should use the second option to push 6.xx.xx.x rom, can you advice where can I find it. I get confused between kernel & OTA, which one is a ROM or neither one?
Click to expand...
Click to collapse
Use this >> http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_81.0.zip
adb push Android_Revolution_HD-One_81.0.zip /sdcard/
or adb sideload Android_Revolution_HD-One_81.0.zip

My device is already formatted and I can only access bootloader(TWRP recovery) and if I boot the phone it gives me white htc screen.
I have downloaded the Android_Revolution_HD-One_81.0 fastboot works fine however adb won't detect my device. I have sdk tools from adroid.development and the latest version of adt tools.

htc1resetting said:
My device is already formatted and I can only access bootloader(TWRP recovery) and if I boot the phone it gives me white htc screen.
I have downloaded the Android_Revolution_HD-One_81.0 fastboot works fine however adb won't detect my device. I have sdk tools from adroid.development and the latest version of adt tools.
Click to expand...
Click to collapse
boot into TWRP
from the PC command prompt
type adb devices
if it's blank you need to reinstall the htc driver
if your device serial number shows it's working normally

When I use the adb command- where should my phone be? adbsideload? fastboot?
The adb won't detect my device even with htc drivers re-installed. When I use the adb sideload button in the TWRP , it stays there for ever.
Can we use fastboot command to flash the ROM, the way we flash recovery?

htc1resetting said:
When I use the adb command- where should my phone be? <<< TWRP
The adb won't detect my device even with htc drivers re-installed. When I use the adb sideload button in the TWRP , it stays there for ever.
Can we use fastboot command to flash the ROM, the way we flash recovery? << NO
Click to expand...
Click to collapse
Go to post 2 of @nkk71 superguide to install the drivers correctly > http://forum.xda-developers.com/showthread.php?t=2541082

Finally I was able to sideload- adb sideload Android_Revolution_HD-One_81.0.zip
After the sideload was 100% my phone was black screen, was no more in recovery TWRP.
What next step to take?
When I restarted the phone, it will again show the white HTC screen , won't go ahead and boot.
I am s-on and with TWRP 2.8.0.1 recovery.

htc1resetting said:
Finally I was able to sideload- adb sideload Android_Revolution_HD-One_81.0.zip
After the sideload was 100% my phone was black screen, was no more in recovery TWRP.
What next step to take?
When I restarted the phone, it will again show the white HTC screen , won't go ahead and boot.
I am s-on and with TWRP 2.8.0.1 recovery.
Click to expand...
Click to collapse
use TWRP 2.6.3.3

Using twrp, 2.6.3- I sideloaded adb sideload Android_Revolution_HD-One_81.0.zip
By the time sideload= 100% on cmd
Phone recovery-twrp showed, zip sign verification failed.
Screen shows as follows:
Updating partition details...
Starting ADB sideload feature...
Installing 'dataa/media/sideload.zip
checking for md5 flile....
skipping md5 check: no MD5 file found
Verifying zip signature...
E: zip signature verification failed.
I unchecked zip file verification from settings and this time was able to complete, followed the step by step installation. After the installation was complete, cleared cache and dalvi and performed system boot. The phone restarts but its again stuck at white htc screen.

clsA said:
use TWRP 2.6.3.3
Click to expand...
Click to collapse
Using twrp, 2.6.3- I sideloaded adb sideload Android_Revolution_HD-One_81.0.zip
By the time sideload= 100% on cmd
Phone recovery-twrp showed, zip sign verification failed.
Screen shows as follows:
Updating partition details...
Starting ADB sideload feature...
Installing 'dataa/media/sideload.zip
checking for md5 flile....
skipping md5 check: no MD5 file found
Verifying zip signature...
E: zip signature verification failed.

htc1resetting said:
Using twrp, 2.6.3- I sideloaded adb sideload Android_Revolution_HD-One_81.0.zip
By the time sideload= 100% on cmd
Phone recovery-twrp showed, zip sign verification failed.
Screen shows as follows:
Updating partition details...
Starting ADB sideload feature...
Installing 'dataa/media/sideload.zip
checking for md5 flile....
skipping md5 check: no MD5 file found
Verifying zip signature...
E: zip signature verification failed.
Click to expand...
Click to collapse
your download is corrupt ..download it again and md5 check your downloads

clsA said:
your download is corrupt ..download it again and md5 check your downloads
Click to expand...
Click to collapse
Made another attempt to sideload and it was successful, phone booted and rebooted. Phone turned on but again restarted after few seconds, the same way it was behaving earlier. Any suggestions?
I was checking htc Dev site, it has download section with my OS version no. 6.15.599.101- is there something I can do with this file to get my phone working.? m7u-3.4.10-ga936d02.zip is the file.
What are options to get RUU for 6.15.599.101 ?

htc1resetting said:
Made another attempt to sideload and it was successful, phone booted and rebooted. Phone turned on but again restarted after few seconds, the same way it was behaving earlier. Any suggestions?
I was checking htc Dev site, it has download section with my OS version no. 6.15.599.101- is there something I can do with this file to get my phone working.? m7u-3.4.10-ga936d02.zip is the file.
What are options to get RUU for 6.15.599.101 ?
Click to expand...
Click to collapse
You still never tried the stock recovery / factory reset
maybe you can extract it from that file
maybe @Danny201281 could help you check and repair your partition's if he has time

I tried factory reset and stock recovery at my first step long time ago. Only after failing, I tried the TWRP recovery and Android Revolution.

htc1resetting said:
My device is already formatted and I can only access bootloader(TWRP recovery) and if I boot the phone it gives me white htc screen.
I have downloaded the Android_Revolution_HD-One_81.0 fastboot works fine however adb won't detect my device. I have sdk tools from adroid.development and the latest version of adt tools.
Click to expand...
Click to collapse
When you say it's formatted are you sure about that?
Format Data is not the same as Factory reset or Wiping partitions. You need to use the Format Data option in twrp to be sure. So in case you haven't already and probably wouldn't hurt to do it again anyway.
Boot into twrp recovery Select the Wipe option and then Format Data option. You will be prompted to type "yes" to confirm. This will wipe everything from your device including your Rom and internal storage. Reboot to recovery to restore a completely new file system to your device.
Now with the phone still in twrp recovery, Select the Mounts option and uncheck all the boxes to unmount the partitions. Return to the twrp home screen (you don't need sideload mode for this part) in the command line type
Code:
adb shell
e2fsck -fvy dev/block/mmcblk35
e2fsck -fvy dev/block/mmcblk36
e2fsck -fvy dev/block/mmcblk37
exit
Once that's done you can push or Sideload your Rom. Personally I prefer the push method but which is easiest for you is fine.
Ideally you want to do a factory reset with Stock recovery also but since you can't find one unless you can extract it from the file on HTC dev just try the above.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
When you say it's formatted are you sure about that?
Format Data is not the same as Factory reset or Wiping partitions. You need to use the Format Data option in twrp to be sure. So in case you haven't already and probably wouldn't hurt to do it again anyway.
Boot into twrp recovery Select the Wipe option and then Format Data option. You will be prompted to type "yes" to confirm. This will wipe everything from your device including your Rom and internal storage. Reboot to recovery to restore a completely new file system to your device.
Now with the phone still in twrp recovery, Select the Mounts option and uncheck all the boxes to unmount the partitions. Return to the twrp home screen (you don't need sideload mode for this part) in the command line type
Code:
adb shell
e2fsck -fvy dev/block/mmcblk35
e2fsck -fvy dev/block/mmcblk36
e2fsck -fvy dev/block/mmcblk37
exit
Once that's done you can push or Sideload your Rom. Personally I prefer the push method but which is easiest for you is fine.
Ideally you want to do a factory reset with Stock recovery also but since you can't find one unless you can extract it from the file on HTC dev just try the above.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
I was using the format data option before as well.
This time, followed the step by step procedure and installed the OS, the phone booted again but it restarts after sometime as it was at the beginning of the problem. Any suggestions?

htc1resetting said:
I was using the format data option before as well.
This time, followed the step by step procedure and installed the OS, the phone booted again but it restarts after sometime as it was at the beginning of the problem. Any suggestions?
Click to expand...
Click to collapse
When the phone is booting, does it take longer than normal? And does it bootloop before finally booting.
Unfortunately this is starting to sound like a hardware problem. After formatting the memory, repairing partitions with e2fsck and flashing a new Rom there's not much else can be done. If your still getting random reboots then something is defiantly a miss.
You can check your supersu app to make sure is properly rooted, by opening supersu, it may ask you to update the Binary's.
Or just flash this in recovery to make sure your on the latest.
http://download.chainfire.eu/452/SuperSU/
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

failed to mount /data (Invalid argument)

Hi,
I just installed Huawei P9 [ROM][6.0] fRomFuture - NewWorld V2 and the phone boots and works fine, but I cant update Su binary because of this error in TWRP ( I have unlocked bootloader and root):
failed to mount /data (Invalid argument)

Just clear the notification on each restart, don't try and update the SU Binary. It's a known issue
See the rom's thread
And re the TWRP issue, are you using the latest one from @paulobrien? 3.0.2.0 RC3?

colthekid said:
Just clear the notification on each restart, don't try and update the SU Binary. It's a known issue
See the rom's thread
And re the TWRP issue, are you using the latest one from @paulobrien? 3.0.2.0 RC3?
Click to expand...
Click to collapse
Thank you, nope I was using the one from SRK TOOL. Do you know how to install TWRP via Paul, its a img file (i'll have a hunt for his copy)

In twrp, go install, choose install image, choose file, select partition recovery and done
Other method with pc-fastboot command -> fastboot flash recovery blabla.img this method need root with stock rom. Custom roms already rooted so dont worry

Milamber said:
Thank you, nope I was using the one from SRK TOOL. Do you know how to install TWRP via Paul, its a img file (i'll have a hunt for his copy)
Click to expand...
Click to collapse
Don't know if the Tool is using the latest version. Paul's is here ... http://forum.xda-developers.com/p9/development/wip-twrp-support-t3372331 still has some issues backing up, but best we have at the mo.
you can either flash as @master' suggests or via adb
adb reboot-bootloader
fastboot flash recovery twrp-3.0.2-0-eva-modaco-rc3.img
fastboot reboot
edit: beaten to it! :highfive:

colthekid said:
Don't know if the Tool is using the latest version. Paul's is here ... http://forum.xda-developers.com/p9/development/wip-twrp-support-t3372331 still has some issues backing up, but best we have at the mo.
you can either flash as @master' suggests or via adb
adb reboot-bootloader
fastboot flash recovery twrp-3.0.2-0-eva-modaco-rc3.img
fastboot reboot
edit: beaten to it! :highfive:
Click to expand...
Click to collapse
Thanks to both of you from Australia!

Hi. when I try backup system ihad message : "createTarFork () process ended with error :255"
What`s wrong?
Last messages from log
I:addFile '/data/hw_init/system/emui' including root: 0
==> set selinux context: ubject_r:system_data_file:s0
I:addFile '/data/hw_init/system/emui/base' including root: 0
I:Error adding file '/data/hw_init/system/emui/base' to '/external_sd/TWRP/BACKUPS/MWS0216C19000719/2017-03-15--12-38-32//data.f2fs.win'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/external_sd/TWRP/BACKUPS/MWS0216C19000719/2017-03-15--12-38-32/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup
Click to expand...
Click to collapse
ok. I changed SD card ,formated it in phone and did backup by TWRP-3.0.2-0-eva. Now I think all done good. Last question is what about this red alert at the end of log?
Unmounting main partitions...
Failed to unmount '/system' (Device or resource busy)
Click to expand...
Click to collapse

RECOVERY - postrecoveryboot.sh - ERROR: 2

Google has no answer for me.
Every time I enter into the recovery and push the message button I get this ERROR: 2.
Everything works fine, its latest TWRP 3.0.2.
Could you tell me something about this error message 2?
What is 'postrecoveryboot.sh'?
How can I get this red message off / without error?
thanx in advance

How do I edit my boot script?

MichaBit said:
Google has no answer for me.
Every time I enter into the recovery and push the message button I get this ERROR: 2.
Everything works fine, its latest TWRP 3.0.2.
Could you tell me something about this error message 2?
What is 'postrecoveryboot.sh'?
How can I get this red message off / without error?
thanx in advance
Click to expand...
Click to collapse
Hi,
I have the same problem. Also on TWRP 3.0.2. and everything seems to work.
Can't find anything about this 'postrecoveryboot.sh' Error 2.
Did you find a solution in the meantime?
Thanks for any help in advance.

Arninho said:
Did you find a solution in the meantime?
Click to expand...
Click to collapse
No, unfortunately not.
If XDA has no solution, who else?

I have the same problem, this is inside the file
Code:
#!/sbin/sh
# Include device-specific vars
source /sbin/bootrec-device
# Turn the LED off
echo 0 > ${BOOTREC_LED_RED}
echo 0 > ${BOOTREC_LED_GREEN}
echo 0 > ${BOOTREC_LED_BLUE}
that error is because this file bootrec-device located at sbin folder always missing when reboot system or recovery
I have try many way
-flash stock rom with flashtool
-flash rom via recovery
-wipe via adb and fastboot
-chmod this file bootrec-device to read only
-remove this file postrecoveryboot.sh just come back after reboot recovery
all that way doesn't work
my Xperia unable to boot right know :crying:
maybe i'll try search what's file that create this??? postrecoveryboot.sh
where's boot script locate???
any help would be apreciated

InAMovies said:
my Xperia unable to boot right know :crying:
Click to expand...
Click to collapse
Thanks for that much information. :good:
A possible 'emergency solution' so that your device reboots again could be attached link.
What really surprised me, no one else has this ERROR: 2, and if not, why not?
http://www.flashtool.net/index.php

You can fix this 'postrecoveryboot.sh' Error 2 with a lower version twrp
I use twrp 2.8.7 which has been uploaded by someone from here androidfilehost.com/?fid=24052804347811669
flash with "fastboot flash boot boot.img" only if you UB, on LB try downgrade your twrp version
and then via file manager, just chmod the file bootrec-device located at sbin folder with read only access
my phone can only be booted only with rom existenz, and it was frequently rebooted and my battery status is unclear, sometimes 65% during the initial boot, and then only a 5% reboot afterwards
I have flash using flashtool with many based rom from 10.5.1.A, 10.6.1.A, 10.7.1.A latest, but it still does not make my phone work just to show sony screen flickered and died with the indicator is still red
all the problems occurred after I had this problem 'postrecoveryboot.sh' Error 2
I still do not know how to turn off the script, when I delete the file after reboot definitely go back there
hoping my phone can be normal again sometime

InAMovies said:
I still do not know how to turn off the script, when I delete the file after reboot definitely go back there
Click to expand...
Click to collapse
Could the cause for the error be a kind of provider branding?
So deeper implemented than the usual firmware.
My device was delivered via German Telekom.

[B]Solution![/B]
After installing Multirom v33 the error message is gone!
Dont ask why, both recoverys, the new one into the FOTA partition from attached link und the older, normal one 3.0.2.0 are error-free! :good:
https://forum.xda-developers.com/xperia-z/orig-development/mod-multirom-v33x-xperia-z-t3432385

I have installed the Modified recovery FOTA, before this error happen all working fine any custom rom working
but after this error, i can boot into recovery and install rom then reboot got bootloop, charger just show blip screen logo
just wanna try your idea with the Multirom v33 non modified

MichaBit said:
Google has no answer for me.
Every time I enter into the recovery and push the message button I get this ERROR: 2.
Everything works fine, its latest TWRP 3.0.2.
Could you tell me something about this error message 2?
What is 'postrecoveryboot.sh'?
How can I get this red message off / without error?
thanx in advance
Click to expand...
Click to collapse
Can You be so Kind to tell me how to flash in the correct way the latest version of TWRP with no error? Thank You very much!!

Ricky_Karmator said:
Can You be so Kind to tell me how to flash in the correct way the latest version of TWRP with no error? Thank You very much!!
Click to expand...
Click to collapse
Download latest recovery 'twrp-3.0.2-0-yuga.img' from link 1.
Put it to your Phone, turn of, push volume + and insert USB-cable for flashmode.
Blue LED-light appears.
Type -fastboot flash boot boot.img
-fastboot reboot
in ADB-connection CMD on your PC --> thats all.
Optional you can use the Tool in link 2.
*Flashing recovery successfully*
https://dl.twrp.me/yuga/
https://twrp.me/app/

MichaBit said:
Download latest recovery 'twrp-3.0.2-0-yuga.img' from link 1.
Put it to your Phone, turn of, push volume + and insert USB-cable for flashmode.
Blue LED-light appears.
Type -fastboot flash boot boot.img
-fastboot reboot
in ADB-connection CMD on your PC --> thats all.
Optional you can use the Tool in link 2.
*Flashing recovery successfully*
https://dl.twrp.me/yuga/
https://twrp.me/app/
Click to expand...
Click to collapse
I wa sure to copy the .img file in "platform-tools" folder in my PC and with cmd type "-fastboot flash boot boot.img" and not to have the file inside the internal memory of my Xperia Z. Obviously i think to rename "Twrp-3.0.blablabla" into boot.img

Ricky_Karmator said:
I wa sure to copy the .img file in "platform-tools" folder in my PC and with cmd type "-fastboot flash boot boot.img" and not to have the file inside the internal memory of my Xperia Z. Obviously i think to rename "Twrp-3.0.blablabla" into boot.img
Click to expand...
Click to collapse
Yes, very correct, copy and rename the file into 'boot.img' to your ADB-folder and flash it. :angel:

Finally with some free time i unlocked and flash the latest TWRP on my old Xperia Z. And yes i've got the same error "ERROR: 2". But everything works from backup to restore and flash Custom ROM. So i think we can nevermind about that

I have the same.
Sometimes my phone randomly reboot, and seems to be some app cause this reboots.
It was happend more and more often. And suddenly couple days ago my phone start to bootloop (just endlesly booting at xperia logo).
I have F5121 stock 8.0 Oreo and done all like in this manual https://forum.xda-developers.com/t/...els-latest-34-4-a-2-118-25-sept-2018.3594502/
So I was have rooted kenrnel twrp 3.2.3.0+DRM-Fix +magisk +FCS_1.3 +debloat script.
Almost 2 years of no problems and this surprise.
When I load to twrp and press menu button i see this:
Updating partition details...
...done
Unable to mount storage
So I was trying do backup of all partitions and after that I go in in wipe menu => advanced wipe => checkbox cache partition => fix patition
than I try to fix all patitions - it doesn't help.
So I do this:
wipe menu => advanced wipe => checkbox data partition => change to exFAT filesystem then => change back to EXT4 filesystem and restore data from backup. And do system/data partitions
and try to restore my backup - and it don't work.
EVEN my older backups don't works - I always become bootloop on xperia logo.
When I download twrp backup to PC and unpack cache.ext4.win\recovery I see file with name last_log.
Thats how last strings of file last_log look like:
~
ro.bootimage.build.date.utc=1533015130
ro.bootimage.build.fingerprint=Sony/omni_suzu/suzu:8.1.0/OPM4.171019.021.R1/4:eng/test-keys
ro.bootloader=s1
ro.debuggable=1
ro.property_service.version=2
init.svc.adbd=running
init.svc.ueventd=running
init.svc.recovery=running
init.svc.ldconfigtxt=stopped
init.svc.set_permissive=stopped
twrp.crash_counter=0
keyguard.no_require_sim=true
tombstoned.max_tombstone_count=50
Running boot script...
I:/sbin/postrecoveryboot.sh process ended with RC=0
Done.
I would like to hear some ideas why that may happen (Unable to mount storage). Coz i lost part of my data and don't wanna have the same experience again and again in future.