this has been on going for 2 days now and i still cant find a way around it...
i know how to flash both different types of recovery modes and can do that without a prob, i have the latest version of super su on a usb stick and also multiple roms on a usb stick which i am capable of flashing these via an OTA cable, but every time i flash the root then flash a rom, it says its installed but when i reboot it just stays on the htc screen with the red writing along the bottom for the best part of 45 seconds then restarts straight back into recovery.
i'll happily admit i'm no expert when it comes to android, but i've had a galaxy ace, s2, s3 and s4 before moving to a htc one, i've never had issues like this before...
if someone has a skype account and is willing to have a chat with me and help me thru this issue so that i can have a working and stable phone again, otherwise i have just bought a £350 paperweight.
Many thanks in advance to all those who help me!!
nottys4 said:
this has been on going for 2 days now and i still cant find a way around it...
i know how to flash both different types of recovery modes and can do that without a prob, i have the latest version of super su on a usb stick and also multiple roms on a usb stick which i am capable of flashing these via an OTA cable, but every time i flash the root then flash a rom, it says its installed but when i reboot it just stays on the htc screen with the red writing along the bottom for the best part of 45 seconds then restarts straight back into recovery.
i'll happily admit i'm no expert when it comes to android, but i've had a galaxy ace, s2, s3 and s4 before moving to a htc one, i've never had issues like this before...
if someone has a skype account and is willing to have a chat with me and help me thru this issue so that i can have a working and stable phone again, otherwise i have just bought a £350 paperweight.
Many thanks in advance to all those who help me!!
Click to expand...
Click to collapse
you need to explain what you have done so far
and post a fastboot getvar all minus your serial no and IMEI
Download TWRP 2.6.3.3
clsA said:
you need to explain what you have done so far
and post a fastboot getvar all minus your serial no and IMEI
Download TWRP 2.6.3.3
Click to expand...
Click to collapse
is there any way you can skype me as its too much to write in a message?
my skype email address is.... [email protected]
nottys4 said:
is there any way you can skype me as its too much to write in a message?
my skype email address is.... [email protected]
Click to expand...
Click to collapse
Sorry but no ..just take your time and explain the best you can
nottys4 said:
this has been on going for 2 days now and i still cant find a way around it...
i know how to flash both different types of recovery modes and can do that without a prob, i have the latest version of super su on a usb stick and also multiple roms on a usb stick which i am capable of flashing these via an OTA cable, but every time i flash the root then flash a rom, it says its installed but when i reboot it just stays on the htc screen with the red writing along the bottom for the best part of 45 seconds then restarts straight back into recovery.
i'll happily admit i'm no expert when it comes to android, but i've had a galaxy ace, s2, s3 and s4 before moving to a htc one, i've never had issues like this before...
if someone has a skype account and is willing to have a chat with me and help me thru this issue so that i can have a working and stable phone again, otherwise i have just bought a £350 paperweight.
Many thanks in advance to all those who help me!!
Click to expand...
Click to collapse
Flash root then a Rom??
You root the ROM not the phone! If you flash root then a rom overtop of course it's unrooted. I thought you had this corrected and the device up and running.
clsA said:
Sorry but no ..just take your time and explain the best you can
Click to expand...
Click to collapse
well i am running recovery-clockwork-touch-6.0.3.1-m7 along side with UPDATE-SuperSU-v1.65 the recovcery was put on via flash boot in command prompt and the super su zip was put on via external usb stick via the OTA cable.
i also have
openrecovery-twrp-2.6.3.0-m7 in an .img file
CWM-SuperSU-v1.30.rar
TWRP_2.6.3.3_m7_renovate.rar
RenovateROM_8.2.rar
Android_Revolution_HD-One_52.0.rar( this file i have never got to work)
recovery-clockwork-touch-6.0.4.6-m7ul.img
but i'm stuck as to what to install and how to do it
nottys4 said:
this has been on going for 2 days now and i still cant find a way around it...
i know how to flash both different types of recovery modes and can do that without a prob, i have the latest version of super su on a usb stick and also multiple roms on a usb stick which i am capable of flashing these via an OTA cable, but every time i flash the root then flash a rom, it says its installed but when i reboot it just stays on the htc screen with the red writing along the bottom for the best part of 45 seconds then restarts straight back into recovery.
i'll happily admit i'm no expert when it comes to android, but i've had a galaxy ace, s2, s3 and s4 before moving to a htc one, i've never had issues like this before...
if someone has a skype account and is willing to have a chat with me and help me thru this issue so that i can have a working and stable phone again, otherwise i have just bought a £350 paperweight.
Many thanks in advance to all those who help me!!
Click to expand...
Click to collapse
For this problem, I know less.
just to let you know i'm running CWM v6.0.3.1
mb_guy said:
Flash root then a Rom??
You root the ROM not the phone! If you flash root then a rom overtop of course it's unrooted. I thought you had this corrected and the device up and running.
Click to expand...
Click to collapse
i would love to flash a rom then root afterwards but once ive got to the end of the rom flash and my recovery says reboot i get the message saying root is broken and get asked to install it, which would normally happen when the rom boots up and it installs susper su inside the rom but as the rom never boots up and just goes back to revovery, i'm rather stuck at this point..
any ideas??
if i need TWRP_2.6.3.3 where can i get the .img file as i have the zip file but cant seem to get that flashed onto my phone, i tried unzipping it and just flashing the recovery.img but it failed
i've just found: openrecovery-twrp-2.6.3.4-m7ul.img
would that do it or do i need 2.6.3.3?
ive just installed TWRP_2.6.3.3_m7_renovate thru the CWM that was installed but now this recovery dosent give me the option of installing from usb stick like the CWM did??
nottys4 said:
i've just found: openrecovery-twrp-2.6.3.4-m7ul.img
would that do it or do i need 2.6.3.3?
Click to expand...
Click to collapse
Okay, first, stay calm. Being in a rush will make you mess things even more. Now, go into your bootloader, what does it say? Alternatively, if you know how to, post the output of fastboot getvar all.
Sent from my iPod touch using Tapatalk
n1234d said:
Okay, first, stay calm. Being in a rush will make you mess things even more. Now, go into your bootloader, what does it say? Alternatively, if you know how to, post the output of fastboot getvar all.
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
i'd like to learn so how do i post the output of fastboot getvar all??
nottys4 said:
i'd like to learn so how do i post the output of fastboot getvar all??
Click to expand...
Click to collapse
Have you set up adb and fastboot on your pc? If not, use this guide,
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
and once done, report back. Till then, just tell me what your phones bootloader says
Sent from my iPod touch using Tapatalk
TAMPERED(in black)
UNLOCKED(in pink)
M7_UL PUT SHIP S-OFF RH
CID-02___001
HBOOT-1.44.0000
RADIO-4A.1.4.3250.13
openDSP-v26.120.274.0202
Emmc-boot
May 4 2013, 05:32:56:-1
FASTBOOT AC(in red)
then vol up etc in orange
n1234d said:
Have you set up adb and fastboot on your pc? If not, use this guide,
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
and once done, report back. Till then, just tell me what your phones bootloader says
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
yes i've dealt with fastboot and adb on my pc before, but been doing it a little blindly....
mant thanks for your help so far...think i'll go grab a coffee back in 5 mins
nottys4 said:
yes i've dealt with fastboot and adb on my pc before, but been doing it a little blindly....
mant thanks for your help so far...think i'll go grab a coffee back in 5 mins
Click to expand...
Click to collapse
Okay, now do you quickly want to go to stock or stay and troubleshoot the problem?
Sent from my iPod touch using Tapatalk
n1234d said:
Okay, now do you quickly want to go to stock or stay and troubleshoot the problem?
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
i'd like to return to stock but i use the toggles on the pull down notification bar a lot and when i got the phone when it was completly un rooted it didnt give me that function. and i love the option of changing what toggles you want up there in the renovation rom, you can prob get them in other roms but the renovation rom is the only 1 i have had working on my phone.
nottys4 said:
i'd like to return to stock but i use the toggles on the pull down notification bar a lot and when i got the phone when it was completly un rooted it didnt give me that function. and i love the option of changing what toggles you want up there in the renovation rom, you can prob get them in other roms but the renovation rom is the only 1 i have had working on my phone.
Click to expand...
Click to collapse
Ok, never mind about that, I'll get you back there. Now do you have any data on your phone that you need? Ps, be a little quick, I've gotta leave home in ~15, and my data plan is over
Sent from my iPod touch using Tapatalk
Related
You can find it on:
http://alpharev.nl/
HBOOT 1.0+ is NOT supported
MOD EDIT: No shouting please!
Boot from ISO and follow instructions yea? Is it safe to boot from USB?
i have 1.0
it works
Damn, why not at my device....?!
http://forum.xda-developers.com/showpost.php?p=10176241&postcount=130
aikon96 said:
Damn, why not at my device....?!
http://forum.xda-developers.com/showpost.php?p=10176241&postcount=130
Click to expand...
Click to collapse
Nand backup CM 6.1, pull the backup to your PC (just to be sure). Install a rooted stock ROM, then try.
ogo2 said:
it works
Click to expand...
Click to collapse
I can't get it to work.. can't access fastboot in step 1 tried power for several minutes..
whitetigerdk said:
I can't get it to work.. can't access fastboot in step 1 tried power for several minutes..
Click to expand...
Click to collapse
Here is the same with Hboot: 0.43.0001. its get complete freezed until I remove the battery, but its not bricked
Suppe123 said:
Here is the same with Hboot: 0.43.0001. its get complete freezed until I remove the battery, but its not bricked
Click to expand...
Click to collapse
Jeeeezz-US! You were lucky...
Ok maybe we should use this thread
Suppe123 said:
Here is the same with Hboot: 0.43.0001. its get complete freezed until I remove the battery, but its not bricked
Click to expand...
Click to collapse
Same problem, haven't been able to find a solution so far
when cell is in hboot usb plug, before turn in fastboot try to navigate with vol+ and vol - and when you see it isn't freeze, push anykey of pc and when it says turn your phone into fastboot do it.
juanporrero said:
when cell is in hboot usb plug, before turn in fastboot try to navigate with vol+ and vol - and when you see it isn't freeze, push anykey of pc and when it says turn your phone into fastboot do it.
Click to expand...
Click to collapse
Tried that, even tried going into fastboot, and back to HBOOT doesn't work either
I've got bootloader 0.43.001 I had the keep it simple froyo rom installed when trying. I'll try the keep it simple eclair rom now
JonasDroid said:
Tried that, even tried going intofastboot, and back to HBOOT doesn't work either
I've got bootloader 0.43.001 I had the keep it simple froyo rom installed when trying.
Click to expand...
Click to collapse
Same thing is here
does this mean we can now change the partitions sizes?
eclair rom didn't help either, didn't really expect it to help but it was worth the try.
Any other suggestions? looks like much off us have this problem
How did you burn the iso (the ones with the fastboot problem)?
I burned it using the build in windows image burner onto a CD. I might try a USB later on but I'll stop trying for now
i do it with azure
Threadstarter,
Can you provide us a complete steps (Tutorial)on how to S-OFF the Hboot ? I totally do not understand, as i have never flash such thing before. I'm using the rooted HTC official Froyo ROM found in xda forum
foosoomin said:
Threadstarter,
Can you provide us a complete steps (Tutorial)on how to S-OFF the Hboot ? I totally do not understand, as i have never flash such thing before. I'm using the rooted HTC official Froyo ROM found in xda forum
Click to expand...
Click to collapse
Burn the iso and boot from it. The rest of the instructions are given to you as you go
Swyped from my HTC Legend
Is it normal that you need to press the power at the right time 2ce?
I managed to get past the first by some pretty stupid method which I'm not going to make public if I'm not sure that it works (cause it's pretty risky)
But that same method doesn't work the second time in step 2/3.
Or isn't it supposed to ask for that a 2nd time?
So I had to pull my battery out in the 2nd step and it showed a message that it was unable to flash the HBoot but luckily the old was still intact.
S-OFF on first try
I used unetbootin to make a usb boot pen, then boot into tiny core, followed instructions and S-OFF
All,
New to htc and flashing, and try doing at 3am didn't help either. hope someone can help. Will paypal $50 to anyone that can help. Thanks in advance.
Here's what i did
using One_S_All-In-One_Kit_v3.5 for all my modding
got token
unlocked bootloaded
didn't flash any recovery
flash a new .img kernel, but i used a boot.img from a zip file (home2wake zip) - don't ask why, i wasn't thinking lol
phone rom was all black, keeps rebooting
i managed to flash recovery, recovery-clockwork-6.0.3.1-m7wls.img
then wanted to restore stock rom
so i downloaded, this rom, http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
flashed zip using recovery
went through the rom custom installation of what i wanted installed.
After that it rebooted and stuck on green htc screen
i can get back into boot loader, but can't load recovery, can't factory reset, any option i select, the screen flash and sends me back to bootloader
rom won't load, can't get into recover, computer not detecting phone
Please help!!!
Check out this maybe a RUU will help -
http://forum.xda-developers.com/showthread.php?t=2251800
Why did you use one s kit, I'm confused
Sent from my HTCONE using xda premium
you can try to load ADB Fastboot on your PC, then connect your phone via usb, be sure to have all of the drivers.
in bootloader, if it reads FASTBOOT USB, then you can us
fastboot flash recovery (Name of recovery).img
once that is done you should be able to at least get back into recovery....
check the link for recovery file
http://forum.xda-developers.com/showthread.php?t=2236418
I am no expert, but my guess would be to go back to stock boot / recovery: http://forum.xda-developers.com/showthread.php?t=2236418
Relock your phone: fastboot oem lock
Install the RUU: http://forum.xda-developers.com/showthread.php?t=2250904
And in the future don't use an All-In-One-Kit meant for another phone (The One S in your case)
p.s. Another thread that may help get you back to square one: http://forum.xda-developers.com/showthread.php?t=2251800
thanks all,
will try all the suggestions above tonight, will let you guys know how it goes. i used the all one s because it was gui and easy and lots of extra and functions. but i guess the extra made it worst.
Right now when i plug in my phone the computer doesn't detect anything, hopefully the adb can talk to it to flash a new recovery/rom/kernel.
Pm me
Sent from my HTCONE using Tapatalk 2
It wasn't the extras that messed it up. It was the fact you were using an AIO that isn't for your device. That's a big no no.
Sent from my HTCONE using xda app-developers app
gu12u7 said:
thanks all,
will try all the suggestions above tonight, will let you guys know how it goes. i used the all one s because it was gui and easy and lots of extra and functions. but i guess the extra made it worst.
Right now when i plug in my phone the computer doesn't detect anything, hopefully the adb can talk to it to flash a new recovery/rom/kernel.
Click to expand...
Click to collapse
Once you get back to stock with the RUU, use Hassoon2000's all in one kit...n00b proof!
P_M_G said:
Once you get back to stock with the RUU, use Hassoon2000's all in one kit...n00b proof!
Click to expand...
Click to collapse
i was using this, all of the recovery on there were for samsung s3/s4/and special edition. so i couldn't get to the recovery. Then i started tweaking around with the extras and flashed a boot.img to a kernel. failed
Android Revolution ROM is not for the sprint htc one. fyi
First you'll need this file http://forum.xda-developers.com/showthread.php?t=2250904
Extract to someplace you can find it, maybe the desktop
if you power the phone down then hold the vol - button does it boot into bootloader?
if so make sure you have the htc fastboot drivers installed from htc sync
if your on a windows machine from command prompt navigate to the platform-tools folder
for example
mine is in C:/users/ray/downloads/adt-bundle-windows-x86_64/adt-bundle-windows-x86_64/sdk/platform-tools
in command prompt issue the command
fastboot oem lock
once the bootloader is re-locked
issue the command
fastboot oem rebootRUU
the phone should reboot into a black screen with greenish htc letters
find the setup.exe file from the ruu file and run it.
if all goes well you should be back to stock with a locked bootloader.
good luck
Awesome, unbricked it! Thank you wranglerray!!!!!!
Also thanks to everyone that replied, but it was wranglerray detailed step that helped me through it. awesome community.
as promised, send me your paypal account wranglerray, i'll send you the $50
Let this thread be a lesson that 1) don't mess with your phone if you don't know what you're doing and 2) don't flash a GSM ROM on your Sprint phone because it wipes your boot and recovery partition (on GSM phones, it wipes data and system but sprints partitions are different).
Sent from my HTCONE using Tapatalk 2
-viperboy- said:
Let this thread be a lesson that 1) don't mess with your phone if you don't know what you're doing and 2) don't flash a GSM ROM on your Sprint phone because it wipes your boot and recovery partition (on GSM phones, it wipes data and system but sprints partitions are different).
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
failing is learning. but more like read all the instructions before messing with your phone.
P_M_G said:
Once you get back to stock with the RUU, use Hassoon2000's all in one kit...n00b proof!
Click to expand...
Click to collapse
Isn't that a One X only kit?
gu12u7 said:
Awesome, unbricked it! Thank you wranglerray!!!!!!
Also thanks to everyone that replied, but it was wranglerray detailed step that helped me through it. awesome community.
as promised, send me your paypal account wranglerray, i'll send you the $50
Click to expand...
Click to collapse
That's what these forums are all about no need to send money. Glad I could help you.
gu12u7 said:
failing is learning. but more like read all the instructions before messing with your phone.
Click to expand...
Click to collapse
Failing after making a bunch of random attempts to do something doesn't constitute learning. Next time you should make sure you actually understand what it is that you are trying to do before you do it, and maybe then you won't end up almost completely wiping your phone clean.
You're lucky that the international One's and Sprint Ones partitions aren't like the Sprint/international S3, or else you would've overrided your bootloader as well and had a brick on your hands.
It started here:
http://forum.xda-developers.com/showthread.php?t=2530605
I followed this post.
http://forum.xda-developers.com/showthread.php?t=2509676
Got nowhere because of the puttytel window timeout problem.
Related to this post was this post:
http://forum.xda-developers.com/showthread.php?p=47749358#post47749358
I have an unlocked bootloader on Moto X from sprint. I just need the easiest way to root.
This looked confusing. http://forum.xda-developers.com/showthread.php?t=2536200. Gotta be another way.
Have considered restoring to stock and taking the dang thing back http://atsgadgets.com/how-to-restor...lite-att-t-mobile-sprint-verizon-us-cellular/. So frustrated.
I've offered paypal to those who can do it successfully. I am so burnt out on trying to make this work. This PITA is not worth android. I have a one click jailbroken phone now. And I have successfully rooted and installed custom roms before but this is totally out of hand how complex this is for me. Maybe I'm just remedial but it seems several are having trouble with this model. For open source, this should not be this tough.
/rant. Almost ready to throw in the towel, but still listening.....
Sorry for the multiple posts. Just trying to get some new opinions. HTC Evo 4 g was done in 10 minutes. This has taken 4 days.
:crying:
bullpen7979 said:
I have an unlocked bootloader on Moto X from sprint. I just need the easiest way to root.
This looked confusing. http://forum.xda-developers.com/showthread.php?t=2536200. Gotta be another way.
Have considered restoring to stock and taking the dang thing back http://atsgadgets.com/how-to-restor...lite-att-t-mobile-sprint-verizon-us-cellular/. So frustrated.
I've offered paypal to those who can do it successfully. I am so burnt out on trying to make this work. This PITA is not worth android. I have a one click jailbroken phone now. And I have successfully rooted and installed custom roms before but this is totally out of hand how complex this is for me. Maybe I'm just remedial but it seems several are having trouble with this model. For open source, this should not be this tough.
/rant. Almost ready to throw in the towel, but still listening.....
Sorry for the multiple posts. Just trying to get some new opinions. HTC Evo 4 g was done in 10 minutes. This has taken 4 days.
:crying:
Click to expand...
Click to collapse
Are you on 4.4 and what computer OS are you using?
I am on android version 4.2.2 and windows xp SP 3. thanks for your response, sir.
bullpen7979 said:
I am on android version 4.2.2 and windows xp SP 3. thanks for your response, sir.
Click to expand...
Click to collapse
Here, go into Settings -> About Phone and tell me what your Build Number is (at the very bottom).
Do not put in the cmd window mfastboot, just try fastboot flash recovery twrp 2.6.3.1-ghost-4.4.img. Now also put the recovery image in the same folder as fast boot, I believe its SDK tools folder
Sent on my Moto X
bullpen7979 said:
I am on android version 4.2.2 and windows xp SP 3. thanks for your response, sir.
Click to expand...
Click to collapse
The method that you thought was confusing, is the one you should use. If I have time, I could try helping you with it.
ALU0506, the build number is 13.9.0Q2.X-116-MX-17-57-1. Thanks everyone for your help.
I have downloaded the files mentioned in the thread. Thats as far as i have gotten. If you have time to help, that would be great. I mean like over the top great
bullpen7979 said:
I have downloaded the files mentioned in the thread. Thats as far as i have gotten. If you have time to help, that would be great. I mean like over the top great
Click to expand...
Click to collapse
I can try helping over gtalk.
bullpen7979 said:
I have downloaded the files mentioned in the thread. Thats as far as i have gotten. If you have time to help, that would be great. I mean like over the top great
Click to expand...
Click to collapse
Plug in your phone and put it into fastboot by typing adb reboot bootloader then type fastboot devices does it show that you are connected?
I will try that as soon as I can and get back to you. I have two computers one at my hotel and one here. I'm not sure I have the ADB tools on my netbook
Sent from my XT1056 using xda app-developers app
bullpen7979 said:
I will try that as soon as I can and get back to you. I have two computers one at my hotel and one here. I'm not sure I have the ADB tools on my netbook
Sent from my XT1056 using xda app-developers app
Click to expand...
Click to collapse
if you are still looking for help i can help you get this done on gtalk as well. send me a pm with your username. it will take virtually no time at all
jayboyyyy said:
if you are still looking for help i can help you get this done on gtalk as well. send me a pm with your username. it will take virtually no time at all
Click to expand...
Click to collapse
especially since he already unlocked the bootloader. Just flash recovery, then flash supersu.zip.
aooga said:
especially since he already unlocked the bootloader. Just flash recovery, then flash supersu.zip.
Click to expand...
Click to collapse
ya during his four days of misery, he could have just read for 1 hour on the stuff so it would seem confusing anymore and then he would have had a rooted phone. But either way, his problem is solvable with a few simple instructions.
OK Jay/Aooga.
Finally back from work.
Plug in your phone and put it into fastboot by typing adb reboot bootloader then type fastboot devices does it show that you are connected?
open cmd window, typed adb reboot bootloader, and got:
T063202TFL and fastboot, and then a prompt.
OK Jay/Aooga.
Finally back from work.
Plug in your phone and put it into fastboot by typing adb reboot bootloader then type fastboot devices does it show that you are connected?
open cmd window, typed adb reboot bootloader, and got:
T063202TFL and fastboot, and then a prompt.
Phone is in fastboot mode with white, yellow green text.
Device is unlocked. Status code 3.
Battery OK Charging
Transfer mode USB connected.
It looked as though I had to be able to accept the 4.4 kitkat OTA in order to get this done. but when i went to the usual spot to look for system updates it said there were none available.
Anyhow, I am super grateful for your help. Sorry to be such a remedial doofus
Looks like we can wait till tomorrow. Or today. Or whatever timeline it is.
Dear experts, I have seen similar threads as with the issue I am facing but I wasnt sure of few parts and if the process as a whole could work for me.
Here's what I know and what the problem is all about, appreciate any help to get back the phone in working condition.
First the basics:
HTC first
GSM unlocked, Bootloader unlocked and TWRP installed
I wanted to delete and format the device as I intended to give this to my friend and I did go to TWRP menu and then clicked on advanced wipe etc and realized I did erase everything the phone needs even to bootup. This I have done without taking backup.
What it looks like now:
When I boot the device out from TWRP, the 'F' logo comes up and stays like that for ever. If I go to TWRP pressing the power and volume down together, it goes to the TWRP menu and thats it..no options seem to help me on this screen to go past the 'F' logo at startup. If I simply power down the device on the 'F' screen it restarts and goes to the same screen making it look like its in a loop. Not sure if this is called soft-brick or hard-brick but it looks like the phone is of no use to me right now.
Can you guys please help me with resolving the problem..any help will be much appreciated
kuldeep_ch said:
Dear experts, I have seen similar threads as with the issue I am facing but I wasnt sure of few parts and if the process as a whole could work for me.
Here's what I know and what the problem is all about, appreciate any help to get back the phone in working condition.
First the basics:
HTC first
GSM unlocked, Bootloader unlocked and TWRP installed
I wanted to delete and format the device as I intended to give this to my friend and I did go to TWRP menu and then clicked on advanced wipe etc and realized I did erase everything the phone needs even to bootup. This I have done without taking backup.
What it looks like now:
When I boot the device out from TWRP, the 'F' logo comes up and stays like that for ever. If I go to TWRP pressing the power and volume down together, it goes to the TWRP menu and thats it..no options seem to help me on this screen to go past the 'F' logo at startup. If I simply power down the device on the 'F' screen it restarts and goes to the same screen making it look like its in a loop. Not sure if this is called soft-brick or hard-brick but it looks like the phone is of no use to me right now.
Can you guys please help me with resolving the problem..any help will be much appreciated
Click to expand...
Click to collapse
Sideload the stock rom and then flash it I've been in your situation and that's all that was needed to be done.
Be sure to also flash the boot.img if you aren't s-off
More questions
Thanks Abraham for your quick response.
I am starter with Android so, please help me how to sideload and also on where to get stock rom. I will also be lying if I said I understood whats s-off..? Please help further
Thanks
abrahammmmmmm_ said:
Sideload the stock rom and then flash it I've been in your situation and that's all that was needed to be done.
Be sure to also flash the boot.img if you aren't s-off
Click to expand...
Click to collapse
S-ON it is
I have checked on HBOOT screen and its S-ON
kuldeep_ch said:
I have checked on HBOOT screen and its S-ON
Click to expand...
Click to collapse
No problem! just be sure to hit that thanks button
Well then you'll have to make sure you flash the boot.IMG as well,
So what you'll do is
1) find the stock ROM around these threads
2) sideload the ROM
3) flash it
4) flash the boot.IMG inside the rom
5) you're done!
Understanding what s-on/off won't be of use here really d:
And the stock ROM is somewhere around these threads. About the side loading you might find a tutorial for that on YouTube. Sorry if it seems that I'm just leaving you in the dust but I am typing this in a hurry since it's 2:50 am at my place. I will be back to whip up a tutorial for you if YouTube wasn't of much help
Okay
Let me try my best till its like a more sociable time for you tomm morning, I will post my updates on the thread on how far I go and any questions I may have..
abrahammmmmmm_ said:
Well then you'll have to make sure you flash the boot.IMG as well,
So what you'll do is
1) find the stock ROM around these threads
2) sideload the ROM
3) flash it
4) flash the boot.IMG inside the rom
5) you're done!
If you need help with a tutorial or need me to go in depth with something it'll be quite a while from now because it's 2:40 am at my place. I'll assume you're a more advanced user since you've already got twrp and sound like you know what you're talking about
Click to expand...
Click to collapse
kuldeep_ch said:
Let me try my best till its like a more sociable time for you tomm morning, I will post my updates on the thread on how far I go and any questions I may have..
Click to expand...
Click to collapse
Yeah, just be sure not to wonder off too far from these threads on to other forums and flash or do something that can brick the device
Oh and btw I edited my post bc I saw your othe reply stating that you aren't all that too advanced with this
boot.img
I should be finding the boot.img on the stock ROM itself, isnt it..?
kuldeep_ch said:
Let me try my best till its like a more sociable time for you tomm morning, I will post my updates on the thread on how far I go and any questions I may have..
Click to expand...
Click to collapse
kuldeep_ch said:
I should be finding the boot.img on the stock ROM itself, isnt it..?
Click to expand...
Click to collapse
That's correct. Unzip the ROM and it should be there
This is how far I could get
Got all stock ROM and the IMG files, installed android SDK
ADB doesnt recognize the device to copy the file for sideloading
Guess issue is with the fact USB debugging was disabled earlier on my device
Can you please advise further
Is it better to chat on google chat or something so its even faster and I could get this fixed tonight (my time)
Thank you
Finally got it fixed
Thanks for the help..it all worked fine and the device is now working fine..
Thanks for all the guidance
kuldeep_ch said:
Got all stock ROM and the IMG files, installed android SDK
ADB doesnt recognize the device to copy the file for sideloading
Guess issue is with the fact USB debugging was disabled earlier on my device
Can you please advise further
Is it better to chat on google chat or something so its even faster and I could get this fixed tonight (my time)
Thank you
Click to expand...
Click to collapse
kuldeep_ch said:
Thanks for the help..it all worked fine and the device is now working fine..
Thanks for all the guidance
Click to expand...
Click to collapse
Great! Sorry I was away but it was getting very late. I'm glad everything worked out tho
kuldeep_ch said:
Got all stock ROM and the IMG files, installed android SDK
ADB doesnt recognize the device to copy the file for sideloading
Guess issue is with the fact USB debugging was disabled earlier on my device
Can you please advise further
Is it better to chat on google chat or something so its even faster and I could get this fixed tonight (my time)
Thank you
Click to expand...
Click to collapse
wait a sec...you dont have a rom or kernel on your device at the moment right?
then there is no way to turn on usb debug on or off cause there is nothing managing the device.
um...use cmd and do adb devices. if its not there then i have no idea but if fast-boot goes into usb mode try flasing it using code
not sure what you would use, but see if "fastboot flash update nameofROM.zip"
but im not sure if that is the right code
stock rom for htc first
kuldeep_ch said:
Got all stock ROM and the IMG files, installed android SDK
ADB doesnt recognize the device to copy the file for sideloading
Guess issue is with the fact USB debugging was disabled earlier on my device
Can you please advise further
Is it better to chat on google chat or something so its even faster and I could get this fixed tonight (my time)
Thank you
Click to expand...
Click to collapse
can you provide a stock rom for htc first because i am having a same issue as yours ........ mine is s off too .....
abrahammmmmmm_ said:
No problem! just be sure to hit that thanks button
Well then you'll have to make sure you flash the boot.IMG as well,
So what you'll do is
1) find the stock ROM around these threads
2) sideload the ROM
3) flash it
4) flash the boot.IMG inside the rom
5) you're done!
Understanding what s-on/off won't be of use here really d:
And the stock ROM is somewhere around these threads. About the side loading you might find a tutorial for that on YouTube. Sorry if it seems that I'm just leaving you in the dust but I am typing this in a hurry since it's 2:50 am at my place. I will be back to whip up a tutorial for you if YouTube wasn't of much help
Click to expand...
Click to collapse
can you please provide a tutorial and and all the link because i m kinda noob . I am unable to find them .
hey guys, Just trying to get my bearings on where to start. A friend game me a HTC Desire 510 that was not loading for him. Just sticking on the HTC loading screen.
He managed to "unlock" it. Not sure if it has root access.
In anycase it will not loal anymore, stuck on HTC load screen. I followed a few threads and tried to reset/restore things but now it looks like i need to just reinstall the OS.
Where I am lost is where/can i get the stock OS for this phone?
If not , do i need to get root access, load in a bootloader and then load in a custom ROM?
last time I did all this before was 2 years ago on a Samsung so I am a little rusty on the steps.
details
HTC Desire 510 - europe (Irish)
HBOOT - 3.19.0.0000
Radio 01.02.012
When I load up the bootloader I have "Sofrware status: Officaial *** at the tope and UNLOCKED under that.
Cheers
check the htc website for the latest rom(update) also this thread is sprint/virgin/boost
http://forum.xda-developers.com/desire-510/development/virgin-sprint-htc-desire-510-stock-t2961521
cricket stock rom: http://forum.xda-developers.com/desire-510/help/stock-rom-cricket-htc-desire-510-t3161697
id see if the htc site works first but thats just me.
hope i was of help to you with your issues if not wait for more experanced members to assist.
roymcd said:
hey guys, Just trying to get my bearings on where to start. A friend game me a HTC Desire 510 that was not loading for him. Just sticking on the HTC loading screen.
He managed to "unlock" it. Not sure if it has root access.
In anycase it will not loal anymore, stuck on HTC load screen. I followed a few threads and tried to reset/restore things but now it looks like i need to just reinstall the OS.
Where I am lost is where/can i get the stock OS for this phone?
If not , do i need to get root access, load in a bootloader and then load in a custom ROM?
last time I did all this before was 2 years ago on a Samsung so I am a little rusty on the steps.
details
HTC Desire 510 - europe (Irish)
HBOOT - 3.19.0.0000
Radio 01.02.012
When I load up the bootloader I have "Sofrware status: Officaial *** at the tope and UNLOCKED under that.
Cheers
Click to expand...
Click to collapse
Are you in Europe? If you are that's most likely a 64 bit phone and you'll need Philz Touch Recovery unless you have one installed. You'll also need to find a 64 bit stock HTC desire 510 rom.. It should work after installing them.
Edit: The HTC websites rom updater will not work since the phones boot is unlocked.. Just try what I said above.
Yes I am in Europe.
Will give what suggested a go and let you know..
cheers
here is your man for the job
ok mthis has happen to me before alright take the sdcard out reboot to fastboot relocok bootloader by typing 'fastboot oem relock' get the ruu for your phone then it will help you if you find this helpful hit the thank you button
bcbradley12 said:
ok mthis has happen to me before alright take the sdcard out reboot to fastboot relocok bootloader by typing 'fastboot oem relock' get the ruu for your phone then it will help you if you find this helpful hit the thank you button
Click to expand...
Click to collapse
It's actually fastboot oem lock
bcbradley12 said:
ok mthis has happen to me before alright take the sdcard out reboot to fastboot relocok bootloader by typing 'fastboot oem relock' get the ruu for your phone then it will help you if you find this helpful hit the thank you button
Click to expand...
Click to collapse
MrMike2182 said:
Are you in Europe? If you are that's most likely a 64 bit phone and you'll need Philz Touch Recovery unless you have one installed. You'll also need to find a 64 bit stock HTC desire 510 rom.. It should work after installing them.
Edit: The HTC websites rom updater will not work since the phones boot is unlocked.. Just try what I said above.
Click to expand...
Click to collapse
Ok guys , getting around to trying this now but running into some small problems.
Question 1
I have installed adb.exe and it does work with my main phone (HTC m8) but when i plug in the broken phone it does not pick up that phone (when i do a ">adb.exe devices") I saw some comments saying that I need to enable debug mode but how can I do that when i cannot even load the phone up ?
Question 2
I would like to install this Philz Touch Recovery , so i can installed the new RUU but I see on some sites that I need to install ClockworkMod first. Now I am not sure if this is needed or not but i still have the problem of being unable to install it from the bootloader screen. There is no option to install from zip? So this might sound like a real n00b question but how can install anything to my phone when all i have it the bootloader screen. My options when i boot up are . . .
Fastboot
-->HBOOT
-->RAMDUMP
-->REBOOT
-->REBOOT fastboot
-->power down
recovery
factory reset
simlock
check smartSD
image CRC show barcode.
Review. . .
I would think my issue is with the broken phones connecting to my laptop and the use of adb.exe. If I could get that working i can use adb.exe to installl clockworkmod and from that I can boot up the phone and install Philz Touch Recovery, and then using phils installer I can install the original 64bit Rom and be in business?
does that seem right?
Cheers
roymcd said:
Ok guys , getting around to trying this now but running into some small problems.
Question 1
I have installed adb.exe and it does work with my main phone (HTC m8) but when i plug in the broken phone it does not pick up that phone (when i do a ">adb.exe devices") I saw some comments saying that I need to enable debug mode but how can I do that when i cannot even load the phone up ?
Question 2
I would like to install this Philz Touch Recovery , so i can installed the new RUU but I see on some sites that I need to install ClockworkMod first. Now I am not sure if this is needed or not but i still have the problem of being unable to install it from the bootloader screen. There is no option to install from zip? So this might sound like a real n00b question but how can install anything to my phone when all i have it the bootloader screen. My options when i boot up are . . .
Fastboot
-->HBOOT
-->RAMDUMP
-->REBOOT
-->REBOOT fastboot
-->power down
recovery
factory reset
simlock
check smartSD
image CRC show barcode.
Review. . .
I would think my issue is with the broken phones connecting to my laptop and the use of adb.exe. If I could get that working i can use adb.exe to installl clockworkmod and from that I can boot up the phone and install Philz Touch Recovery, and then using phils installer I can install the original 64bit Rom and be in business?
does that seem right?
Cheers
Click to expand...
Click to collapse
Never mind if figured it out. .
roymcd said:
Never mind if figured it out. .
Click to expand...
Click to collapse
Nice to see you figured it out!
MrMike2182 said:
Nice to see you figured it out!
Click to expand...
Click to collapse
Well now that you say that. I am having a strange issue. The phone will boot but only when I select "recovery" mode from the bootloader?
I presume what I have done is flashed the wrong image to the wrong section. I think i need to to flash something to boot and not to recovery when I was running the "fastboot flash recovery image.img!"
ideas?
roymcd said:
Well now that you say that. I am having a strange issue. The phone will boot but only when I select "recovery" mode from the bootloader?
I presume what I have done is flashed the wrong image to the wrong section. I think i need to to flash something to boot and not to recovery when I was running the "fastboot flash recovery image.img!"
ideas?
Click to expand...
Click to collapse
I don't get what you're trying to do. If you wanna get back up and running, all you have to do is relock the bootloader and run the RUU... That's it. Your recovery doesn't matter. You don't need a custom recovery for that. Any custom recovery you have will be replaced by the stock one when you run the RUU.
I haven't been on this forum much lately, (so please correct me if I'm wrong, somebody) but from what I remember, the only custom recovery available for the 64-bit variant 510 is Philz. If that's the case then you shouldn't be flashing CWM
Surj138 said:
I don't get what you're trying to do. If you wanna get back up and running, all you have to do is relock the bootloader and run the RUU... That's it. Your recovery doesn't matter. You don't need a custom recovery for that. Any custom recovery you have will be replaced by the stock one when you run the RUU.
I haven't been on this forum much lately, (so please correct me if I'm wrong, somebody) but from what I remember, the only custom recovery available for the 64-bit variant 510 is Philz. If that's the case then you shouldn't be flashing CWM
Click to expand...
Click to collapse
Yes you seem to be correct . I locked the bootloader and then used the command "fastboot flash boot <htc_orginal_ruu>" and it started working again.
I had lots of issues trying to get the CWM installed . It was someone else on this thread that suggested that but I think that info was wrong.
And just to conform for others that may read this someday you do not need Phils recover if you want to get the original system running. if you want to install custom ROMs then you need it then.
Thanks for the input. Half the time its just good to write out your problem so you can understand.
roymcd said:
Yes you seem to be correct . I locked the bootloader and then used the command "fastboot flash boot <htc_orginal_ruu>" and it started working again.
I had lots of issues trying to get the CWM installed . It was someone else on this thread that suggested that but I think that info was wrong.
And just to conform for others that may read this someday you do not need Phils recover if you want to get the original system running. if you want to install custom ROMs then you need it then.
Thanks for the input. Half the time its just good to write out your problem so you can understand.
Click to expand...
Click to collapse
I did say you needed philz touch recovery if you have a 64 bit phone and you never really answered the 64 bit question and I asked because you said you are in Europe (Irish) and if you do have a 64 bit phone then you do need philz if you want to use other roms like the rest (most) of us on here do.
MrMike2182 said:
I did say you needed philz touch recovery if you have a 64 bit phone and you never really answered the 64 bit question and I asked because you said you are in Europe (Irish) and if you do have a 64 bit phone then you do need philz if you want to use other roms like the rest (most) of us on here do.
Click to expand...
Click to collapse
Yeah it was a 64bit phone.
I wanted the original OS back on the phone so that is why i did not need phils tool.
roymcd said:
Yeah it was a 64bit phone.
I wanted the original OS back on the phone so that is why i did not need phils tool.
Click to expand...
Click to collapse
I kinda figured all that out on my own already but why do you just want stock? Why don't you want a rooted phone so you can do a lot more with it?
---------- Post added at 05:46 AM ---------- Previous post was at 05:28 AM ----------
roymcd said:
Yes you seem to be correct . I locked the bootloader and then used the command "fastboot flash boot <htc_orginal_ruu>" and it started working again.
I had lots of issues trying to get the CWM installed . It was someone else on this thread that suggested that but I think that info was wrong.
And just to conform for others that may read this someday you do not need Phils recover if you want to get the original system running. if you want to install custom ROMs then you need it then.
Thanks for the input. Half the time its just good to write out your problem so you can understand.
Click to expand...
Click to collapse
I've read through this entire thread more than 3 times and I never once seen anyone in this thread tell you to run CWM(ClockWorkMod).. or to even use that so where did get that idea from... The only thing I suggested was Philz Touch Recovery as did @Surj138 for a good reason cause it's the only one that's 64 bit for your phone!
MrMike2182 said:
I kinda figured all that out on my own already but why do you just want stock? Why don't you want a rooted phone so you can do a lot more with it?
---------- Post added at 05:46 AM ---------- Previous post was at 05:28 AM ----------
I've read through this entire thread more than 3 times and I never once seen anyone in this thread tell you to run CWM(ClockWorkMod).. or to even use that so where did get that idea from... The only thing I suggested was Philz Touch Recovery as did @Surj138 for a good reason cause it's the only one that's 64 bit for your phone!
Click to expand...
Click to collapse
It was from other threads that I read to install Phils recovery I would need install CWM but I think now that is for other phones. I said it was in this thread by mistake.
As for going for the original ROM as opposed to a custom ROM my reasoning is three fold. . . .
1. This phone will not be staying with me. Will be giving it back to my friend who is giving it to his daughter. She is would have no use for a root phone.
2. The last time I was using custom ROM was with my Samsung S2 about 3 years ago. I did like all the extra features, free apps and full customization that you can do with it but I did find that no matter what custom ROM I found there would be little problems with each one. Performance would slowly drop the more i switched around the custom ROMS.
3. Custom ROMs are great and all but we cannot be 100% sure there is not hidden male-ware in some of them that is robbing my data. It was going to be a spare phone for playing games then i would not mind but to give to someone as there main phone is not the best option.
roymcd said:
It was from other threads that I read to install Phils recovery I would need install CWM but I think now that is for other phones. I said it was in this thread by mistake.
As for going for the original ROM as opposed to a custom ROM my reasoning is three fold. . . .
1. This phone will not be staying with me. Will be giving it back to my friend who is giving it to his daughter. She is would have no use for a root phone.
2. The last time I was using custom ROM was with my Samsung S2 about 3 years ago. I did like all the extra features, free apps and full customization that you can do with it but I did find that no matter what custom ROM I found there would be little problems with each one. Performance would slowly drop the more i switched around the custom ROMS.
3. Custom ROMs are great and all but we cannot be 100% sure there is not hidden male-ware in some of them that is robbing my data. It was going to be a spare phone for playing games then i would not mind but to give to someone as there main phone is not the best option.
Click to expand...
Click to collapse
Understood sir!!