Database Develop

[Q] soft bricked HTC One with no OS installed

Hi ALL!
First off I'd like to say thanks for such a forum! Its the first go to place for me for anything android.
Yesterday I did something terrible and very careless from my side. I un-intentionally deleted the /system partition on my HTC One while playing with it and now I am paying for my careless mistake. I have been looking for possible solutions here on this forum and elsewhere on the internet. I did manage to do an *adb sideload push* of a custom ROM and tried to install that but for some reason I cant mount some partitions from my sdcard for example /cache.
I tried exchanging between TWRP (latest) and CWM (touch latest) but no solution so far with the adb sideload method. So I have no OS installed on my phone and the phone sometimes hangs in the HTC Quietly Brilliant display page or sometimes it wouldnt even go in to the Recovery mode but keeps rebooting.
I am clueless at this point, please shade some light on my situation.
In the attached pic you'd find the output from the *fastboot getvar all* command and the phone is S-ON and Unlocked just to mention.
I really appreciate it...

What is the exact error when installing the ROM?
What ROM?
sent from my mobile device

SaHiLzZ said:
What is the exact error when installing the ROM?
What ROM?
sent from my mobile device
Click to expand...
Click to collapse
I tried installing Android_Revolution_HD-One_51.0 and One_4.18.401.8_odexed ROMS. I tried installing the Android_Revolution_HD ROM by adb sideload method both for the CWM and TWRP recoveries and it would actually start the AROMA installer and goes on to install but its premature installation. It just finishes fast (sometimes with a success flag but mostly with an error message saying META_INF error -- sorry i havent logged that error, so I am not putting the right wordings).
But now I am downloading the RUU for the 2.24.401.8 OS and I will give it a try. And I will get back to you.
tnx

are u s-off? make sure ur using twrp 2.6.3.3 and not 2.6.3.4, also do a full wipe/factory reset before you try flashing the rom

xnknown said:
are u s-off? make sure ur using twrp 2.6.3.3 and not 2.6.3.4, also do a full wipe/factory reset before you try flashing the rom
Click to expand...
Click to collapse
Hi,
No, I am not S-OFF at the moment. ( I have attached a snippet of my status on the phone from the fastboot getvar all command on my first thread)
So currently I have no OS installed and I am not sure if there is any tool that can do S-OFF without installed OS. I tried rumrunner tool but it didnt help either ( I read that its the option to go for if one has hboot version 1.54, which I happen to have)
So the error messages I am getting are as follows.... ( this is in CWM recovery)
E: Can't open /cache/recovery/last_install
E: Can't open /cache/recovery/log
mount: mounting /dev/block/mmcblk0p36 on /cache failed: Invalid argument
W: failed to mount /dev/block/mmcblk0p36 /File exists)
W: Can't unlink /cache/recovery/command​
I appreciate your helps!

If you flash 2.6.3.4 TWRP recovery, and click install, is your SD card size 0?
sent from my mobile device

SaHiLzZ said:
If you flash 2.6.3.4 TWRP recovery, and click install, is your SD card size 0?
sent from my mobile device
Click to expand...
Click to collapse
TWRP 2.6.3.4 recovery is not working correct. It hangs saying "Entering Recovery...". It is something strange.

Fastboot erase cache in fastboot mode
Install the latest twrp by using the fastboot command.
Sideload through adb or store the ROM in your USB, mount USB drive using the usb-otg cable and then flash it from there.
Both methods should work
Sent from my One using XDA Premium HD app

EnIXmA said:
Fastboot erase cache in fastboot mode
Install the latest twrp by using the fastboot command.
Sideload through adb or store the ROM in your USB, mount USB drive using the usb-otg cable and then flash it from there.
Both methods should work
Sent from my One using XDA Premium HD app
Click to expand...
Click to collapse
I have tried Sideload having both latest recoveries of TWRP and CWM. Had problem to mount the cache partition (look earlier post). I will have to resort to the USB-OTG cable.
But I got myself in to a big and real problem now. I locked the oem from the fastboot command line thinking to run RUU.exe but it was a BAD BAD choice! Is there any hope for me now? Now my phone says
*****TAMPERED*****
*****RELOCKED*****
*****Security Warning*******
Oh boy! I am in real trouble. Please help!

SOLVED!
vvolverin said:
I have tried Sideload having both latest recoveries of TWRP and CWM. Had problem to mount the cache partition (look earlier post). I will have to resort to the USB-OTG cable.
But I got myself in to a big and real problem now. I locked the oem from the fastboot command line thinking to run RUU.exe but it was a BAD BAD choice! Is there any hope for me now? Now my phone says
*****TAMPERED*****
*****RELOCKED*****
*****Security Warning*******
Oh boy! I am in real trouble. Please help!
Click to expand...
Click to collapse
HI,
I finally managed to get the phone up and running. Thanks all for your prompt support.
So, what I did was, first I had to unlock using HTCdev unlock and then installed the latest TWRP recovery for the HTC One ( I think its 2.6.3.3 for HTC One and 2.6.3.4 might be for the HTC One X, because I couldn't manage to install it properly and I couldnt find the 2.6.3.4 version in a download list for the HTC One)....anyway after installing the custom recovery I tried installing stock ROM ( latest from Android Revolution HD --- One_4.19.401.8 OS version.
Oh I am so relieved...its been a good learning process anyway but not so nice if one has just one phone to play with. I probably have missed some important phone calls during the time my phone was down
Once again Thumbs up, Kudos for all those who answered to my desperate questions and Mike1986 for the nice work you are doing!

[Q] Stuck with a wiped internal memory

ok so I have been stock and unlocked and rooted with s-on. Decided today to flash my first Custom Rom. I have always been apprehensive
as my past devices have just seemed a lot easier to flash custom roms on and I was worried. I tried to flash Ordroid and the boot.img but was
stuck on the splash screen and just going to recovery constantly. I tried comand for wiping dalvik cache. It did nothing for me, don't know where I went wrong so far. Anyway I managed to wipe my internal storage when I was panicking. So now Im pretty much stuck in the same place I just cant flash anything because I have wiped off ordroid and my back up, or push anything to my phone. I was using a toolkit as well. Can anyone help me? Don't know why it would not boot in the first place I did a full wipe.
I know search blah blah blah but I dont want to make it any worse without some advice as to what I should be doing.
Any help appreciated thanks

-josh- said:
ok so I have been stock and unlocked and rooted with s-on. Decided today to flash my first Custom Rom. I have always been apprehensive
as my past devices have just seemed a lot easier to flash custom roms on and I was worried. I tried to flash Ordroid and the boot.img but was
stuck on the splash screen and just going to recovery constantly. I tried comand for wiping dalvik cache. It did nothing for me, don't know where I went wrong so far. Anyway I managed to wipe my internal storage when I was panicking. So now Im pretty much stuck in the same place I just cant flash anything because I have wiped off ordroid and my back up, or push anything to my phone. I was using a toolkit as well. Can anyone help me? Don't know why it would not boot in the first place I did a full wipe.
I know search blah blah blah but I dont want to make it any worse without some advice as to what I should be doing.
Any help appreciated thanks
Click to expand...
Click to collapse
Seem your using a very old guide .. we don't flash boot.img for over 8 months.
First update your recovery to TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Next go into TWRP /Advanced / sideload
now on the PC put your rom in the same location as adb and fastboot
open command window and type
adb sideload <name of rom>.zip
at the end of sideload the rom install will begin

clsA said:
Seem your using a very old guide .. we don't flash boot.img for over 8 months.
First update your recovery to TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Next go into TWRP /Advanced / sideload
now on the PC put your rom in the same location as adb and fastboot
open command window and type
adb sideload <name of rom>.zip
at the end of sideload the rom install will begin
Click to expand...
Click to collapse
Ok so I managed to sideload the ordroid i was previously trying to install but same problems so Im downloading a different rom now. Which I will have to sideload agian. Any idea where im going wrong? Im currently using TWRP 2.6.3.0 is that not ok, should I upgrade it?
When I sideload the rom will I not need to flash a boot.img? I thought that was needed seen as I am s-on
Thanks very much for your help

-josh- said:
Ok so I managed to sideload the ordroid i was previously trying to install but same problems so Im downloading a different rom now. Which I will have to sideload agian. Any idea where im going wrong? Im currently using TWRP 2.6.3.0 is that not ok, should I upgrade it?
When I sideload the rom will I not need to flash a boot.img? I thought that was needed seen as I am s-on
Thanks very much for your help
Click to expand...
Click to collapse
are you using a Sprint phone ?
if no update to TWRP 2.6.3.3

clsA said:
are you using a Sprint phone ?
if no update to TWRP 2.6.3.3
Click to expand...
Click to collapse
No international ill do that first then

-josh- said:
No international ill do that first then
Click to expand...
Click to collapse
no we stopped flashing boot.img last May
and you need the new recovery for all the kitkat roms

clsA said:
no we stopped flashing boot.img last May
and you need the new recovery for all the kitkat roms
Click to expand...
Click to collapse
Houston we have boot...
lol was scared there for a second it was just the recovery needed updating what a ****. Thanks very much
for your help greatly appreciated.

-josh- said:
Houston we have boot...
lol was scared there for a second it was just the recovery needed updating what a ****. Thanks very much
for your help greatly appreciated.
Click to expand...
Click to collapse
Glad to help :good::highfive:

System partition need to be mounted in TWRP to flash ROMs?

Hey guys. I've got TWRP 2.7.1.1 installed, but have been unable to flash 4.4.4 ROMs. They fail every time. Those who know my situation know my phone was recently soft bricked after I installed tdhite's TWRP 2.7.1.3 for Sprint HTC One m7. After restoring using RUU and reunlocking the bootloader and flashing SuperSU, I got everything working again and luckily had a backup of one of my favorite HTC One setups using the stock ROM only, along with Xposed framework.
Anyway:I was playing around in TWRP today and went to Mount and noticed that the system partition is not mounted. I'm thinking this may be why I am having trouble flashing ROMs. Should I just click on the system partition to mount it and then try to flash one of the custom AOSP ROMS?

MarkBell said:
Hey guys. I've got TWRP 2.7.1.1 installed, but have been unable to flash 4.4.4 ROMs. They fail every time. Those who know my situation know my phone was recently soft bricked after I installed tdhite's TWRP 2.7.1.3 for Sprint HTC One m7. After restoring using RUU and reunlocking the bootloader and flashing SuperSU, I got everything working again and luckily had a backup of one of my favorite HTC One setups using the stock ROM only, along with Xposed framework.
Anyway:I was playing around in TWRP today and went to Mount and noticed that the system partition is not mounted. I'm thinking this may be why I am having trouble flashing ROMs. Should I just click on the system partition to mount it and then try to flash one of the custom AOSP ROMS?
Click to expand...
Click to collapse
no, I don't be-leave it will do anything for you

clsA said:
no, I don't be-leave it will do anything for you
Click to expand...
Click to collapse
What about flashing an earlier version of TWRP and then flashing 2.7.1.1 again? I'm really wanting to try out the GPS fix recommended for the AOSP ROMs.

MarkBell said:
What about flashing an earlier version of TWRP and then flashing 2.7.1.1 again? I'm really wanting to try out the GPS fix recommended for the AOSP ROMs.
Click to expand...
Click to collapse
use that CWM recovery you have

clsA said:
use that CWM recovery you have
Click to expand...
Click to collapse
Still no dice using TWRP or CWM. I'm screwed. Can't flash ANYTHING at all through any version of TWRP or CWM.
Stuck on rooted stock with Xposed tweaks for now, I suppose.
Anyone think it's worth a try to sideload a rom?

MarkBell said:
Those who know my situation
Click to expand...
Click to collapse
Why do you expect us to be familiar with your situation?
MarkBell said:
Anyway:I was playing around in TWRP today and went to Mount and noticed that the system partition is not mounted. I'm thinking this may be why I am having trouble flashing ROMs. Should I just click on the system partition to mount it and then try to flash one of the custom AOSP ROMS?
Click to expand...
Click to collapse
most (probably all) installer scripts mount and unmount (possibly even format) the partitions it needs.
MarkBell said:
Hey guys. I've got TWRP 2.7.1.1 installed, but have been unable to flash 4.4.4 ROMs.
Click to expand...
Click to collapse
you need to start providing more details, a good starting point is usually:
1- a "fastboot getvar all" (excluding IMEI, MEID, S/N)
2- name and version of recovery you are using (yes, you did mention that, next time add it's the sprint variant as most of us are on m7_u/ul)
3- what you are trying flash (including link)
4- what error does the installer throw? "unable to flash" is very vague

nkk71 said:
Why do you expect us to be familiar with your situation?
most (probably all) installer scripts mount and unmount (possibly even format) the partitions it needs.
you need to start providing more details, a good starting point is usually:
1- a "fastboot getvar all" (excluding IMEI, MEID, S/N)
2- name and version of recovery you are using (yes, you did mention that, next time add it's the sprint variant as most of us are on m7_u/ul)
3- what you are trying flash (including link)
4- what error does the installer throw? "unable to flash" is very vague
Click to expand...
Click to collapse
It's ok ..I been helping him for a few days
he has a sprint phone and was softbricked from a bad recovery install. So he's kinda gun shy on flashing recovery's.
He wants to use an AOSP Rom that's kitkat 4.4.4 but all the normal versions of recovery have trouble flashing.

Cannot Mount Internal Storage

By mistake I did an Advanced Wipe of my HTC and wiped everything. Now to install a new ROM I need to put the ROM on the phone, and for that I tried mounting the data from TWRP 2.8 recovery but ADB showed no devices attached. I tried ADB sideload but the progress bar was stuck for about half an hour. I also tried flashing CWM recovery but couldn't mount from there too.
Can someone please help me mount the phone?
P.S. - I am using Ubuntu 14.04

rahulwadhwani said:
By mistake I did an Advanced Wipe of my HTC and wiped everything. Now to install a new ROM I need to put the ROM on the phone, and for that I tried mounting the data from TWRP 2.8 recovery but ADB showed no devices attached. I tried ADB sideload but the progress bar was stuck for about half an hour. I also tried flashing CWM recovery but couldn't mount from there too.
Can someone please help me mount the phone?
P.S. - I am using Ubuntu 14.04
Click to expand...
Click to collapse
have you tried an older version of TWRP? maybe it's a bug in 2.8.0.0
(i haven't tested it, so can't say for sure)

nkk71 said:
have you tried an older version of TWRP? maybe it's a bug in 2.8.0.0
(i haven't tested it, so can't say for sure)
Click to expand...
Click to collapse
I flashed CWM and it worked like a charm for me.
Maybe TWRP was buggy.
Edit : grammatical error

rahulwadhwani said:
I flashed CWM and it worked as a charm for me.
Maybe TWRP was buggy.
Click to expand...
Click to collapse
could be i haven't tried it (yet?), but I recommend you stick with
TWRP 2.6.3.3 (good for Sense based ROMs; CWM will most likely fail for 4.4+ ROMs due to missing SELinux support)
TWRP 2.7.1.1 (but this will erase the firmware version text from your "getvar all") but is needed for CM11 and possibly other ROMs that need a recovery with by-name support
TWRP 2.7.1.2+ (but be careful about possible factory reset this)
---------- Post added at 05:59 PM ---------- Previous post was at 05:19 PM ----------
rahulwadhwani said:
When I was trying to push the Rom to my phone, it was not happening with TWRP, that's why I switched to CWM and not it isn't booting up.
What do you suggest doing now?
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
first off stick with one thread, so let's stay here, let the other one die out
as i mentioned, you'll need to go with TWRP 2.6.3.3 or higher depending on the ROM
if you are going for ARHD 81.0, then use TWRP 2.6.3.3, it's working fine for me
also please check the faq sticky http://forum.xda-developers.com/showpost.php?p=53270352&postcount=21
let me know if you encounter other problems, by posting back here.

check the device manager. That was the problem in my case. The windows device manager did not recognize the driver. After updating this one it worked

leoncornelissen said:
check the device manager. That was the problem in my case. The windows device manager did not recognize the driver. After updating this one it worked
Click to expand...
Click to collapse
I am on Ubuntu 14.04 and not on Windows.

nkk71 said:
could be i haven't tried it (yet?), but I recommend you stick with
TWRP 2.6.3.3 (good for Sense based ROMs; CWM will most likely fail for 4.4+ ROMs due to missing SELinux support)
TWRP 2.7.1.1 (but this will erase the firmware version text from your "getvar all") but is needed for CM11 and possibly other ROMs that need a recovery with by-name support
TWRP 2.7.1.2+ (but be careful about possible factory reset this)
---------- Post added at 05:59 PM ---------- Previous post was at 05:19 PM ----------
first off stick with one thread, so let's stay here, let the other one die out
as i mentioned, you'll need to go with TWRP 2.6.3.3 or higher depending on the ROM
if you are going for ARHD 81.0, then use TWRP 2.6.3.3, it's working fine for me
also please check the faq sticky http://forum.xda-developers.com/showpost.php?p=53270352&postcount=21
let me know if you encounter other problems, by posting back here.
Click to expand...
Click to collapse
The problem now is that I am not able to mount the device. Adb says "Device not found" (tried all USB ports) and ADB Sideload also isn't working. It has been stuck with the progress bar for almost 10 minutes.
How should I transfer the ROM to the phone now?

rahulwadhwani said:
The problem now is that I am not able to mount the device. Adb says "Device not found" (tried all USB ports) and ADB Sideload also isn't working. It has been stuck with the progress bar for almost 10 minutes.
How should I transfer the ROM to the phone now?
Click to expand...
Click to collapse
which recovery are you using?

nkk71 said:
which recovery are you using?
Click to expand...
Click to collapse
TWRP 2.6.3.3

[SOLVED] [Q] HTC One only bootloader and recovery works

Last night tried installing SkyDragon v.9. It installed, the phone booted into rom and then started rebooting. Now i cant flash any rom because the phone reboots on the stage of wiping something. I installed newer twrp 2.8.0.2. Now i have these erros: unable to mount data and unable to mount internal storage. I'm S-ON unlocked. Tried ADB Sideload but it says device not found. Have no idea what to do. Saw somewhere that you can relock, unlock and install RUU to unbrick, but im not sure if i should do that. Help please.

OK. So... Try this:
From recovery go into Advanced Wipe, select all and wipe 2 or 3 times.
Reboot into bootloader.
In fastboot mode, make fastboot erase cache.
Then boot into recovery, and try ADB Sideload again or install rom via USB OTG (if you have)
If it also doesn't work try sth like this - it worked for me some time ago.
I saw that my PC recognizes my phone as normal storage when it's booted into TWRP and I don't need ADB Sideload. Try copy ROM like this and install.
If it won't work, you'll have to install RUU

Bruce666 said:
OK. So... Try this:
From recovery go into Advanced Wipe, select all and wipe 2 or 3 times.
Reboot into bootloader.
In fastboot mode, make fastboot erase cache.
Then boot into recovery, and try ADB Sideload again or install rom via USB OTG (if you have)
If it also doesn't work try sth like this - it worked for me some time ago.
I saw that my PC recognizes my phone as normal storage when it's booted into TWRP and I don't need ADB Sideload. Try copy ROM like this and install.
If it won't work, you'll have to install RUU
Click to expand...
Click to collapse
It didn't work Which RUU should i choose? M7-UL, hboot-1.55.0000, radio-4a.21.3263.04. I live in russia so i suppose i need one with "europe" in it's name? And how should i re-lock? Just by using fastboot command?

Give me CID ill try to find ruu 4u

Bruce666 said:
Give me CID ill try to find ruu 4u
Click to expand...
Click to collapse
HTC_A07

http://www.htc1guru.com/2014/03/android-ruu-europe/

Bruce666 said:
http://www.htc1guru.com/2014/03/android-ruu-europe/
Click to expand...
Click to collapse
Thank you very much! Really hope this works.

It must work. If you need help writr here

[email protected] said:
Last night tried installing SkyDragon v.9. It installed, the phone booted into rom and then started rebooting. Now i cant flash any rom because the phone reboots on the stage of wiping something. I installed newer twrp 2.8.0.2. Now i have these erros: unable to mount data and unable to mount internal storage. I'm S-ON unlocked. Tried ADB Sideload but it says device not found. Have no idea what to do. Saw somewhere that you can relock, unlock and install RUU to unbrick, but im not sure if i should do that. Help please.
Click to expand...
Click to collapse
If it reboots immediately when you try to wipe or flash something (i.e instant black screen then reboot)
You can probably fix it with e2fsck.
Boot to recovery select Mount then unmount all partitions return to twrp home screen and connect usb and check adb is working with
Code:
adb devices
You should get an output of your serial no.
Then do this
Code:
adb shell
e2fsck -fvy /dev/block/mmcblk0p35
e2fsck -fvy /dev/block/mmcblk0p36
e2fsck -fvy /dev/block/mmcblk0p37
exit
Now try to flash the Rom again
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

After i installed twrp 2.8.0.2 i can wipe. Well, sometimes it does wipe but sometimes it just writes error: unable to mount data and unable to mount internal storage. When i try flashing rom, for example viperone 7.0.1, it writes "set_perm some changes failed" right at the 0%. I tried installing cyanogenmod 11s and it installed without errors. But when i boot into rom, it says something like "the process android ui crashed".

[email protected] said:
After i installed twrp 2.8.0.2 i can wipe. Well, sometimes it does wipe but sometimes it just writes error: unable to mount data and unable to mount internal storage. When i try flashing rom, for example viperone 7.0.1, it writes "set_perm some changes failed" right at the 0%. I tried installing cyanogenmod 11s and it installed without errors. But when i boot into rom, it says something like "the process android ui crashed".
Click to expand...
Click to collapse
check the Frequently Asked Question sticky page 3
Point D, relates to unable to mount
Point C, relates to permission errors for certain ROMs, 2.6.3.3 should work or 2.8.0.1;
2.8.0.2 is known to have problems with certain ROMs

nkk71 said:
check the Frequently Asked Question sticky page 3
Point D, relates to unable to mount
Point C, relates to permission errors for certain ROMs, 2.6.3.3 should work or 2.8.0.1;
2.8.0.2 is known to have problems with certain ROMs
Click to expand...
Click to collapse
Dude, you are a wizard! Installed 2.6.3.3 and flashed viper without any problems. Yay it's working :laugh: . Couldn't think that recovery can cause these errors. I've been using 2.7.1.1 for quite a long time so i thought it'll work like it always did, but it just kept rebooting on wiping stage. So now it's working prefectly fine :good: Spent 5 hours today looking for sloutions and i have no idea how i missed your post on the faq thread. Thank you very much for your help! And thanks to everyone who responded!

[email protected] said:
Dude, you are a wizard! Installed 2.6.3.3 and flashed viper without any problems. Yay it's working :laugh: . Couldn't think that recovery can cause these errors. I've been using 2.7.1.1 for quite a long time so i thought it'll work like it always did, but it just kept rebooting on wiping stage. So now it's working prefectly fine :good: Spent 5 hours today looking for sloutions and i have no idea how i missed your post on the faq thread. Thank you very much for your help! And thanks to everyone who responded!
Click to expand...
Click to collapse
no problem,
2.6.3.3 is best for most ROMs, unless they require a recovery with "by-name" support (such as CM11), then you need 2.7.0.8 or higher
i've also successfully flashed using 2.8.0.1, but .2 seems to have issues again.
and if all is good now, can you also edit main thread title to include [SOLVED], thanks
edit the first post -> at the bottom of the edit window, click Go Advanced, and then you can edit main title