I have a friend who put twrp and cid 111111111 hboot 2.14 had viper couldnt make calls wiped data and he deleted his sdcard now he has no OS
i was able to flash recovery on his phone but thats where i'm at..
scrizo said:
I have a friend who put twrp and cid 111111111 hboot 2.14 had viper couldnt make calls wiped data and he deleted his sdcard now he has no OS
i was able to flash recovery on his phone but thats where i'm at..
Click to expand...
Click to collapse
S-ON or S-OFF?
What version of recovery did you flash?
Did he corrupt SD card by doing a factory reset in bootloader or just format it?
exad said:
S-ON or S-OFF?
What version of recovery did you flash?
Did he corrupt SD card by doing a factory reset in bootloader or just format it?
Click to expand...
Click to collapse
You're too fast man
Sent from my Evita
I flashed 2.5.0.0
S-Off
I don't know he did have problems with TWRP not being able to write to .twrp file. If he corrupted the sdcard is he fubared
exad said:
S-ON or S-OFF?
What version of recovery did you flash?
Did he corrupt SD card by doing a factory reset in bootloader or just format it?
Click to expand...
Click to collapse
*UPDATE*
I am using adb push ViperXL-3.2.7 /sdcard/ and it appears to be pushing the file so far.
I am able to do this in recovery mode
Tried to install ViperXL failed.
Unable to mount '/sdcard'
Unable to mount storage
TWRP 2.5 is full of bugs. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery and try flashing ROM again.
Sent from my Evita
After flashing twrp 2.6 you may have to wipe the SD card within twrp if the SDCARD is corrupt.
problem htc.dialer stops working using viperxl
timmaaa said:
TWRP 2.5 is full of bugs. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery and try flashing ROM again.
Sent from my Evita
Click to expand...
Click to collapse
scrizo said:
problem htc.dialer stops working using viperxl
Click to expand...
Click to collapse
That's because there was CWM touch on there previously.
To fix:
reflash CWM touch
fastboot erase cache
flash cwm older NON touch
fastboot erase cache
reflash twrp 2.6
fastboot erase cache
fasctory reset IN TWRP 2.6
Then wipe everything and flash viper XL
I had flashed your 2.6 twrp and wiped everything and did what you said then pushed the viperxl on there and installed and did the wipe data do i still need to reflash the cwm touch and etc
exad said:
That's because there was CWM touch on there previously.
To fix:
reflash CWM touch
fastboot erase cache
flash cwm older NON touch
fastboot erase cache
reflash twrp 2.6
fastboot erase cache
fasctory reset IN TWRP 2.6
Then wipe everything and flash viper XL
Click to expand...
Click to collapse
did everything you said still the same error with htc.dialer i have a htc onex can i transfer my dialer to his phone?
exad said:
That's because there was CWM touch on there previously.
To fix:
reflash CWM touch
fastboot erase cache
flash cwm older NON touch
fastboot erase cache
reflash twrp 2.6
fastboot erase cache
fasctory reset IN TWRP 2.6
Then wipe everything and flash viper XL
Click to expand...
Click to collapse
No that's the only way to fix it.
Sent from my One X using xda app-developers app
Dang it is not working then. still have the issue with the dialer not working.
exad said:
No that's the only way to fix it.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
If this helps he has build # 3.17
Did you flash the three different versions of recovery?
Sent from my Evita
you mean cwm touch
cwm older
twrp?
timmaaa said:
Did you flash the three different versions of recovery?
Sent from my Evita
Click to expand...
Click to collapse
Yeah
Sent from my Evita
yes I flashed CWM touch
I flashed non touch
I flashed twrp 2.6
factory reset
installed viperxl
wiped data
timmaaa said:
Yeah
Sent from my Evita
Click to expand...
Click to collapse
You should have wiped everything (cache/dalvik cache/factory reset/system) before flashing Viper.
Sent from my Evita
Related
Can i flash from 4.0.4 to a lower version rom thru recovery? im on aokp 4.0.4 now
Yes, it should work if you wipe data, system, cache, and then.flash the rom
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
aryehzev said:
Yes, it should work if you wipe data, system, cache, and then.flash the rom
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Click to expand...
Click to collapse
i just tried reflashing to trad rom 4.0.3 thru recovery, it said install is succseful, but just booted to aokp.... what the hell... please man, help me
vaidas196 said:
i just tried reflashing to trad rom 4.0.3 thru recovery, it said install is succseful, but just booted to aokp.... what the hell... please man, help me
Click to expand...
Click to collapse
reflashed again and stuck on bootscreen
I also faced a similar problem when downgrading OS. Was stuck on Boot animation. I had to do a factory reset from the recovery and flash it again to get it t work fine. Make sure you erase data, just erasing cache/ dalvik might not work.
Sent from my Amazon Kindle Fire using Tapatalk 2
sidthegreatest said:
I also faced a similar problem when downgrading OS. Was stuck on Boot animation. I had to do a factory reset from the recovery and flash it again to get it t work fine. Make sure you erase data, just erasing cache/ dalvik might not work.
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
i wiped everything.. im still stuck...
please dudes.. help me. i must do it today because im screwed.. i'm S-ON RL with hboot 1.27.0000 and i have recovery. i do full wipe/dalvik/cahce and whenever i install any rom i either cant install it or im stuck on bootlscreen! please dudes!
vaidas196 said:
please dudes.. help me. i must do it today because im screwed.. i'm S-ON RL with hboot 1.27.0000 and i have recovery. i do full wipe/dalvik/cahce and whenever i install any rom i either cant install it or im stuck on bootlscreen! please dudes!
Click to expand...
Click to collapse
Flash boot.img from the ROM manually from fastboot.
Put the boot.img from the zip file to your adb folder.
Connect your phone in fastboot USB
Open a command window
cd to the adb folder
for example:
Code:
cd c:\android
Then type:
Code:
fastboot flash boot boot.img
Then type:
Code:
fastboot reboot
kgs1992 said:
Flash boot.img from the ROM manually from fastboot.
Put the boot.img from the zip file to your adb folder.
Connect your phone in fastboot USB
Open a command window
cd to the adb folder
for example:
Code:
cd c:\android
Then type:
Code:
fastboot flash boot boot.img
Then type:
Code:
fastboot reboot
Click to expand...
Click to collapse
it worked! THANK YOU
Okay, I tried putting a new rom on my at&t one xl, and it did something horribly wrong. I was able to get to recovery and it told me I had no operating system, the I tried flashing a new rom again. At this point it restarted the phone got stuck at the splash screen and now I cant even get to recovery just the fast boot and boot loader. Any help would greatly appreciated.
You haven't given any of the vital information required to help you. Please provide the following:
hboot/firmware version
S-on or s-off
Recovery version
What ROM(s) you were trying to flash
What you have done to try to recover
Sent from my Evita
timmaaa said:
You haven't given any of the vital information required to help you. Please provide the following:
hboot/firmware version
S-on or s-off
Recovery version
What ROM(s) you were trying to flash
What you have done to try to recover
Sent from my Evita
Click to expand...
Click to collapse
hboot 1.14.002
s is off
cant remember recovery version since I can't access it
I had viper rom and I was going to cyanogen mod 10.1
and I thought I had a titanium backup but my whole sd card go deleted, so I mounted my sd card and got the rom again and flashed it and at that point I couldn't go back to recovery
Did you read the OP for cm10.1? It states in the requirements that you must RUU up to the latest (3.18) to run that ROM. In terms of your recovery, just flash it again from fastboot.
Sent from my Evita
timmaaa said:
Did you read the OP for cm10.1? It states in the requirements that you must RUU up to the latest (3.18) to run that ROM. In terms of your recovery, just flash it again from fastboot.
Sent from my Evita
Click to expand...
Click to collapse
I must of completely overseen that. and sir the only option I have on my boot is fast boot, recovery, factory reset, clear storage, simlock, image crc, and power down. I don't know how to even flash things at this point.
and only options I fast boot are bootloader, reboot, reboot boot loader and powerdown
That's all you need to RUU, it's an exe file that you just run while your phone is connected in fastboot mode. You'll need top flash your recovery again, then you can flash a ROM.
Download the RUU
Run the RUU
Download recovery
Flash recovery
Flash ROM
The fastboot command to flash the recovery is:
fastboot flash recovery "recovery.img"
(The exact recovery filename, without the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you can enter recovery on your phone, mount usb storage, copy ROM to phone, flash ROM.
Sent from my Evita
Thanks guys. My kids an idiot and did this today to his phone (my old phone). He got the information from you guys and left it to me to fix when I got home.
timmaaa said:
That's all you need to RUU, it's an exe file that you just run while your phone is connected in fastboot mode. You'll need top flash your recovery again, then you can flash a ROM.
Download the RUU
Run the RUU
Download recovery
Flash recovery
Flash ROM
The fastboot command to flash the recovery is:
fastboot flash recovery "recovery.img"
(The exact recovery filename, without the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you can enter recovery on your phone, mount usb storage, copy ROM to phone, flash ROM.
Sent from my Evita
Click to expand...
Click to collapse
Cool glad ur all set
Sent from my HTC One XL using xda premium
Hi,
I have an AT&T HTC One X with no OS. I wiped it when I was trying to flash a custom ROM.
I only have access to bootloader and TWRP. Fastboot is working fine but TWRP is not. It does
mount properly, and adb sideload fails as well. I am using a Windows 7 PC and used a USB 2.0 port.
I installed some HTC Drivers from here:
http://forum.xda-developers.com/showthread.php?t=2217396
but it still says "device drivers failed to install" when I boot into recovery.
When I try to mount, it does not let me mount the sdcard. I see an E: drive on my
PC but it is inaccessible.
I have S-On, my bootloader is unlocked, and I have hboot version 2.14 if that info helps.
Does anybody have any suggestions as to what I can try next?
First thing you need to do is clear your post up a bit. You said you have access to TWRP but it isn't working, can you elaborate on that please?
You also said that it does mount, but then you said later it doesn't mount, which is it?
Have you performed a factory reset from the bootloader at any point?
Exactly which ROM(s) did you try to install? I need the exact filename(s) please.
Did you remember to flash the boot.img with fastboot after flashing the ROM?
Do you have a TWRP backup on your phone?
Please answer all questions with as much relevant detail as possible, that'll aid me to help you properly.
Sent from my Evita
I helped him over teamviewer so I can clarify the situation. He can't mount in TWRP, it must of been a typo. It seems he cleared everything when he was trying to wipe to flash a rom. I believe it was ViperXL. He has no backup and sideload does not work as well. Hopefully that will clear things up a little bit more. I installed some newer HTC Drivers since the ones he had were old. The only thing that works seems to be fastboot at this point.
Sent from my HTC One X using Tapatalk
timmaaa said:
First thing you need to do is clear your post up a bit. You said you have access to TWRP but it isn't working, can you elaborate on that please?
You also said that it does mount, but then you said later it doesn't mount, which is it?
Have you performed a factory reset from the bootloader at any point?
Exactly which ROM(s) did you try to install? I need the exact filename(s) please.
Did you remember to flash the boot.img with fastboot after flashing the ROM?
Do you have a TWRP backup on your phone?
Please answer all questions with as much relevant detail as possible, that'll aid me to help you properly.
Sent from my Evita
Click to expand...
Click to collapse
Sorry it was a Typo, I was not able to mount at all. The error said "unable to mount /sdcard"
Yes I have tried performing a factory reset from bootloader but the phone restarts and comes back to TWRP and then same thing.
I tried installing the ViperXL ROM but was not successful.
I was not able to flash the ROM and I tried to fix that but meanwhile looks like I wiped all what I had on my Phone, so no but I did try to flash a new boot.img after and it didnt work.
I dont think I have any TWRP backup on my phone, even though I tried flashing new TWRP but all failed.
Ok first thing, don't ever perform a factory reset from the bootloader because it corrupts your sd card. That's why you're experiencing problems now. You need to wipe the sd card/internal storage using TWRP 2.6 to make it usable again. If you don't currently have TWRP 2.6 installed you'll need to do that. Download it from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you should be able to mount your sd card using TWRP and copy a ROM across to flash.
Sent from my Evita
timmaaa said:
Ok first thing, don't ever perform a factory reset from the bootloader because it corrupts your sd card. That's why you're experiencing problems now. You need to wipe the sd card/internal storage using TWRP 2.6 to make it usable again. If you don't currently have TWRP 2.6 installed you'll need to do that. Download it from . Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you should be able to mount your sd card using TWRP and copy a ROM across to flash.
Sent from my Evita
Click to expand...
Click to collapse
So I followed all the above steps as noted; I had TWRP 2.6.3.0 earlier, I flashed the new TWRP 2.6.0.0 from the link you provided.All
successfully done.
-------------------------------------------------------------------------------------------------------
C:\Fastboot>fastboot devices
HT29WW300913 fastboot
C:\Fastboot>fastboot flash recovery "openrecovery-twrp-2.6
.0.0-evita.img"
sending 'recovery' (8000 KB)... OKAY [ 1.530s]
writing 'recovery'... OKAY [ 1.900s]
finished. total time: 3.430s
C:\Fastboot>fastboot erase cache
erasing 'cache'... OKAY [ 0.120s]
finished. total time: 0.120s
C:\Fastboot>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.070s]
finished. total time: 0.070s
---------------------------------------------------------------------------------------------------------
I rebooted into recovery, still came up as TWRP 2.6.3.0, then I went to TWRP reboot and chose Recovery, phone rebooted into TWRP 2.6.0.0
Tried mounting (could not select /sd card and /cache(expected as we erased it)) and ADB sideload, got the same errors as before. Unable to mount /sdcard.
Rebooted again and it displayed TWRP 2.6.3.0
Did you wipe the sd card/internal storage like I said before trying to mount it?
Sent from my Evita
timmaaa said:
Did you wipe the sd card/internal storage like I said before trying to mount it?
Sent from my Evita
Click to expand...
Click to collapse
Yes I did
And which recovery is currently installed?
Sent from my Evita
timmaaa said:
And which recovery is currently installed?
Sent from my Evita
Click to expand...
Click to collapse
Its 2.6.3.0, but in recovery when I go into option TWRP reboot and chose Recovery button, phone reboots into TWRP 2.6.0.0 and when I reboot it again, its 2.6.3.0
That's really screwy. I think you should try installing recovery again. What happens when you boot the phone normally?
Sent from my Evita
timmaaa said:
That's really screwy. I think you should try installing recovery again. What happens when you boot the phone normally?
Sent from my Evita
Click to expand...
Click to collapse
Ok good news, something happened, I tried all the steps again carefully and now I see TWRP 2.6.0.0 on boot and I am able to mount the sdcard and my computer now recognises the phone and I can manually copy files on to it.
Now in order to not mess it up anymore, should I just copy ViperXL ROM or should I use ADB sideload?
tapukakababa said:
Ok good news, something happened, I tried all the steps again carefully and now I see TWRP 2.6.0.0 on boot and I am able to mount the sdcard and my computer now recognises the phone and I can manually copy files on to it.
Now in order to not mess it up anymore, should I just copy ViperXL ROM or should I use ADB sideload?
Click to expand...
Click to collapse
Either one should be fine. If you have S-ON and the phone gets stuck on the HTC screen, you have to flash the boot.img. here's how to do it.
1. On your PC in the ViperXL.zip, take out the boot.img and put it in the directory where you have the adb and fastboot files.
2. Boot into fastboot.
3.Open cmd. Change the directory to the folder where you have those files.
4.type "fastboot flash boot boot.img"
5. Reboot the phone.
The phone should boot.
Sent from my One Xl using Tapatalk
Definitely install through TWRP. You shouldn't need to flash a boot.img because Viper uses an aroma installer which does that for you. But, if for some reason it doesn't work just flash the boot.img via fastboot.
Sent from my Evita
timmaaa said:
Definitely install through TWRP. You shouldn't need to flash a boot.img because Viper uses an aroma installer which does that for you. But, if for some reason it doesn't work just flash the boot.img via fastboot.
Sent from my Evita
Click to expand...
Click to collapse
So I flashed the boot image, then copied ViperXL and installed it through TWRP, it failed.
Exactly which error is it giving you? Did you check the md5 of the downloaded file? Are you still on TWRP 2.6?
Sent from my Evita
timmaaa said:
Exactly which error is it giving you? Did you check the md5 of the downloaded file? Are you still on TWRP 2.6?
Sent from my Evita
Click to expand...
Click to collapse
No I did not check the MD5, yes I'm on TWRP 2.6.0.0 and the errors it gives are as follows:
unable to mount '/cache'
unable to open zip
Error flashing zip
Always check the md5. It's possibly corrupt.
Sent from my Evita
timmaaa said:
Always check the md5. It's possibly corrupt.
Sent from my Evita
Click to expand...
Click to collapse
Yup redownloaded the file, checked/compared MD5, copied it back to the phone, removed the previous bad copy, flashed ROM successfully..., as per the message but system reboots to recovery.. is that expected?
And I still see both the TWRP's 2.6.3.0 and 2.6.0.0 the phone needs couple reboots in order to get to TWRP 2.6.0.0 but automatic reboot is in TWRP 2.6.3.0 whats the deal here?
I have no idea why your recovery is acting like that. Hopefully someone else can chime in on that.
Sent from my Evita
Hello everyone,
I am a new htc sensation user and I recently rooted it using the traditional method and have been installing roms since then.
However, recently when I was installing CarbonRom Kitkat 4.4.3, the ClockWork Mod recovery told me that I cannot flash the rom ( I don't know for what reason). I thought it was something to do with my recovery. So I decided to flash 4EXT touch recovery but as I have S-on, even after giving the command through fastboot for erasing recovery and all the partitions "fastboot -w" , the command prompt gave me this error " remote access not allowed". So I thought of going on with the flashing and flashed the 4EXT recovery image through fastboot. But when I tried to boot into recovery , the phone was just stuck on the htc white screen.
As I did not erase the recovery and flashed a new recovery, i think that I have overlapped the two recoveries and have corrupted them. Now, my phone boots only into the bootloader and I also have s-on. Can anyone please tell me how to install the stock rom (as I would like to revert back to the original rom) through bootloader and fastboot? i heard about the PG58IMG method but will it work on s-on? Please help me out.
Hi, im guessing u already have recovery.img in ur fastboot folder so try this command from fastboot
fastboot boot recovery.img
Hopefully that will get u there so u can flash a rom but u will have to download 4ext recovery updater app once phone is booted to flash recovery coz doing above command only boots recovery, doesnt flash it. It works on desire s and desire so it should work for sensation too (hopefully)
jmcclue said:
Hi, im guessing u already have recovery.img in ur fastboot folder so try this command from fastboot
fastboot boot recovery.img
Hopefully that will get u there so u can flash a rom but u will have to download 4ext recovery updater app once phone is booted to flash recovery coz doing above command only boots recovery, doesnt flash it. It works on desire s and desire so it should work for sensation too (hopefully)
Click to expand...
Click to collapse
So this means that I should first flash the recovery and then boot it using the command
fastboot boot recovery.img
?? or should I just boot it up using the command . And is there anyway to give any master commands like erase a partition while on s-on? And which recovery do u prefer CWM or 4EXT?
hammadyi said:
So this means that I should first flash the recovery and then boot it using the command
fastboot boot recovery.img
?? or should I just boot it up using the command . And is there anyway to give any master commands like erase a partition while on s-on? And which recovery do u prefer CWM or 4EXT?
Click to expand...
Click to collapse
since you are on S-ON go for 4ext
rzr86 said:
since you are on S-ON go for 4ext
Click to expand...
Click to collapse
That is actually where the problem started from. i tried to install 4ext before erasing CWM and I think that caused the problem.
Do you think that recoveries can be overlapped or am i just being pointless? And can you tell me about any master commands like erasing a parition that will work with s-on?
hammadyi said:
That is actually where the problem started from. i tried to install 4ext before erasing CWM and I think that caused the problem.
Do you think that recoveries can be overlapped or am i just being pointless? And can you tell me about any master commands like erasing a parition that will work with s-on?
Click to expand...
Click to collapse
you can overwrite 4ext in top of cwm
i used to have cwm but i changed it with 4ext using only the command
fastboot fash recovery recovery.img
i didn't use any command for erasing partitions
rzr86 said:
you can overwrite 4ext in top of cwm
i used to have cwm but i changed it with 4ext using only the command
fastboot fash recovery recovery.img
i didn't use any command for erasing partitions
Click to expand...
Click to collapse
I also used the same commands but since then I am not able to get into the recovery. it just shows the htc logo on white background
Do you think it has something to do with s-on? were you on s-off when you flashed the recovery?
hammadyi said:
I also used the same commands but since then I am not able to get into the recovery. it just shows the htc logo on white background
Do you think it has something to do with s-on? were you on s-off when you flashed the recovery?
Click to expand...
Click to collapse
Nothing to do with s-on. Try flashing 4ext recovery again
fastboot flash recovery recovery.img
If that doesnt work then try what i said earlier
fastboot boot recovery.img
hammadyi said:
I also used the same commands but since then I am not able to get into the recovery. it just shows the htc logo on white background
Do you think it has something to do with s-on? were you on s-off when you flashed the recovery?
Click to expand...
Click to collapse
no was on S-ON
I saw this forum on xda which says that we can use the riff box to install partitions so can I do the same with my recovery?
http://forum.xda-developers.com/showthread.php?p=53343296
hammadyi said:
I saw this forum on xda which says that we can use the riff box to install partitions so can I do the same with my recovery?
http://forum.xda-developers.com/showthread.php?p=53343296
Click to expand...
Click to collapse
i don't think you need the riff box now
you can go first for ruu.exe to restore everything back to stock
hammadyi said:
I saw this forum on xda which says that we can use the riff box to install partitions so can I do the same with my recovery?
http://forum.xda-developers.com/showthread.php?p=53343296
Click to expand...
Click to collapse
Did u try the command
fastboot boot recovery.img
I tried it last night on my sensation and it works, boots u into recovery.
jmcclue said:
Did u try the command
fastboot boot recovery.img
I tried it last night on my sensation and it works, boots u into recovery.
Click to expand...
Click to collapse
So i just flashed stock htc sensation recovery but I do not know how to install the stock rom through stock recovery can you tell me how to do that?
hammadyi said:
So i just flashed stock htc sensation recovery but I do not know how to install the stock rom through stock recovery can you tell me how to do that?
Click to expand...
Click to collapse
connect your device in fastboot mode to pc
double click the ruu from pc and follow the on screen instructions
by the way did you do first as jmcclue told you?
rzr86 said:
connect your device in fastboot mode to pc
double click the ruu from pc and follow the on screen instructions
by the way did you do first as jmcclue told you?
Click to expand...
Click to collapse
yes i did that but as there was no recovery it would not boot but after installing the stock rom it worked
hammadyi said:
yes i did that but as there was no recovery it would not boot but after installing the stock rom it worked
Click to expand...
Click to collapse
so now you have access to the OS
did you try again to flash a custom recovery?
rzr86 said:
so now you have access to the OS
did you try again to flash a custom recovery?
Click to expand...
Click to collapse
actually it did not go according to plan and while installing the ruu it failed. so now I am looking for a signed stock rom to install through fastboot using this command
fastboot update update.zip
would that be fine?
hammadyi said:
actually it did not go according to plan and while installing the ruu it failed. so now I am looking for a signed stock rom to install through fastboot using this command
fastboot update update.zip
would that be fine?
Click to expand...
Click to collapse
read from this thread-> 4. Flashing RUU manually
http://forum.xda-developers.com/showthread.php?t=1672425
i don't know if this command exists but you can use this one
fastboot flash zip pg58img.zip
edit: by the way what failure did you have with ruu?
Hello sorry for my bad English I speak Spanish.
I have a Nexus 5 32 GB but now it is 16GB ...
Last month I updated my smartphone to Android 5.1.0 (manually) from bootloader:
fastboot flash bootloader bootloader-hammerhead-hhz12f.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-2.0.50.2.25.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot
When I tried to copy my music I received the "Insufficient memory storage" message :crying:. I checked the Storage menu and it says that my smartphone has only 16GB now . I don't understand what happened because I always update my smartphone from bootloader.
Do a factory reset in the stock recovery and clear cache. This is a common problem. Back up first
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Do a factory reset in the stock recovery and clear cache. This is a common problem. Back up first
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I forgot tell you but I tried flashing Android 4.4 and other official ROMs but I still have the same problem.
hectorkrrillo said:
I forgot tell you but I tried flashing Android 4.4 and other official ROMs but I still have the same problem.
Click to expand...
Click to collapse
That is why you have to do a factery reset in stock recovery.
Problem
I have some problem :/
pipo406 said:
I have some problem :/
Click to expand...
Click to collapse
Do a factory reset in stock recovery
If factory reset does not work (didn't for me for some reason), install TWRP recovery, go to Wipe and choose Format Data. This worked for me. Of course all your data will be lost, but if you backed up, no harm done.
eross said:
If factory reset does not work (didn't for me for some reason), install TWRP recovery, go to Wipe and choose Format Data. This worked for me. Of course all your data will be lost, but if you backed up, no harm done.
Click to expand...
Click to collapse
Ohhh!! Thanks! My phone has 32GB again! :good::good::good:.... I had root on my Nexus 5 and TWRP recovery, I did just "Format Data" from TWRP and wala! 32GB is back... I didn't try to apply factory reset from ROM because I have root.
hectorkrrillo said:
Ohhh!! Thanks! My phone has 32GB again! :good::good::good:.... I had root on my Nexus 5 and TWRP recovery, I did just "Format Data" from TWRP and wala! 32GB is back... I didn't try to apply factory reset from ROM because I have root.
Click to expand...
Click to collapse
Glad to hear that :good: