Database Develop

Htc ONE Brick need help please

Fastboot works perfectly. Adb says no devices found. I have no OS no recovery files no nothing on my phone. Well just clockwork is there but no use when adb doest work.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.61.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA364W916762
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4112mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Help me please

Adv should work via recovery. Have you tried twrp?
Sent from my GT-N7105 using Tapatalk

install the latest drivers just to make sure from here
get the latest CWM Touch Recovery from here and flash it using fastboot method: flash recovery recoveryfilename.img
or you can get TWRP Recovery from here
then go into recovery and then try adb

kamilmirza said:
install the latest drivers just to make sure from here
get the latest CWM Touch Recovery from here and flash it using fastboot method: flash recovery recoveryfilename.img
or you can get TWRP Recovery from here
then go into recovery and then try adb
Click to expand...
Click to collapse
+1
ADB only works in recovery and in android

Just got newest TWRP now the problem is sideload doesnt work in advanced menu. But I managed to push rom, and here comes another problem error could not flash rom.zip in install menu of twrp. (
Also it says internal memory 0mb
Help please

Try twrp. 2.6.3.0

SaHiLzZ said:
Try twrp. 2.6.3.0
Click to expand...
Click to collapse
Now trying to push rom.zip on TWRP 2.6.3.0 . (Sideload still fails)

After pushing rom.zip TWRP 2.6.3.0
Pushed rom.zip to /sdcard/
TWRP Install menu select rom.img
ERROR: unable to mount '/data'
E: unable to mount internal storage
Any ideas what to do now? im stuck

mrfilia said:
Pushed rom.zip to /sdcard/
TWRP Install menu select rom.img
ERROR: unable to mount '/data'
E: unable to mount internal storage
Any ideas what to do now? im stuck
Click to expand...
Click to collapse
sounds like your trying to flash a RUU.zip from recovery .. it won't work
Instructions for Flashing RUU Zip Files:
Download the RUU.zip file and place in your ADB/fastboot folder. I would recommend renaming the zip file to something simple like ruu.zip.
Boot your phone into the bootloader by holding the power and vol up/down buttons at the same time until you see the bootloader screen or if you have your phone booted you can use the ADB command:
adb reboot-bootloader
Now use these fastboot commands:
fastboot oem rebootRUU
Should see the Silver HTC logo. Now issue this command to flash your phone using the ruu.zip file:
fastboot flash zip ruu.zip
Now the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. You have to issue the exact command again:
fastboot flash zip ruu.zip
The green status bar usually does not reach the 100% mark. When the output in the command window is complete, you can reboot:
fastboot reboot
**Notes about the RUU.zip method. You still need to have the proper CID for the RUU. You can run the RUU.zip with super CID, but you will have to lock your bootloader first. If you are running the RUU.zip as base to downgrade all your firmware because you are going to then going to restore a stock Nandroid so the RUU might not be made for your MID, so you may need to edit the android-info.txt inside the ruu.zip to include your MID or CID.
Click to expand...
Click to collapse
where is this rom.img you got from ?

clsA said:
sounds like your trying to flash a RUU.zip from recovery .. it won't work
where is this rom.img you got from ?
Click to expand...
Click to collapse
I got this rom from revolution hd. The rom used to be before brick

mrfilia said:
Pushed rom.zip to /sdcard/
TWRP Install menu select rom.img
ERROR: unable to mount '/data'
E: unable to mount internal storage
Any ideas what to do now? im stuck
Click to expand...
Click to collapse
again let's check:
boot to custom recovery (CWM or TWRP), then
adb devices
-> check adb shows your device
then open a shell, and check /data partition; post back with result (copy/paste command prompt, no screenshots please):
adb shell
e2fsck -n -v -f /dev/block/mmcblk0p37

Rom help please
Maybe I'm using bad rom.
Can someone help me please to get right rom for my htc one? Because I think I'm using wrong ones.

mrfilia said:
Maybe I'm using bad rom.
Can someone help me please to get right rom for my htc one? Because I think I'm using wrong ones.
Click to expand...
Click to collapse
have u checked the partition?

nkk71 said:
again let's check:
boot to custom recovery (CWM or TWRP), then
adb devices
-> check adb shows your device
then open a shell, and check /data partition; post back with result (copy/paste command prompt, no screenshots please):
adb shell
e2fsck -n -v -f /dev/block/mmcblk0p37
Click to expand...
Click to collapse
Went in to recovery twrp-2.6.3.3-m7
\platform-tools>adb devices
List of devices attached
FA364W916762 recovery
\platform-tools>adb shell
~ # ←[6n
~ # ←[6n /dev/block/mmcblk0p37
/dev/block/mmcblk0p37
/sbin/sh: /dev/block/mmcblk0p37: Permission denied
Well this is like all I can show

If you want to flash a 4.4 kit kat Rom then use 2.6.3.3 twrp. Otherwise use 2.6.3.0
Sent from my HTC One using Tapatalk

Ivanovic said:
If you want to flash a 4.4 kit kat Rom then use 2.6.3.3 twrp. Otherwise use 2.6.3.0
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Yep but the problem is sideload doesnt work. And adb push rom.zip doesn't work as well. The rom as if gets there but cannot flash it,error coms up trying install rom.zip /sdcard/, also it says internal storage 0mb

The command is adb push rom.zip /0/data/media
That's the way to send a zip file to the root of the internal storage. Is this what you 're doing?
Sent from my HTC One using Tapatalk

Ivanovic said:
The command is adb push rom.zip /0/data/media
That's the way to send a zip file to the root of the internal storage. Is this what you 're doing?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
\platform-tools>adb push tiktak.zip /data/media/0/
1788 KB/s (476958424 bytes in 260.406s)
now went to install in twrp and run data/media/tiktak.zip
updating partition details
error flashing zip /data/media/0/tiktak.zip
updating partition details
=( tiktak4.4 doesn't work

mrfilia said:
\platform-tools>adb push tiktak.zip /data/media/0/
1788 KB/s (476958424 bytes in 260.406s)
now went to install in twrp and run data/media/tiktak.zip
updating partition details
error flashing zip /data/media/0/tiktak.zip
updating partition details
=( tiktak4.4 doesn't work
Click to expand...
Click to collapse
from the size of the ROM, it looks like a GPE rom, you need S-Off for 4.4 GPE
why not just try an older 4.3 ROM and make sure your phone at least works.

nkk71 said:
from the size of the ROM, it looks like a GPE rom, you need S-Off for 4.4 GPE
why not just try an older 4.3 ROM and make sure your phone at least works.
Click to expand...
Click to collapse
So id better use 2.3RomRUU with S-ON, relocked, by entering fastboot oem recoveryRUU?
Gonna try it, and give response to this operation. By the way is it possible I couldn't use RUU earlier just because I was using incorrect CID romRUU?

[Q] HTC ONE Bricked S off

ok I am new here and I have messed up my phone. I can get to bootloader but i'm lost after that. the PC doesn't see the SD card the phone has TWRP but there isn't anything in it to recover to
what should I do. I see a lot about cmd prompt but I know nothing about getting to the phone that way.

Jamesdbritt said:
ok I am new here and I have messed up my phone. I can get to bootloader but i'm lost after that. the PC doesn't see the SD card the phone has TWRP but there isn't anything in it to recover to
what should I do. I see a lot about cmd prompt but I know nothing about getting to the phone that way.
Click to expand...
Click to collapse
if you can get to bootloader you're not bricked.
don't fiddle with your phone - just leave it like it is.
someone here who knows way more about this stuff than I do will be able to tell you what you need to do.

Jamesdbritt said:
ok I am new here and I have messed up my phone. I can get to bootloader but i'm lost after that. the PC doesn't see the SD card the phone has TWRP but there isn't anything in it to recover to
what should I do. I see a lot about cmd prompt but I know nothing about getting to the phone that way.
Click to expand...
Click to collapse
get into fastboot mode and type "fastboot getvar all" in Command Prompt without the inverted commas. Post the output AND REMOVE IMEI AND SERIAL NO.
This is necessary to obtain a little more info abt the phone's current condition

raghav kapur said:
get into fastboot mode and type "fastboot getvar all" in Command Prompt without the inverted commas. Post the output AND REMOVE IMEI AND SERIAL NO.
This is necessary to obtain a little more info abt the phone's current condition
Click to expand...
Click to collapse
How do I get into Carrboro from command?
Go step by step like talking to a four year old..Lol I'm 28

Jamesdbritt said:
How do I get into Carrboro from command?
Go step by step like talking to a four year old..Lol I'm 28
Click to expand...
Click to collapse
Download and install latest android sdk http://developer.android.com/sdk/index.html
download in install latest htc sync (for drivers installation) then uninstall it, the drivers still be installed. http://www.htc.com/www/software/htc-sync-manager/
go to the folder you installed the android sdk then ---> sdk/platform-tools. Adb.exe and fastboot.exe should be in this folder. Always work in this folder (where adb and fastboot.exe are).
boot your phone in bootloader mode, select fastboot and connect usb cable to computer
Right click on a blank space in the folder where fastboot/adb are then select ''open a cmd prompt here''
in the command prompt type
Code:
fastboot getvar all
and copy paste output here MINUS IMEI AND SN
and please tell us what operating system are you using on your ocmputer? windows 7, 8.0 or 8.1?

How do I get into fastboot mode?

Jamesdbritt said:
How do I get into Carrboro from command?
Go step by step like talking to a four year old..Lol I'm 28
Click to expand...
Click to collapse
and how did you messed your phone?
---------- Post added at 03:26 PM ---------- Previous post was at 03:25 PM ----------
Jamesdbritt said:
How do I get into fastboot mode?
Click to expand...
Click to collapse
when you are in bootloarder mode, select ''fastboot''. use vol up and down to navigate then power button to select.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When in fastboot mode you'll have a screen similar to this with fastboot highlighted in red:

When I right click there is no cmd option

Jamesdbritt said:
When I right click there is no cmd option
Click to expand...
Click to collapse
sry my bad
hold left SHIFT + right click

Ok found cmd typed above and it came with a list of commands
Update
Flashall
Etc..

Jamesdbritt said:
Ok found cmd typed above and it came with a list of commands
Update
Flashall
Etc..
Click to expand...
Click to collapse
please can you make a screenshot of your cmd prompt and post it here? I want to see the command you typed and the ouput

commands:
update <filename> reflash device from
flashall flash boot + recove
flash <partition> [ <filename> ] write a file to a f
erase <partition> erase a flash parti
format <partition> format a flash part
getvar <variable> display a bootloade
boot <kernel> [ <ramdisk> ] download and boot k
flash:raw boot <kernel> [ <ramdisk> ] create bootimage an
devices list all connected
continue continue with autob
reboot reboot device norma
reboot-bootloader reboot device into
help show this help mess
options:
-w erase userdata and
if supported by par
-u do not first erase
formatting
-s <specific device> specify device seri
or path to device p
-l with "devices", lis
-p <product> specify product nam
-c <cmdline> override kernel com
-i <vendor id> specify a custom US
-b <base_addr> specify a custom ke
default: 0x10000000
-n <page size> specify the nand pa
2048
-S <size>[K|M|G] automatically spars
an
size. 0 to disable

Jamesdbritt said:
commands:
update <filename> reflash device from
flashall flash boot + recove
flash <partition> [ <filename> ] write a file to a f
erase <partition> erase a flash parti
format <partition> format a flash part
getvar <variable> display a bootloade
boot <kernel> [ <ramdisk> ] download and boot k
flash:raw boot <kernel> [ <ramdisk> ] create bootimage an
devices list all connected
continue continue with autob
reboot reboot device norma
reboot-bootloader reboot device into
help show this help mess
options:
-w erase userdata and
if supported by par
-u do not first erase
formatting
-s <specific device> specify device seri
or path to device p
-l with "devices", lis
-p <product> specify product nam
-c <cmdline> override kernel com
-i <vendor id> specify a custom US
-b <base_addr> specify a custom ke
default: 0x10000000
-n <page size> specify the nand pa
2048
-S <size>[K|M|G] automatically spars
an
size. 0 to disable
Click to expand...
Click to collapse
type this command:
Code:
fastboot devices
what is the output?

C:\Users\James\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>FASTBO
T GETVAR ALL
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater t
an
size. 0 to disable
C:\Users\James\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>

Jamesdbritt said:
C:\Users\James\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>FASTBO
T GETVAR ALL -------> 1 ''o'' is missing from fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater t
an
size. 0 to disable
C:\Users\James\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
Click to expand...
Click to collapse
fastboot is case sensitive don't use capitals letter unless specified
type
''fastboot getvar all'' NOT ''FASTBOT GETVAR ALL''
and there is a letter missing at fastboot

C:\SDK\ADT\sdk\platform-tools>fastboot devices
FA39DS900733 fastboot
C:\SDK\ADT\sdk\platform-tools>

Jamesdbritt said:
C:\SDK\ADT\sdk\platform-tools>fastboot devices
FA39DS900733 fastboot
C:\SDK\ADT\sdk\platform-tools>
Click to expand...
Click to collapse
ok so now type ''fastboot getvar all'' DON'T USE CAPITALS!

C:\SDK\ADT\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.12.41.1112_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.605.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA39DS900733
(bootloader) imei: xxxxxx
(bootloader) meid: xxxxxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3769mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3c88cdd7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
C:\SDK\ADT\sdk\platform-tools>

Jamesdbritt said:
C:\SDK\ADT\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.12.41.1112_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.605.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei: xxxxxx
(bootloader) meid: xxxxxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3769mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3c88cdd7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
C:\SDK\ADT\sdk\platform-tools>
Click to expand...
Click to collapse
ok so you want to go back to stock rom or you want to install a custom rom?

alray said:
ok so you want to go back to stock rom or you want to install a custom rom?
Click to expand...
Click to collapse
stock right now I know SuperSU is not installed if that means anything
I was having data connection problems before all this started

[SOLVED]I wiped all my data and can't push the rom via adb

HTC M7
I got an error on the phone then I returned to stock rom(relocked)>unlocked the device again>install TWRP 2.6.3.3
but now the problem is I can't push the file via adb or sideload
when I command "adb devices" it said
List of devices attached
HT37xxxxxxxx recovery
or I go to advanced>ADB sideload and try to swipe to start sideload it failed
---------------------------------------------------
ADB Sideload complete (white font)
Failed(red font)
Updating partition details.
----------------------------------------------------
sorry I can't post the image cause a new user condition.
Any helps, thank you

Use USB otg cable & drive
Mount USB then install Rom
USB drive should be fat32 format
from HTC One

tomyo.lfc said:
HTC M7
I got an error on the phone then I returned to stock rom(relocked)>unlocked the device again>install TWRP 2.6.3.3
but now the problem is I can't push the file via adb or sideload
when I command "adb devices" it said
List of devices attached
HT37xxxxxxxx recovery
or I go to advanced>ADB sideload and try to swipe to start sideload it failed
---------------------------------------------------
ADB Sideload complete (white font)
Failed(red font)
Click to expand...
Click to collapse
Sounds like a bad download, have you checked MD5?
also, have you checked the FAQ sticky thread, if it hasn't been updated/moved the info would still be in the last post; and while you're there read the first post (again?) too
(please remember to never post questions in the sticky, if you have more questions post back here)

nkk71 said:
Sounds like a bad download, have you checked MD5?
also, have you checked the FAQ sticky thread, if it hasn't been updated/moved the info would still be in the last post; and while you're there read the first post (again?) too
(please remember to never post questions in the sticky, if you have more questions post back here)
Click to expand...
Click to collapse
I try to flash the MAXIMUS41 and REVOLUTION HD but the point of the problem in my opinion I can't access the sideload
when at the twrp2.6.3.3page i click advanced>ADB sideload>check the wipe Dalvik Cache and Wipe cache(check both) and at the bottom it say swipe to start the sideload then I swipe it happen the failed page immediately and it just stop don't doing anything I don't even choose the sideload rom to transfer

tomyo.lfc said:
I try to flash the MAXIMUS41 and REVOLUTION HD but the point of the problem in my opinion I can't access the sideload
when at the twrp2.6.3.3page i click advanced>ADB sideload>check the wipe Dalvik Cache and Wipe cache(check both) and at the bottom it say swipe to start the sideload then I swipe it happen the failed page immediately and it just stop don't doing anything I don't even choose the sideload rom to transfer
Click to expand...
Click to collapse
MD5 checksum is a way to check that what you downloaded is not corrupt, for example for Maximus and ARHD, you can see the correct MD5 before downloading:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
how do you check it, well you download the file, and use one of the following programs:
on Mac, Linux, and Android terminals it's already built in:
Mac: in terminal, just type md5 <name of file>
----> MD5 (<name of file>) = 12345678901234567890123456789012
Linux: in terminal, just type md5sum <name of file>
----> 12345678901234567890123456789012 <name of file>
Android: in "adb shell", just type md5sum <name of file>
----> 12345678901234567890123456789012 <name of file>
Windows (seems not built-in!?!?): you can use programs such as http://winmd5.com/ , http://implbits.com/hashtab.aspx , http://www.pc-tools.net/win32/md5sums/ or any other one of your choosing.
if the number that you get on your downloaded file, is not exactly the same as the one mentioned in the place where you downloaded, then it is a bad download, and you have to download again.

tomyo.lfc said:
HTC M7
I got an error on the phone then I returned to stock rom(relocked)>unlocked the device again>install TWRP 2.6.3.3
but now the problem is I can't push the file via adb or sideload
when I command "adb devices" it said
List of devices attached
HT37xxxxxxxx recovery
or I go to advanced>ADB sideload and try to swipe to start sideload it failed
---------------------------------------------------
ADB Sideload complete (white font)
Failed(red font)
Updating partition details.
----------------------------------------------------
sorry I can't post the image cause a new user condition.
Any helps, thank you
Click to expand...
Click to collapse
Install stock recovery via fastboot, then go into bootloader and do factory reset. After that install custom recovery and you're good to go

*can't quote your message cause a new user
I think the point is not about the file is broken or not. I just can't use the sideload by twrp 2.6.3.3 and I don't know why.

donkeykong1 said:
Install stock recovery via fastboot, then go into bootloader and do factory reset. After that install custom recovery and you're good to go
Click to expand...
Click to collapse
doesn't work still stuck in the same problem.

tomyo.lfc said:
doesn't work still stuck in the same problem.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2318497
Did you try this?
Can't think of a good sig

donkeykong1 said:
http://forum.xda-developers.com/showthread.php?t=2318497
Did you try this?
Can't think of a good sig
Click to expand...
Click to collapse
this still need sidework to work but I can't use the sidework via my device. It appear the red font failed like I said.

tomyo.lfc said:
this still need sidework to work but I can't use the sidework via my device. It appear the red font failed like I said.
Click to expand...
Click to collapse
can you try adb push as shown below, and copy/paste your command prompt output here:
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_71.1.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [B][I]<- yes, it took over 5 mins,
without showing any progress[/I][/B]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_71.1.zip[/COLOR][/B]
ccc848cbf2b74c5fa33fd7e2269b0499 /sdcard/Android_Revolution_HD-One_71.1.zip
[INDENT]from the OP:
Android Revolution HD 71.1 -- MD5 sum: CCC848CBF2B74C5FA33FD7E2269B0499 --
==> so all is good :)[/INDENT]
C:\ADB3>

nkk71 said:
can you try adb push as shown below, and copy/paste your command prompt output here:
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_71.1.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [B][I]<- yes, it took over 5 mins,
without showing any progress[/I][/B]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_71.1.zip[/COLOR][/B]
ccc848cbf2b74c5fa33fd7e2269b0499 /sdcard/Android_Revolution_HD-One_71.1.zip
[INDENT]from the OP:
Android Revolution HD 71.1 -- MD5 sum: CCC848CBF2B74C5FA33FD7E2269B0499 --
==> so all is good :)[/INDENT]
C:\ADB3>
Click to expand...
Click to collapse
I just use your method and it work I think I can transfer file to my device but when I'm click install>rom file>swipe to flash. It failed again
it said
E:Unable to mount '/data'
Error flashing zip '/sdcard/rom.zip
Updating partition details...
E:Unable to mount '/data'
E:Unable to mount internal storage.
-----------------------------------------------------------------------------------------------
here is command
C:\Users\_\Desktop\ADB Drivers_Updated>adb devices
List of devices attached
HT37XW904211 recovery
C:\Users\_\Desktop\ADB Drivers_Updated>adb push rom.zip /sdcard/
2899 KB/s (1172621282 bytes in 394.971s)
C:\Users\_\Desktop\ADB Drivers_Updated>adbversion
'adbversion' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\_\Desktop\ADB Drivers_Updated>adb version
Android Debug Bridge version 1.0.31
C:\Users\_\Desktop\ADB Drivers_Updated>adb shell md5sum /sdcard/rom.zip
ccc848cbf2b74c5fa33fd7e2269b0499 /sdcard/rom.zip
C:\Users\_\Desktop\ADB Drivers_Updated>

YOu haven't posted a fastboot getvar all output, for all we know you have a Samsung Galaxy tab...
Please post that output.

SaHiLzZ said:
YOu haven't posted a fastboot getvar all output, for all we know you have a Samsung Galaxy tab...
Please post that output.
Click to expand...
Click to collapse
I already said HTC ONE M7
here is getvar all
C:\Users\_\Desktop\ADB Drivers_Updated>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37XW904211
(bootloader) imei: 354435058086489
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4320mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.054s

tomyo.lfc said:
I just use your method and it work I think I can transfer file to my device but when I'm click install>rom file>swipe to flash. It failed again
it said
E:Unable to mount '/data'
Error flashing zip '/sdcard/rom.zip
Updating partition details...
E:Unable to mount '/data'
E:Unable to mount internal storage.
-----------------------------------------------------------------------------------------------
here is command
C:\Users\_\Desktop\ADB Drivers_Updated>adb devices
List of devices attached
HT37XW904211 recovery
C:\Users\_\Desktop\ADB Drivers_Updated>adb push rom.zip /sdcard/
2899 KB/s (1172621282 bytes in 394.971s)
C:\Users\_\Desktop\ADB Drivers_Updated>adbversion
'adbversion' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\_\Desktop\ADB Drivers_Updated>adb version
Android Debug Bridge version 1.0.31
C:\Users\_\Desktop\ADB Drivers_Updated>adb shell md5sum /sdcard/rom.zip
ccc848cbf2b74c5fa33fd7e2269b0499 /sdcard/rom.zip
C:\Users\_\Desktop\ADB Drivers_Updated>
Click to expand...
Click to collapse
In TWRP go to the wipe menu, and select "Format Data". You'll have to confirm that by typing 'yes'.
After format is completed, reboot back to recovery, and do the adb push again
Sent from my HTC One using Tapatalk

nkk71 said:
In TWRP go to the wipe menu, and select "Format Data". You'll have to confirm that by typing 'yes'.
After format is completed, reboot back to recovery, and do the adb push again
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
ืI can flash the rom now. I want to thank you really, I love you thank you so much. :victory::victory:
love xda.

tomyo.lfc said:
ืI can flash the rom now. I want to thank you really, I love you thank you so much. :victory::victory:
love xda.
Click to expand...
Click to collapse
Welcome to xda :good::good:
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

nkk71 said:
Welcome to xda :good::good:
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
Click to expand...
Click to collapse
you're welcome, big thanks again brother.

[Q] Need to Restore to stock

If this is posted in the wrong place I apologize in advance :angel:
Scenario:
I currently own 2 HTC One M7's -One is my daily driver, which is running stock (Lollipop) which works fine with no errors. Never been rooted / anything done to it.
The second is a 'Spare' one which I purchased from a friend rather than having him recycle it for cheap, as there's no hardware fault, he just wanted an upgrade.
This 2nd device is currently rooted -Looks like with TWRP, running a HTC Dev version.
It does not show as "Tampered"
It does show as "Unlocked"
From the BIOS<? screen it is currently S-OFF
Phones original carrier is O2 UK
The only issue with this as far as I can see is that is fails to update, so its running Android 4.4.2 Sense version 5.5 - When installing any update from the 'software updates' area the phone crashes and resets/wipes itself.
What I'm Seeking:
Can anyone link me to a word by word / specific guide in restoring this to (Unlocked) factory stock? Or how to take an image of my first phone and duplicate it onto the second.
End result I would like the phone back to stock, UNLOCKED to accept any SIM so it can be updated and used like a 'normal' phone (To me normal means that nothing has been done to the phone at all relating to rooting -If that makes sense.) with the ability to update and do whatever my 1st phone can without error or major intervention :victory:
I've tried to find an online guide for the past week or 2, with the required software/file however everything I find is either out of date (So it's links no longer work) or expects me to already have all the tools and know how to use them (Which I don't, at all! :crying: )
Reason: I've never been a fan of rooted phones/doing anything I don't fully understand, and don't want the hassle of having to update it manually. That and I don't like old-android.
Love anyone who takes the time to assist me (No-Homo) :highfive:

mentize said:
If this is posted in the wrong place I apologize in advance :angel:
Scenario:
I currently own 2 HTC One M7's -One is my daily driver, which is running stock (Lollipop) which works fine with no errors. Never been rooted / anything done to it.
The second is a 'Spare' one which I purchased from a friend rather than having him recycle it for cheap, as there's no hardware fault, he just wanted an upgrade.
This 2nd device is currently rooted -Looks like with TWRP, running a HTC Dev version.
It does not show as "Tampered"
It does show as "Unlocked"
From the BIOS<? screen it is currently S-OFF
Phones original carrier is O2 UK
The only issue with this as far as I can see is that is fails to update, so its running Android 4.4.2 Sense version 5.5 - When installing any update from the 'software updates' area the phone crashes and resets/wipes itself.
What I'm Seeking:
Can anyone link me to a word by word / specific guide in restoring this to (Unlocked) factory stock? Or how to take an image of my first phone and duplicate it onto the second.
End result I would like the phone back to stock, UNLOCKED to accept any SIM so it can be updated and used like a 'normal' phone (To me normal means that nothing has been done to the phone at all relating to rooting -If that makes sense.) with the ability to update and do whatever my 1st phone can without error or major intervention :victory:
I've tried to find an online guide for the past week or 2, with the required software/file however everything I find is either out of date (So it's links no longer work) or expects me to already have all the tools and know how to use them (Which I don't, at all! :crying: )
Reason: I've never been a fan of rooted phones/doing anything I don't fully understand, and don't want the hassle of having to update it manually. That and I don't like old-android.
Love anyone who takes the time to assist me (No-Homo) :highfive:
Click to expand...
Click to collapse
can you post the output of "fastboot getvar all" from the phone you want to restore back to stock (don't post the imei# nor serialno#)? Is that phone already sim-unlocked? (btw ***unlocked*** in the bootloader doesn't mean sim-unlocked but bootloader unlocked). If yes, it will stay sim-unlocked forever if no you'll need to unlock it.
Wait for your "fastboot getvar all" then we can start reverting back to stock.

alray said:
can you post the output of "fastboot getvar all" from the phone you want to restore back to stock (don't post the imei# nor serialno#)? Is that phone already sim-unlocked? (btw ***unlocked*** in the bootloader doesn't mean sim-unlocked but bootloader unlocked). If yes, it will stay sim-unlocked forever if no you'll need to unlock it.
Wait for your "fastboot getvar all" then we can start reverting back to stock.
Click to expand...
Click to collapse
The phone is currently sim-unlocked, and I want it to stay that way.
@alray Requested Information:
C:\Users\XXXX>Fastboot getvar all
<bootloader> version: 0.5
<bootloader> version-bootloader: 1.56.0000
<bootloader> version-baseband: 4A.25.3263.21
<bootloader> version cpld: None
<bootloader> version-microp: None
<bootloader> version-main: 4.19.401.11
<bootloader> version-misc: PVT SHIP S-OFF
<bootloader> Serialno: XXXXXXXXXXXX
<bootloader> meid: XXXXXXXXXXXXXX
<bootloader> product: m7_u1
<bootloader> platform: HBOOT-8064
<bootloader> modelid: PN0710000
<bootloader> cidum: HTC__001
<bootloader> battery-status: good
<bootloader> battery-voltage: 4178mV
<bootloader> partition-layout: Generic
<bootloader> security: off
<bootloader> build-mode: SHIP
<bootloader> boot-mode: FASTBOOT
<bootloader> commitno-bootloader: dirty-4dab9d12
<bootloader> hbootpreupdate: 11
<bootloader> hencheckpt: 0
all: Done!
finished. total time: 0.087s

mentize said:
The phone is currently sim-unlocked, and I want it to stay that way.
@alray Requested Information:
C:\Users\XXXX>Fastboot getvar all
<bootloader> version: 0.5
<bootloader> version-bootloader: 1.56.0000
<bootloader> version-baseband: 4A.25.3263.21
<bootloader> version cpld: None
<bootloader> version-microp: None
<bootloader> version-main: 4.19.401.11
<bootloader> version-misc: PVT SHIP S-OFF
<bootloader> Serialno: XXXXXXXXXXXX
<bootloader> meid: XXXXXXXXXXXXXX
<bootloader> product: m7_u1
<bootloader> platform: HBOOT-8064
<bootloader> modelid: PN0710000
<bootloader> cidum: HTC__001
<bootloader> battery-status: good
<bootloader> battery-voltage: 4178mV
<bootloader> partition-layout: Generic
<bootloader> security: off
<bootloader> build-mode: SHIP
<bootloader> boot-mode: FASTBOOT
<bootloader> commitno-bootloader: dirty-4dab9d12
<bootloader> hbootpreupdate: 11
<bootloader> hencheckpt: 0
all: Done!
finished. total time: 0.087s
Click to expand...
Click to collapse
You could flash the stock 7.19.401.2 ruu. Instruction and files in this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
(make sure to use the 7.19.401.2 version not the 7.19.401.102 one)

alray said:
You could flash the stock 7.19.401.2 ruu. Instruction and files in this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
(make sure to use the 7.19.401.2 version not the 7.19.401.102 one)
Click to expand...
Click to collapse
@alray
I have downloaded both the RUU and Fastboot exe - the fastboot file was not called "HTC_Fastboot.exe" it was just called fastboot.exe, i assume this is correct?
5. Also use the htc_fastboot.exe not the normal fastboot.exe
get the htc_fastboot.exe here : https://www.androidfilehost.com/?fid=95916177934539737
Rename htc_fastboot to fastboot or if you don't rename the htc_fastboot.exe, then the command will be htc_fastboot flash zip RUU.zip
6. htc_fastboot oem rebootRUU -done
7.htc_fastboot flash zip RUU.zip -when doing this I am told "Cannot open file RUU.zip"
Ideas?

mentize said:
@alray
I have downloaded both the RUU and Fastboot exe - the fastboot file was not called "HTC_Fastboot.exe" it was just called fastboot.exe, i assume this is correct?
5. Also use the htc_fastboot.exe not the normal fastboot.exe
get the htc_fastboot.exe here : https://www.androidfilehost.com/?fid=95916177934539737
Rename htc_fastboot to fastboot or if you don't rename the htc_fastboot.exe, then the command will be htc_fastboot flash zip RUU.zip
6. htc_fastboot oem rebootRUU -done
7.htc_fastboot flash zip RUU.zip -when doing this I am told "Cannot open file RUU.zip"
Ideas?
Click to expand...
Click to collapse
can not open file error is caused by fastboot not finding the ruu. the ruu must be in the same folder as fastboot (htc's fastboot) and must be name "ruu" or "ruu.zip" if file extension are not hidden by default by windows.
And yes the file linked as htc_fastboot.exe is now named only fastboot.exe.Make sure to use this one.
Can you post a screenshot of your fastboot folder please?

alray said:
can not open file error is caused by fastboot not finding the ruu. the ruu must be in the same folder as fastboot (htc's fastboot) and must be name "ruu" or "ruu.zip" if file extension are not hidden by default by windows.
And yes the file linked as htc_fastboot.exe is now named only fastboot.exe.Make sure to use this one.
Can you post a screenshot of your fastboot folder please?
Click to expand...
Click to collapse
@alray - see attached screenshot

mentize said:
@alray - see attached screenshot
[edit] - nvm, rebooted phone, got past error that was originally put here - back to not seeing file
Click to expand...
Click to collapse
You have double file extension at your ruu file. See how the .exe extension of adb and fastboot are hidden? Its the same thing for the zip file. Zip file are considered "known file type" by windows so by default the extension (.zip) is hidden. By renaming the file "ruu.zip" you have double file extension (ruu.zip + the hidden .zip = ruu.zip.zip)
So delete the .zip from the file name and try the command again. Should work fine.
To avoid this kind of problem in the future, you can change windows settings to never hide files extension
http://windows.microsoft.com/en-us/...ions#show-hide-file-name-extensions=windows-7

alray said:
You have double file extension at your ruu file. See how the .exe extension of adb and fastboot are hidden? Its the same thing for the zip file. Zip file are considered "known file type" by windows so by default the extension (.zip) is hidden. By renaming the file "ruu.zip" you have double file extension (ruu.zip + the hidden .zip = ruu.zip.zip)
So delete the .zip from the file name and try the command again. Should work fine.
Click to expand...
Click to collapse
@alray
Done - same error.
Will re-start the whole process in-case it didn't detect the name change and update this post/reply accordingly
[EDIT] - restarted process (so let phone start up, re-booted into oem reboot. Same error

mentize said:
@alray
Done - same error.
Will re-start the whole process in-case it didn't detect the name change and update this post/reply accordingly
[EDIT] - restarted process (so let phone start up, re-booted into oem reboot. Same error
Click to expand...
Click to collapse
post a screenshot of your command prompt

alray said:
post a screenshot of your command prompt
Click to expand...
Click to collapse
@alray - see attachments. I've also posted the new folder.
I have tried leaving the .zip off the end of the command, same error.
-update, forgot attachments, will update in 4 minutes (forum spam filter)

mentize said:
@alray - see attachments. I've also posted the new folder.
I have tried leaving the .zip off the end of the command, same error.
-update, forgot attachments, will update in 4 minutes (forum spam filter)
Click to expand...
Click to collapse
Try to flash the firmware first then the ruu. You can download the firmware here: https://www.androidfilehost.com/?fid=95916177934534374
Code:
fastboot oem rebootRUU
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
fastboot reboot-bootloader
and then using htc's fastboot:
Code:
fastboot oem rebootRUU
fastboot flash zip RUU.zip
fastboot reboot
you could also check the md5 of the ruu and confirm its not corrupted/bad download.

alray said:
Try to flash the firmware first then the ruu. You can download the firmware here: https://www.androidfilehost.com/?fid=95916177934534374
Code:
fastboot oem rebootRUU
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
fastboot reboot-bootloader
and then using htc's fastboot:
Code:
fastboot oem rebootRUU
fastboot flash zip RUU.zip
fastboot reboot
you could also check the md5 of the ruu and confirm its not corrupted/bad download.
Click to expand...
Click to collapse
Downloaded the firmware from provided link - replaced the fastboot file with the original - copy / pasted the command given - Error "Cannot Load M7_UL_Firmware_7.19.401.2.zip"

mentize said:
Downloaded the firmware from provided link - replaced the fastboot file with the original - copy / pasted the command given - Error "Cannot Load M7_UL_Firmware_7.19.401.2.zip"
Click to expand...
Click to collapse
did you started your command prompt from the same folder where fastboot is? I see in your command prompt screenshot that you are working from the folder C:\User\Jason> when fastboot and other files are in C:\User\Jason\AppData\local\Android\android-sdk\platform-tools>
thats probably why fastboot is giving you the "can not load" error. Its not finding the file because you did not changed directory of your command prompt...

alray said:
did you started your command prompt from the same folder where fastboot is? I see in your command prompt screenshot that you are working from the folder C:\User\Jason> when fastboot and other files are in C:\User\Jason\AppData\local\Android\android-sdk\platform-tools>
thats probably why fastboot is giving you the "can not load" error. Its not finding the file because you did not changed directory of your command prompt...
Click to expand...
Click to collapse
@alray
-Moved CMD, now get the attached error

mentize said:
@alray
-Moved CMD, now get the attached error
Click to expand...
Click to collapse
you are doing:
Code:
fastboot reboot
fastboot flash zip ruu.zip
when you should do:
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
don't forget to use htc's version of fastboot. This fastboot version must be in the same folder.
---------- Post added at 07:40 PM ---------- Previous post was at 07:36 PM ----------
I have to go at work. Will try to answer you in my 1st break if it still not working otherwise i'll be back tomorrow to help you. Meanwhile there is many other ppl here that can help you.
good luck

alray said:
you are doing:
Code:
fastboot reboot
fastboot flash zip ruu.zip
when you should do:
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
don't forget to use htc's version of fastboot. This fastboot version must be in the same folder.
---------- Post added at 07:40 PM ---------- Previous post was at 07:36 PM ----------
I have to go at work. Will try to answer you in my 1st break if it still not working otherwise i'll be back tomorrow to help you. Meanwhile there is many other ppl here that can help you.
good luck
Click to expand...
Click to collapse
I'm aware of the commands being used - I am deliberately doing non-oem reboots whenever i 'restart' the cycle, to ensure nothing is stuck before trying again.
@alray - Appreciate all your help, I've restarted both the phone & computer and tried again - see attached screenshot of where we are up too.
Double checked the fastboot is the HTC one, and is in the correct folder, along with the RUU file.
(Ignore that it says 25s to execute the reboot, that's because i forgot to boot the phone into fastboot manually from power-up.
I'm off to sleep, wont be back on for another 9hours or so (yay days off work :victory: )

Come back to this today:
Completely re-installed the platform-tools folder
Re-downloaded both the RUU & HTC Fastboot from different mirrors
Confirmed ADB can see the device
Replaced original Fastboot with HTC Fastboot
Placed the RUU file in the same directory
Ran "Fastboot oem rebootruu"
--Phone rebooted into a black-screen with "HTC" in the centre
Ran "Fastboot flash zip ruu.zip"
---Fastboot.exe has stopped responding (CMD states too many threads same as in previous screenshots)

mentize said:
Come back to this today:
Completely re-installed the platform-tools folder
Re-downloaded both the RUU & HTC Fastboot from different mirrors
Confirmed ADB can see the device
Replaced original Fastboot with HTC Fastboot
Placed the RUU file in the same directory
Ran "Fastboot oem rebootruu"
--Phone rebooted into a black-screen with "HTC" in the centre
Ran "Fastboot flash zip ruu.zip"
---Fastboot.exe has stopped responding (CMD states too many threads same as in previous screenshots)
Click to expand...
Click to collapse
I think you should try using a windows 7 computer. Looks like windows 8 doesn't like htc's fastboot... This fastboot works fine on my computer and downloaded from the same link.

hey guys, i'm trying to the same thing,
did the flashboot oem rebootRUU, which was fine, then i got this:
C:\Users\hp\Desktop\Minimal ADB and Fastboot>fastboot flash zip RUU.zip
sending 'zip'... (43286 KB) OKAY
sending time = 3.114 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 10(s)
any ideas>?>?

Problem installing not incremental ROM

Well I have tried to install MIUI ROM 6.5.26 after not processing updates for months (since november).
So I downloaded latest ROM and put it to the top of the partitions and then I wiped everything and that's where i might have done a mistake: I wiped internal storage (inside TWRP 2.8.7 i found there http://forum.xda-developers.com/mi-...timizing-leo-miui-advanced-tweaks-to-t3286972) then I might have might done a second mistake: I have done the command fastboot 'flash boot boot.img' as I read on an old HTC forum.
Then I pushed the latest ROM to the phone (as it was not there after the wipes) and when I tried installing it, it gave E: unable to mount 'cache' .
Now it seems i cannot enter TWRP, only Fastboot or I am stuck with MI logo.
I just want to install latest ROM, as I have done Titanium Backup before all the mess.
I don't know where i should start.

I am on mac so cannot use Mi Flash

EMJI79 said:
Well I have tried to install MIUI ROM 6.5.26 after not processing updates for months (since november).
So I downloaded latest ROM and put it to the top of the partitions and then I wiped everything and that's where i might have done a mistake: I wiped internal storage (inside TWRP 2.8.7 i found there http://forum.xda-developers.com/mi-...timizing-leo-miui-advanced-tweaks-to-t3286972) then I might have might done a second mistake: I have done the command fastboot 'flash boot boot.img' as I read on an old HTC forum.
Then I pushed the latest ROM to the phone (as it was not there after the wipes) and when I tried installing it, it gave E: unable to mount 'cache' .
Now it seems i cannot enter TWRP, only Fastboot or I am stuck with MI logo.
I just want to install latest ROM, as I have done Titanium Backup before all the mess.
I don't know where i should start.
Click to expand...
Click to collapse
you wiped internal sd so you have nothing the only way to solve is
Download the fastboot ROM https://www.dropbox.com/s/dg198q49dctzfgr/leo_images_5.11.26_20151104.0000.4_5.1_cn.tar.gz?dl=0 (recomend this others from this year locked bootloader)
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
10. Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash tz tz.mbn
C:\Fastboot>fastboot flash dbi sdi.mbn
C:\Fastboot>fastboot flash sbl1 sbl1.mbn
C:\Fastboot>fastboot flash rpm rpm.mbn
C:\Fastboot>fastboot flash aboot emmc_appsboot.mbn
C:\Fastboot>fastboot erase boot
C:\Fastboot>fastboot flash misc misc.img
C:\Fastboot>fastboot flash modem NON-HLOS.bin
C:\Fastboot>fastboot flash system system.img
C:\Fastboot>fastboot flash cache cache.img
C:\Fastboot>fastboot flash userdata userdata.img
C:\Fastboot>fastboot flash recovery recovery.img
C:\Fastboot>fastboot flash boot boot.img
C:\Fastboot>fastboot reboot
Now you're all set and should be able to boot normally.
after you can install recovery
to install recoverytwrp https://www.dropbox.com/s/hkuwc6d881im2hy/TWRP_leo.zip?dl=0
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash recovery TWRP.img
C:\Fastboot>fastboot reboot
done now you can install latest rom from xiaomi.eu Does not locked bootloader

helderfp said:
you wiped internal sd so you have nothing the only way to solve is
Download the fastboot ROM https://www.dropbox.com/s/dg198q49dctzfgr/leo_images_5.11.26_20151104.0000.4_5.1_cn.tar.gz?dl=0 (recomend this others from this year locked bootloader)
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
10. Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash tz tz.mbn
C:\Fastboot>fastboot flash dbi sdi.mbn
C:\Fastboot>fastboot flash sbl1 sbl1.mbn
C:\Fastboot>fastboot flash rpm rpm.mbn
C:\Fastboot>fastboot flash aboot emmc_appsboot.mbn
C:\Fastboot>fastboot erase boot
C:\Fastboot>fastboot flash misc misc.img
C:\Fastboot>fastboot flash modem NON-HLOS.bin
C:\Fastboot>fastboot flash system system.img
C:\Fastboot>fastboot flash cache cache.img
C:\Fastboot>fastboot flash userdata userdata.img
C:\Fastboot>fastboot flash recovery recovery.img
C:\Fastboot>fastboot flash boot boot.img
C:\Fastboot>fastboot reboot
Now you're all set and should be able to boot normally.
after you can install recovery
to install recoverytwrp https://www.dropbox.com/s/hkuwc6d881im2hy/TWRP_leo.zip?dl=0
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash recovery TWRP.img
C:\Fastboot>fastboot reboot
done now you can install latest rom from xiaomi.eu Does not locked bootloader
Click to expand...
Click to collapse
OK thanks a lot. :good:
I will try that tonight or tomorrow (already downloading from your dropbox, thanks again).
I'll let you know.

Only i dont understand: (recomend this others from this year locked boot loader) ?

EMJI79 said:
Only i dont understand: (recomend this others from this year locked boot loader) ?
Click to expand...
Click to collapse
It broke halfway, so I am trying again. Thank you for your patience.

Well, I downloaded it entirely and tried "fastboot the tz", then I get -> "device is locked. Cannot flash images"...
So I guess I locked my bootloader already, somehow... :crying:

EMJI79 said:
Well, I downloaded it entirely and tried "fastboot the tz", then I get -> "device is locked. Cannot flash images"...
So I guess I locked my bootloader already, somehow... :crying:
Click to expand...
Click to collapse
ok
so you have to do this
Download Xiaomi MiFlash Tool and install it to your PC https://www.dropbox.com/s/1qntzckybxg3rr4/MiSetup3.2.1.3111_2717.zip?dl=0
Download Qualcomm Driver 32-bit https://www.dropbox.com/s/klnn6h9z7038u80/QDLoader HS-USB Driver_32bit_Setup.zip?dl=0 OR Qualcomm Driver 64-bit https://www.dropbox.com/s/gvizx1ja1vmihox/QDLoader HS-USB Driver_64bit_Setup.zip?dl=0 install it to your PC
Enter your phone in fastboot mode
in command promt wrtite:
cmd
cd C:\fastboot
fastboot devices
fastboot oem edl
After the last command Your Note pro detected as a new device
Launch MiFlash and flash Note pro not locked ROM if you get one error at the midle (not at the beginnig) of flashing dont worry, you have unlocked bootloader, and you can folow the previous steps you already tried
The latest roms from xiaomi (since January 2016) lockes bootloader that is why i recomend that on the link.

Thanks
But I am on Mac, no MiFlash, only ADB, fastboot...

EMJI79 said:
Thanks
But I am on Mac, no MiFlash, only ADB, fastboot...
Click to expand...
Click to collapse
to work on mac
Download the fastboot ROM for your Mi phone and place it on your desktop. Double-click on it and Archive Utility will extract the file on the desktop, so you'll get a folder,
now go to terminal an type
cd C:\fastboot
fastboot devices
fastboot oem edl
In order to use the fastboot scripts, you should go to the folder. For that purpose, execute the following command (the folder name may be different in your case, the example below is for cancro):
cd ~/Desktop/cancro_global_images_V7.0.5.0.KXDMICI_20151016.0000.3_4.4_global
Copy the Code
Quick tip: you don't need to write the whole folder name, just type cd ~/Desktop/cancro, then press the Tab key and Terminal will append the folder name automatically.
Once inside, you need to make the scripts (all the files with .sh extension) executable. Execute the following command:
chmod +x ./*.sh
Now, the scripts are ready to use. In order to start the process, issue one of the following commands:
./flash_all.sh
or
./flash_all_except_storage.sh
or
./flash_all_except_data_storage.sh
When you start any of the scripts, you'll see the fastboot messages, flowing through the Terminal window. Once the script has done its work, the phone will restart itself automatically.

When I change directory for the fastboot ROM directory, the fastboot screen on my phone disappears. I have done the steps after that but i see no message on the terminal or the phone screen. My phone screen is black.
Edit: In fact the fastboot screen on my phone disappears when I type fastboot oem edl in my terminal although i get the message OKAY in my terminal.

EMJI79 said:
When I change directory for the fastboot ROM directory, the fastboot screen on my phone disappears. I have done the steps after that but i see no message on the terminal or the phone screen. My phone screen is black.
Edit: In fact the fastboot screen on my phone disappears when I type fastboot oem edl in my terminal although i get the message OKAY in my terminal.
Click to expand...
Click to collapse
so don't change the directory put the rom in the fastboot folder and do the next step
if you are not able to flash in your mac try in another pc (windows)

Don't you think I just locked my bootloader and I need to do the apply stuff for getting my phone unlocked?

EMJI79 said:
Don't you think I just locked my bootloader and I need to do the apply stuff for getting my phone unlocked?
Click to expand...
Click to collapse
you dont need
just try
put rom in fastboot folder and
cd C:\fastboot
fastboot devices
fastboot oem edl
chmod +x ./*.sh
./flash_all.sh
to unlock bootloader the previous steps (not this) work fine on windows
http://en.miui.com/thread-237832-1-1.html
https://xiaomi.eu/community/threads/mi-note-pro-complete-beginners-guide.30817/

every time I type:
fastboot oem edl
the screen of the smartphone goes off

Maybe I will buy Windows to make it work in VM...
Only can you interpretate why fastboot oem edl makes the screen go off?

EMJI79 said:
Maybe I will buy Windows to make it work in VM...
Only can you interpretate why fastboot oem edl makes the screen go off?
Click to expand...
Click to collapse
do you have qualcom drivers instaled?

No
Will try tomorrow.
Thanks again.
The link to your dropbox for Qualcomm drivers is for Windows, i found that:https://developer.qualcomm.com/download/software
and Snapdragon SDK but I have to register.

Is Snapdragon SDK actually Qualcomm drivers?

helderfp said:
do you have qualcom drivers instaled?
Click to expand...
Click to collapse
Hello,
OK, no Qualcomm drivers for Mac it seems... I have searched thoroughly and haven't found. I have asked a en.miui dev and waiting for the response.. Don't have them?