Related
I have a problem to install a ROM or turn on my htc one, when I'm in the recoveryMod I go to install from sdcard but I'm Still an error that says "E: can not mount / sdcard /" the problem is start when I try to install the ROm (Android Revolution HD 7.2) I was on the ROM (Maximus7_5.0.0)
it is possible to fix this problem?
it is possible to return to the original ROM?
I'm really deseprer two days I'm looking for a soulition but I find nothing
thank you
help please
help please
Hi
Greetings,
1. Flash the recovery again and try again
2. You can use abd sideload
For abd sideload you need latest abd drivers.
And search for abd sideload and how to use as iam not an one user and dnt know much about sideload but it will help you install Rom directly from pc
Sent from my HTC Sensation Z710e using xda premium
to flash the recovery type
Code:
fastboot flash recovery recovery_name.img
Code:
fastboot erase cache
and then try again
and yes you can return to stock, just decide what you want to do
I already tried to do but it does not work, still the same error
yes I'd like to return to the original version, coment I do?
mehdi2006 said:
I already tried to do but it does not work, still the same error
yes I'd like to return to the original version, coment I do?
Click to expand...
Click to collapse
well in that case the best option is to flash a RUU easy
run this command and paste your output
Code:
fastboot getvar all
matt95 said:
well in that case the best option is to flash a RUU easy
run this command and paste your output
Code:
fastboot getvar all
Click to expand...
Click to collapse
how can I do?
Reboot into bootloader/fastboot with phone connected to pc
It must say fastboot usb
and in abd command
Type the given code your done
Just select that and copy paste here
Sent from my HTC Sensation Z710e using xda premium
shrex said:
Reboot into bootloader/fastboot with phone connected to pc
It must say fastboot usb
and in abd command
Type the given code your done
Just select that and copy paste here
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
i have this error
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.054s
Hi
Greetings,
Are you typing it correctly ?
Is your device connected properly to pc and can abd find your device?
Sent from my HTC Sensation Z710e using xda premium
mehdi2006 said:
i have this error
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.054s
Click to expand...
Click to collapse
yeah, as i thought... is your bootloader unlocked right?
shrex said:
Hi
Greetings,
Are you typing it correctly ?
Is your device connected properly to pc and can abd find your device?
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
yes i try it 2-3 times always the same error
ok that's not a problem, we only need the version-main to see which RUU you have to run... type
Code:
fastboot getvar version-main
matt95 said:
yeah, as i thought... is your bootloader unlocked right?
Click to expand...
Click to collapse
yes its unlocked
try the command above
matt95 said:
ok that's not a problem, we only need the version-main to see which RUU you have to run... type
Code:
fastboot getvar
Click to expand...
Click to collapse
version-main 1.29.206.11
i checked but there is no RUU for that version yet, you have to flash a Nandroid backup to turn back to stock...
matt95 said:
i checked but there is no RUU for that version yet, you have to flash a Nandroid backup to turn back to stock...
Click to expand...
Click to collapse
how I should flash?
type
Code:
fastboot getvar cid
matt95 said:
type
Code:
fastboot getvar cid
Click to expand...
Click to collapse
but i dont have any backup :s
I know, two very bad mistakes. I was excited. First thing I did wrong was install a GE kernel when I should have installed a sense one..then I used fast boot to write TWRP to my boot image by accident instead of recovery. I tried to update RUU using fastboot, but I keep getting errors. I cant mount my internal storage, can't side load either.
Whenever I reboot, I boot into TWRP instead of system now. I probably have to restore, but not being able to RUU or side load, I dont know what to do. Please help!
j2sun said:
I know, two very bad mistakes. I was excited. First thing I did wrong was install a GE kernel when I should have installed a sense one..then I used fast boot to write TWRP to my boot image by accident instead of recovery. I tried to update RUU using fastboot, but I keep getting errors. I cant mount my internal storage, can't side load either.
Whenever I reboot, I boot into TWRP instead of system now. I probably have to restore, but not being able to RUU or side load, I dont know what to do. Please help!
Click to expand...
Click to collapse
Just boot into fastboot and flash a new boot.img which matches your ROM
Thanks! But where do I get a boot.img file? I tried looking but couldn't find one. I could just find ZIP ROMs and RUUs
j2sun said:
Thanks! But where do I get a boot.img file? I tried looking but couldn't find one. I could just find ZIP ROMs and RUUs
Click to expand...
Click to collapse
Go here http://forum.xda-developers.com/showthread.php?t=2316726
Choose the 2.24 firmware file, this one which includes the kernel
https://mega.co.nz/#!iVJEWLBD!T3fwwlKNRTq_f1ls50jicDMQ5ysOG_Y6iMhO78zwrSA
Extract boot.img, flash it, then reflash TWRP correctly also
EddyOS said:
Just boot into fastboot and flash a new boot.img which matches your ROM
Click to expand...
Click to collapse
dgtiii said:
Go here http://forum.xda-developers.com/showthread.php?t=2316726
Choose the 2.24 firmware file, this one which includes the kernel
https://mega.co.nz/#!iVJEWLBD!T3fwwlKNRTq_f1ls50jicDMQ5ysOG_Y6iMhO78zwrSA
Extract boot.img, flash it, then reflash TWRP correctly also
Click to expand...
Click to collapse
Thanks a lot!
Is this the boot.img that I should flash:
hboot_signedbyaa.img
Also, after that, should I RUU?
Thanks!
j2sun said:
Thanks a lot!
Is this the boot.img that I should flash:
hboot_signedbyaa.img
Also, after that, should I RUU?
Thanks!
Click to expand...
Click to collapse
Yes. You also should flash stock recovery before you flash the RUU, just to make sure everything goes right.
kibmikey1 said:
Yes. You also should flash stock recovery before you flash the RUU, just to make sure everything goes right.
Click to expand...
Click to collapse
The RUU flashes the stock recovery so you don't need this. You don't even need the boot.img if you're going to flash an RUU. Just connect the phone in fastboot mode and then run the RUU. So long as you're S-OFF it should run fine
Your phone doesn't need a kernel to boot to recovery or fastboot, recovery has its own kernel built in... Just goto fastboot and flash a new boot.img
Fastboot flash boot boot.img
Hboot_signedbyaa.img isn't a boot.img it's a hboot
Sent from my One using xda app-developers app
how did a do that?
EddyOS said:
The RUU flashes the stock recovery so you don't need this. You don't even need the boot.img if you're going to flash an RUU. Just connect the phone in fastboot mode and then run the RUU. So long as you're S-OFF it should run fine
Click to expand...
Click to collapse
Hi mate, in your signature I red OS 2.24.4018 / HBoot 1.54.0000 and now "tadaaaa" S-OFF and so on.
How did you do that? I've damaged my brain and gnawn down my nails but nothing works ....
Have you installed the 1.54.0000 on top of the 1.44.0000 (unlocked + S-OFF) and your HBOOT is still unlocked and S-OFF?
Or are u using the black&beauty ONE?
Then ou are a lucky man I guess.
God bless you.
I was S-OFF on 1.44 and then did the OTA so I kept S-OFF - sorry to get your hopes up!
EddyOS said:
I was S-OFF on 1.44 and then did the OTA so I kept S-OFF - sorry to get your hopes up!
Click to expand...
Click to collapse
EddyOS said:
The RUU flashes the stock recovery so you don't need this. You don't even need the boot.img if you're going to flash an RUU. Just connect the phone in fastboot mode and then run the RUU. So long as you're S-OFF it should run fine
Click to expand...
Click to collapse
Uhm...I don't have S-OFF. I tried pushing it in recovery , but when I do ./revone -P but I'm stuck with error code = 1
j2sun said:
Uhm...I don't have S-OFF. I tried pushing it in recovery , but when I do ./revone -P but I'm stuck with error code = 1
Click to expand...
Click to collapse
I know, I was replying to another post in this thread...
EddyOS said:
I was S-OFF on 1.44 and then did the OTA so I kept S-OFF - sorry to get your hopes up!
Click to expand...
Click to collapse
Oh yeah, I got it. I decided to buy a new ONE and wait for the exploid to fix my device. Then I'll give it to my wife. I know she will be happy about this....
Sent from my HTC Sensation XE with Beats Audio using XDA Premium 4 mobile app
Hi There,
I searched the threads available to the best of my ability, but im not sure exactly what im looking for. Purchased an HTC one used, flashed with cyanogenmod 10.2. When I tried to update it to 11, it soft bricked (im assuming) as it cant get past the recovery mode. I factory wiped it, in my ignorance thinking this would be able to fix the issue, boot up the stock rom. This cleared the OS so I was more stuck then I previously was.
I figured out how to push roms onto it, and I got the new android revolution rom on there, and when i install it, it says its successful as it goes through all the rom specific steps, but when it system reboots it goes back into this loop.
Are there any suggestions to get out of this? Should i somehow flash the latest RUU?
Thanks a lot I appreciate any help
bronsonb said:
Hi There,
I searched the threads available to the best of my ability, but im not sure exactly what im looking for. Purchased an HTC one used, flashed with cyanogenmod 10.2. When I tried to update it to 11, it soft bricked (im assuming) as it cant get past the recovery mode. I factory wiped it, in my ignorance thinking this would be able to fix the issue, boot up the stock rom. This cleared the OS so I was more stuck then I previously was.
I figured out how to push roms onto it, and I got the new android revolution rom on there, and when i install it, it says its successful as it goes through all the rom specific steps, but when it system reboots it goes back into this loop.
Are there any suggestions to get out of this? Should i somehow flash the latest RUU?
Thanks a lot I appreciate any help
Click to expand...
Click to collapse
what recovery are you using? what version?
also post a fastboot getvar all wihout imei/sn
alray said:
what recovery are you using? what version?
also post a fastboot getvar all wihout imei/sn
Click to expand...
Click to collapse
Im using TWRP 2.5.0.0, and im trying to run the fastboot getvar but its stuck on <waiting for device> ill post an update if that changes, thank you for your response!
bronsonb said:
Im using TWRP 2.5.0.0, and im trying to run the fastboot getvar but its stuck on <waiting for device> ill post an update if that changes, thank you for your response!
Click to expand...
Click to collapse
You must use latest twrp version to flash arhd rom! 2.5.0.0 is very outdated.
Are you using a windows 8.1 computer? If yes then you miht have issue with fastboot.
and make sur your phone variant is M7_U or M7_UL in bootloader screen. (not a sprint version M7wls)
What is the hboot version in bootloader screen?
from the OP of arhd thread:
Android Revolution HD 51.0
--- MD5 Checksum: 1F9253A64D5B0A0566C8B40EC809D05F ---
You need TRWP 2.6.3.3 recovery!
Flashing KitKat F.A.Q. - click here
Click to expand...
Click to collapse
alray said:
You must use latest twrp version to flash arhd rom! 2.5.0.0 is very outdated.
Are you using a windows 8.1 computer? If yes then you miht have issue with fastboot.
and make sur your phone variant is M7_U or M7_UL in bootloader screen. (not a sprint version M7wls)
What is the hboot version in bootloader screen?
Click to expand...
Click to collapse
I had no idea, Ill figure out how to do that right away I really appreciate that.
Im using a mac actually, so i understand everything isnt really made to work with it, though i can use parallels windows 7 if necessary
it shows:
TAMPERED
UNLOCKED
M7_UL PVT SHIP S-ON RH
HBOOT - 1.44.0000
bronsonb said:
I had no idea, Ill figure out how to do that right away I really appreciate that.
Im using a mac actually, so i understand everything isnt really made to work with it, though i can use parallels windows 7 if necessary
it shows:
TAMPERED
UNLOCKED
M7_UL PVT SHIP S-ON RH
HBOOT - 1.44.0000
Click to expand...
Click to collapse
ok so flash twrp 2.6.3.3 and reflash your rom.
Code:
./fastboot flash recovery <name_of_file>.img
./fastboot erase cache
./fastboot reboot-bootloader
then flash arhd again.
alray said:
ok so flash twrp 2.6.3.3 and reflash your rom.
Code:
./fastboot flash recovery <name_of_file>.img
./fastboot erase cache
./fastboot reboot-bootloader
then flash arhd again.
Click to expand...
Click to collapse
is there a line of code to flash the rom through fastboot, rather then rebooting recovery and installing it?
bronsonb said:
is there a line of code to flash the rom through fastboot, rather then rebooting recovery and installing it?
Click to expand...
Click to collapse
No, you'll need a custom recovery to flash a rom.
or
Use a ruu to restore back to 100% stock but you will need to post a ''fastboot getvar all'' to determine if this is possible.
What is going wrong?
You can also post screenshots of you terminal window when you get errors.
alray said:
No, you'll need a custom recovery to flash a rom.
or
Use a ruu to restore back to 100% stock but you will need to post a ''fastboot getvar all'' to determine if this is possible.
What is going wrong?
You can also post screenshots of you terminal window when you get errors.
Click to expand...
Click to collapse
Actually, I just installed it through the newly flashed recovery and it worked perfectly (Android Revolution)
Thank you so much! Saved me a lot of time
bronsonb said:
Actually, I just installed it through the newly flashed recovery and it worked perfectly (Android Revolution)
Thank you so much! Saved me a lot of time
Click to expand...
Click to collapse
np
First of all I would like to apologize if I posted this in the wrong forum or section. I just registered this account to ask for help regarding my bricked HTC One (m7ul). I am not a newbie to XDA as I have visited this site more than once to learn the fundamentals of rooting android phone and so on. I unlocked my bootloader via HTCDev and rooted it using CWM Touch Recovery 6.0.4.5. 3 weeks ago I flashed my HTC One to Probam (AOSB) custom rom, no problems were present, everything ran smoothly and perfectly. Then, 2 weeks ago, I decided to flash ElementalX kernel, being ignorant on purpose to the fact that it was meant for Sense Roms. Upom completion through Aroma Installer, I selected reboot system in recovery. Upon exit, the recovery told me that my phone could have possibly lost its root access and prompted me to root it so i just agreed. There came the problem upon reboot, I could not boot into my OS and I was stuck on the HTC screen. (May I add that I bought my HTC this year March. I S-offed it via Firewater as my Hboot version was 1.56 and Rumrunner couldn't help me S-Off. Advice for those who have hboot versions higher than 1.55 and want to S-off, Firewater is my suggestion. Just make sure you follow the guid also here on XDA forums accurately and I assure you can get s-off) As I was saying, as soon as that happened, I looked for solutions. I tried hasson 2000 all in one toolkit, I tried relocking my bootloader and runming RUU.exe file to return to stock firmware, I tried sideloading a rom in recovery, I tried mounting usb storage to copy a .zip rom into my internal storage but nothing happened. I tried flashing directly via fastboot but the cmd keep saying it couldnt run the file. I couldn't enter adb as the recovery said there is no os present. I really have no more idea what else I can do and I think I've tried just about everything. Please help as it's been 2 weeks into the brick and I'm really desperate. Please help
CID: HTC_044
Hboot:1.56
If there is more information needed please ask as I'm really desperate to fix my phone :C
boksquare said:
First of all I would like to apologize if I posted this in the wrong forum or section. I just registered this account to ask for help regarding my bricked HTC One (m7ul). I am not a newbie to XDA as I have visited this site more than once to learn the fundamentals of rooting android phone and so on. I unlocked my bootloader via HTCDev and rooted it using CWM Touch Recovery 6.0.4.5. 3 weeks ago I flashed my HTC One to Probam (AOSB) custom rom, no problems were present, everything ran smoothly and perfectly. Then, 2 weeks ago, I decided to flash ElementalX kernel, being ignorant on purpose to the fact that it was meant for Sense Roms. Upom completion through Aroma Installer, I selected reboot system in recovery. Upon exit, the recovery told me that my phone could have possibly lost its root access and prompted me to root it so i just agreed. There came the problem upon reboot, I could not boot into my OS and I was stuck on the HTC screen. (May I add that I bought my HTC this year March. I S-offed it via Firewater as my Hboot version was 1.56 and Rumrunner couldn't help me S-Off. Advice for those who have hboot versions higher than 1.55 and want to S-off, Firewater is my suggestion. Just make sure you follow the guid also here on XDA forums accurately and I assure you can get s-off) As I was saying, as soon as that happened, I looked for solutions. I tried hasson 2000 all in one toolkit, I tried relocking my bootloader and runming RUU.exe file to return to stock firmware, I tried sideloading a rom in recovery, I tried mounting usb storage to copy a .zip rom into my internal storage but nothing happened. I tried flashing directly via fastboot but the cmd keep saying it couldnt run the file. I couldn't enter adb as the recovery said there is no os present. I really have no more idea what else I can do and I think I've tried just about everything. Please help as it's been 2 weeks into the brick and I'm really desperate. Please help
CID: HTC_044
Hboot:1.56
If there is more information needed please ask as I'm really desperate to fix my phone :C
Click to expand...
Click to collapse
you do realize what you posted is not readable... right? sorry, but i sort of tried reading it, but
break it down into smaller parts.
nkk71 said:
you do realize what you posted is not readable... right? sorry, but i sort of tried reading it, but
break it down into smaller parts.
Click to expand...
Click to collapse
he flashed a sense kernel to an aosp rom and is in bootloop as near as i can tell
he's s-off hboot 1.56 and needs a RUU I assume
boksquare said:
(...)
I unlocked my bootloader via HTCDev and rooted it using CWM Touch Recovery 6.0.4.5.
(...)
I flashed my HTC One to Probam (AOSB) custom rom, no problems were present,
(...)
I decided to flash ElementalX kernel, being ignorant on purpose to the fact that it was meant for Sense Roms.
(...)
I could not boot into my OS and I was stuck on the HTC screen.
(...)
I S-offed it via Firewater
(...)
Click to expand...
Click to collapse
Did you tried to flash an AOSP compatible kernel after you realized you couldn't boot the phone?
boksquare said:
I tried hasson 2000 all in one toolkit
Click to expand...
Click to collapse
You should use fastboot and adb from cmd prompt instead of toolkit.
boksquare said:
I tried relocking my bootloader and runming RUU.exe file to return to stock firmware,
Click to expand...
Click to collapse
Re-locking bootloader to run a ruu.exe is not required when you have S-OFF. Anyway what was the error code when the RUU exe failed? And what was the ruu version?
boksquare said:
I tried sideloading a rom in recovery
Click to expand...
Click to collapse
What happened? What was the error? What rom?
boksquare said:
I tried mounting usb storage to copy a .zip rom into my internal storage but nothing happened.
Click to expand...
Click to collapse
If you can mount your usb storage with your rom.zip on it, you don't need to copy it to your sdcard! Just install the rom from your mounted usb storage... You said ''nothing happened'' Was there any error code?
boksquare said:
I tried flashing directly via fastboot but the cmd keep saying it couldnt run the file.
Click to expand...
Click to collapse
Wait?! You can't flash a rom.zip from fastboot, only from custom recovery. The only thing you can flash from fastboot is a recovery or a ruu/firmware from fastboot RUU mode.
boksquare said:
I couldn't enter adb as the recovery said there is no os present.
Click to expand...
Click to collapse
ADB should work from custom recovery even if you don't have an OS installed.
boksquare said:
(...)
CID: HTC_044
Hboot:1.56
Click to expand...
Click to collapse
post the output of ''fastboot getvar all'' except IMEI. With S-OFF it should be quite easy to make your phone boot again...
clsA said:
he flashed a sense kernel to an aosp rom and is in bootloop as near as i can tell
he's s-off hboot 1.56 and needs a RUU I assume
Click to expand...
Click to collapse
still... if (yes IF) i learned anything in school "run-on" sentences are a NO-NO!! (and i'm not even talking about english schools)
alray said:
Did you tried to flash an AOSP compatible kernel after you realized you couldn't boot the phone?
Click to expand...
Click to collapse
- No, I downloaded and flashed the kernel on my One while I was outstation, so I couldn't do anything when it was stuck on bootloop.
You should use fastboot and adb from cmd prompt instead of toolkit.
Click to expand...
Click to collapse
-I couldn't get into adb through fastboot with the command on cmd "adb reboot bootloader" (attachment below [capture])
Re-locking bootloader to run a ruu.exe is not required when you have S-OFF. Anyway what was the error code when the RUU exe failed? And what was the ruu version?
Click to expand...
Click to collapse
-That's the problem, there was no error code or anything, it just didn't work, nothing happened. [Capture3]
What happened? What was the error? What rom?
Click to expand...
Click to collapse
-It said device not found. [Capture1]
If you can mount your usb storage with your rom.zip on it, you don't need to copy it to your sdcard! Just install the rom from your mounted usb storage... You said ''nothing happened'' Was there any error code?
Click to expand...
Click to collapse
- I believe you and I have a different understanding of usb storage which obviously I'm misinformed. I thought USB Storage is just mounting your CPU storage to your phone.
ADB should work from custom recovery even if you don't have an OS installed.
Click to expand...
Click to collapse
-Not sure, nothing worked.
post the output of ''fastboot getvar all'' except IMEI. With S-OFF it should be quite easy to make your phone boot again...
Click to expand...
Click to collapse
-Capture2 below.
Again I apologize for any inconvenience caused, I'm still new to using XDA forums instead of just reading it for info, thanks and please reply ASAP, desperate and losing hope
boksquare said:
-It said device not found. [Capture1]
Click to expand...
Click to collapse
check you check FAQ #2 in my guide (forget the guide, just the FAQ#2) http://forum.xda-developers.com/showthread.php?t=2541082
nkk71 said:
check you check FAQ #2 in my guide (forget the guide, just the FAQ#2) http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
The problem is, my phone won't even show up in my computer, I've no idea why.
nkk71 said:
check you check FAQ #2 in my guide (forget the guide, just the FAQ#2) http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
I would like to try your method for using the RUU.exe through downgrading hboot all those, but if I downgraded my hboot and everything, and the RUU.exe doesn't work, will my phone go beyond saving? Please advice.
boksquare said:
I would like to try your method for using the RUU.exe through downgrading hboot all those, but if I downgraded my hboot and everything, and the RUU.exe doesn't work, will my phone go beyond saving? Please advice.
Click to expand...
Click to collapse
i think you're rushing things, but since you're s-off, go for ruu.zip method, shows much more information, but beware Win8.1 as mentioned in the FAQs.
(also there's no need to LOCK since you're s-off, and dont even think about S-On, the guide was meant as return to stock for warranty.
i'm sure you can Device Manager fixed, it's probably somewhere there, just needs corrected/updated drivers, and by the way, don't use TWRP 2.7.0.0 it has problems with adb.
nkk71 said:
i think you're rushing things, but since you're s-off, go for ruu.zip method, shows much more information, but beware Win8.1 as mentioned in the FAQs.
(also there's no need to LOCK since you're s-off, and dont even think about S-On, the guide was meant as return to stock for warranty.
i'm sure you can Device Manager fixed, it's probably somewhere there, just needs corrected/updated drivers, and by the way, don't use TWRP 2.7.0.0 it has problems with adb.
Click to expand...
Click to collapse
Okay, I will get to it right away, but before that, I was using CWM Touch 6.0.4.5 but I still can't get adb in cmd. Once I've entered recovery I will automatically find adb through "adb devices" command without having to do anything special? And do I need to remove tampered all those before running RUU.Zip? Or is it just for going back to stock? I am sorry, as there are just a lot of things I'm not clear about or understand. Please advice :/
boksquare said:
I was using CWM Touch 6.0.4.5 but I still can't get adb in cmd. Once I've entered recovery I will automatically find adb through "adb devices" command without having to do anything special?
Click to expand...
Click to collapse
if adb devices doesn't list your device, then you have to check Windows Device Manager and fix the driver problems.
boksquare said:
And do I need to remove tampered all those before running RUU.Zip? Or is it just for going back to stock?
Click to expand...
Click to collapse
You can leave everything as is, tampered doesn't matter in any case, and unlocked won't matter with S-OFF.
DO NOT GO S-ON.
boksquare said:
I am sorry, as there are just a lot of things I'm not clear about or understand. Please advice :/
Click to expand...
Click to collapse
No problem, better to ask before, otherwise you could end up in a worse situation.
But still don't understand why want to go all the trouble of ruu. can you explain (briefly, not a huge paragraph :angel
By the way, if you're stuck in a bootloop because you were flashing a 4.4 ROM using CWM 6.0.4.5, then that would be the problem, you need TWRP 2.6.3.3 or higher.
nkk71 said:
if adb devices doesn't list your device, then you have to check Windows Device Manager and fix the driver problems.
You can leave everything as is, tampered doesn't matter in any case, and unlocked won't matter with S-OFF.
DO NOT GO S-ON.
No problem, better to ask before, otherwise you could end up in a worse situation.
But still don't understand why want to go all the trouble of ruu. can you explain (briefly, not a huge paragraph :angel
By the way, if you're stuck in a bootloop because you were flashing a 4.4 ROM using CWM 6.0.4.5, then that would be the problem, you need TWRP 2.6.3.3 or higher.
Click to expand...
Click to collapse
Don't worry I won't enter S-On.
But before the brick there were no problems with the drivers as I had installed HTC Sync Drivers. After the brick my phone just couldn't be detected in my computer. I just assumed this problem is linked with the brick.
Because I have no idea what other methods can save my phone, please advice if there are other methods beside RUU
boksquare said:
Don't worry I won't enter S-On.
But before the brick there were no problems with the drivers as I had installed HTC Sync Drivers. After the brick my phone just couldn't be detected in my computer. I just assumed this problem is linked with the brick.
Because I have no idea what other methods can save my phone, please advice if there are other methods beside RUU
Click to expand...
Click to collapse
So after reading your first post i see you tried flashing a 4.4 rom using CWM 6.0.4.5, so
get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then install the ROM again.
nkk71 said:
So after reading your first post i see you tried flashing a 4.4 rom using CWM 6.0.4.5, so
get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then install the ROM again.
Click to expand...
Click to collapse
But the ROM is not in my Htc, how do I move it there? I had no way of moving it there that's why I went for the RUU
boksquare said:
But the ROM is not in my Htc, how do I move it there? I had no way of moving it there that's why I went for the RUU
Click to expand...
Click to collapse
you have 3 choices to get the ROM onto your phone (once you have custom recovery):
1- OTG cable
2- adb sideload
3- adb push
If you don't have OTG cable, I personally like adb push (example below), though many like adb sideload (plenty of guides and how tos around).
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]fastboot devices[/COLOR][/B]
HT34xxxxxxxx fastboot [I][SIZE="1"]<- you are in bootloader[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img[/COLOR][/B]
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s
-> enter RECOVERY
Code:
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [B][I]<- yes, it took over 5 mins,
without showing any progress[/I][/B]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]
C:\ADB3>
-> in recovery, select "install" and install the ROM
.
nkk71 said:
you have 3 choices to get the ROM onto your phone (once you have custom recovery):
1- OTG cable
2- adb sideload
3- adb push
If you don't have OTG cable, I personally like adb push (example below), though many like adb sideload (plenty of guides and how tos around).
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]fastboot devices[/COLOR][/B]
HT34xxxxxxxx fastboot [I][SIZE="1"]<- you are in bootloader[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img[/COLOR][/B]
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s
-> enter RECOVERY
Code:
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [B][I]<- yes, it took over 5 mins,
without showing any progress[/I][/B]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]
C:\ADB3>
-> in recovery, select "install" and install the ROM
.
Click to expand...
Click to collapse
Okay, I'm downloading the drivers after checking the device manager. You were right, the drivers were gone. I had no idea why. I installed Sync Manager before with all the drivers present, no idea why is it gone now.
Still, once the download is finished I will do as you said and will update you ASAP. Thanks in advance. :good::laugh:
boksquare said:
Okay, I'm downloading the drivers after checking the device manager. You were right, the drivers were gone. I had no idea why. I installed Sync Manager before with all the drivers present, no idea why is it gone now.
Still, once the download is finished I will do as you said and will update you ASAP. Thanks in advance. :good::laugh:
Click to expand...
Click to collapse
No problem, good luck
nkk71 said:
No problem, good luck
Click to expand...
Click to collapse
OMG OMG OMG OMG OMG OMG OMG OMG OMG !!!! It worked !!!! At first I was disappointed as I couldn't fix my drivers by reinstalling HTC Sync Manager. I was going to ask you but I took a look back into your guide at FAQ #2 and followed it exactly and I got it reinstalled )))) I pushed the ROM in and flashed in Recovery and I just booted my phone ! Thanks for all your time and advices, really appreciated it. How I wish I could thank you in person or something. Thanks man, really thanks a lot
boksquare said:
OMG OMG OMG OMG OMG OMG OMG OMG OMG !!!! It worked !!!! At first I was disappointed as I couldn't fix my drivers by reinstalling HTC Sync Manager. I was going to ask you but I took a look back into your guide at FAQ #2 and followed it exactly and I got it reinstalled )))) I pushed the ROM in and flashed in Recovery and I just booted my phone ! Thanks for all your time and advices, really appreciated it. How I wish I could thank you in person or something. Thanks man, really thanks a lot
Click to expand...
Click to collapse
My pleasure glad everything worked out, and xda has a nice little thanks button that you can press when a post is useful
and if you could also edit the main thread title to include [SOLVED] (go to 1st post click EDIT, at the bottom of the edit window click GO ADVANCED, then you can edit the main title), thanks
Hello. im new here and i ive just bricked my phone , and i wana get back to stock RUU and i dont know whick RUU to download anny sollutions how to check what RUU do i need? Ps.sorry for my bad english. Anny help would be awesome
ubas98 said:
Hello. im new here and i ive just bricked my phone , and i wana get back to stock RUU and i dont know whick RUU to download anny sollutions how to check what RUU do i need? Ps.sorry for my bad english. Anny help would be awesome
Click to expand...
Click to collapse
post the ouput of "fastboot getvar all" except the IMEI and SERIALNO so we can help you determine which RUU you can use if any available for your phone.
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP -v32.120.274.0909
OS-5.16.161.2 eMMC-boot 2048MB
Ive writed everything that i saw on my screen.if i mised anything please tell me
ubas98 said:
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP -v32.120.274.0909
OS-5.16.161.2 eMMC-boot 2048MB
Ive writed everything that i saw on my screen.if i mised anything please tell me
Click to expand...
Click to collapse
that's not your fastboot getvar all, however, the most important part is there which is your OS number, 5.16.161.2 is Vodafone, there is no RUU for your device, do you not have a backup ? how did you brick ?
Seanie280672 said:
that's not your fastboot getvar all, however, the most important part is there which is your OS number, 5.16.161.2 is Vodafone, there is no RUU for your device, do you not have a backup ? how did you brick ?
Click to expand...
Click to collapse
well ive wanted to get to stock so i unlocked my bootloader and tried to install ruu but it failed. and because i locked the bootloader ive somehow bricked my phone one cm11 loading screen. ive unlocked my bootloader and my recovery was all mesed up it couldnt load anny storage so i cant instal other rooms so im stuck here .i have no clue what to do
ubas98 said:
well ive wanted to get to stock so i unlocked my bootloader and tried to install ruu but it failed. and because i locked the bootloader ive somehow bricked my phone one cm11 loading screen. ive unlocked my bootloader and my recovery was all mesed up it couldnt load anny storage so i cant instal other rooms so im stuck here .i have no clue what to do
Click to expand...
Click to collapse
well as your s-on, you can forget about any RUU's at all for now.
I would recommend you flash twrp recovery, use 2.6.3.3 and then erase cache, then reboot bootloader (see commands below).
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
after that go into twrp recovery and select wipe then format data, this will completely wipe your phone of everything, but as its already messed up then it doesn't really matter, does it.
once that is done, download a sense rom from the development section and try and push it to your internal sdcard, if successful then flash it.
Seanie280672 said:
well as your s-on, you can forget about any RUU's at all for now.
I would recommend you flash twrp recovery, use 2.6.3.3 and then erase cache, then reboot bootloader (see commands below).
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
after that go into twrp recovery and select wipe then format data, this will completely wipe your phone of everything, but as its already messed up then it doesn't really matter, does it.
once that is done, download a sense rom from the development section and try and push it to your internal sdcard, if successful then flash it.
Click to expand...
Click to collapse
well everything worked but when i enter recovery mode it askes me a pasword and i dont know it anny solution?
ubas98 said:
well everything worked but when i enter recovery mode it askes me a pasword and i dont know it anny solution?
Click to expand...
Click to collapse
password ? never seen that before, could you post a photo of it ?
Seanie280672 said:
password ? never seen that before, could you post a photo of it ?
Click to expand...
Click to collapse
http://postimg.org/image/ucolu3a83/ here is the img
ubas98 said:
http://postimg.org/image/ucolu3a83/ here is the img
Click to expand...
Click to collapse
I have never seen that before in all my years of using TWRP, maybe one of the other guys can help you with that
Seanie280672 said:
I have never seen that before in all my years of using TWRP, maybe one of the other guys can help you with that
Click to expand...
Click to collapse
maybe i could use another recovery .if yes anny what is other best recovery?
ubas98 said:
maybe i could use another recovery .if yes anny what is other best recovery?
Click to expand...
Click to collapse
oh somehow the pasword screen went out and now im in the recovery in which folder i could trasfer my rom to the phone?
ubas98 said:
oh somehow the pasword screen went out and now im in the recovery in which folder i could trasfer my rom to the phone?
Click to expand...
Click to collapse
adb push it straight to the sdcard, make sure your phone is plugged into the computer and the rom is in the same folder as adb and fastboot files, then issue this command:
Code:
adb push (name of rom).zip /sdcard/
it will look like its not doing anything but will let you know when its done, then uplug your phone before flashing the rom.
and both TWRP and CWM have their good points, you need CWM to flash AOSP rom's and TWRP to flash sense rom's
Seanie280672 said:
well as your s-on, you can forget about any RUU's at all for now.
I would recommend you flash twrp recovery, use 2.6.3.3 and then erase cache, then reboot bootloader (see commands below).
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
after that go into twrp recovery and select wipe then format data, this will completely wipe your phone of everything, but as its already messed up then it doesn't really matter, does it.
once that is done, download a sense rom from the development section and try and push it to your internal sdcard, if successful then flash it.
Click to expand...
Click to collapse
Strangely this is exactly the position I'm in today too.
I wanted to revert to stock after trying cyanogen, relocked the bootloaded and tried to run an RUU. However it stopped with an 'unknown error'. So I tried to push a zip file to it but the adb can't connect to the device and the phone isn't showing up in the device manager (because it's in boot mode?).
I then tried your advice about twrp and tried a different RUU but still get an unknown error and still can't push to the device.
Any ideas of what to try next? My OS is now showing as empty, there was something there previously.
I figured it was time to get some help before I broke things any more.
SGSII_LEDnotify said:
Strangely this is exactly the position I'm in today too.
I wanted to revert to stock after trying cyanogen, relocked the bootloaded and tried to run an RUU. However it stopped with an 'unknown error'. So I tried to push a zip file to it but the adb can't connect to the device and the phone isn't showing up in the device manager (because it's in boot mode?).
I then tried your advice about twrp and tried a different RUU but still get an unknown error and still can't push to the device.
Any ideas of what to try next? My OS is now showing as empty, there was something there previously.
I figured it was time to get some help before I broke things any more.
Click to expand...
Click to collapse
first thing to do is unlock your bootloader again, if you've not already done that, then get TWRP 2.6.3.3 recovery on there, that maybe a problem though as your phone isn't showing in device manager.
So put your phone into the bootloader and see what device manager says then, it should say something if its detecting your phone, even if drivers arnt installed.
also, which HBOOT are you on ? and which Windows OS are you using ?
Seanie280672 said:
first thing to do is unlock your bootloader again, if you've not already done that, then get TWRP 2.6.3.3 recovery on there, that maybe a problem though as your phone isn't showing in device manager.
So put your phone into the bootloader and see what device manager says then, it should say something if its detecting your phone, even if drivers arnt installed.
also, which HBOOT are you on ? and which Windows OS are you using ?
Click to expand...
Click to collapse
I think I've unlocked the bootloader again, fastboot is available and it's showing 'unlocked' at the top. twrp is on there too and I've done the wipe again. The fastboot commands work but pushing doesn't
error: device not found
HBOOT is 1.55.0000 / win7 64 home
Btw Twrp said it couldn't find cache but the wipe was successful.
Thanks for the help.
SGSII_LEDnotify said:
I think I've unlocked the bootloader again, fastboot is available and it's showing 'unlocked' at the top. twrp is on there too and I've done the wipe again. The fastboot commands work but pushing doesn't
error: device not found
HBOOT is 1.55.0000 / win7 64 home
Btw Twrp said it couldn't find cache but the wipe was successful.
Thanks for the help.
Click to expand...
Click to collapse
ok I see what your saying now, what you need to do is boot into TWRP, main screen only, no sub menu's, at that point is your phone still detected in device manager ?
if so then............
put the rom you want to flash in the same folder as adb and fastboot files on your computer, then type:
Code:
adb push (name of rom).zip /sdcard/
you cant push files to your phone using fastboot or whilst its in the bootloader, that's strictly for flashing simple files like Radio's, HBOOTS, recoveries.
Seanie280672 said:
ok I see what your saying now, what you need to do is boot into TWRP, main screen only, no sub menu's, at that point is your phone still detected in device manager ?
if so then............
put the rom you want to flash in the same folder as adb and fastboot files on your computer, then type:
Code:
adb push (name of rom).zip /sdcard/
you cant push files to your phone using fastboot or whilst its in the bootloader, that's strictly for flashing simple files like Radio's, HBOOTS, recoveries.
Click to expand...
Click to collapse
Well at least I've got something in the device manager even if it is a SAMSUNG Android Phone and not my HTC!
The push command hasn't brought up an error, the cursor is just flashing on the next line. It appears to be doing nothing like you said. So I guess I'm playing the waiting game for ten minutes or so. Will there be a notification when it's completed?
---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------
Ok, transfer complete
SGSII_LEDnotify said:
Well at least I've got something in the device manager even if it is a SAMSUNG Android Phone and not my HTC!
The push command hasn't brought up an error, the cursor is just flashing on the next line. It appears to be doing nothing like you said. So I guess I'm playing the waiting game for ten minutes or so. Will there be a notification when it's completed?
---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------
Ok, transfer complete
Click to expand...
Click to collapse
ok, unplug your phone, then goto install and select the rom from the list you just pushed, follow the Aroma options and instructions and also id recommend when given the option, to wipe data.
Seanie280672 said:
ok, unplug your phone, then goto install and select the rom from the list you just pushed, follow the Aroma options and instructions and also id recommend when given the option, to wipe data.
Click to expand...
Click to collapse
I renamed the zip file because there were spaces in the name causing errors, would that cause a failure when trying to install?
skipping MD5 check: no md5 file found
Error flashing zip '/sdcard/****.zip'
updating partition details
failed