Flash recovery FAILED (remote: no transfered data) - One (M7) Q&A, Help & Troubleshooting

Hello,
1. I think I may have bricked my phone, here's what I did. I was S-OFF, Super CID. Installed new M4 RUU, the only one I could find and then decided to install Stock_SixthSense-M4_5.11Base.
2. I had an error at the end of it 'unable to mount /system'.
3. Tried to start adb sideload to try a different ROM, couldn't start either.
4. Rebooted phone to booloader, tried to start recovery TWRP, screen flashing not starting.
5. Tried to reinstall recovery and this:
C:\adb>fastboot flash recovery twrp.img
< waiting for device >
sending 'recovery' (9432 KB)...
OKAY [ 1.188s]
writing 'recovery'...
FAILED (remote: no transfered data)
finished. total time: 1.219s
What is happening? Please help!

calbertuk said:
Hello,
1. I think I may have bricked my phone, here's what I did. I was S-OFF, Super CID. Installed new M4 RUU, the only one I could find and then decided to install Stock_SixthSense-M4_5.11Base.
2. I had an error at the end of it 'unable to mount /system'.
3. Tried to start adb sideload to try a different ROM, couldn't start either.
4. Rebooted phone to booloader, tried to start recovery TWRP, screen flashing not starting.
5. Tried to reinstall recovery and this:
C:\adb>fastboot flash recovery twrp.img
< waiting for device >
sending 'recovery' (9432 KB)...
OKAY [ 1.188s]
writing 'recovery'...
FAILED (remote: no transfered data)
finished. total time: 1.219s
What is happening? Please help!
Click to expand...
Click to collapse
Try to run the RUU again. If it is successful, then you are back to stock. There is a HTC One Mini forum which will have more expertise than this forum.

majmoz said:
Try to run the RUU again. If it is successful, then you are back to stock. There is a HTC One Mini forum which will have more expertise than this forum.
Click to expand...
Click to collapse
The RUU did install properly. It's an AT&T RUU though and there aren't any others which is a bit of an issue.
Still can't get a custom ROM to install with TRWP

calbertuk said:
The RUU did install properly. It's an AT&T RUU though and there aren't any others which is a bit of an issue.
Still can't get a custom ROM to install with TRWP
Click to expand...
Click to collapse
I don't know what you are trying to accomplish but here is a possibility: How to : Flash HTC One Mini with out S-OFF and no need RUU Stock ROM and [ROM][M4 - 4.09.401.3] Official Stock Sense 6 Rom v2 & Firmware

Related

N1 will not flash recovery

HELP ME! I cannot get this recovery image to flash for the life of me. here's the story. I have what was a ere27 build N1. 2 weeks ago I did the manual update to Google's prerelease of Froyo. Now my phone is a FRF50 build. As everyone else found out it's buggy as hell and GPS does not work. I searched for weeks to try and find a fix and I couldn't find anything other than to unlock the bootloader root the device and flash a different rom onto the phone. So I unlocked the BL from instructions here. Then in downloaded Pauls 1.0 FRF50 superboot. I tested the root with torch and it works, so the unlock and root must have worked. This is the first time I have ever used the cmd window and I have tried everything under the sun to get this thing to work so I can flash Pauls froyo and have working GPS again.
I followed the instructions found here, but I keep getting this error.
Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.
cd C:\fastboot
C:\fastboot>fastboot-windows devices
HT9C*******8 fastboot
C:\fastboot>fastboot-windows flash recovery C:\fastboot\recovery-RA-nexus-v1.6.2
sending 'recovery' (3954 KB)... FAILED (remote: not allowed)
have you done 'fastboot-windows oem unlock' ?
Yessir. Unlocked padlock on startup.
Try this:
fastboot devices
fastboot flash recovery recovery.img
C:\fastboot>fastboot flash recovery C:\fastboot\recovery-RA-nexus-v1.6.2
sending 'recovery' (3954 KB)... OKAY [ 0.641s]
writing 'recovery'... OKAY [ 1.563s]
finished. total time: 2.203s
so it worked once, then it went back to the stock recovery...
Hyper4mance2k said:
C:\fastboot>fastboot flash recovery C:\fastboot\recovery-RA-nexus-v1.6.2
sending 'recovery' (3954 KB)... OKAY [ 0.641s]
writing 'recovery'... OKAY [ 1.563s]
finished. total time: 2.203s
so it worked once, then it went back to the stock recovery...
Click to expand...
Click to collapse
I'm having the EXACT same problem.
Did you apply root before flashing recovery? Flash Paul's superboot, then install AmonRA recovery.
ATnTdude said:
Did you apply root before flashing recovery? Flash Paul's superboot, then install AmonRA recovery.
Click to expand...
Click to collapse
The OP says he is rooted. I am rooted as well. We both have had success in fastboot, but our recovery is defaulting to the standard android one, and not the custom one that we flash.
Hyper4mance2k said:
C:\fastboot>fastboot flash recovery C:\fastboot\recovery-RA-nexus-v1.6.2
sending 'recovery' (3954 KB)... OKAY [ 0.641s]
writing 'recovery'... OKAY [ 1.563s]
finished. total time: 2.203s
so it worked once, then it went back to the stock recovery...
Click to expand...
Click to collapse
All you need to do is
Fastboot flash recovery recovery-ra.img
Or whatever the image name needs to be.
I think I figured out the problem. I was running a rooted version of FRF72, and for whatever reason, no matter how I tried to flash the recovery, it would not stick. I could use clockwork's app to flash and reboot into the custom recovery, but if I rebooted again, it would always default to the stock android recovery.
I now have the custom recovery working for me at all times. Here is what I did (Keep in mind, I take no responsibility if you brick your phone into oblivion...):
First: Make sure that you have an unlocked bootloader, and are rooted. I used Paul's Superboot for the FRF50 build on my FRF72 build, and it worked flawlessly.
1. Find a custom ROM such as the MoDaCo MCR18 or 19 build if you want something close to the OTA builds.. or whichever one you'd like to flash. Make sure it is not a stock/rooted OTA build! I personally used Paul's MCR18 build over at MoDaCo.
2. Download it, and then rename the rom to update.zip and transfer to your SD card's main directory
3. Download the clockwork ROM Manager app from the android Market and run it.
4. Flash ClockworkMod Recovery from the app
5. Use the feature in the app to "Reboot into Recovery"
6. You should now be in the ClockworkMod recovery
7. Do a nandroid backup!! (that may reboot your phone normally.. if so, repeat steps 4 & 5 to reboot back into custom recovery)
8. If your rom requires you to wipe prior to install, then wipe cache partition from the main menu, and then go to advanced and wipe Dalvik cache prior to the next step. I did not have to wipe, so if this rebots your phone normally, repeat steps 4 &5 to get back into custom recovery.
9. Select the option to "apply sdcard:update.zip"
It will then flash the custom ROM onto your Nexus One
10. Once your phone has been rebooted, download the ClockworkMod Rom Manager from the market again (if it is not already on your phone), and re-flash the custom recovery. It should now always boot into the custom recovery.
Hope that helps!!

[Q] Bootloop troubles

I was trying to unlock and root my Vivid and seem to be stuck in a bootloop.
I used the All in one kit v 1.2 (Thanks Hansoon) unlocked my bootloader, and installed CWM.
The problem occurred when I tried to install the HoliCake kernel, after that step I couldn't boot into the base OS.
At the moment I can access hboot, fastboot and CWM.
When I try to boot, all that happens is the HTC logo is visible indefinitely.
Trying to install the stack kernel gives me the following output, and i'm not really sure where to go from here.
Code:
C:\Users\Rohit507\Desktop\Vivid_All-In-One_Kit_v1.2\data>adb push Kernels/Module
sStock/system /system
error: device not found
C:\Users\Rohit507\Desktop\Vivid_All-In-One_Kit_v1.2\data>adb reboot bootloader
error: device not found
C:\Users\Rohit507\Desktop\Vivid_All-In-One_Kit_v1.2\data>fastboot flash boot Ker
nels/Kernel-HereStock/boot.img
sending 'boot' (2838 KB)... OKAY [ 0.658s]
writing 'boot'... OKAY [ 1.578s]
finished. total time: 2.236s
C:\Users\Rohit507\Desktop\Vivid_All-In-One_Kit_v1.2\data>fastboot reboot
rebooting...
finished. total time: 1.879s
Thank you all, since this device is also my main phone, it would be appreciated if I could get it working again before the day is out, but even if that's not possible i'm gratefull for all your help.
I use the same tool. It is amazing.
Were I you, I'd download the stock ROM from the "Revert your phone to stock from ICS" thread in the dev section and start over just to be on the safe side.
Sent from my HTC PH39100 using xda premium
Okay, i'm back to stock, now to figure out how to actually mod this thing when adb doesn't seem to want to connect.

ICS upgrade - boot loop - can't fix - bricked?

I have searched the forums, and I can not find the answer to my specific situation. Please forgive me if it is there somewhere. The story…….
- last working ROM was VIVO ICS official, RUU installed. (RUU_VIVO_ICS_35_S_HTC_WWE_4.10.405.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266013_signed.exe). HBOOT was changed to 2.02 S-ON, bootloader locked. I unlocked via HTCdev. Before this I had IceColdSandwich 8.1.1, ENG Hboot S-OFF. I had originally used the GB downgrade ROM to S-OFF, and restored IceCold backup after this.
- I wanted to be S-OFF again, and so tried installing this zip using CWM Recovery, following the advice of tpbklake:
vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip Version 1.1
(from http://forum.xda-developers.com/showthread.php?t=1756500&page=1)​
- now boot loop. I tried reinstalling other ROMs which I have successfully installed in the past (GB downgrade, stock ICS), and also restore various backups, but all result in boot loop (stuck on white HTC screen). Each time I would use CWM Recovery to clear dalvik, cache etc.
- I have now followed 'fix' instructions in that same thread, ie. :
1. Download the file lib.zip from here: http://bit.ly/PwK4BH
2. Unzip the lib.img and place it on your PC where you have fastboot.exe installed.
3. Boot into FASTBOOT USB mode and then enter the following command:
fastboot flash lib lib.img
4. Download the file format_lib_update.zip from here: http://bit.ly/RIpEUL
5. Copy it to your SD card.
6. Boot into recovery and then install format_lib_update.zip
7. While in recovery format the SYSTEM partition.
8. Then reinstall vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip​
But at step 3 I get the following:
C:\adb>fastboot flash lib lib.img
sending 'lib' (155648 KB)...
OKAY [ 27.553s]
writing 'lib'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 52.417s
C:\adb>​
Please help! I’m close to considering myself properly bricked, and using that as an excuse to go and buy a OneX.
jcr67 said:
I have searched the forums, and I can not find the answer to my specific situation. Please forgive me if it is there somewhere. The story…….
- last working ROM was VIVO ICS official, RUU installed. (RUU_VIVO_ICS_35_S_HTC_WWE_4.10.405.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266013_signed.exe). HBOOT was changed to 2.02 S-ON, bootloader locked. I unlocked via HTCdev. Before this I had IceColdSandwich 8.1.1, ENG Hboot S-OFF. I had originally used the GB downgrade ROM to S-OFF, and restored IceCold backup after this.
- I wanted to be S-OFF again, and so tried installing this zip using CWM Recovery, following the advice of tpbklake:
vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip Version 1.1
(from http://forum.xda-developers.com/showthread.php?t=1756500&page=1)​
- now boot loop. I tried reinstalling other ROMs which I have successfully installed in the past (GB downgrade, stock ICS), and also restore various backups, but all result in boot loop (stuck on white HTC screen). Each time I would use CWM Recovery to clear dalvik, cache etc.
- I have now followed 'fix' instructions in that same thread, ie. :
1. Download the file lib.zip from here: http://bit.ly/PwK4BH
2. Unzip the lib.img and place it on your PC where you have fastboot.exe installed.
3. Boot into FASTBOOT USB mode and then enter the following command:
fastboot flash lib lib.img
4. Download the file format_lib_update.zip from here: http://bit.ly/RIpEUL
5. Copy it to your SD card.
6. Boot into recovery and then install format_lib_update.zip
7. While in recovery format the SYSTEM partition.
8. Then reinstall vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip​
But at step 3 I get the following:
C:\adb>fastboot flash lib lib.img
sending 'lib' (155648 KB)...
OKAY [ 27.553s]
writing 'lib'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 52.417s
C:\adb>​
Please help! I’m close to considering myself properly bricked, and using that as an excuse to go and buy a OneX.
Click to expand...
Click to collapse
OK, so what is the state of your HBOOT? Are you still HBOOT 2.02.0002 UNLOCKED?
When you are using the an unlocked HTC HBOOT and you flash a custom ROM in CWM, you then manually have to extract the boot.img file from that ROM's zip file and flash it manually in FASTBOOT USB mode. If you don't do that, you will get a boot loop.
What you need to do if you can still get into CWM and the bootloader is still UNLOCKED is reflash that ROM again and then flash the boot.img file in FASTBOOT mode and you should be ok.
tpbklake said:
OK, so what is the state of your HBOOT? Are you still HBOOT 2.02.0002 UNLOCKED? .
Click to expand...
Click to collapse
yep
tpbklake said:
When you are using the an unlocked HTC HBOOT and you flash a custom ROM in CWM, you then manually have to extract the boot.img file from that ROM's zip file and flash it manually in FASTBOOT USB mode. If you don't do that, you will get a boot loop.
What you need to do if you can still get into CWM and the bootloader is still UNLOCKED is reflash that ROM again and then flash the boot.img file in FASTBOOT mode and you should be ok.
Click to expand...
Click to collapse
I should have mentioned, I already tried that. However, I will try it one more time. I tried so many things - if I try it again in isolation, I will be 100% sure I am telling you the truth.
Thanks for the reply.
jcr67 said:
I should have mentioned, I already tried that. However, I will try it one more time. I tried so many things - if I try it again in isolation, I will be 100% sure I am telling you the truth.
Thanks for the reply.
Click to expand...
Click to collapse
OK, I tried it again.
- In CWM Recovery, install from zip, chose 'vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip'
- It completed successfuly (rather quickly)
- extracted boot.img from that zip, places in adb/fastboot folder on PC
- Rebooted phone into bootloader USB
- On PC, executed 'fastboot boot boot.img'
C:\adb>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.328s]
booting...
OKAY [ 0.000s]
finished. total time: 1.328s​
- it rebooted automatically, and now stuck on white HTC screen for last 10 minutes
jcr67 said:
OK, I tried it again.
- In CWM Recovery, install from zip, chose 'vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip'
- It completed successfuly (rather quickly)
- extracted boot.img from that zip, places in adb/fastboot folder on PC
- Rebooted phone into bootloader USB
- On PC, executed 'fastboot boot boot.img'
C:\adb>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.328s]
booting...
OKAY [ 0.000s]
finished. total time: 1.328s​
- it rebooted automatically, and now stuck on white HTC screen for last 10 minutes
Click to expand...
Click to collapse
Instead of "fastboot boot boot.img"
it should be
"fastboot flash boot boot.img"
Try that and see how it goes
Cheers
Drugzy said:
Instead of "fastboot boot boot.img"
it should be
"fastboot flash boot boot.img"
Try that and see how it goes
Cheers
Click to expand...
Click to collapse
Aaaarghh....silly me
However, same result. Still white screen after 10min
C:\adb>fastboot flash boot boot.img
sending 'boot' (3824 KB)...
OKAY [ 1.187s]
writing 'boot'...
OKAY [ 1.234s]
finished. total time: 2.422s​
jcr67 said:
Aaaarghh....silly me
However, same result. Still white screen after 10min
C:\adb>fastboot flash boot boot.img
sending 'boot' (3824 KB)...
OKAY [ 1.187s]
writing 'boot'...
OKAY [ 1.234s]
finished. total time: 2.422s​
Click to expand...
Click to collapse
Well then you can always relock the bootloader and then run the 4.10.405.1 RUU like you did originally. Then you can unlock the bootloader since you already have the unlock_code.bin file.
tpbklake said:
Well then you can always relock the bootloader and then run the 4.10.405.1 RUU like you did originally. Then you can unlock the bootloader since you already have the unlock_code.bin file.
Click to expand...
Click to collapse
Then I will end up where I was in the first place? Oh well, at least I could use the phone.
Anyhow......
C:\adb>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.312s​
HBOOT now says:
*** RELOCKED ***
*** Security Warning ***
jcr67 said:
Then I will end up where I was in the first place? Oh well, at least I could use the phone.
Anyhow......
C:\adb>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.312s​
Click to expand...
Click to collapse
Once you get back to that point, unlock the bootloader, install ClockworkMod and then flash su-3.0.7-efghi.zip to root the official ROM. Then you should be able to rerun the downgrade process to get back to S-OFF.
Reinstall the HTC ruu
Sent from my HTC Raider X710e using xda app-developers app
tpbklake said:
Once you get back to that point, unlock the bootloader, install ClockworkMod and then flash su-3.0.7-efghi.zip to root the official ROM. Then you should be able to rerun the downgrade process to get back to S-OFF.
Click to expand...
Click to collapse
But my relock resulted in a security warning, as shown above. Are you telling me that's fine, and I can go ahead with RUU? Thanks
jcr67 said:
But my relock resulted in a security warning, as shown above. Are you telling me that's fine, and I can go ahead with RUU? Thanks
Click to expand...
Click to collapse
Yes you should be ok.
tpbklake said:
Yes you should be ok.
Click to expand...
Click to collapse
yep he will be , during my downgrade i had to relock with security warning and ruu fixed it all
tpbklake said:
Yes you should be ok.
Click to expand...
Click to collapse
Thanks very much. The stock ICS RUU has now installed successfully. I guess when I originally tried to reinstall it, I had left out the 'RELOCK' step, which is why it failed.
So now I am back to the start (stock ICS + HBOOT 2.02 S-ON), and want to get S-OFF and install your ROM zip. ,What I originally intended to do to get S-OFF was:
1) Unlock the bootloader, flash CWM Recovery, flash SU
2) Run downgrade GB RUU
3) S-off with Revolutionary
4) Install Blackrose HBOOT
5) Install your vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip
But step 2) failed with an unknown error. (I then tried to install your zip, and the rest is the sad history.....).
So what caused step 2 to fail? Did I need to relock the bootloader first?
Many thanks for your help, tpbklake
Did you use this script to downgrade and then flash gb ruu?
http://forum.xda-developers.com/showthread.php?t=1373697
If so run it and post up the results. It may not.be downgrading your mainver correctly.
Sent from my HTC Incredible S using xda app-developers app
Drugzy said:
Did you use this script to downgrade and then flash gb ruu?
http://forum.xda-developers.com/showthread.php?t=1373697
If so run it and post up the results. It may not.be downgrading your mainver correctly. p
Click to expand...
Click to collapse
That's it. HBOOT is remaining at 2.02.0002 after runme.cmd
Is the device rooted?
y OR n:y
Waiting for device to connect
Device found
Pushing misc_version
2455 KB/s (367096 bytes in 0.146s)
Correcting permissions
Downgrading main version
--set_version set. VERSION will be changed to: 2.00.000.0
Patching and backing up misc partition...
Error opening input file.
Cleaning temp files​
Any ideas anyone?
What is the status of your bootloader? Is it locked, unlocked or relocked? If it is locked you may have to answer n to is the phone rooted to give temp root. If not on page 76 of this post there is the same issue.
http://forum.xda-developers.com/showthread.php?t=1373697
And fyi it will not change the h boot version, only the main ver which is reported at the end of the script.
Cheers
Sent from my HTC Incredible S using xda app-developers app
Drugzy said:
What is the status of your bootloader? Is it locked, unlocked or relocked? If it is locked you may have to answer n to is the phone rooted to give temp root. If not on page 76 of this post there is the same issue.
http://forum.xda-developers.com/showthread.php?t=1373697
And fyi it will not change the h boot version, only the main ver which is reported at the end of the script.
Cheers
Click to expand...
Click to collapse
No, I'm unlocked and rooted
Does the stock ruu have superuser installed? If it does I'm outta ideas.
Sent from my HTC Incredible S using xda app-developers app
---------- Post added at 07:58 PM ---------- Previous post was at 07:40 PM ----------
One more thing, I would try flashing another ROM, i came from Niks Sense 4a rom, and the script worked with no issues.
Remember you will need to manually flash the boot.img of the rom as you are S-ON.
jcr67 said:
No, I'm unlocked and rooted
Click to expand...
Click to collapse
Open a command window and then type in the command:
adb shell
If you get a # prompt then your ROM is rooted correctly and the script should run. If it doesn't then the ROM isn't properly rooted and the script will fail.

Help htc butterfly s , iam an expert in android but i failed :(

hii ...
i have HTC butterfly s phone is boot looping ,,,
issue :
when entering OS i can see the lock screen for 3 seconds then reboot.
solutions tried :
1- tried to wipe from TWRP recovery when it reaches /data >>> reboot.
2- tried to install another ROM without wiping >>>> reboot
3- tried to install CWM recovery , it says completed in fastboot (CMD) but recovery is not changing.
4- tried to lock the boot loader again , it says no such file or directory .
5- tried to boot in safemode but i see the lock screen for 3 seconds then reboot
iam stuck ... please help
thank you
hello
it happened to me the same, I just download it stock rom that is here, you have to see the version of your phone to know which is for yours.
greetings and good luck
all credits to the creator of the post
http://forum.xda-developers.com/showthread.php?t=2663295
GAVANA said:
hello
it happened to me the same, I just download it stock rom that is here, you have to see the version of your phone to know which is for yours.
greetings and good luck
all credits to the creator of the post
http://forum.xda-developers.com/showthread.php?t=2663295
Click to expand...
Click to collapse
hi .. thanks for reply ,,,
i downloaded stock rom 2.21 and tried to flash it from recovery when it tries to install the rom when it reaches to writing /data phone reboots
you mean something else ?
thanks ...
i want to add one thing ,,,
i have TWRP recovery 2.6.0.0 and i want to change it to CWM , i try to install from fastboot and it says successful but when i go into recovery its not changed !!!!!!
recovery recovery.img
sending 'recovery' (12364 KB)... OKAY [ 1.794s]
writing 'recovery'... OKAY [ 0.983s]
finished. total time: 2.777s
hwoarang626 said:
i want to add one thing ,,,
hello
at first I was the same with the recovery, but install this and it worked well, and use that version of android stock for now
but if you want to upgrade later (OTAS), you would have to have stock recovery and unroot your device, saludos
http://forum.xda-developers.com/showthread.php?t=2730482 .
i have TWRP recovery 2.6.0.0 and i want to change it to CWM , i try to install from fastboot and it says successful but when i go into recovery its not changed !!!!!!
recovery recovery.img
sending 'recovery' (12364 KB)... OKAY [ 1.794s]
writing 'recovery'... OKAY [ 0.983s]
finished. total time: 2.777s
Click to expand...
Click to collapse
hello
at first I was the same with the recovery, but install this and it worked well, and use that version of android stock for now
but if you want to upgrade later (OTAS), you would have to have stock recovery and unroot your device
regards
http://forum.xda-developers.com/showthread.php?t=2730482
its the same ,,, i tried to install the recovery you gave me but it did not install the recovery , Iam still stuck with a recovery that is not doing anything .
thanks
one more point ,,, i noticed that my /system is empty ...
hwoarang626 said:
one more point ,,, i noticed that my /system is empty ...
Click to expand...
Click to collapse
Since no one else is really helping you I will.
So what I gathered is your Rom bootloops and you've tried installing stock Rom but still no luck so you want to switch recoveries but you can't get twrp to flash...?
1. Are you S-Off or S-On? If you are s-on you must flash boot.img with this command
Code:
fastboot flash boot boot.img
2. To flash a recovery made for your device you must place it in fastboot and enter this
Code:
fastboot flash recovery recovery.img
3. Place Rom on internel storage if you choose cwm because it doesn't support external sdcard like twrp. For latest twrp, message @kairi_zeroblade... If you can't place on internal with cwm then you must do a sideload with the Rom same goes for twrp.
Want to support InsertCoin? Just get our donate key
xXminiWHOOPERxX said:
Since no one else is really helping you I will.
So what I gathered is your Rom bootloops and you've tried installing stock Rom but still no luck so you want to switch recoveries but you can't get twrp to flash...?
1. Are you S-Off or S-On? If you are s-on you must flash boot.img with this command
Code:
fastboot flash boot boot.img
2. To flash a recovery made for your device you must place it in fastboot and enter this
Code:
fastboot flash recovery recovery.img
3. Place Rom on internel storage if you choose cwm because it doesn't support external sdcard like twrp. For latest twrp, message @kairi_zeroblade... If you can't place on internal with cwm then you must do a sideload with the Rom same goes for twrp.
Want to support InsertCoin? Just get our donate key
Click to expand...
Click to collapse
thank you for your help ,,,
im S-ON
fastboot flash boot boot
.img
< waiting for device >
sending 'boot' (6104 KB)...
OKAY [ 0.830s]
writing 'boot'...
OKAY [ 0.590s]
finished. total time: 1.420s.
fastboot flash recovery
cwm6.0.4.5.img
sending 'recovery' (12364 KB)...
OKAY [ 1.430s]
writing 'recovery'...
OKAY [ 0.990s]
finished. total time: 2.420s
i did what you said but nothing changed im still on TWRP recovery 2.6.0.0 and my room is boot looping
hwoarang626 said:
thank you for your help ,,,
im S-ON
fastboot flash boot boot
.img
< waiting for device >
sending 'boot' (6104 KB)...
OKAY [ 0.830s]
writing 'boot'...
OKAY [ 0.590s]
finished. total time: 1.420s.
fastboot flash recovery
cwm6.0.4.5.img
sending 'recovery' (12364 KB)...
OKAY [ 1.430s]
writing 'recovery'...
OKAY [ 0.990s]
finished. total time: 2.420s
i did what you said but nothing changed im still on TWRP recovery 2.6.0.0 and my room is boot looping
Click to expand...
Click to collapse
Not sure if you can enter this command without a-off but try
Code:
fastboot erase cache
Then repeat the previous post....
If that doesn't work I'd try firewaters universal s-off tool and obtain s-off and try that command or see if it fixes your issues with your device. if that fails your best bet would be to ruu.. if you can't do that either you got a useless device till s-off exploit Is found if that's the reason why it's messing up.... Or donate it to someone who could fix it (me)
Want to support InsertCoin? Just get our donate key
xXminiWHOOPERxX said:
Not sure if you can enter this command without a-off but try
Code:
fastboot erase cache
Then repeat the previous post....
If that doesn't work I'd try firewaters universal s-off tool and obtain s-off and try that command or see if it fixes your issues with your device. if that fails your best bet would be to ruu.. if you can't do that either you got a useless device till s-off exploit Is found if that's the reason why it's messing up.... Or donate it to someone who could fix it (me)
Want to support InsertCoin? Just get our donate key
Click to expand...
Click to collapse
i tried this and no luck ,,,
actually i tried every thing but the problem is that the data does not change in the phone ,, i even formated (real format fsck) to /data and it was showing its empty but after reboot everything went back ,,, iam fixing android phones since htc desire but never faced anything like this ,,,
thank you for your help ,, and what you mean by donate and get it fixed ?
hwoarang626 said:
i tried this and no luck ,,,
actually i tried every thing but the problem is that the data does not change in the phone ,, i even formated (real format fsck) to /data and it was showing its empty but after reboot everything went back ,,, iam fixing android phones since htc desire but never faced anything like this ,,,
thank you for your help ,, and what you mean by donate and get it fixed ?
Click to expand...
Click to collapse
Seem like you fried your "/data" partition from what you just mentioned above. The only way I could see you fix is ruu. Cause HTC won't fix it if you send it in with a custom recovery at which you can't change.
And what I meant is since the device is rendered completely useless, unless you can get a run to ruu. You'd donate it to me this way i could try and fix it...
Sent from my HTC0P4E1 using Tapatalk
xXminiWHOOPERxX said:
Seem like you fried your "/data" partition from what you just mentioned above. The only way I could see you fix is ruu. Cause HTC won't fix it if you send it in with a custom recovery at which you can't change.
And what I meant is since the device is rendered completely useless, unless you can get a run to ruu. You'd donate it to me this way i could try and fix it...
Sent from my HTC0P4E1 using Tapatalk
Click to expand...
Click to collapse
i think im facing the same problem here, do u know where we can find the RUU, I searched the whole internet and i could not find, im ready to donate if u fix my problem and provide me with the RUU.
Regards
mr_wehbe said:
i think im facing the same problem here, do u know where we can find the RUU, I searched the whole internet and i could not find, im ready to donate if u fix my problem and provide me with the RUU.
Regards
Click to expand...
Click to collapse
There is no RUU for this phone, as far as I know. The closest thing to RUU is flashing everything by hand, but this seems to have failed in this case, unfortunately.

[Q] HELP - Bricked HTC One m7 (m7ul)

Hi,
I am after some help trying to get my HTC One back up and running.
I unlocked the bootloader using the htcdev website and installed cyanogen mod.
This was working fine for quite some time, until I recently wanted to download an app that was only available on stock phones.
I tried editing the /system/build.prop file to change the version to fool the app store but that didn't work.
Then when I restored my backup build.prop, I think I got the permissions wrong or something and the phone rebooted and went into a boot loop.
Then I followed a guide to get twrp on the device which worked.
Then I followed another guide attempting the restore the device to stock using the commands
Code:
fastboot oem lock
and
Code:
fastboot oem rebootRUU
.
Now the phone is stuck in a boot loop. All I can do is hold down power and volume down to get to HBOOT and Fastboot. If I try and load recovery it reboots to the same menu.
What else can I try, or do I now have a new paperweight?
Thanks for any suggestions.
- gatamous
Also,
I have tried flashing the stock recovery but I get signature errors.
Code:
C:\Android\android-sdk-windows-r24.0.2\platform-tools>fastboot flash recovery recovery_2.24.980.2.img
target reported max download size of 1443966976 bytes
sending 'recovery' (8752 KB)...
OKAY [ 1.140s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.846s
OK,
Never mind.
I was unable to unlock my bootloader because I was typing fastboot flash unlock token Unlock_code.bin instead of unlocktoken being one word.
One I fixed that the twrp recovery started again.
Once I opened that the phone apeared on my PC as a storage device.
I copied a cyanogen mode zip to that directory then installed it via twrp.
Now I have cyanogenmod working again.
Yay - no longer a brick.
I guess I am out of luck with reverting it to stock if the RUU I need is not available for my carrier - is that right?
If so I'll stay on cyanogen mod and not worry about reverting to stock.
Next time I guess I'll take one of these nandroid backups while the phone is still stock. Hindsight.
- gatamous

Categories

Resources