The memory fills every 4 days in the other part and I have to reflash and install everything again.
I already installed probe ruu, change firmware and some other things but I still have the problem
Someone can help me?
Thank you so much
Htc One M7 Verizon
M7_WLV PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.44.0000
RADIO-1.13.41.0421
OpenDSP-v31.120.274.0617
eMMC-boot
Then it must be an app you have installed. Try to run your phone for a few days with only the very basic essentials installed.
RolloWolf said:
Then it must be an app you have installed. Try to run your phone for a few days with only the very basic essentials installed.
Click to expand...
Click to collapse
i try reflashing the ROM without installing applications but the problem continues, I'll try flashing the ruu.
the so is not included in the ruu?
because the version that I have does not have it
lxcas said:
i try reflashing the ROM without installing applications but the problem continues, I'll try flashing the ruu.
the so is not included in the ruu?
because the version that I have does not have it
Click to expand...
Click to collapse
so?
if you have s-off flash this please:
http://forum.xda-developers.com/showthread.php?t=2765784
you will not loose S-off but will loose root
once ruu is complete:
fastboot recovery of your choice.
flash rom of your choice.
run it for a bit and see if you get the memory problem. if you dont get it then restore apps.
synisterwolf said:
so?
if you have s-off flash this please:
http://forum.xda-developers.com/showthread.php?t=2765784
you will not loose S-off but will loose root
once ruu is complete:
fastboot recovery of your choice.
flash rom of your choice.
run it for a bit and see if you get the memory problem. if you dont get it then restore apps.
Click to expand...
Click to collapse
Perfect, this weekend try this ruu and tell them like it worked correctly
lxcas said:
Perfect, this weekend try this ruu and tell them like it worked correctly
Click to expand...
Click to collapse
also back up your internal storage and apps because the RUU will wipe /data partition completely.
synisterwolf said:
also back up your internal storage and apps because the RUU will wipe /data partition completely.
Click to expand...
Click to collapse
Hi, I had problems installing the ruu, I had to install another before and after install you sent me, but I had to downgrade and install the ruu recovery and also not install any OS so install a rom and still have my memory problem.
Any idea?
lxcas said:
Hi, I had problems installing the ruu, I had to install another before and after install you sent me, but I had to downgrade and install the ruu recovery and also not install any OS so install a rom and still have my memory problem.
Any idea?
Click to expand...
Click to collapse
Can you link which ruu you installed then? Dottdat's ruus always work for me. Have you tried checking system - storage to see what is taking up the space?
Sent from my One using XDA Free mobile app
Uzephi said:
Can you link which ruu you installed then? Dottdat's ruus always work for me. Have you tried checking system - storage to see what is taking up the space?
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
First I use another ruu because Dottdat's telling me that there is not enough space, and then to use the previous charge of Dottdat's.
how do I make Hecking system - storage?
In my phone says it's in the memory space "other"
Thank you
Uzephi said:
Can you link which ruu you installed then? Dottdat's ruus always work for me. Have you tried checking system - storage to see what is taking up the space?
Sent from my One using XDA Free mobile app[/QUOTE
this is what it says when I try to install the ruu of Dottdat's:
C:\htc>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.051s]
finished. total time: 0.053s
C:\htc>fastboot flash zip vzwruu.zip
sending 'zip' (1368008 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.009s
any ideas?
Click to expand...
Click to collapse
lxcas said:
Uzephi said:
Can you link which ruu you installed then? Dottdat's ruus always work for me. Have you tried checking system - storage to see what is taking up the space?
Sent from my One using XDA Free mobile app[/QUOTE
this is what it says when I try to install the ruu of Dottdat's:
C:\htc>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.051s]
finished. total time: 0.053s
C:\htc>fastboot flash zip vzwruu.zip
sending 'zip' (1368008 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.009s
any ideas?
Click to expand...
Click to collapse
You are on hboot 1.44? Flash the lasest firmware from santod's firmware thread (5.xx.xxx.x) then try the ruu again.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
lxcas said:
Uzephi said:
Can you link which ruu you installed then? Dottdat's ruus always work for me. Have you tried checking system - storage to see what is taking up the space?
Sent from my One using XDA Free mobile app[/QUOTE
this is what it says when I try to install the ruu of Dottdat's:
C:\htc>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.051s]
finished. total time: 0.053s
C:\htc>fastboot flash zip vzwruu.zip
sending 'zip' (1368008 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.009s
any ideas?
Click to expand...
Click to collapse
Do a fastboot erase cache
Then try to flash.
Also, make sure your pc has enough ram to send a 1.5gig file.
Lastly, unzip the below folder on your desktop. Copy the ruu into the new folder. Hold shift and right click inside the window and select open cmd prompt here. Run the ruu commands here now.
https://www.androidfilehost.com/?fid=23501681358559711
Click to expand...
Click to collapse
dottat said:
lxcas said:
Do a fastboot erase cache
Then try to flash.
Also, make sure your pc has enough ram to send a 1.5gig file.
Lastly, unzip the below folder on your desktop. Copy the ruu into the new folder. Hold shift and right click inside the window and select open cmd prompt here. Run the ruu commands here now.
https://www.androidfilehost.com/?fid=23501681358559711
Click to expand...
Click to collapse
I tried everything and still have the same problem.
{
"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"
}
[/url][/IMG]
Click to expand...
Click to collapse
lxcas said:
dottat said:
I tried everything and still have the same problem.
[/url][/IMG]
Click to expand...
Click to collapse
Your computer doesn't have enough RAM (random access memory) to load the file into temporary memory.
You'll need a pc with at least 2 GBs of free ram or so.
Click to expand...
Click to collapse
try with 8GB of RAM but I have the same problem.
Also probe to another computer
Any other ideas?
lxcas said:
try with 8GB of RAM but I have the same problem.
Also probe to another computer
Any other ideas?
Click to expand...
Click to collapse
TRy the EXE RUU I posted here...
http://forum.xda-developers.com/verizon-htc-one/help/exe-ruu-vzw-m7-4-4-3-s-users-t2919442
It uses ram much differently than regular fastboot.
Probe this ruu but with these results:
1. I had to update the firmware, after that it worked.
2. I had to downgrade to hboot 1.44 because it started the recovery
3. cell still is root and s-off
4. Try installing the rom zip file including but not succeed
5. Install the rom: [ROM] [4.4.3] NuSenseSIX | Sense 6.0 | 5.28.605.2 | v8.0 [14/11/09] but continues the problem of memory
hello, install the rom google play edition and the memory becomes full in the various sections and is the smlog it fills, any solution?
Hello friends, I still have this problem.
you have any idea which is the smlog?
any new ideas that you can recommend me?
I will upgrade to ★ ☆ [ROM] [5.0.2] NuSenSeveN | Sense 7.0 | v4.00 [15.06.05] ☆ but usually this does not solve the problem
thanks and regards
Related
Hey!
I have a HTC one X and right now it is in a fase between Paranoid android, and Android with HTC sense. the reason it is that way is becouse i miss somthing in the installation. so i tried to get i back to stock rom, but all of the ruu i found won`t work, i think i am running version 3.18.40. i can not reach the "recovery" meny. is there a newer ruu out there that i can use?
Are you sure it's the right RUU? Do fastboot getvar version-main to be sure.
Did you lock the bootloader before running it? fastboot oem lock
Also, did you run the exe as admin?
re:
TToivanen said:
Are you sure it's the right RUU? Do fastboot getvar version-main to be sure.
Did you lock the bootloader before running it? fastboot oem lock
Also, did you run the exe as admin?
Click to expand...
Click to collapse
When i am installing the ruu, it tells me that i`v got the wrong version. i cant`t connect with the phone trough CMD
i lock the bootloader with fastboot oem lock
an i did run it as admin.
fastboot getvar version-main
Sent from my IceCold One X using xda premium
not working
when i typing that, CMD i saying "waiting for device". and nothing more
Is the phone in fastboot mode? Correct driver?
Sent from my IceCold One X using xda premium
version
TToivanen said:
Is the phone in fastboot mode? Correct driver?
Sent from my IceCold One X using xda premium
Click to expand...
Click to collapse
C:\fastboot>fastboot getvar version-main
version-main: 3.18.401.1
finished. total time: 0.015s
C:\fastboot>
I used this version RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.
Does it matter where the RUU is build for? i used Europa version before, but could not find the right one now. so i used the US one. is that the problem?
Lol that is not even for the one x. It's for one xl.
Go to ruu.androidfiles.org and select endeavor. (You have endeavor right?)
Then ctrl+f 3.18.401 and youll find the right one.
Sent from my IceCold One X using xda premium
Ohh
TToivanen said:
Lol that is not even for the one x. It's for one xl.
Go to ruu.androidfiles.org and select endeavor. (You have endeavor right?)
Then ctrl+f 3.18.401 and youll find the right one.
Sent from my IceCold One X using xda premium
Click to expand...
Click to collapse
Ohh....
There is no "exe" file on that side with endeavor and 3.18.4. only zip
tb47 said:
Ohh....
There is no "exe" file on that side with endeavor and 3.18.4. only zip
Click to expand...
Click to collapse
Here - RUU 3.14.401
Then - OTA to 3.18.401
He can't run a 3.14 ruu if he is already on the 3.18 !
not working
athulele said:
Here - RUU 3.14.401
Then - OTA to 3.18.401
Click to expand...
Click to collapse
{
"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"
}
this is what comes up when i try the one you linked
DL this: http://d-h.st/hFn
Extract and put it onto your sdcard to folder clockworkmod/backups
Take the boot.img and flash it, then restore the backup in recovery.
You will boot to stock 3.18.
Mr Hofs said:
He can't run a 3.14 ruu if he is already on the 3.18 !
Click to expand...
Click to collapse
Says it all .... TT will sort this out
TToivanen said:
DL this: http://d-h.st/hFn
Extract and put it onto your sdcard to folder clockworkmod/backups
Take the boot.img and flash it, then restore the backup in recovery.
You will boot to stock 3.18.
Click to expand...
Click to collapse
How can i put it on the sd card?
Can you go to recovery? Do fastboot erase cache if you can't
Go to mounts and storage and select mount usb storage.
TToivanen said:
Can you go to recovery? Do fastboot erase cache if you can't
Go to mounts and storage and select mount usb storage.
Click to expand...
Click to collapse
That is the big problem, every time i go to "recovery", it tries to update the phone or somthing. so i can`t acsess the recovery
Try the factory reset option in bootloader, also do fastboot erase cache and reflash recovery.
TToivanen said:
Try the factory reset option in bootloader, also do fastboot erase cache and reflash recovery.
Click to expand...
Click to collapse
C:\fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.087s]
finished. total time: 0.087s
C:\fastboot>fastboot flash recovery recovery.img
sending 'recovery' (5790 KB)...
OKAY [ 0.739s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.950s
C:\fastboot>
is this right?
You have a relocked bootloader ! Unlock it and continue
Please help me.. I just unlocked and installed a custom rom on my phone but after the installation the screen has been unresposive..
I tried to reinstall the rom since i forgot to flash the boot image on the first try but still the can't use the screen..
A little more info would be helpful... Which rom? which kernel? What is your hboot?
also post the result of fastboot getvar version-main
vin4yak said:
A little more info would be helpful... Which rom? which kernel? What is your hboot?
also post the result of fastboot getvar version-main
Click to expand...
Click to collapse
I first installed the nocturnal xi40 rom but forgot to flash the boot image and kernel.. awhile ago i tried to install the bindroid xtc rom + kernel but still nothing changed. My phone just boots up to home screen which is still unresposive and at times my music player automatically plays. :crying:
mikenirochiell said:
I first installed the nocturnal xi40 rom but forgot to flash the boot image and kernel.. awhile ago i tried to install the bindroid xtc rom + kernel but still nothing changed. My phone just boots up to home screen which is still unresposive and at times my music player automatically plays. :crying:
Click to expand...
Click to collapse
Don't get tense, this can be sorted out easily m8 if there's not hardware issue here...
Post the result of the following:
Code:
fastboot getvar version-main
fastboot oem readcid
vin4yak said:
Don't get tense, this can be sorted out easily m8 if there's not hardware issue here...
Post the result of the following:
Code:
fastboot getvar version-main
fastboot oem readcid
Click to expand...
Click to collapse
How can I do this?
mikenirochiell said:
How can I do this?
Click to expand...
Click to collapse
Can you pls guide me to this? I dont know how to use the code.
mikenirochiell said:
Can you pls guide me to this? I dont know how to use the code.
Click to expand...
Click to collapse
Use Fastboot.
Link:
http://www.mediafire.com/download/q2540u4g3v6qqd7/Fastboot.zip
Instructions:
1. Put the phone in bootloader (turn your phone off, and hold power + vol. down) then enter fastboot, and make sure it shows:" FASTBOOT USB "
2. Open a terminal windows, change the current location to the fastboot files, for an example: C:/Fastboot. So you need to type cd C:/fastboot (see image below)
3. Run the fastboot commands :good:
{
"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"
}
I did the codes followed the image you posted.. What's next?
wich recovery are you useing,,,also wich radio are you on
mikenirochiell said:
I did the codes followed the image you posted.. What's next?
Click to expand...
Click to collapse
I rebooted my phone but still no changes..still unresposive screen..
after you unlocked your bootloader wich recovery did you flash
hellothere74 said:
wich recovery are you useing,,,also wich radio are you on
Click to expand...
Click to collapse
cwm recovery v6.0.2.7
How can I know which radio I'm on??
Still nothing after reboot..
use the link wich fietspompje just given to you and follow what he has sed it will tell you on the black screen
hellothere74 said:
wich recovery are you useing,,,also wich radio are you on
Click to expand...
Click to collapse
I rebooted my phone but still no changes..still unresposive screen..
mikenirochiell said:
I rebooted my phone but still no changes..still unresposive screen..
Click to expand...
Click to collapse
i need to no what it says on the black screen
hellothere74 said:
i need to no what it says on the black screen
Click to expand...
Click to collapse
its the same as the image you posted..
I don't know what's next after that so iI rebooted.
mikenirochiell said:
its the same as the image you posted..
I don't know what's next after that so iI rebooted.
Click to expand...
Click to collapse
We want your device's version-main and cid!! Please copy paste all the text you can see from your cmd window over here! or we won't be able to help you...
vin4yak said:
We want your device's version-main and cid!! Please copy paste all the text you can see from your cmd window over here! or we won't be able to help you...
Click to expand...
Click to collapse
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\MykRo>cd C:/Fastboot
C:\Fastboot>fastboot getvar version-main
version-main: 3.19.709.2
finished. total time: -0.000s
C:\Fastboot>fastboot oem readcid
... INFODEBUG: cid: HTC__621
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Fastboot>
download this and flash it http://d-h.st/CNx
1 go to fastboot flash that recovery,,
2 reflash boot img
3 reflash rom
mikenirochiell said:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\MykRo>cd C:/Fastboot
C:\Fastboot>fastboot getvar version-main
version-main: 3.19.709.2
finished. total time: -0.000s
C:\Fastboot>fastboot oem readcid
... INFODEBUG: cid: HTC__621
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Fastboot>
Click to expand...
Click to collapse
Arrrghh! Taiwan device?!
There's no nandroid which matches your version-main, you can try to restore this backup : http://d-h.st/K7O
if you have officially received the JB update, it should work...
If you want to flash a custom rom, ICS roms won't work on your device because of the updated touch driver... Go to android development / original android development section and choose a JB rom!
also use this recovery, it is the only recovery which has a fully touch interface and works flawlessly: https://www.dropbox.com/s/p35p0tqf41jbj8b/recovery.img
Hi,
I have a serious problem. My phone for some reason was working fine, but all the sudden is now stuck in HBOOT.
i have tried recovery but the phone would just shut itself down. i couldn't not use adb even though before the phone went into this state, i turned the USB debugging mode on
this is the error message i got for trying to do fastboot flash recovery
target reported max download size of 1830727680 bytes
sending 'recovery' (14826 KB)...
OKAY [ 1.475s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.544s
please help , many thanks
Bump, I'm having the same problem on my tmobile m8
mmmgosu said:
Hi,
I have a serious problem. My phone for some reason was working fine, but all the sudden is now stuck in HBOOT.
i have tried recovery but the phone would just shut itself down. i couldn't not use adb even though before the phone went into this state, i turned the USB debugging mode on
this is the error message i got for trying to do fastboot flash recovery
target reported max download size of 1830727680 bytes
sending 'recovery' (14826 KB)...
OKAY [ 1.475s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.544s
please help , many thanks
Click to expand...
Click to collapse
raphi809 said:
Bump, I'm having the same problem on my tmobile m8
Click to expand...
Click to collapse
What versions of the M8 do you have?
EddyOS said:
What versions of the M8 do you have?
Click to expand...
Click to collapse
I have a t-mobile m8, I actually started a thread over there http://forum.xda-developers.com/tmobile-htc-one-m8/help/m8-bricked-soloution-t2818678 but so far no answers either
raphi809 said:
I have a t-mobile m8, I actually started a thread over there http://forum.xda-developers.com/tmobile-htc-one-m8/help/m8-bricked-soloution-t2818678 but so far no answers either
Click to expand...
Click to collapse
In which case stick to your thread as opposed to jumping on to others, makes it easier to follow
EddyOS said:
In which case stick to your thread as opposed to jumping on to others, makes it easier to follow
Click to expand...
Click to collapse
Yes, if you have already started a thread asking for help, don't jump around.
---------- Post added at 10:44 AM ---------- Previous post was at 10:42 AM ----------
mmmgosu said:
this is the error message i got for trying to do fastboot flash recovery
target reported max download size of 1830727680 bytes
sending 'recovery' (14826 KB)...
OKAY [ 1.475s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.544s
Click to expand...
Click to collapse
What response do you get for:
fastboot devices
If it returns the device ID, than try:
fastboot erase cache
Then try to flash recovery again.
Did you by chance try to factory reset in bootloader (corrupts the internal memory on modded devices)?
when i tried fastboot devices it returns an ID
but when i tried
fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.006s
i have at&t
Maybe try to flash one of the modded hboots?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Hawkysoft said:
Maybe try to flash one of the modded hboots?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
how do i do that?
fastboot oem rebootRUU
fastboot flash zip name_of.zip
fastboot reboot-bootloader
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Hard to help you if you do not even bother to answer all the questions posed to you. As I asked earlier:
Did you by chance try to factory reset in bootloader (corrupts the internal memory on modded devices)?
redpoint73 said:
Hard to help you if you do not even bother to answer all the questions posed to you. As I asked earlier:
Did you by chance try to factory reset in bootloader (corrupts the internal memory on modded devices)?
Click to expand...
Click to collapse
I tried factory reset but it doesn't seem to be doing anything, just a white screen with android picture.
what do you mean by " corrupts the internal memory on modded devices?"
i tried
fastboot oem rebootRUU
but it says ...
(bootloader) [DEBUG] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [DEBUG] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(560): error 2
(bootloader) Start Verify: 3
(bootloader) [DEBUG] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [DEBUG] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 0.018s]
finished. total time: 0.018s
question, can i flash TWRP with 0p6bimg.zip?
If yes, can anyone provide the file?
Thanks
mmmgosu said:
I tried factory reset but it doesn't seem to be doing anything, just a white screen with android picture.
what do you mean by " corrupts the internal memory on modded devices?"
Click to expand...
Click to collapse
It means you should never ever do that (factory reset in bootloader) if bootloader unlocked, rooted, etc.. Only within the OS Settings or in recovery.
What this means, is that on a stock device, factory reset in bootloader works normally; but on a modded (rooted, etc.) device this corrupts the internal memory and renders it unable to be read or written to. This is probably why can't wipe cacher, install custom recovery, reboot RUU, etc (all are giving you errors reading data; and I think this is the reason why).
Connect the phone to a Windows PC (sorry if that is not what you use, its all I know) and use Device Manager to format the phone's internal memory. Once its formatted try again to wipe cache and flash custom recovery again.
This is great info to tuck away for future reference. How should the memory be formatted? FAT32 or exFAT?
Sent from my Nexus 10
bruce7373 said:
How should the memory be formatted? FAT32 or exFAT?
Click to expand...
Click to collapse
FAT32.
redpoint73 said:
It means you should never ever do that (factory reset in bootloader) if bootloader unlocked, rooted, etc.. Only within the OS Settings or in recovery.
What this means, is that on a stock device, factory reset in bootloader works normally; but on a modded (rooted, etc.) device this corrupts the internal memory and renders it unable to be read or written to. This is probably why can't wipe cacher, install custom recovery, reboot RUU, etc (all are giving you errors reading data; and I think this is the reason why).
Connect the phone to a Windows PC (sorry if that is not what you use, its all I know) and use Device Manager to format the phone's internal memory. Once its formatted try again to wipe cache and flash custom recovery again.
Click to expand...
Click to collapse
How exactly does one format the phone's internal memory via Device Manager?
adriankeith said:
How exactly does one format the phone's internal memory via Device Manager?
Click to expand...
Click to collapse
Couldn't actually tell you "exactly" myself as I haven't personally had to do it. But I know its been given as advice many times, and reported to work (at least for some instances of corrupted internal memory or can't mount memory).
In brief, open Device Manager, browse to the device/internal memory, and try to find the option to format FAT32.
Ok, I'm in the same pickle as person above. Let me just post the state the phone was in before everything happened. Unlocked bootloader, s-on, Android revolution HD installed (4.4.3). Friend tried to get back to stock and now the phone is stuck in hboot. Things done to phone: bootloader relocked, tried to change tampered flag without success, flashed stock recovery and boot image. Fastboot devices returns Id, storage is not recognized, adb commands do not work. I think he also tried to do factory reset while in hboot. Just stumbled upon this format memory thing, will do it once I get home. What are the steps after, can I just flash the correct ROM.zip or some moded hboot? If you can just point me in right direction I would very much appreciate it, thanks. Also if you need any additional info just ask for it
Similar problem here also,
I could really use some help guys! The new GPE 6.0 images are out on XDA. http://forum.xda-developers.com/htc...uu-m8-google-play-edition-5-1-lmy470-t3226765
I did a full wipe then I put on the rom using the zip file first through TWRP and it did install but the radio drivers failed.
So I then downloaded the system img file ruu and renamed it to 0P6BIMG.zip and now it is just stuck in a loop and will not boot into the Operating system. It will just freeze at the White HTC logo.
I press the power button and the volume up button to reset the device then push the power button and volume down button to get into the bootloader the bootloader instantly selects Hboot and starts loading up the 0P6BIMG.zip. The phone then procedes to give me the highlighted HBoot option and the message "Press <POWER> to reboot." Which then reboots right into the White HTC loading screen.
The phone is unlocked and has s-on. I have tried using ADB commands but cannot get an ID with ADB devices command.
Can someone help a brotha out?
So I managed to get my phone to this state:
{
"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"
}
Actually I was using this tutorial: http://theunlockr.com/2014/07/15/how-to-unroot-the-htc-desire-816/
My laptop couldn't recognize the phone so I manually rebooted to fastboot, then I entered "fastboot oem relock" and tried to flash but it did NOT work. Now all I have is a bootloader menu. I also tried this but it says that the Hboot version is older. H E L P
Relock the bootloader and install custom ROM ? And are you try this command fastboot " fastboot flash zip 0P9CIMG.zip" ?
tifalyz said:
Relock the bootloader and install custom ROM ? And are you try this command fastboot " fastboot flash zip 0P9CIMG.zip" ?
Click to expand...
Click to collapse
Yup.
C:\Users\Chris\Desktop>fastboot flash zip 0P9CIMG.zip
< waiting for device >
sending 'zip' (1033121 KB)... OKAY [ 78.142s]
writing 'zip'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 153.473s
Try this RUU maybe? http://forum.xda-developers.com/desire-816/general/0p9cimga5ulk44desiresense60htceurope1-t2946515
If you still get the signature verify fail error theres something wrong.
FoxyDrew said:
Try this RUU maybe? http://forum.xda-developers.com/desire-816/general/0p9cimga5ulk44desiresense60htceurope1-t2946515
If you still get the signature verify fail error theres something wrong.
Click to expand...
Click to collapse
Since swearing around here is blocked, imma try something new
C:\Users\Chris\Desktop>fastboot flash zip filename.zip
sending 'zip' (1023339 KB)... OKAY [ 70.279s]
writing 'zip'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 144.966s
What does *** TAMPERED *** even mean though, it's on the top of the screen on the screenshot.
exlective said:
Since swearing around here is blocked, imma try something new
C:\Users\Chris\Desktop>fastboot flash zip filename.zip
sending 'zip' (1023339 KB)... OKAY [ 70.279s]
writing 'zip'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 144.966s
What does *** TAMPERED *** even mean though, it's on the top of the screen on the screenshot.
Click to expand...
Click to collapse
The tampered just means that your phone was previously unlocked/rooted.
Follow all the instructions in the second part of THIS thread, making sure to use YOUR RUU file.
If that fails, re-unlock your bootloader, re-flash a custom recovery, and install custom ROM or a backup.
I have to ask, why did you decide to unroot and relock?
Also swearing isn't allowed on the forums in any way, don't try to get around it.
FoxyDrew said:
The tampered just means that your phone was previously unlocked/rooted.
Follow all the instructions in the second part of THIS thread, making sure to use YOUR RUU file.
If that fails, re-unlock your bootloader, re-flash a custom recovery, and install custom ROM or a backup.
I have to ask, why did you decide to unroot and relock?
Also swearing isn't allowed on the forums in any way, don't try to get around it.
Click to expand...
Click to collapse
After it didn't work using CMD, I looked up the thread you linked and what do I see? You saying it should be done with the sdcard method haha, so I tried it that way and it worked. Thanks for all the help Drew.
I wanted to return to stock because of 3 reasons. I might be swapping my phone for an M7, because even though we have to wait till March/April, I do want that sweet, sweeeet Lollipop+Sense update (if the trade doesn't work), and because even though CM11 is stable, I got sick of it. CM12 has some minor bugs that just get on my nerves.
exlective said:
After it didn't work using CMD, I looked up the thread you linked and what do I see? You saying it should be done with the sdcard method haha, so I tried it that way and it worked. Thanks for all the help Drew.
I wanted to return to stock because of 3 reasons. I might be swapping my phone for an M7, because even though we have to wait till March/April, I do want that sweet, sweeeet Lollipop+Sense update (if the trade doesn't work), and because even though CM11 is stable, I got sick of it. CM12 has some minor bugs that just get on my nerves.
Click to expand...
Click to collapse
No problem, and the Desire 816 is also getting the Lollipop+Sense update from HTC in March.
FoxyDrew said:
No problem, and the Desire 816 is also getting the Lollipop+Sense update from HTC in March.
Click to expand...
Click to collapse
That's what I said At least I think that's what I said, I've been struggling with this phone for 4 hours and my brain is melting atm
os missing
exlective said:
So I managed to get my phone to this state:
Actually I was using this tutorial: http://theunlockr.com/2014/07/15/how-to-unroot-the-htc-desire-816/
My laptop couldn't recognize the phone so I manually rebooted to fastboot, then I entered "fastboot oem relock" and tried to flash but it did NOT work. Now all I have is a bootloader menu. I also tried this but it says that the Hboot version is older. H E L P
Click to expand...
Click to collapse
hii
can you please tell me how that happened .. how the OS deleted >> please
smtb said:
hii
can you please tell me how that happened .. how the OS deleted >> please
Click to expand...
Click to collapse
That's easy, if you wipe system partition in custom recovery, your Rom will be gone, you'll need to flash a nandroid backup (easy) or RUU (harder)to get it back
Hi xda!
I can't flash system with TWRP or Fastboot
Fastboot:
Code:
C:\Users\manager\Desktop\coils\Nexus>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.741s]
sending sparse 'system' 1/4 (516666 KB)...
OKAY [ 17.776s]
writing 'system' 1/4...
FAILED (remote: size too large)
finished. total time: 18.557s
TWRP:
{
"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"
}
I try fastboot erase system
I try repair partition in TWRP
I try change filesystem to ext2 and back to ext4
I try in TWRP
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/system
and
Code:
make_ext4fs /dev/block/mmcblk0p41
Can any body help me with this problem?
Your fastboot is old. Get the latest one from the SDK.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
Your fastboot is old. Get the latest one from the SDK.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I have the latest version, I use this fastboot early and everything was fine
bzz11g said:
I have the latest version, I use this fastboot early and everything was fine
Click to expand...
Click to collapse
Obviously not. The error you are getting is due to an out of date fastboot.
Sent from my Nexus 5X using Tapatalk
piousinquisitor said:
obviously not. The error you are getting is due to an out of date fastboot.
Sent from my nexus 5x using tapatalk
Click to expand...
Click to collapse
IT'S LATEST VERSION
Code:
Microsoft Windows [Version 6.1.7601]
(c) Корпорация Майкрософт (Microsoft Corp.), 2009. Все права защищены.
C:\Users\manager\Desktop\Nexus>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.532s]
sending sparse 'system' 1/4 (516666 KB)...
OKAY [ 17.605s]
writing 'system' 1/4...
FAILED (remote: size too large)
finished. total time: 18.178s
C:\Users\manager\Desktop\Nexus>fastboot --version
fastboot version 8f855a3d9b35-android
C:\Users\manager\Desktop\Nexus>
When i had this problem, i had a bad download. Go redownload the image you are attempting to flash, make sure to check MD5. And where are you getting your fastboot drivers from?
I try redownload firmware and verifi сhecksum, all is good, but I continue to watch same error, can any body help?
bzz11g said:
I try redownload firmware and verifi сhecksum, all is good, but I continue to watch same error, can any body help?
Click to expand...
Click to collapse
Have you updated your platform tools? This new 7.0 system.img takes a while to flash and updating that helped me.
Sent from my Nexus 5X using Tapatalk
Try with:
fastboot flash -S 512M system system.img
i had this error with the nexus 5, fixed by flashing with -s 512m.
Make sure to download the latest platform-tools, pal
That'll fugure out your problem for sure. The do the fastboot and you're just gonna be fine. No reason to go around bushes. Follow the Root 5x thread.
SlimSnoopOS said:
Have you updated your platform tools? This new 7.0 system.img takes a while to flash and updating that helped me.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I try system.img from 7.0 and 6.0.1 and always get the same error
AtField said:
Try with:
fastboot flash -S 512M system system.img
i had this error with the nexus 5, fixed by flashing with -s 512m.
Click to expand...
Click to collapse
yes i try it in first time, without results...
2 All,
please look at the screenshot in first message with TWRP log, I think problem in system partition, other img (vendor, userdata, cache etc.) installed without problems
may be some body know how I can repair system partition across ADB Shell?
bzz11g said:
I try system.img from 7.0 and 6.0.1 and always get the same error
yes i try it in first time, without results...
2 All,
please look at the screenshot in first message with TWRP log, I think problem in system partition, other img (vendor, userdata, cache etc.) installed without problems
may be some body know how I can repair system partition across ADB Shell?
Click to expand...
Click to collapse
You tried with the added -S 512M ?
Because in the first screenshot i dont see that part of the command.
Anyway, if you already tried with -s 512m I'm sorry but I cant help you.
AtField said:
You tried with the added -S 512M ?
Because in the first screenshot i dont see that part of the command.
Anyway, if you already tried with -s 512m I'm sorry but I cant help you.
Click to expand...
Click to collapse
yes, i try this key's
if you look in log
Code:
target reported max download size of 536870912 bytes
it already 512 Mb
536870912 bytes / 1024 = 524288 kB / 1024 = 512 Mb
@bzz11g Issue the following command (after updating your fastboot, lol) and try again.
Code:
fastboot format system
note that there is a difference between erase and format.
Have you tried using the flash-all script?
If nothing else works use the TOT method to fix your phone.
@PiousInquisitor thank you for your note, I already try it..
I try install full stock with flash-all.bat and NRT, and always see the same error
Yesterday I can flash system.img with ADB shell and DD command:
Code:
ADB shell dd if=/sdcard/system.img of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/system
and everything went well, but I still in bootloop and see Google logo..
Can anybody make TWRP backup of system 6.0.1 for me?
bzz11g said:
@PiousInquisitor thank you for your note, I already try it..
I try install full stock with flash-all.bat and NRT, and always see the same error
Yesterday I can flash system.img with ADB shell and DD command:
Code:
ADB shell dd if=/sdcard/system.img of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/system
and everything went well, but I still in bootloop and see Google logo..
Can anybody make TWRP backup of system 6.0.1 for me?
Click to expand...
Click to collapse
You can't flash system.img that way. It isn't a standard .img file.
I don't know what is wrong with your setup, but if you want you can try fastboot from here
http://forum.xda-developers.com/nexus-5x/general/psa-fix-adb-doesnt-winxp-t3403955
I know for sure it has no problems flashing the NRD90M system.img as I did it a few days ago.
If that doesn't work, then the problem is not with fastboot or the usb dll that uses.
sfhub said:
You can't flash system.img that way. It isn't a standard .img file.
Click to expand...
Click to collapse
I know, I want try to restore System with TWRP
sfhub said:
I don't know what is wrong with your setup, but if you want you can try fastboot from here
http://forum.xda-developers.com/nexus-5x/general/psa-fix-adb-doesnt-winxp-t3403955
Click to expand...
Click to collapse
I try it now, thank you
@sfhub
Code:
C:\Users\manager\Desktop\platform-tools-v23.1>fastboot devices
0106fb608bc03dee fastboot
C:\Users\manager\Desktop\platform-tools-v23.1>fastboot -S 512M flash system syst
em.img
erasing 'system'...
OKAY [ 0.556s]
sending sparse 'system' (516666 KB)...
OKAY [ 17.587s]
writing 'system'...
FAILED (remote: size too large)
finished. total time: 18.170s
bzz11g said:
@sfhub
Code:
C:\Users\manager\Desktop\platform-tools-v23.1>fastboot devices
0106fb608bc03dee fastboot
C:\Users\manager\Desktop\platform-tools-v23.1>fastboot -S 512M flash system syst
em.img
erasing 'system'...
OKAY [ 0.556s]
sending sparse 'system' (516666 KB)...
OKAY [ 17.587s]
writing 'system'...
FAILED (remote: size too large)
finished. total time: 18.170s
Click to expand...
Click to collapse
So it isn't related to fastboot.
Are any of your partitions on the remote device full? cache or userdata?
If you can boot into stock recovery, you might want to try the FULL OTA from the nexus factory image site which you can try installing over adb sideload.
---------- Post added at 11:44 AM ---------- Previous post was at 11:42 AM ----------
bzz11g said:
I know, I want try to restore System with TWRP
Click to expand...
Click to collapse
Is that system.img from a factory image or is it from twrp backup?
If it is from factory image, I am not sure if TWRP does what is necessary to restore it either.
---------- Post added at 11:55 AM ---------- Previous post was at 11:44 AM ----------
You didn't mention you were at Qualcomm loader.
You need to use LGUP and the TOT file in the other thread.
I got the same error message a while back - I solved it by re-installing SDK on my computer. I know you have previously said that you have the most recent version of SDK, and I thought I did as well. But I went ahead and uninstalled everything related to SDK on my computer and reinstalled a fresh version. Once I tried flashing system.img after that, it worked perfectly. I'd suggest that you try the same.