Related
I just helped a buddy (this never happened before) and his mytouch is rooted. He upgraded his SPL to Haykuro's and then, through fastboot, he flashed Amon_Ra's 1.2.2 recovery image. Now, we can't get it past the mytouch screen, but can get into fastboot. Any ideas?
Try flashing another rom?
If you can get into fastboot, you can send a new image to the phone.
I don't recall the exact commands, but if you're in fastboot, you're still good.
cursordroid said:
If you can get into fastboot, you can send a new image to the phone.
I don't recall the exact commands, but if you're in fastboot, you're still good.
Click to expand...
Click to collapse
Great man...does anyone know the commands?
Fastboot the recovery image, and then from the recovery, you can flash the new rom.
xyzulu said:
Fastboot the recovery image, and then from the recovery, you can flash the new rom.
Click to expand...
Click to collapse
the recovery image is there. We cant into to recovery to apply the rom.
Get yourself the proper recovery.img for that phone. Not sure what it is, but a quick search will find it. Search for 'mytouch recovery' or 'mt3g recovery'.
Then with the recovery image in your SDK tools folder, run:
Code:
fastboot boot recovery.img
That should at least get you to a point where you can flash a new ROM and commit the proper recovery image to flash using adb commands.
I can't hold your hand through the whole thing, I don't have that phone, but I've been in your situation before.
Ok we tried it, now it says... FAILED(remote: partition does not exist!)
anyone have an idea?
Try to erase Cache
fastboot erase cache
fastboot erase recovery
then flash recovery:
fastboot flash recovery recoveryxxxxxx***.img (***I'm not sure of the version you use...)
antonram said:
fastboot erase cache
fastboot erase recovery
then flash recovery:
fastboot flash recovery recoveryxxxxxx***.img (***I'm not sure of the version you use...)
Click to expand...
Click to collapse
Yeah that's exactl what we did and it worked.
The thing is, we erased the recovvery image and reinstalled it, but now again, it won't go into recovery. I have a feeling he downloaded the wrong Amos_Ra recovery. Probably one for the 32a.
Dear all, I need your help ASAP.
My phone (rooted) doesn't boot now, adb does not recognizes, fastboot still ok. And I don't know what to do.
Recently I rooted my Desire S and succeeded with the stock ROM. After a coupe of days I dicided to flash Endymion, from here: http://forum.xda-developers.com/showthread.php?t=1310845
I downloaded Endymion 3.1 into SD, then used Rom Manager to flash it. But then it was not be able to reboot (stucked on splash screen).
After that I rebooted into recovery (4EXT) and formated system, data, cache, boot and retried to install Endymion 3.1.
But then it became worse, now I can't use adb (always says: device not found), normal boots always stucks at splash screen (with green "HTC"). No hard button can be used, I need to reboot by take off the battery, then put it back on.
fastboot still seems working fine if I reboot to fastboot mode, but when I try "fastboot erase ...", I get "remote: not allowed". But other commands (fastboot flash...) still ok.
4EXT recovery is also still working.
Please help me to install some ROM at least. A lot of thanks.
Not quite sure, but could it be a faulty eMMC chip? Since you did mention you pulled out the battery.
http://forum.xda-developers.com/showthread.php?t=1314629
I did have a similar problem before myself.
So can you get into the boot loader? I'm assuming so since u got into fast boot. I would try flashing an update.zip through there, such as a stock from containing recovery.img,system.img...etc.
Sent from my HTC Desire HD using xda premium
Thank you for replies.
@microlah: I think my problem is not eMMC because I did not get those errors.
@stumpyz9: Before trying to flash Endymion 3.1, I made a backup of the rooted Sense 3.0 through Rom Manager -> a collection of *.img files.
I have tried to boot into fastboot, and executed these commands:
fastboot erase boot -> Error: remote not allowed
fastboot erase recovery -> Error: remote not allowed
fastboot flash system system.img -> OK
fastboot flash boot boot.img -> OK
fastboot flash userdata data.img -> OK
fastboot flash recovery recovery.img -> OK
but after this, the phone still does not boot normally.
Please tell me if I did something wrong or not. I dont know how to make update.zip from *.img files, and dont know where to get and choose the right stock rom for my phone.
d_t_kien said:
Dear all, I need your help ASAP.
My phone (rooted) doesn't boot now, adb does not recognizes, fastboot still ok. And I don't know what to do.
Recently I rooted my Desire S and succeeded with the stock ROM. After a coupe of days I dicided to flash Endymion, from here: http://forum.xda-developers.com/showthread.php?t=1310845
I downloaded Endymion 3.1 into SD, then used Rom Manager to flash it. But then it was not be able to reboot (stucked on splash screen).
Click to expand...
Click to collapse
Are you S-OFF or htcdev unlocked ? If you're still S-on you have to manually flash boot.img with fastboot to get Endymion or others custom roms working.
d_t_kien said:
Thank you for replies.
@microlah: I think my problem is not eMMC because I did not get those errors.
@stumpyz9: Before trying to flash Endymion 3.1, I made a backup of the rooted Sense 3.0 through Rom Manager -> a collection of *.img files.
I have tried to boot into fastboot, and executed these commands:
fastboot erase boot -> Error: remote not allowed
fastboot erase recovery -> Error: remote not allowed
fastboot flash system system.img -> OK
fastboot flash boot boot.img -> OK
fastboot flash userdata data.img -> OK
fastboot flash recovery recovery.img -> OK
but after this, the phone still does not boot normally.
Please tell me if I did something wrong or not. I dont know how to make update.zip from *.img files, and dont know where to get and choose the right stock rom for my phone.
Click to expand...
Click to collapse
No font flash the backup .imgs flash a whole update zip through the boot loader. Use a stock rom that contains a bunch of .imgs. reflashing the ones u already have won't help
Sent from my HTC Desire HD using xda premium
Are you on hboot 2.00.002? If yes, did you flash the boot.img from Endymion via fastboot??
Sent from my iPod touch using Tapatalk
I used htcdev to unlock, it's still S-ON and HBOOT 2.00.002.
I did not flash boot.img of Endymion. Can I do that with "fastboot flash..." ?
Does it matter if "fastboot erase boot" makes error? (as I posted above)
Could you give me instructions step-by-step what I need to do, thank you.
hi all,
i have some problem like a d_t_kien (i have htcdev unlock dev. and HBOOT 2.00.002, 4EXT Recovery).... so after flash ROM (i try Reaper V2.0 - CM7mod) device has freeze on white HTC screen....
Please help us... how correctly flash Endymion ROM via fastboost..
Thanks
For both of you, here's the procedure. First, flash the ROM normally. Then, enter fastboot mode and flash the boot.img that came in the ZIP of your ROM.
Reference - http://forum.xda-developers.com/showpost.php?p=19071114&postcount=37
thx for your answer, its my bad, because i dont use search button... so i finf solution in this thread: http://forum.xda-developers.com/showthread.php?t=1314629
thx again .)
shrome99 said:
For both of you, here's the procedure. First, flash the ROM normally. Then, enter fastboot mode and flash the boot.img that came in the ZIP of your ROM.
Reference - http://forum.xda-developers.com/showpost.php?p=19071114&postcount=37
Click to expand...
Click to collapse
Many thanks. That solved my problem.
Edmyrion works great now on my phone.
Glad i helped
Solved
Please marked this thread as solved. Thanks moderator.
d_t_kien said:
Please marked this thread as solved. Thanks moderator.
Click to expand...
Click to collapse
You'll have to do it yourself.... As OP, that's one of your privileges... Just go to the first post, select EDIT, then ADVANCED, and then you can edit the title of your thread and add "SOLVED" to the title.
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
I tried to boot into TWRP recovery from fastboot but the error comes up.
FAILED <remote:incomplete boot image>
any help? or should i try cwm the same way?
edit:cwm boots but does not show internal SD memory.
edit:can i do "fastboot oem relock"?
gamer.11 said:
I tried to boot into TWRP recovery from fastboot but the error comes up.
FAILED <remote:incomplete boot image>
any help? or should i try cwm the same way?
edit:cwm boots but does not show internal SD memory.
edit:can i do "fastboot oem relock"?
Click to expand...
Click to collapse
you need to flash the recovery again via fastboot
Code:
fastboot flash recovery recovery.img
maybe try redownloading the recovery.img as well
gamer.11 said:
I tried to boot into TWRP recovery from fastboot but the error comes up.
FAILED <remote:incomplete boot image>
any help? or should i try cwm the same way?
edit:cwm boots but does not show internal SD memory.
edit:can i do "fastboot oem relock"?
Click to expand...
Click to collapse
Reflash the recovery zip
You can use this app too http://goo.gl/Njm6Xm
Sent from my Nexus 5 using Tapatalk
Solved
Enddo said:
you need to flash the recovery again via fastboot
Code:
fastboot flash recovery recovery.img
maybe try redownloading the recovery.img as well
Click to expand...
Click to collapse
re downloading the recovery worked. Checked the md5 sum, previously did not match.
Mr hOaX said:
Reflash the recovery zip
You can use this app too http://goo.gl/Njm6Xm
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks but im trying to go back to stock so i need to just boot into it and not install it. thanks for the info
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?